3DB19283ACAATQZZA01_V1_9500 MPR R7.0.0 Product Information Manual

Release 7.0.0 3DB 19383 ACAA Issue 01 Product Information Manual

9500 Microwave Packet Radio

Product Information Manual

Nokia — Proprietary and confidential. Use pursuant to applicable agreements.


Nokia is a registered trademark of Nokia Corporation. Other products and company names mentioned herein may be trademarks or tradenames of their respective owners. The information presented is subject to change without notice. No responsibility is assumed for inaccuracies contained herein. © 2016 Nokia. All rights reserved. Contains proprietary/trade secret information which is the property of Nokia and must not be made available to, or copied or used by anyone outside Nokia without its written authorization. Not to be used or disclosed except in accordance with applicable agreements. Disclaimers Nokia 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 Nokia, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Nokia 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 nonNokia products. Please note that this information is provided as a courtesy to assist you. While Nokia tries to ensure that this information accurately reflects information provided by the supplier, please refer to the materials provided with any non-Nokia product and contact the supplier for confirmation. Nokia assumes no responsibility or liability for incorrect or incomplete information provided about non-Nokia products. However, this does not constitute a representation or warranty. The warranties provided for Nokia products, if any, are set forth in contractual documentation entered into by Nokia 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. THIS PRODUCT COMPLIES WITH D.H.H.S. RADIATION PERFORMANCE STANDARDS 21 CFR, 1040.10, FOR A CLASS 1 LASER PRODUCT.

2


DANGER Invisible laser radiation is present when the optic connector is open. AVOID DIRECT EXPOSURE TO BEAM. This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case users will be required to correct the interference at their own expense. Release notes describing revisions to this software may impact operations described in this manual. This transfer of commodities, technology, or software, if from the United States, is an export in accordance with the U.S. Export Administration Regulations. Diversion contrary to U.S. law is prohibited. The export or re-export (further transfer) of such commodities, technology, software or products made from such technology is prohibited without proper authorization(s) from the U.S. Department of Commerce or other appropriate U.S. government agencies.

3


4


Table of Contents Preface

........................................................................................................55

9500 MPR documentation ...................................................................................................55 Related documentation .......................................................................................................57 Naming conventions in the documentation .........................................................................59 Audience ...................................................................................................................60 Information symbols ............................................................................................................60 Contact information .............................................................................................................61 Technical support ................................................................................................................61 Documentation feedback.....................................................................................................61

1

FCC part 15 subpart B .................................................................63

1.1 1.2 1.3

9500 MPR-A unlicensed radio...................................................................63 FCC Class B compliance statement..........................................................63 FCC Class B requirements........................................................................64

2

Safety awareness..........................................................................65

2.1 2.2

Safety EMC-EMF-ESD norms and equipment labeling ............................65 Declarations of conformity to CE marking and Countries List for the ETSI market.........................................................................................66 Safety rules................................................................................................68 General rules .............................................................................................68 Observe safety rules..................................................................................69 Labels indicating Danger, Forbidding, Command .....................................70 Dangerous electrical voltages ...................................................................70 Labeling: ...................................................................................................70 Safety instructions: ...................................................................................71 Risks of explosions....................................................................................71 Labeling: ...................................................................................................71 Safety instructions: ...................................................................................72 Moving mechanical parts...........................................................................72 Labeling: ...................................................................................................72 Safety instructions: ...................................................................................72 Equipment connection to earth..................................................................73 Labeling: ...................................................................................................73 Safety instructions: ...................................................................................73 Heat-radiating mechanical parts................................................................73 Labeling: ...................................................................................................73 Safety instructions: ...................................................................................74 Microwave radiations (EMF norms)...........................................................74 Safety instructions: ...................................................................................74 Electromagnetic compatibility (EMC norms)..............................................75 Cables: .....................................................................................................77 Equipment protection against electrostatic discharges .............................77 Cautions to avoid equipment damage .......................................................78 Electrostatic-sensitivity ..............................................................................78

2.3 2.3.1 2.3.1.1 2.4 2.4.1 2.4.1.1 2.4.1.2 2.4.2 2.4.2.1 2.4.2.2 2.4.3 2.4.3.1 2.4.3.2 2.4.4 2.4.4.1 2.4.4.2 2.4.5 2.4.5.1 2.4.5.2 2.4.6 2.4.6.1 2.5 2.5.1 2.6 2.7 2.7.1

5


2.7.1.1 2.7.2 2.7.2.1 2.8 2.9 2.10 2.10.1

Handling cards...........................................................................................79 Screw fixing ...............................................................................................80 MSS-ODU cable disconnection / connection.............................................80 Fan, equipment rack, and equipment cabinet precautions........................80 Electrical precautions ................................................................................81 Harmful optical signals ..............................................................................82 Laser precautions ......................................................................................82

Product and Solution descriptions......................................................... 85

6

3

9500 MPR general system description .......................................87

3.1 3.2 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.4 3.4.1 3.4.1.1 3.4.1.2 3.4.2 3.5 3.6 3.7 3.7.1 3.7.2

Introduction................................................................................................87 Purpose and Function ...............................................................................87 Innovative solutions ...................................................................................88 Multiservice aggregation layer...................................................................88 Service awareness ....................................................................................89 Packet node matrix....................................................................................90 Service-driven adaptive modulation ..........................................................91 9500 MPR solutions ..................................................................................91 Split-mount installation ..............................................................................95 MPR-LH solution .......................................................................................95 The MSS-1c...............................................................................................96 MPR-e ......................................................................................................97 9500 MPR family overview ........................................................................97 Standards ..................................................................................................98 JF6-9558H and JF6-9558HC (unlicensed) radio.....................................107 FCC class B compliance statement.........................................................107 FCC class B requirements.......................................................................107

4

System administration ...............................................................109

5

Features.......................................................................................111

5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 5.14 5.15 5.16

Microwave service switch (MSS).............................................................111 Radio .......................................................................................................111 Radio transceivers...................................................................................113 Ethernet ...................................................................................................114 Managed services and profiles................................................................115 Traffic interfaces ......................................................................................116 Power interfaces for MPT ODU ...............................................................116 Configurations .........................................................................................117 Cross-connections...................................................................................117 Database backup and restore .................................................................117 In-service upgrade...................................................................................117 LAG (link aggregation group) ..................................................................117 License key management........................................................................118 Loopback .................................................................................................118 Network Communication .........................................................................118 NE time....................................................................................................118


5.17 5.18 5.19 5.20 5.21 5.22 5.23 5.24 5.25 5.26 5.27 5.28

Non-administrator user ............................................................................118 Performance monitoring ..........................................................................118 Port segregation ......................................................................................119 Remote inventory ....................................................................................119 Security....................................................................................................119 Software package rollback ......................................................................120 Stacking for EAS/EASv2/MPT access cards...........................................120 Synchronization .......................................................................................120 Automatic link discovery ..........................................................................120 Standard features of MPR-e....................................................................121 Standard features of MSS-1c ..................................................................121 MPR-e prerequisites................................................................................122

6

Equipment layout........................................................................125

6.1 6.2 6.3 6.3.1 6.3.2 6.3.3 6.3.4 6.3.5 6.3.6 6.3.6.1 6.3.6.2 6.3.7

Rack assemblies .....................................................................................125 Constraints ..............................................................................................125 Shelf assemblies .....................................................................................126 MSS-8 shelf .............................................................................................127 MSS-4 shelf .............................................................................................128 MSS-1 unit...............................................................................................129 MSS-O.....................................................................................................129 MPT-HL/HLC shelf ..................................................................................131 MPT-HLS shelves....................................................................................132 MPT-HLS standard shelf .........................................................................132 MPT-HLS compact shelf..........................................................................134 Miscellaneous assemblies.......................................................................137

7

Functional operation ..................................................................139

7.1 7.1.1 7.1.2 7.1.3 7.1.4 7.1.5 7.2 7.2.1 7.2.1.1 7.2.1.2 7.2.1.3 7.2.1.4

Microwave service switch (MSS).............................................................139 MSS-8 shelf .............................................................................................140 MSS-4 shelf .............................................................................................140 MSS-1 shelf .............................................................................................141 MSS-O.....................................................................................................141 MSS-1c ...................................................................................................141 Radio .......................................................................................................142 Radio configuration..................................................................................142 Protection schemes .................................................................................142 Channel spacing......................................................................................143 Radio configuration rules for MPT ODU ..................................................143 Rule for 2048 QAM modulation scheme with MPT-HC-HQAM/XPHQAM......................................................................................................144 Multiple channels arrangement for 1024 and 2048 QAM with the same sub-band on one antenna for MPT-HC-HQAM/XP-HQAM............144 Adjacent channels deployment rules for adaptive modulation Copolar or XPIC configurations up to 1024 QAM....................................146 Adaptive modulation ................................................................................147 Admission control ....................................................................................147 Adaptive modulation and admission control with MPT-HLC....................149 Adaptive equalization ..............................................................................150

7.2.1.5 7.2.1.6 7.2.2 7.2.2.1 7.2.3 7.2.4

7


7.2.5 7.2.6 7.2.7 7.2.8 7.2.9 7.2.10 7.2.10.1 7.2.11 7.2.12 7.2.12.1 7.2.12.2 7.2.12.3 7.2.12.4 7.2.12.5 7.2.12.6 7.2.12.7 7.2.12.8 7.2.12.9 7.2.12.10 7.2.12.11 7.2.12.12 7.2.12.13 7.2.12.14 7.2.12.15 7.2.12.16 7.2.12.17 7.2.12.18 7.2.12.19 7.2.12.20 7.2.13 7.2.14 7.2.14.1 7.2.14.2 7.2.15 7.2.15.1 7.2.16 7.2.17 7.2.18 7.2.19 7.2.19.1 7.2.20 7.2.21 7.2.21.1 7.2.21.2 7.2.22 7.2.22.1 7.2.23 7.2.23.1 7.2.24

8

Fiber-microwave protection .....................................................................150 Frequency agility .....................................................................................154 Link identifier ...........................................................................................154 Loopback .................................................................................................154 Performance monitoring ..........................................................................155 Power monitoring.....................................................................................155 Branching loss for MPT-HLC ..................................................................155 Radio direction label ................................................................................156 Radio L1 LAG ..........................................................................................156 Types of L1 link aggregation ..................................................................157 L1 LAG with EASv2 .................................................................................164 L1 LAG on MSS-O...................................................................................166 L1 LAG creation.......................................................................................166 L1 LAG lowest index port ........................................................................168 Port membership rules ............................................................................168 Supported port memberships ..................................................................172 Provisionable radio parameters for members of L1 LAG .......................188 L1 Radio LAG deletion ............................................................................189 L1 Radio LAG QoS configuration ............................................................189 L1 Radio LAG rate...................................................................................189 Admission control ....................................................................................190 Available user ports .................................................................................190 Maximum Ethernet frame length .............................................................190 Cross-connections...................................................................................190 Performance monitoring ..........................................................................190 Port segregation ......................................................................................191 PPP-RF configuration..............................................................................191 SSM.........................................................................................................191 Synchronization .......................................................................................192 Radio L2 LAG ..........................................................................................192 Transmit power control ............................................................................194 ATPC .......................................................................................................195 RTPC.......................................................................................................195 Tx mute....................................................................................................196 Manual timed Tx mute .............................................................................196 Latency optimization ...............................................................................197 AES encryption management..................................................................198 XPIC ........................................................................................................198 XPIC automatic remote TX mute ...........................................................203 Root causes............................................................................................204 Radio transceivers...................................................................................205 MPT ODU ................................................................................................206 MPT-MC (ETSI market only) ...................................................................208 MPR-e (standalone MPT ODU) ..............................................................209 MPT-HL (ANSI market only)....................................................................210 Lower 6 GHz frequency plan ...................................................................210 MPT-HLC (ANSI market only) .................................................................212 Frequency plans ......................................................................................212 MPT-HLS (ETSI market only)..................................................................212


7.2.25 7.2.26 7.2.27 7.2.28 7.2.29 7.2.29.1 7.2.29.2 7.2.30 7.3 7.3.1 7.3.1.1 7.3.1.2 7.3.1.3 7.3.1.4 7.3.1.5 7.3.1.6 7.3.1.7 7.3.1.8 7.3.2 7.3.2.1 7.3.2.2 7.3.3 7.3.4 7.3.4.1 7.3.4.2 7.3.4.3 7.3.4.4 7.3.4.5 7.3.4.6 7.3.4.7 7.3.4.8 7.3.4.9 7.3.4.10 7.3.4.11 7.3.4.12 7.3.4.13 7.3.4.14 7.3.4.15 7.3.4.16 7.3.4.17 7.3.4.18 7.3.4.19 7.3.4.20 7.3.4.21 7.3.4.22 7.3.5 7.3.5.1 7.3.5.2

Radio capacity, channeling and modulation ...........................................217 Monodirectional links ...............................................................................217 Unlicensed radio for MPT-HL, MPT-HLC and 9558HC in the ANSI market......................................................................................................218 Radio configurations with MPR-e ............................................................224 Radio configurations with MSS-1c...........................................................225 1+0 in split-mount configuration for MSS-1c ...........................................225 1+0 repeater configuration for MSS-1c ...................................................225 Typical system configurations for MSS-1c ..............................................226 Ethernet ...................................................................................................228 Ethernet traffic management ...................................................................228 802.1D (with the Core-E card only) .........................................................228 802.1Q.....................................................................................................229 802.1ad....................................................................................................229 Provider bridge components....................................................................230 Ethernet frames processing.....................................................................231 Cross-connected flows processing..........................................................231 Provider Bridge ports with Ethernet LAG.................................................231 Bridge type change..................................................................................232 MSS-1c Ethernet traffic management ....................................................234 Bridge type change..................................................................................234 Reserved multicast addresses ...............................................................234 Frame type ..............................................................................................235 Quality of service (QoS) ..........................................................................236 QoS classification ....................................................................................236 Disabled...................................................................................................236 DiffServ....................................................................................................237 IPv4 traffic class management ................................................................237 IPv6 traffic class management ................................................................237 Priority queue mapping............................................................................238 QoS priority value to internal forwarding class ........................................238 IEEE 802.1p ............................................................................................238 Internal forwarding class to queue mapping............................................242 Scheduler type queue mapping...............................................................242 Queue scheduler algorithm .....................................................................242 Queue size ..............................................................................................243 QoS with jumbo frame ............................................................................244 QoS in the Core-E and CorEvo card .......................................................244 QoS for TMN packets ..............................................................................245 Provider Bridge QoS................................................................................246 QoS for 1588v2 flows ..............................................................................248 QoS in the MPT-HC/HC-HQAM/XP/XP-HQAM.......................................248 QoS in the MPT-HL .................................................................................249 QoS with L1 LAG with EASv2 .................................................................249 QoS in the MSS-1c..................................................................................250 QoS in the MPT with MPR-e and MSS-1c...............................................253 Ethernet features provisioned by craft terminal .......................................256 Port based rate limiting............................................................................256 Storm control (broadcast, multicast, and unknown unicast) ....................257

9


7.3.5.3 7.3.5.4 7.3.6 7.3.6.1 7.3.6.2 7.3.6.3 7.3.6.4 7.3.6.5 7.3.6.6 7.3.7 7.3.7.1 7.3.7.2 7.3.8 7.3.9 7.3.9.1 7.3.9.2 7.3.10 7.3.11 7.3.12 7.3.12.1 7.3.12.2 7.3.12.3 7.3.12.4 7.3.12.5 7.3.12.6 7.3.12.7 7.3.12.8 7.3.13 7.3.13.1 7.3.13.2 7.3.13.3 7.3.13.4 7.3.13.5 7.3.13.6 7.3.13.7 7.3.13.8 7.3.13.9 7.3.13.10 7.3.13.11 7.3.13.12 7.3.13.13 7.3.13.14 7.3.14 7.3.15 7.3.16 7.3.16.1 7.3.16.2 7.3.16.3

10

VLAN based rate limiter...........................................................................258 Per-VLAN per-COS rate limiter ...............................................................259 Ethernet features configured by enhanced configuration file ..................263 Access control list....................................................................................263 Out of range VLAN swap.........................................................................263 Per-flow policer........................................................................................263 Stacked VLAN (Q-in-Q) tagging ..............................................................264 VLAN remarking ......................................................................................264 VLAN swap..............................................................................................264 Input/output flow control ..........................................................................264 Input pause feature..................................................................................265 Output pause feature...............................................................................265 Reserved multicast addresses ...............................................................266 Traffic mode.............................................................................................268 Auto-negotiation ......................................................................................268 Allow 10, 100, and/or 1000 Mb/s half and full duplex ..............................268 Ethernet synchronization messaging channel .........................................269 Ethernet connectivity fault management .................................................269 TACACS+................................................................................................269 Server support ........................................................................................270 Authentication/authorization ...................................................................270 Accounting...............................................................................................271 Parameters for multiple notifications in a single accounting request.....................................................................................................272 Server selection ......................................................................................272 Configuration ..........................................................................................273 Server monitoring ...................................................................................274 Server validation .....................................................................................274 Ethernet ring protection ...........................................................................274 ERP topology...........................................................................................275 Ethernet Ring port restrictions .................................................................277 Ring link...................................................................................................278 Ring port ..................................................................................................278 Ring protection link (RPL)........................................................................278 RPL owner...............................................................................................278 R-APS protocol........................................................................................279 ERP instance...........................................................................................279 ERP operation .........................................................................................279 Ethernet Ring Protection switching criteria..............................................281 Two ERP instances .................................................................................283 TDM traffic ...............................................................................................284 TMN.........................................................................................................285 ERPS and Core protection ......................................................................285 Jumbo frame............................................................................................286 Ethernet L2 LAG......................................................................................286 Packet throughput booster (Header compression)..................................289 Packet throughput booster in L1 LAG .....................................................289 Layer 2 header compression ...................................................................290 Layer 3 header compression ...................................................................290


7.3.16.4 7.3.16.5 7.3.17 7.3.18 7.3.19 7.3.20 7.3.20.1 7.3.20.2 7.3.20.3 7.3.20.4 7.3.21 7.3.21.1 7.3.21.2 7.4 7.4.1 7.4.2 7.4.3 7.4.4 7.4.5 7.4.5.1 7.4.5.2 7.4.5.3 7.4.5.4 7.4.5.5 7.4.6 7.4.6.1 7.4.6.2 7.4.6.3 7.4.7 7.4.7.1 7.4.7.2 7.4.7.3 7.5 7.5.1 7.5.1.1 7.5.1.2 7.5.1.3 7.5.1.4 7.5.2 7.5.2.1 7.5.2.2 7.5.2.3 7.5.2.4 7.5.2.5 7.5.3 7.5.4 7.5.5 7.5.6 7.5.6.1

Dynamically learned address pairs..........................................................291 Automatic fade control.............................................................................291 Performance monitoring ..........................................................................291 Port segregation ......................................................................................291 VLAN IDs.................................................................................................292 EFM OAM Configuration .........................................................................292 Supported functions.................................................................................292 Link OAM operational status ...................................................................293 EFM OAM with Core protection...............................................................294 DTE parameters ......................................................................................294 OAM remote loopback.............................................................................295 Activating OAM remote loopback ............................................................295 ETH OAM alarms ....................................................................................299 Managed services and profiles................................................................299 TDM2TDM ...............................................................................................300 TDM2ETH................................................................................................300 SDH2SDH ...............................................................................................301 ETH2ETH ................................................................................................301 TDM and Ethernet traffic management ...................................................302 Case 1 for E1/DS1/DS3 (TDM2TDM)......................................................303 Case 1 for STM-1/OC-3 (SDH2SDH) ......................................................303 Case 2 for TDM2Eth................................................................................303 Case 3 for TDM2Eth................................................................................303 Case 4 and 5 for ETH2ETH.....................................................................304 TDM2TDM ...............................................................................................304 TDM2Eth .................................................................................................306 SDH2SDH ...............................................................................................307 ETH2ETH ................................................................................................307 MSS-1c traffic profiles .............................................................................308 TDM2TDM ...............................................................................................310 TDM2Eth .................................................................................................312 ETH2ETH ................................................................................................313 Traffic interfaces ......................................................................................313 Core-E .....................................................................................................314 10/100/1000 Base-T Ethernet interfaces.................................................314 GigE SFP Ethernet interfaces .................................................................314 Radio interface for MPT ODU..................................................................314 MPT-HL/HLC/HLS radio interface ...........................................................315 CorEvo.....................................................................................................315 10/100/1000 Base-T Ethernet interfaces.................................................315 Optical SFP Ethernet interfaces ..............................................................315 10GigE SFP Ethernet interfaces on CorEvo-10G ...................................316 Radio interface for MPT ODU..................................................................316 MPT-HL/HLC/HLS radio interface ...........................................................316 E1/DS1 PDH interface.............................................................................316 DS3 PDH interface ..................................................................................317 SDH interface ..........................................................................................317 Ethernet access switch............................................................................317 10/100/1000Base-T Ethernet interfaces..................................................318

11


7.5.6.2 7.5.6.3 7.5.6.4 7.5.7 7.5.7.1 7.5.7.2 7.5.7.3 7.5.7.4 7.5.7.5 7.5.8 7.5.9 7.6 7.6.1 7.6.2 7.6.3 7.6.4 7.7 7.7.1 7.7.2 7.7.3 7.7.4 7.7.5 7.7.6 7.8 7.8.1 7.8.2 7.8.3 7.8.4 7.8.5 7.8.6 7.8.7 7.8.8 7.8.8.1 7.8.8.2 7.8.9 7.8.9.1 7.8.9.2 7.9 7.10 7.11 7.11.1 7.11.2 7.11.3 7.11.4 7.12 7.12.1 7.12.1.1 7.12.1.2 7.12.1.3

12

GigE SFP Ethernet interfaces .................................................................318 MPT-HL/HLC radio interface ...................................................................318 MPT-HC/HC-HQAM/XP/XP-HQAM radio interface .................................318 Ethernet access switch version 2 ............................................................318 10/100/1000Base-T Ethernet interfaces..................................................319 GigE SFP Ethernet interfaces .................................................................319 MPT-HL/HLC/HLS radio interface ...........................................................319 Radio interface for MPT ODU..................................................................319 Backplane compatibility ...........................................................................319 MPT access ............................................................................................320 MSS-1 Shelf ............................................................................................320 Power interfaces for MPT ODU ..............................................................321 Power injector card..................................................................................321 Power injector box ...................................................................................321 MPT power unit .......................................................................................321 MPT Extended Power Unit ......................................................................321 Configurations .........................................................................................322 MSS-8 shelf configurations......................................................................324 MSS-4 shelf configurations......................................................................325 MSS-1 unit configuration .........................................................................327 Stand alone MSS-1/MSS-4/MSS-8 shelf.................................................327 Stacking MSS-1/MSS-4/MSS-8 shelf configuration.................................327 Alarm management .................................................................................329 Cross-connections...................................................................................330 PDH Cross-connections ..........................................................................331 SDH Cross-connections ..........................................................................331 Radio-radio cross-connections ................................................................332 Ethernet cross-connections .....................................................................332 Generic Ethernet flows ............................................................................332 Valid cross connections:..........................................................................332 Point to Point VLAN.................................................................................335 Flow ID number rules ..............................................................................336 Ranging ...................................................................................................336 Destination MAC address........................................................................338 MSS-1c cross-connections......................................................................339 E1/T1 cross-connection...........................................................................340 Ethernet flows..........................................................................................341 Database backup and restore .................................................................341 In-service upgrade...................................................................................342 LAG (link aggregation group) ..................................................................343 LAG overview ..........................................................................................343 LAG hashing............................................................................................343 L1/L2 link aggregation on radio ports (radio L1/L2 LAG).........................344 L2 Link aggregation on user Ethernet ports (Ethernet L2 LAG) ..............344 License key management........................................................................345 License String..........................................................................................345 Transmission capacity .............................................................................346 Unlicensed option (ANSI market only).....................................................347 Adaptive modulation ................................................................................347


7.12.1.4 7.12.1.5 7.12.1.6 7.12.1.7 7.12.1.8 7.12.1.9 7.12.1.10 7.12.1.11 7.12.1.12 7.12.1.13 7.13 7.13.1 7.13.2 7.13.3 7.13.4 7.13.5 7.13.6 7.13.7 7.13.8 7.13.9 7.13.10 7.14 7.15 7.16 7.17 7.18 7.18.1 7.18.1.1 7.18.1.2 7.18.1.3 7.18.1.4 7.18.2 7.18.3 7.18.3.1 7.18.3.2 7.18.3.3 7.18.3.4 7.18.3.5 7.18.3.6 7.18.3.7 7.18.4 7.18.5 7.18.6 7.18.6.1 7.19 7.19.1 7.19.2 7.19.3 7.19.4

Data awareness.......................................................................................347 ERPS.......................................................................................................348 Packet throughput booster ......................................................................348 AES .........................................................................................................348 XPIC ........................................................................................................348 High power (MPT-HLS - ETSI market only) ............................................348 L1 radio LAG with MSS-O .......................................................................348 5+0 L1 radio LAG ...................................................................................349 Number of interfaces able to work at 10 Gb/s .........................................349 1588 transparent clock ............................................................................349 Loopback .................................................................................................350 Core facing radio digital loopback ...........................................................350 Radio facing circuit loopback...................................................................351 Core facing RF loopback .........................................................................352 Core facing @RF - Internal loopback ......................................................352 Line facing PDH (DS1/DS3) loopback.....................................................353 Radio facing PDH (E1/DS1/DS3) loopback.............................................353 Line facing SDH (STM-1/OC-3) loopback ...............................................353 Core facing SDH (STM-1/OC-3) loopback ..............................................354 Loopback time-out ...................................................................................354 Loopback activation.................................................................................354 Network Communication .........................................................................355 Network management .............................................................................357 NE time....................................................................................................357 Non-administrator user ............................................................................358 Performance monitoring ..........................................................................358 Ethernet statistics ....................................................................................358 User Ethernet statistics............................................................................359 L1 Radio LAG Ethernet PM .....................................................................359 Compression gain statistics.....................................................................360 Radio Ethernet statistics..........................................................................362 Adaptive modulation PM..........................................................................363 Radio PM ................................................................................................363 Radio analog PM .....................................................................................363 Radio Ethernet PM ..................................................................................363 Radio hop PM..........................................................................................364 Radio link PM ..........................................................................................364 Radio QoS PM.........................................................................................364 Radio power level PM..............................................................................365 Radio RSL PM.........................................................................................366 PDH PM...................................................................................................367 SDH PM...................................................................................................368 RSL History .............................................................................................369 RSL History with Transmit Diversity Antenna..........................................370 Port segregation ......................................................................................370 Port segregation and frame duplication ..................................................371 TDM ports................................................................................................371 MPT access, P8ETH and EASv2 Ethernet ports ....................................372 MPT ODU number for each MPT plug in ................................................375

13


7.19.5 7.19.6 7.19.7 7.19.8 7.20 7.20.1 7.20.2 7.20.3 7.20.4 7.20.5 7.21 7.22 7.23 7.23.1 7.23.2 7.23.2.1 7.23.2.2 7.23.2.3 7.23.2.4 7.23.3 7.23.4 7.23.5 7.23.6 7.23.7 7.23.8 7.23.8.1 7.23.8.2 7.23.8.3 7.23.8.4 7.23.8.5 7.23.8.6 7.23.8.7 7.23.8.8 7.23.8.9 7.23.8.10 7.23.8.11 7.23.8.12 7.23.8.13 7.23.8.14 7.23.8.15 7.23.8.16 7.23.8.17 7.23.8.18 7.23.8.19 7.23.9 7.23.9.1 7.23.10

14

MPT ODU in protection ..........................................................................376 MPT ODUs protected on different plug-ins .............................................376 MPT ODUs protected on the same plug-in .............................................376 ERPS Ring ports .....................................................................................377 Remote inventory ....................................................................................377 User authentication..................................................................................377 User profile management ........................................................................377 SNMP operating mode (SNMPv3 support)..............................................378 SNMPv2 community string ......................................................................378 SSH and SFTP support ...........................................................................379 Software package rollback ......................................................................379 Stacking for EAS/EASv2/MPT access cards...........................................380 Synchronization .......................................................................................381 Sync switching.........................................................................................381 Master synchronization mode..................................................................382 E1/DS1 port .............................................................................................383 Synchronization input/output ports ..........................................................383 Synchronization status messaging ..........................................................383 SSM operation.........................................................................................384 Slave synchronization mode....................................................................385 Normal operation .....................................................................................388 Failed primary operation..........................................................................389 Wait-to-restore.........................................................................................389 Holdover ..................................................................................................389 Synchronization for PDH/SDH/DATA ......................................................389 Synchronization overview........................................................................389 Differential clock recovery .......................................................................391 Adaptive clock recovery...........................................................................391 SyncE ......................................................................................................392 Synchronization protection ......................................................................392 Synchronization quality level ...................................................................396 Quality level priority .................................................................................396 Hold-off and wait-to-restore .....................................................................397 Synchronization sources assignment ......................................................398 Synchronization sources assignment rules ............................................401 Allowed synchronization sources assignment ........................................401 Synchronization Source with EAS unit ....................................................402 QL and QL priority configuration .............................................................402 Synchronization source with MPT ...........................................................402 Synchronization source with MPT PFoE Access peripheral ...................403 Protected radio configuration with one MPT PFoE access peripheral.................................................................................................403 SSM Summary Table ..............................................................................403 Protected radio configuration with 2 MPT PFoE access peripheral .......404 Synchronization connection in stacking configuration with Core protection.................................................................................................404 Synchronization with MSS-1c..................................................................405 Synchronization overview for MSS-1c.....................................................405 IEEE 1588v2 PTP Transparent Clock .....................................................409


7.23.10.1 7.23.10.2 7.24 7.24.1 7.24.2 7.24.3 7.24.4 7.24.5 7.24.6 7.24.7 7.24.7.1 7.24.7.2 7.24.7.3 7.24.7.4 7.25 7.25.1 7.25.2 7.25.3 7.25.4 7.25.5 7.25.6 7.25.7 7.25.8 7.25.9 7.25.10 7.25.11 7.25.12 7.25.13 7.26 7.26.1 7.26.2 7.27 7.27.1 7.27.1.1 7.27.1.2 7.27.1.3 7.27.1.4 7.28 7.28.1 7.28.2 7.28.2.1 7.28.2.2 7.29 7.29.1 7.29.1.1 7.29.1.2 7.29.1.3 7.29.1.4

Transparent clock at the NE level............................................................411 Transparent clock across the radio hop ..................................................412 IP addressing...........................................................................................413 Local NE interface ...................................................................................413 IPv4 addressing for the local IP address .................................................413 IPv4 addressing for the TMN local Ethernet interface IP address...........414 Default IPv6 addresses ...........................................................................414 IPv6 addressing for the local IP address .................................................415 IPv6 addressing for the TMN local Ethernet interface IP address...........416 MPR-e standalone IP addresses.............................................................417 NE IP addresses......................................................................................417 TMN communication channels ................................................................417 TMN-RF...................................................................................................417 TMN In-Band ...........................................................................................418 Mgmt port interface..................................................................................418 ETH port 4 interface ................................................................................419 Typical interconnect/addressing method .................................................419 Network provisioning ...............................................................................421 Addressing examples ..............................................................................421 Assumptions ............................................................................................422 IP address assignments ..........................................................................422 Radio level subnet addressing ................................................................422 Example:..................................................................................................423 Larger subnet areas ................................................................................424 Future expansion.....................................................................................424 Addressing terminals ...............................................................................425 External LAN attached.............................................................................425 External LAN not attached.......................................................................425 Addressing back-to-back terminals, Other asynchronous radios, and repeaters .........................................................................................426 Preferred addressing method .................................................................426 Alternate addressing method...................................................................427 Network provisioning ...............................................................................428 Network provisioning example.................................................................428 NE-1 ........................................................................................................429 NE-2 ........................................................................................................433 NE-3 ........................................................................................................436 NE-4 ........................................................................................................439 TMN communication channels ...............................................................443 Port functions...........................................................................................444 NE TMN_RF port scenarios ....................................................................444 Open shortest path first (OSPF) ..............................................................447 Static routing............................................................................................448 Protection schemes .................................................................................448 Protection schemes with MPT-HL/MPT-HLC/MPT-HLS .........................448 RPS switching criteria..............................................................................450 EPS switching criteria..............................................................................451 HSB switching criteria..............................................................................451 TDA switching criteria..............................................................................451

15


7.29.2 7.29.2.1 7.29.2.2 7.29.2.3 7.29.2.4 7.29.3 7.29.3.1 7.29.3.2 7.29.3.3 7.29.3.4 7.29.3.5 7.29.3.6 7.30 7.30.1 7.30.2 7.30.3 7.30.3.1 7.30.3.2 7.30.4 7.30.4.1 7.30.4.2 7.30.4.3 7.30.4.4 7.30.5 7.30.5.1 7.30.5.2

Protection schemes with MPT ODU .......................................................452 Supported protection types:.....................................................................453 RPS switching criteria..............................................................................455 EPS switching criteria..............................................................................455 HSB switching criteria..............................................................................456 Core protection ........................................................................................456 User Ethernet interfaces protection ........................................................457 TMN local Ethernet interface protection .................................................457 External synchronization interface protection .........................................457 Node-timed PDH interface protection .....................................................458 Core protection restoration mode ...........................................................458 Core protection switching criteria ............................................................458 Automatic link discovery ..........................................................................459 LLDP overview ........................................................................................459 LLDP on MPR-e ......................................................................................460 Transmitting nearest bridge LLDPDUs....................................................460 Default parameter....................................................................................461 SNMP MIB management.........................................................................461 Receiving nearest bridge LLDPDUs........................................................461 Supported TLVs.......................................................................................462 MIB update scenarios..............................................................................462 Notifying the SNMP manager ..................................................................462 Number of supported neighbors at a time ...............................................463 Transparent relay of nearest non-TPMR bridge and Nearest customer bridge PDUs ............................................................................463 Automatic link discovery scenarios..........................................................463 Displaying Neighbors in the user interface ..............................................463

8

Cables ..........................................................................................465

8.1 8.1.1 8.1.2 8.1.2.1 8.1.2.2

MSS to Outdoor Unit interconnections ....................................................465 How to connect the MPT-HC/HC-HQAM to the station battery ...............465 MSS-4/8 to MPT-HC/HC-HQAM interconnection ....................................466 One cable, Data+DC (MPT Access unit to MPT-HC/HC-HQAM)............466 Two cables, Data and DC (MPT Access unit to MPT-HC/HCHQAM) ....................................................................................................467 Two cables, Data and DC (Core-E unit to MPT-HC/HC-HQAM).............467 One cable, Data+DC (Core-E unit to MPT-HC/HC-HQAM) ....................469 Two cables, Data and DC (CorEvo unit to MPT-HC/HC-HQAM) ............470 One cable, Data+DC (CorEvo unit to MPT-HC/HC-HQAM) ....................472 Two cables, Data and DC (EAS unit to MPT-HC/HC-HQAM) ................473 One cable, Data+DC (EASv2 unit to MPT-HC/HC-HQAM) .....................475 Two cables, Data and DC (EASv2 unit to MPT-HC/HC-HQAM) .............476 MSS to MPT-XP/XP-HQAM interconnection ...........................................477 One cable, Data+DC (MPT Access unit to MPT-XP/XP-HQAM) ............477 Two cables, Data+DC (MPT Access unit to MPT-XP/XP-HQAM)...........478 Two cables, Data and DC (Core-E unit to MPT-XP/XP-HQAM)..............479 One cable, Data+DC (Core-E unit to MPT-XP/XP-HQAM) .....................480 Two cables, Data and DC (CorEvo unit to MPT-XP/XP-HQAM) .............481 One cable, Data+DC (CorEvo unit to MPT-XP/XP-HQAM).....................482

8.1.2.3 8.1.2.4 8.1.2.5 8.1.2.6 8.1.2.7 8.1.2.8 8.1.2.9 8.1.3 8.1.3.1 8.1.3.2 8.1.3.3 8.1.3.4 8.1.3.5 8.1.3.6

16


8.1.3.7 8.1.3.8 8.1.4 8.1.4.1 8.1.4.2 8.1.4.3 8.1.4.4 8.1.5 8.1.5.1 8.1.5.2 8.1.5.3 8.1.5.4 8.1.5.5 8.1.5.6 8.1.5.7 8.1.5.8 8.1.6 8.1.6.1 8.1.6.2 8.1.6.3 8.1.7 8.1.7.1 8.1.7.2 8.1.8 8.1.8.1 8.1.8.2 8.1.9 8.1.10 8.1.10.1 8.1.10.2 8.1.11 8.1.12 8.1.13 8.2 8.2.1 8.2.2 8.2.3

Two cables, Data and DC (EAS or EASv2 unit to MPT-XP/XPHQAM).....................................................................................................483 One cable, Data+DC (EASv2 unit to MPT-XP) .......................................484 MSS-4/8 to MPT-MC interconnection......................................................485 One cable (MPT Access unit to MPT-MC) ..............................................485 One cable (CorEvo unit to MPT-MC).......................................................486 One cable (Core-E unit to MPT-MC) .......................................................488 One cable (EASv2 unit to MPT-MC)........................................................489 MSS-1 to MPT ODU interconnection.......................................................489 One cable, Data+DC (MSS-1 ports 1 and 2 to MPT-HC/HCHQAM).....................................................................................................490 One cable, Data+DC (MSS-1 ports 3 and 4 to MPT-HC/HCHQAM).....................................................................................................490 Two cables, Data and DC (MSS-1 ports 1 and 2 to MPT-HC/HCHQAM).....................................................................................................491 Two cables, Data and DC (MSS-1 ports 5 and 6 to MPT-HC/HCHQAM).....................................................................................................492 One cable, Data+DC (MSS-1 ports 1 to 4 to MPT-XP/XP-HQAM) .........492 Two cables, Data and DC (MSS-1 ports 5 and 6 to MPT-XP/XPHQAM).....................................................................................................493 One cable (MSS-1 ports 1 and 2 to MPT-MC) ........................................493 One cable (MSS-1 ports 3 and 4 to MPT-MC) ........................................493 MSS-O to MPT ODU interconnection......................................................494 One cable, Data+DC (MSS-O ports 1 to 3 to MPT-/HC/HCHQAM).....................................................................................................494 One cable (MSS-O ports 1 and 2 to MPT-MC)........................................495 One cable (MSS-O port 3 to MPT-MC) ...................................................495 MSS-1c to MPT-HC/HC-HQAM/9558HC interconnection .......................495 MSS-1c to MPT-HC/HC-HQAM/9558HC interconnection (one cable).......................................................................................................495 Optical cable............................................................................................496 MSS-1c to MPT-XP/XP-HQAM interconnection ......................................498 MSS-1c to MPT-XP/XP-HQAM interconnection (PFoE) .........................498 Optical cable............................................................................................498 MSS-1c to MPT-MC interconnection .......................................................500 MPT-MC/HC/HC-HQAM/9558HC connectivity for MPR-e (1+0 configuration)...........................................................................................500 Electrical interface ...................................................................................500 Optical interface.......................................................................................504 MPT-HC/HC-HQAM/9558HC connectivity for MPR-e (co-channel XPIC configuration) .................................................................................506 Connection to MPT Power Unit ...............................................................507 Connection to MPT Extended Power Unit ...............................................508 Cable length ............................................................................................509 Cable length with MSS-O ........................................................................510 Cable length with MPT Power Unit..........................................................514 Cable length with MPT Extended Power Unit..........................................515

17


9

Software and miscellaneous unit descriptions ......................517

10

Engineering specifications ........................................................523

10.1 10.2 10.3 10.4 10.5 10.5.1 10.5.2 10.5.3 10.6 10.6.1 10.6.2

Rack specifications..................................................................................523 Power specifications................................................................................523 Environmental specifications ...................................................................523 Radio profiles...........................................................................................523 Signal interface........................................................................................524 Signal cable connections.........................................................................524 DS1 interface...........................................................................................526 DS3 interface...........................................................................................526 Control interface ......................................................................................526 DS1 interface...........................................................................................527 DS3 interface...........................................................................................530

Graphical User Interface descriptions....................................................................... 535

18

11

WebEML craft terminal overview ..............................................537

11.1 11.2 11.2.1 11.2.2 11.2.2.1 11.2.2.2 11.2.2.3 11.2.3 11.2.4 11.2.5 11.3 11.3.1 11.3.2 11.3.3 11.3.4 11.3.5 11.3.6 11.3.7 11.3.8 11.3.9 11.3.10 11.3.11 11.3.11.1 11.3.11.2 11.3.11.3 11.4 11.4.1 11.4.2 11.4.2.1

Introduction..............................................................................................537 Network Element Overview .....................................................................537 Main view.................................................................................................537 NE Configuration area .............................................................................539 NE Information.........................................................................................539 NE Description.........................................................................................540 Command Buttons...................................................................................541 Status & Alarms area...............................................................................541 Supervision Function ...............................................................................543 Bar Menu .................................................................................................543 WebEML main view.................................................................................544 Main menu bar area ................................................................................548 Tab panels...............................................................................................549 Main toolbar area.....................................................................................551 Resource tree area..................................................................................552 Resource list area....................................................................................554 Resource detail area ...............................................................................554 Severity Alarm Synthesis area ................................................................555 Domain Alarm Synthesis area .................................................................556 Status Control area..................................................................................557 Scroll bar .................................................................................................559 Selection criteria ......................................................................................560 Single left click.........................................................................................560 Double-click .............................................................................................561 Button policy ............................................................................................561 PDH main view ........................................................................................561 General information .................................................................................561 Alarms & Settings ....................................................................................563 Alarms tab-panel .....................................................................................563


11.4.2.2 11.4.2.3 11.4.3 11.5 11.5.1 11.5.1.1 11.5.2 11.5.3 11.5.4 11.5.5 11.5.5.1 11.5.5.2 11.5.5.3 11.6 11.6.1 11.6.1.1 11.7 11.7.1 11.8 11.8.1 11.9 11.9.1 11.10 11.10.1 11.11 11.11.1 11.12 11.12.1 11.13 11.13.1 11.14 11.14.1 11.15 11.15.1 11.15.2 11.15.2.1 11.15.2.2 11.15.3 11.15.4 11.15.4.1 11.15.4.2 11.15.4.3 11.15.4.4 11.16 11.16.1 11.16.1.1 11.16.1.2

Settings tab-panel....................................................................................564 General information on Circuit Emulation................................................568 Loopback .................................................................................................569 SDH main view ........................................................................................571 General information on the SDH unit.......................................................571 Tab-panels...............................................................................................571 Alarms .....................................................................................................571 Settings for SDHACC unit (Transparent mode).......................................572 Loopback .................................................................................................572 Settings for SDHCHAN unit (Channelized mode - ETSI market only).........................................................................................................573 Signal Mode.............................................................................................575 Service Profile .........................................................................................575 Buttons ...................................................................................................575 EAS main view for P8ETH and EASv2....................................................576 EAS Domain ............................................................................................576 Ethernet Physical Interface......................................................................577 Ethernet Ring Configuration View ...........................................................585 General information .................................................................................585 LAG Configuration ...................................................................................586 General....................................................................................................586 QoS Configuration ...................................................................................587 General....................................................................................................587 EFM OAM Configuration .........................................................................589 General....................................................................................................589 AUX Cross Connections..........................................................................590 General....................................................................................................590 XPIC configuration...................................................................................591 General information .................................................................................591 VLAN management .................................................................................593 General information .................................................................................593 WT Performance Monitoring Suite ..........................................................595 General information .................................................................................595 Radio view ...............................................................................................595 General information on the Radio domain menu.....................................595 Power Source ..........................................................................................597 Mode 1 - QMA (only with MPT-HC/HC-HQAM on the MPT Access unit)..........................................................................................................601 Mode 2 - PFoE (Power Feed on Ethernet) ..............................................602 Alarms tab ...............................................................................................602 Configuration tabs ...................................................................................602 Settings....................................................................................................603 Additional Settings...................................................................................614 Maintenance ............................................................................................619 Measurement...........................................................................................624 CORE main view .....................................................................................629 General....................................................................................................629 Ethernet Physical Interface......................................................................630 TMN Interface..........................................................................................636

19


11.16.1.3 11.16.1.4 11.16.1.5 11.17 11.17.1 11.18 11.18.1 11.19 11.19.1 11.19.2 11.19.2.1 11.19.2.2

20

Settings tab-panel for TMN In-band .......................................................638 Settings tab-panel for TMN Ethernet Port #4 ..........................................640 MPT ODU connected to the Core ...........................................................641 MSS External Input Point view ...............................................................642 General....................................................................................................642 MSS A-FANS main view..........................................................................643 General....................................................................................................643 AUX view .................................................................................................643 Settings....................................................................................................644 External Points ........................................................................................645 Input External Points ...............................................................................645 Output External Points.............................................................................646

12

NEtO Servers Manager Tool overview ......................................649

12.1 12.1.1 12.1.2 12.1.3 12.1.4

NEtO Servers Manager Tool overview ....................................................649 Launch NEtO Servers Manager tool........................................................649 FTP/SFTP Servers ..................................................................................650 RMI Resource management....................................................................650 Close NEtO Servers Manager Tool .........................................................652

13

Summary Block Diagram overview...........................................653

13.1 13.2 13.3 13.4 13.5

Summary Block overview ........................................................................653 PDH unit secondary view ........................................................................656 SDH unit secondary view ........................................................................660 Radio secondary view (MPT ODU) .........................................................664 XPIC ........................................................................................................670

14

Performance Monitoring Suite overview ..................................673

14.1 14.1.1 14.1.2 14.1.3 14.1.4 14.1.5 14.1.6

Performance Monitoring Suite overview..................................................673 Start up the Performance Monitoring Suite .............................................673 PM Suite overview...................................................................................673 Toolbar area ............................................................................................675 View bar area ..........................................................................................675 Resource tree area..................................................................................676 Resource list area....................................................................................678

15

WT CLI tool overview .................................................................681

15.1 15.1.1 15.1.2 15.1.3 15.2 15.2.1 15.2.2 15.2.3 15.2.4 15.2.5 15.2.6 15.2.7

Introduction..............................................................................................681 Command conventions............................................................................681 Abbreviations...........................................................................................682 Help .........................................................................................................682 Ethernet Connectivity Fault Management CLI commands ......................682 CMD ID: ECFM_1 (MD CREATE) ...........................................................684 CMD ID: ECFM_2 (MD MIP CREATION CRITERIA)..............................685 CMD ID: ECFM_3 (MD DESTROY) ........................................................686 CMD ID: ECFM_4 (MA CREATE) ...........................................................686 CMD ID: ECFM_5 (MA MIP CREATION CRITERIA) ..............................688 CMD ID: ECFM_6 (CCM INTERVAL) .....................................................688 CMD ID: ECFM_7 (MA DESTROY) ........................................................689


15.2.8 15.2.9 15.2.10 15.2.11 15.2.12 15.2.13 15.2.14 15.2.14.1 15.2.15 15.2.15.1 15.2.16 15.2.16.1 15.2.16.2 15.2.17 15.2.17.1 15.2.17.2 15.2.18 15.2.18.1 15.2.19 15.2.19.1 15.2.20 15.2.20.1 15.2.21 15.2.21.1 15.2.22 15.2.23 15.2.24 15.3 15.3.1 15.3.1.1 15.3.1.2 15.3.2 15.3.2.1 15.3.2.2 15.3.3 15.3.3.1 15.3.3.2 15.3.3.3 15.3.4 15.3.4.1 15.3.4.2 15.3.4.3 15.4 15.4.1 15.4.2 15.4.3 15.4.4 15.5 15.6

CMD ID: ECFM_8 (MEP ASSIGN)..........................................................689 CMD ID: ECFM_9 (MEP REMOVE)........................................................689 CMD ID: ECFM_10 (MEP CREATE).......................................................690 CMD ID: ECFM_11 (MEP PRIORITY) ....................................................691 CMD ID: ECFM_12 (MEP ENABLE) .......................................................692 CMD ID: ECFM_13 (CCM ENABLE).......................................................692 CMD ID: ECFM_15 (LOOPBACK) ..........................................................693 WT CLI Tool Example for ECFM loopback count command ...................694 CMD ID: ECFM_16 (LINKTRACE) ..........................................................694 WT CLI Tool Example for ECFM linktrace count command ....................695 CMD ID: ECFM_17 (MD SHOW) ............................................................698 WT CLI Tool Example for ECFM md show command.............................699 WT CLI Tool Example for ECFM md show command.............................699 CMD ID: ECFM_18 (MA SHOW).............................................................700 WT CLI Tool Example for ECFM ma show command.............................700 WT CLI Tool Example for ECFM ma show command.............................700 CMD ID: ECFM_19 (SHOW MP LOCAL)................................................701 WT CLI Tool Example for ECFM ma show mp local command ..............702 CMD ID: ECFM_20 (SHOW MP REMOTE) ............................................702 WT CLI Tool Example for ECFM ma show mp remote command...........702 CMD ID: ECFM_21 (SHOW ERRORS)...................................................703 WT CLI Tool Example for ECFM ma show errors command ..................703 CMD ID: ECFM_22 (SHOW ERROR-LOG) ............................................704 WT CLI Tool Example for ECFM ma show error-log command ..............704 CMD ID: ECFM_23 (CLEAR CCM DATABASE).....................................704 CMD ID: ECFM_24 (CLEAR ERRORS)..................................................705 CMD ID: ECFM_25 (CLEAR ERROR-LOG) ...........................................705 Ethernet CFM scenarios..........................................................................705 Scenario1 ................................................................................................705 Network Element 1 ..................................................................................706 Network Element 2 ..................................................................................707 Scenario1 - removal procedure ...............................................................707 Network Element 1 ..................................................................................707 Network Element 2 ..................................................................................708 Scenario2 ................................................................................................708 Network Element 1 ..................................................................................709 Network Element 2 ..................................................................................710 Network Element 3 ..................................................................................711 Scenario2 - removal procedure ...............................................................712 Network Element 1 ..................................................................................712 Network Element 2 ..................................................................................712 Network Element 3 ..................................................................................713 Automatic MIP creation ...........................................................................713 Scenario 1 ...............................................................................................714 Scenario 2 ...............................................................................................715 Scenario 3 ...............................................................................................715 Scenario 4 ...............................................................................................716 Protocols..................................................................................................717 TACACS+ commands .............................................................................717

21


15.7

22

Example of a TACACS+ Management Session on the 9500MPR ..........720

16

Provisioning Tool overview .......................................................731

16.1 16.2 16.2.1 16.2.2 16.2.2.1 16.2.3 16.2.3.1 16.2.3.2 16.2.3.3 16.2.3.4 16.2.3.5 16.2.3.6 16.2.3.7 16.2.3.8 16.2.4 16.2.5 16.2.5.1 16.2.5.2 16.2.5.3 16.2.5.4 16.2.5.5 16.2.5.6 16.2.5.7 16.2.5.8 16.2.5.9 16.2.6 16.2.6.1 16.2.7 16.2.7.1 16.2.8 16.2.8.1 16.2.8.2 16.2.9 16.2.9.1 16.2.9.2 16.2.9.3 16.2.10 16.2.10.1 16.2.11 16.2.12 16.2.12.1 16.2.12.2 16.2.12.3 16.2.13 16.2.13.1 16.2.13.2

Overview..................................................................................................731 Provisioning tool screens.........................................................................731 MSS Configuration ..................................................................................732 Core Configuration ..................................................................................734 Synch-E ...................................................................................................735 Radio Configuration (ETSI market only)..................................................736 SSM ........................................................................................................736 TMN-RF in band management ...............................................................737 Revertive Restoration Criteria .................................................................737 Link Identifier ...........................................................................................737 Structure ..................................................................................................737 Operation with Fixed Modulation .............................................................738 Operation with Adaptive Modulation........................................................738 Channel area ...........................................................................................739 MPT Access peripheral configuration .....................................................741 MPT configuration ...................................................................................743 User label ................................................................................................744 SSM area.................................................................................................744 PPP RF in band management area.........................................................744 RPS Configuration...................................................................................744 Revertive Restoration Criteria area .........................................................744 XPIC Configuration..................................................................................745 Link Identifier area ...................................................................................745 Structure area..........................................................................................745 Channel area ...........................................................................................747 P32E1DS1 unit configuration for the ANSI market..................................751 DS1 parameters ......................................................................................752 P32E1DS1 unit configuration for the ETSI market ..................................754 E1 parameters .........................................................................................754 SDH unit configuration (ETSI market only)..............................................757 SDHACC Configuration ...........................................................................757 SDHCHAN Configuration ........................................................................758 EASv2 unit configuration .........................................................................760 Configure electrical ports.........................................................................760 Configure optical ports.............................................................................762 Two EASv2 units on the same row..........................................................764 LAG configuration....................................................................................765 LAG configuration procedure ..................................................................766 XPIC configuration...................................................................................767 Synchronization configuration .................................................................769 How to synchronize .................................................................................770 Synchronization Sources assignment .....................................................771 Synch-out port configuration....................................................................773 QoS configuration....................................................................................773 Scheduler Configuration screen ..............................................................774 Queue Size configuration screen ............................................................774


16.2.13.3 16.2.14 16.2.14.1 16.2.14.2 16.2.15 16.2.16 16.2.17 16.2.18

QoS Classification screen .......................................................................775 Bridge configuration.................................................................................779 802.1D .....................................................................................................780 802.1Q.....................................................................................................781 Port VLAN configuration ..........................................................................783 Network configuration..............................................................................785 Trusted managers ...................................................................................788 Final report ..............................................................................................789

17

Web Server overview..................................................................791

17.1 17.1.1 17.1.2 17.1.3 17.1.4

General....................................................................................................791 Configuration ...........................................................................................792 Alarms .....................................................................................................792 DHCP ......................................................................................................793 Administration..........................................................................................793

18

WebCT overview .........................................................................795

18.1

General....................................................................................................795

19

Microwave Craft Terminal overview..........................................799

19.1 19.2 19.3 19.4 19.5 19.6 19.7 19.8

Introduction..............................................................................................799 MCT start.................................................................................................799 MCT main view overview.........................................................................800 MCT toolbar.............................................................................................802 Alarm synthesis .......................................................................................803 Domain alarm synthesis area ..................................................................804 General information on the management state .......................................804 Navigator area .........................................................................................806

Hardware Unit Data Sheets.................................................................... 807 20

Rack and rack accessories unit data sheet .............................809

20.1 20.1.1 20.1.2 20.1.3 20.1.4

Rack descriptions ....................................................................................812 Standard rack or Laborack (19”) .............................................................812 Seismic 19” rack .....................................................................................814 ETSI (21”) rack ........................................................................................816 Outdoor cabinet ......................................................................................820

21

Cables unit data sheet................................................................821

22

MSS-8 microwave service switch shelf unit data sheet ..........839

22.1 22.2 22.3 22.4

Features and application notes ...............................................................841 Description...............................................................................................842 Equipment complement...........................................................................843 Functional overview.................................................................................852

23


23.1

Features and application notes ...............................................................855

23


23.2 23.3 23.4

24


24.1 24.2 24.3 24.4 24.5 24.5.1 24.6 24.7 24.8 24.9

Features and application notes ...............................................................866 Description...............................................................................................866 Functional overview.................................................................................867 Front panel connectors............................................................................867 Alarm and LED behavior .........................................................................873 LEDs........................................................................................................874 Output alarm electrical characteristics.....................................................875 Input alarm electrical characteristics .......................................................875 Power supply ...........................................................................................876 Environmental conditions ........................................................................876

25

MSS-1c unit data sheet ..............................................................877

25.1 25.1.1 25.1.2

Description...............................................................................................877 External user interface.............................................................................880 2 traffic 10/100/1000 Base-T Ethernet interfaces for data and service traffic via RJ45 connector............................................................880 Power supply ...........................................................................................880 Ethernet switch ........................................................................................881 E1/T1 interface ........................................................................................881 MPT interface ..........................................................................................882 Main functions .........................................................................................882 Ethernet user interface ............................................................................882 MSS-1c Fan unit......................................................................................883

25.1.3 25.1.4 25.1.5 25.1.6 25.1.6.1 25.1.7 25.2

24

Description...............................................................................................856 Equipment complement...........................................................................857 Functional overview.................................................................................862

26

MSS-O microwave service switch shelf unit data sheet .........885

26.1 26.2 26.3 26.4 26.5 26.5.1 26.6 26.7

Features and application notes ...............................................................885 Description...............................................................................................886 Functional overview.................................................................................886 Connectors ..............................................................................................887 Alarm and LED behavior .........................................................................888 LEDs........................................................................................................888 Power supply ...........................................................................................889 Environmental conditions ........................................................................889

27

Power distribution unit (PDU) unit data sheet .........................891

27.1 27.2 27.3 27.4

Features and application notes ...............................................................892 Description...............................................................................................892 Indicators, connectors, and control..........................................................893 Functional overview.................................................................................896

28

Microwave packet transport outdoor unit (MPT ODU) unit data sheet ............................................................................897

28.1

Description ..............................................................................................898


28.1.1 28.1.2 28.1.2.1 28.1.2.2 28.1.2.3 28.2 28.2.1 28.2.2 28.2.3 28.2.4 28.2.5 28.2.6 28.2.7 28.2.8 28.2.8.1 28.2.9 28.2.10 28.2.10.1 28.3 28.4 28.4.1 28.4.2 28.4.3 28.4.4 28.4.5

MPT-MC ..................................................................................................900 Features and application notes ...............................................................902 Compatibility between MPT-HC/XP and MPT-HC-HQAM/XPHQAM......................................................................................................903 Replacement of an MPT-HC/XP in 1+1 HSB/FD/SD configuration .........907 Replacement of an MPT-HC/XP/HC-HQAM/XP-HQAM in other configurations ..........................................................................................908 General characteristics............................................................................909 Common belt section...............................................................................909 Power supply interface ............................................................................909 Lightning protection .................................................................................910 Tx side .....................................................................................................910 Rx side.....................................................................................................911 Main functions .........................................................................................911 MPT ODU coupler ..................................................................................912 MPT ODU with external diplexer assembly .............................................912 External diplexer band-pass filters ..........................................................913 Labels affixed on the MPT ......................................................................914 Weatherproofing ......................................................................................916 Gaskets included with the MPT ...............................................................917 Grounding points for MPT-HC-HQAM and MPT-XP-HQAM ...................919 Operative information, views, and access points ....................................920 MPT-MC/HC/MPT-XP/9558HC with external diplexer ...........................920 MPT-MC/HC with embedded diplexer ....................................................922 MPT-XP with external diplexer ...............................................................924 MPT-HC-HQAM/XP-HQAM with external diplexer ..................................925 MPT-HC-HQAM with internal diplexer ....................................................926

29

MPT-HL microwave packet transport-long haul shelf unit data sheet ............................................................................929

29.1 29.2 29.3

Features and application notes ...............................................................930 Description...............................................................................................931 Equipment complement...........................................................................934

30

MPT-HL transceiver (ANSI market only) unit data sheet ........935

30.1 30.2 30.3 30.4

Features and application notes ...............................................................937 Description...............................................................................................937 Indicators, connectors, and control..........................................................938 Functional overview.................................................................................940

31

MPT-HLC transceiver (ANSI market only) unit data sheet ............................................................................................941

31.1 31.2 31.3 31.3.1 31.4

Features and application notes ...............................................................944 Description...............................................................................................945 Indicators, connectors, and control..........................................................945 RSSI monitoring point..............................................................................947 Functional overview.................................................................................948

25


26

32

MPT-HLS standard transceiver (ETSI market only) unit data sheet ....................................................................................949

32.1 32.1.1

MPT-HLS standard..................................................................................962 RSSI monitoring point..............................................................................966

33

MPT-HLS compact transceiver (ETSI market only) unit data sheet ....................................................................................967

33.1 33.1.1

MPT-HLS compact ..................................................................................979 RSSI monitoring point..............................................................................983

34

Fan cards unit data sheet ..........................................................985

34.1 34.2 34.3 34.4 34.5 34.6 34.7

Features and application notes ...............................................................985 Description...............................................................................................986 Indicators, connectors, and control..........................................................986 Functional overview.................................................................................989 Output alarm electrical characteristics.....................................................990 Input alarm electrical characteristics .......................................................990 Housekeeping for the Fan Evo (3EM23911BB) ......................................990

35

Core-E control and switching module unit data sheet............993

35.1 35.1.1 35.2 35.3 35.3.1 35.3.2 35.3.3 35.4

Description...............................................................................................993 Main functions .........................................................................................993 Features and application notes ...............................................................994 Description...............................................................................................995 Purpose and function...............................................................................995 Microprocessor ........................................................................................996 Options/configurations.............................................................................996 Indicators, connectors, and control..........................................................996

36

CorEvo control and switching module unit data sheet...........999

36.1 36.1.1 36.2 36.3 36.3.1 36.3.2 36.4

Description...............................................................................................999 Main functions .......................................................................................1000 Features and application notes .............................................................1000 Description.............................................................................................1002 Microprocessor ......................................................................................1002 Options/configurations...........................................................................1002 Indicators, connectors, and control........................................................1002

37

DS1 RJ-45 Patch Panel unit data sheet ..................................1005

37.1 37.2 37.3

Features and application notes .............................................................1005 Description.............................................................................................1005 Connectors ............................................................................................1006

38

DS1/MSS-1 d-connector patch panel unit data sheet............1009

38.1 38.2 38.3

Features and application notes .............................................................1009 Description.............................................................................................1009 Connectors ............................................................................................1010


39

P32E1DS1 PDH card unit data sheet ......................................1013

39.1 39.2 39.3 39.4 39.5

Description.............................................................................................1013 Features and application notes .............................................................1014 Description.............................................................................................1014 Indicators, connectors, and control........................................................1014 Functional overview...............................................................................1016

40

P2E3DS3 DS3 PDH card unit data sheet ................................1017

40.1 40.2 40.3 40.4 40.5

Description.............................................................................................1017 Features and application notes .............................................................1018 Description.............................................................................................1018 Indicators, connectors, and control........................................................1018 Functional overview...............................................................................1020

41

SDH card unit data sheet .........................................................1021

41.1 41.2 41.3 41.4

Description.............................................................................................1022 Features and application notes .............................................................1023 Indicators, connectors, and control........................................................1025 Functional overview...............................................................................1026

42

P8ETH Ethernet access switch card unit data sheet ............1027

42.1 42.2 42.3 42.4

Features and application notes .............................................................1027 Description.............................................................................................1027 Indicators, connectors, and control........................................................1028 Functional overview...............................................................................1030

43

EASv2 Ethernet access switch card unit data sheet.............1031

43.1 43.2 43.3

Features and application notes .............................................................1031 Description.............................................................................................1031 Indicators, connectors, and control........................................................1032

44

MPTACC MPT access card unit data sheet ............................1035

44.1 44.1.1 44.2 44.3

Description.............................................................................................1035 Main functions .......................................................................................1036 Features and application notes .............................................................1036 Indicators, connectors, and control........................................................1037

45

AUX auxiliary card unit data sheet..........................................1041

45.1 45.2 45.3 45.4 45.4.1 45.4.2 45.4.3 45.4.4

Features and application notes .............................................................1041 Description.............................................................................................1041 Indicators, connectors, and control........................................................1041 Functional overview...............................................................................1043 Housekeeping station alarm inputs .......................................................1043 Housekeeping station alarm input electrical characteristics ..................1044 Output alarm electrical characteristics...................................................1044 Synchronous 64 Kb/s RS422/V.11 DCE co-directional .........................1045

27


28

46

GigE and 10GigE SFP unit data sheet ....................................1047

46.1 46.2 46.3 46.4


47

Sync In/Out SFP unit data sheet .............................................1055

47.1 47.2 47.3 47.4


48

3 dB hybrid splitter unit data sheet.........................................1059

48.1 48.2

Description.............................................................................................1059 Connectors ............................................................................................1060

49

Coupler and OMT unit data sheet ...........................................1061

49.1 49.1.1 49.1.2 49.1.3

Description ............................................................................................1065 Couplers ................................................................................................1065 Ortho mode transducer..........................................................................1065 Ortho mode transducer-coupler.............................................................1066

50

Power injector unit data sheet.................................................1069

50.1 50.2 50.3 50.3.1 50.3.2

Features and application notes .............................................................1069 Description.............................................................................................1070 Indicators, connectors, and control........................................................1070 Power injector box .................................................................................1070 Power injector card................................................................................1071

51

+24/-48 volt converter unit data sheet ....................................1073

51.1 51.2 51.3

Features and application notes .............................................................1073 Description.............................................................................................1073 Indicators, connectors, and control........................................................1074

52

MPT Power Unit unit data sheet ..............................................1077

52.1 52.2 52.3 52.4 52.5 52.6 52.6.1 52.6.2 52.6.3 52.7 52.8

Features and application notes .............................................................1077 Description.............................................................................................1078 Lightning protection ...............................................................................1080 Hot swap function ..................................................................................1080 Operational environment requirements .................................................1081 Electrical overview.................................................................................1081 DC in interfaces .....................................................................................1081 DC out interfaces...................................................................................1081 Housekeeping interfaces .......................................................................1082 Indicators, connectors, and control........................................................1082 Mounting rack ........................................................................................1084


53

MPT Extended Power Unit unit data sheet .............................1085

53.1 53.2 53.2.1 53.3 53.3.1 53.3.2 53.4 53.4.1 53.4.1.1 53.4.1.2 53.4.1.3 53.4.1.4 53.5 53.6 53.7

Features and application notes .............................................................1085 Description.............................................................................................1086 Lightning Protection...............................................................................1088 EMI/EMC ...............................................................................................1089 Radiated Emission.................................................................................1089 Conducted Emission..............................................................................1089 Electrical overview.................................................................................1089 DC In interfaces.....................................................................................1089 DC Out interfaces ..................................................................................1090 RJ-45 connectors ..................................................................................1090 Housekeeping interface.........................................................................1090 Main Power Supply Unit ........................................................................1091 Indicators, connectors, and control........................................................1092 Alarm and LED behavior .......................................................................1093 Mounting rack ........................................................................................1093

54

Glossary ....................................................................................1095

29


30


List of Figures 2

Safety awareness..........................................................................65

Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12

Declaration of conformity for R7.x .............................................................66 Declaration of conformity for MPT-HLS.....................................................67 Declaration of conformity for 9600 LSY extended with MPT-HLS.............68 Dangerous voltage ....................................................................................70 Ground protection warning ........................................................................71 Risk of explosion .......................................................................................71 Openings must be covered........................................................................72 Moving mechanical parts...........................................................................72 Equipment connection to earth..................................................................73 Heat-radiating mechanical parts................................................................73 EMF emission warning ..............................................................................75 Compliance boundaries for 9500 MPR transceivers with 1ft (30 cm) antenna...............................................................................................75 EMC norms................................................................................................76 Electrostatic sensitive ................................................................................78 Electrostatic-sensitive sign ........................................................................79 Electrostatic protection kit..........................................................................80 Class 1 laser..............................................................................................82

Figure 13 Figure 14 Figure 15 Figure 16 Figure 17

3

9500 MPR general system description .......................................87


Multiservice aggregation layer...................................................................89 Service awareness ....................................................................................90 Packet node matrix....................................................................................90 Service-driven packet adaptive modulation...............................................91 9500 MPR configurations .........................................................................94

6

Equipment layout........................................................................125

Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 Figure 28 Figure 29 Figure 30 Figure 31 Figure 32 Figure 33

MSS-8 shelf, front view............................................................................128 MSS-4 shelf, front view............................................................................129 MSS-1......................................................................................................129 MSS-O.....................................................................................................130 MPT-HL/HLC shelf, front view .................................................................131 MPT-HLS shelf components....................................................................133 MPT-HLS shelf cover plates for empty slots ...........................................134 MPT-HLS compact indoor transceivers subshelf ....................................135 MPT-HLS compact branching drawer .....................................................135 MPT-HLS compact assembled on rack: example 1 ................................136 MPT-HLS compact assembled on rack: example 2 ................................136

7


Figure 34 Figure 35 Figure 36 Figure 37

Adjacent channels must be in alternate polarization ...............................144 ATPC with restriction ...............................................................................145 RTPC mode with four different frequencies.............................................145 Example of traffic 28MHz bandwidth and admission control ...................148

31


Figure 38 Figure 39 Figure 40 Figure 41 Figure 42 Figure 43 Figure 44 Figure 45 Figure 46 Figure 47 Figure 48 Figure 49 Figure 50 Figure 51 Figure 52 Figure 53 Figure 54 Figure 55 Figure 56 Figure 57 Figure 58 Figure 59 Figure 60 Figure 61 Figure 62 Figure 63 Figure 64 Figure 65 Figure 66 Figure 67 Figure 68 Figure 69 Figure 70 Figure 71 Figure 72 Figure 73 Figure 74 Figure 75 Figure 76 Figure 77 Figure 78

32

Example of traffic 28MHz bandwidth and modulation downgraded to 16QAM ................................................................................................149 Example of traffic 28MHz bandwidth and modulation downgraded to 4QAM ..................................................................................................149 Fiber-microwave protection .....................................................................151 Fiber-microwave protection - operation ...................................................152 Fiber-microwave protection on tail links ..................................................153 L1 LAG block diagram ............................................................................157 Types of L1 LAG Update .........................................................................158 Intra plug-in L1 link aggregation scenario................................................158 Single card 1+0 intra plug-in L1 LAG configurations .............................159 Dual card 1+0 intra plug-in L1 LAG configurations .................................159 Cross plug-in L1 link aggregation scenario ............................................160 1+0 cross plug-in L1 LAG configurations ................................................161 Protected 1+1 cross plug-in L1 link aggregation scenario ......................162 Protected 2x(1+1) cross plug-in L1 LAG configurations ..........................162 Mix 1+0 and 1+1 protected cross plug-in L1 LAG configurations............163 Protected 3x(1+1)/4x(1+1) cross plug-in L1 LAG configurations.............163 Radio L2 LAG ..........................................................................................192 Radio L2 LAG block diagram...................................................................193 Single 2+0 XPIC ......................................................................................199 Double 2x(1+1) HSB co-channel XPIC ...................................................200 Automatic remote TX mute......................................................................203 Automatic remote TX mute complete loop ..............................................204 Branching box block diagram ..................................................................207 Branching box band-pass detail ..............................................................207 MPT-MC ..................................................................................................209 MPT-HLS system ....................................................................................214 Frequency plan MPT-HL: 5.725 to 5.850 GHz unlicensed band (FCC Part 15 and IC RSS-210) ...............................................................221 Frequency plan 9558HLC: 5.725 to 5.850 GHz unlicensed band (FCC Part 15 and IC RSS-210) ...............................................................223 Frequency plan 9558HC: 5.725 to 5.850 GHz unlicensed band (FCC Part 15 and IC RSS-210) ...............................................................224 1+0 in split-mount configuration ..............................................................225 2x(1+0) repeater configuration ................................................................226 TDM over Ethernet packet node - mapping of E1/T1/DS1 TDM on Ethernet ...................................................................................................227 TDM and Ethernet terminal packet transport E1/T1/DS1 TDM and 1 radio direction .......................................................................................227 TDM and Ethernet terminal packet transport E1/T1/DS1 TDM and 2 radio directions -2x(1+0) repeater ........................................................228 QoS configuration....................................................................................236 QoS in the Core-E unit ...........................................................................245 QoS in the MPT ODU ..............................................................................249 QoS in the MSS-1c..................................................................................251 QoS in the MPT with MSS-1c..................................................................253 QoS in the MPT for MPR-e......................................................................254 Per-VLAN Per-COS rate limiters with duplicate PCP values...................261


Figure 79 Figure 80 Figure 81 Figure 82 Figure 83 Figure 84 Figure 85 Figure 86 Figure 87 Figure 88 Figure 89 Figure 90 Figure 91 Figure 92 Figure 93 Figure 94 Figure 95 Figure 96 Figure 97 Figure 98 Figure 99 Figure 100 Figure 101 Figure 102 Figure 103 Figure 104 Figure 105 Figure 106 Figure 107 Figure 108 Figure 109 Figure 110 Figure 111 Figure 112 Figure 113 Figure 114 Figure 115 Figure 116 Figure 117 Figure 118 Figure 119 Figure 120 Figure 121 Figure 122 Figure 123 Figure 124 Figure 125

Per-VLAN Per-CoS Rate Limiter and VLAN Rate Limiter with the same VLAN ID.........................................................................................262 Per-VLAN Per-CoS Rate Limiter with VLAN ID = Any and a VLAN Rate Limiter .............................................................................................262 Input/output flow control block diagram ...................................................266 Ethernet ring protection, normal operation ..............................................280 Ethernet ring protection, single link failure...............................................280 Two ERP instances, normal operation ....................................................283 Two ERP instances, single link failure.....................................................284 Ethernet L2 LAG block diagram example................................................286 Operational EFM OAM link......................................................................297 Remote OAM loopback ...........................................................................298 TDM2TDM flow diagram..........................................................................300 TDM2Eth flow diagram ............................................................................301 TDM to TDM STM-1 Flow Diagram .........................................................301 Eth to Eth flow diagram ...........................................................................302 Traffic profiles ..........................................................................................302 Traffic profiles ..........................................................................................304 TDM2TDM E1/DS1/DS3 traffic................................................................305 TDM2Eth E1/DS1/DS3 traffic ..................................................................306 SDH2SDH OC-3 traffic ............................................................................307 Eth2Eth E1/DS1/DS3 traffic.....................................................................308 Traffic profiles ..........................................................................................309 Traffic profiles ..........................................................................................310 E1 Traffic in TDM2TDM profile ................................................................311 E1 Traffic in TDM2Eth profile ..................................................................312 E1 Traffic in ETH2ETH (DATA) profile ....................................................313 MSS-8 shelf - front view ..........................................................................324 MSS-8 shelf, unprotected Core-E configuration ......................................325 MSS-8 shelf, protected Core-E configuration ..........................................325 MSS-4 shelf - front view ..........................................................................326 MSS-4 shelf, unprotected Core-E configuration ......................................326 MSS-4 shelf, protected Core-E configuration ..........................................326 MSS-1......................................................................................................327 Stacking configuration with 3 MSS-8, unprotected Core-E cards............328 Stacking configuration with 3 MSS-8, protected Core-E cards................328 Cross-connection.....................................................................................330 Ranging Sequential flow IDs ...................................................................337 Ranging Non-Sequential flow IDs............................................................338 Cross-connection.....................................................................................339 E1/T1 from/to radio port...........................................................................340 E1/T1 from/to Ethernet port .....................................................................340 Core and radio facing radio loopbacks ....................................................351 Port segregation with one MPT connected to the port ............................372 Port segregation scenario: MPT access..................................................373 Port segregation scenario: EASv2 cards ................................................374 Port segregation scenario: MPT access..................................................375 Synchronization block diagram................................................................382 Differential clock recovery .......................................................................391

33


Figure 126 Figure 127 Figure 128 Figure 129 Figure 130 Figure 131 Figure 132 Figure 133 Figure 134 Figure 135 Figure 136 Figure 137 Figure 138 Figure 139 Figure 140 Figure 141 Figure 142 Figure 143 Figure 144 Figure 145 Figure 146 Figure 147 Figure 148 Figure 149 Figure 150 Figure 151 Figure 152 Figure 153 Figure 154 Figure 155 Figure 156 Figure 157 Figure 158 Figure 159 Figure 160 Figure 161 Figure 162 Figure 163 Figure 164 Figure 165 Figure 166 Figure 167 Figure 168 Figure 169 Figure 170

34

Adaptive clock recovery...........................................................................391 Ring network with SSMs and port priorities normal situation ..................394 Ring network in restoration process - last node switched reference .......395 Ring network in restoration process - final situation ................................395 SSM Summary Table ..............................................................................404 Synchronization connection in stacking configuration with Core protection.................................................................................................405 Differential clock recovery .......................................................................406 Adaptive clock recovery...........................................................................407 PTP Slave Clock and Master Clock Synchronization Timing Computation ............................................................................................410 Typical interconnect/addressing method .................................................420 Typical interconnect/addressing method details continued .....................421 Typical terminal addressing.....................................................................424 Typical terminal attached to external LAN...............................................426 Back-to-back terminal and repeater configuration addressing ................427 Back-to-back terminal and repeater configuration addressing ................428 NE-1: NEtO logon window.......................................................................429 NE-1: Ethernet interface provisioning......................................................430 NE-1: Local configuration window ...........................................................430 NE-1: IP static routing configuration window ...........................................431 NE-1: OSPF area configuration...............................................................432 NE-1: IP routing configuration window ....................................................433 NE-2: NEtO logon window.......................................................................433 NE-2: TMN Ethernet interface window ....................................................434 NE-2: local configuration window ............................................................434 NE-2: OSPF area configuration...............................................................435 NE-2: IP routing information window .......................................................436 NE-3: NEtO logon window.......................................................................436 NE-3: TMN Ethernet interface provisioning .............................................437 NE-3: local configuration window ............................................................437 NE-3: OSPF area configuration...............................................................438 NE-3: IP routing information window .......................................................439 NE-4: NEtO logon window.......................................................................439 NE-4: TMN Ethernet interface provisioning .............................................440 NE-4: local configuration window ............................................................440 NE-4: IP static routing configuration window ...........................................441 NE-4: OSPF area configuration...............................................................442 NE-4: IP routing information window .......................................................443 NE TMN_RF port belongs to subnet 2 ....................................................445 NE TMN_RF port belongs to subnet 1 ....................................................446 NE TMN_RF port belongs to separate subnet 3 ....................................447 Transmit Diversity Antenna .....................................................................449 MPT-HL protection scheme block diagram .............................................450 MPT ODU protection schemes ...............................................................454 LLDP........................................................................................................460 Radio discovery protocol and Ethernet user interface LLDP...................463


8

Cables ..........................................................................................465


MPT-HC/HC-HQAM directly connected to the battery ............................465 MPTACC to MPT-HC/HC-HQAM interconnection ..................................466 MPTACC to MPT-HC/HC-HQAM interconnection (2 cables) .................467 Core-E to MPT-HC/HC-HQAM interconnection (2 cables) .....................468 Core-E connection to the MPT-HC/HC-HQAM through the Power Injector Box..............................................................................................469 Core-E connection to the MPT-HC/HC-HQAM through the Power Injector card ............................................................................................470 CorEvo to MPT-HC/HC-HQAM interconnection (2 cables) ....................471 CorEvo connection to the MPT-HC/HC-HQAM through the Power Injector Box..............................................................................................472 CorEvo connection to the MPT-HC/HC-HQAM through the Power Injector card ............................................................................................473 EAS to MPT-HC/HC-HQAM interconnection...........................................474 EASv2 to MPT-HC/HC-HQAM interconnection .......................................475 EASv2 to MPT-HC/HC-HQAM interconnection (2 cables) ......................476 MPT Access to MPT-XP/XP-HQAM interconnection (with MPT Extended Power Unit) .............................................................................478 MPT Access to MPT-XP/XP-HQAM interconnection with optical Ethernet cable (MPT Extended Power Unit) ...........................................479 Core-E to MPT-XP/XP-HQAM interconnection with optical Ethernet cable (MPT Extended Power Unit) ...........................................480 Core-E to MPT-XP/XP-HQAM interconnection with electrical Ethernet cable (MPT Extended Power Unit)............................................481 CorEvo to MPT-XP/XP-HQAM interconnection with optical Ethernet cable (MPT Extended Power Unit) ...........................................482 CorEvo to MPT-XP/XP-HQAM interconnection with electrical Ethernet cable (MPT Extended Power Unit)............................................483 EAS to MPT-XP/XP-HQAM interconnections (with MPT Extended Power Unit) .............................................................................................484 EASv2 to MPT-XP/XP-HQAM interconnection with electrical Ethernet cable (MPT Extended Power Unit)............................................485 MPTACC to MPT-MC interconnection.....................................................486 CorEvo to MPT-MC connection through the Power Injector Box ............486 CorEvo to MPT-MC connection through the Power Injector card............487 Core-E to MPT-MC connection through the Power Injector Box .............488 Core-E to MPT-MC connection through the Power Injector card ............488 EASv2 to MPT-MC interconnection ........................................................489 MPT-HC/HC-HQAM/9558HC connection ...............................................496 MPT-HC/HC-HQAM/9558HC connection (optical cable+power cable from MSS-1c).................................................................................497 MPT-HC/HC-HQAM/9558HC connection (optical cable+power cable from station battery) .......................................................................497 MPT-XP/XP-HQAM connection ..............................................................498 MPT-XP/XP-HQAM connection (optical cable from MSS-1c + (power supply cable from Extended Power Unit) ...................................499 MPT-MC connection................................................................................500

Figure 176 Figure 177 Figure 178 Figure 179 Figure 180 Figure 181 Figure 182 Figure 183 Figure 184 Figure 185 Figure 186 Figure 187 Figure 188 Figure 189 Figure 190 Figure 191 Figure 192 Figure 193 Figure 194 Figure 195 Figure 196 Figure 197 Figure 198 Figure 199 Figure 200 Figure 201 Figure 202

35


Figure 203 Figure 204 Figure 205 Figure 206 Figure 207 Figure 208 Figure 209 Figure 210 Figure 211 Figure 212 Figure 213 Figure 214 Figure 215

36

MPT-HC/HC-HQAM/9558HC connection through the Power Injector Box..............................................................................................501 MPT-XP/XP-HQAM/9558HC connection through the MPT Extended Power Unit ..............................................................................501 AC Power Converter................................................................................502 AC Power O-Ring Pigtail Cable Assembly ..............................................502 Modified AC Power O-Ring Pigtail Cable ................................................503 MPT-HC/HC-HQAM/9558HC connection (optical cable for traffic and coaxial cable to MPT Power Unit) ....................................................504 MPT-HC/HC-HQAM/9558HC connection (optical cable for traffic and coaxial cable to MPT Extended Power Unit) ....................................505 MPT-HC/HC-HQAM/9558HC connection (optical cable for traffic and coaxial cable for power supply) ........................................................505 MPT-HC/HC-HQAM/9558HC connection through the Power Injector Box (co-channel XPIC) ...............................................................506 MPT-HC/HC-HQAM/9558HC connection through the MPT extended power unit (co-channel XPIC)..................................................507 MPT-HC/HC-HQAM/9558HC connection (optical cable for traffic and coaxial cable to MPT Power Unit) ....................................................508 MPT-HC/HC-HQAM/9558HC connection (optical cable for traffic and coaxial cable to MPT Extended Power Unit) ....................................509 MPTACC to MPT-HC/HC-HQAM interconnection (2 cables) .................510

10


Figure 216 Figure 217 Figure 218 Figure 219 Figure 220 Figure 221 Figure 222 Figure 223 Figure 224

DS1 format template................................................................................528 DS1 input jitter accommodation...............................................................529 DS1 jitter transfer characteristics.............................................................529 DS1 jitter measurement filter characteristics ...........................................529 Asynchronous DS3 format template........................................................531 DS3 input jitter accommodation...............................................................532 DS3 jitter transfer characteristics.............................................................532 DS3 jitter measurement filter characteristics ...........................................532 Combined STS-1 and DS3 Format Template..........................................533

11


Figure 225 Figure 226 Figure 227 Figure 228 Figure 229 Figure 230 Figure 231 Figure 232 Figure 233 Figure 234 Figure 235 Figure 236 Figure 237 Figure 238

NEtO main view: initial screen.................................................................538 NEtO main view: reduced screen ............................................................539 NEtO NE Configuration View: NE Information.........................................540 NEtO NE Configuration View: NE Description.........................................540 NEtO NE Configuration View: Command Buttons...................................541 Main View: Status & Alarms ....................................................................542 New icon..................................................................................................544 Open icon ................................................................................................544 CS icon ....................................................................................................544 MSS-8 Main view ....................................................................................545 MSS-4 Main view ....................................................................................546 MSS-1 Main view.....................................................................................547 MSS-O Main view....................................................................................548 Main menu bar.........................................................................................549


Figure 239 Figure 240 Figure 241 Figure 242 Figure 243 Figure 244 Figure 245 Figure 246 Figure 247 Figure 248 Figure 249 Figure 250 Figure 251 Figure 252 Figure 253 Figure 254 Figure 255 Figure 256 Figure 257 Figure 258 Figure 259 Figure 260 Figure 261 Figure 262 Figure 263 Figure 264 Figure 265 Figure 266 Figure 267 Figure 268 Figure 269 Figure 270 Figure 271 Figure 272 Figure 273 Figure 274 Figure 275 Figure 276 Figure 277 Figure 278 Figure 279 Figure 280 Figure 281 Figure 282 Figure 283 Figure 284 Figure 285 Figure 286 Figure 287

Main toolbar area.....................................................................................551 Resource tree area..................................................................................553 Resource list area ...................................................................................554 Resource detail area ...............................................................................554 Severity Alarm Synthesis area ................................................................555 Domain Alarm Synthesis area .................................................................556 Status Control area..................................................................................557 Scroll bar .................................................................................................560 PDH main view (ETSI market shown) .....................................................562 Settings tab-panel....................................................................................564 E1 Loopbacks..........................................................................................570 Settings for SDHACC in transparent mode .............................................572 SDH Loopbacks.......................................................................................573 Settings for SDHCHAN in channelized mode..........................................574 EAS Main view for P8ETH.......................................................................577 EAS Main view for EASv2 .......................................................................578 Settings tab panel for EASv2 port#1 to port#4 ........................................579 Settings tab panel for EASv2 port#5 to port#8 ........................................581 Provider Bridge tab-panel........................................................................583 Policy & Translation tab-panel.................................................................584 Per-VLAN Per-CoS Rate Limiter tab-panel .............................................585 Ethernet Ring Configuration view ............................................................586 LAG configuration....................................................................................587 Scheduler Configuration ..........................................................................588 Queue Size Configuration .......................................................................588 QoS Classification ...................................................................................589 ETH OAM Configuration..........................................................................590 Auxiliary Cross Connections menu..........................................................591 XPIC Configuration view..........................................................................592 Settings tab with available XPIC..............................................................593 802.1D VLAN management.....................................................................594 802.1Q VLAN management (default VLAN only) ....................................594 802.1ad VLAN management with LAG....................................................595 Power Source for MPT Access unit.........................................................598 Power Source for MSS-1.........................................................................599 Power Source for MSS-O ........................................................................600 Power Source for EASv2.........................................................................601 Settings tab with fixed modulation (MPT-HC)..........................................603 Settings tab with fixed modulation (MPT-HQAM) ....................................604 Settings tab with adaptive modulation (MPT-HC)....................................605 Settings with adaptive modulation (MPT-HQAM) ....................................606 Settings tab with fixed modulation (MPT-MC) .........................................607 Settings tab with adaptive modulation (MPT-MC) ...................................608 Settings tab with fixed modulation (MPT-HL) ..........................................609 Settings tab with adaptive modulation (MPT-HL) ....................................610 Settings tab with fixed modulation (MPT-HLC)........................................611 Settings tab with adaptive modulation (MPT-HLC)..................................612 Settings tab with fixed modulation (MPT-HLS)........................................613 Settings tab with adaptive modulation (MPT-HLS)..................................614

37


Figure 288 Figure 289 Figure 290 Figure 291 Figure 292 Figure 293 Figure 294 Figure 295 Figure 296 Figure 297 Figure 298 Figure 299 Figure 300 Figure 301 Figure 302 Figure 303 Figure 304 Figure 305 Figure 306 Figure 307 Figure 308 Figure 309 Figure 310 Figure 311 Figure 312 Figure 313

38

Additional Settings tab (MPT-HC) ...........................................................615 Additional Settings tab (MPT-MC) ...........................................................616 Additional Settings tab (MPT-HL) ............................................................617 Additional Settings tab (MPT-HLC) .........................................................618 Additional settings tab (MPT-HLS) ..........................................................619 Maintenance tab (MPT-HC).....................................................................620 Maintenance tab (MPT-MC) ....................................................................621 Maintenance tab (MPT-HL) .....................................................................622 Maintenance tab (MPT-HLC)...................................................................623 Maintenance tab (MPT-HLS)...................................................................624 Core-E Main view ....................................................................................630 Core-E Main view (with optical SFP Ethernet port#5) .............................631 Settings tab-panel for SFP Ethernet ports...............................................632 Provider Bridge tab-panel........................................................................635 Policy & Translation tab-panel.................................................................635 Per-VLAN Per-CoS Rate Limiter tab-panel .............................................636 TMN Interface..........................................................................................637 TMN In-band Settings tab panel..............................................................638 Settings tab-panel for TMN Ethernet ports ..............................................639 Settings tab-panel for TMN Ethernet port #4...........................................640 MPT-HC example ....................................................................................641 MSS External Input Point Main View.......................................................642 MSS A-FANS Main View .........................................................................643 Settings tab-panel....................................................................................644 Input External Point View ........................................................................646 Output External Points View....................................................................647

12

NEtO Servers Manager Tool overview ......................................649

Figure 314 Figure 315 Figure 316 Figure 317 Figure 318 Figure 319

NEtO Servers Manager Tool ...................................................................649 Manage FTP/SFTP Servers ....................................................................650 RMI Resource counter — normal operation ............................................651 RMI Resource counter — abnormal operation ........................................651 RMI Registry Error dialog window ...........................................................651 NEtO Servers Manager — CLOSE error message .................................652

13

Summary Block Diagram overview...........................................653

Figure 320 Figure 321 Figure 322 Figure 323 Figure 324 Figure 325 Figure 326 Figure 327 Figure 328 Figure 329 Figure 330 Figure 331 Figure 332

Summary Block diagram view .................................................................653 Protected MPT-HL detail view .................................................................654 Loopback icons........................................................................................655 Performance Monitoring tool icons ..........................................................655 1+0 block diagram (E1 unit) (without Core-E protection) ........................657 1+0 block diagram (E1 unit) (with Core-E protection) .............................658 1+1 block diagram (PDH units) (without Core-E protection) ...................659 1+1 block diagram (PDH units) (with Core-E protection) ........................660 1+0 block diagram (SDH unit) (without Core protection) .........................661 1+0 block diagram (SDH unit) (with Core protection) .............................662 1+1 block diagram (SDH unit) (without Core protection) .........................663 1 1 block diagram (SDH unit) (with Core protection) ...............................664 1+0 block diagram (MPT-ACC unit) (without Core-E protection) ............665


Figure 333 Figure 334 Figure 335 Figure 336 Figure 337 Figure 338 Figure 339

1+0 block diagram (MPT-ACC unit) (with Core-E protection) .................666 1+1 FD block diagram (MPT-ACC units) (without Core-E protection)................................................................................................667 1+1 FD block diagram (MPT-ACC units) (with Core-E protection) ..........668 1+1 Hot Standby block diagram (MPT-ACC units) (without Core-E protection)................................................................................................669 1+1 Hot Standby block diagram (MPT-ACC units) (with Core-E protection)................................................................................................670 Co-channel XPIC.....................................................................................671 1+1 XPIC .................................................................................................672

14

Performance Monitoring Suite overview ..................................673

Figure 340 Figure 341 Figure 342 Figure 343 Figure 344 Figure 345 Figure 346 Figure 347 Figure 348

Performance Monitoring Suite main menu bar path ................................673 Performance Monitoring Suite icon .........................................................673 Performance Monitoring Suite main view ................................................674 Toolbar area ............................................................................................675 View bar area ..........................................................................................676 Resource tree area..................................................................................677 Resource list area: List View ...................................................................679 Resource list area: Overview...................................................................679 Resource list area: Bird’s Eye View.........................................................680

15



Port Mapping for Core-E based system ..................................................697 Port Mapping for CorEvo based system..................................................698 Port Mapping for MSS-O .........................................................................698 ECFM Scenario 1 ....................................................................................706 ECFM Scenario 2 ....................................................................................709 MIP creation scenario 1...........................................................................714 MIP creation scenario 2...........................................................................715 MIP creation scenario 3...........................................................................715 MIP creation scenario 4...........................................................................716 List of the available commands with the “help tacplus” command ..........720 Initial Settings: TACACS+ is disabled on all interfaces and there is no server configured................................................................................721 Provisioning server 1 (default settings but IP address) and showing the result..................................................................................................721 Provisioning server 1's key and showing the result .................................722 Performing a test (to check to server reachability and the server response time), then showing TACACS+ settings and status .................722 Provisioning server 2 (specifying secret key) and showing the result........................................................................................................723 Provisioning server 2’s port (such that the server will not be reachable) and showing the result, then performing a test......................724 Updating accounting packet size.............................................................724 Enabling TACACS+ Login for all management interfaces and showing settings and status (remark: server 2 is un-reachable) .............725 Enabling TACACS+ Accounting for all management interfaces and showing settings and status (remark: server 2 is un-reachable) .............726

Figure 360 Figure 361 Figure 362 Figure 363 Figure 364 Figure 365 Figure 366 Figure 367

39


Figure 368 Figure 369

Disabling TACACS+ Login for all management interfaces and showing settings and status (remark: server 2 is un-reachable) .............727 Enabling TACACS+ Login for SNMP management interfaces and showing settings and status (remark: server 2 is un-reachable), then performing a test......................................................................................728

16

Provisioning Tool overview .......................................................731


MSS Configuration screen example ........................................................733 Core Configuration screen example ........................................................736 MOD300 Configuration screen with fixed modulation .............................738 MOD300 configuration screen with adaptive modulation ........................739 ODU300 Channel Data Help window ......................................................740 MPTACC configuration with two units in the row.....................................742 1+1 configuration with MPTACC units.....................................................743 MPT configuration showing MPT-HQAM (1+0 with fixed modulation)..............................................................................................746 MPT configuration screen (1+0 with adaptive modulation) .....................747 Data Help window for the Channel area..................................................748 1+1 HSB Configuration............................................................................749 1+1 FD Configuration ..............................................................................750 DS1 configuration screen ........................................................................753 E1 configuration.......................................................................................756 SDHACC configuration screen ................................................................758 SDHCHAN configuration screen .............................................................759 EASv2 configuration screen: electrical ports ...........................................761 EASv2 configuration screen: optical ports...............................................763 EASv2 protection configuration ...............................................................764 EASv2 protection.....................................................................................765 LAG configuration screen ........................................................................766 XPIC configuration...................................................................................768 Polarization in the MPT Configuration screen .........................................769 Synchronization Configuration screen.....................................................770 Scheduler Configuration screen ..............................................................774 Queue size configuration screen .............................................................775 QoS classification screen ........................................................................776 IEEE 802.1p ...........................................................................................777 IEEE 802.1p classification change ..........................................................778 DiffServ....................................................................................................779 802.1D VLAN management.....................................................................781 802.1Q VLAN management (default VLAN only) ....................................782 Port VLAN configuration - Core-E ports ..................................................784 Port VLAN configuration - EASv2 ports...................................................785 Network configuration example ...............................................................786 Network Configuration screen .................................................................788 Trusted Managers screen........................................................................789 Configuration report ................................................................................790

Figure 378 Figure 379 Figure 380 Figure 381 Figure 382 Figure 383 Figure 384 Figure 385 Figure 386 Figure 387 Figure 388 Figure 389 Figure 390 Figure 391 Figure 392 Figure 393 Figure 394 Figure 395 Figure 396 Figure 397 Figure 398 Figure 399 Figure 400 Figure 401 Figure 402 Figure 403 Figure 404 Figure 405 Figure 406 Figure 407

40

17

Web Server overview..................................................................791

Figure 408

Web Server .............................................................................................792


18

WebCT overview .........................................................................795

Figure 409

WebCT (Administration & Networking domain shown)............................796

19

Microwave Craft Terminal overview..........................................799

Figure 410 Figure 411 Figure 412

Main view: system overview for MPR-e standalone ................................800 Main view: system overview for MSS-1c .................................................801 Main view: System overview with MPT-HC/MPT-XP with XPIC module.....................................................................................................802 Toolbar ....................................................................................................802 Radio synthesis tab .................................................................................804 Radio synthesis tab with XPIC configured...............................................805 Network supervision tab ..........................................................................805


20


Figure 417

Standard equal flange aluminum rack assembly (PN 694-9000006) .........................................................................................................813 Unequal flange seismic rack assembly (PN 1AD014120046) .................815 2200 mm ETSI rack (3CC50230AA) .......................................................817 2000 mm ETSI rack (3CC50231AA) .......................................................818 1700 mm ETSI rack (3CC50232AA) .......................................................819 1300 mm ETSI rack (3CC50192AA) .......................................................820


22



Microwave service switch (MSS-8) shelf .................................................842 MSS-8 shelf dimensions..........................................................................842 MSS-8 shelf slot definitions .....................................................................843 MSS-8 shelf, unprotected Core-E configuration ......................................845 MSS-8 shelf, protected Core-E configuration ..........................................846 MSS-8 stand-alone shelf, equipped with P32E1DS1 (DS1 Card) ...........846 MSS-8 stand-alone shelf, equipped with P2E3DS3 (DS3 Card) .............847 MSS-8 shelf, split mount, 1+0 drop and insert repeater configuration ............................................................................................848 MSS-8 shelf, split mount, 1+1 drop and insert repeater configuration ............................................................................................848 MSS-8 shelf, split mount MPT ODU, 1+0 12-way nodal junction configuration ............................................................................................849 MSS-8 shelf, all indoor mount, 1+1 4-way junction configuration............849 MSS-8 shelf, all indoor mount, 1+0 4-way junction configuration............850 MSS-8 shelf, all indoor mount, 1+1 4-way junction configuration............850 MSS-8 shelf, 1+0, 12 spoke hub configuration........................................851 MSS-8 shelf, 1+0, 12 spoke hub configuration........................................852

Figure 431 Figure 432 Figure 433 Figure 434 Figure 435 Figure 436 Figure 437

23



Microwave service switch (MSS-4) shelf .................................................857 MSS-4 shelf dimensions..........................................................................857 MSS-4 shelf slot definitions .....................................................................857 MSS-4 shelf, unprotected Core-E configuration ......................................859 MSS-4 shelf, protected Core-E configuration ..........................................859

41



24



Microwave service switch (MSS-1) shelf .................................................867 MSS-1 unit dimensions............................................................................867

25



MSS-1c front view ...................................................................................878 MSS-1c rear view ....................................................................................878 MSS-1c and Fan unit...............................................................................883

26


Figure 456

Microwave service switch (MSS-O) unit ..................................................886

27



Power distribution unit (PDU) isometric view...........................................893 Power distribution unit (PDU) front panel view ........................................893 PDU indicator and connector locations ...................................................894

28



MPT system.............................................................................................900 MPT-MC ..................................................................................................901 Supported configurations for MPT-HC/XP and MPTHC/HQAM/XP-HQAM together - 1+0, 1+1, and 2+0 XPIC......................905 Supported configurations for MPT-HC/XP and MPTHC/HQAM/XP-HQAM together - L1 LAG and RING ...............................906 Repair of a failed MPT-HC/XP in 1+1 HSB/FD/SD configuration ............908 MPT ODU with external diplexer assembly .............................................913 External Diplexer box band-pass detail ...................................................914 MPT-HC/XP ODU label ...........................................................................914 MPT-MC label.........................................................................................915 Label on MPT-HC-HQAM/XP-HQAM transceiver boxes.........................915 MPT-HC-HQAM with an external diplexer..............................................916 Round MPT ODU O-RING gasket...........................................................917 Spine MPT ODU O-RING gasket (red/black or blue/black) - color not contractual .........................................................................................918 Example of MPT ODU O-RING gasket installed ....................................919


42

MSS-4 stand-alone shelf, equipped with P32E1DS1 (DS1 card)............859 MSS-4 stand-alone shelf, equipped with P2E3DS3 (DS3 card)..............860 MSS-4 shelf, split mount using MPTACC, 1+0 2-way junction configuration ............................................................................................861 MSS-4 shelf, split mount using MPTACC, 1+1 2-way junction configuration ............................................................................................861 MSS-4 shelf, split mount using MPTACC, 1+0 4-way junction configuration ............................................................................................861 MSS-4 shelf, all indoor mount, 1+0 4-way junction configuration............862 MSS-4 shelf, all indoor mount, 1+1 4-way junction configuration............862 MSS-4 shelf, 1+0, 12 spoke hub configuration........................................862



Views of MPT-MC/HC/9558HC with external diplexer ...........................921 Views of MPT-HC with embedded diplexer ............................................923 Views of MPT-XP with external diplexer .................................................924 Low-frequency MPT-HC-HQAM/XP-HQAM with external diplexer ........925 High-frequency MPT-HC-HQAM with internal diplexer ..........................927

29



Microwave packet transport-long haul (MPT-HL/HLC) shelf ...................931 MPT-HL/HLC shelf dimensions ...............................................................932 MPT-HL/HLC shelf w/diplexer dimensions - top view..............................932 MPT-HL/HLC shelf w/one waveguide bracket dimensions - top view .........................................................................................................933 MPT-HL/HLC shelf w/two waveguide brackets dimensions - top view .........................................................................................................933

Figure 483

30


Figure 484

MPT-HL transceiver.................................................................................938

31


Figure 485

MPT-HLC transceiver .............................................................................945

32



MPT-HLS standard unit ...........................................................................963 MPT-HLS standard system .....................................................................963

33



MPT-HLS compact subshelf....................................................................980 MPT-HLS compact system......................................................................980

34



Fan 2U card w/alarms (front view)...........................................................987 Fan Evo card (front view) ........................................................................987

35


Figure 492

Core-E front panel details........................................................................997

36


Figure 493

CorEvo front panel details ....................................................................1003

37



DS1 RJ-45 patch panel (front view).......................................................1006 DS1 RJ-45 patch panel (rear view) .......................................................1006

43


44

38



DS1 RJ-45 patch panel (front view).......................................................1010 DS1 RJ-45 patch panel (rear view) .......................................................1010

39


Figure 498

P32E1DS1 card front panel view...........................................................1015

40


Figure 499

P2E3DS3 DS3 card (MSS/DS3) front panel view .................................1019

41


Figure 500

SDH card (MSS/SDH (OC-3/STM-1)) front panel view .........................1025

42


Figure 501

P8ETH card (MSS/P8ETH) ...................................................................1028

43


Figure 502

EASv2 card (MSS/EASv2) ....................................................................1032

44


Figure 503

MPTACC card (MSS/MPTACC) ............................................................1037

45



AUX card (MSS/AUX)............................................................................1042 Housekeeping alarm polarity .................................................................1044 64 Kb/s service channel DCE co-directional .........................................1045

46


Figure 507

Optical SFP module...............................................................................1052

47


Figure 508

Sync In/Out SFP....................................................................................1057

48


Figure 509

Hybrid splitter interconnect ....................................................................1059

49



OMT-C...................................................................................................1066 OMT-C...................................................................................................1067

50



Power injector box .................................................................................1071 Power injector box and bracket .............................................................1071 Power injector card................................................................................1072

51


Figure 515

+24/-48 volt converter card....................................................................1074


52



MPT power unit front panel view ...........................................................1078 MPT power unit upper view of box ........................................................1079 MPT power unit upper view of board.....................................................1080 MPT power unit mounting bracket.........................................................1084

53



MPT Extended Power Unit Front Panel View........................................1086 MPT Extended Power Unit Upper View of Box .....................................1087 MPT Extended Power Unit Upper View of Board ..................................1088 MPT Extended Power Unit mounting bracket........................................1094

45


46


List of Tables Preface

........................................................................................................55

Table 1 Table 2 Table 3

9500 MPR documentation .......................................................................55 9500 MPR related documentation ...........................................................57 Naming conventions ................................................................................59

5

Features.......................................................................................111

Table 4

Documentation for graphical user interfaces ........................................111

7


Table 5

Minimum Reference Modulation schemes supported for configurations with adjacent channels ....................................................146 Intra plug-in L1 LAG supported 1+0 configurations on EASv2 electrical ports: single LAG .....................................................................173 Intra plug-in L1 LAG supported 1+0 configurations on MSS-O electrical ports ........................................................................................174 Cross plug-in L1 LAG supported 1+0 configurations on EASv2 electrical ports: single LAG .....................................................................174 Intra plug-in L1 LAG supported 1+0 configurations on P8ETH optical ports: single LAG .........................................................................175 Intra plug-in L1 LAG supported 1+0 configurations on EASv2 optical ports: single LAG .........................................................................176 Cross plug-in L1 LAG supported 1+0 configurations on P8ETH optical ports: single LAG .........................................................................177 Cross plug-in L1 LAG supported 1+0 configurations on EASv2 optical ports: single LAG .........................................................................178 Cross plug-in L1 LAG supported 1+1 configurations on P8ETH optical ports: single L1 LAG ....................................................................179 Cross plug-in L1 LAG supported 1+1 configurations on EASv2 optical ports: single L1 LAG ....................................................................181 Dual L1 LAG Groups, Supported Mixed Plug-in 1+0 Configurations: .......................................................................................182 Cross plug-in L1 LAG supported 1+1 configurations: dual L1 LAGs .......................................................................................................187 Tx Mute characteristics ...........................................................................196 Lower 6 GHz 10 MHZ channel plan .......................................................210 Frequency plan for MPT-HLS (ETSI market) ........................................214 Unlicensed radio .....................................................................................219 5.8 GHz unlicensed antenna options ......................................................220 Actions taken for specific reserved multicast addresses ........................234 Default 802.1p QoS classification criteria to internal forwarding class .......................................................................................................239 Default DiffServ QoS classification criteria to internal forwarding class .......................................................................................................240 Default queue scheduling algorithm .......................................................243 L1 LAG with EASv2 queue weights ........................................................250

Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 Table 23 Table 24 Table 25 Table 26

47


Table 27 Table 28 Table 29 Table 30 Table 31 Table 32 Table 33 Table 34 Table 35 Table 36 Table 37 Table 38 Table 39 Table 40 Table 41 Table 42 Table 43 Table 44 Table 45 Table 46 Table 47 Table 48 Table 49 Table 50

8

Cables ..........................................................................................465

Table 51 Table 52 Table 53 Table 54 Table 55 Table 56

AC Power Converter features .................................................................502 AC Power Converter O-Ring Pigtail Cable features ...............................503 MSS-O cable length for the ETSI market (220V) .................................511 MSS-O cable length for the ANSI market (110V) .................................512 Maximum allowed cable lengths for MPT Power Unit ...........................514 Maximum allowed cable lengths for MPT Extended Power Unit ............515

9

Software and miscellaneous unit descriptions ......................517

Table 57

Software, RTU capacity license, and documentation unit descriptions ............................................................................................517 Miscellaneous unit descriptions ..............................................................522

Table 58

48

IEEE 802.1p classification ......................................................................252 DiffServ classification .............................................................................252 DWRR classification ...............................................................................253 QoS based on 802.1p priority .................................................................255 QoS based on DiffServ priority ...............................................................255 Default weights .......................................................................................256 Reserved multicast addresses ...............................................................267 MPT Types Supporting L1 LAG PTB .....................................................289 MSS backplanes compatible with EASv2 ...............................................320 Configurations ........................................................................................322 Port requirements for network protocols .................................................355 Radio PM default TCA threshold alarm values .......................................365 PDH PM default TCA threshold alarm values ........................................367 SDH PM default TCA threshold alarm values ........................................369 Releases supporting software package rollback ...................................380 Sync source selection details .................................................................384 Default quality level for Primary and Secondary Clock comparison .............................................................................................384 Synchronization clock sources available per clock role ..........................386 SSM quality levels ..................................................................................396 SSM quality levels ..................................................................................397 IEEE 1588v2 PTP Support per Platform ................................................411 IEEE 1588v2 PTP Support per Card .....................................................411 IEEE 1588v2 PTP Support per Radio ....................................................411 Commonly used subnet masks and associated subnet sizes ................423

10


Table 59 Table 60

DS1 interface specifications ...................................................................527 DS3 interface specifications ...................................................................530

11


Table 61

Status Control icon definitions ................................................................558


15


Table 62

WT CLI Tool, Ethernet Connectivity Fault Management commands ..............................................................................................683 Protocols commands ..............................................................................717 TACACS+ commands ............................................................................717

Table 63 Table 64

18

WebCT overview .........................................................................795

Table 65

WebCT menus overview .......................................................................796

20


Table 66 Table 67 Table 68 Table 69

Racks and rack accessories ..................................................................809 MPT-HLS subrack part numbers ...........................................................811 Standard equipment rack specifications .................................................814 Seismic equipment rack specifications ...................................................815

21

Cables unit data sheet................................................................821


Cable assemblies ...................................................................................821 Cords for 2xE1 SFP ................................................................................830 MPT-HLS cable codes ............................................................................831 Accessories and cables for MPT ODU connections ...............................832

22


Table 74 Table 75

MSS-8 microwave service switch shelf ..................................................839 MSS-8 shelf card complement ...............................................................843

23


Table 76 Table 77

MSS-4 microwave service switch shelf ..................................................855 MSS-4 shelf card complement ...............................................................858

24


Table 78 Table 79 Table 80 Table 81 Table 82 Table 83 Table 84 Table 85 Table 86

MSS-1 microwave service switch shelf ..................................................865 MSS-1 ports ............................................................................................868 MSS-1 pinout RJ-45 connector (NMS+Debug) ......................................869 68 pin SCSI cable input (RCV) pinout ....................................................870 68 pin SCSI cable output (XMT) pinout ..................................................871 MSS-1 house-keeping pinout (sub D15 female) .....................................872 Status LED behavior ...............................................................................874 MSS-1 office alarm and control connector / cable detail ........................874 Input alarm electrical behavior ................................................................875

25


Table 87

MSS-1c ...................................................................................................877

26



MSS-O microwave service switch shelf ..................................................885 MSS-O ports ...........................................................................................887 MSS-O pinout RJ-45 connector (PFoE) .................................................888 Status LED behavior ...............................................................................889

49


27


Table 92 Table 93

Power distribution unit (PDU) .................................................................891 PDU connector details ............................................................................894

28



Nose and nose adapter for MPT ODU ...................................................897 Flextwists for MPT ODU .........................................................................898 Supported configurations for MPT-HC/XP and MPT-HCHQAM/XP-HQAM together ....................................................................903 MPT ODU label details ...........................................................................915 MPT ODUs ...........................................................................................920 Back view locking hooks .........................................................................921 MPT ODU external interfaces .................................................................922 MPT ODU: RF interface waveguides .....................................................922 Back view locking hooks .........................................................................923 Legend for low-frequency MPT-HC-HQAM/XP-HQAM back view locking hooks ..........................................................................................925 Legend for MPT-HC-HQAM/XP-HQAM front and back view connectors ..............................................................................................926 Legend for high-frequency MPT-HC-HQAM with embedded diplexer (13-38 GHz) ..............................................................................927

Table 97 Table 98 Table 99 Table 100 Table 101 Table 102 Table 103 Table 104 Table 105

29


Table 106

MPT-HL microwave packet transport-long haul shelf and related kits .........................................................................................................929 Air filters .................................................................................................930

Table 107

50

30



MPT-HL transceiver ................................................................................935 MPT-HL transceiver front panel indicator details ....................................939 MPT-HL transceiver front panel connector details .................................940 MPT-HL transceiver front panel control details ......................................940

31



MPT-HLC transceiver .............................................................................941 MPT-HLC transceiver front panel indicator details .................................946 MPT-HLC transceiver front panel connector details ...............................947 MPT-HLC transceiver front panel control details ....................................947

32


Table 116 Table 117

MPT-HLS standard transceiver part numbers ........................................949 MPT-HLS unit front panel indicator details .............................................965


33


Table 118 Table 119

MPT-HLS compact transceiver part numbers ........................................967 MPT-HLS compact transceiver front panel indicator details ...................982

34


Table 120 Table 121

Fan cards ................................................................................................985 Enhanced FAN 2U w/alarms and Fan Evo (3EM23911AA and 3EM23911BB) front panel indicator details ............................................987 FAN 2U w/alarms and Fan Evo (3EM23911AA and 3EM23911BB) front panel connector details ..................................................................988 FAN 2U w/alarms (3EM23911AA) front panel control details .................988 Fan 2U card office alarm and control connector / cable detail ...............988 Input alarm electrical behavior ................................................................990 Housekeeping pin-out info for Fan Evo EM23911BB (Sub D 15 female) ....................................................................................................991

Table 122 Table 123 Table 124 Table 125 Table 126

35



Core-E control and switching module .....................................................993 Core-E front panel indicator details ........................................................997 Core-E front panel connector details ......................................................998

36



CorEvo control and switching module ....................................................999 CorEvo front panel indicator details ......................................................1003 CorEvo front panel connector details ...................................................1004

37



DS1 RJ-45 Patch Panel ........................................................................1005 P32E1DS1 DS1 card front panel connector details ..............................1006 MSS-1 front panel connector details ....................................................1007

38



DS1/MSS-1 d-connector patch panel ...................................................1009 P32E1DS1 DS1 card front panel connector details ..............................1010 MSS-1 front panel connector details ....................................................1011

39



P32E1DS1 PDH card ...........................................................................1013 P32E1DS1 card front panel indicator details ........................................1015 P32E1DS1 card front panel connector details ......................................1015

40



P2E3DS3 DS3 PDH card .....................................................................1017 P2E3DS3 DS3 card front panel indicator details ..................................1019 P2E3DS3 DS3 card front panel connector details ................................1019

51


41



SDHACC STM-1/OC-3 SDH card and SDH accessories .....................1021 SDH card front panel indicator details ..................................................1025 SDH card front panel connector details ................................................1025

42



P8ETH Ethernet access switch card ....................................................1027 P8ETH front panel indicator details ......................................................1028 P8ETH front panel connector details ....................................................1029

43



UDS-128 EASv2 Ethernet access switch card .....................................1031 EASv2 front panel indicator details .......................................................1033 EASv2 front panel connector details ....................................................1033

44



MPTACC MPT access card ..................................................................1035 MPTACC front panel indicator details ..................................................1038 MPTACC front panel connector details ................................................1039

45



AUX auxiliary card ................................................................................1041 AUX front panel indicator details ..........................................................1042 AUX front panel connector details ........................................................1043

46



GigE and 10GigE SFPs .......................................................................1047 SFP indicator details .............................................................................1052 SFP connector details ..........................................................................1053

47


Table 163 Table 164

Sync In/Out SFP ...................................................................................1055 Sync In/Out SFP pinout details .............................................................1055

48


Table 165 Table 166

3 dB hybrid splitter ................................................................................1059 Hybrid splitter connector detail .............................................................1060

49



MPT ODU couplers ..............................................................................1061 MPT ODU and coupler pole mounts ....................................................1063 MPT-HC/XP/HC-HQAM/XP-HQAM/9558HC 2x(1+0) XPIC Coupler (horizontal and vertical) ..........................................................1063 MPT-HC/XP/HC-HQAM/XP-HQAM/9558HC 4x(1+0) XPIC Coupler (2 horizontal and 2 vertical) ....................................................1063 OMTs ....................................................................................................1064 OMT-C ..................................................................................................1064 Loads for couplers, OMTs and OMT-Cs ...............................................1065


52


50



Power injector .......................................................................................1069 Power injector box connector details ....................................................1071 Power injector card indicator connector details ....................................1072

51



+24/-48 volt converter ...........................................................................1073 +24/-48 volt converter card indicator details .........................................1075 +24/-48 volt converter card connector details ......................................1075

52


Table 180 Table 181 Table 182 Table 183 Table 184 Table 185

MPT Power Unit ...................................................................................1077 MPT power unit electrical characteristics of DC in interfaces ...............1081 MPT power unit electrical characteristics of DC out interfaces ............1081 MPT power unit electrical connections of DC in interfaces ..................1082 MPT power unit electrical connections of DC out interfaces ................1083 MPT power unit electrical connections of housekeeping interfaces ..............................................................................................1083 DC output MPT ODU operation ranges ................................................1083

Table 186

53


Table 187 Table 188

MPT Extended Power Unit ...................................................................1085 MPT Extended Power Unit Electrical Characteristics of DC In Interfaces ..............................................................................................1089 MPT Extended Power Unit Electrical Characteristics of DC Out Interfaces ..............................................................................................1090 MPT Extended Power Unit Electrical Characteristics of dualstacked RJ-45 connectors ....................................................................1090 MPT Extended Power Unit Electrical Connections of housekeeping interface ........................................................................1091 MPT Extended Power Unit Main Power Supply Features ....................1091 MPT Extended Power Unit Electrical Connections of DC In Interfaces ..............................................................................................1092 MPT Extended Power Unit Electrical Connections of DC Out Interfaces ..............................................................................................1092 VDC Input Battery Operation Ranges ..................................................1093 DC output MPT ODU Operation Ranges ..............................................1093

Table 189 Table 190 Table 191 Table 192 Table 193 Table 194 Table 195 Table 196

53


54


Preface

Preface 9500 MPR documentation Table 1 describes the 9500 MPR documentation. See the current Release Notice for part numbers. Table 1

9500 MPR documentation

Document

Description

9500 MPR Product Information Manual

Provides a general description of the 9500 MPR product, solutions available, associated components, applications, and some Engineering specifications This guide replaces the following from previous releases: • ANSI Product Information • Product Information and Planning chapters from the ETSI MSS-1/4/8 User Manual and the MPR-e and MSS-1c User Manual

9500 MPR Hardware Installation and Replacement Manual

Provides detailed procedures for the initial installation of the radio and for replacement of hardware components This guide replaces the following from previous releases: • ANSI Installation Practices • Hardware sections of the Installation chapters from the ETSI MSS-O/1/4/8 User Manual and the MPR-e and MSS-1c User Manual • Hardware replacement procedures from ANSI Maintenance and Trouble Clearing

9500 MPR Software Installation and NE Upgrade Manual

Provides detailed procedures for the initial installation of the 9500 MPR software, software upgrade to the current release, and software rollback to a previous release This guide replaces the following from previous releases: • ANSI Software Installation and Upgrade • Software sections of the Installation chapters from the ETSI MSS-O/1/4/8 User Manual and the MPR-e and MSS-1c User Manual

55

Release 7.0.0 3DB 19383 ACAA Issue 01 Preface


Table 1

56

9500 MPR documentation (Continued)

Document

Description

9500 MPR WebCT User Manual

Provides procedures for performing system operations using the WebCT interface, including monitoring and maintenance activities. This guide describes, along with the WebEML User Guide, how to provision, operate, and monitor a shelf with a CorEvo card.

9500 MPR WebEML User Manual

Provides procedures for performing system operations using the WebEML interface, including: provisioning, performance monitoring, protection switching, and administration activities. This guide describes how to provision, operate, and monitor a radio in a split-mount configuration. This guide replaces the following from previous releases: • ANSI Operation and Administration • NE Management by Software Application chapter from the ETSI MSS-O/1/4/8 User Manual • Provisioning chapter from the ETSI MSS-1/4/8 User Manual

9500 MPR MCT User Manual

Provides procedures for performing system operations using the MCT interface, including: provisioning, performance monitoring, protection switching, and administration activities. This guide describes how to provision, operate, and monitor a radio in MPR-e or MSS-1c configuration. This guide replaces the following from previous releases: • NE Management by Software Application chapter from the MPR-e and MSS-1c User Manual • Provisioning chapter from the MPR-e and MSS-1c User Manual • Maintenance and Trouble Clearing chapter from the MPR-e and MSS-1c User Manual

9500 MPR MCT User Manual for Single NE Mode with 7705 SAR

Provides procedures for performing system operations using the MCT interface, including: provisioning, performance monitoring, protection switching, and administration activities. This guide describes how to provision, operate, and monitor a radio in Single NE mode with 7705 SAR.


Table 1

Preface

9500 MPR documentation (Continued)

Document

Description

9500 MPR Turn-up Manual

Provides procedures for system installation verification, provisioning, turn-up, and acceptance testing. The guide is to be used only during initial system turn-up. It is not intended to be used after equipment has been formally accepted (that is, for maintenance, system growth, system upgrade, or provisioning activities). This guide replaces the following from previous releases: • ANSI Turn-up • Lineup and Commissioning chapters from the ETSI MSS-O/1/4/8 User Manual and the MPR-e and MSS-1c User Manual

9500 MPR Alarm Clearing User Manual

Provides procedures related to the maintenance of the radio including how to clear alarms and abnormal conditions. This guide is intended to be used after the equipment has been installed and tested by the installation and test teams This guide replaces the following from previous releases: • ANSI Maintenance and Trouble Clearing • Maintenance and Trouble Clearing chapter from the ETSI MSS-O/1/4/8 User Manual

Related documentation Table 2 describes the 9500 MPR related documentation. See the Release Notice for part numbers. Table 2

9500 MPR related documentation

Guide

Description

9500 MPR-A Engineering Support Documentation

Provides engineering drawings for the 9500 MPR-A

57



Table 2

9500 MPR related documentation (Continued)

Guide

Description

9500 MPR Test Results Data Sheet

Provides space to record measurements, capture screen shots, capture photos, and record other information. TRDS tabs serve as records of completion of indicated steps in a Turn-up procedure. Not all procedures require entries in the TRDS.

9500 MPR Configuration File Management Manual

Provides information about using the configuration file.

9500 MPR Frequency Plan for MPT Outdoor Transceivers

Provides part number and tuning information for MPT-MC, HC, XP, HC-HQAM and XP-HQAM radios, for modules and for external diplexers.

9500 MPR Technical Specifications for Split Mount Applications

Provides technical specifications for MPT Outdoor transceivers, including general specifications such as dimensions, and radio specifications such as system gain or throughput, and transmit power specifications.

9500 MPR Technical Specifications for Full Indoor Applications

Provides technical specifications for MPT-HLC and HLS.

9500 MPR TMN Networking Guide

Describes TMN networking in the 9500 MPR.

9500 MPR Crossconnections Reference Tables

Provides information about supported cross-connections.

9500 MPR-A MPTHL Engineering Specifications

Provides transmit power specifications for legacy radios.

9500 MPR-A ODU300 Engineering Specifications

58


Preface

Naming conventions in the documentation The generic terms described in Table 3 are used when the topic applies to all of the related items listed. If the topic is specific to one or a subset of the items listed, the specific names will be stated in the guide. Table 3

Naming conventions

Term

Refers to

MPT-HC

MPT-HC V2

MPT ODU

• MPT-HC • MPT-XP • 9558HC* • MPT-MC • MPT-HC-HQAM • MPT-XP-HQAM *The 9558HC is an MPT-HC using the 5.8 GHz unlicensed band, for the ANSI market

MPT-HLS

MPT-HLS standard and MPT-HLS compact

MSS

MSS-1/4/8/O Note that the term MSS does not include the MSS-1c.

EAS

P8ETH and EASv2 cards

Core

Core-E and CorEvo cards MSS/CORE ports of MSS-O and MSS-1

CorEvo

CorEvo-1G and CorEvo-10G cards

PDH

E1, DS1, and DS3

SDH

STM-1 and OC-3

59



Audience This guide is intended for network installers and system administrators who are responsible for installing, configuring, or maintaining networks. This guide assumes you are familiar with electronic and networking technologies.

Information symbols Observe the warnings and notes to avoid injury or equipment damage during installation and maintenance. Follow the safety procedures and guidelines when working with and near electrical equipment. Warning statements and notes are provided in each chapter. The following symbols are contained in the 9500 MPR documentation. Danger: indicates that the described activity or situation may result in serious personal injury or death; for example, high voltage or electric shock hazards.

Warning: indicates that the described activity or situation may, or will, cause equipment damage or serious performance problems.

Caution: indicates that the described activity or situation may, or will, cause service interruption.

Note: provides information that is, or may be, of special interest.

60


Preface

Contact information Technical support If you purchased a service agreement for your 9500 MPR and related products from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller for assistance. If you purchased an Nokia service agreement, check this link for instructions to contact Support personnel: Web: http://support.alcatel-lucent.com

Documentation feedback If you have questions or comments about this documentation, please contact: [email protected]

61


62



FCC part 15 subpart B

1 FCC part 15 subpart B 1.1

9500 MPR-A unlicensed radio The JF6-9558H/6933B-9500MPT (MPT-HL) unlicensed radio provides fast deployment of service with microwave radio. No license and small antennas (no FCC and Industry Canada requirements) allow immediate turn-up. After the license is received, the unlicensed MPT-HL radio can be easily converted to the lower 6 GHz licensed band. The JF6-9558L/6933B-9558L and JF6-9558L-D/6933B-9558L-D (MPT-HLC) unlicensed radio provides fast deployment of service with microwave radio. No license and small antennas (no FCC and Industry Canada requirements) allow immediate turn-up. After the license is received, the unlicensed MPT-HLC radio can be easily converted to the lower 6 GHz licensed band. The JF6-9558HC/6933B-9558HC (9558HC) unlicensed radio provides fast deployment of service with microwave radio. No license and small antennas (no FCC and Industry Canada requirements) allow immediate turn-up. The 9558HC unlicensed radio cannot be upgraded to licensed operation. The JF6-9558H/6933B-9500MPT, JF6-9558HC/6933B-9558HC, JF6-9558L/6933B9558L and JF6-9558L-D/6933B-9558L-D unlicensed radio operates in the 57255850 Information, Scientific, and Medical (ISM) band in accordance with FCC Part 15.247 and IC RSS-210. This unlicensed radio, although operating in the same band as a spread spectrum radio, operates using narrower bandwidths than spread spectrum. The 9558HC 5.8 Unlicensed band (JF6-9558HC/6933B-9558HC) has been certified by the FCC and Industry Canada as of August 7, 2012.

1.2

FCC Class B compliance statement The JF6-9558H/6933B-9500MPT, JF6-9558HC/6933B-9558HC, JF6-9558L/6933B9558L, and JF6-9558L-D/6933B-9558L-D unlicensed radio have been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules and IC RSS-210. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a

63

Release 7.0.0 3DB 19383 ACAA Issue 01 FCC part 15 subpart B


commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.

1.3

FCC Class B requirements This device complies with part 15 of the FCC Rules and IC RSS-210. Operation is subject to the following three conditions: (1) this device may not cause harmful interference. (2) This device must accept any interference received, including interference that may cause undesired operation. (3) This device must be professionally installed. Cet appareil radio est conforme à IC RSS-210. Son fonctionnement respecte les trois conditions suivantes: 1) cette radio ne cause pas d’interférences néfastes, 2) cette radio peut recevoir des interférences, ainsi que des interférences qui peuvent causer des opérations non désirées, et 3) cette radio doit être installée par des Professionnels. Caution: Changes or modifications not expressly approved by Alcatel-Lucent could void the authority to operate the JF6-9558H/6933B-9500MPT, JF6-9558HC/6933B-9558HC, JF69558L/6933B-9558L, and JF6-9558L-D/6933B-9558L-D (unlicensed) radio.

Caution: Installation, Turn-Up, Maintenance, and Operation Instruction supplied with the JF6-9558H/6933B-9500MPT, JF6-9558HC/6933B-9558HC, JF6-9558L/6933B-9558L, and JF6-9558L-D/6933B-9558L-D (unlicensed) radio require strict adherence for continued part 15 of the FCC Rules and IC RSS-210 compliance.

Warning: Regulatory compliance warning: Physical changes or modifications to the JF6-9558H/6933B-9500MPT, JF6-9558HC/6933B-9558HC, JF6-9558L/6933B-9558L, and JF6-9558L-D/6933B-9558L-D (unlicensed) radio are strictly prohibited. Avertissement pour conformité réglementaire: changements physiques ou modifications sur les radios JF6-9558H/6933B-9500MPT, JF6-9558HC/6933B-9558HC, JF6-9558L/ 6933B-9558L, and JF6-9558L-D/6933B-9558L-D (sans licence) sont strictement interdit.

The MPT-HLC 5.8 Unlicensed band JF6-9558L/6933B-9558L and JF6-9558L-D/ 6933B-9558L-D is not available for quote, sale, or deployment until certification is received.

64


Safety awareness

2 Safety awareness 2.1

Safety EMC-EMF-ESD norms and equipment labeling This section 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. •

Declarations of conformity to CE marking and Countries List for the ETSI market

•

Safety rules

•

Electromagnetic compatibility (EMC norms)

•

Equipment protection against electrostatic discharges

•

Cautions to avoid equipment damage

65

Release 7.0.0 3DB 19383 ACAA Issue 01 Safety awareness

2.2


Declarations of conformity to CE marking and Countries List for the ETSI market Figure 1

66

Declaration of conformity for R7.x


Figure 2

Safety awareness

Declaration of conformity for MPT-HLS

67



Figure 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

2.3

Safety rules

2.3.1

General rules Before you perform any installation, turn-on, tests or operation and maintenance operations, carefully read the related sections of this manual, specifically:

68


2.3.1.1

Safety awareness

•

Hardware Installation

•

Commissioning

•

Maintenance and Upgrade

Observe safety rules

When equipment is operating, do not access the inside of the equipment parts which are protected with Cover Plate Shields removable with tools. If access is required to the equipment parts when it is operating, only service personnel, where service personnel or technical assistance is meant: •

“personnel which has adequate technical knowledge and experience necessary to be aware of the danger that may occur when performing an operation and of the necessary measurements to reduce the danger to a minimum for themselves and for others”.

•

The service personnel can only replace the faulty units with spare parts.

•

The service personnel is not allowed to repair, and therefore, the access to the parts that are not specified is not permitted.

•

The keys and/or the tools used to open doors, hinged covers to remove parts which provide access to compartments in which are present high dangerous voltages must belong exclusively to the service personnel.

For the cleaning of the external parts of the equipment, do not use any inflammable substance or substances which in some way may alter the markings, inscriptions, or other labels. 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; for example, do not expose persons, animals, things to the risk of being injured/damaged. When the safety protection features have been impaired, REMOVE POWER. To cut off power, switch off the power supply units and cut off the power station upstream (rack or station distribution frame). The safety rules described in this handbook are distinguished by the following symbol and statement:

69


2.4


Labels indicating Danger, Forbidding, Command Follow the instructions printed on the labels affixed to the units and assemblies. •

Dangerous electrical voltages

•

Risks of explosions

•

Moving mechanical parts

•

Equipment connection to earth

•

Heat-radiating mechanical parts

•

Microwave radiations (EMF norms)

•

Harmful optical signals

Pay attention to the information stated in the following, and proceed as instructed. The symbols presented in following paragraphs are all the possible symbols that could be present on Nokia equipment, but are not all necessarily present on the equipment this handbook refers to.

2.4.1 2.4.1.1

Dangerous electrical voltages Labeling: The warning label in Figure 4 is affixed next to dangerous voltages (>42.4 Vp; >60 Vdc).

Figure 4

Dangerous voltage

If it is a Class 1 equipment connected to mains, then the label in Figure 5 states that the equipment must be grounded before you connect it to the power supply voltage; for example:

70


Figure 5

Safety awareness

Ground protection warning

2.4.1.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: • •

2.4.2 2.4.2.1

Personal injury can be caused by -48VDC. Avoid touching powered terminals with any exposed part of your body. Short circuiting, low-voltage, low-impedance, DC circuits can cause severe arcing that can result in burns and/or eye damage. Remove rings, watches, and other metal jewelry before working with primary circuits. Exercise caution to avoid shorting power input terminals.

Risks of explosions Labeling: This risk is present when batteries are used, and it is signaled by the label in Figure 6:

Figure 6

Risk of explosion

71



2.4.2.2

Safety instructions:

Therefore, slits or apertures are made to let air circulate freely and allow dangerous gasses to down flow (battery-emitted hydrogen). A 417-IEC-5641 Norm. compliant label, as shown in Figure 7, is affixed next to it indicating that the openings must not be covered up. Figure 7

Openings must be covered

2.4.3


2.4.3.1

Labeling: The warning label in Figure 8 is affixed next to fans or other moving mechanical parts:

Figure 8


2.4.3.2


Before carrying out any maintenance operation see that all the moving mechanical parts have been stopped.

72


2.4.4

Safety awareness


2.4.4.1

Labeling: Terminals for equipment connection to earth, to be done according to international safety standards, are pointed out by the symbol in Figure 9.

Figure 9


2.4.4.2


The position of earth connection terminals is specified in the Hardware Installation section.

2.4.5 2.4.5.1

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

Figure 10

Heat-radiating mechanical parts

73



2.4.5.2


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.

2.4.6

Microwave radiations (EMF norms) Equipment emitting RF power (Reminder from site preparation procedure): The site must be compliant with ICNIRP guidelines or local regulation if more restrictive.

2.4.6.1


The following rules should be strictly applied by the 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.

Remind persons standing in front of the 9500 MPR antenna may cause traffic shutdown. Place the warning sticker, as shown in Figure 11, as follows:

74


Figure 11

Figure 12

Safety awareness

EMF emission warning

•

On the site when applicable (when people can cross the compliance boundaries and/or the transmission area of the antenna; for example, 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): EMF emission warning sign, placed on the antenna

Compliance boundaries for 9500 MPR transceivers with 1ft (30 cm) antenna

2.5

Electromagnetic compatibility (EMC norms) The equipment's EMC norms depend on the type of installation being carried out (such as cable termination or grounding) and on the operating conditions (such as, equipment, setting options of the electrical/elec tronic units, presence of dummy covers). Before you perform any installation, turn-on, tests & operation, and maintenance operations, carefully read the related sections of this manual. The norms set down to guarantee EMC compatibility, are distinguished inside this manual by the symbol and term:

75


Figure 13


EMC norms

1. EMC general norms - installation −

All connections (towards the external source of the equipment) made with shielded cables use only cables and connectors suggested in this manual or in the relevant Plant Documentation, or those specified in the Customer's “Installation Norms” (or similar documents)

−

Shielded cables must be suitably terminated

−

Install filters outside the equipment as required

−

Ground connect the equipment utilizing a conductor with correct diameter and impedance

−

Mount shields (if used), previously positioned during the installation phase, but not before having cleaned and degrease it.

−

Before you insert the shielded unit proceed to clean and degrease all peripheral surfaces (such as contact springs and connection points).

−

Screw fasten the units to the subrack.

−

To correctly install EMC compatible equipment follow the instructions given.

2. EMC general norms - turn-on, tests & operation −

Preset the electrical units as required to guarantee EMC compatibility

−

Check that the equipment is operating with all the shields correctly positioned (such as dummy covers and ESD connector protections).

−

To correctly use EMC compatible equipment, follow the provided information.

3. EMC general norms - maintenance

76

−

Before you insert the shielded unit, which replaces the faulty or modified unit, clean and degrease all peripheral surfaces (such as contact springs and connection points).

−

Clean the dummy covers of the spare units.

−

Screw fasten the units to the subrack.


2.5.1

Safety awareness

Cables: The following safety requirements apply to the cable connections for intra-building ports: •

To comply with the GR-1089-CORE requirements for electromagnetic compatibility and safety, all intra-building ports are specified for use with shielded and grounded at both ends.

•

The intra-building ports of the equipment or sub-assembly are suitable for connection to intra-building or unexposed wiring or cabling only. The intra-building ports of the equipment or sub-assembly must not be metallically connected to interfaces that connect to the OSP or its wiring. These interfaces are designed for use as intra-building interfaces only (Type 2 ports as described in GR-1089-CORE) and require isolation from the exposed OSP cabling. The addition of primary protectors is not sufficient protection in order to connect these interfaces metallically to OSP wiring.

Warning: 9500 MPR equipment must be connected to surge suppressors that meet the power surge requirements of GR-1089-CORE. Non-compliant surge suppressors may not have the required secondary surge protection or current limiting function during specific, valid operating states. Connecting 9500 MPR equipment to non-compliant surge suppressors could result in damage to 9500 MPR equipment.

2.6

Equipment protection against electrostatic discharges Before you remove the ESD protections from the monitors, connectors, or other equipment, observe the stated precautionary measures. Ensure that the ESD protections have been replaced and after terminating the maintenance and monitoring operations. Most electronic devices are sensitive to electrostatic discharges, therefore, the warning labels in Figure 14 have been affixed,

77


Figure 14


Electrostatic sensitive

Observe the stated precautionary measures when touching 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 and a coiled cord connected to the elasticized band and to the stud on the subrack. See Figure 16.

2.7 2.7.1

Cautions to avoid equipment damage Electrostatic-sensitivity An Electrostatic-Sensitive Device (ESD) can withstand voltage spikes of only 10 to 100 volts and can be damaged or effectively destroyed by a discharge that might go unnoticed by a technician. Some devices have built-in protection. However, because this protection is effective only against the lower levels of electrostatic charges, a false sense of security often prevails. Warning: Common plastic, white foam, cellophane, and masking adhesive tapes must not come in contact with ESDs or their packaging.

Common plastics (synthetic insulating materials), clothing, and paper or cardboard are the most common sources of static charges. Observe special precautions when the ESD sign is displayed. See Figure 15.

78


Figure 15

Safety awareness

Electrostatic-sensitive sign

The following items are examples of ESDs:

2.7.1.1

•

MOS (Metal Oxide Semiconductor) capacitors, transistors, Integrated Circuits (ICs)

•

CMOS (Complementary Metal Oxide Semiconductor) transistors, ICs

•

JFET (Junction Field Effect Transistors)

•

IGFET (Insulated Gate Field Effect Transistors)

Handling cards

Although the risk of damage to an ESD is reduced considerably after it is assembled into a circuit designed to protect sensitive components, take the following precautions to reduce static charges to harmless levels: •

Handle all cards as ESDs unless they are known not to contain electrostatic-sensitive parts.

•

Wear wrist ground strap, connected to grounded coiled cord before and while touching or handling cards containing ESS devices. See Figure 16 for an illustration of the wrist strap with cord. The wrist strap (PN 1AD 01247 0001) is an elasticized band connected to the coiled cord connected to the rack frame ground.

•

Store (even temporarily), pack, and ship cards in antistatic bags or containers.

•

Do not handle printed circuit board or components unnecessarily. Use plastic handle.

•

Do not use synthetic bristled brushes or acid brushes to clean cards.

•

Handle failed cards with same precautions as good cards.

ESD components are protected when correctly packaged in conductive or antistatic packaging. Acceptable packaging is marked as either conductive or antistatic.

79


Figure 16


Electrostatic protection kit

2.7.2

Screw fixing In normal operation conditions, all screws (such as for unit box closing and cable fixing) must be always tightened to avoid item detachment and to ensure the equipment EMI-EMC performance. •

•

2.7.2.1

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.

MSS-ODU cable disconnection / connection

To avoid equipment damage, always unplug the card first before you disconnect the MSS-ODU cable (at MSS or ODU side).

2.8

Fan, equipment rack, and equipment cabinet precautions When installing the equipment observe the following:

80


Safety awareness

Danger: •

•

•

2.9

Keep your fingers away from the rotating fan blades. Pull the fan-tray card by the thumbscrews only and wait for the fan blades to stop spinning before you attempt to remove the FAN card completely from the MSS-4/8 shelf. The 9500 MPR may require two people to support, align, and attach it to an equipment rack. To prevent equipment damage or personal injury, make sure you have enough help. To prevent personal injury and equipment damage due to unbalanced loading of the equipment rack or cabinet, make sure the equipment rack or cabinet is correctly secured to the floor, ceiling, or other rigid structure before mounting the 9500 MPR in it. For approved methods of securing the equipment rack, read the equipment-rack installation instructions or contact the equipment-rack manufacturer.

Electrical precautions Take appropriate safety precautions when you perform procedures on electrical equipment. Hazardous electrical potentials are present when system power is on. Some procedures in this manual require working with small conductive objects, such as screwdrivers, fuses, washers, screws, and nuts. When working on a shelf at the top of an equipment rack, a dropped object that falls into a lower shelf can cause physical damage and electrical short circuits. To prevent this, place a piece of paper or other cover over the lower shelf to catch fallen objects. Remove the paper or other cover when work is complete.

81



Danger: Remain aware of the following: •

•

•

• •

•

2.10

Install the 9500 MPR in a restricted-access area only. Entrance to a restricted-access area is intended for qualified or trained personnel and access to it is controlled by a locked barrier. The MSS-8 shelf does not contain main overcurrent protection devices. The user must provide circuit breakers or fuses and disconnects between the power source and the 9500 MPR. Each power feed from a source (-48 V dc and Return) requires a dc-rated fast-trip circuit breaker or fuse and disconnect. Circuit breakers or fuses must meet applicable local and national electrical safety codes and be approved for the intended application. Circuit breaker or fuse size is dependent upon site configuration. Refer to site engineering documentation for the correct Circuit breaker or fuse size. The MPT-HL shelf does not contain main overcurrent protection devices. The user must provide circuit breakers or fuses and disconnects between the power source and the 9500 MPR. Each power feed from a source (+ 24 V dc or- 48V dc and Return) requires a dc-rated fast-trip circuit breaker or fuse and disconnect. Circuit breakers or fuses must meet applicable local and national electrical safety codes and be approved for the intended application. Circuit breaker or fuse size is dependent upon site configuration. See the site engineering documentation for the correct Circuit breaker or fuse size. Make sure you connect the node to a + 24 V dc or - 48V dc source that is electrically isolated from the ac source and is reliably connected to earth ground. For personal safety, make sure you connect and secure the installation site’s frameground (earth ground) wire to the frame-ground terminal on the 9500 MPR before you connect any other wires to the node. A dc-power source provides high energy, which can cause serious injury or equipment damage. Only Alcatel-Lucent qualified personnel should connect the dc power to the 9500 MPR To prevent serious injury or equipment damage, make sure the power source cables are de-energized before you handle or connect them to the node.

Harmful optical signals

2.10.1

Laser precautions

The label in Figure 17 is applied when the equipment contains Class 1 laser components according to IEC 60825-1 (par. 5). Figure 17

82

Class 1 laser


Safety awareness

The laser source is placed in the optional SFP plug-in, which is installed in the Core-E card, P8ETH card, and EASv2 card. The laser source is placed in the left side of the SFP plug-in. Verify that laser labels on equipment state that the system conforms to all applicable standards of 21 CFR 1040.10. If there are no danger labels, call the Alcatel-Lucent Technical Support Center (TSC). The invisible infrared radiation emitted by the fiber-optic transmitter can cause eye damage. Observe local office procedures and the following dangers: Danger: • •

• • •

•

•

•

The use of controls and/or adjustments, or the performance of procedures other than those specified herein may result in hazardous infrared radiation exposure. Laser infrared radiation is not in the visible spectrum; therefore, it is not visible to the naked eye or with laser safety glasses. Although it cannot be seen, laser radiation may be present. Never look directly into an unterminated fiber-optic connector unless it is absolutely known that no optical power is being emitted by the connector. Never look into a broken optical fiber cable unless it is absolutely known that no laser radiation is present. Never look at an optical fiber splice, cable, or connector unless it is absolutely known that no laser radiation is present in the fiber. Laser radiation can come from a fiber-optic transmitter, an Optical Time Domain Reflectometer (OTDR), or other optical test equipment. Never look directly into an unterminated optical connector or cable with a magnifier/ microscope unless it is absolutely known that no laser radiation is being emitted from the connector or cable. A magnifier or microscope greatly increases the laser radiation hazard to the eyes. This system normally operates as a Class I Laser Product (no hazard). However, during servicing operations, when optical connectors are being connected, disconnected, or handled without dust covers, it is possible to be exposed to Class IIIb laser radiation, which can cause eye damage. Everyone within a 10 ft (3 m) radius of an unterminated optical fiber or connector that is connected to a powered transmitter must wear laser safety goggles or eye shields.

Laser safety goggles or eye shields are not required if the following work rules are strictly followed: 1. Always remove electrical power from fiber-optic transmitters before disconnecting fiber-optic connectors in the path between the transmitter and the receiver. 2. Never connect an unterminated optical cable to a fiber-optic transmitter. Always connect fiber-optic cables to fiber-optic receivers, test sets, or some other termination first.

83


84



Product and Solution descriptions

Product and Solution descriptions

•

9500 MPR general system description

•

System administration

•

Features

•

Equipment layout

•

Software and miscellaneous unit descriptions

•

Functional operation

•

Cables

•

Engineering specifications

85

Release 7.0.0 3DB 19383 ACAA Issue 01 Product and Solution descriptions

86




3 9500 MPR general system description 3.1

Introduction Nokia 9500 MPR Microwave Packet radio (9500 MPR) is a solution for smooth transformation of backhaul networks from TDM to IP. The Nokia 9500 MPR efficiently transports multimedia traffic by handling packets natively, while still supporting legacy TDM and ATM traffic. It also provides the quality of service needed to satisfy end-users. This solution improves packet aggregation, increases bandwidth and optimizes Ethernet connectivity. With the Nokia 9500 MPR the network can easily and efficiently absorb rapid growth in multimedia traffic, because it adapts the transmission of the packets to the air conditions and the quality required by the different types of services.

3.2

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 provides a generic, modular IP platform for multiple network applications (including 2G/3G/ HSDPA/WiMAX backhauling to Metro Ethernet areas) to accommodate broadband services. The 9500 MPR radio family supports low, medium, and high capacity applications using ANSI and ETSI data rates, frequencies, channel plans, and tributary interfaces. •

TDM/PDH/SDH Data Rates: −

ETSI market: E1, E3, STM-1

−

ANSI market: DS1, DS3 and OC-3

•

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

•

RF Frequency Range: 4 to 80 GHz

87

Release 7.0.0 3DB 19383 ACAA Issue 01 9500 MPR general system description


Most 9500 MPR equipment is available in both the ANSI and ETSI markets. The following equipment is available for one market only: •

•

3.3

ANSI: −

MPT-HL

−

MPT-HLC

ETSI: −

MPT-MC

−

MPT-HLS

Innovative solutions The 9500 MPR employs innovative solutions:

3.3.1

•

Multiservice aggregation layer: the capacity to use Ethernet as a common transmission layer to transport any kind of traffic, independently by the type of interface. Ethernet becomes the convergence layer.

•

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.

Multiservice aggregation layer 9500 MPR 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 such as quality of service. Mapping different access technologies over Ethernet is achieved by standardized protocols like circuit emulation and pseudo-wire.

88


Figure 18


Multiservice aggregation layer

3.3.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 of E1, DS1, DS3, STM-1, OC-3, and/or IP/Eth, coming from different sources, and therefore having different requirements. For instance DS1 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.

89


Figure 19


Service awareness

3.3.3

Packet node matrix 9500 MPR 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 Gb/ s).

Figure 20

90

Packet node matrix


3.3.4


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

Figure 21

Service-driven packet adaptive modulation

3.4

9500 MPR solutions The 9500 MPR hardware consists of Microwave Service Switch (MSS) units and radios. Note: The MOD300 card and ODU300 radio are supported but no longer documented. See documentation from R6.0.0 or earlier for ODU300 information.

The following types of MSS units are available: •

MSS-8: a 2U shelf, connected to an outdoor RF unit (split-mount system) Supported radios: −

MPT ODU

−

MPT-HL/HLC/HLS

91


•


MSS-4: a 1U shelf, connected to an outdoor RF unit (split-mount system) Supported radios:

•

−

MPT ODU

−

MPT-HL/HLC/HLS

MSS-1: a 1/2 U shelf, connected to an outdoor RF unit (split-mount system) Supported radios:

•

−

MPT-HC/HC-HQAM

−

9558HC (The 9558HC is an MPT-HC/XP using the 5.8 GHz unlicensed band, for the ANSI market)

−

MPT-MC

−

MPT-HLC/HLS

MSS-1c: a compact IDU that complements the existing portfolio, addressing the last mile, the far-end application in a nodal solution, and cost-optimized point-to-point applications. Its small size of 1U height and half-rack width drastically reduces the space consumption in busy sites. Supported radios:

•

−

MPT-HC/HC-HQAM

−


−

MPT-MC

MSS-O: an MSS unit optimized for outdoor use Supported radios: −

MPT-HC/HC-HQAM

−


−

MPT-MC

The MPT outdoor units can be deployed in a standalone configuration, or in a splitmount solution connected to any MSS IDU. The following Ethernet ports can be configured for MPT connection, in 1+0, 1+1 FD and 1+1 HSB:

92

•

Up to four MPT-HC can be connected to EASv2, through its optical interfaces

•

Up to four MPT-HC-HQAM can be connected to EASv2, through its optical interfaces

•

Up to four MPT-HLC/HLS can be connected to EASv2, through its optical interfaces


•


Up to four MPT-XP/XP-HQAM can be connected to EASv2, through its optical interfaces: these cannot be powered by EASv2 PfoE.

The following Ethernet ports can be configured for MPT connection in 1+0: •

Up to four MPT-MC can be connected to EASv2 4+4 version, through its electrical 10/100/1000 Base-T Ethernet interfaces

•

Up to four MPT-HC can be connected to EASv2 4+4 version, through its electrical 10/100/1000 Base-T Ethernet interfaces

•

Up to four MPT-HC-HQAM can be connected to EASv2 4+4 version, through its electrical 10/100/1000 Base-T Ethernet interfaces

•

Up to four MPT-XP/XP-HQAM can be connected to EASv2 4+4 version, through its electrical 10/100/1000 Base-T Ethernet interfaces: PfoE is not supported in this case.

Figure 22 shows the available configurations for the 9500 MPR family of products.

93


Figure 22


9500 MPR configurations

MPTxx

MSS-1/4/8

Mobile Antenna Eth TDM

NE: 9500 MPR

TDM Eth

MSS 1c

MPT-HL/HLC

NE: 9500 MPR MPTxx MPTxx Mobile Antenna Eth

MPTxx or ODU300 MSS-1

Eth

NE: 9500 MPR

NE: 9500 MPR-e Eth TDM

MPTxx

Mobile Antenna MSS-8

Mobile Antenna

NE: 9500 MPR

Eth TDM

Eth TDM Single NE with 7705 SAR

Eth TDM

Mobile Antenna

MPTxx

MPT-HLS compact


MSS-4 MPT-HLS standard

NE: 9500 MPR

MSS-1/4/8

MPTxx


MSS-O

Eth TDM MSS-1/4/8

NE: 9500 MPR

NE: 9500 MPR No3019

94



The following types of installation are available:

3.4.1

•

split-mount

•

MPR-e

•

MSS-1c

Split-mount installation A split-mount installation consists of a transceiver and an MSS unit. The installation can be all-indoor, with an indoor MSS unit and an MPT-HL, HLC, or HLS radio, indoor-outdoor with an indoor MSS unit and an MPT ODU, or all-outdoor, with an outdoor MSS-O and an MPT ODU.

3.4.1.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 MPTHLS radio is available in two variants: standard and compact. The following configurations are supported at system level: •

Split mount configurations: in this release the transceiver is available connected to an MSS. The maximum configuration is 20 MPT-HLS standard units or four MPT-HLS compact units 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 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.

95


3.4.1.2


The MSS-1c The MSS-1c uses its Ethernet interface to connect to the following Outdoor Units: •

in the ETSI market —MPT-HC, MPT-HC-HQAM, or MPT-MC

•

in the ANSI market-—MPT-HC, MPT-HC-HQAM, or 9558HC

The MSS-1c can collect up to 10 or 16 TDM flows and Ethernet flows. The implemented radio configuration is 1+0. The ODUs are in a charge of transporting the flows in an efficient way to ensure bandwidth optimization, Quality of service, and TDM constraints.

96


3.4.2


MPR-e The MPR-e product consists of a standalone full outdoor Network Element connected to a Ethernet generic device. The MPR-e system consists of the following ODUs: •

MPT-HC

•

MPT-HC-HQAM

•

MPT-XP

•

MPT-XP-HQAM

•

MPT-MC (ETSI market only)

The ODUs, except the XP variants, are connected to an Ethernet generic device. The Ethernet generic device implements L2/L3 functionalities. The Ethernet Generic Device is a device with the prerequisites listed in MPR-e prerequisites.

3.5

9500 MPR family overview The 9500 MPR offers compact IDU solutions for E1/DS1 and Ethernet hybrid connectivity and a zero footprint solution (no IDU) addressing full out-door applications. The Microwave Packet Tranceiver Outdoor Units (MPT ODU) and the indoor radios, the MPT-HL, MPT-HLC and MPT-HLS, address any application in the microwave domain, including stand-alone and split mount applications depending on the network requirement and layout. The MPT ODU transceivers support a variety of configurations to address mobile packet radio network requirements in the most cost-effective manner. The Microwave Service Switch shelf (MSS) and MSS-1c provide baseband processing and tributary interfaces as well as supervision. The P8ETH Ethernet Access Switch card and the MPT-HC/XP/HC-HQAM/XPHQAM/9558HC, MPT-HL and MPT-HLC transceivers provide radio function from 4 GHz to 11 GHz. The EASv2 Ethernet Access Switch card and the MPT ODU, or MPT-HL/HLC/HLS transceivers provide radio function from 4 GHz to 38 GHz.

97



The MPTACC MPT Access card and MPT ODU transceiver provides radio function from 6 GHz to 38 GHz. The MPT-HC/HC-HQAM transceiver supports direct connection to the Core, P8ETH, and EASv2 electrical and optical Ethernet ports. The MPT-HC/XP/HC-HQAM/XP-HQAM/9558HC transceiver supports direct connection to the P8ETH and EASv2 optical Ethernet ports. The 9500 MPR replaces the traditional terminal or single-link based approach to networking with a nodal solution. The MPT ODU supports up to twelve RF links for operation on the same or different frequency bands. An MPT ODU for each link is connected to a plug-in card inside the MSS-1/4/8 shelf. The following units support connection to MPT ODU transceivers: •

Core: supports up to six MPT ODU transceivers

•

P8ETH: supports up to three MPT ODU transceivers

•

EASv2: supports up to eight MPT ODU transceivers

•

MPTACC: supports up to two MPT ODU transceivers

An MPT Extended Power Unit is required to power an MPT-XP or MPT-XP-HQAM transceiver. Four MPT-HL shelves support up to eight RF links for operation on the same or different frequency bands. An MPT-HL or MPT-HLC Transceiver card in the MPT-HL shelf for each link is connected to an MSS-1 or a Core or EAS card inside the MSS-4/ 8 shelf. A mixture of radio transceiver technologies supports up to a maximum of eighteen radio interfaces. Other plug-in cards provide line interface access and management. Supports a mix of non-protected and protected or diversity operation for single link, repeater, nodal or hub radio configurations. System control and synchronization is provided by the Enhanced Control and Switching Module (Core) card.

3.6

Standards The following is a partial list of the standards that have influenced certain behavioral aspects of the 9500 MPR:

98



•

21 CFR PART 1040.10 and 1040.11

•

AF-PHY-0064.000

•

AF-PHY-0086.000

•

AF-TM-0121.000

•

AF-TM-0150.000

•

ANSI Z136.2

•

ATIS 0600315

•

Banned substances list

•

CENELEC EN 61000-3-2

•


•


•

CENELEC EN 50383

•


•

CENELEC EN 60215

•

CISPR/I/105/CDV-CISPR/I/29/CD-CISPR/I/106/CDV

•

CISPR 16-1-1

•

CISPR 16-1-2

•

CISPR 16-1-4

•

CISPR 16-2-1

•

CISPR 16-2-3

•

CISPR 16-2-4

•

CISPR 16-4-2

•

CISPR 22

•

CSA-C22.2 No 60950

•

EC RoHS Directive 2002/95/EU, compliance with

•

EC WEEE Directive 2002/96/EU, compliance with

•

EN 301 751

•

EN 50 385

•

EN 50 383

•

ETSI and RTTE directive: health and safety

•

ETSI and RTTE directive: electromagnetic compatibility

•

ETSI and RTTE directive: ETSI standard

•

ETSI and RTTE directive: EN 302 217

•

ETSI standards: Transmitter requirements

•

ETSI standards: Receiving requirements

99


100


•

ETSI standards: Note

•

ETSI EN 302 217 - Parts 1,2,3,4: Fixed Radio Systems; Characteristics and requirements for the use of equipment and antennas in system point-to-point

•

ETSI TR 101 506: Fixed Radio Systems; basic definitions, terminology and applicability of the essential requirements given in Article 3.2 Directive 1999/ 05/EC on the fixed radio systems

•

ETSI TR 101 036: Fixed Radio Systems; basic definitions for standards relating to digital fixed radio systems (DFRS)

•

ETSI TR 102 243: Fixed Radio Systems; Representative values for the transmitter power and antenna gain for the analysis of inter-and intracompatibility and sharing

•

ETSI EG 201 399: Electromagnetic compatibility and ERM; Guidelines for the preparation of harmonized standards for application under the R & TTE Directive

•

ETSI EN 300 019: Environmental Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment. Part 1-2-3

•

ETSI EN 301 126-1: Fixed Radio Systems; Conformance testing; Part 1: Point-to-Point equipment - Definitions, general requirements and test procedures

•

ETSI EN 301 126-3-1: Fixed Radio Systems; Conformance testing; Part 3-1: Point-to-Point antennas; Definitions, general requirements and test procedures

•

ETSI EN 302 217-1 to 4

•

ETSI EN 301 489

•

ETSI EN 300 753

•

ETSI EN 300 119

•

ETSI EN 300 132-2

•

ETSI EN 300 132-3

•

ETSI EN 300 253

•

ETSI EN 300 386

•

ETSI EN 301 489-1 and -4

•

ETSI EN 300 462-3-1 V1.1.1 (1998-05)

•

ETSI EN 55022

•

EU Directive EuP Directive 92/42/EEC, Compliance with proposal

•

Directive 1999/5/EC of the European Parliament and of the Council of 9 March 1999 on radio equipment and telecommunications terminal equipment and the mutual recognition of their conformity (R&TTE Directive).



•

ERC/REC 14-03 E: Harmonized arrangement of channels and blocks designed for low and medium capacity in the band of 3400-3600 MHz

•

ERC/REC 12-08 E: Harmonized arrangement of channels and blocks designed for systems of small, medium and large capacity in the band of 3600-4200 MHz

•

ERC/REC 14-01 E: Distribution of radio frequency channels for analog and digital radio relay systems in large capacity the band 5925-6425 MHz

•

ERC/REC 14-02 E: Distribution of radio frequency channels of digital systems is large, medium and small capacity in fixed service in the band of 6425-7125 MHz

•

ECC/REC/(02)06: Distribution of channels for digital systems in the fixed service in the band 7125-8500 MHz

•

ERC/REC 12-05 E: Harmonized radio frequency channel arrangement for digital terrestrial fixed systems in the band 10.0-10.68 GHz

•

ERC/REC 12-06 E: Preferential distribution of channels for systems in the fixed service in the band of 10.7 - 11.7 GHz

•

ERC/REC 12-02 E: Harmonized radio frequency channel arrangement for analogue and digital terrestrial fixed systems in the band 12.75-13.25 GHz

•

ERC/REC 12-07 E: Harmonised radio frequency channel arrangement for digital terrestrial fixed systems in the band 14.5-14.62 GHz GHz paired with 15:23 to 15:35

•

ERC/REC 12-03 E: Harmonized radio frequency channel arrangement for digital terrestrial fixed systems in the band 17.7-19.7 GHz

•

T/R 13-02 E: Preferential distribution of channels for systems in the fixed service in the band 22.0-29.5 GHz

•

REC T/R 12-01: Preferential distribution of channels for systems in the fixed service in the band of 37-39.5 GHz

•

ECC/REC/(09)01: Use of the band 57-64 GHz for fixed wireless point-to-point systems

•

ECC/REC/(05)02: Use of the band 64-66 GHz for fixed service

•

ECC/REC/(05)07: Distribution channel systems in the fixed service in the band 71-76 GHz and 81-86 GHz

•

EU REACH Regulation [2006/1907/CE]

•

FCC OET 65

•

FCC Title 247, Part 15

•

GR-63

•

GR-78

•

GR-487-CORE

•

GR-1089-CORE

101


102

•

GR-3108

•

IC RSS-210

•

IEC 61000-4

•

ICES 003

•

ICNIRP

•

IEC EN 60950-1

•

IEC EN 50385

•

IEC EN 60825-1/-2:2000

•

IEC UL 60950-1

•

IEC 60529

•

IEEE 1613

•

IETF RFC 2474

•

IETF RFC 2475

•

IETF RFC 3550

•

IETF RFC 0793

•

IETF RFC 0791

•

IETF RFC 1157

•

IETF RFC 768

•

IETF RFC 2616

•

MEF 8

•

NAR EIA-310

•

Safety (Canada)

•

SR-332

•

TR NWT 000499

•

TR TSY 000191

•

Synchronization standards: −

G.781

−

G.8260

−

G.8261

−

G.8261 Amd1

−

G.8262

−

G. 8263

−

G.8264

−

G.8264 Amd1

−

G.8264 Amd2 & Corr2



•


−

G.8265

−

G.8265.1

−

G.8272/Y.1367

−

G.8273

−

G.8273.1

−

G.8273.2

−

G.8273.3

−

G.8273.4

−

G.8275

−

G.8275.1

ITU standards: −

ITU-R F.382: Radio-frequency channel arrangements for fixed wireless systems operating in the 2 and 4 GHz bands.

−

ITU-R F.1099: Radio-frequency channel arrangements for high- and medium capacity digital fixed wireless systems in the upper 4 GHz (4 4005 000 MHz) band.

−

ITU-R F.635: Radio-frequency channel arrangements based on a homogeneous pattern for fixed wireless systems operating in the 4 GHz (3 400-4 200 MHz) band.

−

ITU-R F.383: Radio-frequency channel arrangements for high-capacity fixed wireless systems operating in the lower 6 GHz (5 925 to 6 425 MHz) band.

−

ITU-R F.384: Radio-frequency channel arrangements for medium- and high capacity digital fixed wireless systems operating in the upper 6 GHz (6 425-7 125 MHz) band.

−

ITU-R F.385: Radio-frequency channel arrangements for fixed wireless systems operating in the 7 GHz (7 110-7 900 MHz) band.

−

ITU-R F.386: Radio-frequency channel arrangements for fixed wireless systems operating in the 8 GHz (7 725 to 8 500 MHz) band.

−

ITU-R F.387: Radio-frequency channel arrangements for fixed wireless systems operating in the 11 GHz band.

−

ITU-R F.497: Radio-frequency channel arrangements for fixed wireless systems operating in the 13 GHz (12.75-13.25 GHz) frequency band.

−

ITU-R F.636: Radio-frequency channel arrangements for fixed wireless systems operating in the 14.4-15.35 GHz band.

−

ITU-R F.595: Radio-frequency channel arrangements for fixed wireless systems operating in the 17.7-19.7 GHz frequency band.

−

ITU-R F.637: Radio-frequency channel arrangements for fixed wireless systems operating in the 21.2-23.6 GHz band.

103


104


−

ITU-R F.746: Radio-frequency arrangements for fixed service systems.

−

ITU-R F.748: Radio-frequency arrangements for systems of the fixed service operating in the 25, 26 and 28 GHz bands.

−

ITU-R F.749: Radio-frequency arrangements for systems of the fixed service operating in sub-bands in the 36-40.5 GHz band.

−

ITU-R F.2006: Radio-frequency channel arrangements for fixed wireless systems operating in the 71-76 and 81-86 GHz bands.

−

ITU-R F.592: Vocabulary of terms for the fixed service

−

ITU-R F.1101: Characteristics of digital fixed wireless systems below about 17 GHz

−

ITU-R F.1102: Characteristics of fixed wireless systems operating in frequency bands above about 17 GHz

−

ITU-R F.1191-1-2: Necessary and occupied bandwidths and unwanted emissions of digital fixed service systems

−

ITU-R F.1330: Performance limits for bringing into service the parts of international PDH and SDH paths

−

ITU-R F.1668: Error performance objectives for real digital fixed wireless links used in 27 500 km hypothetical reference paths and connections

−

ITU-R F.1703: Availability objectives for real digital fixed wireless links used in 27 500 km hypothetical reference paths and connections

−

ITU-T G.664: Optical safety procedures and requirements for optical transport systems

−

ITU-T G.702: Digital hierarchy bit ratesITU-T G.703Physical/electrical characteristics of hierarchical digital interfaces

−

ITU-T G.704: Synchronous frame structures used at 1544, 2048 kbps hierarchical levels

−

ITU-T G.706: Frame alignment and cyclic redundancy check (CRC) procedures relating to basic frame structures defined in Recommendation G.704

−

ITU-T G.707: Network node interface for the synchronous digital hierarchy (SDH)

−

ITU-T G.775: Loss of Signal (LOS), Alarm Indication Signal (AIS) and Remote Defect Indication (RDI) defect detection and clearance criteria for PDH signals

−

ITU-T G.781: Structure of Recommendations on equipment for the SDH

−

ITU-T G.784: Management aspects of synchronous digital hierarchy (SDH) transport network elements

−

ITU-T G.803: Architecture of transport networks based on the synchronous digital hierarchy



−

ITU-T G.805: Generic functional architecture for transport networks

−

ITU-T G.806: Characteristics of transport equipment - Description methodology and generic functionality

−

ITU-T G.808-1: Generic protection switching

−

ITU-T G.810: Definitions and terminology for synchronization networks

−

ITU-T G.811: Timing requirements at the outputs of primary reference clocks suitable for plesiochronous operation of international digital links

−

ITU-T G.812: Timing requirements at the outputs of slave clocks suitable for plesiochronous operation of international digital links

−

ITU-T G.813: Timing characteristics of SDH equipment slave clocks (SEC)

−

ITU-T G.821: Error performance of an international digital connection operating at a bit rate below the primary rate and forming part of an Integrated Services Digital Network

−

ITU-T G.822: Controlled slip rate objectives on an international digital connection

−

ITU-T G.823: The controls of jitter and wander within digital networks that are based on the 2048 kbps hierarchy

−

ITU-T G.825: The control of jitter and wander within digital networks which are based on SDH

−

ITU-T G.826: End-to-end error performance parameters and objectives for international, constant bit-rate digital paths and connections

−

ITU-T G.828: Error performance parameters and objectives for international, constant bit rate synchronous digital paths

−

ITU-T G.829: Error performance events for SDH multiplex and regenerator sections

−

ITU-T G.831: Management capabilities of transport networks based on the Synchronous Digital Hierarchy (SDH)

−

ITU-T G.957: Optical interfaces for equipments and systems relating to the synchronous digital hierarchy

−

ITU-T G.7043: Virtual concatenation of PDH signals

−

ITU-T G.7710: Common equipment management function requirements

−

ITU-T G.8010: Architecture of Ethernet layer networks

−

ITU-T G.8011: Ethernet over Transport - Ethernet services framework

−

ITU-T G.8011.1: Ethernet private line service

−

ITU-T G.8011.2: Ethernet virtual private line service

−

ITU-T G.8012: Ethernet UNI and Ethernet over transport NNI

105


•

106


−

ITU-T G.8021: Characteristics of Ethernet transport network equipment functional blocks

−

ITU-T G.8032: Ethernet ring protection switching

−

ITU-T G.8261: Timing and synchronization aspects in packet networks

−

ITU-T G.8262: Timing characteristics of a synchronous Ethernet equipment slave clock

−

ITU-T G.8264: Distribution of timing through packet networks

−

ITU-T Y.1291: An architectural framework for support of QoS in packet networks

−

ITU-T Y.1541: Network performance objectives for IP-based services

−

ITU-T G.921

−

ITU-T Recommendation K20

−


−


−


−

G.801

−

G.806

−

G.808.1

−

G.810

−

G.824

−

G.7043/Y.1343

−

Y.1291

Ethernet standards: −

IEEE 802.3/802.3u/802.3ab

−

IEEE 802.3ac

−

IEEE 802.1ad

−

IEEE 802.3ah

−

IEEE 802.3as-2006 (Frame size)

−

IEEE 802.1

−

IEEE 802.1D

−

IEEE 802.1Q

−

IEEE 802.3x

−

IEEE 802.1AX

−

MEF 9

−

MEF 10

−

MEF-14


3.7


JF6-9558H and JF6-9558HC (unlicensed) radio The JF6-9558H/6933B-9500MPT (MPT-HL) and JF6-9558HC/6933B-9558HC (MPT-HC) unlicensed radio provides fast deployment of service with microwave radio. No license and small antennas (no FCC and Industry Canada requirements) allow immediate turn-up. After the license is received, the unlicensed radio can be easily converted to the lower 6 GHz licensed band. The JF6-9558H/6933B-9500MPT and JF6-9558HC/6933B-9558HC unlicensed radio operates in the 5725-5850 Information, Scientific, and Medical (ISM) band in accordance with FCC Part 15.247 and IC RSS-210. This unlicensed radio, although operating in the same band as a spread spectrum radio, operates using narrower bandwidths than spread spectrum. The MPT-HC 5.8 Unlicensed band (JF6-9558HC/6933B-9558HC) is currently being certified and is not available for quote, sale, or deployment.

3.7.1

FCC class B compliance statement The JF6-9558H/6933B-9500MPT and JF6-9558HC/6933B-9558HC unlicensed radio have been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules and IC RSS-210. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.

3.7.2

FCC class B requirements This device complies with part 15 of the FCC Rules and IC RSS-210. Operation is subject to the following three conditions: (1) this device may not cause harmful interference. (2) This device must accept any interference received, including interference that may cause undesired operation. (3) This device must be professionally installed.

107



Caution: Changes or modifications not expressly approved by Alcatel-Lucent could void the authority to operate the JJF6-9558H/6933B-9500MPT and JF6-9558HC/6933B-9558HC unlicensed radio.

Caution: Installation, Turn-Up, Maintenance, and Operation Instruction supplied with the JF6-9558H/6933B-9500MPT and JF6-9558HC/6933B-9558HC unlicensed radio require strict adherence for continued part 15 of the FCC Rules and IC RSS-210 compliance.

108


System administration

4 System administration The following applications are available for 9500 MPR system administration: 1. WebEML (JUSM) 2. Web Server 3. WebCT (available with the CorEvo card only) 4. Provisioning Tool 5. MCT (available with the MPR-e and MSS-1c only) 6. MIB WebEML, WebCT, Web Server and MCT provide a Graphical User Interface (GUI) to enable a user to view and perform system administration for all Network Elements (NEs) in a network, including remote 9500 MPR systems. For more information on WebEML, Web Server and Provisioning Tool see 9500 MPR WebEML User Manual. For more information on WebCT see the 9500 MPR WebCT User Manual. For more information on MCT see 9500 MPR MCT User Manual. Network Management is supported using 1350 OMS, 1352 CM, 1353 NM and 5620 SAM.

109

Release 7.0.0 3DB 19383 ACAA Issue 01 System administration

110



Features

5 Features The following lists the features of the current release of 9500 MPR. To administer these features using the user interfaces, see the documentation as described in Table 4. Table 4

5.1

5.2

Documentation for graphical user interfaces

Interface

Document

WebEML

9500 MPR WebEML User Manual

WebCT

9500 MPR WebCT User Manual

MCT

9500 MPR MCT User Manual 9500 MPR MCT User Manual for Single NE Mode with 7705 SAR

Microwave service switch (MSS) •

MSS-8 shelf

•

MSS-4 shelf

•

MSS-1 shelf

•

MSS-1c

•

MSS-O

Radio •

Radio configuration −

1+0 and 1+1 Terminal

−

1+0 and 1+1 Drop and Insert Repeater

−

1+0 and 1+1 3-Way Junction

111

Release 7.0.0 3DB 19383 ACAA Issue 01 Features


•

−

1+0 and 1+1 Nodal x-Way Junction

−

N+0 (MPT-HL/HLC/HLS only)

Protection schemes For all radios −

1+0 unprotected

−

1+1 Hot StandBy (HSB)

−

1+1 Space Diversity (SD)

−

1+1 Frequency Diversity (FD)

−

2x(1+0) XPIC

−

4x(1+0) XPIC

−

2x(1+1) XPIC

For MPT-HLC/HLS, with or without diversity combiner −

1+0 unprotected

−

N+0 unprotected

−


−

1+1 Hot StandBy (HSB) with antenna protection (MPT-HLC only)

−

1+1 Space Diversity (SD)

−


−

2x(N+0) XPIC

−

4x(N+0) XPIC

−

2x(1+1) XPIC

•

Channel spacing

•

Fixed Modulation

•

Adaptive modulation −

•

Adaptive equalization

•

Fiber-microwave protection

•

Frequency agility

•

Link identifier

•

Loopback

•

112

Admission control

−

Core facing radio digital loopback

−

Radio facing circuit loopback

−

Core facing RF loopback

Performance monitoring


Features

−

Adaptive modulation PM

−

Radio analog PM

−

Radio Ethernet PM

−

Radio hop PM

−

Radio link PM

−

Radio QoS PM

−

Radio power level PM

−

Radio RSL PM

•

Power monitoring

•

Radio direction label

•

Radio L1 LAG

•

Radio L2 LAG

•

Transmit power control

•

−

ATPC

−

RTPC

Tx mute −

5.3

Manual timed Tx mute

•

Latency optimization

•

AES encryption management

•

XPIC

Radio transceivers •

•

MPT ODU −

MPR-e (standalone MPT ODU)

−

Unlicensed radio for MPT-HL, MPT-HLC and 9558HC in the ANSI market

MPT-HL (ANSI market only) −

Lower 6 GHz frequency plan

−


•

MPT-HLC (ANSI market only)

•

MPT-HLS (ETSI market only)

113



5.4

Ethernet •

•

•

•

•

•

114

Ethernet traffic management −

802.1D (with the Core-E card only)

−

802.1Q

−

802.1ad

MSS-1c Ethernet traffic management −

Bridge type change

−

Reserved multicast addresses

Frame type −

Ethernet v2

−

802.3

−

802.1Q

Quality of service (QoS) −

QoS classification

−

QoS priority value to internal forwarding class

−

Internal forwarding class to queue mapping

−

Queue scheduler algorithm

−

Queue size

−

QoS with jumbo frame

−

QoS in the Core-E and CorEvo card

−

QoS for TMN packets

−

QoS for 1588v2 flows

−

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

−

QoS in the MPT-HL

−

QoS with L1 LAG with EASv2

−

QoS in the MSS-1c

−

QoS in the MPT with MPR-e and MSS-1c

IP addressing −

IPv4 addressing for the local IP address

−

IPv4 addressing for the TMN local Ethernet interface IP address

−

IPv6 addressing for the local IP address

−

IPv6 addressing for the TMN local Ethernet interface IP address

Ethernet features provisioned by craft terminal


•

5.5

Features

−

Port based rate limiting

−

Storm control (broadcast, multicast, and unknown unicast)

−

VLAN based rate limiter

−

Per-VLAN per-COS rate limiter

Ethernet features configured by enhanced configuration file −

Access control list

−

Out of range VLAN swap

−

Per-flow policer

−

Stacked VLAN (Q-in-Q) tagging

−

VLAN remarking

−

VLAN swap

•

Input/output flow control

•


•

Traffic mode

•

Ethernet synchronization messaging channel

•

Ethernet connectivity fault management

•

TACACS+

•

Ethernet ring protection

•

Jumbo frame

•

Ethernet L2 LAG

•

Packet throughput booster (Header compression)

•

Performance monitoring

•

Port segregation

•

VLAN IDs

•

EFM OAM Configuration

Managed services and profiles •

TDM2TDM

•

TDM2ETH

•

SDH2SDH

•

ETH2ETH

•

MSS-1c traffic profiles

115



5.6

Traffic interfaces •

•

116

−

10/100/1000 Base-T Ethernet interfaces

−

GigE SFP Ethernet interfaces

−

Radio interface for MPT ODU

−

MPT-HL/HLC/HLS radio interface

CorEvo −


−

Optical SFP Ethernet interfaces

−


−


•

E1/DS1 PDH interface

•

DS3 PDH interface

•

SDH interface

•

Ethernet access switch

•

5.7

Core-E

−

10/100/1000Base-T Ethernet interfaces

−


−

MPT-HL/HLC radio interface

−

MPT-HC/HC-HQAM/XP/XP-HQAM radio interface

Ethernet access switch version 2 −

10/100/1000Base-T Ethernet interfaces

−


−


−


•

MPT access

•

MSS-1 Shelf

Power interfaces for MPT ODU •

Power injector box

•

MPT power unit

•

MPT Extended Power Unit


5.8

5.9

Features

Configurations •

MSS-8 shelf configurations

•

MSS-4 shelf configurations

•

MSS-1 unit configuration

•

Stand alone MSS-1/MSS-4/MSS-8 shelf

•

Stacking MSS-1/MSS-4/MSS-8 shelf configuration

Cross-connections •

PDH Cross-connections

•

SDH Cross-connections

•

Radio-radio cross-connections

•

Ethernet cross-connections

•

Generic Ethernet flows

•

MSS-1c cross-connections

5.10

Database backup and restore

5.11

In-service upgrade

5.12

LAG (link aggregation group) •

L1/L2 link aggregation on radio ports (radio L1/L2 LAG)

•

L2 Link aggregation on user Ethernet ports (Ethernet L2 LAG)

117



5.13

License key management

5.14

Loopback

5.15

118

•


•


•


•

Line facing PDH (DS1/DS3) loopback

•

Radio facing PDH (E1/DS1/DS3) loopback

•

Line facing SDH (STM-1/OC-3) loopback

•

Core facing SDH (STM-1/OC-3) loopback

•

Loopback time-out

Network Communication •

Alcatel-Lucent 1350 OMS

•

Alcatel-Lucent 1352 CM

•

Alcatel-Lucent 1353 NM

•

Alcatel-Lucent 5620 SAM

5.16

NE time

5.17

Non-administrator user

5.18

Performance monitoring •


•

Ethernet statistics


5.19

Features

•

PDH PM

•

SDH PM

•

Radio analog PM

•

Radio Ethernet PM

•

Radio hop PM

•

Radio link PM

•

Radio QoS PM

•

Radio power level PM

•

Radio RSL PM

Port segregation •

TDM ports

•

MPT access, P8ETH and EASv2 Ethernet ports

•

MPT ODU number for each MPT plug in

•

MPT ODU in protection

•

MPT ODUs protected on different plug-ins

•

MPT ODUs protected on the same plug-in

•

ERPS Ring ports

5.20

Remote inventory

5.21

Security •

User authentication

•

User profile management

•

SNMP operating mode (SNMPv3 support)

•

SSH and SFTP support

119



5.22

Software package rollback

5.23

Stacking for EAS/EASv2/MPT access cards

5.24

Synchronization

5.25

120

•

Sync switching

•

Master synchronization mode

•

Slave synchronization mode

•

Normal operation

•

Failed primary operation

•

Wait-to-restore

•

Holdover

•

Synchronization for PDH/SDH/DATA

•

Synchronization with MSS-1c

•

IEEE 1588v2 PTP Transparent Clock −

Transparent clock at the NE level

−

Transparent clock across the radio hop

Automatic link discovery •

LLDP overview

•

LLDP on MPR-e

•

Transmitting nearest bridge LLDPDUs

•

Receiving nearest bridge LLDPDUs

•

Transparent relay of nearest non-TPMR bridge and Nearest customer bridge PDUs


5.26

Features

Standard features of MPR-e Standard features include more radio and site scalability and flexibility for installation teams. The following features are available with MPR-e:

5.27

•

Limited need for factory presetting of channel frequency or bandwidth

•

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

•

Outdoor Unit capacity- and modulation-independent

•

Outdoor Unit can support either split-mount or full-outdoor architecture with the same hardware

•

Adaptive packet transport improves performance for priority services

•

Output power agility

•

ATPC

•

Adaptive Modulation

•

Packet-based internal cross-connect

•

Electrical/Optical Ethernet interfaces

•

Software-based configuration

•

Packet throughput booster for enhanced bandwidth

•

AES-256 radio encryption

•

XPIC

•

QoS on the Ethernet traffic

Standard features of MSS-1c Standard features include more radio and site scalability and flexibility for installation teams. The following features are available with MSS-1c: •

Limited need for factory presetting of channel frequency or bandwidth

121



5.28

•

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

•

Outdoor Unit capacity- and modulation-independent

•

Outdoor Unit can support either split-mount or full-outdoor architecture with the same hardware

•

Adaptive packet transport improves performance for priority services

•

Output power agility

•

ATPC

•

Adaptive Modulation

•

Packet-based internal cross-connect

•

Electrical/Optical Ethernet interfaces

•

Software-based configuration

•

Packet throughput booster for enhanced bandwidth

•

AES-256 radio encryption

•

Flexible aggregate capacity sharing between E1/T1/DS1 and Ethernet

•

TDM MEF8 encapsulation

•

High Switching Capacity

MPR-e prerequisites One Ethernet traffic port: •

electrical to be used with MPT ODU or

•

optical only with MPT-HC/XP/HC-HQAM/XP-HQAM/9558HC

•

An FE (minimum) port

For local management (provisioning phase only): •

VLAN management capability to create a tagged service between the local management port and MPT Ethernet port One service open with VLAN ID on GE Port. Default VLAN ID: 4080

If local management is not required, the NE could be supervised through TMN RF. One Gigabit Ethernet (GE) traffic port:

122


Features

•

electrical to be used with MPT ODU or

•

optical only with MPT-HC/XP/HC-HQAM/XP-HQAM/9558HC

For local management (provisioning phase only): •

An FE (minimum) port

•

VLAN management capability to create a tagged service between the local management port and MPT Ethernet port One service open with VLAN ID on GE Port. Default VLAN ID: 4080 If local management is not required, the NE could be supervised through TMN RF.

123


124



Equipment layout

6 Equipment layout The 9500 MPR contains cards that plug into shelf assemblies and mechanical equipment housed in equipment racks. Power and signaling connections are made through backplane connectors.

6.1

Rack assemblies MSS-1/4/8, MSS-1c, and MPT-HL shelf assemblies are mounted in either an equal flange aluminum equipment rack or an unequal flange seismic rack. Each rack uses 1.75-inch Electronic Industries Association (EIA) rack mounting increments. A 7 feet equal flange aluminum rack provides 46 EIA rack increments. A 7 feet unequal flange seismic rack provides 43 EIA rack increments. Seismic racks meet EIA specifications regarding earthquake resistance. For ETSI applications the MSS-8 is mounted in an Nokia ETSI rack using a special flange adapter (19” to 21”). The MPT-HLS unit is inserted in a specific subrack mounted in the ETSI rack. The subrack for the MPT-HLS standard can support up to 20 transceivers. The subrack for the MPT-HLS compact can support up to four transceivers. The ETSI rack can be equipped with two subracks to support different configurations. See Rack and rack accessories unit data sheet for specifications and part numbers.

6.2

Constraints Certain constraints must be considered when integrating the system into a physical network environment. Each installation presents its own set of considerations.

125

Release 7.0.0 3DB 19383 ACAA Issue 01 Equipment layout

6.3


Shelf assemblies System shelf assemblies follow: •

MSS-8 shelf

•

MSS-4 shelf

•

MSS-1 unit

•

MSS-O

•

MSS-1c shelf

•

MPT-HL/HLC shelf

•

MPT-HLS shelf (standard or compact) (installed in ETSI rack only)

System OutDoor Unit (ODU) assemblies follow: •

MPT-HC

•

MPT-MC

•

MPT-XP

•

MPT-HC-HQAM

•

MPT-XP-HQAM

The following assemblies are also installed in rack assemblies:

126

•

Power Distribution Unit (PDU) for ANSI

•

Top Rack Unit (TRU) for ETSI

•

DS1 37 Pin D-Sub Patch Panel Assembly

•

DS1 RJ-45 Patch Panel Assembly

•

DS3 BNC Patch Panel

•

Type N Adapter Plate Assembly


6.3.1

Equipment layout

MSS-8 shelf

The MSS-8 shelf mounts in a standard 19-inch rack. See Figure 23. Adapter brackets are available to mount MSS-8 shelf in a standard 23-inch rack or an ETSI 21-inch rack. The MSS-8 shelf houses the following cards: •

Core card: −

Core-E—Enhanced Control and Switching Module

−

CorEvo

•

P32E1DS1 —DS1/E1 PDH card

•

P2E3DS3 —DS3 PDH card

•

SDHACC (OC-3/STM-1)—OC-3/STM-1 SDH card

•

P8ETH (EAS)—Ethernet Access Switch card

•

EASv2—Ethernet Access Switch card

•

MPTACC (RADIO)—MPT Access card

•

AUX—Auxiliary card

•

Power Injector card

•

Power Converter

•

Fans: −

FAN—MSS Fan

−

A-FAN—MSS Enhanced Fan with Alarms

−

Fan Evo—MSS Enhanced Fan with Alarms

The fan can be installed and provisioned in slot 9 of the MSS-8. The Fan Evo module is mandatory for a CorEvo based system.

127


Figure 23


MSS-8 shelf, front view

6.3.2

MSS-4 shelf

The MSS-4 shelf mounts in a standard 19-inch rack. See Figure 24. Adapter brackets are available to mount MSS-4 shelf in standard 23-inch rack or ETSI 21-inch rack. The MSS-4 shelf houses the following cards: •

Core card: −

Core-E—Enhanced Control and Switching Module

−

CorEvo 1G Note: CorEvo protection is not supported with MSS-4.

•

P32E1DS1 —DS1/E1 PDH card

•

P2E3DS3 —DS3 PDH card

•

SDHACC (OC-3/STM-1)—OC-3/STM-1 SDH card

•

P8ETH (EAS)—Ethernet Access Switch card

•

EASv2—Ethernet Access Switch card

•

MPTACC (RADIO)—MPT Access card

•

AUX—Auxiliary card

•

Power Injector card

•

Fans: −

128

FAN—MSS Fan


Equipment layout

−

A-FAN—MSS Enhanced Fan with Alarms

The fan can be installed and provisioned in slot 5 of the MSS-4. By default, the FAN module is provisioned. The FAN1U module is mandatory with a CorEvo card. Figure 24

MSS-4 shelf, front view

6.3.3

MSS-1 unit The MSS-1 unit mounts horizontally in a standard 19-inch rack. See Figure 25. Adapter brackets are available to mount the MSS-1 unit in a standard 23-inch rack or an ETSI 21-inch rack.

Figure 25

MSS-1

6.3.4

MSS-O The MSS-O can be installed indoors in a 19-inch rack. However, it is optimized for outdoor installation on a pole or wall. See Figure 26.

129


Figure 26

130

MSS-O



6.3.5

Equipment layout

MPT-HL/HLC shelf The MPT-HL/HLC shelf mounts in a standard 19-inch rack. See Figure 27. Adapter brackets are available to mount the MPT-HL/HLC shelf in a standard 23-inch rack. The MPT-HL/HLC shelf houses the MPT-HL and MPT-HLC Transceiver cards.

Figure 27

MPT-HL/HLC shelf, front view

131



6.3.6

MPT-HLS shelves

The 9500 MPR supports two variants of the MPT-HLS: standard and compact. A shelf is available for each variant.

6.3.6.1

MPT-HLS standard shelf The 9500 MPR supports up to two MPT-HLS shelves in an ETSI 21” rack. Each rack supports up to 10 MPT-HLS standard RTs, or up to four MPT-HLS compact RTs. The MPT-HLS shelf components are: •

a mechanical frame

•

one or two back panels for MPT-HLS powering, and centering pins for each MPT-HLS

•

support guides for each MPT-HLS

•

front and top plates to cover empty slot positions

Figure 28 shows the MPT-HLS shelf components.

132


Figure 28

Equipment layout

MPT-HLS shelf components

133



Figure 29 shows the MPT-HLS shelf panel plates. Figure 29

MPT-HLS shelf cover plates for empty slots

6.3.6.2

MPT-HLS compact shelf

The MPT-HLS compact has been introduced for improving characteristics of the 9500 MPR LH system in terms of flexibility and compactness. Its principle is based on the modularity of the parts permitting the installation of up to four MPT HLS transceivers in a volume efficient way, keeping the performances of the radio channels of the standard MPR LH systems. The system basic components are:

134

•

RT subshelf: able to support up to two transceivers MPT-HLS. The system is able to manage up two subshelves for a total capacity of four radio channels.

•

Branching drawer: containing the passive functions for the radio channelization.


•

Equipment layout

MSS-8 subshelf: can be mounted on the same rack as the MPR LH compact system or a different rack.

Figure 30 and Figure 31 show the subshelf and the branching drawer. Figure 32 and Figure 33 show examples of the MPT-HLS compact units assembled on racks. Figure 30

MPT-HLS compact indoor transceivers subshelf

Figure 31

MPT-HLS compact branching drawer

135


Figure 32

MPT-HLS compact assembled on rack: example 1

Figure 33

MPT-HLS compact assembled on rack: example 2

136



6.3.7

Equipment layout

Miscellaneous assemblies Other system assemblies include the following: •

Power Distribution Unit

•

DS1/E1 37 Pin D-Sub Patch Panel Assembly

•

DS1/E1 RJ45 Patch Panel Assembly

•

DS3 BNC Patch Panel

•

Type N Adapter Plate Assembly

•

Power Injector Box

•

MPT Power Unit

•


137


138




7 Functional operation 7.1

Microwave service switch (MSS) Microwave Service Switch (MSS) shelves provides up to 16 Gb/s packet switch node. If a CorEvo card is in use, the speed can be up to 100 Gb/s. The MSS incorporates the base–band processing, tributaries interfaces, radio port interfaces and supervision. The MSS is frequency–independent. The MSS-4 and MSS-8 shelf consists of a card cage and backplane in which mounts access and radio peripherals and Core control cards. The MSS-1, MSS-1c and MSSO shelves are monoboards. The MSS is frequency–independent. The following MSS shelves are available: •

MSS-8 shelf

•

MSS-4 shelf

•

MSS-1

•

MSS-O

•

MSS-1c shelf

139

Release 7.0.0 3DB 19383 ACAA Issue 01 Functional operation

7.1.1


MSS-8 shelf

A fully equipped Microwave Service Switch (MSS-8) shelf provides up to 450 Mb/s full-duplex Ethernet transport capacity per radio carrier channel. MSS-8 shelf provides up to 100 Gb/s packet switching which creates flexible aggregate capacity sharing across DS1/E1, DS3, OC-3/STM-1, and Ethernet traffic. The MSS-8 shelf supports the following: •

1 or 2 Core Cards (Main & Spare)

•

up to 6 Transport cards

•

1 AUX peripheral unit (optional: supported in transport slot #8)

•

1 DC Converter (optional: supported in transport slots 4, 6, or 8)

•

1 Fans unit

•

support for MPT ODU and MPT-HL/HLC/HLS radios

In the right part of the MSS shelf there are two sub-D 2-pole power supply connectors.

7.1.2

MSS-4 shelf

A fully equipped Microwave Service Switch (MSS-4) shelf provides up to 450 Mb/s full-duplex Ethernet transport capacity per radio carrier channel. MSS-4 shelf provides up to 100 Gb/s packet switching which creates flexible aggregate capacity sharing across DS1/E1, DS3, OC-3/STM-1, and Ethernet traffic. The MSS-4 shelf supports the following: •

1 or 2 Core Cards (Main & Spare)

•

up to 2 Transport cards

•

1 AUX peripheral unit (optional: supported in Transport slot #4)

•

1 Fans unit

•

support for MPT ODU and MPT-HL/HLC/HLS radios

In the right part of the MSS shelf there is one sub-D 2-pole power supply connector.

140


7.1.3


MSS-1 shelf

A Microwave Service Switch (MSS-1) shelf provides up to 450 Mb/s full-duplex Ethernet transport capacity per radio carrier channel. The MSS-1 unit provides up to 16 Gb/s packet switching which creates flexible aggregate capacity sharing across E1/DS1 and Ethernet traffic. The MSS-1 unit provides the function of the following:

7.1.4

•

Main Core-E card

•

1 P32E1DS1 card with 16 ports

•

4 housekeeping alarm inputs

•

support for MPT ODU radios

MSS-O The MSS-O provides three 10/100/1000BaseT Ethernet interfaces, two with PFoE, and one GigE optical Ethernet SFP interface. The 10/100/1000BaseT Ethernet interface supports a mixture of user Ethernet ports or MPT radio ports. The MPT may be MPT-HC, HC-HQAM, XP, XP-HQAM, MC, or 9558HC. The GigE Optical Ethernet interface supports a User Ethernet port. The MSS-O can be installed indoors or outdoors. It is optimized for outdoor installation.

7.1.5

MSS-1c

Microwave Service Switch (MSS-1c) shelf provides up to 314 Mb/s full-duplex Ethernet transport capacity per radio carrier channel. MSS-1c is a compact IDU that complements the existing portfolio addressing the last mile, the far end application in nodal solution and cost optimized point-to-point applications. Its small size of 1 rack unit height and half rack width drastically reduces the space consumption in busy sites. Supports MPT ODU.

141


7.2


Radio The system supports up to eighteen radio channels per node. The system supports a mixture of radio technologies (MPT ODU, MPT-HL, MPTHLS, and/or MPT-HLC) on the same NE. The radio channels can be all the same frequency, different frequencies, or a combination of both. Not all radios are available in both markets. Radio part numbers and frequencies are provided in the 9500 MPR Frequency Plan for MPT Outdoor Transceivers. Radio performances are provided in the 9500 MPR Technical Summary documents:

7.2.1

•

9500 MPR Technical Specifications for Split Mount Applications (MPT-MC, HC, XP, HQAM and GM)

•

9500 MPR Technical Specifications for Full Indoor Applications (MPT-HLC, MPT-HLS)

Radio configuration Support for the following radio configurations:

7.2.1.1

•

1+0 and 1+1 Terminal

•

1+0 and 1+1 Drop and Insert Repeater

•

1+0 and 1+1 3-Way Junction

•

1+0 and 1+1 Nodal x-Way Junction

Protection schemes Support for the following radio protection schemes:

142

•

1+0 unprotected

•

1+0 Space Diversity (SD) for MPT-HLC/HLS with diversity combiner

•


•

1+1 SD

•




•

2x(1+0) XPIC

•

4x(1+0) XPIC

•

2x(1+1) HSB XPIC

For MPT-HLC/HLS: •

1+1 HSB space diversity with RPS

•

1+1 HSB space diversity with combiner

•

1+1 frequency diversity with combiner

•

N+0 frequency diversity with combiner

•

N+0 frequency diversity with XPIC

•

N+0 frequency diversity with XPIC and combiner: for MPT-HLC only at L6U6-11 GHz

For MPT-HLC only at L6/U6/11 GHz:

7.2.1.2

•

1+1 HSB with antenna protection with diplexer and stack

•

1+1 HSB 60 MHz compact and stack (L6 only)

Channel spacing See the 9500 MPR Technical Specifications for Full Indoor Applications and 9500 MPR Technical Specifications for Split Mount Applications for supported channel spacing information.

7.2.1.3

Radio configuration rules for MPT ODU

For the following configurations using multiple channel arrangements on one antenna, one sub-band for all the MPTs is recommended. If you need to use two subbands, contact Alcatel-Lucent. •

4+0 XPIC

•

N+0 (with or without LAG)

•

1+1 FD using coupler, OMT or OMT-C

143


7.2.1.4


Rule for 2048 QAM modulation scheme with MPT-HCHQAM/XP-HQAM To reach the 2048 QAM modulation scheme, the RSL must be higher than the values described in the following table. If ATPC is in use, the ATPC threshold must follow the same rule. Modulation Channel Spacing 2048 QAM 28 to 60 MHz 2048 QAM 14 MHz 2048 QAM 14 to 60 MHz

7.2.1.5

Frequency

RSL

6-13 GHz 6-13 GHz 15-23 GHz

RSL ≥ -45 dBm RSL ≥ -50 dBm RSL ≥ -42 dBm

Multiple channels arrangement for 1024 and 2048 QAM with the same sub-band on one antenna for MPT-HCHQAM/XP-HQAM

The following rules apply when configuring a multiple channel arrangement for 1024 and 2048 QAM. Each rule assumes the previous rules in the list are also being followed. 1. For 2048 QAM, adjacent channels must be in Alternate Polarization, regardless of frequency band or channel spacing., as shown in Figure 34. Figure 34

Adjacent channels must be in alternate polarization

2. In RTPC mode, the Transmit Power of all the channels in a same polarization must be set at the same level.

144



3. At 2048 QAM, with copolar multiple channels in the same sub-band, the maximum modulation scheme could be affected by different PTx values in ATPC. Consequently for those cases, ATPC range is recommended to be limited to: −

-10dB for 6 to 8GHz frequency bands

−

-5dB for 11 to 38GHz frequency bands

See Figure 35. Figure 35

ATPC with restriction

4. In RTPC mode, LAG 4+0 is supported with OMT-C with four different frequencies, see Figure 36. Figure 36

RTPC mode with four different frequencies

ATPC mode can also be supported for 1 Sub-Band if two antennas (and consequently two OMTs) are configured.

145


7.2.1.6


Adjacent channels deployment rules for adaptive modulation Copolar or XPIC configurations up to 1024 QAM The rules are presented in Table 5 describing MPT type, frequency band and Maximum Modulation scheme that can be reached in adaptive modulation (ACM) with Copolar or XPIC configurations. These rules are valid for single adjacent channel or dual adjacent channels, with or without ATPC, for all modulations up to 1024 QAM.

Table 5

Minimum Reference Modulation schemes supported for configurations with adjacent channels

MPT Type

Frequency band

Maximum modulation for ACM up to 256 QAM

Maximum modulation for ACM 512 QAM or 1024 QAM

MPT-MC/HC/ XP

≤ 25 GHz

ANSI market: • Channel Spacing 5, 10, 30, 50, 60MHz: QPSK as minimum reference modulation • Channel Spacing 40MHz: supported if the software release is ≥ 6.0.0 and frequency is ≥ 15 GHz, with QPSK as minimum reference modulation ETSI market: • Channel Spacing ≤ 28 MHz: 64QAM as minimum reference modulation • Channel Spacing 40 MHz: not supported (U6, 11GHz) • Channel Spacing 56 MHz: QPSK as minimum reference modulation

—

MPT-MC/HC

38 GHz

Not supported

Not supported

MPT-HCHQAM/XPHQAM

≤ 28 GHz

Minimum QPSK as reference modulation


146


Table 5


Minimum Reference Modulation schemes supported for configurations with adjacent channels (Continued)

MPT Type

Frequency band

Maximum modulation for ACM up to 256 QAM

Maximum modulation for ACM 512 QAM or 1024 QAM

MPT-HCHQAM

38 GHz


Not supported

7.2.2

Adaptive modulation Adaptive modulation is a mixed mode technology which uses different modulation techniques to maximize capacity during degraded propagation conditions (fading). Modulation switching is errorless for all frequencies. When a terminal operates in adaptive modulation, it is possible to commission the total capacity of both Ethernet and TDM traffic, up to a bandwidth corresponding to the maximum modulation scheme chosen by the operator. This capacity depends on the channel spacing and the modulation scheme.

7.2.2.1

Admission control Admission control ensures that TDM flows are maintained when the modulation scheme is downgraded automatically by the system due to degraded propagation conditions. The number of TDM links supported is limited to the capacity of the lowest modulation technique selected (typically 4 or 64 QAM). The Admission Control feature protects the TDM traffic when TDM traffic is provisioned. The maximum number of E1/DS1 links that can be provisioned (or cross-connected in a given radio direction) equals the number of E1/DS1s supported by the lowest modulation provisioned, typically 4 QAM or 64 QAM capacity. The remaining capacity is devoted to other types of traffic such as Ethernet best effort. From the system point of view, it is not possible to provision more E1/DS1s than are supported by the lowest modulation scheme. When the modulation scheme is downgraded to the lowest value (16QAM to 4QAM), it is not possible for the system to know which E1/DS1s should be maintained and which should be dropped because all E1/DS1 links have the same priority.

147



Admission control checks have been added at the CT level, preventing the user from provisioning more E1/DS1s than are supported by the lowest modulation scheme bandwidth. 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 E1/DS1s are kept. If the RSL value further decreases, modulation scheme is downgraded to 4QAM and any traffic exceeding 4QAM bandwidth is dropped while the E1/DS1s are maintained. Figure 37, Figure 38, and Figure 39 show how the system operates, in case of modulation changes with admission control (28 MHz bandwidth). In this case, the operator has commissioned 13xE1’s. Additionally two other kinds of traffic are provisioned, Ethernet traffic #1 and Fast Ethernet traffic #2. Ethernet traffic #1 has a higher QoS priority than Fast Ethernet traffic #2. See Figure 37 for an example of this configuration in normal operating mode.

Figure 37

Example of traffic 28MHz bandwidth and admission control

The 13xE1s are saved even in the case of a degradation of the modulation down to 4QAM. Remaining available capacity is used to transmit other types of traffic. When the modulation is degraded from 64QAM to 16QAM (Figure 38), the E1 flows are maintained while the Ethernet traffic with lowest priority (Fast Ethernet traffic #2) is reduced.

148


Figure 38


Example of traffic 28MHz bandwidth and modulation downgraded to 16QAM

When the modulation is further degraded to 4QAM (Figure 39), the E1 flows are still maintained while 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 39

Example of traffic 28MHz bandwidth and modulation downgraded to 4QAM

7.2.3

Adaptive modulation and admission control with MPT-HLC The Admission Control feature on the MPT-HLC allows the operator to select any of the supported modulation levels as the reference modulation level. This allows the user to provision a number of DS1s that is greater than are supported by any selected modulation level lower than the reference modulation level selected.

149



If the modulation level drops below the reference modulation level, the system can no longer guarantee DS1 traffic. It is possible to provision a number of DS1s greater than the ones fitting in any selected modulation level lower than the reference modulation level. Since all the DS1 links have the same priority, it is not possible from a system point of view to decide which DS1s should be dropped when the modulation scheme is downgraded below the reference modulation (for example, 64 QAM to 16 QAM). For this reason, careful consideration must be adhered to when selecting the reference modulation level and to the number of DS1s to provision on the radio direction.

7.2.4

Adaptive equalization Adaptive equalization (AE) is employed to improve reliability of operation under dispersive fade conditions, typically encountered over long and difficult paths. This is achieved through a multi-tap equalizer consisting of two registers, one with feed-forward taps, the other with feed-back taps. Each of these registers multiply successive delayed samples of the received signal by weighting-coefficients to remove propagation induced inter-symbol interference.

7.2.5

Fiber-microwave protection The Fiber-Microwave Protection feature allows to protect an Optical Fiber link with a Microwave link. The Main protection resource is the Optical Fiber, while the Spare protection resource is the Microwave link. The Optical Fiber link can be either a physical connection between two MPR NEs or a connection between two MPR NEs by a Wireline network, where the access to that Wireline network by MPR NEs is made by Optical Fiber connections. See Figure 40.

150


Figure 40


Fiber-microwave protection

Normally the traffic (Ethernet and TDM) is transmitted on the Optical Fiber link. In case of failure of the Optical Fiber link, the traffic is rerouted automatically to the Microwave link. When the Optical Fiber connection is restored, the traffic is rerouted again on the Optical Fiber link following a Revertive behavior. See Figure 41. The switching criteria for the Optical fiber link are: •

Ethernet LOS (Core unit)

•

SFP Card Missing

•

SFP Card Fail

151


Figure 41


Fiber-microwave protection - operation

The Fiber-Microwave Protection feature is supported by MPR NE using ERPS performing the following configuration:

152

•

Create a Topology having a radio interface and an optical User Ethernet interface as Ring ports;

•

Create a single Instance in the Topology created before. Since it is requested to manage the overall traffic either over Fiber connection or over radio link, the usage of two Instances to load balance traffic in the Ring is not supported;


•


Define one of the two NEs as RPL Owner and configure the radio interface as RPL. In no-fault condition, this will set the Ring port related to the radio interface in blocking, allowing the traffic to be forwarded over Ethernet optical connection.

In case of Core protection the following configuration has to performed by the operator in order to guarantee a consistent behavior of the Fiber-Microwave Protection: •

Usage of optical splitter;

•

Disable auto-negotiation on optical User Ethernet interface;

•

Disable Ethernet LOS as switching criteria for Core protection;

•

Disable Fixed-LAG.

The Fiber-Microwave Protection feature is applicable to Tail links at the leaf of the backhauling tree. The Fiber-Microwave Protection can be implemented also on Tail links having one MPR NE working as Node, according to the following scenario. See Figure 42. Figure 42

Fiber-microwave protection on tail links

The scenario is supported by the MPR NE using ERPS performing the following configuration: •

Create two Topologies in the NE acting as Node, each Topology having a radio interface and an optical User Ethernet interface as Ring ports;

•

Create a single Instance in both the Topologies created before;

•

For each Instance, define the NE acting as Node or the other NE at Tail end as RPL Owner and configure the radio interface as RPL. In no-fault condition, this will left Ring port related to radio interface in blocking, allowing the traffic to be forwarded over Ethernet optical connection.

153



Note: The TDM traffic in the Node cannot transit between the two Topologies. The tagged Ethernet traffic with same VLANs can transit between the two Topologies. This means that the same VLAN ID can be associated with both the Instances belonging to the two Topologies in the NE acting as Node.

7.2.6

Frequency agility Frequency Agility provides the ability to provision the working RF frequency within the supported sub-band of the transceiver. This provides benefits for spare parts, order processing, and frequency coordination.

7.2.7

Link identifier Link Identifier coding blocks unwanted received signals from being propagated further downstream. The number of microwave links, especially in urban areas, creates a 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.

7.2.8

Loopback To facilitate installation, commissioning, remote maintenance, and troubleshooting various radio loopbacks are supported by the system. The system supports the following radio loopback types: •


•


•


•

Core facing @RF - Internal loopback

For a detailed description of radio loopbacks, see Loopback in this manual.

154


7.2.9


Performance monitoring To facilitate commissioning, remote maintenance, and troubleshooting various radio PM counters are supported by the system. The system supports the following radio PM counters: •


•

Radio analog PM

•

Radio hop PM

•

Radio link PM

•

Radio QoS PM

For a detailed description of radio PM, see Performance monitoring.

7.2.10

Power monitoring

The radio transceivers incorporate a detector for Tx power measurement. It is used to provide measurement of forward power as a performance parameter, and to provide a calibration input for transmitter operation over temperature and output range. Viewed Tx power ranges always match the capabilities of the radio transceivers for a given modulation. When modulation is changed, the CT automatically adjusts/ restricts Tx Power to be within valid range.

7.2.10.1

Branching loss for MPT-HLC Power measurements show the Tx and Rx power at the MPT port. To estimate the power available at the antenna port, the values must be adjusted to account for the loss introduced by branching. Before the radio is placed into service, the branching losses can be measured on the system. The measured loss is entered in JUSM to adjust the power measurement. See the 9500 MPR WebEML User Manual for configuration information. Branching loss configuration affects only the local power analog measurements. See the 9500 MPR Technical Specifications for Full Indoor Applications document for information about branching loss values that can be used for radios that are already in service.

155


7.2.11


Radio direction label

Radio Direction Label provides an aid to users in the identification of radio directions. Radio direction labels may be up to fifteen characters in length. Labels are supported on Radio LAG. The radio direction label is displayed on applicable craft terminal screens.

7.2.12

Radio L1 LAG

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

•

Re-ordering: based on Sequence Number fields inserted at the transmitter side, restores the original traffic ordering

A block diagram of L1 Link Aggregation system is shown in Figure 43.

156


Figure 43


L1 LAG block diagram Distributor

Link Aggregation Group

Aggregation Link

QoS

Collector

Re-ordering

Aggregation Systems *one direction only represented 22890

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 (that is, associated with the physical layer). L1 LAG ports are supported on MPT-HC/HC-HQAM, MPT-HL/HLC/HLS, and MPT-XP/XP-HQAM radio interfaces configured with EAS cards or MSS-O. L1 LAG is not supported on MSS-1 equipment.

7.2.12.1

Types of L1 link aggregation L1 Link Aggregation is implemented inside the card. Two configurations 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 44.

157


Figure 44


Types of L1 LAG Update

Plug-In

MPT

Plug-In

CORE

CORE MPT Plug-In

MPT

Plug-In MPT

Cross Plug-in Link Aggregation

Intra Plug-in Link Aggregation 22899

7.2.12.1.1

Intra plug-in L1 link aggregation scenario Intra plug-in LAG is a LAG with radios connected to the same card. An example of intra plug-in LAG implementation is shown in Figure 45. 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.

Figure 45

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 B

LAG A

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.

158



Single card, intra plug-in supported L1 LAG configurations are shown in Figure 46. Dual card, intra plug-in supported L1 LAG configurations are shown in Figure 47. Figure 46

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) Lowest Index Port indicated in bold 22894

Figure 47

Dual 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 EAS Port5 to Port8) Lowest Index Port indicated in bold 22895

7.2.12.1.2

Cross plug-in L1 LAG scenarios

Cross plug-in LAG is a LAG with radios connected to two EAS cards on the same MSS row.

159



An example of cross plug-in LAG implementation is shown in Figure 48. 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 48

Cross plug-in L1 link aggregation scenario Core NE A


Plug-in 1

Plug-in 2 Stacking

Embedded Segregation

Plug-in 1 LAG A

LAG A

Stacking

LAG A

4 RF Channels

Plug-in 2

LAG B

LAG A

LAG B

4 RF Channels

22891

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

160


Figure 49


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) Lowest Index Port indicated in bold 22892

7.2.12.1.3

Protected cross plug-in L1 LAG scenarios

In the protected cross plug-in LAG configuration, the 1+1 protection group is seen as a single radio interface. The protected 1+1 HSB/SD radio configuration is created using the same SFP port on the left and right Plug-in, that is, port 5 of the left card (main) is protected by port 5 of the right card (spare). Protected L1 LAG configurations on P8ETH cards are only supported using MPT-HL radio interfaces. Protected L1 LAG configurations on EASv2 cards are supported with MPT-HL/HLC and MPT-HC/HC-HQAM. An example of protected cross plug-in LAG implementation is shown in Figure 50. Site A is configured with two 1+1 HSB/SD protected radio links in a protected cross plug-in LAG. Site B is configured with two protected cross plug-in LAGs to implement a radio repeater configuration.

161


Figure 50


Protected 1+1 cross plug-in L1 link aggregation scenario Core NE A


Plug-in 1

Plug-in 2 Stacking

Embedded Segregation

Plug-in 1 LAG A

LAG A

Plug-in 2 Stacking

LAG A

LAG B

LAG A

LAG B

2 RF Channels

2 RF Channels

22897

In this configuration, radio protection handles a failure of a single radio hop belonging to the 1+1 HSB/SD protection group. LAG capacity is not affected by a single radio hop failure belonging to the protection group. Supported protected cross plug-in L1 LAG 2x(1+1) configurations are shown in Figure 51. Figure 51

Protected 2x(1+1) cross plug-in L1 LAG configurations Port5 on one EAS protected with Port5 on the other EAS, ... A*-A’ represent protection groups: *-Main ‘-Spare Operator first creates HSB/SD protection groups and then aggregates them. Size parameter represents the number of protection groups 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 EAS Port5 to Port8) Lowest Index Port indicated in bold 22898

162



A mixture of protected and unprotected L1 LAGs is supported. The protected pair can reside in any of the available P8ETH or EASv2 port pairs. Shown in Figure 52, the protected pairs reside in ports 5 and 7. Figure 52

Mix 1+0 and 1+1 protected cross 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) Lowest Index Port indicated in bold

22896

An extension of the supported protected cross plug-in configuration supports 3x(1+1) and 4x(1+1) as shown in Figure 53. Figure 53

Protected 3x(1+1)/4x(1+1) cross plug-in L1 LAG configurations Port5 on one EAS protected with Port5 on the other EAS, ... A*-A’ represent protection groups: *-Main ‘-Spare Operator first creates HSB/SD protection groups and then aggregates them. Size parameter represents the number of protection groups 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 EAS Port5 to Port8) Lowest Index Port indicated in bold 22889

163


7.2.12.2


L1 LAG with EASv2 Caution: L1 LAG on EASv2 in R6.0.0 or later is not compatible with P8ETH or EASv2 in earlier releases. If traffic is received from an L1 LAG on an EASv2 card in R6.0.0 or later, all traffic may be dropped.

If connected to an EASv2, MPT-HC/MC in 1+0 and 1+1 configuration, MPT-HCHQAM in 1+0 and 1+1 configuration, MPT-HL in 1+0 or 1+1 configuration, and MPTHLC/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-HL

•

MPT-HLC

•

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 and MPT-HLC or MPT-HLS cannot be part of the same LAG. An existing L1 LAG consisting of MPT-HL radios can be extended to add an MPTHLC. This configuration is not recommended for replacing an MPT-HL with an MPTHLC.

164



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. Hitless switching is not supported on MPT-HL.

7.2.12.2.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. 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 the 9500 MPR WebEML User Manual. The drop priority value of a flow defines the minimum LAG bandwidth required to support the flow. An SDH flow with a drop priority of 255 will be the first to be subject to the selective drop, as soon as the LAG rate is not enough to transmit all the SDH flows connected to the LAG. An SDH flow with a drop priority of 1 will be the last to be subject to the selective drop. When a cross-connection is created, the default drop priority of the flow is 255. It is possible to configure different drop priority values for each flow. This will allow the available LAG bandwidth to be used to transport as many cross-connected SDH flows as possible. If the same drop priority value is assigned to more than one SDH flow, the drop priority defines the minimum LAG bandwidth required to transport all SDH flows with that drop priority. If the same flow is cross-connected on the other side of the LAG or in a forwarding path, the drop priority should be configured the same in each NE. The maximum number of SDH2SDH flow cross-connections to an L1 LAG is 16. The following apply in the ANSI market: •

The SDH LAG feature is only available with L1 LAG composed of MPT-HLC radio ports.

165



•

7.2.12.3

Selective flow discard is not supported in the presence of DS3 crossconnections.

L1 LAG on MSS-O Caution: L1 LAG on an MSS-O in R6.0.0 or later is not compatible with P8ETH or EASv2 in earlier releases. If traffic is received from an L1 LAG on an MSS-O in R6.0.0 or later, all traffic may be dropped.

L1 LAG is available on MSS-O with a specific license. The maximum size of the LAG is 2. Only one LAG can be configured on an MSS-O: either an L1 LAG or an L2 Ethernet LAG. The MSS-O does not support radios in 1+1 configuration and L1 LAG at the same time.

7.2.12.4

L1 LAG creation L1 LAG is created using the following parameters: •

LAG ID (LAG Identifier): a mandatory parameter that identifies the LAG in the NE

•

LAG Name: an optional parameter that assists the operator to identify the virtual radio direction. LAG Name is up to 32 characters.

•

LAG Type: a mandatory parameter that defines the LAG type (that is, L1 Radio, L2 Radio, L2 Ethernet)

•

LAG Size: a mandatory parameter that configures the maximum number of radio links included in the L1 LAG. LAG Size cannot be less 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:

166

•

integer from 1 to 14

•

cannot be the same as the LAG ID of an existing L1/L2 LAG ID

•

cannot be the same as the Administrative Key of an existing L2 LAG



When the administrative status of the LAG is disabled, no traffic is sent over the LAG. No LAG alarms are reported to WebEML. When the administrative status of the LAG is enabled, the LAG is available for, and cannot be disabled when involved in any of, the following: •

cross-connections

•

802.1Q port membership

•

selection as synchronization reference

The following features are supported at the L1 LAG level: •

Wait-To-Restore (WTR)

•

PPP RF

•

SSM

•

Packet throughput booster (PTB) See Packet throughput booster (Header compression) for supported configurations.

A WTR timer provides a mechanism to minimize the effect on LAG capacity by fast/ intermittent failures on a radio link member of the LAG. WTR time is configurable from 100 ms to 8 s. The default value is 1 s. 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. When the failure condition is cleared, the WTR period begins. When the WTR period expires, 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 parameters can be modified on the LAG itself after creation: •

Port membership

•

LAG Name

•

LAG Size

•

Wait to Restore time

•

PTB

For information about the radio parameters that can be modified in a LAG, see Provisionable radio parameters for members of L1 LAG.

167


7.2.12.5


L1 LAG lowest index port A LAG lowest index port is defined for each LAG. The lowest index port is responsible for transmitting 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 the LAG configuration scenario. Lowest index port is configured using the following: •

•

Intra plug-in −

port 5 or port 7

−

Lowest index port must have the lowest index in the LAG port membership (that is, if lowest index port is port 7, port 5, 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

−

Lowest index ports must have the lowest index in the LAG port membership (that is, 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 the 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 than used by the intra plug-in LAG.

7.2.12.6

Port membership rules During a port membership add/remove operation, the following rules apply:

168



•

Port add/remove operation rules are applied for all port add and port remove operations. Checks are performed on the entire set of ports.

•

Each radio port is eligible to be a member of only one L1 LAG.

•

The set of ports added to the LAG shall be adjacent in the slot. No holes are allowed in the L1 LAG port membership filtered by slot (that is, ports 5, 7, and 8 are not an allowed configuration).

•

Lowest index ports must always be present in the set of ports attached to the LAG.

•

The 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

−

two lowest index ports per cross plug-in L1 LAG

•

The lowest index port cannot be changed. If the lowest index port is port 7, port 5 and port 6 cannot be added to the L1 LAG.

•

For cross plug-in configuration with P8ETH cards, the maximum number of ports per slot is two. You cannot aggregate three ports on one plug-in and one port on the other plug-in.

•

For cross plug-in configuration with EASv2 electrical ports, the maximum number of ports per slot is four.

•

8x(1+0) cross plug-in L1 LAG is supported with MPT-HLC/HLS on EASv2 optical ports. For an 8x(1+0) cross plug-in LAG, only one LAG can be configured per MSS row. −

If a cross plug-in LAG with more than five ports is present, it is not possible to configure another LAG on the same row.

−

If two LAGs are present on the row, a fifth port cannot be added to either LAG.

169



•

The following rules apply for adding ports to a LAG with PTB: −

A radio that does not support L1 LAG PTB cannot be added to a LAG that has PTB enabled.

−

If a radio with PTB enabled is added to a LAG that supports PTB, but that has PTB disabled, the PTB will be disabled on the radio. The LAG PTB parameter will be unchanged.

−

If a radio with PTB disabled is added to a LAG that supports PTB, but that has PTB enabled, the PTB will be enabled on the radio. The LAG PTB parameter will be unchanged.

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.

7.2.12.6.1

L1 LAG port configuration

The following are the recommended radio configurations for an L1 Radio LAG: •

All the same radio interface type (MPT ODU, MPT-HL or MPT-HLC), except for MPT-HC/XP and MPT-HC/XP-HQAM

•

All radio interfaces configured with the same: −

option setting (except XPIC - radios with and without XPIC can be combined in the same LAG)

−

channel spacing (Reference Channel Spacing)

−

modulation scheme in fixed modulation

Configuration changes can be made when a radio interface is configured as a member of an L1 LAG port; see Provisionable radio parameters for members of L1 LAG. When one of these changes is required, it is recommended to perform a Tx mute operation, modify the configuration on both ends of the radio link, then remove the Tx mute. The LAG can operate with mixed configurations temporarily while settings are aligned. The updated configuration must comply with the recommendations for LAG creation.

170


7.2.12.6.2


Port add restrictions To add a radio direction to a Radio L1 LAG port, the radio direction must not be configured as a member of any of the following: •

cross-connection

•

port segregation

•

VLAN

•

synchronization reference

•

SSM

PPP RF cannot be enabled on the radio channel. PTB cannot be enabled on the radio channel, unless the radio supports PTB in L1 LAG. After the port has been added to a LAG, PTB cannot be enabled on the radio; it can only be enabled or disabled at the LAG level. 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 as 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. When adding an MPT-HL, lowest index port to L1 LAG, the port add restrictions do not apply. During this operation, the following actions are performed by the NE: •

Addition of the port is denied if the radio direction: −

is configured with more than 254 cross-connections

−

is a member of a 1+1 protection group

−

is an MPT ODU

•

LAG administrative state is set to Enabled

•

WebEML/craft terminal is automatically shutdown

•

operation affects traffic

Where a LAG size greater than four is supported, the lowest index port must be port 5 in the left slot in order to add a fifth port. See Cross plug-in port membership on EASv2 optical ports for port membership options.

171


7.2.12.6.3


Port removal restrictions

To remove a radio direction from an L1 LAG port, TX Mute must be provisioned as 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 an 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 not a member of any 802.1Q VLANs (except default VLAN 1)

•

L1 LAG is not a member of any port segregation

•

L1 LAG is not provisioned as a synchronization reference

•

PPP RF is disabled on the L1 LAG port

•

SSM is disabled on the L1 LAG port

If a radio is removed from a LAG that supports PTB, the PTB on the radio will be disabled, regardless of whether PTB was enabled on the LAG or on the radio before it was added to the LAG.

7.2.12.7

Supported port memberships

7.2.12.7.1

Intra plug-in port membership on EASv2 electrical ports Table 6 provides a list of supported 1+0 intra plug-in L1 LAG configurations on EASv2 electrical ports. The L1 LAG lowest index port is indicated with XL. The following radio types are supported:

172

•

MPT-HC

•

MPT-MC

•

MPT-HC-HQAM

•

MPT-XP

•

MPT-XP-HQAM


Table 6 Config


Intra plug-in L1 LAG supported 1+0 configurations on EASv2 electrical ports: single LAG LAG size

Left card (slots 3, 5, 7) P1

P2

P3

P4

P1

P2

P3

P4

EI1

1

XL

—

—

—

—

—

—

—

EI2

2

XL

X

—

—

—

—

—

—

EI3

3

XL

X

X

—

—

—

—

—

EI4

4

XL

X

X

X

—

—

—

—

EI5

1

—

—

—

—

XL

—

—

—

EI6

2

—

—

—

—

XL

X

—

—

EI7

3

—

—

—

—

XL

X

X

—

EI8

4

—

—

—

—

XL

X

X

X

EI9

1

—

—

XL

—

—

—

—

—

EI10

2

—

—

XL

X

—

—

—

—

EI11

1

—

—

—

—

—

—

XL

—

EI12

2

—

—

—

—

—

—

XL

X

7.2.12.7.2

Right card (slots 4, 6, 8)

Intra plug-in port membership on MSS-O ports Table 7 provides a list of supported 1+0 intra plug-in L1 LAG configurations on MSSO electrical ports. The L1 LAG lowest index port is indicated with XL. The following radio types are supported: •

MPT-HC

•

MPT-MC

•

MPT-HC-HQAM

•

MPT-XP

•

MPT-XP-HQAM

173


Table 7


Intra plug-in L1 LAG supported 1+0 configurations on MSS-O electrical ports

Config

LAG size

P1

P2

P3

P4

EI1

1

XL

—

—

—

EI2

2

XL

X

—

—

7.2.12.7.3

Cross plug-in port membership on EASv2 electrical ports Table 8 provides a list of supported 1+0 cross plug-in L1 LAG configurations on EASv2 electrical ports. The L1 LAG lowest index ports (active and standby) are indicated with XL. The following radio types are supported:

Table 8 Config

•

MPT-HC

•

MPT-MC

•

MPT-HC-HQAM

•

MPT-XP

•

MPT-XP-HQAM

Cross plug-in L1 LAG supported 1+0 configurations on EASv2 electrical ports: single LAG LAG size

Left card (slots 3, 5,7) P1

P2

P3

P4

P1

P2

P3

P4

EC1

2

XL

—

—

—

XL

—

—

—

EC2

3

XL

X

—

—

XL

—

—

—

EC3

3

XL

—

—

—

XL

X

—

—

EC4

4

XL

X

—

—

XL

X

—

—

EC5

2

—

—

XL

—

—

—

XL

—

EC6

3

—

—

XL

X

—

—

XL

—

EC7

3

—

—

XL

—

—

—

XL

X

EC8

4

—

—

XL

X

—

—

XL

X

174



7.2.12.7.4


Intra plug-in port membership on P8ETH optical ports Table 9 provides a list of supported 1+0 intra plug-in L1 LAG configurations for P8ETH optical ports. The L1 LAG lowest index port is indicated with XL. The following radio types are supported:

Table 9 Config

•

MPT-HL

•

MPT-HC

•

MPT-HC-HQAM

•

MPT-XP

•

MPT-XP-HQAM

Intra plug-in L1 LAG supported 1+0 configurations on P8ETH optical ports: single LAG LAG size


P6

P7

P8

P5

P6

P7

P8

OI1

1

XL

—

—

—

—

—

—

—

OI2

2

XL

X

—

—

—

—

—

—

OI3

3

XL

X

X

—

—

—

—

—

OI4

4

XL

X

X

X

—

—

—

—

OI5

1

—

—

—

—

XL

—

—

—

OI6

2

—

—

—

—

XL

X

—

—

OI7

3

—

—

—

—

XL

X

X

—

OI8

4

—

—

—

—

XL

X

X

X

OI9

1

—

—

XL

—

—

—

—

—

OI10

2

—

—

XL

X

—

—

—

—

OI11

1

—

—

—

—

—

—

XL

—

OI12

2

—

—

—

—

—

—

XL

X

7.2.12.7.5


Intra plug-in port membership on EASv2 optical ports Table 10 provides a list of supported 1+0 intra plug-in L1 LAG configurations for EASv2 optical ports. The L1 LAG lowest index port is indicated with XL.

175



The following radio types are supported:

Table 10 Config

•

MPT-HL

•

MPT-HLC

•

MPT-HLS

•

MPT-HC

•

MPT-HC-HQAM

•

MPT-XP

•

MPT-XP-HQAM

Intra plug-in L1 LAG supported 1+0 configurations on EASv2 optical ports: single LAG LAG size


P6

P7

P8

P5

P6

P7

P8

OI1

1

XL

—

—

—

—

—

—

—

OI2

2

XL

X

—

—

—

—

—

—

OI3

3

XL

X

X

—

—

—

—

—

OI4

4

XL

X

X

X

—

—

—

—

OI5

1

—

—

—

—

XL

—

—

—

OI6

2

—

—

—

—

XL

X

—

—

OI7

3

—

—

—

—

XL

X

X

—

OI8

4

—

—

—

—

XL

X

X

X

OI9

1

—

—

XL

—

—

—

—

—

OI10

2

—

—

XL

X

—

—

—

—

OI11

1

—

—

—

—

—

—

XL

—

OI12

2

—

—

—

—

—

—

XL

X

7.2.12.7.6


Cross plug-in port membership on P8ETH optical ports Table 11 provides a list of supported 1+0 cross plug-in L1 LAG configurations on P8ETH optical ports. The L1 LAG lowest index ports (active and standby) are indicated with XL.

176



The following radio types are supported:

Table 11 Config

•

MPT-HL

•

MPT-HC

•

MPT-HC-HQAM

•

MPT-XP

•

MPT-XP-HQAM

Cross plug-in L1 LAG supported 1+0 configurations on P8ETH optical ports: single LAG LAG size


P6

P7

P8

P5

P6

P7

P8

OC1

2

XL

—

—

—

XL

—

—

—

OC2

3

XL

X

—

—

XL

—

—

—

OC3

3

XL

—

—

—

XL

X

—

—

OC4

4

XL

X

—

—

XL

X

—

—

OC5

2

—

—

XL

—

—

—

XL

—

OC6

3

—

—

XL

X

—

—

XL

—

OC7

3

—

—

XL

—

—

—

XL

X

OC8

4

—

—

XL

X

—

—

XL

X

7.2.12.7.7


Cross plug-in port membership on EASv2 optical ports Table 12 provides a list of supported 1+0 cross plug-in L1 LAG configurations on EASv2 optical ports. The L1 LAG lowest index ports (active and standby) are indicated with XL. The following radio types are supported: •

MPT-HL

•

MPT-HLS

•

MPT-HLC

•

MPT-HC

•

MPT-HC-HQAM

•

MPT-XP

177



•

MPT-XP-HQAM

The configurations in rows OC9 to OC20 are supported with MPT-HLC and MPTHLS only. Ports can be added to configurations OC9 to OC12 to increase the LAG size higher than four. The maximum size of configurations OC5 to OC8 is four. The configuration in row OC20, 8x(1+0), is supported only if the following conditions are met: •

ETSI market: modem profiles with 28 MHz or 40 MHz channel spacing

•

ANSI market: modem profiles with 30 MHz or 40 MHz channel spacing

•

The MSS-4/8 shelf must be equipped with a 2.5 Gb/s or higher backplane. If an MSS shelf with a 1 Gb/s backplane is used, congestion will occur.

Table 12 Config

Cross plug-in L1 LAG supported 1+0 configurations on EASv2 optical ports: single LAG LAG size


P6

P7

P8

P5

P6

P7

P8

OC1

2

XL

—

—

—

XL

—

—

—

OC2

3

XL

X

—

—

XL

—

—

—

OC3

3

XL

—

—

—

XL

X

—

—

OC4

4

XL

X

—

—

XL

X

—

—

OC5

2

—

—

XL

—

—

—

XL

—

OC6

3

—

—

XL

X

—

—

XL

—

OC7

3

—

—

XL

—

—

—

XL

X

OC8

4

—

—

XL

X

—

—

XL

X

OC9

4

XL

X

X

—

XL

—

—

—

OC10

5

XL

X

X

X

XL

—

—

—

OC11

4

XL

—

—

—

XL

X

X

—

OC12

5

XL

—

—

—

XL

X

X

X

OC13

5

XL

X

X

—

XL

X

—

—

OC14

6

XL

X

X

X

XL

X

—

—

178



Table 12 Config


Cross plug-in L1 LAG supported 1+0 configurations on EASv2 optical ports: single LAG (Continued) LAG size


P6

P7

P8

P5

P6

P7

P8

OC15

5

XL

X

—

—

XL

X

X

—

OC16

6

XL

X

—

—

XL

X

X

X

OC17

6

XL

X

X

—

XL

X

X

—

OC18

7

XL

X

X

X

XL

X

X

—

OC19

7

XL

X

X

—

XL

X

X

X

OC20

8

XL

X

X

X

XL

X

X

X

7.2.12.7.8


Protected cross plug-in port membership configurations on P8ETH optical ports

Table 14 provides a list of supported protected cross plug-in L1 LAG configurations on P8ETH optical ports. Supported configurations contain a mixture of 1+1 and 1+0 radio directions. The L1 LAG lowest index ports (active and standby) are indicated by XL (1+0 port), ML (1+1 main port), and SL (1+1 spare port). Only MPT-HL radios are supported. Table 13 Config

Cross plug-in L1 LAG supported 1+1 configurations on P8ETH optical ports: single L1 LAG LAG size


P6

P7

P8

P5

P6

P7

P8

OP1

1

ML

—

—

—

SL

—

—

—

OP2

2

ML

X

—

—

SL

—

—

—

OP3

2

ML

—

—

—

SL

X

—

—

OP4

3

ML

X

—

—

SL

X

—

—

3

XL

M

—

—

XL

S

—

—

2

ML

M

—

—

SL

S

—

—

1

—

—

ML

—

—

—

SL

—

OP5


179


Table 13 Config


Cross plug-in L1 LAG supported 1+1 configurations on P8ETH optical ports: single L1 LAG (Continued) LAG size


P6

P7

P8

P5

P6

P7

P8

OP6

2

—

—

ML

X

—

—

SL

—

OP7

2

—

—

ML

—

—

—

SL

X

OP8

3

—

—

ML

X

—

—

SL

X

3

—

—

XL

M

—

—

XL

S

2

—

—

ML

M

—

—

SL

S

OP9

3

ML

M

M

—

SL

S

S

—

OP10

4

ML

M

M

M

SL

S

S

S

7.2.12.7.9


Protected cross plug-in port membership configurations on EASv2 optical ports

Table 13 provides a list of supported protected cross plug-in L1 LAG configurations on EASv2 optical ports. Supported configurations contain a mixture of 1+1 and 1+0 radio directions. The L1 LAG lowest index ports (active and standby) are indicated by XL (1+0 port), ML (1+1 main port), and SL (1+1 spare port). The following radio types are supported: •

MPT-HL

•

MPT-HLC

•

MPT-HC

•

MPT-HC-HQAM

•

MPT-XP

•

MPT-XP-HQAM

RPS protection without cable is not supported with L1 LAG for 1+1 MPT-HC/HCHQAM/XP/XP-HQAM: the protection must be set up using the RPS optical cable.

180


Table 14 Config


Cross plug-in L1 LAG supported 1+1 configurations on EASv2 optical ports: single L1 LAG LAG size


P6

P7

P8

P5

P6

P7

P8

OP1

1

ML

—

—

—

SL

—

—

—

OP2

2

ML

X

—

—

SL

—

—

—

OP3

2

ML

—

—

—

SL

X

—

—

OP4

3

ML

X

—

—

SL

X

—

—

3

XL

M

—

—

XL

S

—

—

2

ML

M

—

—

SL

S

—

—

3

ML

X

X

—

SL

—

—

—

3

ML

—

—

—

SL

X

X

—

OP5

1

—

—

ML

—

—

—

SL

—

OP6

2

—

—

ML

X

—

—

SL

—

OP7

2

—

—

ML

—

—

—

SL

X

OP8

3

—

—

ML

X

—

—

SL

X

3

—

—

XL

M

—

—

XL

S

2

—

—

ML

M

—

—

SL

S

OP9

3

ML

M

M

—

SL

S

S

—

OP10

4

ML

M

M

M

SL

S

S

S

7.2.12.7.10


Dual L1 LAG port membership configurations Up to two L1 LAGs are supported on a horizontal row of the MSS-4/8 shelf. The two L1 LAGs must include the same port type, that is, an optical port LAG and an electrical port LAG cannot be configured on the same row. For two LAGs to be supported, both must include four or fewer radio channels. 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.

181



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. Table 15 provides a list of supported dual 1+0 L1 LAG configurations. L1 LAG group master ports (active and standby) are indicated in bold, “A” (LAG A) and “B” (LAG B). Table 15

Dual L1 LAG Groups, Supported Mixed Plug-in 1+0 Configurations:

LAG GROUP A

LAG GROUP B

LEFT card (SLOTS 3, 5,7)

CONFI G

LAG SIZE

CONFI G

LAG SIZE

P5

P6

P7

P8

P5

P6

P7

P8

I1

1

I5

1

A

—

—

—

B

—

—

—

I6

2

A

—

—

—

B

B

—

—

I7

3

A

—

—

—

B

B

B

—

I8

4

A

—

—

—

B

B

B

B

I9

1

A

—

B

—

—

—

—

—

I10

2

A

—

B

B

—

—

—

—

I11

1

A

—

—

—

—

—

B

—

I12

2

A

—

—

—

—

—

B

B

C5

2

A

—

B

—

—

—

B

—

C6

3

A

—

B

B

—

—

B

—

C7

3

A

—

B

—

—

—

B

B

C8

4

A

—

B

B

—

—

B

B

182

RIGHT card (SLOTS 4, 6, 8)


Table 15


Dual L1 LAG Groups, Supported Mixed Plug-in 1+0 Configurations: (Continued)

LAG GROUP A

LAG GROUP B


CONFI G

LAG SIZE

CONFI G

LAG SIZE

P5

P6

P7

P8

P5

P6

P7

P8

I2

2

I5

1

A

A

—

—

B

—

—

—

I6

2

A

A

—

—

B

B

—

—

I7

3

A

A

—

—

B

B

B

—

I8

4

A

A

—

—

B

B

B

B

I9

1

A

A

B

—

—

—

—

—

I10

2

A

A

B

B

—

—

—

—

I11

1

A

A

—

—

—

—

B

—

I12

2

A

A

—

—

—

—

B

B

C5

2

A

A

B

—

—

—

B

—

C6

3

A

A

B

B

—

—

B

—

C7

3

A

A

B

—

—

—

B

B

C8

4

A

A

B

B

—

—

B

B

I5

1

A

A

A

—

B

—

—

—

I6

2

A

A

A

—

B

B

—

—

I7

3

A

A

A

—

B

B

B

—

I8

4

A

A

A

—

B

B

B

B

I11

1

A

A

A

—

—

—

B

—

I12

2

A

A

A

—

—

—

B

B

I5

1

A

A

A

A

B

—

—

—

I6

2

A

A

A

A

B

B

—

—

I7

3

A

A

A

A

B

B

B

—

I8

4

A

A

A

A

B

B

B

B

I11

1

A

A

A

A

—

—

B

—

I12

2

A

A

A

A

—

—

B

B

I3

I4

3

4


183


Table 15



LAG GROUP A

LAG GROUP B


CONFI G

LAG SIZE

CONFI G

LAG SIZE

P5

P6

P7

P8

P5

P6

P7

P8

I5

1

I9

1

—

—

B

—

A

—

—

—

I10

2

—

—

B

B

A

—

—

—

I11

1

—

—

—

—

A

—

B

—

I12

2

—

—

—

—

A

—

B

B

C5

2

—

—

B

—

A

—

B

—

C6

3

—

—

B

B

A

—

B

—

C7

3

—

—

B

—

A

—

B

B

C8

4

—

—

B

B

A

—

B

B

I9

1

—

—

B

—

A

A

—

—

I10

2

—

—

B

B

A

A

—

—

I11

1

—

—

—

—

A

A

B

—

I12

2

—

—

—

—

A

A

B

B

C5

2

—

—

B

—

A

A

B

—

C6

3

—

—

B

B

A

A

B

—

C7

3

—

—

B

—

A

A

B

B

C8

4

—

—

B

B

A

A

B

B

I9

1

—

—

B

—

A

A

A

—

I10

2

—

—

B

B

A

A

A

—

I9

1

—

—

B

—

A

A

A

A

I10

2

—

—

B

B

A

A

A

A

I6

I7

I8

184

2

3

4



Table 15



LAG GROUP A

LAG GROUP B


CONFI G

LAG SIZE

CONFI G

LAG SIZE

P5

P6

P7

P8

P5

P6

P7

P8

I9

1

I11

1

—

—

A

—

—

—

B

—

I12

2

—

—

A

—

—

—

B

B

C1

2

B

—

A

—

B

—

—

—

C2

3

B

B

A

—

B

—

—

—

C3

3

B

—

A

—

B

B

—

—

C4

4

B

B

A

—

B

B

—

—

I11

1

—

—

A

A

—

—

B

—

I12

2

—

—

A

A

—

—

B

B

C1

2

B

—

A

A

B

—

—

—

C2

3

B

B

A

A

B

—

—

—

C3

3

B

—

A

A

B

B

—

—

C4

4

B

B

A

A

B

B

—

—

C1

2

B

—

—

—

B

—

A

—

C2

3

B

B

—

—

B

—

A

—

C3

3

B

—

—

—

B

B

A

—

C4

4

B

B

—

—

B

B

A

—

C1

2

B

—

—

—

B

—

A

A

C2

3

B

B

—

—

B

—

A

A

C3

3

B

—

—

—

B

B

A

A

C4

4

B

B

—

—

B

B

A

A

C5

2

A

—

B

—

A

—

B

—

C6

3

A

—

B

B

A

—

B

—

C7

3

A

—

B

—

A

—

B

B

C8

4

A

—

B

B

A

—

B

B

I10

I11

I12

C1

2

1

2

2


185


Table 15



LAG GROUP A

LAG GROUP B


CONFI G

LAG SIZE

CONFI G

LAG SIZE

P5

P6

P7

P8

P5

P6

P7

P8

C2

3

C5

2

A

A

B

—

A

—

B

—

C6

3

A

A

B

B

A

—

B

—

C7

3

A

A

B

—

A

—

B

B

C8

4

A

A

B

B

A

—

B

B

C5

2

A

—

B

—

A

A

B

—

C6

3

A

—

B

B

A

A

B

—

C7

3

A

—

B

—

A

A

B

B

C8

4

A

—

B

B

A

A

B

B

C5

2

A

A

B

—

A

A

B

—

C6

3

A

A

B

B

A

A

B

—

C7

3

A

A

B

—

A

A

B

B

C8

4

A

A

B

B

A

A

B

B

C3

C4

3

4

7.2.12.7.11


Protected dual L1 LAG port membership configurations

Up to two protected L1 LAGs are supported on a horizontal row of the MSS-4/8 shelf. Supported configurations contain a mixture of 1+1 and 1+0 radio directions. When two protected 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. Table 16 provides a list of supported dual protected 1+1/1+0 L1 LAG configurations. Members of LAG A are indicated with an “A”. Members of LAG B are indicated with a “B”. L1 LAG lowest index ports (active and standby) are indicated in bold, “A” (LAG A) and “B” (LAG B). Main 1+1 ports are indicated with an “M”. Spare 1+1 ports are indicated with an “S”.

186


Table 16


Cross plug-in L1 LAG supported 1+1 configurations: dual L1 LAGs

Group A

Group B

Left card (slots 3, 5,7)


Config

LAG size

Config

LAG size

P5

P6

P7

P8

P5

P6

P7

P8

C1

1

C5

1

AM

—

BM

—

AS

—

BS

—

C6

2

AM

—

BM

B

AS

—

BS

—

C7

2

AM

—

BM

—

AS

—

BS

B

C8

3

AM

—

BM

B

AS

—

BS

B

C8

3

AM

—

B

BM

AS

—

B

BS

C8

2

AM

—

BM

BM

AS

—

BS

BS

C5

1

AM

A

BM

—

AS

—

BS

—

C6

2

AM

A

BM

B

AS

—

BS

—

C7

2

AM

A

BM

—

AS

—

BS

B

C8

3

AM

A

BM

B

AS

—

BS

B

C8

3

AM

A

B

BM

AS

—

B

BS

C8

2

AM

A

BM

BM

AS

—

BS

BS

C5

1

AM

—

BM

—

AS

A

BS

—

C6

2

AM

—

BM

B

AS

A

BS

—

C7

2

AM

—

BM

—

AS

A

BS

B

C8

3

AM

—

BM

B

AS

A

BS

B

C8

3

AM

—

B

BM

AS

A

B

BS

C8

2

AM

—

BM

BM

AS

A

BS

BS

C5

1

AM

A

BM

—

AS

A

BS

—

C6

2

AM

A

BM

B

AS

A

BS

—

C7

2

AM

A

BM

—

AS

A

BS

B

C8

3

AM

A

BM

B

AS

A

BS

B

C8

3

AM

A

B

BM

AS

A

B

BS

C8

2

AM

A

BM

BM

AS

A

BS

BS

C2

C3

C4

2

2

3

187


Table 16


Cross plug-in L1 LAG supported 1+1 configurations: dual L1 LAGs (Continued)

Group A

Group B

Left card (slots 3, 5,7)


Config

LAG size

Config

LAG size

P5

P6

P7

P8

P5

P6

P7

P8

C4

3

C5

1

A

AM

BM

—

A

AS

BS

—

C6

2

A

AM

BM

B

A

AS

BS

—

C7

2

A

AM

BM

—

A

AS

BS

B

C8

3

A

AM

BM

B

A

AS

BS

B

C8

3

A

AM

B

BM

A

AS

B

BS

C8

2

A

AM

BM

BM

A

AS

BS

BS

C5

1

AM

AM

BM

—

AS

AS

BS

—

C6

2

AM

AM

BM

B

AS

AS

BS

—

C7

2

AM

AM

BM

—

AS

AS

BS

B

C8

3

AM

AM

BM

B

AS

AS

BS

B

C8

3

AM

AM

B

BM

AS

AS

B

BS

C8

2

AM

AM

BM

BM

AS

AS

BS

BS

C4

2

7.2.12.8

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 a single radio is not forbidden, but is not supported.

188



•

Performance Monitoring

•

Alarm Profile

•

Radio encryption

For use of the radio encryption feature in a LAG, see the 9500 MPR WebEML User Manual.

7.2.12.9

L1 Radio LAG deletion An L1 LAG can be deleted if:

7.2.12.10

•

Administrative state is Disabled

•

no ports are members of the L1 LAG

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 an L1 LAG port, the NE QoS settings are applied to the radio port. The queue sizes are set to the default values.

7.2.12.11

L1 Radio LAG rate L1 LAG rate represents the total capacity of the L1 LAG port. The L1 LAG rate is calculated by summing 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.

189


7.2.12.12


Admission control Admission control is not performed on L1 LAG. Bandwidth of cross-connected traffic should not exceed the capacity of a single LAG port member.

7.2.12.13

Available user ports Electrical and optical ports that are not members of an L1 LAG may be used for user Ethernet or radio interface ports.

7.2.12.14

Maximum Ethernet frame length The maximum Ethernet frame length is:

7.2.12.15

•

1600 bytes for mixed TDM and Ethernet traffic

•

9728 bytes for pure Ethernet traffic

Cross-connections The maximum number of cross-connections supported by L1 LAG is 254. Cross connections that terminates on a non-ring L1 LAG port must use the multicast MAC address of the NE. Cross connections that terminate on an ERPS node where one or more of the ring ports is an L1 LAG ports must use the Unicast MAC address of the NE.

7.2.12.16

Performance monitoring Ethernet statistics related to the L1 Radio LAG direction monitors all the TDM and Ethernet traffic passing through the lowest index port. To facilitate commissioning, remote maintenance, and troubleshooting, the following L1 Radio LAG PM counters are supported: •

190

Total Number of Tx Packets



•

Total Number of Tx Bytes

•

Total Number of Tx Discarded Packets

•

Available Capacity

•

TTO Throughput

•

TDF Ratio

For a detailed description of radio PM, see section 7.18.

7.2.12.17

Port segregation Port segregation involving the L1 LAG is supported. The following port segregations involving an L1 LAG are supported:

7.2.12.18

•

segregation to user Ethernet or radio ports belonging to same card

•

segregation to user Ethernet ports or radio ports belonging to a card on the same MSS row

•

segregation of card involved in intra plug-in L1 LAG to user Ethernet port connected to Core or other P8ETH or EASv2 cards

•

segregation of card involved in intra plug-in L1 LAG to radio ports connected to Core, MPTACC, or other P8ETH or EASv2 cards

•

segregation of both cards involved in cross plug-in L1 LAG to user Ethernet port connected to Core or other P8ETH or EASv2 cards

•

segregation of both cards involved in cross plug-in L1 LAG to radio ports connected to Core, MPTACC, or other P8ETH or EASv2 cards

PPP-RF configuration PPP-RF is configured at the L1 LAG level.

7.2.12.19

SSM SSM is configured at the L1 LAG level.

191


7.2.12.20


Synchronization An enabled L1 LAG port can be selected as synchronization reference. The L1 LAG port is managed as a single logical synchronization reference. The system selects the 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 nonfaulted members of the L1 LAG. Detection of synchronization degrade on the selected reference is considered a synchronization degrade condition against the entire L1 LAG because the quality of the reference clock is supplied by the remote NE. Synchronization selection is not revertive.

7.2.13

Radio L2 LAG

Radio Link Aggregation (Radio L2 LAG) groups a set of radio ports so that the network nodes can be interconnected using multiple links to increase link capacity and availability. Figure 54

Radio L2 LAG

In this example, user traffic is split up into radio channels. Main advantages:

192

•

Throughput. The overall radio Ethernet throughput is more than 1 Gb/s (4 x 350 Mbit/s, being the value for 256QAM@56 MHz)

•

Protection. In case of a failure of one of the three channels, all the traffic is redirected on the remaining link (with a throughput of around 0.35 Gb/s). The discarded or dropped traffic is the traffic with lower priority, high priority traffic is still running on the remaining active channels.


Figure 55


Radio L2 LAG block diagram

MPT plug-in PDH Trunk 1

MPT plugin

MPT MPT plug-in

MOD300

25085

Radio L2 LAG ports are supported on MPT ODU and MPT-HL radio interfaces when a Core-E card is in use. Radio L2 LAG is supported on radio interfaces in both fixed and adaptive modulation. Radio L2 LAG is not available with the CorEvo card. Members of a radio L2 LAG port must be configured: •

All the same radio interface type

•

MPT ODU radio interface must be configured with MPT Access card, one radio interface per MPT Access card

•

MPT-HL radio interface must be configured with P8ETH card, one radio interface per P8ETH card

•

1+0 unprotected

Radio L2 LAG ports configured in Active/Standby mode are not recommended in this release of the 9500 MPR. Radio LAG size is restricted to the following: •

up to eight Radio L2 LAG ports per NE

•

up to six MPT ODU ports per Radio L2 LAG port

•

up to four MPT-HL ports per Radio L2 LAG port

PPP RF should be disabled on all radio interfaces of a Radio L2 LAG port. TMN In-Band should be cross-connected with only one radio interface of a Radio L2 LAG port. To add a radio port to a Radio L2 LAG port, the radio port must not be provisioned as a member to any of the following: •

cross-connection

193



•

VLAN

•

port segregation

•

RING

•

PPP RF enabled on the radio channel

All cross-connections, VLANs, and port segregation provisioning must be removed before adding the Radio port to a Radio L2 LAG port. After a radio port has been added to a Radio L2 LAG port, the following radio interface parameters may be modified: •

Mode (fixed, Adaptive Modulation)

•

Reference Channel Spacing

•

Modulation Scheme

•

Options

•

Link Identifier

•

Tx Power/ATPC

•

Modulation Range (in Adaptive Modulation)

•

Driving MSE (in Adaptive Modulation)

•

Remote Switching Threshold (in Adaptive Modulation)

•

Manual Operation (in Adaptive Modulation)

•

Tx Mute

•

Loopback

•

Performance Monitoring

•

Alarm Profile

After a radio port has been added to a Radio L2 LAG port, the following radio interface parameters may not be modified:

7.2.14

•

Tx and Rx Frequency

•

Shifter

•

SSM support

Transmit power control

Transmit power control is controlled using one of two modalities: •

194

Automatic Transmit Power Control (ATPC)


•

7.2.14.1


Remote Transmit Power Control (RTPC)

ATPC ATPC function automatically increases or decreases the transmit output power upon request from the downstream receiver. The downstream receiver constantly monitors Receive Signal Level (RSL), receive signal quality, and aggregate Bit Error Rate (BER) of the receive signal. When ATPC is enabled, the transmit output power will remain at its lowest level until a fade occurs (or a receive circuit alarm is detected). When a change in RSL is detected at the receive end, a command is sent to the transmit end to increase power in 0.5 dB steps, up to the maximum level if required. After the fade is over, the receive end commands the transmit power to decrease in 0.5 dB steps to the lowest level. The ATPC range (minimum and maximum limits) is variable, determined by link distance, link location, and link frequency. When ATPC is enabled, the range values (minimum and maximum) are user provisionable within the supported ATPC Range. ATPC is supported at the same time as adaptive modulation on all radios except MPT-HL.

7.2.14.2

RTPC RTPC manages the output power level in a static or fixed mode. RTPC may be preferred to ATPC when hop length or interface problems present a condition that a fixed transmit power level is preferred. The range of output power supported is band and modulation dependent.

195


7.2.15


Tx mute

Radio interfaces support manual and automatic Tx Mute. When a Tx Mute command is activated, the RF signal output of the radio interface is squelched. Tx Mute supports the following states: •

Off: Transmitter not squelched

•

Manual: transmitter squelched due to manual operation

•

Manual timed: transmitter squelched for a specified time due to manual operation

•

Auto: transmitter squelched due to an automatic operation

See Table 17 for Tx Mute of Radio interface characteristics. Table 17

Tx Mute characteristics Automatic

Manual using craft terminal

Manual using Front Panel

Supported Radio Interface

MPT ODU, MPT-HL, MPT-HLC, MPT-HLS

MPT ODU, MPT-HL, MPT-HLC, MPT-HLS

MPT-HL

Radio Main View, Tx Mute Field

Auto Local

Manual Local Manual Local Timed

Manual Local Manual Local Timed

Radio Main View Measurements tab

-100 dBm 1

-100 dBm 1

-100 dBm 1

Abnormal Condition

N/A

Tx Mute

N/A

Alarm condition

N/A

N/A

Replaceable Unit Problem

1. Radio Main View Measurement tab power level equal to “-100 dBm” indicates the transmitter is in Tx Mute.

7.2.15.1

Manual timed Tx mute You can provide a duration for a manual local Tx mute to avoid the risk of a permanent disconnection from the network.

196



The following options appear in the Tx Mute field: •

Manual Local: Choose On to mute the transmitter manually, or Timed to provide a duration that the transmitter will be muted.

•

Timeout: Length of time the transmitter will be muted. The default duration is 30 minutes. The maximum is 2 days, 0 hours, 0 minutes.

Note: If the MSS restarts, the timeout counter will be lost. If the MPT restarts, the timeout will be retained.

After the Timed Tx Mute command has been applied, the NE provides the remaining duration of the command to the managing system. If the NE is reachable from the managing system after the execution of a Timed Tx Mute command, you can reconfigure the timeout. The new timeout will overwrite the previous value and the timer starts again from the current timestamp. It is not possible to configure a timed Tx mute and a non-timed Tx mute at the same time.

7.2.16

Latency optimization

For latency-sensitive applications, it is possible to use a dedicated configuration with the goal of minimizing latency. This configuration is available across all radios except ODU300 and MPT-HL. It is applicable to TDM and Ethernet traffic; the latency improvement is in the range of about 0.15 ms, regardless of modem profile used and packet size. Configuration is performed in the configuration file with an MSS topology. Configuration is performed in MCT with an MPR-e topology; see the 9500 MPR MCT User Manual.

197


7.2.17


AES encryption management

Traffic on MPT-HC/HC-HQAM, MPT-XP/XP-HQAM, MPT-HLS or MPT-HLC 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 JUSM. The MPT generates a 256-bit AES key based on the passphrase. The encryption is disabled by default. An encryption license is required. If encryption is enabled on only one radio in a link, or if the passphrases on two radios in a link do not match, a radio encryption mismatch alarm is raised. A radio encryption mismatch alarm is not a part of the switching criteria for L1 LAG or ERPS.

7.2.18

XPIC

Cross-Polarized Interference Cancellation (XPIC) provides the ability two operate two links on the same radio channel frequency, one using vertical polarization and the other using the horizontal polarization. XPIC typically provides 20 dB improvement in polarization discrimination. The actual improvement will depend on the native discrimination provided by the antenna alignment and any reduction of this discrimination caused by atmospheric effects (fading). The XPIC feature supports the following radio configurations: •

Single 2x(1+0) XPIC

•

Double 2x(1+1) HSB XPIC

See Figure 56 for an example of the single 2x(1+0) XPIC configuration. See Figure 57 for an example of the double 2x(1+1) HSB co-channel XPIC configuration.

198


Figure 56


Single 2+0 XPIC

199


Figure 57


Double 2x(1+1) HSB co-channel XPIC

XPIC is supported on the MPT-HC/HC-HQAM/XP/XP-HQAM, MPT-HLS and MPTHLC only. XPIC functionality is implemented on: •

MPT-HC/XP by installing the XPIC+RPS external module

•

MPT-HLC or MPT-HLS by applying an XPIC license

•

MPT-HC-HQAM/XP-HQAM by installing an RTU license, which can be downloaded.

Both MPTs configured in XPIC configuration must be configured with the same radio parameters:

200

•

Channel Spacing

•

Modulation mode (Fixed/Adaptive)

•

Modulation (in Fixed Modulation)

•

Reference Modulation (in Adaptive Modulation)

•

Range of modulations (in Adaptive Modulation)



•

TX frequency

•

RX frequency

•

Shifter value

The following radio features are supported on channels configured with XPIC: •

Adaptive modulation

•

ATPC

•

Radio L2 LAG

In the ANSI market, XPIC is supported using the following: •

•

•

•

Radio Channels: −

Lower 6 GHz

−

Upper 6 GHz

−

7 GHz

−

8 GHz

−

11 GHz

−

15 GHz

−

18 GHz

−

23 GHz

−

28 GHz

−

38 GHz

Modulation Schemes: −

64 QAM

−

128 QAM

−

256 QAM

−

512 QAM (MPT-HC-HQAM, MPT-XP-HQAM, and MPT-HLC only)

−

1024 QAM (MPT-HC-HQAM, MPT-XP-HQAM, and MPT-HLC only)

−

2048 QAM (MPT-HC-HQAM and MPT-XP-HQAM only)

Radio Channel Spacing: −

30 MHz

−

40 MHz (MPT-HC/HC-HQAM/XP/XP-HQAM only)

−

50 MHz (MPT-HC/HC-HQAM/XP/XP-HQAM only)

−

60 MHz (MPT-HLC only)

Radio L2 LAG

201



For the ETSI market, see the Alcatel-Lucent 9500 MPR Technical Specifications for Full Indoor Applications and the Alcatel-Lucent 9500 MPR Technical Specifications for Split Mount Applications.

202



If space diversity with the receiver diversity combiner is in use with XPIC on an MPTHLC, the following maximum antenna distances apply:

7.2.19

•

38 m for 30 MHz channel spacing

•

20 m for 60 MHz channel spacing

XPIC automatic remote TX mute Automatic remote TX mute is an automatic procedure, which starts in a receiver failure condition to continue ensuring the working of the remaining link. This procedure is automatically disabled when at least one of the radio directions involved in the XPIC association is configured in a protected scheme. In case of double failure conditions; for example, two MPT cards fail or XPIC module card fail alarms affecting both channels having the same polarization, it is acceptable to lose all traffic for both polarizations, because the cancellation function may not work. Under some specific conditions (see Root causes), the remote transmitter signal on the failed link is muted to prevent unwanted interference on the remaining receiver. Figure 58 explains this occurrence.

Figure 58

Automatic remote TX mute

Near end

Far end MPT-H

NE

X

MPT-V 1 MPT-V failure

MPT-H

NE MPT-V 2 TX mute needed 22835

The MPT-V on the Far end is squelched, because the MPT-HC/XP on the Near end could not correctly cancel the V component from the co-polar signal. Upon specific conditions occurrence on one MPT, the MSS (near end) redirects the automatic remote transmitter mute request over the correct radio direction, that is, over its associated channel. When these specific conditions are no longer present and the related alarms are cleared, then the MSS (near end) redirects the automatic remote transmitter unmute request over the same link.

203



As soon as the MPT (far end) receives an automatic mute/unmute remote request, it communicates this information to the MSS. The MSS mutes/unmutes the MPT corresponding to the associated channel, which is the radio direction associated with the one from which the command has been received. Figure 59 explains the complete loop.

Figure 59

Automatic remote TX mute complete loop

Near end

Far end

2

3

4

MPT-H

MPT-H

XPIC Associated channels

XPIC Associated channels

X

MSS

5

MSS

MPT-V 1

X

1 Root cause

4 XPIC automatic TX mute request enable

2 XPIC automatic remote TX mute

5 XPIC automatic Mute

3 Air frame: automatic remote tx mute enable

6 tx mute action

MPT-V 6 7

7 Automute notification

22834

7.2.19.1

Root causes The procedure of automatic remote transmitter mute is activated (sending message number 2 in Figure 59) on the radio interface associated in XPIC mode to the other if one of the following alarms (listed in priority order, starting from higher priority one) is activated:

204

•

MPT Power Supply Failure alarm (used only if MPT is connected to MPT Access unit)

•

MPT/EAS access card fail (used only if the two MPTs associated in XPIC mode are connected to two different EAS/MPT access peripherals)

•

ICP



•

MPT card fail

•

XPIC module card fail

The procedure is automatically activated when both radio directions involved in XPIC mode raise XPIC cable loss alarms. In case of monodirectional XPIC cable loss (alarm associated with only one radio direction involved in XPIC mode), the procedure does not start. If an associated alarm is active in both radio directions involved in XPIC mode (indicated by the Associated channel parameter), then the procedure is performed considering the higher priority alarm. This means that the procedure is activated on the radio interface associated in XPIC mode to the one raising the higher priority alarm. If the same alarm (including XPIC cable loss) is active in both radio directions involved in XPIC mode, then the procedure is activated only on one channel. Automatic remote transmitter mute request is directed toward the V polarization channel to mute the H channel. If the XPIC cable loss alarm and another alarm, from the root causes list, is present in both radio directions involved in XPIC mode, then the procedure is activated considering this other alarm. This means that the procedure is activated on the radio interface associated in XPIC mode to the one raising this alarm. The same procedure is applied for the automatic remote transmitter mute disable, when alarms above are cleared. In case the alarm priority changes, then a procedure is activated to disable the previous remote transmitter mute and another one to enable a new remote transmitter mute for the other polarization. Root alarms are considered valid only if the corresponding MPT is considered in service condition, in order to avoid spurious requests during the startup/configuration phase.

7.2.20

Radio transceivers

The following types of RF transceiver types are available: •

Outdoor Units: −

Microwave Packet Transport - High Capacity (HC/HC-HQAM) and Microwave Packet Transport - eXtended Power (XP/XP-HQAM) (MPT ODU)

205



− •

7.2.21

Microwave Packet Transport - Medium Capacity (MPT-MC (ETSI market only))

Indoor Units: −

Microwave Packet Transport - Long Haul (MPT-HL (ANSI market only))

−

Microwave Packet Transport - Long Haul Cubic (MPT-HLC (ANSI market only))

−

Microwave Packet Transport - Long Haul Slim (MPT-HLS (ETSI market only))

MPT ODU

MPT-MC/HC/HC-HQAM/XP/XP-HQAM/9558HC (MPT ODU) is a multipurpose split mount ODU to address any microwave application. The unit is optimal for urban links: it is extremely compact in size providing 314 Mb/s maximum capacity. MPT ODU can be deployed in stand-alone configuration (MPR-e), with an MSS-1c, or in a split mount solution connected to an MSS. •

Up to eighteen MPT ODU connected to MSS-8

•

Up to fourteen MPT ODU connected to MSS-4

•

Up to six MPT ODU connected to MSS-1

•

Up to two MPT ODU connected to MSS-1c

9558HC supports the 5.8 GHz Unlicensed frequency band in the ANSI market. MPT-XP is very high power version of MPT-HC. The unit provides additional transmit power for some modulations when compared with MPT-HC. For supported modulations and frequencies, see the 9500 MPR Frequency Plan for MPT Outdoor Transceivers. For additional details, see Microwave packet transport outdoor unit (MPT ODU) unit data sheet. The external diplexer included in the available branching assemblies refers to ITU– R F.385, 386 and RF special customers channeling with Tx/Rx separation. Each branching box diplexer is a 3-port passive device with two band–pass filters as described in Figure 60.

206


Figure 60


Branching box block diagram

An example of the arrangement between filters on the same branching device is shown in Figure 61. Figure 61

Branching box band-pass detail

Note: f1, f2, f3 and f4 frequencies of the external diplexers see the extreme channel frequencies and not to the cut–off frequencies of the filters.

MPT-HC/HC-HQAM/XP/XP-HQAM transceivers can be deployable in three hardware configurations to optimize radio configuration growth scenarios.

207



MPT-HC/XP transceivers require additional hardware modules to support XPIC and RPS functions. MPT-HC-HQAM and MPT-XP-HQAM transceivers have integrated XPIC and RPS functions. XPIC is supported by an RTU. Hardware configurations are as follows: •

MPT-MC/HC/XP without optional XPIC or RPS: supports 1+0 Not protected, 1+1 HSB, 1+1 SD, and 1+1 FD radio configurations

•

MPT-MC/HC/XP with 1+1 RPS: supports 1+0 Not protected, 1+1 HSB, 1+1 SD, and 1+1 FD radio configurations

•

MPT-HC/XP with XPIC+RPS: supports 1+0 Not protected, 1+1 HSB, 1+1 SD, 1+1 FD, 2x(1+0) XPIC, 4x(1+0) XPIC, and 2x(1+1) XPIC radio configurations

MPT-HC/HC-HQAM/XP/XP-HQAM transceivers support 1+1 RPS. MPT-HC/XP transceivers require additional hardware module to support RPS functions. MPT-HC-HQAM and MPT-XP-HQAM transceivers have integrated RPS functions. Virtual RPS is not supported for 40, 50, 56, or 60 MHz channel changing and RPS cable is mandatory. Two 1+1 RPS methods are available: •

Cabled 1+1 RPS: RPS cable is required between main and spare transceivers

•

Virtual 1+1 RPS: RPS cable is not required between main and spare transceivers

Supports Ethernet ring protection Switching when connected to MPT Access, Core, MSS-1, and MSS-O. Integrated antenna mounts, Ethernet (electrical and optical) connectivity, and power connectivity to MSS-1c/4/8 shelves simplify installation.

7.2.21.1

MPT-MC (ETSI market only) MPT-MC is similar to MPT-HC from an architecture standpoint. The only differences are: 1. MPT-MC cannot be connected in optical due to a 100m length cable limitation.

208



2. MPT-MC is not delivered with a solar shield. 3. XPIC is not supported with MPT-MC. Figure 62

MPT-MC

7.2.21.2

MPR-e (standalone MPT ODU) MPR-e is the stand alone, full outdoor application of the MPT ODU to address full Ethernet site backhauling (fix or mobile) and to address converged MPLS metro networks reducing the number of deployed equipment.

209


7.2.22


MPT-HL (ANSI market only) MPT-HL is an IDU transceiver to address long haul microwave applications providing 245 Mb/s maximum capacity. MPT-HL is deployed in an all indoor mount solution. Connects to the MSS-1 unit or a Core unit or Ethernet Access Switch (P8ETH or EASv2) housed in the MSS-4/8 shelf. •

Up to eighteen MPT-HL connected to MSS-8

•

Up to ten MPT-HL connected to MSS-4

•

Up to two MPT-HL connected to MSS-1

Supports 5.8 Unlicensed, L6, U6, UU6, 7, 8, 10.5, and 11 GHz frequency bands. Supports 32 QAM, 128 QAM, and 256 QAM fixed modulation techniques. Supports 4/16/64/128/256 QAM adaptive modulation techniques. Supports Bandwidths: 5, 10, 25, 30, and 40 MHz Supports standard and high system gain support Supports 1+0 Unprotected, 1+1 HSB, 1+1 SD, and 1+1 FD radio configurations. MPT-HL supports FEC including Reed Solomon Decoding and TCM 2D/4D. The FEC configuration is a direct consequence of the modem profile provisioned and is not configurable.

7.2.22.1

Lower 6 GHz frequency plan See 9500 MPR-A Equipping Options drawing, found in 9500 MPR-A Electronic Documentation for lower 6 GHz radio configurations and equipping options.

Table 18

Lower 6 GHz 10 MHZ channel plan

GO

RETURN

CHANNEL FREQUENCY

DESIGNATOR

CHANNEL FREQUEN CY

DESIGNATOR

5935.320

L6.D1.L

6187.360

L6.D1.H

210


Table 18


Lower 6 GHz 10 MHZ channel plan (Continued)

GO

RETURN

CHANNEL FREQUENCY

DESIGNATOR

CHANNEL FREQUEN CY

DESIGNATOR

5945.200

L6.D2.L

6197.240

L6.D2.H

5955.080

L6.D3.L

6207.120

L6.D3.H

5964.970

L6.D4.L

6217.010

L6.D4.H

5974.850

L6.D5.L

6226.890

L6.D5.H

5974.730

L6.D6.L

6236.770

L6.D6.H

5994.620

L6.D7.L

6246.660

L6.D7.H

6004.500

L6.D8.L

6256.540

L6.D8.H

6014.380

L6.D9.L

6266.420

L6.D9.H

6024.270

L6.D10.L

6276.310

L6.D10.H

6034.150

L6.D11.L

6286.190

L6.D11.H

6044.030

L6.D12.L

6296.070

L6.D12.H

6053.920

L6.D13.L

6305.960

L6.D13.H

6063.800

L6.D14.L

6315.840

L6.D14.H

6073.680

L6.D15.L

6325.720

L6.D15.H

6083.570

L6.D16.L

6335.610

L6.D16.H

6093.450

L6.D17.L

6345.490

L6.D17.H

6103.330

L6.D18.L

6355.370

L6.D18.H

6113.220

L6.D19.L

6365.260

L6.D19.H

6123.100

L6.D20.L

6375.140

L6.D20.H

6132.980

L6.D21.L

6385.020

L6.D21.H

6142.870

L6.D22.L

6394.910

L6.D22.H

6152.750

L6.D23.L

6404.790

L6.D23.H

6162.630

L6.D24.L

6414.670

L6.D24.H

211


7.2.23


MPT-HLC (ANSI market only)

MPT-HLC is an IDU transceiver to address ANSI long haul microwave applications. MPT-HLC is deployed in an all indoor mount solution. The radio connects to the MSS-1 unit or a Core unit or Ethernet Access Switch (P8ETH or EASv2) housed in the MSS-4/8 shelf. •

Up to 24 MPT-HLC can be connected to MSS-8

•

Up to ten MPT-HLC can be connected to MSS-4

•

Up to two MPT-HLC can be connected to MSS-1

Supports 5.8 Unlicensed, U4, L6, U6, 7, 8, 10.5, and 11 GHz frequency bands. Supports 4/16/32/64/128/256/512/1024 QAM levels, either fixed or adaptive. Supports Bandwidths: 5, 10, 25, 30, 40, and 60 MHz, depending on the frequency band and applicable regulations. Supports standard and high system gain support. Supports 1+0 Unprotected, 1+1 HSB, 1+1 SD, and 1+1 FD radio configurations. A second receiver is available with a diversity combiner. The MPT-HLC includes integrated XPIC capability. It is able to host a diversity combiner, which provides a second receiver. The MPT-HLC with the diversity combiner is identified by a diversity part number; see MPT-HLC transceiver (ANSI market only) unit data sheet.

7.2.23.1

Frequency plans See the 9500 MPR-A Equipping Options drawing, found in the 9500 MPR-A Electronic Documentation, for radio configurations and equipping options.

7.2.24

MPT-HLS (ETSI market only) 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.

212



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 L4, U4, L6, U6, 7, 8, 10, 11 GHz. The MPT-HLS transceiver is only available connected to an MSS-1, MSS-4, or MSS8. MPR-e mode is not available. The MPT-HLS can be connected to the Core or to an EASv2 card. 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 base-band 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.

213


Figure 63


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)


MPT-HLS unit Tx branching filters (lower subrack)

24003

Table 19

Frequency plan for MPT-HLS (ETSI market)

Band (GHz)

Frequency range (GHz)

Recommendation

Channel separation (MHz)

L6

5.925-6.425

ITU-R F.383-9, CEPT T/R 14-01

29.65

L6

5.925-6.425

ITU-R F.383-9, CEPT T/R 14-01

59.3

U6

6.425-7.125

ITU-R F.384-11, CEPT T/R 14-02

40

U6

6.440-7.080

ITU-R F.384 (IRAN)

40

U6

6.425-7.125

ITU-R F.384-11, CEPT T/R 14-02

30

U6

6.425-7.125

ITU-R F.384-11, CEPT T/R 14-02

60

214


Table 19


Frequency plan for MPT-HLS (ETSI market) (Continued)

Band (GHz)


Recommendation


7

7.11-7.44

ITU-R F.385 ANNEX 3 L

28

7

7.44-7075

ITU-R F.385 ANNEX 3 H

28

7

7.428-7.897

ITU-R F.385 ANNEX 4

28

7

7.425-7.725

ITU-R F.385 ANNEX 1

28

7

7.11-7.44

ITU-R F.385 rec. 1 L

28

7

7.24-7.56

ITU-R F.385 rec. 1 M

28

7

7.41-7.74

ITU-R F.385 rec. 1 H

28

7

7126.5-7420

ITU-R F.385 (HONDURAS)

28

7

7.431,5-7.718,5

7.4-7.7 GHz (MEXICO)

28

7

7.142-7.408

ITU-R F.385-6

28

7

7263.5-7536.5

ITU-R F.385-7 (SUDAN)

28

7

7.125-7.425

ITU-R F.385 CEPT T/R 0206

56

7

7.425-7.725


56

8

7.725-8.275

ITU-R F.386 ANNEX 6

29.65

8

7.725-8.275

ITU-R F.386 ANNEX 6

59.3

8

7.725-8.275

ITU-R F.386 ANNEX 1

30

8

7.725-8.275

ITU-R F.386 ANNEX 1

60

8

7.9-8.4

ITU-R F.386 ANNEX 3

28

8

7.9-8.4

ITU-R F.386 ANNEX 3

56

8

8,275-8,5

ITU-R F.386 ANNEX 2

28

8

8,275-8,5

ITU-R F.386 ANNEX 2

56

8

8,025-8,5

ITU-R F.386 ANNEX 5

28

8

7,725-8,275


56

215


Table 19


Frequency plan for MPT-HLS (ETSI market) (Continued)

Band (GHz)


Recommendation


8

8,275-8,5


56

10,5

10,0-10,68

ITU-R F.746

28

10,5

10,0-10,68

CEPT 12/05

28

10,5

10,0-10,68

CEPT 12/05

56

11

10.675-11.7

ITU-R F.387 -10 CEPT 12-06

40

11

10.7-11.7

ITU-R F.387 -10 CEPT 12-06

28

11

10.7-11.7

ITU-R F.387 -10 CEPT 12-06

56

216


7.2.25


Radio capacity, channeling and modulation

See the following documents: •


•


•

9500 MPR-A MPT-HL Engineering Specifications

•

9500 MPR-A ODU300 Engineering Specifications Note: The 512/1024/2048 QAM modulations can be selected in fixed modulation, but it is not recommended to use these configurations: only adaptive modulation is supported. The 2048 QAM modulation can be selected for the 25, 28, and 38 GHz bands, but is not recommended: these configurations are not supported.

7.2.26

Monodirectional links

For the management of mono-directional radio links, different configurations are needed on each side of the link. On the node where the link works in Tx only: •

ATPC, ACM should not be enabled: they cannot work

•

LAG L1, Ring should not be created: they cannot work

•

Radio PM should not be enabled: they work Rx side

•

Link Identifier should not be enabled: it works Rx side

•

PPP must be disabled (otherwise a PPP Failure alarm will be raised)

•

For monodirectional links with the MPT-HLS, the space diversity combiner should not be equipped on the transmitter side.

•

For monodirectional links with the MPT-HLS, the RF switch should be mounted and connected.

•

“No Rx Radio Alarms” alarm profile must be configured in the radio panel (otherwise all the Rx Radio alarms will be raised)

On the node where the link works in Rx only: •

Transmitter must be muted with a TX Mute command

•

ATPC, ACM should not be enabled: they cannot work

217


7.2.27


•

LAG L1, Ring should not be created: they cannot work

•

PPP must be disabled (otherwise a PPP Failure alarm will be raised)

•

For monodirectional links with the MPT-HLS, the space diversity combiner should be equipped only on the receiver side.

•

For monodirectional links with the MPT-HLS, the RF switch should be mounted and connected.

•

“No Tx Radio Alarms” alarm profile must be configured in the radio panel (otherwise all the Tx Radio alarms will be raised)


The JF6-9558H/6933B-9500MPT (MPT-HL) unlicensed radio provide fast deployment of service with microwave radio. No license and small antennas (no FCC and Industry Canada (IC) requirements) allow immediate Turn-Up. After the license is received, the unlicensed MPT-HL radio can be easily converted to the lower 6 GHz licensed band. The JF6-9558L/6933B-9558L and JF6-9558L-D/6933B-9558L-D (MPT-HLC) unlicensed radio provides fast deployment of service with microwave radio. No license and small antennas (no FCC and Industry Canada requirements) allow immediate turn-up. After the license is received, the unlicensed MPT-HLC radio can be easily converted to the lower 6 GHz licensed band. The JF6-9558HC/6933B-9558HC (9558HC) unlicensed radio provide fast deployment of service with microwave radio. No license and small antennas (no FCC and Industry Canada (IC) requirements) allow immediate Turn-Up. The 9558HC unlicensed radio cannot be upgraded to licensed operation. Caution: Changes or modifications not expressly approved by Alcatel-Lucent could void the authority to operate the JF6-9558H/6933B-9500MPT, JF6-9558HC/6933B-9558HC, JF69558L/6933B-9558L, and JF6-9558L-D/6933B-9558L-D (unlicensed) radio.

Caution: Installation, Turn-Up, Maintenance, and Operation Instruction supplied with the JF6-9558H/6933B-9500MPT, JF6-9558HC/6933B-9558HC, JF6-9558L/6933B-9558L, and JF6-9558L-D/6933B-9558L-D (unlicensed) radio require strict adherence for continued part 15 of the FCC Rules and IC RSS-210 compliance.

218


Table 20


Unlicensed radio

Transceiver

FCC ID

Industry Canada ID

9558HC

JF6-9558HC

6933B-9558HC

MPT-HL

JF6-9558H

6933B-9500MPT

MPT-HLC

JF6-9558L

6933B-9558L

MPT-HLC

JF6-9558L-D

6993-9558L-D

See the 9500 MPR-A Equipping Options drawing, found in 9500 MPR-A Electronic Documentation for unlicensed radio configurations and equipping options. The MPT-HL/HLC and 9558HC unlicensed radio operate in the 5725-5850 Information, Scientific, and Medical (ISM) band in accordance with FCC Part 15.247 and IC RSS-210. This unlicensed radio, although operating in the same band as a spread spectrum radio, operates using narrower bandwidths than spread spectrum. Advantages, disadvantages, and antenna recommendations for the unlicensed radio follow: Advantages: •

Fast installation and Turn-Up

•

Between 6.6 — 185 Mb/s user configurable data payload capacity consisting of a combination of E1/DS1, DS3, STM-1/OC-3, and/or Ethernet traffic

•

Field convertible to lower 6 GHz licensed band (MPT-HL/HLC)

•

Field expandable to higher capacities.

•

Common network management with licensed radios.

•

Common spares and training with licensed radios

•

Adaptive Modulation - automatic interference countermeasures

Disadvantages: •

Interference from other 5725-5850 ISM band transmissions are possible

•

Operating restrictions

•

5.725 to 5.850 GHz band

•

Performance could deteriorate due to interference as the frequency band becomes congested.

Antenna Recommendations: •

Frequency – 5.8 GHz

219



•

•

Size and Type – 2, 4, 6, 8, or 10 foot parabolic; 1 or 2 foot flat panel. −

Parabolic antennas, See Table 21.

−

Flat antennas, See Table 21.

Gain and 3 dB Beamwidth

This device has been designed to operate with the antennas listed below, and having a maximum gain of 42.5 dB. Antennas not included in this list or having a gain greater than 42.5 dB are strictly prohibited for use with this device. The required antenna impedance is 50 ohms. Table 21

5.8 GHz unlicensed antenna options

PARABOLIC

FLAT

MPT-HL/HLC/9558HC

MPT-HL/HLC/9558HC

2 ft parabolic – 29 dB/6°

1 ft flat panel – 23 dB/9°


2 ft flat panel – 28 dB/3.5°


—

8 ft parabolic – 41 dB/1.5°

—

10 ft parabolic – 42.5 dB/1.2°

—

These antennas can only be used in a fixed point-to-point configuration. To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not more than that permitted for successful communication. The antennas used for this transmitter must be installed to provide a separation distance of at least 12 meters from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter. Caution: Danger of public exposure to long term RF radiated energy. When using a 1 ft flat panel antenna with a 1 watt (+30 dBm) output power, the antenna must be located in an area that does not allow the general population access to within 12 meters (5.8 Ghz) of the antenna.

Frequency Plan: •

220

For MPT-HL frequency plan for the 5.725 and 5.850 GHz unlicensed band, see Figure 64.



•

For MPT-HLC frequency plan for the 5.725 and 5.850 GHz unlicensed band, see Figure 65.

•

For 9558HC frequency plan for the 5.725 and 5.850 GHz unlicensed band, see Figure 66.

Output Power: A requirement of operating in the unlicensed band is to limit transmit output power to not more than +30.0 dBm at the antenna port. It is the responsibility of the user to transmit not more than +30.0 dBm. Note: To meet FCC part 15 requirements, output power for 9558HC 30 MHz 4QAM and 8QAM channels must not be provisioned greater than 24 dBm. This is not enforced by the user interface and is the responsibility of the operator to guarantee provisioning of the radio transmit power. For transmit power specification, refer to the 9500 MPR-A MPT-HL Engineering Specifications.

Figure 64

Frequency plan MPT-HL: 5.725 to 5.850 GHz unlicensed band (FCC Part 15 and IC RSS-210)

Transmit Channel G1 G2 G3 G4 G5

Frequency (MHz) 5730 5735 5740 5745 5750

Receive Channel G1’ G2’ G3’ G4’ G5’

Frequency (MHz) 5795 5800 5805 5810 5815

B1 B2 B3 B4 B5

5760 5765 5770 5775 5780

B1’ B2’ B3’ B4’ B5’

5825 5830 5835 5840 5845

Notes:

221



1. The drawing above shows the 5 MHz channels used by the JF6-9558H/ 5933B-9558MPT radio. Gray channels are designated “G”. Blue channels are designated “B”. Transmit and receive channels have a 65 MHz separation. 2. RF filters are centered on channels G3, B3, G3’, and B3’. 3. The flexibility of the JF6-9558H/6933B-9500MPT allows any radio to grow to 183 Mb/s without a hardware upgrade.

222


Figure 65


Frequency plan 9558HLC: 5.725 to 5.850 GHz unlicensed band (FCC Part 15 and IC RSS-210)


Frequency (MHz) 5731 5736 5741 5746 5751


Frequency (MHz) 5794 5799 5804 5809 55814

B1 B2 B3 B4 B5

5761 5766 5771 5776 5781

B1’ B2’ B3’ B4’ B5’

5824 5829 5834 5839 5844

Notes: 1. The drawing above shows the 5 MHz channels used by the F6-9558L-D/ 6933B-9558L-D radio. Gray channels are designated “G”. Blue channels are designated “B”. Transmit and receive channels have a 63 MHz separation. 2. RF filters are centered on channels G3, B3, G3’, and B3’. 3. The flexibility of the F6-9558L-D/6933B-9558L-D allows any radio to grow to 183 Mb/s without a hardware upgrade. The MPT-HLC 5.8 Unlicensed band JF6-9558L/6933B-9558L and JF6-9558L-D/ 6933B-9558L-D is not available for quote, sale, or deployment until certification is received.

223


Figure 66


Frequency plan 9558HC: 5.725 to 5.850 GHz unlicensed band (FCC Part 15 and IC RSS-210)


Frequency (MHz) 5730.5 5735.5 5740.5 5745.5 5750.5


Frequency (MHz) 5794.5 5799.5 5804.5 5809.5 5814.5

B1 B2 B3 B4 B5

5760.5 5765.5 5770.5 5775.5 5780.5

B1’ B2’ B3’ B4’ B5’

5824.5 5829.5 5834.5 5839.5 5844.5

Notes: 1. The drawing above shows the 5 MHz channels used by the JF6-9558HC/ 6933B-9558HC radio. Gray channels are designated “G”. Blue channels are designated “B”. Transmit and receive channels have a 64 MHz separation. 2. RF filters are centered on channels G3, B3, G3’, and B3’. 3. The flexibility of the JF6-9558HC/6933B-9558HC allows any radio to grow to 185 Mb/s without a hardware upgrade.

7.2.28

Radio configurations with MPR-e

The following radio configurations are available with MPR-e:

224

•

1+0 full outdoor with MPT ODU

•

1+0 repeater (with MPT-HC/XP/HC-HQAM/XP-HQAM/9558HC only)


•

7.2.29


co-channel XPIC full outdoor (with MPT-HC/XP/HC-HQAM/XP-HQAM/ 9558HC only) used to establish a 2 x (1+0) radio link.

Radio configurations with MSS-1c

The following radio configurations are available with MSS-1c:

7.2.29.1

•

1+0 in split-mount

•

2x(1+0) repeater

1+0 in split-mount configuration for MSS-1c A 1+0 configuration is setup with one MSS-1c and one MPT. See Figure 67.

Figure 67

1+0 in split-mount configuration

7.2.29.2

1+0 repeater configuration for MSS-1c A 1+0 repeater configuration can be easily setup by adding a second radio direction to the MSS-1c. This second MPT will be connected to a User Port and will run as a MPR-e. It can be a MPT-MC or MPT-HC/HC V2/HC-HQAM/XP/XP-HQAM/9558HC. See Figure 68.

225


Figure 68


2x(1+0) repeater configuration

The MPT can be connected to the MSS-1c using electrical connectivity through the User Port 2 (SynchE capability) or using optical connectivity through an optical SFP plugged on User Port 4 or User Port 3 (not available on MSS-1c variant) (both SynchE capability). A DC Power Injector box or MPT Extended Power Unit should be used to power the MPR-e. The speed of the MSS-1c User Port, on which the MPT is connected, must be set to 1000 Mb/s with SynchE enabled.

7.2.30

Typical system configurations for MSS-1c TDM over Ethernet packet node - mapping of E1/T1/DS1 TDM on Ethernet (Figure 69). Note: In this case a connected MPT is needed in order to configure the cross-connections.

TDM and Ethernet terminal packet transport E1/T1/DS1 TDM and 1 radio direction (Figure 70). TDM and Ethernet terminal packet transport E1/T1/DS1 TDM and 2 radio directions -2x(1+0) repeater (Figure 71).

226



Figure 69

TDM over Ethernet packet node - mapping of E1/T1/DS1 TDM on Ethernet

Figure 70

TDM and Ethernet terminal packet transport E1/T1/DS1 TDM and 1 radio direction

227


Figure 71


TDM and Ethernet terminal packet transport E1/T1/DS1 TDM and 2 radio directions -2x(1+0) repeater

7.3

Ethernet The system supports the following Ethernet functionality:

7.3.1

Ethernet traffic management Ethernet traffic is all the traffic entering the MPR network from user Ethernet ports. Ethernet traffic is switched using either 802.1D MAC Address Bridge, 802.1Q Virtual Bridge, or 802.1ad Provider Bridge.

7.3.1.1

802.1D (with the Core-E card only) When the system is configured in 802.1D mode all Ethernet traffic is routed according to the destination MAC address without regard to VLAN ID.

228



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. The 802.1D mode is not available with a CorEvo card.

7.3.1.2

802.1Q When the system is configured in 802.1Q mode all Ethernet traffic is routed according to the VLAN IDs. When 802.1Q mode is enabled, VLAN 1 is automatically created. All user Ethernet ports and all radio ports are members of VLAN 1. VLAN 1 is not editable. In egress VLAN 1 is always removed from all ports. The VLAN ID values configurable must be in the range 2 - 4080. The VLAN IDs already defined to cross-connect internal flows (that is, 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 with E1 tributaries not yet cross connected. The default configuration with the Core-E card is 802.1Q.

7.3.1.3

802.1ad When the NE is configured in Provider Bridge mode, the forwarding of Ethernet traffic is managed according to Service VLAN (S-VLAN). Each Service 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 is 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. S-VLAN is assigned based on User Ethernet port (Port-based service interface) regardless of the type of customer traffic (C-VLAN tagged or untagged)

229



•

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.

•

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

In the ETSI market the default configuration with the CorEvo card is 802.1ad.

7.3.1.4

Provider bridge components A bridge whose ports are all NNIs or a mixture of NNIs and UNI (port based) is supported by a single S-VLAN Component. An S-VLAN Component is a VLANaware bridge able to recognize, insert, and remove S-VLAN tags. It is managed by an S-VLAN Table and by parameters related to NNI and UNI (port based). A bridge having one or more ports configured as UNI (VLAN-based) is supported by a single S-VLAN Component and as many C-VLAN Components as the number of VLAN-based ports. A C-VLAN component is a VLAN-aware bridge able to recognize, insert, and remove C-VLAN tags. In the context of Provider Bridge management it is managed by parameters related to the UNI (VLAN-based) port, mainly to define the C-VLAN to S-VLAN mapping.

230


7.3.1.5


Ethernet frames processing

When the NE is working in Provider Bridge mode, all the switches process Ethernet frames according to S-VLAN Tag. The tag of a single tagged Ethernet frame or the outer tag of a double tagged frame is recognized as an S-VLAN Tag according to the port S-VLAN TPID.

7.3.1.6

Cross-connected flows processing

When the NE is working in Provider Bridge mode, cross-connected flows are managed as single S-VLAN tagged frames. This implies that User Ethernet ports being end-point of a cross-connection must be NNIs. The NE does not allow the set of a cross-connection not having a NNI as end-point. Ethernet LAG interfaces that are the end-point of a cross-connection must also be NNIs. You cannot change a NNI to a UNI (port based) when cross-connections are present that use the NNI as an end-point. You cannot change a NNI to a UNI (VLAN-based) when cross-connections are present that use the NNI as an end-point.

7.3.1.7

Provider Bridge ports with Ethernet LAG User Ethernet interfaces added to an Ethernet LAG can have any port type. The interface cannot belong to a member set of any S-VLAN other than S-VLAN 1. After it has been added to an Ethernet LAG, the port is no longer managed as a Provider Bridge port. When an Ethernet LAG interface is created, the default port type is NNI. When Ethernet LAG is disabled the port type parameter is kept. When a User Ethernet interface is removed from a LAG, it will be managed as a Provider Bridge port with the default port type and default parameters.

231


7.3.1.8


Bridge type change To change the NE bridge mode from 802.1D (MAC Bridge) to 802.1ad (Provider Bridge) 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 having SVLAN ID 1. The change from 802.1D to 802.1ad affects traffic in the following ways: •

TDM Cross-Connected traffic is preserved

•

untagged Ethernet traffic is preserved

•

tagged Ethernet traffic is dropped

•

TMN in-band traffic is preserved

To re-establish the tagged Ethernet traffic, the S-VLAN table must be configured with the definition of the VLANs. The change of NE bridge mode from 802.1Q (Virtual Bridge) to 802.1ad (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 C-VLAN TPID. To change the NE bridge mode from 802.1ad (Provider Bridge) to 802.1D (MAC Bridge) all defined S-VLANs must be removed. The change does not require removal of cross-connections. 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. The change of NE bridge mode from 802.1ad (Provider Bridge) to 802.1Q (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.

232



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 (VLANbased). 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. To change the bridge type from 802.1Q (Virtual Bridge) to 802.1D (MAC bridge), the content of the VLAN table and the VLAN assigned to the user Ethernet ports have to be deleted before the bridge type is changed.

233


7.3.2


MSS-1c Ethernet traffic management The Ethernet traffic is all the traffic entered the MPR network from user Ethernet ports. By MCT/NMS it is possible to define the way to manage the Ethernet traffic according to one of the following options:

7.3.2.1

•

802.1D (MAC Address bridge)

•

802.1Q (Virtual Bridge)

•

802.1ad (QinQ)

Bridge type change In case of change of the bridge type, a new configuration file must be sent to the NE (or an old file can be used).

7.3.2.2


Table 22 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:

Table 22

•

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.

Actions taken for specific reserved multicast addresses

Reserved Multicast Address

Function

Action

01-80-C2-00-00-00

Bridge Group Address

Forward

234


Table 22


Actions taken for specific reserved multicast addresses (Continued)


Function

Action

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 (used by SSM management)

Peer for Link Aggregation and ESMC Discard for OAM

01-80-C2-00-00-03

IEEE 802.1X PAE address

Discard

01-80-C2-00-00-04 01-80-C2-00-00-0D

Reserved for future standardization

Discard

01-80-C2-00-00-0E

IEEE 802.1AB LLDP multicast address

Discard

01-80-C2-00-00-0F


Discard

01-80-C2-00-00-10

All LANs Bridge Management Group Address

Forward

01-80-C2-00-00-11 01-80-C2-00-00-1F

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 01-80-C2-00-00-2F

Reserved for GARP Application

Forward

01-80-C2-00-00-30 01-80-C2-00-00-3F

CCM and LTM Group Destination MAC Addresses (IEEE 802.1ag)

Peer/Forward

7.3.3

Frame type The system supports the following Ethernet Frame types: •

Ethernet v2

•

802.3

•

802.1Q

235


7.3.4


Quality of service (QoS) The QoS feature assigns the priority for Ethernet packets according to the selected QoS mode. See Figure 72 for an overview of the QoS implementation.

Figure 72

QoS configuration

QoS feature provides eight internal queues to support different traffic priorities. The QoS function assigns Ethernet packets to one of the eight egress traffic queues.

7.3.4.1

QoS classification QoS classification determines the method the system uses to assign packet priority. QoS classification criterion is assigned at the NE level and applied to all radio and Ethernet ports. The system supports the following QoS classification modes:

7.3.4.2

•

Disabled

•

DiffServ

•

IEEE 802.1p

Disabled All Ethernet traffic has the same priority (FIFO). All packets are assigned the lowest priority queue. Disabled is the default QoS classification mode.

236


7.3.4.3


DiffServ Default Ethernet traffic QoS classification is per RFC2474. Each packet is classified based on Differentiated Service Code Point (DSCP) field in the IPv4 or IPv6 packet header to determine packet priority. DSCP values are mapped to one of five internal Forwarding Classes. DSCP values apply to the following VLAN bridge modes: •

802.1Q Virtual Bridge

•

802.1D MAC Address Bridge

When incoming packets are not IPv4 or IPv6, the packets are assigned to Q1.

7.3.4.4

IPv4 traffic class management

The system supports IPv4 Traffic class management. IPv4 Traffic management provides customization of DiffServ priority to Queue for IPv4 frames for queuing/ delivery purposes. IPv4 Traffic class management is supported on all P8ETH, EASv2, and Core user Ethernet ports, and MPT ODU radio ports. IPv4 Traffic class management is not supported on MPT-HL radio ports.

7.3.4.5

IPv6 traffic class management

The system supports IPv6 Traffic class management. IPv6 Traffic class management is used to identify and distinguish between different classes and priorities of IPv6 packets for queuing/delivery purposes. IPv6 Traffic class management is supported on all P8ETH, EASv2, and Core user Ethernet ports, and MPT ODU radio ports. IPv6 Traffic class management is not supported on MPT-HL radio ports.

237


7.3.4.6


Priority queue mapping The system supports priority queue mapping. Priority queue mapping allows a user to provision the priority queue management of Diffserv, 802.1p, and MEF-8 external traffic flows. Priority queue mapping is supported on all P8ETH, EASv2, and CSM-E user Ethernet ports and all radio ports except MPT-HL radio ports.

7.3.4.7

QoS priority value to internal forwarding class

The QoS feature allows the user to customize QoS priority values (PCP or DSCP) to internal forwarding class on a per priority value basis. QoS priority values to internal forwarding classes are provisionable using the following:

7.3.4.8

•

Internal forwarding classes FC0 through FC4 are provisionable

•

Internal forwarding classes FC5 through FC7 are not provisionable

•

Provisioned at the NE level and applied to all radio and Ethernet ports

•

QoS priority to internal forwarding classes are provisionable for the following QoS classification criterion: −

IEEE 802.1p

−

DiffServ

IEEE 802.1p Default Ethernet traffic QoS classification is per IEEE 802.1Q. Priority value is carried by Priority Code Point (PCP) field. PCP values are mapped to one of five internal forwarding classes. PCP values apply to the following VLAN bridge modes: •

802.1Q Virtual Bridge

•

802.1D MAC Address Bridge

When incoming packets do not carry a valid 802.1p priority tag (untagged frame), priority is assigned according to the following:

238



•

802.1Q Virtual Bridge: port priority

•

802.1D MAC Address Bridge: priority 1

802.1p priority values to internal forwarding classes are provisionable using the following: •

each PCP value can be mapped to only one internal forwarding class

•

multiple PCP values can be mapped to the same internal forwarding class

•

each time 802.1 p QoS classification criterion is provisioned, the default mapping between PCP values and internal forwarding classes is applied

•

default internal forwarding class values may be retrieved

•

provisioned internal forwarding class values may be restored

See Table 23 for default 802.1p to internal forwarding class mapping. Table 23

Default 802.1p QoS classification criteria to internal forwarding class

PCP

Internal Forwarding Class

Default Egress Queue

Traffic Type

N/A

7 (Highest)

Q8

TDM2TDM

N/A

6

Q7

TDM2ETH

N/A

5

Q6

TMN

111 (7)

4

Q5

Generic Ethernet

110 (6)

3

Q4

101 (5)

2

Q3

100 (4)

2

Q3

011 (3)

1

Q2

010 (2)

1

Q2

001 (1)

0

Q1

000 (0)

0 (Lowest)

Q1

Regarding Ethernet user ports all the TDM (PDH, SDH) traffic flows are assigned to Q7 egress priority queue.

239


7.3.4.8.1


DiffServ

DiffServ priority values to internal forwarding classes are provisionable using the following: •

each DSCP value can be mapped to only one internal forwarding class

•

multiple DSCP values can be mapped to the same internal forwarding class

•

when DiffServ classification criterion is provisioned, the default mapping between DSCP values and internal forwarding classes are applied

•

default internal forwarding class values may be retrieved

•

provisioned internal forwarding class values may be restored

See Table 24 for default DiffServ to internal forwarding class mapping. Table 24

Default DiffServ QoS classification criteria to internal forwarding class

PCP



Traffic Type

N/A

7 (Highest)

Q8

TDM2TDM

N/A

6

Q7

TDM2ETH

N/A

5

Q6

TMN

240


Table 24


Default DiffServ QoS classification criteria to internal forwarding class (Continued)

PCP



Traffic Type

111000 (56) Class Selector 7

4

Q5

Generic Ethernet


4

Q5

1011100 (46) EF

4

Q5


4

Q5

100110 (38) AF4 High

3

Q4

100100 (36) AF4 Medium

3

Q4

100010 (34) AF4 Low

3

Q4


3

Q4

011110 (30) AF3 High

2

Q3

011100 (28) AF3 Medium

2

Q3

011010 (26) AF3 Low

2

Q3


2

Q3

010110 (22) AF2 High

1

Q2

010100 (20) AF2 Medium

1

Q2

010010 (18) AF2 Low

1

Q2


1

Q2

001110 (14) AF1 High

1

Q2

001100 (12) AF1 Medium

1

Q2

001010 (10) AF1 Low

1

Q2


1

Q2


1

Q2

All Remaining Values

0 (Lowest)

Q1

Regarding Ethernet user ports all the TDM (PDH, SDH) traffic flows are assigned to Q7 egress priority queue.

241


7.3.4.9


Internal forwarding class to queue mapping

The QoS feature does not support customizing the mapping from internal forwarding class the egress queue. The QoS configuration tool does allow the user to view internal forwarding classes to Ethernet output queues mapping.

7.3.4.10

Scheduler type queue mapping The system supports scheduler type queue mapping. Scheduler type queue mapping allows a user to provision the scheduler of Diffserv, 802.1p, and MEF-8 external traffic flows as either High Queue Preempt (HQP) or Deficit Weighted Round Robin (DWRR) scheduling. Priority queue mapping is supported on all P8ETH, EASv2, and Core user Ethernet ports and all radio ports except MPT-HL radio ports.

7.3.4.11

Queue scheduler algorithm The QoS queue scheduler algorithm determines the method queues are serviced. The QoS queue scheduler algorithm maybe customized using the following: •

Provisioned at the NE level and applied to all radio QoS

•

Queues Q6 through Q8 are not provisionable

•

Queues Q1 through Q5 are provisionable

•

Supported scheduling algorithms: −

Deficit Weighted Round Robin (DWRR) (supported weight range: 1 to 32)

−

Strict Priority (SP)

•

Provisioned continuous with SP always applied to the highest priority queues

•

Default values may be retrieved

•

Provisioned values may be restored

See Table 25 for the default queue scheduling algorithm.

242


Table 25


Default queue scheduling algorithm

Queue

Default Scheduling Algorithm

Default Weight

Traffic Type

Q8 (Highest)

SP

N/A

TDM2TDM

Q7

SP

N/A

TDM2ETH

Q6

SP

N/A

TMN

Q5

DWRR

16

Generic Ethernet

Q4

DWRR

8

Q3

DWRR

4

Q2

DWRR

2

Q1 (Lowest)

DWRR

1

7.3.4.12

Queue size

The QoS feature allows the user to customize queue size on a per queue, per radio direction basis. Queue sizes are provisionable using the following: •

Queues Q1 through Q5 are provisionable

•

Queues Q6 through Q8 are not provisionable

•

Provisioned at the radio direction level and applied to radio QoS

•

Supported radio configurations:

•

•

−

1+0 not protected

−

1+1 FD

−

1+1 HSB/SD

−

L2 Radio LAG

Queue size supported range: −

maximum: 4034836 bytes

−

minimum: 2480 bytes

Modem profile change to one of the following parameters restores the default queue size values: −

channel spacing

243



•

−

modulation

−

adaptive modulation reference modulation

Protection configuration change: −

for 1+0 to 1+1: the spare radio channel takes the queue sizes of the main radio channel

−

for 1+1 to 1+0: main radio channel maintains the queue sizes of the main radio channel and spare radio channel takes the default queue sizes according to the configured modem profile

•

Default values may be retrieved using QoS Configuration tool

•

Provisioned values may be restored using QoS Configuration tool

An estimated maximum delay for an Ethernet frame is displayed by the QoS Configuration tool based upon the provisioned QoS values. The estimated maximum delay is calculated according to the following provisioned parameters:

7.3.4.13

•

Queue size in bytes

•

Ethernet available bandwidth of the radio channel

•

Scheduling algorithm applied to the queue

•

Weight (for scheduling algorithm DWRR)

QoS with jumbo frame While there is no physical limitation to the number of ports that can receive jumbo frames. If jumbo flows are transmitted toward the same port into two different queues, the QoS could adversely affect the jumbo frames sent to the lowest priority queue. It is recommended to forward jumbo frame only to queue Q1 (lowest priority).

7.3.4.14

QoS in the Core-E and CorEvo card Figure 73 shows an overview of the QoS implementation inside the switch.

244


Figure 73


QoS in the Core-E unit

The QoS feature of the Ethernet switch provides eight internal queues per port to support different traffic priorities. Typically the high-priority traffic experiences less delay than that low-priority in the switch under congested conditions. According to QoS mode configured in the switch, packets are mapped to the appropriate egress queue on each Ethernet/radio port. Packets are not mapped directly to egress queues. Instead packets are first mapped to one of eight internal forwarding classes according to the QoS mode selected. These internal forwarding classes are then mapped to one of eight egress queues. The eight egress queues are as follows:

7.3.4.15

•

Queue 8: TDM2TDM traffic (highest priority)

•

Queue 7: TDM2ETH traffic

•

Queue 6: TMN traffic

•

Queues 1 to 5: generic Ethernet traffic

QoS for TMN packets The system supports the setting of a DSCP and PCP value for IP packets from the TMN In-band interface. The configuration of the values is not allowed if the TMN inband interface is enabled.

245



The DSCP and PCP values allow a priority to be set for TMN management packets exiting the radio network. 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 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.

7.3.4.16

Provider Bridge QoS Provider Bridge flows can be classified for QoS based on IEEE 802.1p or DiffServ.

7.3.4.16.1

IEEE 802.1p For S-VLAN tagged and S-VLAN priority-tagged frames entering an NNI, the priority value is set by the PCP field on the S-VLAN tag. Drop eligibility is set according to the DEI of the S-VLAN tag. For untagged frames, the priority is set by the port priority. Drop eligible is set to false. For Ethernet frames entering a UNI (port-based), the priority is determined by either the port priority or the PCP field of the C-VLAN tag, depending on whether port priority or customer priority has been selected in the provider bridge parameters. If customer priority is selected and the frame is untagged, priority is determined by the port priority parameter. Drop eligibility for tagged frames is set to false unless the CFI filed of the C-VLAN tag is set to 0. Drop eligible is set to false for untagged frames. For C-VLAN tagged frames entering a UNI (VLAN-based), the priority is determined by the PCP field or the defined priority according to the priority assignment selection. For C-VLAN priority-tagged frames, the priority is determined by the PCP field. For untagged frames, the priority is determined by the port priority parameter. Drop eligibility for tagged frames is set to false unless the CFI filed of the C-VLAN tag is set to 0. Drop eligible is set to false for untagged frames. Regardless of the value of the drop eligible parameter, every Ethernet frame is considered in-profile by the QoS performed by NE components. The priority for all frames is mapped to an internal forwarding class according to the configuration of IEEE 802.1p priority to internal forwarding class mapping; see IEEE 802.1p.

246


7.3.4.16.2


DiffServ

Regardless of port type, the priority value of the DSCP field of Ethernet frames entering a User Ethernet interface is mapped to an internal forwarding class according to the configuration of IPv4/IPv6 DiffServ to internal forwarding class mapping; see DiffServ. Ethernet frames not carrying an IPv4/IPv6 packet should be assigned to the lowest priority queue. Drop eligibility is set to false. For Ethernet frames entering an NNI that are not carrying an IPv4/IPv6 packet, the priority is determined by the PCP field for S-VLAN tagged and priority-tagged frames, or by port priority for untagged frames. For Ethernet frames entering a UNI (port-based) that are not carrying an IPv4/IPv6 packet, the priority is determined by port priority or the PCP field of the C-VLAN tag, depending on the priority assignment selection. If customer priority is selected and the frame is untagged, priority is determined by the port priority parameter. For C-VLAN tagged Ethernet frames entering a UNI (VLAN-based) that are not carrying an IPv4/IPv6 packet, the priority is determined either by the PCP field of the C-VLAN tag or the defined priority, according to the priority assignment selection. For priority-tagged frames, the priority is determined by the port priority parameter. The PCP field of the S-VLAN tag of frames exiting an NNI is set as follows: •

The PCP field for S-VLAN untagged frames is set to the internal forwarding class assessed at the ingress port.

•

The PCP field for S-VLAN tagged or priority-tagged frames is remarked with the internal forwarding class assessed at the ingress port.

•

If a frame is S-VLAN untagged and is not carrying an IPv4/IPv6 packet, the S-VLAN tag PCP is determined by the priority assessed at the ingress port.

•

If a frame is S-VLAN tagged or priority-tagged and is not carrying an IPv4/ IPv6 packet, the S-VLAN tag PCP is preserved (not remarked)

Drop eligibility of S-VLAN tagged frames exiting a port is set as follows: •

False when the frame was an S-VLAN untagged frame and the ingress port was an NNI

•

False when the ingress port of the frame was a UNI (port-based)

•

False when the ingress port of the frame was a UNI (VLAN-based)

•

False when the frame was an S-VLAN tagged or S-VLAN priority tagged frame carrying an IPv4/IPv6 packet and the ingress port was an NNI

247



•

7.3.4.17

The value of the received S-VLAN tag’s DEI field when the frame was an SVLAN tagged or S-VLAN priority tagged frame not carrying an IPv4/IPv6 packet and the ingress port was an NNI

QoS for 1588v2 flows The PTP 1588v2 synchronization flows should be mapped to internal forwarding traffic class 4, which in turn maps to the highest priority queue for Ethernet traffic. If possible, no other Ethernet traffic should be mapped to forwarding class 4 and the queue should be serviced with Strict Priority scheduling. If possible, a rate limiter should be applied to 1588 traffic and a rate limiter with bandwidth equal to zero should be applied to non 1588 traffic mapped to forwarding class 4 (Queue 5).

7.3.4.17.1

Restriction applicable to 1588v2 frame size

PTP 1588v2 packets exceeding 355 bytes will be discarded.

7.3.4.18

QoS in the MPT-HC/HC-HQAM/XP/XP-HQAM The Radio QoS is implemented on the MPT-HC/HC-HQAM/XP/XP-HQAM (not on the MPT Access Card). Figure 74 shows an overview of the QoS implementation.

248


Figure 74


QoS in the MPT ODU

The QoS feature provides eight internal queues to support different traffic priorities. The QoS function assigns packets to one of the eight egress transmit queues as defined by Ethernet flow classification.

7.3.4.19

QoS in the MPT-HL The Radio QoS is implemented on the MPT-HL (not on the Ethernet Access Card). The MPT-HL radio QoS features are identical to the QoS in the MPT-HC/HC-HQAM/ XP/XP-HQAM. The QoS function inside the system is the result of a distributed implementation in the switch and Radio Interface modules. Both of these QoS functions must be correctly configured in order to get the desired behavior on Ethernet flows that will be transmitted on the Radios.

7.3.4.20

QoS with 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.

249



Q9 through Q12 are reserved for higher priority traffic that is not managed by the LAG distributor, such as cross-connected TDM flows. Table 26 describes the queues. Table 26

L1 LAG with EASv2 queue weights

Queue

Traffic type

Q12

TDM2TDM

Q11

1588v2 Future use

Q10

SDH2SDH

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

7.3.4.21

QoS in the MSS-1c Figure 75 shows an overview of the QoS implementation inside the switch.

250


Figure 75


QoS in the MSS-1c

The Quality of Service feature of the Ethernet switch provides 4 internal queues per port to support different traffic priorities. Typically the high-priority traffic experiences less delay than that low-priority in the switch under congested conditions. For each egress port according to method of QoS classification configured in the switch, the packets are assigned to each queue.

7.3.4.21.1

TDM flows classification

All the TDM traffic flows will be assigned to the highest egress priority queue (Q4).

251


7.3.4.21.2


Ethernet flows classification

For generic Ethernet flows in the switch the priority of each packet can be assigned according to the information in: •

IEEE 802.1p: the packet is examined for the presence of a valid 802.1P userpriority tag. If the tag is present the correspondent priority is assigned to the packet

Table 27

802.1P priority

Queue

110, 111

Q3 (high priority)

100, 101

Q2

000, 001, 010, 011

Q1

•

DiffServ: each packet is classified based on DSCP field in the IP header to determine the priority.

Table 28

7.3.4.21.3

IEEE 802.1p classification

DiffServ classification

DiffServ priority

Queue

111000, 110000, 101110, 101000

Q3 (high priority)

100110, 100100, 100010, 100000 011110, 011100, 011010, 011000

Q2

All remaining values

Q1

Scheduler

The scheduler algorithm cannot be configured. HQP scheduler algorithm is used on queue Q4. Deficit Weighted Round Robin (DWRR) is used on the other queues with the following weights:

252


Table 29

7.3.4.21.4


DWRR classification

QUEUE

WEIGHT

Q3 (high priority)

4

Q2

2

Q1

1

QoS with jumbo frame While there is no physical limitation to the number of ports that can receive jumbo frame, if to many 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 queue Q1 (lower priority).

7.3.4.22

QoS in the MPT with MPR-e and MSS-1c Figure 76 and Figure 77 shows an overview of the QoS implementation inside the MPT.

Figure 76

QoS in the MPT with MSS-1c

253


Figure 77


QoS in the MPT for MPR-e

The QoS feature provides eight internal queues to support different traffic priorities. The QoS function assigns the packet to one of the eight egress transmit queues. •

Queue 8 is assigned to TDM2TDM traffic (not used for MPR-e in the current release)

•

Queue 7 is assigned to TDM2Eth traffic

•

Queue 6 is assigned to TMN

Queues 1 to 5 are assigned to Ethernet traffic according to the information inside the packet as 802.1p field, DiffServ field or Ethertype (MPR-e only). All the MEF-8 ETH2ETH traffic flows in MPR-e are assigned to the Q5 egress priority queue.

7.3.4.22.1

QoS based on IEEE std. 802.1p When the 802.1p QoS mechanism is adopted, the reference is the standard “IEEE 802.1D-2004 Annex G User priorities and traffic classes”, which defines eight traffic types and the corresponding user priority values. In the Radio Interface module for generic Ethernet traffic, there are five egress queues; therefore, the mapping of the 802.1p value to a queue is as shown in

254


Table 30

7.3.4.22.2


QoS based on 802.1p priority

802.1p priority

Queue

111, 110

Q5 (higher priority)

101

Q4

100

Q3

011, 000

Q2

010, 001

Q1

QoS based on DiffServ Table 31

7.3.4.22.3

QoS based on DiffServ priority

DiffServ priority

Queue

111000, 110000, 101110, 101000


100110, 100100, 100010, 100000

Q4

011110, 011100, 011010, 011000

Q3

010110, 010100, 010010, 010000 001010, 001100, 001010, 001000, 000000

Q2

All remaining values

Q1

Scheduler

The HQP (High Queue Preempt) scheduler algorithm is used on Q8, Q7 and Q6. The other five queues can be selected by the MCT HQP for MPR-e, or the DWRR (Deficit Weighted Round Robin) algorithm. If the DWRR algorithm will be used, the weight to be assigned to each queue can be configured using MCT. By default, the DWRR algorithm is used with the following weights:

255



Table 32

7.3.5

Default weights

Queue

Weight


16

Q4

8

Q3

4

Q2

2

Q1

1

Ethernet features provisioned by craft terminal The following Ethernet features are provisioned using the craft terminal.

7.3.5.1

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.

256



When Ingress Rate Limiter is applied on User Ethernet interfaces of the CorEvo, the CIR and CBS values applied to the system are not independent from each other due to a granularity parameter common to both CIR and CBS configuration. The granularity parameter depends on the value of CIR and CBS configured by the operator and could result in a granularity different from the values available in the craft terminal. This behavior implies that either CIR or CBS value applied to the system can be different from the value configured by the operator. A typical scenario where this can happen is when CIR is configured with a value in its lower range and CBS is configured with a value in its higher range or vice versa. Port based Rate Limiting is supported: •

in 802.1D MAC Bridge mode

•

in 802.1Q Virtual Bridge mode

•

in 802.1ad Provider Bridge mode

•

on Core user Ethernet interfaces

•

on EAS user Ethernet interfaces

A User Ethernet interface cannot be disabled when the Port based Rate Limiting feature is enabled on the interface. Port based Rate Limiting is provisioned using the craft terminal. In cases where 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.

7.3.5.2

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.

257



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 are provisionable 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 mode

•


•


•


•

on P8ETH user Ethernet interfaces

•

on EASv2 user Ethernet interfaces

Storm Control is enabled/disabled for all supported frame types at one time. A User Ethernet interface cannot 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.

7.3.5.3

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

258



•



CIR is configured in the range from 64 Kbit/s to 32 Gb/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: •


•


•


•


•

up to eight VLAN IDs per user Ethernet interface

A User Ethernet interface cannot 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. 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.

7.3.5.4

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.

259



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


•


CIR is configured in the range from 0 Kbit/s to 1 Gb/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

•

2 Mbytes

•

4 Mbytes

•

8 Mbytes

•

16 Mbytes

Per-VLAN Per-COS Rate Limiter is supported:

260

•


•


•




•


•

Up to 16 Rate Limiters can be activated per User Ethernet interface, up to 32 Rate Limiters can be activated on a Core card and up to 32 Rate Limiters can be activated on each P8ETH or EASv2 card.

A User Ethernet interface cannot 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: Possibility of service interruption. 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. The value Any can be used as the VLAN ID: the tagged Ethernet flow will be classified according to the value of the PCP field only. The CT and the NE perform a check to verify that two Per-VLAN Per-CoS rate limiters do not exist on the same port where one is identified by PCP value only and another is identified by a specific VLAN ID and the same PCP value as shown in Figure 78. Figure 78

Per-VLAN Per-COS rate limiters with duplicate PCP values Up to 10 Mbps

Per-Cos Rate Limiter

Any VLAN PCP=5 CIR=10M


VLAN 100 PCP=5 CIR=5M

X

Up to 5 Mbps

23030

A check is also performed to verify that a Per-VLAN Per-CoS rate limiter is not created on the same port with a VLAN ID that is already in use to perform a VLAN Rate Limiter, as shown in Figure 79.

261


Figure 79


Per-VLAN Per-CoS Rate Limiter and VLAN Rate Limiter with the same VLAN ID Up to 10 Mbps

VLAN Rate Limiter

VLAN 100 CIR=10M

X

Up to 5 Mbps


VLAN 100 PCP=5 CIR=5M

23032

A check is performed to verify that a Per-VLAN Per-CoS Rate Limiter identified by PCP value only (VLAN ID = Any) is not created when there is already a VLAN Rate Limiter on the same port, as shown in Figure 80. Figure 80

Per-VLAN Per-CoS Rate Limiter with VLAN ID = Any and a VLAN Rate Limiter Up to 10 Mbps

VLAN Rate Limiter

VLAN 100 CIR=10M

X

Up to 5 Mbps


262

Any VLAN PCP=5 CIR=5M

23031


7.3.6


Ethernet features configured by enhanced configuration file The following Ethernet features can be configured using an Enhanced Configuration File.

7.3.6.1

Access control list

The system supports Access Control List. Access Control List allows a user to restrict MAC addresses allowed in the network. Enabling Access Control List feature automatically drops all MAC addresses which are not specifically provisioned by the user.

7.3.6.2

Out of range VLAN swap The system supports Out of Range VLAN swap. Out of Range VLAN swap allows transport of VLANs outside the supported range (4081-4094). The out of range VLAN ID is swapped to one supported by the system on ingress and vice versa. VLAN swapping is supported on all EAS and Core user Ethernet ports and all radio ports except MPT-HL radio ports.

7.3.6.3

Per-flow policer

The system supports scheduler type queue mapping. Scheduler type queue mapping allows a user to provision the scheduler for Diffserv, 802.1p, and MEF-8 external traffic flows as either High Queue Preempt (HQP) or Deficit Weighted Round Robin (DWRR) scheduling. Priority queue mapping is configured via configuration file. Supported on all P8ETH, EASv2, and Core user Ethernet ports.

263


7.3.6.4


Stacked VLAN (Q-in-Q) tagging

The system supports Stacked VLAN (Q-in-Q) Tagging. VLAN stacking allows all traffic from a single customer (which could be multiple VLANs) into a single VLAN simplifying management across the network. Stacked VLAN (Q-in-Q) Tagging is supported on all P8ETH, EASv2, and Core user Ethernet ports and all radio ports except MPT-HL radio ports.

7.3.6.5

VLAN remarking The system supports 802.1p remarking. VLAN remarking allows packets to be remarked specifying a different priority level in the packet header. VLAN swapping is configured via configuration file. Supported on all P8ETH, EASv2, and Core user Ethernet ports and all radio ports except MPT-HL radio ports.

7.3.6.6

VLAN swap The system supports VLAN swap. VLAN swap allows the inner and outer tags to be swapped on double tagged packets. The inner tag becomes the outer tag and vice versa. VLAN remarking is supported on all P8ETH, EASv2, and Core user Ethernet ports and all radio ports except MPT-HL radio ports. 2xE1DS1 SFP Support The system supports up to two E1/DS1 MEF-8 compliant circuit emulation signals using the 2xE1DS1 SFP. 2xE1DS1 SFP is supported on CSM-E user SFP Ethernet ports.

7.3.7

Input/output flow control The system support for 802.3x asymmetric pause frame towards the link partner.

264


7.3.7.1


Input pause feature This feature makes the auto-negotiation function willing to stop receiving traffic. When the radio input buffers approach overflow, the function sends a pause message to the link partner that is transmitting data to the radio, telling the device to temporarily stop sending data. The link partner will stop sending data if the device has and is provisioned with the Allow Option Pause function. See Figure 81.

If the link partner is either not equipped with or is not provisioned for input pause, data overflowing the registers in the radio will be lost, regardless of the provisioning for input pause in the radio. Any time there is an overflow, the radio will alarm and indicate Dropped Frames on the Performance Monitor screens.

7.3.7.2

Output pause feature

The system does not support 802.3x receive pause frames. When the system receives a pause frame, the pause frame will be dropped. Data overflowing the registers in the link partner will be lost regardless of the provisioning for output pause.

265


Figure 81


Input/output flow control block diagram

7.3.8

Reserved multicast addresses The system handles reserved multicast addresses uniquely since they are designed for layer 2 control protocols. The following actions are supported by the system:

266

•

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 33




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), Clause 57 (OAM) of IEEE 802.3, and ITU-T G.8264 (ESMC)

Peer for Link Aggregation and ESMC Discard for OAM

01-80-C2-00-00-03

IEEE 802.1X PAE address

Discard

01-80-C2-00-00-04 01-80-C2-00-00-0D


Discard

01-80-C2-00-00-0E

IEEE 802.1AB LLDP multicast address

Discard

01-80-C2-00-00-0F


Discard

01-80-C2-00-00-10

All LANs Bridge Management Group Address

Forward

01-80-C2-00-00-11 01-80-C2-00-00-1F

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 01-80-C2-00-00-2F

Reserved for GARP Application

Forward

01-80-C2-00-00-30 01-80-C2-00-00-3F

CCM and LTM Group Destination MAC Addresses (IEEE 802.1ag)

Peer/Forward

267


7.3.9


Traffic mode The user Ethernet traffic ports can be configured in either manual or automatic mode. In manual mode auto-negotiations is disabled. In automatic mode auto-negotiations is enabled. Speed, capability and flow control are negotiated between the link partners. Electrical Ethernet ports support the following parameters on a per port basis: •

Speed: 10, 100, or 1000 Mb/s

•

Capability: Full-duplex or half-duplex

•

Flow control: enable or disabled

•

Master-Slave: PHY Master or PHY Slave (SyncE Interface)

Optical Ethernet ports support the following parameters on a per port basis:

7.3.9.1

•

Speed: 1000 Mb/s

•

Capability: Full-duplex

•

Flow control: enable or disabled

•

Master-Slave: PHY Master or PHY Slave (SyncE Interface)

Auto-negotiation Auto-negotiation is not a stand-alone function, and correct operation and use of all available functions depends on the capabilities of the external customer equipment that is connected to the radio. The fact that an auto-negotiation function is checked for provisioning does not automatically mean that the function is fully operable. The device on the other end of the cable must also have the capability and be provisioned with a matching function. Auto-Negotiate details are beyond the scope of this supplement. When unsure of what functions to check or change from factory default provisioning, leave at default (all auto-negotiation functions are checked). Full auto-negotiation capability is becoming standard for manufacturers of Ethernet devices.

7.3.9.2

Allow 10, 100, and/or 1000 Mb/s half and full duplex

If in doubt as to the link speed and mode of the external device connecting Ethernet to the radio, check all boxes for speeds and modes. If you know the external Ethernet device has speed and/or mode limitations, check only the boxes that apply.

268



Caution: Half duplex capabilities are not available for the CorEvo card. The TMN interface on User Port#4 performs auto-negotiation advertising only Full-Duplex capability. Any hub or switch not supporting or not being configured to work in Full-Duplex configuration must be removed or re-configured in order to work with the TMN Port#4 interface of the CorEvo.

7.3.10

Ethernet synchronization messaging channel Ethernet Synchronization Messaging Channel (ECSM) is supported on Ethernet interfaces configured for synchronous operation mode support SSM and ESMC processing according to ITU-T G.8264. ESMC is supported on Core user Ethernet ports.

7.3.11

Ethernet connectivity fault management The system supports Ethernet Connectivity Fault Management (CFM). CFM provides the capability for detecting, verifying, and isolating connectivity failures in Virtual Bridged Local Area Networks. CFM is supported using the CLI tool.

7.3.12

TACACS+

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 SNMP, http, and telnet/SSH interfaces. Server messages for the SSH interface are discarded if the authentication or authorization is not successful since there will not be a service to display them. TACACS+ is transparent to existing 9500MPR authentication procedures. Login requests are authenticated using TACACS+ instead of the local user database, whenever TACACS+ is enabled and a configured server is available.

269



TACACS+ Authorization shall only be used to determine user membership in one of the existing 9500MPR privilege groups. Authorization of individual commands is not supported. To avoid a possible password conflict due to the same username in both the TACACS+ and local user databases, user modification of their local account password is denied when TACACS+ is enabled on the SNMP interface. If a password needs to be changed, the change can be completed by an administrator. The local user account management by an administrator is not affected by TACACS+ operation except that the administrator must be re-authenticated through TACACS+, when it is enabled on the SNMP interface and a server is available. TACACS+ Accounting is supported on a limited basis for WT-CLI and SNMP commands.

7.3.12.1

Server support The client supports a priority list of up to four TACACS+ servers with a unique server encryption key for each. 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. Only the PAP login type (cleartext username and password) is supported. The TACACS+ server must support PAP authentication. Server messages and custom prompts received in a TACACS+ response are accepted but not displayed to users.

7.3.12.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. If the connection is successful, an authentication START request is sent. The request contains the PAP username and password, the port type (snmp, http, telnet, test), and the client/manager IP address (http or snmp only).

270



If the authentication response is PASS, an authorization REQUEST to start a shell exec service is sent in order to determine the user privilege group. 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. If the authorization response does not include the command pair “vacm={administrator | craftperson | operator | viewer}”, the login procedure will fail. User authentication and authorization management by remote TACACS+ server is not compatible with SNMPv3 user management; see SNMP operating mode (SNMPv3 support). 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.

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

271



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.

7.3.12.4

Parameters for multiple notifications in a single accounting request The deferring of an accounting request is managed according to the following parameters:

7.3.12.5

•

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.

Server selection The server selection process determines the server or authentication method to be used based on the following process: The server list is searched to find the highest priority server that currently has no attempt failures (that is, 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.

272



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.

7.3.12.6

Configuration The TACACS+ management is implemented through a command in the Ethernet Features shell. The command is only supported for users with administrator privilege. The command individually enables TACACS+ for telnet/http/snmp/all ports. The command supports individual configuration of the following parameters for each server: •

index (1 to 4, 1 is highest priority)

•

IP address (IPv4 or IPv6)

•

secret key (up to 32 printable characters, default to 0)

•

port number (0 to 65535, default to 49)

•

timeout (1 to 10 seconds, default to 3)

•

retry attempt limit (1 to 3, default to 1)

Server parameters for the same index may be combined on a single line. The command can support configuration of the server holdoff time (45 to 600 seconds, default to 300). The user has the responsibility to ensure that valid settings and unique server IP addresses are assigned to each server. Invalid server configuration will result in failed server communication with no configuration warnings. The user has the responsibility to ensure that the worst case combination of number of servers, connection attempts and timeouts does not exceed the time limit for the authentication process.

273


7.3.12.7


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.

7.3.12.8

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 correct timeout settings and to confirm correct secret keys. The command is only supported for users with administrator privilege. 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. The server attempt counts are cleared for any server that receives an authentication response (authorization is not required). A server response failure is managed the same as any other authentication request.

7.3.13

Ethernet ring protection Ethernet Ring Protection (ERP) Switching is implemented according to ITU-T G.8032 specifications which specify a protection switching mechanism and the Automatic Protection Switching (APS) protocol for Ethernet ring topologies. The fundamentals of ring protection switching architectures are loop avoidance and the utilization of learning, forwarding, and address table management.

274


7.3.13.1


ERP topology An ERP topology is a collection of Ethernet Ring Nodes forming a closed physical loop. A minimum of two and maximum of sixteen Ethernet Ring Nodes are supported per ERP topology. The maximum number of ERPS topologies allowed in the NE depends on ports that make up the ring. The following rules apply: •

If both ring ports are radio interfaces, the maximum number of ERPS topologies is one.

•

If one ring port is an optical Ethernet interface and the other is a radio, the maximum number of ERPS topologies is one.

•

If the ring ports are both optical Ethernet interfaces, the maximum number of ERPS topologies is one.

Up to two ERP instances are supported per ERP topology. ERP Switching is supported in 802.1Q and 802.1ad Bridging modes. Optical Ethernet ports on the Core can be configured as Ring ports. The SFP must be provisioned. If the NE is in Provider Bridge mode, the Ethernet port must be configured as NNI. The TPID parameter of both ports in the Ring link must be the same.

275



ERP is supported using the following 1+0 unprotected radio interfaces: 1. MPT ODU connected to MPT Access (support for only one MPT-MC/HC/HCHQAM/XP/XP-HQAM when configured as Ethernet Ring port) 2. MPT ODU connected to Core-E, CorEvo, MSS-1, or MSS-O (support for up to two MPT ODU configured as Ethernet Ring ports) 3. MPT-HLC radio interfaces 4. L1 LAG ports that meet the following rules: −

the LAG must be in intra plug-in link configuration

−

only one LAG can be present on the card

−

at least one master port must be defined

−

the LAG must be composed of either 1+0 unprotected MPT ODU, with or without XPIC, or 1+0 MPT-HL radio interfaces

−

LAG size must be between 1 and 4

Supported configurations with radio interfaces as Ring ports are as follows: •

MPT ODU connected to MPT Access radio interface as one Ring port (East/ West) and MPT ODU connected to MPT Access radio interface as other Ring port (West/East)

•

MPT ODU connected to Core radio interface as one Ring port (East/West) and MPT ODU connected to Core radio interface as other Ring port (West/ East)

•

MPT ODU connected to MPT Access radio interface as one Ring port (East/ West) and MPT ODU connected to Core radio interface as other Ring port (West/East)

Supported configurations with optical Ethernet interfaces as Ring ports are as follows: •

Ethernet interface as one Ring port (East/West) and Ethernet interface as other Ring port (West/East)

Supported configurations with L1 LAGs as Ring ports are as follows:

276

•

MPT ODU 1+0 connected to an EAS (LAG size 1) as one Ring port, with an MPT ODU 1+0 connected to an EAS (LAG size 1) as the other Ring port

•

MPT ODU 1+0 connected to an EAS (LAG size 1) as one Ring port, with an Ethernet interface as the other Ring port

•

An intra plug-in L1 LAG on EAS with an N+0 MPT ODU as one Ring port, with an Ethernet interface as the other Ring port


7.3.13.2


•

An intra plug-in L1 LAG on EAS with an N+0 MPT ODU as one Ring port, with an intra plug-in L1 LAG on EAS with an N+0 MPT ODU as the other Ring port

•

An intra plug-in L1 LAG on EASv2 with an N+0 MPT-HLC as one Ring port, with an intra plug-in L1 LAG on EAS with an N+0 MPT ODU as the other Ring port

•

An intra plug-in L1 LAG on EASv2 with an N+0 MPT-HLC as one Ring port, with an intra plug-in L1 LAG on EAS with an N+0 MPT-HL as the other Ring port

•

An intra plug-in L1 LAG on EASv2 with an N+0 MPT-HLC as one Ring port, with an Ethernet interface as the other Ring port

•

An intra plug-in L1 LAG on EASv2 with an N+0 MPT-HLC as one Ring port, with an intra plug-in L1 LAG on EASv2 with an N+0 MPT-HLC as the other Ring port

Ethernet Ring port restrictions The following User Ethernet interfaces can be configured as Ring ports: •

Any optical User Ethernet interface of a Core-E. The SFP must be provisioned and the interface must be enabled.

•

Any optical User Ethernet interface of an MSS-1. The SFP must be provisioned and the interface must be enabled.

•

Any optical 1 GbEth User Ethernet interface of a CorEvo. The SFP must be provisioned and the interface must be enabled.

•

Any optical 10 GbEth/1 GbEth User Ethernet interface of a CorEvo-10G. The optical User Ethernet interface can be configured as a Ring port only when the SFP is provisioned, the interface is enabled and the speed is set to 1000 Mbit/s. A 10 GbEth/1 GbEth User Ethernet interface with the speed set to 10 Gb/s cannot be configured as a Ring port.

If the NE is in Provider Bridge mode, the Ethernet port must be configured as NNI. The TPID parameter of both ports in the Ring link must be the same. The following parameters can be changed on an Ethernet port that is part of a Ring: •

Port VLAN ID

•

Port Priority

•

Acceptable Frame Type

•

TPID

277



•

Auto-negotiation and related speed, Duplex and Flow Control parameters

•

Synchronous Ethernet operation mode and SSM

•

User Label

The following can be configured on a Ring port even if the port is disabled: •

it can be involved in a cross-connection

•

it can be in the member set of any VLAN in the VLAN table

•

it can be selected as either primary or secondary synchronization source

•

SSM protocol can be enabled: if the interface is a primary or secondary synchronization source, a Loss of ESMC alarm is raised.

EFM OAM cannot be enabled on a disabled Ring port.

7.3.13.3

Ring link Ethernet Ring Links connect two adjacent Ethernet Ring Nodes participating in the same ERP Topology.

7.3.13.4

Ring port

The Ethernet port used to construct the Ethernet Ring Link is called a Ring port.

7.3.13.5

Ring protection link (RPL) 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).

7.3.13.6

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 traffic to flow across the RPL.

278


7.3.13.7


R-APS protocol Ring Automatic Protection Switching (R-APS) protocol is used to coordinate the protection actions over the ring.

7.3.13.8

ERP instance An ERP Instance is responsible for protection of the VLANs that transport traffic over the physical ERP Topology. Up to two ERP Instances are supported per ERP Topology. Each ERP Instance is independent of the other ERP Instance. Each ERP Instance has its own RPL and RPL Owner. Additionally, each ERP Instance has its own independent R-APS protocol session using dedicated R-APS VLAN ID for protection coordination.

7.3.13.9

ERP operation The protection switching mechanism is based on the Automatic Switching protocol for Ethernet ring topologies, R-APS, and is used to coordinate the protection actions over the ring. The fundamentals of this ring protection architecture are: •

principle of loop avoidance.

•

utilization of learning, forwarding, and address table mechanisms defined in the Ethernet flow forwarding function.

Under normal operating conditions the RPL is blocked, and traffic flows on all links in the ring except the RPL. See Figure 82 for an example of an ERP Instance in normal operating condition.

279


Figure 82


Ethernet ring protection, normal operation

Under a ring link failure condition, the RPL owner is responsible to unblock the RPL. The Ring Node (or nodes) which perform local detection of the signal fail condition, put their Ring ports in a blocking state the set of VLANs assigned to the ERP Instance on the radio interface where the failure has been detected. See Figure 83 for an example of an ERP Instance in a link failure operating condition. Figure 83

280

Ethernet ring protection, single link failure



The ERP Control Process controls the forwarding function to perform the following actions: •

To disable forwarding over the set of VLANs assigned to the ERP Instance corresponding to blocked ring links.

•

To flush the learned MAC address table

Radio bandwidth is managed using the radio QoS feature. Only revertive switching mode is supported.

7.3.13.10

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

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

•

ERPS resources not configured

These defects are used as switching criteria before the defects correlation and defect persistence processing actions take place. The only exception is Modulator Fail defects which are used as switching criteria after defect persistence processing. 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

281



•

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 ring’s ports as members of that VLAN.

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

282

•

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

7.3.13.11

Two ERP instances Two ERP instances are supported on each ring’s node. Each Ring Instance has its own RPL and RPL Owner. See Figure 84 for an example of two ERP Instances in normal operating condition.

Figure 84

Two ERP instances, normal operation

283



Under a ring link failure condition, both RPL owners are responsible to unblock their RPL. The Ring Node (or nodes) which perform local detection of the signal fail condition, puts in blocking state for the set of VLANs assigned to both ERP Instances on the radio interface where the failure has been detected. Ethernet flows are managed using radio QoS. Lower priority Ethernet flows may be dropped to maintain higher priority Ethernet flows. See Figure 85 for an example of two ERP Instances in a link failure operating condition. Figure 85

Two ERP instances, single link failure

7.3.13.12

TDM traffic TDM traffic is switched according to cross-connections. In normal operation, the VLAN IDs assigned to TDM traffic are cross-connected to an ERP Instance. Under a ring link failure condition, the RPL owner is responsible to unblock its RPL. The Ring Node (or nodes) which perform local detection of the signal fail condition, puts in blocking state for the set of TDM VLANs assigned to the ERP Instance on the radio interface where the failure has been detected. VLANs used for TDM traffic cannot be used for User Ethernet traffic.

284


7.3.13.13


TMN PPPoE connections are established over each ring’s link. Flooding of Ethernet frames carrying PPPoE must be avoided by sending the frame only to the relevant Ethernet switch interface facing the radio where PPP connection has to be established. The OSPF routing protocol must be enabled on every PPP interface. The OSPF calculates the routing path breaking the loop from an IP point of view. In case of ring link failure, the PPP connection will cause a recalculation of the OSPF topology in order to have all nodes reachable. Static routes which have PPP interfaces belonging to the ring as gateway are not supported. The VLAN used to deliver TMN traffic is not blocked by any ERP Instance.

7.3.13.14

ERPS and Core protection The ERPS forwarding status (Blocked/Unblocked) is kept aligned on both the Main and the Spare Core cards to minimize the traffic hit during Core Protection switchover. 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 Fixed 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.

285


7.3.14


Jumbo frame

The system supports Jumbo frame lengths up to 9728 bytes with VLAN tag or 9724 without VLAN tag.

7.3.15

Ethernet L2 LAG The system supports 802.1ad Ethernet Link Aggregation (L2 LAG). User Ethernet ports (electrical or optical) on the same Core card or MSS-O can be provisioned as a member of an Ethernet L2 LAG port.

Figure 86

Ethernet L2 LAG block diagram example

Trunk 1

PHY PHY

PDH MPT plugin

Trunk 2

PHY PHY

MOD300

SFP SFP 25086

Ethernet L2 LAG ports support a minimum of one and maximum of four user Ethernet ports. Ethernet L2 LAG size for MSS-4/8 is restricted to the following: •

up to eight Ethernet L2 LAG ports per NE

•

up to four electrical Ethernet ports per Ethernet L2 LAG

•

up to two optical Ethernet ports per Ethernet L2 LAG

Ethernet L2 LAG size for MSS-O is restricted to the following:

286

•

up to two LAG ports per NE: either Ethernet L2 LAG or Radio L1 LAG

•

up to two electrical Ethernet ports per Ethernet L2 LAG. Ports can have PFoE enabled.

•

ports 1, 2, and 3 on the MSS-O are available for Ethernet L2 LAG membership



When a Core-E card is in use, the range for the LAG ID value is 1 to 14. When a CorEvo card is in use, the range for the LAG ID value is 1 to 12. The LACP protocol is supported. Members of an Ethernet L2 LAG port must be: •

same media type (either all electrical or optical)

•

full duplex

•

a single data rate

•

same data rate as all other members of the L2 LAG

•

provisioned either Auto negotiations enabled or disabled on all user Ethernet ports

To add a user Ethernet port to an Ethernet L2 LAG port the user Ethernet port must not be provisioned as a member to any of the following: •

cross-connection

•

VLAN

•

port segregation

If the Ethernet ports that will be part of the Ethernet L2 LAG will be used as TMN inband interfaces, the TMN in-band must be configured before the Ethernet L2 LAG is created. After the Ethernet L2 LAG has been created, the TMN in-band parameters cannot be changed. To change the TMN in-band parameters, the Ethernet L2 LAG must be removed. Note: The user interfaces that are part of the Ethernet L2 LAG will not be shown in the Associated Ethernet Ports panel of the TMN in-band interface.

All cross-connections, VLAN, and port segregation provisioning must be removed before adding the user Ethernet port to an Ethernet L2 LAG port. After a user Ethernet port has been added to an Ethernet L2 LAG port, the following user Ethernet port parameters cannot be modified: •

Link Capacity (10, 100, 1000 Mb/s)

•

Duplex Mode

•

VLAN 802.1Q port priority

•

VLAN 802.1Q port filter mode

•

Auto Negotiation Enabled/Disabled

287



•

Disable the port

•

Synchronous Ethernet Operation Mode

•

SynchE Master/Slave (electrical only)

•

SSM support

In 802.1Q virtual bridge mode, filter mode (acceptable frame type), Port VLAN ID, and port priority are provisioned at the L2 LAG level through the craft terminal. Ethernet L2 LAG and 802.1ad Provider Bridge mode are not compatible.

288


7.3.16


Packet throughput booster (Header compression) PTB uses a proprietary algorithm to compress header fields in a loss-less manner, on standard protocol fields within incoming data streams, to save radio bandwidth. PTB is supported on MPT ODU, MPT-HL, MPT-HLC and MPT-HLS. PTB is supported with the following system configurations: •

•

Bridge types: −

802.1D

−

802.1Q

−

802.1ad

TCP/IP stacks: −

IPv4

−

IPv6

•

L2 Radio or Ethernet LAG

•

Ethernet ring protection (ERP)

•

1+1 radio protection: HSB, SD, or FD (valid for RPS protection with and without cable)

•

XPIC

PTB is enabled on the MPT or LAG using the JUSM interface. PTB must be enabled on both ends of the radio link for the feature to function.

7.3.16.1

Packet throughput booster in L1 LAG PTB is available for the following:

Table 34

MPT Types Supporting L1 LAG PTB MPT Type

LAG Implementation

EASv2 MSS-O

HL

HC/XP

MC

HC-HQAM/ XP-HQAM

HLC

HLS

X

X

X

X

X

X

X

X

X

289



PTB is not supported on MPT HCv1. Mixed HCv1 and HCv2 will result in traffic integrity issues. All references to HC within PTB imply that HCv2 is used. Mixed channel spacings are not allowed on LAG PTB. Mixed MPTs of some types are supported (HC and HC-HQAM, MC and HC, HL and HLC). At the L1 LAG level, PTB is the same as PTB on a 1+0 or 1+1 radio link. PTB can be configured on the LAG only after radios have been added to the LAG and only if all radios in the LAG support PTB on L1 LAG. PTB in L1 LAG must be enabled on both ends of the radio link for it to work effectively. The minimum recommended modulation scheme when PTB is enabled are: •

16 QAM on MSS-O with 2 links HQAM/HCv2/MC or mixed configuration

•

16 QAM on EASv2 with 4 links HQAM/HCv2/MC or mixed configuration

•

16 QAM on EASv2 with 8 links HLv2 (cubic and slim) configured

•

4 QAM on EASv2 with 4 links HLv2 (cubic and slim) configured - with CS = 28, 30 and 40MHz only

The following restrictions apply to the LAG when PTB is enabled: •

SDH (STM-1/OC-3) services are not supported

•

Ethernet frames with length greater than 2000 bytes are not supported

Each MPT can carry a maximum of 1 Gbit/sec. Total LAG capacity can be 1.4 Gbit/ sec for MSS-O and 2.5 Gbit/sec with EASv2. A 200% limitation exists on the gain when the radio link is running at maximum rate.

7.3.16.2

Layer 2 header compression The following is a list of Layer 2 header fields that the algorithm can compress:

7.3.16.3

•

up to 64 destination and source MAC address pairs (dynamically learned)

•

up to 2 TPIDs corresponding to C-VLAN and S-VLAN respectively

Layer 3 header compression The following is a list of Layer 3 header fields that the algorithm can compress:

290


7.3.16.4


•

up to 64 destination and source IPv4 address pairs (dynamically learned)

•

up to 64 destination and source IPv6 address pairs (dynamically learned)

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.

7.3.16.5

Automatic fade control To guarantee delivery of compressed header fields, the Early Warning condition is used 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.

7.3.17

Performance monitoring To facilitate commissioning, remote maintenance, and troubleshooting, various Ethernet PM counters are supported by the system. The system supports Ethernet statistics counters. For a detailed description of radio PM, see section 7.18.

7.3.18

Port segregation

Port segregation provides the ability to prohibit packet flow from one port to another port. For a detailed description of port segregation, see section 7.19.

291


7.3.19


VLAN IDs

The system supports VLAN IDs in the range of (0-4080). VLAN IDs outside the supported range are dropped. VLAN IDs associated with TDM flows are accepted.

7.3.20

EFM OAM Configuration EFM OAM provides the ability to monitor the health of the network and determine the location of failing links or fault conditions. EFM OAM information is conveyed in Slow Protocol frames called OAM Protocol Data Units (OAMPDUs). OAMPDUs contain the control and status information used to monitor, test and troubleshoot OAM-enabled links. OAMPDUs are passed between peer OAM entities. When OAM is enabled, an autodiscovery protocol is launched to locate a remote Data Terminating Entity (DTE) in the network. The OAM discovery process allows a local DTE to detect OAM on a remote DTE. When OAM support is detected, both ends of the link exchange state and configuration information. If both DTEs are satisfied with the settings, OAM is established on the link. The OAM Discovery Process is kept alive by every OAMPDU received by the Local DTE regardless of the EFM OAM function they are related to. The OAM Discovery Process resets at the expiration of a 5 seconds timer which is reset at every OAMPDU reception. The loss of the Ethernet link or a failure to receive OAMPDUs for five seconds causes the discovery process to restart. DTEs may be in active or passive mode. Passive mode DTEs generally wait for the peer device to instigate OAM communications and respond to, but do not instigate, commands and queries. Active mode DTEs instigate OAM communications and can issue queries and commands to a remote device.

7.3.20.1

Supported functions

The following functions are supported by EFM OAM: •

292

Remote Loopback: the local DTE supports OAM Remote Loopback mode



Note: OAM Remote loopbacks do not generate an Abnormal Condition.

•

Link events: the local DTE supports interpreting Critical Link Events

The following functions are not supported by EFM OAM: •

Link monitoring

•

MIB variable retrieval

EFM OAM can be enabled on any electrical or optical User Ethernet interface of the Core, or EAS cards on an MSS-4 or MSS -8 and on any electrical or optical User Ethernet interface of an MSS-1 or MSS-O. The interface must be enabled to enable the EFM OAM. If ETH OAM is enabled, the interface cannot be disabled, unless the interface is configured as a Ring port. The operator cannot initiate an NE restart if an OAM Remote Loopback is present. If an NE restart is triggered with OAM Remote Loopback present, the card where the loopback was active is re-configured to recover the state present before the activation of OAM Remote Loopback. This will be traffic affecting. The following operations will trigger an NE restart. It is not recommended to perform these operations when an OAM Remote Loopback is active to avoid an effect on traffic.

7.3.20.2

•

Change of the Local IP address

•

Change of the active IP stack, activating either IPv4 or IPv6

•

SWP activation

•

MPT-HC, MPT-HL, or P8ETH conversion

Link OAM operational status The Operational Status of OAM Discovery process is displayed in the Link OAM Op. Status column of the EFM OAM Configuration window. The Operational Status values are: •

Disabled, when the EFM OAM is not enabled on the User Ethernet interface

•

Link Fault, when the Local DTE has detected an LOS of User Ethernet interface

293


7.3.20.3


•

Passive Wait (applicable only to Passive mode)

•

Active Send Local (applicable only to Active mode)

•

Send Local & Remote

•

Send Local & Remote OK

•

Operational

EFM OAM with Core protection Core protection can be configured regardless of the presence of EFM OAM on the Core or EAS cards. Information OAMPDUs are sent only by the active Core card. If an OAM Remote Loopback is present on the Core or an EAS card, the loopback should be removed before executing a Core protection switch. If a Core protection switch occurs due to automatic switching criteria (for example, in a Card Fail scenario), the card where loopback was active will be reconfigured with an effect on traffic forwarded by the card itself. The operator must remove any active loopback present on the peer equipment connected to the protected Core cards. If the peer equipment was acting as Local DTE, the OAM Remote Loopback needs to be removed on the peer equipment. If the peer equipment was acting as Remote DTE, an OAM Remote Loopback needs to be activated again on the new active Core card and, if needed, removed after the activation.

7.3.20.4

DTE parameters The following read-only parameters are displayed for the local DTE: •

Operational status: the link operational status

•

Functions supported: the functions available for the link

•

Revision: the revision number starts at zero when the link is established and increases every time the information sent by the local DTE to the remote DTE is updated

•

Max OAMPDU size: the maximum OAMPDU size supported by the remote DTE

The following read-only parameters are displayed for the remote DTE when a link is operational •

294

MAC address: source MAC address of the received OAMPDU


7.3.21


•

Mode: active or passive

•

Revision: the revision number for the remote DTE

•

Functions supported: the supported functions on the DTE

•

Vendor specific information: provided in the OAMPDU

•

Vendor OUI: provided in the OAMPDU

•

Max OAMPDU size: the maximum OAMPDU size is fixed at 1518 bytes

OAM remote loopback

If supported on the remote DTE, the local DTE can put the remote DTE into loopback mode using a Loopback Control OAMPDU. The following conditions must be satisfied in order to activate remote loopback: •

Local DTE in Active mode

•

Operational Status value is Operational

•

Remote DTE supports Remote Loopback function

•

Local DTE not in loopback mode

A Loopback Control OAMPDU requesting to enable a loopback is sent from the local DTE to the remote DTE. Upon receipt of the OAMPDU, the remote DTE enters loopback mode. Every Ethernet frame received is transmitted back on the same interface except OAMPDUs. Exchange of OAMPDUs must be maintained during a loopback state to maintain the OAM discovery process. Ethernet frames to be forwarded on the interface are dropped. The remote DTE exits loopback mode upon receiving a Loopback Control OAMPDU from the local DTE requesting to disable the loopback.

7.3.21.1

Activating OAM remote loopback A Loopback Control OAMPDU requesting to enable a loopback is sent from the local DTE to the remote DTE. Upon receipt of the OAMPDU, the remote DTE enters loopback mode.

295



Every Ethernet frame received is transmitted back on the same interface except OAMPDUs. Exchange of OAMPDUs must be maintained during a loopback state to maintain the OAM discovery process. Ethernet frames to be forwarded on the interface are dropped. The remote DTE exits loopback mode upon receiving a Loopback Control OAMPDU from the local DTE requesting to disable the loopback. Note: If a simultaneous OAM Remote Loopback request is sent by the remote DTE, it is ignored by the local DTE. The procedure to compare the source MAC addresses of the DTEs as described in Clause 57 of the IEEE 802.3 specification is not supported.

Figure 87 shows an operational link, ready to initiate a loopback. To create a loopback:

1. In the Link OAM Loopback pane, select the Start check box. 2. Click on the Apply button. The Link OAM Loopback status is updated to Remote Loopback.

296


Figure 87


Operational EFM OAM link

Figure 88 shows a loopback in operation.

297


Figure 88


Remote OAM loopback

To remove a loopback 1. In the Link OAM Loopback pane, select the Stop check box. 2. Click on the Apply button. The Link OAM Loopback status is updated to No Loopback.

298


7.3.21.2


ETH OAM alarms The following alarms can be reported:

7.4

•

OAM Discovery not completed: reported when EFM OAM is enabled on a User Ethernet interface and the OAM Discovery process is not in Operational status.

•

Critical Link Event: reported when EFM OAM is enabled on a User Ethernet interface and the interface receives an OAMPDU with at least one of the following flags set: −

Link Fault

−

Critical Event

−

Dying Gasp

Managed services and profiles The following describes the association of managed services and profiles: •

TDM2TDM – This is the typical service associated with a traditional TDM network in which E1/DS1 traffic is transported, switched and terminated inside a 9500 MPR network.

•

TDM2ETH – 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/DS1 is transported, switched and provided to an external ETH network in standard format (MEF-8).

•

SDH2SDH – This is the typical service associated with a traditional TDM network in which OC-3 traffic is transported, switched and terminated inside a 9500 MPR network.

•

ETH2ETH – This is not a real CES due to the native IP architecture of 9500 MPR. Ethernet traffic is directly managed by the L2 switch on the Core board.

299


7.4.1


TDM2TDM

Definition: This service identifies a flow inside MPR network, in which E1/DS1 is transported, switched and terminated. Application: Typical microwave 2G back hauling application, in which E1/DS1s are terminated before entering into aggregation network. Figure 89

TDM2TDM flow diagram

7.4.2

TDM2ETH Definition: E1/DS1 TDM input signals are packetized according to MEF8 standard; E1/DS1s are transported, switched and provided to an external ETH network in standard format (MEF-8). Application:

300

•

Typical microwave 2G back hauling application, in which E1/DS1s are terminated before entering into aggregation network, where aggregation network is a packet network. E1/DS1s are not terminated at the end of the microwave back hauling and an end-to-end circuit emulation services could be established between 9500 MPR and the service router in front of BSC/ RNC

•

9500 MPR without ODU (MSS-8 or MSS-4 stand alone) provides the same level of feature of a site aggregator box, grooming together different services (in this particular case E1/DS1 TDM) into the common Ethernet layer.


Figure 90

TDM2Eth flow diagram

Figure 91

TDM to TDM STM-1 Flow Diagram

7.4.3


SDH2SDH Definition: This service identifies a flow inside MPR network, in which OC-3 is transported, switched and terminated. Application: Typical microwave 2G back hauling application, in which OC-3s are terminated before entering into aggregation network.

7.4.4

ETH2ETH Definition: Ethernet traffic is transported and switched automatically by the standard auto-learning algorithm of the built-in MPR 10 Gbit Ethernet switch.

301



Application: Typical microwave 3G back hauling/WiMax application, in which transport of Ethernet packets coming from base stations is requested. Figure 92

Eth to Eth flow diagram

7.4.5

TDM and Ethernet traffic management Three kinds of traffic management have been identified: •

TDM2TDM (9500 MPR→ 9500 MPR, internal to the MPR network)

•

TDM2ETH (9500 MPR → TDM to Ethernet)

•

ETH2ETH (Ethernet to Ethernet)

The first two profiles meet MEF8 standard. Figure 93

302

Traffic profiles


7.4.5.1


Case 1 for E1/DS1/DS3 (TDM2TDM)

The E1/DS1/DS3 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 module are both internal to the 9500 MPR network. The Circuit Emulation Service is TDM2TDM in Node 1 and Node 2. The Cross connections to be implemented are PDH-Radio type.

7.4.5.2

Case 1 for STM-1/OC-3 (SDH2SDH) The STM-1/OC-3 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 module are both internal to the 9500 MPR network. The Circuit Emulation Service is SDH2SDH in Node 1 and Node 2. The Cross connections to be implemented are SDH-Radio type.

7.4.5.3

Case 2 for TDM2Eth The E1/DS1/DS3 stream is inserted in Node 1 and extracted in Node 2. One IWF is inside the 9500 MPR, but the second IWF is external to the 9500 MPR 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.

7.4.5.4

Case 3 for TDM2Eth The E1/DS1/DS3 stream is inserted/extracted in Node 1. One IWF is inside the 9500 MPR, but the second IWF is external to the 9500 MPR 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.

303


Figure 94


Traffic profiles

7.4.5.5

Case 4 and 5 for ETH2ETH In these cases Ethernet packets enter Node 1 and are extracted in Node 2. In case 4 the Ethernet packets encapsulate the E1/DS1/DS3 stream; in case 5 the packets are native Ethernet packets. None of the IWFs belongs to the 9500 MPR 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 Ethernet switch.

7.4.6

TDM2TDM

DS1 traffic packetized only internally to 9500 MPR equipment.

304


Figure 95


TDM2TDM E1/DS1/DS3 traffic

Flow Id present (user defined) Intermediate node configuration (E1/DS1/DS3 provisioning): •

node by node (building Cross-connection tables based on Flow Id)

•

Bandwidth guaranteed (according to QoS → Highest Queue Priority association)

•

No flooding-auto learning necessary

Both the IWFs belong to 9500 MPR and the packets are not supposed to exit the 9500 MPR network. The IWF parameters listed above, have predetermined values and don’t need to be provisioned. •

Mac addresses are determined as consequences of the cross connections.

•

Payload size is fixed to 121 bytes

•

ECID will be the same value as Flow Id (ECID = Emulated Circuit Identifier)

•

TDM clock source: clock recovery differential,

•

Flow Id provisioned by ECT/NMS

305


7.4.6.1


TDM2Eth

DS1 traffic both internal and external to 9500 MPR equipment. Figure 96

TDM2Eth E1/DS1/DS3 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 and the packets are supposed to exit the 9500 MPR network.

306

•

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 bidirectional circuit emulated E1/DS1/DS3 flow)



For this case the expected latency for 1 hop is 3.5 ms for 256 bytes.

7.4.6.2

SDH2SDH OC-3 (STM-1) traffic both internal and external to 9500 MPR equipment.

Figure 97

SDH2SDH OC-3 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 and the packets are not supposed to exit the 9500 MPR network. The IWF parameters listed above, have predetermined values and don’t need to be provisioned.

7.4.6.3

•


•

Payload size is fixed

•

Clock source: clock recovery differential/node timing

•


ETH2ETH None of the IWFs belongs to 9500 MPR. None of the parameters listed in the previous slide has to be configured (the 9500 MPR is transparent).

307


Figure 98


Eth2Eth E1/DS1/DS3 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.

7.4.7

MSS-1c traffic profiles Three kinds of traffic profiles have been identified: •

TDM2TDM (9500 MPR → 9500 MPR, internal to an MPR network)

•

TDM2Eth (9500 MPR→ TDM to Ethernet)

•

ETSI market: ETH2ETH (Ethernet to Ethernet)

•

ANSI market: DATA (Ethernet to Ethernet)

The second profile meets MEF8 standard.

308


Figure 99


Traffic profiles

•

Case 1 In MSS-1c these “Case X” is shown in a graphic. The E1 or T1 stream is inserted in Terminal 1 and extracted in Terminal 2. In this case the two IWFs used to packetize the traffic for the Ethernet switch in the MSS-1c are both internal to the 9500 MPR network. The Circuit Emulation Service is TDM2TDM in Terminal 1 and Terminal 2. The Cross connections to be implemented are PDH-Radio type.

•

Case 2 The E1 or T1 stream is inserted in Terminal 1 and extracted in Terminal 2. One IWF is inside the 9500 MPR, but the second IWF is external to the 9500 MPR network. The Circuit Emulation Service is TDM2ETH in Terminal 1 and Terminal 2. The Cross connections to be implemented are PDH-Radio type in Terminal 1 and Radio-Eth type in Terminal 2.

•

Case 3 The E1 or T1 stream is inserted/extracted in Terminal 1. One IWF is inside the 9500 MPR, but the second IWF is external to the 9500 MPR network. The Circuit Emulation Service is TDM2ETH in Terminal 1 and Terminal 2. The Cross connections to be implemented are PDH-Eth type in Terminal 1.

309


Figure 100


Traffic profiles

•

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

7.4.7.1

TDM2TDM E1 or T1 traffic packetized only internally to 9500 MPR equipment. E1 Traffic in TDM2TDM profile shows an example using E1 traffic.

310


Figure 101


E1 Traffic in TDM2TDM profile

Flow Id present (user defined)

7.4.7.1.1

Intermediate node configuration (E1 or T1 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 and the packets are not supposed to exit the 9500 MPR network. The IWF parameters listed above, have predetermined values and don’t need to be provisioned. •


•

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, node timing

•

Flow Id provisioned by MCT/NMS

311


7.4.7.2


TDM2Eth

E1 or T1 traffic both internal and external to 9500 MPR equipment. Figure 102 shows an example using E1 traffic. Figure 102

E1 Traffic in TDM2Eth profile

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 and the packets are supposed to exit the 9500 MPR network.

312

•

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 MCT/NMS.

•

Payload size: is fixed to 256 bytes

•

ECID: provisioned by MCT/NMS, 2 different values may be used for each direction (ECID = Emulated Circuit Identifier)

•

TDM clock source is provisioned by MCT/NMS: clock recovery adaptive, clock recovery differential


•

7.4.7.3


Flow Id is provisioned by MCT/NMS (One VLAN is assigned to each bidirectional circuit emulated E1 or T1 flow)

ETH2ETH None of the IWFs belongs to 9500 MPR. None of the parameters listed in the previous section has to be configured (the 9500 MPR is transparent). Figure 103 shows an example using E1 traffic.

Figure 103

E1 Traffic in ETH2ETH (DATA) profile

7.5

Traffic interfaces The system supports the following traffic interfaces: •

Core-E

•

CorEvo

•

E1/DS1 PDH interface (P32E1DS1)

•

DS3 PDH interface (P2E3DS3)

•

SDH interface (SDHACC/SDHCHAN)

•

Ethernet access switch (P8ETH)

•

Ethernet access switch version 2 (EASv2)

•

MPT access (MPTACC)

313


7.5.1


Core-E The Core-E, Control Switching Module card provides six user Ethernet interfaces, up to four 10/100/1000BaseT electrical Ethernet Interfaces, up to two 1000 Base-X (GigE) SFP Ethernet interfaces, the local WebEML interface, and local debug interface. The Core-E card has two roles, main and spare Core-E. The main Core-E performs key node management, control functions, provisioning, configuration management, and cross-connection matrix. The matrix is a standard Ethernet switch based on VLAN. The card also houses a plug-in flash card which stores node configuration and license data. The main Core-E card is required. The spare Core-E card provides aggregate traffic and control platform protection. The spare Core-E card is optional. Caution: If an MPT is connected to the main Core card, Core protection is not supported. A protection switch will cause communication with the MPT to be lost.

7.5.1.1


Four 10/100/1000Base-T interfaces provide access for traffic, data, or MPT ODU connections.

7.5.1.2


Two GigE SFP Ethernet interfaces are 1000 Base-X, Base-T, or copper cable access for traffic, data, MPT-MC/HC/HC-HQAM/XP/XP-HQAM/9558HC, or MPT-HL/HLC/ HLS connections.

7.5.1.3

Radio interface for MPT ODU The 10/100/1000 BaseT Ethernet interfaces support connectivity for up to four 1+0 MPT ODUs or two 1+1 MPT ODUs. The GigE SFP interfaces support connectivity for up to two 1+0 MPT ODUs or one 1+1 MPT ODU.

314


7.5.1.4


MPT-HL/HLC/HLS radio interface The GigE SFP interfaces support connectivity for up to two 1+0 MPT-HL/MPT-HLC connections.

7.5.2

CorEvo

The CorEvo card provides eight user Ethernet interfaces, up to four 10/100/ 1000BaseT electrical Ethernet Interfaces, up to four optical SFP Ethernet interfaces, the local WebEML interface, and local debug interface. The CorEvo card has two roles, main and spare. The main CorEvo performs key node management, control functions, provisioning, configuration management, and cross-connection matrix. The matrix is a standard Ethernet switch based on VLAN. The card also houses a plug-in flash card which stores node configuration and license data. The main CorEvo card is required. The spare CorEvo card provides aggregate traffic and control platform protection. The spare CorEvo card is optional. Caution: If an MPT-HL is connected to the main CorEvo card, CorEvo protection is not supported. A protection switch will cause communication with the MPT-HL to be lost.

7.5.2.1


Four 10/100/1000Base-T interfaces provide access for traffic, data, or MPT ODU connections.

7.5.2.2

Optical SFP Ethernet interfaces

Four optical SFP Ethernet interfaces are 1000 Base-X, Base-T, CDWDM, 10 GB/s, or copper cable access for traffic, data, MPT ODU, or MPT-HL/HLC/HLS connections. MPTs can be connected to optical ports 7 and 8. MPT connection is not allowed on ports 5 and 6.

315


7.5.2.3


10GigE SFP Ethernet interfaces on CorEvo-10G Two of the optical SFP interfaces on the CorEvo-10G card are 10 GB/s capable if a specific license is present.

7.5.2.4

Radio interface for MPT ODU The 10/100/1000 BaseT Ethernet interfaces support connectivity for up to four 1+0 MPT ODUs or two 1+1 MPT ODUs. The optical SFP interfaces 7 and 8 support connectivity for up to two 1+0 MPT ODUs or one 1+1 MPT ODU.

7.5.2.5

MPT-HL/HLC/HLS radio interface The SFP interfaces 7 and 8 support connectivity for up to two 1+0 or one 1+1 MPT-HL/MPT-HLC connection.

7.5.3

E1/DS1 PDH interface The P32E1DS1, PDH Interface card is a transport card which provides the external interfaces for up to 32 E1/DS1 tributaries. Manages the encapsulation/reconstruction of PDH data to/from standard Ethernet packets, and sends/receives standard Ethernet packets to/from both Core cards. Supports 1+1 EPS protection switching. Contains DC/DC converter unit. The system supports up to six 1+0 unprotected or up to 3 pairs of 1+1 EPS protected P32E1DS1 cards per MSS-8 shelf. The system supports up to two 1+0 unprotected or up to 1 pair of 1+1 EPS protected P32E1DS1 cards per MSS-4 shelf. System supports unframed format, Superframe Format (SF), and Extended Superframe Format (ESF) E1/DS1 frame formats. The system supports PM on incoming and outgoing E1/DS1 signals. For a detailed description of E1/DS1 PDH PM, see section 7.3.17. The system supports insertion of AIS upon detection of Loss of Frame (LOF) on DS1 inputs and outputs. This behavior is provisionable enable or disable at the NE level.

316


7.5.4


DS3 PDH interface The P2E3DS3, DS3 TDM Interface card is a transport card which provides the external interfaces for up to 2 DS3 tributaries. Manages the encapsulation/ reconstruction of PDH data to/from standard Ethernet packets, and sends/receives standard Ethernet packets to/from both Core cards. Supports 1+1 EPS protection switching. Contains DC/DC converter unit. The system supports up to six 1+0 unprotected (12 DS3s) or up to 3 pairs of 1+1 EPS protected (6 DS3s) P2E3DS3 cards per MSS-8 shelf. The system supports up to two 1+0 unprotected (4 DS3s) or up to 1 pair of 1+1 EPS protected (2 DS3s) P2E3DS3 cards per MSS-4 shelf. System supports unframed clear channel and framed clear channel Format for Loss Of Frame (LOF) detection DS3 frame formats.

7.5.5

SDH interface The SDHACC, OC-3 TDM Interface card is a transport card which provides the external interfaces for up to 2 OC-3 tributaries. Manages the encapsulation/ reconstruction of SDH data to/from standard Ethernet packets, and sends/receives standard Ethernet packets to/from both Core cards. Supports 1+1 EPS protection switching. Contains DC/DC converter unit. The system supports up to six 1+0 unprotected (12 OC-3s) or up to 3 pairs of 1+1 EPS protected (6 OC-3s) SDHACC cards per MSS-8 shelf. The system supports up to two 1+0 unprotected (4 OC-3s) or up to 1 pair of 1+1 EPS protected (2 OC-3s) SDHACC cards per MSS-4 shelf.

7.5.6

Ethernet access switch The Ethernet Access Switch (P8ETH) card provides user interfaces for four 10/100/ 1000BaseT Ethernet Interfaces and four GigE SFP Ethernet interfaces or MPT-HC/ HC-HQAM or MPT-HL radio interfaces. The system supports up to six 1+0 unprotected or three pairs of stacked P8ETH cards per MSS-8 shelf.

317



The system supports up to two 1+0 unprotected or 1 pair of stacked P8ETH cards per MSS-4 shelf.

7.5.6.1

10/100/1000Base-T Ethernet interfaces Four 10/100/1000Base-T interfaces provide access for traffic or data connections.

7.5.6.2


Four GigE SFP Ethernet interfaces are 1000 Base-X, Base-T, or copper cable access for traffic, data, MPT-HL, or MPT-HC/HC-HQAM/XP/XP-HQAM connections.

7.5.6.3

MPT-HL/HLC radio interface The GigE SFP interfaces support connectivity for up to four MPT-HL/HLC per P8ETH card.

7.5.6.4

MPT-HC/HC-HQAM/XP/XP-HQAM radio interface

The GigE SFP interfaces support connectivity for up to four MPT-HC/HC-HQAM/XP/ XP-HQAMs per P8ETH card.

7.5.7

Ethernet access switch version 2 The Ethernet Access Switch version 2 (EASv2) card provides user interfaces for four 10/100/1000BaseT Ethernet Interfaces and four GigE SFP Ethernet interfaces or MPT ODU or MPT-HL radio interfaces. The system supports up to six 1+0 unprotected or three pairs of stacked EASv2 cards per MSS-8 shelf. The system supports up to two 1+0 unprotected or 1 pair of stacked EASv2 cards per MSS-4 shelf.

318


7.5.7.1


10/100/1000Base-T Ethernet interfaces Four 10/100/1000Base-T interfaces provide access for traffic or data connections. The electrical Ethernet ports can be configured to perform as any of the following:

7.5.7.2

•

User Ethernet port

•

MPT connection with PFoE (power and data)

•

MPT connection without PFoE (data only)

•

PFoE only (power only)


Four GigE SFP Ethernet interfaces are 1000 Base-X, Base-T, or copper cable access for traffic, data, MPT-HL, MPT-HLC, or MPT-HC/HC-HQAM/XP/XP-HQAM connections.

7.5.7.3

MPT-HL/HLC/HLS radio interface The GigE SFP interfaces support connectivity for up to four MPT-HL/HLC/HLS per EASv2 card.

7.5.7.4


The 10/100/1000 BaseT Ethernet interfaces support connectivity for up to four 1+0 MPT ODUs or two 1+1 MPT ODUs. The GigE SFP interfaces support connectivity for up to four MPT-HC/HC-HQAM/XP/ XP-HQAM/9558HCs per EASv2 card.

7.5.7.5

Backplane compatibility The EASv2 hardware is compatible with the MSS backplanes shown in Table 35.

319


Table 35


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

7.5.8

MPT access The MPT Access card is a transport card which provides Ethernet connectivity for up to two MPT ODUs. Connectivity is accomplished using either two 10/100/ 1000Base-T interfaces, two GigE SFP interfaces, or one of each. The MPT Access card provides power to the MPT ODU using either Power over Ethernet (PFoE) solution or a dedicated coaxial connection.

7.5.9

MSS-1 Shelf The MSS-1 shelf supports the same traffic interfaces as the Main Core-E card and a 16 port E1/DS1 PDH interface P32E1DS1 card.

320


7.6


Power interfaces for MPT ODU The system supports the following external power interfaces:

7.6.1

•

Power injector card

•

Power injector box

•

MPT power unit

•


Power injector card The Power Injector card is installed in the MSS-4/8 slot. The card combines DC battery and Ethernet connections for interconnections with MPT-HC/HC-HQAM/MC/ 9558HC for interconnection between MSS-4/8 Core, P8ETH and EASv2 Ethernet ports.

7.6.2

Power injector box The Power Injector box mounts to the rack. The box combines DC battery and Ethernet connections for interconnections with MPT-HC/HC-HQAMMC/9558HC for interconnection between MSS-1/4/8 Core Ethernet ports. Power connections A & B connect directly to battery supply.

7.6.3

MPT power unit

The MPT Power Unit mounts to the rack and remotely powers four external MPT-HC/ HC-HQAM/MC/9558HC ODUs through N-connector cables.

7.6.4

MPT Extended Power Unit The MPT Extended Power Unit mounts to the rack and feeds power to up to two MPT ODUs. Compared to the standard power bar, the MPT Extended Power Unit offers the following additional features:

321


7.7


•

Galvanic Isolation between Battery Input and ODU Power Output

•

Output voltage stabilized at -57V

•

Power Input capability for the following voltages: −

+20.4VDC to +28VDC

−

-57.6VDC to -38.4VDC

•

Output Power available by means of both N-Connectors and RJ-45 Connectors

•

Use of the RJ-45 connectors to establish an Ethernet data link connection between IDU and ODU.

Configurations See Table 36 for descriptions of the modular configurations the system supports.

Table 36

Configurations

ITEM

DESCRIPTION

Microwave Switching Services (MSS-8) Shelf PN: 3DB18001AA Qty: 1 per node

The MSS-8 houses equipment that supports 16 Gb/s packet switching, synchronization, protection switching, provisioning, and alarm management utilizing either one Core card in unprotected configuration or two Core cards in protected configuration. Six transport slots support any mixture of unprotected and/or 1+1 EPS protected transport cards. Supported transport types include: up to six P8ETH cards, up to six EASv2 cards, up to six P32E1DS1 cards, up to six P2E3DS3, up to six SDHACC, and/or up to six MPTACC (radio) cards. One fan card is required for system cooling.

322


Table 36


Configurations (Continued)

ITEM

DESCRIPTION

Microwave Switching Services (MSS-4) Shelf PN: 3DB18219AB Qty: 1 per node

The MSS-4 houses equipment that supports 16 Gb/s packet switching, synchronization, protection switching, provisioning, and alarm management utilizing either one Core card in unprotected configuration or two Core cards in protected configuration. Two transport slots support either unprotected and/or 1+1 EPS protected transport cards. Supported transport types include: up to two P8ETH cards, up to two EASv2 cards, up to two P32E1DS1 cards, up to two P2E3DS3, up to two SDHACC, and/or up to two MPTACC (radio) cards. One fan card is required for system cooling.

Microwave Switching Services Shelf (MSS-1) PN: 3DB19015AA Qty: 1 per node

The MSS-1 houses equipment that supports 10 Gb/s packet switching, synchronization, protection switching, provisioning, and alarm management. It is composed of a monoboard. The monoboard provides the functions of one Control and Switching Module (Core-E) card and one P32E1DS1 card with 16 ports.

Microwave Packet Transport-Long Haul (MPT-HL) Shelf PN: 3EM22618AB, 3EM22618AC Qty: Up to 4 per 9500 MPR node (ANSI market only)

The MPT-HL shelf supports two MPT-HL or MPT-HLC transceiver radio cards.

Transport cards

Thirty-two port P32E1DS1 for E1/DS1(T1) interface Two port P2E3DS3 for DS3(T3) interface Two port SDHACC for OC-3 interface Eight port P8ETH for 10,100,1000,GigE Ethernet Ports Eight port EASv2 for 10,100,1000,GigE Ethernet Ports

I/O interface types

DS1, DS3, OC-3, Ethernet

Battery feeds

Independent, redundant battery feeds Independent, isolated battery returns

Power supply redundancy

1:1 protected

Bay power distribution

PDU

323


7.7.1


MSS-8 shelf configurations MSS-8 shelf has a modular design: Consists of backplane, card cage, and nine front access card slots. Two slots are dedicated for the Core cards. Six slots are dedicated for Transport, Auxiliary or Power Converter cards. One slot is dedicated for the FAN card. See Figure 104 for a front view of the MSS-8 shelf.

Figure 104

MSS-8 shelf - front view

MSS-8 shelf slot 1 is dedicated to the main Core card and is required in every application. See Figure 105 to see an example of the unprotected Core configuration. Slot 2 is dedicated for an optional spare Core card for protected Core configurations. See Figure 106 to see an example of the MSS-8 protected Core configuration. Slots 3 through 8 support any Transport cards, MPTACC, P2E3DS3, P32E1DS1, SDHACC, P8ETH and EASv2 cards. Slot 8 supports the Auxiliary card. Power Converter card is supported in slots 4, 6, and 8, one per shelf. Slot 9 supports the Fan card. Unprotected 1+0 transport cards are supported in any slots 3 through 8. Protected 1+1 transport cards are horizontally located. The main transport cards are located in slots 3, 5, and 7 and the spare transport cards are located in slots 4, 6, and 8 respectively.

324


Figure 105

MSS-8 shelf, unprotected Core-E configuration

Figure 106

MSS-8 shelf, protected Core-E configuration

7.7.2


MSS-4 shelf configurations MSS-4 shelf has a modular design: Consists of backplane, card cage, and five front access card slots. Two slots are dedicated for the Core cards. Two slots are dedicated for Transport cards and one slot supports the Auxiliary card. One slot is dedicated for the FAN card. See Figure 107 for a front view of the MSS-4 shelf.

325


Figure 107


MSS-4 shelf - front view

MSS-4 shelf slot 1 is dedicated to the main Core card and is required in every application. See Figure 108 to see an example of the unprotected Core configuration. Slot 2 is dedicated to an optional spare Core card for protected Core configurations. See Figure 109 to see an example of the MSS-8 protected Core configuration. Slots 3 and 4 support any Transport cards, MPTACC, P2E3DS3, P32E1DS1, SDHACC, P8ETH, and EASv2. Slot 4 supports the Auxiliary card. Unprotected 1+0 transport cards are supported in both slots 3 and 4. Protected 1+1 transport cards are horizontally located. The main transport card is located in slot 3 and the spare transport card is located in slot 4. Figure 108


Figure 109


326


7.7.3


MSS-1 unit configuration 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 110).

Figure 110

MSS-1

7.7.4

Stand alone MSS-1/MSS-4/MSS-8 shelf MSS-4/8 may be deployed in standalone configuration and provides up to 16 Gb/s packet aggregation for E1/DS1, DS3, OC-3, and Ethernet traffic.

7.7.5

Stacking MSS-1/MSS-4/MSS-8 shelf configuration To manage more directions the Stacking configuration can be realized by installing up to 3 MSS-1/MSS-4/MSS-8 shelves, interconnected through the Ethernet ports and Synchronization ports on the Core cards. An example of three stacked MSS-8 shelves equipped with unprotected Core-E cards is shown in Figure 111. An example of three stacked MSS-8 shelves equipped with protected Core-E cards is shown in Figure 112. In case of stacking of two 9500 MPR nodes with Core Protection, it is suggested to disable the Static LAG. In case of stacking of three 9500 MPR nodes with Core Protection, it is recommended to disable the Static LAG. In stacking shelf configuration the Core protection restoration mode must be configured as Non Revertive. With Core protection a maximum of three MSS-1/MSS-4/MSS-8 shelves can be interconnected as shown in Figure 112.

To implement this configuration the LOS alarm on the Ethernet ports must be enabled as switching criterion for Core protection. To enable this functionality the Ethernet LOS Criteria feature must be enabled.

327


328


Figure 111

Stacking configuration with 3 MSS-8, unprotected Core-E cards

Figure 112

Stacking configuration with 3 MSS-8, protected Core-E cards


7.7.6


Alarm management Alarm Monitor Tool TBA TBA DHCP server support System Alarms The alarm LEDs on the. System alarms indicate detection of faults in the system, local office, or network. The system provides the following fault indications: Visible indicators on the equipment Contact closures that can be connected to an external alarm system The system logs all alarm and status information and maintains the status of current active alarms in the system status database. Summaries of active alarms can be retrieved on command. Alarms are reported automatically to network management equipment. The system logs all alarm and status information and maintains the status of current active alarms in the system status database. Summaries of active alarms can be retrieved on command and displayed at the Craft. Alarms are reported automatically to network management equipment. Equipment Alarms The equipment alarms Facility Alarms Facility alarms indicate failures of a E1/DS1 and/or Ethernet. Facility alarms and parameters can be established individually. Notification codes follow: Critical (CR) Major (MJ) Minor (MN) Cleared (CL)

329



Housekeeping alarms

7.8

Cross-connections The cross-connections between slots and between slot and Ethernet user ports are realized with a Layer-2 Ethernet Switch inside the Core unit. The decision made by the switch to forward the received packet is based on the destination MAC address.

Figure 113

Cross-connection

Using the MSS-4/8 screen, the operator can switch: •

PDH (ports) lines

•

SDH (ports) lines

•

Ethernet (ETH icons) data

Using the MSS-1 screen, the operator can switch: •

E1/DS1(ports) lines

Note: All procedures are shown using the MSS-8 screen, however, the operation is similar for all MSS shelves.

330



The screen allows the operator to select E1/DS1/DS3 (PDH or MSS E1 or MSS DS1 icons), Ethernet (ETH icons), and/or Core/P8ETH/EASv2/MPTACC Radio (RADIO icons), Ethernet LAG (ETH LAG icons), Radio LAG (Radio LAG icons), Ethernet Ring (Ring icons) ports as source and destination ports and provides a graphical presentation of the switch functions. The license key installed on the MSS determines the Ethernet data capacity that can be cross connected. When parallel radio paths exist between two MSS shelves, provision port segregation between the radio paths to prevent traffic from one radio path being transmitted back to the originating site on one of the other radio paths. The Ethernet ports involved in an Ethernet LAG port are only present in the LAG/ RING area, not in the CORE area. The Radio ports involved in a Radio LAG port are only present in the LAG/RING area, not in the MPTACC card area. Radio ports involved in an Ethernet Ring are not available for cross-connection. Cross-connections to these radio ports are made through the Ring icon in the LAG/ RING area (not in the Radio area).

7.8.1

PDH Cross-connections Each E1/DS1/DS3 can be cross connected independently. E1/DS1/DS3s can be cross connected to the following interfaces: •

Radio interface

•

Ethernet interface

Each tributary (board #, port #) must be associated with an unique signal flow ID.

7.8.2

SDH Cross-connections Each STM-1/OC-3 can be cross connected independently. STM-1/OC-3s can be cross connected to the following interfaces: •

Radio interface

•

L1 Radio LAG on an EASv2 card

331



In the ANSI market, the LAG must be composed of MPT-HLC radios. •

Ring

Each STM-1/OC-3 (board #, port #) must be associated with an unique SDH2SDH signal flow ID.

7.8.3

Radio-radio cross-connections Ethernet frames, coming from a radio direction, can be cross-connected to another radio direction.

7.8.4

Ethernet cross-connections

7.8.5

Generic Ethernet flows All flows different from the TDM2TDM, TDM2ETH, and SDH2SDH ones are managed as the standard Ethernet packets: if the 802.1Q is enabled the related management is performed looking the VLAN, then, according to the destination address, each packet is switched to the correct port: radio, user Ethernet, or E1/DS1. If the 802.1D is enabled only the destination MAC 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/DS1s crossconnected on that radio interface. Hence the available bandwidth for Ethernet flows will be the configured radio bandwidth decreased by bandwidth used by TDM2TDM, TDM2ETH, and SDH2SDH traffic flows.

7.8.6

Valid cross connections: •

332

PDH to radio: −

PDH (P32E1DS1 E1/DS1 port) to RADIO (P8ETH radio port)

−

PDH (P32E1DS1 E1/DS1 port) to RADIO (EASv2 radio port)

−

PDH (P32E1DS1 E1/DS1 port) to RADIO (MPTACC radio port)

−

PDH (P32E1DS1 E1/DS1 port) to RADIO (Core radio port)

−

PDH (P32E1DS1 E1/DS1 port) to RADIO (Radio LAG port)


•

•

•


−

PDH (P2E3DS3 DS3 port) to RADIO (P8ETH radio port)

−

PDH (P2E3DS3 DS3 port) to RADIO (EASv2 radio port)

−

PDH (P2E3DS3 DS3 port) to RADIO (MPTACC radio port)

−

PDH (P2E3DS3 DS3 port) to RADIO (Core radio port)

−

PDH (P2E3DS3 DS3 port) to RADIO (Radio LAG port)

PDH to Ethernet: −

PDH (P32E1DS1 E1/DS1 port) to ETH (Core Ethernet port)

−

PDH (P32E1DS1 E1/DS1 port) to ETH (P8ETH Ethernet port)

−

PDH (P32E1DS1 E1/DS1 port) to ETH (EASv2 Ethernet port)

−

PDH (P32E1DS1 E1/DS1 port) to ETH (Ethernet LAG port)

−

PDH (P2E3DS3 DS3 port) to ETH (Core Ethernet port)

−

PDH (P2E3DS3 DS3 port) to ETH (P8ETH Ethernet port)

−

PDH (P2E3DS3 DS3 port) to ETH (EASv2 Ethernet port)

−

PDH (P2E3DS3 DS3 port) to ETH (Ethernet LAG port)

SDH to radio: −

SDH (SDHACC OC-3 port) to RADIO (P8ETH radio port)

−

SDH (SDHACC OC-3 port) to RADIO (EASv2 radio port)

−

SDH (SDHACC OC-3 port) to RADIO (MPTACC radio port)

−

SDH (SDHACC OC-3 port) to RADIO (Core radio port)

SDH to Ring: −

•

SDH to LAG: −

•

SDH (SDHACC OC-3 port) to Ethernet Ring (ERP Topology port) SDH (SDHACC port) to LAG (L1 Radio LAG on EASv2 card)

Ethernet to radio: −

ETH (Core Ethernet port) to RADIO (P8ETH radio port)

−

ETH (Core Ethernet port) to RADIO (EASv2 radio port)

−

ETH (Core Ethernet port) to RADIO (MPTACC radio port)

−

ETH (Core Ethernet port) to RADIO (Core radio port)

−

ETH (Core Ethernet port) to RADIO (Radio LAG port)

−

ETH (P8ETH Ethernet port) to RADIO (P8ETH radio port)

−

ETH (P8ETH Ethernet port) to RADIO (EASv2 radio port)

−

ETH (P8ETH Ethernet port) to RADIO (MPTACC radio port)

−

ETH (P8ETH Ethernet port) to RADIO (Core radio port)

−

ETH (P8ETH Ethernet port) to RADIO (Radio LAG port)

−

ETH (EASv2 Ethernet port) to RADIO (P8ETH radio port)

333



•

•

•

•

−

ETH (EASv2 Ethernet port) to RADIO (EASv2 radio port)

−

ETH (EASv2 Ethernet port) to RADIO (MPTACC radio port)

−

ETH (EASv2 Ethernet port) to RADIO (Core radio port)

−

ETH (EASv2 Ethernet port) to RADIO (Radio LAG port)

−

ETH (Ethernet LAG port) to RADIO (P8ETH radio port)

−

ETH (Ethernet LAG port) to RADIO (EASv2 radio port)

−

ETH (Ethernet LAG port) to RADIO (MPTACC radio port)

−

ETH (Ethernet LAG port) to RADIO (Core radio port)

−

ETH (Ethernet LAG port) to RADIO (Radio LAG port)

Radio to radio: −

RADIO (P8ETH radio port) to RADIO (P8ETH radio port)

−

RADIO (P8ETH radio port) to RADIO (EASv2 radio port)

−

RADIO (P8ETH radio port) to RADIO (MPTACC radio port)

−

RADIO (P8ETH radio port) to RADIO (Core radio port)

−

RADIO (P8ETH radio port) to RADIO (Radio LAG port)

−

RADIO (EASv2 radio port) to RADIO (EASv2 radio port)

−

RADIO (EASv2 radio port) to RADIO (P8ETH radio port)

−

RADIO (EASv2 radio port) to RADIO (MPTACC radio port)

−

RADIO (EASv2 radio port) to RADIO (Core radio port)

−

RADIO (EASv2 radio port) to RADIO (Radio LAG port)

−

RADIO (MPTACC radio port) to RADIO (MPTACC radio port)

−

RADIO (MPTACC radio port) to RADIO (Core radio port)

−

RADIO (MPTACC radio port) to RADIO (Radio LAG port)

−

RADIO (Core radio port) to RADIO (Radio LAG port)

−

RADIO (Radio LAG port) to RADIO (Radio LAG port)

PDH to Ring: −

PDH (P32E1DS1 E1/DS1 port) to Ethernet Ring (ERP Topology port)

−

PDH (P2E3DS3 DS3 port) to Ethernet Ring (ERP Topology port)

Radio to Ring: −

RADIO (MPTACC radio port) to Ethernet Ring (ERP Topology port)

−

RADIO (Core radio port) to Ethernet Ring (ERP Topology port)

−

RADIO (P8ETH radio port) to Ethernet Ring (ERP Topology port)

−

RADIO (EASv2 radio port) to Ethernet Ring (ERP Topology port)

Ethernet to Ring: −

334

ETH (Core Ethernet port) to Ethernet Ring (ERP Topology port)



− •

ETH (Ethernet LAG port) to Ethernet Ring (ERP Topology port)

Ring to Ring: −

Ethernet Ring (ERP Topology port) to Ethernet Ring (same ERP Topology port)

After a cross connection has been created, the two cross connected slots are visually linked by a line: a line in the context of this application represents a bundle of flows, which share same source and destination entity. In addition, all 802.1Q tagged Ethernet traffic having the same VLAN ID as cross connection Flow ID number will only be forwarded between these cross connected slots.

7.8.7

Point to Point VLAN The Point to Point (P2P) VLAN cross connect feature allows the user to direct VLANtagged traffic between specified Ethernet and/or radio ports. Rather than directing all traffic to and from the cross connected ports, the feature directs Ethernet traffic where the VLAN tag matches the cross connect Flow ID. •

When making the connection for a P2P VLAN flow (Ethernet port to radio), the user should enter a MAC address of all 0's (000000000000). P2P VLAN cross connects will direct matching VLAN-tagged Ethernet traffic to the cross connected ports regardless of the destination MAC address in the Ethernet frames.

•

Ethernet traffic entering the cross connected port with a VLAN tag matching the flow id will be directed only to the port on the other end of the cross connect. Traffic will not be flooded. This will also take precedence over any MAC address learning for VLAN-tagged traffic that matches the flow id in the cross connect.

•

Ethernet traffic entering the cross connected port with no VLAN tag or VLAN tags that do not match the flow id specified in the cross connect will flood to all ports until MAC address learning takes place. The P2P VLAN cross connect will have no effect on this traffic.

•

VLAN tagged Ethernet traffic that enters a port will be dropped if the VLAN tag matches the flow id of a cross connect that is on a different port.

The user must know the Ethernet VLAN ID, provisioned by the customer, before provisioning/cross connecting E1/DS1/DS3 data lines. Each radio link can handle a maximum of 256 VLAN IDs.

335



When configuring MPLS T1's via Ethernet through a multi-path 9500 MPR network (Nx1+0/1), Point-to-Point VLAN (P2P VLAN) cross-connects will be required to restrict the traffic to one radio/Ethernet port combination. This is because the multiple path connections will deliver several copies of the LDP messages between the MPLS T1's NE's causing regular traffic interruptions. When there are 3 radio links between the same two shelves, 3 copies of each LDP message are delivered to the MPLS T1's. Creating the P2P VLAN cross-connect between the Ethernet port and radio (where the MPLS T1's connects) allows only one copy of the message to reach the MPLS T1's and corrects the problem.

7.8.8

Flow ID number rules The Flow ID number entered by the operator on the MSS/DS1 or MSS/DS3 provisioning screen is one of the parameters the software management uses to determine source, destination, and direction of the E1/DS1/DS3 port when the data is switched in the Core card. The following rules apply to the Flow ID: 1. Number is unique to the entire network. It cannot be used in any other radio or hop in the network. 2. Range of Flow ID numbers to choose from is determined by total number of Flow ID's in the network.

7.8.8.1

Ranging Ranging allows the operator to enter multiple cross-connects simultaneously. When multiple cross-connections are required between the same two ports, the MAC Address is the same, and multiple Flow IDs are to be cross-connected, ranging can be used to enter the cross-connections at the same time. When multiple cross-connections are required between the same two ports, the MAC Address is the same, and the Flow IDs are sequential, ranging can be used to enter the cross-connections at the same time. In the Flow ID field, enter the end points of the sequence using the notation [n-m]; where ‘n’ equals the start value of the sequence and ‘m’ equals the stop value of the sequence. Example: to enter cross-connections for Flow IDs 147 through 156, in the Flow ID field enter “147-156”. See Figure 114.

336



When multiple cross-connections are required between the same two ports, the MAC Address is the same, and the Flow IDs are not sequential, ranging can be used to enter the cross-connections at the same time. In the Flow ID field, enter the multiple Flow IDs separated by commas. Example: to enter cross-connections for Flow IDs 47, 62, 135, and 201, in the Flow ID field enter “47,62,135,201”. See Figure 115. To ensure successful completion of the cross-connection requests, the user should limit the number of cross-connections created using a single ranging operation to ten. Ranging is supported for Radio to Radio and Ethernet to Radio cross-connection entry. Ranging is supported for PtP VLAN cross-connection entry. Figure 114

Ranging Sequential flow IDs

337


Figure 115


Ranging Non-Sequential flow IDs

7.8.8.2

Destination MAC address The destination MAC address is dependent upon the protection scheme of the destination port. Provision/set the first two digits of the destination MAC Address as follows for the following destination port types: •

Unprotected radio or PDH port: ‘Unicast’ or ‘00’

•

Protected 1+1 radio or PDH port: ‘Multicast’ or ‘01’

•

ERPS ring node: ‘Unicast’ or ‘00’

•

L1 LAG: ‘Multicast’ or ‘01’

•

L1 LAG, configured as an ERPS ring port: ‘Unicast’ or ‘00’

The destination MAC address for a P2P VLAN provisioned in 802.1D, the crossconnect must be set to “00:00:00:00:00:00”. Example #1: The destination port is an unprotected radio or PDH port and the NE MAC Address is “00:43:23:19:87:92”. In the cross-connection MAC Address field, enter: “00:43:23:19:87:92”. Example #2: The destination port is 1+1 protected radio or PDH port and the NE MAC Address is “00:43:23:19:87:92”. In the cross-connection MAC Address field, enter: “01:43:23:19:87:92”.

338



Example #3: The destination port is L1 LAG and the NE MAC Address is “00:43:23:19:87:92”. In the cross-connection MAC Address field, enter: “01:43:23:19:87:92”. Example #4: The destination port is an ERPS ring node, regardless of whether one of the radio ports is a L1 LAG, and the NE MAC Address is “00:43:23:19:87:92”. In the cross-connection MAC Address field, enter: “00:43:23:19:87:92”. Example #5: The cross-connect is a P2P VLAN (802.1D), the destination port is set to “00:00:00:00:00:00”. In the cross-connection MAC Address field, enter: “00:00:00:00:00:00”.

7.8.9 Figure 116

MSS-1c cross-connections

Cross-connection

Note: Max #10 or #16 depending on the MSS-1C variant.

The cross-connections are realized with a Layer-2 Ethernet Switch inside the MSS-1c. The decision made by the switch to forward the received packet is based on the destination MAC address.

339


7.8.9.1


E1/T1 cross-connection

Each E1 or T1 can be cross connected independently. E1 or T1 can be cross connected to any of the following ports: •

Radio port (Figure 117)

•

Ethernet port (Figure 118)

Each E1 or T1 must be associated with a unique signal flow ID. Figure 117

E1/T1 from/to radio port

Figure 118

E1/T1 from/to Ethernet port

340



Typical use of the E1 or T1 from/to Ethernet port is in case of two co-located MSS to expand the number of PDH ports for the other radio direction. Note: To configure these cross-connections a connected MPT is needed.

7.8.9.2

Ethernet flows All flows different from the TDM2TDM and TDM2ETH ones are managed as the standard Ethernet packets: •

if 802.1D is enabled, only the destination address is considered to route the packets.

•

if 802.1Q is enabled, the related management is performed looking the CVLAN, then, according to the destination address, each packet is switched to the correct port: radio, user Ethernet or E1

•

if 802.1ad (Q in Q) is enabled, the related management is performed looking the S-VLAN, then, according to the destination address, each packet is switched to the correct port: radio, user Ethernet or E1.

The bandwidth assigned globally to the radio interface to the Ethernet traffic is the consequence, with a given radio capacity, of the number of E1 cross-connected on the radio interface. Hence the available bandwidth for Ethernet flows will be the configured radio bandwidth decreased by the bandwidth used by each TDM2TDM and TDM2ETH.

7.9

Database backup and restore The system supports a full database backup and restore from the craft terminal or network manager, including provisioning and configuration information stored on the NE. The following networking parameters are not saved during MIB Management Database Backup. •

All log files including the alarm and event log file

•

Loopbacks

•

Manual protection switches

341



•

Local Shelf and Peripheral MAC Addresses (for example, any specified external MAC address for TDM2ETH connections shall be backed up)

•

Forced Adaptive Modulation

The above listed parameters are not affected during MIB Management Database Restore.

7.10

In-service upgrade Systems software and hardware can be upgraded to a new release, as specified in the upgrade procedure. The upgrade procedure can be completed in less than four hours and within one maintenance window. Default values used when upgrading to are defined for all new provisioning parameters. The system saves and maintains the content of the customer’s existing generic database through the upgrade process, including the alarm database and all provisioning. Historical PM data and the log file are not preserved. See the Release Notice for supported software upgrade paths based on existing software versions.

342


7.11


LAG (link aggregation group)

7.11.1

LAG overview Link Aggregation groups a set of ports so that two network nodes can be interconnected using multiple links to increase link capacity and availability between them. When aggregated, two or more physical links operate as a single logical link with a traffic capacity that is the sum of the individual link capacities. This doubling, tripling or quadrupling of capacity is relevant where more capacity is required than can be provided on one physical link. Link aggregation also provides redundancy between the aggregated links. If a link fails, its traffic is 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. Supported LAG ID numbers are 1 to 14.

7.11.2

LAG hashing

LAG hashing provides two different traffic load balancing algorithms configured on the LAG: Layer 2 (L2 Hash) and Layer 3 (L3 Hash). •

•

L2 Hash (load balancing algorithm is based on fields contained in the Ethernet MAC frame header: −

Destination MAC Address + Source MAC Address + VLAN ID + EtherType

−

Destination MAC Address + Source MAC Address (for Multicast, Broadcast, and Unknown traffic)

L3 Hash (load balancing algorithm is based on fields contained in the IP frame header and TCP/UDP ports):

343



•

−

Destination IP Address + Source IP Address + TCP/UDP Destination Port + TCP/UDP Source Port

−

Destination IP Address + Source IP Address (for Multicast IP traffic)

If the frame is not IP and Destination and Source IP Addresses are not available, Destination MAC Address + Source MAC Address are used to evaluate the traffic distribution.

The chosen algorithm applies only to traffic learned by the switch. The same interface will be used for all packets in Ethernet flow. Traffic from the same flow is not evenly distributed over all the interfaces. Even if multiple physical interfaces are used at the same time for traffic forwarding, it is not guaranteed at all to have a complete and full load balance on ports in L2 LAG. This means that a single physical port can be overloaded in L2 LAG and consequently discards all traffic in excess (according to QoS priorities) even when other physical ports in the L2 LAG have residual bandwidth not exploited. Neither Revertive nor Not Revertive behavior can be associated with frame distribution performed by the hashing function. It is not guaranteed that the association of a traffic flow to a specific interface is maintained when the interface has been removed from L2 LAG due to a failure, then re-inserted in the L2 LAG due to the clear of the failure.

7.11.3

L1/L2 link aggregation on radio ports (radio L1/L2 LAG) Link aggregation can be applied to radio ports, in this case it is named Radio L1/L2 Link Aggregation (Radio L1/L2 LAG). For a detailed description of Radio L1 LAG, see Radio L1 LAG. For a detailed description of Radio L2 LAG, see Radio L2 LAG.

7.11.4

L2 Link aggregation on user Ethernet ports (Ethernet L2 LAG) User Ethernet ports (electrical or optical) on the same Core card can be provisioned as a member of an Ethernet L2 LAG port. For a detailed description of Ethernet L2 LAG, see Ethernet L2 LAG.

344


7.12


License key management License key management provides the mechanism to enable features on the basis of the customer needs, considering a predefined set of different functionalities as different elementary licenses. A set of key features is identified and each one of them is associated with one elementary license, providing the possibility to add features in an incremental approach. The management of the license key is managed utilizing the following fields: •

RMU Serial Number: serial number of the flash card (read-only field)

•

License String: displays the set of key features supported by the NE (readonly field)

•

License Key: used to upgrade the license string

Provisioning the RMU Serial Number, License String, and License Key are supported from the craft terminal. The RMU Serial Number and License String are viewable from Web Server or WebCT.

7.12.1

License String The following unique Elementary Licenses (EL) are available to construct the License String. The loaded License String determines the provisionable features on the NE. The available ELs are as follows: •

Transmission capacity

•

Unlicensed option (ANSI market only)

•

Adaptive modulation

•

Data awareness

•

ERPS

•

Packet throughput booster

•

AES

•

XPIC

•

High power (MPT-HLS - ETSI market only)

•

L1 radio LAG with MSS-O

•

5+0 L1 radio LAG

•

Number of interfaces able to work at 10 Gb/s

345



•

7.12.1.1

1588 transparent clock

Transmission capacity Transmission capacity defines the maximum net Ethernet throughput for the radio interface. Ethernet throughput is based on the radio profile channel spacing and modulation technique selected. Ethernet throughput is rounded to the nearest 10 Mb/ s to determine the minimum required Transmission Capacity EL. The Transmission Capacity EL consists of two parts: number of radio interfaces and maximum net Ethernet throughput. Up to eighteen radio interfaces may be licensed with one Transmission Capacity EL. There are five levels of Transmission Capacity supported. Transmission Capacity uses the following format: YCapXXX, where Y is the number of radio interfaces licensed and XXX is the maximum throughput of the radio interfaces. The supported Transmission Capacity throughputs are as follows: •

40 Mb/s: Format: YCap040. Example: 1Cap040 means only one license is available for radio interface capacity up to 40 Mb/s.

•

80 Mb/s: Format: YCap080. Example: 3Cap080 means three licenses are available for radio interface capacities up to 80 Mb/s.

•

120 Mb/s: Format: YCap120. Example: 4Cap120 means four licenses are available for radio interface capacities up to 120 Mb/s.

•

160 Mb/s: Format: YCap160. Example: 8Cap160 means eight licenses are available for radio interface capacities up to 160 Mb/s.

•

220 Mb/s: Format: YCap220. Example: 8Cap220 means eight licenses are available for radio interface capacities up to 220 Mb/s.

•

320 Mb/s: Format: YCap320. Example: 12Cap320 means twelve licenses are available for radio interface capacities up to 320 Mb/s.

•


•


More than one Transmission Capacity EL is supported in a single license string. Example: 4Cap080/2Cap160/TDM2ETH means four licenses available for radio interface capacities up to 80 Mb/s and two licenses available for radio interface capacities up to 160 Mb/s.

346


7.12.1.2


Unlicensed option (ANSI market only)

Unlicensed Option EL restricts the use of Transmission Capacity licenses to the unlicensed band (5725 to 5875 MHz). Unlicensed Option EL uses the following format: YUnlOpt, where Y equals the number of radio interfaces restricted to unlicensed radio profiles, up to the total of Transmission Capacity licenses available. When no Unlicensed Option EL is present, none of the available Transmission Capacity licenses are restricted to the unlicensed band. The following are examples of license strings with and without Unlicensed Option LE:

7.12.1.3

•

4Cap160/TDM2ETH means four licenses available for radio interface capacities up to 160 Mb/s, none are restricted to the unlicensed band.

•

6Cap080/2Cap320/TDM2ETH/2UnlOpt means six licenses available for radio interface capacities up to 80 Mb/s, two licenses available for radio interface capacities up to 320 Mb/s, and two of the eight available Transmission Capacity licenses are restricted to the unlicensed band.

Adaptive modulation

The adaptive modulation EL provides the right to use adaptive modulation for transmission capacity licenses. The adaptive modulation EL uses the following format: YModAdp, where Y equals the number of radio profiles available to use adaptive modulation radio profiles, up to the total of transmission capacity licenses available. When no adaptive modulation EL is present, none of the available transmission capacity licenses are available to be configured with adaptive modulation. The following are examples of license strings with and without adaptive modulation EL:

7.12.1.4

•

7Cap080/TDM2ETH means seven licenses available for radio interface capacities up to 80 Mb/s, none are available for adaptive modulation.

•

6Cap080/3ModAdp/TDM2ETH/1UnlOpt means six licenses available for radio interface capacities up to 80 Mb/s, three Transmission Capacity licenses are available for adaptive modulation, and one of the six available Transmission Capacity licenses are restricted to the unlicensed band.

Data awareness The data awareness EL provides the right to support TDM over Ethernet, MEF8 standard traffic. Data Awareness license uses the following format: TDM2ETH. Currently all license strings available include the data awareness EL.

347


7.12.1.5


ERPS The ERPS EL provides the right to configure ERPS Topology with any type of interface as Ring port. ERPS license uses the following format: Ring.

7.12.1.6

Packet throughput booster The Packet throughput booster EL provides the right to configure a packet throughput booster on an MPT ODU, MPT-HL, MPT-HLC, or MPT-HLS radio interface, or on an L1 Radio LAG. The Packet throughput booster license uses the following format: PTB.

7.12.1.7

AES The AES EL provides the right to configure AES encryption on an MPT-HC/XP/HCHQAM/XP-HQAM/9558HC or MPT-HLC radio interface. The AES license uses the following format: AES.

7.12.1.8

XPIC The XPIC EL provides the right to configure XPIC on an MPT-HLC or MPT-HCHQAM/XP-HQAM radio interface. The XPIC license uses the following format: [Y]XPIC, where Y is the number of interfaces available for XPIC configuration.

7.12.1.9

High power (MPT-HLS - ETSI market only) The high power EL provides the right to configure the high power range on an MPTHLS radio interface. The license uses the following format: [Y]HLsHP, where Y is the number of interfaces available for High Power configuration.

7.12.1.10

L1 radio LAG with MSS-O The L1 radio LAG in MSS-O EL provides the right to configure an L1 LAG on an MSS-O. The license uses the following format: MSSOL1LAG.

348


7.12.1.11


5+0 L1 radio LAG The 5+0 L1 radio LAG EL provides the right to configure an L1 LAG with a LAG size greater than 4. The license uses the following format: 5+L1LAG.

7.12.1.12

Number of interfaces able to work at 10 Gb/s The number of interfaces able to work at 10 Gb/s EL defines the number of optical interfaces on a CorEvo-10G card that can work at a speed of up to 10 Gb/s. The license uses the following format: Y10G, where Y is the number of interfaces: either 1 or 2.

7.12.1.13

1588 transparent clock The 1588 transparent clock EL provides the right to configure 1588 transparent clock. The license uses the following format: 1588TC.

349


7.13


Loopback To facilitate installation, commissioning, remote maintenance, and troubleshooting, various loopbacks are supported by the system. The activation of a loopback affects traffic. The presence of a loopback is indicated with an abnormal condition. For a loopback to function correctly, the LinkID must be disabled and the Tx ECID must be equal to the Rx ECID. The system supports the following loopback types:

7.13.1

•


•


•


•

Core facing @RF - Internal loopback

•

Line facing PDH (DS1/DS3) loopback

•

Radio facing PDH (E1/DS1/DS3) loopback

•


•

Core facing SDH (STM-1/OC-3) loopback

Core facing radio digital loopback Core facing radio digital loopback is an internal loopback on the aggregate traffic. For MPT-HC/HC-HQAM/XP/XP-HQAM, this loopback routes data from the output of the Tx Data Awareness block (after compression) to the input of the Rx data awareness block (before decompression). For MPT-HL, this loopback routes the Tx modem signal (after compression and QoS) to Rx modem signal (before decompression). This loopback type is shown in Figure 119.

350


Figure 119


Core and radio facing radio loopbacks

1. Core facing radio digital loopback. 2. Radio facing circuit loopback. This loopback is supported by MPT-HC/HC-HQAM/XP/XP-HQAM ODUs and MPT-HL transceivers. This loopback is loop and continue. This loopback is configured using the craft terminal. The Core facing radio loopback operation applies an Automatic Tx mute before the execution of the command and the Tx mute removed after the execution of the loopback command. When this loopback is activated the behavior is as follows:

7.13.2

•

Compressed flows (TDM2TDM and TDM2ETH) are forwarded back to Core module with correct assignment of source and destination MAC addresses (for example, 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 values are the same. In cases where the ECID Tx is different form ECID Rx, the TDM2ETH flows are dropped.

•

Generic Ethernet flows are dropped.

Radio facing circuit loopback Radio facing loopback is a remote loopback which provides an over-the-air loopback test on the aggregate traffic. This loopback connects the receive data interface to the transmit data interface. This loopback type is shown in Figure 119. This loopback is supported by MPT-HC/HC-HQAM/XP/XP-HQAM ODUs only.

351



This loopback is loop and continue. This loopback is a line external loopback on the aggregate signal level. This loopback is configured using the craft terminal. When this loopback is activated the behavior is as follows:

7.13.3

•

Compressed flows (TDM2TDM and TDM2ETH) are forwarded back to Core module with correct assignment of source and destination MAC addresses (for example, 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 values are the same. In cases where the ECID Tx is different form ECID Rx, the TDM2ETH flows are dropped.

•

Generic Ethernet flows are dropped.

Core facing RF loopback Local core facing RF loopback provides a method to troubleshoot RF paths constructed with MPT-HLs. This loopback routes the Tx RF signal to the Rx RF. This loopback may be activated for each port. This loopback is supported by MPT-HL transceivers only. This loopback requires an external Tx to Rx connection to guarantee operation. This loopback is traffic affecting.

7.13.4

Core facing @RF - Internal loopback Core facing @RF internal loopback provides a method to troubleshoot RF paths constructed with MPT-HLCs. This loopback routes the Tx RF signal to the Rx RF. This loopback may be activated for each MPT-HLC radio. This loopback is supported by MPT-HLC transceivers only. It is not guaranteed if ATPC is in use. This loopback is traffic affecting.

352



The following considerations apply when an @RF - Internal loopback is configured: •

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.

•

If the MPT-HLC 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 an MPT-HLC with SD enabled, a combiner loss of alignment alarm will remain active to indicate that alignment cannot be performed.

7.13.5

Line facing PDH (DS1/DS3) loopback Line facing PDH loopback is a local loopback which loops the receive line signal (from the line) onto the transmit signal (towards the Line). This loopback is drop and continue. This loopback is configured using the craft terminal.

7.13.6

Radio facing PDH (E1/DS1/DS3) loopback Radio facing PDH loopback is a remote loopback which loops the receive tributary signal (from the Core) onto the transmit signal (towards the Core). This loopback may be activated for each E1/DS1/DS3 tributary port. This loopback is loop and continue. This loopback is configured using the craft terminal.

7.13.7


Line facing SDH loopback is a local loopback which loops the receive line signal (from the line) onto the transmit signal (towards the Line). This loopback may be activated for each STM-1/OC-3 tributary port.

353



This loopback is drop and continue. This loopback is configured using the craft terminal.

7.13.8

Core facing SDH (STM-1/OC-3) loopback Core facing SDH loopback is a remote loopback which loops the receive tributary signal (from the Core) onto the transmit signal (towards the Core). This loopback may be activated for each STM-1/OC-3 tributary port. This loopback is loop and continue. This loopback is configured using the craft terminal.

7.13.9

Loopback time-out The system supports a loopback time-out mechanism to avoid the risk of a permanent disconnection from the craft terminal to a remote NE after executing a loopback. The time--out period is entered into the management system expressed in days/ hours/minutes. The maximum time-out period is 4 days. The default time-out period is 5 minutes

7.13.10

Loopback activation

Loopbacks can be activated by local or remote management systems. The activation command includes the duration of the loopback (time-out). Core facing, Core facing RF, and Radio facing loopbacks are not supported at the same time. The time-out period starts at the activation time and expires at the end of the timeout period. The operator has the option to deactivate the loopback during the activation period.

354



The operator also has the option to extend the time-out period during the activation period. In this case, the time-out period is re-initiated. The specified time period starts over from the new activation date, overwriting the previous activation date and timeout values.

7.14

Network Communication Table 37 describes the port requirements for protocols supported in the network.

Table 37

Port requirements for network protocols

Protocol

From port

To port

Direction

Notes

UDP

>1023 on NEtO

161 on NE

bi-directional

SNMP

UDP

5010 on NEtO

>1023 on NE

uni-directional

- the SNMP trap is always sourced by the NE - the DA port is the one communicated by the manager when registering - the NEtO always performs registration communicating Destination Port 5010

UDP

162 on NEtO

>1023 on NE

uni-directional

SNMP Traps (SNMPv2/SNMPv3)

TCP

21 on NEtO

>1023 on NE

bi-directional

MSS-1/4/8 FTP SW Download - the NE acts as the FTP client, connecting toward the server listening on port 21

TCP

>1023 on NEtO

21 on NE

bi-directional

MSS-1/4/8 FTP MIB backup/MIB restore - the NE acts as the FTP server and the 5620 SAM or NEtO acts as the FTP client connecting toward the NE and listening on port 21

TCP

21 on NEtO

>1023 on NE

bi-directional

MSS-1c/MPR-e FTP SW download/backup/ restore/provisioning - in most cases the MPT acts as a passive FTP client

TCP

>1023 on NEtO

>1023 on NE

bi-directional

Passive FTP ports for data transfer

355


Table 37


Port requirements for network protocols (Continued)

Protocol

From port

To port

Direction

Notes

TCP

20 on NEtO

>1023 on NE

bi-directional

Active FTP ports for data transfer for SW download for MSS-1/4/8 and performance monitoring for MSS-1c/MPR-e

TCP

22 on NEtO

>1023 on NE

bi-directional

SFTP SW download for MSS-1/4/8 - starting from R4.1.0 SSHv2 is used for secure login

TCP

>1023 on NEtO

22 on NE

bi-directional

FTP MIB backup/MIB restore for MSS-1/4/8 - starting from R4.1.0 SSHv2 is used for secure login

TCP

>1023 on NEtO

22 on NE

bi-directional

SSHv2 for MSS-1/4/8

TCP

>1023 on NEtO

80 on NE

bi-directional

HTTP for MSS-1/4/8

TCP

>1023 on NEtO

23 on NE

bi-directional

Telnet

TCP

49 on TACACS+ server

>1023 on NE (TACACS + client)

bi-directional

MSS-1/4/8 TACACS+ - the NE acts as the TACACS+ client and initiates communication toward TACACS+ server, which is assumed to be in the same network as the NEtO - by default the TACACS+ server listens on port 49. This can be changed. The MSS-1/4/ 8 allows the configuration of a destination port, for which the TACACS+ server is provisioned on the NE

TCP

Any port on NEtO

11500 on NE

bi-directional

GUI Equipment view for MSS-1c and MPRe. This is fixed and cannot be changed.

356


7.15


Network management The system supports the following network managers:

7.16

•

1350 OMS

•

1352 CM

•

1353 NM

•

5620 SAM

•

TSM-8000

NE time NE time (date and time) is used for time and date stamping of alarm conditions and alarm logs, abnormal conditions, event, and PM functions. NE time can be provisioned to use one of the following: •

PC/laptop operating system time

•

set manually by the operator

•

Network Time Protocol (NTP)

The date format is yyyy/mm/dd, where yyyy equals the four digit year, mm equals the two-digit month, and dd equals the two-digit day. The time format is hh:mm:ss, where hh equals the two-digit hour (00 to 23), mm equals the two-digit minute (00 to 59), and ss equals the two-digit second (00 to 59). NE Time is provisionable from the craft terminal and Web Server. When using Web Server, NE time can be provisioned manually or to match the PC/ laptop operating system time. NTP provisioning is not supported using Web Server. Alcatel-Lucent recommends that NTP be used to maintain consistent NE times within the network. This allows for easy correlation of alarm/event/PM timestamps with an external time reference. To minimize NTP traffic within the TMN network, each NE could use the next NE toward the external time reference as the main server. When the NE is configured with NTP, NE time cannot be provisioned manually. Timestamp events appear in timestamp order.

357



After an NE time change, time stamp events (alarm and event logs PM history intervals) can appear in NE time order rather than chronological order. To prevent this from occurring, when changing NE time, Alcatel-Lucent recommends saving then clearing alarm and event logs and PM history, to prevent reporting erroneous events and data. After a power cycle on an NE not provisioned with NTP, the NE time will revert to the default NE time. The default NE time is January 1st, 1970 (that is, 1970/01/01 00/00/00).

7.17

Non-administrator user The system supports non-administrator users and user groups. It is not mandatory that TCO Suite applications be started up by a user with Administrator privileges. However, full-control permissions are required to allow TCO Suite software applications to write their own log files. Non-administrator users must have full-control permissions applied to the folder where the TCO Suite is saved, for correct operation of the TCO Suite software applications.

7.18

Performance monitoring Performance monitoring (PM) is supported by the system, and performed through the PM Tool. PM data is collected for 15-min and 24-h time periods. PM counters that the system supports are described in the following sections.

7.18.1

Ethernet statistics Ethernet statistics are available for user Ethernet ports, L1 Radio LAG Ethernet ports, and radio Ethernet ports.

358


7.18.1.1


User Ethernet statistics User Ethernet statistics provides an indication of the Quality of Service (QoS) for the Ethernet port. Two Ethernet PM views are available: Ethernet Aggregate Tx (outgoing) and Ethernet Aggregate Rx (incoming). The Ethernet Aggregate Tx PM view supports default Ethernet statistics, which are collected on the NE: •

Total Transmitted Octets (TTO)— the number of transmitted octets on the port.

•

Total Transmitted Frames (TTF)—the total number of transmitted frames on the port.

•

Total Discarded Frames (TDF)— the number of transmitted frames discarded on the port.

•

Total Transmitted Octets after compression (TTO-C)— the number of transmitted octets (after compression) on the port.

The Ethernet Aggregate Rx PM view supports the following Ethernet statistics:

7.18.1.2

•

Total Received Octets (TRO)— the number of received octets on the port, including good, FCS, alignment errored, undersized, fragmented, and oversized packets.

•

Total Received Frames (TRF)— the number of received frames on the port, including good, FCS, alignment errored, undersized, fragmented, and oversized packets.

•

Total Received Frames (TRSEF)— the number of received errored frames on the port, including; FCS, alignment errored, undersized, fragmented, and oversized packets.

•

Total Discarded Frames (TDF)— the number of received frames discarded.

•

TRF Unicast— the number of good received unicast frames on the port.

•

TRF Multicast— the number of good received multicast frames on the port.

•

TRF Broadcast— the number of good received broadcast frames on the port.

L1 Radio LAG Ethernet PM

L1 Radio LAG Ethernet PM provides an indication of the QoS for the L1 Radio LAG Ethernet port. The radio QoS Ethernet statistics are related to radio QoS queues (queues 1 to 8) for each Tx L1 Radio LAG direction. Besides counting native Ethernet traffic, L1 Radio LAG Ethernet PM counts TDM2TDM, TDM2ETH, and TMN traffic that passes through the lowest index port.

359



L1 Radio LAG Ethernet PM supports the following PM counters: •

Total Transmitted Octets (TTO)—the number of good transmitted octets on the port.

•

Total Transmitted Frames (TTF)—the number of good transmitted frames on the port.

•

Total Discarded Frames (TDF)—the number of transmitted frames discarded on the port.

•

Available Capacity— For static modulation or adaptive modulation without admission control, Available Capacity is the combined available bandwidth values of the radios in the LAG, expressed in Mb/s. Note: when the number of radios in the LAG exceeds four, the sum of the capacities of the LAG channels, which defines the shaper rate of the LAG master port, can be higher than the Lag rate value of 2 364 712 Gb/s. This rate corresponds to the maximum master port ingress rate for frames with length of 363 bytes. In this case, the Available Capacity is calculated based on a jumbo frame size of 1522 bytes. This means that, depending on the modulation of the radios, the Available Capacity can exceed the LAG rate, which is based on a frame size of 363 bytes. For adaptive modulation with admission control, Available Capacity as defined previously is corrected by a delta value depending on radio type. For MPT radios, it is the delta between the maximum and minimum adaptive capacity values for that radio direction.

•

Used Capacity—the ratio of TTF to the capacity of the L1 Radio LAG Ethernet flow.

•

TTO Throughput—the TTO Throughput of the L1 Radio LAG Ethernet flow.

•

TDF Ratio—the ratio of TDF to TTF of the L1 Radio LAG Ethernet flow.

For an L1 Radio LAG on an EASv2 card, you can choose whether to include TDM traffic in the Ethernet counters (included by default). For an L1 Radio LAG on P8ETH, the TDM traffic is always included.

7.18.1.3

Compression gain statistics Compression gain counters are available for MPTs and L1 LAG with Packet Throughput Booster. They are only displayed in the Bird’s Eye View.

360



The view is split into two parts: the upper part shows nominal capacity, capacity L2 (at layer 2), capacity L1 (at layer 1), and L1 and L2 throughput. The lower part shows the transmitted octets after compression, the transmitted octets at layer 2, and the transmitted octets at layer 1. The gains at L1 and L2 are shown in the table, and in the graph as a percentage on top of the respective bars. With no traffic running, the gain is displayed as “--”. Default and elaborated (detailed) counters are displayed at the bottom of the page. Compression gain statistics support the following Ethernet statistics: Default counters: •

•

TTO: number of octets of Ethernet frames transmitted by the MPT radio (TTO-C) or received by the port (TTO-L2 and TTO-L1). −

TTO-C: TTO after compression

−

TTO-L2: TTO counted at layer 2

−

TTO-L1: TTO counted at layer 1

Gain: percentage increase in TTO from using compressed frames. −

Gain L2: 100 x (ΔTTO-L2 / ΔTTO-C)

−

Gain L1: 100 x (ΔTTO-L1 / ΔTTO-C)

Elaborated counters: •

Available Nominal Capacity: radio bandwidth available for Ethernet traffic, allowing for adaptive modulation and admission control, if applicable

•

Available Capacity L2: (Available Nominal Capacity) x (Gain L2)

•

Available Capacity L1: (Available Nominal Capacity) x (Gain L1)

•

Throughput L2: (ΔTTO-L2 x 8) / (Δt x 106) [Mb/s] where: ΔTTO-L2 = TTO-L2(n)-TTO-L2(n-1) [bytes] = delta between measures for TTO-L2 Δt = t(n) - t(n-1) = delta time between measures in [seconds]

•

Throughput L1: (ΔTTO-L2 x 8) / (Δt x 106) [Mb/s] where: ΔTTO-L1 = TTO-L1(n)-TTO-L1(n-1) [bytes] = delta between measures for TTO-L1 Δt = t(n) - t(n-1) = delta time between measures in [seconds] TTO-L1 = TTO-L2 + (TTF (number of Ethernet frames transmitted by the MPT)) x 20

361



The addition of TTF x 20 allows for the standard 20 bytes of IFG and preamble for each transmitted frame. If Packet Throughput Booster is not enabled, the TTO-C is equal to TTO-L2 and Available Capacity L2 is equal to the nominal capacity. Gain L1 is always greater than 100%, regardless of whether Packet Throughput Booster is enabled; therefore, Available Capacity L1 is always greater than Available Capacity L2 and TTO-L1 is always greater than TTO-L2.

7.18.1.4

Radio Ethernet statistics Radio Ethernet statistics provide an indication of the QoS for the radio Ethernet port. The radio QoS Ethernet statistics are related to radio QoS queues (queues 1 to 5) for each Tx radio direction. Queue 5 is the highest priority queue and queue 1 is the lowest priority queue. Radio Ethernet statistics support the following statistics: •

Total Transmitted Octets (TTO)—the number of good transmitted octets on the port.

•

Total Transmitted Frames (TTF)—the number of good transmitted frames on the port.

•

Total Discarded Frames (TDF)—the number of transmitted frames discarded on the port.

•

Available Capacity—the available capacity of the radio Ethernet flow.

•

TTO Throughput—the TTO Throughput of the radio Ethernet flow.

•

TDF Ratio—the ratio of TDF to TTF of the radio Ethernet flow.

Radio Ethernet statistics support the following views:

362

•

Class Of Service—Provides Ethernet statistics tracking the number of TDFs per Ethernet QoS queue, Available Capacity, and TTOs per Ethernet QoS queue.

•

Queue #5 through Queue #1—Provides Ethernet statistics tracking the number of TTOs, TTFs, TDFs, Available Capacity, TTO Throughput, and TDF Ratio associated with the selected Ethernet QoS queue.

•

Ethernet Aggregate Tx—Provides Ethernet statistics tracking the number of TTOs, TTFs, TDFs, Available Capacity, TTO Throughput, and TDF Ratio associated with the aggregate Tx Ethernet radio flow.


7.18.2


Adaptive modulation PM Adaptive modulation PM records the modulation scheme used for the transmitter when adaptive modulation is enabled. In the 1+1 HSB radio configuration, the statistics are associated with the link level after radio protection switching. Adaptive modulation PM is not supported in 1+1 FD radio configurations.

7.18.3

Radio PM Radio PM provides an indication of the QoS and the radio power levels of the transmitters and receivers associated with the Radio Hop Section and Link Hop Section, defined as follows:

7.18.3.1

•

Radio Hop Section—The unprotected radio channel (before radio protection switching in 1+1 radio configurations).

•

Link Hop Section—The protected radio channel (after radio protection switching); only supported in 1+1 radio configurations.

Radio analog PM PM of the local analog Tx and Rx power levels is supported on MPT-HC/HC-HQAM. PM counters are available for each radio hop and link (on the 1+1 Rx side only). The available radio analog PM counters are:

7.18.3.2

•

Tx Minimum Power Level

•

Tx Maximum Power Level

•

Tx Average Power Level

•

Rx Minimum Power Level

•

Rx Maximum Power Level

•

Rx Average Power Level

Radio Ethernet PM

PM of the radio Ethernet statistics related to the Tx radio link are supported for each radio direction. The available Radio Ethernet PM counters are: •

Total Number of Tx Packets

363


7.18.3.3


•

Total Number of Tx Bytes

•

Total Number of Tx Discarded Packets

Radio hop PM PM of the radio hop section (before radio protection switching) is supported for each radio hop. The available radio hop PM counters are:

7.18.3.4

•

Errored Seconds (ES)

•

Severely Errored Seconds (SES)

•

Background Block Errors (BBE)

•

Unavailable Seconds (UAS).

Radio link PM

PM of the protected radio channel (after radio protection switching) is supported for each radio link. The available radio link PM counters are:

7.18.3.5

•

Errored Seconds (ES)

•

Severely Errored Seconds (SES)

•

Background Block Errors (BBE)

•

Unavailable Seconds (UAS).

Radio QoS PM PM of the radio QoS queues (queues 1 to 5) related to Ethernet traffic for each radio direction is supported. The available radio QoS PM counters are: •

Number of Tx Packets

•

Number of Tx Bytes

•

Number of Tx Discarded Packets

•

Number of Rx Packets

•

Number of Rx Bytes

Three radio QoS views are available: Radio Link, Radio Hop Ch#1, and Radio Hop Ch#0.

364



Defect second on a radio hop section is a second in which an LOF or DemFail occurs. Defect second on a Link hop section is a second in which an LOF occurs at the link level after radio protection switching. Errored Block count for a radio hop section is the number of errored blocks. Errored Block count for a link hop section is the number of errored blocks at the link level after radio protection switching. Four counters are supported for radio QoS, as follows: •

Errored Second (ES)—When a defect second is set or there is at least one or more errored blocks.

•

Severely Errored Seconds (SES)—When a defect second is set and the errored block count is greater than or equal to 30% of the blocks in 1 s.

•

Background Block Error (BBE)—The number of block errors in a 1-s period and the second is not an SES.

•

Unavailable Seconds (UAS)—A time period starting after ten consecutive SES events are detected, and ending upon the detection of ten consecutive non SES events. The non-SES seconds are not included in the UAS time period.

Threshold crossing alarms (TCA) are supported for radio QoS PM. TCA thresholds can be provisioned from the Threshold Editor. Two default TCA threshold data tables are provided: one for 15-min TCAs and one for 24-h TCAs. Two additional TCA threshold data tables can be provisioned for both 15-min TCAs and 24-h TCAs. See Table 38 for default TCA thresholds values. Table 38

Radio PM default TCA threshold alarm values

TCA alarm

15-minute low

15-minute high

24-hour low

24-hour high

BBE

200

9000

0

48000

ES

20

180

0

1500

SES

0

15

0

20

7.18.3.6

Radio power level PM Five radio power level counters are supported.available:

365



•

Analog Hop Rx Ch#1

•

Analog Hop Rx Ch#0

•

Analog Hop Tx Ch#1

•

Analog Hop Tx Ch#0

•

Analog Link (Rx power level for the hop receiver that is active for the link)

Three radio power level counters are supported for each radio power level tab, as follows:

7.18.3.7

•

Minimum Level—Minimum power level measured on the port during the collection period.

•

Average Level—Average power level measured on the port during the collection period.

•

Maximum Level—Maximum power level measured on the port during the collection period.

Radio RSL PM PM of the local Receive Signal Level (RSL) and Transmit Signal Level (TSL) is supported for each MPT-HL or MPT-HLC radio link. For radio links configured with 1+1 RPS, the RSL of the active channel in monitored. The available Radio RSL PM counters are: •

Lowest RSL

•

Highest RSL

•

Average RSL

•

Lowest TSL

•

Highest TSL

•

Average TSL Note: The following notes apply: • • •

366

RSL history is not available within the first 15 minutes after the system is provisioned. RSL history can be retrieved using Web Server. Timestamps are always provided in UCT. Following an NE time change, PM history data must be cleared to prevent reporting erroneous PM history data.


7.18.4


PDH PM PDH PM provides an indication of the QoS of the incoming and outgoing signals associated with E1/DS1 PDH signals. A defect second on an incoming E1/DS1 signal is a second in which an LOS, SEF (framed signal mode only), or AIS occurs. A defect second on an outgoing E1/DS1 signal is a second in which an LOS CES, SEF (framed signal mode only), or AIS occurs. Four counters are supported for E1/DS1 PDH PM, as follows: •

Errored Second (ES)—When a defect second is set or there is one or more errored blocks.

•

Severely Errored Seconds (SES)—When a defect second is set and the errored block count is greater than or equal to 30% of the blocks in 1 s.

•

Background Block Error (BBE)—The number of block errors in a 1-s period, if the second is not an SES. If the second is an SES, the BBE count is set to zero.

•

Unavailable Seconds (UAS)—A time period starting after ten consecutive SES events are detected, and ending upon the detection of ten consecutive non SES events. The non-SES seconds are not included in the UAS time period.

Threshold crossing alarms (TCAs) are supported for PDH QoS PM. TCA thresholds can be provisioned from the Threshold Editor. Two default TCA threshold data tables are provided: one for 15-min TCAs and one for 24-h TCAs. Two additional TCA threshold data tables can be provisioned for both 15-min TCAs and 24-h TCAs. See Table 39 for PDH default TCA thresholds values. Table 39

PDH PM default TCA threshold alarm values

TCA alarm

15-minute low

15-minute high

24-hour low

24-hour high

BBE

0

13296

0

132960

ES

0

65

0

648

SES

0

10

0

100

367


7.18.5


SDH PM SDH PM provides an indication of the QoS of the incoming and outgoing signals associated with SDH signals. A defect second on an incoming SDH signal is a second in which an LOS or LOF occurs. A defect second on an outgoing SDH signal is a second in which an LOF occurs. The following counters are supported for SDH PM: •

Background Block Error (BBE)—The number of block errors in a 1-s period, if the second is not an SES. If the second is an SES, the BBE count is set to zero.

•

Out of Frame Second (OFS)—When an OOF event, LOF alarm, or LOS alarm is detected in a 1-s period.

•

Errored Second (ES)—When a defect second is set or there is one or more errored blocks.

•

Severely Errored Seconds (SES)—When a defect second is set and if the errored block count is greater than or equal to 30% of the blocks in 1 s.

•

Unavailable Seconds (UAS)—A time period starting after ten consecutive SES events are detected, and ending upon the detection of ten consecutive non-SES events. The non-SES seconds are not included in the UAS time period.

•

Loss of Packet Second (LPS)—An LPS is generated if at least one Loss of Single Packet (LOP) is detected in 1 s. If an OOF is also detected in the same second, both an LPS and an OFS event are generated. If an LOF is also detected, an SES is generated and an LPS is not generated. LPS events are only generated for outgoing signal monitoring. Note: Due to a difference in NE time between the NE where the outgoing signal is monitored and the NE where the incoming signal is monitored, the monitoring second may start at different times on the two NEs. Therefore the same alarm event can generate counters on both NEs with a time difference of one second.

Threshold crossing alarms (TCAs) are supported for SDH PM. TCA thresholds can be provisioned from the Threshold Editor. Two default TCA threshold data tables are provided: one for 15-min TCAs and one for 24-h TCAs. Two additional TCA threshold data table can be provisioned for both 15-min TCAs and 24-h TCAs. See Table 40 for SDH default TCA thresholds values.

368



Table 40

7.18.6

SDH PM default TCA threshold alarm values

TCA alarm

15-minute low

15-minute high

24 hour

BBE

200

24000

36000

ES

5

50

150

SES

0

10

15

OFS

0

900

86400

RSL History RSL History PM provides an indication of the radio power levels of the transmitters and receivers associated with the Radio Hop Section and Radio Link Section for both the local and far-end. Additionally, RSL History PM records the TPS and RPS switch statuses, and HBER alarms for both the local and the far-end. Eight radio power level counters are supported: •

Local Tx (Ch#0 and Ch#1)

•

Local Rx (Ch#0 and Ch#1)

•

Remote Tx (Ch#0 and Ch#1)

•

Remote Rx (Ch#0 and Ch#1)

Eight protection switch status indicators are supported: •

Local TPS (Ch#0 and Ch#1)

•

Local RPS (Ch#0 and Ch#1)

•

Remote TPS (Ch#0 and Ch#1)

•

Remote RPS (Ch#0 and Ch#1)

369


7.18.6.1


RSL History with Transmit Diversity Antenna When TDA is enabled, the local TPS status of the main channel reports Active when the main antenna is selected and Inactive when the diversity antenna is selected. That is, the local TPS status of the main channel reports the protection switch status of the diversity antenna. The local TPS status of the spare channel reports Active when the spare transmitter is selected and Inactive when the spare transmitter is in standby. That is, the local TPS status of the spare channel reports the protection switch status of the transmitter. This is the same behavior as when TDA is not enabled. For example, if the main transmitter and spare antenna were active, the local TPS status would report Inactive on both channels. Remote TPS status counters reflect only the status of the transmitter at the remote site. Note: The TPS status reported in the protection screens and in the MIB does not change its behavior when TDA is configured.

7.19

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 cannot be exchanged with specific user Ethernet ports/radio directions. Port segregation allows partitioning of Core, P8ETH, EASv2, MPT Access Ethernet and Radio switch ports into virtual private domains. For example, if all traffic from one Ethernet port must be forwarded only in one radio direction, it is recommended to enable traffic exchange only between these ports. Each packet received on a specific port will be forwarded only to the ports in the same virtual private domain. The use of port segregation separates the network into different domains. This means that the effect of potential issues is limited to on small parts of the network. Consequently the use of port segregation can make the network more stable in the case of incorrect configuration performed in the field. If a port is segregated from all other available ports or peripherals, all packets are blocked.

370



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)

Using JUSM it is possible to change this default configuration. When TDM flow crossconnections are defined and involve TDM ports, port segregation involving these ports are implicitly prohibited. There are several situations where port segregation and EFM OAM Remote Loopback are not compatible:

7.19.1

•

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.

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.

7.19.2

TDM ports Port Segregation is not supported for TDM ports (DS1/DS3/OC-3) by ECT/NMS. At system level TDM ports are segregated among them and not segregated from Radio directions involved in TDM flows cross-connections.

371


7.19.3


MPT access, P8ETH and EASv2 Ethernet ports The information in this section applies to MPT access peripheral ports, P8ETH user ports, P8ETH, and EASv2 radio ports. Port segregation can be applied by the operator at two different points: •

between ports connected to MPT ODUs: to segregate connected MPT ODUs

•

between ports connected to MSS backplane and the other backplane ports: to segregate all connected MPT ODUs towards User Ports or other radio directions.

In case only one MPT is connected to the port, the port segregation behavior is as shown in Figure 120. Figure 120

Port segregation with one MPT connected to the port Any Core part

Any Core part

Any Core part

X Core

Core

X

X

Active

Active

Active

Active

Peripheral Card

Peripheral Card

Peripheral Card

Peripheral Card

MPT

MPT

MPT

MPT

Active

Active

Active

Active

With frame duplication: segregation ensures only no loop in the network

No frame duplication at all: each core port is mapped to a single ODU at the time No3400

Assuming two MPT ODUs in 1+0 configuration are connected to the same card, (the only configuration supported within this release with more than one MPT on same MPT Access peripheral), the following scenarios have to be considered: 1. no port segregation is applied by operator between ports and to port towards backplane: in this case, all the involved ports can exchange the data among them (case A);

372



2. port segregation is applied by operator between ports, while no port segregation is applied by operator to port towards backplane: in this case, the two MPT ODUs 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 ports, while operator applies segregation to port towards backplane. This case represents a card isolated from MSS backplane, in such case, the two MPT ODUs can only exchange data between them (case C). 4. A fourth scenario for application of port segregation is possible, but in this release is not applicable: port segregation is applied by operator between ports and port towards backplane, no traffic can be exchanged between MPT ODUs and with MSS with the current number of supported ports. No check has been implemented to forbid this application of port segregation since it can be applied in future releases where use of all MPT Access peripheral ports is supported (case D). Figure 121

Port segregation scenario: MPT access

When two P8ETH, EASv2 or MPT Access plug-ins are equipped in the same shelf row, port segregation can be applied between all ports across the two plug-ins. Port segregation can be applied to:

373



•

User ports (either electrical or optical)

•

a User port and a Radio port

•

Radio ports

Port segregation between P8ETH, EASv2 or MPT Access port and Core ports is not allowed. For any individual port on a P8ETH, EASv2 or MPT Access port, port segregation between User or Radio ports in different shelf rows is not allowed. Figure 122 shows an example of port segregation with stacked EASv2 cards in slots 3 and 4 and another EASv2 card in slot 5. Figure 122

Port segregation scenario: EASv2 cards

Segregation of the EAS ports on the same row of the MSS looks different than between slots of different rows because the stacked EAS cards have direct interconnectivity via the backplane. At a glance, all ports (physical and Radio LAG) not being used for the data transport in one radio link direction are segregated from each other and no Ethernet data can pass between them. Using the port segregation configuration shown in Figure 122 allows only the following Ethernet data flows:

374

•

EASv2 at slot#3: P#1 can exchange data with the Radio LAG of this EASv2

•


•


•

All EASv2 boards could have a data flow to a Core user interface if enabled and required.


7.19.4


MPT ODU number for each MPT plug in

If port segregation is applied by operator to an MSS User port and to MPT Access plug-in port towards backplane, MPT ODUs connected to the 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. Figure 123

Port segregation scenario: MPT access

375


7.19.5


MPT ODU in protection Explicit port segregation between protected MPTs is not allowed. MPT protection cannot be configured if the associated SFPs have been segregated. Port segregation between protected MPTs is implicitly applied. Port segregation is removed when the protection is removed.

7.19.6

MPT ODUs protected on different plug-ins When two MPT ODUs are provisioned for 1+1 protected configuration on two different peripherals, the plug-in ports towards backplane will not be implicitly segregated from each other. Otherwise, when a future release supports the possibility to connect another MPT to the same MPT Access peripherals, it would not be possible to have it in repeater configuration with the protected MPT pair. Operator is allowed to apply port segregation to MPT Access peripherals hosting an MPT pair in 1+1, but since connection to other MPT on same plug-in is not supported in this release, only the segregation of MPT Access port towards the backplane is effective. The spare radio direction must have the same port segregation configuration (for the plug-in port towards the backplane). Any previous port segregation configuration for spare radio direction must be deleted by operator.

7.19.7

MPT ODUs protected on the same plug-in When two MPT ODUs are provisioned for 1+1 protected configuration on the same P8ETH, EASv2 or MPT Access peripheral, the plug-in ports facing the MPTs have to be segregated from each other. The MPT Access interface facing the Core card can be segregated from other peripheral interfaces of User Ethernet interfaces of the Core card.

376


7.19.8


ERPS Ring ports

To segregate one port from ERPS Ring ports both Ring ports must be segregated from that port. Segregation of one port from one Ring port causes inconsistent behavior of traffic delivery over the ring.

7.20

Remote inventory Remote Inventory (RI) provides operators with the capability to remotely determine what equipment is installed in the system. RI data contains information programmed in the factory to indicate the configuration, capability, and compatibility of the subrack and any installed MSS cards, MPT ODU, and MPT-HL transceivers. Security The system provides a mechanism to protect access to the NE.

7.20.1

User authentication Communication access is accomplished using Username and Password authentication. An NE supports a maximum of twenty-three provisioned users.

7.20.2

User profile management NE rejects username and passwords that do not meet complexity parameters. These complexity parameters are as follows: •

Username length: Username must not exceed twenty characters in length.

•

Password length: Passwords must not be less than eight and not longer than twenty characters in length.

•

Password composition: Passwords must be composed of UPPER case, lower case, numeric, and special characters.

Access privileges to the system are controlled using four user profiles. User profiles privileges are as follows:

377


7.20.3


•

Administrator: Full access to the NE including security parameters.

•

CraftPerson: Users assigned to installation and maintenance tasks at the radio site. Full access to the NE except security parameters.

•

Operator: Users assigned to operational tasks at the network level, not at the radio site.

•

Viewer: Users who require read only access.

SNMP operating mode (SNMPv3 support) The SNMP operating mode of the NE can be set using WebEML or the web interface. The following SNMP operating modes are supported: •

SNMPv2: Only SNMPv2 or v1 managers can access the NE. This is the default operating mode.

•

SNMPv3: Only SNMPv3 managers can access 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.

7.20.4

SNMPv2 community string The system supports SNMPv2 Community String (CS).

378



Two Community Strings are supported, “Get CS” and “Set CS”. CS must not be less than six and not longer than ten characters in length. Only alphanumeric characters are supported.

7.20.5

SSH and SFTP support

The system supports the client-server model for SSH. The server mode is enabled at startup and cannot be disabled. The operator can open up to five simultaneous SSH sessions. The client mode is supported only for file downloads using SFTP. SFTP is not used for internal file transfers between CPUs within a 9500 MPR system. FTP or SFTP can be used to download software. When SFTP is used, the server host key fingerprint must be provided during download initialization. FTP is the default protocol selection. If FTP is disabled, only SFTP can be used. SFTP cannot be disabled. Backup and restore file transfers can also be performed using either FTP or SFTP. To initiate an SFTP session, the user must have either administrator or craftperson privileges.

7.21

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 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 affect traffic including a possible long outof 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.

379



Alcatel-Lucent recommends backing up the system, including the license key, before performing a software upgrade or rollback. If a provisioning mismatch alarm is generated after the rollback, apply the license key from the earlier release. 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 (that is, Rxx.xx.xx ICS01 and Rxx.xx.xx ICS02)

•

release versions that differ by the last digits of the release version number (that is, 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 41 provides a list of supported software package rollbacks: Table 41

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

R 4.0.0 or R4.1.0

No

R4.0.0 or later

R4.1.0 or later

Yes

7.22

Stacking for EAS/EASv2/MPT access cards Two EAS cards, two EASv2 cards, or two MPT Access cards installed on the same row (for example, slot #3 and slot #4) are automatically configured in stacking configuration. The benefits of stacking are:

380

•

The intra-board traffic between the two cards does not transit through the Core card (no traffic effect in case of Core switch).

•

Each port of the cards can be individually segregated from the other ports.


7.23


Synchronization All 9500 MPR radios in the network must be synchronized to the same Master clock. This clock is also called the Network Element Clock (NEC). Only one radio in the network is provisioned Master. All other radios in the network must be provisioned Slave. The slave radios all sync to the clock provided by the master.

7.23.1

Sync switching With the exception of the master when the radio is provisioned to sync from the local oscillator, the sync clock source is switched from primary to secondary if the primary source fails. Sync clock switching provisioning is dependent on the role of the radio in the network (master or slave) and on user preference. A revertive switching feature is a provisioning option that restores the sync clock to the original source when the alarm on the primary source is cleared. If revertive switching is not selected, the secondary sync source will continue to provide sync clock after the alarm is cleared. If the secondary source fails, the sync clock switches to the primary source. The MPT-HL sends out Do Not Use signals (DUS) in the following situations: •

The MPT-HL is not receiving reliable timing information from the Ethernet port, or there is a timing issue with a P8ETH, EASv2, or MPTACC peripheral.

•

An NE upstream of the MPT-HL and an NE downstream of the MPT-HL are using the MPT-HL as a synchronization source. This creates the possibility of a timing loop.

If the NE receiving the DUS is using the MPT-HL as a synchronization source, the DUS will trigger a synchronization switch.

381


Figure 124


Synchronization block diagram MSS-4/8 Core-E MD300 MPTACC P8ETH EASv2 Module

ODU/ MPT

P32E1DS1/ P2E3DS3/ SDHACC Module

Core-E MD300 MPTACC P8ETH EASv2 Module

ODU/ MPT

Radio Port Sync-In Port

E1/T1/ STM1/OC-3 Port PLL

CLK SELECT

Selected Sync Source

P32E1DS1/ P2E3DS3/ SDHACC Module N

LOCAL OSC Free-Run Local Oscillator

User Ethernet Port

Sync in Ethernet Port In/Out

Synchronous Ethernet clock

Core-E Module

Sync out 23232

7.23.2

Master synchronization mode An NE provisioned Master NEC supports two provisionable restoration modes; Revertive and Not Revertive. In Revertive mode, the NEC will automatically revert to the selected primary clock source after the failed primary clock source functionality has been restored. In Not Revertive mode, the NEC will remain on the selected clock source until failure is detected on the selected clock source. The master primary clock synchronization source is provisionable to one of five clock sources; free running local oscillator, any available input E1 or DS1 port, Sync-In port, any available SyncE Ethernet port, or any available STM-1/OC-3 port. The secondary master clock sources available are dependent on the primary master clock source selected. Three rules determine the available secondary master clock sources available: 1. Primary clock source selected is not permitted to be the secondary clock source.

382



2. When an E1/DS1 port is selected, other E1/DS1 ports supported by the same E1/DS1 card are prohibited from being the secondary clock source. 3. If an STM-1/OC-3 is chosen to be Primary source, another STM-1/OC-3 coming from the same peripheral cannot be selected as the secondary source and vice-versa. 4. When free running local oscillator is selected as primary clock source, no secondary clock source is supported.

7.23.2.1

E1/DS1 port The E1/DS1 port must meet the interface requirements in G.824, Section 6.

7.23.2.2

Synchronization input/output ports The Sync-In port supports four frequency options: 1.024, 2.048 MHz, 5 MHz, or 10 MHz. The NEC supports a dedicated Sync-Out port. The Sync-Out port supports four frequency options: 1.024, 2.048 MHz, 5 MHz, or 10 MHz. The Sync-In and Sync-Out ports can be dedicated ports on the card or the Sync-In/ Out SFP on the CorEvo or MSS-1.

7.23.2.2.1

Sync-In/Out SFP

The CorEvo card and MSS-1 unit do not have dedicated Sync ports. The Sync-In/ Out SFP provides both Sync-In and Sync-Out ports. The SFP can be installed in 1 GbEth SFP ports 7 and 8 of the CorEvo card and ports 5 and 6 of the MSS-1.

7.23.2.3

Synchronization status messaging The system supports Synchronization Status Messaging (SSM). SSM can be provisioned as enabled/disabled for radio interfaces. 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.

383



The NEC uses Clock Source Quality Level (QL) to select the clock source for the NEC. See Table 42 for a list of supported QL SSM codes and their priority. Table 42

Sync source selection details

SSM QL CODE

PRIORITY

QL-PRC

Highest

QL-SSU-A QL-SSU-B QL-SEC QL-DNU

Lowest All other SSM codes are not supported and are considered: QL-INV: Invalid Quality Level. See Table 43 for a list of supported QL SSM codes and their priority.

Table 43

Default quality level for Primary and Secondary Clock comparison

SYNC SOURCE

DEFAULT QUALITY LEVEL VALUE

Free Run Local Oscillator

QL-SEC

DS1 Port

QL-SSU-A

Sync-In Port

QL-SSU-A

STM-1/OC-3 Port

QL-SSU-A

Radio Port or L1 LAG interface (SSM Enabled)

Acquired from incoming ESMC messages

Radio Port or L1 LAG interface (SSM Disabled)

QL-SSU-A

7.23.2.4

SSM operation Enabling SSM on a radio port configures the radio interface to send ESMC messages out the port. When the radio interface is configured as a sync source and SSM is enabled, the received ESMC messages are used according to the sync source selection table.

384



When the radio interface is not configured as a sync source and SSM is enabled, the received ESMC messages are forwarded to the downstream node can use the ESMC messages for sync source selection. The local NE ignores the ESMC messages for sync source selection. The radio port must be configured as a sync source and SSM enabled for Loss of ESMC alarm to be declared.

7.23.3

Slave synchronization mode An NE provisioned Slave only supports the revertive restoration mode. The Slave primary clock synchronization source can be provisioned to use one of three clock sources; Sync-In port, Radio/MPT port, or any available SyncE Ethernet port. The secondary slave clock sources available are dependent on the primary slave clock source selected. Two rules determine the available secondary slave clock sources available: 1. Primary clock source selected is not permitted to be the secondary clock source. 2. When a Radio/MPT port is selected, the same Radio/MPT port is not permitted to be the secondary clock source.

Table 44 describes synchronization clock sources available per clock role selected.

385


Table 44


Synchronization clock sources available per clock role

CLOCK ROLE

PRIMARY SOURCE

SECONDARY SOURCE AVAILABLE

Master

Free Run Local Oscillator

None (No secondary clock source supported)

E1/DS1 Port

Free Run Local Oscillator E1/DS1 Port available from a different E1/DS1 card Sync-In Port Synch-E enabled Ethernet port OC-3 (STM-1) L1 Radio LAG None

Sync-In Port

Free Run Local Oscillator E1/DS1 Port Synch-E enabled Ethernet port OC-3 (STM-1) L1 Radio LAG None

Synch-E enabled Ethernet port

Free Run Local Oscillator E1/DS1 Port Sync-In Port Synch-E enabled Ethernet port OC-3 (STM-1) L1 Radio LAG None

386


Table 44


Synchronization clock sources available per clock role (Continued)

CLOCK ROLE

PRIMARY SOURCE


Master (continued)

OC-3 (STM-1)

Free Run Local Oscillator E1/DS1 Port Sync-In Port Synch-E enabled Ethernet port OC-3 (STM1) L1 Radio LAG None

Slave

Sync-In Port

Free Run Local Oscillator E1/DS1 Port Radio/MPT Port Synch-E enabled Ethernet port OC-3 (STM-1) L1 Radio LAG None

Radio/MPT Port

Free Run Local Oscillator E1/DS1 Port Sync-In Port Radio/MPT Port from a different Radio/MPT Port Synch-E enabled Ethernet port OC-3 (STM-1) L1 Radio LAG None

387


Table 44


Synchronization clock sources available per clock role (Continued)

CLOCK ROLE

PRIMARY SOURCE


Slave

Synch-E enabled Ethernet port

Free Run Local Oscillator E1/DS1 Port Sync-In Port Radio/MPT Port Synch-E enabled Ethernet port OC-3 (STM-1) L1 Radio LAG None

L1 Radio LAG

Free Run Local Oscillator E1/DS1 Port Sync-In Port Radio/MPT Port Synch-E enabled Ethernet port OC-3 (STM-1) L1 Radio LAG None

7.23.4

Normal operation During normal operation, the master can be provisioned to get sync clock from two separate sources: an internal local oscillator (most common source) or external clock from customer provided equipment. The slave radios can be provisioned to receive the sync clock from one of two sources: clock recovered by the radio receiver or the sync clock from another radio in the network. Normally at a repeater, the sync clock is received over the RF path and recovered by the radio receiver. A typical slave terminal uses the clock from an adjacent radio.

388


7.23.5


Failed primary operation With the exception of the master when the radio is provisioned to sync off the local oscillator, the provisioned secondary sync source is enabled if the primary source fails. When the master, provisioned to accept sync clock at the Core from an external source, fails, the internal free-running local oscillator is enabled. Provisioning choices for the secondary source for slave radios are dependent upon the choices made from the primary source. See the following descriptions for details.

7.23.6

Wait-to-restore The system supports a provisionable Wait-To-Restore time to ensure the QL of a sync source. After a clock source defect has been cleared, the Wait-To-Restore time is applied before the new QL value is passed to the sync source selection process. Wait-To-Restore time is provisionable from 0 to 12 minutes in steps of 10 seconds. In revertive mode, the wait-to-restore time is the time the system takes to return to the primary source after the alarm is cleared.

7.23.7

Holdover In the event both the primary and secondary sync sources fail. The NE will use the free run local oscillator as its sync reference.

7.23.8 7.23.8.1

Synchronization for PDH/SDH/DATA 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” Three main methods can be used to recover at the Rx site, the original bit rate:

389



•

Differential clock recovery (DCR): recalculation of the original clock based of the Delta respect to a reference clock that is available at both Tx and Rx site (Differential: used in case of clock distribution on the whole network. It’s more reliable than Adaptive; also used in TDM2TDM traffic (MPR to MPR)). This method can be selected for each PDH/SDH stream.

•

Adaptive clock recovery (ACR): based on the average rate at which the packets (fragments) arrive at RX site (Adaptive: simpler network, but performances depends on the PDV (Packet Delay Variation) in the Network. Always used when the reference clock isn’t distributed on the whole network). This method can be selected for each PDH/SDH stream.

•

Node Timing: timing from the network clock as defined in G.8261. The enabling of the Node Timing is applied to all tributaries of the PDH/SDH unit.

•

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 popular way to recover the clock in the industry of service routers and site aggregator boxes. This feature inside the 9500 MPR platform adds interworking capabilities with third parties service routers and circuit emulations gateway.

•

In node-timing working mode, all the tributaries are re-sampled with the network element clock. This means that, as also reported in G8261, this method does not preserve the service timing (clock).

•

Recovered clock is according to G. 823 synchronization masks.

The available clock recovery techniques with TDM2TDM and SDH2SDH profiles are: •

DCR: differential clock recovery

•

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

•

Node timing.

Note: In meshed networks (rings) do not close the synchronization configuration.

Note: If the NODE TIMING is enabled, the CT still proposes the 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.

390


7.23.8.2 Figure 125


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

7.23.8.3 Figure 126

Adaptive clock recovery


Common reference clock is not available at both ends.

391



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.

7.23.8.4

SyncE The system supports electrical and optical Synchronous Ethernet (SyncE) signals on Core Ethernet ports. When SyncE is enabled on a port, the receive side extracts the frequency of the input signal and passes it to the system clock as a candidate frequency reference. SyncE interfaces support SSM for synchronous Ethernet and ESMC processing according to ITU-T G.8264. SyncE is supported in the following configurations: •

Core and EASv2 Ethernet Ports (electrical and optical) −

7.23.8.5

When Electrical Ethernet Port, the user must configure the port as Master or Slave

•

User Ethernet port may be configured 1000 Mb/s

•

SyncE is not supported on P8ETH Ethernet ports

Synchronization protection 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. Sync status messages (SSM) are supported by SyncE enabled interfaces (Core and EASv2 User Ethernet interfaces working in synchronous operation mode), radio interfaces, and L1 LAG ports. SSM carries information about the quality level of the source clock from clock to clock along the network. There are a number of pre-defined quality levels (QL) corresponding to existing clock specifications that is, QL-PRC, QL-SSU-A, QL-SSUB, QL-SEC and QL-DNU. The last message means ‘Do Not Use’. This signaling system is used for controlling protection switching in case of link or clock failures and protecting against sync loops. Of course, SSM also exists in Synchronous Ethernet. It works in exactly the same way as in SDH and SONET. The only difference is the communication channel used for transferring the SSM from clock to clock. In SDH

392



and SONET the SSM is contained in the SSM Byte (SSMB) of the STM-n or OC-n frame overhead. Synchronous Ethernet uses ‘Ethernet Synchronization Messaging Channel’ or ESMC. It consists of special Ethernet frames. The important point to note here is that there is a perfect continuity between SDH and SONET on side, Hybrid NEs and Synchronous Ethernet on the other. SSM messages represent the quality level of the system clocks located in the various network elements. SSM contains the Clock Quality Level (QL) and Quality Level Priority (QLP). QLP is optional. Quality level refers to the holdover performance of a clock. SSM messages shall be received and monitored on interfaces that are configured as sync sources and with SSM support enabled; otherwise received messages shall be ignored and silently discarded. In this case, The default (initial) value for the QL is DNU and QLP is Undefined until a valid QL/QLP is received over the interface. When a valid QL is received by an interface providing a sync source signal, the carried SSM-QL is assigned as the clock QL of this interface and used by the system clock selection algorithm. Lack of reception of an SSM within a five-second period results in the QL of the interface being set to QL-FAILED and QL Priority being set to Undefined. Loss of ESMC defect is raised and it is cleared on receipt of the first SSM. SSM messages are generated on interfaces with SSM enabled. These messages are generated once per second. Given two sync sources, the NEC will use QL/QLP to determine the selected sync source. The selected QL/QLP will be sent out over interfaces with SSM enabled. 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;

393



•

Clock Source Quality Level Priority

The QL-DNU and QL Priority Undefined are advertised over the synchronization interface that is currently selected to avoid sync loops. When a Signal Fail or Signal Degrade defects are detected on a synchronization clock source input, the Quality Level of this source input is set to QL-FAILED value. When the NEC goes into holdover, the QL is set to QL-SEC/QL-EEC1. Figure Figure 127 to Figure 129 is a ring example using DNU to prevent loops and used during protection switching: Figure 127

Ring network with SSMs and port priorities normal situation PRC

1

2 SEC PRC

2 SEC PRC

1

PRC

1

PRC

1

1

PRC

SEC DNU

DNU

Timing Hub Node

SEC 2

2 SEC

1 not a sync port

DNU

not a sync port DNU

2

SEC DNU

2 22921

394



Figure 128

Ring network in restoration process - last node switched reference

Figure 129

Ring network in restoration process - final situation

SSM ESMC messages are queued in Q6. SSM are sent one per second, so the bandwidth is very low. 32 octets but future extensions could be larger.

395


7.23.8.6


Synchronization quality level According to Table 8 of ITU-T G.781 the Clock Source Quality Level is identified by the following SSM Codes:

Table 45

•

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

SSM quality levels

Quality Level

Order

QL-PRC

Highest

QL-SSU-A

|

QL-SSU-B

|

QL-SEC/QL-EEC1

|

QL-DNU

|

QL-FAILED/QL-INV

Lowest

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.

7.23.8.7

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:

396


Table 46


•

0x01 - Master1

•

0x10 - Slave1

•

0x00 - Undefined

SSM quality levels

Quality Level Priority

Order

Master1

Highest

Slave1

|

Undefined

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

7.23.8.8

Hold-off and wait-to-restore In order to correctly manage the QL-FAILED (Clock Source Fail or Clock Source Degrade) the automatic selection process must take into account the Hold-Off time and Wait-To-Restore time defined in ITU-T G.781: •

The Hold-Off time ensures that short activation of signal fail are not passed to the selection process. The QL value of QL-FAILED is passed to the selection process after the Hold-off time. In the 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-To-Restore time is applied before the new QL value is passed to the selection process. In the meantime, the quality level QLFAILED is passed to the selection process. The Wait-To-Restore time is the

397



same for each input of the selection process and it is configurable in the range of 0 to 12 minutes in steps of 10 seconds. The default value is 5 minutes. When changed before its expiration, the WTR time restart from the new value without take into account the previous remaining time to expiration. The WTR time is also applied when a LOS of ESMC defect is cleared on a synchronization clock source, also in that case the quality level QL-FAILED is passed to the selection process until the WTR time expires.

7.23.8.9

Synchronization sources assignment The physical interfaces to be assigned to Primary and Secondary synchronization sources can be selected from the following: 1. Free Run Local Oscillator: −

is not affected by any alarm (no Fail, no Degrade)

−

Quality Level value is fixed to QL-SEC/EEC1 (G.812/G8262)

−

QL Priority is Master1 if the NEC is configured as Master

−

QL Priority is Slave1 if the NEC is configured as Slave

2. E1/DS1 which is enabled on input traffic interface: −

meets the interface requirements in G.824, Section 6

−

the specific E1/DS1 port must be selected

−

For these sources the Fail alarm has to be detected by CRU when LOS, AIS, or LOF (in case of DS1s framed) occurs

−

Default value for Quality Level is QL-SSU-A (G.812)

−


−

QL Priority is Slave1 if the NEC is configured as Slave.

3. Synchronization signal available from the dedicated Sync-In port must be configured from 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 correctly scaled from 2.048 MHz to 1.024 MHz.

398

•

Fail alarm is detected by CRU when LOS occurs

•


•




•


4. The Symbol Rate of the RX signal of any available Radio: −

the specific Radio Port must be selected

−

Fail alarm must be detected by CRU when a DEM-Fail or a Loss of Radio Frame occurs

−

When SSM support is enabled, the QL and QL Priority are acquired from ESMC PDUs received on the selected radio interface

−

When SSM support is disabled, the default value for Quality Level is QLSSU-A (G.812)

−


−


5. A SyncE clock source available at enabled User Ethernet traffic interface: −

electrical or optical interface configured in synchronous operation mode at 1000 Mb/s.

−

the specific User Ethernet port must be selected

−

from ITU-T G.8261 point of view, the MSS is Synchronous Ethernet equipment, equipped with a system clock (NEC) following the ITU-T G.8262 recommendation.

−

When SSM support is enabled, the QL is acquired from ESMC PDUs received on the specific Synchronous Ethernet interface

−

by default, the QL Priority is not advertised by ESMC PDUs

−


−


−

when the QL Priority is advertised by ESMC PDUs, the QL Priority is acquired from them

−

when the SSM support is disabled, the default Quality Level is QL-SSUA (G.812) and QL Priority is Master1 if the NEC is configured as Master and QL Priority is Slave1 if the NEC is configured as Slave

−

electrical User Ethernet interfaces perform link auto negotiation to determine the master/slave role for clock 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 CT/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.

399



−

For Synchronous Ethernet clock sources from electrical User Ethernet ports the Fail/degrade alarm will be raised when Loss of Synch (that is, Ethernet Link Down) occurs.

−

For Synchronous Ethernet clock sources from optical User Ethernet ports the Fail/degrade alarm will be raised when Loss of Optical signal occurs.

6. Any OC-3 (STM1) available at SDH input traffic interface: −

the specific OC-3 (STM1) port must be selected

−

Fail alarm will be raised when LOS, LOF, TIM, MS-AIS, or High BER occurs

−


−


−

QL Priority is Slave1 if the NEC is configured as Slave.

7. Any L1 Radio LAG with administrative state enabled. −

NE selects one of the LAG members according to current alarm status

−

in case of synchronization failure to the current reference, the NE performs a selection switch to another member of the LAG

−

When SSM support is enabled, the QL Priority is advertised by ESMC PDUs, the QL Priority is acquired from them

−

when the SSM support is disabled, the default Quality Level is QL-SSUA (G.812)

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.

400


7.23.8.10


Synchronization sources assignment rules Some rules have to be followed while assigning the Primary and Secondary clock sources: The NEC has to be defined (configured) as Master or Slave.

7.23.8.11

•

If a specific interface is chosen as Primary, it cannot be selected as Secondary too.

•

If a E1/DS1 is chosen as Primary source, another E1/DS1 coming from the same peripheral cannot be selected as Secondary source and vice-versa.

•

If an MPT ODU radio interface is chosen as Primary source, another MPT radio interface connected to the same MPT Access peripheral cannot be selected as Secondary source and vice-versa.

•

If an MPT ODU or MPT- HL radio interface is chosen as Primary source, another MPT ODU or MPT- HL/HLC radio interface connected to the same peripheral can be selected as Secondary source and vice-versa

•

If an OC-3 (STM-1) is chosen to be Primary source, another OC-3 (STM-1) coming from the same peripheral cannot be selected as Secondary source and vice-versa.

Allowed synchronization sources assignment Only one Master is allowed in the network. If Master: •

The Restoration Mode must be chosen between Revertive and NonRevertive;

•

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.

401



•

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.

•

The Secondary clock source input must be chosen among 1), 2), 3), 4), 5), 6), 7), or 8).

When SSM is enabled on the secondary reference, the user should 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. 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.

7.23.8.12

Synchronization Source with EAS unit

The EAS units perform the clock recovery for each connected MPT. The MPT can be selected as a Primary or Secondary synchronization Source.

7.23.8.13

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.

7.23.8.14

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:

402


7.23.8.15


•

if an Optical Ethernet connection is used, then the optical Ethernet port of MPT must be locked, at transmission, to symbol rate of the Rx signal;

•

if an Electrical Ethernet connection is used, it shall be Synch-E capable, meaning that a common clock at physical layer level, not locked to the NEC, is available between MSS and MPT for a differential clock recovery method based on custom time-stamp protocol (referred to Symbol Rate of the air Rx Signal).

Synchronization source with MPT PFoE Access peripheral MPT Access peripheral performs the clock recovery for each connected MPT-HC/ HC-HQAM/XP/XP-HQAM. One of the MPT-HC/HC-HQAM/XP/XP-HQAMs can be selected to be the Primary synchronization source.

7.23.8.16

Protected radio configuration with one MPT PFoE access peripheral When MPT-HC/HC-HQAM/XP/XP-HQAMs in protected configuration are connected to only one MPT Access peripheral, the MPT Access peripheral selects the MPT-HC/ HC-HQAM/XP/XP-HQAM in EPS active state as the clock signal to be used for synchronization source.

7.23.8.17

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

403


Figure 130


SSM Summary Table

7.23.8.18

Protected radio configuration with 2 MPT PFoE access peripheral When MPT ODUs 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.

7.23.8.19

Synchronization connection in stacking configuration with Core protection In case of Stacking configuration with Core protection the two MPR must be synchronized as shown in Figure 131.

404


Figure 131


Synchronization connection in stacking configuration with Core protection

7.23.9 7.23.9.1

Synchronization with MSS-1c Synchronization overview for MSS-1c TDM data flow is fragmented and the fragments are transmitted over a Packet Switched Network (PSN); The received fragments need to be reassembled in the original TDM data flow at the “original bit rate” Two main methods can be used to recover at the Rx site, the original bit rate:

405



•

Differential clock recovery with or without the node timing: recalculation of the original clock based on the time delta with respect to a reference clock that is available at both Tx and Rx site (Differential: used in case of clock distribution on the whole network. It’s more reliable than Adaptive; also used in TDM2TDM traffic (MPR to MPR)). This method can be selected for each E1 stream.

•

Adaptive clock recovery with or without the node timing: based on the average rate at which the packets (fragments) arrive at Rx site (Adaptive: simpler network, but performances depends on the PDV (Packet Delay Variation) in the Network. Always used when the reference clock isn’t distributed on the whole network). This method can be selected for each E1 stream for TDM2Eth only.

Note: In meshed networks (rings) do not close the synchronization configuration.

7.23.9.1.1


Figure 132 illustrates differential clock recovery. Figure 132


A common reference clock is available at both ends. The IWF system, at Rx side, generates the output clock based on RTP TimeStamps which are sent together with each fragment.

7.23.9.1.2

Adaptive clock recovery Figure 133 illustrates adaptive clock recovery.

406


Figure 133



A common reference clock is not available at both ends. The IWF system, at Rx side, generates the 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.

7.23.9.1.3

Node timing

The Node timing is timing from the network clock as defined in G.8261. When it is selected the regenerated E1 at receiver side is synchronized to the network element clock (NEC). This method can be selected for each E1 stream. At MSS-1c level, all the “Node Timed” TDM flows: •

will egress the MSS-1c with the same clock (the MSS-1c NEC);

•

MUST ingress the MSS-1c being synchronized by the same clock.

As for any synchronisation clock transmission, the user shall particularly take care to avoid synchronisation loop and TDM traffic hits: •

or the MSS-1c is the master clock and the external equipment must recover its own clock from one of the “node timed” TDM flows and use this recovered clock to generate its TDM flows;

•

or the external equipment is the master clock (that is, it generates all its TDM flows by using its internal clock) and the MSS-1c MUST use one of the “node timed” ingressing TDM flows as clock source for its NEC;

•

or both of the MSS-1c and external equipment MUST be synchronized by the same clock if this clock comes from another equipment.

407


7.23.9.1.4


Synchronization for MSS-1c

Each Network Element must have a reference clock (NEC), which will be distributed to each circuit of the NE. Such clock is a 25 MHz generated in the MSS-1c in the Clock Reference Unit (CRU) function. The NEC is locked to a Synchronization Source. The sources can be: •

Internal Local Oscillator. It is the clock provided by the Local Oscillator inside the NE

•

Any E1/T1 available at input traffic interfaces (the specific E1/T1 port has to be chosen)

•

The Symbol Rate of the Rx signal of the Radio direction

•

SynchE: Any Synchronous Ethernet clock source available at enabled User Ethernet traffic interfaces (both electrical and optical), configured in synchronous operation mode (the User Ethernet ports, SynchE compatible, are given in the Alcatel-Lucent 9500 MPR MCT User Manual). From ITU-T G.8264 point of view, the MSS is a Synchronous Ethernet equipment equipped with a system clock (NEC). A User Ethernet interface configured in synchronous operation mode can work only at 1 Giga. In the particular case of electrical User Ethernet interfaces, these interfaces perform link auto negotiation to determine the master and slave clocks for the link. The clock slave role must be configured as part of auto negotiation parameters in order to use the interface as Synchronous Ethernet clock source.

Some rules have to be followed while configuring the Primary and Secondary clock sources. All the NECs have to be configured as Master or Slave.

408



Only one Master is allowed in the network. •

If Master, −

The Restoration Mode can be Revertive or Not Revertive. If the mode is Revertive, when a failed source becomes available, the switch goes back.

−

The Primary sources must be chosen among 1), 2) or 4). •

•

depending on master primary selection, the Master Secondary Source must be selected among 1), 2) or 4).

If Slave, −

The Restoration Mode is fixed to Revertive.

−

The Primary Source must be chosen between 3) or 4)

−

The Secondary Source can be chosen among 1), 2) or 4).

For each available sync source, the CRU detects the signal Degrade Alarm on each available sync source. Such Signal Degrade alarm raises also in case of muted (missing) clock. The Signal Degraded Alarm relevant to the selected Synchronization Source, or the relevant circuit Fail, causes the switching of the Synchronization Source.

7.23.10

IEEE 1588v2 PTP Transparent Clock The IEEE 1588v2 standard synchronizes the frequency and time from a master clock to one or more slave clocks over a packet stream. This packet-based synchronization can be over UDP/IP or Ethernet and can be multicast or unicast. As part of the basic synchronization timing computation, a number of event messages are defined for synchronization messaging between the PTP slave clock and PTP master clock. A one-step or two-step synchronization operation can be used, with the two-step operation requiring a follow-up message after each synchronization message. The current release supports end-to-end transparent clock in one-step mode on specified equipment; see Table 47, Table 48, and Table 49. During startup, the PTP slave clock receives the synchronization messages from the PTP master clock before a network delay calculation is made. Prior to any delay calculation, the delay is assumed to be zero. A drift compensation is activated after a number of synchronization message intervals occur.

409



The basic synchronization timing computation between the PTP slave clock and PTP best master is illustrated in Figure 134. This figure illustrates the offset of the slave clock referenced to the best master signal during startup. Figure 134

PTP Slave Clock and Master Clock Synchronization Timing Computation

Master

Slave 40

38

42

40

44

42

46 48

48

Sync

50 Follow_up (t1)

50

D = Delay t2

52 54

52

56 t3

54 Delay_req 56 t4

58

O

D

t1, t2, t3, t4 are measured values t2 - t1 = Delay + Offset = 51 - 44 = 7 t4 - t3 = Delay - Offset = 57 - 56 = 1 Delay = ((t2-t1) + (t4 - t3))/2 = 4 Offset = ((t2 - t1) - (t4 - t3))/2 = 3

60

58 60

O = Offset = Slave - Master

46

t1 44

62 Delay_resp (t4)

62

64

20503

The system supports the PTP mappings defined in the following: •

IEEE 1588v2 Annex D (PTP to UDP over IPv4)

•

IEEE 1588v2 Annex E (PTP to UDP over IPv6)

•

Annex F (PTP over IEEE 802.3, special Ethertype 0x88F7).

For all the defined mappings all the following Ethernet frames formats are supported: untagged, 802.1Q, 802.1ad. For all mappings over IPv4 and IPv6 UDP port 319 identifies event messages and UDP port 320 identifies general messages. In the case of PTP over Ethernet with a special Ethertype, event and general messages are identified by fields in the PTP. PTP can be enabled at the NE level on any platform. Enabling 1588v2 PTP on the NE enables it on all cards and radios connected to the NE.

410



Hardware that supports PTP updates the Correction Field for 1588 messages with their residence time. Hardware that does not support PTP transports event messages without applying time stamps. Table 47 describes the PTP support on each platform; Table 48 describes the available PTP support on each card; Table 49 describes the available PTP support on each radio.

PTP Clock Type

MSS-1

MSS-1c

MSS-4

MSS-8

MPR-e

IEEE 1588v2 PTP Support per Platform MSS-O

Table 47

Transparent Clock

See Table 48

YES

YES

See Table 48

See Table 48

YES

Table 48

IEEE 1588v2 PTP Support per Card CorEvo

MOD300

MPTACC

P8ETH

EASv2

MSS-O

Transparent Clock

Core-E

PTP Clock Type

Optical ports

All ports

—

All ports

—

All ports 1

All ports 1

Note: 1.

Table 49

1588v2 PTP is supported by MSS-O and EASv2 electrical ports only when the port is operating at 1 Gbit/s. Autonegotiation must be enabled.

IEEE 1588v2 PTP Support per Radio

PTP Clock Type

ODU300

MPT-MC

MPT-HC/ XP

MPT-HCHQAM/ XP-HQAM

MPT-HL

MPT-HLC

MPT-HLS

Transparent Clock

—

Yes

Yes

Yes

—

Yes

Yes

7.23.10.1

Transparent clock at the NE level If 1588 is enabled, the NE updates the Correction Field of 1588 event messages with time stamps when they ingress the NE and when they egress the NE.

411



For the purpose of Transparent Clock at the NE level, the Core card acts as a master timestamp and the other cards in the NE are aligned with it. If Core protection is in use and a protection switch is triggered, the spare Core card aligns the slave clocks and the time stamp is reset. If a Core protection switch occurs between ingress and egress for an event message, there may be an error in the time stamping for that message. If 1588 is enabled and the forwarding path includes a CorEvo, the event message is time stamped by the CorEvo switch regardless of whether the ingress or egress port supports 1588. The 1588 TC can be enabled in a mixed link, for example, a link between an MSS-4 and an MPR-e, or an MSS-1 and an MSS-8.

7.23.10.2

Transparent clock across the radio hop Transparent clock is supported across a radio hop if time alignment has been completed symmetrically on both the local and remote MPT. The time alignment is based on exchange of messages between the local and remote MPTs using transmit and receive paths with constant latency. If the time alignment cannot be guaranteed, a 1588 TC Fail alarm is raised. A 1588 event message, when forwarded from 9500 MPR NE A to 9500 MPR NE B through a radio link, with all ports and MPTs supporting TC, will be updated with three time stamps: the first related to NE A, the second to the radio link and the third to NE B. The MPT can be in a 1+0 or a 1+1 configuration. TC across the hop is supported with both physical and virtual 1+1 coupling. The MPT can be a member of an L1 LAG if the following conditions are met: •

the 1588 TC is supported by an L1 LAG

•

the remote peers of all MPTs in the LAG must support 1588

•

the LAG must be on a card that supports 1588 (EASv2 or MSS-O)

When 1588 TC is enabled with L1 LAG, the MSS sends the TC setting to its connected MPTs only if all of them support 1588 TC. Consequently the MPT will apply time stamps, but only if the MPT on the other side of the hop also supports 1588. If one MPT supports 1588 and the other does not, no time stamps are applied by the MPT.

412


7.24 7.24.1


IP addressing Local NE interface The NE TMN_RF interface (hereafter referred to as the Local NE interface) is an unnumbered Point-to-Point interface. It uses a single IP address as an endpoint identifier. The Local NE interface is always active and cannot be disabled. This Local NE IP address is the same as the Mgmt Port IP address (if enabled) or ETH Port 4 IP address (if enabled) but not both. See TMN communication channels for details. The 9500 MPR supports both IPv4 and IPv6 addressing. Caution: Mixed configuration of IPv4 and IPv6 NEs is not supported.

Note: In an IPv6 environment, the maximum LSA handled by the 9500 MPR is 1 280 bytes.

7.24.2

IPv4 addressing for the local IP address The default IPv4 address is 10.0.1.2. 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.

413


7.24.3


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.

7.24.4

Default IPv6 addresses The IPv6 default addresses are set using the ULA (Unique Local Address FC00::/7) range: NE Local IPv6 address TMN Local Eth IPv6 address TMN Port#4 IPv6 address TMN In-Band IPv6 address TMN In-Band IPv6 address

414

FC00:0:0:1::1/128 FC00:0:0:1::1/64 FC00:0:0:2::1/64 FC00:0:0:3::1/64 FC00:0:0:4::1/64


7.24.5


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 FC00:0:0:1::1/128. The prefix length is not configurable and is fixed to 128. 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.

415


7.24.6


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

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.

416



NDP is used to perform IPv6 Stateless Address Autoconfiguration to assign an IPv6 Global Unicast address to the host connected to TMN Local Ethernet.

7.24.7 7.24.7.1

MPR-e standalone IP addresses NE IP addresses The NE IP address is a network IP address used to access the MPR-e through the radio and traffic Ethernet traffic port. This address is configured statically by the operator through the management system. The default IPv4 address is 10.0.1.2. The subnet mask is 255.255.255.255 (/32). This mask is fixed and not configurable by the operator.

7.24.7.2

TMN communication channels On 9500 MPR Network Element the following types of TMN communication channels are present:

7.24.7.3

•

In-band TMN through the use of any USER port requiring the activation of a user defined VLAN

•

TMN-RF allowing the management of a remote NE through radio.

•

MSS-1c only: 2 NMS interfaces through the use of VLANs 4085 and 4086 and 2 dedicated RJ45 ports.

TMN-RF The TMN-RF interface is associated with the radio port and is used to connect the MPR-e to the NE on the other side of the radio link. There are two different selectable modes for this interface: PPP or In-Band.

417



When an MPR-e is interfacing with any NE belonging to the MPR family at the other end of a radio link, TMN-RF PPP is required. TMN-RF PPP doesn’t have an explicit IP address configuration because it automatically inherits the NE IP address. When the NE at the other end is a 7705 SAR in Single NE with MPR-e, TMN-RF InBand is required. As TMN In-Band, this interface requires a unique IP address, a subnet mask and a unique VLAN ID (it cannot be the same as the TMN In-Band VLAN ID). The 7705 SAR must have a similar valid interface within the same subnet with the same VLAN ID as the MPR-e to establish IP connectivity over the radio link.

7.24.7.4

TMN In-Band The TMN In-Band interface dedicated to TMN is used to connect the MPR-e NE to the LAN exchanging TMN information through a VLAN mixed with the user Ethernet traffic. This interface has a local default IP address, and the operator can reconfigure this IP address as a public address. The IP address of the TMN In-Band interface can be equal to the local IP address (NE IP address). If the IP address is different from the NE IP address, the TMN In-Band subnet is different from the NE logical subnet calculated by masking the NE IP address with the TMN In-Band subnet mask. The default address is 192.168.100.1. The default subnet mask is 255.255.255.0 (/24). The default TMN In-Band VLAN ID is 4080.

7.25

Mgmt port interface The Mgmt Port is provisioned independently from the Local NE interface, and unlike the Local NE interface, the Mgmt Port can be disabled if not needed. See the Core-E or CorEvo provisioning for details. When addressing the Mgmt Port interface, you may follow CIDR guidelines and use Variable Length Subnet Masks (VLSM) as defined in RFC-1519 and in RFC-1878. The longest usable netmask for the Mgmt Port interface is 30 bits (Netmask 255.255.255.252).

418



If the Mgmt Port interface is enabled, it is recommended that it be assigned the same IP address as the Local NE interface. This allows the radio to be known throughout the network by only one IP address, and eliminates a potential problem of one radio appearing to be two different pieces of equipment to an SNMP manager. It should be noted that the factory default IP address assigned to the Local NE and Mgmt Port is 10.0.1.1. Use of this IP address within the radio network should be avoided, since installing a new 9500 MPR could possibly cause a disruption of the network if that address is already in use.

7.25.1

ETH port 4 interface A backup for the Mgmt Port is provided by enabling Ethernet Port 4 to transport TMN data. The ETH Port 4 interface is provisioned independently from the Local NE interface and Mgmt Port interface, and can be disabled if not needed. See the Core-E or CorEvo provisioning for details. ETH Port 4 and Mgmt Port IP addresses must be different. If the ETH Port 4 interface is enabled, and the Mgmt Port interface is disabled, it is recommended that it be assigned the same IP address as the Local NE interface.

7.25.2

Typical interconnect/addressing method

See Figure 135 and Figure 136 for a typical interconnect and addressing method, using the Local NE interface to connect sites and Mgmt Port interface to connect radios at each site. IPv4 addressing is used.

419


Figure 135

420

Typical interconnect/addressing method



Figure 136


Typical interconnect/addressing method details continued

Note the various subnet masks used. The use of VLSM allows subnets to be sized as appropriate for the amount of external equipment to be deployed. This helps minimize the number of unused or unusable addresses.

7.25.3

Network provisioning See the following example of Network provisioning and description of the provisioning screens.

7.25.4

Addressing examples Addressing depends on the type of backhaul required; that is, external or radio WAN. •

For external backhaul, address the Local NE and Mgmt Port as a member device of the external LAN with a single address.

421



•

7.25.5

7.25.6

IF the Radio is providing backhaul for IP traffic, the recommended addressing scheme is to assign a small subnet to each radio. The radio and Mgmt Port can share one IP address from the subnet and the remaining address(es) of the subnet can then be used to address additional local equipment. The local equipment can then use the radio as the default gateway for IP transport. To assign radio subnets, follow the general procedures shown in Radio Level Subnet Addressing.

Assumptions •

OSPF will be enabled within the radio network.

•

The recommended configuration is such that the Ethernet port will have the same IP address as the radio.

•

Radios that attach directly to external networks (Corporate LAN/WAN) should be addressed as members of the subnet to which they attach.

IP address assignments Since the size of the Static Routing table is limited, IP Address assignment should strive to minimize the size of the Static Routing table.

7.25.7

•

In general, IP addresses should increase (or decrease) as distance increases away from terminals or junction. This allows the use of route aggregation when specifying static routes.

•

The static routing table size is inversely related to IP address efficiency. Although there is less effect when used with OSPF, a side effect of minimizing the static routing table size can leave more unused/unusable addresses.

Radio level subnet addressing Assign Radio Level Subnets as follows: 1. Radios connected by RF, or PPP links must each get their own subnet. 2. Radios connected by Ethernet need to share a subnet. Each radio will use one address from the Ethernet subnet. 3. Determine the radio and external equipment configuration at each site/radio.

422



4. Size the Ethernet subnet based on the number of devices that will be attached, both known and anticipated. 5. Determine the number of required addresses at each radio, and round this number up to the next highest usable hosts number; see Table 1. From the usable hosts number, select the size of the radio subnet. The minimum amount of address space to assign to a radio subnet is 4 addresses (2 usable host addresses). Table 50

Commonly used subnet masks and associated subnet sizes

ETHERNET SUBNET MASK

MASK BITS

HOST BITS

TOTAL NUMBER OF ADDRESSES IN RANGE

USABLE HOST ADDRESSES 1

255.255.255.254

31

1

2

0 (unusable)

255.255.255.252

30

2

4

2

255.255.255.248

29

3

8

6

255.255.255.240

28

4

16

14

255.255.255.224

27

5

32

30

255.255.255.192

26

6

64

62

255.255.255.128

25

7

128

126

255.255.255.0

24

8

256

254

1. The first and last addresses of a subnet are reserved for the network number and broadcast address respectively. This makes the number of usable host addresses two less than the total number of addresses in the subnet.

7.25.8

Example: A radio has a single SNMP device attached via the Ethernet. Planned future expansion will add two more SNMP devices for a total of four devices. From Table 50, the nearest usable subnet size provides for a total of 6 usable addresses. This correlates to a required radio subnet size of 8, and an Ethernet Subnet mask of 29 bits (255.255.255.248). Of the 6 usable addresses, one is for the radio, three are for the SNMP devices, and the remaining two unassigned addresses are for future expansion. See Figure 137 and Figure 139 for examples.

423


Figure 137


Typical terminal addressing

7.25.9

Larger subnet areas 1. Group radio subnets into larger subnet areas. Larger subnet areas normally consist of: −

All radios from a Terminal to a Junction.

−

All radios between two Junctions.

2. Start at one end of a group and begin assigning addresses to each radio subnet in sequential order.

7.25.10

Future expansion

Reserve addresses and design routing tables to allow for the following: 1. Future expansion/extension of Backbone. 2. Future addition of local TCP/IP equipment at each site. 3. Future Spurs or Spur extensions to be assigned addresses in the same subnet. It is possible to disable the Ethernet interface of the TMN card, assign only one IP address to the radio, and still use the radio WAN for IP transport. This method is discouraged because it leaves no IP addresses available within the radio WAN for expansion or addition of new Ethernet equipment at radio sites.

424



Caution: Obtaining additional address space in the future may require readdressing of the entire network. Readdressing of a radio network requires a site visit for each radio affected and, until the process is complete, radio WAN communications (SNMP management and WAN IP transport) could possibly be unavailable.

7.25.11

Addressing terminals

(See Figure Figure 137 and Figure Figure 138)

7.25.12

External LAN attached

For terminals attached to external LAN see Figure 138. When attached to external LAN, proceed as follows:

1. Address both the WAN and LAN interfaces of the radio as a member device in the external LAN and enable OSPF. 2. Interfacing to external routers a. If external routers use OSPF, the radio network can be integrated with the external OSPF design. b. If the external routers do not support dynamic routing, or if it is desired to keep the radio network dynamic routing separated from the external network, set a static route in the radio to point to the default gateway in the external LAN. Configure the external router to use the radio as a gateway to the radio network.

7.25.13

External LAN not attached For terminals not attached to external LAN, proceed as follows:

1. Assign an IP Subnet to the Radio and enable OSPF, otherwise set the default route in the radio to point to the “RF” interface. 2. Set the default route in all local Ethernet equipment to point to the Radio.

425


Figure 138


Typical terminal attached to external LAN

7.26

7.26.1

Addressing back-to-back terminals, Other asynchronous radios, and repeaters Preferred addressing method See Figure 139.

1. Assign one subnet for the site, address radios as members of that subnet and enable OSPF. 2. Interconnect the radios using Ethernet (Avoid loops or other problematic connections).

426



3. Provision the default gateway of any locally attached Ethernet equipment to point to a radio.

7.26.2

Alternate addressing method See Figure 139.

1. Assign a separate subnet to each radio. 2. Assign each radio an address from its Ethernet subnet. 1. Local Ethernet Equipment a. Address as part of the radio subnet to which the equipment connects. b. Set the default gateway to point to the radio to which the equipment is attached. Figure 139

Back-to-back terminal and repeater configuration addressing

427


7.27


Network provisioning Note: The following example shows IPv4. The network provisioning process is the same for IPv6.

Figure 140

Back-to-back terminal and repeater configuration addressing Site 1

Corporate Intranet

External router B

Site 2 A

Site 3

A

NE-1 172.22.46.115

A

NE-2 172.22.47.73 B

NE-3 172.22.47.74

A

NE-4 172.22.46.81

B

External Switch Net: 172.22.47.72 Mask: 255.255.255.248

A = NE TMN_RF Port

Net: 172.22.47.80 Mask: 255.255.255.248

B = Mgmt (NMS) Port TMN Network address B set the same as the Local Address A , OSPF enabled. Static route in MSS-1 with default gateway as External router. External router configured to use MSS-1 as gateway for 172.22.47.64/255.255.255.192 network. 23178

7.27.1

Network provisioning example •

Site 1 −

•

•

Site 2 −

NE-2: See Figure 147 through Figure 151

−


Site 3 −

428




7.27.1.1 Figure 141


NE-1

NE-1: NEtO logon window

429


Figure 142

NE-1: Ethernet interface provisioning

Figure 143

NE-1: Local configuration window

430



Figure 144


NE-1: IP static routing configuration window

431


Figure 145

432

NE-1: OSPF area configuration



Figure 146

NE-1: IP routing configuration window

7.27.1.2 Figure 147


NE-2


433


Figure 148

NE-2: TMN Ethernet interface window

Figure 149

NE-2: local configuration window

434



Figure 150



435


Figure 151

NE-2: IP routing information window

7.27.1.3 Figure 152

436


NE-3



Figure 153

NE-3: TMN Ethernet interface provisioning

Figure 154



437


Figure 155

438




Figure 156


7.27.1.4 Figure 157


NE-4


439


Figure 158

NE-4: TMN Ethernet interface provisioning

Figure 159


440



Figure 160


NE-4: IP static routing configuration window

441


Figure 161

442




Figure 162



7.28

TMN communication channels TMN traffic is assigned to QoS queue 6 which is a higher priority than Ethernet traffic queues, but lower than MEF8 (TDM2TDM and TDM2ETH) traffic queues. TMN bandwidth is not reserved, which allows user traffic, up to the maximum capacity of the radio link when the TMN port is idle. TMN traffic must be considered when configuring CIR flows. When deploying external devices using the TMN channel, care must be taken to avoid using more bandwidth than is available on the radio link. It is recommended to use a user Ethernet port to attach remote devices for monitoring instead of the TMN port. See the different NE TMN_RF Port scenarios. TMN routing in the 9500 MPR consists of a 3-port router and associated circuits in the Core card plus CT screens for configuring automatic (OSPF) and manual (static) routing.

443


7.28.1

7.28.2

444


Port functions •

NE TMN_RF Port (Local NE) - TMN channel carried by Ethernet frames in the dedicated TMN port (on the front panel of the Core card) (this port is normally used to connect the LCT)

•

Mgmt Port - Primary function TMN data channel, up to 512 kbit/s channel inside Radio frame. Secondary function- CT access

•

Eth Port 4 - Primary function- provisioned Ethernet and transport Ethernet traffic. Secondary function - TMN channel carried by Ethernet frames in Ethernet tributary 4 (on the front panel of the Core card)

•

Two TMN In-band interfaces (by using the Ethernet traffic ports)

NE TMN_RF port scenarios •

NE TMN_RF Port Belongs to Subnet 2

•

NE TMN_RF Port Belongs to Subnet 1

•

NE TMN_RF Port Belongs to Separate Subnet 3


Figure 163


NE TMN_RF port belongs to subnet 2

445


Figure 164

446

NE TMN_RF port belongs to subnet 1



Figure 165


NE TMN_RF port belongs to separate subnet 3

7.28.2.1

Open shortest path first (OSPF) •

OSPF is the preferred method for routing within the radio WANs.

•

The 9500 MPR uses a simplified OSPF implementation. If the NE is configured in IPv6 mode, OSPFv3 is used.

•

Configuration requires only an Area ID and Mask.

•

Supports redundant WAN paths, allowing linear, tree, ring, mesh and other WAN topologies. If redundant paths are available, OSPF can reconfigure routes to work around a failed link.

•

Dynamically assigns a routing metric to redundant paths based on route cost, where the route cost is determined by the speed of the interface used and the hop count to a destination.

•

Does not perform route aggregation.

•

Supports a maximum of 250 routes within a single OSPF area.

447


7.28.2.2


Static routing •

−

use for reaching external networks when the external network does not use a supported dynamic routing protocol.

−

control the exchange of dynamic route information between the radio WAN and the external network.

•

Static routing only supports provisioning a single route to a given destination at any radio. Route metrics and redundant routes are not supported. This limits the useful WAN topologies to linear and tree configurations when using Static Routing.

•

Maximum of 25 static route entries per radio.

•

7.29

Usually used at radio WAN border routers to specify a default gateway to:

−

To minimize the number of static route entries required, the radio network addressing plan should allow for maximum route aggregation.

−

Static routes directed out the PPP interfaces use the interface name as the route destination; rf, rptr, or (front) ppp.

A TMN interface cannot be disabled when it is in use as the outgoing interface of a Static Route.

Protection schemes

7.29.1

Protection schemes with MPT-HL/MPT-HLC/MPTHLS Note: If an RF loopback is active on an MPT-HLC/MPT-HLS, you need to deactivate it before configuring protection.

Supported Protection types: •

RPS (Radio Protection Switching) Hitless for each radio direction (RPS-RX) −

•

EPS (Equipment Protection Switching) for both transmit and receive signals −

448

RPS is distributed in Transceivers before termination to the Transceiver radio frame circuitry. Tx direction: Both Working and Spare Transceiver send their own signal to the mate Transceiver. The Core selects either the main or spare signal.



− •

HSB-TPS (Hot StandBy - Transmission Protection Switch) −

•

Rx direction: The Core selects either the main or spare signal after Transceiver radio frame circuitry. The other signal is squelched. The Core selects either the main or spare signal. The other signal is squelched.

HSB-TDA (Hot StandBy - Transmit Diversity Antenna) for MPT-HLC only −

The TX Diversity Antenna configuration allows the MPT-HLC transmitters in a 1+1 HSB radio configuration to broadcast on either the main or diversity antenna of a space diversity receiver configuration. This protection type requires a dual relay; see Figure 166.

Figure 166

Transmit Diversity Antenna

Hot Standby W/Transmit Diversity Antenna Tx Eth Access

MPT-HLC Transceiver Main

RF Switch RF Diplexer

Rx

Tx Eth Access

MPT-HLC Transceiver Standby

RF Diplexer

Rx 25378

Note: The TDA Feature is operational only if the radio has been equipped with the dual relay switch assembly, and is correctly connected to a diversity antenna.

449


Figure 167


MPT-HL protection scheme block diagram

7.29.1.1

RPS switching criteria The switching criteria are:

450

•

SF (Signal Fail): generated from transmission and equipment alarms affecting the Rx radio section:

•

Demodulation Fail

•

MPT-HL link failure

•


•

Main and spare IDU HW failures (card fail)

•

HBER (high BER)

•

EW (Early Warning)


7.29.1.2


EPS switching criteria

The switching criteria are:

7.29.1.3

•

MPT-HL/MPT-HLC/MPT-HLS Transceiver Fail (switching off of the peripheral included)

•

MPT-HL/MPT-HLC/MPT-HLS Transceiver Missing

•

LOS of all the tributaries (of course only in case of PDH local access peripheral protection) managed via SW.

HSB switching criteria


7.29.1.4

•

MPT-HL/MPT-HLC/MPT-HLS Transceiver Fail (switching off of the peripheral included)

•

MPT-HL/MPT-HLC/MPT-HLS Transceiver Missing

•

IDU TX chain alarm (this is an OR of the following alarms: LOS at IF input, modfail, txFail, IDU card fail).

•

Incompatible Shifter alarm

•

Incompatible Frequency alarm

•

Incompatible Power alarm

•

Incompatible Modulation Parameters alarm

•

Common Loss Alarm

TDA switching criteria Antenna switching is controlled by the main MPT. The process is triggered when an RX status message is received reporting that there is no valid remote receiver that can lock on the transmitter signal. A remote receiver is considered not valid if RSL is 0 or less than -99 dBm (that is, reporting a special code) or an equipment alarm is active. The switching criteria are: •

HBER alarm on the remote receiver

•

Demodulation Failure alarm on the remote receiver

451



•

7.29.2

RSL information on the remote receiver indicating transmission failure

Protection schemes with MPT ODU

The MPT-MC, 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. Starting from R 3.3, the RPS protection without cable function is available. Therefore the RPS module and RPS optical cable between two mate MPTs 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 the 9500 MPR WebEML User Manual. 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 168 Ethernet port 2 of one MPT ODU is connected to Ethernet port 2 of the second MPT ODU. Note: In Figure 168 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 unit, or to different P8ETH or EASv2 units.

The MPT ODUs can be connected to MPT Access, Core, or EAS units. Both MPTs in a protected configuration must use the same type of port (optical or electrical). Port 2 can protect port 1, port 4 can protect port 3, and port 6 can protect port 5. The optical RPS cable between the MPTs is mandatory in the following cases:

452

•

In case of 2 x (1+1 HSB) XPIC split-mount configuration

•

In case of 2 x (1+1 SD) XPIC split-mount configuration

•

In case of 2+0 XPIC full-outdoor configuration (MPR-e)


•


In case of mixed traffic E1/DS1 and Ethernet for MPT-MC/HC/XP: if jumbo frames (≥ 5000 bytes) are transported with mixed TDM traffic, the maximum number of TDM2TDMs that can be cross-connected in a given radio direction in 1+1 configuration without RPS module and tight cable is limited: −

111 DS1 in 40 MHz / 256QAM and 86 DS1 in 50 MHz / 256QAM and 81 DS1 in 60 MHz/256QAM for jumbo frame = 5000 bytes

−

109 E1 in 40 MHz / 256QAM and 81 E1 in 56 MHz / 256QAM for jumbo frame = 5000 bytes

−

For MPT-HC-HQAM / MPT-XP-HQAM: for 40, 50, 56 & 60MHz channel spacings, RPS protection without cable is not possible, the RPS cable must be used and consequently there is no effect on the maximum number of the supported E1/DS1

−

For MPT-MC, the only possible working mode is without the tight cable between the two mate MPTs: the previous limit applies to MPT-MC as well.

If no jumbo frames are transported or if the number of TDM flows is lower than the maximum, the suggested configuration is without RPS module and tight cable. In case of Packet Throughput Booster, in 1+1 configuration, the maximum throughput that can be transmitted without RPS module is 440Mb/s (applicable to MPT-MC, HC, XP, HQAM). Consequently the use of the RPS module and tight cable is recommended in 1+1 configuration for channel spacing equal or above 50 MHz. For smaller channels, assuming 30% gain using PTB, the module / tight cable might not be normally used but check your traffic. For MPT-MC, the only available working mode is without the tight cable between the two mate MPTs: the previous limit applies to MPT-MC. No limit is present in case of full Ethernet traffic.

7.29.2.1

Supported protection types: •

•

RPS (Radio Protection Switching) Hitless for each radio direction −

RPS can be implemented with or without the external module and interconnection cable between the two MPT ODUs.

−

When no external module and interconnection cable is used, the 1+1 RPS messages are exchanged in the MSS-4/MSS-8 shelf.

−

When the external modules and interconnection cable is used, the 1+1 RPS messages are exchanged between the MPT ODUs.

EPS (Equipment Protection Switching) for the MPT ODU

453



− •

HSB-TPS (Hot StandBy - Transmission Protection Switch) −

Figure 168

454

EPS protects the MPT ODU and the cables connecting it to the MSS. Spare ODU module is squelched.

MPT ODU protection schemes


7.29.2.2


RPS switching criteria The switching criteria are: •

SF (Signal Fail): generated from transmission and equipment alarms affecting the Rx radio section

•

Rx Fail

•

Demodulation Fail

•


•

inter-MPT coupling link failure

•

HBER (high BER) based on the demodulated erroneous blocks ratio

•

EW (Early Warning) based on MSE

Moreover, MPT ODU 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 (for example, due to the frame alignment error). The Enhanced RPS switching criterion depends on the presence of errors in the decoded LDPC word.

7.29.2.3

EPS switching criteria

The switching criteria are: •

Card Fail

•

Card Missing

•

IDU-ODU Connection Failure

•

ICP alarm

•

LOS of all the tributaries (of course only in case of PDH local access peripheral protection) managed via SW.

•

Mated MPT Access card Failure

455


7.29.2.4


HSB switching criteria


7.29.3

•

MPT ODU Access Card Fail status

•

IDU-ODU Connection Failure

•

ICP alarm

•

Incompatible Shifter alarm

•

Incompatible Frequency alarm

•

Incompatible Power alarm

•

Incompatible Modulation Parameters alarm

•

Mated MPT ODU Access card Failure

•

Inter-MPT ODU 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-MPR coupling link failure.

Core 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. The two Core units must be the same variant: Core-E, CorEvo-10G, or CorEvo-1G. Mixed configuration is not supported. 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. If an optical splitter is used in Core protection configuration autonegotations 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.

456



Note: Core protection is not supported when an MPT is connected to the main Core unit.

7.29.3.1

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.

7.29.3.2

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 effect 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. Note: When the Core unit is protected, it is suggested to protect the Ethernet data ports also to avoid losing 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 Fixed LAG.

7.29.3.3

External synchronization interface protection The Protection of the external synchronization interface is supported. The output port on the stand-by Core is muted.

457


7.29.3.4


Node-timed PDH interface protection

In case of node-timed PDH interface the protection of the NE Clock provided by Core is supported.

7.29.3.5

Core protection restoration mode The restoration mode is configurable to either Revertive or Non Revertive. In Revertive mode, after the conditions causing EPS to switch to Core Spare has cleared, the EPS is restored to Core Main. In Non-revertive mode, after the conditions causing EPS to switch to Core Spare has cleared, the EPS is kept on Core Spare. The default configuration of restoration mode is Non-revertive.

7.29.3.6

Core protection switching criteria

The 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. If the “Ethernet LOS Criteria” feature has been enabled the following additional switching criteria are added:

458

•

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.

7.30

Automatic link discovery Automatic link discovery allows 9500 MPR equipment (MSS, MPR-e, MSS-1c) to discover and store information about its neighbors. This information is then used by network managers such as 5620 SAM to automatically learn the network topology. The radio link discovery is performed via an Alcatel-Lucent proprietary Discovery Protocol. In addition the MPR-e supports automatic link discovery over Ethernet using LLDP.

7.30.1

LLDP overview LLDP is a neighbor discovery protocol that defines a method for Ethernet network devices to advertise information about themselves, such as device configuration, capabilities and identification, to directly connect LLDP-enabled devices on the same physical LAN and store the information received from other stations in IEEE-defined Management Information Bases (MIB) modules. LLDP is a data-link layer protocol operating above the MAC service layer and, as a result, can be used in any networking device that implements a MAC service. Using LLDP over the User Ethernet interfaces, an MPT in MPR-e topology is able to advertise its own identification information its capabilities and media-specific configuration information and learn the same information from the LLDP-Enabled devices connected to it. The IEEE 802.1ab Link Layer Discovery Protocol defines a standard way for Ethernet devices to advertise information about themselves to their network neighbors and store information they discover from other device. Figure 169 shows the discovery process.

459


Figure 169


LLDP

Legend: 1. The MPT and the LLDP enabled device advertise their chassis/port IDs and system descriptions along with other information to each other. 2. The devices store the information they learn about each other in local MIB/ databases accessible via SNMP. 3. Network management systems discover the network topology by crawling the NEs and querying the MIB on each device.

7.30.2

LLDP on MPR-e

By default the LLDP functionality is disabled on the Ethernet user interface. The activation and deactivation of the feature can be done using SNMP or MCT.

7.30.3

Transmitting nearest bridge LLDPDUs The MPR-e originates untagged Nearest Bridge LLDPDUs advertising management information about itself on its LLDP-enabled Ethernet interface. The MPR-e includes all the optional TLVs in the outgoing Nearest Bridge LLDPDUs:

460

•

portDesc

•

sysName

•

sysDesc

•

sysCap


•


Management Address TLV

This is not configurable. The MPR-e does not originate Nearest non-TPMR and Nearest Customer Bridge LLDPDUs.

7.30.3.1

Default parameter The LLDP timers are configured with the default values below and can't be modified. The following are the default values: •

lldpV2MessageTxInternal = 30 (msgTxInterval)

•

lldpV2MessageTxHoldMultiplier = 30 (msgTxHold)

•

lldpV2ReinitDelay = 2 (reinitDelay)

•

lldpV2NotificationInterval = 30

•

lldpV2TxCreditMax = 5 (txCreditMax)

•

lldpv2MessageFastTx = 1 (msgFastTx)

•

lldpV2TxFastInit = 4 (txFastInit)

The LLDP agent is configured to advertise the NE's public IP address as the local management address. The operator cannot modify this configuration. If LLDP is activated on the User Ethernet interface, it is enabled for transmission and reception LLDPDUs (Transmit only and Receive only modes are not supported).

7.30.3.2

SNMP MIB management

These default values are instantiated, with the appropriate scalar object, in the LLDPV2 MIB so that a Network Management System (NMS) could query them.

7.30.4

Receiving nearest bridge LLDPDUs The MPR-e terminates the Nearest Bridge LLDPDUs (untagged and tagged). If the received PDU is identified as a Nearest bridge, then the MPR-e uses the PDU’s content to update its LLDP remote system MIB.

461


7.30.4.1


Supported TLVs Any other optional TLV different from Port Description TLV, System Name TLV, System Description TLV, System Capabilities TLV and Management Address TLV of the received PDU is not managed. Management Address TLVs containing a Management Address Subtype other than IPv4 (IPV6 is not supported on MPR-e) is not managed and if such a subtype is detected the corresponding entry in the lldpV2RemManAddr SNMP table will not be created. A non-MPR neighbor may announce several management addresses in its LLDP PDU, even a mix of IPV4 and IPV6 addresses. The MPR-e can store multiple IPV4 addresses; the remaining IPV6 addresses are discarded.

7.30.4.2

MIB update scenarios

If the neighbor is unknown, that is, no entry exists in the remote systems MIB for that neighbor, the MPR-e creates it. If the neighbor is known, the MPR-e uses the new information contained in the LLDPDU to replace the existing entry in the MIB. If there are information elements in the existing MIB entry for which there are corresponding elements in the received LLDPDU, then those elements are updated using the received information. Any other information elements in the existing MIB entry are deleted.

7.30.4.3

Notifying the SNMP manager When detecting a new neighbor or a neighbor modification, the MPR-e: 1. Sends optics IM (object deletion and object creation) traps to the SNMP manager to notify of the destruction or creation of the LLDP MIB entries and stores these events in its event log. 2. Sends an lldpV2RemTablesChange notification to the manager indicating that something has changed in the LLDP remote systems MIB associated with that neighbor.

462


7.30.4.4


Number of supported neighbors at a time The maximum number of neighbors supported at a time is one. When a neighbor already exists and a new neighbor is discovered, the information related to the old neighbor is removed from the MPR-e database and the new neighbor takes its place. The management of the Too Many Neighbors condition described in 9.2.7.7.5 of 802.1AB-2009 applies.

7.30.5

Transparent relay of nearest non-TPMR bridge and Nearest customer bridge PDUs Whether its LLDP configuration is enabled or disabled, the MPR-e processes incoming Nearest non-TPMR bridge and Nearest Customer bridge LLDPDUs as data traffic and relays them transparently.

7.30.5.1

Automatic link discovery scenarios

Figure 170 provides an example where Alcatel-Lucent’s radio Discovery Protocol and Ethernet user interface LLDP can be used. Figure 170

Radio discovery protocol and Ethernet user interface LLDP

7.30.5.2

Displaying Neighbors in the user interface The NE’s radio and Ethernet interface neighbors are visible in the user interface.

463


464



Cables

8 Cables This chapter describes cabling options for MPT ODUs, including requirements for cable lengths. For cable part numbers, see Cables unit data sheet.

8.1 8.1.1

MSS to Outdoor Unit interconnections How to connect the MPT-HC/HC-HQAM to the station battery Figure 171 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:

Figure 171

•

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)

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

465

Release 7.0.0 3DB 19383 ACAA Issue 01 Cables


8.1.2

MSS-4/8 to MPT-HC/HC-HQAM interconnection The MPT-HC/HC-HQAM can be connected in the following ways: •

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)

•

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 (CorEvo unit to MPT-HC/HC-HQAM)

•

One cable, Data+DC (CorEvo 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)

See the Cable length section for cable length information.

8.1.2.1

One cable, Data+DC (MPT Access unit to MPT-HC/HCHQAM) One electrical Ethernet cable connects an MPT Access unit in the MSS to its MPTHC/HC-HQAM (the MPT Access unit provides the PFoE). The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool (1AD160490001).

Figure 172

MPTACC to MPT-HC/HC-HQAM interconnection

Ethernet CAT5e Bat A

Mgmt Port

9500 MPR

+

Bat A

Major

Bat B

Minor

External Alarms DC VOLTAGE

DC VOLTAGE

+ FAN ALARM

Bat B

25485

466


8.1.2.2

Cables

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

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

One cable is a coaxial or Cat5E cable to send the power supply to the MPTHC/HC-HQAM: −

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

− •

50 ohm coaxial cable

The second cable is an Ethernet optical cable. The Ethernet optical cable is preassembled and available in different lengths.

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

Figure 173

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

N-to-Ethernet pair pigtail RJ45 + R2CT Fiber

Coaxial cable

Bat A

Mgmt Port

9500 MPR

+

Bat A

Major

Bat B

Minor


DC VOLTAGE

+ FAN ALARM

Bat B

25486

8.1.2.3

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

Two cables connect the MPT:

467



•

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:

Figure 174

•

Station battery, as shown in Figure 174

•

MPT Power Unit

•


•

Power Injector Box/Power Injector Card

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


Coaxial cable Lightning arrestor + Low pass filter + Pigtail N-to-2 wires Bat A

Mgmt Port

9500 MPR

+

Bat A

Major

Bat B

Minor

To the battery (Note)


DC VOLTAGE

+ FAN ALARM

Bat B

25487

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 see How to connect the MPT-HC/HC-HQAM to the station battery.

468


8.1.2.4

Cables

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. Figure 175 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 176 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.

Figure 175

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

CAT5e 9500 MPR POWER INJECTOR

MPT 1

MPT 2 DC Voltage

DATA DC Voltage

-48 VDC

DC+DATA

DC Voltage

DATA

DC+DATA

Power Injector Box

-48 VDC

To the battery Bat A

Mgmt Port

9500 MPR

+

Bat A

Major

Bat B

Minor


DC VOLTAGE

+ FAN ALARM

Bat B

25488

469


Figure 176


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

CAT5e

Bat A

Mgmt Port

9500 MPR

DC VOLTAGE

POWER INJECTOR

DC VOLTAGE

MPT 1

DC + DATA

DATA -48V

MPT2

DC + DATA

DATA

DC

-48V

+

Bat A

Major

Bat B

Minor

DC


DC VOLTAGE

+ FAN ALARM

Bat B

25489

8.1.2.5

Two cables, Data and DC (CorEvo unit to MPT-HC/HCHQAM)

Two cables connect the MPT: •

one optical cable connected to port#7 or port #8 of the CorEvo unit or one electrical cable connected to the electrical ports (port#1 to port#4) of the CorEvo unit.

•



470

•


•

MPT Power Unit

•


•



Figure 177

Cables

CorEvo to MPT-HC/HC-HQAM interconnection (2 cables)

N-to-Ethernet pair pigtail + RJ45 + R2CT Coaxial cable lighting arrestor + low pass filter +pigtail N to 2 wires


Fiber CSMv2

Bat A

Mgmt Port

R

S

9500 MPR 1

2

3

4

5

6

7

8

DC VOLTAGE

POWER INJECTOR

DC VOLTAGE

MPT 1

DC + DATA

DATA

10G

-

A

-48V

DC

MPT2

DC + DATA

DATA -48V

+ Bat A

Major

Bat B

Minor

DC

External Alarms

+ FAN ALARM

Bat B

24968



471



8.1.2.6

One cable, Data+DC (CorEvo unit to MPT-HC/HC-HQAM) The CorEvo 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. Figure 178 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 179 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.

Figure 178

CorEvo connection to the MPT-HC/HC-HQAM through the Power Injector Box

Power Injector box CAT5e 9500 MPR POWER INJECTOR

MPT 1

MPT 2 DC Voltage

DATA

DC+DATA

DC Voltage

DATA

DC+DATA

DC Voltage

-48 VDC

-48 VDC

To the battery CSMv2

Bat A

Mgmt Port

R

S

9500 MPR 1

2

3

4

5

6

7

8

DC VOLTAGE

POWER INJECTOR

DC VOLTAGE

MPT 1

DC + DATA

DATA

10G

-

A

-48V

DC

MPT2

DC + DATA

DATA -48V

+ Bat A

Major

Bat B

Minor

DC

External Alarms

+ FAN ALARM

Bat B

24964

472


Figure 179

Cables

CorEvo connection to the MPT-HC/HC-HQAM through the Power Injector card

CAT5e

CSMv2

Bat A

Mgmt Port

R

S

9500 MPR 1

2

3

4

5

6

7

8

-

A DC VOLTAGE

POWER INJECTOR

DC VOLTAGE

MPT 1

DC + DATA

DATA -48V

10G

DC

MPT2

DC + DATA

DATA -48V

+ Bat A

Major

Bat B

Minor

DC

External Alarms

+ FAN ALARM

Bat B

24965

8.1.2.7

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


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

•


Power can be supplied by the following: •

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

•

MPT Power Unit

•


•


473


Figure 180


EAS to MPT-HC/HC-HQAM interconnection


Coaxial cable Lightning arrestor + Low pass filter + Pigtail N-to-2 wires Bat A

Mgmt Port

9500 MPR

+

Bat A

Major

Bat B

Minor



DC VOLTAGE

+ FAN ALARM

Bat B

25484



474


8.1.2.8

Cables

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 Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool (1AD160490001).

Figure 181

EASv2 to MPT-HC/HC-HQAM interconnection


Mgmt Port

9500 MPR

+

Bat A

Major

Bat B

Minor


DC VOLTAGE

+ FAN ALARM

Bat B

25485

475



8.1.2.9

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


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

•



Figure 182

•

Station battery

•

MPT Power Unit, as shown in Figure 182

•


•


•

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

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


Coaxial cable 9500 MPR

MPT Power Unit

MPT1

MPT2

MPT3

MPT4

MPT Alarms

1 2

3 4

A B

Battery VDC Normal -48V VDC Range -57.6V to -38.4V

DC Voltage

Battery A

+

DC Voltage

VDC

Battery B

-

+

VDC

-

Bat A

9500 MPR

+

2

S

Bat A

Major

Bat B

Minor

External Alarms

-

1

+ FAN ALARM

Bat B

25477


The recommended value is 3 Amps.

476


Cables

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

8.1.3

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 (CorEvo unit to MPT-XP/XP-HQAM)

•

One cable, Data+DC (CorEvo 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.

8.1.3.1

One cable, Data+DC (MPT Access unit to MPT-XP/XPHQAM) 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 183 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. The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool (1AD160490001).

477


Figure 183


MPT Access to MPT-XP/XP-HQAM interconnection (with MPT Extended Power Unit)




MPT1

MPT2

VDC Normal +24 or -48V VDC Range -/+19.2 to +57.6V

Alarms DC Voltage MPT1 Batt.A

DC

DC Voltage

DC+ODU Data

DC

DC Voltage

DC+ODU Data

MPT2 Batt.B

Battery A

+

VDC

Battery B

-

+

VDC

-

Bat A

Mgmt Port

9500 MPR

+

Bat A

Major

Bat B

Minor


DC VOLTAGE

+ FAN ALARM

Bat B

25493

8.1.3.2

Two cables, Data+DC (MPT Access unit to MPT-XP/XPHQAM) 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 100 m the power cable can be CAT5E cable 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 100m, 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 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).

478


Cables

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

Figure 184

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




MPT1

MPT2



DC

DC Voltage

DC+ODU Data

DC

DC Voltage

DC+ODU Data

MPT2 Batt.B

Battery A

+

VDC

Battery B

-

+

VDC

-

Bat A

Mgmt Port

9500 MPR

+

DC VOLTAGE

Bat A

Major

Bat B

Minor

External Alarms

+ FAN ALARM

Bat B

25476

8.1.3.3

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

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.

479


Figure 185


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




MPT1

MPT2



DC

DC Voltage

DC+ODU Data

DC

DC Voltage

Battery A

MPT2 Batt.B

DC+ODU Data

+

VDC

Battery B

-

+

VDC

-

Bat A

Mgmt Port

9500 MPR

+

Bat A

Major

Bat B

Minor


DC VOLTAGE

+ FAN ALARM

Bat B

25481

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.

8.1.3.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). In Figure 186 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.

480


Figure 186

Cables

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

9500 MPR


MPT1

RJ45 + R2CT CAT5e outdoor rated, shielded

MPT2



DC

DC Voltage

DC+ODU Data

DC

DC Voltage

DC+ODU Data

MPT2 Batt.B

Battery A

+

VDC

Battery B

-

+

VDC

-

CAT5e indoor rated, shielded

Bat A

Mgmt Port

9500 MPR

+

DC VOLTAGE

Bat A

Major

Bat B

Minor

External Alarms

+ FAN ALARM

Bat B

25475

8.1.3.5

Two cables, Data and DC (CorEvo unit to MPT-XP/XPHQAM)


one optical cable connected to port#7 or port #8 of the CorEvo unit.

•


481


Figure 187


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

N-to-Ethernet pair pigtail + RJ45 + R2CT

9500 MPR

Coaxial cable


MPT1

MPT2



DC

DC Voltage

DC+ODU Data

DC

DC+ODU Data

DC Voltage

Battery A

MPT2 Batt.B

+

VDC

Battery B

-

+

VDC

-

Fiber CSMv2

Bat A

Mgmt Port

R

S

9500 MPR 1

2

3

4

5

6

7

8

DC VOLTAGE

POWER INJECTOR

DC VOLTAGE

MPT 1

DC + DATA

DATA

10G

-

A

-48V

DC

MPT2

DC + DATA

DATA -48V

+ Bat A

Major

Bat B

Minor

DC

External Alarms

+ FAN ALARM

Bat B

24966

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.

8.1.3.6

One cable, Data+DC (CorEvo unit to MPT-XP/XP-HQAM) The MPT-XP/XP-HQAM is connected to the CorEvo through the MPT Extended Power Unit using electrical Ethernet cables. One cable connects an CorEvo in the MSS to the MPT Extended Power Unit. A second cable connects the MPT Extended Power Unit to its MPT-XP/XP-HQAM (the MPT Extended Power Unit provides the PFoE). In Figure 188 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.

482


Figure 188

Cables

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

CAT5e outdoor rated, shielded RJ45 + R2CT

9500 MPR


MPT1

MPT2



DC

DC Voltage

DC+ODU Data

DC

DC+ODU Data

DC Voltage

Battery A

MPT2 Batt.B

+

VDC

Battery B

-

+

VDC

-

CAT5e indoor rated, shielded CSMv2

Bat A

Mgmt Port

R

S

9500 MPR 1

2

3

4

5

6

7

8

DC VOLTAGE

POWER INJECTOR

DC VOLTAGE

MPT 1

DC + DATA

DATA

10G

-

A

-48V

DC

MPT2

DC + DATA

DATA -48V

+ Bat A

Major

Bat B

Minor

DC

External Alarms

+ FAN ALARM

Bat B

24967

8.1.3.7

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


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

•


483


Figure 189


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




MPT1

MPT2



DC

DC Voltage

DC+ODU Data

DC

DC Voltage

DC+ODU Data

MPT2 Batt.B

Battery A

+

VDC

Battery B

-

+

VDC

-

Bat A

Mgmt Port

9500 MPR

+

Bat A

Major

Bat B

Minor


DC VOLTAGE

+ FAN ALARM

Bat B

25480

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.

8.1.3.8

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

484


Figure 190

Cables

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

9500 MPR


MPT1

MPT2


Alarms

RJ45 + R2CT CAT5e outdoor rated, shielded

DC Voltage MPT1 Batt.A

DC

DC Voltage

DC+ODU Data

DC

DC Voltage

DC+ODU Data

MPT2 Batt.B

Battery A

+

VDC

Battery B

-

+

VDC

-

CAT5e indoor rated, shielded

Bat A

9500 MPR

+

2

Bat A

Major

Bat B

Minor

External Alarms

S

-

1

+ FAN ALARM

Bat B

25479

8.1.4

MSS-4/8 to MPT-MC interconnection The MPT-MC can be connected in the following ways:

8.1.4.1

•

One cable (MPT Access unit to MPT-MC)

•

One cable (CorEvo unit to MPT-MC)

•

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

•

One cable (EASv2 unit to MPT-MC)

One cable (MPT Access unit to MPT-MC)

One electrical Ethernet cable connects an MPT Access unit in the MSS to its MPTMC (the MPT Access unit provides the PFoE). The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool (1AD160490001).

485


Figure 191


MPTACC to MPT-MC interconnection

Ethernet CAT5e

Bat A

Mgmt Port

9500 MPR

+

Bat A

Major

Bat B

Minor


DC VOLTAGE

+ FAN ALARM

Bat B

25490

8.1.4.2

One cable (CorEvo unit to MPT-MC)

The MPT-MC is connected to a Power Injector through one electrical Ethernet cable. Figure 192 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 193 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 192

CorEvo to MPT-MC connection through the Power Injector Box

Power Injector box CAT5e 9500 MPR POWER INJECTOR

MPT 1

MPT 2 DC Voltage

DATA

DC+DATA

DC Voltage

DATA

DC+DATA

DC Voltage

-48 VDC

-48 VDC

To the battery CSMv2

Bat A

Mgmt Port

R

S

9500 MPR 1

2

3

4

5

6

7

8

DC VOLTAGE

POWER INJECTOR

DC VOLTAGE

MPT 1

DC + DATA

DATA

10G

-

A

-48V

DC

MPT2

DC + DATA

DATA -48V

+ Bat A

Major

Bat B

Minor

DC

External Alarms

+ FAN ALARM

Bat B

24969

486


Figure 193

Cables

CorEvo to MPT-MC connection through the Power Injector card

CAT5e

CSMv2

Bat A

Mgmt Port

R

S

9500 MPR 1

2

3

4

5

6

7

8

DC VOLTAGE

POWER INJECTOR

DC VOLTAGE

MPT 1

DC + DATA

DATA

10G

-

A

-48V

DC

MPT2

DC + DATA

DATA -48V

+ Bat A

Major

Bat B

Minor

DC

External Alarms

+ FAN ALARM

Bat B

24970

487



8.1.4.3

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

The MPT-MC is connected to a Power Injector through one electrical Ethernet cable. Figure 192 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 193 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 194

Core-E to MPT-MC connection through the Power Injector Box


MPT 1

MPT 2 DC Voltage

DATA

DC+DATA

DC Voltage

DATA

Power Injector Box

DC+DATA

DC Voltage

-48 VDC

-48 VDC

To the battery Bat A

Mgmt Port

9500 MPR

+

Bat A

Major

Bat B

Minor


DC VOLTAGE

+ FAN ALARM

Bat B

25488

Figure 195

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

CAT5e

Bat A

Mgmt Port

9500 MPR

DC VOLTAGE

POWER INJECTOR

DC VOLTAGE

MPT 1

DC + DATA

DATA -48V

MPT2

DC + DATA

DATA

DC

-48V

+

Bat A

Major

Bat B

Minor

DC


DC VOLTAGE

+ FAN ALARM

Bat B

25489

488


8.1.4.4

Cables

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 Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool (1AD160490001).

Figure 196

EASv2 to MPT-MC interconnection


9500 MPR

+

2

S

Bat A

Major

Bat B

Minor

External Alarms

-

1

+ FAN ALARM

Bat B

25478

8.1.5

MSS-1 to MPT ODU interconnection The MSS-1 can be connected to an MPT ODU in the following 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 1 and 2 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)

•


489



8.1.5.1

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

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

8.1.5.2

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

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

490


8.1.5.3

Cables

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

Two cables connect MSS-1 ports 1 or 2 to MPT-HC/HC-HQAM: •

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

•

a cable connected to either the ports #1 or #2 of the MSS-1, a Power Injector box, MPT Power Unit, MPT Extended Power Unit (for very long distances), or station battery, to provide the power supply. −

For length lower or equal to 100 m, the power cable is generally CAT5E cable, except a coax cable (with a RJ45-to-N pigtrail) in the case of MPT power unit. The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool (1AD160490001);

−

For length higher than 100 m, the cable is 50 ohm coaxial cable with a pigtail RJ45-to-N (two pigtails are needed with MSS-1 PFoE ports).

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

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.

These connections are similar to those shown in Figure 172.

491



8.1.5.4

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


•

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

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

−


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

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.

These connections are similar to those shown in Figure 185.

8.1.5.5

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

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/XP-HQAM (the MPT Extended Power Unit provides the PFoE). These connections are similar to those shown in Figure 186. 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.

492


8.1.5.6

Cables

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 185. •


•


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.

8.1.5.7


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 191. The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool (1AD160490001).

8.1.5.8


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

493



8.1.6

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 to 3 to MPT-/HC/HC-HQAM)

•

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

•

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

Table 53 provides information about MSS-O cable length for the ETSI market. Table 54 provides information about MSS-O cable length for the ANSI market. For power consumption information, see the 9500 MPR Technical Specifications for Split Mount Applications.

8.1.6.1

One cable, Data+DC (MSS-O ports 1 to 3 to MPT-/HC/HCHQAM)

One electrical Ethernet cable connects MSS-O shelf ports 1 to 3 to its MPT-HC/HCHQAM (MSS-O port provides the PFoE). These connections are similar to those shown in Figure 172. Power can also be supplied by the following: •


•

MPT Power Unit

•


•


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 see How to connect the MPT-HC/HC-HQAM to the station battery. The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool (1AD160490001).

494


8.1.6.2

Cables

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 191. The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool (1AD160490001).

8.1.6.3

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

One electrical Ethernet cable connects MSS-O port 3 to a power injector box. 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 192. The power injector box is an indoor device to be installed in a 19”/21” rack. Note: The power injector box must be connected to a fuse or a breaker on a customer power distribution box. The recommended value is 3 Amps per MPT.

8.1.7

8.1.7.1

MSS-1c to MPT-HC/HC-HQAM/9558HC interconnection MSS-1c to MPT-HC/HC-HQAM/9558HC interconnection (one cable) One electrical Ethernet cable connects the MSS-1c to its MPT-HC/HC-HQAM/ 9558HC. The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool (1AD160490001).

495


Figure 197


MPT-HC/HC-HQAM/9558HC connection

CAT5e 9500 MPR MPT 1

DC Voltage

USER 3

USER 1

HK

NMS 1

MPT 1

USER 2 Sync E

CT

NMS 2

MPT 2

E1/T1 (9-10)

MPT 2

USER 4 Sync E

E1/T1 (1-8)

M

W

MPT 1

m

A

MPT 2

+ -48 VDC -

25473

8.1.7.2

Optical cable

Two cables connect the MSS-1c to its MPT-HC/HC-HQAM/9558HC: •

One cable is a 50 ohm cable to send the power supply to the MPT-HC/HCHQAM/9558HC: −


− •


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 adapter cord must be connected to the coaxial cable on the MPT-HC/HCHQAM/9558HC.

496


Figure 198

Cables

MPT-HC/HC-HQAM/9558HC connection (optical cable+power cable from MSS-1c)

N-to Ethernet pair pigtail + RJ45 + R2CT Coaxial cable N-to Ethernet pair pigtail + RJ45

Fiber 9500 MPR MPT 1

USER 3

MPT 2

USER 4 Sync E

DC Voltage

USER 1

HK

NMS 1

MPT 1

USER 2 Sync E

CT

NMS 2

MPT 2

E1/T1 (9-10)

E1/T1 (1-8)

M

W

MPT 1

m

A

MPT 2

+ -48 VDC -

25474

Figure 199

MPT-HC/HC-HQAM/9558HC connection (optical cable+power cable from station battery)

N-to-Ethernet pair pigtail RJ45 + R2CT

Fiber

Coaxial cable Lightning arrestor + Low pass filter + Pigtail N-to-2 wires 9500 MPR MPT 1

DC Voltage

USER 3

USER 1

HK

NMS 1

MPT 1

USER 2 Sync E

CT

NMS 2

MPT 2

E1/T1 (9-10)

MPT 2

USER 4 Sync E

E1/T1 (1-8)

M

W

MPT 1

m

A

MPT 2

To the battery

+ -48 VDC -

25482

Note: MPT-HC/HC-HQAM/9558HC must be connected to a fuse or a breaker on a customer power distribution box. The recommended value is 3 Amps.

497



8.1.8

MSS-1c to MPT-XP/XP-HQAM interconnection

8.1.8.1

MSS-1c to MPT-XP/XP-HQAM interconnection (PFoE) One electrical Ethernet cable connects the MSS-1c to MPT Extended Power Unit and a second Ethernet cable connects the MPT Extended Power Unit to its MPT-XP/ XP-HQAM. The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool (1AD160490001).

Figure 200

MPT-XP/XP-HQAM connection Electrical Ethernet Cable (DC+DATA)


CT Port

MSS-1c MPT #1

WebEML 23065

8.1.8.2

Optical cable

Two cables connect the MSS-1c to its MPT-XP/XP-HQAM: •

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


− •



498


Cables

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

Figure 201

MPT-XP/XP-HQAM connection (optical cable from MSS-1c + (power supply cable from Extended Power Unit) N-RJ45 Adapter Cord Coaxial power supply cable Optical Ethernet cable


CT Port

MSS-1c MPT #1

WebEML 23064

499



8.1.9

MSS-1c to MPT-MC interconnection One electrical Ethernet cable connects the MSS-1c to its MPT-MC. The Ethernet electrical cable is provided with connectors to be mounted on site with the specific RJ45 tool (1AD160490001).

Figure 202

MPT-MC connection

Ethernet CAT5e 9500 MPR MPT 1

USER 3

MPT 2

USER 4 Sync E

DC Voltage

USER 1

HK

NMS 1

MPT 1

USER 2 Sync E

CT

NMS 2

MPT 2

E1/T1 (9-10)

E1/T1 (1-8)

M

W

MPT 1

m

A

MPT 2

+ -48 VDC -

25483

8.1.10

MPT-MC/HC/HC-HQAM/9558HC connectivity for MPR-e (1+0 configuration) The MPT-MC/HC/HC-HQAM/9558HC can be connected to the Ethernet generic Device through: •

Electrical interface

•

Optical interface (an optional SFP must be installed in the MPT-MC/HC/HCHQAM/9558HC).

or

8.1.10.1

Electrical interface The MPT-MC/HC/HC-HQAM/9558HC is connected to a Power Injector through one electrical Ethernet cable. Figure 203 shows the connections used with the Power Injector Box.

500


Cables

Figure 204 shows the connections used with the MPT Extended Power Unit. The Power Injector box is an indoor device that is installed in a 19-inch or 21-inch rack. Figure 203

MPT-HC/HC-HQAM/9558HC connection through the Power Injector Box


MPT 1

MPT 2 DC Voltage

DATA

DC Voltage

DC+DATA

DATA

DC+DATA

DC Voltage

-48 VDC

-48 VDC

To the Ethernet generic device

To the battery

25471

Figure 204

MPT-XP/XP-HQAM/9558HC connection through the MPT Extended Power Unit

To the Ethernet generic device 9500 MPR


CAT5e

MPT1

MPT2



DC

DC Voltage

DC+ODU Data

DC

DC Voltage

DC+ODU Data

MPT2 Batt.B

Battery A

+

VDC

Battery B

-

+

VDC

-

To the battery 25470

8.1.10.1.1

Connecting an AC Power Converter to a Power Injector Box (ETSI market) This section provides information on how to connect an external AC power converter to a Power Injector Box (PIB) when an AC power source is required. The procedure involves modifying the open end of a pigtail O-ring cable so that the wires can be connected to the DC power terminal block on the PIB, then connecting the other end of the cable to the AC power converter. The following hardware and tools are required:

501


Figure 205


•

AC power supply (250W 120/240V AC power converter) – part number 3HE05838AA; see Figure 205.

•

7705 AC power converter pigtail - O-ring – part number 3HE05837BA; see Figure 206.

•

wire stripper

•

wire cutter

AC Power Converter

1

2 21523

Table 51

AC Power Converter features

Key

Description

1

Male 6-pin connector

2

AC cord set1 1: Two AC cord sets are supplied with the AC power converter to match North American and European style AC outlets.

Figure 206

AC Power O-Ring Pigtail Cable Assembly

1

2 3 21525

502


Table 52

Cables

AC Power Converter O-Ring Pigtail Cable features

Key

Description

1

Ring lug connector (–VDC, black wire)

2

Ring lug connector (+VDC, red wire)

3

Female 6-pin connector Preparing the O-Ring Cable Modify the pigtail O-ring cable by cutting off the output terminals (the O-ring lug connectors) on the O-ring cable and splicing the open-ended wires to interface with the DC power terminal block on the PIB. Danger: Ensure that the power supply is disconnected from the AC main power feed before preparing and cutting the DC wires.

To modify the pigtail O-ring cable: •

Figure 207

Cut off the O-ring lugs (items 1 and 2 on the cable in Figure 206) and strip approximately 0.5 cm of shield from each wire to expose the conductors. See Figure 207.

Modified AC Power O-Ring Pigtail Cable

0.5 cm (0.2 in) 23094

Connecting the AC Power Converter to the DC inputs on the PIB To connect the AC power converter to the DC inputs on the PIB: •

Connect the modified end of the pigtail O-ring cable to the DC inputs on the PIB. Connect the -VDC (black wire) to the -Batt terminal on the PIB terminal block; connect the +VDC (red wire) to the +Batt terminal on the PIB terminal block.

•

Connect the male 6-pin connector on the AC Power Converter (item 1 in Figure 205) to the female 6-pin connector on the pigtail cable (item 3 in Figure 206).

503



•

8.1.10.2

Plug the AC power converter cord (item 2 in Figure 205) into an AC power outlet.

Optical interface One Optical Ethernet cable connects the MPT-HC/HC-HQAM/9558HC to the Ethernet generic Device and one coaxial cable connects the MPT-HC/HC-HQAM/ 9558HC to MPT Power Unit or MPT Extended Power Unit. For longer cable lengths than described in this document, contact Product Management. Figure 208 shows the connections used with the MPT Power Unit. Figure 209 shows the connections used with the MPT Extended Power Unit. Figure 210 shows the connections used with direct connection to office power. The MPT Power unit is an indoor device that is installed in a 19-inch or 21-inch rack.

Figure 208

MPT-HC/HC-HQAM/9558HC connection (optical cable for traffic and coaxial cable to MPT Power Unit)



MPT Power Unit

MPT1

MPT2

MPT3

MPT4

MPT Alarms

1 2

3 4

A B


DC Voltage

Battery A

DC Voltage

+

VDC

Battery B

-

+

VDC

-

To the battery Optical connection To the Ethernet generic device 25500

504


Figure 209

Cables

MPT-HC/HC-HQAM/9558HC connection (optical cable for traffic and coaxial cable to MPT Extended Power Unit)




MPT1

MPT2



DC

DC Voltage

DC+ODU Data

DC

DC Voltage

DC+ODU Data

MPT2 Batt.B

Battery A

+

VDC

Battery B

-

+

VDC

-


Figure 210

MPT-HC/HC-HQAM/9558HC connection (optical cable for traffic and coaxial cable for power supply)


Coaxial cable

Lightning arrestor + low pass filter + pigtail N to 2 wires

To the battery

Optical connection To the Ethernet generic device 25501

Note: The MPT-HC/HC-HQAM/9558HC must be connected to a fuse or a breaker on a customer power distribution box.


505



8.1.11

MPT-HC/HC-HQAM/9558HC connectivity for MPR-e (co-channel XPIC configuration)

In this configuration, the MPT-HC/HC-HQAM/9558HC units must be installed on the OMT that is directly connected to the antenna. The two MPT-HC/HC-HQAM/9558HC units must be connected to the Indoor Section as explained in MPT-MC/HC/HCHQAM/9558HC connectivity for MPR-e (1+0 configuration). The two MPT-HC/HC-HQAM/9558HC units must also be interconnected through two terminated cables (XPIC and RPS cables) as shown in Figure 211, Figure 212, and Figure 213. Note: The extra length of the RPS and XPIC cables must be bound by using tie-wraps, either on the pole or on the other cables coming from the ODUs.

Figure 211

MPT-HC/HC-HQAM/9558HC connection through the Power Injector Box (co-channel XPIC)

RPS cable

XPIC cable

9500 MPR POWER INJECTOR

MPT 1

MPT 2 DC Voltage

DATA

DC+DATA

DC Voltage

DATA

DC+DATA

DC Voltage

-48 VDC

To the battery

-48 VDC

To the Ethernet generic device To the Ethernet generic device 25502

506


Figure 212

Cables

MPT-HC/HC-HQAM/9558HC connection through the MPT extended power unit (cochannel XPIC)

RPS cable

XPIC cable CAT5e 9500 MPR


MPT1

MPT2



DC

DC Voltage

DC+ODU Data

DC

DC Voltage

DC+ODU Data

MPT2 Batt.B

Battery A

+

VDC

Battery B

-

+

VDC

-

To the battery To the Ethernet generic device To the Ethernet generic device

8.1.12

25504

Connection to MPT Power Unit

One Optical Ethernet cable connects the MPT-HC/HC-HQAM/9558HC to the MSS or Ethernet generic Device and one coaxial cable connects the MPT-HC/HC-HQAM/ 9558HC to MPT Power Unit. For longer cable lengths than described in this document, contact Product Management. Figure 208 shows the connections used with the MPT Power Unit. The MPT Power unit is an indoor device that is installed in a 19-inch or 21-inch rack.

507



Figure 213

MPT-HC/HC-HQAM/9558HC connection (optical cable for traffic and coaxial cable to MPT Power Unit)

N-to-Ethernet pair pigtail RJ45 + R2CT Coaxial cable

Fiber

9500 MPR

MPT Power Unit

MPT1

MPT2

MPT3

MPT4

MPT Alarms

1 2

3 4

A B


DC Voltage

Battery A

DC Voltage

+

VDC

Battery B

-

+

VDC

-




8.1.13

Connection to MPT Extended Power Unit

One Optical Ethernet cable connects the MPT-HC/HC-HQAM/9558HC to the MSS or Ethernet generic Device and one coaxial cable connects the MPT-HC/HC-HQAM/ 9558HC to the MPT Extended Power Unit. For longer cable lengths than described in this document, contact Product Management. Figure 209 shows the connections used with the MPT Extended Power Unit. The MPT Extended Power unit is an indoor device that is installed in a 19-inch or 21inch rack.

508


Figure 214

Cables

MPT-HC/HC-HQAM/9558HC connection (optical cable for traffic and coaxial cable to MPT Extended Power Unit)




MPT1

MPT2



DC

DC Voltage

DC+ODU Data

DC

DC Voltage

DC+ODU Data

MPT2 Batt.B

Battery A

+

VDC

Battery B

-

+

VDC

-




8.2

Cable length When separate cables are used for data and power, two cables connect an MSS-1/ 4/8 or MSS-1c to the MPT ODU: •

One cable is a coaxial or Cat5E cable connected to 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 ODU

509



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.

•


Note: A special cord adapter must be connected to the coaxial cable on the MPT ODU. 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.

These connections are similar to those shown in Figure 215. Figure 215

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


Coaxial cable

Bat A

Mgmt Port

9500 MPR

+

Bat A

Major

Bat B

Minor


DC VOLTAGE

+ FAN ALARM

Bat B

25486

8.2.1

Cable length with MSS-O Table 53 provides information about MSS-O cable length for the ETSI market. Table 54 provides information about MSS-O cable length for the ANSI market.

510


Table 53

Cables

MSS-O cable length for the ETSI market (220V)

MSS-O version

Power to MSS-O

MSS-O to MPT

ALU Cable type

Maximum distance

ALU Cable type

Maximum distance

MSS-O AC

3x 1.5 mm2 cord

1000 m

CAT5e

3x 1.5 mm2 cord

1000 m

2x 2.5 mm2 cord

MSS-O DC

Maximum number of MPT supported

Comments

100 m

2x MPT-HC, HCHQAM, or MC

—

CAT5e

70 m

1x MPT-XP or XP-HQAM

No other ODU supported

50 m

CAT5e

100 m

2x MPT-HC, HCHQAM, or MC

—

2x 2.5 mm2 cord

50 m

CAT5e

70 m

1x MPT-XP or XP-HQAM

—

2x 2.5 mm2 cord

50 m

CAT5e

100 m MPT-HC/ MC/HCHQAM 70 m MPTXP/XPHQAM

1x MPT-HC, HCHQAM, or MC + 1x MPT-XP or XP-HQAM 1

—

Note: 1.

Concerns a mixture of MPT-HC-HQAM/XP-HQAM on different links, not on the same link (for example, in 1+1)

511


Table 54


MSS-O cable length for the ANSI market (110V)

MSS-O version

AC voltage

Minimum voltage at power socket on wall

Power to MSS-O

MSS-O to MPT

ALU Cable type

Maximum distance

ALU Cable type

Maximum distance

MSS-O AC

110 V

102 V

3x 1.5 mm2 AWG15

42 m

CAT5e

110 V

101 V

3x 1.5 mm2 AWG15

21 m

110 V

Other value

Other cables

110 V

102 V

110 V

110 V

512


Comments

100 m

2x MPTHC, HCHQAM, or MC

—

CAT5e

100 m


—

To be calculate d1

CAT5e

100 m


—

3x 1.5 mm2 AWG15

42 m

CAT5e

70 m

1x MPTXP or XPHQAM


101 V

3x 1.5 mm2 AWG15

21 m

CAT5e

70 m

1x MPTXP or XPHQAM


Other value

Other cables

To be calculate d1

CAT5e

70 m

1x MPTXP or XPHQAM



Table 54

Cables

MSS-O cable length for the ANSI market (110V) (Continued)

MSS-O version

AC voltage

MSS-O DC

—

Minimum voltage at power socket on wall

Power to MSS-O

MSS-O to MPT


Comments

ALU Cable type

Maximum distance

ALU Cable type

Maximum distance

2x 2.5 mm2 AWG13

50 m

CAT5e

100 m


—

2x 2.5 mm2 AWG13

50 m

CAT5e

70 m


—

2x 2.5 mm2 AWG13

50 m

CAT5e

100 m MPT-HC/ MC/HCHQAM 70 m MPT-XP/ XPHQAM 2

1x MPTHC, HCHQAM, or MC + 1x MPTXP or XPHQAM 2

—

Notes: 1.

To ensure 100 V at the MSS-O power connector

2.

Concerns a mixture of MPT-HC-HQAM/XP-HQAM on different links, not on the same link (for example, in 1+1)

513



8.2.2

Cable length with MPT Power Unit Table 55 provides the maximum allowed cable length without step-up for a minimum input battery voltage of 38.4 V.

Table 55

Maximum allowed cable lengths for MPT Power Unit

Cable type

Coaxial cable 1AC001100022/ 1AC014320002

Coaxial cable 1AC041350001

Powering and data

Power only, data optical cable

Power only, data optical cable

Configuration

Power need

Maximum length

Maximum length

MPT-HC1

42.0 W

510 m/1673 ft

230 m

MPT-HC with XPIC1

48.0 W

435 m/1427 ft

200 m

MPT-HC-HQAM1

39.5 W

550 m/1804 ft

255 m

MTP-HC-HQAM with XPIC1

40.5 W

535 m/1755 ft

245 m

Note: 1.

Equipped with SFP

Note: 1AC001100022 and 1AC041350001 are used in ETSI, 1AC014320002 is used in ANSI.

514


8.2.3

Cables

Cable length with MPT Extended Power Unit Table 56 provides the maximum allowed cable length with step-up with output voltage of -57 V.

Table 56

Maximum allowed cable lengths for MPT Extended Power Unit

Cable type

Ethernet UTP 5E with outer screen and braid 1AC016760006

Ethernet UTP 5E with outer screen and braid 1AC016760006

Coaxial cable 1AC001100022 / 1AC014320002

Coaxial cable 1AC041350001

Powering and data

Power and Data on Ethernet cable

Power only, Data optical cable



Configuration

Power need

Maximum length

Maximum length

Maximum length

Maximum length

MPT-HC 1

42.0 W

N/A

400 m/1312 ft

1100 m/3608 ft

500 m

MPT-HC with XPIC 1

48.0 W

N/A

350 m/1148 ft

1000 m/3280 ft

440 m

MPT-XP 1

77.0 W

40m/131 ft

155 m/508 ft

480 m/1574 ft

280 m

MPT-XP with XPIC 1

83.0 W

40m/131 ft

115 m/508 ft

360 m/1181 ft

200 m

MPT-HCHQAM 1

39.5 W

N/A

440 m/1143 ft

1700 m/5577 ft

790 m

MPT-HCHQAM with XPIC 1

40.5 W

N/A

430 m/1410 ft

1600 m/5249 ft

770 m

MPT-XPHQAM 1

75.0 W

40 m/131 ft

170 m/557 ft

650 m/2132 ft

300 m

MPT-XPHQAM with XPIC 1

76.0 W

40 m/131 ft

165 m/541 ft

620 m/2033 ft

290 m

Note: 1.

Equipped with SFP

515



Note: Any additional external Lightning Arrestor will reduce this length of 10 m.

Note: 1AC016760006 and 1AC014320002 are used in ETSI and ANSI installations. 1AC041350001 is used in ETSI only.

516



9 Software and miscellaneous unit descriptions See Table 57 for brief descriptions of software, RTU capacity License, and documentation. See Table 58 for brief descriptions of miscellaneous components. Table 57

Software, RTU capacity license, and documentation unit descriptions

UNIT

DESCRIPTION

9500 MPR CT License PN: 3EM23067AAAA Qty: 1 per PC Installed

Craft Terminal license for PC used to interface with 9500 MPR.

RTU Capacity License PN: 3EM23068AAAA/3EM23068AGAA Qty: 1 per radio channel

Right To Use (RTU) Capacity Licenses conditions the 9500 MPR-A NE to the maximum capacity of a radio channel. The RTU capacity license supports the entire band supported by the radio. An RTU Capacity license is required for each radio channel configured on the 9500 MPR-A NE. PN: 3EM23068AAAA is RTU up to 40Mb/s TRx Capacity PN: 3EM23068ABAA is RTU up to 80Mb/s TRx Capacity PN: 3EM23068ACAA is RTU up to 120Mb/s TRx Capacity PN: 3EM23068ADAA is RTU up to 160Mb/s TRx Capacity PN: 3EM23068AFAA is RTU up to 220Mb/s TRx Capacity PN: 3EM23068AEAA is RTU up to 320Mb/s TRx Capacity PN: 3EM23068AGAA is RTU up to 450Mb/s TRx Capacity

RTU Adaptive Modulation (License) PN: 3EM23073AAAA Qty: 1 per adaptive modulation radio channel

Right To Use (RTU) Adaptive Modulation License conditions the 9500 MPR-A NE to the number of radio channels which can be configured with adaptive modulation. An RTU Adaptive Modulation license is required for each radio channel configured with adaptive modulation.

517

Release 7.0.0 3DB 19383 ACAA Issue 01 Software and miscellaneous unit descriptions

Table 57


Software, RTU capacity license, and documentation unit descriptions (Continued)

UNIT

DESCRIPTION

RTU 5.8 GHz Unlicensed Band (License) PN: 3EM23261AAAA Qty: 1 per unlicensed band radio channel

Right To Use (RTU) 5.8 GHz Unlicensed Band License conditions the 9500 MPR-A NE to restrict the use of a RTU Capacity License to the 5.8 GHz Unlicensed Band. When the RTU 5.8 GHz Unlicensed Band License is present the radio must operated in the 5.8 GHz unlicensed band. The RTU 5.8 GHz Unlicensed Band license is used in conjunction with a RTU Capacity license.

RTU 9500 MSP Ring (License) PN: 3MU00086AAAA Qty: 1 per Ring configured with MPT-HC/ HC-HQAM/XP/XP-HQAM

Right To Use (RTU) 9500 MSP Ring RTU License conditions the 9500 MPR-A NE to the number of Ethernet Ring Protection which can be configured in the NE which include MPT-HC/HC-HQAM/XP/XP-HQAM radio. A 9500 MSP Ring license is required for each ERPS Ring configured with MPT-HC/HC-HQAM/XP/XP-HQAM on the NE.

RTU 9500 Packet Throughput Booster (License) PN: 3MU00092AAAA Qty: 1 per NE

Right To Use (RTU) 9500 Packet Throughput Booster RTU License conditions the 9500 MPR-A NE to enable the Packet Throughput Booster on MPT-HC/XP/HC-HQAM/ XP-HQAM/9558HC and MPT-HL radio interfaces.

518


Table 57



UNIT

DESCRIPTION

RTU Capacity License Upgrades PN: 3EM23577AAAA/3EM23577AGAA Qty: 1 per each additional radio channel/ capability

Right To Use (RTU) Capacity License Upgrade conditions the 9500 MPR-A NE to increase the number of radio channels supported on the NE and the maximum capacity of the additional radio channel. A RTU license is required for each radio channel configured on the 9500 MPR-A NE. PN: 3EM23577AAAA is RTU up to 40Mb/s TRx Capacity Upgrade PN: 3EM23577ABAA is RTU up to 80Mb/s TRx Capacity Upgrade PN: 3EM23577ACAA is RTU up to 120Mb/s TRx Capacity Upgrade PN: 3EM23577ADAA is RTU up to 160Mb/s TRx Capacity Upgrade PN: 3EM23577BBAA is RTU up to 220Mb/s TRX Capacity Upgrade PN: 3EM23577AEAA is RTU up to 320Mb/s TRx Capacity Upgrade PN: 3EM23577BCAA is RTU up to 450Mb/s TRX Capacity Upgrade PN: 3EM23577BTAA is RTU up to 500Mb/s TRX Capacity Upgrade PN: 3EM23577AFAA is RTU Adaptive Modulation Upgrade PN: 3EM23577AGAA is RTU 5.8 GHz Unlicensed Band Upgrade PN: 3EM23577AUAA is 9500 MSP Ring RTU Upgrade PN: 3EM23577AVAA is RTU Packet Throughput Booster Upgrade

519


Table 57



UNIT

DESCRIPTION

Capacity Upgrades PN: 3EM23577AHAA/3EM23577ASAA Qty: 1 per radio channel capacity increase

Capacity Upgrades increases the maximum capacity of radio channels supported on an 9500 MPR-A NE. PN: 3EM23577AHAA is MPT-TR-40T80 (40 Mb/s to 80 Mb/s) PN: 3EM23577AJAA is MPT-TR-40T120 (40 Mb/s to 120 Mb/s) PN: 3EM23577AKAA is MPT-TR-40T160 (40 Mb/s to 160 Mb/s) PN: 3EM23577BDAA is MPT-TR-40T220 (40 Mb/s to 220 Mb/s) PN: 3EM23577ALAA is MPT-TR-40T320 (40 Mb/s to 320 Mb/s) PN: 3EM23577BHAA is MPT-TR-40T450 (40 Mb/s to 450 Mb/s) PN: 3EM23577AMAA is MPT-TR-80T120 (80 Mb/s to 120 Mb/s) PN: 3EM23577BEAA is MPT-TR-80T220 (80 Mb/s to 220 Mb/s) PN: 3EM23577ANAA is MPT-TR-80T160 (80 Mb/s to 160 Mb/s) PN: 3EM23577APAA is MPT-TR-80T320 (80 Mb/s to 320 Mb/s) PN: 3EM23577BJAA is MPT-TR-80T450 (80 Mb/s to 450 Mb/s) PN: 3EM23577BAA is MPT-TR-120T160 (120 Mb/s to 160 Mb/s) PN: 3EM23577BFAA is MPT-TR-120T220 (120 Mb/s to 220 Mb/s) PN: 3EM23577BKAA is MPT-TR-120T450 (120 Mb/s to 450 Mb/s) PN: 3EM23577BGAA is MPT-TR-160T220 (160 Mb/s to 220 Mb/s) PN: 3EM23577BLAA is MPT-TR-160T450 (160 Mb/s to 450 Mb/s) PN: 3EM23577ASAA is MPT-TR-160T320 (160 Mb/s to 320 Mb/s) PN: 3EM23577BMAA is MPT-TR-220T450 (220 Mb/s to 450 Mb/s)

520


Table 57



UNIT

DESCRIPTION

XPIC RTU 3MU00122AAAA

PN: 3EM23577BNAA is MPT-TR-320T450 (320 Mb/s to 450 Mb/s) Right To Use (RTU) XPIC RTU License conditions the 9500 MPR-A NE to enable XPIC on MPT-HLC and MPTHC-HQAM/MPT-XP-HQAM radio interfaces. PN: 3EM23577AYAA is XPIC RTU Upgrade

AES RTU 3MU00121AAAA

Right To Use (RTU) AES RTU License conditions the 9500 MPR-A NE to enable AES encryption on MPT-HC/ XP/HC-HQAM/XP-HQAM/9558HC and MPT-HLC radio interfaces. PN: 3EM23577AZAA is 9500 MPR AES RTU Upgrade

1588 TC RTU 3DB19304AAAA

Right To Use (RTU) 1588 TC RTU License conditions the 9500 MPR NE to enable 1588 Transparent Clock

5+ L1 LAG Upgrade RTU 3EM23577BWAA

Right To Use (RTU) 5+ L1 LAG Upgrade RTU License conditions the 9500 MPR NE to enable an L1 LAG with size greater than 4.

Customer Configuration Certificates 3EM24226AB/3EM24226AG Qty: 1 per transceiver

Customer configuration certificates are certificates of factory acceptance testing. PN: 3EM24226AB (MPT-HL) PN: 3EM24226AC (MPT-HC/XP/HQQAM) PN: 3EM24226AE (MPT-HLC) PN:3EM24226AF (Customer Witness Test) PN: 3EM24226AG (Integrated 7705/MPT)

9500 MPR Customer Documentation Library PN: 3DB19275AC for the ANSI market PN: 3DB19282AC for the ETSI market Qty: 1 per documentation library

9500 MPR R7.0.0 Customer Documentation Library contains the user documentation covering the 9500 MPR product release.

521


Table 58


Miscellaneous unit descriptions

UNIT

DESCRIPTION

Optical removal and cleaning tool PN: 3EM07060AA Qty: as required

To clean fiber-optic connectors found in equipment

Aerotech World Trade Ltd equipment for use in cleaning fiber optic connectors

522

•

Inspection microscope, 200X to 400X— Aerotech World Trade Ltd. AWT200 or AWT300

•

Anti-static lint-free swab—Texwipe PN TX757E

•

CLETOP fiber-optic cleaner, Aerotech World Trade Ltd. PN 14100500 for all fiber-optic connectors except bulkhead type

•

CLETOP 2.5mm Stick-Type cleaner- Aerotech World Trade Ltd. PN 14100400, box of 200

•

CLETOP 1.25mm Stick-Type cleaner Aerotech World Trade Ltd. PN 14100401 box of 200



10 Engineering specifications This section provides basic information and specifications relating to signal interfaces, alarm interfaces, and control interfaces. Information about connection points, connector types, and pin assignments are also provided.

10.1

Rack specifications See Rack and rack accessories unit data sheet.

10.2

Power specifications See the following documents:

10.3

•


•


Environmental specifications The 9500 MPR is suitable for installation in the following locations: •

Network Telecommunication Facilities

•

OSP

See the 9500 MPR Technical Specifications for Split Mount Applications.

10.4

Radio profiles For information about radio profiles, see the following documents: •


•


•

9500 MPR-A MPT-HL Engineering Specifications

523

Release 7.0.0 3DB 19383 ACAA Issue 01 Engineering specifications

•

10.5


9500 MPR-A ODU300 Engineering Specifications

Signal interface System signal interfaces comply with customer interface specifications. Supported signal interfaces include the following: E1/DS1, DS3, 10/100/1000 BaseT (electrical) Ethernet, and Gigabit (GigE optical) Ethernet SFP cable connectors.

10.5.1

Signal cable connections P32E1DS1 card •

Each P32E1DS1 card provides two 68-position SCSI connectors. Each SCSI connector supports sixteen (Tx and Rx) E1/DS1 connections for customer E1/DS1 cable interconnect for unprotected P32E1DS1-equipped MSS-4/8 shelf for a total of thirty-two E1/DS1 connections per P32E1DS1 card.

•

Optional E1/DS1 D-Connector patch panel provides four 37-position D-Sub connectors for customer E1/DS1 cable interconnect for the P32E1DS1 equipped MSS-4/8 shelf. There are thirty-two (Tx and Rx) E1/DS1 connections available on the E1/DS1 D-Connector patch panel and feed each E1/DS1 signal to both the main and spare P32E1DS1 cards in protected P32E1DS1 configurations.

•

Optional E1/DS1 RJ-45 patch panel provides thirty-two RJ-45 connectors for customer E1/DS1 cable interconnect for the P32E1DS1 equipped MSS-4/8 shelf. There are thirty-two (Tx and Rx) E1/DS1 connections available on the E1/DS1 RJ-45 patch panel and feed each E1/DS1 signal to both the main and spare P32E1DS1 cards in protected P32E1DS1 configurations.

P2E3DS3 card •

Four mini-BNC connectors on the 2-port P2E3DS3 card provide two (Tx and Rx) DS3 mini-BNC connections for customer DS3 cable interconnect for unprotected P2E3DS3-equipped MSS-4/8 shelf. Optional mini-BNC to BNC cables are available to provide a typical DS3 interface.

•

Optional DS3 Hybrid 3 dB splitters provide (Tx and Rx) DS3 BNC connections and feed each DS3 signal to both main and spare P2E3DS3 cards.

Core-E card

524



•

Four RJ-45 connectors on the Core-E card provide access to the four 10/100/ 1000 Base-T Ethernet ports for customer 10/100/1000 Base-T Ethernet interconnect.

•

One GigE optical SFP port on the Core-E card provides customer access to the GigE optical port on the Core-E card.

CorEvo card •

Four RJ-45 connectors on the CorEvo card provide access to the four 10/100/ 1000 Base-T Ethernet ports for customer 10/100/1000 Base-T Ethernet interconnect.

•

Two 1/10GigE optical SFP ports on the CorEvo-10G card provide customer access to the 10GigE optical port on the card, if the license is present. On the CorEvo-1G card or if the license is not present, the ports serve as GigE optical ports.

•

Two GigE optical SFP ports on the CorEvo card provide customer access to the GigE optical port on the card.

P8ETH card •

Four RJ-45 connectors on the P8ETH card provide access to the four 10/100/ 1000 Base-T Ethernet ports for customer 10/100/1000 Base-T Ethernet interconnect.

•

Four GigE optical SFP ports on the P8ETH card provides customer access to the four GigE optical ports on the P8ETH card. Optionally, the four GigE optical SFP ports are used to interface MPT-HL/MPT-HLC transceiver cards or MPT-HC/HC-HQAM/XP/XP-HQAM units.

EASv2 card •

Four RJ-45 connectors on the EASv2 card provide access to the four 10/100/ 1000 Base-T Ethernet ports for customer 10/100/1000 Base-T Ethernet interconnect.

•

Four GigE optical SFP ports on the EASv2 card provide customer access to the four GigE optical ports on the EASv2 card. Optionally, the four GigE optical SFP ports are used to interface MPT-HL/MPT-HLC transceiver cards or MPT-HC/HC-HQAM/XP/XP-HQAM/MC units.

MSS-O •

Three RJ-45 connectors on the MSS-O provide access to the three 10/100/ 1000 Base-T Ethernet ports for customer 10/100/1000 Base-T Ethernet interconnect.

•

One GigE optical SFP port on the MSS-O provides customer access to the GigE optical port on the MSS-O.

525


10.5.2


DS1 interface See Table 59 for the DS1 interface specifications. See Figure 216 for the asynchronous DS1 format template. The template specifies the signal waveshape boundaries. DS1 waveshape at the 9500 MPR must fit within the template bounds. See Figure 217, Figure 218, and Figure 219 for DS1 jitter characteristics.

10.5.3

DS3 interface See Table 60 for the DS3 interface specifications. See Figure 220 for the asynchronous DS3 format template. The template specifies the signal waveshape boundaries. DS3 waveshape at the DSX must fit within the template bounds. See Figure 221, Figure 222, and Figure 223 for DS3 jitter characteristics.

10.6

Control interface One RJ-45 connector on the Core-E and CorEvo cards provide access to the NMS (MGMT) Craft port. Optionally, Core-E and CorEvo 10/100/1000 BaseT Ethernet interface port 4 can be configured for TMN Ethernet interface. Caution: Half duplex capabilities are not available for the CorEvo card. The TMN interface on User Port#4 performs auto-negotiation advertising only Full-Duplex capability. Any hub or switch not supporting or not being configured to work in Full-Duplex configuration must be removed or re-configured in order to work with the TMN Port#4 interface of the CorEvo.

Optionally, Core-E and CorEvo 10/100/1000 BaseT Ethernet interface ports 1 through 4 and/or GigE SFP ports can be configured to support In-band TMN VLAN traffic.

526


10.6.1 Table 59


DS1 interface

DS1 interface specifications

ITEM

CHARACTERISTICS

Location

DS1 connectors on P32E1DS1 card equipped in MSS-8 shelf

Function

Couples DS1s into and out of P32E1DS1 card equipped in MSS-8 shelf

Capacity

32 unprotected DS1s per P32E1DS1 card 32 protected DS1s per pair of P32E1DS1 cards

Frequency

1.544 Mb/s ±32 pulse position modulation (ppm)

Line code

AMI (bipolar) with B8ZS coding

Line impedance

100 ohms ±5%, balanced

Level

Measured with all 1's signal in 3 kHz bandwidth centered at 772 kHz into100 ohms ±5%

Input @ 772 kHz

+12.6 to +17.9 dBm at equal-level point plus attenuation of 0 to 655 ft of cable

Output @ 772 kHz

+12.6 to +17.9 dBm at equal-level point after attenuation of 0 to 655 ft of cable

Output @ 1.544 MHz

More than 29 dB below level at 772 kHz

Pulse shape: Output

Complies with GR-499-CORE. Meets DS1 format template requirements (see Figure 216).

Cable type

Twisted-pair cable, typical 22 AWG ABAM. Complies with ANSI T1.102-1993

Maximum cable length

660 ft from defined DSX-level point

527


Figure 216

528

DS1 format template



Figure 217

DS1 input jitter accommodation

Figure 218

DS1 jitter transfer characteristics

Figure 219

DS1 jitter measurement filter characteristics


529


10.6.2 Table 60


DS3 interface

DS3 interface specifications

ITEM

CHARACTERISTICS

Location

Mini-BNC connectors on the P2E3DS3 card equipped in the MSS-8 shelf

Function

Couples DS3s into and out of P2E3DS3 card

Capacity

1 to 2 full-duplex DS3 ports per P2E3DS3 card

Frequency

44.736 Mb/s ±20 ppm

Line code

AMI (bipolar) with B3ZS coding

Format

Asynchronous framed DS3 per ANSI T1.107-1997 standard. See Figure 220. DS3 C-bit parity with C-bit mode operation per ANSI Standard T1.107a (R5.0)

Line impedance

75 ohms +5%, unbalanced

Level

Measured with all 1's signal and 3 kHz bandwidth into 75 ohms +5%

Input @ 22 MHz

-1.8 to +5.7 dBm at equal-level point less attenuation of 0 to 450 ft of cable

Output @ 44 MHz

More than 20 dB below level @ 22 MHz

Pulse shape: Output

Compliant with GR-499-CORE. Meets DS3 format template requirements (see Figure 220).

Cable type

75 ohm BNC coaxial cables, 728A

Mating connector type

Mini-BNC male

Jitter

All measurements are made on a half-duplex cross-connection.

Input accommodation

See Figure 221.

Output transfer

See Figure 222.

Generation

0.5 unit interval (UI) p-p nominal 0.7 unit interval (UI) p-p maximum Filter used to measure jitter must have shape shown in Figure 223.

530


Figure 220


Asynchronous DS3 format template

531



Figure 221

DS3 input jitter accommodation

Figure 222

DS3 jitter transfer characteristics

Figure 223

DS3 jitter measurement filter characteristics

-20 dB/DECADE

-20 dB/DECADE

10 Hz

300 kHz LOG FREQUENCY 25498

532


Figure 224


Combined STS-1 and DS3 Format Template

533


534



Graphical User Interfacedescriptions

Graphical User Interface descriptions

•

WebEML craft terminal overview

•

NEtO Servers Manager Tool overview

•

Summary Block Diagram overview

•

Performance Monitoring Suite overview

•

WT CLI tool overview

•

Provisioning Tool overview

•

Web Server overview

•

WebCT overview

•

Microwave Craft Terminal overview

535

Release 7.0.0 3DB 19383 ACAA Issue 01 Graphical User Interfacedescriptions

536




11 WebEML craft terminal overview 11.1

Introduction This chapter provides an introduction to the WebEML craft terminal. Defines the various page layouts, navigation, and resources available to quickly monitor the condition of a 9500 MPR radio. This chapter describes the screens. See the Nokia 9500 MPR WebEML User Manual for configuration information. The WebEML craft terminal is used to provision and monitor the MSS shelves. Navigation of the WebEML craft terminal is independent of MSS shelf type. All the examples contained in this manual reference the MSS-8 shelf.

11.2

Network Element Overview The Network Element Overview (NEtO) is the starting point of the WebEML application. NEtO functions require the NE IP Address. Only one NE can be managed in a NEtO session. The User Interface is provided by the NEtO Main View described below.

11.2.1

Main view

When NEtO starts, the main view screen is shown in Figure 225.

537

Release 7.0.0 3DB 19383 ACAA Issue 01 WebEML craft terminal overview

Figure 225


NEtO main view: initial screen

Menu Bar

25748

This screen has the following specific areas: •

NE Configuration area: displays NE general information (left side);

•

Status & Alarms area: reports supervision status and alarms (right side);

•

Discovered NEs: in the lower part is shown the list of the discovered NEs. With a double click on a row the IP address of the NE in the row automatically is written in the NE Info field

The Show and Alarm Monitor buttons are enabled when a NE is supervised only. Supervision starts as soon as the operator writes an IP address in the specific field and clicks on the OK button. Note: For more information on the Alarm Monitor application refer to Diagnosis > Alarms in the NE.

The NEtO Main view can also be reduced by using the shrink glass button in the Bar Menu.

Figure 226 shows the reduced NEtO view, allowing the operator to save screen space while continuously checking supervision and alarms status. Gray icons mean that supervision is not active. The magnifying glass button allows to show the normal NEtO main view (see Figure 225).

538



The alarm severity icon (shown in Figure 225 and Figure 226) appears in the operating system tray bar, close to the system clock and other system software icons. Figure 226

NEtO main view: reduced screen

This icon also has a specific tooltip, visible when mouse cursor is moved over it, that will show: name of application, NE IP address, and highest severity alarms number. The tray-bar icon is present in the Windows system bar (in the lower part of the screen). The tray-bar icon takes the color of the most severe alarm. The tray-bar icon is not interactive and does not present any menu or executable command if clicked either with left or right mouse button.

11.2.2

NE Configuration area The panel is divided in three sections: 1. NE Info section, containing information related to NE addressing; 2. NE Description section, with information about NE characteristics; 3. Command Buttons section, providing buttons to manage NEtO functions.

11.2.2.1

NE Information This area is related to wanted NE identification (Figure 227).

539


Figure 227


NEtO NE Configuration View: NE Information

"IP Address or DNS name" field: insert the NE IP address or DNS name, if the network can provide this facility. "OK" button will start supervision on specified NE, if reachable. Keyboard shortcut "Alt + o" behaves as clicking on "OK" button with mouse. If the IP address is correct, you can also start the supervision process by pressing the Enter key on the keyboard.

11.2.2.2

NE Description This area contains some parameters displaying general information about the supervised NE (Figure 228).

Figure 228

NEtO NE Configuration View: NE Description

Note: If you are connected to an ETSI equipment the type is 9500 MPR-E. If you are connected to an ANSI equipment the type is 9500 MPR-A.

Parameters can be read and modified (and applied to NE using the Apply button). The Type and Version parameters are retrieved from the NE. The Site Name, Site Location, Latitude and Longitude can be configured as needed. Note: The Site Name and Site Location fields must not include the special characters (\ / : * ? < > |).

540



Changing the values of the labels will also automatically update NEtO window title content: the window title will always contain the Site Name of a supervised NE. The keyboard shortcut Alt + a behaves the same as clicking on the Apply button.

11.2.2.3

Command Buttons Figure 229 shows command buttons available through NEtO.

Figure 229

NEtO NE Configuration View: Command Buttons

The Show button will start WebEML (JUSM/ WebEML) application on a supervised NE. The Alarm Monitor button starts the Alarm Monitor application. The WTPMS button starts the WT Performance Monitoring Suite application. The Show and Alarm Monitor buttons are enabled when NE is supervised only. The Exit button will close NEtO, stopping a possibly running supervision and closing all related applications. The following keyboard shortcuts can be used:

11.2.3

•

Alt + S: Show button

•

Alt + m: Alarm Monitor button

•

Alt + E: Exit button

Status & Alarms area Information on supervision status and active alarms are shown in this area (Figure 230).

541


Figure 230


Main View: Status & Alarms

Round-shaped icons change their colors according to current NEtO functions and situation. With respect to Supervision status: •

green color means that supervision function is ongoing,

•

red color means that NE link does not work,

•

gray icons mean that supervision is not active (to be started).

Alarm synthesis contains the list of the alarms listed by severity: whether an icon is not gray, means that such kind of severity contains one alarm at least.

542



The round-shaped icons change the color and the letter inside according to the severity of the active alarms: •

orange (letter M): Major alarm

•

yellow (letter m): Minor alarm

•

blue (letter W): Warning alarm

Note: The Indeterminate alarms are not supported.

11.2.4

Supervision Function The supervision function allows the operator to register a new manager inside the NE MIB and perform cyclic (periodic) monitoring on the connection. To start supervision, specify the NE IP address in the IP Address field and click on the OK button. If supervision succeeds, the screen is updated with information retrieved from the NE and supervision icon changes its color from gray to green. When a supervision error, a link down or other problems arise during supervision, the icon will become red. The Alarm Synthesis area will also be updated. Click on the Show button, to open WebEML (JUSM/ WebEML) for MPR equipment. To close an ongoing supervision, click on the Exit button (this will also close NEtO) or change NE IP address and click on the OK button to start the supervision procedure on a different NE (this will stop previous supervision).

11.2.5

Bar Menu NEtO can manage and organize a list of favorite NEs by showing operator a table containing such data.

The New icon (Figure 231) allows the operator to create a new NE list. The Open icon (Figure 232) allows the operator to open a previously saved file containing a list of NEs. For information about managing NE lists, see the 9500 MPR WebEML User Manual.

543



Figure 231

New icon

Figure 232

Open icon

Figure 233 shows the CS (Community String) icon. For information about the Community String, see the 9500 MPR WebEML User Manual. Figure 233

11.3

CS icon

WebEML main view The main view is the entry point of the application and provides the basic diagnostic and configuration functions. The main view shows a high level overview of the areas on the main screen. Different Main views are shown according to MSS shelf type:

544

•

MSS-8 Shelf, (Figure 234)

•


•


•

MSS-O unit, (Figure 237)


Figure 234


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

545


Figure 235


MSS-4 Main view


Resource Tree Area

Resource List Area


23714

546


Figure 236


MSS-1 Main view


Resource Tree Area

Resource List Area


23157

547


Figure 237


MSS-O Main view


Resource Tree Area

Resource List Area


24399

The main screen is comprised of the following areas.

11.3.1

•

Main menu bar area

•

Tab panels

•

Main toolbar area

•

Resource tree area

•

Resource list area

•

Resource detail area

•

Severity Alarm Synthesis area

•

Domain Alarm Synthesis area

•

Status Control area

Main menu bar area

The main menu bar area allows the management of the 9500 MPR NE resources function to access all the menu options, performing all the configuration and supervision functions of the Network Element. See Figure 238.

548


Figure 238


Main menu bar

The main menu bar has the following drop-down menus:

11.3.2

•

Views

•

Configuration

•

Diagnosis

•

Supervision

•

SW Download

•

Equipment

Tab panels Each tab panel represents a set of functions. Each tab panel consists of three areas: See Figure 234. •

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.

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.

Each tab panel is the entry point of the application and provides basic diagnostic and configuration functions. The following tabs are available: •

Equipment: for Equipment configuration −

Alarms

−

Settings

−

Remote Inventory (not available for MSS-1 or MSS-O)

•

Summary

•

Protection Schemes: −

Provisioning

549


− •


Protection Switching

Synchronization: −

Alarms

−

Provisioning

−

Status

•

Connections

•

NE Neighbors

From the equipment tab the following main views are available: •

AUX view, for Auxiliary channel domain (double-click on the AUX peripheral unit)

•

Core view, for Core and Ethernet domain and MPT ODU and MPT-HL/HLC radio domain (double-click on a Core-E, CorEvo, or MSS/CORE unit)

•

EAS main view: for Ethernet domain and MPT ODU and MPT-HL/HLC radio domain (double click on a P8ETH or EASv2)

•

MPT main view: for MPT ODU radio domain (double-click on a MPT Access unit)

•

PDH view: for PDH domain (double-click on a PDH unit)

•

Radio view: for Radio domain (double-click on a Radio)

The summary tab view displays only the resource list area and shows all provisioned equipment. This tab allows the operator to launch the Alarm Monitor Tool and view equipment tool tips. MPT-HLS units do not appear on the Summary tab. From the Protection Schemes tab the following operations are available: •

Provision protection schemes: −

Revertive

−

Non-revertive

•

View protection switch status

•

Perform manual protection switching: −

Equipment Protection Switching (EPS)

−

Hot StandBy Protection Switching (HSB)

−

Rx Radio Protection Switching (RPS)

From the Synchronization tab the following operations are available: •

550

Provision synchronization



•

View synchronization status

•

View synchronization alarms

From the Connections tab cross-connection details are available. The NE Neighbors tab shows the remote NEs that are connected to the local NE through a radio interface. The radio interface can be an MPT ODU, an MPT-HL/HLC/ HLS, or a LAG. The IP address of the remote unit is provided by the remote unit in IPv4 or IPv6 according to the enabled IP stack on the remote unit. By default, the IP address is 0.0.0.0 (IPv4) or 0:0:0:0:0:0:0:0 (IPv6). The Remote Port column provides the port number of the unit on the other end of the hop. If the other end is a LAG, the Remote Port column shows the LAG ID. The Remote Site Name column provides the name of the remote side, if available. The list can be printed or exported to a file. The default file name is neighbors.csv.

11.3.3

Main toolbar area This main toolbar area contains a selection of quick-access icons to access common features. See Figure 239.

Figure 239 Previous View

Zoom

Main toolbar area Next View

NE Inventory

Summary Block Diagram View

Segregated Ports View

CrossConnections

LAG Configuration View

Ethernet QoS Ring Configuration Configuration View View

ETH OAM Configuration View

XPIC Configuration

VLAN Configuration

WT Performance Monitoring Tool 24369

The main toolbar area has the following quick-access icons: •

Previous View

•

Zoom

551


11.3.4


•

Next View

•

Summary Block Diagram View (not available with the CorEvo)

•

NE Inventory

•

Cross-Connections

•

Segregated Ports View

•

Ethernet Ring Configuration View

•

LAG Configuration View

•

QoS Configuration View

•

ETH OAM Configuration View

•

XPIC Configuration

•

Auxiliary Cross-Connections (ETSI market only)

•

VLAN Configuration

•

WT Performance Monitoring Tool

Resource tree area Resource tree area displays all the available resources of the Radio NE in a tree structure. See Figure 240.

552


Figure 240


Resource tree area

Each tree node consists of two symbols. The first symbol indicates the state of the structure, for example, if the symbol has a + the tree can be expanded to a lower level. The tree structure can be collapsed if the symbol is a -. Finally, if there is no symbol, the node represents a leaf. The second symbol is the graphical representation of the resource. The user must select the resource by clicking with the mouse to carry out an action that depends on the type of click and the resource detail area related to the selected element that is displayed. Each resource listed may be selected by using the mouse with a single click or a double-click. Click: single left mouse click highlights the resource. This selection causes the activation of the resource list area, for example, every time the user selects a resource in the resource tree area the corresponding tabular or graphical representation is displayed in the resource list area. Double-click: double left mouse click expands the tree structure and activates the resource list area displaying the same information described above. When the tree node is expanded, a double-click will collapse the tree node showing the same information in the resource list area.

553


11.3.5


Resource list area The resource list area provides a graphical view of the NE. Additional resource function to access additional menu for performing configuration and supervision functions of the Network Element. See Figure 241.

Figure 241

Resource list area

11.3.6

Resource detail area The resource detail area allows the management of the 9500 MPR NE resources function. See Figure 242. Available tab panels in the resource detail area are as follows:

Figure 242

•

Alarms

•

Settings

•

Remote Inventory (available for MSS-4/MSS-8 only)

Resource detail area

Include alarms from sub-nodes check box, when enabled (checked) includes active alarms for the sub-nodes of the selected object.

554


11.3.7


Severity Alarm Synthesis area The Severity Alarm Synthesis Area 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. See Figure 243.

Figure 243

Severity Alarm Synthesis area

There are six different alarm severity levels. These different levels are associated with colors as follows: •

Green: Normal condition

•

Red: Critical alarm (C)

•

Orange: Major alarm (M)

•

Yellow: Minor alarm (m)

•

Cyan: Warning alarm (W)

•

White: Indeterminate (I) 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, Module view or Port view) so that the operator is always aware of the alarms occurring in the system. An alarm icon colored green indicates that no alarms of the type defined by the icon is occurring. See Figure 243, Critical and Indeterminate. An alarm icon with a associated letter inside (and a number at the bottom of the icon) indicates that alarms of the number and the type defined by the icon are occurring. See Figure 243, Major, Minor, and Warning. An alarm icon grayed out indicates that a spontaneous incoming alarm notification has been inhibited.

555


11.3.8


Domain Alarm Synthesis area The domain alarm synthesis area provides an alarm functionality that informs the operator on the domain of the different alarms in the NE as well as on the number of current alarms. There are different alarm domain types according to the different domains in which the NE can be subdivided (example: External (EXT), Equipment (EQP), Transmission (TRS)). See Figure 244.

Figure 244

Domain Alarm Synthesis area

The color corresponds to the highest severity among the set of active alarms for the relevant domain. There are six different alarm severity levels. These different levels are associated with colors as follows: •

Green: Normal condition

•

Red: Critical alarm (C)

•

Orange: Major alarm (M)

•

Yellow: Minor alarm (m)

•

Cyan: Warning alarm (W)

•

White: Indeterminate (I) Not operative.

Each domain alarm is represented by an alarm icon situated in the top right hand corner of the view. These alarm icons are constantly represented on the different domain types so that the operator is always aware of the alarms occurring in the system. The shape of the alarm icons in the alarm panel gives an indication of alarm occurrence. An alarm icon colored green indicates that no alarms of the type defined by the icon are occurring. See Figure 244. An alarm icon with a associated letter 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. See Figure 244. An alarm icon grayed out indicates that a spontaneous incoming alarm notification has been inhibited.

556


11.3.9


Status Control area The Status Control Area provides different management states concerning the NE and are represented via icons located to the right of the resource list area. See Figure 245.

Figure 245

Status Control area

See Table 61 for the seven management status icon and color definitions.

557


Table 61


Status Control icon definitions

DESCRIPTION

LOCAL ACCESS STATE: Indicates operational status for the terminal to manage the NE.

ICON

STATUS

Indicates that the craft terminal has the OS permission to manage the NE (granted)

Indicates the craft terminal requested OS permission to manage the NE (requested)

Indicates that the craft terminal does not have the OS permission to manage the NE (denied)

COMMUNICATION: Indicates the operational status of the connection between the NE and the OS (SDH service link)

Indicates the “Enable” operational state of the connection between NE and the terminal (SDH service link up)

SUPERVISION: Indicates whether the NE is under OS supervision

Indicates the NE is under supervision

Indicates the “Disable” operational state of the connection between NE and the terminal (SDH service link down)

Indicates the NE is not under supervision. Used in the OS

OPERATIONAL SYSTEM ISOLATION: Indicates operational status of the NE to be managed by the 1353SH.

558

Indicates the User State is unblocked

Indicates the User State is blocked


Table 61


Status Control icon definitions (Continued)

DESCRIPTION

ICON

NETWORK TIME PROTOCOL SERVER STATUS: Indicates the operational status of the Network Time Protocol.

STATUS

NTP server disabled

Both servers are reachable

Neither server is reachable

Only one server is reachable

ABNORMAL CONDITION: Indicates the status of Abnormal Conditions present on the NE

11.3.10

Normal operating condition

Detection of an Abnormal operative condition exist on the NE

Scroll bar

On some views, there are more parameters required than can be displayed on one screen height. In these cases the pane has been divided with a scroll bar. To view the hidden parameters, slide the scroll bar up or down accordingly. See Figure 246 for an example of how the scroll bar appears on the display. To view an example in the craft terminal, open the radio main view for a radio direction and select Adaptive Modulation in the Mode drop-down menu.

559


Figure 246


Scroll bar

11.3.11

Selection criteria

Each tree node consists of up to three symbols and a label. The first optional symbol indicates tree structure state: •

if symbol is "+", tree structure can be expanded

•

if symbol is "-", tree structure can be collapsed

•

if no symbol exists, tree structure 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. The operator can select a resource by selecting with mouse to perform the action dependent on click type. The resource detail area related to the selected item is displayed. Each resource listed above may be selected using the mouse:

11.3.11.1

•

Single left click

•

Double-click

Single left click Single left click on a resource in the resource tree area initiates the following action:

560


11.3.11.2


•

highlights the resource in the resource tree area

•

highlights the resource in the resource detail area

•

displays the associated resources in the resource list area

Double-click Double-click on a resource in the resource tree area initiates the following action:

11.3.11.3

•

if the tree structure is collapsed, then expands the associated tree structure

•

if the tree structure is expanded, then collapses the associated tree structure

Button policy The available buttons are as follows:

11.4 11.4.1

•

Apply: applies or writes the modified parameters to the Core card

•

Cancel: closes the window without applying or writing the modified parameters to the Core card

•

OK: applies or writes the modified parameters to the Core card and closes the window

•

Refresh: refreshes or repaints the window to the parameters stored on the Core card

•

Close: closes the window

PDH main view General information The PDH domain view allows the operator to manage the E1, DS1, or DS3 streams. See Figure 247. To open this view, double click on a PDH card.

561


Figure 247


PDH main view (ETSI market shown)

Resource Tree Area: displays the tributary ports sorted by the channel number

Resource List Area: displays tabular information about the selected resource in the tree area

Resource Detail Area: displays through tab windows, the selected object’s properties in list area. This area performs the available functions for involved resource

22998

This domain view consists of the following areas: •

Resource Tree Area: displays the PDH ports sorted by channel number.

•

Resource List Area: displays tabular information about the selected resource in tree area.

•

Resource Detail Area: displays, through tab windows, the object’ s properties selected in list area. This area enables to execute the available functions for involved resource.

Two tab panels are present in the Resource Detail Area:

562

•

Alarms & Settings: shows the active alarms and allows to configure the E1 streams

•

Loopback: activates the loopbacks available with the equipment.


11.4.2


Alarms & Settings In the Resource List Area is given the information related to the tributaries: 1. Port Number - User Label: port number and label for a given channel and type of port 2. Signal Mode: type of frame (Unframed/Framed/Disabled) 3. Flow Id: identifier of the tributary for the cross-connection 4. Service Profile: possible profile to be associated with the tributary (TDM2TDM/TDM2Eth) 5. Payload Size: bytes of the payload (256) 6. TDM Clock source: type of the clock to be associated with the tributary (Adaptive/Differential/Node Timing) Note: The selection of TDM clock source (clock recovery type) as to be common for all the E1 belonging to the same card, independently if the node timing has been enabled in the same NE, it is possible to mix a PDH card with E1s set in DCR and a PDH card with E1s set in ACR. Of course the NODE TIMING must be used correctly

Note: Columns 5, 6, 7 and 8 are only available if the Service Profile is TDM2Eth.

For every tributary two tab-panels are available:

11.4.2.1

•

Alarms

•

Settings

Alarms tab-panel The Alarms tab panel provides the fault management, which checks the current state of alarms related to the selected object. The alarm tab panel has one row for each possible alarm, but only rows related to the active alarms are highlighted. When the alarm disappears it is automatically cleared in the screen. By putting a tick in the Include alarms from sub-nodes box the alarms currently active in the sub-nodes of the object will also appear.

563



For every alarm the following information is given:

11.4.2.2

•

Severity: the severity associated with the alarm and assigned in the Alarm Profile

•

Event Time: the time of the generation of the alarm

•

Entity: the entity involved in the alarm

•

Probable Cause: the probable cause of the alarm

•

Managed Object Class: the class of the alarm.

Settings tab-panel This tab-panel performs all available functions for a tributary port. The managed tributary types are: E1 in the ETSI market and DS1 or DS3 in the ANSI market. To define the involved ports, the interface selection in the tree view is first required; therefore the selection of the desired tributary port in the tabular view enables the Resource Detail list to show the available functions for the single one resource. Warning: To change something in the Settings tab-panel first change the Signal Mode to Framed/Unframed. Then, all the other fields can be changed.

Figure 248

Settings tab-panel

The following buttons appear on the Settings tab for all tributaries:

564

•

Apply: the configuration for the selected E1 tributary will become active

•

Apply to All: the configuration present in the screen will be applied to all the ports.

•

Help: Click on this button to open the online help.


11.4.2.2.1


E1 tributary

In the Setting tab-panel for an E1 tributary the following fields appear: •

Port Number: identifies the ports for a given interface and type of port (readonly fields)

•

User Label: user configurable

•

Flow Id: Flow identifier value (2 to 4080)

Caution: The Flow Id must be unique in the MPR network.

•

Signal Mode: The possible values are: −

Unframed for the unframed received signal

−

Framed for the collection of the performances at the input in Tx side and at the output in Rx side

−

Disabled

The current state can be modified selecting a different signal mode value, then click on the “Apply” button to send the new value to NE. •

Service Profile: The possible profiles are: −

TDM2TDM

−

TDM2Eth

Fields ECID Tx, ECID Rx, Payload Size and TDM Clock Source can be written only if the Service Profile is TDM2Eth. Note: With the TDM2TDM service profile the TDM Clock source is fixed to Differential (RTP - Real Time Protocol is used); with the TDM2Eth service profile the TDM Clock source can be Differential (RTP - Real Time Protocol is used) or Adaptive (RTP is not used). In the unit it is not possible to have mixed configurations with service profiles using RTP and other service profiles not using RTP. Example: if in the unit only one E1 has service profile TDM2TDM it is possible to configure other E1 with service profile TDM2Eth only with the Differential clock source (not with the Adaptive clock source). If the Adaptive clock source is requested the E1 must be connected to another PDH unit.

Alarm profile: Not implemented.

565


11.4.2.2.2


DS1 tributary

In the Setting tab-panel for a DS1 tributary the following fields appear: •


•


•

Line Length: length in feet to the cross-connect point

•

Line Coding: AMI or B8ZS

•



•



−

Framed SF for the DS1 Super Frame received signal

−

Framed ESF for the DS1Extended Super Frame received signal

−

Disabled



TDM2TDM

−

TDM2Eth

Fields ECID Tx, ECID Rx, Payload Size and TDM Clock Source can be written only if the Service Profile is TDM2Eth. Note: With the TDM2TDM service profile the TDM Clock source is fixed to Differential (RTP - Real Time Protocol is used); with the TDM2Eth service profile the TDM Clock source can be Differential (RTP - Real Time Protocol is used) or Adaptive (RTP is not used). In the unit it is not possible to have mixed configurations with service profiles using RTP and other service profiles not using RTP. Example: if in the unit only one E1 has service profile TDM2TDM it is possible to configure other DS1 with service profile TDM2Eth only with the Differential clock source (not with the Adaptive clock source). If the Adaptive clock source is requested the DS1 must be connected to another PDH unit.

566




11.4.2.2.3

DS3 tributary

In the Setting tab-panel for a DS1 tributary the following fields appear: •


•


•

Line Length: length in feet to the cross-connect point

•

AIS signal type: Blue Signal (G.704) or All Ones

•



•



−

Framed for the Frame received signal

−

Disabled



TDM2TDM

−

TDM2Eth

Fields ECID Tx, ECID Rx, Payload Size and TDM Clock Source can be written only if the Service Profile is TDM2Eth.

567



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


11.4.2.3

General information on Circuit Emulation 9500 MPR-E performs Circuit Emulation on PDH TDM flows, then transports those "TDM packets" mixed to native Ethernet frames. The Circuit Emulation IWF (inter-working function) is according the Metro Ethernet Forum implementation agreement known as MEF 8, limited to the structure agnostic case. MEF 8 emulated circuits is based on exchange of service parameters between two CES IWFs at either end of the emulated circuit; if one of those IWFs belong to the 9500 MPR-E the following parameters are defined: •

MAC addresses of the two IWFs

•

Payload size

•

ECID (2 different values may be used for each direction). It is suggested to set ECID Tx and ECID Rx with the same value of the Flow Id.

•

TDM clock source

•

−

adaptive

−

differential

−

node timing

VLAN (One Vlan is assigned to each bi-directional circuit emulated E1 flow)

Two different cases of Circuit Emulation services are implemented: 1. TDM2TDM 2. TDM2ETH

568



TDM2TDM Both the IWFs belong to 9500 MPR-E and the packets are not supposed to go out the 9500 MPR-E network. The IWF parameters listed above, have predetermined values and don’t need to be provisioned. •

MAC addresses are determined as consequences of the cross connections.

•

Payload size: fixed to 121 bytes

•

ECID will be the same value as Flow Id

•

TDM clock source: differential, node timing

•


TDM2ETH Only one of the IWFs belongs to 9500 MPR-E and the packets are supposed to go out the 9500 MPR-E network.

11.4.3

•

MAC addresses: in all involved nodes are determined as consequences of the cross connections; the only exception is the Ethernet Terminal Node (the node where that TDM2ETH traffic goes through an user Ethernet port). In such ETN the source address will be the node Mac address, the destination mac address will be provisioned by ECT/NMS.

•

Payload size: fixed to 256 bytes

•

ECID: provisioned by ECT/NMS, 2 different values may be used for each direction

•

TDM clock source will be provisioned by ECT/NMS: adaptive, differential, node timing

•

Flow Id will be provisioned by ECT/NMS (One Vlan is assigned to each bidirectional circuit emulated E1 flow)

Loopback The functions described in this section allow to perform the test operations using loopbacks. Note: The loopbacks can be activated on the local NE only

569



In the Resource List Area are listed all the loopbacks which can be performed. In this area the following information is given: 1. Interface: number of the channel and type of the loopback 2. Direction: type of the loopback 3. Activation: activation status of a loopback (Active/Not Active) 4. Activation date: date of loopback activation 5. Timeout: timeout period, if has been set. Figure 249

570

E1 Loopbacks


11.5 11.5.1


SDH main view General information on the SDH unit The SDH main view allows the operator to manage STM-1/OC-3 streams. To open the SDH main view, double click on an SDH card.

11.5.1.1

Tab-panels Two tab-panels are present:

11.5.2

•

Alarms: shows the active alarms

•

Settings: allows to configure the STM-1 interface.

Alarms The Alarms tab panel provides the fault management, which checks the current state of alarms related to the selected object. The alarm tab panel has one row for each possible alarm, but only rows related to the active alarms are highlighted. When the alarm disappears it is automatically cleared in the screen. By putting a tick in the Include alarms from sub-nodes box the alarms currently active in the sub-nodes of the object will also appear. For every alarm the following information is given: •


•


•


•


•


571


11.5.3


Settings for SDHACC unit (Transparent mode) This tab-panel allows to configure the STM-1/OC-3 signal.

Figure 250

Settings for SDHACC in transparent mode

11.5.4

Loopback The functions described in this section allow to perform the test operations using loopbacks. Note: The loopbacks can be activated on the local NE only

In the Resource List Area are listed all the loopbacks which can be performed.

572



In this area the following information is given: 1. Interface: number of the channel and type of the loopback 2. Direction: type of the loopback 3. Activation: activation status of a loopback (Active/Not Active) 4. Activation date: date of loopback activation 5. Timeout: timeout period Figure 251

SDH Loopbacks

11.5.5

Settings for SDHCHAN unit (Channelized mode ETSI market only) This tab-panel allows to configure the STM-1 signal.

573


Figure 252


Settings for SDHCHAN in channelized mode

The E1 tab-panel performs all available functions for the tributary. To define the involved ports, the interface selection in the tree view is first required; therefore the selection of the desired tributary port in the tabular view enables the “Resource Detail list” to show the available functions for the single one resource. Warning: To change something in the Settings tab-panel first change the Signal Mode to Unframed or Framed. Then, all the other fields can be changed.

In the Setting tab-panel there are the following fields: Port Number: identifies the ports for a given interface and type of port (read-only fields).

574


11.5.5.1


Signal Mode

The possible values are: •


•

Framed for the collection of the performances at the input in Tx side and at the output in Rx side

•

Disabled

The current state can be modified selecting a different signal mode value, then click on the “Apply” button to send the new value to NE.

11.5.5.2

Service Profile

The possible profiles are: •

TDM2TDM

•

TDM2Eth

Flow Id: To implement cross-connections between line side and radio side each E1 tributary must be associated with an identifier. Enter the Flow identifier value in the relevant field (possible values: 2 to 4080) and press Apply. Fields ECID Tx, ECID Rx, Payload Size and TDM Clock Source can be written only if the Service Profile is TDM2Eth. Note: The service profile must be the same for all the E1s.

Alarm profile: Not implemented now.

11.5.5.3

Buttons Apply: the configuration for the selected E1 tributary will become active Apply to All: the configuration present in the screen will be applied to all the ports. Help: by clicking on this button the operator calls the help on line.

575


11.6 11.6.1


EAS main view for P8ETH and EASv2 EAS Domain This section describes the function types offered to the operator in order to navigate the EAS domain. The EAS (Ethernet Access Service) domain contains multiple views: •

P8ETH or EASv2, displaying functions associated with the 8 Ethernet Interfaces.

•

Power Source (EASv2 only), displaying functions associated with the 4 PFoE ports

•

Port#s.p, displaying functions associated with Radio Interface directions (slot.port).

A Port# view is present for each Radio Interface that has been enabled in the unit (refer to the Equipment menu). Click on the associated view icon to select the view. See Radio view for details on the Port# views. The main view contains a single tab-panel: •

Ethernet Physical Interface

Note: The Ethernet ports can be members of a VLAN, but they cannot be cross-connected (no TDM2TDM or TDM2Eth cross-connection can be implemented).

This domain view consists of the following areas:

576

•

Resource Tree, displaying Ethernet physical interface with related port number;

•

Resource List, displaying tabular information about tributaries in tree area;

•

Resource Detail, providing access to EAS Ethernet Interface detail view “Alarms” and “Settings”.


11.6.1.1 Figure 253



EAS Main view for P8ETH

577


Figure 254


EAS Main view for EASv2

The Ethernet Port#5 to Port#8 will only appear if optional SFP plug-ins have been enabled in the unit (refer to the Equipment menu). This tab-panel refers to the Ethernet ports, which can be used as traffic ports. It includes the following tab-panels for each Ethernet port:

11.6.1.1.1

•

Alarms tab-panel

•

Settings tab-panel

•

Provider Bridge tab-panel

•

Policy & Translation tab-panel

•

Per-VLAN Per-CoS Rate Limiter tab-panel

Alarms tab-panel

The “Alarms” view shows the Ethernet port-related alarms. Select the node in the Tree area to check the current state of the Ethernet tributary alarms.

578


11.6.1.1.2


Settings tab-panel

For Ethernet Port#1 to Port#4 Figure 255

Settings tab panel for EASv2 port#1 to port#4

This Settings view performs all the available functions for Ethernet electrical tributary ports. Information related to a data port configuration is provided by the following parameters: •

User Label (User configurable)

•

Port Status (Enabled or Disabled);

•

Auto-Negotiation Status (Enabled or Disabled);

•

Flow Control (Enabled or Disabled);

•

Configuration (“Other” / “Configuring” / “Complete” / “Disabled” / “Parallel Detect Fail”) all read-only;

•

Advertised Capability (“10 Mb/s – Half Duplex”, “10 Mb/s – Full Duplex”, “100 Mb/s – Half Duplex”, “100 Mb/s – Full Duplex”, “1000 Mb/s – Full Duplex”). Note that the 1000 Mb/s Capability can only be selected when AutoNegotiation is enabled;

•

VLAN configuration. The traffic, received on each user Ethernet port, can be untagged or tagged. For each port it is possible to configure: −

Acceptable Frame Type: •

Admit tagged only (only tagged frames are allowed in ingress; the untagged frames are dropped)

•

Admit all (tagged and untagged frames are allowed in ingress)

•

Default value: “Admit all”.

579


−


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

Note: Untagged frames The untagged frames received on one user Ethernet port, configured as “Admit tagged only”, are dropped.

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

•

Synchronous Ethernet Operation Mode (EASv2 only) From an Ethernet traffic interface configured at 1000 Mb/s, you can recover the physical Rx synchronization signal or deliver the NE clock synchronization signal. To do this the Ethernet port must be set a Synch-E Master. Synchronous Ethernet Operation Mode is required to set up synchronous Ethernet networks addressed by G.8261.

•

Alarm Profile (not implemented);

The “Restart” button forces auto-negotiation to begin link re-negotiation.

580



For Ethernet Port#5 to Port#8 Figure 256

Settings tab panel for EASv2 port#5 to port#8

This Settings view performs all the available functions for Ethernet SFP tributary ports. Information related to the port configuration is provided by the following parameters: •


•

Port Status (Enabled or Disabled): select Enabled and click on Apply to enable the port;

•


•

Auto-Negotiation Status (Enabled or Disabled): the Auto-Negotiation can be enabled or disabled;

•


•


•

Advertised Capability (“1000 Mb/s – Full Duplex”);

•




•

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

581


−


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

Note: Untagged frames The untagged frames received on one user Ethernet port, configured as “Admit tagged only”, are dropped.

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

The SFP Info field is a read-only field which displays characteristics of the SFP. Note: For electrical SFPs, the Laser Wavelength is always reported as 0 nm.

•

Synchronous Ethernet Operation Mode (EASv2 only) From an Ethernet traffic interface configured at 1000 Mb/s, you can recover the physical Rx synchronization signal or deliver the NE clock synchronization signal. To do this the Ethernet port must be set a Synch-E Master. Synchronous Ethernet Operation Mode is required to set up synchronous Ethernet networks addressed by G.8261.

The “Restart” button forces auto-negotiation to begin link re-negotiation.

11.6.1.1.3


The Provider Bridge tab-panel allows you to configure the port type for each port, if the NE is configured in 802.1ad (Provider Bridge) mode. The port can be configured as:

582



1. NNI 2. UNI (port based) 3. UNI (VLAN based) Figure 257


11.6.1.1.4


The Policy & Translation tab-panel allows to configure for each user Ethernet port the following advanced Ethernet features: 1. Port Rate Limiter (Ingress and/or Egress) 2. Storm Control (Ingress) 3. VLAN Rate Limiter (Ingress)

583


Figure 258



11.6.1.1.5

Per-VLAN Per-CoS Rate Limiter tab-panel The Per-VLAN Per-CoS Rate Limiter tab panel allows you to configure a Per-VLAN Per-CoS Rate Limiter on a User Ethernet port; see Figure 259. A Per-VLAN Per-CoS Rate Limiter can be applied to each User Ethernet port for the ingress direction. The rate limiter is applied to a tagged Ethernet flow classified according to the VLAN ID and the 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.

584


Figure 259



11.7 11.7.1

Ethernet Ring Configuration View General information The Ethernet Ring Configuration view allows the operator to manage Ethernet Ring topologies. See Figure 260. To open this view, click on the Ethernet Ring Configuration View icon ( ) from the WebEML Main View.

585


Figure 260


Ethernet Ring Configuration view

11.8 11.8.1

LAG Configuration General The LAG Configuration screen allows the operator to configure L1 and L2 Link Aggregation Groups. See Figure 261. To open this view, click on the LAG Configuration View icon ( ) from the WebEML Main View.

586


Figure 261


LAG configuration

11.9 11.9.1

QoS Configuration General The QoS Configuration menu allows the operator to configure Quality of Service. To open this view, click on the QoS Configuration View icon ( ) from the WebEML Main View. The Qos Configuration menu has 3 tab-panels: •

Scheduler Configuration, see Figure 262

•

Queue Size Configuration, see Figure 263

•

QoS Classification, see Figure 264

587


Figure 262

Scheduler Configuration

Figure 263

Queue Size Configuration

588



Figure 264


QoS Classification

11.10 11.10.1

EFM OAM Configuration General The EFM OAM Configuration menu allows the operator to configure Ethernet First Mile OAM. See Figure 265. EFM OAM provides the ability to monitor the health of the network and determine the location of failing links or fault conditions. To open this view, click on the EFM OAM Configuration View icon ( ) from the WebEML Main View.

589


Figure 265


ETH OAM Configuration

11.11 11.11.1

AUX Cross Connections General The AUX Cross Connections menu allows the operator to configure AUX cross connections. See Figure 266. To open this view, click on the AUX Cross Connections icon ( ) from the WebEML Main View. Two types of AUX Cross-Connections can be implemented:

590

•

Local User Service Channel Cross-Connection

•

Service Channels Cross-connection in pass-through



Note: Cross-Connection towards MPT In this release cross-connection of Service Channels towards a radio direction with MPT is not supported. The operator therefore will not have the possibility to select a radio direction with MPT for such cross-connection.

Figure 266

Auxiliary Cross Connections menu

11.12 11.12.1

XPIC configuration General information The XPIC Configuration view allows the operator to configure XPIC. See Figure 267. To open this view, click on the XPIC Configuration View icon ( ) from the WebEML Main View.

591


Figure 267


XPIC Configuration view

The XPIC Configuration is available only when a mask with XPIC (with or without Adaptive Modulation) is configured in the Radio menu. For the MPT-HC/XP, the XPIC module must be present. For the MPT-HC-HQAM/XP-HQAM, MPT-HLC and MPT-HLS, the XPIC license must be present.

592


Figure 268


Settings tab with available XPIC

11.13 11.13.1

VLAN management General information The VLAN Management view allows the operator to configure VLANs. To open this view, click on the VLAN Management icon ( ) from the WebEML Main View.

593


Figure 269

802.1D VLAN management

Figure 270

802.1Q VLAN management (default VLAN only)

594



Figure 271


802.1ad VLAN management with LAG

11.14 11.14.1

WT Performance Monitoring Suite General information The WT Performance Monitoring Suite provides PM measurements for Ethernet, Radio, PDH, and IMA user lines. To open the WTPMS, click on the WT Performance Monitoring Suite icon ( ) from the WebEML Main View. For more information about the screens, see Performance Monitoring Suite overview.

11.15 11.15.1

Radio view General information on the Radio domain menu To open this view double click on one of the following:

595



•

an MPT Access unit, Core unit, EAS unit, or EASv2 unit

•

an MPT ODU

The Radio domain view allows the operator to manage the resources of the radio transmission channel. The following types of Radio are available: Note: The GUI does not distinguish between MPT-HC and MPT-XP transceivers, or between MPT-HC-HQAM and MPT-XP-HQAM transceivers. The radio is labeled MPT-HC or MPT-HQAM. From a functional point of view, the HC and the XP variants are the same.

•

MPT-HC/XP

•

MPT-HC-HQAM/XP-HQAM.

•

ETSI market only:

•

−

MPT-MC

−

MPT-HLS

ANSI market only: −

MPT-HL

−

MPT-HLC

A Radio NE consists of one or two radio channels with a set of functional blocks such as tributary ports and radio ports. This domain view consists of the following areas: •

Resource Tree Area: displays the radio ports sorted by channel number.

•

Resource List Area: displays tabular information about the selected resource in tree area.

•

Resource Detail Area: displays, through tab windows, the object’ s properties selected in list area. This area enables to execute the available functions for involved resource.

The following tab panels are present in the Resource Detail Area:

596

•

Alarms: shows the active alarms

•

Settings: configures the radio parameters

•

Additional Settings: configures the radio parameters

•

Maintenance: performs maintenance and trouble-shooting functions

•

Measurements: performs the Tx and Rx power measurements.



The Power Source tab-panel is available with the MPT Access unit and EASv2 to interface MPT-HC/HC-HQAM or MPT-MC.

11.15.2

Power Source This menu is available when MPT ODUs are connected to MSS-O, MSS-1, MPT Access, and EASv2 units. Two power supply modes are available to power the MPT: 1. QMA (MPT Access unit only) 2. PFoE Two Sources are available with the MPT Access unit (shown in Figure 272), MSS-1 (shown in Figure 273), and MSS-O (shown in Figure 274). Four Sources are available with the EASv2 unit (shown in Figure 275). If the Type is Disabled no power supply is provided to the MPT. After the power supply selection click on Apply. Note: The Alarm Profile field is not supported.

597


Figure 272

598

Power Source for MPT Access unit



Figure 273


Power Source for MSS-1

599


Figure 274

600

Power Source for MSS-O



Figure 275


Power Source for EASv2

Note: An MPT-MC or an MPT-HC/HC-HQAM can be connected to an external Power Injector Box, MPT Power Unit or MPT Extended Power Unit, which add the Power Supply and the Ethernet Traffic on the same cable. In this case the Power Source Type must be Disabled.

11.15.2.1

Mode 1 - QMA (only with MPT-HC/HC-HQAM on the MPT Access unit) This mode is the default mode. In QAM mode the MPT-HC is power supplied with a dedicated coaxial cable connected on the QMA connector on the front panel of the MPT Access unit.

601


11.15.2.2


Mode 2 - PFoE (Power Feed on Ethernet) In PFoE mode the MPT-HC/HC-HQAM or MPT-MC is power supplied by using the electrical Ethernet cable. Warning: Check the MPT Access card part number before providing power supply to the PFoE port. To check the part number use the Remote Inventory facility.

11.15.3

Alarms tab The Alarms tab panel provides the fault management, which checks the current state of alarms related to the selected object. The alarm tab panel has one row for each possible alarm, but only rows related to the active alarms are highlighted. When the alarm disappears it is automatically cleared in the screen. By putting a tick in the Include alarms from sub-nodes box the alarms currently active in the sub-nodes of the object will also appear. For every alarm the following information is given:

11.15.4

•


•


•


•


•


Configuration tabs

This section provides examples of the configuration tabs for the radios. The actual appearance of the screen will depend on the configuration. For each tab, the Direction panel shows parameters for the radio direction and the Channel panel shows parameters for each individual radio. See the 9500 MPR WebEML User Manual for configuration procedures.

602


11.15.4.1


Settings The Direction panel of the Settings tab shows the following: •

User Label

•

Mode

•

XPIC Configuration (not supported with MPT-MC)

The Channel panel of the Settings tab shows the following: •

Shifter

•

Frequency

•

Power mode (MPT-HLS only)

•

ATPC Settings or Manual Transmit Power Control

The figures in this section show examples of the Settings tab for each radio. Figure 276

Settings tab with fixed modulation (MPT-HC)

603


Figure 277

604

Settings tab with fixed modulation (MPT-HQAM)



Figure 278


Settings tab with adaptive modulation (MPT-HC)

605


Figure 279

606

Settings with adaptive modulation (MPT-HQAM)



Figure 280


Settings tab with fixed modulation (MPT-MC)

607


Figure 281

608

Settings tab with adaptive modulation (MPT-MC)



Figure 282


Settings tab with fixed modulation (MPT-HL)

609


Figure 283

610

Settings tab with adaptive modulation (MPT-HL)



Figure 284


Settings tab with fixed modulation (MPT-HLC)

611


Figure 285

612

Settings tab with adaptive modulation (MPT-HLC)



Figure 286


Settings tab with fixed modulation (MPT-HLS)

613


Figure 287


Settings tab with adaptive modulation (MPT-HLS)

11.15.4.2

Additional Settings The Direction panel shows the followings: •

PPP RF

•

Synchronization

•

Encryption (available if an encryption license is present)

•

Link Identifier Configuration

•

Pkt Throughput Booster (available if a PTB license is present)

•

Alarm Profile

The figures in this section show examples of the Additional Settings tab for each radio.

614


Figure 288


Additional Settings tab (MPT-HC)

615


Figure 289

616

Additional Settings tab (MPT-MC)



Figure 290


Additional Settings tab (MPT-HL)

617


Figure 291

618

Additional Settings tab (MPT-HLC)



Figure 292


Additional settings tab (MPT-HLS)

11.15.4.3

Maintenance The Direction panel shows ACM Manual Maintenance. The Channel panel shows the following: •

Loopback

•

Tx Mute

•

Rx Squelch (MPT-HLC/HLS only)

•

MPT Temperature (read-only) −

The retrieved temperature of each MPT, in Celsius, is shown in the MPT temperature field. If the temperature cannot be retrieved, the MPT Temperature panel is dimmed.

619


•

Power Supply (read-only, MPT-HQAM only) −

• Figure 293

620


The retrieved power consumption of the MPT is shown in the Power Supply panel. If the information cannot be retrieved, the power supply panel is dimmed.

Low Voltage Alarm (MPT-HQAM only)

Maintenance tab (MPT-HC)


Figure 294


Maintenance tab (MPT-MC)

621


Figure 295

622

Maintenance tab (MPT-HL)



Figure 296


Maintenance tab (MPT-HLC)

623


Figure 297


Maintenance tab (MPT-HLS)

11.15.4.4

Measurement The Power Measurements capability is performed from of the Measurements tab panel. The Measurements screen allows the operator to set initial parameters for the required measurement. "Measurement interval" fields allow the operator to set the time duration of the measurement. The default is Days: 7, Hours: 0, Minutes: 0. A 7-day measurement interval is also the maximum allowed interval. "Sample time" field is the period between two consecutive measurement samples. The choice is among 2, 4, 6, 30, 60 sec. The last section of the dialog is referred to an optional Log file.

624



By selecting Create File the log file is created and a default path and name for this file is displayed to the operator. The file is stored in the MPRE_CT_V00.07.08 directory. The file name must not include the following characters: \ ? : * “ < > |. The log file contains the sample value and records the measurement up to a maximum dimension (7 days for a 2 s sample time). By clicking on the "Start" button the screen "Power Measurement Graphic" appears. The Power Measurement Graphic is available only if WebEML is connected to the NE. The Power Measurement Graphic screen shows the Tx and Rx measurements related to the local and remote NE. Through this screen the operator can see, in real time, the power transmitted by the local and remote transmitter (Tx) and the power received by the local and remote receiver (Rx). The top graphic screen area shows the TX curves (local and remote), while the bottom area shows the Rx curves (local and remote). Where the diversity module is present with MPT-HLS, curves are also displayed for the diversity receiver. Note that the colors represent the linked end-point of the two NE; for example, if the local TX is blue, the remote receiver will also have the same color. The top of the screen offers all the characteristics present in the current measurement: •

Radio port: gives the symbolic name associated with the radio channel being analyzed

•

Sample time: indicates the frequency used to send the measurement requests to NE;

•

Start time: is the first request time;

•

Stop time: is the interval time selected in the previous parameters window, added to the start time;

•

Time: is the current response time;

•

Log File: is the complete path of the file where the received values are stored.

By clicking on "Show details" box, on the left side of the Power Measurement Graphic, a new table appears; this table shows the following relevant values of the received and transmitted power: •

Tx Local End

625



max Tx local value and date when this value was received for the first time. min. Tx local value and its current date when this value was received for the first time. current Tx local value and its current date. •

Tx Far End max Tx remote value and date when this value was received for the first time. min. Tx remote value and its current date when this value was received for the first time. current Tx remote value and its current date.

•

Rx Local End max Rx local value and date when this value was received for the first time. min. Rx local value and its current date when this value was received for the first time. current Rx local value and its current date.

•

Rx Far End max Rx remote value and date when this value was received for the first time. min. Rx remote value and its current date when this value was received for the first time. current Rx remote value and its current date.

•

Rx Div Local End (MPT-HLS in SD configuration only) max Rx local value and date for the diversity receiver when this value was received for the first time. min. Rx local value and its current date when this value was received for the first time. current Rx local value and its current date.

•

Rx Div Far End (MPT-HLS in SD configuration only) max Rx remote value and date for the diversity receiver when this value was received for the first time. min. Rx remote value and its current date when this value was received for the first time. current Rx remote value and its current date.

Note: When an error is present, results for the diversity receiver are displayed as follows:

If an ICP or Cable Loss alarm occurs, the value displayed is -99.8 dBm.

626



If a failure reading the register containing the received power occurs, the value displayed is -99.7 dBm. If SD is disabled or it is enabled but the diversity receiver is missing, the value displayed is -99.7 dBm. If the diversity receiver is squelched, the measurement is not affected. Note: When not receiving any signal, RSL value is not set to a fixed specific value.

Note: For radios other than the MPT-HLS, PTx and PRx levels software readings tolerance is: PTx = Real Value ± 3dB PRx = Real Value ± 5dB

Note: For the MPT-HLS, PTx and PRx levels software readings tolerance is: PTx = Real Value ± 2dB PRx = Real Value ± 3 dB

627



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

11.15.4.4.1

How to read a Power Measurement file

Tick the Read File box and press the Select File button. The directory of WebEML automatically opens to navigate and get the power measurement file. Note: By default the measurement files are stored in the MPRE_ CT_Vxx.xx.xx directory and have extension .txt.

Select the desired file and click Open. The selected file will appear in the Log file field. Click button Start (on the right side of the Sample Time field). The file opens.

628



The buttons in the lower part of the window allow to flow the graph within the measurement interval. Note: The measurement file can be opened also with a standard text editor (for example, WordPad). Open the directory where the txt files are stored and open the file. The measurements are shown in the tabular mode.

11.16 11.16.1

CORE main view General This chapter describes the functions types offered to the operator in order to navigate the Core card. To open this view double-click on a Core-E, CorEvo, MSS-1 or MSSO unit. The CORE domain multiple main view contains two tab-panels: •


•

TMN Interface

This domain view consists of the following areas: •

Resource Tree, displaying Ethernet physical interface with related port number;

•

Resource List, displaying tabular information about tributaries in tree area;

•

Resource Detail, providing access to Core detail view “Alarms” and “Settings”.

629


11.16.1.1 Figure 298



Core-E Main view

If the optional SFP optical plug-in has been enabled in the Core unit optical ports (refer to Equipment menu) also the relevant Ethernet Port # will appear (see Core-E Main view (with optical SFP Ethernet port#5)). Note: Fewer ports are available with MSS-1 and MSS-O units. The configuration of the ports is the same.

630


Figure 299


Core-E Main view (with optical SFP Ethernet port#5)

This tab-panel refers to the Ethernet ports, which can be used as traffic ports and includes three tab-panels each Ethernet port:

11.16.1.1.1

•

Alarms tab-panel

•

Settings tab-panel

•

Advanced tab-panel

•


Alarms tab-panel

The “Alarms” view shows the Ethernet port-related alarms. Select the node in the Tree area to check the current state of the Ethernet tributary alarms.

631


11.16.1.1.2


Settings tab-panel

For SFP Ethernet Ports Figure 300

Settings tab-panel for SFP Ethernet ports

The Settings view performs all the available functions for SFP Ethernet tributary ports. Information related to the port configuration is provided by the following parameters: •


•

Port Status (Enabled or Disabled)

Warning: Before enabling the Ethernet port, when the Static LAG and the Ethernet Interface Criteria for 1+1 EPS Core features have been enabled in Configuration Menu > System Settings, it is recommended first to disable the “Ethernet Interface Criteria for 1+1 EPS Core” feature. This feature could be enabled again after that this additional port has been correctly configured. No traffic effect is foreseen with this operation.

632

•

Auto-Negotiation Status (Enabled or Disabled)

•




Note: Only asymmetric pause capability can be configured to transmit pause frame but not receive pause frame on the Ethernet ports. If a pause frame is received on Ethernet ports such frame is dropped. Default values for manual mode are 100 Mbit/s, full duplex, pause disable.

•

Hold Off (Enabled or Disabled) This parameter enables the 500 ms hold off timer for the Ethernet LOS defect. The parameter can be enabled if the port is part of a Ring.

•


•

Advertised Capability, (“1000 Mb/s – Full Duplex”). The “Restart” button allows forcing auto-negotiation to begin link re-negotiation.

•

The SFP Info field is a read-only field which displays characteristics of the SFP.

Note: For electrical SFPs, the Laser Wavelength is always reported as 0 nm.

•


−



•

Admit all (tagged and untagged frames are allowed in ingress)

•

Default value: “Admit all”.

Port VLAN ID: if the Acceptable Frame Type is set to “Admit all” the VLAN-ID and Priority fields (to be added in ingress to untagged frames) must be configured. Only VLAN-ID values already defined (in the VLAN management menu) can be configured for this purpose. The Priority values allowed are in the range 0 - 7.

The default Port VLAN-ID and Priority values are: VLAN-ID=1; Priority=0. The VLAN 1 is always removed when the frame is forwarded. Note: Untagged frames The untagged frames received on one user Ethernet port, configured as “Admit tagged only”, are dropped.

633



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

11.16.1.1.3

•


•

Synchronous Ethernet Operation Mode From an Ethernet traffic interface configured at 1000 Mb/s, you can recover the physical Rx synchronization signal or deliver the NE clock synchronization signal. To do this the Ethernet port must be set a Synch-E Master. Synchronous Ethernet Operation Mode is required to set up synchronous Ethernet networks addressed by G.8261.


The Provider Bridge tab-panel allows you to configure the port type for each port, if the NE is configured in 802.1ad (Provider Bridge) mode. For information about provider bridge parameters, see section Provider Bridge tab-panel. The port can be configured as: 1. NNI 2. UNI (port based) 3. UNI (VLAN based)

634


Figure 301



11.16.1.1.4


The Policy & Translation tab-panel allows to configure for each user Ethernet port the following advanced Ethernet features:

Figure 302

•

Port Rate Limiter (Ingress and/or Egress)

•

Storm Control (Ingress)

•

VLAN Rate Limiter (Ingress)


635


11.16.1.1.5



The Per-VLAN Per-CoS Rate Limiter tab panel allows you to configure a Per-VLAN Per-CoS Rate Limiter on a User Ethernet port; see Figure 303. A Per-VLAN Per-CoS Rate Limiter can be applied to each User Ethernet port for the ingress direction. The rate limiter is applied to a tagged Ethernet flow classified according to the VLAN ID and the PCP fields of the VLAN tag. The flow is identified by one VLAN ID value and one PCP value. Figure 303


11.16.1.2

TMN Interface With the introduction of TMN In-Band two new IP interfaces are added to those already available. •

NE Local IP Address

•

TMN Local Ethernet interface, IP/subnet

•

TMN Out-of-Band interface on User Ethernet port 4, IP/subnet

•

TMN In-Band interface #1, IP/subnet

•

TMN In-Band interface #2, IP/subnet

User Ethernet port 4 can then used as:

636

•

pure Ethernet traffic interface

•

pure Out-of-band TMN Local Ethernet interface

•

Ethernet traffic interface carrying TMN In-Band traffic



The NE Local IP Address can be reused on one of the other TMN interfaces. These interfaces must have different IP subnets. Figure 304

TMN Interface

This tab-panel refers to the TMN Interface. The interfaces are of two types: 1. TMN Ethernet on a dedicated connector 2. Port #4 of the Ethernet traffic ports, which can be dedicated to TMN purpose and not to traffic. This tab-panel has 2 tab-panels: •

Alarm tab-panel

•

Settings tab-panel

637


11.16.1.2.1


Alarms tab-panel

The Alarm view shows the Ethernet ports-related alarms. Selecting the node in the Tree area allows checking Ethernet tributary alarms current state.

11.16.1.3 Figure 305

Settings tab-panel for TMN In-band

TMN In-band Settings tab panel

The TMN In-Band feature allows the extension of the DCN over User Ethernet interfaces used to carry user traffic. Two default TMN In-Band interfaces (TMN In-band #1 and #2) are supported, each having its own IP address and subnet. The TMN traffic delivered In-Band is VLAN tagged and identified by a specific VLAN ID defined by the operator in the range 2-4080. The delivery of TMN In-Band can be enabled on all User Ethernet interface of the Core board, both Optical and Electrical. Note: If two Ethernet ports, associated with the same TMN In-band logical interface, are segregated, the two ports do not communicate with each other, as for the normal Ethernet traffic (they have the same VLAN ID). If two Ethernet ports, configured in different TMN Inband logical interfaces, are segregated, the two ports can communicate with each other, as they have 2 different VLAN IDs).

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.

638



The OSPF and related Area ID can be enabled on a TMN In-Band interface. For each TMN In-Band interface the following parameters must be configured:

11.16.1.3.1

•

Working Mode: enabled or disabled

•

IP address and IP Mask (IPv4) or Prefix Length (IPv6): −

IPv4 default address is 10.0.3.2/24 for interface #1 and 10.0.4.2/24 for interface #2

−

IPv6 default address is FEC0:0:0:3::1/64 for interface #1 and FEC0:0:0:4::1/64 for interface #2.

•

VLAN ID: no default value is defined for interface #1 and for interface #2

•

DSCP value between 0 and 63: default is 34.

•

PCP value from 0 to 7: default is 7.

•

List of User Ethernet interfaces where TMN In-Band traffic is transmitted or received: default is None (multiple selection or deselection can be done by holding the Ctrl key while clicking on one or more entries)

•

IP routing protocol, Static Routing or OSPF: default is Static Routing for both interfaces

•

OSPF Area Number if OSPF is enabled: default is 0. The area must be created in advance.

Settings tab-panel for TMN Ethernet port

Figure 306 shows the tab-panel. Figure 306

Settings tab-panel for TMN Ethernet ports

639



If used, the following must be configured for TMN Ethernet: •

Working Mode enabled.

•

IP address with IP mask (IPv4 mode) or Prefix Length (IPv6).

•

IP Routing Protocol: Static Routing or OSPF. If OSPF has been selected, the Area Number must also be assigned.

•

Alarm Profile:

Note: When a TMN interface is disabled, the SNMP manager checks for static routes on the interface to be disabled. If static routes exist, an error message will display when the interface is disabled.

11.16.1.4

Settings tab-panel for TMN Ethernet Port #4 Figure 307 shows the tab-panel.

Figure 307

Settings tab-panel for TMN Ethernet port #4

If the Ethernet Port 4 has been used as TMN port, the port 4 must be:

640

•

Enabled.

•

Assigned an IP address with its IP mask.

•

Selected the IP Routing Protocol: Static Routing or OSPF. If OSPF has been selected, assign also the area number.


11.16.1.5


MPT ODU connected to the Core The electrical Ethernet ports#1 to 4, Core-E Ethernet port #5 and #6, or CorEvo ports #7 and #8 can be used to connect an MPT. In this case a new tab-panel will appear which allows to access directly to the MPT menu. Note: Ethernet ports#1 to #4 can be used to connect an MPT-MC, MPT-HC/HC-HQAM, or MPT-XP/XP-HQAM; Ethernet ports#5 and #6 (Core-E), or Ethernet ports #7 and #8 (CorEvo) can be used to connect only an MPT-HC/HC-HQAM/XP/XP-HQAM (Ethernet ports are available by installing the relevant SFP).

In the example in Figure 308, an MPT-HC (Port #1 tab-panel) has been connected to Port #1 and another MPT-HC (Port #5 tab-panel) has been connected to Port #5. The Ethernet Port #1 and Port #5 are not available as an Ethernet Physical Interface: it has been removed from the Tributaries Data list. Figure 308

MPT-HC example

641


11.17 11.17.1


MSS External Input Point view General To open this view, double-click on the HK inputs on an MSS-1. An input external point is described by the following parameters (see Figure 309): •

Id: identification number

•

UserLabel: associates a user-friendly name to an external point

•

Polarity: describes the polarity (Active Low/ Active High)

•

External State: describes the state (on /off)

•

Alarm Profile: describes the associated Alarm Profile (not implemented)

After a row selection, the user can modify the User Label and Polarity. Figure 309

642

MSS External Input Point Main View


11.18 11.18.1


MSS A-FANS main view General To open this view, double-click on an A-FANS card. An input external point is described by the following parameters (see Figure 310): •


•


•


•


•


After a row selection, the user can modify the User Label and Polarity. Figure 310

MSS A-FANS Main View

11.19

AUX view To open the AUX view, double-click on an AUX card.

643



The AUX peripheral unit has two tab-panels:

11.19.1

•

Settings

•

External points

Settings To enable the 64 kbit/s user Service channel #1 or #2 set the Channel Status to Enabled and click Apply. Note: The Protocol Type is fixed to Synchronous 64 kbit/s RS422/V.11 DCE co-directional.

Note: The EOW Interface is not implemented in the current release.

Figure 311

644

Settings tab-panel


11.19.2


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

11.19.2.1

Input External Points An input external point is described by the following parameters (Figure below): •


•


•


•


•


After a row selection, the user can modify the User Label, the Polarity.

645


Figure 312


Input External Point View

11.19.2.2

Output External Points Seven output external points are available. The output external points (CPO#1 ... 7) are described by the following parameters:

646

•


•

UserLabel: a user friendly name can be associated with an external point

•

Polarity: describes the polarity (Active Low/ Active High). In this field the polarity of the external point can be changed.

•

Criteria: fixed to Manual. (The output can be activated manually). Note: the Automatic mode is not supported in this release.

•

External State: describes the state (on /off). In this field the external point can be activated (on) or deactivated (off).


Figure 313


Output External Points View

647


648




12 NEtO Servers Manager Tool overview 12.1

NEtO Servers Manager Tool overview The NEtO Servers Manager is an application included in the WebEML Tool Suite and manages the FTP and SFTP servers available on the operator’s computer/server where the NEtO application is running. The NEtO Servers Manager also manages RMI Registry components started through the NEtO application.

12.1.1

Launch NEtO Servers Manager tool Before the NEtO application is started, the RMI registry and any SFTP or FTP servers should be stopped. The NEtO Servers Manager is automatically started when the first NEtO application is started or the Offline Performance Monitoring Tool is started by the operator. See Figure 314.

Figure 314

NEtO Servers Manager Tool

649

Release 7.0.0 3DB 19383 ACAA Issue 01 NEtO Servers Manager Tool overview

12.1.2


FTP/SFTP Servers The FTP and SFTP Servers are disabled by default. An example of the FTP server disabled (grey indicator) and the SFTP enabled (green indicator) is shown in Figure 315. Hovering the cursor over either FTP or SFTP Server button displays a tool tip which includes the status of the server.

Figure 315

Manage FTP/SFTP Servers

12.1.3

RMI Resource management The NEtO Servers Manager tracks the number of RMI Registry resources that register themselves in the running RMI registry and displays the count in the manager window. The following WebEML components register in the RMI Registry: •

NEtO

•

Alarms Log Monitor

•

Performance Monitoring Tool (on-Line and off-line)

•

NEtO Servers Manager

In the example shown in Figure 316, three RMI Resources are detected by the NEtO Servers Manager. All three RMI Resources are being managed by the NEtO Servers Manager. This is indicated with the green normal status indicator.

650


Figure 316


RMI Resource counter — normal operation

If an RMI Registry is already running and the NEtO Servers Manager cannot create its own, the abnormal status indicator appears, see Figure 317. Figure 317

RMI Resource counter — abnormal operation

When JUSM is started by the 5620SAM, the NEtO Servers Manager is started by NEtO in background mode. In this application the JUSM RMI Registry includes only two resources: the NEtO and the NEtO Servers Manager. The RMI Registry is not managed by the NEtO Servers Manager if it is previously opened by another Java based application. The dialog window shown in Figure 318 displays. Also this is indicated with the abnormal status indicator as shown in Figure 317. Figure 318

RMI Registry Error dialog window

651

Release 7.0.0 3DB 19383 ACAA Issue 01 NEtO Servers Manager Tool overview

12.1.4


Close NEtO Servers Manager Tool

The NEtO Servers Manager will close itself automatically when the following conditions are satisfied: •

FTP server is not running

•

SFTP server is not running

•

The list of RMI Registry components running includes only the NEtO Servers Manager

The NEtO Servers Manager will close itself automatically when the list of RMI registry components registered with NEtO Servers Manager is reduced to one, the “NEtO Servers Manager” and the automatic shutdown procedure has been activated by at least one known WebEML application. At least two WebEML related resources must have previously registered. If no new WebEML applications registers to the RMI registry and the RMI registry count remains at one, the automatic shutdown procedure is not activated. A list of RMI registry components is included in section The following WebEML components register in the RMI Registry: and includes the Offline WT Performance Monitoring Suite. The NEtO Servers Manager will not close itself automatically when RMI registry components are still running that were not opened and managed by the NEtO Servers Manager. In this condition either the RMI registry components may be closed or the NEtO Servers Manager may be closed manually. When the NEtO Servers Manager is closed manually, the error message shown in Figure 319 displays. Verify no software downloads are in progress and it is safe to close the NEtO Servers Manager. Figure 319

652

NEtO Servers Manager — CLOSE error message



13 Summary Block Diagram overview 13.1

Summary Block overview When a Core-E card is in use, the summary block diagram view provides a logical view of the radio configuration, a synthesis of alarms, and the state of performance monitoring ports and loopbacks. The Summary Block Diagram View is not available when a CorEvo card is in use. See Figure 320 for an example of the Summary Block Diagram View.

Figure 320

Summary Block diagram view

Each entity has an alarm indicator (colored ball icon) which indicates the alarm status of the entity. See Severity Alarm Synthesis area for definitions of supported alarm severities and their associated colors. The alarm indicators update automatically with changes to the entity alarm status. In the summary block diagram view, the current configuration of the MSS shelf is displayed including the equipped card types (Core-E, PDH, P8ETH or EASv2), provisioned protection schemes, and provisioned cross-connections between the different equipment ports.

653

Release 7.0.0 3DB 19383 ACAA Issue 01 Summary Block Diagram overview


Double-clicking on an object navigates the user to the associated view. See Figure 321 for an example of a protected radio (MPT-HL Detail View). Figure 321

Protected MPT-HL detail view

On the detail views, the active signal paths, Transmit (TX) and Receive (RX), are displayed with a green line, including all possible switching paths and the current status of the switch. The active signal path updates automatically with changes to the protection switch state (EPS, HSB, and Rx Radio). Displayed on some slots and ports is an icon representing Loopback. When the loopback icon is present the associated slot or port supports a loopback feature. When a loopback is active the icon is displayed green. While in a detail view, double-click the loopback icon navigates the user to the associated loopback tab. See Figure 322 for an example of the loopback icons.

654


Figure 322


Loopback icons

Displayed on some slots and ports is an icon representing the Performance Monitoring Tool (PMT). When the PMT icon is present the associated slot or port supports Performance Monitoring feature. When a PMT counter is active the icon is displayed green. While in a detail view, double-clicking the PMT icon navigates the user to the PMT. See Figure 323 for an example of the Performance Monitoring Tool icons. Note: Though the PMT icon is displayed with E1/DS1 (P32E1DS1) and DS3 (P2E3DS3) cards, the PMT is not supported by these cards in this release.

Figure 323

Performance Monitoring tool icons

Navigation options available from the summary block diagram view include: detailed block diagrams, Ethernet Physical Interface tab, Synchronization tab, Protection Schemes tab, Performance Monitoring Tool, Loopback tab, TMN Local Interface tab, Abnormal Condition List. Details on navigation options are as follows: Double-click on a Radio icon navigates to the associated radio Detail View. See Figure 321 for an example of a protected radio (MPT-HL) Detail View. •

Double-clicking on a PDH slot icon navigates to the associated PDH Detail View. See Figure 324 for an example of a PDH Detail View. See Figure 326 for an example of a protected PDH Detail View.

•

Double-clicking on an Ethernet icon navigates to the associated Ethernet Physical Interface tab.

•

Double-clicking on the TMN Local Interfaces box navigates to the TMN Interface tab associated with the Core card.

655



•

Double-clicking on a Protection Switch symbol (Core EPS, PDH EPS, radio EPS, HSB, and Rx Radio) navigates to the associated Protection Schemes tab.

•

Double-clicking on SYNC navigates to the synchronization tab.

•

Double-clicking on a Loopback icon navigates to the associated loopback tab.

•

Double-clicking on a Performance Monitoring Tool icon navigates to the Performance Monitoring Tool.

•

Double-clicking on the Abnormal Condition List box navigates to the Abnormal Condition List.

The Refresh button updates the main view and all opened detailed views. The Help button opens Summary Block Diagram help. The Close button closes the Summary Block Diagram View.

13.2

PDH unit secondary view Depending on the configuration, different diagrams are shown to the operator (see Figure 324 to Figure 327), describing the actual NE status and working mode. On the PDH slot the loopback icons ( ) are supported and are shown in green color ( ) whenever a loopback is active. Performance Monitoring icons ( ) are shown in green whenever a PM is active. By double clicking on the Performance Monitoring icon ( ) the navigation to the WT Performance Monitoring Suite starts.

656


Figure 324


1+0 block diagram (E1 unit) (without Core-E protection)

657


Figure 325

658

1+0 block diagram (E1 unit) (with Core-E protection)



Figure 326


1+1 block diagram (PDH units) (without Core-E protection)

659


Figure 327


1+1 block diagram (PDH units) (with Core-E protection)

13.3

SDH unit secondary view Depending on the configuration, different diagrams are shown to the operator (see Figure 328 to Figure 331), describing the actual NE status and working mode. On the SDH slot the loopback icons ( ) are supported and are shown in green color ( ) whenever a loopback is active. Performance Monitoring icons ( ) are not supported.

660


Figure 328


1+0 block diagram (SDH unit) (without Core protection)

661


Figure 329

662

1+0 block diagram (SDH unit) (with Core protection)



Figure 330


1+1 block diagram (SDH unit) (without Core protection)

663


Figure 331


1 1 block diagram (SDH unit) (with Core protection)

13.4

Radio secondary view (MPT ODU) Depending on the configuration, different diagrams are shown to the operator (see Figure 332 to Figure 337), describing the actual NE status and working mode. Loopback icons ( ) are shown in green color ( ) whenever a loopback is active. Performance Monitoring icons ( ) are shown in green whenever a PM is active. By double clicking on the Performance Monitoring icon ( ) the navigation to the WT Performance Monitoring Suite starts. Ethernet Counters icon is shown in green whenever the counter has been activated. By double clicking on the Loopback icon, on the PM icon or on the Ethernet Counters icon the navigation to the relevant menus starts. The switch blocks are updated according to the signal path, following light greencoloured line.

664


Figure 332


1+0 block diagram (MPT-ACC unit) (without Core-E protection)

665


Figure 333

666


1+0 block diagram (MPT-ACC unit) (with Core-E protection)


Figure 334


1+1 FD block diagram (MPT-ACC units) (without Core-E protection)

667


Figure 335

668


1+1 FD block diagram (MPT-ACC units) (with Core-E protection)


Figure 336


1+1 Hot Standby block diagram (MPT-ACC units) (without Core-E protection)

669


Figure 337


1+1 Hot Standby block diagram (MPT-ACC units) (with Core-E protection)

13.5

XPIC If an MPT-HC/MPT-XP has an XPIC+RPS external module installed and if the XPIC has been enabled in the Radio menu, the XPIC+RPS module will appear in the Block diagram, as shown in the next figure. For MPT-HC-HQAMs and XP-HQAMs, which have embedded XPIC and RPS functions, the functions appear in the block diagram. For XPIC, an RTU licence is required.

670


Figure 338


Co-channel XPIC

671


Figure 339

672

1+1 XPIC




14 Performance Monitoring Suite overview 14.1

Performance Monitoring Suite overview This chapter provides a user guide to the Performance Monitoring Suite, defining the PM Suite page layout, navigation, and resources available to understand the navigation of the PM Suite on the 9500 MPR. The PM Suite supports monitoring of up to five NEs at a time.

14.1.1

Start up the Performance Monitoring Suite The main view of the craft terminal provides two ways to start up the PM Suite. The PM Suite can be started up by either using the main menu bar, Diagnosis > Performance Monitoring path, (see Figure 340) or by clicking the PM Suite icon from the main toolbar (see Figure 341).

Figure 340

Performance Monitoring Suite main menu bar path

Figure 341

Performance Monitoring Suite icon

14.1.2

PM Suite overview The PM Suite provides the configuration, performance monitor controls, printing, and exporting functions; see Figure 342. The main view comprises the following areas.

673

Release 7.0.0 3DB 19383 ACAA Issue 01 Performance Monitoring Suite overview

Figure 342

674

•

Toolbar area

•

View bar area

•

Resource tree area

•

Resource list area

Performance Monitoring Suite main view



14.1.3


Toolbar area

The toolbar area contains icons for quick access to PM Suite controls to operate and archive PM results; see Figure 343. Figure 343

Toolbar area

The toolbar area icons are defined as follows:

14.1.4

•

Close—Closes the PM Suite

•

PM Status—Shows PM Status and starts or stops PM data collection

•

Move to Front—(Not supported in this release)

•

Move to Back—(Not supported in this release)

•

Sort—(Not supported in this release)

•

Background—(Not supported in this release)

•

Refresh—Refreshes displayed PM data counters.

•

Reset—Resets PM data counters.

•

Export—Exports selected PM data.

•

Print — Prints selected PM data.

•

Help—Open online help.

•

Offline Mode—Change to offline mode.

•

Threshold Editor—Access Radio PM Threshold Editor

View bar area Two tabs are provided for quick access to navigate between monitored NEs. The two tabs available are NEs List and Selected NE (by IP address); see Figure 344.

675


Figure 344


View bar area

14.1.5

•

List View—Switches the resource list area to the List View.

•

Overview—Switches the resource list area to the Overview.

•

Bird’s Eye View—Switches the resource list area to the Bird’s Eye View.

•

Note—Opens the Legend window. The Legend window provides a list and definition of the selected PM data fields.

•

General Help—Opens the PM Suite general help file.

Resource tree area The resource tree area provides access to the monitored NEs. The following tabs are provided for quick access to navigate between monitored NEs; see Figure 345.

676

•

Selected NE (by IP address) tab

•

NEs List tab


Figure 345


Resource tree area

The PM counter types are arranged in panels for quick access to all PM counters. Each panel is arranged in a tree structure listing the shelf slots, including the provisioned card type. Seven PM counter panels are supported: •

Ethernet Statistics — Includes PM counters supported on enabled Ethernet ports and enabled radio port Tx Ethernet queues.

•

Radio PM — Includes PM counters supported on enabled radio hops and links, for both the transmit and receive direction, and radio QoS and radio power level counters.

•

Adaptive Modulation PM — PM counters related to Tx modulation technique active.

•

PDH PM — Includes PM counters related to Quality of Service (QoS) of the incoming and outgoing signals associated with E1/DS1 PDH signals.

•

SDH PM — Includes PM counters related to Quality of Service (QoS) of the incoming and outgoing signals associated with SDH signals.

677


•


RSL History — Includes RSL History counters supported on enabled MPT-HL radio ports, including Tx and Rx power levels for channel #1 and #0 for both the local and far-end of the radio hop/link.

Each tree node consists of two symbols. The first symbol indicates the state of the structure, for example, if the symbol has a “+”, the tree can be expanded to a lower level. If the symbol is a “-”, the tree structure can be collapsed. If there is no first symbol, the node represents a leaf. The second symbol is a graphical representation of the entity. When PM counters are available on a slot/port, the circle icon is colored according to the highest alarm state of the entity. When no PM counters are available for a slot/port, the circle icon is colored gray and is not selectable.

14.1.6

Resource list area The resource list area contains a tabular view and a graphical view. The resource list area displays PM data associated with the selected entity in the resource tree area for the selected NE, in both graphical and tabular formats. PM data can be displayed in the following three views:

678

•

List View — See Figure 346.

•

Overview — See Figure 347.

•

Bird’s Eye View — See Figure 348.


Figure 346

Resource list area: List View

Figure 347

Resource list area: Overview


679


Figure 348

680

Resource list area: Bird’s Eye View




15 WT CLI tool overview 15.1

Introduction Ethernet Connectivity Fault Management (ECFM) (IEEE802.1ag) is performed using the WT CLI Tool. The WT CLI Tool is launched with the WebEML craft terminal (CT), see the 9500 MPR WebEML User Manual. This chapter describes the following features:

15.1.1

•

Ethernet Connectivity Fault Management CLI commands

•

Ethernet CFM scenarios

•

Protocols

•

TACACS+ commands

Command conventions

The following command conventions are used in this chapter. Shell interface is case-sensitive, all the command keywords shall be lowercase. Elements in angle brackets ( < > ) represent a field requested as an input to the operator. Elements in square brackets ( [ ] ) represent an optional field. Elements in braces ( { } ) represent the group of parameters admitted for the specific command. Different values are separated by the | separator. Mandatory command keywords shall be inserted in the order specified in this document. Optional command keywords (fields in square brackets) can be inserted in any order.

681

Release 7.0.0 3DB 19383 ACAA Issue 01 WT CLI tool overview

15.1.2


Abbreviations Abbreviations used in describing the WT CLI Tool are listed in the following table.

CCM CFM LACP LAG LBM LBR LTM LTR MA MD MEP MIP NE PDU

Continuity Check Message Connectivity Fault Management Link Aggregation Control Protocol Link Aggregation Group LoopBack Message LoopBack Reply LinkTrace Message LinkTrace Reply Maintenance Association Maintenance Domain Maintenance association End Point Maintenance association Intermediate Point Network Element Protocol Data Unit

15.1.3

Help

For a list of commands related to a specific functionality, it is possible to use the help command followed by the name of the feature: help ecfm

15.2

Ethernet Connectivity Fault Management CLI commands The CLI Ethernet Connectivity Fault Management (ECFM) commands available in the WT CLI tool are listed in Table 62.

682


Table 62


WT CLI Tool, Ethernet Connectivity Fault Management commands

COMMANDS

DEFAULT VALUES

md create [format {dns-like-name|mac-addr|char-string}] name level [mip-creation-criteria {none|default|explicit}]

format char-string mip-creationcriteria none

md modify mip-creation-criteria {none|default|explicit} md destroy ma create md [format {primary-vid|charstring|unsigned-int16|rfc2865-vpn-id}] name vlan [mip-creation-criteria {none|default|explicit|defer}] [interval {onesec|ten-sec|one-min|ten-min}]

format char-string mip-creationcriteria defer interval one-sec

ma modify mip-creation-criteria {none|default|explicit|defer} ma modify interval {one-sec|ten-sec|one-min|ten-min} ma destroy ma mep assign ma mep remove mep : create [direction {up|down}] {if |lag } [priority ] [enable {true|false}]

direction down priority 7 enable false

mep : modify priority mep : enable {true|false} mep : ccm enable {true|false}

ccm enable false

mep : destroy loopback : {mpid | mac } [count ]

count 1

linktrace : {mpid | mac } [ttl ] [usefdbonly]

ttl 64 usefdbonly not set

md [] show ma [] show

683


Table 62


WT CLI Tool, Ethernet Connectivity Fault Management commands (Continued)

COMMANDS

DEFAULT VALUES

ma show mp local ma show mp remote ma show errors ma show error-log clear ccm database clear errors clear error-log

15.2.1

CMD ID: ECFM_1 (MD CREATE)

md create [format {dns-like-name|mac-addr|char-string}] name level [mip-creation-criteria {none|default|explicit}] Description: creates a Maintenance Domain (MD)

Parameters: •

•

•

684

md_index (mandatory) −

Range: 1-16

−

Description: identifies the MD in the equipment

format (optional) −

Values: dns-like-name|mac-addr|char-string

−

Default: char-string

−

Description: sets the format of the name of the MD. •

dns-like-name: insert a DNS name string

•

mac-addr: insert a MAC address and an unsigned integer (for example, 00:00:00:00:00:01:3457). Integer value shall be in the range 0 – 65535.

•

char-string: insert a character string (maximum 20 characters; ASCII printable characters—Space excluded)

name (mandatory)



− •

•

Description: sets the name of the MD according to the format configured. Name shall be unique

level (mandatory) −

Range: 0-7

−

Description: sets the MD Level. It is used to define different levels of monitoring for a specific service.

mip-creation-criteria (optional) −

Values: none|default|explicit

−

Default: none

−

Description: sets the creation criteria parameter of the MD. This parameter is used by the automatic MIP creation mechanism. None (no MIPs are created); Default (MIPs are created on all ports belonging to the MA’s VLAN); Explicit (MIPs are created on ports belonging to the MA’s VLAN only if a MEP is present at a lower MD Level). See Automatic MIP creation for details.

Network Element shall be in 802.1Q Virtual Bridge Mode

15.2.2

CMD ID: ECFM_2 (MD MIP CREATION CRITERIA)

md modify mip-creation-criteria {none|default|explicit} Description: modifies the MIP creation criteria of a specific MD Parameters: 1. md_index (mandatory) −

Range: 1-16

−


2. mip-creation-criteria (mandatory) −

Values: none|default|explicit

−

Description: sets the creation criteria parameter of the MD. This parameter is used by the automatic MIP creation mechanism. None (no MIPs are created); Default (MIPs are created on all ports belonging to the MA’s VLAN); Explicit (MIPs are created on ports belonging to the MA’s VLAN only if a MEP is present at a lower MD Level). See Automatic MIP creation for details.

685


15.2.3


CMD ID: ECFM_3 (MD DESTROY)

md destroy Description: destroys a MD Parameters: •

md_index (mandatory) −

Range: 1-16

−


MD cannot be destroyed if any MA is associated with it. Destroy all MAs belonging to the MD, using MA DESTROY command, before removing it.

15.2.4

CMD ID: ECFM_4 (MA CREATE)

ma create md [format {primary-vid|char-string|unsignedint16|rfc2865-vpn-id}] name vlan [mip-creationcriteria {none|default|explicit|defer}] [interval {one-sec|ten-sec|one-min|ten-min}] Description: creates a Maintenance Association (MA) Parameters: •

•

686

ma_index (mandatory) −

Range: 1-512

−

Description: identifies the MA in the equipment

format (optional) −

Values: primary-vid|char-string|unsigned-int16|rfc2865-vpn-id

−

Default: char-string

−

Description: sets the format of the name of the MA •

primary-vid: insert a VLAN ID

•

char-string: insert a character string (maximum 20 characters; ASCII printable characters—Space excluded)

•

unsigned-int: insert an unsigned integer in the range 0 – 65535.

•

rfc2865-vpn-id: insert a VPN ID. It is composed by 3 bytes VPN OUI and 4 bytes VPN Index separated by colon (for example, 00A157:1111FFFF)


•


name (mandatory) −

Description: sets the name of the MA according to the format configured

•

vlan (mandatory)

•

Range: 0-4080

•

Description: sets the VLAN ID to be associated with the MA. The value 0 configures a VLAN unaware MA.

•

mip-creation-criteria (optional)

•

−

Values: none|default|explicit|defer

−

Default: defer

−

Description: sets the creation criteria parameter of the MA. This parameter is used by the automatic MIP creation mechanism. None (no MIPs are created); Default (MIPs are created on all ports belonging to the MA’s VLAN); Explicit (MIPs are created on ports belonging to the MA’s VLAN only if a MEP is present at a lower MD Level); Defer (mip-creationcriteria of the associated MD is considered). See Automatic MIP creation for details.

interval (optional) −

Values: one-sec|ten-sec|one-min|ten-min

−

Default: one-sec

−

Description: set the transmission interval of CCM messages.

MA cannot be created if the VLAN associated is not present in the Network Element. Once an MA is created, the associated VLAN cannot be removed from the Network Element: MA shall be destroyed before removing the VLAN. MA cannot be created if there is another MA, in the same MD, associated with the same VLAN. MA cannot be created if there is another MA, with same VLAN and MD Level, with an UpMEP configured. The level of a VLAN-unaware MA cannot be equal or greater than the level of a VLAN-aware MA. The level of a VLAN-aware MA cannot be equal or less than the level of a VLANunaware MA.

687


15.2.5


CMD ID: ECFM_5 (MA MIP CREATION CRITERIA)

ma modify mip-creation-criteria {none|default|explicit|defer} Description: modifies the MIP creation criteria of a specific MA Parameters: •

•

15.2.6


Range: 1-512

−


mip-creation-criteria (mandatory) −

Values: none|default|explicit|defer

−

Description: sets the creation criteria parameter of the MA. This parameter is used by the automatic MIP creation mechanism. None (no MIPs are created); Default (MIPs are created on all ports belonging to the MA’s VLAN); Explicit (MIPs are created on ports belonging to the MA’s VLAN only if a MEP is present at a lower MD Level); Defer (mip-creationcriteria of the associated MD is considered). See Automatic MIP creation for details.

CMD ID: ECFM_6 (CCM INTERVAL)

ma modify interval {one-sec|ten-sec|one-min|ten-min} Description: modifies the CCM interval of a specific MA Parameters: •

•

688


Range: 1-512

−


interval (mandatory) −

Values: one-sec|ten-sec|one-min|ten-min

−

Description: set the transmission interval of CCM messages.


15.2.7


CMD ID: ECFM_7 (MA DESTROY)

ma destroy Description: destroys a MA Parameters: •


Range: 1-512

−


MA cannot be destroyed if any MEP is assigned to it. Remove all MEPs assigned to the MA, using MEP REMOVE command, before removing it.

15.2.8

CMD ID: ECFM_8 (MEP ASSIGN)

ma mep assign Description: assigns MEPID to the MA. All MEPs belonging to a MA shall be inserted in the MEP table. This list includes both local and remote MEPs. This command is used to populate that table. MEPIDs of local MEPs must be inserted in this list before MEP creation. Parameters: •


Range: 1-512

−


• •

15.2.9

mepid (mandatory) −

Range: 1-8191

−

Description: represents the MEP identifier of the MEP to be associated with the MA

CMD ID: ECFM_9 (MEP REMOVE)

ma mep remove

689



Description: removes MEPID from the MA. Parameters: •

•


Range: 1-512

−



Range: 1-8191

−

Description: represents the MEP identifier of the MEP to be removed from the MA

MEP cannot be removed from the MA if it is still present in the Network Element. Destroy the MEP with MEP DESTROY command before removing it.

15.2.10

CMD ID: ECFM_10 (MEP CREATE)

mep : create [direction {up|down}] {if |lag } [priority ] [enable {true|false}] Description: creates a MEP on a specific interface Parameters: •


Range: 1-512

−


• •

•

690


Range: 1-8191

−

Description: represents the MEP identifier of the MEP to be created

direction (optional) −

Values: up|down

−

Default: down

−

Description: sets the direction of a MEP. Each MEP has an active and a passive side. The active side generates CCM, LBM and LTM. It also receives all the response messages. A Down MEP has the active side directed towards the physical layer. An Up MEP has the active side directed towards the relay entity.


•


slot/port|lag-id (mandatory) −

•

•

Description: identifies the physical interface or the LAG on which configure the MEP

priority (optional) −

Range: 0-7

−

Default: 7

−

Description: sets the priority bits of CCM, LBM and LTM.

enable (optional) −

Values: true|false

−

Default: false

−

Description: enable or disable the administrative state of the MEP

Interface indicated (slot/port or LAG) shall belong to the VLAN of the MA. MEP cannot be create if there is another MEP, on the same interface, with same Direction, MD Level and VLAN. UpMEP cannot be created on the MA if there is another MA with same VLAN and MD Level. MEP cannot be configured if there is another MEP, with same MEP ID, on the same MD Level and VLAN. UpMEP cannot be configured on a VLAN-unaware MA.

15.2.11

CMD ID: ECFM_11 (MEP PRIORITY)

mep : modify priority Description: modifies the priority bits of messages sent by the MEP Parameters: •


Range: 1-512

−


•

mepid (mandatory)

•

Range: 1-8191

•

Description: identifies the MEP in the MA

•

priority (mandatory)

691


15.2.12


−

Range: 0-7

−

Description: sets the priority bits of CCM, LBM and LTM.

CMD ID: ECFM_12 (MEP ENABLE)

mep : enable {true|false} Description: modifies the administrative state of the MEP Parameters: •

•

•

15.2.13


Range: 1-512

−



Range: 1-8191

−


enable (mandatory) −

Values: true|false

−

Description: enable or disable the administrative state of the MEP

CMD ID: ECFM_13 (CCM ENABLE)

mep : ccm enable {true|false} Description: enables or disables the CCM transmission Parameters: •


Range: 1-512

−


• •

•

692


Range: 1-8191

−


ccm enable (mandatory)



−

Values: true|false

−

Description: enable or disable the CCM transmission. At the MEP creation this value is set to False

CMD ID: ECFM_14 (MEP DESTROY) mep : destroy Description: destroys a MA Parameters: •

•

15.2.14


Range: 1-512

−



Range: 1-8191

−


CMD ID: ECFM_15 (LOOPBACK)

loopback : {mpid | mac } [count ] Description: sends a loopback message Parameters: •

•

•


Range: 1-512

−



Range: 1-8191

−

Description: identifies the MEP in the MA. It is the source MEP of the LBM

mpid|mac (mandatory) −

•

Description: defines the MEPID (valid for a LB towards a MEP) or the MAC Address (valid for a LB towards both a MEP and a MIP) of the destination Maintenance Point

count (optional) −

Range: 1-1024

693


15.2.14.1


−

Default: 1

−

Description: sets the number of LBM to be transmitted

WT CLI Tool Example for ECFM loopback count command Example response for loopback mpid count command: MPR> loopback 1:1 mpid 2 count 1 Sending 1 Ethernet CFM loopback message, timeout is 5 seconds Success rate is 100.0 percent 1/1

15.2.15

CMD ID: ECFM_16 (LINKTRACE)

linktrace : {mpid | mac } [ttl ] [usefdbonly] Description: sends a linktrace message Parameters: •


Range: 1-512

− − •

•


Range: 1-8191

−

Description: identifies the MEP in the MA. It is the source MEP of the LTM

mpid|mac (mandatory) −

•

694


Description: defines the MEPID (valid for a LT towards a MEP) or the MAC Address (valid for a LT towards both a MEP and a MIP) of the target Maintenance Point

ttl (optional) −

Range: 0-255

−

Default: 64

−

Description: sets the time-to-live of the LTM PDU


•


usefdbonly (optional) −

Values: present(1) or not present(0)

−

Default: not present(0)

−

Description: intermediate nodes receiving LTM forward a new LTM towards the next hop only if the target MAC Address has been learnt on a specific port. The target MAC Address can be found in the FDB (ForwadingDataBase – L2 table used for normal traffic forwarding) or in a specific DB described in the CFM standard (MIP CCM DataBase) populated by MIPs with source MAC Addresses of CCM traffic passingthrough.

If usefdbonly parameter is not present, MIP shall look for the target MAC Address either in the FDB or in the MIP CCM Database. If usefdbonly parameter is present, the target MAC Address shall be found in the FDB only (otherwise, the frame must not be forwarded). This parameter sets the useFDBonly flag bit in the LTM frame.

15.2.15.1

WT CLI Tool Example for ECFM linktrace count command Example response for linktrace mpid count command: MPR> linktrace 1:1 mpid 2 Traceroute to Macaddress 00:20:60:00:00:24 in domain Domain5 at level 5 with vlanId 101 -----------------------------------------------------------------------Hops

HostIngress MACIngress ActionRelay Action Next HostEgress MACEgress ActionFwd Status

-----------------------------------------------------------------------100:20:60:00:00:22:00:0c00:20:60:00:00:23IngOKRlyFDB 00:20:60:00:00:23:00:0c00:20:60:00:00:23EgrOKForwarded

695



200:20:60:00:00:23:00:0c--RlyHit 00:20:60:00:00:24:00:0b00:20:60:00:00:24EgrOKTerminalMEP -----------------------------------------------------------------------Each LTR received is displayed in this output. HOPS column identifies the LTR receiving order (in the example: Hop 1 identifies the first LTR; Hop 2 identifies the second one, …). In case of LTM transmitted by an UpMEP, the first reply is generated by the node itself. In case of LTM For each Hop (LTR received), the following information is displayed: •

HOST: identifies the sender of the LTM that triggered the LTR response. The first 6 bytes represent the sender MAC address; the last 2 bytes identifies uniquely the LTM transmitted (this value is retrieved according to the port mapping described below).

•

NEXT HOST: identifies the sender of the LTR (actually the LT Responder). The first 6 bytes represent the sender MAC address; the last 2 bytes identifies uniquely the LTM forwarded (this value is retrieved according to the port mapping described below).

•

INGRESS MAC: represent the MAC address of the MP present at the ingress port (if not present, a dash is displayed)

•

EGRESS MAC: represent the MAC address of the MP present at the egress port (if not present, a dash is displayed)

In the example: at Hop1, two MIPs are present at both the ingress and egress ports. At Hop2, a MEP is present at the egress port.

696

•

INGRESS ACTION: reports how the data frame targeted by LTM would be received on the receiving MP

•

EGRESS ACTION: reports how the data frame targeted by LTM would be passed through the egress port

•

RELAY ACTION: reports how the data frame targeted by LTM would be passed through the MAC Relay Entity to the egress port. Possible values: −

RlyHit (the LTM reached an MP whose MAC address matches the Target MAC Address)

−

RlyFDB (the egress port was determined by consulting the FDB)



− •

RlyMPDB (the egress port was determined by consulting the MIP CCM Database)

FWD STATUS: represents the value of Flag Bits in the LTR. Possible values: −

Forwarded (the LTM, that triggered the LTR transmission, has been forwarded)

−

Not Forwarded (the LTM, that triggered the LTR transmission, has not been forwarded)

−

Terminal MEP (the MP that triggered the LTR transmission is a MEP)

Figure 349, Figure 350, and Figure 351 show the port mapping for Core-E, CorEvo and MSS-O systems. Figure 349

Port Mapping for Core-E based system

697



Figure 350

Port Mapping for CorEvo based system

Figure 351

Port Mapping for MSS-O

15.2.16

CMD ID: ECFM_17 (MD SHOW)

md [] show Description: shows the parameters of one MD. If the MD Index is not present, a summary table of all the MDs in the equipment is shown. Parameters: •

698

md_index (optional) −

Range: 1-16

−

Description: identifies the MD in the equipment. If not present, all MDs in the NE are shown.


15.2.16.1


WT CLI Tool Example for ECFM md show command Example response for md show command: MPR> md show MD NAME

| MD

| LEVEL | MIP-CREATION-CRITERIA

INDEX ------------------|----------|-------|----------------------

15.2.16.2

Domain5

|

1

|

5

|

none

Domain2

|

2

|

2

|

none

WT CLI Tool Example for ECFM md show command Example response for md show command: MPR> md 1 show Maintenance Domain

1

********************* NAME:

Domain5

FORMAT:

char-string

LEVEL:

5

MIP-CREATION-CRITERIA:

none

TOTAL MA:

2

VLAN | MA

| MA NAME

| INDEX | ------|-------|---------------101 |

1

500 |

| TDM101 2

| VLAN500

699


15.2.17


CMD ID: ECFM_18 (MA SHOW)

ma [] show Description: shows the parameters of one MA and the list of associated MEPs. If the MA Index is not present, a summary table of all the MAs in the equipment is shown. Parameters: •

15.2.17.1

ma_index (optional) −

Range: 1-512

−

Description: identifies the MA in the equipment. If not present, all MAs in the NE are shown

WT CLI Tool Example for ECFM ma show command Example response for ma show command: MPR> ma show MA NAME | MA CREATION

| MD

| VLAN | LEVEL | CCM INT

| INDEX | INDEX |

|

|

| MIP-

| CRITERIA

--------|-------|-------|------|------|---------|-------------

15.2.17.2

TDM101 |

1

|

VLAN500 |

2

|

1 1

|

101 |

| 500 |

5 5

defer

| one-sec | defer

WT CLI Tool Example for ECFM ma show command Example response for ma show command: MPR> ma 1 show Maintenance Association ***********************

700

| one-sec |

1



NAME:

TDM101

FORMAT:

char-string

MD NAME:

Domain5

MD FORMAT:

char-string

MD INDEX:

1

MD LEVEL:

5

VLAN ID:

101

CCM INTERVAL:

one-sec

MIP-CREATION-CRITERIA: defer TOTAL MEPS: MPID |

TYPE

2 | STATUS |

PORT

| MAC

-----|-----------|--------|--------|-------------------

15.2.18

1 |

LOCAL |

Ena |

3/ 1 | 00:20:60:00:00:01

2 |

Remote |

OK |

-/ - | 00:20:60:00:00:0A

CMD ID: ECFM_19 (SHOW MP LOCAL)

ma show mp local Description: shows the parameters the local Maintenance Points associated with a MA. Parameters: •


Range: 1-512

−


701


15.2.18.1


WT CLI Tool Example for ECFM ma show mp local command Example response for ma show mp local command: MPR> ma 1 show mp local MPID | LEVEL | VLAN | PRIO | TYPE | DIR

| PORT | CC

| STATUS

-----|-------|------|------|------|------|------|-----|-----1

15.2.19

|

5

| 101

|

7

| Mep

|

Up

| 3/ 1 | Ena | Ena

CMD ID: ECFM_20 (SHOW MP REMOTE)

ma show mp remote Description: shows the parameters the remote MEP associated with a MA. These parameters are dynamically learnt observing the received CCM frames. Parameters: •

15.2.19.1


Range: 1-512

−


WT CLI Tool Example for ECFM ma show mp remote command Example response for ma show mp remote command: MPR> ma 1 show mp remote

702

MAC ADDRESS:

00:20:60:00:00:0A

MD NAME:

Domain5

MD LEVEL:

5

VLAN:

101



LOCAL MEP ID:

1

REMOTE MEP ID:

2

REMOTE MEP STATUS:

OK

REMOTE MEP RDI:

False

PORT STATUS TLV:

Port is up

INTERFACE STATUS TLV: Interface Up

15.2.20

CMD ID: ECFM_21 (SHOW ERRORS)

ma show errors Description: shows the errors currently present in a MA Parameters: •

15.2.20.1


Range: 1-512

−


WT CLI Tool Example for ECFM ma show errors command Example response for ma show errors command: MPR> ma 1 show errors MEP ID: 1 ********** LEVEL | VLAN | RMEP ID | DEFECT TYPE -------|------|---------|------------5

| 101

|

2

| CCM Defect

703


15.2.21


CMD ID: ECFM_22 (SHOW ERROR-LOG)

ma show error-log Description: shows the errors present in the error log table Parameters: •

15.2.21.1


Range: 1-512

−


WT CLI Tool Example for ECFM ma show error-log command Example response for ma show error-log command: MPR> ma 1 show error-log MEP ID:1

[PORT: 3/1]

********** TIME OF OCCURRANCE

| RMEP ID |

ERROR TYPE

| STATUS

-----------------------|---------|-----------------------|------26 June 2010 8:0:46 GMT | | Exit 26 June 2010 8:0:40 GMT | | Entry

15.2.22

2

2

|

Loss of Continuity

|

Loss of Continuity

CMD ID: ECFM_23 (CLEAR CCM DATABASE)

clear ccm database Description: clears dynamic information held by MEPs in the NE retrieved from the received CCMs

704



The CCM Database, after the command is performed, is re-populated according to CCMs received.

15.2.23

CMD ID: ECFM_24 (CLEAR ERRORS)

clear errors Description: clears all errors raised by MEPs in the NE. After the command is performed, errors are raised again according to the current alarm conditions.

15.2.24

CMD ID: ECFM_25 (CLEAR ERROR-LOG)

clear error-log Description: clears all errors contained in the error log table. After this command is performed, all the Entry or Exit events are lost and the error log is re-populated according to the new alarm state transitions.

15.3 15.3.1

Ethernet CFM scenarios Scenario1 Set the 802.1Q bridge mode. Create VLAN 100 on NE1 configuring the membership on Electrical Port 2 and Radio Port 2 on Slot 4. Create VLAN 100 on NE2 configuring the membership on Optical Port 6 and Radio Port 1 on Slot 6. Create a TDM2ETH with FlowID 50. Cross-connect, on NE1, PDH board on Slot 3 with Radio Port 2 on Slot 4. On NE2, cross-connect PDH board on Slot 5 with Radio Port 1 on Slot 6.

705


Figure 352


ECFM Scenario 1

15.3.1.1

Network Element 1 Configure a MD on Level 2, a MA and an Up MEP on Port 2 for VLAN 100. Configure a MD on Level 5, a MA and an Up MEP on Slot 3 for FlowID 50. MPR> md 1 create name Domain2 level 2 MPR> ma 1 create md 1 name Service100 vlan 100 interval one-sec MPR> ma 1 mep assign 1 MPR> ma 1 mep assign 2 MPR> mep 1:1 create direction up if 1/2 enable true MPR> mep 1:1 ccm enable true MPR> md 2 create name Domain5 level 5 MPR> ma 2 create md 2 name TDM2ETH50 vlan 50 interval one-sec MPR> ma 2 mep assign 1 MPR> ma 2 mep assign 2

706



MPR> mep 2:1 create direction up if 3/1 enable true MPR> mep 2:1 ccm enable true

15.3.1.2

Network Element 2 Configure a MD on Level 2, a MA and an Up MEP on Port 6 for VLAN 100. Configure a MD on Level 5, a MA and an Up MEP on Slot 5 for FlowID 50. MPR> md 1 create name Domain2 level 2 MPR> ma 1 create md 1 name Service100 vlan 100 interval one-sec MPR> ma 1 mep assign 1 MPR> ma 1 mep assign 2 MPR> mep 1:2 create direction up if 1/6 enable true MPR> mep 1:2 ccm enable true MPR> md 2 create name Domain5 level 5 MPR> ma 2 create md 2 name TDM2ETH50 vlan 50 interval one-sec MPR> ma 2 mep assign 1 MPR> ma 2 mep assign 2 MPR> mep 2:2 create direction up if 5/1 enable true MPR> mep 2:2 ccm enable true

15.3.2

Scenario1 - removal procedure Here is described the procedure to remove all the configurations done in Scenario1.

15.3.2.1

Network Element 1 MPR> mep 1:1 destroy

707



MPR> ma 1 mep remove 1 MPR> ma 1 mep remove 2 MPR> ma 1 destroy MPR> md 1 destroy MPR> mep 2:1 destroy MPR> ma 2 mep remove 1 MPR> ma 2 mep remove 2 MPR> ma 2 destroy MPR> md 2 destroy

15.3.2.2

Network Element 2 MPR> mep 1:2 destroy MPR> ma 1 mep remove 1 MPR> ma 1 mep remove 2 MPR> ma 1 destroy MPR> md 1 destroy MPR> mep 2:2 destroy MPR> ma 2 mep remove 1 MPR> ma 2 mep remove 2 MPR> ma 2 destroy MPR> md 2 destroy

15.3.3

Scenario2 Set the 802.1Q bridge mode.

708



Create VLAN 100 on NE1 configuring the membership on Electrical Port 2 and Radio Port 2 on Slot 4. Create VLAN 100 on NE2 configuring the membership on Electrical Port 2 and Radio Port 1 on Slot 6. Create VLAN 100 on NE3 configuring the membership on Electrical Port 1 and Optical Port 6. Create a TDM2ETH with FlowID 50. Cross-connect, on NE1, PDH board on Slot 3 with Radio Port 2 on Slot 4. On NE2, cross-connect PDH board on Slot 3 with Radio Port 1 on Slot 6. Create a TDM2ETH with FlowID 75. Cross-connect, on NE1, PDH board on Slot 3 with Radio Port 2 on Slot 4. On NE2, cross-connect Radio Port 1 on Slot 6 with Electrical Port 2. Set the NE MAC Address of NE3. On NE3, cross-connect PDH board on Slot 5 with Electrical Port 1. Set the NE MAC Address of NE2. Figure 353

ECFM Scenario 2

15.3.3.1

Network Element 1 Configure a MD on Level 2, a MA and an Up MEP on Port 2 for VLAN 100. Configure a MD on Level 5, a MA and an Up MEP on Slot 3 for FlowID 50. Configure a MA and an Up MEP on Slot 3 for FlowID 75.

709



MPR> md 1 create name Domain2 level 2 MPR> ma 1 create md 1 name Service100 vlan 100 interval one-sec MPR> ma 1 mep assign 1 MPR> ma 1 mep assign 2 MPR> mep 1:1 create direction up if 1/2 enable true MPR> mep 1:1 ccm enable true MPR> md 2 create name Domain5 level 5 MPR> ma 2 create md 2 name TDM2ETH50 vlan 50 interval one-sec MPR> ma 2 mep assign 1 MPR> ma 2 mep assign 2 MPR> mep 2:1 create direction up if 3/1 enable true MPR> mep 2:1 ccm enable true MPR> ma 3 create md 2 name TDM2ETH75 vlan 75 interval one-sec MPR> ma 3 mep assign 1 MPR> ma 3 mep assign 2 MPR> mep 3:1 create direction up if 3/1 enable true MPR> mep 3:1 ccm enable true

15.3.3.2

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

710



MPR> ma 2 create md 2 name TDM2ETH50 vlan 50 interval one-sec MPR> ma 2 mep assign 1 MPR> ma 2 mep assign 2 MPR> mep 2:2 create direction up if 3/1 enable true MPR> mep 2:2 ccm enable true MPR> ma 3 create md 2 name TDM2ETH75 vlan 75 mip-creation-criteria default

15.3.3.3

Network Element 3 Configure a MD on Level 2, a MA and an Up MEP on Port 6 for VLAN 100. Configure a MD on Level 5, a MA and an Up MEP on Slot 5 for FlowID 75. MPR> md 1 create name Domain2 level 2 MPR> ma 1 create md 1 name Service100 vlan 100 interval one-sec MPR> ma 1 mep assign 1 MPR> ma 1 mep assign 2 MPR> mep 1:2 create direction up if 1/6 enable true MPR> mep 1:2 ccm enable true MPR> md 2 create name Domain5 level 5 MPR> ma 2 create md 2 name TDM2ETH75 vlan 75 interval one-sec MPR> ma 2 mep assign 1 MPR> ma 2 mep assign 2 MPR> mep 2:2 create direction up if 5/1 enable true MPR> mep 2:2 ccm enable true

711


15.3.4


Scenario2 - removal procedure Here is described the procedure to remove all the configurations done in Scenario2.

15.3.4.1

Network Element 1 MPR> mep 1:1 destroy MPR> ma 1 mep remove 1 MPR> ma 1 mep remove 2 MPR> ma 1 destroy MPR> md 1 destroy MPR> mep 2:1 destroy MPR> ma 2 mep remove 1 MPR> ma 2 mep remove 2 MPR> ma 2 destroy MPR> mep 3:1 destroy MPR> ma 3 mep remove 1 MPR> ma 3 mep remove 2 MPR> ma 3 destroy MPR> md 2 destroy

15.3.4.2

Network Element 2 MPR> ma 1 destroy MPR> md 1 destroy MPR> mep 2:2 destroy MPR> ma 2 mep remove 1

712



MPR> ma 2 mep remove 2 MPR> ma 2 destroy MPR> ma 3 destroy MPR> md 2 destroy

15.3.4.3

Network Element 3 MPR> mep 1:2 destroy MPR> ma 1 mep remove 1 MPR> ma 1 mep remove 2 MPR> ma 1 destroy MPR> md 1 destroy MPR> mep 2:2 destroy MPR> ma 2 mep remove 1 MPR> ma 2 mep remove 2 MPR> ma 2 destroy MPR> md 2 destroy

15.4

Automatic MIP creation Automatic MIP Creation scenarios are shown combining different mip-creationcriteria values. MIPs are configured automatically, following the MIP Creation Criteria of their associated MD or MA. The automatic MIP creation follows this procedure: for each port P and VLAN X, it is done a list of MD Levels that contains: •

MD Levels of each of the MAs (if any) that includes VLAN X and a MEP configured on port P

713



•

MD Levels of each of the MAs (if any) that includes VLAN X and has an Up MEP configured on a port different from port P

•

MD Levels of each of the MAs (if any) that includes VLAN X and has no MEPs configured on any bridge port

From this list, the creation process selects the MA with the lowest MD Level D that: •

has not MEPs configured on port P and VLAN X at level D

•

and has not MEPs configured on port P and VLAN X at an higher level

Once the MA is selected, the rules of MIP creation are defined by either the MIP Creation Criteria of MA or the MIP Creation Criteria of the MD (if the MA parameter is set to Defer). The possible values of MIP Creation Criteria are:

15.4.1 Figure 354

•

None: no MIPs are created for this VLAN

•

Default: MIPs are created on any port of this VLAN where (1) there are no lower MD levels or (2) there is a MEP at the next lower MD level on the port

•

Explicit: MIPs are created on any port of this VLAN where there is a MEP at the next lower MD level on the port

Scenario 1

MIP creation scenario 1

MPR> md 1 create name Domain1 level 2 MPR> ma 1 create md 1 name Service1 vlan 100 mip-creation-criteria default

714


15.4.2 Figure 355


Scenario 2


MPR> md 1 create name Domain1 level 2 MPR> ma 1 create md 1 name Service1 vlan 100 mip-creation-criteria default MPR> md 2 create name Domain2 level 5 MPR> ma 2 create md 2 name Service2 vlan 100 mip-creation-criteria default (or explicit)

15.4.3 Figure 356

Scenario 3


715



MPR> md 1 create name Domain1 level 2 MPR> ma 1 create md 1 name Service1 vlan 100 MPR> ma 1 mep assign 1 MPR> ma 1 mep assign 2 MPR> mep 1:1 create direction up if 1/1 enable true MPR> md 2 create name Domain2 level 5 MPR> ma 2 create md 2 name Service2 vlan 100 mip-creation-criteria default (or explicit) If explicit is set, at the same way, MIP will be created only on port 1.

15.4.4 Figure 357

Scenario 4


MPR> md 1 create name Domain1 level 2 MPR> ma 1 create md 1 name Service1 vlan 100 MPR> ma 1 mep assign 1 MPR> ma 1 mep assign 2 MPR> mep 1:1 create direction down if 1/2 enable true MPR> md 2 create name Domain2 level 5

716



MPR> ma 2 create md 2 name Service2 vlan 100 mip-creation-criteria default If explicit is set, MIP will be created only on port 2.

15.5

Protocols The protocols setting commands are only available to users having an Administrator portfolio who are connected through SSH.

Table 63

Protocols commands

COMMANDS

DESCRIPTION

protocols enable {ftp|telnet|all}

Enables FTP, Telnet, or both

protocols disable {ftp|telnet|all}

Disables FTP, Telnet or both

protocols show

Shows the enabling status of the available protocols

help protocols

Shows the list of available commands

15.6

TACACS+ commands TACACS+ commands available in the WT CLI tool are listed in Table 64.

Table 64

TACACS+ commands

COMMANDS

DEFAULT VALUES

DESCRIPTION

tacplus enable {all|snmp|ssh|telnet|http}

Enables TACACS+ for all interfaces, SNMP only, SSH only, Telnet only or HTTP only.

tacplus disable {all|snmp|ssh|telnet|http}

Disables TACACS+ for all interfaces, SNMP only, SSH only, Telnet only, or HTTP only.

tacplus accounting enable {all|snmp|ssh|telnet}

Enables TACACS+ accounting for all interfaces, SNMP only, SSH only, or Telnet only.

717


Table 64


TACACS+ commands (Continued)

COMMANDS

DEFAULT VALUES

tacplus accounting disable {all|snmp|ssh|telnet}

DESCRIPTION

Disables TACACS+ accounting for all interfaces, SNMP only, SSH only, or Telnet only.

tacplus accounting size < max accounting packet size in bytes (2001400) >

900

Configures the maximum packet size used by the Accounting process. The range is from 200 to 1400 bytes; the default is 900 bytes.

tacplus server address addressv6 [secret ""] [port ] [timeout ] [attempts ]

secret "", port 49, timeout 3, attempts 1

Adds a Server to TACACS+ Server list with default values for the other Server parameters or configures the IP address parameter for an already-created Server. Index defines the Server index and its priority in the selection process (1 is the highest priority).

tacplus server address

Configures the related parameter for an already-created Server. Address is the IPv4 address of the Server. The parameter is mandatory when the Server is defined for the first time.

tacplus server addressv6

Configures the related parameter for an already-created Server. Address is the Global Unicast address of the Server, in IPv6 format. The parameter is mandatory when the Server is defined for the first time.

718


Table 64



COMMANDS

DEFAULT VALUES

DESCRIPTION

tacplus server secret “”

Configures the related parameter for an already-created Server. Secret is the shared secret used to encrypt the messages between NE (acting as TACACS+ Client) and Server, it is a string of up to 32 alphanumeric characters, it is optional having as default the empty string.

tacplus server port

Configures the related parameter for an already-created Server. Port is the TCP port where the Server is listening to, it is optional with range from 0 to 65535, default 49.

tacplus server timeout

Configures the related parameter for an already-created Server. Timeout is the timeout in seconds to declare as failed a connection attempt to Server, it is optional with range from 1 to 10 seconds, default 3 seconds.

tacplus server attempts

Configures the related parameter for an already-created Server. Attempts is the maximum number of connection attempts for the Server, it is optional with range from 1 to 3 attempts, default 1 attempt.

tacplus no server

Removes a Server from TACACS+ Server list.

tacplus holdoff

300

Configures the Holdoff time used by the Server selection process, range from 45 to 600 seconds, initial default 300 seconds.

719


Table 64



COMMANDS

DEFAULT VALUES

DESCRIPTION

tacplus show {all|ipv4|ipv6}

Shows TACACS+ configuration including Servers parameters and their status.

tacplus test

Starts a test which tries to setup connection the each Server in order to verify Server reachability and TACACS+ service availability.

help tacplus

This command shows the list of all the available commands.

15.7

Example of a TACACS+ Management Session on the 9500MPR Welcome to Nokia WT-CLI - Ver 0.1.4-reentrant

Figure 358

720

List of the available commands with the “help tacplus” command



Figure 359

Initial Settings: TACACS+ is disabled on all interfaces and there is no server configured

Figure 360

Provisioning server 1 (default settings but IP address) and showing the result

721



Figure 361

Provisioning server 1's key and showing the result

Figure 362

Performing a test (to check to server reachability and the server response time), then showing TACACS+ settings and status

722


Figure 363


Provisioning server 2 (specifying secret key) and showing the result

723



Figure 364

Provisioning server 2’s port (such that the server will not be reachable) and showing the result, then performing a test

Figure 365

Updating accounting packet size

724


Figure 366


Enabling TACACS+ Login for all management interfaces and showing settings and status (remark: server 2 is un-reachable)

Note: It is recommended always to enable all interfaces.

725


Figure 367


Enabling TACACS+ Accounting for all management interfaces and showing settings and status (remark: server 2 is un-reachable)

Note: Login must be enabled on an interface before accounting can be enabled.

726


Figure 368


Disabling TACACS+ Login for all management interfaces and showing settings and status (remark: server 2 is un-reachable)

Note: Accounting must be disabled before login can be disabled.

727


Figure 369

728


Enabling TACACS+ Login for SNMP management interfaces and showing settings and status (remark: server 2 is un-reachable), then performing a test



729


730




16 Provisioning Tool overview The Provisioning can be performed by using Provisioning Tool or WebEML. The Provisioning Tool provides an option to create and modify a provisioning file and apply it to an NE. Some equipment and parameters must be provisioned using WebEML. Note: Graphics in this chapter are examples.

16.1

Overview The Provisioning Tool is used to create and modify provisioning files. The Provisioning Tool allows you to prepare the provisioning in the back office, minimizing time on field and potential for error.

16.2

Provisioning tool screens The provisioning tool presents screens that reflect the provisioning selections previously made. Different screens will appear as you proceed depending on the selections made. The MSS Subrack panel appears on every screen, showing the units configured for each slot and the MPTs configured, if any. The slot currently being configured is shaded blue. The screens are presented in slot order: the Core-E configuration screen is always first, followed by the configuration screen for the unit configured in slot 3. Eight slots will appear in the tool. If you are provisioning an MSS-4, do not provision anything in slots 5 to 8. The graphics in this section are examples. The following buttons appear on every screen: •

Restore: allows to restore in the screen the initial data without any change

731

Release 7.0.0 3DB 19383 ACAA Issue 01 Provisioning Tool overview

16.2.1


•

Prev: the procedure goes back to the previous screen (the changed data may be lost after the Warning message)

•

Next: the procedure goes on to the next screen (some checks and data storage is done)

•

Cancel: the procedure goes back to the opening screen

•

Help: click on this button to open the help on line.

MSS Configuration The MSS Configuration screen allows the operator to configure the main MSS data by setting NE name and location, content for each slot, and protection configuration where available. The Protection scheme is always between two units on the same row. Generally, the user cannot modify the slot content while odd and even slots in a single row are in protection mode. Note: Protection for MPT-HC, MPT-HQAM, or MPT-XP units on the Core-E must be configured with WebEML.

The following cards can be configured in the ANSI market: •

Core-E

•

P32E1DS1_A

•

MPTACC

•

EASv2

The following cards can be configured in the ETSI market: •

Core-E

•

P32E1DS1

•

MOD300

•

MPTACC

•

SDH-ACC (SDH unit in transparent mode)

•

SDH-CHAN (SDH unit in channalized mode)

•

EASv2

All other units must be configured with WebEML.

732



Note: On this screen, the MPT-ACC unit cannot be configured in protected configuration.

In Figure 370, two unprotected P32E1DS1 units are installed in slots 3 and 4, MPTACC units are installed in slots 5 and 6, and EASv2 units are installed in slots 7 and 8. The Fan unit is configured in slot 9. Core-E protection is configured. Protection can be configured for the Core-E and P32E1DS1 units (the drop-down box is not dimmed), but not for the MPT-ACC or EASv2 units. Slot 9 supports the FANS or A_FANS units. Figure 370

MSS Configuration screen example

733


16.2.2


Core Configuration The Core Configuration screen contains the Core-E unit configuration with six Ethernet port configuration areas. Each Ethernet port configuration area contains parameters such as enabling/disabling the port itself, auto-negotiation and flow control enabling. Note: The Ethernet Advanced features of the Ethernet ports must be configured with WebEML.

A User Label can be added to the port if needed. The Ethernet ports can be configured in two ways: •

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

•

MPT-HC or MPT-HQAM: to be used to connect an MPT-HC to port#1 to port#4; an MPT-HC or MPT-HQAM to port#5 and port#6. Note: The Provisioning Tool does not distinguish between MPT-HC or MPT-HCHQAM and their -XP variants. For example, to configure an MPT-XP-HQAM choose MPT-HQAM.

Note: MPT-MC appears in the drop-down menu. The MPT-MC unit is not used in North America.

Ethernet port #4, if enabled, has three different Working modes: TMN, Transport or MPT-HC/MPT-HQAM. If TMN is selected, the Port 4 area is disabled and no configuration can be done on this screen for the port. Otherwise, when Transport is selected, the Port 4 area is completely enabled as for the other ports. If in port#5 and port#6 the Equip SFP plug-in check box is ticked and the Ethernet port is set as Transport the Autonegotiation protocol and the Flow Control can be enabled by selecting the relevant check box. The Speed - Duplex area will change depending on whether auto-negotiation is enabled or not.

734



As shown in Figure 371, if the auto-negotiation option is enabled (left side, “Port 1" area), the Speed-Duplex area will contain all available values usable by autonegotiation procedure. When auto-negotiation is disabled (right side, “Port 2" area), the user can select a fixed speed and direction pair in the “Speed - Duplex” area.

16.2.2.1

Synch-E From the six Ethernet traffic interfaces (configured as 1000 Mb/s) it is possible to recover the physical Rx synchronization signal. In transmission direction the clock of these interfaces will be locked to the NEC (network element clock). This feature is needed in order to realize “Synchronous Ethernet Networks” addressed by G.8261. Note: If the Ethernet port has to be used as Synchronous Source, the Ethernet port must be set as Slave.

735


Figure 371


Core Configuration screen example

16.2.3

Radio Configuration (ETSI market only) The Radio Configuration screen includes all the parameters needed to completely describe and configure an ODU300 unit. The Radio panel is split in many areas, each containing specific parameters.

16.2.3.1

SSM The SSM (Synchronization Status Message) can be enabled to be transmitted over the radio channel.

736


16.2.3.2


TMN-RF in band management

TMN-RF in band management contains information about routing protocols and methods. It allows the operator to select between the OSPF and Static Routing protocols for routing purposes. With OSPF a specific OSPF area can be associated with routing functions.

16.2.3.3

Revertive Restoration Criteria “Revertive Restoration Criteria” contains the EPS, RPS and TPS (Hot Standby) restoration criteria. If you put a check mark in the box the restoration criteria are “Revertive”; otherwise they are “Not Revertive”. Note: Do not enable the “Revertive” feature if you want traffic on the protection channel to stay on the protection channel, when alarms clear or a switch command is released. Traffic can be manually switched back to the main channel. Enable the “Revertive” feature if you want traffic on the protection channel to automatically switch back to the main channel, when alarms clear or a switch command is released.

16.2.3.4

Link Identifier When the Status is Enabled, this area contains information about expected and transmitted ID value that can be selected within specific range. The number for Transmitter ID must match the associated Transmitter ID at the other end of the hop. The number for Receiver ID must match the associated Receiver ID at the other end of the hop.

16.2.3.5

Structure The operation can be with Fixed or Adaptive Modulation. If the Reference Channel Spacing is 50 MHz in the Radio Profile check box, Std or High Gain can be selected.

737


16.2.3.6


Operation with Fixed Modulation Figure 372 shows the screen with fixed modulation.

Figure 372

MOD300 Configuration screen with fixed modulation

16.2.3.7

Operation with Adaptive Modulation Figure 373 shows the screen with adaptive modulation. The Adaptive Modulation is available only for unprotected (1+0) and Protected (1+1 HSB) Radio configuration without ATPC.

738


Figure 373


MOD300 configuration screen with adaptive modulation

The main idea behind Adaptive Modulation in Point to Point system is to adaptively adjust the modulation along with a range of other system parameters based on the near-instantaneous channel quality information perceived by the receiver, which is fed back to the transmitter with the aid of a feedback channel. The switching between the modulation schemes is hitless.

16.2.3.8

Channel area The most significant data in the radio panel are related to the “Channel” areas. The areas contain shifter values and Tx frequency fields to set specific parameters for each channel. The “Data Help” button will show an information dialog window containing the shifter list according to MPT types. See Figure 374 for an example.

739


Figure 374


ODU300 Channel Data Help window

Each “Channel” area also contains data and information for configuring ATPC or Manual Transmit Power Control. Content of those areas depend on ATPC activation status. If ATPC is “Enabled”, the set of three ATPC parameters is shown; if ATPC is disabled, the single manual Tx Power parameter is shown. The ATPC parameters are the min Tx power and max Tx power and the low Rx power at which the ATPC algorithm starts to operate. Note: With the Adaptive Modulation the ATPC is not supported.

16.2.3.8.1

Manual transmit power control (with Fixed Modulation)

If the ATPC is disabled the manual Tx Power field is present. In this field write the new value within the allowed transmitted power range. The range is shown on the right side of Manual Transmit Power Control area.

740


16.2.3.8.2


Manual transmit power control (with Adaptive Modulation)

In the 4 QAM field the operator has to enter the constant power, which will be used with 4 QAM modulation. The power range depends on the selected Reference mode. Note: The same power value will be used by the 16 QAM and 64 QAM modulation schemes.

16.2.4

MPT Access peripheral configuration The MPT Access peripheral configuration screen includes all the parameters needed to completely describe and configure an MPT-ACC unit. The following types of Outdoor Units, with different mechanical structure, can be connected to the MPT Access unit: •

MPT-HC

•

MPT-HQAM

The configuration is different according to the number of MPT-ACC units equipped in the same row: 1 or 2. Figure 375 shows the MPT Access peripheral screen with two MPTACC units in the row.

741


Figure 375


MPTACC configuration with two units in the row

In the MPT Access area enable the port to be used to interface the MPT for the MPT Access unit on the left side and on the right side. Port#1 and port#2 are electrical Ethernet ports; port#3 and port#4 are optical Ethernet ports. One or two ports can be enabled per MPT Access unit. Power type is also shown: •

PFoE (Power Feed over Ethernet) (one cable for Ethernet traffic + power supply) or

•

QMA (one cable for Power Supply and one cable for Ethernet traffic)

The MPT-HC and MPT-HQAM can use either PFoE or QMA.

742



In the MPT Protection Configuration area the Main port and the MPT Spare port and the protection configuration can be selected. In the example of the following figure s5p1 means Slot #5 Port #1. For the 1+1 configuration the ports must be both electrical or optical (no mixed configuration is allowed). The 1+1 configuration can be set up with two ports on the same unit or on two different units. The screen shown in Figure 376 shows a completed screen. Figure 376

1+1 configuration with MPTACC units

16.2.5

MPT configuration The following types of MPT can be configured using the Provisioning Tool:

743



•

MPT-HC

•

MPT-HLC

•

MPT-HQAM

The MPT panel is split in many areas, each containing specific parameters.

16.2.5.1

User label A label can be inserted in this field to identify the radio direction.

16.2.5.2

SSM area The SSM (Synchronization Status Message) can be enabled to be transmitted over the radio channel.

16.2.5.3

PPP RF in band management area

The PPP RF in band management area contains information about routing protocols and methods. It allows to select between OSPF and Static Routing protocols for routing purposes. With OSPF a specific OSPF area can be associated with routing functions or disabled.

16.2.5.4

RPS Configuration In a protection configuration, enable the Physical Cable check box if a physical RPS cable is in use.

16.2.5.5

Revertive Restoration Criteria area “Revertive Restoration Criteria” contains the EPS, RPS and TPS (Hot Standby) restoration criteria. If you put a check mark in the check box the restoration criteria are “Revertive”; otherwise they are “Not Revertive”.

744



Disable the “Revertive” feature if you want traffic on the protection channel to stay on the protection channel, when alarms clear or a switch command is released. Traffic can be manually switched back to the main channel. Enable the “Revertive” feature if you want traffic on the protection channel to automatically switch back to the main channel, when alarms clear or a switch command is released.

16.2.5.6

XPIC Configuration This field is available when an XPIC modem profile has been chosen in the Data Help window. The XPIC can be configured in 1+0 or 1+1 HSB (with or without adaptive modulation). Note: Not all the channel spacings and modulation schemes can support the XPIC Configuration.

16.2.5.7

Link Identifier area When the Use Link Identifier box is checked, this area contains information about expected and transmitted ID value that can be selected within a specific range. Enter a number from 1 to 255 for Expected. The number must match the associated Transmitter ID at the other end of the hop. Enter a number from 1 to 255 for Transmitted. The number must match the associated Receiver ID at the other end of the hop.

16.2.5.8

Structure area The operation can be with Fixed or Adaptive Modulation.

16.2.5.8.1

1+0 Operation with Fixed Modulation

Figure 377 shows the configuration screen for 1+0 configuration with fixed modulation.

745


Figure 377


MPT configuration showing MPT-HQAM (1+0 with fixed modulation)

16.2.5.8.2

1+0 Operation with Adaptive Modulation

The Adaptive Modulation is available without ATPC in the Provisioning Tool. ATPC with Adaptive Modulation must be configured in JUSM. Figure 378 shows the configuration screen for 1+0 configuration with adaptive modulation.

746


Figure 378


MPT configuration screen (1+0 with adaptive modulation)

The main idea behind Adaptive Modulation in Point to Point system is to adaptively adjust the modulation along with a range of other system parameters based on the near-instantaneous channel quality information perceived by the receiver, which is fed back to the transmitter with the aid of a feedback channel. The switching between the modulation schemes is hitless.

16.2.5.9

Channel area The most significant data in the radio panel are related to the Channel areas. The areas contain shifter values and Tx frequency fields to set specific parameters for each channel. The Data Help button will show an information dialog window containing the shifter list according to MPT types. See Figure 379 for an example.

747



The Data Help window provides the range of allowed transmit frequencies for each part number and shifter. The ranges for transmit and receive frequencies are displayed in the Channel area when a value has been selected. The following rule applies for calculating the receive frequency: •

If the minimum Tx Frequency is lower than the minimum Rx Frequency (low band): Rx Frequency = Tx Frequency + Shifter

•

If the minimum Tx Frequency is higher than the minimum Rx Frequency (high band): Rx Frequency = Tx Frequency - Shifter

The operator must ensure that the correct values are entered and that the transmit and receive frequencies match the other end of the hop. Figure 379

Data Help window for the Channel area

In a 1+1 configuration, Channel 0 is also available. In HSB configuration the shifter value is the same for both channels, see Figure 380. In FD configuration the two channels can have different shifter values, see Figure 381.

748


Figure 380


1+1 HSB Configuration

749


Figure 381


1+1 FD Configuration

16.2.5.9.1

ATPC

Each Channel area also contains data and information for configuring ATPC or Manual Transmit Power Control. Content of those areas depend on ATPC activation status. If ATPC is “Enabled”, the set of three ATPC parameters is shown; if ATPC is disabled, the single manual Tx Power parameter is shown. The ATPC parameters are the min Tx power and max Tx power and the low Rx power at which the ATPC algorithm starts to operate. Note: With the Adaptive Modulation the ATPC is not supported.

750


16.2.5.9.2


Manual transmit power control (with Fixed Modulation)

If the ATPC is disabled the manual Tx Power field is present. In this field write the new value within the allowed transmitted power range. The range is shown on the right side of Manual Transmit Power Control area.

16.2.5.9.3

Manual transmit power control (with Adaptive Modulation)

In the Tx power field the operator has to enter the constant power, which will be used with the reference modulation.

16.2.6

P32E1DS1 unit configuration for the ANSI market The DS1 configuration screen contains the list of all 32 DS1 tributaries with Impedance and Restoration criteria configuration areas. You can modify each tributary by itself or use the ‘One-Shot’ Tributaries Configuration feature to configure all tributaries at the same time. The One-Shot Tributaries Configuration allows the operator to configure the following for all tributaries: •

Signal Mode column: allows changing all tributaries from Disabled to Framed, Unframed, Framed SF or Framed ESF

•

Service Profile: TDM2TDM or TDM2Eth

•

Flow ID: is unique in the network. Enter a flow ID in the One-Shot Tributaries Configuration to provide the Flow ID for port #1. The tool will number the other tributaries consecutively from the number entered.

•

Payload size: the payload size is fixed at 192 bytes.

•

ECID TX: Tx Over-the-hop ID. Must match the Rx ID at the other end. Enter an ID in the One-Shot Tributaries Configuration to provide the ECID for port #1. The tool will number the other tributaries consecutively from the number entered.

•

ECID RX: Rx Over-the-hop ID. Must match the Tx ID at the other end. Enter an ID in the One-Shot Tributaries Configuration to provide the ECID for port #1. The tool will number the other tributaries consecutively from the number entered.

751


16.2.6.1


•

TDM Clock Source: Adaptive or Differential.

•

Line Length

•

Line Coding

DS1 parameters The following parameters can be configured for each DS1 port: •

Signal Mode: the DS1 configuration (Disabled/Unframed/Framed SF/Framed ESF). If the signal mode is Framed, the performances regarding this DS1 stream can be collected at the input in Tx side and at the output in Rx side.

•

Service profile: −

Choose TDM2TDM if radio is being used to transport DS1 data only (no Ethernet).

−

Choose TDM2ETH if radio is being used to transport just Ethernet or Ethernet plus DS1 data.

•

Flow ID: is unique in the network. No two Flow IDs in a network can be the same.

•


•

ECID Tx: Tx Over-the-hop ID

•

ECID Rx: Rx Over-the-hop ID. Must match Tx ID at other end.

•

TDM Clock Source: The purpose of TMN Clock Source provisioning is to select the mode, that will be used to sync TDM DS1 data to the node Synchronization source. The user can select one of the two modes: Adaptive or Differential. −

Select Adaptive to sync TDM output to packets.

−

Select Differential to sync TDM output to NE Synchronization source.

•

Line Coding: choose AMI or B8ZS.

•

Line Length: the distance to the cross-connection. The range is 0 to 655.

With the TDM2TDM service profile the TDM Clock Source is fixed to Differential (RTP - Real Time Protocol is used); with the TDM2Eth service profile the TDM Clock source can be Differential (RTP - Real Time Protocol is used) or Adaptive (RTP is not used). In the unit it is not possible to have mixed configurations with service profiles using RTP and other service profiles not using RTP.

752



Example: if one DS1 on the card has the TDM2TDM service profile it is possible to configure another DS1 with the TDM2Eth service profile only with the Differential clock source. If a DS1 with an Adaptive clock source is required, it must be configured for a DS1 on a different P32E1DS1 card. Figure 382 shows the DS1 configuration screen. Figure 382

DS1 configuration screen

The following parameters apply to all ports: •

AIS Insertion for LOF detection on DS1: select Enabled or Disabled. This setting is applied to all DS1 modules according to the value of the field for the module with the highest slot value: it is not applied on a per tributary basis.

•

Restoration Criteria: for 1+1 EPS are fixed to “Not Revertive” and cannot be changed.

753



As for all other screens, all the data are checked and validated with respect to existing configuration when the user clicks on the “Next” button. There are many different checks, each one with its own error message (example: Flow ID value error message, Payload value error message, ECID Tx value error message, ECID Rx value error message).

16.2.7

P32E1DS1 unit configuration for the ETSI market The E1 configuration screen contains the list of all 32 E1 tributaries with Impedance and Restoration criteria configuration areas. You can modify each tributary by itself or use the ‘One-Shot’ Tributaries Configuration feature to configure all tributaries at the same time. The One-Shot Tributaries Configuration allows the operator to configure the following for all tributaries: •

Signal Mode column: allows changing all tributaries from Disabled to Unframed or Framed

•

Service Profile: TDM2TDM or TDM2Eth

•

Flow ID: is unique in the network. nter a flow ID in the One-Shot Tributaries Configuration to provide the Flow ID for port #1. The tool will number the other tributaries consecutively from the number entered.

•


•

ECID TX: Tx Over-the-hop ID. Must match the Rx ID at the other end. Enter an ID in the One-Shot Tributaries Configuration to provide the ECID for port #1. The tool will number the other tributaries consecutively from the number entered.

•

ECID RX: Rx Over-the-hop ID. Must match the Tx ID at the other end. Enter an ID in the One-Shot Tributaries Configuration to provide the ECID for port #1. The tool will number the other tributaries consecutively from the number entered.

•

16.2.7.1

TDM Clock Source: Adaptive or Differential.

E1 parameters The following parameters can be configured for each E1 port:

754


•


Signal Mode: the E1 configuration (Framed/Unframed). If the configuration is Framed, the performances regarding this E1 stream can be collected at the input in Tx side and at the output in Rx side.

•

Service profile: −

Choose TDM2TDM if radio is being used to transport E1 data only (no Ethernet).

−

Choose TDM2ETH if radio is being used to transport just Ethernet or Ethernet plus E1 data.

•

Flow ID: is unique in the network. No two Flow IDs in a network can be the same.

•


•

ECID TX: Tx Over-the-hop ID

•

ECID RX: Rx Over-the-hop ID. Must match Rx/Tx ID at other end.

•

TDM Clock Source: The purpose of TMN Clock Source provisioning is to select the mode, that will be used to sync TDM E1 data to the node Synchronization source. The user can select one of the two modes: Adaptive or Differential. −

Select Adaptive to sync TDM output to packets.

−

Select Differential to sync TDM output to NE Synchronization source.

With the TDM2TDM service profile the TDM Clock Source is fixed to Differential (RTP - Real Time Protocol is used); with the TDM2Eth service profile the TDM Clock source can be Differential (RTP - Real Time Protocol is used) or Adaptive (RTP is not used). In the unit it is not possible to have mixed configurations with service profiles using RTP and other service profiles not using RTP. For example: if one E1 on the card has the TDM2TDM service profile it is possible to configure another E1 with the TDM2Eth service profile only with the Differential clock source. If a DS1 with an Adaptive clock source is required, it must be configured for an E1 on a different P32E1DS1 card. Figure 383 shows the E1 configuration screen.

755


Figure 383


E1 configuration

The following parameters apply to all ports: •

Impedance: select the impedance to be used for the E1 streams (Unbalanced 75 ohm or Balanced 120 ohm).

•

Restoration Criteria: for 1+1 EPS are fixed to “Not Revertive” and cannot be changed.

•

Node Timing: timing from the network element clock as defined in G.8261. The enabling of the Node Timing is applied to all E1s of the PDH unit. By enabling the Node Timing the E1 streams in Rx side are retimed at the output with the network element clock.

As for all other screens, all the data is checked and validated with respect to existing configuration when the user clicks on the “Next” button.

756



There are many different checks, each one with its own error message (example: Flow ID value error message, Payload value error message, ECID Tx value error message, ECID Rx value error message).

16.2.8

SDH unit configuration (ETSI market only) The SDHACC configuration screen contains the configuration of the SDH unit. The SDH unit can be used in two different working modes, addressing two different network scenarios: •

STM-1 transparent (SDH-ACC)

•

STM-1 channelized (SDH-CHAN)

The STM-1 channelized mode is available by provisioning the unit as “SDH-CHAN” and the STM-1 transparent mode is available by provision the unit as “SDH-ACC”. The SDH 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. 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).

16.2.8.1

SDHACC Configuration Figure 384 shows the configuration screen for SDHACC.

757


Figure 384


SDHACC configuration screen

16.2.8.2

SDHCHAN Configuration Figure 385 shows the configuration screen for SDHCHAN.

758


Figure 385


SDHCHAN configuration screen

All the E1s can be configured in one shot by entering the following parameters in the “One Shot” Tributaries Configuration: •

Service Profile The available profiles are: −

TDM2TDM

−

TDM2Eth

•

Flow Id: To implement cross-connections between line side and radio side each E1 tributary must be associated with an identifier. Enter the Flow identifier value in the relevant field (possible values: 2 to 4080).

•

The ECID Tx, ECID Rx, Payload Size and TDM Clock Source fields can be written only if the Service Profile is TDM2Eth.

759


16.2.9


EASv2 unit configuration The EASv2 configuration screens contain the configuration of the electrical and optical ports on the EASv2 unit and configuration of protection of the MPTs connected to stacked EASv2 cards. Note: The Ethernet Advanced features of the Ethernet ports can be configured only with WebEML.

16.2.9.1

Configure electrical ports Click on the Electrical tab to configure the electrical ports (ports #1 to #4) and the Optical tab to configure the optical ports (ports #5 to #8). A User Label can be added to the port if needed. The ports can be configured in two ways: •

Transport: to be used as GigaEthernet interface for Ethernet traffic

•

MPT-HC or MPT-HQAM: to be used to connect MPT-HC or MPT-HQAM. Note: The Provisioning Tool does not distinguish between MPT-HC or MPT-HCHQAM and their -XP variants. For example, to configure an MPT-XP-HQAM choose MPT-HQAM.

Note: MPT-MC appears in the drop-down menu. The MPT-MC unit is not used in North America.

If the Ethernet port is set as “Transport” the Autonegotiation protocol and the Flow Control can be enabled by selecting the relevant check box. The “Speed - Duplex” area will change depending on whether auto-negotiation is enabled or not. As shown in Figure 386, if auto-negotiation option is enabled (left side, “Port 1" area), the Speed-Duplex area will contain all available values usable by the autonegotiation procedure. If auto-negotiation is disabled (right side, “Port 2" area), the user can select a fixed speed and direction pair with a different content of “Speed Duplex” area.

760


Figure 386


EASv2 configuration screen: electrical ports

16.2.9.1.1

Synch-E From the Ethernet traffic interfaces (configured as 1000 Mb/s) it is possible to recover the physical Rx synchronization signal. In transmission direction the clock of these interfaces will be locked to the NEC (network element clock). This feature is needed in order to realize “Synchronous Ethernet Networks” addressed by G.8261. To enable the Synch-E in Port Configuration field put a check mark in the Auto Negotiation box, then tick on Synchronous and select the operating mode: Master or Slave. The SSM (Synchronization Status Message) message can also be enabled. Note: If the Ethernet port has to be used as Synchronous Source, the Ethernet port must be set as Slave.

761


16.2.9.1.2


Power Source

If the port has been configured for an MPT and will be used as a power source, choose PFoE.

16.2.9.2

Configure optical ports If the “Equip SFP plug-in” check box is selected and the Ethernet port is set as “Transport” the Autonegotiation protocol and the Flow Control can be enabled by selecting the relevant check box. A User Label can be added to the port if needed. The ports can be configured in two ways. The optional SFP must be installed. •

Transport: to be used as GigaEthernet interface for Ethernet traffic (Note: for optical ports the optional SFP must be installed)

•

MPT-HC, MPT-HLC, or MPT-HQAM: to be used to connect MPT-HC, MPTHLC or MPT-HQAM Note: The Provisioning Tool does not distinguish between MPT-HC or MPT-HCHQAM and their -XP variants. For example, to configure an MPT-XP-HQAM choose MPT-HQAM.

Note: The Ethernet Advanced features of the Ethernet ports can be configured only with WebEML.

If the Ethernet port is set as “Transport” the Autonegotiation protocol and the Flow Control can be enabled by selecting the relevant check box. The “Speed - Duplex” area will change depending on whether auto-negotiation is enabled or not. As shown in Figure 387, if auto-negotiation option is enabled (left side, “Port 1" area), the Speed-Duplex area will contain all available values usable by auto-negotiation procedure. Whether auto-negotiation is disabled (right side, “Port 2" area), the user can select a fixed speed and direction pair with a different content of “Speed Duplex” area.

762


Figure 387


EASv2 configuration screen: optical ports

16.2.9.2.1

Synch-E From the Ethernet traffic interfaces (configured as 1000 Mb/s) it is possible to recover the physical Rx synchronization signal. In transmission direction the clock of these interfaces will be locked to the NEC (network element clock). This feature is needed in order to realize “Synchronous Ethernet Networks” addressed by G.8261. To enable the Synch-E in Port Configuration field put a check mark in the Auto Negotiation box, then tick on Synchronous and select the operating mode: Master or Slave. The SSM (Synchronization Status Message) message can also be enabled. Note: If the Ethernet port has to be used as Synchronous Source, the Ethernet port must be set as Slave.

763


16.2.9.3


Two EASv2 units on the same row Figure 388 shows EASv2 units in slots 7 and 8.

Figure 388

EASv2 protection configuration

In the MPT Protection Configuration area select the MPT Main port and the MPT Spare port (in the example figure s7p5 means Slot #7 Port #5) and in the Prot Type field select the protection configuration: 1+1 HSB or 1+1 FD. After the selection click on ADD to set up the protection; see Figure 389.

764


Figure 389


EASv2 protection

Click on the Next button to configure the MPTs. After one port is enabled the screen for MPT configuration appears.

16.2.10

LAG configuration

The LAG configuration screen allows the operator to configure L1 Radio LAG. Other types of LAG must be configured using WebEML. The LAG configuration screen appears regardless of whether a radio has been configured. See Radio L1 LAG for general information about LAGs, ports allowed in a LAG and LAG restrictions.

765


16.2.10.1


LAG configuration procedure The procedure to configure a LAG using the provisioning tool is the same as the procedure to create a LAG using WebEML. Figure 390 shows the LAG configuration screen.

Figure 390

LAG configuration screen

When the LAG is configured, the radio icons for the radios in the LAG show an L symbol in the MSS Subrack panel: ( )

766


16.2.11


XPIC configuration

The XPIC Configuration screen allows the operator to configure the XPIC. The polarization of the MPTs must be configured on the MPT configuration screen. The XPIC configuration screen appears regardless of whether a radio has been configured. Two XPIC configurations can be implemented: •

1+0 XPIC

•

1+1 XPIC

The 1+1 XPIC Configuration consists of two groups of 1+ HSB with different polarization. Figure 391 shows the XPIC Configuration screen.

767


Figure 391


XPIC configuration

XPIC Configuration is available only with the MPT-HC or MPT-HQAM with an option with XPIC (1+0 or 1+1 HSB with or without Adaptive Modulation) configured in the Radio menu and with a suitable polarization (vertical or horizontal) as shown in Figure 392.

768


Figure 392


Polarization in the MPT Configuration screen

16.2.12

Synchronization configuration The Synchronization configuration screen allows the operator to configure the synchronization. The synchronization data are needed to specify how to detect and use signal synchronization methods. The “Role” area states the type of working mode the NE will adopt to synchronize its signal with other NEs. “Sources” area asks to the user to describe how the synchronization shall be managed. Then, for each configured source a specific “Source Configuration” area contains detail configuration parameters depending on synchronization source type. A “Synch-out port” can be configured as well.

769



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. Figure 393 shows the synchronization configuration screen. Figure 393

Synchronization Configuration screen

16.2.12.1

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

770



The NEC is locked to a Synchronization Source. The NEC is locked to a Synchronization Source.

16.2.12.2

Synchronization Sources assignment The physical interfaces to be assigned to Primary and Secondary synchronization sources can be chosen among the following in the Master synchronization role: •

Free Run Local Oscillator. Quality Level value is fixed to QL-SEC/EEC1 (G.812/G8262), the value of QL Priority is Master1 if the NEC is configured as Master and Slave1 if the NEC is configured as Slave.

•

Any E1/DS1 available at input traffic interfaces (the specific port has to be chosen). Default value for Quality Level is QL-SSU-A (G.812), the value of QL Priority is Master1 if the NEC is configured as Master and Slave1 if the NEC is configured as Slave.

•

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 exception: timing correctly scaled from 2.048 MHz to 1.024 MHz

•

Any Available Synch-E clock source at enabled User Ethernet traffic interfaces (both electrical and optical) configured in synchronous operation mode (the specific User Ethernet port has to be chosen).

•

From ITU-T G.8261 point of view, the MSS is a Synchronous Ethernet equipment equipped with a system clock (NEC) following the ITU-T G.8262 recommendation. A User Ethernet interface 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 CT/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 equipments.

771



For Synchronous Ethernet clock sources from electrical User Ethernet ports the Fail alarm will be raised when Loss of Synch (that is, Ethernet Link Down) occurs. For Synchronous Ethernet clock sources from optical User Ethernet ports the Fail alarm will be raised when Loss of Optical signal occurs. •

Any STM1 available at SDH input traffic interfaces (the specific STM1 port must be selected). Default value for Quality Level is QL-SSU-A (G.812), the value of QL Priority is Master1 if the NEC is configured as Master and Slave1 if the NEC is configured as Slave.

For a secondary source in the Master role, the synchronization source can also be set to None. The physical interfaces to be assigned to Primary and Secondary synchronization sources can be chosen among the following in the Slave synchronization role: •

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 exception: timing correctly scaled from 2.048 MHz to 1.024 MHz

772

•

Any available radio, which can be selected from a drop-down menu. A LAG can also be selected.

•

Any Synch-E clock source available at enabled User Ethernet traffic interfaces (both electrical and optical) configured in synchronous operation mode (the specific User Ethernet port has to be chosen).

•

From ITU-T G.8261 point of view, the MSS is a Synchronous Ethernet equipment equipped with a system clock (NEC) following the ITU-T G.8262 recommendation. A User Ethernet interface 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 CT/ 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 equipments. For Synchronous Ethernet clock sources from electrical User Ethernet ports the Fail alarm will be raised when Loss of Synch (that is, 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 occurs. The following are available for secondary sources only in the Slave role:

16.2.12.3

•

Free Run Local Oscillator. Quality Level value is fixed to QL-SEC/EEC1 (G.812/G8262), the value of QL Priority is Master1 if the NEC is configured as Master and Slave1 if the NEC is configured as Slave.

•

Any E1/DS1 available at input traffic interfaces (the specific port has to be chosen). Default value for Quality Level is QL-SSU-A (G.812), the value of QL Priority is Master1 if the NEC is configured as Master and Slave1 if the NEC is configured as Slave.

•

None

Synch-out port configuration The NEC can be available to the user on a dedicated Sync-Out port configurable according to the following options:

16.2.13

•

2.048 MHz, electrical levels according G.703, clause 13

•

5 MHz, + 6 dBm into 50 ohm, sine-wave

•

10 MHz, + 6 dBm into 50 ohm, sine-wave

•

1.024 MHz, electrical levels according to G.703, clause 13 with the following exception: timing correctly scaled from 2.048 MHz to 1.024 MHz

QoS configuration

The QoS Configuration only refers to queues Q1-Q5. The QoS Configuration menu has 3 screens: •

Scheduler Configuration

•

Queue Size Configuration

•

QoS Classification

773


16.2.13.1


Scheduler Configuration screen Figure 394 shows the Scheduler Configuration screen, showing the default configuration.

Figure 394

Scheduler Configuration screen

For each queue the Mode (SP/DWRR) and the relevant Weight (in the 1-32 range) can be assigned.

16.2.13.2

Queue Size configuration screen Figure 395 shows the Queue Size configuration screen.

774


Figure 395


Queue size configuration screen

For each queue and for each radio direction the buffer size (in Bytes) can be assigned.

16.2.13.3

QoS Classification screen The classification can be disabled or done according to: •

IEEE 802.1p

•

DiffServ

Select the classification in the QoS Classification Criterion field; see Figure 396.

775


Figure 396


QoS classification screen

16.2.13.3.1

IEEE 802.1p Figure 397 shows the IEEE 802.1p configuration screen, with default settings.

776


Figure 397


IEEE 802.1p

The classification of the Priority Code Point to a specific queue takes place in two steps: •

From the Priority Code Point (P#) to the FC (Forwarding Class): on the left area of the screen

•

From the FC (Forwarding Class) to the Egress Queue (Q#): on the right area of the screen. This association is fixed and cannot be changed.

777


Figure 398


IEEE 802.1p classification change

16.2.13.3.2

DiffServ

Figure 399 shows the DiffServ configuration screen, with the default settings.

778


Figure 399


DiffServ

The classification of the DiffServ Code Point to a specific queue takes place in two steps:

16.2.14

•

From the DiffServ Code Point (#) to the FC (Forwarding Class): on the left area of the screen

•

From the FC (Forwarding Class) to the Egress Queue (Q#): on the right area of the screen. This association is fixed and cannot be changed.

Bridge configuration

You can configure different ways to manage the Ethernet traffic using the provisioning tool: •

802.1D (MAC Address Bridge)

779


•


802.1Q (Virtual Bridge). This is the default in the ANSI market.

Note: 802.1ad (Provider Bridge) must be configured using WebEML.

The MSS Subrack panel does not appear in the Bridge configuration screen by default. Click on the MSS Summary button to view it.

16.2.14.1

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

780


Figure 400


802.1D VLAN management

16.2.14.2

802.1Q When the NE is configured in this mode, the management of Ethernet traffic looking at the VLAN is enabled. In this mode, one VLAN will be assigned to all Ethernet frames inside the MPR network. Figure 401 shows the 802.1Q screen.

781


Figure 401


802.1Q VLAN management (default VLAN only)

VLAN 1 Management: •

VLAN-ID 1 is automatically defined by the NE when the 802.1Q bridge type is selected.

•

VLAN-ID 1 is shown to the operator, but it can be neither changed nor deleted.

•

All the user Ethernet ports (enabled and disabled) and all the radio ports are members of the VLAN 1.

•

In egress VLAN-ID 1 is always removed from all the ports.

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

782


16.2.15


Port VLAN configuration

The Port VLan Configuration screen opens only if the 802.1Q (Virtual Bridge) has been selected on the Bridge Configuration screen. Figure 402 shows the configuration tab for the six ports of the Core-E card. Figure 403 shows the configuration tab for the eight ports of the EASv2 card. Only Ethernet ports can be configured. The untagged frames, received on each user Ethernet port on the Core-E (port 1 to 4, and ports 5 and 6 if the optical SFP plug-in has been installed and configured) or EASv2 card (port 5 to 8), can be Accepted or Discarded. If the untagged frames are accepted, the VLAN-ID and Priority fields must be configured. Only VLAN-ID values already defined (in the VLAN management menu) can be configured for this purpose. The Priority values allowed are in the range 0 - 7. The default Port VLAN-ID and Priority values are: VLAN-ID=1; Priority=0. VLAN 1 is always removed, when the frame is forwarded.

783


Figure 402

784

Port VLAN configuration - Core-E ports



Figure 403


Port VLAN configuration - EASv2 ports

16.2.16

Network configuration The network configuration screen allows the operator to configure the network parameters. The NE has the following IP addresses: •

Local IP Address: it is the Controller IP address (default IP address = 10.0.1.2 with fixed mask 255.255.255.255)

•

NMS Ethernet Port IP address: it is the IP address relevant to the Ethernet TMN port (default IP address = 10.0.1.2 with mask 255.255.255.0)

•

NMS Ethernet Port 4 IP address: the Ethernet Port 4 can be used for traffic or TMN depending on the configuration on the Core Configuration screen.

785


•


TMN In-Band interface #1, IP/subnet;TMN In-Band interface #2, IP/subnet

User Ethernet port 4 can then used as: •

pure Ethernet traffic interface

•

pure Out-of-band TMN Local Ethernet interface

•

Ethernet traffic interface carrying TMN In-Band traffic

The NE Local IP Address can be reused on one of the other TMN interfaces. These interfaces must have different IP subnets. Figure 404 shows an example network. Figure 404

Network configuration example

“Local IP Address” area local IP address for NE with the simple and widely used decimal dot notation. Networking parameters goes further by configuring Ethernet. Enabling TMN allows setting IP data (address and mask) together with routing protocol, the same way as for “TMN-RF in band management” in the MPT menus. Warning: If remote NEs have to be reached from this NE, you need to configure the Routing Protocol of the TMN-RF channel, if the remote NE is connected through the radio link or of the NMS Ethernet Port, if the remote NE is connected through the Ethernet cable.

Port 4 area will be configurable if ETH4 area in Core configuration screen would be set in “TMN” Working Mode. If the area is enabled, it behaves the same as for Ethernet Configuration. For each “TMN In-Band interface” the following parameters must be selected: •

786

IP address and subnet: default 10.0.3.2/24 for interface #1 and 10.0.4.2/24 for interface #2



•

VLAN ID: no default ID for interface #1 and interface #2 (Note: if the two interfaces are disabled, the VLAN ID will appear in the final report as undefined).

•

List of User Ethernet interfaces where transmit/receive TMN In-Band traffic: default None (multiple selection with the mouse can be done)

•

Routing Protocol: Static Routing or OSPF. The default is Static Routing.

•

Area ID in case of OSPF protocol enabled: from 0 to 3

The configuration panel contains also “Static Routing” and “OSPF Areas” Configurations. Both are shown as tables with simple management to add/remove rows containing data that can be directly edited. Configuration of the PCP and DSCP fields of the VLAN tag is not supported by the Provisioning Tool. Default values are applied. Figure 405 shows the Network Configuration screen.

787


Figure 405


Network Configuration screen

At the bottom of the Network Configuration screen the screen contains the Network Time Protocol area, used to configure NTP servers.

16.2.17

Trusted managers You can configure up to five trusted managers. A Trusted manager is an SNMP manager to which the NE automatically sends the traps generated inside the NE. Figure 406 shows the trusted managers screen.

788


Figure 406


Trusted Managers screen

16.2.18

Final report The configuration report panel shows a summary of the selected parameters and configurations. The user can go back to the configuration screens or save the configuration as shown. Configuration information is saved in MCML (XML-based) format. Note: Since MCML configuration files are XML-based, they contain simple text characters with specific tags to identify information. This allows the user to possibly modify the file manually. However, configuration files not strictly fulfilling XML and MCML grammar and structure cannot be considered correct and used by TCO Tools management. Such manual modification is strongly discouraged.

789



The Report Panel also shows the MPR version; see Figure 407. Figure 407

790

Configuration report


Web Server overview

17 Web Server overview 17.1

General Web Server allows the user to perform some management functions using a web browser. Web Server is available when a Core-E card is in use. If a CorEvo card is in use, the web-based tool is WebCT, see WebCT overview. See the 9500 MPR WebEML User Manual for procedures using Web Server. See the 9500 MPR WebCT User Manual for procedures using WebCT. Web Server provides configuration information, alarms and administration functions. The following items appear in the Main Menu: •

Configuration

•

Alarms

•

DHCP

•

Administration

791

Release 7.0.0 3DB 19383 ACAA Issue 01 Web Server overview


Figure 408 shows the Web Server. Figure 408

Web Server

17.1.1

Configuration The configuration menu offers the following options:

17.1.2

•

Date & Time Setting: allows the user to administer date and time settings.

•

Configuration Setting: allows the user to apply a configuration file to an NE that has not yet been configured.

•

Configuration Info: choose this option to download a configuration file. The file is the same as the one created by the Provisioning Tool.

Alarms Click on Active Alarms to view the alarms for the NE.

792


17.1.3

Web Server overview

DHCP

Click on DHCP Setting to view or change the DHCP setting. DHCP can also be controlled from the System Settings menu.

17.1.4

Administration The administration menu offers the following options: •

License Info: allows the user to view the RMU Serial Number and License String.

•

Community Strings: allows the user to manage the Community String.

•

Snmp version: allows the user to view or change the SNMP version. This can also be performed from the System Settings menu.

•

Debug info: allows the user to perform troubleshooting functions to analyze Ethernet traffic.

•

Retrieve RSL Info: allows the user to download RSL information for an MPT, in .csv format.

•

MPT/EAS Conversion: allows the user to perform the PC-based component of the procedures to convert equipment to another version: −

an MPT-HC/XP to an MPT-HC-HQAM/XP-HQAM

−

a P8ETH card to an EASv2 card

−

an MPT-HL to an MPT-HLC

For the complete procedures see the 9500 MPR Hardware Installation and Replacement Manual. •

CorEvo Upgrade: allows the user to perform the first part of the operation to upgrade from a Core-E card to a CorEvo card. See the Core-E to CorEvo Upgrade Procedure document for more information.

•

Tx Diversity Antenna: allows the user to manage a transmit diversity antenna on an MPT-HLC radio in 1+1 HSB configuration. Note: TDA Feature is operational only if the radio has been equipped with the dual relay switch assembly, and is correctly connected to a diversity antenna.

793

Release 7.0.0 3DB 19383 ACAA Issue 01 Web Server overview

794



WebCT overview

18 WebCT overview 18.1

General WebCT allows the user to perform some management and monitoring functions using a web browser. WebCT is available when a CorEvo card is in use. If a Core-E card is in use, the web-based tool is Web Server, see Web Server overview. See the 9500 MPR WebCT User Manual for procedures using WebCT. See the 9500 MPR WebEML User Manual for procedures using Web Server. WebCT is the web interface for NEs using the CorEvo card. The web interface for NEs using the Core-E card is Web Server. See the 9500 MPR WebEML User Manual for information. WebCT provides configuration information, alarms, monitoring and administration functions. Table 65 describes the menus available on the WebCT webpages. Many of the webpages in WebCT provide links to each other; for example, if an alarm is present, a link to the Active Alarms webpage is available. Where the navigation icon is available ( ), a link to a resource is provided; for example, the LAG maintenance webpages provide links to the Radio or Ethernet resources in the LAG. Where up and down arrows are available on column headers, the column can be sorted based on its contents.

795

Release 7.0.0 3DB 19383 ACAA Issue 01 WebCT overview


Figure 409 shows the WebCT. Figure 409

WebCT (Administration & Networking domain shown)

Table 65

WebCT menus overview

Menu

Description

Administration & Networking domain Network Element information

Provides basic information about the NE, such as site name, latitude and longitude, and 9500 MPR version. Some of the fields can be edited on this webpage; others are read-only.

System settings

Allows the user to view or change NE settings, such as date and time and DHCP. These settings can also be modified using JUSM.

SNMP settings

Allows the user to view or change the SNMP version and community strings

License information

Provides read-only information about the RMU serial number and license string. The license information can be updated using JUSM.

796


Table 65

WebCT overview

WebCT menus overview (Continued)

Menu

Description

CorEvo Upgrade

Completes the operation to upgrade from a Core-E card to a CorEvo card. See the Core-E to CorEvo Upgrade Procedure document for more information.

Monitoring & Maintenance domain Active Alarms

Shows the alarms for the NE

Alarms Log

Shows the record of alarms. Comments can be added on this webpage.

NE Inventory

Allows the user to view or save the current configuration view and remote inventory

Debug info

Allows the user to perform troubleshooting functions to analyze Ethernet traffic. Commands can be run from the webpage or sent to a file.

Tx Diversity Antenna

Allows the user to manage a transmit diversity antenna on an MPT-HLC radio in 1+1 HSB configuration. TDA Feature is operational only if the radio has been equipped with the dual relay switch assembly, and is correctly connected to a diversity antenna.

L2 show

Lists all the MAC addresses and associated VLANs learned by the NE (the list includes static entries self-defined by NE)

Radio Analog Measurements

Allows the user to perform radio monitoring

Radio Maintenance

Allows the user to view and change Tx mute and Radio Loopback, perform an MPT Restart, or download an RSL history file for the MPTs connected to the NE

Ethernet Maintenance

Allows the user to view settings, alarms, and SFP information, and run commands on enabled Ethernet ports

LAG Maintenance

Allows the user to view LAG and port status and alarms for enabled Radio and Ethernet LAGs

797

Release 7.0.0 3DB 19383 ACAA Issue 01 WebCT overview

Table 65


WebCT menus overview (Continued)

Menu

Description

Ring Maintenance

Allows the user to view alarms, information, and status of Rings

PDH Maintenance

Allows the user to view settings and alarms and perform loopbacks on enabled PDH tributaries

SDH Maintenance

Allows the user to view settings and alarms and perform loopbacks on enabled SDH tributaries

Protection Maintenance

Allows the user to view protection schemes in effect and perform protection switching commands

798



19 Microwave Craft Terminal overview 19.1

Introduction This chapter provides an introduction to the MCT interface. MCT is used to provision and monitor NEs in MPR-e standalone configuration or connected to an MSS-1c.

19.2

MCT start MCT is started from the WebEML launcher or MCT launcher on the desktop. If the WebEML launcher is used, the NEtO recognizes the IP address as an MPR-e configuration and opens the appropriate interface. WebEML must be connected to the CT port of the MSS-1c or to the MPR-e Ethernet generic device as explained in the 9500 MPR MCT User Manual. Refer to the 9500 MPR Software Installation and NE Upgrade Manual for information on copying WebEML from the software package and connecting the PC to the MSS1c or Ethernet generic device in order to access the MPT. Note: For MPR-e, the PC should be in the same sub-network as the default IP address of the TMN in-band (first connection); see the Nokia 9500 MPR MCT User Manual for configuration information. If TMN in band is different from the Local NE IP, there also needs to be a route on the PC with the gateway of the TMN in band.

Note: For MSS-1c, to access the NE the PC must be configured to “Get automatically an IP address” (DHCP server) and a static route must be added using the command “route add 10.0.1.2 mask 255.255.255.255 192.168.30.1”. If the NE IP address cannot be retrieved, it is possible to use the local IP address of the CT port of the MSS-1c. This address doesn't need to create a static route. Without the MPT connected to the MSS-1c, it is not possible to open MCT on the CT port from MSS-1c. If all the images/icons are missing, check that file msimg32.dll is present in System32.

799

Release 7.0.0 3DB 19383 ACAA Issue 01 Microwave Craft Terminal overview

19.3


MCT main view overview The main view is the entry point of the application and provides the basic diagnostic and configuration functions. The main view shows a high level overview of the areas on the main screen. Different Main views are shown according to configuration type: •

MPR-e standalone, (Figure 410)

•

MSS-1c, (Figure 411)

•

MPR-e with XPIC, (Figure 412)

Note: If the MCT is connected to an MPT-HC/XP/HC-HQAM/XP-HQAM/9558HC with the XPIC + RPS external module installed (but with no XPIC feature configured), the screen in Figure 412 will appear.

Figure 410

Main view: system overview for MPR-e standalone Domain alarm synthesis

Perspective tab-panels

Tool bar Alarm Synthesis

Navigator

General information

IP address of the connected NE 23701

800


Figure 411


Main view: system overview for MSS-1c Domain alarm synthesis

Perspective tab-panels

Tool bar Alarm Synthesis

Navigator

General information

IP address of the connected NE 23700

801


Figure 412

Main view: System overview with MPT-HC/MPT-XP with XPIC module

19.4 Figure 413


MCT toolbar

Toolbar

With MPR-e standalone and MSS-1c the MCT toolbar has the following buttons:

802

•

Disconnect from NE: to disconnect from the NE

•

Export NE information: to export the NE configuration and current alarms to a text file. Only the information related to the MPR-e is reported.


19.5


Alarm synthesis The CT provides an alarm functionality that informs the operator on the severity of the different alarms in the NE as well as on the number of current alarms. There are five different alarm severity levels. In the CT these different levels are associated with colors. •

Red: Critical alarm (CRI)

•

Orange: Major alarm (MAJ)

•

Yellow: Minor alarm (MIN)

•

Cyan: Warning alarm (WAR)

•

Blue: Indeterminate (IND)

The meaning of each icon in the Alarm Synthesis is: •

CRI - Critical alarm Synthesis of alarms that need immediate troubleshooting (typical: NE isolation)

•

MAJ - Major (Urgent) alarm Synthesis of alarms that need immediate troubleshooting

•

MIN - Minor (Not Urgent) alarm Synthesis of alarms for which an intervention can be deferred

•

WAR - Warning alarm Synthesis of alarms due to failure of another NE in the network

•

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 always represented on the different Equipment views so that the operator is always aware of the alarms occurring in the system. Furthermore the number in the alarm icon indicates the number of active alarms with that specific severity.

803


19.6


Domain alarm synthesis area This area contains the icons representing the alarms per domain. Each icon indicates the number of alarm occurrences for each domain. The meaning of each icon in the Domain alarm synthesis area is: •

COM – Communication alarm Synthesis of alarms in the Communication domain

•

EQT – Equipment alarm Synthesis of alarms in the Equipment domain

19.7

General information on the management state The different management states concerning the NE are shown in two tab-panels: •

Figure 414

Radio synthesis tab

•

804

Radio Synthesis

Radio Synthesis with XPIC configured (only with MPT-HC/XP/HCHQAM/XP-HQAM/9558HC in MPR-e configuration)


Figure 415

Radio synthesis tab with XPIC configured

• Figure 416


Network Supervision

Network supervision tab

The Radio Synthesis provides information about the: •

Abnormal Condition state: indicates whether abnormal conditions have been recognized.

The Network Supervision gives information on the: •

Local Access state: indicates whether the NE is managed by a craft terminal or by the OS

•

OS Supervision state: indicates whether the communication with the OS is established

805


19.8


Navigator area The Navigator panel displays different options depending on the selected function in the upper tabs. See the 9500 MPR MCT User Manual or the 9500 MPR MCT User Manual for Single NE Mode with 7705 SAR for more information about the options. The System Overview tab (Figure 410, or Figure 411) is a read-only screen, which shows all the configuration parameters of the MPT.

806


Hardware Unit Data Sheets

Hardware Unit Data Sheets

Unit Data Sheets provide detailed information and specifications for hardware and related items. •

Rack and rack accessories unit data sheet

•

Cables unit data sheet

•

MSS-8 microwave service switch shelf unit data sheet

•


•


•

MSS-1c unit data sheet

•

MSS-O microwave service switch shelf unit data sheet

•

Power distribution unit (PDU) unit data sheet

•

Microwave packet transport outdoor unit (MPT ODU) unit data sheet

•

MPT-HL microwave packet transport-long haul shelf unit data sheet

•

MPT-HL transceiver (ANSI market only) unit data sheet

•

MPT-HLC transceiver (ANSI market only) unit data sheet

•

MPT-HLS standard transceiver (ETSI market only) unit data sheet

•

MPT-HLS compact transceiver (ETSI market only) unit data sheet

•

Fan cards unit data sheet

•

Core-E control and switching module unit data sheet

•

CorEvo control and switching module unit data sheet

•

DS1 RJ-45 Patch Panel unit data sheet

•

DS1/MSS-1 d-connector patch panel unit data sheet

•

P32E1DS1 PDH card unit data sheet

•

P2E3DS3 DS3 PDH card unit data sheet

•

SDH card unit data sheet

•

P8ETH Ethernet access switch card unit data sheet

•

EASv2 Ethernet access switch card unit data sheet

•

MPTACC MPT access card unit data sheet

•

AUX auxiliary card unit data sheet

807

Release 7.0.0 3DB 19383 ACAA Issue 01 Hardware Unit Data Sheets

808


•

GigE and 10GigE SFP unit data sheet

•

Sync In/Out SFP unit data sheet

•

3 dB hybrid splitter unit data sheet

•

Coupler and OMT unit data sheet

•

Power injector unit data sheet

•

+24/-48 volt converter unit data sheet

•

MPT Power Unit unit data sheet

•

MPT Extended Power Unit unit data sheet



20 Rack and rack accessories unit data sheet This chapter provides information about racks in use with 9500 MPR. See the following for additional information: •

9500 MPR Frequency Plan for MPT Outdoor Transceivers for transceiver part numbers

•

9500 MPR Technical Specifications for Split Mount Applications and 9500 MPR Technical Specifications for Full Indoor Applications for technical specifications

•

9500 MPR Hardware Installation and Replacement Manual for installation information.

•

Cables for information about cables

•

Cables unit data sheet for cable part numbers

See Table 66 for brief descriptions of racks and rack accessories. See Table 67 for brief descriptions of MPT-HLS subrack part numbers. See Table 68 for standard equipment rack specifications. See Table 69 for seismic equipment rack specifications. Table 66

Racks and rack accessories

PART NUMBER/ MNEMONIC

NAME

Rack assemblies 1AD114560001

Laborack (19” rack)

3DB04656AA 3CC50230AAXX

ETSI rack (H2200 21" rack)

3CC50231AAXX

ETSI Rack H 2000 for MPT-HLS

3CC50232AAXX

ETSI Rack H 1700 for MPT-HLS

3CC50192AAXX

ETSI Rack H 1300 for MHT-HLS

3DB18181AA

Bracket kit for MSS-8 in 21” rack

3DB18171AA

Bracket kit for MSS-4 in 21” rack

809

Release 7.0.0 3DB 19383 ACAA Issue 01 Rack and rack accessories unit data sheet

Table 66


Racks and rack accessories (Continued)


NAME

694-9000-006 Qty: 1

7.0 Ft. Aluminum Rack

690-1125-003 Qty: 1

Rack Extension

695-1001-006 Qty: 1 or 2

Aluminum Rack Screw Kit (for EFE)

695-1001-007 Qty: 1 or 2

Seismic Rack Screw Kit

1AD014120046 Qty: 1

7.0 Ft. Seismic Rack

695-1001-006 Qty: 1 or 2

Rack Screw Kit (for Shelf & EFE)

3CC07810AAAA

3U Distributor subrack for 120 ohm EMC

3CC08061AAAA

Connector support 1.5./5.6 75 ohm (Panel 1U)

3DB16104AAAA

Panel E1 protection 75 ohm 1.0/2.3

3CC08061ABAA

Connector support BNC 75 ohm (Panel 1U)

Brackets 3DB16109AA

DS1 37 Pin D Demarcation Panel Mounting Bracket

Power 3EM13317AB, 3EM13317AC

Power Distribution Unit (PDU) The PDU provides power distribution and protection fuses for equipment protection. PN: 3EM13317AB is the PDU with Fuse Alarm Card PN: 3EM13317AC is the PDU with Relay Alarm Card

3EM10496AA

Alarm Board Assembly Optional for PDU installation

Kits

810


Table 66


Racks and rack accessories (Continued)


NAME

3EM24705AB

6 GHz Rack Mount Kit MPT ODU Rack Mount Bracket kit provides 19 inch rack bracket, and miscellaneous hardware for use in Nonintegrated 1+0 and 1+1 configuration. Add appropriate nose adapter for specific application.

3EM24705AC

7/8 GHz Rack Mount Kit MPT ODU Rack Mount Bracket kit provides 19 inch rack bracket, and miscellaneous hardware for use in Nonintegrated 1+0 and 1+1 configuration. Add appropriate nose adapter for specific application.

3EM24705AA

10.5 to 38 GHz Rack Mount Kit MPT ODU Rack Mount Bracket kit provides 19 inch rack bracket, and miscellaneous hardware for use in Nonintegrated 1+0 and 1+1 configuration. Add appropriate nose adapter for specific application.

3CC50027AA

IDU wall mounting kit (10U)

3CC09614AA

IDU wall mounting kit (3U)

3DB16151AB

Trib/serv panel 19” universal bracket kit

3CC13424AAAA

Rack grounding kit

3CC13423AAAA

Subrack grounding kit (includes the yellow/green cable)

1AF15185AAAA

IP Phone

3CC06503AAAA

Consumable kit

3DB18181AAAA

IDU kit subrack (brackets 21" kit)

3CC50065AAAA

19” to 21” adapter bracket kit 1U

Table 67

MPT-HLS subrack part numbers

Name

Code

TR subrack

3DB80211AAXX

Back panel MPT HLS

3DB80268AAXX

EXT Subrack One TR

3DB80227AAXX

811


Table 67


MPT-HLS subrack part numbers (Continued)

Name

Code

Dummy plate kit

3DB80226AAXX

Fan dummy plate

3DB80464AAXX

Kit support 2 fans 1x4 MPT-HLS

3DB80470AAXX

Fan tray 1x4 MPT-HLS

3DB80477ABXX

Branching front plate kit

3DB80459AAXX

20.1

Rack descriptions MSS-1/4/8, MSS-1c, and MPT-HL shelf assemblies are mounted in either an equal flange aluminum equipment rack or an unequal flange seismic rack. Each rack uses 1.75-inch Electronic Industries Association (EIA) rack mounting increments. A 7 feet equal flange aluminum rack provides 46 EIA rack increments. A 7 feet unequal flange seismic rack provides 43 EIA rack increments.

20.1.1

Standard rack or Laborack (19”) The standard rack uses extruded aluminum channels with 12-24 tapped mounting holes vertically spaced at EIA increments. The tapped-hole pattern provides for mounting the modular subsystems on the front of the channels, and the waveguide and rack rear cover on the back. The bottom of the rack is held together by steel angles mounted to the front and back of the rack channels. As an option, the rear angle can be turned in toward the rack channel or toward the rear (normal position) to increase the base dimensions and provide a more stable footing. If the rear angle is turned in, the front angle must be removed during installation for access to the holes in the rear-mounting angle. Two optional snap-on front covers are available. Side covers are provided for the rack. The side covers protect the cable runs and are secured to the card cages and to slots located on the main rack channels. Retaining screws are used at the top and bottom of each side cover. The Laborack is a light weight 19” rack available in the ETSI market. Installation is similar to the standard rack. Figure 417 shows the standard rack assembly. See Table 68 for standard equipment rack specifications.

812


Figure 417


Standard equal flange aluminum rack assembly (PN 694-9000-006)

813


Table 68


Standard equipment rack specifications

ITEM

CHARACTERISTICS

Description

Equal-flange aluminum rack provides mounting space for shelves in areas where zone 4 earthquake compliance is not required

Physical dimensions (bays) Height Width Depth MSS-8 Stand-Alone Shelf

7 ft 0 in. 20.5 in. 12 in.

MSS-4 Stand-Alone Shelf

12 in.


12 in.

MSS-1c Stand-Alone Shelf

12 in.

MPT-HL Shelf W/diplexer

13.5 in.

MPT-HL Shelf W/One Waveguide Bracket

17 in.

MPT-HL Shelf W/Two Waveguide Bracket

22.0 in.

20.1.2

Seismic 19” rack A seismic rack, designed to withstand seismic anomalies, such as earthquakes, is available. Seismic racks meet EIA specifications regarding earthquake resistance. The rack frame is steel and consists of the rack top support and front and rear baseplates welded to the rack channels. Side covers fit only the seismic rack and are not interchangeable with side covers on the standard extruded aluminum racks. The side covers protect the cable runs and are secured to the card cages and the rack channels by the side holders. The side covers (left and right) slide onto the side panel holders. Figure 418 shows the seismic rack assembly. See Table 69 for seismic equipment rack specifications.

814



Figure 418

Unequal flange seismic rack assembly (PN 1AD014120046)

Table 69

Seismic equipment rack specifications

ITEM

CHARACTERISTICS

Description

Unequal-flange seismic rack provides mounting space for shelves in areas where zone 4 earthquake compliance is required

815


Table 69


Seismic equipment rack specifications (Continued)

ITEM

CHARACTERISTICS

Physical dimensions (bays) Height Width Depth MSS-8 Stand-Alone Shelf

7 ft 0 in. 22 in. 12 in.


12 in.


12 in.

MSS-1c Stand-Alone Shelf 12 in. MPT-HL Shelf W/diplexer MPT-HL Shelf W/One Waveguide Bracket

13.5 in.

MPT-HL Shelf W/Two Waveguide Bracket

17 in. 22.0 in.

20.1.3

ETSI (21”) rack For ETSI applications the MSS-8 is mounted in an Nokia ETSI rack using a special flange adapter (19” to 21”). The MPT-HLS unit is inserted in a specific subrack mounted in the ETSI rack which can support up to 20 MPT-HLS transceivers. The ETSI rack can be equipped with two subracks for a total of 20 MPT-HLS transceivers to support different configurations. ETSI racks are available in four heights. All ETSI racks are 21” (533 mm) wide. Figure 419, Figure 420, Figure 421, and Figure 422 provide dimensions.

816


Figure 419


2200 mm ETSI rack (3CC50230AA)

817


Figure 420

818




Figure 421



819


Figure 422



20.1.4

Outdoor cabinet The outdoor cabinet supports a variety of mounting options and is a GR-487 certified outdoor enclosure solution. Nokia provides expert Installation Services for installations that have different requirements from the recommended configuration as outlined in this manual. Contact Nokia for more information.

820



21 Cables unit data sheet The following tables provide part number information about cables in use with 9500 MPR. See the following for additional information: •


•

9500 MPR Technical Specifications for Split Mount Applications and 9500 MPR Technical Specifications for Full Indoor Applications for technical specifications

•


•


See Table 70 for brief descriptions of cables used with MSS and ODUs. See Table 71 for cables used with the 2xE1 SFP. See Table 72 for brief descriptions of MPT-HLS cables. See Table 73 for brief descriptions of cables for MPT ODU installation. Table 70

Cable assemblies

UNIT

DESCRIPTION

Ethernet electrical cables 3CC52141AAAA

RJ45-RJ45 Eth. CAT5E shielded straight cable 1 m

3CC52141ABAA


3CC52141ACAA


821

Release 7.0.0 3DB 19383 ACAA Issue 01 Cables unit data sheet

Table 70


Cable assemblies (Continued)

UNIT

DESCRIPTION

PDH and SDH Cables DS1 to X-Connect Cables PN: 3EM23110AA/3EM23110AD QTY: as required per NE configuration

Protected ABAM 8 DS1 pair cable assemblies. Cables are designed to interconnect with the 37 pin DSUB customer interconnect panel. Cables are pigtails with connector on one end only. PN: 3EM23110AA is DS1 to X-Connect cable 15 ft. PN: 3EM23110AB is DS1 to X-Connect cable 30 ft. PN: 3EM23110AC is DS1 to X-Connect cable 50 ft. PN: 3EM23110AD is DS1 to X-Connect cable 100 ft.

P32E1DS1 to Patch Panel Cable PN: 3CC52118AA QTY: 2 per Non-Protected P32E1DS1 QTY: 4 per Protected P32E1DS1 Pair

SCSI 68-SCSI 68 pin to pin P32E1DS1 to Patch Panel cable interconnects P32E1DS1 card or MSS-1 68 pin SCSI connector to the DS1 D-Sub or DS1 RJ-45 patch panel.

P32E1DS1 68 Pin SCSI to X-Connect Cables PN: 3EM21339AA/3EM21339AD QTY: as required per NE configuration

Non-Protected ABAM 16 DS1 pair cable assemblies. Cables are designed to interconnect with the 68 pin SCSI connectors on the P32E1DS1 card or MSS-1 unit. Cables are pigtails with connector on one end only. PN: 3EM21339AA is P32E1DS1 to X-Connect cable, Left Side Rack Exit (Slots 3, 5, and 7), 25 ft. PN: 3EM21339AB is P32E1DS1 to X-Connect cable, Right Side Rack Exit (Slots 4, 6, and 8), 25 ft. PN: 3EM21339AC is P32E1DS1 to X-Connect cable, Left Side Rack Exit (Slots 3, 5, and 7), 50 ft. PN: 3EM21339AD is P32E1DS1 to X-Connect cable, Right Side Rack Exit (Slots 4, 6, and 8), 50 ft.

DS3 BNC to Mini-BNC Cable Assembly PN: 3EM22687AA/3EM22687AB QTY: 4 per P2E3DS3 Card

DS3 BNC to Mini-BNC Cable Assembly interconnects P2E3DS3 Mini-BNC to X-Connect. PN: 3EM22687AA is DS3 BNC to Mini-BNC Cable, 2 meters PN: 3EM22687AB is DS3 BNC to Mini-BNC Cable, 5 meters

SCSI 68pin - blue block 3CC52133AA

SCSI 68pin - blue block L = 1.1m

822


Table 70



UNIT

DESCRIPTION

Cable 8XE1 IDU-DISTRIBUTOR 120 ohm 3CC52183AA

Cable 8XE1 IDU-DISTRIBUTOR 120 ohm L = 1m 45° (37 pin)


Cable 8XE1 IDU-DISTRIBUTOR 75 ohm 1.5/5.6 L = 1m 45° (37 pin)


Cable 8XE1 IDU-DISTRIBUTOR 75 ohm BNC L = 1m 45° (37 pin)

2xSCSI, 68 pin - 4 Compax 3CC52157AA

2xSCSI, 68 pin - 4 Compax blue blocks (120 ohm) L = 1.1 m

Adapter cord 3CC52134AA

Adapter cord from SCSI68 male to two D-Sub37 female

3CC52117AB

Wires AWG28, SCSI 68 pin - FW L = 15m

8xE1 IDU-distributor 75 ohm coax 3CC50152AA

Cable 8xE1 IDU-distributor 75 ohm coax no connectors L = 15 m (37 pin). See the 9500 MPR Hardware Installation and Replacement Manual for the cable pin function.

RJ45 to wire-wrap cable 3CC52015AA

Cable, Trib, E1, RJ45 to wire-wrap L = 5 m. See the 9500 MPR Hardware Installation and Replacement Manual for the color table.

Compax terminal block 3CC07917AA

Compax terminal block – 120 ohms – 10 pairs AWG28 to 20 (0,32 to 0,8mm)

RJ45 to RJ45 cross-over cable 3CC52020AA

RJ45 to RJ45 E1 cross-over cable

SCSI-SCSI cross-cable 3CC52150AAAA

SCSI-SCSI cross-cable L = 1.6 m

SCSI-SCSI cross-cable 3CC52150ABAA

SCSI-SCSI cross-cable L = 6.4 m

Cable for STM-1/OC-3 protection 3CC52197AA

Coax cable, one coax plug to two coax plugs; for STM1protection

823


Table 70



UNIT

DESCRIPTION

Ethernet Optical Cables - single-mode fiber Single mode fiber, LC to LC 3CC52077AAAA, 3CC52078AAAA, 3CC52079AAAA

PN: 3CC52077AAAA is Fiber 3M SM LC to LC PN: 3CC52078AAAA is Fiber 5M SM LC to LC PN: 3CC52079AAAA is Fiber 10M SM LC to LC

Single-Mode Fiber, LC to LC PN: 3EM07641AF/3EM07641AK QTY: as required per NE configuration

Single-Mode Fiber, LC to LC for optical Ethernet connectivity. PN: 3EM07641AF is Single-Mode Fiber, LC to LC, 1 meter PN: 3EM07641AG is Single-Mode Fiber, LC to LC, 2 meter PN: 3EM07641AH is Single-Mode Fiber, LC to LC, 3 meter PN: 3EM07641AJ is Single-Mode Fiber, LC to LC, 5 meter PN: 3EM07641AK is Single-Mode Fiber, LC to LC, 10 meter

Single-Mode Fiber, LC to SC PN: 3EM07646AF/3EM07646AK QTY: as required per NE configuration

Single-Mode Fiber, LC to SC for optical Ethernet connectivity. PN: 3EM07646AF is Single-Mode Fiber, LC to SC, 1 meter PN: 3EM07646AG is Single-Mode Fiber, LC to SC, 2 meter PN: 3EM07646AH is Single-Mode Fiber, LC to SC, 3 meter PN: 3EM07646AJ is Single-Mode Fiber, LC to SC, 5 meter PN: 3EM07646AK is Single-Mode Fiber, LC to SC, 10 meter

Single mode fiber, LC to SC 3CC52083AAAA, 3CC52085AAAA, 3CC52086AAAA, 3CC52087AAAA

PN: 3CC52083AAAA is Fiber 3M SM LC to SC PN: 3CC52085AAAA is Fiber 5M SM LC to SC PN: 3CC52086AAAA is Fiber 10M SM LC to SC PN: 3CC52087AAAA is Fiber 3M SM LC to SC

Single mode fiber, LC to FC 3CC52080AAAA, 3CC52081AAAA, 3CC52084AAAA

PN: 3CC52080AAAA is Fiber 3M SM LC to FC PN: 3CC52081AAAA is Fiber 5M SM LC to FC PN: 3CC52084AAAA is Fiber 10M SM LC to FC

Single mode fiber, FC to SC 3CC52088AAAA

PN: 3CC52088AAAA is Fiber 5M, SM FC-SC PN: 3CC52017AAAA is Fiber 10M, SM FC-SC

Single mode fiber, SC to SC 3CC52023AAAA, 3CC52025AAAA, 3CC52029AAAA

PN: 3CC52023AAAA is Fiber 3M, SM SC-SC PN: 3CC52025AAAA is Fiber 5M, SM SC-SC PN: 3CC52029AAAA is Fiber 10M, SM SC-SC

824


Table 70



UNIT

DESCRIPTION

Ethernet Optical Cables - multi-mode fiber 2 Multi-Mode Fiber, LC to LC 1AB214000016, 1AB214000017

PN: 1AB214000016 is Fiber Simplex MM jumper LC-LC L = 5m PN: 1AB214000017 is Fiber Simplex MM jumper LC-LC L = 10m

LC-LC multi-mode fiber optic cable 3CC52170BA/3CC52170BN

PN: 3CC52170BN is LC-LC Fiber Optic Cable 25 m PN: 3CC52170BM is LC-LC Fiber Optic Cable 50m PN: 3CC52170BA is LC-LC Fiber Optic Cable 80 m PN: 3CC52170BB is LC-LC Fiber Optic Cable 100 m PN: 3CC52170BC is LC-LC Fiber Optic Cable 120 m PN: 3CC52170BD is LC-LC Fiber Optic Cable 140 m PN: 3CC52170BE is LC-LC Fiber Optic Cable 160 m PN: 3CC52170BF is LC-LC Fiber Optic Cable 180 m PN: 3CC52170BG is LC-LC Fiber Optic Cable 200 m PN: 3CC52170BH is LC-LC Fiber Optic Cable 220 m PN: 3CC52170BI is LC-LC Fiber Optic Cable 250 m PN: 3CC52170BL is LC-LC Fiber Optic Cable 300 m

Multi-Mode Fiber, LC to FC 1AB240330033, 1AB240330032

PN: 1AB240330033 is Fiber Simplex MM jumper LC-FC L = 5m PN: 1AB240330032 is Fiber Simplex MM jumper LC-FC L = 10m

Multi-Mode Fiber, LC to SC 1AB200240003, 1AB200240004

PN: 1AB200240003 is Fiber Simplex MM jumper LC-SC L = 5m PN: 1AB200240004 is Fiber Simplex MM jumper LC-SC L = 10m

Multi-Mode Fiber, LC to SC PN: 3EM07646AA/3EM07646AE QTY: as required per NE configuration

Multi-Mode Fiber, LC to SC for optical Ethernet connectivity. PN: 3EM07646AA is Multi-Mode Fiber, LC to SC, 1 meter PN: 3EM07646AB is Multi-Mode Fiber, LC to SC, 2 meter PN: 3EM07646AC is Multi-Mode Fiber, LC to SC, 3 meter PN: 3EM07646AD is Multi-Mode Fiber, LC to SC, 5 meter PN: 3EM07646AE is Multi-Mode Fiber, LC to SC, 10 meter

825


Table 70



UNIT

DESCRIPTION

Multi-Mode Fiber, LC to LC PN: 3EM07641AA/3EM07641AE QTY: as required per NE configuration

Multi-Mode Fiber, LC to LC for optical Ethernet connectivity. PN: 3EM07641AA is Multi-Mode Fiber, LC to LC, 1 meter PN: 3EM07641AB is Multi-Mode Fiber, LC to LC, 2 meter PN: 3EM07641AC is Multi-Mode Fiber, LC to LC, 3 meter PN: 3EM07641AD is Multi-Mode Fiber, LC to LC, 5 meter PN: 3EM07641AE is Multi-Mode Fiber, LC to LC, 10 meter

Ethernet SFPs, Electrical, Optical Cable Assemblies RJ-45 Cat5E Cable Assemblies 1 PN: 3EM15052AA/3EM15052BD QTY: as required per NE configuration

826

RJ-45 Cat5E Cable assemblies. Cables are designed to interconnect with electrical Ethernet ports and the DS1 RJ-45 Patch Panel. One cable is required for each electrical Ethernet/DS1 port. Cable assemblies are not TIA/ EIA T568A color pin out compliant. PN: 3EM15052AA/3MU00085AC is RJ-45 to RJ-45 cable 3 ft. PN: 3EM15052AD/3MU00085AD is RJ-45 to RJ-45 cable 6 ft. PN: 3EM15052AH/3MU00085AE is RJ-45 to RJ-45 cable 10 ft. PN: 3EM15052AN/3MU00085AF is RJ-45 to RJ-45 cable 20 ft. PN: 3EM15052AQ/3MU00085AG is RJ-45 to RJ-45 cable 30 ft. PN: 3EM15052AU/3MU00085AH is RJ-45 to RJ-45 cable 50 ft. PN: 3EM15052AY/3MU00085AJ is RJ-45 to RJ-45 cable 70 ft. PN: 3EM15052BB/3MU00085AK is RJ-45 to RJ-45 cable 100 ft. PN: 3EM15052BC/3MU00085AL is RJ-45 to RJ-45 cable 200 ft. PN: 3EM15052BD/3MU00085AM is RJ-45 to RJ-45 cable 300 ft.


Table 70



UNIT

DESCRIPTION

Power cables SFP Cable (electrical) PN: 3EM23141AA/3EM23141AD QTY: as required per NE configuration

SFP Cable (electrical) for SFP Ethernet connectivity. PN: 3EM23141AA is SFP Cable (electrical), 0.5 meter PN: 3EM23141AB is SFP Cable (electrical), 1.0 meter PN: 3EM23141AC is SFP Cable (electrical), 1.5 meter PN: 3EM23141AG is SFP Cable (electrical), 2.0 meter PN: 3EM23141AD is SFP Cable (electrical), 3.0 meter PN: 3EM23141AE is SFP Cable (electrical), 5.0 meter PN: 3EM23141AF is SFP Cable (electrical), 10.0 meter

Power Converter Power Cable

PN: 3DB18766AA

AC Power Cable for MSS-O PN: 3DB19132AA QTY: as required per NE configuration

AC power cable is for MSS-O connectivity

Optical cables for MSS-O QTY: as required per NE configuration

Optical cables for MSS-O PN: 3CC52210AA is 5 meter PN: 3CC52210AB is 10 meter PN: 3CC52210AC is 25 meter

MSS-4/MSS-8 Shelf Power Cable 3DB18271AA Qty: 1 or 2

MSS-4 power-cable supply connection 2x4mm2 (L = 4m)

DC power supply cable 1AC041800001

DC power supply cable (2x16mm2)

MSS-8 power supply cord 3CC52190AA

MSS-8 power supply cord 2x6mm2 (L = 4 m)

MSS grounding Kit 3CC13423AA

MSS grounding Kit

QMA to RF cable 3DB18205AA

QMA (male) - N (female) RF cable (from Radio Access card to bracket) (L = 0.35m)

QMA to RF cable 3DB18205AB

QMA (male) - N (female) RF cable (L = 2m)

827


Table 70



UNIT

DESCRIPTION

Sync Cable Sync Coaxial Cables PN: 3DB05850AA, 3DB18204AA, 3DB04295AA, 3DB02901AA QTY: as required per NE configuration

Core Sync connections require a slip fit coax 1.0/2.3 connector. Available sync cables are as follows: PN: 3DB05850AA is slip fit coax 1.0/2.3 to panel mount female BNC connector, 1 meter (used for sync input and output interconnection) PN: 3DB18204AA is clock to clock w/T slip fit coax 1.0/2.3 cable, 8 inches (used for protected Core Sync interconnection) PN: 3DB04295AA is slip fit coax cable, 1.1 meter (used to interconnect two MSS-4/8 shelf sync ports) PN: 3DB02901AA is slip fit coax cable, 6.0 meters (used to interconnect two MSS-4/8 shelf sync ports)

Synch distribution cable 3DB10109AA

Cord 1.0/2.3 M straight L = 15 m (for synch. distribution)

Synch distribution cable 3CC52138AA

Cord 1.0/2.3 M 90° M90° L = 5 m (for synch. distribution)

Synch distribution cable 3DB01516AA

Cord 1.0/2.3 M 90° M90° L = 1.6 m (for synch. distribution)

Sync SFP Sync-In/Out SFP PN: 3DB78017AAAB QTY: up to two per CorEvo card or MSS1 unit

Provides a reference clock for the CorEvo or MSS-1.

Cable for Sync-In/Out connection PN: 3CC52203AA QTY: as required per CorEvo card with Sync-In/Out SFP

PN: 3CC52203AA is Cord T adapter M/F to M 1.0/2.3 mini

Cables for RSSI voltage measurement MPT-HLS/HLC RSSI voltage cable PN: 3CC50210AA QTY: up to one per MPT-HLS/HLC transceiver

828

For RSSI voltage measurement with MPT-HLS/HLC.


Table 70



UNIT

DESCRIPTION

MPT/AWY service cable PN: 3CC52191AA QTY: up to one per MPT ODU

For RSSI voltage measurement with MPT ODU.

829


Table 70



UNIT

DESCRIPTION

Fan Alarm Cables Fan Alarm Cable PN: 3EM24105AA, 3EM24105AB Qty: 1 per FAN 2U W/Alarms

Provides fan alarm cable stub. PN: 3EM24105AA is Fan Alarm Cable 25 Ft. PN: 3EM24105AB is Fan Alarm Cable 50 Ft.

Housekeeping Alarm Cables Housekeeping Alarm Cable PN: 3CC52200AA Qty: 1 per AUX card

Permits management of alarms from the MPT Power Unit or MPT Extended Power Unit using the AUX card.

FAN Housekeeping cable 3CC52194AA

FAN Housekeeping Cable (L = 7.5m)

Power Unit Housekeeping cable 3CC52201AA

Power Unit to MSS-1 or Enhanced Fan card housekeeping alarm cable

Miscellaneous cables 3EM23311AA/AB

Jumper Cable for type N adapter bracket installation (1 each for non protected, 2 each for protected) Notes: RJ-45 Cat5E Cable assemblies 3EM15052AA/BD are being phased out and replaced with TIA/EIA 568B compliant RJ-45 cable assemblies 3MU00085AA/AM.

2.

Longer assemblies with single-mode fiber are available upon request.

Cords for 2xE1 SFP

1.6/5.6

BNC

1.6/5.6

x

BNC

2 x E1 cord RJ45 plug - free

RJ45

3CC52168ABXX

1+1

RJ45

120 ohms

1+0

120 ohms

Table 71

1.

x

x

x

x

10m 1 3CC52172AAXX

830

cord RJ45 socket - 2 x RJ45 plugs 0,5m 2

x


Cords for 2xE1 SFP (Continued)

3CC52192AAXX

cord RJ45 plug - 4 x coax

RJ45

1.6/5.6

BNC

x

1.6/5.6

cord RJ45 plug - 2 x RJ45 plugs 10m 3

BNC

3CC52174ACXX

1+1

RJ45

120 ohms

1+0

120 ohms

Table 71


x

x

x x

x

free 10m 4 1AB006420060

4 connectors BNC

1AB009870002

4 connectors 1.6/5,6

x

x x

x

Notes:

Table 72

1.

Stranded wires, to be used with Compax terminal blocks (Nexans).

2.

Y cable for SFP protection

3.

Separates the 2 E1 on two RJ45

4.

No 75 ohms connector included.

MPT-HLS cable codes

Name

Code

Remarks

Power cable zip to battery (6 mm2) subrack RT

1AC007800069

Power cable zip to battery (1 mm2) fans

1AC007800068

2X6mm2 L=4 m power supply cord per MSS-8

3CC52190AAXX

Fan cable MNGT L = 1.3 m

3CC52141AD

RJ-45 to RJ-45 Ethernet direct cable for Fan management

Power cord for MPT-HLS compact subshelf

3DB18272AA

A 10 A breaker is required on the power distribution unit

2x4 mm2 L=4 m

831


Table 72


MPT-HLS cable codes (Continued)

Name

Code

Remarks

Copper SFP (0.5 m sim.) MSS-TRs upper

3DB80628AD

Can be used to connect MPT-HLS transceivers to the MSS-1/4/8 unit, or to connect transceivers on the same subshelf to each other in RPS configuration.

Copper SFP (1 m sim.) MSS-TRs upper

3DB80628AE

Copper SFP (1.5 m sim.) MSS-TRs upper

3DB80628AA

Copper SFP (2 m sim.) MSS-TRs upper

3DB80628AB

Copper SFP (3 m sim.) MSS-TRs lower

3DB80628AC

XPIC cable

3CC52204AD

0.5 m

3CC52204AE

1m

3CC52204AA

3m

3CC52204AB

5m

3CC52204AC

10 m

Table 73

Accessories and cables for MPT ODU connections

3CC50074ABXX

Support kit for 4 cords

1AB357780003

QMA 90° connector for coax. cable (diam.=6.85 mm)

3CC52188AAXX

N-to-Ethernet pair pigtail (N female-Free wires) for the power supply cable (1 m) The N-to-Ethernet pair pigtail adapts a Type N coax male connector to free wires which are terminated with an RJ-45 and R2CT connector. This assembly is used to connect power to the MPT ODU.

1AB074610027

RJ45 connector (boot included). To be terminated on the 1 m Adapter cord for Indoor connection or Outdoor connection.

832


Table 73


Accessories and cables for MPT ODU connections (Continued)

1AB150990002

R2CT connector. To be terminated on the 1 m Adapter cord for Outdoor connection.

1AC016760006

IDU-ODU Cat5e Ethernet cable (cable to be used for PFoE with RJ45 and R2CT connectors)

1AD040130004

Grounding kit for Cat5e cable

1AC001060084

ODU Grounding cable 16 mm2

1AC001100022

Coax cable 50 ohm (diam.=10.3 mm) for L>200 m

1AB095530023

N Conn. male straight 50 ohm for coax. cable (diam.=10.3 mm)

1AB128500002

Grounding kit for coax. cable (diam.=10.3 mm)

1AC041350001

Coax. cable 50 ohm (diam.=6.85 mm) for L<200 m

1AB095530036

N Conn. male straight 50 ohm for coax. cable (diam.=6.85 mm)

1AD040130004

Grounding kit for coax. cable (diam.=6.85 mm)

1AB187280040, 1AB187280045

SFP Module for data interconnection between MPT-HC/HC-HQAM/XP/XPHQAM and Core card or MPT Access card. 1AB187280040 is SFP Module, 1000BaseT-Lx SM fiber up to 5 km 1AB187280045 is SFP Module, 1000BaseT-Sx MM fiber up to 550 meter

1AB383760001/ 3CC50167AAAA

Optional 1000BASE-SX SFP for Multimode Fiber, to be plugged in the ODU and MSS when they are connected through fiber

3CC52170BN

LC/Q-XCO to LC Fiber cord (L = 25 m for MPT IDU-ODU connection)

3CC52170BM


3CC52170BA


3CC52170BB


3CC52170BC


833


Table 73



3CC52170BD


3CC52170BE


3CC52170BF


3CC52170BG


3CC52170BH


3CC52170BY


3CC52170BL


3CC50097AAXX

Cable overlength box (wall and pipe mounting only)

3CC50095AAAA

Cable overlength tray 1U for rack

3CC52169BA

RPS Q-XCO to Q-XCO optical cable (L = 1 m for 1+1)

3CC52169BB


3CC52169BC


3CC52169BD


XPIC cable cat7 3CC52186CAXX

MPT XPIC cord 1 m (for integrated antenna with OMT or OMT-C)

3CC52186CBXX

MPT XPIC cord 2.5 m (for double polarization antenna with flextwists)

1AD160490001

Tool for HIROSE RJ45 IDU-ODU cable assembling

3CC50098AAXX

MPR-MPT tool bag (special tools)

3CC50099AAXX

Standard tool bag

For MPT-HC/HQAM only

These optionals accessories must be used to connect the power coaxial cable of MPT-HC/HC-HQAM to the station battery

3CC52159AAXX

Pigtail

1AB251350001

Low Pass Filter

834


Table 73



3CC50030AAAA

Lightning Arrestor

MPT-HC Station Battery Accessories QTY: 1 each for MPT-HC/HC-HQAM direct connection to station battery.

MPT-HC/HC-HQAM Station Battery Accessories provide connectivity to station battery. Required for MPT-HC/HC-HQAM connected to Core, P8ETH, and EASv2 card, or MPR-e. PN: 3CC50149AA is Lightning Arrestor bracket (up to 4) PN: 3CC50030AAAA is Lightning arrestor W/ground cable PN: 1AB251350001 is Low Pass Filter PN: 1AB328430001 is Cat5e Surge Suppressor kit PN: 1AB074610027 is RJ45 connector, outdoor rated PN: 3CC52159AA is Type N BNC to 2-Wire Adapter PN: 1AC014320002 is LMR-400 Coax cable 50 ohm for Length ≤ 300m PN: 1AB095530045 is Type N BNC, Male, Straight, Qty 3 PN: 1AB095530046 is Type N BNC, Female, Straight PN: 3CC52188AA is Adapter Cable, N to RJ45 PN: 1AB150990002 is R2CT connector PN: 1AB38393001 is PPC compression tool kit PN: 1AB350440001 is Grounding Kit for Coax cable, Qty site specific

Cat5E Cable, Outdoor rated PN: 1AC016760006 QTY: as required per site configuration

Cat5E Cable, Outdoor rated used for MPT-HC/HC-HQAM/XP/XP-HQAM PFoE and power only applications.

RJ-45 Cat5E Connector Kit PN: 1AB016760006 QTY: as required per site configuration

RJ-45 Cat5E connector kit is used with Cat5E outdoor cable.

835


Table 73



MPT ODU Cat5E, Outdoor rated, Cable Assembly PN: 3CC52199AA/ 3CC52199AD QTY: as required per site configuration

MPT ODU Cat5E, Outdoor rated, Cable Assembly are pre assembled outdoor Cat5E cable (1AC016760006), R2CT, RJ-45 for MPT ODU PFoE applications.

Preassembled Cat5E R2TC/RJ-45 XP max

3CC52199AJ

Cat5E Cable, Indoor rated PN: 1AC016760003 QTY: as required per site configuration

Cat5E Cable, Indoor rated used for indoor Ethernet cable and Core MPT-HC/ HC-HQAM/XP/XP-HQAM port to Power Injector card/box.

RJ-45 Cat5E Connector Kit PN: 1AB074610008 QTY: as required per site configuration

RJ-45 Cat5E connector kit is used with Cat5E indoor cable.

MPT-HC/XP/HQAM outdoor fiber cable storage box PN: 3CC50097AB QTY: as required per NE configuration

GR-3108 compatible outdoor fiber cable storage box

Hirose Crimping Tool (RJ-45) PN: 1AD160490001 QTY: Minimum of 1 available per site installation

Hirose Crimping Tool (RJ-45) used to terminate RJ-45 connectors to Cat5E cable.

R2CT Housing PN: 1AB150990002 QTY: as required per site configuration

R2CT Housing provides watertight cable transition to MPT-HC/HC-HQAM/ XP/XP-HQAM for Data+Power connection.

836

PN: 3CC52199AA is 25m MPT ODU cable assembly PN: 3CC52199AB is 50m MPT ODU cable assembly PN: 3CC52199AC is 75m MPT ODU cable assembly PN: 3CC52199AD is 100m MPT ODU cable assembly


Table 73



Cat5E Grounding Kit PN: 3CC50251AA QTY: as required per site configuration

Cat5E Grounding Kit

LMR-400 Grounding Kit PN: 1AB350440001 QTY: as required per site configuration

LMR-400 Grounding Kit

Hoisting Protection Tube PN: 1AF17000AAAA QTY: Minimum of 1 available per site installation

—

837


838




22 MSS-8 microwave service switch shelf unit data sheet Table 74

MSS-8 microwave service switch shelf


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB18485AA

MSS-8 Microwave Service Switch Shelf

N/A

459923

213266

Inactive

3DB18485AB


CRMLB10HRA

459923

213266

Active

3DB18485CA

High speed MSS-8 Microwave Service Switch Shelf backplane

CRMM110BRA

462095

—

Active

3DB18485DA

MSS-8 slot shelf with 10G backplane

CRM6900ERA

467245

—

Active

3DB18163AB

MSS-4/8 Shelf Slot Cover MSS-4/8 shelf slot cover is required for all unequipped slots for EMI compliance and correct system cooling.

N/A

—

—

Active

839

Release 7.0.0 3DB 19383 ACAA Issue 01 MSS-8 microwave service switch shelf unit data sheet

Table 74


MSS-8 microwave service switch shelf (Continued)


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3EM22715AE 3EM22715AF 3EM22715AG

MSS-8 shelf Kits MSS-8 shelf kits provide one MSS-8 shelf, power cables, FAN card, and miscellaneous rack hardware.

N/A

—

—

Active 3EM22715AC, 3EM22715AD is MSS-8 shelf kit W/Alarm FAN Card 3EM22715AE, 3EM22715AF, 3EM22715AG is MSS-8 shelf kit W/Alarm FAN Card - HS 3EM22715AB, 3EM22715AC, and 3EM22715AD have been phased out

840


22.1


Features and application notes •

The Microwave Service Switch (MSS-8) shelf provides cross-connection, port aggregation, switching, and equipment management.

•

300 Mb/s full-duplex Ethernet transport capacity

•

Flexible aggregate capacity sharing DS1/E1, DS3, OC-3/STM-1, and Ethernet traffic

•

Split mount configuration supports up to six unprotected RF channels, three 1+1 HSB, Space Diversity (SD) or Frequency Diversity (FD) protected RF channels in one MSS-8 shelf connected to up to six OutDoor Units (ODUs).

•

Split mount configuration utilizing the MPTACC card supports up to twelve unprotected RF channels, up to six 1+1 HSB, Space Diversity (SD) or Frequency Diversity (FD) protected RF channels in one MSS-8 shelf connected to up to twelve MPT ODUs.

•

Split mount configuration utilizing the Core SFP ports supports:

•

•

−

up to two unprotected RF channels in one MSS-8 shelf connected to up to two MPT-HC/HC-HQAM/XP/XP-HQAM transceivers.

−

up to one protected RF channel in one MSS-8 shelf connected to up to two MPT-HC/HC-HQAM/XP/XP-HQAM transceivers.

Split mount configuration utilizing the Core electrical Ethernet ports supports: −

up to four unprotected RF channels in one MSS-8 shelf connected to up to four MPT ODUs.

−

up to two protected RF channels in one MSS-8 shelf connected to up to four MPT ODUs.

Split mount configuration utilizing the EAS SFP ports support up to eighteen unprotected RF channels in one MSS-8 shelf connected to up to eighteen MPT ODUs.

Note: MPT-MC is not supported by P8ETH.

•

All indoor mount supports up to twenty unprotected RF channels, nine 1+1 HSB, Space Diversity (SD) or Frequency Diversity (FD) protected RF channels in one MSS-8 shelf using EAS cards connected to up to nine Microwave Packet Transport-Long Haul (MPT-HL/HLC/HLS) shelves and the Core card connected to up to two MPT-HL/HLC/HLS shelves.

•

Stand-alone shelf configuration

•

All cards are accessed from the front side of the shelf

841


22.2


•

Mounts in a 19-inch aluminum rack, 19-inch seismic rack, or 21 inch rack. Adapter flanges available to mount in a 23-inch aluminum rack

•

Provides two mounting depth options: flush mount or 5 inch projection

•

Provides nine card slots. Two are dedicated for Control and Switching Modules (Core-E and CorEvo). Six universal slots are available for transport cards: P32E1DS1, P2E3DS3, SDHACC, and/or EAS. Slot 8 also supports the AUX card. One slot is dedicated for fan card.

Description The MSS-8 self consists of a module cage and backplane which provides nine slots. See Figure 423 for an example of the MSS-8 shelf. The MSS-8 shelf is 19 inches wide (17.25 inches wide without mounting flanges), 3.46 inches high (2 EIA rack increments), and 9.75 inches deep. Adapter plates are available to mount the MSS-8 shelf in 23 inch aluminum racks. See Figure 424 for outline and shelf dimensions of the MSS-8 shelf.

Figure 423

Microwave service switch (MSS-8) shelf

Figure 424

MSS-8 shelf dimensions

842


22.3


Equipment complement MSS-8 shelf slots 1 and 2 are dedicated to the Core card. Slots 3 through 8 are available for transport cards P32E1DS1, P2E3DS3, MPTACC, SDHACC, SDHCAN, and/or EAS. Slot 9 is dedicated for required fan card. See Figure 425 for MSS-8 shelf slot definitions. See Table 75 for details of card equipage options. Caution: If an MPT is connected to the main Core card, Core protection is not supported. A protection switch will cause communication with the MPT to be lost.

Figure 425

MSS-8 shelf slot definitions

Table 75

MSS-8 shelf card complement

CIRCUIT PACK/ UNIT DATA SHEET

PART NO.

CLEI

QTY

SLOT

Core-E control and switching module Core-E control and switching module unit data sheet

3DB18326AC

CRCCACMJAA

1 or 2

1 and 2

CorEvo-10G control and switching module CorEvo control and switching module unit data sheet

3DB19318AA 3DB18788AC

CRGIAEGKAA

1 or 2

1 and 2

843


Table 75


MSS-8 shelf card complement (Continued)


PART NO.

CLEI

QTY

SLOT

MPTACC MPT Access MPTACC MPT access card unit data sheet

3DB18634AB

N/A

Up to 6

3, 4, 5, 6, 7, 8

P2E3DS3 DS3 PDH Card P2E3DS3 DS3 PDH card unit data sheet

3DB18194AC

CRG2AA9DAA

Up to 6

3, 4, 5, 6, 7, 8

P8ETH Ethernet Access Switch Card P8ETH Ethernet access switch card unit data sheet

3DB18206AC

CRCCACGJAA

Up to 2

3, 4, 5, 6, 7, 8

EASv2 Card EASv2 Ethernet access switch card unit data sheet

3DB19017AB

CRG2AKKDAA

Up to 2

3, 4, 5, 6, 7, 8

P32E1DS1 PDH Card P32E1DS1 PDH card unit data sheet

3DB18126AE

CRG2ABUDAA

Up to 6

3, 4, 5, 6, 7, 8

SDHACC SDH Card SDH card unit data sheet

3DB18735AA

N/A

Up to 6

3, 4, 5, 6, 7, 8

AUX Auxiliary Card AUX auxiliary card unit data sheet

3DB18236AB

N/A

Up to 1

8

+24/-48 Volt Converter (2 Converters W/Chassis) 1 or +24/-48 Volt Converter (1 Converter W/Chassis)For shelves equipped with the +24/48 Volt Converter card, the FAN 2U Card W/Alarms is required. +24/-48 volt converter unit data sheet

3DB18862AA

N/A

Up to 1

4, 6, 8

3DB18863AA

N/A

844


Table 75


MSS-8 shelf card complement (Continued)


Fan 2U Card or Fan 2U Card With Alarms Fan cards unit data sheet

PART NO.

CLEI

QTY

SLOT

3DB18134BB

CRCCACPJAA

1

9

3EM23911AA,

CRCCADYJAA

1. For shelves equipped with the +24/-48 Volt Converter card, the FAN 2U Card W/Alarms is required. MSS-8 shelf slot 1 is dedicated to the main Core card and is required in every application. See Figure 426 to see an example of the MSS-8 shelf configured in the unprotected Core configuration. Slot 2 is dedicated for an optional spare Core card for protected Core configurations. See Figure 427 to see an example of the MSS-8 shelf configured in the protected Core configuration. Figure 426


845


Figure 427



MSS-8 shelves supports up to six P32E1DS1 cards in unprotected E1/DS1 aggregation configurations. Supports up to three pairs of P32E1DS1 cards in 1+1 EPS protected E1/DS1 aggregation configurations. In 1+1 EPS protected configuration, the main P32E1DS1 cards are equipped in slots 3, 5, and/or 7, and the spare (protection) P32E1DS1 cards are equipped in slots 4, 6, and/or 8 respectively. See Figure 428 to see an example of a stand-alone MSS-8 shelf configured with two pairs of P32E1DS1s in slots 3 through 6 in the protected 1+1 EPS configuration and slots 7 and 8 configured in the unprotected configuration. Figure 428

846

MSS-8 stand-alone shelf, equipped with P32E1DS1 (DS1 Card)



MSS-8 shelves supports up to six P2E3DS3 cards in unprotected configurations. Supports up to three pairs of P2E3DS3 cards in 1+1 EPS protected configurations. In 1+1 EPS protected configuration, the main P2E3DS3 cards are equipped in slots 3, 5, and/or 7, and the spare (protection) P2E3DS3 cards are equipped in slots 4, 6, and/or 8 respectively. See Figure 429 to see an example of a stand-alone MSS-8 shelf configured with two pairs of P2E3DS3s in slots 3 through 6 in the protected 1+1 EPS configuration and slots 7 and 8 configured in the unprotected configuration. Figure 429

MSS-8 stand-alone shelf, equipped with P2E3DS3 (DS3 Card)

MSS-8 shelves supports up to six SDHACC cards in unprotected configurations. Supports up to three pairs of SDHACC cards in 1+1 EPS protected configurations. In 1+1 EPS protected configuration, the main SDHACC cards are equipped in slots 3, 5, and/or 7, and the spare (protection) SDHACC cards are equipped in slots 4, 6, and/or 8 respectively. See Figure 430 to see an example of the MSS-8 shelf configured as a split mount, 1+0 drop and insert repeater in slots 7 and 8, with a pair of P32E1DS1s in slots 3 and 4 in the protected 1+1 EPS configuration, and with a pair of P2E3DS3s in slots 5 and 6 in the protected 1+1 EPS configuration. See Figure 431 to see an example of the MSS-8 shelf configured as a split mount, 1+1 drop and insert repeater in slots 5 through 8, with a P32E1DS1s in slot 3 in the unprotected configuration, and with a P2E3DS3 in slot 4 in the unprotected configuration.

847



Figure 430

MSS-8 shelf, split mount, 1+0 drop and insert repeater configuration

Figure 431

MSS-8 shelf, split mount, 1+1 drop and insert repeater configuration

MSS-8 shelves supports up to six MPTACC cards in unprotected configuration, up to twelve RF radio channels. Supports three pairs of MPTACC cards in protected 1+1 HSB/FD configuration, up to six protected RF radio channels. In 1+1 HSB, SD or FD configuration, the main MPTACC card is equipped in slot 3, 5, and/or 7 and the spare (protection) MPTACC card is equipped in slot 4, 6, and/or 8 respectively. See Figure 432 to see an example of the MSS-8 shelf configured as a split mount, unprotected Core-E, 12-way nodal junction in slots 3 through 8. See Figure 433 to see an example of the MSS-8 shelf configured as a protected Core-E, 1+1 protected 4-way junction in slots 5 through 8, and slots 3 and 4 configured in the unprotected E1/DS1 configuration.

848



Figure 432

MSS-8 shelf, split mount MPT ODU, 1+0 12-way nodal junction configuration

Figure 433

MSS-8 shelf, all indoor mount, 1+1 4-way junction configuration

MSS-8 shelves equipped with EAS cards, the EAS is supported in slots 3 through 8. For stacked EAS applications, the main EAS card resides in slot 3, 5, and/or 7 and the spare EAS resides in slots 4, 6, and/or 8. See Figure 434 to see an example of the MSS-8 shelf configured as an all indoor mount, 1+0 4-way junction in slot 3, with a pair of P32E1DS1s in slots 5 and 6 in the protected 1+1 EPS configuration. See Figure 435 to see an example of the MSS-8 shelf configured as an all indoor mount, 1+1 4-way junction in slots 3 and 4, with three P32E1DS1s in slots 5 through 7 in the unprotected configuration.

849



Figure 434


Figure 435


See Figure 436 to see an example of the MSS-8 shelf configured as a 12 spoke hub using all indoor mount (EAS/MPT-HL).

850


Figure 436


MSS-8 shelf, 1+0, 12 spoke hub configuration

See Figure 437 to see an example of the MSS-8 shelf configured mixing all three radio technologies. EAS cards equipped in slots 3 and 4 support up to eight MPT-HL 1+0 unprotected radio channels or as shown up to four MPT-HL 1+1 protected radio channels. MPT Access cards in slots 5 and 6 support up to 4 MPT ODU 1+0 unprotected radio channels, or as shown two MPT ODU 1+1 protected radio channels. The MOD300 card in slot 7 supports one ODU300 1+0 radio channel. Slot 8 is shown with one 1+0 P32E1DS1 E1/DS1 Interface with support for up to 32 E1/ DS1 signals. The Core card in slot 1 can support the following: •

up to six MPT ODU 1+0 radio channels

•

up to three MPT ODU 1+1 radio channels

•

up to two MPT-HL 1+0 radio channels

851


Figure 437



22.4

Functional overview MSS-8 implements functionality of grooming, routing, switching and protection, exploiting a packet oriented technology in order to meet the overall architecture. The MSS-8 Core platform, with multiplexing and symmetrical cross-connect functions, can manage different radio directions (up to fourteen), with the possibility to add-drop data flows of local E1/DS1/DS3/OC-3/Ethernet traffic. Core platform is based on packet technology (Ethernet Switch) with a generic serial GigE interface between the Core and transport cards. The MSS-8 shelf houses the following cards:

852

•

Core-E Control and Switching Module—houses one main and one optional spare control and switching modules. Provides four 10/100/1000 Base-T Ethernet ports. Provides two GigE optical Ethernet port.

•

CorEvo Control and Switching Module—houses one main and one optional spare control and switching modules. Provides four 10/100/1000 Base-T Ethernet ports. Provides two GigE optical Ethernet ports and two 1/10GigE optical Ethernet ports.

•

MPTACC MPT Access card—houses up to six MPTACC cards for MSS-8 to two MPT ODU interfaces (Ethernet and power) for split mount configuration.

•

P2E3DS3 DS3 PDH card—houses up to six P2E3DS3 cards for DS3 TDM traffic encapsulation/extraction into standard Ethernet packets



•

EAS Ethernet Access Switch (P8ETH or EASv2)—houses up to six EAS cards for MSS-8-to-MPT-HL or MSS-8-to-MPT ODU interfaces. The EAS card functions as a layer 2 switch, cross-connecting VLAN tagged Ethernet data to/from the addressed MPT unit. The EAS card provides traffic management for Core cards for up to six directions using protected radios and up to twelve directions using unprotected radios. EAS cards also provide four 10/100/1000 Base-T Ethernet ports and up to four GigE optical Ethernet ports.

•

P32E1DS1 PDH card—houses up to six P32E1DS1 cards for E1/DS1 TDM traffic encapsulation/extraction into standard Ethernet packets

•

SDHACC OC-3 SDH card—houses up to six SDHACC cards for OC-3 TDM traffic encapsulation/extraction into standard Ethernet packets

•

The MSS-8 shelf houses one fan card resident in slot 9 on the right-hand side of the shelf and provides forced-air cooling for the shelf.

•

The MSS-8 shelf houses up to one AUX card optional in slot 8 to provide up to nine station alarm inputs and eight station alarm control outputs.

853


854







NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB18219AB


N/A

N/A

N/A

Active

3DB18163AB

MSS-4/8 Shelf Slot Cover MSS-4/8 shelf slot cover is required for all unequipped slots for EMI compliance and correct system cooling.

N/A

—

—

Active

3EM24463AA

MSS-4 shelf Kit MSS-4 shelf kit provides one MSS-4 shelf, power cable, FAN card, and miscellaneous rack hardware.

N/A

N/A

N/A

Active

3DB18835AA

MSS-4 shelf kit without PBA If the FAN-1 module is to be used, this kit must be equipped.

N/A

N/A

N/A

Active

23.1


The Microwave Service Switch (MSS-4) shelf provides cross-connection, port aggregation, switching, and equipment management.

•

16Gb Packet Based Node

•

300 Mb/s full-duplex Ethernet transport capacity

•

Flexible aggregate capacity sharing PDH, SDH and Ethernet traffic

855


•

Split mount configuration utilizing the MPTACC card supports up to four unprotected RF channels, up to two 1+1 HSB, Space Diversity (SD) or Frequency Diversity (FD) protected RF channels in one MSS-4 shelf connected to up to four MPT ODUs.

•

Split mount configuration utilizing the Core SFP ports supports:

•

23.2


−

up to two unprotected RF channels in one MSS-4 shelf connected to up to two MPT-HC/HC-HQAM/XP/XP-HQAM transceivers

−

up to one protected RF channel in one MSS-4 shelf connected to up to two MPT-HC/HC-HQAM/XP/XP-HQAM transceivers.

Split mount configuration utilizing the Core electrical Ethernet ports supports: −

up to four unprotected RF channels in one MSS-4 shelf connected to up to four MPT ODUs.

−

up to two protected RF channels in one MSS-4 shelf connected to up to four MPT ODUs.

•

All indoor mount utilizing the P8ETH cards support up to ten unprotected RF channels, four 1+1 HSB, Space Diversity (SD) or Frequency Diversity (FD) protected RF channels in one MSS-4 shelf using P8ETH cards connected to up to four Microwave Packet Transport-Long Haul (MPT-HL) Transceivers and the Core card connected to up to two MPT-HL shelves.

•


•

All cards are accessed from the front side of the shelf

•

Mounts in a 19-inch aluminum rack or 19-inch seismic rack. Adapter flanges available to mount in a 23-inch aluminum rack

•


•

Provides five card slots. Two are dedicated for Control and Switching Modules (Core-E and CorEvo). Two universal slots are available for transport cards: P32E1DS1, P2E3DS3, SDHACC, MPTACC and/or EAS. One slot supports optional AUX card. One slot is dedicated for fan card.

Description The MSS-4 self consists of a module cage and backplane which provides five slots. See Figure 438 for an example of the MSS-4 shelf. The MSS-4 shelf is 19 inches wide (17.25 inches wide without mounting flanges), 1.73 inches high (1 EIA rack increments), and 9.75 inches deep. Adapter plates are available to mount the MSS-4 shelf in 23 inch aluminum racks. See Figure 439 for outline and shelf dimensions of the MSS-4 shelf.

856



Figure 438


Figure 439

MSS-4 shelf dimensions

23.3

Equipment complement MSS-4 shelf slots 1 and 2 are dedicated to the Core card. Slots 3 and 4 are available for transport cards; P32E1DS1, P2E3DS3, MPTACC, SDHACC, and/or EAS. Slot 4 supports optional AUX card. Slot 5 is dedicated for required fan card. See Figure 440 for MSS-4 shelf slot definitions. See Table 77 for details of card equipage options.

Figure 440

MSS-4 shelf slot definitions

857


Table 77


MSS-4 shelf card complement


PART NO.

CLEI

QTY

SLOT

Core-E control and switching module Core-E control and switching module unit data sheet

3DB18326AC

CRCCACMJAA

1 or 2

1 and 2

CorEvo-10G control and switching module CorEvo control and switching module unit data sheet

3DB19318AA 3DB18788AC

CRGIAEGKAA

1 or 2

1 and 2

MPTACC MPT Access MPTACC MPT access card unit data sheet

3DB18634AB

N/A

Up to 6

3, 4, 5, 6, 7, 8

P2E3DS3 DS3 PDH Card P2E3DS3 DS3 PDH card unit data sheet

3DB18194AC

CRG2AA9DAA

Up to 6

3, 4, 5, 6, 7, 8

P8ETH Ethernet Access Switch Card P8ETH Ethernet access switch card unit data sheet

3DB18206AC

CRCCACGJAA

Up to 2

3, 4, 5, 6, 7, 8

EASv2 Card EASv2 Ethernet access switch card unit data sheet

3DB19017AB

CRG2AKKDAA

Up to 2

3, 4, 5, 6, 7, 8

P32E1DS1 PDH Card P32E1DS1 PDH card unit data sheet

3DB18126AE

CRG2ABUDAA

Up to 6

3, 4, 5, 6, 7, 8

SDHACC SDH Card SDH card unit data sheet

3DB18735AA

N/A

Up to 6

3, 4, 5, 6, 7, 8

AUX Auxiliary Card AUX auxiliary card unit data sheet

3DB18236AB

N/A

Up to 1

8

858



MSS-4 shelf slot 1 is dedicated to the main Core card and is required in every application. See Figure 441 to see an example of the MSS-4 shelf configured in the unprotected Core configuration. Slot 2 is dedicated for an optional spare Core card for protected Core configurations. See Figure 442 to see an example of the MSS-4 shelf configured in the protected Core-E configuration. Figure 441


Figure 442


MSS-4 shelves supports up to two P32E1DS1 card in unprotected E1/DS1 aggregation configurations. Supports one pair of P32E1DS1 cards in 1+1 EPS protected E1/DS1 aggregation configuration. In 1+1 EPS protected configuration, the main P32E1DS1 card is equipped in slot 3 and the spare (protection) P32E1DS1 card is equipped in slot 4 respectively. See Figure 443 to see an example of a stand-alone MSS-4 shelf configured with one pair of P32E1DS1s in slots 3 and 4 in the protected 1+1 EPS configuration. Figure 443

MSS-4 stand-alone shelf, equipped with P32E1DS1 (DS1 card)

859



MSS-4 shelves supports up to two P2E3DS3 cards in unprotected configurations. Supports one pair of P2E3DS3 cards in 1+1 EPS protected configurations. In 1+1 EPS protected configuration, the main P2E3DS3 card is equipped in slot 3, and the spare (protection) P2E3DS3 card is equipped in slot 4 respectively. See Figure 444 to see an example of a stand-alone MSS-4 shelf configured with one pair of unprotected P2E3DS3s in slots 3 and 4 in the unprotected configuration. Figure 444

MSS-4 stand-alone shelf, equipped with P2E3DS3 (DS3 card)

MSS-4 shelves supports up to two SDHACC cards in unprotected configurations. Supports one pair of SDHACC cards in 1+1 EPS protected configurations. In 1+1 EPS protected configuration, the main SDHACC card is equipped in slot 3, and the spare (protection) SDHACC card is equipped in slot 4 respectively. MSS-4 shelves supports up to two MPTACC cards in unprotected configuration, up to four RF radio channels. Supports one pair of MPTACC cards in protected 1+1 HSB/FD configuration, up to two protected RF radio channels. In 1+1 HSB, SD or FD configuration, the main MPTACC card is equipped in slot 3 and the spare (protection) MPTACC card is equipped in slot 4 respectively. See Figure 445 to see an example of the MSS-4 shelf configured as a split mount, unprotected, up to 2-way junction in slot 3, with a P32E1DS1 card in slot 4. See Figure 449 to see an example of the MSS-4 shelf configured as a split mount, 1+1 EPS, up to 2-way junction in slots 3 and 4. See Figure 447 to see an example of the MSS-4 shelf equipped with two MPTACC cards supports up to a four spoke hub. In this configuration; main MPTACC cards are equipped in slots 3 and 4 and support up to four 1+0 spokes.

860



Figure 445

MSS-4 shelf, split mount using MPTACC, 1+0 2-way junction configuration

Figure 446


Figure 447


MSS-4 shelves supports up to two P8ETH cards in unprotected configuration. Supports one pair of P8ETH cards in protected in 1+1 EPS configuration. In 1+1 EPS configuration, the main P8ETH card is equipped in slot 3 and the spare (protection) P8ETH card is equipped in slot 4 respectively. See Figure 448 to see an example of the MSS-4 shelf configured as an all indoor mount, unprotected, up to 4-way junction in slot 3, with a P32E1DS1 card in slot 4. See Figure 449 to see an example of the MSS-4 shelf configured as an all indoor mount, 1+1 EPS, up to 4-way junction in slots 3 and 4. See Figure 450 to see an example of the MSS-4 shelf equipped with two P8ETH cards support up to an eight spoke hub. In this configuration; main P8ETH cards are equipped in slots 3 and 4 and support up to eight 1+0 spokes.

861



Figure 448


Figure 449


Figure 450


MSS-4 shelf slot 4 supports the AUX (Auxiliary) card for applications that require office station alarms and controls.

23.4

Functional overview MSS-4 implements functionality of grooming, routing, switching and protection, exploiting a packet oriented technology in order to meet the overall architecture.

862



The MSS-4 Core platform, with multiplexing and symmetrical cross-connect functions, can manage different radio directions (up to four), with the possibility to add-drop data flows of local E1/DS1/DS3/OC-3//Ethernet traffic. Core platform is based on packet technology (Ethernet Switch) with a generic serial GigE interface between Core and transport cards. The MSS-4 shelf houses the following cards: •

AUX Auxiliary card—houses one optional Auxiliary card in slot 4. Auxiliary card provides six station alarm inputs and seven station alarm control outputs.

•

Core-E Control and Switching Module—houses one main and one optional spare control and switching modules. Provides four 10/100/1000 Base-T Ethernet ports. Provides two GigE optical Ethernet port.

•

CorEvo Control and Switching Module—houses one main and one optional spare control and switching modules. Provides four 10/100/1000 Base-T Ethernet ports. Provides two GigE optical Ethernet ports and two 1/10GigE optical Ethernet ports.

•

P2E3DS1 1 PDH card—houses up to two P2E3DS1 cards for E1/DS1 TDM traffic encapsulation/extraction into standard Ethernet packets

•

P8ETH Ethernet Access Switch—houses up to two P8ETH cards for MSS-4to-MPT-HL interface for all indoor configurations. The P8ETH card functions as a layer 2 switch, cross-connecting VLAN tagged Ethernet data to/from the addressed MPT-HL. The P8ETH card provides traffic management for Core for up to four directions using protected radios and up to eight directions using unprotected radios. P8ETH cards also provide four 10/100/1000 Base-T Ethernet ports and up to four GigE optical Ethernet ports.

•

SDHACC OC-3/STM-1 SDH card—houses up to two SDHACC cards for OC-3 TDM traffic encapsulation/extraction into standard Ethernet packets

•

P2E3DS3 DS3 PDH card—houses up to two P2E3DS3 cards for DS3 TDM traffic encapsulation/extraction into standard Ethernet packets

•

The MSS-4 shelf houses one fan card resident in slot 5 on the right-hand side of the shelf and provides forced-air cooling for the shelf.

863


864







NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB19015AA


DRMVY10DR A

N/A

N/A

Active

3DB19015BA


N/A

N/A

N/A

Active

3MU00109AA

MSS-1 shelf Kit MSS-1 shelf kit provides one MSS-1 shelf, power cable, and miscellaneous rack hardware. Includes 2-Conductor Power Wire, 17 AWG, PN: 1AC007800068

N/A

N/A

N/A

Inactive

3MU00109AB

MSS-1 shelf Kit MSS-1 shelf kit provides one MSS-1 shelf, power cable, and miscellaneous rack hardware. Includes 2-Conductor Power Wire, 17 AWG, PN: 1AC007800068

N/A

N/A

N/A

Active

3DB19002AA

Field Assembly parts kit Includes Ferrite Beads, PN: 1AB093970013

N/A

N/A

N/A

Active

865


24.1


Features and application notes Warning: MSS1/MSS-O output connectors for supplying power to MPT family ODU units (port 1 and 2) are NOT to be considered as ordinary Power Over Ethernet connectors as they can supply up to 2 A. For this reason only the dedicated cable (ALU code 1AC016760006) can be connected to these ports. WARNING DONOT CONNECT ORDINARY POE CABLES TO THESE PORTS.

Note: The above Warning applies to MPT radio applications where the Ethernet port provides power to an MPT ODU unit. In these applications the 1AC016760006 cable MUST be used.

In applications where the port does not provide power to the MPT ODU, such as when an external power device is used to provide power to an MPT ODU or when the Ethernet port is used strictly for data traffic, an appropriate Ethernet cable may be used.

24.2

•

The Microwave Service Switch (MSS-1) is a monoboard that provides user Ethernet, TDM, housekeeping and management interfaces.

•

16 Gb Packet Based Node

•

1 Gb/s full-duplex Ethernet transport capacity

•

Flexible aggregate capacity sharing E1/DS1 and Ethernet traffic

•

IPv6 routing and tunneling

•

Four housekeeping alarm input interfaces

•

Three housekeeping alarm output interfaces (alarm LEDs)

•


•


•

Provides two mounting options: flush mount or 5 inch projection

Description See Figure 451 for an example of the MSS-1 shelf. The MSS-1 shelf is 16.14 inches wide, 0.08 inches high, and 5.51 inches deep. See Figure 452 for outline and shelf dimensions of the MSS-1 shelf.

866



Figure 451


Figure 452

MSS-1 unit dimensions 482.6

MSS 1

21.8 465.1 5.95 23184

24.3

Functional overview MSS-1 implements functionality of grooming, routing, and switching, exploiting a packet oriented technology in order to meet the overall architecture. The MSS-1 Core platform, with multiplexing and symmetrical cross-connect functions, can manage different radio directions (up to six), with the possibility to adddrop data flows of local E1/DS1 traffic.

24.4

Front panel connectors The MSS-1 provides six native Ethernet user interfaces. Using these interfaces, you can connect any radio that can be connected to a Core card. In applications where the port does not provide power to the MPT ODU, such as when an external power device is used to provide power to an MPT ODU or when the Ethernet port is used strictly for data traffic, an appropriate Ethernet cable may be used. Warning: MSS-1/MSS-O output connectors for supplying power to MPT ODUs (port 1 and 2) can supply up to 2 A. For this reason only the dedicated cable (1AC016760006) can be connected to these ports. Do not connect ordinary PFoE cables to these ports.

867




In applications where the port does not provide power to the MPT ODU, such as when an external power device is used to provide power to an MPT ODU or when the Ethernet port is used strictly for data traffic, an appropriate Ethernet cable may be used. Table 79 defines the port numbering, interface type, traffic support and MPT connectivity. Table 79

MSS-1 ports

Ports

Interface type

Traffic/TMN In-band ports

1

10/100/1000BaseT with PFoE

2

TMN Out-band ports

MPT-HC/ HC-HQAM ports

MPT-XP/ XP-HQAM 1 ports

X

X

X


X

X

X

3

10/100/1000BaseT without PFoE

X

X1

X

4


X

X2

X

5

GigE optical

X

X2

X

X

6

GigE optical

X

X2

X

X

X

MPT-HL ports

1. An MPT Extended Power Unit is required to connect an MPT-XP/XP-HQAM to all MSS-1 shelf 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 these ports. Power the ODU according to the information in the UDSs for the MPT-HC and MPT-HC-HQAM. The following are the connectors on the front panel of the MSS-1:

868



•

2 RJ-45 connectors (PFoE): These connectors provide Ethernet links with a maximum autonegotiation capability of 1 Gb/s and provide power to the ODU through a proprietary PFoE.

•

2 RJ-45 connectors (without PFoE): These connectors provide Ethernet links with a maximum autonegotiation capability of 1 Gb/s.

•

1 RJ-45 connector (Management Port): This connector provides an Ethernet link (10/100) to the microprocessor through a single PHY for the craft terminal. This connector is direct, with no inversion of Tx and Rx and a UART interface to the microprocessor for debugging. The signal for the Serial Debug interface is also present in this connector.

•

2 Ethernet optical interfaces (SFP standard), connected to the FPGA.

•

1 female SCSI connector: M15.

•

1 15 position D-Sub connector. This connector provides the housekeeping alarm inputs and outputs.

•

2 battery connectors: A and B

•

The flash card is available at the front panel

Table 80 provides the pinout information for the RJ-45 connectors. Table 80

MSS-1 pinout RJ-45 connector (NMS+Debug)

PIN #

Signal

1

TX_P

2

TX_N

3

RX_N

4

Debug_TX

5

Debug_Rx

6

RX_P

7

DTR

8

GND Table 81 and Table 82 provide the pinout information for the SCSI connector.

869


Table 81


68 pin SCSI cable input (RCV) pinout

PAIR

FROM

WIRE COLOR

FUNCTION

1

Jx-3

White/Blue

Input1 - Tip (RCV)

Jx-37

Blue/White

Input1- Ring (RCV)

Jx-5

White/Orange

Input2 - Tip (RCV)

Jx-39

Orange/White

Input2- Ring (RCV)

Jx-7

White/Green

Input3- Tip (RCV)

Jx-41

Green/White

Input3- Ring (RCV)

Jx-9

White/Brown

Input4 - Tip (RCV)

Jx-43

Brown/White

Input4- Ring (RCV)

Jx-11

White/Slate

Input5 - Tip (RCV)

Jx-45

Slate/White

Input5- Ring (RCV)

Jx-13

Red/Blue

Input6 - Tip (RCV)

Jx-47

Blue/Red

Input6- Ring (RCV)

Jx-15

Red/Orange

Input7 - Tip (RCV)

Jx-49

Orange/Red

Input7- Ring (RCV)

Jx-17

Red/Green

Input8 - Tip (RCV)

Jx-51

Green/Red

Input8- Ring (RCV)

Jx-19

Red/Brown

Input9 - Tip (RCV)

Jx-53

Brown/Red

Input9- Ring (RCV)

Jx-21

Red/Slate

Input10 - Tip (RCV)

Jx-55

Slate/Red

Input10- Ring (RCV)

Jx-23

Black/Blue

Input11- Tip (RCV)

Jx-57

Blue/Black

Input11- Ring (RCV)

Jx-25

Black/Orange

Input12 - Tip (RCV)

Jx-59

Orange/Black

Input12- Ring (RCV)

Jx-27

Black/Green

Input13 - Tip (RCV)

Jx-61

Green/Black

Input13- Ring (RCV)

2

3

4

5

6

7

8

9

10

11

12

13

870


Table 81


68 pin SCSI cable input (RCV) pinout (Continued)

PAIR

FROM

WIRE COLOR

FUNCTION

14

Jx-29

Black/Brown

Input14 - Tip (RCV)

Jx-63

Brown/Black

Input14- Ring (RCV)

Jx-31

Black/Slate

Input15 - Tip (RCV)

Jx-65

Slate/Black

Input15- Ring (RCV)

Jx-33

Yellow/Blue

Input16 - Tip (RCV)

Jx-67

Blue/Yellow

Input16- Ring (RCV)

15

16

Table 82

68 pin SCSI cable output (XMT) pinout

PAIR

FROM

WIRE COLOR

FUNCTION

1

Jx-2

White/Blue

Output1 - Tip (XMT)

Jx-36

Blue/White

Output1- Ring (XMT)

Jx-4

White/Orange

Output2 - Tip (XMT)

Jx-38

Orange/White

Output2- Ring (XMT)

Jx-6

White/Green

Output3- Tip (XMT)

Jx-40

Green/White

Output3- Ring (XMT)

Jx-8

White/Brown

Output4 - Tip (XMT)

Jx-42

Brown/White

Output4- Ring (XMT)

Jx-10

White/Slate

Output5 - Tip (XMT)

Jx-44

Slate/White

Output5- Ring (XMT)

Jx-12

Red/Blue

Output6 - Tip (XMT)

Jx-46

Blue/Red

Output6- Ring (XMT)

Jx-14

Red/Orange

Output7 - Tip (XMT)

Jx-48

Orange/Red

Output7- Ring (XMT)

Jx-16

Red/Green

Output8 - Tip (XMT)

Jx-50

Green/Red

Output8- Ring (XMT)

2

3

4

5

6

7

8

871


Table 82


68 pin SCSI cable output (XMT) pinout (Continued)

PAIR

FROM

WIRE COLOR

FUNCTION

9

Jx-18

Red/Brown

Output9 - Tip (XMT)

Jx-52

Brown/Red

Output9- Ring (XMT)

Jx-20

Red/Slate

Output10 - Tip (XMT)

Jx-54

Slate/Red

Output10- Ring (XMT)

Jx-22

Black/Blue

Output11- Tip (XMT)

Jx-56

Blue/Black


Jx-24

Black/Orange


Jx-58

Orange/Black


Jx-26

Black/Green


Jx-60

Green/Black


Jx-28

Black/Brown


Jx-62

Brown/Black


Jx-30

Black/Slate


Jx-64

Slate/Black


Jx-32

Yellow/Blue


Jx-66

Blue/Yellow


10

11

12

13

14

15

16

Table 83 describes the pinout configuration of the frontal connector used for housekeeping. Table 83

MSS-1 house-keeping pinout (sub D15 female)

PIN

SIGNAL

PIN

SIGNAL

1

HK_IN1

9

—

2

HK_IN2

10

HK_OUT2 -

3

—

11

HK_IN3

4

HK_OUT3 +

12

HK_IN4

5

HK_OUT3 -

13

—

872


Table 83


MSS-1 house-keeping pinout (sub D15 female) (Continued)

PIN

SIGNAL

PIN

SIGNAL

6

—

14

HK_OUT1 +

7

GND

15

HK_OUT1 -

8

HK_OUT2 +

—

—

24.5

Alarm and LED behavior The MSS-1 unit provides the following functionality: •

Main Core-E card

•

Main 16 port P32E1DS1 card

•

Housekeeping alarm input/outputs

Core-E card alarms are reported as MSS/CORE. E1/DS1 card alarms are reported MSS/DS1 or MSS/E1. The Card Fail alarm indicates one or more of the following: •

lack of secondary power supply

•

loss of FPGA

•

loss of oscillator

•

loss of -55 V DC/DC power supply

873


24.5.1


LEDs The front panel of the MSS-1 has the following LEDs: •

Major alarm (red): at least one Major or Critical alarm is present

•

Minor alarm (red): at least one Minor alarm is present

•

Warning (yellow): at least one Warning alarm is present

•

Abnormal (yellow): at least one Abnormal Condition is present

•

Status

•

2 PFoE LEDs: on indicates that PFoE is active

Table 84 describes the behavior of the status LED. Table 84

Status LED behavior

DESCRIPTION

LED COLOR

Not equipped, not provisioned, or not powered

Off

FPGA download or software booting

Green blinking

Card in service

Green

MSS-1 failure

Red Table 85 describes the cable details of the housekeeping alarm inputs and outputs.

Table 85

MSS-1 office alarm and control connector / cable detail

PIN DEFINITION

CONTACT NUMBER

WIRE COLOR

Alarm Input 1

01

White/Blue

Alarm Input 2

02

Blue/White

Alarm Input 3

11

White/Orange

Alarm Input 4

12

Orange/White

Ground

07

White/Green

14

White/Brown

15

Brown/White

Alarm Output 1 Alarm Output 1

874

Function

Summary Alarm


Table 85


MSS-1 office alarm and control connector / cable detail (Continued)

PIN DEFINITION

Function

CONTACT NUMBER

WIRE COLOR

Alarm Output 2

Major Alarm

08

White/Slate

10

Slate/White

04

Red/Blue

Alarm Output 3

05

Blue/Red

Not Used

03

N/A

Not Used

06

N/A

Not Used

09

N/A

Not Used

13

N/A


24.6

Minor Alarm

Output alarm electrical characteristics Each alarm output has two pins. Depending if the alarm is present or not the two relevant pins will be in short circuit or in open circuit condition. When the relay alarm output pins will be in short circuit condition, the alarm outputs will tolerate a 50mA max current and the max voltage between the two pins never exceed 2V. When the relay alarm output pins are in open circuit condition the alarm outputs will tolerate 60V and the max leakage current will never exceed 0.2mA.

24.7

Input alarm electrical characteristics The inputs must be able to reveal if the relevant pin is open or short circuit with respect to GND. Table 86 shows the alarm behavior.

Table 86

Input alarm electrical behavior

Input pin status

OPEN

Logical “1”

GND (0V)

Logical “0”

Alarmed, Not Alarmed condition depends on alarm polarity settings provisioned

The short circuit is detected with an input voltage -2V < V < 0V.

875



The open circuit is detected with an input voltage -60V < V < -2.2V. The negative voltage is allowed for compatibility with legacy equipment which have their Housekeeping Output done with a PNP Open collector circuit. That needs to be biased with a negative voltage. The alarm inputs can tolerate –60 volts to +5 volts without damage.

24.8

Power supply For MSS-1, PN 3DB19015AA, the input voltage for the MSS-1 is -20 VDC to -72 VDC or +20 to +72 VDC. The current range is from 7.5 A to 2.0 A, depending on input voltage and number of PFoE interfaces in use. Dual battery inputs are supported. The battery is isolated at the MSS-1 level toward the radios. Battery protection is enabled by default. For MSS-1, PN 3DB19015BA, the input voltage is -38.4 VDC to -57.6 VDC. The max current is 4.7 A, depending on input voltage and number of PFoE interfaces in use. Dual battery inputs are supported. Battery protection is enabled by default.

24.9

Environmental conditions Environmental conditions are compliant with ETS EN 300 019-2-3 class 3.2 plus extended range (GR-3108 Section 1.3.2, Class 2): •

Stationary use class 3.2

•

Transportation class 2.3

•

Storage class 1.2

•

Cabinet degree of protection IP20

•

Acoustic noise class 3.1 & 3.2

See the 9500 MPR Technical Specifications for Split Mount Applications for more information.

876



25 MSS-1c unit data sheet Table 87

MSS-1c

Name

Code

Remarks

MSS-1c 16PDH

3DB18613BAXX

Up to 16E1/T1s supported

MSS-1c (ETSI market only)

3DB18613AAXX

Up to 10E1s supported

MSS-1c Fan unit

3DB77002AAXX

To be installed if the ambient temperature is higher than 55°C (for MSS-1c 16PDH) and 50°C (for MSS-1c)

25.1

Description The MSS-1c provides user port interface, cross-connection and switching management. The cross-connection matrix implements all the cross-connections between the User ports (4 Ethernet ports and E1/T1 streams) and the Radio port. The matrix is a standard Ethernet switch, based on VLAN, assigned by MCT. The E1/T1 enter the LIU, then the IWF, which manages the encapsulation and reconstruction of PDH data to and from standard Ethernet packets and sends and receives standard Ethernet packets to and from the Ethernet switch. Two variants of MSS-1c are available: •

MSS-1c providing 10E1 and 4 User Ethernet ports

•

MSS-1c 16PDH providing 16E1 or 16T1 and 4 User Ethernet ports. This version is HW ready to manage up to 2 STM-1 frames (instead of 2 Ethernet ports) not supported by the current SW Release

The Radio Interface interfaces the MPT ODU. The radio interface is a standard GbEth interface: electrical only for MPT-MC (ETSI market only) and electrical or optical for MPT-HC, MPT-HC-HQAM, MPT-XP, MPTXP-HQAM, and 9558HC (ANSI market only). It sends/receives standard Ethernet packets to and from the Ethernet switch. In case of electrical radio interface, the power supply for the MPT is also sent on the same cable by using the Power Feed over Ethernet (PFoE) function.

877

Release 7.0.0 3DB 19383 ACAA Issue 01 MSS-1c unit data sheet


Note: The MPT ODU can also be connected by using an optical cable for the Ethernet traffic and a coaxial cable for the power supply.

The MSS-1c incorporates the base–band processing and also radio interface functionalities only when the MPT ODU is connected. MSS-1c offers tributaries interfaces as well as supervision. The MSS-1c is frequency–independent. (*)Not supported in the current release. (**)Depending on the MSS-1c variant. Figure 453

MSS-1c front view

Figure 454

MSS-1c rear view

878



Note: To use the User Ethernet Ports 3 and 4 an SFP plug-in (electrical or optical) must be installed

The meanings of the six LEDs are: •

LED M: Major Alarm (red)

•

LED m: Minor Alarm (red) (not supported in the current release: permanently OFF)

•

LED W: Warning (yellow) (not supported in the current release: permanently OFF)

•

LED A: Abnormal condition (yellow)

•

LED MPT1: MPT Status (green/red/yellow)

•

LED MPT2: not supported

LED A is ON in the following conditions: •

Tx Power muted by operator

•

ACM frozen by operator

•

MPT loopback active

LED MPT1 can be: •

GREEN: MPT is emitting power as expected according the known configuration

•

YELLOW: MPT is not emitting power due to a forced Squelch condition

•

RED: MPT is abnormally emitting power

•

SWITCHED OFF: MPT is not emitting power according with the known configuration

At start-up the MSS-1c: •

lights on all the alarm LEDs (Major, Minor, Warning and Abnormal)

•

lights on the MPT LED as yellow, then this LED will be GREEN, RED or YELLOW, as explained above.

See the 9500 MPR Technical Specifications for Split Mount Applications for technical information.

879


25.1.1


External user interface •

2 traffic 10/100/1000 Base-T Ethernet interfaces for data and service traffic via RJ45 connector

Note: For 100 Ethernet interface the standard is 100Base-Tx.

•

2 SFP ready to accept optical 1000Base-LX/SX SFP or Electrical 1000BaseT SFP

•

2x 10/100 Ethernet NMS interfaces for connection of TMN on RJ45 connector

•

1 Local Craft terminal interface 10/100 Ethernet allows the straight connection to MPT remote Controller via RJ45 connector

•

10E1 or 16E1/T1 bi-directional interfaces on 2 subD connectors

•

4 In housekeeping for external alarms collections, RJ45 connector + 2 IN/ OUT (not supported)

•

9 poles SubD Connector in the rear side for FAN unit feed/control.

25.1.2

2 traffic 10/100/1000 Base-T Ethernet interfaces for data and service traffic via RJ45 connector

25.1.3

Power supply The MSS-1c receives the Battery input through 1 power connector mounted on the front panel. The input voltage range is from -38.4 V to -57.6 Vdc.

880


25.1.4


Ethernet switch

The switch provides the following features:

25.1.5

•

Address learning up to 8K Mac address and static entries,

•

Standard 802.1Q management (VLAN)

•

Layer 2 switching (MAC Address)

•

2 QoS per port (802.1P and DiffServ)

•

Flexible output scheduler: SP (strict priority), DWRR (deficit weighted round robin).

E1/T1 interface The E1/T1 Interface performs the following macro functions: •

ETSI market: Termination of 10E1 or 16E1 signals (E1 bi-directional interfaces according ITU-T G.703 on the front panel)

•

ANSI market: Termination of 16T1 signal with MSS-1c 16PDH variant (T1 bidirectional interfaces according to ANSI T1.403/TR 62411 on the front panel)

•

Encapsulation/Extraction of those PDH data flows into/from standard Ethernet packets Inter Working Function

•

Reconstruction of the original PDH Timing

•

Sending/getting those std Ethernet packets to the Ethernet switch

•

Communication with the Controller for provisioning and status report.

881


25.1.6


MPT interface The MPT Interface is the interface for one MPT ODU. For interconnections with MSS-1c, see MSS-1c to MPT-HC/HC-HQAM/9558HC interconnection, MSS-1c to MPT-XP/XP-HQAM interconnection, and MSS-1c to MPT-MC interconnection.

25.1.6.1

25.1.7

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

•

Clock distribution function

•

Ethernet link quality monitor function

•

Communication with Controller for provisioning and status report.

Ethernet user interface The following 4 Ethernet User Interfaces are available: •

2 traffic 10/100/1000 Base-T Ethernet interfaces for data and service traffic via RJ45 connector. N.B. For 100 Ethernet interface the standard is 100Base-Tx.

•

2 SFP ready to accept optical 1000Base-LX/SX SFP or Electrical 1000BaseT SFP.

The User port 2 can be used as SynchE synchronization. The User port 3 and port 4 can be used as SynchE synchronization in optical mode. Note: In the ETSI market, User port 3 is not available as a synchronization source on the MSS-1c variant.

882


25.2


MSS-1c Fan unit An optional Fan unit must be used to dissipate the MSS-1c in the special case when the ambient temperature is > +50°C (MSS-1c) or >+55°C (MSS-1c 16PDH). Figure 455 shows the installation position: the MSS-1c on the right and the Fan unit on the left. The MSS-1c and the Fan unit are mounted on a bracket compatible with 19" rack. Height is 1.3U. The Fan unit is powered by the MSS-1c with a cable placed on the rear side. The cable is provided with the Fan unit. The Fan unit includes two fans. One bi-color LED on the front panel gives the status of the Fan unit:

Figure 455

•

Fans alarm = OFF <-> LED = green

•

Fans alarm = ON <-> LED = red

MSS-1c and Fan unit

883


884




26 MSS-O microwave service switch shelf unit data sheet Table 88

MSS-O microwave service switch shelf


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB19139AA

MSS-O Microwave Service Switch Shelf (AC version)

CRM6A10ERA

N/A

N/A

Active

3DB19280AA

MSS-O Microwave Service Switch Shelf (DC version)

CRM7E10ARA

N/A

N/A

Active

3DB19159AA

MSS-O Kit (AC version) MSS-O kit provides one MSS-O, power cable, and wall or pole mounting hardware.

N/A

N/A

N/A

Active

3DB19182AA

MSS-O Kit (DC version) The MSS-O wall or pole mounting kit provides the hardware to mount an MSS-O on a wall or 114 mm pole.

N/A

N/A

N/A

Active

1AB150990012

RFE connector housing for MSS-O

N/A

N/A

N/A

Active

26.1


The Microwave Service Switch (MSS-O) is a monoboard that provides optical and electrical user Ethernet interfaces.

•

Two electrical interfaces support PFoE

•


•

Mounts outdoors on a pole or wall

•

Mounts in a 19-inch aluminum rack, 19-inch seismic rack, or 21-inch rack.

885

Release 7.0.0 3DB 19383 ACAA Issue 01 MSS-O microwave service switch shelf unit data sheet

26.2


Description See Figure 456 for an example of the MSS-O unit. The MSS-O unit is 13.58 inches long, 8.25 inches wide, and 2.56 inches deep.

Figure 456

Microwave service switch (MSS-O) unit

26.3

Functional overview The MSS-O provides two PFoE-capable 10/100/1000 BaseT Ethernet interfaces, one non-PFoE-capable 10/100/1000 BaseT Ethernet interface, and one optical Ethernet SFP interface. In-band TMN is supported on all ports. The following are not supported:

886

•

Out-band TMN

•

Sync-in and sync-out ports (synchronization must be performed using SynchE or a radio link)

•

PDH interfaces

•

SDH interfaces

•

Housekeeping interfaces

•

CPU reset button


26.4


Connectors The MSS-O provides three native Ethernet user interfaces. Using these interfaces, you can connect an MPT-HC/XP/HC-HQAM/XP-HQAM radio. An SFP can be connected to the optical interface. In applications where the port does not provide power to the MPT ODU, such as when an external power device is used to provide power to an MPT ODU or when the Ethernet port is used strictly for data traffic, an appropriate Ethernet cable may be used. Warning: MSS1/MSS-O output connectors for supplying power to MPT ODUs (port 1 and 2) can supply up to 2 A. For this reason only the dedicated cable (1AC016760006) can be connected to these ports. Do not connect ordinary PFoE cables to these ports.


Table 89 defines the port numbering, interface type, traffic support and MPT connectivity. Table 89

MSS-O ports

Ports

Interface type

Traffic/TMN In-band ports

1


2

TMN Out-band ports

MPT-HC/HCHQAM ports

MPT-XP/XPHQAM ports

X

X

X


X

X

X

3


X

X1

X

4

GigE Ethernet optical

X

1. 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 these ports. Power the ODU according to the information in the UDSs for the MPT-HC and MPT-HC-HQAM.

887



The following are the connectors on the bottom panel of the MSS-O: •

2 RJ-45 connectors (PFoE): These connectors provide Ethernet links with a maximum autonegotiation capability of 1 Gb/s and provide power to the MPT through a proprietary PFoE.

•

1 RJ-45 connector (without PFoE): This connector provides an Ethernet link with a maximum autonegotiation capability of 1 Gb/s.

•

1 Ethernet optical interface (SFP standard), connected to the FPGA.

•

The flash card is available at the bottom panel

Table 90 provides the pinout information for the PFoE RJ-45 connectors. Table 90

MSS-O pinout RJ-45 connector (PFoE)

PIN #

Signal

1

V+

2

V+

3

V+

4

V-

5

V-

6

V+

7

V-

8

V-

Shield

GND

26.5

Alarm and LED behavior MSS-O alarms are reported as MSS- O Core.

26.5.1

LEDs Table 91 describes the behavior of the status LED.

888


Table 91


Status LED behavior

DESCRIPTION

LED COLOR

Not equipped, not provisioned, or not powered

Off

FPGA download or software booting

Green blinking

In service

Green

MSS-O failure

Red

26.6

Power supply See the 9500 MPR Technical Specifications for Split Mount Applications.

26.7

Environmental conditions Environmental conditions are compliant with GR-3108 Class 4: •

Operative temperature range: −40°C / +46°C + Solar Load

•

Full RoHS6

•

Degree of protection IP67

889


890




27 Power distribution unit (PDU) unit data sheet Table 92

Power distribution unit (PDU)


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3EM13317AA

PDU Power Distribution Unit

N/A

N/A

N/A

Inactive

3EM13317AB

PDU Power Distribution Unit with standard fuse alarm card

N/A

N/A

N/A

Active

3EM13317AC

PDU Power Distribution Unit with relay alarm card

N/A

N/A

N/A

Active

Power distribution panel kits 3CC50160AAXX

Panel with 6 fuse holders and one battery input. Height 115mm. Set of fuses included: 6x6A; 6x16A; 2x32A.

N/A

N/A

N/A

Active

3CC50161AAXX

Extension kit to add 6 fuse holders and a second battery input. Set of fuses included: 6x6A; 6x16A; 2x32A.

N/A

N/A

N/A

Active

3CC50155AAXX

Panel with 10 breaker slots and one battery input. Height 132 mm. (No breaker included).

N/A

N/A

N/A

Active

3CC50156AAXX

Panel with 20 breaker slots and two battery inputs. Height 132 mm. (No breaker included).

N/A

N/A

N/A

Active

891

Release 7.0.0 3DB 19383 ACAA Issue 01 Power distribution unit (PDU) unit data sheet

Table 92


Power distribution unit (PDU) (Continued)


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3CC50157AAXX

Extension kit to add 10 breaker slots and a second battery input on a 10-breaker panel. (No breaker included).

N/A

N/A

N/A

Active

27.1

27.2


Distributes A and B battery power that feeds MSS-4/8 and/or MPT-HL shelves and/or auxiliary equipment

•

Provides fused protection for individual shelves and auxiliary equipment

•

Floating Battery inputs to support both ±24 and ±48 VDC operation

•

Optional relay card that provides eight Form-C outputs

•

Mounts in a 19-inch aluminum rack, 19-inch seismic rack, or 21 inch rack. Adapter flanges available to mount in a 23-inch aluminum rack

•

Requires 5.25 inches (3 EIA rack increments) of open rack space

Description The PDU provides redundant, fuse protected connections to up to six 9500 MPR-A shelves and/or auxiliary equipment. Two isolated battery input connections (A & B). Each battery input is distributed to six alarm indicating fused battery outputs (A+/A& B+/B-) See Figure 457 for an isometric view of the PDU. See Figure 458 for a front panel view of the PDU.

892



Figure 457

Power distribution unit (PDU) isometric view

Figure 458

Power distribution unit (PDU) front panel view

27.3

Indicators, connectors, and control The PDU card has the following indicators, connectors, and controls.

893



See Figure 459 for PDU card front panel indicator and connector locations. The PDU has fuse summary alarm indicator. See Table 93 for PDU connector details. Figure 459

PDU indicator and connector locations

Table 93

PDU connector details

CONNECTOR

DESIGNATOR

TYPE

FUNCTION

A+

TB1

A Battery positive battery input

A-

TB2

B+

TB3

One-Hole, 0.250 inch, compression lug

B-

TB4

B Battery negative battery input

FA1+

E1

Fused A1 battery positive output

FA2+

E2


FA3+

E3


FA4+

E4


FA5+

E5


FA6+

E6


FA1-

E7

Fused A1 battery negative output

FA2-

E8


FA3-

E9


FA4-

E10


894

A Battery negative battery input B Battery positive battery input


Table 93


PDU connector details (Continued)

CONNECTOR

DESIGNATOR

TYPE

FUNCTION

FA5-

E11


FA6-

E12


FB1+

E13

Fused B1 battery positive output

FB2+

E14


FB3+

E15


FB4+

E16


FB5+

E17


FB6+

E18


FB1-

E19

Fused B1 battery negative output

FB2-

E20


FB3-

E21


FB4-

E22


FB5-

E23


FB6-

E24


GND A1

E25

Ground A1 output

GND A2

E26

Ground A2 output

GND A3

E27

Ground A3 output

GND A4

E28

Ground A4 output

GND A5

E29

Ground A5 output

GND A6

E30

Ground A6 output

GND B1

E36

Ground B1 output

GND B2

E35

Ground B2 output

GND B3

E34

Ground B3 output

GND B4

E33

Ground B4 output

GND B5

E32

Ground B5 output

GND B6

E31

Ground B6 output

895


Table 93


PDU connector details (Continued)

CONNECTOR

DESIGNATOR

TYPE

FUNCTION

A- STR

E37

A ground strap for positive voltage applications 1

GND STR A

E38

A ground common 2

A+ STR

E39

A ground strap for negative voltage applications 3

B- STR

E40

B ground strap for positive voltage applications

GND STR B

E41

B ground common

B+ STR

E42

B ground strap for negative voltage applications 1. Connector is used to configure PDU for floating rectifier positive battery voltage applications. Connect jumper between A/B- Str and GND STR A/B. 2. A/B ground common strap, connects to the A/B GND connectors on the PDU. 3. Connector is used to configure PDU for floating rectifier negative battery voltage applications. Connect jumper between A/B+ Str and GND STR A/B.

27.4

Functional overview The PDU accepts two ±24 or ±48 V DC inputs and splits them into twelve separate, fuse protected outputs. The input power interface consists of two pairs of ±24 or ±48 V DC (A+/A- B+/-) connections. These connections are rated at 60 amps each. The PDU splits each BATT connection into six separate output connections. Both positive and negative outputs are protected by GMT fuses, 20 amps maximum each. All fuses are accessible and replaceable from the front panel. The electrical inputs are accessible from the top of the PDU. The electrical output connections are accessible from the side and rear panel.

896



28 Microwave packet transport outdoor unit (MPT ODU) unit data sheet This chapter provides information about the MPT-HC, MC, HC-HQAM, XP and XPHQAM. See the following for additional information:

Table 94

•


•

9500 MPR Technical Specifications for Split Mount Applications for technical specifications

•


•


•

GigE and 10GigE SFP unit data sheet for information about SFPs

Nose and nose adapter for MPT ODU

Part number

Description

3CC50172AA

5.8 GHz unlicensed Nose for Non-Integrated Antenna (N-Type)

3DB01460AB

5.8 GHz Unlicensed/6 GHz Nose Adapter with waveguide output for Not Integrated Antenna (WR137)

3CC50172AA

5.8GHz Unlicensed/6GHz Nose Adapter with N output for Not Integrated Antenna (

3DB10135AA

7/8 GHz Nose for Non-Integrated Antenna (WR112)

3CC50125AA

10.5 and 11 GHz Nose for Non-Integrated Antenna (WR90) (Flange UBR100)

3CC50179AAXX

13 GHz Nose for Non-Integrated Antenna (WR75)

3CC50177AA

15 GHz Nose for Non-Integrated Antenna (WR62)

3CC50178AA

18/23 GHz Nose for Non-Integrated Antenna (WR42)

3DB02082AA

28-38 GHz Nose for Non-Integrated Antenna (WR28)

3DB10135AA

7/8 GHz Nose Adapter for Not Integrated Antenna

3CC50125AA

11 GHz Nose Adapter for Not Integrated Antenna

3CC50179AA

13 GHz Nose Adapter for Not Integrated Antenna

897

Release 7.0.0 3DB 19383 ACAA Issue 01 Microwave packet transport outdoor unit (MPT ODU) unit data sheet

Table 94


Nose and nose adapter for MPT ODU (Continued)

Part number

Description

3CC50177AA

15 GHz Nose Adapter (for Not Integrated Antenna)

3CC50178AA

18/23/25 Nose Adapter (for Not Integrated Antenna)

3DB02082AA

28/38 Nose Adapter (for Not Integrated Antenna)

3DB01460AB

5.8 and 6 GHz Nose for Non-Integrated Antenna (WR137)

Table 95

Flextwists for MPT ODU

Part number

Description

1AF02951AB

6 GHz flextwist L = 1m (PDR-UDR)

1AF11977AA

7/8 GHz flextwist WR112 L = 1m (PDR84/UBR84)

3CC05751AC

11 GHz flextwist L = 0.6m

3CC05751AC


3CC05750AC


3CC05749AC

18/23/25 GHz flextwist L = 0.6m

3DB00682AA

28/38 GHz flextwist L = 0.6m

28.1

Description The MPT ODU (Microwave Packet Transport) is a Microwave Equipment capable to transport the Ethernet traffic over an RF radio channel. For the ANSI market, the MPT-HC using the 5.8 GHz channel is referred to as the 9558HC. The MPT ODU includes a waveguide antenna port, a maintenance connector (with captive protection cap) for RSSI access, 1 electrical GE interface. The MPT-HC/XP has 1 GE optical interface. A module can be added to extend the connectivity of the MPT: there is a second 1GE optical interface with 1+1 RPS or 1 XPIC connector. The MPT-HC-HQAM/XP-HQAM has 2GE optical interfaces (1 for data, 1 for 1+1 RPS) and 1 XPIC connector. The MPT-HC/XP has one grounding point. The MPT-XP/XP-HQAM has two grounding points: one for ETSI and one for ANSI.

898



The MPT ODU can be installed on an integrated antenna or on standard poles, wall or pedestal mount, with an appropriate fastening system. The MPT ODU (one or two depending on the configuration 1+0 or 1+1, each one with a solar shield) 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-MC/HC/HC-HQAM/9558HC/HC-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 5.8 to 38 GHz. The MPT-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 8 GHz. The MPT ODU is fixed by means of quick latches. This system allows the transceiver to be changed without altering antenna pointing. Where two MPT ODU 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, where the branching (diplexer) is internal to the MPT ODU cabinet; this type of MPT ODU is identified by one Logistical Item only. The following frequencies are available: −

MPT-MC/HC: 11GHz to 38GHz, L6 / U6 GHz internal diplexer version

−

MPT-HC-HQAM: 13GHz to 38GHz

2. with external diplexer (also called branching filter), where the branching (diplexer) is external to the MPT ODU cabinet; this type of MPT ODU is identified by two Logistical Items. The following frequencies are available: −

MPT-MC/HC: 5.8, L6, U6, 7, 8, 10.5 GHz

−

MPT-HC-HQAM: L6, U6, 7, 6, 11 GHz

−

MPT-XP: L6, U6, 7, 8 GHz

−

MPT-XP-HQAM: L6, U6, 7, 8, 11 GHz

For MPT ODU with internal diplexer, polarization is determined by the rotation of the nose fitted in the antenna port of the MPT ODU in 1+0 configuration and by the position of a polarization rotator fitted within the coupler in 1+1 configuration.

899



For MPT ODU with external diplexer, polarization is determined by the rotation of the MPT ODU mounted to the antenna port in 1+0 configuration and by the position of a polarization rotator fitted within the coupler in 1+1 configuration. MPT ODU is broken down to the following sections:

Figure 460

•

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.

MPT system

The MPT ODU 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. See 9500 MPR Technical Specifications for Split Mount Applications for technical specifications.

28.1.1

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 due to the 100 m 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.

900



4. MPT-MC supports one-step end-to-end transparent clock across a radio hop. The 1588v2 TC must be supported by all equipment involved in the hop and be enabled on both the local and the remote NE. Figure 461

MPT-MC

901


28.1.2


Features and application notes

The following features apply to both the HC and the XP variants unless indicated otherwise: •

MPT-HC-HQAM is designed to replace the MPT-HC

•

MPT-XP-HQAM is designed to replace the MPT-XP

•

Optimal for split mount applications

•

Supports the following deployment models: −

split mount—MSS and MSS-1c

−

stand alone mode—MPR-e

−

integration with the 7705 SAR or 1850 TSS for MPLS converged networks

•

Supports fixed and adaptive modulation

•

Band specific

•

Channel frequency software selectable within tuning range of the MPT-HC/ HC-HQAM/XP/XP-HQAM

•

Support for L1 and L2 Radio LAG ports and ERP ports

•

Protection schema: Note: The MPT-HC-HQAM and MPT-XP-HQAM transceivers have integrated XPIC and RPS functions. XPIC is supported by an RTU. For MPT-HCHQAM/XP-HQAM, virtual RPS is not supported for 40, 50, 56, or 60 MHz channel spacing and RPS cable is mandatory.

902

−

1+0 Not protected, 1+1 HSB, 1+1 SD, and 1+1 FD radio configurations support without optional XPIC or RPS

−

1+0 Not protected, 1+1 HSB, 1+1 SD, 1+1 FD radio configurations support with optional 1+1 RPS (using Virtual 1+1 RPS or Cabled RPS configuration)

−

1+1 HSB, 1+1 SD, 1+1 FD, 2x(1+0) XPIC, 4x(1+0) XPIC, 2x(1+1) HSB XPIC radio configuration support with optional XPIC+RPS or RPS (using Virtual 1+1 RPS or Cabled RPS configuration)

•

Input interface—standard Gigabit Ethernet interface (electrical or optical)

•

Cabling—one or two cables (power and Ethernet) are required to connect to the MPT-HC-HQAM or MPT-XP-HQAM; see section 8.1.

•

MPT-XP-HQAM extended emissions power—depending on modulation, increases system gain from 5 to 9dB over low frequencies: L6 GHz, U6 GHz, 7 GHz, 8 GHz, and 11 GHz


28.1.2.1


•

AES encryption—when enabled, the MPT encrypts all the outgoing traffic transmitted over the radio interface using an AES cipher. Encryption is performed on the full Ethernet frame using a 256 bits key length.

•

1588v2 Transparent Clock — the MPT-HC-HQAM/XP-HQAM supports onestep end-to-end transparent clock across a radio hop. The 1588v2 TC must be supported by all equipment involved in the hop and be enabled on both the local and the remote NE.

•

Automatic Transmit Power Control (ATPC) support

•

Integrated antenna mount

•

Non-Integrated antenna mount is optional

•

Polarization is field configurable, Vertical (standard) or horizontal (optional)

•

MPT-HC-HQAM/XP-HQAMs include built-in lightning surge suppressor

•

No solar shield is required for MPT-HC/HC-HQAM

Compatibility between MPT-HC/XP and MPT-HC-HQAM/XPHQAM

Air compatibility between MPT-HC/XP and MPT-HC-HQAM/XP-HQAM 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/XPHQAM is configured in compatibility mode. Note: in compatibility mode, the ETSI market 7 MHz ACM XPIC modem profiles are not supported.

•

an MPT-HC-HQAM/XP-HQAM and an MPT-HC-HQAM/XP-HQAM only when both ODUs are configured in the same mode; that is, both must be in standard mode or both must be in compatibility mode.

The MPT-HC-HQAM/XP-HQAM can be used as a spare for the MPT-HC/XP in specified configurations. Table 96 summarizes the supported configurations for MPT-HC-HQAM/XP-HQAM in combination with MPT-HC/XP. Figure 462 and Figure 462 show the supported configurations. Table 96

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

Configuration

Comments

Supported

1+0

Air compatibility

Yes

903


Table 96


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

Configuration

Comments

Supported

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

If 4 QAM not used as Minimum Modulation scheme

Yes

LAG L2

—

Yes

(1+0) RING

—

Yes

904


Figure 462


Supported configurations for MPT-HC/XP and MPT-HC/HQAM/XP-HQAM together 1+0, 1+1, and 2+0 XPIC 1+0 MPT-HC/XP

MPT-HQAM

STATION A

STATION B

1+1 HSB/FD/SD MAIN: MPT-HC/XP

MAIN: MPT-HQAM

SPARE: MPT-HC/XP

SPARE: MPT-HQAM

2+0 XPIC all configurations supported

25804

905


Figure 463


Supported configurations for MPT-HC/XP and MPT-HC/HQAM/XP-HQAM together L1 LAG and RING N+0 L1 LAG MPT-HC/XP

if 4QAM not used as Minimum Modulation scheme

MPT-HQAM

MPT-HC/XP

MPT-HQAM

MPT-HC/XP

MPT-HC/XP

MPT-HQAM

MPT-HQAM or MPT-HQAM

N+0 RING 2+0 west direction

2+0 east direction

MPT-HQAM

MPT-HC/XP

MPT-HQAM

MPT-HC/XP if 4QAM not used as Minimum Modulation scheme

MPT-HQAM

25805

906


28.1.2.2


Replacement of an MPT-HC/XP in 1+1 HSB/FD/SD configuration The use of an MPT-HC/XP as a spare for an MPT-HC-HQAM/XP-HQAM is not supported. If an MPT-HC/XP in 1+1 HSB/FD/SD configuration fails, two options are available for replacement; see Figure 464: 1. Replace the failed MPT-HC/XP with a new MPT-HC/XP 2. Replace both MPT-HC/XP units with MPT-HC-HQAM/XP-HQAM units. Option 2 must be performed during a maintenance window. See the 9500 MPR Hardware Installation and Replacement Manual for information about the replacement procedure.

907


Figure 464


Repair of a failed MPT-HC/XP in 1+1 HSB/FD/SD configuration 1+1 HSB/FD/SD MAIN: MPT-HC/XP

MAIN: MPT-HC/XP

SPARE: MPT-HQAM

SPARE: MPT-HC/XP

Repair if an MPT in 1+1 fails MAIN: MPT-HC/XP

X

MAIN: MPT-HC/XP

R

SPARE: MPT-HC/XP

SPARE: MPT-HC/XP

Replace faulty MPT-HC/XP with new MPT-HC/XP OR MAIN: MPT-HQAM

X

MAIN: MPT-HC/XP

R

R NEWSPARE: MPT-HQAM

SPARE: MPT-HC/XP

Replace both MPTs with MPT-HQAM 25803

28.1.2.3

Replacement of an MPT-HC/XP/HC-HQAM/XP-HQAM in other configurations See Table 96.

908


28.2


General characteristics

28.2.1

Common belt section

The Common Belt section is frequency independent. It is the digital section of the MPT-HC/HC-HQAM/XP/XP-HQAM. The main functions are the following: Interfaces the MSS for traffic transport and MSS communication messages in both directions, through one Gigabit Ethernet optical or electrical cable. •

28.2.2

Micro-Processor for −

Indoor - MPT ODU dialogue

−

Inter-MPT ODU dialog in 1+1 configurations

−

HW configuration and monitoring of all MPT ODU parts

−

Dynamic regulation process such as ATPC

•

Transport of the system reference clock (synchronization)

•

Switches the traffic and management to the correct port (processor port, radio port)

•

Performs traffic adaptation if needed

•

Performs Quality of Service and policing on flow to be sent over the radio link.

•

Modulation and demodulation of the resulting modem frame

•

In 1+1 configuration manages the switching, forwarding received modem frame to the second MPT ODU and sending built modem frame to the second MPT ODU.

Power supply interface It is provided by a RJ-45 connector, with the positive to ground. The power supply for the MPT ODU comes from the MSS, power injector box, MPT Power Unit, or MPT Extended Power Unit. The MPT-XP/XP-HQAM must be powered by an MPT Extended Power Unit.

909


28.2.3


Lightning protection The lightning protection is internal to the MPT ODU. This protection applies to:

28.2.4

•

the Ethernet electrical cable

•

the XPIC cable

Tx side Following the flow from user Ethernet port to radio, the section performs:

910

•

Reception of incoming Ethernet frames from the optical or electrical user interface

•

Recovery of the clock coming from the MSS

•

Management of the 1+1 EPS protection layer 2 messages

•

Switch of the management frames from user port to internal processor

•

Generation of MPT ODU to MPT ODU messages needed for radio link (ATPC, ACM,...)

•

Compression of the TDM2Eth frames header (TDM2TDM - MEF8, TDM2ETH - MEF8)

•

Management of the Quality of Service

•

Fragmentation of the Ethernet frames

•

Shaping of the traffic to adapt it to radio bandwidth

•

Radio encryption

•

Tx Modem frame building

•

In 1+1 duplication of the built Tx modem frame and sending to the second MPT ODU through the protection coupling port

•

In 1+1, reception of the Tx modem frame coming from the second MPT ODU

•

In 1+1, switch of the Tx modem frame between the local and the one coming from second MPT ODU depending on the EPS position

•

Tx Radio frame building (FEC, pilots,...)

•

Synchronization of the symbol rate to the MSS recovered clock

•

Modulation in I and Q analogue signals to be sent to the RF section.


28.2.5


Rx side Following the flow from radio to user Ethernet port, the section performs:

28.2.6

•

Reception of the I and Q analogue signals coming from the RF section

•

Demodulation of the Rx radio frame into Rx modem frame

•

In 1+1, Recovery of the symbol clock and duplication to the second MPT ODU

•

In 1+1, duplication of the Rx modem frame and sending to the second MPT ODU through the protection coupling port

•

In 1+1, reception of the Rx modem frame coming from the second MPT ODU

•

In 1+1, hosts the RPS decision machine

•

In 1+1, switch of the Rx modem frame between the local and the one coming from second MPT ODU depending on the traditional RPS position and the modem frames quality

•

Enhanced RPS

•

In 1+1, switch of the recovered clock between the local and the one coming from second MPT ODU depending on the traditional RPS position

•

Radio decryption

•

Deframing of the Rx modem frame

•

Re-assembly of fragmented Ethernet frame

•

Decompression of TDM2Eth frames header

•

Extraction of MPT ODU to MPT ODU messages needed for radio link (ATPC, ACM,...)

•

Management of service channels frames

•

Switch of the management frames from internal processor to user port.

•

Management of the 1+1 EPS protection layer 2 messages

•

Send the recovered clock to the MSS

•

In 1+1 EPS, transmit or not the Ethernet frames to the MSS depending on the EPS position

Main functions 1. TX block: −

IF TX Quadrature modulator

−

IF Tx Synthesizer

911


−

RF Up-Converter

−

Output power management


2. Tx_Rx Common block: −

RF_LO Synthesizer

3. Rx block:

28.2.7

−

LNA

−

RF Down Converter

−

IF amplification and overload management

−

IF down conversion

−

IF filtering

−

Quadrature demodulator

−

Base band filter and AGC loop

MPT ODU 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.

28.2.8

MPT ODU with external diplexer assembly The MPT ODU with an external diplexer assembly has two components: •

transceiver—performs all the radio functions, but does not include the diplexer system. The transceiver can be changed in the field without disconnecting the external diplexer from the pole mounting/antenna.

•

diplexer—provides the interface between the pole mounting/antenna and the transceiver

Figure 465 shows the MPT ODUs that support an external diplexer assembly.

912


Figure 465


MPT ODU with external diplexer assembly

28.2.8.1

External diplexer band-pass filters The diplexer included in the available external diplexer assemblies refers to ITU–R F.385, 386 and RF special customer channeling with Tx/Rx separation specified in the 9500 MPR Frequency Plan for MPT Outdoor Transceivers. Each external diplexer box is a 3-port passive device with two band–pass filters. Figure 466 shows an example of the arrangement between filters on the same external diplexer device.

913


Figure 466


External Diplexer box band-pass detail

Note: f1, f2, f3, and f4 frequencies of the external diplexer filters refer to the extreme channel frequencies and not to the cut–off frequencies of the filters.

28.2.9

Labels affixed on the MPT The labels depicted in Figure 467, Figure 468, and Figure 469 and described in Table 97 are affixed externally to all types of MPT ODU and MPT ODU transceiver boxes;

Figure 467

914

MPT-HC/XP ODU label



Figure 468

MPT-MC label

Figure 469

Label on MPT-HC-HQAM/XP-HQAM transceiver boxes

9500 MPR HQAM -28VDC

-58VDC 1,5A

TX Frequency MHZ

SHIFTER

Tx Sub band

1450014724

420-475

1-1P

MPT HQAM SERIAL No

0,7A

0682

3DB20373BAAA01

123456789

A

B 24488

Table 97

MPT ODU label details

SYMBOL OR WRITING

MEANING

9500 MPR

Equipment Acronym & Nokia Logo

CE

European Community logo

!

Not harmonized frequency logo 2002/96/EC WEEE (Waste Electrical and Electronic Equipment) Logo

-28 V / -58 V

1,5 A / 0,7 A

Power supply range and current range

Logistical Item (shown numbers as examples)

Logistical Item for Customer

A

Logistical Item for Customer, bar code 128

Serial n° (shown numbers as examples)

Factory Serial number

915


Table 97


MPT ODU label details (Continued)

SYMBOL OR WRITING

MEANING

B

Factory Serial number bar code 128

TX Frequency MHz (shown numbers as examples)

Working frequency range

Shifter MHz (shown numbers as examples)

Shifter

TX Sub-band (shown numbers as examples)

TX Sub-band

28.2.10

Weatherproofing

An O-RING in the transceivers ensures that the assemblies are waterproof. Figure 470 shows the MPT-HC-HQAM assembly, with warnings and instructions regarding waterproofing the coupling of the transceiver and diplexer components. Note: This is a conductive O-RING and must be left dry. Do not wet it with silicon grease.

Figure 470

916

MPT-HC-HQAM with an external diplexer



Warning: Waterproof tape is glued on the waveguide of the MPT ODU. It must never be removed.

Warning: This gasket must never be removed.

28.2.10.1

Gaskets included with the MPT There are three types of gaskets that can be included with the MPT ODU: •

Figure 471

Round O-ring gasket, as shown in Figure 471 - no longer sold.

Round MPT ODU O-RING gasket

•

Spine O-ring gasket, as shown in Figure 472 - available in black, red and black or blue and black. There is no difference in behavior between these gaskets.

917


Figure 472


Spine MPT ODU O-RING gasket (red/black or blue/black) - color not contractual

For installation information, see the 9500 MPR Hardware Installation and Replacement Manual. Figure 473 shows an example of the gasket installed on the unit.

918


Figure 473


Example of MPT ODU O-RING gasket installed

28.3

Grounding points for MPT-HC-HQAM and MPT-XP-HQAM Two options are available for grounding, depending on the market: •

ANSI—the front of the MPT-HC-HQAM/XP-HQAM transceiver supports a double-screw grounding position

•

ETSI—the back of the MPT-HC-HQAM/XP-HQAM transceiver supports a single grounding screw. The grounding screw is positioned on the back by default.

919



Warning: One of the front grounding positions may be used, if required. Remove the grounding screw from the back of the transceiver. Install the screw in one of the grounding positions on the front of the transceiver. Do not attempt to ground the system using the front and back positions at the same time.

28.4

Operative information, views, and access points The external interfaces for embedded and external diplexer versions of the MPTs and their corresponding connectors are described in this section. Table 98 lists where to find more information about each MPT.

Table 98

MPT ODUs

MPT-ODU type

See section

MPT-MC/HC/XP/9558HC with external diplexer

28.4.1

MPT-HC with embedded diplexer

28.4.2

MPT-HC-HQAM/XP-HQAM with external diplexer

28.4.4

MPT-HC-HQAM with internal diplexer

28.4.5

28.4.1

MPT-MC/HC/MPT-XP/9558HC with external diplexer Figure 474 shows the views and access points of the MPT-MC/HC/9558HC with external diplexer. Table 99 describes the locking hooks on the back of the MPT-MC/ HC/XP/9558HC with external diplexer. Table 100 describes the connectors on the front and back of the MPT-MC/HC/XP/9558HC.

920



Figure 474

Views of MPT-MC/HC/9558HC with external diplexer

Table 99

Back view locking hooks

REFERENCE NUMBER

INTERFACE

(A)

Four locking hooks to fix/unfix external diplexer assembly to transceiver

(B)

Four locking hooks to fix/unfix external diplexer assembly to antenna or coupler

Note: If the SFP does not have the bail latch, to extract it (if required) use the suitable tool.

921


Table 100


MPT ODU external interfaces

REFERENC E NUMBER

INTERFACE

CONNECTOR

ADDITIONAL INFORMATION

(1)

RF interface for connection to antenna or coupler WARNING: A waterproofing tape is glued on the waveguide of the MPT ODU. It must never be removed.

waveguide

Table 101

(2)

Connector for power supply cable or for PFoE (Power Supply + Ethernet Traffic) cable

RJ45 + R2CT

—

(3)

Optical Ethernet connection

LC + Q-XCO

—

(4)

RPS Connector (connection to a second MPT ODU in 1+1

LC + Q-XCO

—

(5)

XPIC connector

Round proprietary

—

Table 101

MPT ODU: RF interface waveguides

FREQUENCY GHz

5.8

6

7

8

11

15

18-23

38

Waveguide Type

WR137

WR137

WR112

WR112

WR75

WR62

WR42

WR28

28.4.2

MPT-MC/HC with embedded diplexer Figure 475 shows the views and access points of the MPT-MC/HC with embedded diplexer. Table 102 describes the locking hooks on the back of the MPT-MC/HC with external diplexer. The connectors on the front and back of the MPT-MC/HC with embedded diplexer are described in Table 100.

922



Figure 475

Views of MPT-HC with embedded diplexer

Table 102

Back view locking hooks

REFERENCE NUMBER

INTERFACE

(A)

Locking hooks (4) to fix/unfix MPT-HC assembly to antenna or coupler

(1)

RF interface for connection to antenna or coupler WARNING: A waterproofing tape is glued on the waveguide of the MPT-HC. It must never be removed.

923


28.4.3


MPT-XP with external diplexer Figure 476 shows the views and access points of the MPT-XP with external diplexer. The locking hooks on the back and the connectors on the front and back of the MPTXP are the same as the MPT-HC/9558HC and are described in Table 99 and Table 100.

Figure 476

924

Views of MPT-XP with external diplexer


28.4.4


MPT-HC-HQAM/XP-HQAM with external diplexer

Figure 477 shows the MPT-HC-HQAM/XP-HQAM with external diplexer views and access points. Figure 478 lists the locking hooks on the back of the MPT-HC-HQAM/ XP-HQAM with external diplexer and Table 105 describes the connectors on the front and back of all MPT-HC-HQAM/XP-HQAM versions. Figure 477

Low-frequency MPT-HC-HQAM/XP-HQAM with external diplexer

Table 103

Legend for low-frequency MPT-HC-HQAM/XP-HQAM back view locking hooks

REFERENCE

INTERFACE

A

4 locking hooks to fix/unfix external diplexer assembly to the transceiver

B

4 locking hooks to fix/unfix external diplexer assembly to the antenna or coupler

Note: If the SFP does not have the bail latch, to extract it (if required) use the suitable tool.

925


Table 104


Legend for MPT-HC-HQAM/XP-HQAM front and back view connectors

RE F

CONNECTOR

TYPE

FUNCTION

1

Antenna Port

Waveguide Interface

RF interface for connection to antenna or coupler. See Table 101 for more information about RF interface waveguide types.

2

RSSI

LEMO

RSSI Monitor Port.

3

SFP

LC + Q-XCO

Optical GigE Data Interface connection to MSS

4

Data & Power In

RJ45 + R2CT

Electrical Data & DC Power connection to MSS or external power source

5

RPS

LC + Q-XCO

Optical GigE RPS Interface connection to second MPT-HC/HC-HQAM

6

XPIC

Round Proprietary

Connection to second MPT-HC/HC-HQAM in XPIC configuration.

7

Ground points

Market specific

Two options are available for grounding, depending on the market:

28.4.5

•

ANSI—the front of the MPT-HC-HQAM/XPHQAM transceiver supports a double-screw grounding connector

•

ETSI—the back of the MPT-HC-HQAM/XPHQAM transceivers support a single-screw grounding connector

MPT-HC-HQAM with internal diplexer Figure 478 shows the MPT-HC-HQAM with internal diplexer views and access points. Table 105 lists the connectors on the back of the MPT-HC-HQAM with internal diplexer. The connectors on the front of the high-frequency MPT-HC-HQAM are the same as the low-frequency version and are described in Table 105.

926



Figure 478

High-frequency MPT-HC-HQAM with internal diplexer

Table 105

Legend for high-frequency MPT-HC-HQAM with embedded diplexer (13-38 GHz)

REFERENCE

INTERFACE

A

Locking hooks (4) to fix/unfix MPT-HC/XP HQAM assembly to antenna or coupler

1-7

See Table 99.

927


928




29 MPT-HL microwave packet transport-long haul shelf unit data sheet This chapter provides information about the MPT-HL transceiver. See Table 106 for MPT-HL shelf part numbers. See Table 107 for air filters. See the following for additional information:

Table 106

•

9500 MPR Technical Specifications for Full Indoor Applications for technical specifications about full-indoor transceivers

•


•

The Equipping Options Drawing in the 9500 MPR-A Engineering Support Documentation for filter, waveguide, kit, and stacking and diplexer application information.

•


•


•

MPT-HL transceiver (ANSI market only) unit data sheet for information about the MPT-HL transceiver

•

MPT-HLC transceiver (ANSI market only) unit data sheet for information about the MPT-HLC transceiver

MPT-HL microwave packet transport-long haul shelf and related kits


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3EM22618AB 3EM22618AC

MPT-HL Microwave Packet transport-Long Haul Shelf

N/A

N/A

N/A

Active

MPT-HL/HLC shelf kits The MPT-HL/HLC shelf kits contain; one MPT-HL/HLC shelf, MPT-HL Transceiver power cables, Transceiver blank cover, and miscellaneous rack hardware. MPT-HL/HLC shelf kits are unpopulated. 3EM24238AA

Single Transceiver shelf kit

N/A

N/A

N/A

Active

3EM23238AB

Dual Transceiver shelf kit

N/A

N/A

N/A

Active

929

Release 7.0.0 3DB 19383 ACAA Issue 01 MPT-HL microwave packet transport-long haul shelf unit data sheet

Table 106


MPT-HL microwave packet transport-long haul shelf and related kits (Continued)


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3EM24447AA, 3EM2447AB

MPT-HL Transmit Monitor Port Kit Provides transmit monitor port for 6 GHz and 11 GHz PN: 3EM24447AA is 6 GHz Transmit Monitor Port PN: 3EM24447AB is 11 GHz Transmit Monitor Port

N/A

N/A

N/A

Active

Table 107

Air filters

UNIT

DESCRIPTION

3EM24040AA

MPT-HL Transceiver Air Filter Replacement MPT-HL Transceiver air filter.

3DB80367AA

MPT-HLC Transceiver Air Filter Replacement MPT-HLC Transceiver air filter.

29.1

930


The Microwave Packet Transport-Long Haul (MPT-HL) shelf provides an all indoor solution when used in conjunction with the 9500 MPR ANSI MSS-1/4/ 8 shelf.

•

The MPT-HL shelf provides support for two high-capacity, long-haul RF transmission MPT Transceivers.

•

All cards are accessed from the front side of the shelf.

•


•



29.2


Description The MPT-HL self consists of a module cage and backplane which provides two slots dedicated for two MPT-HL or MPT-HLC Transceiver cards. See Figure 479 for an example of the MPT-HL/HLC shelf. The MPT-HL/HLC shelf is 19 inches wide (17.25 inches wide without mounting flanges), 4.25 inches high (2.5 EIA rack increments), and 10.5 inches deep without diplexer and waveguide mounting brackets. Adapter plates are available to mount the MPT-HL/HLC shelf in 23 inch aluminum racks. See Figure 480 through Figure 483 for outline and shelf dimensions of the MPT-HL shelf in various configurations.

Figure 479

Microwave packet transport-long haul (MPT-HL/HLC) shelf

931


Figure 480

MPT-HL/HLC shelf dimensions

Figure 481

MPT-HL/HLC shelf w/diplexer dimensions - top view

932




Figure 482

MPT-HL/HLC shelf w/one waveguide bracket dimensions - top view

Figure 483

MPT-HL/HLC shelf w/two waveguide brackets dimensions - top view

933


29.3


Equipment complement The MPT-HL/HLC shelf houses one or two MPT Transceivers. The MPT Transceivers can be configured either in 1+1 protection, one 1+0 unprotected, or two 1+0 unprotected radio channels.

934



30 MPT-HL transceiver (ANSI market only) unit data sheet This chapter provides information about the MPT-HL transceiver. See Table 108 for MPT-HL transceiver part numbers. See the following for additional information:

Table 108

•

9500 MPR-A MPT-HL Engineering Specifications for technical specifications

•


•


•


•

MPT-HL microwave packet transport-long haul shelf unit data sheet for information about the MPT-HL shelf

•


•

MPT-HLS standard transceiver (ETSI market only) unit data sheet for information about the MPT-HLS transceiver

MPT-HL transceiver


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3EM22617AA

MPT-HL Transceiver L6, 5725-6425 MHz

CRTUAAXFAA

171610

070VLL

Active

3EM22617AB

MPT-HL Transceiver U6, 6425-6930 MHz

CRTUAAYFAA

171611

070VLM

Active

3EM22617AC

MPT-HL Transceiver L6, 5925-6425 MHz, HP

CRTUABLFAA

173789

070XRS

Active

3EM22617AD

MPT-HL Transceiver U6, 6425-6930 MHz, HP

CRTUABMFAA

173790

070XRS

Active

3EM22617AE

MPT-HL Transceiver UU6, 6875-7125 MHz, HP

N/A

N/A

N/A

Active

3EM24627AA

MPT-HL Transceiver 7, 7125-7775 MHz

N/A

N/A

N/A

Active

935

Release 7.0.0 3DB 19383 ACAA Issue 01 MPT-HL transceiver (ANSI market only) unit data sheet

Table 108


MPT-HL transceiver (Continued)


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3EM24627AB


N/A

N/A

N/A

Active

3EM23888AA

MPT-HL Transceiver 10.5, 10400-10700 MHz

CRTUABPCAA

174725

070YGX

Active

3EM23888AB


CRTUABRCAA

174727

070YGY

Active

3EM23888AC


CRTUABSCAA

174728

070YGZ

Active

3EM22518AA

MPT-HL Fan Filter Dust filter for the MPT-HL Transceiver

N/A

N/A

N/A

Active

936


30.1



High-capacity, long-haul RF transmission shelf

•

Supported on P8ETH, EASv2, Core-E, or CorEvo cards and MSS-1 SFP ports in 1+0 and 1+1 configurations, L1 and L2 Radio LAG ports

•

Support for the following RF configurations: −

Non-Standby

−

Hot Standby

−

Hot Standby with Space Diversity

−

Frequency Diversity

−

N+0 LAG

−

N+N LAG

•

Support for the following channel plans: 5.8 GHz Unlicensed, Lower 6 GHz, Upper 6 GHz, Upper Upper 6 GHz, 7 GHz, 8 Ghz, 10.5 GHz, and 11 GHz

•

Support for the following fixed radio profiles:

•

−

Supported fixed channel bandwidths: 5, 10, 30, and 40 MHz

−

Supported fixed modulations: 32 QAM, 128 QAM, and 256 QAM

Support for the following adaptive radio profiles: −

Supported adaptive channel bandwidths: 25 MHz (UU6 only), 30 MHz

−

Supported adaptive modulations: 4/16/64/128/256 QAM

•


•

Gigabit Ethernet connection to 9500 MPR MSS indoor unit using standard SFPs

For technical information, see 9500 MPR Technical Specifications for Full Indoor Applications.

30.2

Description The MPT-HL Transceiver is a microprocessor controlled RF transceiver that interfaces between the MSS shelf and the antenna. The MPT-HL Transceiver microprocessor manages transmit and receive frequencies, transmit power, alarming, and performance monitoring. There are no MPT-HL Transceiver options. The MPT-HL Transceiver resides in the MPT-HL shelf.

937


30.3


Indicators, connectors, and control The MPT-HL Transceiver has the following indicators, connectors, and controls. See Figure 484 for MPT-HL Transceiver front panel indicator and connector locations. See Table 109 for MPT-HL Transceiver indicators details. See Table 110 for MPT-HL Transceiver connector details. See Table 111 for MPT-HL Transceiver control details.

Figure 484

938

MPT-HL transceiver


Table 109


MPT-HL transceiver front panel indicator details

INDICATOR

STATUS

DEFINITION

Status (S)

Off

Card not equipped, not provisioned, or not powered

Green Blinking

Configuration 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

In Protect, Properly Provisioned. EPS and RPS currently in Standby.

Green/Red Blinking

Card Properly Equipped and Provisioned. Either TX or RX equipment or signal Fault. EPS or RPS currently In-Service/Active. Traffic is probable affected.

Yellow/Red Blinking

Card Properly Equipped and Provisioned, TX or RX signal Fault, EPS and RPS currently in Standby. Traffic maybe affected.

Red

Card Fail

Red Blinking

MAP Communication Time-out: Communication between the MPT-HL Transceiver and the P8ETH cards is lost.

Off

MPT-HL Transceiver is not emitting power for reasons other than “forced squelch”. Transmit Protection Switch (TPS) is currently in standby state. Software booting or FPGA download in progress

Green Blinking

MPT-HL Transceiver is not emitting power due to a forced squelch condition. TX mute active PA switch is positioned Off

Green

MPT-HL Transceiver is emitting power as expected according to the known configuration.

Off

Link Down

On

Link Up

Off

No Tx/Rx activity

Blinking

Tx/Rx activity

Power Emission

Link (L)

Activity (A)

939


Table 110


MPT-HL transceiver front panel connector details

CONNECTOR

TYPE

FUNCTION

Battery Power

D-SUB

MPT-HL Transceiver Power Input

SFP Port

SFP

Communication link with the P8ETH card

Craft terminal/CT

RJ45

Not supported in this release.

Table 111

MPT-HL transceiver front panel control details

CONTROL

POSITION

FUNCTION

PA

0

Transmit OFF (TxMute)

1

Transmit ON

30.4

Functional overview In the TX direction, the MPT-HL Transceiver converts Ethernet packet data from the MSS into a modulated IF output signal. The modulated IF signal is converted into a RF signal which is amplified by the Power Amplifier (PA) and routed through a bandpass filter to the antenna. In the RX direction, the MPT-HL Transceiver amplifies the incoming RF signal and converts the RF signal into a first IF signal. The first IF signal is then converted to a second IF signal. The second IF signal is filtered, demodulated, and converted into Ethernet packet data. The Ethernet packet data is then sent to the MSS.

940



31 MPT-HLC transceiver (ANSI market only) unit data sheet This chapter provides information about the MPT-HLC transceiver. See Table 112 for MPT-HLC transceiver part numbers. See the following for additional information:

Table 112

•

9500 MPR Technical Specifications for Full Indoor Applications for technical specifications

•


•


•


•

MPT-HL microwave packet transport-long haul shelf unit data sheet for information about the MPT-HL/HLC shelf

•


•

MPT-HLS standard transceiver (ETSI market only) unit data sheet for information about the MPT-HLS transceiver

MPT-HLC transceiver


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB76123AA

MPT-HLC Transceiver U4, WO/Combiner 4400 5000 MHz

N/A

N/A

N/A

Active

3DB76123BA

MPT-HLC Transceiver U4, W/Combiner 4400 - 5000 MHz

N/A

N/A

N/A

Active

3DB19060AA

MPT-HLC Transceiver L6, WO/Combiner 5725-6425 MHz

CRM6X10ERB

N/A

N/A

Active

3DB19060BA

MPT-HLC Transceiver L6, W/Combiner 5725-6425 MHz

CRM6110ERB

N/A

N/A

Active

941

Release 7.0.0 3DB 19383 ACAA Issue 01 MPT-HLC transceiver (ANSI market only) unit data sheet

Table 112


MPT-HLC transceiver (Continued)


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB19060CA

MPT-HLC Transceiver L6, HP, WO/Combiner 57256425 MHz

CRM6610ERB

N/A

N/A

Active

3DB19060DA

MPT-HLC Transceiver L6, HP, W/Combiner 57256425 MHz

CRM6710ERB

N/A

N/A

Active

3DB76047AA

MPT-HLC Transceiver U6, WO/Combiner 6425-7125 MHz

CRM6Y10ERB

N/A

N/A

Active

3DB76047BA

MPT-HLC Transceiver U6, W/Combiner 6425-7125 MHz

CRM6210ERB

N/A

N/A

Active

3DB76047CA

MPT-HLC Transceiver U6, HP, WO/Combiner 64257125 MHz

CRM8D00ARA

N/A

N/A

Active

3DB76047DA

MPT-HLC Transceiver U6, HP, W/Combiner 64257125 MHz

CRM8E00ARA

N/A

N/A

Active

3DB76048AA

MPT-HLC Transceiver 7, WO/Combiner 7125-7775 MHz

N/A

N/A

N/A

Active

3DB76048BA

MPT-HLC Transceiver 7, W/Combiner 7125-7775 MHz

N/A

N/A

N/A

Active

3DB76048CA

MPT-HLC Transceiver 7, HP, WO/Combiner 71257775 MHz

N/A

N/A

N/A

Active

3DB76048DA

MPT-HLC Transceiver 7, HP, W/Combiner 71257775 MHz

N/A

N/A

N/A

Active

3DB76049AA

MPT-HLC Transceiver 8, WO/Combiner 7725-8500 MHz

N/A

N/A

N/A

Active

942


Table 112


MPT-HLC transceiver (Continued)


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB76049BA


N/A

N/A

N/A

Active

3DB76049CA

MPT-HLC Transceiver 8, HP, WO/Combiner 77258500 MHz

N/A

N/A

N/A

Active

3DB76049DA

MPT-HLC Transceiver 8, HP, W/Combiner 77258500 MHz

N/A

N/A

N/A

Active

3DB76078AA

MPT-HLC Transceiver 10.5, WO/Combiner 10400-10700 MHz

CRM8H00ARA

N/A

N/A

Active

3DB76078BA

MPT-HLC Transceiver 10.5, W/Combiner 1040010700 MHz

CRM8J00ARA

N/A

N/A

Active

3DB76050AA

MPT-HLC Transceiver 11, WO/Combiner 1070011700 MHz

CRM8F00ARA

N/A

N/A

Active

3DB76050BA


CRM8G00ARA

N/A

N/A

Active

3DB76050CA

MPT-HLC Transceiver 11, HP, WO/Combiner 1070011700 MHz, TX LO

CRM6810ERB

N/A

N/A

Active

3DB76050DA

MPT-HLC Transceiver 11, HP, W/Combiner 1070011700 MHz, TX LO

CRM7A00ARB

N/A

N/A

Active

3DB76050EA

MPT-HLC Transceiver 11, HP, WO/Combiner, TX HIGH

CRM7B00ARB

N/A

N/A

Active

3DB76050FA

MPT-HLC Transceiver 11, HP, W/Combiner, TX HIGH

CRM7C00ARB

N/A

N/A

Active

943


31.1



High-capacity, long-haul RF transmission shelf

•

Supported on EASv2, Core-E, CorEvo, and MSS-1 SFP ports in 1+0 and 1+1 configurations, L1 and L2 Radio LAG ports

•

Support for the following RF configurations when connected to Core-E, CorEvo, EASv2, and MSS-1 SFP ports: −

Non-Standby

−

Non-Standby with Space Diversity

−

Hot Standby

−

Hot Standby with Space Diversity

−

Frequency Diversity

−

N+0 LAG

−

N+0 LAG with Space Diversity

−

2x(1+0) single shelf repeater with and without Space Diversity

−

Up to 8+0 LAG, with and without Space Diversity

−

XPIC

•

Supports 5.8 Unlicensed, U4, L6, U6, 7, 8, 10.5, and 11 GHz frequency bands.

•

Supports 4/16/32/64/128/256/512/1024 QAM levels, either fixed or adaptive.

•

Supports Bandwidths: 5, 10, 25, 30, 40, and 60 MHz, depending on the frequency band and applicable regulations.

•


•

Gigabit Ethernet connection to 9500 MPR MSS unit using standard SFPs

•

Combiner variants provide an optional second receiver (SD)

For modem profile information, see 9500 MPR Technical Specifications for Full Indoor Applications.

944


31.2


Description The MPT-HLC Transceiver card is a microprocessor controlled RF transceiver that interfaces the Core-E card, CorEvo card, EASv2 card, or MSS-1 unit MPT-HLC port with the antenna. The MPT-HLC Transceiver microprocessor manages transmit and receive frequencies, transmit power, alarming, and performance monitoring. The MPT-HLC Transceiver resides in the MPT-HL/HLC shelf.

31.3

Indicators, connectors, and control The MPT-HLC Transceiver card has the following indicators, connectors, and controls. See Figure 485 for MPT-HLC Transceiver card front panel indicator and connector locations. See Table 113 for MPT-HLC Transceiver card indicators details. See Table 114 for MPT-HLC Transceiver card connector details. See Table 115 for MPT-HLC Transceiver card control details.

Figure 485

MPT-HLC transceiver

945


Table 113


MPT-HLC 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 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 in Standby.

Yellow/Red Blinking

Card Properly Equipped and Provisioned, RX signal Fault, EPS currently in Standby. Traffic may be affected.

Red

•

HW Card Fail

•

Modem Tx sync alarm

•

PA switch active

•

Combiner board card fail (only in combiner mode)

•

RF switch fail (only for the spare MPT-HLC in HSB configuration)

In a PA critical temperature condition, the LED remains green.

Power Emission

946

Red Blinking

MAP Communication Time-out: Communication between the MPT-HLC Transceiver and the EAS cards is lost. This occurs in split-mount configuration only.

Off

MPT-HLC Transceiver is not emitting power, according to the known configuration; for example, Hot Standby.

Green

MPT-HLC Transceiver is emitting power as expected according to the known configuration.

Yellow

MPT-HLC Transceiver is not emitting power due to an operator command, including manual PA PSU switch or Tx mute.

Red

MPT-HLC Transceiver is abnormally emitting power, in contrast with the known configuration (for example, when Tx power alarm is raised during normal operative mode)


Table 113


MPT-HLC transceiver front panel indicator details (Continued)

INDICATOR

STATUS

DEFINITION

Off

Link Down

On

Link Up

Off

No Tx/Rx activity

Blinking

Tx/Rx activity

SFP interface LEDs Link (L)

Activity (A)

Table 114

MPT-HLC transceiver front panel connector details

CONNECTOR

TYPE

FUNCTION

Battery Power

D-SUB

MPT-HLC Transceiver Power Input

Optical SFP Ports (2)

SFP

Electrical ports (4)

Table 115

RJ45

•

GE (Communication link with the MSS)

•

GE-RPS (Future)

•

RSL (analog Rx power main, analog Rx power space diversity used for antenna alignment)

•

XPIC (Horizontal-Vertical interconnect)

•

Upper Right (Future)

•

Lower Right (Future)

MPT-HLC transceiver front panel control details

CONTROL

POSITION

FUNCTION

PA

0

Transmit OFF (TxMute)

1

Transmit ON

31.3.1

RSSI monitoring point

The RSSI is available on the RSL RJ-45 connector and is used to manually align the antenna in the field. Higher RSSI voltage indicates better antenna alignment. See the Antenna Alignment chapter in the 9500 MPR Hardware Installation and Replacement Manual for pinout information and typical voltage levels.

947


31.4


Functional overview In the TX direction, the MPT-HLC Transceiver converts Ethernet packet data from the EAS (Ethernet Access Switch - P8ETH or EASv2) card MPT-HL port or Core-E or CorEvo Ethernet port into a modulated IF output signal. The modulated IF signal is converted into a RF signal which is amplified by the Power Amplifier (PA) and routed through a band-pass filter to the antenna. In the RX direction, the MPT-HLC Transceiver card amplifies the incoming RF signal. Converts the RF signal into a first IF signal. The first IF signal is then converted to a second IF signal. The second IF signal is filtered, demodulated, and converted into Ethernet packet data. The Ethernet packet data is then sent to the EAS card MPT-HL port. For each frequency two different versions of the MPT-HLC 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.

948



32 MPT-HLS standard transceiver (ETSI market only) unit data sheet This chapter provides information about the MPT-HLS standard transceiver. See Table 116 for MPT-HLS standard transceiver part numbers. See the following for additional information:

Table 116

•


•


•


•


•

MPT-HLS compact transceiver (ETSI market only) unit data sheet for information about the MPT-HLS compact transceiver

•


•


MPT-HLS standard transceiver part numbers

Name

Code

Remarks

MPT HLS 4L

3DB80803AA

MPT-HL 4L RT STD slim

MPT HLS 4L SD

3DB80803BA

MPT-HL 4L RT SD slim

MPT HLS 4U

3DB80805AA

MPT-HL 4U RT STD slim

MPT HLS 4U SD

3DB80805BA

MPT-HL 4U RT SD slim

MPT HLS 6L

3DB80493AA

MPT-HL 6L RT STD slim

MPT HLS 6U

3DB80511AA

MPT-HL 6U RT STD slim

MPT HLS 6L SD

3DB80493BA

MPT-HL 6L RT SD slim

MPT HLS 6U SD

3DB80511BA

MPT-HL 6U RT SD slim

MPT-HLS 7Ghz

3DB80519AA

MPT-HL 7Ghz RT STD slim

MPT-HLS 7Ghz SD

3DB80519BA

MPT-HL 7Ghz RT SD slim

949

Release 7.0.0 3DB 19383 ACAA Issue 01 MPT-HLS standard transceiver (ETSI market only) unit data sheet

Table 116


MPT-HLS standard transceiver part numbers (Continued)

Name

Code

Remarks

MPT-HLS 8Ghz

3DB80520AA

MPT-HL 8Ghz RT STD slim

MPT-HLS 8Ghz SD

3DB80520BA

MPT-HL 8Ghz RT SD slim

MPT-HLS 10 GHz

3DB80580AA

MPT-HL 10 GHz RT STD slim

MPT-HLS 10 GHz SD

3DB80580BA

MPT-HL 10 GHz RT SD slim

MPT-HLS 11 GHz

3DB80581AB

MPT-HL 11 GHz RT STD slim

MPT-HLS 11 GHz SD

3DB80581BB

MPT-HL 11 GHz RT SD slim

MPT-HLS FAN parts Kit Support 2 Fans 1x4 MPT HLS

3DB80470AA

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

3DB80477AB

FAN4

Fan Dummy Plate

3DB80464AA

—

TRU

3CC50156AAXX 3CC50276AAXX

To be installed on the top of the ETSI rack

21" bracket kit for distribution panel

3CC50042AAXX

—

Breaker 20A

1AB121750001

—

Breaker 10A

1AB058580016

—

Breaker 2A

1AB284990001

—

Breaker 6A

1AB058580014

—

Breaker 16A

1AB058580013

—

Breaker 32A

1AB121750002

—

3DB80856AA

—

3DB80890AA

—

3DB80857AA

—

MPT-HLS TRU part numbers

MPT-HLS branching items Kit antenna circulator 4L GHz Kit antenna circulator 4L GHz pol. Kit antenna circulator 4U GHz

950

4


Table 116



Name

Code

Remarks

4

3DB80891AA

—

1st channel BRN 4L-4UGHz TRX left high

3DB80839AA

—

1st channel BRN 4L-4UGHz TRX right high

3DB80840AA

—

1st channel BRN 4L-4UGHz RXD left high

3DB80841AA

—

1st channel BRN 4L-4UGHz RXD right high

3DB80842AA

—

1st CH BRN 6/7/8 GHz TRX Left High

3DB80409AB

—

1st CH BRN 6/7/8 GHz TRX Right High

3DB80410AB

—

1st CH BRN 6/7/8 GHz RXD Left High

3DB80411AB

—

1st CH BRN 6/7/8 GHz RXD Right High

3DB80412AB

—

1st channel BRN 11GHz TRX left high

3DB80613AA

—

1st channel BRN 11GHz TRX right high

3DB80614AA

—

1st channel BRN 11GHz RXD left high

3DB80615AA

—

1st channel BRN 11GHz RXD right high

3DB80616AA

—

WR137 Power Absorber 5.6-7.1 GHz

3DB01185AA

—

WR137 Power Absorber 7.1-8.5 GHz

3DB01186AA

—

Power absorber 11-13 GHz WR75

3DB02189AA

—

Branching Front Plate Kit

3DB80459AA

—

Kit antenna circulator 4U GHz pol.

951


Table 116



Name

Code

Remarks

Closing kit for channel circulation 6/7/8 GHz

3DB80438AA

—

Closing kit for channel circulation 11GHz

3DB03055AA

—

Extension TRX 4L-4UGHz 1 channel

3DB80843AA

—

Extension RXD 4L-4UGHz 1 channel

3DB80844AA

—

EXT TRX 6/7/8 GHz one channel

3DB80413AB

—

EXT RXD 6/7/8 GHz one channel

3DB80414AB

—

Extension RXD 6/7/8GHz 1 channel 4 pos

3DB80422AA

—

Extension TRX 6/7/8GHz 1 channel 4 pos

3DB80421AA

—

Extension TRX 11GHz 1 channel

3DB80617AA

—

Extension RXD 11GHz 1 channel

3DB80618AA

—

Kit 5th channel 6/7/8 GHz TRX High

3DB80417AB

—

Kit 5th channel 6/7/8 GHz RXD High

3DB80419AB

—

Flanged stub 4L GHz

3DB80878AA

—

Flanged stub 4U GHz

3CY04705AA

—

Flanged stub UDR70 5.9-7.7 GHz

3DB03022AA

—

Flanged stub UDR100 11 GHz

3DB03074AA

—


3DB03023AA

—

Flanged stub 6/7/8 GHz L=47 mm

3DB02412AA

—


3DB02413AA

—


3DB24239AA

—

952


Table 116



Name

Code

Remarks


3DB24240AA

—


3DB02414AA

—


3DB02415AA

—


3DB02416AA

—


3DB02417AA

—


3DB02418AA

—

Flanged stub 11 GHz L=39 mm

3DB03890AA

—


3DB03891AA

—


3DB03892AA

—


3DB03893AA

—

Flanged stub 11GHz L=195 mm

3DB03894AA

—


3DB03895AA

—


3DB03896AA

—


3DB24241AA

—


3DB24242AA

—

1st channel BRN 4L-4UGHz TRX right low

3DB80824AA

—

1st channel BRN 4L-4UGHz RXD right low

3DB80825AA

—

1st channel BRN 4L-4UGHz TRX 4 position

3DB80884AA

—

1st channel BRN 4L-4UGHz RXD 4 position

3DB80885AA

—

953


Table 116



Name

Code

Remarks

1st CH BRN 6/7/8 GHz TRX Right Low

3DB80415AB

—

1st CH BRN 6/7/8 GHz RXD Right Low

3DB80416AB

—

1st CH BRN 6/7/8 GHz TRX 4 Position

3DB80418AB

—

1st CH BRN 6/7/8 GHz RXD 4 Position

3DB80420AB

—

Kit 5th CH 6/7/8 GHz TRX 4 Position

3DB80423AB

—

Kit 5th CH 6/7/8 GHz RXD 4 Position

3DB80424AB

—

1st channel BRN 11GHz TRX right low

3DB80632AA

—

1st channel BRN 11GHz RXD right low

3DB80634AA

—

1st channel BRN 11GHz TRX 4 position

3DB80636AA

—

1st channel BRN 11GHz RXD 4 position

3DB80637AA

—

Coax Load Male 4L-4U GHz

1AB006420058

—

Coax Load Female 4L-4U GHz

1AB006420059

—

Kit fixing waveguide TRX MPT HLS

3DB80448AA

—

Kit fixing waveguide RXD MPT HLS

3DB80456AA

—

Flanged stub UDR70 5,9-7,1 GHz

3DB03022AA

—

Flanged stub UDR84 7,1-8,5 GHz

3DB03023AA

—

Flanged stub UDR120

3DB03073AA

—

Flanged stub UDR100

3DB03074AA

—

954


Table 116



Name

Code

Remarks

3DB80389AAAA

S-shaped waveguide for Rx branching in heteropolar systems with one sub-rack only

3DB80388AAAA

S-shaped waveguide for: •

Rx Div. Branching in heteropolar systems with one subrack only

•

Rx and Rx Div. Branching in heteropolar systems with two sub-racks (four polarizations)

MPT-HLS HSB kits Kit TRX HSB Left 5.725-6.425 GHz

3DB80601AA

—

Kit RXD HSB Left 5.725-6.425 GHz

3DB80603AA

—

Kit TRX HSB Right 5.725-6.425 GHz

3DB80593AA

—

Kit RXD HSB Right 5.725-6.425 GHz

3DB80595AA

—

Kit TRX HSB Left 6.425-7.125 GHz

3DB80602AA

—


3DB80604AA

—


3DB80594AA

—


3DB80596AA

—

Kit TRX HSB Left 7.110-8.500 GHz

3DB80791AA

—


3DB80792AA

—


3DB80793AA

—


3DB80794AA

—

955


Table 116



Name

Code

Remarks

5.6-8.5 GHz 3 dB 10W Splitter

1AB430730001

—

5.6-8.5 GHz 10 dB 10W SMA Coupler

1AB430740001

—

MPT-HLS filter and circulator items 4L GHz antenna circulator

3CY09590AA

—

4L GHz channel circulator

3DB02686AA

—

Filter 3.6-3.98 GHz 6 CAV.BW 25,5 MHz

3DB80331AA

—

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

3DB80332AA

—

Filter 3.6-3.98 GHz 6 CAV.BW 32 MHz

3DB80864AA

—

Filter 3,9-4,2 GHz 6 CAV.BW 32 MHz

3DB80865AA

—

Filter 3.6-3.98 GHz 6 CAV.BW 48 MHz

3DB80868AA

—


3DB80869AA

—

4U GHz antenna circulator

3CY09589AA

—

4U GHz channel circulator

3CY02030AA

—


3DB80333AA

—

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

3DB80334AA

—


3DB80866AA

—

Filter 4,7-5 GHz 6 CAV.BW 32 MHz

3DB80867AA

—


3DB80870AA

—

956


Table 116



Name

Code

Remarks

Filter 4,7-5 GHz 6 CAV.BW 48 MHz

3DB80871AA

—

5.6-6.4 GHz circulator

3DB01184AA

—


3DB80335AA

—


3DB80336AA

—

Filter 5.9-6.2 GHz BW 56 MHz

3DB80287AA

—


3DB80288AA

—

L6 Rejection filter 3 cav for 29.65 MHz CS

3DB80820AA

—

L6 Rejection filter 6cav for 59.3 MHz CS

3DB80815AA

—

U6 Rejection filter 3 cavities 6.7GHz

3DB80816AA

—


3DB01183AA

—


3DB80337AA

—


3DB80338AA

—


3DB80546AA

—


3DB80547AA

—


3DB80307AA

—


3DB80310AA

—

7.1-7.9 GHZ circulator

3DB01181AA

—


3DB80339AA

—


3DB80340AA

—

957


Table 116



Name

Code

Remarks


3DB80341AA

—


3DB80711AA

—


3DB80712AA

—


3DB80713AA

—

Rejection filter 6 cavities 7.4GHz

3DB80817AA

—


3DB05095AA

—

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

3DB80347AA

—


3DB80342AA

—

Filter 7.7-8 GHz BW 56 MHz

3DB80714AA

—


3DB80715AA

—


3DB80343AA

—


3DB80716AA

—

Rejection filter 3 cavities 8.1GHz

3DB80818AA

—

Filter 6.4-6.7 GHz cav Bw 32 MHz

3DB80546AA

—

Filter 6.7-7.1 GHz cav Bw 32 MHz

3DB80547AA

—

10 GHz circulator

3DB02132AA

—

Filter 10,378-10,630 GHz 6 CAV.BW 25,5 MHZ

3DB80344AA

—

Filter 10,028-10,280 GHz 6 CAV.BW 25,5 MHZ

3DB80345AA

—

Filter 10,028-10,280 GHz 5 CAV.BW 48 MHZ

3DB80591AA

—


3DB80592AA

—

11 GHz circulator

3DB02132AA

—

958


Table 116



Name

Code

Remarks

Filter 11.2-11.7 GHz BW 25.5 MHz

3DB80346AA

—


3DB80350AA

—


3DB80566AA

—


3DB80567AA

—


3DB80570AA

—


3DB80571AA

—

Mechanical adapter

3BD80504AA

—

Cable kit 6/7/8 GHz

3DB80543AB

—

Cable kit 10/11/13 GHz for LSY

3DB80797AA

—

Branching cover kit Rx-RXd MPTHLS to LSY

3DB80781AAAA

—

Cable kit RF CP LHRC replacement

3DB80909AA

—

Cable kit RF AP LHRC replacement

3DB80910AA

—

Interface kit MPT-HLS to LSY LHRC

3DB80896AA

—

Fan support kit MPT-HLS to LSY LHRC

3DB80901AA

—

Dummy plate LHRC

3DB80915AA

—

RF cables TxRx 6/7/8 GHz ext RT

3DB80753AA

—

RF cables TxRx 6/7/8 GHz inter RT

3DB80754AA

—

RF cables Rxd 6/7/8 GHz ext RT

3DB80755AA

—

RF cables Rxd 6/7/8 GHz inter RT

3DB80756AA

—

RT subrack LH

3DB80669AA

—

Dummy plate masking

3DB80676AA

—

Kits for MPT-HLS in LSY subrack

959


Table 116



Name

Code

Remarks

MPT-HLS expansion kits and materials Tx and Rx expansion kit (RF cables + fixation n brackets and screws

3DB80843AAAA

4L and 4U All configurations (w/o Diversity)

Rx Div expansion kit (RF cable + fixation n brackets and screws

3DB80844AAAA

4L and 4U All configurations (w Diversity)

Coax antenna cable for Rx branching expansion above 5th channel in homopolar configuration

3DB80863AAAA

4L and 4U Homopolar above

Back panel kit

3DB80268AA

6L to 13GHz All configurations

Sub-rack extension kit for one RT

3DB80227AA

6L to 13GHz All configurations

One channel extension kit (Tx and Rx)

3DB80413AB

6L to 8GHz Homopolar systems and heteropolar systems with one sub-rack

One channel extension kit (Rx Div)

3DB80414AB



3DB80617AA

10 to 13GHz All configurations


3DB80618AA

10 to 13GHz All configurations

5th channel extension kit Tx and Rx

3DB80417AB


5th channel extension kit Rx Div

3DB80419AB


960


Table 116



Name

Code

Remarks


3DB80421AA

6L to 8GHz Heteropolar systems with two sub-rack (four polarizations)


3DB80422AA

6L to 8GHz Heteropolar systems with two sub-rack (four polarizations)

5th channel extension kit (Tx and Rx)

3DB80423AB

6L to 8GHz Heteropolar systems with two sub-racks

5th channel extension kit (Rx Div)

3DB80424AB

6L to 8GHz Heteropolar systems with two sub-racks

961


32.1


MPT-HLS standard The MPT-HLS standard 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 standard transceiver is only available connected to an MSS-1, MSS4, or MSS-8. MPR-e mode is not available. The MPT-HLS standard can be connected to the Core or to an EASv2 card. 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 base-band combiner, which provide a combination of main receiver and second receiver signals. The MPT-HLS standard includes integrated XPIC capability. A license is required. The unit is able to host a diversity combiner, which provides a second receiver. The MPT-HLS standard with the diversity combiner is identified by an SD part number; see Table 116. The MPT-HLS standard radio is installed in an ETSI rack. 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 standard co-polar in one RT subrack

•

Up to 5 MPT-HLS standard alternate polar (with two diplexers and a dual polarization antenna) or XPIC in one RT subrack

•

Up to 20 MPT- HLS standard in XPIC on 2 RT subrack (due to limited RF resources): this option is available with the 2200 mm rack only.

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. Figure 486 shows an MPT-HLS standard unit.

962


Figure 486


MPT-HLS standard unit

Figure 487 shows an MPT-HLS standard system. Figure 487

MPT-HLS standard system

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


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


MPT-HLS unit Tx branching filters (lower subrack)

24003

The MPT-HLS standard supports the following external interfaces: •

GE (SFP data port)

•

GE - RPS (SFP port)

•

RF out

963


•

RF main in

•

RF diversity in

•

HSB (RF out switch control)

•

Fan Mgmt

•

Mgmt (not used)

•

XPIC port

•

PRx (RSL port)

Table 117 describes the unit LEDs.

964



Table 117


MPT-HLS unit front panel indicator details

INDICATOR

STATUS

DEFINITION

Status (S)

Off

Card not powered

Green Blinking


Green


Yellow


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 in HSB configuration)

In a PA critical temperature condition, the LED remains green. Red Blinking

MAP Communication Time-out: Communication between the Transceiver and the EASv2 cards is lost. This occurs in split-mount configuration only.

965


Table 117


MPT-HLS unit front panel indicator details (Continued)

INDICATOR

STATUS

DEFINITION

Power Emission

Off

Transceiver is not emitting power, according to the known configuration; for example, Hot Standby.

Green

Transceiver is emitting power as expected according to the known configuration.

Yellow

Transceiver is not emitting power due to an operator command, including manual PA PSU switch or Tx mute.

Red

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


Activity (A)

32.1.1


The RSSI is available on the PRx connector and is used to manually align the antenna in the field. Higher RSSI voltage indicates better antenna alignment. See the Antenna Alignment chapter in the 9500 MPR Hardware Installation and Replacement Manual for pinout information and typical voltage levels.

966



33 MPT-HLS compact transceiver (ETSI market only) unit data sheet This chapter provides information about the MPT-HLS compact transceiver. See Table 118 for MPT-HLS compact transceiver part numbers. See the following for additional information: •


•


•


•


•

MPT-HLS standard transceiver (ETSI market only) unit data sheet for information about the MPT-HLS standard transceiver

•


•


An option is also available to deploy the MPT-HLS compact system in an outdoor cabinet. Refer to the 9500 MPR Hardware Installation and Replacement Manual, Appendix A. Table 118

MPT-HLS compact transceiver part numbers

Name

Code

Common MPT-HLS items MPT-HLS6L RT STD

3DB80493AA

MPT-HLS 6L RT SD

3DB80493BA

MPT-HLS 6U RT STD

3DB80511AA

MPT-HLS 6U RT SD

3DB80511BA

MPT-HLS 7GHz RT STD

3DB80519AA

MPT-HLS 7GHz RT SD

3DB80519BA

MPT-HLS 8GHz RT STD

3DB80520AA

967

Release 7.0.0 3DB 19383 ACAA Issue 01 MPT-HLS compact transceiver (ETSI market only) unit data sheet

Table 118


MPT-HLS compact transceiver part numbers (Continued)

Name

Code

MPT-HLS 8GHz RT SD

3DB80520BA

MPT-HLS 4L GHz STD

3DB80803AA

MPT-HLS 4L GHz SD

3DB80803BA

MPT-HLS 4U GHz STD

3DB80805AA

MPT-HLS 4U GHz SD

3DB80805BA

MPT-HLS 10GHz RT Slim STD

3DB80580AA

MPT-HLS 10 GHz RT Slim SD

3DB80580BA

MPT-HLS 11 GHz RT Slim STD

3DB80581AB

MPT-HLS 11 GHz RT Slim SD

3DB80581BB

MPT-HLS 13 GHz STD

3DB80833AA

MPT-HLS 13 GHz SD

3DB80833BA

MPT-HLS 13 GHz STD allocated

3DB80833AAXX

MPT-HLS 13 GHz SD allocated

3DB80833BAXX

Racks and subracks / Fan Components

968

ETSI RACK H 1300

3CC50192AA

ETSI RACK H 2200

3CC50230AA

ETSI RACK H 2000

3CC50231AA

ETSI RACK H 1700

3CC50232AA

Nokia supplied 19" rack

1AD208450001

ETSI rack mounting kit TRU MSS - integrated new

3CC50276AA

ETSI rack mounting kit TRU MSS - integrated

3CC50042AAXX

Power distribution 2 batt for breakers - integrated

3CC50156AA

Breaker 2A - integrated

3CC50252AA


3CC50253AA


3CC50254AA

TR subrack

3DB80211AA


Table 118



Name

Code

Dummy Plate Kit

3DB80226AA

EXT Subrack One TR

3DB80227AA

Back Panel MPT-HLS v2

3DB80268AA

Branching Front Plate Kit

3DB80459AA

Fan Dummy Plate

3DB80464AA

Kit Support 2 Fans MPT-HLS v2

3DB80470AA

Fan Tray 1x4 MPT-HLS v2

3DB80477AB

Filters and Circulators Filter 5.9-6.2 GHz BW 56 MHz

3DB80287AA


3DB80288AA

Filter 6.4-6.7 GHz Bw 56 MHz

3DB80307AA


3DB80310AA


3DB80331AA


3DB80332AA


3DB80333AA

Filter 4.7-5 GHz BW 25.5 MHz

3DB80334AA

Filter 5,9-6,2 GHz BW 25,5 MHz

3DB80335AA


3DB80336AA


3DB80337AA


3DB80338AA


3DB80339AA


3DB80340AA


3DB80341AA


3DB80342AA


3DB80343AA

Filter 10,378-10,630GHz 6 CAV.BW 25,5MHz

3DB80344AA

969


Table 118

970



Name

Code

Filter 10,028-10,280GHz 6 CAV.BW 25,5MHz

3DB80345AA


3DB80346AA

Filter 7,7-8 GHz BW 25,5 MHz

3DB80347AA


3DB80350AA


3DB80546AA


3DB80547AA

Filter 11, 2-11,7 GHz 6 CAV.BW 32 MHz

3DB80566AA

Filter 10, 7-11,2 GHz 6 CAV.BW 32 MHz

3DB80567AA

Filter 10, 7-11,2 GHz BW 56 MHz

3DB80570AA

Filter 11,2-11,7 GHz BW 56 MHz

3DB80571AA


3DB80591AA


3DB80592AA


3DB80711AA


3DB80712AA


3DB80713AA


3DB80714AA


3DB80715AA


3DB80716AA


3DB80864AA


3DB80865AA


3DB80866AA


3DB80867AA


3DB80868AA


3DB80869AA


3DB80870AA


3DB80348AA


Table 118



Name

Code


3DB80349AA


3DB80871AA

4,4-5 GHz MS-MS-FS Circulator

3CY02030AAXX

7.1-7.9 GHz Circulator

3DB01181AAXX


3DB01182ABXX


3DB01183AAXX


3DB01184AAXX

11 GHz Circulator

3DB02132AAXX

13 GHz Circulator

3DB02734AAXX

10GHz Circulator

3DB04059AAXX

7,7-8,5GHz Circulator

3DB05095AAXX

CIRC. MS-MS-FS 3,6-4,2GHz

3DB02686AAXX

4 GHz kit antenna circulator

3DB80856AA

4.7 GHz kit antenna circulator

3DB80857AA

4 GHz kit antenna circulator 4 Pol

3DB80890AA

4.7 GHz kit antenna circulator 4 Pol

3DB80891AA

Rejection Filters Rejection Filter 6 CAV 6 GHz LOW

3DB80815AA

Rejection Filter 3 CAV 6 GHz HIGH

3DB80816AA

Rejection Filter 6 CAV 7 GHz

3DB80817AA

Rejection Filter 3 CAVITY 8 GHz

3DB80818AA

Rejection Filter 3 CAV 6 GHz LOW

3DB80820AA

Branching items WR137 Power absorber 5.6-7.1 GHz

3DB01185AAXX

WR137 Power absorber 7.1-8.5 GHz

3DB01186AAXX

Termination 11-13GHz WR75

3DB02189AAXX

971


Table 118

972



Name

Code

Flanged Stub L=47 MM

3DB02412AAXX


3DB02413AAXX


3DB02414AAXX


3DB02415AAXX


3DB02416AAXX


3DB02417AAXX


3DB02418AAXX


3DB03022AAXX


3DB03023AAXX

Flanged Stub UDR120

3DB03073AAXX

Flanged Stub UDR100

3DB03074AAXX


3DB03890AAXX


3DB03891AAXX


3DB03892AAXX


3DB03893AAXX


3DB03894AAXX


3DB03895AAXX


3DB03896AAXX

Flanged Stub L=376 MM (8+1)

3DB24239AAXX


3DB24240AAXX


3DB24241AAXX


3DB24242AAXX

Kit ext. TX-RX from 5ch to 6ch WR75

3DB80981AA

Kit ext. RXD from 5ch to 6ch WR75

3DB80982AA

Kit EXT 6CH WR75

3DB80985AA

Kit EXT 7CH WR75

3DB80986AA


Table 118



Name

Code

Kit EXT 8CH WR75

3DB80987AA

Kit EXT 9CH WR75

3DB80988AA

Kit EXT 10CH WR75

3DB80989AA

1st channel BRN 6/7/8GHz TRX left high

3DB80409AB

1st channel BRN 6/7/8GHz TRX right high

3DB80410AB

1st channel BRN 6/7/8GHz RXD left high

3DB80411AB

1st channel BRN 6/7/8GHz RXD right high

3DB80412AB

Extension TRX 6/7/8GHz 1 channel

3DB80413AB

Extension RXD 6/7/8GHz 1 channel

3DB80414AB

1st channel BRN 6/7/8GHz TRX right low

3DB80415AB

1st channel BRN 6/7/8GHz RXD right low

3DB80416AB

Kit 5th channel 6/7/8GHz TRX high

3DB80417AB

1st channel BRN 6/7/8GHz TRX 4 position

3DB80418AB

Kit 5th channel 6/7/8GHz RXD high

3DB80419AB

1st channel BRN 6/7/8GHz RXD 4 position

3DB80420AB

Extension TRX 6/7/8GHz 1 channel 4 pos

3DB80421AA

Extension RXD 6/7/8GHz 1 channel 4 pos

3DB80422AA

Kit 5th channel 6/7/8GHz TRX 4 position

3DB80423AB

Kit 5th channel 6/7/8GHz RXD 4 position

3DB80424AB

Kit of closing for channel circ.6/7/8 GH

3DB80438AA

Kit fixing waveguide TRX MPT HL V2

3DB80448AA

Kit fixing waveguide RXD MPT HL V2

3DB80456AA

1st channel BRN 11GHz TRX left high

3DB80613AA

1st channel BRN 11GHz TRX right high

3DB80614AA

1st channel BRN 11GHz RXD left high

3DB80615AA

1st channel BRN 11GHz RXD right high

3DB80616AA

973


Table 118



Name

Code

Extension TRX 11GHz 1 channel

3DB80617AA

Extension RXD 11GHz 1 channel

3DB80618AA

1st channel BRN 11GHz TRX right low

3DB80632AA

1st channel BRN 11GHz RXD right low

3DB80634AA

1st channel BRN 11GHz TRX 4 position

3DB80636AA

1st channel BRN 11GHz RXD 4 position

3DB80637AA

1st channel BRN 4/4.7GHz TRX left high

3DB80839AA

1st channel BRN 4/4.7GHz TRX right high

3DB80840AA

1st channel BRN 4/4.7GHz RXD left high

3DB80841AA

1st channel BRN 4/4.7GHz RXD right high

3DB80842AA

Extension TRX 4/4.7GHz 1 channel

3DB80843AA

Extension RXD 4/4.7GHz 1 channel

3DB80844AA

Cable for 6 to 10 channels high

3DB80863AA

1st channel BRN 4/4.7GHz TRX 4 position

3DB80884AA

1st channel BRN 4/4.7GHz RXD 4 position

3DB80885AA

1st channel BRN 4/4.7GHz TRX right low

3DB80924AA

1st channel BRN 4/4.7GHz RXD right low

3DB80925AA

Cable for 6 to 10 channels low

3DB80961AA

Kit of closing for channel circ.11 GHz

3DB80699AA

CON-COAX*COAX 4.1/9.5_MAL*N.A.*50Ohm

1AB006420058

CON-COAX*COAX 4.1/9.5_FEM*N.A.*50Ohm

1AB006420059

Customer Kit KIT stub FOR REJ Filter

3DB81101AA

KIT EXT RXD ON RX and TX DIV 7 GHz

3DB80799AA

KIT EXT RXD ON RX and TX DIV 6U

3DB81015AA

MPT-HLS HSB kits

974


Table 118



Name

Code

Kit TXRX HSB Right 5.725-6.425 GHz

3DB80593AA


3DB80594AA


3DB80595AA


3DB80596AA

Kit TXRX HSB Left 5.725-6.425 GHz

3DB80601AA


3DB80602AA


3DB80603AA


3DB80604AA


3DB80791AA


3DB80792AA


3DB80793AA


3DB80794AA

Kit BRN TX-RX HSB 4GHz L

3DB80966AA

Kit BRN RXD HSB 4GHz L

3DB80967AA

Kit BRN TX-RX HSB 4GHz U

3DB80968AA

Kit BRN RXD HSB 4GHz U

3DB80969AA

5,6-8,5 GHz 3 dB 10W SPLITTER

1AB430730001

5,6-8,5 GHz 10 dB 10W SMA COUPLER

1AB430740001

Coupler 10 dB HSB 4GHz

1AB459390001

Coupler 3 dB HSB 4GHz

1AB459400001

Kit for Adjacent CH Kit Adjacent ch 28 MHz TRX 7/8GHz

3DB80945AA

Kit Adjacent ch 28 MHz RXD 7/8GHz

3DB80946AA

Kit Adjacent ch 28 MHz TRX 7/8GHz 5th CH4 Pol

3DB80947AA

Kit Adjacent ch 28 MHz RXD 7/8GHz 5th CH4 Pol

3DB80948AA

Kit Adjacent ch 28 MHz TRX 7/8GHz 1-4 CH4 Pol

3DB80949AA

975


Table 118



Name

Code

Kit Adjacent 28MHz TRX 10.5GHz

3DB80950AA

Kit Adjacent 28MHz TRX 11GHz

3DB80951AA

Kit Adjacent 28MHz TRX 13GHz

3DB80952AA

Kit Adjacent 28MHz RXD 10.5GHz

3DB80953AA

Kit Adjacent 28MHz RXD 11GHz

3DB80954AA

Kit Adjacent 28MHz RXD 13GHz

3DB80955AA

Kit Adjacent CH 28MHz TRX 6L

3DB81019AA

Kit Adjacent CH 28MHz RXD 6L

3DB81020AA

Kit Adjacent 28MHz TRX L4

3DB81023AA

Kit Adjacent 28MHz RXD L4

3DB81024AA

Kit Adjacent 28MHz TRX U4

3DB81025AA

Kit Adjacent 28MHz RXD U4

3DB81026AA

Cables cord RJ45-RJ45 for fan management L=1,3m

3CC52141AD

cord RJ45-RJ45 for fan management L=1,3m

3CC52141ADXX

XPIC RJ45-RJ45 cord 3m

3CC52204AA


3CC52204AB


3CC52204AC

Zip power cable 2 x 1 mm2 integrated

3CC52205AAXX

Zip power cable 2 x 6 mm2 integrated

3CC52206AAXX

SFP to SFP cable assembly 1.5 m

3DB80628AA

SFP to SFP cable assembly 2 m

3DB80628AB


3DB80628AC

SFP to SFP cable assembly 0.5 m

3DB80628AD


3DB80628AE

Items for Compact Indoor

976


Table 118



Name

Code

MSS-1/4/8 Adapter bracket kit

3DB18181AAAB

Branching Kit TX/RX 4ch OMO WR137 Exit Back

3DB81072AA

Kit RXD 4ch OMO WR137 Exit Back

3DB81164AA

Kit TX/RX 4ch Omo WR137 Exit Top

3DB81074AA

Kit RXD 4ch Omo WR137 Exit Top

3DB81166AA

Kit TX/RX 2ch Omo WR137 Exit Back

3DB81075AA

Kit RXD 2ch Omo WR137 Exit Back

3DB81167AA

Kit TX/RX 2ch Omo WR137 Exit Top

3DB81077AA

Kit RXD 2ch Omo WR137 Exit Top

3DB81169AA

Kit TX/RX 2x2ch AP WR137 Exit Back

3DB81080AA

Kit RXD 2x2ch AP WR137 Exit Back

3DB81172AA

Kit TX/RX 2x2ch AP WR137 Exit Back

3DB81078AA

Kit RXD 2x2ch AP WR137 Exit Back

3DB81170AA

Kit TX/RX 2x2ch AP WR137 Exit Top

3DB81080AA

Kit RXD 2x2ch AP WR137 Exit Top

3DB81172AA

Common Items Compact Subrack 2 TRs MPT-HLS

3DB80992AA

Fan board HLv2 Compact

3DB81009AB

TRs Dummy Plate

3DB81153AA

Adaptor Bracket Kit 2U ETSI

3CC50287AA

Adaptor Bracket Kit 4U ETSI

3CC50289AA

Waveguide on ETSI Rack Kit ETSI Rack Exit WG TXRX OMO High

3DB81121AA

Kit ETSI Rack Exit WG RXD OMO High

3DB81122AA

977


Table 118



Name

Code

Kit ETSI Rack Exit WG TXRX AP High

3DB81125AA

Kit ETSI Rack Exit WG RXD AP High

3DB81126AA

PSU cable TR/MSS subrack compact

3DB81028AA

Cables

978

KIT COAX CABLE OMO TX-RX TR 1

3DB81087AA


3DB81088AA


3DB81089AA


3DB81090AA

COAX CABLE OMO RXD TR 1

3CY09402AA


3CY04468AA


3CY04468AA


3CY04468AA

KIT COAX CABLE AP TX-RX TR 1

3DB81091AA


3DB81092AA


3DB81093AA


3DB81094AA

COAX CABLE AP RXD TR 1

3CY04468AA


3DB81158AA


3DB81159AA


3CY04467AA


33.1


MPT-HLS compact The MPT-HLS compact 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. The MPT-HLS compact uses the same MPT-HLS unit as the standard version but differs from the MPT-HLS standard allowing modularity of parts that provides more flexibility and compactness for smaller footprints. In this release the frequencies supported are L6 GHz and U6 GHz The MPT-HLS compact transceiver is available connected to an MSS-1/4/8. The MPT-HLS compact can be connected to the Core or to an EASv2 card. 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 base-band combiner, which provide a combination of main receiver and second receiver signals. The MPT-HLS compact includes integrated XPIC capability. A license is required. The unit is able to host a diversity combiner, which provides a second receiver. The MPT-HLS compact with the diversity combiner is identified by an SD part number; see Table 118. The MPT-HLS compact radio is installed in one of the following racks for indoor use: •

21” ETSI rack. Four different ETSI racks are available (2200, 2000, 1700, 1300 mm). Antenna feeder access is on the top of the rack.

•

19” rack. This rack can be Nokia or customer provided.Antenna feeder access is on the back side of the branching drawer.

For 21” ETSI installations, all parts are delivered mounted and connected with the exception of the MSS-1/4/8. For 19” rack installations, parts arrive unmounted and are assembled on-site. Inside the rack, are the following components: •

A RT subshelf to support up to 2 transceivers and a fan unit. The MPT-HLS compact supports up to 2 subshelves (4 total radio channels). Power supply access is part of the subshelf and uses 2 filtered connectors for protected battery connection.

•

A branching drawer containing the passive functions for radio channelization

•

An MSS-1/4/8 that can be mounted (recommended) or not mounted with the MPT-HLS compact system.

The TRU (always protected) must be located on the top of the rack.

979



Figure 488 shows an equipped MPT-HLS compact subshelf. Figure 488

MPT-HLS compact subshelf

Figure 489 shows an MPT-HLS compact system. Figure 489

MPT-HLS compact system

The MPT-HLS compact supports the following external interfaces: •

980

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 119 describes the LEDs found on the unit.

981


Table 119


MPT-HLS compact transceiver front panel indicator details

INDICATOR

STATUS

DEFINITION

Status (S)

Off

Card not powered

Green Blinking


Green


Yellow


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 in HSB configuration)

In a PA critical temperature condition, the LED remains green. Red Blinking

982

MAP Communication Time-out: Communication between the Transceiver and the EASv2 cards is lost. This occurs in split-mount configuration only.


Table 119


MPT-HLS compact 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


Activity (A)

33.1.1


The RSSI is available on the PRx connector and is used to manually align the antenna in the field. Higher RSSI voltage indicates better antenna alignment. See the Antenna Alignment chapter in the 9500 MPR Hardware Installation and Replacement Manual for pinout information and typical voltage levels.

983


984




34 Fan cards unit data sheet Table 120

Fan cards


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB18134BA 3DB23911BAXX

Fan 2U Card

N/A

N/A

N/A

Active

3DB18134BB

Fan 2U Card

CRCCACPJAA

171275

070VGP

Active

3EM23911AA, 3EM23911AAXX

Fan 2U Card With Alarms

CRCCADYJAA

172825

070XBK

Active

3EM23911BB 3EM23911BBXX

Fan Evo 2U Card W/ Alarms

CRCCASZJAA

N/A

N/A

Active

3DB18218AD

Fan 1U Card

N/A-4

N/A-4

N/A-4

Active-4

34.1


Provides forced air flow for MSS-8 or MSS-4 shelf cooling.

•

Fan 2U card types are used in MSS-8 shelf application. The following fan types are available: −

Fan 2U card (Basic fan card)

−

FAN 2U card W/Alarms provides relay and housekeeping alarm support

−

Fan Evo card provides relay and housekeeping alarm support

•

The Fan cards with Alarms provide Summary, major, and Minor alarm front panel LEDs and alarm relay outputs

•

Fan 1U card is used in MSS-4 shelf application.

Note: The different fan types appear differently in JUSM: • • •

Basic fan card: FAN Fan card with alarms: A-FAN Fan Evo card: E-FAN

985

Release 7.0.0 3DB 19383 ACAA Issue 01 Fan cards unit data sheet

34.2


Description Both the basic and enhanced Fan 2U cards provide forced air cooling for the MSS-8 shelf. The Fan 2U cards with alarms provide up to four alarm input signals to the MSS-8 shelf and up to three alarm outputs.

34.3

Indicators, connectors, and control The Fan 1U card has no indicators, connectors and controls. The basic Fan 2U card has no indicators, connectors and controls. See Figure 490 for enhanced Fan 2U cards with alarms front panel indicator, controls, and connector locations. See Table 121 for Fan 2U card with alarms (3EM23911AA and 3EM23911BB) indicators details. See Table 122 for Fan 2U card connector details. See Table 123 for Fan 2U card control details. Alarm Cutoff and Lamp Test are not supported with the current release software. The ACD/LT button does not appear on the 3EM23911BB card.

986



Figure 490

Fan 2U card w/alarms (front view)

Figure 491

Fan Evo card (front view)

Table 121

Enhanced FAN 2U w/alarms and Fan Evo (3EM23911AA and 3EM23911BB) front panel indicator details

INDICATOR

STATUS

DEFINITION

Fan

Green

Normal operation

Amber

Failure of one fan

Red

Card fail

987


Table 121


Enhanced FAN 2U w/alarms and Fan Evo (3EM23911AA and 3EM23911BB) front panel indicator details (Continued)

INDICATOR

STATUS

DEFINITION

Batt A

Green

Normal operation

Off

Battery fail

Green

Normal operation

Off

Battery fail

Green

Normal operation

Red

NE summary alarm indicates either a Major or Minor alarm.

Major

Red

NE summary, indicates a Major alarm is present.

Minor

Yellows

NE summary, indicates a Minor alarm is present.

Batt B

Summary

Table 122

FAN 2U w/alarms and Fan Evo (3EM23911AA and 3EM23911BB) front panel connector details

CONNECTOR

TYPE

FUNCTION

External Alarms

DSUB 15 Position

External Alarm Inputs and Outputs

Table 123

FAN 2U w/alarms (3EM23911AA) front panel control details

CONNECTOR

TYPE

FUNCTION

ACO/LT 1

push button

Alarm cutoff

Note: 1.

Table 124

ACO/LT control is not supported in the current release software.

Fan 2U card office alarm and control connector / cable detail

PIN DEFINITION

CONTACT NUMBER

WIRE COLOR

Alarm Input 1

01

White/Blue

Alarm Input 2

02

Blue/White

Alarm Input 3

11

White/Orange

988

Function


Table 124


Fan 2U card office alarm and control connector / cable detail (Continued)

PIN DEFINITION

CONTACT NUMBER

WIRE COLOR

Alarm Input 4

12

Orange/White

Ground

07

White/Green

14

White/Brown

15

Brown/White

08

White/Slate

10

Slate/White

04

Red/Blue

Alarm Output 3

05

Blue/Red

Not Used

03

N/A

Not Used

06

N/A

Not Used

09

N/A

Not Used

13

N/A

Alarm Output 1

Function

Summary Alarm


Major Alarm


34.4

Minor Alarm

Functional overview Both the basic and enhanced Fan 2U cards provide forced air cooling for the MSS-8 shelf. The Fan 1U card provides forced air cooling for the MSS-4 shelf. Alarm output 1 (Summary Alarm) is energized for the no-alarm state, so that it generates an alarm when shelf power is lost. As a result, all outputs are open during system operation with no alarms. The enhanced Fan 2U card Alarm Cutoff and Lamp Test are not supported with the current release software.

989


34.5


Output alarm electrical characteristics Each alarm output has two pins. Depending if the alarm is present or not the two relevant pins will be in short circuit or in open circuit condition. When the relay alarm output pins will be in short circuit condition, the alarm outputs will tolerate a 50mA max current and the max voltage between the two pins never exceed 2V. When the relay alarm output pins are in open circuit condition the alarm outputs will tolerate 60V and the max leakage current will never exceed 0.2mA.

34.6

Input alarm electrical characteristics The inputs must be able to reveal if the relevant pin is open or short circuit with respect to GND. Table 125 shows the alarm behavior.

Table 125

Input alarm electrical behavior

Input pin status

OPEN

Logical “1”

GND (0V)

Logical “0”

Alarmed, Not Alarmed condition depends on alarm polarity settings provisioned

The short circuit is detected with an input voltage 0.5 V < V < +8.5 V. The open circuit is detected with an input voltage +2.25 V < V < +5.5 V. The alarm inputs can tolerate –0.5 volts to +5 volts without damage.

34.7

Housekeeping for the Fan Evo (3EM23911BB) The Fan Evo card with alarms provides 11 housekeeping signals that correspond to eight alarm inputs used to monitor alarms and three alarm outputs. Input alarms can be mapped to outputs: •

Individual FAN alarm inputs or internal alarm events may be mapped to any output within the network.

•

Multiple input or internal events may be mapped to a common output.

Table 126 shows the pin-out of the housekeeping connector.

990


Table 126


Housekeeping pin-out info for Fan Evo EM23911BB (Sub D 15 female)

Pin

Signal

Pin

Signal

1

HK_IN1

9

HK_IN7

2

HK_IN2

10

HK_OUT2 -

3

HK_IN5

11

HK_IN3

4

HK_OUT3 +

12

HK_IN4

5

HK_OUT3 +

13

HK_IN8

6

HK_IN6

14

HK_OUT1 +

7

GND

15

HK_OUT1 -

8

HK_OUT2 +

991


992




35 Core-E control and switching module unit data sheet Table 127

Core-E control and switching module


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB18326AC

Core-E control and switching module

CRCCACMJ AA

171233

—

Active

35.1

Description The Core-E unit provides the following hardware support: 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. 2x1000 base-Lx or Sx (SFP optical interface) or 2x1000 base-T (SFP electrical interface) available with an optional plug-in: port #5 and port #6. Port #1 through port #6 support interconnection directly to MPT-HC/HC-HQAM/XP/ XP-HQAM. Port #1 through port #4 support interconnection directly to MPT-MC. Port #5 and port #6 support interconnection directly to MPT-HL.

35.1.1

Main functions •

Controller

•

Layer 2+ Eth Switch, VLAN management & MAC based −

Ethernet MAC learning

−

Cross-connect function for PDH and Data payload traffic

−

For any “packetized” data flow, the layer 2 switch is in charge to manage the EPS protection

−

QoS management.

993

Release 7.0.0 3DB 19383 ACAA Issue 01 Core-E control and switching module unit data sheet

•


Selection of the synchronization clock distributed to all plug-in.

The Core-E unit has the option to equip 1GigE Ethernet interface in the SFP ports (port #5, port #6). These ports can be used to connect Ethernet user traffic or to connect directly to an MPT-HC/HC-HQAM/XP/XP-HQAM or MPT-HL/HLC/HLS. Three modules are available: •

1000BASE-LX (optical)

•

1000BASE-SX (optical)

•

1000BASE-T (electrical)

The flash card stores the license type, the equipment software, the equipment MIB and the equipment MAC address. Warning: The optional optical SFP plug-in, which may 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 included on the equipment due to the lack of space.

35.2

Features and application notes The Core-E card provides the following functions: •

•

994

Four 10/100/1000 BaseT Ethernet ports, supporting the following: −

User Ethernet ports

−

MPT ODU 1+0

−

MPT ODU 1+1

Two GigE optical Ethernet ports, supporting the following: −

User Ethernet ports

−

MPT-HC/HC-HQAM/XP/XP-HQAM 1+0

−


−

MPT-HL/HLC/HLS 1+0

−

MPT-HL/HLC/HLS 1+1

•

Network Management System (NMS) port

•

TMN Ethernet Interface port

•

MSS shelf synchronization clock reference

•

External clock reference input and output


•


Supports unprotected and 1+1 Core-E Equipment Protection Switch (EPS) configurations

Caution: The following Cautions apply: • •

If an MPT-HL is connected to the main Core card, Core protection is not supported. A protection switch will cause communication with the MPT-HL to be lost. A Core-E cannot serve as a spare for a CorEvo card or vice versa.

•

The active Core-E card manages communications — between all of the peripheral cards (P32E1DS1, P2E3DS3, SDHACC, MPT-HL Transceiver, and P8ETH) to provide peripheral management, NMS, equipment configuration, event reporting and logging, equipment database management and software downloads.

•

Layer 2 Ethernet Switch — performs the cross-connection between the peripheral cards and the Ethernet ports.

•

35.3 35.3.1

−

The Switch shall assure to the system a complete interconnection between all cards connected into the MSS-4/8 shelf.

−

The Switch shall perform address learning, standard 802.1Q management (VLAN), Layer 2 switching (MAC address, VLAN), and QOS per system (802.1P and DiffServ).

−

VLAN table and Address Tables shall be required to be maintained/ updated by the system for Core-E and Peripheral Switches.

Storage of Log Files for events and alarms. Storage capacity is the most recent 500 events and 700 alarms.

Description Purpose and function The Control and Switching Module (Core-E) performs all supervisory functions for the MSS and switches Ethernet packets from peripherals to radio cards. The Core-E consists of microprocessor and Ethernet switch circuits.

995


35.3.2


Microprocessor The microprocessor consists of a 128 Mbyte system memory (SDRAM), 8 Mbyte boot memory (EEPROM), and 128 Mbyte flash memory.

35.3.3

Options/configurations There are no card options. The Core-E card is required in slot 1. The Spare Core-E card resides in slot 2 when equipped.

35.4

Indicators, connectors, and control The Control and Switch Module (Core-E) card has the following indicators, connectors, and controls. See Figure 492 for Core-E card front panel indicator and connector locations. See Table 128 for Core-E card indicators details. See Table 129 for Core-E card connector details. The Core-E card has a reset control for performing a manual hard reset of the Core-E card.

996



Figure 492

Core-E front panel details

Table 128

Core-E front panel indicator details

INDICATOR

STATUS

DEFINITION

Indicators on Ethernet ports Link (L)

Activity (A)

Off

Link Down

On

Link Up

Off

No Tx/Rx activity

Blinking

Tx/Rx activity

Indicators on the face plate of the card Major Alarm (M)

On (Red)

At least one alarm is present on the NE with Major severity is present on the NE.

Minor Alarm (m)

On (Red)

At least one alarm is present on the NE with Minor severity is present on the NE.

Warning Alarm (W)

On (Yellow)

At least one alarm is present on the NE with Warning severity is present on the NE.

Abnormal Condition (A)

On (Yellow)

At least one Abnormal Condition is present on the NE.

997


Table 128


Core-E front panel indicator details (Continued)

INDICATOR

STATUS

DEFINITION

Status (S)

Off


Green Blinking

Table 129

•

Download, Software Booting, or Flash Card Realignment in Progress

•

Card Mismatch

•

A spare Core-E card is inserted in slot 2 but not provisioned

Green

In Service, Normal Operation, and Correctly Provisioned

Yellow

In Protect, Correctly Provisioned as EPS

Red

Card Fail

Core-E front panel connector details

CONNECTOR

TYPE

FUNCTION

Ethernet Ports 1-4

RJ45

10/100/1000BaseT Ethernet Port

Ethernet Port 4

RJ45

TMN network interface

SFP Port

SFP

GigE Ethernet Optical Port

Craft terminal/IT/TFC

RJ45

Dedicated craft terminal port

USB

USB

Not used

Sync In

Slip Fit Coax 1.0/2.3, Female

System sync input

Sync Out

Slip Fit Coax 1.0/2.3, Female

System sync output

998



36 CorEvo control and switching module unit data sheet Table 130

CorEvo control and switching module


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB19318AA

CorEvo-10G control and switching module

CRGIAEGKA A

194254

—

Active

3DB18788AC

CorEvo-1G control and switching module

CRGIAEFKA A

194115

—

Active

36.1

Description The CorEvo unit provides the following hardware support: •

Based on packet technology with eight GbEth serial internal interfaces between CorEvo and peripherals (jumbo frames 9728 bytes allowed)

•

4x10/100/1000 Ethernet electrical embedded interface (RJ45): port #1 to port #4

•

2x1000 SFP optical interface with speed up to 10 Gb/s: port #5 and port #6 The following SFP are supported on these ports:

•

−

1000 Base-Sx

−

1000 Base-Lx

−

10/100/1000 Base-T

−

CWDM

−

SFP copper cable assembly

−

2E1/DS1

−

EoSDH

2x1000 SFP optical interface with speed up to 1 Gb/s: port #7 and port #8 The following SFP are supported on these ports: −

1000 Base-Sx

−

1000 Base-Lx

−

10/100/1000 Base-T

999

Release 7.0.0 3DB 19383 ACAA Issue 01 CorEvo control and switching module unit data sheet

•

36.1.1

−

CWDM

−

SFP copper cable assembly

−

Sync-in/Sync-out

−

1588 ToD


Port #1 through port #4 support interconnection directly to MPT ODU. Port #7 and port #8 support interconnection directly to MPT-HC/HC-HQAM/XP/XPHQAM and MPT-HL/HLC/HLS.

Main functions •

Controller

•

Layer 2+ Eth Switch, VLAN management & MAC based −

Ethernet MAC learning

−

Cross-connect function for PDH and Data payload traffic

−

For any “packetized” data flow, the layer 2 switch is in charge to manage the EPS protection

−

QoS management

The CorEvo unit has the option to equip 10 GigE Ethernet interface in the SFP ports (port #5, port #6) if a license is present. The flash card stores the license type, the equipment software, the equipment MIB and the equipment MAC address. Warning: The optional optical SFP plug-in, which may be installed in port #5 to port #8 of the CorEvo 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 included on the equipment due to the lack of space.

36.2

Features and application notes The Core-E card provides the following functions: •

1000

Four 10/100/1000 BaseT Ethernet ports, supporting the following: −

User Ethernet ports

−

MPT ODU 1+0

−

MPT ODU 1+1


•

•



User Ethernet ports

−


−


−

MPT-HL/HLC/HLS 1+0

−

MPT-HL/HLC/HLS 1+1


User Ethernet ports

−

Sync-in/Sync-out SFP

•

Network Management System (NMS) port

•

TMN Ethernet Interface port

•

MSS shelf synchronization clock reference

•

1588 transparent clock reference

•

External clock reference input and output

•

Supports unprotected and 1+1 CorEvo Equipment Protection Switch (EPS) configurations

Caution: The following Cautions apply: • •

If an MPT is connected to the main Core card, Core protection is not supported. A protection switch will cause communication with the MPT to be lost. A Core-E cannot serve as a spare for a CorEvo card or vice versa.

•

The active Core card manages communications among all of the peripheral cards to provide peripheral management, NMS, equipment configuration, event reporting and logging, equipment database management and software downloads.

•

Layer 2 Ethernet Switch — performs the cross-connection between the peripheral cards and the Ethernet ports.

•

−

The Switch shall assure to the system a complete interconnection between all cards connected into the MSS-4/8 shelf.

−

The Switch shall perform address learning, standard 802.1Q management (VLAN), Layer 2 switching (MAC address, VLAN), and QOS per system (802.1P and DiffServ).

−

VLAN table and Address Tables shall be required to be maintained/ updated by the system for Core-E and Peripheral Switches.

Storage of Log Files for events and alarms. Storage capacity is the most recent 500 events and 700 alarms.

1001


36.3


Description The Control and Switching Module (CorEvo) performs all supervisory functions for the 9500 MPR MSS and switches Ethernet packets from peripherals to radio cards. The CorEvo consists of microprocessor and Ethernet switch circuits.

36.3.1

Microprocessor The microprocessor consists of a 128 Mbyte system memory (SDRAM), 8 Mbyte boot memory (EEPROM), and 128 Mbyte flash memory.

36.3.2

Options/configurations There are no card options. The Core card is required in slot 1. The Spare Core card resides in slot 2 when equipped.

36.4

Indicators, connectors, and control The CorEvo card has the following indicators, connectors, and controls. See Figure 493 for CorEvo card front panel indicator and connector locations. See Table 131 for CorEvo card indicators details. See Table 132 for CorEvo card connector details. The CorEvo card has a reset control for performing a manual hard reset of the card. Caution: A manual hard reset of the CorEvo card is traffic affecting.

1002


Figure 493


CorEvo front panel details MGMT port (RJ-45)

CorEvo

Hardware reset button

Status LED

Mgmt Port

R 1

2

3

4

5

6

7

A

8

10/100/1000 Ethernet 10GigE SFP GigE SFP electrical ports 1-4 (RJ-45) ports 5-6 ports 7-8

S

Alarm LED 25100

Table 131

CorEvo front panel indicator details

INDICATOR

STATUS

DEFINITION

Indicators on Ethernet ports Link Two Link LEDs on each Ethernet port

Off

Link Down

On

Link Up

Activity

Off

No Tx/Rx activity

Blinking

Tx/Rx activity

Indicators on the face plate of the card Status (S)

Off


Green Blinking

Software Booting or Flash Card Realignment in Progress

Green

In Service, Normal Operation, and Properly Provisioned

Yellow

Properly Provisioned as EPS, In Standby

Red

Card Fail or Card Mismatch

1003


Table 131


CorEvo front panel indicator details (Continued)

INDICATOR

STATUS

DEFINITION

Alarm/information (A)

Off

No alarms, warnings or abnormal conditions

Yellow Blinking

At least one Abnormal Condition is present on the NE.

Yellow

At least one alarm with Warning severity is present on the NE. An Abnormal Condition may also be present.

Red

At least one alarm with Major or Minor severity is present on the NE. An alarm of Warning severity or an Abnormal Condition may also be present.

Red and Yellow transition

At least one alarm with Major or Minor severity and at least one alarm with Warning severity is present on the NE.

Table 132

CorEvo front panel connector details

CONNECTOR

TYPE

FUNCTION

Ethernet Ports 1-4

RJ45

Electrical Ethernet Port

Ethernet Port 4

RJ45

TMN network interface

SFP Port

SFP


Mgmt port

RJ45

Dedicated craft terminal port

1004



37 DS1 RJ-45 Patch Panel unit data sheet Table 133

DS1 RJ-45 Patch Panel


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

1AF15245AB

DS1 RJ-45 Patch Panel

N/A

N/A

N/A

Active

37.1

37.2


Converts P32E1DS1 card SCSI connectors to thirty-two RJ-45 connectors.

•

MSS-1 unit support: converts MSS-1 unit MSS/DS1 connector to sixteen RJ45 connectors. −

Supports up to two MSS-1 units

−

Requires one 68 pin SCSI cable per MSS-1 unit

•

Supports both protected and non-protected P32E1DS1 applications.

•

Requires two 68 pin SCSI cables in non-protected DS1 configuration. Requires four 68 pin SCSI cables in protected DS1 configuration.

Description The DS1 RJ-45 Patch Panel mounts above and/or below the MSS-1/4/8 shelf. Requires 1.5 rack increments. Customer interconnect are thirty-two RJ-45 connectors, I/O 1 through I/O 32. Each RJ-45 connector supports one DS1 signal, 1 through 32 respectively and provides both input and output signal connections. Four 68 pin SCSI connectors interconnects the main and spare P32E1DS1 card connectors. See Figure 494 for a front view of the DS1 RJ-45 Patch Panel. See Figure 495 for a rear view of the DS1 RJ-45 Patch Panel.

1005

Release 7.0.0 3DB 19383 ACAA Issue 01 DS1 RJ-45 Patch Panel unit data sheet


Figure 494

DS1 RJ-45 patch panel (front view)

Figure 495

DS1 RJ-45 patch panel (rear view)

37.3

Connectors See Table 134 for DS1 RJ-45 Patch Panel connector details for P32E1DS1 card.

Table 134

P32E1DS1 DS1 card front panel connector details

CONNECTOR

TYPE

FUNCTION

I/O (1- 32)

RJ-45

DS1, Tx and Rx (tip and ring), interconnect DS1s number 1 through 32

M1

64 position SCSI connector

DS1, Tx and Rx (tip and ring), interconnect DS1s number 1 through 16, Main

M2



M3


DS1, Tx and Rx (tip and ring), interconnect DS1s number 1 through 16, Spare

M4


DS1, Tx and Rx (tip and ring), interconnect DS1s number 17 through 32, Spare

See Table 135 for DS1 RJ-45 Patch Panel connector details for MSS-1 unit.

1006


Table 135


MSS-1 front panel connector details

CONNECTOR

TYPE

FUNCTION

I/O (1- 32)

RJ-45


M1



M2



1007

Release 7.0.0 3DB 19383 ACAA Issue 01 DS1 RJ-45 Patch Panel unit data sheet

1008




38 DS1/MSS-1 d-connector patch panel unit data sheet Table 136

DS1/MSS-1 d-connector patch panel


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB16102AA

DS1 D-Connector Patch Panel

N/A

N/A

N/A

Active

38.1

38.2


Converts P32E1DS1 card SCSI connectors to four 37 position DSUB connectors.

•

MSS-1 unit support: converts MSS-1 unit MSS/DS1 SCSI connector to sixteen DSUB connectors. −

Supports up to two MSS-1 units

−

Requires one 68 pin SCSI cable per MSS-1 unit

•

Supports both protected and non-protected P32E1DS1 applications.

•

Requires two 68 pin SCSI cables in non-protected DS1 configuration. Requires four 68 pin SCSI cables in protected DS1 configuration.

Description The DS1 D-Connector Patch Panel mounts above and/or below the MSS-8 shelf. Requires 1 rack increments. Customer interconnect are the four 37 position DSUB connectors. Each 37 position DSUB connector supports eight DS1 signals. Four 68 pin SCSI connectors interconnects the main and spare P32E1DS1 card connectors. See Figure 496 for a front view of the DS1 D-Connector Patch Panel. See Figure 497 for a rear view of the DS1 D-Connector Patch Panel.

1009

Release 7.0.0 3DB 19383 ACAA Issue 01 DS1/MSS-1 d-connector patch panel unit data sheet

Figure 496

DS1 RJ-45 patch panel (front view)

Figure 497

DS1 RJ-45 patch panel (rear view)

38.3


Connectors See Table 137 for DS1 D-Connector Patch Panel connector details.

Table 137


CONNECTOR

TYPE

FUNCTION

E1/DS1 - 1/8

37 position DSUB connector

DS1, Tx and Rx (tip and ring), Customer Interconnect DS1s number 1 through 8

E1/DS1 - 9/16



E1/DS1 - 17/24



E1/DS1 - 25/32



E1/DS1 - 1/16 Main


DS1, Tx and Rx (tip and ring), P32E1DS1 Interconnect DS1s number 1 through 16, Main

1010


Table 137


P32E1DS1 DS1 card front panel connector details (Continued)

CONNECTOR

TYPE

FUNCTION

E1/DS1 - 17/32 Main



E1/DS1 - 1/16 Spare


DS1, Tx and Rx (tip and ring), P32E1DS1 Interconnect DS1s number 1 through 16, Spare

E1/DS1 - 17/32 Spare


DS1, Tx and Rx (tip and ring), P32E1DS1 Interconnect DS1s number 17 through 32, Spare

See Table 138 for MSS-1 D-Connector Patch Panel connector details. Table 138

MSS-1 front panel connector details

CONNECTOR

TYPE

FUNCTION

E1/DS1 - 1/8



E1/DS1 - 9/16



E1/DS1 - 17/24



E1/DS1 - 25/32



E1/DS1 - 1/16 Main



E1/DS1 - 17/32 Main



1011

Release 7.0.0 3DB 19383 ACAA Issue 01 DS1/MSS-1 d-connector patch panel unit data sheet

1012




39 P32E1DS1 PDH card unit data sheet Table 139

P32E1DS1 PDH card


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB18126AD

P32E1DS1 PDH Card

N/A

N/A

N/A

Inactive

3DB18126AE

P32E1DS1 PDH Card

CRG2ABUDAA

070VGM

171272

Active

39.1

Description In the TX direction, the E1/DS1 PDH card (DS1/E1 Access) processes and encapsulates up to 32 DS1 or E1 input lines into Ethernet packets that are sent to the Core cards. In the RX direction, the card extracts data from the Ethernet data packets and processes the data to provide up to 32 output lines. The 32xE1DS1 Local Access Module performs the following macro functions: •

Termination of 32 DS1 or E1 signals (32 DS1/E1 bi-directional interfaces according ITU-T G.703 on the front panel)

•

Framed DS1/E1 bi-directional alarm management

•

Bi-directional Performance Monitoring on Framed DS1/E1

•


•

Reconstruction of the original PDH Timing meeting G823/824.

•

Selection of the Active Core

•

Sending/getting those standard Eth packets to the Core card

•

Communication with the Controller for provisioning and status report

The module communicates with the Core cards through two GbEth Serial copper bidirectional interfaces on the backplane.

1013

Release 7.0.0 3DB 19383 ACAA Issue 01 P32E1DS1 PDH card unit data sheet

39.2

39.3



Terminates up to 32 DS1or E1 signals

•

Framed DS1/E1 Bi-Directional alarm management

•

Bi-Directional performance monitoring on framed DS1/E1 signals

•

Encapsulation of data flows into standard Ethernet packets Inter Working Function (IWF)

•

Extraction of data flows from standard Ethernet packets IWF

•

Supports both unprotected and 1+1 EPS protected configurations

•

MSS-8 shelf supports up to six unprotected P32E1DS1 cards and up to three P32E1DS1 protected pairs

Description The P32E1DS1 card provides 32 interfaces. The MSS-8 shelf supports up to six P32E1DS1 cards or 192 unprotected DS1/E1 interfaces or 96 protected DS1/E1 interfaces. The P32E1DS1 are supported in MSS-8 slots 3 through 8 for unprotected radio configurations. In protected radio configurations, a pair of P32E1DS1s are required. The main P32E1DS1s are equipped in slots 3, 5, or 7 and the protect (spare) P32E1DS1s are equipped in the slots directly across from the main (slot 4, 6, or 8). The spare P32E1DS1 card protects the radio if the main P32E1DS1 fails.

39.4

Indicators, connectors, and control The P32E1DS1 PDH card has the following indicator and connectors: See Figure 498 for P32E1DS1 PDH card front panel indicator and connectors. See Table 140 for P32E1DS1 PDH card indicators details. See Table 141 for P32E1DS1 PDH card connector details. The P32E1DS1 PDH card has no controls located on the card.

1014



Figure 498

P32E1DS1 card front panel view

Table 140

P32E1DS1 card front panel indicator details

INDICATOR

STATUS

DEFINITION

Status (S)

Off


Green Blinking


Green


Yellow

In Protect, Properly Provisioned as EPS

Red

Card Fail

Red Blinking

Card Mismatch

Table 141

P32E1DS1 card front panel connector details

CONNECTOR

TYPE

FUNCTION

I/O (16-1)



I/O (32-17)



1015

Release 7.0.0 3DB 19383 ACAA Issue 01 P32E1DS1 PDH card unit data sheet

39.5


Functional overview In the transmit direction, the P32E1DS1 receives up to thirty-two DS1/E1 signals from the customer interfaces. Encapsulates the data flows into standard Ethernet packets, (IWF). The Ethernet packets are sent to the cross-connections matrix for connection to their provisioned destinations. In the receive direction, the P32E1DS1 receives Ethernet packets from the crossconnections matrix from their provisioned sources. Extracts the data flows from standard Ethernet packets (IWF). The signals are sent to up to thirty-two customer interfaces.

1016



40 P2E3DS3 DS3 PDH card unit data sheet Table 142

P2E3DS3 DS3 PDH card


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB18194AB

P2E3DS3 DS3 PDH Card

N/A

N/A

N/A

Inactive

3DB18194AC

P2E3DS3 DS3 PDH Card

CRG2AA9DAA

167528

070SN E

Active

40.1

Description In the TX direction, the DS3 PDH card (DS3 Access) processes and encapsulates up to 2 DS3 input lines into an Ethernet packets that are sent to the Core cards. In the RX direction, the DS3 Access card extracts data from the Ethernet data packets and processes the data to provide up to 2 DS3 output lines. The 2xE3DS3 Local Access Module performs the following macro functions: •

Termination of 2 DS3 signals (2 DS3 bi-directional interfaces according ITUT G.703 on the front panel)

•

Framed DS3 bi-directional alarm management

•

Bi-directional Performance Monitoring on Framed DS3

•


•

Reconstruction of the original PDH Timing meeting G823/824.

•


•

Sending/getting those standard Eth packets to the Core cards

•


The module communicates with the Core modules through two GbEth Serial copper bi-directional interfaces on the backplane.

1017

Release 7.0.0 3DB 19383 ACAA Issue 01 P2E3DS3 DS3 PDH card unit data sheet

40.2

40.3



Terminates up to two DS3 signals.

•

Framed DS3 Bi-Directional alarm management

•

Bi-Directional performance monitoring on framed DS3 signals

•

Encapsulation of DS3 data flows into standard Ethernet packets Inter Working Function (IWF)

•

Extraction of DS3 data flows from standard Ethernet packets IWF

•


•

MSS-8 shelf supports up to six unprotected P2E3DS3 cards and up to three P2E3DS3 protected pairs

Description The P2E3DS3 card provides 2 DS3 interfaces. The MSS-8 shelf supports up to six P2E3DS3 cards or 12 unprotected DS3 interfaces or 6 protected DS3 interfaces. The P2E3DS3 is supported in MSS-8 slots 3 through 8 for unprotected radio configurations. In protected radio configurations, a pair of P2E3DS3s are required. The main P2E3DS3s are equipped in slots 3, 5, and/or 7 and the protect (spare) P2E3DS3s are equipped in the slots directly across from the main (slots 4, 6, and/or 8). The protect (spare) P2E3DS3 card protects the radio if the main P3E3DS3 fails.

40.4

Indicators, connectors, and control The P2E3DS3 DS3 PDH card has the following indicator and connectors. See Figure 499 for P2E3DS3 DS3 PDH card front panel indicator and connectors. See Table 143 for P2E3DS3 DS3 PDH card indicators details. See Table 144 for P2E3DS3 DS3 PDH card connector details. The P2E3DS3 DS3 PDH card has no controls located on the card.

1018



Figure 499

P2E3DS3 DS3 card (MSS/DS3) front panel view

Table 143

P2E3DS3 DS3 card front panel indicator details

INDICATOR

STATUS

DEFINITION

Status (S)

Off


Green Blinking


Green


Yellow


Red

Card Fail

Red Blinking

Card Mismatch

Table 144


CONNECTOR

TYPE

FUNCTION

LINE 1

75 ohm male, mini-BNC - Qty 2

IN - DS3 Rx interconnect OUT - DS3 Tx interconnect

LINE 2

75 ohm male, mini-BNC - Qty 2

IN - DS3 Rx interconnect OUT - DS3 Tx interconnect

1019

Release 7.0.0 3DB 19383 ACAA Issue 01 P2E3DS3 DS3 PDH card unit data sheet

40.5


Functional overview In the transmit direction, the P2E3DS3 receives DS3 signals from the customer interfaces. Encapsulates the DS3 data flows into standard Ethernet packets, (IWF). The Ethernet packets are sent to the cross-connections matrix for connection to their provisioned destinations. In the receive direction, the P2E3DS3 receives Ethernet packets from the crossconnections matrix from their provisioned sources. Extracts the DS3 data flows from standard Ethernet packets (IWF). The DS3 signals are sent to the customer interfaces.

1020



41 SDH card unit data sheet Table 145

SDHACC STM-1/OC-3 SDH card and SDH accessories


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB18735AA

SDHACC SDH Card

N/A

N/A

N/A

Active

1AB194670005/ 3CC50166AA

STM-1/OC-3 SFP, 850 nm

N/A

N/A

N/A

Active

1AB194670007/ 3CC50165AA

STM-1/OC-3 SFP, 1310 nm

N/A

N/A

N/A

Active

1AB210170001

SFP plug-in STM-1 Copper

N/A

N/A

N/A

Active

3EM09257AA

Fiber Management Panel for STM-1/OC-3, Ethernet fiber storage

N/A

N/A

N/A

Active

Optical splitters for STM-1 signal and EoSDH (SFP for Core unit) 1AB123320022

Multi-Mode, SC, optical 50/50 fiber coupler unit

N/A

N/A

N/A

Active

1AB123320023

Single-Mode, SC, optical 50/50 fiber coupler unit

N/A

N/A

N/A

Active

3CC52062AAAA

SC-SC to LC Splitter (L = 4 m) Single mode 1310 mm

N/A

N/A

N/A

Active

3CC52030AAAA

LC-LC Output to FC Input Splitter (L = 4 m) Single mode 1310 mm

N/A

N/A

N/A

Active

3CC52035AAAA

LC-LC Output to SC Input Splitter (L = 4 m) Single mode 1310 mm

N/A

N/A

N/A

Active

3CC52018AAAA

LC-LC Output to LC Input Splitter (L = 0.4 m) Single mode 1310 mm

N/A

N/A

N/A

Active

3CC52040AAAA

LC-LC Output to LC Input Splitter (L = 2 m) Single mode 1310 mm

N/A

N/A

N/A

Active

1021

Release 7.0.0 3DB 19383 ACAA Issue 01 SDH card unit data sheet

Table 145


SDHACC STM-1/OC-3 SDH card and SDH accessories (Continued)


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3CC52043AAAA

LC-LC Output to ST Input Splitter (L = 4 m) Single mode 1310 mm

N/A

N/A

N/A

Active

1AB405480001

LC-LC Output to LC Input Splitter (L = 1 m) Single mode 1310 mm and 1550 mm

N/A

N/A

N/A

Active

41.1

Description The SDH card provides 2 OC-3/STM-1 interfaces. The MSS-8 shelf supports up to six SDHACC cards or 12 unprotected interfaces or 6 protected interfaces. In the ETSI market the card can be provisioned as SDHACC for transparent mode operation or SDHCHAN for channelized mode operation. In the ANSI market only transparent mode (SDHACC) is available. The SDH card is supported in MSS-8 slots 3 through 8 for unprotected radio configurations. In protected radio configurations, a pair of SDH cards are required. The main SDH cards are equipped in slots 3, 5, and/or 7 and the protect (spare) SDH cards are equipped in the slots directly across from the main (slots 4, 6, and/or 8). The protect (spare) SDH card protects the radio if the main SDH card fails. This unit can manage up to 2xOC-3 by installing two optional STM-1/OC-3 SFP plugins (electrical or optical). In the ETSI market 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 provisioning the unit as SDHCHAN and the STM-1 transparent mode is available by provisioning the unit as SDHACC. The STM-1 unit can support 1 channelized STM-1 or up to 2 transparent STM-1/OC3 interfaces. In the ANSI market only transparent mode is available.

1022



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. 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 OC-3 units must be installed. Clock source from the incoming OC-3 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 OC-3 Local Access unit processes and encapsulates up to 2xOC-3 input lines into an Ethernet packet that is sent to the Core cards. In the Rx direction, the OC-3 Local Access unit extracts data from the Ethernet data packets and processes the data to provide up to 2 OC-3 output lines. •

The 2xOC-3 Local Access Unit performs the following macro functions:

•

Transparent or channelized transport of the OC-3

•

Encapsulation/Extraction of the OC-3 into/from standard Ethernet packets Inter Working Function

•

Reconstruction of the original OC-3 Timing

•


•

Sending/getting those std Eth packets to the Core card

•


The unit communicates with the Core cards through two GbEth Serial copper bidirectional interfaces on the backplane.

41.2


Terminates up to two OC-3 signals.

1023


1024


•

Framed OC-3 Bi-Directional alarm management

•

Encapsulation of OC-3 data flows into standard Ethernet packets Inter Working Function (IWF)

•

Extraction of OC-3 data flows from standard Ethernet packets IWF

•


•

MSS-4/8 shelf supports up to six unprotected SDH cards and up to three SDH card protected pairs


41.3


Indicators, connectors, and control The SDH card has the following indicator and connectors. See Figure 500 for SDH card front panel indicator and connectors. See Table 146 for SDH card indicators details. See Table 147 for SDH card connector details. The SDH card has no controls located on the card.

Figure 500

SDH card (MSS/SDH (OC-3/STM-1)) front panel view

Table 146

SDH card front panel indicator details

INDICATOR

STATUS

DEFINITION

Status (S)

Off


Green Blinking


Green


Yellow


Red

Card Fail

Red Blinking

Card Mismatch

Table 147

SDH card front panel connector details

CONNECTOR

TYPE

FUNCTION

SFP Port 1-2

SFP

STM-1/OC-3 electrical/optical port

1025


41.4


Functional overview In the transmit direction, the SDH card receives OC-3 signals from the customer interfaces. Encapsulates the OC-3 data flows into standard Ethernet packets, (IWF). The Ethernet packets are sent to the cross-connections matrix for connection to their provisioned destinations. In the receive direction, the SDH card receives Ethernet packets from the crossconnections matrix from their provisioned sources. Extracts the OC-3 data flows from standard Ethernet packets (IWF). The OC-3 signals are sent to the customer interfaces.

1026



42 P8ETH Ethernet access switch card unit data sheet Table 148

P8ETH Ethernet access switch card


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB18206AC

P8ETH Ethernet Access Switch Card

CRCCACGJAA

169403

070UPD

Active

42.1

42.2


Terminates up to four GigE optical Ethernet SFP interfaces

•

Terminates up to four 10/100/1000 10BaseT Ethernet interfaces

•

Terminates up to four MPT-HL Transceiver cards

•

Supports one MPT-HL L2 Radio LAG port

•

Supports up to four L1 Radio LAG ports

•

Terminates up to four MPT-HC/HC-HQAM/XP/XP-HQAM units

•

Supports both unprotected and 1+1 EPS protected configurations with MPTHL

•

Supports unprotected configurations with MPT-HC/HC-HQAM/XP/XPHQAM

Description The P8ETH card provides four 10/100/1000 BaseT Ethernet interfaces and four GigE optical Ethernet SFP interfaces. The MSS-8 shelf supports up to three stacked pairs of P8ETH cards. The MSS-4 shelf supports one stacked pair of P8ETH cards. With card stacking, traffic between the two cards goes directly from one card to the other across the backplane, not through the Core card. Traffic is not affected if a Core switch occurs. The P8ETH is supported in MSS-8 slots 3 through 8 for unprotected radio configurations. In protected radio configurations, a pair of P8ETHs are required.

1027

Release 7.0.0 3DB 19383 ACAA Issue 01 P8ETH Ethernet access switch card unit data sheet


The P8ETH is supported in MSS-4 slots 3 and 4 for unprotected radio configurations. In protected radio configurations, a pair of P8ETHs are required.

42.3

Indicators, connectors, and control The P8ETH card has the following indicators, connectors, and controls. See Figure 501 for P8ETH card front panel indicator and connector locations. See Table 149 for P8ETH card indicators details. See Table 150 for P8ETH card connector details.

Figure 501

P8ETH card (MSS/P8ETH)

Table 149

P8ETH front panel indicator details

INDICATOR

STATUS

DEFINITION

Status (S)

Off


Green Blinking

Download, Software Booting, or Flash Card Realignment in Process

Green

In-Service, Normal Operation, and Properly Provisioned

Yellow


Red

Card Fail

Red Blinking

Card Mismatch

Off

Link Down

On

Link Up

Link

1028


Table 149


P8ETH front panel indicator details (Continued)

INDICATOR

STATUS

DEFINITION

Activity

Off

No Tx/Rx activity

Blinking

Tx/Rx activity

Table 150

P8ETH front panel connector details

CONNECTOR

TYPE

FUNCTION

Ethernet Ports 1-4

RJ45

10/100/1000BaseT Ethernet Port

SFP Ports 5-8

SFP


1029

Release 7.0.0 3DB 19383 ACAA Issue 01 P8ETH Ethernet access switch card unit data sheet

42.4


Functional overview The main purpose of the Ethernet Access Switch (P8ETH) module is to provide the MSS-to-MPT interface for the 9500 MPR all indoor configuration. The P8ETH module functions as a layer 2 switch, cross-connecting VLAN tagged Ethernet data to/from the addressed MPT. The P8ETH module provides traffic management for Cores for up to four directions using protected radios and up to eight directions using not-protected radios. A secondary purpose of the P8ETH module is to provide four RJ45 10/100/ 1000Base-T Ethernet ports, in addition to the four Core Ethernet ports, and four SFP optical Ethernet ports, in addition to the Core SFP optical Ethernet port.

1030



43 EASv2 Ethernet access switch card unit data sheet Table 151

UDS-128 EASv2 Ethernet access switch card


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB19017AB

EASv2 Card

CRG2AKKDAA

N/A

N/A

Active

43.1


Terminates up to four optical Ethernet SFP interfaces

•

Terminates up to four 10/100/1000 10BaseT Ethernet interfaces

•

Terminates up to eight of the following MPT types: −

MPT-HL Transceiver cards

−

MPT-HLC Transceiver cards

−

MPT ODU

•

Supports one MPT-HL L2 Radio LAG port

•

Supports up to four L1 Radio LAG ports

•


See the 9500 MPR Technical Specifications for Split Mount Applications for technical information.

43.2

Description The EASv2 card provides four PFoE-capable 10/100/1000 BaseT Ethernet interfaces and four optical Ethernet SFP interfaces. The MSS-8 shelf supports up to three stacked pairs of EASv2 cards. The MSS-4 shelf supports one stacked pair of EASv2 cards. With card stacking, traffic between the two cards goes directly from one card to the other across the backplane, not through the Core card. Traffic is not affected if a Core switch occurs. The EASv2 is supported in MSS-8 slots 3 through 8 for unprotected radio configurations. In protected radio configurations, a pair of EASv2s are required.

1031

Release 7.0.0 3DB 19383 ACAA Issue 01 EASv2 Ethernet access switch card unit data sheet


The EASv2 is supported in MSS-4 slots 3 and 4 for unprotected radio configurations. In protected radio configurations, a pair of EASv2s are required. The dimensions of the EASv2 card are:

43.3

•

Height: 20 mm (0.5U)

•

Width: 170 mm

•

Depth: 225 mm

•

Maximum thickness: 1.73 mm ± 10% overplating

Indicators, connectors, and control The following are the connectors on the front panel of the EASv2: •

4 RJ-45 connectors (PFoE): These connectors provide Ethernet links with a maximum autonegotiation capability of 2.5 Gb/s (with the compatible backplane) and provide power to the ODU

•

4 Ethernet optical interfaces (SFP standard), connected to the FPGA.

Figure 502 shows EASv2 card front panel indicator and connector locations. Figure 502

EASv2 card (MSS/EASv2)

Table 152 provides EASv2 card indicators details.

1032


Table 152


EASv2 front panel indicator details

INDICATOR

STATUS

DEFINITION

Status (S)

Off


Green Blinking


Green


Yellow


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

Table 153 provides EASv2 card connector details. Table 153

EASv2 front panel connector details

Port

Interface type

Function

MPT ODU port 1

1

RJ45

10/100/1000BaseT Ethernet Port with PFoE

X

2

RJ45


X

3

RJ45


X1

4

RJ45


X

5

SFP


X except MPT-MC

MPT-HL/MPT-HLC port

X

1033

Release 7.0.0 3DB 19383 ACAA Issue 01 EASv2 Ethernet access switch card unit data sheet

Table 153


EASv2 front panel connector details (Continued)

Port

Interface type

Function

MPT ODU port 1

MPT-HL/MPT-HLC port

6

SFP


X except MPT-MC

X

7

SFP


X except MPT-MC

X

8

SFP


X except MPT-MC

X

1. An MPT Extended Power Unit is required to connect an MPT-XP/XP-HQAM to all RJ45 (electrical) ports. 2. Power must be provided to MPT units connected to SFP (optical) ports. Power can be supplied to an MPT-HC/HC-HQAM by a power injector device (Power Injector Card/Box, MPT Power Unit, MPT Extended Power Unit), or by electrical PFoE ports on the EASv2 card (if the EASv2 electrical PFoE ports are not in use as data ports). An MPT Extended Power Unit is required to connect an MPT-XP/XP-HQAM to these ports. The main purpose of the Ethernet Access Switch, version 2 (EASv2) module is to provide the MSS-to-MPT interface for the 9500 MPR configuration. The EASv2 module functions as a layer 2 switch, cross-connecting VLAN tagged Ethernet data to/from the addressed MPT. The EASv2 module provides traffic management for Core cards for up to four directions using protected radios and up to eight directions using not-protected radios. A secondary purpose of the EASv2 module is to provide four RJ45 10/100/ 1000Base-T Ethernet ports with PFoE, in addition to the four Core Ethernet ports, and four SFP optical Ethernet ports, in addition to the Core SFP optical Ethernet port.

1034



44 MPTACC MPT access card unit data sheet Table 154

MPTACC MPT access card


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB18634AB

MPTACC MPT Access

N/A

N/A

N/A

Active

44.1

Description The MPTACC is an interface for one or two MPT ODUs. This interface is comprised of two components, Ethernet and DC power. The Ethernet interface to the MPT ODU is a standard GbEth interface (electrical or optical). It sends/receives standard Ethernet packets to/from both Core-E or CorEvo modules. It contains the logic for the EPS Core protection. One or two MPT ODU can be connected. The MPTACC is supported in MSS-8 slots 3 through 8 and MSS-4 slots 3 and 4. In unprotected radio configurations the main MPTACC card is supported in any of the supported MSS-4/8 slots, two radio channels per MPTACC card for a maximum of twelve MPT ODU radio channels per MSS-8 shelf and four radio channels per MSS-4 shelf. In protected radio configurations, two arrangements are available. The first arrangement uses one interface on a MPTACC card configured as main and the second interface as spare for a single protected radio channel. This arrangement is supported in MSS-8 slots 3 through 8 and MSS-4 slots 3 and 4. The second arrangement uses a main MPTACC card and a spare MPTACC card. The main MPTACCs are equipped in slots 3, 5, and/or 7 and the protect (spare) MPTACCs are equipped in the slots directly across from the main (slots 4, 6, and/or 8). The MPTACC card can be equipped with GigE SFP as required to meet system requirements. The MPTACC card supports one MPT ODU L2 Radio LAG port. The MPTACC card provides four GigE ports, two electrical (ports 1 and 2) and two optical SFP (ports 3 and 4). Only two GigE ports are supported simultaneously, either two electrical, two optical, or one electrical and one optical.

1035

Release 7.0.0 3DB 19383 ACAA Issue 01 MPTACC MPT access card unit data sheet


Either electrical port #1 or optical port #3 can be enabled and is associated with power supply port #1. Either electrical port #2 or optical port #4 can be enabled and is associated with power supply port #2. In the TX direction, the MPTACC card receives Ethernet packets from the Core cards and outputs the Ethernet packets towards the MPT ODU. In the RX direction, the MPTACC card receives Ethernet packets from the MPT ODU and sends the packets to the Core cards.

44.1.1

Main functions •

Provide the power supply interface and the Ethernet interface

•

Provide the Power Feed over Ethernet function

•

Lightning and surge protection

•


•

EPS/HSB management function

•


•

L2 packet based Proprietary clock algorithm

•


•

Radio Link Quality notification through MPR Protection Protocol frames

•

Communication with Core controller for provisioning and status report.

According to the IEC 60825-1 the explanatory label is not included on the equipment due to the lack of space.

44.2

1036


Provide traffic interface between Core switch and up to two MPT ODUs

•

Simplified interconnection with MPT ODU using PFoE function (Ethernet traffic and power supply on the same cable)

•

Supports both unprotected and 1+1 EPS/HSB protected configurations

•

Supports one MPT ODU L2 Radio LAG port

•

MPT ODU EPS/HSB management function

•



44.3


•

L2 packet based Proprietary clock algorithm

•


•

Radio Link Quality notification through MPR Protection Protocol frames

•

Communication with Core controller for provisioning and status report.

•

Provide the power supply interface to the MPT ODU, except XP variants.

•

Lightning and surge protection for both electrical GbEth and power interfaces that are connected to MPT ODU

•


Indicators, connectors, and control See Figure 503 for MPTACC card front panel indicator and connectors. See Table 155 for MPTACC card indicators details. See Table 156 for MPTACC card connector details. The MPTACC card has no controls located on the card.

Figure 503

MPTACC card (MSS/MPTACC)

1037


Table 155


MPTACC front panel indicator details

INDICATOR

STATUS

DEFINITION

Power Emission Status (M)

Off

No Output Power (for example: Hot-Standby Transmitter, Software is Booting, or FPGA Downloading is InProgress)

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


Green Blinking


Green

In Service, Normal Operation, and Properly Provisioned 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

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

Status (S)

LINK

ACTIVITY

The GREEN and YELLOW colors of the Card Status LED have different meaning, if two MPT ODUs are connected: •

MPT ODU in 1+0 not protected is provisioned: −

•

1 MPT ODU in 1+1 EPS protection is provisioned, with mated MPT ODU provisioned on another MPT Access card: −

1038

YELLOW color is not applicable (traffic effect if MPT Access card is unplugged)

GREEN if provisioned MPT ODU is EPS Active



− •

1 MPT ODU in 1+1 EPS protection is provisioned, with mated MPT ODU provisioned on another MPT Access card, 1 MPT in 1+0 is provisioned on same MPT ODU Access card: −

•

•

YELLOW if provisioned MPT ODU is EPS Standby (no traffic effect if MPT Access card is unplugged)

YELLOW color is not applicable (traffic effect if peripheral is unplugged)

2 MPT ODUs in 1+1 EPS protection are provisioned, with mated MPT ODU provisioned on a different MPT Access card: −

GREEN if at least one of provisioned MPT ODU is EPS Active

−

YELLOW if both MPT ODUs are EPS Standby (no traffic effect if MPT Access is unplugged)

2 MPT ODUs in 1+1 EPS protection on the same MPT Access card are provisioned: −

YELLOW color is not applicable (traffic effect if peripheral is unplugged)

Warning: The optional SFP plug-in, which may be installed in the MPT Access card, contains a Class 1 laser source. The laser source is placed in the left side of the SFP plug-in.

Table 156

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

1039


1040




45 AUX auxiliary card unit data sheet Table 157

AUX auxiliary card


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB18236AB

AUX Auxiliary Card

N/A

N/A

N/A

Active

45.1


45.2

Housekeeping alarm points (six station alarm inputs and seven station control outputs) −

User provisionable alarm labels

−

User provisionable polarity (Active Low/Active High)

•

Hardware support for EOW. EOW is not supported in the current release.

•

Hardware support for two 64 Kb/s, RS422/V.11 DCE co-directional service channels. Service channels are not supported in the current release.

•

One AUX card supported per MSS shelf. In the MSS-4 shelf, AUX card is supported in slot 4 only. In the MSS-8 shelf, AUX card is supported in MSS-8 shelf slot 8 only.

Description The AUX card provides thirteen housekeeping alarm points, six station alarm inputs and seven station control outputs. Housekeeping alarm points support user provisionable alarm labels on a per alarm basis. User provisionable alarm active polarity on a per alarm basis.

45.3

Indicators, connectors, and control The AUX card has the following indicators, connectors, and controls. See Figure 504 for AUX card front panel indicator and connector locations.

1041

Release 7.0.0 3DB 19383 ACAA Issue 01 AUX auxiliary card unit data sheet


See Table 158 for AUX card indicators details. See Table 159 for AUX card connector details. Figure 504

AUX card (MSS/AUX)

Table 158

AUX front panel indicator details

INDICATOR

STATUS

DEFINITION

Status (S)

Off


Green Blinking


Green


Yellow


Red

Card Fail

Red Blinking

Card Mismatch

Off

EOW Line Status LED is not supported in the current release

EOW Line Status (E)

1042


Table 159


AUX front panel connector details

CONNECTOR

TYPE

FUNCTION

Service Channel 1 1

15-Position D-Sub Female

64 Kb/s, RS422/V.11 DCE Co-Directional Service Channel 1

Service Channel 2 1


64 Kb/s, RS422/V.11 DCE Co-Directional Service Channel 2

Housekeeping


Housekeeping Alarm Points: 6 Station Alarm Inputs and 7 Station Control Outputs EOW

EOW 2

1. Service channel 1 and 2 are not supported in the current release. 2. EOW is not supported in the current release.

45.4 45.4.1

Functional overview Housekeeping station alarm inputs The polarity of each input housekeeping alarm input is configurable using the ECT/ NMS. When the active state of an alarm input is configured high (open contact) the voltage on the input is high. When the active state of an alarm input is configured low (closed contact) the voltage on the input is low. The default value is low (closed contact). The polling rate of the input alarms is 1 second, no latch of input state is performed.

1043


Figure 505


Housekeeping alarm polarity

45.4.2

Housekeeping station alarm input electrical characteristics Open Contact: 2V < |V|< 60 V; |I| < 0.2mA Closed Contract: 0V < |V|< 2 V; |I| < 50mA Though the housekeeping equipment requirement on max input voltage is 60 V, the PCB layout of peripheral must be able to manage 72 V. By default the presence of active alarm corresponds to closed relay contact with a common wire available to the customer. By CT/NMS it is possible to change the polarity independently for each alarm (both normally closed and normally open contacts are available on the I/O connector). When the power supply is down (and also when the power supply is on but the SW hasn't yet initialized the HW), all the relays of the outputs of the alarms/housekeeping are in the "open contact" state (HW default condition).

45.4.3

Output alarm electrical characteristics Open Contact: 2V < |V|< 60 V; |I| < 0.2mA Closed Contract: 0V < |V|< 2 V; |I| < 50mA

1044



Though the housekeeping equipment requirement on max input voltage is 60 V, the PCB layout of peripheral must be able to manage 72 V.

45.4.4

Synchronous 64 Kb/s RS422/V.11 DCE codirectional The service channel interface is DCE co-directional definition where it is possible to assume that the timing signals are equal in both the directions: the subordinate equipment (DTE) has to synchronize the output data with the unique timing signal received. The NEs at either end of a service channel must be synchronized to the same Network Element Clock (NEC) in each MSS node.

Figure 506

64 Kb/s service channel DCE co-directional

1045


1046




46 GigE and 10GigE SFP unit data sheet Table 160

GigE and 10GigE SFPs


NAME

CLEI

ECI/ BAR CODE

REMARKS

1AB383760002/ 3CC50168AAAA

SFP plug-in 1000Base-Lx

CRTUAD1FAA

194074

Can be installed in the Core-E card, CorEvo card, EAS card, EASv2 card, MPT Access card, MSS-1, MSS-1c, or MSS-O Can also be installed in the MPT ODU to provide an optical interface The SFP is mandatory for cabled 1+1 configuration with MPT-HC/ MPT-XP.

1AB383760003/ 3CC50170AAAA

SFP plug-in 1000Base-Zx

CRTUAD0FAA

194072

Can be installed in the Core-E card, EAS card, EASv2 card, MPT Access card, MSS-1, or MSS-O

1AB359780002/ 3CC50169AAAA

SFP plug-in 1000Base-T (Copper Transceiver)

N/A

N/A

Can be installed in the Core-E card, CorEvo card, EAS card, EASv2 card, MSS-1, MSS-1c, or MPT Access card

3CC50183AAAA (1310nm) 3CC50184AAAA (1550nm)

SFP 1000Base-BX20

N/A

N/A

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

1047

Release 7.0.0 3DB 19383 ACAA Issue 01 GigE and 10GigE SFP unit data sheet

Table 160


GigE and 10GigE SFPs (Continued)


NAME

CLEI

ECI/ BAR CODE

REMARKS

3CC50198AAAA (1310nm) 3CC50199AAAA (1550nm)

SFP 1000Base-BX40

N/A

N/A

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

3DB78012AAAA

SFP 2xE1

N/A

N/A

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

1AB380750004

SFP E3

N/A

N/A

Can be installed in the Core-E card or MSS-1 The E3 SFP is not supported for E3 traffic passing through an L1 LAG link.

1AB380750003

SFP S1.1 GE over STM-1

N/A

N/A

Can be installed in the Core-E card

1AB380750003

EOSDH SFP

N/A

N/A

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

3CC50201AGAA

CWDM-SFP-1470

N/A

N/A

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

3CC50200AAAA

CWDM-SFP-1490

N/A

N/A


3CC50201ABAA

CWDM-SFP-1510

N/A

N/A


1048


Table 160




NAME

CLEI

ECI/ BAR CODE

REMARKS

3CC50201ACAA

CWDM-SFP-1530

N/A

N/A


3CC50201AAAA

CWDM-SFP-1550

N/A

N/A

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

3CC50201ADAA

CWDM-SFP-1570

N/A

N/A


3CC50201AEAA

CWDM-SFP-1590

N/A

N/A


3CC50201AFAA

CWDM-SFP-1610

N/A

N/A


3EM20277AA

GigE SFP 1000BaseSX, 850 nm

DRR3AA3CAA

147527

Active

1AB 38376 0001/ 3CC50167AA

SFP 1000Base-SX

N/A

N/A

Optical SFP module to be installed optionally in the MPT-HC/XP/HCHQAM/XP-HQAM/ 9558HC to provide the optical Gigabit Ethernet interface

3DB80628AC

Copper SFP (3 meter sim.) MSS - TRs lower

N/A

N/A

For MPT-HLS

1049


Table 160




NAME

CLEI

ECI/ BAR CODE

REMARKS

3EM20277AB

GigE SFP 1000BaseLX, 1310 nm

DRR3AA4CAA

147539

—

3EM20277AC

GigE SFP 1000BaseEX, 1310 nm

DRR3AA5CAA

147542

—

3EM20277AD

GigE SFP 1000BaseZX, 1550 nm

DRR3AA6CAA

147544

—

1AB123320022

Multi-Mode, SC, optical 50/50 fiber coupler unit for Core card GigE SFP port protection

N/A

N/A

—

1AB123320023

Single-Mode, SC, optical 50/50 fiber coupler unit for Core card GigE SFP port protection

N/A

N/A

—

3AL82027AAAA

10 GB/s SFP 10GBase-SR

CRTUADXFAA

193815

—

3AL82026AAAA

10 GB/s SFP 10GBase-LR

CRTUADWFA A

193808

—

1AB187280040

SFP 1000Base-Lx

To be installed in the Ethernet user port 3 or 4 of the (optional)

—

1AB383760001

SFP 1000Base-Sx

To be installed in the Ethernet user port 3 or 4 (optional)

—

3AL81424AA

SFP removal tool

N/A

MSS-1c SFPs

1050

N/A

—


46.1

46.2



Is an in-service pluggable optical card

•

A GigE SFP provides a 1.25 Gb/s Gigabit Ethernet (GigE) interface for Control and Switching Module (Core-E or CorEvo) or Ethernet Access Switch Card (P8ETH).

•

A 10GigE SFP provides a or 10 Gb/s interface for a CorEvo-10G card, if a license is present. The SFP can be inserted in port 5 or 6 of a CorEvo-10G card.

•

Available in the following optical reaches −

1000Base-SX, 850 nm (up to 550 meter applications)

−

1000Base-LX, 1310 nm (up to 10 kilometer applications)

−

1000Base-EX, 1310 nm (up to 40 kilometer applications)

−

1000Base-ZX, 1550 nm (up to 80 kilometer applications)

•

Provides a duplex LC connector

•

Is compliant with SFP Multi-Service Agreement (MSA)

Description The GigE SFP is installed in one slot of a Core-E, CorEvo, or EAS card. Provides a 1.25 Gb/s; 1000Base-SX 850 nm, 1000Base-LX 1310 nm, 1000Base-EX 1310 nm, or 1000Base-ZX 1550 nm GigE interface and a duplex LC connector. See Figure 507 for an illustration of the GigE SFP.

1051


Figure 507


Optical SFP module

46.3

Indicators, connectors, and control The GigE SFPs have the following indicators and connector. See Table 161 for GigE SFP indicators details. See Table 162 for GigE SFP connector details. The GigE SFP has no controls located on the assembly.

Table 161

SFP indicator details

INDICATOR

STATUS

DEFINITION

LINK

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

ACTIVITY

1052


Table 162


SFP connector details

CONNECTOR

TYPE

FUNCTION

DUPLEX OPTICAL CONNECTOR

LC

Tx and Rx GigE ports

46.4

Functional overview The SFP interfaces with the card through a 2.5 Gb/s data signal line. All timing, control, and power are provided by the unit in which it is housed (see the Unit Data Sheet for information). On the transmitter side, the SFPs has an automatic optical output power control circuit, a laser driver and a laser diode module. The transmitter is based on a noncooled DFB laser. The laser safety class for the complete integrated module is class 1 according to IEC 60825. It can manage commands for TX disable and provides a TX fault alarm. TX fault indicates a laser fault. The transmitter is not disabled when the TX fault signal is active. TX disable is an input that is used to shut down the transmitter optical output. On the receiver side, the SFPs have a PIN photo detector for light-to-electrical current conversion and a limiting amplifier. The photo-detected current is amplified by an electrical circuit that delivers two complementary data signals. The module provides LOS alarm (loss of input power signal alarm). This output signal indicates the received optical power is below the worst-case receiver sensitivity (as defined by the standard in use). The transceiver has an EEPROM to provide Remote Inventory RI information. DDM supports analog parameter measurements such as temperature, laser bias, and laser power.

1053


1054




47 Sync In/Out SFP unit data sheet Table 163

Sync In/Out SFP


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB78017AA

Sync In/Out SFP

N/A

N/A

N/A

Active

47.1

Features and application notes

47.2

•

Is an in-service pluggable optical card

•

Provides a synchronization interface for the CorEvo card and the MSS-1.

•

Provides a reference clock

•

Is compliant with SFP Multi-Service Agreement (MSA)

Description The CorEvo card and the MSS-1 do not have dedicated Sync ports. The Sync In/Out SFP provides both Sync-In and Sync-Out ports. The SFP can be installed in ports 7 and 8 of a CorEvo, and ports 5 and 6 of an MSS-1.

47.3

Indicators, connectors, and control The Sync In/Out SFP has no indicators or controls located on the assembly. See Table 164 for Sync In/Out SFP pinout details. Table 164

Sync In/Out SFP pinout details

PIN

DEFINITION

PIN

DEFINITION

1

GND

11

Not connected

2

TX Clock

12

Not connected

1055

Release 7.0.0 3DB 19383 ACAA Issue 01 Sync In/Out SFP unit data sheet

Table 164

47.4


Sync In/Out SFP pinout details (Continued)

PIN

DEFINITION

PIN

DEFINITION

3

TX Clock Disable

13

Not connected

4

I2C Data

14

Not connected

5

I2C Clock

15

Vcc

6

Presence

16

Vcc

7

Card Fail

17

Not connected

8

RX Clock

18

Not connected

9

Not Connected

19

Not connected

10

Not Connected

20

Not connected

Functional overview With the Sync In/Out SFP installed, the unit can provide a reference clock according to any of the following options: •

2.048 MHz, electrical levels according to G.703, clause 13

•

5 MHz, + 6 dBm ± 1.5 dBm into 50 ohm, sine-wave

•

10 MHz, + 6 dBm ± 1.5 dBm into 50 ohm, sine-wave

•

1.024 MHz, electrical levels according to G.703, clause 13 with the following exception: −

timing scaled from 2.048 MHz to 1.024 MHz

The ingress and egress ports can be configured separately: Sync-In can be configured differently from Sync-Out. For configuration procedures, see the 9500 MPR WebEML User Manual. EPS protection is available in a CorEvo protection configuration using an optical splitter cable. During a CorEvo protection switch, the active card mutes its Sync-Out ports and the standby card enables its Sync-Out ports. Figure 508 shows the Sync In/Out SFP.

1056


Figure 508


Sync In/Out SFP

1057

Release 7.0.0 3DB 19383 ACAA Issue 01 Sync In/Out SFP unit data sheet

1058



3 dB hybrid splitter unit data sheet

48 3 dB hybrid splitter unit data sheet Table 165

3 dB hybrid splitter


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3EM22900AA

DS3 Hybrid Splitter

N/A

N/A

N/A

Active

3EM24462AA

DS3 Hybrid Splitter Grooming Panel Kit Hybrid Splitter Grooming Panel provides mounting location for up to 6 input/ output pairs to manage multiple hybrid splitters.

N/A

N/A

N/A

Active

48.1

Description External 3 dB hybrid splitter used to interconnect protected DS3 signals.

Figure 509

Hybrid splitter interconnect

1059

Release 7.0.0 3DB 19383 ACAA Issue 01 3 dB hybrid splitter unit data sheet

48.2


Connectors See Table 166 for DS3 Hybrid Splitter connector details.

Table 166

Hybrid splitter connector detail

CONNECTOR

TYPE

FUNCTION

Customer Interconnect

75 ohm BNC, Female

Protected DS3 customer interconnect, input and output.

P2E3DS3 Card Interconnect

75 ohm male, mini-BNC

Protected DS3 P2E3DS3 Card interconnect, input and output.

1060



49 Coupler and OMT unit data sheet This chapter provides information about the MPT ODU couplers, ortho mode transducers, OMT-Cs, and loads for unused ports. The following tables provide part number information. See the following for additional information: •


•

9500 MPR Technical Specifications for Split Mount Applications for technical specifications

•


•


•


•

Microwave packet transport outdoor unit (MPT ODU) unit data sheet for information about MPT ODUs

See Table 167 for brief descriptions of MPT ODU couplers. See Table 168 for MPT ODU and coupler pole mounts. See Table 169 for MPT-HC/XP/HC-HQAM/XP-HQAM/9558HC 2x(1+0) XPIC couplers. See Table 170 for MPT-HC/XP/HC-HQAM/XP-HQAM/9558HC 4x(1+0) XPIC couplers. See Table 171 for OMTs. See Table 172 for OMT-Cs. See Table 173 for loads for couplers, OMTs, and OMT-Cs. Table 167

MPT ODU couplers

Description

Part number

5.7-7.1 GHz Band 3 dB coupler

3CC58276AC

5.7-7.1 GHz Band 1 dB/10 dB coupler

3CC58276AD

5.8 GHz Unlicensed Band 1 dB/10 dB coupler

3CC58276AB

1061

Release 7.0.0 3DB 19383 ACAA Issue 01 Coupler and OMT unit data sheet

Table 167


MPT ODU couplers (Continued)

Description

Part number

6 GHz 1 dB/10 dB coupler

3CC58056ABXX 3CC58056AD

6 GHz 3 dB coupler

3CC58056AAXX 3CC58056AC

7.1-8.5 GHz 1 dB/10 dB coupler

3CC14536AAXX

7.1-8.5 GHz 3 dB coupler MPT

3CC14536ABXX

10-11.7GHz 3dB coupler

3CC58224AAXX 3CC58224AB

10-11.7GHz 1 dB/10 dB coupler

3CC58226AAXX 3CC58226AB

10.7-11.7 GHz 3 dB coupler

3CC14140AAXX 3CC14140AA

10.7-11.7GHz GHz 1 dB/10 dB coupler

3CC14140ABXX

11 GHz Band 1 dB/10 dB coupler

3CC14140AD

13-15 GHz 1 dB/10 dB coupler

3CC13472ABXX 3CC13472AB

13-15 GHz 3 dB coupler

3CC13472AAXX 3CC13472AA

18-23-25 GHz 1 dB/10 dB coupler

3CC13473ABXX

18-23-25 GHz 3 dB coupler MPT

3CC13473AAXX

18/25 GHz Band 3 dB coupler

3CC13473AC

18/25 GHz Band 1 dB/10 dB coupler

3CC13473AD

28-38 GHz 1 dB/10 dB coupler

3CC13474ABXX 3CC13474AD

28-38 GHz 3 dB coupler

3CC13474AAXX 3CC13474AC

1062


Table 168


MPT ODU and coupler pole mounts

Description

Part number

Pole mount assembly for integrated antenna configuration

3CC06071AA 3CC10752AB

Pole mount assembly for not-integrated antenna configuration

3CC13034AA 3DB10137AA

Table 169

MPT-HC/XP/HC-HQAM/XP-HQAM/9558HC 2x(1+0) XPIC Coupler (horizontal and vertical)

Description

Part number

L6 GHz Band XPIC Coupler

3CC58134AA

U6 GHz Band XPIC Coupler

3CC58186AA

7 GHz Band XPIC Coupler

3CC58124AA


3CC58133AA

11 GHz Band XPIC Coupler (The 11 GHz band is MPT-HC only)

3CC58161AA


3CC58163AA


3CC58164AA


3CC58165AA

Table 170

MPT-HC/XP/HC-HQAM/XP-HQAM/9558HC 4x(1+0) XPIC Coupler (2 horizontal and 2 vertical)

Description

Part number

L6 GHz Band 4 ODU OMT-C XPIC Coupler

3CC58244AA

U6 GHz Band 4 ODU OMT-C XPIC Coupler

3CC58266AA

7/8 GHz Band 4 ODU OMT-C XPIC Coupler

3CC58268AA

11 GHz Band 4 ODU OMT-C XPIC Coupler (The 11 GHz band is MPT-HC only)

3CC58200AA

13 GHz Band 4 ODU OMT-C XPIC Coupler

3CC58245AA


3CC58246AA

1063


Table 170


MPT-HC/XP/HC-HQAM/XP-HQAM/9558HC 4x(1+0) XPIC Coupler (2 horizontal and 2 vertical) (Continued)

Description

Part number


3CC58201AA


3CC58202AA

Table 171

OMTs

Description

Part number

OMT 6 GHz L

3CC58134AAXX

OMT 6 GHz U

3CC58186AAXX

OMT 7 GHz

3CC58124AAXX

OMT 8 GHz

3CC58133AAXX

OMT 10-11 GHz This is the only OMT compatible with the MPT-HC-HQAM/ XP-HQAM.

3CC58229AAXX

OMT 11 GHz

3CC58161AAXX

OMT 13 GHz

3CC58162AAXX

OMT 15 GHz

3CC58163AAXX

OMT 18 GHz

3CC58164AAXX

OMT 23 GHz

3CC58165AAXX

Table 172

OMT-C

Description

Part number

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

1064


Table 172


OMT-C (Continued)

Description

Part number

OMT-C 18 GHz

3CC58201AAXX

OMT-C 23 GHz

3CC58202AAXX

Table 173

Loads for couplers, OMTs and OMT-Cs

Description

Part number

WR28 Load (38 GHz)

3CC58220AAXX

WR42 Load (18-25 GHz)

3CC58221AAXX


3CC58228AAXX

WR75 Load (11 GHz)

3CC58223AAXX


3CC58230AAXX

WR137 Load (6 GHz)

3CC58225AAXX

49.1

Description

49.1.1

Couplers

The coupler allows two MPT ODUs to be installed in the same polarization. The MPT ODUs can mount to the coupler vertically or face to face.

49.1.2

Ortho mode transducer The OMT allows two MPT ODUs to be installed in H and V polarizations. The OMT can only be installed on an integrated antenna.

1065


49.1.3


Ortho mode transducer-coupler

The OMT-C allows up to 4 MPT ODUs to be installed using H and V polarizations. Each MPT ODU is in the opposite polarization to the other MPT ODU on the same side of the OMT-C. The OMT-C can only be installed on an integrated antenna. Figure 510

1066

OMT-C


Figure 511


OMT-C

1067


1068




50 Power injector unit data sheet Table 174

Power injector


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3CC50128AA 3CC50120AAXX

Power Injector Card

N/A

N/A

N/A

Active


Power Injector Box

N/A

N/A

N/A

Active

3DB77008AC 3DB77008ACXX

Power Injector Bracket Bracket to be used to install the Power Injector box in a 19-inch rack.

N/A

N/A

N/A

Active


Kit used with Power Injector bracket to install Power Injector box in a 21 inch rack.

N/A

N/A

N/A

Active

50.1


Allows a single electrical Ethernet cable run between the MSS-1/4/8 shelf and the MPT-MC/HC/HC-HQAM/9558HC Transceiver mounting location.

•

Redundant DC power inputs from -48V battery

•

Low pass filtering

•

Insertion of the DC voltage on two Ethernet streams to power two MPT-MC/ HC/HC-HQAM/9558HCs

•

Surge protection on both Ethernet output ports (K44 & K45)

•

The maximum cable length is 100 m for PFoE applications. With coax cable and fiber for data, the maximum length is 300 m.

1069

Release 7.0.0 3DB 19383 ACAA Issue 01 Power injector unit data sheet

50.2


Description The Power Injector is an indoor device designed to deliver the DC power supply to MPT-MC/HC/HC-HQAM/9558HC by using the same cable carrying the Ethernet traffic. MPT-MC/HC/HC-HQAM/9558HC is powered through an electrical Ethernet cable from the Power Injector. The Power Injector box/Card combines the Ethernet traffic and DC power and sends the output on one connector the Power Supply + Ethernet Traffic. This solution is called PFoE (Power Feed over Ethernet), and is proprietary. Power Injector box is 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 can support two boxes side by side with a height of 1.3 rack increments. Power Injector Card installs in any unused MSS-4/8 shelf slot, powered through MSS-4/MSS-8 shelf backplane connector. The Power Injector can supply up to 2 MPT-MC/HC/HC-HQAM/9558HC. The two Power Supply Sources provide power supply redundancy. The input voltage range is -38.4 to -57.6 Vdc.

50.3 50.3.1

Indicators, connectors, and control Power injector box The Power Injector Box has no controls. The Power Injector Box has two indicators which indicate the presence of DC voltage on their respective Ethernet output. See Figure 512 for Power Injector Box front panel connector locations. See Figure 513 for Power Injector Box and bracket mounted in a rack. See Table 175 for Power Injector box connector details.

1070



Figure 512

Power injector box

Figure 513

Power injector box and bracket

Table 175

Power injector box connector details

CONNECTOR

TYPE

DC Voltage (+ & -)

FUNCTION

Station Battery and Return

Data (MPT1 & MPT2)

RJ-45

Ethernet interconnect

DC+Data (MPT1 & MPT2)

RJ-45

Ethernet and DC power Interconnect with MPT-HC

Station Ground

50.3.2

Chassis ground (located on the Injector Box Bracket)

Power injector card The Power Injector Card has no controls. The Power Injector Card has two indicators which indicate the presence of DC voltage on their respective Ethernet output. See Figure 512 for Power Injector Card front panel connector and indicator locations. See Table 176 for Power Injector box connector details.

1071

Release 7.0.0 3DB 19383 ACAA Issue 01 Power injector unit data sheet


Figure 514

Power injector card

Table 176

Power injector card indicator connector details

CONNECTOR

TYPE

FUNCTION

Data (MPT1 & MPT2)

RJ-45


DC+Data (MPT1 & MPT2)

RJ-45

Ethernet and DC power Interconnect with MPT-HC

1072



51 +24/-48 volt converter unit data sheet Table 177

+24/-48 volt converter


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3DB18862AA

+24/-48 Volt Converter (2 Converters W/Chassis)

N/A

N/A

N/A

Active

3DB18863AA

+24/-48 Volt Converter (1 Converter W/Chassis)

N/A

N/A

N/A

Active

3DB18764AA

+24/-48 Volt Converter (Spare)

N/A

N/A

N/A

Active

51.1

51.2


Converts +24 Vdc office battery voltage to -48 Vdc for +24 Vdc office applications.

•

Supports redundant power configuration

•

Supports MSS-8 shelf applications, up to a maximum of 348 watts including any connected ODUs.

•

+24/-48 Volt Converter card requires the FAN 2U Card W/Alarms (PN 3EM23911AA).

•

Keyed power cables to connect the converter cards to the MSS-8 shelf are included with 3DB18862AA and 3DB18863AA kits.

Description The +24/-48 Volt Converter operates from nominal +24 Vdc office battery input and provides -48 Vdc output to the MSS-8 shelf. Single converter card can be inserted into the converter chassis to support unprotected power configurations. Two converter cards can be inserted into the converter chassis to support redundant power configurations. +24/-48 Volt Converter installs in MSS-8 shelf slots 4, 6, or 8.

1073

Release 7.0.0 3DB 19383 ACAA Issue 01 +24/-48 volt converter unit data sheet


The input voltage range is +19 to +36 Vdc.

51.3

Indicators, connectors, and control See Figure 515 for +24/-48 Volt Converter card front panel indicator and connectors. The +24/-48 Volt Converter card has the following indicators, connectors, and controls. See Table 178 for +24/-48 Volt Converter card indicators details. See Table 179 for +24/-48 Volt Converter card connector details. The +24/-48 Volt Converter card has no controls.

Figure 515

1074

+24/-48 volt converter card


Table 178


+24/-48 volt converter card indicator details

INDICATOR

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 179

+24/-48 volt converter card connector details

CONNECTOR

TYPE

FUNCTION

+24 Vdc Input

Station Battery and Return

-48 Vdc Output


1075

Release 7.0.0 3DB 19383 ACAA Issue 01 +24/-48 volt converter unit data sheet

1076




52 MPT Power Unit unit data sheet Table 180

MPT Power Unit


NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3CC50173AA 3CC50173AB

MPT Power Unit

N/A

N/A

N/A

Active

3CC50191AA

MPT Power Unit Bracket Supports up to 2 MPT Power Units or MPT Extended Power Units

52.1


Distributes power remotely to up to four external MPT ODUs with or without XPIC

•

Dual battery input provided with surge protection

•

Power feed to support -48V DC on the ODU side

•

In rush and short circuit protection on the ODU side

•

Reverse polarity protection on the -48V Power input side

•

Lightning protection on the ODU side

•

Hot Swap function

•

Output low-pass filter

•

Power ORing feeds the board from two independent battery power lines

•

Up to two units can be mounted in a 19-inch aluminum rack or 19-inch seismic rack.

•

To power the ODU one coaxial cable is connected to:

•

−

MPT Power Unit (Type N Connector)

−

Type N to Ethernet pair Pigtail (RJ45 of pair Pigtail is connected to RJ-45 of MPT ODU)

For data transmission, optical fiber is connected to the IDU and the MPT using optical connectors.

1077

Release 7.0.0 3DB 19383 ACAA Issue 01 MPT Power Unit unit data sheet

52.2


Description The MPT Power Unit is designed to remotely power four MPT ODUs through Type N-connector cables. The size of the board is 205 x172 mm. See Figure 516 for a front panel view of the MPT Power Unit. See Figure 517 for a top view of the box, and Figure 518 for a top view of the board.

Figure 516

MPT power unit front panel view 6.1 mm 21.8 mm 3.6 mm 37.8 mm 23.9 mm

15.2 mm 18.2 mm

33 mm

15.9mm

5.6 mm

5.2 mm

6.1 mm

205 mm 22830

1078


Figure 517


MPT power unit upper view of box

172 mm

21.2 mm 22832

1079


Figure 518


MPT power unit upper view of board 198 mm

150 mm

RJ45 (1AB004290261) N-CONNECTORS (1AB079710032)

PWR CONNECTOR (1AB323760002)

LIGHTPIPE (30B77012AAAA) 22831

52.3

Lightning protection Surge protection is added on the Battery Input for compliance with ETSI EN 300 1322 and Telcordia GR-1089-CORE. Lightning protection is added on each of the ODU Outputs for compliance with ITU-T K44 and K45.

52.4

Hot swap function The Hot Swap function is mainly used for the following two tasks: •

Limit the In Rush current sunk by the remote MPT ODU during power-up.

•

Break the current sourced by the power bar board in case of short circuit on the power link towards the remote MPT ODU.

It also accomplishes other minor tasks such as Overvoltage and Undervoltage shut down.

1080


52.5


Operational environment requirements The list of environmental requirements is reported in the 9500 MPR Technical Specifications for Split Mount Applications.

52.6

Electrical overview

52.6.1

DC in interfaces

The MPT Power Unit card sinks the -48V power from the DC In interfaces to feed the remote MPT ODU units. There are two power inputs on the front side. Table 181 describes the electrical characteristics of the DC In Interface. Table 181

MPT power unit electrical characteristics of DC in interfaces

DC voltage from the battery

Surge protection

52.6.2

Voltage range

-38.4V down to -57.6V

Typical Current

6.5 A

Max Current

8A

Standard

ETSI EN300 132-2

DC out interfaces The DC Out interfaces are N connectors interfaces for connection to remote powered MPT ODU units. These interfaces carry the -48V DC power. Table 182 describes the electrical characteristics of the DC Out Interface.

Table 182

MPT power unit electrical characteristics of DC out interfaces

DC (Remote Powering)

Lightning protection

Voltage range

-38.4V down to -57.6V

Current

2A

K45

1081



Note: The output voltage range indicated in Table 182 is equal to the input voltage range. These values have to be adjusted depending on power consumption and on the number of MPTs connected, to take into account the voltage drop on the power path.

As a general consideration, considering a maximum total current of 8A, with 2A on each MPT: •

Maximum Voltage drop: 0.67 V

The minimum drop can be calculated considering only one MPT connected and thus 2A as total current consumption: •

52.6.3

Minimum Voltage drop: 0.44 V

Housekeeping interfaces

Housekeeping interfaces are RJ45 copper Ethernet connectors.Alarm data and common signal will be mapped.The logic for housekeeping signals is GROUND (normal operation) or TRI-STATE (fail condition).

52.7

Indicators, connectors, and control The MPT Power Unit has the following indicators, connectors, and controls: •

2 x Power In Connector

•

6 x Green LED

•

4 x N Connector

•

1 x RJ45 connector

Table 183 describes the electrical connections of the DC in interfaces. Table 184 describes the electrical connections of the DC out interfaces. Table 185 describes the electrical characteristics of the Housekeeping Interfaces. Table 183

MPT power unit electrical connections of DC in interfaces

SIGNAL

DESCRIPTION

Power

-48V

1082



Table 183

MPT power unit electrical connections of DC in interfaces (Continued)

Ground

GND

Table 184

MPT power unit electrical connections of DC out interfaces

PIN

N-connector Signal

Description

Centre-tap

-48V

-48 V power

Shield

GND

Ground

Table 185 PIN

MPT power unit electrical connections of housekeeping interfaces RJ45 Signal

Description

1

BATT_0_FAIL

Power FAIL from Battery 0

2

BATT_1_FAIL

Power FAIL from Battery 1

3

PRES_OUT_0

ODU Power 0 FAIL

4

PRES_OUT_1

ODU Power 1 FAIL

5

PRES_OUT_2

ODU Power 2 FAIL

6

PRES_OUT_3

ODU Power 3 FAIL

7

HK_COM

Common signal for HK

8

HK_COM

Common signal for HK

Note: The Housekeeping outputs are present on pins 7 and 8 of the RJ-45 Connector. These pins are isolated from the board Ground.

Table 186 describes DC output MPT ODU operation ranges. Table 186

DC output MPT ODU operation ranges

Working range

0A < DC < 2A

Short circuit or over current fault

DC > 2A

1083


52.8


Mounting rack A bracket is provided to mount the MPT Power Unit in a 19 inch rack. The bracket provides an attachment point for grounding, located in the central strut. The same bracket can be used to mount the MPT Power Unit. See Figure 519.

Figure 519

MPT power unit mounting bracket

22833

1084



53 MPT Extended Power Unit unit data sheet Table 187



NAME

CLEI

ECI/ BAR CODE

CPR

STATUS

3CC50174AB


N/A

N/A

N/A

Active

3CC50191AA

MPT Power Unit Bracket Supports up to 2 MPT Power Units or MPT Extended Power Units

53.1


Feeds power to up to two external MPT ODUs with or without XPIC

•

Dual battery input provided with surge protection

•

Output voltage stabilized at -57V

•

Total Output Power: 200W

•

Galvanic Isolation between Battery Input and ODU Power Output

•

Output Power available by means of both Type N-connectors and RJ-45 connectors

•

Power Input capability for the following voltages: −

+19.2VDC to +57.6VDC

−

-19.2DC to -57.6VDC

•

Input In-Rush and EMI filter

•

Lightning protection on the ODU side

•

Output Hot-Swap / Short Circuit Protection

•

Input Reverse polarity protection

•

Output low-pass filter

•

Power ORing feeds the board from two independent battery power lines

•

Up to two units can be mounted in a 19-inch aluminum rack or 19-inch seismic rack.

•

There are two ways to power the ODU: 1. Data on Cat5e cable:

1085

Release 7.0.0 3DB 19383 ACAA Issue 01 MPT Extended Power Unit unit data sheet

•


Ethernet cable is connected to MPT Extended Power Unit (RJ-45 connector DC ODU Data) and MPT (RJ45 connector)

2. Data on fiber: •

Power can be on an Ethernet cable with RJ-45 connectors connected to the MPT Extended Power Unit and the MPT, or

•

on a coaxial cable with Type N connectors, with an Ethernet pair pigtail connected to the MPT Extended Power Unit and the MPT (the RJ-45 of the pair pigtail is connected to the MPT).

Both cases have limitations on cable length due to data on Ethernet or to power loss in the cables (length limitation depends on MPT configuration and the cable used).

53.2

Description The MPT Extended Power Unit is designed to power up to two MPT ODUs through Type N-connector cables and RJ-45 connectors. The MPT Extended Power Unit also uses the RJ-45 connectors to establish an Ethernet data link connection between IDU and ODU. The size of the board is 208 x 150 mm. See Figure 520 for a front panel view of the MPT Extended Power Unit. See Figure 521 for a top view of the box, and Figure 522 for a top view of the board.

Figure 520

MPT Extended Power Unit Front Panel View 9500 MPR


MPT1

MPT2



DC

DC Voltage

DC+ODU Data

DC

DC Voltage

DC+ODU Data

MPT2 Batt.B

Battery A

+

VDC

Battery B

-

+

VDC

-

23060

1086


Figure 521


MPT Extended Power Unit Upper View of Box

172 mm

22828

1087


Figure 522


MPT Extended Power Unit Upper View of Board

198 mm

150 mm

RJ45 (1AB004290261) 2 X RJ45 (1AB004290215) N-CONNECTORS (1AB079710032)

PWR CONNECTOR (MOLEX 39536-0002)

LIGHTPIPE 1AB108190004 (DIALIGHT 515-1061) 22827

53.2.1

Lightning Protection Surge protection is added on the Battery Input for compliance with ETSI EN 300 1322 and Telcordia GR-1089-CORE. Lightning protection is added on each of the ODU Outputs for compliance with ITU-T K44 and K45.

1088


53.3


EMI/EMC

53.3.1

Radiated Emission The MPT Extended Power Unit meets the Radiated Emission criteria as described in section 3.2.1 of GR-1089 reference Class A, and in section 8.2.3 of EN 301 489-1 reference Class B.

53.3.2

Conducted Emission

DC In Interface Ports meet the Conducted Emission requirements as detailed in section 3.2.2 of GR-1089 and section 8.3.3 of EN 301 489-1.

53.4

Electrical overview

53.4.1

DC In interfaces

The dual battery input is provided by two DC In connectors. Table 188 describes the electrical characteristics of the DC In Interface. Table 188

MPT Extended Power Unit Electrical Characteristics of DC In Interfaces

DC voltage from the battery

Surge protection

Voltage range

19.2V to 57.6V -19.2V to -57.6V

Max Current

15 A

Standard

ETSI EN300 132-2 GR-1089-CORE

1089


53.4.1.1


DC Out interfaces

The DC Out interfaces provide the power supply to two external MPT ODUs. For each ODU the power is available on Type N and RJ-45 connectors. Only one output (Type N or RJ-45) must be used to power an MPT. If an RJ-45 connector is used to power an MPT, the data coming from the other RJ-45 can be added. Table 189 describes the electrical characteristics of the DC Out Interface. Table 189

MPT Extended Power Unit Electrical Characteristics of DC Out Interfaces

ODU DC voltage


53.4.1.2

Voltage range

-57V

Max Current

1.8 A

ITU-T K44 ITU-T K45 GR-1089-CORE

RJ-45 connectors There are two dual-stacked RJ-45 connectors. Table 190 describes the electrical characteristics of the dual-stacked RJ-45 connectors.

Table 190

MPT Extended Power Unit Electrical Characteristics of dual-stacked RJ-45 connectors

Ethernet signal

Standards

100 Base-T 1000 Base-T

DC (remote powering)

Voltage range

-57V

Current

500 mA per contact


53.4.1.3

ITU-T K45

Housekeeping interface The housekeeping interface is a dedicated RJ-45 copper Ethernet connector. Alarm data and common signal will be mapped.The logic for housekeeping signals is GROUND (normal operation) or High Impedance (fail condition).

1090



Table 191 describes the electrical connections of the housekeeping interface. Table 191

MPT Extended Power Unit Electrical Connections of housekeeping interface

RJ-45 PIN

Signal

Description

1

BATT_A_FAIL

Power FAIL from Battery A

2

BATT_B_FAIL

Power FAIL from Battery B

3

PRES_OUT_1

ODU 1 Power FAIL

4

PRES_OUT_2

ODU 2 Power FAIL

7

HK_COM

Housekeeping Common

8

HK_COM

Housekeeping Common

5 6

Note: The Housekeeping outputs are present on pins 7 and 8 of the RJ-45 Connector. These pins are isolated from the board ground.

53.4.1.4

Main Power Supply Unit The Main Power Supply Unit shall achieve the following tasks: •

Isolation between Battery Input and ODU Output

•

Stabilization of the output voltage at -57V despite the variation of the input voltage

Table 192 describes the main features of the MPT Extended Power Unit. Table 192

MPT Extended Power Unit Main Power Supply Features

Feature

Value

Input Range

18-60V

Output Voltage

-57V

Output Power

200W

1091


Table 192


MPT Extended Power Unit Main Power Supply Features (Continued)

Isolation

1500V

53.5

Indicators, connectors, and control The MPT Extended Power Unit has the following indicators, connectors, and controls: •

2 x Green LED for Battery Power presence

•

2 x Green LED for Output Power presence

•

2 x N-Connectors for Power Output

•

2 x RJ-45 Connectors for Power Output and Data In/Out from/to ODU

•

2 x RJ-45 Connectors for Data In/Out from/to IDU.

•

Housekeeping output signaling through dedicated RJ-45 Connector

Table 193 describes the electrical connections of the DC In interfaces. Table 194 describes the electrical connections of the DC Out interfaces. Table 193

MPT Extended Power Unit Electrical Connections of DC In Interfaces

SIGNAL

PIN NUMBER

Positive Supply

1

Negative Supply

2

Note: The battery ground needs to be isolated from the RJ-45 ground and N-connector ground. The RJ-45 ground and N ground must be Chassis grounds. This is because a surge can be delivered directly to the unit through the CAT5e outer shield. The outer shield should be coupled to the RJ-45 shield that is coupled to the metal box.

Table 194

MPT Extended Power Unit Electrical Connections of DC Out Interfaces

Type

Pin

Signal

Type N

Center Tap

-57V

Shield

GND

1092



Note: The shield of the dual stacked RJ-45 connector must be connected to ground; this will allow the cable shielding to be included in the return current path.

53.6

Alarm and LED behavior The following tables summarize the alarm and LED behavior. Table 195 describes VDC input battery operation ranges. Table 196 describes DC output MPT ODU operation ranges.

Table 195

VDC Input Battery Operation Ranges

Working range

+19.2V < VDC < +57.6V -19.2V < VDC < -57.6V

Undervoltage

0V < VDC < +19.2V 0V < VDC < -19.2V

Overvoltage

VDC > +57.6V VDC > -57.6V

Table 196

DC output MPT ODU Operation Ranges

Working range

0A < DC < 1.75A

Short circuit or over current fault

DC > 1.75A

53.7

Mounting rack A bracket is provided to mount the MPT Extended Power Unit in a 19 inch rack. The bracket provides an attachment point for grounding, located in the central strut. The same bracket can be used to mount the MPT Power Unit. See Figure 523.

1093


Figure 523


MPT Extended Power Unit mounting bracket

22833

1094


Glossary

54 Glossary A AIS - Alarm Indication Signal AMI - Alternating Mark Inversion ANSI - American National Standards Institute APT - Active Problem Table ASAP - Alarm Severity Assignment Profile ASIC - Application Specific Integrated Circuit ATPC - Automatic Transmit Power Control AVC - Attribute Value Change B BBE - Background Block Error BER - Bit Error Rate BIP - Bit Interleaved Parity C CAS - Channel Associated Signaling CD - Current Data CES - Circuit Emulation Service CESoETH - Circuit Emulation Service over Ethernet CESoP - Circuit Emulation Services over Packet CFA - Carrier Failure Alarm CFM - Connectivity Fault Management CLA - Common Loss Alarm Core - Generic term for Core-E, CorEvo and MSS/CORE

1095

Release 7.0.0 3DB 19383 ACAA Issue 01 Glossary


Core-E - Control and Switching Module CoS - Class of Service CRC - Cyclic Redundancy Check CRU - Clock Reference Unit CSM-E - Control and Switching Module (Core-E card) CT - Craft Terminal D DCN - Data Communications Network DDF - Digital Distribution Frame DEI - Drop Eligible Indication DL - Data Link DS - Differentiated Services DSCP - Differentiated Services Code Point E EAS - Ethernet Access Switch Card EAS in the documentation refers to both P8ETH and EASv2 cards unless otherwise stated. ECID - ECID (Emulation IDentification) is a network unique 8-bit code identifier used along with V-Lan to identify and switch individual PDH and SDH lines through the Core-E. ECT - Equipment Craft Terminal EFC - Ethernet Flow Control EFD - Event Forwarding Discriminator EOW - Engineering Order Wire EPS - Equipment Protection Switching ERP - Ethernet Ring Protection

1096


Glossary

ES - Errored Second ESMC - Ethernet Synchronization Message Channel ETH - ETHernet ETSI - European Telecommunications Standards Institute EW - Early Warning F F - Framing FAS - Frame Alignment Signal FCS - Frame Check Sequence FD - Frequency Diversity FE - Fast Ethernet FEC - Forward Error Correction FPGA - Field Programmable Gate Array G GFP - Generic Frame Protocol GNE - Gateway Network Element H HBER - High Bit Error Ratio HD - History Data HDB3 - High Density order 3 Bipolar encoding HET - Hetero frequency HS - Hitless Switch HSB - Hot Stand-By I IDU - InDoor Unit

1097



IM - Information Model IP - Internet Protocol ISPB - Intra Shelf Parallel Switching IWF - Interworking Function J JA - Jitter Attenuator JTAG - Joint Test Action Group JUSM - Java User-based Security Model K L LAN - Local Area Network LAPD - Link Access Procedure on D-channel LBER - Low Bit Error Ration LIM - Link Identifier Mismatch LIU - Line Interface Unit LOF - Loss Of Frame LOS - Loss Of Signal M MAC - Medium Access Control MAU - Medium Attachment Unit MEF - Metro Ethernet Forum MEN - Metro Ethernet Network MIB - Management Information Base MPR - Microwave Packet Radio MPT - Microwave Packet Transport

1098


Glossary

MPT-HC - Microwave Packet Transport, High Capacity. MPT-HC in the documentation refers to MPT-HC V2 unless otherwise stated. MRTIE - Maximum Relative Time Interval Error MSOH - Multiple Section OverHead MSS - Microwave Service Switch MTIE - Maximum Time Interval Error MXC - Microwave Cross Connect N NE - Network Element NEC - Network Element Clock NEtO - Network Element Overview NMS - Network Management System NNI - Network Node Interface NRZ - Not Return to Zero NSA - Not Service Affecting NTP - Network Time Protocol O OAM - Operations and Maintenance OAMPDU - OAM Protocol Data Unit OC - ODU Controller ODU - Outdoor Unit OFS - Out of Frame Second OH - OverHead OMS - Operations Management System OOF - Out Of Frame

1099



OS - Operation System OSP - OutSide Plant OSPF - Open Short Path First P P2E3DS3 - Two port DS3 PDH Interface Card P8ETH - Eight port Ethernet Access Switch Card P32E1DS1 - Thirty-two port E1/DS1 PDH Interface Card PDH - Plesiochronous Digital Hierarchy PDH in the documentation refers to E1, DS1 and DS3 PDU - Protocol Data Unit PLM - PayLoad Mismatch PM - Performance Monitoring PNU - Packet Node Unit PPM - Part Per Million PRBS - Pseudo Random Binary Sequence PRS - Clock Primary Reference Source Clock PSU - Power Supply Unit PTP - Precision Time Protocol PTU - Packet Transport Unit Q QoS - Quality of Service R R-APS - Ring Automatic Protection Switching RAI - Remote Alarm Indication RDI - Remote Defect Indication

1100


Glossary

REI - Remote Error Indication RFC - Remote Frequency Control RI - Remote Inventory RPL - Ring Protection Link RPS - Radio Protection Switching RSOH - Regenerator Section Over-Head RSL - Receive Signal Level RTPC - Remote Transmit Power Control RTU - Right To Use S SA - Service Affecting SD - Space Diversity SDH - Synchronous Digital Hierarchy SDH in the documentation refers to STM-1 and OC-3 SDHACC - Two port SDH Interface Card SDHCHANN - Two port SDH Interface Card in Channelized mode (ETSI market only) SEF - Service Errored Frame SerDes - Serializer / Deserializer SES - Severely Errored Second SF - Signal Fail SNMP - Simple Network Management Protocol SP - Spare SPI - Serial Peripheral Interface SW - Software

1101



SWP - Software Package Symbol Rate - The number of symbol changes (signalling events) made to the transmission medium per second using a digitally modulated signal or a line code. Also known as baud rate or modulation rate. T TBI - Ten Bit Interface TC - Transparent Clock TCA - Threshold Crossing Alarm TCO - Total Cost of Ownership TD - Threshold Data TDEV - Time Deviation TDF - Total Discarded Frames TDM - Time Division Multiplexed TDM2ETH - Time Division Multiplexed To Ethernet TDM2TDM - Time Division Multiplexed To Time Division Multiplexed TIM - Trace Identifier Mismatch TMN - Telecommunication Management Network TPS - Tx Protection Switching TRCF - Total Received Correct Frames TRCO - Total Received Correct Octets TRSEF - Total Received Service Errored Frames TS - Time Slot TSM - Transmission Systems Manager TTF - Total Transmitted Frames TTO - Total Transmitted Octets TTP - Trail Termination Point

1102


Glossary

U UAS - UnAvailable Second UAT - UnAvailable Time UDP - User Datagram Protocol UI - Unit Interval V VC-n - Virtual Container - n VLAN - Virtual Local Area Network W WebEML - Web Element Manager Layer. A set of Java applications (craft terminal) containing NEtO and JUSM. WK - Working X XPIC - Cross Polar Interference Canceler Y Z ZBTSI - Zero Byte Time Slot Interchange

1103


1104


Release 7.0.0 3DB 19383 ACAA Issue 01

Customer document and product support

Customer documentation Customer Documentation Welcome Page Product manuals and documentation updates are available at alcatel-lucent.com. If you are a new user and require access to this service, please contact your Nokia sales representative.

Technical Support Product Support Portal

Documentation feedback Customer Documentation Feedback

Release 7.0.0 3DB 19383 ACAA Issue 01

© 2016 Nokia.

3DB19283ACAATQZZA01_V1_9500 MPR R7.0.0 Product Information Manual

Recommend Documents