3db18528diaa - v1 - 9500 MPR Users Manual (Etsi) r1.4.0

9500 MPR ETSI
Microwave Packet Radio
Rel. 1.4.0
User Manual
3DB 18528 DIAA
Issue 1
February 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 18528 DIAA

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

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

2.1 Purpose and Function ......................................................................................................... 40
2.1.1 Innovative solutions ........................................................................................................ 40
2.1.2 Description ...................................................................................................................... 43
2.1.3 MSS Purpose, Function and Description ........................................................................ 43
2.1.4 Stacking configuration..................................................................................................... 46
2.1.5 ODU300 .......................................................................................................................... 47
2.1.6 MSS-ODU cable (Interfaces and Traffic) ........................................................................ 48
2.1.7 Antennas......................................................................................................................... 48
2.2 Radio capacity, channelling and modulation .................................................................... 49
2.3 Main Features....................................................................................................................... 50
2.4 Radio Configurations .......................................................................................................... 51
2.5 Typical System Configurations .......................................................................................... 51
2.6 Environmental & Electrical Characteristics ...................................................................... 55
2.6.1 Outdoor Units (6 to 15 GHz) ........................................................................................... 55
2.6.2 Outdoor Units (18 to 38 GHz) ......................................................................................... 58
2.6.3 System Parameters ........................................................................................................ 60
2.6.4 RTPC (Manual Transmit Power Control) ........................................................................ 61
2.6.5 Minimizing Latency Latency contribution for a 9500 MPR-E Cloud ............................. 63
2.7 Parts Lists............................................................................................................................. 64
2.7.1 MSS ................................................................................................................................ 64
2.7.2 ODU300 with internal lightning surge suppressor .......................................................... 67
2.8 Functional description ........................................................................................................ 81
2.8.1 MSS (Indoor Unit) ........................................................................................................... 81
2.8.2 ODU300 .......................................................................................................................... 92
2.8.3 Protection schemes ........................................................................................................ 96
2.8.4 Radio Transmission Features ......................................................................................... 101
2.8.5 TMN communication channels ....................................................................................... 104
2.8.6 Admission control ........................................................................................................... 104
User Manual 9500 MPR ETSI Rel. 1.4.0

Table of Contents 3DB 18528 DIAA Issue 1 1/578
2.8.7 Traffic profiles ................................................................................................................. 109
2.8.8 ATM Traffic Management................................................................................................ 113
2.8.9 Ethernet Traffic Management ......................................................................................... 117
2.8.10 Quality Of Services (QoS) ............................................................................................ 119
2.8.11 Cross-connection .......................................................................................................... 125
2.8.12 Synchronization for PDH/DATA .................................................................................... 126
2.8.13 Synchronization for E1 ports with ASAP unit ................................................................ 129
2.8.14 Synchronization distribution from 9500 MPR to 9400 AWY.......................................... 130
2.8.15 Synchronization connection in Stacking configuration with Core protection ................. 131
3 NE MANAGEMENT BY SOFTWARE APPLICATION ................................................................. 133

3.1 Network Element Overview................................................................................................. 133
3.1.1 Main view ........................................................................................................................ 133
3.1.2 NE Configuration area .................................................................................................... 134
3.1.3 Status & Alarms area ...................................................................................................... 135
3.1.4 Supervision Function ...................................................................................................... 136
3.1.5 Menu bar......................................................................................................................... 136
3.2 Main View.............................................................................................................................. 139
3.2.1 Tab-panels ...................................................................................................................... 139
3.2.2 Main Tool Bar Area ......................................................................................................... 141
3.2.3 Severity Alarm Area ........................................................................................................ 141
3.2.4 Domain Alarm Synthesis Area ........................................................................................ 142
3.2.5 Management State Control Area .................................................................................... 142
3.2.6 Selection Criteria ............................................................................................................ 143
3.3 How to configure a new equipment ................................................................................... 145
3.4 Menu Configuration ............................................................................................................. 146
3.4.1 Menu NE Time ................................................................................................................ 146
3.4.2 Menu Network Configuration .......................................................................................... 147
3.4.3 Menu Alarm Severities.................................................................................................... 152
3.4.4 Menu System Settings .................................................................................................... 153
3.4.5 Menu Cross connections ................................................................................................ 156
3.4.6 AUX Cross Connections ................................................................................................. 189
3.4.7 Menu VLAN Configuration .............................................................................................. 191
3.4.8 Traffic Descriptors ........................................................................................................... 192
3.4.9 Menu Profile Management.............................................................................................. 194
3.5 Menu Diagnosis ................................................................................................................... 199
3.5.1 Alarms............................................................................................................................. 199
3.5.2 Log Browsing .................................................................................................................. 206
3.5.3 Remote Inventory ........................................................................................................... 209
3.5.4 Abnormal Condition List.................................................................................................. 210
3.5.5 Summary Block Diagram View ....................................................................................... 211
3.5.6 Current Configuration View............................................................................................. 218
3.6 Menu Supervision ................................................................................................................ 219
3.6.1 Access State ................................................................................................................... 219
3.6.2 Restart NE ...................................................................................................................... 220
3.6.3 MIB Management ........................................................................................................... 220
3.6.4 SW Licence..................................................................................................................... 223
3.7 Menu SW Download............................................................................................................. 224
3.7.1 Server Access Configuration .......................................................................................... 224
3.7.2 Init Sw Download ............................................................................................................ 225
3.7.3 Sw Status ........................................................................................................................ 226
3.8 Tab-panel Equipment........................................................................................................... 228
3.8.1 General ........................................................................................................................... 228
3.8.2 Starting From Scratch ..................................................................................................... 230
9500 MPR ETSI Rel. 1.4.0 User Manual

2/578 3DB 18528 DIAA Issue 1 Table of Contents
3.8.3 Tab panels in the Resource Detail Area.......................................................................... 231
3.8.4 Alarms tab-panel............................................................................................................. 231
3.8.5 Settings tab-panel ........................................................................................................... 232
3.8.6 Remote Inventory tab-panel............................................................................................ 234
3.8.7 How to configure a new equipment ................................................................................ 234
3.9 Tab-panel Protection Schemes........................................................................................... 236
3.9.1 Equipment Protection Management ............................................................................... 239
3.9.2 Rx Radio Protection Management .................................................................................. 240
3.9.3 HSB Protection Management ......................................................................................... 242
3.10 Tab-panel Synchronization ............................................................................................... 244
3.10.1 How to synchronize ...................................................................................................... 244
3.11 Tab-panel Connections...................................................................................................... 247
3.12 PDH VIEW for PDH DOMAIN (this menu opens with double click on a PDH unit)....... 248
3.12.1 General information on the PDH domain menu ............................................................ 248
3.12.2 Alarms & Settings ......................................................................................................... 248
3.12.3 Loopback ...................................................................................................................... 255
3.13 RADIO VIEW for RADIO DOMAIN (this menu opens with double click
on a Radio unit)................................................................................................................. 257
3.13.1 General information on the Radio domain menu .......................................................... 257
3.13.2 Alarms........................................................................................................................... 257
3.13.3 Settings......................................................................................................................... 258
3.13.4 Measurement................................................................................................................ 267
3.13.5 Loopback ...................................................................................................................... 269
3.14 ATM view for ATM DOMAIN (this menu opens with double click on an ASAP unit).... 272
3.14.1 E1 Layer ....................................................................................................................... 272
3.14.2 IMA Layer ..................................................................................................................... 273
3.14.3 ATM Layer..................................................................................................................... 275
3.14.4 ATM PW Layer.............................................................................................................. 281
3.15 Core-E view for Core-E and ETHERNET DOMAIN (this menu opens with
double click on a Core-E unit) ......................................................................................... 283
3.15.1 Core-E domain.............................................................................................................. 283
3.16 AUX view for AUX DOMAIN (this menu opens with double click on the
AUX peripheral unit) ......................................................................................................... 290
3.16.1 Settings......................................................................................................................... 290
3.16.2 External Points.............................................................................................................. 290
3.17 Performance Monitoring tool............................................................................................ 293
3.17.1 Core-E unit performances............................................................................................. 294
3.17.2 MD300 unit performances ............................................................................................ 299
3.17.3 P32E1DS1 unit performances ...................................................................................... 314
3.17.4 A16E1DS1 (ASAP) unit performances ......................................................................... 329
3.18 VLAN management ............................................................................................................ 335
3.18.1 802.1D .......................................................................................................................... 335
3.18.2 802.1Q .......................................................................................................................... 336
4 INSTALLATION............................................................................................................................ 339
4.1 Hardware Installation........................................................................................................... 339
4.1.1 Power consumption ........................................................................................................ 339
4.1.2 Rack Installation ............................................................................................................. 340
4.1.3 ODU300 Installation........................................................................................................ 354
4.1.4 Indoor Installation ........................................................................................................... 375
4.1.5 Antenna Alignment ......................................................................................................... 420
4.2 Software local copy ............................................................................................................. 428
4.2.1 Getting Started ................................................................................................................ 429
4.2.2 PC Characteristics .......................................................................................................... 429

4.2.3 Download Software Package (SWP) to PC .................................................................... 430
4.2.4 Download Craft Terminal (CT) and TCO Suite Software to PC ...................................... 433
4.2.5 Configure PC Network Card to Connect to NE ............................................................... 438
4.2.6 Download Software Package to NE................................................................................ 442
5 PROVISIONING............................................................................................................................ 449
5.1 Provisioning by WebEML.................................................................................................... 449
5.1.1 Start WebEML................................................................................................................. 449
5.1.2 Provisioning .................................................................................................................... 452
5.2 Provisioning by Provisioning tool...................................................................................... 489
5.2.1 Start Provisioning tool ..................................................................................................... 489
6 MAINTENANCE AND TROUBLE-CLEARING ............................................................................ 513

6.1 Introduction .......................................................................................................................... 513
6.2 Maintenance Philosophy..................................................................................................... 514
6.3 Personal Computer (PC)/Laptop ........................................................................................ 514
6.4 Troubleshooting................................................................................................................... 514
6.4.1 Before Going to Site Checklist ........................................................................................ 514
6.4.2 Troubleshooting Basics................................................................................................... 515
6.4.3 Troubleshooting Path Problems...................................................................................... 523
6.4.4 Troubleshooting Configuration Problems........................................................................ 525
6.4.5 Troubleshooting Ethernet Problems ............................................................................... 525
6.4.6 Troubleshooting TMN Problems ..................................................................................... 526
6.5 Card Removal and REPLACEMENT ................................................................................... 528
6.5.1 Core-E Card Removal and Replacement Core-E Protected Radio ............................. 530
6.5.2 Flash card replacement procedure ................................................................................. 530
6.6 Replacement procedure of Core-B card with Core-E card .............................................. 531
6.6.1 Core replacement from Rel. 1.1.0................................................................................... 531
6.6.2 Core replacement from Rel. 1.1.1................................................................................... 532
6.7 Upgrade from Not Protected to a Protected Radio (with ODU300) ................................. 533
6.7.1 1+0 Adaptive Modulation to 1+1 HSB Adaptive Modulation and 1+1 EPS..................... 533
6.7.2 1+0 Static Modulation to 1+1 HSB Static Modulation and 1+1 EPS ............................... 534
6.7.3 1+0 to 1+1 Frequency Diversity and 1+1 EPS................................................................ 534
6.8 Downgrade from Protected to a Not Protected Radio (with ODU300) ............................ 535
6.8.1 1+1 HSB Adaptive Modulation and 1+1 EPS to 1+0 Adaptive Modulation..................... 535
6.8.2 1+1 HSB Static Modulation and 1+1 EPS to 1+0 Static Modulation ............................... 536
6.8.3 1+1 FD to 1+0 ................................................................................................................. 536
6.9 Cleaning................................................................................................................................ 537
7 LINEUP AND COMMISSIONING ............................................................................................... 539

7.1 Introduction .......................................................................................................................... 540
7.1.1 General ........................................................................................................................... 540
7.1.2 SafetyEMCEMFESD norms and cautions to avoid equipment damage ................... 541
7.1.3 Conventions.................................................................................................................... 541
7.1.4 Summary of the lineup, commissioning, and acceptance phases ................................ 542
7.1.5 General information about test bench drawings ............................................................. 543
7.2 Commissioning of STATION A phase 1 (Turn up).......................................................... 544
7.2.1 Turnon preliminary operations ...................................................................................... 544
7.2.2 Powering up the MSS(s) with ODU(s) connected........................................................... 545
7.3 Commissioning of STATION B phase 1 (Turn up).......................................................... 545
7.4 Fine antenna alignment and preliminary checks Stations A & B ................................. 545
7.4.1 Fine antenna alignment .................................................................................................. 545
7.4.2 Preliminary checks.......................................................................................................... 546
7.5 End of commissioning phase 1 (Turn up) in STATION A ................................................. 550
7.6 Commissioning station A phase 2 (acceptance test) .................................................... 551

7.6.1 Installation and cabling visual inspection ........................................................................ 553
7.6.2 System configuration ...................................................................................................... 553
7.6.3 P32E1 unit ...................................................................................................................... 559
7.6.4 16E1/DS1 ASAP unit ...................................................................................................... 561
7.6.5 AUX unit.......................................................................................................................... 562
7.6.6 Core-E unit...................................................................................................................... 562
7.6.7 NE configuration ............................................................................................................. 563
7.6.8 Data/Time settings .......................................................................................................... 563
7.6.9 Hop E1 stability test ........................................................................................................ 564
7.6.10 Ethernet Traffic stability test.......................................................................................... 565
7.6.11 ATM Traffic stability test ................................................................................................ 569
7.6.12 64 kbit/s Service Channel functionality test (optional) .................................................. 571
7.7 Commissioning station B Phase 2 (acceptance Test) ................................................... 572
7.8 Final operations ................................................................................................................... 572
7.9 Annex A: fine antenna alignment ....................................................................................... 572
ABBREVIATIONS ............................................................................................................................ 573
CUSTOMER DOCUMENTATION FEEDBACK.............................................................................. 577

LIST OF FIGURES
Figure 1. Multiservice Aggregation Layer ......................................................................................... 40
Figure 2. Service Awareness ............................................................................................................ 41
Figure 3. Packet Node ...................................................................................................................... 42
Figure 4. Service-driven Packet Adaptive Modulation ...................................................................... 42
Figure 5. Naming Convention ........................................................................................................... 43
Figure 6. MSS-8 shelf ....................................................................................................................... 44
Figure 7. MSS-4 shelf ....................................................................................................................... 44
Figure 8. MSS-8 block diagram ........................................................................................................ 45
Figure 9. MSS-4 block diagram ........................................................................................................ 46
Figure 10. Stacking configuration with 2 MSS .................................................................................. 46
Figure 11. Stacking configuration with Core protection ..................................................................... 47
Figure 12. ODU300........................................................................................................................... 47
Figure 13. TDM/ATM Over Ethernet Packet Node - Mapping of 32 E1 TDM and
16 E1 ATM on Ethernet................................................................................................... 52
Figure 14. TDM/ATM and Ethernet Terminal Packet Transport 32 E1 TDM and
16 E1 ATM Access, 1 Radio Direction ............................................................................ 52
Figure 15. TDM/ATM and Ethernet Add/Drop N1 Packed Node-Ethernet and
32 E1 TDM and 16 E1 ATM Local Access, 1 Back Link, 1 Haul Link ............................. 52
Figure 16. TDM/ATM and Ethernet Terminal Packet Node-Ethernet and 32 E1 TDM and
16 E1 ATM Local Access, 2 Back Links.......................................................................... 53
Figure 17. TDM/ATM and Ethernet Add/Drop Packet Node-Ethernet and 32 E1 TDM and
16 E1 ATM Local Access, 1 back Link and 2 Haul Links ................................................ 53
Figure 18. TDM/ATM and Ethernet Add/Drop NN Packet Node-ethernet and 32 E1 TDM and
16 E1 ATM Local Access, 2 Haul Links and 2 Back Links .............................................. 54
Figure 19. Power Distribution Architecture ....................................................................................... 82
Figure 20. Core-E unit....................................................................................................................... 83
Figure 21. Core-E unit....................................................................................................................... 84
Figure 22. 32xE1 Local Access unit.................................................................................................. 84
Figure 23. PDH Access unit.............................................................................................................. 85
Figure 24. ASAP simplified block diagram........................................................................................ 87
Figure 25. ASAP unit ........................................................................................................................ 88
Figure 26. Modem unit ...................................................................................................................... 88
Figure 27. Modem unit ...................................................................................................................... 89
Figure 28. AUX peripheral unit block diagram .................................................................................. 90
Figure 29. AUX peripheral unit.......................................................................................................... 91
Figure 30. 9500 MPR-E ODU 300 housing....................................................................................... 92
Figure 31. ODU block diagram ......................................................................................................... 93
Figure 32. 9500 MPR-E Packet Node Full Protection (Radio).......................................................... 96
Figure 33. 9500 MPR-E Packet Node Full Protection (Radio).......................................................... 96
Figure 34. Core-E protection (PDH unit - 1+0).................................................................................. 98
Figure 35. Core-E protection (PDH unit - 1+1).................................................................................. 98
Figure 36. Core-E protection (Radio unit - 1+0)................................................................................ 99
Figure 37. Core-E protection (Radio unit - 1+1)................................................................................ 99
Figure 38. Available loopbacks ......................................................................................................... 102
Figure 39. Example of traffic in case of 28MHz bandwidth and Admission Control Enabled............ 105
Figure 40. Example of traffic in case of 28MHz bandwidth and modulation downgraded to 16QAM 106
Figure 41. Example of traffic in case of 28MHz bandwidth and modulation downgraded to 4QAM . 106
Figure 42. Example of traffic in case of 28MHz bandwidth and Admission Control Disabled........... 107
Figure 43. Example of traffic in case of 28MHz bandwidth and modulation downgraded to 16QAM 108
Figure 44. Example of traffic in case of 28MHz bandwidth and modulation downgraded to 4QAM . 108
Figure 45. Traffic profiles .................................................................................................................. 109
Figure 46. Traffic profiles .................................................................................................................. 110

List of Figures 3DB 18528 DIAA Issue 1 7/578
Figure 47. E1 Traffic.......................................................................................................................... 110
Figure 48. E1 Traffic.......................................................................................................................... 111
Figure 49. E1 Traffic.......................................................................................................................... 112
Figure 50. ATM Traffic Management - General block diagram ......................................................... 113
Figure 51. Block diagram for ATM Ingress (ATM -> Packet) direction .............................................. 114
Figure 52. ATM Traffic Management on Modem card - Block diagram............................................. 117
Figure 53. QoS in the Core-E unit..................................................................................................... 120
Figure 54. QoS in the Modem unit .................................................................................................... 122
Figure 55. Cross-connection............................................................................................................. 125
Figure 56. Synchronization ............................................................................................................... 128
Figure 57. Synchronization distribution from MPR to AWY............................................................... 130
Figure 58. Synchronization connection in Stacking configuration with Core protection .................... 131
Figure 59. NETO main view: initial screen ........................................................................................ 133
Figure 60. NETO main view: reduced screen ................................................................................... 134
Figure 61. NETO NE Configuration View: NE Information................................................................ 134
Figure 62. NETO NE Configuration View: NE Description................................................................ 135
Figure 63. NETO NE Configuration View: Command Buttons .......................................................... 135
Figure 64. Main View: Status & Alarms............................................................................................. 135
Figure 65. NETO List Management .................................................................................................. 137
Figure 66. MSS-8 Main view............................................................................................................. 139
Figure 67. MSS-4 Main view............................................................................................................. 140
Figure 68. System Settings menu..................................................................................................... 153
Figure 69. Main Cross-Connections View......................................................................................... 156
Figure 70. Cross-connections Example ............................................................................................ 157
Figure 71. Creating cross-connection between PDH and radio........................................................ 158
Figure 72. Cross-connections buttons .............................................................................................. 158
Figure 73. Segregated Port View (default configuration) .................................................................. 159
Figure 74. Not segregated ports ....................................................................................................... 160
Figure 75. Port #2 to Port #5 segregated.......................................................................................... 160
Figure 76. Segregated Ports............................................................................................................. 160
Figure 77. Actual coloured view example ......................................................................................... 162
Figure 78. PDH-Radio configuration dialog ...................................................................................... 163
Figure 79. Completed PDH-radio cross-connection ......................................................................... 164
Figure 80. Radio-radio configuration dialog ...................................................................................... 165
Figure 81. Completed radio-radio cross-connection ......................................................................... 166
Figure 82. Radio-Ethernet configuration dialog (ranges) .................................................................. 167
Figure 83. Radio-Ethernet configuration dialog (values)................................................................... 168
Figure 84. Completed radio-Ethernet cross-connection ................................................................... 169
Figure 85. PDH-Ethernet configuration dialog .................................................................................. 170
Figure 86. Completed PDH-Ethernet cross-connection.................................................................... 171
Figure 87. No protection ................................................................................................................... 171
Figure 88. 1+1 radio protection between NE B and C ...................................................................... 172
Figure 89. 1+1 EPS protection in NE A............................................................................................. 172
Figure 90. PDH-radio cross-connection modification........................................................................ 173
Figure 91. Modifying a Radio-Radio cross-connection ..................................................................... 174
Figure 92. Modifying a Radio-Ethernet cross-connection ................................................................. 175
Figure 93. Modifying a PDH-Ethernet cross-connection................................................................... 176
Figure 94. ASAP-Radio configuration dialog .................................................................................... 177
Figure 95. Completed ASAP-radio cross-connection ....................................................................... 178
Figure 96. Radio-radio configuration dialog ...................................................................................... 179
Figure 97. Traffic Descriptor.............................................................................................................. 179
Figure 98. Completed radio-radio cross-connection ......................................................................... 180
Figure 99. Radio-Ethernet configuration dialog ................................................................................ 181
Figure 100. Completed Radio-Ethernet cross-connection ................................................................ 182

8/578 3DB 18528 DIAA Issue 1 List of Figures
Figure 101. ASAP-Ethernet configuration dialog .............................................................................. 183
Figure 102. Completed ASAP-Ethernet cross-connection................................................................ 184
Figure 103. ASAP-radio cross-connection modification.................................................................... 185
Figure 104. Modifying a Radio-Radio cross-connection ................................................................... 186
Figure 105. Modifying a Radio-Ethernet cross-connection ............................................................... 187
Figure 106. Modifying an ASAP-Ethernet cross-connection............................................................. 188
Figure 107. Auxiliary Cross Connections menu................................................................................ 189
Figure 108. New AUX Cross Connection.......................................................................................... 190
Figure 109. Delete an AUX Cross Connection ................................................................................. 191
Figure 110. Traffic Description View.................................................................................................. 192
Figure 111. Login window.................................................................................................................. 194
Figure 112. Login Failed ................................................................................................................... 194
Figure 113. Profiles Management ..................................................................................................... 195
Figure 114. Create User.................................................................................................................... 196
Figure 115. Delete user confirmation ................................................................................................ 197
Figure 116. Confirm Administrator Password to Delete a User......................................................... 197
Figure 117. Change Password of User by Admin ............................................................................. 198
Figure 118. Change User Password ................................................................................................. 198
Figure 119. Cross-connection (Main) block diagram......................................................................... 211
Figure 120. 1+0 block diagram (PDH unit) (without Core-E protection)............................................ 212
Figure 121. 1+0 block diagram (PDH unit) (with Core-E protection)................................................. 213
Figure 122. 1+1 block diagram (PDH units) (without Core-E protection).......................................... 213
Figure 123. 1+1 block diagram (PDH units) (with Core-E protection)............................................... 214
Figure 124. 1+0 block diagram (Radio unit) (without Core-E protection).......................................... 215
Figure 125. 1+0 block diagram (Radio unit) (with Core-E protection)............................................... 215
Figure 126. 1+1 FD block diagram (Radio units) (without Core-E protection) .................................. 216
Figure 127. 1+1 FD block diagram (Radio units) (with Core-E protection) ....................................... 216
Figure 128. 1+1 Hot Standby block diagram (Radio units) (without Core-E protection) ................... 217
Figure 129. 1+1 Hot Standby block diagram (Radio units) (with Core-E protection) ........................ 217
Figure 130. Panel 1 (Committed software) ....................................................................................... 226
Figure 131. Panel 2 (Stand by software)........................................................................................... 227
Figure 132. SW units details ............................................................................................................. 227
Figure 133. Equipment View (starting from scratch) with MSS-8...................................................... 230
Figure 134. Expected Equipment Type Configuration ...................................................................... 232
Figure 135. Protection Example........................................................................................................ 233
Figure 136. SFP plug-in enabling ..................................................................................................... 235
Figure 137. Protection scheme screen ............................................................................................. 237
Figure 138. 1+1 PDH unit block diagram .......................................................................................... 237
Figure 139. 1+1 Radio unit block diagram (FD) ................................................................................ 238
Figure 140. 1+1 Radio unit block diagram (HSB) ............................................................................. 238
Figure 141. Synchronization Settings view ....................................................................................... 244
Figure 142. Synchronization ............................................................................................................. 245
Figure 143. Cross-Connections View ............................................................................................... 247
Figure 144. 9500 MPR-E applications .............................................................................................. 253
Figure 145. 9500 MPR-E applications .............................................................................................. 253
Figure 146. Node timing.................................................................................................................... 254
Figure 147. E1 Loopbacks ................................................................................................................ 255
Figure 148. Radio unit without Adaptive Modulation settings ........................................................... 259
Figure 149. Radio unit with Adaptive Modulation settings ................................................................ 260
Figure 150. Loopback ....................................................................................................................... 270
Figure 151. ASAP E1 Layer view...................................................................................................... 272
Figure 152. ASAP IMA Layer view.................................................................................................... 273
Figure 153. IMA Link Monitoring ....................................................................................................... 274
Figure 154. IMA Group Monitoring.................................................................................................... 274

Figure 155. ATM Interface type......................................................................................................... 275
Figure 156. ASAP ATM Layer view................................................................................................... 276
Figure 157. VP Layer Configuration.................................................................................................. 276
Figure 158. Ingress Traffic Description ............................................................................................. 277
Figure 159. VC Layer Configuration ................................................................................................. 279
Figure 160. ASAP ATM PW Layer view ............................................................................................ 281
Figure 161. Core-E Main view .......................................................................................................... 283
Figure 162. Core-E Main view (with optical SFP Ethernet port#5) ................................................... 284
Figure 163. Settings tab-panel .......................................................................................................... 290
Figure 164. Input External Point View............................................................................................... 291
Figure 165. Output External Points View .......................................................................................... 292
Figure 166. Performance Monitoring tool welcome screen............................................................... 293
Figure 167. Tool bar .......................................................................................................................... 294
Figure 168. Ethernet Aggregate Rx Table......................................................................................... 295
Figure 169. Ethernet Aggregate Rx Table display (at port level) ...................................................... 295
Figure 170. Ethernet Aggregate Rx Table display (all enabled ports)............................................... 296
Figure 171. Ethernet Aggregate Tx Table ......................................................................................... 297
Figure 172. Ethernet Aggregate Tx Table display (at port level)....................................................... 298
Figure 173. Ethernet Aggregate Tx Table display (all enabled ports) ............................................... 299
Figure 174. MD300 unit performance screen ................................................................................... 299
Figure 175. Radio sections ............................................................................................................... 300
Figure 176. Current Data Table (15 Min) .......................................................................................... 301
Figure 177. Current Data Table (15 Min) display .............................................................................. 302
Figure 178. Alarm Data Table (15 Min) ............................................................................................. 302
Figure 179. History Data Table (15 Min) ........................................................................................... 304
Figure 180. Threshold creation ......................................................................................................... 305
Figure 181. Threshold change .......................................................................................................... 306
Figure 182. Threshold association.................................................................................................... 307
Figure 183. Adaptive Modulation performances ............................................................................... 308
Figure 184. Current Data Table (15 min) .......................................................................................... 308
Figure 185. History Data Table (15 min) ........................................................................................... 309
Figure 186. Ethernet Aggregate Tx Table ......................................................................................... 310
Figure 187. Ethernet Aggregate Tx Table Performance display ....................................................... 310
Figure 188. Ethernet Aggregate Per Queue ..................................................................................... 312
Figure 189. Ethernet Aggregate Per Queue (Queue #01) ................................................................ 312
Figure 190. Ethernet Aggregate Per Queue (all queues) ................................................................. 313
Figure 191. P32E1DS1 unit performance screen ............................................................................. 314
Figure 200. One-Shot Start/Stop the PM .......................................................................................... 323
Figure 201. Threshold creation ......................................................................................................... 324
Figure 202. Threshold change .......................................................................................................... 325
Figure 203. One-Shot Threshold association (from E1 threshold).................................................... 326
Figure 204. Threshold association (Incoming and Outgoing) ........................................................... 327
Figure 205. Threshold association (Incoming).................................................................................. 328
Figure 206. Threshold association (Outgoing).................................................................................. 328
Figure 207. A16E1DS1 (ASAP) unit performance screen ................................................................ 329
Figure 208. IMA Group Statistics ...................................................................................................... 330

Figure 209. IMA Link Statistics.......................................................................................................... 331
Figure 210. ATM Interface Statistics Monitoring................................................................................ 332
Figure 211. ATM VP Statistics Monitoring ......................................................................................... 333
Figure 212. ATM VC Statistics Monitoring......................................................................................... 333
Figure 213. 802.1D VLAN management........................................................................................... 335
Figure 214. 802.1Q VLAN management (default VLAN only) .......................................................... 336
Figure 215. VLAN Table Management.............................................................................................. 337
Figure 216. 802.1Q VLAN management........................................................................................... 338
Figure 217. Fixing the Rack to Floor (1) ........................................................................................... 341
Figure 218. Fixing the Rack to Floor (2) ........................................................................................... 342
Figure 219. Floor file drilling template............................................................................................... 343
Figure 220. Example of securing rack assembly to computer floor .................................................. 344
Figure 221. Laborack ........................................................................................................................ 345
Figure 222. MSS-8 Subrack.............................................................................................................. 346
Figure 223. MSS-4 Subrack.............................................................................................................. 346
Figure 224. Fixed Subrack with screw .............................................................................................. 347
Figure 225. Subrack grounding point (bracket on the right side) ...................................................... 347
Figure 226. Mechanical Support (Two brackets) .............................................................................. 348
Figure 227. Installation kit to fix the mechanical support .................................................................. 348
Figure 228. MSS 8 Fixed on wall mounting ...................................................................................... 349
Figure 229. Top Rack Unit (T.R.U.) ................................................................................................... 349
Figure 230. Top Rack Unit - Front/Rear ............................................................................................ 349
Figure 231. Top Rack Unit - Fixed to rack......................................................................................... 349
Figure 232. TRU Connections .......................................................................................................... 351
Figure 233. TRU Grounding position on Laborack ........................................................................... 351
Figure 234. ETSI Rack - Ground connection .................................................................................... 352
Figure 235. Laborack - Ground connection ...................................................................................... 352
Figure 236. 2W2C Connector and Cable (3DB18271AAXX)............................................................ 352
Figure 237. Battery Access Card on subrack ................................................................................... 353
Figure 238. ODU (with the internal Lightning Surge Suppressor)..................................................... 354
Figure 239. ODU and Mounting Collar.............................................................................................. 355
Figure 240. Andrew Pole Mount and ODU Mounting Collar ............................................................. 356
Figure 241. RFS Pole Mount and Mounting Collar ........................................................................... 356
Figure 242. Precision Pole Mounting and ODU Mounting Collar...................................................... 356
Figure 243. Andrew ODU Collar and Polarization Rotator................................................................ 357
Figure 244. RFS Rotator ................................................................................................................... 358
Figure 245. ODU orientation for Vertical or Horizontal Polarization .................................................. 358
Figure 246. Remote Mount: front view.............................................................................................. 360
Figure 247. Remote Mount: rear view............................................................................................... 360
Figure 248. Remote Mount with an ODU installed: front view .......................................................... 361
Figure 249. Remote Mount with an ODU installed: rear view ........................................................... 361
Figure 250. Remote Mount with an ODU installed and flexible waveguide ...................................... 362
Figure 251. Remote Mount with the 1+1 coupler installed................................................................ 362
Figure 252. Remote Mount with the 1+1 coupler and one ODU installed......................................... 363
Figure 253. Coupler fitted to Antenna ............................................................................................... 368
Figure 254. Coupler Installation with ODUs ...................................................................................... 368
Figure 255. Coupler Installation with ODUs: Rear View ................................................................... 369
Figure 256. Locations for Cable Grounds ......................................................................................... 372
Figure 257. Cord for AUX management ........................................................................................... 378
Figure 258. SCSI 68 male connector................................................................................................ 379
Figure 259. Protection Panel 32E1 SCSI 68 - 1.0/2.3 75 ohm (Front/Rear) (3DB16104AAAA) ....... 381
Figure 260. Protection Panel RJ45 120 ohm (Front/Rear) (1AF15245ABAA) ................................. 381
Figure 261. Protection Panel 32E1 SCSI 68 - 1.6/5.6 75 ohm (Front) (1AF15243AAAA) ................ 381
Figure 262. Protection Panel 32E1 BNC 75 ohm (Front) (1AF15244AAAA) ................................... 381

Figure 263. Connector support 1.6/5.6 75 ohm Panel 1U (3CC08061AAAA) .................................. 381
Figure 264. Connector support BNC 75 ohm Panel 1U (3CC08061ABAA)...................................... 381
Figure 265. Support 19 Inch modules 120 ohm Panel 3U (3CC07810AAAA).................................. 382
Figure 266. E1 Protection SCSI 68/Sub-D 37 (Front/Rear) (3DB16102AAAA) ................................ 382
Figure 267. Core-E Card................................................................................................................... 383
Figure 268. Radio Access Card ........................................................................................................ 383
Figure 269. 32xE1 PDH Access Card............................................................................................... 383
Figure 270. 16xE1 ATM ASAP Card ................................................................................................. 383
Figure 271. AUX Peripheral Card ..................................................................................................... 383
Figure 272. Installation subrack and 3 cord N/QMA Kit .................................................................... 385
Figure 273. Installation Card ............................................................................................................. 385
Figure 274. Installation Accessory .................................................................................................... 385
Figure 275. Connection Cables ........................................................................................................ 386
Figure 276. Repeater 2x1+0 32E1 (1 PBA PDH) towards customer DDF 120 Ohms 3U................. 388
Figure 277. Repeater 2x1+0 32E1 (1 PBA PDH) towards customer DDF 120 Ohms 3U................. 388
Figure 278. Repeater 2x1+0 32E1 (1 PBA PDH) towards internal DDF 120 Ohms 3U.................... 389
Figure 280. Repeater 2x1+0 32E1 (2 PBA PDH) towards 2xinternal DDF 75 Ohms
BNC 2x1U with cords 3CC52134AAAA (1 SCSI68 to 2 DB37) .................................... 390
Figure 283. Repeater 2x1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms ...................... 392
Figure 286. Repeater 2x1+0 32E1 (2 PBA PDH) towards internal DDF 75 Ohms 1.6/5.6 2U.......... 394
Figure 287. Repeater 2x1+0 32E1 (2 PBA PDH) towards internal DDF 75 Ohms 1.6/5.6 2U.......... 394
Figure 288. Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U ............ 395
Figure 289. Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U ............ 395
Figure 293. Terminal 1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms ........................... 398
Figure 294. Terminal 1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms ........................... 398
Figure 295. Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms BNC 3U .................. 399
Figure 296. Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms BNC 3U .................. 399
Figure 297. Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U......................... 400
Figure 298. Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U......................... 400
Figure 299. Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF
75 Ohms 1.0/2.3 1U...................................................................................................... 401
75 Ohms 1.0/2.3 1U...................................................................................................... 401
75 Ohms RJ45 2U ........................................................................................................ 402
75 Ohms RJ45 2U ........................................................................................................ 402
Figure 303. Terminal 1+1 32E1 Full protected with 2 cords 3CC52157AAAA (2 PBA PDH)
towards internal DDF 120 Ohms 3U ............................................................................. 403
Figure 304. Terminal 1+1 32E1 Full protected with 2 cords 3CC52157AAAA (2 PBA PDH)
towards internal DDF 120 Ohms 3U ............................................................................. 403
Figure 305. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards customer DDF 120 Ohms. 404

Figure 307. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF
75 Ohms 1.0/2.3 1U...................................................................................................... 405
Figure 308. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF
75 Ohms 1.0/2.3 1U...................................................................................................... 405
Figure 309. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 120 Ohms 3U 406
Figure 310. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 120 Ohms 3U 406
Figure 311. Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards 2xinternal DDF
75 Ohms 1.0/2.3 1U...................................................................................................... 407
75 Ohms 1.0/2.3 1U...................................................................................................... 407
75 Ohms 1.0/2.3 1U...................................................................................................... 408
120 Ohms 3U................................................................................................................ 409
120 Ohms 3U................................................................................................................ 409
120 Ohms 3U................................................................................................................ 410
Figure 319. Example of Ethernet port interconnection...................................................................... 412
Figure 320. Example of Synch interconnection ................................................................................ 412
Figure 321. DTE-DCE Interface........................................................................................................ 417
Figure 322. Alarm Polarity ................................................................................................................ 418
Figure 323. Polarity of the alarm....................................................................................................... 419
Figure 324. Checking Feedhead Flange with a Spirit level............................................................... 424
Figure 325. Indicative head-on signal pattern for a parabolic antenna ............................................. 426
Figure 326. Example Tracking Path Signals ..................................................................................... 427
Figure 327. Example Tracking Path Signals on the First Side Lobe................................................. 427
Figure 328. Network Element Overview ........................................................................................... 449
Figure 329. How to Login.................................................................................................................. 450
Figure 330. Provisioning sequence................................................................................................... 452
Figure 331. Enable SFP optical plug-in ............................................................................................ 453
Figure 332. Enable Spare Core-E Card ............................................................................................ 454
Figure 333. Enabling E1 Access Card .............................................................................................. 455
Figure 334. Enabling E1 Access Card on the same row (to implement protected configuration) ..... 456
Figure 335. Enabling E1 Access Card protection ............................................................................. 457
Figure 336. Enabling Modem Card ................................................................................................... 458
Figure 337. Enabling Modem Card on the same row (to implement protected configuration) .......... 459
Figure 338. Enabling Modem Card protection .................................................................................. 460
Figure 339. Enabling ASAP Card ..................................................................................................... 461
Figure 340. Enabling AUX Card........................................................................................................ 462
Figure 341. Enabling Fan Unit .......................................................................................................... 463
Figure 342. Core-E Card Provisioning (Ethernet ports 1-4) .............................................................. 464
Figure 343. Core-E Card Provisioning (Ethernet port 5)................................................................... 465
Figure 344. E1 Access Card Provisioning TDM2TDM ...................................................................... 466
Figure 345. E1 Access Card Provisioning TDM2ETH ...................................................................... 467
Figure 346. Access Card Details ...................................................................................................... 468
Figure 347. Modem Card Provisioning, Presetting Mode (Sheet 1 of 2) .......................................... 469
Figure 348. Modem Card Provisioning, Presetting Mode (Sheet 2 of 2) .......................................... 470
Figure 349. Modem Card Provisioning, Adaptive Modulation Mode (Sheet 1 of 3) .......................... 471
Figure 352. ASAP Card Provisioning................................................................................................ 474

Figure 353. AUX Card Provisioning .................................................................................................. 475
Figure 354. Provisioning Master with Free Run Local Oscillator as Primary Source........................ 477
Figure 355. Provisioning Slave with Radio Port as Primary Source ................................................. 478
Figure 356. Provisioning NTP protocol ............................................................................................. 479
Figure 357. NE Time Provisioning .................................................................................................... 480
Figure 358. Auxiliary Cross Connections menu................................................................................ 482
Figure 359. System Setting............................................................................................................... 483
Figure 360. Local Configuration Provisioning ................................................................................... 484
Figure 361. TMN Ethernet Port Configuration Provisioning .............................................................. 485
Figure 362. Ethernet Port 4 Configuration Provisioning.................................................................... 486
Figure 363. IP Static Routing Provisioning........................................................................................ 487
Figure 364. OSPF Static Routing Provisioning ................................................................................. 488
Figure 365. TCO Main Menu ............................................................................................................ 489
Figure 366. Provisioning Tool Connectivity ....................................................................................... 490
Figure 367. Provisioning Tool Connectivity ....................................................................................... 490
Figure 368. Provisioning Tool Screen (off-line working).................................................................... 491
Figure 369. Provisioning Tool Screen (direct connection to the NE)................................................. 491
Figure 370. Configuration Options Screen........................................................................................ 492
Figure 371. Core-E Configuration (Sheet 1 of 2) .............................................................................. 493
Figure 372. Core-E Configuration (Sheet 2 of 2) .............................................................................. 494
Figure 373. E1 Configuration ............................................................................................................ 495
Figure 374. Radio Provisioning (without Adaptive Modulation) ........................................................ 496
Figure 375. Radio Provisioning (with Adaptive Modulation) ............................................................. 497
Figure 376. Synchronization Configuration (Master) ........................................................................ 498
Figure 377. Synchronization Configuration (Slave) .......................................................................... 499
Figure 378. Cross Connections Configuration (Sheet 1 of 6) ........................................................... 500
Figure 384. 802.1D management ..................................................................................................... 506
Figure 385. 802.1Q management ..................................................................................................... 507
Figure 386. VLAN Management ....................................................................................................... 508
Figure 387. Port VLan configuration ................................................................................................. 509
Figure 388. Network Configuration ................................................................................................... 510
Figure 389. Trusted Managers screen .............................................................................................. 511
Figure 390. Typical Report Panel...................................................................................................... 512
Figure 391. Relative positions of stations A and B ........................................................................... 541
Figure 392. ODU(s) alarm status ...................................................................................................... 546
Figure 393. Transmit power check.................................................................................................... 547
Figure 394. Received power check................................................................................................... 548
Figure 395. Power measurements .................................................................................................... 549
Figure 396. Received power details.................................................................................................. 549
Figure 397. IF Cable loopback.......................................................................................................... 556
Figure 398. Loopback control in the CT............................................................................................ 557
Figure 399. Protection command (Main)........................................................................................... 558
Figure 400. Protection command (Spare) ......................................................................................... 558
Figure 401. Test bench for tributary functionality check .................................................................... 560
Figure 402. Tributary alarm status monitoring .................................................................................. 561
Figure 403. Test bench for hop stability test ..................................................................................... 564
Figure 404. Test bench for optional Ethernet Data Channel functionality with 1
additional PC and 1 Ethernet cable .............................................................................. 566
Figure 405. Test bench for optional Ethernet Data Channel functionality with 2 additional PCs ..... 567

Figure 406. Test bench for optional Ethernet Data Channel functionality with
2 Ethernet Data Analyzers ............................................................................................ 568
Figure 407. Test bench for ATM traffic .............................................................................................. 570
Figure 408. Test bench for 64 kbit/s Service Channel functionality check ........................................ 571

LIST OF TABLES
Table 1. Radio capacity, channelling scheme and modulation (Static Modulation) ........................... 49
Table 2. Radio capacity, channelling scheme and modulation (Adaptive Modulation)...................... 49
Table 3. RSSI Table .......................................................................................................................... 94
Table 4. Waveguide Flange Data ...................................................................................................... 95
Table 5. 802.1p mapping................................................................................................................... 115
Table 6. RR weights .......................................................................................................................... 116
Table 7. PW label EXP bits ............................................................................................................... 116
Table 8. Command priority list........................................................................................................... 240
Table 9. Command priority list........................................................................................................... 241
Table 10. Command priority list......................................................................................................... 243
Table 11. Waveguide Flange Data .................................................................................................... 364
Table 12. Cord for AUX management - Pin function ......................................................................... 378
Table 13. SCSI 68 pins FW cable colors........................................................................................... 379
Table 14. Pin Function: Tributaries 1-16 (32E1 PDH card/16E1 ASAP card) ................................... 413
Table 15. Pin Function: Tributaries 17-32 (32E1 PDH card) ............................................................. 414
Table 16. Service channel 1 pin functions......................................................................................... 416
Table 17. Service channel 2 pin functions......................................................................................... 416
Table 18. Housekeeping connector pin function ............................................................................... 418
Table 19. Alarm Matrix ...................................................................................................................... 516
Table 20. Modem Card Alarm Matrix ................................................................................................ 520
Table 21. Troubleshooting Ethernet Problems ................................................................................. 526
Table 22. TMN Network Troubleshooting ........................................................................................ 527
Table 23. Test and commissioning instruments ................................................................................ 540

List of Tables 3DB 18528 DIAA Issue 1 17/578
18/578 3DB 18528 DIAA 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 27.

Preface 3DB 18528 DIAA Issue 1 19/578
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-E
PRODUCT RELEASE
9500 MPR-E 1.4.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 February 2010

20/578 3DB 18528 DIAA Issue 1 Preface
Change notes
The features of Rel. 1.4.0 have been added:
E1 Node Timing
E1 Loopbacks
New criteria for 1+1 EPS Core Protection
Hybrid management of User Ethernet interfaces (Static LAG)
Synchronous Ethernet
1.024 MHz Sync-In/Synch-Out clock
Backup&Restore
256 QAM 56 MHz Modem Profile
URU Alarm
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
9500 MPR-E HW architecture, and gives its technical characteris-
tics.
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 Craft Terminal for the LineUp and Commission-
ing 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 20.
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 20;
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-Lucent-Information-System as a struc-
tured list.
Whenever a new edition of any of such handbooks/documents is released in the Alcatel-Lucent archive
system, a check in the Alcatel-Lucent-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 18528 DIAA Issue 1 27/578
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

28/578 3DB 18528 DIAA 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.
Compliance boundaries for 9500 MPR-E transceivers with 1ft (30 cm) antenna:

Compliance boundaries
Modulation Worst configuration A (m) B (m)
4 QAM 1+0 with integrated antenna (13 GHz 1 ft. SP integrated antenna) 0,4 2,63
Antenna configurations:
a) 1+0 with 1ft. integrated antenna
b) 1+1 HSB with coupler and 1ft. integrated antenna
c) Configuration with separated 1 ft. 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:
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 40)
Innovative solutions (par. 2.1.1 on page 40)
Description (par. 2.1.2 on page 43)
MSS Purpose, Function and Description (par. 2.1.3 on page 43)
ODU300 (par. 2.1.5 on page 47)
MSS-ODU cable (Interfaces and Traffic) (par. 2.1.6 on page 48)
Antennas (par. 2.1.7 on page 48)
Radio capacity, channelling and modulation (par. 2.2 on page 49)
Standard Features (par. 2.3 on page 50)
Radio Configurations (par. 2.4 on page 51)
System Configurations (par. 2.5 on page 51)
Environmental and Electrical Characteristics (par. 2.6 on page 55)

Outdoor Units (6 to 15 GHz) (par. 2.6.1 on page 55)
Outdoor Units (18 to 38 GHz) (par. 2.6.2 on page 58)
System Parameters (par. 2.6.3 on page 60)
Parts Lists (par. 2.7 on page 64)
Functional description (par. 2.8 on page 81)

MSS (Indoor Unit) (par. 2.8.1 on page 81)
Power distribution (par. 2.8.1.1 on page 82)
ODU300 (par. 2.8.2 on page 92)
Protection schemes (par. 2.8.3 on page 96)
Radio Transmission Features (par. 2.8.4 on page 101)
TMN communication channels (par. 2.8.5 on page 104)
Traffic profiles (par. 2.8.7 on page 109)
Quality Of Services (QoS) (par. 2.8.10 on page 119)
Cross-connection (par. 2.8.11 on page 125)
Synchronization for PDH/DATA (par. 2.8.12 on page 126)

Product information and planning 3DB 18528 DIAA Issue 1 39/578
2.1 Purpose and Function
The 9500 Microwave Packet Radio (MPR) is a microwave digital radio that supports both PDH and packet
data (Ethernet) for migrating from TDM 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 and North American (US and Canada) data rates, frequencies,
channel plans, and tributary interfaces.
TDM/PDH Data Rates: E1
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

40/578 3DB 18528 DIAA Issue 1 Product information and planning
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, 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
9500 MPR-E allows to fully exploit the air bandwidth in its entirety by changing modulation scheme
according to the propagation availability, associating to the different services quality the available
transport capacity.

2.1.2 Description
The 9500 MPR-E consists of a Microwave Service Switch (MSS) and Outdoor Unit (ODU).
Figure 5. Naming Convention
MSS and ODU are connected with a single standard coaxial cable.
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 self 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
FANS
Transport Transport module
module module
Transport
Transport module or AUX
module peripheral
module
Figure 6. MSS-8 shelf
Main Core-E Spare Core-E

module module
FANS
module
Transport
Transport
module or AUX
module
peripheral
module
Figure 7. MSS-4 shelf
The Core-E modules provide five Ethernet user interfaces, the local CT 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
LCT.
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.
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 Radio Interface module: 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, one radio interface module in the MSS and one associated ODU has to be
provisioned in case of 1+0 radio configuration. Two radio interface modules and two associated ODUs
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
TRANSPORT Flash
PSU Controller
MODULE RAM
TRANSPORT
MODULE
TRANSPORT
MODULE
1 GbEth
TRANSPORT
MODULE
ETHERNET
TRANSPORT
SWITCH
MODULE
TRANSPORT
MODULE
LIU LIU
4x10/100/1000 1x1000
Ethernet ports Optical
Ethernet
Figure 8. MSS-8 block diagram

Core-E MODULE
TRANSPORT Flash
PSU Controller
MODULE RAM
TRANSPORT
MODULE
1 GbEth
ETHERNET
SWITCH
LIU LIU
4x10/100/1000 1x1000
Ethernet ports Optical Ethernet
Figure 9. MSS-4 block diagram
2.1.4 Stacking configuration

To manage more than 6 radio directions the Stacking configuration can be realized by installing two
(or more than two) MSS interconnected through the Ethernet ports in the Core-E module, as shown in the
example of Figure 10.
TMN Synch
Shelf 2
Shelf 1
Figure 10. Stacking configuration with 2 MSS
With the Core protection max. 2 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 alarm the Ethernet Interface Criteria for 1+1 EPS Core fea-
ture has to be enabled (refer to Menu System Setting in par. 3.4.4).
TMN
Shelf 2
Ethernet Ethernet TMN
Shelf 1
Figure 11. Stacking configuration 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 ODU consists of cable interface, modulator, 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.
The microprocessor manages ODU frequency, transmit power alarming, and performance monitoring.
Power is provided by -48Vdc from the MSS to the ODU DC-DC converter.
The ODU is frequency dependent.
Figure 12. ODU300

2.1.6 MSS-ODU cable (Interfaces and Traffic)
A single 50 ohm coaxial cable connects a ODU300 Radio Interface to its ODU. The max. cable length
is up to 150 m. ODU cable, connectors and grounding kits are separately provided.
The ODU cable carries DC power (-48 Vdc) 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)
Signal extracting and merging is carried out in N-Plexers within the ODU300 Radio Interface and ODU.
2.1.7 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 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
Channel Modulation Net radio throughput E1 Equivalent Capacity

(TDM2TDM)
4 QAM 10,88 Mbit/s 4 E1
7 MHz 16 QAM 21,76 Mbit/s 8 E1
64 QAM 32,64 Mbit/s 13 E1
4 QAM 21,76 Mbit/s 8 E1
14 MHz 16 QAM 43,52 Mbit/s 18 E1
64 QAM 65,28 Mbit/s 27 E1
4 QAM 43,52 Mbit/s 18 E1
16 QAM 87,04 Mbit/s 37 E1
32 QAM 111,36 Mbit/s 48 E1

28 MHz
64 QAM 130,56 Mbit/s 56 E1
128 QAM 156,80 Mbit/s 68 E1
256 QAM 177,60 Mbit/s 77 E1
16 QAM 166,40 Mbit/s 72 E1
56 MHz 128 QAM 313,60 Mbit/s 136 E1
256 QAM 344,198 Mbit/s 150 E1
Table 1. Radio capacity, channelling scheme and modulation (Static Modulation)
Channel Spacing Modulation Net radio throughput Equivalent capacity E1 (Note)
4 QAM 43,52 Mbit/s 18 E1
28 MHz 16 QAM 87,04 Mbit/s 37 E1
64 QAM 130,56 Mbit/s 56 E1
4 QAM 21,76 Mbit/s 8 E1
14 MHz 16 QAM 43,52 Mbit/s 18 E1
64 QAM 65,28 Mbit/s 27 E1
4 QAM 10,88 Mbit/s 4 E1
64 QAM 32,64 Mbit/s 13 E1
Table 2. Radio capacity, channelling scheme and modulation (Adaptive Modulation)

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.3 Main 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 six outdoor units
Universal ODU that is capacity and modulation independent
Flexible aggregate capacity sharing between E1 and Ethernet
Adaptive packet transport that improves performance for priority services
Output power agility
ATPC
Adaptive Modulation
Packet-based internal cross-connect
TDM MEF8 encapsulation
Electrical and optical GE interfaces
Software-based configuration
Multiservice Switching Capacity greater than 10Gb/s
Radio throughput greater than 2Gb/s
Termination of 192xE1 in circuit emulation
Two 64 kbit/s service channels
Housekeeping alarms (6 inputs/7 outputs)
No single point of failure

2.4 Radio Configurations
1+0
1+1 Hot-Standby (HSB) (two types of coupler: 3 dB/3 dB balanced coupler or 1 dB/6 dB unbalanced
coupler)
1+1 Hot-Standby Space Diversity (HSB SD) (no combiner)
1+1/2x(1+0) Frequency Diversity (FD) (homo-polar)
1+1/2x(1+0) Frequency Diversity (FD) (hetero-polar)
2.5 Typical System Configurations

TDM/ATM Over Ethernet Packet Node - Mapping of 32 E1 TDM and 16 E1 ATM on Ethernet (Figure
13.)
TDM/ATM and Ethernet Terminal Packet Transport - 32 E1 TDM and 16 E1 ATM Access, 1 Radio
Direction (Figure 14.)
TDM/ATM and Ethernet Add/Drop N1 Packet Node - Ethernet and 32 E1 TDM and 16 E1 ATM Local
Access, 1 Back Link, 1 Haul Link (Figure 15.)
TDM/ATM and Ethernet Terminal Packet Node-Ethernet and 32 E1 TDM and 16 E1 ATM Local
Access, 2 Back Links (Figure 16.)
TDM/ATM and Ethernet Add/Drop Packet Node-Ethernet and 32 E1 TDM and 16 E1 ATM Local
Access, 2 Haul Links and 1 back Link (Figure 17.)
TDM/ATM and Ethernet Add/Drop NN Packet Node - Ethernet and 32 E1 TDM and 16 E1 ATM Local
Access, 2 Haul Links and 2 back Links (Figure 18.)

Figure 13. TDM/ATM Over Ethernet Packet Node - Mapping of 32 E1 TDM and 16 E1 ATM on Ether-
net
Figure 14. TDM/ATM and Ethernet Terminal Packet Transport 32 E1 TDM and 16 E1 ATM Access,
1 Radio Direction
Figure 15. TDM/ATM and Ethernet Add/Drop N1 Packed Node-Ethernet and 32 E1 TDM and 16 E1
ATM Local Access, 1 Back Link, 1 Haul Link

Figure 16. TDM/ATM and Ethernet Terminal Packet Node-Ethernet and 32 E1 TDM and 16 E1 ATM
Local Access, 2 Back Links
Figure 17. TDM/ATM and Ethernet Add/Drop Packet Node-Ethernet and 32 E1 TDM and 16 E1 ATM
Local Access, 1 back Link and 2 Haul Links

Figure 18. TDM/ATM and Ethernet Add/Drop NN Packet Node-ethernet and 32 E1 TDM and 16 E1
ATM Local Access, 2 Haul Links and 2 Back Links

2.6 Environmental & Electrical Characteristics
Outdoor Units (6 to 15 GHz) (par. 2.6.1)
Outdoor Units (18 to 38 GHz) (par. 2.6.2)
System Parameters (par. 2.6.3)
2.6.1 Outdoor Units (6 to 15 GHz)
L6/U6 7 GHz 8 GHz 10 GHz 11 GHz 13 GHz 15 GHz

GHz
System
Frequency 5.925 - 7.125 - 7.725 - 10.0 - 10.7 - 12.75 - 14.4 -

Range, GHz 6.425 7.9 8.5 10.68 11.7 13.25 15.35
6.425 -
7.11
T-R Spacings 252.04 154, 119, 126, 91, 230, 490, 530 266 315,
supported MHz 340 161, 151.614, 143.5, 420,
168, 266, 350 490,
196, 245 311.32 644, 728
Maximum Tuning 56 56 140 165 165 84 245

Range
(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 PDR70 or PDR84 PDR84 PDR100 PDR100 PBR120 PBR140

Type CDR70 or or or or or or
CDR84 CDR84 CDR100 CDR100 CDR120 CBR140

GHz
System Gain [1]
System Gain at 7 MHz QPSK 121,0 dB 121,0 dB 121,0 dB 118,0 dB 116,0 dB 115,0 dB 114,0 dB
10-6 BER
16 QAM 112,0 dB 112,0 dB 112,0 dB 109,0 dB 107,5 dB 106,5 dB 105,0 dB
13.75 / QPSK 118,0 dB 118,0 dB 118,0 dB 115,0 dB 113,5 dB 112,5 dB 111,0 dB

14 MHz
27.5 / 28 QPSK 115,5 dB 115,5 dB 115,5 dB 112,5 dB 111,0 dB 110,0 dB 108,5 dB

MHz
55 / 56 16QAM 105,0 dB 105,0 dB 105,0 dB 102,0 dB 100,0 dB 99,0 dB 97,5 dB

MHz

GHz
Transmitter
Specifications
Power Output, QPSK 28,5 dBm 28,5 dBm 28,5 dBm 26,0 dBm 24,0 dBm 23,0 dBm 22,0 dBm
nominal
16 QAM 26,5 dBm 26,5 dBm 26,5 dBm 24,0 dBm 22,0 dBm 21,0 dBm 20,0 dBm
64 25,5 dBm 25,5 dBm 25,5 dBm 23,0 dBm 21,0 dBm 20,0 dBm 19,0 dBm
QAM[2]
Receiver
Specifications
[1]
Threshold at 10-6 7 MHz QPSK -92,5 dBm -92,5 dBm -92,5 dBm -92,0 dBm -92,0 dBm -92,0 dBm -92,0 dBm
BER
16 QAM -85,5 dBm -85,5 dBm -85,5 dBm -85,0 dBm -85,5 dBm -85,5 dBm -85,0 dBm
13.75 / QPSK -89,5 dBm -89,5 dBm -89,5 dBm -89,0 dBm -89,5 dBm -89,5 dBm -89,0 dBm
14
MHz 16 QAM -83,5 dBm -83,5 dBm -83,5 dBm -83,0 dBm -83,0 dBm -83,0 dBm -82,5 dBm
27.5 / QPSK -87,0 dBm -87,0 dBm -87,0 dBm -86,5 dBm -87,0 dBm -87,0 dBm -86,5 dBm
28
MHz 16 QAM -81,0 dBm -81,0 dBm -81,0 dBm -80,5 dBm -80,5 dBm -80,5 dBm -80,0 dBm
55 / 56 16 QAM -78,5 dBm -78,5 dBm -78,5 dBm -78,0 dBm -78,0 dBm -78,0 dBm -77,5 dBm
MHz
Guaranteed power consumption 45 W
All specifications are referenced to the ODU antenna flange, and are typical values unless otherwise
stated, and are subject to change without notice.
For Guaranteed values (over time and operational range) subtract 2 dB from Power Output, add 2 dB to
Threshold values, and subtract 4 dB from System Gain values.
[1] System Gain and Rx Threshold values are for BER=10-6. Values for BER=10-3 are improved by 1 dB.
[2] 10 GHz Power Output and System Gain specifications are reduced by 1.5 dB and 3 dB respectively
for 91 MHz T-R option.

2.6.2 Outdoor Units (18 to 38 GHz)
18 GHz 23 GHz 26 GHz 28 GHz 32 GHz 38 GHz
System
Frequency Range, 17.7 - 19.7 21.2 - 24.52 - 27.5 - 29.5 31.8-33.4 37.0 -
GHz 23.632 26.483 39.46
T-R Spacings 1010, 1008, 1008 1008 812 1260

supported MHz 1092.5 1200,
1232
Maximum Tuning 380 370 360 360 370 340

Range (dependent
upon 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
System Gain [1]
System Gain at 7 MHz QPSK 111,0 dB 110,5 dB 106,5 dB 106,0 dB 109,0 dB 108,0 dB
10-6 BER
16 QAM 102,5 dB 102,0 dB 97,0 dB 97,0 dB 99,5 dB 98,5 dB
13.75 / QPSK 108,5 dB 108,0 dB 103,0 dB 103,0 dB 105,5 dB 104,5 dB

14 MHz
27.5 / 28 QPSK 106,0 dB 105,0 dB 100,0 dB 100,0 dB 102,5 dB 101,5 dB

MHz
55 / 56 16QAM 95,0 dB 94,0 dB 89,0 dB 88,5 dB 91,0 dB 90,0 dB

MHz

18 GHz 23 GHz 26 GHz 28 GHz 32 GHz 38 GHz
Transmitter
Specifications
Power Output, QPSK 19,5 dBm 19,5 dBm 15,5 dBm 15,0 dBm 18,0 dBm 17,5 dBm
nominal
16 QAM 17,5 dBm 17,5 dBm 13,5 dBm 13,0 dBm 16,0 dBm 15,5 dBm
64 16,5 dBm 16,5 dBm 12,5 dBm 12,0 dBm 15,0 dBm 14,5 dBm
QAM[2]
Receiver
Specifications [1]
Threshold at 10-6 7 MHz QPSK -91,5 dBm -91,0 dBm -91,0 dBm -91,0 dBm -91,0 dBm -90,5 dBm
BER
16 QAM -85,0 dBm -84,5 dBm -83,5 dBm -84,0 dBm -83,5 dBm -83,0 dBm
13.75 / QPSK -89,0 dBm -88,5 dBm -87,5 dBm -88,0 dBm -87,5 dBm -87,0 dBm
14 MHz
27.5 / 28 QPSK -86,5 dBm -85,5 dBm -84,5 dBm -85,0 dBm -84,5 dBm -84,0 dBm
MHz
55 / 56 16 QAM -77,5 dBm -76,5 dBm -75,5 dBm -75,5 dBm -75,0 dBm -74,5 dBm
MHz
Guaranteed power consumption 30 W
All specifications are referenced to the ODU antenna flange, and are typical values unless otherwise
stated, and are subject to change without notice.
For Guaranteed values (over time and operational range) subtract 2 dB from Power Output, add 2 dB to
Threshold values, and subtract 4 dB from System Gain values.
[1] System Gain and Rx Threshold values are for BER=10-6. Values for BER=10-3 are improved by 1 dB.
[2] 10 GHz Power Output and System Gain specifications are reduced by 1.5 dB and 3 dB respectively
for 91 MHz T-R option.

2.6.3 System Parameters
General
Operating Frequency Range 6 - 38 GHz
Capacity Range Options (E1) 18x, 37x, 48x, 68x, 136x E1
Capacity Range Options (Ethernet) 40, 80, 100, 150, 300 Mbit/s
Modulation Options with Static Modulation 4 QAM, 16 QAM, 32 QAM,

64 QAM, 128 QAM, 256 QAM
Adaptive Modulation 4 QAM, 16 QAM, 64 QAM
Error Correction FEC, Reed Solomon Decoding
Error Correction 24 tap T/2 equalizer
Radio Path Protection Options
Non Protected, 1+0
Protected Hot Standby, 1+1
Space Diversity, 1+1
Frequency Diversity, 1+1/2x(1+0)
Standards Compliance
EMC MSS EN 301 489-1, EN 301 489-4

EN 55022 Class B)
Operation ODU300 ETS 300 019, Class 4.1
Operation MSS 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 IEC 60529 (IPX6)
Environmental
Operating Temperature MSS Guaranteed -5 C to +55 C
MSS Extended -40 C to +65 C

(with cold start at -20C)
ODU300 Guaranteed -33 C to +55 C
Humidity MSS Guaranteed 0 to 95%, non-condensing
ODU300 Guaranteed 0 to 100%
Fault and Configuration Management
Protocol SNMP
Interface, electrical Ethernet 10/100/1000 Base-T

Interface, electrical physical RJ-45
Local/remote Configuration and Support JUSM

Tool
Routing Protocols supported Static and dynamic routing, OSPF
Network Management Alcatel-Lucent 1350 OMS

Alcatel-Lucent 1352 Compact
Alcatel-Lucent 5620 SAM
Options with the AUX peripheral unit
64 kbit/s service channels 2 (synchronous RS422/V.11 DCE

co-directional)
Housekeeping alarms 6 inputs/7 outputs
2.6.4 RTPC (Manual Transmit Power Control)
6GHz 7GHz 8GHz 10.5GHz 11GHz 13GHz 15GHz
Reference
Channel QAM RTPC RTPC RTPC RTPC RTPC RTPC RTPC
Spacing
min max min max min max min max min max min max min max
(MHz)
dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm
7 4 8,5 28,5 8,5 28,5 6 26 3 23 2 22
16 8,5 26,5 8,5 26,5 7 24 5 21 4 20
64 8,5 25,5 8,5 25,5 7 23 5 20 4 19
14 4 8,5 28,5 8,5 28,5 6 26 3 23 2 22
16 10 26,5 10 26,5 10 24 8 21 7 20
64 10 25,5 10 25,5 10 23 8 20 7 19
28 4 8,5 28,5 8,5 28,5 8,5 28,5 6 26 3 23 2 22
16 13 26,5 13 26,5 13 26,5 13 24 11 21 10 20
32 13 26 13 26 13 26 13 23,5 11 20,5 7 19,5
64 13 25,5 13 25,5 13 25,5 13 23 14 21 11 20 10 19
128 13 24,5 13 24,5 13 24,5 13 22 13 20 11 19 10 18
256 13 22,5 13 22,5 13 22,5 13 20 13 18 11 17 10 16

6GHz 7GHz 8GHz 10.5GHz 11GHz 13GHz 15GHz
56 16
128 15,5 24,5 15,5 24,5 16 22 14 19 13 18
256 15,5 24,5 15,5 24,5 16 22 14 19 13 18
18GHz 23GHz 26GHz 28GHz 32GHz 38GHz
Reference
Channel QAM RTPC RTPC RTPC RTPC RTPC RTPC
Spacing
min max min max min max min max min max min max
(MHz)
dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm
7 4 -0,5 19,5 -0,5 19,5 -4,5 15,5 -5 15 -2 18 0 17,5
16 2 17,5 -0,5 17,5 -4,5 13,5 -5 13 -2 16 0 15,5
64 -0,5 16,5
14 4 -0,5 19,5 -0,5 19,5 -4,5 15,5 -5 15 -2 18 0 17,5
16 5 17,5 0 17,5 -4 13,5 -5 13 -2 16 0 15,5
64 -0,5 16,5 0 16,5 -4 12,5 -5 12 -2 15 0 14,5
28 4 -0,5 19,5 -0,5 19,5 -4,5 15,5 -5 15 -2 18 0 17,5
16 8 17,5 3,5 17,5 -1 13,5 -2 13 -2 16 0 15,5
32 3,5 17 3,5 17 -1 13 -2 12,5 -2 15,5 0 15
64 3,5 16,5 3,5 16,5 -1 12,5 -2 12 -2 15 0 14,5
128 3,5 15,5 3,5 15,5 -1 11,5 -2 11 -2 14 0 13,5
256 3,5 13,5 3,5 13,5 -1 9,5 -2 9 -2 12 0 11,5
56 16 6 17,5 6 17,5 1,5 13,5 1 13 -1,5 16 1 15,5
128 6,5 15,5 6,5 15,5 2 11,5 1 11 -1 14 1 13,5
256 6,5 15,5 6,5 15,5 2 11,5 1 11 -1 14 1 13,5

2.6.5 Minimizing Latency Latency contribution for a 9500 MPR-E Cloud
2.6.5.1 E1 to E1 Single Hop - TDM2TDM (Static Modulation)
TDM2TDM Delay [ms]

Mod Chan Min Typ Max
4QAM 7MHz 3,0 3,5 3,8
4QAM 14MHz 3,3 3,5 3,8
4QAM 28MHz 3,1 3,3 3,5
16QAM 7MHz 2,8 3,4 3,7
16QAM 14MHz 2,9
16QAM 28MHz 2,7
32QAM 28MHz 2,9
64QAM 7MHz 3,1 3,6 3,9
64QAM 14MHz 3,2 3,5 3,7
64QAM 28MHz 2,9 3,3 3,5
128QAM 28MHz 2,8
128QAM 56MHz 2,6 3,1
256QAM 56MHz 2,6 3,1
2.6.5.2 Ethernet to Ethernet Single Hop (Static Modulation)
Ethernet Ethernet Ethernet

Delay Delay Delay
[ms] [ms] [ms]
Modem Profile ETH P2P Modem Profile ETH P2P Modem Profile ETH P2P
Frame Frame Frame
4QAM 7MHz 64 1,697 4QAM 7MHz 512 2,062 4QAM 7MHz 1024 2,495

2.7 Parts Lists
2.7.1 MSS
APR Name APR Code Remarks
Core-E Card 3DB18326ABXX
MSS-8 slot shelf 3DB18485AAXX
MSS-4 slot shelf 3DB18219ABXX
Fan Card 3DB18134BAXX To be used in MSS-8
FAN1 Module 3DB18218ACXX To be used in MSS-4
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 be used with 56 MHz bandwidth (no adaptive

modulation)
3DB18136ADXX
Modem 300EN 3DB18538AAXX To be used with bandwidth up to 28 MHz (with

ot without adaptive modulation)
3DB18538ABXX
Front plate 3DB18163ABXX
SPF plug-in 1000Base-Lx 1AB187280040 To be installed in the Core-E card
SPF plug-in 1000Base-Sx 1AB187280045 To be installed in the Core-E card
SFP 1000 SX 1AB383760001 To be installed in the Core-E card
APR name License String APR Code
Flash Cards 1.3.1 (Note)
MPR Memory L6TD-131 R/6Cap040 3DB18283AFAA
MPR Memory M1TD-131 R/5Cap040/1Cap080 3DB18284AEAA
MPR Memory M2TD-131 R/4Cap040/2Cap080 3DB18285AEAA
MPR Memory M6TD-131 R/6Cap080 3DB18501AEAA
MPR Memory H1TD-131 R/5Cap040/1Cap100 3DB18286AEAA
MPR Memory H2TD-131 R/4Cap040/2Cap100 3DB18287AEAA
MPR Memory H6TD-131 R/6Cap100 3DB18502AEAA
MPR Memory V1TD-131 R/5Cap040/1Cap150 3DB18288AEAA

MPR Memory V2TD-131 R/4Cap040/2Cap150 3DB18289AEAA
MPR Memory V6TD-131 R/6Cap150 3DB18489AEAA
MPR Memory E1TD-131 R/5Cap040/1Cap300 3DB18290AEAA
MPR Memory E2TD-131 R/4Cap040/2Cap300 3DB18291AEAA
MPR Memory E6TD-131 R/6Cap300 3DB18490AEAA
MPR Memory L6SA-131 R/6Cap040/TDM2Eth/ATM2Eth 3DB18283BEAA
MPR Memory M1SA-131 R/5Cap040/1Cap080/TDM2Eth/ATM2Eth 3DB18284BEAA
MPR Memory M2SA-131 R/4Cap040/2Cap080/TDM2Eth/ATM2Eth 3DB18285BEAA
MPR Memory M6SA-131 R/6Cap080/TDM2Eth/ATM2Eth 3DB18501BEAA
MPR Memory H1SA-131 R/5Cap040/1Cap100/TDM2Eth/ATM2Eth 3DB18286BEAA
MPR Memory H2SA-131 R/4Cap040/2Cap100/TDM2Eth/ATM2Eth 3DB18287BEAA
MPR Memory H6SA-131 R/6Cap100/TDM2Eth/ATM2Eth 3DB18502BEAA
MPR Memory V1SA-131 R/5Cap040/1Cap150/TDM2Eth/ATM2Eth 3DB18288BEAA
MPR Memory V2SA-131 R/4Cap040/2Cap150/TDM2Eth/ATM2Eth 3DB18289BEAA
MPR Memory V6SA-131 R/6Cap150/TDM2Eth/ATM2Eth 3DB18489BEAA
MPR Memory E1SA-131 R/5Cap040/1Cap300/TDM2Eth/ATM2Eth 3DB18290BEAA
MPR Memory E2SA-131 R/4Cap040/2Cap300/TDM2Eth/ATM2Eth 3DB18291BEAA
MPR Memory E6SA-131 R/6Cap300/TDM2Eth/ATM2Eth 3DB18273BEAA
MPR Memory I1TD-131 R/5Cap040/1Cap060 3DB18579AEAA
MPR Memory I2TD-131 R/4Cap040/2Cap060 3DB18580AEAA
MPR Memory I6TD-131 R/6Cap060 3DB18581AEAA
MPR Memory I1SA-131 R/5Cap040/1Cap060/TDM2Eth/ATM2Eth 3DB18582AEAA
MPR Memory I2SA-131 R/4Cap040/2Cap060/TDM2Eth/ATM2Eth 3DB18583AEAA
MPR Memory I6SA-131 R/6Cap060/TDM2Eth/ATM2Eth 3DB18584AEAA
MPR Memory A1TD-131 R/5Cap040/1Cap130 3DB18585AEAA
MPR Memory A2TD-131 R/4Cap040/2Cap130 3DB18586AEAA
MPR Memory A6TD-131 R/6Cap130 3DB18587AEAA
MPR Memory A1SA-131 R/5Cap040/1Cap130/TDM2Eth/ATM2Eth 3DB18588AEAA
MPR Memory A2SA-131 R/4Cap040/2Cap130/TDM2Eth/ATM2Eth 3DB18589AEAA
MPR Memory A6SA-131 R/6Cap130/TDM2Eth/ATM2Eth 3DB18590AEAA
MPR Memory A1TD-131A R/5Cap040/1Cap130/6modAdp 3DB18591AEAA
MPR Memory A2TD-131A R/4Cap040/2Cap130/6modAdp 3DB18592AEAA
MPR Memory A6TD-131A R/6Cap130/6modAdp 3DB18593AEAA
MPR Memory A1SA-131A R/5Cap040/1Cap130/TDM2Eth/ATM2Eth/6modAdp 3DB18594AEAA

MPR Memory A2SA-131A R/4Cap040/2Cap130/TDM2Eth/ATM2Eth/6modAdp 3DB18595AEAA
MPR Memory A6SA-131A R/6Cap130/TDM2Eth/ATM2Eth/6modAdp 3DB18596AEAA
MPR Memory L6TD-131A R/6Cap040/6modAdp 3DB18562AEAA
MPR Memory M2TD-131A R/4Cap040/2Cap080/6modAdp 3DB18563AEAA
MPR Memory M6TD-131A R/6Cap080/6modAdp 3DB18564AEAA
MPR Memory V1TD-131A R/5Cap040/1Cap150/6modAdp 3DB18565AEAA
MPR Memory L6SA-131A R/6Cap040/TDM2Eth/ATM2Eth/6modAdp 3DB18566AEAA
MPR Memory M2SA-131A R/4Cap040/2Cap080/TDM2Eth/ATM2Eth/6modAdp 3DB18567AEAA
MPR Memory M6SA-131A R/6Cap080/TDM2Eth/ATM2Eth/6modAdp 3DB18569AEAA
MPR Memory V1SA-131A R/5Cap040/1Cap150/TDM2Eth/ATM2Eth/6modAdp 3DB18568AEAA
MPR Memory W6SA-131 R/6Cap150/6Cap175/TDM2Eth 3DB18640AEAA
MPR Memory W6TD-131 R/6Cap150/6Cap175 3DB18641AEAA
SW 1.4.0
SWP 9500 MPR-E 1.4.0 Packet Operating System 3DB18555AIAA
SWP 9500 MPR-E 1.4.0 Hybrid Operating System 3DB18554AIAA
MPR-E 1.4.0 & TCO 3.4.0 User Manual CD ROM EN 3DB18497AIAA
TCO SW Suite Rel 3.4.0 3DB18557AIAA
9500 MPR-E 1.4 SNMP 3DB18556ADAA
Note: For Rel. 1.4.0 the Flash Cards of Rel. 1.3.1 are used.

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

(MHz) Range
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
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

(MHz) Range
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
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

(MHz) Range
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-


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

(MHz) Range
HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX High
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

(MHz) Range
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
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


(MHz) Range

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
10645-10655 ODU 300, 10GHz, T-R 0065MHz, 10645-10655MHz,

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-


(MHz) Range
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-

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-


(MHz) Range
HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH

HP, TX LOW

HP, TX HIGH

HP, TX LOW

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

(MHz) Range
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-

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

(MHz) Range
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,

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-


(MHz) Range

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-

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

(MHz) Range
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.8 Functional description
2.8.1 MSS (Indoor Unit)

The MSS incorporates the baseband processing/modem functionalities and 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 shelf)
1 or 2 Core-E Modules (Working & Spare)
up to 6 Transport Modules
1 AUX peripheral unit (option)
1 Fans unit
The MSS-4 is made of:
1 subrack (MSS shelf)
1 or 2 Core-E Modules (Working & Spare)
up to 2 Transport Modules
1 AUX peripheral unit (option)
1 Fans unit
There are three types of Transport Modules:
32xE1 Local Access Module
16xE1 ATM Local Access - ASAP Module
ODU300 Radio Module.
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 receives the Battery input via the Backplane.
The input voltage range is from -40.5 to -57.6 Vdc.
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.
Each ODU 300 Radio Module unit provides a -48V to supply the ODU.
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
9500 MPR-E
RADIO
ODU 300
RADIO
BACK PLANE
Figure 19. Power Distribution Architecture

2.8.1.2 Core-E unit
Figure 20. Core-E unit
Based on packet technology with 8 GbEth serial internal interfaces between Core-E and
peripherals (jumbo frames 9728 bytes allowed)
4x10/100/1000 Eth embedded interface (RJ45)
1x1000 base-Lx or Sx (SFP optical interference), available with an optical plug-in.
Macro 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 a 1000 optical intrerface in the SFP slot.
Two modules are available:
1000BASE-LX
1000BASE-SX
The flash card stores the licence type, the equipment software, the equipment MIB and the equipment
MAC address.

Figure 21. Core-E unit
Warning: The optional SFP plug-in, which has to be installed in the Core-E unit, contains a Class 1 laser
source. 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.
2.8.1.3 32xE1 Local Access unit
wk core
FPGA
32 E1 sp core
LIUs (Ceres) CES
wk core
sp core
Figure 22. 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. The spare Core-E in not implemented.
E1 E1
17-32 1-16
Figure 23. PDH Access unit
2.8.1.4 ASAP unit
The ASAP unit is used to transport 16xE1 ATM traffic, with E1/IM! 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-
toEdgeeEmulation, 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 8 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 24 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 tail
than are available 3 different radio tails
VPC mode
It is possible to transport max 24 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.
Interfaces
16 E1 G.704 - SCSI Connectors
75 ohm or 120 ohm (at NE level)
Block Diagram
(Refer to Figure 24. on page 87).
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 24. ASAP simplified block diagram

Figure 25. ASAP unit
2.8.1.5 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 26. 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 MXC Out Door Unit
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 27. Modem unit

2.8.1.6 AUX peripheral unit
2.8.1.6.1 Overview
Service Channels access and Housekeeping alarms are available with the optional Auxiliary peripheral
unit.
Only one Auxiliary peripheral can be equipped. It can be installed in Slot 8 of MSS-8 or Slot 4 of MSS-4.
The Auxiliary peripheral unit on front panel is equipped with four connectors:
one connector to manage the Service Channel 1

one connector to manage the Service Channel 2
one connector to manage the housekeeping alarms
one connector for EOW (not used in the current release)
Figure 28. AUX peripheral unit block diagram
2.8.1.6.2 Service Channels
By CT/NMS the user can enable/disable the 64 kbit/s Service Channel interfaces. By default they are dis-
abled.
When enabled, the Service Channel interface 1 can be configured to transport the following protocol:
1) Synchronous 64 Kb/s RS422/V.11 DCE co-directional

When enabled, the Service Channel interface 2 can be configured to transport the following protocol:
1) Synchronous 64 Kb/s RS422/V.11 DCE co-directional
Radio Service Channels
On each radio direction three 64 kbit/s out-of-band channels are dedicated to the transmission of the Ser-
vice Channels.
2.8.1.6.3 Alarm-Housekeeping
13 Alarm-Housekeeping pins are provided: 6 pins are configured as inputs and 7 pins are configured as
outputs.
Input alarms
The polarity of each input Alarm-Housekeeping is configurable. The state of each alarm input is config-
urable in order to be active, if the voltage on the input is high (open contact) or if the voltage is low (closed
contact). This second option is the default value.
It is possible to assign one user label for each input.
Output alarms
By default the presence of active alarm corresponds to closed relay contact with a common wire available
to the customer. By CT/NMS the polarity can be changed independently for each alarm (both normally
closed and normally open contacts are available on the I/O connector).
When the power supply is down (and also when the power supply is on but the SW has not yet initialized
the HW), all the relays of the outputs of the alarms/housekeeping are in the "open" state (HW default con-
dition).
The Output Housekeeping can be managed in Manual mode only: in Manual mode the output state of
each housekeeping is controlled by the operator.
Note: the Automatic mode is not supported in this release.
It is possible to assign one user label for each output.
Figure 29. AUX peripheral unit

2.8.2 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.
Equal loss is nominally 3 dB/3 dB. Unequal loss is nominally 1 dB/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
Pressed aluminium cover
Base and cover passivated and then polyester powder coated
Compression seal for base-cover weatherproofing
Carry-handle
Figure 30. 9500 MPR-E ODU 300 housing
ODUs are frequency-band specific, but within each band are capacity-independent up to their design
maximums.

2.8.2.1 ODU block diagram
Figure 31.shows the ODU block diagram.
MSS
Figure 31. 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.2.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.
The RSSI figures in dBm are identical to the RSL figures displayed in A9500 MXC Craft Terminal.
Table 3. 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.2.3 Waveguide Flange Data
Table 4. lists the antenna port flange types used with the ODU 300, 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 4. Waveguide Flange Data

Freq Radio Waveguide Waveguide Spring Bolts Bolt Thread Hole Bolt Length
Band Flange Mating Type Washers Reqd Type Spec Depth Required
Flange Reqd mm
6 GHz UDR70 PDR70 WR137 8 x M5 8 M5x0.8 6H 10 Flange thickness +
Hole depth - 2mm
7/8 GHz UDR84 PDR84 WR112 8 x M4 8 M4x0.7 6H 8 Flange thickness +
Hole depth - 2mm
10/11 GHz UDR100 PDR100 WR90 8 x M4 8 M4x0.7 6H 8 Flange thickness +
Hole depth - 2mm
13 GHz UBR120 PBR120 WR75 4 x M4 4 M4x0.7 6H 8 Flange thickness +
Hole depth - 2mm
15 GHz UBR140 PBR140 WR62 4 x M4 4 M4x0.7 6H 8 Flange thickness +
Hole depth - 2mm
18/23/26 UBR220 PBR220 WR42 4 x M3 4 M3x0.5 6H 6 Flange thickness +
GHz Hole depth - 2mm
28/32/38 UBR320 PBR320 WR28 4 x M3 4 M3x0.5 6H 6 Flange thickness +
2.8.2.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 dB on the main path/6 dB on
the secondary path).
The couplers are connected between the cabinets and the antenna.

2.8.3 Protection schemes
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 (Hot StandBy)

Spare ODU module is powered off.
2 3
2 1
Legend:
1 RPS 2 EPS 3 HSB
Figure 32. 9500 MPR-E Packet Node Full Protection (Radio)
2
Legend: 2 EPS
Figure 33. 9500 MPR-E Packet Node Full Protection (Radio)

[4] Core-E protection
The logic of this protection is distributed in each access and radio peripheral unit. All the switch-
ing 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 Ether-
net 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 5 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 rel-
evant 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 inter-
face protection 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 sup-
ported.
Core protection restoration mode
The restoration mode is always revertive: the Core main becomes active as soon as it has
recovered from failure or when a switch command is released.

Figure 34. Core-E protection (PDH unit - 1+0)
Figure 35. Core-E protection (PDH unit - 1+1)

Figure 36. Core-E protection (Radio unit - 1+0)
Figure 37. Core-E protection (Radio unit - 1+1)
2.8.3.1 RPS Switching Criteria
The switching criteria are:
Early Warning
High BER
Dem Fail
Loss of Frame (LOF) on the radio signal coming from the direct way
Loss of Frame (LOF) on the radio signal coming from the cross way

2.8.3.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.3.3 HSB Switching Criteria
The switching criteria are :
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)
Degradation of the Rx RF field (only with the Adaptive Modulation enabled).
2.8.3.4 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 Interface Criteria for 1+1 EPS Core 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.4 Radio Transmission Features
2.8.4.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.4.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.4.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.4.4 Power Monitoring
The ODU 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 ODU for a given modulation. When
modulation is changed, the CT automatically adjusts/restricts Tx Power to be within valid range.

2.8.4.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.4.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.4.7 MSS loopbacks
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 loopback supported by the Radio board is shown in the following figure.
PDH board RADIO board
LIU FPGA CORE MODEM

FPGA
NxE1 SWITCH
1 3
2
Figure 38. Available loopbacks
1) Line PDH tributaries loopback (external loopback): realized by means the LIU, the traffic
received from the line side is redirect toward the line; this loopback can be enabled on the single
E1.
2) Radio PDH tributaries loopback ( internal loopback): realized by means the FPGA, the traffic
received from the switch side is redirect toward the switch itself; this loopback can be enabled
on the single E1.
3) IF Radio loopback: is implemented in the analog IF part of the ODU 300 Radio Module, the traf-
fic 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 expected 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.
Data flows: simply are redirect toward the switch without any change
2.8.4.7.1 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 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.4.7.2 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.
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.5 TMN communication channels
On 9500 MPR-E Network Element three types of TMN communication channels 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 LCT);
TMN channel carried up to 512 kbit/s channel inside Radio frame;
TMN channel carried by Ethernet frames in Ethernet tributary 4 (on the front panel of the Core-E
module).
2.8.6 Admission control
2.8.6.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 Craft Terminal (CT), it is possible to decide to enable or
not the admission control check (default value is Enabled).
2.8.6.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.6.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 CT level has been inserted, avoiding a possible mistake from the user to pro-
vision 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 39., Figure 40. and Figure 41. here below show how the system operates, in case of modulation
changes when admission control is enabled (case of 28 MHz bandwidth).
Figure 39. 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 40.), the E1 flows are kept whilst the
Ethernet traffic with lowest priority (Fast Ethernet traffic #2) is reduced.

Figure 40. Example of traffic in case of 28MHz bandwidth and modulation downgraded to 16QAM
When the modulation is further degraded to 4QAM (Figure 41.), 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.6.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 CT 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 42., Figure 43. and Figure 44. show how the system operates in case of modulation changes when
admission control is disabled (case of 28 MHz bandwidth).
Figure 42. 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.7 Traffic profiles
Three kinds of traffic profiles have been identified:
TDM2TDM (9500 MPR-E 9500 MPR-E, internal TDM)
TDM2Eth (9500 MPR-E TDM to Ethernet)
DATA (Ethernet to Ethernet)
The first two profiles meet MEF8 standard.
Figure 45. Traffic profiles
Case 1
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 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 46. 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.7.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 47. E1 Traffic
Flow Id present (user defined)

Intermediate node configuration (E1 provisioning):
node by node (building Cross-connection tables based on Flow Id)
Bandwidth guaranteed (according to QoS Highest Queue Priority association)
No flooding-autolearning necessary
Both the IWFs belong to 9500 MPR-E and the packets are not supposed to exit the 9500 MPR-E network.
The IWF parameters listed above, have predetermined values and dont need to be provisioned.
Mac addresses are determined as consequences of the cross connections.
Payload size is fixed to 122 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.7.2 TDM2Eth
E1 traffic both internal and external to 9500 MPR-E equipment.
E1
BTS
PSN
Eth Eth E1
E1
BTS BSC
E1
BTS
Flow Id present (user defined)
All the parameters must be configured compliant with the MEF8 standard
Adaptive or differential clock recovery supported
Bandwidth guaranteed (according to QoS Highest Queue Priority association)
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
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.7.3 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.8 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 50.), 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 50. ATM Traffic Management - General block diagram
In Figure 51 is shown a more detailed block diagram of the ASAP unit in Ingress.

Figure 51. 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 5.
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 5. 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
The ATM cells are sent to ATM i/f, where a 4-queue scheduling is available before being trans-
mitted on physical interface (IMA/E1).
ATM Shaping (cell-based) is automatically configured, for each VP/VC configured on ATM
interface, according to its Egress Traffic Descriptor (PCR,SCR,MBS,CDVT), with Service Cat-
egory CBR.
ATM Cells belonging to an UBR and UBR+ VP/VC are assigned to the fourth lower priority
queue. Oversubscription is managed by a Weighted Round Robin scheduling among all UBR/
UBR+ VP/VC, whose weights are assigned according to VP/VC MDCR.
MDCR, up to [cell/s] RR Weight
151 1
302 2
604 3
1208 4
2415 5
3623 6
4528 7
> 4528 8
e.g. MDCR = 1000 [cell/s] -> Weight = 4

An UBR has MDCR=0 -> weight = 1
Table 6. RR weights
2.8.8.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 7. PW label EXP bits

2.8.8.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 52. 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.9 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.9.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, remains stored in the NE MIB.
Note: To change the configuration from 802.1D to 802.1Q, it is necessary to configure all the Ethernet
ports in Admit all mode to avoid hits on the traffic on that specific port.
2.8.9.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 Discard

(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
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.10 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 Craft Terminal) the configuration files can
be used. The configuration files configure the Ethernet switch inside the Core-E and the FPGA
inside the Modem 300 board.
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
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
The use of the Configuration files is explained in the relevant document Configuration File Management
3DB 18648 0001 TQZZA.

2.8.10.1 QoS in the Core-E unit
Figure 53. 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 eight internal queues per port to support
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.10.2 QoS in the Modem unit
Figure 54. QoS in the Modem unit
In the figure is shown an overview of the QoS implementation inside the Radio Interface module.
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 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 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.
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
001010, 001100, 001010, 001000, 000000 Q2
All remaining values Q1
QoS based on VLAN_ID
The VLAN_ID classification is always enabled, when a packet with VLAN is received the Radio Interface
module search inside the local memory if the VLAN_ID has been configured. If the query is positive the
packet is sent to the queue assigned to the VLAN_ID itself; if the query is negative the packet follow the
classification flow described above in the flow chart.
Inside the Radio Interface module up to 4096 VLAN can be assigned and to each one is associated one
egress priority queue. This association in release 1.0 is predefined:
For the VLAN_IDs used to configure TDM2TDM flows the egress priority queue is Q8;
For the VLAN_IDs used to configure TDM2ETH flows the egress priority queue is Q7
For the VLAN_IDs used to configure internal control traffic flows the egress priority queue is Q6.
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.11 Cross-connection
Figure 55. Cross-connection
The cross-connections between slots and between slots 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.11.1 E1 Cross-connection
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 a unique signal flow ID.
2.8.11.2 Radio-Radio Cross-connection
Ethernet frames, coming from a radio direction, can be cross-connected to another radio direction.
2.8.11.3 Ethernet Cross-connection
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.

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.
When TDM flow cross-connections or ATM PW flow cross-connections are defined and they don't involve
TDM or ATM ports, a port segregation involving User Ethernet ports or radio directions involved in these
flows cross-connections must be not already present. If present, the port segregation must be removed
before defining TDM or ATM PW flow cross-connection. Port Segregation between two ports can be
applied only if they are not used from the other cross-connection types (TDM or ATM PW flows cross-
connections). If for example, between one User Ethernet port and one radio direction there is a TDM2ETH
flow cross-connected, it is not possible to remove the port based cross-connection.
2.8.12 Synchronization for PDH/DATA
2.8.12.1 Synchronization overview
TDM 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 TDM data flow at the original bit rate
Three main methods can be used to recover at the Rx site, the original bit rate:
Differential clock recovery: 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 traffic (MPR to MPR)).
This method can be selected for each E1 stream.
Adaptive clock recovery: 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.
Node Timing: timing from the network clock as defined in G.8261. The enabling of the Node Timing
is applied to all E1s of the PDH unit.
By enabling the Node Timing the E1 streams in Rx side are retimed at the output with the network
element clock.
Note
In meshed networks (rings) do not close the synchronisation configuration.

2.8.12.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.12.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.12.2 Synchronization interface
Each Network Element must have a reference clock (NEC), which will be distributed to each board of the
NE. Such clock is a 25 MHz generated in the Core-E Module in the Clock Reference Unit (CRU) function.
The NEC also provides a Sync Out port on the Core-E Module.
The NEC is locked to a Synchronization Source.
The sources can be:
[1] Free Run Local Oscillator.
[2] Any E1 available at input traffic interfaces (the specific E1 port has to be chosen)

[3] A specific synchronization signal available from the dedicated Sync-In port, which can be configured
according to the following options:
a) 2.048 MHz, electrical levels according G.703, clause 13
b) 5 MHz, + 6 dBm 50 ohm, sine-wave
c) 10 MHz, + 6 dBm 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;
test load impedance 30 ohm.
[4] The Symbol Rate of the Rx signal of any available Radio direction (the specific Radio Port has to
be chosen).
Figure 56. Synchronization
[5] Any Available SynchrE: 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.8264 point of view, the MSS is a Synchronous
Ethernet equipment equipped with a system clock (NEC) following the ITU-T G.8262 recommenda-
tion. A User Ethernet interface configured in synchronous operation mode can work only at 1G. In
the particular case of electrical User Ethernet interfaces, these interfaces perform link auto negoti-
ation to determine the master and slave clocks for 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.
Some rules have to be followed while configuring the Primary and Secondary clock sources.
All the NEC has to be configured as Master or Slave.
Only one Master is allowed in the network.
If Master,

The Restoration Mode can be Revertive and Not Revertive
The Primary sources must be chosen among 1), 2), 3) or 5).
If the selected Master Primary Source is 1)
then the Master Secondary Source doesn't need to be selected because the Primary is
never supposed to fail.
If the selected Master Primary Source is 2), 3) or 5)
then Master Secondary Source must be selected among 1), 2), 3) or 5).
If Slave,
The Restoration Mode is fixed to Revertive.
The Primary Source must chosen between 3), 4) or 5)
Slave primary sources is allowed to be 3) or 5)
The Secondary Source can be chosen among 1), 2), 3) or 5).
Each Module will mute its own Synchronization clock in case of Fail Alarm.
For each available sync source, the CRU detects the signal Degrade Alarm on each available sync
source. Such Signal Degrade alarm raises also in case of muted (missing) clock.
The Signal Degrade Alarm relevant to the selected Synchronization Source, or the relevant Card Fail,
causes the switching of the Synchronization Source.
2.8.13 Synchronization for E1 ports with ASAP unit

The synchronization of each E1 ATM port in the ASAP unit can be configured (by the Craft Terminal) 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.14 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 57.
N.B. With this second solution 9400 AWY must be used to transport Ethernet traffic only.
Install the Ethernet

Data plug-in
Figure 57. 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.15 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 58.
Figure 58. 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 Network Element Overview

The Network Element Overview (NETO) is the starting point of the CT application.
NETO functions require to know the NE identity by means the related IP Address.
Only one NE can be managed in a NETO session.
The User Interface is provided by the NETO Main View described below.
3.1.1 Main view

When NETO starts, the main view screen is shown in Figure 59.
Figure 59. NETO main view: initial screen
This screen has three specific areas:
NE Configuration area: displays NE general information (left side);
Status & Alarms area: reports supervision status and alarms (right side);
Discovered NEs: in the lower part is shown the list of the discovered NEs. With a double click on
a row the IP address of the NE in the row automatically is written in the NE Info field
"Show" and "Alarm Monitor" buttons are enabled when a NE is supervised only. Supervision starts as
soon as the operator writes an IP address in the specific field and press the "OK" button.

NE Management by software application 3DB 18528 DIAA Issue 1 133/578
NETO Main view can also be reduced by using the shrink glass ( ) button in the Menu Bar.
Figure 60 shows the reduced NETO view, allowing the operator to save screen space while continuously
checking supervision and alarms status. Gray icons mean that supervision is not active. The magnifying
glass ( ) button allows to show the normal NETO main view (see Figure 59).
The alarm severity icon (shown in Figure 59 and Figure 60) appears in operating system "tray bar", close
to system clock and other system software icons.
Figure 60. NETO main view: reduced screen
This icon also has a specific tooltip, visible when mouse cursor is moved over it, that will show: name of
application, NE IP address, and highest severity alarms number. The tray-bar icon is present in the Win-
dows system bar (in the lower part of the screen). The tray-bar icon takes the color of the most severe
alarm. The tray-bar icon is not interactive and does not present any menu or executable command if
clicked either with left or right mouse button.
3.1.2 NE Configuration area

The panel is divided in three sections:
[1] NE Info section, containing information related to NE addressing;
[2] NE Description section, with information about NE characteristics;
[3] Command Buttons section, providing buttons to manage NETO functions.
3.1.2.1 NE Information
This area is related to wanted NE identification (Figure 61).
Figure 61. NETO NE Configuration View: NE Information
"IP Address" field displays the actual NE IP address used by NETO functions.
"OK" button will start supervision on specified NE, if reachable. Keyboard shortcut "Alt + o" behaves as
clicking on "OK" button with mouse.
Whether the IP address is correctly written, other than clicking on "OK" button, supervision process will
start on specified NE by pressing "enter" (carriage return) key on keyboard.

134/578 3DB 18528 DIAA Issue 1 NE Management by software application
3.1.2.2 NE Description
This area contains some parameters displaying general information about the supervised NE (Figure 62).
Figure 62. NETO NE Configuration View: NE Description
Parameters can be read and modified (and applied to NE using the "Apply" button).
Please note that changing these labels values will also automatically update NETO window title content:
window title will always contain "Site Name" of supervised NE. Keyboard shortcut "Alt + a" behaves the
same as clicking on "Apply" button with mouse.
3.1.2.3 Command Buttons
Figure 63 shows command buttons available through NETO.
Figure 63. NETO NE Configuration View: Command Buttons
"Show" button will start WebEML (JUSM/CT) application on a supervised NE.
"Alarm Monitor" button starts AM application. For the Alarm Monitor application refer to par. 3.5.1.
Buttons "Show" and "Alarm Monitor" will be enabled when NE is supervised only.
"Exit" button will close NETO, stopping a possibly running supervision and closing all related applications.
Keyboard shortcut "Alt + S" behaves as clicking on "Show" button with mouse. Keyboard shortcut "Alt +
m" behaves as clicking on "Alarm Monitor" button with mouse. Key-board shortcut "Alt + E" behaves as
clicking on "Exit" button with mouse.
3.1.3 Status & Alarms area

Information on supervision status and active alarms are shown in this area (Figure 64).
Figure 64. Main View: Status & Alarms

Round-shaped icons change their colours according to current NETO functions and situation. With
respect to "Supervision" status:
green colour means that supervision function is ongoing,
red colour means that NE link does not work,
gray icons mean that supervision is not active (to be started).
Alarm synthesis contains the list of the alarms listed by severity: whether an icon is not gray, means that
such kind of severity contains one alarm at least. "Alarm Monitor" button shown in Figure 63 opens the
Alarm Monitor application external tool.
3.1.4 Supervision Function

The supervision function allows operator registering a new manager inside NE MIB and performing cyclic
(periodic) monitoring on connection.
To start supervision, the operator must specify NE IP address in the "IP Address" field and then simply
press "OK" button.
If supervision succeeds, screen is updated with information retrieved from NE and supervision icon
changes its colour from gray to green stating NE is correctly supervised.
When a supervision error, a link down or other problems arise during supervision, icon will become red.
Alarm Synthesis area will be updated as well. Clicking on "Show" button, NETO will open the WebEML
(JUSM/CT) for MPR equipment.
To close an ongoing supervision, simply click on "Exit" button (this will also close NETO) or change NE
IP address and click "OK" button to start supervision procedure on a different NE (this will stop previous
supervision).
3.1.5 Menu bar
(New)
(Open)
NETO can manage and organize a list of available NEs by showing operator a table containing such data.
Using both (New) and (Open) icons, the operator will be able to open NEs table modal window
(see Figure 65).
"Open" icon allows opening a previously saved file containing a list of NEs.
"New" icon allows creating a new list, specifying the file name containing its data, only when those data
will be saved. Window allows the operator managing its NEs data by:

"Get Current" button is used to read information from main NETO view. This operation will always
add a new line in NE list table with all information related to currently supervised NE. This happens
even though a NE with corresponding IP address is still present in the list;
"New" button, adding a new NE from scratch. This allows the operator to fill the "IP Address" field
only with its needed NE.
"Remove" button, removing a selected NE;
"Set Current" button, filling main NETO view IP address with datum from selected NE. The operator
must pre-viously select a valid line in NEs table and then click on "Set Current" button so filling NETO
main win-dow data. This operation will automatically close the NE list window but does not start
supervision on set NE;
"Save" button, saving table list in a specified file.
All data are saved in a custom XML format called "NETO" and this structured file will contain all data shown
in Figure 59 related to all NEs added to the list.
Figure 65. NETO List Management
The operator can have its own NEs lists repository, containing all .NETO files that it produced with NEs
information inside. To close this window click on "Close" button. The operator can see the data related
to NEs as shown in Figure 65. As for NETO main window, even NE list window allows using keyboard and
hotkeys to perform operations. Through:
Keyboard shortcut "Alt + g" behaves as clicking on "Get Current" button with mouse;
Keyboard shortcut "Alt + s" behaves as clicking on "Set Current" button with mouse;
Keyboard shortcut "Alt + n" behaves as clicking on "New" button with mouse;
Keyboard shortcut "Alt + r" behaves as clicking on "Remove" button with mouse;
Keyboard shortcut "Alt + v" behaves as clicking on "Save" button with mouse;
Keyboard shortcut "Alt + c" behaves as clicking on "Close" button with mouse.
(Magnifying glass)
NETO Main view can also be reduced by using the shrink glass ( ) button.

Suggested usage sequence for NETO interface and NE list
1) Fill NETO main view "IP Address" field with NE IP address;
2) Start supervision by clicking "Ok" button;
3) Open the NEs table (any method, through "New" or "Open" button);
4) Click on "Get Current";
5) "Save" the list and "Close" the list window.
This operation will produce a clean and up-to-date NEs table list. The NE table lists are not updated, if
the operator will modify, NE site name site location or even IP address. Such data are used for references
purposes, but the operator must take care to keep them updated.

3.2 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 possible according to the MSS version:
MSS-8 (refer to Figure 66)
MSS-4 (refer to Figure 67)
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)
Protection 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.
Figure 66. MSS-8 Main view

Figure 67. MSS-4 Main view
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 66. 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);
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 66., 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 211);
Current Configuration View (refer to par. 3.5.6 on page 218);
Cross-Connections (refer to par. 3.4.5 on page 156);
Segregated ports (refer to par. 3.4.5.1.4 on page 159);
AUX Cross Connections (refer to par. 3.4.6 on page 189);
VLAN management (refer to par. 3.18 on page 335);
Performance Monitoring tool (refer to par. 3.17 on page 293).
3.2.3 Severity Alarm Area

The CT 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
CT 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 craft terminal
or by the OS
[2] COM icon: Operational state: indicates whether or not the communication with the OS is established.

[3] SUP icon: Supervision state: indicates whether or not the NE is under OS supervision.
[4] OS icon: OS isolation.
[5] NTP Server Status icon.
[6] AC icon: abnormal condition state: indicates whether some abnormal conditions have been recog-
nized. The operator can visualize them with the Diagnosis Abnormal condition list menu.
N.B. As for the alarm icons, a rectangular management state icon represents the stable state while
a circular icon shape represents an unstable management state.
The meaning of the icons in the Management State Control Panel is:
[1] Local Access State

GREEN LED: Indicates that the Craft Terminal has the OS permission to manage the NE (granted).
CYAN LED: Indicates that the Craft Terminal 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 Craft Ter-
minal (link down).
RED LED: Identifies the Disable operational state of the connection between NE and Craft Terminal
(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 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: 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 16xE1 ATM (ASAP) unit (if any): refer to ATM VIEW for ATM DOMAIN (this menu
opens with double click on an ASAP unit)
[6] Create Traffic Descriptors for ATM traffic: refer to MENU CONFIGURATION (Traffic Descriptors)
[7] Configure the Synchronization: refer to TAB-PANEL SYNCHRONIZATION (Synchronization)
[8] Configure the NE time: refer to MENU CONFIGURATION (NE Time)
[9] Configure the System parameters: refer to MENU CONFIGURATION (System Settings)
[10] Create the Cross-connections: refer to MENU CONFIGURATION (Xconnections)
[11] Configure IP/SNMP: refer to MENU CONFIGURATION (Network Configuration)
[12] Select the VLAN configuration and create VLAN, if required: refer to VLAN MANAGEMENT

3.4 Menu Configuration
3.4.1 Menu NE Time

The NE local time can be displayed and/or re-aligned to the OS time basis.
From the Configuration pull down menu, select the NE Time option.
The following dialogue box opens, from which the local NE time can be set.
The NE Time dialogue box displays the current NE time and the current OS time.
To re-align the NE time to the OS time, click on the Set NE Time With OS Time check box and click the
Apply pushbutton to validate.
The Refresh pushbutton causes the refresh of the screen.
The NTP Status field is a read-only field, which shows the configuration regarding the NTP (Network Time
Protocol), if the protocol has been enabled and configured in Menu Configuration Network Config-
uration NTP Configuration.
The NTP Status field shows:
status of NTP (enabled/disabled);
IP address of the Main Server, which distributes the time to all the NEs in the network;
IP address of the Spare Server (if any), 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 CT 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, if any.
The Server reachability field is a read-only field, which shows the reachability of the NTP servers. The
following information can appear:
"Main server reachable"
"Spare server reachable"
"None servers reachable"
"Both servers reachable"
Click on 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

This menu is not implemented in the current release.

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 8 fields:
1) Tributary Port Configuration
2) Quality Of Service
3) DHCP
4) Admission Control for Adaptive Modulation
5) Ethernet Interface Criteria for 1+1 EPS Core
6) Static Lag Criteria
7) Event and Alarm Log
8) NE MAC Address
Figure 68. 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
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 CT level has been inserted, avoiding any potential mis-
takes 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 Interface Criteria for 1+1 EPS Core
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 of user traffic passing through the User Ether-
net 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 69.) 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 5 Ethernet ports placed on the bottom, ordered from 1 to 5 from left to right.
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 is visible if in the Core-E unit has been installed and enabled the SFP optical plug-in.
There are a maximum of 6 PDH/ASAP/Radio slots (placed in the MSS-8 sub-rack) or 2 PDH/ASAP/
Radio 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 69. Main Cross-Connections View
Note
Ethernet port#5 will appear only if the optional optical 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.

3.4.5.1.1 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 or ASAP slots;
identifies Radio slots.
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 70. Cross-connections Example

3.4.5.1.2 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 71. 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.3 Buttons
Figure 72. 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 local cache and update the graphical state; any modification per-
formed 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.4 Segregated port view
From the Cross Connection view by pressing Alt+W the Segregated Port view opens.
Figure 73. Segregated Port View (default configuration)
In the default configuration (shown in Figure 73.) all the slots and Ethernet ports in Core-E unit are cross-
connectedable each other (all the slots/ports are not segregated).
To go back to the Cross Connection View press Alt+W.
3.4.5.1.4.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#7 RADIO Figure 74. opens.

Figure 74. Not segregated ports
To segregate Slot#7 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 75.
Figure 75. Port #2 to Port #5 segregated
By clicking OK the Segregated Port view opens, which now shows (with dashed lines) the segregated
ports, as shown in Figure 76.
Figure 76. 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".

Warning: In the Nx(1+0) configuration (multiple RF channels in the same radio direction) to avoid loops
only one radio port must be active (all the other radio ports must be segregated), if the Ethernet switch
is set in 802.1D mode.
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 77., it is possible to see different aspects of configuration created by
the operator:
Slot#8 PDH is cross-connected to Slot#7 radio;
Slot#4 PDH is cross-connected to Slot#7 radio;
Slot#3 PDH is cross-connected to Ethernet Port#1;
Slot#5 RADIO (and Slot#6 RADIO) are cross-connected to Ethernet Port#2;
Slot#8 PDH is cross-connected to Ethernet Port#4;
Slot#4 PDH (blue) could not accept more cross-connections;
Slot#3 PDH (green) could accept more cross-connections;
Radio slots#5 and #6 (green) could accept more cross-connections.
Each connection line is coloured according to slots types it connects (as shown in Figure 77.):
PDH-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.

Figure 77. 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 (in Figure 71.:
Slot#3 PDH is cross-connected with third radio slot).
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.3 TDM Cross-Connections
The Cross-connections to be implemented are:
[1] PDH-Radio
[2] Radio-Radio
[3] Radio-Eth
[4] PDH-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 Radio
By dragging a connection between a PDH slot and a radio slot, the operator will see the configuration dia-
log in Figure 78.
Configuration parameters will ask to specify Flow ID number, as associated in PDH slot.
Once correctly completed the cross-connection configuration and clicked on OK button, the operator will
see a black line describing the PDH-radio cross-connection defined (see Figure 79.).
Figure 78. PDH-Radio configuration dialog

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

Figure 80. Radio-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-Radio cross-connection defined (see Figure 81.).

Figure 81. Completed radio-radio cross-connection
[3] Radio Ethernet
By dragging a connection between a Radio slot and an Ethernet port, the operator will see the configu-
ration dialog in Figure 82.
Select the TDM service and enter the Flow ID, the Profile (TDM2TDM or TDM2Eth), the TDM Clock
Source (only in case of TDM2Eth ADAPTIVE or DIFFERENTIAL) and the Destination MAC Address (only
in case of TDM2Eth profile).

Figure 82. Radio-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 83.

Figure 83. Radio-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
on used input style (ranges or values), the operator will see two different confirmation dialogs.
see a green line describing the Radio-Ethernet cross-connection defined.

Figure 84. Completed radio-Ethernet cross-connection
[4] PDH Ethernet
By dragging a connection between a PDH slot and an Ethernet port, the operator will see the configuration
dialog in Figure 85.
To create other cross-connections drag other lines between the PDH slot and the Ethernet port and repeat
the operations.

Figure 85. PDH-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 green line describing the PDH-Ethernet cross-connection defined (see Figure 86.).

Figure 86. Completed PDH-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 87. No protection

Figure 88. 1+1 radio protection between NE B and C
Figure 89. 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.4 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.4.1 PDH-Radio
In Figure 90., the operator is modifying a previously created cross-connection (in this case Slot#8 PDH
and Slot#4 radio): this action brings up a dialog almost like the creation one, but with some differences
in allowed actions:
Previously assigned tributaries (13 in the example) are active and selected;
Tributaries assigned to another cross-connection (if any) are not active and not selected.
Figure 90. PDH-radio cross-connection modification
Remove the check mark and create again a cross-connection.

3.4.5.4.2 Radio-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 91. will appear.
Figure 91. Modifying a Radio-Radio cross-connection

3.4.5.4.3 Radio-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 92. can be managed by
the operator.
Figure 92. Modifying a Radio-Ethernet cross-connection
Select the TDM Service and remove the check mark and create again a cross-connection.

3.4.5.4.4 PDH-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 93. can be managed by the
operator.
Figure 93. Modifying a PDH-Ethernet cross-connection
3.4.5.5 ATM Cross-Connections
The Cross-connections to be implemented are:
[1] ASAP-Radio
[2] Radio-Radio
[3] Radio-Eth
[4] ASAP-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] ASAP Radio
By dragging a connection between an ASAP slot and a radio slot, the operator will see the configuration
dialog in Figure 94.
Configuration parameters will ask to:
select the ATM interface (this interface is the IMA group: from 1 to 8)
select the PW label
assign the VLAN ID
N.B. The Traffic Descriptor is automatically created.
see an orange line describing the ASAP-radio cross-connection defined (see Figure 95.).
Figure 94. ASAP-Radio configuration dialog

Figure 95. Completed ASAP-radio cross-connection
[2] Radio Radio
By dragging a connection between two different radio slots, the operator will see the configuration dialog
in Figure 96.
To create other cross-connections drag other lines between the two radio slots and repeat the operations.

Figure 96. 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 97. Traffic Descriptor
The operator has to fill in data to complete the cross-connection configuration.

Figure 98. Completed radio-radio cross-connection
[3] Radio Ethernet
By dragging a connection between a Radio slot and an Ethernet port, the operator will see the configu-
ration dialog in Figure 99.
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 99. Radio-Ethernet configuration dialog
see a green line describing the Radio-Ethernet cross-connection defined.

Figure 100. Completed Radio-Ethernet cross-connection
[4] ASAP Ethernet
By dragging a connection between an ASAP slot and an Ethernet port, the operator will see the config-
uration dialog in Figure 101.
To create other cross-connections drag other lines between the ASAP slot and the Ethernet port and
repeat the operations.

Figure 101. ASAP-Ethernet configuration dialog
select the ATM interface
select the PW label
assign the VLAN ID
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 102.).

Figure 102. 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.6 How to modify an ATM 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.6.1 ASAP-Radio
In Figure 103., the operator is modifying a previously created cross-connection: this action brings up a
dialog almost like the creation one:
Previously assigned tributaries (703 in the example) are active and selected;
Tributaries assigned to another cross-connection (706, 709 and others) are not active and not
selected.
Figure 103. ASAP-radio cross-connection modification
Select the ATM interface and remove the check mark and create again a cross-connection.

3.4.5.6.2 Radio-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 91. will appear.
Figure 104. Modifying a Radio-Radio cross-connection
Select the ATM Service and remove the check mark and create again a cross-connection.

3.4.5.6.3 Radio-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 105. can be managed by
the operator.
Figure 105. Modifying a Radio-Ethernet cross-connection
Select the ATM Service and remove the check mark and create again a cross-connection.

3.4.5.6.4 ASAP-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 106. can be managed by the
operator.
Figure 106. Modifying an ASAP-Ethernet cross-connection
Select the ATM interface and remove the check mark and create again a cross-connection.

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
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 107. 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 108. 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 109. Delete an AUX Cross Connection
3.4.7 Menu VLAN Configuration

For the VLAN Management refer to paragraph 3.18 on page 335.

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 110. 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 111. 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 112.) 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 112. 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 113. 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 113. 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 114. 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 115.) will be displayed; then the window to confirm the administrator password will be dis-
played (Figure 116.).
Figure 115. Delete user confirmation
Figure 116. 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 117. 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 118. 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.5 Menu Diagnosis
3.5.1 Alarms
This menu opens the Alarms Monitor application.
Alarms Monitor is an application which allows to display and store the alarms of all the NEs requiring it.
Alarms Monitor can be also started by clicking on the Alarms Monitor button on Neto.
On the left side of the application, below each NE, two global lists of alarms are displayed:
CURRENT_ALARM shows all the equipment alarms currently present,
ALARM_LOG shows all the equipment alarms currently present and the history of the alarms (i.e.
cleared alarms).

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

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

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

Filter Name field
Enter the filter name in the Filter Name field.
The filters can be created selecting one of the following fields (or more). To save the created filter click
on the Done pushbutton. (Clicking on the Cancel pushbutton clears the filter configuration). The created
filter appears on the left side of the application.
Scope field
Select APT (Current) to create a filter showing the current alarms only or select Log to create a filter for
current and cleared alarms.
The filter can be applied to all the NEs by selecting All or it can be applied to one or more NEs by selecting
one or more NEs using the mouse.
Alarm Type field
Select Alarm Type to create a filter for the selected type of alarm:
TRS = Transmission Alarm
EQUIPMENT = Equipment alarm
Perceived severity field
Select Perceived severity and then one or more severity levels and/or Cleared state to filter the alarm
having the selected severity levels.
Event Time field
Select Event Time and then enter the starting date (From) and the ending date (To) to filter the alarms
created during that specific time frame only.
Probable Cause field
Select Probable Cause and then choose a specific alarm (one or more) to filter these particular alarms
only.

Resource field
Put a check mark on the Resource box and write the object name the alarms of which have to be filtered
(if required).
[3] Edit Selected Filter
A filter, previously created, can be modified.
[4] Delete Selected Filter
A filter, previously created, can be deleted.
[5] Delete Filters ...
When this menu is selected, the window shown below opens.
By means of this menu the filters previously created can be canceled. Default filters cannot be canceled.
Select one specific NE (or more NEs) in the Scope column, select a specific filter (or more filters) in the
Filters column and then click on the Done pushbutton.
Clicking on the Cancel pushbutton all the selections are cleared.
[6] Save Filters As ...
A default filter, or a filter previously created by means of the Add a filter menu can be saved to be used
for some other LCTs.

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

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

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

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

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

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

3.5.5 Summary Block Diagram View
The Summary Block Diagram View of the Diagnosis menu displays a global logical view (strictly
related to the physical implementation) highlighting a synthesis of all the alarms and statuses present in
the system.
3.5.5.1 Main Block diagram view
Figure 119. shows an example of the Main block diagram view.
Figure 119. Cross-connection (Main) block diagram
Each block has its Alarm indicator (coloured ball icon) that shows the alarm status (different colors
according to the alarm severity).
In the Main view the current configuration of the PNU is shown, with the equipped units (PDH or Radio),
with the protection schemes and with the cross-connections implemented between the different units and
the different Ethernet ports, if any.
On the RADIO slot icon there is the symbol because on this unit a loopback can be activated, the sym-
bol because it is also possible to activate a Performance Monitoring and/or the Ethernet traffic
counters. If these symbols are green, it means that the loopback is active or the Perfomance Monitoring/
Ethernet Counters have been activated.
By double clicking on an object it s possible to navigate to specific views. In detail:
by double clicking on the Alarm indicator the relevant active alarm is displayed;
by double clicking on the Abnormal Condition List box, it is possible to navigate to the Abnormal
Condition List menu;

by double clicking on the TMN Local Interface box, it is possible to navigate to the TMN view in the
Core-E unit;
by double clicking on a PDH slot icon, it is possible to navigate to the secondary view for the PDH
unit;
by double clicking on a Radio slot icon, it is possible to navigate to the secondary view for the Radio
unit;
by double clicking on a Protection switch the relevant configuration is displayed;
by double clicking on a Loopback the relevant configuration is displayed.
The Refresh button will close all secondary windows, updating the main view one, and re-opening all
previously opened secondary windows, with updated content views.
All diagrams are automatically refreshed. According to the following figures, bold light green lines update
according to the actually NE working way; alarm icons update as well.
The green line is the current active path.
3.5.5.2 PDH unit secondary view
Depending on the configuration, different diagrams are shown to the operator (see Figure 120. to Figure
123.), describing the actual NE status and working mode.
Performance Monitoring icons ( ) are shown in green whenever a PM is active.
By double clicking on the Performance Monitoring icon ( ) the navigation to the Performance Monitoring
tool starts.
Figure 120. 1+0 block diagram (PDH unit) (without Core-E protection)

Figure 121. 1+0 block diagram (PDH unit) (with Core-E protection)
Figure 122. 1+1 block diagram (PDH units) (without Core-E protection)

Figure 123. 1+1 block diagram (PDH units) (with Core-E protection)
3.5.5.3 Radio unit secondary view
Depending on the configuration, different diagrams are shown to the operator (see Figure 124. to Figure
129.), describing the actual NE status and working mode.
Loopback icons ( ) are shown in green colour ( ) whenever a loopback is active.
Performance Monitoring icons ( ) are shown in green whenever a PM is active.
By double clicking on the Performance Monitoring icon ( ) the navigation to the Performance Monitoring
tool starts.
Ethernet Counters icon ( ) is shown in green whenever the counter has been activated.
By double clicking on the Loopback icon, on the PM icon or on the Ethernet Counters icon the navigation
to the relevant menus starts.
Switch block (EPS Core-E, RPS TX, RPS Rx, ) are updated according to the signal path, following
light green-coloured line.

Figure 124. 1+0 block diagram (Radio unit) (without Core-E protection)
Figure 125. 1+0 block diagram (Radio unit) (with Core-E protection)

Figure 126. 1+1 FD block diagram (Radio units) (without Core-E protection)
Figure 127. 1+1 FD block diagram (Radio units) (with Core-E protection)

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

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

3.6 Menu Supervision
3.6.1 Access State

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

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

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

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

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

3.7 Menu SW Download
3.7.1 Server Access Configuration

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

fields and then by clicking on button OK

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

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

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

Figure 131. Panel 2 (Stand by software)
By clicking on the Software Units Status button a screen opens, giving additional information on the soft-
ware package.
Figure 132. SW units details
The following information is displayed on the screen:
MDPAR: firmware version of the FPGA involved in the MSS/ODU communication channel.
OC_R: software on the ODU Controller (Radio)
FCERE: FPGA firmware version (32xE1 Local Access unit)
FGUIN: FPGA firmware version (Modem Unit)
FDUFF: FPGA firmware version (Core-E unit)
FFURO: FPGA firmware version (AUX unit)
FRCFG, FCNFD, FASAP, FASAB: FPGA firmware version (ASAP unit)
EC: software on the Equipment Controller

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

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

3.8.2 Starting From Scratch
Figure 133. Equipment View (starting from scratch) with MSS-8
When equipment configuration panel is open starting from a scratched NE, the operator will see the panel
in figure below. The Resource Tree area contains a list of empty slots that have to be configured.
Icon is used to identify an empty slot.
To create a unit select the slot. The setting tab-panel, shown in the figure, opens.
Select the unit type in the Equipment type profile and click on Apply.
The Setting tab-panel of the SFP is shown here below.
Click on Apply on the Plug-in Type field to enable the SFP optional optical plug-in, if the plug-in has been
installed in the Core-E unit.

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

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

3.8.5 Settings tab-panel
In the Settings tab-panel the following fields are present:
[1] Equipment Type
[2] Alarm Profile
[3] Protection Type Configuration
[1] Equipment Type
This field lists all the units that can be installed in a specific slot.
If the user selects the expected equipment type equal to received one, the Apply button is enabled.
If the user selects an expected equipment type different from received expected equipment type, the
Apply button is enabled.
If the user applies a new expected equipment type, panel is reloaded and updated.
If protection type is 1+1, the Apply button, related to expected equipment, is disabled (Expected equip-
ment change is allowed in 1+0 configuration only).
Figure 134. Expected Equipment Type Configuration
When a board shows the check mark icon, while same-pair (same-row) one shows switch symbol
, this means pair (row) is protected. In this situation, the couple is considered as if it is one board and
each single board cannot be removed/un-configured unless removing protection.

Check mark icon denotes active board while switch one represents stand-by board.
Same behaviour occurs when X-shaped icon , representing cross-connections, appears. PDH board
cannot be removed as well when Flow IDs are configured; this situation cannot be seen, while watching
MSS schematics as in Figure 134. An error message will be shown if the operator will try to perform such
operations.
[2] Alarm Profile
This function relates to an alarm severity profile to be assigned to the selected equipment (not imple-
mented).
[3] Protection Type Configuration
This function allows the operator to configure the NE protection type. This function is shown selecting slots
3 to 8 only.
For slots 1 and 2 (reserved to Main and Spare Core-E boards), protection type is configured by the system,
according to equipped Core-E board.
After the equipment selection, protection type list box is filled with the allowed protection types list whose
content depends on expected equipment configured:
If it is configured as P32E1DS1, allowed protection types are 1+0 and 1+1 EPS;
If it is configured as MD300, allowed protection types are 1+0, 1+1 HSB and 1+1 FD.
If the operator selects a protection type equal to received one, the Apply button is disabled. If the operator
selects a protection type different from received one, Apply button is enabled. If slot is in protection mode
(received protection type different from 1+0): Apply button related to expected-equipment is disabled
(equipment changing is allowed in 1+0 configuration only).
Figure 135. Protection Example

Configuring a 1+1 protected board, if peer board is not configured, the CT will be in charge of applying
such configuration to un-configured peer board, before creating protection in MIB.
If the user applies a new expected protection type, both tree view and configuration panel are reloaded
and updated. With a configured 1+1 protection, involved slots are bounded by light green lines (see Figure
135.).
3.8.6 Remote Inventory tab-panel

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

The recommended sequence to configure the NE is the following:
1) Enable the plug-in units: refer here in TAB-PANEL EQUIPMENT
2) Configure the Core-E unit: refer to Core-E VIEW for Core-E and ETHERNET DOMAIN (this
menu opens with double click on a Core-E unit) (file Core-E domain)
To enable the optional SFP plug-in select the Core-E unit in the Equipment tab-panel and click
on Apply in the Plug-in Type field, as shown in Figure 136.
3) Configure the Radio unit: refer to RADIO VIEW for RADIO DOMAIN (this menu opens with
double click on a Radio unit) (file Settings)
4) Configure the PDH unit: refer to PDH VIEW for PDH DOMAIN (this menu opens with double
click on a PDH unit) (file PDH unit configuration)
5) Configure the ASAP unit (if any): refer to ATM VIEW for ATM DOMAIN (this menu opens with
double click on an ASAP unit) (file ASAP unit configuration)
6) Create Traffic Descriptors for ATM traffic: refer to MENU CONFIGURATION (file Traffic
Descriptors)
7) Configure the Synchronization: refer to TAB-PANEL SYNCHRONIZATION (file Synchroniza-

tion)
8) Configure the NE time: refer to MENU CONFIGURATION (file NE Time)
9) Configure the System parameters: refer to MENU CONFIGURATION (file System Settings)
10) Create the Cross-connections: refer to MENU CONFIGURATION (file Xconnections)
11) Configure IP/SNMP: refer to MENU CONFIGURATION (file Network Configuration)
12) Select the VLAN configuration and create VLAN, if required: refer to VLAN MANAGEMENT

Figure 136. SFP plug-in enabling

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

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

Figure 139. 1+1 Radio unit block diagram (FD)
Figure 140. 1+1 Radio unit block diagram (HSB)

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

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

The PDH protection type is Not-Revertive and cannot be changed.
Note
In case of 1+1 HSB-EPS, the restoration criteria are always greyed out.
No changes can be done separately for 1+1 HSB-EPS.
The restoration criteria selected for HSB-TPS will be applied to EPS automatically.
3.9.1.2 Commands
To enter the Commands menu click on the Spare #0 element in the Tree view or on the Main #1 element.
The operator by the Craft Terminal can modify the state of the switch through commands Lockout, Forced
and Manual. Select the suitable command and click on Apply.
Note
On the Main#1 channel the only available commands are Manual and
Forced (only Forced for the Core-E protection).
On the Spare#0 channel the only available commands are Manual and
Lockout (only Lockout for the Core-E protection).
Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel), inde-
pendently of the possible active alarms. This command activates signaling ABN.

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

Command Priority
Lockout 1
Forced 2
Automatic switch 3
Manual 4
Note
To release a previously activated command select None and click on Apply.
3.9.2 Rx Radio Protection Management

The Radio Protection Management is performed by selecting the Rx Radio Protection element tree.
This window allows a complete view of all NE resource involved in a RPS protection.
The tab-panels are:

Commands
The tab-panel Protection Schema Parameters displays the parameters that can be modify.
The Schema Parameters are:
Protection Type field: defines the protection schema architecture: 1+1 hitless;
Operation Type field: the possible values are revertive (automatic restoration allowed) or notRe-
vertive (automatic restoration Inhibited).

3.9.2.2 Commands
To enter the Commands menu click on the Spare #0 element in the Tree view or on the Main #1 element.
Note
On the Main#1 channel the only available commands are Manual and Forced.
On the Spare#0 channel the only available commands are Manual and Lockout.
Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel), inde-
pendently of the possible active alarms. This command activates signaling ABN.
Forced has higher priority than the automatic operation: the activation of this command forces in service
Channel 0, independently of the possible active alarms. This command activates signaling ABN.
The Manual command can be activated only if the two channels are aligned.
Note
The Forced command for channel 1 is equivalent to the Lockout command for the channel 0. In both
case, the result is that the relevant channel protection path is forced to standby status.

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

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

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

3.10 Tab-panel Synchronization
Synchronization menu allows the operator to manage the synchronization features.
Using Synchronization tab view (shown in the figure below) the operator can select and configure syn-
chronization source(s) for the equipment.
Together with Role and Restoration criteria, the operator can select Input and Output ports and can
discriminate between different possible Primary or Secondary sources, according to the Role.
Figure 141. Synchronization Settings view
The Resource list area shows the configuration summary describing current synchronization.
As for all other views, Synchronization contains Alarms tab as well and it allows discriminating synchro-
nization-specific alarms.
3.10.1 How to synchronize

Each Network Element must have a reference Clock (NEC), which will be distributed to each board of the
NE. Such clock is a 25 MHz generated in the Core-E Module in the Clock Reference Unit (CRU) function.
The NEC also provides a Sync Out port on the Core-E Module, which can be used to synchronize other
NEs.
The NEC is locked to a Synchronization Source.

The sources can be:
[1] Free Run Local Oscillator.
[2] Any E1 available at input traffic interfaces (the specific E1 port has to be chosen)
[3] Sync-In port is a specific synchronization input, which can be configured according to the following
options:
a) 2.048 MHz, electrical levels according G.703, clause 13

b) 5 MHz, + 6 dBm 50 ohm, sine-wave
c) 10 MHz, + 6 dBm 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;
test load impedance 30 ohm.
[4] Radio Port: Symbol Rate of the Rx signal of any available Radio direction (the specific Radio Port
has to be chosen).
Figure 142. Synchronization
[5] Any Available SynchrE: 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.8264 point of view, the MSS is a Synchronous
Ethernet equipment equipped with a system clock (NEC) following the ITU-T G.8262 recommenda-
tion. A User Ethernet interface configured in synchronous operation mode can work only at 1G. In
the particular case of electrical User Ethernet interfaces, these interfaces perform link auto negoti-
ation to determine the master and slave clocks for 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.
Some rules have to be followed while configuring the Primary and Secondary clock sources.
ll the NEC has to be configured as Master Role or Slave Role.
Only one Master is allowed in the network.
If Master Role,

The Restoration Mode can be Revertive and Not Revertive
The Primary sources must be chosen among 1), 2), 3) or 5).
If the selected Master Primary Source is 1)
then the Master Secondary Source doesn't need to be selected because the Primary is
never supposed to fail.
If the selected Master Primary Source is 2), 3) or 5)
then Master Secondary Source must be selected among 1), 2), 3) or 5).
If Slave Role,
The Restoration Mode is fixed to Revertive.
The Primary Source must chosen between 3), 4) or 5)
Slave primary sources is allowed to be 3) or 5)
The Secondary Source can be chosen among 1), 2), 3) or 5).
Each Module will mute its own Synchronization clock in case of Fail Alarm.
For each available sync source, the CRU detects the signal Degrade Alarm on each available sync
source. Such Signal Degrade alarm raises also in case of muted (missing) clock.
The Signal Degrade Alarm relevant to the selected Synchronization Source, or the relevant Card Fail,
causes the switching of the Synchronization Source.

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

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

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

3) Flow Id: identifier of the tributary for the cross-connection
4) Service Profile: possible profile to be associated to the tributary (TDM2TDM/TDM2Eth)
5) Payload: bytes of the payload (256)
6) ECID Tx: Emulated Circuit Identifier in Tx direction (up to 65.536)
7) ECID Rx: Emulated Circuit Identifier in Rx direction (up to 65.536)
8) TDM Clock source: type of the clock to be associated to the tributary (Adaptive/Differential/
Tdmline)
Note
Columns 5, 6, 7 and 8 are only available if the Service Profile is TDM2Eth.
For every E1 tributary two tab-panels are available:
Alarms tab-panel
Settings tab-panel
3.12.2.1 Alarms tab-panel
3.12.2.2 Settings tab-panel
This tab-panel performs all available functions for a tributary port. The managed tributary types are: E1.
To define the involved ports, the interface selection in the tree view is first required; therefore the selection
of the desired tributary port in the tabular view enables the Resource Detail list to show the available func-
tions for the single one resource.
Warning: to change something in the Settings tab-panel first change the Signal Mode to Framed/
Unframed. Then, all the other fields can be changed.

In the Setting tab-panel there are the following fields:
Port Number: identifies the ports for a given interface and type of port (read-only fields)
Signal Mode:
The possible values are:
Unframed for the unframed received signal
Framed for the collection of the performances at the input in Tx side and at the output in Rx side
Disabled
The current state can be modified selecting a different signal mode value and then click on the Apply
button to send the new value to NE.
Service Profile:
The possible profiles are:
TDM2TDM
TDM2Eth
Flow Id: To implement cross-connections between line side and radio side each E1 tributary must be
associated to an identifier. Enter the Flow identifier value in the relevant field (possible values: 2 to 4080)
and press Apply.
WARNING: The Flow Id must be unique in the MPR network.
Fields ECID Tx, ECID Rx, Payload Size and TDM Clock Source can be written only if the Service Profile
is TDM2Eth.
Note
With the TDM2TDM service profile the TDM Clock source is fixed to Differential (RTP - Real Time Protocol
is used); with the TDM2Eth service profile the TDM Clock source can be Differential (RTP - Real Time
Protocol is used) or Adaptive (RTP is not used). In the unit it is not possible to have mixed configura-
tions with service profiles using RTP and other service profiles not using RTP.
Example: if in the unit only one E1 has service profile TDM2TDM it is possible to configure other E1 with
service profile TDM2Eth only with the Differential clock source (not with the Adaptive clock source). If the
Adaptive clock source is requested the E1 must be connected to another PDH unit.

Alarm profile: Not implemented now.
Buttons:
Apply: the configuration for the selected E1 tributary will become active
Apply to All: the configuration present in the screen will be applied to all the ports.
Help: by clicking on this button the operator calls the help on line.
3.12.2.3 General information on Circuit Emulation
9500 MPR-E performs Circuit Emulation on PDH TDM flows, and then transport those "TDM packets"
mixed to native Ethernet frames.
The Circuit Emulation IWF (inter-working function) is according the Metro Ethernet Forum implementation
agreement known as MEF 8, limited to the structure agnostic case.
MEF 8 emulated circuits is based on exchange of service parameters between two CES IWFs at either
end of the emulated circuit; if one of those IWFs belong to the 9500 MPR-E the following parameters are
defined:
MAC addresses of the two IWFs
Payload size
ECID (2 different values may be used for each direction)
TDM clock source

clock recovery adaptive
clock recovery differential
VLAN (One Vlan is assigned to each bi-directional circuit emulated E1 flow)
RTP, which is optional in MEF8, is always present, but not used if the clock recovery is not differential.
The common clock for Differential clock recovery is 25 MHz.
Three different cases of Circuit Emulation services are implemented:
1) TDM2TDM
2) TDM2ETH
3) ETH2ETH
TDM2TDM
Both the IWFs belong to 9500 MPR-E and the packets are not supposed to go out the 9500 MPR-E net-
work.
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: fixed to 121 bytes
ECID will be the same value as Flow Id
TDM clock source: clock recovery differential,
Flow Id provisioned by ECT/NMS
TDM2ETH
Only one of the IWFs belongs to 9500 MPR-E and the packets are supposed to go out the 9500 MPR-
E network.
MAC addresses: in all involved nodes are determined as consequences of the cross connections;
the only exception is the Ethernet Terminal Node (the node where that TDM2ETH traffic goes
through an user Ethernet port). In such ETN the source address will be the node Mac address, the
dest. mac address will be provisioned by ECT/NMS.
Payload size: fixed to 256 bytes
ECID : provisioned by ECT/NMS, 2 different values may be used for each direction
TDM clock source will be provisioned by ECT/NMS: clock recovery adaptive, clock recovery differ-
ential
Flow Id will be 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 only is 3.5 msec for 256 bytes.
ETH2ETH
None of the IWFs belongs to 9500 MPR-E.
None of the above parameters has to be configured (the 9500 MPR-E is transparent).
Any packet belonging to an Eth2Eth TDM flow is treated as any other Ethernet packet with the only excep-
tion of giving it an higher priority based on the MEF 8 Ethertype.

3.12.2.4 Application examples
With 9500 MPR-E different applications can be implemented as shown in Figure 144. and Figure 145.
Figure 144. 9500 MPR-E applications
Figure 145. 9500 MPR-E applications
Case 1
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 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.
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-learn-
ing algorithm of the 9500 MPR-E Ethernet switch.
3.12.2.5 Node Timing configuration
Click on the slot icon (as shown in Figure 146.) to access the Node Timing menu.
Figure 146. Node timing
Node Timing: timing from the network clock as defined in G.8261. The enabling of the Node Timing is
applied to all E1s of the PDH unit.
By enabling the Node Timing the E1 streams in Rx side are retimed at the output with the network element
clock.

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

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

3.13 RADIO VIEW for RADIO DOMAIN (this menu opens with double click
on a Radio unit)
3.13.1 General information on the Radio domain menu

The Radio domain view allows the operator to manage the resources of the radio transmission channel.
A Radio NE consists of one or two radio channels with a set of functional blocks (tributary ports, radio ports
etc).
Resource Tree Area: displays the radio ports sorted by channel number.
Resource Detail Area: displays, through tab windows, the object s properties selected in list area.
This area enables to execute the available functions for involved resource.
Four tab panels are present in the Resource Detail Area:
Alarms: shows the active alarms
Settings: configures the radio parameters
Measurements: performs the Tx and Rx power measurements.
Loopback: activates the loopbacks available with the equipment.
3.13.2 Alarms

3.13.3 Settings
3.13.3.1 General
To configure the Radio unit click in the Main view on the icon of the Radio unit to be configured.
The Radio Main View opens.
The Radio Main View is divided in two parts:
on the left side is present the Direction # menu
on the right side is present the Channel #1 menu (for 1+0 configuration) and Channel #1 and Channel
#0 menus (for 1+1 configuration).
Warning: to configure the Radio unit first configure the Shifter and the Tx Frequency in the Frequency
field (in the Channel menu) and click on Apply. Then configure all the other parameters.
Warning: When in an already working system, a new modem card is inserted (for example in order to cre-
ate a new radio direction) with IDU/ODU cable disconnected, the radio can be configured by using the
CT: "Shifter", "Tx frequency", "Tx power", "Capacity" values are "correctly" applied into the database (not
to ODU because it is missing). When the idu/odu cable is connected the ODU is not right configured:
Shifter value result "Undefined" and the "Tx mute" is active. It is necessary to apply again the ODU param-
eters (pushbutton Apply in CT screen).
3.13.3.2 Direction menu
This part of the screen is divided into 3 parts:
1) Mode
2) Link Identifier Configuration
3) PPP RF
1) Mode
The operation mode can be without or with the Adaptive Modulation.

a) Operation without the Adaptive Modulation
Figure 148. Radio unit without Adaptive Modulation settings
Select in the Mode field Presettings.
Select in the Reference Channel Spacing field the suitable channel spacing to be used.
Select in the Modulation field the suitable Modulation scheme. Refer to next table for the possible
selections.
According to the selected Channel Spacing and to the Modulation the relevant capacity in the Capac-
ity field will appear.
To confirm the selection click on Apply.

Radio capacity, channelling scheme and modulation (Static Modulation)
Channel Modulation Net radio throughput E1 Equivalent Capacity (TDM2TDM)
4 QAM 10,88 Mbit/s 4 E1
64 QAM 32,64 Mbit/s 13 E1
4 QAM 21,76 Mbit/s 8 E1
14 MHz 16 QAM 43,52 Mbit/s 18 E1
64 QAM 65,28 Mbit/s 27 E1
4 QAM 43,52 Mbit/s 18 E1
16 QAM 87,04 Mbit/s 37 E1
32 QAM 111,36 Mbit/s 48 E1

28 MHz
64 QAM 130,56 Mbit/s 56 E1
128 QAM 156,80 Mbit/s 68 E1
256 QAM 177,60 Mbit/s 77 E1
16 QAM 166,40 Mbit/s 72 E1
56 MHz 128 QAM 313,60 Mbit/s 136 E1
256 QAM 344,198 Mbit/s 150 E1
b) Operation with the Adaptive Modulation
Figure 149. Radio unit with Adaptive Modulation settings

The main idea behind Adaptive Modulation in Point to Point system is to adjust adaptively the modulation
as well as a range of other system parameters based on the near-instantaneous channel quality infor-
mation perceived by the receiver, which is fed back to the transmitter with the aid of a feedback channel.
The following table provides the figures in terms of radio capacity, channelling scheme and modulation
in case of adaptive modulation.
Radio capacity, channelling scheme and modulation (Adaptive Modulation)

Channel Spacing Modulation Net radio throughput Equivalent capacity E1 (Note)
4 QAM 43,52 Mbit/s 18 E1
28 MHz 16 QAM 87,04 Mbit/s 37 E1
64 QAM 130,56 Mbit/s 56 E1
4 QAM 21,76 Mbit/s 8 E1
14 MHz 16 QAM 43,52 Mbit/s 18 E1
64 QAM 65,28 Mbit/s 27 E1
4 QAM 10,88 Mbit/s 4 E1
64 QAM 32,64 Mbit/s 13 E1
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).
The switching between the modulation schemes is hitless and maintains the same RF channel bandwidth.
The Adaptive Modulation is available for unprotected (1+0) and Protected (1+1 HSB) Radio configuration
without ATPC.
To configure the Adaptive Modulation:
Select in the Mode field Adaptive Modulation.
Select in the Modulation Range field the Modulation range (4/16 QAM or 4/16/64 QAM) to be used
by the Adaptive Modulation.
Select in the Reference Channel Spacing field the suitable channel spacing.
Select in the Reference Mode field the spectral efficiency class to be set as reference.
Select in the Remote Threshold field how many dB the switching thresholds have to be moved from
the default value (+4 dB/-2 dB). The default value is approx. 6 dB below the 10-6 Rx threshold.
To confirm the selection click on Apply.

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

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

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

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

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

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

From Adaptive to Static
When the Adaptive Modulation is disabled, if all the pre-configured TDM2TDM or TDM2ETH
in the Old Adaptive Modem Profile, stays in the capacity of the New Static Modem Profile, the
request is accepted and the residual bandwidth for new Static Modem Profile will be computed.
If all the pre-configured TDM2TDM or TDM2ETH cannot stay in the capacity of the New Static
Modem Profile, the request of change is rejected.
2) Link Identifier
This part allows the operator to define the expected and sent identifier values of parameters related to
the link management and, if necessary, modify them.
The operator choices will be sent to the NE by clicking on the related Apply button.
If the Link Identifier is Enabled the following fields can be written:
Expected Identifier: this field is the link identifier expected at the receiving NE
Sent Identifier: this field is the link identifier inserted on the transmitting NE (from 1 to 255).
3) PPP RF
The PPP-RF interface is a communication interface based on the use of an inframe RF proprietary 64
kbit/s channel. Through the PPP-RF interface the NE can exchange management messages with a
remote OS (or Craft Terminal) station.
The PPP-RF channel can be Enabled or Disabled.
If enabled, in the Remote Address field will appear the IP address of the remote connected NE.
In the Routing IP Protocol field enter the used IP protocol and in case of OSPF protocol select also the
associated OSPF area.
3.13.3.3 Channel menu
This menu is divided in 5 parts:
a) Frequency
b) ATPC (this menu is alternative to RTPC menu)
c) Manual Transmit Power Control (this menu is alternative to ATPC menu)
d) Tx Mute
e) Alarm Profile
a) Frequency
The system can operate with different types of ODU according to the RF band and to the channel arrange-
ment. There are ODUs which can manage only one shifter or several predefined shifters.
In the Shifter field select the suitable shifter and press Apply.

In the Tx frequency field insert the suitable Tx frequency (the Rx frequency is automatically calculated
by using the inserted Tx frequency and the shifter) and press push-button Apply.
b) ATPC
Note
the ATPC area is not present if the Adaptive Modulation has been selected.
The ATPC can be Enabled or Disabled.
The new value will be applied when the Apply button is pressed. If the ATPC has been enabled, the ATPC
Range and ATPC Rx Threshold parameters must be filled.
ATPC Range
The Min Tx power and Max Tx power, regarding the Tx Range in the ATPC management, can be
written in the relevant field.
When the Apply button is pressed the new values will be applied.
ATPC Rx Threshold
The value of the low power threshold can be changed by writing the new value in the field. When
the Rx power is equal to this power the ATPC algorithm starts to operate.
When the Apply button is pressed the new values will be applied.
c1) Manual Transmit Power Control (without Adaptive Modulation)
If the ATPC is disabled the Tx Power field is present.
In this field write the new value within the allowed transmitted power range. The range is shown on the
right side of Manual Transmit Power Control area.
c2) Tx Power (with Adaptive Modulation)
The operator can modify only the 4 QAM field. In this field the operator has to enter the constant power,
which will be used with 4 QAM modulation. The power range is shown on the right side and depends on
the selected reference mode.
Note
the same power value will be used by the 16 QAM and 64 QAM modulation schemes.

d) Tx Mute
The information related to the transmitter status is shown in the Tx Mute field (Off/Manual/Auto). To
squelch the transmitter select Enable and press Apply button.
The following indications will appear in the Tx Mute field:
Off: Transmitter not squelch
Manual: Transmitter squelched due to the manual operation
Auto: Transmitter squelched due to an automatic operation
N.B. When the mute command is applied, alarms and errors occur on reverse direction of the same
radio path.
e) Alarm Profile
Not implemented in the current release.

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

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

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

Radio analog received power level (remote ODU)
In case of failure on reading the register containing the remote received power the value shown at
management system is -99.7 dBm. If the power level read is out of the allowed range, the value
shown by the management system is -101 dBm. In case of alarms on the remote NE on one of the
two radio channels in HSB configuration (typically ICP, Cable Loss, Card Missing, Card Fail), the
value shown by the management system is -127 dBm.
3.13.4.1 How to read a Power Measurement file
Click on Read File field and press on the Select File button. The directory of the CT automatically opens
to navigate and get the power measurement file.
Note
As default the measurement files are stored in the MPRE_CT_V001.02.xx

directory and have extension .txt.
Select the desired file and click Open.
Click button Open on the right side of the Sample Time field.
The buttons in the lower part of the window allow to flow the graph within the measurement interval.
Note: The measurement file can be opened also with a standard text editor (e.g. WordPad). Go in the
directory where the txt files are stored and open the file. The measurements are shown in the tabular
mode.
3.13.5 Loopback
The functions described in this section allow to perform the test operations by loopbacks.
Resource Tree Area: displays the object on which the loopbacks can be performed, sorted by num-
ber.
Resource List Area: displays tabular information about the loopback supported by the resource
selected in the tree area.
Resource Detail Area: displays, through tabbed windows, the properties done in list area. This area
enable to perform the available functions for the involved resource.
Note
The loopbacks can be activated on the local NE only.
In the Resource List Area are listed all the loopbacks which can be performed. In the current software
version only the IF cable loopback is available.

In this area the following information is given:
1) Interface: number of the channel and type of the loopback
2) Direction: type of the loopback
3) Activation: activation status of a loopback (Active/Not Active)
4) Activation date: date of loopback activation
5) Timeout: timeout period, if has been set.
In Figure 150. is given the association of the loopback and the position in the block diagram of the equip-
ment provided by the Summary Block Diagram View option, available in the Diagnosis menu.
Figure 150. Loopback
3.13.5.1 How to activate a loopback
[1] Before to activate the loopback mute the Transmitter. Double click on the front panel of the Radio
unit and enter the Settings tab-panel.
[2] Select the loopback to be activated by clicking on the relevant object in the Resource Tree Area or
[3] Select Active in the Activation field.
[4] Click on Apply.
[5] The Loopback is now ACTIVE (in the row in the Resource List Area the Activation field of the loop-
back will change from Not Active to Active).
Note 1
The IF cable loopback is active only on the cross-connections with TDM2TDM and TDM2Eth profiles.

Note 2
In the Timeout Period field a timeout period can be set for the loopback activation (max. 4 days).
At the end of this period the loopback will be automatically deactivated.
3.13.5.2 How to remove a loopback
[1] Select the loopback to be removed by clicking on the relevant object in the Resource Tree Area or
[2] Select Not Active in the Activation field.
[3] Click on Apply.
[4] The Loopback is now DEACTIVATED (in the row in the Resource List Area the Activation field of the
relevant loopback will change from Active to Not Active).
[5] Remove the muting from the Transmitter.

3.14 ATM view for ATM DOMAIN (this menu opens with double click on
an ASAP unit)
The configuration of the ASAP unit is divided in four tab-panels:
E1 Layer (par. 3.14.1)
IMA Layer (par. 3.14.2)
ATM Layer (par. 3.14.3)
ATM PW Layer (par. 3.14.4)
3.14.1 E1 Layer
Figure 151. ASAP E1 Layer view
This menu allows to configure the physical E1 layer.
To configure the E1 layer:
1. Select the E1 port# (from 1 to 16)

2. Select the Signal mode: Framed/Disabled
3. Select the Clock mode: node-timed/loop-timed.
4. Click on Apply.
N.B. By clicking on Apply To All the same configuration will be applied to the 16 E1 ports.
N.B. The line impedance can be 75 ohm or 120 ohm.
N.B. The Alarm Profile is not implemented in the current release.

3.14.2 IMA Layer
Figure 152. ASAP IMA Layer view
In the ASAP unit max. 8 IMA groups can be created.
To configure an IMA group:
1. Select the IMA group (from #01 to #08).
2. Enter the Near End ID (this identifier will be written in the ATM cells of the IMA protocol).
3. Enter the Min number of links (this is the minimum numbers of working E1 links, with which
the IMA group is still operational).
4. Enter the Max Differential Delay (in ms) between the E1 streams of the IMA group.
5. Click on Apply in the IMA Group Parameters are.
6. Select the E1 streams, which will be associated to the IMA group, by putting a check mark in
the Add check box. Up to 16 E1 links can be associated to the same IMA group.
N.B. When an E1 has to be removed from an IMA group it is necessary, before applying
the operation, to set the administrative status to down. In this case there is no affect
on the traffic.
7. Click on Apply in the IMA Link Table area.
N.B. By clicking on the Monitor in the Link column in the IMA Link Table area, the screen in
Figure 153 opens.
N.B. The Administrative Status must be set to Up in the ATM Layer tab-panel.

Figure 153. IMA Link Monitoring
This screen is a read-only screen in which all the parameters regarding the E1 link are shown.
N.B. By clicking on the IMA Group Monitoring the screen in Figure 154 opens.
Figure 154. IMA Group Monitoring
This screen is a read-only screen in which all the parameters regarding the IMA group are shown.

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

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

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

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

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

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

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

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

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

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

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

3.15 Core-E view for Core-E and ETHERNET DOMAIN (this menu opens
with double click on a Core-E unit)
3.15.1 Core-E domain

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

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

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

Admit tagged only (only tagged frames are allowed in ingress)
Admit all (tagged and untagged frames are allowed in ingress)
Default value: Admit all.

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

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

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

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

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

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

The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as
Admit tagged only, are dropped.
The priority packets (VLAN-ID=0) received on one user Ethernet port, with the "Admit
all" configuration enabled, are managed as untagged frames for VLAN-ID field, while
the Priority field is the same of the received packets".
Alarm Profile (not implemented);
Synchronous Ethernet Operation Mode
From the optical Ethernet traffic interface it is possible to recover the physical Rx synchronization
signal. This feature is needed in order to realize "synchronous Ethernet Networks" addressed by
G.8261.
Enable the Synch-E mode by setting Synchronous.

3.15.1.2 TMN Interface
This tab-panel refers to the TMN Interface. The interfaces are of two types:
1) TMN Ethernet on a dedicated connector
2) Port #4 of the Ethernet traffic ports, which can be dedicated to TMN purpose and not to traffic.
This tab-panel has 2 tab-panels:
Alarm tab-panel
Settings tab-panel
Alarms tab-panel
Alarm view shows the Ethernet ports-related alarms. Selecting the node in Tree area allows checking
Ethernet tributary alarms current state.

Settings tab-panel for TMN Ethernet port
If used, the TMN Ethernet must be:
Enabled.
Assigned an IP address with its IP mask.
Selected the IP Routing Protocol: Static Routing or OSPF. If OSPF has been selected, assign also
the area number.
Click on Apply to activate the selections.
Settings tab-panel for Port #4 TMN Ethernet
If the Ethernet Port 4 has been used as TMN port, the port 4 must be:
Enabled.
Assigned an IP address with its IP mask.
Selected the IP Routing Protocol: Static Routing or OSPF. If OSPF has been selected, assign also
the area number.
Click on Apply to activate the selections.

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

There are two types of external points: input and output external points.
By clicking on the tree root, displayed in Figure 164, the tree will be expanded.
A single left click selection of a tree element causes the activation of the corresponding Tabular repre-
sentation displayed in the "Resource list area" (upper right side of the screen).
A click on a row in the Resource list area opens the Settings menu.

3.16.2.1 Input External Points
An input external point is described by the following parameters (Figure below):
Id: identification number
UserLabel: associates a user-friendly name to an external point
Polarity: describes the polarity (Active Low/ Active High)
External State: describes the state (on /off)
Alarm Profile: describes the associated Alarm Profile (not implemented)
After a row selection, the user can modify the User Label, the Polarity.
The operator choices will be sent to NE after selecting the "Apply" button.
Figure 164. Input External Point View
3.16.2.2 Output External Points
Seven output external points are available.
The output external points (CPO#1 ... 7) are described by the following parameters:
Id: identification number
UserLabel: a user friendly name can be associated to an external point

Polarity: describes the polarity (Active Low/ Active High). In this field the polarity of the external
point can be changed.
Criteria: fixed to Manual. (The output can be activated manually). Note: the Automatic mode
is not supported in this release.
External State: describes the state (on /off). In this field the external point can be activated (on)
or deactivated (off).
The operator choices will be sent to NE by clicking on the "Apply" button.
Figure 165. Output External Points View

3.17 Performance Monitoring tool
To open the Performance Monitoring tool click on the relevant icon in the Menu bar as shown in the next
figure.
Performance Monitoring
tool icon
The Performance Monitoring tool allows to display all the performances available on the units of MPR:
Core-E unit (par. 3.17.1 on page 294)
MD300 unit (par. 3.17.2 on page 299)
P32E1DS1 unit (par. 3.17.3 on page 314)
A16E1DS1 (ASAP) unit (par. 3.17.4 on page 329)
The welcome screen of the Performance Monitoring screen is shown in Figure 166.
The Performance Monitoring tool can be used for different NEs. In the left column will be present all the
NEs. In the example only one NE is present (151.98.96.117).
Figure 166. Performance Monitoring tool welcome screen

By clicking on a specific unit will appear the performances available with the selected unit.
Tool bar:
Start Reset Export Help
Stop Refresh Print
Figure 167. Tool bar
3.17.1 Core-E unit performances

Two groups of Performance Monitoring are available:
Ethernet Aggregate Rx Table (incoming side)
Ethernet Aggregate Tx Table (outgoing side)
3.17.1.1 Ethernet Aggregate Rx Table
To activate the Rx performances (Incoming side):
[1] Select the Ethernet Aggregate Rx Table row as shown in the next figure.
[2] Select the Interval (the collection time of the performances): 4, 6, 30, 60 seconds. The default value
is 4 sec.
[3] Select the Duration of the performance monitor in hour and minutes. The max. duration is 24 hours.
[4] Click on the Start button to start the monitoring.

3 2
Figure 168. Ethernet Aggregate Rx Table
To display the performance monitor select the suitable port, as shown in the next figure (port #2 in the
example).
Figure 169. Ethernet Aggregate Rx Table display (at port level)

The available performances at port level are:
TRCO: total number of octects of Ethernet frames received by the Virtual Ethernet Interface,
including Ethernet header characters.
TRCF: total number of Ethernet frames received by the Virtual Ethernet Interface.
TRSEF: total number of errored frames.
TDF: total number of Ethernet frames which were chosen to be discarded due to buffer congestion.
TRCF Unicast: total number of Ethernet Unicast frames received correctly by the Virtual Ethernet
Interface.
TRCF Multicast: total number of good packets received that were directed to a multicast address.
This number does not include packets directed to the broadcast address.
TRCF Broadcast: total number of good packets received that were directed to the broadcast
address. This number does not include multicast packets.
The performances are displayed in two different formats:
graphical format in the lower part
tabular format in the upper part
In the graphical format by putting a check mark on the check box only one (or more than one or all)
performance can be displayed.
By selecting the Ethernet Aggregate Rx Table (as shown in the next figure) all the performances regarding
all the enabled Ethernet ports are shown in tabular format.
Figure 170. Ethernet Aggregate Rx Table display (all enabled ports)

3.17.1.2 Ethernet Aggregate Tx Table
To activate the Tx performances (Outgoing side):
[1] Select the Ethernet Aggregate Tx Table row as shown in the next figure.
is 4 sec.
3 2
Figure 171. Ethernet Aggregate Tx Table
To display the performance monitor select the suitable port, as shown in the next figure (port #2 in the
example).

Figure 172. Ethernet Aggregate Tx Table display (at port level)
The available performances at port level are:
TTO: total number of octets of Ethernet frames transmitted out by the Interface, including Ethernet
header characters.
TTF: total number of Ethernet frames transmitted out by the interface.
TDF: total number of Transmitted Ethernet frames which were chosen to be discarded due to buffer
congestion.
TRCF Unicast: total number of Ethernet Unicast frames transmitted out by the Virtual Ethernet
Interface.
TRCF Multicast: total number of good packets transmitted by this address that were directed to a
multicast address. This number does not include packets directed to the broadcast address.
TRCF Broadcast: total number of good packets transmitted by this address that were directed to the
broadcast address.
By selecting the Ethernet Aggregate Tx Table (as shown in the next figure) all the performances regarding
all the enabled Ethernet ports are shown in tabular format.

Figure 173. Ethernet Aggregate Tx Table display (all enabled ports)
3.17.2 MD300 unit performances

By selecting the MD300 unit the screen in Figure 174. opens.
Figure 174. MD300 unit performance screen

The performance monitoring (PM) gives indication on the quality of service of the radio system.
Quality of service Performance Monitoring is performed in accordance with G.826 and G.784.
It has assumed that the quality of the single tributary (E1, ...) can be derived from the quality of the aggre-
gate signal, therefore no dedicated quality of service Performance Monitoring is foreseen on the single
tributaries.
Considering one section (see below), one current register is for 15 min report and one for 24 h report; 96
history data can be stored for 15 min report and 8 history data for 24 h report.
Note
The 15 min Performance Monitoring data are stored in the History Data
report only if errors have been occurred.
The 24 h Performance Monitoring data are always stored in the History Data report.
Two different radio sections can be monitored:
Radio Hop Section: section between two radio stations inside the protection section.
Radio Link Section: section identifying the protected section.
Figure 175. Radio sections
The counters supported are the following:
Errored Seconds
Severely Errored Seconds
Background Block Error
Unavailable Seconds
The performance reports can be of 2 different types:
15 minutes
24 hours
The following description explains the functions to provide the Performance Monitoring process with a
granularity period of 15 min. The same functions are provided for 24h Performance Monitoring process.
The Performance Monitoring are of HOP or LINK type.
HOP refer to Performance Monitoring before the RPS switch.

LINK refer to Performance Monitoring after the RPS switch. The current report can be seen (and config-
ured) and the history log can be seen.
3.17.2.1 Current Data Table
To see (and configure) the Current Data report:
[1] Click on the desired granularity (15 m or 24 h) on the Current Data Table below the HOP channel
(0 or 1) (in 1+0 configuration channel 1 only) to see the HOP report or below the LINK to see the LINK
report. Refer to the next figure.
[2] Click on the Start button in the Tool bar.
Figure 176. Current Data Table (15 Min)
Refer to Figure 177. to see an example of the Current Data display and to Figure 178. to see the Alarm
Data tab panel to see the alarms regarding the performances, if any.

Figure 177. Current Data Table (15 Min) display
Figure 178. Alarm Data Table (15 Min)

3.17.2.1.1 CD parameters
The fields displayed in the Current Data tab-panel allow the operator to check and manage the parameter
of the current data collection.
Elapsed Time field (read-only) displays the elapsed time in the current interval of monitoring.
Last Update: display time of the Performance Monitoring in the graphical description and in the tab-
ular description. This time changes after the Auto Refresh.
Max Interval supp.: max. number of intervals (reports) which can be suppressed in the History
because they dont have errors.
Num. Interval supp.: number of intervals (reports) suppressed in the History because they dont
have errors.
Suspect interval shows whether the current data are suspect or not (Note).
Note
An interval is defined as suspect if at least one of the following conditions occurs in the collection period:
- the elapsed time deviates more than 10 seconds of the nominal time
- loss of the Performance Monitoring data in the equipment
- performance counters have been reset during the interval.
3.17.2.1.2 CD counters
BBE (Background Block Errors)
ES (Errored Second)
SES (Severely Errored Second)
UAS (Unavailable Second).
Note
These values refer to the last refresh performed with the Auto Refresh.
3.17.2.2 History Data Table
To see an History Data report:
[1] Click on the desired granularity (15 m or 24 h) on the History Data Table below the HOP channel (0
or 1) (in 1+0 configuration channel 1 only) to see the HOP report or click on LINK to see the LINK
report
Refer to Figure 179. to open the History Data Table.

Figure 179. History Data Table (15 Min)
The Performance Monitoring process monitors the parameters during a specified interval (i.e. 15min) and
stores their values in history data. A History Data collection is created automatically at the end of each
time interval of Current Data.
Note: Use the arrows Right and Left in the lower part to pass from one log to another log in the history.
3.17.2.2.1 HD Counters
ES (Errored Second)
3.17.2.3 Threshold tables
This section describes how to display or change or create the threshold tables assigned to Performance
Monitoring counters.
To view the available threshold for Performance Monitoring process, the operator must select the Thresh-
olds Tables node tree.
There are threshold tables for the HOP and for the LINK.
There are two default threshold tables for HOP: Threshold #1 (to be associated to 15 min report) and
Threshold #4 (to be associated to 24 h report).

There are two default threshold tables for LINK: Threshold #1 (to be associated to 15 min report) and
3.17.2.3.1 How to create a new threshold table
Note: Four threshold tables can be created for the HOP (Threshold #2, #3, #5 and #6).
Two threshold tables can be created for the LINK (Threshold #2 and #4).
To create a new threshold table:
[1] Click on Threshold Tables HOP (or LINK) node tree.

The Threshold Data Creation screen will appear, as shown in the next figure (Hop threshold).
[2] Write the values for the Low and High thresholds.
[3] Click on Create. Automatically the new threshold takes a name with a progressive number.
Figure 180. Threshold creation

3.17.2.3.2 How to change/delete a threshold table
Note: Only the created thresholds can be modified or deleted. The default thresholds can be only dis-
played.
[1] Click on the Threshold to be modified in Threshold node tree (Threshold #3 in the example of the
next figure).
Figure 181. Threshold change
[2] Low and high thresholds for each counter are shown. Edit the new values in the table fields to change
them.
[3] Click on the Apply button to confirm the changes or click on the Delete button to delete the threshold.
3.17.2.4 Threshold table association
To each Performance Monitoring can be associated a Threshold Table.
To associate a Threshold Table click on Current Data Table or History Data Table of HOP-Channel#0 (or
Channel#1) or of LINK. The 15min&24h tab panel will appear.

Figure 182. Threshold association
In the Counter Thresholds field select the threshold to be associated and click on Apply.
3.17.2.5 Adaptive Modulation performance
If the Adaptive Modulation has been enabled in the Modem unit, in the Performance Monitoring tool will
appear also the performances regarding the Adaptive Modulation: these performances show the time dur-
ing which a specific modulation scheme has been active.
To activate the Adaptive Modulation performance:
[1] Click on the desired granularity (15 m or 24 h) on the Current Data Table below the HOP channel
(0 or 1) (in 1+0 configuration channel 1 only) to see the HOP report or below the LINK to see the LINK
report. Refer to the next figure.

Figure 183. Adaptive Modulation performances
Next Figure 184. shows a display of Current Data report (15 min).
The Scale of the diagram can be changed by simply selecting the portion of the chart.
Figure 184. Current Data Table (15 min)

Next Figure 185. shows a display of History Data report (15 min).
Figure 185. History Data Table (15 min)
3.17.2.6 Ethernet Aggregate Tx Table
To activate the Tx performances (Outgoing side):
[1] Select the Ethernet Aggregate Tx Table row as shown in the next figure.
is 4 sec.

3 2
Figure 186. Ethernet Aggregate Tx Table
Refer to next figure to see the performances.
Figure 187. Ethernet Aggregate Tx Table Performance display

The available performances at output Tx radio port are:
TTO: total number of octets of Ethernet frames transmitted out by the Interface, including Ethernet
header characters.
TTF: total number of Ethernet frames transmitted out by the interface.
TDF: total number of Transmitted Ethernet frames which were chosen to be discarded due to buffer
congestion.

3.17.2.7 Ethernet Aggregate Per Queue
The MD300 unit has 8 output queues.

Queue 8 is reserved to TDM2TDM traffic.
Queue 7 is reserved to TDM2Eth traffic.
Queue 6 is reserved to TMN traffic.
The remaining 5 queues are reserved to Ethernet traffic. Queue 5 is the highest priority queue.
To activate the Ethernet Aggregate Per Queue performances (Outgoing radio side):
[1] Select the Ethernet Aggregate Per Queue row as shown in the next figure.
is 4 sec.

3 2
Figure 188. Ethernet Aggregate Per Queue
To display the performance monitor select the suitable queue, as shown in the next figure (Queue #1 in
the example).
Figure 189. Ethernet Aggregate Per Queue (Queue #01)

The available performances at queue level (for each queue) are:
TCF: total number of Ethernet conforming frames accepted and transmitted out by the specific queue
of the interface.
Discard TCF: total number of Discarded Ethernet conforming frames accepted by the specific queue
of the interface.
TCO: total number of Ethernet conforming octects accepted and transmitted out by the specific
queue of the interface.

In the graphical format by putting a check mark on the check box only one (or more or all) performance
can be displayed.
By selecting the Ethernet Aggregate Per Queue row (as shown in the next figure) all the performances
regarding all the queues are shown in tabular format.
Figure 190. Ethernet Aggregate Per Queue (all queues)

3.17.3 P32E1DS1 unit performances
By selecting the P32E1DS1 unit the screen in Figure 191 opens.
Figure 191. P32E1DS1 unit performance screen
The performance monitoring (PM) gives indication on the quality of the E1 streams, which have been con-
figured as "Framed".
In Figure 191 the E1 streams, configured as "Framed" are shown in bold; for all the other E1 streams (in
grey) the performance are not available because the relevant streams are disabled or they have been con-
figured as "Unframed".
Two types of performances are available:
Incoming: these performances are detected at the input in Tx side.
Outgoing: these performances are detected at the output in Rx side.
Note: 9500MPR is transparent regarding the E1 stream. The CRC is used to detect the quality of the E1
stream; it is never changed.
The Quality is performed in accordance with G.826 and G.784.
The performance reports are of 2 different types:
15 minutes
24 hours
One current register is for 15 min report and one for 24 h report; 96 history data can be stored for 15 min
report and 8 history data for 24 h report.

Note: The 15 min Performance Monitoring data are stored in the History Data report only if errors have
been occurred. The 24 h Performance Monitoring data are always stored in the History Data report.
Note: For a better quality in the Performance Monitoring it is recommended to start up to 128 E1 PM
counters on the same NE. This means 4 counters (Incoming 15 Minutes, Incoming 24 hours, Outgoing
15 Minutes and Outgoing 24 Hours) for 32 E1 streams.
Note: Stability measurement on Ethernet counters (with duration from few hours to 24 Hours) should be
performed by selecting an high value (60 seconds) as collection time of the performances (refer to param-
eter Interval in Ethernet Aggregate Tx Table section).
The following description explains the functions to provide the Performance Monitoring process with a
granularity period of 15 min. The same functions are provided for 24h Performance Monitoring process.
3.17.3.1 Incoming (Current Data Table)
[1] Click on the desired granularity (15 m or 24 h) on the Current Data Table. Refer to the next figure.
[3] Click on Refresh button to update the collection.
Refer to Figure 193 to see an example of the Current Data display and to Figure 194 to see the Alarm


have errors.
Note: An interval is defined as Suspect if at least one of the following conditions occurs in the collection
period:
the elapsed time deviates more than 10 seconds of the nominal time
loss of the Performance Monitoring data in the equipment
performance counters have been reset during the interval.
ES (Errored Second)
Note: These values refer to the last refresh performed with the Refresh button in the Tool bar.
3.17.3.2 Incoming (History Data Table)
1) Click on the desired granularity (15 m or 24 h) on the History Data Table.
Refer to Figure 195 to open the History Data Table.

ES (Errored Second)

3.17.3.3 Outgoing (Current Data Table)
[1] Click on the desired granularity (15 m or 24 h) on the Current Data Table. Refer to the next figure.
[3] Click on Refresh button to update the collection.
Refer to Figure 197 to see an example of the Current Data display and to Figure 198 to see the Alarm


have errors.
Note: An interval is defined as Suspect if at least one of the following conditions occurs in the collection
period:
the elapsed time deviates more than 10 seconds of the nominal time
loss of the Performance Monitoring data in the equipment
performance counters have been reset during the interval.
ES (Errored Second)
Note: These values refer to the last refresh performed with the Refresh button in the Tool bar.
3.17.3.4 Outgoing (History Data Table)
1) Click on the desired granularity (15 m or 24 h) on the History Data Table.
Refer to Figure 199 to open the History Data Table.

ES (Errored Second)
Note: How to Start/Stop the perfomance monitoring for a selected E1 in one-shot.
[1] Click on PDH. The One-Shot Start/Stop PM panel will appear.
2) Select the E1 Port #.
3) Select the Signal type.
4) Select the Interval type.

5) Click on Start.
Figure 200. One-Shot Start/Stop the PM
3.17.3.4.2 Threshold tables
This section describes how to display or change or create the threshold tables assigned to Performance
Monitoring counters.
To view the available threshold for Performance Monitoring process, the operator must select the Thresh-
olds Tables node tree, as shown in Figure 201.
There are two default threshold tables:
Threshold #1 (to be associated to 15 min report)

3.17.3.4.3 How to create a new threshold table
Note: Four threshold tables can be created (Threshold #2, #3 for 15 min report and #5 and #6 for 24 h
report).
To create a new threshold table:
[1] Click on the Threshold Tables. The Threshold Data Creation screen will appear, as shown in the next
figure.
[2] Write the values for the Low and High thresholds.
[3] Click on Create. Automatically the new threshold takes a name with a progressive number.
Figure 201. Threshold creation
3.17.3.4.4 How to change/delete a threshold table
Note: Only the created thresholds can be modified or deleted. The default thresholds can be only dis-
played.
[1] Click on the Threshold to be modified in Threshold node tree (Threshold #2 in the example of the
next figure).

Figure 202. Threshold change
[2] Low and high thresholds for each counter are shown. Edit the new values in the table fields to change
them.
[3] Click on the Apply button to confirm the changes or click on the Delete button to delete the threshold.
3.17.3.5 Threshold table association
To each Performance Monitoring can be associated a Threshold Table.
To associate a Threshold Table to an E1 stream three methods can be used:
[1] One-Shot Threshold association (from E1 threshold): with this method the same Threshold Table is
applied in one shot for the selected E1 streams, to Incoming, Outgoing or both.
[2] Specific E1 Port # association: with this method a Threshold Table is applied only to a specific E1
stream, Incoming and Outgoing.
[3] Specific E1 Port # Incoming or Outgoing: with this method a Threshold Table is applied only to a spe-
cific E1 stream, Incoming or Outgoing.

3.17.3.6 One-Shot Threshold association (from E1 Threshold)
To associate a Threshold Table:
[1] Click on E1 Threshold. The One-Shot Threshold Apply panel will appear.
[2] Select the E1 Port #.
[3] Select the the threshold to be associated to the 15min and/or 24h performance interval.
[4] Click on Apply.
Figure 203. One-Shot Threshold association (from E1 threshold)
3.17.3.7 Specific E1 Port # association
[1] Click on the E1 Port #. The 15min&24h tab panel will appear.
[2] In the Counter Thresholds field select the threshold to be associated and click on Apply.

Figure 204. Threshold association (Incoming and Outgoing)
3.17.3.8 Specific E1 Port # Incoming or Outgoing
[1] Click on the E1 Port #. The 15min&24h tab panel will appear.
[2] In the Counter Thresholds field select the threshold to be associated and click on Apply.

Figure 205. Threshold association (Incoming)
Figure 206. Threshold association (Outgoing)

3.17.4 A16E1DS1 (ASAP) unit performances
Two groups of Performance Monitoring are available:
IMA Group (par. 3.17.4.1 on page 329)
ATM Interface (par. 3.17.4.2 on page 332)
Figure 207. A16E1DS1 (ASAP) unit performance screen
N.B. To have the correct time for the PM counters set the NE time as the OS time.
3.17.4.1 IMA Group Monitoring
The quality of IMA Group and Links is evaluated by monitoring IMA Group and Link Counters. This mon-
itoring is based on IMA standard.
3.17.4.1.1 IMA Group Statistics
Select the IMA Group as shown in Figure 208 (GroupID#1 has been selected).

Figure 208. IMA Group Statistics
For each configured and active IMA Group the following counters are available:
Unavailable Seconds: counter of the seconds where the IMA group traffic state machine is down.
Near-End group failure: counter of the number of times a failure alarm condition (Config-
Aborted,Insufficient-Links, Config-Aborted-FE, Insufficient-Links-FE, Blocked-FE) has been
reported for Near-End IMA Group.
3.17.4.1.2 IMA Link Statistics
Select the IMA Link as shown in Figure 209 (LinkID#1 has been selected).

Figure 209. IMA Link Statistics
For each active IMA link, belonging to an activated IMA Group, the following counters are available:
IMA Violation: counter of errored, invalid or missing ICP cells, except during SES-IMA or UAS-IMA
conditions;
OIF (Out of IMA Frame) anomalies: counter of OIF anomalies, except during SES-IMA or UAS-IMA
conditions;
SES (Severly Errored Seconds): counter of one second intervals containing more then 30% of the
ICP cells counted as IMA Violation, or one or more link defects (e.g., LOS,OOF/LOF, AIS, or LCD),
LIF defects, or LODS defects, except during UAS-IMA condition, for Near-End side;
UAS (UnAvailable Seconds): counter of the seconds unavailability beginning at the onset of 10
contiguous SES-IMA and ends at the onset of 10 contiguous seconds with no SES-IMA, for Near-
End side;
UUS (UnUsable Seconds): counter of unusable seconds declared by the Link State Machine at TX
and RX directions for Near-End side;
NE failure: counter of the number of times a failure alarm condition has been entered on this link
at TX and RX directions for Near-End side.

3.17.4.2 ATM Interface Monitoring
The quality of ATM PW Service is evaluated by monitoring the ATM interface and VP/VC cell counters.
3.17.4.2.1 ATM Interface Statistics Monitoring
Select the ATM Interface as shown in Figure 210 (Interface ATM#1 has been selected).
Figure 210. ATM Interface Statistics Monitoring
For each configured and active ATM interface the following counters are available:
Usage Rx Cells: counter of the number of cells received on the ATM interface.
Usage Tx Cells: counter of the number of cells transmitted on the ATM interface.
Invalid Header Discarded Cells: counter of the number of cells discarded because of Invalid
Header, invalid VPI or invalid VCI.
3.17.4.2.2 ATM VP/VC Statistics Monitoring
Select the VP as shown in Figure 211 (VPLID#2 has been selected) or the VC as shown in Figure 212
(VCLID#37 in VPLID#1 has been selected).

Figure 211. ATM VP Statistics Monitoring
Figure 212. ATM VC Statistics Monitoring

For each active VP, if configured as Termination end-point, and active VC configured over an active ATM
interface, the following counters are available:
Discarded Cells: counter of the total number of valid VP/VC cells discarded by the traffic policing
entity. This includes cells originally received with CLP=0 and CLP=1.
Discarded CLP0 Cells: counter of the total number of valid VP/VC cells received with CLP=0 and
discarded by the traffic policing entity.
Tagged Cells: counter of the total number of valid VP/VC cells tagged by the traffic policing entity
from CLP=0 to CLP=1 and transmitted.
Rx Cells: counter of the total number of valid VP/VC cells received including both CLP=0 and CLP=1
cells. The cells are counted prior to the application of the traffic policing.
Tx Cells: counter of the total number of valid VP/VC cells transmitted including both CLP=0 and
CLP=1 cells. The cells are counted prior to the application of the traffic policing.
Rx CLP0 Cells: counter of the number of valid VP/VC cells received with CLP=0. The cells are
counted prior to the application of the traffic policing.
Tx CLP0 Cells: counter of the number of valid VP/VC cells transmitted with CLP=0. The cells are
counted prior to the application of the traffic policing.

3.18 VLAN management
Two different ways to manage the Ethernet traffic are allowed:
802.1D (MAC Address Bridge)
802.1Q (Virtual Bridge)
3.18.1 802.1D
When the NE is configured in this mode (default configuration), the Ethernet traffic is switched according
to the destination MAC address without looking the VLAN.
The packets from the user Ethernet ports having the VLAN ID out the allowed range (0 and 2-4080) are
dropped. The packets having a VLAN ID already used for a TDM flow are accepted.
Figure 213. 802.1D VLAN management

3.18.2 802.1Q
When the NE is configured in this mode, the management of Ethernet traffic looking the VLAN is enabled.
In this modality, one VLAN will be assigned to all Ethernet frames inside the MPR network.
WARNING: The VLAN ID values configurable must be in the range 2 - 4080. The VLAN IDs already
defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) cannot be used. The management
system prohibits the definition of VLAN ID already used. The VLAN ID must be different also from the Flow
Id associated to E1 tributaries not yet cross connected
Figure 214. 802.1Q VLAN management (default VLAN only)
VLAN 1 Management
VLAN-ID 1 is automatically defined by the NE when the 802.1Q bridge type is selected.
VLAN-ID 1 is shown to the operator, but it cannot be neither changed nor deleted.
All the user Ethernet ports (enabled and disabled) and all the radio ports are members of the VLAN 1.
In egress VLAN-ID 1 is always removed from all the ports.
Buttons
New: to create a new VLAN (refer to VLAN table management)
Edit: to change the parameters of a VLAN (VLAN name, VLAN member ports, VLAN untagged ports
in egress).

Delete: to delete a VLAN-ID. It is possible to remove a VLAN-ID from the VLAN-ID table even if this
VLAN-ID has been already configured on one or more user ports as Port VLAN to be added in ingress
to untagged frames. As consequence, the VLAN-ID=1 and PRI=0 are added to the untagged frames
received on this port. Before applying this deletion, a confirmation of the operation is shown to the
operator.
Export: to export the VLAN configuration in a file with extension CSV. The file can be stored in the
PC to be read later.
Filter: by inserting a name in the "Filter by Name" box and by clicking on Filter will be displayed in
the table only the VLAN, which name corresponds (totally or partially) to the name written in the "Filter
by Name" box.
Clear Filter: by clicking this button all the VLAN created in VLAN table will again appear.
Refresh: the VLAN table is updated.
3.18.2.1 VLAN Table Management
1
2
3 4
Figure 215. VLAN Table Management
[1] VLAN ID field: Enter the VLAN ID (the values configurable must be in the range 2 - 4080)
Warning: The VLAN IDs already defined as Flow Id to identify the E1 streams for the cross-con-
nections (i.e. TDM2TDM, TDM2ETH) cannot be used.
[2] VLAN Name field: Enter the VLAN Name: a text string of up to 32 characters.
N.B. There is no check on unambiguity name.
[3] VLAN Ports field: Select the ports members of this VLAN by putting a check mark on the relevant
check box. All the user Ethernet ports and all the Radio directions can be considered. Both enabled
and disabled user Ethernet ports (radio ports when declared are implicitly enabled) can be member
of a VLAN. This means that a disabled port can be configured as a member of a VLAN and a port
already member of a VLAN can be disabled continuing to be a member of the same VLAN.

[4] Untagged Ports field: Select, among the ports belonging to this VLAN (members), the untagged
ports (in egress the VLAN will be removed from the frames). Only the user Ethernet ports, enabled
and disabled, are manageable. The VLAN cannot be removed from the radio ports (with the excep-
tion of the VLAN 1).
N.B. The VLAN-ID values allowed are in the range 2 - 4080. By default, for the VLAN IDs defined,
all the ports are members and the Untag flag is set to False, which means all the frames are
transmitted with Tag.
N.B. Tagged frames

If one tagged packet with VLAN-ID X is received on a port which is not member of the VLAN-
ID X, the packet is dropped.
In the following figure three VLANs have been created (VLAN 2, 3 and 4).
Figure 216. 802.1Q VLAN management
N.B. When an ODU300 port which is member of a VLAN, is unconfigured, the operation is denied
stating that "Operation not permitted: the board <board no> is member of a static VLAN". To
unconfigure this board, the user must first navigate to VLAN Configuration window and remove
this port from the static VLAN.

4 Installation
4.1 Hardware Installation

4.1.1 - Power consumption on page 339
4.1.2 - Rack Installation on page 340
4.1.3 - ODU300 Installation on page 354
4.1.4 - Indoor Installation on page 375
4.1.5 - Antenna Alignment on page 420
4.1.1 Power consumption
Part Max. Power Consumption Typical Power Consumption
Core-E 22 W 19 W
MODEM ACCESS CARD 23 W 23 W
32 E1 PDH ACCESS CARD 12 W 10 W
16 E1 ASAP CARD 22 W
AUX PERIPHERAL CARD 10 W
FAN 10 W 8W
ODU300 45 W for ODUs < 15 GHz

30 W for ODUs > 15 GHz
Note
Figures are for normal (not start-up) operation.

Installation 3DB 18528 DIAA Issue 1 339/578
4.1.2 Rack Installation
4.1.2.1 General
Indoor units (IDU) of the 9500 MPR-E system can be installed in 3 different ways:
"ETSI (WTD) rack (21") (see par. 4.1.2.2 on page 340)
"North American standard rack (19") (par. 4.1.2.3 on page 345)
The equipment can also be installed on the wall (par. 4.1.2.5 on page 348)
For each of the above type of installation special mechanical supporting fixtures are available.
Special mechanical fittings are provided for this type of installation, depending to the width of rack (19"
or 21"). The examples show the fittings used to insert the equipment in ETSI racks (21"). For installation
in 19" DIN racks the adaptors must be changed.
4.1.2.2 ETSI Rack Installation
4.1.2.2.1 Mechanical Installation
Installation has been sub-divided into the following phases:
Rack Positioning and Fastening
Fixing the rack to floor using expansion bolts or Fixing to floating floor;
T.R.U. fastening to WTD rack.
4.1.2.2.2 Rack Positioning and fastening
Proceed as follows:
Refer to the plant documentation to see rack row assignment
Fasten the rack to the station structure according to one of the following procedures
Fixing the rack to floor
Fixing the rack to floating floor
4.1.2.2.3 Fixing the rack to floor using expansion bolts
(Refer to Figure 217. and Figure 218.).
Mount the rack in a vertical position in the desired place.
Mark the base-plate with six holes (1) to be drilled on the floor.
Temporarily remove the rack and drill the holes at the points drawn on the floor. Place the inserts into
the holes.
Secure the expander bolts to the floor through the base-plate holes.

340/578 3DB 18528 DIAA Issue 1 Installation
Figure 217. Fixing the Rack to Floor (1)

Figure 218. Fixing the Rack to Floor (2)

4.1.2.2.4 Fixing to floating floor
(Refer to Figure 219. and Figure 220.).
The drilling mask is the same used for concrete floor fastening.
In this case a hole must be created for the cables coming from the bottom according to Figure 219.
The rack fastening is to be mounted on the concrete floor below using a suitable stud as shown in Figure
219.
Using the row layout drawing, mark out the cable entry areas in the floor tiles and cut out with a jigsaw.
Remember that the beginning of the row must be approved by the customer.
N.B. Unused or incompletely used cable entry areas should be blocked off with foam rubber.
Figure 219. Floor file drilling template

Figure 220. Example of securing rack assembly to computer floor

4.1.2.3 Laborack (19") installation
Figure 221. Laborack
The Laborack must be fixed to the floor by means of the four (4) screws.
(For more information see the manufacturer instructions).
When you have correctly positioned the fixing brackets on the 19" unit, the front panel will hold the
equipment by four screws fitted into the laborack cage nuts.
Fasten the IDU to the rack by inserting screws into holes of 19" mechanical adaptors and by screwing them
into relevant holes provided with nut cage situated on rack brackets.

4.1.2.4 Subrack Installation
Figure 222. MSS-8 Subrack
Figure 223. MSS-4 Subrack

Figure 224. Fixed Subrack with screw
Figure 225. Subrack grounding point (bracket on the right side)
The subrack must be grounded using the ground screw present on the front panel of the bracket on the
right side.
The section cable (wire) to use must be a 1x6 mm (9AWG) (Yellow/Green).
The subrack-mounting item adds a good electrical connection to rack ground.

4.1.2.5 Wall Mounting Installation
The IDU wall mounting kit (3CC50027AAAA) can be used for wall installation and it can support a
maximum of three units.
The kit includes:
Two brackets
Four fixing for the brackets
M6x50 socket cap screws
Onduflex washers
Expansion bolt
The mechanical support is 10 U high.
Figure 226. Mechanical Support (Two brackets)
Figure 227. Installation kit to fix the mechanical support

Figure 228. MSS 8 Fixed on wall mounting
The mechanical support must be grounded using the Grounding Kit 3CC13423AAAA.
4.1.2.6 Top Rack Unit
The Top Rack Unit (T.R.U.) fastening to the rack guarantees the connection to the protection ground in
that the rack is wired to the station protection ground.
Figure 229. Top Rack Unit (T.R.U.)
The T.R.U. is positioned on the top of the Rack and it is use to provide the Power Supply to the equipment.
Figure 230. Top Rack Unit - Front/Rear
The T.R.U. is fixed to the rack by means two (2) screws.
Figure 231. Top Rack Unit - Fixed to rack

4.1.2.6.1 Top Rack Unit Components
Description Component Q.ty Particular View
Terminal Block 16mm 2
Thermal Magnetic Circuit Breaker Unipolar 6
Bus Bar Supply to 12 Fuse Carrier 1
Screws M6x16 with plastic Washer 4
Natched Clamp Nuts M6 4
Rail + Front 19" 1

4.1.2.6.2 Top Rack Unit Connections
The photo's below show the connections from IDU to T.R.U.
Figure 232. TRU Connections
4.1.2.6.3 Top Rack Unit Grounding
The rack must be grounded by means of a connection to the protection ground terminal of the site
electrical plant.
The rack must be connected to the protection ground before performing any other electrical connection.
Figure 233. TRU Grounding position on Laborack
The rack is grounded to the station through a 16 to 25 mm2 (1 to 2 AWG) section cable (1) terminated
onto the cable terminal lug (2).

Figure 234. ETSI Rack - Ground connection
Figure 235. Laborack - Ground connection
4.1.2.6.4 Power Supply Cable
Two solutions of the Power Supply cable can be provided as shown in Figure 236.
Figure 236. 2W2C Connector and Cable (3DB18271AAXX)

Figure 237. Battery Access Card on subrack
A power cable is supplied in the IDU Installation Kit, which has a 2-pin 2W2C fitted at one end and wire
at the other. The cable is nominally 4 m, and the wires are 4 mm2 (AWG 12). The blue wire must be
connected to -48 Vdc (live); the black wire to ground/+ve.
Note
The 2W2C DC power connector can be shorted inadvertently if applied at an angle.

Always insert with correct alignment.
For WTD rack the TRU doesn't require any cable ground connection to the rack.

4.1.3 ODU300 Installation
This section describes the following installation procedures:
Installing the Antenna (par. 4.1.3.1 on page 354)
Installing the ODU (par. 4.1.3.2 on page 355)
Installing a Coupler (par. 4.1.3.3 on page 366)
Installing ODU Cables and Connectors (par. 4.1.3.4 on page 370)
Weatherproofing (par. 4.1.3.5 on page 373)
The ODU300 has an internal Lightning Surge Suppressor.
The figure shows on the left side the yellow sticker meaning the presence of the internal Lightning Surge
Suppressor.
Figure 238. ODU (with the internal Lightning Surge Suppressor)
4.1.3.1 Installing the Antenna
Antennas must be installed in accordance with the manufacturer's instructions.
For direct-mounted ODUs the antenna includes a collar with integral polarization rotator. Dependant
on frequency band, these antennas are available in diameters up to 1.8 m (6 ft).
Where standard antennas are to be used, the ODU must be installed on a remote-mount, and a flex-
ible waveguide used to connect to its antenna.
Before going to the site, check that you have the required installation tools as recommended by the
antenna manufacturer, and that you have data for positioning the antenna on the tower, its polarization
and initial pointing.
For direct-mounted ODUs, polarization is determined by the setting of the polarization rotator.
For standard antennas, polarization is determined by the orientation of the antenna.
Note
Unused or incompletely used cable entry areas should be blocked off with foam rubber.

4.1.3.2 Installing the ODU
The type is ODU300.
All ODUs are designed for direct-mounting to a collar supplied with direct-fit antennas.
All ODUs can also be installed with standard antennas using a flex-waveguide remote-mount kit.
For single-antenna protected operation a coupler is available to support direct mounting of the two ODUs
to its antenna, or to support direct mounting onto a remote-mounted coupler.
4.1.3.2.1 Direct-Mounted ODUs
4.1.3.2.1.1 Overview
The ODU is attached to its mounting collar using four mounting bolts, with captive 19 mm (3/4") nuts.
The ODU mounts directly to its antenna mount as shown below.
An ODU should be installed with its connectors facing down as shown below.
Figure 239. ODU and Mounting Collar

Figure 240. Andrew Pole Mount and ODU Mounting Collar
Figure 240. shows the ODU mounting collar, pole mounting polarization rotator for an Andrew antenna.
Figure 241. RFS Pole Mount and Mounting Collar
Figure 241. shows the ODU mounting collar, pole mounting, and polarization rotator for RFS antenna.
Figure 242. Precision Pole Mounting and ODU Mounting Collar
Figure 242. shows the ODU mounting collar, pole mount, and polarization rotator for a Precision antenna.

4.1.3.2.2 Setting the Polarization
The polarization of the transmitted signal, horizontal or vertical, is determined by the position of the
polarization rotator fitted within the ODU mounting collar. The ODU is then mounted on the collar to match
the chosen polarization. The rotator is an integral part of the antenna mount. Vertical polarization is the
default setting. If the rotator is not set for the required polarization, you must adjust its orientation. This
topic includes typical adjustment procedures for Radio Waves and Andrew antennas. Antenna installation
instructions are included with all antennas. These instructions include procedures for setting polarization.
4.1.3.2.2.1 Procedure for Andrew Rotator
To change the polarization of the Andrew antenna:
1) Release (do not completely undo) the six metric Allen-head screws approximately 10 mm (3/
8 inch). Pull the collar forward and hold the rotator back, which will allow the rotator to disengage
from a notch in the collar, and turn freely.
2) Turn the rotator hub 90 until it locates back into a notched "timing recess" in the collar.
3) Check that the timing mark on the rotator hub has aligned with either a V or an H on the collar
to confirm polarization. Refer to this photo.
4) Ensure the rotator hub is correctly seated within its collar, then push the collar back against the
antenna mount and re-tighten the six screws.
Figure 243. Andrew ODU Collar and Polarization Rotator

4.1.3.2.2.2 Procedure for RFS Rotator
The polarization rotator is fixed by two Allen-head bolts.
To change the polarization of the RFS antenna:
1) Loosen the bolts. Refer to Figure 244.
2) Rotate by 90.
3) Check bolt heads are located in the slot recesses.
4) Refasten.
Figure 244. RFS Rotator
Figure 244. shows a close-up of the polarization rotator being released from the vertical position (left) and
rotated clockwise towards horizontal (right).
4.1.3.2.2.3 ODU Polarization
The ODU must be mounted on the collar to match the chosen polarization.
Correct positioning for vertical or horizontal polarization is shown below.
Figure 245. ODU orientation for Vertical or Horizontal Polarization

4.1.3.2.3 Direct-Mount ODU Attachment Procedure
This topic describes the physical attachment of an ODU to an antenna mounting collar.
Related procedures are:
Grounding an ODU (par. 4.1.3.2.6 on page 365)
Installing the ODU cable and connectors (par. 4.1.3.4 on page 370)
4.1.3.2.3.1 Attaching the ODU
An ODU should be installed with connectors facing down.
To attach the ODU:
1) Check that the ODU mounting collar, polarization rotator, ODU waveguide feed head and O-
ring, are undamaged, clean, and dry.
2) Set the polarization rotator for the required polarization. Refer to par. 4.1.3.2.2 - Setting the
Polarization on page 357.
3) Apply a thin layer of silicon grease around the ODU feed-head O-ring.
A tube of silicon grease is included in the ODU installation kit.
4) Fully loosen the nuts on the four ODU mounting bolts.
5) Position the ODU so the waveguide slots (ODU and rotator) will be aligned when the ODU is
rotated to its end position.
6) Fit the ODU onto its mounting collar by inserting the bolts through receptor holes in the collar,
then rotate the ODU clockwise to bring the mounting bolts hard up against the slot ends.
7) Carefully bring the ODU forward to fully engage the ODU feed head with the polarization rotator.
8) Finger-tighten the four nuts, checking to ensure correct engagement of ODU with mounting col-
lar.
9) Ensure the ODU bolt-down points are correctly seated, then tighten the four nuts with a 19 mm
(3/4") torque wrench (it must be set to 35 Nm).
10) To remove an ODU, reverse this procedure.
When removing an ODU from its mount, ensure the ODU fastening nuts are fully released.

4.1.3.2.4 Remote-Mounted ODUs
An ODU can be installed separate from its antenna, using a remote-mount to support the ODU, and a
flexible-waveguide to connect the ODU to its antenna. A remote mount allows use of standard, single or
dual polarization antennas. The mount can also be used to remotely support a protected ODU pairing
installed on a coupler. The coupler connects to the remote mount assembly in the same way as an ODU.
When co-channel XPIC single antenna link operation is required, the two ODUs must each be connected
to their respective V and H antenna ports using remote mounts.
The remote mount clamps to a standard 114 mm pole-mount, and is common to all frequency bands.
The following photos show the remote mount solution (P/N 3CC58046AAAA).
Figure 246. Remote Mount: front view
Figure 247. Remote Mount: rear view

Figure 248. Remote Mount with an ODU installed: front view
Figure 249. Remote Mount with an ODU installed: rear view

Figure 250. Remote Mount with an ODU installed and flexible waveguide
Figure 251. Remote Mount with the 1+1 coupler installed

Figure 252. Remote Mount with the 1+1 coupler and one ODU installed
4.1.3.2.4.1 Flexible waveguides
Flexible waveguides are frequency band specific and are normally available in two lengths, 600 mm (2
ft) or 1000 mm (3.28 ft). Both flange ends are identical, and are grooved for a half-thickness gasket, which
is supplied with the waveguide, along with flange mounting bolts.
To prevent wind-flex, a flexible waveguide or coax must be suitably fastened or supported over its length.
Note
The flexible waveguides have tin-plated brass flanges to minimize dissimilar-metal corrosion between the
aluminum feed-head on the ODU and the brass antenna port(s) used on most standard antennas.
Where a flexible-waveguide length greater than the 1 m (3.28 ft) maximum included in the
9500 MPR-E accessories list is needed, contact your Alcatel-Lucent service support center.

4.1.3.2.4.2 Waveguide Flange Data
Table 11. 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 11. Waveguide Flange Data

Waveguide
Waveguide
Frequency
Washers
Thread
Flange
Flange
Mating
Spring
Depth
Radio
Bolt Length
Band
Reqd
Reqd
Bolts
Spec
Type
Type
Hole
Bolt
Required
Flange thickness +
6 GHz UDR70 PDR70 WR137 8 x M5 8 M5x0.8 6H 10
Hole depth - 2mm
Flange thickness +
7/8 GHz UDR84 PDR84 WR112 8 x M4 8 M4x0.7 6H 8
Hole depth - 2mm
Flange thickness +
10/11 GHz UDR100 PDR100 WR90 8 x M4 8 M4x0.7 6H 8
Hole depth - 2mm
Flange thickness +
13 GHz UBR120 PBR120 WR75 4 x M4 4 M4x0.7 6H 8
Hole depth - 2mm
Flange thickness +
15 GHz UBR140 PBR140 WR62 4 x M4 4 M4x0.7 6H 8
Hole depth - 2mm
18/23/26 Flange thickness +

UBR220 PBR220 WR42 4 x M3 4 M3x0.5 6H 6
28/32/38 Flange thickness +

UBR320 PBR320 WR28 4 x M3 4 M3x0.5 6H 6

4.1.3.2.5 Remote-Mount Installation Procedure
This topic describes the installation of a remote mount, the attachment of the ODU to the mount, and the
installation of the flexible waveguide.
4.1.3.2.5.1 Installing the Remote Mount
The remote mount attaches to a standard 114 mm pipe mount using two saddle clamps. Firmly fasten the
clamp nuts.
4.1.3.2.5.2 Attaching the ODU and Flexible Waveguide
Before attaching the ODU to the remote mount, fit the flexible waveguide to the ODU.
1) Remove one gasket from the packet supplied with the flexible waveguide,apply a thin smear
of silicon grease to the gasket, and fit the gasket to the recess in the flange.
2) Firmly attach the flange to the ODU feed head using the bolts supplied.
3) Fully loosen the nuts on the four ODU mounting bolts, then thread the waveguide through the
center of the mount.
4) Attach the ODU to the mount by inserting the bolts through the receptor holes,and rotating the
ODU clockwise to bring the mounting bolts hard up against the slot ends.
5) Tighten the four nuts with a 19 mm (3/4") torque wrench (it must be set to 35 Nm).
6) Prepare the antenna-end of the flexible waveguide as in step 1 above.
7) Check, and adjust if necessary, the run of the waveguide for best protection and support posi-
tion before fastening the flange to the antenna port.
8) Secure the waveguide to prevent wind-flex using hanger assemblies or similar. If cable ties are
used, do not over-tighten.
4.1.3.2.6 Grounding the ODU
To ground the ODU use the following procedure:
1) Locate the green 2 m ground wire in the ODU installation Kit. One end is fitted with a crimp lug,
the other is free.
2) Fasten the lugged end of ground wire to the ODU grounding stud. Before tightening, ensure
the cable is correctly aligned towards the tower.
3) Locate a position on a tower member for the ground clamp. This must be as close as practical
below the ODU for downward-angled positioning of the ground wire.
4) Scrape any paint or oxidation from the tower at the clamping point to ensure there will be good
low-resistance contact
5) Cut the ground wire so there will be a just a little slack in the wire when it is connected to the
ground clamp. A ground clamp is supplied as part of all ODU Cable Installation and Suppressor
kits.

6) Strip the insulation back by 25 mm (1 inch), fit into ground clamp, and firmly secure the clamp
to tower.
7) Liberally apply conductive grease/paste around the ground clamp to provide corrosion resis-
tance. Also apply to the ODU ground stud.
4.1.3.3 Installing a Coupler
4.1.3.3.1 Coupler Overview
Couplers (combiners) are available for equal loss or unequal loss.
For equal loss the attenuation per side is nominally 3.5 dB (3.5 / 3.5 dB), which applies to both the
transmit and receive directions, meaning the additional total one-way attenuation compared to a non-
protected link is 7 dB.
For unequal loss the attenuation is nominally 1.5/6.5 dB. They have application on rain-affected
bands, 13 GHz and above.
The rationale for using unequal ratios is that they can be shown to lower annual outage due to rain fades
as compared to links deployed with equal loss couplers.
4.1.3.3.2 Coupler Installation Procedure
Note
A coupler installation procedure is included with each coupler.
The following procedure summarizes installation of a direct-mounted coupler. A coupler may also be
installed remote-mounted, where a single flexible waveguide is used to connect the coupler to its antenna.
4.1.3.3.2.1 Attaching a Direct-Mounted Coupler
Before installing a coupler check there will be sufficient mechanical clearance for the coupler and its
ODUs. There should be no clearance issues using approved antennas when installed correctly on its
mount with the appropriate left or right offset. However care must be taken at locations where a non-
standard antenna installation is required.
The ODUs are attached to the coupler as if attaching to an antenna except that there is no polarization
rotator associated with each ODU. Rather the coupler polarization is set to match the V or H antenna
polarization using 0 degree or 90 degree coupler interfaces, which are supplied with the coupler. Couplers
are default fitted with the vertical polarization interface.
A coupler must always be installed onto its antenna before ODUs are attached to the coupler.
To install a coupler:
For a vertically polarized antenna proceed to step 2. For a horizontally polarized antenna begin at step
1. (Antenna polarization setting is described in par. 4.1.3.2.2 - Setting the Polarization on page 357).

1) To change the coupler interface, remove by unscrewing its four retaining screws. Replace with
the required interface, ensuring correct alignment between the interface and coupler body
alignment indicators. Relocate the O-ring to the newly fitted interface.
2) Remove all protective tape from the waveguide ports and check that the ODU/coupler mounting
collar, polarization rotator, coupler interface and O-ring, are undamaged, clean, and dry.
3) Apply a thin layer of silicon grease around the coupler interface O-ring.
Note
A tube of silicon grease is included in ODU and coupler installation kits
4) Fully loosen the nuts on the four coupler mounting bolts.
5) Position the coupler so the waveguide slots (coupler and rotator) will be aligned when the ODU
is rotated to its end position.
6) Fit the coupler onto its mounting collar by inserting the bolts through receptor holes in the collar,
then rotate the coupler clockwise to bring the mounting bolts hard up against the slot ends.
7) Carefully bring the coupler forward to fully engage the coupler feed head with the polarization
rotator in the mounting collar.
8) Finger-tighten the four nuts, checking to ensure correct engagement of coupler with mounting
collar.
9) Ensure the coupler bolt-down points are correctly seated, then tighten the four nuts with an
open-ended 19 mm (3/4") spanner.
10) To remove a coupler, reverse this procedure.
Figure 253. shows an installed coupler. Figure 254. and Figure 255. show a completed installation with
ODUs, surge suppressors and grounding.
Related procedures are:
Installing the ODUs; refer to par. 4.1.3.2.3 - Direct-Mount ODU Attachment Procedure on page 359.
Note that when attaching an ODU to a coupler there is no requirement to first set a polarization; the
ODUs are attached such that when rotated into position there is correct alignment of the waveguide
slots. ODUs may be attached such that cables exit to the right or left of the ODU.
Grounding an ODU; refer to par. 4.1.3.2.6 - Grounding the ODU on page 365.
Installing the ODU cable and connectors; refer to par. 4.1.3.4 - Installing ODU Cables and Connectors on
page 370.

Figure 253. Coupler fitted to Antenna
Figure 254. Coupler Installation with ODUs

Figure 255. Coupler Installation with ODUs: Rear View
Warning: it is necessary to add some extra-lenght for maintenance or orientation modification of the
antenna.
N.B. The external ligthning suppressors are no more needed.
4.1.3.3.3 Unused and Disconnected Coupler
Unused ODU ports on a coupler must the blanked off with a microwave load as at some frequencies the
reflected power can affect operation at the remaining port, partly canceling the wanted signal.
A flange-mounted termination is used to absorb the RF energy. They are needed in 1+0 and cascaded
coupler applications where some ODU ports are left open/ not attached to an ODU.
Terminations are available from Alcatel-Lucent.

4.1.3.4 Installing ODU Cables and Connectors
Note
The ODU cable installation must comply with 9500 MPR-E requirements. If the cable, grounds and
weatherproofing are incorrectly installed, the Alcatel-Lucent warranty can be voided.
This section includes information on:
Cable Options (par. 4.1.3.4.1 on page 370)
Coaxial Cable Installation Requirements (par. 4.1.3.4.1.1 on page 370)
Cable Grounding (par. 4.1.3.4.2 on page 371)
Type N Cable Connectors (par. 4.1.3.4.2.1 on page 372)
4.1.3.4.1 Cable Options
The recommended ODU cable type for connections of less than 80 m (262 ft) is the 1AC041350001 cable.
For other cable options to reach higher distance (300m/984ft) ask Alcatel-Lucent.
4.1.3.4.1.1 Coaxial Cable Installation Requirements
Task Required Considerations Explanation
Installing Connectors Crimped connectors Always use the crimp tool designed for the
crimped connectors/cable being used. A rec-
ommended crimp tool for the connectors
used with the ET 390998 cable is available
from Alcatel-Lucent.
When removing the jacket Take great care when removing the jacket to
- all coaxial cable keep the outer conductor intact. A scored
outer conductor will weaken the cable and,
for a solid outer cable, can cause the outer
conductor to break or crack when subse-
quently bent.
When removing the jacket Always use the cut-off and strip tool specifi-
-solid outer conductor cable cally designed for the cable being used.
Fastening Type N connectors Tighten Type N connectors (male to female)

by hand only.
Weatherproofing All outdoor connections must be made

weatherproof. Refer to Weatherproofing.
cont.

Planning the Route Protection for the cable The route chosen must provide physical pro-
tection for the cable (protection against acci-
dental damage).
Keep access to tower and ser- The cable must be positioned so that there is
vices clear unimpeded access to the tower and to ser-
vices on the tower.
Ease of running and fastening Use a route which minimizes potential for
damage to the cable jacket and avoids
excessive cable re-bending.
Installing the Cable Cable jacket Keep cable clear of sharp edges.
Cable support Rod support kits or similar must be used

across unsupported sections of the cable run
so that the cable cannot flex in the wind.
Bend radius Ensure the minimum bend radius for the

cable is not exceeded.
Cable ties Use one UV-resistant cable tie every 1m (3 ft)

or less, of cable.
Cable grounding Ensure the cable is grounded in accordance

with the instructions provided in Cable
Grounding.
Ice-fall protection Ensure adequate physical protection for the

cable where ice-fall from towers can occur.
4.1.3.4.2 Cable Grounding
Ground kits are included in the ODU Cable Kits.
For tower/mast installations the ODU cable must be grounded at:
The point where it comes on to the tower from the ODU
The point where it leaves the tower to go to the equipment building
Not more than 25 m (80 ft) intervals on the tower if the height on the tower exceeds 50 m (165 ft)
A point just prior to building entry
Figure 256. shows typical tower locations for cable grounding and lightning surge suppressors.
At non-standard installations, such as building tops or the sides of buildings, follow the same general
guidelines but where proper grounding points are not provided these must first be installed.
For ground kit installation instructions refer to the guide provided with each kit.

ODU & antenna
ODU ground wire
Cable ground
ODU cable supported by black cable ties

at not more than 1 m intervals.
Must not run adjacent to tower lightning
ground or electrical cables
Install additional cable grounds at not more

than 25 m intervals if the height of cable on
the tower exceeds 50 m
Cable ground Cable ground
Cable carrier Rack ground bar
ground bar
Site grounding
Figure 256. Locations for Cable Grounds
4.1.3.4.2.1 Type N Cable Connectors
Note
All type N connectors used outdoors must be weatherproofed.

Refer to par. 4.1.3.5 - Weatherproofing on page 373.
Ensure connectors are correctly fitted. Where crimp connectors are used, ensure the correct crimp tool
is used.

4.1.3.5 Weatherproofing
Weatherproofing kits are included with consumable kit. Two types of weatherproofing media are supplied.
4.1.3.5.1 Mastic Tape
The ODU cable ground kits include rolls of vinyl and butyl mastic tape. For these, a two-layer wrap process
is recommended:
An initial layer of mastic tape. It is this tape that provides the weatherproofing.
A top layer of vinyl tape to support good amalgamation and adhesion of the mastic tape and to
provide UV protection.
Note
If mastic tape is used to weatherproof connectors a three-layer process is recommended, where a layer
of vinyl tape is applied before the mastic to facilitate easy strip-back when connector disconnection is
required. Special attention must be given to ensuring the mastic tape seals cleanly to the primary surfaces,
such as the cable jacket.
4.1.3.5.1.1 Wrapping Guidelines, Mastic tape
To weatherproof connectors start at 1. To weatherproof a cable ground start at 3.
1) Ensure connectors are firmly hand-tightened, dry, and free from all grease and dirt. If neces-
sary, clean with rag lightly moistened with alcohol-based cleaner.
2) Pre-wrap using vinyl tape. Use a 25% overlay when wrapping. To avoid curl-back do not stretch
the tape too tightly at the end point.
Note
On an ODU connector, leave at least two-thirds of the smooth length of the barrel clear
of pre-wrap vinyl tape, to ensure the mastic tape has sufficient area of direct grip.
3) Wrap with mastic tape using a 75% overlay. Where possible, use not less than a 25 mm (1")
attachment onto the primary surface (25 mm past the cable sheath cut, or any pre-wrap).
Note
There must be a full seal of mastic tape onto the primary surface for weatherproofing integrity.
4) Lightly firm over by hand to ensure a full seal at all points, using a tear-off section of the mastic
tape backing to protect your hands. Check that there is no possibility of water entry before pro-
ceeding to the next step 5.
5) Cover the mastic tape with a final layer of vinyl tape. To avoid curl-back, do not stretch the tape
too tightly at the end.

Note
To avoid displacement of the mastic tape, do not stretch the final layer of
vinyl tape across sharp corners and edges.
4.1.3.5.2 Self Amalgamating Tape
Self amalgamating tape binds to the host and bonds between layers to provide a continuous seal. It is
especially useful in tight locations, such as around the Type N connectors of the suppressor when installed
with its support bracket on an ODU.
4.1.3.5.2.1 Wrapping Guidelines, Amalgamating Tape
1) Ensure the connectors are firmly hand-tightened, dry, and free from all grease and dirt. If nec-
essary, clean with a rag lightly moistened with alcohol-based cleaner.
2) Apply the tape with tension (slight stretching), using at least a 75% overlay.
3) Where possible, apply the tape 25 mm (1") past the ends of the connector barrels to ensure
the weatherproof bond extends beyond the areas requiring protection. The tape must be
applied in such a way that the sealing is robust (no obvious weak points).
4) To avoid curl-back, do not stretch the tape too tightly at the end.
5) To assist UV protection, a post-wrap using vinyl tape can be applied.

4.1.4 Indoor Installation
This section includes:
Indoor accessories (par. 4.1.4.1 on page 375)
Indoor cables (par. 4.1.4.2 on page 376)
Distributors (par. 4.1.4.4 on page 381)
MSS cards (par. 4.1.4.5 on page 383)
Ethernet Electrical Cables (par. 4.1.4.6 on page 384)
Ethernet Optical Cables (par. 4.1.4.7 on page 384)
Installing the Indoor section (par. 4.1.4.8 on page 385)
Installation components (par. 4.1.4.9 on page 387)
Types of Indoor configurations (par. 4.1.4.10 on page 388)
Connectors on the front panel of the 32E1 PDH card and 16 E1 ASAP card (68 Pin SCSI Functions)
(par. 4.1.4.12 on page 413)
4.1.4.1 Indoor accessories
1AD137820001 TRU: Power Distribution with 1 Input 48VDC and 6 breakers 16A
1AD137830001 TRU: Power Distribution with 1 Input 48VDC and 12 breakers 16A
3CC50042AAAA ETSI Rack mounting kit (valid for TRU 1AD137820001, TRU 1AD137830001,
support 19" module 120 ohm 3CC07810AAAA)
3CC50027AAAA IDU wall mounting kit (10U)
3DB16102AAAA Panel E1 protection 120 ohm
3DB16151AAAA DIN rack kit for Panel distributor 120 ohm
3DB16152AAAA ETSI rack kit for Panel distributor 75/120 ohm
3CC07810AAAA 3U Distributor subrack for 120 ohm EMC
3CC08061AAAA Connector support 1.5./5.6 75 ohm (Panel 1U)
3DB16104AAAA Panel E1 protection 75 ohm 1.0/2.3
3CC08061ABAA Connector support BNC 75 ohm (Panel 1U)
1AD114560001 Laborack (19" rack)
3DB04656AAAA ETSI rack (H2200 21" rack)
3DB18171ABAA DIN Bracket
3DB18159ABAA ETSI bracket

3CC13424AAAA Rack grounding kit
3CC13423AAAA Subrack grounding kit (includes the yellow/green cable)
3CC06503AAAA Consumable kit
3DB18181AAAA IDU kit subrack (brackets 21" kit)
1AF15185AAAA IP Phone
3CC50065AAAA Adaptor bracket kit 1U ETSI (valid for 3CC08062AAAA, 3CC08061AAAA,

3CC08061ABAA)
4.1.4.2 Indoor cables
1AC041800001 24V DC 3G power supply cable (2x16mm2) (from Station battery to TRU)
3DB18271AAAB TRU-MSS power-cable supply connection 2x4mm2 unshielded (L = 4m)
3CC13423AAAA MSS grounding Kit
3DB18205AAAA QMA (male) - N (female) RF cable (from Radio Access card to bracket)
(L = 0.35m)
3DB18205ABXX QMA (male) - N (female) RF cable (L = 2m)
1AB357780003 QMA 90 Male connector (to be used only with diam. = 6.85 mm coax cable
and to be terminated on field for direct connection between MSS and
ODU300)
3CC52133AAAA SCSI 68pin - blue block L = 1.1m
3CC52118AAAA SCSI 68-SCSI 68 pin to pin
3CC07658AFAB Cable 8XE1 IDU-DISTRIBUTOR 120 ohm L = 1m 45 (37 pin)
3CC07885AFAA Cable 8XE1 IDU-DISTRIBUTOR 75 ohm 1.5/5.6 L = 1m 45 (37 pin)
3CC07759AFAA Cable 8XE1 IDU-DISTRIBUTOR 75 ohm BNC L = 1m 45 (37 pin)
3CC52157AAAA 2xSCSI, 68 pin - 4 Compax blue blocks (120 ohm) L = 1.1 m
3CC52134AAAA Adapter cord from 1SCSI68 male to 2DB37 female
3DB18204AAAA 1.0/2.3-1.0/2.3 Synchronization (2.048-5-10 MHz) protection
3CC52138AAAA Cord 1.0/2.3 M 90 M90 L = 5m (for synch. distribution)
3DB01516AAXX Cord 1.0/2.3 M 90 M90 L = 1.6m (for synch. distribution)
3CC52117AAAA SCSI 68pin - FW L = 30m (for the cable colors refer to Figure 258. and Table
13.)

3CC52117ABAA SCSI 68pin - FW L = 15m (for the cable colors refer to Figure 258. and Table
13.)
3DB10003AAXX Cable 8xE1 IDU-DISTRIBUTOR 75 ohm coax no connectors L = 15m (37 pin)
3DB06371ABAA SUB D 37 pin - FW L = 20m 45
3CC52015AAXX Cable, Trib, E1, RJ45 to wire-wrap L = 5m
3CC52020AAXX RJ45 to RJ45 E1 cross-over cable
3CC52150AAAA SCSI-SCSI cross-cable L = 1.6m
3CC52150ABAA SCSI-SCSI cross-cable L = 6.4m
3DB10087AAAA MPR ESC - MPR (AWY) ESC L=1.6m
3DB10088AAAA MPR ESC - MPR (AWY) ESC L=6.4m
3DB10093AAAA MPR ESC - LUX NMS1 or NMS2 L=1.6m
3DB10094AAAA MPR ESC - LUX NMS1 or NMS2 L=6.4m
3CC52165AAAA MPR Audio - AWY audio L=1.6m
3CC52165ABAA MPR Audio - AWY audio L=6.4m
3CC52112AAAA HD26M - 3xsubD 9p F SYNC L=1M
3CC52122AAAA 9500MXC-AWY (MPR) sync continuity L=1.6m
3CC52123AAAA 9500MXC-AWY (MPR) sync continuity L=6.4m
3CC52111AAAA HD26M - 3xsubD 9p F ASYNCH L=1M
3CC52124AAAA 9500MXC-AWY (MPR) asynch continuity L=1.6m
3CC52125AAAA 9500MXC-AWY (MPR) asynch continuity L=6.4m
3DB05594AAAA Cord for AUX management (refer to Figure 257. and Table 12. for the pin func-
tion)

Figure 257. Cord for AUX management
Table 12. Cord for AUX management - Pin function
M1 Pair colour Twisted Pair No. Quad No.
2 Blue
1
9 White
1
3 Violet
2
10 Turquoise
4 Orange
3
1 White
2
5 Violet
4
12 Turquoise
6 Green
5
13 White
3
7 Violet
6
14 Turquoise
8 Brown
7
15 White
4
11 Violet
8
N.B.3 Turquoise

Figure 258. SCSI 68 male connector
Table 13. SCSI 68 pins FW cable colors
Pair No. Signal Pin # Wire colour Pin # Wire colour
GND 1 35
1 TTIP 2 White 36 Blue
1 RTIP 3 White 37 Blue
2 TTIP 4 White 38 Orange
2 RTIP 5 White 39 Orange
3 TTIP 6 White 40 Green
3 RTIP 7 White 41 Green
4 TTIP 8 White 42 Brown
4 RTIP 9 White 43 Brown
5 TTIP 10 White 44 Grey
5 RTIP 11 White 45 Grey
6 TTIP 12 Yellow 46 Blue
6 RTIP 13 Yellow 47 Blue
7 TTIP 14 Yellow 48 Orange
7 RTIP 15 Yellow 49 Orange
8 TTIP 16 Yellow 50 Green
8 RTIP 17 Yellow 51 Green
9 TTIP 18 Yellow 52 Brown
9 RTIP 19 Yellow 53 Brown
10 TTIP 20 Yellow 54 Grey
10 RTIP 21 Yellow 55 Grey
11 TTIP 22 Violet 56 Blue

11 RTIP 23 Violet 57 Blue
12 TTIP 24 Violet 58 Orange
12 RTIP 25 Violet 59 Orange
13 TTIP 26 Violet 60 Green
13 RTIP 27 Violet 61 Green
14 TTIP 28 Violet 62 Brown
14 RTIP 29 Violet 63 Brown
15 TTIP 30 Violet 64 Grey
15 RTIP 31 Violet 65 Grey
16 TTIP 32 Black 66 Blue
16 RTIP 33 Black 67 Blue
GND 34 68
4.1.4.3 Accessories and cables for ODU300 connections
3CC50074ABXX Support kit for 4 cord. N/QMA IDU MPR
1AB095530023 Coax cable conn. male straight 50 ohm (diam.=10.3 mm)
1AB128500002 Coax cable grounding kit (diam.=10.3 mm)
1AB095530036 Coax cable conn. male straight 50 ohm (diam.=6.85 mm)
1AD040130004 Coax cable grounding kit (diam.=6.85 mm)
3DB00714AAXX Coax cable N conn. male (LCF 3/8 CU H cable)
3DB00715AAXX Coax cable N conn. 90 male (LCF 3/8 CU H cable)
3DB00698AAXX Coax cable grounding kit (LCF 3/8 CU H cable)
1AD127970001 Cable grounding kit KMT11-N (Yellow/Green)
1AB3557780003 QMA Connector for coax. cable (diam. 6.85 mm)
1AC001100022 Coax cable 50 ohm (diam.=10.3 mm) (L = <150m )
1AC041350001 Coax cable 50 ohm (diam.=6.85 mm) (L = <80m)
3DB00713AAXX Coax cable 50 ohm LCF 3/8 CU H (L = <300m)
3CC50100AAXX MSS ODU300 tool bag (special tools)

4.1.4.4 Distributors
The Distributor subracks available are:
Figure 259. Protection Panel 32E1 SCSI 68 - 1.0/2.3 75 ohm (Front/Rear) (3DB16104AAAA)
Figure 260. Protection Panel RJ45 120 ohm (Front/Rear) (1AF15245ABAA)
Figure 261. Protection Panel 32E1 SCSI 68 - 1.6/5.6 75 ohm (Front) (1AF15243AAAA)
Figure 262. Protection Panel 32E1 BNC 75 ohm (Front) (1AF15244AAAA)
Figure 263. Connector support 1.6/5.6 75 ohm Panel 1U (3CC08061AAAA)
Figure 264. Connector support BNC 75 ohm Panel 1U (3CC08061ABAA)

Figure 265. Support 19 Inch modules 120 ohm Panel 3U (3CC07810AAAA)
Figure 266. E1 Protection SCSI 68/Sub-D 37 (Front/Rear) (3DB16102AAAA)

4.1.4.5 MSS cards
The MSS available cards are:
Figure 267. Core-E Card
Figure 268. Radio Access Card
Figure 269. 32xE1 PDH Access Card
Figure 270. 16xE1 ATM ASAP Card
Figure 271. AUX Peripheral Card

4.1.4.6 Ethernet Electrical Cables
3CC52141ABAA RJ45-RJ45 Eth. CAT5E shielded straight cable 5 m
3CC52141ACAA RJ45-RJ45 Eth. CAT5E shielded straight cable 15 m
4.1.4.7 Ethernet Optical Cables
The following multi-mode jumpers are available:
1AB214000016 Fiber Simplex MM jumper LC-LC L=5m
1AB214000017 Fiber Simplex MM jumper LC-LC L=10m
1AB240330033 Fiber Simplex MM jumper LC-FC L=5m
1AB240330032 Fiber Simplex MM jumper LC-FC L=10m
1AB200240003 Fiber Simplex MM jumper LC-SC L=5m
1AB200240004 Fiber Simplex MM jumper LC-SC L=10m
The following single-mode jumpers are available:
3CC52077AAAA Fiber 3M SM LC to LC
3CC52080AAAA Fiber 3M SM LC to FC
3CC52083AAAA Fiber 3M SM LC to SC
3CC52088AAAA Fiber 5M, SM FC-SC
3CC52017AAAA Fiber 10M, SM FC-SC
3CC52023AAAA Fiber 3M, SM SC-SC

4.1.4.8 Installing the Indoor section
Figure 272. Installation subrack and 3 cord N/QMA Kit
Figure 273. Installation Card
Figure 274. Installation Accessory

Figure 275. Connection Cables

4.1.4.9 Installation components
Alcatel-Lucent code Description
1AD114560001 Laborack
or
3DB04656AAAA ETSI RACK H 2200
1AD137820001 Power Distribution with 1 Input 48VDC and 6 breakers 16A

or
1AD137830001 Power Distribution with 1 Input 48VDC and 12 breakers 16A
3DB18125ABAA Subrack
3DB18171AAAA Din Brackets

or
3DB18159ABAA
3CC50074ABAA Kit support for 4 Cord N/QMA
1AF15245AAAA Protection panel RJ45
3DB18172ABXX Fan unit card
3DB18007ABXX Core-E card
3DB18136ACXX Modem 300 card
3DB18136ADXX
3DB18538AAXX Modem 300EN card
3DB18538ABXX
3DB18126ADXX 32E1 PDH card
3DB18602AAXX 16E1 ASAP card
3DB18236ABXX AUX Peripheral card
3CC13423AAAA IDU Grounding kit
1AB187280040 1000BASE-LX optical plug-in (option)
1AB187280045 1000BASE-SX optical plug-in (option)
3AL81728AAAA Tool for SFP plug-in extraction (option)
N.B. The 16E1 ASAP card has on the front panel only 1 SCSI 68 pin connector (not 2 SCSI 68 pin
connectors present on the front panel of the 32E1 PDH card). For this reason to install the ASAP
card only 1 cable is needed.

4.1.4.10 Types of Indoor configurations
4.1.4.10.1 Repeater 2x1+0 32E1 (1 PBA PDH) towards customer DDF 120 Ohms 3U
Figure 276. Repeater 2x1+0 32E1 (1 PBA PDH) towards customer DDF 120 Ohms 3U
Figure 277. Repeater 2x1+0 32E1 (1 PBA PDH) towards customer DDF 120 Ohms 3U

4.1.4.10.2 Repeater 2x1+0 32E1 (1 PBA PDH) towards internal DDF 120 Ohms 3U
Figure 278. Repeater 2x1+0 32E1 (1 PBA PDH) towards internal DDF 120 Ohms 3U

4.1.4.10.3 Repeater 2x1+0 32E1 (2 PBA PDH) towards 2xinternal DDF 75 Ohms BNC 2x1U with
cords 3CC52134AAAA (1 SCSI68 to 2 DB37)
Figure 280. Repeater 2x1+0 32E1 (2 PBA PDH) towards 2xinternal DDF 75 Ohms BNC 2x1U with


4.1.4.10.4 Repeater 2x1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms
Figure 283. Repeater 2x1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms


4.1.4.10.5 Repeater 2x1+0 32E1 (2 PBA PDH) towards internal DDF 75 Ohms 1.6/5.6 2U
Figure 286. Repeater 2x1+0 32E1 (2 PBA PDH) towards internal DDF 75 Ohms 1.6/5.6 2U
Figure 287. Repeater 2x1+0 32E1 (2 PBA PDH) towards internal DDF 75 Ohms 1.6/5.6 2U

4.1.4.10.6 Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U
Figure 288. Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U
Figure 289. Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U

4.1.4.10.7 Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U


4.1.4.10.8 Terminal 1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms
Figure 293. Terminal 1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms
Figure 294. Terminal 1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms

4.1.4.10.9 Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms BNC 3U
Figure 295. Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms BNC 3U
Figure 296. Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms BNC 3U

4.1.4.10.10 Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U
Figure 297. Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U
Figure 298. Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U

4.1.4.10.11 Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms 1.0/2.3 1U
Figure 299. Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms 1.0/2.3 1U
Figure 300. Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms 1.0/2.3 1U

4.1.4.10.12 Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U
Figure 301. Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U
Figure 302. Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U

4.1.4.10.13 Terminal 1+1 32E1 Full protected with 2 cords 3CC52157AAAA (2 PBA PDH) towards
internal DDF 120 Ohms 3U
Figure 303. Terminal 1+1 32E1 Full protected with 2 cords 3CC52157AAAA (2 PBA PDH) towards
Figure 304. Terminal 1+1 32E1 Full protected with 2 cords 3CC52157AAAA (2 PBA PDH) towards

4.1.4.10.14 Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards customer DDF 120 Ohms
Figure 305. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards customer DDF 120 Ohms

4.1.4.10.15 Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 75 Ohms 1.0/
2.3 1U
Figure 307. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 75 Ohms 1.0/
2.3 1U
Figure 308. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 75 Ohms 1.0/
2.3 1U

4.1.4.10.16 Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 120 Ohms 3U
Figure 309. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 120 Ohms 3U
Figure 310. Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 120 Ohms 3U

4.1.4.10.17 Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards 2xinternal DDF 75 Ohms 1.0/
2.3 1U
Figure 311. Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards 2xinternal DDF 75 Ohms 1.0/
2.3 1U
2.3 1U

2.3 1U

4.1.4.10.18 Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards 2xinternal DDF 120 Ohms 3U
Figure 314. Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards 2xinternal DDF 120 Ohms 3U


4.1.4.10.19 Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards customer DDF 120 Ohms

4.1.4.11 Stacking configuration with Core Protection
4.1.4.11.1 Example of Ethernet port interconnection
Figure 319. Example of Ethernet port interconnection
4.1.4.11.2 Example of Synch interconnection
Figure 320. Example of Synch interconnection
N.B. In the upper MPR as example the Synch In cable has been installed. In this case the upper
MPR receives the synch from another equipment.

4.1.4.12 Connectors on the front panel of the 32E1 PDH card and 16 E1 ASAP card (68
Pin SCSI Functions)
Table 14. Pin Function: Tributaries 1-16 (32E1 PDH card/16E1 ASAP card)
Description Pin # Pin # Description
GND 1 35 GND
TTIP Trib. 1 2 36 1 Trib. TTIP
RTIP Trib. 1 3 37 1 Trib. RTIP

GND 34 68 GND
Table 15. Pin Function: Tributaries 17-32 (32E1 PDH card)
Description Pin # Pin # Description
GND 1 35 GND

GND 34 68 GND

4.1.4.13 Connectors on the front panel of the AUX peripheral card
The Service Channel interface 1 connector on front panel is a SubD 15 female.
Table 16. Service channel 1 pin functions

Pin Signal Direction Pin Signal Direction
1 GND NA 9 Audio(-) from user

Input
2 Audio(+) from 10 Audio(-) to user Party Line

user Input Output
Party Line
3 Audio(+) to user Output 11
4 GND for Audio NA 12 RS422 Data in (-) Input
5 RS422 Data in Input 13 RS422 Clock in Input

(+) (-)
RS422/
6 RS422 Clock in Input 14 RS422 Data out Output
V.11
(+) RS422/ (-)
64K
V.11
7 RS422 Data out Output 15 RS422 Output
64K
(+) Clock out
(-)
8 RS422 Clock out Output

(+)
The Service Channel interface 2 connector on front panel is a SubD 15 female.
Table 17. Service channel 2 pin functions
1 GND NA 9 G 703 Data in (-)

Input
2 G 703 Data in (+) 10 G 703 Data out (-) G 703

Input Output 64K
G 703
3 G 703 Data out (+) Output 64K 11 RS232 Data out Output RS232/
V.24/V.28

4 RS232 Data in Input RS232/ 12 RS422 Data in (-) Input
V.24/V.28
5 RS422 Data in (+) Input 13 RS422 Clock in (-) Input

RS422/
V.11
6 RS422 Clock in Input 14 RS422 Data out (- Output
64K or 9.6K
(+) RS422/ )
V.11
7 RS422 Data out Output 15 RS422 Output
64K or 9.6K
(+) Clock out
(-)
8 RS422 Clock out Output

(+)
Synchronous 64 Kb/s RS422/V.11 DCE co-directional
Figure 321. DTE-DCE Interface
This interface is a particular case of the co-directional definition when it is possible to assume that the tim-
ing signals are equal in both the directions: the subordinate equipment (DTE) has to synchronize the out-
put data with the unique timing signal received.

Table 18. Housekeeping connector pin function
1 Housekeeping 1 Input 9 COM NA Common

return
2 Housekeeping 2 Input 10 GND NA Ground
3 Housekeeping 3 Input 11 Housekeeping 9 Output

House-
House-
6 Housekeeping 6 Input 14 Housekeeping 12 Output keeping
keeping
7 Housekeeping 7 Output 15 Housekeeping 13 Output
8 Housekeeping 8 Output
Input alarm
The polarity of each input Alarm-Housekeeping is configurable. The state of each alarm input is config-
urable by ECT/NMS in order to be active if the voltage on the input is high (open contact) or if the voltage
is low (closed contact). This second option is the default value.
The polling rate of the input alarms is 1 second, no latch of input state is performed.
Figure 322. Alarm Polarity

Input alarm electrical characteristics
open contact: 2V < |V|< 60 V; |I| < 0.2mA
closed contract: 0V < |V|< 2 V; |I| < 50mA
Though the housekeeping equipment requirement on max input voltage is 60 V, the PCB layout of periph-
eral must be able to manage 72 V.
By default the presence of active alarm corresponds to closed relay contact with a common wire available
to the customer. By CT/NMS it is possible to change the polarity independently for each alarm (both nor-
mally closed and normally open contacts are available on the I/O connector).
When the power supply is down (and also when the power supply is on but the SW hasn't yet initialized
the HW), all the relays of the outputs of the alarms/housekeeping are in the "open" state (HW default con-
dition).
Figure 323. Polarity of the alarm
Output alarm electrical characteristics
open contact: 2V < |V|< 60V; |I| < 0.2mA
closed contract: 0V < |V|< 2V; |I| < 50mA
Though the housekeeping equipment requirement on max output voltage is 60 V, the PCB layout of
peripheral must be able to manage 72 V.
4.1.4.14 Interconnection to AWY
To interconnect the MPR to AWY refer to the AWY Hardware Installation manual.

4.1.5 Antenna Alignment
This section includes:
Preparation (see par. 4.1.5.1 on page 420)

Signal Measurement (see par. 4.1.5.2 on page 420)
Aligning the Antenna (see par. 4.1.5.3 on page 422)
Main Beams and Side Lobes (see par. 4.1.5.4 on page 426)
4.1.5.1 Preparation
Before aligning antennas ensure:
The ODUs are powered up at both ends of the link.

Transmit and receive frequencies are correctly set.
Transmit powers are correctly set and transmit mute is turned off.
Note
If frequency and/or power settings are not correct for the application,
interference may be caused to other links in the same geographical area.
4.1.5.2 Signal Measurement
Two receive signal-strength indicators are provided to assist antenna alignment, RSL in the CT
Performance screen, and the RSSI voltage at the BNC connector on the ODU. Refer to:
Using RSL Data (see par. 4.1.5.2.1 on page 420)
Using the RSSI Voltage at the ODU (see par. 4.1.5.2.2 on page 421)
RSL Measurement Guidelines (see par. 4.1.5.2.2.1 on page 421)
4.1.5.2.1 Using RSL Data
As CT is accessed via connection to the INU or IDU, a separate means of communication such as two-
way radio or cell phone is required between the CT operator and the person at the antenna.
To align using RSL:
1) Monitor RSL in the CT Performance screen.
2) Set antenna alignment for maximum RSL.
3) Repeat for the far end of the link.
4) Compare actual RSLs with the expected RSLs from the link installation datapack. RSL mea-
surement accuracies for ODU300 are:
a) 2 dB for levels -40 to -70 dBm, over a temperature range of 0 to +35C.
b) 4 dB for levels -25 to -85 dBm, over an extended -33 to +55C range.

4.1.5.2.2 Using the RSSI Voltage at the ODU
A voltmeter, such as a multimeter, is used to measure RSSI voltage at the BNC connector on the ODU.
A suitable BNC to banana-plug connecting cable is available as an optional ODU accessory.
1) To align using the RSSI voltage at the ODU:
2) Connect the voltmeter to the BNC connector. Center pin is positive. Use a low voltage range
for best resolution, nominally 2.5 Vdc FSD.
3) Adjust antenna alignment until the voltmeter reading is at minimum value.
4) Repeat for the far end of the link.
Check and record the peak voltage at each end. The RSSI voltage provides a direct relationship with RSL.
An RSSI of 0.25 Vdc _-10 dBm RSL, and each additional 0.25 Vdc RSSI increase thereafter corresponds
to a 10 dBm decrease in RSL, as follows:
Units Measurement
BNC (Vdc) 0.25 0.5 0.75 1.0 1.25 1.5 1.75 2.0 2.25 2.5
RSL (dBm) -10 -20 -30 -40 -50 -60 -70 -80 -90 -100
5) Compare actual RSLs to the expected RSLs from the link installation datapack. Refer to par.
4.1.5.2.2.1 - RSL Measurement Guidelines.
6) Replace the BNC weatherproofing.
Note
Failure to replace the RSSI BNC weatherproof cap may result in damage to the ODU.
4.1.5.2.2.1 RSL Measurement Guidelines
Interference
The RSSI filter has a nominal 56 MHz bandwidth, which means that depending on the channel bandwidth
used, multiple adjacent channels will be included within the filter passband. Normally this will not cause
a problem as antenna discrimination (beamwidth) and good frequency planning should exclude adjacent
channel interferers. However at sites where this is not the case, ATPC 1should not be enabled.
ATPC operates on the RSL. Any interferer that affects the RSL will adversely affect ATPC operation
Check for interference by muting the Tx at the far end and checking RSSI/RSL at the local end
Note
For CCDP operation and where there is a measurable

adjacent channel RSL, do not use ATPC.

RSSI/RSL Accuracy
When checking RSSI/RSL against the predicted link values ensure appropriate allowances are made for
Tx power-setting accuracy, path-loss calculation accuracy, and RSSI/RSL measurement accuracy.
For a worst-case the overall accuracy is the sum of the individual accuracy limits, which for an
ODU300 link would be 4 dB of the predicted value (2 dB for transmit, 2 dB for receive, 0 to 35C),
aside from the path-loss calculation accuracy, which should be within limits of 3 dB.
Typically, where the measured RSSI/RSL is more than 4 dB lower than the expected receive level
you should check the path survey results, path calculations and antenna alignment.
Note
When checking RSSI/RSL ensure the measurement is made under normal,

unfaded and interference-free path conditions.
A discrepancy of 20 dB or greater between the measured and calculated RSSI/ RSLs suggests an
antenna is aligned on a side lobe, or there is a polarization mismatch.
4.1.5.3 Aligning the Antenna
Antenna alignment involves adjusting the direction of each antenna until the received signal strength
reaches its maximum level at each end of the link.Fine adjustment for azimuth (horizontal angle) and
elevation (vertical angle) is built into each antenna mount.
Adjustment procedures will be provided with each antenna.If the horizontal adjuster does not provide
sufficient range to locate the main beam, the antenna mounting brackets will need to be loosened and
the antenna swiveled on its pole mount to locate the beam.
Before doing this ensure the horizontal adjuster is set for mid-travel.
Some mounts for larger antennas have a separately clamped swivel base to allow the loosened antenna
to swivel on it without fear of slippage down the pole. Where such a mount is not provided a temporary
swivel clamp can often be provided using a pair of pipe brackets bolted together immediately below the
antenna mount.
Note
Ensure antennas are aligned on the main beam, and not a side lobe.
For guidance, refer to the sections Locating the Main Beam (see par. 4.1.5.4.1 on page 426)
and Tracking Path Error (see par. 4.1.5.4.2 on page 427).
Ensure ATPC is turned off during the alignment procedure.

4.1.5.3.1 Standard Alignment Procedure
To align an antenna:
1) Loosen the azimuth adjuster on the antenna mount (horizontal angle) and adjust azimuth posi-
tion for maximum signal strength.
2) Tighten the azimuth securing mechanism. Ensure signal strength does not drop as it is tight-
ened.
3) Loosen the elevation adjuster (vertical angle) and adjust for maximum signal strength.
4) Tighten the elevation securing mechanism. Ensure signal strength does not drop as it is tight-
ened. The terminal is now aligned and ready to carry operational traffic.
5) Record RSL and/or RSSI voltage in the commissioning log.
4.1.5.3.2 Alignment Procedure for Dual polarized Antenna
The following procedure details steps required to:
Check and if necessary set feedhead alignment using a spirit level.
Align the antennas at each end using just one of the feeds, H or V. (Standard co-plane antenna
alignment).
Check cross pole discrimination (XPD).
Note
Optimize alignment of the feed-heads to achieve maximum cross polarization discrimination.

This procedure assumes that the antennas used at each end of the link do comply with their
cross-polarization discrimination specification. If in doubt, refer to the antenna supplier.
Procedure:
[1] Static Feedhead Alignment
During antenna installation and before weatherproofing is installed, use a spirit level to check and
set exact vertical / horizontal alignment of the feeds:
Do not rely on antenna markings as these will not be accurate where a mount is not perfectly
level.
Set the spirit level against the flange of the feedhead. Take care that only the flange of the feed-
head is measured, so that no error is introduced by any minor misalignment of the mating flex-
ible waveguide flange. See Figure 324.

Figure 324. Checking Feedhead Flange with a Spirit level
If not exactly vertical or horizontal, adjust the feedhead skew angle (rotate the feedhead) until
correct (spirit level bubble is precisely centered). For a typical feedhead check both flanges for
level, using an end point half way between the level points of the two flanges should there be
any discrepancy between the two.
[2] Align Antennas
Align the antennas at both ends using the standard (co-plane) alignment procedure, but using just one
of the feeds, V or H. Refer to Standard Alignment Procedure (see par. 4.1.5.3.1 on page 423). When
correct, proceed to step 3.
[3] - TBD -
Power-up both V and H links and check they are operating normally and are alarm-free. Use the Per-
formance screens to check that:
Tx power measurements are within 1 dB (typically). If not check Tx power settings.
RSL measurements are within 2 dB. See Using RSL Data (see par. 4.1.5.2.1 on page 420) for
guidance on measurement accuracy.
Links are operating error-free.
Note
Where there is potential for interference from other links in the same geographical area,
check by turning the far end transmitter(s) off and measuring the local end RSL
on both V and H feeds.

[4] Measure the actual V and H signal discrimination from each antenna.
Where measured XPDs are better than 25 dB no further adjustment is needed
Where less than 25 dB proceed to the next step.
Note
The alignment procedures listed under steps 1 and 2 should result in a discrimination of better than 25dB.
However, for best results and greater operating margins during fading, feedhead alignment should be opti-
mized using the following procedure.
[5] Optimize End-End Feedhead Alignment
This procedure corrects for any minor rotational alignment between antennas at each end.
One antenna is the reference antenna and its feed-head assembly is not adjusted during this pro-
cedure.
Note
Only check/adjust skew angles on one antenna. If both antennas are adjusted and re-adjusted there is
potential for progressive misalignment to occur. Select one antenna as the reference antenna. On long
hops and where fading is prevalent there is potential for the V and H plane paths to be affected differently
and to therefore exhibit variable cross-polarization discrimination. This alignment procedure must be con-
ducted during periods of known, stable path conditions.
[6] Adjust the feedhead skew angle of the antenna for maximum XPD on both V and H link. If the max-
imums for each are at (slightly) different angles, adjust for a mid-point.
Note
Ensure that as you adjust the skew angle, the physical antenna alignment does not shift, which would
make it necessary to repeat step 2. Check that antenna mounting bolts and azimuth and elevation adjuster
locks have been correctly tightened. The maximum points may be quite sharp, rotate the feedhead slowly
to ensure they are not missed.
[7] Check the XPD on the link at the reference end of the link, which should be within 1 to 2 dB of the
measurements at the adjusted end.
[8] On completion ensure feedhead bolts are correctly tightened - check that XPDs do not change during
tightening.
[9] Retain feed-head adjustment data for the commissioning records.

4.1.5.4 Main Beams and Side Lobes
This section describes how to locate the main beam, and typical tracking path errors.
4.1.5.4.1 Locating the Main Beam
Ensure the antennas are aligned on the main beam, and not a side lobe.
Once a measurable signal is observed, very small alignment adjustments are required to locate the main
beam. For instance, a 1.2m antenna at 23 GHz typically has 0.9 of adjustment from center of main beam
to the first null (0.4 to the -3 dB point). Antenna movement across the main beam will result in a rapid
rise and fall of signal level. As a guide, 1 degree of beam width is equivalent to moving approximately 1.0
mm around a standard 114 mm (4.5 in.) diameter O/D pipe.
Antennas can be verified as being on main beam (as opposed to a side lobe) by comparing measured
receive signal level with the calculated level.
Signal strength readings are usually measurable when at least a main beam at one end and first side lobes
at the other are aligned.
The strongest signal occurs at the center of the main beam. The highest first lobe signal is typically 20 -
25 dB less than the main beam signal. When both antennas are aligned for maximum main beam signal
strength, the receive signal level should be within 2 dB of the calculated level for the path. This calculated
level should be included in the installation datapack for the link.
Figure 325. is an example of a head-on, conceptual view of the beam signal strength, with concentric rings
of side lobe peaks and troughs radiating outward from the main beam.
Figure 325. Indicative head-on signal pattern for a parabolic antenna

4.1.5.4.2 Tracking Path Error
Side lobe signal readings can be confused with main beam readings. This is particularly true for the first
side lobe as the signal level at its center is greater than the signal level at the edges of the main beam,
and if tracking on an incorrect elevation (or azimuth) a false impression of main beam reception can be
obtained. This illustration shows an example of this with a simplified head-on view of an antenna radiation
pattern, and tracking paths for three elevation settings.
Figure 326. Example Tracking Path Signals
Line AA represents the azimuth tracking path of a properly aligned antenna.The main beam is at point
2, and the first side lobes at points 1 and 3. Line BB represents the azimuth tracking path with the antenna
tilted down slightly. Signal strength readings show only the first side lobe peaks, 4 and 5. In some instances
the side lobe peaks are unequal due to antenna characteristics, which can lead to the larger peak being
mistaken for the main beam. The correct method for locating the main beam in this case is to set the
azimuth position midway between the first side lobe peaks, and then adjust the elevation for maximum
signal.
Line CC represents an azimuth tracking path with the antenna tilted down further still. The first side lobe
signal peaks (6 and 7) appear as one peak, leading to a mistaken interpretation of a main beam. The
correct method for locating the main beam is to set the azimuth at mid peak, between 6 and 7, and then
adjust elevation for maximum signal.
This first side lobe peaking is probably the most frequent cause of misalignment in both azimuth and
elevation, especially so if one side lobe peaks higher than the other, as shown in Figure 327. A common
error is to move the antenna left to right along line DD, or top to bottom along line EE, always ending up
with the maximum signal at position 1.
Figure 327. Example Tracking Path Signals on the First Side Lobe

4.2 Software local copy
This section explains how to prepare the TCO Suite and Craft Terminal environment in your PC.
Getting Started (par. 4.2.1 on page 429)
PC Characteristics (par. 4.2.2 on page 429)
Download Software Package (SWP) to PC (par. 4.2.3 on page 430)
Download Craft Terminal (CT) and TCO Suite Software to PC (par. 4.2.4 on page 433)
Java JRE Package Installation (par. 4.2.4.1 on page 435)
Local Copy of WebEML (JUSM/CT) (par. 4.2.4.2 on page 435)
Local Copy of TCO Suite (par. 4.2.4.3 on page 436)
Configure PC Network Card to Connect to NE (par. 4.2.5 on page 438)
Download Software Package to NE (par. 4.2.6 on page 442)
Server Access Configuration (par. 4.2.6.1 on page 442)
Init SW Download (par. 4.2.6.2 on page 443)
SW Status (par. 4.2.6.3 on page 446)

4.2.1 Getting Started
Note
Read the following before starting.
The operator must be familiar with the use of personal computers in WINDOWS environment,
internally from which the NE application software operates.
TCO Suite and Craft Terminal applications are on one CD. Software Package (SWP) is on another
CD. Verify versions of the CD-ROM.
To properly install TCO Suite and Craft Terminal applications, a PC is required, having the
characteristics specified here below.
4.2.2 PC Characteristics
The PC to use for TCO Suite and Craft Terminal applications must meet following characteristics:
PC Hardware Configuration:
CPU: AMD Atlhon/Intel Celeron/Intel Pentium 4 or higher

RAM: 500 MB (1 GB recommended - strongly recommended with Windows Vista)
Hard Disk space: 1.5 GB (available space for log files, JRE excluded)
Display Resolution: 1024x768 pixel
CD-ROM Drive: 24X
Serial Interface: RS-232-C 9.6 to 57.5 Kbps
Ethernet Interface: Ethernet Card 10/100 Mbps
Operating Systems Supported:
Microsoft Windows XP Professional service pack 3 or Microsoft Windows Vista Ultimate service pack
2
Additional requirements:
Microsoft Internet Explorer 6 SP1, 7, 8, Mozilla Firefox 2, 3, 3.5

Standard user can be used to run the applications, but for TCO Suite use the Administrator password
is needed
Java Runtime Environment (JRE) 6 Update 14
Disable all Firewall software on PC used

4.2.3 Download Software Package (SWP) to PC
Follow these steps to download the Software Package (SWP) to the PC.
[1] Insert the SWP CD into the CD-ROM drive.
Note
The Software Package will auto-run and open up the computer's default browser program (if auto-run fea-
ture is enabled on user's PC) as soon as the CD-ROM is read by the PC. If auto-run does not start, user
must run (double-click with left mouse button on it) the Start.exe file, available on CD-ROM root, in order
to launch the Software Package.
Note
This certificate is not signed by a public/trusted certification authority. The Warning Security dialog (see
screen below) will inform the user about this problem and browser/JRE will probably recognize the sig-
nature as "not valid". This is neither an error nor a problem. If the dialog message specifies that the sig-
nature cannot be verified, it means the signed applet is correct but that the signature cannot be publicly
checked on the Internet. As usual, both language and graphical layout could vary with respect to browser,
operating system version, operating system and browser languages and so on. To avoid further requests
it is suggested to confirm and "always trust " the stated certificate source.
This screen shows an example of these warnings: as wrote before, things can differ with respect to
language or graphics and so on.
[2] Click the Yes button to proceed with the Software Package local copy.

[3] Click on the Local Copy of Software Package button to copy the software to your local PC.
[4] Choose a directory location to install the Local Copy of Software Package. Click Open and OK to
begin the copy process.

The files will be copied from the CD to the PC and will create a directory named ECT.
[5] A successful copy message will display when all files have been copied. Click OK.
[6] Remove the SWP CD from the CD-ROM drive.

4.2.4 Download Craft Terminal (CT) and TCO Suite Software to PC
Follow these steps to download the CT/TCO Suite software to the PC.
[1] Insert the CT/TCO Suite CD into the CD-ROM drive.
Note
The CT/TCO Suite software will auto-run and open up the computer's default browser program (if auto-
run feature is enabled on user's PC) as soon as the CD-ROM is read by the PC. If auto-run does not start,
user must run (double-click with left mouse button on it) the Start.exe file, available on CD-ROM root, in
order to launch the Software Package.
Note
This certificate is not signed by a public/trusted certification authority. The Warning Security dialog (see
screen below) will inform the user about this problem and browser/JRE will probably recognize the
signature as "not valid". This is neither an error nor a problem. If the dialog message specifies that the
signature cannot be verified, it means the signed applet is correct but that the signature cannot be publicly
checked on the Internet. As usual, both language and graphical layout could vary with respect to browser,
operating system version, operating system and browser languages and so on. To avoid further requests
it is suggested to confirm and "always trust" the stated certificate source.
This screen shows an example of these warnings: as wrote before, things can differ with respect to
language or graphics and so on.
[2] Click the Yes button to proceed with the CT/TCO Suite software local copy.

[3] Click on the Advanced Settings button below.
[4] Select one of the three Advanced Settings options to copy software to the PC.
Java JRE Package Installation (par. 4.2.4.1 on page 435)
Local Copy of WebEML (JUSM/CT) (par. 4.2.4.2 on page 435)
Local Copy of TCO Suite (par. 4.2.4.3 on page 436)

4.2.4.1 Java JRE Package Installation
[1] Click on the Java JRE Package Installation button to install the Sun Java Runtime Environment
(JRE) 6 Update 3 version to your PC.
4.2.4.2 Local Copy of WebEML (JUSM/CT)
[1] Click on the Local Copy of WebEML (JUSM/CT) button to copy the WebEML software to your PC.
Choose the directory location and click Open and then OK.
[2] When the files have finished copying, this window will display. Click the OK button. The files will be
copied to a created directory named MPRE_CT_VXX.XX.XX (where the X's are the version num-
ber).
[3] An icon will be created on the desktop if the user clicked yes.

4.2.4.3 Local Copy of TCO Suite Installation
[1] Click on the Local Copy of TCO Suite button to install the TCO Suite software to your PC. Choose
the directory location and click Open and then OK.
Note
This software does not have to reside in a directory name with no spaces in the name. Microsoft Windows
defaults to the My Documents directory. It is recommended to install this software in the same location
as the WebEML software.
The files will be copied from the CD to the PC in a created directory.
[2] When the file has been successfully copied, click the OK button.

[3] The user has the option to create a shortcut link on the PC desktop. Click Yes or No.
An icon similar to this one will be created on the desktop if the user clicked yes.

4.2.5 Configure PC Network Card to Connect to NE
This example uses a Microsoft Windows XP Professional system.
[1] Connect a CAT 5/5E cable from the PC network card to NMS connector on Slot 1 Core-E card.
[2] Click on the START menu on the Windows desktop and open up the CONTROL PANEL.
[3] Open up the NETWORK CONNECTIONS. Highlight the network card as shown below.
[4] Dobule click on Properties to display the screen below and scroll down the list to highlight the Inter-
net Protocol (TCP/IP) line. Click the OK button.

[5] As default the DHCP server on the MPR is enabled. Set the PC to get automatically an IP address.

[6] If for any reason the DHCP server on the MPR has been disabled, enter the IP address of 10.0.1.3
for the PC network card as shown below. Click OK.
Note
The 10.0.1.3 IP address example shown below is derived from the default NE IP address (10.0.1.2) plus
1. If there is an IP address conflict within your network, increment the last number by two.
Note
It is suggested to keep enabled only one network connection on a PC.
[7] To check the connectivity between the PC and the NE, open up a DOS window or Command Prompt.
Click on the START menu on the Windows desktop and open up the RUN window as shown below.
[8] Type cmd and click OK to open up a DOS window.
The DOS window will display.

[9] In the DOS window, click the cursor after the > and type ping 10.0.1.2 to verify a connection between
the PC and the NE. The Ping statistics for the IP address 10.0.1.2 should display 4 packets sent and
and 4 packets received.
Note
The 10.0.1.2 IP address is the default NE IP address.

4.2.6 Download Software Package to NE
After the switching on of the equipment click on the MPRE-CT icon on your desktop.
The Server Access Configuration menu option in the menu bar allows the user to configure the FTP server
to be used to download the Software Package (SWP) to the NE.
[1] On the WebEML main screen, click on the SW Download dropdown menu and select Server
Access Configuration.
4.2.6.1 Server Access Configuration
The user has the choice of implementing Step 2 OR Step 3 below. Afterwards, continue to Step 4.
[2] Enter the User Id and Password login information to access the FTP server. In the Address field,
write the IP address of the FTP server. In the Port field, write the port to be used and in the Root
Directory field, write the directory into which the software has been downloaded.
[3] Click the Set Default button and the screen below will appear showing the default configuration. The
CT is the default FTP server with the following parameters:
User Id: anonymous

Password
Address: Local host IP address
Port: 21
Root Dir: /

Note
The set default parameters can be changed by writing different values in the fields and then by clicking
on the OK button.
[4] Click the OK button.
4.2.6.2 Init SW Download
Warning:The download of a new software version takes time:

5 minutes for the Core-E unit
3 minutes for the PDH unit
20 minutes for the Modem unit
1 minute for the ASAP unit
30 seconds for the AUX unit
Warning: During the firmware download of the ASAP unit a Card Fail alarm will raise. The alarm is cleared
when the download is over. The duration of this alarm is 30 seconds approx.
[1] On the WebEML main screen, click on the SW Download dropdown menu and select Init SW Down-
load. This menu option allows the user to download software to the NE for initial downloads and
upgrades.
[2] Click the Add button to add the available software packages on the PC.

Note
Before the starting the software download it is recommended to set the RTPC mode to the maximum Tx
power.
[3] Browse to the directory where the NE software was installed and click the Open button.
[4] Highlight the description file (i.e. R95M.DSC) and click the Open button.

[5] Highlight the line as shown below and click on the Init Download button.
[6] Click the Yes button to begin the download process.

When the SW download starts, a screen showing the in progress operation of the download appears. The
download is aborted when the Abort button is pressed.
[7] Click Ok.
4.2.6.3 Software Status Detail
[1] On the WebEML main screen, click on the SW Download dropdown menu and select SW Status.
This screen shows the last two software versions details (par. 4.2.6.3.1 and par. 4.2.6.3.2) stored on
the NE. In this example, par. 4.2.6.3.1 shows the current committed software running on the NE. par.
4.2.6.3.2 shows the standby software or previous software.

4.2.6.3.1 Tab 1 Committed Software
This is the current software running on the NE.
4.2.6.3.2 Tab 2 Standby Software
This is the software that was downloaded above or was the previous SW version.
[2] Select Tab 2 and click on the Software Management Action drop down list.
[3] Select Activation from the Software Management Action drop down list.
[4] Click the Apply Action button to confirm the action.

[5] Click Confirm.
[6] Click OK.
[7] The card will reboot automatically with the new software in Tab 2 and will display this message. Click
OK.
Note
After the Core-E card reboots, the Tab 2 software version that was activated above (i.e. V01.00.15) will
be listed under the Tab 1 SW status detail and is the committed software running the NE. The previous
software (i.e. V01.00.00) will be listed under Tab 2 now.

5 Provisioning
The Provisioning can be performed by using:
WebEML (refer to paragraph 5.1 on page 449)
Provisioning tool (refer to paragraph 5.2 on page 489)
N.B. A feature, regarding the Ethernet traffic, can be implemented by using a configuration file, which
is written by using a set of low level commands provisioning in the proper way the different
devices of the different MPR cards. After an NE reset, the configuration file is applied, provi-
sioning the Ethernet switch and other devices to implement the desired feature.
5.1 Provisioning by WebEML
5.1.1 Start WebEML

1) Double click on the 9500MPR-E 1.4 WebEML icon on the Desktop.
2) Enter the IP Address or DNS name.
3) Click OK.
2 3
Figure 328. Network Element Overview

Provisioning 3DB 18528 DIAA Issue 1 449/578
4) If the Supervision is ongoing, click Show.
5) The application has been started pop-up will automatically close in a few seconds. The user
can click the OK but it is not necessary. The Login screen will appear.
6) Type your username must not be more than 20 characters.
7) Type your password must not be less than six (6) or more than 20 characters and must be
composed of full ASCII characters set (UPPER/lower case, numeric and special characters).
8) Click on Apply.
Figure 329. How to Login

450/578 3DB 18528 DIAA Issue 1 Provisioning
Note
Profile Types there are four user profiles defined.
Administrator (full access also for NMS local system security parameters).
CraftPerson: person in charge for installation and the mantenance at radio site; full access to NE but
not for security parameters, only for own password.
Operator (person in charge to operate at the network level, not at the radio side).
Viewer (view screens only).
Note
Default User Accounts at the NE installation time, two default user accounts
are created on NE independently from the SNMP operating mode.
Profile: administrator
Username: initial
Password: adminadmin
Profile: craftPerson
Username: Craftperson
Password: craftcraft

5.1.2 Provisioning
Note
Changes to provisioning do not have to be made in any particular order.
Click on Provisioning. Check current provisioning and change as required.

See Figure 330. for recommended sequence.
Start
Enable Plug-In Cards (par. 5.1.2.1)
Provision Plug-In Cards (par. 5.1.2.2)
Provision Synchronization (par. 5.1.2.3)
Provision NTP protocol (par. 5.1.2.4)
Provision NE Time (par. 5.1.2.5)
Provision VLAN (if required)

(par. 5.1.2.6)
TDM Cross-Connections
(par. 5.1.2.7)
ATM Cross-Connections
(par. 5.1.2.8)
AUX Cross-Connections (if

required) (par. 5.1.2.9)
Provision System (par. 5.1.2.10)
Provision management parameters

(par. 5.1.2.11 to par. 5.1.2.15)
Figure 330. Provisioning sequence

5.1.2.1 Enable Plug-In Cards
MSS E1 Access Card and Modem Card have to be enabled in order to communicate what type of card
is in what MSS slot to the microprocessor in the Core-E Card. This is accomplished on the Settings screen
for that card. The Core-E Card in MSS slot 1 is enabled by default. The ODU is enabled concurrently with
the associated Modem Card. The Fan Unit must be enabled.
Enable MSS modules using the following procedures. See Figure 331. through Figure 341.
5.1.2.1.1 Enable SFP optical plug-in
See Figure 331. Follow the steps to enable the optional SFP plug-in for the optical 1000 Mb/s Ethernet
interface.
Figure 331. Enable SFP optical plug-in

5.1.2.1.2 Enable Spare Core-E Card
See Figure 332. Follow the steps to enable the Spare Core-E Card in slot 2.
Figure 332. Enable Spare Core-E Card

5.1.2.1.3 Enable E1 Access Card
See Figure 333. Follow the steps to enable the E1 Access Card(s).
Figure 333. Enabling E1 Access Card

Figure 334. Enabling E1 Access Card on the same row (to implement protected configuration)

Figure 335. Enabling E1 Access Card protection

5.1.2.1.4 Enable Modem Card
See Figure 336. Follow the steps to enable the Modem Card(s).
Note
ODU is automatically enabled when Modem Card is enabled.
Figure 336. Enabling Modem Card

Figure 337. Enabling Modem Card on the same row (to implement protected configuration)

Figure 338. Enabling Modem Card protection

5.1.2.1.5 Enable ASAP Card
See Figure 339. Follow the steps to enable the ASAP Card.
Figure 339. Enabling ASAP Card

5.1.2.1.6 Enable AUX Card (option)
See Figure 340. Follow the steps to enable the AUX Card.
Figure 340. Enabling AUX Card

5.1.2.1.7 Enable Fan Unit
See Figure 341. Follow the steps to enable the Fan Unit.
Figure 341. Enabling Fan Unit

5.1.2.2 Provision Plug-In Cards
See Figure 342. through Figure 351. to provision MSS plug-in card parameters after the cards have been
enabled.
5.1.2.2.1 Provision Core-E Card
See Figure 342. Follow the steps to provision Ethernet ports 1-4.
Double Left
Click
1
2
Current provisioning for Ethernet Ports #01 - #04.
Area updates when Apply buttons are clicked.
Click this Apply Check to enbale NE auto-

button. negotiation functions.
4 6
Check to enable the
selected port. Uncheck 5
Check to allow
to disable first in order to
communication at
change any settings. the selected data
3 rate between two
locations. Choose
Check to enable input
half duplex for only
and output pause
one direction at a
features. time, or full duplex
7 for communication
in both directions
8 at the same time.
For the configuration
refer to the Core unit
menu.
9 11
10
Check to enable Click this Apply Check to enable the
the Synch-E button. Master/Slave operation
Figure 342. Core-E Card Provisioning (Ethernet ports 1-4)

See Figure 343. Follow the steps to provision Ethernet port 5 (available if the optional SFP plug-in has
been installed and enabled in the Core-E unit).
Double Left
Click
1
Click this Apply button.

4
2 Current provisioning for Ethernet Ports #05.
Area updates when Apply buttons are clicked. Check to enbale NE auto-
negotiation functions.
5
Check to enable the
selected port. Uncheck
to disable first in order to The Optical
change any settings. Info field is a
3 read-only
Check to enable input field not
and output pause implemented
features. in the current
6 release.
7
For the configuration
refer to the Core unit
menu.
8 9
Check to enable Click this Apply
the Synch-E button.
Figure 343. Core-E Card Provisioning (Ethernet port 5)

5.1.2.2.2 Provision E1 Access Card TDM2TDM
See Figure 344. Follow the steps to provision E1 lines (ports) 1-32.
Double Left
Click
1
3
See
details
5
6 Choose TDM2TDM if
Flow ID number 4 7 radio is being used to
required to transport transport E1 data only
E1 data. (no Ethernet).
Flow ID number is system unique and must not be

repeated in radio network. Loss of E1 data can occur.
Figure 344. E1 Access Card Provisioning TDM2TDM

5.1.2.2.3 Provision E1 Access Card TDM2ETH
See Figure 345. Follow the steps to provision E1 lines (ports) 1-32.
Double Left
Click
1
3
See
details
7 4 9
Flow ID number 8
required to transport
E1 data.
Flow ID number is system unique and must not be

repeated in radio network. Loss of E1 data can occur.
Figure 345. E1 Access Card Provisioning TDM2ETH

Select Disabled if port (E1 line) is not:
being used as a source or destination (typical
choice for a line not being used at a terminal or not
being dropped and inserted at a repeater);
being dropped or inserted (typical choice for a line
being passed through at a through repeater and
not being dropped and inserted at a drop and insert
repeater).
Select Framed:
to be able to collect the performances at the input
in Tx side and at the output in Rx side.
Signal Mode. Select Unframed:
Configures line format. Allows user being used as a source or destination (typical
to choose if line is dropped and choice for a line being used at a terminal);
inserted (by selecting Framed/ being dropped or inserted (typical choice for a line
Unframed) or passed through or being dropped and inserted at a drop and insert
not used (by selecting Disabled) repeater)
4
Figure 346. Access Card Details

5.1.2.2.4 Provision Modem Card
See Figure 347. and follow the steps to provision the Modem Card for Presetting Mode.
See Figure 349. and follow the steps to provision the Modem Card for Adaptive Modulation mode.
Figure 347. Modem Card Provisioning, Presetting Mode (Sheet 1 of 2)

Figure 348. Modem Card Provisioning, Presetting Mode (Sheet 2 of 2)
Note
When the Mode is changed from Presetting to Adaptive Modulation, the radio defaults to 14 MHz band-
width at 4 QAM. If the capacity of the radio (number of E1 lines cross connected) exceeds the available
capacity of a 14 MHz Channel at 4 QAM, Adaptive Modulation will not enable. It may be necessary to per-
form one of the following provisioning changes:
1. Reduce the quantity of E1 lines being transported to meet the required capacity.
2. Increase Reference Channel Spacing.

Figure 349. Modem Card Provisioning, Adaptive Modulation Mode (Sheet 1 of 3)



5.1.2.2.5 Provision ASAP Card
See Figure 352. and follow the steps to provision the ASAP Card.
Figure 352. ASAP Card Provisioning
The configuration of the ASAP unit is divided in four tab-panels:
E1 Layer
IMA Layer
ATM Layer
ATM PW Layer
For the configuration of the tab-panels refer to paragraph 3.14 on page 272.

5.1.2.2.6 Provision AUX Card
See Figure 353. and follow the steps to provision the AUX Card.
Figure 353. AUX Card Provisioning
The configuration of the AUX unit is divided in two tab-panels:
Settings
External Points
For the configuration of the tab-panels refer to paragraph 3.16 on page 290.

5.1.2.3 Provision Synchronization
All the NEs radios in the network must be synchronized to the same clock. One radio in the network is
provisioned Master. All other radios in the network must be provisioned Slave. The slave radios all sync
to the clock provided by the master.
5.1.2.3.1 Normal Operation
During normal operation, the master can be provisioned to get synchronization clock from two separate
sources: an internal local oscillator (most common source) or external clock from customer provided
equipment. The slave radios can be provisioned to receive the synchronization clock from one of two
sources: clock recovered by the radio receiver or the synchronization clock from another radio in the
network. Normally at a repeater, the synchronization clock is received over the RF path and recovered
by the radio receiver. A typical slave terminal uses the clock from an adjacent radio. See Figure 354. for
typical master terminal provisioning. See Figure 355. for typical slave terminal provisioning.
5.1.2.3.2 Failed Primary Operation
With the exception of the master when the radio is provisioned to synchronization off the local oscillator,
the provisioned secondary synchronization source is enabled if the primary source fails. When the master,
provisioned to accept synchronization clock at the Core-E from an external source, fails, the internal free-
running local oscillator is enabled. Provisioning choices for the secondary source for slave radios are
dependent upon the choices made from the primary source.
5.1.2.3.3 Sync Switching
With the exception of the master when the radio is provisioned to synchronization off the local oscillator,
the synchronization clock source is switched from primary to secondary if the primary source fails.
Synchronization clock switching provisioning is dependent on the role of the radio in the network (master
or slave) and on user preference. A revertive switching feature is a provisioning option that restores the
synchronization clock to the original source when the alarm on the primary source is cleared. If revertive
switching is not selected, the secondary synchronization source will continue to provide synchronization
clock, and if the secondary source fails, must be manually switched to the primary source.

Figure 354. Provisioning Master with Free Run Local Oscillator as Primary Source

Figure 355. Provisioning Slave with Radio Port as Primary Source

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

5.1.2.5 Provision NE Time
The user can provision either the operating system (PC/laptop) or Network Time Protocol (NTP) servers
to manage time and date stamping functions. Time and date provisioning is accomplished using the NE
Time Configuration screens. See Figure 357. and follow the steps to provision Network Equipment Time.
Click to display pop-up dialog

for NE Time configuration.
If NPT Protocol is disabled,

when checked, enables func-
tion to synchronize Operating
System and Network Equip-
ment Times.
3
Figure 357. NE Time Provisioning

5.1.2.6 Provision VLAN (if required)
To provision the VLAN management, if required, refer to par. 3.18 on page 335.
5.1.2.7 TDM Cross-Connections
The cross-connections screen is used to configure switching of packetized data through the Core-E Card.
The valid cross-connections are:
PDH to RADIO
PDH to ETH
ETH to RADIO
RADIO to RADIO
To create the TDM cross-connections refer to par. 3.4.5.3 on page 163.
5.1.2.8 ATM Cross-Connections
The cross-connections screen is used to configure switching of packetized data through the Core-E Card.
The valid cross-connections are:
ASAP to RADIO
RADIO to RADIO
RADIO to ETH
ASAP to ETH
To create the ATM Cross-connections refer to par. 3.4.5.5 on page 176.

5.1.2.9 AUX Cross-Connections
From the Configuration menu select AUX Cross-Connections.
Valid Cross Connections:
Local User Service Cross-Connection
Pass-through User Service Cross-Connection
Figure 358. Auxiliary Cross Connections menu

5.1.2.10 Provision System
See Figure 359. Follow the steps to provision the system parameters as explained in par. 3.4.4 on page
153.
Figure 359. System Setting

5.1.2.11 Provision Local NE IP Address
See Figure 360. Follow the steps to enter the NE IP address, allowing the network to communicate with
the NE.
Click to display pop-up dialog

for the IP configuration.
4
Enter NE IP Address.
5
Apply the IP Address.
Note
After IP address change, the NE restarts.
Figure 360. Local Configuration Provisioning

5.1.2.12 Provision TMN Ethernet Port
See Figure 361. Follow the steps to provision TMN Ethernet Port on the Core-E unit.
4
Enable TMN Ethernet
5
Enter IP address
6 7
Select Static Routing for manual routing. Enter IP Mask and
Select OSPF (Open Shortest Path First click on Apply
protocol) for automatic routing.
Figure 361. TMN Ethernet Port Configuration Provisioning

5.1.2.13 Provision Ethernet Port 4 for TMN (if required)
See Figure 362. Follow the steps to provision Ethernet Port 4 for TMN on the Core-E unit to carry SNMP
data.
4
Enable the TMN
Port 4
5
Enter IP address
6 7
Select Static Routing for manual routing. Enter IP Mask and
Select OSPF (Open Shortest Path First click on Apply
protocol) for automatic routing.
Figure 362. Ethernet Port 4 Configuration Provisioning

5.1.2.14 Provision IP Static Routing
See Figure 363. Follow the steps to provision.
Click now to display pop-up dialog for

the IP Static Routing Configuration.
Route to specific IP address
5
Input IP Address. IP Mask.
6 7
8
IP interface to a host or network.
Typically used to a spur to
interface a host over the RF path.
In this scenario, the Default
Gateway IP Address is 0.0.0.0
9
List of RF path
and the IP Mask (greyed out) is
directions.
0.0.0.0. Also typically used at an
Click to view
end terminal in a radio link for
drop down list.
interface with the network.
Create new or change

10
existing IP static routes.
Figure 363. IP Static Routing Provisioning

5.1.2.15 Provision OSPF Static Routing
See Figure 364. Follow the steps to provision Open Shortest Path First (OSPF) protocol static (automatic)
routing.
Figure 364. OSPF Static Routing Provisioning

5.2 Provisioning by Provisioning tool
5.2.1 Start Provisioning tool

Create and modify provisioning files using the Provisioning Tool.
[1] Double click on the mpreSuitexxx icon on the Desktop.
[2] Click on the Provisioning Tool button.
Start provisioning
See Warning below
Figure 365. TCO Main Menu
Warning: When quit the Provisioning Tool application or Alarms & Settings application always click on
Close Current session to restore the correct network setting in the PC.
Select:
to run the provisioning tool for MPR 1.4.0 or previous releases (in the lower part of the screen)
the direct connection to the NE by putting a check mark on Connect to NE, by entering the IP
address and by clicking on Apply.
Note 1: in the default configuration the DHCP Server is enabled. For this reason in the Properties
panel of the Internet Protocol (TCP/IP) the PC settings must be Obtain an IP address automatically.
In this case in the Connect to NE field is written the IP address of the NE and this address cannot
be changed.
Note 2: If the DHCP server is disabled, the IP address to be entered is the IP address of the NMS
Ethernet port.
or
the off-line configuration by putting a check mark on Do not connect to NE and by clicking on
Apply.

Figure 366. Provisioning Tool Connectivity
Figure 367. Provisioning Tool Connectivity
After loading the JRE package, the screen in Figure 368 will display, if you are working off-line or the
screen in Figure 369, if you are directly connected to the NE.

Figure 368. Provisioning Tool Screen (off-line working)
Figure 369. Provisioning Tool Screen (direct connection to the NE)

5.2.1.1 Configuration Screen Options
The screen below is a generic one that depicts all of the pull-down options possible depending on which
card is selected in the card slot. Protections options shown below are for all cards. See the screens shown
below for more information.
Warning: The Provisioning Tool allows to configue all the units, except the ASAP and AUX units. (The
ASAP and AUX units must be configured with the LCT).
Warning: To configure the equipment extract the ASAP and/or AUX units, if any.
Protections options
for the Core cards
Protections options
shown for Slot 3
and Slot 4
Protections options
shown for Slot 5
and Slot 6
Figure 370. Configuration Options Screen

Note:
A white icon indicates that there are no cross-connec-
tions, but cross-connections can be created.
A blue icon indicates the destination is full. The limits
granted by the license key have been exceeded. A mes-
sage is also displayed stating that no more E1 ports will
be accepted. When checked this feature
A green icon indicates that the source and destination
are available and the destination can accept more E1 enables input and output
ports. pause features
Check to enable Check to enable

E1 Access Ethernet Icon the selected port auto negotiation
Card Icon
Radio Access
Card Icon
Check to allow communication Check to allow Select Transport if ETH Port

at data rate in both directions communication at 4 on the Core Card is used
at the same time data rate but in to transport Ethernet data
only one direction
at a time
Select TMN if ETH Port
4 on the Core Card is
used for SNMP data
Figure 371. Core-E Configuration (Sheet 1 of 2)

The Quality Of Service feature enables priority forwarding
in the Core Card switch based on how the packets are
tagged: not tagged or tagged 802.1p or DiffServ. For general
traffic, the packets are not tagged and QOS can be disabled.
The user has to know if the packets are tagged, and if tagged
802.1p or DiffServ in order to know which QOS function to
chose.
Check to
enable the
Admission
Control
Check to enable the Each packet is classified

optical SFP plug-in based on presence of valid
802.1p user priority tag
Check to enable the Check to select the Each packet is based on

Synch-E operation mode DSCP field in IP header
to determine priority
Priority forwarding
disabled
Figure 372. Core-E Configuration (Sheet 2 of 2)

The purpose of TMN Clock Source provi-
sioning is to select the mode that will be
Flow ID is unique to network. used to sync TDM E1 data to the node Syn-
No two Flow IDs in a network chronization source. The user can select
can be the same one of modes: Adaptive, Differential.
Select Adaptive to sync TDM output to pack-
ets.
Choose TDM2ETH if radio is
Select Differential to sync TDM output to NE
being used to transport just
Synchronization source
Ethernet or Ethernet plus E1 data
Rx Over-the-hop ID. Must
Choose TDM2TDM if radio match Rx/Tx ID at other end
is being used to transport E1
data only (no Ethernet) Tx Over-the-hop ID
Select Unbalanced 75 ohm if Select Balanced 120 ohm if Check to enable

tributary cable is coax tributary cable is twisted pair the Node Timing
Note
With the TDM2TDM service profile the TDM Clock source is fixed to Differential (RTP - Real Time
Protocol is used); with the TDM2Eth service profile the TDM Clock source can be Differential
(RTP - Real Time Protocol is used) or Adaptive (RTP is not used). In the unit it is not possible to have
mixed configurations with service profiles using RTP and other service profiles not using RTP.
Example: if in the unit only one E1 has service profile TDM2TDM it is possible to configure other E1
with service profile TDM2Eth only with the Differential clock source (not with the Adaptive clock
source). If the Adaptive clock source is requested the E1 must be connected to another PDH unit.
Figure 373. E1 Configuration

Enter number from 1 to 255
for Receiver ID. Must match Check to enable PPP RF port.
associated Receiver ID at The user can select:
other end of hop. - Static routing or
- OSPF Area
Select the modulation
Enter number from 1 to 255 for scheme.
Transmitter ID. Must match
Select the suitable refer-
associated Transmitter ID at
ence channel spacing. Select Revertive feature if you want
other end of hop.
traffic on the protection channel to
automatically switch back to the
Check to enable radio No check
main channel when alarms clear or a
ID mismatch function. mark here.
switch command is released.
Enter the ATPC Select Tx (Go) and Rx (Return)

Check to
parameters. separation frequency from
enable ATPC.
drop-down list.
Enter the Tx
Power Enter the Tx RF
frequency within
the allowed range.
Figure 374. Radio Provisioning (without Adaptive Modulation)

Enter number from 1 to 255
for Receiver ID. Must match
associated Receiver ID at
Check mark to enable the
other end of hop.
Adaptive Modulation. The
only available configura-
Enter number from 1 to 255 for tion is: 1+1 HSB.
Transmitter ID. Must match
associated Transmitter ID at
other end of hop. Enable PPP RF port. Select Revertive feature if you want
The user can select: traffic on the protection channel to
- Static routing or automatically switch back to the
Check to enable radio - OSPF Area main channel when alarms clear or a
ID mismatch function. switch command is released.
Enter the Tx RF Select in the Reference Mode

frequency within field the spectral efficiency
class to be set as reference. Select in the Threshold field how
the allowed range. many dB the switching thresholds
Select Tx (Go) and Rx (Return) Select in the Reference Chan- have to be moved from the default
separation frequency from nel Spacing field the suitable value (+4 dB/-2 dB).
drop-down list. channel spacing. The default value is approx. 6 dB
below the 10-6 Rx threshold.
Enter the Tx Select in the Scheme field the
Power Modulation range (4/16 QAM
or 4/16/64 QAM) to be used by
the Adaptive Modulation.
Figure 375. Radio Provisioning (with Adaptive Modulation)

Secondary source:
- Synch-In Port
Clock from external source received on the
Sync In connector on the Core card.
- Any available E1
Clock from E1 source via E1 peripheral.
- Any available Synch-E
Clock from the User Giga Ethernet interface.
- Free Run Local Oscillator
Restoration Criteria: Local oscillator on Core Card.
- Revertive
Switches sync source back to primary source
after alarm on primary source clears. Primary source:
- Non-Revertive - Synch-In Port
Does not switch back to primary source after Clock from external source received on the
primary alarm clears and stays on secondary Sync In connector on the Core card.
sync source. - Any available E1
Synchronization Role: Clock from the User Giga Ethernet interface.
Master - Free Run Local Oscillator
Local oscillator on Core Card.
This field will appear, if as Synch-Out Port configuration This field will appear, if as Source (Primary or
Source (Primary or Second- Connector that can be used to Secondary) has been selected the Any
ary) has been selected the provide sync to another radio or available E1.
Synch-In port: 1.024 MHz, ancillary equipment: 1.024 MHz, Select the slot number and the E1 tributary
2.048 MHz, 5 MHz, 10 MHz. 2.048 MHz, 5 MHz, 10 MHz. number.
Figure 376. Synchronization Configuration (Master)

Secondary source:
- Synch-In Port
- Any available E1
Clock from the User Giga Ethernet interface.
- Free Run Local Oscillator
Local oscillator on Core Card.
Primary source:
- Synch-In Port
- Any available E1
Synchronization Role: Clock from the User Giga Ethernet interface.
Slave - Rx Symbol Rate
Clock extracted from the radio side.
This field will appear, if as

Primary Source has been This field will appear, if as
selected the Rx Symbol Source (Primary or Second-
Rate. Select the radio slot ary) has been selected the
to be used. Synch-In port: 1.024 MHz,
2.048 MHz, 5 MHz, 10 MHz.
Synch-Out Port configuration

This field will appear, if as Secondary Source
Connector that can be used to
has been selected the Any available E1.
provide sync to another radio or
Select the slot number and the E1 tributary
ancillary equipment: 1.024 MHz,
number.
2.048 MHz, 5 MHz, 10 MHz.
Figure 377. Synchronization Configuration (Slave)

Figure 378. Cross Connections Configuration (Sheet 1 of 6)






When the NE is configured in this mode (default configuration),
the Ethernet traffic is switched according to the destination
MAC address without looking the VLAN.
The packets from the user Ethernet ports having the VLAN ID
out the allowed range (0 and 2-4080) are dropped. The packets
having a VLAN ID already used for a TDM flow are accepted.
Figure 384. 802.1D management

VLAN 1 Management
VLAN-ID 1 is automatically defined by the NE
when the 802.1Q bridge type is selected.
When the NE is configured in this
VLAN-ID 1 is shown to the operator, but it can-
mode, the management of Ethernet
not be neither changed nor deleted.
traffic looking the VLAN is enabled.
All the user Ethernet ports (enabled and dis-
abled) and all the radio ports are members of
In this mode, one VLAN will be
the VLAN 1.
assigned to all Ethernet frames inside
In egress VLAN-ID 1 is always removed from
the MPR network.
all the ports.
ADD VLan: to create a new VLAN By clicking Next the Port VLan con-
(refer to Figure 386 - VLAN manage- figuration screen opens (Figure 387).
ment)
DEL VLan: to delete a VLAN-ID. It is possible to
EDIT VLan: to change the parameters remove a VLAN-ID from the VLAN-ID table even if
of a VLAN (VLAN name, VLAN member this VLAN-ID has been already configured on one
ports, VLAN untagged ports in egress). or more user ports as Port VLAN to be added in
ingress to untagged frames. As consequence, the
VLAN-ID=1 and PRI=0 are added to the untagged
frames received on this port. Before applying this
deletion, a confirmation of the operation is shown to
the operator.
Figure 385. 802.1Q management

[1] VLAN ID field: Enter the VLAN ID (the configurable values must be in the range 2 - 4080)
N.B.: The VLAN IDs already defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) can-
not be used.
[2] VLAN Name field: Enter the VLAN Name: a text string of up to 32 characters.
N.B.: There is no check on unambiguity name.
[3] VLAN Ports field: Select the ports members of this VLAN by putting a check mark on the relevant
check box. All the user Ethernet ports and all the Radio directions can be considered. Both
enabled and disabled user Ethernet ports (radio ports when declared are implicitly enabled) can
be member of a VLAN. This means that a disabled port can be configured as a member of a
VLAN and a port already member of a VLAN can be disabled continuing to be a member of the
same VLAN.
[4] Untagged Ports field: Select, among the ports belonging to this VLAN (members), the untagged
ports (in egress the VLAN will be removed from the frames). Only the user Ethernet ports,
enabled and disabled, are manageable. The VLAN cannot be removed from the radio ports (with
the exception of the VLAN 1).
N.B.: The VLAN-ID values allowed are in the range 2 - 4080. By default, for the VLAN IDs defined,
all the ports are members and the Untag flag is set to False, which means all the frames are trans-
mitted with Tag.
N.B.: Tagged frames

If one tagged packet with VLAN-ID X is received on a port which is not member of the VLAN-
ID X, the packet is dropped.
Figure 386. VLAN Management

Admit all frames (tagged frames with Admit tag frames only (only
VLAN ID values already defined in the tagged frames with VLAN ID
VLAN management menu are allowed in values already defined in the
ingress and untagged frames are allowed VLAN management menu are
in ingress). allowed in ingress).
Port VLAN ID and Priority: if the Acceptable Frame Type is set

to Admit all frames the VLAN-ID and Priority fields, to be added
in ingress to untagged frames, must be configured. Only VLAN-
ID values already defined (in the VLAN management menu) can
be configured for this purpose. The Priority values allowed are
in the range 0 - 7.
The default Port VLAN-ID and Priority values are: VLAN-ID=1;
PCP=0.
When the Port VLAN-ID value is different from the default value,
the relevant port is removed as member of the VLAN 1.
Figure 387. Port VLan configuration
Note
The Port VLan Configuration screen opens only if in the Bridge Configuration screen the 802.1Q (Virtual
Bridge) has been selected.

Enter local Enter IP Address
IP Address. for radio.
Select Static Routing for manual

Enter TMN VLAN routing. Select OSPF (Open
feature on Core. Shortest Path First Protocol) for
automatic routing.
Enable the NTP protocol.

Enter the IP address of the
Enter the IP address of the Spare (standby) NTP server.
Main NTP server.
Figure 388. Network Configuration

The default UDP Port is 5010, but The Manager Type cannot be
with a click on this column another changed (it is fixed to 5620 SAM).
port can be configured.
To activate a trusted manager click on Add Manager, To remove a manager select the manager from the list
then click on the IP Address column and write the IP and click on Remove Manager(s).
address of the SNMP manager. The multiple selection of different managers can be
To confirm the selection click Enter. done to remove more than one manager in one shot.
A Trusted manager is an SNMP manager to which the NE automatically sends the TRAPS generated
inside the NE.
Figure 389. Trusted Managers screen

Figure 390. Typical Report Panel

6 Maintenance and Trouble-clearing
6.1 Introduction
This section contains information and procedures to aid in restoring the equipment to its proper operating
condition after it has been determined that a problem exists.
The following warnings and cautions apply while operating, performance testing, troubleshooting, or
repairing the 9500 MPR-E series radios.
Short circuits in low-voltage, low-impedance dc circuits can cause

severe arcing that may result in burns or eye injury. Remove rings,
watches, and other metal jewelry while working with primary circuits.
Exercise caution to avoid shorting power input terminals.
Units with the electrostatic-sensitive (ESS) symbol contain ESS

devices. Store these units in an antistatic container when not in use,
and anyone handling a unit should observe antistatic precautions.
Refer to the Special Precautions pages in the front of the instruction
book for detailed handling information.
Note
Ensure that all antennas are properly aligned and waveguide is in

good physical condition.
Note
Before performing procedures that might in any way affect transmission,

it is recommended that the person performing the procedure
understand the Rules and Regulations pertaining to the equipment
and be properly authorized to operate the equipment.

Maintenance and Trouble-clearing 3DB 18528 DIAA Issue 1 513/578
6.2 Maintenance Philosophy
This section provides information and procedures for equipment maintenance down to the Card level.
Card repair is not covered in this manual.
The use of maintenance procedures in this section may result from failure of a periodic check, an alarm
indication, or unacceptable performance.
6.3 Personal Computer (PC)/Laptop

Connect the RJ 45 Interface cable between Craft Terminal connector on the Core-E Card and the PC.
6.4 Troubleshooting
This section provides guidance on:
Before Going to Site Checklist
Troubleshooting Basics
Troubleshooting Path Problems
Troubleshooting Configuration Problems
Troubleshooting Ethernet Problems
Troubleshooting TMN Problems
6.4.1 Before Going to Site Checklist

Where possible, before going to site obtain the following information:
Does the fault require immediate attention?
Determine who is the best-placed person to attend the fault.
Confirm the nature and severity of the reported fault, its location, 9500 MPR-E type, frequency band,
high/low end ODU, capacity modulation and configuration (nonprotected, protected, diversity). Ask:
Is just one 9500 MPR-E link affected, or a number of links in the same geographical area?
Is the path down completely or is traffic passing but with a BER alarm?
Is only one or a number of tributaries affected?
Could the fault be in the equipment connected to 9500 MPR-E, rather than in 9500 MPR-E?
Are there alarms on other, connected equipment?
Is it a hard or intermittent fault?
Do alarms confirm which end of an alarmed link is faulty?
Could the weather (rain, ice, high wind, temperature) be a factor in the reported fault?

514/578 3DB 18528 DIAA Issue 1 Maintenance and Trouble-clearing
Note
If the fault suggests a rain fade or other weather related fade

condition and it matches the prevailing weather conditions, do
not take any action until the weather abates.
Does link history suggest any fault trends?
Does the fault history for the link indicate a likely cause?
Is the 9500 MPR-E link newly installed?
Has there been any recent work done on the link?
Ensure that you have with you:
Appropriate spares. Where an equipment failure is suspected, these should include replace-
ment Cards/plug-ins and ODU. If an ODU is suspected then local/national climbing safety
requirements must be adhered to.
A laptop PC loaded with Craft Terminal, and an Ethernet cable. If an Ethernet connection is to
be used, you need the 9500 MPR-E Node/Terminal IP address and also the addresses for any
remote sites to be accessed.
If login security has been enabled, you need the engineer password for the local and also any
remote sites to be accessed.
Any special test equipment that may be needed, such as a BER tester.
Toolkit.
Key(s) for access to the site.
6.4.2 Troubleshooting Basics

This section provides general guidance on 9500 MPR-E troubleshooting:
Check front-panel LED indications. These provide summary alarm indications, which can help
narrow down the location and type of failure. Refer to Operation section for details.
Where a Status LED on a plug-in is off (unlit), but power to the MS is confirmed by LEDs on
other plug-ins, check the seating of the affected plug-in.
Check Main Screen. When logging into 9500 MPR-E with Craft Terminal, the opening screen is the
Main Screen. Use the information provided in menu Diagnosis Alarms NE alarms and in
menu Diagnosis Log Browsing Event Log to check for severity and problem type. Refer to
Table 19. - Alarm Matrix, for probable cause and recommended action.

Table 19. Alarm Matrix
Configuration/
Alarm
Equipment Alarm Description Most Probable Cause Action
1+0 1+1
EPS
Core-E Card Card Fail Major Minor Core-E card failed Replace Core-E Card
Equipment Mismatch N/A Minor Card in slot does not match Install correct configured
card configured in Core-E card
memory
Card Missing N/A Minor Core-E card is missing from Install Core-E Card in slot
slot
SFP missing alarm Major Minor The SFP optional plug-in is Install the plug-in in the
provisioned, but not present SFP slot
Unconfigured Equip- N/A Minor Card in slot is not provi- Provision card
ment sioned (enabled)
LOS on ETH TMN Minor Minor No Ethernet input signal Check link partner and
Interface detected on ETH 4 on Core- cable between link partner
E Card and ETH 4 connector
PPP IP Fail Minor Minor
LOS on Gigabit ETH Major Minor Loss of Ethernet is detected Check link partner and
Interface on ETH 1-4 on Core-E Card cable between link partner
and ETH 1-4 connector
Firmware Download Minor Minor Status of download Wait for downloading to

In Progress complete
LOS on Sync Inter- Minor Minor No sync clk detected at Check sync source and
face Sync in port on Core-E Card cable between sync
source and Sync in port
Degraded Signal on Minor Minor Sync clk errors detected at Check sync source for
Sync Interface Sync in port on Core-E Card errors
License Mismatch for Major Major Wrong flash card installed Install correct flash card
Equipment Provi- on Core-E Card for license
sioned
Underlying Resource Major Major On detection of card failure Replace Core-E card
Unavailable (URU) the E1 port, Ethernet port,
Radio port objects emit a
communication Alarm notifi-
cation showing the trans-
mission resources are
affected by the equipment
failure

Configuration/
Alarm
1+0 1+1
EPS
E1 Access Card Fail Major Minor Failure of E1 Access Card Replace E1 Access Card
Card
Equipment Mismatch Major Minor Card in slot does not match Install correct configured
Card configured in Core-E card
memory
Card Missing Major Minor E1 Access Card is missing Install E1 Access Card in
from slot slot
Unconfigured Equip- Major Major Card is not Enabled on the Enable card
ment Settings screen
LOS on PDH Tribu- Major Minor No E1 input signal detected Check E1 source and/or
tary on any one or more of 32 cable
lines
Degraded Signal Minor Minor Low quality sync signal for Replace E1 Access Card
E1 Access Card
AIS on PDH Tributary Major Major AIS detected by the receive Check for upstream E1
(RX) circuits on one or more E1 source for errors
lines, indicating upstream
failure
AIS on PDH Tributary Major Major AIS detected on one or Check E1 source
(TX) more E1 lines at input to
PDH 32xE1 Access Card
Loss of CESoETH Major Major Packets are not being 1. Check/troubleshoot

Frame received by the emulation farend alarms
circuits 2. Replace alarmed E1
Access Card
Firmware Download Minor Minor Status of download Wait for downloading to

Underlying Resource Major Major On detection of card failure Replace E1 Access card
Unavailable (URU) the E1 port objects emit a
failure
16E1DS1 ASAP Card Fail Major - Failure of ASAP Card Replace ASAP Card
Card
Equipment Mismatch Major - Card in slot does not match Install correct configured
Card configured in Core-E card
memory
Card Missing Major - ASAP Card is missing from Install ASAP Card in slot
slot

Configuration/
Alarm
1+0 1+1
EPS
Unconfigured Equip- Major - Card is not Enabled on the Enable card

Firmware Download Minor - Status of download Wait for downloading to

Loss Of Signal (LOS) Major - Loss of signal on each Check E1 source and/or
incoming E1 signal cable
(detected according to ITU-
T G.775-sect.4)
Tx Alarm Indication Major - Alarm Indication Signal Check E1 source

Signal (Tx AIS) detected on each incoming
E1 signal (Tx side)
T G.775-sect.4)
Loss Of Frame (LOF) Major - Loss of frame on each Check to CRC4 multi-
incoming E1 signal frame alignment of the Far
(detected according to ITU- End equipment
T G.706-sect.4)
Loss of Cell Delinea- Major - Loss of ATM cell delineation Check the ATM scram-
tion (LCD) on each incoming E1 signal, bling of the Far End equip-
when the E1 port is used as ment
physical layer for ATM
T I.432)
Loss of IMA Frame Major - Loss of IMA Frame on each Check the IMA configura-
(LIF) incoming E1 signal, when tion of the Far End equip-
the E1 port is used as IMA ment
link (detected according to
IMA Standard AF-PHY-
0086.000)
Link Out of Delay Major - It reports the event that, Check the synchroniza-
Synchronisation when the E1 port is used as tion of the Far End equip-
(LODS) IMA link, it is not synchro- ment
nized with the other links
within the IMA group
(detected according to IMA
Standard AF-PHY-
0086.000)
RDI/Link Failure Major - It reports, when the E1 port Check the Far End equip-
is used as IMA link, the OR ment
of other alarms that are fore-
seen by IMA Standard AF-
PHY-0086.000:
RFI-IMA
Tx-Mis-Connected
Rx-Mis-Connected
Tx-Unusable-FE
Link Rx-Unusable-FE

Configuration/
Alarm
1+0 1+1
EPS
IMA Group Trail Sig- Major - It reports, for a configured Check the Far End equip-
nal Fail (TSF) IMA Group, the event that its ment
Group Traffic State Machine
is 'down', that is NE and FE
Group State Machine are
both NOT in "operational"
state (IMA Standard AF-
PHY-0086.000)
IMA Group TSFAlarm is
also generated by OR of the
following alarms (IMA Stan-
dard AF-PHY-0086.000):
Tx-Unusable-FE
Link Rx-Unusable-FE
Group Start-up-FE
Group Config-Aborted
Group Config-
Aborted-FE
Group Insufficient-
Links
Group Insufficient-
Links-FE
Group Blocked-FE
Group GR-Timing-
Mismatch
Underlying Resource Major Major On detection of card failure Replace 16E1DS1 ASAP
Unavailable (URU) the E1 port objects emit a Card
failure
Fans Unit Card Fail Major Fan failed Replace fan unit
Card Missing Major Fan unit is missing from slot Install fan unit
Unconfigured Equip- Minor Minor Unit is not Enabled on the Enable fan unit

Table 20. Modem Card Alarm Matrix
Configuration/Alarm

1+0 1+1 1+1
HS FD
Modem Card Card Fail Major Minor Minor Modem Card failed Replace Modem Card
Equipment Mismatch Minor Minor Minor Card in slot does not Install correct config-
match card configured ured card
in Core-E memory
Card Missing Major Minor Minor Modem Card is missing Install Modem Card in
from slot slot
Unconfigured Equip- Minor Minor Minor Card is not Enabled on Enable card
ment the Settings screen
PNU Cable Loss Major Minor Minor Bad cable connection Check/repair IF cable
at IF in/out connector connection on alarmed
on Modem Card Modem Card
Loss of Radio Frame Minor Minor Minor Farend XMTR prob- 1. Switch farend XMTRs
lems, RF path prob- (in a protected system).
lems, or local circuit If alarm clears, replace
failures have caused farend off-line Modem
BER to increase to the Card.
point that frames are 2. Check/troubleshoot
being lost farend alarms
3. Replace alarmed
Modem Card
Loss of Alignment N/A Minor Minor Delay between main 1. Replace main
and protect RF paths Modem Card
detected 2. Replace protect
Modem Card
3. Replace main ODU
4. Replace protect ODU
Demod Function Fail Major Minor Minor Internal receive circuit Replace Modem Card
failure
High BER Major Minor Minor Bit Error Rate threshold 1. Verify RF path is
(10E-4) exceeded on clear, antenna is
RCVR input circuits on aligned, and no existing
modem weather-related prob-
lems
2. Verify RSL is above
RCV threshold. a). If not
check upstream
XMTR output/trouble-
shoot XMTR. b). If ok,
Early Warning N/A Minor Minor 10E-9 BER detected No action is required at
this time. Monitor
receive signal for
increased degrading

Configuration/Alarm

1+0 1+1 1+1
HS FD
Link Identifier Mis- Major Major Major Link identifier number Set numbers at both
match provisioned on Modem ends of hop to match
Card settings screen is
different from link iden-
tifier number provi-
sioned at other end of
hop
TCA on Radio Link N/A N/A Major Alarm threshold Switch farend XMTRs
exceeded on standby (in a protected system).
Modem Card If alarm clears, replace
farend off-line Modem
Card
TCA on Radio Hop Major N/A Minor Alarm threshold

exceeded on standby
Modem Card after
switching from main to
standby
UAT on Radio Link N/A N/A Major 10 consecutive SES Switch farend XMTRs
(unavailable time (in a protected system).
period) detected on If alarm clears, replace
main Modem Card farend off-line Modem
Card
UAT on Radio Hop Major N/A Minor 10 consecutive SES

(unavailable time
period) detected on
standby Modem Card
after switching from
admin to standby
Firmware Download Minor Minor Minor Download status Wait for downloading to
Degraded Signal Minor Minor Minor Low quality sync signal Replace Modem Card
from Modem Card
License Mismatch for Major Major Major Modem card type does Replace Modem Card
Equipment Provi- not match card type with correct card type
sioned stored in memory on
the Core-E Card flash
card
Underlying Resource Major Major Major On detection of card Replace Modem Card
Unavailable (URU) failure the Radio port
objects emit a commu-
nication Alarm notifica-
tion showing the
transmission
resources are affected
by the equipment fail-
ure

Configuration/Alarm

1+0 1+1 1+1
HS FD
ODU Card Fail Major Minor Minor ODU failed Replace ODU
Equipment Mismatch Major Minor Minor ODU does not match Replace ODU
ODU configured in
Core-E memory
RCV Function Fail Major Minor Minor ODU RCVR circuit Replace ODU
failed
RF Frequency Mis- Major Minor Minor Frequency out-of- Re-configure frequency

match range of configured TX
frequency
Shifter Frequency Major Minor Minor Configured shifter Re-configure shifter

Mismatch value not supported by value
ODU
TX Power Mismatch Minor Minor Minor Configured TX power Re-configure TX power

value not supported by value
ODU
Software Mismatch Minor Minor Minor Software version on Download correct soft-
ODU does not match ware version
software version on
Core
ODU Not Responding Minor Minor Minor Loss of communication 1. Replace ODU
with ODU 2. Replace alarmed
Modem Card
Major Major Major Major On detection of card Replace ODU

failure the Radio port
objects emit a commu-
nication Alarm notifica-
tion showing the
transmission
resources are affected
by the equipment fail-
ure
EPS Equipment Protection Switching
LOS Loss of Signal
RPS Radio Protection Switching
TCA Threshold Crossing Alarm
UAT Un-Available Time
Check the basics first.
For example, if multiple alarms are present, and these include power supply voltage or hard-
ware alarms, always check their cause before looking at resultant down-stream path failure or
path warning (signal) alarms.

Similarly, if a path-related failure is indicated (no hardware or software alarms), investigate the
path. Go to the Craft Terminal History screen (15 minute view) to check supporting data, such
as low RSL and incidence of intermittent pre-failure BER alarms, which if present are evidence
of a path-related failure.
Check if symptoms match the alarm. Alarms reflect the alarm state, but in exceptional
circumstances an alarm may be raised because of a failure to communicate correctly with the alarm
source, or a failure in alarm management processing. Always check to see if symptoms match the
alarm, using LED indications and the Craft Terminal.
Check if recent work may be a cause. Recent work at the site may be a cause or contributing factor.
Check for a configuration change, software upgrade, power recycling (reboot), or other site work:
Many hardware alarms are only initiated as a loss-of-communications alarm during a reboot,
software upgrade, or reconfiguration. By not being able to communicate with the Core-E, their
settings cannot be loaded. The fault may be at the hardware device (most likely), communi-
cations to it, or the Core-E.
Hardware/software compatibility alarms will be raised when a new plug-in is installed that
needs a later version of 9500 MPR-E software.
Hardware incompatible alarms will be raised when a plug-in is installed in a slot that has been
configured for a different plug-in.
MSS before an ODU. If there is doubt about whether a fault is in the MSS or ODU, always replace
the MSS first; it is quicker and easier.
Hot-pluggable. MSS cards are hot-pluggable. There is no need to power-down before replacing,
but traffic will be lost unless the plug-in is protected.
Plug-in restoration time. Ensure adequate time is allowed for services to resume when a plug-in
is replaced.
6.4.3 Troubleshooting Path Problems

A path-related problem, with the exception of interference, is characterized by traffic being similarly
affected in both directions. Generally, if you are experiencing only a one-way problem, it is not a path
problem.
Note
A path extends from ODU antenna port to ODU antenna port.
Normally a path problem is signalled by a reduced RSL, and depending on its severity, a high BER.
Only in worst case situations, such as an antenna knocked out of alignment, will a path fail
completely, and stay that way.
For weather-related problems, such as rain or ducting, the path problem will disappear as the
weather returns to normal.

6.4.3.1 Path Problems on a Commissioned Link
A path problem on an existing link, one that has ben operating satisfactorily may be caused by:
Weather-related path degradation
If BER alarms are fleeting/not permanent and RSL returns to its normal, commissioned level after
the alarm is cleared, rain, diffraction, or multipath fading is indicated. Rain fade is the likely cause
of fade for links 13 GHz and higher. Diffraction and multipath/ducting for links 11 GHz and lower. If
these alarms are persistent, there could be a problem with the link design or original installation.
Changed antenna alignment or antenna feed problem
If RSLs do not return to commissioned levels after a period of exceptionally strong winds, suspect
antenna alignment. Also, check the antenna for physical damage, such as may occur with ice-fall.
For a remote-mounted ODU, check its antenna feeder.
New path obstruction
Where all other parameters check as normal, and the path has potential for it to be obstructed by
construction works, view/survey the path for possible new obstructions.
Interference from other signal sources
Interference usually affects traffic in just one direction. Unlike other path problems, RSL is not
affected. If suspected, check for new link installations at, or in the same geographical area, as the
affected site. Ultimately, a spectrum analyzer may have to be used to confirm interference, which
is not an easy task given the need to connect directly to the antenna port, after removing the ODU.
6.4.3.2 Path Problems on a New Link
For a new link, potential problems can extend to also include:
Incorrect antenna alignment
One or both antennas incorrectly aligned. Refer to Installation alignment procedure on CD.
Mismatching antenna polarizations
Given a typical polarization discrimination of 30 dB, for most links it is not possible to capture a signal
to begin the antenna alignment process.
Incorrect path calculations
If the RSLs are too low or too high, antenna alignment is correct, and Tx power settings are correct,
check the path calculations used to determine the link performance. A good calculation match is +/
- 2 dB. Disagreements in excess of 3 dB should be investigated.
Reflections
Reflection (path cancellation) problems may not have been picked up at the path planning stage, par-
ticularly if the survey was a simple line-of-sight. If suspected, resurvey the path.

6.4.4 Troubleshooting Configuration Problems
Configuration problems should only occur during the setup of a new link, or reconfiguration of an existing
link. The more common problems may be broadly categorized as:
Compatibility Problems
The two alarms that may activate are Configuration Not Supported and SW/HW Incompatible:
Configuration Not Supported: The plug-in installed is not enabled or is incorrect for the con-
figuration.
SW/HW Incompatible: Typically raised when new hardware is plugged into an existing MSS
that has software from an earlier release. To remove the alarm, compatible 9500 MPR-E soft-
ware is required; install the latest software.
Incorrect circuit connections
No alarms are activated for incorrect circuit connections. An incorrect assignment means the
expected end-to-end circuit connectivity will not happen. Re-check circuit assignments for all nodes
carrying the lost circuit(s).
Take extra care when configuring ring circuits.
Incorrect ID naming and commissioning
All traffic-carrying circuits must have a unique flow ID for the cross-connect capability to operate.
Incorrect/incompatible trib settings
Trib line interface settings incorrect, or line levels incompatible. While no alarm activates for an incor-
rect setting, its effect may result in line levels being too low (LOS alarm), or too high, resulting in a
high BER.
6.4.5 Troubleshooting Ethernet Problems

This section gives general guidance on troubleshooting problems related to the four Ethernet ports on the
Core-E Card.
The most common Ethernet problems are network and connectivity related and therefore always check
the following first:
Verify link partner capability, provisioning, and connection
Verify radio provisioning matches link partner
Verify cabling between radio and link partner
The LEDs on the Core-E Card front panel for each Ethernet connector are a good indicator of correct
connectivity and activity on the Ethernet port. Refer to Table 21. for detail troubleshooting using the LEDs
locally at the alarmed site.

Table 21. Troubleshooting Ethernet Problems
LED Indication Probable Cause Corrective Action
ETH IN LOS Green LED Loss of Ethernet RCV/radio XMT signal

Not Lit in. Most probable causes:
1 Cable between link partner and radio Connect/repair cable.
is disconnected/broken. 1. Check local Ethernet provisioning
2. Speed/Mode provisioning mismatch screen.
between link partner and radio. 2. Check link partner provisioning.
ETH OUT Green LED Loss of Ethernet XMT/radio RCV signal Check local RSL screen on CT. Is RSL
LOS Not Lit out. Most probable causes: ok?
1. Loss of RF input to Modem Card Yes - Check farend for Ethernet alarm.
No - Check farend Tx output. Is farend
Tx Out ok?
Yes - Check path, antenna, waveguide/
cabling
No - Check/replace farend Modem
Card.
2. Loss of Ethernet input to Modem
Card Check farend for Ethernet alarms.
Are any alarms indicated?
Yes - Troubleshoot farend alarms
No - Check farend Ethernet status. Is
only abnormal status indicated?
Yes - Troubleshoot farend Ethernet sta-
tus.
No -
1. Replace local alarmed Core-E Card.
2. Replace local Modem Card.
In order for the green Link LED to light:
1) Cable must be connected to Ethernet port
2) Ethernet port must be enabled (provisioned Enabled on Core-E Settings Screen)
3) Speed and mode (on Core-E Settings Screen) must be provisioned the same as the link partner.
The yellow LED opposite the green on the connector indicates activity only. The flashing yellow LED is
not an indicator of signal type or quality.
6.4.6 Troubleshooting TMN Problems

This section gives general guidance on troubleshooting TMN problems related to Ethernet port 4 on the
Core-E Card. Ethernet port 4 on the Core-E Card can be used to transport SNMP IP data. Troubleshoot
port 4 connectivity alarms the same as Ethernet ports 1-3.
The most common TMN problems are network related and first alert is normally observed by improper
operation at the SNMP master. Always check the following first:
Verify master is properly registered in NE to receive traps.
Verify SNMP version matches system requirements
Verify correct community string and privileges
Verify proper network routing.

Refer to Table 22. for detail TMN network troubleshooting.
Table 22. TMN Network Troubleshooting

Problem Possible Cause Possible Solution
Unusually slow communication in 1. Normal network management traf- 1. There may be too many radios
radio network fic is saturating the communications being managed within a single
channel. region. Split the radio network man-
agement into different regions and
backhaul the traffic for each region
through separate channels.
2. Polling radios for PM data or 2. Poll the radios more slowly.

missed alarms too rapidly
3. Multiple remote software down- 3. Download to fewer radios at a

loads in process time.
4. IP traffic other than network man- 4. Configure external routers to allow

agement traffic being routed through only network management related
radio network traffic through the Management net-
work of the radios. Dynamic route
updates (OSPF, RIP) may attempt to
reroute high speed traffic through the
TMN network if a high speed ink fails.
Unable to operate controls using To perform control operations, the Register the Manager as a craft
SNMP Manager must be registered as a device. Manager registration type
craft device. can be changed as needed to type ct
to allow control operation and then be
changed back to nml for normal
operation.
Can Read SNMP objects but cannot 1. Incorrect community string 1. Use the correct community string.
Write to SNMP objects
2. If the TMN Interface is configured 2. Use the correct write community
for SNMPv2, the write community string.
string is probably wrong.
No traps being received from NE 1. Manager not registered in NE to 1. Register Manager with NE.
receive traps
2. Communication failure in network 2. Check network connectivity.

Check redundant network paths and
routing. Traceroute (tracert) is useful
for locating path or routing faults.
Unable to communicate with the NE Possible communication path failure Use traceroute (tracert) to help locate
through the radio network (unable to or routing failure within the radio net- for communication path or routing
ping the NE). work. problems.
Can ping the TMN Interface but can- If using SNMPv2, using the wrong Verify community string or username/
not communicate with the NE using community string. passphrase.
SNMP, or can only see a few SNMP
objects in the NE.

6.5 Card Removal and REPLACEMENT
The basic rules for installing plug-in cards are as follows:
Never install, change or remove a card without first connecting

to the shelf with an ESD grounding cable. Failure to do so may
cause ESD damage to the cards.
Plug-ins must be withdrawn and inserted using their finger-grip

fastener/pulls. Never withdraw or insert using attached cable(s).
Pulling on the cables may damage the cable, plug-in connector,
and/or plug-in card connector attachment.
When installing a plug-in, ensure its backplane connector is

correctly engaged before applying sufficient pressure to bring
the plug-in panel flush with the front panel. Improper alignment
can result in damaged pins on the backplane connector and/or
damage to the plug-in connector.
All slots must be filled with either a peripheral plug-in card or a

blank panel. Failure to do so will compromise EMC integrity and
cooling air from the fan.

Use extreme caution when connecting or disconnecting the ODU cable on the
Modem Card. The shelf battery voltage is present on the center conductor
of the connector. When removing or replacing a Modem Card, withdraw
the card from the shelf before disconnecting the cable to the ODU. Failure to
follow these cautions may cause arcing and/or possible power spikes that could
affect traffic on other links installed at the node.
Removing an in-service card in an unprotected link will cause loss of traffic.

Removing an in-service card in a protected link requires switching the traffic
onto the standby (protection) channel.
The main Core-E Card, standby Core-E Card, and fan card have dedicated slots.
The E1 Access Card and Modem Cards (peripherals) can be installed in any of the universal slots
(3 through 8).
The MSS-8 can be configured with a maximum of six peripherals; three protected links, six non-
protected links, or a combination of protected and non-protected links.
For protected links, main and standby (spare) peripherals must be plugged in side-by-side.
All plug-ins can be removed and installed with power applied.
If the main Core-E Card fails, traffic and platform data will switch to the spare
Core-E Card automatically. Do not remove power from the NE during the
removal and replacement of the failed main Core-E Card without
first reviewing/performing the following procedure:
a) Turn off NE power.
b) Remove failed main Core-E Card.
c) Turn on NE power.
d) Wait two (2) minutes.
e) Install replacement Core-E Card.

6.5.1 Core-E Card Removal and Replacement Core-E Protected Radio
If the Main Core-E Card in slot 1 fails, traffic/services protection and control
platform protection switches to the spare Core-E Card in slot 2. Loopbacks
and all other manual operations, such as manual switch, tx mute, will be lost
(deactivated). Alarms previously active will be newly detected and reported via
notification, with a new time stamp.
Verify the replacement Core-E Card meets the following compatibility rules:
Main Core-E Card (in slot 1) and Spare Core-E Card (in slot 2) must be the same type.
Local and far end Core-E Cards must use the same software version, but do not have to be the same
type.
6.5.2 Flash card replacement procedure

First case: Core-E Protected
1) Get a spare FLASH CARD with the same sw-package release and license of the Main flash.
2) Remove the faulty FLASH CARD from the main Core-E and insert the spare one.
3) Insert the Core-E with the new FLASH CARD
4) The MIB (MAIN FLASH) will be automatically aligned with the MIB (SPARE FLASH).
Second case: Core-E Not Protected (NB)
1) Get a spare FLASH CARD with the same sw-package release and license.
2) Remove the faulty FLASH CARD from the main Core-E and insert the spare one.
3) Insert the Core-E with the new FLASH CARD
4) Carry-out the RESTORE procedure.
ATTENTION (caution to avoid complete traffic loss)

Do not insert in the system a Flash Card the content of which is unknow.
You must be aware that, if a Flash Card with SW information different from that running in the
system is inserted as it is, the software download will be automatically carried out from the
Flash Card toward the System, thus causing a complete system crash.
Note
The license of the Spare Flash card can be different from the license of the Main Flash card.
Only the license of the Main Flash card manages the NE.
By changing the Main Flash card, also the MAC address changes:
in this case the cross-connection must be reviewed.

6.6 Replacement procedure of Core-B card with Core-E card
6.6.1 Core replacement from Rel. 1.1.0

Note: flash memory not to be replaced.
For 1+0 configuration:
Remove all the TDM2Eth Cross-connections.
Load (from remote, if necessary) the SW 1.2 into Core-B (without activating it): at this stage the
standby side of the flash is loaded with the SW 1.2.
Making use of the Core-B, start the standby side of the flash through 1.2 CT: this is like having the
SW 1.2 into Core-B (as for the activation).
Database is converted automatically (with Core-E written on it and subsequent mismatching

activation, as expected).
Using the 1.2 CT, load SW 1.2 again into Core-B (from remote as well) and execute a second
activation (this is required to load Duff).
Switch the system off.
Replace Core-B with Core-E keeping the same flash.
Switch the system on: traffic interruption is in the order of 5-10 minutes.
Remove all the TDM2Eth Cross-connections.
Load the SW 1.2 from remote into Core-B (without activation).
Remove the spare Core-B.
Follow the 1+0 configuration procedure
Making use of the, start the standby side of the flash through 1.2 CT: this is like having the SW
1.2 into Core-B (as for the activation).

activation, as expected),
Switch on and wait for traffic restoration (same impact on the traffic as for the 1+0 case).
Insert the spare Core-E with the flash from spare Core-B.
Tools:
ETH patch-cord for the connection to the PC,

CD of SWP MPR 1.2,
1.2 Craft Terminal.

6.6.2 Core replacement from Rel. 1.1.1
Note: flash memory not to be replaced.
Load (from remote, if necessary) the SW 1.2 into Core-B (without activating it): at this stage the
standby side of the flash is loaded with the SW 1.2.
Making use of the Core-B, start the standby side of the flash through 1.2 CT: this is like having the
SW 1.2 into Core-B (as for the activation).

activation, as expected).
Using the 1.2 CT, load SW 1.2 again into Core-B (from remote as well) and execute a second
activation (this is required to load Duff).
Switch the system on: traffic interruption is in the order of 5-10 minutes.
Load the SW 1.2 from remote into Core-B (without activation).
Remove the spare Core-B.
Follow the 1+0 configuration procedure
Making use of the, start the standby side of the flash through 1.2 CT: this is like having the SW
1.2 into Core-B (as for the activation).

activation, as expected),
Switch on and wait for traffic restoration (same impact on the traffic as for the 1+0 case).
Insert the spare Core-E with the flash from spare Core-B.
Tools:
ETH patch-cord for the connection to the PC,
CD of SWP MPR 1.2,
1.2 Craft Terminal.

6.7 Upgrade from Not Protected to a Protected Radio (with ODU300)
6.7.1 1+0 Adaptive Modulation to 1+1 HSB Adaptive Modulation and 1+1 EPS
Starting from a 1+0 configuration (see an example in the graphics below) perform the following procedure
to upgrade to a 1+1 HSB radio with Adaptive Modulation and 1+1 EPS.
This is an in-service but not a hitless procedure.
1) Plug-in E1 Access card in slot 4 (spare). An Unconfigured Equipment alarm displays.
2) Plug-in Modem card in slot 8 (spare). An Unconfigured Equipment alarm displays.
3) On CT Settings screen enable the E1 Access card in slot 4.
4) On CT Settings screen enable the Modem card in slot 8.
5) On CT Settings screen provision the E1 Access cards (slots 3 and 4) for 1+1 EPS Protection
Type.
6) On CT Settings screen provision the Modem cards (slots 7 and 8) for HSB Protection Type.
Local station and remote station will observe 2 seconds sync loss.
7) Connect the E1 signal cables to the spare E1 Access card in slot 4.
8) Connect the new IDU/ODU cable to the spare Modem card in slot 8.
Note
After the changes a modification must be done in the TDM2Eth cross-connections of the remote
NE: the MAC address must be changed from Unicast to Multicast as explained in Figure 87., Figure
88. and Figure 89.

6.7.2 1+0 Static Modulation to 1+1 HSB Static Modulation and 1+1 EPS
Refer to the 1+0 Adaptive Modulation to 1+1 HSB Adaptive Modulation procedure above.
6.7.3 1+0 to 1+1 Frequency Diversity and 1+1 EPS
This is an in-service but not a hitless procedure.
Starting from a 1+0 configuration (see an example in the graphics below) perform the following procedure
to upgrade to a 1+1 Frequency Diversity and 1+1 EPS.
1) Plug-in E1 Access card in slot 4 (spare). An Unconfigured Equipment alarm displays.

2) Plug-in Modem card in slot 8 (spare). An Unconfigured Equipment alarm displays.
3) On CT Settings screen enable the E1 Access card in slot 4.
4) On CT Settings screen enable the Modem card in slot 8.
5) On CT Settings screen provision the E1 Access cards (slots 3 and 4) for 1+1 EPS Protection
Type.
6) On CT Settings screen provision the Modem cards (slots 7 and 8) for 1+1 FD Protection Type.
Local station and remote station will observe 2 seconds sync loss.
7) Connect the E1 signal cables to the spare E1 Access card in slot 4.
8) Connect the new IDU/ODU cable to the spare Modem card in slot 8.
9) Properly configure the protection ODU.
Note
88. and Figure 89.

6.8 Downgrade from Protected to a Not Protected Radio (with
ODU300)
6.8.1 1+1 HSB Adaptive Modulation and 1+1 EPS to 1+0 Adaptive Modulation
Downgrading from 1+1 HSB and 1+1 EPS to 1+0 configuration is an out-of-service procedure.
The main channel must be in service including sync source before starting procedure.
1) Disconnect E1 signal cables from the spare E1 Access card in slot 4.

2) Disconnect IDU/ODU cable on the spare Modem card in slot 8.
3) On CT Settings screen for Modem cards (slots 7 and 8) enable Local Tx Mute for Channel #1
and Channel #0.
4) On CT Settings screen for Modem cards (slots 7 and 8) set Protection Type to no Protection.
5) On CT Settings screen provision the MPT Access cards (slots 7 and 8) for HSB or FD Protection
Type. The Local station will observe a short traffic impact.
6) On CT Settings screen for Modem cards (slots 7 and 8) disable Local Tx Mute for Channel #1
and Channel #0.
7) On CT Settings screen for E1 Access cards (slots 3 and 4) set Protection Type to no Protection.
8) On CT Settings screen for spare E1 Access card (slot 4) set Equipment Type to EMPTY.
9) On CT Settings screen for spare Modem card (slot 8) set Equipment Type to EMPTY.
10) Remove spare Modem card (slot 8).
11) Remove spare E1 Access card (slot 4).
12) Power off and power on the NE.
Note
88. and Figure 89.

6.8.2 1+1 HSB Static Modulation and 1+1 EPS to 1+0 Static Modulation
Refer to the 1+1 HSB Adaptive Modulation and 1+1 EPS to 1+0 Adaptive Modulation procedure above.
6.8.3 1+1 FD to 1+0
Downgrading from 1+1 FD to 1+0 configuration is an out-of-service procedure.

The main channel must be in service including sync source before starting procedure.
1) Disconnect E1 signal cables from the spare E1 Access card in slot 4.

2) Disconnect IDU/ODU cable on the spare Modem card in slot 8.
Note
Local AIS will remain active throughout remainder of procedure.
4) On CT Settings screen provision the MPT Access cards (slots 7 and 8) for HSB or FD Protection
Type. The Local station will observe a short traffic impact.
5) On CT Settings screen for E1 Access cards (slots 3 and 4) set Protection Type to no Protection.
7) On CT Settings screen for spare E1 Access card (slot 4) set Equipment Type to EMPTY.
8) On CT Settings screen for spare Modem card (slot 8) set Equipment Type to EMPTY.
9) Remove spare Modem card (slot 8).
10) Remove spare E1 Access card (slot 4).
11) Power off and power on the NE.
Note
88. and Figure 89.

6.9 Cleaning
Do not use acid, alcohol, or brushes to clean cards because

damage to the silkscreen labeling and antistatic coating can
result. Cleaning should be confined to the removal of dust and
dirt using a damp cloth.
Cleaning should normally be confined to the removal of dust and dirt using a soft bristled (natural fiber)
brush and a low velocity blower (such as a vacuum cleaner with a plastic blower nozzle). Do not use acid
or synthetic bristled brushes to clean cards that contain electrostatic-sensitive components.

7 Lineup and Commissioning
This chapter details all phases necessary for the equipment lineup and commissioning.
Subject On page
Introduction 540
General 540
SafetyEMCEMFESD norms and Cautions to avoid equipment damage 541
Conventions 541
Summary of the commissioning phases 542
General information about test bench drawings 543
Commissioning of STATION A phase 1 (Turn up) 544
Commissioning of STATION B phase 1 (Turn up) 545
Fine antenna alignment and preliminary checks Stations A & B 545
End of commissioning phase 1 (Turn up) in STATION A 550
Commissioning station A phase 2 (acceptance test) 551
Commissioning station B Phase 2 (acceptance Test) 572
Final operations 572
Annex A: fine antenna alignment 572

Lineup and Commissioning 3DB 18528 DIAA Issue 1 539/578
7.1 Introduction
7.1.1 General
This chapter details all phases necessary for the equipment lineup, commissioning, and acceptance,
providing the user with the information needed to connect, power on, and perform a minimum turnup of
a radio link comprising two 9500 MPR-E Rel.1.4.0 Network Elements.
It is assumed that, at both premises (Station A and Station B), the mechanical installation and cabling of
the INDOOR and OUTDOOR units is completed, the antennas are installed and prepositioned, and the
MSSODU cable(s) has/have been connected to the MSS.
Any information needed to complete the above mentioned operations are out of the scope of this chapter.
For this purpose refer to the Installation section.
All the cables and measurement kits as described in Table 23. below are supposed to be available.
Table 23. Test and commissioning instruments

INSTRUMENT QTY CHARACTERISTICS
Laptop computer running the 1 SWP 9500 MPR-E V01.40.00

supervisory software
PDH Analyzer Pattern Generator 1 E1 traffic
In alternative, for Ethernet Data Optional

channel functionality tests:
1 PC + 1 Ethernet cable (for

ping function)
or
2 PCs (for ping function)
or
2 Ethernet Data Analyzers
Multimeter 1 Voltmeter AC and DC Loop tester
TRS 1 Test Result Sheet, available as separate document
The AlcatelLucent Software package SWP 9500 MPR-E V1.4.0 must have already been copied in the
PC used as the Craft Terminal (CT) and the same software V1.4.0 must be already present as commit
version in the Flash Card of both two Network Elements.
Before proceeding with lineup and commissioning, ensure that you have the equipment and accesso-
riesrequired for that purpose.

540/578 3DB 18528 DIAA Issue 1 Lineup and Commissioning
7.1.2 SafetyEMCEMFESD norms and cautions to avoid equipment damage
If not yet done, read whole Chapter 1 on page 27: it describes the operations and/or precautions to be
observed to safeguard operating personnel during the working phases, and to guarantee equipment
safety. Read them with accuracy before to start every action on the equipment.
7.1.3 Conventions
To simplify the description of actions, the following symbols are in use:
Symbol used Meaning
& Manual action
3 Check/Verify
CT On Craft Terminal Select
Select a Menu item
Sub Menu item
The commissioning operations described in this document are for a radio link between a Station A and
a Station B.
If the network includes supervision, station A is the one located between the supervisory station and sta-
tion B (see figure below). Installation and commissioning begin at station A.
MSS MSS
Figure 391. Relative positions of stations A and B
WARNING: at the beginning of this procedure, the local IP address and Ethernet IP address of both
the NE 9500 MPR-E stations, are still set to default value 10.0.1.2 (as delivered from AlcatelLucent
factory). For this reason, their physical connection to the TMN network must be done after having changed
such addresses to correct values.

7.1.4 Summary of the lineup, commissioning, and acceptance phases
Note: The following procedure must be used for every Modem unit installed in MSS.
The commissioning procedure is summarized as follows:
[1] Turn up (phase 1)
1) Visual inspection and NE configuration.
a) Station A, roughly point the antenna towards station B (if not done in the Hardware Instal-
lation procedure)
b) Commission station A (phase 1)
c) Commission station B (phase 1)
MSS MSS
2) Fine antenna alignment and preliminary checks Stations A & B
a) Station B, fine align the antenna towards station A, and preliminary checks
b) Station A, fine align the antenna towards station B, and preliminary checks
MSS MSS
[2] Site acceptance tests (phase 2)
3) Station A, perform all the commissioning checks and tests Report the results in the TRS.
MSS MSS

4) Station B, perform all the commissioning checks and tests Report the results in the TRS.
MSS MSS
7.1.5 General information about test bench drawings

In the test bench drawings depicted in the following paragraphs of this chapter, take always into account
the following considerations:
[1] Actual station configuration
For detailed information on the layout and equipment interconnections refer to the Plant documen-
tation.
[2] 1+0 and 1+1 configurations
Test bench drawings refer usually to the 1+0 configuration. When necessary, the additional mate-
rial for 1+1 configurations is drawn in dotted line.
[3] Equipment interfaces for test access points, signal meaning and use
The standard equipment interfaces for access points are always considered at Station DDF. Station
DDF is not detailed in the drawings: refer to your own plant documentation for details.
[4] Craft terminal need

The Craft Terminal (CT) is always required.

7.2 Commissioning of STATION A phase 1 (Turn up)
Where necessary, switch OFF the power supply before disconnecting the earth connection,
Do not connect instruments directly to the MSS/ODU cable connector since the connector
carries DC voltage used to supply the ODU.
Do not connect the IF cable between MSS and ODU while the MSS is powered up.
7.2.1 Turnon preliminary operations
ALL THESE OPERATIONS ARE PERFORMED WITH THE POWER OFF
3 The antenna of station A (or B) is pointed towards station B (or A) the best as possible (use compass
if necessary).
3 The hardware configuration of the equipment corresponds to the expected one.
3 Make visual inspection for units installation and cabling:
The MSS subrack allocation according to the station layout
The MSS subrack and units ground connections
The power supply voltage is present with the correct polarity at the MSS power supply input
Tributaries are cabled on the station DDF
The MSSODU cables ground kit connections
The ODU(s) ground connections (In the case of a nonintegrated antenna, the antenna and the
ODU(s) must be ground connected)
The MSS(s) / ODU(s) cables are connected to MSS(s) and ODU(s)
The ODU(s) cables connectors waterproofing.

7.2.2 Powering up the MSS(s) with ODU(s) connected
This operation has the following scopes:
verify the SWP present both in CT and NE
make the Central Frequency and Shifter values of ODUs be acquired by MSS (so that they are
retained in the NEs data base).
Proceed as follows:
a) Switch on the MSS by using the circuit breakers
b) Connect locally the CT to the MSS of the local station and perform the NE login with NETO.
1) Make a local connection through the Ethernet cable, between the Ethernet port of the PC and
the NMS interface on the MSS
2) Power on the PC and wait for its startup
3) Startup the LCT and wait for the NETO screen
4) Insert the local IP address of the NE 9500 MPR-E station
5) Start supervision on the local Network Element
c) Configure the NE as explained in the Provisioning chapter.
7.3 Commissioning of STATION B phase 1 (Turn up)

To commission Station B, perform (at Station B premises) the same operations carried on at Station
APhase 1.
& For near future tests, establish, on the DDF of Station B, hardware loops on every tributary.
7.4 Fine antenna alignment and preliminary checks Stations A & B
7.4.1 Fine antenna alignment

When Station A and Station B are fully configured and operational, and assuming that the antenna insta-
tion A (or B) has been previously correctly pointed toward the antenna in station B (or A), you shoul dre-
ceive some field from station B (or A).
Now, proceed to a fine tuning of the antenna to improve as much as possible the received level, in both-
Station A (at Station A premises) and Station B (at Station B premises). To perform the fine antenna align-
ment refer to Annex A: fine antenna alignment on page 572.

7.4.2 Preliminary checks
At first on Station A (at Station A premises), then on Station B (at Station B premises), log in the NE and-
perform following checks by CT:
Subject On page
Verify ODU(s) alarm status 546
Transmitter power output check 547
Received power measurement 548
7.4.2.1 Verify ODU(s) alarm status
Purpose: Verify no abnormal communication alarm between MSS(s) and ODU(s)
Required Instruments: PC with Craft Terminal software
Procedure: Connect CT to MSS.
& CT Views Equipment
In the left window, select ODU ch#1n
3 In the lower right window, verify in the alarms list for that there is no internal communication failuren
3 In the lower right window, verify in the alarms list that there is no TX failure
Repeat for Ch#0 if any (1+1)
Figure 392. ODU(s) alarm status

7.4.2.2 Transmitter power output check
Purpose: Verify via CT the ODU(s) transmitted power output.
& CT Double click on the front panel of the Modem unit (Channel #1)
3 Verify that ATPC is Disabled (If required, change the ATPC status to disable in the ATPC field then
Apply)
3 Verify that Tx Power value complies with the suitable value already set (If required, change the Tx
Power in the RTPC field then Apply)
Figure 393. Transmit power check

7.4.2.3 Received power measurement
Purpose: Verify via CT the received power to detect any interference
& CT Double click on the front panel of the Modem unit (Channel #1)
Select Measurements tab panel
In the Sample time (sec), write the suitable measurement poling time then press Start
Figure 394. Received power check

Pressing Start will prompt a graphic monitoring view of the transmitted and received levels:
Figure 395. Power measurements
Ticking the box Show Details in the lower left corner will call a summary view of the TX an Rx levels:
Figure 396. Received power details
3 Verify in the hop calculation (plant documentation) that the calculated received level has been
reached.
3 Verify that the current Rx local End received level is < 95 dBm (no interferences)
WARNING:
If in the Tx end field the indication in dBm is +99, the Transmitter is off (or in HSB Configuration the-
transmitter is in standby).
If in the Tx end field the indication in dBm is +99 and, at the same time, in the relevant Rx end field
the information in dBm is 99, probably the supervision has been lost.

7.5 End of commissioning phase 1 (Turn up) in STATION A
In Station A, proceed to a final fine alignment of the antenna toward the antenna of Station B. To per-
form the fine antenna alignment, refer to Annex A: fine antenna alignment on page 572.
In Station A, proceed to the remote NE (station B) acquisition (by opening a second NETO session)
in order to verify in both the stations:
3 Received level complies with hop calculation
3 No alarm showing (except unloaded tributaries)

7.6 Commissioning station A phase 2 (acceptance test)
Commissioning phase 2 is a site acceptance test procedure made up of the required tests to ensure that
the equipment is fully operational.
This phase describes first of all the way to check and to change (if necessary) via the Craft Terminal
menuthe different configuration parameters already set, for most of them, during the Provisioning followed
by various tests.
Most of the tests and checks results have to be recorded in the TRS (Test Results Sheet). Operator will
be invited to do so each time it is required by the following sentence: Report in the TRS.
N.B. The lettered titles in following table [ a ) , b ) , etc.] correspond to the pages heading titles of
the TRS document.
Test On page Report

in TRS
a) Installation and cabling visual inspection 553
Indoor System installation and cabling visual inspection 3
Outdoor System installation and cabling visual inspection 3
b) System configuration 553
Check/set Mode (Presettings or Adaptive modulation), Channel spacing, 3

Modulation
Check/set Link Identifier configuration (optional) 3
Check/set the QoS criteria to be used 3
Check/set the Automatic Restoration Criteria (only 1+1) 3
HSB Transmission Protection (1+1 HSB configurations only) 3
Radio Protection (RPS) 3
EPS Protection 3
Check/set Tx/Rx Spacing, Transmission and Reception frequencies 3
Check/set Tx power (ATPC Off ) or Tx range and Rx threshold (ATPC On) 3
Tx and Rx power measurement (with CT) 3
IF Loopback functionality 3
c) P32E1 unit 559
Balanced or Unbalanced impedance 3
Check/set E1 tributaries configuration 3
Protection functionality (1+1 only) 3
E1 point to point loop test 3

Test On page Report
in TRS
d) 16E1/DS1 ASAP unit 561
Check/set E1 layer configuration 3
Check/set IMA layer configuration 3
Check/set ATM layer configuration 3
Check/set ATM PW layer configuration 3
e) AUX unit 562
Check/set AUX unit configuration 3
Check/set the Housekeeping configuration 3
f) Core-E unit 562
Check the Software Licence Code 3
Check/set Traffic Ethernet port parameters 3
g) NE configuration 563
Check/set the local NE IP address 3
Check/set OSPF Area Configuration 3
Check/set the Ethernet access (OS) configuration 3
Check/set IP static routing configuration 3
h) Data/Time settings 563 3
i) Hop E1 stability test 564 3
j) Ethernet Traffic stability test 565 3
k) ATM Traffic stability test 569 3
l) 64 kbit/s Service Channel functionality test (optional) 571 3

7.6.1 Installation and cabling visual inspection
7.6.1.1 Indoor System installation and cabling visual inspection
See and fill the indoor inspection check list in the TRS.
7.6.1.2 Outdoor System installation and cabling visual inspection
See and fill the indoor inspection check list in the TRS.
7.6.2 System configuration

Purpose: Verify via CT the Radio configuration of the Local Station.
Procedure: Connect CT to MSS
7.6.2.1 Check/set Mode (Presettings or Adaptive modulation), Channel spacing,

Modulation
& CT Double click on the front panel of the Modem unit Settings tab panel
In the left window Mode (Presettings or Adaptive modulation), Channel spacing, Modulation (Sup-
ported Modulation Schemes and Switching Threshold, if the Adaptive Modulation has been enabled)
If required, change any paramater.
Report the parameters in the TRS.
7.6.2.2 Check/set Link Identifier configuration (optional)
Double click on the front panel of the Modem unit System Settings Link Identifier
If it is necessary, change any parameter.
Report the Link Identifier status (Enabled or Disabled), and, if Enabled, the Expected andSent values.
7.6.2.3 Check/set the QoS criteria to be used
& CT Menu bar Configuration System Settings

Select the suitable QoS criteria to be used: Disabled/802.1p/DiffServ.
Report in the TRS.
7.6.2.4 Check/set the Automatic Restoration Criteria (only 1+1)
7.6.2.4.1 HSB Transmission Protection (1+1 HSB configurations only)
& CT Views Protection Schemes
In the left window HSB Protection
In the lower right window Protection Scheme Parameters Tab panel Protection Type 1+1
If required, change Operation type (Revertive or Not Revertive) then Apply

Report the Operation Type in the TRS.
7.6.2.4.2 Radio Protection (RPS)
In the left window Rx Radio Protection (RPS)
7.6.2.4.3 EPS Protection
In the left window Equipment Protection
7.6.2.5 Check/set Tx/Rx Spacing, Transmission and Reception frequencies
& CT Double click on the front panel of the Modem unit
In the central window Channel #1 Shifter, Tx frequency
Repeat for Channel 0 (only in 1+1)
Report the Shifter, Tx and the Rx frequencies in the TRS.
If required, change the Tx frequency then Apply. Rx Freq. will be automatically adjusted.
7.6.2.6 Check/set Tx power (ATPC Off ) or Tx range and Rx threshold (ATPC On)
ATPC Disabled:
& CT Double click on the front panel of the Modem unit Setting tab panel
RTPC&ATPC field
3 ATPC Disabled
Report the ATPC Disabled status, Tx nominal Power and Tx Power setting into theTRS.
ATPC Enabled:
& CT Double click on the front panel of the Modem unit Setting tab panel
RTPC&ATPC field
3 ATPC Enabled

Report the ATPC Enabled status, ATPC Range and ATPC RX Threshold setting in the TRS.
If required, change ATPC Mode or ATPC Range or ATPC Rx Threshold then Apply
7.6.2.7 Tx and Rx power measurement (with CT)
Purpose: Verify via CT the Transmitted (PTx) and Received (PRx) power.
& CT Double click on the front panel of the Modem unit
From the left window select Channel #1 select Measurements tab panel
In the Sample time (sec), write the suitable measurement poling time then press Start
Pressing Start will prompt a graphic monitoring view of the transmitted and received levels.
Ticking the box Show details in the lower left corner will call a summary view of the TX an Rx levels.
Report the Current Tx Local End (PTx) and the current Rx Local End (PRx) in the TRS.
7.6.2.8 IF Loopback functionality
Purpose: Verify via CT the IF cable loopback functionality (only in the local NE)
Required Instruments: PC with Craft Terminal software and E1 Data Analyzer

Connect Pattern Generator/Error Detector analyzer on one Tributary Access
(At the Station DDF)
A delay up to 10 seconds may be observed for each activation/deactivation.
Ensure that the local tributary access is active (unframed and configured).
Ensure that the local transmitter is muted (double click on the front panel of the Modem unit Set-
tings tab panel).

IF cable loopback
Figure 397. IF Cable loopback
& CT Double click on the front panel of the Modem unit Loopback tab panel
In the left window IF cable
In the lower right window Active Apply
3 Error Detector showing no errors.
3 Loopback showing in the Summary Block Diagram view.
To remove the loopback: in the lower right window Not Active Apply
Report about the Loopback functionality in the TRS.

Figure 398. Loopback control in the CT
7.6.2.9 Protection functionality (1+1 only)
Purpose: Force command (if the active channel is the Main) and Lockout command (if the
active channel is the Spare)
& CT View Protection Schemes
In the left window Rx Radio Protection Main #1 or Spare #0
In the Commands tab panel window Commands scroll list Forced or Lockout Apply
Repeat for HSB Tx Protection (for 1+1 HSB configurations only)
Repeat for Equipment Protection
3 Check in the Summary block diagram that the full channel (Tx and Rx) path is in service.
Report about the Channel protection switching functionality in the TRS.

Figure 399. Protection command (Main)
Figure 400. Protection command (Spare)

7.6.3 P32E1 unit
7.6.3.1 Balanced or Unbalanced impedance
& CT Menu bar Configuration System Settings

Set the impedance for the E1 streams.
Report the Impedance in the TRS.
7.6.3.2 Check/set E1 tributaries configuration
& CT Double click on the front panel of the P32E1DS1 unit
In the left window E1 port# 1
In the lower right window Settings Tab panel
If it is necessary, change the E1 parameters.
Report in the TRS.
Repeat for each E1 port#
7.6.3.3 Protection functionality (1+1 only)
Purpose: Force command (if the active channel is the Main) and Lockout command (if the
active channel is the Spare)
& CT View Protection Schemes
In the left window Equipment Protection Main #1 or Spare #0
In the Commands tab panel Forced or Lockout Apply
3 Check in the Summary block diagram that the full channel (TX and RX) path is in service.
Report about the Channel protection switching functionality in the TRS.
7.6.3.4 E1 point to point loop test
Purpose: Verify the point to point Tributaries quality

Verify the tributaries alarm status monitoring functionality

Connect Pattern Generator/Error Detector on Tributary Access (At the Station
DDF)
& CT Diagnosis Summary Block Diagram View

Report the result in the TRS.

ODU ODU
REMOTE STATION
ODU ODU
Main Core Main Core
Main Modem Spare Modem Main Modem Spare Modem

FANS FANS
Main P32E1DS1 Spare P32E1DS1 Main P32E1DS1 Spare P32E1DS1
DDF DDF
E1
"Tributary loopback"
Error Analyzer
Pattern Generator
Figure 401. Test bench for tributary functionality check
[1] Point to point Tributaries quality test
Assuming that all the tributaries have been enabled and configured (Unframed status and configu-
ration) via CT in both stations and that every tributary is looped at the DDF in the remote station:
Perform one minute of BER test on each E1 tributary
3 Verify that the analyzer detects no error.
3 Verify the tributary alarm status:
& CT Double click on the front panel of the P32E1DS1 unit

In the lower right Alarms tab panel, verify that while the data analyzer is connected,
theAlarmLossSignal on the relevant tributary is off.
Leave the Alarms screen open, to perform following check
[2] Check of the tributaries alarm status monitoring functionality
To create an alarmed condition, remove the Tributary loopback at the Remote station.
In the lower right Alarms, verify that while the data analyzer is connected, the AlarmLossSignalon the
relevant tributary goes on.
Restore the Tributary loopback at the Remote station, and verify that the AlarmLossSignal on there-
levant tributary goes off.

Figure 402. Tributary alarm status monitoring
Report about the Tributary BER test and alarm CT monitoring in the TRS.
7.6.4 16E1/DS1 ASAP unit
7.6.4.1 Check/set E1 layer configuration
& CT Double click on the front panel of the 16E1/DS1 ASAP unit
To configure refer to par. 3.14.1 on page 272.
Report in the TRS.
7.6.4.2 Check/set IMA layer configuration
Report in the TRS.
7.6.4.3 Check/set ATM layer configuration

Report in the TRS.
7.6.4.4 Check/set ATM PW layer configuration
Report in the TRS.
7.6.5 AUX unit
7.6.5.1 Check/set AUX unit configuration
& CT Double click on the front panel of the AUX unit

Report in the TRS.
7.6.5.2 Check/set the Housekeeping configuration
& CT Double click on the front panel of the AUX unit

Report in the TRS.
7.6.6 Core-E unit
7.6.6.1 Check the Software Licence Code
& CT Menu bar Supervision SW licence

Report the Licence string and code in the TRS.
7.6.6.2 Check/set Traffic Ethernet port parameters
& CT Double click on the front panel of the Core-E unit
In the left window Ethernet Port#1 or Ethernet Port#2 or Ethernet Port#3 or Ethernet Port#4 or Optical
SFP Ethernet Port #5.
In the lower right window Settings Tab panel
If it is necessary, change the parameters.
Report in the TRS.

7.6.7 NE configuration
7.6.7.1 Check/set the local NE IP address
& CT Configuration Network Configuration Local Configuration

Report the local IP Address in the TRS.
7.6.7.2 Check/set OSPF Area Configuration
& CT Configuration Network Configuration IP Configuration OSPF Area Configuration

Report the Id, IP Address, IP Mask and Stub flag in the TRS.
7.6.7.3 Check/set the Ethernet access (OS) configuration
& CT Double click on the front panel fo the Core-E unit TMN Interface tab panel
Report the IP Address, IP Mask, IP Routing protocol and OSPF Area in the TRS.
7.6.7.4 Check/set IP static routing configuration
& CT Configuration Network Configuration IP Configuration IP Static Routing Configuration

Report the IP Address, IP Mask and Default gateway IP Address or interface type into theTRS.
7.6.8 Data/Time settings
& CT Menu bar Configuration NE Time

Enter the time settings.
Report in the TRS.
& CT Menu bar Configuration Network Configuration NTP Server Configuration

Enter the IP address of the NTP Server, if any.

7.6.9 Hop E1 stability test
N.B.: this test is in alternative to that described in point d) (performed on one Ethernet port)
Purpose: Verify the Hop stability

Connect Data analyzer on one Tributary Access (At the Station DDF)
The Hop stability test is performed during two consecutive hours, one time, on one Tributary, in real-
working condition whatever the protection configuration (1+ 0 or 1+1).
The two-hour stability test must be free of error in normal propagation conditions (out of fading
period)
Via the CT, let only one active tributary in both station
In the remote Station, place a hardware loop on the relevant tributary access (at the station DDF).
In the local station, connect the E1 Data Analyzer on the relevant tributary. Check that the
Tributary Alarm Loss disappears.
3 Verify in both stations that there are no active software loopbacks or switching requests.
3 Verify in both stations that none alarm is showing.
Report the two-hour error-free of error Hop Stability Test result in the TRS.
ODU ODU
REMOTE STATION
ODU ODU
Main Core Main Core

FANS FANS
DDF DDF
E1
"Tributary loopback"
Error Analyzer
Pattern Generator
Figure 403. Test bench for hop stability test

7.6.10 Ethernet Traffic stability test
Purpose: Verify the quality of point to point Ethernet Data Channels
Required Instruments: PC with Craft Terminal software and, in alternative:

1 additional PC and 1 Ethernet cable
2 additional PCs
Procedure:
a) Connect CT to MSS of local station
b) Perform the connectivity test on port #1, according to the chosen test bench:
Test bench with 1 additional PC and 1 Ethernet cable: see point [1]
Test bench with 2 additional PCs: see point [2]
Test bench with 2 Ethernet Data Analyzers: see point [3]
c) Perform the connectivity test on ports #2 , #3, #4 and #5 (if enabled)

If required in plant documentation, repeat the connectivity test [step b) above] for the other three-
ports, with obvious test bench changes on remote station.
Report about the connectivity test of Ethernet Data Channels in the TRS.
d) Perform the hop stability test
1) Set up the test bench with 2 Ethernet Data Analyzers (point [3]). On both stations, connect the
Data analyzer on Ethernet port #1 on the Core-E unit.
2) Start this test after the learning of the MAC address.
3) Configure the pattern A generator, in order to generate continuos traffic, and set the data rate-
half to the radio capacity and with packet size of 1518 bytes.
4) Perform the stability test for 2 hours.
5) Compare the number of TX and Rx Frames on the Pattern A: the number of frames must be
equal in normal propagation conditions (out of fading period).
Report the two-hour error-free Ethernet Stability Test result in the TRS.

[1] Test bench with 1 additional PC and 1 Ethernet cable
a) Connections
On local station, connect the additional PC on Ethernet port #1 (testing port).
On remote station, through the Ethernet cable, connect the NMS Ethernet port to the
Ethernet port #1 (port to be tested)
b) Set Enable, Flow Control disable, and Capability Advertised for ports to test
& CT perform the following operations on each data port (Ethernet ports #1 to #4) of both
stations:
Enabled Apply
Auto Negotiation Status Disabled Apply
Flow Control Disabled Apply
Capability Advertised 1000 Mb/s Full Apply
c) Perform the connectivity test on port #1
1) at local station, on PC connected to Ethernet port #1 (N.B.), ping the remote station
(using) the NEs Ethernet Configuration IP address) with 50 packets with 1000 byte
length.
N.B.: the PCs IP address and the NEs Ethernet Configuration IP address must
belong to the same subnetwork.
Windows OS details, if necessary:
Start Programs Accessories Command Prompt
ping <space> l <space> 1000 <space> n <space> 50 <space> IP Address
<enter>
2) the RIGHT LED on the corresponding front panel blinks with cable inserted and traffic
running
At least 45 packets must pass without any packet loss from the 5th packet
ODU ODU
REMOTE STATION
ODU ODU
Main Core Main Core

FANS FANS
Port #1
Port #1
(testing) Mngt Port
(tested)
Ethernet cable
CT
PC for ping
Figure 404. Test bench for optional Ethernet Data Channel functionality with 1 additional PC and
1 Ethernet cable

[2] Test bench with 2 additional PCs
a) Connections
On local station, connect the additional PC on Ethernet port #1 (testing port)
On remote station, connect the additional PC on Ethernet port #1 (port to be tested)
stations:
Enabled Apply
1) at local station, on PC connected to Ethernet port #1, ping the farend PC with 50
packets with 1000 byte length.
Windows OS details, if necessary:
Start Programs Accessories Command Prompt
ping <space> l <space> 1000 <space> n <space> 50 <space> IP Address
<enter>
running.
At least 45 packets must pass without any packet loss from the 5th packet.
ODU ODU
REMOTE STATION
ODU ODU
Main Core Main Core

FANS FANS
Port #1
Port #1
(testing)
(tested)
CT
PC for ping PC for ping
Figure 405. Test bench for optional Ethernet Data Channel functionality with 2 additional PCs

[3] Test bench with 2 Ethernet Data Analyzers
a) Connections
On local station, connect the Data analyzer on Ethernet port #1 (testing port)
On remote station, connect the Data analyzer on Ethernet port #1 (port to be tested)
stations:
Enabled Apply
1) Start this test after the learning of the MAC address.

2) Configure Pattern Generator A in order to generate 50 packets with 1000 byte length,
and set the data rate half of the radio capacity.
running.
At least 45 packets must pass without any packet loss from the 5th packet.
ODU ODU
REMOTE STATION
ODU ODU
Main Core Main Core

FANS FANS
Port #1 Port #1
(testing) (tested)
Ethernet Data Ethernet Data

Analyzer Analyzer
Pattern A CT Pattern B: Ethernet loop: Destination

MAC address and Source
MAC addresses are swapped
Figure 406. Test bench for optional Ethernet Data Channel functionality with

7.6.11 ATM Traffic stability test
Purpose: Verify the quality of point to point ATM Data Channels (where 16E1/DS1 ASAP
unit has been installed)
Required Instruments: PC with Craft Terminal software and 1 4xE1 ATM/IMA Generator/Analizer
Procedure:
The Hop stability test is performed during two consecutive hours, one time, on one IMA Group con-
figured on 16E1DS ASAP peripheral, in realworking condition whatever the radio peripheral protec-
tion configuration (1+ 0 or 1+1).
The two-hour stability test must be free of error (no ATM Cell Loss) in normal propagation conditions
(out of fading period)
a) Connect CT to MSS of local station
b) Check IMA connectivity in the local Station:
"configure on ATM/IMA instrument a 4xE1 IMA Group with MPR default configuration values
"activate the IMA Group of ATM/IMA instrument: it will result in "Not Operational" state since
no connection to MSS and IMA configuration has been yet performed
"connect E1 ports of ATM/IMA instrument to DDF connection points corresponding to E1 ports

#1,#2,#3,#4 of relevant ASAP peripheral
on MSS, enable E1 ports #1,#2,#3,#4 of relevant 16E1DS1 ASAP peripheral by config-

uring as Framed their Signal Mode
without change to default configuration values, activate ATM interface #1 associated to

IMA Group #1 of relevant ASAP peripheral
associate to IMA Group #1 of relevant ASAP peripheral and make active as IMA Links the
E1 ports #1,#2,#3,#4
activate ATM interface #1,associated to IMA Group #1 of relevant ASAP peripheral
the IMA Group #1 of relevant ASAP peripheral and the one in the ATM/IMA instrument
shall become "Operational" ("TSF" alarm should be cleared, if previously raised)
c) Perform the IMA connectivity test for all E1 ports of relevant ASAP peripheral(s)
Repeat the IMA connectivity test [step b) above] for the other E1 ports, with the below association
associate to IMA Group #2 of relevant ASAP peripheral the E1 ports #5,#6,#7,#8
Report about the IMA connectivity test of ATM Data Channels in the TRS.
d) Configure ATM traffic in the local Station
On ATM interface #1 (associated to IMA Group #1) of relevant ASAP peripheral create and con-
figure:

"one ATM Traffic Descriptor for an ATM Circuit of type CBR, PCR=17960 cell/s,
CDVT=1000 microsecond, ATM Policing Enabled
"one VP of "Not Logical" type, with VPI=1 and associate the above ATM TD (both for
Ingress/Egress)
On PW Layer of relevant ASAP peripheral create one ATM PW flow associated to the above
VP, with PW Label = 100, 1 cell max per frame and 1 millisecond timeout (no VPI translation)
On PW Layer of relevant ASAP peripheral create one ATM PW flow associated to the above
VP, with PW Label = 100, 1 cell max per frame and 1 millisecond timeout (no VPI translation)
Configure the cross-connection of the above ATM PW flow towards the relevant radio periph-
eral, with associated VLAN ID = 4000
e) Configure in the remote Station a Loopback at DDF level, as shown in Figure 407.
f) Configure and start in the local Station the ATM Generator/Analizer
Configure, ATM Generator of ATM/IMA instrument for one ATM Cell stream, with rate 17960
cell/s, VPI=1, VCI=1 (if the ATM Generator has this capability, use test pattern inside ATM Cells
to detect Cell Loss), without starting traffic
Start ATM Analyzer
Start ATM Generator
Check the same rate of ATM Cell of configured ATM Circuit is transmitted by ATM Generator
is also received by the ATM Analyzer (since ATM Traffic is looped-back by the remote Station);
if random pattern is available on ATM/IMA instrument, directly check on ATM Analyzer that no
cell is actually lost
Report the two-hour error-free ATM Stability Test result in the TRS.
Figure 407. Test bench for ATM traffic

7.6.12 64 kbit/s Service Channel functionality test (optional)
Purpose: Verify the point to point Service Data Channel quality
Required Instruments: PC with Craft Terminal software and RS422 / V11 64 Kbit/s Data Analyzer

Connect Data analyzer on the service channel Access
Figure 408. Test bench for 64 kbit/s Service Channel functionality check
Assuming that the User service Channel is looped in the remote station:
Perform 10 minutes of BER test.
3 Verify that the Data analyzer detects no error.
Report about the 64 Kbit/s Data channel BER test into the TRS.

7.7 Commissioning station B Phase 2 (acceptance Test)
Repeat in Station B all the tests performed in Station A except the Hop Stability Test that has to be run
only one time for the full hop.
Fill a second Test Result Sheet for Station B
END OF COMMISSIONING ACCEPTANCE TEST
7.8 Final operations

Complete the commissioning of each NE, creating the NE operator profiles and saving its data.
7.9 Annex A: fine antenna alignment

Safety requirements for workers on antenna pole, and microwave radiations (EMF norms)
SAFETY RULES
When operating on the antenna pole, strictly follow cautions.
In particular, if ODU is powered on from MSS, do not stand on the antenna axis
and beaware of the compliance boundaries.
Antenna prepointing should have been done during equipment hardware installation.
This annex explains how to carry out the antenna fine alignment.
To monitor the received level during alignment in the local station:
use the ODU Rx power monitoring in addition to a voltmeter,
or, after having logged in the NE, use the Craft Terminal received power measurement facility
Alignment procedure using the ODU Rx power monitoring
a) the radio link must be up
b) in general, fine alignment should be done only on one station of the radio link
c) connect a voltmeter to the ODU
d) proceed with Vertical alignment, then with Horizontal alignment
e) in configurations with two antennas, repeat the procedure for the second antenna.
Note
Procedures for Vertical and Horizontal alignment depend on the type of integrated polemounting
employed.

ABBREVIATIONS
ABBREVIATION MEANING
ADM Add Drop Multiplexer
AIS Alarm Indication Signal
ALS Automatic Laser Shutdown
AP Access Point
APS Automatic Protection Switching
AS Alarm Surveillance
ASAP Any Service Any Protocol
ATM Asynchronous Transport Module
BER Bit Error Rate
BR & SW Bridge & Switch
Browser Application which allows to browse all RM-MIB objects
CCLNP ConnectionLess Network Protocol
CDCC Data Communication Channel
CD-ROM Compact Disc Read Only Memory
CES Circuit Emulation Service
CI Communication Infrastructure
CRU Clock Reference Unit
CTP Connection Termination Point
CT Craft Terminal
DCI Drop & Continue Interconnection
DCN Data Communications Network
DS Degraded Signal
ECC Embedded Communication Channels
EML Element Management Layer

Abbreviations 3DB 18528 DIAA Issue 1 573/578
EML domain A set of NEs that are maintained by the same EML-OS.
EPS Equipment Protection Switching
EM-OS Element Manager-Operation System
EMS Event Management Services
ET Elementary Topology. It is a grouping of some nodes connected

according to specific rules. A typical ET is a ring.
FLS Frame Loss Second
Gbit/s Gigabits per second
FM FM Fault Management
GNE Gateway Network Element
HSB Hot Stand-By
IWF Inter-Working Function
Link Connection (lc ) A transport entity provided by the client/server association.It is

formed by a near-end adaptation function,a server trail and a far-
end adaptation function between connection points. It can be con-
figured as part of the trail management process in the associated
server layer.
IEEE Institute of Electrical and Electronics Engineers
IM Information Manager
Kbit/s Kilobits per second
LAN Local Area Network
LOS Loss Of Signal
Mbit/s Megabits per seconds
MEF Metro Ethernet Forum
MIB Management Information Base
MPR Microwave Packet Radio
MSS Microwave Service Switch
NE Network Element
NEC Network Element Clock
Node It is the view of the NE at NML level
NTP NetworkTime Protocol
ODU OutDoor Unit

574/578 3DB 18528 DIAA Issue 1 Abbreviations
OFS Out of Frame Seconds
OS Operation System
PDH Plesiochronous Digital Hierarchy
PM Performance Monitoring
PNU Packet Node Unit
Port Physical Interface of a Node. A port can be SDH or PDH.
PI Physical Interface
PPI PDH Physical Interface
RSL Receive Signal Level
SA Site Aggregator
SDH Synchronous Digital Hierarchy
SD Signal Degrade
SF Signal Failure
SONET Synchronous Optical Network
SPDH Super PDH
STM Synchronous Transport Module
TMN Telecommunications Management Network
TCA Threshold Crossing Alarm
USM User Service Manager
UPA Unavailable path alarm
URU Underlying Resource Unavailable
WTR Wait Time to Restore

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

Customer Documentation Feedback 3DB 18528 DIAA Issue 1 577/578
CUSTOMER DOCUMENTATION FEEDBACK
Handbook Data
Handbook title, release,version:
Handbook type:
Handbook part number and edition:
General Feedback Evaluation
SUBJECT 5(max) 4 3 2 1 (min)
Total evaluation
Info quantity
Info quality
Info structure
Consulting facility
Layout
Chapters Feedback Evaluation
HANDBOOK PARTS 5(max) 4 3 2 1(min)
PREFACE
CHAPTER 1
CHAPTER 2
CHAPTER 3
CHAPTER 4
CHAPTER 5
CHAPTER 6
CHAPTER 7
Your Comments (stricltly necessary when value is less than 3):
Suggestion for Improvement

Which subject to deepen:
How to deepen:
Subject to eliminate or reduce
Other comments/suggestions
Errors Identified
Reader Info
Name:
Company:
Address:
E-mail:
Phone:
578 9500 MPR ETSI Rel. 1.4.0 User Manual

578/578 3DB 18528 DIAA Issue 1 Customer Documentation Feedback
3DB 18528 DIAA
Edition 1
All rights reserved.
Passing on and copying of this document,
use and communication of its contents is not permitted
without written authorization from Alcatel -Lucent.
www.alcatel-lucent.com

3db18528diaa - v1 - 9500 MPR Users Manual (Etsi) r1.4.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3db18528diaa - v1 - 9500 MPR Users Manual (Etsi) r1.4.0

Uploaded by

Copyright:

Available Formats

9500 MPR ETSI

Microwave Packet Radio

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

All rights reserved.

LIST OF TABLES ........................................................................................................................... 17

1 SAFETY, EMC, EMF, ESD NORMS AND EQUIPMENT LABELLING ........................................ 27

2 PRODUCT INFORMATION AND PLANNING ............................................................................. 39

User Manual 9500 MPR ETSI Rel. 1.4.0

3 NE MANAGEMENT BY SOFTWARE APPLICATION ................................................................. 133

9500 MPR ETSI Rel. 1.4.0 User Manual

User Manual 9500 MPR ETSI Rel. 1.4.0

6 MAINTENANCE AND TROUBLE-CLEARING ............................................................................ 513

7 LINEUP AND COMMISSIONING ............................................................................................... 539

9500 MPR ETSI Rel. 1.4.0 User Manual

ABBREVIATIONS ............................................................................................................................ 573

CUSTOMER DOCUMENTATION FEEDBACK.............................................................................. 577

User Manual 9500 MPR ETSI Rel. 1.4.0

User Manual 9500 MPR ETSI Rel. 1.4.0

9500 MPR ETSI Rel. 1.4.0 User Manual

User Manual 9500 MPR ETSI Rel. 1.4.0

9500 MPR ETSI Rel. 1.4.0 User Manual

User Manual 9500 MPR ETSI Rel. 1.4.0

9500 MPR ETSI Rel. 1.4.0 User Manual

User Manual 9500 MPR ETSI Rel. 1.4.0

9500 MPR ETSI Rel. 1.4.0 User Manual

User Manual 9500 MPR ETSI Rel. 1.4.0

User Manual 9500 MPR ETSI Rel. 1.4.0

2) Access to the Equipment

User Manual 9500 MPR ETSI Rel. 1.4.0

SERVICE PERSONNEL SKILL

9500 MPR-E 1.4.0

ISSUE DATE DESCRIPTIONS

9500 MPR ETSI Rel. 1.4.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-

User Manual 9500 MPR ETSI Rel. 1.4.0

ABBREVIATIONS The abbreviation list is supplied.

9500 MPR ETSI Rel. 1.4.0 User Manual

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

User Manual 9500 MPR ETSI Rel. 1.4.0

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

9500 MPR ETSI Rel. 1.4.0 User Manual

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

The CD-ROM can be used both in PC and Unix WS environments.

User Manual 9500 MPR ETSI Rel. 1.4.0