Motorola MOTOWI 4, PTP 500, PTP 300 User Manual

Download

Page 1

PTP 500 Series

User Guide

phn-1115-000v001

Page 2

MOTOROLA, Inc.

Point-to-Point Wireless Bridges – PTP 500 Series

Software Release PTP 500-01-xx

System User Manual

March 7th, 2008

Ref: PHN-1115-00.01

This document is the conﬁdential 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. rReg. U.S. Pat & Tm. Oﬃce. PTP 500 is a trademark of Motorola, Inc. All other product or service names are the property of their respective owners.

http://www.motorola.com/ptp

Compliance

General

Changes or modiﬁcations 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 is 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.

Page 3

The system has been tested for compliance to both US (FCC) and European (ETSI) speciﬁcations. It has been shown to comply with the limits for emitted spurious radiation for a Class B digital device1, 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 oﬀ 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 aﬀected equipment and ODU.

• Connect the ODU/PIDU into a power outlet on a circuit diﬀerent 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-speciﬁc License Keys.

The following examples show how the regulatory limits apply in some speciﬁc 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 fulﬁlled 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.

The system has been tested for compliance to both US (FCC) and European (ETSI) speciﬁcations. It has been shown to comply with the limits for emitted spurious radiation for a Class B digital device, pursuant to Part 15 of the FCC Rules in the USA and appropriate European ENs. These limits have been designed to provide reasonable protection against harmful interference. However the equipment can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to other radio communications. There is no guarantee that interference will not occur in a particular installation.

Class B Digital Device, A digital device that is marketed for use in a residential environment notwithstanding use in commercial, business and industrial environments.

Page 4

Regulations applicable to 5.4GHz PTP 500 Series Bridge 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 (30dBm or 1W EIRP with Radar Detection)

ETSI Under ETSI Regulations, operation of this product is only allowed with a

License Key for Region 24 (30dBm or 1W EIRP with Radar Detection)

Australia, Canada Under Australian Communications Authorities and Industry Canada

Regulations, operation of this product is only allowed with a License Key for Region 13 (30dBm or 1W EIRP with Radar Detection and barring of the band 5600-5650MHz)

Thailand Operation of this product is only allowed with a License Key for Region

20 (30 dBm or 1W EIRP)

Korea Operation of this product is only allowed with a License Key for Region

21 (28 dBm EIRP (15 MHz))

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, speciﬁc local regulations may apply. It is the responsibility of the installer/user to check that the equipment as deployed meets local regulatory requirements.

Page 5

Regulations applicable to 5.8GHz PTP 500 Series Bridge variant

Examples of Regulatory Limits at 5.8GHz

USA / Canada / Taiwan / Brazil Equipment can be operated in any mode, best results will

be obtained using Region 1 settings

China Operation of this product is only allowed with a License

Key for Region 2 (33 dBm or 2W EIRP)

Australia Operation of this product is only allowed with a License

Key for Region 3 (36 dBm or 4W EIRP)

Hong Kong Under Hong Kong Regulations, operation of this product is

only allowed with a License Key for Region 3 (36 dBm or 4W EIRP)

UK Under UK Regulations, operation of this product is

allowed with a License Key for Region 4 (3W EIRP with Radar Detection)

Singapore Under Singapore Regulations, operation of this product is

only allowed with a License Key for Region 5 (20 dBm or 100mW EIRP)

Eire Under Eire Regulations, operation of this product is only

allowed with a License Key for Region 6 (33 dBm or 2W EIRP. Note lower power limits in narrow bandwidths.)

Korea Under Korean Regulations, operation of this product is

only allowed with a License Key for Region 11 (43 dBm or 20W EIRP)

India Operation of this product is only allowed with a License

Key for Region 19 (36 dBm or 4W EIRP at 15 MHz)

Thailand Operation of this product is only allowed with a License

Key for Region 20 (30 dBm or 1W EIRP)

Germany Operation of this product is only allowed with a License

Key for Region 22 (36 dBm or 4W EIRP)

Bahrain Operation of this product is only allowed with a License

Key for Region 24 (33 dBm or 2W EIRP)

Page 6

General Notice Applicable to Europe

This equipment complies with the essential requirements for the EU R&E Directive 1999/5/EC.

The use of 5.8GHz for Point to Point radio links is not harmonized across the EU.

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 speciﬁcally conﬁrmed 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 speciﬁcation at its discretion. The publication of information in this document does not imply freedom from patent or other rights of Motorola, Inc. or others.

Page 7

Contents

1 About This User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.1 Interpreting Typeface and Other Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.2 Getting Additional Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.2.1 Sending Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2 Avoiding Hazards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.1 Preventing Overexposure to RF Energy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.1.1 Calculations for Separation Distances and Power Compliance Margins . . . . . . . . . . . . 18

3 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.1 For Your Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.2 Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.2.1 Who Should Use This Guide? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.2.2 Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.2.3 Repair and Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.3 Product Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.3.1 The Outdoor Unit (ODU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.3.2 PIDU Plus – PTP 500 Series Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.3.3 Redundancy and Alternate Powering Conﬁgurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.3.4 Remote LEDs and Recovery Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.3.5 Cables and connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.3.6 PTP and Lightning Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.3.7 Mounting Brackets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.3.8 Conﬁguration and Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.4 Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4 Product Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

5 General Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

5.1 Spectrum Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

5.2 Region Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

5.3 Operational Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.3.1 Radar Avoidance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.3.2 RTTT Avoidance and Other Channel Use Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5.3.3 Radar Avoidance, i-DFS and Variable (Narrow) Bandwidth Operation . . . . . . . . . . . . 38

5.4 Variable Channel Bandwidth Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5.5 5.4 GHz Speciﬁc Frequency Planning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5.5.1 5.4 GHz Raster Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5.5.2 5.4 GHz Transmit Power Reduction at the Band Edges . . . . . . . . . . . . . . . . . . . . . . . . . 39

5.6 5.8 GHz Speciﬁc Frequency Planning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

5.6.1 5.8 GHz Raster Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

5.6.2 5.8 GHz Transmit Power Reduction at the Band Edges . . . . . . . . . . . . . . . . . . . . . . . . . 40

5.7 Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.8 Networking Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.9 Lightning Protection and regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5.10 Electrical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

6 Site Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

6.1 Site Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

6.1.1 ODU Site Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

6.1.2 PTP 500 Series Bridge PIDU Plus Site Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

6.1.3 Path Loss Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Page 8

6.1.4 Deﬁnitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

6.1.5 5.4 GHz Product Variant - Link Loss, Output Power and System Thresholds

versus Modulation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

6.1.6 5.8 GHz Product Variant - Link Loss, Output Power and System Thresholds

versus Modulation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

7 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

7.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

7.2 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

7.3 Tools Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

7.4 Installation Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

7.5 Legal Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

7.6 Mounting the ODUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

7.7 Connecting Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

7.7.1 Preparing the PIDU Plus To ODU Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

7.7.2 Making the Connections at the ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

7.7.3 Making the PTP 500 Series Bridge PIDU Plus Connection At The ODU . . . . . . . . . . 51

7.7.4 Routing the Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

7.7.5 Fitting a Lightning Protection Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

7.7.6 Grounding the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

7.7.7 Making the ODU Connection at the PTP 500 Series Bridge PIDU Plus . . . . . . . . . . . 53

7.7.8 Making the Network Connection at The PIDU Plus – PTP 500 Series Bridge . . . . . . 54

7.7.9 Mounting the PTP 500 Series Bridge PIDU Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

7.7.10 Powering Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

7.7.11 Aligning the PTP 500 Series Bridge ODUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

8 Web Page Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

8.1 Home Page – PTP 500 Series Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

8.1.1 Home Page Alarm Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

8.2 Systems Status Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

8.3 System Administration Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

8.3.1 System Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

8.3.2 Statistics Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

8.3.3 Detailed Counters Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

8.3.4 Install Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

8.3.5 Graphical Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

8.3.6 Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

8.3.7 Spectrum Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

8.3.8 Spectrum Management (Fixed Frequency) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

8.3.9 Spectrum Management Control – With Operational Restrictions . . . . . . . . . . . . . . . . 107

8.3.10 Remote Management Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

8.3.11 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

8.3.12 Change System Administration Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

8.3.13 License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

8.3.14 Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

8.3.15 Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

9 Recovery Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

9.1 Upgrade Software Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

9.2 Reset IP and Ethernet Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

9.3 Erase Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

9.4 Erase Security Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Page 9

9.5 Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

10 Fault Finding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

10.1 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

10.1.1 Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

10.1.2 Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

10.1.3 Checking your wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

10.2 Radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

10.2.1 No Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

10.2.2 Some Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

11 Lightning Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

11.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

11.1.1 Lightning Protection Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

11.2 Detailed Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

11.3 Testing Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

11.3.1 Pre-Power Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

11.3.2 Post-Power Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

11.4 Locating the Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

12 Wind Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

12.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

12.2 Calculation of Lateral Force . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

12.3 Capabilities of the PTP 500 Series Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

12.4 Wind Speed Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

13 PTP 500 Series Bridge - Connectorized Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

13.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

13.2 Product Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

13.2.1 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

13.2.2 Antenna Choices – 5.8 GHz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

13.2.3 Antenna Choices – 5.4 GHz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

13.3 Software/Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

13.3.1 Status Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

13.3.2 Conﬁguration Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

13.3.3 Installation Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

13.4 Deployment Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

13.5 Link Budget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

13.6 Regulatory Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

13.6.1 Antenna Choice (FCC and Industry Canada Regions Only) . . . . . . . . . . . . . . . . . . . . 151

13.6.2 Cable Losses (FCC Regions Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

13.6.3 Antennas for USA / Canada – 5.8 GHz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

13.6.4 Antennas for USA / Canada – 5.4 GHz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

13.7 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

13.7.1 Antenna Choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

13.7.2 Cables and Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

13.7.3 Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

13.7.4 Miscellaneous supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

13.7.5 Mounting the Connectorized 500 Series Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

13.7.6 Mounting the antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

13.7.7 Alignment Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

13.7.8 Aligning Dual Polar Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

13.7.9 Aligning Separate Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Page 10

13.7.10 Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

13.7.11 Antenna Cable Fixing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

13.7.12 Antenna Connection Weatherprooﬁng . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

13.8 Additional Lightning Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

13.8.1 ODU Mounted Outdoors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

13.8.2 ODU Mounted Indoors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

14 Data Rate Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

15 AES Encryption Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

15.1 Conﬁguring Link Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

15.1.1 License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

15.1.2 Encryption Mode and Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

15.2 Wireless Link Encryption FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

15.2.1 Encryption data entry ﬁelds are not available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

15.2.2 Link fails to bridge packets after enabling link encryption . . . . . . . . . . . . . . . . . . . . . . 175

15.2.3 Loss of AES following downgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

16 Legal and Regulatory Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

16.1 Important Note on Modiﬁcations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

16.2 National and Regional Regulatory Notices – 5.8 GHz variant . . . . . . . . . . . . . . . . . . . 176

16.2.1 European Union Notiﬁcation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

16.2.2 UK Notiﬁcation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

16.3 National and Regional Regulatory Notices – 5.4 GHz Variant . . . . . . . . . . . . . . . . . . . 178

16.3.1 U.S. Federal Communication Commission (FCC) and Industry Canada (IC)

Notiﬁcation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

16.3.2 European Union Notiﬁcation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

16.4 Exposure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

16.5 Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

16.5.1 Motorola Inc. End User License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

16.5.2 Limit of Liability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

17 Speciﬁcations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

17.1 System Speciﬁcations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

17.1.1 Wireless 5.4GHz Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

17.1.2 Wireless 5.8GHz Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

17.1.3 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

17.1.4 Ethernet Bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

17.1.5 Physical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

17.1.6 Powering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

17.2 Safety Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

17.3 EMC Emissions Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

17.3.1 5.4GHz Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

17.3.2 5.8GHz Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

17.4 EMC Immunity Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

17.5 Radio Certiﬁcations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

17.5.1 Radio Certiﬁcations - 5.4 GHz Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

17.5.2 Radio Certiﬁcations - 5.8 GHz Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

17.6 Environmental Speciﬁcations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

17.7 System Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

17.7.1 PIDU Plus to ODU and ODU to Network Equipment Connections . . . . . . . . . . . . . . 193

18 FAQs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

19 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Page 11

List of Figures

1 Typical PTP 500 Series Bridge Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2 PTP 500 Series Bridge Outdoor Unit (ODU) with PTP-LPU . . . . . . . . . . . . . . . . . . . . 24

3 Power Indoor Unit (PIDU Plus) – PTP 500 Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4 PIDU Plus Recovery Switch Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5 PTP 500 Series Bridge PIDU Plus Power Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

6 PTP 500 Series Bridge PIDU Plus to ODU Cable Length Graph . . . . . . . . . . . . . . . . . 27

7 External DC Supply Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

8 External DC Supply and AC Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

9 External DC Supply and Redundant AC Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

10 Remote LED and Recovery Switch Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

11 PTP 500 Series Bridge Layer Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

12 5.8 GHz UK RTTT Channel Avoidance – 15 MHz Channel Bandwidth Only . . . . . . . 38

13 5.4 GHz Available Spectrum Settings – 15 MHz Channel Bandwidth . . . . . . . . . . . . . . 39

14 5.8 GHz Available Spectrum Settings – 15 MHz Channel Bandwidth . . . . . . . . . . . . . . 40

15 Mounting to pole diameters 25mm (1”) to 50mm (2”) . . . . . . . . . . . . . . . . . . . . . . . . . . 47

16 Integral Safety Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

17 Correct Cable Preparation for the Recommended Cable . . . . . . . . . . . . . . . . . . . . . . . . . 49

18 Completed ODU Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

19 Warning Not To Over tighten Cable Gland . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

20 PTP 500 Series Bridge PIDU Plus Connexion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

21 Connecting the PIDU+ to the ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

22 Disconnecting the ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

23 Making the Network Connection at the PIDU Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

24 PTP 500 Series PIDU Plus Drip Loop Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

25 Menu Navigation Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

26 System Summary Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

27 Alarm Warning Triangle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

28 Status Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

29 System Administration Login Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

30 System Conﬁguration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

31 LAN Conﬁguration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

32 Conﬁguration Reboot Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

33 Conﬁguration Reboot Page – Ethernet Auto Negotiation Disabled . . . . . . . . . . . . . . . . 70

34 VLAN Conﬁguration Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

35 LAN Conﬁguration Page – Manual Ethernet Conﬁguration . . . . . . . . . . . . . . . . . . . . . . 72

36 Save and Restore Conﬁguration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

37 Save Conﬁguration File Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

38 PTP 500 Example Conﬁguration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

39 Restore Conﬁguration File Pop Up Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

40 Reset Conﬁguration and Reboot Conﬁrmation Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . 76

41 System Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

42 Detailed Counters Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

43 License Key Data Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

44 Installation Wizard Internet Protocol Conﬁguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

45 VLAN Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

46 5.8 GHz and 5.4 GHz Variants - Installation Wizard Wireless Conﬁguration . . . . . . . 86

47 5.8 GHz and 5.4 GHz Variants - Fixed Frequency Operation . . . . . . . . . . . . . . . . . . . . . 89

Page 12

48 5.8 GHz and 5.4 GHz Variants - Installation Wizard Conﬁrm Conﬁguration . . . . . . . 90

49 Reboot Conﬁrmation Pop Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

50 5.8 GHz and 5.4 GHz Variant - Disarm Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

51 Optional Post Disarm Conﬁguration 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

52 Optional Post Disarm Conﬁguration 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

53 Graphical Installation Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

54 Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

55 Software Upgrade Image Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

56 Software Download Progress Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

57 Software Upgrade Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

58 Reboot Conﬁrmation Pop Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

59 Spectrum Management as seen from the Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

60 Spectrum Management as seen from the Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

61 Example Spectrum Management Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

62 Active Channel History Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

63 Spectrum Management Time Series Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

64 Spectrum Management Fixed Frequency Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

65 Spectrum Management Help Page (Fixed Frequency) . . . . . . . . . . . . . . . . . . . . . . . . . . 107

66 Spectrum Management Master Screen With Operational Restrictions . . . . . . . . . . . . 108

67 Spectrum Management Slave Screen With Operational Restrictions . . . . . . . . . . . . . 109

68 Remote Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

69 Warning when disabling HTTP Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

70 Remote Management – Diagnostic Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

71 Diagnostic Plotter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

72 CSV Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

73 Password Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

74 Software License Key Data Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

75 License Key reboot Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

76 Reboot Conﬁrmation Pop Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

77 Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

78 System Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

79 Reboot Conﬁrmation Pop Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

80 Recovery Mode Warning Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

81 Recovery Options Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

82 Software Download Progress Indicator Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

83 Software Download Complete Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

84 Reboot Conﬁrmation Pop Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

85 Conﬁrm Reset to Factory Default Pop Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

86 IP and Ethernet Erased Successfully page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

87 Reboot Conﬁrmation Pop Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

88 Conﬁrm Erase Conﬁguration Pop Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

89 Erase Conﬁguration Successful Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

90 Erase Conﬁguration – Reboot Conﬁrmation Pop Up . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

91 Conﬁrm Zeroise Security Parameters Pop Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

92 Zeroise Parameters Successful Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

93 Recovery – Reboot Conﬁrmation Pop Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

94 ODU mounted in Zones A and B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

95 Showing how the use of a Finial enables the ODU to be mounted inside Zone B . . . 136

96 Diagrammatically Showing Typical Mast and Wall Installations . . . . . . . . . . . . . . . . . 138

Page 13

97 PTP LPU End Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

98 Simpliﬁed Circuit Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

99 PTP LPU test Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

100 Connectorized 500 Series Bridge Outdoor Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

101 Connectorized 500 Series bridge Status Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

102 Connectorized 500 Series bridge ‘System Conﬁguration’ Page . . . . . . . . . . . . . . . . . . . 147

103 Connectorized PTP 500 Series Bridge ‘Installation Wizard’ Page . . . . . . . . . . . . . . . . 148

104 Connectorized 500 Series bridge ‘Conﬁrm Installation’ Page . . . . . . . . . . . . . . . . . . . . 149

105 Connectorized 500 Series bridge ‘Disarm Installation’ Page . . . . . . . . . . . . . . . . . . . . . 150

106 Forming a Drip Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

107 Weatherprooﬁng the Antenna Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

108 Additional Grounding When Using Connectorized Units . . . . . . . . . . . . . . . . . . . . . . . 162

109 Lightning Arrestor Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

110 Polyphaser Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

111 BPSK 0.50 Single Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

112 QPSK 0.50 Single Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

113 QPSK 0.75 Single Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

114 16 QAM 0.50 Single Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

115 16 QAM 0.75 Single Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

116 64 QAM 0.67 Single Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

117 64 QAM 0.83 Single Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

118 256 QAM 0.75 Single Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

119 QPSK 0.50 Dual Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

120 QPSK 0.75 Dual Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

121 16 QAM 0.50 Dual Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

122 16 QAM 0.75 Dual Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

123 64 QAM 0.67 Dual Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

124 64 QAM 0.83 Dual Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

125 256 QAM 0.75 Dual Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

126 AES Software License Key Data Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

127 AES Conﬁguration Data Entry Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

128 Conﬁguration Reboot Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

129 Cable Connection Diagram (T568B Color Coding) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Page 14

List of Tables

1 Font types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2 Admonition types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3 Power Compliance Margins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4 Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5 PTP 500 Series Bridge Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

6 5.8 GHz Band Edge Tx Power Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

7 5.4GHz - IP Mode - Sensitivity Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

8 5.4GHz -TDM Mode - Sensitivity Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

9 5.8GHz - IP Mode - Sensitivity Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

10 5.8GHz - TDM Mode - Sensitivity Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

11 Audio indications from the ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

12 500 Series Bridge Factory Conﬁguration Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

13 Spectrum Management change state key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

14 Spectrum Management Time Series Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

15 Spectrum Management Change State Key With Operational Restrictions . . . . . . . . 110

16 Protection Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

17 Resistance Table Referenced to the RJ45 at the PIDU Plus . . . . . . . . . . . . . . . . . . . . 140

18 Lateral Force – Imperial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

19 Lateral Force – Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

20 Cable Losses per Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Page 15

About This User Guide

1 About This User Guide

This guide covers the installation, commissioning, operation and fault ﬁnding 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 speciﬁc 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.

Page 16

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 speciﬁc 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.

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

1.2 Getting Additional Help

To get information or assistance as soon as possible for problems that you encounter, use the following sequence of action:

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 Readerrsearch capability for keywords that apply.

2. Visit the Motorola website at http://www.motorola.com/ptp

Reader is a registered trademark of Adobe Systems, Incorporated.

Page 17

3. Ask your Motorola products supplier to help.

4. Gather information from aﬀected units such as:

a. the IP addresses and MAC addresses b. the software releases c. the conﬁguration 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.2.1 Sending Feedback

We welcome your feedback on the PTP 500 Series Bridge system documentation

About This User Guide

support.ptp@motorola.com.

This includes feedback on the structure, content, accuracy, or completeness of our documents, and any other comments you have.

Page 18

Avoiding Hazards

2 Avoiding Hazards

2.1 Preventing Overexposure to RF Energy

Caution 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 ﬁelds 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 ﬁeld 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.

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

• 6 W/m2 for RF energy in the 900-MHz frequency band in the US and Canada.

• 10 W/m2 for RF energy in the 2.4-, 5.2-, 5.4-, and 5.8-GHz frequency bands.

Peak power density in the far ﬁeld of a radio frequency point source is calculated as follows:

P.G

S =

Where:-

4πd

(1)

S = power density W/m P = Maximum Average transmit power capability of the radio W G = total Tx gain as a factor, converted from dB d = distance from point source m

Page 19

Avoiding Hazards

Rearranging terms to solve for distance yields

P.G

d =

4πS

2.1.1.1 Calculated Distances and Power Compliance Margins

Table 3 shows calculated minimum separation distances d, recommended distances and resulting

power compliance margins for each frequency band and antenna combination.

(2)

Band Antenna Max

5.4

Integrated 0.005

GHz

External

3ft Dish

5.8

Integrated 0.32

GHz

External

2ft Flat

Plate

External

6ft Dish

Average

Transmit

Power in

Burst (Watt)

(7dBm)

0.00035

(-4.6dBm)

(25dBm)

0.32

(25dBm)

0.32

(25dBm)

(Watt)

0.00250 200

0.00017 2884

0.16 200

0.16 631

0.16 6310

Variable D

G S

(23dBi)

(34.6dBi)

(23dBi)

(28dBi)

(38dbi)

(m)

(W/m2)

10 0.06 1 15.9

10 0.06

10 0.5 2 4.0

10 0.9 4 4.5

10 2.83 10 3.5

Recommended

Distance (m)

Power

Compliance

Margin

Table 3 Power Compliance Margins

Notes:

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

2. At 5.4GHz the product is generally to a ﬁxed EIRP which can be achieved with the Integrated Antenna. If there are no EIRP limits, use the distance calculations for 5.8GHz.

3. At 5.8GHz, for antennas between 0.6m (2ft) and 1.8m (6ft), alter the distance proportionally to the antenna gain

Page 20

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. 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. 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 500 Series is used to power the PTP 500 Series Bridge ODU. The use of other power sources may invalidate safety approval and aﬀect your warranty.

WARNING: When using alternate DC supplies (via the PIDU Plus DC in terminals as described in Section 3.3.3 “Redundancy and Alternate Powering Conﬁgurations”), 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, and

• The power source cannot provide more than the Energy Hazard Limit as deﬁned by IEC/EN/UL6090,

Clause 2.5, Limited Power (The Energy Hazard Limit is 240VA)

CAUTION: Users and installers should note that the main power supply is the primary disconnect device.

CAUTION: Safety will be compromised if external quality cables are not used for connections that will be exposed to the weather.

CAUTION: Safety will be compromised if a diﬀerent power supply is used than the one supplied by Motorola as part of the system.

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.

Page 21

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:

• Outdoor radio equipment installation

• Network conﬁguration

• Use of web browser for system conﬁguration, monitoring and fault ﬁnding

3.2.2 Contact Information

Postal Address: Motorola, Inc.

Web Site: http://www.motorola.com/ptp

Getting Started

Unit A1, Linhay Business Park, Eastern Road, Ashburton, Devon. TQ13 7UP United Kingdom

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

3.2.3 Repair and Service

For unit repair or service, contact your service provider or an authorized Motorola Point-to-Point Distributor for Return Material Authorization (RMA) and shipping instructions. Alternatively, contact the PTP Global Technical Support Center to process an RMA.

+44 (0) 808 234 4640 (Toll Free in the Uk).

Table 4 Contact Information

Page 22

Getting Started

3.3 Product Description

This User Manual is speciﬁcally 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 oﬀers true non-line-of-sight (NLOS) operation by using a combination of Orthogonal Frequency Division Multiplexing (OFDM) modulation and Multiple-Input MultipleOutput (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 conﬁgured as Master or Slave.

Each end of the link consists of:

• An integrated (or connectorized - see 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).

section 13) outdoor transceiver unit containing all the

Page 23

Getting Started

A pair of units is normally supplied pre-conﬁgured 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 nonstandard powering technique.

Power is fed into the PTP 500 Series Bridge PIDU Plus from the mains via a standard “ﬁgure 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.

Page 24

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 500 Series Bridge PIDU Plus. Figure 2 shows an installation example of a PTP 500 Series ODU with a Motorola lightning protection unit (PTP-LPU).

Getting Started

Figure 2 PTP 500 Series Bridge Outdoor Unit (ODU) with PTP-LPU

Page 25

3.3.2 PIDU Plus – PTP 500 Series Bridge

The PTP 500 Series Bridge PIDU Plus is used to generate the ODU supply voltage from the mains supply and inject this supply voltage into the 1000BaseT Ethernet connection to the ODU. Connection uses a CAT5e cable using standard RJ45 wiring.

CAUTION: Care should be taken not to connect equipment other than an ODU for the PTP 500 Series Bridge to a PIDU Plus ODU port as equipment damage may occur. The PTP 500 Series Bridge PIDU Plus is not interchangeable with the PTP 400 Series PIDU Plus but can be used with the PTP 600 Series.

Getting Started

Figure 3 Power Indoor Unit (PIDU Plus) – PTP 500 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, ﬂashing when there is Ethernet activity. The fact that it lights also indicates that the ODU is powered. At power up the LED will ﬂash 10 times to indicate that a correct start up sequence has occurred. See Section 10 “Fault Finding” for further fault ﬁnding 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

Page 26

Getting Started

The Recovery switch is used to recover the unit from conﬁguration 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 500 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 Alternate Powering Conﬁgurations”.

WARNING: When using alternate 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 deﬁned by IEC/EN/UL6090,

Clause 2.5, Limited Power (The Energy Hazard Limit is 240VA)

Also on the left hand side of the PTP 500 Series Bridge PIDU Plus, connectors and jumpers can be found that allow the remote connection of power LED, Ethernet LED and Recovery switch. The connection instructions can be found in Section 3.3.4 “Remote LEDs and Recovery Switch”.

The input supply range for the 500 Series PIDU Plus is 90V-264V AC, 47-63Hz. Mains connection to the PIDU Plus is made using a standard “ﬁgure of eight” mains lead as shown in Figure 5.

Figure 5 PTP 500 Series Bridge PIDU Plus Power Input

Page 27

Getting Started

3.3.3 Redundancy and Alternate Powering Conﬁgurations

NOTE: The use of DC supplies of less than 55v will reduce the usable distance between the PIDU Plus and ODU see Figure 6.

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 PTP 500 Series Bridge PIDU

Plus to ODU Cable Length Graph

Figure 7 External DC Supply Only

Page 28

3.3.3.2 External DC Supply and AC Supply

To give redundancy through the use of mains and DC supply.

Figure 8 External DC Supply and AC Supply

Getting Started

3.3.3.3 External DC Supply and Redundant AC Supply

To guard against mains failure, DC supply failure of PTP 500 Series Bridge PIDU Plus failure.

Figure 9 External DC Supply and Redundant AC Supply

Page 29

3.3.4 Remote LEDs and Recovery Switch

The PTP 500 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 10.

Getting Started

Figure 10 Remote LED and Recovery Switch Wiring

3.3.5 Cables and connectors

The cable used to connect the PTP 500 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 speciﬁcation below be used:

Cable: Superior Essex BBDGE CAT 5e Connector Type: Tyco, 5-558530-1 Gland: Motorola WB1811

Page 30

Caution: Failure to use the recommended (or equivalent) standard of cable may invalidate the system’s safety certiﬁcation.

The cable used to connect the PTP 500 Series Bridge PIDU Plus to the users Network Equipment can be any standard CAT5e Cable.

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 speciﬁcations identiﬁed in Section 17 “Speciﬁcations”, 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”.

Getting Started

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 ﬁrst. 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 500 Series Bridge”.

3.3.8 Conﬁguration and Management

Conﬁguration and Management of the PTP 500 Series Bridge is implemented using an inbuilt web server hosting a number of Conﬁguration and Management web pages. This approach allows Conﬁguration 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 traﬃc. Connection to the unit is via a preset IP address. This address can be changed via the Network Interface Conﬁguration web page. A full explanation of the available web pages and their use can be found in Section 8 “Web Page Reference”.

Page 31

Getting Started

3.4 Warranty

Motorola’s standard hardware warranty is for one (1) year from date of shipment from Motorola or a Motorola Point-to-Point Distributor. Motorola warrants that hardware will conform to the current relevant published speciﬁcations 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 License Agreement”.

Section 16.5.1 “Motorola Inc. End User

Page 32

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. The non-line-of-sight (NLOS) aspects of the product are provided by Multiple-Input Multiple-Output (MIMO), coupled with Orthogonal Frequency Division Multiplexing (OFDM) modulation.

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)

• ETSI 5.8 GHz band C (5.725-5.850 GHz) and the USA 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 reduce the data rate in severe or adverse conditions. The PTP 500 series provides wireless Ethernet bridging between two ﬁxed locations. To be more precise, it forwards Ethernet frames as a two-port transparent heterogeneous encapsulation bridge, meaning that each bridge forwards frames between two dissimilar interfaces (Ethernet and wireless), encapsulating Ethernet MAC frames within a PTP MAC frames for transmission at the wireless interface. A link consisting of a pair of back to back bridges appears to the data network to be very similar to a standard two-port Ethernet bridge.

The PTP500 series provides two egress queues in each direction, classifying Ethernet frames into one of the two prioritised queues based on inspection of the user priority ﬁeld (802.1p) in the IEEE802.1Q VLAN tag. Untagged frames receive a default priority. The queuing method is strict priority. The bridge does not implement any VLAN functions for bridged frames apart from inspection of the priority ﬁeld, and consequently the bridge forwards tagged and untagged Ethernet frames regardless of VLAN ID and without modiﬁcation of any protocol header ﬁelds..

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

Page 33

Product Architecture

Figure 11 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 conﬁgured to use VLAN tags on the management interfaces.

The PTP 500 Series Bridge is fully software upgradeable. New software images are ﬁrst 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 ﬁrst loaded into RAM and check-summed. If the compressed image transfer has completed successfully the image is decompressed and written to ﬂash 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.

Page 34

General Considerations

5 General Considerations

5.1 Spectrum Planning

The PTP 500 Series Bridge has four frequency variants in its product range.

Band Deﬁnition Frequency

Coverage

5.4 GHz ETSI 5 GHz band B, USA UNII Band

5.8 GHz USA ISM Band / ETSI 5 GHz band C

Table 5 PTP 500 Series Bridge Variants

Note: for 5.4 GHz and 5.8 GHz, 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. i-DFS can be inﬂuenced 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 ﬁxed frequency mode is used to statically allocate transmit and receive channels.

5470-5725 MHz 15 MHz 5 MHz

5725-5850 MHz 15 MHz 5 MHz

Variable Channel Width

Channel Raster

Page 35

General Considerations

5.2 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

1 5.8 GHz FCC Compliant (e.g.

2 5.8 GHz China 10 dBm 33 dBm

3 5.8 GHz Australia, Hong

4 5.8 GHz UK 12 dBm 35 dBm Radar Avoidance

Frequency Band

Regulatory Body or Countries

USA, Canada, Taiwan, Brazil)

Kong

Max Tx Power

25 dBm None Reduced TX Power

13 dBm 36 dBm

EIRP Limit

Operational Restrictions (see

Section 5.3

“Operational Restrictions”)

at Band Edges see

Section 5.6.2 “5.8

GHz Transmit Power Reduction at the Band Edges”

Enabled and RTTT (Road Transport and Traﬃc Telematics, 5795 to 5815 MHz channels cannot be used)

5 5.8 GHz Singapore -3 dBm 20 dBm

6 5.8 GHz Eire 10 dBm 33 dBm

7 5.4/5.8 GHz Unregulated DFS

and RTTT

8 5.4 / 5.8 GHz Unregulated Internal

Use

25 dBm None Radar Avoidance

25 dBm None

Enabled and RTTT (Road Transport and Traﬃc Telematics, 5795 to 5815 MHz channels cannot be used)

Page 36

General Considerations

Region Code

Frequency Band

Regulatory Body or Countries

Max Tx Power

EIRP Limit

Operational Restrictions (see

Section 5.3

“Operational Restrictions”)

11 5.4 GHz Korea 20 dBm 43 dBm Band restricted :

5725 MHz to 5825 MHz

12 5.4 GHz USA 7 dBm 30 dBm Radar Avoidance

Enabled

13 5.4 GHz Australia, Canada 7 dBm 30 dBm Radar Avoidance

Enabled Weather; Radar Band (5600 to 5650 MHz) barred

16 2.5 GHz USA 23 dBm >=63 dBm Licensed Band

operation. Note Power reduction in the Upper Band.

18 2.5 GHz Taiwan 23 dBm Channel 2590 MHz

should not be used because of in-band interference.

19 5.8 GHz India 13 dBm 36 dBm 5.825 MHz to 5.850

MHz Only

20 5.4 / 5.8 GHz Thailand 7 dBm 30 dBm Fixed Power for all

bandwidths.

21 5.4 GHz Korea 5 dBm 28 dBm Maximum Channel

Bandwidth 20 MHz. 5470 MHz to 5650 MHz only.

22 5.8 GHz Germany 12 dBm 35 dBm 5755 MHz to 5850

MHz only.

23 4.5 GHz Military 25 dBm None

24 5.8 GHz Bahrain 20 dBm 33 dBm

26 5.4 GHz ETSI 7 dBm 30 dBm Radar Avoidance

Enabled Weather; Radar Band (5600 to 5650 MHz) barred

Page 37

General Considerations

Note: For Region Code 16, the EIRP limit is approximately 63 dBm + 10 x Log(360/Antenna Azimuth BW.

When shipped from the factory units3are conﬁgured as follows:

• PTP 500 Series Bridge 5.4 GHz – Region Code 26

• PTP 500 Series Bridge 5.8 GHz – 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.

• Provide on aggregate a uniform loading of the spectrum across all devices, i.e. Fixed Frequency operation is not allowed.

• Radar avoidance is not applicable to the PTP54600 product.

To address the primary aims the Spectrum Management algorithm implements a radar detection function which looks for impulsive interference on the active channel only. If impulsive interference is detected Spectrum Management will mark the current active channel as having detected radar and initiate a channel hop to an available channel. The previous active channel will remain in the radar detected state for thirty minutes after the last impulsive interference pulse was detected. After the thirty minutes have expired the channel will be returned to the available channel pool.

The radar detection algorithm will always scan the active channel for 60 seconds for radar interference before using the 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.

Note that 5.4 GHz and 5.8 GHz are diﬀerent products.

Note that the Quickstart Guide also contains the license keys for region 12 and 13.

Page 38

General Considerations

Band Edge

5725 MHz

Band Edge

5850 MHz

Default

5735MHz

5735

5740

5745

5750

5755

5760

5765

5770

5775

5780

5785

5790

5795

5800

5805

5810

5815

5820

5825

5830

5835

5840

5736MHz

5736

5741

5746

5751

5756

5761

5766

5771

5776

5781

5786

5791

5796

5801

5806

5811

5816

5821

5826

5831

5836

5841

5737MHz

5737

5742

5747

5752

5757

5762

5767

5772

5777

5782

5787

5792

5797

5802

5807

5812

5817

5822

5827

5832

5837

5842

5738MHz

5738

5743

5748

5753

5758

5763

5768

5773

5778

5783

5788

5793

5798

5803

5808

5813

5818

5823

5828

5833

5838

5739MHz

5739

5744

5749

5754

5759

5764

5769

5774

5779

5784

5789

5794

5799

5804

5809

5814

5819

5824

5829

5834

5839

Lower Center

Frequency

5.3.2 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 dependent on the channel raster selected. For example see the eﬀect of the UK RTTT channel restrictions in Figure 12. 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”.

NOTE: “Radar Avoidance Enabled” is only valid with 30 MHz channel bandwidth.

Figure 12 5.8 GHz UK RTTT Channel

Avoidance – 15 MHz Channel Bandwidth Only

5.3.3 Radar Avoidance, i-DFS and Variable (Narrow) Bandwidth Operation

Radar avoidance at 5.8 GHz is applicable to EU operation and the requirements are currently as deﬁned in EN 302 502 v1.1.1

5.4 Variable Channel Bandwidth Operation

Channel bandwidth of 15 MHz5is supported for Only Full versions of the PTP 500. Conﬁguration of the variable bandwidth operation must be symmetric, i.e. the Transmit and receive channels must use identical channel bandwidths.

15MHz channel widths are available where allowed by local regulations and subject to some restrictions on channel choice.

Page 39

General Considerations

Band Edge 5470 MHz

Band Edge

5725 MHz

Default

5480MHz

5480

5485

5490

5495

5500

5505

5510

5515

5520

5525

5530

5535

5540

5545

5550

5555

5560

5565

5570

5575

5580

5585

5590

5595

5600

5605

5610

5615

5620

5625

5630

5635

5640

5645

5650

5655

5660

5665

5670

5675

5680

5685

5690

5695

5700

5705

5710

5715

5481MHz

5481

5486

5491

5496

5501

5506

5511

5516

5521

5526

5531

5536

5541

5546

5551

5556

5561

5566

5571

5576

5581

5586

5591

5596

5601

5606

5611

5616

5621

5626

5631

5636

5641

5646

5651

5656

5661

5666

5671

5676

5681

5686

5691

5696

5701

5706

5711

5716

5482MHz

5482

5487

5492

5497

5502

5507

5512

5517

5522

5527

5532

5537

5542

5547

5552

5557

5562

5567

5572

5577

5582

5587

5592

5597

5602

5607

5612

5617

5622

5627

5632

5637

5642

5647

5652

5657

5662

5667

5672

5677

5682

5687

5692

5697

5702

5707

5712

5717

5483MHz

5483

5488

5493

5498

5503

5508

5513

5518

5523

5528

5533

5538

5543

5548

5553

5558

5563

5568

5573

5578

5583

5588

5593

5598

5603

5608

5613

5618

5623

5628

5633

5638

5643

5648

5653

5658

5663

5668

5673

5678

5683

5688

5693

5698

5703

5708

5713

5484MHz

5484

5489

5494

5499

5504

5509

5514

5519

5524

5529

5534

5539

5544

5549

5554

5559

5564

5569

5574

5579

5584

5589

5594

5599

5604

5609

5614

5619

5624

5629

5634

5639

5644

5649

5654

5659

5664

5669

5674

5679

5684

5689

5694

5699

5704

5709

5714

Lower Center

Frequency

5.5 5.4 GHz Speciﬁc 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 13.

Figure 13 5.4 GHz Available Spectrum Settings – 15 MHz Channel Bandwidth

5.5.1 5.4 GHz Raster Considerations

The PTP 500 Series Bridge 5.4 GHz variant operates on a 5 MHz channel raster. The channel raster is set to even centre frequencies. See Figure 13.

5.5.2 5.4 GHz Transmit Power Reduction at the Band Edges

The 5.4 GHz product variant does not apply any band edge power reduction.

Page 40

General Considerations

Band Edge

5725 MHz

Band Edge

5850 MHz

Default

5735MHz

5735

5740

5745

5750

5755

5760

5765

5770

5775

5780

5785

5790

5795

5800

5805

5810

5815

5820

5825

5830

5835

5840

5736MHz

5736

5741

5746

5751

5756

5761

5766

5771

5776

5781

5786

5791

5796

5801

5806

5811

5816

5821

5826

5831

5836

5841

5737MHz

5737

5742

5747

5752

5757

5762

5767

5772

5777

5782

5787

5792

5797

5802

5807

5812

5817

5822

5827

5832

5837

5842

5738MHz

5738

5743

5748

5753

5758

5763

5768

5773

5778

5783

5788

5793

5798

5803

5808

5813

5818

5823

5828

5833

5838

5739MHz

5739

5744

5749

5754

5759

5764

5769

5774

5779

5784

5789

5794

5799

5804

5809

5814

5819

5824

5829

5834

5839

Lower Center

Frequency

5.6 5.8 GHz Speciﬁc 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 14 shows the available spectrum.

Figure 14 5.8 GHz Available Spectrum Settings – 15 MHz Channel Bandwidth

5.6.1 5.8 GHz Raster Considerations

The PTP 500 Series Bridge 5.8 GHz variant operates on a 5 MHz channel raster. The channel raster is set to even center frequencies. See

Figure 14.

5.6.2 5.8 GHz 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 conﬁgurations the PTP 500 Series Bridge solution reduces the power when operating at the edge channels. The amount of reduction, if any, is dependent on the region code of the region of operation. This currently only aﬀects systems conﬁgured with Region Code 1. The power reduction in the edge channels for 15 MHz is presented in Table 6 (for region code 1 ONLY).

Page 41

General Considerations

Channel Center Frequency

(MHz)

5735 25

5736 25

5737 25

5738 25

5739 - 5838 25

5740 25

5742 - 5832 25

5839 26

5840 26

Maximum Output Power (dBm)

Channel Bandwidth (MHz)

Table 6 5.8 GHz Band Edge Tx Power Reduction

5.7 Distance

The PTP 500 Series Bridge will operate at ranges from 100 m (330 ft) to 200 km (124 miles), within 3 modes: 0-40km (0-25 miles), 0-100km (0-62 miles) and 0-200km (0-124 miles). Operation of the system will depend on obstacles in the path between the units. Operation at 40 km (25 miles) or above will require a near line-of-sight path. Operation at 100m (330 ft) could be achieved with one unit totally obscured from the other unit, but with the penalty of transmitting at higher power in a non-optimal direction, thereby increasing interference in the band. This subject is covered in more detail in

Section 6.1.3 “Path Loss Considerations”.

5.8 Networking Information

The PTP 500 Series Bridge operates as a transparent Ethernet bridge. Each unit requires an IP address. This IP address is for management purposes only and it plays no part in the operation of the system. IP addresses are assigned during initial conﬁguration as described in Section 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 ﬁtted 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 conﬁgured as part of the system installation to be fully eﬀective. 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 speciﬁc 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 (Section 3.3.2 “PIDU Plus – PTP 500 Series Bridge”).

Page 42

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

• 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])

• Distance from the PIDU Plus to the ODU (Maximum cable run from the PIDU Plus to the ODU is 300m [990 ft] when using the Fiber interface)

Site Planning

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.

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

Where

free_space

excess

fade

seasonal

capability

free_space

= Free Space Path Loss dB = Excess Path Loss dB

= Fade Margin Required dB = Seasonal Fading dB = Equipment Capability dB

+ L

excess

+ L

fade

+ L

seasonal

< L

capability

(3)

Page 43

6.1.4 Deﬁnitions

The equipment capability is given in Table 7, Table 9 (IP Mode) and Table ??, Table 10 (TDM Mode). Each table gives Link Loss Output Power and System Thresholds for PTP 500 Series Bridge in all modulation modes for the channel bandwidth 15 MHz. 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 3 needs to be performed to judge whether a particular link can be installed. When the link has been installed, web pages provide information about the link loss currently measured by the equipment both instantaneously and averaged. The averaged value will require maximum seasonal fading to be added, and then the radio reliability of the link can be computed.

For minimum error rates on TDM links the maximum modulation mode should be limited to 64QAM 0.75.

The values for (BPSK) are static receive sensitivity measurements. The other values are static receive sensitivity measurements with an AMOD threshold applied. The AMOD threshold applied is for a benign radio channel.

Sensitivity: Sensitivity is deﬁned as the combined receive input signal level on both horizontal and vertical inputs that produces a Null Bit Error Ratio of 3x10-7.

Site Planning

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 diﬀerent region codes are selected.

AMOD Threshold: The AMOD threshold is the combined receive input signal level on both horizontal and vertical inputs that results in the link consistently entering the receive modulation mode under consideration as the signal level is increased.

System Threshold: Thresholds for all modes except BPSK are for the relevant link optimization AMOD thresholds. System threshold for BPSK is the RPSK receive sensitivity.

Max Link Loss: The maximum link loss for each modulation mode is derived from the AMOD threshold for that mode (sensitivity threshold for BPSK) and the maximum Region 1 centre channel output power. The ﬁgures assume integral antennas with 23dBi (5.8 GHz and 5.4 GHz) gain are used.

Page 44

Site Planning

6.1.5 5.4 GHz Product Variant - Link Loss, Output Power and System Thresholds versus Modulation Mode

Table 7 and Table 8 show respectively sensitivity ﬁgures for IP and TDM respectively.

Modulation Mode Threshold Value (dBm) Output Power (dBm) Maximum Link Loss (dB)

Channel Bandwidth (MHz)

15 MHz

256QAM 0.75 dual -65.02 +21 133.02

64 QAM 0.83 dual -69.63 +21 137.63

64QAM 0.67 dual -73.22 +22 142.22

16QAM 0.75 dual -76.59 +23 146.59

16QAM 0.50 dual -80.72 +24 151.72

QPSK 0.75 dual -82.78 +25 154.78

QPSK 0.50 dual -89.08 +26 162.08

256QAM 0.75 single -68.58 +21 136.58

64QAM 0.83 single -72.90 +21 140.90

64QAM 0.67 single -76.35 +22 145.35

16QAM 0.75 single -79.72 +23 149.72

16QAM 0.50 single -83.82 +24 154.82

QPSK 0.75 single -85.74 +25 157.74

QPSK 0.50 single -89.02 +26 162.02

BPSK 0.50 single -94.25 +27 168.25

Table 7 5.4GHz - IP Mode - Sensitivity Figures

Modulation Mode Threshold Value (dBm) Output Power (dBm) Maximum Link Loss (dB)

Channel Bandwidth (MHz)

15 MHz

256QAM 0.75 dual -63.52 +21 131.52

64 QAM 0.83 dual -68.13 +21 136.13

64QAM 0.67 dual -71.72 +22 140.72

16QAM 0.75 dual -75.09 +23 145.09

16QAM 0.50 dual -79.22 +24 150.22

QPSK 0.75 dual -81.28 +25 153.28

QPSK 0.50 dual -87.58 +26 160.58

256QAM 0.75 single -67.08 +21 135.08

64QAM 0.83 single -71.40 +21 139.40

64QAM 0.67 single -74.85 +22 143.85

16QAM 0.75 single -78.22 +23 148.22

16QAM 0.50 single -82.32 +24 153.32

QPSK 0.75 single -84.24 +25 156.24

QPSK 0.50 single -87.52 +26 160.52

BPSK 0.50 single -94.25 +27 168.25

Table 8 5.4GHz -TDM Mode - Sensitivity Figures

Page 45

Site Planning

6.1.6 5.8 GHz Product Variant - Link Loss, Output Power and System Thresholds versus Modulation Mode

Table 9 and Table 10 show respectively sensitivity ﬁgures for IP and TDM respectively.

Modulation Mode Threshold Value (dBm) Output Power (dBm) Maximum Link Loss (dB)

Channel Bandwidth (MHz)

15 MHz

256QAM 0.75 dual -65.02 +21 133.02

64 QAM 0.83 dual -69.63 +21 137.63

64QAM 0.67 dual -73.22 +22 142.22

16QAM 0.75 dual -76.59 +23 146.59

16QAM 0.50 dual -80.72 +24 151.72

QPSK 0.75 dual -82.78 +25 154.78

QPSK 0.50 dual -89.08 +26 162.08

256QAM 0.75 single -68.58 +21 136.58

64QAM 0.83 single -72.90 +21 140.90

64QAM 0.67 single -76.35 +22 145.35

16QAM 0.75 single -79.72 +23 149.72

16QAM 0.50 single -83.82 +24 154.82

QPSK 0.75 single -85.74 +25 157.74

QPSK 0.50 single -89.02 +26 162.02

BPSK 0.50 single -94.25 +27 168.25

Table 9 5.8GHz - IP Mode - Sensitivity Figures

Modulation Mode Threshold Value (dBm) Output Power (dBm) Maximum Link Loss (dB)

Channel Bandwidth (MHz)

15 MHz

256QAM 0.75 dual -63.52 +21 131.52

64 QAM 0.83 dual -68.13 +21 136.13

64QAM 0.67 dual -71.72 +22 140.72

16QAM 0.75 dual -75.09 +23 145.09

16QAM 0.50 dual -79.22 +24 150.22

QPSK 0.75 dual -81.28 +25 153.28

QPSK 0.50 dual -87.58 +26 160.58

256QAM 0.75 single -67.08 +21 135.08

64QAM 0.83 single -71.40 +21 139.40

64QAM 0.67 single -74.85 +22 143.85

16QAM 0.75 single -78.22 +23 148.22

16QAM 0.50 single -82.32 +24 153.32

QPSK 0.75 single -84.24 +25 156.24

QPSK 0.50 single -87.52 +26 160.52

BPSK 0.50 single -94.25 +27 168.25

Table 10 5.8GHz - TDM Mode - Sensitivity Figures

Page 46

Installation

7 Installation

Motorola recommends that only qualiﬁed personnel undertake the installation of a PTP 500 Series Bridge solution.

7.1 Preparation

Before proceeding with the installation you should:

• 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 qualiﬁed 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”.

7.2 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 500 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”

7.3 Tools Required

The following speciﬁc tools are required to install a PTP 500 Series Bridge in addition to general tools:

• 13mm Spanner / Wrench

• RJ45 Crimp Tool

• IBM Compatible Personal Computer (PC) running Windows 98 or later with 10, 100 or

1000BaseT Ethernet (Ability to change IP settings easily is recommended)

• Either Internet Explorer version 6 or higher, or FireFox 1.5 or higher are recommended.

• Ethernet patch cable

7.4 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”.

Page 47

Installation

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.

7.6 Mounting the ODUs

The ODU mounting bracket is designed to ease installation by ﬁxing the bracket to a pole and then bringing the ODU into position using a single bolt ﬁxing. 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.

Pole diameters of 25mm (1”) to 50mm (2”) can be accommodated by inverting the back of the bracket as shown in Figure 15.

Figure 15 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.

Step 2: Mate the unit to

the bracket together and

tighten the nut and bolt.

Page 48

Installation

The enclosure and mounting brackets of the PTP 500 Series Bridge product range are capable of withstanding wind speeds up to 151mph (242kph). The installer should ensure that the structure the bridge is ﬁxed to is also capable of withstanding the prevalent wind speeds and loads. See

Section 12 "Wind Loading".

The integral safety loop should be used both for hoisting the ODU up a mast or building and into position, and also as a ﬁxing point to secure a permanent safety lanyard from the tower/building to the ODU in case of mounting failure.

Figure 16 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 ﬁxed to a separate ﬁxing point that is not part of the direct mounting system for the ODU.

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). Cable lengths up to 300m (984 ft) can be used where the PIDU Plus to ODU cable is supplying power only, i.e., when using the PTP 500 Series Bridge Optical Interface.

Page 49

Installation

The cable should be assembled as shown in Figure 17:

Figure 17 Correct Cable Preparation for the Recommended Cable

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 use a cable gland.

Page 50

Installation

Figure 18 shows a completed ODU to PIDU Plus cable.

Figure 18 Completed ODU Connector

CAUTION: Do not over tighten the glands as the internal seal and structure may be damaged.

See Figure 19 for an example of an over tightened cable gland.

Figure 19 Warning Not To Over tighten Cable Gland

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 ﬁrst hole on the right (Figure 20) and is labeled “PIDU +”.

Figure 20 PTP 500 Series Bridge PIDU Plus Connexion

Page 51

Installation

7.7.3 Making the PTP 500 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 5.7.1 above

Step 3: Screw in the body of the

weather prooﬁng gland and tighten

Figure 21 Connecting the PIDU+ to the ODU

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

Page 52

Installation

Should it be necessary to disconnect the PIDU Plus to ODU cable at the ODU, this can be achieved by removing the weather prooﬁng gland and depressing the RJ45 locking tab with a small screwdriver as shown below:

Figure 22 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 ﬁt a Lightning Protection unit, this should be installed by following the manufacturer’s instruction. For recommended types see Section 11 "Lightning Protection”

7.7.6 Grounding the Installation

The Outdoor Unit (ODU) must be properly grounded to protect against power surges. It is the user’s responsibility to install the equipment in accordance with Section 810 of the National Electric Code, ANSI/NFPA No.70-1984 or Section 54 of the National Electrical Code in the country of installation. These codes describe correct installation procedures for grounding the outdoor unit, mast, lead-in wire and discharge unit, size of grounding conductors and connection requirements for grounding electrodes. It is recommended that installation of the outdoor unit be contracted to a professional installer.

Page 53

Installation

7.7.7 Making the ODU Connection at the PTP 500 Series Bridge PIDU Plus

The ODU is connected to the PIDU Plus by means of a concealed RJ45 connector. The RJ45 connection has been placed inside the PIDU Plus hinged cover to prevent the user from inadvertently plugging other equipment into the ODU RJ45 socket.

CAUTION: Plugging other equipment into the ODU RJ45 socket may damage the equipment due to the non-standard techniques employed to inject DC power into the 1000BaseT connection between the PIDU Plus and the ODU. Plugging the ODU into other equipment may damage the ODU and/or the other equipment.

Step 1: Undo the retaining

screw and hinge back the cover

Step 3: Replace the cover and secure with the retaining screw

Step 2: Plug in the ODU into the PIDU

Plus Cable ensuring that it snaps home

Page 54

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

Figure 23 Making the Network Connection at the PIDU Plus

7.7.9 Mounting the PTP 500 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.

Plus to the wall using the lugs provided

Make connections as per Section 7.7.8

Page 55

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 ﬁt 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. As shown in Figure 24. 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.

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, ﬁlling up the drip loop and eventually ﬁnding its way into the PIDU Plus. To protect against this the outer protective layer of the cable can be opened up at the bottom of the drip loop to allow this moisture to escape.

7.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 conﬁgured with an IP address of 169.254.n.n and subnet mask of 255.255.0.0 where n is any value between 1 and 254 but excluding 1.1 or 1.2. If the default addresses of the unit 169.254.1.1/2 clashes with an address you are already using on your LAN, or you are not sure, you should set up an isolated LAN. As the LAN connection presented at the PIDU Plus has a default conﬁguration

Figure 24 PTP 500 Series PIDU Plus Drip Loop Conﬁguration

Page 56

Installation

as a hub/switch (and auto-sensing MDI/MDIX cross over is employed), connection can be made directly to the computer using a standard CAT 5 patch cable.

Before physical installation takes place the units to be installed should be set up as described in the Section 8.3.4 "Install Pages". It is recommended that this procedure be carried out on the bench before physical installation commences. Providing it is safe to do so, the installer should take the process to the point where a radio link is established before proceeding to the installation site.

NOTE: It is possible that some units may not be accessed using the above default URL. This is because these units may have been previously conﬁgured with IP addresses 10.10.10.11 (Master) and 10.10.10.10 (Slave). Therefore, users must use the URL http://10.10.10.10/ and/or URL http://10.10.10.11/ to conﬁgure the units. Please ensure that a computer with web browsing capabilities is conﬁgured with an IP address of 10.10.10.n, where n is any value between 2 and 254 but excluding 10 and 11, to conﬁgure these units.

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

Rx Power

wanted signal

Synchronized Fast broken tone Demodulating the

Rx Power

wanted signal

Registered Solid tone Both Master and Slave

Rx Power units exchanging Radio layer MAC management messages

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

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.

Page 57

Installation

may be suﬀering 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.

For the ease of alignment, both Master and Slave units use the install tones in the same way but with some small behavioral diﬀerences. This allows the installer to install the Slave unit ﬁrst and carry out the initial alignment with the Master unit if desired. However, due to the behavioral diﬀerences of Master and Slave units, it is recommended that the Master unit is installed ﬁrst and the initial alignment carried out at the Slave unit.

Note also that there is a graphical installation screen (Section 8.3.5 "Graphical Install") available using the web interface that displays the state of the link during the alignment process (up green,Down, red).

The following behavior should be noted:

• When ﬁrst started up and from time to time, the Master unit will carry out a band scan to determine which channels are not in use. During this time, between 10 and 15 seconds, the Master unit will not transmit and as a consequence of this neither will the Slave unit. During this time the installation tone on the master unit will drop back to the band scan state, and the Slave unit will drop back to the Scanning state with the pitch of the tone set to the background noise level. Alignment of the unit should cease during this time.

• The master unit can take up to 60 seconds in 0-40km (0-25 miles) mode, 90 seconds in 0-130km (0-81 miles) mode and 120 seconds in 0-200km (0-124 miles) mode to determine the range of the link being installed7. The Master unit will remain in the Scanning state until the range of the link has been established. The Master unit will only move to the Synchronized state when the range of the link has been established.

• If, at the end of the ranging period, the Registered state is not achieved due to interference or other reasons, the Master unit will retry twice more on the same channel before moving to another available channel. Should this occur it might take a number of minutes to establish a link in the Registered state.

• The Slave unit does not have a ranging process. The slave unit will change to the Synchronized state as soon as the wanted signal is demodulated.

When the alignment process is complete the installer MUST REMEMBER TO DISARM8BOTH UNITS in the link as described in

Section 8.3.4 "Install Pages". This is necessary in order to:

• Turn oﬀ 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

If the unit is operating where mandatory radar avoidance algorithms are implemented the ranging behavior for the PTP 500 Series Bridge may be aﬀected. 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.

After 24 hours, the units will be disarmed automatically provided that they are armed and that the link is UP.

Page 58

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 ﬁnal section is the system administration section. This section is password protected and allows the system administrator to perform all the day-today administrative procedures, e.g. software upgrade and performing conﬁguration 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 79.

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

The web pages have also been tested with Firefox 2.0.0.12. Other browsers may function correctly but have not been tested.

Page 59

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 pointto-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 ﬁrst 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 identiﬁcation of the unit, network or building.

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, e.g., 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 explains how to set the clock.

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 26 System Summary Page

Page 60

Web Page Reference

Figure 27 Alarm Warning Triangle

The following system alarms are deﬁned:

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.

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 misconﬁgured Target MAC Address will normally fail to establish a wireless link. However, rare circumstances may establish a partial wireless link and detect this situation. NB: A non-OK value on start-up, or a change of value during operation, may generate an SNMP trap and/or SMTP email alert.

Install Arm State: This alarm warns when a wireless unit is in installation mode. After installation the wireless unit should be disarmed. This will increase the wireless link’s data-carrying capacity and stop the installation tone generator. The wireless link is disarmed from the ‘Installation Wizard’ see Section 8.3.4.4 “Disarm”. Note that 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, 5.4 GHz and 2.5 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.

Page 61

Web Page Reference

Incompatible Master and Slave: A non-zero value indicates that the master and slave ends of the wireless link are diﬀerent hardware products, or have diﬀerent 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 Conﬁguration 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 conﬁguration 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.

SNTP Synchronization Failed: This warning indicates that SNTP has been enabled but that the unit is unable to synchronize with the speciﬁed SNTP server. Section 8.3.10.8 “SNTP (Simple Network Time Protocol) explains how to conﬁgure 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 SNMP Interface (see Section 8.3.10 “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 Disable Warning: This warning is displayed if the Ethernet link has been administratively disabled via the SNMP Interface (see Section 8.3.10 “Remote Management Page”). The Ethernet Interface MIB-II ifAdminStatus attribute has been set to DOWN. To enable the Ethernet interface, set the ifAdminStatus attribute to UP. Note that a change of state may generate an SNMP trap and/or SMTP email alert.

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.

Fiber Link Status: If the ﬁber link is not OK, there are two possible causes: Either the ﬁber link has been installed but disabled (because the license key does not include ﬁber support), or the link could not be established even though an optical carrier was detected (due perhaps to a broken TX ﬁber, or the link is disabled at the ﬁber link partner). Note that a change of status may generate an SNMP trap and/or SMTP email alert.

TDD Synchronization Status: Current status of the TDD Synchronization (acquiring synchronization, no timing reference and timing system not connected). Note that a change of state may generate an SNMP trap and/or SMTP email alert.

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.

Page 62

Web Page Reference

The page is subdivided into three main categories Equipment, Wireless and Ethernet/Internet. The ‘Equipment’ section contains the unit’s inventory and identiﬁcation 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 conﬁgured to refresh itself at an operator deﬁned 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

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 (2.5, 5.4 or 5.8 GHz), SSS is the System Release, XX is the major release version and YY is the minor release version.

Page 63

Web Page Reference

Hardware Version: The hardware version attribute contains all the combined hardware version information. The attribute is formatted as DXX-RYY-Z where DXX contain the version of the digital card, RYY contains the version of the RF (radio frequency) card and Z describes the antenna type which can be I (integrated) or C (connectorized).

Region Code: The region code is used by the system to constrain the wireless to operate within regulatory regime of the particular country. The region code is encoded in the product license key. If the operator wishes to change region code, a new license key must be obtained from Motorola or the local point-to-point distributor / system integrator.

Elapsed Time Indicator: The elapsed time indicator attribute presents the total time in years, days, hours, minutes and seconds since the last system restart. The system can restart for several reasons, e.g. 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.

Ethernet Speed and Duplex: The negotiated speed and duplex setting of the Ethernet interface. The speed setting is speciﬁed in Mbps. Full Duplex data transmission means that data can be transmitted in both directions on a signal carrier at the same time. For example, on a local area network with a technology that has full duplex transmission; one workstation can be sending data on the line while another workstation is receiving data. Half Duplex data transmission means that data can be transmitted in both directions on a signal carrier, but not at the same time. For example, on a local area network using a technology that has half duplex transmission, one workstation can send data on the line and then immediately receive data on the line from the same direction in which data was just transmitted.

Remote IP Address: Hyperlink to the other side of the Link. The IP address of the peer link is displayed if the Link is UP, otherwise “unavailable” is displayed.

Refresh Page Period: The Status page refreshes automatically according to the setting entered here (in seconds). This attribute is only displayed when the user is logged on as System Administrator.

Wireless Link Status: As the attribute name suggests it displays the current status of the wireless link. A state of ‘Up’ on a green background indicates that a point-to-point link is established. A state of ‘Down’ on a red background indicates that the wireless link is not established.

Maximum Transmit Power: The maximum transmit power that the local wireless unit is permitted to use to sustain a link.

Remote Maximum Transmit Power: The maximum transmit power that the remote wireless unit is permitted to use to sustain a link.

Transmit Power: Transmit power histogram10is 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.

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

Page 64

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 10 “histograms”.

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 10 “histograms”.

Link Loss: The link loss is the total attenuation of the wireless signal between the two point-topoint units. See footnote 10 “histograms”.

The link loss calculation presented below:

Pl= PT− PR+ gT+ g

(4)

Where

= Link Loss dB

= Transmit power of the remote wireless unit dBm

= Received signal power at the local unit dBm

gt, gr= Antenna gain at the remote and local units respectively11dBi

Equation - 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 10 “histograms”. Expected data rates can be found in Section 14 “Data Rate Calculations”.

Link Capacity: The maximum aggregate data rate capacity available for user traﬃc, 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 where data rate calculations plots are given for each available modulation mode.

The antenna gain of the 500 Series bridge (23.5 dBi) is used unless one or both of the units is a Connectorized

version.

Page 65

Web Page Reference

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 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-conﬁgured 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 range12between the 500 Series bridge ODUs.

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:

• Conﬁguration

• Statistics

• The Installation Wizard

• Software Upgrade

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 “Properties”.

Page 66

• Spectrum Management including DFS

• Remote management

• Diagnostics Plotter

• Password Management

• License Key Management

• Properties

• System Reboot

8.3.1 System Conﬁguration

The conﬁguration of the 500 Series Bridge is organized into three sections:

• General conﬁguration

• LAN conﬁguration

Web Page Reference

• Telecoms Conﬁguration

• Save and Restore

The general conﬁguration allows modiﬁcation of high level administrative (descriptive) attributes and high level wireless conﬁguration.

The LAN conﬁguration sub menu allows the system administrator to modify the Ethernet and IP conﬁguration of the 500 Series Bridge.

The telecoms submenu displays the current status of the telecoms interface and allows the conﬁguration of interface loopbacks.

The save and restore submenu allows the system administrator to backup and restore the bridge conﬁguration. It is recommended after a unit has been successfully installed; a copy of the active conﬁguration is taken and archived by the system administrator.

8.3.1.1 General Conﬁguration Page

The general conﬁguration page (Figure 30) is used by the system administrator to conﬁgure the 500 Series Bridge’s high level administrative (descriptive) attributes and high level wireless conﬁguration.

Page 67

Web Page Reference

Figure 30 System Conﬁguration Page

While the majority of the system conﬁguration is entered during installation and should never require changing, this page oﬀers the system administrator the ability to change the basic system parameters for both the wireless and Ethernet components.

Link Name: User deﬁned 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

modiﬁed using the Installation Wizard pages. See Section 8.3.4 “Install Pages”

Max Receive Modulation Mode: This is the maximum mode the unit will use as its adaptive modulation. By default the Max Receive Modulation Mode is the highest mode available.

For minimum error rates on TDM links the user should set the maximum modulation mode to 64QAM 0.75 at both ends of the link.

Ethernet Capped Max Wireless Speed: When enabled this option will cap the wireless speed to a mode that the connected Ethernet connection can sustain.

Maximum Transmit Power: This speciﬁes the maximum transmit power in dBm of the system. It is country dependent and although the user can change this in 1dB steps, it will be limited to that country’s regulations13.

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 License Key, an additional facility is provided on the conﬁguration page that allows the transmitted power to be reduced by 19dB compared to the maximum allowed with a simple single step control.

Page 68

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 beneﬁt to other users of the band, e.g. ﬁxed satellite links.

8.3.1.2 LAN Conﬁguration Page

The LAN conﬁguration page (Figure 31) is used by the system administrator to conﬁgure the 500 Series Bridge’s LAN interface.

Web Page Reference

Figure 31 LAN Conﬁguration 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 ﬂow of network traﬃc between hosts to be segregated based on a network conﬁguration.

Gateway IP Address: The IP address of a computer / router on the current network that acts as a gateway.

Page 69

Web Page Reference

VLAN High Priority Traﬃc Threshold: All packets with an 802.1P priority tag greater than or equal to the indicated value will be treated as a high priority packet for transmission over the wireless link.

Use VLAN For Management Interfaces: This controls whether the management interfaces (WWW/SNMP/SMTP/SNTP) use 802.1Q VLAN tags or not. See

Section 8.3.1.3 “LAN Con-

ﬁguration Page - Use VLAN For Management Interface”.

Ethernet Auto Negotiation: This enables the Ethernet conﬁguration to be forced rather than auto negotiated.

Caution:The conﬁguration should only be forced if you are having problems with auto negotiation. You must ensure that you conﬁgure both this unit and the Ethernet port to which it is connected identically. If you force a ﬁxed Ethernet Conﬁguration on the 500 Series bridge then you MUST also force the same ﬁxed conﬁguration on the equipment to which it is connected. If you fail to force the conﬁguration of the connected equipment, its automatic conﬁguration mechanisms will normally cause a duplex mismatch, and you will receive greatly reduced throughput!

When Ethernet Auto Negotiation is Disabled the format of the LAN conﬁguration page will change see Section 8.3.1.4 “LAN Conﬁguration Page – Manual Ethernet Conﬁguration”.

Auto Neg Advertisement: This controls the rates that the auto negotiation mechanism will advertise as available. Warning: Over the air throughput will be capped to the rate of the Ethernet interface at the receiving end of the link.

Ethernet Auto Mdix: This enables/disables the Auto Medium Dependent Interface (MDI)/Medium Dependent Interface Crossover (MDIX) capability. Default is “Enabled”.

Drop Ethernet Link On Wireless Link Down: When this option is enabled the Ethernet link is momentarily dropped when the wireless link goes down. This feature is used to indicate to the connected network equipment that this Ethernet link is no longer available, thus causing STP (Spanning Tree Protocol) to re-route packets through an alternate link.

Local Packet Filtering: When Local Packet Filtering is “Enabled”, the bridge learns the source MAC addresses of devices transmitting Ethernet packets on the local Ethernet network, and only bridges packets to the remote unit if the destination MAC address has not been learned as a ’local’ device. When Local Packet Filtering is ‘Disabled’ the bridge does not learn the source MAC addresses of devices transmitting Ethernet packets on the local Ethernet network, and bridges ALL Ethernet packets received to the remote unit. Local Packet Filtering should be disabled when external Ethernet switching hardware or a router is present. The default setting for Local Packet Filtering is disabled.

All of the above attributes are non-volatile, once set they will be used by the unit even after a power on reboot. A number of attributes, such as IP Address, Subnet Mask and Gateway IP Address and VLAN settings will require a reboot before they are used. If any of these attributes are changed a reboot screen appears asking the user to verify the reboot (

Figure 32 or Figure 33).

Page 70

Web Page Reference

Figure 32 Conﬁguration Reboot Page

Figure 33 Conﬁguration Reboot Page

– Ethernet Auto Negotiation Disabled

This will be followed by a pop-up dialogue box asking to conﬁrm 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.

8.3.1.3 LAN Conﬁguration Page – Use VLAN For Management Interfaces

The layout of the LAN Conﬁguration 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.

Page 71

Web Page Reference

Caution: You must ensure that you can access the VLAN which you conﬁgure here, otherwise you will be unable to access the unit following the next reboot.

Caution: The PTP 500 is only compatible with single VLAN tagged packets. Any packet with two or more tags will be ignored.

Figure 34 VLAN Conﬁguration Fields

VLAN Management VID: This 802.1Q VLAN 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 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 conﬁgured 802.1Q VLAN Management VID; otherwise packets with any VID will be accepted.

Page 72

Web Page Reference

8.3.1.4 LAN Conﬁguration Page – Manual Ethernet Conﬁguration

Figure 35 LAN Conﬁguration Page – Manual Ethernet Conﬁguration

Force Conﬁguration: This option allows the user to force the speed and duplex setting of the

Ethernet interface.

Warning: Over the air throughput will be capped to the rate of the Ethernet interface at the receiving end of the link

Page 73

Web Page Reference

8.3.1.5 Save and Restore Conﬁguration File

The save and restore feature of a PTP 500 Series Bridge allows the system administrator to backup the operation conﬁguration 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 ﬁeld, the replacement unit can be reconﬁgured by simply playing back the saved conﬁguration ﬁle.

To save the conﬁguration ﬁle click on the ‘Save Conﬁguration File’ button ( the conﬁguration ﬁle (.cfg) to the hard drive of your computer

14 15

Figure 36) and save

Figure 36 Save and Restore Conﬁguration Page

There is a feature of Internet Explorer (all versions) that will always look at the content of any downloadable ﬁle as make an assessment whether to treat the ﬁle as an ASCII or binary ﬁle. Unfortunately the conﬁguration ﬁle is always treated as ASCII and the browser attempts to display it instead of downloading it. Firefox (all versions) makes no such assumptions.

The conﬁguration ﬁle 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.

Page 74

Web Page Reference

Figure 37 Save Conﬁguration File Screen

Page 75

Web Page Reference

The conﬁguration ﬁle is encoded using an ASCII encoding scheme. An example is show in

Figure 38.

Figure 38 PTP 500 Example Conﬁguration File

CAUTION: The conﬁguration ﬁle is currently restricted to a single software version and can

only be restored into a wireless unit operating the software version indicated in the conﬁguration ﬁle header.

The conﬁguration ﬁle can also be used when swapping out a faulty wireless unit. If one of the wireless units is replaced on a wireless link a conﬁguration ﬁle captured from the faulty unit can be uploaded into the new unit to speed up replacement. It should be noted that when placing a conﬁguration ﬁle into a wireless unit with a diﬀerent 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 conﬁguration ﬁles can be performed using the Restore conﬁguration tool. Using the browser button to locate the conﬁguration ﬁle you wish to restore then click the ‘Restore Conﬁguration File and Reboot’ button (Figure 39). The user will then be prompted to conﬁrm the action (

Figure 40)

Page 76

Web Page Reference

Figure 39 Restore Conﬁguration File Pop Up Screen

Figure 40 Reset Conﬁguration and Reboot Conﬁrmation Pop-up

Page 77

Web Page Reference

On conﬁrmation the PTP 500 Series Bridge will:

• Upload the conﬁguration ﬁle

• Perform data integrity checking

• Erase previous conﬁguration

• Apply the new conﬁguration

• Restart

After the unit has restarted the entire conﬁguration from the conﬁguration ﬁle 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 conﬁguration ﬁle, Figure 38.

CAUTION: A reboot is always required to restore a conﬁguration ﬁle.

Page 78

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.

Web Page Reference

Figure 41 System Statistics

Wireless Tx Packets: This displays the total number of good packets the bridge has sent for

transmission by the wireless interface16.

Wireless Rx Packets: This displays the total number of good packets the bridge has received from the wireless interface. See footnote 16 “number of packets”.

The number in between brackets displays the number of packets received since the last page refresh.

Page 79

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 16 “number of packets”.

Ethernet Rx Packets: This displays the total number of good packets the bridge has received from the local Ethernet interface. . See note See footnote 16 “number of packets”.

Packets To Internal Stack: This displays the total number of good packets the bridge has transmitted to the internal stack (e.g., ARP requests, PING requests, HTTP requests). See footnote 16 “number of packets”.

Packets From Internal Stack: This displays the total number of good packets the bridge has received from the internal stack (e.g. ARP responses, PING replies, HTTP responses). See

footnote 16 “number of packets”.

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 10 “histograms”. 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 10 “histograms”. 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 Note

15. Expected data rates can be found in Section 14 “Data Rate Calculations”.

Link Capacity: The maximum aggregate data capacity available for user traﬃc 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 ﬁgure if the link isn’t fully loaded by the current traﬃc proﬁle.

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 eﬀective 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: The modulation mode currently being used on the receive channel. The number in brackets after the modulation mode and coding rate string is the eﬀective 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-conﬁgured Target Modulation Mode

Page 80

Web Page Reference

• 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 10 “histograms”.

Wireless Link Availability: Expresses the link availability as a percentage of time since the ﬁrst 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.

Page 81

8.3.3 Detailed Counters Page

Web Page Reference

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 deﬁnitions:

Tx & Rx Octets: Total number of octets (bytes) transmitted or received over the interface.

Rx Drops: Frames dropped due to lack of receive buﬀer. 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.

Rx Multicasts: Total number of good multicast packets.

Page 82

Web Page Reference

Rx CRC and Align: Total number of packets with CRC or frame alignment errors.

Rx Undersize: Total number of packets received that are less than 64 bytes and have a valid

CRC.

Rx Oversize: Total number of packets received that are greater than the maximum number of bytes with a valid CRC.

Rx Fragments: Total number of packets that are less than 64 bytes with an invalid CRC (these packet types are also known as runts).

Rx Jabbers: Total number of packets received that are greater than the maximum number of bytes with an invalid CRC.

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.

Tx Multicasts: Total number of good multicast packets.

Tx Collisions: Total number frames experiencing collisions.

Tx FIFO Drops: Total number frames dropped due to lack of capacity in the transmit buﬀer,

for example when the 500 Series bridge is connected to the local Ethernet at a connection speed of less than 1 Gbps.

Rx & Tx High Priority: Total number of received or transmitted frames marked as high priority.

Rx & Tx Low Priority: Total number of received or transmitted frames marked as low priority.

Rx & Tx Pause Frames: Total number of received or transmitted pause frames.

Statistics Page Refresh Period: The statistics page refreshes automatically according to the

setting entered here (in seconds).

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 conﬁguration process. The actual installation process is described in Section 8.3.4.1 “Manually Conﬁguring the Wireless Units”.

All wireless links are shipped as paired units. They are pre-conﬁgured at the factory so that they can be installed without the user supplying any conﬁguration. Each wireless link is shipped with a quick start guide. Attached to the quick start guide is a summary of the pre-conﬁgured conﬁguration data. committed to the wireless unit’s non-volatile storage.

Table 12 shows a sample link conﬁguration. The values highlighted have been

Page 83

Web Page Reference

Example PTP 500 Series Conﬁguration Data

For your convenience these two units have been pre-conﬁgured as a 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

Conﬁgured as:

Master Slave

Target MAC address Target MAC address

00:04:56:10:00:A0 00:04:56:10:00:96

License key License Key

0557-D8B0-47A1-B0DD 534F-4F54-D1B0-E2DA

IP Address IP Address

169.254.1.2 169.254.1.1

Table 12 500 Series Bridge Factory Conﬁguration Values

The factory default conﬁguration is limited in range to 40 Km (25 miles). If you wish to install a wireless link with a range of > 40 Km (> 25 miles) and < 200 Km (< 124 miles) or < 5 Km (< 3 miles) you must follow the steps in Section 8.3.4.1 “Manually Conﬁguring The Wireless Units”.

The factory default conﬁguration is set to Region 26. Region 26 allows the 500 Series bridge a maximum transmit power of 25 dBm. If the local regulatory regime limits the maximum transmit power (EIRP) to less than 25 dBm you should obtain a new license key containing the correct region code from your local distributor or direct from Motorola. Alternatively in the short term, you should reduce the maximum transmit power by following the procedures in Section 8.3.4.1 “Manually Conﬁguring The Wireless Units”.

8.3.4.1 Manually Conﬁguring The Wireless Units

If the installer / system administrator wishes, they may modify the default installation conﬁguration. If only the IP addresses (network conﬁguration) are incorrect it is recommended that the values are changed via the conﬁguration menu (Section 8.3.1.2 “LAN Conﬁguration Page”). If

Page 84

Web Page Reference

any other parameters require modiﬁcation 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 speciﬁc parameters in to the unit.

Figure 43 License Key Data Entry

A license key is programmed into each unit during production and can be found written on the Conﬁguration 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 Conﬁguration

Step 1 of the installation wizard requires the installer to enter the Internet Protocol (IP) conﬁguration.

Page 85

Web Page Reference

Figure 44 Installation Wizard Internet Protocol Conﬁguration

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 ﬂow of network traﬃc between hosts to be segregated based on a network conﬁguration. By organizing hosts into logical groups, subnetting can improve network security and performance. Gateway IP Address: The IP address of a computer / router on the current network that acts as a gateway. A gateway acts as an entrance / exit to packets from / to other networks.

Use VLAN Management Interface:Controls whether the management interfaces (HTTP/SNMP /SMTP/SNTP) use a VLAN. Selecting this option presents the user with extra ﬁelds in which to enter the Management VLAN ID, Priority and whether to validate the VLAN ID. If the user modiﬁes this control, a warning dialog is displayed see Figure 45.

Telecoms Interface This allows the activation of the 500 Series bridge telecoms interface. If the selection options are disabled, T1 or E1 note mixed T1/E1 conﬁgurations are not permitted.

Page 86

Once complete, click the ‘Submit Internet Protocol Conﬁguration’ button or the ‘Next’ link.

8.3.4.3 Wireless Conﬁguration

Step 2 of the installation wizard requires the installer to enter the wireless conﬁguration parameters.

Web Page Reference

Figure 45 VLAN Warning

Figure 46 5.8 GHz and 5.4 GHz Variants -

Installation Wizard Wireless Conﬁguration

Page 87

Web Page Reference

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 ﬁeld or the units conﬁguration has been erased).

Master Slave Mode:At this point it is necessary to decide which end will designate a Master.

The Master unit is the controlling unit with respect to the point-to-point link and its maintenance. The master transmits until the link is made, while the Slave listens for its peer and only transmits when the peer has been identiﬁed.

Link Mode Optimization:Optimizes the link behavior according to the type of traﬃc that will be bridged. There are two modes to choose from: IP and TDM.

In IP Mode, the PTP 500 product runs an Adaptive TDD scheme. Basically an unloaded link runs 10:10 mode (10 OFDM bursts alternately in each direction). A sustained traﬃc load in one direction for example may cause a threshold to be reached where the TDD mode automatically adapts to say 20:10. If the load continues to increase, then the TDD structure may adapt even further through 30:10 to 40:10. This is a state of maximum link asymmetry (40 OFDM bursts in one direction compared with 10 in the other). If the load increases in BOTH directions, then the TDD structure can adapt from 10:10, through 20:20, 30:30 and ﬁnally 40:40. This is a state of maximum aggregate throughput. So if three out of these combinations are considered; 10:10, 40:10 and 40:40 they would give the following characteristics:

10:10: equal performance in each direction, lowest aggregate throughput and lowest Latency.

40:10: achieves maximum one way throughput performance, to the detriment of both latency and

throughput in the opposite direction.

40:40: Maximum link aggregate rate, balanced performance in each direction, higher latency.

Note that there is an engineering trade-oﬀ between the ﬂexibility of ATDD and Latency as follows: When the TDD structure changes, there will be a short term impact on Latency for a few Frames. This would not aﬀect the steady state long term average latency, but could be recorded as a Maximum latency. This aﬀect may be ampliﬁed for short Latency tests or if the traﬃc loading is oscillating either side of a boundary condition. As the TDD burst length increases, Traﬃc in each direction will have to wait longer before a Transmit window is available, but more data can be sent during the burst. There is an impact on latency but it varies depending upon installation range, Frame size and modulation mode.

In TDM mode, two major diﬀerences in link behaviour occur compared with IP mode. First the TDD structure is ﬁxed symmetrically. Either 10:10, 20:20, 30:30 or 40:40 based upon the installed range.

Secondly, the point at which a modulation mode changes for given RF conditions is more conservative. In practice, this means that the link will typically stay in a lower modulation mode, but with increased tolerance to RF variability.

Page 88

Web Page Reference

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-oﬀ 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. Value is 15 MHz.

Spectrum Management Control:Is used to conﬁgure 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 co-channel interference. Fixed frequency mode allows the installer to ﬁx transmit and receive frequencies on the units. The frequencies may be conﬁgured symmetrically or asymmetrically.

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 oﬀset. It eﬀectively slides the channelization up or down. See Sections Section 5.5 “5.4 GHz Speciﬁc Frequency Planning Considerations” and Section 5.6 “5.8 GHz Speciﬁc Frequency Planning Considerations” depending on the frequency variant.

Warning: The lower center frequency attribute must be conﬁgured 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 ﬁx the Transmit and the Receive frequencies for a wireless link. The settings must be compatible at each end of the link. Once conﬁgured 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 ﬁxed frequency conﬁguration for a 30 MHz channel bandwidth. 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 conﬁguring 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 ﬁxed Tx frequency box is limited to that raster.

Page 89

Web Page Reference

Figure 47 5.8 GHz and 5.4 GHz 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 satisﬁed with the wireless conﬁguration options then the “Submit Wireless Conﬁguration” button or the “Next” link should be clicked.

Page 90

Web Page Reference

Figure 48 5.8 GHz and 5.4 GHz Variants -

Installation Wizard Conﬁrm Conﬁguration

If the settings are correct and appropriate, click the “Conﬁrm Conﬁguration, Arm Installation and Reboot” button. The user will now be prompted to conﬁrm the action (Figure 49).

Page 91

Web Page Reference

Figure 49 Reboot Conﬁrmation Pop Up

All the attributes are committed to non-volatile memory. Immediately following the write to nonvolatile memory the unit is reset. Note: If you have changed the Ethernet parameters you must reconnect using the correct network and address settings.

Page 92

8.3.4.4 Disarm

Step 5 of the installation wizard is the disarm phase.

Web Page Reference

Figure 50 5.8 GHz and 5.4 GHz Variant - Disarm Installation

Page 93

Web Page Reference

Once Section 8.3.4.3 “Wireless Conﬁguration” is complete pressing the “Disarm Installation Agent” button completes the installation process17and the audible installation tone will be switched oﬀ. If the installer wishes to modify the installation conﬁguration 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 one of two possible conﬁguration pages, see Figure 52 and Figure 51. The screen presents hyperlinks to the main conﬁguration and spectrum management pages.

Figure 51 Optional Post Disarm Conﬁguration 2

Figure 52 Optional Post Disarm Conﬁguration 1

After installation the system administrator may wish to modify the wireless units descriptive conﬁguration (link name and link location). In addition the system administrator may wish to change the spectrum management conﬁguration 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 conﬁguration is taken. Hyperlinks are provided on the post disarm page for ease of use.

The installation process is completed when both ends of the link are ‘disarmed’.

Page 94

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 53. Both the PDA and the large format installation screen have the same content and only diﬀer in size. The PDA installation screen is 232 by 220 pixels to be compatible with the typical size of a PDA screen.

Web Page Reference

Figure 53 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.

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://<ip-address>/pda.cgi. It should be noted that this link is only available after the user has logged in as system administrator.

The large screen version of the graphical user interface is available as a submenu option of the installation wizard.

Page 95

8.3.6 Software Upgrade

The 500 Series system has two software image banks; one is a ﬁxed image which is stored in protected non-volatile memory and cannot be modiﬁed by the user. The second bank is used by the system administrator to upgrade the ﬁrmware when necessary. Figure 54 shows the main software upgrade web page.

Web Page Reference

Figure 54 Software Upgrade

The ‘Fixed’ or ‘Recovery’ image is used by the System Administrator to:

• Reset Ethernet conﬁguration to default settings

• Erase Conﬁguration

• Upgrade software

For a full description of the Recovery image see Section 9 “Recovery Mode”.

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 ﬁle. Once the zip ﬁle has been downloaded, the user should extract the PTP 500 Series Software image, identiﬁable by its ‘.dld’ ﬁle extension.

The ﬁrst step (Figure 54) 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 upgrade process18.

During the software upgrade process, ensure that the remote end is upgraded ﬁrst using the wireless connection and then the local end can be upgraded.

Page 96

Web Page Reference

The software image will now be uploaded to the unit. This upload should only take a few seconds. Once complete the image is veriﬁed 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 55)

Figure 55 Software Upgrade Image Check

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.

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 ﬁxed 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 56). 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.

Page 97

Web Page Reference

Figure 56 Software Download Progress Indicator

Figure 57 Software Upgrade Complete

When the software image has been written to non-volatile memory Figure 57 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 conﬁrm this action as shown in

Figure 58.

Figure 58 Reboot Conﬁrmation 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.

Page 98

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 predeﬁned overlapping channels. There are a diﬀerent number of channels, depending on the raster mode selected. Each channel occupies 15 MHz of wireless spectrum and is oﬀset 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.

Web Page Reference

The default channelization can be modiﬁed by varying the lower center frequency attribute in the installation wizard - see Section 8.3.4.3 “Wireless Conﬁguration”. See Section 5 “General Considerations” for more detail.

8.3.7.2 Spectrum Management Measurements

The 500 Series Bridge performs two mean signal measurements per TDD cycle, per channel. This mean measurement represents the mean received signal power for the 40 microseconds measurement period.

The Spectrum Management algorithm collects measurements equally from all channels.

This process is called the Channel Availability Check (hereafter referred to by the acronym CAC).

The CAC uses a round-robin channel selection process to collect an equal amount of measurements from each channel. It is important to note that the CAC measurement process is not altered by the channel barring process. Measurements are still collected for all channels irrespective of the number of barred channels.

8.3.7.3 Measurement Analysis

Spectrum Management uses statistical analysis to process the received peak and mean measurement. The statistical analysis is based on a ﬁxed, one minute, measurement quantization period. Spectrum Management collects data for the speciﬁed quantization period and only at the end of the period is the statistical analysis performed.

The analysis produces three key metrics for each channel:

Page 99

Web Page Reference

• 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 eﬀect of the mean of means.

Mean of Means:is the arithmetic mean19of 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. Important 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 conﬁgured during installation. All Spectrum Management conﬁguration changes MUST be performed from the master. To enforce this, the Spectrum Management web page has a diﬀerent appearance depending if you are viewing the data from the master or slave.

All conﬁguration changes are applied at the master only. These changes are then messaged from the master to the slave. Any Spectrum Management conﬁguration messages received at the slave are stored in non-volatile memory. This enables both master and slave to keep identical copies of Spectrum Management conﬁguration 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 conﬁguration.

The arithmetic mean is the true power mean and not the mean of the values expressed in dBm.

Page 100

Web Page Reference

Figure 59 Spectrum Management as seen from the Master

100