Вы находитесь на странице: 1из 1956

User Manual 3DB19901AFAA Edition 01

Alcatel-Lucent 9500
MICROWAVE PACKET RADIO for ETSI | RELEASE 5.2.0
User Manual
3DB19901AFAA Edition 01

Alcatel-Lucent Proprietary
This document contains proprietary information of Alcatel-Lucent and is not to
be disclosed or used except in accordance with applicable agreements.
Copyright 2014 Alcatel-Lucent. All rights reserved.

Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is subject to change
without notice.
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks
are the property of their respective owners.
Copyright 2014 Alcatel-Lucent.
All rights reserved.
Disclaimers
Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design engineering,
they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe
performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic
control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to
death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale,
license or other distribution of the products for any such application without the prior written consent of
Alcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent
harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the
use, sale, license or other distribution of the products in such applications.
This document may contain information regarding the use and installation of non-Alcatel-Lucent products. Please
note that this information is provided as a courtesy to assist you. While Alcatel-Lucent tries to ensure that this
information accurately reflects information provided by the supplier, please refer to the materials provided with any
non-Alcatel-Lucent product and contact the supplier for confirmation. Alcatel-Lucent assumes no responsibility or
liability for incorrect or incomplete information provided about non-Alcatel-Lucent products.
However, this does not constitute a representation or warranty. The warranties provided for Alcatel-Lucent products,
if any, are set forth in contractual documentation entered into by Alcatel-Lucent and its customers.
This document was originally written in English. If there is any conflict or inconsistency between the English
version and any other version of a document, the English version shall prevail.

Table of Contents
Preface ............................................................................................................... 57
Preliminary Information..................................................................................................... 57
WARRANTY ................................................................................................................ 57
INFORMATION ............................................................................................................. 57
COPYRIGHT NOTIFICATION.............................................................................................. 57
SAFETY RECOMMENDATIONS ............................................................................................ 57
SERVICE PERSONNEL SKILL .............................................................................................. 58
Applicability .................................................................................................................. 58
Scope........................................................................................................................... 59
History ......................................................................................................................... 59
Change notes ................................................................................................................. 59
Handbook Structure ......................................................................................................... 59
General on Alcatel-Lucent Customer Documentation .................................................................. 60
CustomerIndependent Standard Customer Documentation ...................................................... 61
Product levels and associated Customer Documentation .......................................................... 61
Handbook Updating .................................................................................................. 62
Changes introduced in the same productrelease (same handbook P/N) ................................... 62
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS ............................................... 63
Supplying updated handbooks to Customers ..................................................................... 63
Changes due to new product version ............................................................................. 63

1 Safety, EMC, EMF, ESD Norms and Equipment Labeling............................................... 65


1.1
1.2
1.3
1.4

Declarations of conformity to CE marking and Countries List ................................................ 65


Specific label for MPR-E equipment ............................................................................... 69
Applicable standards and recommendations ..................................................................... 70
Safety Rules ........................................................................................................... 70
1.4.1 General Rules ................................................................................................... 70
1.4.2 Labels Indicating Danger, Forbidding, Command ......................................................... 72
1.4.3 Dangerous Electrical Voltages................................................................................ 72
1.4.4 Risks of Explosions: labeling and safety instructions ..................................................... 73
1.4.5 Moving Mechanical Parts: labeling and safety instructions .............................................. 74
1.4.6 Equipment connection to earth.............................................................................. 74
1.4.7 Heat-radiating Mechanical Parts: labeling and safety instructions..................................... 75
1.4.8 Optical safety................................................................................................... 75
1.4.9 Microwave radiations (EMF norms) .......................................................................... 75
1.5 Electromagnetic Compatibility (EMC norms) ..................................................................... 77
1.6 Equipment protection against electrostatic discharges ........................................................ 78
1.7 Cautions to avoid equipment damage............................................................................. 78
1.8 Waste from Electrical and Electronic Equipment (WEEE) ...................................................... 79

2 Product information and planning ......................................................................... 81


2.1 Purpose and Function ................................................................................................ 85
2.1.1 Innovative solutions............................................................................................ 85
2.1.2 Description ...................................................................................................... 88
2.1.2.1 MPR-LH solution .......................................................................................... 90
2.1.3 MSS Purpose, Function and Description .................................................................... 90

User Manual 3DB19901AFAA Edition 01

2.1.3.1 MSS-4/8 modules......................................................................................... 92


2.1.3.2 MSS-1 functions .......................................................................................... 94
2.1.3.3 MSS-O functions .......................................................................................... 95
2.1.3.4 Block diagrams ........................................................................................... 95
2.1.4 Stacking configuration......................................................................................... 97
2.1.5 ODU300 .......................................................................................................... 99
2.1.6 MPT-HC/HC-HQAM ............................................................................................100
2.1.7 MPT-XP/XP-HQAM .............................................................................................101
2.1.8 Sparing strategy: MPT-HC/XP replacement with MPT-HC-HQAM/XP-HQAM ..........................102
2.1.9 MPT-MC .........................................................................................................103
2.1.10 MPT-HLS .......................................................................................................104
2.1.11 MSS to Outdoor Unit interconnections....................................................................105
2.1.11.1 MSS-4/8 to ODU300 interconnection ...............................................................105
2.1.11.2 MSS-4/8 to MPT-HC/HC-HQAM interconnection ..................................................106
2.1.11.3 How to connect the MPT-HC/HC-HQAM to the station battery ................................118
2.1.11.4 MSS to MPT-XP/XP-HQAM interconnection ........................................................119
2.1.11.5 MSS-4/8 to MPT-MC interconnection ...............................................................128
2.1.11.6 MSS-1 to MPT ODU interconnection.................................................................132
2.1.11.7 MSS-O to MPT ODU interconnection ................................................................135
2.1.12 Antennas ......................................................................................................137
2.2 Radio capacity, channeling and modulation ....................................................................137
2.2.1 ODU300 .........................................................................................................137
2.2.2 MPT-HC/MPT-XP/MPT-MC ...................................................................................138
2.2.3 MPT-HC-HQAM and MPT-XP-HQAM .........................................................................144
2.2.4 MPT-HLS ........................................................................................................149
2.3 Standard Features ..................................................................................................150
2.4 Radio Configurations ................................................................................................151
2.4.1 Split mount (short haul) radio configurations: ODU300, MPT-HC/HC-HQAM, MPT-MC,
MPT-XP/XP-HQAM ......................................................................................................151
2.4.2 All indoor (long haul) radio configurations: MPT-LH using MPT-HLS ..................................152
2.5 Typical System Configurations.....................................................................................152
2.6 Environmental and Electrical Characteristics ..................................................................157
2.6.1 System Parameters ...........................................................................................157
2.6.2 ODU300 .........................................................................................................162
2.6.2.1 6 to 15 GHz ..............................................................................................162
2.6.2.2 18 to 38 GHz .............................................................................................162
2.6.3 MPT-HLS ........................................................................................................163
2.6.4 Cable length and power consumption of MPT-HC/HC-HQAM/XP/XP-HQAM using MPT
Power Unit or MPT Extended Power Unit............................................................................164
2.6.5 Radio performances...........................................................................................167
2.6.6 Power Injector general characteristics ....................................................................168
2.6.7 General characteristics (MPT power unit).................................................................168
2.6.8 Maximum allowed cable lengths for MPT Power Unit ...................................................169
2.6.9 General characteristics (MPT extended power unit) ....................................................169
2.6.10 Maximum allowed cable length for MPT Extended Power Unit ......................................170
2.7 Parts Lists.............................................................................................................171
2.7.1 Indoor items....................................................................................................171
2.7.2 ODU300 (with internal lightning surge suppressor) ......................................................180
2.7.3 MPT-HC/HC-HQAM with internal diplexer .................................................................198

User Manual 3DB19901AFAA Edition 01

2.7.4 MPT-MC with internal diplexer..............................................................................198


2.7.5 MPT-HC/HC-HQAM/MC/XP/XP-HQAM with branching filter ...........................................199
2.7.5.1 MPT ODU codes..........................................................................................200
2.7.5.2 External diplexer codes................................................................................200
2.7.6 MPT-HC/HC-HQAM/XP/XP-HQAM optical interface ......................................................200
2.7.7 MPT-HC/MPT-XP external modules (option) ..............................................................200
2.7.8 MPT-HC/HC-HQAM/MC/XP/XP-HQAM couplers ...........................................................200
2.7.9 OMT couplers ..................................................................................................201
2.7.10 OMT-C coupler ...............................................................................................202
2.7.11 Loads for unused ports......................................................................................204
2.8 Functional description ..............................................................................................204
2.8.1 MSS (Microwave Service Shelf) ..............................................................................204
2.8.1.1 MSS-4/8 modules........................................................................................206
2.8.1.2 Power distribution ......................................................................................206
2.8.1.3 +24 Vdc/-48 Vdc Converter unit......................................................................207
2.8.1.4 AC Converter unit for MSS-O ..........................................................................209
2.8.1.5 Core-E unit...............................................................................................210
2.8.1.6 32xE1 Local Access unit................................................................................213
2.8.1.7 2xSTM-1 Local Access unit.............................................................................215
2.8.1.8 ASAP unit.................................................................................................218
2.8.1.9 Modem unit ..............................................................................................221
2.8.1.10 MPT Access Unit (with PFoE) ........................................................................223
2.8.1.11 EAS unit .................................................................................................227
2.8.1.12 EASv2 unit ..............................................................................................229
2.8.2 MSS (Indoor/Outdoor unit)...................................................................................232
2.8.3 Power Injector.................................................................................................232
2.8.4 ODU300 .........................................................................................................234
2.8.4.1 ODU block diagram .....................................................................................235
2.8.4.2 RSSI Monitoring Point...................................................................................237
2.8.4.3 Waveguide Flange Data ................................................................................237
2.8.4.4 ODU Coupler .............................................................................................238
2.8.5 MPT-HC/HC-HQAM/XP/XP-HQAM ...........................................................................239
2.8.5.1 RSSI Monitoring Point...................................................................................246
2.8.5.2 Waveguide Flange Data ................................................................................247
2.8.5.3 MPT-HC/HC-HQAM/XP/XP-HQAM Coupler ..........................................................247
2.8.5.4 MPT-HC/HC-HQAM/XP/XP-HQAM Integrated OMT (Orthogonal Mode Transducer) ..........247
2.8.6 MPT-MC .........................................................................................................248
2.8.6.1 MPT-MC Coupler.........................................................................................250
2.8.7 MPT-HLS ........................................................................................................250
2.8.8 Protection schemes ...........................................................................................253
2.8.8.1 Protection schemes with ODU300 ....................................................................253
2.8.8.2 Protection schemes with MPT-HC/HC-HQAM/XP/XP-HQAM ......................................254
2.8.8.3 Protection schemes with MPT-HLS ...................................................................258
2.8.8.4 Core-E protection .......................................................................................259
2.8.9 Stacking for EAS unit/EASv2 unit/MPT Access unit ......................................................262
2.8.10 Ethernet Ring Protection ...................................................................................262
2.8.10.1 Definitions ..............................................................................................262
2.8.10.2 Ring Link and Ring Port...............................................................................262
2.8.10.3 ERPS operation.........................................................................................263

User Manual 3DB19901AFAA Edition 01

2.8.10.4 Ethernet Ring Protection switching criteria.......................................................267


2.8.10.5 ERPS and Core protection ............................................................................269
2.8.11 Radio Transmission Features with ODU300 ..............................................................269
2.8.11.1 Frequency Agility ......................................................................................269
2.8.11.2 Automatic Transmit Power Control (ATPC)........................................................270
2.8.11.3 Transmitted power control: RTPC function .......................................................270
2.8.11.4 Power Monitoring......................................................................................270
2.8.11.5 Adaptive Equalization ................................................................................271
2.8.11.6 XPIC (with MPT-HC/HC-HQAM/XP/XP-HQAM and MPT-HLS only)...............................271
2.8.11.7 Link identifier..........................................................................................273
2.8.11.8 Loopbacks with ODU300 ..............................................................................274
2.8.12 Radio Transmission Features with MPT-HC/HC-HQAM/HLS/MC/XP/XP-HQAM .....................274
2.8.12.1 Adaptive Equalization ................................................................................274
2.8.12.2 Link identifier..........................................................................................275
2.8.12.3 Loopbacks with MPT-HC/HC-HQAM/HLS/MC/XP/XP-HQAM .....................................275
2.8.12.4 Loopback activation...................................................................................278
2.8.12.5 Loopback life time ....................................................................................278
2.8.12.6 Packet throughput booster (Header compression) ...............................................279
2.8.13 TACACS+.......................................................................................................281
2.8.13.1 Overview ...............................................................................................281
2.8.14 TMN interfaces ...............................................................................................285
2.8.15 IP addressing .................................................................................................285
2.8.15.1 IPv4 addressing for the local IP address ...........................................................285
2.8.15.2 IPv4 addressing for the TMN local Ethernet interface IP address ..............................286
2.8.15.3 IPv6 addressing for the local IP address ...........................................................286
2.8.15.4 IPv6 addressing for the TMN local Ethernet interface IP address ..............................287
2.8.16 Admission control in Adaptive Modulation (only with ODU300) ......................................288
2.8.16.1 What does Admission Control mean? ............................................................288
2.8.16.2 Radio capacity in case of adaptive modulation...................................................288
2.8.16.3 Adaptive modulation and admission control enabled ...........................................289
2.8.16.4 Adaptive modulation and admission control disabled ..........................................292
2.8.17 Managed Services and profiles.............................................................................294
2.8.18 TDM and Ethernet traffic management ..................................................................297
2.8.18.1 TDM2TDM ...............................................................................................300
2.8.18.2 TDM2Eth ................................................................................................301
2.8.18.3 SDH2SDH ................................................................................................302
2.8.18.4 ETH2ETH ................................................................................................303
2.8.19 ATM Traffic Management ...................................................................................304
2.8.19.1 ATM Traffic Management on ASAP - PW Label Exp bits and scheduling type ................309
2.8.19.2 ATM Traffic Management on Modem card - Block diagram for ATM PW Flow
policer ................................................................................................................309
2.8.19.3 Support of ATMoMPLS Protocol Stack (with or without MPLS Tunnel Label ..................310
2.8.20 Ethernet Traffic Management .............................................................................312
2.8.20.1 802.1D (MAC Address bridge) .......................................................................312
2.8.20.2 802.1Q (Virtual bridge) ...............................................................................313
2.8.20.3 802.1ad (Provider bridge) ............................................................................313
2.8.20.4 Bridge type change....................................................................................314
2.8.20.5 Advanced Ethernet features .........................................................................316
2.8.21 LAG (Link Aggregation Group) .............................................................................322

User Manual 3DB19901AFAA Edition 01

2.8.21.1 LAG overview ..........................................................................................322


2.8.22 Quality Of Services (QoS) ...................................................................................342
2.8.22.1 QoS configuration .....................................................................................342
2.8.22.2 QoS for TMN packets ..................................................................................345
2.8.22.3 QoS in the MPT-HC/HC-HQAM/MC/XP/XP-HQAM ................................................346
2.8.22.4 QoS in L1 LAG with EASv2 ............................................................................346
2.8.23 Cross-connections ...........................................................................................347
2.8.23.1 E1 Cross-connections .................................................................................347
2.8.23.2 STM-1 Cross-connections .............................................................................348
2.8.23.3 Radio-Radio Cross-connections......................................................................348
2.8.23.4 Ethernet Cross-connections..........................................................................348
2.8.23.5 ATM PW cross-connections ...........................................................................348
2.8.23.6 Port Segregation ......................................................................................357
2.8.24 Software package rollback .................................................................................363
2.8.25 Synchronization for PDH/SDH/DATA ......................................................................364
2.8.25.1 Synchronization overview ............................................................................364
2.8.25.2 Synchronization Sources and protection policy...................................................366
2.8.25.3 Synchronization Sources assignment ...............................................................369
2.8.25.4 Synchronization sources assignment rules ........................................................370
2.8.25.5 Allowed synchronization sources assignment ....................................................371
2.8.26 Synchronization for E1 ports with ASAP unit ............................................................373
2.8.27 Synchronization distribution from 9500 MPR to 9400 AWY ............................................374
2.8.28 Synchronization connection in Stacking configuration with Core protection ......................375

3 NE Management by software application............................................................... 377


3.1 WebEML start ........................................................................................................377
3.2 WebEML Main View ..................................................................................................380
3.2.1 Tab-panels .....................................................................................................384
3.2.2 Main Tool Bar Area ............................................................................................386
3.2.3 Severity Alarm Area...........................................................................................388
3.2.4 Domain Alarm Synthesis Area ...............................................................................389
3.2.5 Management State Control Area ............................................................................390
3.2.6 Selection Criteria .............................................................................................392
3.2.6.1 Single left click:.........................................................................................393
3.2.6.2 Double left click: .......................................................................................393
3.2.6.3 Button Policy ............................................................................................393
3.3 How to configure a new equipment ..............................................................................393
3.4 Configuration Menu .................................................................................................395
3.4.1 NE Time Menu .................................................................................................395
3.4.2 Network Configuration Menu ................................................................................396
3.4.2.1 Local Configuration.....................................................................................397
3.4.2.2 NTP Configuration ......................................................................................398
3.4.2.3 Ethernet Configuration ................................................................................399
3.4.2.4 IP Static Routing Configuration .......................................................................399
3.4.2.5 OSPF Area Configuration...............................................................................400
3.4.2.6 IP Point to Point Configuration .......................................................................403
3.4.2.7 Activate IPv6 stack .....................................................................................403
3.4.2.8 Activate IPv4 stack .....................................................................................404
3.4.2.9 IPv6 pre-provisioning ...................................................................................404

User Manual 3DB19901AFAA Edition 01

3.4.2.10 Routing Information...................................................................................404


3.4.3 Alarm Severities Menu........................................................................................405
3.4.4 System Settings................................................................................................408
3.4.5 Cross connections Menu ......................................................................................413
3.4.5.1 Main Cross Connection View ..........................................................................413
3.4.5.2 How to create a cross-connection....................................................................423
3.4.5.3 TDM Cross-Connections ................................................................................427
3.4.5.4 SDH Cross-Connections with SDHACC - Transparent mode .......................................441
3.4.5.5 SDH Cross-Connections with SDHCHAN - Channelized mode .....................................451
3.4.5.6 ATM Cross-Connections ................................................................................457
3.4.5.7 LAG-LAG Cross-Connections ...........................................................................468
3.4.5.8 Ring Cross-Connections ................................................................................474
3.4.5.9 Ring Cross-Connections in a mixed fiber/microwave ring ........................................489
3.4.5.10 Create Ring Cross-connections in a mixed fiber-microwave Ring using the
aided cross-connection tool .......................................................................................634
3.4.6 LAG Configuration.............................................................................................644
3.4.6.1 LAG (Link Aggregation Group) overview ............................................................644
3.4.6.2 How to create an L1 Radio LAG.......................................................................649
3.4.6.3 How to Upgrade MPT-HC/HC-HQAM/XP/XP-HQAM to
MPT-HC/HC-HQAM/XP/XP-HQAM L1 LAG Port .................................................................656
3.4.6.4 How to create an L2 Ethernet LAG...................................................................659
3.4.6.5 How to remove a LAG ..................................................................................667
3.4.7 QoS Configuration .............................................................................................668
3.4.7.1 Scheduler Configuration ..............................................................................668
3.4.7.2 Queue Size Configuration .............................................................................669
3.4.7.3 QoS Classification .......................................................................................672
3.4.8 EFM OAM Configuration ......................................................................................677
3.4.8.1 Supported functions ....................................................................................678
3.4.8.2 EFM OAM with Core-E protection.....................................................................678
3.4.8.3 Link OAM operational status ..........................................................................679
3.4.8.4 DTE parameters .........................................................................................679
3.4.8.5 To configure EFM OAM .................................................................................680
3.4.9 OAM remote loopback ........................................................................................681
3.4.9.1 Activating OAM remote loopback.....................................................................681
3.4.9.2 ETH OAM alarms.........................................................................................683
3.4.10 AUX Cross Connections......................................................................................684
3.4.10.1 Local User Service Channel Cross-connection ....................................................684
3.4.10.2 Service Channels Cross-connection in pass-through .............................................684
3.4.10.3 How to create an AUX cross-connection ...........................................................684
3.4.10.4 How to delete an AUX Cross Connection...........................................................686
3.4.11 XPIC Configuration Menu ...................................................................................687
3.4.12 VLAN Configuration Menu...................................................................................687
3.4.13 Traffic Descriptors...........................................................................................687
3.4.14 Profile Management Menu ..................................................................................690
3.4.14.1 Introduction ............................................................................................690
3.4.14.2 User Profiles Management ..........................................................................691
3.4.14.3 User Management .....................................................................................692
3.4.14.4 USM Users Management..............................................................................696
3.4.15 Ethernet Features Shell.....................................................................................703

User Manual 3DB19901AFAA Edition 01

3.4.15.1 To open the Ethernet Features Shell ...............................................................704


3.4.15.2 Ethernet connectivity fault management (IEEE802.1ag) command list.......................704
3.4.15.3 Protocols command list...............................................................................724
3.4.15.4 TACACS+ command list ...............................................................................724
3.4.15.5 Example of a TACACS+ Management Session on the 9500MPR..................................727
3.4.15.6 APPENDIX A - Ethernet CFM Scenarios .............................................................739
3.4.15.7 APPENDIX B - Automatic MIP Creation .............................................................747
3.5 Diagnosis Menu.......................................................................................................750
3.5.1 Alarms...........................................................................................................750
3.5.2 Log Browsing ...................................................................................................784
3.5.2.1 Event Log Browser ......................................................................................785
3.5.3 Remote Inventory .............................................................................................788
3.5.4 Abnormal Condition List......................................................................................789
3.5.5 Summary Block Diagram View...............................................................................790
3.5.5.1 Main Block diagram view ..............................................................................790
3.5.5.2 PDH unit secondary view ..............................................................................793
3.5.5.3 SDH unit secondary view...............................................................................797
3.5.5.4 Radio unit secondary view (ODU300) ................................................................801
3.5.5.5 MPT-ACC unit secondary view (MPT-HC/HC-HQAM/XP/XP-HQAM) ..............................807
3.5.5.6 MPT-ACC unit secondary view (MPT-MC) ............................................................813
3.5.5.7 XPIC .......................................................................................................820
3.5.6 NE Inventory ...................................................................................................822
3.6 Supervision Menu ....................................................................................................823
3.6.1 Access State....................................................................................................823
3.6.1.1 Requested (Switching from the OS to the WebEML access state) ...............................824
3.6.1.2 OS (Switching from the WebEML access state back to the OS access state) ..................824
3.6.2 Restart NE ......................................................................................................825
3.6.3 Restart MPT ....................................................................................................825
3.6.3.1 MIB Management ........................................................................................826
3.6.3.2 Backup ...................................................................................................826
3.6.3.3 Restore ..................................................................................................827
3.6.3.4 Remove file .............................................................................................828
3.6.4 SW License .....................................................................................................829
3.7 SW Download Menu..................................................................................................830
3.7.1 Server Access Configuration .................................................................................830
3.7.2 Init Sw Download ..............................................................................................833
3.7.3 Sw Status .......................................................................................................834
3.7.4 How to upgrade the software from an older version ....................................................836
3.8 Equipment Tab-panel ...............................................................................................837
3.8.1 General .........................................................................................................837
3.8.2 Summary tab ...................................................................................................840
3.8.3 NE Neighbors tab ..............................................................................................841
3.8.4 Starting From Scratch ........................................................................................842
3.8.5 Tab panels in the Resource Detail Area ...................................................................844
3.8.6 Alarms tab-panel ..............................................................................................844
3.8.7 Settings tab-panel.............................................................................................844
3.8.8 Remote Inventory tab-panel (MSS-4/8 only) ..............................................................852
3.9 Protection Schemes Tab-panel ....................................................................................852
3.9.1 Equipment Protection Management ........................................................................867

User Manual 3DB19901AFAA Edition 01

3.9.1.1 Protection Scheme Parameters.......................................................................867


3.9.2 Rx Radio Protection Management ..........................................................................869
3.9.2.1 Alarms ....................................................................................................870
3.9.2.2 Protection Scheme Parameters.......................................................................870
3.9.2.3 Commands ...............................................................................................871
3.9.3 HSB Protection Management ................................................................................873
3.9.3.1 Protection Scheme Parameters.......................................................................873
3.9.3.2 Commands ...............................................................................................873
3.10 Synchronization Tab-panel .......................................................................................874
3.10.1 Synchronization Sources and protection policy .........................................................875
3.10.1.1 Clock Source Quality Level...........................................................................876
3.10.1.2 Quality Level Priority ................................................................................876
3.10.1.3 Hold-off and Wait-To-Restore ......................................................................877
3.10.2 Synchronization Sources assignment......................................................................877
3.10.3 Synchronization sources assignment rules ..............................................................879
3.10.4 Allowed synchronization sources assignment ...........................................................879
3.10.4.1 Synchronization Source with EAS unit..............................................................880
3.10.4.2 Synchronization Source with MPT ..................................................................880
3.10.4.3 Synchronization Source with MPT PFoE Access unit .............................................881
3.10.4.4 Protected radio configuration with one MPT PFoE Access unit ................................881
3.10.4.5 Protected radio configuration with 2 MPT PFoE Access unit ...................................881
3.10.5 SSM Summary Table .........................................................................................881
3.11 Connections Tab-panel ............................................................................................882
3.12 PDH VIEW for PDH DOMAIN (to open this view double click on a PDH unit) ..............................883
3.12.1 General information on the PDH domain menu .........................................................883
3.12.2 Alarms & Settings ............................................................................................884
3.12.2.1 Alarms tab-panel ......................................................................................885
3.12.2.2 Settings tab-panel.....................................................................................886
3.12.2.3 General information on Circuit Emulation ........................................................887
3.12.2.4 Node Timing configuration...........................................................................889
3.12.3 Loopback ......................................................................................................890
3.12.3.1 How to activate a loopback..........................................................................891
3.12.3.2 How to remove a loopback ..........................................................................892
3.13 SDH VIEW for SDH DOMAIN (to open this view double click on an SDH unit)..............................892
3.13.1 General information on the SDH unit .....................................................................892
3.13.1.1 Protection .............................................................................................893
3.13.1.2 Clocking options .......................................................................................893
3.13.1.3 Tab-panels..............................................................................................893
3.13.2 Alarms .........................................................................................................893
3.13.3 Settings for SDHACC unit (Transparent mode) ..........................................................894
3.13.4 Loopback ......................................................................................................895
3.13.4.1 How to activate a loopback..........................................................................896
3.13.4.2 How to remove a loopback ..........................................................................897
3.13.5 Settings for SDHCHAN unit (Channelized mode) ........................................................897
3.13.5.1 Signal Mode.............................................................................................900
3.13.5.2 Service Profile .........................................................................................900
3.13.5.3 Buttons .................................................................................................901
3.13.5.4 General information on Circuit Emulation........................................................901
3.14 EAS VIEW for P8ETH and EASv2 ..................................................................................902

10

User Manual 3DB19901AFAA Edition 01

3.14.1 EAS Domain ...................................................................................................902


3.14.1.1 Ethernet Physical Interface ..........................................................................903
3.15 Ethernet Ring Configuration View ...............................................................................918
3.15.1 ERP Configuration ...........................................................................................918
3.15.1.1 ERP Topology...........................................................................................918
3.15.1.2 Maximum number of ERPS topologies ..............................................................918
3.15.1.3 ERP Instances ..........................................................................................922
3.15.2 ERP Configuration procedure ..............................................................................930
3.15.2.1 Step 1: Topology creation (Create new Ring Topology field)...................................931
3.15.2.2 Step 2: ERP Instance Creation.......................................................................933
3.15.2.3 Step 3: Add VLANs to created instances ...........................................................937
3.15.2.4 Step 4: OAM switching criteria (optional) .........................................................939
3.15.2.5 Step 5: ERP Instances enabling......................................................................939
3.15.3 Configuration example of an Ethernet ring..............................................................940
3.15.4 To upgrade a Ring to R5.1.0 software from a release prior to R5.0 .................................942
3.16 XPIC configuration .................................................................................................951
3.16.1 XPIC overview ................................................................................................951
3.16.2 Automatic remote TX mute ................................................................................953
3.16.2.1 Root causes.............................................................................................955
3.16.3 How to configure the XPIC.................................................................................956
3.16.3.1 2x(1+0) or Radio LAG XPIC ...........................................................................958
3.16.3.2 2x(1+1) XPIC............................................................................................961
3.16.4 How to remove the XPIC association .....................................................................963
3.17 RADIO VIEW for RADIO DOMAIN ..................................................................................963
3.17.1 General information on the Radio domain menu .......................................................963
3.17.2 Power Source .................................................................................................965
3.17.2.1 Mode 1 - QMA (only with MPT-HC/HC-HQAM on the MPT Access unit) ........................969
3.17.2.2 Mode 2 - PFoE (Power Feed on Ethernet)..........................................................970
3.17.3 Alarms .........................................................................................................970
3.17.4 Radio Settings tabs ..........................................................................................970
3.17.4.1 ODU300 .................................................................................................970
3.17.4.2 MPT-HC/HC-HQAM/XP/XP-HQAM ...................................................................980
3.17.4.3 MPT-MC .................................................................................................996
3.17.4.4 MPT-HLS............................................................................................... 1008
3.17.4.5 Monodirectional links ............................................................................... 1023
3.17.5 Measurement ............................................................................................... 1024
3.17.5.1 How to read a Power Measurement file ......................................................... 1027
3.18 Loopback tab-panel for ODU300 ............................................................................... 1028
3.18.1 How to activate a loopback .............................................................................. 1029
3.18.2 How to remove a loopback ............................................................................... 1030
3.19 ATM view for ATM DOMAIN (to open this view double click on an ASAP unit) .......................... 1030
3.19.1 E1 Layer ..................................................................................................... 1030
3.19.2 IMA Layer.................................................................................................... 1032
3.19.3 ATM Layer................................................................................................... 1035
3.19.3.1 ATM Layer Configuration ........................................................................... 1036
3.19.3.2 VP Layer Configuration ............................................................................ 1037
3.19.3.3 VC Layer Configuration ............................................................................ 1041
3.19.4 ATM PW Layer .............................................................................................. 1043
3.19.4.1 ATM PW Parameters................................................................................. 1043

User Manual 3DB19901AFAA Edition 01

11

3.19.4.2 VPI/VCI Translation ................................................................................. 1045


3.20 CORE VIEW for Core-E and ETHERNET DOMAIN (to open this view double click on a
Core-E, MSS-1 or MSS-O unit)............................................................................................ 1045
3.20.1 Core-E domain.............................................................................................. 1045
3.20.1.1 Ethernet Physical Interface ........................................................................ 1046
3.20.1.2 TMN Interface ........................................................................................ 1061
3.20.1.3 Settings tab-panel for TMN In-band ............................................................. 1064
3.20.1.4 Settings tab-panel for TMN Ethernet Port #4 ................................................... 1066
3.20.1.5 MPT-HC/HC-HQAM/XP/XP-HQAM connected to the Core-E .................................. 1067
3.21 MSS External Input Point view (to open this view double click on the HK inputs on an
MSS-1)....................................................................................................................... 1068
3.21.1 Input External Points ...................................................................................... 1068
3.22 MSS A-FANS main view (to open this view double click on an A-FANS card) ............................ 1069
3.22.1 Input External Points ...................................................................................... 1069
3.23 AUX view for AUX DOMAIN (to open this view double click on the AUX peripheral unit) ............. 1070
3.23.1 Settings...................................................................................................... 1071
3.23.2 External Points ............................................................................................. 1072
3.23.2.1 Input External Points ............................................................................... 1072
3.23.2.2 Output External Points ............................................................................. 1073
3.24 WT Performance Monitoring Suite............................................................................. 1075
3.24.1 How to start the WT Performance Monitoring Suite ................................................. 1075
3.24.2 Tool bar ..................................................................................................... 1076
3.24.3 Bar Menu .................................................................................................... 1079
3.24.3.1 Export ................................................................................................. 1081
3.24.3.2 Print ................................................................................................... 1082
3.24.4 Feature bar area ........................................................................................... 1083
3.24.5 NE Measurement Main Tree .............................................................................. 1084
3.24.5.1 List View .............................................................................................. 1085
3.24.5.2 Overview.............................................................................................. 1085
3.24.5.3 Birds Eye View ...................................................................................... 1086
3.24.6 How to Start and Stop the Measurements ............................................................. 1087
3.24.6.1 Start the Measurements ............................................................................ 1087
3.24.6.2 Stop the Measurements............................................................................. 1089
3.24.6.3 Offline Mode ......................................................................................... 1089
3.24.7 PM selectable options ..................................................................................... 1092
3.24.8 Ethernet Statistics ......................................................................................... 1093
3.24.8.1 CORE-ENH unit Ethernet Statistics................................................................ 1094
3.24.8.2 MPTACC unit, MD300, EAS and EASv2 unit Ethernet Statistics ............................... 1098
3.24.8.3 Compression Gain ................................................................................... 1106
3.24.8.4 Layer 1 Radio LAG Ethernet Statistics ........................................................... 1108
3.24.8.5 Formulas used for the Ethernet Statistics elaborated counters.............................. 1113
3.24.9 RADIO PMs................................................................................................... 1114
3.24.9.1 General information on the radio performance monitoring process ........................ 1114
3.24.9.2 RADIO PMs performance monitoring procedures ............................................... 1116
3.24.9.3 Threshold management ............................................................................ 1121
3.24.9.4 How to display a threshold......................................................................... 1121
3.24.9.5 How to create a new threshold ................................................................... 1122
3.24.9.6 How to modify/delete a threshold ............................................................... 1124
3.24.9.7 How to associate a threshold ...................................................................... 1125

12

User Manual 3DB19901AFAA Edition 01

3.24.10 Adaptive Modulation ..................................................................................... 1126


3.24.10.1 Adaptive Modulation PMs performance monitoring procedures ............................ 1126
3.24.11 PDH Performance Monitoring ........................................................................... 1129
3.24.11.1 P32E1DS1 unit performances..................................................................... 1129
3.24.11.2 Incoming ............................................................................................ 1130
3.24.11.3 Outgoing............................................................................................. 1132
3.24.11.4 Threshold management ........................................................................... 1133
3.24.11.5 Example of the other views ...................................................................... 1137
3.24.12 IMA Layer Statistics ...................................................................................... 1139
3.24.12.1 IMA Group Monitoring ............................................................................. 1139
3.24.13 ATM Interface Statistics ................................................................................. 1142
3.24.13.1 Interface ............................................................................................ 1143
3.24.14 RSL History ................................................................................................ 1147
3.25 VLAN management ............................................................................................... 1150
3.25.1 802.1D ....................................................................................................... 1150
3.25.2 802.1Q ....................................................................................................... 1151
3.25.3 802.1ad...................................................................................................... 1154
3.25.3.1 Provider bridge components....................................................................... 1155
3.25.3.2 Ethernet frames processing........................................................................ 1155
3.25.3.3 Cross-connected flows processing ................................................................ 1155
3.25.3.4 Provider Bridge ports with Ethernet LAG ........................................................ 1156
3.25.4 VLAN Table Management ................................................................................. 1157
3.25.5 Ethernet Ring............................................................................................... 1160
3.26 Network Element Overview .................................................................................... 1161
3.26.1 Main view ................................................................................................... 1161
3.26.2 NE Configuration area..................................................................................... 1162
3.26.2.1 NE Information....................................................................................... 1163
3.26.2.2 NE Description ....................................................................................... 1163
3.26.2.3 Command Buttons ................................................................................... 1164
3.26.3 Status & Alarms area ...................................................................................... 1165
3.26.4 Supervision Function ...................................................................................... 1165
3.26.5 Bar Menu .................................................................................................... 1166
3.26.6 CS (Community String) .................................................................................... 1168
3.27 NEtO Servers Manager Overview ............................................................................... 1171
3.27.1 Launch NEtO Servers Manager tool...................................................................... 1172
3.27.2 FTP/SFTP Server management .......................................................................... 1172
3.27.3 RMI Resource management............................................................................... 1173
3.27.4 Close NEtO Servers Manager Tool ....................................................................... 1174
3.28 TCP/UPD ports required by DCN Protocols................................................................... 1175

4 Installation...................................................................................................1177
4.1 Hardware Installation ............................................................................................. 1177
4.1.1 Power consumption ......................................................................................... 1178
4.1.2 Rack Installation............................................................................................. 1179
4.1.2.1 General ................................................................................................. 1179
4.1.2.2 ETSI Rack Installation ................................................................................ 1180
4.1.2.3 Laborack (19") installation .......................................................................... 1184
4.1.2.4 Rack grounding ........................................................................................ 1185
4.1.2.5 MSS subrack installation ............................................................................. 1187

User Manual 3DB19901AFAA Edition 01

13

4.1.2.6 Top Rack Unit (TRU).................................................................................. 1191


4.1.2.7 -48 Vdc Power Supply connection .................................................................. 1200
4.1.2.8 +24 Vdc Power Supply connection ................................................................. 1202
4.1.2.9 Wall Mounting Installation........................................................................... 1203
4.1.3 MSS Indoor Installation ..................................................................................... 1204
4.1.3.1 Indoor accessories for MSS .......................................................................... 1205
4.1.3.2 Indoor cables .......................................................................................... 1206
4.1.3.3 AUX card housekeeping alarm connectors ....................................................... 1212
4.1.3.4 Enhanced fan alarm connectors .................................................................... 1214
4.1.3.5 Accessories for SDH SFP.............................................................................. 1216
4.1.3.6 Accessories for E3 SFP ............................................................................... 1216
4.1.3.7 Optical splitters for STM-1 signal and EoSDH (SFP for port #5 and #6 of Core-E
unit) ................................................................................................................. 1216
4.1.3.8 Cords to be used with 2xE1 SFP (SFP for port #5 and #6 of Core-E unit) .................... 1216
4.1.3.9 MPT Power units ...................................................................................... 1218
4.1.3.10 Distributors ........................................................................................... 1238
4.1.3.11 MSS cards ............................................................................................. 1241
4.1.3.12 Ethernet Electrical Cables ........................................................................ 1244
4.1.3.13 Ethernet Optical Cables ........................................................................... 1244
4.1.3.14 Type of Indoor configurations ..................................................................... 1245
4.1.3.15 MSS-4/8 installation................................................................................. 1293
4.1.3.16 MSS-1 installation.................................................................................... 1299
4.1.3.17 Connectors on the front panel of the MSS-1, 32E1 PDH card and 16 E1 ASAP
card (68 Pin SCSI Functions) ..................................................................................... 1310
4.1.3.18 Connectors on the front panel of the AUX peripheral card ................................... 1313
4.1.3.19 2xE1 SFP pin functions.............................................................................. 1318
4.1.3.20 Interconnection to AWY ............................................................................ 1319
4.1.3.21 Power Injector Indoor Installation ................................................................ 1319
4.1.4 MSS-O Installation ........................................................................................... 1324
4.1.4.1 Equipment placement................................................................................ 1324
4.1.4.2 Equipment grounding................................................................................. 1326
4.1.4.3 Equipment powering ................................................................................. 1329
4.1.4.4 Data connection on MSS-O........................................................................... 1330
4.1.4.5 Electrical data connections ......................................................................... 1331
4.1.4.6 Optical data connections ............................................................................ 1332
4.1.5 ODU300 Installation......................................................................................... 1333
4.1.5.1 Installing the Antenna................................................................................ 1334
4.1.5.2 Installing the ODU .................................................................................... 1335
4.1.5.3 Installing a Coupler ................................................................................... 1350
4.1.5.4 Installing ODU Cables and Connectors ............................................................. 1355
4.1.5.5 Weatherproofing ...................................................................................... 1359
4.1.6 MPT-HC/HC-HQAM/MPT-XP/XP-HQAM Installation..................................................... 1360
4.1.6.1 External module to be installed (MPT-HC/XP only) ............................................. 1362
4.1.6.2 MPT-HC/HC-HQAM/XP/XP-HQAM operative information ....................................... 1367
4.1.6.3 How to change polarization in the MPT-HC/XP/HC-HQAM/XP-HQAM......................... 1384
4.1.6.4 Types of RF couplers ................................................................................. 1386
4.1.6.5 Types of RF OMTs ..................................................................................... 1389
4.1.6.6 Types of RF loads for unused ports ................................................................ 1395
4.1.6.7 Types of Pole Mounting Installation kits .......................................................... 1396

14

User Manual 3DB19901AFAA Edition 01

4.1.6.8 Types of nose adapters .............................................................................. 1399


4.1.6.9 1+0 MPT-HC/HC-HQAM/XP/XP-HQAM installation (integrated antenna) - all
frequencies......................................................................................................... 1400
4.1.6.10 1+0 MPT-HC/HC-HQAM/XP/XP-HQAM installation (non integrated antenna) all frequencies..................................................................................................... 1404
4.1.6.11 1+1 MPT-HC/HC-HQAM/XP/XP-HQAM installation (integrated antenna).................... 1407
4.1.6.12 1+1 MPT-HC/HC-HQAM installation (non integrated antenna) ............................... 1446
4.1.6.13 Cable connections (MPT-HC/HC-HQAM/XP/XP-HQAM to MSS)................................ 1456
4.1.6.14 Direct Interconnection between two MPT-HC/HC-HQAM/XP/XP-HQAM .................... 1464
4.1.6.15 Installing the Flextwist waveguide (not integrated antenna cases) ...................... 1468
4.1.6.16 MPT-HC/HC-HQAM/XP/XP-HQAM system grounding ........................................... 1470
4.1.6.17 Cable Grounding ..................................................................................... 1473
4.1.6.18 Type N connectors and Grounding kits waterproofing on the IDU/ODU cables............ 1475
4.1.7 MPT-MC Installation......................................................................................... 1476
4.1.7.1 MPT-MC operative information ..................................................................... 1477
4.1.7.2 How to change polarization in the MPT-MC....................................................... 1486
4.1.7.3 Types of RF couplers ................................................................................. 1488
4.1.7.4 Types of RF integrated OMTs ....................................................................... 1488
4.1.7.5 Types of RF OMT-Cs .................................................................................. 1488
4.1.7.6 Types of RF loads for unused ports ................................................................ 1489
4.1.7.7 Types of Pole Mounting Installation kits .......................................................... 1489
4.1.7.8 Types of nose adapters .............................................................................. 1489
4.1.7.9 1+0 MPT-MC installation (integrated antenna) - all frequencies .............................. 1489
4.1.7.10 1+0 MPT-MC installation (non integrated antenna) - all frequencies ....................... 1493
4.1.7.11 1+1 MPT-MC installation (integrated antenna) ................................................. 1495
4.1.7.12 1+1 MPT-MC installation (non integrated antenna) ............................................ 1506
4.1.7.13 How to terminate and to connect the Ethernet cable (MPT side) ........................... 1513
4.1.7.14 Installing the Flextwist waveguide (not integrated antenna cases) ...................... 1514
4.1.7.15 MPT-MC system grounding ......................................................................... 1514
4.1.7.16 Cable Grounding ..................................................................................... 1514
4.1.8 Nose Adapter for MPT-HC/HC-HQAM/XP/XP-HQAM and MPT-MC .................................... 1514
4.1.9 Flextwists for MPT-HC/HC-HQAM/XP/XP-HQAM and MPT-MC ........................................ 1514
4.1.10 MPT-HLS Installation in an ETSI rack.................................................................... 1515
4.1.10.1 MPT-HLS TRU installation requirements ........................................................ 1515
4.1.10.2 Preparing power cabling for MPT-HLS components ............................................ 1515
4.1.10.3 MPT-HLS fan assembly .............................................................................. 1519
4.1.10.4 MSS-8 and E1 distribution patch panel .......................................................... 1528
4.1.10.5 MPR-LH subrack ..................................................................................... 1535
4.1.10.6 MPT-HLS Module installation ...................................................................... 1541
4.1.10.7 MPT-HLS module connections to MPR-LH components........................................ 1543
4.1.11 MPT-HLS installation in an LSY rack .................................................................... 1556
4.1.11.1 LSY existing installations ........................................................................... 1556
4.1.11.2 Upgrade use cases................................................................................... 1558
4.1.11.3 Common operation description ................................................................... 1563
4.1.11.4 Cooling system (fan module) replacement ...................................................... 1568
4.1.11.5 Upgrading of the transceivers sub-shelf ......................................................... 1575
4.1.11.6 Branching section expansion....................................................................... 1580
4.1.11.7 Positioning and powering of the MSS-8 sub-shelf............................................... 1581
4.1.12 MPT-HLS system expansion............................................................................... 1583

User Manual 3DB19901AFAA Edition 01

15

4.1.12.1 Preparation of the system for expansion ........................................................ 1583


4.1.12.2 RT sub-rack operations for system expansion................................................... 1584
4.1.12.3 Branching expansion ................................................................................ 1592
4.1.12.4 Cooling system upgrading .......................................................................... 1609
4.1.12.5 TRU upgrading ....................................................................................... 1610
4.1.12.6 Available kits for system expansion .............................................................. 1610
4.1.13 Antenna Alignment ....................................................................................... 1611
4.1.13.1 Preparation........................................................................................... 1611
4.1.13.2 Signal Measurement................................................................................. 1612
4.1.13.3 Aligning the Antenna................................................................................ 1617
4.1.13.4 Main Beams and Side Lobes ........................................................................ 1623
4.2 Software local copy ............................................................................................... 1626
4.2.1 Getting Started .............................................................................................. 1626
4.2.2 PC Characteristics........................................................................................... 1627
4.2.2.1 Local copy of the Software Package (SWP) to the PC........................................... 1628
4.2.3 Local copy of the WebEML and TCO Suite Software to PC............................................ 1630
4.2.3.1 Local Copy of WebEML (JUSM/CT) ................................................................. 1632
4.2.3.2 Local Copy of Provisioning Tool installation ...................................................... 1636
4.2.4 Configure PC Network Card to Connect to NE ......................................................... 1637
4.2.5 Non-administrator user..................................................................................... 1641
4.2.6 Download Software Package to NE ....................................................................... 1643
4.2.6.1 Server Access Configuration......................................................................... 1644
4.2.6.2 Enable FTP/SFTP server ............................................................................. 1645
4.2.6.3 Init SW Download .................................................................................... 1646
4.2.6.4 Software Status Detail ............................................................................... 1650

5 Provisioning .................................................................................................1653
5.1 Provisioning by Provisioning Tool ............................................................................... 1653
5.1.1 Start Provisioning Tool ..................................................................................... 1653
5.1.1.1 Provisioning tool screens ............................................................................ 1655
5.2 Provisioning by WebEML .......................................................................................... 1723
5.2.1 Start WebEML ................................................................................................ 1723
5.2.2 Provisioning .................................................................................................. 1725
5.2.2.1 Enable Plug-In Cards ................................................................................. 1726
5.2.2.2 Provision Plug-In Cards............................................................................... 1753
5.2.2.3 Provision XPIC ......................................................................................... 1757
5.2.2.4 Provision Space Diversity ............................................................................ 1757
5.2.2.5 Provision Synchronization ........................................................................... 1758
5.2.2.6 Provision NTP protocol ............................................................................... 1758
5.2.2.7 Provision NE Time..................................................................................... 1760
5.2.2.8 Provision VLAN (if required)......................................................................... 1761
5.2.2.9 Provision Cross-Connections ........................................................................ 1761
5.2.2.10 Provision AUX Cross-Connections ................................................................. 1762
5.2.2.11 Provision Ethernet Ring............................................................................. 1763
5.2.2.12 Provision LAG ........................................................................................ 1763
5.2.2.13 Provision QoS......................................................................................... 1764
5.2.2.14 Provision Ethernet Connectivity fault management ........................................... 1765
5.2.2.15 Provision System..................................................................................... 1766
5.2.2.16 Provision Local NE IP Address ..................................................................... 1768

16

User Manual 3DB19901AFAA Edition 01

5.2.2.17
5.2.2.18
5.2.2.19
5.2.2.20
5.2.2.21
5.2.2.22

Provision TMN in-band .............................................................................. 1769


Provision TMN Ethernet Port....................................................................... 1769
Provision Ethernet Port 4 for TMN (if required) ................................................ 1769
Provision IP Static Routing ......................................................................... 1769
Provision OSPF Static Routing ..................................................................... 1771
IPv6 pre-provisioning ............................................................................... 1772

6 Maintenance and Trouble-clearing .....................................................................1777


6.1
6.2
6.3
6.4

Introduction ........................................................................................................ 1777


Maintenance Philosophy .......................................................................................... 1777
Personal Computer (PC)/Laptop ................................................................................ 1778
Troubleshooting.................................................................................................... 1778
6.4.1 Before Going to Site Checklist ............................................................................ 1778
6.4.2 Troubleshooting Basics ..................................................................................... 1780
6.4.3 Troubleshooting Path Problems ........................................................................... 1833
6.4.3.1 Path Problems on a Commissioned Link ........................................................... 1834
6.4.3.2 Path Problems on a New Link ....................................................................... 1834
6.4.4 Troubleshooting Configuration Problems ................................................................ 1835
6.4.5 Troubleshooting Ethernet Problems...................................................................... 1835
6.4.6 Troubleshooting TMN Problems ........................................................................... 1836
6.4.7 Analyzing the Ethernet traffic with the Troubleshooting Tool....................................... 1838
6.5 Card Removal and Replacement ............................................................................... 1840
6.5.1 Core-E Card Removal and Replacement with Core Protection....................................... 1842
6.5.2 Flash card replacement procedure ....................................................................... 1843
6.5.3 ODU300 or MPT-HC/HC-HQAM/MC/XP/XP-HQAM removal and replacement ...................... 1844
6.6 Removal and replacement of a 7/8 GHz Standard Power MPT-HC/MC in 1+1 configuration .......... 1844
6.7 MPT-HC upgrade or replacement to MPT-HQAM .............................................................. 1844
6.7.1 Prerequisites ................................................................................................. 1845
6.7.2 General ....................................................................................................... 1845
6.7.3 Procedure .................................................................................................... 1846
6.8 Upgrade from Not Protected to a Protected Radio (with ODU300) ........................................ 1853
6.8.1 1+0 Adaptive Modulation to 1+1 HSB Adaptive Modulation and 1+1 EPS ........................... 1853
6.8.1.1 1+0 Static Modulation to 1+1 HSB Static Modulation and 1+1 EPS............................. 1855
6.8.2 1+0 to 1+1 Frequency Diversity and 1+1 EPS............................................................ 1855
6.9 Upgrade from Not Protected to a Protected Radio (with
MPT-HC/HC-HQAM/MC/XP/XP-HQAM) ................................................................................. 1856
6.9.1 1+0 Adaptive Modulation to 1+1 HSB/FD Adaptive Modulation and 1+1 EPS ....................... 1856
6.9.2 1+0 Static Modulation to 1+1 HSB/FD Static Modulation and 1+1 EPS .............................. 1858
6.10 Downgrade from Protected to a Not Protected Radio (with ODU300) ................................... 1858
6.10.1 1+1 HSB Adaptive Modulation and 1+1 EPS to 1+0 Adaptive Modulation .......................... 1858
6.10.2 1+1 HSB Static Modulation and 1+1 EPS to 1+0 Static Modulation ................................. 1859
6.10.3 1+1 FD to 1+0............................................................................................... 1859
6.11 Downgrade from Protected to a Not Protected Radio (with
MPT-HC/HC-HQAM/MC/XP/XP-HQAM) ................................................................................ 1861
6.11.1 1+1 HSB/FD Adaptive Modulation and 1+1 EPS to 1+0 Adaptive Modulation...................... 1861
6.11.2 1+1 HSB/FD Static Modulation and 1+1 EPS to 1+0 Static Modulation ............................. 1862
6.12 Software package rollback ..................................................................................... 1862
6.13 WebEML/TCO Suite/NEtO startup issues ..................................................................... 1867
6.13.1 Resolve WebEML/TCO Suite/NEtO startup issues..................................................... 1867

User Manual 3DB19901AFAA Edition 01

17

6.13.2 Remove ALL previous versions of WebEML/TCO Suite ............................................... 1868


6.14 Cleaning ........................................................................................................... 1868

7 Lineup and Commissioning ..............................................................................1869


7.1 Introduction ........................................................................................................ 1869
7.1.1 General ....................................................................................................... 1869
7.1.2 SafetyEMCEMFESD norms and cautions to avoid equipment damage ............................ 1871
7.1.3 Conventions .................................................................................................. 1871
7.1.4 Summary of the lineup, commissioning, and acceptance phases................................... 1872
7.1.5 General information about test bench drawings ....................................................... 1874
7.2 Commissioning of STATION A phase 1 (Turn up) ............................................................ 1874
7.2.1 Turnon preliminary operations........................................................................... 1875
7.2.2 Powering up the MSS(s) with ODU(s) connected........................................................ 1875
7.3 Commissioning of STATION B phase 1 (Turn up) ............................................................ 1876
7.4 Fine antenna alignment and preliminary checks Stations A & B ......................................... 1876
7.4.1 Fine antenna alignment .................................................................................... 1876
7.4.2 Preliminary checks .......................................................................................... 1877
7.4.2.1 Verify ODU300 and MPT-HC/HC-HQAM/MC/XP/XP-HQAM alarm status ...................... 1877
7.4.2.2 Transmitter power output check ................................................................... 1877
7.4.2.3 Received power measurement...................................................................... 1878
7.5 End of commissioning phase 1 (Turn up) in STATION A ...................................................... 1881
7.6 Commissioning station A phase 2 (acceptance test) ....................................................... 1882
7.6.1 Installation and cabling visual inspection ............................................................... 1884
7.6.1.1 Indoor System installation and cabling visual inspection ....................................... 1884
7.6.1.2 Outdoor System installation and cabling visual inspection..................................... 1885
7.6.2 System configuration ....................................................................................... 1885
7.6.2.1 Check Software Release ............................................................................. 1885
7.6.2.2 Check/set Mode (Presettings or Adaptive modulation), Channel spacing,
Modulation ......................................................................................................... 1885
7.6.2.3 Check/set Link Identifier configuration (optional) .............................................. 1885
7.6.2.4 Check/set the QoS configuration................................................................... 1886
7.6.2.5 Check/set the LAG configuration .................................................................. 1886
7.6.2.6 Check/set the Automatic Restoration Criteria (only 1+1) ...................................... 1886
7.6.2.7 Check/set Tx/Rx Spacing, Transmission and Reception frequencies ......................... 1887
7.6.2.8 Check/set Tx power (ATPC Off) or Tx range and Rx threshold (ATPC On)................... 1887
7.6.2.9 Check/set the XPIC configuration (if required) .................................................. 1888
7.6.2.10 Check/set the synchronization .................................................................... 1888
7.6.2.11 Check/set the encryption (if required) .......................................................... 1889
7.6.2.12 Tx and Rx power measurement (with WebEML) ................................................ 1889
7.6.2.13 Loopback functionality ............................................................................. 1889
7.6.2.14 Protection functionality (1+1 only) ............................................................... 1892
7.6.3 P32E1 unit .................................................................................................... 1892
7.6.3.1 Balanced or Unbalanced impedance ............................................................... 1893
7.6.3.2 Check/set E1 tributaries configuration............................................................ 1893
7.6.3.3 Protection functionality (1+1 only) ............................................................... 1893
7.6.3.4 E1 point to point loop test .......................................................................... 1894
7.6.4 STM-1 unit .................................................................................................... 1896
7.6.4.1 Check/set STM-1 configuration ..................................................................... 1896
7.6.4.2 Protection functionality (1+1 only) ............................................................... 1896

18

User Manual 3DB19901AFAA Edition 01

7.6.4.3 STM-1 point to point loop test ...................................................................... 1897


7.6.5 16E1/DS1 ASAP unit......................................................................................... 1899
7.6.5.1 Check/set E1 layer configuration .................................................................. 1899
7.6.5.2 Check/set IMA layer configuration ................................................................. 1899
7.6.5.3 Check/set ATM layer configuration ................................................................ 1899
7.6.5.4 Check/set ATM PW layer configuration ........................................................... 1899
7.6.6 A-FANS unit .................................................................................................. 1899
7.6.6.1 Check/set the Housekeeping configuration ...................................................... 1900
7.6.7 MSS-1 unit .................................................................................................... 1900
7.6.7.1 Check/set the Housekeeping configuration ...................................................... 1900
7.6.8 AUX unit ...................................................................................................... 1900
7.6.8.1 Check/set AUX unit configuration.................................................................. 1900
7.6.8.2 Check/set the Housekeeping configuration ...................................................... 1900
7.6.9 EAS unit....................................................................................................... 1901
7.6.9.1 Check/set EAS unit configuration .................................................................. 1901
7.6.10 EASv2 unit................................................................................................... 1901
7.6.10.1 Check/set EASv2 unit configuration .............................................................. 1901
7.6.11 Core-E unit.................................................................................................. 1901
7.6.11.1 Check the Software license Code ................................................................. 1901
7.6.11.2 Check/set Traffic Ethernet port parameters ................................................... 1901
7.6.12 NE configuration ........................................................................................... 1902
7.6.12.1 Check/set the local NE IP address ................................................................ 1902
7.6.12.2 Check/set OSPF Area Configuration .............................................................. 1902
7.6.12.3 Check/set the Ethernet access (OS) configuration............................................. 1902
7.6.12.4 Check/set IP static routing configuration ....................................................... 1902
7.6.13 Data/Time settings ........................................................................................ 1903
7.6.14 E1 Hop stability test....................................................................................... 1903
7.6.15 STM-1 Hop stability test .................................................................................. 1905
7.6.16 Ethernet Traffic stability test ........................................................................... 1907
7.6.17 ATM Traffic stability test ................................................................................. 1912
7.6.18 64 kbit/s Service Channel functionality test (optional) ............................................. 1915
7.7 Commissioning station B Phase 2 (acceptance Test) ....................................................... 1916
7.8 Final operations.................................................................................................... 1917
7.9 Annex A: fine antenna alignment ............................................................................... 1917

8 Appendix A - Fiber-Microwave Protection ............................................................1919


8.1 Overview ............................................................................................................ 1919
8.2 How to create the Fiber-Microwave Protection .............................................................. 1923
8.2.1 Step 1: Topology creation (Create new Ring Topology field) ....................................... 1924
8.2.2 Step 2: ERP Instance Creation............................................................................. 1926
8.2.3 Step 3: Add VLANs to the instance ....................................................................... 1930
8.2.4 Step 4: Cross-connection creation........................................................................ 1932
8.2.5 Step 5: ERP Instances enabling ........................................................................... 1940
8.3 How to create the Fiber-Microwave Protection without removing the existing
cross-connections ......................................................................................................... 1941
8.3.1 Requirements ................................................................................................ 1941
8.3.2 Step 1: Radio slot "cleanup" .............................................................................. 1942
8.3.3 Step 2: Radio-fiber creation............................................................................... 1945
8.3.4 Step 3: HW apply and update ............................................................................. 1945

User Manual 3DB19901AFAA Edition 01

19

9 Abbreviations ...............................................................................................1947

20

User Manual 3DB19901AFAA Edition 01

List of Figures
1 Safety, EMC, EMF, ESD Norms and Equipment Labeling............................................... 65
Figure 1.1 Declaration of conformity for R5.x........................................................................ 66
Figure 1.2 Declaration of conformity for MPT-HLS................................................................... 67
Figure 1.3 Declaration of conformity for 9600 LSY extended with MPT-HLS..................................... 68

2 Product information and planning ......................................................................... 81


Figure 2.1 Multiservice Aggregation Layer ............................................................................ 86
Figure 2.2 Service Awareness ........................................................................................... 87
Figure 2.3 Packet node matrix .......................................................................................... 88
Figure 2.4 Service-driven Packet Adaptive Modulation ............................................................. 88
Figure 2.5 9500 MPR-E Main Components ............................................................................. 89
Figure 2.6 MSS-8 shelf .................................................................................................... 91
Figure 2.7 MSS-4 shelf .................................................................................................... 91
Figure 2.8 MSS-1........................................................................................................... 91
Figure 2.9 MSS-1 unit ..................................................................................................... 91
Figure 2.10 MSS-O ......................................................................................................... 92
Figure 2.11 MSS-8 block diagram ....................................................................................... 96
Figure 2.12 MSS-4 block diagram ....................................................................................... 96
Figure 2.13 MSS-1 block diagram ....................................................................................... 97
Figure 2.14 MSS-O block diagram ....................................................................................... 97
Figure 2.15 Stacking configuration with 3 MSS ....................................................................... 98
Figure 2.16 Stacking configuration with 3 MSS with Core protection ............................................. 99
Figure 2.17 ODU300......................................................................................................100
Figure 2.18 MPT-HC ......................................................................................................101
Figure 2.19 MPT-MC......................................................................................................104
Figure 2.20 MPT-HLS system............................................................................................105
Figure 2.21 MSS to ODU300 interconnection .........................................................................106
Figure 2.22 MPTACC to MPT-HC/HC-HQAM interconnection ......................................................108
Figure 2.23 MPTACC to MPT-HC/HC-HQAM interconnection (2 cables) .........................................110
Figure 2.24 Core-E to MPT-HC/HC-HQAM interconnection (2 cables) ...........................................111
Figure 2.25 Core-E connection to the MPT-HC/HC-HQAM through the Power Injector Box ..................113
Figure 2.26 Core-E connection to the MPT-HC/HC-HQAM through the Power Injector card ................114
Figure 2.27 EAS to MPT-HC/HC-HQAM interconnection ............................................................115
Figure 2.28 EASv2 to MPT-HC/HC-HQAM interconnection .........................................................116
Figure 2.29 EASv2 to MPT-HC/HC-HQAM interconnection (2 cables).............................................117
Figure 2.30 MPT-HC/HC-HQAM directly connected to the battery ...............................................119
Figure 2.31 MPT Access to MPT-XP/XP-HQAM interconnection (with MPT Extended Power Unit) ..........120
Figure 2.32 MPT Access to MPT-XP/XP-HQAM interconnection with optical Ethernet cable
(MPT Extended Power Unit) ...............................................................................122
Figure 2.33 Core-E to MPT-XP/XP-HQAM interconnection with optical Ethernet cable (MPT
Extended Power Unit) .....................................................................................123
Figure 2.34 Core-E to MPT-XP/XP-HQAM interconnection with electrical Ethernet cable (MPT
Extended Power Unit) ......................................................................................125
Figure 2.35 EAS to MPT-XP/XP-HQAM interconnections (with MPT Extended Power Unit) ..................126
Figure 2.36 EASv2 to MPT-XP/XP-HQAM interconnection with electrical Ethernet cable (MPT
Extended Power Unit) ......................................................................................128

User Manual 3DB19901AFAA Edition 01

21

Figure 2.37 MPTACC to MPT-MC interconnection ...................................................................129


Figure 2.38 Core-E to MPT-MC connection through the Power Injector Box ....................................130
Figure 2.39 Core-E to MPT-MC connection through the Power Injector card ...................................131
Figure 2.40 EASv2 to MPT-MC interconnection .....................................................................132
Figure 2.41 PDH/ATM Over Ethernet Packet Node - Mapping of 32 E1 and 16 E1 ATM on
Ethernet ......................................................................................................153
Figure 2.42 PDH/SDH/ATM and Ethernet Terminal Packet Transport 32 E1, 2xSTM-1 and 16 E1
ATM Access, 1 Radio Direction ............................................................................154
Figure 2.43 PDH/SDH/ATM and Ethernet Add/Drop Packed Node-Ethernet and 32 E1, 2xSTM-1
and 16 E1 ATM Local Access, 1 Back Link, 1 Haul Link ................................................154
Figure 2.44 PDH/SDH/ATM and Ethernet Terminal Packet Node-Ethernet and 32 E1, 2xSTM-1
and 16 E1 ATM Local Access, 2 Back Links ..............................................................155
Figure 2.45 PDH/SDH/ATM and Ethernet Add/Drop Packet Node-Ethernet and 32 E1, 2xSTM-1
and 16 E1 ATM Local Access, 1 Back Link and 2 Haul Links...........................................156
Figure 2.46 PDH/SDH/ATM and Ethernet Add/Drop Packet Node-Ethernet and 32 E1, 2xSTM-1
and 16 E1 ATM Local Access, 2 Haul Links and 2 Back Links..........................................156
Figure 2.47 ...............................................................................................................199
Figure 2.48 OMT-C .......................................................................................................202
Figure 2.49 OMT-C .......................................................................................................203
Figure 2.50 Power Distribution Architecture for MSS-8 ............................................................207
Figure 2.51 +24 Vdc/-48 Vdc Converter unit.........................................................................208
Figure 2.52 +24 Vdc/-48 Vdc Converter unit.........................................................................209
Figure 2.53 Core-E unit..................................................................................................210
Figure 2.54 Core-E unit..................................................................................................213
Figure 2.55 32xE1 Local Access unit ..................................................................................214
Figure 2.56 PDH Access unit ............................................................................................214
Figure 2.57 2xSTM-1 Local Access unit................................................................................216
Figure 2.58 STM-1 Access unit..........................................................................................217
Figure 2.59 ASAP simplified block diagram ..........................................................................220
Figure 2.60 ASAP unit....................................................................................................221
Figure 2.61 Modem unit .................................................................................................221
Figure 2.62 Modem unit .................................................................................................223
Figure 2.63 MPT Access unit (with PFoE) block diagram ...........................................................224
Figure 2.64 MPTACC card (MSS/MPTACC).............................................................................226
Figure 2.65 EAS unit block diagram ..................................................................................228
Figure 2.66 EAS unit .....................................................................................................229
Figure 2.67 EASv2 unit ..................................................................................................232
Figure 2.68 Power Injector card .......................................................................................233
Figure 2.69 Power Injector box ........................................................................................233
Figure 2.70 Power Injector front panel ...............................................................................234
Figure 2.71 ODU300 housing............................................................................................235
Figure 2.72 ODU block diagram ........................................................................................236
Figure 2.73 MPT-HC/XP housing (embedded diplexer) .............................................................241
Figure 2.74 Correct protected mounting of 6 GHz MPT-xC with internal and external diplexers ...........242
Figure 2.75 Incorrect protected mounting of 6 GHz MPT-xC with internal and external
diplexers ......................................................................................................243
Figure 2.76 View of MPT-HC-HQAM with external diplexer (13-38 GHz) ........................................244
Figure 2.77 MPT system .................................................................................................245
Figure 2.78 MPT-HC/XP housing (internal diplexer) ................................................................245

22

User Manual 3DB19901AFAA Edition 01

Figure 2.79 MPT-HC/XP housing (external diplexer)................................................................246


Figure 2.80 MPT-XP housing (external diplexer) ....................................................................246
Figure 2.81 MPT-MC housing (internal diplexer) ....................................................................249
Figure 2.82 MPT-MC housing (external diplexer) ....................................................................249
Figure 2.83 MPT-HLS .....................................................................................................251
Figure 2.84 MPT-HC/MC/HC-HQAM/XP/XP-HQAM protection schemes ..........................................256
Figure 2.85 Normal Operation (No-fault).............................................................................264
Figure 2.86 Single link failure ..........................................................................................265
Figure 2.87 Multiple ERPS instances (Normal No-fault Operation) ...............................................266
Figure 2.88 Multiple ERPS instances (Single Link Failure) .........................................................267
Figure 2.89 Single 2+0 XPIC.............................................................................................272
Figure 2.90 Double 1+1 HSB co-channel XPIC ........................................................................273
Figure 2.91 Available loopbacks .......................................................................................274
Figure 2.92 Available loopbacks .......................................................................................276
Figure 2.93 Loopback with MPT-HC/HC-HQAM, MPT-XP/XP-HQAM, and MPT-MC ..............................278
Figure 2.94 Example of traffic 28MHz bandwidth and admission control .......................................290
Figure 2.95 Example of traffic in case of 28MHz bandwidth and modulation downgraded to
16QAM.........................................................................................................291
Figure 2.96 Example of traffic in case of 28MHz bandwidth and modulation downgraded to
QPSK...........................................................................................................291
Figure 2.97 Example of traffic in case of 28MHz bandwidth and Admission Control Disabled ...............293
Figure 2.98 Example of traffic in case of 28MHz bandwidth and modulation downgraded to
16QAM.........................................................................................................293
Figure 2.99 Example of traffic in case of 28MHz bandwidth and modulation downgraded to
QPSK...........................................................................................................294
Figure 2.100 Traffic profiles............................................................................................297
Figure 2.101 Traffic profiles............................................................................................299
Figure 2.102 Traffic profiles............................................................................................300
Figure 2.103 E1 Traffic ..................................................................................................301
Figure 2.104 E1 Traffic ..................................................................................................302
Figure 2.105 STM-1 Traffic..............................................................................................303
Figure 2.106 E1 Traffic ..................................................................................................304
Figure 2.107 ATM Traffic Management - General block diagram .................................................305
Figure 2.108 Block diagram for ATM Ingress (ATM Packet) direction .........................................306
Figure 2.109 ATM Traffic Management on Modem card - Block diagram ........................................309
Figure 2.110 Radio LAG overview......................................................................................323
Figure 2.111 Radio LAG .................................................................................................324
Figure 2.112 Ethernet LAG..............................................................................................325
Figure 2.113 Types of L1 LAG ..........................................................................................329
Figure 2.114 Intra Plug-in L1 Link Aggregation Scenario ...........................................................330
Figure 2.115 Single card 1+0 Intra Plug-in L1 LAG Configurations................................................330
Figure 2.116 Dual card 1+0 Intra Plug-in L1 LAG Configurations..................................................331
Figure 2.117 Cross Plug-in L1 Link Aggregation Scenario ..........................................................331
Figure 2.118 1+0 Cross Plug-in L1 LAG Configurations .............................................................332
Figure 2.119 QoS configuration ........................................................................................343
Figure 2.120 Cross-connection .........................................................................................347
Figure 2.121 Synchronization distribution from MPR to AWY .....................................................374
Figure 2.122 Synchronization connection in Stacking configuration with Core protection ...................376

User Manual 3DB19901AFAA Edition 01

23

3 NE Management by software application............................................................... 377


Figure 3.1 WebEML desktop icon ......................................................................................377
Figure 3.2 NEtO Servers Manager window ............................................................................378
Figure 3.3 NEtO window ................................................................................................378
Figure 3.4 NEtO supervision established with NE ...................................................................379
Figure 3.5 Acknowledgment of Authorization window .............................................................379
Figure 3.6 MSS-8 Main view ............................................................................................381
Figure 3.7 MSS-4 Main view ............................................................................................382
Figure 3.8 MSS-1 Main view .............................................................................................383
Figure 3.9 MSS-O Main view ............................................................................................384
Figure 3.10 Check mark .................................................................................................385
Figure 3.11 Switch symbol ..............................................................................................385
Figure 3.12 Cross connections..........................................................................................386
Figure 3.13 Left arrow to previous screen icon .....................................................................386
Figure 3.14 Second button..............................................................................................386
Figure 3.15 Right arrow to next screen icon .........................................................................386
Figure 3.16 Block Diagram View icon .................................................................................386
Figure 3.17 NE Inventory icon ..........................................................................................386
Figure 3.18 Cross-Connections icon ...................................................................................387
Figure 3.19 Segregated ports icon .....................................................................................387
Figure 3.20 Ethernet Ring icon.........................................................................................387
Figure 3.21 LAG Configuration icon ...................................................................................387
Figure 3.22 QoS Configuration icon ...................................................................................387
Figure 3.23 ETH OAM Configuration icon .............................................................................387
Figure 3.24 AUX Cross Connections icon..............................................................................387
Figure 3.25 XPIC Configuration icon...................................................................................388
Figure 3.26 VLAN management icon ..................................................................................388
Figure 3.27 WT Performance Monitoring Suite icon ................................................................388
Figure 3.28 WebEML has the OS permission to manage the NE icon .............................................390
Figure 3.29 WebEML does not have the OS permission to manage the NE icon ................................390
Figure 3.30 Enable operational state of the connection between NE and WebEML icon..................390
Figure 3.31 Disable operational state of the connection between NE and WebEML icon ..................391
Figure 3.32 NE is under supervision icon .............................................................................391
Figure 3.33 NE is not under supervision icon ........................................................................391
Figure 3.34 User State unblocked icon ...............................................................................391
Figure 3.35 User State blocked icon ..................................................................................391
Figure 3.36 Protocol disabled .........................................................................................391
Figure 3.37 Protocol enabled, but neither server is reachable ...................................................392
Figure 3.38 Protocol enabled and at least one of the two servers is reachable ...............................392
Figure 3.39 Protocol enabled...........................................................................................392
Figure 3.40 Normal operating condition ..............................................................................392
Figure 3.41 Detection of an ABNORMAL operative condition......................................................392
Figure 3.42 Configuration menu .......................................................................................395
Figure 3.43 NE Time configuration menu.............................................................................396
Figure 3.44 Local Configuration menu ................................................................................397
Figure 3.45 NTP Configuration menu..................................................................................398
Figure 3.46 IP Static Routing Configuration menu ..................................................................399
Figure 3.47 OSPF area configuration with OSPFv2 ..................................................................401
Figure 3.48 OSPF area configuration with OSPFv3 ..................................................................401

24

User Manual 3DB19901AFAA Edition 01

Figure 3.49 New OSPF Area Configuration menu ....................................................................402


Figure 3.50 IPv6 stack warning.........................................................................................404
Figure 3.51 Routing Information screen ..............................................................................405
Figure 3.52 Alarm Severities Profile ..................................................................................406
Figure 3.53 Select object to associate an alarm profile ...........................................................407
Figure 3.54 Associate an alarm profile ...............................................................................408
Figure 3.55 System Settings menu.....................................................................................409
Figure 3.56 P8ETH module..............................................................................................414
Figure 3.57 Main Cross-Connections View ............................................................................415
Figure 3.58 LAG cross-connection .....................................................................................416
Figure 3.59 Ring cross-connection.....................................................................................417
Figure 3.60 Cross-connections Example ..............................................................................419
Figure 3.61 Creating cross-connection between PDH and radio ..................................................420
Figure 3.62 Cross-connections buttons ...............................................................................420
Figure 3.63 Segregated Port View (default configuration) ........................................................421
Figure 3.64 Port selection window ....................................................................................422
Figure 3.65 To segregate ports.........................................................................................422
Figure 3.66 Segregated Ports ..........................................................................................423
Figure 3.67 Actual colored view example ............................................................................425
Figure 3.68 PDH to Radio configuration dialog ......................................................................428
Figure 3.69 Completed PDH to Radio cross-connection ............................................................429
Figure 3.70 Radio to Radio configuration dialog ....................................................................430
Figure 3.71 Completed Radio to Radio cross-connection ..........................................................431
Figure 3.72 Radio to Ethernet configuration dialog (ranges)......................................................432
Figure 3.73 Radio/MPT-ACC to Ethernet configuration dialog (values)..........................................433
Figure 3.74 Completed Radio to Ethernet cross-connection ......................................................434
Figure 3.75 PDH to Ethernet configuration dialog ..................................................................435
Figure 3.76 Completed PDH to Ethernet cross-connection ........................................................436
Figure 3.77 No protection...............................................................................................436
Figure 3.78 1+1 radio protection between NE B and C .............................................................437
Figure 3.79 1+1 EPS protection in NE A ...............................................................................437
Figure 3.80 PDH to Radio cross-connection modification ..........................................................438
Figure 3.81 Modifying a Radio to Radio cross-connection..........................................................439
Figure 3.82 Modifying a Radio to Ethernet cross-connection......................................................440
Figure 3.83 Modifying a PDH to Ethernet cross-connection .......................................................441
Figure 3.84 SDH to Radio configuration dialog ......................................................................442
Figure 3.85 Completed SDH to Radio cross-connection ............................................................443
Figure 3.86 Radio to Radio configuration dialog ....................................................................444
Figure 3.87 Completed Radio to Radio cross-connection ..........................................................445
Figure 3.88 SDH to Ring configuration dialog ........................................................................446
Figure 3.89 Completed SDH to Ring cross-connection..............................................................447
Figure 3.90 SDH to LAG configuration dialog ........................................................................448
Figure 3.91 Completed SDH to LAG cross-connection ..............................................................449
Figure 3.92 SDH to Radio cross-connection modification ..........................................................450
Figure 3.93 Modifying a Radio to Radio cross-connection..........................................................451
Figure 3.94 SDH to Radio configuration dialog ......................................................................452
Figure 3.95 Completed SDH to Radio cross-connection ............................................................453
Figure 3.96 PDH to SDH configuration dialog ........................................................................454
Figure 3.97 Completed PDH to SDH cross-connection ..............................................................455

User Manual 3DB19901AFAA Edition 01

25

Figure 3.98 SDH to Radio cross-connection modification ..........................................................456


Figure 3.99 Modifying a PDH to SDH cross-connection .............................................................457
Figure 3.100 ASAP-Radio configuration dialog (ODU300) ..........................................................458
Figure 3.101 ASAP-Radio configuration dialog (MPT-HC/HC-HQAM/MC/XP/XP-HQAM) .......................459
Figure 3.102 Completed ASAP-radio cross-connection .............................................................460
Figure 3.103 Radio-radio configuration dialog.......................................................................461
Figure 3.104 Traffic Descriptor ........................................................................................461
Figure 3.105 Completed radio-radio cross-connection .............................................................462
Figure 3.106 Radio-Ethernet configuration dialog ..................................................................463
Figure 3.107 Completed Radio-Ethernet cross-connection ........................................................464
Figure 3.108 ASAP-Ethernet configuration dialog ...................................................................465
Figure 3.109 Completed ASAP-Ethernet cross-connection .........................................................466
Figure 3.110 ASAP-radio cross-connection modification ...........................................................467
Figure 3.111 Modifying a Radio-Radio cross-connection ...........................................................467
Figure 3.112 Modifying a Radio-Ethernet cross-connection .......................................................468
Figure 3.113 Modifying an ASAP-Ethernet cross-connection.......................................................468
Figure 3.114 Ethernet LAG - Radio LAG configuration dialog .....................................................469
Figure 3.115 Completed Ethernet LAG - Radio LAG cross-connection ...........................................470
Figure 3.116 Radio LAG - Radio LAG configuration dialog .........................................................471
Figure 3.117 Completed Radio LAG - Radio LAG cross-connection ...............................................472
Figure 3.118 Ethernet LAG - Radio LAG cross-connection modification .........................................473
Figure 3.119 Modifying a Radio - Radio cross-connection..........................................................474
Figure 3.120 PDH - Ring configuration dialog ........................................................................475
Figure 3.121 Completed PDH - Ring cross-connection..............................................................476
Figure 3.122 Radio - Ring configuration dialog ......................................................................477
Figure 3.123 Radio - Ring cross-connections .........................................................................478
Figure 3.124 Completed Radio - Ring cross-connection ............................................................479
Figure 3.125 Ethernet - Ring configuration dialog .................................................................480
Figure 3.126 Ethernet - Ring cross-connections .....................................................................481
Figure 3.127 Completed Ethernet - Ring cross-connection ........................................................482
Figure 3.128 Pass-through configuration dialog .....................................................................483
Figure 3.129 Pass-through cross-connections ........................................................................484
Figure 3.130 Completed Pass-through cross-connection ...........................................................485
Figure 3.131 PDH - Radio cross-connection modification (no Ethernet port in Ring)..........................486
Figure 3.132 Modifying a Radio - Ring cross-connection ...........................................................487
Figure 3.133 Modifying an Ethernet - Ring cross-connection ......................................................488
Figure 3.134 Modifying a Pass-through cross-connection ..........................................................489
Figure 3.135 Sample mixed fiber/microwave ring ..................................................................490
Figure 3.136 Example 1: Neither traffic end point belongs to the fiber chain .................................491
Figure 3.137 Example 1: Pass-through configuration on Node A..................................................491
Figure 3.138 Example 1: Pass-through configuration on Node B..................................................492
Figure 3.139 Example 1: Pass-through configuration on Node C..................................................493
Figure 3.140 Example 1: Pass-through configuration on Node D..................................................494
Figure 3.141 Example 2: One traffic end point belongs to the fiber chain .....................................495
Figure 3.142 Example 2: Pass-through configuration on Node A..................................................495
Figure 3.143 Example 2: Pass-through configuration on Node B..................................................496
Figure 3.144 Example 2: Pass-through configuration on Node C..................................................497
Figure 3.145 Example 2: Radio-Ring configuration on Node D ....................................................498
Figure 3.146 Example 2: PDH-Ring configuration on Node D ......................................................498

26

User Manual 3DB19901AFAA Edition 01

Figure 3.147 Example 2.1: Cross-connection between Node J and Node D, where the end
point on Node D is protected ..............................................................................499
Figure 3.148 Example 2.1: Pass-through configuration on Node A ...............................................500
Figure 3.149 Example 2.1: Pass-through configuration on Node B ...............................................501
Figure 3.150 Example 2.1: Pass-through configuration on Node C ...............................................502
Figure 3.151 Example 2.1: Radio-Ring configuration on Node D..................................................503
Figure 3.152 Example 2.1: PDH-Ring configuration on Node D....................................................503
Figure 3.153 Example 3: One traffic end point belongs to the fiber chain .....................................504
Figure 3.154 Example 3: Radio-Ring configuration on Node B ....................................................505
Figure 3.155 Example 3: PDH-Ring configuration on Node B ......................................................505
Figure 3.156 Example 3: Pass-through configuration on Node A..................................................506
Figure 3.157 Example 3: Pass-through configuration on Node C..................................................507
Figure 3.158 Example 3: Pass-through configuration on Node D..................................................508
Figure 3.159 Example 3.1: Cross-connection between Node K and Node B, where the end
point on Node B is protected ..............................................................................509
Figure 3.160 Example 3.1: Radio-Ring configuration on Node B ..................................................510
Figure 3.161 Example 3.1: PDH-Ring configuration on Node B....................................................510
Figure 3.162 Example 3.1: Pass-through configuration on Node A ...............................................511
Figure 3.163 Example 3.1: Pass-through configuration on Node C ...............................................512
Figure 3.164 Example 3.1: Pass-through configuration on Node D ...............................................513
Figure 3.165 Example 4: cross-connection between Node I and NE G ...........................................514
Figure 3.166 Example 4: Ethernet-Radio configuration on NE G..................................................515
Figure 3.167 Example 4: Ethernet-PDH configuration on NE G ...................................................516
Figure 3.168 Example 4: Ethernet-Ring configuration on Node C ................................................517
Figure 3.169 Example 4: Pass-through configuration on Node A..................................................518
Figure 3.170 Example 4: Pass-through configuration on Node B..................................................519
Figure 3.171 Example 4: Pass-through configuration on Node D..................................................520
Figure 3.172 Example 4.1: Cross-connection between Node I and NE G, where the end point
on NE G is protected........................................................................................521
Figure 3.173 Example 4.1: Ethernet-Radio configuration on NE G ...............................................522
Figure 3.174 Example 4.1: Ethernet-PDH configuration on NE G .................................................523
Figure 3.175 Example 4.1: Ethernet-Ring configuration on Node C ..............................................524
Figure 3.176 Example 4.1: Pass-through configuration on Node A ...............................................525
Figure 3.177 Example 4.1: Pass-through configuration on Node B ...............................................526
Figure 3.178 Example 4.1: Pass-through configuration on Node D ...............................................527
Figure 3.179 Example 5: Cross-connection between Node I and NE E ...........................................528
Figure 3.180 Example 5: Ethernet-Radio configuration on NE E ..................................................529
Figure 3.181 Example 5: Ethernet-PDH configuration on NE E....................................................530
Figure 3.182 Example 5: Ethernet-Ring configuration on Node A ................................................531
Figure 3.183 Example 5: Pass-through configuration on Node B..................................................532
Figure 3.184 Example 5: Pass-through configuration on Node C..................................................533
Figure 3.185 Example 5: Pass-through configuration on Node D..................................................534
Figure 3.186 Example 5.1: Cross-connection between Node I and NE E, where the end point
on NE E is protected ........................................................................................535
Figure 3.187 Example 5.1: Ethernet-Radio configuration on NE E................................................536
Figure 3.188 Example 5.1: Ethernet-PDH configuration on NE E .................................................537
Figure 3.189 Example 5.1: Ethernet-Ring configuration on Node A ..............................................538
Figure 3.190 Example 5.1: Pass-through configuration on Node B ...............................................539
Figure 3.191 Example 5.1: Pass-through configuration on Node C ...............................................540

User Manual 3DB19901AFAA Edition 01

27

Figure 3.192 Example 5.1: Pass-through configuration on Node D ...............................................541


Figure 3.193 Example 6: Cross-connection between Node A and Node D .......................................542
Figure 3.194 Example 6: Radio-Ring configuration on Node A ....................................................543
Figure 3.195 Example 6: PDH-Ring configuration on Node A ......................................................543
Figure 3.196 Example 6: Pass-through configuration on Node B..................................................544
Figure 3.197 Example 6: Pass-through configuration on Node C..................................................545
Figure 3.198 Example 6: Radio-Ring configuration on Node D ....................................................546
Figure 3.199 Example 6: PDH-Ring configuration on Node D ......................................................546
Figure 3.200 Example 6.1: cross-connection between Node A and Node D, where the end
point on Node D is protected ..............................................................................547
Figure 3.201 Example 6.1: Radio-Ring configuration on Node A ..................................................548
Figure 3.202 Example 6.1: PDH-Ring configuration on Node A....................................................548
Figure 3.203 Example 6.1: Pass-through configuration on Node B ...............................................549
Figure 3.204 Example 6.1: Pass-through configuration on Node C ...............................................550
Figure 3.205 Example 6.1: Radio-Ring configuration on Node D..................................................551
Figure 3.206 Example 6.1: PDH-Ring configuration on Node D....................................................551
Figure 3.207 Example 6.2: cross-connection between Node A and Node D where the end
points on both Node D and Node A are protected......................................................552
Figure 3.208 Example 6.2: Radio-Ring configuration on Node A ..................................................553
Figure 3.209 Example 6.2: PDH-Ring configuration on Node A....................................................553
Figure 3.210 Example 6.2: Pass-through configuration on Node B ...............................................554
Figure 3.211 Example 6.2: Pass-through configuration on Node C ...............................................555
Figure 3.212 Example 6.2: Radio-Ring configuration on Node D..................................................556
Figure 3.213 Example 6.2: PDH-Ring configuration on Node D....................................................556
Figure 3.214 Example 7: Cross-connection between Node A and Node C .......................................557
Figure 3.215 Example 7: Radio-Ring configuration on Node A ....................................................558
Figure 3.216 Example 7: PDH-Ring configuration on Node A ......................................................558
Figure 3.217 Example 7: Pass-through configuration on Node B..................................................559
Figure 3.218 Example 7: Radio-Ring configuration on Node C ....................................................560
Figure 3.219 Example 7: PDH-Ring configuration on Node C ......................................................560
Figure 3.220 Example 7: Pass-through configuration on Node D..................................................561
Figure 3.221 Example 7.1: Cross-connection between Node A and Node C where the end
point on Node C is protected ..............................................................................562
Figure 3.222 Example 7.1: Radio-Ring configuration on Node A ..................................................562
Figure 3.223 Example 7.1: PDH-Ring configuration on Node A....................................................563
Figure 3.224 Example 7.1: Pass-through configuration on Node B ...............................................564
Figure 3.225 Example 7.1: Radio-Ring configuration on Node C ..................................................565
Figure 3.226 Example 7.1: PDH-Ring configuration on Node C....................................................565
Figure 3.227 Example 7.1: Pass-through configuration on Node D ...............................................566
Figure 3.228 Example 8: Cross-connection between Node B and Node C .......................................567
Figure 3.229 Example 8: Radio-Ring configuration on Node B ....................................................568
Figure 3.230 Example 8: PDH-Ring configuration on Node B ......................................................568
Figure 3.231 Example 8: Radio-Ring configuration on Node C ....................................................569
Figure 3.232 Example 8: PDH-Ring configuration on Node C ......................................................570
Figure 3.233 Example 8: Pass-through configuration on Node A..................................................571
Figure 3.234 Example 8: Pass-through configuration on Node D..................................................572
Figure 3.235 Example 9: Cross-connection between NE E and Node D ..........................................573
Figure 3.236 Example 9: Ethernet-Radio configuration on NE E ..................................................574
Figure 3.237 Example 9: Ethernet-PDH configuration on NE E....................................................575

28

User Manual 3DB19901AFAA Edition 01

Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure

3.238 Example 9: Ethernet-Ring configuration on Node A ................................................576


3.239 Example 9: Pass-through configuration on Node B..................................................577
3.240 Example 9: Pass-through configuration on Node C..................................................578
3.241 Example 9: Radio-Ring configuration on Node D ....................................................579
3.242 Example 9: PDH-Ring configuration on Node D ......................................................579
3.243 Example 10: Cross-connection between NE E and Node C .........................................580
3.244 Example 10: Ethernet-Radio configuration on NE E.................................................581
3.245 Example 10: Ethernet-PDH configuration on NE E ..................................................582
3.246 Example 10: Ethernet-Ring configuration on Node A ...............................................583
3.247 Example 10: Pass-through configuration on Node B ................................................584
3.248 Example 10: Radio-Ring configuration on Node C ...................................................585
3.249 Example 10: PDH-Ring configuration on Node C.....................................................585
3.250 Example 10: Pass-through configuration on Node D ................................................586
3.251 Example 11: Cross-connection between Node F and Node C ......................................587
3.252 Example 11: Ethernet-Radio configuration on NE F.................................................588
3.253 Example 11: Ethernet-PDH configuration on NE F ..................................................589
3.254 Example 11: Ethernet-Ring configuration on Node B ...............................................590
3.255 Example 11: Radio-Ring configuration on Node C ...................................................591
3.256 Example 11: PDH-Ring configuration on Node C.....................................................591
3.257 Example 11: Pass-through configuration on Node A ................................................592
3.258 Example 11: Pass-through configuration on Node D ................................................593
3.259 Example 11.1: Cross-connection between NE F and Node C, where the end point
at Node C is protected .....................................................................................594
Figure 3.260 Example 11.1: Ethernet-Radio configuration on NE F ..............................................595
Figure 3.261 Example 11.1: Ethernet-PDH configuration on NE F ................................................596
Figure 3.262 Example 11.1: Ethernet-Ring configuration on Node B.............................................597
Figure 3.263 Example 11.1: Radio-Ring configuration on Node C ................................................598
Figure 3.264 Example 11.1: PDH-Ring configuration on Node C ..................................................598
Figure 3.265 Example 11.1: Pass-through configuration on Node A..............................................599
Figure 3.266 Example 11.1: Pass-through configuration on Node D..............................................600
Figure 3.267 Example 11.2: Cross-connection between Node F and Node C, where the both
end
points at Node F and Node C are protected.............................................................601
Figure 3.268 Example 11.2: Ethernet-Radio configuration on NE F ..............................................602
Figure 3.269 Example 11.2: Ethernet-PDH configuration on NE F ................................................603
Figure 3.270 Example 11.2: Ethernet-Ring configuration on Node B.............................................604
Figure 3.271 Example 11.2: Radio-Ring configuration on Node C ................................................605
Figure 3.272 Example 11.2: PDH-Ring configuration on Node C ..................................................605
Figure 3.273 Example 11.2: Pass-through configuration on Node A..............................................606
Figure 3.274 Example 11.2: Pass-through configuration on Node D..............................................607
Figure 3.275 Example 12: Cross-connection between NE E and NE H............................................608
Figure 3.276 Example 12: Ethernet-Radio configuration on NE E.................................................609
Figure 3.277 Example 12: Ethernet-PDH configuration on NE E ..................................................610
Figure 3.278 Example 12: Ethernet-Radio configuration on NE H ...............................................611
Figure 3.279 Example 12: Ethernet-PDH configuration on NE H ..................................................612
Figure 3.280 Example 12: Ethernet-Ring configuration on Node A ...............................................613
Figure 3.281 Example 12: Pass-through configuration on Node B ................................................614
Figure 3.282 Example 12: Pass-through configuration on Node C ................................................615
Figure 3.283 Example 12: Ethernet-Ring configuration on Node D ...............................................616

User Manual 3DB19901AFAA Edition 01

29

Figure 3.284
Figure 3.285
Figure 3.286
Figure 3.287
Figure 3.288
Figure 3.289
Figure 3.290
Figure 3.291
Figure 3.292
Figure 3.293
Figure 3.294
Figure 3.295
Figure 3.296
Figure 3.297
Figure 3.298
Figure 3.299
Figure 3.300
Figure 3.301
Figure 3.302
Figure 3.303
Figure 3.304
Figure 3.305
Figure 3.306
Figure 3.307
Figure 3.308
Figure 3.309
Figure 3.310
Figure 3.311
Figure 3.312
Figure 3.313
Figure 3.314
Figure 3.315
Figure 3.316
Figure 3.317
Figure 3.318
Figure 3.319
Figure 3.320
Figure 3.321
Figure 3.322
Figure 3.323
Figure 3.324
Figure 3.325
Figure 3.326
Figure 3.327
Figure 3.328
Figure 3.329
Figure 3.330
Figure 3.331
Figure 3.332

30

Example 13: Cross-connection between NE E and NE G............................................617


Example 13: Ethernet-Radio configuration on NE E.................................................618
Example 13: Ethernet-PDH configuration on NE E ..................................................619
Example 13: Ethernet-Radio configuration on NE G ................................................620
Example 13: Ethernet-PDH configuration on NE G ..................................................621
Example 13: Ethernet-Ring configuration on Node A ...............................................622
Example 13: Pass-through configuration on Node B ................................................623
Example 13: Ethernet-Ring configuration on Node C ...............................................624
Example 13: Pass-through configuration on Node D ................................................625
Example 14: Cross-connection between NE F and NE G............................................626
Example 14: Ethernet-Radio configuration on NE F.................................................627
Example 14: Ethernet-PDH configuration on NE F ..................................................628
Example 14: Ethernet-Radio configuration on NE G ................................................629
Example 14: Ethernet-PDH configuration on NE G ..................................................630
Example 14: Ethernet-Ring configuration on Node B ...............................................631
Example 14: Ethernet-Ring configuration on Node C ...............................................632
Example 14: Pass-through configuration on Node A ................................................633
Example 14: Pass-through configuration on Node D ................................................634
Rings Fiber Chain Description .........................................................................636
Rings Fiber Chain for Aided Cross-connections window ...........................................637
Add&Drop cross-connection: Other end point is outside the fiber chain........................638
Add&Drop cross-connection: Other end point is inside the fiber chain .........................639
Pass-through cross-connection: Both end points are inside the fiber chain (1) ................640
Pass-through cross-connection: Both end points are inside the fiber chain (2) ................641
Pass-through cross-connection: One end point is inside the fiber chain (1) ....................642
Pass-through cross-connection: One end point is inside the fiber chain (2) ....................643
Pass-through cross-connection: Both end points are outside the fiber chain...................644
L2 Radio LAG configuration.............................................................................646
L2 Radio LAG creation ...................................................................................647
L2 Radio LAG configuration.............................................................................648
MPT tooltip ................................................................................................649
L1 Radio LAG configuration.............................................................................650
L1 Radio LAG creation ...................................................................................651
L1 Radio LAG configuration.............................................................................652
Lowest index port .......................................................................................654
MPT tooltip ................................................................................................654
SDH LAG screen...........................................................................................656
L2 Ethernet LAG creation ...............................................................................662
L2 Ethernet LAG configuration - Settings tab........................................................663
L2 Ethernet LAG configuration .........................................................................665
Ethernet port tooltip ....................................................................................665
Partner state tooltip.....................................................................................666
Advanced column ........................................................................................666
L2 Ethernet LAG configuration - Provider Bridge tab...............................................667
Scheduler Configuration.................................................................................668
Queue Size Configuration ...............................................................................669
Queue Size Configuration ...............................................................................670
Queue Size Configuration ...............................................................................671
Warning message .........................................................................................672

User Manual 3DB19901AFAA Edition 01

Figure 3.333 QoS Classification ........................................................................................672


Figure 3.334 Warning message .........................................................................................673
Figure 3.335 IEEE 802.1p................................................................................................673
Figure 3.336 Warning message .........................................................................................674
Figure 3.337 IEEE 802.1p classification change......................................................................674
Figure 3.338 DiffServ ....................................................................................................675
Figure 3.339 Warning message .........................................................................................675
Figure 3.340 DiffServ classification change ..........................................................................676
Figure 3.341 Read-only table...........................................................................................677
Figure 3.342 ETH OAM window.........................................................................................680
Figure 3.343 Operational EFM OAM link ..............................................................................682
Figure 3.344 Remote OAM loopback...................................................................................683
Figure 3.345 Auxiliary Cross Connections menu .....................................................................685
Figure 3.346 New AUX Cross Connection .............................................................................686
Figure 3.347 Delete an AUX Cross Connection.......................................................................687
Figure 3.348 Traffic Description View ................................................................................688
Figure 3.349 Login window .............................................................................................690
Figure 3.350 Login Failed ...............................................................................................691
Figure 3.351 Profiles Management ....................................................................................692
Figure 3.352 Create User ...............................................................................................693
Figure 3.353 Delete user confirmation ...............................................................................695
Figure 3.354 Confirm Administrator Password to Delete a User ..................................................695
Figure 3.355 Change Password of User by Admin ...................................................................696
Figure 3.356 USM Users Management .................................................................................697
Figure 3.357 USM Create User..........................................................................................698
Figure 3.358 USM Delete user confirmation..........................................................................700
Figure 3.359 USM Change Password of User by Admin .............................................................701
Figure 3.360 Change User Password (SNMPv2).......................................................................702
Figure 3.361 Change User Password (SNMPv3).......................................................................703
Figure 3.362 List of the available commands with the help tacplus command..............................727
Figure 3.363 Initial Settings: TACACS+ is disabled on all interfaces and there is no server
configured ....................................................................................................728
Figure 3.364 Provisioning server 1 (default settings but IP address) and showing the result ................729
Figure 3.365 Provisioning server 1's key and showing the result..................................................730
Figure 3.366 Performing a test (to check to server reachability and the server response
time), then showing TACACS+ settings and status .....................................................731
Figure 3.367 Provisioning server 2 (specifying secret key) and showing the result............................732
Figure 3.368 Provisioning server 2s port (such that the server will not be reachable) and
showing the result, then performing a test .............................................................733
Figure 3.369 Updating accounting packet size ......................................................................734
Figure 3.370 Enabling TACACS+ Login for all management interfaces and showing settings and
status (remark: server 2 is un-reachable) ...............................................................735
Figure 3.371 Enabling TACACS+ Accounting for all management interfaces and showing
settings and status (remark: server 2 is un-reachable) ...............................................736
Figure 3.372 Disabling TACACS+ Login for all management interfaces and showing settings and
status (remark: server 2 is un-reachable) ...............................................................737
Figure 3.373 Enabling TACACS+ Login for SNMP management interfaces and showing settings
and status (remark: server 2 is un-reachable), then performing a test ............................738
Figure 3.374 Summary block diagram.................................................................................791

User Manual 3DB19901AFAA Edition 01

31

Figure 3.375
Figure 3.376
Figure 3.377
Figure 3.378
Figure 3.379
Figure 3.380
Figure 3.381
Figure 3.382
Figure 3.383
Figure 3.384
Figure 3.385
Figure 3.386
Figure 3.387
Figure 3.388
Figure 3.389
Figure 3.390
Figure 3.391
Figure 3.392
Figure 3.393
Figure 3.394
Figure 3.395
Figure 3.396
Figure 3.397
Figure 3.398
Figure 3.399
Figure 3.400
Figure 3.401
Figure 3.402
Figure 3.403
Figure 3.404
Figure 3.405
Figure 3.406
Figure 3.407
Figure 3.408
Figure 3.409
Figure 3.410
Figure 3.411
Figure 3.412
Figure 3.413
Figure 3.414
Figure 3.415
Figure 3.416
Figure 3.417
Figure 3.418
Figure 3.419
Figure 3.420
Figure 3.421
Figure 3.422
Figure 3.423

32

1+0 block diagram (PDH unit) (without Core-E protection) .......................................794


1+0 block diagram (PDH unit) (with Core-E protection) ...........................................795
1+1 block diagram (PDH units) (without Core-E protection) ......................................796
1+1 block diagram (PDH units) (with Core-E protection) ..........................................797
1+0 block diagram (SDH unit) (without Core protection) ..........................................798
1+0 block diagram (SDH unit) (with Core protection) .............................................799
1+1 block diagram (SDH unit) (without Core protection) ..........................................800
1 1 block diagram (SDH unit) (with Core protection)...............................................801
1+0 block diagram (Radio unit) (without Core-E protection)......................................802
1+0 block diagram (Radio unit) (with Core-E protection)..........................................803
1+1 FD block diagram (Radio units) (without Core-E protection).................................804
1+1 FD block diagram (Radio units) (with Core-E protection).....................................805
1+1 Hot Standby block diagram (Radio units) (without Core-E protection) .....................806
1+1 Hot Standby block diagram (Radio units) (with Core-E protection) .........................807
1+0 block diagram (MPT-ACC unit) (without Core-E protection)..................................808
1+0 block diagram (MPT-ACC unit) (with Core-E protection)......................................809
1+1 FD block diagram (MPT-ACC units) (without Core-E protection) ............................810
1+1 FD block diagram (MPT-ACC units) (with Core-E protection).................................811
1+1 Hot Standby block diagram (MPT-ACC units) (without Core-E protection).................812
1+1 Hot Standby block diagram (MPT-ACC units) (with Core-E protection) .....................813
1+0 block diagram (MPT-ACC unit) (without Core protection) ....................................814
1+0 block diagram (MPT-ACC unit) (with Core protection) ........................................815
1+1 Hot Standby block diagram (MPT-ACC units) (without Core protection) ...................816
1+1 Hot Standby block diagram (MPT-ACC units) (with Core protection) .......................817
1+1 FD block diagram (MPT-ACC units) (without Core protection) ...............................818
1+1 FD block diagram (MPT-ACC units) (with Core protection) ...................................819
1+0 block diagram (MPT-HC/MPT-XP connected to P8ETH) .......................................820
Co-channel XPIC ..........................................................................................821
1+1 XPIC ...................................................................................................822
NE Inventory ..............................................................................................823
Software download confirmation ......................................................................834
Panel 1 (Committed software) .........................................................................835
Panel 2 (Stand by software) ............................................................................836
Summary tab ..............................................................................................841
NE Neighbors tab .........................................................................................842
Equipment View (starting from scratch) with MSS-8................................................843
Core-E unit Ethernet port configuration..............................................................846
MPT Access settings......................................................................................846
SDH unit configuration ..................................................................................847
P8ETH unit configuration ...............................................................................847
Protection Example ......................................................................................849
How to configure the protection ......................................................................850
Protected configuration on MPT-HCs..................................................................851
Protection configuration with STM-1 units ...........................................................851
Protection scheme screen ..............................................................................854
1+1 PDH unit block diagram ............................................................................855
1+1 SDH unit block diagram ............................................................................856
1+1 FD Radio unit block diagram (ODU300) ..........................................................857
1+1 HSB Radio unit block diagram (ODU300).........................................................858

User Manual 3DB19901AFAA Edition 01

Figure 3.424 1+1 FD Radio unit block diagram (MPT-HC/HC-HQAM/XP/XP-HQAM with MPTACC) ..........859
Figure 3.425 1+1 HSB Radio unit block diagram (MPT-HC/HC-HQAM/XP/XP-HQAM with MPTACC)..........860
Figure 3.426 1+1 FD Radio unit block diagram (MPT-HC/HC-HQAM/XP/XP-HQAM with Core-E) .............861
Figure 3.427 1+1 HSB Radio unit block diagram (MPT-HC/HC-HQAM/XP/XP-HQAM with Core-E) ...........862
Figure 3.428 1+1 FD Radio unit block diagram (MPT-MC with MPTACC) .........................................863
Figure 3.429 1+1 HSB Radio unit block diagram (MPT-MC with MPTACC)........................................864
Figure 3.430 1+1 FD Radio unit block diagram (MPT-MC with Core-E) ...........................................865
Figure 3.431 1+1 HSB Radio unit block diagram (MPT-MC with Core-E) .........................................866
Figure 3.432 1+1 HSB Radio unit block diagram (MPT-HLS)........................................................866
Figure 3.433 1+1 SD Radio unit block diagram (MPT-HLS with Rx diversity) ....................................867
Figure 3.434 Protection Scheme Parameters tab ...................................................................870
Figure 3.435 Physical Cable warning example.......................................................................871
Figure 3.436 Synchronization Settings view..........................................................................875
Figure 3.437 SSM Summary Table......................................................................................882
Figure 3.438 Cross-Connections View .................................................................................883
Figure 3.439 Node timing ...............................................................................................889
Figure 3.440 E1 Loopbacks..............................................................................................891
Figure 3.441 STM-1 Loopbacks .........................................................................................896
Figure 3.442 EAS Main view for P8ETH................................................................................903
Figure 3.443 EAS Main view for EASv2 ................................................................................904
Figure 3.444 Settings tab panel for EASv2 port#1 to port#4.......................................................905
Figure 3.445 Settings tab panel for EASv2 port#5 to port#8.......................................................907
Figure 3.446 Provider Bridge tab-panel...............................................................................910
Figure 3.447 Policy & Translation tab-panel .........................................................................911
Figure 3.448 Per-VLAN Per-CoS Rate Limiter tab-panel............................................................915
Figure 3.449 Duplicate Per-VLAN Per-CoS Rate Limiter with the same PCP value.............................916
Figure 3.450 Per-VLAN Per-CoS Rate Limiter and VLAN Rate Limiter with the same VLAN ID ...............916
Figure 3.451 Per-VLAN Per-CoS Rate Limiter with VLAN ID = Any and a VLAN Rate Limiter .................917
Figure 3.452 Ethernet Ring Protection configuration...............................................................938
Figure 3.453 Add VLANs .................................................................................................939
Figure 3.454 OAM switching criteria ..................................................................................939
Figure 3.455 Ethernet Ring example ..................................................................................941
Figure 3.456 Ring example for upgrade ..............................................................................943
Figure 3.457 Activate Tx mute to Node C ............................................................................944
Figure 3.458 Activate software on Node B ...........................................................................945
Figure 3.459 Remove Tx mute to Node C.............................................................................946
Figure 3.460 Activate Tx mute and activate SW on Node C .......................................................947
Figure 3.461 Remove Tx mute to Node D ............................................................................948
Figure 3.462 Activate Tx mute and activate SW on Node D .......................................................949
Figure 3.463 Remove Tx mute to Node A.............................................................................950
Figure 3.464 Activate SW on Node A ..................................................................................951
Figure 3.465 2x(1+0) or Radio LAG XPIC ..............................................................................952
Figure 3.466 2x(1+1) XPIC on MPTACC ................................................................................953
Figure 3.467 Automatic remote Tx mute .............................................................................954
Figure 3.468 Automatic remote TX mute - complete loop ........................................................955
Figure 3.469 Settings tab with available XPIC .......................................................................958
Figure 3.470 Settings tab with configured XPIC (MPT-HC) .........................................................961
Figure 3.471 Power Source for MPT Access unit.....................................................................966
Figure 3.472 Power Source for MSS-1 .................................................................................967

User Manual 3DB19901AFAA Edition 01

33

Figure 3.473 Power Source for MSS-O .................................................................................968


Figure 3.474 Power Source for EASv2 .................................................................................969
Figure 3.475 Modem unit without Adaptive Modulation settings (ODU300) .....................................972
Figure 3.476 Modem unit with Adaptive Modulation settings (ODU300) .........................................973
Figure 3.477 Fixed Modulation settings (MPT-HC) ..................................................................982
Figure 3.478 Fixed Modulation settings (MPT-HC-HQAM) ..........................................................983
Figure 3.479 Option settings (MPT-HC-HQAM) .......................................................................984
Figure 3.480 Adaptive Modulation settings (MPT-HC) ..............................................................985
Figure 3.481 Adaptive Modulation settings (MPT-HC-HQAM) ......................................................986
Figure 3.482 MPT-HC Settings tab with XPIC.........................................................................989
Figure 3.483 Additional Settings tab-panel (MPT-HC) ..............................................................992
Figure 3.484 Edit passphrase window .................................................................................993
Figure 3.485 Maintenance tab-panel (MPT-HC)......................................................................995
Figure 3.486 Fixed Modulation settings (MPT-MC) ..................................................................998
Figure 3.487 Adaptive Modulation settings (MPT-MC) ..............................................................999
Figure 3.488 Additional Settings tab-panel (MPT-MC) ............................................................ 1005
Figure 3.489 Maintenance tab-panel (MPT-MC) ................................................................... 1007
Figure 3.490 Fixed Modulation settings (MPT-HLS) ............................................................... 1010
Figure 3.491 Adaptive Modulation settings (MPT-HLS) ........................................................... 1011
Figure 3.492 Settings tab with XPIC configuration (MPT-HLS)................................................... 1015
Figure 3.493 MPT-HLS Additional settings tab-panel ............................................................. 1018
Figure 3.494 Edit passphrase window ............................................................................... 1019
Figure 3.495 MPT-HLS Maintenance tab-panel..................................................................... 1021
Figure 3.496 Loopback with ODU300 ................................................................................ 1029
Figure 3.497 ASAP E1 Layer view .................................................................................... 1031
Figure 3.498 ASAP IMA Layer view................................................................................... 1032
Figure 3.499 IMA Link Monitoring .................................................................................... 1034
Figure 3.500 IMA Group Monitoring.................................................................................. 1035
Figure 3.501 ATM Interface type..................................................................................... 1036
Figure 3.502 ASAP ATM Layer view .................................................................................. 1037
Figure 3.503 VP Layer Configuration ................................................................................ 1038
Figure 3.504 Ingress Traffic Description ............................................................................ 1039
Figure 3.505 VC Layer Configuration ................................................................................ 1041
Figure 3.506 ASAP ATM PW Layer view ............................................................................. 1043
Figure 3.507 Core-E Main view ....................................................................................... 1046
Figure 3.508 Core-E Main view (with optical SFP Ethernet port#5) ............................................ 1047
Figure 3.509 Settings tab-panel for Ethernet ports ............................................................... 1048
Figure 3.510 Settings tab-panel for SFP Ethernet ports.......................................................... 1050
Figure 3.511 Provider Bridge tab-panel............................................................................. 1053
Figure 3.512 Policy & Translation tab-panel ....................................................................... 1054
Figure 3.513 Per-VLAN Per-CoS Rate Limiter tab-panel.......................................................... 1058
Figure 3.514 Duplicate Per-VLAN Per-CoS Rate Limiter with the same PCP value........................... 1059
Figure 3.515 Per-VLAN Per-CoS Rate Limiter and VLAN Rate Limiter with the same VLAN ID ............. 1059
Figure 3.516 Per-VLAN Per-CoS Rate Limiter with VLAN ID = Any and a VLAN Rate Limiter ............... 1060
Figure 3.517 TMN In-band Settings tab panel...................................................................... 1064
Figure 3.518 MPT-HC example ....................................................................................... 1067
Figure 3.519 MSS External Input Point Main View ................................................................. 1069
Figure 3.520 MSS A-FANS Main View................................................................................. 1070
Figure 3.521 Settings tab-panel...................................................................................... 1072

34

User Manual 3DB19901AFAA Edition 01

Figure 3.522
Figure 3.523
Figure 3.524
Figure 3.525
Figure 3.526
Figure 3.527
Figure 3.528
Figure 3.529
Figure 3.530
Figure 3.531
Figure 3.532
Figure 3.533
Figure 3.534
Figure 3.535
Figure 3.536
Figure 3.537
Figure 3.538
Figure 3.539
Figure 3.540
Figure 3.541
Figure 3.542
Figure 3.543
Figure 3.544
Figure 3.545
Figure 3.546
Figure 3.547
Figure 3.548
Figure 3.549
Figure 3.550
Figure 3.551
Figure 3.552
Figure 3.553
Figure 3.554
Figure 3.555
Figure 3.556
Figure 3.557
Figure 3.558
Figure 3.559
Figure 3.560
Figure 3.561
Figure 3.562
Figure 3.563
Figure 3.564
Figure 3.565
Figure 3.566
Figure 3.567
Figure 3.568
Figure 3.569
Figure 3.570

Input External Point View............................................................................. 1073


Output External Points View ......................................................................... 1074
WTPMS welcome screen............................................................................... 1076
Toolbar................................................................................................... 1077
Export: Save............................................................................................. 1081
Exported files ........................................................................................... 1082
Print ...................................................................................................... 1083
Feature Bar Area and Configuration area .......................................................... 1084
Customized View Builder.............................................................................. 1085
Bird's Eye View.......................................................................................... 1086
Options................................................................................................... 1087
Selection tree and start button ...................................................................... 1088
Example of PM counters display ..................................................................... 1089
Saving the current NE status ......................................................................... 1090
Offline: archive name ................................................................................. 1090
Offline: current status saving ........................................................................ 1090
Offline Mode: select the NE .......................................................................... 1091
Types of PM ............................................................................................. 1093
Ethernet Aggregate Tx ................................................................................ 1095
Port 1 Aggregate Rx ................................................................................... 1096
Overview................................................................................................. 1097
Birds Eye View ......................................................................................... 1098
MPT ACC unit statistics ................................................................................ 1099
Configurations of the MPTACC ....................................................................... 1100
Ethernet Aggregate Per Queue (Queue #5) ........................................................ 1102
Overview (Modem unit) ............................................................................... 1104
Birds Eye View - MPT Access unit (Default Counters)............................................ 1105
Birds Eye View (Elaborated Counters) ............................................................. 1106
Compression Gain counters ........................................................................... 1108
Ethernet Aggregate Tx ................................................................................ 1110
Overview................................................................................................. 1111
Birds Eye View ......................................................................................... 1112
Configuration for Layer1 Radio LAG Ethernet counters on EASv2 .............................. 1114
Radio sections .......................................................................................... 1115
Radio PMs................................................................................................ 1117
Radio PMs: Radio Hop Ch 1 counters ................................................................ 1118
Radio PMs: Analog Hop Rx Ch #1 ..................................................................... 1120
Threshold Editor menu ................................................................................ 1122
Threshold creation ..................................................................................... 1123
Threshold 2 creation................................................................................... 1123
New Threshold created................................................................................ 1124
New Threshold created................................................................................ 1124
Threshold association.................................................................................. 1125
Adaptive Modulation PMs ............................................................................. 1127
Adaptive Modulation PMs: Hop Ch 1 counters ..................................................... 1128
P32E1DS1 Incoming (15 Min).......................................................................... 1131
Threshold Editor menu ................................................................................ 1134
Threshold creation ..................................................................................... 1134
Threshold 2 creation................................................................................... 1135

User Manual 3DB19901AFAA Edition 01

35

Figure 3.571 New Threshold created................................................................................ 1135


Figure 3.572 New Threshold created................................................................................ 1136
Figure 3.573 Threshold association.................................................................................. 1137
Figure 3.574 Overview................................................................................................. 1138
Figure 3.575 Birds Eye View ......................................................................................... 1139
Figure 3.576 IMA Group and IMA Link statistics ................................................................... 1141
Figure 3.577 IMA Link.................................................................................................. 1142
Figure 3.578 ATM Interface Statistics (List view example) ...................................................... 1144
Figure 3.579 Logical VPs Statistics Monitoring..................................................................... 1145
Figure 3.580 Not Logical VPs Statistics Monitoring................................................................ 1146
Figure 3.581 RSL History: List view.................................................................................. 1148
Figure 3.582 RSL History: Overview ................................................................................. 1149
Figure 3.583 RSL History: Birds Eye view .......................................................................... 1150
Figure 3.584 802.1D VLAN management............................................................................ 1151
Figure 3.585 802.1Q VLAN management (default VLAN only) ................................................... 1152
Figure 3.586 802.1Q VLAN management (default VLAN only) with LAG ....................................... 1153
Figure 3.587 802.1ad VLAN management with LAG............................................................... 1157
Figure 3.588 VLAN Table Management.............................................................................. 1158
Figure 3.589 802.1Q VLAN management............................................................................ 1159
Figure 3.590 R-APS VID ................................................................................................ 1160
Figure 3.591 NEtO main view: initial screen ....................................................................... 1161
Figure 3.592 NEtO main view: reduced screen .................................................................... 1162
Figure 3.593 NEtO NE Configuration View: NE Information...................................................... 1163
Figure 3.594 NEtO NE Configuration View: NE Description ...................................................... 1163
Figure 3.595 NEtO NE Configuration View: Command Buttons .................................................. 1164
Figure 3.596 Main View: Status & Alarms .......................................................................... 1165
Figure 3.597 New icon................................................................................................. 1166
Figure 3.598 Open icon................................................................................................ 1166
Figure 3.599 CS icon ................................................................................................... 1166
Figure 3.600 NEtO List Management ................................................................................ 1167
Figure 3.601 Opens the current list of the favorite NEs ......................................................... 1168
Figure 3.602 Magnifying glass ........................................................................................ 1168
Figure 3.603 Community String request step 1 ................................................................... 1169
Figure 3.604 Community String request step 2 .................................................................... 1169
Figure 3.605 WEB Interface: Community String menu............................................................ 1171
Figure 3.606 NEtO Servers Manager Tool ........................................................................... 1172
Figure 3.607 Manage FTP/SFTP Servers ............................................................................ 1172
Figure 3.608 FTP/SFTP Server error message...................................................................... 1172
Figure 3.609 RMI Resource counter normal operation ......................................................... 1173
Figure 3.610 RMI Resource counter abnormal operation ...................................................... 1173
Figure 3.611 RMI Registry dialog window........................................................................... 1174
Figure 3.612 NEtO Servers Manager Close warning message ................................................. 1175

4 Installation...................................................................................................1177
Figure
Figure
Figure
Figure
Figure

36

4.1
4.2
4.3
4.4
4.5

Fixing the Rack to Floor (1) ............................................................................. 1181


Fixing the Rack to Floor (2) ............................................................................. 1182
Example of securing rack assembly to computer floor ............................................. 1183
Floor file drilling template .............................................................................. 1184
Laborack ................................................................................................... 1185

User Manual 3DB19901AFAA Edition 01

Figure 4.6 ETSI rack grounding....................................................................................... 1186


Figure 4.7 Photo detail of rack grounding point................................................................... 1187
Figure 4.8 Laborack grounding ....................................................................................... 1187
Figure 4.9 MSS-8 Subrack ............................................................................................. 1188
Figure 4.10 MSS-4 Subrack ............................................................................................ 1188
Figure 4.11 MSS-1 unit................................................................................................. 1189
Figure 4.12 Fix the subrack with screws............................................................................ 1190
Figure 4.13 Subrack grounding point (bracket on the right side) (Note) ...................................... 1190
Figure 4.14 TRU (6 fuse holders) shown without cover .......................................................... 1192
Figure 4.15 TRU (10 breakers slots) shown without cover ....................................................... 1192
Figure 4.16 TRU (20 breakers slots) shown without cover ....................................................... 1192
Figure 4.17 Breaker adding ........................................................................................... 1193
Figure 4.18 TRU shown with cover .................................................................................. 1193
Figure 4.19 TRU in ETSI 21 rack .................................................................................... 1196
Figure 4.20 Fix the battery cables to the GND bar ............................................................... 1197
Figure 4.21 Remove the plastic protection cap ................................................................... 1198
Figure 4.22 Close the lock on the breaker and insert it in the TRU ............................................ 1198
Figure 4.23 Close the breaker lock and tighten the upper screw .............................................. 1199
Figure 4.24 Breaker distribution schema ........................................................................... 1199
Figure 4.25 TRU example configuration ............................................................................ 1200
Figure 4.26 2W2C Connector and Cable ............................................................................ 1201
Figure 4.27 MSS-8 Battery Access Card on subrack ............................................................... 1201
Figure 4.28 MSS-1 cabling ............................................................................................. 1202
Figure 4.29 +24 Vdc Power Supply connections ................................................................... 1203
Figure 4.30 Mechanical Support 10U (Two brackets) ............................................................ 1204
Figure 4.31 Installation kit to fix the mechanical support ..................................................... 1204
Figure 4.32 MSS 8 Fixed on wall mounting ........................................................................ 1204
Figure 4.33 SCSI 68 male connector ................................................................................. 1208
Figure 4.34 MPT Power Unit Front Panel View .................................................................... 1219
Figure 4.35 MPT Power Unit Upper View of Box................................................................... 1219
Figure 4.36 MPT Power Unit Upper View of Board ................................................................ 1220
Figure 4.37 MPT Power Unit Block Diagram ........................................................................ 1221
Figure 4.38 MPT Power Unit mounting bracket.................................................................... 1226
Figure 4.39 MPT Extended Power Unit Front Panel View ........................................................ 1228
Figure 4.40 MPT Extended Power Unit Upper View of Box ...................................................... 1228
Figure 4.41 MPT Extended Power Unit Upper View of Board.................................................... 1229
Figure 4.42 MPT Extended Power Unit Block Diagram............................................................ 1231
Figure 4.43 MPT Extended Power Unit mounting bracket ....................................................... 1238
Figure 4.44 Protection Panel 32E1 SCSI 68 - 1.0/2.3 75 ohm (Front/Rear) (3DB16104AAAA) .............. 1239
Figure 4.45 Protection Panel RJ45 120 ohm (Front/Rear) (1AF15245ABAA) .................................. 1239
Figure 4.46 Protection Panel 32E1 SCSI 68 - 1.6/5.6 75 ohm (Front) (1AF15243AAAA) ..................... 1239
Figure 4.47 Protection Panel 32E1 BNC 75 ohm (Front) (1AF15244AAAA) ..................................... 1240
Figure 4.48 Connector support 1.6/5.6 75 ohm Panel 1U (3CC08061AAAA) .................................. 1240
Figure 4.49 Connector support BNC 75 ohm Panel 1U (3CC08061ABAA)....................................... 1240
Figure 4.50 Support 19 Inch modules 120 ohm Panel 3U (3CC07810AAAA).................................... 1240
Figure 4.51 E1 Protection SCSI 68/Sub-D 37 (Front/Rear) (3DB16102AAAA) .................................. 1241
Figure 4.52 Core-E Card............................................................................................... 1241
Figure 4.53 Modem Card (to interface ODU300) .................................................................. 1242
Figure 4.54 MPT Access Card (to interface MPT-HC/HC-HQAM) ................................................ 1242

User Manual 3DB19901AFAA Edition 01

37

Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure

4.55 32xE1 PDH Access Card ................................................................................. 1243


4.56 16xE1 ATM ASAP Card ................................................................................... 1243
4.57 AUX Peripheral Card..................................................................................... 1243
4.58 STM-1 Access Card ....................................................................................... 1243
4.59 EAS P8ETH Card .......................................................................................... 1244
4.60 EASv2 Card................................................................................................ 1244
4.61 Repeater 2x1+0 32E1 (1 PBA PDH) towards customer DDF 120 Ohms 3U ....................... 1246
4.62 Repeater 2x1+0 32E1 (1 PBA PDH) towards customer DDF 120 Ohms 3U ....................... 1247
4.63 Repeater 2x1+0 32E1 (1 PBA PDH) towards internal DDF 120 Ohms 3U ......................... 1248
4.64 Repeater 2x1+0 32E1 (1 PBA PDH) towards internal DDF 120 Ohms 3U ......................... 1249
4.65 Repeater 2x1+0 32E1 (1 PBA PDH) towards 2xinternal DDF 75 Ohms BNC 2x1U
with cords 3CC52134AAAA (1 SCSI68 to 2 DB37)...................................................... 1250
Figure 4.66 Repeater 2x1+0 32E1 (1 PBA PDH) towards 2x internal DDF 75 Ohms BNC 2x1U
with cords 3CC52134AAAA (1 SCSI68 to 2 DB37)...................................................... 1251
Figure 4.67 Repeater 2x1+0 32E1 (1 PBA PDH) towards 2x internal DDF 75 Ohms BNC 2x1U
with cords 3CC52134AAAA (1 SCSI68 to 2 DB37)...................................................... 1252
Figure 4.68 Repeater 2x1+0 32E1 (2 PBA PDH) towards 2x internal DDF 75 Ohms BNC 2x1U
with cords 3CC52164AAXX (2 SCSI68 to 2 DB37) ...................................................... 1253
Figure 4.69 Repeater 2x1+0 32E1 (2 PBA PDH) towards 2x internal DDF 75 Ohms BNC 2x1U
with cords 3CC52164AAXX (2 SCSI68 to 2 DB37) ...................................................... 1254
Figure 4.70 Repeater 2x1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms ........................... 1255
Figure 4.71 Repeater 2x1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms ........................... 1256
Figure 4.72 Repeater 2x1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms ........................... 1257
Figure 4.73 Repeater 2x1+0 32E1 (1 PBA PDH) towards internal DDF 75 Ohms 1.6/5.6 2U................. 1258
Figure 4.74 Repeater 2x1+0 32E1 (1 PBA PDH) towards internal DDF 75 Ohms 1.6/5.6 2U................. 1259
Figure 4.75 Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U .................... 1260
Figure 4.76 Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms RJ45 2U .................... 1261
Figure 4.77 Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U ......................... 1262
Figure 4.78 Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U ......................... 1263
Figure 4.79 Repeater 2x1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U ......................... 1264
Figure 4.80 Terminal 1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms .............................. 1265
Figure 4.81 Terminal 1+0 64E1 (2 PBA PDH) towards customer DDF 120 Ohms .............................. 1266
Figure 4.82 Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms BNC 3U........................ 1267
Figure 4.83 Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 75 Ohms BNC 3U........................ 1268
Figure 4.84 Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U ............................ 1269
Figure 4.85 Terminal 1+0 64E1 (2 PBA PDH) towards internal DDF 120 Ohms 3U ............................ 1270
Figure 4.86 Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms
1.0/2.3 1U .................................................................................................. 1271
Figure 4.87 Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms
1.0/2.3 1U .................................................................................................. 1272
Figure 4.88 Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms
RJ45 2U ..................................................................................................... 1273
Figure 4.89 Terminal 1+1 32E1 Full protected (2 PBA PDH) towards internal DDF 75 Ohms
RJ45 2U ..................................................................................................... 1274
Figure 4.90 Terminal 1+1 32E1 Full protected with 2 cords 3CC52157AAAA (2 PBA PDH)
towards internal DDF 120 Ohms 3U..................................................................... 1275
Figure 4.91 Terminal 1+1 32E1 Full protected with 2 cords 3CC52157AAAA (2 PBA PDH)
towards internal DDF 120 Ohms 3U..................................................................... 1276
Figure 4.92 Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards customer DDF 120 Ohms .......... 1277

38

User Manual 3DB19901AFAA Edition 01

Figure 4.93 Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards customer DDF 120 Ohms .......... 1278
Figure 4.94 Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 75 Ohms
1.0/2.3 1U .................................................................................................. 1279
Figure 4.95 Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 75 Ohms
1.0/2.3 1U .................................................................................................. 1280
Figure 4.96 Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 120 Ohms 3U........ 1281
Figure 4.97 Terminal 1+1 32E1 Radio protected (1 PBA PDH) towards internal DDF 120 Ohms 3U........ 1282
Figure 4.98 Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards 2xinternal DDF 75 Ohms
1.0/2.3 1U .................................................................................................. 1283
Figure 4.99 Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards 2xinternal DDF 75 Ohms
1.0/2.3 1U .................................................................................................. 1284
Figure 4.100 Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards 2xinternal DDF 75
Ohms 1.0/2.3 1U .......................................................................................... 1285
Figure 4.101 Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards 2x internal DDF 120
Ohms 3U .................................................................................................... 1286
Figure 4.102 Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards 2x internal DDF 120
Ohms 3U .................................................................................................... 1287
Figure 4.103 Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards 2x internal DDF 120
Ohms 3U .................................................................................................... 1288
Figure 4.104 Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards customer DDF 120 Ohms......... 1289
Figure 4.105 Terminal 1+1 64E1 Radio protected (2 PBA PDH) towards customer DDF 120 Ohms......... 1290
Figure 4.106 MPT Access peripheral unit electrical connections ............................................... 1291
Figure 4.107 MPT Access peripheral unit optical connections .................................................. 1291
Figure 4.108 2xE1 SFP and EoSDH SFP .............................................................................. 1292
Figure 4.109 STM-1 units .............................................................................................. 1293
Figure 4.110 Installation subrack and 4 cord N/QMA Kit......................................................... 1293
Figure 4.111 MSS-4/8 Installation of a Card ....................................................................... 1294
Figure 4.112 Installation of an Accessory .......................................................................... 1294
Figure 4.113 Connection Cables ..................................................................................... 1295
Figure 4.114 MSS-1 Mounting Kit..................................................................................... 1300
Figure 4.115 MSS-1 Installation ...................................................................................... 1300
Figure 4.116 MSS-1 front panel ...................................................................................... 1301
Figure 4.117 MSS-1 installation constraints ........................................................................ 1305
Figure 4.118 MSS-1 grounding ........................................................................................ 1306
Figure 4.119 MSS-1 power supply .................................................................................... 1307
Figure 4.120 MSS-1 E1 external connections ....................................................................... 1310
Figure 4.121 DTE-DCE Interface ..................................................................................... 1315
Figure 4.122 Alarm Polarity .......................................................................................... 1317
Figure 4.123 Polarity of the alarm .................................................................................. 1318
Figure 4.124 Power Injector box + Bracket 3DB77008ACXX ..................................................... 1319
Figure 4.125 Grounding ............................................................................................... 1320
Figure 4.126 Power supply connector............................................................................... 1320
Figure 4.127 AC Power Converter ................................................................................... 1322
Figure 4.128 AC Power O-Ring Pigtail Cable Assembly ........................................................... 1322
Figure 4.129 Modified AC Power O-Ring Pigtail Cable ............................................................ 1323
Figure 4.130 Power Injector card.................................................................................... 1324
Figure 4.131 3DB19158AAAA installation kit components........................................................ 1325
Figure 4.132 Pole mounting of MSS-O ............................................................................... 1325
Figure 4.133 Wall mounting of MSS-O ............................................................................... 1326

User Manual 3DB19901AFAA Edition 01

39

Figure 4.134 MSS-O grounding........................................................................................ 1327


Figure 4.135 Grounding of data cable through the 1AD040130004 kit ......................................... 1327
Figure 4.136 Termination of ground cable ......................................................................... 1328
Figure 4.137 Grounding of the data cables using the 3CC50271AA grounding kit ........................... 1328
Figure 4.138 Installation of the 3CC50271AA grounding kit for compliance with IEEE 1613 ............... 1329
Figure 4.139 Installation instructions for the AC power connector ............................................ 1330
Figure 4.140 Power cable conductors placement on the connector terminal blocks........................ 1330
Figure 4.141 Data connection on MSS-O ............................................................................ 1331
Figure 4.142 RFE connector for optical data connections ....................................................... 1332
Figure 4.143 ODU (with the internal Lightning Surge Suppressor).............................................. 1334
Figure 4.144 ODU and Mounting Collar ............................................................................. 1336
Figure 4.145 Andrew Pole Mount and ODU Mounting Collar .................................................... 1336
Figure 4.146 RFS Pole Mount and Mounting Collar ................................................................ 1337
Figure 4.147 Precision Pole Mounting and ODU Mounting Collar .............................................. 1337
Figure 4.148 Andrew ODU Collar and Polarization Rotator ...................................................... 1338
Figure 4.149 RFS Rotator.............................................................................................. 1339
Figure 4.150 ODU orientation for Vertical or Horizontal Polarization ......................................... 1340
Figure 4.151 Remote Mount: front view ........................................................................... 1342
Figure 4.152 Remote Mount: rear view ............................................................................ 1343
Figure 4.153 Remote Mount with an ODU installed: front view ................................................ 1344
Figure 4.154 Remote Mount with an ODU installed: rear view ................................................. 1345
Figure 4.155 Remote Mount with the 1+1 coupler installed .................................................... 1346
Figure 4.156 Remote Mount with the 1+1 coupler and one ODU installed ................................... 1347
Figure 4.157 Coupler fitted to Antenna ............................................................................ 1353
Figure 4.158 Coupler Installation with ODUs (NB: The external lightning suppressors are no
longer needed) ............................................................................................ 1354
Figure 4.159 Coupler Installation with ODUs: Rear View (NB: The external lightning
suppressors are no longer needed) ..................................................................... 1354
Figure 4.160 Locations for Cable Grounds.......................................................................... 1358
Figure 4.161 MPT-HC/MPT-XP mounted ............................................................................ 1362
Figure 4.162 RPS module.............................................................................................. 1365
Figure 4.163 XPIC + RPS module ..................................................................................... 1366
Figure 4.164 External module installed............................................................................. 1366
Figure 4.165 Correct screw position ................................................................................ 1367
Figure 4.166 Views of MPT-HC with embedded diplexer......................................................... 1369
Figure 4.167 Views of MPT-HC with external diplexer .......................................................... 1370
Figure 4.168 Views of MPT-XP with external diplexer ........................................................... 1371
Figure 4.169 Fully equipped MPT-HC/XP ........................................................................... 1372
Figure 4.170 Low-frequency MPT-HC-HQAM/XP-HQAM with external diplexer (6 to 11 GHz).............. 1373
Figure 4.171 High-frequency MPT-HC-HQAM with internal diplexer (13-38 GHz) ............................ 1374
Figure 4.172 Composition of MPT-HC/HC-HQAM/XP/XP-HQAM with external diplexer ..................... 1376
Figure 4.173 MPT-HC/HC-HQAM/XP/XP-HQAM transceiver and external diplexer coupling
surfaces ..................................................................................................... 1377
Figure 4.174 MPT ODU O-RING gasket shapes...................................................................... 1378
Figure 4.175 Round MPT ODU O-RING gasket ...................................................................... 1378
Figure 4.176 Spine MPT ODU O-RING gasket ....................................................................... 1379
Figure 4.177 Round MPT ODU O-RING gasket installed ........................................................... 1380
Figure 4.178 Spine MPT ODU O-RING gasket installed ............................................................ 1381
Figure 4.179 Label on MPT-HC/XP transceiver boxes............................................................. 1382

40

User Manual 3DB19901AFAA Edition 01

Figure 4.180 Label on MPT-HC-HQAM/XP-HQAM transceiver boxes ............................................ 1382


Figure 4.181 Label affixed on the MPT-HC/HC-HQAM/XP/XP-HQAM transceiver box ....................... 1383
Figure 4.182 Changing the polarization on a MPT-HC/HC-HQAM ............................................... 1385
Figure 4.183 Example of vertical polarization MPT-HC/HC-HQAM/XP/XP-HQAM external
diplexer ..................................................................................................... 1386
Figure 4.184 Example of horizontal polarization MPT-HC/HC-HQAM/XP/XP-HQAM external
diplexer .................................................................................................... 1386
Figure 4.185 MPT-HC/HC-HQAM/XP/XP-HQAM RF coupler views (Bands 6-7-8/11 GHz) .................... 1388
Figure 4.186 MPT-HC/HC-HQAM RF coupler view (Bands from 11 to 38 GHz) ................................ 1389
Figure 4.187 MPT-HC/HC-HQAM/XP/XP-HQAM 6-7-8/11 GHz Integrated OMTs views ....................... 1391
Figure 4.188 MPT-HC/HC-HQAM 11 to 23 GHz Integrated OMTs views......................................... 1392
Figure 4.189 MPT-HC/MPT-XP (6-11 GHz) and MPT-HC-HQAM/XP-HQAM (6-10 GHz) Integrated
OMT-Cs views .............................................................................................. 1394
Figure 4.190 MPT-HC/XP (11, 18 and 23 GHz) and MPT-HC-HQAM/XP-HQAM (18 and 23 GHz)
Integrated OMT-Cs views................................................................................. 1395
Figure 4.191 Loads for unused ports ................................................................................ 1396
Figure 4.192 Example of integrated antenna Pole Mounting (with antenna and nose adapter) ........... 1397
Figure 4.193 Pre-cut part to be removed with a cutter in case of 1+1 configuration ....................... 1398
Figure 4.194 "Pole Mounting for Remote ODU" Installation kit (3DB10137AAXX) ............................ 1399
Figure 4.195 Example of antenna polarization change (1+0
MPT-HC/HC-HQAM/XP/XP-HQAM integrated antenna) .............................................. 1401
Figure 4.196 Putting silicone grease on O-ring before MPT-HC/HC-HQAM/XP/XP-HQAM insertion ....... 1402
Figure 4.197 MPT-HC 1+0 installation for integrated antenna (11-38 GHz) ................................... 1403
Figure 4.198 MPT-HC/MPT-XP 1+0 installation for integrated antenna (6-7-8 GHz: vertical
polarization) ............................................................................................... 1403
Figure 4.199 MPT-HC/MPT-XP 1+0 installation for integrated antenna (6-7-8 GHz: horizontal
polarization) ............................................................................................... 1404
Figure 4.200 "Pole Mounting for Remote ODU" installation...................................................... 1405
Figure 4.201 Putting silicone grease on O-ring before MPT-HC/HC-HQAM/XP/XP-HQAM insertion ....... 1405
Figure 4.202 MPT-HC 1+0 installation for not integrated antenna (embedded diplexer with
pole mounting P/N 3DB10137AAXX) .................................................................... 1406
Figure 4.203 MPT-HC/MPT-XP 1+0 installation for not integrated antenna (external diplexer
with pole mounting P/N 3DB10137AAXX) .............................................................. 1406
Figure 4.204 Coupler Polarization Change (11-38 GHz) - 1st Step and 2nd step ............................. 1408
Figure 4.205 Coupler Polarization Change (11-38 GHz) - 1st Step execution ................................ 1409
Figure 4.206 Coupler Polarization Change (11-38 GHz) - 2nd Step execution ................................ 1409
Figure 4.207 Coupler Polarization Change (11-38 GHz) - Screws fixing ....................................... 1410
Figure 4.208 Putting silicone grease on O-ring before RF coupler insertion (11-38 GHz)................... 1410
Figure 4.209 Installing the RF coupler to the radio support (11-38 GHz) ..................................... 1411
Figure 4.210 Putting silicone grease on RF couplers O-ring before MPT-HC insertion (11-38
GHz) ......................................................................................................... 1412
Figure 4.211 Installing the MPT-HC 1+1 on the RF coupler (embedded diplexer) ........................... 1413
Figure 4.212 Views of MPT-HC 1+1 integrated antenna after installation (embedded diplexer) .......... 1413
Figure 4.213 Coupler Polarization Change (6-7-8 GHz) .......................................................... 1415
Figure 4.214 Check or change the polarization of the RF coupler.............................................. 1416
Figure 4.215 Installing the RF coupler to the radio support (6-7-8 GHz) ...................................... 1418
Figure 4.216 Putting silicone grease on O-ring before MPT-HC/MPT-XP insertion (6-7-8-10/11
GHz) ......................................................................................................... 1419
Figure 4.217 Installing the MPT-HC/MPT-XP 1+1 on the RF coupler (6-7-8-10/11 GHz) .................... 1420

User Manual 3DB19901AFAA Edition 01

41

Figure 4.218 Fasten the MPT-HC/MPT-XP to the OMT ............................................................ 1426


Figure 4.219 MPT-HC/MPT-XP fastened to the OMT (6-7-8-10/11 GHz) ....................................... 1426
Figure 4.220 Locking hooks and fastening brackets .............................................................. 1434
Figure 4.221 L6 GHz OMT-C lateral noses assembly with the pipe on the left .............................. 1440
Figure 4.222 L6 and U6 GHz OMT-C lateral noses assembly with the pipe on the right .................... 1441
Figure 4.223 Sway bar kit ............................................................................................. 1442
Figure 4.224 Sway bar kit mounting................................................................................. 1442
Figure 4.225 Sway bar positioning ................................................................................... 1443
Figure 4.226 Pole Mounting for Remote ODU installation........................................................ 1446
Figure 4.227 Putting silicone grease on O-ring before RF coupler insertion .................................. 1447
Figure 4.228 11-38 GHz RF coupler installation (with pole mounting P/N 3DB10137AAXX) ................ 1448
Figure 4.229 Putting silicone grease on RF couplers O-ring before MPT-HC insertion (11-38
GHz) ......................................................................................................... 1449
Figure 4.230 Installation of MPT-HC 1+1 (11-38 GHz) - Update Figure! ....................................... 1450
Figure 4.231 "Pole Mounting for Remote ODU" installation...................................................... 1451
Figure 4.232 Putting silicone grease on O-ring before RF coupler insertion .................................. 1451
Figure 4.233 6-7-8 GHz RF coupler installation (with pole mounting P/N 3DB10137AAXX)................. 1452
Figure 4.234 Putting silicone grease on O-ring before MPT-HC/HC-HQAM/XP/XP-HQAM
insertion (6-7-8-10/11 GHz) ............................................................................. 1453
Figure 4.235 Installing the MPT-HC/MPT-XP 1+1 on the RF coupler (7-8 GHz) .............................. 1454
Figure 4.236 MPT-HC/MPT-XP 1+1 installed on the RF coupler (6-7-8-10/11 GHz) ......................... 1455
Figure 4.237 Plug kit R2CT............................................................................................ 1456
Figure 4.238 Plug kit R2CT items .................................................................................... 1457
Figure 4.239 LC/Q-XCO to LC Fiber cord ........................................................................... 1462
Figure 4.240 Fiber cable overlength box ........................................................................... 1463
Figure 4.241 RPS Q-XCO to Q-XCO optical jumper ................................................................ 1465
Figure 4.242 XPIC connector position (with external XPIC module on MPT-HC/XP) ......................... 1466
Figure 4.243 XPIC connector position (with embedded XPIC on MPT-HC-HQAM/XP-HQAM) ................ 1466
Figure 4.244 XPIC cable interconnection (MPT-HC/XP) .......................................................... 1467
Figure 4.245 XPIC cable interconnection (MPT-HC-HQAM/XP-HQAM) .......................................... 1467
Figure 4.246 MPT HC/XP grounding connector position .......................................................... 1470
Figure 4.247 MPT HC-HQAM/XP-HQAM single-screw grounding connector position ......................... 1471
Figure 4.248 MPT HC-HQAM/XP-HQAM double-screw grounding connector position ........................ 1472
Figure 4.249 Grounding plate ........................................................................................ 1473
Figure 4.250 Locations for Cable Grounds.......................................................................... 1474
Figure 4.251 Example of realization ................................................................................ 1476
Figure 4.252 Detail of the waterproofing of the kit .............................................................. 1476
Figure 4.253 Views of MPT-MC with embedded diplexer......................................................... 1479
Figure 4.254 Views of MPT-MC with external diplexer ........................................................... 1480
Figure 4.255 Composition of MPT-MC with external diplexer ................................................... 1481
Figure 4.256 MPT-MC Transceiver and external diplexer coupling surfaces .................................. 1482
Figure 4.257 7-8 GHz MPT-MC external diplexer mistake-proofing............................................. 1483
Figure 4.258 Label affixed on the MPT-MC and MPT-MC transceiver box ..................................... 1485
Figure 4.259 Example of antenna polarization change (1+0 MPT-MC integrated antenna) .............. 1490
Figure 4.260 Putting silicone grease on O-ring before MPT-MC insertion ..................................... 1491
Figure 4.261 MPT-MC 1+0 installation for integrated antenna (6 GHz and 11-38 GHz) ..................... 1491
Figure 4.262 MPT-MC 1+0 installation for integrated antenna (7-8 GHz: vertical polarization) ........... 1492
Figure 4.263 MPT-MC 1+0 installation for integrated antenna (7-8 GHz: horizontal polarization) ........ 1492
Figure 4.264 "Pole Mounting for Remote ODU" installation...................................................... 1493

42

User Manual 3DB19901AFAA Edition 01

Figure 4.265 Putting silicone grease on O-ring before MPT-MC insertion ..................................... 1494
Figure 4.266 MPT-MC 1+0 installation for not integrated antenna (with pole mounting P/N
3DB10137AAXX) ............................................................................................ 1494
Figure 4.267 Coupler Polarization Change (6 GHz and 11-38 GHz) - 1st Step and 2nd step ................ 1495
Figure 4.268 Coupler Polarization Change (6 GHz and 11-38 GHz) - 1st Step execution................... 1496
Figure 4.269 Coupler Polarization Change (6 GHz and 11-38 GHz) - 2nd Step execution .................. 1496
Figure 4.270 Coupler Polarization Change (6 GHz and 11-38 GHz) - Screws fixing .......................... 1497
Figure 4.271 Putting silicone grease on O-ring before RF coupler insertion (6 GHz and 11-38
GHz) ......................................................................................................... 1497
Figure 4.272 Installing the RF coupler to the radio support (6 GHz and 11-38 GHz) ........................ 1498
Figure 4.273 Putting silicone grease on RF couplers O-ring before MPT-MC insertion (6 GHz
and 11-38 GHz) ............................................................................................ 1499
Figure 4.274 Installing the PROTECTION MPT-MC 1+1 on the RF coupler (6 GHz and 11-38 GHz) ......... 1500
Figure 4.275 Installing the MAIN MPT-MC 1+1 on the RF coupler (6 GHz and 11-38 GHz)................... 1501
Figure 4.276 Coupler Polarization Change (7-8 GHz) ............................................................. 1502
Figure 4.277 Installing the RF coupler to the radio support (7-8 GHz) ........................................ 1504
Figure 4.278 Putting silicone grease on O-ring before MPT-MC insertion (7-8 GHz) ......................... 1505
Figure 4.279 Installing the MPT-MC 1+1 on the RF coupler (7-8 GHz).......................................... 1506
Figure 4.280 "Pole Mounting for Remote ODU" installation...................................................... 1507
Figure 4.281 Putting silicone grease on O-ring before RF coupler insertion .................................. 1507
Figure 4.282 6 GHz and 11-38 GHz RF coupler installation (with pole mounting
P/N 3DB10137AAXX) ...................................................................................... 1508
Figure 4.283 Putting silicone grease on RF couplers O-ring before MPT-MC insertion (6 GHz
and 11-38 GHz) ............................................................................................ 1509
Figure 4.284 Installation of MPT-MC 1+1 (6 GHz and 11-38 GHz) ............................................... 1510
Figure 4.285 "Pole Mounting for Remote ODU" installation...................................................... 1511
Figure 4.286 Putting silicone grease on O-ring before RF coupler insertion .................................. 1511
Figure 4.287 7-8 GHz RF coupler installation (with pole mounting P/N 3DB10137AAXX) ................... 1512
Figure 4.288 Putting silicone grease on O-ring before MPT-MC insertion (7-8 GHz) ......................... 1512
Figure 4.289 MPT-MC 1+1 installed on the RF coupler (7-8 GHz) ............................................... 1513
Figure 4.290 Right-side cable duct detail .......................................................................... 1517
Figure 4.291 Routing power cable to the MPR-LH subrack ...................................................... 1519
Figure 4.292 Fan support rack ....................................................................................... 1520
Figure 4.293 Rubber shock absorber ................................................................................ 1521
Figure 4.294 Cover plate.............................................................................................. 1522
Figure 4.295 Fan module connector with cable ................................................................... 1522
Figure 4.296 Fan cabling components .............................................................................. 1523
Figure 4.297 Separate cable and make a loop..................................................................... 1523
Figure 4.298 Install the ferrite on the wire ........................................................................ 1523
Figure 4.299 Close the ferrite on the wire ......................................................................... 1523
Figure 4.300 Pull the wire on both sides ........................................................................... 1524
Figure 4.301 Second wire ............................................................................................. 1524
Figure 4.302 Remove the wire jacket............................................................................... 1524
Figure 4.303 Power supply with ferrites on a fan module ....................................................... 1524
Figure 4.304 Terminate the power cord............................................................................ 1525
Figure 4.305 Insert fan cables in the duct cable .................................................................. 1525
Figure 4.306 Remove the faulty fan module ....................................................................... 1526
Figure 4.307 Unscrew the screws from the top cover ............................................................ 1526
Figure 4.308 Remove screws in the bottom cover ................................................................ 1527

User Manual 3DB19901AFAA Edition 01

43

Figure 4.309 Unwind wires and remove the connector .......................................................... 1527
Figure 4.310 FAN battery terminals ................................................................................. 1528
Figure 4.311 MPT-HLS rack components ............................................................................ 1530
Figure 4.312 MSS distribution patch panel ......................................................................... 1531
Figure 4.313 MSS-8 Battery connector location ................................................................... 1532
Figure 4.314 Distribution cable connections ....................................................................... 1533
Figure 4.315 Routing distribution cables from the MSS-8 to the distribution rack........................... 1534
Figure 4.316 Distribution panel ...................................................................................... 1535
Figure 4.317 Top view of cables connected to the back of the distribution panel .......................... 1535
Figure 4.318 MPR-LH subrack components ......................................................................... 1536
Figure 4.319 MPR-LH subrack cover plates for empty slots...................................................... 1537
Figure 4.320 Cables to connector.................................................................................... 1539
Figure 4.321 Positive cable ........................................................................................... 1540
Figure 4.322 Negative cable.......................................................................................... 1541
Figure 4.323 MPR-LH subrack back panel........................................................................... 1542
Figure 4.324 Inserting an MPT-HLS module ........................................................................ 1543
Figure 4.325 RF connectors on the MPT-HLS module ............................................................. 1544
Figure 4.326 RF connections from the MPT-HLS module to the TX and RX filters ........................... 1545
Figure 4.327 RX filter cover plate ................................................................................... 1546
Figure 4.328 Data and RPS ports: expanded view................................................................. 1546
Figure 4.329 Data and RPS connections in the ETSI rack......................................................... 1549
Figure 4.330 MPT-HLS fan management port ...................................................................... 1550
Figure 4.331 FAN Mgmt ports on the fan module ................................................................. 1551
Figure 4.332 Protected and non-protected fan management .................................................. 1552
Figure 4.333 Example of routing of Fan management cables ................................................... 1553
Figure 4.334 XPIC connector port ................................................................................... 1554
Figure 4.335 Supported XPIC configurations ....................................................................... 1555
Figure 4.336 LSY system without ADM .............................................................................. 1557
Figure 4.337 LSY system with ADM .................................................................................. 1558
Figure 4.338 Case a .................................................................................................... 1560
Figure 4.339 Case b .................................................................................................... 1561
Figure 4.340 Case c .................................................................................................... 1562
Figure 4.341 Case d .................................................................................................... 1563
Figure 4.342 Front view of LSY TRU ................................................................................. 1564
Figure 4.343 Connection of supply cables to the breaker holder bar for 3DB05602AA TRU ................ 1565
Figure 4.344 Connection of supply cables to the breaker holder bar for 3DB00734AA TRU ................ 1566
Figure 4.345 Breaker for LSY TRU ................................................................................... 1566
Figure 4.346 Breaker insertion in LSY TRU ......................................................................... 1566
Figure 4.347 Use of tool-screw for breaker extraction........................................................... 1567
Figure 4.348 Supply cords for fan unit and MSS-8 pre-assembled with crimp connectors and
plug-in to terminals ....................................................................................... 1568
Figure 4.349 Two 4x fan modules in the fan support............................................................. 1569
Figure 4.350 Remove Rx branching cover .......................................................................... 1570
Figure 4.351 Supply cables and CAN-BUS connectors............................................................. 1570
Figure 4.352 Supply cables and CAN-BUS connectors unplugged ............................................... 1571
Figure 4.353 Remove the fan unit ................................................................................... 1571
Figure 4.354 Bottom side of base band shelf before and after dust removal................................. 1571
Figure 4.355 Shock absorbing rubber band......................................................................... 1572
Figure 4.356 Placement of the 3DB80783AAAA gasket ........................................................... 1572

44

User Manual 3DB19901AFAA Edition 01

Figure 4.357 Routing of supply cables for fans .................................................................... 1573


Figure 4.358 CAN-BUS connection scheme for LSY systems without ADM ..................................... 1574
Figure 4.359 CAN-BUS connection scheme for LSY systems with ADM ......................................... 1574
Figure 4.360 CAN-BUS terminator for case a ...................................................................... 1575
Figure 4.361 CAN-BUS terminator for case b ...................................................................... 1575
Figure 4.362 Removal of front and top cover to enable a new slot on the sub-shelf ....................... 1576
Figure 4.363 Placement of MPT-HLS transceiver adapters ...................................................... 1577
Figure 4.364 MPT-HLS transceivers in the LSY sub-shelf with details of the blocking screws.............. 1578
Figure 4.365 RF connections for new MPT-HL transceivers in a LSY sub-shelf................................ 1579
Figure 4.366 New RX branching cover placement................................................................. 1580
Figure 4.367 Placement of MSS-8 in the ADM reserved empty space .......................................... 1581
Figure 4.368 Placement of MSS-8 in the space left by Base Band removal.................................... 1582
Figure 4.369 Remove RX branching cover .......................................................................... 1583
Figure 4.370 Systems with one or two back panels mounted ................................................... 1584
Figure 4.371 Yellow protection caps ................................................................................ 1585
Figure 4.372 Mount the back plane on the support bar .......................................................... 1585
Figure 4.373 Cables inside the rack ................................................................................. 1586
Figure 4.374 RT subrack with dummy plates ...................................................................... 1586
Figure 4.375 Front dummy plate removal .......................................................................... 1587
Figure 4.376 Top dummy plate removal ............................................................................ 1587
Figure 4.377 Septum plate to be removed ......................................................................... 1588
Figure 4.378 Bottom support guide placement.................................................................... 1589
Figure 4.379 Top support guide placement ........................................................................ 1590
Figure 4.380 Centering pin placement on back panel ............................................................ 1590
Figure 4.381 Protection cap removal ............................................................................... 1591
Figure 4.382 Remount the septum plate ........................................................................... 1592
Figure 4.383 RT sub-rack before and after new slot enabled ................................................... 1592
Figure 4.384 Detail of a branching section in a system ready for expansion ................................. 1594
Figure 4.385 Detail of a branching section in a system not ready for expansion ............................ 1594
Figure 4.386 TX and RX branching sections in a system ready for expansion................................. 1595
Figure 4.387 Remove the metallic plate ........................................................................... 1596
Figure 4.388 Repeat on the next circulator........................................................................ 1596
Figure 4.389 Example of a system branching (TX, RX and RX diversity) expanded to five
channels .................................................................................................... 1597
Figure 4.390 Remove the circulator termination.................................................................. 1598
Figure 4.391 Assemble the new expansion circulator ............................................................ 1598
Figure 4.392 Assemble the channel filters ......................................................................... 1599
Figure 4.393 Mount the second branching support bracket ..................................................... 1600
Figure 4.394 Four channels Tx heteropolar branching ........................................................... 1600
Figure 4.395 Remove the fourth circulator terminations ........................................................ 1601
Figure 4.396 Left circulator .......................................................................................... 1602
Figure 4.397 Right circulator ......................................................................................... 1602
Figure 4.398 Rx branching with two and three channels ........................................................ 1603
Figure 4.399 Screws to be removed ................................................................................. 1605
Figure 4.400 Expansion of RX and RX div branching from two to three channels in an
homopolar system ......................................................................................... 1606
Figure 4.401 Fifth channel expansion ............................................................................... 1606
Figure 4.402 Change of position of the bracket fixation points ................................................ 1607
Figure 4.403 Remove the existing waveguide stub ............................................................... 1608

User Manual 3DB19901AFAA Edition 01

45

Figure 4.404 S-shaped waveguide ................................................................................... 1608


Figure 4.405 Assemble the new Rx (Rx div) channel filters ..................................................... 1609
Figure 4.406 MPT Service Cord....................................................................................... 1614
Figure 4.407 Connect a voltmeter to the MPT-HLS ............................................................... 1616
Figure 4.408 Cable for RSSI voltage reading ....................................................................... 1617
Figure 4.409 XPD measurement...................................................................................... 1619
Figure 4.410 Checking Feedhead Flange with a Spirit level ..................................................... 1621
Figure 4.411 Indicative head-on signal pattern for a parabolic antenna ...................................... 1624
Figure 4.412 Example Tracking Path Signals ....................................................................... 1625
Figure 4.413 Example Tracking Path Signals on the First Side Lobe ........................................... 1626
Figure 4.414 Folder properties security tab ....................................................................... 1642
Figure 4.415 Non-administrator Full Control permissions provisioned....................................... 1643
Figure 4.416 Server Access Configuration for FTP server ........................................................ 1644
Figure 4.417 Server Access Configuration for SFTP server....................................................... 1645
Figure 4.418 Enable SFTP server..................................................................................... 1646
Figure 4.419 FTP/SFTP Server error message...................................................................... 1646

5 Provisioning .................................................................................................1653
Figure 5.1 Provisioning Tool Screen ................................................................................. 1654
Figure 5.2 Report panel for opened configuration file ........................................................... 1655
Figure 5.3 MSS Configuration screen example ..................................................................... 1657
Figure 5.4 Core Configuration screen example .................................................................... 1659
Figure 5.5 MOD300 Configuration screen with fixed modulation ............................................... 1661
Figure 5.6 MOD300 configuration screen with adaptive modulation ........................................... 1662
Figure 5.7 ODU300 Channel Data Help window.................................................................... 1663
Figure 5.8 MPTACC configuration with one unit in the row ..................................................... 1665
Figure 5.9 MPTACC configuration with two units in the row .................................................... 1666
Figure 5.10 1+1 configuration with MPTACC units ................................................................ 1667
Figure 5.11 XPIC polarization selection ............................................................................ 1669
Figure 5.12 MPT configuration showing MPT-HQAM (1+0 with fixed modulation) ............................ 1671
Figure 5.13 Data Help window for Profile area (fixed modulation) ............................................ 1672
Figure 5.14 MPT configuration screen showing MPT-HQAM (1+0 with adaptive modulation)............... 1673
Figure 5.15 Data Help window for Profile area (adaptive modulation)........................................ 1674
Figure 5.16 Data Help window for the Channel area ............................................................. 1675
Figure 5.17 1+1 HSB Configuration .................................................................................. 1676
Figure 5.18 1+1 FD Configuration.................................................................................... 1677
Figure 5.19 E1 configuration ......................................................................................... 1680
Figure 5.20 SDHACC configuration screen .......................................................................... 1682
Figure 5.21 SDHCHAN configuration screen ........................................................................ 1684
Figure 5.22 EASv2 configuration screen: electrical ports ........................................................ 1686
Figure 5.23 EASv2 configuration screen: optical ports ........................................................... 1688
Figure 5.24 EASv2 protection configuration........................................................................ 1689
Figure 5.25 EASv2 protection......................................................................................... 1690
Figure 5.26 LAG configuration screen............................................................................... 1691
Figure 5.27 LAG creation window ................................................................................... 1692
Figure 5.28 Created L1 Radio LAG................................................................................... 1693
Figure 5.29 Available ports ........................................................................................... 1693
Figure 5.30 Lowest index port selected ............................................................................ 1694
Figure 5.31 XPIC configuration ....................................................................................... 1695

46

User Manual 3DB19901AFAA Edition 01

Figure 5.32 Polarization in the MPT Configuration screen ....................................................... 1696


Figure 5.33 To configure 1+0 XPIC................................................................................... 1697
Figure 5.34 1+0 XPIC ................................................................................................... 1698
Figure 5.35 To configure 1+1 XPIC................................................................................... 1699
Figure 5.36 1+1 XPIC ................................................................................................... 1700
Figure 5.37 Synchronization Configuration screen ................................................................ 1701
Figure 5.38 Scheduler Configuration screen ....................................................................... 1705
Figure 5.39 Queue size configuration screen ...................................................................... 1706
Figure 5.40 QoS classification screen ............................................................................... 1707
Figure 5.41 IEEE 802.1p .............................................................................................. 1708
Figure 5.42 IEEE 802.1p classification change ..................................................................... 1709
Figure 5.43 DiffServ.................................................................................................... 1710
Figure 5.44 DiffServ classification change ......................................................................... 1711
Figure 5.45 Read-only table .......................................................................................... 1712
Figure 5.46 802.1D VLAN management ............................................................................. 1713
Figure 5.47 802.1Q VLAN management (default VLAN only) .................................................... 1714
Figure 5.48 Example of created VLANs ............................................................................. 1716
Figure 5.49 Port VLAN configuration - Core-E ports .............................................................. 1717
Figure 5.50 Port VLAN configuration - EASv2 ports ............................................................... 1718
Figure 5.51 Network configuration example ....................................................................... 1719
Figure 5.52 Network Configuration screen ......................................................................... 1720
Figure 5.53 Trusted Managers screen ............................................................................... 1721
Figure 5.54 Configuration report (offline) ......................................................................... 1723
Figure 5.55 Network Element Overview ............................................................................ 1724
Figure 5.56 How to Login ............................................................................................. 1725
Figure 5.57 Acknowledgment of Authorization window .......................................................... 1725
Figure 5.58 Enable SFP optical plug-in.............................................................................. 1727
Figure 5.59 Enabling one port in the Core-E card................................................................. 1728
Figure 5.60 Enabling Protection configuration with MPT-HC/MPT-MC ......................................... 1729
Figure 5.61 Enable Spare Core-E Card .............................................................................. 1730
Figure 5.62 Enabling E1 Access Card ................................................................................ 1731
Figure 5.63 Enabling E1 Access Card on the same row (to implement protected configuration).......... 1732
Figure 5.64 Enabling E1 Access Card protection .................................................................. 1733
Figure 5.65 Enabling STM-1 Access Card............................................................................ 1734
Figure 5.66 Enabling SFP for SDHACC ............................................................................... 1735
Figure 5.67 Enabling SFP for SDHCHAN ............................................................................. 1735
Figure 5.68 Enabling STM-1 Access Card on the same row (to implement protected
configuration).............................................................................................. 1736
Figure 5.69 Enabling STM-1 Access Card protection .............................................................. 1737
Figure 5.70 Enabling Modem Card ................................................................................... 1738
Figure 5.71 Enabling Modem Card on the same row (to implement protected configuration)............. 1739
Figure 5.72 Enabling Modem Card protection ..................................................................... 1740
Figure 5.73 Enabling MPT Access Card .............................................................................. 1741
Figure 5.74 Enabling one port in the MPT Access card ........................................................... 1742
Figure 5.75 Enabling MPT Access Card - 1 .......................................................................... 1743
Figure 5.76 Enabling one port in the MPT Access card - 1 ....................................................... 1744
Figure 5.77 Enabling Protection configuration with MPT-HC/MPT-MC ......................................... 1745
Figure 5.78 Enabling ASAP Card ..................................................................................... 1746
Figure 5.79 Enabling EAS Card ....................................................................................... 1747

User Manual 3DB19901AFAA Edition 01

47

Figure 5.80 Enabling EASv2 Card..................................................................................... 1748


Figure 5.81 Enabling AUX Card ....................................................................................... 1749
Figure 5.82 Enable the subrack for an MPT-HLS radio............................................................ 1750
Figure 5.83 Enable the MPT-HLS radio .............................................................................. 1751
Figure 5.84 Enable the MPT-HLS fan ................................................................................ 1752
Figure 5.85 Enabling Fan Unit ........................................................................................ 1753
Figure 5.86 Housekeeping input provisioning (MSS-1 or A-FANS unit).......................................... 1754
Figure 5.87 MPTACC Card Provisioning.............................................................................. 1755
Figure 5.88 EAS Card Provisioning ................................................................................... 1756
Figure 5.89 EASv2 Card Provisioning ................................................................................ 1757
Figure 5.90 Provisioning NTP protocol .............................................................................. 1759
Figure 5.91 NE Time Provisioning.................................................................................... 1761
Figure 5.92 Auxiliary Cross Connections menu .................................................................... 1763
Figure 5.93 LAG creation.............................................................................................. 1764
Figure 5.94 QoS configuration........................................................................................ 1765
Figure 5.95 Ethernet Connectivity fault management ........................................................... 1766
Figure 5.96 System Setting ........................................................................................... 1767
Figure 5.97 NE IP address provisioning.............................................................................. 1768
Figure 5.98 IP Static Routing Provisioning.......................................................................... 1770
Figure 5.99 OSPF Static Routing Provisioning ...................................................................... 1772
Figure 5.100 IPv6 Pre-provisioning .................................................................................. 1773
Figure 5.101 IPv6 Pre-provisioning step 1 of 3..................................................................... 1774
Figure 5.102 IPv6 Pre-provisioning step 2 of 3..................................................................... 1775
Figure 5.103 IPv6 Pre-provisioning step 3 of 3..................................................................... 1776

6 Maintenance and Trouble-clearing .....................................................................1777


Figure 6.1 Web interface: MPT Type Conversion option ......................................................... 1848
Figure 6.2 Web interface: choosing the main MPT-HC for conversion ......................................... 1849
Figure 6.3 Web interface: choosing the spare MPT-HC for conversion ........................................ 1849
Figure 6.4 Web interface 1+0 conversion .......................................................................... 1850
Figure 6.5 Physical replacement and log in prompt .............................................................. 1851
Figure 6.6 MPT-HC in compatibility mode.......................................................................... 1852
Figure 6.7 Software bank with upgrade software version Committed status ................................. 1864
Figure 6.8 Software bank with Initial software version Standby status ....................................... 1864
Figure 6.9 Software Management Action - Forced Activation ................................................... 1865
Figure 6.10 Software bank with initial software version Committed status .................................. 1866
Figure 6.11 Software bank with upgrade software version Standby status ................................... 1866

7 Lineup and Commissioning ..............................................................................1869


Figure 7.1 Relative positions of stations A and B ................................................................. 1872
Figure 7.2 Received power check ................................................................................... 1879
Figure 7.3 Power measurements..................................................................................... 1880
Figure 7.4 Received power details .................................................................................. 1881
Figure 7.5 IF Cable loopback ......................................................................................... 1890
Figure 7.6 Core-facing loopback ..................................................................................... 1891
Figure 7.7 Test bench for tributary functionality check with ODU300......................................... 1894
Figure 7.8 Test bench for tributary functionality check with MPT-HC/MC.................................... 1895
Figure 7.9 Test bench for tributary functionality check with ODU300......................................... 1897
Figure 7.10 Test bench for tributary functionality check with MPT-HC V2/MC .............................. 1898

48

User Manual 3DB19901AFAA Edition 01

Figure
Figure
Figure
Figure
Figure

7.11 Test bench for hop stability test with ODU300 ..................................................... 1904
7.12 Test bench for tributary functionality check with MPT-HC V2/XP/MC .......................... 1905
7.13 Test bench for hop stability test with ODU300 ..................................................... 1906
7.14 Test bench for tributary functionality check with MPT-HC V2/MC .............................. 1907
7.15 Test bench for optional Ethernet Data Channel functionality with 1 additional PC
and 1 Ethernet cable ..................................................................................... 1909
Figure 7.16 Test bench for optional Ethernet Data Channel functionality with 2 additional PCs ......... 1910
Figure 7.17 Test bench for optional Ethernet Data Channel functionality with 2 Ethernet
Data Analyzers ............................................................................................. 1912
Figure 7.18 Test bench for ATM traffic ............................................................................. 1915
Figure 7.19 Test bench for 64 kbit/s Service Channel functionality check ................................... 1916

8 Appendix A - Fiber-Microwave Protection ............................................................1919


Figure 8.1 Fiber-Microwave Protection ............................................................................. 1920
Figure 8.2 Fiber-Microwave Protection - operation............................................................... 1921
Figure 8.3 Fiber-Microwave Protection on Tail links ............................................................. 1922
Figure 8.4 Ethernet Protection Ring configuration ............................................................... 1924
Figure 8.5 Topology creation ......................................................................................... 1925
Figure 8.6 Just created topology .................................................................................... 1926
Figure 8.7 ERP Instance Creation .................................................................................... 1927
Figure 8.8 New ERP Instance ......................................................................................... 1927
Figure 8.9 New ERP Instance ......................................................................................... 1929
Figure 8.10 Just created topology ................................................................................... 1930
Figure 8.11 Add VLANs to created instances - 1................................................................... 1931
Figure 8.12 Add VLANs to the instance - 2 ......................................................................... 1932
Figure 8.13 Cross-connections 1 ..................................................................................... 1933
Figure 8.14 Cross-connections 2 ..................................................................................... 1934
Figure 8.15 Cross-connections 3 ..................................................................................... 1935
Figure 8.16 Cross-connections 4 ..................................................................................... 1936
Figure 8.17 Cross-connections 5 ..................................................................................... 1937
Figure 8.18 Cross-connections 6 ..................................................................................... 1938
Figure 8.19 Cross-connections 7 ..................................................................................... 1939
Figure 8.20 Cross-connections 8 ..................................................................................... 1940
Figure 8.21 Add VLANs to the instance - 3 ......................................................................... 1941

User Manual 3DB19901AFAA Edition 01

49

50

User Manual 3DB19901AFAA Edition 01

List of Tables
Preface ............................................................................................................... 57
Table 1 Applicability ..................................................................................................... 58
Table 2 History ............................................................................................................ 59
Table 3 Handbook structure ............................................................................................ 60

2 Product information and planning ......................................................................... 81


Table
Table
Table
Table
Table
Table
Table

2.1
2.2
2.3
2.4
2.5
2.6
2.7

Supported configurations for MPT-HC/XP and MPT-HC-HQAM/XP-HQAM together ...............103


ODU300 Modem Profiles (Fixed and Adaptive Modulation) ...........................................138
MPT-HC/MPT-XP/MPT-MC Modem Profiles (Fixed and Adaptive Modulation) ......................139
MPT-HC/MPT-XP/MPT-MC XPIC Modem Profiles (Fixed Modulation) [4] [7] ........................141
MPT-HC/MPT-XP/MPT-MC: XPIC Modem Profiles (Adaptive Modulation) [4] .......................142
MPT-HC/MPT-XP/MPT-MC XPIC SDH Modem Profiles ..................................................143
MPT-HC-HQAM / XP-HQAM Modem Profiles, including XPIC (Fixed and Adaptive
Modulation) ..................................................................................................145
Table 2.8 MPT-HC-HQAM / XP-HQAM SDH Fixed and Adaptive Modulation Modem Profiles .................147
Table 2.9 MPT-HC-HQAM / XP-HQAM High Gain Fixed Modulation Modem Profiles ............................148
Table 2.10 MPT-HLS modem profiles (Fixed and Adaptive modulation) ........................................149
Table 2.11 System parameters ........................................................................................157
Table 2.12 ODU300: 6 to 15 GHz characteristics ...................................................................162
Table 2.13 ODU300: 18 to 38 GHz characteristics ..................................................................163
Table 2.14 MPT-HLS: 4 to 13 GHz characteristics ..................................................................163
Table 2.15 MPT-XP power system: power requirements ...........................................................164
Table 2.16 MPT-HC power system: power requirements...........................................................166
Table 2.17 Power Injector general characteristics .................................................................168
Table 2.18 General characteristics (MPT power unit) .............................................................168
Table 2.19 Maximum allowed cable lengths for MPT Power Unit ...............................................169
Table 2.20 General characteristics (MPT extended power unit) .................................................169
Table 2.21 Maximum allowed cable length for MPT Extended Power Unit .....................................170
Table 2.22 MSS item codes .............................................................................................171
Table 2.23 MPT-HLS transceiver codes ...............................................................................174
Table 2.24 MPT-HLS FAN codes.......................................................................................175
Table 2.25 MPT-HLS TRU codes ......................................................................................175
Table 2.26 ETSI rack and MPT-HLS subrack codes .................................................................175
Table 2.27 MPT-HLS branching item codes .........................................................................176
Table 2.28 MPT-HLS filter and circulator item codes .............................................................177
Table 2.29 MPT-HLS cable codes ......................................................................................178
Table 2.30 Kits for MPT-HLS in LSY subrack ........................................................................178
Table 2.31 External Power Source item codes ......................................................................179
Table 2.32 Software item codes ......................................................................................179
Table 2.33 ODU300 item codes ........................................................................................181
Table 2.34 MPT-HC/MPT-XP optical interface ......................................................................200
Table 2.35 MPT-HC/HC-HQAM/MC/XP/XP-HQAM couplers ........................................................201
Table 2.36 OMT couplers ...............................................................................................201
Table 2.37 OMT-C coupler .............................................................................................203
Table 2.38 OMT Loads ..................................................................................................204
Table 2.39 MSS-1 unit indicator details ..............................................................................205

User Manual 3DB19901AFAA Edition 01

51

Table 2.40 +24/-48 Volt Converter card indicator details ........................................................208


Table 2.41 +24/-48 Volt Converter card connector details .......................................................208
Table 2.42 +24/-48 Volt Converter card indicator details ........................................................209
Table 2.43 +24/-48 Volt Converter card connector details .......................................................210
Table 2.44 P32E1DS1 DS1 card front panel indicator details .....................................................215
Table 2.45 P32E1DS1 DS1 card front panel connector details ....................................................215
Table 2.46 STM-1 Access unit front panel indicator details ......................................................218
Table 2.47 STM-1 Access unit front panel connector details .....................................................218
Table 2.48 MPTACC front panel indicator details ..................................................................226
Table 2.49 MPTACC front panel connector details .................................................................227
Table 2.50 MSS backplanes compatible with EASv2 ................................................................230
Table 2.51 EASv2 front panel indicator details .....................................................................230
Table 2.52 EASv2 front panel connector details ....................................................................231
Table 2.53 RSSI Table ...................................................................................................237
Table 2.54 Waveguide Flange Data ...................................................................................238
Table 2.55 MPT ODUs that support an embedded diplexer ......................................................240
Table 2.56 MPT ODUs that support an external diplexer.........................................................244
Table 2.57 RSSI Table ...................................................................................................247
Table 2.58 Waveguide Flange Data ...................................................................................247
Table 2.59 MPT-HLS transceiver front panel indicator details ...................................................252
Table 2.60 802.1p mapping ............................................................................................307
Table 2.61 RR weights ..................................................................................................308
Table 2.62 PW label EXP bits ..........................................................................................309
Table 2.63 Reserved Multicast Addresses ............................................................................316
Table 2.64 Intra Plug-in L1 LAG Supported 1+0 Configurations: Single LAG Group ...........................335
Table 2.65 Cross Plug-in L1 LAG Supported 1+0 Configurations: Single LAG Group ...........................336
Table 2.66 Cross Plug-in L1 LAG Supported 1+1 Configurations: Dual L1 LAG Groups ........................337
Table 2.67 ATM PW flow classifications ..............................................................................344
Table 2.68 ATM DWRR queue weights ................................................................................345
Table 2.69 L1 LAG with EASv2 queue weights ......................................................................346
Table 2.70 Releases supporting software package rollback ......................................................364

3 NE Management by software application............................................................... 377


Table 3.1 Network Configuration menu ..............................................................................396
Table 3.2 Types of ATM Traffic Contract ............................................................................689
Table 3.3 Ethernet connectivity fault management (IEEE802.1ag) command list ............................704
Table 3.4 Protocols command list ....................................................................................724
Table 3.5 TACACS+ command list .....................................................................................724
Table 3.6 Alarm list .....................................................................................................758
Table 3.7 MSS-8 consists of a subrack with 9 physical slots ......................................................838
Table 3.8 MSS-4 consists of a subrack with 5 physical slots ......................................................839
Table 3.9 Command priority list ......................................................................................869
Table 3.10 Command priority list .....................................................................................872
Table 3.11 Command priority list .....................................................................................874
Table 3.12 SDH capacity mask required configurations - fixed modulation (MPT-HC/XP) ..................984
Table 3.13 SDH capacity mask required configurations for adaptive modulation (MPT-HC/XP) ............986
Table 3.14 SDH capacity mask required configurations for fixed modulation (MPT-MC) .....................998
Table 3.15 SDH capacity mask required configurations for adaptive modulation (MPT-MC) .............. 1000
Table 3.16 Bandwidth ................................................................................................ 1040

52

User Manual 3DB19901AFAA Edition 01

Table 3.17 Port requirements for DCN protocols ................................................................. 1175

4 Installation...................................................................................................1177
Table 4.1 Power Consumption ....................................................................................... 1178
Table 4.2 Power distribution panel kits ............................................................................ 1191
Table 4.3 Recommended breaker/fuse values (A) ............................................................... 1194
Table 4.4 Number of radios powered and supported by MSS ................................................... 1194
Table 4.5 Indoor accessories for MSS ............................................................................... 1205
Table 4.6 Indoor cables .............................................................................................. 1206
Table 4.7 SCSI 68 pins FW cable colors ............................................................................ 1208
Table 4.8 Cable 8xE1 IDU-DISTRIBUTOR 75 ohm coax Free L = 15m (37 pin) ................................ 1209
Table 4.9 SUB D 37 pin - FW cable .................................................................................. 1211
Table 4.10 RJ45 E1 to wire-wrap cable ............................................................................ 1212
Table 4.11 AUX card housekeeping alarm connector detail .................................................... 1213
Table 4.12 Wiring connections for housekeeping alarm cable (3CC52200AA) ............................... 1213
Table 4.13 Enhanced Fan Housekeeping pin-out details ........................................................ 1214
Table 4.14 Enhanced Fan Housekeeping input alarm behavior ................................................ 1215
Table 4.15 Optical splitters for STM-1 signal and EoSDH (SFP for port #5 and #6 of Core-E unit) ........ 1216
Table 4.16 Cords for 2xE1 SFP ....................................................................................... 1217
Table 4.17 2 x E1 cord (RJ45 plug to free wire) .................................................................. 1217
Table 4.18 Operational environment requirements .............................................................. 1220
Table 4.19 MPT Power Unit Electrical Characteristics of DC In Interfaces ................................... 1221
Table 4.20 MPT Power Unit Electrical Characteristics of DC Out Interfaces ................................. 1222
Table 4.21 MPT Power Unit Electrical Connections of DC In Interfaces ...................................... 1223
Table 4.22 MPT Power Unit Electrical Connections of DC Out Interfaces .................................... 1223
Table 4.23 MPT Power Unit Electrical Connections of Housekeeping Interfaces ............................ 1223
Table 4.24 Main cases of alarms and LEDs by VDC MPT input battery ........................................ 1224
Table 4.25 VDC Input Battery Operation Ranges ................................................................. 1225
Table 4.26 Main cases of alarms and LEDs by VDC MPT output (N connectors) .............................. 1225
Table 4.27 DC output MPT (ODU) Operation Ranges ............................................................. 1225
Table 4.28 Maximum allowed cable length for MPT Power Unit ............................................... 1226
Table 4.29 Operational environment requirements .............................................................. 1230
Table 4.30 MPT Extended Power Unit Electrical Characteristics of DC In Interfaces ....................... 1231
Table 4.31 MPT Extended Power Unit Electrical Characteristics of DC Out Interfaces ..................... 1231
Table 4.32 MPT Extended Power Unit Electrical Characteristics of dual-stacked RJ-45
connectors ................................................................................................. 1232
Table 4.33 MPT Extended Power Unit Electrical Characteristics of housekeeping interface .............. 1232
Table 4.34 MPT Extended Power Unit main power supply features ........................................... 1233
Table 4.35 MPT Extended Power Unit Electrical Connections of DC In Interfaces .......................... 1234
Table 4.36 MPT Extended Power Unit Electrical Connections of DC Out Interfaces ........................ 1234
Table 4.37 MPT Extended Power Unit Electrical Connections of top section of dual-stacked
RJ-45 connector .......................................................................................... 1234
Table 4.38 MPT Extended Power Unit Electrical Connections of bottom section of
dual-stacked RJ-45 connector .......................................................................... 1235
Table 4.39 MPT Extended Power Unit alarm and LED indications by input battery voltage (Vin) ........ 1236
Table 4.40 VDC Input Battery Operation Ranges ................................................................ 1236
Table 4.41 MPT Extended Power Unit alarm and LED indications by MPT ODU output current
on N and RJ-45 connectors .............................................................................. 1237
Table 4.42 DC output MPT (ODU) Operation Ranges ............................................................. 1237

User Manual 3DB19901AFAA Edition 01

53

Table 4.43 Maximum allowed cable length for MPT Extended Power Unit ................................... 1237
Table 4.44 Ethernet Electrical Cables ............................................................................. 1244
Table 4.45 Ethernet Optical Cables - multi-mode jumpers ..................................................... 1244
Table 4.46 Ethernet Optical Cables - single-mode jumpers .................................................... 1245
Table 4.47 Accessories and cables for ODU300 connections .................................................... 1295
Table 4.48 Accessories and cables for MPT-HC/HC-HQAM/XP/XP-HQAM connections ..................... 1296
Table 4.49 Accessories and cables for MPT-MC connections .................................................... 1299
Table 4.50 Pinout RJ-45 connectors (NMS+Debug) ............................................................... 1301
Table 4.51 68 pin SCSI cable input (RCV) pinout ................................................................. 1302
Table 4.52 68 pin SCSI cable output (XMT) pinout ............................................................... 1303
Table 4.53 MSS-1 house-keeping pinout (sub D15 female) ...................................................... 1304
Table 4.54 MSS-1 Housekeeping pin-out details .................................................................. 1307
Table 4.55 MSS-1 Housekeeping input alarm behavior .......................................................... 1308
Table 4.56 Wiring connections for housekeeping alarm cable (3CC52201AA) ............................... 1309
Table 4.57 Pin Function: Tributaries 1-16 (MSS/E1, 32E1 PDH card, and 16E1 ASAP card) ................ 1310
Table 4.58 Pin Function: Tributaries 17-32 (32E1 PDH card) ................................................... 1312
Table 4.59 Service channel 1 pin functions ....................................................................... 1313
Table 4.60 Service channel 2 pin functions ....................................................................... 1314
Table 4.61 Housekeeping connector pin function ................................................................ 1315
Table 4.62 2xE1 SFP pin functions .................................................................................. 1318
Table 4.63 AC Power Converter features .......................................................................... 1322
Table 4.64 AC Power Converter O-Ring Pigtail Cable features ................................................. 1322
Table 4.65 Optical cables for MSS-O ................................................................................ 1332
Table 4.66 Waveguide Flange Data ................................................................................. 1348
Table 4.67 Coaxial Cable Installation Requirements ............................................................ 1356
Table 4.68 MPT-HC/MPT-XP external interfaces ................................................................. 1368
Table 4.69 RF interface .............................................................................................. 1368
Table 4.70 Legend for low-frequency MPT-HC-HQAM/XP-HQAM back view locking hooks.................. 1373
Table 4.71 Legend for MPT-HC-HQAM/XP-HQAM front and back view connectors........................... 1373
Table 4.72 Legend for high-frequency MPT-HC-HQAM with embedded diplexer (13-38 GHz).............. 1375
Table 4.73 SYMBOL OR WRITING .................................................................................... 1382
Table 4.74 SYMBOL OR WRITING .................................................................................... 1383
Table 4.75 Codes, characteristics and views of RF couplers for bands from 5.8-6 to 11 GHz ............. 1387
Table 4.76 Codes, characteristics and views of RF couplers for bands from 11 to 38 GHz ................ 1389
Table 4.77 Codes, characteristics and views of RF couplers for bands from 5.8-6 to 11 GHz ............. 1390
Table 4.78 Codes, characteristics and views of RF OMTs for bands from 11 to 23 GHz .................... 1391
Table 4.79 Codes, characteristics and views of RF OMT-Cs .................................................... 1392
Table 4.80 Codes, characteristics and views of loads for unused ports ...................................... 1395
Table 4.81 Wiring connection table for coaxial cable ........................................................... 1464
Table 4.82 MPT-HC/HC-HQAM/XP/XP-HQAM Output flanges with external antenna ....................... 1468
Table 4.83 6-38GHz Flextwist waveguide ......................................................................... 1469
Table 4.84 MPT-MC external interfaces ............................................................................ 1478
Table 4.85 RF interface .............................................................................................. 1478
Table 4.86 SYMBOL OR WRITING ................................................................................... 1484
Table 4.87 Label affixed inside the MPT-MC external diplexer ................................................ 1485
Table 4.88 Nose Adapter for MPT-HC/HC-HQAM and MPT-MC .................................................. 1514
Table 4.89 Flextwists for MPT-HC/HC-HQAM and MPT-MC ...................................................... 1515
Table 4.90 Rack positions ........................................................................................... 1530
Table 4.91 SCSI port to port connections ......................................................................... 1534

54

User Manual 3DB19901AFAA Edition 01

Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table

4.92 MPR-LH subrack positions .............................................................................. 1537


4.93 RF coaxial cable list ..................................................................................... 1544
4.94 Electrical cables ........................................................................................ 1547
4.95 Optical cables ........................................................................................... 1547
4.96 SFPs ....................................................................................................... 1548
4.97 XPIC cables ............................................................................................... 1554
4.98 TRU breaker utilization in 9600 LSY .................................................................. 1564
4.99 Breakers for TRU ........................................................................................ 1565
4.100 Supply cords for system upgrading ................................................................. 1567
4.101 RF cables reference table for MPT-HLS transceivers in an LSY rack .......................... 1579
4.102 LSY system upgrading - frequency list for branching expansion ............................... 1593
4.103 Torque forces for screws used in the branching sections ....................................... 1595
4.104 Waveguide stubs for 6L, 6U, 7, 8 GHz systems .................................................. 1603
4.105 Waveguide stubs for 10, 11, 13 GHz systems .................................................... 1604
4.106 Waveguide bendings (S-Shaped) for 6L, 6U, 7, 8GHz branching expansion .................. 1608
4.107 List of extension kits.................................................................................. 1610
4.108 Typical RSSI voltage levels with RSL for ODU300 .................................................. 1613
4.109 Typical RSSI voltage levels with RSL for MPT-HC/HC-HQAM/MC/XP/XP-HQAM ............... 1614
4.110 Typical RSSI voltage levels with RSL for MPT-HLS ................................................. 1616
4.111 Wiring table for PRX cable ............................................................................ 1617
4.112 PC Hardware Configuration ........................................................................... 1627
4.113 Operating Systems Supported ........................................................................ 1627
4.114 Java Runtime Environment ........................................................................... 1627
4.115 Tested FTP Servers ..................................................................................... 1628

6 Maintenance and Trouble-clearing .....................................................................1777


Table 6.1
Table 6.2
Table 6.3
Table 6.4
Table 6.5
Table 6.6

Alarm Matrix ............................................................................................... 1780


Modem Card and ODU300 Alarm Matrix ................................................................ 1807
MPT Access Peripheral Card, MPT-HC/HC-HQAM/HLS/XP/XP-HQAM Alarm Matrix ............ 1812
MPT-MC Alarm Matrix ..................................................................................... 1826
TMN Network Troubleshooting ......................................................................... 1837
Association of the GExx in the command output and the NE port ................................ 1840

7 Lineup and Commissioning ..............................................................................1869


Table
Table
Table
Table
Table

7.1
7.2
7.3
7.4
7.5

Phases of line-up and commissioning ................................................................... 1869


Test and commissioning instruments .................................................................. 1870
Symbols ..................................................................................................... 1871
Test ......................................................................................................... 1882
Test ......................................................................................................... 1883

8 Appendix A - Fiber-Microwave Protection ............................................................1919


Table 8.1 SFP/Splitter suggested combinations .................................................................. 1923

9 Abbreviations ...............................................................................................1947
Table 9.1 Abbreviations .............................................................................................. 1947

User Manual 3DB19901AFAA Edition 01

55

56

User Manual 3DB19901AFAA Edition 01

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

User Manual 3DB19901AFAA Edition 01

57

Applicability

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 preventing damage to 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 Safety, EMC, EMF, ESD Norms
and Equipment Labeling.

4.

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 prevail. Should not local regulations be
mandatory, then safety rules stated in this manual will prevail.

SERVICE PERSONNEL SKILL


Service Personnel must have an adequate technical background on telecommunications and
in particular 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:
Table 1 Applicability
PRODUCT
9500 MPR
PRODUCT

58

RELEASE

User Manual 3DB19901AFAA Edition 01

Scope
Table 1 Applicability (Continued)
Indoor: MSS-8/MSS-4/MSS-1

5.2.0

Outdoor: MPT-HC/MPT-HC-HQAM/MPT-MC/MPT-XP/MPT-XPHQAM

Scope
This document aims to describe the hardware and software functions 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.
For information regarding the MPT-HC (MPT-HC v1), see R4.2 user manual or prior.

History
Table 2 History
ISSUE

DATE

DESCRIPTIONS

01

October 2014

Initial Release

Change notes
There are no Change Notes related to this User Manual at the time of release.

Handbook Structure
This handbook has been edited according to the Alcatel-Lucent standardized drawing-up
guides complying with such suggestion.
This handbook is divided into the main topics described in the table of contents:

User Manual 3DB19901AFAA Edition 01

59

General on Alcatel-Lucent Customer Documentation

Table 3 Handbook structure


PREFACE

It contains general information as preliminary information, handbook


scope, history. Furthermore, it describes the handbook structure and the
customer documentation.

SAFETY

This section includes all the safety instructions.

PRODUCT INFORMATION AND


PLANNING

This section provides the equipment description (at system, MSS and ODU
levels), introduces the basic information regarding the HW architecture,
and gives its technical characteristics.

NE MANAGEMENT BY

This section gives the description and use of the SW tools available for the
NE management.

SOFTWARE APPLICATIONS
INSTALLATION

This section provides whole information regarding Equipment hardware


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, buttons).
This section provides also the whole operative instructions for the
preparation of the WebEML for the LineUp and Commissioning of the two
NEs making up the radio link.

PROVISIONING

This section gives all the instructions to provision (to configure) the NE.

MAINTENANCE AND

This section contains the whole logical and operative information for the
equipment maintenance and system upgrade.

TROUBLE-CLEARING
LINE-UP AND

This section provides all the instructions for the line-up and commissioning
of the NE.

COMMISSIONING
Appendix A

This section describes how to provision the Fiber-Microwave Protection


Ring feature.

ABBREVIATIONS

The abbreviation list is supplied.

CUSTOMER DOCUMENTATION
FEEDBACK

It contains info regarding customer opinions collection about this


documentation.

General on Alcatel-Lucent Customer Documentation


This section describes in general the AlcatelLucent Customer Documentation system,
details the association between the product levels and the associated documentation, and
explains Customer Documentation characteristics as well as the policies for its delivery and
updating.
60

User Manual 3DB19901AFAA Edition 01

General on Alcatel-Lucent Customer Documentation

CustomerIndependent Standard Customer Documentation


a.

Definition
Standard Customer Documentation, referred to hereafter, must be always meant as
plantindependent 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 maintaining the equipment according to Alcatel
Lucent Laboratory design and Installation Dept. choices. In particular:

the contents of the chapters associated to the software applications focus on the
explanation of the manmachine interface and of the operating procedures
allowed by it;

maintenance is described down to faulty PCB location and replacement.

Note: No supply to Customers of design documentation (like PCB hardware design and
production 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 functions 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 Package (SWP); as a whole, they identify the possible network
applications and the equipment performances that the specific productrelease has
been designed, engineered, and marketed for.

c.

Configurations and Network Elements

User Manual 3DB19901AFAA Edition 01

61

General on Alcatel-Lucent Customer Documentation

In some cases, a productrelease includes different possible configurations


which are distinguished 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 productrelease 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 Version 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, and is 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.
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)

62

User Manual 3DB19901AFAA Edition 01

General on Alcatel-Lucent Customer Documentation

The edition and date of issue might change on future handbook versions for the following
reasons:

only the date changes (pointed out in the Table of Contents) when modifications are
made to the editorial system not changing the technical contents of the handbook.

the edition, hence the date, is changed because modifications made concern technical
contents. In this case:

the changes with respect to the previous edition are listed in History

in affected chapters, revision bars on the left of the page indicate modifications
in text and drawings.

Changes concerning the technical contents of the handbook cause the edition number
increase (e.g. from Ed.01 to Ed.02). Slight changes (e.g. for corrections) maintain the same
edition but with the addition of a version character (e.g. from Ed.02 to Ed.02A). Version
character can be used for draft or proposal editions.

NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE


APPLICATIONS
Handbooks relevant to software applications (typically the Operator's Handbooks) are not
modified unless the new software version distributed to Customers implies 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.

Changes due to new product version


A new product version changes the handbook P/N and the edition starts from 01.

User Manual 3DB19901AFAA Edition 01

63

General on Alcatel-Lucent Customer Documentation

In this case the modified parts of the handbook are not listed.

64

User Manual 3DB19901AFAA Edition 01

1 Safety, EMC, EMF, ESD Norms and


Equipment Labeling

This chapter describes the equipment labeling and the norms mandatory or suggested that
must be considered to avoid injuries on persons and/or damage to the equipment.
This chapter is organized as follows:

Declarations 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

Waste from Electrical and Electronic Equipment (WEEE)

1.1 Declarations of conformity to CE marking and


Countries List

User Manual 3DB19901AFAA Edition 01

65

Declarations of conformity to CE marking and Countries List


Figure 1.1 Declaration of conformity for R5.x

66

User Manual 3DB19901AFAA Edition 01

Declarations of conformity to CE marking and Countries List


Figure 1.2 Declaration of conformity for MPT-HLS

User Manual 3DB19901AFAA Edition 01

67

Declarations of conformity to CE marking and Countries List


Figure 1.3 Declaration of conformity for 9600 LSY extended with MPT-HLS

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

68

User Manual 3DB19901AFAA Edition 01

Specific label for MPR-E equipment

1.2 Specific label for MPR-E equipment

Field

Field Name

Note

Alcatel-Lucent Logo

Equipment acronym

Power Supply Version MSS-8

See NB 1

Power Supply Version MSS-4

See NB 2

Power Supply Version MSS-1

See NB 3

Feeding to continuous current

European Community Logo

Not harmonized frequency logo

User Manual 3DB19901AFAA Edition 01

69

Applicable standards and recommendations

Field

Field Name

Note

WEEE Logo

Electrostatic Device Logo

NB1: 40.5V / - 57.6V; 10.2A / 7.2A


NB2: 40.5V / - 57.6V; 7.2A / 5.0A
NB3: 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


Warning: The following warnings apply:
Equipment intended for installation in Restricted Access Location
Equipment is only to be accessed by trained service personnel

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:

70

Hardware Installation

User Manual 3DB19901AFAA Edition 01

Safety Rules

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 measurements 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 inflammable substance or substances which in some way may alter the markings,
inscriptions and so on.

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

User Manual 3DB19901AFAA Edition 01

71

Safety Rules

1.4.2 Labels Indicating Danger, Forbidding, 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 following information stated in the following, and proceed as
instructed.
Note: The symbols presented in following sections are all the possible symbols that could
be present on Alcatel-Lucent equipment, but are not all necessarily present on the
equipment this handbook refers to.

1.4.3 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 equipment will have to be grounded before connecting it to the power supply
voltage, e.g.:

72

User Manual 3DB19901AFAA Edition 01

Safety Rules

2.

Safety instructions

Danger: 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.

1.4.4 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 gases
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.

User Manual 3DB19901AFAA Edition 01

73

Safety Rules

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

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

74

User Manual 3DB19901AFAA Edition 01

Safety Rules

1.4.7 Heat-radiating Mechanical Parts: labeling and safety


instructions
The presence of heat-radiating mechanical parts is indicated by the following warning label
in compliance with IEC 417 Norm, Fig.5041:

Danger: 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.

1.4.8 Optical safety


The equipment contains Class 1 laser component according to IEC 60825-1 (par. 5).

The laser source is placed in the optional SFP plug-in. 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 attached to the equipment due to
the lack of space.
See Table 2.22 for a list of boards using SFPs.

1.4.9 Microwave radiations (EMF norms)

User Manual 3DB19901AFAA Edition 01

75

Safety Rules

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

Assure good cable connection.

Install the antenna as high as possible from floor or area with public access (if
possible the cylinder delimiting 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:

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 someone moving in front of the antenna (roof top installation)

On the antenna (rear side)

76

EMF emission warning sign, placed on the antenna.

User Manual 3DB19901AFAA Edition 01

Electromagnetic Compatibility (EMC norms)

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:

1.

2.

3.

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 (contact springs and connection points, etc.)

Screw fasten the units to the subrack.

To correctly install EMC compatible equipment follow the instructions given.

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

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

User Manual 3DB19901AFAA Edition 01

77

Equipment protection against electrostatic discharges

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 measures 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 installation/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.

78

User Manual 3DB19901AFAA Edition 01

Waste from Electrical and Electronic Equipment (WEEE)

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 EMIEMC 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 and/or in difficult de-installation
operations, if necessary.

Note: This statement is referenced to in many parts of this manual, when necessary.

c.

MSS-ODU cable disconnection / connection


Before you disconnect or connect the MSS-ODU cable (at MSS or ODU side) switch
off the corresponding MSS Unit.

1.8 Waste from Electrical and Electronic Equipment


(WEEE)
This product must be selectively collected and treated. Treatment applied at end of life of
the product shall comply with the applicable national laws implementing directive on waste
electrical and electronic equipment (WEEE).
The use of the crossed-out wheeled bin symbol indicates that the product is subject to
separate collection and is not to be treated as general household waste (only for B2C
equipment).

User Manual 3DB19901AFAA Edition 01

79

Waste from Electrical and Electronic Equipment (WEEE)

WEEE Symbol

21828

Separate collection and recycling of waste equipment at the time of disposal contribute to
avoid possible negative effects on the environment and on human health.

80

User Manual 3DB19901AFAA Edition 01

2 Product information and planning

This chapter discusses the following topics:

Purpose and Function

Innovative solutions

Description

MSS Purpose, Function and Description

Stacking configuration

ODU300

MPT-HC/HC-HQAM

MPT-XP/XP-HQAM

Sparing strategy: MPT-HC/XP replacement with MPT-HC-HQAM/XPHQAM

MPT-MC

MPT-HLS

MSS to Outdoor Unit interconnections

MSS-4/8 to ODU300 interconnection

MSS-4/8 to MPT-HC/HC-HQAM interconnection

How to connect the MPT-HC/HC-HQAM to the station battery

MSS to MPT-XP/XP-HQAM interconnection

MSS-4/8 to MPT-MC interconnection

MSS-1 to MPT ODU interconnection

Antennas

Radio capacity, channeling and modulation

ODU300

MPT-HC/MPT-XP/MPT-MC

MPT-HC-HQAM and MPT-XP-HQAM

MPT-HLS

Standard Features

Radio Configurations

User Manual 3DB19901AFAA Edition 01

81

Split mount (short haul) radio configurations: ODU300, MPT-HC/HC-HQAM,


MPT-MC, MPT-XP/XP-HQAM

All indoor (long haul) radio configurations: MPT-LH using MPT-HLS

Typical System Configurations

Environmental and Electrical Characteristics

System Parameters

ODU300
6 to 15 GHz

18 to 38 GHz

MPT-HLS

Radio performances

Power Injector general characteristics

Parts Lists

Indoor items

ODU300 (with internal lightning surge suppressor)

MPT-HC/HC-HQAM with internal diplexer

MPT-MC with internal diplexer

MPT-HC/HC-HQAM/MC/XP/XP-HQAM with branching filter

MPT-HC/HC-HQAM/XP/XP-HQAM optical interface

MPT-HC/MPT-XP external modules (option)

MPT-HC/HC-HQAM/MC/XP/XP-HQAM couplers

OMT couplers

OMT-C coupler

Loads for unused ports

Functional description

82

MSS (Microwave Service Shelf)

Power distribution

+24 Vdc/-48 Vdc Converter unit

Core-E unit

32xE1 Local Access unit

2xSTM-1 Local Access unit

ASAP unit

Modem unit

MPT Access Unit (with PFoE)

EAS unit

EASv2 unit
User Manual 3DB19901AFAA Edition 01

Power Injector

ODU300

ODU block diagram

RSSI Monitoring Point

Waveguide Flange Data

ODU Coupler

MPT-HC/HC-HQAM/XP/XP-HQAM

RSSI Monitoring Point

Waveguide Flange Data

MPT-HC/HC-HQAM/XP/XP-HQAM Coupler

MPT-HC/HC-HQAM/XP/XP-HQAM Integrated OMT (Orthogonal


Mode Transducer)

MPT-MC

MPT-MC Coupler

MPT-HLS

Protection schemes

Protection schemes with ODU300

Protection schemes with MPT-HC/HC-HQAM/XP/XP-HQAM

RF Switch Fail (1+1 HSB only)

Stacking for EAS unit/EASv2 unit/MPT Access unit

Ethernet Ring Protection

Definitions

ERPS operation

ERPS and Core protection

Frequency Agility

Automatic Transmit Power Control (ATPC)

Transmitted power control: RTPC function

Power Monitoring

Adaptive Equalization

XPIC (with MPT-HC/HC-HQAM/XP/XP-HQAM and MPT-HLS only)

Link identifier

Loopbacks with ODU300

Radio Transmission Features with MPT-HC/HC-HQAM/HLS/MC/XP/XPHQAM

Adaptive Equalization

Link identifier

User Manual 3DB19901AFAA Edition 01

83

Loopbacks with MPT-HC/HC-HQAM/HLS/MC/XP/XP-HQAM

Loopback activation

Loopback life time

Packet throughput booster (Header compression)

TACACS+

TMN interfaces

Admission control in Adaptive Modulation (only with ODU300)

What does Admission Control mean?

Radio capacity in case of adaptive modulation

Adaptive modulation and admission control enabled

Adaptive modulation and admission control disabled

Managed Services and profiles

TDM and Ethernet traffic management

TDM2TDM

TDM2Eth

SDH2SDH

ETH2ETH

ATM Traffic Management

ATM Traffic Management on ASAP - PW Label Exp bits and scheduling


type

ATM Traffic Management on Modem card - Block diagram for ATM PW


Flow policer

Support of ATMoMPLS Protocol Stack (with or without MPLS Tunnel


Label

Ethernet Traffic Management

Bridge type change

Reserved Multicast Addresses

Advanced Ethernet features

LAG (Link Aggregation Group)

84

Overview

LAG overview

Quality Of Services (QoS)

QoS configuration

QoS in the MPT-HC/HC-HQAM/MC/XP/XP-HQAM

Cross-connections

E1 Cross-connections

STM-1 Cross-connections
User Manual 3DB19901AFAA Edition 01

Purpose and Function

Radio-Radio Cross-connections

Ethernet Cross-connections

ATM PW cross-connections

Port Segregation

Software package rollback

Synchronization for PDH/SDH/DATA

Synchronization overview

Synchronization Sources and protection policy

Synchronization Sources assignment

Synchronization sources assignment rules

Allowed synchronization sources assignment

Synchronization for E1 ports with ASAP unit

Synchronization distribution from 9500 MPR to 9400 AWY

Synchronization connection in Stacking configuration with Core protection

2.1 Purpose and Function


The 9500 Microwave Packet Radio (MPR) is a microwave digital radio that supports PDH,
SDH and packet data (Ethernet) for migrating to IP. The 9500 MPR-E provides a generic,
modular IP platform for multiple network applications (including 2G/3G/HSDPA/WiMAX
backhauling to Metro Ethernet areas) to accommodate broadband services. The 9500 MPRE radio family supports low, medium, and high capacity applications using European data
rates, frequencies, channel plans, and tributary interfaces.

TDM/PDH Data Rates: E1, E3

SDH Data Rates: STM-1

ATM Data Rates: E1

Ethernet Data Speed: 10, 100, 1000 Mb/s

RF Frequency Range: 6 to 38 GHz

2.1.1 Innovative solutions


The 9500 MPR-E innovative solutions mainly are:

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 convergence layer.

User Manual 3DB19901AFAA Edition 01

85

Purpose and Function

Service awareness: traffic handling and quality management, queuing traffic


according to the type of service assigned, independently by the type of interface

Packet node: no service aggregation limits with all traffic aggregated in packets, in
term of: capacity, type of service requirements and type of interface

Service-driven adaptive modulation: fully exploit the air bandwidth in its entirety
by changing modulation scheme according to the propagation availability and
allocate transport capacity, discriminating traffic by different services, only possible
in a packet-based environment.

1.

Multiservice aggregation layer


Figure 2.1 Multiservice Aggregation Layer

9500 MPR-E aggregates and carries over a COMMON PACKET LAYER: TDM
2G, 3G, LTE 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.

86

Service awareness

User Manual 3DB19901AFAA Edition 01

Purpose and Function


Figure 2.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, STM1, 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 matrix

User Manual 3DB19901AFAA Edition 01

87

Purpose and Function


Figure 2.3 Packet node matrix

9500 MPR-E offers a PACKET NODE 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 2.4 Service-driven Packet Adaptive Modulation

Traffic with high priority will always have bandwidth available, like voice
(deterministic approach).
Broadband traffic is discriminated by QoS dynamically, with modulation scheme
changes driven by propagation conditions.

2.1.2 Description
The 9500 MPR-E consists of one Microwave Service Switch (MSS) and one or more
Outdoor Units (ODU) or Indoor Units (MPR-LH).

88

User Manual 3DB19901AFAA Edition 01

Purpose and Function


Figure 2.5 9500 MPR-E Main Components
9500 MPR
Microwave Packet Radio

Outdoor Units

Indoor Units

Microwave Service Switch

MPT-HLS

MSS-8
8 Slots

ODU300
or
or

MSS-4
4 Slots
or

MPT-HC V2/MPT-XP
or

MPT-MC

MSS-1
1 Slot
or

MSS-O
No2958

Up to 6 ODU300 can be connected to an MSS-8

Up to 2 ODU300 can be connected to an MSS-4

Up to 18 MPT can be connected to an MSS-8


Note: The maximum number that can be powered directly by an MSS-8 shelf is 8.

Up to 12 MPT can be connected to an MSS-4

Up to 6 MPT can be connected to an MSS-1

Up to 3 MPT can be connected to an MSS-O

User Manual 3DB19901AFAA Edition 01

89

Purpose and Function

For the interconnections between the MSS and the Outdoor Units refer to MSS to Outdoor
Unit interconnections.
Note: Another type of MSS is available (MSS-1c), which is described in the Alcatel-Lucent
9500 MPR MPR-e and MSS-1c User Manual.

2.1.2.1 MPR-LH solution


The MPR Long Haul system is an indoor solution providing long haul service to the ETSI
market. The solution includes the MPT-HL Slim radio (MPT-HLS).
The following configurations are supported at system level:

Split mount configurations: in this release the transceiver is available connected to an


MSS. Maximum configuration is 20 MPT-HLS in the same rack.

Nodal and repeater configurations (repeater up to 10 MPT- HLS)

MPT-HLS can be used in conjunction with MSS-1, MSS-4 and MSS-8.

MPT-HLS can be connected to the Core-E or to an EASv2 card.

For each frequency two different MPT-HLS radios are available and supported in this
release: standard and space diversity version.
Each hardware version supports standard power and high power version with dedicated
licenses.
The release supports all frequencies from 4 to 13 GHz. However, not all hardware may be
available.

2.1.3 MSS Purpose, Function and Description


The MSS shelf houses the indoor cards. It is available in three versions:

MSS-8

MSS-4

MSS-1

The MSS family also includes the MSS-O, which can be installed indoors or outdoors.
The MSS provides cross-connection, port aggregation, switching, and equipment
management.

90

User Manual 3DB19901AFAA Edition 01

Purpose and Function

The MSS-4 and MSS-8 shelf consists of card cage and backplane in which mounts access
and radio peripheral and Core-E control plug-in cards (see Figure 2.6 and Figure 2.7).
Figure 2.6 MSS-8 shelf

Slot #1: Main Core-E module

Slot #2: Spare Core-E module

Slot #3: Transport module

Slot #4: Transport module

Slot #5: Transport module

Slot #6: Transport module

Slot #7: Transport module

Slot #8: Transport module or


AUX peripheral module

Slot #9:
FANS
module

23550

Figure 2.7 MSS-4 shelf

Slot #1: Main Core-E module

Slot #2: Spare Core-E module

Slot #3: Transport module

Slot #4: Transport module or


AUX peripheral module

Slot #5:
FANS
module
23551

The MSS-1 unit is a monoboard without a card cage or backplane which provides the
functions of a Core-E module and a TDM 32E1/DS1 local access module with 16 ports (see
Figure 2.8 and Figure 2.9).
Figure 2.8 MSS-1

Figure 2.9 MSS-1 unit

Core-E

TDM 16E1/DS1

Housekeeping
23552

The MSS-O is a power injector and switch, part of the MSS family. The MSS-O is
optimized for outdoor usage and can be installed outdoors or indoors. It provides three RJ45
Ethernet ports, two of these with PFoE, and one SFP port.

User Manual 3DB19901AFAA Edition 01

91

Purpose and Function


Figure 2.10 MSS-O

2.1.3.1 MSS-4/8 modules


The Core-E modules provide six Ethernet user interfaces (4 electrical interfaces as default
+ 2 electrical/optical interfaces available with optional SFP. For the available SFPs, see
Available SFPs for port #5 and port #6), the local WebEML interface and the local debug
interface.
The Main Core-E and the Spare Core-E modules have different roles.
The Main Core-E is always provided. It performs key node management and control
functions, and provides various DC rails from the -48 Vdc input. It also incorporates a plugin flash card, which holds node configuration and license data.
The Main Core-E also includes the cross-connection matrix, which implements all the
cross-connections between the Transport modules, between the Ethernet user ports and
between the Ethernet user ports and the Transport modules. The matrix is a standard
Ethernet switch, based on VLAN, assigned by the WebEML.
The Ethernet ports of the Core-E can be configured in 2 ways:

92

1.

to be used as GigaEthernet interface for Ethernet traffic (Note: for port#5 and port#6
the optional SFP must be installed);

2.

to be used to connect an MPT: MPT-HC/HC-HQAM/MC/XP/XP-HQAM to port#1


to port#4; an MPT-HC/HC-HQAM/XP/XP-HQAM only to port#5 and port#6.

User Manual 3DB19901AFAA Edition 01

Purpose and Function

For each radio direction with MPT, one Ethernet port on the Core-E and one
associated MPT has to be provisioned in case of 1+0 radio configuration. Two
Ethernet ports on the Core-E and two associated MPT have to be provisioned in case
of 1+1 radio configurations.
The Spare Core-E is an optional unit to provide aggregated traffic protection and control
platform protection.
The following Transport modules are supported:

TDM 32E1/DS1 local access module: provides the external interfaces for up to
32xE1 tributaries, manages the encapsulation/reconstruction of PDH data to/from
standard Ethernet packets and sends/receives standard Ethernet packets to/from both
Core-E modules; it contains the switch for the EPS Core-E protection and the DC/DC
converter unit.

STM-1 local access module: provides the external interfaces for up to 2 electrical or
optical STM-1 signals, manages the encapsulation/reconstruction of SDH data to/
from standard Ethernet packets and sends/receives standard Ethernet packets to/from
both Core-E modules; it contains the switch for the EPS Core-E protection and the
DC/DC converter unit.

ASAP module: provides the external interfaces for up to 16xE1 tributaries carrying
ATM cells, manages the encapsulation/reconstruction of ATM cells (according to the
PWE3 standard) to/from standard Ethernet packets and sends/receives standard
Ethernet packets to/from both Core-E modules; it contains the DC/DC converter unit.

ODU300 Access module: this module is used to interface one ODU300. It sends/
receives standard Ethernet packets to/from both Core-E modules, manages the radio
frame (on Ethernet packet form) generation/termination, the interface to/from the
alternate Radio module (for RPS management), the cable interface functions to ODU;
it contains the logic for the EPS Core-E protection, the RPS logic and the DC/DC
converter unit.
For each radio direction with ODU300, one ODU300 Access module in the MSS and
one associated ODU300 has to be provisioned in case of 1+0 radio configuration.
Two radio access modules and two associated ODU300 have to be provisioned in
case of 1+1 radio configurations.

MPT Access (with PFoE) module: this module is used to interface up to two MPTHC/HC-HQAM/MC/XP/XP-HQAM. This module provides the Power Feed over
Ethernet to the MPT (only one cable to carry Ethernet traffic and power supply). The
interface to the MPT-HC/HC-HQAM/XP/XP-HQAM is a standard GbEth interface
(electrical or optical) and a power supply cable. The interface to the MPT-MC is a
standard GbEth interface (electrical). It sends/receives standard Ethernet packets to/
from both Core-E modules. It contains the logic for the EPS Core-E protection and
the DC/DC converter unit.

User Manual 3DB19901AFAA Edition 01

93

Purpose and Function

For each radio direction with MPT, one MPT Access module in the MSS and one
associated MPT has to be provisioned in case of 1+0 radio configuration. One (or
two) MPT Access modules and two associated MPT have to be provisioned in case
of 1+1 radio configurations.

EAS Peripheral (P8ETH) module: provides up to 8 ports for customer Ethernet


traffic or for the connection to an MPT-HC/HC-HQAM/XP/XP-HQAM
It supports the following traffic external interfaces:

port #1 to port #4: Ethernet 10/100/1000 Base-T

port #5 to port #8: Ethernet SFP 1000 Base-X optical: 1000BASE-LX (GbE LX
10 km) or 1000BASE-SX (GbE SX 550 m) or 1000BASE-CX (GbE CX 25 m)
Port #5 to port #8 can also be used to connect an MPT-HC/HC-HQAM/XP/XPHQAM (by installing an SFP 1000BASE-SX) in 1+0 configuration. The MPTHC/HC-HQAM/XP/XP-HQAM can be grouped to create an L1 Radio LAG.

EASv2 module: provides up to 8 ports for customer Ethernet traffic or for the
connection to an MPT-HC/HC-HQAM/XP/XP-HQAM, MPT-MC, or MPT-HLS.
This module provides the Power Feed over Ethernet to the MPT-xC, using only one
cable to carry Ethernet traffic and power supply. This option is not compatible with
the MPT-XP/XP-HQAM. The interface to the MPT-HC/HC-HQAM/XP/XP-HQAM
is a standard GbEth interface (electrical or optical) and a power supply cable. The
interface to the MPT-MC is a standard GbEth interface (electrical).
It supports the following traffic external interfaces:

port #1 to port #4: Ethernet 10/100/1000 Base-T

port #5 to port #8: Ethernet SFP 1000 Base-X optical: 1000BASE-LX (GbE LX
10 km), 1000BASE-SX (GbE SX 550 m), 1000BASE-CX (GbE CX 25 m),
Port #5 to port #8 can also be used to connect an MPT-HC/HC-HQAM/XP/XPHQAM (by installing an SFP 1000BASE-SX) in 1+0 configuration.

The MPT-HC/HC-HQAM/XP/XP-HQAM connected to optical or electrical


ports on the EASv2 can be grouped to create an L1 Radio LAG.

Note: A cross-plugin LAG can be created if two EASv2 modules are provisioned on the
same row in the MSS. A cross-plugin LAG cannot be created between an EAS module and
an EASv2 module.

According to the transport modules installed different configurations can be implemented.


The optional AUX peripheral module provides 2x64 kbit/s service channels and
housekeeping alarms.
The optional +24 Vdc/-48 Vdc Converter module (to be installed in transport slot 4, 6 or
8 of MSS-8) can be used to power supply the MSS for +24 Vdc office applications.

2.1.3.2 MSS-1 functions


94

User Manual 3DB19901AFAA Edition 01

Purpose and Function

The MSS-1 provides the functions of a main Core-E module and a a TDM 32E1/DS1 local
access module with 16 ports, along with four input alarm interfaces for housekeeping.
The Core-E provides six Ethernet user interfaces (4 electrical interfaces as default + 2
electrical/optical interfaces available with optional SFP), the local WebEML interface and
the local debug interface. See Available SFPs for port #5 and port #6 or the available SFPs.
Note: The Core-E interfaces appear in the WebEML as MSS/CORE.

TDM 32E1/DS1 local access provides the external interfaces for 16xE1 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.
Note: The E1 interfaces appear in the WebEML as MSS/E1.

2.1.3.3 MSS-O functions


The MSS-O provides four ports for customer Ethernet traffic or for the connection to an
MPT-HC/HC-HQAM/XP/XP-HQAM or MPT-MC. Two of the ports provide the Power
Feed over Ethernet to the MPT-xC, using only one cable to carry Ethernet traffic and power
supply. This option is not compatible with the MPT-XP/XP-HQAM.
The interface to the MPT-HC/HC-HQAM/XP/XP-HQAM or MPT-MC is a standard
GbEth interface (electrical).
It supports the following traffic external interfaces:

port #1 to port #3: Ethernet 10/100/1000 Base-T

port #4: Ethernet SFP 1000 Base-X optical

Note: The interfaces appear in the WebEML as MSS/CORE.

2.1.3.4 Block diagrams


A simplified block diagram of the MSS is shown in Figure 2.11 for MSS-8, Figure 2.12 for
MSS-4, Figure 2.13 for MSS-1, and in Figure 2.14 for MSS-O.
User Manual 3DB19901AFAA Edition 01

95

Purpose and Function


Figure 2.11 MSS-8 block diagram
Core-E MODULE
PSU

TRANSPORT
MODULE
TRANSPORT
MODULE

Controller

Flash
RAM

1 GbEth

TRANSPORT
MODULE

ETHERNET
SWITCH

TRANSPORT
MODULE
TRANSPORT
MODULE

LIU

LIU

TRANSPORT
MODULE
4x10/100/1000
2 Electrical/Optical SFPs
electrical Ethernet ports
(port #5 to port #6)
(port #1 to port #4)
23180

Figure 2.12 MSS-4 block diagram


Core-E MODULE
PSU

Controller

Flash
RAM

1 GbEth
TRANSPORT
MODULE
TRANSPORT
MODULE

ETHERNET
SWITCH

LIU

LIU

4x10/100/1000
2 Electrical/Optical SFPs
electrical Ethernet ports
(port #5 to port #6)
(port #1 to port #4)
23181

96

User Manual 3DB19901AFAA Edition 01

Purpose and Function


Figure 2.13 MSS-1 block diagram
MSS/CORE
PSU

Flash

Controller

RAM

1 GbEth
MSS/E1
MSS/DS1

ETHERNET
SWITCH

LIU

LIU

PFoE hot swap PFoE hot swap

RJ45 RJ45 RJ45 RJ45

SCSI

I2C

housekeeping
expanded
SUB-D 15

2 Electrical/Optical SFPs
(port #5 to port #6)
23179

Figure 2.14 MSS-O block diagram

2.1.4 Stacking configuration


User Manual 3DB19901AFAA Edition 01

97

Purpose and Function

To manage more directions the Stacking configuration can be realized by installing up


to 3 MSS, interconnected through the Ethernet ports in the Core-E module. In the example
of Figure 2.15 are shown the interconnected MSS.
Figure 2.15 Stacking configuration with 3 MSS

For the Stacking configuration it is recommended to enable the Static Lag Criteria.
Also with the Core protection a maximum of 3 MSS can be interconnected as shown in
Figure 2.16. For the synchronization connection refer to Synchronization connection in
Stacking configuration with Core protection.
To implement this configuration the LOS alarm on the Ethernet ports must be enabled as
switching criterion of the Core protection. To enable this functionality the Ethernet LOS
Criteria feature has to be enabled (refer to System Settings).

98

User Manual 3DB19901AFAA Edition 01

Purpose and Function


Figure 2.16 Stacking configuration with 3 MSS with Core protection

2.1.5 ODU300
The ODU300 is a microprocessor controlled transceiver that interfaces the MSS with the
antenna.
Transmitter circuits in the ODU300 consist of cable interface, local oscillator, upconverter/
mixer, power amplifier, and diplexer.
Receive circuits consist of diplexer, low-noise amplifier, local oscillator, downconverter/
mixer, automatic gain control, and cable interface.

User Manual 3DB19901AFAA Edition 01

99

Purpose and Function

Power is provided by -48Vdc from the MSS to the ODU300 DC-DC converter.
The ODU300 is frequency dependent.
Figure 2.17 ODU300

2.1.6 MPT-HC/HC-HQAM
The high-capacity (HC) MPT ODUs are available in two models. Both models share the
same characteristics except where indicated below:

MPT-HCsupports QPSK, and 8, 16, 32, 64, 128,and 265 QAM

MPT-HC-HQAM supports the same range as the MPT-HC, but adds support for
512 QAM and 1024 QAM

MPT-HC/HC-HQAM is microwave equipment capable of transporting the Ethernet traffic


over an RF radio channel.
MPT-HC/HC-HQAM is microprocessor-controlled equipment that interfaces the MSS
with the antenna.
The input interface is a standard Giga Ethernet interface (electrical or optical).
The Ethernet traffic is transmitted over the radio channel according to the configured QoS
and to the scheduler algorithms.
Transmitter circuits in the MPT-HC/HC-HQAM consist of Ethernet input interface,
modulator, local oscillator, upconverter/mixer, power amplifier, and diplexer.
Receiver circuits consist of diplexer, low-noise amplifier, local oscillator, downconverter/
mixer, automatic gain control, demodulator and Ethernet output interface.
The microprocessor manages the frequency, transmit power alarming, and performance
monitoring.

100

User Manual 3DB19901AFAA Edition 01

Purpose and Function

The MPT-HC/HC-HQAM is Ethernet powered using proprietary PFoE. Alternatively, the


ODUs can be powered using two cables: one cat5e or coaxial cable for the power supply
and one optical cable for the Ethernet traffic.
MPT-HC is XPIC-ready, and requires the installation of a dedicated module.
The MPT-HC-HQAM has an integrated, on-board XPIC function which can be enabled by
software upgrade using a dedicated XPIC RTU license. No additional hardware module is
required.
The MPT-HC-HQAM does not require a solar shield.
The MPT-HC/HC-HQAM is frequency dependent.
The MPT-HC V2 can be used as a spare for the MPT-HC V1, except on a radio link where
radio encryption is active. The radio encryption feature is not supported by the MPT-HC
V1. See Sparing strategy: MPT-HC/XP replacement with MPT-HC-HQAM/XPHQAMfor information about MPT-HC-HQAM spares.
Figure 2.18 MPT-HC

2.1.7 MPT-XP/XP-HQAM
The extended power (XP) MPT ODUs are available in two model. Both models share the
same characteristics except where indicated below:

MPT-XPsupports QPSK, and 8, 16, 32, 64, 128,and 265 QAM

User Manual 3DB19901AFAA Edition 01

101

Purpose and Function

MPT-XP-HQAM supports the same range as the MPT-XP, but adds support for
512 QAM and 1024 QAM

MPT-XP is a very high power version of the MPT-HC.


The MPT-XP provides an additional 5 to 9 dB of transmit power as compared to equivalent
MPT-HC.
MPT-XP is XPIC-ready, and requires the installation of a dedicated module.
The MPT-XP-HQAM has an integrated, on-board XPIC function which can be enabled by
software upgrade using a dedicated XPIC RTU license. No additional hardware module is
required.
The power MUST be provided from the MPT Extended Power Unit to the MPT-XP/XPHQAM Data+-DC connector.
The MPT-XP/XP-HQAM is frequency dependent.
See Sparing strategy: MPT-HC/XP replacement with MPT-HC-HQAM/XP-HQAM for
information about XP-HQAM spares.

2.1.8 Sparing strategy: MPT-HC/XP replacement with


MPT-HC-HQAM/XP-HQAM
The MPT-HC-HQAM/XP-HQAM can be used as a spare for the MPT-HC/XP in specified
configurations. The main and spare MPT-HC/XPs in 1+1 HSB/SD or 1+1 FD configuration
must be replaced with MPT-HC-HQAM/XP-HQAMs.
Air compatibility is supported as follows:

an MPT-HC is air compatible with an MPT-HC-HQAM and an MPT-XP is air


compatible with an MPT-XP-HQAM only when the MPT-HC-HQAM/XP-HQAM is
configured in compatibility mode

an MPT-HC-HQAM/XP-HQAM and an MPT-HC-HQAM/XP-HQAM only when e


both ODUs are configured in the same mode; that is, both must be in standard mode
or both must be configured in compatibility mode.

Table 2.1 summarizes the supported configurations for MPT-HC-HQAM/XP-HQAM in


combination with MPT-HC/XP.

102

User Manual 3DB19901AFAA Edition 01

Purpose and Function

Table 2.1 Supported configurations for MPT-HC/XP and MPT-HC-HQAM/XP-HQAM


together
Configuration

Comments

Supported

1+0

Air compatibility

Yes

1+1 HSB/FD/SD

Same MPT type for main


and spare on one station

Yes

Different MPT types for


main and spare on one
station

No

Same MPT type for main


and spare on one station

Yes

Co-channel XPIC

Different MPT types for


main and spare on one
station
(N+0) LAG L1

Minimum modulation
scheme of 16 QAM

Yes

LAG L2

Yes

(1+0) RING

Yes

2.1.9 MPT-MC
MPT-MC is similar to MPT-HC from an architecture standpoint. The only differences are:
1.

MPT-MC cannot be connected in optical 100m length cable limitation.

2.

MPT-MC is not delivered with a solar shield.

3.

XPIC is not supported with MPT-MC. RPS is supported only with a cable.

User Manual 3DB19901AFAA Edition 01

103

Purpose and Function


Figure 2.19 MPT-MC

2.1.10 MPT-HLS
Starting from R5.0.0 the Alcatel-Lucent 9500 MPR Product Line has been enhanced with
the introduction of the Indoor platform based on the MPT. This radio concept has been
integrated and adapted to the Alcatel-Lucent 9500 MPR Long Haul platform to support all
indoor applications.
The indoor units are common for all the needs (Short haul / Long Haul) and the indoor
Transceivers (MPT- HLS) are fully inherited from the outdoor units, and have been adapted
to Long Haul and cabinet requirements.
The MPT-HLS is part of the MPT family with the same behavior as other MPTs, but with
specific characteristics related to the needs of long haul and high capacity networks.
In this release the frequencies supported are L6 GHz and U6 GHz.
The MPT-HLS transceiver is only available connected to an MSS-1, MSS-4, or MSS-8.
MPR-e mode is not available. The MPT-HLS can be connected to the Core-E or to an
EASv2 card.

104

User Manual 3DB19901AFAA Edition 01

Purpose and Function

For each frequency 2 different RTs are available and supported in this release: standard and
space diversity version. The space diversity version includes a second receiver and a baseband combiner, which provide a combination of main receiver and second receiver signals.
XPIC is available with a dedicated license.
Four different ETSI racks are available (2200, 2000, 1700, 1300 mm).
Inside the ETSI rack 2 different RT subracks can be hosted with up to 10 transceivers in
each.
The TRU (always protected) has to be located on the top of the ETSI rack.
For each RT subrack a fans subrack has to be installed.
Figure 2.20 MPT-HLS system

TRU
Fan modules
Rx diversity filters (upper subrack)
Rx main filters (upper subrack)

Rx branching filters (covered)

MPT-HLS unit
Tx branching filters (upper subrack)
MSS unit
MSS unit
Fan modules
Rx diversity filters (lower subrack)
Rx main filters (lower subrack)

Rx branching filters (covered)

MPT-HLS unit
Tx branching filters (lower subrack)

24003

2.1.11 MSS to Outdoor Unit interconnections


2.1.11.1 MSS-4/8 to ODU300 interconnection
User Manual 3DB19901AFAA Edition 01

105

Purpose and Function

A single 50 ohm coaxial cable connects a ODU300 Modem unit to its ODU. The max. cable
length is up to 150 m. ODU cable, connectors and grounding kits are separately provided.
The ODU cable carries DC power supply for the ODU and five signals:

Tx telemetry

Reference signal to synchronize the ODU IQ Mod/Demod oscillator

311 MHz IQ modulated signal from the ODU300 Radio Interface (transmit IF)

Rx telemetry

126 MHz IQ modulated signals from the ODU (receive IF)


Figure 2.21 MSS to ODU300 interconnection

2.1.11.2 MSS-4/8 to MPT-HC/HC-HQAM interconnection


The MPT-HC/HC-HQAM can be connected in the following ways:

106

One cable, Data+DC (MPT Access unit to MPT-HC/HC-HQAM)

Two cables, Data and DC (MPT Access unit to MPT-HC/HC-HQAM)


User Manual 3DB19901AFAA Edition 01

Purpose and Function

Two cables, Data and DC (Core-E unit to MPT-HC/HC-HQAM)

One cable, Data+DC (Core-E unit to MPT-HC/HC-HQAM)

Two cables, Data and DC (EAS unit to MPT-HC/HC-HQAM)

One cable, Data+DC (EASv2 unit to MPT-HC/HC-HQAM)

Two cables, Data and DC (EASv2 unit to MPT-HC/HC-HQAM)

2.1.11.2.1 One cable, Data+DC (MPT Access unit to MPT-HC/HC-HQAM)


One electrical Ethernet cable connects an MPT Access unit in the MSS to its MPT-HC/HCHQAM (the MPT Access unit provides the PFoE).
The max cable length is 100 m.
The Ethernet electrical cable is provided with connectors to be mounted on site with the
specific RJ45 tool (1AD160490001).

User Manual 3DB19901AFAA Edition 01

107

Purpose and Function


Figure 2.22 MPTACC to MPT-HC/HC-HQAM interconnection

2.1.11.2.2 Two cables, Data and DC (MPT Access unit to MPT-HC/HC-HQAM)


Two cables connect an MPT Access unit in the MSS to its MPT-HC/HC-HQAM:

108

One cable is a coaxial or Cat5E cable to send the power supply to the MPT-HC/HCHQAM:

User Manual 3DB19901AFAA Edition 01

Purpose and Function

for length lower or equal to 100 m the power cable can be Cat5E cable to send
the power supply to the MPT-HC/HC-HQAM. The Ethernet electrical cable is
provided with connectors to be mounted on site with the specific RJ45 tool
(1AD160490001);

for length higher than 100m, the cable is a 50 ohm coaxial cable to send the
power supply to the MPT-HC/HC-HQAM

Note: In case of length lower than 100m and presence in the field of 1 coaxial already
installed and free it is recommended to use the coax cable to minimize the installation
effort.

The second cable is an Ethernet optical cable.


The Ethernet optical cable is preassembled and available in different lengths (up to
300 m).

Note: A special cord adapter must be connected to the coaxial cable on the MPT-HC/HCHQAM.

User Manual 3DB19901AFAA Edition 01

109

Purpose and Function


Figure 2.23 MPTACC to MPT-HC/HC-HQAM interconnection (2 cables)

2.1.11.2.3 Two cables, Data and DC (Core-E unit to MPT-HC/HC-HQAM)


Two cables connect the MPT:

110

one optical cable connected to port#5 or port #6 of the Core-E unit or one electrical
cable connected to the electrical ports (port#1 to port#4) of the Core-E unit.

a coaxial cable connected to a power source. Power can be supplied by the following:

Station battery, as shown in Figure 2.24

MPT Power Unit

MPT Extended Power Unit

Power Injector Box/Power Injector Card

User Manual 3DB19901AFAA Edition 01

Purpose and Function


Figure 2.24 Core-E to MPT-HC/HC-HQAM interconnection (2 cables)

Note: MPT-HC/HC-HQAM must be connected to a fuse or a breaker on a customer power


distribution box.

The recommended value is 3 Amps.


For the connection to the station battery refer to How to connect the MPT-HC/HC-HQAM
to the station battery.

User Manual 3DB19901AFAA Edition 01

111

Purpose and Function


2.1.11.2.4 One cable, Data+DC (Core-E unit to MPT-HC/HC-HQAM)
The Core-E data is connected to a Power Injector Box, Power Injector Card or MPT
Extended Power Unit using one electrical Ethernet cable. The data and power are connected
from the power supply to the MPT-HC/HC-HQAM using a second electrical Ethernet
cable.
The maximumcable length is 100 m.
Figure 2.25 shows the connection with the Power Injector Box. The Power Injector box is
an indoor device to be installed in a 19/21 rack.
Figure 2.26 shows the connection with the Power Injector Card. The Power Injector card is
a unit to be installed in the MSS-4 or MSS-8.

112

User Manual 3DB19901AFAA Edition 01

Purpose and Function


Figure 2.25 Core-E connection to the MPT-HC/HC-HQAM through the Power Injector Box

User Manual 3DB19901AFAA Edition 01

113

Purpose and Function


Figure 2.26 Core-E connection to the MPT-HC/HC-HQAM through the Power Injector card

2.1.11.2.5 Two cables, Data and DC (EAS unit to MPT-HC/HC-HQAM)


Two cables connect the MPT:

114

one optical cable connected to one port (from port#5 to port #8) of the EAS unit.

a coaxial cable connected to a power source. Power can be supplied by the following:

Station battery, as shown in EAS to MPT-HC/HC-HQAM interconnection

MPT Power Unit

MPT Extended Power Unit

Power Injector Box/Power Injector Card

User Manual 3DB19901AFAA Edition 01

Purpose and Function


Figure 2.27 EAS to MPT-HC/HC-HQAM interconnection

Note: MPT-HC/HC-HQAM must be connected to a fuse or a breaker on a customer power


distribution box.

The recommended value is 3 Amps.


For the connection to the station battery refer to How to connect the MPT-HC/HC-HQAM
to the station battery.

User Manual 3DB19901AFAA Edition 01

115

Purpose and Function


2.1.11.2.6 One cable, Data+DC (EASv2 unit to MPT-HC/HC-HQAM)
One electrical Ethernet cable connects an EASv2 unit in the MSS to its MPT-HC/HCHQAM (the EASv2 unit provides the PFoE).
The maximum cable length is 100 m.
The Ethernet electrical cable is provided with connectors to be mounted on site with the
specific RJ45 tool (1AD160490001).
Figure 2.28 EASv2 to MPT-HC/HC-HQAM interconnection

2.1.11.2.7 Two cables, Data and DC (EASv2 unit to MPT-HC/HC-HQAM)


Two cables connect the MPT:

116

User Manual 3DB19901AFAA Edition 01

Purpose and Function

one optical cable connected to one port (from port#5 to port #8) of the EASv2 unit.

a coaxial cable connected to a power source. Power can be supplied by the following:

Station battery

MPT Power Unit, as shown in Figure 2.29

MPT Extended Power Unit

Power Injector Box/Power Injector Card

PFoE ports (#1 through #4) of the EASv2 card


Figure 2.29 EASv2 to MPT-HC/HC-HQAM interconnection (2 cables)

User Manual 3DB19901AFAA Edition 01

117

Purpose and Function

Note: MPT-HC/HC-HQAM must be connected to a fuse or a breaker on a customer power


distribution box.

The recommended value is 3 Amps.


For the connection to the station battery refer to How to connect the MPT-HC/HC-HQAM
to the station battery.

2.1.11.3 How to connect the MPT-HC/HC-HQAM to the station battery


Figure 2.30 shows the devices used to connect an MPT directly to a battery.
Note: This type of powering is only possible when the connection to the MPT is by optical
fiber.

From front to back:

118

Coaxial cable with N connector

Wall mount support 3CC50149AAXX (max 4 MPT)

Lightning arrestor with its grounding cable

Low pass filter

Cable N to two wires ("pigtail")

Grounding kits

Cable N to RJ-45 (pigtail)

User Manual 3DB19901AFAA Edition 01

Purpose and Function


Figure 2.30 MPT-HC/HC-HQAM directly connected to the battery

2.1.11.4 MSS to MPT-XP/XP-HQAM interconnection


The MPT-XP can be connected in the following ways:

One cable, Data+DC (MPT Access unit to MPT-XP/XP-HQAM)

Two cables, Data+DC (MPT Access unit to MPT-XP/XP-HQAM)

Two cables, Data and DC (Core-E unit to MPT-XP/XP-HQAM)

One cable, Data+DC (Core-E unit to MPT-XP/XP-HQAM)

Two cables, Data and DC (EAS or EASv2 unit to MPT-XP/XP-HQAM)

One cable, Data+DC (EASv2 unit to MPT-XP)

The MPT-XP/XP-HQAM requires the MPT Extended Power Unit in all cases.

2.1.11.4.1 One cable, Data+DC (MPT Access unit to MPT-XP/XP-HQAM)


The MPT-XP/XP-HQAM is connected to the MPT Access card through the MPT Extended
Power Unit using electrical Ethernet cables. One cable connects an MPT Access unit in the
MSS to the MPT Extended Power Unit. And a second cable connects the MPT Extended
Power Unit to its MPT-XP/XP-HQAM (the MPT Extended Power Unit provides the
PFoE).
Figure 2.31 shows the connections implemented with the MPT Extended Power Unit.

User Manual 3DB19901AFAA Edition 01

119

Purpose and Function

Table 2.21 shows the maximum cable lengths. For cable lengths longer than 40 m, optical
fiber is required.
The MPT Extended Power Unit is an indoor device to be installed in a 19/21 rack.
The Ethernet electrical cable is provided with connectors to be mounted on site with the
specific RJ45 tool (1AD160490001).
Figure 2.31 MPT Access to MPT-XP/XP-HQAM interconnection (with MPT Extended Power Unit)

120

User Manual 3DB19901AFAA Edition 01

Purpose and Function


2.1.11.4.2 Two cables, Data+DC (MPT Access unit to MPT-XP/XP-HQAM)
Table 2.21 shows the maximum cable lengths. For cable lengths longer than the maximum
CAT5E cable length, optical fiber is required.
Two cables connect an MPT Access unit in the MSS to its MPT-XP/XP-HQAM:

One cable is a 50 ohm coaxial cable to send the power supply from the MPT Extended
Power Unit to the MPT-XP/XP-HQAM:

for length lower or equal to the maximum CAT5E cable length, CAT5E cable
can be used to send the power supply to the MPT-XP/XP-HQAM. The Ethernet
electrical cable is provided with connectors to be mounted on site with the
specific RJ45 tool (1AD160490001);

for length higher than the maximum CAT5E cable length, the cable is a 50 ohm
coaxial cable to send the power supply to the MPT-XP/XP-HQAM

Note: In case of length lower than the maximum CAT5E length and presence in the field
of 1 coaxial already installed and free it is recommended to use the coax cable to
minimise the installation effort.

The second cable is an Ethernet optical cable.


The Ethernet optical cable is preassembled and available in different lengths (up to
300 m).

Note: A special cord adapter must be connected to the coaxial cable on the MPT-XP/XPHQAM.

User Manual 3DB19901AFAA Edition 01

121

Purpose and Function


Figure 2.32 MPT Access to MPT-XP/XP-HQAM interconnection with optical Ethernet
cable (MPT Extended Power Unit)

122

User Manual 3DB19901AFAA Edition 01

Purpose and Function


2.1.11.4.3 Two cables, Data and DC (Core-E unit to MPT-XP/XP-HQAM)
Two cables connect the MPT-XP/XP-HQAM:

one optical cable connected to port#5 or port #6 of the Core-E unit.

a coaxial cable connected to the MPT Extended Power Unit to provide the power
supply.
Figure 2.33 Core-E to MPT-XP/XP-HQAM interconnection with optical Ethernet
cable (MPT Extended Power Unit)

Note: MPT Extended Power Unit must be connected to a fuse or a breaker on a customer
power distribution box. The recommended value is 3 Amps per MPT.

User Manual 3DB19901AFAA Edition 01

123

Purpose and Function


2.1.11.4.4 One cable, Data+DC (Core-E unit to MPT-XP/XP-HQAM)
The MPT-XP/XP-HQAM is connected to the Core-E through the MPT Extended Power
Unit using electrical Ethernet cables. One cable connects an Core-E in the MSS to the MPT
Extended Power Unit. And a second cable connects the MPT Extended Power Unit to its
MPT-XP/XP-HQAM (the MPT Extended Power Unit provides the PFoE).
Table 2.21 shows the maximum cable lengths. For cable lengths longer than the maximum
CAT5E cable length, optical fiber is required.
In Figure 2.34 is shown the connections implemented with the MPT Extended Power Unit.
The MPT Extended Power Unit is an indoor device to be installed in a 19/21 rack.

124

User Manual 3DB19901AFAA Edition 01

Purpose and Function


Figure 2.34 Core-E to MPT-XP/XP-HQAM interconnection with electrical Ethernet cable (MPT
Extended Power Unit)

2.1.11.4.5 Two cables, Data and DC (EAS or EASv2 unit to MPT-XP/XP-HQAM)


Two cables connect the MPT-XP/XP-HQAM:

one optical cable connected to one port (from port#5 to port #8) of the EAS unit.

a coaxial cable connected to the MPT Extended Power Unit to provide the power
supply.

User Manual 3DB19901AFAA Edition 01

125

Purpose and Function


Figure 2.35 EAS to MPT-XP/XP-HQAM interconnections (with MPT Extended Power
Unit)

Note: MPT Extended Power Unit must be connected to a fuse or a breaker on a customer
power distribution box. The recommended value is 3 Amps per MPT-XP/XP-HQAM.

126

User Manual 3DB19901AFAA Edition 01

Purpose and Function


2.1.11.4.6 One cable, Data+DC (EASv2 unit to MPT-XP)
The MPT-XP is connected to the EASv2 through the MPT Extended Power Unit using
electrical Ethernet cables. One cable connects an EASv2 in the MSS to the MPT Extended
Power Unit. A second cable connects the MPT Extended Power Unit to its MPT-XP (the
MPT Extended Power Unit provides the PFoE).
Table 2.21 shows the maximum cable lengths. For cable lengths longer than the maximum
CAT5E cable length, optical fiber is required.
Figure 2.34 shows the connections implemented with the MPT Extended Power Unit.
The MPT Extended Power Unit is an indoor device to be installed in a 19/21 rack.

User Manual 3DB19901AFAA Edition 01

127

Purpose and Function


Figure 2.36 EASv2 to MPT-XP/XP-HQAM interconnection with electrical Ethernet cable (MPT
Extended Power Unit)

2.1.11.5 MSS-4/8 to MPT-MC interconnection


The MPT-MC can be connected in the following ways:

128

One cable (MPT Access unit to MPT-MC)

One cable (Core-E unit to MPT-MC)

One cable (EASv2 unit to MPT-MC)

User Manual 3DB19901AFAA Edition 01

Purpose and Function


2.1.11.5.1 One cable (MPT Access unit to MPT-MC)
One electrical Ethernet cable connects an MPT Access unit in the MSS to its MPT-MC (the
MPT Access unit provides the PFoE).
The max cable length is 100 m.
The Ethernet electrical cable is provided with connectors to be mounted on site with the
specific RJ45 tool (1AD160490001).
Figure 2.37 MPTACC to MPT-MC interconnection

User Manual 3DB19901AFAA Edition 01

129

Purpose and Function


2.1.11.5.2 One cable (Core-E unit to MPT-MC)
The MPT-MC is connected to a Power Injector through one electrical Ethernet cable.
The max cable length is 100 m.
Figure 2.38 shows the connection with a Power Injector Box. The Power Injector box is an
indoor device to be installed in a 19/21 rack.
Figure 2.39 shows the connections implemented with the Power Injector card. The Power
Injector card is a unit to be installed in a MSS-4 or MSS-8.
Figure 2.38 Core-E to MPT-MC connection through the Power Injector Box

130

User Manual 3DB19901AFAA Edition 01

Purpose and Function


Figure 2.39 Core-E to MPT-MC connection through the Power Injector card

2.1.11.5.3 One cable (EASv2 unit to MPT-MC)


One electrical Ethernet cable connects an EASv2 unit in the MSS to its MPT-MC (the
EASv2 unit provides the PFoE).
The max cable length is 100 m.
The Ethernet electrical cable is provided with connectors to be mounted on site with the
specific RJ45 tool (1AD160490001).

User Manual 3DB19901AFAA Edition 01

131

Purpose and Function


Figure 2.40 EASv2 to MPT-MC interconnection

2.1.11.6 MSS-1 to MPT ODU interconnection


The MSS-1 can be connected to an MPT ODU in seven different ways:

One cable, Data+DC (MSS-1 ports 1 and 2 to MPT-HC/HC-HQAM)

One cable, Data+DC (MSS-1 ports 3 and 4 to MPT-HC/HC-HQAM)

Two cables, Data and DC (MSS-1 ports 5 and 6 to MPT-HC/HC-HQAM)

One cable, Data+DC (MSS-1 ports 1 to 4 to MPT-XP/XP-HQAM)

Two cables, Data and DC (MSS-1 ports 5 and 6 to MPT-XP/XP-HQAM)

One cable (MSS-1 ports 1 and 2 to MPT-MC)

One cable (MSS-1 ports 3 and 4 to MPT-MC)

2.1.11.6.1 One cable, Data+DC (MSS-1 ports 1 and 2 to MPT-HC/HC-HQAM)


One electrical Ethernet cable connects MSS-1 unit ports 1 or 2 to its MPT-HC/HC-HQAM
(MSS-1 port provides the PFoE). These connections are similar to those shown in
Figure 2.22.
132

User Manual 3DB19901AFAA Edition 01

Purpose and Function

The max cable length is 100 m.


The Ethernet electrical cable is provided with connectors to be mounted on site with the
specific RJ45 tool (1AD160490001).

2.1.11.6.2 One cable, Data+DC (MSS-1 ports 3 and 4 to MPT-HC/HC-HQAM)


MSS-1 unit ports 3 or 4 connect to the MPT-HC/HC-HQAM through a Power Injector Box
or MPT Extended Power unit through one electrical Ethernet cable (Power Injector Box or
MPT Extended Power Unit provides the PFoE). These connections are similar to those
shown in Figure 2.25.
The max cable length is 100 m.
The Power Injector box is an indoor device to be installed in a 19/21 rack.
The MPT Extended Power Unit is an indoor device to be installed in a 19/21 rack.

2.1.11.6.3 Two cables, Data and DC (MSS-1 ports 5 and 6 to MPT-HC/HC-HQAM)


Two cables connect MSS-1 ports 5 or 6 to MPT-HC/HC-HQAM:

one Ethernet optical cable connected to MSS-1 port#5 or port #6. The Ethernet optical
cable is preassembled and available in different lengths (up to 300 m).

a coaxial cable connected to either a Power Injector box, MPT Power Unit, MPT
Extended Power Unit, or station battery to provide the power supply.

for length lower or equal to 100 m the power cable can be CAT5E cable to send
the power supply to the MPT-HC/HC-HQAM. The Ethernet electrical cable is
provided with connectors to be mounted on site with the specific RJ45 tool
(1AD160490001);

for length higher than 100m, the cable is a 50 ohm coaxial cable to send the
power supply to the MPT-HC/HC-HQAM

These connections are similar to those shown in Figure 2.33.


Note: In case of length lower than 100m and presence in the field of 1 coaxial already
installed and free it is recommended to use the coax cable to minimise the installation
effort.
Note: A special cord adapter must be connected to the coaxial cable at the MPT-HC/HCHQAM.

User Manual 3DB19901AFAA Edition 01

133

Purpose and Function

Note: If the Power Injector box is used with coax cable, a special cord adapter must be
connected to the coax cable at the Power Injector end.

2.1.11.6.4 One cable, Data+DC (MSS-1 ports 1 to 4 to MPT-XP/XP-HQAM)


The MPT-XP is connected to MSS-1 ports 1 to 4 through the MPT Extended Power Unit
using electrical Ethernet cables. One cable connects an MSS-1 port to the MPT Extended
Power Unit. A second cable connects the MPT Extended Power Unit to its MPT-XP/XPHQAM (the MPT Extended Power Unit provides the PFoE). These connections are similar
to those shown in Figure 2.34.
The max cable length is 100 m.
The MPT Extended Power Unit is an indoor device to be installed in a 19/21 rack.
Note: MPT Extended Power Unit must be connected to a fuse or a breaker on a customer
power distribution box. The recommended value is 3 Amps per MPT.

2.1.11.6.5 Two cables, Data and DC (MSS-1 ports 5 and 6 to MPT-XP/XP-HQAM)


Two cables connect MSS-1 port 5 or 6 to the MPT-XP/XP-HQAM. These connections are
similar to those shown in Figure 2.33.

one Ethernet optical cable connected to MSS-1 port#5 or port #6. The Ethernet optical
cable is preassembled and available in different lengths (up to 300 m).

a coaxial cable connected to the MPT Extended Power Unit to provide the power
supply.

The MPT Extended Power Unit is an indoor device to be installed in a 19/21 rack.
Note: MPT Extended Power Unit must be connected to a fuse or a breaker on a customer
power distribution box. The recommended value is 3 Amps per MPT.

2.1.11.6.6 One cable (MSS-1 ports 1 and 2 to MPT-MC)


One electrical Ethernet cable connects MSS-1 ports 1 or 2 to its MPT-MC (MSS-1 ports 1
and 2 provides the PFoE). This connection is similar to those shown in Figure 2.37.
The max cable length is 100 m.
134

User Manual 3DB19901AFAA Edition 01

Purpose and Function

The Ethernet electrical cable is provided with connectors to be mounted on site with the
specific RJ45 tool (1AD160490001).

2.1.11.6.7 One cable (MSS-1 ports 3 and 4 to MPT-MC)


One electrical Ethernet cable connects MSS-1 ports 3 or 4 to an external power source,
Power Injector card or MPT Extend Power Unit. The MPT-MC is then connected to the
external power source through a second electrical Ethernet cable. These connections are
similar to those shown in Figure 2.38.
The max cable length is 100 m.
The Power Injector box is an indoor device to be installed in a 19/21 rack.
The MPT Extended Power Unit is an indoor device to be installed in a 19/21 rack.
Note: MPT Extended Power Unit must be connected to a fuse or a breaker on a customer
power distribution box. The recommended value is 3 Amps per MPT.

2.1.11.7 MSS-O to MPT ODU interconnection


The MSS-O can be connected to an MPT ODU in the following ways:

One cable, Data+DC (MSS-O ports 1 and 2 to MPT-/HC/HC-HQAM)

Two cables, Data and DC (MSS-O port 3 to MPT-HC/HC-HQAM)

One cable (MSS-O ports 1 to 3 to MPT-XP/XP-HQAM)

One cable (MSS-O ports 1 and 2 to MPT-MC)

One cable (MSS-O port 3 to MPT-MC)

2.1.11.7.1 One cable, Data+DC (MSS-O ports 1 and 2 to MPT-/HC/HC-HQAM)


One electrical Ethernet cable connects MSS-O shelf ports 1 or 2 to its MPT-HC/HCHQAM (MSS-O port provides the PFoE). These connections are similar to those shown in
Figure 2.22.
The max cable length is 100 m.
The Ethernet electrical cable is provided with connectors to be mounted on site with the
specific RJ45 tool (1AD160490001).

User Manual 3DB19901AFAA Edition 01

135

Purpose and Function


2.1.11.7.2 Two cables, Data and DC (MSS-O port 3 to MPT-HC/HC-HQAM)
Two cables connect the MPT:

one electrical cable connected to port #3 of the MSS-O.

a coaxial cable connected to a power source. Power can be supplied by the following:

Station battery, as shown in Figure 2.24

MPT Power Unit

MPT Extended Power Unit

Power Injector Box/Power Injector Card

Note: MPT-HC/HC-HQAM must be connected to a fuse or a breaker on a customer power


distribution box.
The recommended value is 3 Amps per MPT.

For the connection to the station battery refer to How to connect the MPT-HC/HC-HQAM
to the station battery.

2.1.11.7.3 One cable (MSS-O ports 1 to 3 to MPT-XP/XP-HQAM)


The MPT-XP is connected to MSS-O ports 1 to 3 through the MPT Extended Power Unit
using electrical Ethernet cables. One cable connects an MSS-O port to the MPT Extended
Power Unit. A second cable connects the MPT Extended Power Unit to its MPT-XP/XPHQAM (the MPT Extended Power Unit provides the PFoE). These connections are similar
to those shown in Figure 2.34.
The max cable length is 100 m.
The MPT Extended Power Unit is an indoor device to be installed in a 19/21 rack.
Note: MPT Extended Power Unit must be connected to a fuse or a breaker on a customer
power distribution box. The recommended value is 3 Amps per MPT.

2.1.11.7.4 One cable (MSS-O ports 1 and 2 to MPT-MC)


One electrical Ethernet cable connects MSS-O ports 1 or 2 to its MPT-MC (MSS-O ports
1 and 2 provides the PFoE). This connection is similar to those shown in Figure 2.37.
The max cable length is 100 m.
The Ethernet electrical cable is provided with connectors to be mounted on site with the
specific RJ45 tool (1AD160490001).
136

User Manual 3DB19901AFAA Edition 01

Radio capacity, channeling and modulation


2.1.11.7.5 One cable (MSS-O port 3 to MPT-MC)
One electrical Ethernet cable connects MSS-O port 3 to an external power source, Power
Injector card or MPT Extended Power Unit. The MPT-MC is then connected to the external
power source through a second electrical Ethernet cable. These connections are similar to
those shown in Figure 2.38.
The max cable length is 100 m.
The Power Injector box is an indoor device to be installed in a 19/21 rack.
The MPT Extended Power Unit is an indoor device to be installed in a 19/21 rack.
Note: MPT Extended Power Unit must be connected to a fuse or a breaker on a customer
power distribution box. The recommended value is 3 Amps per MPT.

2.1.12 Antennas
Antennas for direct mounting an ODU are available in diameters from 0.3 m to 1.8 m,
depending on the frequency band.
A polarization rotator is included within the antenna collar, and direct-mounting equal or
unequal loss couplers are available for single antenna protected operation.
Antenna mounts are designed for use on industry-standard 114 mm OD pipe-mounts.
An ODU can also be used with standard antennas via a remote-mount kit and flexible
waveguide.

2.2 Radio capacity, channeling and modulation


2.2.1 ODU300
Table 2.2 provides modem profile information for the ODU300.

User Manual 3DB19901AFAA Edition 01

137

Radio capacity, channeling and modulation

Table 2.2 ODU300 Modem Profiles (Fixed and Adaptive Modulation)


Modem profile

Net radio throughput


(Mbit/s)

Number of E1

7 MHz QPSK class 2

10.88

7 MHz 16 QAM class 4

21.76

7 MHz 64 QAM class 5

32.64

13

14 MHz QPSK class 2

21.76

14 MHz 16 QAM class 4

43.52

18

14 MHz 64 QAM class 5

65.28

27

28 MHz QPSK class 2

43.52

18

28 MHz 16 QAM class 4

87.04

37

28 MHz 32 QAM class 4

111.36

48

28 MHz 64 QAM class 5

130.56

56

28 MHz 128 QAM class 5

156.8

68

28 MHz 256 QAM class 6

177.6

77

56 MHz 16 QAM class 4

166.4

72

56 MHz 128 QAM class 5

313.6

136

56 MHz 256 QAM class 6

345.6

150

Note: QPSK can be also named 4 QAM.

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 QPSK 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 QPSK-16-64 QAM range or 16 QAM for QPSK-16 QAM
range).

2.2.2 MPT-HC/MPT-XP/MPT-MC

138

User Manual 3DB19901AFAA Edition 01

Radio capacity, channeling and modulation

The following tables provide modem profile information for MPT-HC, MPT-XP and MPTMC ODUs. Table 2.3 describes the modem profiles for fixed and adaptive modulation
without XPIC, Table 2.4 describes XPIC modem profiles in fixed modulation, and
Table 2.5 describes XPIC modem profiles in adaptive modulation. Table 2.6 describes
SDH modem profiles in fixed and adaptive modulation.
Table 2.3 MPT-HC/MPT-XP/MPT-MC Modem Profiles (Fixed and Adaptive Modulation)
Modem profile

Net radio throughput (Mbit/s)

Number of E1

3.5MHz QPSK class 2

4.47

3.5MHz 8PSK class 2

7.14

3.5MHz 16QAM class 4

9.04

3.5MHz 32QAM class 4

11.31

3.5MHz 64QAM class 5

14.13

7MHz QPSK class 2

9.06

7MHz 8PSK class 2

13.93

7MHz 16QAM class 4

20.27

7MHz 32QAM class 4

25.06

11

7MHz 64QAM class 5

30.60

13

7MHz 128QAM class 5

36.54

16

7MHz 256QAM class 6

41.92

19

14 MHz QPSK class2

20.44

14 MHz 8PSK class2

30.90

14

14 MHz 16QAM class 4

42.15

19

14 MHz 32QAM class 4

51.91

23

14 MHz 64QAM class 5

63.90

29

14 MHz 128QAM class 5

75.67

34

14MHz 256QAM class 6

89.18

41

28MHz QPSK class 2

42.52

19

28MHz 8PSK class 2

63.83

29

28MHz 16QAM class 4

85.89

39

28MHz 16QAM class 4 "unified"

89.67

41

28MHz 32QAM class 4

110.00

50

User Manual 3DB19901AFAA Edition 01

139

Radio capacity, channeling and modulation


Table 2.3 MPT-HC/MPT-XP/MPT-MC Modem Profiles (Fixed and Adaptive Modulation) (Continued)
Modem profile

Net radio throughput (Mbit/s)

Number of E1

28MHz 64QAM class 5

131.83

60

28MHz 128QAM class 5

155.95

71

28MHz 128QAM class 5 SDH

157.54

1xSTM1

28MHz 256QAM class 6

184.91

85

30 MHz QPSK [6]

44.46

20

30 MHz 8PSK [5]

66.80

30

30 MHz 16QAM [5]

89.20

41

30 MHz 32QAM [5]

111.06

51

30 MHz 64QAM [5]

141.09

65

30 MHz 128QAM

166.60

76

30 MHz 256QAM

189.81

87

40MHz 64QAM class 5

191.01

88

40MHz 128QAM class 5

225.86

104

40MHz 256QAM class 5

254.28

117

50 MHz QPSK [8]

76.00

35

50 MHz 8PSK [8]

113.66

52

50 MHz 16QAM [8]

151.83

70

50 MHz 32QAM [8]

188.90

87

50 MHz 64QAM [8]

239.81

110

50 MHz 128QAM [8]

283.06

130

50 MHz 256QAM [8]

322.15

148

56 MHz 4QAM class 2

82.16

37

56 MHz 8PSK class2

122.88

56

56 MHz 16QAM class 4

163.63

75

56 MHz 16QAM class 4 unified

165.65

76

56 MHz 32QAM class 4

200.83

92

56 MHz 64QAM class 5

258.77

119

56 MHz 128QAM class 5

305.93

141

140

User Manual 3DB19901AFAA Edition 01

Radio capacity, channeling and modulation


Table 2.3 MPT-HC/MPT-XP/MPT-MC Modem Profiles (Fixed and Adaptive Modulation) (Continued)
Modem profile

Net radio throughput (Mbit/s)

Number of E1

56MHz 128QAM class 5 SDH

314.22

2xSTM1

56MHz 256QAM class 6

348.19

160

Table 2.4 MPT-HC/MPT-XP/MPT-MC XPIC Modem Profiles (Fixed Modulation) [4] [7]
Modem profile

Net radio throughput (Mbit/s)

Number of E1

7MHz 64QAM class 5

31.42

14

7MHz 128QAM class 5

37.47

16

7MHz 256QAM class 6

42.22

19

14MHz 64QAM class 5

64.72

29

14MHz 128QAM class 5

76.61

34

14MHz 256QAM class 6

86.10

39

28MHz 64QAM class 5

132.65

60

28MHz 128QAM class 5

156.86

72

28MHz 128QAM class 5 SDH

158.53

1xSTM1

28MHz 256QAM class 6

173.47

79

40MHz 64QAM class 5

192.14

88

40MHz 128QAM class 5

226.68

104

40MHz 256QAM class 5

257.84

118

50MHz 64QAM class 5

240.63

110

50MHz 128QAM class 5

283.88

130

50MHz 256QAM class 5

322.89

148

56MHz 64QAM class 5

259.58

119

56MHz 128QAM class 5

306.85

141

56MHz 128QAM class 5 SDH

315.24

2xSTM1

56MHz 256QAM class 6

349.01

160

User Manual 3DB19901AFAA Edition 01

141

Radio capacity, channeling and modulation

Table 2.5 MPT-HC/MPT-XP/MPT-MC: XPIC Modem Profiles (Adaptive Modulation) [4]


Modem profile

Net radio throughput (Mbit/s)

Number of E1

7MHz QPSK class 2

9.88

7MHz 16QAM class 2

19.68

7MHz 32QAM class 2

24.38

10

7MHz 64QAM class 2

31.05

13

7MHz 128QAM class 2

36.66

16

7MHz 256QAM class 2

41.69

18

14MHz QPSK class 2

21.26

14MHz 16QAM class 2

42.31

19

14MHz 32QAM class 2

52.60

23

14MHz 64QAM class 2

66.73

30

14MHz 128QAM class 2

78.74

35

14MHz 256QAM class 2

89.57

40

28MHz QPSK class 2

45.22

20

28MHz 16QAM class 2

89.98

41

28MHz 32QAM class 2

111.81

51

28MHz 64QAM class 2

141.87

65

28MHz 128QAM class 2

167.38

76

28MHz 256QAM class 2

190.31

87

40MHz 64QAM class 5

192.14

88

40MHz 128QAM class 5

226.68

104

40MHz 256QAM class 5

257.84

118

50MHz 64QAM class 5

240.63

110

50MHz 128QAM class 5

283.88

130

50MHz 256QAM class 5

322.89

148

56MHz QPSK class 2

82.98

37

56MHz 16QAM class 2

164.97

75

56MHz 32QAM class 2

205.00

94

56MHz 64QAM class 2

260.04

119

142

User Manual 3DB19901AFAA Edition 01

Radio capacity, channeling and modulation


Table 2.5 MPT-HC/MPT-XP/MPT-MC: XPIC Modem Profiles (Adaptive Modulation) [4] (Continued)
Modem profile

Net radio throughput (Mbit/s)

Number of E1

56MHz 128QAM class 2

306.78

141

56MHz 256QAM class 2

348.86

160

Table 2.6 MPT-HC/MPT-XP/MPT-MC XPIC SDH Modem Profiles


Modem profile

Fixed /
Adaptive

Minimum
Modulation
scheme in
Adaptive
Modulation

Number of
STM1

Number of
E1 TDM2TDM

Number of
E1 TDM2ETH

Eth any
length (641518k) Mb/s

28MHz
128QAM SDH
Class 5

Fixed

NA

1xSTM-1

1.23

28MHz
256QAM Class
6

Fixed

NA

1xSTM-1

12

12

27.9

40 MHz
64QAM Class
5

Fixed/
Adaptive

64 QAM

1xSTM-1

15

15

33.84

40 MHz
128QAM Class
5

Fixed/
Adaptive

64 QAM

1xSTM-1

31

30

67.81

40 MHz
256QAM Class
5

Fixed/
Adaptive

64 QAM

1xSTM-1

44

43

95.5

56MHz
16QAM Class
4

Fixed/
Adaptive

16 QAM

1xSTM-1

9.30

56MHz
32QAM Class
4

Fixed/
Adaptive

16 QAM

1xSTM-1

22

21

47.51

56MHz
64QAM Class
5

Fixed/
Adaptive

16 QAM

1xSTM-1

47

45

100.69

56MHz
128QAM
(SDH) Class 5

Fixed

NA

1xSTM-1

72

69

153.91

User Manual 3DB19901AFAA Edition 01

143

Radio capacity, channeling and modulation


Table 2.6 MPT-HC/MPT-XP/MPT-MC XPIC SDH Modem Profiles
Modem profile

Fixed /
Adaptive

Minimum
Modulation
scheme in
Adaptive
Modulation

Number of
STM1

Number of
E1 TDM2TDM

Number of
E1 TDM2ETH

Eth any
length (641518k) Mb/s

56MHz
256QAM Class
6

Fixed

NA

1xSTM-1

88

84

187.01

56MHz
128QAM
(SDH) Class 5

Fixed

NA

2xSTM-1

1.09

56MHz
256QAM Class
6

Fixed

NA

2xSTM-1

15

15

34.19

Notes:
1.

Packet throughput booster technique: compression considering IPv6 packets


transported over Ethernet with inner and outer VLAN. Available from R 4.1.

2.

Packet throughput booster technique: compression considering IPv4 packets


transported over Ethernet with inner and outer VLAN. Available from R 4.1.

3.

Packet throughput booster technique: compression considering Ethernet frames with


inner and outer VLAN. Available from R 4.1.

4.

XPIC not available with MPT-MC.

5.

modem profile supported in adaptive modulation only (no support in fixed


modulation).

6.

modem profile support in adaptive modulation from R4.x & fixed modulation from
R5.x.

7.

32QAM FCM modem profile not available: use the adaptive modem profile, setting
max modulation scheme equal to 32QAM.

8.

50 MHz modem profile available at 23 Ghz for Mexican market.

2.2.3 MPT-HC-HQAM and MPT-XP-HQAM


The following tables provide modem profile information for MPT-HQAM ODUs.
Table 2.7 describes the modem profiles for fixed and adaptive modulation including XPIC,
Table 2.8 describes SDH modem profiles in fixed and adaptive modulation, and Table 2.9
describes High Gain fixed modulation modem profiles.

144

User Manual 3DB19901AFAA Edition 01

Radio capacity, channeling and modulation

Table 2.7 MPT-HC-HQAM / XP-HQAM Modem Profiles, including XPIC (Fixed and Adaptive
Modulation)
Modem profile

Net radio throughput (Mbit/s)

Number of E1

3.5MHz QPSK

4.5

3.5MHz 16QAM

9.9

3.5MHz 32QAM

12.6

3.5MHz 64QAM

16.0

3.5MHz 128QAM

17.6

3.5MHz 256QAM

20.4

7MHz QPSK

9.5

7MHz 16QAM

20.3

7MHz 32QAM

25.3

11

7MHz 64QAM [6]

32.2

14

7MHz 128QAM [6]

38.1

17

7MHz 256QAM [6]

43.8

20

7MHz 512QAM [4] [6]

47.1

20

7MHz 1024QAM [4] [6]

52.4

20

14 MHz QPSK

21.0

14 MHz 16QAM

42.3

19

14 MHz 32QAM

53.1

24

14 MHz 64QAM [6]

66.5

30

14 MHz 128QAM [6]

78.7

36

14MHz 256QAM [6]

90.8

41

14 MHz 512QAM [4] [6]

97.1

41

14 MHz 1024QAM [4] [6]

107.7

41

28MHz QPSK

44.8

20

28MHz 16QAM

86.1

39

28MHz 32QAM

111.1

51

28MHz 64QAM [6]

135.8

62

28MHz 128QAM [6]

160.7

74

User Manual 3DB19901AFAA Edition 01

145

Radio capacity, channeling and modulation


Table 2.7 MPT-HC-HQAM / XP-HQAM Modem Profiles, including XPIC (Fixed and Adaptive
Modulation) (Continued)
Modem profile

Net radio throughput (Mbit/s)

Number of E1

28MHz 256QAM [6]

185.6

85

28MHz 512QAM [4] [6]

199.7

85

28MHz 1024QAM [4] [6]

221.6

85

40MHz QPSK

61.2

28

40MHz 16QAM

123.3

56

40MHz 32QAM

154.4

71

40MHz 64QAM [6]

194.4

89

40MHz 128QAM [6]

229.9

106

40MHz 256QAM [6]

257.2

118

40MHz 512QAM [4] [6]

285.6

118

40MHz 1024QAM [4] [6]

310.2

118

50 MHz QPSK [7]

76.2

35

50 MHz 16QAM [7]

152.1

70

50 MHz 32QAM [7]

189.1

87

50 MHz 64QAM [7] [6]

240.2

110

50 MHz 128QAM [7] [6]

283.1

130

50 MHz 256QAM [7] [6]

322.4

148

50 MHz 512QAM [7] [4] [6]

362.4

148

50 MHz 1024QAM [7] [4] [6]

393.5

148

56 MHz QPSK

82.4

38

56 MHz 16QAM

165.8

76

56 MHz 32QAM

204.3

94

56 MHz 64QAM [6]

259.6

119

56 MHz 128QAM [6]

306.0

141

56 MHz 256QAM [6]

348.5

160

56MHz 512QAM [4] [6]

391.6

160

56MHz 1024QAM [4] [6]

425.3

160

146

User Manual 3DB19901AFAA Edition 01

Radio capacity, channeling and modulation

Table 2.8 MPT-HC-HQAM / XP-HQAM SDH Fixed and Adaptive Modulation Modem Profiles
Modem profile

Fixed /
Adaptive

Minimum
Modulation
scheme in
Adaptive
Modulation

Number of
STM1

Number of
E1 TDM2TDM

Number of
E1 TDM2ETH

Eth any
length (641518k) Mb/s

28MHz
128QAM
(SDH) [6]

Fixed/
Adaptive

128 QAM

1xSTM-1

4.31

28MHz
256QAM
(SDH) [6]

Fixed/
Adaptive

128 QAM

1xSTM-1

13

12

28.53

28MHz
512QAM
(SDH) [4] [6]

Adaptive

128 QAM

1xSTM-1

19

18

42.33

28MHz
1024QAM
(SDH) [4] [6]

Adaptive

128 QAM

1xSTM-1

29

28

63.73

40 MHz
64QAM

Fixed/
Adaptive

64 QAM

1xSTM-1

17

16

37.11

40 MHz
128QAM

Fixed/
Adaptive

64 QAM

1xSTM-1

33

32

71.70

40 MHz
256QAM

Fixed/
Adaptive

64 QAM

1xSTM-1

46

44

98.31

40 MHz
512QAM

Adaptive

64 QAM

1xSTM-1

59

57

126.05

40 MHz
1024QAM

Adaptive

64 QAM

1xSTM-1

70

67

150.01

56MHz
16QAM

Fixed/
Adaptive

16 QAM

1xSTM-1

9.30

56MHz
32QAM

Fixed/
Adaptive

16 QAM

1xSTM-1

22

21

47.51

56MHz
64QAM

Fixed/
Adaptive

16 QAM

1xSTM-1

47

45

100.69

56MHz
128QAM
(SDH)

Fixed/
Adaptive

16 QAM

1xSTM-1

72

69

153.90

56MHz
256QAM
(SDH)

Fixed/
Adaptive

16 QAM

1xSTM-1

89

86

190.25

User Manual 3DB19901AFAA Edition 01

147

Radio capacity, channeling and modulation


Table 2.8 MPT-HC-HQAM / XP-HQAM SDH Fixed and Adaptive Modulation Modem Profiles
Modem profile

Fixed /
Adaptive

Minimum
Modulation
scheme in
Adaptive
Modulation

Number of
STM1

Number of
E1 TDM2TDM

Number of
E1 TDM2ETH

Eth any
length (641518k) Mb/s

56MHz
512QAM
(SDH)

Adaptive

16 QAM

1xSTM-1

109

105

232.63

56MHz
1024QAM
(SDH)

Adaptive

16 QAM

1xSTM-1

125

120

265.72

56MHz
128QAM
(SDH) [6]

Fixed/
Adaptive

128 QAM

2xSTM-1

1.09

56MHz
256QAM
(SDH) [6]

Fixed/
Adaptive

128 QAM

2xSTM-1

17

16

37.44

56MHz
512QAM
(SDH) [4] [6]

Adaptive

128 QAM

2xSTM-1

37

36

79.81

56MHz
1024QAM
(SDH) [4] [6]

Adaptive

128 QAM

2xSTM-1

53

51

112.91

Table 2.9 MPT-HC-HQAM / XP-HQAM High Gain Fixed Modulation Modem Profiles
Modem profile

Net radio throughput (Mbit/s)

Number of E1

7MHz QPSK (High Gain)

6.2

14MHz QPSK (High Gain)

15.2

28MHz QPSK (High Gain)

32.2

14

40MHz QPSK (High Gain)

46.4

21

56MHz QPSK (High Gain)

58.4

26

Notes:

148

1.

Packet throughput booster technique: compression considering IPv6 packets


transported over Ethernet with inner and outer VLAN. Available from R 4.1.

2.

Packet throughput booster technique: compression considering IPv4 packets


transported over Ethernet with inner and outer VLAN. Available from R 4.1.
User Manual 3DB19901AFAA Edition 01

Radio capacity, channeling and modulation

3.

Packet throughput booster technique: compression considering Ethernet frames with


inner and outer VLAN. Available from R 4.1.

4.

Only available in Adaptive Modulation.

5.

modem profile supported in adaptive modulation only (no support in fixed


modulation).

6.

Modem profile also available in XPIC (Fixed and Adaptive).

7.

50 MHz modem profile available at 23 Ghz for Mexican market.

2.2.4 MPT-HLS
Table 2.10 describes modem profiles for the MPT-HLS.
Table 2.10 MPT-HLS modem profiles (Fixed and Adaptive modulation)
Modem profile

Net radio throughput


(Mbit/s)

Number of E1

Number of STM-1

28 MHz QPSK class 2

44.49

20

28 MHz 32QAM class 4

110.66

51

28 MHz 64QAM class 5

131.91

60

28 MHz 128QAM class 5

157.74

72

28 MHz 256QAM class 6

181.10

83

28 MHz 512QAM class 6

204.68

94

28 MHz 1024QAM class 6

225.26

103

40 MHz 64QAM class 5

185.12

85

40 MHz 128QAM class 5

214.92

99

40 MHz 256QAM class 6

246.67

113

40 MHz 512QAM class 6

277.169

127

40 MHz 1024QAM class 6

305.346

140

56 MHz QPSK class 2

82.77

38

56 MHz 16QAM class 4

165.67

76

56 MHz 32QAM class 4

205.84

95

56 MHz 64QAM class 5

266.42

122

56 MHz 128QAM class 5

316.66

146

User Manual 3DB19901AFAA Edition 01

149

Standard Features
Table 2.10 MPT-HLS modem profiles (Fixed and Adaptive modulation) (Continued)
Modem profile

Net radio throughput


(Mbit/s)

Number of E1

Number of STM-1

56 MHz 256QAM class 6

362.19

167

56 MHz 512QAM class 6

410.177

189

56 MHz 1024QAM class 6

451.113

208

2.3 Standard Features


More radio and site scalability and flexibility for installation teams:

150

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, 3G and LTE network compatible

Intelligent indoor nodal unit that supports up to 18 outdoor units, expandable to 54


with the stacking configuration (with MPT)

Flexible aggregate capacity sharing between E1, STM-1 and Ethernet

Adaptive packet transport that improves performance for priority services

Output power agility

ATPC

Adaptive Modulation

XPIC

Packet-based internal cross-connect

E1 MEF8 encapsulation

E3 encapsulation

STM-1 encapsulation

EoSDH feature

ATM over PW according to RFC 4717

L2 Radio and Ethernet LAGs

L1 Radio LAG

Ethernet Ring

Ethernet First Mile Operation Administration and Maintenance

Electrical and optical GE interfaces

User Manual 3DB19901AFAA Edition 01

Radio Configurations

Software-based configuration

Multiservice Switching Capacity greater than 16 Gb/s

No single point of failure

TACACS+ access control to the NE

2.4 Radio Configurations


2.4.1 Split mount (short haul) radio configurations: ODU300,
MPT-HC/HC-HQAM, MPT-MC, MPT-XP/XP-HQAM

1+0

1+1 Hot-Standby (HSB)

two types of couplers for ODU300:

3 dB/3 dB balanced coupler

1.5 dB/6.0 dB unbalanced coupler

two types of couplers for MPT-HC/HC-HQAM/MC/XP/XP-HQAM:

3 dB/3 dB balanced coupler

1 dB/10 dB unbalanced coupler

1+1 Hot-Standby Space Diversity (HSB/SD) (no coupler)

1+1/2x(1+0) Frequency Diversity (FD) (co-polar)

1+1/2x(1+0) Frequency Diversity (FD) (cross-polar)

1+0/1+1 XPIC (with MPT-HC/HC-HQAM/XP/XP-HQAM)

The following notes apply:

MPT-HC/HC-HQAM/XP/XP-HQAM configurations are supported by Core-E,


EASv1 (P8ETH), EASv2, MPTACC, MSS-1 unit electrical and optical Ethernet
ports and MSS-O shelf electrical Ethernet ports.

MPT-MC configurations are supported by Core-E, EASv2, MPTACC, MSS-1 unit,


and MSS-O shelf electrical Ethernet ports.

ODU300 configurations are supported by the MD300 card only.

The 1+1 configuration with MPT-MC does not require an interconnection cable
between the two ODUs.

The 1+1 configuration with MPT-HC/HC-HQAM or MPT-XP/XP-HQAM can be


implemented with or without an interconnection cable between the two ODUs.

User Manual 3DB19901AFAA Edition 01

151

Typical System Configurations

MPT-HC/HC-HQAM can be configured in 1+1 configuration with an XP/XPHQAM. The 2 MPT can be interconnected by using a specific cord.

In a 1+1 radio configuration with EASv2, the MPTs must be connected to ports
belonging to different EASv2 cards on the same row.

XPIC with MPT-HC or MPT-XP requires an XPIC module and is implemented with
an XPIC cable between the two ODUs.

MPT-HC-HQAM or MPT-XP-HQAM have an integrated, on-board XPIC function


that is enabled by software upgrade using a dedicated XPIC RTU. No additional
hardware module is required. An XPIC cable is required between the two ODUs.

2.4.2 All indoor (long haul) radio configurations: MPT-LH


using MPT-HLS

1+0

1+0 SD (using diversity receiver)

1+1 Hot-Standby (HSB)

RF transmit switch

two types of couplers

3 dB/3 dB balanced coupler

1 dB/10 dB unbalanced coupler

1+1 Hot-Standby Space Diversity (HSB/SD) (no coupler)

1+1/2x(1+0) Frequency Diversity (FD) (co-polar)

1+1/2x(1+0) Frequency Diversity (FD) (cross-polar)

1+0/1+1 XPIC

Note: MPT-HLS configurations are supported by Core-E and EASv2 card optical Ethernet
ports only.

Note: The 1+1 configuration is implemented with an interconnection RPS cable between
the two MPT-HLSs.

Note: XPIC with MPT-HLS requires an XPIC license.

2.5 Typical System Configurations


152

User Manual 3DB19901AFAA Edition 01

Typical System Configurations

PDH/ATM Over Ethernet Packet Node - Mapping of 32 E1 and 16 E1 ATM on


Ethernet (Figure 2.41)

PDH/SDH/ATM and Ethernet Terminal Packet Transport 32 E1, 2xSTM-1 and 16 E1


ATM Access, 1 Radio Direction (Figure 2.42)

PDH/SDH/ATM and Ethernet Add/Drop Packed Node-Ethernet and 32 E1, 2xSTM1 and 16 E1 ATM Local Access, 1 Back Link, 1 Haul Link (Figure 2.43)

PDH/SDH/ATM and Ethernet Terminal Packet Node-Ethernet and 32 E1, 2xSTM-1


and 16 E1 ATM Local Access, 2 Back Links (Figure 2.44)

PDH/SDH/ATM and Ethernet Add/Drop Packet Node-Ethernet and 32 E1, 2xSTM1 and 16 E1 ATM Local Access, 1 Back Link and 2 Haul Links (Figure 2.45)

PDH/SDH/ATM and Ethernet Add/Drop Packet Node-Ethernet and 32 E1, 2xSTM1 and 16 E1 ATM Local Access, 2 Haul Links and 2 Back Links (Figure 2.46)

Note: Radio LAG and Ethernet LAGs can be created to increase the capacity and
availability.

Figure 2.41 PDH/ATM Over Ethernet Packet Node - Mapping of 32 E1 and 16 E1 ATM
on Ethernet

User Manual 3DB19901AFAA Edition 01

153

Typical System Configurations


Figure 2.42 PDH/SDH/ATM and Ethernet Terminal Packet Transport 32 E1, 2xSTM1 and 16 E1 ATM Access, 1 Radio Direction

Figure 2.43 PDH/SDH/ATM and Ethernet Add/Drop Packed Node-Ethernet and 32 E1, 2xSTM-1 and
16 E1 ATM Local Access, 1 Back Link, 1 Haul Link

154

User Manual 3DB19901AFAA Edition 01

Typical System Configurations


Figure 2.44 PDH/SDH/ATM and Ethernet Terminal Packet Node-Ethernet and 32 E1, 2xSTM-1 and
16 E1 ATM Local Access, 2 Back Links

User Manual 3DB19901AFAA Edition 01

155

Typical System Configurations


Figure 2.45 PDH/SDH/ATM and Ethernet Add/Drop Packet Node-Ethernet and 32
E1, 2xSTM-1 and 16 E1 ATM Local Access, 1 Back Link and 2 Haul Links

Figure 2.46 PDH/SDH/ATM and Ethernet Add/Drop Packet Node-Ethernet and 32


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

156

User Manual 3DB19901AFAA Edition 01

Environmental and Electrical Characteristics

2.6 Environmental and Electrical Characteristics

System Parameters

ODU300

MPT-HLS

Cable length and power consumption of MPT-HC/HC-HQAM/XP/XP-HQAM using


MPT Power Unit or MPT Extended Power Unit

Radio performances

Power Injector general characteristics

General characteristics (MPT power unit)

Maximum allowed cable lengths for MPT Power Unit

General characteristics (MPT extended power unit)

Maximum allowed cable length for MPT Extended Power Unit

2.6.1 System Parameters


Table 2.11 provides general system information for the 9500 MPR and for the MPTs.
For part numbers and T-R spacing information for outdoor MPTs, see the 9500 MPR
Frequency Plan for MPT Outdoor Transceivers.
Table 2.11 System parameters
General with 9500 MPR
Operating Frequency Range

5.8 - 80 GHz

Max Ethernet throughput

from 10 up to 451.113 Mbit/s (2 Gb/s for 80 GHz)

Bandwidth

up to 56 MHz (250 / 500 MHZ for 80GHz)

Modulation Options in FCM

QPSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM, 512 QAM,
1024 QAM

Adaptive Modulation

QPSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM, 512 QAM,
1024 QAM

General with ODU300


Operating Frequency Range

6 - 38 GHz

Max Ethernet throughput

from 10 up to 310 Mbit/s

Modulation Options in FCM

QPSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM

User Manual 3DB19901AFAA Edition 01

157

Environmental and Electrical Characteristics


Table 2.11 System parameters (Continued)
Adaptive Modulation

QPSK, 16 QAM, 64 QAM,

General with MPT-HC


Operating Frequency Range

5.8 - 38 GHz

Max Ethernet throughput

349 Mbit/s

Bandwidth

up to 56 MHz

Modulation Options in FCM

QPSK, 8PSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM

Adaptive Modulation

QPSK, 8PSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM

General with MPT-XP


Operating Frequency Range

6 - 8 GHz

Max Ethernet throughput

349 Mbit/s

Bandwidth

up to 56 MHz

Modulation Options in FCM

QPSK, 8PSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM

Adaptive Modulation

QPSK, 8PSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM

General with MPT-MC


Operating Frequency Range

6 - 38 GHz

Max Ethernet throughput

349 Mbit/s

Bandwidth

up to 56 MHz

Modulation Options in FCM

QPSK, 8PSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM

Adaptive Modulation

QPSK, 8PSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM

General with MPT-HLS


Operating Frequency Range

4-13 GHz

Max Ethernet throughput

451.113 Mbit/s

Bandwidth

up to 56 MHz

Modulation Options in FCM

QPSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM, 512 QAM,
1024 QAM

Adaptive Modulation

QPSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM, 512 QAM,
1024 QAM

General with MPT-HC-HQAM


Operating Frequency Range

5.8 - 38 GHz

Max Ethernet throughput

425 Mbit/s

158

User Manual 3DB19901AFAA Edition 01

Environmental and Electrical Characteristics


Table 2.11 System parameters (Continued)
Bandwidth

up to 56 MHz

Modulation Options in FCM

QPSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM, 512 QAM,
1024 QAM

Adaptive Modulation

QPSK, 8PSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM, 512
QAM, 1024 QAM

General with MPT-XP-HQAM


Operating Frequency Range

6 - 8 GHz

Max Ethernet throughput

425 Mbit/s

Bandwidth

up to 56 MHz

Modulation Options in FCM

QPSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM, 512 QAM,
1024 QAM

Adaptive Modulation

QPSK, 8PSK, 16 QAM, 32 QAM, 64 QAM, 128 QAM, 256 QAM, 512
QAM, 1024 QAM

Radio Path Protection Options


Non Protected, 1+0
Protected Hot Standby, 1+1
Space Diversity, 1+1
Frequency Diversity, 1+1
N x (1+0), not protected
N x (1+1), protected
XPIC 1+0/1+1 (with MPT-HC/HCHQAM/XP/XP-HQAM)
Radio LAG with four radio
channels (with MPT-HC/HCHQAM/MC/XP/XP-HQAM)
MSS-4/8 Power supply
Input voltage range

-40.5 to -57.6 Vdc

The input voltage range can be


set to from -57 to -60 Vdc
without any damage, but with
no guaranteed performance

+19 to +36 Vdc

The optional +24 Vdc/-48 Vdc


converter module has to be
installed for +24 Vdc office
applications

MSS-1 Power Supply

User Manual 3DB19901AFAA Edition 01

159

Environmental and Electrical Characteristics


Table 2.11 System parameters (Continued)
Input voltage range

-38.4 to -57.6 Vdc

The supported input voltage


range is from +20 to +28.8 Vdc
and -19.2 to -72 Vdc. Input
voltage polarity is determined
by reference cable connection
with respect to ground.

(-48 Vdc office power)


-20 to -72 Vdc
(-60 Vdc office power)
+19.2 to +28.8 Vdc
(+24 Vdc office power)
MSS-O Power Supply
Electrical parameters

AC input voltage 110/230 Vac

Line frequency 60/50 Hz


PFoE output voltage 50 to
57 Vdc
Typical 54 Vdc
PFoE output power 2x 55 W
maximum or
1x 100 W maximum
Standards Compliance
EMC

MSS-8/MSS-4/MSS-1

EN 301 489-1, EN 301 489-4


EN 55022 Class B)

Operation

ODU300/MPT

ETS 300 019, Class 4.1

Operation

MSS-8/MSS-4/MSS-1

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

160

ODU300/MPT

IEC 60529 (IPX6)

User Manual 3DB19901AFAA Edition 01

Environmental and Electrical Characteristics


Table 2.11 System parameters (Continued)
Environmental
Operating Temperature

MSS-4 with FAN (still air)


guaranteed (*)

-40 to +55 C

MSS-4 forced air guaranteed


(*)

-40 to +65 C

MSS-8 guaranteed (*)

-40 to +65 C

MSS-1 still air guaranteed

-40 to +55 C

MSS-1 forced air guaranteed

-40 to +65 C

ODU300/MPT guaranteed

-33 to +55 C

MSS-O

40 to +46 C + Solar Load


Compliant with GR3108 Class 4

Environmental compliance

MSS-O

Product Full RoHs6


IP 67

Dimensions (mm)

MSS-O

345 x 209.5 x 65

Weight (kg)

MSS-O

4.2

Start up temperature from low

ODU300/MSS-1

-20C

MPT

-45C

MSS-8/MSS-4/MSS-1/MSS-O
Guaranteed

0 to 95%, non-condensing

ODU300/MPT Guaranteed

0 to 100%

temperature
Humidity

Management
Protocol

SNMP

Interface, electrical

Ethernet 10/100/1000 Base-T (RJ45)

Local/remote Configuration and

JUSM

Support Tool
Routing Protocols supported

Static routing and dynamic routing (OSPF)

TMN In-band

2 interfaces

Network Management

Alcatel-Lucent 1350 OMS


Alcatel-Lucent 1352 Compact
Alcatel-Lucent 5620SAM

User Manual 3DB19901AFAA Edition 01

161

Environmental and Electrical Characteristics

(*) if equipped with P8ETH (EASv1) or with +24 VDC / -48 VDC Converter, temperature
range is restricted to : -5 to +55 degrees

2.6.2 ODU300
2.6.2.1 6 to 15 GHz
Table 2.12 ODU300: 6 to 15 GHz characteristics
L6/U6 GHz

7 GHz

8 GHz

10 GHz

11 GHz

13 GHz

15 GHz

Frequency Range, GHz

5.925 6.425
6.425 7.11

7.125 7.9

7.725 8.5

10.0 10.68

10.7 11.7

12.75 13.25

14.4 15.35

T-R Spacings supported,


MHz

252.04,

119, 126,
151.614,
266,
311.32

91, 230,
143.5,
350

490, 530

266

340

154, 161,
168, 196,
245

315,
420,
490,
644, 728

Maximum Tuning Range


(dependent upon T-R
spacing), MHz

56

56

140

165

165

84

245

Waveguide Type

R70
(WR137)

R84
(WR112)

R84
(WR112)

R100
(WR90)

R100
(WR90)

R120
(WR75)

R140
(WR62)

Flange Type

UDR70

UDR84

UDR84

UDR100

UDR100

UBR120

UBR140

Mating Flange Type

PDR70 or
CDR70

PDR84 or
CDR84

PDR84 or
CDR84

PDR100
or
CDR100

PDR100
or
CDR100

PBR120
or
CDR120

PBR140
or
CBR140

System

Antenna Interface

Guaranteed power
consumption

44 W

2.6.2.2 18 to 38 GHz

162

User Manual 3DB19901AFAA Edition 01

Environmental and Electrical Characteristics

Table 2.13 ODU300: 18 to 38 GHz characteristics


18 GHz

23 GHz

25 GHz

28 GHz

32 GHz

38 GHz

Frequency Range, GHz

17.7 19.7

21.2 23.632

24.52 26.483

27.5 29.5

31.833.4

37.0 39.46

T-R Spacings supported, MHz

1010,
1092.5

1008,
1200,
1232

1008

1008

812

1260

Maximum Tuning Range (dependent


upon T-R spacing), MHz

380

370

360

360

370

340

Waveguide Type

R220
(WR42)

R220
(WR42)

R220
(WR42)

R320
(WR28)

R320
(WR28)

R320
(WR28)

Flange Type

UBR220

UBR220

UBR220

UBR320

UBR321

UBR320

Mating Flange Type

PBR220

PBR220

PBR220

PBR320

PBR321

PBR320

Guaranteed power consumption

30 W

System

Antenna Interface

2.6.3 MPT-HLS
Table 2.14 MPT-HLS: 4 to 13 GHz characteristics
L4 GHz

U4 GHz

L6 GHz

U6 GHz

7 GHz

8 GHz

11 GHz

13 GHz

Frequency Range, GHz

5.930 6.420

6.4207.115

7.125 7.9

7.725 8.5

10.7 11.7

12.75 13.25

T-R Spacings supported,


MHz

252.04

340

154;

119;
126;
151.61
4; 208;
213,5;
266;
294.44
;
305.56
;
311.32

490;

266

System

160;
161;
168;
196;
245

530

Antenna Interface

User Manual 3DB19901AFAA Edition 01

163

Environmental and Electrical Characteristics


Table 2.14 MPT-HLS: 4 to 13 GHz characteristics (Continued)
L4 GHz

U4 GHz

L6 GHz

U6 GHz

7 GHz

8 GHz

11 GHz

13 GHz

WR137

WR137

WR112

WR112

WR75

WR62

System

Waveguide Type
Input voltage range

-48 to +60 Vdc 20%

Maximum power
consumption - STD

82 W without SD

Maximum power
consumption - HP

91 W without SD

95 W with SD
105 W with SD

2.6.4 Cable length and power consumption of MPT-HC/HCHQAM/XP/XP-HQAM using MPT Power Unit or MPT Extended
Power Unit
For MPT-XP system power consumption with the MPT Extended Power Unit, refer to
Table 2.15.
For MPT-HC system power consumption with the MPT Power Unit, refer to Table 2.16.
Table 2.15 MPT-XP power system: power requirements
Cable type

Cable Length

Ethernet UTP 5E
1AC016760006

0m

20 m

20 - 40m

Coaxial Cable
1AC001100022

0m

56 m

56 - 168 m

168 - 280 m

Coaxial Cable
1AC041350001

0m

25 m

25 - 75 m

75 - 125 m

Number
of
MPT ODU

Input Voltage for


MPT Extended
Power Unit

+24
(Vdc)

-48
(Vdc)

+24
(Vdc)

-48
(Vdc)

+24
(Vdc)

-48
(Vdc)

+24
(Vdc)

-48
(Vdc)

1 MPT

MPT-XP + XPIC

81.0W

81.0W

81.0W

81.0W

81.0W

81.0W

81.0W

81.0W

Cable Losses

0.0W

0.0W

2.0W

2.0W

6.6W

6.6W

12.7W

12.7W

Extended Power
Unit

11.0W

15.4W

11.3W

15.8W

12.0W

16.7W

12.8W

17.8W

Total power
consumption

92.0W

96.4W

94.3W

98.8W

99.6W

104.3W

106.5W

111.5W

164

User Manual 3DB19901AFAA Edition 01

Environmental and Electrical Characteristics


Table 2.15 MPT-XP power system: power requirements

Number
of
MPT ODU

2 MPT

Cable type

Cable Length

Ethernet UTP 5E
1AC016760006

0m

20 m

20 - 40m

Coaxial Cable
1AC001100022

0m

56 m

56 - 168 m

168 - 280 m

Coaxial Cable
1AC041350001

0m

25 m

25 - 75 m

75 - 125 m

Input Voltage for


MPT Extended
Power Unit

+24
(Vdc)

-48
(Vdc)

+24
(Vdc)

-48
(Vdc)

+24
(Vdc)

-48
(Vdc)

+24
(Vdc)

-48
(Vdc)

MPT-XP-HQAM +
XPIC

74.0W

74.0W

74.0W

74.0W

74.0W

74.0W

74.0W

74.0W

Cable Losses

0.0W

0.0W

2.0W

2.0W

6.6W

6.6W

12.7W

12.7W

Extended Power
Unit

11.0W

15.4W

11.3W

15.8W

12.0W

16.7W

12.8W

17.8W

Total power
consumption

85.0W

89.4W

87.3W

91.8W

92.6W

97.3W

99.5W

104.5W

MPT-XP + XPIC

162W

162W

162W

162W

162W

162W

162W

162W

Cable Losses

0.0W

0.0W

4.0W

4.0W

13.2W

13.2W

25.4W

25.4W

Extended Power
Unit

22.0W

30.8W

22.6W

31.6W

24W

33.4W

25.6W

35.6W

Total power
consumption

184.0W

192.8W

188.6W

197.6W

199.2W

208.6W

213.0W

223.0W

MPT-XP-HQAM +
XPIC

148W

148W

148W

148W

148W

148W

148W

148W

Cable Losses

0.0W

0.0W

4.0W

4.0W

13.2W

13.2W

25.4W

25.4W

Extended Power
Unit

22.0W

30.8W

22.6W

31.6W

24W

33.4W

25.6W

35.6W

Total power
consumption

170.0W

178.8W

174.6W

183.6W

185.2W

194.6W

199.0W

209.0W

(MPR-e only)

(MPR-e only)

User Manual 3DB19901AFAA Edition 01

165

Environmental and Electrical Characteristics

Table 2.16 MPT-HC power system: power requirements


Cable type
P/N

Coaxial Cable 1AC001100022

Coaxial Cable
1AC041350001

Cable Length

0 - 100 m

100 - 200 m

200 - 300 m

300 - 440 m

0 - 100 m

100 - 190 m

Number
of MPT
ODU

Input Voltage for


MPT Power Unit

-38.4
(Vdc)

38.4 (Vdc)

38.4 (Vdc)

38.4 (Vdc)

38.4
(Vdc)

38.4 (Vdc)

1 MPT

MPT-HC + XPIC

47.0 W

47.0 W

47.0 W

47.0 W

47.0 W

47.0 W

Cable Losses

1.9 W

4.3 W

7.2 W

13.1 W

4.7 W

11.5 W

Power Unit

2.0 W

2.0 W

2.0 W

2.0 W

2.0 W

2.0 W

Total power
consumption

50.9 W

53.3 W

56.2 W

62.1 W

53.7 W

60.5 W

MPT-HC-HQAM +
XPIC

40.5 W

40.5 W

40.5 W

40.5 W

40.5 W

40.5 W

Cable Losses

1.9 W

4.3 W

7.2 W

13.1 W

4.7 W

11.5 W

Power Unit

2.0 W

2.0 W

2.0 W

2.0 W

2.0 W

2.0 W

Total power
consumption

44.4 W

46.8 W

49.7 W

55.6 W

47.2 W

54.0 W

MPT-HC + XPIC

94.0 W

94.0 W

94.0 W

94.0 W

94.0 W

94.0 W

Cable Losses

3.8 W

8.6 W

14.4 W

26.2 W

9.4 W

23.0 W

Power Unit

4.0 W

4.0 W

4.0 W

4.0 W

4.0 W

4.0 W

Total power
consumption

101.8 W

106.6 W

112.4 W

124.2 W

107.4 W

121.0 W

MPT-HC-HQAM +
XPIC

81.0 W

81.0 W

81.0 W

81.0 W

81.0 W

81.0 W

Cable Losses

3.8 W

8.6 W

14.4 W

26.2 W

9.4 W

23.0 W

Power Unit

4.0 W

4.0 W

4.0 W

4.0 W

4.0 W

4.0 W

Total power
consumption

88.8 W

93.6 W

99.4 W

111.2 W

94.4 W

108.0 W

(MPR-e only)

(MPR-e only)

2 MPT

(MPR-e only)

(MPR-e only)

166

User Manual 3DB19901AFAA Edition 01

Environmental and Electrical Characteristics


Table 2.16 MPT-HC power system: power requirements

Number
of MPT
ODU

3 MPT

Cable type
P/N

Coaxial Cable 1AC001100022

Coaxial Cable
1AC041350001

Cable Length

0 - 100 m

100 - 200 m

200 - 300 m

300 - 440 m

0 - 100 m

100 - 190 m

Input Voltage for


MPT Power Unit

-38.4
(Vdc)

38.4 (Vdc)

38.4 (Vdc)

38.4 (Vdc)

38.4
(Vdc)

38.4 (Vdc)

MPT-HC + XPIC

141.0 W

141.0 W

141.0 W

141.0 W

141.0 W

141.0 W

Cable Losses

5.7 W

12.9 W

21.6 W

39.3 W

14.1 W

34.5 W

Power Unit

6.0 W

6.0 W

6.0 W

6.0 W

6.0 W

6.0 W

Total power
consumption

152.7 W

159.9 W

168.6 W

186.3 W

161.1 W

181.5 W

MPT-HC-HQAM +
XPIC

121.5 W

121.5 W

121.5 W

121.5 W

121.5 W

121.5 W

Cable Losses

5.7 W

12.9 W

21.6 W

39.3 W

14.1 W

34.5 W

Power Unit

6.0 W

6.0 W

6.0 W

6.0 W

6.0 W

6.0 W

Total power
consumption

133.2 W

140.4 W

149.1 W

166.8 W

141.6 W

162.0 W

MPT-HC + XPIC

188.0 W

188.0 W

188.0 W

188.0 W

188.0 W

188.0 W

Cable Losses

7.6 W

17.2 W

28.8 W

52.4 W

18.8 W

46.0 W

Power Unit

8.0 W

8.0 W

8.0 W

8.0 W

8.0 W

8.0 W

Total power
consumption

203.6 W

213.2 W

224.8 W

248.4 W

214.8 W

242.0 W

MPT-HC-HQAM +
XPIC

162.0 W

162.0 W

162.0 W

162.0 W

162.0 W

162.0 W

Cable Losses

7.6 W

17.2 W

28.8 W

52.4 W

18.8 W

46.0 W

Power Unit

8.0 W

8.0 W

8.0 W

8.0 W

8.0 W

8.0 W

Total power
consumption

177.6 W

187.2 W

198.8 W

222.4 W

188.8 W

216.0 W

(MPR-e only)

(MPR-e only)

4 MPT

(MPR-e only)

(MPR-e only)

2.6.5 Radio performances


User Manual 3DB19901AFAA Edition 01

167

Environmental and Electrical Characteristics

The radio performances are provided in the 9500 MPR Frequency Plan for MPT Outdoor
Transceivers.

2.6.6 Power Injector general characteristics


Table 2.17 Power Injector general characteristics
Power Injector

Input Voltage range

-38.4 to -57.6 Vdc

Standards Compliance (Power Injector)


EMC

EN 301 489-1, EN 301 489-4, EN 55022 Class B

Stationary use

ETS 300 019 1-3, Class 3.2

Storage

ETS 300 019 2-1, Class 1.2

Transportation

ETS 300 019 2-2, Class 2.3

Safety

EN 60950

Environmental
Operating Temperature

-40 to +65 C

(Guaranteed)
Humidity

0 to 95%, non condensing

(Guaranteed)

2.6.7 General characteristics (MPT power unit)


Table 2.18 General characteristics (MPT power unit)
Standards Compliance (MPT Power Unit)

EMC

EN 301 489-1, GR-1089 Class A

Storage

ETS 300 019, Class 1.2, GR-3108

Transportation

ETS 300 019 1-2, Class 2.3, GR-3108-CORE

Safety

EN 60950, UL-60950

Environmental

168

User Manual 3DB19901AFAA Edition 01

Environmental and Electrical Characteristics


Table 2.18 General characteristics (MPT power unit) (Continued)
Standards Compliance (MPT Power Unit)

Operating Temperature

-40 to +65 C

(Guaranteed)
Start up temperature from
low temperature

-40 C

Humidity

0 to 95%

(Guaranteed)

2.6.8 Maximum allowed cable lengths for MPT Power Unit


Table 2.19 Maximum allowed cable lengths for MPT Power Unit
Cable type

Coaxial cable
1AC001100022
Power only, Data
optical cable

Coaxial cable
1AC041350001
Power only, data
optical cable

Configuration

Required power

Maximum length

Maximum length

MPT-HC (*)

42.0 W

510 m

230 m

MPT-HC with XPIC (*)

48.0 W

435 m

200 m

MPT-HC -HQAM (*)

39.5 W

550 m

255 m

MPT-HC-HQAM with XPIC (*)

40.5 W

535 m

245 m

(*) equipped with SFP

2.6.9 General characteristics (MPT extended power unit)


The MPT Extended Power Unit is an indoor device to be installed in a 19/21 rack.
Table 2.20 General characteristics (MPT extended power unit)
Standards Compliance (Power Extractor)

EMC

EN 301 489-1, GR-1089 Class A

Storage

ETS 300 019, Class 1.2, GR-3108

Transportation

ETS 300 019 1-2, Class 2.3, GR-3108-CORE

User Manual 3DB19901AFAA Edition 01

169

Environmental and Electrical Characteristics


Table 2.20 General characteristics (MPT extended power unit) (Continued)
Standards Compliance (Power Extractor)

Safety

EN 60950, UL-60950

Environmental
Operating Temperature

-40 to +55 C

(Guaranteed)
Start up temperature from
low temperature

-40 C

Humidity

0 to 95%

(Guaranteed)

2.6.10 Maximum allowed cable length for MPT Extended


Power Unit
Table 2.21 provides the maximum cable lengths for use with an MPT Extended Power
Unit. The use of an additional external lightning arrestor will reduce the cable length by 10
m.
Table 2.21 Maximum allowed cable length for MPT Extended Power Unit
Cable type

Ethernet UTP
5E with outer
screen and
braid. Power
and Data on
Ethernet cable

Ethernet UTP
5E with outer
screen and
braid. Power
only, Data
optical cable

Coaxial cable
1AC001100022
Power only,
Data optical
cable

Coaxial cable
1AC041350001
Power only,
Data optical
cable

Configuration

Power
requirement

Maximum
length

Maximum
length

Maximum
length

Maximum
length

MPT-HC (*)

42.0 W

100 m

400 m

1100 m

500 m

MPT-HC with XPIC (*)

48.0 W

100 m

350 m

1000 m

440 m

MPT-XP (*)

77.0 W

40 m

155 m

480 m

280 m

MPT-XP with XPIC (*)

83.0 W

40 m

115 m

360 m

200 m

MPT-HC-HQAM (*)

39.5 W

100 m

440 m

1700 m

790 m

MPT-HC-HQAM with
XPIC (*)

40.5 W

100 m

430 m

1600 m

770 m

MPT-XP-HQAM (*)

75.0 W

40 m

170 m

650 m

300 m

170

User Manual 3DB19901AFAA Edition 01

Parts Lists
Table 2.21 Maximum allowed cable length for MPT Extended Power Unit (Continued)
Cable type

Ethernet UTP
5E with outer
screen and
braid. Power
and Data on
Ethernet cable

Ethernet UTP
5E with outer
screen and
braid. Power
only, Data
optical cable

Coaxial cable
1AC001100022
Power only,
Data optical
cable

Coaxial cable
1AC041350001
Power only,
Data optical
cable

Configuration

Power
requirement

Maximum
length

Maximum
length

Maximum
length

Maximum
length

MPT-XP-HQAM with
XPIC (*)

76.0 W

40 m

165 m

620 m

290 m

(*) equipped with SFP

2.7 Parts Lists


2.7.1 Indoor items
Table 2.22 MSS item codes
Name

Code

Remarks

MSS-8 slot shelf

3DB18485ABXX

MSS-8 slot shelf HS

3DB18485CAXX

High speed MSS-8 shelf

MSS-4 slot shelf

3DB18219ADXX

If the FAN-1 module is to be used the kit 3DB18835AAXX


must be equipped.

MSS-1 unit

3DB19015AAXX

MSS-O shelf

3DB19139AAAA

Core-E Card

3DB18326ACXX

Fan Card

3DB18134BBXX

To be used in MSS-8

Enhanced Fan Alarm Card

3EM23911AAXX

To be used in MSS-8

FAN1 Module

3DB18218ADXX

To be used in MSS-4

STM-1 Access Card

3DB18735AAXX

Up to 2 STM-1 signals

E1 Access Card

3DB18126AEXX

Up to 32 E1 TDM stream

User Manual 3DB19901AFAA Edition 01

Can be installed indoor or outdoor

171

Parts Lists
Table 2.22 MSS item codes (Continued)
Name

Code

Remarks

EAS Card

3DB18206ACXX

Up to 8 Ethernet traffic interfaces. For the last four


interfaces the dedicated SFP must be installed.

EASv2 Card

3DB19017ABXX

Up to 8 Ethernet traffic interfaces. For the last four


interfaces the dedicated SFP must be installed. Provides
PFoE to up to four MPTs.

ASAP Card

3DB18602AAXX

Up to 16 E1 streams with ATM cells

AUX peripheral Card

3DB18236ABXX

Modem 300 Card

3DB18136AEXX

To interface the ODU300 to be used with 56 MHz


bandwidth (no adaptive modulation)

Modem 300EN Card

3DB18538ACXX

To interface the ODU300 to be used with bandwidth up to


28 MHz (with or without adaptive modulation)

MPT Access Card (with


PFoE)

3DB18634ABXX

To interface one or two MPT-HC/MPT-XP or MPT-MC or one


MPT-HC/MPT-XP and one MPT-MC

+24 Vdc/-48 Vdc


Converter Card

3DB18862AAXX

Two converters on the card for +24 Vdc office applications

+24 Vdc/-48 Vdc


Converter Card

3DB18863ABXX

One converter on the card for +24 Vdc office applications

+24 Vdc/-48 Vdc


Converter

3DB18764AAXX

To replace a failed converter on the +24 Vdc/

Front plate

3DB18163ABXX

SFP plug-in STM-1 L1.1

1AB194670005/
3CC50166AAAA

Can be installed in the STM-1 Access card

SFP plug-in STM-1 S1.1

1AB194670007/
3CC50165AAAA

Can be installed in the STM-1 Access card

SFP plug-in STM-1 Copper

1AB210170001

Can be installed in the STM-1 Access card

SDH electrical SFP

1AB210170001

Can be installed in the STM-1 Access card

SFP plug-in 1000Base-Lx

1AB383760002/
3CC50168AAAA

Can be installed in the Core-E card, EAS card, EASv2 card,


MPT Access card, MSS-1, or MSS-O

SFP plug-in 1000Base-Sx

1AB383760001/
3CC50167AAAA

Can be installed in the Core-E card, EAS card, EASv2 card,


MPT Access card, MSS-1, or MSS-O

SFP plug-in 1000Base-Zx

1AB383760003/
3CC50170AAAA

Can be installed in the Core-E card, EAS card, EASv2 card,


MPT Access card, MSS-1, or MSS-O

172

-48 Vdc Converter Card

User Manual 3DB19901AFAA Edition 01

Parts Lists
Table 2.22 MSS item codes (Continued)
Name

Code

Remarks

EAS Card

3DB18206ACXX

Up to 8 Ethernet traffic interfaces. For the last four


interfaces the dedicated SFP must be installed.

EASv2 Card

3DB19017ABXX

Up to 8 Ethernet traffic interfaces. For the last four


interfaces the dedicated SFP must be installed. Provides
PFoE to up to four MPTs.

ASAP Card

3DB18602AAXX

Up to 16 E1 streams with ATM cells

AUX peripheral Card

3DB18236ABXX

Modem 300 Card

3DB18136AEXX

To interface the ODU300 to be used with 56 MHz


bandwidth (no adaptive modulation)

Modem 300EN Card

3DB18538ACXX

To interface the ODU300 to be used with bandwidth up to


28 MHz (with or without adaptive modulation)

MPT Access Card (with


PFoE)

3DB18634ABXX

To interface one or two MPT-HC/MPT-XP or MPT-MC or one


MPT-HC/MPT-XP and one MPT-MC

+24 Vdc/-48 Vdc


Converter Card

3DB18862AAXX

Two converters on the card for +24 Vdc office applications

+24 Vdc/-48 Vdc


Converter Card

3DB18863ABXX

One converter on the card for +24 Vdc office applications

+24 Vdc/-48 Vdc


Converter

3DB18764AAXX

To replace a failed converter on the +24 Vdc/

Front plate

3DB18163ABXX

SFP plug-in STM-1 L1.1

1AB194670005/
3CC50166AAAA

Can be installed in the STM-1 Access card

SFP plug-in STM-1 S1.1

1AB194670007/
3CC50165AAAA

Can be installed in the STM-1 Access card

SFP plug-in STM-1 Copper

1AB210170001

Can be installed in the STM-1 Access card

SDH electrical SFP

1AB210170001

Can be installed in the STM-1 Access card

SFP plug-in 1000Base-Lx

1AB383760002/
3CC50168AAAA

Can be installed in the Core-E card, EAS card, EASv2 card,


MPT Access card, MSS-1, or MSS-O

SFP plug-in 1000Base-Sx

1AB383760001/
3CC50167AAAA

Can be installed in the Core-E card, EAS card, EASv2 card,


MPT Access card, MSS-1, or MSS-O

SFP plug-in 1000Base-Zx

1AB383760003/
3CC50170AAAA

Can be installed in the Core-E card, EAS card, EASv2 card,


MPT Access card, MSS-1, or MSS-O

-48 Vdc Converter Card

User Manual 3DB19901AFAA Edition 01

173

Parts Lists
Table 2.22 MSS item codes (Continued)
Name

SFP plug-in 1000Base-T


(Copper Transceiver)
SFP 1000Base-BX20

Code

Remarks

1AB359780002/
3CC50169AAAA

Can be installed in the Core-E card, EAS card, EASv2 card,


MSS-1, or MPT Access card

3CC50183AAAA
(1310nm)

Can be installed in the Core-E card, MSS-1, or MSS-O

3CC50184AAAA
(1550nm)
SFP 1000Base-BX40

3CC50198AAAA
(1310nm)

Can be installed in the Core-E card, MSS-1, or MSS-O

3CC50199AAAA
(1550nm)
SFP 2xE1

3DB78012AAAA

Can be installed in the Core-E card or MSS-1

SFP E3

1AB380750004

Can be installed in the Core-E card or MSS-1

SFP S1.1 GE over STM-1

1AB380750003

Can be installed in the Core-E card

EOSDH SFP

1AB380750003

Can be installed in the Core-E card or MSS-1

CWDM-SFP-1470

3CC50201AGAA

Can be installed in the Core-E card, EASv2 card, MSS-1, or


MSS-O

CWDM-SFP-1490

3CC50200AAAA

Can be installed in the Core-E card, EASv2 card, MSS-1, or


MSS-O

CWDM-SFP-1510

3CC50201ABAA

Can be installed in the Core-E card, EASv2 card, MSS-1, or


MSS-O

CWDM-SFP-1530

3CC50201ACAA

Can be installed in the Core-E card, EASv2 card, MSS-1, or


MSS-O

CWDM-SFP-1550

3CC50201AAAA

Can be installed in the Core-E card, EASv2 card, MSS-1, or


MSS-O

CWDM-SFP-1570

3CC50201ADAA

Can be installed in the Core-E card, EASv2 card, MSS-1, or


MSS-O

CWDM-SFP-1590

3CC50201AEAA

Can be installed in the Core-E card, EASv2 card, MSS-1, or


MSS-O

CWDM-SFP-1610

3CC50201AFAA

Can be installed in the Core-E card, EASv2 card, MSS-1, or


MSS-O

Table 2.23 MPT-HLS transceiver codes


Name

MPT HLS 6L

174

Code

Remarks

3DB80493AAXX

MPT-HL 6L RT STD slim

User Manual 3DB19901AFAA Edition 01

Parts Lists
Table 2.23 MPT-HLS transceiver codes (Continued)
Name

Code

Remarks

MPT HLS 6U

3DB80511AAXX

MPT-HL 6U RT STD slim

MPT HLS 6L SD

3DB80493BAXX

MPT-HL 6L RT SD slim

MPT HLS 6U SD

3DB80511BAXX

MPT-HL 6U RT SD slim

MPT-HLS 7Ghz

3DB80519AAXX

MPT-HL 7Ghz RT STD slim

MPT-HLS 7Ghz SD

3DB80519BAXX

MPT-HL 7Ghz RT SD slim

MPT-HLS 8Ghz

3DB80520AAXX

MPT-HL 8Ghz RT STD slim

MPT-HLS 8Ghz SD

3DB80520BAXX

MPT-HL 8Ghz RT SD slim

Table 2.24 MPT-HLS FAN codes


Name

Code

Remarks

Kit Support 2 Fans 1x4 MPT HLS

3DB80470AAXX

Fan Tray 1x4 MPT HLS (Class B,


40.5V to 72V)

3DB80477AAXX

FAN4

Fan Tray 1x4 MPT HLS (Class B, 20V


to 72V)

3DB80477ABXX

FAN4

Fan Dummy Plate

3DB80464AAXX

Table 2.25 MPT-HLS TRU codes


Name

Code

Remarks

TRU

3CC50156AAXX

To be installed on the top of the


ETSI rack

MSS TRU ETSI Bracket

3CC50042AAAA

Breaker 20A

1AB121750001

Breaker 10A

1AB058580016

Breaker 2A

1AB284990001

Table 2.26 ETSI rack and MPT-HLS subrack codes


Name

Code

ETSI Rack H 2200

3CC50230AAXX

User Manual 3DB19901AFAA Edition 01

Remarks

175

Parts Lists
Table 2.26 ETSI rack and MPT-HLS subrack codes (Continued)
Name

Code

TR subrack

3DB80211AAXX

Back panel MPT HLS

3DB80268AAXX

EXT Subrack One TR

3DB80227AAXX

Dummy plate kit

3DB80226AAXX

Remarks

Table 2.27 MPT-HLS branching item codes


Name

Code

1st CH BRN TRX Left High

3DB80409AB

1st CH BRN TRX Right High

3DB80410AB

1st CH BRN RXD Left High

3DB80411AB

1st CH BRN RXD Right High

3DB80412AB

WR137 Power Absorber 5,6-7,1


GHz

3DB01185AAXX

WR137 Power Absorber 7,1-8,5


GHz

3DB01186AAXX

Branching Front Plate Kit

3DB80459AA

Closing kit for channel circulation

3DB80438AA

EXT TRX one channel

3DB80413AB

EXT RXD one channel

3DB80414AB

Kit 5th channel TRX High

3DB80417AB

Kit 5th channel RXD High

3DB80419AB

Flanged stub L=47 mm

3DB02412AAXX

Flanged stub L=94 mm

3DB02413AAXX

Flanged stub L=376 mm

3DB24239AAXX

Flanged stub L=423 mm

3DB24240AAXX

Flanged stub L=141 mm

3DB02414AAXX

Flanged stub L=188 mm

3DB02415AAXX

Flanged stub L=235 mm

3DB02416AAXX

Flanged stub L=282 mm

3DB02417AAXX

176

Remarks

User Manual 3DB19901AFAA Edition 01

Parts Lists
Table 2.27 MPT-HLS branching item codes (Continued)
Name

Code

Flanged stub L=329 mm

3DB02418AAXX

1st CH BRN TRX Right Low

3DB80415AB

1st CH BRN RXD Right Low

3DB80416AB

1st CH BRN TRX 4 Position

3DB80418AB

1st CH BRN RXD 4 Position

3DB80420AB

Kit 5th CH TRX 4 Position

3DB80423AB

Kit 5th CH RXD 4 Position

3DB80424AB

Kit fixing waveguide TRX MPT HLS

3DB80448AA

Kit fixing waveguide RXD MPT HLS

3DB80456AA

Flanged stub UDR70 5,9-7,1 GHz

3DB03022AAXX

Flanged stub UDR84 7,1-8,5 GHz

3DB03023AAXX

Remarks

Table 2.28 MPT-HLS filter and circulator item codes


Name

Code

5.6-6.4 GHz circulator

3DB01184AAXX

Filter 5,9-6,2 GHz 6 CAV.BW 25,5


MHz

3DB80335AA

Filter 6,15-6,45 GHz 6 CAV.BW


25,5 MHz

3DB80336AA

6.4-7.1 GHz circulator

3DB01183AAXX

Filter 6,4-6,75 GHz 6 CAV.BW 25,5


MHz

3DB80337AA

Filter 6,7-7,1 GHz 6 CAV.BW 25,5


MHz

3DB80338AA

7.1-7.9 GHZ circulator

3DB01181AAXX

Filter 7,1-7,45 GHz 6 CAV.BW 25,5


MHz

3DB80339AA

Filter 7,4-7,75 GHz 6 CAV.BW 25,5


MHz

3DB80340AA

Filter 7,65-7,9 GHz 6 CAV.BW 25,5


MHz

3DB80341AA

User Manual 3DB19901AFAA Edition 01

Remarks

177

Parts Lists
Table 2.28 MPT-HLS filter and circulator item codes (Continued)
Name

Code

7.7-8.5 GHz circulator

3DB05095AAXX

Filter 7,7-8 GHz 6 CAV.BW 25,5


MHz

3DB80347AA

Filter 7,9-8,3 GHz 6 CAV.BW 25,5


MHz

3DB80342AA

Filter 8,15-8,5 GHz 6 CAV.BW 25,5


MHz

3DB80343AA

Filter 6.4-6.7 GHz cav Bw 32 MHz

3DB80546AA

Filter 6.7-7.1 GHz cav Bw 32 MHz

3DB80547AA

Remarks

Table 2.29 MPT-HLS cable codes


Name

Code

Power cable zip to battery (6 mmq)


subrack RT

1AC007800069

Power cable zip to battery (1 mmq)


fans

1AC007800068

2X6mm2 L=4 mt power supply cord


per MSS8

3CC52190AAXX

Fan cable MNGT

3CC52141AD

Copper SFP (1,5meter sim.) MSS TRs upper

3DB80628AA

Copper SFP (3 meter sim.) MSS TRs lower

3DB80628AC

XPIC cable

3CC52204AA

Remarks

Table 2.30 Kits for MPT-HLS in LSY subrack


Name

Code

Mechanical adapter

3BD80504AA

Cable kit 6/7/8 GHz

3DB80543AB

Kit cover branching Rx-RXd MPTHLS to LSY

3DB80781AAAA

178

Remarks

User Manual 3DB19901AFAA Edition 01

Parts Lists

Table 2.31 External Power Source item codes


Name

Code

Remarks

Power Injector box

3CC50129AAXX

To be installed in a 19/21 rack to provide the PFoE to the


MPT-MC

Power Injector card

3CC50120AAXX

To be installed in a MSS shelf to provide the PFoE to the


MPT-MC or to the MPT-HC/HC-HQAM

Bracket

3DB77008ACXX

Bracket to be used to install the Power Injector box in a 19


rack

19 to 21 Adapter
bracket kit

3CC50065AAAA

Kit to be used with bracket item to install the Power


Injector box in a 21 rack

MPT Power Unit

3CC50173AAXX

To be installed in a 19/21 rack to provide four Type N


power connections for MPT-HC/HC-HQAM

MPT Extended Power Unit

3CC50174AAXX

To be installed in a 19/21 rack to provide two PFoE or


Type N power connections for MPT-HC/HC-HQAM, MPT-XP/
XP-HQAM, or MPT-MC

Table 2.32 Software item codes


Name

Code

SW 4.2.0
SWP 9500 MPR-E 4.2.0

3DB18969ADAA

Hybrid Operating System


SWP 9500 MPR-E 4.2.0

3DB18970ADAA

Packet Operating System


MPR-E 4.2.0

3DB19902ACAA

User Manual CD ROM EN


TCO SW Suite R4.10

3DB18971ADAA

9500 MPR 4.1.0 SNMP

3DB18896DAAA

SW 5.0.0
SWP 9500 MPR-E 5.0.0

3DB18969AEAA

Hybrid Operating System


SWP 9500 MPR-E 5.0.0

3DB18970AEAA

Packet Operating System


MPR-E 5.0.0

3DB19902ADAA

User Manual CD ROM EN

User Manual 3DB19901AFAA Edition 01

179

Parts Lists
Table 2.32 Software item codes (Continued)
Name

Code

TCO SW Suite Rel 5.0

3DB18971AEAA

9500 MPR 5.0.0 SNMP

3DB18896EAAA

SW 5.1.0
SWP 9500 MPR-E 5.1.0

3DB18969AFAA

Hybrid Operating System


SWP 9500 MPR-E 5.1.0

3DB18970AFAA

Packet Operating System


MPR-E 5.1.0

3DB19902AEAA

User Manual CD ROM EN


TCO SW Suite Rel 5.1

3DB18971AFAA

9500 MPR 5.1.0 SNMP

3DB18896EAAA

SW 5.2.0
SWP 9500 MPR-E 5.2.0

3DB18969AGAA

Hybrid Operating System


SWP 9500 MPR-E 5.2.0

3DB18970AGAA

Packet Operating System


MPR-E 5.2.0

3DB19902AFAA

User Manual CD ROM EN


TCO SW Suite Rel 5.2

3DB18971AGAA

9500 MPR 5.2.0 SNMP

3DB18896GAAA

2.7.2 ODU300 (with internal lightning surge suppressor)

180

User Manual 3DB19901AFAA Edition 01

Parts Lists

Table 2.33 ODU300 item codes


CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23216HAXX

6 GHz

340

6430-6590

ODU 300, 06GHz, T-R 340MHz, 6430-6590MHz, HP, TX


LOW

3DB23216HBXX

6770-6930

ODU 300, 06GHz, T-R 340MHz, 6770-6930MHz, HP, TX


HIGH

3DB23216HCXX

6515-6675

ODU 300, 06GHz, T-R 340MHz, 6515-6675MHz, HP, TX


LOW

3DB23216HDXX

6855-7015

ODU 300, 06GHz, T-R 340MHz, 6855-7015MHz, HP, TX


HIGH

3DB23216HEXX

6600-6760

ODU 300, 06GHz, T-R 340MHz, 6600-6760MHz, HP, TX


LOW

3DB23216HFXX

6940-7100

ODU 300, 06GHz, T-R 340MHz, 6940-7100MHz, HP, TX


HIGH

6540-6610

ODU 300, 06GHz, T-R 160/170MHz, 6540-6610MHz,


HP, TX LOW

3DB23214HBXX

6710-6780

ODU 300, 06GHz, T-R 160/170MHz, 6710-6780MHz,


HP, TX HIGH

3DB23214HCXX

6590-6660

ODU 300, 06GHz, T-R 160/170MHz, 6590-6660MHz,


HP, TX LOW

3DB23214HDXX

6760-6830

ODU 300, 06GHz, T-R 160/170MHz, 6760-6830MHz,


HP, TX HIGH

3DB23214HEXX

6640-6710

ODU 300, 06GHz, T-R 160/170MHz, 6640-6710MHz,


HP, TX LOW

3DB23214HFXX

6800-6870

ODU 300, 06GHz, T-R 160/170MHz, 6800-6870MHz,


HP, TX HIGH

3DB23214HAXX

6 GHz

160/170

User Manual 3DB19901AFAA Edition 01

181

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23215HAXX

6 GHz

252.04

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

7184-7240

ODU 300, 07GHz, T-R 154MHz, 7184-7240MHz, HP, TX


LOW

7338-7394

ODU 300, 07GHz, T-R 154MHz, 7338-7394MHz, HP, TX


HIGH

3DB23027HAXX
3DB23027HBXX

182

7 GHz

154

User Manual 3DB19901AFAA Edition 01

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23028HBXX

7 GHz

161

7124-7184

ODU 300, 07GHz, T-R 161MHz, 7124-7184MHz, HP, TX


LOW

3DB23028HGXX

7282-7342

ODU 300, 07GHz, T-R 161MHz, 7282-7342MHz, HP, TX


HIGH

3DB23028HCXX

7170-7230

ODU 300, 07GHz, T-R 161MHz, 7170-7230MHz, HP, TX


LOW

3DB23028HIXX

7331-7391

ODU 300, 07GHz, T-R 161MHz, 7331-7391MHz, HP TX


HIGH

3DB23028HDXX

7208-7268

ODU 300, 07GHz, T-R 161MHz, 7208-7268MHz, HP, TX


LOW

3DB23028HKXX

7366-7426

ODU 300, 07GHz, T-R 161MHz, 7366-7426MHz, HP, TX


HIGH

3DB23028HOXX

7549-7606

ODU 300, 07GHz, T-R 161MHz, 7549-7606MHz, HP, TX


LOW

3DB23028HRXX

7710-7767

ODU 300, 07GHz, T-R 161MHz, 7710-7767MHz, HP, TX


HIGH

3DB23028HPXX

7598-7655

ODU 300, 07GHz, T-R 161MHz, 7598-7655MHz, HP, TX


LOW

3DB23028HSXX

7759-7816

ODU 300, 07GHz, T-R 161MHz, 7759-7816MHz, HP, TX


HIGH

3DB23028HQXX

7633-7690

ODU 300, 07GHz, T-R 161MHz, 7633-7690MHz, HP, TX


LOW

3DB23028HTXX

7794-7851

ODU 300, 07GHz, T-R 161MHz, 7794-7851MHz, HP, TX


HIGH

User Manual 3DB19901AFAA Edition 01

183

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23026HAXX

7 GHz

154/
161/168

7424-7488

ODU 300, 07GHz, T-R 154/161/168MHz, 74247488MHz, HP, TX LOW

3DB23026HDXX

7581-7649

ODU 300, 07GHz, T-R 154/161/168MHz, 75817649MHz, HP, TX HIGH

3DB23026HBXX

7480-7544

ODU 300, 07GHz, T-R 154/161/168MHz, 74807544MHz, HP, TX LOW

3DB23026HEXX

7637-7705

ODU 300, 07GHz, T-R 154/161/168MHz, 76377705MHz, HP, TX HIGH

3DB23026HCXX

7512-7568

ODU 300, 07GHz, T-R 154/161/168MHz, 75127568MHz, HP, TX LOW

3DB23026HFXX

7666-7729

ODU 300, 07GHz, T-R 154/161/168MHz, 76667729MHz, HP, TX HIGH

7114-7170

ODU 300, 07GHz, T-R 161MHz, 7114-7170MHz, HP, TX


LOW

3DB23028HFXX

7275-7331

ODU 300, 07GHz, T-R 161MHz, 7275-7331MHz, HP, TX


HIGH

3DB23028HUXX

7298-7358

ODU 300, 07GHZ, T-R 161MHz, 7298-7358MHz, HP, TX


LOW

3DB23028HVXX

7459-7519

ODU 300, 07GHZ, T-R 161MHz, 7459-7519MHz, HP, TX


HIGH

3DB23296HAXX

7125-7191

ODU 300, 07GHZ, T-R 161MHz, 7125-7191MHz, HP, TX


LOW

3DB23296HBXX

7282-7352

ODU 300, 07GHZ, T-R 161MHz, 7282-7352MHz, HP, TX


HIGH

3DB23296HCXX

7209-7275

ODU 300, 07GHZ, T-R 161MHz, 7209-7275MHz, HP, TX


LOW

3DB23296HDXX

7367-7436

ODU 300, 07GHZ, T-R 161MHz, 7367-7436MHz, HP, TX


HIGH

3DB23028HAXX

184

7 GHz

161

User Manual 3DB19901AFAA Edition 01

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23298HAXX

7 GHz

154/
161/168

7480-7554

ODU 300, 07GHz, T-R 154/161/168MHz, 74807554MHz, HP, TX HIGH

3DB23299HAXX

7637-7715

ODU 300, 07GHz, T-R 154/161/168MHz, 76377715MHz, HP, TX HIGH

3DB23026HGXX

7421-7491

ODU 300, 07GHz, T-R 154/161/168MHz, 74217491MHz, HP, TX HIGH

3DB23026HHXX

7581-7652

ODU 300, 07GHz, T-R 154/161/168MHz, 75817652MHz, HP, TX HIGH

7247-7309

ODU 300, 07GHz, T-R 161/168MHz, 7247-7309MHz,


HP, TX LOW

3DB23028HLXX

7408-7470

ODU 300, 07GHz, T-R 161/168MHz, 7408-7470MHz,


HP, TX HIGH

3DB23028HWXX

7333,57393

ODU 300, 07GHz, T-R 161/168MHz, 7333,5-7393MHz,


HP, TX LOW

3DB23028HXXX

7494,57554

ODU 300, 07GHz, T-R 161/168MHz, 7494,5-7554MHz,


HP, TX HIGH

7428-7512

ODU 300, 07GHz, T-R 245MHz, 7428-7512MHz, HP, TX


LOW

7673-7757

ODU 300, 07GHz, T-R 245MHz, 7673-7757MHz, HP, TX


HIGH

7512-7596

ODU 300, 07GHz, T-R 245MHz, 7512-7596MHz, HP, TX


LOW

3DB23189HDXX

7757-7841

ODU 300, 07GHz, T-R 245MHz, 7757-7841MHz, HP, TX


HIGH

3DB23189HEXX

7568-7652

ODU 300, 07GHz, T-R 245MHz, 7568-7652MHz, HP, TX


LOW

3DB23189HFXX

7813-7897

ODU 300, 07GHz, T-R 245MHz, 7813-7897MHz, HP, TX


High

3DB23028HEXX

3DB23189HAXX

7 GHz

7 GHz

161

245

3DB23189HBXX
3DB23189HCXX

7 GHz

245

User Manual 3DB19901AFAA Edition 01

185

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23186HAXX

7 GH

161/168

7443-7527

ODU 300, 07GHz, T-R 161/168MHz, 7443-7527MHz,


HP, TX LOW

3DB23186HBXX

7611-7695

ODU 300, 07GHz, T-R 161/168MHz, 7611-7695MHz,


HP, TX HIGH

3DB23186HCXX

7499-7583

ODU 300, 07GHz, T-R 161/168MHz, 7499-7583MHz,


HP, TX LOW

3DB23186HDXX

7667-7751

ODU 300, 07GHz, T-R 161/168MHz, 7667-7751MHz,


HP, TX HIGH

7107-7191

ODU 300, 07GHz, T-R 196MHz, 7107-7191MHz, HP, TX


LOW

3DB23188HBXX

7303-7387

ODU 300, 07GHz, T-R 196MHz, 7303-7387MHz, HP, TX


HIGH

3DB23188HCXX

7163-7247

ODU 300, 07GHz, T-R 196MHz, 7163-7247MHz, HP, TX


LOW

3DB23188HDXX

7359-7443

ODU 300, 07GHz, T-R 196MHz, 7359-7443MHz, HP, TX


HIGH

7424-7485

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


LOW

3DB23218HAXX

7574-7635

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


HIGH

3DB23219HAXX

7470-7530

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


LOW

3DB23220HAXX

7620-7680

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


HIGH

3DB23221HAXX

7515-7575

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


LOW

3DB23222HAXX

7665-7725

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


HIGH

3DB23188HAXX

3DB23217HAXX

186

7 GHz

7 GHz

196

150

User Manual 3DB19901AFAA Edition 01

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23223HAXX

7 GHz

175

7124-7185

ODU 300, 07GHz, T-R 175MHz, 7124-7185MHz, HP, TX


LOW

3DB23224HAXX

7299-7360

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


HIGH

3DB23225HAXX

7157.57217.5

ODU 300, 07GHz, T-R 175MHz, 7157.5-7217.5MHz,


HP, TX LOW

3DB23226HAXX

7332.57392.5

ODU 300, 07GHz, T-R 175MHz, 7332.5-7392.5MHz,


HP, TX HIGH

3DB23227HAXX

7190-7250

ODU 300, 07GHz, T-R 175MHz, 7190-7250MHz, HP, TX


LOW

3DB23228HAXX

7365-7425

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


HIGH

7718-7802

ODU 300, 08GHz, T-R 195MHz, 7718-7802MHz, HP, TX


LOW

7913-7997

ODU 300, 08GHz, T-R 195MHz, 7913-7997MHz, HP, TX


HIGH

7722,57859

ODU 300, 08GHz, T-R 300/310/311.32/305.56MHz,


7722,5-7859MHz, HP, TX LOW

8025-8171

ODU 300, 08GHz, T-R 300/310/311.32/305.56MHz,


8025-8171MHz, HP, TX LOW

3DB23033HFXX

7844-7981

ODU 300, 08GHz, T-R 300/310/311.32/305.56MHz,


7844-7981MHz, HP, TX LOW

3DB23033HHXX

8145-8287

ODU 300, 08GHz, T-R 300/310/311.32/305.56MHz,


8145-8287MHz, HP, TX LOW

3DB23289HAXX

8 GHz

195

3DB23289HBXX

3DB23033HEXX
3DB23033HGXX

8 GHz

300/
310/
311.32/
305.56

User Manual 3DB19901AFAA Edition 01

187

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23030HAXX

8 GHz

151

8204-8275

ODU 300, 08GHz, T-R 151MHz, 8204-8275MHz, HP, TX


LOW

3DB23030HCXX

8355-8426

ODU 300, 08GHz, T-R 151MHz, 8355-8426MHz, HP, TX


HIGH

3DB23030HBXX

8273-8345

ODU 300, 08GHz, T-R 151MHz, 8273-8345MHz, HP, TX


LOW

3DB23030HDXX

8425-8496

ODU 300, 08GHz, T-R 151MHz, 8425-8496MHz, HP, TX


HIGH

8279-8321

ODU 300, 08GHz, T-R 119/126MHz, 8279-8321MHz,


HP, TX LOW

3DB23029HDXX

8398-8440

ODU 300, 08GHz, T-R 119/126MHz, 8398-8440MHz,


HP, TX HIGH

3DB23029HBXX

8307-8349

ODU 300, 08GHz, T-R 119/126MHz, 8307-8349MHz,


HP, TX LOW

3DB23029HEXX

8426-8468

ODU 300, 08GHz, T-R 119/126MHz, 8426-8468MHz,


HP, TX HIGH

3DB23029HCXX

8335-8377

ODU 300, 08GHz, T-R 119/126MHz, 8335-8377MHz,


HP, TX LOW

3DB23029HFXX

8454-8496

ODU 300, 08GHz, T-R 119/126MHz, 8454-8496MHz,


HP, TX HIGH

7898-8021

ODU 300, 08GHz, T-R 266MHz, 7898-8021MHz, HP, TX


LOW

3DB23032HCXX

8164-8290

ODU 300, 08GHz, T-R 266MHz, 8164-8290MHz, HP, TX


HIGH

3DB23032HBXX

8010-8133

ODU 300, 08GHz, T-R 266MHz, 8010-8133MHz, HP, TX


LOW

3DB23032HDXX

8276-8399

ODU 300, 08GHz, T-R 266MHz, 8276-8399MHz, HP, TX


HIGH

3DB23029HAXX

3DB23032HAXX

188

8 GHz

8 GHz

119/126

266

User Manual 3DB19901AFAA Edition 01

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23034HAXX

8 GHz

310

7905-8045

ODU 300, 08GHz, T-R 310MHz, 7905-8045MHz, HP, TX


LOW

3DB23034HCXX

8215-8355

ODU 300, 08GHz, T-R 310MHz, 8215-8355MHz, HP, TX


HIGH

3DB23034HBXX

8045-8185

ODU 300, 08GHz, T-R 310MHz, 8045-8185MHz, HP, TX


LOW

3DB23034HDXX

8355-8495

ODU 300, 08GHz, T-R 310MHz, 8355-8495MHz, HP, TX


HIGH

8050-8148

ODU 300, 08GHz, T-R 208MHz, 8050-8148MHz, HP, TX


LOW

3DB23031HCXX

8258-8356

ODU 300, 08GHz, T-R 208MHz, 8258-8356MHz, HP, TX


HIGH

3DB23031HBXX

8099-8197

ODU 300, 08GHz, T-R 208MHz, 8099-8197MHz, HP, TX


LOW

3DB23031HDXX

8307-8405

ODU 300, 08GHz, T-R 208MHz, 8307-8405MHz, HP, TX


HIGH

3DB23031HEXX

8148-8246

ODU 300, 08GHz, T-R 208MHz, 8148-8246MHz, HP, TX


LOW

3DB23031HFXX

8356-8454

ODU 300, 08GHz, T-R 208MHz,8356-8454MHz, HP, TX


HIGH

7750-7900

ODU 300, 08GHz, T-R 360MHz, 7750-7900MHz, HP, TX


LOW

3DB23304HAXX

8110-8260

ODU 300, 08GHz, T-R 360MHz, 8110-8260MHz, HP, TX


HIGH

3DB23305HAXX

7870-8020

ODU 300, 08GHz, T-R 360MHz, 7870-8020MHz, HP, TX


LOW

3DB23306HAXX

8230-8380

ODU 300, 08GHz, T-R 360MHz, 8230-8380MHz, HP, TX


HIGH

3DB23307HAXX

7990-8140

ODU 300, 08GHz, T-R 360MHz, 7990-8140MHz, HP, TX


HIGH

3DB23308HAXX

8350-8500

ODU 300, 08GHz, T-R 360MHz, 8350-8500MHz, HP, TX


HIGH

3DB23031HAXX

3DB23303HAXX

8 GHz

8 GHz

208

360

User Manual 3DB19901AFAA Edition 01

189

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23261HAXX

10 GHz

350

10150.510252

ODU 300, 10GHz, T-R 350MHz, 10150.5-10252MHz,


EP, TX LOW

3DB23261HBXX

10500.510602

ODU 300, 10GHz, T-R 350MHz, 10500.5-10602MHz,


EP, TX HIGH

3DB23261HCXX

1019610297.5

ODU 300, 10GHz, T-R 350MHz, 10196-10297.5MHz,


EP, TX LOW

3DB23261HDXX

1054610647.5

ODU 300, 10GHz, T-R 350MHz, 10546-10647.5MHz,


EP, TX HIGH

10500.510516.3

ODU 300, 10GHz, T-R 91MHz, 10500.5-10516.3MHz,


EP, TX LOW

3DB23255HBXX

10591.510607.3

ODU 300, 10GHz, T-R 91MHz, 10591.5-10607.3MHz,


EP, TX HIGH

3DB23255HCXX

10514.510530.3

ODU 300, 10GHz, T-R 91MHz, 10514.5-10530.3MHz,


EP, TX LOW

3DB23255HDXX

10605.510621.3

ODU 300, 10GHz, T-R 91MHz, 10605.5-10621.3MHz,


EP, TX HIGH

3DB23255HEXX

10528.510544.3

ODU 300, 10GHz, T-R 91MHz, 10528.5-10544.3MHz,


EP, TX LOW

3DB23255HFXX

10619.510635.3

ODU 300, 10GHz, T-R 91MHz, 10619.5-10635.3MHz,


EP, TX HIGH

3DB23255HGXX

10542.510558.3

ODU 300, 10GHz, T-R 91MHz, 10542.5-10558.3MHz,


EP, TX LOW

3DB23255HHXX

10633.510649.3

ODU 300, 10GHz, T-R 91MHz, 10633.5-10649.3MHz,


EP, TX HIGH

10556.510572.3

ODU 300, 10GHz, T-R 91MHz, 10556.5-10572.3MHz,


EP, TX LOW

3DB23255HLXX

10647.510663.3

ODU 300, 10GHz, T-R 91MHz, 10647.5-10663.3MHz,


EP, TX HIGH

3DB23255HMXX

10570.510586.3

ODU 300, 10GHz, T-R 91MHz, 10570.5-10586.3MHz,


EP, TX LOW

3DB23255HNXX

10661.510677.3

ODU 300, 10GHz, T-R 91MHz, 10661.5-10677.3MHz,


EP, TX HIGH

3DB23255HAXX

3DB23255HIXX

190

10 GHz

10 GHz

91

91

User Manual 3DB19901AFAA Edition 01

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23241HAXX

10 GHz

65

1055010560

ODU 300, 10GHz, T-R 65MHz, 10550-10560MHz, EP,


TX LOW

3DB23242HAXX

1061510625

ODU 300, 10GHz, T-R 65MHz, 10615-10625MHz, EP,


TX HIGH

3DB23243HAXX

1056010570

ODU 300, 10GHz, T-R 65MHz, 10560-10570MHz, EP,


TX LOW

3DB23244HAXX

1062510635

ODU 300, 10GHz, T-R 65MHz, 10625-10635MHz, EP,


TX HIGH

3DB23245HAXX

1057010580

ODU 300, 10GHz, T-R 65MHz, 10570-10580MHz, EP,


TX LOW

3DB23246HAXX

1063510645

ODU 300, 10GHz, T-R 65MHz, 10635-10645MHz, EP,


TX HIGH

3DB23247HAXX

1058010590

ODU 300, 10GHz, T-R 65MHz, 10580-10590MHz, EP,


TX LOW

3DB23248HAXX

1064510655

ODU 300, 10GHz, T-R 65MHz, 10645-10655MHz, EP,


TX HIGH

3DB23249HAXX

1059010600

ODU 300, 10GHz, T-R 65MHz, 10590-10600MHz, EP,


TX LOW

3DB23250HAXX

1065510665

ODU 300, 10GHz, T-R 65MHz, 10655-10665MHz, EP,


TX HIGH

3DB23251HAXX

1060010610

ODU 300, 10GHz, T-R 65MHz, 10600-10610MHz, EP,


TX LOW

3DB23252HAXX

1066510675

ODU 300, 10GHz, T-R 65MHz, 10665-10675MHz, EP,


TX HIGH

3DB23253HAXX

1060510615

ODU 300, 10GHz, T-R 65MHz, 10605-10615MHz, EP,


TX LOW

3DB23254HAXX

1067010680

ODU 300, 10GHz, T-R 65MHz, 10670-10680MHz, EP,


TX HIGH

User Manual 3DB19901AFAA Edition 01

191

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23035HAXX

11 GHz

490/
500/530

1067510835

ODU 300, 11GHz, T-R 490/0500/0530MHz, 1067510835MHz, HP, TX LOW

3DB23035HEXX

1120011345

ODU 300, 11GHz, T-R 490/0500/0530MHz, 1120011345MHz, HP, TX HIGH

3DB23035HBXX

1079510955

ODU 300, 11GHz, T-R 490/0500/0530MHz, 1079510955MHz, HP, TX LOW

3DB23035HFXX

1131011465

ODU 300, 11GHz, T-R 490/0500/0530MHz, 1131011465MHz, HP, TX HIGH

3DB23035HCXX

1091511075

ODU 300, 11GHz, T-R 490/0500/0530MHz, 1091511075MHz, HP, TX LOW

3DB23035HGXX

1143011585

ODU 300, 11GHz, T-R 490/0500/0530MHz, 1143011585MHz, HP, TX HIGH

3DB23035HDXX

1103511200

ODU 300, 11GHz, T-R 490/0500/0530MHz, 1103511200MHz, HP, TX LOW

3DB23035HHXX

1155011705

ODU 300, 11GHz, T-R 490/0500/0530MHz, 1155011705MHz, HP, TX HIGH

1275112835

ODU 300, 13GHz, T-R 266MHz, 12751-12835MHz, HP,


TX LOW

3DB23036HEXX

1301713101

ODU 300, 13GHz, T-R 266MHz, 13017-13101MHz, HP,


TX HIGH

3DB23036HBXX

1280712891

ODU 300, 13GHz, T-R 266MHz, 12807-12891MHz, HP,


TX LOW

3DB23036HFXX

1307313157

ODU 300, 13GHz, T-R 266MHz, 13073-13157MHz, HP,


TX HIGH

3DB23036HDXX

1289112975

ODU 300, 13GHz, T-R 266MHz, 12891-12975MHz, HP,


TX LOW

3DB23036HHXX

1315713241

ODU 300, 13GHz, T-R 266MHz, 13157-13241MHz, HP,


TX HIGH

3DB23036HCXX

1283512919

ODU 300, 13GHz, T-R 266MHz, 12835-12919MHz, HP,


TX LOW

3DB23036HGXX

1310113185

ODU 300, 13GHz, T-R 266MHz, 13101-13185MHz, HHP,


TX HIGH

3DB23036HAXX

192

13 GHz

266

User Manual 3DB19901AFAA Edition 01

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23037HAXX

15 GHz

315/322

1462714788

ODU 300, 15GHz, T-R 315MHz, 14627-14788MHz, HP,


TX LOW

3DB23037HCXX

1494215103

ODU 300, 15GHz, T-R 315MHz, 14942-15103MHz, HP,


TX HIGH

3DB23037HBXX

1476014914

ODU 300, 15GHz, T-R 315MHz, 14760-14914MHz, HP,


TX LOW

3DB23037HDXX

1507515229

ODU 300, 15GHz, T-R 315MHz, 15075-15229MHz, HP,


TX HIGH

1450114648

ODU 300, 15GHz, T-R 420MHz, 14501-14648MHz, HHP,


TX LOW

3DB23038HDXX

1492115068

ODU 300, 15GHz, T-R 420MHz, 14921-15068MHz, HP,


TX HIGH

3DB23038HBXX

1464114788

ODU 300, 15GHz, T-R 420MHz, 14641-14788MHz, HP,


TX LOW

3DB23038HEXX

1506115208

ODU 300, 15GHz, T-R 420MHz, 15061-15208MHz, HP,


TX HIGH

3DB23038HCXX

1478114928

ODU 300, 15GHz, T-R 420MHz, 14781-14928MHz, HP,


TX LOW

3DB23038HFXX

1520115348

ODU 300, 15GHz, T-R 420MHz, 15201-15348MHz, HP,


TX HIGH

1440314634

ODU 300, 15GHz, T-R 490/490MHz, 14403-14634MHz,


HP, TX LOW

3DB23039HFXX

1489315124

ODU 300, 15GHz, T-R 490/490MHz, 14893-15124MHz,


HP, TX HIGH

3DB23039HAXX

1462714873

ODU 300, 15GHz, T-R 475/0490MHz, 1462714873MHz, HP, TX LOW

3DB23039HBXX

1511715348

ODU 300, 15GHz, T-R 475/0490MHz, 1511715348MHz, HP, TX HIGH

3DB23038HAXX

3DB23039HEXX

15 GHz

15 GHz

420

475/490

User Manual 3DB19901AFAA Edition 01

193

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23295HAXX

15 GHz

640/
644/728

1450014714.5

ODU 300, 15GHz, T-R 640/644/0728MHz, 1450014714.5MHz, HP, TX LOW

15136.515350

ODU 300, 15GHz, T-R 640/644/0728MHz, 15136.515350MHz, HP, TX HIGH

1450014660

ODU 300, 15GHz, T-R 475MHz, 14500-14660MHz, HP,


TX LOW

1497515135

ODU 300, 15GHz, T-R 475MHz, 14975-15135MHz, HP,


TX HIGH

17700 18140

ODU 300, 18GHz, T-R 1560MHz, 17700-18140MHz, HP,


TX LOW

19260 19700

ODU 300, 18GHz, T-R 1560MHz, 19260-19700MHz, HP,


TX HIGH

1858018660

ODU 300, 18GHz, T-R 340MHz, 18580-18660MHz, HP,


TX LOW

3DB23041HDXX

1892019000

ODU 300, 18GHz, T-R 340MHz, 18920-19000MHz, HP,


TX HIGH

3DB23041HBXX

1866018740

ODU 300, 18GHz, T-R 340MHz, 18660-18740MHz, HP,


TX LOW

3DB23041HEXX

1900019080

ODU 300, 18GHz, T-R 340MHz, 19000-19080MHz, HP,


TX HIGH

3DB23041HCXX

1874018820

ODU 300, 18GHz, T-R 340MHz, 18740-18820MHz, HP,


TX LOW

3DB23041HFXX

1908019160

ODU 300, 18GHz, T-R 340MHz, 19080-19160MHz, HP,


TX HIGH

3DB23295HBXX

3DB23039HCXX

15 GHz

475

3DB23039HDXX

3DB23062HCXX

18 GHz

1560

3DB23062HDXX

3DB23041HAXX

194

18 GHz

340

User Manual 3DB19901AFAA Edition 01

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23042HAXX

18 GHz

1008/
1010/
1092/
1120

1770018060

ODU 300, 18GHz, T-R 1008/1010/1092/1120MHz,


17700-18060MHz, HP, TX LOW

1871019070

ODU 300, 18GHz, T-R 1008/1010/1092/1120MHz,


18710-19070MHz, HHP, TX HIGH

3DB23042HBXX

1790518275

ODU 300, 18GHz, T-R 1008/1010/1092/1120MHz,


17905-18275MHz, HHP, TX LOW

3DB23042HFXX

1892019290

ODU 300, 18GHz, T-R 1008/1010/1092/1120MHz,


18920-19290MHz, HP, TX HIGH

3DB23042HCXX

1811018490

ODU 300, 18GHz, T-R 1008/1010/1092/1120MHz,


18110-18490MHz, HP, TX LOW

3DB23042HGXX

1913019510

ODU 300, 18GHz, T-R 1008/1010/1092/1120MHz,


19130-19510MHz, HP, TX HIGH

3DB23042HDXX

1833018690

ODU 300, 18GHz, T-R 1008/1010/1092/1120MHz,


18330-18690MHz, HP, TX LOW

3DB23042HHXX

1934019700

ODU 300, 18GHz, T-R 1008/1010/1092/1120MHz,


19340-19700MHz, HP, TX HIGH

2120021570

ODU 300, 23GHz, T-R 1200/1232MHz, 2120021570MHz, HP, TX LOW

3DB23045HEXX

2240022770

ODU 300, 23GHz, T-R 1200/1232MHz, 2240022770MHz, HP, TX HIGH

3DB23045HBXX

2147521845

ODU 300, 23GHz, T-R 1200/1232MHz, 2147521845MHz, HP, TX LOW

3DB23045HFXX

2267523045

ODU 300, 23GHz, T-R 1200/1232MHz, 2267523045MHz, HP, TX HIGH

3DB23045HCXX

2175022120

ODU 300, 23GHz, T-R 1200/1232MHz, 2175022120MHz, HP, TX LOW

3DB23045HGXX

2295023320

ODU 300, 23GHz, T-R 1200/1232MHz, 2295023320MHz, HP, TX HIGH

2203022400

ODU 300, 23GHz, T-R 1200/1232MHz, 2203022400MHz, HP, TX LOW

2332023600

ODU 300, 23GHz, T-R 1200/1232MHz, 2323023600MHz, HP, TX HIGH

3DB23042HEXX

3DB23045HAXX

3DB23045HDXX
3DB23045HHXX

23 GHz

23 GHz

1200/
1232

1200/
1232

User Manual 3DB19901AFAA Edition 01

195

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23044HAXX

23 GHz

1008

2195222312

ODU 300, 23GHz, T-R 1008MHz, 21952-22312MHz, HP,


TX LOW

3DB23044HDXX

2296023320

ODU 300, 23GHz, T-R 1008MHz, 22960-23320MHz, HP,


TX HIGH

3DB23044HCXX

2223222592

ODU 300, 23GHz, T-R 1008MHz, 22232-22592MHz, HP,


TX LOW

3DB23044HFXX

2324023600

ODU 300, 23GHz, T-R 1008MHz, 23240-23600MHz, HP,


TX HIGH

3DB23044HBXX

2200222337

ODU 300, 23GHz, T-R 1008MHz, 22002-22337MHz, HP,


TX LOW

3DB23044HEXX

2301023345

ODU 300, 23GHz, T-R 1008MHz, 23010-23345MHz, HP,


TX HIGH

2214022380

ODU 300, 23GHz, T-R 600MHz, 22140-22380MHz, HP,


TX LOW

2274022980

ODU 300, 23GHz, T-R 600MHz, 22740-22980MHz, HP,


TX HIGH

2454924909

ODU 300, 25GHz, T-R 1008MHz, 24549-24909MHz, HP,


TX LOW

3DB23259HBXX

2555725917

ODU 300, 25GHz, T-R 1008MHz, 25557-25917MHz, HP,


TX HIGH

3DB23259HCXX

2481725177

ODU 300, 25GHz, T-R 1008MHz, 24817-25177MHz, HP,


TX LOW

3DB23259HDXX

2582526185

ODU 300, 25GHz, T-R 1008MHz, 25825-26185MHz, HP,


TX HIGH

3DB23259HEXX

2508525445

ODU 300, 25GHz, T-R 1008MHz, 25085-25445MHz, HP,


TX LOW

3DB23259HFXX

2609326453

ODU 300, 25GHz, T-R 1008MHz, 26093-26453MHz, HP,


TX HIGH

3DB23043HAXX

23 GHz

600

3DB23043HBXX

3DB23259HAXX

196

25 GHz

1008

User Manual 3DB19901AFAA Edition 01

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23213HAXX

28 GHz

1008

2750027870

ODU 300, 28GHz, T-R 1008MHz, 27500-27870MHz, HP,


TX LOW

3DB23213HDXX

2850828878

ODU 300, 28GHz, T-R 1008MHz, 28508-28878MHz, HP,


TX HIGH

3DB23213HBXX

2782028190

ODU 300, 28GHz, T-R 1008MHz, 27820-28190MHz, HP,


TX LOW

3DB23213HEXX

2882829198

ODU 300, 28GHz, T-R 1008MHz, 28828-29198MHz, HP,


TX HIGH

3DB23213HCXX

2814028510

ODU 300, 28GHz, T-R 1008MHz, 28140-28510MHz, HP,


TX LOW

3DB23213HFXX

2914829518

ODU 300, 28GHz, T-R 1008MHz, 29148-29518MHz, HP,


TX HIGH

3180032050

ODU 300, 32GHz, T-R 812MHz, 31800-32050MHz, HP,


TX LOW

3DB48245HBXX

3261232862

ODU 300, 32GHz, T-R 812MHz, 32612-32862MHz, HP,


TX HIGH

3DB48245HCXX

3197832228

ODU 300, 32GHz, T-R 812MHz, 31978-32228MHz, HP,


TX LOW

3DB48245HDXX

3279033040

ODU 300, 32GHz, T-R 812MHz, 32790-33040MHz, HP,


TX HIGH

3DB48245HGXX

3215132401

ODU 300, 32GHz, T-R 812MHz, 32151-32401MHz, HP,


TX LOW

3DB48245HHXX

3296333213

ODU 300, 32GHz, T-R 812MHz, 32963-33213MHz, HP,


TX HIGH

3DB48245HIXX

3231932590

ODU 300, 32GHz, T-R 812MHz, 32319-32590MHz, HP,


TX HIGH

3DB48245HLXX

3313133402

ODU 300, 32GHz, T-R 812MHz, 33131-33402MHz, HP,


TX HIGH

3DB48245HAXX

32 GHz

812

User Manual 3DB19901AFAA Edition 01

197

Parts Lists
Table 2.33 ODU300 item codes (Continued)
CODES

Freq.

TRsp
(MHz)

Frequency
Range

Description

3DB23258HAXX

38 GHz

1260

3702837368

ODU 300, 38GHz, T-R 1260MHz, 37028-37368MHz, HP,


TX LOW

3DB23258HBXX

3828838628

ODU 300, 38GHz, T-R 1260MHz, 38288-38628MHz, HP,


TX HIGH

3DB23258HCXX

3730837648

ODU 300, 38GHz, T-R 1260MHz, 37308-37648MHz, HP,


TX LOW

3DB23258HDXX

3856838908

ODU 300, 38GHz, T-R 1260MHz, 38568-38908MHz, HP,


TX HIGH

3DB23258HEXX

3758837928

ODU 300, 38GHz, T-R 1260MHz, 37588-37928MHz, HP,


TX LOW

3DB23258HFXX

3884839188

ODU 300, 38GHz, T-R 1260MHz, 38848-39188MHz, HP,


TX HIGH

3DB23258HGXX

3786838208

ODU 300, 38GHz, T-R 1260MHz, 37868-38208MHz, HP,


TX LOW

3DB23258HHXX

3912839468

ODU 300, 38GHz, T-R 1260MHz, 39128-39468MHz, HP,


TX HIGH

3DB23258HIXX

3725137526

ODU 300, 38GHz, T-R 1260MHz, 37251-37526MHz, HP,


TX LOW

3DB23258HLXX

3851138786

ODU 300, 38GHz, T-R 1260MHz, 38511-38786MHz, HP,


TX HIGH

3DB23258HMXX

3705837478

ODU 300, 38GHz, T-R 1260MHz, 37058-37478MHz, HP,


TX LOW

3DB23258HNXX

3831838738

ODU 300, 38GHz, T-R 1260MHz, 38318-38738MHz, HP,


TX HIGH

2.7.3 MPT-HC/HC-HQAM with internal diplexer


For information about MPT-HC with internal diplexer, see the 9500 MPR Frequency Plan
for MPT Outdoor Transceivers.

2.7.4 MPT-MC with internal diplexer

198

User Manual 3DB19901AFAA Edition 01

Parts Lists

For information about MPT-MC with internal diplexer, see the 9500 MPR Frequency Plan
for MPT Outdoor Transceivers.

2.7.5 MPT-HC/HC-HQAM/MC/XP/XP-HQAM with branching


filter
The diplexer included in the available branching filter assemblies refers to ITUR F.385,
386 and RF special customers channeling with Tx/Rx separation specified in the 9500 MPR
Frequency Plan for MPT Outdoor Transceivers.
For information about MPT-HC/HC-HQAM/MC/XP/XP-HQAM with branching filter,
see the 9500 MPR Frequency Plan for MPT Outdoor Transceivers.
Each diplexer is a 3-port passive device with two bandpass filters as described hereafter.

An example of the arrangement between each filter on the same branching filter device is
shown below:
Figure 2.47

User Manual 3DB19901AFAA Edition 01

199

Parts Lists

Warning: f1, f2, f3 and f4 frequencies of the external diplexer filters refer to the extreme
channel frequencies and not to the cutoff frequencies of the filters.

2.7.5.1 MPT ODU codes


For information about MPT ODU codes, see the 9500 MPR Frequency Plan for MPT
Outdoor Transceivers.

2.7.5.2 External diplexer codes


For information about external diplexer codes, see the 9500 MPR Frequency Plan for MPT
Outdoor Transceivers.

2.7.6 MPT-HC/HC-HQAM/XP/XP-HQAM optical interface


Table 2.34 MPT-HC/MPT-XP optical interface
Description

Codes

SFP 1000Base-Sx Transceiver

1AB383760001/
3CC50167AAAA

SFP 1000Base-Lx Transceiver

1AB383760002/
3CC50168AAAA

Remarks

Optical SFP module to be installed optionally in the


MPT to provide the optical interface

Note: The SFP is mandatory for cabled 1+1 configuration with MPT-HC/MPT-XP.

2.7.7 MPT-HC/MPT-XP external modules (option)


For information about external modules, see the 9500 MPR Frequency Plan for MPT
Outdoor Transceivers.

2.7.8 MPT-HC/HC-HQAM/MC/XP/XP-HQAM couplers


200

User Manual 3DB19901AFAA Edition 01

Parts Lists

Table 2.35 MPT-HC/HC-HQAM/MC/XP/XP-HQAM couplers


Description

Codes

6 GHz 1 dB/10 dB coupler

3CC58056ABXX

6 GHz 3 dB coupler

3CC58056AAXX

7.1-8.5 GHz 1 dB/10 dB coupler

3CC14536AAXX

7.1-8.5 GHz 3 dB coupler MPT

3CC14536ABAA

10-11.7GHz 3dB coupler

3CC58224AAXX

10-11.7GHz 10dB coupler

3CC58226AAXX

10.7-11.7 GHz 3 dB coupler

3CC14140AAXX

10.7-11.7GHz GHz 10 dB coupler

3CC14140ABXX

13-15 GHz 1 dB/10 dB coupler

3CC13472ABXX

13-15 GHz 3 dB coupler MPT

3CC13472AAXX

18-23-25 GHz 1 dB/10 dB coupler

3CC13473ABXX

18-23-25 GHz 3 dB coupler MPT

3CC13473AAXX

28-38 GHz 1 dB/10 dB coupler

3CC13474ABXX

28-38 GHz 3 dB coupler MPT

3CC13474AAXX

2.7.9 OMT couplers


The OMT allows to install 2 MPT using H and V polarizations. The OMT can be installed
only to the integrated antenna.
Table 2.36 OMT couplers
Description

Codes

OMT 6 GHz L

3CC58134AAXX

OMT 6 GHz U

3CC58186AAXX

OMT 7 GHz

3CC58124AAXX

OMT 8 GHz

3CC58133AAXX

OMT 11 GHz

3CC58161AAXX

OMT 13 GHz

3CC58162AAXX

User Manual 3DB19901AFAA Edition 01

201

Parts Lists
Table 2.36 OMT couplers (Continued)
Description

Codes

OMT 15 GHz

3CC58163AAXX

OMT 18 GHz

3CC58164AAXX

OMT 23 GHz

3CC58165AAXX

2.7.10 OMT-C coupler


The OMT-C allows to install up to 4 MPT using H and V polarizations.
The OMT-C can be installed to the integrated antenna only.
Figure 2.48 OMT-C

202

User Manual 3DB19901AFAA Edition 01

Parts Lists
Figure 2.49 OMT-C

Table 2.37 OMT-C coupler


Description

Codes

OMT-C L6 GHz

3CC58244AAXX

OMT-C U6 GHz

3CC58266AAXX

OMT-C 7.1-8.5 GHz

3CC58268AAXX

OMT-C 11 GHz (MPT-HC only)

3CC58200AAXX

OMT-C 13 GHz

3CC58245AAXX

OMT-C 15 GHz

3CC58246AAXX

OMT-C 18 GHz

3CC58201AAXX

OMT-C 23 GHz

3CC58202AAXX

User Manual 3DB19901AFAA Edition 01

203

Functional description

2.7.11 Loads for unused ports


Table 2.38 OMT Loads
Description

Codes

WR28 Load (38 GHz)

3CC58220AAXX

WR42 Load (18-25 GHz)

3CC58221AAXX

WR62 Load (13-15 GHz)

3CC58228AAXX

WR75 Load (11 GHz)

3CC58223AAXX

WR112 Load (7-8 GHz)

3CC58230AAXX

WR137 Load (6 GHz)

3CC58225AAXX

2.8 Functional description


2.8.1 MSS (Microwave Service Shelf)
The MSS incorporates the baseband processing, tributaries interfaces and supervision.
The MSS-4 and MSS-8 also offer modem functionalities when an ODU300 is connected.
The MSS is frequencyindependent.
The following MSS are available:

MSS-8

MSS-4

MSS-1

MSS-O

The MSS-8 is made of:

204

1 subrack (MSS-8 shelf)

1 or 2 Core-E Modules (Main & Spare)

up to 6 Transport Modules

1 AUX Peripheral Module (option: to be installed in Transport slot #8)

1 +24 Vdc/-48 Vdc Converter Module (option for +24 Vdc office application: to be
installed in Transport slot #4, #6 or #8)

1 Fans unit
User Manual 3DB19901AFAA Edition 01

Functional description

The MSS-4 is made of:

1 subrack (MSS-4 shelf)

1 or 2 Core-E Modules (Main & Spare)

up to 2 Transport Modules

1 AUX Peripheral Module (option: to be installed in Transport slot #4)

1 Fans unit

The MSS-1 is made of:

1 monoboard

Ethernet ports that provide the functions of a Core-E Module

Connectors that provide the functions of a 16xE1 Local Access Transport Module
with 16 ports

Housekeeping interfaces

The MSS-1 supports connection to radios that can be connected to a Core-E module.
Table 2.39 provides MSS-1 unit indicator details.
Table 2.39 MSS-1 unit indicator details
Indicator
(LED)

Status

Definition

Status

OFF

MSS-1 shelf not Provisioned


MSS-1 shelf not Powered
MSS-1 shelf not Equipped

Green
Blinking

Configuration Downloading, SW Booting.

Green

MSS-1 shelf Properly Equipped and Provisioned. Currently In-Service.

Red

MSS-1 shelf Fail

Major Alarm

Red

At least one alarm with Critical or Major severity present in the NE.

Minor Alarm

Red

At least one alarm with Minor severity present in the NE.

Warning

Yellow

At least one alarm with Warning severity present in the NE.

Abnormal

Yellow

At least one abnormal condition present in the NE.

PFoE

Yellow

Port is emitting power according to the configuration.

OFF

Port is emitting power according to the configuration.

The MSS-O is made of:


User Manual 3DB19901AFAA Edition 01

205

Functional description

1 monoboard

Three electrical Ethernet ports, two with PFoE

One optical SPF Ethernet port

The MSS-O supports connection to MPT-MC/HC/HC-HQAM/XP/XP-HQAM radios.

2.8.1.1 MSS-4/8 modules


The following types of Transport Modules are supported by the MSS-4 and MSS-8:

32xE1 Local Access Module

16xE1 ATM Local Access - ASAP Module

2xSTM-1 Local Access Module

Modem Module: to interface the ODU300

MPT Access Module: to interface up to two MPT. It can provide the PFoE

EAS Module: provides up to 8 ports. Port #1 to port #4 are electrical Ethernet ports
for user Ethernet traffic. Port #5 to port #8 (by installing the relevant SFP) can be used
as optical ports for user Ethernet traffic or can be used to connect an MPT-HC/HCHQAM/XP/XP-HQAM in 1+0 configuration. The MPT-HC/HC-HQAM/XP/XPHQAM can be grouped to create an L1 Radio LAG.

EASv2 Module: provides up to 8 ports. Port #1 to port #4 are electrical Ethernet ports
for user Ethernet traffic and MPT connectivity. Port #5 to port #8 (by installing the
relevant SFP) can be used as optical ports for user Ethernet traffic or can be used to
connect an MPT-HC/HC-HQAM/XP/XP-HQAM in 1+0 configuration. The MPTHC/HC-HQAM/XP/XP-HQAM connected to optical or electrial ports can be
grouped to create an L1 Radio LAG. Provides PFoE for up to four MPTs.

Note: A cross-plugin LAG can be created when two EAS or EASv2 units are installed in the
same slot of the MSS. A cross-plugin LAG cannot be created with an EAS unit and an EASv2
unit.

In the right part of the MSS shelf there are two sub-D 2-pole power supply connectors.

2.8.1.2 Power distribution


The MSS-4 and MSS-8 receive the Battery input through 2 power connectors mounted on
the Subrack structure and connected directly to the Backplane.
The MSS-1 receives battery input through 2 power connectors on the front panel.
The MSS-O receives battery input through an AC converter and connector.
206

User Manual 3DB19901AFAA Edition 01

Functional description

Each board, in which a converter is mounted, is provided with fuses and diodes on all the
lines, in order to be fully independent from the other ones.
The ODU300 Modem unit provides the power supply to the ODU300.
The MPT Access, MSS-1, MSS-O or EASv2 unit can provide the PFoE to MPT to supply
the MPT by using the same cable used also to carry the Ethernet traffic.
On the output section the Core-E (Main) board provides +3.3V in parallel with the Core-E
(Spare) board to supply the Fan Unit.
A 3.3V, coming from the two Core-E units, is provided to read the EEPROM present on
each board also when the DC/DC converter, present on its board, is out of order.
Figure 2.50 Power Distribution Architecture for MSS-8
Batt. A
-48 Vdc + 15%/-20%

Batt. B
-48 Vdc + 15%/-20%

Core-E
(Spare)

FAN UNIT

Core-E
(Main)

BACK
PLANE

32E1/ASAP/
STM-1
MPT
Access
ODU300
MODEM

EAS/EASv2
24121

2.8.1.3 +24 Vdc/-48 Vdc Converter unit


When office power configuration consists of +24 Vdc a +24/-48 volt power converter is
required to condition office power to -48 Vdc for the MSS-8 shelf.
The power converter can be used only with MSS-8 shelf, in combination with FAN unit
(3EM23911AAAA) and, for max efficiency, positioned in slots 4, 6 or 8.
Office power (+24 Vdc) is connected to the PDU which in turn connects to the power
converter.
User Manual 3DB19901AFAA Edition 01

207

Functional description

The output of the Power Converter (-48 Vdc) is then connected to the MSS-8 shelf power
connector(s).
The Power Converter supports both unprotected and protected power arrangements.
The same PDU power cables are used to connect between the PDU and the power
converter.
Keyed power cables are used to connect between the power converter and the MSS-8 shelf.
Figure 2.51 +24 Vdc/-48 Vdc Converter unit

Table 2.40 provides details about the +24/-48 Vdc Converter card indicators.
Table 2.41 provides details about the +24/-48 Vdc Converter card connectors.
Table 2.40 +24/-48 Volt Converter card indicator details
Indicator (LED)

Status

Definition

Status (top)

Off

Card not equipped, not powered, or hardware


failure has been detected.

Green

Normal operation (input and output)

Off

Card not equipped, not powered, or no failure is


detected.

Red

PSU Failure indication detected.

PSU Failure Indication


(bottom)

Table 2.41 +24/-48 Volt Converter card connector details

208

Connector

Function

+24 Vdc Input

Station Battery and Return

-48 Vdc Output

Ethernet interconnect

User Manual 3DB19901AFAA Edition 01

Functional description

2.8.1.4 AC Converter unit for MSS-O


An AC converter unit is required to provide AC power to the MSS-O shelf.
The power converter can be used only with MSS-8 shelf, in combination with FAN unit
(3EM23911AAAA) and, for max efficiency, positioned in slots 4, 6 or 8.
Office power (+24 Vdc) is connected to the PDU which in turn connects to the power
converter.
The output of the Power Converter (-48 Vdc) is then connected to the MSS-8 shelf power
connector(s).
The Power Converter supports both unprotected and protected power arrangements.
The same PDU power cables are used to connect between the PDU and the power
converter.
Keyed power cables are used to connect between the power converter and the MSS-8 shelf.
Figure 2.52 +24 Vdc/-48 Vdc Converter unit

Table 2.40 provides details about the +24/-48 Vdc Converter card indicators.
Table 2.41 provides details about the +24/-48 Vdc Converter card connectors.
Table 2.42 +24/-48 Volt Converter card indicator details
Indicator (LED)

Status

Definition

Status (top)

Off

Card not equipped, not powered, or hardware


failure has been detected.

Green

Normal operation (input and output)

Off

Card not equipped, not powered, or no failure is


detected.

Red

PSU Failure indication detected.

PSU Failure Indication


(bottom)

User Manual 3DB19901AFAA Edition 01

209

Functional description

Table 2.43 +24/-48 Volt Converter card connector details


Connector

Function

+24 Vdc Input

Station Battery and Return

-48 Vdc Output

Ethernet interconnect

2.8.1.5 Core-E unit


Figure 2.53 Core-E unit

Based on packet technology with 7 GbEth serial internal interfaces between Core-E
and peripherals (jumbo frames 9728 bytes allowed)

4x10/100/1000 Ethernet electrical embedded interface (RJ45): port #1 to port #4

2 optional SFPs: port #5 and port #6

The Ethernet ports of the Core-E can be configured in 2 ways:


1.

to be used as GigaEthernet interface for Ethernet traffic (Note: for port#5 and port#6
the optional SFP must be installed);

2.

to be used to connect an MPT: MPT-HC/HC-HQAM, MPT-XP/XP-HQAM, or


MPT-MC to port#1 to port#4; an MPT-HC/HC-HQAM, MPT-XP/XP-HQAM only
to port#5 and port#6.

The flash card stores the license type, the equipment software, the equipment MIB and the
equipment MAC address.

210

User Manual 3DB19901AFAA Edition 01

Functional description
2.8.1.5.1 Main Functions

Controller

Layer 2+ Eth Switch, VLAN management & MAC based

Ethernet MAC learning

x-connect function for PDH and Data payload traffic;

For any packetized flow, the switch will be in charge to manage the EPS also.

QoS management.

Rate limiting by port

Rate limiting by VLAN

Storm control

VLAN translation

Selection of the synchronization clock to be distributed to all plug-in.

The Core-E unit has the option to equip two SFPs (in port #5, port #6). These ports can be
also used to connect directly an MPT-HC/HC-HQAM/XP/XP-HQAM.

2.8.1.5.2 Available SFPs for port #5 and port #6


The following SFPs are available:

1000BASE-LX (optical interface for Ethernet traffic)

1000BASE-SX (optical interface for Ethernet traffic)

1000BASE-T (electrical interface for Ethernet traffic)

2xE1 (electrical interface for 2 E1 streams)

E3 (electrical interface for 1 E3 stream)

EoSDH (optical interface for STM-1 signal with Ethernet traffic encapsulation)

2.8.1.5.2.1 2xE1 SFP


The 2xE1 SFP is an SFP module supporting MEF8 circuit emulation of up to 2 E1.
This module supports:

differential clock recovery

node timing

loop timing

User Manual 3DB19901AFAA Edition 01

211

Functional description

This module is Synchronous Ethernet capable and it is compliant to optical SFP


1000BASE-X. It can deliver the clock recovered from one of two tributaries to hosting card
through the standard SFP pin-out.
SFP module supports TDM2TDM and TDM2ETH services.
The port, in which the SFP has been installed, must be enabled by the WebEML as an
optical port, then all the configuration must be done with an Enhanced Configuration File.
Note: The SFP must be installed after the Configuration File has been downloaded. If the
SFP has been installed before, remove it and then plug it again.

2.8.1.5.2.2 E3 SFP
The E3 SFP is an SFP module supporting the circuit emulation of one E3.
The E3 frame is encapsulated in packets and transmitted to the switch via serial link
between SFP and Core unit. A VLAN ID must be assigned to the packets, encapsulating
the E3 stream. On the destination MPR node, the E3 frame is rebuilt by a peer E3 SFP on
the Core unit.
The input/output connectors are microcoaxial 1.0/2.3 connectors.
Note: Dip switches located on bottom side of the SFP are reserved for factory use only.

2.8.1.5.2.3 EoSDH SFP


The Ethernet over SDH SFP is an SFP module supporting the delivery of Ethernet traffic
over SDH layer by GFP encapsulation.
The module is compliant to 1000BASE-X specification and support one STM1 interface.
The NE manages the EoSDH SFP as an optical User Ethernet interface. Synchronous
operation mode and SSM support are not available, when EoSDH SFP is hosted as optical
User Ethernet interface.
Note: For the correct operation of the EoSDH SFP it is necessary to disable the
autonegotiation using the WebEML or the Configuration File (see the Configuration File
User Manual).

212

User Manual 3DB19901AFAA Edition 01

Functional description

Note: The related rate limiter must be set on the port where the EoSDH SFP is in use. The
following values must be entered:

Rate limiter 133 Mb/s


Burst 4 Kbit
Note: Dip switches located on bottom side of the SFP are reserved for factory use only.

Figure 2.54 Core-E unit

Warning: The optional optical SFP plug-in, which has to be installed in port #5 and port
#6 of the Core-E unit, contains a Class 1 laser source. The laser source is placed in the left
side of the SFP plug-in.

According to the IEC 60825-1 the explanatory label is not sticked on the equipment due to
the lack of space.

2.8.1.6 32xE1 Local Access unit

User Manual 3DB19901AFAA Edition 01

213

Functional description
Figure 2.55 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 the 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 bidirectional interfaces on the backplane.
Figure 2.56 PDH Access unit

214

User Manual 3DB19901AFAA Edition 01

Functional description

Table 2.44 provides details about the PDH Access unit indicators.
Table 2.45 provides details about the PDH Access unit connectors.
Table 2.44 P32E1DS1 DS1 card front panel indicator details
Indicator

Status

Definition

Status (S)

Off

Card not equipped, not provisioned, or not


powered

Green blinking

Download, Software Booting, or Flash Card


Realignment in Progress

Green

In Service, Normal Operation, and Properly


Provisioned

Yellow

In Protect, Properly Provisioned as EPS

Red

Card Fail

Red blinking

Card Mismatch

Table 2.45 P32E1DS1 DS1 card front panel connector details


Connector

Type

Function

I/O (16-1)

64 position SCSI connector

E1, Tx and Rx (tip and ring),


interconnect E1s number 1 through 16

I/O (32-17)

64 position SCSI connector

E1, Tx and Rx (tip and ring),


interconnect E1s number 17 through 32

2.8.1.7 2xSTM-1 Local Access unit

User Manual 3DB19901AFAA Edition 01

215

Functional description
Figure 2.57 2xSTM-1 Local Access unit

This unit can manage up to 2xSTM-1 by installing two optional STM-1 SFP plug-ins
(electrical or optical).
The STM-1 unit can be used in two different working modes, addressing two different
network scenarios:

STM-1 channelized

STM-1 transparent

The STM-1 channelized mode is available by provision the unit as "SDHCHAN" and the
STM-1 transparent mode is available by provision the unit as "SDHACC".
The STM-1 unit can support 1 channelized STM-1 or up to 2 transparent STM-1 interfaces.
The STM-1 channelized interface works as a terminal multiplexer; it terminates or
originates the SDH frame. It multiplexes NxE1 into an STM-1 electrical/optical line
connection. The clock source can be Loop time or Node time. Typical application is a
direct connection to SDH add-drop multiplexers (ADMs). STM-1 card manages one 155
Mbit/s STM1 interface and up to 63xE1. Standard VC4 mapping of lower-order E1 traffic
streams to/from STM-1 is applied, that means that a VC4 directly maps up to 63xVC12 into
an STM-1 signal (in turn each VC12 contains 1xE1).
Link options include:

1+0 non-protected operation

1+1 EPS protection (available ONLY with the optical interface)

When the protection of the unit is required (1+1 EPS protection), two STM-1 units must be
installed.
216

User Manual 3DB19901AFAA Edition 01

Functional description

Clock source from the incoming STM-1 signal can be selected as Network Element source
clock. In the event the clock source is lost, clocking falls back to the internal clock or to
other of any synch in options.
In the Tx direction, the STM-1 Local Access unit processes and encapsulates up to 2xSTM1 input lines into an Ethernet packet that is sent to the Core-E card(s).
In the Rx direction, the STM-1 Local Access unit extracts data from the Ethernet data
packets and processes the data to provide up to 2 STM-1 output lines.
The 2xSTM-1 Local Access Unit performs the following macro functions:

Transparent or channelized transport of the STM-1

Encapsulation/Extraction of the STM-1 into/from standard Ethernet packets Inter


Working Function

Reconstruction of the original STM-1 Timing

Selection of the Active Core-E

Sending/getting those std Eth packets to the Core-E module

Communication with the Controller for provisioning and status report

The unit communicates with the Core-E modules through two GbEth Serial copper bidirectional interfaces on the backplane.
Figure 2.58 STM-1 Access unit

Table 2.46 provides details about the STM-1 Access unit indicators.
Table 2.47 provides details about the STM-1 Access unit connectors.

User Manual 3DB19901AFAA Edition 01

217

Functional description

Table 2.46 STM-1 Access unit front panel indicator details


Indicator (LED)

Status

Definition

Status (S)

Off

Card not equipped, not provisioned, or not


powered

Green blinking

Download, Software Booting, or Flash Card


Realignment in Progress

Green

In Service, Normal Operation, and Properly


Provisioned

Yellow

In Protect, Properly Provisioned as EPS

Red

Card Fail

Red blinking

Card Mismatch

Table 2.47 STM-1 Access unit front panel connector details


Connector

Type

Function

SFP Port 1-2

SFP

STM-1 electrical/optical port

2.8.1.8 ASAP unit


The ASAP unit is used to transport 16xE1 ATM traffic, with E1/IMA physical layer, in an
MPR network.
The ASAP units are unprotected (No 1+1 EPS is available).
ATM traffic is transported within MPR network as "special" Ethernet traffic.
This "special" Ethernet traffic is managed by MPR following to RFC 4717 (IETF ATM
PseudoWire EdgetoEdgeEmulation, 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

218

16xE1 G.704 supporting ATM/IMA

IMA protocol 1.1

Node-timed/loop-timed E1 port synch


User Manual 3DB19901AFAA Edition 01

Functional description

ATM PWE3 encapsulation with N-to-one (N=1) encapsulation format (RFC 4717)

Max 8 IMA group

Max 16 E1 per IMA group

The IMA group must be in the same ASAP card

Ingress/Egress VPI translation

Transport of ATM traffic can be done in VCC mode or VPC mode (all the nodes of
the MPR chain must have the same mode):

VCC mode

It is possible to transport max 48 VC for every IMA group. It is possible


to manage VC switching (= VCI and VPI change)

It is possible to assign at every VC one specific QoS. Policing and shaping


at ATM level has performed VC mode only

The VC of the same class level (CBR / UBR+ / UBR) are managed in the
same radio queue, then are available 3 different radio queues

VPC mode

It is possible to transport max 48 VP for every IMA group. It is possible


to manage only VP switching (=only VPI change)

All the VC inside the VP must have same QoS (= for ex. all CBR or all
UBR)

The radio QoS (= radio tails) and QoS ATM (=policing and shaping) is
managed only at VP level.
Note: The sum of VP + VC configured on a single ASAP card must be
<128.

Interfaces

16 E1 G.704 - SCSI Connectors

75 ohm or 120 ohm (at NE level)

Block Diagram
(Refer to Figure 2.59).
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:

User Manual 3DB19901AFAA Edition 01

219

Functional description

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 multiframe 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 different 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 2.59 ASAP simplified block diagram

220

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.60 ASAP unit

2.8.1.9 Modem unit


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

User Manual 3DB19901AFAA Edition 01

221

Functional description

Classification of incoming packets from the Core-E (QoS)

Fragmentation

Air Frame Generation (synchronous with NE clock)

Digital Modulator
TX Analog Chain

DAC & low pass filtering

Modulation to 311 MHz IF TX

In Rx direction, the MODEM 300 Module terminates the IF signal coming from the
ODU300 extracting the original CBR and then the original Ethernet packets to be given the
Core-E which distributes them to the proper Module.
RX Analog Chain

126 MHz IF RX demodulation to I & Q

low pass filtering & ADC

Digital Demodulator

Carrier & CK recovery

Equalisation

Error Correction

Digital Deframer

222

RPS (hitless)

Defragmentation

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.62 Modem unit

2.8.1.10 MPT Access Unit (with PFoE)

User Manual 3DB19901AFAA Edition 01

223

Functional description
Figure 2.63 MPT Access unit (with PFoE) block diagram

The MPT Access Unit is the interface for up to two MPT-HC/HC-HQAM/MC/XP/XPHQAMs.


The two MPTs can be configured in unprotected or protected configuration.
The connection to the MPT-HC/HC-HQAM can be realized:
a.

by using only one electrical Ethernet cable with the enabling of the PFoE (Power Feed
over Ethernet) function (Ethernet traffic + Power Supply on the same cable)

b.

or by using two connectors:

one Gigabit Ethernet connector (optical) to send the Ethernet traffic and the
Ethernet control frames to the MPT-HC/HC-HQAM

one DC power supply connector to send the power supply to the MPT-HC/HCHQAM

The connection to the MPT-MC is realized by using only one electrical Ethernet cable with
the enabling of the PFoE (Power Feed over Ethernet) function (Ethernet traffic + Power
Supply on the same cable)
The connection to the MPT-XP/XP-HQAM can be realized:
a.

224

by using electrical Ethernet cable: The electrical Ethernet port MUST be connected
to the MPT Extended Power Unit IDU Data port. The MPT Extended Power Unit
DC+ODU Data port then provides the PFoE (Power Feed over Ethernet) function
(Ethernet traffic + Power Supply on the same cable) to the MPT-XP/XP-HQAM

User Manual 3DB19901AFAA Edition 01

Functional description

b.

or by using one data and one power cable:

one Gigabit Ethernet connector (optical) to send the Ethernet traffic and the
Ethernet control frames to the MPT-XP/XP-HQAM

DC power supply MUST be provided by the MPT Extended Power Unit


DC+ODU Data or DC connector to send the power supply to the MPT-XP/XPHQAM

If an optical port is used, an SFP plug-in must be installed into the MPT Access Unit.
Note: When port #1 is enabled (optical or electrical), the associated Power Supply port is
#1.

Note: When port #2 is enabled (optical or electrical), the associated Power Supply port is
#2.

Note: When MPT-XP/XP-HQAMs are used, the associated Power Supply port must be
disabled.

Main Functions

Provide the power supply interface and the Ethernet interface

Provide the Power Feed over Ethernet function

Lightning and surge protection

Ethernet and power interface supervision

EPS/HSB management function

Clock distribution function

L2 packet based Proprietary clock algorithm

Ethernet link quality monitor function

Radio Link Quality notification through MPR Protection Protocol frames

Communication with Core controller for provisioning and status report.

User Manual 3DB19901AFAA Edition 01

225

Functional description
Figure 2.64 MPTACC card (MSS/MPTACC)

Table 2.48 MPTACC front panel indicator details


INDICATOR

STATUS

DEFINITION

Power Emission Status (M)

Off

No Output Power (e.g.: Hot-Standby Transmitter, Software is


Booting, or FPGA Downloading is In-Progress)

Green

Normal Output Power

Yellow

Forced Squelch Enabled on Craft Terminal or unit is in


Protect, Properly Provisioned as EPS, or Squelch enabled
related to HSB protection

Off

Card not equipped, not provisioned, or not powered

Green Blinking

Download, Software Booting, or Flash Card Realignment in


Progress

Green

In Service, Normal Operation, and Properly Provisioned

Status (S)

In an EPS configuration, the MPTs configured on the card are


active
Yellow

In Standby, Properly Provisioned as EPS, or


Squelch enabled related to HSB protection

LINK

ACTIVITY

226

Red

Card Fail

Red Blinking

Card Mismatch

Off

Indicates GigE link is down

Green

Indicates GigE link is up

Off

Indicates no activity on GigE link

Amber Blinking

Indicates activity on GigE link

User Manual 3DB19901AFAA Edition 01

Functional description

Table 2.49 MPTACC front panel connector details


CONNECTOR

TYPE

FUNCTION

GigE Ports 1, 2

RJ45

Electrical GigE Ethernet Radio Port

GigE Ports 3, 4

SFP

Optical GigE Ethernet Radio Port

DC 1, 2

SMA

DC Power Supply Port 1 and 2

Warning: The optional SFP plug-in, which has to be installed in the MPT Access unit,
contains a Class 1 laser source. The laser source is placed in the left side of the SFP plugin.
According to the IEC 60825-1 the explanatory label is not attached to the equipment due
to the lack of space.

2.8.1.11 EAS unit


The EAS unit (P8ETH) offers eight 10/100/1000 Ethernet interfaces.
An embedded 10 Gbit/sec L2 switch is present on the unit.
There are 4 Electrical 10/100/1000 base-T electrical ports (port #1 to port #4) and 4 optical
SFP - LX, SX or CX (port #5 to port #8).
Port #5 to port #8 (by installing an SFP SX) can also be used to connect an MPT-HC/HCHQAM/XP/XP-HQAM in 1+0 configuration. The MPT-HC/HC-HQAM/XP/XP-HQAM
can be grouped to create an L1 Radio LAG.

User Manual 3DB19901AFAA Edition 01

227

Functional description
Figure 2.65 EAS unit block diagram
P8ETH Ethernet Access Switch
SFP
SFP
SFP
SFP

SerDes From/to Mate P8ETH (FPS0)

SerDes

SerDes From/to Mate P8ETH (FPS1)

SerDes
SerDes

FPGA

25 MHz CSM Act & Stby


ISPB

SerDes
Control
Bus

SerDes

Backplane
SerDes Core-E Main

RJ45
RJ45
RJ45
RJ45

Giga
XSwitch

SerDes
SerDes
SerDes

Ethernet
Switch

SerDes Core-E Spare

SerDes From/to Mate P8ETH (FPS0)


SerDes From/to Mate P8ETH (FPS1)

SerDes

Legend:
1.25 GHz SerDes
23792

228

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.66 EAS unit

2.8.1.12 EASv2 unit


The EASv2 unit offers eight interfaces. The EASv2 unit can provide PFoE to up to four
MPTs.
An embedded 10 Gbit/sec L2 switch is present on the unit.
There are 4 Electrical 10/100/1000 base-T electrical ports (port #1 to port #4) and 4 optical
SFP - LX, SX or CX (port #5 to port #8). The electrical Ethernet ports can be configured to
perform as any of the following:

User Ethernet port

MPT connection with PFoE

MPT connection without PFoE

PFoE only

Port #5 to port #8 (by installing an SFP SX) can also be used to connect an MPT-HC/HCHQAM/XP/XP-HQAM, or MPT-HLS in 1+0 configuration. The MPT-HC/HC-HQAM/
XP/XP-HQAM connected to EASv2 optical or electrical ports can be grouped to create an
L1 Radio LAG.

User Manual 3DB19901AFAA Edition 01

229

Functional description

The EASv2 is compatible with the MSS backplanes shown in Table 2.50.
Table 2.50 MSS backplanes compatible with EASv2
Description of subrack

Backplane part
number

Hardwired code

Backplane RI
mnemonic

2U, 8 slots, 1Gb/s, no


RI.Seep

3DB18008AAAA

11000

2U, 8 slots, 1Gb/s, with


R.I.Seep

3DB18008BAAA

11010

BACK2U

1U, 4 slots, 1 Gb/s, with


R.I.Seep

3DB18216BAAA

11111

BACK1U

2U, 8 slots, 2.5 Gb/s, EVO 1st

3DB18008CAAA

11001

BACK2U

2U, 8 slots, 2.5 Gb/s, EVO


2nd

3DB18008CBAA

01010

BACK2Uv2

Table 2.51 provides EASv2 unit indicators details.


Table 2.51 EASv2 front panel indicator details
INDICATOR

STATUS

DEFINITION

Status (S)

Off

Card not equipped, not provisioned, or not


powered

Green
Blinking

Download, Software Booting, or Flash Card


Realignment in Process

Green

In-Service, Normal Operation, and Properly


Provisioned

Yellow

In Protect, Properly Provisioned as EPS

Red

Card Fail

Red Blinking

Card Mismatch or not equipped

Off

Link Down

On

Link Up

Off

No Tx/Rx activity

Blinking

Tx/Rx activity

Off

No power present

Yellow

Power present

Link (green)

Activity (yellow)

PFoE

230

User Manual 3DB19901AFAA Edition 01

Functional description

Table 2.52 provides EASv2 unit connector details.


Table 2.52 EASv2 front panel connector details
Port

Interface type

Function

MPT-HC/HC-HQAM/
MPT-XP/XP-HQAM 1
port

RJ45

10/100/1000BaseT Ethernet
Port with PFoE

RJ45

10/100/1000BaseT Ethernet
Port with PFoE

RJ45

10/100/1000BaseT Ethernet
Port with PFoE

X1

RJ45

10/100/1000BaseT Ethernet
Port with PFoE

SFP

GigE Ethernet optical

X2

SFP

GigE Ethernet optical

X2

SFP

GigE Ethernet optical

X2

SFP

GigE Ethernet optical

X2

1.

An MPT Extended Power Unit is required to connect an MPT-XP/XP-HQAM to all


RJ45 (electrical) ports.

2.

A power injector device (Power Injector Card/Box, MPT Power Unit, MPT Extended
Power Unit) is required to connect an MPT-HC/HC-HQAM to SFP (optical) ports.
An MPT Extended Power Unit is required to connect an MPT-XP/XP-HQAM to these
ports.

User Manual 3DB19901AFAA Edition 01

231

Functional description
Figure 2.67 EASv2 unit

2.8.2 MSS (Indoor/Outdoor unit)


The MSS-O can be installed indoors or outdoors. The MSS-O is made of:

1 monoboard

Ethernet ports that provide the functions of a Core-E Module

The MSS-O supports PFoE and connection to radios that can be connected to a Core-E
module.

2.8.3 Power Injector


The Power Injector is an indoor device designed to deliver the DC power supply to MPT
(as shown in MSS to Outdoor Unit interconnections) by using the same cable carrying the
Ethernet traffic.
The Power Injector receives at the input the Ethernet traffic and the power supply on two
dedicated connectors and sends to the output on one connector the Power Supply + Ethernet
Traffic. This solution, called PFoE (Power Feed over Ethernet), is proprietary.
The Power Injector can power up to 2 MPT.
The two Power Supply Sources provide power supply redundancy.

232

User Manual 3DB19901AFAA Edition 01

Functional description

Main functions of the injector

Securing of two DC power inputs from -48V battery

Low pass filtering

Insertion of the DC voltage on two Ethernet streams to power two MPT units

Surge protection on both Ethernet output ports (K44 & K45)

Power Injector versions


Two versions are available:
1.

Power Injector card: installed in the MSS shelf and powered through the backplane.
Figure 2.68 Power Injector card

The Power Injector card is not managed by MSS. The Plug-in just needs an empty
slot to be inserted in. As consequence, no specific commissioning activity is needed
to insert a Power Injector card on a existing MSS shelf.
2.

Power Injector box: stand-alone box, powered through two connectors on the front
providing power supply redundancy. The box can be mounted in a rack by means of
a separate bracket. The bracket supports one or two boxes (1.3U).
Figure 2.69 Power Injector box

Connectors

Two DC connectors in the front (for box version), or power from the backpanel (for
plug-in version).

Two RJ45 for the data in (DATA)

Two RJ45 for the data + DC out (DC+DATA)

LEDs

Two LEDs indicate the presence of DC voltage on each Ethernet output.

User Manual 3DB19901AFAA Edition 01

233

Functional description
Figure 2.70 Power Injector front panel

2.8.4 ODU300
The ODUs include a waveguide antenna port, type-N female connector for the ODU cable,
a BNC female connector (with captive protection cap) for RSSI access, and a grounding
stud.
The ODUs, are designed for direct antenna attachment via a 9500 MPR-E-specific
mounting collar supplied with the antennas.
ODU polarization is determined by the position of a polarization rotator fitted within the
antenna mounting collar.
A remote ODU mounting kit is also available as an option. These may be used to connect
an ODU to a standard antenna, or to a dual-polarized antenna for co-channel link operation.
ODUs are fixed for Tx High or Tx Low operation.
Where two ODUs are to be connected to a single antenna for hot-standby or frequency
diversity configurations, a direct-mounting coupler is used. They are available for equal or
unequal loss operation. Balanced loss is nominally 3 dB. Unbalanced loss is nominally 1/6
dB.
The ODU assembly meets the ASTME standard for a 2000 hour salt-spray test, and relevant
IEC, UL, and Bellcore standards for wind-driven rain.
The ODU housing comprises:

234

Cast aluminium base (alloy 380)

Pressed aluminium cover (sheet grade alloy 1050).

Base and cover passivated and then polyester powder coated

Compression seal for base-cover weatherproofing

Carry-handle

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.71 ODU300 housing

ODUs are frequency-band specific, but within each band are capacity-independent up to
their design maximums.

2.8.4.1 ODU block diagram


Figure 2.72 shows the ODU block diagram.

User Manual 3DB19901AFAA Edition 01

235

Functional description
Figure 2.72 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.

236

User Manual 3DB19901AFAA Edition 01

Functional description

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.4.2 RSSI Monitoring Point


The ODU has a capped BNC female connector to access RSSI during antenna alignment.
There is a linear relationship of voltage to RSSI, as shown in the table below; an RSSI of
0.25 Vdc is equivalent to -10 dBm RSSI, and each additional 0.25 Vdc RSSI increase
thereafter corresponds to a 10 dBm decrease in RSSI.
The lower the voltage the higher RSSI and better aligned the antenna is.
Table 2.53 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.4.3 Waveguide Flange Data


Table 2.54 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.

User Manual 3DB19901AFAA Edition 01

237

Functional description

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.

Radio Flange

Waveguide Mating Flange

Waveguide Type

Spring Washers Reqd

Bolts Reqd

Bolt Type

Thread Spec

Hole Depth mm

6 GHz

UDR70

PDR70

WR137

8 x M5

M5x0.8

6H

10

Flange thickness +
Hole depth - 2mm

7/8 GHz

UDR84

PDR84

WR112

8 x M4

M4x0.7

6H

Flange thickness +
Hole depth - 2mm

10/11 GHz

UDR100

PDR100

WR90

8 x M4

M4x0.7

6H

Flange thickness +
Hole depth - 2mm

13 GHz

UBR120

PBR120

WR75

4 x M4

M4x0.7

6H

Flange thickness +
Hole depth - 2mm

15 GHz

UBR140

PBR140

WR62

4 x M4

M4x0.7

6H

Flange thickness +
Hole depth - 2mm

18/23/25
GHz

UBR220

PBR220

WR42

4 x M3

M3x0.5

6H

Flange thickness +
Hole depth - 2mm

28/32/38
GHz

UBR320

PBR320

WR28

4 x M3

M3x0.5

6H

Flange thickness +
Hole depth - 2mm

Bolt Length Required

Freq Band

Table 2.54 Waveguide Flange Data

2.8.4.4 ODU Coupler


The ODU coupler is used in the 1+1 HSB or 1+1/2x(1+0) FD co-polar configurations.
The coupler can be equal type (3 dB/3 dB insertion loss) or unequal type (1.5 dB on the
main path/6 dB on the secondary path).

238

User Manual 3DB19901AFAA Edition 01

Functional description

The couplers are connected between the cabinets and the antenna.

2.8.5 MPT-HC/HC-HQAM/XP/XP-HQAM
MPT-HC/HC-HQAM/XP/XP-HQAM (Microwave Packet Transport) is a Microwave
Equipment capable to transport the Ethernet traffic over an RF radio channel.
The MPT-HC/HC-HQAM/XP/XP-HQAM includes a waveguide antenna port, a
maintenance connector (with captive protection cap) for RSSI access, 1 electrical GE
interface (PFoE or power only), 2 GE optical interfaces (1 for data, 1 for RPS) and a
grounding stud.
MPT-HC/HC-HQAM/XP/XP-HQAM can be natively Ethernet powered through a
proprietary PFoE.
MPT-HC/MPT-XP is able to host external modules (RPS module for 1+1 configurations or
XPIC_RPS module for XPIC and/or 1+1 configurations)
MPT-HC-HQAM/XP-HQAM transceivers include integrated XPIC and RPS functions. No
hardware modules are required. An RTU license is required to enable XPIC functions.
The MPT-HC/HC-HQAM/XP/XP-HQAM can be installed on an integrated antenna or on
standard poles, wall or pedestal mount, with an appropriate fastening system.
The MPT-HC/HC-HQAM/XP/XP-HQAM (one or two depending on the configuration 1+0
or 1+1) incorporates the complete RF transceiver and can be associated with an integrated
or separate antenna.
The cabinet is a very compact and robust weatherproof (IP 67) container, designed to be
compatible with hot and very sunny climatic zones.
The MPT-HC/HC-HQAM/XP/XP-HQAM can be rapidly installed on standard poles with
an appropriate fastening system. The pole mounting is the same for 1+0 or 1+1
configurations from 6 to 38 GHz.
The MPT-HC/HC-HQAM/XP/XP-HQAM is fixed by means of quick latches. This system
allows to change the MPT-HC/HC-HQAM/XP/XP-HQAM without altering antenna
pointing.
For the following, when an external diplexer is in use, the MPT polarization is determined
by the rotation of the transceiver in 1+0 configuration and by the position of a polarization
rotator fitted within the coupler in 1+1 configuration:

MPT-HC: 5,8 / L6 / U6 / 7 / 8 / 10.5 GHz

MPT-HC-HQAM: L6 / U6 / 7 / 8 / 11 GHz

MPT-XP: L6 / U6 / 7 / 8 GHz

User Manual 3DB19901AFAA Edition 01

239

Functional description

MPT-XP-HQAM: L6 / U6 / 7 / 8 / 11 GHz

For the following, when an internal diplexer is in use, the MPT polarization is determined
by the rotation of the nose fitted in the antenna port of the transceiver in 1+0 configuration
and by the position of a polarization rotator fitted within the coupler in 1+1 configuration:

MPT-HC: L6, U6 GHz (old products no longer manufactured) / 11GHz to 38 GHz

MPT-HC-HQAM: 13 GHz to 38 GHz

Where two MPT-HC/HC-HQAM/XP/XP-HQAM have 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.
Unequal is nominally 1/10 dB.
Two mechanical solutions are adopted:
1.

with embedded diplexer for cost optimisation, as shown in Figure 2.73, where the
diplexer is internal to the MPT ODU cabinet; this type of MPT ODU is identified by
one Logistical Item only.
Table 2.55 lists the MPT ODUs that can support an embedded diplexer.
Table 2.55 MPT ODUs that support an embedded diplexer
Radio

Frequency range

MPT-HC

L6
U6 GHz (old products no
longer manufactured)
11 GHz to 38 GHz

MPT-HC-HQAM

13 GHz to 38 GHz

MPT-XP

Not supported

MPT-XP-HQAM

Not supported

Figure 2.73 shows an MPT-HC with an embedded diplexer.

240

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.73 MPT-HC/XP housing (embedded diplexer)

Warning: To mount a 6 GHz MPT-HC with internal diplexer in a 1+1 configuration with a
MPT-HC with external diplexer, the MPT with internal diplexer must be the Main unit and
the MPT with external diplexer must be the Spare unit, see Figure 2.74. If the units are
mounted the other way, the cabling will cause interference; see Figure 2.75.

User Manual 3DB19901AFAA Edition 01

241

Functional description
Figure 2.74 Correct protected mounting of 6 GHz MPT-xC with internal and
external diplexers

242

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.75 Incorrect protected mounting of 6 GHz MPT-xC with internal and
external diplexers

2.

with external diplexer: due to a high number of shifters, the diplexer is external for
the flexibility of the shifter customization, where MPT ODU is composed of two
independent units: the external diplexer assembly (containing the diplexer) and the
RF transceiver assembly (containing the RF section); each of this type of MPT ODU
is identified by two Logistical Items, one for the external diplexer assembly and
another for the RF transceiver assembly. To read the external diplexer assembly
identification label, it is necessary to separate the external diplexer assembly from the
RF transceiver assembly.
Table 2.56 lists the MPT ODUs that can support an external diplexer.

User Manual 3DB19901AFAA Edition 01

243

Functional description

Table 2.56 MPT ODUs that support an external diplexer


Radio

Frequency range

MPT-HC

5.8/L6/U6/7/8/10.5 GHz

MPT-HC-HQAM

L6/U6/7/8/11 GHz

MPT-XP

L6/U6/7/8 GHz

MPT-XP-HQAM

L6/U6/7/8/11 GHz

Figure 2.76 shows an example of an MPT-HC-HQAM with an external diplexer.


Figure 2.76 View of MPT-HC-HQAM with external diplexer (13-38 GHz)

MPT-HC/HC-HQAM/XP/XP-HQAM is broken down into the following sections:

244

MPT-CB: Common Belt section. This section is frequency independent, and all the
features relevant to this unit are common to all the MPT RF options.

MPT-RF: Radio Frequency section that is frequency dependent.

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.77 MPT system

The MPT-HC/HC-HQAM/XP/XP-HQAM interface is based on a Gb Ethernet, that can be


either optical or electrical depending on the needs and the cable length. If the optical port
has/have to be used (data and/or RPS port), the corresponding SFP plug-in must be
installed.
Figure 2.78 MPT-HC/XP housing (internal diplexer)

User Manual 3DB19901AFAA Edition 01

245

Functional description
Figure 2.79 MPT-HC/XP housing (external diplexer)

Figure 2.80 MPT-XP housing (external diplexer)

2.8.5.1 RSSI Monitoring Point


The RSSI is available on the maintenance LEMO connector and is used to manually point
the antenna on the field.
The higher the voltage the higher RSSI and better aligned the antenna is.

246

User Manual 3DB19901AFAA Edition 01

Functional description

Table 2.57 RSSI Table


Units

Measurement (with MPT-HC/HC-HQAM/XP/XP-HQAM)

BNC (Vdc)

4.71

4.12

3.5

2.9

2.3

1.71

1.11

0.59

0.14

RSL (dBm)

-10

-20

-30

-40

-50

-60

-70

-80

-90

-100

2.8.5.2 Waveguide Flange Data

L6 GHz

U6 GHz

5.8 GHz

7 GHz

8 GHz

10.5 GHz

11 GHz

13 GHz

15 GHz

18 GHz

23 GHz

25 GHz

38 GHz

Wave- guide Type

Table 2.58 Waveguide Flange Data

WR137

WR137

WR137

WR112

WR112

WR75

WR75

WR62

WR62

WR42

WR42

WR42

WR28

2.8.5.3 MPT-HC/HC-HQAM/XP/XP-HQAM Coupler


The coupler is used in the 1+1 HSB or 1+1/2x(1+0) FD co-polar configurations.
The coupler can be equal type (3 dB/3 dB insertion loss) or unequal type (1 dB on the main
path/10 dB on the secondary path).
The couplers are connected between the MPT and the antenna.

2.8.5.4 MPT-HC/HC-HQAM/XP/XP-HQAM Integrated OMT (Orthogonal


Mode Transducer)
The OMT are used in the 1+1 or 2+0 FD cross-polar configurations.
The OMT are connected between the MPT and the antenna.

User Manual 3DB19901AFAA Edition 01

247

Functional description

2.8.6 MPT-MC
MPT-MC is similar to MPT-HC from an architecture standpoint. The only differences are:
1.

MPT-MC is natively Ethernet powered through a proprietary PFoE

2.

MPT-MC cannot be connected in optical 100m length cable limitation.

3.

MPT-MC is not delivered with a solar shield.

4.

XPIC is not supported with MPT-MC. RPS is supported only with a cable.

Two mechanical solutions are adopted:


1.

with embedded diplexer for cost optimisation (L6 GHz, U6 GHz, and from 11 to 38
GHz), where the diplexer is internal to the MPT-MC cabinet; this type of MPT-MC
is identified by one Logistical Item only;

2.

with external diplexer: due to a very high number of shifters, the diplexer is external
for the flexibility of the shifter customization (L6, U6, 7, and 8 GHz), where MPTMC is composed of two independent units: the external diplexer assembly
(containing the diplexer) and the RF TRANSCEIVER assembly (containing the RF
section); each of this type of MPT-MC is identified by two Logistical Items, one for
the external diplexer assembly and another for the RF TRANSCEIVER assembly. To
read the external diplexer assembly identification label, it is necessary to separate the
external diplexer assembly from the RF TRANSCEIVER assembly.

Warning: To mount a 6 GHz MPT-MC with internal diplexer in a 1+1 configuration with a
MPT-MC with external diplexer, the MPT with internal diplexer must be the Main unit and
the MPT with external diplexer must be the Spare unit, see Figure 2.74. If the units are
mounted the other way, the cabling will cause interference; see Figure 2.75.

248

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.81 MPT-MC housing (internal diplexer)

Figure 2.82 MPT-MC housing (external diplexer)

User Manual 3DB19901AFAA Edition 01

249

Functional description

2.8.6.1 MPT-MC Coupler


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

2.8.7 MPT-HLS
The MPT-HLS is a fully indoor radio system, adapted to long haul and cabinet
requirements, able to transport the Ethernet traffic over an RF radio channel.
The MPT-HLS radio is installed in an ETSI rack. Inside the ETSI rack 2 different RT
subracks can be hosted with up to 10 transceivers in each. Four different ETSI racks are
available (2200, 2000, 1700, 1300 mm). The system can also be installed in a 9600 LSY
rack.
Inside the ETSI rack 2 different RT subracks can be hosted. The following configurations
are available:

Up to 10 MPT-HLS co-polar in one RT subrack

Up to 5 MPT-HLS alternate polar (with two diplexers and a dual polarization


antenna) or XPIC in one RT subrack

Up to 20 MPT- HLS in XPIC on 2 RT subrack (due to limited RF resources): this


option is available with the 2200 mm rack only.

Mixed frequencies are supported on the same ETSI racks. There are no limitations if the
frequencies are supported by same waveguide group: 4L and 4U, 6/7and 8 GHz and 11/13
GHz. Different frequencies are managed like different polarizations.
The TRU (always protected) has to be located on the top of the ETSI rack.
For each RT subrack a fans subrack has to be installed. In this release 2 types of fan
modules can be installed on the relevant subrack.
The MPT-HLS includes integrated XPIC capability. It is able to host a diversity combiner,
which provides a second receiver. The MPT-HLS with the diversity combiner is identified
by an SD part number; see Table 2.23.
The HSB 1+1 configuration is supported in the standard RT subrack. A tight cable is
required: the RPS signals are shared between the radios using the cable.

250

User Manual 3DB19901AFAA Edition 01

Functional description

The two radios in protection have to be placed one near to the other with a kit hosting the
RF switch and an HLS with a combiner on the receiver side. In case of HSB configuration
an RF filter an RF switch are required. On the receiver side the two signals are separated
by the combiner. Two options are available: 1:10 dB (unbalanced losses) and 3:3 dB with
balanced losses on the two transceivers.
It is possible to host multiple couples of MPT-HL in 1+1 on the same subrack for an Nx
(1+1) configuration with N up to 5.
The MPT-HLS is supported on the MSS-1, Core-E Card, and EASv2 card.
Figure 2.83 shows an MPT-HLS unit.
Figure 2.83 MPT-HLS

The MPT-HLS supports the following external interfaces:

GE (SFP data port)

GE - RPS (SFP port)

RF out

RF main in

RF diversity in

HSB (RF out switch control)

Fan Mgmt

Mgmt (not used)

XPIC port

PRx (RSL port)

Table 2.59 describes the LEDs found on the MPT-HLS.

User Manual 3DB19901AFAA Edition 01

251

Functional description

Table 2.59 MPT-HLS transceiver front panel indicator details


INDICATOR

STATUS

DEFINITION

Status (S)

Off

Card not powered

Green
Blinking

FPGA Downloading, or SW Booting. (Different


blink rates identify each step of the startup
process.)

Green

In Service, Normal Operation, and Properly


Provisioned. EPS or RPS currently In-Service/
Active.

Yellow

Card Properly Equipped and Provisioned in 1+1,


currently in Standby.

Green/Red
Blinking

Card Properly Equipped and Provisioned, Rx


signal fault, EPS and RPS in Standby.

Yellow/Red
Blinking

Card Properly Equipped and Provisioned, RX


signal Fault, EPS and RPS currently in Standby.
Traffic may be affected.

Red

HW Card Fail

Power supply failure (Autotest failure)

FPGA failures

LO alarms

Modem Tx sync alarm

PA switch active

Diversity board card fail (only in combiner


mode)

RF switch fail (only for the spare MPT-HLS


in HSB configuration)

In a PA critical temperature condition, the LED


remains green.
Red Blinking

252

MAP Communication Time-out: Communication


between the MPT-HLS Transceiver and the
EASv2 cards is lost. This occurs in split-mount
configuration only.

User Manual 3DB19901AFAA Edition 01

Functional description
Table 2.59 MPT-HLS transceiver front panel indicator details (Continued)
INDICATOR

STATUS

DEFINITION

Power Emission

Off

MPT-HLS Transceiver is not emitting power,


according to the known configuration, for
example, Hot Standby.

Green

MPT-HLS Transceiver is emitting power as


expected according to the known
configuration.

Yellow

MPT-HLS Transceiver is not emitting power due


to an operator command, including manual PA
PSU switch or Tx mute.

Red

MPT-HLS Transceiver is abnormally emitting


power, in contrast with the known
configuration (for example, when Tx power
alarm is raised during normal operative mode)

Off

Link Down

On

Link Up

Off

No Tx/Rx activity

Blinking

Tx/Rx activity

SFP interface LEDs


Link (L)

Activity (A)

2.8.8 Protection schemes


2.8.8.1 Protection schemes with ODU300
Supported Protection types:
1.

RPS (Radio Protection Switching) Hitless for each radio direction (RPS-RX)

2.

EPS (Equipment Protection Switching) for each module type

3.

RPS is distributed in 9500 MSS modules before termination of 9500 MSS


frame.
Both Main and Spare modules send its own signal to the Core-E. Core-E selects
the best signal.

HSB-TPS (Hot StandBy - Transmission Protection Switch)

Spare ODU module is squelched.

User Manual 3DB19901AFAA Edition 01

253

Functional description
2.8.8.1.1 RPS Switching Criteria
The switching criteria are:

SF (Signal Fail): generated from transmission and equipment alarms affecting the Rx
radio section:

Demodulator Fail

IDU-ODU cable loss

LOF of aggregate signal radio side

Main and spare ODU, IDU HW failures (card fail)

HBER (high BER)

EW (Early Warning)

2.8.8.1.2 EPS Switching Criteria


The switching criteria are:

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.8.1.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).

2.8.8.2 Protection schemes with MPT-HC/HC-HQAM/XP/XP-HQAM


The MPT-HC and MPT-XP offer the possibility to expand their capabilities using a module
which can be directly plugged on the outdoor unit, called an RPS module (to be used for
1+1 configuration). The two mate MPTs are consequently interconnected through a cable
to allow the exchange of signals needed to perform RPS functionalities.

254

User Manual 3DB19901AFAA Edition 01

Functional description

Starting from R 3.3, the RPS protection without cable function is available. Therefore the
RPS module (3DB1820117Bxxx) and RPS QXCO to QXCO optical cable
(3DB52169Bxxx) between two mate MPT-HC and XP are optional.
The default configuration for 1+1 HSB/SD/FD radio protection does not require an RPS
module and tight cable: the signals needed for RPS are exchanged between two mate MPTs
through IDU/ODU cables and through the MSS instead of using RPS modules and tight
cable, leading to a cost-optimized solution.
For more information, see section 3.9.2.2 for more advanced notes.
In the MPT-HC-HQAM and MPT-XP-HQAM case RPS functionality is embedded inside
the MPT: modularity is no longer needed. Specifically for these ODUs, the RPS cable is
mandatory for channel spacings 40, 50, 56 and 60 MHz.
In Figure 2.84 Ethernet port 2 of one MPT-HC/HC-HQAM/XP/XP-HQAM is connected to
Ethernet port 2 of the second MPT-HC/HC-HQAM/XP/XP-HQAM. To implement the 1+1
configuration an optical cable can be used if needed from one MPT-HC/HC-HQAM/XP/
XP-HQAM to the second MPT-HC/HC-HQAM/XP/XP-HQAM.
Note: In Figure 2.84 the two MPT are connected to two different MPT Access units, but
they can also be connected to the same MPT Access Unit, the same Core-E unit, or to
different EAS or EASv2 units.

Supported Protection types:


1.

RPS (Radio Protection Switching) Hitless for each radio direction

2.

EPS (Equipment Protection Switching) for the MPT-HC/MC/HC-HQAM/XP/XPHQAM

3.

RPS can be implemented with or without an interconnection cable between the


two MPT.

EPS protects the MPT-HC/HC-HQAM/XP/XP-HQAM and the cables


connecting it to the MSS.

HSB-TPS (Hot StandBy - Transmission Protection Switch)

Spare ODU module is squelched.

User Manual 3DB19901AFAA Edition 01

255

Functional description
Figure 2.84 MPT-HC/MC/HC-HQAM/XP/XP-HQAM protection schemes

2.8.8.2.1 RPS Switching Criteria


The switching criteria are:

256

User Manual 3DB19901AFAA Edition 01

Functional description

SF (Signal Fail): generated from transmission and equipment alarms affecting the Rx
radio section

Rx Fail

Demodulator Fail

LOF of aggregate signal radio side

inter-MPT coupling link failure

HBER (high BER) based on the demodulated erroneous blocks ratio

EW (Early Warning) based on MSE

Moreover, MPT-HC/HC-HQAM/XP/XP-HQAM supports a further embedded


functionality called Enhanced RPS. Enhanced RPS is a frame-based protection
mechanism, aimed to reach a quick reaction time and increasing significantly the quality of
the radio interface in the Rx side. It assumes the alignment between the 2 received radio
channels and it is based on frame by frame selection of the best frame between the frames
received from the Main and the Spare radio channel. The Enhanced RPS assumes that the
classical RPS criteria are used to give indication about the preferred channel, whose
frame has to be selected, when the frame-based choice between the 2 streams is not possible
(e.g. due to the frame alignment error). The Enhanced RPS switching criterion depends on
the presence of errors in the decoded LDPC word.

2.8.8.2.2 EPS Switching Criteria


The switching criteria are:

Card Fail status

Card Missing

IDU-ODU Connection Failure

ICP alarm

Mated MPT Access card Failure

2.8.8.2.3 HSB Switching Criteria


The switching criteria are:

Card Fail status

IDU-ODU Connection Failure

ICP alarm

Incompatible Shifter alarm

Incompatible Frequency alarm

Incompatible Power alarm

User Manual 3DB19901AFAA Edition 01

257

Functional description

Incompatible Modulation Parameters alarm

Mated MPT Access card failure

Inter-MPT coupling link failure. Where there is a cross configuration (EPS on Spare
& TPS on main), HSB (TPS) will switch and align with EPS position, if there is an
inter-MPT coupling link failure.

2.8.8.3 Protection schemes with MPT-HLS


Supported Protection types:
1.

RPS (Radio Protection Switching) Hitless for each radio direction

2.

EPS (Equipment Protection Switching) for the MPT-HLS

3.

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

HSB-TPS (Hot StandBy - Transmission Protection Switch)

4.

RPS is implemented using an external RPS cable.

The spare module does not need to be squelched with MPT-HLS because an
external RF switch is present.

FD (Frequency Diversity)

FD protection combines RPS and EPS protection.

In this release, 1+1 configuration is supported only on MPT-HLS connected to a Core-E


card or MSS-1.

2.8.8.3.1 RPS Switching Criteria


The switching criteria are:

258

SF (Signal Fail): generated from transmission and equipment alarms affecting the Rx
radio section

Rx Fail

Demodulator Fail

LOF of aggregate signal radio side

inter-MPT coupling link failure

HBER (high BER) based on the demodulated erroneous blocks ratio

EW (Early Warning) based on MSE

User Manual 3DB19901AFAA Edition 01

Functional description

The MPT-HLS supports a further embedded functionality called "Enhanced RPS".


Enhanced RPS is a frame-based protection mechanism, aimed to reach a quick reaction
time and increasing significantly the quality of the radio interface in the Rx side. It assumes
alignment between the two received radio channels and it is based on frame by frame
selection of the best frame between the frames received from the Main and the Spare radio
channel. The Enhanced RPS assumes that the classical RPS criteria are used to give
indication about the preferred channel, whose frame has to be selected, when the framebased choice between the two streams is not possible (e.g. due to the frame alignment
error). The Enhanced RPS switching criterion depends on the presence of errors in the
decoded LDPC word.

2.8.8.3.2 EPS Switching Criteria


The switching criteria are:

Card Fail status

Card Missing

ICP alarm

2.8.8.3.3 HSB Switching Criteria


The switching criteria are:

Card Fail status

Loss of Ethernet signal

ICP alarm

Incompatible Shifter alarm

Incompatible Frequency alarm

Incompatible Power alarm

Incompatible Modulation Parameters alarm

Excessive Temperature (higher threshold crossing)

RF Switch Fail (1+1 HSB only)

2.8.8.4 Core-E protection


The logic of this protection is distributed in each access and radio peripheral unit. All the
switching criteria coming from both the Core units, are available (via backpanel) to each
peripheral in order to allow to each logic to take the same decision.

User Manual 3DB19901AFAA Edition 01

259

Functional description

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.
Note: When the Core-e unit is protected, it is suggested to protect also the Ethernet data
cables to avoid loss of traffic after a Core switch. If the Ethernet cables are not protected,
it is recommended to enable LOS as switch criteria and to enable Static LAG.
Note: If an optical splitter is used in Core protection configuration autonegotiations need
to be disabled and LOS criteria need to be disabled on involved ports. Note that usage of
an optical splitter is intended to provide protection in case of Core board failure not for
providing line protection on the fiber link.

User Ethernet interfaces protection


In order to support User Ethernet interfaces protection using an external device, the User
Ethernet ports of the Core in standby status are switched off.
The switch on of the User Ethernet interfaces when the Core in standby status becomes
active, due to operator commands or automatic switch, is done within few seconds. In case
of Optical Ethernet interface, the Lambda, Link Length, Connector and Gigabit Ethernet
Compliance Code information are read from the active Core.
Note: It is recommended to connect the Ethernet port of the Core main to the 'default'
port of an external equipment to reduce risk in case of interwork with a revertive
equipment.

TMN Local Ethernet interface protection


In order to support TMN Local Ethernet interface protection using an external device, the
relevant Ethernet port of the Core in standby status is switched off.
The switch on of the TMN Local Ethernet interface when the Core in standby status
becomes active, due to operator commands or automatic switch, is done within 5 seconds.
In order to avoid impact on the Core, the external device used for the TMN Local Ethernet
interface protection is kept separate from the one used for protection of User Ethernet
interface.

260

User Manual 3DB19901AFAA Edition 01

Functional description

External synchronization interface protection


The Protection of the external synchronization interface is supported. The output port on
the stand-by Core is muted.
Node-Timed PDH interface protection
In case of node-timed PDH interface the protection of the NE Clock provided by Core is
supported.
Core protection restoration mode
The restoration mode can be revertive or non revertive.

2.8.8.4.1 Core-E protection Switching Criteria


The switching criteria are:

Core Card Fail

Core Card Missing

Card Not Ready and Flash Card Realignment In Progress conditions represent inhibition of
the Core protection switching with respect to Operator Commands and the additional
criteria listed above.
If the Ethernet LOS Criteria feature has been enabled the following additional switching
criteria are added:

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 fourth User
Ethernet interface working as TMN Local Ethernet interface, and including an
Electrical User Ethernet interface that belongs to an Ethernet LAG.

Note: In case of stand-by Flash Card realignment in progress, the application SW refuses/
removes a manual switch command.

2.8.8.4.2 Port #5 and port #6 protection

If in the Port #5 and/or port #6 a 2xE1 SFP or EoSDH SFP has been installed, the
protection is implemented by using special splitters. See Cords to be used with 2xE1
SFP (SFP for port #5 and #6 of Core-E unit).

User Manual 3DB19901AFAA Edition 01

261

Functional description

2.8.9 Stacking for EAS unit/EASv2 unit/MPT Access unit


Two EAS units, two EASv2 units, or two MPT Access units installed on the same row (for
example, slot #3 and slot #4) are automatically configured in stacking configuration.
The benefits of the stacking are:
1.

the intra-board traffic between the two units does not transit through the Core-E unit
(no traffic impact in case of Core-E switch);

2.

each port of the units can be individually segregated from the other ports.

2.8.10 Ethernet Ring Protection


The implemented Ethernet Ring Protection Switching (ERPS) is according to ITU-T
G.8032 recommendation. The ERPS is a protection mechanism for Ethernet ring
topologies. For use of radio encryption with an Ethernet Ring, see the encryption portions
of sections Additional Settings tab: Direction area (MPT-HC/HC-HQAM/XP/XP-HQAM)
and Additional Settings tab: Direction area (MPT-HLS).

2.8.10.1 Definitions

2.8.10.1.1 Topology
An ERPS Topology is a collection of Ethernet Ring Nodes forming a closed physical loop.
Each Ethernet Ring Node is connected to two adjacent Ethernet Ring Nodes via a duplex
communications facility.

2.8.10.2 Ring Link and Ring Port


Each Ethernet Ring Node is connected to adjacent Ethernet Ring Nodes participating in the
same ERPS Topology, using two independent Ring Links. A Ring Link is bounded by two
adjacent Ethernet Ring Nodes and a port for a Ring Link is called a Ring Port.

262

User Manual 3DB19901AFAA Edition 01

Functional description
2.8.10.2.1 Ring Protection Link (RPL)
The loop avoidance in the ring is achieved by guaranteeing that, at any time, traffic may
flow on all but one of the Ring Links. This particular link is called the Ring Protection Link
(RPL).

2.8.10.2.2 RPL Owner


One designated node, the RPL Owner, is responsible to block traffic over the RPL.
Under a ring failure condition, the RPL Owner is responsible to unblock the RPL, allowing
the RPL to be used for traffic.

2.8.10.2.3 R-APS Protocol


An APS protocol, called R-APS (Ring Automatic Protection Switching), is used to
coordinate the protection actions over the ring.

2.8.10.2.4 ERPS Instance


An ERPS Instance is an entity responsible for the protection of a subset of the VLANs that
transport traffic over the physical ERPS Topology. Each ERPS Instance is independent of
other ERPS Instances that may be configured on the physical ERPS Topology. Only two
ERPS instances are supported.
Each ERPS Instance has its own RPL and RPL Owner.
Additionally, an independent session of R-APS protocol is used, over a dedicated R-APS
VID, for the ERPS Instance protection coordination.

2.8.10.3 ERPS operation


The protection switching mechanism is based on the Automatic Protection Switching
protocol for Ethernet ring topologies (called R-APS). This protocol is used to coordinate
the protection actions over the ring.
The fundamentals of this ring protection switching architecture are:

principle of loop avoidance.

utilization of learning, forwarding, and address table mechanisms defined in the


Ethernet flow forwarding function.

User Manual 3DB19901AFAA Edition 01

263

Functional description

The loop avoidance in the ring is achieved by guaranteeing that, at any time, traffic may
flow on all but one of the ring links. This particular link is called the Ring Protection Link
(RPL).
Under normal conditions this link is blocked, i.e., not used for traffic. One designated node,
the RPL Owner, is responsible to block traffic over the RPL.
Under a ring failure condition, the RPL owner is responsible to unblock the RPL, allowing
the RPL to be used for traffic.
Figure 2.85 Normal Operation (No-fault)

264

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.86 Single link failure

Two ERPS Control Processes are instantiated on each rings node. Each instance selects its
own RPL and RPL Owner.
The ERPS Control Process controls the forwarding function to perform the following
actions:

to disable forwarding over the set of VLANs assigned to the ERPS instance
corresponding to blocked ring links;

to flush the learned MAC address table.

Only revertive switching mechanism is supported.


The Wait-to-Restore is managed by the RPL Owner, it is configured by the operator in 1
minute steps between 1 and 12 minutes. The default value is 5 minutes.
Note: In case of a double failure, if the restoring of the two failures takes place at the
same time, an out of service equal to the WTR could occur. To note that a switching off
of a single NE causes a double failure in the Ring.

A Guard Timer is used to prevent ring nodes from receiving outdated R-APS messages.
During the duration of the guard timer, all received R-APS messages are ignored by the
ERPS Control Process. The period of the guard timer may be configured by the operator in
10 ms steps between 10 ms and 2 seconds, with a default value of 500 ms.

User Manual 3DB19901AFAA Edition 01

265

Functional description

The Ethernet MAC (ETH) layer, where the ERPS take place, is supported by radio links,
optical Ethernet links and/or radio links in L1 LAG acting as Ethernet PHY (ETY) layer in
1+0 configuration.
Since the ERPS instances operate per VLAN on a logical ring protecting a set of VLANs,
this set must consequently be configured.
Figure 2.87 Multiple ERPS instances (Normal No-fault Operation)

266

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.88 Multiple ERPS instances (Single Link Failure)

2.8.10.4 Ethernet Ring Protection switching criteria


The defects used to declare the Signal Fail condition of ERPS when radio direction is
configured in 1+0 protection scheme are:

ODU 300 Card Fail

IDU-ODU Cable Loss

Demodulator Fail

LOF of aggregate signal radio side

HBER (High BER)

RDI (Remote Defect Indication) coming from remote end

Radio peripheral Card Fail

Radio peripheral Card Missing

These defects are used as switching criteria before the defects correlation and defect
persistency processing actions take place.
The only exception are ODU 300 Card Fail and Modulator Fail defects which are used as
switching criteria after defect persistency processing.

User Manual 3DB19901AFAA Edition 01

267

Functional description

The defects used to declare the Signal Fail condition of the L1 LAG port used as a Ring
port are the same as those used to declare the Loss of Signal condition for the L1 LAG.
You can force the Ring to switch by disabling the LAG.
The defects used to declare the Signal Fail condition of ERPS when an Ethernet port is used
as a Ring port are:

Ethernet LOS on Core

SFP Card Missing

SFP Card Fail

A hold off timer parameter for the Ethernet LOS defect can be configured for each Ethernet
port in the ERPS topology. The hold off timer can be enabled only after the ERPS topology
has been created. It is independent of the presence or status of ERPS Instances.
The timer is fixed to 500 ms.
You can force the Ring to switch by disabling the SFP.
A Wait-to-Restore timer is used to prevent undesired protection switches for intermittent
failures. The Wait-to-Restore timer is managed by the RPL Owner. It is configured by the
operator in 1 minute increments between 1 and 12 minutes. The default value is 5 minutes.
A Guard Timer is used to prevent ring nodes from receiving outdated R-APS messages.
During the guard timer period, all received R-APS messages are ignored by the ERP
Control Process. It is configured by the operator in 10 ms increments between 10 ms and 2
seconds. The default value is 500 ms.
Traffic is switched according to MAC learning.
Each Radio interface belonging to the ring is seen as a single interface in the VLAN table
port membership.
In order to deliver Ethernet traffic over the Ring, the operator creates the VLAN and assigns
the rings ports as members of that VLAN.

2.8.10.4.1 EFM OAM switching criteria


When Ethernet First Mile OAM is enabled on User Ethernet interfaces in the Ring, Critical
Link Event and OAM Discovery Not Completed alarms can be configured to be ERPS
switching criteria. By default, the EFM alarms are not used as switching criteria.
The configuration is performed on an ERPS instance but applies to all ERPS instances
related to the ERPS topology. The configuration is applied as follows:

268

User Manual 3DB19901AFAA Edition 01

Functional description

If one ERPS instance has been created with the EFM alarms not enabled as switching
criteria, if a second instance is created the criteria will not be enabled

If one ERPS instance has been created with the EFM alarms enabled as switching
criteria, if a second instance is created the criteria will be enabled

If two ERPS instances have been created with the criteria disabled and the EFM
alarms are enabled on either instance, the criteria will be enabled for both

If two ERPS instances have been created with the criteria enabled and the EFM
alarms are disabled on either instance, the criteria will be disabled for both

If the ERPS instance is in Idle state and the EFM OAM switching criteria is enabled and
either a Critical Link Event or OAM Discovery Not Completed alarm, or both, is active, the
ERPS instance will enter a Protection state.
If the ERPS instance is in Protection state due to EFM OAM alarms and the EFM OAM
alarms are cleared or the criteria is disabled, the ERPS instance will enter Pending state.
The criteria configuration is kept when the ERPS instance is disabled.

2.8.10.5 ERPS and Core protection


The ERPS forwarding status (Blocked/Unblocked) is kept aligned on both the Main and the
Spare Core boards to minimize the traffic hit during Core Protection switch over.
When an Optical User Ethernet interface is assigned as Ring Port, the following
configuration must be performed to guarantee a consistent behavior of ERPS in
combination with Core Protection:

Use an optical splitter

Disable auto-negotiation on Optical User Ethernet interface

Disable Ethernet LOS as switching criteria for Core protection

Disable Static LAG

Enable the Hold Off parameter on both ends of the optical connection when the other
end of the connection is working with Core Protection. If both ends are working with
Core Protection, enable Hold Off on both ends. If neither end is working with Core
Protection, disable Hold Off on both ends.

2.8.11 Radio Transmission Features with ODU300


2.8.11.1 Frequency Agility
User Manual 3DB19901AFAA Edition 01

269

Functional description

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 co
ordination.

2.8.11.2 Automatic Transmit Power Control (ATPC)


The Automatic Transmit Power Control (ATPC) function automatically increases or
decreases the transmit 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 signal.
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 frequency. When ATPC Enabled is checked, the range values are shown
in parenthesis (minimum - maximum) 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.11.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.11.4 Power Monitoring


The ODU300 incorporates a detector for Tx power measurement. It is used to provide
measurement of forward power as a performance parameter, and to provide a calibration
input for transmitter operation over temperature and output range.

270

User Manual 3DB19901AFAA Edition 01

Functional description

Viewed Tx power ranges always match the capabilities of the ODU300 for a given
modulation. When modulation is changed, the WebEML automatically adjusts/restricts Tx
Power to be within valid range.

2.8.11.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 feedforward 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.11.6 XPIC (with MPT-HC/HC-HQAM/XP/XP-HQAM and MPT-HLS


only)
The MPT-HC/HC-HQAM/XP/XP-HQAM and MPT-HLS support Co-channel Dual
Polarized (CCDP) operation using a built-in Cross-polarized Interference Cancellation
(XPIC) function. This function is implemented with the MPT-HC/XP by installing the
RPS+XPIC external module. With MPT-HC-HQAM and MPT-XP-HQAM the
integrated XPIC function requires only a RTU software upgrade. With the MPT-HLS, only
an XPIC license is required.
Two links are operated on the same radio channel, with one using the vertical polarization,
the other the horizontal. XPIC typically provides a 20 dB improvement in polarization
discrimination. The actual improvement will depend on the native discrimination provided
at antenna alignment, and any reduction of this discrimination caused by atmospheric
effects (fading).
If space diversity with the receiver diversity combiner is in use with XPIC on an MPT-HLS,
the following maximum antenna distances apply:

40 m for 28 MHz channel spacing

28 m for 40 MHz channel spacing

20 m for 56 MHz channel spacing

The XPIC can be implemented with or without the Adaptive Modulation.


Radio configuration supported:

Single 2+0 XPIC

Double 1+1 HSB co-channel XPIC

User Manual 3DB19901AFAA Edition 01

271

Functional description
Figure 2.89 Single 2+0 XPIC

272

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.90 Double 1+1 HSB co-channel XPIC

Note: To configure the double 1+1 HSB co-channel XPIC follow the following steps:

1.

Configure the 1+1 HSB protection between the two mate MPT units;

2.

Configure the XPIC on the protected radio (in the MPT-HC/HC-HQAM/XP/XPHQAM or MPT-HLS 1+1 Main view configure the Option mask for XPIC profile).

2.8.11.7 Link identifier


The amount of microwave links, especially in urban areas presents a risk 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.

User Manual 3DB19901AFAA Edition 01

273

Functional description

2.8.11.8 Loopbacks with ODU300


To facilitate the installation/commissioning and the remote maintenance one loopback is
available.
As the activation of a loopback affects the traffic, the presence of a loopback is indicated
to the management systems as an abnormal condition.
The loopback is "loop and cut" type (the signal sent after the loopback execution is the same
signal sent back).
The loopback supported by the Radio board is shown in the following figure.
The loopback supported by the Radio board is shown in the following figure.
Figure 2.91 Available loopbacks

PDH board
LIU

NxE1

FPGA

RADIO board
SerDes

CORE
SWITCH

FPGA

MODEM

1
23553

1.

IF Radio loopback: is implemented in the analog IF part of the ODU300 Radio


Module, the traffic received from switch side is redirected toward the switch itself;
this loopback can be activated only on the aggregate traffic. When this loop is enabled
the behaviour is the following:

TDM2TDM flows: before transmitting the packets towards the switch, the
FPGA looking the VLAN will rebuild the right Ethernet header.

TDM2ETH flows: before transmitting the packets towards the switch, the
FPGA looking the VLAN will rebuild the right Ethernet header.

The Ethernet flows are dropped.

2.8.12 Radio Transmission Features with MPT-HC/HC-HQAM/


HLS/MC/XP/XP-HQAM
2.8.12.1 Adaptive Equalization
Adaptive equalization (AE) is employed to improve reliability of operation under
dispersive fade conditions, typically encountered over long and difficult paths.
274

User Manual 3DB19901AFAA Edition 01

Functional description

This is achieved through a multi-tap equalizer consisting of two registers, one with feedforward 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.12.2 Link identifier


The amount of microwave links, especially in urban areas puts the problem of possible
interferences during installation and turn-on phase.
The digital frame incorporates link identity coding capabilities to prevent the capture of an
unwanted signal.
In case of Link Identifier Mismatch all the traffic is dropped.
The Link identifier management can be enabled or disabled by the management systems.

2.8.12.3 Loopbacks with MPT-HC/HC-HQAM/HLS/MC/XP/XP-HQAM


To facilitate the installation/commissioning and the remote maintenance one loopback is
available.
Because 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).
LinkIDs must be disabled before a loopback can be configured. For TDM2ETH flows the
loopback works only if the ECID Tx and ECID Rx are the same.
The loopbacks supported are shown in the following figure.

User Manual 3DB19901AFAA Edition 01

275

Functional description
Figure 2.92 Available loopbacks

1.

Core facing radio loopback: this loopback routes data from the output of the Tx Data
Awareness block (after compression) to the input of the Rx data awareness
(decompression).
This is an internal loopback provided by the MPT FPGA.
It is a Loop and Continue. It is possible to enable this loopback only at aggregate
level.
When this loopback is activated the behavior is the following:

Compressed flows (TDM2TDM,TDM2ETH and ATM PW) are forwarded


back to Core module with proper assignment of source and destination MAC
addresses (e.g. incoming MAC SA is used as MAC DA for looped frame, while
MAC SA in the looped frame is the MAC assigned to slot hosting radio card).

For ATM PW flows the loopback works only if the Inbound and Outbound PW
Labels are the same, in case they are different the loopback doesn't work.

Generic Ethernet flows are dropped.

The Core facing radio loopback operation implies the Automatic Tx mute before
the execution of the command and the Tx mute removal after the execution of the
loopback command.
2.

Core facing RF loopback: local core facing RF loopback provides a method to


troubleshoot RF paths constructed with MPT-HLS. The mode is enabled by the user
provisioning the MPT-HLS Tx and Rx frequencies to the same value.
This loopback is supported by MPT-HLS transceivers only. It is not guaranteed if
ATPC is in use.
This loopback is traffic affecting.
The following considerations apply when an @RF - Internal loopback is configured:

276

If the diversity combiner is active, you need to squelch the diversity receiver.

If XPIC is enabled, you need to mute the remote XPIC transmitter to avoid
interference on the associated XPIC polarization.

User Manual 3DB19901AFAA Edition 01

Functional description

If the MPT-HLS is 1+1HSB configuration, you need to apply an RPS Lockout/


forced switch to the channel where the loopback will be activated.

When a core facing RF loopback is performed with SD enabled, a combiner loss of


alignment alarm will remain active to indicate that alignment cannot be performed.
3.

Radio facing Circuit loopback: remote loopback allows an over-the-air loopback test
to be performed when the modem is operating in a continuous mode.
The loopback is internally provided by the MPT FPGA and connects the Receive data
interface to the Transmit data interface.
This is a line external loopback. This loopback is a Loop and Continue.
It is possible to enable this loopback only at aggregate level.
When this loop is enabled the expected behavior is the following:

Compressed flows (TDM2TDM,TDM2ETH and ATM PW) are forwarded


back to Core module with proper assignment of source and destination MAC
addresses (e.g. incoming MAC SA is used as MAC DA for looped frame, while
MAC SA in the looped frame is the MAC assigned to slot hosting radio card).

For TDM2ETH flows the loopback works only if the ECID Tx and ECID Rx
are the same, in case of ECID Tx is different form ECID Rx the loopback
doesn't work.

For ATM PW flows the loopback works only if the Inbound and Outbound PW
Labels are the same, in case they are different the loopback doesn't work.

Generic Ethernet flows are dropped.

Figure 2.93 shows the summary block diagram of a loopback.

User Manual 3DB19901AFAA Edition 01

277

Functional description
Figure 2.93 Loopback with MPT-HC/HC-HQAM, MPT-XP/XP-HQAM, and MPT-MC

2.8.12.4 Loopback activation


The loopback can be activated by each management system (local or remote). The
activation command allows the duration of the loopback (time-out) to be defined. The
default is five minutes.
The two loopbacks (Core facing and Radio facing) cannot be supported at the same time.
The time-out period starts at the activation time and expires at the end of the period
spontaneously in the NE, a part for the case in which another reconfiguration of the timeout 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 timeout 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.12.5 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.
278

User Manual 3DB19901AFAA Edition 01

Functional description

The management system's operator has to provide the time range of the loopback time-out
period expressed in days/hours/minutes starting from the time of the loopback activation.
The default timeout is five minutes.
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.12.6 Packet throughput booster (Header compression)


Packet throughput booster utilizes a proprietary algorithm to compress header fields in a
loss less manner on standard protocol fields within incoming data streams in order to save
radio bandwidth.
Packet throughput booster is supported on MPT-HC/HC-HQAM/MC/XP/XP-HQAM
ODUs (MPT ODU) and on MPT-HLS.
Packet throughput booster is supported with the following system configurations:

Bridge types:

802.1D

802.1Q

802.1ad

TCP/IP Stacks:

IPv4

IPv6

L2 Radio LAG

Ethernet ring protection (ERP)

1+1 radio protection; HSB, SD, or FD (valid for RPS protection with and without
cable).

XPIC

Packet throughput booster is not supported with L1 Radio LAG.


Packet throughput booster is enabled individually using the JUSM interface.
Packet throughput booster must be enabled on both ends of the radio link for the feature to
function.

User Manual 3DB19901AFAA Edition 01

279

Functional description
2.8.12.6.1 Layer 2 header compression
The following is a list Layer2 header fields which the algorithm can compress:

up to 64 dst and src MAC address pairs (dynamically learned)

up to 2 TPIDs corresponding to C-VLAN and S-VLAN respectively

single Ethertype

MPLS uni/multicast

IPv4

IPv6

up to three user defined Ether types

2.8.12.6.2 Layer 3 header compression


The following is a list Layer3 header fields which the algorithm can compress:

up to 64 dst and src IPv4 address pairs (dynamically learned)

up to 64 dst and src IPv6 address pairs (dynamically learned)

2.8.12.6.3 Encryption management


Traffic on MPT-HC/HC-HQAM/XP/XP-HQAM or MPT-HLS radios in 1+0 or 1+1
configuration can be encrypted. When encryption is enabled, the MPT encrypts all
outgoing traffic transmitted over the radio interface using an AES cipher. You can
configure an AES passphrase in the JUSM. The MPT generates a 256-bit AES key based
on the passphrase.
The encryption is disabled by default.
An encryption license is required.
Radio encryption is not supported on MPT-MC or MPT-HC V1. Therefore the MPT-HC
V1 cannot be used as a spare for an MPT-HC on a radio link when the encryption function
is active.
If AES encryption is active on a link with MPT-HC/ MPT-HC-HQAM, the MPT-HC V1
can not be used as a spare part.

280

User Manual 3DB19901AFAA Edition 01

Functional description
2.8.12.6.4 Dynamically learned address pairs
Dynamically learned address pairs are subject to a learning table size of 64 learned address
pairs. When the table is full no additional address pairs can be learned. Table entries are
removed from the table using an aging timer within the MPT ODU.

2.8.12.6.5 Automatic fade control


To guarantee delivery of compressed header fields, the Early Warning condition is utilized
to detect a fade condition and automatically disengage header compression. Header
compression will remain disengaged until the Early Warning condition is cleared, at which
time header compression automatically is re-engaged.

2.8.13 TACACS+
2.8.13.1 Overview
The system supports a TACACS+ client as defined by IETF draft-grant-tacacs-02 to
perform centralized Authentication, Authorization, and Accounting (AAA) of user logins.
TACACS+ is supported on MSS-1/4/8 snmp, http, and telnet/SSH interfaces.
Server messages for the SSH interface are discarded if the authentication and authorization
is not successful since there will not be a service to display them.
Login requests are authenticated using TACACS+ instead of the local user database,
whenever TACACS+ is enabled and a configured server is available.
TACACS+ Authorization shall only be used to determine user membership in one of the
existing 9500 MPR privilege groups. Authorization of individual commands is not
supported.
If TACACS+ is enabled, the user cannot change its own password. If a password needs to
be changed, an administrator user can change the other local user accounts.
TACACS+ Accounting is supported on a limited basis for WT-CLI and SNMP commands.

2.8.13.1.1 Server Support


The client supports a priority list of up to four TACACS+ servers with a unique server
encryption key for each.
User Manual 3DB19901AFAA Edition 01

281

Functional description

All server exchanges are secured by the TACACS+ protocol by multiplexing the
appropriate contents with a string of MD5 hashes based on the provisioned server secret
key. The unencrypted mode of operation is not supported.
Note: Only the PAP login type (cleartext username and password) is supported.

Server messages and custom prompts received in a TACACS+ response are accepted but
not displayed to users.

2.8.13.1.2 Authentication/Authorization
Each time an authentication is required on a user interface, the client uses the server
selection process to determine, if a TACACS+ server is available. When no servers are
available, the local login database is used. The authentication request is denied, if a
matching username and password are not found. If a server is available, the client opens a
TCP connection to the selected server and perform authentication/authorization as follows.
The authorization response of PASS-ADD is parsed to locate a command pair,
vacm={administrator | craftperson | operator | viewer}, that assigns the privilege group
for the user. The authorization is denied for any other authorization response or if no valid
privilege group is defined for the user. This provides security against authentication of valid
users, who are not authorized to access the NE.
Note: The Operator shall be "explicitly" alerted about the requested settings server side
to build a set-up interoperable with MPR9500; i.e. the Authorization response shall
include command pair "vacm={administrator | craftperson | operator | viewer}",
otherwise login procedure will fail.

User authentication and authorization management by remote TACACS+ server is not


compatible with SNMPv3 user management. If the NE is configured in SNMPv3 mode, it
is not possible to enable TACACS+ on the SNMP interface using the Ethernet features
shell.
If TACACS+ is enabled on the SNMP interface, it is not possible to configure the NE in
SNMPv3 mode.

282

User Manual 3DB19901AFAA Edition 01

Functional description
2.8.13.1.3 Accounting
When commands are received on a user interface where accounting is enabled, the client
uses the server selection process to determine where to send an accounting request. When
no servers are available, the latest notifications are held in queue on a space available basis
for later reporting. When a server is available, the client opens a TCP connection to the
selected server and performs the accounting request as follows:
If the connection is successful, an accounting STOP REQUEST is sent. The request
contains a task ID (separate count for each interface), the NE IP address, the client/manager
IP address, the port type (snmp, telnet, SSH), stop time, and command notification strings.
The username and privilege group is included for the telnet/SSH ports.
An accounting REPLY of SUCCESS indicates that the request was accepted by the server.
Any other response from the server is ignored.
The TACACS+ single-connection mode is not supported. Each TCP connection is closed
after the accounting transfer is complete and a new TCP connection is used for the next
request. The telnet/SSH interfaces report all WT-CLI commands including any arguments.
The snmp interface reports all object ID strings and values contained in any SET command
received from a registered manager. The SET commands to register a manager and SET
commands to perform a registration or deletion are also reported.
Accounting notifications are not supported for commands received on the HTTP interface.
A circular message queue is supported that is capable of storing at least 20 accounting
notification events. When the queue is full, the oldest notifications will be removed to keep
the latest notifications. Multiple notifications for the same port, user, and client/manager IP
address may be included in a single accounting request. The request may be deferred until
a minimum number of notifications are held in the queue, a minimum time has passed
without additional notifications, or the maximum notifications for a single request have
been received.

2.8.13.1.4 Parameters for multiple notifications in a single accounting request


The deferring of an accounting request is managed according to the following parameters:

Minimum number of notifications to hold in the queue is 1

Minimum time to pass without additional notifications is 500 ms

Maximum number of notifications for a single request is the number that can be held
in a payload of 200-1400 bytes.

User Manual 3DB19901AFAA Edition 01

283

Functional description
2.8.13.1.5 Server Selection
The server selection process determines the server or authentication method to be used
based on the following procedure.
The server list is searched to find the highest priority server that currently has no attempt
failures (i.e. skip any servers with attempt failures).
The primary server is selected, if any lower priority servers have no attempt failures and the
time since the primary server last failure exceeds the configured holdoff time. This allows
the primary server to again be used for the first connection attempt of the authentication
request but return directly to the last reachable server if the attempt fails. Otherwise, the
highest priority server with no attempt failures is selected.
When all servers have attempt failures, the highest priority server from those with the
minimum attempt count not exceeding the retry attempt limit is selected. When all servers
have exceeded their retry attempt limit, the highest priority server with a time since last
attempt failure that exceeds the configured holdoff time is selected.
The selection process does attempt to use another server or use the local login database if
an authentication/authorization request is denied by a reachable server.
The configuration command is only supported for users with administrator privilege.

2.8.13.1.6 Server Monitoring


TACACS+ status monitoring is implemented through a command in the Ethernet Features
shell.
The command is only supported for users with administrator privilege.
The command displays the current TACACS+ configuration, attempt failures for each
server, and time since last server failure.

2.8.13.1.7 Server Validation


TACACS+ validation testing is implemented through a command in the Ethernet Features
shell. This test allows to monitor round-trip response times for determining proper timeout
settings and to confirm correct secret keys.
The command is only supported for users with administrator privilege.

284

User Manual 3DB19901AFAA Edition 01

Functional description

The command generates a single dummy authentication request to each configured


server. The authentication response status is reported as TCP Timeout, AA Timeout, or OK.
The elapsed time from TCP connection start to the initiation of TCP connection close is
reported with tenths of a second resolution.
The request is sent regardless of holdoff status or attempt counts.

2.8.14 TMN interfaces


On 9500 MPR-E Network Element the following types of TMN communication interfaces
are present:

TMN channel carried by Ethernet frames in the dedicated TMN port (on the front
panel of the Core-E module) (this port is normally used to connect the WebEML);

TMN channel carried up to 512 kbit/s channel inside Radio frame;

TMN channel carried by Ethernet frames in User Ethernet port# 4 (on the front panel
of the Core-E module);

Two TMN In-band interfaces (by using the Ethernet traffic ports).

2.8.15 IP addressing
All TMN interfaces except Ethernet ports are unnumbered ports. An unnumbered port uses
the local IP address of the router as its own address. This allows a single IP address, called
the Local IP Address, to identify the NE over TMN-RF PPP interfaces.
The local IP address is configured statically using the management systems. You can use
IPv4 or IPv6 addressing.
Caution: Mixed configuration of IPv4 and IPv6 NEs is not supported.

Note: In an IPv6 environment, the maximum LSA length handled by the 9500 MPR is 1 280
bytes.

2.8.15.1 IPv4 addressing for the local IP address


The default IPv4 address is 10.0.1.2.

User Manual 3DB19901AFAA Edition 01

285

Functional description

The local IPv4 address must be configured according to the following rules:

Only Class A, Class B and Class C IP addresses are allowed. Classless addressing is
allowed.

IP Address 0.0.0.0 is not allowed.

IP addresses from 127.0.0.0 to 127.255.255.255 are not allowed.

IP addresses having 0 or 255 in the last byte of the address are not allowed.

2.8.15.2 IPv4 addressing for the TMN local Ethernet interface IP


address
The TMN local Ethernet interface is used to connect the NE to LAN exchanging TMN
information. It has its own IP address and subnet mask assigned using a management
system.
The IP address of TMN Local Ethernet interface can be equal to the Local IP address. If the
IP address is
different from the Local IP address, they must belong to different subnets.
The default address is 10.0.1.2. The default subnet mask is 255.255.255.0.
The IPv4 address must be configured according to the following rules:

Class A, Class B and Class C IP addresses are allowed. Classless addressing is


allowed.

IP Address 0.0.0.0 is not allowed.

IP address from 127.0.0.0 to 127.255.255.255 are not allowed.

IP Address must be checked with Subnet Mask to prevent the IP address referring to
the subnet itself (all 0 in the Host portion of the address) or referring to the subnet
broadcast address (all 1 in the Host portion of the address).

The subnet assigned to this interface must be different from the one assigned to the other
TMN Ethernet interfaces.

2.8.15.3 IPv6 addressing for the local IP address


The NE Local IPv6 address is a Global Unicast address which identifies the NE in the DCN.
The default address is FEC0:0:0:1::1. The prefix length is not configurable and is fixed to
128.

286

User Manual 3DB19901AFAA Edition 01

Functional description

The NE Local IPv6 address must be configured according to the following rules:

IPv6 addresses having the Interface ID portion equal to all 0 are not allowed.

IPv6 address::/128 (Unspecified address) is not allowed.

IPv6 address::1/128 (Loopback Address) is not allowed.

IPv6 addresses having FF00::/8 as high-order bits (Multicast addresses) are not
allowed.

IPv6 addresses having FE80::/10 as high-order bits (Link Local Addresses) are not
allowed.

Every time the Local IPv6 address is changed a NE warm restart is automatically
performed.

2.8.15.4 IPv6 addressing for the TMN local Ethernet interface IP


address
The Local Ethernet interface dedicated to TMN is used to connect the NE to LAN
exchanging TMN information. It has its own Global Unicast IPv6 address and prefix length
assigned using a management system.
The IPv6 Global Unicast address of the TMN Local Ethernet interface can be equal to the
Local IPv6 address provided that the IPv6 address of other TMN interfaces have not been
already set to the same address.
If the IPv6 address of the TMN local Ethernet interface is different from the Local IPv6
address, they must belong to different subnets. The subnet number of the Local IPv6
address is obtained and applied to the subnet prefix assigned to the TMN Local Ethernet
interface.
The default address is FEC0:0:0:1::1/64.
The TMN Local Ethernet IPv6 address must be configured according to the following rules:

IPv6 addresses having the Interface ID portion equal to all 0 are not allowed.

IPv6 address::/128 (Unspecified address) is not allowed.

IPv6 address::1/128 (Loopback Address) is not allowed.

IPv6 addresses having FF00::/8 as high-order bits (Multicast addresses) are not
allowed.

IPv6 addresses having FE80::/10 as high-order bits (Link Local Addresses) are not
allowed.

User Manual 3DB19901AFAA Edition 01

287

Functional description

The TMN Local Ethernet IPv6 address must belong to a subnet number different than the
ones associated with other TMN interfaces (the subnet numbers resulting from applying the
shortest prefix length must not be the same).
When TMN Local Ethernet is disabled, its IPv6 configuration is lost.
Every time the TMN Local Ethernet interface is enabled or its IPv6 Global Unicast address
is modified, Duplicate Address Detection must be performed prior to assigning it to the
TMN interface. When a duplicate address is detected an alarm is raised. You need to change
the IPv6 address to remove duplicates.
IPv6 addresses FF02::1 (All nodes) and FF02::2 (All Routers) Multicast Group addresses
must be joined by an enabled TMN Local Ethernet interface.
NDP (Neighbor Discovery Protocol) is used to perform Neighbor Address Resolution to
retrieve MAC address-IPv6 address association over the LAN.
NDP is used to perform IPv6 Stateless Address Autoconfiguration to assign an IPv6 Global
Unicast address to the host connected to TMN Local Ethernet.

2.8.16 Admission control in Adaptive Modulation (only with


ODU300)
Note: With the MPT-HC/HC-HQAM/MC/XP/XP-HQAM the Admission Control is always
enabled (and cannot be disabled). The total available capacity is the capacity available
with the minimum modulation scheme.

2.8.16.1 What does Admission Control mean?


The Admission Control is a feature that is available only when operating in Adaptive
modulation. It ensures that the requested TDM flows are kept when the modulation scheme
is downgraded automatically by the system due to the degraded propagation condition.
The Admission Control check is optional: from WebEML, it is possible to decide to enable
or not the admission control check (default value is Enabled).

2.8.16.2 Radio capacity in case of adaptive modulation

288

User Manual 3DB19901AFAA Edition 01

Functional description

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.3 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.16.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 QPSK capacity.
Note: There is no possibility to provision a number of E1s greater than the one fitting in
QPSK modulation. 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 QPSK. To secure provisioning and commissioning
operations, the admission control check at WebEML level has been inserted, avoiding a
possible mistake from the user to provision a number of E1s that are not fitting inside
QPSK bandwidth.

Depending on the channel spacing value, the maximum number of E1 that can be
provisioned is (refer to Table 2.3):

Channel spacing of 7 MHz: 4 x E1

Channel spacing of 14 MHz: 8 x E1

Channel spacing of 28 MHz: 18 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 QPSK
and the whole traffic exceeding QPSK bandwidth is dropped while the E1s are kept.
Figure 2.94, Figure 2.95 and Figure 2.96 here below show how the system operates, in case
of modulation changes when admission control is enabled (case of 28 MHz bandwidth).

User Manual 3DB19901AFAA Edition 01

289

Functional description
Figure 2.94 Example of traffic 28MHz bandwidth and admission control

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 QPSK.
Remaining available capacity is used to transmit other kinds of traffic.
When the modulation is degraded from 64QAM to 16QAM (Figure 2.95), the E1 flows are
kept whilst the Ethernet traffic with lowest priority (Fast Ethernet traffic #2) is reduced.

290

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.95 Example of traffic in case of 28MHz bandwidth and modulation downgraded to 16QAM

When the modulation is further degraded to QPSK (Figure 2.96), the E1 flows are still kept
whilst the Ethernet traffic with the lowest priority is dropped (Fast Ethernet traffic #2) and
the Ethernet traffic with the highest priority is reduced (Ethernet traffic #1) to fit the
remaining available bandwidth.
Figure 2.96 Example of traffic in case of 28MHz bandwidth and modulation downgraded to QPSK

User Manual 3DB19901AFAA Edition 01

291

Functional description

2.8.16.4 Adaptive modulation and admission control disabled


The E1 flows are no more guaranteed traffic when the operators disable the admission
control. The maximum 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.
Note: 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 QPSK. To secure provisioning and commissioning operations, the
admission control check at WebEML level has been inserted, avoiding a possible mistake
from the user to provision a number of E1s that are not fitting inside16QAM bandwidth.

Depending on the channel spacing value, the maximum number of E1s that can be
provisioned is (refer to Table 2.3):

Channel spacing of 7 MHz: 8 x E1

Channel spacing of 14 MHz: 18 x E1

Channel spacing of 28 MHz: 37 x E1

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 QPSK, 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.
Note: It might happen that some E1(s) are temporarily up and transmitting, but this is a
random behaviour 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 2.97, Figure 2.98 and Figure 2.99 show how the system operates in case of
modulation changes when admission control is disabled (case of 28 MHz bandwidth).

292

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.97 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.
Figure 2.98 Example of traffic in case of 28MHz bandwidth and modulation
downgraded to 16QAM

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

User Manual 3DB19901AFAA Edition 01

293

Functional description
Figure 2.99 Example of traffic in case of 28MHz bandwidth and modulation
downgraded to QPSK

2.8.17 Managed Services and profiles


Here below the association of managed services and profiles:

294

TDM to TDM This is the typical service associated to a traditional TDM network
in which E1 traffic is transported, switched and terminated inside a MPR network.

TDM to ETH This is the service allowing the TDM traffic to be aggregated and
output in a single ETH stream. On this service specific algorithms are applied in order
the E1 is transported, switched and provided to an external ETH network in standard
format (MEF-8).

SDH to SDH This is the typical service associated to a traditional SDH transport
network. STM-1 traffic is transparently transported, switched and terminated inside
a MPR network.

ETH to ETH This is not a real CES due to the native IP architecture of MPR.
Ethernet traffic is directly managed by the L2 switch on the Core board, thanks to the
auto-learning algorithm, VLANs etc.

ATM to ATM This profile allows the management of the ATM services inside a
9500 MPR network. E1s IMA/ATM are terminated/reconstructed at the borders of
the 9500 MPR cloud; encapsulation/extraction of ATM streams into/from ATM PW
packets is performed according to RFC 4717.

ATM to ETH This profile allows the ATM service to be terminated and
encapsulated into an Ethernet stream towards an IP/MPLS Core Network.
User Manual 3DB19901AFAA Edition 01

Functional description

1.

2.

TDM to TDM flow

Definition: This service identifies a flow inside MPR network, in which E1 is


transported, switched and terminated.

Application: Typical microwave 2G backhauling application, in which E1s are


terminated before entering into aggregation network.

TDM to ETH flow

Definition: E1 TDM input signals are packetized according to MEF8 standard;


E1s are transported, switched and provided to an external ETH network in
standard format (MEF-8).

Application:
a.

Typical microwave 2G backhauling application, in which E1s are


terminated before entering into aggregation network, where aggregation
network is a packet network. E1s are not terminated at the end of the
microwave backhauling and an end-to-end circuit emulation services
could be established between 9500 MPR and the service router in front of
BSC/RNC

b.

9500 MPR without ODU (MSS-8, MSS-4, or MSS-1 stand alone)


provides the same level of feature of a site aggregator box, grooming
together different services (in this particular case E1 TDM) into the
common Ethernet layer.

User Manual 3DB19901AFAA Edition 01

295

Functional description

3.

4.

5.

SDH to SDH flow

Definition: This service identifies a flow inside MPR network, in which STM1 is transparently transported, switched and terminated.

Application: Typical microwave transport application.

ETH to ETH flow

Definition: Ethernet traffic is transported and switched automatically by the


standard auto-learning algorithm of the built-in MPR 10 Gbit Ethernet switch.

Application: Typical microwave 3G backhauling/WiMax application, in which


transport of Ethernet packets coming from basestations is requested.

ATM2ATM flow

296

Definition: 9500 MPR terminates the native IMA/ATM and performs


encapsulation/extraction of those ATM flows into/from ATM PW packets
according to RFC 4717. The 9500MPR facing the aggregation network, the
original ATM flows are re-built on ASAP board.

User Manual 3DB19901AFAA Edition 01

Functional description

6.

Application: Typical microwave 3G backhauling application, in which


transport of Ethernet packets coming from 3G base station is requested.

ATM2ETH flow

Definition: 9500 MPR terminates the native IMA/ATM and ATM traffic,
encapsulated in Ethernet frames, is transported into IP/MPLS Core Network.

Application: Typical microwave 3G backhauling application, in which


transport of Ethernet packets coming from 3G basestation is requested.

2.8.18 TDM and Ethernet traffic management


Three kinds of traffic management have been identified:

TDM2TDM (9500 MPR-E 9500 MPR-E, the two IWFs are internal to the MPR
network)

TDM2Eth (9500 MPR-E TDM to Ethernet)

SDH2SDH (9500 MPR-E 9500 MPR-E, the two IWFs are internal to the MPR
network)

DATA (Ethernet to Ethernet)

The first two profiles meet MEF8 standard.


Figure 2.100 Traffic profiles

User Manual 3DB19901AFAA Edition 01

297

Functional description

Case 1 for E1 (TDM2TDM over MPR network)


The E1 stream is inserted in Node 1 and extracted in Node 2. In this case the two IWFs used
to packetize the traffic for the Ethernet switch in the Core-E module are both internal to the
9500 MPR-E network. The Circuit Emulation Service is TDM2TDM in Node 1 and Node
2. The Cross connections to be implemented are PDH-Radio type.
Case 1 for STM-1 (SDH2SDH)
The STM-1 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 SDH2SDH in Node 1 and
Node 2. The Cross connections to be implemented are SDH-Radio type.
Case 2 (TDM2Eth)
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 (TDM2Eth)
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.

298

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.101 Traffic profiles

Case 4 and 5 (ETH2ETH)


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.

User Manual 3DB19901AFAA Edition 01

299

Functional description
Figure 2.102 Traffic profiles

Case 6 for E1 (TDM2TDM over Ethernet)


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-Eth type.

2.8.18.1 TDM2TDM
E1 traffic packetized only internally to 9500 MPR-E equipment.

300

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.103 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 121 bytes

ECID will be the same value as Flow Id (ECID = Emulated Circuit Identifier)

TDM clock source: clock recovery differential,

Flow Id provisioned by ECT/NMS

2.8.18.2 TDM2Eth
E1 traffic both internal and external to 9500 MPR-E equipment.
User Manual 3DB19901AFAA Edition 01

301

Functional description
Figure 2.104 E1 Traffic

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, clock loopback (TDM line in)

Flow Id is provisioned by ECT/NMS (One Vlan is assigned to each bi-directional


circuit emulated E1 flow)

For this case the expected latency for 1 hop is 3.5 msec for 256 bytes.

2.8.18.3 SDH2SDH
STM-1 traffic packetized only internally to 9500 MPR-E equipment.

302

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.105 STM-1 Traffic

Flow Id present (user defined)


If there are intermediate nodes in each node build the 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

Clock source: clock recovery differential/node timing

Flow Id provisioned by ECT/NMS

2.8.18.4 ETH2ETH
None of the IWFs belongs to 9500 MPR-E.
None of the parameters listed in the previous slide has to be configured (the 9500 MPR-E
is transparent).

User Manual 3DB19901AFAA Edition 01

303

Functional description
Figure 2.106 E1 Traffic

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.19 ATM Traffic Management

304

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 2.107), 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.

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.107 ATM Traffic Management - General block diagram

In Figure 2.108 is shown a more detailed block diagram of the ASAP unit in Ingress.

User Manual 3DB19901AFAA Edition 01

305

Functional description
Figure 2.108 Block diagram for ATM Ingress (ATM Packet) direction

1.

ATM Ingress Policing

2.

ATM Policing (cell-based) can be enabled/disabled, on provisioning base, for


each VP/VC configured 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

Conformance Definition: CBR.1

Cells to packet
The ATM cells are encapsulated in PWE3 packet.

3.

306

Packet Profiled Scheduling

ATM cell(s) are put into a packet, as result of provisioned value of max contact.
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:


User Manual 3DB19901AFAA Edition 01

Functional description

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 discarded 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 2.60
It is mapped to 802.1p bits in the following manner:
Table 2.60 802.1p mapping

4.

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

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 applies to queues with guaranteed Traffic:

5.

It applies to queue 7 and 6.

To avoid delay on queue 7, shared among TDM2ETH, ATM CBR, the fill level
to start discarding is configured according to max acceptable delay (about 1
ms).

Shared Tx queues
The packet according to its service category is send to one of the output queues.

User Manual 3DB19901AFAA Edition 01

307

Functional description

6.

Rx Queues
Flows of the same type are reassembled in different queues.

7.

Packet to cells
The ATM cells are extracted from the PWE3 packet.

8.

ATM Egress Shaping

A four-queue scheduling is used for ATM traffic egressing MPR system.

The higher priority queues are reserved for ATM shaped traffic, while the
lowest one is reserved to not shaped traffic.

Cell-based ATM Shaping is applied for a VP/VC that has been configured with
CBR and VBR Service Category on the basis of its configured egress ATM
Traffic Descriptor, general reference for this feature is ATM standards.

A Weighted Round Robin is instead applied for all VPs/VCs that are not
shaped. The weights are based on the value of configured MDCR in the egress
ATM Traffic Descriptor value according to below table:
Table 2.61 RR weights
MDCR [cell/s]

RR Weight

<= 149

<= 300

<= 602

<= 1206

<= 2413

<= 3621

<= 4529

>= 4530

e.g. MDCR = 1000 [cell/s] Weight = 4


An UBR has MDCR=0 weight = 1
Note: ATM Light Service

With MPT-HC/HC-HQAM/MC/XP/XP-HQAM there is no full support of ATM Traffic as


with ODU300, but the so-called ATM Light Service applies.
In this release, ATM PW traffic will be transported as native Ethernet traffic over radio
directions with MPT ODU.

308

User Manual 3DB19901AFAA Edition 01

Functional description

Radio QoS applied to ATM PW traffic will be the one for native Ethernet traffic, but since
bandwidth cannot be guaranteed, admission control will not be applied.
Transport of ATM PW traffic within an MPR network must be done with radio links using
all the same type of ODU, either ODU300 or MPT ODU.
To avoid NE reconfiguration in migration towards future release fully supporting ATM PW
Service on radio directions with MPT ODU, a complete provisioning is applied since this
release (including declaration of traffic descriptors).
However, configurations where ATM PW flows are cross-connected between a RadioEthernet terminal and an ATM-Ethernet terminal will require NE reconfiguration, as
different MAC Address need to be provisioned.

2.8.19.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.
Table 2.62 PW label EXP bits
ATM Service category

EXP bits

Scheduling type

CBR

110

Expedited

UBR+

010

Best Effort

UBR

000

Best Effort

2.8.19.2 ATM Traffic Management on Modem card - Block diagram for


ATM PW Flow policer
Figure 2.109 ATM Traffic Management on Modem card - Block diagram

User Manual 3DB19901AFAA Edition 01

309

Functional description

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.19.3 Support of ATMoMPLS Protocol Stack (with or without MPLS


Tunnel Label

2.8.19.3.1 ATM PW over MPLS (ATMoMPLS)


In order to support inter-working of ATM PW Service with IP/MPLS network at least at
datapath level, in this release it will be supported the ATMoMPLS protocol stack
referenced by RFC 4717, with the characteristics/limitation described in this section.
For network deployment where both terminations of ATM traffic is carried out by MPR
NEs, in order to save radio bandwidth it will be possible to have the ATM PW Service using
the ATMoMPLS protocol stack without the MPLS Tunnel Label.

2.8.19.3.2 Protocol Stack Termination


In this release the ATMoMPLS protocol stack is terminated directly by the MPR NE where
native ATM interface is present (i.e. MPLS Tunnel Label, if present, is added by ASAP
Card).
That implies all MPR NEs must be aware of MPLS Tunnel Label presence, i.e. to apply
ATM PW Header Compression.

2.8.19.3.3 802.1q VLAN Tag


ATMoMPLS protocol stack used by MPR foresees to have the 802.1q VLAN Tag.
VLAN is used, within MPR network, to define for ATM PW frames:

310

forwarding plane

colour marking consequent to profiled scheduling

specific processing (ATM PW Header Compression) and QoS (queue assignment and
colour-based policing) on radio interfaces

User Manual 3DB19901AFAA Edition 01

Functional description

The same VLAN ID can be used by several ATM PW flows only if they share the same
CoS and forwarding plane. Thinking to future releases, to use the same VLAN ID, the ATM
PW flows must also share the same encapsulation format (i.e. N-1 cell mode with or
without Control Word, AAL5 SDU or PDU modes).
A VLAN ID that is used by ATM PW flow(s) can never be used for TDM flows.
The fields of the 802.1Q VLAN Tag to be inserted into ATM PW flow frames are assigned
in the following manner:

12-bit VLAN ID will be provisioned by ECT/NMS

3-bit PCP field is assigned according to the ATM PW flow COS and packet profiled
scheduling

1-bit CFI field is set to 0

2.8.19.3.4 VLAN Swap


VLAN Swap feature is foreseen on "hand-off" MPR NE, i.e. the NE connected to IP/MPLS
network.
VLAN Swap means that ATM PW flows ingressing/egressing the "hand-off" MPR will
have the same common "external" VLAN ID, while within MPR network each ATM PW
flow will use its own "internal" VLAN ID (may be shared among several ATM PW flows
with same path and CoS).
To avoid possible configuration clashing, the above "external" VLAN ID should belong to
the allowed range. Moreover, the "external" VLAN ID should be different from each
"internal" VLAN ID.
VLAN Swap performed by the "hand-off" MPR NE is based on:

for ingress, IP/MPLS network MPR network direction: the Inbound PW Label
value

for egress, MPR network IP/MPLS network direction: ATM PW CoS (to reduce
numbers of "rules" used for such mapping).

2.8.19.3.5 802.1p remarking


In addition to VLAN Swap, 802.1p bits remarking are also applied by "hand-off" MPR NE
to ATM PW frames:

for ingress, IP/MPLS network MPR network direction: all frames will be declared
as "green"

User Manual 3DB19901AFAA Edition 01

311

Functional description

for egress, MPR network IP/MPLS network direction: 802.1p bits will copy ATM
PW Exp Bits

2.8.19.3.6 Tunnel Label


The MPLS Tunnel Label for ATM PW frames is foreseen only for compatibility with
ATMoMPLS protocol stack.
MPR network is actually not using information from MPLS Tunnel Label value in ATM
PW frames, for example:

forwarding is based on VLAN/MAC DA

CoS assignment of such frames will be always based on PW Label Exp bits

Tunnel Label fields to be inserted into ATM PW frames generated by MPR are assigned as
below reported:

20-bit Tunnel Label will be provisioned by ECT/NMS

EXP bits are copied from PW Label Exp bits

BoS bit is set to 0

TTL field is set to 255

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

802.1ad (Provider bridge)

2.8.20.1 802.1D (MAC Address bridge)

312

User Manual 3DB19901AFAA Edition 01

Functional description

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

2.8.20.2 802.1Q (Virtual bridge)


When the NE is configured in this mode, the management of Ethernet traffic looking the
VLAN is enabled.In this modality, a 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 also be different from the Flow Id associated to E1 tributaries not yet cross
connected.

2.8.20.3 802.1ad (Provider bridge)


When the NE is configured in Provider Bridge mode, the forwarding of Ethernet traffic is
managed according to Service VLAN. Each Service VLAN (S-VLAN) represents a service
instance that Ethernet traffic from a customer network is mapped to.
In Provider Bridge mode, an S-VLAN is assigned to all Ethernet frames managed by the
NE. The assignment of an S-VLAN to an Ethernet frame ingressing the NE shall be done
according to the type of the Provider Bridge port:

NNI: this is an interface internal to the Provider Bridged Network. S-VLAN is


assigned based on S-VLAN ID carried by S-VLAN Tag or based on the ingress
interface in case of S-VLAN untagged frames

UNI (port based): this is an interface at the edge of the Provider Bridged Network. SVLAN is assigned based on User Ethernet port (Port-based service interface)
regardless of the type of customer traffic (C-VLAN tagged or untagged)

UNI (VLAN-based): this is an interface at the edge of the Provider Bridged Network.
S-VLAN is assigned based on C-VLAN ID carried by C-VLAN Tag or based on User
Ethernet port in case of untagged frames (C-tagged service interface)

You can change the type of a Provider Bridge port. The following rules apply:

An NNI can be changed to a port-based UNI only if the NNI was in the member set
and untagged set of only one S-VLAN.

User Manual 3DB19901AFAA Edition 01

313

Functional description

An NNI can be changed to a VLAN-based UNI only if the NNI was in the untagged
set of all S-VLANs it belonged to.

A port-based UNI can be changed to an NNI or a VLAN-based UNI with no


restrictions about its S-VLAN membership. The new port type inherits the S-VLAN
membership and untagged set membership from the port-based UNI.

A VLAN-based UNI can be changed to an NNI with no restrictions about its S-VLAN
membership. The NNI inherits the S-VLAN membership and untagged set
membership from the VLAN-based UNI. Any C-VLAN to S-VLAN assignments
must be removed from the VLAN-based UNI before changing it to an NNI.

A VLAN-based UNI can be changed to a port-based UNI only if it was in the member
set and untagged set of only one S-VLAN. Any C-VLAN to S-VLAN assignments
must be removed from the VLAN-based UNI before changing it to a port-based UNI.

2.8.20.4 Bridge type change

2.8.20.4.1 Changing from 802.1D (MAC bridge) to 802.1ad (Provider bridge)


The change of NE bridge mode from MAC Bridge to Provider Bridge does not require the
removal of existing cross-connections.
All User Ethernet and Ethernet LAG interfaces are set as NNI with S-VLAN TPID equal
to 0x8100. The S-VLAN table is empty except for S-VLAN 1.

2.8.20.4.2 Changing from 802.1Q (Virtual Bridge) to 802.1ad (Provider bridge)


The change of NE bridge mode from Virtual Bridge to Provider Bridge does not require the
removal of existing cross-connections or the removal of VLANs defined in the VLAN
Table.
All User Ethernet and Ethernet LAG interfaces are set as NNI with S-VLAN TPID equal
to 0x8100. The S-VLAN Table is filled with S-VLANs having S-VLAN ID equal to the
VLAN ID of VLANs previously defined in the VLAN Table. Port VLAN ID and Port
Priority assigned to User Ethernet interfaces are assigned as Port S-VLAN ID and Port
Priority of NNIs. This allows continuing to deliver existing C-VLAN tagged Ethernet
traffic even if the NE bridge mode is changed to Provider Bridge. C-VLANs are seen by
the NE as S-VLANs since all the ports are NNI with an S-VLAN TPID the same as the CVLAN TPID.
The C-VLAN Translation feature is not available when the NE is configured in Provider
Bridge mode. The request to enable the Provider Bridge mode when there are translated CVLANs on any User Ethernet interface will be refused.
314

User Manual 3DB19901AFAA Edition 01

Functional description
2.8.20.4.3 Changing bridge mode configuration from 802.1ad (Provider Bridge) to
802.1D (MAC Bridge)
The change of NE bridge mode from Provider Bridge to MAC Bridge does not require the
removal of existing cross-connections. All defined S-VLANs must be removed.
The NE will check for S-VLANs before performing the change. If an S-VLAN is present,
the NE will refuse to migrate from Provider Bridge to MAC Bridge mode.

2.8.20.4.4 Changing bridge mode configuration from to 802.1ad (Provider Bridge)


to 802.1Q (Virtual Bridge)
The change of NE bridge mode from Provider Bridge to Virtual Bridge does not require the
removal of existing cross-connections.
All defined S-VLANs must be removed from the S-VLAN table and from any other
parameters involving S-VLAN IDs.
All User Ethernet and Ethernet LAG interfaces previously configured as NNI will take Port
Priority and Acceptable Frame Type parameters from the NNI. The Port VLAN ID is set
equal to the Port S-VLAN ID of the NNI, which will be VLAN 1 due to the removal of
configured VLANs from the table.
All User Ethernet interfaces previously configured as either UNI (port-based) or UNI
(VLAN-based) will take Port Priority from either UNI (port-based) or UNI (VLAN-based).
The Port VLAN ID is set to the Port S-VLAN ID of the UNI, which is VLAN 1 after
removal of the S-VLAN IDs. The Acceptable Frame Type is set to the default value, Admit
all.

2.8.20.4.5 Changing from 802.1Q (Virtual Bridge) to 802.1D (MAC bridge)


To change the bridge type from 802.1Q to 802.1D, the content of the VLAN table and the
VLAN assigned to the user Ethernet ports (refer to Reserved Multicast Addresses) has to
be deleted before the bridge type is changed.

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

User Manual 3DB19901AFAA Edition 01

315

Functional description

Discard - The system discards all ingress Ethernet frames and must not generate any
egress Ethernet Frame carrying the reserved multicast address.

Forward - The system accepts all ingress Ethernet frames as standard multicast
frames and forwards them accordingly.

Peer - The system acts as a peer of the connected device in the operation of the
relevant Layer 2 Control Protocol.
Table 2.63 Reserved Multicast Addresses

Reserved Multicast
Address

Function

Action

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


(OAM) of IEEE 802.3

Peer for Link Aggregation and ESMC

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

CCM and LTM Group Destination MAC


Addresses (IEEE 802.1ag)

Peer/Forward

Discard for QAM

01-80-C2-00-00-0D

01-80-C2-00-00-1F

01-80-C2-00-00-2F
01-80-C2-00-00-30 01-80-C2-00-00-3F

2.8.20.5 Advanced Ethernet features

316

User Manual 3DB19901AFAA Edition 01

Functional description

For each user Ethernet port (in Core unit or in EAS/EASv2 unit) the following advanced
Ethernet features as supported:
1.

C-VLAN Translation

2.

Port Based Rate Limiter (Ingress and/or Egress)

3.

Storm Control (Ingress)

4.

VLAN Based Rate Limiter (Ingress)

2.8.20.5.1 C-VLAN Translation


The system supports C-VLAN Translation on user Ethernet interfaces, the translation is
applied bi-directional.
Tagged ingress frames entering the User Ethernet interface, C-VLAN ID (From), are
changed to a new C-VLAN ID (To). At the same time, tagged egress frames, C-VLAN ID
(To) are changed to C-VLAN ID (From) exiting the User Ethernet interface.
The PCP field and CFI field are left unchanged.
The available set of C-VLAN IDs (To) is the list of VLAN IDs which have the User
Ethernet interface as a member of the VLAN port set.
The available set of C-VLAN IDs (To) is the list of VLAN IDs which have the User
Ethernet interface as a member of the VLAN port set and which have at most two ports
(User Ethernet interface and another either Ethernet or Radio port) as members of
the VLAN port set.
C-VLAN Translation is supported:

in 802.1Q Virtual Bridge mode

on Core-E user Ethernet interfaces

on EAS user Ethernet interfaces

up to eight C-VLAN IDs (from) can be translated to C-VLAN IDs (to) per user
Ethernet interface

A User Ethernet interface can not be disabled when the C-VLAN Translation feature is
enabled on the interface.
When a C-VLAN ID is selected as C-VLAN ID (To), the following actions are not
permitted:

modification of the C-VLAN parameters

deletion of the C-VLAN ID

C-VLAN Translation is provisioned using the Craft Terminal.


User Manual 3DB19901AFAA Edition 01

317

Functional description

The VLAN ID selected as C-VLAN ID (From) does not require VLAN creation using the
VLAN Configuration Tool.
When a VLAN ID is selected as C-VLAN ID (From), the creation/modification of that
VLAN in the VLAN Configuration Tool is not supported.
C-VLAN Translation feature is not supported with the following features:

Ethernet Ring Protection Switching (ERPS)

L2 Radio Link Aggregation

VLAN Rate Limiter

ECFM

2.8.20.5.2 Port Based Rate Limiting


The system supports Port based Rate Limiting on user Ethernet interfaces. Port based Rate
Limiting allows a user to provision on a per user Ethernet port basis the maximum data rate
on ingress and egress directions.
The Rate Limiter is managed according to a Leaky Bucket algorithm, Ethernet frames that
do not find room in the Bucket are dropped.
The parameters of Rate Limiter are:

Committed Information Rate (CIR): Ethernet throughput not taking into account
Preamble and IFG frames.

Committed Burst Size (CBS)

CIR is configured in the range from 64 Kbit/s to 1,000,000 Kbit/s in step of 64 Kbit/s. The
default value for CIR is 64 Kbit/s.
CBS is configured in the range from 4 Kbytes (4096 bytes) to 16 MBytes in steps of 4
Kbytes. The default value for CBS is 12 Kbytes.
Ingress Rate Limiter and Egress Rate Limiter can be enabled/disabled independently.
Port based Rate Limiting is supported:

in 802.1D MAC Bridge, 802.1Q Virtual Bridge, and 802.1ad Provider Bridge mode

on Core-E user Ethernet interfaces

on EAS user Ethernet interfaces

A User Ethernet interface can not be disabled when the Port based Rate Limiting feature is
enabled on the interface.

318

User Manual 3DB19901AFAA Edition 01

Functional description

Port based Rate Limiting is provisioned using the Craft Terminal.


In cases were Port based Rate Limiting was provisioned using file based configuration, it
is required to remove the file based Port based Rate Limiting configuration prior to
provisioning using the Craft Terminal.

2.8.20.5.3 Storm Control (Broadcast, Multicast, and unknown Unicast)


The system supports traffic Storm Control for the following Ethernet traffic frame types:

Broadcast

Multicast

Unknown Unicast

Storm Control provides a mechanism to control the effects of broadcast, multicast, and
unknown unicast storms on physical user Ethernet interfaces. This helps prevent traffic
storms from being disruptive and degrading network performance.
When storm control is enabled, and in a 1 second time interval, the number of broadcast,
multicast, and/or unknown unicast Ethernet frames exceeds the configured threshold, a
dropping mechanism is applied.
Frame rate thresholds can be provisioned for broadcast, multicast, and unknown unicast
traffic. Frame rate thresholds are configured from 0 Frame/s to 16,777,215 Frame/s. The
default threshold for all frame types is 100 Frame/s.
Storm Control is supported:

in 802.1D MAC Bridge, 802.1Q Virtual Bridge, and 802.1ad Provider Bridge mode

on Core-E user Ethernet interfaces

on EAS user Ethernet interfaces

Storm Control is enabled/disabled for all supported frame types at one time.
A User Ethernet interface can not be disabled when the Storm Control feature is enabled on
the interface.
Storm Control is provisioned using the Craft Terminal.
In cases were the Storm Control feature was provisioned using file based configuration, it
is required to remove the file based Storm Control configuration prior to provisioning using
the Craft Terminal.

User Manual 3DB19901AFAA Edition 01

319

Functional description
2.8.20.5.4 VLAN based Rate Limiter
The system supports a VLAN based Rate Limiter on user Ethernet interfaces for the ingress
direction. VLAN based Rate Limiter allows a user to provision, on a per VLAN ID basis,
the maximum data rate for the ingress direction.
The VLAN IDs available for VLAN based Rate Limiter are those which include the User
Ethernet interface as a member of the VLAN port set.
Note: If a VLAN rate limiter is set on a port, the VLAN cannot be modified. The rate
limiting must be removed before making any change.

The Rate Limiter is managed according to a Token Bucket algorithm, Ethernet frames that
do not find available tokens are dropped.
The parameters of VLAN Rate Limiter are:

Committed Information Rate (CIR): Ethernet throughput not taking into account
Preamble and IFG frames.

Committed Burst Size (CBS)

CIR is configured in the range from 64 Kbit/s to 32 Gbit/s in step of 64 Kbit/s. The default
value for CIR is 64 Kbit/s.
CBS is configured in the range from 4 Kbytes (4096 bytes) to 2 MBytes. The default value
for CBS is 16 Kbytes.
VLAN based Rate Limiter is supported:

in 802.1Q Virtual Bridge mode and 802.1ad Provider Bridge mode

on Core-E user Ethernet interfaces

on EAS user Ethernet interfaces

up to eight VLAN IDs per user Ethernet interface

A User Ethernet interface can not be disabled when the VLAN based Rate Limiter feature
is enabled on the interface.
When a VLAN based Rate Limiter is enabled on a VLAN ID, the following actions are not
permitted:

modification of the VLAN parameters

deletion of the VLAN ID

VLAN Rate Limiter should not be activated in conjunction with Port based Rate Limiter.
VLAN based Rate Limiter is provisioned using the Craft Terminal.
320

User Manual 3DB19901AFAA Edition 01

Functional description

In cases where a VLAN based Rate Limiter was provisioned using file based configuration,
it is required to remove the file based VLAN based Rate Limiter configuration prior to
provisioning using the Craft Terminal.

2.8.20.5.5 Per-VLAN Per-CoS Rate Limiter


The system supports a per-VLAN per-COS Rate Limiter on user Ethernet interfaces for the
ingress direction.
The rate limiter is applied to a tagged Ethernet flow classified according to the VLAN ID
and PCP fields of the VLAN tag. The flow is identified by one VLAN ID value and one
PCP value.
If the NE is in Provider Bridge mode, the VLAN ID and PCP for rate limiting are taken
from the S-VLAN Tag. If QoS classification based on DiffServ is in use, the PCP value is
the Forwarding Class assigned to the DSCP value carried by the Ethernet frame.
The VLAN IDs available for per-VLAN per-COS Rate Limiter are those which include the
User Ethernet interface as a member of the VLAN port set.
The Rate Limiter is managed according to a Token Bucket algorithm, Ethernet frames that
do not find available tokens are dropped.
The parameters of per-VLAN per-COS Rate Limiter are:

Committed Information Rate (CIR): Ethernet throughput not taking into account
Preamble and IFG frames.

Committed Burst Size (CBS)

CIR is configured in the range from 0 Kbit/s to 1 Gbit/s in step of 64 Kbit/s. The default
value for CIR is 64 Kbit/s. A value of 0 Kbit/s indicates a drop of the Ethernet flow.
CBS is configured in the range from 4 Kbytes (4096 bytes) to 16 MBytes. The default value
for CBS is 16 Kbytes. The allowed values for CBS are:

4 Kbytes

8 Kbytes

16 Kbytes

32 Kbytes

64 Kbytes

128 Kbytes

256 Kbytes

512 Kbytes

1 Mbytes

User Manual 3DB19901AFAA Edition 01

321

Functional description

2 Mbytes

4 Mbytes

8 Mbytes

16 Mbytes

Per-VLAN Per-COS Rate Limiter is supported:

in 802.1Q Virtual Bridge mode

in 802.1ad Provider Bridge mode

on Core-E user Ethernet interfaces

on EAS user Ethernet interfaces

Up to 16 Rate Limiters can be activated per User Ethernet interface, up to 32 Rate Limiters
can be activated on a Core-E card and up to 32 Rate Limiters can be activated on each
P8ETH card.
A User Ethernet interface can not be disabled when the per-VLAN per-COS Rate Limiter
feature is enabled on the interface.
When a per-VLAN per-COS Rate Limiter is enabled on a VLAN ID, the following actions
are not permitted:

modification of the VLAN parameters

deletion of the VLAN ID

Per-VLAN per-COS Rate Limiter should not be activated in conjunction with VLAN based
Rate Limiter.
Caution: When a Per-VLAN Per-CoS Rate Limiter is activated in conjunction with a Port
Rate Limiter, the Per-VLAN Per-CoS Rate Limiter must apply to Ethernet frames that meet
the Port Rate Limiter parameters.

Per-VLAN per-COS Rate Limiter is provisioned using the Craft Terminal.


In cases where a VLAN based Rate Limiter was provisioned using file based configuration,
it is required to remove the file based VLAN based Rate Limiter configuration prior to
provisioning using the Craft Terminal.

2.8.21 LAG (Link Aggregation Group)


2.8.21.1 LAG overview
322

User Manual 3DB19901AFAA Edition 01

Functional description

Link Aggregation groups a set of ports so that two network nodes can be interconnected
using multiple links to increase link capacity and availability between them.
When aggregated, two or more physical links operate as a single logical link with a traffic
capacity that is the sum of the individual link capacities.
This doubling, tripling or quadrupling of capacity is relevant where more capacity is
required than can be provided on one physical link.
Link aggregation also provides redundancy between the aggregated links. If a link fails, its
traffic is redirected onto the remaining link, or links.
If the remaining link or links do not have the capacity needed to avoid a traffic bottleneck,
appropriate QoS settings are used to prioritize traffic so that all high priority traffic
continues to get through.
The Link Aggregation is performed according to 802.3ad and can be applied to Radio ports
and to User Ethernet ports.

2.8.21.1.1 Link aggregation on Radio ports (Radio LAG)


Link aggregation can be applied to radio ports (in this case it is named Radio Link
Aggregation).
Figure 2.110 Radio LAG overview

In this example, user traffic is split up into radio channels. Main advantages:

Throughput. The overall radio Ethernet throughput can be more than 1 Gbit/sec.

Protection. In case of a failure of one of the three channels, all the traffic is redirected
on the remaining links (with a reduction in throughput). The discarded or dropped
traffic is the one with lower priority: high priority traffic is still running on the
remaining active channels.

User Manual 3DB19901AFAA Edition 01

323

Functional description
Figure 2.111 Radio LAG

The radio LAG can be implemented with each type of supported ODU.
Note: One MPT per MPT Plug-in unit.

Two types of Radio LAG can be configured:

L1 Radio (Layer 1)

L2 Radio (Layer 2)

Note: For an overview on the Layer 1 Radio LAG scenarios refer to Radio Layer 1 Link
Aggregation scenarios.

2.8.21.1.2 Link aggregation on User Ethernet ports (Ethernet LAG)


Link aggregation can be applied to Ethernet user ports (electrical or optical) on the same
Core-E unit.
The LACP protocol is supported.

324

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.112 Ethernet LAG

Only one type of Ethernet LAG can be configured:

L2 Ethernet (Layer 2).

2.8.21.1.3 Radio Layer 1 Link Aggregation scenarios


Layer 1 Link Aggregation allows the aggregation of multiple links in order to obtain a
unique logical connection with increased traffic capacity.
A Layer 1 Link Aggregation Group (L1 LAG) represents the group of links bundled
together between two Aggregation Systems (NEs connected through the L1 LAG).
Each Aggregation System comprises the following entities:

QoS: performs buffering and scheduling functions based on the L1 LAG aggregated
bandwidth

Distributor: spreads the traffic over aggregation links belonging to L1 LAG according
to a distribution algorithm

Collector: receives traffic from aggregation links belonging to L1 LAG and combines
them together to create a single traffic flow.

User Manual 3DB19901AFAA Edition 01

325

Functional description

In Layer 1 Link Aggregation, the Distributor performs a packet-based traffic distribution


over multiple links regardless of the content of the packets. Distributor takes into account
the number of bytes sent over a specific link and loads links according to the available
bandwidth. As a consequence, Layer 1 Link Aggregation allows a traffic load balancing
independently of traffic content. Since the distribution does not depend on Layer 2 or Layer
3 header content, this kind of Link Aggregation is called Layer 1 (i.e., associated to the
physical layer).
L1 LAG ports are supported on MPT-HC/HC-HQAM/XP/XP-HQAM radio interfaces
configured with P8ETH or EASv2 SFP ports, and on MPT-HLS interfaces configured with
EASv2 ports.
MPT-HC/HC-HQAM/XP/XP-HQAM radio interface must be configured with a P8ETH or
EASv2 card.

The following radio configurations are supported if connected to a P8ETH card:

1+0 MPT-HC/HC-HQAM/XP/XP-HQAM connected to P8ETH SFP port

The following radio configurations are supported if connected to an EASv2 card:

1+0 MPT-HC/HC-HQAM/XP/XP-HQAM connected to EASv2 SFP port

1+0 MPT-HC/HC-HQAM/XP/XP-HQAM connected to EASv2 RJ45 port

1+0 MPT-MC connected to EASv2 RJ45 port

1+0 MPT-HLS connected to EASv2 SFP port

1+1 MPT-HC/HC-HQAM/XP/XP-HQAM connected to EASv2 SFP port

RPS protection without cable is not supported with L1 LAG for 1+1 MPT-HC/HC-HQAM/
XP/XP-HQAM: the protection must be set up using the RPS optical cable.
L1 LAG is not supported with MSS-1 equipment.
Supported L1 LAG port configurations:

up to four L1 LAG ports per NE

up to four MPT-HC/HC-HQAM/XP/XP-HQAM ports per L1 LAG port

static and adaptive modulation

radio interfaces must reside on the same horizontal shelf row (for example, MSS-8
shelf, slots 3 and/or 4).

It is possible to configure an L1 LAG with MPT-HC and MPT-HC-HQAM in the same


group. This combination is for upgrade scenarios, when an MPT-HC is replaced with an
MPT-HC-HQAM in legacy mode. No other use for this configuration is recommended.
Members of a L1 LAG port configured with static modulation must be configured:

326

As the same radio interface type, except in the case of MPT-HC/XP and MPT-HC/
XP-HQAM
User Manual 3DB19901AFAA Edition 01

Functional description

All radio interfaces configured with the same modem profile

static modulation type (mode set to preset)

channel spacing (Reference Channel Spacing)

modulation scheme

Radio ports with XPIC profiles can be part of the same LAG as radio ports with non-XPIC
profiles. All other radio parameters must be the same.
The following configuration changes are prohibited when a radio interface is configured as
a member of a static modulation L1 LAG port:

frequency settings

channel spacing (Reference Channel Spacing)

option

modulation scheme

Members of a L1 LAG port configured with adaptive modulation must be configured:

As the same radio interface type, except in the case of MPT-HC/XP and MPT-HC/
XP-HQAM

All radio interfaces configured with the same modem profile

adaptive modulation type (mode set to Adaptive Modulation)

channel spacing (Reference Channel Spacing)

To guarantee LAG traffic integrity the recommended minimum channel spacing supported
is 14 MHz.
L1 LAG radio interfaces configured with adaptive modulation are not required to be
configured with the same modulation range and reference modulation.
The modulation range and reference modulation may be changed while a radio interface is
configured as a members of an adaptive modulation L1 LAG port.
The following configuration changes are prohibited when a radio interface is configured as
a member of a adaptive modulation L1 LAG port:

frequency settings

channel spacing (Reference Channel Spacing)

option

User Manual 3DB19901AFAA Edition 01

327

Functional description
2.8.21.1.4 L1 LAG with EASv2
If connected to an EASv2, MPT-HC in 1+0 and 1+1 configuration, MPT-HC-HQAM//XP/
XP-HQAM in 1+0 and 1+1 configuration, MPT-MC in 1+0 configuration, and MPT-HLS
in 1+0 or 1+1 configuration are supported.
LAG L1 configurations with EASv2 with mixed MPT-HC/MPT-HC-HQAM or MPT-XP/
MPT-XP-HQAM radios are supported if 4QAM is not used as minimum modulation
scheme.
The following can be connected to either optical or electrical ports on the EASv2:

MPT-HC/XP in 1+0 configuration

MPT-HC-HQAM/XP-HQAM in 1+0 configuration

The following must be connected to optical ports:

MPT-HLS

MPTs in 1+1 configuration

MPT-MC in 1+0 configuration must be connected to an electrical port. MPT-MC in 1+1


configuration cannot be added to an L1 LAG.
MPTs connected to optical ports and MPTs connected to electrical ports cannot be part of
the same LAG.
An optical LAG and an electrical LAG cannot be configured on the same EASv2 card or
on the same MSS row.
MPT-HC/HC-HQAM/MC and MPT-HLS cannot be part of the same LAG.
It is possible to configure an L1 LAG with MPT-HC and MPT-HC-HQAM in the same
group. This combination is for upgrade scenarios, when an MPT-HC is replaced with an
MPT-HC-HQAM in legacy mode. No other use for this configuration is recommended.
L1 LAG with EASv2 offers hitless switching: if propagation conditions worsen on one or
more links in one direction, the LAG can remove the link, preventing a loss of traffic.

2.8.21.1.4.1 SDH2SDH flows with L1 LAG on EASv2


It is possible to create a cross-connection of SDH2SDH flows from an SDHACC card to an
L1 Radio LAG on an EASv2 card. SDH2SDH flows cannot be cross-connected to any other
LAG.
The maximum number of SDH2SDH flow cross-connections to an L1 LAG is 16.

328

User Manual 3DB19901AFAA Edition 01

Functional description

If the LAG rate decreases below the bandwidth required to support all the SDH flows,
congestion and frame loss in the LAG egress queue could result. To prevent this issue, the
9500 MPR selectively drops a subset of the cross-connected SDH flows to ensure that
enough bandwidth is available to transmit the remaining flows. Drop priority can be
configured for each SDH flow: see chapter 3.

2.8.21.1.5 Types of L1 Link Aggregation


L1 Link Aggregation is implemented inside the card.
Two configuration are supported to create L1 LAG:

Intra plug-in LAG

Cross Plug-in LAG

A block diagram of L1 Link Aggregation configurations is shown in Figure 2.113.


Figure 2.113 Types of L1 LAG

Plug-In

MPT

CORE

Plug-In
CORE
MPT

Plug-In

MPT

Plug-In
MPT

Cross Plug-in Link Aggregation

Intra Plug-in Link Aggregation


22899

2.8.21.1.6 Intra Plug-in L1 Link Aggregation Scenario


Intra plug-in LAG is a LAG with MPT-HC/HC-HQAM/XP/XP-HQAM or MPT-HLS
connected to the same card.
An example of Intra Plug-in LAG implementation is shown in Figure 2.114. Site A is
configured with four radio links in an Intra Plug-in LAG configuration. Site B is configured
with two intra Plug-in LAGs to implement a radio repeater configuration.

User Manual 3DB19901AFAA Edition 01

329

Functional description
Figure 2.114 Intra Plug-in L1 Link Aggregation Scenario
Core NE A

Core NE B
Embedded
Segregation

Plug-in 1

Plug-in 1

Plug-in 2
Stacking

LAG A

LAG B

LAG A

4 RF
Channels

4 RF
Channels

22893

In the event of a radio link failure, the capacity of the LAG is reduced by the capacity of
the radio link.
In the event of a Plug-in (card) failure, the associated LAG direction is lost.
Single card, Intra Plug-in supported L1 LAG configurations are shown in Figure 2.115.
Dual card Intra Plug-in supported L1 LAG configurations are shown in Figure 2.115.
Figure 2.115 Single card 1+0 Intra Plug-in L1 LAG Configurations

G = number of Link Aggregation Groups


S = LAG Size (Number of Radio Protection Groups in the LAG)
Links with the same letter (A or B) belong to the same group
Diagram shows two MSS Slots on the same row. SFP Ports represented only (from Port5 to Port8)
Master Ports indicated in bold
22894

330

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.116 Dual card 1+0 Intra Plug-in L1 LAG Configurations
Port5 on one card protected with
Port5 on the other card, ...
A*-A represent protection groups:
*-Main -Spare
A/B with no symbols represents a 1+0 radio
in this diagram
Operator first creates HSB/SD
protection groups and then
aggregates them. Size parameter
represents the number of
protection groups + number of 1+0 radios
in the LAG

G = number of Link Aggregation Groups


S = LAG Size (Number of Radio Protection Groups in the LAG)
Links with the same letter (I.e., A) belong to the same group
Diagram shows two MSS Slots on the same row. SFP Ports represented only (from Port5 to Port8)
Master Ports indicated in bold

22896

2.8.21.1.7 Cross Plug-in L1 LAG Scenarios


Cross Plug-in LAG is a LAG with MPTs connected to two P8ETH or EASv2 cards on the
same MSS row. The two cards must be the same type: cross plug-in LAG with a P8ETH
card and an EASv2 card is not supported.
An example of Cross Plug-in LAG implementation is shown in Figure 2.117. Site A is
configured with four radio links in a Cross Plug-in LAG configuration. Site B is configured
with two Cross Plug-in LAGs to implement a radio repeater configuration.
Figure 2.117 Cross Plug-in L1 Link Aggregation Scenario
Core NE A

Core NE B
Embedded
Segregation

Plug-in 1

Plug-in 2
Stacking

Embedded
Segregation

Plug-in 1
LAG A

LAG A

LAG A

4 RF
Channels

Plug-in 2
Stacking

LAG B

LAG A

LAG B

4 RF
Channels

22891

User Manual 3DB19901AFAA Edition 01

331

Functional description

In the event of a radio link failure, the capacity of the LAG is reduced by the capacity of
the radio link.
In the event of a Plug-in (EAS) failure, the LAG capacity is reduced, but the LAG direction
is maintained utilizing the remaining radio interfaces supported by the other Plug-in.
Supported Cross Plug-in L1 LAG configurations are shown in Figure 2.117.
Figure 2.118 1+0 Cross Plug-in L1 LAG Configurations

G = number of Link Aggregation Groups


S = LAG Size (Number of Radio Protection Groups in the LAG)
Links with the same letter (A or B) belong to the same group
Diagram shows two MSS Slots on the same row. SFP Ports represented only (from Port5 to Port8)
Master Ports indicated in bold
22892

2.8.21.1.8 L1 LAG Creation


L1 LAG is created using the following parameters:

LAG ID (LAG Identifier): is mandatory parameter that identifies the LAG in the NE

LAG Name: is an optional parameter which assist the operator to identify the virtual
radio direction. LAG Name is up to 32 characters in length.

LAG Type: is a mandatory parameter that defines the LAG type (i.e., L1 Radio, L2
Radio, L2 Ethernet).

LAG Size: is a mandatory parameter that configures the maximum number of radio
links included in the L1 LAG. LAG Size cannot be lower than the number of radio
links belonging to the LAG.

Administrative Status: indicates the operational status of the LAG and is configured
by the operator

LAG ID is selected with the following restrictions:

332

integer from 1 to 14

User Manual 3DB19901AFAA Edition 01

Functional description

cannot be same as LAG ID of an existing L1/L2 LAG ID

cannot be equal to the Administrative Key of an existing L2 LAG

When the administrative state of the LAG is disabled, no traffic is sent out the LAG. No
LAG alarms are reported to the WebEML.
When the administrative state of the LAG is enabled, the LAG is available for the
following:

cross-connections

802.1Q port membership

selected as synchronization reference

A LAG cannot be disabled when involved in any of the following:

cross-connections

802.1Q port membership

selected as synchronization reference

The following features are supported at the L1 LAG level:

Wait-To-Restore (WTR)

TMN RF

SSM

A Wait-To-Restore timer provides a mechanism to minimize the impact to LAG capacity


by fast/intermittent failures on a radio link member of the LAG. WTR time is configurable
from 100 milliseconds to 8 seconds. The default value is 1 second.
When a radio link member of a LAG declares a traffic affecting condition, that member is
removed from the available radio links and the capacity of the LAG is reduced accordingly.
Once the failure condition is cleared, the WTR period is applied. Upon expiration of the
WTR period, if the radio link remains condition free, the radio link is restored as a member
of the LAG and becomes available to carry traffic. The capacity of the LAG is increased
accordingly.
The following LAG parameters can be modified after creation:

Port membership

LAG Name

LAG Size

Wait to Restore time

User Manual 3DB19901AFAA Edition 01

333

Functional description
2.8.21.1.9 L1 LAG Lowest index port
A LAG Lowest index port is defined for each LAG. The Lowest index port is responsible
to transmit traffic from the Distributor (near end) towards the Collector (far end) and vice
versa.
Lowest index port is selected from SFP ports 5 or 7 depending on LAG configuration
scenario.
Lowest index port is configured using the following:

Intra Plug-in

Port 5 or Port 7

the interface with the lowest index in the LAG port membership (i.e., if Lowest
index port is Port 7, Port 5 and/or Port 6 cannot be added to the LAG).

one Lowest index port per LAG

Cross Plug-in

port 5 or port 7 on both cards configured in LAG

the interface with the lowest index in the LAG port membership (i.e., if Lowest
index port is port 7, port 5 or port 6 cannot be added to the LAG).

one Lowest index port is main (active)

one Lowest index port is spare (standby)

For Intra Plug-in LAG, the active Lowest index port is configured on the card hosting LAG.
For Cross Plug-in LAG, the active Lowest index port is configured:

left card (slots 3, 5, or 7) port 5 when available

right card (slots 4, 6, or 8) port 7 when available

When a mixture of Intra/Cross Plug-in LAGs are configured on the same row, the active
Lowest index port of the Cross Plug-in LAG is configured on a different plug-in used by
the Intra Plug-in LAG.

2.8.21.1.10 Port Provisioning Rules


During port membership add/remove operation, the following rules apply:

334

Lowest index port(s) must always be present in the set of ports attached to the LAG

considering the slot, Lowest index port shall have the lowest index in the LAG port
membership.

Port 5 or Port 7

one Lowest index port per Intra Plug-in L1 LAG


User Manual 3DB19901AFAA Edition 01

Functional description

two Lowest index ports per Cross Plug-in L1 LAG

Set of ports added to the LAG shall be adjacent considering the slot. No holes are
allowed in the L1 LAG port membership filtered by slot (i.e., ports 5, 7, and 8 are not
an allowed configuration).

For Cross Plug-in configuration, the maximum number of ports per slot is two. It is
not supported to aggregate 3 ports on one Plug-in and 1 port on the other Plug-in.

Lowest index port cannot be changed. If Lowest index port is Port 7, Port 5 and Port
6 cannot be added to the L1 LAG.

Port add/remove operation rules are applied for all port add and port remove
operation. Checks are performed on the entire set of ports.

radio port is eligible to be a member of only one L1 LAG.

2.8.21.1.11 Intra Plug-in Port Membership


Table 2.64 provides a list of supported 1+0 Intra Plug-in L1 LAG configurations. L1 LAG
group Lowest index port is indicated in bold, X.
Table 2.64 Intra Plug-in L1 LAG Supported 1+0 Configurations: Single LAG Group
CONFIG

LAG
SIZE

LEFT EAS (SLOTS 3, 5, 7)


P5

P6

P7

P8

P5

P6

P7

P8

I1

I2

I3

I4

I5

I6

I7

I8

I9

I10

I11

I12

User Manual 3DB19901AFAA Edition 01

RIGHT EAS (SLOTS 4, 6, 8)

335

Functional description
2.8.21.1.12 Cross Plug-in Port Membership Configurations
Cross Plug-in L1 LAG Supported 1+0 Configurations: Single LAG Group provides a list
of supported 1+0 Cross Plug-in L1 LAG configurations. L1 LAG group Lowest index ports
(active and standby) are indicated in bold, X.
Table 2.65 Cross Plug-in L1 LAG Supported 1+0 Configurations: Single LAG Group
CONFIG

LAG
SIZE

LEFT EAS (SLOTS 3, 5,7)

RIGHT EAS (SLOTS 4, 6, 8)

P5

P6

P7

P8

P5

P6

P7

P8

C1

C2

C3

C4

C5

C6

C7

C8

2.8.21.1.13 Dual L1 LAG Port Membership Configurations


Up to two L1 LAGs are supported on a horizontal row of the MSS-4/8 shelf.
When two L1 LAGs are located on the same horizontal row, the system locates the master
LAG port on different Plug-in cards when possible. This optimizes throughput and re-order
capabilities for both LAGs.
When a mixture of Intra/Cross Plug-in LAGs are configured on the same row, the active
Lowest index port of the Cross Plug-in LAG is configured on a different plug-in used by
the Intra Plug-in LAG.
Cross Plug-in L1 LAG Supported 1+1 Configurations: Dual L1 LAG Groups provides a list
of supported dual 1+0 L1 LAG configurations. L1 LAG group Lowest index ports (active
and standby) are indicated in bold, A (LAG A) and B (LAG B).

336

User Manual 3DB19901AFAA Edition 01

Functional description

Table 2.66 Cross Plug-in L1 LAG Supported 1+1 Configurations: Dual L1 LAG Groups
GROUP A

GROUP B

LEFT EAS
(SLOTS 3, 5,7)

RIGHT EAS
(SLOTS 4, 6, 8)

CONFIG

LAG
SIZE

CONFIG

LAG
SIZE

P5

P6

P7

P8

P5

P6

P7

P8

C1

C5

C6

C7

C8

C8

C8

C5

C6

C7

C8

C8

C8

C5

C6

C7

C8

C8

C8

C5

C6

C7

C8

C8

C8

C2

C3

C4

User Manual 3DB19901AFAA Edition 01

337

Functional description
Table 2.66 Cross Plug-in L1 LAG Supported 1+1 Configurations: Dual L1 LAG Groups (Continued)
GROUP A

GROUP B

LEFT EAS
(SLOTS 3, 5,7)

RIGHT EAS
(SLOTS 4, 6, 8)

CONFIG

LAG
SIZE

CONFIG

LAG
SIZE

P5

P6

P7

P8

P5

P6

P7

P8

C4

C5

C6

C7

C8

C8

C8

C5

C6

C7

C8

C8

C8

C4

2.8.21.1.14 Port Add Restrictions


To add a radio direction to a Radio L1 LAG port, the radio direction must NOT be
provisioned as a member to any of the following:

cross-connection

VLAN

port segregation

TMN RF enabled on the radio channel

Synchronization reference

SSM

ALL cross-connections, VLANs, and port segregation provisioning must be removed


before adding a Radio direction to a Radio LAG port.
Tx Mute must be provisioned enabled to add a radio direction to an enabled L1 LAG port.
TX Mute should not be disabled until both sides of the radio direction are ready to carry
traffic through the LAG port.

338

User Manual 3DB19901AFAA Edition 01

Functional description
2.8.21.1.15 Port Removal Restrictions
To remove a radio direction from an L1 LAG port, Tx Mute must be provisioned enabled
on both sides of the LAG direction.
ALL cross-connections, VLANs, and port segregation provisioning must be removed from
the L1 LAG port before removing the Lowest index port.
To remove the Lowest index port from a L1 LAG port, the following conditions must exist
on the L1 LAG port:

all other radio ports must be removed from the L1 LAG port

L1 LAG port must be disabled

no cross-connections are configured on L1 LAG

L1 LAG is member of no 802.1Q VLANs (except default VLAN 1)

L1 LAG is member of no port segregation

L1 LAG is not provisioned as a synchronization reference

TMN RF is disabled on the L1 LAG port

SSM is disabled on the L1 LAG port

2.8.21.1.16 Provisionable Radio Parameters for Members of L1 LAG


After a radio port has been added to an L1 Radio LAG port, the following radio interface
parameters may be modified:

Link Identifier

Tx Power/ATPC

Remote Switching Threshold (in Adaptive Modulation)

Tx Mute

Loopback

Note: When the MPT is configured in a Radio L1 LAG, the loopback of the single radio is
not forbidden, but it is not supported.

Performance Monitoring

Alarm Profile

Radio encryption (MPT-HC, MPT-XP, MPT-HC-HQAM, MPT-XP-HQAM, MPTHLS)

For use of the radio encryption feature in a LAG, see the radio encryption portions of
sections Additional Settings tab: Direction area (MPT-HC/HC-HQAM/XP/XP-HQAM)
and Additional Settings tab: Direction area (MPT-HLS).
User Manual 3DB19901AFAA Edition 01

339

Functional description
2.8.21.1.17 L1 Radio LAG Deletion
A L1 LAG can be deleted if:

Administrative state is Disabled

no ports are members of the LAG

2.8.21.1.18 L1 Radio LAG QoS Configuration


NE QoS and queue size settings are applied to the L1 Radio LAG port.

QoS Scheduler settings

QoS Mapping

Radio Queue size

When a radio port is added to the L1 LAG port all custom QoS and queue size configuration
is lost.
When a radio port is removed from a L1 LAG port, the NE QoS settings are applied to the
radio port. The queue sizes are set to the default values.

2.8.21.1.19 L1 Radio LAG Rate


L1 LAG rate represents the total capacity of the L1 LAG port. The LAG rate is determined
by adding the capacity of all radio interfaces included in the LAG port.
For L1 LAG ports configured with adaptive modulation, the radio interface capacity is the
capacity of the highest modulation scheme provisioned for each radio interface included in
the LAG port.

2.8.21.1.20 Maximum Ethernet Frame Length


The maximum Ethernet frame length is:

1540 bytes for mixed TDM and Ethernet traffic

9728 bytes for pure Ethernet traffic

2.8.21.1.21 Admission Control


Admission control is not performed on L1 LAG.

340

User Manual 3DB19901AFAA Edition 01

Functional description

Bandwidth of cross-connected traffic should not exceed the capacity of a single LAG port
member.

2.8.21.1.22 Maximum Number of Cross-Connections


The maximum number of cross-connections supported by L1 LAG is 254.
Cross connections which terminate on a ERPS node where both ring ports are L1 LAG
ports must use the Unicast MAC address of the NE.

2.8.21.1.23 Port Segregation


Port segregation involving the L1 LAG is supported.
The following port segregation involving an L1 LAG are supported:

segregation to user Ethernet or radio ports belonging to same P8ETH or EASv2 card

segregation to user Ethernet ports or radio ports belonging to a P8ETH or EASv2 card
on the same MSS row

segregation of card involved in Intra Plug-in L1 LAG to user Ethernet port connected
to Core-E or other P8ETH or EASv2 cards

segregation of card involved in Intra Plug-in L1 LAG to radio ports connected to


Core-E, MOD300, MPT ACC, or other P8ETH or EASv2 cards

segregation of both cards involved in Cross Plug-in L1 LAG to user Ethernet port
connected to Core-E or other P8ETH or EASv2 cards

segregation of both cards involved in Cross Plug-in L1 LAG to radio ports connected
to Core-E, MOD300, MPT ACC, or other P8ETH or EASv2 cards

2.8.21.1.24 Synchronization
An enabled L1 LAG port can be selected as synchronization reference. The L1 LAG port
is managed as a single logical synchronization reference.
System selects L1 LAG radio link as synchronization reference based upon alarm status of
the individual radio links.
For a synchronization failure, the system selects a new reference from the non-faulted
members of the L1 LAG.
Detection of synchronization degrade on selected reference is consider synchronization
degrade condition against entire L1 LAG because the quality of the reference clock is
supplied by the remote NE.
User Manual 3DB19901AFAA Edition 01

341

Functional description

Synchronization selection is not revertive.

2.8.21.1.25 SSM
SSM is configured at the L1 LAG level.

2.8.21.1.26 TMN-RF Configuration


TMN-RF is configured at the L1 LAG level.

2.8.21.1.27 Available EAS User Ports


Electrical and optical P8ETH or EASv2 ports which are not members of a LAG may be
used for user Ethernet or radio interface ports.

2.8.22 Quality Of Services (QoS)


The QoS function inside 9500 MPR-E is the result of a distributed implementation in the
switch in the Core-E unit and Radio Interface unit. Both those QoS functions are properly
configured in order to get the wished behavior on Ethernet flows that will be transmitted
towards the Radio.

2.8.22.1 QoS configuration


The QoS configuration is the same for all the involved units:

Core-E

P8ETH

EASv2

Modem unit (to interface the ODU300)

MPT-HC/HC-HQAM/MC/XP/XP-HQAM

In the figure is shown an overview of the QoS implementation inside the Core-E unit and
Modem unit which is used to interface the ODU300.

342

User Manual 3DB19901AFAA Edition 01

Functional description
Figure 2.119 QoS configuration

The QoS feature provides eight internal queues to support different traffic priorities. The
QoS function can assign the packet to one of the eight egress transmit queues.

Queue 8 is assigned to TDM2TDM traffic (fixed assignment)

Queue 7 is assigned to TDM2Eth traffic (fixed assignment)

Queue 6 is assigned to TMN (fixed assignment)

Queues 1 to 5 are assigned to Ethernet traffic according to the information inside the
packet as 802.1p field or DiffServ field.

TDM flows classification


All the TDM2TDM traffic flows are assigned to the highest egress priority queue (Q8). All
the TDM2ETH traffic flows are assigned to the Q7 egress priority queue. All the MEF-8
ETH2ETH traffic flows are assigned to the Q5 egress priority queue.
TMN flows classification
All TMN traffic flows are assigned to the Q6 egress priority queue.
QoS based on IEEE std. 802.1p
When 802.1p QoS mechanism is adopted, the reference is the standard IEEE 802.1D-2004
Annex G User priorities and traffic classes that defines 7 traffic types and the
corresponding user priority values.
By the WebEML each Priority Code Point can be assigned to a specific queue (from Q1 to
Q5).
Q5 is the highest priority queue.
QoS based on DiffServ
User Manual 3DB19901AFAA Edition 01

343

Functional description

When DiffServ mechanism is adopted, each packet is classified based on the DSCP field in
the IP header (64 traffic types).
By the WebEML each DiffServ Code Point can be assigned to a specific queue (from Q1
to Q5).
Q5 is the highest priority queue.
ATM PW flows classification
ATM PW flows will be assigned to radio queues according to below table:
Table 2.67 ATM PW flow classifications
ATM PW CoS

Radio Queue

Guaranteed (CBR)

Q7 (higher priority)

Best Effort (UBR+)

Q6

BackGround (UBR)

Q1

Queue size setting for radio interface


The size of queues from Q1 (lowest priority queue) to Q5 (highest priority queue) can be
configured using the WebEML.
The setting is made at radio interface level and applied to Radio QoS in the following
configurations:

1+0;

1+1 FD, 1+1 HSB/SD (the two protected radio interfaces have the same setting);

L2 Radio Link Aggregation (each radio interface in the LAG has its own setting).

In case the configuration of radio interfaces changes from 1+0 to 1+1, the Radio QoS of
Spare interface takes the queue sizes of the Radio QoS of Main interface. The previous
configuration of queue sizes of the Radio QoS of Spare interface is lost.
In case of the configuration of radio interfaces changes from 1+1 to 1+0, the Radio QoS of
Main interface maintains the previous configuration of queue sizes, while the Spare
interface takes the default queue sizes according to the configured Modem Profile.
The size of the queue is defined in number of bytes of Ethernet traffic, that has to be
buffered by the queue.
The size can be configured in the following range:

344

maximum queue size = 3987220 bytes

User Manual 3DB19901AFAA Edition 01

Functional description

minimum queue size = 2480 bytes

In order to give an estimation of the maximum delay, that an Ethernet frame can experience
when entering the specific queue in case of congestion of radio interface, the WebEML
shows a read-only value, which is the queue size configured by the operator converted in a
time value (msec).
The maximum delay estimation is done according to the following parameters:

Queue size in bytes as configured by the operator;

Ethernet available bandwidth of the Radio interface;

Scheduling algorithm applied to the queue;

Weight in case the scheduling algorithm is DWRR.

Scheduler
Strict Priority (SP) scheduler algorithm is used on Q8, Q7 and Q6 (fixed assignment).
Strict Priority (SP) or Deficit Weighted Round Robin (DWRR) algorithm can be selected
for the other five queues. The selection is done by the WebEML.
By default, the DWRR algorithm is used with the following weights:
Table 2.68 ATM DWRR queue weights
Queue

Weight

Q5 (higher priority)

16

Q4

Q3

Q2

Q1

The weights can be changed using the WebEML.


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.22.2 QoS for TMN packets


User Manual 3DB19901AFAA Edition 01

345

Functional description

The system supports the setting of a DSCP and PCP value for IP packets from the TMN Inband interface. The configuration of the values is not allowed if the TMN in-band interface
is enabled.
The DSCP and PCP values allow a priority to be set for TMN management packets to the
Data Communications Network (DCN). Queue mapping for TMN management packets is
performed outside the 9500 MPR. TMN packets inside the radio network are in a fixed
high-priority queue.
The DSCP value can range from 0 to 63. The default is 34.
The DSCP value is not saved in the backup file.
The PCP value can range from 0 to 7. The default is 7.
The PCP value is saved in the backup file.

2.8.22.3 QoS in the MPT-HC/HC-HQAM/MC/XP/XP-HQAM


The QoS is implemented by MPT-HC/HC-HQAM/MC/XP/XP-HQAM itself (not in the
MPT Access unit).
The set of MPT QoS features is the same of the one specified in QoS configuration with the
exception of the ATM CBR and UBR+ CoS: in MPT-HC/HC-HQAM/MC/XP/XP-HQAM
they are sent to queue #5 and queue #4 respectively (and not to queue #7 and queue #6).

2.8.22.4 QoS in L1 LAG with EASv2


Each L1 LAG on an EASv2 unit can support up to twelve egress queues. Queue 12 has the
highest priority. Frames are assigned to each queue according to the priority encoded in the
802.1P field, DiffServ, Ethertype, or 802.1Q VLAN ID.
Q9 through Q12 are reserved for higher priority traffic that is not managed by the LAG
distributor, such as cross-connected TDM flows. Table 2.69 describes the queues.
Table 2.69 L1 LAG with EASv2 queue weights
Queue

Traffic type

Q12

TDM2TDM

Q11
Q10

346

Future use
SDH2SDH

User Manual 3DB19901AFAA Edition 01

Functional description
Table 2.69 L1 LAG with EASv2 queue weights (Continued)
Queue

Traffic type

Q9

TDM2ETH

Q8

Forwarding class 7

Q7

Forwarding class 6 (TMN, SSM)

Q6

Forwarding class 5 (R-APS)

Q5

Forwarding class 4

Q4

Forwarding class 3

Q3

Forwarding class 2

Q2

Forwarding class 1

Q1

Forwarding class 0

2.8.23 Cross-connections
Figure 2.120 Cross-connection

The cross-connections between slots and between slot and Ethernet user ports are realized
with a Layer-2 Ethernet Switch inside the Core-E unit.
The decision made by the switch to forward the received packet is based on the destination
MAC address.

2.8.23.1 E1 Cross-connections
Each E1 can be cross connected independently.
User Manual 3DB19901AFAA Edition 01

347

Functional description

E1 can be cross connected to any of the following interfaces:

Radio interface

Ethernet interface

Each E1 (board #, port #) must be associated to an unique signal flow ID.

2.8.23.2 STM-1 Cross-connections


Each STM-1 can be cross connected independently.
STM-1 SDH2SDH flows can be cross connected to the following interfaces:

Radio interface

L1 LAG on EASv2 board

Each STM-1 (board #, port #) must be associated to an unique SDH2SDH signal flow ID.

2.8.23.3 Radio-Radio Cross-connections


Ethernet frames, coming from a radio direction, can be cross-connected to another radio
direction.

2.8.23.4 Ethernet Cross-connections


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

2.8.23.5 ATM PW cross-connections


348

User Manual 3DB19901AFAA Edition 01

Functional description

Cross-connection of ATM PW flows involves the following levels of operation:

an ATM PW is composed of two unidirectional flows, so its cross-connection is


internally managed by NE as two unidirectional flow cross-connections

for ATM PW flow with guaranteed bandwidth, an admission control check must be
performed in each flow direction: there shall be enough available bandwidth on both
directions

VLAN-based settings in terms of Ethernet switch and Radio QoS are then performed
(as the same VLAN can be used for ATM PW flows with same CoS and path).

The minimum bandwidth foreseen for an ATM PW flow corresponds to the case of
PCR, SCR or MDCR of 1 cell/s rate, with max 1 cell for frame.

MAC SA assignment for ATM PW frames generated by ASAP peripheral


MAC Source Address of ATM PW frames generated by ASAP peripheral should be
assigned to be equal to:

the internal MAC Address of slot hosting that ASAP peripheral in case of crossconnection towards radio interface

the NE Mac Address in case of cross-connection towards Ethernet interface.

In this release it is accepted to assign always the NE Mac Address as MAC Source Address
of ATM PW frames generated by ASAP peripheral.
Admission control for ATM PW flows towards radio directions
Each time a cross-connection for an ATM PW flow involving, at least, one radio direction,
is required by the management systems, an admission control is performed.
The admission control depends on the remaining bandwidth computed on the basis of
specific Radio Profile and on the previously configured TDM or ATM PW flows.
The bandwidth available for each radio direction is available to ECT/NMS.
Admission control for ATM PW flows towards User Ethernet interface
Each time a cross-connection for ATM PW flow involving, at least, one user Ethernet port,
is required by the management systems, an admission control is to be performed if the
Ethernet port is in manual configuration with speed at 1000 MBit/s and pause disabled.
The admission control depends on the remaining bandwidth computed on the basis of the
configured speed and on the previously configured TDM2ETH or ATM PW flows.
The bandwidth available for each user Ethernet port is available to ECT/NMS.
Admission control for ATM PW flows towards ATM interface

User Manual 3DB19901AFAA Edition 01

349

Functional description

In this release no admission control is performed for an ATM PW flow cross-connection in


the direction from a radio or Ethernet interface towards an ATM interface.
ATM PW flows admission control in AM
When the admission control is enabled, the cross-connection of the ATM PW flows
requiring guaranteed bandwidth towards a radio direction configured to work in Adaptive
Modulation Mode, is allowed only if there is sufficient bandwidth at the lowest modulation.
This means that it is not allowed to cross-connect ATM PW flows, requiring guaranteed
bandwidth, exceeding the bandwidth available with the lowest modulation.
When the admission control is disabled, the cross-connection of the ATM PW flows
requiring guaranteed bandwidth towards a radio direction configured to work in Adaptive
Modulation Mode, is allowed only if there is sufficient bandwidth at the highest
modulation.
This means that it is not allowed to cross-connect ATM PW flows, requiring guaranteed
bandwidth, exceeding the bandwidth available with the highest modulation.
Common Consistency Checks
In any kind of below cross-connection, it is necessary to perform the following common
checks:

the same VLAN ID cannot be shared between a TDM2TDM/TDM2ETH flow and an


ATM PW flow

the same VLAN ID shall be used for the two directions of ATM PW

ATM PW flows into ATM-Radio terminal


This configuration is needed when an ATM PW flow terminated on ASAP board is
transmitted on a radio direction.
ATM PW flows termination on ASAP board assumes a previous layered configuration of
E1, IMA and ATM interface (the latter with the explicit definition of VPI/VCI, ATM
Traffic Descriptors and VPC/VCC termination).
Each ATM PW flow can be cross-connected towards a Radio direction according to the
following rules:

each ATM PW flow can be cross-connected independently

each ATM PW flow can be cross-connected towards one Radio direction.

The cross-connection of an ATM PW flow involves the following main parameters:

350

ATM PW flow n A, its CoS and flow policing enable flag (derived by configured
Ingress ATM Traffic Descriptor)

User Manual 3DB19901AFAA Edition 01

Functional description

slot n B of the ASAP board where the ATM PW n A is terminated

slot n C of the Radio board

VLAN_ID n D used to transport the ATM PW flow.

If the ATM PW flow CoS requires guaranteed bandwidth towards radio interface, its CIR
value and average frame size S in ingress Ethernet Traffic Descriptor (both derived by
configured Ingress ATM Traffic Descriptor) shall be used to perform admission control on
the Radio interface. In this release no admission control towards ASAP board (ATM
interface) is performed.
The above parameters shall be used:

for ASAP board to derive the following ATM PW Header fields:

slot n C of the Radio board is used to derive MAC Destination Address

VLAN_ID n D is used for 802.1q VLAN tag

ATM PW CoS defines static value for 802.1p bits (Expedite vs Best Effort
scheduling)

ATM PW flow n A is mapped to the Outbound and Inbound PW Labels

ATM PW CoS defines EXP bits in PW Header

for Ethernet switch to perform configuration related to:

VLAN_ID n D membership for ASAP and Radio board ports

assignment, for these ports and VLAN n D, the egress queue as defined by
ATM PW CoS

configure static routes for internal MAC Address associated to slot n B/C and
VLAN_ID n D

for Radio board to perform configuration related to:

to identify, by VLAN_ID n D and MAC DA of the internal MAC associated


to slot n C, the ATM PW flow frames to be transmitted over radio physical
layer, in order:

to enable/disable ATM PW flow policing

to perform header compression and ATM PW frames fragmentation

to perform queue assignment according to its CoS

to identify, by VLAN_ID n D, the ATM PW fragments received from radio


physical layer, in order to rebuild ATM PW frames performing header
decompression, with assignment as MAC DA of the internal MAC associated
to slot n B

Checks related to use of same VLAN_ID

User Manual 3DB19901AFAA Edition 01

351

Functional description

Ethernet switch and Radio boards configuration must be done only in case they were not
already done for another ATM PW flow that is using the same VLAN_ID n D (with same
VLAN membership and CoS). In case the VLAN_ID n D has been already configured for
different port membership and/or CoS, the cross-connection will be refused.
Deletion of a ATM PW flow cross-connection previously configured according to SR. ID
8204, implies deletion of Ethernet switch and Radio boards configuration only if no other
ATM PW flow is using that VLAN_ID.
ATM PW flows into Radio-Radio repeater
This configuration is needed when an ATM PW flow received on one radio direction
doesnt terminate but it is transmitted on other radio direction (and viceversa).
Each ATM PW flow can be cross-connect between a pair of Radio directions according to
the following rules:

each ATM PW flow can be cross-connected independently

each ATM PW flow can be cross-connected between one Radio direction pair.

The cross-connection of an ATM PW flow between a Radio direction pair involves the
following parameters:

ATM PW flow n A, its CoS and flow policing enable flags

slot n B for first Radio board

slot n C for second Radio board

VLAN_ID n D used to transport the ATM PW flow

If the ATM PW flow CoS requires guaranteed bandwidth, the CIR value and average frame
size S configured in ATM PW flow Ethernet Traffic Descriptors, shall be used to perform
admission control. The cross-connection can be accepted only if there's available
bandwidth for both directions, otherwise it shall be refused.
The above parameters shall be used:

for Ethernet switch to perform configuration related to:

VLAN_ID n D membership for Radio boards ports

assignment, for these ports and VLAN n D, the egress queue as defined by
ATM PW CoS

configure static routes for internal MAC Address associated to slot n B/C and
VLAN_ID n D

for Radio boards to perform configuration related to:

352

to identify, by VLAN_ID n D and MAC DA of the internal MAC associated


to slot n B/C, the ATM PW flow frames to be transmitted over radio physical
layer, in order:

User Manual 3DB19901AFAA Edition 01

Functional description

to enable/disable ATM PW flow policing

to perform header compression and ATM PW frames fragmentation

to perform queue assignment according to its CoS

to identify, by VLAN_ID n D, the ATM PW fragments received from radio


physical layer, in order to rebuild ATM PW frames performing header
decompression, with assignment as MAC DA of the internal MAC associated
to slot n B/C

Limitation for ODU300 <-> MPT Cross-connection


ATM PW Cross-Connection between a radio direction with ODU300 and another radio
direction with MPT ODU is not possible.
Checks related to use of same VLAN_ID
Ethernet switch and Radio boards configuration must be done only in case they were not
already done for another ATM PW flow that is using the same VLAN_ID n D (with same
VLAN membership and CoS). In case the VLAN_ID n D has been already configured for
different port membership and/or CoS, the cross-connection will be refused.
Deletion of a ATM PW flow cross-connection previously configured, implies deletion of
Ethernet switch and Radio boards configuration only if no other ATM PW flow is using
that VLAN_ID.
Consequence of that is the deletion of an ATM PW cross-connection does not imply the
related traffic is implicitly stopped (if another ATM PW flow is using the associated
VLAN_ID).
ATM PW flows into Radio-ETH terminal
This configuration is needed when an ATM PW flow generated by remote MPR node (with
ASAP board) is transported/terminated by external equipment linked to local MPR node by
an User Ethernet interface.
In this case manual configuration of Ethernet interface at 1000 MBit/s and pause disabled
is mandatory.
Each ATM PW flow can be cross-connect between a radio direction and an Ethernet
interface according to the following rules:

each ATM PW flow can be cross-connected independently

each ATM PW flow can be cross-connected between one radio direction and one
Ethernet interface.

The cross-connection of an ATM PW flow between a radio direction and an Ethernet


interface involves the following parameters:

ATM PW flow n A, its CoS, flow policing enable flag

User Manual 3DB19901AFAA Edition 01

353

Functional description

slot n B for first Radio board

User Ethernet port n C

VLAN_ID n D used to transport the ATM PW flow

If the ATM PW flow CoS requires guaranteed bandwidth, the CIR value and average frame
size S configured in ATM PW flow Ethernet Traffic Descriptors shall be used to perform
admission control. The cross-connection can be accepted only if there's available
bandwidth for both directions, otherwise it shall be refused.
The above parameters shall be used:

for Ethernet switch to perform configuration related to:

VLAN_ID n D membership for Radio boards ports

assignment, for these ports and VLAN n D, the egress queue as defined by
ATM PW CoS

configure static routes for internal MAC Address associated to slot n B/C and
VLAN_ID n D

for Radio board to perform configuration related to:

to identify, by VLAN_ID n D and MAC DA of the MPR NE MAC Address,


the ATM PW flow frames to be transmitted over radio physical layer, in order:

to enable/disable ATM PW flow policing

to perform header compression and ATM PW frames fragmentation

to perform queue assignment according to its CoS

to identify, by VLAN_ID n D, the ATM PW fragments received from radio


physical layer, in order to:

rebuild ATM PW frames performing header decompression

assignment as MAC SA of the MPR NE MAC

assignment as MAC DA of the MAC Address to be used for interworking


that has been configured for the ATM PW

Checks related to use of same VLAN_ID


Ethernet switch and Radio boards configuration must be done only in case they were not
already done for another ATM PW flow that is using the same VLAN_ID n D (with same
VLAN membership, CoS and Peer MAC Address).
In case the VLAN_ID n D has been already configured for different port membership, CoS
and Peer MAC Address, the cross-connection will be refused.
Deletion of a ATM PW flow cross-connection previously configured, implies deletion of
Ethernet switch and Radio boards configuration only if no other ATM PW flow is using
that VLAN_ID.

354

User Manual 3DB19901AFAA Edition 01

Functional description

Consequence of that is the deletion of an ATM PW cross-connection does not imply the
related traffic is implicitly stopped (if another ATM PW flow is using the associated
VLAN_ID).
Limitation in checks related to use of same VLAN ID
In this release, the check related to configure the same Peer MAC Address in case the same
VLAN ID is used by several ATM PW flows is not performed.
ATM PW flows into ATM-Ethernet terminal
This configuration is needed when an ATM PW flow terminated on ASAP board is directly
transported/terminated by external equipment linked to remote MSS node by an User
Ethernet interface.
In this case manual configuration of Ethernet interface at 1000 MBit/s and pause disabled
is mandatory.
ATM PW flows termination on ASAP board assumes a previous layered configuration of
E1, IMA and ATM interface (the latter with the explicit definition of VPI/VCI, ATM
Traffic Descriptors and VPC/VCC termination).
Each ATM PW flow can be cross-connected towards an Ethernet interface according to the
following rules:

each ATM PW flow can be cross-connected independently

each ATM PW flow can be cross-connected towards one Ethernet port.

The cross-connection of an ATM PW flow involves the following parameters:

ATM PW flow n A and its CoS (derived by configured Ingress ATM Traffic
Descriptor)

slot n B of the ASAP board where the ATM PW n A is terminated

User Ethernet port n C

VLAN_ID n D used to transport the ATM PW flow.

If the ATM PW flow CoS requires guaranteed bandwidth, its CIR value and average frame
size S in ingress Ethernet Traffic Descriptor (both derived by configured Ingress ATM
Traffic Descriptor) shall be used to perform admission control on the Ethernet interface. In
this release no admission control towards ATM interface (ASAP board) is performed.
The above parameters shall be used:

for ASAP board to derive the following ATM PW Header fields:

MAC Destination Address is the provisioned Peer MAC Address

VLAN_ID n D is used for 802.1q VLAN tag

User Manual 3DB19901AFAA Edition 01

355

Functional description

ATM PW CoS defines static value for 802.1p bits (Expedite vs Best Effort
scheduling)

ATM PW flow n A is mapped to the Outbound and Inbound PW Labels

ATM PW CoS defines EXP bits in PW Header

for Ethernet switch to perform configuration related to:

VLAN_ID n D membership for ASAP board and User Ethernet ports

assignment, for these ports and VLAN n D, the egress queue as defined by
ATM PW CoS

configure static routes for MPR NE MAC Address, Peer MAC Address and
VLAN_ID n D

Checks related to use of same VLAN_ID


Ethernet switch configuration must be done only in case they were not already done for
another ATM PW flow that is using the same VLAN_ID n D (with same VLAN
membership, CoS and Peer MAC Address). In case the VLAN_ID n D has been already
configured for different port membership, CoS, or Peer MAC Address the cross-connection
will be refused.
Deletion of a ATM PW flow cross-connection previously configured, implies deletion of
Ethernet switch configuration only if no other ATM PW flow is using that VLAN_ID.

2.8.23.5.1 ATM Local Switch feature


Termination of ATM traffic into the same MPR Node ("ATM Switch-like") is supported
with the following characteristics:

356

1.

ATM traffic switching requires in any case ATM PW termination;

2.

the only limitation in terms of involved ATM i/f (IMA Groups), is switching is not
possible between ATM i/fs hosted by same ASAP peripheral: VPs/VCs to be
switched must always belong to two ATM i/fs hosted by different ASAP peripherals;
for example it is possible to aggregate the VP/VC belonging to 2 or more different
ATM i/fs, hosted by same ASAP peripheral, towards a single ATM i/f only if the
latter is hosted by a different ASAP peripheral;

3.

no direct configuration of cross-connections for the ATM PW flow pair is supported,


instead it will be necessary to configure, for each ATM PW flow belonging to the
ATM PW flow pair to be cross-connected, an ATMEthernet cross-connection
towards a given Ethernet port (it can be the same); the Ethernet port(s) involved in
these cross-connections can be used for other traffic, with the only impact due to
bandwidth reservation, if applicable;

4.

a proper MAC Destination Address has to be configured for each ATM PW: it has to
be different from NE MAC, but since the ATM PW frames are not sent outside the
NE, in principle any other valid MAC value can be used;
User Manual 3DB19901AFAA Edition 01

Functional description

5.

to allow ATM PW flow frame forwarding, without external cable, and swap between
VLAN IDs, an Ethernet Switch configuration file has to be used.

2.8.23.6 Port Segregation


This feature is based on the port based VLAN feature supported by the Ethernet switch and
allows the following behavior: all traffic received/transmitted from one user Ethernet port
or radio direction can not be exchanged with specific user Ethernet ports/radio directions.
The default configuration foresees:

Every user Ethernet port is cross-connected to all Radio directions (bidirectional


connection)

All the Radio directions are cross-connected between them (bidirectional connection)

All the user Ethernet ports are cross-connected between them (bidirectional
connection)

By ECT/NMS it is possible to change this default configuration. When TDM flow crossconnections or ATM PW flow cross-connections are defined and involve TDM or ATM
ports, port segregation involving these ports are implicitly prohibited.

2.8.23.6.1 Port Segregation and Frame Duplication


The Operator must be aware that application of port segregation between an User Port and
radio ports in 1+0 configuration (segregated among them) towards the same NE can lead to
duplication of broadcast, multicast of flooding traffic.

User Manual 3DB19901AFAA Edition 01

357

Functional description

2.8.23.6.2 TDM ports


Port Segregation is not supported for TDM ports (E1/DS1) by ECT/NMS. At system level
TDM ports are segregated among them and not segregated from Radio directions involved
in TDM flows cross-connections.

2.8.23.6.3 ATM ports


Port Segregation is not supported for ATM ports by ECT/NMS. At system level ATM ports
are segregated among them and not segregated from Radio directions involved in ATM PW
flows cross-connections.

358

User Manual 3DB19901AFAA Edition 01

Functional description
2.8.23.6.4 General rules
Port Segregation between two ports can be applied only if they are not involved in TDM
flows cross-connections, ATM PW flows cross-connections or Service Channels crossconnections.
For example, when there is a TDM2ETH flow or ATM PW flow cross-connected between
one User Ethernet port and one Radio direction, it is not possible to apply Port Segregation.
A TDM flows cross-connection or an ATM PW flows cross-connection can be applied
between User Ethernet and Radio ports only if the involved ports are not segregated. Before
apply the cross-connection the operator has to remove the Port Segregation.
A Service Channels cross-connection between two Radio directions can be applied only if
the involved ports are not segregated.
There are several situations where port segregation and EFM OAM Remote Loopback are
not compatible:

When a radio or L1 LAG interface is segregated with respect to other interfaces and
EFM OAM Loopback is applied on an User Ethernet interface of the same board,
EFM OAM Loopback cannot be applied to the interface.

EPS protection for radio interfaces cannot be provisioned or deprovisioned when port
segregation and EFM OAM loopback are both present on either radio interface
involved in the protection.

L1 LAG configuration cannot be changed from intra plug-in to cross plug-in or vice
versa when port segregation and EFM OAM loopback are both present on the LAG
interface.

2.8.23.6.5 MPT plug in ports


For MPT Access, EAS and EASv2 ports, port segregation can be applied by operator at two
different points:

between peripheral ports connected to MPTs: to segregate connected MPTs

between them between the peripheral port connected to MSS backplane and the other
backplane ports: to segregate all connected MPTs towards User Ports or other radio
directions.

In case only one MPT is connected to a port, the port segregation behaviour is the same as
with ODU300 radio direction.
Assuming 2 MPTs in 1+0 configuration are connected to same MPT Access peripheral,
since that is the only configuration supported within this release with more than one MPT
on same MPT Access peripheral, three scenarios have to be considered:

User Manual 3DB19901AFAA Edition 01

359

Functional description

1.

no port segregation is applied by operator between MPT Access peripheral ports and
to MPT Access peripheral port towards backplane: in this case, all the involved ports
can exchange the data among them (case A);

2.

port segregation is applied by operator between MPT Access plug-in ports, while no
port segregation is applied by operator to MPT Access peripheral port towards
backplane: in this case, the two MPTs cannot exchange data (case B); in this case,
frame duplication for broadcast, multicast and flooding traffic will surely occur in
case the two radio directions are towards the same NE;

3.

no port segregation is applied by operator between MPT Access plug-in ports, while
operator applies segregation to MPT Access peripheral port towards backplane. This
case represents an MPT Access peripheral isolated from MSS backplane, in such
case, the two MPTs can only exchange data between them (case C).
A fourth scenario for application of port segregation is possible, but in this release is
not applicable:

4.

360

port segregation is applied by operator between MPT Access peripheral ports and
MPT Access peripheral port towards backplane, no traffic can be exchanged between
MPTs and with MSS with the current number of supported MPT Access peripheral
ports. No check has to be implemented to forbid this application of port segregation
since it can be it applied in future releases where use of all MPT Access peripheral
ports is supported (case D).

User Manual 3DB19901AFAA Edition 01

Functional description

2.8.23.6.6 MPTs number for each MPT plug in


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

User Manual 3DB19901AFAA Edition 01

361

Functional description

2.8.23.6.7 ODU300
In case the Core-E user port is segregated from ODU300 radio: consequently, the ODU300
is segregated from the Core-E user port and vice versa.
In case of protected radio direction, the spare radio direction must have the same port
segregation configuration.
Any previous port segregation configuration for spare radio direction must be deleted by
operator.
362

User Manual 3DB19901AFAA Edition 01

Functional description
2.8.23.6.8 ODU300 and MPTACC
If port segregation is applied by operator to an ODU300 radio port and to MPT Access
plug-in port towards backplane, all the MPT Access ports are segregated from the ODU300
radio port and vice versa.

2.8.23.6.9 MPTs protected on different plug-ins


When two MPTs are provisioned for 1+1 protected configuration on two different
peripherals, the plug-in ports towards the backplane will not be implicitly segregated from
each other.
Otherwise, when it will be supported in future release the possibility to connect another
MPT to the same MPT Access peripheral(s), it would not possible to have it in repeater
configuration with the protected MPT pair.
Operator is allowed to apply port segregation to MPT Access peripherals hosting an MPT
pair in 1+1, but since connection to other MPT on same plug-in is not supported in this
release, only the segregation of the port towards the backplane is effective.
The spare radio direction must have the same port segregation configuration (for the plugin port towards the backplane).
Any previous port segregation configuration for spare radio direction must be deleted by
operator.

2.8.24 Software package rollback


The system supports software package rollback to the previous committed software
version. Software package rollback is supported when the software package and the MSS
database for the previous committed software version are both still present on the Core-E
flash card.
All configuration changes applied to the NE after the software version upgrade will be lost
during the software package rollback operation.
Software package rollback operation WILL impact traffic including a possible long out-of
service period. For this reason software package rollback should be considered as a critical
operation to be performed as a last resort only after all other alternatives have been
explored.
Alcatel-Lucent recommends backing up the system, including the license key, before
performing a software upgrade or rollback. If a provisioning mismatch alarm is raised after
the rollback is completed, apply the software license from the earlier release.
User Manual 3DB19901AFAA Edition 01

363

Functional description

Software package rollback functionality was added in R4.0.0 and is available for software
upgrades from R4.0.0 and greater.
Software package rollback is NOT supported between the following software releases:

release versions that differ by ICS version only (i.e., Rxx.xx.xx ICS01 and Rxx.xx.xx
ICS02)

release versions that differ by the last digits of the release version number((i.e.,
Rxx.xx.00 and Rxx.xx.01)

For these cases, a revert to the previous release version and a database restore is required.
Contact the next level of technical support for assistance.
Table 2.70 provides a list of supported software package rollbacks:
Table 2.70 Releases supporting software package rollback
Initial software release version
Current Status: Stand by

Upgrade software release


version Current Status:
Committed

Software package
rollback support

R3.2.0, R3.3.0, or R3.4.0

R4.0.0

No

R3.4.0

R4.1.0

No

R4.0.0 or greater

R4.1.0 or greater

Yes

2.8.25 Synchronization for PDH/SDH/DATA


2.8.25.1 Synchronization overview
PDH/SDH data flow is fragmented and the fragments are transmitted over a Packet
Switched Network (PSN);
The received fragments need to be reassembled in the original PDH/SDH data flow at the
original bit rate
Two main methods can be used to recover at the Rx site, the original bit rate:

364

Differential clock recovery with or without the Node Timing: recalculation of the
original clock based of the Delta respect to a reference clock that is available at both
Tx and Rx site (Differential: used in case of clock distribution on the whole network.
Its more reliable than Adaptive; also used in TDM2TDM/SDH2SDH traffic (MPR
to MPR)). This method can be selected for each E1/STM-1 stream.

User Manual 3DB19901AFAA Edition 01

Functional description

Adaptive clock recovery with or without the Node Timing: based on the average
rate at which the packets (fragments) arrive at RX site (Adaptive: simpler network,
but performances depends on the PDV (Packet Delay Variation) in the Network.
Always used when the reference clock isnt distributed on the whole network). This
method can be selected for each E1 stream.

The available clock recovery techniques with TDM2TDM and SDH2SDH profiles are:

DCR: differential clock recovery

with/without Node timing

The available clock recovery techniques with TDM2ETH profile are:

ACR: adaptive clock recovery (if a common reference clock is not available)

DCR: differential clock recovery

with/without Node timing.

Note: In meshed networks (rings) do not close the synchronisation configuration.

Note: If the NODE TIMING is enabled, the WebEML still propose the possible selection
between ACR and DCR: in this specific case, the meaning of this option is not related to
the clock recovery algorithms, but rather to the MRF8 frame format.

2.8.25.1.1 Differential clock recovery

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.

User Manual 3DB19901AFAA Edition 01

365

Functional description
2.8.25.1.2 Adaptive clock recovery

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.25.1.3 Node Timing


The Node Timing is the timing from the network clock as defined in G.8261. The enabling
of the Node Timing is applied to all E1s of the PDH unit or to each STM-1.
This feature (called either network clock re-timing or node timing or, according to G.
8261 wording, network-synchronous operation for service clock) introduces an
additional possibility to recover the clock.
Node timing is a way to recover the clock quite popular in the industry of service routers
and site aggregator boxes. This feature inside the 9500 MPR platform is adding
interworking capabilities with third parties service routers and circuit emulations gateway.
In node-timing working mode, all the E1s are re-sampled with the network element clock.
This means that, as also reported in G8261, this method does not preserve the service timing
(E1 clock).
Recovered E1 clock is according to G. 823 synchronization masks.

2.8.25.2 Synchronization Sources and protection policy

366

User Manual 3DB19901AFAA Edition 01

Functional description

In order to get any node in a meshed network or ring topology network always locked for
each node the synchronization sources and the automatic selection process are defined, as
described in the following points.
The selection process works always in QL-enabled mode, the selected synchronization
clock source is used to lock the NEC. The QL of the selected synchronization clock source
determines the QL of the NEC, unless the NEC is in Holdover mode.
The selection process has two nominated synchronization clock source inputs:

Primary clock source input;

Secondary clock source input.

For such sources the following selection criteria are defined:

Clock Source Fail when the source is not available;

Clock Source Degrade when the frequency of the source is away from its nominal
value with the following rules: the degrade alarm will never be asserted if the actual
frequency is within 10 ppm of its nominal value; the degrade alarm will always be
asserted if the actual frequency is not within 50 ppm of its nominal value;

Clock Source Quality Level (QL) according to ITU-T G.781;

Clock Source Quality Level Priority

According to Table 8 of ITU-T G.781 the Clock Source Quality Level is identified by the
following SSM Codes:

0010 - QL-PRC for timing quality generated by a primary reference clock as defined
in ITU-T G.811;

0100 - QL-SSU-A for timing quality generated by a type I or V slave clock as defined
in ITU-T G.812;

1000 - QL-SSU-B for timing quality generated by a type VI slave clock as defined in
ITU-T G.812;

1011 - QL-SEC/QL-EEC1 for timing quality generated by a SEC or EEC as defined


in ITU-T G.813/ITU-T G.8262;

1111 - QL-DNU (Do Not Use).

Any other SSM Code values different from the ones listed above must be considered as an
Invalid Quality Level (QL-INV).
The QL of the NEC is advertised over radio interfaces and Synchronous Ethernet
interfaces.

User Manual 3DB19901AFAA Edition 01

367

Functional description
2.8.25.2.1 Quality Level Priority
A QL Priority parameter is defined for each node and assigned to synchronization clock
sources and to the NEC.
The QL Priority values are identified by the following codes:

0x00 - Undefined

0x01 - Master1

0x10 - Slave1

The QL Priority of the NEC is advertised, together with the QL, over radio interfaces.
The equipment shall be ready to advertise the QL Priority of the NEC over Synchronous
Ethernet interfaces too.
The QL Priority is a proprietary parameter (not foreseen in G.781) introduced with the aim
to deal with a ring or meshed scenario where, due to a lack of external synchronization
sources and failure on the synchronization distribution path on the MPR wireless network,
the synchronization distribution network is partitioned in more than one isle each of them
locked to a different oscillator in Holdover or Free-Run mode.

2.8.25.2.2 Hold-off and Wait-To-Restore


In order to proper manage the QL-FAILED (Clock Source Fail or Clock Source Degrade)
the automatic selection process must take into account the Hold-Off time and Wait-ToRestore time defined in ITU-T G.781:

368

The Hold-Off time ensures that short activation of signal fail are not passed to the
selection process. The QL value of QL-FAILED is passed to the selection process
after the Hold-off time. In the meantime, the previous QL value is passed to the
selection process. The Hold-Off time is the same for each input of the selection
process and it is fixed to 500 ms.

The Wait-To-Restore time ensures that a previous failed synchronization source is


only again considered as available by the selection process if it is fault free for a
certain time. When a Signal Fail or Signal Degrade defects are cleared, the Wait-ToRestore time is applied before the new QL value is passed to the selection process. In
the meantime, the quality level QL-FAILED is passed to the selection process. The
Wait-To-Restore time is the same for each input of the selection process and it is
configurable in the range of 0 to 12 minutes in steps of 10 seconds. The default value

User Manual 3DB19901AFAA Edition 01

Functional description

is 5 minutes. When changed before its expiration, the WTR time restart from the new
value without take into account the previous remaining time to expiration. The WTR
time is also applied when a LOS of ESMC defect is cleared on a synchronization
clock source, also in that case the quality level QL-FAILED is passed to the selection
process until the WTR time expires.

2.8.25.3 Synchronization Sources assignment


The physical interfaces to be assigned to Primary and Secondary synchronization sources
can be chosen among the following:
1.

Free Run Local Oscillator. This source will never be affected by any alarm (no Fail,
no Degrade). Quality Level value is fixed to QL-SEC/EEC1 (G.812/G8262), the
value of QL Priority is Master1 if the NEC is configured as Master and Slave1 if the
NEC is configured as Slave.

2.

Any E1 or T1 available at input traffic interfaces (the specific E1/T1 port has to be
chosen). For these sources the Fail alarm has to be detected by CRU when LOS, AIS
or LOF (in case of E1s framed) will happen. Default value for Quality Level is QLSSU-A (G.812), the value of QL Priority is Master1 if the NEC is configured as
Master and Slave1 if the NEC is configured as Slave.

3.

A specific synchronization signal available from the dedicated Sync-In port, which
can be configured according the following options:
a.

2.048 MHz, electrical levels according to G.703, clause 13;

b.

5 MHz, + 6 dBm into 50 ohm, sine-wave;

c.

10 MHz, + 6 dBm into 50 ohm, sine-wave;

d.

1.024 MHz, electrical levels according to G.703, clause 13 with the following
exceptions:

timing properly scaled from 2.048 MHz to 1.024 MHz.

For this source the Fail alarm is detected by CRU when LOS will happen. Default
value for Quality Level is QL-SSU-A (G.812), the value of QL Priority is Master1 if
the NEC is configured as Master and Slave1 if the NEC is configured as Slave.
4.

The Symbol Rate of the RX signal of any available Radio (the specific Radio Port has
to be chosen). For these sources the Fail alarm has to be detected by CRU when a
DEM-Fail or a Loss of Radio Frame will happen. When the SSM support is enabled
the QL and QL Priority are acquired from ESMC PDUs received on the specific radio
interface. When the SSM support is disabled the default value for Quality Level is
QL-SSU-A (G.812), the value of QL Priority is Master1 if the NEC is configured as
Master and Slave1 if the NEC is configured as Slave.

User Manual 3DB19901AFAA Edition 01

369

Functional description

5.

Any Synchronous Ethernet clock source available at enabled User Ethernet traffic
interfaces (both electrical and optical) configured in synchronous operation mode
(the specific User Ethernet port has to be chosen).
An optical User Ethernet interface can be configured in Synchronous operation mode
either when it is working in manual mode or when it is working in auto-negotiation.
From ITU-T G.8261 point of view, the MSS is a Synchronous Ethernet equipment
equipped with a system clock (NEC) following the ITU-T G.8262 recommendation.
A User Ethernet interface configured in synchronous operation mode can work only
at 1000 Mbit/s. In the particular case of electrical User Ethernet interfaces, these
interfaces perform link auto negotiation to determine the master/slave role for clocks
delivery over the link. The clock slave role must be configured as part of auto
negotiation parameters in order to use the interface as Synchronous Ethernet clock
source input, either as Primary or Secondary. This check is performed by WebEML/
NMS but not by EC. The clock master role must be configured as part of auto
negotiation parameters in order to use the interface as Synchronous Ethernet clock
source output to distribute NEC to other equipment. For Synchronous Ethernet clock
sources from electrical User Ethernet ports the Fail alarm will be raised when Loss of
Synch (i.e. Ethernet Link Down) will happen. For Synchronous Ethernet clock
sources from optical User Ethernet ports the Fail alarm will be raised when Loss of
Optical signal will happen.

6.

Any STM1 available at SDH input traffic interfaces (the specific STM1 port must be
selected). For these sources the Fail alarm will be raised when LOS, LOF, TIM, MSAIS, or High BER happen. Default value for Quality Level is QL-SSU-A (G.812), the
value of QL Priority is Master1 if the NEC is configured as Master and Slave1 if the
NEC is configured as Slave.

7.

Any Layer 1 Radio Link Aggregation Group (the specific LAG interface has to be
chosen) with Administrative State enabled. The NE selects one of the Radio Links,
belonging to the LAG, according to current alarm status. Additionally, in case of
synchronization failure of the current reference, the NE performs a selection switch
on another interface belonging the same group (passing through the Holdover). A
LAG Synchronization Reference is no more valid if none of the Radio interfaces of
the Group represents a valid Synchronization source.
When the SSM support is enabled the QL and QL Priority are acquired from ESMC
PDUs received on the Radio LAG interface.
When the SSM support is disabled the default value for Quality Level is QL-SSU-A
(G.812), the value of QL Priority is Master1 if the NEC is configured as Master and
Slave1, if the NEC is configured as Slave.

8.

None of the above, this means that no physical synchronization interface is assigned
to the synchronization clock source input. In case of failure of the other clock source
input the CRU enters the Holdover state.

2.8.25.4 Synchronization sources assignment rules


370

User Manual 3DB19901AFAA Edition 01

Functional description

Some rules have to be followed while assigning the Primary and Secondary clock sources:
The NEC has to be defined (configured) as Master or Slave.

If a specific interface is chosen as Primary, it cannot be selected as Secondary too.

If an E1/T1 is chosen to be Primary source, another E1/T1 coming from the same
peripheral cannot be selected as Secondary source and vice-versa.

If an MPT radio interface is chosen to be Primary source, another MPT radio interface
connected to the same MPT Access peripheral cannot be selected as Secondary
source and vice-versa.

If an STM1 is chosen to be Primary source, another STM1 coming from the same
peripheral cannot be selected as Secondary source and vice-versa.

An MPT can be chosen as a Primary source, and another MPT, connected to the same
EAS/EASv2 unit, can be selected as a Secondary source and vice-versa.

The default NEC mode is Master.

2.8.25.5 Allowed synchronization sources assignment


Only one Master is allowed in the network.
If Master:

The Restoration Mode must be chosen between Revertive and Non-Revertive;

The Primary clock source input must be chosen among 1), 2), 3), 5) or 6).

If the selected Master Primary clock source input is 1):

the Master Secondary clock source input doesn't need to be selected because the
Primary is never supposed to fail.

If the selected Master Primary clock source input is 2), 3), 5) or 6):

the Master Secondary clock source input must be selected among 1), 2), 3), 5), 6) or
8).

If Slave:

The Restoration Mode is fixed to Revertive.

The Primary clock source input must be chosen among 3), 4), 5) or 7). Slave Primary
clock source input is allowed to be 3) or 5) for full indoor configuration and for Piling
configuration.

User Manual 3DB19901AFAA Edition 01

371

Functional description

The Secondary clock source input must be chosen among 1), 2), 3), 4), 5), 6), 7) or 8).

The default primary source is the free Run Local Oscillator.


The default restoration mode is revertive.
Note: Any link that has been assigned as a timing reference at both ends (Primary source
on one side and Secondary source on the other side) must have SSM support enabled on
both synchronization sources at either side of the link.

When SSM is enabled on the secondary reference, ensure that the QL and QLP will not
exceed the normal QL and QLP of the primary reference.
In case of Ring configuration having an optical interface and a radio interface as Ring ports
and having both selected as synchronization references with SSM enabled, the QLP of
radio interface takes precedence.
Provided that QLs received by SSM over optical interface and radio interface are the same,
the radio interface is selected as synchronization source to lock the NEC regardless of the
Primary/Secondary reference configuration.

2.8.25.5.1 QL and QL Priority configuration


In the current release the QL of synchronization interfaces is not configurable by the
operator and, when applicable, takes the default values.
The QL Priority of the node is not configurable by the operator.

2.8.25.5.2 Synchronization Source with EAS/EASv2 unit


The EAS units perform the clock recovery for each connected MPT. The MPT can be
selected as a Primary or Secondary synchronization Source.

2.8.25.5.3 Synchronization Source with MPT


In order to use the symbol rate of the Rx signal of an MPT as selectable synchronization
source for the NEC, the following is needed:

372

if an Optical Ethernet connection is used, then the optical Ethernet port of MPT must
be locked, at transmission, to symbol rate of the Rx signal;

User Manual 3DB19901AFAA Edition 01

Functional description

if an Electrical Ethernet connection is used, it shall be Synch-E capable, meaning that


a common clock at physical layer level, not locked to the NEC, is available between
MSS and MPT for a differential clock recovery method based on custom time-stamp
protocol (referred to Symbol Rate of the air Rx Signal).

2.8.25.5.4 Synchronization Source with MPT PFoE Access peripheral


MPT Access peripheral performs the clock recovery for each connected MPT, one of them
can be selected to be used as Primary synchronization Source.

2.8.25.5.5 Protected radio configuration with one MPT PFoE Access peripheral
When MPTs in protected configuration are connected to one MPT Access peripheral only,
the MPT Access peripheral selects, from the MPT in EPS active state, the clock signal to
be used as synchronization Source.

2.8.25.5.6 Protected radio configuration with 2 MPT PFoE Access peripheral


When MPTs in protected configuration are connected to two MPT Access peripherals, both
MPT Access peripheral, for the radio direction configured as synchronization Source,
forwards its own recovered clock signal.
This clock will be then selected according to the correspondent EPS state for MPT and
MPT Access peripheral.

2.8.26 Synchronization for E1 ports with ASAP unit


The synchronization of each E1 ATM port in the ASAP unit can be configured (by the
WebEML) in two ways:

Loop-timed: the transmit clock is derived from the E1 clock source received

Node-timed: the transmit clock is the NE clock

The E1 ports belonging to the same IMA group must have the same configuration.

User Manual 3DB19901AFAA Edition 01

373

Functional description

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

Note: With this second solution 9400 AWY must be used to transport Ethernet traffic only.

Figure 2.121 Synchronization distribution from MPR to AWY

374

User Manual 3DB19901AFAA Edition 01

Functional description

Note: 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.28 Synchronization connection in Stacking configuration


with Core protection
In case of Stacking configuration with Core protection the three MSS must be synchronized
as shown in Synchronization connection in Stacking configuration with Core protection

User Manual 3DB19901AFAA Edition 01

375

Functional description
Figure 2.122 Synchronization connection in Stacking configuration with Core protection

376

User Manual 3DB19901AFAA Edition 01

3 NE Management by software
application

3.1 WebEML start


This chapter explains all the screens of the WebEML, which is started by a double click
on the WebEML icon of the PC desktop.
The PC must be connected to a TMN port or the Local Management Port of the Core-E unit
in the MSS.
See Local copy of the WebEML and TCO Suite Software to PC to copy the WebEML from
the software package and to connect the PC to the NE.
Note: Graphics in this chapter may not match the current release.

1.

Start the WebEML by double clicking on the relevant icon on the PC desktop (refer
to Figure 3.1). The application may also be started by double-clicking the NEtO.exe
file located in the NETO directory where the WebEML application was saved
(default: C:\Alcatel-Lucent).
Figure 3.1 WebEML desktop icon

2.

NEtO Servers Manager (refer to Figure 3.2) and NEtO (refer to Figure 3.3) open. In
NEtO, insert the IP address of the NE (default: 10.0.1.2) and click OK. The Login
window opens.
For more details on NEtO refer to Network Element Overview.
For more details on NEtO Servers Manager refer to NEtO Servers Manager
Overview.

User Manual 3DB19901AFAA Edition 01

377

WebEML start

Note: In case of connection to Local Management Port and DHCP Server functionality
enabled on NE, to access the NE the PC must be configured to Get automatically an IP
address, because NE works as a DHCP Server with default IP address 10.0.1.2.
Figure 3.2 NEtO Servers Manager window

Figure 3.3 NEtO window

378

3.

Enter your Login Name must not be more than 20 characters.

4.

Enter 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).

5.

Click on the Login button.

6.

When the NE is supervised, the Show button becomes available, see Figure 3.4.

User Manual 3DB19901AFAA Edition 01

WebEML start
Figure 3.4 NEtO supervision established with NE

7.

Click on the Show button. An acknowledgment window opens.


Figure 3.5 Acknowledgment of Authorization window

8.

Click on the Accept button to proceed.

9.

The Main view opens (see WebEML Main View).

Note: There are four user profiles defined.


Administrator (full access also for NMS local system security parameters).
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.
Operator (person in charge to operate at the network level, not at the radio side).
Viewer (view screens only).

At the NE installation time, two default user accounts are created on the NE
independently from the SNMP operating mode.

Profile: administrator

Username: initial

Password: adminadmin

Profile: craftPerson

Username: Craftperson

User Manual 3DB19901AFAA Edition 01

379

WebEML Main View

Password: craftcraft
To change the Default UserName and Password see Profile Management Menu.

3.2 WebEML Main View


The Main View Area manages all domains from which the operator can start. It is organized
with tab panels, e.g. many windows placed one upon another. Each window is selectable
(placing it on top of the others) with a tab shown on the top.
Three Main views are shown according to the MSS version:

MSS-8 (refer to Figure 3.6)

MSS-4 (refer to Figure 3.7)

MSS-1 (refer to Figure 3.8)

MSS-O (refer to Figure 3.9)

Note: The figures in this chapter use the MSS-8 shelf; however, the operation is similar
for all MSS shelves.

380

User Manual 3DB19901AFAA Edition 01

WebEML Main View


Figure 3.6 MSS-8 Main view
Main
Tool
Bar
Severity
Alarm
Panel
Tabpanel
Management
State Control
Panel

Resource
Tree
Area

Resource
List
Area

Resource
Detail
Area

23682

User Manual 3DB19901AFAA Edition 01

381

WebEML Main View


Figure 3.7 MSS-4 Main view
Main
Tool
Bar
Severity
Alarm
Panel
Tabpanel
Management
State Control
Panel

Resource
Tree
Area

Resource
List
Area

Resource
Detail
Area

23714

382

User Manual 3DB19901AFAA Edition 01

WebEML Main View


Figure 3.8 MSS-1 Main view
Main
Tool
Bar
Severity
Alarm
Panel
Tabpanel
Management
State Control
Panel

Resource
Tree
Area

Resource
List
Area

Resource
Detail
Area

23157

User Manual 3DB19901AFAA Edition 01

383

WebEML Main View


Figure 3.9 MSS-O Main view
Main
Tool
Bar
Severity
Alarm
Panel
Tabpanel
Management
State Control
Panel

Resource
Tree
Area

Resource
List
Area

Resource
Detail
Area

24399

3.2.1 Tab-panels
Each tab-panel represents a set of functions. The following tab-panels are present:

Equipment (to manage the equipment configuration)

Schemes (to manage the protection schemes in 1+1 configuration)

Synchronization (to manage the synchronization)

Connections (to manage the cross-connections)

The following figure shows the Main view organization.


Each tab-panel consists of three areas:

384

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.
User Manual 3DB19901AFAA Edition 01

WebEML Main View

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 3.6 is the entry point of the application and provides basic diagnostic and
configuration functions. The following main views are available according to the units
present:

Equipment view, for Equipment configuration;

Radio view, for Radio domain (double click on a Radio unit);

PDH view, for PDH domain (double click on a PDH unit);

SDH view, for SDH domain (double click on an SDH unit);

EAS view, for EAS domain (double click on a P8ETH or EASv2 unit);

ATM view, for ATM domain (double click on an ASAP unit);

AUX view, for Auxiliary channel domain (double click on the AUX peripheral unit);

Core-E view, for Core-E and Ethernet domain (double click on a Core-E unit).

CORE view, for MSS/CORE and Ethernet domain (double click on an MSS-1 or
MSS-O).

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 window 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 colored 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 (Figure 3.10)
or a switch symbol (Figure 3.11).
Figure 3.10 Check mark

Figure 3.11 Switch symbol

Figure 3.10 means the slot is active

Figure 3.11 means the slot is in stand-by mode.

As shown in Figure 3.6, an X-shaped icon (Figure 3.12) will be added on the left to
slots when some cross connections are related to it.

User Manual 3DB19901AFAA Edition 01

385

WebEML Main View


Figure 3.12 Cross connections

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;


Figure 3.13 Left arrow to previous screen icon

Second button: not operative;


Figure 3.14 Second button

Right arrow to next screen;


Figure 3.15 Right arrow to next screen icon

Block Diagram View (refer to Summary Block Diagram View);


Figure 3.16 Block Diagram View icon

NE Inventory (refer to NE Inventory);


Figure 3.17 NE Inventory icon

386

Cross-Connections (refer to Cross connections Menu);

User Manual 3DB19901AFAA Edition 01

WebEML Main View


Figure 3.18 Cross-Connections icon

Segregated ports (refer to Segregated port view);


Figure 3.19 Segregated ports icon

Ethernet Ring (refer to Ethernet Ring Configuration View);


Figure 3.20 Ethernet Ring icon

LAG Configuration (refer to LAG Configuration);


Figure 3.21 LAG Configuration icon

QoS Configuration (refer to QoS Configuration);


Figure 3.22 QoS Configuration icon

ETH OAM Configuration (refer to EFM OAM Configuration);


Figure 3.23 ETH OAM Configuration icon

AUX Cross Connections (refer to AUX Cross Connections);


Figure 3.24 AUX Cross Connections icon

User Manual 3DB19901AFAA Edition 01

387

WebEML Main View

XPIC Configuration (refer to XPIC configuration);


Figure 3.25 XPIC Configuration icon

VLAN management (refer to VLAN management).


Figure 3.26 VLAN management icon

WT Performance Monitoring Suite (refer to WT Performance Monitoring Suite).


Figure 3.27 WT Performance Monitoring Suite icon

3.2.3 Severity Alarm Area


The WebEML provides an alarm functionality that informs the operator on the severity of
the different alarms in the NE as well as on the number of current alarms. There are five
different alarm severity levels. In the WebEML these different levels are associated with
colors.

388

Red: Critical alarm (CRI).

Orange: Major alarm (MAJ).

Yellow: Minor alarm (MIN).

Cyan: Warning alarm (WNG).

Blue: Indeterminate (IND).

User Manual 3DB19901AFAA Edition 01

WebEML Main View

Note: The meaning of the icons in the Severity alarm synthesis is:
1.CRI - Critical alarm
Synthesis of alarms relevant to the reachability of the NE (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 intervention can be deferred.
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 occurring.
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 indicates 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.

User Manual 3DB19901AFAA Edition 01

389

WebEML Main View

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.

LAC icon: Local Access Control state: indicates whether the NE is managed by a
WebEML or by the OS.

2.

COM icon: Operational state: indicates whether or not the communication with the
NE is established.

3.

SUP icon: Supervision state: indicates whether or not the NE is under supervision.

4.

OS icon: indicates whether or not the OS is connected.

5.

NTP icon: indicates whether or not the NTP Server is reachable.

6.

AC icon: abnormal condition state: indicates whether some abnormal conditions have
been recognized. The operator can visualize the Abnormal condition with the
DiagnosisAbnormal condition list menu.

Note: 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.

LAC - Local Access Control State

Figure 3.28 indicates that the WebEML has the OS permission to manage the
NE (granted).
Figure 3.28 WebEML has the OS permission to manage the NE icon

Figure 3.29 indicates that the WebEML does not have the OS permission to
manage the NE (denied).

Figure 3.29 WebEML does not have the OS permission to manage the NE icon

2.

COM NE reachable/unreachable

Figure 3.30 identifies the Enable operational state of the connection between
NE and WebEML.

Figure 3.30 Enable operational state of the connection between NE and


WebEML icon

390

User Manual 3DB19901AFAA Edition 01

WebEML Main View

Figure 3.31 identifies the Disable operational state of the connection between
NE and WebEML.

Figure 3.31 Disable operational state of the connection between NE and WebEML
icon

3.

SUP Supervision state

Figure 3.32 shows the NE is under supervision.


Figure 3.32 NE is under supervision icon

Figure 3.33 shows the NE is not under supervision.


Figure 3.33 NE is not under supervision icon

4.

OS OS isolation

Figure 3.34 shows the User State unblocked.


Figure 3.34 User State unblocked icon

Figure 3.35 shows the User State blocked.


Figure 3.35 User State blocked icon

a.

NTP Network Timing Protocol

Figure 3.36 shows the Protocol disabled


Figure 3.36 Protocol disabled

Figure 3.37 shows the Protocol enabled, but neither server is reachable.

User Manual 3DB19901AFAA Edition 01

391

WebEML Main View


Figure 3.37 Protocol enabled, but neither server is reachable

Figure 3.38 shows the Protocol enabled and at least one of the two servers is
reachable.

Figure 3.38 Protocol enabled and at least one of the two servers is reachable

Figure 3.39 shows the Protocol enabled, and both servers are reachable.
Figure 3.39 Protocol enabled

5.

AC Abnormal Condition

Figure 3.40 shows the Normal operating condition.


Figure 3.40 Normal operating condition

Figure 3.41 shows the Detection of an ABNORMAL operative condition. The


operator can visualize Abnormal condition with the Diagnosis Abnormal
condition list menu.
Figure 3.41 Detection of an ABNORMAL operative condition

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 "+", the tree 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 a round-shape icon showing the alarm status of component.

392

User Manual 3DB19901AFAA Edition 01

How to configure a new equipment

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

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

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

3.2.6.3 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, including optional equipment, is the
following:
User Manual 3DB19901AFAA Edition 01

393

How to configure a new equipment

394

1.

Enable the plug-in units: refer to EQUIPMENT TAB-PANEL (Equipment)

2.

MSS-1 only: configure the housekeeping inputs: see MSS External Input Point
view (to open this view double click on the HK inputs on an MSS-1) (Housekeeping)

3.

MSS-8 only: configure the Enhanced Fan unit if applicable: see MSS A-FANS Main
View (to open this view double click on the A-FANS card) (Housekeeping)

4.

Configure the Core-E unit: refer to Core-E VIEW for Core-E and ETHERNET
DOMAIN (to open this view double click on a Core-E unit) (Core-E domain)

5.

Configure the Radio unit or the MPT Access Unit: refer to RADIO VIEW for
RADIO DOMAIN (to open this view double click on a Radio unit) (Settings)

6.

Configure the PDH unit: refer to PDH VIEW for PDH DOMAIN (to open this view
double click on a PDH unit) (PDH unit configuration)

7.

Configure the SDH unit: refer to SDH VIEW for SDH DOMAIN (to open this view
double click on a SDH unit) (SDH unit configuration)

8.

Configure the P8ETH or EASv2 unit (if any): refer to EAS VIEW for P8ETH and
EASv2

9.

Configure the Ethernet Ring (if required): refer to ETHERNET RING


CONFIGURATION VIEW (Ethernet Ring Configuration)

10.

Configure the LAG (if required): refer to LAG CONFIGURATION (LAG


Configuration)

11.

Configure the QoS (if required): refer to QoS CONFIGURATION (QoS


Configuration)

12.

Configure the 16xE1 ATM (ASAP) unit (if any): refer to ATM VIEW for ATM
DOMAIN (to open this view double click on an ASAP unit)

13.

Create Traffic Descriptors for ATM traffic: refer to CONFIGURATION MENU


(Traffic Descriptors)

14.

Configure the AUX peripheral unit, if any, to enable the 64kbit/s service channels and
to use the external points: refer to AUX VIEW for AUX DOMAIN (to open this
view double click on the AUX Peripheral unit)

15.

Configure the Synchronization: refer to SYNCHRONIZATION TAB-PANEL


(Synchronization)

16.

Configure the NE time: refer to CONFIGURATION MENU (NE Time)

17.

Configure the System parameters: refer to CONFIGURATION MENU (System


Settings)

18.

Create the Cross-connections: refer to CONFIGURATION MENU (Crossconnections)

19.

Create the Auxiliary Service Channel cross connections, if the AUX peripheral unit
has been installed: refer to CONFIGURATION MENU (AUX Cross Connections)

20.

Configure IP/SNMP: refer to CONFIGURATION MENU (Network


Configuration)

21.

Select the VLAN configuration and create VLAN, if required: refer to VLAN
MANAGEMENT
User Manual 3DB19901AFAA Edition 01

Configuration Menu

3.4 Configuration Menu


Figure 3.42 Configuration menu

3.4.1 NE Time Menu


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
Configuration Menu Network Configuration NTP Configuration.
The NTP Status field shows:

status of NTP (enabled/disabled);

User Manual 3DB19901AFAA Edition 01

395

Configuration Menu

IP address of the Main Server, which distributes the time to all the NEs in the
network;

IP address of the Spare Server (IP address of a second NTP Server), which replaces
the Main Server in case of failure.
Figure 3.43 NE Time configuration menu

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

3.4.2 Network Configuration Menu


To get access the Network Configuration option select the Configuration pull down
menu.
The Network Configuration menu includes the following operations:
Table 3.1 Network Configuration menu
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

396

User Manual 3DB19901AFAA Edition 01

Configuration Menu
Table 3.1 Network Configuration menu (Continued)
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)
Activate IPv6 stack or Activate IPv4 stack
IPv6 pre-provisioning
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 IPv4 address: 10.0.1.2
Fixed default mask: 255.255.255.255
Figure 3.44 Local Configuration menu

Default IPv6 address: FEC0:0:0:1::1


Fixed prefix length: 128
The 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.
The Close button closes the dialogue.

User Manual 3DB19901AFAA Edition 01

397

Configuration Menu

The 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).
Figure 3.45 NTP Configuration menu

Put a check mark in the NTP protocol field to enable the protocol and write in the Main
Server address field the IP address of the server, which is in charge to distribute the time
to all the NEs in the network. In the Spare Server address field write the IP address of the
Spare Server.
The Server reachability field is a read-only field, which shows the reachability of the NTP
servers. The following information can appear:

Main server reachable

Spare server reachable

None servers reachable

Both servers reachable

Click on Refresh to update the screen.


Click on Apply to send to the NE the NTP Configuration.

398

User Manual 3DB19901AFAA Edition 01

Configuration Menu

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 parameters for IP Static Routing Configuration.
Figure 3.46 IP Static Routing Configuration menu

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 (if using IPv4) or Prefix length (if using IPv6):allows to define the IP Mask
to reach a network, or specifies the prefix length

3.

Gateways: 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.

User Manual 3DB19901AFAA Edition 01

399

Configuration Menu

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
(dimmed) 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 Gateway 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; see Figure 3.47.
Note: If the NE local IP address is configured in IPv6, the OSPF version used will be
OSPFv3; see Figure 3.48.

400

User Manual 3DB19901AFAA Edition 01

Configuration Menu
Figure 3.47 OSPF area configuration with OSPFv2

Figure 3.48 OSPF area configuration with OSPFv3

The following fields and data are present:

OSPF Area IP Address

OSPF Area Stub

The fields give information that includes all the addresses (specific to a NE and to a
Network) in an Area.

User Manual 3DB19901AFAA Edition 01

401

Configuration Menu

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

To configure a new area tick the new check box to activate the IP address stub area. Enter
the OSPF Area Address and the OSPF Area Stub Flag (True/False) and press Create
button to apply and add the area to the table.
Figure 3.49 New OSPF Area Configuration menu

Note: A maximum of 3 areas can be created.

Note: When the 9500 MPR is used with other equipment, the OSPF interface parameters
of the equipment must be the same as those of the related TMN interface on the 9500
MPR.

The 9500 MPR OSPF parameters are:

402

User Manual 3DB19901AFAA Edition 01

Configuration Menu

Hello Interval: 10 seconds

Router Dead Interval: 40 seconds

Retransmit Interval: 5 seconds

Interface Transit Delay: 1 second

MTU: 1500 bytes

3.4.2.6 IP Point to Point Configuration


This menu is not implemented.

3.4.2.7 Activate IPv6 stack


The 9500 MPR can use either an IPv4 or an IPv6 stack for TCP/IP and to build the DCN.
Applications running over the internal NE LAN, such as MAP and FTP, are always bound
to the IPv4 stack.
If you activate IPv6 on the NE without performing pre-provisioning, default parameters
will be applied.
Caution: Mixed configuration of IPv4 and IPv6 NEs is not supported. Before activating
IPv6, ensure that all NEs in the network are IPv6 capable, that is, running R4.1.0 software.
A controlled activation will be required; see your local guidelines.
Note: If the IPv6 stack has been activated, you will not be able to configure IPv4
parameters using the SNMP interface.

When Activate IPv6 stack is selected a warning screen is displayed, as shown in


Figure 3.50. Click on the Yes button to complete the activation.

User Manual 3DB19901AFAA Edition 01

403

Configuration Menu
Figure 3.50 IPv6 stack warning

3.4.2.8 Activate IPv4 stack


If the IPv6 stack has been activated, the menu item changes to Activate IPv4 stack, to return
to the IPv4 stack.

3.4.2.9 IPv6 pre-provisioning


Choose IPv6 Pre-provisioning to set IPv6 parameters before activating IPv6 on the NE. If
you activate IPv6 on the NE without performing pre-provisioning, default parameters will
be applied. To pre-provision the NE for IPv6, see IPv6 pre-provisioning.
Caution: Mixed configuration of IPv4 and IPv6 NEs is not supported. Before activating
IPv6, ensure that all NEs in the network are IPv6 capable, that is, running R4.1.0 software.
A controlled activation will be required; see your local guidelines.

3.4.2.10 Routing Information


Select the Configuration pull down menu. Select the Network Configuration and then
from the cascading 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.

404

User Manual 3DB19901AFAA Edition 01

Configuration Menu
Figure 3.51 Routing Information screen

The Refresh button allows to refresh the information shown in the screen.
The Close button closes the dialogue without changing of the data.

3.4.3 Alarm Severities Menu


By selecting the Alarm Severities option from the Configuration menu the screen in
Figure 3.52 appears.
In this screen in the Profile Name field are listed the 4 default Alarm Severity Profiles:

Profile "No Alarms". With this profile all alarms are disabled.

Profile "All Alarms". This profile enables the emission of all the alarms.

Profile "No Radio Tx Alarms". This profile disables the emission of the Tx alarms
of the radio link.

Profile "No Radio Rx Alarms". This profile disables the emission of the Rx alarms
of the radio link.

Profile "MptSubrack Battery Alarms". This profile disables the emission of the
Battery Fail alarms of the MPT-HLS equipment.

User Manual 3DB19901AFAA Edition 01

405

Configuration Menu
Figure 3.52 Alarm Severities Profile

This screen is a read-only screen. It is only possible to select one Profile Name and display
the relevant alarms.
An Alarm Profile is the complete set of the equipment alarms with their severity in case of
Service Affecting situation and No Service Affecting situation.
Each alarm has its Service Affecting and No Service Affecting attribute, which can differ
according to the Alarm Severity Profile.
In the current release an Alarm Profile can be assigned to the following objects in the
equipment: MSS subrack, TMN local Ethernet, Radio, and Core-E SFPs.
To do this association (in the example in the next Figure the MSS-8 object has been used):

406

1.

Select the object to which an Alarm Profile has to be associated.

2.

Click on the icon.

User Manual 3DB19901AFAA Edition 01

Configuration Menu
Figure 3.53 Select object to associate an alarm profile

Note: Buttons Rename, Modify, Clone and Delete are not supported.

3.

Select the Alarm Profile to be associated.

4.

Put a check mark on the "Show details" box.

5.

The list of the alarms with the relevant severity will appear.

6.

Click on the Apply button to associate the Alarm Profile.

User Manual 3DB19901AFAA Edition 01

407

Configuration Menu
Figure 3.54 Associate an alarm profile

3.4.4 System Settings


This menu allows the system configuration, providing the setting of some parameters for
the NE setup.
Figure 3.55 shows the System Settings window. The window has the following fields:

408

1.

Tributary Port Configuration

2.

DHCP

3.

Admission Control for Adaptive Modulation (ODU300 only) (for ETSI market only)

4.

Ethernet LOS Criteria


User Manual 3DB19901AFAA Edition 01

Configuration Menu

5.

Static Lag Criteria

6.

System Priority Parameter

7.

Event and Alarm Log

8.

NE MAC Address

9.

SNMP Mode

10.

Latitude and Longitude

Note: The QoS Classification criteria, that was present in the System Setting in the
previous releases, was moved to the Configuration QoS Configuration menu.

Figure 3.55 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.

DHCP

User Manual 3DB19901AFAA Edition 01

409

Configuration Menu

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

Admission Control for Adaptive Modulation (ODU300 only)


The Admission Control for TDM flows (cross-connected to radio direction working
in Adaptive Modulation) can be enabled or disabled. Default: Enabled.
When the Admission Control is "Enabled", the check is performed taking into
account the capacity of the QPSK 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 QPSK and all the traffic exceeding QPSK
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 QPSK. In order to facilitate
provisioning and commissioning operations, a specific admission control check at
WebEML level has been inserted, avoiding any potential mistakes from the user
provisioning a number of E1s that are not fitting inside QPSK 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 QPSK-16-64 QAM range or 16 QAM for QPSK-16 QAM
range).
it is possible to provision a number of E1s exceeding the QPSK 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 QPSK, all the TDM traffic
is impacted. This feature is answering the need of transmitting an high number of
E1s, but without giving up the benefits of adaptive modulation for Ethernet traffic.

4.

Ethernet LOS Criteria


By enabling this feature the following additional criteria are added to the Core
protection switching criteria:

410

LOS of Optical User Ethernet interface


User Manual 3DB19901AFAA Edition 01

Configuration Menu

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
Card Not Ready and Flash Card Realignment In Progress conditions represent inhibition of
the Core protection switching with respect to Operator Commands and the additional
criteria listed above.

5.

Static Lag Criteria


This feature is available only if the spare Core unit has been installed.
By enabling this feature the Ethernet ports of the Core-E unit in stand-by are in ON
state (as the ports of the Active Core-E unit), but the Ethernet traffic is not forwarded.
This behavior allows to reduce the out of service time (within few seconds) of user
traffic passing through the User Ethernet interfaces in case of Core protection
switching.
This feature shall not be used, when the NE is connected to an equipment performing
Link Aggregation and not supporting Active/Standby management of aggregated
links.

6.

System Priority Parameter


This parameter is required in LAG system supporting the LACP to provision the
System Priority (2 bytes) associated to the NE.
This parameter, together with the System ID (the NE MAC address), determines the
System Aggregation Priority (8 bytes). The range for the System Priority parameter
is: 0 to 65,535 (default: 32,768).
System Aggregation Priority:

[0 - 1 bytes] System Priority

[2 - 7 bytes] NE MAC address

The System Aggregation Priority of each System is an eight octet binary number.
A LAG system, supporting the LACP, dynamically assigns the member ports of the
LAG group, starting by the highest priority port to the lowest priority ports.
At the remote end of the same LAG link, there is another system that wants also to
assign the ports to the LAG group according to its own port priorities.
Here two systems propose two different port assignments for the same LAG group
and it is the system, with the highest system priority, that overrides the link and
imposes its port assignment.
7.

Event and Alarm Log

User Manual 3DB19901AFAA Edition 01

411

Configuration Menu

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 that shows the MAC address of the NE. This MAC
address must be used in the cross-connection with TDM2Eth profile.

9.

SNMP Mode
The 9500 MPR supports access from SNMP managers implementing both SNMPv2/
v1 and SNMPv3 protocols. The supported SNMP operating modes are the following:

SNMPv2: This is the default mode. Only SNMPv2/v1 managers are allowed
access to the NE for both reading and writing.

SNMPv3: Only SNMPv3 managers are allowed access to the NE.

SNMPv3 addresses security problems by adding two new features on top of the
existing SNMPv1 and SNMPv2 network management protocols:

Authentication using hashing and time stamps.

Confidentiality using encryption.

SNMPv3 is based on the following:

The User based Security Model (USM), which provides strong user
authentication, data integrity, privacy (encryption) and time stamp management
(timeliness),

The View base Access Control Model (VACM), which provides a mechanism
for managing what information is available to users.

Authentication is provided using the HMAC-MD5-96 standard authentication


protocol.
The SNMP operating mode is stored in permanent memory on a Flash card.
Caution: possibility of service interruption. Changing the SNMP mode requires the NE to
restart in the new mode.

Caution: possibility of service interruption. When the NE has been configured to operate
in SNMPv3 mode, the database must be cleared for the NE to be returned to SNMPv2
mode.
Note: User authentication using SNMPv3 is not compatible with user authentication and
authorization management by remote TACACS+ server. If the NE is configured in SNMPv3
mode, it is not possible to enable TACACS+ on the SNMP interface using the WT-CLI. If
TACACS+ is enabled on the SNMP interface, it is not possible to configure the NE in SNMPv3
mode.

To change the SNMP Mode from SNMPv2 to SNMPv3, choose the SNMPv3 radio
button in the SNMP Mode Migration field and click on the Apply button.
10.

412

Latitude and Longitude

User Manual 3DB19901AFAA Edition 01

Configuration Menu

This field is a read-only field that shows the Latitude and Longitude of the NE, if
available.

3.4.5 Cross connections Menu


3.4.5.1 Main Cross Connection View
The Main view (refer to Figure 3.57) is a graphical representation of Cross-connectable
slots. Slots and Ethernet ports (represented by connectors) are arranged according to the
equipment configuration:

The CORE module is on the left side of the screen.

The even numbered slots of rows 2 to 4 are on the top of the screen.

The odd numbered slots of rows 2 to 4 are on the bottom of the screen.

There are a maximum of 6 PDH/SDH/ASAP/EAS/Radio/MPT-ACC slots (placed in


the MSS-8 sub-rack) or 2 PDH/SDH/ASAP/EAS/Radio/MPT-ACC slots (placed in
the MSS-4 sub-rack).

Protection groups are represented by:

PDH modules have a dashed line connecting the two connector icons. The even
card connector icon is grayed out.

P8ETH (EAS Ethernet Access Service) and EASv2 modules have a dashed box
surrounding the two slots.

MPT radios have a dashed line connecting the two connector icons. The higher
numbered radio's connector icon is grayed out.

There are a maximum of 6 Ethernet ports placed on the Core-E area in the left side of
the screen. Port 4 is visible only when set to transport mode. If Ethernet port 4 is
set to TMN, icon 4 is not shown. Port 5 and 6 are visible, if the SFP plug-in has
been installed and enabled in the Core-E unit.

P8ETH or EASv2 module: Ports 5 to 8 can be provisioned with EMPTY, SFP, or MPT-HC/
HC-HQAM/XP/XP-HQAM. With an EASv2 module, ports 1 to 4 can also be provisioned
with MPT-HC/HC-HQAM/MC/XP/XP-HQAM and ports 5 to 8 can be provisioned with
MPT-HLS.
For ports provisioned with EMPTY, no connector icon will be displayed for that port. For
ports provisioned with SFP, an Ethernet connector icon will be displayed for that port. For
ports provisioned with MPT-HC/HC-HQAM/XP/XP-HQAM or MPT-HLS, a Radio
connector icon will be displayed for that port. The Ethernet ports cannot be crossconnected. The Radio ports can be cross-connected. Refer to Figure 3.56.

User Manual 3DB19901AFAA Edition 01

413

Configuration Menu
Figure 3.56 P8ETH module

Note: In the following pages the examples will be shown 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). Refer to Figure 3.57.

414

User Manual 3DB19901AFAA Edition 01

Configuration Menu
Figure 3.57 Main Cross-Connections View

Note: Ethernet port#5 and port#6 will appear only if the optional SFP plug-in has been
installed and enabled in the Core-E unit. To enable the SFP plug-in go to the Setting tabpanel of the Core-E unit in the Equipment tab-panel.

3.4.5.1.1 LAG/RING area


This area includes the created LAGs (if any) and the created Ethernet Ring (if any).

3.4.5.1.2 LAG
If a LAG (Radio or Ethernet) has been created by using Configuration menu > LAG
Configuration, in the LAG area (on the right side of the screen) will appear the icons of
the LAG with the identifying number of the LAG.
Different icons are used to identify Radio LAG or Ethernet LAG.
The Ethernet ports involved in an Ethernet LAG are only present in the LAG area (not in
the CORE-E area).
In the Figure LAG #4 is a Radio LAG, LAG #1 is an Ethernet LAG.

User Manual 3DB19901AFAA Edition 01

415

Configuration Menu

Note: Cross-connections that have to be terminated on a Layer1 LAG shall be performed


with the Multicast MAC Address of the NE hosting the LAG.

Figure 3.58 LAG cross-connection

3.4.5.1.3 Ring
If an Ethernet Ring has been created by using the Ring icon in the Tool bar, the icon of the
Ring will appear with the identifying number.

416

User Manual 3DB19901AFAA Edition 01

Configuration Menu
Figure 3.59 Ring cross-connection

3.4.5.1.4 Connectors
The connectors representing the MSS slots are start- and end-point for actual crossconnections. By using the mouse drag-and-drop operations the operator can create crossconnections through these points. These connectors have specific icons:

identifies Ethernet RJ-45 connector (Core-E, MSS/CORE and EAS Ethernet ports)

identifies Radio slots (to interface ODU300)

identifies PDH/SDH ports

identifies Radio slots (to interface MPT-HC/HC-HQAM/HLS/MC/XP/XPHQAM)

User Manual 3DB19901AFAA Edition 01

417

Configuration Menu

identifies Radio LAG

identifies Ethernet LAG

identifies an Ethernet Ring

The connectors have different colors depending on the associated slots state:

White: a connector able to accept a cross-connection and has no active crossconnection

Green: a connector able to accept a cross-connection and already has at least one
active cross-connection

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 3.60).

418

User Manual 3DB19901AFAA Edition 01

Configuration Menu
Figure 3.60 Cross-connections Example

3.4.5.1.5 Graphical Area


This area contains a panel and various components representing NE cross-connectable slots
(or connectors). The operator can directly edit with the mouse this graphical area to visually
create and modify cross-connections between available connectors: Figure 3.61 shows an
example of ongoing cross-connections configuration.

User Manual 3DB19901AFAA Edition 01

419

Configuration Menu
Figure 3.61 Creating cross-connection between PDH and radio

Some steps (modification dialogs) differ depending on cross-connection types.

3.4.5.1.6 Buttons
Figure 3.62 Cross-connections buttons

At the bottom in the menu there are four buttons:

420

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 produce any visual change (in other words, the state of the
NE will be consistent with what is shown in the GUI) anyway, clicking on Apply
button will show a progress dialog.

Refresh: reload the data from the NE and update the graphical state; any modification
performed and not applied will be lost.

Close: close the cross-connection view, and return to the caller (JusmMainView), any
modification performed and not applied will be lost.
User Manual 3DB19901AFAA Edition 01

Configuration Menu

Help: opens the Help On Line.

3.4.5.1.7 Segregated port view


From the Cross Connection view by pressing Alt+W the Segregated Port view opens.
Figure 3.63 Segregated Port View (default configuration)

In the default configuration (shown in Figure 3.63) all the slots and Ethernet ports in CoreE unit are cross-connectable to each other (all the slots/ports are not segregated).
To go back to the Cross Connection View press Alt+W.
Note: The MPT Access and EAS unit ports can be segregated from each other, but they
cannot be individually segregated with other ports belonging to other units. Only the
complete MPT Access or EAS unit can be segregated with other ports.

User Manual 3DB19901AFAA Edition 01

421

Configuration Menu
3.4.5.1.7.1 How to segregate slots or ports
Double click on a slot icon or an Ethernet port icon and select the slots/ports that can be
connected (this means that the not selected slots/ports cannot be connected; they are
segregated).
Example: with a double click on the icon of Slot#5 RADIO Figure 3.64 opens.
Figure 3.64 Port selection window

To segregate Slot#5 RADIO from Ethernet ports#2, #3, #4, #5 in the Core-E unit, click on
the relevant square to remove the check mark, as shown in Figure 3.65.
Figure 3.65 To segregate ports

By clicking OK the Segregated Port view updates and shows (with dashed lines) the
segregated ports, as shown in Figure 3.66.

422

User Manual 3DB19901AFAA Edition 01

Configuration Menu
Figure 3.66 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: To avoid loops all radio ports of the Nx(1+0) or Nx(1+1) configuration must be
segregated from each other.

3.4.5.2 How to create a cross-connection


Perform the following to create a cross-connection:
1.

Move the mouse pointer on the source port;

2.

Press the left button and, while keeping button pressed, move mouse pointer onto
destination port;

3.

Release the left button.

If the action involves two cross-connectable ports, a dialog will appear allowing you to
setup a cross-connection. Looking at Figure 3.67, it is possible to see different aspects of
configuration:

User Manual 3DB19901AFAA Edition 01

423

Configuration Menu

Slot#8 PDH is cross-connected to Slot#5 radio ODU300, to Slot#4 MPT-ACC and to


Ethernet Port#1;

Slot#4 MPT-ACC is cross-connected to Ethernet Port#1;

Slot#5 RADIO (and Slot#6 RADIO) are cross-connected to Ethernet Port#2;

Slot#3 MPT-ACC is cross-connected to Slot#4 MPT-ACC;

Ethernet Port#3 PDH (blue) could not accept cross-connections;

Slot#3 and Slot#4 (green) could accept more cross-connections;

Slot#5 and Slot#6 are in 1+1 configuration.

Each connection line is colored according to slots types it connects (as shown in
Figure 3.67):

PDH-Radio connection: black line;

SDH-Radio connection: black line;

ATM-Radio connection: orange line;

PDH-Eth connection: blue line;

ATM-Eth connection: magenta line;

Radio-Radio connection: red line;

Radio-Eth connection: green line;

Ring connection: cyan line.

SDH-LAG connection: black line.

These colors will be applied to the graphical area, when the operator releases the mouse
button above cross-connection destination slot.
Note: The ATM cross-connection lines have the following colors:
ATM-Radio connection: orange line;
ATM-Eth connection: magenta line.

In the types of cross-connections above Eth means Ethernet User Port or Ethernet LAG
and Radio means Radio to interface ODU300 or Radio LAG.

424

User Manual 3DB19901AFAA Edition 01

Configuration Menu
Figure 3.67 Actual colored view example

3.4.5.2.1 Creation Dialogs


When connecting two linkable slots through a cross-connection, a di