Cambium Networks 49100 PTP49600, Wireless Ethernet Bridge User Manual PTP 600 Series User Guide

Cambium Networks Limited PTP49600, Wireless Ethernet Bridge PTP 600 Series User Guide

User manual

PTP 600 Series User Guide MOTOROLA POINT-TO-POINT WIRELESS SOLUTIONS
1MOTOROLA, Inc. Point-to-Point Wireless Bridges – PTP 600 Series Software Release PTP 600-08-xx System User Guide December 2nd, 2008 Ref: PHN-0896-08.00 Copyright Information This document is the confidential property of Motorola, Inc. and without its prior written consent may not be copied or released to third parties. MOTOROLA, the stylized M Logo and all other trademarks indicated as such herein are trademarks of Motorola, Inc. ® Reg. U.S. Pat & Tm. Office. PTP 600 is a trademark of Motorola, Inc. All other product or service names are the property of their respective owners. © 2008-2006 Motorola, Inc. All rights reserved. http://www.motorola.com/ptp Compliance General Changes or modifications not expressly approved by Motorola could void the user’s authority to operate the system. NOTE: This system has achieved Type Approval in various countries around the world. This means that the system has been tested against various local technical regulations and found to comply. The frequency bands in which the system operates may be ‘unlicensed’ and, in these bands, the system can be used provided it does not cause interference. Further, it is not guaranteed protection against interference from other products and installations.
2The system has been tested for compliance to both US (FCC) and European (ETSI) specifications. It has been shown to comply with the limits for emitted spurious radiation for a Class B digital device, pursuant to Part 15 of the FCC Rules in the USA and appropriate European ENs. These limits have been designed to provide reasonable protection against harmful interference. However the equipment can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to other radio communications. There is no guarantee that interference will not occur in a particular installation. NOTE: A Class B Digital Device is a device that is marketed for use in a residential environment, notwithstanding use in commercial, business and industrial environments. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: x Reorient or relocate the Outdoor Unit (ODU). x Increase the separation between the affected equipment and ODU. x Connect the ODU/PIDU into a power outlet on a circuit different from that to which the receiver is connected. x Consult your installer or supplier for help. Deployment and Operation The Radio Regulations of various countries’ limits constrain the operation of radio products generally. In particular the local regulator may limit the amount of conducted or radiated transmitter power and may require registration of the radio link. The power transmitted by the PTP 600 Series Bridge is controlled by the use of Region-specific License Keys. The following examples show how the regulatory limits apply in some specific countries at the current time. Operators should note that regulations are subject to change. Contact your supplier/installer to ensure that your product is set for the correct License Key for your Country/Region and to ensure that you have fulfilled all the local regulatory requirements, especially if you are intending to use a link with external antennas. Footnotes to the table below indicate countries where registration of the link is currently mandatory.
3The system has been tested for compliance to both US (FCC) and European (ETSI) specifications. It has been shown to comply with the limits for emitted spurious radiation for a Class B digital device, pursuant to Part 15 of the FCC Rules in the USA and appropriate European ENs. These limits have been designed to provide reasonable protection against harmful interference. However the equipment can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to other radio communications. There is no guarantee that interference will not occur in a particular installation. CAUTION: When planning a link that will use Connectorized PTP 600 Series bridges (with external antennas), ensure that regulatory requirements are met for the installation, as described in Section 13.6 “Regulatory Issues with Connectorized Units”. Regulations applicable to PTP 25600 variant Examples of Regulatory Limits at 2.5GHz FCC Under FCC Regulations, operation of this product is only allowed with a License Key for Region 16 which ensures that the product will meet the requirements of FCC part 27. Note: Spectrum in this band (2496MHz to 2690MHz) is allocated on a licensed basis in USA. Regulations applicable to PTP 45600 variant Examples of Regulatory Limits at 4.5GHz Operation of this product is only allowed with a License Key for Region 23 (USA Military). Regulations applicable to PTP 48600 variant Examples of Regulatory Limits at 4.8GHz Operation of this product is only allowed with a License Key for Regions 15 or 23 (USA Military). Regulations applicable to PTP 49600 variant Examples of Regulatory Limits at 4.9GHz Operation of this product is only allowed with a License Key for Region 14 (USA/Canada Public Safety) or Region 18 (Hong Kong Public Safety).
4Regulations applicable to PTP 54600 variant Examples of Regulatory Limits at 5.4GHz FCC Operation of this product is only allowed with a License Key for Region 12. This implements Radar Detection in accordance with FCC Regulations and limits the EIRP to the regulatory limits below: EIRP  Max of [(17 +10 x Log(Channel BW)) and 30] dBm. ETSI Oeration of this product is only allowed with a License Key for Region 26. This implements Radar Detection, including barring of the band from 5600 MHz to 5650 MHz and limits the EIRP to the regulatory limits below: EIRP  Max of [(17 +10 x Log(Channel BW)) and 30] dBm Australia, Canada Oeration of this product is only allowed with a License Key for Region 13. This implements Radar Detection, including barring of the band from 5600 MHz to 5650 MHz and limits the EIRP to the regulatory limits below: EIRP  Max of [(17 +10 x Log(Channel BW)) and 30] dBm Thailand Operation of this product is only allowed with a License Key for Region 20 (30 dBm or 1W EIRP) Korea Operation of this product is only allowed with a License Key for Region 21 (28 dBm EIRP (15 MHz), 27 dBm EIRP (10 MHz), 24 dBm EIRP (5 MHz)). General Notice Applicable to Europe This equipment complies with the essential requirements for the EU R&E Directive 1999/5/EC. NOTE: In regions other than EU/USA, specific local regulations may apply. It is the responsibility of the installer/user to check that the equipment as deployed meets local regulatory requirements.
5Regulations applicable to PTP 58600 variant Examples of Regulatory Limits USA/ Canada/ Taiwan/ Brazil Equipment can be operated in any mode, best results will be obtained using Region 1 settings. There are some limitations on the use of antennas above 4ft diameter plus a band edge power reduction. China Operation of this product is only allowed with a License Key for Region 2 (33 dBm or 2W EIRP). Australia Operation of this product is only allowed with a License Key for Region 3 (36 dBm or 4W EIRP). Hong Kong Operation of this product is only allowed with a License Key for Region 3 (36 dBm or 4W EIRP). UK Operation of this product is allowed with a License Key for Region 4 . This implements Radar Detection with barring of the band from 5795 MHz to 5815 MHz and above 5850 MHz. It limits the EIRP to the Regulatory Limits below: EIRP  Max of [(23 +10 x Log(Channel BW)) and 36] dBm Singapore Operation of this product is only allowed with a License Key for Region 5 (20 dBm or 100mW EIRP). Eire Operation of this product is only allowed with a License Key for Region 6 (33 dBm or 2W EIRP). The lower power limits are lower in narrower bandwidths. Korea Operation of this product is only allowed with a License Key for Region 11 (43 dBm or 20W EIRP). India Operation of this product is only allowed with a License Key for Region 19 (36 dBm or 4W EIRP at 15 MHz and 10 MHz and 33 dBm or 2 W EIRP at 5 MHz channel bandwidth). Thailand Operation of this product is only allowed with a License Key for Region 20 (30 dBm or 1W EIRP). Germany Operation of this product is only allowed with a License Key for Region 22. This limits the band of operation to 5755 MHz to 5850 MHz and limits the EIRP to the Regulatory Limits below: EIRP  Max of [(23 +10 x Log(Channel BW)) and 36] dBm Bahrain Operation of this product is allowed with a License Key for Region 24 . This limits the EIRP to the Regulatory Limits below: EIRP  Max of [(20 +10 x Log(Channel BW)) and 33] dBm Norway Under Norway Regulations, operation of this product is only allowed with a License Key for Region 7. This implements Radar Detection and limits the EIRP to the Regulatory Limits below: EIRP  Max of [(40 +10 x Log(Channel BW)) and 53] dBm Spectral density at border between Norway and neighbouring countries shall not exceed -122,5 dBW/m2 measured with a reference bandwidth of 1 MHz.
6 General Notice Applicable to Europe This equipment complies with the essential requirements for the EU R&E Directive 1999/5/EC. The use of 5.8GHz for Point to Point radio links is not harmonized across the EU and currently the product may only be deployed in the UK, Eire (IRL), Germany, Denmark and Norway. However, the regulatory situation in Europe is changing and the radio spectrum may become available in other countries in the near future. Please contact Motorola for the latest situation. Regulations applicable to PTP 59600 variant Examples of Regulatory Limits Russia Operation of this product is only allowed with a License Key for Region 16 (no power limit) India Operation of this product is only allowed with a License Key for Regions 17 or 19 (36 dBm or 4W EIRP at 30 MHz, 15 MHz and 10 MHz; and 33 dBm or 2 W EIRP at 5 MHz channel bandwidth). NOTES:UK Registration of Links – OfCom, The application form may be found at: http://www.ofcom.org.uk/radiocomms/isu Eire Registration of Links – Commission for Communication Regulation, The application form may be found at: http://www.comreg.ie/licensing_and_services Disclaimer
7The parameters quoted in this document must be specifically confirmed in writing before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments to the detail specification at its discretion. The publication of information in this document does not imply freedom from patent or other rights of Motorola, Inc. or others.
8Contents 1 About This User Guide ....................................................................................................... 28 1.1 Interpreting Typeface and Other Conventions ...................................................................... 28 1.2 Getting Additional Help .........................................................................................................30 1.3 Sending Feedback ................................................................................................................30 2 Avoiding Hazards................................................................................................................31 2.1 Preventing Overexposure to RF Energy ............................................................................... 31 2.1.1 Calculations for Separation Distances and Power Compliance Margins.............................. 31 2.1.1.1 Calculated Distances and Power Compliance Margins ........................................................ 32 3 Getting Started .................................................................................................................... 34 3.1 For Your Safety ..................................................................................................................... 34 3.2 Welcome ............................................................................................................................... 35 3.2.1 Who Should Use This Guide................................................................................................. 35 3.2.2 Contact Information ............................................................................................................... 35 3.2.3 Repair and Service................................................................................................................ 35 3.3 Product Description............................................................................................................... 36 3.3.1 The Outdoor Unit (ODU) ....................................................................................................... 38 3.3.2 PIDU Plus – PTP 600 Series Bridge..................................................................................... 39 3.3.3 Redundancy and Alternative Powering Configurations......................................................... 41 3.3.3.1 External DC Supply Only ...................................................................................................... 41 3.3.3.2 External DC Supply and AC Supply...................................................................................... 42 3.3.3.3 External DC Supply and Redundant AC Supply ................................................................... 42 3.3.4 Remote LEDs and Recovery Switch..................................................................................... 43 3.3.5 Cables and connectors ......................................................................................................... 43 3.3.6 PTP and Lightning Protection ............................................................................................... 44 3.3.7 Mounting Brackets................................................................................................................. 44 3.3.8 Configuration and Management............................................................................................ 45 3.4 Warranty................................................................................................................................ 45 4 Product Architecture .......................................................................................................... 46 4.1 Radio Link ............................................................................................................................. 46 4.2 Frequency Bands .................................................................................................................. 46 4.3 Ethernet Frames.................................................................................................................... 47 4.4 Management Function .......................................................................................................... 47 4.5 Channel Bandwidth and Link Symmetry Control .................................................................. 48 4.6 Upgradeable Software .......................................................................................................... 48
95 Radio Link Planning and Regulations ............................................................................. 49 5.1 Spectrum Planning................................................................................................................ 49 5.2 Licenses and Region Codes ................................................................................................. 50 5.2.1 PTP 25600 Licenses and Region Codes .............................................................................. 51 5.2.2 PTP 45600 Licenses and Region Codes .............................................................................. 51 5.2.3 PTP 48600 Licenses and Region Codes .............................................................................. 52 5.2.4 PTP 49600 Licenses and Region Codes .............................................................................. 53 5.2.5 PTP 54600 Licenses and Region Codes .............................................................................. 54 5.2.6 PTP 58600 Licenses and Region Codes .............................................................................. 55 5.2.7 PTP 59600 Licenses and Region Codes .............................................................................. 57 5.3 Operational Restrictions........................................................................................................58 5.3.1 Radar Avoidance................................................................................................................... 58 5.3.2 RTTT Avoidance and Other Channel Use Restrictions ........................................................ 59 5.3.3 Radar Avoidance, i-DFS and Variable (Narrow) Bandwidth Operation ................................ 60 5.4 Variable Channel Bandwidth Operation................................................................................ 60 5.5 PTP 25600 Specific Frequency Planning Considerations .................................................... 60 5.5.1 Power Reduction in the Upper Band..................................................................................... 62 5.6 PTP 45600 Specific Frequency Planning Considerations .................................................... 63 5.6.1 PTP 45600 Raster Considerations........................................................................................ 65 5.6.2 PTP 45600 Transmit Power Reduction at the Band Edges.................................................. 65 5.7 PTP 48600 Specific Frequency Planning Considerations .................................................... 65 5.8 PTP 49600 Specific Frequency Planning Considerations .................................................... 66 5.9 PTP 54600 Specific Frequency Planning Considerations .................................................... 67 5.9.1 PTP 54600 Raster Considerations:....................................................................................... 69 5.9.2 Transmit Power Reduction at the Band Edges ..................................................................... 69 5.10 PTP 58600 Specific Frequency Planning Considerations .................................................... 70 5.10.1 PTP 58600 Raster Considerations........................................................................................ 72 5.10.2 PTP 58600 Transmit Power Reduction at the Band Edges.................................................. 73 5.11 PTP 59600 Specific Frequency Planning Considerations .................................................... 74 5.11.1 PTP 59600 Raster Considerations........................................................................................ 76 5.12 Time Division Duplex (TDD) Synchronization....................................................................... 77 5.12.1 Introduction............................................................................................................................ 77 5.12.2 TDD Synchronization ............................................................................................................ 78 5.12.3 Implementation of TDD Synchronization............................................................................... 79 5.12.4 System Constraints with TDD Synchronization Enabled ...................................................... 79 5.13 Color Codes .......................................................................................................................... 80
105.14 Distance ................................................................................................................................ 80 5.15 Networking Information ......................................................................................................... 81 5.16 Lightning Protection............................................................................................................... 81 5.17 Electrical Requirements ........................................................................................................ 81 6 Site Planning........................................................................................................................ 82 6.1 Site Selection Criteria............................................................................................................ 82 6.1.1 ODU Site Selection ............................................................................................................... 82 6.1.2 PTP 600 Series Bridge PIDU Plus Site Selection................................................................. 82 6.1.3 Path Loss Considerations ..................................................................................................... 83 6.1.4 Definitions.............................................................................................................................. 83 6.1.5 PTP 25600 Product Variant - Link Loss, Output Power and System Threshold versus Modulation Mode .................................................................................................................................. 85 6.1.6 PTP 45600 Product Variant - Link Loss, Output Power and System Threshold versus Modulation Mode .................................................................................................................................. 87 6.1.7 PTP 48600 Product Variant - Link Loss, Output Power and System Threshold versus Modulation Mode .................................................................................................................................. 89 6.1.8 PTP 49600 Product Variant - Link Loss, Output Power and System Threshold versus Modulation Mode .................................................................................................................................. 91 6.1.9 PTP 54600 Product Variant - Link Loss, Output Power and System Thresholds versus Modulation Mode .................................................................................................................................. 93 6.1.10 PTP 58600 Product Variant - Link Loss, Output Power and System Thresholds versus Modulation Mode .................................................................................................................................. 95 6.1.11 PTP 59600 Product Variant - Link Loss, Output Power and System Thresholds versus Modulation Mode .................................................................................................................................. 97 7 Installation ........................................................................................................................... 99 7.1 Preparation............................................................................................................................ 99 7.2 Installation Procedure ........................................................................................................... 99 7.3 Tools Required .................................................................................................................... 100 7.4 Installation Support.............................................................................................................. 100 7.5 Legal Disclaimer.................................................................................................................. 100 7.6 Mounting the ODUs............................................................................................................. 101 7.7 Connecting Up..................................................................................................................... 103 7.7.1 Preparing the PIDU Plus To ODU Cable ............................................................................ 103 7.7.2 Making the Connections at the ODU................................................................................... 106 7.7.3 Making the PTP 600 Series Bridge PIDU Plus Connection At The ODU ........................... 107 7.7.4 Routing the Cable................................................................................................................ 108 7.7.5 Fitting a Lightning Protection Unit ....................................................................................... 108 7.7.6 Grounding the Installation ................................................................................................... 109
117.7.7 Making the ODU Connection at the PTP 600 Series Bridge PIDU Plus............................. 109 7.7.8 Making the Network Connection at The PIDU Plus – PTP 600 Series Bridge ................... 110 7.7.9 Mounting the PTP 600 Series Bridge PIDU Plus ................................................................ 111 7.7.10 Powering Up........................................................................................................................ 113 7.7.11 Aligning the PTP 600 Series Bridge ODUs......................................................................... 114 8 Web Page Reference......................................................................................................... 117 8.1 Home Page – PTP 600 Series Bridge................................................................................. 119 8.1.1 Home Page Alarm Display .................................................................................................. 120 8.2 Systems Status Page.......................................................................................................... 124 8.2.1 Histogram Data ................................................................................................................... 129 8.3 System Administration Pages .............................................................................................130 8.3.1 System Configuration .......................................................................................................... 131 8.3.1.1 General Configuration Page................................................................................................ 131 8.3.1.2 LAN Configuration Page ..................................................................................................... 133 8.3.1.3 LAN Configuration Page – Use VLAN For Management Interfaces ................................... 136 8.3.1.4 LAN Configuration Page – Manual Ethernet Configuration ................................................ 137 8.3.1.5 Save and Restore Configuration File .................................................................................. 138 8.3.1.5.1 Save Configuration File ....................................................................................................... 138 8.3.1.5.2 Restore Configuration File ..................................................................................................140 8.3.1.6 Telecoms Configuration Page............................................................................................. 142 8.3.2 Statistics Page..................................................................................................................... 144 8.3.3 Detailed Counters Page ...................................................................................................... 147 8.3.4 Install Pages........................................................................................................................ 150 8.3.4.1 Manually Configuring The Wireless Units ........................................................................... 151 8.3.4.2 Internet Protocol Configuration ........................................................................................... 153 8.3.4.3 Telecoms Interface.............................................................................................................. 155 8.3.4.4 Wireless Configuration ........................................................................................................ 156 8.3.4.5 Confirm Configuration ......................................................................................................... 163 8.3.4.6 Disarm ................................................................................................................................. 165 8.3.5 Graphical Install................................................................................................................... 167 8.3.6 Software Upgrade ............................................................................................................... 168 8.3.7 Spectrum Management....................................................................................................... 172 8.3.7.1 Wireless Channels ..............................................................................................................172 8.3.7.2 Spectrum Management Measurements .............................................................................. 172 8.3.7.3 Measurement Analysis........................................................................................................ 172 8.3.7.4 The Spectrum Management Master / Slave Relationship................................................... 173
128.3.7.5 Spectrum Management Configuration ................................................................................ 176 8.3.7.6 Barring Channels................................................................................................................. 177 8.3.7.7 Master and Slave Channel Spectrum Graphics.................................................................. 177 8.3.7.8 Active Channel History........................................................................................................ 179 8.3.7.9 Viewing Historic Spectrum Management Metrics ...............................................................180 8.3.8 Spectrum Management (Fixed Frequency) ........................................................................ 181 8.3.9 Spectrum Management Control - With Operational Restrictions ........................................ 182 8.3.10 Spectrum Management – Example of PTP 25600 Product variant .................................... 185 8.3.11 Remote Management Page ................................................................................................ 186 8.3.11.1 Control Access to HTTP Interface....................................................................................... 187 8.3.11.2 Control Access to Telnet Interface...................................................................................... 187 8.3.11.3 SNMP (Simple Network Management Protocol)................................................................. 187 8.3.11.4 Supported Management Information Bases (MIBS) ........................................................... 187 8.3.11.5 Diagnostics Alarms.............................................................................................................. 189 8.3.11.6 SNMP Configuration............................................................................................................ 190 8.3.11.7 SMTP (Simple Mail Transport Protocol).............................................................................. 190 8.3.11.8 SNTP (Simple Network Time Protocol)............................................................................... 191 8.3.11.9 Setting the clock .................................................................................................................. 191 8.3.12 Diagnostics.......................................................................................................................... 192 8.3.12.1 Diagnostic Plotter ................................................................................................................ 193 8.3.12.2 Diagnostics Download......................................................................................................... 194 8.3.13 Change System Administration Password.......................................................................... 195 8.3.14 License Key......................................................................................................................... 195 8.3.15 Properties ............................................................................................................................ 197 8.3.16 Reboot................................................................................................................................. 198 9 Recovery Mode.................................................................................................................. 199 9.1 Upgrade Software Image .................................................................................................... 201 9.2 Reset IP & Ethernet Configuration ...................................................................................... 203 9.3 Erase Configuration............................................................................................................. 204 9.4 Reboot................................................................................................................................. 207 10 Lightning Protection ......................................................................................................... 208 10.1 Overview ............................................................................................................................. 208 10.1.1 Lightning Protection Zones .................................................................................................208 10.2 Detailed Installation............................................................................................................. 211 10.3 Installation Wiring................................................................................................................ 214 10.4 LPU Recommended Configurations.................................................................................... 215
1310.4.1 Typical Mast or Tower Installation....................................................................................... 216 10.4.2 Typical Wall Installation....................................................................................................... 217 10.4.3 Mast or Tower Installation with E1/T1................................................................................. 218 10.4.4 Wall Installation with E1/T1 ................................................................................................. 219 10.4.5 Mast or Tower Installation with GPS Sync Box................................................................... 220 10.4.6 Wall Installation with GPS Sync Box................................................................................... 221 10.4.7 Mast or Tower Installation with GPS Sync Box and E1/T1................................................. 222 10.4.8 Wall Installation with GPS Sync Box and E1/T1 ................................................................. 223 11 Troubleshooting (Fault Finding)...................................................................................... 224 11.1 Test Link End Hardware...................................................................................................... 224 11.1.1 Power LED is Off................................................................................................................. 226 11.1.2 Power LED is Flashing........................................................................................................ 227 11.1.3 Ethernet LED did not Flash 10 Times ................................................................................. 227 11.1.4 No Ethernet Activity............................................................................................................. 228 11.1.5 Irregular Ethernet Activity.................................................................................................... 229 11.1.6 Connection is not 1000 BaseT ............................................................................................ 229 11.1.7 Test RJ45 Resistance ......................................................................................................... 229 11.2 Test Radio Link ................................................................................................................... 231 11.2.1 No Activity ........................................................................................................................... 231 11.2.2 Some Activity....................................................................................................................... 231 12 Wind Loading..................................................................................................................... 232 12.1 General................................................................................................................................ 232 12.2 Calculation of Lateral Force ................................................................................................ 232 12.3 Capabilities of the PTP 600 Series Bridges ........................................................................ 233 12.4 Wind Speed Statistics ......................................................................................................... 233 13 Connectorized PTP 600 Series Bridge............................................................................ 234 13.1 Scope .................................................................................................................................. 234 13.2 Product Description............................................................................................................. 234 13.2.1 Hardware............................................................................................................................. 234 13.2.2 Antenna ............................................................................................................................... 234 13.3 Software/Features ............................................................................................................... 235 13.3.1 Status Page......................................................................................................................... 235 13.3.2 Configuration Pages............................................................................................................ 236 13.3.3 Installation Pages ................................................................................................................ 237 13.4 Deployment Considerations ................................................................................................ 240 13.5 Link Budget ......................................................................................................................... 240
1413.6 Regulatory Issues with Connectorized Units ...................................................................... 240 13.6.1 Cable Losses (FCC Regions Only) .................................................................................... 241 13.6.2 Antenna Choices ................................................................................................................. 241 13.6.3 FCC Antenna Restrictions on the PTP 58600 .................................................................... 242 13.6.4 FCC Antenna Restrictions on the PTP 54600 .................................................................... 246 13.7 Installation ........................................................................................................................... 249 13.7.1 Antenna Choice................................................................................................................... 249 13.7.2 Cables and Connectors....................................................................................................... 249 13.7.3 Tools.................................................................................................................................... 249 13.7.4 Miscellaneous supplies ....................................................................................................... 250 13.7.5 Mounting the Connectorized 600 Series Bridge ................................................................. 250 13.7.6 Mounting the antennas........................................................................................................ 250 13.7.7 Alignment Process .............................................................................................................. 251 13.7.8 Aligning Dual Polar Antennas ............................................................................................. 251 13.7.9 Aligning Separate Antennas................................................................................................ 251 13.7.10 Completing the Installation.................................................................................................. 252 13.7.11 Antenna Cable Fixing .......................................................................................................... 252 13.7.12 Antenna Connection Weatherproofing ................................................................................ 253 13.8 Additional Lightning Protection............................................................................................ 254 13.8.1 ODU Mounted Outdoors ..................................................................................................... 254 13.8.2 ODU Mounted Indoors ........................................................................................................ 255 14 TDD Synchronization Configuration and Installation Guide ........................................ 256 14.1 Introduction.......................................................................................................................... 256 14.1.1 Installing the Recommended GPS Synchronization Kit...................................................... 257 14.2 TDD Synchronization Configuration.................................................................................... 261 14.2.1 TDD Synchronization Enable .............................................................................................. 261 14.2.2 TDD Synchronization Configuration - Standard Mode........................................................ 262 14.2.3 TDD Synchronization Configuration – Expert Mode ........................................................... 265 14.2.4 Confirm Settings and Reboot ODU ..................................................................................... 266 14.2.5 Disarm ODU Following TDD Sync Configuration................................................................ 268 15 E1/T1 Installation Guide ................................................................................................... 269 15.1 Preparing the PTP 600 Series Bridge E1/T1 Cable............................................................ 269 15.2 Making the Connection at the ODU .................................................................................... 270 15.3 Routing the Cable................................................................................................................ 272 15.4 Fitting a Lightning Protection Unit ....................................................................................... 272 15.5 Customer Cable Termination .............................................................................................. 272
1515.6 Lightning Protection and E1/T1........................................................................................... 275 15.6.1 Overview ............................................................................................................................. 275 15.6.2 Recommended Additional Components for E1/T1 Installation. .......................................... 275 15.7 Testing the E1/T1 Installation.............................................................................................. 276 15.7.1 Pre-Power Testing............................................................................................................... 276 16 Data Rate Calculations ..................................................................................................... 277 16.1 Calculation Procedure and Example................................................................................... 277 16.1.1 Procedure............................................................................................................................ 277 16.1.2 Example .............................................................................................................................. 278 16.2 Data Throughput Capacity .................................................................................................. 279 16.3 Range Adjustment Curves ..................................................................................................284 17 AES Encryption Upgrade ................................................................................................. 298 17.1 Configuring Link Encryption ................................................................................................ 298 17.1.1 License Keys ....................................................................................................................... 298 17.1.2 Encryption Mode and Key ................................................................................................... 300 17.2 Wireless Link Encryption FAQ ............................................................................................ 302 17.2.1 Encryption data entry fields are not available ..................................................................... 302 17.2.2 Link fails to bridge packets after enabling link encryption................................................... 302 17.2.3 Loss of AES following downgrade....................................................................................... 302 18 Remote Software Upgrade by TFTP ................................................................................ 303 19 Legal and Regulatory Notices.......................................................................................... 305 19.1 Important Note on Modifications ......................................................................................... 305 19.2 National and Regional Regulatory Notices – PTP 49600 variant ....................................... 305 19.3 National and Regional Regulatory Notices – PTP 59600 variant ....................................... 305 19.3.1 Russia ................................................................................................................................. 305 19.4 National and Regional Regulatory Notices – PTP 58600 variant ....................................... 306 19.4.1 U.S. Federal Communication Commission (FCC) and Industry Canada (IC) Notification.. 306 19.4.2 European Union Notification ............................................................................................... 307 19.4.3 UK Notification..................................................................................................................... 308 19.5 National and Regional Regulatory Notices – PTP 54600 Variant....................................... 309 19.5.1 U.S. Federal Communication Commission (FCC) and Industry Canada (IC) Notification.. 309 19.5.2 European Union Notification ............................................................................................... 310 19.6 National and Regional Regulatory Notices – PTP 25600 Variant....................................... 311 19.6.1 U.S. Federal Communication Commission (FCC) Notification ........................................... 311 19.7 Exposure ............................................................................................................................. 311 19.8 Legal Notices....................................................................................................................... 312
1619.8.1 Motorola Inc. End User License Agreement ....................................................................... 312 19.8.1.1 Definitions............................................................................................................................ 312 19.8.1.2 Grant of License.................................................................................................................. 312 19.8.1.3 Conditions of Use................................................................................................................ 313 19.8.1.4 Title; Restrictions................................................................................................................. 314 19.8.1.5 Confidentiality...................................................................................................................... 314 19.8.1.6 Right to Use Motorola’s Name ............................................................................................315 19.8.1.7 Transfer ............................................................................................................................... 315 19.8.1.8 Updates ............................................................................................................................... 315 19.8.1.9 Maintenance........................................................................................................................ 315 19.8.1.10 Disclaimer............................................................................................................................ 316 19.8.1.11 Limitation of Liability............................................................................................................ 316 19.8.1.12 U.S. Government................................................................................................................. 317 19.8.1.13 Term of License................................................................................................................... 317 19.8.1.14 Governing Law .................................................................................................................... 317 19.8.1.15 Assignment.......................................................................................................................... 317 19.8.1.16 Survival of Provisions.......................................................................................................... 318 19.8.1.17 Entire Agreement ................................................................................................................ 318 19.8.1.18 Third Party Software............................................................................................................ 318 19.8.2 Hardware Warranty in U.S. ................................................................................................. 320 19.8.3 Limit of Liability.................................................................................................................... 321 20 Specifications .................................................................................................................... 322 20.1 System Specifications ......................................................................................................... 322 20.1.1 Wireless PTP 25600 Variant ............................................................................................... 322 20.1.2 Wireless PTP 45600 Variant ............................................................................................... 323 20.1.3 Wireless PTP 48600 Variant ............................................................................................... 324 20.1.4 Wireless PTP 49600 Variant ............................................................................................... 325 20.1.5 Wireless PTP 54600 Variant ............................................................................................... 326 20.1.6 Wireless PTP 58600 Variant ............................................................................................... 327 20.1.7 Wireless PTP 59600 Variant ............................................................................................... 328 20.1.8 Management ....................................................................................................................... 329 20.1.9 Ethernet Bridging................................................................................................................. 329 20.1.10 Physical ............................................................................................................................... 330 20.1.11 Powering ............................................................................................................................. 330 20.1.12 Telecoms Interface.............................................................................................................. 330 20.2 Safety Compliance .............................................................................................................. 331
1720.3 EMC Emissions Compliance............................................................................................... 331 20.3.1 PTP 25600 Variant .............................................................................................................. 331 20.3.2 PTP 45600 Variant .............................................................................................................. 331 20.3.3 PTP 48600 Variant .............................................................................................................. 331 20.3.4 PTP 49600 Variant .............................................................................................................. 331 20.3.5 PTP 54600 Variant .............................................................................................................. 332 20.3.6 PTP 58600 Variant .............................................................................................................. 332 20.4 EMC Immunity Compliance................................................................................................. 333 20.5 Radio Certifications ............................................................................................................. 334 20.5.1 PTP 25600 Variant .............................................................................................................. 334 20.5.2 PTP 45600 Variant .............................................................................................................. 334 20.5.3 PTP 48600 Variant .............................................................................................................. 334 20.5.4 PTP 49600 Variant .............................................................................................................. 334 20.5.5 PTP 54600 Variant .............................................................................................................. 334 20.5.6 PTP 58600 Variant .............................................................................................................. 335 20.6 Environmental Specifications .............................................................................................. 336 20.7 System Connections ........................................................................................................... 336 20.7.1 PIDU Plus to ODU and ODU to Network Equipment Connections..................................... 336 21 FAQs................................................................................................................................... 338 22 Glossary ............................................................................................................................. 340 23 Index ................................................................................................................................... 341
18List of Figures Figure 1 - Typical PTP 600 Series Bridge Deployment........................................................................ 36 Figure 2 - Mod Record Label................................................................................................................ 37 Figure 3 – PTP 600 Series Bridge Outdoor Unit (ODU) with PTP-LPU ............................................... 38 Figure 4 - Power Indoor Unit (PIDU Plus) – PTP 300/500/600 Series................................................. 39 Figure 5 – PIDU Plus Recovery Switch Location ................................................................................. 39 Figure 6 –PTP 300/500/600 Series Bridge PIDU Plus Power Input..................................................... 40 Figure 7 – PTP 600 Series Bridge PIDU Plus to ODU Cable Length Graph ....................................... 41 Figure 8 - External DC Supply Only ..................................................................................................... 41 Figure 9 - External DC Supply and AC Supply.....................................................................................42 Figure 10 - External DC Supply and Redundant AC Supply................................................................ 42 Figure 11 - Remote LED and Recovery Switch Wiring ........................................................................ 43 Figure 12 – PTP 600 Series Bridge Layer Diagram ............................................................................. 47 Figure 13 - 5.8 GHz UK RTTT Channel Avoidance – 30 MHz Channel Bandwidth (Example)........... 59 Figure 14 - 2.5 GHz BRS Band Channel Assignments ........................................................................ 62 Figure 15 - 4.5 GHz Available Spectrum Settings – 30 MHz Channel Bandwidth............................... 63 Figure 16 - 4.5 GHz Available Spectrum Settings – 15 MHz Channel Bandwidth............................... 64 Figure 17 - 4.5 GHz Available Spectrum Settings – 10 MHz Channel Bandwidth............................... 64 Figure 18 - 4.5 GHz Available Spectrum Settings – 5 MHz Channel Bandwidth................................. 65 Figure 19 - 4.9 GHz Available Spectrum Settings - 20 MHz Channel Bandwidth................................ 66 Figure 20 - 4.9 GHz Available Spectrum Settings - 10 MHz Channel Bandwidth................................ 66 Figure 21 - 4.9 GHz Available Spectrum Settings - 5 MHz Channel Bandwidth.................................. 67 Figure 22 - 5.4 GHz Available Spectrum Settings - 30 MHz Channel Bandwidth................................ 67 Figure 23 - 5.4 GHz Available Spectrum Settings - 15 MHz Channel Bandwidth................................ 68 Figure 24 - 5.4 GHz Available Spectrum Settings - 10 MHz Channel Bandwidth................................ 68 Figure 25 - 5.4 GHz Available Spectrum Settings - 5 MHz Channel Bandwidth.................................. 68 Figure 26 - 5.8 GHz Available Spectrum Settings – 30 MHz Channel Bandwidth............................... 70
19Figure 27 - 5.8 GHz Available Spectrum Settings - 15 MHz Channel Bandwidth................................ 71 Figure 28 - 5.8 GHz Available Spectrum Settings - 10 MHz Channel Bandwidth................................ 71 Figure 29 - 5.8 GHz Available Spectrum Settings - 5 MHz Channel Bandwidth.................................. 71 Figure 30 - 5.9 GHz Available Spectrum Settings – 30 MHz Channel Bandwidth............................... 74 Figure 31 - 5.9 GHz Available Spectrum Settings - 15 MHz Channel Bandwidth................................ 75 Figure 32 - 5.9 GHz Available Spectrum Settings - 10 MHz Channel Bandwidth................................ 75 Figure 33 - 5.9 GHz Available Spectrum Settings - 5 MHz Channel Bandwidth.................................. 76 Figure 34 - Co-location of Links Interference Problem - A Simple Example ........................................ 77 Figure 35 TDD Synchronization And Co location Example.................................................................. 78 Figure 36 - Mounting to pole diameters 25mm (1”) to 50mm (2”) ......................................................101 Figure 37 - Integral Safety Loop ......................................................................................................... 102 Figure 38 - Correct Cable Preparation for the Recommended Cable ................................................ 104 Figure 39 - Completed ODU Connector ............................................................................................. 105 Figure 40 - Correct and Incorrect Tightening of Cable Gland ............................................................ 105 Figure 41 – PTP 600 Series Bridge PIDU Plus Connexion................................................................ 106 Figure 42 - Connecting the PIDU+ to the ODU .................................................................................. 107 Figure 43 - Disconnecting the ODU.................................................................................................... 108 Figure 44 - Making the Network Connection at the PIDU Plus .......................................................... 110 Figure 45 – PTP 600 Series PIDU Plus Drip Loop Configuration ...................................................... 112 Figure 46 - Menu Navigation Bar........................................................................................................ 118 Figure 47 - System Summary Page ................................................................................................... 119 Figure 48 - Alarm Warning Triangle ................................................................................................... 120 Figure 49 - Status Page...................................................................................................................... 124 Figure 50 - System Administration Login Page ..................................................................................130 Figure 51 - System Configuration Page ............................................................................................. 131 Figure 52 - LAN Configuration Page .................................................................................................. 133 Figure 53 - Configuration Reboot Page.............................................................................................. 135
20Figure 54 - Configuration Reboot Page - Ethernet Auto Negotiation Disabled.................................. 135 Figure 55 - VLAN Configuration Fields............................................................................................... 136 Figure 56 - LAN Configuration Page - Manual Ethernet Configuration.............................................. 137 Figure 57 - Save and Restore Configuration Page ............................................................................ 138 Figure 58 - Save Configuration File Screen ....................................................................................... 139 Figure 59 – PTP 600 Example Configuration File .............................................................................. 139 Figure 60 - Restore Configuration File Pop Up Screen...................................................................... 140 Figure 61 - Reset Configuration and Reboot Confirmation Pop-up ................................................... 141 Figure 62 - Telecoms Data Entry........................................................................................................ 142 Figure 63 - System Statistics.............................................................................................................. 144 Figure 64 - Detailed Counters Page................................................................................................... 147 Figure 65 - License Key Data Entry.................................................................................................... 152 Figure 66 - Installation Wizard Internet Protocol Configuration.......................................................... 153 Figure 67 - VLAN Warning ................................................................................................................. 154 Figure 68 - Telecoms Configuration Interface .................................................................................... 155 Figure 69 –Wireless Configuration ..................................................................................................... 156 Figure 70 – Fixed Frequency Configuration Example ........................................................................ 162 Figure 71 – Installation Wizard Confirm Configuration....................................................................... 163 Figure 72 - Reboot Confirmation Pop Up ........................................................................................... 164 Figure 73 – Disarm Installation........................................................................................................... 165 Figure 74 - Optional Post Disarm Configuration 1..............................................................................166 Figure 75 - Optional Post Disarm Configuration 2..............................................................................166 Figure 76 – Graphical Installation Screen .......................................................................................... 167 Figure 77 - Software Upgrade ............................................................................................................ 168 Figure 78 - Software Upgrade Image Check...................................................................................... 169 Figure 79 - Software Download Progress Indicator............................................................................ 170 Figure 80 - Software Upgrade Complete............................................................................................ 170
21Figure 81 - Reboot Confirmation Pop Up ........................................................................................... 171 Figure 82 - Spectrum Management as seen from the Master............................................................ 174 Figure 83 - Spectrum Management as seen from the Slave.............................................................. 175 Figure 84 - Example Spectrum Management Graphic ....................................................................... 177 Figure 85 - Active Channel History Screen ........................................................................................ 179 Figure 86 - Spectrum Management Time Series Plot ........................................................................180 Figure 87 - Spectrum Management Fixed Frequency Screen ........................................................... 181 Figure 88 - Spectrum Management Help Page (Fixed Frequency) ...................................................182 Figure 89 - Spectrum Management Master Screen With Operational Restrictions ........................... 183 Figure 90 - Spectrum Management Slave Screen With Operational Restrictions ............................. 184 Figure 91 - PTP 25600 Example of Spectrum Management Page .................................................... 185 Figure 92 - Remote Management....................................................................................................... 186 Figure 93 – Warning when disabling HTTP interface......................................................................... 188 Figure 94 - Remote Management - Diagnostic Alarms ...................................................................... 189 Figure 95 - Diagnostic Plotter ............................................................................................................. 193 Figure 96 - CSV Download................................................................................................................. 194 Figure 97 - Password Change............................................................................................................ 195 Figure 98 - Software License Key Data Entry .................................................................................... 195 Figure 99: License Key reboot Screen ............................................................................................... 196 Figure 100 - Reboot Confirmation Pop Up ......................................................................................... 196 Figure 101 – Properties ...................................................................................................................... 197 Figure 102 - System Reboot............................................................................................................... 198 Figure 103 - Reboot Confirmation Pop Up ......................................................................................... 198 Figure 104 - Recovery Mode Warning Page ...................................................................................... 199 Figure 105 - Recovery Options Page ................................................................................................. 200 Figure 106 - Software Download Progress Indicator Page ................................................................ 201 Figure 107 - Software Download Complete Page .............................................................................. 201
22Figure 108 - Reboot Confirmation Pop Up ......................................................................................... 202 Figure 109 - Confirm Reset to Factory Default Pop Up...................................................................... 203 Figure 110 - IP and Ethernet Erased Successfully page.................................................................... 203 Figure 111 - Reboot Confirmation Pop Up ......................................................................................... 204 Figure 112 - Confirm Erase Configuration Pop Up............................................................................. 204 Figure 113 - Erase Configuration Successful Page ........................................................................... 205 Figure 114 – Erase Configuration - Reboot Confirmation Pop Up ..................................................... 206 Figure 115 – Recovery - Reboot Confirmation Pop Up...................................................................... 207 Figure 116 - ODU mounted in Zones A & B ....................................................................................... 209 Figure 117 - Showing how the use of a Finial enables the ODU to be mounted inside Zone B ........ 210 Figure 118 – Example of PTP-LPU Configuration – Option 1 (Back-to-Back Recommended) ......... 211 Figure 119 - PTP-LPU - Installation Option 2 (Using U-Bolt) ............................................................. 212 Figure 120 - PTP LPU Full Kit ............................................................................................................ 213 Figure 121 - Simplified Circuit Diagram.............................................................................................. 214 Figure 170 - Typical Mast or Tower Installation ................................................................................. 216 Figure 171 - Typical Wall Installation.................................................................................................. 217 Figure 172 – Mast or Tower Installation with E1/T1 ........................................................................... 218 Figure 173 - Wall Installation with E1/T1............................................................................................ 219 Figure 174 – Mast or Tower Installation with GPS Sync Box............................................................. 220 Figure 175 –Wall Installation with GPS Sync Box.............................................................................. 221 Figure 176 - Mast or Tower Installation with GPS Sync Box and E1/T1............................................ 222 Figure 177 - Wall Installation with GPS Sync Box and E1/T1............................................................ 223 Figure 122 – Link End Hardware Test Flowchart ............................................................................... 225 Figure 123 - PTP LPU Test Points ..................................................................................................... 228 Figure 124 – Connectorized 600 Series Bridge Outdoor Unit............................................................ 234 Figure 125 - Connectorized 600 Series bridge Status Page.............................................................. 235 Figure 126 - Connectorized 600 Series bridge ‘System Configuration’ Page.................................... 236
23Figure 127 - Connectorized PTP 600 Series Bridge ‘Installation Wizard’ Page ................................237 Figure 128 - Connectorized 600 Series bridge ‘Confirm Installation’ Page........................................ 238 Figure 129 - Connectorized 600 Series bridge ‘Disarm Installation’ Page......................................... 239 Figure 130 - Forming a Drip Loop ...................................................................................................... 253 Figure 131 - Weatherproofing the Antenna Connections................................................................... 253 Figure 132- Additional Grounding When Using Connectorized Units ................................................ 254 Figure 133 - Lightning Arrestor Mounting........................................................................................... 255 Figure 134 - Polyphaser Assembly..................................................................................................... 255 Figure 135 - GPS Synchronization Unit.............................................................................................. 257 Figure 136 - GPS Synchronization Unit Connections ........................................................................ 258 Figure 137 - TDD Sync - PTP600 Deployment Diagram.................................................................... 259 Figure 138- GPS Synchronization Unit Complete Installation............................................................ 260 Figure 139 - Enabling TDD Synchronization Feature......................................................................... 261 Figure 140 - Configuring TDD Synchronization – Screen 1 ............................................................... 262 Figure 141 - Configuring TDD Synchronization Feature - Screen 2 .................................................. 264 Figure 142 - Configure TDD Synchronisation Expert Mode............................................................... 265 Figure 143 - Confirm TDD Synchronization Configuration Parameters ............................................. 266 Figure 144 - Status Page - TDD Enabled and Synchronized............................................................. 267 Figure 145 - Status Page - TDD Enabled and Not Synchronized ..................................................... 267 Figure 146 - Disarm Following TDD Synchronization ........................................................................ 268 Figure 147 - RJ45 Pin Connection (T568B Color Coding) ................................................................. 269 Figure 148 - PIDU Plus and E1-T1 Connexion .................................................................................. 270 Figure 149 - Disconnecting the ODU.................................................................................................. 271 Figure 150 - Example of a Balun ........................................................................................................ 272 Figure 151 - Diagrammatically Showing the E1-T1 Connections.......................................................273 Figure 152 - Two E1-T1-120 Ohms signal Balanced to PTP600 Interface........................................ 274 Figure 153 – PTP 600 Range Adjustment for Data Rates, Curve A ..................................................285
24Figure 154 – PTP 600 Range Adjustment for Data Rates, Curve B ..................................................286 Figure 155 – PTP 600 Range Adjustment for Data Rates, Curve C .................................................. 287 Figure 156 – PTP 600 Range Adjustment for Data Rates, Curve D .................................................. 288 Figure 157 – PTP 600 Range Adjustment for Data Rates, Curve E ..................................................289 Figure 158 – PTP 600 Range Adjustment for Data Rates, Curve F .................................................. 290 Figure 159 – PTP 600 Range Adjustment for Data Rates, Curve G.................................................. 291 Figure 160 – PTP 600 Range Adjustment for Data Rates, Curve H .................................................. 292 Figure 161 – PTP 600 Range Adjustment for Data Rates, Curve I....................................................293 Figure 162 – PTP 600 Range Adjustment for Data Rates, Curve J................................................... 294 Figure 163 – PTP 600 Range Adjustment for Data Rates, Curve K ..................................................295 Figure 164 – PTP 600 Range Adjustment for Data Rates, Curve L...................................................296 Figure 165 – PTP 600 Range Adjustment for Data Rates, Curve M..................................................297 Figure 166 – AES Software License Key Data Entry ......................................................................... 299 Figure 167 – AES Configuration Data Entry Page ............................................................................. 300 Figure 168 - Configuration Reboot Screen......................................................................................... 301 Figure 169 - Cable Connection Diagram (T568B Color Coding)........................................................ 336
25List of Tables Table 1 - Font types............................................................................................................................ 28 Table 2 - Admonition types................................................................................................................... 29 Table 3 - Power Compliance Margins .................................................................................................. 32 Table 4 - Contact Information ............................................................................................................... 35 Table 5 - PTP 600 Series Bridge Frequency Variants ......................................................................... 49 Table 6 – PTP 25600 Licenses and Region Codes ............................................................................. 51 Table 7 – PTP 45600 Licenses and Region Codes ............................................................................. 51 Table 8 – PTP 48600 Licenses and Region Codes ............................................................................. 52 Table 9 – PTP 49600 Licenses and Region Codes ............................................................................. 53 Table 10 – PTP 54600 Licenses and Region Codes ........................................................................... 54 Table 11 – PTP 58600 Licenses and Region Codes ........................................................................... 55 Table 12 – PTP 59600 Licenses and Region Codes ........................................................................... 57 Table 13 - PTP 25600 Product Variant Channel Plan - FCC BRS-EBS Post-Transition Band ........... 61 Table 14 - Power Reduction in the Upper Band................................................................................... 62 Table 15 – PTP 48600 Channel Center Frequencies .......................................................................... 65 Table 16 – PTP 58600 Band Edge Tx Power Reduction ..................................................................... 73 Table 17 - PTP 25600 - IP Mode – Loss, Output Power and System Threshold Vs Modulation Mode....................................................................................................................................................... 85 Table 18 - PTP 25600 - TDM Mode – Loss, Output Power and System Threshold Vs Modulation Mode.............................................................................................................................................. 86 Table 19 - PTP 45600 - IP Mode – Loss, Output Power and System Threshold Vs Modulation Mode....................................................................................................................................................... 87 Table 20 - PTP 45600 - TDM Mode – Loss, Output Power and System Threshold Vs Modulation Mode.............................................................................................................................................. 88 Table 21 - PTP 48600 - IP Mode – Loss, Output Power and System Threshold Vs Modulation Mode....................................................................................................................................................... 89 Table 22 - PTP 48600 - TDM Mode – Loss, Output Power and System Threshold Vs Modulation Mode.............................................................................................................................................. 90
26Table 23 - PTP 49600 - IP Mode – Loss, Output Power and System Threshold Vs Modulation Mode....................................................................................................................................................... 91 Table 24 - PTP 49600 - TDM Mode – Loss, Output Power and System Threshold Vs Modulation Mode.............................................................................................................................................. 92 Table 25 – PTP 54600 - IP Mode - Link Loss, Output Power, System Threshold Vs Modulation Mode....................................................................................................................................................... 93 Table 26 – PTP 54600 - TDM Mode - Link Loss, Output Power, System Threshold Vs Modulation Mode.............................................................................................................................................. 94 Table 27 - PTP 58600 - IP Mode - Link Loss, Output Power, System Threshold Vs Modulation Mode....................................................................................................................................................... 95 Table 28 - PTP 58600 - TDM Mode - Link Loss, Output Power, System Threshold Vs Modulation Mode.............................................................................................................................................. 96 Table 29 - PTP 59600 - IP Mode - Link Loss, Output Power, System Threshold Vs Modulation Mode....................................................................................................................................................... 97 Table 30 - PTP 59600 - TDM Mode - Link Loss, Output Power, System Threshold Vs Modulation Mode.............................................................................................................................................. 98 Table 31 - Audio indications from the ODU........................................................................................ 114 Table 32 – 600 Series Bridge Factory Configuration Values ............................................................. 150 Table 33 – TDD Structure in TDM Mode............................................................................................ 158 Table 34 - Spectrum Management change state key......................................................................... 178 Table 35 - Spectrum Management Time Series Key .........................................................................180 Table 36 - Spectrum Management Change State Key With Operational Restrictions....................... 184 Table 37 - Protection Requirements................................................................................................... 210 Table 38 - Resistance Table Referenced To The RJ45 at the PIDU+ ............................................... 230 Table 39 - Lateral Force – Imperial .................................................................................................... 232 Table 40 - Lateral Force – Metric ....................................................................................................... 232 Table 41 - Cable Losses per Length .................................................................................................. 241 Table 42 - Allowed Antennas for Deployment in USA/Canada – 5.8 GHz......................................... 242 Table 43 - Allowed Antennas for Deployment in USA/Canada – 5.4 GHz......................................... 246 Table 44 - Common Burst Durations .................................................................................................. 263 Table 45 - Protection Requirements................................................................................................... 275
27Table 46 - Resistance Table Referenced To the E1/T1 Source ........................................................ 276 Table 47 – Data Throughput for PTP 600 Full, Link Symmetry = 1:1, Link Optimization = IP........... 280 Table 48 – Data Throughput for PTP 600 Full, Link Symmetry = 1:1, Link Optimization = TDM.......281 Table 49 – Data Throughput for PTP 600 Full, Link Symmetry = 2:1, Link Optimization = IP........... 282 Table 50 – Data Throughput for PTP 600 Full, Link Symmetry = 2:1, Link Optimization = TDM.......282 Table 51 – Data Throughput for PTP 600 Full, Link Symmetry = Adaptive Link Optimization = IP... 283 Table 52 – Range Adjustment Characteristics ................................................................................... 284 Table 53 - Telecoms Connection Pin Out........................................................................................... 337 List of Equations Equation 1 - Peak power density in the far field ................................................................................... 32 Equation 2 - Path Loss ......................................................................................................................... 83 Equation 3 - Link Loss ........................................................................................................................ 127
1 About This User Guide 281 About This User Guide This guide covers the installation, commissioning, operation and fault finding of the Motorola PTP 600 Series of Point-to-Point Wireless Ethernet Bridges. 1.1 Interpreting Typeface and Other Conventions This document employs distinctive fonts to indicate the type of information, as described in Table 1. Table 1 - Font types Font Type of Information variable width bold Selectable option in a graphical user interface or settable parameter in a web-based interface. constant width regular Literal system response in a command-line interface. constant width italic Variable system response in a command-line interface. constant width bold Literal user input in a command-line interface. constant width bold italicVariable user input in a command-line interface. This document employs specific imperative terminology as follows: x Type means press the following characters. x Enter means type the following characters and then press Enter. x Highlight means click anywhere in a row of data to highlight the entire row. x Select means use the mouse to click on or branch to the menu item that follows. Use this table and the Glossary to aid in interpreting the technical acronyms used throughout this User Guide.
1 About This User Guide 29This document also employs a set of consistently used admonitions. Each type of admonition has a general purpose that underlies the specific information in the box. These purposes are indicated in Table 2. Table 2 - Admonition types Admonition Label General Message Note Informative content that may: x Defy common or cursory logic. x Describe a peculiarity of the 600 Series solutions implementation. x Add a conditional caveat. x Provide a reference. x Explain the reason for a preceding statement or provide backgroundfor what immediately follows. Recommendation Suggestion for an easier, quicker, or safer action or practice. Important Informative content that may: x Identify an indication that you should watch for. x Advise that your action can disturb something that you may not wantdisturbed. x Reiterate something that you presumably know but should always keep in mind. Caution! A notice that the risk of harm to equipment or service exists. Warning! A notice that the risk of harm to person exists.
1 About This User Guide 301.2 Getting Additional Help To get information or assistance as soon as possible for problems that you encounter, follow this procedure: 1. Search this document, the user manuals that support the modules, and the software release notes of supported releases: a. In the Table of Contents for the topic. b. In the Adobe Reader® search capability for keywords that apply (Reader is a registered trademark of Adobe Systems, Incorporated). 2. Visit the Motorola website at www.motorola.com/ptp 3. Ask your Motorola products supplier to help. 4. Gather information from affected units such as: a. the IP addresses and MAC addresses b. the software releases c. the configuration of software features d. any available diagnostic downloads 5. Escalate the problem to Motorola Technical Support as follows. You may either: a. Send e-mail to support.ptp@motorola.com b. Call our 24x7 Technical Support Center on +1 (0) 877 515 0400 (Worldwide) or +44 (0) 808 234 4640 (UK Customers). For warranty assistance, contact your reseller or distributor for the process. 1.3 Sending Feedback We welcome your feedback on the PTP 600 Series Bridge system documentation. This includes feedback on the structure, content, accuracy, or completeness of our documents, and any other comments you have. Send feedback to support.ptp@motorola.com.
2 Avoiding Hazards 312 Avoiding Hazards 2.1 Preventing Overexposure to RF Energy WARNING: To protect from overexposure to RF energy, install the radios for the 600 family of PTP wireless solutions so as to provide and maintain the minimum separation distances from all persons as shown in Table 3. When the system is operational, avoid standing directly in front of the antenna. Strong RF fields are present when the transmitter is on. The Outdoor Unit (ODU) must not be deployed in a location where it is possible for people to stand or walk inadvertently in front of the antenna. At these and greater separation distances, the power density from the RF field is below generally accepted limits for the general population. NOTE: These are conservative distances that include compliance margins. 2.1.1 Calculations for Separation Distances and Power Compliance Margins Limits and guidelines for RF exposure come from: x US FCC limits for the general population. See the FCC web site at http://www.fcc.gov, and the policies, guidelines, and requirements in Part 1 of Title 47 of the Code of Federal Regulations, as well as the guidelines and suggestions for evaluating compliance in FCC OET Bulletin 65. x Health Canada limits for the general population. See the Health Canada web site at http://www.hc-sc.gc.ca/ewh-semt/pubs/radiation/99ehd-dhm237/limits-limites_e.html and Safety Code 6. x EN 50383:2002 Basic standard for the calculation and measurement of electromagnetic field strength and SAR related to human exposure from radio base stations and fixed terminal stations for wireless telecommunication systems (110 MHz - 40 GHz). x ICNIRP (International Commission on Non-Ionizing Radiation Protection) guidelines for the general public. See the ICNIRP web site at http://www.icnirp.de/ and Guidelines for Limiting Exposure to Time-Varying Electric, Magnetic, and Electromagnetic Fields.
2 Avoiding Hazards 32The applicable power density exposure limit from the documents referenced above is: x 10 W/m2 for RF energy in the 2.4-, 5.2-, 5.4-, 5.8- and 5.9 GHz frequency bands. Peak power density in the far field of a radio frequency point source is calculated as follows: Equation 1 - Peak power density in the far field Where Rearranging terms to solve for distance yields: 2.1.1.1 Calculated Distances and Power Compliance Margins Table 3 shows calculated minimum separation distances d, recommended distances and resulting power compliance margins for each frequency band and antenna combination. Table 3 - Power Compliance Margins VariableBand Antenna MaxAverage TransmitPower in Burst (Watt) P(Watt) G S(W/m2)d(m) Recom- mendedDistance(m) Power ComplianceMargin2.5 GHz Integrated 0.25 0.125 63 (18dBi) 10 0.25 2 8.0 4.5 GHz Integrated 0.5 0.4 63 (22dBi) 10 0.71 5 7.0 Integrated 0.5 0.4 63 (22dBi) 10 0.71 5 7.0 4.8 GHz Connectorized 0.5 0.4 (26 dBi) 10 1.1 5 4.5 Integrated 0.25 0.2 63 (22dBi) 10 0.5 2 4.0 4.9 GHz Connectorized 0.25 0.2 (26 dBi) 10 0.8 5 6.25 S = power density in W/m2 P= Maximum Average transmit power capability of the radio, in W G= total Tx gain as a factor, converted from dB d = distance from point source, in m 24.dGPSS SGPd.4.S
2 Avoiding Hazards 33VariableBand Antenna MaxAverage TransmitPower in Burst (Watt) P(Watt) G S(W/m2)d(m) Recom- mendedDistance(m) Power ComplianceMarginIntegrated 0.005 (7dBm) 0.00250200 (23dBi) 10 0.06 5.4 GHz External 4ft Dish 0.00035 (-4.6dBm) 0.000172884 (34.6dBi) 10 0.061 15.9 Integrated 0.32 (25dBm) 0.16 200 (23dBi) 10 0.5 2 4.0 External 2ft Flat Plate 0.32 (25dBm) 0.16 631 (28dBi) 10 0.9 4 4.5 5.8 GHz External 6ft Dish 0.32 (25dBm) 0.16 6310 (38dbi) 10 2.83 10 3.5 Integrated 0.32 (25dBm) 0.16 200 (23dBi) 10 0.5 2 4.0 External 2ft Flat Plate 0.32 (25dBm) 0.16 631 (28dBi) 10 0.9 4 4.5 5.9 GHz External 6ft Dish 0.32 (25dBm) 0.16 6310 (38dbi) 10 2.83 10 3.5 NOTES: x The regulations require that the power used for the calculations is the maximum power in the transmit burst subject to allowance for source-based time-averaging. x At 5.4 GHz and EU 5.8 GHz, the products are generally limited to a fixed EIRP which can be achieved with the Integrated Antenna. The calculations above assume that the maximum EIRP allowed by the regulations is being transmitted. x If there are no EIRP limits in the country of deployment, use the distance calculations for FCC 5.8 GHz for all frequency bands. x At FCC 5.8 GHz, for antennas between 0.6m (2ft) and 1.8m (6ft), alter the distance proportionally to the antenna gain. x At 2.5 GHz, for antennas between 1.2m (4ft) and 3.6m (12ft) the safe distance is increased to between 0.8m (2.6 ft) and 2.4m (7.8 ft).
3 Getting Started 343 Getting Started 3.1 For Your Safety WARNING: Use extreme care when installing antennas near power lines. WARNING: Use extreme care when working at heights. WARNING: The Outdoor Unit (ODU) for the PTP 600 Series Bridge must be properly grounded to protect against lightning. In the USA and Canada it is the user’s responsibility to install the equipment in accordance with Section 810 of the National Electric Code, ANSI/NFPA No.70-1984 or Section 54 of the Canadian Electrical Code. These codes describe correct installation procedures for grounding the outdoor unit, mast, lead-in wire and discharge unit, size of grounding conductors and connection requirements for grounding electrodes. Other regulations may apply in different countries and therefore it is recommended that installation of the outdoor unit be contracted to a professional installer. WARNING: The ODU for the PTP 600 Series Bridge must be grounded to a Protective Earth in accordance with the Local Electrical Regulations. WARNING: It is recommended that the supplied Power Indoor Plus (PIDU Plus) – PTP 600 Series is used to power the PTP 600 Series Bridge ODU. The use of other power sources may invalidate safety approval and affect your warranty. WARNING: When using alternative DC supplies (via the PIDU Plus DC in terminals as described in Section 3.3.3 “Redundancy and Alternative Powering Configurations”), such as battery-backed DC power source, the supply MUST comply with the following requirements: x The voltage and polarity is correct and is applied to the correct terminals in the PIDU Plus x The power source is rated as SELV x The power source is rated to supply at least 1A continuously x The power source cannot provide more than the Energy Hazard Limit as defined by IEC/EN/UL6090, Clause 2.5, Limited Power (The Energy Hazard Limit is 240VA) WARNING: Users and installers should note that the main power supply is the primary disconnect device. WARNING: Safety will be compromised if external quality cables are not used for connections that will be exposed to the weather. WARNING: Safety will be compromised if a different power supply is used than the one supplied by Motorola as part of the system.
3 Getting Started 353.2 WelcomeCongratulations on the purchase of the PTP 600 Series Bridge from Motorola. The PTP 600 Series Bridge is the latest innovation in high-speed wireless networking that lets you deploy wireless networks in areas previously unattainable. 3.2.1 Who Should Use This Guide The guide is for use by the system installer and the end user IT professional. The system installer will require expertise in the following areas: x Outdoor radio equipment installation x Network configuration x Use of web browser for system configuration, monitoring and fault finding 3.2.2 Contact Information Table 4 - Contact Information Postal Address: Motorola, Inc. Unit A1, Linhay Business Park, Eastern Road, Ashburton, Devon. TQ13 7UP United Kingdom Web Site: http://www.motorola.com/ptp Sales Enquiries: sales.ptp@motorola.com Web Support: http://www.motorola.com/ptp/ Email Support: support.ptp@motorola.com All Other Enquiries: info.ptp@motorola.com Telephone Enquiries and Global Support:+1 (0) 877 515 0400 (Toll Free in the USA) and +44 (0) 808 234 4640 (Toll Free in the Uk). 3.2.3 Repair and Service For unit repair or service, contact your service provider or an authorized Motorola Point-to-Point Distributor for Return Material Authorization (RMA) and shipping instructions. Alternatively, contact the PTP Global Technical Support Center to process an RMA.
3 Getting Started 363.3 Product Description This User Manual is specifically written for the 600 family of point-to-point broadband wireless solutions. The PTP 600 Series Bridge has been developed to provide Point-to-Point data connectivity via a 2.5 GHz, 4.5 GHz, 4.8 GHz, 4.9 GHz, 5.4 GHz, 5.8 GHz or 5.9 GHz wireless Ethernet bridge operating at broadband data rates. The PTP 600 Series Bridge is aimed at a wide range of applications. An example application is an enterprise that has a requirement to connect together the Local Area Network (LAN) of two or more buildings as shown in Figure 1. Figure 1 - Typical PTP 600 Series Bridge Deployment The PTP 600 Series Bridge offers true non-line-of-sight (NLOS) operation by using a combination of Orthogonal Frequency Division Multiplexing (OFDM) modulation and Multiple-Input Multiple-Output (MIMO) techniques. These technologies enable the PTP 600 Series Bridge to drive through foliage and around buildings to such an extent that almost universal coverage can be expected at short range. A PTP 600 Series Bridge system consists of a pair of identical devices that are deployed one at each end of the link. At installation, the user sets up one unit as the Master and the other as the Slave. Either unit can be configured as Master or Slave.
3 Getting Started 37Each end of the link consists of: x An integrated (or connectorized -see section 13) outdoor transceiver unit containing all the radio and networking electronics hereafter referred to as the Outdoor Unit (ODU). x An indoor connection box containing a mains power supply, status indicators and network connection port. Hereafter referred to as the Power Indoor Unit Plus (PIDU Plus). A pair of units is normally supplied pre-configured as a link. The network connection to a PTP 600 Series Bridge is made via a 1000BaseT Ethernet connection. Power is provided to the ODU over the 1000BaseT Ethernet connection using a patented non-standard powering technique. Previous releases of the PTP 600 Series Bridge platform used different powering and connection arrangements. Users of equipment prior to “Mod Record 1” should refer to the User Guide shipped with the original equipment. The “Mod Record” label can be found on the back of the ODU as shown in Figure 2. Figure 2 - Mod Record Label Alternatively, the network connection to a PTP 600 Series Bridge can be made using a 1000BaseSX Fiber Optic cable connected directly to the ODU. In this case power is still provided over the 1000BaseT Ethernet connection. In the case of Fiber Optic cable failure the PTP 600 Series Bridge will automatically fall back to the copper Ethernet connection (provided the cable length <=100m [330 ft]). “PTP 600 Series Optical Interface Upgrade Kits” can be obtained from your distributor, reseller or system integrator. Power is fed into the PTP 600 Series Bridge PIDU Plus from the mains via a standard “figure of eight” mains plug. Connection between the ODU and PIDU Plus is made using standard CAT5e outdoor UV resistant cable. Connection between the PIDU Plus and the Network Equipment is made using standard CAT5e cable.
3 Getting Started 383.3.1 The Outdoor Unit (ODU)The ODU is a self-contained unit. It houses both radio and networking electronics. The ODU for the PTP 600 Series Bridge should only be deployed using the supplied PTP 600 Series Bridge PIDU Plus. Figure 3 shows an installation example of a PTP 600 Series ODU with a Motorola lightning protection unit (PTP-LPU). Figure 3 – PTP 600 Series Bridge Outdoor Unit (ODU) with PTP-LPU
3 Getting Started 393.3.2 PIDU Plus – PTP 600 Series Bridge The PTP 600 Series Bridge PIDU Plus is used to generate the ODU supply voltage from the mains supply and inject this supply voltage into the 1000BaseT Ethernet connection to the ODU. Connection uses a CAT5e cable using standard RJ45 wiring. CAUTION: Care should be taken not to connect equipment other than an ODU for the PTP 600 Series Bridge to a PIDU Plus ODU port as equipment damage may occur. The PTP 600 Series Bridge PIDU Plus is not interchangeable with the PTP 400 Series PIDU Plus. Figure 4 - Power Indoor Unit (PIDU Plus) – PTP 300/500/600 Series The front panel contains indicators showing the status of the power and Ethernet connections. The power indicator is illuminated when the PIDU Plus is receiving mains power. The Ethernet indicator normally illuminates when the Ethernet link is working, flashing when there is Ethernet activity. The fact that it lights also indicates that the ODU is powered. At power up the LED will flash 10 times to indicate that a correct start up sequence has occurred. See Section 11 “Fault Finding” for further fault finding information. At the bottom of the PIDU Plus is an entry point for the PIDU Plus to ODU cable, the 1000BaseT Ethernet network port and the Recovery switch. Figure 5 – PIDU Plus Recovery Switch Location
3 Getting Started 40The Recovery switch is used to recover the unit from configuration errors or software image corruption. To put a PTP 600 Series Bridge into Recovery mode the Recovery switch should be pressed then the power applied. The Recovery switch should be kept pressed for at least 20 seconds after the power has been applied. Full instruction on the recovery mode can be found in Section 9 “Recovery Mode”. A simple reboot can be performed by removing and re-applying the mains power to the PTP 600 Series Bridge PIDU Plus. On the left hand side of the PIDU Plus, 48V DC input and output connections can be found. These are used to power the PTP 600 Series Bridge from an external DC source or to provide a level of power supply redundancy, as shown in Section 3.3.3 “Redundancy and Alternative Powering Configurations”. WARNING: When using alternative DC supplies the supply MUST comply with the following requirements: x The voltage and polarity is correct and is applied to the correct terminals in the PIDU Plus x The power source is rated as SELV x The power source is rated to supply at least 1A continuously x The power source cannot provide more than the Energy Hazard Limit as defined by IEC/EN/UL6090, Clause 2.5, Limited Power (The Energy Hazard Limit is 240VA) Also on the left hand side of the PTP 600 Series Bridge PIDU Plus, connectors and jumpers can be found that allow the remote connection of power LED, Ethernet LED and Recovery switch. The connection instructions can be found in Section 3.3.4 “Remote LEDs and Recovery Switch”. The input supply range for the 600 Series PIDU Plus is 90V-264V AC, 47-63Hz. Mains connection to the PIDU Plus is made using a standard “figure of eight” mains lead as shown in Figure 6. Figure 6 –PTP 300/500/600 Series Bridge PIDU Plus Power Input
3 Getting Started 413.3.3 Redundancy and Alternative Powering Configurations NOTE: The use of DC supplies of less than 55v will reduce the usable distance between the PIDU Plus and ODU see Figure 7. Figure 7 – PTP 600 Series Bridge PIDU Plus to ODU Cable Length Graph CAUTION: The maximum distance from the ODU to the connected network equipment is 100m (330 ft) when using 1000BaseT. Powering distances over 100m (330 ft) are only applicable when using a 1000BaseSX (Fiber Optic) connection. 3.3.3.1 External DC Supply Only This configuration is for use where there is no mains supply. Figure 8 - External DC Supply Only
3 Getting Started 423.3.3.2 External DC Supply and AC Supply This configuration provides redundancy through the use of mains and DC supply. Figure 9 - External DC Supply and AC Supply 3.3.3.3 External DC Supply and Redundant AC Supply This configuration guards against mains failure and failure of the DC output of single PTP 300/500/600 PIDU Plus. Figure 10 - External DC Supply and Redundant AC Supply
3 Getting Started 433.3.4 Remote LEDs and Recovery Switch The PTP 600 Series Bridge PIDU Plus provides a facility to connect remote LEDs and Recovery switch allowing the PIDU Plus to be mounted inside an enclosure. At the left hand end of the PIDU Plus under the ODU connection cover can be found a PCB header and three jumpers. Jumpers J906 and J907 should be removed and connection to the remote LEDs and Recovery switch made to J908 as shown in Figure 11. Figure 11 - Remote LED and Recovery Switch Wiring 3.3.5 Cables and connectors The cable used to connect the PTP 600 Series Bridge PIDU Plus to the ODU can be any standard CAT5e type provided that it is suitable for outdoor deployment. Motorola recommends that cables to the specification below be used: Cable: Superior Essex BBDGE CAT 5e Connector Type: Tyco, 5-569278 Gland: Motorola WB1811 CAUTION: Failure to use the recommended (or equivalent) standard of cable may invalidate the system’s safety certification. The cable used to connect the PTP 600 Series Bridge PIDU Plus to the users Network Equipment can be any standard CAT5e Cable.
3 Getting Started 44The PIDU Plus to ODU and the PIDU Plus to Network Equipment cables may be unscreened (UTP) or screened (STP). However, unscreened cables reduce the system’s ability to cope with nearby lightning strikes. If lightning activity is common in the area of deployment, the use of screened cable is highly recommended. See Section 10 “Lightning Protection”. The PIDU Plus provides screen continuity between the ODU and Network Equipment connections. NOTE: The ODU network connection implements automatic MDI/MDI-X sensing and pair swapping allowing connection to networking equipment that require cross-over cables (MDI-X networks) or straight-through cables (MDI Networks). 3.3.6 PTP and Lightning Protection The PTP 600 Series Bridge PIDU Plus meets the low level static discharge specifications identified in Section 20 “Specifications”, but does not provide lightning or surge suppression. Installations will generally require lightning or surge suppression, a separate Ethernet surge suppressor must be used and appropriately earthed. Suitable surge suppressors can be sourced from your Motorola Point-to-Point Distributor or Solutions Provider. See Section 10 “Lightning Protection”. 3.3.7 Mounting Brackets The PTP 600 Series Bridge is supplied with a mounting bracket suitable for mounting the ODU to a pole of 50mm (2”) to 75mm (3”) in diameter. For more details on mounting, see Section 7 “Installation”. The bracket allows for adjustment in both azimuth and elevation. The bracket may be split allowing the pole mount section of the bracket to be mounted to the pole first. This allows the installer to take the weight of the unit and secure it, one handed, with a single mounting bolt. The PIDU Plus can either be desk or wall mounted. The preference is wall mounted with the cables dressed to a cable channel. Wall mounting is achieved by screwing through the mounting lugs on either side of the unit. Remember to leave space for access to the Recovery button. See Section 3.3.2 “PIDU Plus – PTP 600 Series Bridge”.
3 Getting Started 453.3.8 Configuration and Management Configuration and Management of the PTP 600 Series Bridge is implemented using an inbuilt web server hosting a number of Configuration and Management web pages. This approach allows Configuration and Management to be carried out on any standard web browsing technology. The PTP 600 Series Bridge can also be managed remotely using the SNMP management protocol. Connection to the bridge is via the Ethernet connection carrying the bridge network traffic. Connection to the unit is via a preset IP address. This address can be changed via the Network Interface Configuration web page. A full explanation of the available web pages and their use can be found in Section 8 “Web Page Reference”. 3.4 Warranty Motorola’s standard hardware warranty is for one (1) year from date of shipment from Motorola or a Motorola Point-to-Point Distributor. Motorola warrants that hardware will conform to the current relevant published specifications and will be free from material defects in material and workmanship under normal use and service. Motorola shall within this time, at its own option, either repair or replace the defective product within thirty (30) days of receipt of the defective product. Repaired or replaced product will be subject to the original warranty period but not less than thirty (30) days. Motorola warranty for software is described in details in 19.8.1 “Motorola Inc. End User License Agreement”.
4 Product Architecture 464 Product Architecture 4.1 Radio Link The PTP 600 Series Bridge consists of an identical pair of units deployed one at each end of the link. The radio link operates on a single frequency channel in each direction using Time Division Duplex (TDD). One unit is deployed as a master and the other as a slave. The master unit takes responsibility for controlling the link in both directions. The non-line-of-sight (NLOS) aspects of the product are provided by Multiple-Input Multiple-Output (MIMO), coupled with Orthogonal Frequency Division Multiplexing (OFDM) modulation. 4.2 Frequency Bands The PTP 600 Series Bridge has been developed to operate within license exempt frequency bands as well as the licensed 2.5GHz band in the USA. The current product range supports: x USA BRS-EBS Post-Transition band 2.5 GHz (2496 – 2690 GHz) x ETSI 5.4 GHz band B (5.470-5.725 GHz) x ETSI 5.8 GHz band C (5.725–5.850 GHz) and the USA 5 GHz ISM band (5.725-5.850 GHz) x US Federal 4.5 GHz band (4.404-4.596 GHz) x USA and Canada Public Safety 4.9 GHz band x Military 4.8 GHz band x 5.9 GHz band (5.825-5.925 GHz) The PTP 600 Series Bridge has been designed to coexist with other users of the band in an optimal fashion using a combination of Transmit Power Control (TPC), Spectrum Management functionality and Antenna beam shape. In order to maintain link availability, the product employs adaptive modulation techniques that dynamically reduce the data rate in severe or adverse conditions.
4 Product Architecture 474.3 Ethernet Frames The PTP 600 series provides wireless Ethernet bridging between two fixed locations. To be more precise, it forwards Ethernet frames as a two-port transparent heterogeneous encapsulation bridge, meaning that each bridge forwards frames between two dissimilar interfaces (Ethernet and wireless), encapsulating Ethernet MAC frames within a PTP MAC frames for transmission at the wireless interface. A link consisting of a pair of back to back bridges appears to the data network to be very similar to a standard two-port Ethernet bridge. The PTP600 series provides two egress queues in each direction, classifying Ethernet frames into one of the two prioritised queues based on inspection of the user priority field (802.1p) in in a customer (IEEE802.1Q) VLAN tag or provider (IEEE802.1ad) VLAN tag. Untagged frames receive a default priority. The queuing method is strict priority. The bridge does not implement any VLAN functions for bridged frames apart from inspection of the priority field, and consequently the bridge forwards tagged and untagged Ethernet frames regardless of VLAN ID and without modification of any protocol header fields. The PTP 600 series supports a maximum Ethernet frame size of 2000 bytes for bridged traffic. 4.4 Management Function The management function of the PTP 600 Series Bridge is logically equivalent to a separate protocol stack with virtual point of attachment at the Ethernet interface. This is illustrated in Figure 12. Figure 12 – PTP 600 Series Bridge Layer Diagram
4 Product Architecture 48Each unit in the link is manageable through an IP connection. Standard IP protocols are utilized for all management functions, for example, HP, SNMP, etc. The unit can be configured to use a VLAN with a single C-tag or S-tag on the management interfaces. 4.5 Channel Bandwidth and Link Symmetry Control The PTP 600 series provides configurable channel bandwidth in the radio link (5 MHz, 10 MHz, 15 MHz, 20 MHz and 30 MHz depending on the frequency band for the bandwidth choice, see Table 5), and configurable fixed and adaptive link symmetry. Fixed link symmetry supports: x 2:1 x 1:1 x 1:2 Channel bandwidth 5 MHz supports link symmetry 1:1 only. 4.6 Upgradeable Software The PTP 600 Series Bridge is fully software upgradeable. New software images are first downloaded from the Motorola website http://www.motorola.com/ptp to a convenient computer. The image is then uploaded to the ODU via the web management page described in Section 8.3.6 “Software Upgrade”. The compressed image is first loaded into RAM and check-summed. If the compressed image transfer has completed successfully the image is decompressed and written to flash memory. On completion of this process the unit can be rebooted to use the newly uploaded image. Should this process fail, the unit will revert to a protected compressed image installed during manufacturing to allow the unit to be recovered.
5 Radio Link Planning and Regulations 495 Radio Link Planning and Regulations 5.1 Spectrum PlanningThe PTP 600 Series Bridge has seven frequency variants in its product range. Table 5 - PTP 600 Series Bridge Frequency Variants Variant Definition Frequency Coverage VariableChannel WidthChannel Raster 2496-2568 MHz 5, 10, 15 and 30 MHz 5.5 MHz 2572-2614 MHz 5, 10, 15 and 30 MHz 6 MHz PTP 25600 FCC BRS-EBS Post-Transition Band 2618-2690 MHz 5, 10, 15 and 30 MHz 5.5 MHz 4404-4596 MHz 5, 10, 15 MHz 6 MHz PTP 45600 Military 4404-4596 MHz 30 MHz 10 MHz Military 4710-4940 MHz 5, 10, 20 MHz 5 MHz PTP 48600 Military Extended 4710-5000 MHz 5, 10, 20 MHz 5 MHz USA/Canada Public Safety 4940-4990 MHz 5, 10, 20 MHz 5 MHz PTP 49600 Hong Kong Public Safety 4900-4950 MHz 5, 10, 20 MHz 5 MHz 5470-5725 MHz 5,10,15 MHz 6 MHz PTP 54600 ETSI 5 GHz Band B FCC UNII Band 5470-5725 MHz 30 MHz 10 MHz 5725-5850 MHz 5,10,15 MHz 6 MHz PTP 58600 ETSI 5 GHz Band C FCC ISM Band 5725-5850 MHz 30 MHz 10 MHz 5, 10, 15 MHz 6 MHz Russia 5825-5925 MHz 30 MHz 10 MHz 5, 10, 15 MHz 6 MHz PTP 59600 India 5875-5925 MHz 30 MHz 10 MHz NOTE: For PTP 25600, channel widths of 30 MHz are available where allowed by local regulations and subject to some restrictions on channel choice.
5 Radio Link Planning and Regulations 50NOTE: For PTP 54600, PTP 58600 and PTP 59600, use of the product is allowed according to local regulations. There are two alternative methods of spectrum planning: x First an operator can utilize the default spectrum management mode i-DFS (intelligent Dynamic Frequency Selection). This mode uses the PTP 600 Series Bridge ability to measure the interference levels in all channels to build up a picture of the interference / noise levels in all channels. The PTP 600 Series Bridge uses statistical techniques to select the most appropriate transmit and receive channels. The i-DFS mode can be influenced in its channel decision process by selectively barring channels from use. The use of this functionality is described in detail in Section 8.3.7 “Spectrum Management”. x Second, when detailed control of the spectrum allocation is required, it is recommended that the fixed frequency mode is used to statically allocate transmit and receive channels. CAUTION: These methods are not allowed when Radar Detection is enabled. 5.2 Licenses and Region Codes The PTP 600 Series Bridge uses a system of Region Codes to control the operation of the radio link. The user must ensure the product is configured to conform to local regulatory requirements by installing a License Key for the correct Region Code. CAUTION: For the connectorized model, when using external antennas of higher gain than the appropriate integrated antenna, the regulations may require the maximum Tx power to be reduced. To ensure that regulatory requirements are met for connectorized installations, refer to Section 13.6 “Regulatory Issues with Connectorized Units”.
5 Radio Link Planning and Regulations 515.2.1 PTP 25600 Licenses and Region Codes PTP 25600 units may be operated in any of the regions listed in Table 6. When shipped, PTP 25600 units are configured with a license key for Region Code 16. An alternative license key is provided in the Deployment Guide for Region Code 18. NOTE: For a PTP 25600 in Region Code 16, the EIRP limit is approximately 63 dBm + 10 x Log(360/Antenna Azimuth BW). Table 6 – PTP 25600 Licenses and Region Codes RegionCodeLicense / Regulation Frequencies DFSChannel Bandwidth Max Power Notes15, 30 MHz 63 dBm EIRP 10 MHz 63 dBm EIRP FCC Upper 2624 - 2690 MHz 5 MHz 63 dBm EIRP The 30MHzbandwidth is not approved in FCC regions. FCC Middle 2572 - 2614 MHz 5, 10, 15 MHz 63 dBm EIRP 16 FCC Lower 2496 - 2568 MHz 5, 10, 15, 30 MHz 63 dBm EIRP 15 MHz 23 dBm 10 MHz 22 dBm Taiwan Upper 2660 - 2690 MHz 5 MHz 21 dBm Taiwan Middle 2595 - 2625 MHz 5, 10, 15 MHz 23 dBm 18 Taiwan Lower 2565 - 2595 MHz 5, 10, 15 MHz 23 dBm 5.2.2 PTP 45600 Licenses and Region Codes PTP 45600 units may be operated in any of the regions listed in Table 7. When shipped, PTP 45600 units are configured with a license key for Region Code 23. Table 7 – PTP 45600 Licenses and Region Codes RegionCodeLicense / Regulation Frequencies DFSChannel Bandwidth Max Power Notes23 USA Military 4400 - 4600 MHz 5, 10, 15, 30 MHz 25 dBm
5 Radio Link Planning and Regulations 52 5.2.3 PTP 48600 Licenses and Region Codes PTP 48600 units may be operated in any of the regions listed in Table 8. When shipped, PTP 48600 units are configured with a license key for Region Code 23. An alternative license key is provided in the Deployment Guide for Region Code 14. If the link is to be installed in any other permitted region, the user must obtain a new license key from the reseller or distributor. Table 8 – PTP 48600 Licenses and Region Codes RegionCodeLicense / Regulation Frequencies DFSChannel Bandwidth Max Power Notes14 USA/Canada Public Safety 4940 - 4990 MHz 5, 10, 20 MHz 25 dBm See note below. 15 USA Military Extended 4710 - 5000 MHz 5, 10, 20 MHz 27 dBm 23 USA Military 4710 - 4940 MHz 5, 10, 20 MHz 27 dBm NOTE: Region Code 14 Max Power depends upon Antenna Gain: x If Antenna Gain < 26 dBi then Max Power = 25 dBm x If Antenna Gain >= 26 dBi then Max Power = (51 – Antenna Gain) dBm
5 Radio Link Planning and Regulations 53 5.2.4 PTP 49600 Licenses and Region Codes PTP 49600 units may be operated in any of the regions listed in Table 9. When shipped, PTP 49600 units are configured with a license key for Region Code 14. An alternative license key is provided in the Deployment Guide for Region Code 18. Table 9 – PTP 49600 Licenses and Region Codes RegionCodeLicense / Regulation Frequencies DFSChannel Bandwidth Max Power Notes14 USA/Canada Public Safety 4940 - 4990 MHz 5, 10, 20 MHz 25 dBm See note below. 18 Hong Kong Public Safety 4900 - 4950 MHz 5, 10, 20 MHz 25 dBm See note below. NOTE: Region Codes 14 and 18 Max Power depends upon Antenna Gain: x If Antenna Gain < 26 dBi then Max Power = 25 dBm x If Antenna Gain >= 26 dBi then Max Power = (51 – Antenna Gain) dBm
5 Radio Link Planning and Regulations 54 5.2.5 PTP 54600 Licenses and Region Codes PTP 54600 units may be operated in any of the regions listed in Table 10. When shipped, PTP 54600 units are configured with a license key for Region Code 26. Alternative license keys are provided in the Deployment Guide for Region Codes 12 and 13. If the link is to be installed in any other permitted region, the user must obtain a new license key from the reseller or distributor. Table 10 – PTP 54600 Licenses and Region Codes RegionCodeLicense / Regulation Frequencies DFSChannel Bandwidth Max Power Notes7 Full Power + Radar 5470 - 5725 MHz Yes 5, 10, 15, 30 MHz 25 dBm 8 Full Power 5470 - 5725 MHz 5, 10, 15, 30 MHz 25 dBm 30 MHz 30 dBm EIRP 15 MHz 27 dBm EIRP 10 MHz 25 dBm EIRP 12 FCC 5470 - 5725 MHz Yes 5 MHz 22 dBm EIRP 12 ETSI 5470 - 5725 MHz Yes 30 MHz 30 dBm EIRP Before system release 600-06-00 30 MHz 30 dBm EIRP 15 MHz 27 dBm EIRP 10 MHz 25 dBm EIRP 13 Australia, Canada 5470 - 5600 MHz 5650 - 5725 MHz Yes 5 MHz 22 dBm EIRP 20 Thailand 5470 - 5725 MHz 5, 10, 15, 30 MHz 30 dBm EIRP 15 MHz 28 dBm EIRP 10 MHz 27 dBm EIRP 21 Korea 5470 - 5650 MHz 5 MHz 24 dBm EIRP
5 Radio Link Planning and Regulations 55RegionCodeLicense / Regulation Frequencies DFSChannel Bandwidth Max Power Notes30 MHz 30 dBm EIRP 15 MHz 27 dBm EIRP 10 MHz 25 dBm EIRP 26 ETSI 5470 - 5600 MHz 5650 - 5725 MHz Yes 5 MHz 22 dBm EIRP The band 5600 MHz to 5650 MHz is reserved for the use of weather radars 5.2.6 PTP 58600 Licenses and Region Codes PTP 58600 units may be operated in any of the regions listed in Table 11. When shipped, PTP 58600 units are configured with a license key for Region Code 1. An alternative license key is provided in the Deployment Guide for Region Code 25. If the link is to be installed in any other permitted region, the user must obtain a new license key from the reseller or distributor. Table 11 – PTP 58600 Licenses and Region Codes RegionCodeLicense / Regulation Frequencies DFS Channel Bandwidth Max Power Notes1 FCC USA, Canada, Taiwan, Brazil 5725 - 5850 MHz 5, 10, 15, 30 MHz 25 dBm Reduced TX power at band edges 2 China 5725 - 5850 MHz 5, 10, 15, 30 MHz 33 dBm EIRP 3 Australia, Hong Kong 5725 - 5850 MHz 5, 10, 15, 30 MHz 36 dBm EIRP 30 MHz 35 dBm EIRP 15 MHz 34 dBm EIRP 10 MHz 32 dBm EIRP 4 UK 5725 - 5795 MHz 5815 - 5850 MHz Yes 5 MHz 29 dBm EIRP 5795 MHz to 5815 MHz is assigned for Road Transport and Traffic Telematics (RTTT).
5 Radio Link Planning and Regulations 56RegionCodeLicense / Regulation Frequencies DFS Channel Bandwidth Max Power Notes5 Singapore 5725 - 5850 MHz 5, 10, 15, 30 MHz 20 dBm EIRP 30 MHz 33 dBm EIRP 15 MHz 31 dBm EIRP 10 MHz 30 dBm EIRP 6 Eire 5725 - 5850 MHz 5 MHz 27 dBm EIRP 30 MHz 53 dBm EIRP 15 MHz 51 dBm EIRP 10 MHz 50 dBm EIRP 7 Norway 5725 - 5795 MHz 5815 - 5850 MHz Yes 5 MHz 47 dBm EIRP 8 Full Power 5725 - 5850 MHz 5, 10, 15, 30 MHz 25 dBm 30 MHz 44 dBm EIRP 15 MHz 41 dBm EIRP 10 MHz 40 dBm EIRP 11 Korea 5725 - 5825 MHz 5 MHz 37 dBm EIRP 10, 15 MHz 36 dBm EIRP 19 India 5825 - 5850 MHz 5 MHz 33 dBm EIRP 20 Thailand 5725 - 5850 MHz 5, 10, 15, 30 MHz 30 dBm EIRP 30 MHz 35 dBm EIRP 15 MHz 34 dBm EIRP 10 MHz 32 dBm EIRP 22 Germany 5755 - 5850 MHz Yes 5 MHz 29 dBm EIRP 30 MHz 33 dBm EIRP 15 MHz 31 dBm EIRP 10 MHz 30 dBm EIRP 24 Bahrain 5725 - 5850 MHz Yes 5 MHz 27 dBm EIRP 30 MHz 35 dBm EIRP 15 MHz 34 dBm EIRP 10 MHz 32 dBm EIRP 25 ETSI 5725 - 5850 MHz Yes 5 MHz 29 dBm EIRP 1dB reduction required to achieve adjacent channel emmissions
5 Radio Link Planning and Regulations 57RegionCodeLicense / Regulation Frequencies DFS Channel Bandwidth Max Power Notes30 MHz 35 dBm EIRP 15 MHz 34 dBm EIRP 10 MHz 32 dBm EIRP 27 Denmark 5725 - 5795 5815 - 5850 MHz Yes 5 MHz 29 dBm EIRP 5795 MHz to 5815 MHz is assigned for Road Transport and Traffic Telematics (RTTT) 5.2.7 PTP 59600 Licenses and Region Codes PTP 59600 units may be operated in any of the regions listed in Table 12. When shipped, PTP 59600 units are configured with a license key for Region Code 16. An alternative license key is provided in the Deployment Guide for Region Code 17. If the link is to be installed in any other permitted region, the user must obtain a new license key from the reseller or distributor. Table 12 – PTP 59600 Licenses and Region Codes RegionCodeLicense / Regulation Frequencies DFSChannel Bandwidth Max Power Notes15 Unrestricted 5825 - 5925 MHz 5, 10, 15, 30 MHz 25 dBm 16 Russia 5825 - 5925 MHz 5, 10, 15, 30 MHz 25 dBm 10, 15, 30 MHz 36 dBm EIRP 17 India 5875 - 5925 MHz 5 MHz 33 dBm EIRP 10, 15, 30 MHz 36 dBm EIRP 19 India 5825 - 5875 MHz 5 MHz 33 dBm EIRP NOTE: The 5.8 GHz license for India is addressed using both PTP 58600 and PTP 59600 frequency variants.
5 Radio Link Planning and Regulations 58 5.3 Operational Restrictions 5.3.1 Radar Avoidance Radar Avoidance requires that equipment used in the region: x Detects interference from other systems and avoids co-channel operation with these systems, notably radar systems. x Provide on aggregate a uniform loading of the spectrum across all devices, that is, Fixed Frequency operation is not allowed. Radar avoidance is not applicable to the PTP 25600 product or the PTP 45600 product. To address the primary aims, the Spectrum Management algorithm implements a radar detection function which looks for impulsive interference on the operating channel only. If impulsive interference is detected, Spectrum Management will mark the current operating channel as having detected radar (unavailable channel) and initiate a channel hop to an available channel. The previous operating channel will remain in the unavailable state for thirty minutes after the last impulsive interference pulse was detected. After the thirty minutes have expired the channel will be returned to the usable channel pool. The equipment can only transmit on available channels, of which there are none at initial power up. The radar detection algorithm will always scan a usable channel for 60 seconds for radar interference before making the channel an available channel. This compulsory channel scan will mean that there is a 60 seconds service outage every time radar is detected and that the installation time is extended by 60 seconds even if there is found to be no radar on the channel. NOTE: On system installation or start-up this extends the initial scan time of the Master unit by 60 seconds. To address the “provide aggregate uniform loading of the spectrum across all devices” requirement, the channel selection algorithm will choose a channel at random from a list of useable channels. The channel selection algorithm is initiated at link initialization and when radar interference is detected.
5 Radio Link Planning and Regulations 595.3.2 RTTT Avoidance and Other Channel Use Restrictions Where regulatory restrictions apply to certain channels these channels are barred. RTTT avoidance may be necessary in all channel bandwidths. The number of channels barred is dependant on the channel raster selected. For example see the effect of the UK RTTT channel restrictions in the 30 MHz bandwidth (Figure 13), where blocks in red indicate channels that are barred. Barred channels are indicated by a “No Entry” symbol displayed on the “Spectrum Management” web page, see Section 8.3.9 “Spectrum Management Control - With Operational Restrictions”. Figure 13 - 5.8 GHz UK RTTT Channel Avoidance – 30 MHz Channel Bandwidth (Example)
5 Radio Link Planning and Regulations 605.3.3 Radar Avoidance, i-DFS and Variable (Narrow) Bandwidth Operation PTP 600 Series bridges do not support operation with 5, 10 or 15 MHz channel bandwidth in regions where radar avoidance is enabled. NOTE: Radar avoidance requirements in the 5.4GHz band in the EU is detailed in specification EN 301-893 version 1.4.1 and in the US in the specification FCC part 15.437. Radar avoidance at 5.8GHz is applicable to EU operation and the requirements are currently as defined in EN 302 502. 5.4 Variable Channel Bandwidth Operation The selection of Channel Bandwidth depends upon the PTP bridge variant: x For PTP 25600, PTP 54600, PTP 58600 and PTP 59600, Channel Bandwidth may be 30, 15, 10 or 5 MHz. x For PTP 48600 and PTP 49600, Channel Bandwidth may be 20, 10 or 5 MHz. The 30MHz channel widths are available where allowed by local regulations and subject to some restrictions on channel choice. Lite versions of the PTP 600 products do not support a Channel Bandwidths of 5 MHz. Configuration of the variable bandwidth operation must be symmetric, that is, the Transmit and receive channels must use identical Channel Bandwidths. 5.5 PTP 25600 Specific Frequency Planning Considerations The supported 2.5GHz frequency range is split into three bands, according to the bands specified in the FCC BRS-EBS Post-Transition Band plan (only for PTP 25600 and Region Code 16): x Lower: 2496 MHz to 2572 MHz with a 5.5MHz channel raster (76 MHz total). x Middle: 2572 MHz to 2614 MHz with a 6 MHz channel raster (42 MHz total). x Upper: 2618 MHz to 2690 MHz with a 5.5 MHz channel raster (76 MHz total). NOTE: For the PTP 25600 product variant, the unit will only operate in Fixed Frequency mode, and the user is unable to select i-DFS.
5 Radio Link Planning and Regulations 61The PTP 25600 product variant support channel centre frequencies as specified in Table 13. Table 13 - PTP 25600 Product Variant Channel Plan - FCC BRS-EBS Post-Transition Band Block Channel Bandwidth (MHz) Channel Centre Frequencies (MHz) 5 2499.25, 2504.75, 2510.25, 2515.75, 2521.25, 2526.75, 2532.25, 2537.75, 2543.25, 2548.75, 2554.25, 2559.75, 2565.25 10 2502, 2507.5, 2513, 2518.5, 2524, 2529.5, 2535, 2540.5, 2546, 2551.5, 2557, 2562.5 15 2504.75, 2510.25, 2515.75, 2521.25, 2526.75, 2532.25, 2537.75, 2543.25, 2548.75, 2554.25, 2559.75 Lower Band Segment 30 2513, 2524, 2535, 2546 5 2575, 2581, 2587, 2593, 2599, 2605, 2611 10 2578, 2584, 2590, 2596, 2602, 2608 15 2581, 2587, 2593, 2599, 2605 Middle Band Segment 30 Not supported 5 2626.75, 2632.25, 2637.75, 2643.25, 2648.75, 2654.25, 2659.75, 2665.25, 2670.75, 2676.25, 2681.75, 2687.25 10 2629.5, 2635, 2640.5, 2646, 2651.5, 2657, 2662.5, 2668, 2673.5, 2679, 2684.5 15 2632.25, 2637.75, 2643.25, 2648.75, 2654.25, 2659.75, 2665.25, 2670.75, 2676.25, 2681.75 Upper Band Segment 30 2640.5, 2651.5, 2662.5, 2673.5 The channel centre frequencies listed above have been selected to align with the so-called post-transition BRS channels as shown in Figure 14. NOTE: The PTP 25600 frequency variant supports three portions of the BRS spectrum allocation. These are configurable at installation and constrain the wireless to operate in a limited portion of the Spectrum. The three frequency bands are as shown in Figure 14: Band 1: channels A, B, C and D (16.5 MHz blocks) Band 2: channels A through G (6 MHz blocks) Band 3: channels E, F, G and H (16.5 MHz blocks)
5 Radio Link Planning and Regulations 62Figure 14 - 2.5 GHz BRS Band Channel Assignments 5.5.1 Power Reduction in the Upper Band Operation in the Upper Band Segment (Table 14) will result in a lower maximum transmit power and the reduction depends on the channel bandwidth. The maximum power levels produced are shown below. Table 14 - Power Reduction in the Upper Band Band 15MHz Channel 10MHz Channel 5MHz Channel Lower Band Segment 23dBm 23dBm 23dBm Middle Band Segment 23dBm 23dBm 23dBm Upper Band Segment 23dBm 22dBm 21dBm
5 Radio Link Planning and Regulations 635.6 PTP 45600 Specific Frequency Planning Considerations Adjustment of the lower centre frequency allows the operator to slide the available frequency settings up and down the 4.5 GHz band. Figure 15 to Figure 18 show the available spectrum settings for the 30 MHz, 15 MHz, 10 MHz and 5 MHz channel bandwidths All channel centre frequencies may not be available for all Region Codes. . Figure 15 - 4.5 GHz Available Spectrum Settings – 30 MHz Channel Bandwidth
5 Radio Link Planning and Regulations 64Figure 16 - 4.5 GHz Available Spectrum Settings – 15 MHz Channel Bandwidth Figure 17 - 4.5 GHz Available Spectrum Settings – 10 MHz Channel Bandwidth
5 Radio Link Planning and Regulations 65Figure 18 - 4.5 GHz Available Spectrum Settings – 5 MHz Channel Bandwidth 5.6.1 PTP 45600 Raster Considerations The PTP 45600 variant operates on a 10 MHz channel raster (for 30 MHz channel bandwidth) and 6 MHz for the variant channel bandwidths 5, 10 and 15 MHz. The channel raster is set to even centre frequencies. See Figure 15 to Figure 18. 5.6.2 PTP 45600 Transmit Power Reduction at the Band Edges The PTP 45600 product variant does not apply any band edge power reduction. 5.7 PTP 48600 Specific Frequency Planning Considerations Adjustment of the lower centre frequency allows the operator to slide the available frequency settings up and down the 4.8 GHz band in steps of 1 MHz. Table 15 shows the available Channel Center Frequencies for each Channel Bandwidth. Table 15 – PTP 48600 Channel Center Frequencies RegionCodeChannel Bandwidth Available Channel Center Frequencies 20 MHz 4720 MHz – 4990 MHz 10 MHz 4715 MHz – 4995 MHz 15 5 MHz 4715 MHz – 4997 MHz 20 MHz 4720 MHz – 4930 MHz 10 MHz 4715 MHz – 4935 MHz 23 5 MHz 4715 MHz – 4937 MHz
5 Radio Link Planning and Regulations 66 5.8 PTP 49600 Specific Frequency Planning Considerations Adjustment of the lower centre frequency allows the operator to slide the available frequency settings up and down the 4.9 GHz band. Figure 19 to Figure 21 show the available spectrum settings for the 20 MHz, 10 MHz and 5 MHz channel bandwidths All channel centre frequencies may not be available for all Region Codes. Figure 19 - 4.9 GHz Available Spectrum Settings - 20 MHz Channel Bandwidth Figure 20 - 4.9 GHz Available Spectrum Settings - 10 MHz Channel Bandwidth
5 Radio Link Planning and Regulations 67Figure 21 - 4.9 GHz Available Spectrum Settings - 5 MHz Channel Bandwidth 5.9 PTP 54600 Specific Frequency Planning Considerations Adjustment of the lower centre frequency allows the operator to slide the available frequency settings up and down the 5.4 GHz band. Figure 22 to Figure 25 show the available spectrum settings for the 30 MHz, 15 MHz, 10 MHz and 5 MHz channel bandwidths All channel centre frequencies may not be available for all Region Codes. Figure 22 - 5.4 GHz Available Spectrum Settings - 30 MHz Channel Bandwidth
5 Radio Link Planning and Regulations 68Figure 23 - 5.4 GHz Available Spectrum Settings - 15 MHz Channel Bandwidth Figure 24 - 5.4 GHz Available Spectrum Settings - 10 MHz Channel Bandwidth Figure 25 - 5.4 GHz Available Spectrum Settings - 5 MHz Channel Bandwidth
5 Radio Link Planning and Regulations 695.9.1 PTP 54600 Raster Considerations: The PTP 54600 variant operates on a 10 MHz channel raster (for 30 MHz channel bandwidth) and 6 MHz for the variant channel bandwidths 5, 10 and 15 MHz. The channel raster is set to even centre frequencies. See Figure 22 to Figure 25. 5.9.2 Transmit Power Reduction at the Band Edges The PTP 54600 product variant does not apply any band edge power reduction.
5 Radio Link Planning and Regulations 705.10 PTP 58600 Specific Frequency Planning Considerations Adjustment of the lower center frequency allows the operator to slide the available frequency settings up and down the 5.8 GHz bands. Figure 26 to Figure 29 show the available spectrum settings for the 30 MHz, 15 MHz, 10 MHz and 5 MHz channel bandwidths in those regions where the band edge is 5850 MHz (for example FCC). All channel centre frequencies may not be available for all Region Codes. Figure 26 - 5.8 GHz Available Spectrum Settings – 30 MHz Channel Bandwidth
5 Radio Link Planning and Regulations 71Figure 27 - 5.8 GHz Available Spectrum Settings - 15 MHz Channel Bandwidth Figure 28 - 5.8 GHz Available Spectrum Settings - 10 MHz Channel Bandwidth Figure 29 - 5.8 GHz Available Spectrum Settings - 5 MHz Channel Bandwidth
5 Radio Link Planning and Regulations 725.10.1 PTP 58600 Raster Considerations The PTP 58600 variant operates on a 10 MHz channel raster (for 30 MHz channel bandwidth) and 6 MHz for the variant channel bandwidths 5, 10 and 15 MHz. The channel raster is set to even center frequencies. See Figure 26 to Figure 29.
5 Radio Link Planning and Regulations 735.10.2 PTP 58600 Transmit Power Reduction at the Band Edges Operation at or near the 5.8 GHz band edges can results in a lower maximum transmit power. In some configurations the PTP 600 Series Bridge solution reduces the power when operating at the edge channels. The amount of reduction, if any, is dependant on the region code of the region of operation. This currently only affects systems configured with Region Code 1. The power reductions in the edge channels for 5 MHz, 10 MHz, 15 MHz and 30 MHz are presented in Table 16 (for region code 1 ONLY). Table 16 – PTP 58600 Band Edge Tx Power Reduction Channel Width (MHz) Power Levels for Channel Centre 510 15 305730 25 N/A N/A N/A 5732 25 23 N/A N/A 5734 25 25 1N/A N/A 5736 25 25 23 N/A 5738 25 25 25 N/A 5740 25 25 25 17 5742 - 5750 25 25 25 21 5752 - 5822 25 25 25 25 5824 - 5832 25 25 25 21 5834 25 25 25 17 5840 25 25 23 N/A 5842 25 23 19 N/A 5844 25 19 N/A N/A 5846 23 N/A N/A N/A
5 Radio Link Planning and Regulations 745.11 PTP 59600 Specific Frequency Planning Considerations Adjustment of the lower center frequency allows the operator to slide the available frequency settings up and down the 5.9 GHz bands. Figure 30 to Figure 33 show the available spectrum depending on the channel width (30 MHz, 15 MHz, 10 MHz and 5 MHz respectively). Figure 30 - 5.9 GHz Available Spectrum Settings – 30 MHz Channel Bandwidth
5 Radio Link Planning and Regulations 75 Figure 31 - 5.9 GHz Available Spectrum Settings - 15 MHz Channel Bandwidth Figure 32 - 5.9 GHz Available Spectrum Settings - 10 MHz Channel Bandwidth
5 Radio Link Planning and Regulations 76Figure 33 - 5.9 GHz Available Spectrum Settings - 5 MHz Channel Bandwidth 5.11.1 PTP 59600 Raster Considerations The PTP 59600 variant operates on a 10 MHz channel raster (for 30 MHz channel bandwidth) and 6 MHz for the variant channel bandwidths 5, 10 and 15 MHz. The channel raster is set to even center frequencies. See Figure 30 to Figure 33.
5 Radio Link Planning and Regulations 775.12 Time Division Duplex (TDD) Synchronization 5.12.1 Introduction In a TDD system, a radio transmits for a portion of the radio frame and receives in a different portion of the frame. Motorola PTP600 links consist of a Master unit and a Slave unit with the Master transmitting for the first part of the radio frame (Slave receiving) and the Slave transmitting in the remainder of the radio frame (Master receiving). The portion of the frame apportioned to each period can be dynamic, for example in IP optimisation mode where the split is a function of the offered traffic in each direction. However, if the frames of the two links are not aligned in time, then an interference mechanism exists where one Master unit may be transmitting when the Master unit from the other link is receiving. A similar mechanism exists for Slave units. The level of interference becomes very signicant when the units are located in close proximity, for example when units are located on the same mast. This problem is illustrated in Figure 34 where it can be seen that transmissions from Master unit A overlap with the receive portion of Master unit B and vice versa. Figure 34 - Co-location of Links Interference Problem - A Simple Example
5 Radio Link Planning and Regulations 78Interference can be minimised by increasing the radio channel separation between units which are in close proximity, for example for units on the same mast. This may not always be possible if the mast is hosting a large number of links and if spectrum is limited. Also, the achieved reduction may not always be sufficient. Another way to reduce interference is to reduce the transmit power of an interfering radio. Again, this may not always be possible if the link causing the interference does not itself have sufficient radio gain margin to allow the power of its radios to be reduced. 5.12.2 TDD Synchronization TDD synchronization overcomes these issues by aligning the radio frame of all links in the network such that all Master units transmit at the same time and receive at the same time. This eliminates interference between units on the same mast if the units on the mast are configured as Master units. This illustrated in Figure 28 where the frames of the two links are aligned in time. Figure 35 TDD Synchronization And Co location Example Due to propagation delay, a mechanism exists where an interfering signal from a remote Master unit arrives at a victim Master delayed in time. This would occur when Master units are installed on different masts. Similarly, an interfering signal from a remote Slave unit will arrive at a victim Slave unit delayed in time. Correct configuration of TDD synchronization ensures that the delayed signals do not overlap with the receive portion of the victim frame. In order to eliminate the interference from delayed signals, the configuration and the resulting TDD frame structure will actually depend upon characteristics of the overall network such as the longest link and the maximum distance between interfering Master units and interfering Slave units. The installation wizard requests that these parameters are entered when TDD synchronization is enabled. This is covered in detail in Section 14 “TDD Synchronization Configuration and Installation Guide”.
5 Radio Link Planning and Regulations 795.12.3 Implementation of TDD SynchronizationTDD synchronization is achieved by connecting each Master unit to a GPS Synchronization Unit. Installation details are covered in Section 14 “TDD Synchronization Configuration and Installation Guide”. The GPS unit provides the Master unit with a precise 1Hz signal where the leading edge occurs at the same point in time for all units in the network which have been locked to the GPS Satellite system. The Master radio then aligns its radio frame to start on the leading edge of the 1Hz signal. 5.12.4 System Constraints with TDD Synchronization Enabled The following constraints apply when TDD synchronization is enabled: x As the radio frame needs to be aligned across the network, the apportioning of the frame between the two link directions can no longer be dynamic. The split is fixed at 50:50. x In order that the start of the radio frame can always align with the leading edge of the 1Hz signal, the radio frame duration must be an integer fraction of 1s. The exact frame length is calculated by the installation wizard as a function of the network characteristics such as longest link, and longest distance between interfering masters and interfering slaves. x TDD synchronisation is a feature which enables a network of links to co-exist. A major part of network design is concerned with frequency planning which is required in order to minimise interference between links. It is therefore reasonable that when TDD synchronisation is enabled, the radio is configured for a specific fixed frequency selected as part of the network design. As such, Intelligent Dynamic Frequency Selection (iDFS) is disabled. x It is not possible to enable TDD synchronisation in regions where radar avoidance is enabled. This is because radar avoidance requires the random selection of frequency after detection, rather than a fixed frequency which is selected as part of a network design.
5 Radio Link Planning and Regulations 80 5.13 Color Codes Color Codes allow the user to optimize densely populated synchronized PTP 600 networks. There are two such parameters to be configured for each link: x Tx Color Code x Rx Color Code The Color Code parameters have 5 possible values: A, B, C, D and E. Different color codes have subtly different transmit waveforms. Setting the wanted signal Colour Code and the interfering signal Color Code to different values has the effect of de-correlating the two co-channel, synchronized signals, making the interference appear more noise-like to the victim. This improves synchronized, co-channel performance by up to 7 dB. This feature allows users to plan very dense networks where signal to interference levels below 14 dB can now be tolerated. This was previously not possible for synchronized, co-channel interference. The configuration of Tx and Rx Color Code is performed as part of the installation process. See Section 8.3.4.4 “Wireless Configuration”. 5.14 DistanceThe PTP 600 Series Bridge will operate at ranges from 100 m (330 ft) to 200 km (124 miles), within 3 modes: 0-40km (0-25 miles), 0-100km (0-62 miles) and 0-200km (0-124 miles). Operation of the system will depend on obstacles in the path between the units. Operation at 40 km (25 miles) or above will require a near line-of-sight path. Operation at 100m (330 ft) could be achieved with one unit totally obscured from the other unit, but with the penalty of transmitting at higher power in a non-optimal direction, thereby increasing interference in the band. This subject is covered in more detail in Section 6.1.3 “Path Loss Considerations“.
5 Radio Link Planning and Regulations 815.15 Networking Information The PTP 600 Series Bridge operates as a transparent Ethernet bridge. Although each unit requires an IP address, this IP address is for management purposes only, and it plays no part in the forwarding of bridged Ethernet frames. IP addresses are assigned during initial configuration as described in Section 7.2 “Installation Procedure”. 5.16 Lightning ProtectionThe amount of lightning protection is dependent on regulatory requirements and the end user requirements. The standard ODU for the PTP 600 Series Bridge is fitted with surge limiting circuits and other features to minimize the risk of damage due to nearby lightning strikes. These standard features may require some additional equipment to be configured as part of the system installation to be fully effective. CAUTION: Motorola recommends the use of screened cable and Lightning Protection units to protect connected equipment from nearby strikes. NOTE: The PTP 600 Series Bridge is not designed to survive direct lightning strikes. For this reason the unit should not be installed as the highest point in a localized area, unless specific precautions are taken. See Section 10 “Lightning Protection”. 5.17 Electrical RequirementsThe PTP 600 Series Bridge requires one mains supply outlet at each end of the link to plug in the PIDU Plus units. See Section 3.3.2 “PIDU Plus – PTP 600 Series Bridge”.
6 Site Planning 826 Site Planning 6.1 Site Selection CriteriaThe following are guidelines for selecting the installation location of the ODU and PIDU Plus for a PTP 600 Series Bridge. 6.1.1 ODU Site Selection When selecting a site for the ODU the following should be taken into consideration: x It is not possible for people to stand or walk inadvertently in front of the antenna x Height and location to achieve the best radio path x Height in relation to other objects with regard to lightning strikes x Aesthetics and planning permission issues x Distance from the ODU and connected Network equipment (Maximum cable run from the ODU to the connected equipment is 100m [330 ft]) x Distance from the PIDU Plus to the ODU (Maximum cable run from the PIDU Plus to the ODU is 300m [990 ft] when using the Fiber interface) x If using the GPS Sync Unit, ensure that it is exposed to an unobstructed path to the sky. Please refer to the “GPS Synchronization Unit Kit” User Manual delivered with the kit. 6.1.2 PTP 600 Series Bridge PIDU Plus Site SelectionWhen selecting a site for the PIDU Plus the following should be taken into consideration: x Availability of a mains electricity supply x Accessibility for viewing status indicators and pressing Recovery switch.
6 Site Planning 836.1.3 Path Loss Considerations The path loss is the amount of attenuation the radio signal undergoes between the two ends of the link. The path loss is the sum of the attenuation of the path if there were no obstacles in the way (Free Space Path Loss), the attenuation caused by obstacles (Excess Path Loss) and a margin to allow for possible fading of the radio signal (Fade Margin). Equation 2 - Path Loss capabilityseasonalfadeexcessspacefree LLLLL _ Where spacefreeL_ Free Space Path Loss (dB) excessL Excess Path Loss (dB) fadeL Fade Margin Required (dB) seasonalL Seasonal Fading (dB) capabilityL Equipment Capability (dB) 6.1.4 Definitions The equipment capability is given in Table 17 to Table 30. Each table gives Link Loss, Output Power and System Thresholds for PTP 600 Series Bridge in all modulation modes for all available channel bandwidths. Adaptive Modulation will ensure that the highest throughput that can be achieved instantaneously will be obtained taking account of propagation and interference. The calculation of Equation 1 needs to be performed to judge whether a particular link can be installed. When the link has been installed, web pages provide information about the link loss currently measured by the equipment both instantaneously and averaged. The averaged value will require maximum seasonal fading to be added, and then the radio reliability of the link can be computed. For minimum error rates on TDM links the maximum modulation mode should be limited to 64QAM 0.75. The values for (BPSK) are static receive sensitivity measurements. The other values are static receive sensitivity measurements with an AMOD threshold applied. The AMOD threshold applied is for a benign radio channel.
6 Site Planning 84Sensitivity: Sensitivity is defined as the combined receive input signal level on both horizontal and vertical inputs that produces a Null BER Error ratio of 3x10-7. Output Power: The output power is for a centre channel in Region 1. The output power will be reduced on the edge channels and may vary if different region codes are selected. AMOD Threshold: The AMOD threshold is the combined receive input signal level on both horizontal and vertical inputs that results in the link consistently entering the receive modulation mode under consideration as the signal level is increased. System Threshold: Thresholds for all modes except BPSK are for the relevant link optimization AMOD thresholds. System threshold for BPSK is the RPSK receive sensitivity. Max Link Loss: The maximum link loss for each modulation mode is derived from the AMOD threshold for that mode (sensitivity threshold for BPSK) and the maximum Region 1 centre channel output power. The figures assume integral antennas are used, with gain depending upon frequency band as follows: x 23 dBi (5.9 GHz, 5.8 GHz and 5.4 GHz) x 22 dBi (4.8 GHz and 4.9 GHz) x 21.5 dBi (4.5 GHz) x 18 dBi (2.5 GHz)
6 Site Planning 85 6.1.5 PTP 25600 Product Variant - Link Loss, Output Power and System Threshold versus Modulation Mode PTP 25600 system threshold figures are given in the following tables: x Table 17 - IP Mode. x Table 18 - TDM Mode. These figures assume that antenna gain is 23 dBi. Table 17 - PTP 25600 - IP Mode – Loss, Output Power and System Threshold Vs Modulation ModeThreshold Value (dBm) Output Power (dBm) MaximumLink Loss (dB) Channel Bandwidth (MHz) ModulationMode5MHz10MHz15MHz30MHzAllBands 5MHz10MHz15MHz30MHzBPSK 0.63 single -97.57 -95.14 -92.95 -90.39 +23 156.6 154.1 152.0 149.4 QPSK 0.63 single -93.87 -90.66 -90.49 -86.65 +23 152.9 149.7 146.6 145.7 QPSK 0.87 single -90.72 -87.60 -87.45 -83.94 +23 149.7 146.6 146.5 142.9 16QAM 0.63 single -89.06 -85.98 -86.02 -82.11 +23 148.0 145.5 145.0 140.4 16QAM 0.63 dual -86.71 -83.93 -83.96 -79.43 +23 145.7 142.9 143.0 138.4 16QAM 0.87 single -84.21 -82.45 -80.52 -76.50 +23 143.2 141.4 139.5 135.5 16QAM 0.87 dual -80.97 -77.65 -77.44 -72.92 +23 140.0 136.6 136.4 131.9 64QAM 0.75 single -81.61 -79.24 -77.42 -73.45 +23 140.6 138.2 136.4 132.4 64QAM 0.75 dual -77.83 -74.71 -74.34 -69.81 +23 136.8 133.7 133.3 128.8 64QAM 0.92 single -78.80 -76.25 -74.42 -70.27 +23 137.8 135.2 133.4 129.3 64QAM 0.92 dual -75.46 -71.32 -71.88 -66.51 +23 134.5 130.3 130.9 125.5 256QAM 0.81 single -77.17 -74.94 -72.92 -68.81 +23 136.2 133.9 131.9 127.8 256QAM 0.81 dual -73.53 -70.07 -69.68 -65.14 +23 132.5 129.1 128.7 124.1
6 Site Planning 86 Table 18 - PTP 25600 - TDM Mode – Loss, Output Power and System Threshold Vs Modulation ModeThreshold Value (dBm) Output Power (dBm)MaximumLink Loss (dB) Channel Bandwidth (MHz) ModulationMode5MHz10MHz15MHz30MHzAllBands 5MHz10MHz15MHz30MHzBPSK 0.63 single -97.57 -95.14 -92.95 -90.39 +23 156.6 154.1 152.0 149.4 QPSK 0.63 single -91.55 -89.12 -88.20 -85.19 +23 150.6 148.1 147.2 144.2 QPSK 0.87 single -88.28 -85.58 -85.12 -81.51 +23 147.3 144.6 144.1 140.5 16QAM 0.63 single -86.37 -83.86 -83.45 -79.36 +23 145.4 142.9 142.5 138.4 16QAM 0.63 dual -84.18 -80.79 -80.73 -76.62 +23 143.2 139.8 139.7 135.6 16QAM 0.87 single -81.68 -78.11 -77.27 -73.64 +23 140.7 137.1 136.3 132.6 16QAM 0.87 dual -78.64 -74.42 -74.30 -70.03 +23 137.6 133.4 133.3 129.0 64QAM 0.75 single -78.76 -75.24 -74.19 -70.55 +23 137.8 134.2 133.2 129.6 64QAM 0.75 dual -75.39 -70.99 -70.86 -66.72 +23 134.4 130.0 129.9 125.7 64QAM 0.92 single -76.04 -73.44 -72.15 -68.64 +23 135.0 132.4 131.2 127.6 64QAM 0.92 dual -73.49 -69.25 -68.92 -64.84 +23 132.5 128.2 127.9 123.8 256QAM 0.81 single -73.39 -71.63 -69.11 -65.41 +23 132.4 130.6 128.1 124.4 256QAM 0.81 dual -70.44 -67.58 -65.89 -61.62 +23 129.4 126.6 124.9 120.6
6 Site Planning 876.1.6 PTP 45600 Product Variant - Link Loss, Output Power and System Threshold versus Modulation Mode PTP 45600 system threshold figures are given in the following tables: x Table 19 - IP Mode. x Table 20 - TDM Mode. These figures assume that antenna gain is 23 dBi. Table 19 - PTP 45600 - IP Mode – Loss, Output Power and System Threshold Vs Modulation ModeThreshold Value (dBm) Output Power (dBm)MaximumLink Loss (dB) Channel Bandwidth (MHz) ModulationMode5MHz10MHz15MHz30MHzAllBands 5MHz10MHz15MHz30MHzBPSK 0.63 single -97.86 -95.25 -93.00 -89.56 +25 165.9 163.3 161.0 157.6 QPSK 0.63 single -93.13 -90.51 -88.91 -84.62 +25 161.1 158.5 156.9 152.6 QPSK 0.87 single -89.69 -86.28 -84.17 -81.34 +25 157.7 154.3 152.2 149.3 16QAM 0.63 single -87.58 -84.00 -81.85 -79.06 +25 155.6 152.0 149.9 147.1 16QAM 0.63 dual -84.34 -80.96 -79.19 -76.33 +25 152.3 149.0 147.2 144.3 16QAM 0.87 single -81.26 -77.89 -75.92 -72.45 +25 149.3 145.9 143.9 140.5 16QAM 0.87 dual -77.69 -73.70 -71.96 -69.10 +25 145.7 141.7 140.0 137.1 64QAM 0.75 single -78.02 -74.28 -72.47 -69.24 +25 146.0 142.3 140.5 137.2 64QAM 0.75 dual -74.18 -70.29 -68.62 -65.93 +25 142.2 138.3 136.6 133.9 64QAM 0.92 single -74.27 -71.62 -69.63 -66.51 +25 142.3 139.6 137.6 134.5 64QAM 0.92 dual -71.69 -68.04 -66.47 -63.27 +25 139.7 136.0 134.5 131.3 256QAM 0.81 single N/A N/A N/A -64.50 +25 N/A N/A N/A 132.5 256QAM 0.81 dual N/A N/A N/A -60.48 +25 N/A N/A NA 128.5
6 Site Planning 88 Table 20 - PTP 45600 - TDM Mode – Loss, Output Power and System Threshold Vs Modulation ModeThreshold Value (dBm) Output Power (dBm)MaximumLink Loss (dB) Channel Bandwidth (MHz) ModulationMode5MHz10MHz15MHz30MHzAllBands 5MHz10MHz15MHz30MHzBPSK 0.63 single -97.86 -95.25 -93.00 -89.56 +25 165.9 163.3 161.0 157.6 QPSK 0.63 single -90.42 -88.78 -85.56 -82.82 +25 158.4 156.8 153.6 150.8 QPSK 0.87 single -86.07 -84.02 -80.83 -78.67 +25 154.1 152.0 148.8 146.7 16QAM 0.63 single -83.53 -81.83 -78.74 -76.39 +25 151.5 149.8 146.7 144.4 16QAM 0.63 dual -80.70 -78.86 -75.74 -73.35 +25 148.7 146.9 143.7 141.4 16QAM 0.87 single -77.12 -73.86 -72.03 -69.25 +25 145.1 141.9 140.0 137.2 16QAM 0.87 dual -73.48 -71.50 -68.68 -66.77 +25 141.5 139.5 136.7 134.8 64QAM 0.75 single -73.07 -70.39 -68.65 -66.06 +25 141.1 138.4 136.7 134.1 64QAM 0.75 dual -69.60 -68.30 -65.37 -63.38 +25 137.6 136.3 133.4 131.4 64QAM 0.92 single -70.51 -68.26 -66.52 -63.93 +25 138.5 136.3 134.5 131.9 64QAM 0.92 dual -67.27 -66.03 -63.11 -60.04 +25 135.3 134.0 131.1 128.0 256QAM 0.81 single N/A N/A N/A -63.93 +25 N/A N/A N/A 131.9 256QAM 0.81 dual N/A N/A N/A -60.04 +25 N/A N/A N/A 128.0
6 Site Planning 89 6.1.7 PTP 48600 Product Variant - Link Loss, Output Power and System Threshold versus Modulation Mode PTP 48600 system threshold figures are given in the following tables: x Table 21 - IP Mode. x Table 22 - TDM Mode. These figures assume that antenna gain is 22 dBi. Table 21 - PTP 48600 - IP Mode – Loss, Output Power and System Threshold Vs Modulation ModeThreshold Value (dBm) Output Power (dBm)MaximumLink Loss (dB) Channel Bandwidth (MHz) ModulationMode5MHz10MHz15MHz30MHzAllBands 5MHz10MHz15MHz30MHzBPSK 0.63 single -97.86 -95.25 -93.00 -89.56 +25 165.9 163.3 161.0 157.6 QPSK 0.63 single -93.13 -90.51 -88.91 -84.62 +25 161.1 158.5 156.9 152.6 QPSK 0.87 single -89.69 -86.28 -84.17 -81.34 +25 157.7 154.3 152.2 149.3 16QAM 0.63 single -87.58 -84.00 -81.85 -79.06 +25 155.6 152.0 149.9 147.1 16QAM 0.63 dual -84.34 -80.96 -79.19 -76.33 +25 152.3 149.0 147.2 144.3 16QAM 0.87 single -81.26 -77.89 -75.92 -72.45 +25 149.3 145.9 143.9 140.5 16QAM 0.87 dual -77.69 -73.70 -71.96 -69.10 +25 145.7 141.7 140.0 137.1 64QAM 0.75 single -78.02 -74.28 -72.47 -69.24 +25 146.0 142.3 140.5 137.2 64QAM 0.75 dual -74.18 -70.29 -68.62 -65.93 +25 142.2 138.3 136.6 133.9 64QAM 0.92 single -74.27 -71.62 -69.63 -66.51 +25 142.3 139.6 137.6 134.5 64QAM 0.92 dual -71.69 -68.04 -66.47 -63.27 +25 139.7 136.0 134.5 131.3 256QAM 0.81 single N/A N/A N/A -64.50 +25 N/A N/A N/A 132.5 256QAM 0.81 dual N/A N/A N/A -60.48 +25 N/A N/A NA 128.5
6 Site Planning 90Table 22 - PTP 48600 - TDM Mode – Loss, Output Power and System Threshold Vs Modulation ModeThreshold Value (dBm) Output Power (dBm)MaximumLink Loss (dB) Channel Bandwidth (MHz) ModulationMode5MHz10MHz15MHz30MHzAllBands 5MHz10MHz15MHz30MHzBPSK 0.63 single -97.86 -95.25 -93.00 -89.56 +25 165.9 163.3 161.0 157.6 QPSK 0.63 single -90.42 -88.78 -85.56 -82.82 +25 158.4 156.8 153.6 150.8 QPSK 0.87 single -86.07 -84.02 -80.83 -78.67 +25 154.1 152.0 148.8 146.7 16QAM 0.63 single -83.53 -81.83 -78.74 -76.39 +25 151.5 149.8 146.7 144.4 16QAM 0.63 dual -80.70 -78.86 -75.74 -73.35 +25 148.7 146.9 143.7 141.4 16QAM 0.87 single -77.12 -73.86 -72.03 -69.25 +25 145.1 141.9 140.0 137.2 16QAM 0.87 dual -73.48 -71.50 -68.68 -66.77 +25 141.5 139.5 136.7 134.8 64QAM 0.75 single -73.07 -70.39 -68.65 -66.06 +25 141.1 138.4 136.7 134.1 64QAM 0.75 dual -69.60 -68.30 -65.37 -63.38 +25 137.6 136.3 133.4 131.4 64QAM 0.92 single -70.51 -68.26 -66.52 -63.93 +25 138.5 136.3 134.5 131.9 64QAM 0.92 dual -67.27 -66.03 -63.11 -60.04 +25 135.3 134.0 131.1 128.0 256QAM 0.81 single N/A N/A N/A -63.93 +25 N/A N/A N/A 131.9 256QAM 0.81 dual N/A N/A N/A -60.04 +25 N/A N/A N/A 128.0
6 Site Planning 91 6.1.8 PTP 49600 Product Variant - Link Loss, Output Power and System Threshold versus Modulation Mode PTP 49600 system threshold figures are given in the following tables: x Table 23 - IP Mode. x Table 24 - TDM Mode. These figures assume that antenna gain is 22 dBi. Table 23 - PTP 49600 - IP Mode – Loss, Output Power and System Threshold Vs Modulation ModeThreshold Value (dBm) Output Power (dBm)MaximumLink Loss (dB) Channel Bandwidth (MHz) ModulationMode5MHz10MHz15MHz30MHzAllBands 5MHz10MHz15MHz30MHzBPSK 0.63 single -97.86 -95.25 -93.00 -89.56 +25 165.9 163.3 161.0 157.6 QPSK 0.63 single -93.13 -90.51 -88.91 -84.62 +25 161.1 158.5 156.9 152.6 QPSK 0.87 single -89.69 -86.28 -84.17 -81.34 +25 157.7 154.3 152.2 149.3 16QAM 0.63 single -87.58 -84.00 -81.85 -79.06 +25 155.6 152.0 149.9 147.1 16QAM 0.63 dual -84.34 -80.96 -79.19 -76.33 +25 152.3 149.0 147.2 144.3 16QAM 0.87 single -81.26 -77.89 -75.92 -72.45 +25 149.3 145.9 143.9 140.5 16QAM 0.87 dual -77.69 -73.70 -71.96 -69.10 +25 145.7 141.7 140.0 137.1 64QAM 0.75 single -78.02 -74.28 -72.47 -69.24 +25 146.0 142.3 140.5 137.2 64QAM 0.75 dual -74.18 -70.29 -68.62 -65.93 +25 142.2 138.3 136.6 133.9 64QAM 0.92 single -74.27 -71.62 -69.63 -66.51 +25 142.3 139.6 137.6 134.5 64QAM 0.92 dual -71.69 -68.04 -66.47 -63.27 +25 139.7 136.0 134.5 131.3 256QAM 0.81 single N/A N/A N/A -64.50 +25 N/A N/A N/A 132.5 256QAM 0.81 dual N/A N/A N/A -60.48 +25 N/A N/A NA 128.5
6 Site Planning 92Table 24 - PTP 49600 - TDM Mode – Loss, Output Power and System Threshold Vs Modulation ModeThreshold Value (dBm) Output Power (dBm)MaximumLink Loss (dB) Channel Bandwidth (MHz) ModulationMode5MHz10MHz15MHz30MHzAllBands 5MHz10MHz15MHz30MHzBPSK 0.63 single -97.86 -95.25 -93.00 -89.56 +25 165.9 163.3 161.0 157.6 QPSK 0.63 single -90.42 -88.78 -85.56 -82.82 +25 158.4 156.8 153.6 150.8 QPSK 0.87 single -86.07 -84.02 -80.83 -78.67 +25 154.1 152.0 148.8 146.7 16QAM 0.63 single -83.53 -81.83 -78.74 -76.39 +25 151.5 149.8 146.7 144.4 16QAM 0.63 dual -80.70 -78.86 -75.74 -73.35 +25 148.7 146.9 143.7 141.4 16QAM 0.87 single -77.12 -73.86 -72.03 -69.25 +25 145.1 141.9 140.0 137.2 16QAM 0.87 dual -73.48 -71.50 -68.68 -66.77 +25 141.5 139.5 136.7 134.8 64QAM 0.75 single -73.07 -70.39 -68.65 -66.06 +25 141.1 138.4 136.7 134.1 64QAM 0.75 dual -69.60 -68.30 -65.37 -63.38 +25 137.6 136.3 133.4 131.4 64QAM 0.92 single -70.51 -68.26 -66.52 -63.93 +25 138.5 136.3 134.5 131.9 64QAM 0.92 dual -67.27 -66.03 -63.11 -60.04 +25 135.3 134.0 131.1 128.0 256QAM 0.81 single N/A N/A N/A -63.93 +25 N/A N/A N/A 131.9 256QAM 0.81 dual N/A N/A N/A -60.04 +25 N/A N/A N/A 128.0
6 Site Planning 936.1.9 PTP 54600 Product Variant - Link Loss, Output Power and System Thresholds versus Modulation Mode PTP 54600 system threshold figures are given in the following tables: x Table 25 - IP Mode. x Table 26 - TDM Mode. These figures assume that antenna gain is 23 dBi. Table 25 – PTP 54600 - IP Mode - Link Loss, Output Power, System Threshold Vs Modulation ModeThreshold Value (dBm) Output Power (dBm)MaximumLink Loss (dB) Channel Bandwidth (MHz) ModulationMode5MHz10MHz15MHz30MHzAllBands 5MHz10MHz15MHz30MHzBPSK 0.63 single -98.24 -94.58 -92.26 -88.90 +25 169.2 165.6 163.3 159.9 QPSK 0.63 single -93.02 -89.99 -88.50 -82.86 +24 163.0 160.0 158.5 152.9 QPSK 0.87 single -90.23 -86.68 -85.25 -80.10 +23 159.2 155.7 154.3 149.1 16QAM 0.63 single -87.98 -83.75 -82.82 -78.33 +22 156.0 151.8 150.8 146.3 16QAM 0.63 dual -84.29 -80.68 -79.32 -74.64 +22 152.3 148.7 147.3 142.6 16QAM 0.87 single -82.44 -79.10 -78.20 -72.98 +20 148.4 145.1 144.2 139.0 16QAM 0.87 dual -79.65 -75.74 -74.67 -70.58 +20 145.7 141.7 140.7 136.6 64QAM 0.75 single -78.93 -76.44 -74.93 -70.28 +18 142.9 140.4 138.9 134.3 64QAM 0.75 dual -76.45 -72.74 -71.55 -67.69 +18 140.5 136.7 135.6 131.7 64QAM 0.92 single -74.40 -71.66 -70.42 -64.96 +18 138.4 135.7 134.4 129.0 64 QAM 0.92 dual -70.65 -68.51 -66.88 -62.33 +18 134.7 132.5 130.9 126.3 256QAM 0.81 single N/A N/A N/A -63.63 +18 N/A N/A N/A 127.6 256QAM 0.81 dual N/A N/A N/A -60.46 +18 N/A N/A N/A 124.5
6 Site Planning 94 Table 26 – PTP 54600 - TDM Mode - Link Loss, Output Power, System Threshold Vs Modulation Mode Threshold Value (dBm) Output Power (dBm)MaximumLink Loss (dB) Channel Bandwidth (MHz) ModulationMode5MHz10MHz15MHz30MHzAllBands 5MHz10MHz15MHz30MHzBPSK 0.63 single -98.24 -94.58 -92.26 -88.90 +25 169.2 165.6 163.3 159.9 QPSK 0.63 single -89.70 -88.28 -86.35 -81.35 +24 159.7 158.3 156.4 151.4 QPSK 0.87 single -86.70 -84.30 -82.34 -78.42 +23 155.6 153.3 151.3 147.4 16QAM 0.63 single -86.56 -81.81 -79.91 -75.99 +22 151.7 149.8 147.9 144.0 16QAM 0.63 dual -83.70 -78.23 -76.54 -72.41 +22 148.8 146.3 144.5 140.4 16QAM 0.87 single -78.75 -76.61 -75.47 -69.76 +20 144.8 142.6 141.5 135.8 16QAM 0.87 dual -76.92 -73.85 -72.19 -68.70 +20 142.9 139.9 138.2 134.7 64QAM 0.75 single -74.66 -72.21 -71.77 -66.59 +18 138.7 136.2 135.8 130.6 64QAM 0.75 dual -73.00 -70.41 -68.79 -65.63 +18 137.0 134.4 132.8 129.6 64QAM 0.92 single -70.91 -68.59 -67.40 -62.94 +18 134.9 132.6 131.4 126.9 64 QAM 0.92 dual -68.15 -65.62 -64.23 -60.50 +18 132.1 129.6 128.2 124.5 256QAM 0.81 single N/A N/A N/A -65.36 +18 N/A N/A N/A 126.9 256QAM 0.81 dual N/A N/A N/A -60.50 +18 N/A N/A N/A 124.5
6 Site Planning 956.1.10 PTP 58600 Product Variant - Link Loss, Output Power and System Thresholds versus Modulation Mode PTP 58600 system threshold figures are given in the following tables: x Table 27 - IP Mode. x Table 28 - TDM Mode. These figures assume that antenna gain is 23 dBi. Table 27 - PTP 58600 - IP Mode - Link Loss, Output Power, System Threshold Vs Modulation ModeThreshold Value (dBm) Output Power (dBm)MaximumLink Loss (dB) Channel Bandwidth (MHz) ModulationMode5MHz10MHz15MHz30MHzAllBands 5MHz10MHz15MHz30MHzBPSK 0.63 single -95.05 -92.51 -90.78 -86.33 +25 166.1 163.5 161.8 157.3 QPSK 0.63 single -91.86 -90.04 -87.73 -83.00 +24 161.9 160.0 157.7 153.0 QPSK 0.87 single -88.69 -86.64 -84.84 -80.26 +23 157.7 155.6 153.8 149.3 16QAM 0.63 single -85.99 -84.31 -82.44 -78.34 +22 154.0 152.3 150.4 146.3 16QAM 0.63 dual -83.46 -80.36 -78.51 -75.34 +22 151.5 148.4 146.5 143.3 16QAM 0.87 single -82.12 -79.50 -78.13 -72.47 +20 148.1 145.5 144.1 138.5 16QAM 0.87 dual -79.24 -76.21 -73.92 -71.49 +20 145.2 142.2 139.9 137.5 64QAM 0.75 single -78.82 -76.70 -75.20 -69.16 +18 142.8 140.7 139.2 133.2 64QAM 0.75 dual -76.14 -73.14 -70.99 -67.67 +18 140.1 137.1 135.0 131.7 64QAM 0.92 single -74.40 -72.48 -66.24 -64.98 +18 138.4 136.5 134.6 129.0 64 QAM 0.92 dual -70.23 -69.07 -70.69 -61.53 +18 134.2 133.1 130.2 125.5 256QAM 0.81 single N/A N/A N/A -64.03 +18 N/A N/A N/A 128.0 256QAM 0.81 dual N/A N/A N/A -59.59 +18 N/A N/A N/A 123.6
6 Site Planning 96 Table 28 - PTP 58600 - TDM Mode - Link Loss, Output Power, System Threshold Vs Modulation ModeThreshold Value (dBm) Output Power (dBm)MaximumLink Loss (dB) Channel Bandwidth (MHz) ModulationMode5MHz10MHz15MHz30MHzAllBands 5MHz10MHz15MHz30MHzBPSK 0.63 single -95.05 -92.51 -90.78 -86.33 +25 166.1 163.5 161.8 157.3 QPSK 0.63 single -88.70 -87.77 -85.95 -80.59 +24 158.7 157.8 155.9 150.6 QPSK 0.87 single -85.51 -83.79 -81.56 -77.82 +23 154.5 152.8 150.6 146.8 16QAM 0.63 single -81.98 -81.26 -79.06 -75.29 +22 150.0 149..3 147.1 143.3 16QAM 0.63 dual -79.40 -77.58 -75.62 -71.72 +22 147.4 145.6 143.6 139.7 16QAM 0.87 single -78.66 -76.32 -74.67 -71.21 +20 144.7 142.3 140.7 137.2 16QAM 0.87 dual -75.05 -73.16 -71.03 -67.73 +20 141.0 139.2 137.0 133.7 64QAM 0.75 single -74.44 -72.26 -70.64 -67.94 +18 138.4 136.3 134.6 131.9 64QAM 0.75 dual -70.90 -69.52 -67.59 -64.02 +18 134.9 133.5 131.6 128.0 64QAM 0.92 single -70.86 -68.01 -66.63 -63.07 +18 134.9 132.0 130.6 127.1 64 QAM 0.92 dual -66.80 -64.62 -65.52 -58.65 +18 130.8 128.6 126.5 122.7 256QAM 0.81 single N/A N/A N/A -63.07 +18 N/A N/A N/A 127.1 256QAM 0.81 dual N/A N/A N/A -58.65 +18 N/A N/A N/A 122.7
6 Site Planning 976.1.11 PTP 59600 Product Variant - Link Loss, Output Power and System Thresholds versus Modulation Mode PTP 59600 system threshold figures are given in the following tables: x Table 29 - IP Mode. x Table 30 - TDM Mode. These figures assume that antenna gain is 23 dBi. Table 29 - PTP 59600 - IP Mode - Link Loss, Output Power, System Threshold Vs Modulation ModeThreshold Value (dBm) Output Power (dBm)MaximumLink Loss (dB) Channel Bandwidth (MHz) ModulationMode5MHz10MHz15MHz30MHzAllBands 5MHz10MHz15MHz30MHzBPSK 0.63 single -97.11 -94.07 -91.96 -88.66 +25.0 168.1 165.1 163.0 159.7 QPSK 0.63 single -90.71 -88.06 -87.13 -82.53 +24.0 160.7 158.1 157.1 152.5 QPSK 0.87 single -87.23 -84.38 -83.50 -79.29 +23.0 156.2 153.4 152.5 148.3 16QAM 0.63 single -85.04 -81.89 -81.21 -77.10 +22.0 153.0 149.9 149.2 145.1 16QAM 0.63 dual -81.90 -78.75 -77.47 -73.47 +22.0 149.9 146.8 145.5 141.5 16QAM 0.87 single -80.90 -77.95 -76.72 -72.87 +20.0 146.9 143.9 142.7 138.9 16QAM 0.87 dual -76.48 -73.92 -73.19 -70.03 +20.0 142.5 139.9 139.2 136.0 64QAM 0.75 single -77.02 -74.56 -73.63 -70.28 +18.0 141.0 138.6 137.6 134.3 64QAM 0.75 dual -73.14 -71.04 -70.40 -67.54 +18.0 137.1 135.0 134.4 131.5 64QAM 0.92 single -72.09 -70.98 -68.90 -65.65 +18.0 136.1 135.0 132.9 129.7 64 QAM 0.92 dual -70.20 -67.15 -66.11 -62.07 +18.0 134.2 131.1 130.1 126.1 256QAM 0.81 single N/A N/A N/A -63.91 +18.0 N/A N/A N/A 127.9 256QAM 0.81 dual N/A N/A N/A -59.88 +18.0 N/A N/A N/A 123.9
6 Site Planning 98 Table 30 - PTP 59600 - TDM Mode - Link Loss, Output Power, System Threshold Vs Modulation ModeThreshold Value (dBm) Output Power (dBm)MaximumLink Loss (dB) Channel Bandwidth (MHz) ModulationMode5MHz10MHz15MHz30MHzAllBands 5MHz10MHz15MHz30MHzBPSK 0.63 single -97.11 -94.07 -91.96 -88.66 +25.0 168.1 165.1 163.0 159.7 QPSK 0.63 single -88.47 -86.12 -84.37 -79.38 +24.0 158.5 156.1 154.4 149.4 QPSK 0.87 single -84.64 -81.89 -80.09 -76.00 +23.0 153.6 150.9 149.1 145.0 16QAM 0.63 single -82.45 -79.60 -77.75 -73.66 +22.0 150.4 147.6 145.8 141.7 16QAM 0.63 dual -78.81 -75.96 -74.12 -70.42 +22.0 146.8 144.0 142.1 138.4 16QAM 0.87 single -78.27 -75.07 -73.66 -70.19 +20.0 144.3 141.1 139.7 136.2 16QAM 0.87 dual -74.23 -71.63 -70.18 -66.89 +20.0 140.2 137.6 134.2 132.9 64QAM 0.75 single -74.69 -71.38 -70.23 -67.31 +18.0 138.7 135.4 134.2 131.3 64QAM 0.75 dual -70.85 -68.25 -66.75 -63.60 +18.0 134.8 132.2 130.8 127.6 64QAM 0.92 single -71.20 -68.05 -66.99 -63.27 +18.0 135.2 132.0 131.0 127.3 64 QAM 0.92 dual -66.66 -64.17 -62.71 -58.72 +18.0 130.7 128.2 126.7 122.7 256QAM 0.81 single N/A N/A N/A -63.27 +18.0 N/A N/A N/A 127.3 256QAM 0.81 dual N/A N/A N/A -58.72 +18.0 N/A N/A N/A 122.7
7 Installation 997 Installation IMPORTANT Motorola recommends that only qualified personnel undertake the installation of a PTP 600 Series Bridge solution. We recommend that the practices and procedures detailed in the Motorola manual R56 "STANDARDS AND GUIDELINES FOR COMMUNICATION SITES" (68P81089E50) be applied to all new site build activities. For a copy of the manual please see your local Motorola representative. The manual can be downloaded from the Motorola Intranet site http://compass.mot.com/go/190860869. 7.1 PreparationBefore proceeding with the installation you should: x Check the contents of all packages against the parts lists shown in the packing list. x Ensure that you have the correct tools for the job. x Ensure that you are qualified to undertake the work. x Ensure that you have taken the correct safety precautions. x Have completed the site planning as described in Section 6 “Site Planning”. 7.2 Installation Procedure The 600 Series installation procedure consists of the following steps: x Mounting the ODUs, Section 7.6 “Mounting the ODUs” x Connecting up, Section 7.7 “Connecting Up” x Mounting the PIDU Plus units, Section 7.7.9 “Mounting the PTP 600 Series Bridge PIDU Plus” x Mounting the Lightning Protection Units, Section 10.2 “Detailed Installation”. x Mounting the GPS Sync Unit (if required), Section 14 “TDD Synchronization Configuration and Installation Guide” and refer to the “GPS Sync Unit Kit” User Manual available in your installation CD for specific information related to the GPS Sync Unit. x Powering Up, Section 7.7.10 “Powering Up”. x Aligning the ODUs, Section 7.7.11 “Aligning the PTP 600 Series Bridge ODUs”.
7 Installation 1007.3 Tools RequiredThe following specific tools are required to install a PTP 600 Series Bridge in addition to general tools: x 13mm Spanner / Wrench x RJ45 Crimp Tool x IBM Compatible Personal Computer (PC) running Windows 98 or later with 10, 100 or 1000 BaseT Ethernet (Ability to change IP settings easily is recommended) x Either Internet Explorer version 6 or higher, or FireFox 1.5 or higher are recommended. x Ethernet patch cable 7.4 Installation SupportOnline installation support and contact details for your regional support can be found at http://www.motorola.com/ptp A Frequently Asked Questions (FAQ) section can be found in Section 21 “FAQs”. 7.5 Legal DisclaimerIN NO EVENT SHALL MOTOROLA, INC. BE LIABLE FOR ANY INJURY TO ANY PERSONS OR ANY DAMAGE CAUSED DURING THE INSTALLATION OF THE MOTOROLA PTP 600 SERIES PRODUCT.
7 Installation 1017.6 Mounting the ODUsThe ODU mounting bracket is designed to ease installation by fixing the bracket to a pole and then bringing the ODU into position using a single bolt fixing. The ODU should be mounted using the following steps ensuring that the cable entry is at the bottom. The ODU mounting bracket is designed to work with poles with diameters in the range 50mm (2”) to 75mm (3”). Figure 36 - Mounting to pole diameters 25mm (1”) to 50mm (2”) Step 1: Mount the bracket to the pole. Step 2: Mate the unit to the bracket together and tighten the nut and bolt. Pole diameters of 25mm (1”) to 50mm (2”) can be accommodated by inverting the back of the bracket as shown in Figure 36. When adjustment is complete tighten all bolts to 14Nm (11lb ft). CAUTION: Do not over tighten the bolts as bracket failure may occur. The enclosure and mounting brackets of the PTP 600 Series Bridge product range are capable of withstanding wind speeds up to 151mph (242kph). The installer should ensure that the structure the bridge is fixed to is also capable of withstanding the prevalent wind speeds and loads. See Section 12 “Wind Loading”.
7 Installation 102 WARNING: The integral safety loop should be used both for hoisting the ODU up a mast or building and into position, and also as a fixing point to secure a permanent safety lanyard from the tower/building to the ODU in case of mounting failure. Figure 37 - Integral Safety Loop The length of the safety lanyard must not exceed 1m (approx 3 ft) in length. The lanyard should be made from a material that does not degrade in an outdoor environment. The safety lanyard must be fixed to a separate fixing point that is not part of the direct mounting system for the ODU.
7 Installation 1037.7 Connecting Up7.7.1 Preparing the PIDU Plus To ODU Cable The maximum cable length between the ODU and the user’s Network Equipment is 100m (330 ft). Cable lengths up to 300m (984 ft) can be used where the PIDU Plus to ODU cable is supplying power only, that is, when using the PTP 600 Series Bridge Optical Interface. WARNING: The copper screen of the recommended Superior Essex cable is very sharp and may cause personal injury. When preparing this cable, take the following precautions: x ALWAYS wear cut resistant gloves (check the label to ensure thay are cut resistant). x ALWAYS wear protective eyewear. x ALWAYS use a rotary blade tool to strip the cable (DO NOT use a bladed knife). To use the rotary blade tool, fit it around the outer cable sheaf and rotate the cutter around the cable once or twice. The stripped outer section can then be removed.
7 Installation 104The cable should be assembled as shown in Figure 38: Figure 38 - Correct Cable Preparation for the Recommended Cable CAUTION: Check that the crimp tool matches the RJ45 connector being used. Both ends of the ODU cable are terminated in the same way. The above procedure should be repeated for the PIDU Plus end of the cable when the cable routing process is complete. This assumes that the installation uses PTP LPUs. If not, then the PIDU Plus end of the cable does not require a Gland, but just the RJ45. NOTE: The PIDU Plus end of the cable does not employ a cable gland.
7 Installation 105 Figure 39 shows a completed ODU to PIDU Plus cable. Figure 39 - Completed ODU Connector CAUTION: Do not over tighten the glands as the internal seal and structure may be damaged. See Figure 40 for an example of an over tightened cable gland. Figure 40 - Correct and Incorrect Tightening of Cable Gland
7 Installation 106 7.7.2 Making the Connections at the ODU Looking at the back of the unit with the cable entry at the bottom, the PTP 600 Series Bridge PIDU Plus connection is the first hole on the right (Figure 41) and is labeled “PIDU +”. Figure 41 – PTP 600 Series Bridge PIDU Plus Connexion
7 Installation 1077.7.3 Making the PTP 600 Series Bridge PIDU Plus Connection At The ODU The following procedure describes how connection is made at the ODU. It is often easier to carry out this procedure on the ground or a suitable surface prior to mounting the ODU. Ensure that no power is connected to the PIDU Plus or present on the cable before connecting the ODU. Figure 42 - Connecting the PIDU+ to the ODU Step 1: Assemble the cable as described in 7.7.1 above Step 2: Insert the RJ45 connector making sure that the locking tab snaps home Step 3: Screw in the body of the weather proofing gland and tighten Step 4: Screw on the clamping nut and tighten (Do not over tighten – see Figure 40)
7 Installation 108Should it be necessary to disconnect the PIDU Plus to ODU cable at the ODU, this can be achieved by removing the weather proofing gland and depressing the RJ45 locking tab with a small screwdriver as shown below. Figure 43 - Disconnecting the ODU CAUTION: Ensure that power is removed from the system at the PIDU Plus to prevent damage to the ODU while making or breaking the connection. 7.7.4 Routing the Cable After connecting the cable to the ODU it can be routed and secured using standard cable routing and securing techniques. When the cable is in place it can then be cut to the desired length at the PIDU Plus prior to connection to the PIDU Plus. 7.7.5 Fitting a Lightning Protection Unit If you have opted to fit a Lightning Protection unit, this should be installed by following the manufacturer’s instruction. For recommended types see Section 10 “Lightning Protection”.
7 Installation 1097.7.6 Grounding the Installation The Outdoor Unit (ODU) must be properly grounded to protect against power surges. It is the user’s responsibility to install the equipment in accordance with Section 810 of the National Electric Code, ANSI/NFPA No.70-1984 or Section 54 of the National Electrical Code in the country of installation. These codes describe correct installation procedures for grounding the outdoor unit, mast, lead-in wire and discharge unit, size of grounding conductors and connection requirements for grounding electrodes. It is recommended that installation of the outdoor unit be contracted to a professional installer. 7.7.7 Making the ODU Connection at the PTP 600 Series Bridge PIDU Plus The ODU is connected to the PIDU Plus by means of a concealed RJ45 connector. The RJ45 connection has been placed inside the PIDU Plus hinged cover to prevent the user from inadvertently plugging other equipment into the ODU RJ45 socket. CAUTION: Plugging other equipment into the ODU RJ45 socket may damage the equipment due to the non-standard techniques employed to inject DC power into the 1000BaseT connection between the PIDU Plus and the ODU. Plugging the ODU into other equipment may damage the ODU and/or the other equipment. Step 1: Undo the retaining screw and hinge back the cover. Step 2: Plug in the ODU into the PIDU Plus Cable ensuring that it snaps home
7 Installation 110 Step 3: Replace the cover and secure with the retaining screw 7.7.8 Making the Network Connection at The PIDU Plus – PTP 600 Series Bridge The Network connection is made by connecting the user’s Network Equipment directly to the PIDU Plus LAN port as shown in Figure 44. Figure 44 - Making the Network Connection at the PIDU Plus
7 Installation 1117.7.9 Mounting the PTP 600 Series Bridge PIDU Plus This step is optional. Motorola recommends that you mount the PIDU Plus on a wall or other suitable mounting surface. This prevents the unit from being knocked or kicked and can help maintain link availability. Ensure that the Recovery switch can be accessed when mounting the unit. Step 1: Fix the PIDU Plus to the wall using the lugs provided. Step 2: Make connections as per Section 7.7.7 “Making the ODU Connection at the PTP 600 Series Bridge PIDU Plus” CAUTION: The PIDU Plus is not waterproof and should be mounted away from sources of moisture. If mounted outdoors, the unit should be mounted in a rain proof enclosure, preferably ventilated.
7 Installation 112It is also recommended that you fit a drip loop on the PIDU Plus to ODU cable to ensure that any moisture that runs down the cable into the cabinet or enclosure cannot enter the PIDU Plus. This is shown in Figure 45. The network connection and mains cable should be treated in the same way if there is a risk that they can carry moisture to the PIDU Plus. Figure 45 – PTP 600 Series PIDU Plus Drip Loop Configuration CAUTION: It is possible for moisture to enter the cable due to damage to the outer protective layer. This moisture can track down the inside of the cable, filling up the drip loop and eventually finding its way into the PIDU Plus. To protect against this the outer protective layer of the cable can be opened up at the bottom of the drip loop to allow this moisture to escape.
7 Installation 1137.7.10 Powering Up The PTP 600 Series Bridge is supplied as a pair of matched Master/Slave units. The Master unit can now be powered up and accessed using the default URL http://169.254.1.2/; the Slave unit can be accessed using http://169.254.1.1/. Prior to powering up the PTP 600 Series Bridge, a computer with web browsing capabilities should be configured with an IP address of 169.254.n.n and subnet mask of 255.255.0.0 where n is any value between 1 and 254 but excluding 1.1 or 1.2. If the default addresses of the unit 169.254.1.1/2 clashes with an address you are already using on your LAN, or you are not sure, you should set up an isolated LAN. As the LAN connection presented at the PIDU Plus has a default configuration as a hub/switch (and auto-sensing MDI/MDIX cross over is employed), connection can be made directly to the computer using a standard CAT 5 patch cable. Before physical installation takes place the units to be installed should be set up as described in the Section 8.3.4 “Install Pages”. It is recommended that this procedure be carried out on the bench before physical installation commences. Providing it is safe to do so, the installer should take the process to the point where a radio link is established before proceeding to the installation site. NOTE: It is possible that some units may not be accessed using the above default URL. This is because these units may have been previously configured with IP addresses 10.10.10.11 (Master) and 10.10.10.10 (Slave). Therefore, users must use the URL http://10.10.10.10/ and/or URL http://10.10.10.11/ to configure the units. Please ensure that a computer with web browsing capabilities is configured with an IP address of 10.10.10.n, where n is any value between 2 and 254 but excluding 10 and 11, to configure these units.
7 Installation 1147.7.11 Aligning the PTP 600 Series Bridge ODUs The following is a description of the steps taken to establish a radio link between the two units forming the bridge and align the units for the best signal strength. The PTP 600 Series Bridge uses audible tones during installation to assist the installer with alignment. The installer should adjust the alignment of the ODU in both azimuth and elevation until highest pitch tone is achieved. The pitch of the alignment tone is proportional to the received power of the wireless signals. The best results are usually achieved by making small incremental movement in angular alignment. The tones and their meanings are as follows: Table 31 - Audio indications from the ODU State Name ToneDescription State Description Pitch Indication (Higher pitch = higher power) Free Channel Search Regular beep Executing band scan N/A Scanning Slow broken tone Not demodulating the wanted signal Rx Power Synchronized Fast broken tone Demodulating the wanted signal Rx Power Registered Solid tone Both Master and Slave units exchanging Radio layer MAC management messages Rx Power The term ‘wanted signal’ refers to that of the peer unit being installed. In each of the states detailed above, the unit should be aligned to give the highest pitch tone. It should be noted that if, when in the Synchronized or Registered state, the tone varies wildly, you may be suffering from interference or a fast fading link. Installing in this situation may not give a reliable link. The cause of the problem should be investigated.
7 Installation 115For the ease of alignment, both Master and Slave units use the install tones in the same way but with some small behavioral differences. This allows the installer to install the Slave unit first and carry out the initial alignment with the Master unit if desired. However, due to the behavioral differences of Master and Slave units, it is recommended that the Master unit is installed first and the initial alignment carried out at the Slave unit. There is a graphical installation screen (section 8.3.5 “Graphical Install”) available using the web interface that displays the state of the link during the alignment process (up = green, down = red). The following behavior should be noted: x Band scan: When first started up and from time to time, the Master unit will carry out a band scan to determine which channels are not in use. During this time, between 10 and 15 seconds, the Master unit will not transmit and as a consequence of this neither will the Slave unit. During this time the installation tone on the master unit will drop back to the band scan state, and the Slave unit will drop back to the Scanning state with the pitch of the tone set to the background noise level. Alignment of the unit should cease during this time. x Radar detection: If the unit is operating where mandatory radar avoidance algorithms are implemented, the ranging behaviour for the PTP 600 Series Bridge may be affected. The Master has to monitor the initially chosen channel for 60 seconds to make sure it is clear of radar signals before transmitting. If a radar is detected during any of the installation phases, a further compulsory 60 seconds channel scan will take place as the master unit attempts to locate a new channel that is free of radar interference. x Ranging: The Master unit can take up to 60 seconds in 0-40km (0-25 miles) mode, 90 seconds in 0-130km (0-81 miles) mode and 120 seconds in 0-200km (0-124 miles) mode to determine the range of the link being installed. The Master unit will remain in the Scanning state until the range of the link has been established. The Master unit will only move to the Synchronized state when the range of the link has been established. x Retrying same channel: If, at the end of the ranging period, the Registered state is not achieved due to interference or other reasons, the Master unit will retry twice more on the same channel before moving to another available channel. Should this occur it might take a number of minutes to establish a link in the Registered state. x Slave unit: The Slave unit does not have a ranging process. The slave unit will change to the Synchronized state as soon as the wanted signal is demodulated.
7 Installation 116When the alignment process is complete, the installer MUST REMEMBER TO DISARM BOTH UNITS in the link, as described in Section 8.3.4 “Install Pages”. This is necessary in order to: x Turn off the audible alignment aid (section 8.3.4.6 “Disarm”) x Enable Adaptive Modulation x Fully enable Advanced Spectrum Management with i-DFS x Clear unwanted installation information from the various systems statistics x Store the link range for fast link acquisition on link drop x Enable higher data rates NOTE: After 24 hours, the units will be disarmed automatically, provided that they are armed and that the link is UP.
8 Web Page Reference 1178 Web Page Reference The web user interface has three main sections. The home page presents to the operator a high level summary of the PTP 600 Series Bridge point-to-point wireless link. The status page presents a more detailed set of system parameters describing the performance of the wireless link together with other key system performance metrics. The final section is the system administration section. This section is password protected and allows the system administrator to perform all the day-to-day administrative procedures, for example software upgrade and configuration changes. The following subsections give a detailed usage guide for all the web user interfaces. The web pages are best viewed using a screen resolution of at least 1024 x 768 pixels on a PC using Microsoft Internet Explorer Version 6 or 7. NOTE: The web pages have also been tested with Firefox 2.0.0.12. Other browsers have not been tested.
8 Web Page Reference 118The navigation bar on the left hand side of the web page is used to move between the various management pages. The currently selected page is always highlighted with a light blue background. The menu is hierarchical. Selecting a menu item which has associated submenu options will automatically display all sub options. A sample web page with the navigation menu is shown in Figure 46 when the ‘Home’ Link is highlighted as the current page. Figure 46 - Menu Navigation Bar
8 Web Page Reference 1198.1 Home Page – PTP 600 Series Bridge The home page for the PTP 600 Series Bridge has been designed to display a high level summary of the status of the wireless link and associated equipment. The home page (Figure 47) normally displays four key system attributes: Wireless Link Status: The Wireless Link Status attribute displays the current status of the PTP 600 Series Bridge wireless link. A state of ‘Up’ on a green background indicates that a point-to-point link is established. A state of ‘Down’ on a red background indicates that the wireless link is not established. If the link is down for an unknown reason the system administrator should first consult the status web page for a more detailed summary of up to date system diagnostics. Link Name: The link name attribute is a name and/or handle allocated by the system administrator to aid the identification of the unit, network or building. Figure 47 - System Summary Page Elapsed Time Indicator: The elapsed time indicator attribute presents the total time in days, hours, minutes and seconds since the last system restart. The system can restart for several reasons, for example, commanded reboot from the system reboot webpage, or a power cycle of the equipment. System Clock: If SNTP (Simple Network Time Protocol) is enabled, or the clock has been set, then a system clock attribute is displayed giving the date and time of the last page refresh. Section 8.3.11.8 “SNTP (Simple Network Time Protocol)” explains how to enable SNTP and Section 8.3.11.9 “Setting the clock” explains how to set the clock.
8 Web Page Reference 1208.1.1 Home Page Alarm Display The home page is also used to display all outstanding major system alarms. Whenever system alarms are asserted, a yellow warning triangle is displayed on web page navigation bar. The warning triangle will be visible from all web pages. Clicking the warning triangle will cause the web page to jump back to the system homepage. Figure 48 shows a sample alarm screen. Figure 48 - Alarm Warning Triangle
8 Web Page Reference 121The following system alarms are defined: Ethernet Link Status: Current status of the Ethernet link. If there are any problems with the Ethernet interface, this alarm will be asserted. This alarm will most likely be seen if the unit has no Ethernet cable plugged into its Ethernet socket. Note that a change of state may generate an SNMP trap and/or SMTP email alert. Telecoms Channel A Status (see section 8.3.4.3 “Telecoms Interface” for a description of the Telecoms Interface): Current status of telecoms channel A. Indicates that there is a problem with the telecoms channel A. Possible problems are "No Signal (local)", "No Signal (Remote)", and "No Signal (Local and Remote)". Note that a change of state may generate an SNMP trap and/or SMTP email alert. Telecoms Channel B Status (see section 8.3.4.3 for a description of the Telecoms Interface): Current status of telecoms channel B. Indicates that there is a problem with the telecoms channel B. Possible problems are "No Signal (local)", "No Signal (Remote)", and "No Signal (Local and Remote)". Note that a change of state may generate an SNMP trap and/or SMTP email alert. Telecoms Interface A Loopback (see section 8.3.4.3 for a description of the Telecoms Interface): The loopback status of telecoms channel A. This is intended for installation testing and should be set to 'None' for normal operation. The wire connections to a unit can be tested by applying a 'Copper' loopback to the local unit. The wireless connection to the remote unit can be tested by applying a 'Wireless' loopback to the remote unit with no loopback on the local unit. Note that a change of state may generate an SNMP trap and/or SMTP email alert. The loopback can be disabled from the telecoms configuration sub menu (see Section 8.3.1.6). Telecoms Interface B Loopback (see section 8.3.4.3 for a description of the Telecoms Interface): The loopback status of telecoms channel B. This is intended for installation testing and should be set to 'None' for normal operation. The wire connections to a unit can be tested by applying a 'Copper' loopback to the local unit. The wireless connection to the remote unit can be tested by applying a 'Wireless' loopback to the remote unit with no loopback on the local unit. Note that a change of state may generate an SNMP trap and/or SMTP email alert. The loopback can be disabled from the telecoms configuration sub menu (see Section 8.3.1.6 “Telecoms Configuration Page”). Region Code: The region code prohibits the wireless unit from operating outside the regulated limits. An invalid region code indicates a corrupted license key. Note that a change of state may generate an SNMP trap and/or SMTP email alert.
8 Web Page Reference 122Install Status: A non-OK value indicates that signaling was received with the wrong MAC address. Note that it is very unusual to detect this, because units with wrongly configured Target MAC Address will normally fail to establish a wireless link. However, rare circumstances may establish a partial wireless link and detect this situation. NB: A non-OK value on start-up, or a change of value during operation, may generate an SNMP trap and/or SMTP email alert. Install Arm State: This alarm warns when a wireless unit is in installation mode. After installation the wireless unit should be disarmed. This will increase the wireless link’s data-carrying capacity and stop the installation tone generator. The wireless link is disarmed from the ‘Installation Wizard’ see Section 8.3.4.6 “Disarm”. A change of state may generate an SNMP trap and/or SMTP email alert. Unit Out Of Calibration: The unit is out of calibration and must be returned to the factory using the RMA process for re-calibration. Encryption Enable Mismatch (see section 17 “AES Encryption Upgrade”): Encryption has been enabled on one end of the wireless link but not the other. Incompatible Region Codes: The PTP 600 Series Bridge uses region codes to comply with local regulatory requirements governing the transmission of wireless signals in the 5.9 GHz, 5.8 GHz, 5.4 GHz, 4.5 GHz and 2.5 GHz bands. Region codes can only be changed by obtaining a new PTP600. Note that a change of state may generate an SNMP trap and/or SMTP email alert. Series license key: If this alarm is encountered the appropriate license keys from the country of operation should be obtained from your distributor. Applying license keys containing the same region codes to both ends of the link will remove the alarm. No Wireless Channel Available: Spectrum Management was unable to locate a suitable wireless channel to operate on. Note that a change of state may generate an SNMP trap and/or SMTP email alert. Wireless Link Disable Warning: This warning is displayed if the Wireless link has been administratively disabled via the SNMP Interface (see Section 8.3.11 “Remote Management Page”). The Wireless Interface MIB-II ifAdminStatus attribute has been set to DOWN. To enable the Ethernet interface, set the ifAdminStatus attribute to UP. Note that a change of state may generate an SNMP trap and/or SMTP email alert.
8 Web Page Reference 123Ethernet Link Disable Warning: This warning is displayed if the Ethernet link has been administratively disabled via the SNMP Interface (see section 8.3.11 “Remote Management Page”). The Ethernet Interface MIB-II ifAdminStatus attribute has been set to DOWN. To enable the Ethernet interface, set the ifAdminStatus attribute to UP. Note that a change of state may generate an SNMP trap and/or SMTP email alert. Fiber Link Status: If the fiber link is not OK, there are two possible causes: Either the fiber link has been installed but disabled (because the license key does not include fiber support), or the link could not be established even though an optical carrier was detected (due perhaps to a broken TX fiber, or the link is disabled at the fiber link partner). Note that a change of status may generate an SNMP trap and/or SMTP email alert. Ethernet Configuration Mismatch Alarm: The detection of Ethernet fragments (runt packets) when the link is in full duplex is an indication of an auto-negotiation or forced configuration mismatch. Note that a change of state may generate an SNMP trap and/or SMTP email alert. Incompatible Master and Slave: A non-zero value indicates that the master and slave ends of the wireless link are different hardware products, or have different software versions. Note that it is very unusual to detect this because incompatible units will normally fail to establish a wireless link. However, some combinations may establish a partial wireless link and detect this situation. Note that a non-zero value may generate an SNMP trap and/or SMTP email alert. TDD Synchronization Status: Current status of the TDD Synchronization (acquiring synchronization, no timing reference and timing system not connected). Note that a change of state may generate an SNMP trap and/or SMTP email alert. SNTP Synchronization failed: This warning indicates that SNTP has been enabled but that the unit is unable to synchronize with the specified SNTP server. Section 8.3.11.8 “SNTP (Simple Network Time Protocol)” explains how to configure SNTP. Note that a change of state may generate an SNMP trap and/or SMTP email alert.
8 Web Page Reference 1248.2 Systems Status PageThe status page has been designed to give the system administrator a detailed view of the operation of the 600 Series Bridge from both the wireless and network perspectives. The page is subdivided into four main categories Equipment, Wireless, Telecoms and Ethernet/Internet. The ‘Equipment’ section contains the unit’s inventory and identification information. The ‘Wireless’ section presents the key wireless metrics, which are displayed as a series of measurements. The ‘Ethernet/Internet’ section describes the unit’s network identity and connectivity. “Telecoms” controls the unit’s E1/T1 telecoms interfaces. The status page can be configured to refresh itself at an operator defined rate (if the user is logged in as system administrator). The refresh period defaults to 3600 seconds and can easily be changed to refresh at any period between 2 seconds and 3600 seconds. Pressing the ‘Update Page Refresh Period’ button causes a new page refresh period to be adopted by the system. The page refresh mechanism uses a HTML Meta refresh command. Therefore the refresh is always initiated by the local browser and not by the 600 Series Bridge at this interval. The two PTP 600 Series bridges units are arranged in a master and slave relationship. The roles of the units in this relationship are displayed in the page title. The master unit will always have the title ‘- Master’, and the slave will always have ‘- Slave’ appended to the ‘Systems Status’ page title. Figure 49 - Status Page
8 Web Page Reference 125The following section details all the attributes displayed on the status page: Link Name: The link name is allocated by the system administrator and is used to identify the equipment on the network. The link name attribute is limited to a maximum size of 63 ASCII characters. Link Location: The link location is allocated by the system administrator and can be used as a generic scratch pad to describe the location of the equipment or any other equipment related notes. The link location attribute is limited to a maximum size of 63 ASCII characters. Software Version: The attribute describes the version of software installed on the equipment. The format of the attributes is FFSSS-XX-YY where FF is the frequency variant (2.5, 4.5, 5.4, 5.8 or 5.9 GHz), SSS is the System Release, XX is the major release version and YY is the minor release version. Hardware Version: The hardware version attribute contains all the combined hardware version information. The attribute is formatted as DXX-RYY-Z where DXX contain the version of the digital card, RYY contains the version of the RF (radio frequency) card and Z describes the antenna type which can be I (integrated) or C (connectorized). Region Code: The region code is used by the system to constrain the wireless to operate within regulatory regime of the particular country. The region code is encoded in the product license key. If the operator wishes to change region code, a new license key must be obtained from Motorola or the local point-to-point distributor / system integrator. Elapsed Time Indicator: The elapsed time indicator attribute presents the total time in years, days, hours, minutes and seconds since the last system restart. The system can restart for several reasons, for example commanded reboot from the system reboot web page, or a power cycle of the equipment. Ethernet Link Status: Current status of the Ethernet link. A state of ‘Up’ with a green background indicates that an Ethernet link is established. A state of ‘Down’ with a red background indicates that the Ethernet link is not established.
8 Web Page Reference 126Ethernet Speed and Duplex: The negotiated speed and duplex setting of the Ethernet interface. The speed setting is specified in Mbps. Full Duplex data transmission means that data can be transmitted in both directions on a signal carrier at the same time. For example, on a local area network with a technology that has full duplex transmission; one workstation can be sending data on the line while another workstation is receiving data. Half Duplex data transmission means that data can be transmitted in both directions on a signal carrier, but not at the same time. For example, on a local area network using a technology that has half duplex transmission, one workstation can send data on the line and then immediately receive data on the line from the same direction in which data was just transmitted. Remote IP Address: Hyperlink to the other side of the Link. The IP address of the peer link is displayed if the Link is UP, otherwise “unavailable” is displayed. Channel A: The status of telecom interface A. Channel B: The status of telecom interface B. Refresh Page Period: The Status page refreshes automatically according to the setting entered here (in seconds). This attribute is only displayed when the user is logged on as System Administrator. Wireless Link Status: As the attribute name suggests it displays the current status of the wireless link. A state of ‘Up’ on a green background indicates that a point-to-point link is established. A state of ‘Down’ on a red background indicates that the wireless link is not established. Maximum Transmit Power: The maximum transmit power that the local wireless unit is permitted to use to sustain a link. Remote Maximum Transmit Power: The maximum transmit power that the remote wireless unit is permitted to use to sustain a link. Transmit Power: Transmit power histogram is expressed in dBm and presented as: max, mean, min, and latest. The max, min and latest are true instantaneous measurements; the mean is the mean of a set of one second means. See Section 8.2.1 “Histogram Data”. Receive Power: Receive power histogram is expressed in dBm and presented as: max, mean, min, and latest. The max, min and latest are true instantaneous measurements; the mean is the mean of a set of one second means. See Section 8.2.1 “Histogram Data”.
8 Web Page Reference 127Vector Error: The vector error measurement compares the received signal’s In phase / Quadrature (IQ) modulation characteristics to an ideal signal to determine the composite error vector magnitude. The results are stored in an histogram and expressed in dB and presented as: max, mean, min and latest. The max, min and latest are true instantaneous measurements; the mean is the mean of a set of one second means. The expected range for Vector Error would be approximately -2dB (NLOS link operating at sensitivity limit on BPSK 0.67) to –33dB (short LOS link running 256 QAM 0.83). See Section 8.2.1 “Histogram Data”. Link Loss: The link loss is the total attenuation of the wireless signal between the two point-to-point units. See Section 8.2.1 “Histogram Data”.. The link loss calculation presented below: Equation 3 - Link Loss xxxx RTRTll ggPPP  Where is llP Link Loss (dB) xTP Transmit power of the remote wireless unit (dBm) xRP Received signal power at the local unit (dBm) xx RT gg , Antenna gain at the remote and local units respectively (dBi). The antenna gain of the 600 Series bridge (23.5 dBi) is used unless one or both of the units is a Connectorized version. Transmit Data Rate: The data rate in the transmit direction, expressed in Mbps and presented as: max, mean, min, and latest in an histogram format. The max, min and latest are true instantaneous measurements; the mean is the mean of a set of one second means. See Section 8.2.1 “Histogram Data”. Expected data rates can be found in Section 16 “Data Rate Calculations”. Receive Data Rate: The data rate in the receive direction, expressed in Mbps and presented as: max, mean, min, and latest in an histogram format. The max, min and latest are true instantaneous measurements; the mean is the mean of a set of one second means. See Section 8.2.1 “Histogram Data”. Expected data rates can be found in Section 16 “Data Rate Calculations”.
8 Web Page Reference 128Link Capacity: The maximum aggregate data rate capacity available for user traffic, assuming the units have been connected using Gigabit Ethernet. The link capacity is variable and depends of the prevailing wireless conditions as well as the distance (range) between the two wireless units.. Transmit Modulation Mode: The modulation mode currently being used on the transmit channel. List of all the modulation modes can be found in Section 16 “Data Rate Calculations” where data rate calculations plots are given for each available modulation mode.. Receive Modulation Mode: The modulation mode currently being used on the receive channel. List of all the modulation modes can be found in Section 16 “Data Rate Calculations” where data rate calculations plots are given for each available modulation mode. Link Symmetry: The Link Symmetry control setting, expressed as a ratio of the number of OFDM symbols in each TDD frame where the first number represents the transmit direction and the second number represents the receive direction. NOTE: If Link Symmetry is set to “2 to 1” at the master ODU, it will be displayed as “1 to 2” in the Status Page of the slave ODU, indicating that the master-slave direction has double the capacity of the slave-master direction. Receive Modulation Mode Detail: This supplies the user with information regarding the receive modulation mode in use. Possible values are: x Running at maximum receive mode x Running at user-configured Max Modulation Mode x Restricted due to byte errors on the wireless link or local Ethernet Tx Fifo Drops x Restricted because a DFS channel change is in progress x Restricted due to telecoms acquisition mode x Restricted due to the low Ethernet link speed x Limited by the wireless conditions Range: The range between the 600 Series bridge ODUs. The PTP 600 Series Bridge displays range in km by default, but if the user would prefer to display range using Miles, the ‘Distance Units’ attribute should be set to imperial, as described in Section 8.3.15 “Properties”.
8 Web Page Reference 1298.2.1 Histogram Data The histogram is calculated over a one hour period. If the equipment has been running for less than one hour, then the histogram is calculated over the current elapsed time. The data used to compute the histogram statistics can be downloaded in an ASCII comma separated value (CSV) format via the diagnostics CSV Download page, see Section 8.3.12.2 “Diagnostics Download”.
8 Web Page Reference 1308.3 System Administration PagesThe following menu options are available for the system administrator and can be password protected. Figure 50 shows the system administration login page. By default a system administrator password is not set. Simply click the login button to access the system administration features. Figure 50 - System Administration Login Page Once the password has been set using the ‘Change Password’ menu item the system administration pages will only be available after the user has entered the correct password. The features that are only available to the system administrator are: x Configuration x Statistics x The Installation Wizard x Software Upgrade x Spectrum Management including DFS x Remote management x Diagnostics Plotter x Password Management x License Key Management x Properties x System Reboot
8 Web Page Reference 1318.3.1 System Configuration The configuration of the 600 Series Bridge is organized into three sections: x General configuration x LAN configuration x Telecoms Configuration x Save and Restore The general configuration allows modification of high level administrative (descriptive) attributes and high level wireless configuration. The LAN configuration sub menu allows the system administrator to modify the Ethernet and IP configuration of the 600 Series Bridge. The telecoms submenu displays the current status of the telecoms interface and allows the configuration of interface loopbacks. The save and restore submenu allows the system administrator to backup and restore the bridge configuration. It is recommended after a unit has been successfully installed; a copy of the active configuration is taken and archived by the system administrator. 8.3.1.1 General Configuration Page The general configuration page (Figure 51) is used by the system administrator to configure the 600 Series Bridge’s high level administrative (descriptive) attributes and high level wireless configuration. Figure 51 - System Configuration Page
8 Web Page Reference 132 While the majority of the system configuration is entered during installation and should never require changing, this page offers the system administrator the ability to change the basic system parameters for both the wireless and Ethernet components. Link Name: User defined identity for the unit (max 63 characters). Link Location: Can be used as a generic scratch pad to describe the location of the equipment. Master Slave Mode and Link Mode Optimization: Current settings are displayed and can be modified using the Installation Wizard pages 8.3.4 “Install Pages”. Max Receive Modulation Mode: This is the maximum mode the unit will use as its adaptive modulation. By default the Max Receive Modulation Mode is the highest mode available. For minimum error rates, set the maximum modulation mode to the minimum necessary to carry the required traffic. Ethernet Capped Max Wireless Speed: When enabled this option will cap the wireless speed to a mode that the connected Ethernet connection can sustain. Maximum Transmit Power: This specifies the maximum transmit power in dBm of the system. It is country dependent and although the user can change this in 1dB steps, it will be limited to that country’s regulations. NOTE: In the UK there is a legal requirement to provide a minimum of 19 dB of transmit power control range. When the equipment is operating with a UK Licence Key, an additional facility is provided on the configuration page that allows the transmitted power to be reduced by 19 dB compared to the maximum allowed with a simple single step control.. NOTE: Why Reduce Transmit Power? If the link losses are low and the link data rate and availability targets are being easily achieved, the transmitted power level may be reduced with a consequent benefit to other users of the band, such as fixed satellite links.
8 Web Page Reference 1338.3.1.2 LAN Configuration Page The LAN configuration page (Figure 52) is used by the system administrator to configure the 600 Series Bridge’s LAN interface. Figure 52 - LAN Configuration Page IP Address: Internet protocol (IP) address. This address is used by the family of Internet protocols to uniquely identify this unit on a network. Subnet Mask: A subnet allows the flow of network traffic between hosts to be segregated based on a network configuration.
8 Web Page Reference 134Gateway IP Address: The IP address of a computer / router on the current network that acts as a gateway. VLAN High Priority Traffic Threshold: All packets with an 802.1P priority tag greater than or equal to the indicated value will be treated as a high priority packet for transmission over the wireless link.Use VLAN For Management Interfaces: This controls use of VLAN tags at the management interfaces (WWW/SNMP/SMTP/SNTP). See Section 8.3.1.3 “LAN Configuration Page – Use VLAN For Management Interfaces”. Ethernet Auto Negotiation This enables the Ethernet configuration to be forced rather than auto negotiated. CAUTION: The configuration should only be forced if you are having problems with auto negotiation. You must ensure that you configure both this unit and the Ethernet port to which it is connected identically. If you force a fixed Ethernet Configuration on the 600 Series bridge then you MUST also force the same fixed configuration on the equipment to which it is connected. If you fail to force the configuration of the connected equipment, its automatic configuration mechanisms will normally cause a duplex mismatch, and you will receive greatly reduced throughput! When Ethernet Auto Negotiation is Disabled the format of the LAN configuration page will change see Section 8.3.1.4 “LAN Configuration Page – Manual Ethernet Configuration”. Auto Neg Advertisement: This controls the rates that the auto negotiation mechanism will advertise as available. CAUTION: Over the air throughput will be capped to the rate of the Ethernet interface at the receiving end of the link. Ethernet Auto Mdix: This enables/disables the Auto Medium Dependent Interface (MDI)/Medium Dependent Interface Crossover (MDIX) capability. Default is “Enabled”. Drop Ethernet Link On Wireless Link Down: When this option is enabled the Ethernet link is momentarily dropped when the wireless link goes down. This feature is used to indicate to the connected network equipment that this Ethernet link is no longer available, thus causing STP (Spanning Tree Protocol) to re-route packets through an alternative link.
8 Web Page Reference 135Local Packet Filtering: When Local Packet Filtering is “Enabled”, the bridge learns the source MAC addresses of devices transmitting Ethernet packets on the local Ethernet network, and only bridges packets to the remote unit if the destination MAC address has not been learned as a 'local' device. When Local Packet Filtering is ‘Disabled’ the bridge does not learn the source MAC addresses of devices transmitting Ethernet packets on the local Ethernet network, and bridges ALL Ethernet packets received to the remote unit. Local Packet Filtering should be disabled when external Ethernet switching hardware or a router is present. The default setting for Local Packet Filtering is disabled. All of the above attributes are non-volatile, once set they will be used by the unit even after a power on reboot. A number of attributes, such as IP Address, Subnet Mask and Gateway IP Address and VLAN settings will require a reboot before they are used. If any of these attributes are changed a reboot screen appears asking the user to verify the reboot (Figure 53 or Figure 54). Figure 53 - Configuration Reboot Page Figure 54 - Configuration Reboot Page - Ethernet Auto Negotiation Disabled This will be followed by a pop-up dialogue box asking to confirm the action.
8 Web Page Reference 136NOTE: At this point you will lose connection to the unit. If you have just changed the IP Address you now have to reconnect to the unit using the address just set. 8.3.1.3 LAN Configuration Page – Use VLAN For Management Interfaces The layout of the LAN Configuration page changes if this attribute is enabled in order to allow the VLAN VID and VLAN Priority to be set, see Figure 55. The VLAN settings are applied only after the unit is rebooted. CAUTION: You must ensure that you can access the VLAN which you configure here, otherwise you will be unable to access the unit following the next reboot. CAUTION: The PTP 600 management function is only compatible with single VLAN tagged packets. Any management packet with two or more packets will be ignored. Figure 55 - VLAN Configuration Fields
8 Web Page Reference 137Use VLAN For Management Interfaces: This control can be configured with one of the following three values: x No VLAN Tagging x IEEE 802.1Q Tagged (C-Tag, Type 8100) x IEEE 802.1ad Tagged (S-Tag or B-Tag, Type 88a8) VLAN Management VID: This 802.1Q or 802.1ad VLAN ID (VID) will be included in packets generated by the management interfaces. Valid settings are in the range 0 to 4094. VLAN Management Priority: This 802.1Q or 802.1ad VLAN Priority will be included in packets generated by the management interfaces. Valid settings are in the range 0 to 7. VLAN Management VID Validation: If enabled, the management interfaces will only respond to Ethernet packets tagged with the configured Management VID; otherwise packets with any VID will be accepted. 8.3.1.4 LAN Configuration Page – Manual Ethernet Configuration Figure 56 - LAN Configuration Page - Manual Ethernet Configuration Force Configuration: This option allows the user to force the speed and duplex setting of the Ethernet interface.
8 Web Page Reference 138CAUTION: Over the air throughput will be capped to the rate of the Ethernet interface at the receiving end of the link. 8.3.1.5 Save and Restore Configuration File The save and restore feature of a PTP 600 Series Bridge allows the system administrator to backup the operation configuration of the wireless unit. It is recommended that this facility is used immediately after a successful PTP 600 Series Bridge installation or prior to any software upgrade. In the unlikely event that a unit has to be replaced in the field, the replacement unit can be reconfigured by simply playing back the saved configuration file. 8.3.1.5.1 Save Configuration File To save the configuration file click on the ‘Save Configuration File’ button (Figure 57) and save the configuration file (.cfg) to the hard drive of your computer. Figure 57 - Save and Restore Configuration Page The configuration file format is MAC-mm-mm-mm_IP-iii-iii-iii-iii.cfg, where mm and iii are the lower 3 bytes of the MAC address and the unit IP address respectively. NOTE: There is a feature of Internet Explorer (all versions) that looks at the content of any downloadable file and decides whether to treat the file as ASCII or binary. As a result of this feature, Internet Explorer always treats the configuration file as ASCII and attempts to display it instead of downloading it. Firefox (all versions) makes no such assumption.
8 Web Page Reference 139Figure 58 - Save Configuration File Screen The configuration file is encoded using an ASCII encoding scheme. An example is show in 1Figure 59. Figure 59 – PTP 600 Example Configuration File
8 Web Page Reference 140 CAUTION: The configuration file is currently restricted to a single software version and can only be restored into a wireless unit operating the software version indicated in the configuration file header. 8.3.1.5.2 Restore Configuration File The configuration file can also be used when swapping out a faulty wireless unit. If one of the wireless units is replaced on a wireless link a configuration file captured from the faulty unit can be uploaded into the new unit to speed up replacement. NOTE: The licence key of the faulty unit should be setup on the replacement unit before the configuration file is loaded. This can be obtained either from the Quick Start Guide supplied with the faulty wireless unit or directly from Motorola. The target MAC address at the other end needs to be changed to ensure that it is using the MAC address of the replaced unit. The restoration of configuration files can be performed using the Restore configuration tool. Using the browser button to locate the configuration file you wish to restore then click the ‘Restore Configuration File and Reboot’ button (Figure 60). The user will then be prompted to confirm the action (Figure 61) Figure 60 - Restore Configuration File Pop Up Screen
8 Web Page Reference 141 Figure 61 - Reset Configuration and Reboot Confirmation Pop-up On confirmation the PTP 600 Series Bridge will: x Upload the configuration file x Perform data integrity checking x Erase previous configuration x Apply the new configuration x Restart After the unit has restarted the entire configuration from the configuration file will now be active. Note: The IP address of the unit may have also been changed. The user can check the new IP address by reading the header of the configuration file, Figure 59. CAUTION: A reboot is always required to restore a configuration file.
8 Web Page Reference 142 8.3.1.6 Telecoms Configuration Page The Telecoms page is only available when the Telecoms Interface has been set to either T1 or E1 in the Installation Wizard. It displays the interface setting and line code for the available telecoms channels. The PTP 600 Series Bridge is able to support two T1 or E1 channels. However, in the “Lite” configuration one of these channels is disabled. The channels are referred to as "Channel A" and "Channel B". The "Channel B" configuration and controls will be displayed only when the second channel is enabled. Figure 62 - Telecoms Data Entry Telecoms Interface: May be either T1, E1 reflecting the Installation Wizard setting. Line Code: Displays the Line Code setting for each channel. The Line Code configuration must match the configuration of the connected equipment and may be set using the Installation Wizard.
8 Web Page Reference 143Cable Length: The Cable Length setting is applicable in T1 mode only and shows the cable length specified in the installation wizard. Loopback: Allows the T1 or E1 data stream to be looped back at the copper or wireless interface. During normal operation the loopback must be set to "None". It may be helpful during installation to test the telecoms links by performing loopback connections. A "Copper" loopback connects the received data on a given telecoms interface to the Transmit. A "Copper" loopback may be used, in conjunction with an appropriate test unit, to confirm that the correct connections have been made to the ODU. A "Wireless" loopback sends the telecoms data received across the wireless link back across the link on the same Telecom channel. The link may be checked using, for example, a Bit Error Rate Tester to ensure that no errors are detected. A typical T1 or E1 installation might include a "Copper" loopback on the local unit followed by a "Wireless" loopback on the remote unit. It is important to remove all loopbacks on channels for normal operation. Alarms on the Home Page indicate the presence of loopbacks on either channel.
8 Web Page Reference 1448.3.2 Statistics Page The 600 Series bridge statistics page is designed to display some key statistics of the Ethernet Bridge and the underlying wireless performance. The numbers in brackets display the number of packets received since the last page refresh. Figure 63 - System Statistics Wireless Tx Packets: This displays the total number of good packets the bridge has sent for transmission by the wireless interface. Wireless Rx Packets: This displays the total number of good packets the bridge has received from the wireless interface.
8 Web Page Reference 145Ethernet Tx Packets: This displays the total number of good packets the bridge has sent for transmission by the local Ethernet interface. Ethernet Rx Packets: This displays the total number of good packets the bridge has received from the local Ethernet interface. Packets To Internal Stack: This displays the total number of good packets the bridge has transmitted to the internal stack (for example, ARP requests, PING requests, HTTP requests). Packets From Internal Stack: This displays the total number of good packets the bridge has received from the internal stack (for example ARP responses, PING replies, HTTP responses). Link Symmetry: Master ODU only. The Link Symmetry control setting, expressed as a ratio of the number of OFDM symbols in each TDD frame where the first number represents the transmit direction and the second number represents the receive direction. Transmit Data Rate: The data rate in the transmit direction, expressed in Mbps and presented as: max, mean, min, and latest in an histogram format. The max, min and latest are true instantaneous measurements; the mean is the mean of a set of one second means. See Section 8.2.1 “Histogram Data”. Expected data rates can be found in Section 16 “Data Rate Calculations”. Receive Data Rate: The data rate in the receive direction, expressed in Mbps and presented as: max, mean, min, and latest in an histogram format. The max, min and latest are true instantaneous measurements; the mean is the mean of a set of one second means. See Section 8.2.1 “Histogram Data”. Expected data rates can be found in Section 16 “Data Rate Calculations”. Aggregate Data Rate: The sum of the data rate in the directions expressed in Mbps and presented as: max, mean, min, and latest in an histogram format. The max, min and latest are true instantaneous measurements; the mean is the mean of a set of one second means. See Section 8.2.1 “Histogram Data”. Expected data rates can be found in Section 16 “Data Rate Calculations”. Link Capacity: The maximum aggregate data capacity available for user traffic under the current radio link conditions, assuming the units have been connected using Gigabit Ethernet. The sum of the displayed Transmit and Receive data rates may be lower than this figure if the link isn't fully loaded by the current traffic profile.
8 Web Page Reference 146Transmit Modulation Mode: The modulation mode currently being used on the transmit channel. The number in brackets after the modulation mode and coding rate string is the effective data rate available to all MAC layer protocols. List of all the modulation modes can be found in Section 16 “Data Rate Calculations” where data rate calculations plots are given for each available modulation mode. Receive Modulation Mode: The modulation mode currently being used on the receive channel. The number in brackets after the modulation mode and coding rate string is the effective data rate available to all MAC layer protocols. List of all the modulation modes can be found in Section 16 “Data Rate Calculations” where data rate calculations plots are given for each available modulation mode. Receive Modulation Mode Detail: This supplies the user with information regarding the receive modulation mode in use. Possible values are: x Running at maximum receive mode x Running at user-configured Target Modulation Mode x Restricted because Installation is armed x Restricted because of byte errors on the wireless link x Restricted because a DFS channel change is in progress x Restricted due to the low Ethernet link speed x Limited by the radio conditions Signal Strength Ratio: The Signal Strength Ratio is the ratio of the power received by the Vertical / Horizontal receivers and presented as: max, mean, min, and latest in an histogram format. The max, min and latest are true instantaneous measurements; the mean is the mean of a set of one second means. See Section 8.2.1 “Histogram Data”. Wireless Link Availability: Expresses the link availability as a percentage of time since the first successful registration after a system restart, expressed as a percentage to four decimal places. Byte Error Ratio: The ratio of detected Byte errors to the total number of bytes since the last system reboot. This is a true measure of link quality as this measurement is made continually using null frames when there is no user data to transport. Statistics Page Refresh Period: The statistics page refreshes automatically according to the setting entered here (in seconds). Reset System Counters: By pressing this button all counters in the system are reset to zero. Reset System Histograms: All histograms are reset, and the calculation period is restarted.
8 Web Page Reference 1478.3.3 Detailed Counters Page Figure 64 - Detailed Counters Page
8 Web Page Reference 148 The detailed counters page is subdivided into two columns. Column one presents the detailed statistics for the bridge’s Ethernet interface. Column two relates to the wireless interface. The Counters have the following definitions: Tx & Rx Octets: Total number of octets (bytes) transmitted or received over the interface. Rx Drops: Total number of frames dropped due to the lack of sufficient capacity in the receive buffer. Rx Packets: Total number of packets received by the interface. This includes both good and bad packets. Rx Broadcasts: Total number of good broadcast packets. Rx Multicasts: Total number of good multicast packets. Rx CRC and Align: Total number of packets with CRC or frame alignment errors. Rx Undersize: Total number of packets received that are less than 64 bytes and have a valid CRC. Rx Oversize: Total number of packets received that are greater than the maximum number of bytes with a valid CRC. Rx Fragments: Total number of packets that are less than 64 bytes with an invalid CRC (these packet types are also known as runts). Rx Jabbers: Total number of packets received that are greater than the maximum number of bytes with an invalid CRC. Rx 64 Bytes: Total number 64 byte frames received Rx 65 to 127 Bytes: Total number of frames received in the size range 65 to 127 bytes. Rx 128 to 255 Bytes: Total number of frames received in the size range 128 to 255 bytes. Rx 256 to 511 Bytes: Total number of frames received in the size range 256 to 511 bytes. Rx 512 to 1023 Bytes: Total number of frames received in the size range 512 to 1023 bytes. Rx 1024 to Max: Total number of frames received in the size range 1024 to Maximum bytes. Tx Drops: Total number of frames dropped due excessive collisions, late collision and frame ageing.
8 Web Page Reference 149Tx Packets: Total number of packets received by the interface. This includes both good and bad packets. Tx Broadcasts: Total number of good broadcast packets. Tx Multicasts: Total number of good multicast packets. Tx Collisions: Total number frames experiencing collisions. Tx 64 Bytes: Total number 64 byte frames transmitted Tx 65 to 127 Bytes: Total number frames transmitted in the size range 65 to 127 bytes. Tx 128 to 255 Bytes: Total number frames transmitted in the size range 128 to 255 bytes. Tx 256 to 511 Bytes: Total number frames transmitted in the size range 256 to 511 bytes. Tx 512 to 1023 Bytes: Total number frames transmitted in the size range 512 to 1023 bytes. Tx 1024 to Max: Total number frames transmitted in the size range 1024 to Maximum bytes. Tx FIFO Drops: Total number frames dropped due to lack of capacity in the transmit buffer, for example when the 600 Series bridge is connected to the local Ethernet at a connection speed of less than 1 Gbps. Rx & Tx High Priority: Total number of received or transmitted frames marked as high priority. Rx & Tx Low Priority: Total number of received or transmitted frames marked as low priority. Rx & Tx Pause Frames: Total number of received or transmitted pause frames. Rx Classifier Drops: Total number of received frames dropped due to the application of classifier rules. Statistics Page Refresh Period: The statistics page refreshes automatically according to the setting entered here (in seconds).
8 Web Page Reference 150 8.3.4 Install PagesThese pages are used during system installation. There follows a description of the install pages along with their use during the installation configuration process. The actual installation process is described in Section 8.3.4.1 “Manually Configuring The Wireless Units”. NOTE:This section assumes that the integrated PTP 600 is being installed. If the connectorized variant is being installed, refer to Section 13.3 “Software/Features” for details of the additional functionality that must be configured. All wireless links are shipped as paired units. They are pre-configured at the factory so that they can be installed without the user supplying any configuration. Each wireless link is shipped with a quick start guide. Attached to the quick start guide is a summary of the pre-configured configuration data. Table 32 shows a sample link configuration. The values in red type have been committed to the wireless unit’s non-volatile storage. Table 32 – 600 Series Bridge Factory Configuration Values Example PTP 600 Series Configuration Data For your convenience these two units have been pre-configured as a link Units: ODU serial number ODU serial number 016780000FFF 016780000FC7 Ethernet MAC address Ethernet MAC address 00:04:56:80:0F:FF 00:04:56:80:0F:C7 Configured as: Master Slave Target MAC address Target MAC address
8 Web Page Reference 15100:04:56:80:0F:C7 00:04:56:80:0F:FF License Key License Key A471-FE88-428D-E1F3 534F-4F54-D1B0-E2DA IP Address IP Address 169.254.1.2 169.254.1.1 CAUTION: The factory default configuration is limited in range to 40 Km (25 miles). If you wish to install a wireless link with a range of > 40 Km (> 25 miles) and < 200 Km (< 124 miles) or < 5 Km (< 3 miles) you must follow the ‘Manually Configuring The Wireless Units’ in Section 8.3.4.1. CAUTION: The factory default configuration is set to Region 1. Region 1 allows the 600 Series bridge a maximum transmit power of 25 dBm. If the local regulatory regime limits the maximum transmit power (EIRP) to less than 25 dBm you should obtain a new license key containing the correct region code from your local distributor or direct from Motorola. Alternatively in the short term, you should reduce the maximum transmit power by following the procedures in ‘Manually Configuring The Wireless Units’ in Section 8.3.4.1. 8.3.4.1 Manually Configuring The Wireless Units If the installer / system administrator wishes, they may modify the default installation configuration. If only the IP addresses (network configuration) are incorrect it is recommended that the values are changed via the configuration menu (Section 8.3.1.2 “LAN Configuration Page”). CAUTION: If any other parameters (for example Region Code) require modification, then it is recommended that the system administrator use the Installation Wizard. A detailed description of the Installation Wizard follows: The 600 Series bridge operational software requires a license key to enable the wireless bridging capability and programs region code specific parameters in to the unit.
8 Web Page Reference 152Figure 65 - License Key Data Entry A license key is programmed into each unit during production and can be found written on the Configuration Data Summary Label which is attached to the Quick Install Guide. If subsequently the license key has been mislaid, replacement keys can be applied for online or via your distributor. If a valid license key is not detected in the unit’s non-volatile memory then the user is prompted to enter a valid key. It should be noted that 600 Series bridge units are shipped as link pairs and, as such, valid license keys are entered during the production process. To enter a license key simply type or paste the license key into the data entry box (Figure 65) and click the ‘validate license key’ button.
8 Web Page Reference 153 8.3.4.2 Internet Protocol Configuration Step 1 of the installation wizard requires the installer to enter the Internet Protocol (IP) configuration. Figure 66 - Installation Wizard Internet Protocol Configuration IP Address: Internet protocol (IP) address. This address is used by the family of Internet protocols to uniquely identify this unit on a network. Subnet Mask: A subnet allows the flow of network traffic between hosts to be segregated based on a network configuration. By organizing hosts into logical groups, subnetting can improve network security and performance. Gateway IP Address: The IP address of a computer / router on the current network that acts as a gateway. A gateway acts as an entrance / exit to packets from / to other networks. Use VLAN Management Interface: Controls whether the management interfaces (HTTP/SNMP/SMTP/SNTP) use a VLAN. Selecting this option presents the user with extra fields in which to enter the Management VLAN ID, Priority and whether to validate the VLAN ID. If the user modifies this control, a warning dialog is displayed see Figure 67.
8 Web Page Reference 154Telecoms Interface This allows the activation of the 600 Series bridge telecoms interface. The selection options are None, E1 or T1. Mixed T1/E1 configurations are not permitted. Figure 67 - VLAN Warning Once complete, click the ‘Submit Internet Protocol Configuration’ button or the ‘Next’ link.
8 Web Page Reference 1558.3.4.3 Telecoms Interface If the telecoms interface is configured to either T1 or E1 then Step 1 of the installation wizard contains additional configuration fields. Figure 68 - Telecoms Configuration Interface The additional E1 or T1 fields are: Telecoms Channel Selection: This controls the selection of the telecoms interface standard supported options or T1 and E1. Channel A Line Code: The line code setting of the telecoms interface. This must match the setting of the device connected to this interface. Channel B Line Code: The line code setting of the telecoms interface. This must match the setting of the device connected to this interface. Cable Length: This field is applicable to the T1 operating mode only. It configures the T1 transceiver to output a signal suitable for driving a cable of the specified length. This should be set to reflect the length of cable between the wireless unit and the connected equipment.
8 Web Page Reference 156 8.3.4.4 Wireless Configuration Step 2 of the installation wizard requires the installer to enter the wireless configuration parameters. Figure 69 is an example of the Wireless Configuration screen. Figure 69 –Wireless Configuration
8 Web Page Reference 157The contents of the Wireless Configuration screen vary depending upon the PTP 600 variant as follows: x PTP 25600: Frequency Band field is also displayed. x PTP 48600 and PTP 49600: Channel Bandwidth options are 20, 10 and 5 MHz. x PTP 49600: Lower Center Frequency is not displayed. Screen contents also vary depending upon the options selected as follows: x If Spectrum Management Control is set to “Fixed Frequency”, the Lower Center Frequency field is replaced by Fixed Tx Frequency and Fixed Rx Frequency. x If Platform Variant is set to “Connectorized”, Antenna Gain and Cable Loss are also displayed. For more information about the configuration of connectorized PTP 600 units, refer to Section 13.3 “Software/Features”. See the field definitions below for more details. Target MAC Address: This is the MAC Address of the peer unit that will be at the other end of the wireless link. This is used by the system to ensure the unit establishes a wireless link to the correct peer. The MAC Address can be found embedded within the serial number of the unit. The last six characters of the serial number are the last three bytes of the unit’s MAC address. NOTE: A PTP 600 Series system is shipped as a pair of units with pre-loaded correct MAC addresses. Target MAC addresses will only need to be entered if an existing unit has to be replaced in the field or the units configuration has been erased. Master Slave Mode: At this point it is necessary to decide which end will designate a Master. The Master unit is the controlling unit with respect to the point-to-point link and its maintenance. The master transmits until the link is made, while the Slave listens for its peer and only transmits when the peer has been identified. Link Mode Optimization: Optimizes the link behavior according to the type of traffic that will be bridged. There are two modes to choose from: IP and TDM. NOTE: In TDM mode it is recommended to reduce the Maximum Modulation Mode to 64QAM 0.75, but preferably to the minimum mode necessary to carry the required traffic.
8 Web Page Reference 158In IP Mode, the PTP 600 product runs an Adaptive TDD scheme. Basically an unloaded link runs 10:10 mode (10 OFDM bursts alternately in each direction). A sustained traffic load in one direction for example may cause a threshold to be reached where the TDD mode automatically adapts to say 20:10. If the load continues to increase, then the TDD structure may adapt even further through 30:10 to 40:10. This is a state of maximum link asymmetry (40 OFDM bursts in one direction compared with 10 in the other). If the load increases in BOTH directions, then the TDD structure can adapt from 10:10, through 20:20, 30:30 and finally 40:40. This is a state of maximum aggregate throughput. So if three out of these combinations are considered; 10:10, 40:10 and 40:40 they would give the following characteristics: x 10:10 equal performance in each direction, lowest aggregate throughput and lowest Latency. x 40:10 achieves maximum one way throughput performance, to the detriment of both latency and throughput in the opposite direction. x 40:40 Maximum link aggregate rate, balanced performance in each direction, higher latency. NOTE: There is an engineering trade-off between the flexibility of ATDD and Latency as follows: When the TDD structure changes, there will be a short term impact on Latency for a few Frames. This would not affect the steady state long term average latency, but could be recorded as a Maximum latency. This affect may be amplified for short Latency tests or if the traffic loading is oscillating either side of a boundary condition. As the TDD burst length increases, Traffic in each direction will have to wait longer before a Transmit window is available, but more data can be sent during the burst. There is an impact on latency but it varies depending upon installation range, Frame size and modulation mode. In TDM mode, two major differences in link behavior occur compared with IP mode. First the TDD structure is fixed symmetrically. Either 10:10, 20:20, 30:30 or 40:40 based upon the installed range, as shown in Table 33. Table 33 – TDD Structure in TDM Mode OFDMBursts Radar Avoidance Range (km) 30 MHz Band Range (km) 15 MHz Band Range (km) 10 MHz Band Range (km) 5 MHz Band Range (km) 10:10 1-20 1-43 1-60 1-94 1 -200 20:20 21-63 44-95 61-130 95-200 N/A 30:30 64 -145 96 -150 131 -200 N/A N/A 40:40 146 -200 151 -200 N/A N/A N/A
8 Web Page Reference 159 Secondly, the point at which a modulation mode changes for given RF conditions is more conservative. In practice, this means that the link will typically stay in a lower modulation mode, but with increased tolerance to RF variability. Depending upon the link characteristic that the customer requires, this may very well be the best choice. It increases consistency of link performance and equality in each direction as a trade-off against maximum throughput. TDD Synchronization Mode: Enables the TDD Synchronization feature (see Section 5.12 “Time Division Duplex (TDD) Synchronization” for basic description and Section 14 “TDD Synchronization Configuration and Installation Guide” for installation and configuration details). Tx Max Power: This attribute controls the maximum transmit power the unit is permitted to use when installing and executing the wireless link. The maximum setting for a particular region or country is controlled by the License Key. Ranging Mode: During installation, the wireless units perform “Automatic Ranging”. The ranging mode allows the installer to control the behavior of the system’s automatic ranging algorithms. The default value is 0 to 40 km (0 to 25 miles). If the installer is required to install a link of greater than 40 km (25 miles) then the ranging mode attribute MUST be configured to ‘0 to 100km’ (0 to 62 miles) or ‘0 to 200km’ (0 to 124 miles) mode depending on the range of the link. NOTE: If preferred, PTP 600 Series Bridge range functions can be configured to operate in miles, as described in Section 8.3.15 “Properties”. Target Range: Installers that know the range between the two wireless units to within r 1 km can use the target range mode. The main advantage of the target range mode is that it reduces the time taken by the units to range. To use the target range mode the installer MUST select Target Range as the ranging mode and enter the approximate range in km in the Target range data entry field at both ends of the link. Platform Variant: Chooses between an integrated unit or a connectorized unit that requires an external antenna.
8 Web Page Reference 160Frequency Band: Only displayed for the PTP 25600 product variant, which operates in one of three bands as described in Section 5.4 “Variable Channel Bandwidth Operation”: x Lower: 2496 MHz to 2568 MHz x Middle: 2572 MHz to 2614 MHz x Upper: 2624 MHz to 2690 MHz Channel Bandwidth: Users can choose a variable channel bandwidth for the available spectrum. The selection depends upon the PTP bridge variant: x For PTP 25600, PTP 45600, PTP 54600, PTP 58600 and PTP 59600, Channel Bandwidth may be 30, 15, 10 or 5 MHz. x For PTP 48600 and PTP 49600, Channel Bandwidth may be 20, 10 or 5 MHz. Link Symmetry: (Master only) Values of Adaptive, 2:1, 1:1 and 1:2 can be selected. In fixed symmetric mode, the master spends an equal amount of time transmitting and receiving whereas in fixed asymmetric mode, the master transmit and receive times have a fixed ratio. NOTE: (a) "Adaptive" is not supported in regions where radar avoidance is in use, (b) "Adaptive" is not supported when link optimization is set to "TDM", (c) "Adaptive" is not supported in 5 MHz channel bandwidth, (d) "2:1" and "1:2" are not supported in 5 MHz channel bandwidth. Spectrum Management Control: Is used to configure the PTP 600 Series Bridge’s Spectrum Management features, see Section 8.3.7 “Spectrum Management” for more details. i-DFS is the abbreviation for intelligent Dynamic Frequency Selection. This feature continually monitors the spectrum looking for the channel with the lowest level of on channel and co-channel interference. Fixed frequency mode allows the installer to fix transmit and receive frequencies on the units. The frequencies may be configured symmetrically or asymmetrically. Only 30MHz channels are available in regions that mandate DFS (Radar Detection), and the Spectrum Management Control may not be available because the regulations for some regions force DFS, others force fixed frequency (for example 2.5 GHz). Lower Center Frequency: Not displayed for the PTP 49600. Not displayed when Spectrum Management Control is set to “i-DFS”. The software for the PTP 600 Series Bridge allows a user to optionally adjust the channel center frequencies. Changing the Lower Center Frequency attribute causes all channel center frequencies to be offset. It effectively slides the channelization up or down. See Sections 5.5 to 5.11, depending on the frequency variant. NOTE: Because the 4.9 GHz spectrum is restricted by license, the Lower Center Frequency is fixed for the PTP 49600 and is therefore not displayed.
8 Web Page Reference 161CAUTION: The lower center frequency attribute must be configured to the same value for both the master and slave. Failure to do so will cause the wireless link to fail reestablishment. The only way to recover from this situation is to modify the Lower Center Frequency attribute so that they are identical on both the master and slave unit. Default Raster: If this is set to “On”, the list of options presented in the fixed Tx frequency box is limited by the default raster.Fixed Tx Frequency, Fixed Rx Frequency: Only displayed when Spectrum Management Control is set to “Fixed Frequency”. The software for the PTP 600 Series Bridge allows a user to optionally fix the Transmit and the Receive frequencies for a wireless link. The settings must be compatible at each end of the link. Once configured, the spectrum management software will not attempt to move the wireless link to a channel with lower co-channel or adjacent channel interference. Therefore this mode of operation is only recommended for deployments where the installer has a good understanding of the prevailing interference environment. Figure 70 shows an example fixed frequency configuration for a 30 MHz channel bandwidth. In this example, the Fixed Transmit Frequency is set to 5742 MHz and the Fixed Receive Frequency is set to 5742 MHz. Care must be taken when configuring the Fixed Transmit and Receive Frequencies to ensure that both frequencies are on the same channel raster as the Lower Center Frequency. For example, if the channel raster is 10 MHz, both the Fixed Transmit and Receive Frequencies must be a multiple of 10 MHz from the Lower Center Frequency (5752 = 5742 + 10 MHz) and (5782 = 5742 + 10 MHz u 3). NOTE: A raster limits the selection of the Rx frequency based upon the setting of the Tx frequency. Tx Color Code, Rx Color Code: When co-channel interference is from another PTP 600, co-channel performance is improved by selecting different values for the Color Code attribute at the victim and interfering links. For the vast majority of links, both Color Code parameters can use the default value "A". The parameter only requires consideration when planning complex networks. If the network planner deems that there is a significant level of co-channel interference from a synchronized PTP 600, performance can be optimised by setting the victim Rx Color Code and the interfering Tx Color Code to different values. Tx Color Code at one end of the link must always be set to the same value as Rx Color Code at the other end of the link. For more information, see Section 5.13 “Color Codes”. NOTE:As long as the victim Rx Color Code and interferer Tx Color Code are different, the same level of optimization will be achieved, that is, an A / B combination is as good as an A / E combination.
8 Web Page Reference 162Installation Tones: Where the use of audio installation tones is not required, this control allows the installer to optionally disable the tone generator during the installation process. Once the installer is satisfied with the wireless configuration options then the “Submit Wireless Configuration” button or the “Next” link should be clicked. Figure 70 – Fixed Frequency Configuration Example
8 Web Page Reference 163 8.3.4.5 Confirm Configuration Step 3 of the installation wizard requires the installer to confirm the wireless configuration parameters. Figure 71 is an example of the Confirm Configuration screen. The screen contents vary depending upon the product variant and configuration options selected. Figure 71 – Installation Wizard Confirm Configuration
8 Web Page Reference 164If the settings are correct and appropriate, click the “Confirm Configuration, Arm Installation and Reboot” button. The user will now be prompted to confirm the action (Figure 72). Figure 72 - Reboot Confirmation Pop Up All the attributes are committed to non-volatile memory. Immediately following the write to non-volatile memory the unit is reset. NOTE: If you have changed the Ethernet parameters you must reconnect using the correct network and address settings.
8 Web Page Reference 165 8.3.4.6 Disarm Figure 73 is an example of the Disarm Installation screen. The screen contents vary depending upon the product variant and configuration options selected. Figure 73 – Disarm Installation
8 Web Page Reference 166When Section 8.3.4.5 “Confirm Configuration” is complete, the installation is armed and rebooted. Pressing the “Disarm Installation Agent” button completes the installation process and the audible installation tone will be switched off. If the installer wishes to modify the installation configuration then the ‘Back’ link can be used to access the installation wizard steps described above. The installation process is completed when both ends of the link are ‘disarmed’. After disarming the wireless link the user is presented with one of two possible configuration pages, see Figure 74 and Figure 75. The screen presents hyperlinks to the main configuration and spectrum management pages. Figure 74 - Optional Post Disarm Configuration 1 Figure 75 - Optional Post Disarm Configuration 2 After installation the system administrator may wish to modify the wireless units descriptive configuration (link name and link location). In addition the system administrator may wish to change the spectrum management configuration of the wireless unit, or look at the analysis of the 5.8 GHz spectrum to see if the automatic channel selection is appropriate for the system administrator’s network. It is also recommended that a backup copy of the wireless units configuration is taken. Hyperlinks are provided on the post disarm page for ease of use.
8 Web Page Reference 167 8.3.5 Graphical Install To aid the installation of wireless links two graphical installation aids have been introduced in this 600 Series system version. x A PDA installation screen x A larger installation screen available from the main HTTP management interface. The design of the installation screen has been deliberately kept simple and uncluttered. An example of the installation screen is shown in Figure 76. Both the PDA and the large format installation screen have the same content and only differ in size. The PDA installation screen is 232 by 220 pixels to be compatible with the typical size of a PDA screen. Figure 76 – Graphical Installation Screen The screen displays the receive power over the last three minutes. This will allow the installer to slowly sweep the antenna during installation and monitor the variation in signal strength with angular position. The screen automatically refreshes every three seconds. The screen also displays the current state of the wireless link in two ways. First, the actual state of the wireless link is written in the top left corner of the screen. The instantaneous receive power bar also encodes the state of the wireless link using green to signify that the wireless link is up and red for all other states.
8 Web Page Reference 168For the more technically, aware the installation metric is simply the instantaneous receive power in dBm + 100. The PDA installation tool is accessed via a hidden URL http://<ip-address>/pda.cgi. It should be noted that this link is only available after the user has logged in as system administrator. The large screen version of the graphical user interface is available as a submenu option of the installation wizard. 8.3.6 Software Upgrade The 600 Series system has two software image banks; one is a fixed image which is stored in protected non-volatile memory and cannot be modified by the user. The second bank is used by the system administrator to upgrade the firmware when necessary. Figure 77 shows the main software upgrade web page. Figure 77 - Software Upgrade The ‘Fixed’ or ‘Recovery’ image is used by the System Administrator to: x Reset Ethernet configuration to default settings x Erase Configuration x Upgrade software For a full description of the Recovery image see Section 9 “Recovery Mode”.
8 Web Page Reference 169The software upgrade pages are used to update a unit’s operational software. The software image to be uploaded should be downloaded to local storage from the Motorola web site. The software image is delivered by Motorola as a compressed zip file. Once the zip file has been downloaded, the user should extract the PTP 600 Series Software image, identifiable by its ‘.dld’ file extension. The first step (Figure 77) is to use the “Browse” button to locate the software image previously downloaded to local storage from the Motorola web site. Once the image is located, the user should press the Upload Software Image button to start the software upgrade process. RECOMMENDATION: During the software upgrade process, ensure that the remote end is upgraded first using the wireless connection, and then the local end can be upgraded. The software image will now be uploaded to the unit. This upload should only take a few seconds. Once complete the image is verified and validated to ensure that no errors occurred during transfer and that the image is valid to run on the current platform. If there are any problems a warning screen will appear. The unit being upgraded will now display information about the build it currently has stored in the image bank and the one that’s just been uploaded. If the image is not the right one, the user has the option to go back and reload a new image. (See Figure 78) Figure 78 - Software Upgrade Image Check
8 Web Page Reference 170The user should ensure that the correct image is shown before pressing the “Program Software Image into Non-Volatile Memory” button. Once this button has been pressed the image is stored into non-volatile memory, this process can take up to 60 seconds and must not be interrupted. CAUTION: If the upgrade process is interrupted during the erasure of the image bank, or during the reprogramming of the image bank, the image bank will be left in a corrupt state. If this occurs the software must be reloaded. All software images that are stored in non-volatile memory are protected via the use of CRCs. If the software detects an invalid CRC the image bank is marked as ‘corrupt’ and the 600 Series bridge boot code will boot the fixed software image. If this occurs the user must attempt to reload the correct version of software. During the write process the progress of the upgrade is displayed on the progress tracking page (Figure 79). The upgrade process should not be interrupted. Interruption of this process can result in a corrupt main software image, which will result in the recovery image been booted at the next reset cycle. Figure 79 - Software Download Progress Indicator Figure 80 - Software Upgrade Complete When the software image has been written to non-volatile memory Figure 80 will be displayed showing the status of the software upload.
8 Web Page Reference 171Reboot the unit by clicking the “Reboot Wireless Unit” button. You will be asked to confirm this action as shown in Figure 81. Figure 81 - Reboot Confirmation Pop Up This will reboot the unit, taking up to 120 seconds. During this time you will not be able to communicate with the unit. If you cannot communicate with the unit after 120 seconds, this could indicate a problem with the memory update process. Under these circumstances the user should enter “Recovery Mode”, see Section 9 “Recovery Mode”. After the reboot the user should check that the required software image is loaded and running. NOTE: Please ensure that you are upgrading the correct units. Units cannot be downgraded.
8 Web Page Reference 1728.3.7 Spectrum Management Spectrum Management Selection is the PTP 600 Series Bridge feature that monitors the available wireless spectrum and directs both ends of the wireless link to operate on a channel with a minimum level of co-channel and adjacent channel interference. 8.3.7.1 Wireless Channels The PTP 600 Series Bridge operates using a set of predefined overlapping channels. There are a different number of channels, depending on the raster mode selected. Each channel occupies 30 MHz, 20 MHz, 15 MHz, 10 MHz or 5 MHz of wireless spectrum and is offset in center frequency from its neighboring channel by 10 MHz or 6 MHz. It is important to note that adjacent channels on the Spectrum management display have a 10 MHz or 6 MHz overlap to the adjacent channel. The default channelization can be modified by varying the lower center frequency attribute in the installation wizard - see Section 8.3.4.4 “Wireless Configuration”. See Section 5.4 “Variable Channel Bandwidth Operation” and 5.10 “PTP 58600 Specific Frequency Planning Considerations” for more detail. 8.3.7.2 Spectrum Management Measurements The 600 Series Bridge performs two mean signal measurements per TDD cycle, per channel. This mean measurement represents the mean received signal power for the 40 microseconds measurement period. The Spectrum Management algorithm collects measurements equally from all channels. This process is called the Channel Availability Check (hereafter referred to by the acronym CAC). The CAC uses a round-robin channel selection process to collect an equal amount of measurements from each channel. It is important to note that the CAC measurement process is not altered by the channel barring process. Measurements are still collected for all channels irrespective of the number of barred channels. 8.3.7.3 Measurement Analysis Spectrum Management uses statistical analysis to process the received peak and mean measurement. The statistical analysis is based on a fixed, one minute, measurement quantization period. Spectrum Management collects data for the specified quantization period and only at the end of the period is the statistical analysis performed.
8 Web Page Reference 173The analysis produces three key metrics for each channel: x Peak of Means x 99.9% Percentile of the Means x Mean of Means Peak of Means is the largest mean interference measurement encountered during the quantization period. The peak of means is similar to the peak of peaks and is useful for detecting slightly longer duration spikes in the interference environment. 99.9% Percentile of the Means is the value of mean interference measurement which 99.9% of all mean measurements fall below, during the quantization period. The 99.9% percentile metric is useful for detecting short duration repetitive interference that by its very nature has a minimal effect of the mean of means. Mean of Means is the arithmetic mean of the measured means during a quantization period. The mean of means is a coarse measure of signal interference and gives an indication of the average interference level measured during the quantization period. The metric is not very good at predicting intermittent interference and is included to show the spread between the mean of means, the 99.9% percentile and the peak of means. NOTE: The arithmetic mean is the true power mean and not the mean of the values expressed in dBm. NOTE: Spectrum Management uses the 99.9% percentile as the prime interference measurement. All subsequent references to interference level refer to this percentile measurement. The display of statistical measurement on the spectrum management page always shows a statistical summary of all channel measurement. The statistical summary is controlled by the Statistics Window attribute. This attribute defaults to a value of twenty minutes, which means that the mean and percentile values displayed for each channel are calculated over the 20 minute period. All channel decisions are made using the values computed over the statistics window period. 8.3.7.4 The Spectrum Management Master / Slave Relationship The Spectrum Management operates in a master / slave relationship. The master is assumed to be the link master configured during installation. All Spectrum Management configuration changes MUST be performed from the master. To enforce this, the Spectrum Management web page has a different appearance depending if you are viewing the data from the master or slave.
8 Web Page Reference 174All configuration changes are applied at the master only. These changes are then messaged from the master to the slave. Any Spectrum Management configuration messages received at the slave are stored in non-volatile memory. This enables both master and slave to keep identical copies of Spectrum Management configuration data in their non-volatile memories. It is therefore possible to swap master and slave roles on an active Point-to-Point link without modifying Spectrum Management configuration. Figure 82 - Spectrum Management as seen from the Master
8 Web Page Reference 175 Figure 83 - Spectrum Management as seen from the Slave NOTE: These plots are for 30 MHz operation; 5/10/15/20 MHz operation is similar - the width of the vertical green bar represents the channel width. Figure 82 shows an example Spectrum Management webpage as seen from the master. Figure 83 shows an example Spectrum Management webpage as seen from the slave. It should be noted that the key configuration attributes are not available on the slave web page.
8 Web Page Reference 1768.3.7.5 Spectrum Management Configuration The following section describes the user modifiable configuration accessible from the Spectrum Management webpage. It is recommended that the default values are maintained. If the user believes that the performance of the Spectrum Management algorithm requires some modifications this should only be done after consulting your Motorola Point-to-Point distributor or one of the system field support engineers. Page Refresh Period: The page refreshes automatically according to the setting entered here (in seconds). Hopping Margin: Spectrum Management uses this margin when making a channel hop decision. The target channel has to have an interference level 3 dB (default) better than the current active channel. Hopping Period (not configurable): The Spectrum Management algorithm evaluates the metrics every ‘Hopping Period’ seconds (180 seconds by default) looking for a channel with lower levels of interference. If a better channel is located, Spectrum Management performs an automated channel hop. If SNMP or SMTP alerts are enabled an SNMP TRAP or an email alert is sent warning the system administrator of the channel change. Hopping Counter: is used to record the number of channel hops. The number in the “(+)” brackets indicates the number of channel changes since the last screen refresh. Interference Threshold: Spectrum Management uses the interference threshold to perform instantaneous channel hops. If the measured interference on a channel exceeds the specified threshold, then iDFS will instruct the wireless to immediately move to a better channel. If a better channel cannot be found the 600 Series Bridge will continue to use the current active channel. (Default –85 dBm) Asymmetric DFS: The default configuration of symmetric operation constrains the link to operate symmetrically, using the same transmit and receive channels. When in symmetric mode the slave unit will always follow the master. If the master moves to a new channel the slave will hop to the same channel. When the Point-to-Point link is configured as an asymmetric link both the master and slave are free to select the best channel from their own set of local interference metrics. Channel Bandwidth (not configurable): shows the value of the variable channel bandwidth selected.
8 Web Page Reference 1778.3.7.6 Barring Channels Channels can only be barred / unbarred by the system administrator from the master Spectrum Management web page. The barring / unbarring operations are disabled on the slave web page. If an attempt to bar / unbar a channel is made at the slave, a warning dialog is generated. Barring/Unbarring of channels is performed by clicking the appropriate channel on the local or peer channel spectrum plots on the master web page. Each bar / unbar attempt will be proceeded by a confirmation dialog. It should be noted that the channel bar will take effect immediately and is not related to the measurement quantization period. 8.3.7.7 Master and Slave Channel Spectrum Graphics Spectrum Management presents its computed statistical measurements in a graphical display on both the master and slave Spectrum Management web page. Figure 84 - Example Spectrum Management Graphic The X-axis shows a stylized view of the 9 or 10 selectable wireless channels. It is important to note that adjacent channels on the display have a 10 MHz overlap. The display separates the display of channels to help the clarity of the resultant display. The axis is labeled using the channel center frequencies in MHz. The Y-axis shows the interference power levels from –100 to –40 dBm. The active channel (channel 5 in Figure 84) is always marked using hatched green and white lines. The width of the hatching is directly proportional the channel bandwidth spectral occupancy of the channel. The individual channel metrics are displayed using a colored bar and an ‘I’ bar.
8 Web Page Reference 178The colored bar represents the following channel state: Table 34 - Spectrum Management change state key Green Active The channel is currently in use, hosting the Point-to-Point wireless link Orange Interference The channel has interference above the interference threshold Blue Available The channel has an interference level below the interference threshold and is considered by the Spectrum Management algorithm suitable for hosting the Point-to-Point link Grey Barred The system administrator has barred this channel from use. For improved visibility, an additional red ‘lock’ symbol is used to indicate that a channel is barred. The top of the colored bar represents the 99.9% percentile metric for specific channel. The ‘I’ Bar is used to display the mean of means and peak of means metrics. The lower horizontal bar represents the mean of means and the upper horizontal bar represents the peak of means. The vertical bar is used as a visual cue to highlight the statistical spread between the peak and the mean of the statistical distribution.
8 Web Page Reference 1798.3.7.8 Active Channel History The active channel history is a time series display of the channels used by the PTP 600 Series Bridge over the last 25 hours. The active channel history is activated from the main Spectrum Management page using the ‘Active Channel History’ hyperlink. An example of the active channel history display is shown in Figure 85. Where there are parallel entries on the display this signifies that the wireless link occupied this channel during the measurement period. The measurement periods are one minute (from zero to sixty minutes) and twenty minutes from (60 minutes to twenty five hours). Figure 85 - Active Channel History Screen
8 Web Page Reference 180 8.3.7.9 Viewing Historic Spectrum Management Metrics Spectrum Management allows the system administrator to view the results of previous measurement quantization periods. Holding down the shift key and clicking the appropriate channel on the local channel spectrum plots activates this feature. This feature is available on both the master and slave web page. Figure 86 - Spectrum Management Time Series Plot Figure 86 shows an example time series plot. A time series plot displays the previous 132 measurement quantization periods. If the PTP 600 Series Bridge has not been running for 132 quantization periods then only the number of measurement quantization periods that are available are displayed. Table 35 - Spectrum Management Time Series Key GREEN Peak of Means interference measurement BLACK 99.9% percentile of means interference measurement BLUE Mean of Means interference measurement
8 Web Page Reference 1818.3.8 Spectrum Management (Fixed Frequency) The PTP 600 Series Bridge software allows a user to optionally fix transmit and receive frequencies for a wireless link. Once configured, the spectrum management software will not attempt to move the wireless link to a channel with lower co and adjacent channel interference. Therefore this mode of operation is only recommended for deployments where the installer has a good understanding the prevailing interference environment. (See Section 8.3.4.4 “Wireless Configuration”). Care must also be taken to ensure that the frequency allocations at each end of the link are compatible. To help the user when identifying the mode of operation Spectrum Management uses two visual cues. See Figure 87. The main page title identifies the mode of operation using the “Fixed Frequency Mode” postfix and the selected channels are identified by a red capital ‘F’. Figure 87 - Spectrum Management Fixed Frequency Screen Channel barring is disabled in fixed frequency mode; it is not required as dynamic channel hopping is prohibited in this mode.
8 Web Page Reference 182The only controls available to the master are the Statistics Window and Interference Threshold attributes. They will have no effect on the operation of the wireless link and will only effect the generation of the channel spectrum graphics. The active channel history menu is removed in this mode of operation as channel hopping is prohibited. Figure 88 - Spectrum Management Help Page (Fixed Frequency) 8.3.9 Spectrum Management Control - With Operational RestrictionsWhen operating with Radar Avoidance enabled the following variances in operation apply: x The words “Radar Avoidance” are appended to the “Spectrum Management” title at the top of the screen. See Figure 89 and Figure 90. x The only controls available to the master are the Interference Threshold attribute. This has no effect on the operation of the wireless link and will only affect the generation of the channel spectrum graphics. See Figure 89.
8 Web Page Reference 183x Extra color coding of the interference histogram is provided. See Table 36. When operating with RTTT (Road transport and Traffic Telematics) Avoidance enabled or other regulatory restrictions on channel usage the following variances apply: x All channels marked with a ‘no entry’ symbol with their associated statistics colored black are the prohibited channels. See Figure 89 and Figure 90. These channels are never used to host the wireless link, but CAC measurements are still taken so that adjacent channel biases can be calculated correctly and so the user can see if other equipment is in use. Figure 89 - Spectrum Management Master Screen With Operational Restrictions
8 Web Page Reference 184Figure 90 - Spectrum Management Slave Screen With Operational Restrictions The colored bar represents the following channel state: Table 36 - Spectrum Management Change State Key With Operational Restrictions Green Active The channel is currently in use hosting the Point-to-Point wireless link Orange Interference The channel has interference above the interference threshold Blue Available The channel has an interference level below the interference threshold and is considered by the Spectrum Management algorithm suitable for hosting the Point-to-Point link Grey Barred The system administrator has barred this channel from use. Because the low signal levels encountered when a unit is powered up in a laboratory environment prior to installation (which makes the grey of the channel bar difficult to see). An additional red ‘lock’ symbol is used to indicate that a channel is barred. Red Radar Detected Impulsive Radar Interference has been detected on this channel and the channel is unavailable for 30 minutes. At the end of the 30 minute period a Channel Availability Check is required to demonstrate no radar signals remain on this channel before it can be used for the radio link.
8 Web Page Reference 185Region Bar Region Bar This channel has been barred from use by the local region regulator 8.3.10 Spectrum Management – Example of PTP 25600 Product variant As described in Section 5.5 “PTP 25600 Specific Frequency Planning Considerations”, the PTP 25600 product variant can operate in three frequency bands. Figure 91 shows an example of a Lower Band with a 30 MHz channel bandwidth. Figure 91 - PTP 25600 Example of Spectrum Management Page
8 Web Page Reference 1868.3.11 Remote Management Page The Remote Management page (Figure 92) allows the system administrator to configure the remote management of the PTP 600 Series Bridge. Figure 92 - Remote Management
8 Web Page Reference 187 8.3.11.1 Control Access to HTTP Interface The attribute HTTP Access Enabled allows a user to stop any access to a unit via the web interface. The default value for this control is set to “yes”, which means that the unit can be accessed using the web interface. If the option “No” is selected, then a warning is displayed as shown in Figure 93. 8.3.11.2 Control Access to Telnet Interface The attribute HTTP Telnet Enabled allows a user to stop any access to a unit via the telnet interface. The default value for this control is set to “yes”, which means that the unit can be accessed using the telnet interface. NOTE: If HTTP, Telnet and SNMP interfaces have been disabled, then the user needs to use the Recovery image to reset IP & Ethernet Configuration back to factory defaults to re-enable the HTTP-Telnet interfaces. SNMP can also be used to re-enable the other interfaces if SNMP is enabled.8.3.11.3 SNMP (Simple Network Management Protocol) The industry standard remote management technique is SNMP (Simple Network Management Protocol). The PTP 600 Series Bridge supports version 1 and version 2c of the SNMP protocol. 8.3.11.4 Supported Management Information Bases (MIBS) The PTP 600 Series Bridge SNMP stack currently supports the following MIBs: x MIB-II, RFC-1213, The PTP 600 Series Bridge supports the ‘System Group’ and ‘Interfaces Group’. x Bridge MIB, RFC-1493, The PTP 600 Series Bridge supports the ‘dot1dBase Group’ and the ‘dot1dBasePortTable Group’. x PTP 600 Series Bridge proprietary MIB x RFC-2233 (High capacity counter) MIB x WiMAX MIB
8 Web Page Reference 188SNMP TRAPs supported: x Cold Start x Link Up x Link Down x DFS Channel Change x DFS Impulsive Interference Figure 93 – Warning when disabling HTTP interface
8 Web Page Reference 1898.3.11.5 Diagnostics Alarms A number of diagnostics alarms have been added to allow SNMP agents to receive traps and emails if required. Refer to Section 8.1.1 “Home Page Alarm Display” for a description of all these alarms. Checking the control “Enabled Diagnostic Alarms” in SNMP and/or SNTP selects all the alarms shown in Figure 94. Users can access the sub-menu “Diagnostic Alarms” to modify the alarms selected. Figure 94 - Remote Management - Diagnostic Alarms For a copy of the Motorola proprietary version 1 and version 2 MIB RFCs please consult the installation CD
8 Web Page Reference 1908.3.11.6 SNMP Configuration SNMP State: The SNMP state attribute controls the creation of the SNMP features. Changing the SNMP state attribute requires a mandatory reboot of the unit. Only when the SNMP state is enabled at system start-up will the SNMP processor task be created. SNMP Enabled Traps: The SNMP Enabled Traps attribute controls which SNMP Traps the unit will send. SNMP Community String: The SNMP community string acts like a password between the networks SNMP management entity and the distributed SNMP clients (600 Series bridge). Only if the community string is configured correctly on all SNMP entities can the flow of management information take place. By convention the default value is set to ‘public’. When the community string is changed the system requires a mandatory reboot before the new string or phrase is adopted. SNMP Port Number: Is the port the SNMP management agent is listening to for commands from an SNMP manager. The default value for this port number is 161. SNMP Trap IP Address: Is the address of either the network SNMP manager or Trap receiver. When asynchronous events (traps in SNMP terminology) are generated, the client unicasts these to this IP Address. When the address is changed the system requires a mandatory reboot before the setting is adopted SNMP Trap Port Number: The SNMP Trap Port Number is the port number of either the networked SNMP manager or Trap receiver. By convention the default value for the port number is 162. When the port number is changed the system requires a mandatory reboot before the setting is adopted. WiMAX Control: Enables and Disables the WiMAX (802.16) MIB. This control is only displayed when ‘Fixed Frequency’ is selected during installation. 8.3.11.7 SMTP (Simple Mail Transport Protocol) The SMTP client is an alternative method for the 600 Series bridge to alert a system administrator when there are or have been system errors SMTP Email Alert: This attribute controls the activation of the SMTP client. SMTP Enabled Messages: The SMTP Enabled Messages attribute controls which email alerts the unit will send. SMTP IP Address: The IP address of the networked SMTP server.
8 Web Page Reference 191SMTP Port Number: The SMTP Port Number is the port number used by the networked SMTP server. By convention the default value for the port number is 25. SMTP Source Email Address: The email address used by the 600 Series to log into the SMTP server. This must be a valid email address that will be accepted by your SMTP Server. SMTP Destination Email Address: The email address to which the 600 Series bridge will send the alert messages. 8.3.11.8 SNTP (Simple Network Time Protocol) The SNTP client allows the 600 Series to obtain accurate date and time updates from a networked timeserver. The system time is used for SNMP and event logging. SNTP State: When enabled, the Remote Management web page permits the following attributes to be set: SNTP IP Address: The IP address of the networked SNTP server. SNTP Port Number: The port number of the networked SNTP server. By convention the default value for the port number is 123. SNTP Poll Interval: The period at which the SNTP client polls the server for time correction updates. Default 1 hour. If for any reason an SNTP poll fails, the client will automatically perform 3 retries before waiting for the user defined poll period. Time Zone: The time zone is a fixed offset from GMT that is added to the SNTP time to allow the expression of time in all geographic time zones. Daylight Saving: Allows a fixed offset of one hour to be added to the SNTP time in order to reflect the local daylight saving time. 8.3.11.9 Setting the clock The PTP 600 Series bridge has a system clock which can be used to supply accurate date and time information in the absence of a SNTP server. The system clock is battery backed and will continue to operate for several days if the 600 Series bridge has been switched off. SNTP State: If the SNTP State is set to “Disabled”, see Figure 92, then the Remote Management web page allows the following attributes to be set: Set Time: Shows the current time in 24 hour mode. The three editable fields display hours minutes and seconds.
8 Web Page Reference 192Set Date: Displays the current date. The year, month and day can be set using the drop-down selection boxes. Time Zone: See Section.8.3.11.9 “Setting the clock”. Daylight Saving: See Section 8.3.11.9 “Setting the clock” 8.3.12 Diagnostics To further enhance the diagnostic capabilities of the PTP 600 Series, the storage of link performance histograms has been extended to 31. To optimize RAM (volatile memory) usage a cascading histogram approach has been adopted. The root histogram is identical to the histograms in earlier releases of the software, that is data is stored for one hour at a resolution of one second. Previously, the histograms were simple cyclic buffers which never stored more that the last one hour of data. The new cascading histogram approach daisy chains multiple histograms together. When the first histogram fills up the overflow from the first is used as an input to the next histogram in line. To optimize memory utilization, a statistical analysis is performed on the overflow to reduce the amount of data to be stored. In the case of the PTP 600 Series the cascading histograms are defined as: x Histogram 1: 1 hour at a resolution of 1 second x Histogram 2: 24 hours at a resolution of 1 minute x Histogram 3: 30 Days at a resolution of 1 hour For example, when histogram 1 fills up and starts to overflow the first minute of overflow is analyzed and the maximum, minimum and mean over that minute are computed and inserted into histogram 2. When histogram 2 fills up and starts to overflow the first hour of overflow is analyzed and the maximum, minimum and mean over that hour is computed and inserted into histogram 3. When histogram 3 starts to overflow, the overflow data is simply discarded.
8 Web Page Reference 1938.3.12.1 Diagnostic Plotter New for the PTP 600 Series is the system administration diagnostic plotter facility see Figure 95. Figure 95 - Diagnostic Plotter The diagnostic plotter allows the system administrator to view the cascading histogram data in an easily accessible graphical form. The plot always displays three traces, maximum, minimum and mean by default. The diagnostic selector allows the user to select the various categories of histogram. The histograms that are available are: x Vector Error x Rx Power x Tx Power x Signal Strength Ratio x Link Loss x Rx Data Rate x Tx Data Rate x Aggregate Data Rate The diagnostic plotter uses a novel time representation in the x-axis which compresses the timeline of the plot without sacrificing resolution.
8 Web Page Reference 194The trace selection allows the user to control which traces are plotted. As with other management pages the page refresh period can be used to interactively monitor the wireless link. 8.3.12.2 Diagnostics Download The diagnostics Download page allows the system administrator to download snapshots of system diagnostics. Figure 96 - CSV Download The following diagnostics are available: x Vector Error x Rx Power x Tx Power x Signal Strength Ratio V/H x Link Loss x Rx Data Rate x Tx Data Rate x Aggregate Data Rate x Receive SNR x Rx Gain All diagnostics are extracted from the associated status and statistics web page histograms. They are translated in a CSV file containing at most 5784 entries. These 5784 entries comprise 3600 entries for the first hour, 1440 entries for the next 24 hours and 744 entries for the next 31 days.
8 Web Page Reference 1958.3.13 Change System Administration Password This page (Figure 97) is used to change the password for the system administration (The factory default is blank). Figure 97 - Password Change The password may contain any combination of characters, up to 31 characters in length. 8.3.14 License Key The License Key data entry page allows the system administrator to update the 600 Series bridge license key. Figure 98 shows a sample license key data entry page. Figure 98 - Software License Key Data Entry
8 Web Page Reference 196 The user must enter the license key and click the ‘Validate License Key’ button to check that the key is valid and program it to non-volatile memory. If a valid license key is detected then the user will be presented by a system reboot screen. Figure 99: License Key reboot Screen The user will then be asked to confirm the reboot (Figure 100). Figure 100 - Reboot Confirmation Pop Up
8 Web Page Reference 197 8.3.15 Properties The web page properties screen allows the user to configure the web page interface. Figure 101 – Properties WEB Properties: Disable Front Page Login. Allows access to homepage and status page web pages without forcing a login as the system administrator. WEB Properties: Disable HTTP NO-CACHE META data. Removes the HTTP NO-CACHE META clause from all dynamically created web pages. Auto Logout Timer Configures the time, in minutes, when the system administrator is automatically logged out if no web page activity is detected. Distance Units Swaps the default metric display of distance in to imperial units, for example km to Miles. Use Long Integer Comma Formatting Changes the format of long integers from 1000000 to 1,000,000.
8 Web Page Reference 1988.3.16 Reboot The reboot page allows the system administrator to perform commanded reboots of the wireless unit. The reboot page also allows the system administrator to view a list of past reboot reasons. The “Previous Reasons For Reset/Reboot” field has been implemented as a drop down selection box, where the latest reason for reboot is located at the top of the list. If the SNTP service from the remote management section above is active, or the system time has been set, then the command reboot reason will be accompanied by the date and time at which the reboot occurred. Figure 102 - System Reboot Figure 103 - Reboot Confirmation Pop Up
9 Recovery Mode 1999 Recovery Mode The Motorola PTP 600 point-to-point wireless Ethernet bridges have a special mode of operation that allows the user to recover a unit from configuration errors or software image corruption. Recovery mode is entered by depressing the Recovery Switch located on the underside of the PIDU Plus while applying mains power, as shown in Section 3.3.2 “PIDU Plus – PTP 600 Series Bridge” The Recovery Switch should be held in the depressed state for between 10 and 20 seconds after the application of mains power. The Ethernet LED will flash with 10 double flashes at power up (following the release of the Recovery switch). When in recovery mode the user will be able to access the unit via the Ethernet interface. The Ethernet interface will have its IP address set to 169.254.1.1 (or 10.10.10.10 see section 7.7.10 “Powering Up”). On connection to a unit in recovery mode the following screen is displayed (Figure 104): Figure 104 - Recovery Mode Warning Page
9 Recovery Mode 200Clicking on the warning page image will take the user on to the Recovery Option Page (Figure 105). Figure 105 - Recovery Options Page The recovery options available are: Upgrade Software Image: This allows the user to reload a software image. This may be the original image if software corruption is suspected or a step back to an old image if an incorrect image has just been loaded. Reset IP & Ethernet Configuration back to factory defaults: This allows the user to reset the unit back to the factory defaults: x IP Address 169.254.1.1 (or 10.10.10.10) x Netmask 255.255.0.0 x Gateway 169.254.1.0 x Ethernet Interface Auto-negotiate, Auto-MDI/MDIX Erase Configuration: This allows the user to erase the unit’s entire configuration. Executing this option will also erase factory settings such as target MAC address, range setting, license key, etc. Reboot: This allows the user to reboot the unit. This option must be executed after resetting the IP & Ethernet configuration or erasing the configuration detailed above. Software Version: This is the software version of the recovery operating system permanently installed during manufacture.
9 Recovery Mode 201Recovery Reason: Indicates the reason the unit is operating in Recovery mode. Possible reasons are “Recovery button active” or “Invalid or corrupt image” MAC Address: The MAC address shown here is the MAC address of the unit programmed during manufacture. 9.1 Upgrade Software Image The first step (Figure 105) is to use the ‘Browse’ button to locate the software image to be downloaded. Once located the user should press the “Upgrade Software Image” button to start the software download process. During software download, progress is indicated by a pair of progress bars (Figure 106). Figure 106 - Software Download Progress Indicator Page When the download is complete a page is displayed indicating the status of the software download (Figure 107). Figure 107 - Software Download Complete Page
9 Recovery Mode 202After carefully checking that correct image has been downloaded the user should reboot the unit by pressing the “Reboot Wireless Unit” button. The user will then be presented with a pop up box asking them to confirm the action (Figure 108). Figure 108 - Reboot Confirmation Pop Up The unit will now reboot. Providing the unit configuration is still intact the unit should restart in normal operational mode and the link should recover. Should the unit or link fail to recover the user should refer to Section 11 “ (Fault Finding”.
9 Recovery Mode 2039.2 Reset IP & Ethernet Configuration To reset IP & Ethernet configuration back to factory defaults the user should press the “Reset IP & Ethernet Configuration back to factory defaults” button on the “Recovery Options” page (1Figure 105). The user will now be presented with a pop up box asking them to confirm the action (Figure 109). Figure 109 - Confirm Reset to Factory Default Pop Up On confirmation the following page will be displayed (Figure 110). The user should now reboot the unit by pressing the “Reboot” button. Figure 110 - IP and Ethernet Erased Successfully page
9 Recovery Mode 204 The user will now be presented with a pop up box asking them to confirm the action (Figure 111). Figure 111 - Reboot Confirmation Pop Up The unit will now reboot. The unit should now start up in normal mode but with the IP address set to 169.254.1.1 and the Ethernet interface set to auto-negotiate and auto-MDI/MDIX. Should the unit fail to start up the user should refer to Section 11 “ (Fault Finding”. 9.3 Erase Configuration To erase the unit’s configuration the user should press the “Erase Configuration” button on the “Recovery Options” page (Figure 105). The user will now be presented with a pop up box asking them to confirm the action (Figure 112). Figure 112 - Confirm Erase Configuration Pop Up
9 Recovery Mode 205On confirmation the following page will be displayed (Figure 113). The user should now reboot the unit by pressing the “Reboot” button. Figure 113 - Erase Configuration Successful Page
9 Recovery Mode 206The user will now be presented with a pop up box asking them to confirm the action (Figure 114) Figure 114 – Erase Configuration - Reboot Confirmation Pop Up The unit will now reboot. The unit should now start up in normal mode but with all configuration erased. Should the unit fail to start up the user should refer to Section 11 “ (Fault Finding”.
9 Recovery Mode 2079.4 RebootThis option can be used to reboot the unit. The user will now be presented with a pop up box asking them to confirm the action (Figure 115). Figure 115 – Recovery - Reboot Confirmation Pop Up The unit will now reboot. The unit should now start up in normal operational mode. Should the unit fail to start up the user should refer to Section 11 “Troubleshooting (Fault Finding)”.
10 Lightning Protection 20810 Lightning Protection CAUTION: EMD (Lightning) damage is not covered under standard warranty. The recommendations in this user manual, when implemented correctly, give the user the best protection from the harmful effects of EMD. However 100% protection is neither implied nor possible. 10.1 Overview The purpose of lightning protection is to protect structures, equipment and people against lightning by conducting the lightning current to ground via a separate preferential solid path. The following should be treated as a guide only. The actual degree of lightning protection required depends on local conditions and weather patterns and applicable local regulations. Full details of lightning protection methods and requirements can be found in the international standards IEC 61024-1 and IEC 61312-1, the U.S. National Electric Code ANSI/NFPA No. 70-1984 or section 54 of the Canadian Electric Code. 10.1.1 Lightning Protection Zones The installation of the ODU can be classified into two different lightning protection zones: x Zone A: In this zone a direct lighting strike is possible. x Zone B: In this zone a direct lightning strike is unusual, but the un-attenuated electromagnetic eld is still present. The zones are determined using the ‘rolling sphere method’, an imaginary sphere, typically 50 meter in radius is rolled over the structure. All structure points that contact the sphere, (Zone A) indicate the zone where a direct strike is possible. Similarly points that do not contact the sphere indicate a zone (zone B) where a direct strike is less likely.
10 Lightning Protection 209The following diagrams (Figure 116 & Figure 117) show this zoning pictorially: Equipment mounted in Zone A should be capable of carrying the full lightning current. Mounting of the ODU in Zone A is not recommended. Mounting in Zone A should only be carried out observing the rules governing installations in Zone A Failure to do so may put structures, equipment and life at risk. NOTE: Local regulations may also require the fitting of the 8 AWG ground wire referred below.Equipment mounted in Zone B should be grounded using grounding wire of at least 10 AWG. This grounding wire should be connected to a grounding rod or the building grounding system before entry in to building. The PTP 600 Series bridge ODU grounding point can be found on the bottom of the unit. The 600 Series Bridge is supplied with an appropriate grounding lug for attachment to the ODU. Figure 116 - ODU mounted in Zones A & B
10 Lightning Protection 210Figure 117 - Showing how the use of a Finial enables the ODU to be mounted inside Zone B Table 37 - Protection Requirements Component Zone A Zone B Earth ODU Mandatory Mandatory Screen Cable Mandatory Mandatory Lightning Protection Unit at ODU – PTP-LPU Mandatory Mandatory Earth Cable at Building Entry Mandatory Mandatory Lightning Protection Unit at Building Entry – PTP-LPU Mandatory Mandatory
10 Lightning Protection 211 10.2 Detailed Installation The PTP LPU can be installed in one of the following configurations: x Option 1: Back-to-Back with the ODU using the supplied brackets delivered part of the installation of a link. This is the configuration recommended by Motorola. x Option 2: using the U-Bolt bracket supplied with the PTP LPU Kit. Typical examples of these two configurations are shown in Figure 118 and Figure 119. NOTE: Grounding Points are shown unprotected for clarity. Grounding points should be adequately weatherproofed to prevent corrosion and possible loss of ground continuity. Figure 118 – Example of PTP-LPU Configuration – Option 1 (Back-to-Back Recommended)
10 Lightning Protection 212Figure 119 - PTP-LPU - Installation Option 2 (Using U-Bolt) A second Lightning protection Unit should be mounted at the building entry point and must be grounded. The PTP-LPU Kit is supplied with a 600mm ODU to PTP-LPU cable pre-fitted with glands. Figure 120 shows all the components that are supplied with the Motorola Kit 2907.
10 Lightning Protection 213Figure 120 - PTP LPU Full Kit The cable between the two lightning protection units (top and bottom) should be of the type recommended by Motorola (Section 3.3.5 “Cables and connectors”) and terminated as shown in Figure 38.
10 Lightning Protection 21410.3 Installation Wiring Figure 121 shows the correct installation wiring for a PTP 600 with lightning protection. Figure 121 - Simplified Circuit Diagram
10 Lightning Protection 21510.4 LPU Recommended Configurations This section contains diagrams to show how the components of PTP 600 sites are installed and connected. The diagrams cover the following configurations: x Typical mast or tower installation x Typical wall installation x Mast or tower installation with E1/T1 x Wall installation with E1/T1 x Mast or tower installation with GPS Sync Box x Wall installation with GPS Sync Box x Mast or tower installation with GPS Sync Box and E1/T1 x Wall installation with GPS Sync Box and E1/T1 The recommended components are listed under each diagram. The recommended cables are specified in Section 3.3.5 “Cables and connectors”. NOTE: There may be a local regulatory requirement to cross bond the CAT 5e cable at regular intervals to the mast or tower. This may be as frequent as every 10 meters (33 feet).
10 Lightning Protection 216 10.4.1 Typical Mast or Tower Installation Figure 122 shows a typical PTP 600 Series Mast or Tower installation using PTP-LPU Surge protection for a configuration without a GPS Sync box or E1/T1 ports. Figure 122 - Typical Mast or Tower Installation The recommended components for this installation are: x Surge Arrestor: Motorola PTP- LPU - 4 per link (2 Motorola Kits Part Number 2907) x Grounding Stake x RJ45 screened connectors
10 Lightning Protection 21710.4.2 Typical Wall Installation Figure 123 shows a typical PTP 600 Series Wall installation using PTP-LPU Surge protection for a configuration without a GPS Sync box or E1/T1 ports. Figure 123 - Typical Wall Installation The recommended components for this installation are: x Surge Arrestor: Motorola Type PTP-LPU - 4 per link (2 Motorola Kits Part Number 2907) x Grounding Stake x RJ45 screened connectors x 8 AWG Grounding Cable – Minimum size, preferably 6 or 4
10 Lightning Protection 21810.4.3 Mast or Tower Installation with E1/T1 Figure 124 shows a typical PTP 600 Series Mast or Tower installation using PTP-LPU Surge protection for a configuration that includes E1/T1 ports. Figure 124 – Mast or Tower Installation with E1/T1 The recommended components for this installation are: x Surge Arrestor: Motorola Type PTP-LPU - 8 per link (4 Motorola Kits Part Number 2907) x Grounding Stake x RJ45 screened connectors
10 Lightning Protection 21910.4.4 Wall Installation with E1/T1 Figure 125 shows a PTP 600 Series Wall installation using PTP-LPU Surge protection for a configuration that includes E1/T1 ports. Figure 125 - Wall Installation with E1/T1 The recommended components for this installation are: x Surge Arrestor: Motorola Type PTP-LPU - 8 per link (4 Motorola Kits Part Number 2907) x Grounding Stake x RJ45 screened connectors x 8 AWG Grounding Cable – Minimum size, preferably 6 or 4
10 Lightning Protection 22010.4.5 Mast or Tower Installation with GPS Sync Box Figure 126 shows a PTP 600 Series Mast or Tower installation using PTP-LPU Surge protection for a configuration that includes a GPS Sync box. Figure 126 – Mast or Tower Installation with GPS Sync Box The recommended components for this installation are: x Surge Arrestor: Motorola Type PTP-LPU - 4 per link (2 Motorola Kits Part Number 2907) x GPS Sync Box from MemoryLinkl – 1 per link (1 Motorola kit) x Grounding Stake x RJ45 screened connectors
10 Lightning Protection 22110.4.6 Wall Installation with GPS Sync Box Figure 127 shows a PTP 600 Series Wall installation using PTP-LPU Surge protection for a configuration that includes a GPS Sync box. Figure 127 –Wall Installation with GPS Sync Box The recommended components for this installation are: x Surge Arrestor: Motorola Type PTP-LPU - 4 per link (2 Motorola Kits Part Number 2907) x GPS Sync Box from MemoryLinkl – 1 per link (1 Motorola kit) x Grounding Stake x RJ45 screened connectors x 8 AWG Grounding Cable – Minimum size, preferably 6 or 4
10 Lightning Protection 22210.4.7 Mast or Tower Installation with GPS Sync Box and E1/T1 Figure 128 shows a PTP 600 Series Mast or Tower installation using PTP-LPU Surge protection for a configuration that includes a GPS Sync box and E1/T1 ports. Figure 128 - Mast or Tower Installation with GPS Sync Box and E1/T1 The recommended components for this installation are: x Surge Arrestor: Motorola Type PTP-LPU - 8 per link (4 Motorola Kits Part Number 2907) x GPS Sync Box from MemoryLinkl – 1 per link (1 Motorola kit) x Grounding Stake x RJ45 screened connectors
10 Lightning Protection 22310.4.8 Wall Installation with GPS Sync Box and E1/T1 Figure 129 shows a PTP 600 Series Wall installation using PTP-LPU Surge protection for a configuration that includes a GPS Sync box and E1/T1 ports. Figure 129 - Wall Installation with GPS Sync Box and E1/T1 The recommended components for this installation are: x Surge Arrestor: Motorola Type PTP-LPU - 8 per link (4 Motorola Kits Part Number 2907) x GPS Sync Box from MemoryLinkl – 1 per link (1 Motorola kit) x Grounding Stake x RJ45 screened connectors x 8 AWG Grounding Cable – Minimum size, preferably 6 or 4
11 Troubleshooting (Fault Finding) 22411 Troubleshooting (Fault Finding) Perform troubleshooting (fault finding) procedures either on a newly installed link, or on an operational link if communication is lost: 1. Test the hardware at one end of the link, as described in Section 11.1 “Test Link End Hardware”. 2. Test the hardware at the other end of the link, as described in Section 11.1 “Test Link End Hardware”. 3. Test the radio link, as described in Section 11.2 ”Test Radio Link”. 11.1 Test Link End Hardware When the link end hardware (PIDU, LPU, ODU and cabling) has been installed, start it by following this procedure: 1. Connect the RJ45 from the ODU (or LPU if fitted) to the PIDU and apply mains or battery power to the PIDU. The green Power LED should illuminate continuously. 2. After 45 seconds, the yellow Ethernet LED should be observed starting with 10 slow flashes. 3. Connect the RJ45 from the LAN port of the PIDU to the network. The yellow Ethernet LED should blink randomly as traffic passes through. If the Power and Ethernet LEDs do not illuminate correctly, test the link end as described in the flowchart (Figure 130). NOTE:The flowchart contains references to the detailed test procedures 11.1.1 to 11.1.7.
11 Troubleshooting (Fault Finding) 225Figure 130 – Link End Hardware Test Flowchart Start Is the green power LED on solid? Is the power LED flashing?Did the Ethernet LED flash 10 Is Ethernet activity now normal? Is Ethernet connection 1000 BaseT? No Power LED is Off (11.1.1) Power LED Flashes (11.1.2) No Yes Yes Ethernet LED did not Flash 10 Times (11.1.3) No Yes Yes No Is there any Ethernet activity?Irregular Ethernet Activity (11.1.5) No Ethernet Activity (11.1.4) No Yes Connection is not 1000 BaseT (11.1.6) Test RJ45 Resistance (11.1.7) Yes No
11 Troubleshooting (Fault Finding) 226 11.1.1 Power LED is Off If the green Power LED does not light up at all, perform the following tests: 1. Remove the power lead from the PIDU and test that the power source (mains or 56 V battery) is working. 2. If the main or battery power supply is working, open the flap on the left hand side of the PIDU and remove the RJ45 ODU cable from the PIDU. 3. If the Power LED does not illuminate when the RJ45 ODU cable is removed: i. Measure the voltage across the +55 V and 0 V pads inside the PIDU flap. An incorrect reading indicates that the PIDU is short-circuited. ii. Measure the impedance across the Power connector. An incorrect reading indicates that the PIDU is short-circuited. iii. If both of the above tests are successful, it is likely that the PIDU Power LED is faulty. 4. If the Power LED does illuminate when the RJ45 ODU cable is removed: i. Remove the jumper (J906) found inside the PIDU flap. ii. Measure the current with an ammeter placed across the two jumper pins. It should be 10 mA with the ODU disconnected. An incorrect ammeter reading indicates that the PIDU is faulty. 5. If all tests so far have succeeded: i. Reconnect the RJ45 ODU cable to the PIDU. ii. Measure the current with an ammeter placed across the two jumper pins. It should be in the range 300 mA to 1 A with the ODU connected. iii. If the ammeter reading is too high, the ODU may be drawing too much power, or the ODU may be short-circuited. iv. If the ammeter reading is too low, the PIDU may be supplying too little power.
11 Troubleshooting (Fault Finding) 227 11.1.2 Power LED is Flashing If the green Power LED flashes, perform the following tests on the RJ45 cable that connects the PIDU to the LPU or ODU: 1. Check that pins 4&5 and 7&8 are not crossed with pins 1&2 and 3&6. 2. Check that the resistance between pins 1&8 is greater than 100K ohms. 3. If either test fails, replace or repair the RJ45 cable. 11.1.3 Ethernet LED did not Flash 10 Times When the PIDU is connected to the power supply and the green Power LED illuminates, there should be a 45 second delay, following which the yellow Ethernet LED should flash 10 times. If the Ethernet LED did not flash 10 times, perform the following tests on the RJ45 cable that connects the PIDU to the LPU or ODU: 1. Check that the wiring to pins 4&5 and 7&8 is correct. For example, the wiring to pins 4 and 7 may be crossed. 2. If an LPU is installed, it can be used to check that power is available on the cable to the ODU. The connections can be accessed by rotating the LPU lid as shown in Figure 131 The Lid nut only needs to be slacken, do not remove. Test point P1 on the LPU PCB corresponds to pin 1 on the RJ45 etc. An indication of power on the Ethernet cable is also provided inside the LPU: the LED PWR1 should illuminate but LED PWR2 should not.
11 Troubleshooting (Fault Finding) 228Figure 131 - PTP LPU Test Points 3. If either test fails, replace or repair the RJ45 cable. 11.1.4 No Ethernet Activity If the Ethernet LED did flash 10 times but then went off, check that the RJ45 connection from the LAN port of the PIDU to the PC is working. If the PC connection is working, perform the following tests on the RJ45 cable that connects the PIDU to the LPU or ODU: 1. Check that the wiring to pins 1&2 and 4&6 is correct. For example, the wiring to pins 1 and 3 may be crossed. 2. If this test fails, replace or repair the RJ45 cable.
11 Troubleshooting (Fault Finding) 22911.1.5 Irregular Ethernet Activity The yellow Ethernet LED should blink randomly as normal traffic passes through. If the Ethernet LED flashes irregularly, for example there is a short flash followed by a long flash, this indicates that the ODU has booted in recovery mode. The causes may be installation wiring or a corrupt ODU software load. For more information, see Section 9 “Recovery Mode”. 11.1.6 Connection is not 1000 BaseT If the Ethernet connection to the network is only 10/100 BaseT, when 1000 BaseT is expected, perform the following tests on the RJ45 cable that connects the PIDU to the LPU or ODU: 1. Check that the wiring to pins 4&5 and 7&8 is correct. For example, the wiring to pins 4 and 7 may be crossed. 2. If this test fails, replace or repair the RJ45 cable. 11.1.7 Test RJ45 Resistance If the above procedures fail to diagnose the issue, there may be a fault in the wiring of the RJ45 cable that connects the ODU (or LPU) to the PIDU. Unplug this cable from the PIDU, then perform the following test procedure: 1. Check the cable resistance between pins 1&2, 3&6, 4&5 and 7&8 at the RJ45. Check against column 2 in Table 38. Resistances for each pair should be within 1 ohm of each other. 2. Check the cable resistance between pins 1&3 and 4&7 at the RJ45. Check against columns 3 and 4 respectively in Table 38. 3. Ensure that there is greater than 100K ohms between pins 1&8 for all cable lengths. 4. Ensure that there is greater than 100K ohms between pin 1 and ODU ground for all cable lengths. 5. If GPS is not fitted, ensure that there is greater than 100K ohms between pin 8 and ODU ground for all cable lengths. If GPS is fitted, ensure there is greater than 3K ohms between pin 8 and ODU ground.
11 Troubleshooting (Fault Finding) 230 Table 38 - Resistance Table Referenced To The RJ45 at the PIDU+ Resistances should fall within + or -10% of the stated values. CAT-5 Length(Meters) Resistance between pins 1&2, 3&6 , 4&5 and pins 7&8 (ohms) Resistance between pins 1&3 (ohms) Resistance between pins 4&7 (ohms) 0 0.8 1.0 1.6 10 2.7 2.7 3.3 20 4.6 4.4 5.0 30 6.5 6.1 6.7 40 8.3 7.8 8.4 50 10.2 9.5 10.1 60 12.1 11.2 11.8 70 14.0 12.9 13.5 80 15.8 14.6 15.2 90 17.7 16.3 16.9 100 19.6 18.0 18.6 150 29.0 26.5 27.1 200 38.4 35.0 35.6 250 47.7 43.5 44.1 300 57.1 52.0 52.6
11 Troubleshooting (Fault Finding) 231 11.2 Test Radio Link 11.2.1 No Activity If there is no communication over the radio link and the unit at the other end of the link can be managed on its local network, the following procedure should be adopted: If there is no wireless activity then the configuration should be checked. It is essential that the following items are correct: x Check for Alarm conditions on Home page x Check that the software at each end of the link is the same version x Check that the Target Mac address has not been mis-configured at each end of the link x Check Range x Check Tx Power x Check License keys to ensure that both units are the same product variant x Check Master/Slave status for each unit and ensure that one unit is Master and the other unit is slave x Check that the link has not been further obscured or the ODU misaligned x Check the DFS page at each end of the link and establish that there is a quiet wireless channel to use. If there are no faults found in the configuration and there is absolutely no wireless signal, retry the installation procedure. If this does not work then the ODU may be faulty. 11.2.2 Some Activity If there is some activity but the link is unreliable or does not achieve the data rates required then: x Check that the interference has not increased using the i-DFS measurements x If a quieter channel is available check that it is not barred x Check that the path loss is low enough for the communication rates required x Check that the ODU has not become misaligned
12 Wind Loading 23212 Wind Loading 12.1 GeneralAntennas and electronic equipment mounted on towers or pole mounted on buildings will subject the mounting structure to significant lateral forces when there is appreciable wind. Antennas are normally specified by the amount of force (in pounds) for specific wind strengths. The magnitude of the force depends on both the wind strength and size of the antenna. 12.2 Calculation of Lateral Force The 600 Series bridge with or without the integral antenna is essentially a flat structure and so the magnitude of the lateral force can be estimated from: Force (in pounds) = 0.0042 . A . v2 Where A is the surface area in square feet and v is the wind speed in miles per hour. The lateral force produced by a single 600 Series bridge (integrated or connectorized model) at different wind speeds is shown in Table 39 and Table 40. Table 39 - Lateral Force – Imperial Lateral Force (Pound) at wind speed (mph) Largest Surface Area (sq ft) 80 100 120 140 150PTP 600 Series Bridge - Integrated 1.36 36.6 57.1 82.3 146.2 228.5 PTP 600 Series Connectorized 1.00 26.9 42 60.5 107.5 168.0 Table 40 - Lateral Force – Metric Lateral Force (kg) at wind speed (m/s) Largest Surface Area (sq m) 30 40 50 60 70PTP 600 Series Bridge - Integrated 0.130 12 22 34 49 66 PTP 600 Series- Connectorized 0.093 9 16 24 35 48
12 Wind Loading 233NOTE: When the connectorized version of 600 Series bridge is used with external antennas, the figures from the antenna manufacturer for lateral force should be included to calculate to total loading on the mounting structure. 12.3 Capabilities of the PTP 600 Series Bridges The structure and mounting brackets of the PTP Series systems are capable of withstanding wind speeds up to 151mph (242 kph). The installer should ensure that the structure to which the 600 Series Bridge is fixed to is also capable of withstanding the prevalent wind speeds and loads. 12.4 Wind Speed Statistics Installers are recommended to contact the national meteorological office for the country concerned to identify the likely wind speeds prevalent at the proposed location. This will enable the installer to estimate the total wind loading on the support structures. Examples of the sort of statistics that are available are: USA - Reported Fastest Single Wind Velocities for Selected U.S. Cities (Source: National Weather Service). City, State Wind Velocity (mph)Bismarck, North Dakota 72 Buffalo, New York 91 Chicago, Illinois 87 Hatteras, North Carolina 110 Miami, Florida 132 New York, New York 99 Pensacola, Florida 114 UK Meteorological Office, www.meto.gov.uk Peak wind speed contour maps can be found as Fig 3a/3b at: http://www.meto.gov.uk/education/historic/1987.html
13 Connectorized PTP 600 Series Bridge 23413 Connectorized PTP 600 Series Bridge 13.1 ScopeThis section details the changes and additional features relevant to the connectorized version of the PTP 600 Series products.. 13.2 Product Description 13.2.1 Hardware The Connectorized PTP 600 Series Bridge is a variant designed to provide the system integrator and installer with the ability to provide extra capability to cope with very difficult radio links compared to the PTP 600 Series Integrated model. The variant allows the use of a variety of externally mounted antennas, either Flat Plate or Dish, which have higher gains than provided by the integrated antenna that is normally used. Figure 132 – Connectorized 600 Series Bridge Outdoor Unit 13.2.2 AntennaThe antenna choices for the Connectorized PTP 58600 and 54600 are described in 13.6.2 “Antenna Choices”.
13 Connectorized PTP 600 Series Bridge 23513.3 Software/Features This section only describes the areas where functionality is modified for the connectorized variant. For details of the functionality that is common to the integrated and connectorized variants, see Section 8 “Web Page Reference”. 13.3.1 Status Page The link loss calculation presented on the Status Page of the management interface has to be modified to allow for the increased antenna gains at each end of the link. The manufacturing process of the Connectorized 600 Series Bridge configures the standard hardware of the unit for use with external antennas. The installer is prompted, as part of the installation process, to enter the gain of the external antenna(s) and cable losses at each end of the link. Peer-to-peer messaging is used to pass the effective antenna gain to each end of the link so that the link loss calculations can be correctly computed. Figure 133 - Connectorized 600 Series bridge Status Page
13 Connectorized PTP 600 Series Bridge 23613.3.2 Configuration Pages The Configuration web page for the connectorized variant is shown in Figure 134. The parameters Antenna Gain, Cable Loss and EIRP are specific to the connectorized variant. Figure 134 - Connectorized 600 Series bridge ‘System Configuration’ Page
13 Connectorized PTP 600 Series Bridge 23713.3.3 Installation Pages The installer is prompted to enter the Antenna Gain and Cable Loss (Connectorized PTP 600 Series Bridge to antenna) at each end of the link. The Installation Pages for the connectorized version are shown as Figure 135 to Figure 137. Figure 135 - Connectorized PTP 600 Series Bridge ‘Installation Wizard’ Page Antenna Gain: Gain of the antenna you are connecting to the unit, see Section 13.6.2 “Antenna Choices”. Cable Loss: Loss in the cable between the ODU and the antenna. NOTE: In the event that there is a significant difference in length of the antenna cables for the two antenna ports, then the average value should be entered.
13 Connectorized PTP 600 Series Bridge 238Spectrum Management Control: Is used to configure the 600 Series Bridge Spectrum Management features, see Section 8.3.7 “Spectrum Management” for more details. iDFS is the abbreviation for intelligent Dynamic Frequency Selection, which continually monitors the spectrum looking for the channel with the lowest level of on channel and co-channel interference. Fixed frequency mode allows the installer to fix the Transmit and receive frequencies on the units. The frequencies may be configured symmetrically or asymmetrically. Figure 136 - Connectorized 600 Series bridge ‘Confirm Installation’ Page
13 Connectorized PTP 600 Series Bridge 239EIRP: The Confirm Installation Page displays the EIRP (Effective Isotropic Radiated Power), which describes the strength of the radio signal leaving the wireless unit. This allows the operator to verify that their link configuration (Max Transmit Power, Antenna Gain and Cable Loss) do not cause the link to exceed any applicable regulatory limit. Figure 137 - Connectorized 600 Series bridge ‘Disarm Installation’ Page
13 Connectorized PTP 600 Series Bridge 24013.4 Deployment Considerations The majority of radio links can be successfully deployed with the 600 Series. It should only be necessary to use external antennas where the LINKPlanner indicates marginal performance for a specific link – for example when the link is heavily obscured by dense woodland on an NLOS link or extremely long LOS links (>80km or >50 miles) over water. The external antennas can be either dual-polarization (as the integrated antenna) or two single polarized antennas can be used in a spatially diverse configuration. It is expected that the dual-polarization antennas would normally be used to simplify the installation process; spatially diverse antennas may provide additional fade margin on very long LOS links where there is evidence of correlation of the fading characteristics on Vertical and Horizontal polarizations. 13.5 Link Budget An estimate of the link budget for a specific application can be obtained by using the Motorola Systems link estimation tools. For more information see the Motorola web site. 13.6 Regulatory Issues with Connectorized Units Installations must conform to any applicable local regulations for the Equivalent Isotropic Radiated Power (EIRP). Ensuring compliance becomes more complex when the connectorized unit is used with external antennas which may be locally sourced. With higher gain external antennas fitted, the Maximum Transmit power may need to be reduced for operation in specific countries. In some regions, operation of the PTP 600 products is constrained by EIRP limits. For more information on these limits, see Section 5.2 “Licenses and Region Codes”. When operating with external antennas, the installer/operator has to set the maximum transmit power to ensure that the EIRP limit is not exceeded. Use this formula: Maximum Transmit Power Allowed = EIRP Limit – Antenna Gain + Cable Losses Set the power to the 1dB value lower than the actual value calculated.
13 Connectorized PTP 600 Series Bridge 24113.6.1 Cable Losses (FCC Regions Only) The FCC approval for the product is based on tests with a cable loss between the units of not less than 1.2dB at 5.8GHz. The use of lower cable losses would result in the installation being outside the FCC rules. As an indication, 1.2dB of cable loss corresponds to the following cable lengths excluding connector losses (source: Times Microwave). Table 41 - Cable Losses per Length Length for 1.2dB Cable Loss at 5.8GHz Cable(ft) (m) LMR100 1.9 0.6 LMR200 4.6 1.4 LMR300 7.25 2.2 LMR400 11.1 3.4 LMR600 16.5 5.0 13.6.2 Antenna Choices In non-FCC regions, antenna choice is not restricted, but any region specific EIRP limit must be obeyed by reducing the maximum Transmit power, see Section 5.2 “Licenses and Region Codes”. In FCC regions, antenna choice is restricted as described in Section 13.6.3 “FCC Antenna Restrictions on the PTP 58600” and Section 13.6.4 “FCC Antenna Restrictions on the PTP 54600”. The maximum permitted antenna gain depends upon product variant and channel bandwidth as follows: x PTP 49600: 26 dBi x PTP 58600: 37.7 dBi x PTP 54600 at channel bandwidth 30, 15 or 10 MHz: 34.9 dBi x PTP 54600 at channel bandwidth 5 MHz: 33.4dBi
13 Connectorized PTP 600 Series Bridge 24213.6.3 FCC Antenna Restrictions on the PTP 58600 In FCC regions, external antennas from the list in Table 42 can be used with the Connectorized version of the PTP 600 Series Bridge. These are approved by the FCC for use with the product and are constrained by the following limit for Single/Dual Polarization Parabolic Dish Antennas: up to 37.7 dBi per polarization or antenna. In FCC regions when using external antennas, cable loss between the connectorized version of the PTP 600 Series Bridge and the antenna ports must not be less than 1.2 dB. CAUTION: Antennas not included in this table, or those having a gain greater than the specified maximum, are strictly prohibited for use with the PTP 58600. The required antenna impedance is 50 ohms. Table 42 - Allowed Antennas for Deployment in USA/Canada – 5.8 GHz Manufacturer Antenna Type Gain(dBi) FlatPlateParabolicDishAndrew Andrew 1-foot Flat Panel, FPA5250D12-N (23.6dBi) 23.6 Y Andrew Andrew 2-foot Flat Panel, FPA5250D24-N (28dBi) 28 Y Gabriel Gabriel 1-foot Flat Panel, DFPD1-52 (23.5dBi) 23.5 Y Gabriel Gabriel 2-foot Flat Panel, DFPD2-52 (28dBi) 28 Y MTI MTI 17 inch Diamond Flat Panel, MT-485009 (23dBi) 23 Y MTI MTI 15 inch Dual-Pol Flat Panel, MT-485025/NVH (23dBi) 23 Y MTI MTI 2 ft Directional Flat Panel, MT-20004 (28dBi) 28 Y MTI MTI 2 ft Flat Panel, MT-486001 (28dBi) 28 Y RFS RFS 1-foot Flat Panel, MA0528-23AN (23dBi) 23 Y RFS RFS 2-foot Flat Panel, MA0528-28AN (28dBi) 28 Y Telectronics Teletronics 2-foot Flat Plate Antenna, ANT-P5828 (28dBi) 28 Y Andrew Andrew 2-foot Parabolic, P2F-52 (29.4dBi) 29.4 Y Andrew Andrew 2-foot Dual-Pol Parabolic, PX2F-52 (29.4dBi) 29.4 Y
13 Connectorized PTP 600 Series Bridge 243Manufacturer Antenna Type Gain(dBi) FlatPlateParabolicDishAndrew Andrew 3-foot Parabolic, P3F-52 (33.4dBi) 33.4 Y Andrew Andrew 3-foot Dual-Pol Parabolic, PX3F-52 (33.4dBi) 33.4 Y Andrew Andrew 4-foot Parabolic, P4F-52 (34.9dBi) 34.9 Y Andrew Andrew 4-foot Dual-Pol Parabolic, PX4F-52 (34.9dBi) 34.9 Y Andrew Andrew 6-foot Parabolic, P6F-52 (37.6dBi) 37.6 Y Andrew Andrew 6-foot Dual-Pol Parabolic, PX6F-52 (37.6dBi) 37.6 Y Gabriel Gabriel 2-foot High Performance QuickFire Parabolic, HQF2-52-N 28.2 Y Gabriel Gabriel 4-foot High Performance QuickFire Parabolic, HQF4-52-N 34.4 Y Gabriel Gabriel 6-foot High Performance QuickFire Parabolic, HQF6-52-N 37.4 Y Gabriel Gabriel 2-foot High Performance Dual QuickFire Parabolic, HQFD2-52-N 28.1 Y Gabriel Gabriel 4-foot High Performance Dual QuickFire Parabolic, HQFD4-52-N 34.3 Y Gabriel Gabriel 6-foot High Performance Dual QuickFire Parabolic, HQFD6-52-N 37.3 Y Gabriel Gabriel 2-foot Standard QuickFire Parabolic, QF2-52-N 28.5 Y Gabriel Gabriel 2-foot Standard QuickFire Parabolic, QF2-52-N-RK 28.5 Y Gabriel Gabriel 2.5-foot Standard QuickFire Parabolic, QF2.5-52-N 31.2 Y Gabriel Gabriel 4-foot Standard QuickFire Parabolic, QF4-52-N 34.8 Y Gabriel Gabriel 4-foot Standard QuickFire Parabolic, QF4-52-N-RK 34.8 Y Gabriel Gabriel 6-foot Standard QuickFire Parabolic, QF6-52-N 37.7 Y
13 Connectorized PTP 600 Series Bridge 244Manufacturer Antenna Type Gain(dBi) FlatPlateParabolicDishGabriel Gabriel 2-foot Standard Dual QuickFire Parabolic, QFD2-52-N 28.4 Y Gabriel Gabriel 2.5-foot Standard Dual QuickFire Parabolic, QFD2.5-52-N 31.1 Y Gabriel Gabriel 2-foot Standard Dual QuickFire Parabolic, QFD2-52-N-RK 28.4 Y Gabriel Gabriel 4-foot Standard Dual QuickFire Parabolic, QFD4-52-N 34.7 Y Gabriel Gabriel 4-foot Standard Dual QuickFire Parabolic, QFD4-52-N-RK 34.7 Y Gabriel Gabriel 6-foot Standard Dual QuickFire Parabolic, QFD6-52-N 37.7 Y RadioWaves Radio Waves 2-foot Dual-Pol Parabolic, SPD2-5.2 (28.1dBi) 28.1 Y RadioWaves Radio Waves 2-foot Parabolic, SP2-5.2 (29.0dBi) 29 Y RadioWaves Radio Waves 3-foot Dual-Pol Parabolic, SPD3-5.2 (31.1dBi) 31.1 Y RadioWaves Radio Waves 3-foot Parabolic, SP3-5.2 (31.4dBi) 31.4 Y RadioWaves Radio Waves 4-foot Dual-Pol Parabolic, SPD4-5.2 (34.4dBi) 34.4 Y RadioWaves Radio Waves 4-foot Parabolic, SP4-5.2 (34.8dBi) 34.8 Y RadioWaves Radio Waves 6-foot Dual-Pol Parabolic, SPD6-5.2 (37.5dBi) 37.5 Y RadioWaves Radio Waves 6-foot Parabolic, SP6-5.2 (37.7dBi) 37.7 Y RadioWaves Radio Waves 2-foot Parabolic, SP2-2/5 (28.3dBi) 28.3 Y RadioWaves Radio Waves 3-foot Parabolic, SP3-2/5 (31.4dBi) 31.4 Y RadioWaves Radio Waves 4-foot Parabolic, SP4-2/5 (34.6dBi) 34.6 Y RadioWaves Radio Waves 6-foot Parabolic, SP6-2/5 (37.7dBi) 37.7 Y RFS RFS 2-foot Parabolic, SPF2-52AN or SPFX2-52AN (27.9dBi) 27.9 Y RFS RFS 3-foot Parabolic, SPF3-52AN or SPFX3-52AN(31.4dBi) 31.4 Y
13 Connectorized PTP 600 Series Bridge 245Manufacturer Antenna Type Gain(dBi) FlatPlateParabolicDishRFS RFS 4-foot Parabolic, SPF4-52AN or SPFX4-52AN(33.9dBi) 33.9 Y RFS RFS 6-foot Parabolic, SPF6-52AN or SPFX6-52AN (37.4dBi) 37.4 Y RFS RFS 2-foot HP Parabolic, SDF2-52AN or SDFX2-52AN (31.4dBi) 31.4 Y RFS RFS 4-foot HP Parabolic, SDF4-52AN or SDFX4-52AN (33.9dBi) 33.9 Y RFS RFS 6-foot HP Parabolic, SDF6-52AN or SDFX6-52AN (37.4dBi) 37.4 Y StellaDoradus StellaDoradus 45 inch Parabolic Antenna, 58PSD113 33.8 Y
13 Connectorized PTP 600 Series Bridge 246 13.6.4 FCC Antenna Restrictions on the PTP 54600 In FCC regions, external antennas from the list in Table 43 can be used with the Connectorized version of the PTP 54600. These are approved by the FCC for use with the product and are constrained by the following limit for Single/Dual Polarization Parabolic Dish Antennas: up to 34.9 dBi (33.4 dBi for 5 MHz bandwidth) per polarization or antenna. However, the Maximum Transmit Power must be reduced to avoid exceeding the EIRP limits. In FCC regions when using external antennas, cable loss between the connectorized version of the PTP 600 Series Bridge and the antenna ports must not be less than 1.2 dB. CAUTION: Antennas not included in this table, or those having a gain greater than the specified maximum, are strictly prohibited for use with the PTP 54600. The required antenna impedance is 50 ohms. Table 43 - Allowed Antennas for Deployment in USA/Canada – 5.4 GHz Manufacturer Antenna Type Gain(dBi) ParabolicDishAndrew Andrew 2-foot Parabolic, P2F-52 (29.4dBi) 29.4 Y Andrew Andrew 2-foot Dual-Pol Parabolic, PX2F-52 (29.4dBi) 29.4 Y Andrew Andrew 3-foot Parabolic, P3F-52 (33.4dBi) 33.4 Y Andrew Andrew 3-foot Dual-Pol Parabolic, PX3F-52 (33.4dBi) 33.4 Y Andrew Andrew 4-foot Parabolic, P4F-52 (34.9dBi) 34.9 Y Andrew Andrew 4-foot Dual-Pol Parabolic, PX4F-52 (34.9dBi) 34.9 Y Gabriel Gabriel 2-foot High Performance QuickFire Parabolic, HQF2-52-N 28.2 Y Gabriel Gabriel 4-foot High Performance QuickFire Parabolic, HQF4-52-N 34.4 Y Gabriel Gabriel 2-foot High Performance Dual QuickFire Parabolic, HQFD2-52-N 28.1 Y Gabriel Gabriel 4-foot High Performance Dual QuickFire Parabolic, HQFD4-52-N 34.3 Y Gabriel Gabriel 2-foot Standard QuickFire Parabolic, QF2-52-N 28.5 Y
13 Connectorized PTP 600 Series Bridge 247Manufacturer Antenna Type Gain(dBi) ParabolicDishGabriel Gabriel 2-foot Standard QuickFire Parabolic, QF2-52-N-RK 28.5 Y Gabriel Gabriel 2.5-foot Standard QuickFire Parabolic, QF2.5-52-N 31.2 Y Gabriel Gabriel 4-foot Standard QuickFire Parabolic, QF4-52-N 34.8 Y Gabriel Gabriel 4-foot Standard QuickFire Parabolic, QF4-52-N-RK 34.8 Y Gabriel Gabriel 2-foot Standard Dual QuickFire Parabolic, QFD2-52-N 28.4 Y Gabriel Gabriel 2.5-foot Standard Dual QuickFire Parabolic, QFD2.5-52-N 31.1 Y Gabriel Gabriel 2-foot Standard Dual QuickFire Parabolic, QFD2-52-N-RK 28.4 Y Gabriel Gabriel 4-foot Standard Dual QuickFire Parabolic, QFD4-52-N 34.7 Y Gabriel Gabriel 4-foot Standard Dual QuickFire Parabolic, QFD4-52-N-RK 34.7 Y RadioWaves Radio Waves 2-foot Dual-Pol Parabolic, SPD2-5.2 (28.1dBi) 28.1 Y RadioWaves Radio Waves 2-foot Parabolic, SP2-5.2 (29.0dBi) 29 Y RadioWaves Radio Waves 3-foot Dual-Pol Parabolic, SPD3-5.2 (31.1dBi) 31.1 Y RadioWaves Radio Waves 3-foot Parabolic, SP3-5.2 (31.4dBi) 31.4 Y RadioWaves Radio Waves 4-foot Dual-Pol Parabolic, SPD4-5.2 (34.4dBi) 34.4 Y RadioWaves Radio Waves 4-foot Parabolic, SP4-5.2 (34.8dBi) 34.8 Y RadioWaves Radio Waves 2-foot Parabolic, SP2-2/5 (28.3dBi) 28.3 Y RadioWaves Radio Waves 3-foot Parabolic, SP3-2/5 (31.4dBi) 31.4 Y RadioWaves Radio Waves 4-foot Parabolic, SP4-2/5 (34.6dBi) 34.6 Y RFS RFS 2-foot Parabolic, SPF2-52AN or SPFX2-52AN (27.9dBi) 27.9 Y
13 Connectorized PTP 600 Series Bridge 248Manufacturer Antenna Type Gain(dBi) ParabolicDishRFS RFS 3-foot Parabolic, SPF3-52AN or SPFX3-52AN(31.4dBi) 31.4 Y RFS RFS 4-foot Parabolic, SPF4-52AN or SPFX4-52AN(33.9dBi) 33.9 Y RFS RFS 2-foot HP Parabolic, SDF2-52AN or SDFX2-52AN (31.4dBi) 31.4 Y RFS RFS 4-foot HP Parabolic, SDF4-52AN or SDFX4-52AN (33.9dBi) 33.9 Y
13 Connectorized PTP 600 Series Bridge 24913.7 Installation The section covers the generic installation instructions for the Connectorized versions of the PTP 600 Series point-to-point wireless Ethernet bridges. The actual installation procedure will depend on antenna choice, cable choice, required antenna separation etc. 13.7.1 Antenna Choice Section 13.6.3 “FCC Antenna Restrictions on the PTP 58600” and Section 13.6.4 “FCC Antenna Restrictions on the PTP 54600” show a wide variety of antennas that can be used with the Connectorized PTP 600 Series bridge. The main selection criteria will be the required antenna gain. The secondary criteria should be the ease of mounting and alignment. For example the Radio Waves Parabolic dishes are supplied with a mount that allows adjustment for alignment independent of the actual antenna mounting. This type of antenna is much easier to align than those that have to be rotated around the mounting pole for alignment. 13.7.2 Cables and Connectors Cables should be selected using the above criteria. However it should be noted that a cable of a type similar to LMR400 is a lot more difficult to handle and route than a cable of a type similar to LMR100. Motorola recommends the use of weatherproof connectors -- preferably, ones that come supplied with adhesive lined heat shrink sleeve that is fitted over the cable/connector interface. The connectors required at the Connectorized 600 Series bridge end of the antenna cables are N-Type Male. The connectors required at the antenna end of the antenna cables is dependant on the antenna type chosen. 13.7.3 ToolsThe tools required for mounting a Connectorized 600 Series bridge unit are the same as those required for an Integrated 600 Series bridge detailed in Section 7.3 “Tools Required”. The tools required for mounting the antennas are specific to the antenna chosen. The installer should refer to the antenna manufacturer’s instructions.
13 Connectorized PTP 600 Series Bridge 25013.7.4 Miscellaneous supplies The following miscellaneous supplies will be required: x Cable ties, cable cleats – for securing cables x Self-amalgamating tape – to weatherproof the RF connectors x PVC tape – for additional protection of the RF connectors and securing cables 13.7.5 Mounting the Connectorized 600 Series Bridge A Connectorized 600 Series bridge is shipped with the same bracket as supplied with an Integrated unit. Details on the use of this bracket can be found in Section 3.3.7 “Mounting Brackets”. The 600 Series Bridge should be mounted in a position that gives it maximum protection from the elements, but still allows easy access for making off the various connections and applying the recommended weatherproofing. When using dual polar antennas the Connectorized 600 Series bridge should be mounted in such a position as to minimize the cable length, keeping losses to a minimum (taking into account the minimum cable lengths required by the FCC regulations, see Section 13.6.3 “FCC Antenna Restrictions on the PTP 58600”. When using separate antennas the Connectorized 600 Series Bridge should be mounted in such a position as to minimize both cable runs between the unit and the antennas. It is not necessary to mount the Connectorized 600 Series Bridge at the mid point between the antennas. 13.7.6 Mounting the antennas The Antennas should be mounted according to the manufacturer’s instructions. Actual antenna position will depend on the available mounting positions and link requirements. It may be necessary to mount the antennas 20m apart or at a certain distance from the ground to get the desired results.
13 Connectorized PTP 600 Series Bridge 25113.7.7 Alignment Process When aligning antennas deployed with a Connectorized 600 Series bridge unit it may not be possible to hear the alignment tone emanating from the unit. In this case it may be necessary for a second installer to assist in the operation. Alternatively, it may be possible to extend the tube on the supplied stethoscope to give a longer reach. Recommendation: Fine antenna alignment can sometimes be achieved by tightening and loosening the bolts on either side of the antenna mounting bracket, rather than trying to turn the whole bracket on the mounting pole. 13.7.8 Aligning Dual Polar Antennas The process for aligning a dual polar antenna is the same as aligning an Integrated unit with an integrated antenna. This procedure is detailed in Section 7.7.11 “Aligning the PTP 600 Series Bridge ODUs”. 13.7.9 Aligning Separate Antennas When using separate antennas to achieve spatial diversity, one should be mounted with Horizontal polarization and the other with Vertical polarization. The following steps should be followed: Step 1: Mount the Antennas Step 2: Mount the connectorized version of the PTP 600 Series Bridge unit Step 3: Route and make off the ends of the Antenna cables Step 4: Connect the antenna cables at the antennas Step 5: Connect one of the antenna cables at the Connectorized version of the 600 Series bridge unit. Step 6: Connect the Connectorized 600 Series Bridge ODU to PIDU Plus cable and configure the unit as described in Section 7.7 “Connecting Up”. Step 7: Align the connected antenna using the tones as described in Section 7.7.11 “Aligning the PTP 600 Series Bridge ODUs”. Step 8: Connect the other antenna to the Connectorized 600 Series bridge. Step 9: Disconnect the cable to the already aligned antenna.
13 Connectorized PTP 600 Series Bridge 252Step 10: Align the second antenna using the tones as described in Section 7.7.11 “Aligning the PTP 600 Series Bridge ODUs”. Step 11: Re-connect the second antenna to the Connectorized 600 Series bridge (Note: you will notice the tone pitch increase as you re-connect the second antenna due to the additional received signal). Step 12: Use the relevant status web pages to check that you are getting the results you expect from your link planning. Step 13: Complete the installation as detailed below. 13.7.10 Completing the Installation The installation should be completed by checking all mounting nuts bolts and screws, securing all cables and weatherproofing the installation. CAUTION: Finally tightening the antenna mountings may cause the antenna alignment to be altered, due to distortion in the mounting bracket caused by action of tightening. It is recommended that the installation tone be left turned on (armed) during this process so that any movement can be noticed and counteracted by tightening the other side of the bracket. 13.7.11 Antenna Cable Fixing Cables should be secured in place using cable ties, cleats or PVC tape. Care should be taken to ensure that no undue strain is placed on the connectors on both the Connectorized 600 Series bridge and the Antennas and also to ensure that the cables do not flap in the wind. Flapping cables are prone to damage and induce unwanted vibrations in the mast to which the units are attached.
13 Connectorized PTP 600 Series Bridge 25313.7.12 Antenna Connection Weatherproofing Where a cable connects to an antenna or unit from above, a drip loop should be left to ensure that water is not constantly channeled towards the connector. Figure 138 - Forming a Drip Loop All joints should be weatherproofed using self-amalgamating tape. It is recommended that a layer of PVC tape be placed over the self-amalgamating tape to protect the joint while the self-amalgamating tape cures and gives additional protection. Figure 139 shows this diagrammatically for the 600 Series bridge end of the antenna cables. If the antenna manufacturer has not supplied guidance on this matter, the same technique should be employed at the antenna end of the cable. Figure 139 - Weatherproofing the Antenna Connections
13 Connectorized PTP 600 Series Bridge 25413.8 Additional Lightning Protection The following guidelines should be applied in addition to those described in Section 10 ”Lightning Protection”. 13.8.1 ODU Mounted Outdoors Where the ODU is mounted outdoors and is mounted some distance from the antenna, it is advisable to add additional grounding by utilizing Andrew Assemblies (such as Andrew Type 223158 www.andrew.com) as shown in Figure 140. Figure 140- Additional Grounding When Using Connectorized Units
13 Connectorized PTP 600 Series Bridge 25513.8.2 ODU Mounted Indoors Where the ODU is mounted indoors, lightning arrestors should be deployed where the antenna cables enter the building as shown in Figure 141. Figure 141 - Lightning Arrestor Mounting The lighting arrestors should be ground bonded to the building ground at the point of entry. Motorola recommends Polyphaser LSXL-ME or LSXL lighting arrestors. These should be assembled as show in Figure 142. Figure 142 - Polyphaser Assembly
14 TDD Synchronization Configuration and Installation Guide 25614 TDD Synchronization Configuration and Installation Guide 14.1 IntroductionWhen planning a network of links, a key consideration is the interference that exists between the links. TDD synchronization is a feature which eliminates two specific interference mechanisms, namely interference between Master and Master and interference between Slave and Slave. One example which highlights the need for TDD synchronization is the case where a number of links are required from a single mast. Without TDD synchronization, high levels of interference will occur between the units on the mast due to their close proximity. By enabling TDD synchronization, interference between these units is eliminated if all are of the same type. The recommendation is for all units on a mast to be configured as Masters. The maximum number of links on a mast depends on the customer requirements such as required throughput, link availability, available spectrum, maximum EIRP, bandwidth, channel separation and the longest link. However, in some cases, it may even be possible to re-use radio channels on the same mast which would not be possible without TDD synchronization. In summary, by eliminating interference between units of a like type, TDD synchronization increases network capacity by increasing frequency re-use and increasing the density of links across the network. This section will cover the two steps required to enable TDD synchronization: x Physical installation of the GPS Synchronisation Unit. This will include wiring diagrams, illustrations showing the placement of the GPS box and the recommended components for installation. x The latter will describe the step by step configuration process using the Web interface.
14 TDD Synchronization Configuration and Installation Guide 25714.1.1 Installing the Recommended GPS Synchronization Kit The recommended GPS Sync installation kit includes the following: x GPS Sync Unit from MemoryLink (see Figure 143), with three attached terminated Ethernet and Sync cables and cable glands (2) which connect directly to a PTP 600 Series ODU. x Mounting bracket and mounting bracket bolts x Outdoor rated UV resistant cable tie x GPS Sync Unit User Manual. In addition to the hardware mentioned above, it is recommended to have an appropriate lightning protection (PTP LPU as described in Section 15.6 “Lightning Protection and E1/T1”). NOTE: Refer to GPS Sync Unit User manual for details on the lengths of cables used to connect the GPS Sync Unit to the ODU and PTP LPU. Figure 143 - GPS Synchronization Unit
14 TDD Synchronization Configuration and Installation Guide 258Figure 144 shows the inside of the GPS Sync Unit and Figure 145 is a diagram that shows how to connect the GPS Sync Unit to the ODU and the Lightning protection unit. Figure 144 - GPS Synchronization Unit Connections
14 TDD Synchronization Configuration and Installation Guide 259 Figure 145 - TDD Sync - PTP600 Deployment Diagram NOTE: Installation details of the GPS Sync Unit are described in the GPS Sync Unit User Manual. Figure 146 shows an example of mast installation using lightning protection and a GPS Sync Unit.
14 TDD Synchronization Configuration and Installation Guide 260 Figure 146- GPS Synchronization Unit Complete Installation
14 TDD Synchronization Configuration and Installation Guide 26114.2 TDD Synchronization Configuration TDD synchronization is enabled and configured using the install wizard during the installation process of the link. TDD synchronisation is not available in regions where radar avoidance is enabled. 14.2.1 TDD Synchronization Enable Figure 147 shows how to enable TDD Synchronization. Figure 147 - Enabling TDD Synchronization Feature When TDD Synchronization is enabled, note that: x Ranging Mode and Target Range are disabled on the wireless configuration page. x Link Symmetry is forced to ‘1:1’ operation only. x Spectrum Management Control is forced to ‘Fixed Frequency’ operation only.
14 TDD Synchronization Configuration and Installation Guide 26214.2.2 TDD Synchronization Configuration - Standard Mode When TDD Synchronization is enabled, there is an extra installation screen (“TDD Synchronization”) as shown in Figure 148. Figure 148 - Configuring TDD Synchronization – Screen 1 The TDD Synchronization screen provides the following controls: Expert Mode: Select “Yes” to use “Expert Mode”. This is an option recommended only for experienced network and cell planners and is outside the scope of this document (see Figure 150 for parameters required to configure in this mode). If “Expert Mode” is not selected, then the user is required to enter some basic information to allow the software to calculate the best values for Frame Duration and Burst Duration. Longest Link in Network: Default value is 100 kms (60 miles). It is the distance of the longest link in the network (maximum is 200 kms or 120 miles).
14 TDD Synchronization Configuration and Installation Guide 263Bandwidths in Network: It is very likely that there will be several different channel bandwidths in a given network. Table 44 gives a list of bandwidth combinations that permit synchronization without gross loss of efficiency. Depending on the channel bandwidth size, only subsets of Table 44 will be shown in the configuration wizard screen. Table 44 - Common Burst Durations Bandwidth Combination(MHz) 30 30/5 30/10 5/10/30 15/30 15 10/15 5/10 10 5 Collocated Masters: The network needs to be configured differently depending on whether all masters for which interference can potentially occur are collocated or whether interference needs to be considered for masters which are not collocated. Answer “Yes” to this question if master to master interference only occurs between collocated masters, otherwise answer “No”. If “No” is selected, the maximum distance between masters which can potentially interfere is required. This is the subject of the next bullet. Master to Master Range: This is only displayed (see Figure 138.) if the answer to the above question was “No”. In this case, the longest distance over which two masters can interfere must be entered here. Maximum range is 200 km (120 miles). Slave Interfere: Select “No” if there is no potential of a slave interfering with another slave. Select “Yes” if there is potential for one slave to interfere with another slave. If the option “Yes” is selected, then the maximum distance between slaves which can potentially interfere is required. This is the subject of the next bullet. Slave to Slave Range: This is only displayed (see Figure 138.) if the answer to the above question was “Yes”. In this case, the longest distance over which two slaves can interfere must be entered here. Maximum range is 200 km (120 miles).
14 TDD Synchronization Configuration and Installation Guide 264Configure Link Range: Choose “yes” to enter the range of the link in control below: Note that Link Range MUST be less or equal to “Longest Link in Network”. In some networks, throughput can be increased by entering the exact range of each link in the wizard. TDD Holdover Mode: Two values: “Strict” and “Best Effort”. If a PTP 600 master ODU is configured for a TDD Holdover Mode set to “Strict”, then it will not transmit when synchronization is lost. On the other hand, a link configured for TDD Holdover Mode set to “Best Effort” will synchronize when a reference signal is available, but will otherwise use best efforts to operate in unsynchronized fashion. Figure 149 - Configuring TDD Synchronization Feature - Screen 2 CAUTION: the values entered for the controls in Figure 149 MUST be the same for master/slave pairs for all the links in the network, except for the attribute “Range of This Link” which can be entered exactly for better performance.
14 TDD Synchronization Configuration and Installation Guide 26514.2.3 TDD Synchronization Configuration – Expert Mode When “Expert Mode” is selected, the user is required to configure the parameters shown in Figure 150. As mentioned previously, this is outside the scope of this document. However, this mode can be used as informative to ensure that the values of the parameters are the same for all the links in the network. When “Expert Mode” is not selected, the controls in Figure 150 are automatically filled by the software Figure 150 - Configure TDD Synchronisation Expert Mode
14 TDD Synchronization Configuration and Installation Guide 26614.2.4 Confirm Settings and Reboot ODU When all the parameters have been entered, then the user can commit the values to the unit and reboot. Figure 151 shows the list of the installation parameters. Figure 151 - Confirm TDD Synchronization Configuration Parameters Following the reboot and provided the GPS has synchronized, an additional control is displayed in the Status Page as shown in Figure 152 (Sync) or Figure 153 (Not Sync).
14 TDD Synchronization Configuration and Installation Guide 267 Figure 152 - Status Page - TDD Enabled and Synchronized Figure 153 - Status Page - TDD Enabled and Not Synchronized
14 TDD Synchronization Configuration and Installation Guide 26814.2.5 Disarm ODU Following TDD Sync Configuration Figure 154 - Disarm Following TDD Synchronization CAUTION: In a synchronized network, links MUST be configured separately before bringing the whole network up.
15 E1/T1 Installation Guide 26915 E1/T1 Installation Guide 15.1 Preparing the PTP 600 Series Bridge E1/T1 Cable NOTE: The maximum cable length between the ODU and the customers terminating equipment is 200m (656 feet) for E1/T1. The E1/T1 cable should be assembled as described in Section 3.3.5 “Cables and connectors”. This procedure applies to the ODU termination. The above procedure should be repeated for the customer equipment end of the cable when the cable is terminated with a RJ45. Figure 155 - RJ45 Pin Connection (T568B Color Coding)
15 E1/T1 Installation Guide 27015.2 Making the Connection at the ODU Looking at the back of the unit with the cable entry at the bottom, the PTP 600 Series Bridge E1/T1 connection is the first hole on the left (Figure 156) and is labeled E1/T1. Figure 156 - PIDU Plus and E1-T1 Connexion The following procedure describes how connection is made at the ODU. It is often easier to carry out this procedure on the ground or a suitable surface prior to mounting the ODU. Ensure no power is connected to the PIDU Plus.
15 E1/T1 Installation Guide 271Figure 157 - Disconnecting the ODU Step 1: Assemble the cable as described in above Step 2: Insert the RJ45 connector making sure that the locking tab snaps home Step 3: Screw in the body of the weather proofing gland and tighten Step 4: Screw on the clamping nut and tighten Should it be necessary to disconnect the E1/T1 cable at the ODU this can be achieved by removing the weatherproofing gland and depressing the RJ45 locking tab with a small screwdriver as shown in the opposite photograph.
15 E1/T1 Installation Guide 272CAUTION: Do not over tighten the glands as the internal seal and structure may be damaged. See Figure 40 for an example of an over tightened cable gland. 15.3 Routing the Cable After connecting the cable to the ODU it can be routed and secured using standard cable routing and securing techniques. When the cable is in place it can then be cut to the desired length. 15.4 Fitting a Lightning Protection Unit If you have opted to fit a Lightning Protection Unit, it should be installed as described in Section 10 “Lightning Protection”. 15.5 Customer Cable Termination The two channels can be separated by means of a patch panel which may include Baluns for transmission over 75 Ohm co-axial unbalanced lines. Such equipment should conform to the requirements of C.C.I.T.T. G703. An example of a Balun is shown below. It allows the transmit and receive data carried over a 75 Ohm cable to be converted to a balanced form for transmission over a 120 Ohm signal balanced twisted pair. Figure 158 - Example of a Balun
15 E1/T1 Installation Guide 273 Figure 159 - Diagrammatically Showing the E1-T1 Connections
15 E1/T1 Installation Guide 274Figure 160 - Two E1-T1-120 Ohms signal Balanced to PTP600 Interface
15 E1/T1 Installation Guide 27515.6 Lightning Protection and E1/T1 15.6.1 Overview Section 10 “Lightning Protection” contains the requirements for the Motorola PTP 600 Series deployment. For E1/T1, an extra Earthing cable is supplied to connect the other PTP-LPU to the ODU ground. This section details the additional requirements for the deployment of E1/T1. 15.6.2 Recommended Additional Components for E1/T1 Installation. For a description of Zone A and Zone B refer to Section 10 “Lightning Protection”. Table 45 - Protection Requirements Component Zone A Zone B Earth ODU Mandatory Mandatory Screen Cable Mandatory Mandatory Lightning Protection Unit PTP LPU at ODU Mandatory Mandatory Earth Cable at Building Entry Mandatory Mandatory Lightning Protection Unit PTP LPU at Building Entry Mandatory Mandatory Refer to Section 10.4 “LPU Recommended Configurations” to see how the components of PTP 600 sites with E1/T1 are installed and connected. This section also lists the recommended components for each type of installation.
15 E1/T1 Installation Guide 27615.7 Testing the E1/T1 Installation If you have opted to fit a Lightning Protection Unit, it should be tested as described in Section 10.3 “Installation”. Test the telecoms links by performing loopback connections as described in Section 8.3.1.6 “Telecoms Configuration Page”. 15.7.1 Pre-Power Testing Before connecting your E1/T1 source, check the following resistances: Check the cable resistance between pins 3 & 6 (Green/White & Green) and 7 & 8 (Brown/White & Brown). Check against Table 46 column 2. Check the cable resistance between pins 1 & 2 (Orange/White & Orange) and 4 & 5 (Blue & Blue/White). Check against Table 46 column 3. Table 46 - Resistance Table Referenced To the E1/T1 Source CAT-5 Length (Meters) Resistance between pins 3 & 6 and pins 7 & 8 (ohms) Resistance between pins 1 & 2 and pins 4 & 5 (ohms) 0 0.8 1.3 10 2.5 3.0 20 4.2 4.7 30 5.9 6.4 40 7.6 8.2 50 9.3 9.8 60 11.0 11.5 70 12.7 13.2 80 14.4 14.9 90 16.1 18.2 100 17.8 18.3
16 Data Rate Calculations 27716 Data Rate Calculations The data rate capacity of a PTP link is defined as the maximum end-to-end ethernet throughput that it can support. Use the tables and graph in this section to calculate the data rate capacity that can be provided by alternative PTP 600 configurations. It is assumed that ethernet frames are 1500 octet. Data rate capacity is determined by the following factors: x Product variant (PTP 600 Full or Lite) x Link Symmetry x Link Mode Optimization (IP or TDM) x Modulation Mode x Channel Bandwidth x Link Range 16.1 Calculation Procedure and Example 16.1.1 Procedure To calculate the data rate capacity of a PTP 600 link, follow this procedure: 1. Use the tables in Section 16.2 to look up the data throughput capacity rates (Tx, Rx and Both) for the required combination of: o Link Symmetry o Link Mode Optimization o Modulation Mode o Channel Bandwidth 2. The tables in Section 16.2 contain data rates for PTP 600 Full only. If the ODUs are PTP 600 Lite, divide the data rates in Section 16.2 by 2. 3. The tables in Section 16.2 contain data rates for links of zero range. Use the curves in Section 16.3 to look up the Throughput Factor that must be applied to adjust the data rates for the actual range of the link. 4. Multiply the data rates by the Throughput Factor to give the throughput capacity of the link.
16 Data Rate Calculations 278NOTE: There is a small difference between the rates for IP and TDM because there is fragmentation in TDM (for low priority traffic) which causes the throughput to be reduced buy approximately 1% compared to the IP mode. 16.1.2 ExampleSuppose that the link characteristics are: x Product variant = PTP 600 Lite x Link Symmetry = 1:1 x Link Mode Optimization = TDM x Modulation Mode = 64QAM 0.92 Dual x Channel Bandwidth = 10 MHz x Link Range = 60 km Applying the calculation procedure: 1. Use Table 48 to look up the data throughput capacity rates: o Tx = 41.41 Mbits/s o Rx = 41.41 Mbits/s o Both = 82.81 Mbits/s 2. Divide these rates by 2 to give PTP 600 Lite rates: o Tx = 20.70 Mbits/s o Rx = 20.70 Mbits/s o Both = 41.40 Mbits/s 3. Use Figure 171 to look up the Throughput Factor for 1:1, TDM and Link Range 60 km. The factor is 0.86. 4. Multiply the rates from Step 2 by the Throughput Factor from Step 3 to give the throughput capacity of the link: o Tx = 17.80 Mbits/s o Rx = 17.80 Mbits/s o Both = 35.60 Mbits/s
16 Data Rate Calculations 27916.2 Data Throughput Capacity Table 47, Table 48, Table 49, Table 50 and Table 51 show the data throughput rates (Mbits/s) that are achieved when two PTP 600 Full ODUs are linked and the link distance (range) is 0 km. Use the curves in Section 16.3 to adjust these figures to allow for link range. NOTE: When using these tables, be aware of the following points: x PTP 600 Lite data rates are half the PTP 600 Full rates given in this section. x Modulation Mode “256QAM 0.81 dual” is not available in all product variants and channel bandwidths. x Throughput for Link Symmetry 2:1 is the same as that for 1:2, but the Tx and Rx data rates are swapped. x The data rates for Adaptive symmetry apply to the most asymmetric case where the link has significant offered traffic in one direction only. The data rates for Adaptive symmetry with bidirectional offered traffic are the same as those for Link Symmetry = 1:1 with Link Optimization = IP.
16 Data Rate Calculations 280 Table 47 – Data Throughput for PTP 600 Full, Link Symmetry = 1:1, Link Optimization = IP (Mbit/s) 30 MHz 20 MHz and 15 MHz 10 MHz Modulation Mode Tx Rx Both Tx Rx Both Tx Rx Both 256QAM 0.81 dual 150.01 150.01 300.02 75.37 75.37 150.74 50.11 50.11 100.2164QAM 0.92 dual 126.39 126.39 252.78 63.50 63.50 127.01 42.22 42.22 84.4364QAM 0.75 dual 103.28 103.28 206.57 51.89 51.89 103.79 34.50 34.50 69.0016QAM 0.87 dual 80.35 80.35 160.70 40.37 40.37 80.74 26.84 26.84 53.6816QAM 0.63 dual 57.76 57.76 115.52 29.02 29.02 58.04 19.29 19.29 38.59256QAM 0.81 single 75.00 75.00 150.01 37.69 37.69 75.37 25.05 25.05 50.1164QAM 0.92 single 63.19 63.19 126.39 31.75 31.75 63.50 21.11 21.11 42.2164QAM 0.75 single 51.64 51.64 103.28 25.95 25.95 51.89 17.25 17.25 34.5016QAM 0.87 single 40.17 40.17 80.35 20.18 20.18 40.37 13.42 13.42 26.8416QAM 0.63 single 28.88 28.88 57.76 14.51 14.51 29.02 9.65 9.65 19.29QPSK 0.87 single 20.09 20.09 40.17 10.09 10.09 20.18 6.71 6.71 13.42QPSK 0.63 single 14.44 14.44 28.88 7.25 7.25 14.51 4.82 4.82 9.64BPSK 0.63 single 7.22 7.22 14.44 3.63 3.63 7.25 2.41 2.41 4.82 5 MHz Modulation Mode Tx Rx Both 256QAM 0.81 dual 24.22 24.22 48.4364QAM 0.92 dual 20.40 20.40 40.8064QAM 0.75 dual 16.67 16.67 33.3416QAM 0.87 dual 12.97 12.97 25.9416QAM 0.63 dual 9.32 9.32 18.65256QAM 0.81 single 12.11 12.11 24.2164QAM 0.92 single 10.20 10.20 20.4064QAM 0.75 single 8.34 8.34 16.6716QAM 0.87 single 6.48 6.48 12.9716QAM 0.63 single 4.66 4.66 9.32QPSK 0.87 single 3.24 3.24 6.48QPSK 0.63 single 2.33 2.33 4.66BPSK 0.63 single 1.16 1.16 2.33
16 Data Rate Calculations 281 Table 48 – Data Throughput for PTP 600 Full, Link Symmetry = 1:1, Link Optimization = TDM (Mbit/s) 30 MHz 20 MHz and 15 MHz 10 MHz Modulation Mode Tx Rx Both Tx Rx Both Tx Rx Both 256QAM 0.81 dual 140.87 140.87 281.74 72.92 72.92 145.83 49.14 49.14 98.2964QAM 0.92 dual 118.69 118.69 237.38 61.43 61.43 122.87 41.41 41.41 82.8164QAM 0.75 dual 96.99 96.99 193.98 50.20 50.20 100.41 33.84 33.84 67.6716QAM 0.87 dual 75.45 75.45 150.91 39.06 39.06 78.11 26.32 26.32 52.6416QAM 0.63 dual 54.24 54.24 108.48 28.08 28.08 56.15 18.92 18.92 37.84256QAM 0.81 single 70.43 70.43 140.87 36.46 36.46 72.91 24.57 24.57 49.1464QAM 0.92 single 59.34 59.34 118.69 30.72 30.72 61.43 20.70 20.70 41.4064QAM 0.75 single 48.49 48.49 96.99 25.10 25.10 50.20 16.92 16.92 33.8316QAM 0.87 single 37.73 37.73 75.45 19.53 19.53 39.05 13.16 13.16 26.3216QAM 0.63 single 27.12 27.12 54.24 14.04 14.04 28.07 9.46 9.46 18.92QPSK 0.87 single 18.86 18.86 37.72 9.76 9.76 19.52 6.58 6.58 13.16QPSK 0.63 single 13.56 13.56 27.12 7.02 7.02 14.03 4.73 4.73 9.46BPSK 0.63 single 6.78 6.78 13.56 3.51 3.51 7.02 2.36 2.36 4.73 5 MHz Modulation Mode Tx Rx Both 256QAM 0.81 dual 24.22 24.22 48.4364QAM 0.92 dual 20.40 20.40 40.8064QAM 0.75 dual 16.67 16.67 33.3416QAM 0.87 dual 12.97 12.97 25.9416QAM 0.63 dual 9.32 9.32 18.65256QAM 0.81 single 12.11 12.11 24.2164QAM 0.92 single 10.20 10.20 20.4064QAM 0.75 single 8.34 8.34 16.6716QAM 0.87 single 6.48 6.48 12.9716QAM 0.63 single 4.66 4.66 9.32QPSK 0.87 single 3.24 3.24 6.48QPSK 0.63 single 2.33 2.33 4.66BPSK 0.63 single 1.16 1.16 2.33
16 Data Rate Calculations 282 Table 49 – Data Throughput for PTP 600 Full, Link Symmetry = 2:1, Link Optimization = IP (Mbit/s) (This combination is not available with Channel Bandwidth 5 MHz) 30 MHz 20 MHz and 15 MHz 10 MHz Modulation Mode Tx Rx Both Tx Rx Both Tx Rx Both 256QAM 0.81 dual 198.58 99.29 297.88 100.50 50.25 150.74 66.38 33.19 99.5664QAM 0.92 dual 167.31 83.66 250.97 84.67 42.33 127.01 55.92 27.96 83.8864QAM 0.75 dual 136.73 68.36 205.09 69.19 34.59 103.79 45.70 22.85 68.5516QAM 0.87 dual 106.37 53.18 159.55 53.83 26.91 80.74 35.55 17.78 53.3316QAM 0.63 dual 76.47 38.23 114.70 38.70 19.35 58.04 25.56 12.78 38.34256QAM 0.81 single 99.29 49.64 148.94 50.25 25.12 75.37 33.19 16.59 49.7864QAM 0.92 single 83.66 41.83 125.48 42.33 21.17 63.50 27.96 13.98 41.9464QAM 0.75 single 68.36 34.18 102.54 34.59 17.30 51.89 22.85 11.42 34.2716QAM 0.87 single 53.18 26.59 79.77 26.91 13.46 40.37 17.78 8.89 26.6616QAM 0.63 single 38.23 19.11 57.35 19.35 9.67 29.02 12.78 6.39 19.17QPSK 0.87 single 26.59 13.29 39.88 13.46 6.73 20.18 8.89 4.44 13.33QPSK 0.63 single 19.11 9.56 28.67 9.67 4.84 14.51 6.39 3.19 9.58BPSK 0.63 single 9.56 4.78 14.33 4.84 2.42 7.25 3.19 1.60 4.79 Table 50 – Data Throughput for PTP 600 Full, Link Symmetry = 2:1, Link Optimization = TDM (Mbit/s) (This combination is not available with Channel Bandwidth 5 MHz) 30 MHz 20 MHz and 15 MHz 10 MHz Modulation Mode Tx Rx Both Tx Rx Both Tx Rx Both 256QAM 0.81 dual 193.06 96.53 289.58 98.83 49.42 148.25 66.38 33.19 99.5664QAM 0.92 dual 162.66 81.33 243.98 83.27 41.63 124.90 55.92 27.96 83.8864QAM 0.75 dual 132.92 66.46 199.38 68.05 34.02 102.07 45.70 22.85 68.5516QAM 0.87 dual 103.41 51.70 155.11 52.94 26.47 79.40 35.55 17.78 53.3316QAM 0.63 dual 74.34 37.17 111.50 38.05 19.03 57.08 25.56 12.78 38.34256QAM 0.81 single 96.53 48.26 144.79 49.42 24.71 74.12 33.19 16.59 49.7864QAM 0.92 single 81.33 40.66 121.99 41.63 20.82 62.45 27.96 13.98 41.9464QAM 0.75 single 66.46 33.23 99.69 34.02 17.01 51.03 22.85 11.42 34.2716QAM 0.87 single 51.70 25.85 77.55 26.47 13.23 39.70 17.78 8.89 26.6616QAM 0.63 single 37.17 18.58 55.75 19.03 9.51 28.54 12.78 6.39 19.17QPSK 0.87 single 25.85 12.92 38.77 13.23 6.62 19.85 8.89 4.44 13.33QPSK 0.63 single 18.58 9.29 27.87 9.51 4.76 14.27 6.39 3.19 9.58BPSK 0.63 single 9.29 4.64 13.93 4.76 2.38 7.13 3.19 1.60 4.79
16 Data Rate Calculations 283 Table 51 – Data Throughput for PTP 600 Full, Link Symmetry = Adaptive Link Optimization = IP (Mbit/s) (This combination is not available with Channel Bandwidth 5 MHz) 30 MHz 20 MHz and 15 MHz 10 MHz Modulation Mode Tx Rx Both Tx Rx Both Tx Rx Both 256QAM 0.81 dual 236.95 59.23 296.18 112.12 37.37 149.49 66.38 33.19 99.5664QAM 0.92 dual 199.63 49.91 249.54 94.46 31.49 125.95 55.92 27.96 83.8864QAM 0.75 dual 163.14 40.78 203.92 77.19 25.73 102.92 45.70 22.85 68.5516QAM 0.87 dual 126.91 31.73 158.64 60.05 20.02 80.07 35.55 17.78 53.3316QAM 0.63 dual 91.24 22.81 114.04 43.17 14.39 57.56 25.56 12.78 38.34256QAM 0.81 single 118.47 29.62 148.09 56.06 18.68 74.74 33.19 16.59 49.7864QAM 0.92 single 99.82 24.95 124.77 47.23 15.74 62.97 27.96 13.98 41.9464QAM 0.75 single 81.57 20.39 101.96 38.59 12.86 51.46 22.85 11.42 34.2716QAM 0.87 single 63.46 15.86 79.32 30.02 10.01 40.03 17.78 8.89 26.6616QAM 0.63 single 45.62 11.40 57.02 21.58 7.19 28.78 12.78 6.39 19.17QPSK 0.87 single 31.73 7.93 39.66 15.01 5.00 20.01 8.89 4.44 13.33QPSK 0.63 single 22.81 5.70 28.51 10.79 3.60 14.39 6.39 3.19 9.58BPSK 0.63 single 11.40 2.85 14.25 5.39 1.80 7.19 3.19 1.60 4.79
16 Data Rate Calculations 28416.3 Range Adjustment Curves Use these curves to look up the link Range and find the Throughput Factor that must be applied to adjust the 0 km data throughput rates for the required combination of Channel Bandwidth, Link Symmetry, Link Optimization, DFS and Link Range (km). Table 52 – Range Adjustment Characteristics Channel Bandwidth LinkSymmetry LinkOptimisationDFS Range Adjustment Curve See Figure IP A Figure 161 1:1 TDM B Figure 162 IP C Figure 163 2:1 TDM D Figure 164 30 MHz Adaptive IP E Figure 165 IP F Figure 166 1:1 TDM G Figure 167 IP F Figure 166 None H Figure 168 2:1 TDM FCC or ETSI C Figure 163 20 MHz or 15 MHz Adaptive IP I Figure 169 IP J Figure 170 1:1 TDM K Figure 171 IP L Figure 172 2:1 TDM L Figure 172 10 MHz Adaptive IP L Figure 172 5 MHz 1:1 Don’t Care M Figure 173
16 Data Rate Calculations 285Figure 161 – PTP 600 Range Adjustment for Data Rates, Curve A Channel Bandwidth = 30 MHz, Link Symmetry = 1:1, Link Optimization = IP.
16 Data Rate Calculations 286 Figure 162 – PTP 600 Range Adjustment for Data Rates, Curve B Channel Bandwidth = 30 MHz, Link Symmetry = 1:1, Link Optimization = TDM.
16 Data Rate Calculations 287 Figure 163 – PTP 600 Range Adjustment for Data Rates, Curve C Channel Bandwidth = 30 MHz, Link Symmetry = 2:1, Link Optimization = IP. Channel Bandwidth = 20 or 15 MHz, Link Symmetry = 2:1, Link Optimization = TDM, DFS = FCC or ETSI.
16 Data Rate Calculations 288 Figure 164 – PTP 600 Range Adjustment for Data Rates, Curve D Channel Bandwidth = 30 MHz, Link Symmetry = 2:1, Link Optimization = TDM.
16 Data Rate Calculations 289 Figure 165 – PTP 600 Range Adjustment for Data Rates, Curve E Channel Bandwidth = 30 MHz, Link Symmetry = Adaptive, Link Optimization = IP.
16 Data Rate Calculations 290 Figure 166 – PTP 600 Range Adjustment for Data Rates, Curve F Channel Bandwidth = 20 or 15 MHz, Link Symmetry = 1:1 or 2:1, Link Optimization = IP.
16 Data Rate Calculations 291 Figure 167 – PTP 600 Range Adjustment for Data Rates, Curve G Channel Bandwidth = 20 or 15 MHz, Link Symmetry = 1:1, Link Optimization = TDM.
16 Data Rate Calculations 292 Figure 168 – PTP 600 Range Adjustment for Data Rates, Curve H Channel Bandwidth = 20 or 15 MHz, Link Symmetry = 2:1, Link Optimization = TDM, DFS = None.
16 Data Rate Calculations 293 Figure 169 – PTP 600 Range Adjustment for Data Rates, Curve I Channel Bandwidth = 20 or 15 MHz, Link Symmetry = Adaptive, Link Optimization = IP.
16 Data Rate Calculations 294 Figure 170 – PTP 600 Range Adjustment for Data Rates, Curve J Channel Bandwidth = 10 MHz, Link Symmetry = 1:1, Link Optimization = IP.
16 Data Rate Calculations 295 Figure 171 – PTP 600 Range Adjustment for Data Rates, Curve K Channel Bandwidth = 10 MHz, Link Symmetry = 1:1, Link Optimization = TDM.
16 Data Rate Calculations 296 Figure 172 – PTP 600 Range Adjustment for Data Rates, Curve L Channel Bandwidth = 10 MHz, Link Symmetry = 2:1 or Adaptive.
16 Data Rate Calculations 297 Figure 173 – PTP 600 Range Adjustment for Data Rates, Curve M Channel Bandwidth = 5 MHz, Link Symmetry = 1:1.
17 AES Encryption Upgrade 29817 AES Encryption Upgrade The Motorola PTP 600 Series bridges support link encryption using the NIST approved Advanced Encryption Standard, HFIPS-197UTH. This standard specifies AES (Rijndael) as a FIPS-approved symmetric encryption algorithm that may be used by U.S. Government organizations (and others) to protect sensitive information. Link Encryption is not available in the standard PTP 600 Series system. A license key to enable link encryption can be purchased from your Motorola Point-to-Point Distributor or Solutions Provider. AES can be activated on receipt of the activation on the Motorola Systems Support Page. There are two levels of encryption that are available to purchase: x 128-bit x 128 and 256-bit Option 1 allows the user to encrypt all traffic sent over the wireless link using 128-bit encryption. Option 2 allows the user to encrypt traffic using either 128 or 256-bit encryption. The configuration process for both encryption variants is identical except for the selection of algorithm. The following configuration example is for a 256-bit encryption key. 17.1 Configuring Link Encryption After purchasing AES encryption for the PTP 600 Series wireless link, two new license keys will be issued, one for each end of the wireless link. The following configuration process gives a step by step guide to enabling AES link encryption on a PTP 600 Series bridge. 17.1.1 License Keys The first step when configuring link encryption is to enter the new license keys in both 600 Series wireless units. Figure 174 shows the license key data entry screen. This screen can only be accessed by the system administrator. If you do not have access to the PTP 600 Series system administration pages then please contact your designated system administrator.
17 AES Encryption Upgrade 299 Figure 174 – AES Software License Key Data Entry Configuring link encryption will necessitate a 600 Series bridge service outage. Therefore it is recommended that the configuration process be scheduled during an appropriate period of low link utilization. Motorola recommends the following process for entering new license keys and minimizing service outage: 1. Open two browsers, one for each end of the link 2. Navigate to the ‘License Key’ data entry page for each end of the link 3. Enter the license keys and click the ‘Validate license key’ button at each end of the link. This will allow the software to validate the license key prior to the system reset. (DO NOT CLICK ARE YOU SURE POPUP DIALOG)
17 AES Encryption Upgrade 3004. When both license keys have been successfully validated confirm the reboot for both ends of the link. The software is designed to allow five seconds so that a user can command both ends of the link to reset before the wireless link drops. 5. The link will automatically re-establish. 17.1.2 Encryption Mode and Key Entering the license keys only does not initialize AES link encryption. Link encryption can only be enabled via the Configuration or Installation Wizard pages. Motorola recommends that the Configuration page Figure 175 be used to configure AES link encryption. Figure 175 – AES Configuration Data Entry Page
17 AES Encryption Upgrade 301 Motorola recommends the following process for entering AES link encryption configuration: 1. Open two browsers, one for each end of the link 2. Navigate to the ‘Configuration’ data entry page for each end of the link 3. At both ends of the link select the ‘AES (Rijndael)’ Encryption Algorithm required. 4. At both ends of the link enter ether an 128-bit or 256-bit encryption key. Note the key consists of 32/64 case insensitive hexadecimal characters. The same Key must be entered at both ends of the link. Failure to enter the same key will cause the link to fail. 5. Submit configuration on both ends of the link, but do not reboot. 6. Reboot both ends of the link Figure 176. The software is designed to allow five seconds so that a user can command both ends of the link to reboot before the wireless link drops. Figure 176 - Configuration Reboot Screen
17 AES Encryption Upgrade 30217.2 Wireless Link Encryption FAQ 17.2.1 Encryption data entry fields are not available Check that the correct license key has been inserted into the unit. The current license key is displayed on the ‘License Key’ data entry page. 17.2.2 Link fails to bridge packets after enabling link encryption If the wireless link status on the status web page indicates that the link is ‘Searching’, and you can browse to the local end of the link but not to the remote end, then check that the same encryption algorithm and key have been entered at both ends of the link. Failure to enter the same algorithm and key will result in received packets not being decrypted correctly. 17.2.3 Loss of AES following downgrade When downgrading (using Recovery software image 05-01 onwards) to an earlier version of software that does not support AES, the unit will indicate that the region code is invalid. The user will be required to re-install correct software (supplied when AES key was activated) and reboot the unit.
18 Remote Software Upgrade by TFTP 30318 Remote Software Upgrade by TFTP The ODU software can be upgraded remotely using Trivial FTP (TFTP) triggered by SNMP. To perform a remote software upgrade, follow this procedure: 1. Set the following tFTP attributes: tFTPServerIPAddress: The IP address of the TFTP server from which the TFTP software upgrade file Name will be retrieved. For example, to set the TFTP server IP address for unit 10.10.10.10 to 10.10.10.1: snmpset_d.exe -v 2c -c public 10.10.10.10 .iso.3.6.1.4.1.17713.1.9.5.0 a 10.10.10.1tFTPServerPortNumber: This setting is optional. The port number of the TFTP server from which the TFTP software upgrade file name will be retrieved (default=69). tFTPSoftwareUpgradeFileName: The filename of the software upgrade to be loaded from the TFTP server. For example, to set the TFTP software upgrade filename on 10.10.10.10 to "B1095.dld": snmpset_d.exe -v 2c -c public 10.10.10.10 .iso.3.6.1.4.1.17713.1.9.7.0 s B1095.dldtFTPStartSoftwareUpgrade: Write '1' to this attribute to start the TFTP software upgrade process. The attribute will be reset to 0 when the upgrade process has finished. Example: snmpset_d.exe -v 2c -c public 10.10.10.10 .iso.3.6.1.4.1.17713.1.9.8.0 i 1
18 Remote Software Upgrade by TFTP 3042. Monitor the values of the following tFTP attributes: tFTPSoftwareUpgradeStatus: The current status of the TFTP software upgrade process. Values: o idle(0) o uploadinprogress(1) o uploadsuccessfulprogrammingFLASH(2) o upgradesuccessfulreboottorunthenewsoftwareimage(3) o upgradefailed(4). Example: snmpget_d.exe -v 2c -c public 10.10.10.10 .iso.3.6.1.4.1.17713.1.9.9.0 tFTPSoftwareUpgradeStatusText: This describes the status of the TFTP software upgrade process, including any error details. Example: snmpget_d.exe -v 2c -c public 10.10.10.10 .iso.3.6.1.4.1.17713.1.9.10.0 tFTPSoftwareUpgradeStatusAdditionalText: Used if tFTPSoftwareUpgradeStatusText is full and there are more than 255 characters to report. Additional text describing the status of the TFTP software upgrade process, including any error details. Example: snmpget_d.exe -v 2c -c public 10.10.10.10 .iso.3.6.1.4.1.17713.1.9.11.0 3. When the upgrade is complete, reboot the ODU to run the newly loaded software image. See Section 9.4“Reboot”.
19 Legal and Regulatory Notices 30519 Legal and Regulatory Notices 19.1 Important Note on Modifications Intentional or unintentional changes or modifications to the equipment must not be made unless under the express consent of the party responsible for compliance. Any such modifications could void the user’s authority to operate the equipment and will void the manufacturer’s warranty. 19.2 National and Regional Regulatory Notices – PTP 49600 variant The system has been approved under FCC Part 90 and Industry Canada RSS-111 for Public Safety Agency usage. The installer or operator is responsible for obtaining the appropriate site licenses before installing or using the system. FCC IDs and Industry Canada Certification Numbers are listed below: 19.3 National and Regional Regulatory Notices – PTP 59600 variant 19.3.1 Russia This system has been tested for type approval in Russia of fixed link equipment under the heading of BPD TZS 12.     -1--0241  28  2008 .
19 Legal and Regulatory Notices 30619.4 National and Regional Regulatory Notices – PTP 58600 variant 19.4.1 U.S. Federal Communication Commission (FCC) and Industry Canada (IC) Notification This system has achieved Type Approval in various countries around the world. This means that the system has been tested against various local technical regulations and found to comply. The frequency band in which the system operates is ‘license exempt’ and the system is allowed to be used provided it does not cause interference. Further, the licensing authority does not guaranteed protection against interference from other products and installations. This device complies with part 15 of the US FCC Rules and Regulations and with RSS-210 of Industry Canada. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation. In Canada, users should be cautioned to take note that high power radars are allocated as primary users (meaning they have priority) of 5650 – 5850 MHz and these radars could cause interference and/or damage to license-exempt local area networks (LELAN). For the connectorized version of the product and in order to reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the Effective Isotropically Radiated Power (EIRP) is not more than that permitted for successful communication. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the US FCC Rules and with RSS-210 of Industry Canada. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with these instructions, may cause harmful interference to radio communications. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment on and off, the user is encouraged to correct the interference by one or more of the following measures: x Increase the separation between the affected equipment and the unit; x Connect the affected equipment to a power outlet on a different circuit from that which the receiver is connected to; x Consult the dealer and/or experienced radio/TV technician for help.
19 Legal and Regulatory Notices 307FCC IDs and Industry Canada Certification Numbers are listed below: Where necessary, the end user is responsible for obtaining any National licenses required to operate this product and these must be obtained before using the product in any particular country. Contact the appropriate national administrations for details on the conditions of use for the bands in question and any exceptions that might apply. 19.4.2 European Union Notification The PTP 58600 connectorized product is a two-way radio transceiver suitable for use in Broadband Wireless Access System (BWAS), Radio Local Area Network (RLAN), or Fixed Wireless Access (FWA) systems. It is a Class 2 device and uses operating frequencies that are not harmonized throughout the EU member states. The operator is responsible for obtaining any national licenses required to operate this product and these must be obtained before using the product in any particular country. This equipment complies with the essential requirements for the EU R&TTE Directive 1999/5/EC. The use of 5.8GHz for Point to Point radio links is not harmonized across the EU and currently the product may only be deployed in the UK, Eire (IRL), Germany, Norway and Denmark. However, the regulatory situation in Europe is changing and the radio spectrum may become available in other countries in the near future. Also see www.ero.dk for further information. Motorola declares that the PTP 58600 product complies with the essential requirements and other relevant provisions of Directive 1999/5/EC. The declaration of conformity may be consulted at http://motorola.canopywireless.com/doc.php. This equipment is marked to show compliance with the European R&TTE directive 1999/5/EC.
19 Legal and Regulatory Notices 308European Union (EU) Waste of Electrical and Electronic Equipment (WEEE) directive The European Union's WEEE directive requires that products sold into EU countries must have the crossed out trash bin label on the product (or the package in some cases). As defined by the WEEE directive, this cross-out trash bin label means that customers and end-users in EU countries should not dispose of electronic and electrical equipment or accessories in household waste. Customers or end-users in EU countries should contact their local equipment supplier representative or service center for information about the waste collection system in their country. 19.4.3 UK Notification The PTP 58600 connectorized product has been notified for operation in the UK, and when operated in accordance with instructions for use it is compliant with UK Interface Requirement IR2007. For UK use, installations must conform to the requirements of IR2007 in terms of EIRP spectral density against elevation profile above the local horizon in order to protect Fixed Satellite Services. The frequency range 5795-5815 MHz is assigned to Road Transport & Traffic Telematics (RTTT) in the U.K. and shall not be used by FWA systems in order to protect RTTT devices. UK Interface Requirement IR2007 specifies that radiolocation services shall be protected by a Dynamic Frequency Selection (DFS) mechanism to prevent co-channel operation in the presence of radar signals. IMPORTANT: This equipment operates as a secondary application, so it has no rights against harmful interference, even if generated by similar equipment, and must not cause harmful interference on systems operating as primary applications.
19 Legal and Regulatory Notices 309 19.5 National and Regional Regulatory Notices – PTP 54600 Variant 19.5.1 U.S. Federal Communication Commission (FCC) and Industry Canada (IC) Notification This device complies with part 15.407 of the US FCC Rules and Regulations and with RSS-210 Issue 7 of Industry Canada. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation. In Canada, users should be cautioned to take note that high power radars are allocated as primary users (meaning they have priority) of 5250 – 5350 MHz and 5650 – 5850 MHz and these radars could cause interference and/or damage to license-exempt local area networks (LELAN). For the connectorized version of the product and in order to reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (EIRP) is not more than that permitted by the regulations. The transmitted power must be reduced to achieve this requirement. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the US FCC Rules and with RSS-210 of Industry Canada. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with these instructions, may cause harmful interference to radio communications. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment on and off, the user is encouraged to correct the interference by one or more of the following measures: x Increase the separation between the affected equipment and the unit; x Connect the affected equipment to a power outlet on a different circuit from that which the receiver is connected to; x Consult the dealer and/or experienced radio/TV technician for help. x FCC IDs and Industry Canada Certification Numbers are listed below:
19 Legal and Regulatory Notices 310Where necessary, the end user is responsible for obtaining any National licenses required to operate this product and these must be obtained before using the product in any particular country. Contact the appropriate national administrations for details on the conditions of use for the bands in question and any exceptions that might apply. 19.5.2 European Union Notification The PTP 54600 product is a two-way radio transceiver suitable for use in Broadband Wireless Access System (WAS), Radio Local Area Network (RLAN), or Fixed Wireless Access (FWA) systems. It is a Class 1 device and uses operating frequencies that are harmonized throughout the EU member states. The operator is responsible for obtaining any national licenses required to operate this product and these must be obtained before using the product in any particular country. This equipment complies with the essential requirements for the EU R&TTE Directive 1999/5/EC and has been tested compliant with EuroNorm EN 301 893. Also see www.ero.dk for further information. Motorola declares that the PTP 58600 product complies with the essential requirements and other relevant provisions of Directive 1999/5/EC. The declaration of conformity may be consulted at http://motorola.canopywireless.com/doc.php. This equipment is marked to show compliance with the European R&TTE directive 1999/5/EC. European Union (EU) Waste of Electrical and Electronic Equipment (WEEE) directive The European Union's WEEE directive requires that products sold into EU countries must have the crossed out trash bin label on the product (or the package in some cases). As defined by the WEEE directive, this cross-out trash bin label means that customers and end-users in EU countries should not dispose of electronic and electrical equipment or accessories in household waste. Customers or end-users in EU countries should contact their local equipment supplier representative or service center for information about the waste collection system in their country.
19 Legal and Regulatory Notices 31119.6 National and Regional Regulatory Notices – PTP 25600 Variant 19.6.1 U.S. Federal Communication Commission (FCC) Notification This device complies with Part 27 of the US FCC Rules and Regulations. Use of this product is limited to operators holding Licenses for the specific operating channels. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15E of the US FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with these instructions, may cause harmful interference to radio communications. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment on and off, the user is encouraged to correct the interference by one or more of the following measures: x Increase the separation between the affected equipment and the unit; x Connect the affected equipment to a power outlet on a different circuit from that which the receiver is connected to; x Consult the dealer and/or experienced radio/TV technician for help. x FCC IDs Certification Numbers are listed below: Where necessary, the end user is responsible for obtaining any National licenses required to operate this product and these must be obtained before using the product in any particular country. Contact the appropriate national administrations for details on the conditions of use for the bands in question and any exceptions that might apply. 19.7 ExposureSee Section 2 “Avoiding Hazards”.
19 Legal and Regulatory Notices 31219.8 Legal Notices 19.8.1 Motorola Inc. End User License Agreement In connection with Motorola’s delivery of certain proprietary software or products containing embedded or pre-loaded proprietary software, or both, Motorola is willing to license this certain proprietary software and the accompanying documentation to you only on the condition that you accept all the terms in this End User License Agreement (“Agreement”). IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, DO NOT USE THE PRODUCT OR INSTALL THE SOFTWARE. INSTEAD, YOU MAY, FOR A FULL REFUND, RETURN THIS PRODUCT TO THE LOCATION WHERE YOU ACQUIRED IT OR PROVIDE WRITTEN VERIFICATION OF DELETION OF ALL COPIES OF THE SOFTWARE. ANY USE OF THE SOFTWARE, INCLUDING BUT NOT LIMITED TO USE ON THE PRODUCT, WILL CONSTITUTE YOUR ACCEPTANCE TO THE TERMS OF THIS AGREEMENT. 19.8.1.1 Definitions In this Agreement, the word “Software” refers to the set of instructions for computers, in executable form and in any media, (which may include diskette, CD-ROM, downloadable internet, hardware, or firmware) licensed to you. The word “Documentation” refers to electronic or printed manuals and accompanying instructional aids licensed to you. The word “Product” refers to Motorola’s MOTOwi4™ fixed wireless broadband devices for which the Software and Documentation is licensed for use. 19.8.1.2 Grant of License Motorola, Inc. (“Motorola”) grants you (“Licensee” or “you”) a personal, nonexclusive, non-transferable license to use the Software and Documentation subject to the Conditions of Use set forth in Section 3 “Getting Started” and the terms and conditions of this Agreement. Any terms or conditions relating to the Software and Documentation appearing on the face or reverse side of any purchase order, purchase order acknowledgment or other order document that are different from, or in addition to, the terms of this Agreement will not be binding on the parties, even if payment is accepted.
19 Legal and Regulatory Notices 31319.8.1.3 Conditions of Use Any use of the Software and Documentation outside of the conditions set forth in this Agreement is strictly prohibited and will be deemed a breach of this Agreement. Only you, your employees or agents may use the Software and Documentation. You will take all necessary steps to insure that your employees and agents abide by the terms of this Agreement. You will use the Software and Documentation (i) only for your internal business purposes; (ii) only as described in the Software and Documentation; and (iii) in strict accordance with this Agreement. You may use the Software and Documentation, provided that the use is in conformance with the terms set forth in this Agreement. Portions of the Software and Documentation are protected by United States copyright laws, international treaty provisions, and other applicable laws. Therefore, you must treat the Software like any other copyrighted material (for example, a book or musical recording) except that you may either: (i) make 1 copy of the transportable part of the Software (which typically is supplied on diskette, CD-ROM, or downloadable internet), solely for back-up purposes; or (ii) copy the transportable part of the Software to a PC hard disk, provided you keep the original solely for back-up purposes. If the Documentation is in printed form, it may not be copied. If the Documentation is in electronic form, you may print out 1 copy, which then may not be copied. With regard to the copy made for backup or archival purposes, you agree to reproduce any Motorola copyright notice, and other proprietary legends appearing thereon. Such copyright notice(s) may appear in any of several forms, including machine-readable form, and you agree to reproduce such notice in each form in which it appears, to the extent it is physically possible to do so. Unauthorized duplication of the Software or Documentation constitutes copyright infringement, and in the United States is punishable in federal court by fine and imprisonment. You will not transfer, directly or indirectly, any product, technical data or software to any country for which the United States Government requires an export license or other governmental approval without first obtaining such license or approval.
19 Legal and Regulatory Notices 31419.8.1.4 Title; Restrictions If you transfer possession of any copy of the Software and Documentation to another party outside of the terms of this agreement, your license is automatically terminated. Title and copyrights to the Software and Documentation and any copies made by you remain with Motorola and its licensors. You will not, and will not permit others to: (i) modify, translate, decompile, bootleg, reverse engineer, disassemble, or extract the inner workings of the Software or Documentation, (ii) copy the look-and-feel or functionality of the Software or Documentation; (iii) remove any proprietary notices, marks, labels, or logos from the Software or Documentation; (iv) rent or transfer all or some of the Software or Documentation to any other party without Motorola’s prior written consent; or (v) utilize any computer software or hardware which is designed to defeat any copy protection device, should the Software and Documentation be equipped with such a protection device. If the Software and Documentation is provided on multiple types of media (such as diskette, CD-ROM, downloadable internet), then you will only use the medium which best meets your specific needs, and will not loan, rent, lease, or transfer the other media contained in the package without Motorola’s written consent. Unauthorized copying of the Software or Documentation, or failure to comply with any of the provisions of this Agreement, will result in automatic termination of this license. 19.8.1.5 Confidentiality You acknowledge that all Software and Documentation contain valuable proprietary information and trade secrets and that unauthorized or improper use of the Software and Documentation will result in irreparable harm to Motorola for which monetary damages would be inadequate and for which Motorola will be entitled to immediate injunctive relief. If applicable, you will limit access to the Software and Documentation to those of your employees and agents who need to use the Software and Documentation for your internal business purposes, and you will take appropriate action with those employees and agents to preserve the confidentiality of the Software and Documentation, using the same degree of care to avoid unauthorized or improper disclosure as you use for the protection of your own proprietary software, but in no event less than reasonable care. You have no obligation to preserve the confidentiality of any proprietary information that: (i) was in the public domain at the time of disclosure; (ii) entered the public domain through no fault of yours; (iii) was given to you free of any obligation to keep it confidential; (iv) is independently developed by you; or (v) is disclosed as required by law provided that you notify Motorola prior to such disclosure and provide Motorola with a reasonable opportunity to respond.
19 Legal and Regulatory Notices 31519.8.1.6 Right to Use Motorola’s Name Except as required in 19.8.1.3 above, you will not, during the term of this Agreement or thereafter, use any trademark of Motorola, or any word or symbol likely to be confused with any Motorola trademark, either alone or in any combination with another word or words. 19.8.1.7 Transfer The Software and Documentation may not be transferred to another party without the express written consent of Motorola, regardless of whether or not such transfer is accomplished by physical or electronic means. Motorola’s consent may be withheld at its discretion and may be conditioned upon transferee paying all applicable license fees and agreeing to be bound by this Agreement. 19.8.1.8 Updates During the first 12 months after purchase of a Product, or during the term of any executed Maintenance and Support Agreement for the Product, you are entitled to receive Updates. An “Update” means any code in any form which is a bug fix, patch, error correction, or minor enhancement, but excludes any major feature added to the Software. Updates are available for download at http://www.motowi4solutions.com/software/. Major features may be available from time to time for an additional license fee. If Motorola makes available to you major features and no other end user license agreement is provided, then the terms of this Agreement will apply. 19.8.1.9 Maintenance Except as provided above, Motorola is not responsible for maintenance or field service of the Software under this Agreement.
19 Legal and Regulatory Notices 31619.8.1.10 Disclaimer MOTOROLA DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY, OR IN ANY COMMUNICATION WITH YOU. MOTOROLA SPECIFICALLY DISCLAIMS ANY WARRANTY INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILTY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED “AS IS.” MOTOROLA DOES NOT WARRANT THAT THE SOFTWARE WILL MEET YOUR REQUIREMENTS, OR THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR FREE, OR THAT DEFECTS IN THE SOFTWARE WILL BE CORRECTED. MOTOROLA MAKES NO WARRANTY WITH RESPECT TO THE CORRECTNESS, ACCURACY, OR RELIABILITY OF THE SOFTWARE AND DOCUMENTATION. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. 19.8.1.11 Limitation of Liability THE TOTAL LIABILITY OF MOTOROLA UNDER THIS AGREEMENT FOR DAMAGES WILL NOT EXCEED THE TOTAL AMOUNT PAID BY YOU FOR THE PRODUCT LICENSED UNDER THIS AGREEMENT. IN NO EVENT WILL MOTOROLA BE LIABLE IN ANY WAY FOR INCIDENTAL, CONSEQUENTIAL, INDIRECT, SPECIAL OR PUNITIVE DAMAGES OF ANY NATURE, INCLUDING WITHOUT LIMITATION, LOST BUSINESS PROFITS, OR LIABILITY OR INJURY TO THIRD PERSONS, WHETHER FORESEEABLE OR NOT, REGARDLESS OF WHETHER MOTOROLA HAS BEEN ADVISED OF THE POSSIBLITY OF SUCH DAMAGES. Some jurisdictions do not permit limitations of liability for incidental or consequential damages, so the above exclusions may not apply to you.
19 Legal and Regulatory Notices 31719.8.1.12 U.S. Government If you are acquiring the Product on behalf of any unit or agency of the U.S. Government, the following applies. Use, duplication, or disclosure of the Software and Documentation is subject to the restrictions set forth in subparagraphs (c) (1) and (2) of the Commercial Computer Software – Restricted Rights clause at FAR 52.227-19 (JUNE 1987), if applicable, unless being provided to the Department of Defense. If being provided to the Department of Defense, use, duplication, or disclosure of the Products is subject to the restricted rights set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 (OCT 1988), if applicable. Software and Documentation may or may not include a Restricted Rights notice, or other notice referring specifically to the terms and conditions of this Agreement. The terms and conditions of this Agreement will each continue to apply, but only to the extent that such terms and conditions are not inconsistent with the rights provided to you under the aforementioned provisions of the FAR and DFARS, as applicable to the particular procuring agency and procurement transaction. 19.8.1.13 Term of License Your right to use the Software will continue in perpetuity unless terminated as follows. Your right to use the Software will terminate immediately without notice upon a breach of this Agreement by you. Within 30 days after termination of this Agreement, you will certify to Motorola in writing that through your best efforts, and to the best of your knowledge, the original and all copies, in whole or in part, in any form, of the Software and all related material and Documentation, have been destroyed, except that, with prior written consent from Motorola, you may retain one copy for archival or backup purposes. You may not sublicense, assign or transfer the license or the Product, except as expressly provided in this Agreement. Any attempt to otherwise sublicense, assign or transfer any of the rights, duties or obligations hereunder is null and void. 19.8.1.14 Governing Law This Agreement is governed by the laws of the United States of America to the extent that they apply and otherwise by the laws of the State of Illinois. 19.8.1.15 Assignment This agreement may not be assigned by you without Motorola’s prior written consent.
19 Legal and Regulatory Notices 31819.8.1.16 Survival of Provisions The parties agree that where the context of any provision indicates an intent that it survives the term of this Agreement, then it will survive. 19.8.1.17 Entire Agreement This agreement contains the parties’ entire agreement regarding your use of the Software and may be amended only in writing signed by both parties, except that Motorola may modify this Agreement as necessary to comply with applicable laws. 19.8.1.18 Third Party Software The software may contain one or more items of Third-Party Software supplied by other third-party suppliers. The terms of this Agreement govern your use of any Third-Party Software UNLESS A SEPARATE THIRD-PARTY SOFTWARE LICENSE IS INCLUDED, IN WHICH CASE YOUR USE OF THE THIRD-PARTY SOFTWARE WILL THEN BE GOVERNED BY THE SEPARATE THIRD-PARTY LICENSE.
19 Legal and Regulatory Notices 319UCD SNMP. Copyright 1989, 1991, 1992 by Carnegie Mellon University, Derivative Work – 1996, 1998-2000, Copyright 1996, 1998-2000 The regents of the University of California All Rights reserved. Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission. CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED. WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. ONLY OPEN THE PACKAGE, OR USE THE SOFTWARE AND RELATED PRODUCT IF YOU ACCEPT THE TERMS OF THIS LICENSE. BY BREAKING THE SEAL ON THIS DISK KIT / CDROM, OR IF YOU USE THE SOFTWARE OR RELATED PRODUCT, YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT. IF YOU DO NOT AGREE TO THESE TERMS, DO NOT USE THE SOFTWARE OR RELATED PRODUCT; INSTEAD, RETURN THE SOFTWARE TO PLACE OF PURCHASE FOR A FULL REFUND. THE FOLLOWING AGREEMENT IS A LEGAL AGREEMENT BETWEEN YOU (EITHER AN INDIVIDUAL OR ENTITY), AND MOTOROLA, INC. (FOR ITSELF AND ITS LICENSORS). THE RIGHT TO USE THIS PRODUCT IS LICENSED ONLY ON THE CONDITION THAT YOU AGREE TO THE FOLLOWING TERMS. BZIP2 License Terms. Terms. This. “bzip2" and associated library "libbzip2", are copyright (C) 1996-2000 Julian R Seward. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of condition sand the following disclaimer.The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.
19 Legal and Regulatory Notices 320Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. zlib.h – Interface of the 'zlib' general purpose compression library version 1.2.3, July 18th, 2005. Copyright (C) 1995-2005 Jean-loup Gailly and Mark Adler. This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: x The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. x Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. x This notice may not be removed or altered from any source distribution. Jean-loup Gailly jloup@gzip.org Mark Adler madler@alumni.caltech.edu 19.8.2 Hardware Warranty in U.S. Motorola U.S. offers a warranty covering a period of one year from the date of purchase by the customer. If a product is found defective during the warranty period, Motorola will repair or replace the product with the same or a similar model, which may be a reconditioned unit, without charge for parts or labor.
19 Legal and Regulatory Notices 32119.8.3 Limit of Liability IN NO EVENT SHALL MOTOROLA BE LIABLE TO YOU OR ANY OTHER PARTY FOR ANY DIRECT, INDIRECT, GENERAL, SPECIAL, INCIDENTAL, CONSEQUENTIAL, EXEMPLARY OR OTHER DAMAGE ARISING OUT OF THE USE OR INABILITY TO USE THE PRODUCT (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION OR ANY OTHER PECUNIARY LOSS, OR FROM ANY BREACH OF WARRANTY, EVEN IF MOTOROLA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. (Some states do not allow the exclusion or limitation of incidental or consequential damages, so the above exclusion or limitation may not apply to you.) IN NO CASE SHALL MOTOROLA’S LIABILITY EXCEED THE AMOUNT YOU PAID FOR THE PRODUCT.
20 Specifications 32220 Specifications 20.1 System Specifications 20.1.1 Wireless PTP 25600 Variant Radio Technology Specification RF Band Lower: 2.496-2.568 GHz Middle: 2.572-2.614 GHz Upper: 2.618-2.690 GHz Channel Selection Manual selection. Dynamic Frequency Control N/A Channel size 5, 10, 15 and 30 MHz Manual Power Control Maximum power can be controlled lower than the power limits shown above in order to control interference to other users of the band. Receiver Noise Figure Typically 5 dB Antenna Type Integrated flat plate antenna Antenna Gain 18 dBi typical Antenna Beamwidth 18 Degrees Max Path Loss (5 MHz channel) 157 dB Duplex Scheme TDD, Symmetric (1:1) Range 125 miles (200km) optical Line-of-Sight 6 miles (10km) non-Line-of-Sight Over-the-Air Encryption Proprietary scrambling mechanism. Weather Sensitivity Sensitivity at higher modes may be reduced during high winds through trees due to Adaptive Modulation Threshold changes. Error Correction FEC
20 Specifications 32320.1.2 Wireless PTP 45600 Variant Radio Technology Specification RF Band 4.400-4.600 GHz Channel Selection Manual selection. Dynamic Frequency Control By intelligent Dynamic Frequency Selection (i-DFS) or manual intervention; automatic selection on start-up and continual adaptation to avoid interference. Channel size 5, 10, 15 and 30 MHz Manual Power Control Maximum power can be controlled lower than the power limits shown above in order to control interference to other users of the band. Receiver Noise Figure Typically 5 dB Antenna Type Integrated flat plate antenna Antenna Gain 21.5 dBi typical Antenna Beamwidth 11 Degrees Max Path Loss (5 MHz channel) 157 dB Duplex Scheme TDD, Symmetric (1:1) Range 125 miles (200km) optical Line-of-Sight 6 miles (10km) non-Line-of-Sight Over-the-Air Encryption Proprietary scrambling mechanism. Weather Sensitivity Sensitivity at higher modes may be reduced during high winds through trees due to Adaptive Modulation Threshold changes Error Correction FEC
20 Specifications 324 20.1.3 Wireless PTP 48600 Variant Radio Technology Specification RF Band 4.710-5.000 GHz Channel Selection Manual selection. Dynamic Frequency Control By intelligent Dynamic Frequency Selection (i-DFS) or manual intervention; automatic selection on start-up and continual adaptation to avoid interference. Channel size 5, 10 and 20 MHz Manual Power Control Maximum power can be controlled lower than the power limits shown above in order to control interference to other users of the band. Receiver Noise Figure Typically 5 dB Antenna Type Integrated flat plate antenna Antenna Gain 22 dBi typical Antenna Beamwidth 11 Degrees Max Path Loss (5 MHz channel) 157 dB Duplex Scheme TDD, Symmetric (1:1) Range 125 miles (200km) optical Line-of-Sight 6 miles (10km) non-Line-of-Sight Over-the-Air Encryption Proprietary scrambling mechanism. Weather Sensitivity Sensitivity at higher modes may be reduced during high winds through trees due to Adaptive Modulation Threshold changes Error Correction FEC
20 Specifications 325 20.1.4 Wireless PTP 49600 Variant Radio Technology Specification RF Band 4.900-4.990 GHz Channel Selection Manual selection. Dynamic Frequency Control By intelligent Dynamic Frequency Selection (i-DFS) or manual intervention; automatic selection on start-up and continual adaptation to avoid interference. Channel size 5, 10 and 20 MHz Manual Power Control Maximum power can be controlled lower than the power limits shown above in order to control interference to other users of the band. Receiver Noise Figure Typically 5 dB Antenna Type Integrated flat plate antenna Antenna Gain 22 dBi typical Antenna Beamwidth 11 Degrees Max Path Loss (5 MHz channel) 157 dB Duplex Scheme TDD, Symmetric (1:1) Range 125 miles (200km) optical Line-of-Sight 6 miles (10km) non-Line-of-Sight Over-the-Air Encryption Proprietary scrambling mechanism. Weather Sensitivity Sensitivity at higher modes may be reduced during high winds through trees due to Adaptive Modulation Threshold changes Error Correction FEC
20 Specifications 32620.1.5 Wireless PTP 54600 Variant Radio Technology Specification RF Band 5.470-5.725 GHz Channel Selection By dynamic frequency control and manual intervention Automatic detection on start-up and continual adaptation to avoid interference. Dynamic Frequency Control Initial capture 10-15 sec. Out of service on interference 100 ms. Channel size 5, 10, 15 and 30 MHz Manual Power Control Maximum power can be controlled lower than the power limits shown above in order to control interference to other users of the band. Receiver Noise Figure Typically 6 dB Antenna Type Integrated flat plate antenna Antenna Gain 23 dBi typical Antenna Beamwidth 8 Degrees Max Path Loss (5 MHz channel) 169 dB Duplex Scheme TDD, Symmetric (1:1) Range 125 miles (200km) optical Line-of-Sight 6 miles (10km) non-Line-of-Sight Over-the-Air Encryption Proprietary scrambling mechanism. Weather Sensitivity Sensitivity at higher modes may be reduced during high winds through trees due to Adaptive Modulation Threshold changes Error Correction FEC
20 Specifications 32720.1.6 Wireless PTP 58600 Variant Radio Technology Specification RF Band 5.725-5.850 GHz Channel Selection By dynamic frequency control and manual intervention Automatic detection on start-up and continual adaptation to avoid interference. Dynamic Frequency Control Initial capture 10-15 sec. Out of service on interference 100 ms. Channel size 5, 10, 15 and 30 MHz Manual Power Control Maximum power can be controlled lower than the power limits shown above in order to control interference to other users of the band. Receiver Noise Figure Typically 6 dB Antenna Type Integrated flat plate antenna Antenna Gain 23 dBi typical Antenna Beamwidth 8 Degrees Max Path Loss (5 MHz Channel) 166 dB Duplex Scheme TDD, Symmetric (1:1) Range 125 miles (200km) optical line-of-sight 6 miles (10km) non-line-of-sight Over-the-Air Encryption Proprietary scrambling mechanism. Weather Sensitivity Sensitivity at higher modes may be reduced during high winds through trees due to Adaptive Modulation Threshold changes Error Correction FEC
20 Specifications 32820.1.7 Wireless PTP 59600 Variant Radio Technology Specification RF Band 5.825-5.925GHz Channel Selection By dynamic frequency control and manual intervention Automatic detection on start-up and continual adaptation to avoid interference. Dynamic Frequency Control Initial capture 10-15 sec. Out of service on interference 100 ms. Channel size 5, 10, 15 and 30 MHz Manual Power Control Maximum power can be controlled lower than the power limits shown above in order to control interference to other users of the band. Receiver Noise Figure Typically 6 dB Antenna Type Integrated flat plate antenna Antenna Gain 23 dBi typical Antenna Beamwidth 8 Degrees Max Path Loss (5 MHz Channel) 166 dB Duplex Scheme TDD, Symmetric (1:1) Range 125 miles (200km) optical line-of-sight 6 miles (10km) non-line-of-sight Over-the-Air Encryption Proprietary scrambling mechanism. Weather Sensitivity Sensitivity at higher modes may be reduced during high winds through trees due to Adaptive Modulation Threshold changes Error Correction FEC
20 Specifications 32920.1.8 Management Management Specification Power status Ethernet Link Status Status Indication Data activity Web server and browser for setup Audio tone feedback during installation , plus graphical installation tool suitable for laptop and PDA computing devices Installation Web server for conrmation Radio Performance and Management Via web server and browser, SNMP Alarms Via congurable email alerts, SNMP 20.1.9 Ethernet Bridging Ethernet Bridging Specification Protocol IEEE802.1; IEEE802.1p; IEEE802.3 compatible Interface 10/100/1000BaseT (RJ-45), Supports MDI/MDIX Auto Crossover Data Rates See Section 16 “Data Rate Calculations” Maximum Ethernet Frame Size 2000 bytes NOTE: Practical Ethernet rates will depend on network configuration, higher layer protocols and platforms used. CAUTION: Over the air throughput will be capped to the rate of the Ethernet interface at the receiving end of the link.
20 Specifications 33020.1.10 Physical Integrated Specification Dimensions Width 14.5” (370mm), Height 14.5” (370mm), Depth 3.75” (95mm) Weight 12.1 lbs (5.5 Kg) including bracket Connectorized Specification Dimensions Width 12” (305mm), Height 12” (305mm), Depth 4.01” (105mm) Weight 9.1 lbs (4.3 Kg) including bracket 20.1.11 Powering Power Supply Separate power supply unit (included) Dimensions Width 9.75” (250mm), Height 1.5” (40mm), Depth 3” (80mm) Weight 1.9 lbs (0.864 Kg) Power source 90 – 264 VAC, 50 – 60 Hz / 36 – 60 VDC Power consumption 55 W max 20.1.12 Telecoms Interface TelecomsInterfaces 2 E1 balanced 120R or 2 T1 balanced 100R over a CAT5 screened twisted pair cable Jitter and Wander Compliant with G.823/ G.824. Surge Protection and Power Cross Compliant with GR1089, EN60950, K20, K21.
20 Specifications 33120.2 Safety Compliance Region Specification USA UL 60950 Canada CSA C22.2 No.60950 International CB certified & certificate to IEC 60950 20.3 EMC Emissions Compliance20.3.1 PTP 25600 Variant Region Specification USA FCC Part 15 (Class B) 20.3.2 PTP 45600 Variant Region Specification USA - Military 20.3.3 PTP 48600 Variant Region Specification USA - Military 20.3.4 PTP 49600 Variant Region Specification USA FCC Part 15B
20 Specifications 332 20.3.5 PTP 54600 Variant Region Specification USA FCC Part 15 Class B Canada CSA Std C108.8, 1993 Class B Europe EN55022 CISPR 22 20.3.6 PTP 58600 Variant Region Specification USA FCC Part 15 Class B Canada CSA Std C108.8, 1993 Class B Europe EN55022 CISPR 22
20 Specifications 333 20.4 EMC Immunity Compliance Top-level Specification ETSI 301-489. Specification Comment EN 55082-1 Generic EMC and EMI requirements for Europe EN 61000-4-2: 1995 Electro Static Discharge (ESD), Class 2, 8 kV air, 4 kV contact discharge Testing will be carried to ensure immunity to 15kV air and 8kV contact EN 61000-4-3: 1995 ENV50140: 1993 (radiated immunity) 3 V/m EN 61000-4-4: 1995 (Bursts/Transients), Class 4, 4 kV level (power lines AC & DC) Signal lines @ 0.5 kV open circuit voltage. EN 6100045:1995, (Surge Immunity) Requires screened connection to users network EN 61000-4-6: 1996 (Injected RF), power line, Class 3 @ 10 V/m Signal lines, Class 3 @ 3 V RMS un-modulated.
20 Specifications 33420.5 Radio Certifications20.5.1 PTP 25600 Variant Region Specification (Type Approvals) USA FCC Part 27 20.5.2 PTP 45600 Variant Region Specification (Type Approvals) USA FCC Part 27, NTIA Red Book, TBC 20.5.3 PTP 48600 Variant Region Specification (Type Approvals) USA FCC Part 27, NTIA Red Book, TBC 20.5.4 PTP 49600 Variant Region Specification (Type Approvals) USA FCC Part 90 Canada RSS-111 20.5.5 PTP 54600 Variant Region Specification (Type Approvals) USA FCC Part 15 E EU EN301 893 V1.4.1 with DFS testing using radar parameters as defined in V1.5.1 CANADA RSS 210 Issue 7, Annex 9
20 Specifications 33520.5.6 PTP 58600 Variant Region Specification (Type Approvals) USA FCC Part 15.247 CANADA RSS 210 Issue 7, Annex 8 UK IR 2007 Eire ComReg 02/71R1 EU EN302 502 v 1.2.1
20 Specifications 33620.6 Environmental SpecificationsCategory Specification Temperature ODU: -40°F (-40°C) to 140°F (+60°C) PIDU Plus (indoor deployment): 32°F (0°C) to 104oF (+40°C) PIDU Plus (outdoor deployment within weatherproofed cabinet): -40°F (-40°C) to 140°F (+60°C) Wind Loading 150mph Max (242kph). See Section 12 “Wind Loading” for a full description. Humidity 100% Condensing Waterproof IP65 (ODU), IP53 (PIDU Plus) UV Exposure 10 year operational life (UL746C test evidence) 20.7 System Connections 20.7.1 PIDU Plus to ODU and ODU to Network Equipment Connections Figure 177 - Cable Connection Diagram (T568B Color Coding)
20 Specifications 337Table 53 - Telecoms Connection Pin Out Telecoms Connector Pinout Signal Name Pin 1 E1T1A_TX- Pin 2 E1T1A_TX+ Pin 3 E1T1A_RX- Pin 4 E1T1B_TX- Pin 5 E1T1B_TX+ Pin 6 E1T1A_RX+ Pin 7 E1T1B_RX- Pin 8 E1T1B_RX+
21 FAQs 33821 FAQs Can I source and use my own PoE adaptor with the 600 Series bridge? No. The 600 Series bridge uses a non-standard PoE configuration. Failure to use the Motorola supplied Power Indoor Unit could result in equipment damage and will invalidate the safety certification and may cause a safety hazard. Why has Motorola launched the 600 Series bridge? The 600 Series bridge is the first product to feature Multiple-Input Multiple-Output (MIMO). The PTP 600 Series solutions allow wireless connections of up to 200km (124 miles) in near line-of-sight conditions and up to 10km (6 miles) in deep non-line-of-sight conditions. What is Multiple-Input Multiple-Output (MIMO)? The 600 Series bridge radiates multiple beams from the antenna - the effect of which is to significantly protect against fading and to radically increase the probability that the receiver will decode a usable signal. When the effects of MIMO are combined with those of OFDM techniques and a best in class link budget, there is a significant improvement to the probability of a robust connection over a non-line-of-sight path. What do you mean by “non-line-of-sight”? A wireless connection between two points without optical line-of-sight, that is, with obstructions between the antennas the transmitted signal is still able to reach the receiver and produce a good quality link. What else is special about the 600 Series bridge ? There are many special features built-in to the hardware of the 600 Series bridge. The product offers the highest system gain in its class through high sensitivity antennas for improved signal recovery. It also features a Software Defined Radio system that operates on ultra fast digital signal processors but is controlled by firmware giving the ability to download new firmware when enhancements become available. The 600 Series bridge has a built-in web server for advanced management capabilities including detailed radio signal diagnosis. In which frequency bands does the 600 Series bridge operate? The Motorola point-to-point 600 Series bridge operates in the licensed bands 2.5 GHz and 4.5 GHz, and in the unlicensed bands 5.4 GHz (ETSI Band B), 5.8 GHz (ETSI Band C and FCC ISM band) and 5.9 GHz. Users must ensure that the PTP 600 Series bridge complies with local operating regulations.
21 FAQs 339Why does the 600 Series bridge operate in the 5GHz band? The 5 GHz band offers the dual benefits of high data throughput and good radio propagation characteristics. The wide band of spectrum available is subdivided into several channels such that multiple systems can operate in the vicinity without causing interference to one another. Is the 600 Series bridge an 802.11a device? No, although similar, the 600 Series bridgeuses different encoding and radio transmission systems from 802.11a. In areas where 802.11a systems are operating, the 600 Series bridge will detect the 802.11a radio signals and choose a clear channel away from any interference. How much power does the 600 Series bridge transmit? At all times the 600 Series bridgeoperates within country / region specific regulations for radio power emissions. In addition, the 600 Series bridge uses a technique known as Transmit Power Control (TPC) to ensure that it only transmits sufficient radio power such that the other antenna can receive a high quality signal. How does the PTP 600 Series Bridge avoid interference from other devices nearby? At initialization, the 600 Series bridge monitors the available frequency channels to find a channel that is clear of interference. In operation 600 Series bridge continuously monitors the spectrum to ensure it is operating on the cleanest channel. How does the 600 Series bridge integrate into my data network? The 600 Series bridgeacts as a transparent bridge between two segments of your network. In this sense, it can be treated like a virtual wired connection between the two buildings. The 600 Series bridgeforwards 802.3 Ethernet packets destined for the other part of the network and filters packets it does not need to forward. The system is transparent to higher-level management systems such as VLANs and Spanning Tree. How does the 600 Series bridge provide security for data traffic? The 600 Series bridgehas a range of security features. At installation time each link must be programmed with the serial ID of its partner. The two ends of the link will only communicate with one another, eliminating any chance of "man in the middle" attacks. Over the air security is achieved through a proprietary scrambling mechanism that cannot be disabled, spoofed or snooped by commercial tools. Can I use Apple Macintosh OS X to control and monitor my 600 Series bridge? Yes, but there are some restrictions. Mozilla 1.6 or higher is recommended.
22 Glossary 34022 Glossary ARP Address Resolution Protocol NLOS non-Line-of-Sight ARQ Automatic Repeat reQuest ODU Outdoor Unit BPSK Binary Phase Shift Keying OFDM DC Direct Current Orthogonal Frequency Division Multiplex DFS Dynamic Frequency Selection PC IBM Compatible Personal Computer ETSI European Telecommunications PIDU + Power Indoor Unit Plus Standards Institute PING Packet Internet Groper FAQ Frequently Asked Question POE Power over Ethernet GPS Global Positioning System PSU Power Supply Unit HP Hypertext Transfer Protocol PTP Point-to-Point ID Identity QAM Quadrature Amplitude Modulation IEEE Institute of Electrical and Electronic Engineers RAM Random Access Memory IP Internet Protocol STC Space Time Coding IQ In phase / Quadrature STP Shielded Twisted Pair ISM Industrial Scientific and Medical TCP Transmission Control Protocol I International Telecommunications Union TPC Transmit Power Control LAN Local Area Network URL Universal Resource Location MAC Medium Access Control Layer USA United States of America MDI Medium Dependent Interface UTP Unshielded Twisted Pair MDIX Medium Dependent Interface Crossover UV Ultraviolet VLAN Virtual Local Area Network
23 Index 34123 Index Alarm 121, 122, 123 Alignment 114, 251 Antenna 234, 237, 241, 249, 251 Architecture 46 Cable Loss 237, 241 Cables 108, 249, 252 channels 58, 183 Channels 172, 177, 179 Clock 191 Compliance 331, 333 Configuration45, 131, 137, 151, 153, 156, 163, 176, 200, 204, 236 Connecting 103, 106, 107, 109, 110, 253, 336 Connectors 249 Deployment 240 diagnostics 129, 194 Diagnostics 194 Disarm 165 Distance 80 EIRP 239 Environmental 336 Ethernet 36, 134, 145 Fault Finding 224 Glossary 340 Grounding 109 Installation 150, 211, 237, 249, 252, 275 IP address 113 Licence Key 195 license 46 Lightning 44, 81, 208 Link Budget 240 MAC Address 201 Management 45, 186 MIB 187 Mounting 44, 101, 111 Networking 81 Password 195 Path Loss 83 Planning 49, 82 Properties 197 radio 2, 6 Radio 231, 334 Reboot 198, 200, 207 Recovery 199 Regulatory 240 Repair 35 Reset 200, 203 Restore 138 Safety 34 Save 138 Service 35 SMTP 190 SNMP 187, 190 SNTP 191 Software 200, 235 Spectrum Management 172, 238 Statistics 144 Status 124, 235 Support 100 Surge 44, 108 TDD 77, 159 TFTP 303 Throughput 85, 87, 89, 91 Tools 100, 249 Upgrade 168, 200, 201 Warning 121, 123 Wind 232
23 Index 342 MOTOROLA, the stylized M Logo and all other trademarks indicated as such herein are trademarks of Motorola, Inc. ® Reg. US Pat & Tm. Office. All other product or service names are the property of their respective owners. © 2007 Motorola, Inc. All rights reserved. Unit A1, Linhay Business Park Eastern Road, Ashburton Devon, TQ 13 7UP, UKTelephone Support: +1 877 515-0400 (Worldwide) +44 808 234 4640 (UK) www.motorola.com/ptp

Navigation menu