Cambium Networks 58500 Wireless Ethernet Bridge User Manual PTP 500 Series User Guide

Cambium Networks Limited Wireless Ethernet Bridge PTP 500 Series User Guide

Manual

Download:
Mirror Download [FCC.gov]
Document ID	992908
Application ID	dGzPjewhBHzvsEtqZy9nlw==
Document Description	Manual
Short Term Confidential	No
Permanent Confidential	No
Supercede	No
Document Type	User Manual
Display Format	Adobe Acrobat PDF - pdf
Filesize	273.6kB (3420044 bits)
Date Submitted	2008-08-29 00:00:00
Date Available	2008-10-01 00:00:00
Creation Date	2008-08-15 18:06:06
Producing Software	Acrobat Distiller 8.1.0 (Windows)
Document Lastmod	2008-08-15 18:24:25
Document Title	PTP 500 Series User Guide
Document Creator	Acrobat PDFMaker 8.1 for Word
Document Author:	Bill Trezise

PTP 500 Series
User Guide
MOTOROLA POINT-TO-POINT WIRELESS SOLUTIONS
MOTOROLA, Inc.
Point-to-Point Wireless Bridges – PTP 500 Series
Software Release PTP 500-03-xx
System User Guide
August 15th, 2008
Ref: PHN-1115-003v000
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 500 is a trademark of Motorola, Inc. All other
product or service names are the property of their respective owners.
© 2006-2008 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.
The 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 1 ,
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.
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:
•
Reorient or relocate the Outdoor Unit (ODU).
•
Increase the separation between the affected equipment and ODU.
•
Connect the ODU/PIDU into a power outlet on a circuit different from that to which the
receiver is connected.
•
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 500 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. Notes below the tables indicate countries
where registration of the link is currently mandatory.
Class B Digital Device, A digital device that is marketed for use in a residential environment, notwithstanding use in
commercial, business and industrial environments.
Regulations applicable to PTP 54500 variant
Examples of Regulatory Limits at 5.4GHz
FCC
Under FCC Regulations, 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
Under ETSI Regulations, operation of this product is only allowed with
a License Key for Region 26. This implements Radar Detection in
accordance with ETSI Regulations, including barring of the band from
5600MHz to 5650MHz and limits the EIRP to the regulatory limits
below:
EIRP ≤ Max of [(17 +10 x Log(Channel BW)) and 30]dBm
Canada
Under Industry Canada Regulations, operation of this product is only
allowed with a License Key for Region 13. This implements Radar
Detection in accordance with Canadian Regulations, including barring
of the band from 5600MHz to 5650MHz and limits the EIRP to the
regulatory limits below:
EIRP ≤ Max of [(17 +10 x Log(Channel BW)) and 30]dBm
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.
Regulations applicable to PTP 58500 variant
Examples of Regulatory Limits
USA/ Canada/ Equipment can be operated in any mode, best results will be obtained using
Taiwan
Region 1 settings
Under UK Regulations, operation of this product is allowed with a License Key
for Region 4 . This implements Radar Detection with barring of the band from
5795MHz to 5815MHz and above 5850MHz. It limits the EIRP to the
Regulatory Limits below:
UK
EIRP ≤ Max of [(23 +10 x Log(Channel BW)) and 36]dBm
Under Eire Regulations, operation of this product is only allowed with a License
Key for Region 6. This implements Radar Detection and limits the EIRP to the
Regulatory Limits below:
Eire
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 limits the EIRP to the Regulatory Limits below:
EIRP ≤ Max of [(40 +10 x Log(Channel BW)) and 53]dBm
Germany
Operation of this product is only allowed with a License Key for Region 22 This
limits the band of operation to 5755MHz to 5875MHz and limits the EIRP to the
Regulatory Limits below:
EIRP ≤ Max of [(23 +10 x Log(Channel BW)) and 36]dBm
Denmark
Operation of this product is only allowed with a License Key for Region 27 .
This implements Radar Detection with barring of the band from 5795MHz to
5815MHz. It limits the EIRP to the Regulatory Limits below:
EIRP ≤ Max of [(23 +10 x Log(Channel BW)) and 36]dBm
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.
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.
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
The 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.
Contents
About This User Guide ....................................................................................................... 19
1.1
Interpreting Typeface and Other Conventions ...................................................................... 19
1.2
Getting Additional Help ......................................................................................................... 21
1.3
Sending Feedback ................................................................................................................ 21
Avoiding Hazards ................................................................................................................ 22
2.1
Preventing Overexposure to RF Energy ............................................................................... 22
2.1.1
Calculations for Separation Distances and Power Compliance Margins.............................. 22
Getting Started .................................................................................................................... 25
3.1
For Your Safety ..................................................................................................................... 25
3.2
Welcome ............................................................................................................................... 26
3.2.1
Who Should Use This Guide................................................................................................. 26
3.2.2
Contact Information ............................................................................................................... 26
3.2.3
Repair and Service................................................................................................................ 26
3.3
Product Description ............................................................................................................... 27
3.3.1
The Outdoor Unit (ODU) ....................................................................................................... 28
3.3.2
PIDU Plus – PTP 300/500/600 Series Bridge....................................................................... 29
3.3.3
Redundancy and Alternative Powering Configurations......................................................... 31
3.3.4
Remote LEDs and Recovery Switch ..................................................................................... 33
3.3.5
Cables and connectors ......................................................................................................... 33
3.3.6
PTP and Lightning Protection ............................................................................................... 34
3.3.7
Mounting Brackets................................................................................................................. 34
3.3.8
Configuration and Management............................................................................................ 35
3.4
Warranty................................................................................................................................ 35
Product Architecture .......................................................................................................... 36
General Considerations ..................................................................................................... 39
5.1
Spectrum Planning ................................................................................................................ 39
5.2
Licenses and Region Codes ................................................................................................. 40
5.3
Operational Restrictions ........................................................................................................ 42
5.3.1
Radar Avoidance................................................................................................................... 42
5.3.2
5.8GHz Restrictions .............................................................................................................. 43
5.4
Channel Bandwidth Operation .............................................................................................. 44
5.5
PTP 54500 Specific Frequency Planning Considerations .................................................... 45
5.5.1
PTP 54500 Raster Considerations:....................................................................................... 45
5.5.2
Transmit Power Reduction at the Band Edges ..................................................................... 45
5.6
PTP 58500 Specific Frequency Planning Considerations .................................................... 46
5.6.1
PTP 58500 Raster Considerations........................................................................................ 46
PTP ....................................................................................................................................... 47
5.6.2
58500 Transmit Power Reduction at the Band Edges .......................................................... 47
5.7
Distance ................................................................................................................................ 48
5.8
Networking Information ......................................................................................................... 48
5.9
Lightning Protection and Regulations ................................................................................... 48
5.10
Electrical Requirements ........................................................................................................ 48
Site Planning........................................................................................................................ 49
6.1
Site Selection Criteria............................................................................................................ 49
6.1.1
ODU Site Selection ............................................................................................................... 49
6.1.2
PTP 500 Series Bridge PIDU Plus Site Selection................................................................. 49
6.1.3
Path Loss Considerations ..................................................................................................... 50
6.1.4
Definitions.............................................................................................................................. 50
6.1.5
PTP 54500 Product Variant - Link Loss, Output Power and System Threshold versus
Modulation Mode .................................................................................................................................. 52
6.1.6
PTP 58500 Product Variant - Link Loss, Output Power and System Threshold versus
Modulation Mode .................................................................................................................................. 54
Installation ........................................................................................................................... 56
7.1
Preparation............................................................................................................................ 56
7.2
Installation Procedure ........................................................................................................... 56
7.3
Tools Required ...................................................................................................................... 57
7.4
Installation Support................................................................................................................ 57
7.5
Legal Disclaimer.................................................................................................................... 57
7.6
Mounting the ODUs............................................................................................................... 58
7.7
Connecting Up....................................................................................................................... 60
7.7.1
Preparing the PIDU Plus To ODU Cable .............................................................................. 60
7.7.2
Making the Connections at the ODU..................................................................................... 62
7.7.3
Making the PTP 300/500/600 Series Bridge PIDU Plus Connection At The ODU ............... 63
7.7.4
Routing the Cable.................................................................................................................. 64
7.7.5
Fitting a Lightning Protection Unit ......................................................................................... 64
7.7.6
Grounding the Installation ..................................................................................................... 65
7.7.7
Making the ODU Connection at the PTP 300/500/600 Series Bridge PIDU Plus................. 65
7.7.8
Making the Network Connection at The PIDU Plus – PTP 500 Series Bridge ..................... 66
7.7.9
Mounting the PTP 300/500/600 Series Bridge PIDU Plus .................................................... 66
7.7.10
Powering Up.......................................................................................................................... 68
7.7.11
Aligning the PTP 500 Series Bridge ODUs ........................................................................... 69
7.7.12
Additional Installation Notes.................................................................................................. 72
Web Page Reference........................................................................................................... 73
8.1
Home Page – PTP 500 Series Bridge................................................................................... 75
8.1.1
Home Page Alarm Display .................................................................................................... 76
8.2
Systems Status Page ............................................................................................................ 81
8.3
System Administration Pages ............................................................................................... 86
8.3.1
System Configuration ............................................................................................................ 87
8.3.2
Statistics Page....................................................................................................................... 99
8.3.3
Detailed Counters Page ...................................................................................................... 102
8.3.4
Install Pages........................................................................................................................ 104
8.3.5
Graphical Install................................................................................................................... 115
8.3.6
Software Upgrade ............................................................................................................... 116
8.3.7
Spectrum Management....................................................................................................... 119
8.3.8
Spectrum Management (Fixed Frequency) ........................................................................ 127
8.3.9
Spectrum Management Control - With Operational Restrictions ........................................ 128
8.3.10
Remote Management Page ................................................................................................ 132
8.3.11
Diagnostics.......................................................................................................................... 137
8.3.12
Change System Administration Password .......................................................................... 140
8.3.13
License Key......................................................................................................................... 140
8.3.14
Properties ............................................................................................................................ 141
8.3.15
Reboot................................................................................................................................. 142
Recovery Mode.................................................................................................................. 143
9.1
Upgrade Software Image .................................................................................................... 144
9.2
Reset IP & Ethernet Configuration ...................................................................................... 146
9.3
Erase Configuration............................................................................................................. 147
9.4
Erase Security Parameters ................................................................................................. 148
9.5
Reboot................................................................................................................................. 149
10
Fault Finding...................................................................................................................... 150
10.1
Hardware............................................................................................................................. 150
10.1.1
Power .................................................................................................................................. 150
10.1.2
Ethernet............................................................................................................................... 151
10.1.3
Checking your wiring ........................................................................................................... 152
10.2
Radio ................................................................................................................................... 153
10.2.1
No Activity ........................................................................................................................... 153
10.2.2
Some Activity....................................................................................................................... 154
11
Lightning Protection ......................................................................................................... 155
11.1
Overview ............................................................................................................................. 155
11.1.1
Lightning Protection Zones ................................................................................................. 155
11.2
Detailed Installation ............................................................................................................. 157
11.3
Testing Your Installation...................................................................................................... 160
11.3.1
Pre-Power Testing............................................................................................................... 161
11.3.2
Post-Power Testing ............................................................................................................. 162
11.4
Locating the Fault................................................................................................................ 163
12
Wind Loading..................................................................................................................... 164
12.1
General................................................................................................................................ 164
12.2
Calculation of Lateral Force ................................................................................................ 164
12.3
Capabilities of the PTP 500 Series Bridges ........................................................................ 165
12.4
Wind Speed Statistics ......................................................................................................... 165
13
PTP 500 Series Bridge – Connectorized Model ............................................................. 166
13.1
Scope .................................................................................................................................. 166
13.2
Product Description ............................................................................................................. 166
13.2.1
Hardware............................................................................................................................. 166
13.2.2
Antenna Choices – 5.8 GHz................................................................................................ 167
13.2.3
Suggested Antenna Choices – 5.4 GHz ............................................................................. 167
13.3
Software/Features ............................................................................................................... 168
13.3.1
Status Page......................................................................................................................... 168
13.3.2
Configuration Pages............................................................................................................ 169
13.3.3
Installation Pages ................................................................................................................ 170
13.4
Deployment Considerations ................................................................................................ 172
13.5
Link Budget ......................................................................................................................... 173
13.6
Regulatory Issues................................................................................................................ 173
13.6.1
Antenna Choice (FCC and Industry Canada Regions Only) .............................................. 174
13.6.2
Cable Losses (FCC Regions Only) ..................................................................................... 174
13.6.3
Antennas for USA / Canada – 5.8 GHz............................................................................... 175
13.6.4
Suggested Antennas - 5.4 GHz .......................................................................................... 178
13.7
Installation ........................................................................................................................... 180
13.7.1
Antenna Choice................................................................................................................... 180
13.7.2
Cables and Connectors....................................................................................................... 180
13.7.3
Tools.................................................................................................................................... 180
13.7.4
Miscellaneous supplies ....................................................................................................... 181
13.7.5
Mounting the Connectorized 500 Series Bridge ................................................................. 181
13.7.6
Mounting the antennas........................................................................................................ 181
13.7.7
Alignment Process .............................................................................................................. 181
13.7.8
Aligning Dual Polar Antennas ............................................................................................. 182
13.7.9
Aligning Separate Antennas................................................................................................ 182
13.7.10 Completing the Installation.................................................................................................. 183
13.7.11 Antenna Cable Fixing .......................................................................................................... 183
13.7.12 Antenna Connection Weatherproofing ................................................................................ 184
13.8
Additional Lightning Protection............................................................................................ 185
13.8.1
ODU Mounted Outdoors ..................................................................................................... 185
13.8.2
ODU Mounted Indoors ........................................................................................................ 186
14
Data Rate Calculations ..................................................................................................... 187
15
AES Encryption Upgrade ................................................................................................. 194
15.1
Configuring Link Encryption ................................................................................................ 194
15.1.1
License Keys ....................................................................................................................... 194
15.1.2
Encryption Mode and Key ................................................................................................... 196
15.2
Wireless Link Encryption FAQ ............................................................................................ 197
15.2.1
Encryption data entry fields are not available ..................................................................... 197
15.2.2
Link fails to bridge packets after enabling link encryption................................................... 197
15.2.3
Loss of AES following downgrade....................................................................................... 197
16
Legal and Regulatory Notices.......................................................................................... 198
16.1
Important Note on Modifications ......................................................................................... 198
16.2
National and Regional Regulatory Notices – PTP 58500 variant ....................................... 198
16.2.1
U.S. Federal Communication Commission (FCC) and Industry Canada (IC) Notification.. 198
16.2.2
European Union Notification ............................................................................................... 199
16.2.3
UK Notification..................................................................................................................... 200
16.3
National and Regional Regulatory Notices – PTP 54500 Variant....................................... 201
16.3.1
FCC and Industry Canada (IC) Notification ........................................................................ 201
16.3.2
European Union Notification ............................................................................................... 202
16.4
Exposure ............................................................................................................................. 203
16.5
Legal Notices....................................................................................................................... 204
16.5.1
Motorola Inc. End User License Agreement ....................................................................... 204
16.5.2
Hardware Warranty in U.S. ................................................................................................. 213
16.5.3
Limit of Liability.................................................................................................................... 213
17
Specifications .................................................................................................................... 214
17.1
System Specifications ......................................................................................................... 214
17.1.1
Wireless PTP 54500 Variant ............................................................................................... 214
17.1.2
Wireless PTP 58500 Variant ............................................................................................... 215
10
17.1.3
Management ....................................................................................................................... 216
17.1.4
Ethernet Bridging................................................................................................................. 216
17.1.5
Physical ............................................................................................................................... 217
17.1.6
Powering ............................................................................................................................. 217
17.2
Safety Compliance .............................................................................................................. 217
17.3
EMC Emissions Compliance............................................................................................... 218
17.3.1
PTP 54500 Variant .............................................................................................................. 218
17.3.2
PTP 58500 Variant .............................................................................................................. 218
17.4
EMC Immunity Compliance................................................................................................. 219
17.5
Radio Certifications ............................................................................................................. 220
17.5.1
PTP 54500 Variant .............................................................................................................. 220
17.5.2
PTP 58500 Variant .............................................................................................................. 220
17.6
Environmental Specifications .............................................................................................. 220
17.7
System Connections ........................................................................................................... 221
17.7.1
PIDU Plus to ODU and ODU to Network Equipment Connections..................................... 221
18
FAQs................................................................................................................................... 222
19
Glossary ............................................................................................................................. 224
20
Index ................................................................................................................................... 225
11
1 About This User Guide
List of Figures
Figure 1 - Typical PTP 500 Series Bridge Deployment........................................................................ 27
Figure 2 – PTP 500 Series Bridge Outdoor Unit (ODU) with PTP-LPU ............................................... 28
Figure 3 - Power Indoor Unit (PIDU Plus) – PTP 300/500/600 Series................................................. 29
Figure 4 – PIDU Plus Recovery Switch Location ................................................................................. 29
Figure 5 –PTP 300/500/600 Series Bridge PIDU Plus Power Input..................................................... 31
Figure 6 - External DC Supply Only ..................................................................................................... 31
Figure 7 - External DC Supply and AC Supply..................................................................................... 32
Figure 8 - External DC Supply and Redundant AC Supply .................................................................. 32
Figure 9 - Remote LED and Recovery Switch Wiring .......................................................................... 33
Figure 10 – PTP 500 Series Bridge Layer Diagram ............................................................................. 37
Figure 11 - 5.8 GHz UK RTTT Channel Avoidance – 15 MHz Channel Bandwidth Only .................... 44
Figure 12 - 5.4 GHz Available Spectrum Settings - 15 MHz Channel Bandwidth................................ 45
Figure 13 - 5.8 GHz Available Spectrum Settings – 15 MHz Channel Bandwidth ............................... 46
Figure 14 - Mounting to pole diameters 25mm (1”) to 50mm (2”) ........................................................ 58
Figure 15 - Integral Safety Loop ........................................................................................................... 59
Figure 16 - Correct Cable Preparation for the Recommended Cable .................................................. 60
Figure 17 - Completed ODU Connector ............................................................................................... 61
Figure 18 - Warning Not To Over tighten Cable Gland ........................................................................ 61
Figure 19 – PTP 500 Series Bridge PIDU Plus Connexion.................................................................. 62
Figure 20 - Connecting the PIDU+ to the ODU .................................................................................... 63
Figure 21 - Disconnecting the ODU...................................................................................................... 64
Figure 22 - Making the Network Connection at the PIDU Plus ............................................................ 66
Figure 23 – PTP 500 Series PIDU Plus Drip Loop Configuration ........................................................ 67
Figure 24 - Using DVM For Alignment.................................................................................................. 71
Figure 25 - Menu Navigation Bar.......................................................................................................... 74
Figure 26 - System Summary Page ..................................................................................................... 75
12
1 About This User Guide
Figure 27 - Alarm Warning Triangle ..................................................................................................... 76
Figure 28 - Status Page........................................................................................................................ 81
Figure 29 - System Administration Login Page .................................................................................... 86
Figure 30 - System Configuration Page ............................................................................................... 87
Figure 31 - LAN Configuration Page .................................................................................................... 89
Figure 32 - Configuration Reboot Page................................................................................................ 90
Figure 33 - Configuration Reboot Page - Ethernet Auto Negotiation Disabled .................................... 90
Figure 34 - VLAN Configuration Fields................................................................................................. 91
Figure 35 - QoS Configuration Page .................................................................................................... 92
Figure 36 - Save and Restore Configuration Page .............................................................................. 95
Figure 37 - Save Configuration File Screen ......................................................................................... 96
Figure 38 – PTP 500 Example Configuration File ................................................................................ 96
Figure 39 - Restore Configuration File Pop Up Screen........................................................................ 97
Figure 40 - Reset Configuration and Reboot Confirmation Pop-up ..................................................... 98
Figure 41 - System Statistics................................................................................................................ 99
Figure 42 - Detailed Counters Page ................................................................................................... 102
Figure 43 - License Key Data Entry.................................................................................................... 105
Figure 44 - Installation Wizard Internet Protocol Configuration.......................................................... 106
Figure 45 - VLAN Warning ................................................................................................................. 107
Figure 46 –PTP 58500 and PTP 54500 Variants - Installation Wizard Wireless Configuration........ 108
Figure 47 –PTP 58500 and PTP 54500 Variants - Fixed Frequency Operation ................................ 111
Figure 48 –PTP 58500 and PTP 54500 Variants - Installation Wizard Confirm Configuration .......... 112
Figure 49 - Reboot Confirmation Pop Up ........................................................................................... 112
Figure 50 –PTP 58500 and PTP 54500 Variant - Disarm Installation................................................ 113
Figure 51 - Optional Post Disarm Configuration 2.............................................................................. 114
Figure 52 – Graphical Installation Screen .......................................................................................... 115
Figure 53 - Software Upgrade ............................................................................................................ 116
13
1 About This User Guide
Figure 54 - Software Upgrade Image Check...................................................................................... 117
Figure 55 - Software Download Progress Indicator............................................................................ 118
Figure 56 - Software Upgrade Complete............................................................................................ 118
Figure 57 - Reboot Confirmation Pop Up ........................................................................................... 119
Figure 58 - Spectrum Management as seen from the Master............................................................ 122
Figure 59 - Spectrum Management as seen from the Slave.............................................................. 122
Figure 60 - Active Channel History Screen ........................................................................................ 125
Figure 61 - Spectrum Management Time Series Plot ........................................................................ 126
Figure 62 - Spectrum Management Fixed Frequency Screen ........................................................... 127
Figure 63 - Spectrum Management Help Page (Fixed Frequency) ................................................... 128
Figure 64 - Spectrum Management Master Screen With Operational Restrictions ........................... 129
Figure 65 - Spectrum Management Slave Screen With Operational Restrictions ............................. 130
Figure 66 - Remote Management....................................................................................................... 132
Figure 67 – Warning when disabling HTTP Interface......................................................................... 133
Figure 68 - Remote Management - Diagnostic Alarms ...................................................................... 134
Figure 69 - Diagnostic Plotter ............................................................................................................. 138
Figure 70 - CSV Download................................................................................................................. 139
Figure 71 - Password Change............................................................................................................ 140
Figure 72 - Software License Key Data Entry .................................................................................... 140
Figure 73: License Key reboot Screen ............................................................................................... 141
Figure 74 - Reboot Confirmation Pop Up ........................................................................................... 141
Figure 75 – Properties ........................................................................................................................ 141
Figure 76 - System Reboot................................................................................................................. 142
Figure 77 - Reboot Confirmation Pop Up ........................................................................................... 142
Figure 78 - Recovery Mode Warning Page ........................................................................................ 143
Figure 79 - Recovery Options Page ................................................................................................... 143
Figure 80 - Software Download Progress Indicator Page .................................................................. 145
14
1 About This User Guide
Figure 81 - Software Download Complete Page ................................................................................ 145
Figure 82 - Reboot Confirmation Pop Up ........................................................................................... 145
Figure 83 - Confirm Reset to Factory Default Pop Up........................................................................ 146
Figure 84 - IP and Ethernet Erased Successfully page...................................................................... 146
Figure 85 - Reboot Confirmation Pop Up ........................................................................................... 147
Figure 86 - Confirm Erase Configuration Pop Up............................................................................... 147
Figure 87 - Erase Configuration Successful Page ............................................................................. 147
Figure 88 – Erase Configuration - Reboot Confirmation Pop Up ....................................................... 148
Figure 89 - Confirm Zeroise Security Parameters Pop Up................................................................. 148
Figure 90 - Zeroise Security Parameters Successful Page................................................................ 149
Figure 91 – Recovery - Reboot Confirmation Pop Up........................................................................ 149
Figure 92 - ODU mounted in Zones A & B ......................................................................................... 156
Figure 93 - Showing how the use of a Finial enables the ODU to be mounted inside Zone B .......... 157
Figure 94 - Diagrammatically Showing Typical Mast and Wall Installations ...................................... 158
Figure 95 - PTP LPU Installation Example for PTP 500 Series (Not to Scale) .................................. 158
Figure 96 - PTP 500 Series LPU Kit................................................................................................... 159
Figure 97 - Simplified Circuit Diagram................................................................................................ 160
Figure 98 - PTP LPU test Points ........................................................................................................ 163
Figure 99 – Connectorized 500 Series Bridge Outdoor Unit .............................................................. 166
Figure 100 - Connectorized 500 Series bridge Status Page .............................................................. 168
Figure 101 - Connectorized 500 Series bridge ‘System Configuration’ Page .................................... 169
Figure 102 - Connectorized PTP 500 Series Bridge ‘Installation Wizard’ Page ............................... 170
Figure 103 - Connectorized 500 Series bridge ‘Confirm Installation’ Page........................................ 171
Figure 104 - Connectorized 500 Series bridge ‘Disarm Installation’ Page......................................... 172
Figure 105 - Forming a Drip Loop ...................................................................................................... 184
Figure 106 - Weatherproofing the Antenna Connections ................................................................... 184
Figure 107- Additional Grounding When Using Connectorized Units ................................................ 185
15
1 About This User Guide
Figure 108 - Lightning Arrestor Mounting ........................................................................................... 186
Figure 109 - Polyphaser Assembly..................................................................................................... 186
Figure 110 - BPSK 0.50 Single Payload............................................................................................. 187
Figure 111 - QPSK 0.50 Single Payload ............................................................................................ 188
Figure 112 - QPSK 0.75 Single Payload ............................................................................................ 188
Figure 113 - 16 QAM 0.50 Single Payload......................................................................................... 189
Figure 114 - 16 QAM 0.75 Single Payload......................................................................................... 189
Figure 115 - 64 QAM 0.67 Single Payload......................................................................................... 190
Figure 116 - 64 QAM 0.83 Single Payload......................................................................................... 190
Figure 117 – QPSK 0.50 Dual Payload .............................................................................................. 191
Figure 118 - QPSK 0.75 Dual Payload............................................................................................... 191
Figure 119 - 16 QAM 0.50 Dual Payload ........................................................................................... 192
Figure 120 - 16 QAM 0.75 Dual Payload ........................................................................................... 192
Figure 121 - 64 QAM 0.67 Dual Payload ........................................................................................... 193
Figure 122 - 64 QAM 0.83 Dual Payload ........................................................................................... 193
Figure 123 – AES Software License Key Data Entry ......................................................................... 195
Figure 124 – AES Configuration Data Entry Page ............................................................................. 196
Figure 125 - Configuration Reboot Screen......................................................................................... 197
Figure 126 - Cable Connection Diagram (T568B Color Coding)........................................................ 221
16
1 About This User Guide
List of Tables
Table 1 - Font types ............................................................................................................................ 19
Table 2 - Admonition types................................................................................................................... 20
Table 3 - Power Compliance Margins .................................................................................................. 23
Table 4 - Contact Information ............................................................................................................... 26
Table 5 - PTP 500 Series Bridge Frequency Variants ......................................................................... 39
Table 6 – PTP 58500 Licenses and Region Codes ............................................................................. 41
Table 7 – PTP 54500 Licenses and Region Codes ............................................................................. 42
Table 8 – PTP 58500 FCC Max Transmit Power at the Edge Channels (FCC) .................................. 47
Table 9 - PTP 54500 - IP Mode –System Threshold Figures – 15MHz BW ........................................ 52
Table 10 - PTP 54500 - TDM Mode – System Threshold Figures – 15 MHz BW................................ 53
Table 11 - PTP 58500 - IP Mode –System Threshold Figures – 15 MHz BW ..................................... 54
Table 12 - PTP 58500 - TDM Mode –System Threshold Figures – 15 MHz BW................................. 55
Table 13 - Audio indications from the ODU .......................................................................................... 69
Table 14 - Graphical Installation Behavior ........................................................................................... 70
Table 15 – QoS Default Settings .......................................................................................................... 93
Table 16 – Classification rules upgrade example................................................................................. 93
Table 17 – IEEE802.1Q Classification rules ........................................................................................ 94
Table 18 – 500 Series Bridge Factory Configuration Values ............................................................. 104
Table 19 - Spectrum Management change state key......................................................................... 125
Table 20 - Spectrum Management Time Series Key ......................................................................... 126
Table 21 - Spectrum Management Change State Key With Operational Restrictions....................... 131
Table 22 - Power Indoor Unit LED check chart .................................................................................. 152
Table 23 - Resistance Table Referenced To The RJ45 at the PIDU+ ............................................... 161
Table 24 - Lateral Force – Imperial .................................................................................................... 164
Table 25 - Lateral Force – Metric ....................................................................................................... 164
Table 26 - Cable Losses per Length .................................................................................................. 174
17
1 About This User Guide
Table 27 - Allowed Antennas for Deployment in USA/Canada – 5.8 GHz......................................... 177
Table 28 - Suggested Antennas – 5.4 GHz....................................................................................... 179
List of Equations
Equation 1 - Path Loss ......................................................................................................................... 50
Equation 2 - Link Loss .......................................................................................................................... 84
18
1 About This User Guide
1 About This User Guide
This guide covers the installation, commissioning, operation and fault finding of the Motorola
PTP 500 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.
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
italic
Variable user input in a command-line interface.
Table 1 - Font types
This document employs specific imperative terminology as follows:
•
Type means press the following characters.
•
Enter means type the following characters and then press Enter.
•
Highlight means click anywhere in a row of data to highlight the entire row.
•
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.
19
1 About This User Guide
This 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.
Admonition
Label
General Message
Note Informative content that may:
•
Defy common or cursory logic.
•
Describe a peculiarity of the 500 Series solutions implementation.
•
Add a conditional caveat.
•
Provide a reference.
•
Explain the reason for a preceding statement or provide background
for what immediately follows.
Recommendation Suggestion for an easier, quicker, or safer action or
practice.
Important Informative content that may:
•
Identify an indication that you should watch for.
•
Advise that your action can disturb something that you may not want
disturbed.
•
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.
Table 2 - Admonition types
20
1 About This User Guide
1.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.
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 500 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.
Adobe Reader is a registered trademark of Adobe Systems, Incorporated.
21
2 Avoiding Hazards
2 Avoiding Hazards
2.1
Preventing Overexposure to RF Energy
WARNING: To protect from overexposure to RF energy, install the radios for the 500 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:
•
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.
•
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.
•
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)
•
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.
The applicable power density exposure limits from the documents referenced above are:
•
10 W/m2 for RF energy in the 2.4-, 5.2-, 5.4-, 5.8- and 5.9 GHz frequency bands.
22
2 Avoiding Hazards
Peak power density in the far field of a radio frequency point source is calculated as follows:
P .G
S=
4π d 2
Where
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
Rearranging terms to solve for distance yields:
d=
2.1.1.1
P.G
4π .S
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.
Band
5.4
GHz
EU
Antenna
FCC
5.8
GHz
(Watt)
(m)
(W/m2)
Recom-
Power
mended
Compliance
Distance
(m)
Margin
15.9
200
(23dBi)
(-4.6dBm)
0.00017
2884
(34.6dBi)
10
0.06
0.020
(13dBm)
0.01
200
(23dBi)
10
0.13
7.6
(-1.4dBm)
0.0007
2884
(34.6dBi)
10
0.13
7.6
Integrated
0.32
(25dBm)
0.16
200
(23dBi)
10
0.5
4.0
External
2ft Flat
Plate
0.32
(25dBm)
0.16
631
(28dBi)
10
0.9
4.5
External
6ft Dish
0.32
(25dBm)
0.16
6310
(38dbi)
10
2.83
10
3.5
External
4ft Dish
Integrated
External
4ft Dish
0.005
(7dBm)
Variable
0.00250
Integrated
5.8
GHz
Max
Average
Transmit
Power in
Burst
(Watt)
0.00035
0.0014
10
0.06
Table 3 - Power Compliance Margins
Notes:
•
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.
23
2 Avoiding Hazards
•
At 5.4GHz and EU 5.8GHz, 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.
•
If there are no EIRP limits in the country of deployment, use the distance calculations for
FCC 5.8GHz.
•
At FCC 5.8GHz, for antennas between 0.6m (2ft) and 1.8m (6ft), alter the distance
proportionally to the antenna gain.
24
3 Getting Started
3 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 500 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 500 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
300/500/600 Series is used to power the PTP 500 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:
•
The voltage and polarity is correct and is applied to the correct terminals in the PIDU Plus
•
The power source is rated as SELV
•
The power source is rated to supply at least 1A continuously
•
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.
25
3 Getting Started
3.2
Welcome
Congratulations on the purchase of the PTP 500 Series Bridge from Motorola. The PTP 500
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:
3.2.2
•
Outdoor radio equipment installation
•
Network configuration
•
Use of web browser for system configuration, monitoring and fault finding
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).
Table 4 - Contact Information
3.2.3
Repair and Service
For unit repair or service, contact your service provider or an authorized Motorola Point-toPoint Distributor for Return Material Authorization (RMA) and shipping instructions.
Alternatively, contact the PTP Global Technical Support Center to process an RMA.
26
3 Getting Started
3.3
Product Description
This User Manual is specifically written for the 500 family of point-to-point broadband wireless
solutions. The PTP 500 Series Bridge has been developed to provide Point-to-Point data
connectivity via a 5.4 GHz or 5.8 GHz wireless Ethernet bridge operating at broadband data
rates. The PTP 500 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 500 Series Bridge Deployment
The PTP 500 Series Bridge offers true non-line-of-sight (NLOS) operation by using a
combination of Orthogonal Frequency Division Multiplexing (OFDM) modulation and MultipleInput Multiple-Output (MIMO) techniques. These technologies enable the PTP 500 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 500 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.
27
3 Getting Started
Each end of the link consists of:
•
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).
•
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 500 Series Bridge is made via a 100BaseT Ethernet
connection. Power is provided to the ODU over the 100BaseT Ethernet connection using a
patented non-standard powering technique.
Power is fed into the PTP 500 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.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 500 Series Bridge should only be deployed using the supplied PTP 300/500/600
Series Bridge PIDU Plus. Figure 2 shows an installation example of a PTP 500 Series ODU.
Figure 2 – PTP 500 Series Bridge Outdoor Unit (ODU) with PTP-LPU
28
3 Getting Started
3.3.2
PIDU Plus – PTP 300/500/600 Series Bridge
The PTP 300/500/600 Series Bridge PIDU Plus is used to generate the ODU supply voltage
from the mains supply and inject this supply voltage into the 100BaseT 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
500 Series Bridge to a PIDU Plus ODU port as equipment damage may occur. The PTP
300/500/600 Series Bridge PIDU Plus is not interchangeable with the PTP 400 Series PIDU
Plus.
Figure 3 - 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 10 “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
100BaseT Ethernet network port and the Recovery switch.
Figure 4 – PIDU Plus Recovery Switch Location
29
3 Getting Started
The Recovery switch is used to recover the unit from configuration errors or software image
corruption. To put a PTP 500 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
30 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
300/500/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 500 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:
•
The voltage and polarity is correct and is applied to the correct terminals in the PIDU Plus
•
The power source is rated as SELV
•
The power source is rated to supply at least 1A continuously
•
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 300/500/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”.
30
3 Getting Started
The input supply range for the 300/500/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 5 –PTP 300/500/600 Series Bridge PIDU Plus Power Input
3.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.
CAUTION: The maximum distance from the ODU to the connected network equipment is
100m (330 ft) when using 100BaseT.
3.3.3.1
External DC Supply Only
For use where there is no mains supply.
Figure 6 - External DC Supply Only
31
3 Getting Started
3.3.3.2
External DC Supply and AC Supply
To give redundancy through the use of mains and DC supply.
Figure 7 - External DC Supply and AC Supply
3.3.3.3
External DC Supply and Redundant AC Supply
To guard against mains failure, and failure of the DC output of single PTP 300/500/600 PIDU
Plus.
Figure 8 - External DC Supply and Redundant AC Supply
32
3 Getting Started
3.3.4
Remote LEDs and Recovery Switch
The PTP 300/500/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 9.
Figure 9 - Remote LED and Recovery Switch Wiring
3.3.5
Cables and connectors
The cable used to connect the PTP 300/500/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 500 Series Bridge PIDU Plus to the users Network
Equipment can be any standard CAT5e Cable.
33
3 Getting Started
The 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 11 “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 500 Series Bridge PIDU Plus meets the low level static discharge specifications
identified in Section 17 “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 11
“Lightning Protection”.
3.3.7
Mounting Brackets
The PTP 500 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 300/500/600 Series Bridge”.
34
3 Getting Started
3.3.8
Configuration and Management
Configuration and Management of the PTP 500 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 500 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 purchase. You can register at
http://www.motorola.com/ptp/support/registration/.
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 16.5.1 “Motorola Inc. End User
License Agreement”.
35
4 Product Architecture
4 Product Architecture
The PTP 500 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. This product features
Multiple-Input Multiple-Output (MIMO) technology as well as Orthogonal Frequency Division
Multiplexing (OFDM) modulation, hence enabling a robust link to be achieved in a non-line-ofsight (NLOS) environment.
The PTP 500 Series Bridge has been developed to operate within license exempt frequency
bands.
The current product range supports:
•
ETSI 5.4 GHz band B (5.470-5.725 GHz)
•
USA/Canada UNII Band (5.470-5.725GHz)
•
ETSI 5.8 GHz band C (5.725-5.875 GHz)
•
USA/Canada 5 GHz ISM band (5.725-5.850 GHz)
The PTP 500 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 switches to a more robust
modulation mode in severe or adverse conditions.
The PTP 500 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 and fragments of deprioritised Ethernet MAC frames within 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 as a
standard two-port Ethernet bridge.
36
4 Product Architecture
The PTP 500 series provides eight traffic classes, classifying Ethernet frames into one of
eight prioritised queues based on inspection of the user priority field (802.1p) in a customer
(IEEE802.1Q) VLAN tag or provider (IEEE802.1ad) VLAN tag. Untagged frames receive a
default priority. The scheduling 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 management function of the PTP 500 Series Bridge is logically equivalent to a separate
protocol stack with virtual point of attachment at the Ethernet interface. This is illustrated in
Figure 10.
Figure 10 – PTP 500 Series Bridge Layer Diagram
Each unit in the link is manageable through an IP connection. Standard IP protocols are
utilized for all management functions e.g., HP, SNMP, etc. The unit can be configured to use
VLAN tags on the management interfaces.
37
4 Product Architecture
The PTP 500 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.
38
5 General Considerations
5.1
General Considerations
Spectrum Planning
The PTP 500 Series Bridge has two frequency variants in its product range.
Variant
Definition
Frequency Coverage
Variable
Channel
Width
Channel
Raster
PTP
54500
ETSI 5 GHz Band B
5470-5725 MHz
5, 10, 15
MHz
5 MHz
PTP
58500
ETSI Band,
5725-5875 MHz (ETSI) and
5725-5850 MHz (FCC)
5, 10, 15
MHz
5 MHz
FCC UNII Band
FCC ISM Band
Table 5 - PTP 500 Series Bridge Frequency Variants
NOTE: For PTP 54500 and PTP 58500, use of the product is allowed according to local
regulations.
There are two distinct approaches to spectrum planning:
•
First an operator can utilize the default spectrum management mode i-DFS (intelligent
Dynamic Frequency Selection). This mode uses the PTP 500 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 500 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”.
•
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.
WARNING:This approach must not be used when Radar Detection is enabled.
39
5 General Considerations
5.2
Licenses and Region Codes
The PTP 500 Series Bridge uses a system of Region Codes to control the operation of the
radio link. The Region Code is set by a License Key.
CAUTION To meet the regulatory requirements of your region you should set the correct
Region Code by obtaining a new License Key from your reseller or distributor.
Region
Code
License /
Regulation
Frequencies
FCC USA,
Canada,
Taiwan,
Brazil
Channel
Bandwidth
Max Power
Notes
5725 - 5850
MHz
5, 10, 15 MHz
27 dBm
Reduced TX
power at
band edges
China
5725 - 5850
MHz
5, 10, 15 MHz
33 dBm EIRP
Australia,
Hong Kong
5725 - 5850
MHz
No
5, 10, 15 MHz
34 dBm EIRP
UK
5725 - 5795
MHz
5815 - 5850
MHz
Yes
5 MHz
30 dBm EIRP
10 MHz
33 dBm EIRP
15 MHz
34 dBm EIRP
5, 10, 15 MHz
20 dBm EIRP
5 MHz
27 dBm EIRP
10 MHz
30 dBm EIRP
15 MHz
31 dBm EIRP
5 MHz
47 dBm EIRP
10 MHz
50 dBm EIRP
15 MHz
51 dBm EIRP
5, 10, 15 MHz
27 dBm
5, 10, 15 MHz
27 dBm
5 MHz
33 dBm EIRP
10 MHz
36 dBm EIRP
15 MHz
36 dBm EIRP
Singapore
5725 - 5850
MHz
Eire
5725 - 5875
MHz
Norway
5725 - 5795
MHz
5815 - 5850
MHz
Full Power
Full Power
5725 - 5875
MHz
19
India
5825 - 5875
MHz
DFS
No
Yes
Yes
No
40
5795 MHz to
5815 MHz is
assigned for
Road
Transport
and Traffic
Telematics
(RTTT).
5 General Considerations
Region
Code
License /
Regulation
Frequencies
DFS
Channel
Bandwidth
Max Power
20
Thailand
5725 - 5850
MHz
No
5, 10, 15 MHz
30 dBm EIRP
22
Germany
5725 - 5875
MHz
Yes
5 MHz
30 dBm EIRP
10 MHz
33 dBm EIRP
15 MHz
34 dBm EIRP
5 MHz
27 dBm EIRP
10 MHz
30 dBm EIRP
15 MHz
31 dBm EIRP
5 MHz
30 dBm EIRP
10 MHz
33 dBm EIRP
15 MHz
34 dBm EIRP
5 MHz
30 dBm EIRP
10 MHz
33 dBm EIRP
15 MHz
34 dBm EIRP
24
25
27
Bahrain
ETSI
Denmark
5725 - 5850
MHz
5725 - 5875
MHz
5725 - 5795
5815 - 5875
MHz
Yes
Yes
Yes
Notes
5795 MHz to
5815 MHz is
assigned for
Road
Transport
and Traffic
Telematics
(RTTT)
Table 6 – PTP 58500 Licenses and Region Codes
Region
Code
License /
Regulation
Frequencies
DFS
Channel
Bandwidth
Max Power
Full Power +
Radar
5470 - 5600
MHz
5650 - 5725
MHz
Yes
5, 10, 15 MHz
27 dBm
Full Power
5470 - 5725
MHz
5, 10, 15 MHz
27 dBm
12
FCC USA
5470 - 5725
MHz
5 MHz
24 dBm EIRP
10 MHz
27 dBm EIRP
15 MHz
28 dBm EIRP
5 MHz
24 dBm EIRP
10 MHz
27 dBm EIRP
15 MHz
28 dBm EIRP
13
Australia,
Canada
5470 - 5600
MHz
5650 - 5725
MHz
Yes
41
Notes
The band
5600 MHz to
5650 MHz is
reserved for
the use of
weather
5 General Considerations
Region
Code
License /
Regulation
Frequencies
DFS
Channel
Bandwidth
Max Power
Notes
radars
20
Thailand
26
5470 - 5725
MHz
ETSI
5470 - 5600
MHz
5650 - 5725
MHz
No
Yes
5, 10, 15 MHz
30 dBm EIRP
10 MHz
27 dBm EIRP
15 MHz
30 dBm EIRP
5 MHz
24 dBm EIRP
10 MHz
27 dBm EIRP
15 MHz
28 dBm EIRP
The band
5600 MHz to
5650 MHz is
reserved for
the use of
weather
radars
Table 7 – PTP 54500 Licenses and Region Codes
When shipped from the factory units are configured as follows:
•
PTP 54500 – Region Code 26 4
•
PTP 58500 – Region Code 1
5.3
Operational Restrictions
5.3.1
Radar Avoidance
Radar Avoidance requires that equipment used in the region:
•
Detects interference from other systems and avoids co-channel operation with these
systems, notably radar systems.
•
Provides on aggregate a uniform loading of the spectrum across all devices, that is, Fixed
Frequency operation is not allowed.
Note that PTP 54500 and PTP 58500 are different products.
The Deployment Guide for PTP 54500 also contains the license keys for region 13.
42
5 General Considerations
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 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 available channels. The channel selection algorithm is initiated at link initialization and
when radar interference is detected.
5.3.2
5.3.2.1
5.8GHz Restrictions
RTTT Avoidance and Other Channel Use Restrictions
Where regulatory restrictions apply to certain channels these channels are barred. The user
should note that the number of channels barred is dependant on the channel raster selected.
For example see the effect of the UK RTTT channel restrictions in Figure 11, 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”.
43
5 General Considerations
Figure 11 - 5.8 GHz UK RTTT Channel Avoidance – 15 MHz Channel Bandwidth Only
5.3.2.2
Radar Avoidance, i-DFS and Bandwidth Operation
Radar avoidance at 5.8 GHz is applicable to EU operation and the requirements are currently
as defined in EN 302 502 v1.1.1.
5.4
Channel Bandwidth Operation
Channel bandwidths of 5, 10 and 15 MHz is supported for the PTP 500 product. Configuration
of the variable bandwidth operation must be symmetric, that is, the transmit and receive
channels must use identical channel bandwidths.
44
5 General Considerations
5.5
PTP 54500 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. See Figure 12 (15 MHz channel bandwidth shown).
Figure 12 - 5.4 GHz Available Spectrum Settings - 15 MHz Channel Bandwidth
5.5.1
PTP 54500 Raster Considerations:
The PTP 54500 variant operates on a 5 MHz channel raster. See Figure 12.
5.5.2
Transmit Power Reduction at the Band Edges
The PTP 54500 product variant does not apply any band edge power reduction.
Check
45
5 General Considerations
5.6
PTP 58500 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 13 shows the available spectrum (15 MHz
channel bandwidth shown).
Figure 13 - 5.8 GHz Available Spectrum Settings – 15 MHz Channel Bandwidth
5.6.1
PTP 58500 Raster Considerations
The PTP 58500 variant operates on a 5 MHz channel raster, see Figure 13.
46
5 General Considerations
5.6.2
PTP 58500 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 500 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 for with Region
Code 1. The maximum powers at the edge channels for 5 MHz, 10 MHz and 15 MHz are
presented in Table 8 (FCC). DLCF in the table denotes the default lower center frequency.
Channel
Frequency
(MHz)
Max Power (dBm)
Max Power (dBm)
Max Power (dBm)
5 MHz Bandwidth
10 MHz Bandwith
15 MHz Bandwidth
5730
26(DLCF)
N/A
N/A
5731
27
N/A
N/A
5732
27
N/A
N/A
5733
27
26
N/A
5734
27
27
N/A
5735
27
27 (DCLF)
25 (DCLF)
5736
27
27
25
5737
27
27
25
5738
27
27
25
5739
27
27
25
5740
27
27
27
5838
27
27
27
5839
27
27
26
5840
27
27
26
5841
27
27
N/A
5842
27
26
N/A
5843
27
N/A
N/A
5844
27
N/A
N/A
5845
26
N/A
N/A
Table 8 – PTP 58500 FCC Max Transmit Power at the Edge Channels (FCC)
47
5 General Considerations
5.7
Distance
The PTP 500 Series Bridge will operate at ranges from 100 m (330 ft) to 250 km (155 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.8
Networking Information
The PTP 500 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 7.2 “Installation Procedure”.
5.9
Lightning Protection and Regulations
The amount of lightning protection is dependent on regulatory requirements and the end user
requirements. The standard ODU for the PTP 500 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 500 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 11 “Lightning Protection”.
5.10
Electrical Requirements
The PTP 500 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 300/500/600 Series Bridge”.
48
6 Site Planning
6 Site Planning
6.1
Site Selection Criteria
The following are guidelines for selecting the installation location of the ODU and PIDU Plus
for a PTP 500 Series Bridge.
6.1.1
ODU Site Selection
When selecting a site for the ODU the following should be taken into consideration:
•
It is not possible for people to stand or walk inadvertently in front of the antenna
•
Height and location to achieve the best radio path
•
Height in relation to other objects with regard to lightning strikes
•
As high as practically possible over obstructions
•
Point it at the Remote end
•
Aesthetics and planning permission issues
•
Distance from the ODU and connected Network equipment (Maximum cable run from the
ODU to the connected equipment is 100m [330 ft])
6.1.2
PTP 500 Series Bridge PIDU Plus Site Selection
When selecting a site for the PIDU Plus the following should be taken into consideration:
•
Availability of a mains electricity supply
•
Accessibility for viewing status indicators and pressing Recovery switch.
49
6 Site Planning
6.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).
L free _ space + Lexcess + L fade + Lseasonal < Lcapability
Where
L free _ space
Lexcess
L fade
Lseasonal
Lcapability
Free Space Path Loss (dB)
Excess Path Loss (dB)
Fade Margin Required (dB)
Seasonal Fading (dB)
Equipment Capability (dB)
Equation 1 - Path Loss
6.1.4
Definitions
The equipment capability is given in Table 9, Table 11 (IP Mode) and Table 10, Table 12
(TDM Mode). Each table gives Link Loss, Output Power and System Thresholds for PTP 500
Series Bridge in all modulation modes.
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 and channel coding rate of R= 0.75, denoted as 64QAM 0.75.
50
6 Site Planning
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.
Sensitivity: Sensitivity is defined as the combined receive input signal level on both
-7
horizontal and vertical inputs that produces a Null BER Error ratio of 3x10 .
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 BPSK receive sensitivity.
Maximum 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 with 23 dBi (5.8 GHz and
5.4 GHz) gain are used.
51
6 Site Planning
6.1.5
PTP 54500 Product Variant - Link Loss, Output Power and System Threshold versus
Modulation Mode
Table 9 and Table 10 show typical system threshlold figures for IP and TDM, respectively (15
MHz channel bandwidth shown).
Modulation Mode
Threshold
Value (dBm)
Output Power
Maximum Link
(dBm)
Loss (dB)
64 QAM 0.83 dual
-69.6
+21
136.6
64QAM 0.67 dual
-73.6
+22
141.6
16QAM 0.75 dual
-76.5
+23
145.5
16QAM 0.50 dual
-81.1
+24
151.1
QPSK 0.75 dual
-82.49
+25
153.5
64QAM 0.83 single
-73.2
+21
140.2
64QAM 0.67 single
-77.1
+22
145.1
16QAM 0.75 single
-79.9
+23
148.9
16QAM 0.50 single
-84.6
+24
154.7
QPSK 0.75 single
-86.2
+25
157.2
QPSK 0.50 single
-89.2
+26
161.2
BPSK 0.50 single
-95.5
+27
168.5
Table 9 - PTP 54500 - IP Mode –System Threshold Figures – 15MHz BW
52
6 Site Planning
Modulation Mode
Threshold
Value (dBm)
Output Power
Maximum Link
(dBm)
Loss (dB)
64 QAM 0.83 dual
-65.3
+21
132.3
64QAM 0.67 dual
-68.8
+22
136.8
16QAM 0.75 dual
-73.1
+23
142.1
16QAM 0.50 dual
-76.3
+24
146.3
QPSK 0.75 dual
-79.5
+25
150.5
64QAM 0.83 single
-69.0
+21
136.0
64QAM 0.67 single
-72.2
+22
140.2
16QAM 0.75 single
-76.6
+23
145.6
16QAM 0.50 single
-79.6
+24
149.6
QPSK 0.75 single
-83.3
+25
154.3
QPSK 0.50 single
-85.8
+26
157.8
BPSK 0.50 single
-95.51
+27
168.5
Table 10 - PTP 54500 - TDM Mode – System Threshold Figures – 15 MHz BW
53
6 Site Planning
6.1.6
PTP 58500 Product Variant - Link Loss, Output Power and System Threshold versus
Modulation Mode
Table 11 and Table 12 show typical system threshlold figures for IP and TDM, respectively
(15 MHz channel bandwidth shown).
Modulation Mode
Threshold
Value (dBm)
Output Power
Maximum Link
(dBm)
Loss (dB)
64 QAM 0.83 dual
-70.6
+21
137.6
64QAM 0.67 dual
-74.8
+22
142.9
16QAM 0.75 dual
-78.1
+23
147.1
16QAM 0.50 dual
-83.4
+24
153.4
QPSK 0.75 dual
-84.5
+25
155.5
64QAM 0.83 single
-74.3
+21
141.3
64QAM 0.67 single
-78.0
+22
146.0
16QAM 0.75 single
-81.2
+23
150.2
16QAM 0.50 single
-86.7
+24
156.7
QPSK 0.75 single
-88.6
+25
159.6
QPSK 0.50 single
-90.5
+26
162.5
BPSK 0.50 single
-96.2
+27
169.3
Table 11 - PTP 58500 - IP Mode –System Threshold Figures – 15 MHz BW
54
6 Site Planning
Modulation Mode
Threshold
Value (dBm)
Output Power
Maximum Link
(dBm)
Loss (dB)
64 QAM 0.83 dual
-66.0
+21
133.0
64QAM 0.67 dual
-99.0
+22
137.0
16QAM 0.75 dual
-73.9
+23
142.9
16QAM 0.50 dual
-77.2
+24
147.2
QPSK 0.75 dual
-80.4
+25
151.4
64QAM 0.83 single
-69.9
+21
136.9
64QAM 0.67 single
-73.0
+22
141.0
16QAM 0.75 single
-77.7
+23
146.8
16QAM 0.50 single
-81.0
+24
151.0
QPSK 0.75 single
-85.1
+25
156.1
QPSK 0.50 single
-87.6
+26
159.6
BPSK 0.50 single
-96.2
+27
169.3
Table 12 - PTP 58500 - TDM Mode –System Threshold Figures – 15 MHz BW
55
7 Installation
7 Installation
IMPORTANT Motorola recommends that only qualified personnel undertake the installation of
a PTP 500 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
Preparation
Before proceeding with the installation you should:
7.2
•
Check the contents of all packages against the parts lists shown in the packing list.
•
Ensure that you have the correct tools for the job.
•
Ensure that you are qualified to undertake the work.
•
Ensure that you have taken the correct safety precautions.
•
Have completed the site planning as described in Section 6 “Site Planning”.
Installation Procedure
The 500 Series installation procedure consists of the following steps:
•
Mounting the ODUs, Section 7.6 “Mounting the ODUs”
•
Connecting up, Section 7.7 “Connecting Up”
•
Mounting the PIDU Plus units, Section 7.7.9 “Mounting the PTP 300/500/600 Series
Bridge PIDU Plus”
•
Mounting the Lightning Protection Units, Section 7.7.5 “Fitting a Lightning Protection
Unit”.
•
Powering Up, Section 7.7.10 “Powering Up”.
•
Aligning the ODUs, Section 7.7.11 “Aligning the PTP 500 Series Bridge ODUs”.
56
7 Installation
7.3
Tools Required
The following specific tools are required to install a PTP 500 Series Bridge in addition to
general tools:
•
13mm and 22mm Spanner / Wrench
•
RJ45 Crimp Tool. Must be the tool specified for the RJ45 plugs being used.
•
IBM Compatible Personal Computer (PC) running Windows 98 or later with 10, 100 or
1000BaseT Ethernet (Ability to change IP settings easily is recommended)
7.4
•
Either Internet Explorer version 6 or higher, or FireFox 1.5 or higher are recommended.
•
Ethernet patch cable
Installation Support
Online 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 18 “FAQs”.
7.5
Legal Disclaimer
IN NO EVENT SHALL MOTOROLA, INC. BE LIABLE FOR ANY INJURY TO ANY PERSONS
OR ANY DAMAGE CAUSED DURING THE INSTALLATION OF THE MOTOROLA PTP 500
SERIES PRODUCT.
57
7 Installation
7.6
Mounting the ODUs
The 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”).
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 14.
Figure 14 - Mounting to pole diameters 25mm (1”) to 50mm (2”)
When adjustment is complete tighten all bolts to 14Nm (11lb ft).
CAUTION: Do not over tighten the bolts as bracket failure may occur.
58
7 Installation
The enclosure and mounting brackets of the PTP 500 Series Bridge product range are
capable of withstanding wind speeds up to 200 mph (320 kph). 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”.
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 15 - 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.
59
7 Installation
7.7
Connecting Up
7.7.1
Preparing the PIDU Plus To ODU Cable
NOTE: The maximum cable length between the ODU and the user’s Network Equipment is
100m (330 ft). The cable should be assembled as shown in Figure 16:
Figure 16 - Correct Cable Preparation for the Recommended Cable
CAUTION: Check that the crimp tool matches the RJ45 connector being used.
60
7 Installation
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.
Figure 17 shows a completed ODU to PIDU Plus cable.
Figure 17 - Completed ODU Connector
CAUTION: Do not over tighten the glands as the internal seal and structure may be
damaged. See Figure 18 for an example of an over tightened cable gland.
Figure 18 - Warning Not To Over tighten Cable Gland
61
7 Installation
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 500 Series Bridge
PIDU Plus connection is the first hole on the right (Figure 19) and is labeled “PIDU +”.
Figure 19 – PTP 500 Series Bridge PIDU Plus Connexion
62
7 Installation
7.7.3
Making the PTP 300/500/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.
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 4: Screw on the clamping nut and tighten
(Do not over tighten – see Figure 18)
Step 3: Screw in the body of the weather
proofing gland and tighten
Figure 20 - Connecting the PIDU+ to the ODU
Should 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.
63
7 Installation
Figure 21 - 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 11 “Lightning Protection”.
64
7 Installation
7.7.6
Grounding the Installation
CAUTION: 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 300/500/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 100BaseT
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
Step 3: Replace the cover and secure with the retaining screw
65
7 Installation
7.7.8
Making the Network Connection at The PIDU Plus – PTP 500 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 22.
Figure 22 - Making the Network Connection at the PIDU Plus
7.7.9
Mounting the PTP 300/500/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.8.
66
7 Installation
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.
It 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 23. 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 23 – PTP 500 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.
67
7 Installation
7.7.10 Powering Up
The PTP 500 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 500 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 auto-sensing MDI/MDIX cross over capability, 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.
68
7 Installation
7.7.11 Aligning the PTP 500 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 500 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 tones and their meanings are as follows:
State Name
Tone
Description
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. Note: During
acquisition there may be
cycling between Scanning
and Synchronized states until
the alignment is sufficient to
maintain the link up.
Rx Power
Registered
Solid tone
Both Master and Slave units
exchanging Radio layer MAC
management messages
Rx Power
Table 13 - Audio indications from the ODU
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.
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.
69
7 Installation
For 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 available (Section 8.3.5 “Graphical Install”) 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:
State Name
Tone Description
State Description
Initialising
Slow beep
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. During this
time the installation tone on the master unit will drop back
to the band scan state. Alignment of the unit should cease
during this time.
Radar CAC
Slow beep
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.
Searching
Slow broken
Searching for peer PTP 500.
Acquiring
Fast broken tone
Found a PTP 500. If it is the right one, it will move onto the
Registering state providing link conditions are OK,
otherwise, it will reverse to Searching.
Registering
Fast broken
Found right PTP 500 and is performing ranging function.
Link Up
Solid Tone
The ranging process is complete and the link is UP.
Alarm
Fast broken dual
A fatal error has occurred.
tone
Table 14 - Graphical Installation Behavior
70
7 Installation
In addition, it is possible to use the BNC connector on the PTP 500 Series ODU and a DVM
to help with the alignment process. The BNC connector provides an analogue voltage which
is proportional to the receive signal strength. To use remove the protective cap frome the
case mounted BNC connector and connect a DVM.Yo may have to invert the pole for correct
reading. Figure 24 shows the relationship between measured values and the receive signal
strength.
Figure 24 - Using DVM For Alignment
When 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:
•
Turn off the audible alignment aid (section 8.3.4.4 “Disarm”)
•
Enable Adaptive Modulation
•
Fully enable Advanced Spectrum Management with i-DFS
•
Clear unwanted installation information from the various systems statistics
•
Store the link range for fast link acquisition on link drop
•
Enable higher data rates
After 24 hours, the units will be disarmed automatically provided that they are armed and that the link is UP.
71
7 Installation
7.7.12 Additional Installation Notes
According to the LINKPlanner report power settings values, some additional steps are
required. These are necessary to ensure that the power levels of the installed units are not
too high.
Higher power levels may cause the saturation of the receivers or may cause false Radar
detection (in Radar Enabled regions) which will cause a degradation of the link performance
and may be responsible for a link failure.
The following procedure describes the additional steps required.
1. Consult the report generated by the LINKPlanner tool and note the Receive and
Transmit power recommended levels.
2. Set the local unit power equal to the 'LOCAL - Max Transmit Power setting while
pointing' value from the LINKPlanner report.
3. Set the remote unit power equal to the 'REMOTE - Max Transmit Power setting while
pointing' value from the LINKPlanner report.
4. Access each unit separately using a PC to reboot the units.
5. Align the units as described in the User Guide.
6. Repeat Step 2 and 3 using the values 'LOCAL - Max Transmit Power setting before
disarm' and 'REMOTE - Max Transmit Power setting before disarm' , if different than
the corresponding 'while pointing' values.
7. Reboot the local unit then reboot the remote unit.
8. Disarm the units.
9. After 1 hour of operation the mean value of Link Loss on the status page should be
within the values given in the LINKPlanner report. Further adjustments of the power
levels may be necessary. Consult the LINKPlanner report notes and adjust the
powers accordingly. You will not be required to reboot the units for that to take effect.
72
8 Web Page Reference
8 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 500 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 .
The web pages have also been tested with Firefox 2.0.0.12. Other browsers may function correctly but have not
been tested.
73
8 Web Page Reference
The 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 25 when the ‘Home’ Link is highlighted as the current page.
Figure 25 - Menu Navigation Bar
74
8 Web Page Reference
8.1
Home Page – PTP 500 Series Bridge
The home page for the PTP 500 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
26) normally displays four key system attributes:
Wireless Link Status: The Wireless Link Status attribute displays the current status of the
PTP 500 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 26 - 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.10.8 “SNTP (Simple Network Time Protocol)” explains how to enable
SNTP and Section 8.3.10.9 “Setting the clock” explains how to set the clock.
75
8 Web Page Reference
8.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 27 shows a sample alarm
screen.
Figure 27 - Alarm Warning Triangle
The following system alarms are defined:
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.
76
8 Web Page Reference
Install 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 datacarrying capacity and stop the installation tone generator. The wireless link is disarmed from
the ‘Installation Wizard’ see Section 8.3.4.4 “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. Note that a change of state may generate an SNMP
trap and/or SMTP email alert.
Incompatible Region Codes: The PTP 500 Series Bridge uses region codes to comply with
local regulatory requirements governing the transmission of wireless signals in the 5.8 GHz
and 5.4 GHz bands. Region codes can only be changed by obtaining a new PTP 500. 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.
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.
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.
77
8 Web Page Reference
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.10.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.
Wireless Link Disable Warning: This warning is displayed if the Wireless link has been
administratively
disabled
via
the
78
SNMP
Interface
(see
8.3.10
“
8 Web Page Reference
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.
Ethernet Link Disabled Warning: This warning is displayed if the Ethernet link has been
administratively
disabled
via
the
79
SNMP
Interface
(see
8.3.10
“
8 Web Page Reference
Remote Management Page”), that is, 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.
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.
80
8 Web Page Reference
8.2
Systems Status Page
The status page has been designed to give the system administrator a detailed view of the
operation of the 500 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.
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 500 Series Bridge at this
interval.
The two PTP 500 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 28 - Status Page
81
8 Web Page Reference
The 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
(5.4 or 5.8 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-RAA.BB-Z where DXX contain the
version of the digital card, AA is the major hardware version number, BB is the minor
hardware version number 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.
82
8 Web Page Reference
Ethernet 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.
MAC Address: MAX address of the unit.
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.
Automatic Page Refresh Period in Seconds: 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. The Transmit Power may be less than the
maximum permitted Transmit Power due to the TPC (Transmit Power Control) mechanism.
This mechanism adjusts Transmit Power to achieve best link performance while minimizing
the interference it causes to other users of this part of the Spectrum.
An 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.11.2 “Diagnostics Download”.
83
8 Web Page Reference
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 footnote 8.
Vector 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 footnote 8.
Link Loss: The link loss is the total attenuation of the wireless signal between the two
point-to-point units. See footnote 8.
The link loss calculation presented below:
Pll = PTx − PRx + g Tx + g Rx
Where
is
Pll
Link Loss (dB)
PTx
Transmit power of the remote wireless unit
(dBm)
PRx
Received signal power at the local unit
(dBm)
g Tx , g R x
Antenna gain at the remote and local units
respectively (dBi) 9 .
Equation 2 - Link Loss
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 footnote 8. Expected data rates can be found in Section 14 “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.
9 The antenna gain of the 500 Series bridge
Connectorized version.
(23.5 dBi) is used unless one or both of the units is a
84
8 Web Page Reference
See footnote 8. Expected data rates can be found in Section 14 “Data Rate Calculations”.
Link 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 14 “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 14 “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:
•
Running at maximum receive mode
•
Running at user-configured Max Modulation Mode
•
Restricted due to byte errors on the wireless link or local Ethernet Tx Fifo Drops
•
Restricted because a DFS channel change is in progress
•
Restricted due to telecoms acquisition mode
•
Restricted due to the low Ethernet link speed
•
Limited by the wireless conditions
Range: The range
10
between the 500 Series bridge ODUs. The range is automatically set by
the PTP 500 Series during installation.
10
The PTP 500 Series Bridge displays range in km by default, if the user would prefer to display range using
Miles the ‘Distance Units’ attribute should be set to imperial, see the “Properties” web page Section 8.3.14.
85
8 Web Page Reference
8.3
System Administration Pages
The following menu options are available for the system administrator and can be password
protected. Figure 29 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 29 - 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:
•
Configuration
•
Statistics
•
The Installation Wizard
•
Software Upgrade
•
Spectrum Management including DFS
•
Remote management
•
Diagnostics Plotter
•
Password Management
•
License Key Management
•
Properties
•
System Reboot
86
8 Web Page Reference
8.3.1
System Configuration
The configuration of the 500 Series Bridge is organized into three sections:
•
General configuration
•
LAN configuration
•
QoS Configuration
•
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 500 Series Bridge.
The QoS configuration sub menu allows the system administrator to modify the classification
of priority encoded Ethernet frames into traffic classes.
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 30) is used by the system administrator to configure
the 500 Series Bridge’s high level administrative (descriptive) attributes and high level
wireless configuration.
Figure 30 - System Configuration Page
87
8 Web Page Reference
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.
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
11
limited to that country’s regulations .
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.
11
In the UK there is a legal requirement to provide a minimum of 19dB 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 19dB compared to the maximum allowed with a simple single step
control.
88
8 Web Page Reference
8.3.1.2
LAN Configuration Page
The LAN configuration page (Figure 31) is used by the system administrator to configure the
500 Series Bridge’s LAN interface.
Figure 31 - 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.
Gateway IP Address: The IP address of a computer / router on the current network that acts
as a gateway.
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”.
89
8 Web Page Reference
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.
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
32 or Figure 33).
Figure 32 - Configuration Reboot Page
Figure 33 - Configuration Reboot Page - Ethernet Auto Negotiation Disabled
This will be followed by a pop-up dialogue box asking to confirm the action.
NOTE: 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.
90
8 Web Page Reference
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 34. 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 500 management function is only compatible with single VLAN tagged
packets. Any management packet with two or more packets will be ignored.
Figure 34 - VLAN Configuration Fields
91
8 Web Page Reference
Use VLAN For Management Interfaces: This control can be configured with one of the
following three values:
•
No VLAN Tagging
•
IEEE 802.1Q Tagged (C-Tag, Type 8100)
•
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
QoS Configuration Page
The QoS configuration page (Figure 35) allows the system administrator to configure the
classification of priority encoded Ethernet frames into up to eight traffic classes.
Figure 35 - QoS Configuration Page
Priority Queue Mapping: specifies the VLAN priority flag to packet queue mapping. The
higher the queue number the greater its priority.
92
8 Web Page Reference
Quality of Service Default Settings
The default classification rules are as shown in Table 15.
Link Layer Priority
Traffic Class
Untagged
Q0
Q0
Q1
Q1
Q1
Q1
Q1
Q1
Q1
Table 15 – QoS Default Settings
NOTE: In the case where the ODU is upgraded from an earlier release that does not support
the 'Multiple Traffic Classes' feature, the classification rules will be initialized as defined in
Table 15 modified to reflect the stored value of "VLAN High Priority Traffic Threshold". For
example, if the existing threshold was set to "VLAN User Priority 4 and Above" then the
classification rules would be initialised as shown in Table 16.
Link Layer Priority
Traffic Class
Untagged
Q0
Q0
Q0
Q0
Q0
Q1
Q1
Q1
Q1
Table 16 – Classification rules upgrade example
93
8 Web Page Reference
The user interface allows also to configure IEEE802.1Q classification rules as shown in Table
17 using the button ‘Set Default 802.1Q Priority Mappings’.
Link Layer Priority
Traffic Class
Untagged
Q1
Q1
Q0
Q2
Q3
Q4
Q5
Q6
Q7
Table 17 – IEEE802.1Q Classification rules
94
8 Web Page Reference
8.3.1.5
Save and Restore Configuration File
The save and restore feature of a PTP 500 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 500 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 36) and
save the configuration file (.cfg) to the hard drive of your computer
12 13
Figure 36 - Save and Restore Configuration Page
12
There is a feature of Internet Explorer (all versions) that will always look at the content of any downloadable file
as make an assessment whether to treat the file as an ASCII or binary file. Unfortunately the configuration file is
always treated as ASCII and the browser attempts to display it instead of downloading it. Firefox (all versions)
makes no such assumptions.
13
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.
95
8 Web Page Reference
Figure 37 - Save Configuration File Screen
The configuration file is encoded using an ASCII encoding scheme. An example is show in
Figure 38.
Figure 38 – PTP 500 Example Configuration File
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.
96
8 Web Page Reference
8.3.1.6
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. It should be noted that when
placing a configuration file into a wireless unit with a different MAC Address the license key
will not be restored and may need to be entered. This can be obtained either from the Quick
Start Guide supplied with the replacement wireless unit or directly from Motorola. Note that
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 39). The user will then be prompted to
confirm the action (Figure 40)
Figure 39 - Restore Configuration File Pop Up Screen
97
8 Web Page Reference
Figure 40 - Reset Configuration and Reboot Confirmation Pop-up
On confirmation the PTP 500 Series Bridge will:
•
Upload the configuration file
•
Perform data integrity checking
•
Erase previous configuration
•
Apply the new configuration
•
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 38.
CAUTION: A reboot is always required to restore a configuration file.
98
8 Web Page Reference
8.3.2
Statistics Page
The 500 Series bridge statistics page is designed to display some key statistics of the
Ethernet Bridge and the underlying wireless performance.
Figure 41 - System Statistics
Wireless Tx Packets: This displays the total number of good packets the bridge has sent for
14
transmission by the wireless interface .
Wireless Rx Packets: This displays the total number of good packets the bridge has
received from the wireless interface. See footnote 14.
14
The number in between brackets displays the number of packets received since the last page refresh.
99
8 Web Page Reference
Ethernet Tx Packets: This displays the total number of good packets the bridge has sent for
transmission by the local Ethernet interface. See footnote 14.
Ethernet Rx Packets: This displays the total number of good packets the bridge has
received from the local Ethernet interface. See footnote 14.
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).
See footnote 14.
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). See footnote 14.
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 footnote 8. Expected data rates can be found in Section 14 “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
footnote 8. Expected data rates can be found in Section 14 “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 footnote 8. Expected data rates can be found in Section 14 “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.
Transmit 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 14 “Data Rate Calculations” where data rate calculations plots are given
for each available modulation mode.
100
8 Web Page Reference
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 14 “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:
•
Running at maximum receive mode
•
Running at user-configured Target Modulation Mode
•
Restricted because Installation is armed
•
Restricted because of byte errors on the wireless link
•
Restricted because a DFS channel change is in progress
•
Restricted due to the low Ethernet link speed
•
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 footnote 8.
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.
Code Word Error Ratio: The ratio of uncorrected Codeword errors to the total number of
Codewords, calculated since the last reset of the system counters.
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.
101
8 Web Page Reference
8.3.3
Detailed Counters Page
Figure 42 - Detailed Counters Page
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: Frames dropped due to lack of capacity in the receive buffer. This includes
packets dropped when the wireless link cannot transmit packets as quickly as they are being
received at the Ethernet interface.
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 (Ethernet interface only).
Rx Multicasts: Total number of good multicast packets (Ethernet interface only).
Rx CRC and Align: Total number of packets with CRC or frame alignment errors.
102
8 Web Page Reference
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) (Ethernet interface only).
Rx Jabbers: Total number of packets received that are greater than the maximum number of
bytes with an invalid CRC (Ethernet interface only).
Tx Drops: Total number of frames dropped due excessive collisions, late collision and frame
ageing.
Tx Packets: Total number of packets received by the interface. This includes both good and
bad packets.
Tx Broadcasts: Total number of good broadcast packets (Ethernet interface only).
Tx Multicasts: Total number of good multicast packets (Ethernet interface only).
Tx Collisions: Total number frames experiencing collisions (Ethernet interface only).
Tx FIFO Drops: Total number frames dropped due to lack of capacity in the transmit buffer,
for example when the 500 Series bridge is connected to the local Ethernet at a connection
speed of less than 100 Mbps (Ethernet interface only).
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 (Ethernet
interface only).
Datailed Counters Page Refresh Period: The statistics page refreshes automatically
according to the setting entered here (in seconds).
103
8 Web Page Reference
8.3.4
Install Pages
These 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”.
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 preconfigured configuration data. Table 18 shows a sample link configuration. The values in red
type have been committed to the wireless unit’s non-volatile storage.
Example PTP 500 Series Configuration Data
For your convenience these two units have been pre-configured as link Units.
Units:
ODU serial number
ODU serial number
0167100000A0
016710000096
Ethernet MAC address
Ethernet MAC address
00:04:56:10:00:96
00:04:56:10:00:A0
Configured as:
Master
Slave
Target MAC address
Target MAC address
00:04:56:20:00:05
00:04:56:20:00:0D
License Key
License Key
9eb8-c807-396c-7c3f-2819-393e-1f48-e46f
c49a-e2ac-9ca7-3925-e4e2-a8cc-120d-2f5e
IP Address
IP Address
169.254.1.2
169.254.1.1
Table 18 – 500 Series Bridge Factory Configuration Values
104
8 Web Page Reference
CAUTION: The factory default configuration is set to Region 26. Region 26 allows the 500
Series bridge a maximum transmit power of 27 dBm. If the local regulatory regime limits the
maximum transmit power (EIRP) to less than 27 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 Section 8.3.4.1 ‘Manually Configuring The Wireless Units’.
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”). If any other parameters require modification then it is recommended that the system
administrator use the Installation Wizard.
A detailed description of the Installation Wizard follows:
The 500 Series bridge operational software requires a license key to enable the wireless
bridging capability and programs region code specific parameters in to the unit.
Figure 43 - License Key Data Entry
105
8 Web Page Reference
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 500 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 43) and click
the ‘validate license key’ button.
8.3.4.2
Internet Protocol Configuration
Step 1 of the installation wizard requires the installer to enter the Internet Protocol (IP)
configuration.
Figure 44 - 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.
106
8 Web Page Reference
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 45.
Figure 45 - VLAN Warning
Once complete, click the ‘Submit Internet Protocol Configuration’ button or the ‘Next’ link.
107
8 Web Page Reference
8.3.4.3
Wireless Configuration
Step 2 of the installation wizard requires the installer to enter the wireless configuration
parameters.
Figure 46 –PTP 58500 and PTP 54500 Variants Installation Wizard Wireless Configuration
Target MAC Address: It 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 500 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.
108
8 Web Page Reference
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. For both modes, the TDD
structure is fixed symmetrically 16:16 (16 OFDM bursts alternately in each direction).
However, the point at which a modulation mode changes for given RF conditions is more
conservative in TDM Mode. 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.
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.
Platform Variant: Chooses between an integrated unit or a connectorized unit that requires
an external antenna.
Channel Bandwidth: Users can choose a variable channel bandwidth for the available
spectrum. Values of 5 MHz, 10 MHz and 15 MHz can be selected.
Link Symmetry: 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. Finally, in adaptive mode the transmit and receive periods
adjust with applied load.
Spectrum Management Control: Is used to configure the PTP 500 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 cochannel interference. Fixed frequency mode allows the installer to fix transmit and receive
frequencies on the units. The frequencies may be configured symmetrically or
asymmetrically.
109
8 Web Page Reference
Lower Center Frequency: The software for the PTP 500 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 Section 5.5 “PTP 54500 Specific Frequency Planning
Considerations” and Section 5.6 “PTP 58500 Specific Frequency Planning Considerations”
depending on the frequency variant.
CAUTION: 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.
Fixed Transmit Frequency, Fixed Receive Frequency: The software for the PTP 500
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 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 47 shows a sample fixed frequency configuration. In the
example the lower center frequency is set to its default values and the Fixed Transmit
Frequency is set to 5735 MHz and the Fixed Receive Frequency is set to 5735 MHz. Care
must be taken when configuring the Fixed Transmit and Receive Frequencies to ensure that
both frequencies are on the same 5 MHz channel raster as the Lower Center Frequency. For
example both the Fixed Transmit and Receive Frequencies must be a multiple of 5 MHz from
the Lower Center Frequency (5740 = 5735 + 5 MHz) and (5745 = 5735 + 5 MHz x 2). Please
note that there is a raster that limits the selection of the Rx frequency based upon the setting
of the Tx frequency, and that the list of options presented in the fixed Tx frequency box is
limited to that raster.
110
8 Web Page Reference
Figure 47 –PTP 58500 and PTP 54500 Variants - Fixed Frequency Operation
Installation 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.
111
8 Web Page Reference
Figure 48 –PTP 58500 and PTP 54500 Variants - Installation Wizard Confirm Configuration
If 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 49).
Figure 49 - Reboot Confirmation Pop Up
All the attributes are committed to non-volatile memory. Immediately following the write to
nonvolatile memory the unit is reset.
112
8 Web Page Reference
NOTE: If you have changed the Ethernet parameters you must reconnect using the correct
network and address settings.
8.3.4.4
Disarm
Step 5 of the installation wizard is the disarm phase.
Figure 50 –PTP 58500 and PTP 54500 Variant - Disarm Installation
113
8 Web Page Reference
Once Section 8.3.4.3 “Wireless Configuration” is complete pressing the “Disarm Installation
Agent” button completes the installation process
15
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.
After disarming the wireless link the user is presented with a message as shown in Figure 51.
This message has been obtained when configuring the link with a Region Code where
maximum power is used (Region Code of 1 and power of 27 dBm). The unit shows that the
Transmit Power has been reduced to the lower operating power band.
The screen presents hyperlinks to the main configuration and spectrum management pages.
Figure 51 - 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.
15
The installation process is completed when both ends of the link are ‘disarmed’.
114
8 Web Page Reference
8.3.5
Graphical Install
To aid the installation of wireless links two graphical installation aids have been introduced in
this 500 Series system version.
•
A PDA installation screen
•
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 52. 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 52 – 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.
115
8 Web Page Reference
For 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:///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 500 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 53 shows the
main software upgrade web page.
Figure 53 - Software Upgrade
The ‘Fixed’ or ‘Recovery’ image is used by the System Administrator to:
•
Reset Ethernet configuration to default settings
•
Erase Configuration
•
Upgrade software
For a full description of the Recovery image see Section 9 “Recovery Mode”.
116
8 Web Page Reference
The 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 500 Series Software image, identifiable by its
‘.dld’ file extension.
The first step (Figure 53) 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 image to wireless unit” button to start the software
16
upgrade process .
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 54)
Figure 54 - Software Upgrade Image Check
16
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.
117
8 Web Page Reference
The 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 500 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 55). 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 55 - Software Download Progress Indicator
Figure 56 - Software Upgrade Complete
118
8 Web Page Reference
When the software image has been written to non-volatile memory Figure 56 will be displayed
showing the status of the software upload.
Reboot the unit by clicking the “Reboot Wireless Unit” button. You will be asked to confirm
this action as shown in Figure 57.
Figure 57 - 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.3.7
Spectrum Management
Spectrum Management Selection is the PTP 500 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 500 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 15 MHz, 10 MHz or 5 MHz of wireless spectrum and is offset in center frequency
from its neighboring channel by 5 MHz. It is important to note that adjacent channels on the
Spectrum management display have a 5 MHz overlap to the adjacent channel.
119
8 Web Page Reference
The default channelization can be modified by varying the lower center frequency attribute in
the installation wizard - see Section 8.3.4.3 “Wireless Configuration”. See Section 5 “General
Considerations” for more detail.
8.3.7.2
Spectrum Management Measurements
Each end of the 500 Series Bridge performs a single measurement of the combined receiver
input power in an inactive portion of the TDD cycle. The measurement is made with an
effective bandwidth of 15 MHz, 10 MHz or 5 MHz on a single channel and includes the
contribution from receiver noise.
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.
The analysis produces three key metrics for each channel:
•
Peak of Means
•
99.9% Percentile of the Means
•
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.
120
8 Web Page Reference
Mean of Means is the arithmetic mean
17
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: 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.
All 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.
17
The arithmetic mean is the true power mean and not the mean of the values expressed in dBm.
121
8 Web Page Reference
Figure 58 - Spectrum Management as seen from the Master
Figure 59 - Spectrum Management as seen from the Slave
122
8 Web Page Reference
Note: These plots are for 15MHz operation; 5/10MHz operation is similar - the width of the
vertical green bar represents the channel width
Figure 58 shows an example Spectrum Management webpage as seen from the master.
Figure 59 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.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 500 Series Bridge will continue to use the current active
channel. (Default –85 dBm)
123
8 Web Page Reference
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.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. See Figure 58 for an
example.
The X-axis shows a stylized view of the 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 1 in Figure 58) 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.
124
8 Web Page Reference
The colored bar represents the following channel state:
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.
Table 19 - Spectrum Management change state key
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.3.7.8
Active Channel History
The active channel history is a time series display of the channels used by the PTP 500
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 60. 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 60 - Active Channel History Screen
125
8 Web Page Reference
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 61 - Spectrum Management Time Series Plot
Figure 61 shows an example time series plot. A time series plot displays the previous 132
measurement quantization periods. If the PTP 500 Series Bridge has not been running for
132 quantization periods then only the number of measurement quantization periods that are
available are displayed.
GREEN
Peak of Means interference measurement
BLACK
99.9% percentile of means interference measurement
BLUE
Mean of Means interference measurement
Table 20 - Spectrum Management Time Series Key
126
8 Web Page Reference
8.3.8
Spectrum Management (Fixed Frequency)
The PTP 500 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.3 “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 62.
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 62 - 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.
127
8 Web Page Reference
Note: These plots are for 15MHz operation; 5/10MHz operation is similar - the width of the
vertical green bar represents the channel width
The 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 63 - Spectrum Management Help Page (Fixed Frequency)
8.3.9
Spectrum Management Control - With Operational Restrictions
When operating with Radar Avoidance enabled the following variances in operation apply:
•
The words “Radar Avoidance” are appended to the “Spectrum Management” title at the
top of the screen. See Figure 64 and Figure 65.
128
8 Web Page Reference
•
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 64.
•
Extra color coding of the interference histogram is provided. See Table 21.
When operating with RTTT (Road transport and Traffic Telematics) Avoidance enabled or
other regulatory restrictions on channel usage the following variances apply:
•
All channels marked with a ‘no entry’ symbol with their associated statistics colored black
are the prohibited channels. See Figure 64 and Figure 65. 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 64 - Spectrum Management Master Screen With Operational Restrictions
129
8 Web Page Reference
Figure 65 - Spectrum Management Slave Screen With Operational Restrictions
130
8 Web Page Reference
The colored bar represents the following channel state:
Green
Active
The channel is currently in use hosting the Point-to-Point wireless
link.
Orange
Interfere
nce
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.
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.
Region
Bar
Region
Bar
This channel has been barred from use by the local region
regulator.
Grey
Table 21 - Spectrum Management Change State Key With Operational Restrictions
131
8 Web Page Reference
8.3.10 Remote Management Page
The Remote Management page (Figure 66) allows the system administrator to configure the
remote management of the PTP 500 Series Bridge.
Figure 66 - Remote Management
132
8 Web Page Reference
8.3.10.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 67.
Figure 67 – Warning when disabling HTTP Interface
8.3.10.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
18
accessed using the telnet interface .
8.3.10.3 SNMP (Simple Network Management Protocol)
The industry standard remote management technique is SNMP (Simple Network
Management Protocol). The PTP 500 Series Bridge supports version 1 and version 2c of the
SNMP protocol.
8.3.10.4 Supported Management Information Bases (MIBS)
The PTP 500 Series Bridge SNMP stack currently supports the following MIBs:
•
MIB-II, RFC-1213, The PTP 500 Series Bridge supports the ‘System Group’ and
‘Interfaces Group’.
•
Bridge MIB, RFC-1493, The PTP 500 Series Bridge supports the ‘dot1dBase Group’ and
the ‘dot1dBasePortTable Group’.
18
•
PTP 500 Series Bridge proprietary MIB
•
RFC-2233 (High capacity counter) MIB
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.
133
8 Web Page Reference
•
WiMAX MIB
SNMP TRAPs supported:
•
Cold Start
•
Link Up
•
Link Down
•
DFS Channel Change
•
DFS Impulsive Interference
8.3.10.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 68. Users can access the sub-menu “Diagnostic
Alarms” to modify the alarms selected.
Figure 68 - Remote Management - Diagnostic Alarms
For a copy of the Motorola proprietary version 1 and version 2 MIB RFCs please consult the
installation CD
134
8 Web Page Reference
8.3.10.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 (500 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 Version: The SNMP protocol version to use for SNMP traps. Note that a system
reboot is required to activate changes to this attribute.
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.
135
8 Web Page Reference
8.3.10.7 SMTP (Simple Mail Transport Protocol)
The SMTP client is an alternative method for the 500 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.
SMTP 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 500 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 500 Series bridge will
send the alert messages.
8.3.10.8 SNTP (Simple Network Time Protocol)
The SNTP client allows the 500 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.
136
8 Web Page Reference
8.3.10.9 Setting the clock
The PTP 500 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 500 Series bridge has been switched off.
SNTP State: If the SNTP State is set to “Disabled”, see Figure 66, 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.
Set Date: Displays the current date. The year, month and day can be set using the dropdown selection boxes.
Time Zone: See Section.8.3.10.9 “Setting the clock”.
Daylight Saving: See Section 8.3.10.9 “Setting the clock”
8.3.11 Diagnostics
For the PTP 500 Series, the storage of link performance histograms is set to 31 days worth of
data. To optimize RAM (volatile memory) usage of a cascading histogram approach has been
adopted. The data is stored for one hour at a resolution of one second. The histograms use a
cascading approach to daisy chain 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. The cascading histograms are defined as::
•
Histogram 1: 1 hour at a resolution of 1 second
•
Histogram 2: 24 hours at a resolution of 1 minute
•
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.
137
8 Web Page Reference
8.3.11.1 Diagnostic Plotter
New for the PTP 500 Series is the system administration diagnostic plotter facility see Figure
69.
Figure 69 - 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:
•
Vector Error
•
Rx Power
•
Tx Power
•
Signal Strength Ratio
•
Link Loss
•
Rx Data Rate
•
Tx Data Rate
•
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.
138
8 Web Page Reference
The 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.11.2 Diagnostics Download
The diagnostics Download page allows the system administrator to download snapshots of
system diagnostics.
Figure 70 - CSV Download
The following diagnostics are available:
•
Vector Error
•
Rx Power
•
Tx Power
•
Signal Strength Ratio V/H
•
Link Loss
•
Rx Data Rate
•
Tx Data Rate
•
Aggregate Data Rate
•
Receive SNR
•
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.
139
8 Web Page Reference
8.3.12 Change System Administration Password
This page (Figure 71) is used to change the password for the system administration (The
factory default is blank).
Figure 71 - Password Change
To change the password any combination of alphanumeric characters, up to 31 characters in
length, can be used.
8.3.13 License Key
The License Key data entry page allows the system administrator to update the 500 Series
bridge license key. Figure 72 shows a sample license key data entry page.
Figure 72 - Software License Key Data Entry
140
8 Web Page Reference
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 73: License Key reboot Screen
The user will then be asked to confirm the reboot (Figure 74).
Figure 74 - Reboot Confirmation Pop Up
8.3.14 Properties
The web page properties screen allows the user to configure the web page interface.
Figure 75 – Properties
WEB Properties: Disable Front Page Login. Allows access to homepage and status page
web pages without forcing a login as the system administrator.
141
8 Web Page Reference
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.
popup Help: Click on the attribute to get a help text box which gives a brief description of the
attribute.
8.3.15 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 76 - System Reboot
Figure 77 - Reboot Confirmation Pop Up
142
9 Recovery Mode
9 Recovery Mode
The Motorola PTP 500 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
300/500/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. On connection to a unit in
recovery mode the following screen is displayed (Figure 78):
Figure 78 - Recovery Mode Warning Page
Clicking on the warning page image will take the user on to the Recovery Option Page
(Figure 79).
Figure 79 - Recovery Options Page
143
9 Recovery Mode
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:
•
IP Address 169.254.1.1
•
Netmask
255.255.0.0
•
Gateway
169.254.1.0
•
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.
Zeroise Critical Security Parameters: This allows the user to erase the security parameters
such as AES parameters. This is to comply with FIPS requirements.
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.
Recovery 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 79) 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 80).
144
9 Recovery Mode
Figure 80 - Software Download Progress Indicator Page
When the download is complete a page is displayed indicating the status of the software
download (Figure 81).
Figure 81 - Software Download Complete Page
After 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 82)
Figure 82 - 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 10 “Fault Finding”.
145
9 Recovery Mode
9.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
(Figure 79). The user will now be presented with a pop up box asking them to confirm the
action (Figure 83).
Figure 83 - Confirm Reset to Factory Default Pop Up
On confirmation the following page will be displayed (Figure 84). The user should now reboot
the unit by pressing the “Reboot” button.
Figure 84 - IP and Ethernet Erased Successfully page
146
9 Recovery Mode
The user will now be presented with a pop up box asking them to confirm the action (Figure
85)
Figure 85 - 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 10 “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 79). The user will now be presented with a pop up box
asking them to confirm the action (Figure 86).
Figure 86 - Confirm Erase Configuration Pop Up
On confirmation the following page will be displayed (Figure 87). The user should now reboot
the unit by pressing the “Reboot” button.
Figure 87 - Erase Configuration Successful Page
147
9 Recovery Mode
The user will now be presented with a pop up box asking them to confirm the action (Figure
88).
Figure 88 – 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 10 “Fault
Finding”.
9.4
Erase Security Parameters
To erase the unit's security parameters and to comply with FIPS the user should press the
``Zeroise Critical Security Parameters'' button on the ``Recovery Options'' page Figure 79.
The user will now be presented with a pop up box asking them to confirm the action (Figure
89).
Figure 89 - Confirm Zeroise Security Parameters Pop Up
148
9 Recovery Mode
On confirmation the following page will be displayed (Figure 90).
Figure 90 - Zeroise Security Parameters Successful Page
9.5
Reboot
This 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 91).
Figure 91 – 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 10 “Fault Finding”.
149
10 Fault Finding
10 Fault Finding
If communication has been lost with the unit at the near end of the link then there may be a
hardware fault with the wiring, network or hardware. Go to the hardware section below. If
communication with the far end of the link is lost then go to the radio section below.
10.1
Hardware
If there are problems suspected with the link hardware the following procedure is
recommended:
10.1.1 Power
Check the power LED at each end of the link. If the power lights are illuminated go to the
Ethernet section below. If at either end they are not illuminated then
19
check the power
source. If neither is illuminated then there is no voltage on the power wires to the ODU.
•
Check that the mains power is connected and switched on.
•
Check that the power LED illuminates if the ODU connector is disconnected at the PIDU
Plus (open the PIDU Plus flap on the left hand side).
If it does illuminate then either the ODU is drawing too much current, or the power wiring to
the ODU is short circuit or the PSU is supplying insufficient power. The likely fault can be
determined by removing the jumper (J906), found inside the removable cover of the PIDU
Plus, and measuring the current taken with an ammeter placed across the 2 jumper pins. This
is normally 10mA without the ODU connected and 300mA to 1A when the ODU is connected.
If it does not illuminate then recheck that power is applied to the PIDU Plus by measuring the
voltage across +55V and 0V pads inside the removable cover in the PIDU Plus. Check that
the PIDU Plus is not short circuit by measuring the impedance across the Power connector. Is
the led faulty?
19
The power indicator LED should be continually illuminated.
150
10 Fault Finding
10.1.2 Ethernet
The Ethernet LED is driven from the ODU processor and thus is capable of informing you of
many conditions using different flash sequences. If the Ethernet indicator does not illuminate
at all there are four possible conditions.
•
There is no power reaching the ODU because of a wiring fault
•
The ODU is faulty
•
The PIDU Plus is faulty
•
The Ethernet network side is faulty
Look at the following table to check the LED response for power up, disconnect the power
and reapply and note what happens.
Differentiating between 1-3 and 4 can be achieved by removing the power for 1 second.
Watch the Ethernet indicator for 1 minute while power is removed, if it never flashes then the
problem is 1-3. Take the jumper (J905) out of the PIDU Plus and check the current taken by
the ODU. This should be 300mA to 1A when starting to run normally.
If the Ethernet indicator flashes to begin with but then stops flashing, the ODU is powered and
software loaded but Ethernet connectivity has been lost between the ODU and the users
connected equipment. All Ethernet connections should be rechecked.
151
10 Fault Finding
Mode
Green LED
Yellow LED No Ethernet
Cable Connected
Yellow LED
Ethernet Cable
Connected between
PIDU Plus and
NIC/Switch/Hub
No Power Applied
Off
Off
Off
Will flash once per
second regularly
approximately 30
seconds after power
applied for 10
seconds then operate
as Ethernet
Link/Activity LED
Power Applied
On
Will flash once per second
regularly approximately 30
seconds after power
applied for 10 seconds then
will go out and stay out
Valid Ethernet Link
and no traffic
On
N/A
Will be on solid for a
valid link.
Valid Ethernet Link
with traffic
On
N/A
Will be on solid, but
will blink randomly as
traffic passes through
Recovery Switch
Pressed and held
for >10 seconds
from power on
(Recovery is
pressed while
power is applied)
Off while switch pressed.
On
Approximately 30 seconds after releasing the
switch, flashes twice per second regularly for 10
seconds, then boots in “Recovery Mode”.
While in “Recovery Mode” the unit will only be
accessible via the IP address 169.254.1.1.
Table 22 - Power Indoor Unit LED check chart
10.1.3 Checking your wiring
If the above procedures fail to diagnose the issue you may have a wiring fault. Unplug the
RJ45 from the PIDU+ and check the following resistances at the RJ45:
1. Check the cable resistance between pins 1 & 2, 3 & 6, 4 & 5 and 7 & 8 at the RJ45.
2. Check against column 2 in Table 23. Resistances for each pair should be within 1 ohm of
each other.
3. Check the cable resistance between pins 1 & 3 at the RJ45. Check against column 3 in
Table 23.
152
10 Fault Finding
4. Check the cable resistance between pins 4 & 7 at the RJ45. Check against column 4 in
Table 23.
5. Ensure that there is greater than 100K ohms between pins 1 & 8 for all cable lengths.
6. Ensure that there is greater than 100K ohms between pin 1 and ODU ground for all cable
lengths.
7. Ensure that there is greater than 100K ohms between pin 8 and ODU ground for all cable
lengths
10.2
Radio
10.2.1 No Activity
If communication over the radio link has been lost 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:
•
Check for Alarm conditions on Home page
•
Check that the software at each end of the link is the same version
•
Check that the Target Mac address has not been mis-configured at each end of the link
•
Check Tx Power
•
Check License keys to ensure that both units are the same product variant
•
Check Master/Slave status for each unit and ensure that one unit is Master and the other
unit is slave
•
Check that the link has not been further obscured or the ODU misaligned
•
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.
153
10 Fault Finding
10.2.2 Some Activity
If there is some activity but the link is unreliable or doesn’t achieve the data rates required
then:
•
Check that the interference has not increased using the i-DFS measurements
•
If a quieter channel is available check that it is not barred
•
Check that the path loss is low enough for the communication rates required
•
Check that the ODU has not become misaligned
154
11 Lightning Protection
11 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.
11.1
Overview
The idea 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.
11.1.1 Lightning Protection Zones
The installation of the ODU can be classified into two different lightning protection zones:
•
Zone A: In this zone a direct lighting strike is possible.
•
Zone B: In this zone a direct lightning strike is unusual, but the full electromagnetic field 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.
The following diagrams (Figure 92 & Figure 93) 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
20
Failure to do so may put
structures, equipment and life at risk.
20
Local regulations may also require the fitting of the 8 AWG ground wire referred below.
155
11 Lightning Protection
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 500 Series bridge ODU grounding point can be found on the bottom of the unit. The
500 Series Bridge is supplied with an appropriate grounding lug for attachment to the ODU.
Figure 92 - ODU mounted in Zones A & B
156
11 Lightning Protection
Figure 93 - Showing how the use of a Finial enables the ODU to be mounted inside Zone B
11.2
Detailed Installation
The recommended components for an installation protected for nearby strikes are:
•
Recommended cables as described in Section 3.3.5 “Cables and connectors”.
•
Lightning protection: Motorola PTP-LPU - 2 per link (2 Motorola Kits, part number 2978)
•
Grounding Stake
•
RJ45 screened connectors
NOTE: There may be a local regulatory requirement to cross bond the CAT 5e cable at
regular intervals to the mast. This may be as frequent as every 10 meters (33 feet).
Figure 94 includes illustrations showing the placement of the PTP lightning protection units
and the recommended components for typical Mast/Tower or Wall installations.
157
11 Lightning Protection
Figure 94 - Diagrammatically Showing Typical Mast and Wall Installations
The Lightning protection Unit should be mounted at the building entry point and must be
grounded (Figure 95).
Figure 95 - PTP LPU Installation Example for PTP 500 Series (Not to Scale)
158
11 Lightning Protection
Figure 96 shows all the components that are supplied with the Motorola Kit 2978.
Figure 96 - PTP 500 Series LPU Kit
159
11 Lightning Protection
11.3
Testing Your Installation
If you have followed the above instructions you will have wired your system to the following
diagram:
Figure 97 - Simplified Circuit Diagram
160
11 Lightning Protection
11.3.1 Pre-Power Testing
Before plugging the RJ45 from the lower LPU (or if not fitted the ODU) into the PIDU, check
the following resistances at the RJ45:
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 23. 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 23.
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. Ensure that there is greater than 100K ohms between pin 8 and ODU ground for all cable
lengths.
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.8
1.0
1.6
10
2.5
2.7
3.3
20
4.2
4.4
5.0
30
5.9
6.1
6.7
40
7.6
7.8
8.4
50
9.3
9.5
10.1
60
11.0
11.2
11.8
70
12.7
12.9
13.5
80
14.4
14.6
15.2
90
16.1
16.3
16.9
100
17.8
18.0
18.6
Table 23 - Resistance Table Referenced To The RJ45 at the PIDU+
161
11 Lightning Protection
11.3.2 Post-Power Testing
The Correct Operation is as follows
1. Connect the RJ45 to the PIDU and apply power to the PIDU, the power LED should
illuminate continuously.
2. After 30 seconds, the Ethernet LED should be observed starting with 10 slow flashes.
3. If there is a network connection the Ethernet LED will then show Ethernet activity.
If the system does not operate correctly, refer to the fault finding guide below:
The PIDU Green power LED does not illuminate
Unplug the ODU connection from the PIDU and check the power LED illumination. If the
power LED still does not light then check the power source.
The PIDU Green power LED flashes
A flashing power LED indicates that there is a short circuit on the output of the PIDU. Check
that pins 4&5 and 7&8 are not crossed with pins 1&2 and 3&6 on the RJ45, and also greater
than 100K ohms between pins 1&8
The Ethernet LED flashes ten times but does not show Ethernet activity
Failure of the Ethernet LED to show Ethernet activity can be due to wiring to pins 1&2 and
3&6 being incorrect, for example if the wiring to pins 1 and 3 are crossed.
The Ethernet connection to the network is only 10/100 BaseT, when 1000 BaseT was
expected
It is likely there is a fault with the wiring to pins 4&5 and 7&8.
162
11 Lightning Protection
11.4
Locating the Fault
Having identified which of the wiring cores are likely to be connected incorrectly, the location
of the faulty cable can be narrowed by disconnecting sections of the drop cable and by
unplugging the relevant RJ45 connectors from the LPUs.
As a further aid to locating the fault the Ethernet connections are also available inside the
LPU. The connections can be accessed by rotating the LPU lid as shown in Figure 98. The
Lid nut only needs to be slackened, 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, LED PWR1 will
illuminate in the case of the PTP500 Series, LED PWR2 should not.
Figure 98 - PTP LPU test Points
163
12 Wind Loading
12 Wind Loading
12.1
General
Antennas 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 lateral force produced by a single 500 Series bridge (integrated or connectorized model)
at different wind speeds is shown in Table 24 and Table 25.
Largest Surface
Area (sq ft)
Lateral Force (Pound) at wind speed (mph)
80
100
120
160
200
PTP 500 Series
Bridge - Integrated
1.36
36.6
57.1
82.3
146.2
228.5
PTP 500 Series
Bridge Connectorized
1.00
26.9
42
60.5
107.5
168.0
Table 24 - Lateral Force – Imperial
Largest Surface
Area (sq m)
Lateral Force (kg) at wind speed (m/s)
30
40
50
60
70
PTP 500 Series
Bridge - Integrated
0.130
12
22
34
49
66
PTP 500 SeriesConnectorized
0.093
16
24
35
48
Table 25 - Lateral Force – Metric
NOTE: When the connectorized version of 500 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.
164
12 Wind Loading
12.3
Capabilities of the PTP 500 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 500 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
165
13 PTP 500 Series Bridge – Connectorized Model
13 PTP 500 Series Bridge – Connectorized Model
13.1
Scope
This section details the changes and additional features relevant to the connectorized version
of the PTP 500 Series products..
13.2
Product Description
13.2.1 Hardware
The Connectorized PTP 500 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 500 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 99 – Connectorized 500 Series Bridge Outdoor Unit
166
13 PTP 500 Series Bridge – Connectorized Model
13.2.2 Antenna Choices – 5.8 GHz
The integrated antenna has a gain of 23 dBi.
In non-FCC regions antenna choice is not restricted but any region specific EIRP limit must
21
be obeyed by reducing the maximum Transmit power , see Section 5.2 “Licenses and
Region Codes”.
•
In FCC regions external antennas from the list in Section 13.6.3 “Antennas for USA /
Canada – 5.8 GHz” can be used with the Connectorized version of the PTP 500 Series
Bridge. These are approved by the FCC for use with the product and are basically
constrained by the following limits:
•
Single/Dual Polarization Parabolic Dish Antennas – up to 37.7dBi per polarization or
antenna.
In FCC regions when using external antennas – cable loss between the connectorized
version of the PTP 500 Series Bridge and the antenna ports must not be less than 1.2dB.
When operating PTP58500 with a 5MHz channel bandwidth and with dish antennas larger
than 4 foot diameter, the maximum operating power must be reduced to 24dBm (3dB
reduction) to ensure meeting FCC requirements.
13.2.3 Suggested Antenna Choices – 5.4 GHz
The integrated antenna has a gain of 23 dBi.
External antennas from the list in Section 13.6.4 “Suggested Antennas - 5.4 GHz” can be
used with the Connectorized version of the PTP 500 Series Bridge. These are approved by
the FCC for use with the product and are basically constrained by the following limit:
•
Single/Dual Polarization Parabolic Dish Antennas – up to 34.9dBi per polarization or
antenna.
However, the Maximum Transmit Power must be reduced to avoid exceeding the EIRP
21
limits .
In FCC regions when using external antennas – cable loss between the connectorized
version of the 500 Series Bridge and the antenna ports must not be less than 1.2dB
21
Maximum Transmit Power Allowed = EIRP Limit – Antenna Gain + Cable Losses; set the power to the 1dB
value lower than the actual value calculated.
167
13 PTP 500 Series Bridge – Connectorized Model
13.3
Software/Features
The connectorized variant operates in the same way as the basic 500 Series and is released
initially with the feature set to the Connectorized PTP 500 Series variant. The areas where
the functionality is modified are:
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 500 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 100 - Connectorized 500 Series bridge Status Page
168
13 PTP 500 Series Bridge – Connectorized Model
13.3.2 Configuration Pages
The amended Configuration web page is shown below as Figure 101. Please refer to Section
8.3.4 “Install Pages” for the definitions of the parameters Antenna Gain, Cable Loss and
EIRP.
Figure 101 - Connectorized 500 Series bridge ‘System Configuration’ Page
169
13 PTP 500 Series Bridge – Connectorized Model
13.3.3 Installation Pages
The installer is prompted to enter the Antenna Gain and Cable Loss (Connectorized PTP 500
Series Bridge to antenna) at each end of the link. The Installation Pages are shown as Figure
102 to Figure 104.
Figure 102 - Connectorized PTP 500 Series Bridge
‘Installation Wizard’ Page
Antenna Gain: Gain of the antenna you are connecting to the unit, see table in Section
13.6.4 “Suggested Antennas - 5.4 GHz”
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.
170
13 PTP 500 Series Bridge – Connectorized Model
Spectrum Management Control: Is used to configure the 500 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 103 - Connectorized 500 Series bridge ‘Confirm Installation’ Page
171
13 PTP 500 Series Bridge – Connectorized Model
EIRP: 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 104 - Connectorized 500 Series bridge ‘Disarm Installation’ Page
13.4
Deployment Considerations
The majority of radio links can be successfully deployed with the 500 Series. It should only be
necessary to use external antennas where the Link Estimator 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.
172
13 PTP 500 Series Bridge – Connectorized Model
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.
Dual polarization antennas (with a gain greater than the integrated antenna) are currently only
available in parabolic dish form.
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
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.
See Section 5.2 “Licenses and Region Codes” for any EIRP restrictions that may apply in
your region.
In some regions, operation of the PTP 54500 products is constrained by an EIRP limit. The
normal constraint is that the EIRP does not exceed 30 dBm (36 dBm for PTP 58500) for radio
signals with a bandwidth of >=20 MHz. As the PTP 54500 operating bandwidth is
approximately 15 MHz, then the limit is 34.8 dBm EIRP (28.8 dBm for PTP 58500).
When operating with external antennas, the installer/operator has to set the maximum
transmit power to ensure that the EIRP limit is not exceeded. The Set_Max_Transmit_Power
is calculated as below:
Set_Max_Transmit_Power = [Max_Transmit_Power] rounded down to nearest lower dB.
173
13 PTP 500 Series Bridge – Connectorized Model
13.6.1 Antenna Choice (FCC and Industry Canada Regions Only)
The antennas which can be deployed with the Connectorized 500 Series Bridge are shown in
Section 13.6.3 “Antennas for USA / Canada – 5.8 GHz” and Section 13.6.4 “Suggested
Antennas - 5.4 GHz”.
For FCC and Industry Canada, the PTP500 Series Bridge has been designated to operate
with the antennas listed in Section 13.6.3 “Antennas for USA / Canada – 5.8 GHz” and
Section 13.6.4 “Suggested Antennas - 5.4 GHz”, and having a maximum gain of 37.7 dB
(34.9 dB for PTP 54500 product variant). Antennas not included in these tables or having a
gain greater than 37.7 dB (34.9 dB for PTP 54500 product variant) are strictly prohibited for
use with this device. The required antenna impedance is 50 ohms.
13.6.2 Cable Losses (FCC Regions Only)
The FCC approval for the product is based on tests with a cable loss between the units of
approximately 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).
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
Table 26 - Cable Losses per Length
174
13 PTP 500 Series Bridge – Connectorized Model
13.6.3 Antennas for USA / Canada – 5.8 GHz
Gain
(dBi)
Flat
Plate
Parabolic
Dish
Manufacturer
Antenna Type
Andrew
Andrew 2-foot Parabolic, P2F-52
(29.4dBi)
29.4
Andrew
Andrew 2-foot Dual-Pol Parabolic,
PX2F-52 (29.4dBi)
29.4
Andrew
Andrew 3-foot Parabolic, P3F-52
(33.4dBi)
33.4
Andrew
Andrew 3-foot Dual-Pol Parabolic,
PX3F-52 (33.4dBi)
33.4
Andrew
Andrew 4-foot Parabolic, P4F-52
(34.9dBi)
34.9
Andrew
Andrew 4-foot Dual-Pol Parabolic,
PX4F-52 (34.9dBi)
34.9
Andrew
Andrew 6-foot Parabolic, P6F-52
(37.6dBi)
37.6
Andrew
Andrew 6-foot Dual-Pol Parabolic,
PX6F-52 (37.6dBi)
37.6
Gabriel
Gabriel 2-foot High Performance
QuickFire Parabolic, HQF2-52-N
28.2
Gabriel
Gabriel 4-foot High Performance
QuickFire Parabolic, HQF4-52-N
34.4
Gabriel
Gabriel 6-foot High Performance
QuickFire Parabolic, HQF6-52-N
37.4
Gabriel
Gabriel 2-foot High Performance Dual
QuickFire Parabolic, HQFD2-52-N
28.1
Gabriel
Gabriel 4-foot High Performance Dual
QuickFire Parabolic, HQFD4-52-N
34.3
Gabriel
Gabriel 6-foot High Performance Dual
QuickFire Parabolic, HQFD6-52-N
37.3
Gabriel
Gabriel 2-foot Standard QuickFire
Parabolic,
QF2-52-N
28.5
Gabriel
Gabriel 2-foot Standard QuickFire
Parabolic,
QF2-52-N-RK
28.5
Gabriel
Gabriel 2.5-foot Standard QuickFire
Parabolic, QF2.5-52-N
31.2
175
13 PTP 500 Series Bridge – Connectorized Model
Gain
(dBi)
Flat
Plate
Parabolic
Dish
Manufacturer
Antenna Type
Gabriel
Gabriel 4-foot Standard QuickFire
Parabolic,
QF4-52-N
34.8
Gabriel
Gabriel 4-foot Standard QuickFire
Parabolic,
QF4-52-N-RK
34.8
Gabriel
Gabriel 6-foot Standard QuickFire
Parabolic,
QF6-52-N
37.7
Gabriel
Gabriel 2-foot Standard Dual QuickFire
Parabolic, QFD2-52-N
28.4
Gabriel
Gabriel 2.5-foot Standard Dual
QuickFire Parabolic, QFD2.5-52-N
31.1
Gabriel
Gabriel 2-foot Standard Dual QuickFire
Parabolic, QFD2-52-N-RK
28.4
Gabriel
Gabriel 4-foot Standard Dual QuickFire
Parabolic, QFD4-52-N
34.7
Gabriel
Gabriel 4-foot Standard Dual QuickFire
Parabolic, QFD4-52-N-RK
34.7
Gabriel
Gabriel 6-foot Standard Dual QuickFire
Parabolic, QFD6-52-N
37.7
RadioWaves
Radio Waves 2-foot Dual-Pol Parabolic,
SPD2-5.2 (28.1dBi)
28.1
RadioWaves
Radio Waves 2-foot Parabolic, SP2-5.2
(29.0dBi)
29
RadioWaves
Radio Waves 3-foot Dual-Pol Parabolic,
SPD3-5.2 (31.1dBi)
31.1
RadioWaves
Radio Waves 3-foot Parabolic, SP3-5.2
(31.4dBi)
31.4
RadioWaves
Radio Waves 4-foot Dual-Pol Parabolic,
SPD4-5.2 (34.4dBi)
34.4
RadioWaves
Radio Waves 4-foot Parabolic, SP4-5.2
(34.8dBi)
34.8
RadioWaves
Radio Waves 6-foot Dual-Pol Parabolic,
SPD6-5.2 (37.5dBi)
37.5
RadioWaves
Radio Waves 6-foot Parabolic, SP6-5.2
(37.7dBi)
37.7
RadioWaves
Radio Waves 2-foot Parabolic, SP2-2/5
(28.3dBi)
28.3
RadioWaves
Radio Waves 3-foot Parabolic, SP3-2/5
(31.4dBi)
31.4
176
13 PTP 500 Series Bridge – Connectorized Model
Gain
(dBi)
Flat
Plate
Parabolic
Dish
Manufacturer
Antenna Type
RadioWaves
Radio Waves 4-foot Parabolic, SP4-2/5
(34.6dBi)
34.6
RadioWaves
Radio Waves 6-foot Parabolic, SP6-2/5
(37.7dBi)
37.7
RFS
RFS 2-foot Parabolic, SPF2-52AN or
SPFX2-52AN (27.9dBi)
27.9
RFS
RFS 3-foot Parabolic, SPF3-52AN or
SPFX3-52AN(31.4dBi)
31.4
RFS
RFS 4-foot Parabolic, SPF4-52AN or
SPFX4-52AN(33.9dBi)
33.9
RFS
RFS 6-foot Parabolic, SPF6-52AN or
SPFX6-52AN (37.4dBi)
37.4
RFS
RFS 2-foot HP Parabolic, SDF2-52AN
or SDFX2-52AN (31.4dBi)
31.4
RFS
RFS 4-foot HP Parabolic, SDF4-52AN
or SDFX4-52AN (33.9dBi)
33.9
RFS
RFS 6-foot HP Parabolic, SDF6-52AN
or SDFX6-52AN (37.4dBi)
37.4
StellaDoradus
StellaDoradus 45 inch Parabolic
Antenna, 58PSD113
33.8
Table 27 - Allowed Antennas for Deployment in USA/Canada – 5.8 GHz
177
13 PTP 500 Series Bridge – Connectorized Model
13.6.4 Suggested Antennas - 5.4 GHz
Manufacturer
Antenna Type
Gain
(dBi)
Parabolic
Dish
Andrew
Andrew 2-foot Parabolic, P2F-52 (29.4dBi)
29.4
Andrew
Andrew 2-foot Dual-Pol Parabolic, PX2F-52
(29.4dBi)
29.4
Andrew
Andrew 3-foot Parabolic, P3F-52 (33.4dBi)
33.4
Andrew
Andrew 3-foot Dual-Pol Parabolic, PX3F-52
(33.4dBi)
33.4
Andrew
Andrew 4-foot Parabolic, P4F-52 (34.9dBi)
34.9
Andrew
Andrew 4-foot Dual-Pol Parabolic, PX4F-52
(34.9dBi)
34.9
Gabriel
Gabriel 2-foot High Performance QuickFire
Parabolic, HQF2-52-N
28.2
Gabriel
Gabriel 4-foot High Performance QuickFire
Parabolic, HQF4-52-N
34.4
Gabriel
Gabriel 2-foot High Performance Dual
QuickFire Parabolic, HQFD2-52-N
28.1
Gabriel
Gabriel 4-foot High Performance Dual
QuickFire Parabolic, HQFD4-52-N
34.3
Gabriel
Gabriel 2-foot Standard QuickFire
Parabolic,
QF2-52-N
28.5
Gabriel
Gabriel 2-foot Standard QuickFire
Parabolic,
QF2-52-N-RK
28.5
Gabriel
Gabriel 2.5-foot Standard QuickFire
Parabolic, QF2.5-52-N
31.2
Gabriel
Gabriel 4-foot Standard QuickFire
Parabolic,
QF4-52-N
34.8
Gabriel
Gabriel 4-foot Standard QuickFire
Parabolic,
QF4-52-N-RK
34.8
Gabriel
Gabriel 2-foot Standard Dual QuickFire
Parabolic, QFD2-52-N
28.4
Gabriel
Gabriel 2.5-foot Standard Dual QuickFire
Parabolic, QFD2.5-52-N
31.1
Gabriel
Gabriel 2-foot Standard Dual QuickFire
Parabolic, QFD2-52-N-RK
28.4
Gabriel
Gabriel 4-foot Standard Dual QuickFire
Parabolic, QFD4-52-N
34.7
178
13 PTP 500 Series Bridge – Connectorized Model
Gain
(dBi)
Parabolic
Dish
Gabriel 4-foot Standard Dual QuickFire
Parabolic, QFD4-52-N-RK
34.7
RadioWaves
Radio Waves 2-foot Dual-Pol Parabolic,
SPD2-5.2 (28.1dBi)
28.1
RadioWaves
Radio Waves 2-foot Parabolic, SP2-5.2
(29.0dBi)
29
RadioWaves
Radio Waves 3-foot Dual-Pol Parabolic,
SPD3-5.2 (31.1dBi)
31.1
RadioWaves
Radio Waves 3-foot Parabolic, SP3-5.2
(31.4dBi)
31.4
RadioWaves
Radio Waves 4-foot Dual-Pol Parabolic,
SPD4-5.2 (34.4dBi)
34.4
RadioWaves
Radio Waves 4-foot Parabolic, SP4-5.2
(34.8dBi)
34.8
RadioWaves
Radio Waves 2-foot Parabolic, SP2-2/5
(28.3dBi)
28.3
RadioWaves
Radio Waves 3-foot Parabolic, SP3-2/5
(31.4dBi)
31.4
RadioWaves
Radio Waves 4-foot Parabolic, SP4-2/5
(34.6dBi)
34.6
RFS
RFS 2-foot Parabolic, SPF2-52AN or
SPFX2-52AN (27.9dBi)
27.9
RFS
RFS 3-foot Parabolic, SPF3-52AN or
SPFX3-52AN(31.4dBi)
31.4
RFS
RFS 4-foot Parabolic, SPF4-52AN or
SPFX4-52AN(33.9dBi)
33.9
RFS
RFS 2-foot HP Parabolic, SDF2-52AN or
SDFX2-52AN (31.4dBi)
31.4
RFS
RFS 4-foot HP Parabolic, SDF4-52AN or
SDFX4-52AN (33.9dBi)
33.9
Manufacturer
Antenna Type
Gabriel
Table 28 - Suggested Antennas – 5.4 GHz
179
13 PTP 500 Series Bridge – Connectorized Model
13.7
Installation
The section covers the generic installation instructions for the Connectorized versions of the
PTP 500 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 “Antennas for USA / Canada – 5.8 GHz” and Section 13.6.4 “Suggested
Antennas - 5.4 GHz” show a wide variety of antennas that can be used with the
Connectorized PTP 500 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 500 Series bridge end of the antenna cables
are N-Type Male.
The connectors required at the antenna end of the antenna cables are dependant on the
antenna type chosen.
13.7.3 Tools
The tools required for mounting a Connectorized 500 Series bridge unit are the same as
those required for an Integrated 500 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.
180
13 PTP 500 Series Bridge – Connectorized Model
13.7.4 Miscellaneous supplies
The following miscellaneous supplies will be required:
•
Cable ties, cable cleats – for securing cables
•
Self-amalgamating tape – to weatherproof the RF connectors
•
PVC tape – for additional protection of the RF connectors and securing cables
13.7.5 Mounting the Connectorized 500 Series Bridge
A Connectorized 500 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 PTP 500 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 500 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
“Antennas for USA / Canada – 5.8 GHz”.
When using separate antennas the Connectorized 500 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 500 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.7.7 Alignment Process
When aligning antennas deployed with a Connectorized 500 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.
181
13 PTP 500 Series Bridge – Connectorized Model
Tip: 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 500
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 500 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 500 Series
bridge unit.
Step 6: Connect the Connectorized 500 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 500 Series Bridge ODUs”.
Step 8: Connect the other antenna to the Connectorized 500 Series bridge.
Step 9: Disconnect the cable to the already aligned antenna.
Step 10: Align the second antenna using the tones as described in Section 7.7.11 “Aligning
the PTP 500 Series Bridge ODUs”.
Step 11: Re-connect the second antenna to the Connectorized 500 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.
182
13 PTP 500 Series Bridge – Connectorized Model
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
500 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.
183
13 PTP 500 Series Bridge – Connectorized Model
13.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 105 - 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 106 shows this
diagrammatically for the 500 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 106 - Weatherproofing the Antenna Connections
184
13 PTP 500 Series Bridge – Connectorized Model
13.8
Additional Lightning Protection
The following guidelines should be applied in addition to those described in Section 11
”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 107.
Figure 107- Additional Grounding When Using Connectorized Units
185
13 PTP 500 Series Bridge – Connectorized Model
13.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 108.
Figure 108 - 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 109.
Figure 109 - Polyphaser Assembly
186
14 Data Rate Calculations
14 Data Rate Calculations
To aid the calculation of data rate throughput (end to end ethernet throughput assuming 1500
octet ethernet frames), the following plots of throughput verses link range have been
produced for all the PTP 500 Series modulation modes, assuming the units are connected
using 100 Mbps Ethernet. Please note that only 15 MHz channel bandwidth has been
considered and the plots are the same for IP or TDM modes (High priority traffic), although
there is a small difference between the two modes' rates 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.
Aggregate data rate capacity can be calculated using four key system parameters:
•
Receive modulation mode
•
Transmit modulation mode
•
Range Between the two wireless units
•
Wireless link mode (IP or TDM) There are more than this
Using these parameters the Receive and Transmit data rates can be looked up using the
plots Figure 110 through Figure 122.
Need a way of adding data for different bandwidths and TDD structures
Figure 110 - BPSK 0.50 Single Payload
187
14 Data Rate Calculations
Figure 111 - QPSK 0.50 Single Payload
Figure 112 - QPSK 0.75 Single Payload
188
14 Data Rate Calculations
Figure 113 - 16 QAM 0.50 Single Payload
Figure 114 - 16 QAM 0.75 Single Payload
189
14 Data Rate Calculations
Figure 115 - 64 QAM 0.67 Single Payload
Figure 116 - 64 QAM 0.83 Single Payload
190
14 Data Rate Calculations
Figure 117 – QPSK 0.50 Dual Payload
Figure 118 - QPSK 0.75 Dual Payload
191
14 Data Rate Calculations
Figure 119 - 16 QAM 0.50 Dual Payload
Figure 120 - 16 QAM 0.75 Dual Payload
192
14 Data Rate Calculations
Figure 121 - 64 QAM 0.67 Dual Payload
Figure 122 - 64 QAM 0.83 Dual Payload
193
15 AES Encryption Upgrade
15 AES Encryption Upgrade
The Motorola PTP 500 Series bridges support link encryption using the NIST approved
Advanced Encryption Standard, HFIPS-197 H. This standard specifies AES (Rijndael) as a
UT
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 500 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:
•
128-bit
•
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.
15.1
Configuring Link Encryption
After purchasing AES encryption for the PTP 500 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 500 Series bridge.
15.1.1 License Keys
The first step when configuring link encryption is to enter the new license keys in both 500
Series wireless units.
Figure 123 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 500 Series system administration
pages then please contact your designated system administrator.
194
15 AES Encryption Upgrade
Figure 123 – AES Software License Key Data Entry
Configuring link encryption will necessitate a 500 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)
4. 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.
195
15 AES Encryption Upgrade
15.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 124 be used to configure AES link encryption.
Figure 124 – AES Configuration Data Entry Page
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.
196
15 AES Encryption Upgrade
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 125). 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 125 - Configuration Reboot Screen
15.2
Wireless Link Encryption FAQ
15.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.
15.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.
15.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.
197
16 Legal and Regulatory Notices
16 Legal and Regulatory Notices
16.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.
16.2
National and Regional Regulatory Notices – PTP 58500 variant
16.2.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.
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:
•
Increase the separation between the affected equipment and the unit;
198
16 Legal and Regulatory Notices
•
Connect the affected equipment to a power outlet on a different circuit from that which the
receiver is connected to;
•
Consult the dealer and/or experienced radio/TV technician for help.
•
FCC 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.
16.2.2 European Union Notification
The PTP 58500 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.
This equipment is marked to show compliance with the European R&TTE directive 1999/5/EC.
199
16 Legal and Regulatory Notices
The relevant Declaration of Conformity can be found at www.motorola.com/ptp. Is this true??
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.
16.2.3 UK Notification
The PTP 58500 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 cochannel 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.
NOTE: Norway regulation is FOR2007-04-20 Nr 439 regarding border PFD limit.
200
16 Legal and Regulatory Notices
16.3
National and Regional Regulatory Notices – PTP 54500 Variant
16.3.1 FCC and Industry Canada (IC) Notification
This device complies with FCC Part 15 for the USA and 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. 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 5470 – 5725 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:
•
Increase the separation between the affected equipment and the unit;
•
Connect the affected equipment to a power outlet on a different circuit from that which the
receiver is connected to;
•
Consult the dealer and/or experienced radio/TV technician for help.
•
FCC and Industry Canada Certification Numbers are listed below:
201
16 Legal and Regulatory Notices
16.3.2 European Union Notification
The PTP 54500 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.
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.
This equipment is marked to show compliance with the European R&TTE directive
1999/5/EC.
We need a new label with the same NB number as for PTP58500 as we have had to use a
NB because of testing partially to V1.5.1
The relevant Declaration of Conformity can be found at www.motorola.com
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.
202
16 Legal and Regulatory Notices
16.4
Exposure
See Section 2 “Avoiding Hazards”.
203
16 Legal and Regulatory Notices
16.5
Legal Notices
16.5.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.
16.5.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.
16.5.1.2 Grant of License
Motorola, Inc. (“Motorola”) grants you (“Licensee” or “you”) a personal, nonexclusive, nontransferable 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.
204
16 Legal and Regulatory Notices
16.5.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.
1. 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.
2. 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.
3. You may use the Software and Documentation, provided that the use is in conformance
with the terms set forth in this Agreement.
4. 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.
Documentation is in printed form, it may not be copied.
If the
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.
5. 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.
205
16 Legal and Regulatory Notices
16.5.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.
16.5.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.
206
16 Legal and Regulatory Notices
1. 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.
16.5.1.6 Right to Use Motorola’s Name
Except as required in 16.5.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.
16.5.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.
16.5.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/.
1. 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.
16.5.1.9 Maintenance
Except as provided above, Motorola is not responsible for maintenance or field service of the
Software under this Agreement.
207
16 Legal and Regulatory Notices
16.5.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.
16.5.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.
208
16 Legal and Regulatory Notices
16.5.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.
16.5.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.
16.5.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.
16.5.1.15 Assignment
This agreement may not be assigned by you without Motorola’s prior written consent.
209
16 Legal and Regulatory Notices
16.5.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.
16.5.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.
16.5.1.18 Third Party Software
The software may contain one or more items of Third-Party Software supplied by other thirdparty 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.
210
16 Legal and Regulatory Notices
1. UCD 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.
2. 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
211
16 Legal and Regulatory Notices
acknowledgment in the product documentation would be appreciated but is not
required.
Altered 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.
3. 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:
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.
Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.
This notice may not be removed or altered from any source distribution.
Jean-loup Gailly jloup@gzip.org
Mark Adler madler@alumni.caltech.edu
212
16 Legal and Regulatory Notices
16.5.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.
16.5.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.
213
17 Specifications
17 Specifications
17.1
System Specifications
17.1.1 Wireless PTP 54500 Variant
Radio Technology
Specification
RF Band
5.470-5.725GHz
Channel Selection
By intelligent Dynamic Frequency Selection (i-DFS) or
manual intervention.
Automatic detection on start-up and continual adaptation to
avoid interference.
Channel size
5, 10 and 15 MHz
Transmit Power
Varies with modulation mode and settings from -18 dBm to
27 dBm.
Modulation
Dynamic; adapting between BPSK single and 64 QAM.
Antenna Type
Integrated: Flat plate antenna. Connectorized: Approved to
operate with a selection of separately-purchased single and
dual polar antennas through 2xN-type connectors (check
local regulations prior to purchase).
Antenna Gain
23 dBi typical
Antenna Beamwidth
8 Degrees
Receiver Sensitivity
Adaptive, varying between -94 dBm and -69 dBm.
Duplex Scheme
Symmetric Fixed TDD, Same frequency Tx/Rx.
Range
155 miles (250km)
Security and Encryption
Proprietary scrambling mechanism. Optional FIPS-197
compliant 128- and 256-bit AES Encryption.
Weather Sensitivity
Sensitivity at higher modes may be reduced during high
winds through trees due to Adaptive Modulation Threshold
changes.
Error Correction
FEC
214
17 Specifications
17.1.2 Wireless PTP 58500 Variant
Radio Technology
Specification
RF Band
5.725-5.875GHz
By intelligent Dynamic Frequency Selection (i-DFS) or
manual intervention
Channel Selection
Automatic detection on start-up and continual adaptation to
avoid interference.
Channel size
5, 10 and 15 MHz
Transmit Power
Varies with modulation mode and settings from -18 dBm to
27 dBm.
Modulation
Dynamic; adapting between BPSK single and 64 QAM.
Antenna Type
Integrated: Flat plate antenna. Connectorized: Approved to
operate with a selection of separately-purchased single and
dual polar antennas through 2xN-type connectors (check
local regulations prior to purchase).
Antenna Gain
23 dBi typical
Antenna Beamwidth
8 Degrees
Receiver Sensitivity
Adaptive, varying between -94 dBm and -69 dBm.
Duplex Scheme
Symmetric Fixed TDD, same or split frequency Tx/Rx where
regulations permit.
Range
155 miles (250km)
Security and Encryption
Proprietary scrambling mechanism. Optional FIPS-197
compliant 128- and 256-bit AES Encryption.
Weather Sensitivity
Sensitivity at higher modes may be reduced during high
winds through trees due to Adaptive Modulation Threshold
changes
Error Correction
FEC
215
17 Specifications
17.1.3 Management
Management
Specification
Status Indication
Power status
Ethernet Link Status
Data activity
Installation
Web server and browser for setup.
Audio tone feedback during installation , plus
graphical installation tool suitable for laptop and
PDA computing devices.
Web server for confirmation.
Radio Performance and Management
Via web server and browser, SNMP
Alarms
Via configurable email alerts, SNMP
System Management
Web or SNMP v1/v2c using MIBII, WiMAX MIB,
and a proprietary PTP MIB; Canopy Prizm.
Lightning protection
Built into the ODU; an external PTP Lightning
Protection Unit (PTP-LPU) end device is required
near the base of the tower or wall at the cable
entrance point leading to the network.
17.1.4 Ethernet Bridging
Ethernet Bridging
Specification
Protocol
IEEE802.3
QoS
IEEE 802.1p (eight levels), IEEE 802.1Q, IEEE
802.1ad.
Interface
10/100BaseT (RJ-45), Supports MDI/MDIX Auto
Crossover
Data Rates
Dynamically variable up to 105 Mbps at the
Ethernet (aggregate) for the Full version of the
product and up to 52 Mbps for the Lite version.
See Section 14 “Data Rate Calculations”.
Maximum Packet Rate
50000 frames/s
Maximum Frame Lifetime
1160 ms
Maximum Ethernet Frame Size
2000 bytes
216
17 Specifications
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.
17.1.5 Physical
Integrated
Specification
Dimensions
Width 14.5” (370mm), Height 14.5” (370mm), Depth 3.75” (95mm)
Weight
11.8 lbs (5.35 Kg) including bracket
Connectorized
Specification
Dimensions
Width 12.2” (309mm), Height 12.2” (309mm), Depth 4.01” (105mm)
Weight
10.4 lbs (4.7 Kg) including bracket
17.1.6 Powering
17.2
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
Safety Compliance
Region
Specification
USA
UL 60950
Canada
CSA C22.2 No.60950
International
CB certified & certificate to IEC 60950
217
17 Specifications
17.3
7.3
EMC Emissions Compliance
17.3.1 PTP 54500 Variant
Region
Specification
USA
CFR 47 Part 15 Class B
Canada
CSA Std C108.8, 1993 Class B
Europe
EN55022 CISPR 22
17.3.2 PTP 58500 Variant
Region
Specification
USA
CFR 47 Part 15 Class B
Canada
CSA Std C108.8, 1993 Class B
Europe
EN55022 CISPR 22
218
17 Specifications
17.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 performed 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 unmodulated.
219
17 Specifications
17.5
Radio Certifications
17.5.1 PTP 54500 Variant
Region
Specification (Type Approvals)
EU
EN301 893 V1.4.1
USA
FCC Part 15 E
CANADA
RSS 210 Issue 7, Annex 9
17.5.2 PTP 58500 Variant
17.6
Region
Specification (Type Approvals)
USA
FCC Part 15.247
CANADA
RSS 210 Issue 7, Annex 8
UK
IR 2007
Eire
ComReg 02/71R1
Germany
Order No 47/2007
Environmental Specifications
Category
Specification
ODU: -40°F (-40°C) to 140°F (+60°C)
Temperature
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
220
17 Specifications
17.7
Waterproof
IP65 (ODU), IP53 (PIDU Plus)
UV Exposure
10 year operational life (UL746C test evidence)
System Connections
17.7.1 PIDU Plus to ODU and ODU to Network Equipment Connections
Figure 126 - Cable Connection Diagram (T568B Color Coding)
221
18 FAQs
18 FAQs
Can I source and use my own PoE adaptor with the 500 Series bridge? No. The 500
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.
What is Multiple-Input Multiple-Output (MIMO)? The 500 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 500 Series bridge ? There are many special features builtin to the hardware of the 500 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 500 Series bridge has a built-in web server for advanced management
capabilities including detailed radio signal diagnosis.
In which frequency bands does the 500 Series bridge operate? The Motorola point-topoint 500 Series bridge operates in the unlicensed bands 5.4 GHz (ETSI Band B) and 5.8
GHz (ETSI Band C and FCC ISM band). This means that no license is required to operate the
PTP 500 Series bridge.
Why does the 500 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 500 Series bridge an 802.11a device? No, although similar, the 500 Series bridge
uses different encoding and radio transmission systems from 802.11a. In areas where
802.11a systems are operating, the 500 Series bridge will detect the 802.11a radio signals
and choose a clear channel away from any interference.
222
18 FAQs
How much power does the 500 Series bridge transmit? At all times the 500 Series bridge
operates within country / region specific regulations for radio power emissions. In addition, the
500 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 500 Series Bridge avoid interference from other devices nearby? At
initialization, the 500 Series bridge monitors the available frequency channels to find a
channel that is clear of interference. In operation 500 Series bridge continuously monitors the
spectrum to ensure it is operating on the cleanest channel.
How does the 500 Series bridge integrate into my data network? The 500 Series bridge
acts 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 500 Series bridge
forwards 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 500 Series bridge provide security for data traffic? The 500 Series bridge
has 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.
223
19 Glossary
19 Glossary
AES
Advanced Encryption Standard
MIMO
Multiple Input Multiple Output
ARP
Address Resolution Protocol
NIST
National Institute of Standards
and Technology
ARQ
Automatic Repeat reQuest
NLOS
non-Line-of-Sight
BPSK
Binary Phase Shift Keying
ODU
Outdoor Unit
OFDM
Orthogonal Frequency Division
Multiplex
PC
IBM Compatible Personal
Computer
DC
DFS
Direct Current
Dynamic Frequency Selection
EIRP
Equivalent Isotropically Radiated
Power
PIDU +
EMD
Electric Magnetic Discharge
PING
ETSI
European Telecommunications
Standards Institute
PoE
FAQ
Frequently Asked Question
PSU
FCC
Federal Communications
Commission
PTP
GPS
HTTP
ID
Global Positioning System
Hypertext Transfer Protocol
Identity
Power Indoor Unit Plus
Packet Internet Groper
Power over Ethernet
Power Supply Unit
Point-to-Point
QAM
Quadrature Amplitude
Modulation
RAM
Random Access Memory
RTTT
Road Transport and Traffic
Telematics
IEEE
Institute of Electrical and
Electronic Engineers
STC
i-DFS
Intelligent Dynamic Frequency
Selection
STP
Shielded Twisted Pair
IP
Internet Protocol
TCP
Transmission Control Protocol
IQ
In phase / Quadrature
TPC
Transmit Power Control
ISM
Industrial Scientific and Medical
URL
Universal Resource Location
ITU
International
Telecommunications Union
USA
United States of America
LAN
Local Area Network
UTP
Unshielded Twisted Pair
LED
Light Emitting Diode
UV
Ultraviolet
LPU
Lightning Protection Unit
VLAN
Virtual Local Area Network
MAC
Medium Access Control Layer
MDI
Medium Dependent Interface
MDIX
Medium Dependent Interface Crossover
224
Space Time Coding
20 Index
20 Index
Alarm
Alignment
73
MIB
65, 173
Mounting
125
32, 54, 62
antenna
159
Antenna
159, 162, 166, 172, 174
Password
132
35
Path Loss
46
Architecture
Cable Loss
Cables
162, 166
39, 122
Channels
112, 117, 118
Compliance
Planning
60, 172, 175
channels
Clock
Networking
133
radio
2, 4
Reboot
209, 210, 211
Configuration33, 81, 99, 100, 102, 116, 136,
139, 161
36, 45
Properties
Radio
129
43
145, 212
134, 136, 141
Recovery
135
Regulatory
165
Repair
24
Connecting
56, 58, 59, 61, 62, 176, 213
Connectors
172
Restore
89
Deployment
164
Safety
23
Save
89
Reset
136, 138
diagnostics
77, 131
Diagnostics
131
Service
24
Disarm
106
SMTP
128
43
SNMP
125, 127
EIRP
164
SNTP
128
Environmental
212
Software
136, 160
Spectrum Management
112, 163
Distance
Ethernet
25, 84, 94, 143
Fault Finding
142
Statistics
Glossary
216
Status
Grounding
60
Installation
98, 149, 162, 172, 175
IP address
64
Licence Key
Lightning
Support
132
93
75, 160
53
Surge
32, 60
Throughput
48, 50
Tools
53, 172
32, 44, 147
Upgrade
109, 136
Link Budget
165
Warning
73
MAC Address
136
Wind
Management
33, 124
225
156
20 Index
Unit A1, Linhay Business Park
Eastern Road, Ashburton
Devon, TQ 13 7UP, UK
Telephone Support: +1 877 515-0400 (Worldwide)
+44 808 234 4640 (UK)
www.motorola.com/ptp
226
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.

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.4
Linearized                      : No
Tagged PDF                      : Yes
XMP Toolkit                     : Adobe XMP Core 4.0-c316 44.253921, Sun Oct 01 2006 17:14:39
Producer                        : Acrobat Distiller 8.1.0 (Windows)
Company                         : Motorola Inc.
Source Modified                 : D:20080815165841
Creator Tool                    : Acrobat PDFMaker 8.1 for Word
Modify Date                     : 2008:08:15 18:24:25+01:00
Create Date                     : 2008:08:15 18:06:06+01:00
Metadata Date                   : 2008:08:15 18:24:25+01:00
Document ID                     : uuid:5be48ee8-5a3a-49ba-a14b-f4a8bd7b59e3
Instance ID                     : uuid:13d56d32-2d2e-4c20-84b7-ed14498629c0
Subject                         : 7
Format                          : application/pdf
Creator                         : Bill Trezise
Title                           : PTP 500 Series User Guide
Page Count                      : 228
Page Layout                     : OneColumn
Author                          : Bill Trezise

EXIF Metadata provided by EXIF.tools

Cambium Networks 58500 Wireless Ethernet Bridge User Manual PTP 500 Series User Guide

Cambium Networks Limited Wireless Ethernet Bridge PTP 500 Series User Guide

Contents

Manual

FCC ID Filing: QWP58500

Navigation menu

Namespaces

Views

Navigation