Cambium PTP 500 Series, PTP 54500, PTP 58500, PTP 300 Series User Manual

Cambium
PTP 500 and PTP 300 Series
User Guide

System Releases 500-05-03 and 300-05-03

Accuracy

Copyrights

Restrictions

License Agreements

High Risk Materials

While reasonable efforts have been made to assure the accuracy of this document, Cambium
Networks assumes no liability resulting from any inaccuracies or omissions in this document, or
from use of the information obtained herein. Cambium reserves the right to make changes to

any products described herein to improve reliability, function, or design, and reserves the right

to revise this document and to make changes from time to time in content hereof with no
obligation to notify any person of revisions or changes. Cambium does not assume any liability
arising out of the application or use of any product, software, or circuit described herein;
neither does it convey license under its patent rights or the rights of others. It is possible that
this publication may contain references to, or information about Cambium products (machines
and programs), programming, or services that are not announced in your country. Such
references or information must not be construed to mean that Cambium intends to announce
such Cambium products, programming, or services in your country.

This document, Cambium products, and 3rd Party software products described in this document
may include or describe copyrighted Cambium and other 3
stored in semiconductor memories or other media. Laws in the United States and other
countries preserve for Cambium, its licensors, and other 3

rd

Party supplied computer programs

rd

Party supplied software certain
exclusive rights for copyrighted material, including the exclusive right to copy, reproduce in any
form, distribute and make derivative works of the copyrighted material. Accordingly, any
copyrighted material of Cambium, its licensors, or the 3

rd

Party software supplied material
contained in the Cambium products described in this document may not be copied, reproduced,
reverse engineered, distributed, merged or modified in any manner without the express written
permission of Cambium. Furthermore, the purchase of Cambium products shall not be deemed
to grant either directly or by implication, estoppel, or otherwise, any license under the
copyrights, patents or patent applications of Cambium or other 3rd Party supplied software,
except for the normal non-exclusive, royalty free license to use that arises by operation of law in
the sale of a product.

Software and documentation are copyrighted materials. Making unauthorized copies is
prohibited by law. No part of the software or documentation may be reproduced, transmitted,
transcribed, stored in a retrieval system, or translated into any language or computer language,
in any form or by any means, without prior written permission of Cambium.

The software described in this document is the property of Cambium and its licensors. It is
furnished by express license agreement only and may be used only in accordance with the
terms of such an agreement.

Components, units, or 3rd Party products used in the product described herein are NOT fault­tolerant and are NOT designed, manufactured, or intended for use as on-line control equipment
in the following hazardous environments requiring fail-safe controls: the operation of Nuclear
Facilities, Aircraft Navigation or Aircraft Communication Systems, Air Traffic Control, Life
Support, or Weapons Systems (High Risk Activities). Cambium and its supplier(s) specifically
disclaim any expressed or implied warranty of fitness for such High Risk Activities.

© 2012 - 2013 Cambium Networks Limited. All rights reserved.

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide

Safety and regulatory information

This section describes important safety and regulatory guidelines that must be observed by
personnel installing or operating PTP 500 equipment.

Important safety information

To prevent loss of life or physical injury, observe the safety guidelines in this
section.

Power lines

Exercise extreme care when working near power lines.

Working at heights

Exercise extreme care when working at heights.

Grounding and protective earth

The Outdoor Unit (ODU) must be properly grounded to protect against lightning. It is the
user’s responsibility to install the equipment in accordance with national regulations. In
the USA, follow Section 810 of the
In Canada, follow Section 54 of the
correct installation procedures for grounding the outdoor unit, mast, lead-in wire and
discharge unit, size of grounding conductors and connection requirements for grounding
electrodes. Other regulations may apply in different countries and therefore it is
recommended that installation of the outdoor unit be contracted to a professional installer.

National Electric Code, ANSI/NFPA No.70-1984

Canadian Electrical Code

. These codes describe

(USA).

PIDU

Always use the Cambium Power Indoor Unit Plus (PIDU Plus PTP 300/500/600 Series) to
power the ODU. Failure to use the Cambium supplied PIDU could result in equipment
damage and will invalidate the safety certification and may cause a safety hazard.

phn-2511_005v000 (Mar 2013)

I

Safety and regulatory information

Alternative DC supplies

If an AC supply is not required or an additional back up DC supply is required, the DC
supply is connected to the PIDU Plus DC IN terminals. This is the only method of supplying
external DC to the ODU. The DC supply must comply with the following requirements:

• The voltage and polarity is correct and is applied to the correct terminals in the PIDU.

• The power source is rated as Safety Extra Low Voltage (SELV).

• The power source is rated to supply at least 1A continuously.

• The power source cannot provide more than the Energy Hazard Limit as defined by

IEC/EN/UL60950-1, Clause 2.5, Limited Power (The Energy Hazard Limit is 240VA).

Powering down before servicing

Always power down and unplug the equipment before servicing.

Lightning protection unit (LPU)

Do not remove the LPU printed circuit board when the LPU is connected to the power
supply, as high voltages are present.

Drop cable tester

The drop cable tester must NEVER be used at the ODU end connected to power from the
PIDU. It must only be used (with a multimeter) to test a cable with an ODU attached, not a
cable with a PIDU attached. This is because the PIDU voltage exceeds the limit allowed in
some countries for safe handling in wet conditions and therefore may create a safety
hazard.

Primary disconnect device

The main power supply is the primary disconnect device.

External cables

Safety may be compromised if outdoor rated cables are not used for connections that will
be exposed to the outdoor environment.

Grounding PTP-SYNC

In order to meet the safety requirements for deployment in Australia and New Zealand
(AS/NZS 60950-1), the PTP-SYNC unit, if deployed, must be grounded to a Protective
Ground in accordance with Local Electrical Regulations.

II

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide

RF exposure near the antenna

Strong radio frequency (RF) fields will be present close to the antenna when the
transmitter is on. Always turn off the power to the ODU before undertaking maintenance
activities in front of the antenna.

Minimum separation distances

Install the ODUs so as to provide and maintain the minimum separation distances from all
persons.

The minimum separation distances for each frequency variant are specified in Calculated

distances and power compliance margins on page 4-28.

Important regulatory information

The PTP 500 product is certified as an unlicensed device in frequency bands where it is not
allowed to cause interference to licensed services (called primary users of the bands).

Radar avoidance

In countries where radar systems are the primary band users, the regulators have
mandated special requirements to protect these systems from interference caused by
unlicensed devices. Unlicensed devices must detect and avoid co-channel operation with
radar systems.

The PTP 500 provides detect and avoid functionality for countries and frequency bands
requiring protection for radar systems.

Installers and users must meet all local regulatory requirements for radar detection. To
meet these requirements, users must set the correct license key and region code during
commissioning of the PTP 500. If this is not done, installers and users may be liable to civil
and criminal penalties.

Contact the Cambium helpdesk if more guidance is required.

phn-2511_005v000 (Mar 2013)

III

Safety and regulatory information

USA and Canada specific information

The USA Federal Communications Commission (FCC) has asked manufacturers to
implement special features to prevent interference to weather radar systems that operate
in the band 5600 MHz to 5650 MHz. These features must be implemented in all products
able to operate outdoors in the band 5470 MHz to 5725 MHz.

Manufacturers must ensure that such radio products cannot be configured to operate
outside of FCC rules; specifically it must not be possible to disable or modify the radar
protection functions that have been demonstrated to the FCC.

In order to comply with these FCC requirements, Cambium supplies variants of the
PTP 500 for operation in the USA or Canada. These variants are only allowed to operate
with license keys and region codes that comply with FCC/IC rules. In particular, operation
of radio channels overlapping the band 5600-5650 MHz is not allowed and these channels
are permanently barred.

In addition, other channels may also need to be barred when operating close to weather
radar installations.

To ensure compliance with FCC rules (KDB 443999: Interim Plans to Approve UNII
Devices Operating in the 5470 - 5725 MHz Band with Radar Detection and DFS
Capabilities), follow the instructions in Avoidance of weather radars (USA only) on page

2-5.

Other variants of the PTP 500 are available for use in the rest of the world, but these
variants are not supplied to the USA or Canada except under strict controls, when they are
needed for export and deployment outside the USA or Canada.

Specific expertise and training required for professional installers

To ensure that the PTP 500 is installed and configured in compliance with the
requirements of Industry Canada and the FCC, installers must have the radio engineering
skills and training described in this section. This is particularly important when installing
and configuring a PTP 500 system for operation in the 5.4 GHz UNII band.

Avoidance of weather radars

The installer must be familiar with the requirements in FCC KDB 443999. Essentially, the
installer must be able to:

• Access the FCC data base of weather radar location and channel frequencies.

• Use this information to correctly configure the product (using the GUI) to avoid

operation on channels that should be barred according to the guidelines that are
contained in the KDB and explained in detail in this user guide.

IV

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide

External antennas

When using a connectorized version of the product (as compared to the version with an
integrated antenna), the conducted transmit power must be reduced to ensure the
regulatory limit on transmitter EIRP is not exceeded. The installer must have an
understanding of how to compute the effective antenna gain from the actual antenna gain
and the feeder cable losses.

The product GUI automatically applies the correct conducted power limit to ensure that it
is not possible for the installation to exceed the EIRP limit, when the appropriate values
for antenna gain and feeder cable losses are entered into the GUI.

Ethernet networking skills

The installer must have the ability to configure IP addressing on a PC and to set up and
control products using a web browser interface.

Lightning protection

To protect outdoor radio installations from the impact of lightning strikes, the installer
must be familiar with the normal procedures for site selection, bonding and grounding.
Installation guidelines for the PTP 500 can be found in Chapter 2: Planning considerations
and Chapter 5: Installation.

Training

The installer needs to have basic competence in radio and IP network installation. The
specific requirements applicable to the PTP 500 should be gained by reading Chapter 5:

Installation and Chapter 6: Configuration and alignment and by performing sample set

ups at base workshop before live deployments.

phn-2511_005v000 (Mar 2013)

V

Safety and regulatory information

VI

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide

Contents

Safety and regulatory information .................................................................................... I

Important safety information .................................................................................................... I

Important regulatory information ......................................................................................... III

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

General information ....................................................................................................................... 2

Contacting Cambium Networks ............................................................................................... 2

Problems and warranty .................................................................................................................. 4

Security advice ............................................................................................................................... 6

Warnings, cautions, and notes ....................................................................................................... 7

Caring for the environment ........................................................................................................... 8

Chapter 1: Product description .................................................................................. 1-1

Overview of the PTP 500 ............................................................................................................. 1-2

Purpose .................................................................................................................................. 1-2

Key features .......................................................................................................................... 1-2

Typical deployment ............................................................................................................... 1-3

System components .............................................................................................................. 1-4

Product variants .................................................................................................................... 1-5

Support for discontinued product variants .......................................................................... 1-6

Outdoor unit (ODU) .................................................................................................................... 1-7

ODU description .................................................................................................................... 1-7

ODU interfaces ...................................................................................................................... 1-8

Connectorized ODU antenna interfaces ............................................................................... 1-9

Mounting brackets ................................................................................................................ 1-9

Network connection .............................................................................................................. 1-9

Further reading on the ODU .............................................................................................. 1-10

Powered indoor unit (PIDU) ..................................................................................................... 1-11

PIDU description ................................................................................................................. 1-11

PIDU interfaces ................................................................................................................... 1-11

Redundancy and alternative powering configurations ...................................................... 1-13

Remote LEDs and recovery switch ..................................................................................... 1-14

Further reading on the PIDU .............................................................................................. 1-15

phn-2511_005v000 (Mar 2013)

i

Contents

Cabling and lightning protection .............................................................................................. 1-16

PTP and lightning protection .............................................................................................. 1-16

Outdoor connections ........................................................................................................... 1-16

Indoor connections ............................................................................................................. 1-17

Cable grounding kits ........................................................................................................... 1-17

Lightning protection units (LPUs) ...................................................................................... 1-18

Further reading on cabling and lightning protection ........................................................ 1-18

PTP-SYNC unit .......................................................................................................................... 1-19

PTP-SYNC unit description ................................................................................................. 1-19

Model number ..................................................................................................................... 1-19

PTP-SYNC unit interfaces ................................................................................................... 1-20

Further reading on PTP-SYNC ........................................................................................... 1-21

Wireless operation .................................................................................................................... 1-22

Time division duplexing ...................................................................................................... 1-22

Link mode optimization ...................................................................................................... 1-24

Link symmetry .................................................................................................................... 1-24

OFDM and channel bandwidth ........................................................................................... 1-25

Spectrum management ....................................................................................................... 1-25

Adaptive modulation ........................................................................................................... 1-27

MIMO .................................................................................................................................. 1-27

Dynamic spectrum optimization ......................................................................................... 1-28

Radar avoidance ................................................................................................................. 1-28

Security ............................................................................................................................... 1-29

Region codes ....................................................................................................................... 1-29

PTP networks ...................................................................................................................... 1-30

TDD synchronization ........................................................................................................... 1-31

Further reading on wireless operation .............................................................................. 1-33

Ethernet bridging ...................................................................................................................... 1-34

Customer network .............................................................................................................. 1-34

Management network ......................................................................................................... 1-35

Back-to-back links ............................................................................................................... 1-36

Protocol model .................................................................................................................... 1-37

Further reading on Ethernet bridging ............................................................................... 1-38

Telecoms circuits ...................................................................................................................... 1-40

Lowest telecoms modulation mode .................................................................................... 1-40

Fixed frequency operation .................................................................................................. 1-40

Further reading on telecoms circuits ................................................................................. 1-41

ii

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User Guide

System management ................................................................................................................. 1-42

Management agent ............................................................................................................. 1-42

Web server .......................................................................................................................... 1-42

RADIUS authentication ....................................................................................................... 1-45

SNMP .................................................................................................................................. 1-45

Simple Network Time Protocol (SNTP) .............................................................................. 1-46

SNMPv3 security ................................................................................................................ 1-46

System logging (syslog) ...................................................................................................... 1-49

AES license .......................................................................................................................... 1-50

Critical security parameters ............................................................................................... 1-51

Login information ................................................................................................................ 1-51

Capacity upgrades .............................................................................................................. 1-51

Software upgrade ................................................................................................................ 1-52

Recovery mode .................................................................................................................... 1-52

Further reading on system management ........................................................................... 1-53

Chapter 2: Planning considerations ........................................................................... 2-1

Regulatory planning .................................................................................................................... 2-2

Regulatory limits ................................................................................................................... 2-2

Conforming to the limits ....................................................................................................... 2-2

Available spectrum................................................................................................................ 2-3

Channel bandwidth ............................................................................................................... 2-4

Frequency selection .............................................................................................................. 2-4

Avoidance of weather radars (USA only) ............................................................................. 2-5

Site planning ............................................................................................................................... 2-6

ODU site selection ................................................................................................................ 2-6

PIDU site selection ................................................................................................................ 2-6

PTP-SYNC site selection ....................................................................................................... 2-6

Maximum cable lengths ........................................................................................................ 2-7

Wind loading ......................................................................................................................... 2-8

Link planning ............................................................................................................................ 2-10

PTP LINKPlanner ................................................................................................................ 2-10

Range and obstacles ........................................................................................................... 2-10

PTP LINKPlanner for synchronized networks .................................................................... 2-11

Path loss considerations ..................................................................................................... 2-11

System threshold, output power and link loss ................................................................... 2-13

Calculating data rate capacity ............................................................................................ 2-13

Planning for connectorized units .............................................................................................. 2-15

phn-2511_005v000 (Mar 2013)

iii

Contents

When to install connectorized units ................................................................................... 2-15

Choosing external antennas ............................................................................................... 2-15

Calculating maximum power level for connectorized units ............................................... 2-16

Calculating RF cable length (5.8 GHz FCC only) ............................................................... 2-18

Grounding and lightning protection ......................................................................................... 2-19

The need for power surge protection ................................................................................. 2-19

Standards ............................................................................................................................ 2-19

Lightning protection zones ................................................................................................. 2-20

General protection requirements ....................................................................................... 2-21

Protection requirements for a mast or tower installation ................................................. 2-22

Protection requirements for a wall installation ................................................................. 2-24

Protection requirements on a high rise building ............................................................... 2-25

Configuration options for TDD synchronization ...................................................................... 2-28

Single link configuration with PTP-SYNC .......................................................................... 2-28

Cluster with PTP-SYNC and GPS receiver ......................................................................... 2-29

Cluster with PTP-SYNC and no GPS receiver .................................................................... 2-30

Mounting options for the PTP-SYNC GPS receiver .................................................................. 2-32

GPS receiver location requirements .................................................................................. 2-32

Mounting the GPS receiver module on the equipment building ....................................... 2-32

Mounting the GPS receiver module on a metal tower or mast ......................................... 2-34

Data network planning ............................................................................................................. 2-35

VLAN membership .............................................................................................................. 2-35

Priority for management traffic .......................................................................................... 2-35

IP interface .......................................................................................................................... 2-35

Quality of service for bridged Ethernet traffic................................................................... 2-35

Back to back links ............................................................................................................... 2-36

‘Green Ethernet’ switches .................................................................................................. 2-36

Security planning ...................................................................................................................... 2-37

Planning for SNTP operation .............................................................................................. 2-37

Planning for HTTPS/TLS operation .................................................................................... 2-37

Planning for SNMP operation ............................................................................................. 2-38

Planning for SNMPv3 operation ......................................................................................... 2-40

Planning for RADIUS operation .......................................................................................... 2-44

Ordering components ............................................................................................................... 2-46

PTP 500 kits ........................................................................................................................ 2-46

Other standard components ............................................................................................... 2-50

Components required with connectorized ODUs ............................................................... 2-52

iv

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User Guide

PTP-SYNC installations ....................................................................................................... 2-60

GPS receiver installations ................................................................................................... 2-61

E1 or T1 installations .......................................................................................................... 2-62

Chapter 3: Legal informati on ..................................................................................... 3-1

Cambium Networks end user license agreement ...................................................................... 3-2

Acceptance of this agreement .............................................................................................. 3-2

Definitions ............................................................................................................................. 3-2

Grant of license ..................................................................................................................... 3-2

Conditions of use ................................................................................................................... 3-3

Title and restrictions ............................................................................................................. 3-4

Confidentiality ....................................................................................................................... 3-4

Right to use Cambium’s name .............................................................................................. 3-5

Transfer ................................................................................................................................. 3-5

Updates ................................................................................................................................. 3-5

Maintenance .......................................................................................................................... 3-5

Disclaimer ............................................................................................................................. 3-6

Limitation of liability ............................................................................................................. 3-6

U.S. government ................................................................................................................... 3-7

Term of license ...................................................................................................................... 3-7

Governing law ....................................................................................................................... 3-7

Assignment ............................................................................................................................ 3-7

Survival of provisions ............................................................................................................ 3-8

Entire agreement .................................................................................................................. 3-8

Third party software ............................................................................................................. 3-8

Hardware warranty ................................................................................................................... 3-22

Limit of liability ......................................................................................................................... 3-23

Chapter 4: Reference information .............................................................................. 4-1

Equipment specifications ............................................................................................................ 4-2

ODU specifications ................................................................................................................ 4-2

PIDU specifications ............................................................................................................... 4-3

PTP-SYNC specifications ...................................................................................................... 4-4

Wireless specifications ................................................................................................................ 4-7

General wireless specifications ............................................................................................ 4-7

Available spectrum settings .................................................................................................. 4-9

System threshold, output power and link loss ................................................................... 4-14

Data network specifications...................................................................................................... 4-21

Ethernet interfaces ............................................................................................................. 4-21

phn-2511_005v000 (Mar 2013)

v

Contents

Syslog message formats ........................................................................................................... 4-22

Format of syslog server messages ..................................................................................... 4-22

Configuration and status messages .................................................................................... 4-22

Event messages ................................................................................................................... 4-24

Compliance with safety standards ............................................................................................ 4-26

Electrical safety compliance ............................................................................................... 4-26

Electromagnetic compatibility (EMC) compliance ............................................................ 4-26

Human exposure to radio frequency energy ...................................................................... 4-27

Compliance with radio regulations ........................................................................................... 4-30

Type approvals .................................................................................................................... 4-30

FCC and ETSI compliance testing (without PTP-SYNC) .................................................... 4-31

FCC and ETSI compliance testing (with PTP-SYNC) ......................................................... 4-31

Examples of regulatory limits ............................................................................................. 4-31

Type approval status ................................................................................................................. 4-36

PTP 54500 FCC and IC status ............................................................................................ 4-36

PTP 54500 European Union status ..................................................................................... 4-37

PTP 58500 FCC and IC status ............................................................................................ 4-38

PTP 58500 European Union notification ............................................................................ 4-40

Thailand notification ........................................................................................................... 4-40

Data throughput tables ............................................................................................................. 4-41

Data throughput capacity ................................................................................................... 4-41

Range adjustment curves ................................................................................................... 4-47

Chapter 5: Installation .............................................................................................. 5-1

Preparing for installation ............................................................................................................ 5-2

Unit pre-configuration .......................................................................................................... 5-2

Safety precautions during installation ................................................................................. 5-2

Protection requirements ....................................................................................................... 5-2

Selecting installation options ............................................................................................... 5-2

Preparing personnel ............................................................................................................. 5-3

Preparing inventory .............................................................................................................. 5-3

Preparing tools ...................................................................................................................... 5-3

Installing the ODU ...................................................................................................................... 5-4

Checks and safety precautions ............................................................................................. 5-4

Selecting a position for the ODU (connectorized) ............................................................... 5-5

Mounting the ODU ................................................................................................................ 5-6

Installing connectorized antennas .............................................................................................. 5-8

Preparing for connectorized installations ............................................................................ 5-8

vi

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User Guide

Mounting and connecting antennas ..................................................................................... 5-8

Weatherproofing an N type connector ............................................................................... 5-11

Installing the drop cable and LPU ............................................................................................ 5-14

Preparing drop cables ......................................................................................................... 5-15

Assembling an RJ45 connector and gland .......................................................................... 5-16

Installing and grounding the main drop cable ................................................................... 5-18

Connecting an RJ45 and gland to a unit ............................................................................. 5-19

Disconnecting an RJ45 and gland from a unit .................................................................... 5-20

Making a drop cable ground point ..................................................................................... 5-21

Installing and grounding the drop cable at building entry ................................................ 5-25

Installing the PIDU .................................................................................................................... 5-27

Mounting the PIDU ............................................................................................................. 5-27

Connecting the PIDU to the ODU cable ............................................................................. 5-27

Preparing the PIDU to LAN cable ...................................................................................... 5-29

Installing a PTP-SYNC unit ....................................................................................................... 5-30

Preparing for PTP-SYNC installation .................................................................................. 5-30

Mounting the PTP-SYNC unit ............................................................................................. 5-31

Connecting up the PTP-SYNC unit ..................................................................................... 5-32

Powering up the PTP-SYNC installation ............................................................................. 5-34

Installing a GPS receiver for PTP-SYNC .................................................................................. 5-35

Mounting the GPS receiver ................................................................................................ 5-35

Preparing GPS drop cables ................................................................................................. 5-36

Assembling an RJ45 plug and housing for GPS .................................................................. 5-37

Assembling a 12 way circular connector............................................................................ 5-39

Installing the GPS drop cable ............................................................................................. 5-43

Grounding the GPS drop cable ........................................................................................... 5-44

Installing the GPS drop cable at building entry ................................................................. 5-46

Installing an E1 or T1 interface ................................................................................................ 5-47

Connecting the E1/T1 cable to the PIDU ........................................................................... 5-47

Testing the E1/T1 installation ............................................................................................. 5-48

Chapter 6: Configuration and alignment .................................................................... 6-1

Preparing for configuration and alignment ................................................................................ 6-2

Safety precautions during configuration and alignment ..................................................... 6-2

Regulatory compliance during configuration and alignment .............................................. 6-2

Selecting configuration options ............................................................................................ 6-2

Task 1: Connecting to the unit.................................................................................................... 6-3

Configuring the management PC ......................................................................................... 6-3

phn-2511_005v000 (Mar 2013)

vii

Contents

Connecting to the PC and powering up ............................................................................... 6-5

Logging into the web interface ............................................................................................ 6-5

Task 2: Configuring IP and Ethernet interfaces ........................................................................ 6-7

Configuring IP and Ethernet attributes ............................................................................... 6-7

Reconnecting to the management PC ................................................................................ 6-10

Task 3: Installing license keys .................................................................................................. 6-11

Checking licensed capabilities ........................................................................................... 6-11

Generating a new license key ............................................................................................. 6-13

Entering a new license key ................................................................................................. 6-13

Starting the full capacity trial ............................................................................................ 6-14

Task 4: Upgrading software version ........................................................................................ 6-15

Checking the installed software version ............................................................................ 6-15

Upgrading to a new software version ................................................................................ 6-16

Task 5: Configuring security .................................................................................................... 6-19

Configuring AES encryption ............................................................................................... 6-19

Configuring HTTPS/TLS ..................................................................................................... 6-21

Using the Security Wizard .................................................................................................. 6-21

Configuring local user accounts ......................................................................................... 6-30

Changing own user password ............................................................................................. 6-36

Protecting access to the summary and status pages ......................................................... 6-36

Configuring RADIUS authentication .................................................................................. 6-37

Task 6: Configuring wireless and telecoms interfaces ............................................................ 6-40

Starting installation wizard ................................................................................................ 6-40

Step 1: Interface configuration .......................................................................................... 6-43

Step 2: Wireless configuration ........................................................................................... 6-46

Step 3: TDD synchronization (optional) ............................................................................. 6-53

Step 3 or 4: Confirm installation configuration ................................................................. 6-55

Barring channels ................................................................................................................. 6-57

Task 7: Setting up SNMP agent ............................................................................................... 6-58

Configuring SNMPv3 agent ................................................................................................ 6-58

Configuring SNMPv1/2c agent ........................................................................................... 6-67

Task 8: Configuring alarms and messages ............................................................................... 6-71

Configuring generation of diagnostics alarms ................................................................... 6-71

Configuring generation of email messages ........................................................................ 6-72

Task 9: Configuring syslog ....................................................................................................... 6-74

Configuring system logging (syslog) .................................................................................. 6-74

Task 10: Configuring remote access ........................................................................................ 6-76

viii

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User Guide

Configuring web-based management attributes ................................................................ 6-76

Task 11: Aligning antennas ....................................................................................................... 6-78

Starting up the units ........................................................................................................... 6-78

Checking that the units are armed ..................................................................................... 6-79

Aligning antennas ............................................................................................................... 6-79

Aligning separate antennas for spatial diversity ................................................................ 6-81

Monitoring received signal level ........................................................................................ 6-81

Disarming the units ............................................................................................................. 6-86

Task 12: Updating system configuration .................................................................................. 6-87

Reviewing system configuration attributes ........................................................................ 6-87

Task 13: Checking wireless performance ................................................................................ 6-89

Comparing actual to predicted performance ..................................................................... 6-89

Task 14: Configuring quality of service .................................................................................... 6-90

Configuring quality of service ............................................................................................ 6-90

Task 15: Connecting link to the network ................................................................................. 6-91

Connecting to the network ................................................................................................. 6-91

Setting the real-time clock.................................................................................................. 6-91

Saving the system configuration ........................................................................................ 6-94

Chapter 7: Operation ................................................................................................. 7-1

Web-based management ............................................................................................................. 7-2

Accessing the web interface ................................................................................................. 7-2

Using the menu options ........................................................................................................ 7-4

Viewing the system summary ............................................................................................... 7-6

Viewing the system status .................................................................................................... 7-7

Logging out ......................................................................................................................... 7-14

Managing alarms and events .................................................................................................... 7-15

Managing alarms ................................................................................................................ 7-15

Managing email alerts ........................................................................................................ 7-19

Managing event notification messages .............................................................................. 7-20

Managing spectrum .................................................................................................................. 7-21

Configuring spectrum usage at the master ........................................................................ 7-21

Viewing spectrum usage at the slave ................................................................................. 7-24

Interpreting the spectrum management plots ................................................................... 7-25

Viewing the active channel history..................................................................................... 7-32

Viewing historic spectrum management metrics ............................................................... 7-33

Managing security .................................................................................................................... 7-34

Zeroizing critical security parameters ............................................................................... 7-34

phn-2511_005v000 (Mar 2013)

ix

Contents

Displaying login information .............................................................................................. 7-34

Managing performance ............................................................................................................. 7-36

Checking system statistics.................................................................................................. 7-36

Checking detailed counters ................................................................................................ 7-42

Using the diagnostics plotter ............................................................................................. 7-45

Downloading diagnostic data ............................................................................................. 7-46

Diagnostics calculated over time........................................................................................ 7-47

Restoring, upgrading and rebooting ........................................................................................ 7-48

Restoring the system configuration ................................................................................... 7-48

Upgrading software ............................................................................................................ 7-49

Rebooting or reviewing reboot reasons ............................................................................. 7-52

Using recovery mode ................................................................................................................ 7-53

Entering recovery mode ..................................................................................................... 7-53

Selecting a recovery option ................................................................................................ 7-54

Upgrading software image ................................................................................................. 7-56

Resetting IP & Ethernet configuration ............................................................................... 7-57

Erasing configuration ......................................................................................................... 7-58

Rebooting the unit from recovery mode ............................................................................ 7-59

Chapter 8: Troubleshooting ....................................................................................... 8-1

Testing link end hardware .......................................................................................................... 8-2

Checking the PIDU LEDs ...................................................................................................... 8-2

Power LED is off ................................................................................................................... 8-3

Power LED is blinking .......................................................................................................... 8-3

Ethernet LED did not blink 10 times .................................................................................... 8-3

Ethernet LED is off ............................................................................................................... 8-4

Ethernet LED blinks irregularly ........................................................................................... 8-5

Power LED is on, Ethernet LED blinks randomly ................................................................ 8-5

Testing resistance in the ODU cable .................................................................................... 8-8

Testing the radio link ................................................................................................................ 8-10

No activity ........................................................................................................................... 8-10

Some activity ....................................................................................................................... 8-10

Radio and television interference ....................................................................................... 8-11

Testing PTP-SYNC ..................................................................................................................... 8-12

Checking the PTP-SYNC LEDs ........................................................................................... 8-12

LEDs do not illuminate ....................................................................................................... 8-13

STATUS LED is on steady ................................................................................................... 8-13

STATUS LED double-blinks ................................................................................................ 8-13

x

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User Guide

ODU LED does not illuminate within 90 seconds .............................................................. 8-13

ODU LED blinks red ............................................................................................................ 8-14

GPS LED does not illuminate or blink on clustered units .................................................. 8-14

Testing a telecoms link ............................................................................................................. 8-15

Performing a telecoms loopback test ................................................................................. 8-15

Glossary ........................................................................................................................... I

phn-2511_005v000 (Mar 2013)

xi

PTP 500 and PTP 300 Series User G uide

List of Figures

Figure 1 Typical bridge deployment (grounding not shown) ......................................................... 1-4

Figure 2 Integrated ODU (front and rear views) ............................................................................ 1-7

Figure 3 Connectorized ODU (front and rear views) ..................................................................... 1-7

Figure 4 ODU interfaces ................................................................................................................. 1-8

Figure 5 Connectorized ODU antenna interfaces .......................................................................... 1-9

Figure 6 PIDU interfaces .............................................................................................................. 1-11

Figure 7 External DC supply only ................................................................................................. 1-13

Figure 8 External DC supply and AC supply ................................................................................ 1-13

Figure 9 External DC supply and redundant AC supply .............................................................. 1-14

Figure 10 Remote LED and recovery switch wiring .................................................................... 1-14

Figure 11 Cable grounding kit for 1/4” and 3/8” cable ................................................................ 1-17

Figure 12 LPU single end kit ........................................................................................................ 1-18

Figure 13 PTP-SYNC kit ................................................................................................................ 1-19

Figure 14 PTP-SYNC front panel .................................................................................................. 1-20

Figure 15 TDD cycle ...................................................................................................................... 1-23

Figure 16 Protocol layers between Ethernet and wireless interfaces ......................................... 1-37

Figure 17 Protocol layers between external interfaces and the management agent .................. 1-38

Figure 18 Cable length restrictions when PTP-SYNC is installed ................................................. 2-7

Figure 19 Rolling sphere method to determine the lightning protection zones ......................... 2-20

Figure 20 Grounding cable minimum bend radius and angle ...................................................... 2-22

Figure 21 Grounding and lightning protection on mast or tower ................................................ 2-23

Figure 22 Grounding and lightning protection on wall ................................................................ 2-24

Figure 23 Grounding and lightning protection on building ......................................................... 2-26

Figure 24 Grounding and lightning protection inside high building ........................................... 2-27

Figure 25 TDD synchronization configuration – single link with PTP-SYNC ............................... 2-29

Figure 26 TDD synchronization configuration – cluster with PTP-SYNC and GPS ..................... 2-30

Figure 27 TDD synchronization configuration – cluster with PTP-SYNC and no GPS ................ 2-31

Figure 28 Grounding and lightning protection for GPS receiver on building ............................. 2-33

Figure 29 Grounding and lightning protection for GPS receiver on tower or mast .................... 2-34

Figure 30 PTP 54500 available spectrum in 15 MHz channel bandwidth ................................... 4-10

Figure 31 PTP 54500 available spectrum in 10 MHz channel bandwidth ................................... 4-10

phn-2511_005v000 (Mar 2013)

xii

PTP 500 and PTP 300 Series User Guide

Figure 32 PTP 54500 available spectrum in 5 MHz channel bandwidth ..................................... 4-11

Figure 33 PTP 58500 available spectrum in 15 MHz channel bandwidth ................................... 4-12

Figure 34 PTP 58500 available spectrum in the 10 MHz channel bandwidth ............................ 4-12

Figure 35 PTP 58500 available spectrum in 5 MHz channel bandwidth ..................................... 4-13

Figure 36 FCC and IC certifications on 5.4 GHz product label ................................................... 4-37

Figure 37 European Union certification on 5.4 GHz product label ............................................. 4-37

Figure 38 FCC and IC certifications on 5.8 GHz product label ................................................... 4-39

Figure 39 European Union certification on 5.8 GHz product label ............................................. 4-40

Figure 40 PTP 500 range adjustment for data rates, curve A...................................................... 4-48

Figure 41 PTP 500 range adjustment for data rates, curve B ..................................................... 4-48

Figure 42 Do not reverse the rear bracket strap ........................................................................... 5-4

Figure 43 Checking the ODU before mounting .............................................................................. 5-5

Figure 44 Correct cable preparation for drop cable of the supported type ................................ 5-17

Figure 45 Drop cable with RJ45 and gland ................................................................................... 5-18

Figure 46 Grounding at building entry ......................................................................................... 5-25

Figure 47 Rack mount securing screws for PTP-SYNC ................................................................ 5-31

Figure 48 PTP-SYNC mounted on a wall ...................................................................................... 5-31

Figure 49 Inserting RJ45 pins into the 12 way circular connector .............................................. 5-40

Figure 50 Grounding and weatherproofing requirements for GPS adapter cable ...................... 5-45

Figure 51 Wrapping self-amalgamating tape around the GPS adapter cable joint ..................... 5-45

Figure 52 Wrapping PVC tape around the GPS adapter cable joint ............................................ 5-45

Figure 53 Grounding and weatherproofing example for GPS adapter cable .............................. 5-46

Figure 54 E1/T1 splitter ................................................................................................................ 5-47

Figure 55 Software License Key page .......................................................................................... 6-11

Figure 56 Software License Key page with full capacity trial in progress .................................. 6-14

Figure 57 Security Configuration Wizard page ............................................................................ 6-22

Figure 58 Step 1: Enter Key of Keys page .................................................................................... 6-23

Figure 59 Step 2: TLS Private Key and Public Certificate page .................................................. 6-24

Figure 60 Step 3: User Security Banner page .............................................................................. 6-24

Figure 61 Step 4: Login Information Settings page ..................................................................... 6-25

Figure 62 Step 5: Random Number Entropy Input page ............................................................. 6-26

Figure 63 Step 6: Enter Wireless Link Encryption Key page ....................................................... 6-26

Figure 64 Step 7: HTTP and Telnet Settings page ....................................................................... 6-27

Figure 65 Step 8: Commit Security Configuration page .............................................................. 6-29

Figure 66 Local User Accounts page (identity-based user accounts not shown) ........................ 6-31

Figure 67 Identity-based user accounts ....................................................................................... 6-35

Figure 68 Change Password page (System Administration example) ......................................... 6-36

phn-2511_005v000 (Mar 2013)

xiii

List of Figures

Figure 69 Webpage Properties page ............................................................................................ 6-37

Figure 70 RADIUS Authentication page ....................................................................................... 6-38

Figure 71 Disarm Installation page (when unit is armed) ........................................................... 6-41

Figure 72 Current Installation Summary page (when unit is disarmed) ..................................... 6-42

Figure 73 Step 1: Interface Configuration page .......................................................................... 6-43

Figure 74 Step 1: Interface Configuration page with T1 enabled ............................................... 6-44

Figure 75 Step 2: Wireless Configuration page ........................................................................... 6-46

Figure 76 Step 2: Wireless Configuration page for connectorized ODUs ................................... 6-47

Figure 77 Step 2: Wireless Configuration page (extract) for fixed frequency ............................ 6-52

Figure 78 Step 3: TDD Synchronization page .............................................................................. 6-53

Figure 79 Step 3: Confirm Installation Configuration page ......................................................... 6-56

Figure 80 Reboot confirmation pop up ......................................................................................... 6-56

Figure 81 Current SNMP Summary page (when SNMP is disabled) .......................................... 6-58

Figure 82 Step 1: SNMP Configuration page (for SNMPv3) ....................................................... 6-59

Figure 83 Step 1: SNMP MIB-II System Objects page ................................................................. 6-60

Figure 84 Step 2: SNMP User Policy Configuration page (for SNMPv3) .................................... 6-61

Figure 85 Step 4: SNMP User Accounts Configuration page (for SNMPv3) ............................... 6-63

Figure 86 Step 5: SNMP Trap Configuration page (for SNMPv3) ............................................... 6-64

Figure 87 Confirm SNMP Configuration page (for SNMPv3) ...................................................... 6-66

Figure 88 Step 1: SNMP Configuration page (for SNMPv1/2c) .................................................. 6-67

Figure 89 Step 3: SNMP Trap Configuration page (for SNMPv1/2c) .......................................... 6-68

Figure 90 Confirm SNMP Configuration page (for SNMPv1/2c) ................................................. 6-70

Figure 91 Diagnostic Alarms page ................................................................................................ 6-71

Figure 92 Syslog Configuration page ........................................................................................... 6-74

Figure 93 Web-Based Management page ..................................................................................... 6-76

Figure 94 System Summary page (when unit is armed) .............................................................. 6-79

Figure 95 Using DVM for alignment ............................................................................................. 6-84

Figure 96 Graphical installation page .......................................................................................... 6-85

Figure 97 Optional post-disarm configuration ............................................................................. 6-86

Figure 98 System Configuration page .......................................................................................... 6-87

Figure 99 QoS Configuration page ............................................................................................... 6-90

Figure 100 Time Configuration page (SNTP disabled) ................................................................ 6-92

Figure 101 Time Configuration page (SNTP enabled) ................................................................. 6-93

Figure 102 Save & Restore Configuration page........................................................................... 6-95

Figure 103 Login page .................................................................................................................... 7-2

Figure 104 Menu and System Summary page (wireless link up) .................................................. 7-3

Figure 105 System Summary page ................................................................................................. 7-6

xiv

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User Guide

Figure 106 System Status page ...................................................................................................... 7-7

Figure 107 Status page - TDD enabled and synchronized ........................................................... 7-13

Figure 108 Status page - TDD enabled and not synchronized ..................................................... 7-14

Figure 109 Alarm warning triangle .............................................................................................. 7-15

Figure 110 Syslog local log ........................................................................................................... 7-20

Figure 111 Spectrum Management as seen from the Master ..................................................... 7-22

Figure 112 Spectrum Management as seen from the Slave ........................................................ 7-24

Figure 113 Example spectrum management plot ........................................................................ 7-25

Figure 114 Spectrum Management Fixed Frequency Mode page ............................................... 7-28

Figure 115 Spectrum Management page with radar avoidance - master ................................... 7-29

Figure 116 Spectrum Management page with radar avoidance - slave ...................................... 7-30

Figure 117 Active channel history screen .................................................................................... 7-32

Figure 118 Spectrum management time series plot .................................................................... 7-33

Figure 119 Login Information page .............................................................................................. 7-35

Figure 120 System Statistics page ............................................................................................... 7-37

Figure 121 Detailed Counters page .............................................................................................. 7-43

Figure 122 Diagnostic Plotter page .............................................................................................. 7-45

Figure 123 Diagnostic attributes calculated over time (System Status page) ............................. 7-47

Figure 124 Reboot Wireless Unit page ......................................................................................... 7-52

Figure 125 Reboot confirmation pop up ....................................................................................... 7-52

Figure 126 PIDU recovery switch location ................................................................................... 7-53

Figure 127 Recovery Image Warning page .................................................................................. 7-54

Figure 128 Recovery Options Page ............................................................................................... 7-54

Figure 129 Ethernet packet test test flowchart ............................................................................. 8-6

Figure 130 Drop cable tester (front and back views) ..................................................................... 8-8

Figure 131 Telecoms page ............................................................................................................ 8-16

phn-2511_005v000 (Mar 2013)

xv

PTP 500 and PTP 300 Series User G uide

List of Tables

Table 1 PTP 500 Series frequency variants .................................................................................... 1-5

Table 2 Interpretation of existing PTP 300 and PTP 500 licenses ................................................. 1-6

Table 3 ODU interface functions..................................................................................................... 1-8

Table 4 PIDU interface functions .................................................................................................. 1-12

Table 5 PIDU LED functions ......................................................................................................... 1-12

Table 6 PTP-SYNC front panel interface functions ...................................................................... 1-20

Table 7 PTP-SYNC LED functions ................................................................................................. 1-20

Table 8 Lateral force – metric ......................................................................................................... 2-8

Table 9 Lateral force – US ............................................................................................................... 2-9

Table 10 Parameters that influence modulation mode selection ................................................. 2-12

Table 11 Normal EIRP limits with operating channel bandwidth ................................................ 2-17

Table 12 Setting maximum transmit power to meet general EIRP limits ................................... 2-17

Table 13 RF cable lengths required to achieve 1.2 dB loss at 5.8 GHz ....................................... 2-18

Table 14 HTTPS/TLS security material ........................................................................................ 2-37

Table 15 Permitted character set for SNMPv3 passphrases ....................................................... 2-42

Table 16 Default SNMPv3 users ................................................................................................... 2-43

Table 17 Definition of auth-role vendor specific attributes ......................................................... 2-45

Table 18 Selecting the required regional variant ........................................................................ 2-46

Table 19 PTP 54500 kit part numbers .......................................................................................... 2-47

Table 20 PTP 58500 kit part numbers .......................................................................................... 2-48

Table 21 Inventory for PTP 500 kits ............................................................................................. 2-48

Table 22 Additional inventory for standard installations ............................................................. 2-50

Table 23 Additional inventory for connectorized ODUs ............................................................... 2-52

Table 24 Allowed antennas for deployment in USA/Canada – 5.4 GHz ....................................... 2-54

Table 25 Allowed antennas for deployment in USA/Canada – 5.8 GHz ....................................... 2-56

Table 26 Sectored antennas for deployment in USA/Canada – 5.8 GHz ..................................... 2-59

Table 27 Additional inventory for PTP-SYNC installations .......................................................... 2-60

Table 28 Additional inventory for GPS receiver installations ...................................................... 2-61

Table 29 Recommended components and tools for direct GPS connection ................................ 2-62

Table 30 Additional inventory for E1 or T1 installations ............................................................. 2-62

Table 31 Integrated ODU physical specifications .......................................................................... 4-2

phn-2511_005v000 (Mar 2013)

xvi

PTP 500 and PTP 300 Series User Guide

Table 32 Connectorized ODU physical specifications .................................................................... 4-2

Table 33 ODU environmental specifications .................................................................................. 4-2

Table 34 PIDU physical specifications ............................................................................................ 4-3

Table 35 PIDU environmental specifications .................................................................................. 4-3

Table 36 PIDU electrical specifications .......................................................................................... 4-3

Table 37 PTP-SYNC unit physical specifications ............................................................................ 4-4

Table 38 PTP-SYNC unit environmental specifications .................................................................. 4-4

Table 39 PTP-SYNC unit electrical specifications .......................................................................... 4-4

Table 40 PTP-SYNC unit timing specifications - GPS/SYNC IN (RJ-45) ......................................... 4-5

Table 41 PTP-SYNC unit timing specifications - 1PPS IN (SMA) ................................................... 4-5

Table 42 GPS/SYNC IN port pinouts ............................................................................................... 4-6

Table 43 PTP 54500 RF specifications ............................................................................................ 4-7

Table 44 PTP 58500 RF specifications ............................................................................................ 4-8

Table 45 PTP 58500 maximum transmit power at the edge channels (FCC) .............................. 4-13

Table 46 PTP 54500 thresholds - IP mode (15 MHz bandwidth) ................................................. 4-15

Table 47 PTP 54500 thresholds - TDM mode (15 MHz bandwidth) ............................................. 4-15

Table 48 PTP 54500 thresholds - IP mode (10 MHz bandwidth) ................................................. 4-16

Table 49 PTP 54500 thresholds - TDM mode (10 MHz bandwidth) ............................................. 4-16

Table 50 PTP 54500 thresholds - IP mode (5 MHz bandwidth) ................................................... 4-17

Table 51 PTP 54500 thresholds - TDM mode (5 MHz bandwidth) ............................................... 4-17

Table 52 PTP 58500 thresholds - IP mode (15 MHz bandwidth) ................................................. 4-18

Table 53 PTP 58500 thresholds - TDM mode (15 MHz bandwidth) ............................................. 4-18

Table 54 PTP 58500 thresholds - IP mode (10 MHz bandwidth) ................................................. 4-19

Table 55 PTP 58500 thresholds - TDM mode (10 MHz bandwidth) ............................................. 4-19

Table 56 PTP 58500 thresholds - IP mode (5 MHz bandwidth) ................................................... 4-20

Table 57 PTP 58500 thresholds - TDM mode (5 MHz bandwidth) ............................................... 4-20

Table 58 Ethernet bridging specifications .................................................................................... 4-21

Table 59 Telecoms interface specifications .................................................................................. 4-21

Table 60 Event messages .............................................................................................................. 4-24

Table 61 Safety compliance specifications ................................................................................... 4-26

Table 62 EMC emissions compliance ............................................................................................ 4-26

Table 63 Power compliance margins ............................................................................................ 4-29

Table 64 Radio certifications ........................................................................................................ 4-30

Table 65 Regulatory limits for PTP 54500 .................................................................................... 4-32

Table 66 Regulatory limits for PTP 58500 .................................................................................... 4-33

Table 67 Default and alternative region codes for PTP 500 variants .......................................... 4-35

Table 68 Throughput: licensed 25 Mbps, link symmetry = adaptive or 3:1 (Mbps) ................... 4-42

phn-2511_005v000 (Mar 2013)

xvii

List of Tables

Table 69 Throughput: licensed 25 Mbps, link symmetry 1:1, link optimization IP (Mbps) ........ 4-43

Table 70 Throughput: licensed 25 Mbps, link symmetry 1:1, link optimization TDM (Mbps) .... 4-44

Table 71 Throughput: licensed 105 Mbps, link symmetry = adaptive or 3:1 (Mbps) ................. 4-45

Table 72 Throughput: licensed 105 Mbps, link symmetry 1:1, link optimization IP (Mbps) ...... 4-46

Table 73 Throughput: licensed 105 Mbps, link symmetry 1:1, link optimization TDM (Mbps) .. 4-47

Table 74 GPS 12 way circular connector to RJ45 pin mappings.................................................. 5-39

Table 75 E1/T1 splitter output pin connections ........................................................................... 5-48

Table 76 LAN Configuration attributes .......................................................................................... 6-8

Table 77 Capability summary attributes ...................................................................................... 6-12

Table 78 HTTP and Telnet attributes ........................................................................................... 6-27

Table 79 Local User account management attributes ................................................................. 6-32

Table 80 Password complexity configuration attributes .............................................................. 6-33

Table 81 Identity-based user accounts attributes ........................................................................ 6-35

Table 82 RADIUS Authentication attributes ................................................................................. 6-39

Table 83 Step 1: Interface Configuration standard attributes ..................................................... 6-44

Table 84 Step 2: Wireless Configuration attributes ..................................................................... 6-48

Table 85 Step 3: TDD Synchronization attributes ........................................................................ 6-54

Table 86 Step 1: SNMP Configuration attributes (for SNMPv3) ................................................. 6-59

Table 87 Step 2: SNMP MIB-II System Objects attributes .......................................................... 6-60

Table 88 Step 3: SNMP User Policy Configuration attributes (for SNMPv3) ............................. 6-61

Table 89 Step 3: SNMP User Accounts Configuration attributes (for SNMPv3) ........................ 6-63

Table 90 Step 5: SNMP Trap Configuration attributes (for SNMPv3) ........................................ 6-64

Table 91 Step 1: SNMP Configuration attributes (for SNMPv1/2c) ............................................ 6-67

Table 92 Step 3: SNMP Trap Configuration attributes (for SNMPv1/2c) ................................... 6-69

Table 93 Email Configuration attributes ...................................................................................... 6-73

Table 94 Syslog Configuration attributes ..................................................................................... 6-75

Table 95 Web-Based Management attributes .............................................................................. 6-77

Table 96 ODU installation tones ................................................................................................... 6-82

Table 97 System Configuration attributes .................................................................................... 6-87

Table 98 QoS default settings ....................................................................................................... 6-90

Table 99 Manual clock attributes ................................................................................................. 6-92

Table 100 SNTP clock attributes .................................................................................................. 6-93

Table 101 Procedures performed from each menu option ............................................................. 7-4

Table 102 System Summary attributes ........................................................................................... 7-6

Table 103 System Status attributes ................................................................................................ 7-8

Table 104 System alarms .............................................................................................................. 7-16

Table 105 Telecoms channel alarm conditions ............................................................................. 7-19

xviii

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User Guide

Table 106 Email alerts................................................................................................................... 7-19

Table 107 Spectrum Management attributes ............................................................................... 7-22

Table 108 Channel states represented in the spectrum management plot ................................. 7-26

Table 109 Key metrics represented in the spectrum management plot ...................................... 7-26

Table 110 Channel states represented in the spectrum management plot (radar avoidance) ... 7-31

Table 111 Interference represented in the time series plot ........................................................ 7-33

Table 112 System Histograms attributes in the System Statistics page ..................................... 7-38

Table 113 Data Port Counter attributes in the System Statistics page ....................................... 7-40

Table 114 Management Port Counter attributes in the System Statistics page ......................... 7-40

Table 115 Wireless Port Counter attributes in the System Statistics page ................................. 7-40

Table 116 Other attributes in the System Statistics page ........................................................... 7-42

Table 117 Detailed Counters attributes ........................................................................................ 7-43

Table 118 Setting tFTP attributes................................................................................................. 7-50

Table 119 Monitoring tFTP attributes .......................................................................................... 7-51

Table 120 Recovery Options attributes ........................................................................................ 7-55

Table 121 Recovery Options buttons ............................................................................................ 7-55

Table 122 RJ45 cable resistance tests at the PIDU end ................................................................. 8-9

Table 123 PTP-SYNC indicator LED states ................................................................................... 8-12

Table 124 Clustered PTP-SYNC units - ‘GPS’ LEDs Fault-finding ............................................... 8-14

Table 125 Telecoms Loopback values ........................................................................................... 8-16

phn-2511_005v000 (Mar 2013)

xix

List of Tables

xx

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide

About This User Guide

This guide describes the planning, installation and operation of the Cambium PTP 500
Series of point-to-point wireless Ethernet bridges. It is intended for use by the system
designer, system installer and system administrator.

Cambium no longer supplies the following product variants: PTP 300, PTP 500 Lite or
PTP 500 Full. However, PTP 300 and PTP 500 System Releases continue to support these
discontinued variants. See Support for discontinued product variants on page 1-6.

Wherever this user guide refers (for brevity) to PTP 500, it means both PTP 500 and
PTP 300.

Users of this guide should have knowledge of the following areas:

• Radio network design

• Outdoor radio equipment installation

• System installation, configuration, monitoring and fault finding

System designers should refer to the following chapters:

• Chapter 1: Product description

• Chapter 2: Planning considerations

• Chapter 3: Legal information

• Chapter 4: Reference information

Installers should refer to the following chapters:

• Chapter 5: Installation

• Chapter 6: Configuration and alignment

• Chapter 8: Troubleshooting

Operators should refer to the following chapters:

• Chapter 1: Product description

• Chapter 6: Configuration and alignment

• Chapter 7: Operation

• Chapter 8: Troubleshooting

phn-2511_005v000 (Mar 2013)

1

General informa tion About This User Guide

General information

Version information

The following shows the issue status of this document:

Document
issue

002v000 Mar 2012 System releases 500-05-01 and 300-05-01

003v000 Jul 2012 System releases 500-05-02 and 300-05-02

004v000 Feb 2013 System releases 500-05-03 and 300-05-03

005v000 Mar 2013 System releases 500-05-03 and 300-05-03 (revised)

Date of issue Remarks

Contacting Cambium Networks

Support website: http://www.cambiumnetworks.com/support

Main website: http://www.cambiumnetworks.com

Sales enquiries: [e-mail]

Support enquiries: [e-mail]

Telephone number list: http://www.cambiumnetworks.com/contact.php

Address: Cambium Networks Limited,

Linhay Business Park,
Eastern Road,
Ashburton,
Devon, UK,
TQ13 7UP

2

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide General informa tion

Purpose

Cambium Networks Point-To-Point (PTP) documents are intended to instruct and assist
personnel in the operation, installation and maintenance of the Cambium PTP equipment
and ancillary devices. It is recommended that all personnel engaged in such activities be
properly trained.

Cambium disclaims all liability whatsoever, implied or express, for any risk of damage, loss
or reduction in system performance arising directly or indirectly out of the failure of the
customer, or anyone acting on the customer's behalf, to abide by the instructions, system
parameters, or recommendations made in this document.

Cross references

References to external publications are shown in italics. Other cross references,
emphasized in blue text in electronic versions, are active links to the references.

This document is divided into numbered chapters that are divided into sections. Sections
are not numbered, but are individually named at the top of each page, and are listed in the
table of contents.

Feedback

We appreciate feedback from the users of our documents. This includes feedback on the
structure, content, accuracy, or completeness of our documents. Send feedback to

[e-mail]

.

phn-2511_005v000 (Mar 2013)

3

Problems and warranty About This User Guide

Problems and warranty

Reporting problems

If any problems are encountered when installing or operating this equipment, follow this
procedure to investigate and report:

Search this document and the software release notes of supported releases.

1

Visit the support website.

2

Ask for assistance from the Cambium product supplier.

3

Gather information from affected units, such as any available diagnostic

4

downloads.

Escalate the problem by emailing or telephoning support.

5

Repair and service

If unit failure is suspected, obtain details of the Return Material Authorization (RMA)
process from the support website.

Warranty

Cambium’s standard hardware warranty is for one (1) year from date of shipment from
Cambium or a Cambium distributor. Cambium warrants that hardware will conform to the
relevant published specifications and will be free from material defects in material and
workmanship under normal use and service. Cambium 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.

To register PTP products or activate warranties, visit the support website.

For warranty assistance, contact the reseller or distributor.

Using non-Cambium parts for repair could damage the equipment or void warranty.
Contact Cambium for service and repair instructions.

4

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Problems and warranty

Portions of Cambium equipment may be damaged from exposure to electrostatic
discharge. Use precautions to prevent damage.

phn-2511_005v000 (Mar 2013)

5

Security advice About This User Guide

Security advice

Cambium Networks systems and equipment provide security parameters that can be
configured by the operator based on their particular operating environment. Cambium
recommends setting and using these parameters following industry recognized security
practices. Security aspects to be considered are protecting the confidentiality, integrity,
and availability of information and assets. Assets include the ability to communicate,
information about the nature of the communications, and information about the parties
involved.

In certain instances Cambium makes specific recommendations regarding security
practices, however the implementation of these recommendations and final responsibility
for the security of the system lies with the operator of the system.

6

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Warnings, cautions, and notes

Warnings, cautions, and notes

The following describes how warnings and cautions are used in this document and in all
documents of the Cambium Networks document set.

Warnings

Warnings precede instructions that contain potentially hazardous situations. Warnings are
used to alert the reader to possible hazards that could cause loss of life or physical injury.
A warning has the following format:

Warning text and consequence for not following the instructions in the warning.

Cautions

Cautions precede instructions and are used when there is a possibility of damage to
systems, software, or individual items of equipment within a system. However, this
damage presents no danger to personnel. A caution has the following format:

Caution text and consequence for not following the instructions in the caution.

Notes

A note means that there is a possibility of an undesirable situation or provides additional
information to help the reader understand a topic or concept. A note has the following
format:

Note text.

phn-2511_005v000 (Mar 2013)

7

Caring for the environment About This User Guide

Caring for the environment

The following information describes national or regional requirements for the disposal of
Cambium Networks supplied equipment and for the approved disposal of surplus
packaging.

In EU countries

The following information is provided to enable regulatory compliance with the European
Union (EU) directives identified and any amendments made to these directives when using
Cambium equipment in EU countries.

Disposal of Cambium equipment

European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment
(WEEE)

Do not dispose of Cambium equipment in landfill sites. For disposal instructions, refer to

http://www.cambiumnetworks.com/doc.php

Disposal of surplus packaging

Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual
recipient’s responsibility to ensure that packaging materials are collected and recycled
according to the requirements of EU environmental law.

In non-EU countries

In non-EU countries, dispose of Cambium equipment and all surplus packaging in
accordance with national and regional regulations.

.

8

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide

Chapter 1: Product description

This chapter provides a high level description of the PTP 500 product. It describes in
general terms the function of the product, the main product variants and typical
deployment. It also describes the main hardware components.

The following topics are described in this chapter:

• Overview of the PTP 500 on page 1-2 introduces the key features, typical uses, product

variants and components of the PTP 500.

• Outdoor unit (ODU)

• Powered indoor unit (PIDU) on page 1-11 describes the PIDU and its interfaces.

• Cabling and lightning protection on page 1-16 describes the cabling and lightning

protection components of PTP 500 installations.

• PTP-SYNC unit on page 1-19 describes the (optional) PTP-SYNC unit and its interfaces.

This unit may be used to implement TDD synchronization.

• Wireless operation on page 1-22 describes how PTP 500 wireless links are operated,

including modulation modes, power control and security.

• Ethernet bridging on page 1-34 describes how the PTP 500 controls Ethernet data, in

both the customer and system management networks.

• Telecoms circuits on page 1-40 describes how telecoms traffic (E1 or T1) may be

carried over PTP 500 links.

• System management on page 1-42 introduces the PTP 500 management system,

including the web interface, installation, configuration, alerts and upgrades.

on page 1-7 describes the ODU and its interfaces.

phn-2511_005v000 (Mar 2013)

1-1

Overview of the PTP 500 Chapter 1: Product d es cription

Overview of the PTP 500

This section introduces the key features, typical uses, product variants and components of
the PTP 500.

Purpose

Cambium PTP 500 Series products are designed for Ethernet bridging over point-to-point
microwave links in the unlicensed bands 5.4 GHz (ETSI Band B) and 5.8 GHz (ETSI Band C
and FCC ISM band). Users must ensure that the links comply with local operating
regulations.

The PTP 500 is used to create a transparent bridge between two segments of the
operator’s network. This bridge can be treated as a virtual wired connection between two
points. The system is transparent to higher-level protocols such as VLANs and Spanning
Tree.

Key features

The key features of the PTP 500 Series include:

• True non-line-of-sight (NLOS) operation by using a combination of Orthogonal

Frequency Division Multiplexing (OFDM) modulation and Multiple-Input Multiple­Output (MIMO) techniques.

• Wireless connections of up to 250 km (155 miles) in near line-of-sight conditions and up

to 100 meters (330 ft) in deep non-line-of-sight conditions.

• Coexistence with other users of the band using a combination of Spectrum

Management functionality and Antenna beam shape.

• High link availability, through the use of adaptive modulation techniques that

dynamically reduce the data rate in severe or adverse conditions.

• High system gain through high sensitivity antennas for improved signal recovery.

• A radio system that operates using ultra-fast digital signal processors and is controlled

by updateable firmware.

• A built-in web server for advanced management capabilities including detailed radio

signal diagnosis.

• A range of security features to prevent unauthorized access to data. Optional AES

encryption for data transmitted over the wireless, with 128-bit or 256-bit encryption
keys. Optional HTTPS/TLS security on the web-based management interface. SNMPv3
with optional AES privacy and SHA1 authentication.

1-2

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Overview of the PTP 500

Benefit of the chosen bands

The products operate in bands that offer the dual benefits of high data throughput and
good radio propagation characteristics. The wide band of spectrum available is subdivided
into several channels such that multiple systems can operate in the vicinity without
causing interference to one another.

Similarity to 802.11a devices

The products are not 802.11a devices. Although similar, they use different encoding and
radio transmission systems from 802.11a. In areas where 802.11a systems are operating,
the products will detect the 802.11a radio signals and choose a clear channel away from
any interference.

Avoiding interference from nearby devices

At initialization, the products monitor the available frequency channels to find a channel
that is clear of interference. In operation, the products continuously monitor the spectrum
to ensure it is operating on the cleanest channel.

Typical deployment

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

phn-2511_005v000 (Mar 2013)

1-3

Overview of the PTP 500 Chapter 1: Product d es cription

Figure 1 Typical bridge deployment (grounding not shown)

System components

Each end of the link consists of:

• Outdoor Unit (ODU): An integrated (or connectorized) outdoor transceiver unit

containing all the radio and networking electronics.

• PIDU: An indoor connection box containing a mains power supply, status indicators

and network connection port.

• Cabling and lightning protection: Cat5e cables, grounding cables, connectors and a

lightning protection unit (LPU).

1-4

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Overview of the PTP 500

Product variants

The PTP 500 Series is available in the following product variants:

• Frequency variants: There is a frequency variant for each license exempt frequency

band 5.4 GHz and 5.8 GHz (Table 1). Check that local regulations allow the use of
these frequency variants.

• Integrated or Connectorized: Both frequency variants are available in either

Integrated (with attached antenna) or Connectorized (without an antenna) variants.

• Link Complete or End Complete: The Link Complete kit consists of two ODUs and

two PIDU units, pre-configured as a link. The End Complete kit consists of one ODU
and one PIDU unit.

• FCC/IC or ETSI/RoW: Both frequency variants are available in two regional variants:

one is for use in regions where FCC or IC licensing restrictions apply (FCC/IC), and the
other is for use in ETSI or the rest of the world (ETSI/RoW).

To identify the available combinations of the above variants, refer to PTP 500 kits on page

2-46.

Table 1 PTP 500 Series frequ enc y variants

Variant Band Region Frequency

Coverage

PTP 54500 5.4 GHz ETSI 5 GHz Band B

FCC UNII Band

PTP 58500 5.8 GHz ETSI Band 5725-5875

FCC ISM Band 5725-5850

All PTP 500 product variants are supplied with a licensed data throughput capacity limit
of 25 Mbps. This limit may subsequently be increased to 52 Mbps or 105 Mbps. For more
information, see Capacity upgrades on page 1-51.

5470-5725
MHz

MHz

MHz

Variable
Channel
Bandwidth

5, 10, 15
MHz

5, 10, 15
MHz

5, 10, 15
MHz

Channel
Raster

5 MHz

5 MHz

5 MHz

phn-2511_005v000 (Mar 2013)

1-5

Overview of the PTP 500 Chapter 1: Product d es cription

Support for discontinued product variants

Cambium no longer supplies the following product variants:

• PTP 300

• PTP 500 Lite

• PTP 500 Full

However, PTP 300 and PTP 500 System Releases continue to support these discontinued
variants. License keys for the discontinued variants are interpreted as equivalent capacity
licenses as shown in Table 2.

Table 2 Int erpretation of existing PTP 300 and PTP 500 licenses

Old license New license

PTP 300 PTP 300 25 Mbps

PTP 300 + Line of Sight PTP 300 52 Mbps

PTP 500 Lite PTP 500 52 Mbps

PTP 500 Full PTP 500 105 Mbps

Existing PTP 300 units retain their PTP 300 personality when operating with the latest
System Release. Units already converted from PTP 300 to PTP 500 retain their PTP 500
personality. PTP 500 and PTP 300 units support identical feature sets and, in particular,
PTP 300 units support TDD Synchronization using PTP-SYNC. A PTP 300 unit with the Line
of Sight capability operates at the 52 Mbps capacity level, equivalent to the earlier Line of
Sight mode, even though the web interface does not provide a Line Of Sight mode control.

PTP 300 and PTP 500 units are allowed to interwork in a link. In this case, the link
operates at the lower licensed capacity of the two ends.

1-6

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Outdoor unit (ODU)

Outdoor unit (ODU)

This section describes the PTP 500 ODU and its interfaces.

ODU description

The ODU is a self-contained unit that houses both radio and networking electronics. The
ODU is supplied in two configurations: integrated (attached to its own flat plate antenna,

Figure 2) or connectorized (without an antenna, Figure 3).

Figure 2 Integrated O DU (front and rear views)

Figure 3 Connectorized ODU (front and rear views)

phn-2511_005v000 (Mar 2013)

1-7

Outdoor unit (ODU) Chapter 1: Product d es cription

Connectorized variant

The connectorized ODU is designed to work with externally mounted antennas that have
higher gains than the integrated antenna. Connectorized units can cope with more difficult
radio conditions, as described in When to install connectorized units on page 2-15.

ODU interfaces

The ODU interfaces are illustrated in Figure 4 and described in Table 3.

Figure 4 ODU interfaces

Table 3 ODU interface functions

Interface Function

Ground studs For grounding the ODU to the supporting structure. The

ground cable (supplied with the ODU) may be connected
to either ground stud.

BNC connector Use with a digital voltmeter (DVM) to help with the

alignment process.

PIDU+ RJ45 socket for connecting to power supply and network

via the PIDU.

1-8

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Outdoor unit (ODU)

Connectorized ODU antenna interfaces

The connectorized ODU also has interfaces to connect to an external antenna (Figure 5)
via an N type connector with cable of type LMR100, LMR200, LMR300, LMR400 or
LMR600. The ‘V’ interface is for vertical polarization and the ‘H interface is for horizontal
polarization.

Figure 5 Connectorized ODU antenna interfaces

Mounting brackets

The ODU is supplied with a bracket for mounting it to a pole of 50mm (2”) to 75mm (3”) in
diameter.

The bracket allows for adjustment in both azimuth and elevation. The bracket may be split
to allow the pole mount section of the bracket to be mounted to the pole first. This allows
the installer to take the weight of the unit and secure it, one handed, with a single
mounting bolt.

Network connection

The network connection to the ODU is made via a 100BaseT Ethernet connection. Power is
provided to the ODU over the 100BaseT Ethernet connection using a patented
non-standard powering technique.

phn-2511_005v000 (Mar 2013)

1-9

Outdoor unit (ODU) Chapter 1: Product d es cription

Further reading on the ODU

For more information on the ODU, refer to the following:

• ODU site selection on page 2-6 describes how to select a site for the ODU.

• When to install connectorized units on page 2-15 describes when to choose

connectorized ODUs and external antennas rather than integrated ODUs.

• General protection requirements on page 2-21 describes the grounding and lightning

protection requirements of a PTP 500 installation, including the ODU.

• Ordering components on page 2-46 lists the components required for PTP 500

installations, including ODUs, with Cambium part numbers.

• FCC and IC approved antennas on page 2-53 contains specifications of the antennas

that may be used with connectorized ODUs.

• ODU specifications on page 4-2 contains specifications of the ODU such as dimensions,

weight and environmental requirements.

• Installing the ODU on page 5-4 describes how to install the ODU (integrated or

connectorized) on the supporting structure.

• Installing connectorized antennas on page 5-8 describes how to install separate

antenna(s) for a connectorized ODU.

• Task 11: Aligning antennas on page 6-78 describes how to align the antennas for both

integrated and connectorized ODUs.

1-10

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Powered indoor unit (PI DU)

Powered indoor unit (PIDU)

This section describes the PIDU Plus PTP 300/500/600 Series and its interfaces.

PIDU description

The PIDU generates the ODU supply voltage from the mains supply (or from an external
DC source) and injects this supply voltage into the ODU.

The PIDU is connected to the ODU and network equipment using Cat5e cable with RJ45
connectors.

The ODU should only be deployed using the supplied PIDU Plus PTP 300/500/600 Series.

The PIDU ODU port is designed to connect only to PTP 300, PTP 500 or PTP 600 ODUs,
LPUs or PTP-SYNC units. Do not connect any other equipment, as damage may occur.
The PIDU Plus PTP 300/500/600 Series is not interchangeable with the PIDU Plus
PTP 400 Series.

PIDU interfaces

The PIDU interfaces are illustrated in Figure 6 and described in Table 4 and Table 5.

Figure 6 PIDU interfaces

phn-2511_005v000 (Mar 2013)

1-11

Powered indoor u nit (PIDU) Chapter 1: Product description

Table 4 PIDU interface functions

Interface Function

100-240 V ac

Mains power input.

47-63Hz 1.8A

DC In Alternative DC power supply input. Refer to Redundancy

and alternative powering configurations on page 1-13.

DC Out DC power output to a second PIDU. Used to provide power

supply redundancy. Refer to Redundancy and alternative

powering configurations on page 1-13.

ODU RJ45 socket for connecting Cat5e cable to ODU.

LAN RJ45 socket for connecting Cat5e cable to network.

Recovery Used to recover the unit from configuration errors or

software image corruption.

Table 5 PIDU LED functions

LED Function

Power (green) Power supply detection

Ethernet (yellow) Ethernet traffic detection

For a full list of LED states and fault-finding actions, refer to Testing link end hardware
on page 8-2.

1-12

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Powered indoor unit (PI DU)

Redundancy and alternative powering configurations

The PTP 500 Series can be powered from an external DC source and can be provided with
power supply redundancy as follows:

• External DC supply only (Figure 7): This configuration is for use where there is no

mains supply.

• External DC supply and AC supply (Figure 8): This configuration provides redundancy

through the use of mains and DC supply.

• External DC supply and redundant AC Supply (Figure 9): This configuration guards

against mains failure and failure of the DC output of one PIDU.

Figure 7 External DC supply only

Figure 8 External DC supply and AC supply

phn-2511_005v000 (Mar 2013)

1-13

Powered indoor u nit (PIDU) Chapter 1: Product d es cription

Figure 9 External DC supply and redundant AC supply

Remote LEDs and recovery switch

The PIDU provides a facility to connect remote LEDs and Recovery switch allowing the
PIDU to be mounted inside an enclosure. At the left hand end of the PIDU 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.

Figure 10 Remote LED and recovery switch wiring

1-14

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Powered indoor unit (PI DU)

Further reading on the PIDU

For more information on the PIDU, refer to the following:

• PIDU site selection on page 2-6 describes how to select a location for the PIDU.

• Ordering components on page 2-46 lists the components required for PTP 500

installations, including PIDU units, with Cambium part numbers.

• PIDU specifications on page 4-3 contains specifications of the PIDU such as

dimensions, weight, environmental and electrical requirements.

• Installing the PIDU on page 5-27 describes how to install the PIDU, connect it to the

ODU, and prepare the network cables.

• Task 1: Connecting to the unit on page 6-3 describes how to connect the PIDU to a

management PC to allow configuration and alignment of the PTP 500.

• Task 15: Connecting link to the network on page 6-91 describes how to connect the

PIDU to the network when configuration, installation and alignment are complete.

• Testing link end hardware on page 8-2 describes how the PIDU is used when testing

the link end hardware for suspected faults.

phn-2511_005v000 (Mar 2013)

1-15

Cabling and lightning protection Chapter 1: Product d es cription

Cabling and lightning protection

This section describes the cabling and lightning protection components of PTP 500
installations.

PTP and lightning protection

The PIDU meets the low level static discharge specifications identified in Electromagnetic

compatibility (EMC) compliance on page 4-26 but does not provide lightning or surge

suppression.

The amount of lightning protection is dependent on regulatory and end user requirements.
The standard ODU is fitted with surge limiting circuits and other features to minimize the
risk of damage due to nearby lightning strikes. To be fully effective, these standard
features require some additional equipment to be configured as part of the system
installation.

The units are not designed to survive direct lightning strike. For this reason they
must not be installed in ‘Zone A’, as defined in Grounding and lightning

protection on page 2-19. Mounting in Zone A may put equipment, structures and

life at risk.

Outdoor connections

The term ‘drop cable’ refers to the cable that is used for all connections that terminate
outside the building, for example, connections between the ODU, LPU (if installed), GPS
receiver (if installed) and the ODU port of the PIDU.

For outdoor connections, always use Cat5e cable that is gel-filled and shielded with
copper-plated steel. This is the only type of outdoor drop cable supported in this
application.

1-16

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Cabling and lightning protection

Indoor connections

The Cat5e cable that connects the PIDU to the network equipment must meet the
following requirements:

• Screening: Must be either foil screen (FTP) or braided screen (STP) cable.

• Connectors: Must use screened RJ45 connectors with metal shells at both ends.

• Electrical connection: There must be a continuous electrical connection between

both screened connectors.

The connected network equipment must feature screened RJ45 connectors and must be
connected to ground, otherwise the PIDU will not be grounded, and this may increase the
levels of unwanted radiation from the ODU - PIDU cables.

The ODU network connection implements automatic MDI/MDI-X sensing and pair
swapping, allowing connection to networking equipment that requires cross-over cables
(MDI-X networks) or straight-through cables (MDI Networks).

Cable grounding kits

Drop cables must be grounded at the points specified in Grounding and lightning

protection on page 2-19. One cable grounding kit (Figure 11) is required for each drop

cable grounding point.

Figure 11 Cable grounding kit for 1/4” and 3/8” cable

phn-2511_005v000 (Mar 2013)

1-17

Cabling and lightning protection Chapter 1: Product description

Lightning protection units (LPUs)

One LPU single end kit (Figure 12) is required for each ODU drop cable. If GPS is installed
(for PTP-SYNC), one additional LPU kit is required for the GPS drop cable. The LPU is
installed near the point at which the drop cable enters the building.

Figure 12 LPU single end kit

Further reading on cabling and lightning protection

For more information on cabling and lightning protection, refer to the following:

• Maximum cable lengths on page 2-7 gives maximum permitted lengths of interface

cables in PTP 500 installations.

• Grounding and lightning protection on page 2-19 describes the grounding and

lightning protection requirements of a PTP 500 installation.

• Ordering components on page 2-46 lists the components required for PTP 500

installations, including cables, connectors, grounding kits and LPUs.

• Installing the drop cable and LPU on page 5-14 describes how to install the drop cable

from the ODU to the LPU and PIDU, and to provide grounding for the installation.

• Installing the PIDU on page 5-27 describes how to prepare the indoor cables to connect

to the network.

1-18

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide PTP-SYNC unit

PTP-SYNC unit

This section describes the (optional) PTP-SYNC unit and its interfaces. This unit may be
used to implement TDD synchronization.

PTP-SYNC unit description

The PTP-SYNC unit (Figure 13) is an optional component. It is required when TDD
synchronization is implemented using PTP-SYNC. It measures the difference between the
TDD frame timing and a 1 Hz timing reference, and signals this time difference to the
ODU.

For more information on this feature, refer to TDD synchronization on page 1-31.

The PTP-SYNC is a compact indoor unit mounted on a wall or a shelf or (using an optional
rack mounting adaptor) in a standard 19 inch rack. It is powered using standard power­over-Ethernet from the PIDU. One PTP-SYNC unit is required for each synchronized link.

Figure 13 PTP-SYNC kit

Model number

The PTP-SYNC model number (for example WB3665HH, WB3665BB or WB3665AA) is
located underneath the unit, on the bar code label.

Legacy installations may incorporate PTP-SYNC model number WB3665AA. This model
does not provide all of the LED states that are available in later models. Installations with
this model are subject to shorter maximum cable lengths (see Maximum cable lengths on
page 2-7).

phn-2511_005v000 (Mar 2013)

1-19

PTP-SYNC unit Chapter 1: Product d es cription

PTP-SYNC unit interfaces

The PTP-SYNC front panel is illustrated in Figure 14. The annotated interfaces are
described in Table 6 and Table 7.

Figure 14 PTP-SYNC front panel

Table 6 PTP-SYNC front panel interface functions

Number Description Function

1 GPS/SYNC IN Input from GPS receiver or from the daisy-chained

SYNC OUT signal of another PTP-SYNC.

2 SYNC OUT Output to daisy-chained PTP-SYNC units.

3 UPGRADE Input for software upgrades. Contact Cambium for

instructions.

4 1PPS IN Coaxial alternative to GPS/SYNC IN. Peak input voltage

must not exceed 5 V.

5 LED bank LEDs and their functions are described in Table 7.

6 PIDU IN Input from PIDU.

7 ODU OUT Output to ODU.

8 Ground stud For connecting to a ground point.

Table 7 PTP-SYNC LED functions

LED Function

GPS GPS satellite data detection.

SYNC SYNC OUT port data detection.

STATUS Power and satellite lock detection.

ODU ODU signal detection.

1-20

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide PTP-SYNC unit

Further reading on PTP-SYNC

For more information on PTP-SYNC and TDD synchronization, refer to the following:

• TDD synchronization on page 1-31 describes how TDD synchronization is achieved

using PTP-SYNC.

• PTP-SYNC site selection on page 2-6 describes factors to be considered when choosing

sites for the PTP-SYNC unit.

• Configuration options for TDD synchronization on page 2-28 describes the different

TDD synchronization methods that may be implemented using PTP-SYNC.

• Mounting options for the PTP-SYNC GPS receiver on page 2-32 describes the

requirements of the (optional) GPS receiver for PTP-SYNC.

• Ordering components on page 2-46 lists the components required for PTP 500

installations, including PTP-SYNC and GPS units, with Cambium part numbers.

• PTP-SYNC specifications on page 4-4 contains specifications of the PTP-SYNC unit that

is supplied by Cambium for PTP 500 installations.

• Installing a PTP-SYNC unit on page 5-30 describes how to install a PTP-SYNC unit.

• Installing a GPS receiver for PTP-SYNC on page 5-35 describes how to install an

optional GPS receiver for PTP-SYNC.

• Task 6: Configuring wireless and telecoms interfaces on page 6-40 describes how to

configure TDD synchronization.

• Testing PTP-SYNC on page 8-12 describes how to test a PTP-SYNC installation when a

fault is suspected.

phn-2511_005v000 (Mar 2013)

1-21

Wireless operation Chapter 1: Product d es cription

Wireless operation

This section describes how PTP 500 wireless links are operated, including modulation
modes, power control and security.

Time division duplexing

TDD cycle

PTP 500 links operate using Time Division Duplexing (TDD). They use a TDD cycle in
which the ODUs alternately transmit and receive TDD bursts. The TDD cycle is illustrated
in Figure 15. The steps in the cycle are as follows:

1. The TDD master transmits a burst to the TDD slave.

2. A delay occurs as the master-slave burst propagates over the link.

3. The slave receives the burst from the master.

4. The slave processes the master-slave burst.

5. The slave transmits a burst to the master.

6. A delay occurs as the slave-master burst propagates over the link.

7. The master receives the burst from the slave.

8. The master transmits the next burst to the slave.

TDD frame parameters

The TDD burst duration varies depending on the following:

• Channel bandwidth

• Link range

• Link optimization mode

• Link symmetry

• Offered traffic loading.

The TDD frame duration varies depending on the following:

• TDD burst duration master-slave.

• TDD burst duration slave-master.

• Link range.

1-22

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Wireless operation

The propagation delay in Step 2 is necessarily equal to the propagation delay in Step 5,
and is determined solely by the link range. There will be added delays between rx and tx

on the master and slave to minimize interference.

Figure 15 TDD cycle

Channel selection

The PTP 500 Series links are capable of transmitting and receiving on the same channel or
on different channels. In other words, the slave-master direction may use a different
channel from the master-slave direction. Independent selection of transmit and receive
frequencies can be useful in planned networks or for countering interference.

When links operate in radar avoidance regions, each unit must monitor its transmit
channel for the presence of radar signals, and thus transmit and receive channels are
always identical.

phn-2511_005v000 (Mar 2013)

1-23

Wireless operation Chapter 1: Product d es cription

Link mode optimization

Link mode optimization allows the link to be optimized according to the type of traffic that
will be bridged. The link supports two modes, IP Traffic and TDM Traffic.

IP traffic

IP Traffic mode is optimized to provide the maximum possible link capacity. IP Traffic
mode is an appropriate choice where applications in the bridged networks provide some
measure of reliable transmission, and where very low latency is not critical. IP mode
supports both fixed and adaptive link symmetry (see Link symmetry on page 1-24).

TDM traffic

TDM Traffic mode is optimized to provide the lowest possible latency. TDM Traffic mode
additionally implements a more conservative approach to adaptive modulation, leading to
lower error rates in fading channels at the expense of slightly lower link capacity. TDM
Traffic mode is an appropriate choice for delay intolerant data without reliable
transmission (for example voice over IP data). TDM mode is selected automatically when
Telecom interfaces are enabled.

Link symmetry

The PTP 500 Series provides four configuration options for apportioning the available
capacity between the two link directions.

• Symmetric: The Master and Slave have equal capacity. The system achieves this by

allocating an equal Burst Duration for the Master and the Slave.

• 3:1 The capacity in the direction Master to Slave is three times that of the direction

Slave to Master. The system series achieves this by setting the Burst Duration of the
Master to three times that of the Slave.

• 1:3 The capacity in the direction Slave to Master is three times that of the direction

Master to Slave. The system achieves this by setting the Burst Duration of the Slave to
three times that of the Master.

The 3:1 and 1:3 modes are not available when TDD synchronization is enabled or when
5 MHz bandwidth is selected.

1-24

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Wireless operation

• Adaptive: The capacity allocated to a given link direction is dependent on the offered

level of network traffic in both link directions. If the level of offered traffic in both
directions is equally high or equally low, the system will allocate equal capacity to both
directions. If however the offered level of traffic is greater in one direction, it is
allocated a greater proportion of the overall link capacity. The system achieves this by
increasing (or decreasing) the duration of the Transmit Burst in a given link direction
as the offered level of network traffic increases (or decreases) in this same direction.
This is done independently for the two directions.

Adaptive mode is not available in the following configurations:

o When link mode optimization is set to TDM Traffic see Link mode optimization on

page 1-24).

o When TDD synchronization is enabled.
o In regions where radar avoidance is operational (see Radar avoidance on page 1-

28).

o When 5 MHz bandwidth is selected.

OFDM and channel bandwidth

The PTP 500 transmits using Orthogonal Frequency Division Multiplexing (OFDM). This
wideband signal consists of many equally spaced sub-carriers. Although each sub carrier is
modulated at a low rate using conventional modulation schemes, the resultant data rate
from all the sub-carriers is high. OFDM works exceptionally well over a Non-Line-of-Sight
(NLoS) channel.

The channel bandwidth of the OFDM signal is configurable to one of three values: 5 MHz,
10 MHz and 15 MHz. Higher bandwidths provide greater link capacity at the expense of
using more spectrum. Systems configured for a narrower channel bandwidth provide
better receiver sensitivity and can also be an appropriate choice in deployments where the
amount of free spectrum is limited.

Each channel is offset in center frequency from its neighboring channel by 5 MHz.

The Channel Bandwidth must be configured to the same value at both ends of the link.

Spectrum management

The spectrum management feature of the PTP 500 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.

phn-2511_005v000 (Mar 2013)

1-25

Wireless operation Chapter 1: Product d es cription

Spectrum management measurements

The system performs two mean signal measurements per TDD cycle, per channel. This
mean measurement represents the mean received signal power for the measurement
period (40 microseconds).

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

Measurement analysis

Spectrum Management uses statistical analysis to process the received peak and mean
measurement. The statistical analysis is based on a fixed, one minute, measurement
quantization period. Spectrum Management collects data for the specified quantization
period and only at the end of the period is the statistical analysis performed. The analysis
produces three key metrics for each channel:

• Peak of Means

• 99.9% Percentile of the Means

• Mean of Means

These metrics are defined in Interpreting the spectrum management plots on page 7-25.

Statistical summary

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.

Spectrum management in fixed frequency mode

The transmit and receive frequencies can be fixed in a PTP 500 wireless link. Once fixed
frequency mode is configured, the spectrum management software will not attempt to
move the wireless link to a channel with lower co-channel and 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
(see Step 2: Wireless configuration on page 6-46). Care must also be taken to ensure that
the frequency allocations at each end of the link are compatible.

1-26

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Wireless operation

Fixed frequency mode is not available in regions where radar detection is required by the
regulations.

Adaptive modulation

The PTP 500 can transport data over the wireless link using a number of different
modulation modes ranging from 64QAM 0.83 to BPSK 0.50. For a given channel bandwidth
and TDD frame structure, each modulation mode transports data at a fixed rate. Also, the
receiver requires a given signal to noise ratio in order to successfully demodulate a given
modulation mode. Although the more complex modulations such as 64QAM 0.83 will
transport data at a much higher rate than the less complex modulation modes, the receiver
requires a much higher signal to noise ratio.

The system provides an adaptive modulation scheme where the receiver constantly
monitors the quality of the received signal and notifies the far end of the link of the
optimum modulation mode with which to transmit. In this way, optimum capacity is
achieved at all times. This is one of a number of features which allows the system to
operate in challenging non-line of sight radio channels.

Specifications of capacity for all channel bandwidths, modulation modes and
configurations are provided in Data throughput capacity on page 4-41.

Specifications of receive level thresholds for each modulation mode (assuming no
interference) are provided in the various system threshold tables in Chapter 4: Reference

information.

MIMO

Multiple-Input Multiple-Output (MIMO) techniques provide protection against fading and
increase the probability that the receiver will decode a usable signal. When the effects of
MIMO are combined with those of OFDM techniques and a high link budget, there is a
high probability of a robust connection over a non-line-of-sight path.

The PTP 500 transmits two signals on the same radio frequency, one of which is vertically
polarized and the other horizontally polarized. The system also has the ability to adapt
between two modes of operation:

PTP LINKPlanner includes an estimate of mean data rate, the data rate provided by each
modulation and the percentage of time spent in each modulation mode.

• Dual Payload: When the radio channel conditions allow, the system will transmit two

different and parallel data streams, one on the vertical channel and one on the
horizontal channel. This doubles the capacity of the system.

phn-2511_005v000 (Mar 2013)

1-27

Wireless operation Chapter 1: Product d es cription

• Single Payload: As the radio channel becomes more challenging, the system has the

ability to detect this and switch to a mode which transmits the same data stream on
both vertical and horizontal channels. This provides polar diversity and is another key
feature which allows the system to operate in challenging non- line of sight radio
channels.

The two modes have been implemented by the introduction of two sets of modulation
modes. The lower order modulations (BPSK 0.50 up to QPSK 0.50) are only available as
single payload modes. Each of the higher order modulations (QPSK 0.75 to 64QAM 0.83)
are available in single payload mode and dual payload mode. The switching between
modes is automatically controlled by the adaptive modulation feature described in

Adaptive modulation on page 1-27.

The system automatically chooses between dual and single payload to try to increase the
capacity of a link. However the user may choose 'single payload only' at installation time,
forcing this more robust option.

Dynamic spectrum optimization

The PTP 500 uses an interference mitigation technique known as Intelligent Dynamic
Spectrum Optimization (DSO). Both the Master and Slave continually monitor for
interference on all channels and then select the best frequency of operation. This is a
dynamic process where the system can continually move channels in response to changes
in interference. Two modes of operation are available:

• First mode: the two link directions are forced to select the same frequency, determined

by the Master.

• Second mode: the frequency of operation can be determined independently for each

direction. This mode is not permitted in radar regions.

DSO was previously known as Intelligent Dynamic Frequency Selection (i-DFS).

Radar avoidance

In regions where protection of radars is part of the local regulations, the PTP 500 must
detect interference from radar-like systems and avoid co-channel operation with these
systems.

To meet this requirement, the PTP 500 implements the following features:

• The equipment can only transmit on available channels, of which there are none at

initial power up. The radar detection algorithm will always scan a usable channel for 60
seconds for radar interference before making the channel an available channel.

1-28

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Wireless operation

• This compulsory channel scan will mean that there is at least 60 seconds service

outage every time radar is detected and that the installation time is extended by at
least 60 seconds even if there is found to be no radar on the channel

• When operating on a channel, the spectrum management algorithm implements a

radar detection function which looks for impulsive interference on the operating
channel. If impulsive interference is detected, spectrum management will mark the
current operating channel as having detected radar (unavailable channel) and initiate a
channel hop to an available channel. The previous operating channel will remain in the
unavailable state for thirty minutes after the impulsive interference pulse was
detected.

• After the thirty minutes have expired the channel will be returned to the usable

channel pool.

There is a secondary requirement for bands requiring radar avoidance. Regulators have
mandated that products provide a uniform loading of the spectrum across all devices. In
general, this prevents operation with fixed frequency allocations. However:

• ETSI regulations do allow frequency planning of networks (as that has the same effect

of spreading the load across the spectrum).

• The FCC does allow channels to be barred if there is actually interference on them.

Fixed frequency allocation is not recommended in radar avoidance regions, as any radar
detection would cause a system outage of at least 30 minutes.

Security

The PTP 500 supports optional encryption for data transmitted over the wireless link. The
encryption algorithm used is the Advanced Encryption Standard (AES) with 128-bit and
256-bit key size. AES is a symmetric encryption algorithm approved by U.S. Government
organizations (and others) to protect sensitive information. The AES implementation in
PTP 500 is approved to FIPS-197.

Encryption is enabled through the purchase of an upgrade.

Region codes

Some aspects of wireless operation are controlled, enforced or restricted according to a
region code. Region codes represent individual countries (for example Denmark) or
regulatory regions (for example FCC or ETSI).

Region codes affect the following aspects of wireless operation:

• Maximum transmit power

• Radar avoidance

phn-2511_005v000 (Mar 2013)

1-29

Wireless operation Chapter 1: Product d es cription

• Transmit power reduction in edge channels

• Frequency range

• Channel plan

A region code is encoded in the license key. The region code can be changed by generating
and entering a new license key.

Some units are supplied with two alternative license keys for different region codes, one
of which is factory configured.

To avoid possible enforcement action by the country regulator, always operate links in
accordance with local regulations.

PTP networks

Using Dynamic Spectrum Optimization

The Dynamic Spectrum Optimization (DSO) feature allows a PTP 500 unit to select
wireless channels for a lower level of radio frequency (RF) interference. This approach is
appropriate where the network consists of a small number of PTP links, or where the RF
interference is predominantly from equipment belonging to other operators.

Using frequency planning

Networks will benefit from the use of fixed channel allocations if (a) the network consists
of multiple PTP links, and (b) RF interference predominantly arises from equipment in the
same network.

Frequency planning is the exercise of assigning operating channels to PTP units so as to
minimize RF interference between links. Frequency planning must consider interference
from any PTP unit to any other PTP unit in the network. Low levels of interference
normally allow for stable operation and high link capacity.

The frequency planning task is made more straightforward by use of the following
techniques:

• Using several different channels

• Separating units located on the same mast

• Using high performance (directional) external antennas

For help with planning networks, refer to Chapter 2: Planning considerations, or contact
your Cambium distributor or re-seller.

1-30

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Wireless operation

Synchronized networks

TDD synchronization can be used to relax constraints on the frequency planning of
PTP 500 networks. Synchronization has the following benefits:

• Allows tighter frequency re-use, and thus wider channel bandwidth.

• Allows more convenient collocation of units on a single mast.

• Allows use of smaller or lower performance antennas.

• Reduces inference, resulting in use of more efficient modulation modes.

In a correctly designed synchronised network, all links are configured with the same TDD
frame duration, and the TDD frame contains guard periods longer than the propagation
delay between the most distant interfering units.

Each synchronized unit is assigned to one of two phases. A master ODU can be assigned to
either phase. A slave ODU must be assigned to a different phase from the associated
master ODU. The phase is set by suitable configuration of TDD Frame Offset.

TDD synchronization eliminates RF interference between units in the same phase. This
means that frequency planning in a synchronized network is concerned only with
interference between units in different phases. Frequency planning is still necessary, but
the number of potential interference paths to be considered is halved. Frequency planning
in a synchronized TDD network has approximately the same level of complexity as
frequency planning in a Frequency Division Duplex (FDD) network.

TDD synchronization

PTP 500 does not allow TDD synchronization to be enabled when telecoms (E1 or T1) is
enabled.

Additional hardware

To synchronize PTP 500 links, one PTP-SYNC unit is required for each master ODU. The
PTP-SYNC unit is connected in line in the drop cable between the PIDU and the ODU, and
is collocated with the PIDU.

PTP 500 System Releases earlier than 500-04-00 do not support PTP-SYNC.

PTP 300 System Releases earlier than 300-05-01 do not support PTP-SYNC.

phn-2511_005v000 (Mar 2013)

1-31

Wireless operation Chapter 1: Product d es cription

Timing references for use with PTP-SYNC

PTP-SYNC requires an external timing reference in all but the simplest networks. Up to
ten PTP-SYNCs can be connected in a chain to share the timing signal from one timing
reference. In the majority of applications, one reference is required for each site that
contains master ODUs.

The timing reference can be from any timing system that provides a 1 Hz signal,
accurately synchronized in frequency and phase with a network-wide master timing
reference. GPS timing receivers are a very practical way of obtaining a suitable reference.
The PTP-SYNC is compatible with the following GPS timing receivers:

• Trimble Acutime™ Gold GPS receiver

In simple networks where all master ODUs are at a single site, the external reference can
be omitted. In this case, one ODU acts as a reference for other collocated units.

Configuring the TDD frame

In synchronized operation, frame duration and burst duration must be configured directly
in the web-based management interface. Frame duration must be identical across all links
in a synchronized network.

PTP LINKPlanner provides a capability for computing suitable frame parameters in a
synchronized network. Please refer to the
configuring TDD synchronization.

Link symmetry is always 1:1 in synchronized networks.

PTP LINKPlanner User Guide

for guidance on

Link capacity in synchronized networks

The TDD frame duration is extended in synchronized networks to allow for the propagation
delay of the longest link in the network and to incorporate additional guard periods. These
guard periods protect against delayed interference from distant units in the same network.

The longer frame duration results in slightly lower link capacity than for an equivalent
non-synchronized link with the same channel bandwidth and modulation mode. However,
TDD synchronization also reduces interference, and this may allow operation in higher
modulation modes. The benefit of operating in a higher modulation mode normally
outweighs the penalty of the slightly longer TDD frame.

Advantages of PTP-SYNC

The advantages of PTP-SYNC over alternative technologies are:

• PTP-SYNC does not require individual GPS receivers, nor must they be located close to

the ODUs. This reduces the complexity and the cost of the installation on the mast.

1-32

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Wireless operation

• The GPS receiver can be located anywhere with a clear view of the sky, offering

additional flexibility in the installation.

• The PTP-SYNC solution is compatible with standard 1 Hz interfaces, allowing an

operator to take advantage of alternative timing references that may be already
present at the site.

• The recommended GPS receiver continues to provide accurate timing even after the

number of received satellites has dropped down to one, leading to significantly better
availability of the reference signal.

• The PTP-SYNC offers the possibility of creating synchronized single-hub networks

where no GPS receiver is required.

Further reading on wireless operation

For information on planning wireless operation, refer to the following:

• Regulatory planning on page 2-2 describes the regulatory restrictions that affect radio

spectrum usage, such as frequency range and radar avoidance.

• Link planning on page 2-10 describes factors to be taken into account when planning

links, such as range, path loss and data throughput, and introduces PTP LINKPlanner.

• Wireless specifications on page 4-7 contains specifications of the PTP 500 wireless

interface, such as RF bands, channel width, spectrum settings, maximum power and
link loss.

• Compliance with safety standards on page 4-26 lists the safety specifications against

which the PTP 500 has been tested, and describes how to keep RF exposure within
safe limits.

• Compliance with radio regulations on page 4-30 describes how the PTP 500 complies

with the radio regulations that are in force in various countries.

• Type approval status on page 4-36 contains notifications of compliance with the radio

regulations that are in force in various regions.

For information on configuring and operating the wireless link, refer to the following:

• Task 6: Configuring wireless and telecoms interfaces on page 6-40 describes how to

configure the wireless interface using the installation wizard.

• Comparing actual to predicted performance on page 6-89 describes how to check that

a newly installed link is achieving predicted levels of performance.

• Managing performance on page 7-36 describes how to manage the performance of a

PTP 500 link.

• Testing the radio link on page 8-10 describes what to do if the radio link is not working,

or it is unreliable, or the data throughput rate is too low.

phn-2511_005v000 (Mar 2013)

1-33

Ethernet bridging Chapter 1: Product d es cription

Ethernet bridging

This section describes how the PTP 500 controls Ethernet data, in both the customer and
system management networks.

Customer network

Transparent Ethernet service

The PTP 500 provides an Ethernet service between the Ethernet port at a local ODU and
the Ethernet port at an associated remote ODU. The Ethernet service is based on
conventional layer two transparent bridging, and is equivalent to the Ethernet Private Line
(EPL) service defined by the Metro Ethernet Forum (MEF).

The service is transparent to untagged frames, standard VLAN frames, priority-tagged

frames, provider bridged frames, Q-in-Q frames and provider backbone bridged frames. In

each case, the service preserves MAC addresses, VLAN ID, Ethernet priority and Ethernet
payload in the forwarded frame. The maximum frame size for bridged frames is 2000
octets.

Layer two control protocols

The PTP 500 is transparent to layer two control protocols (L2CP) including:

• Spanning tree protocol (STP), rapid spanning tree protocol (RSTP)

• Multiple spanning tree protocol (MSTP)

• Link aggregation control protocol (LACP)

• Link OAM, IEEE 802.3ah

• Port authentication, IEEE 802.1X

• Ethernet local management interface (E-LMI), ITU-T Q.933.

• Link layer discovery protocol (LLDP)

• Multiple registration protocol (MRP)

• Generic attribute registration protocol (GARP)

The system does not generate or respond to any L2CP traffic.

1-34

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Ethernet bridging

Quality of service for bridged Ethernet traffic

The PTP 500 supports eight traffic classes for Ethernet frames queued for transmission
over the wireless link. Ethernet frames are classified by inspection of the Ethernet priority
code point in the outermost VLAN tag.

The system provides a configurable mapping between Ethernet priority and traffic class,
together with a simple way to restore a default mapping based on the recommended
default in IEEE 802.1Q-2005. Untagged frames can be classified into any one of the eight
classes.

Scheduling for transmission over the wireless link is by strict priority. In other words, a
frame at the head of a given queue is transmitted only when all higher priority queues are
empty.

Fragmentation

The PTP 500 minimizes latency and jitter for high-priority Ethernet traffic by fragmenting
Ethernet frames before transmission over the wireless link. The fragment size is selected
automatically according to channel bandwidth and modulation mode of the wireless link.
Fragments are reassembled on reception, and incomplete Ethernet frames are discarded.

Management network

IP interface

The PTP 500 ODU contains an embedded management agent with a single IP interface.
Network management communication is exclusively based on IP and associated higher
layer transport and application protocols. The default IP address of the management agent
is 169.254.1.2 in the master ODU and 169.254.1.1 in the slave ODU. The products do not
require use of supplementary serial interfaces.

MAC address

The management agent end-station MAC address is recorded on the enclosure. The MAC
address is not configurable by the user.

VLAN membership

The management agent can be configured to transmit and receive either untagged,
priority-tagged, C-tagged (IEEE 802.1Q) or S-tagged (IEEE 802.1ad) frames. S-tagged
frames must be single tagged, in other words, an S-tag with no encapsulated C-tag. The
VLAN ID can be 0 (priority tagged) or in the range 1 to 4094.

phn-2511_005v000 (Mar 2013)

1-35

Ethernet bridging Chapter 1: Product d es cription

In-band management

In the in-band management mode, the management agent can be reached from the
Ethernet port at the local ODU, and (assuming that the wireless link is established) the
Ethernet port at the remote ODU.

Management frames in the customer network are processed by the management agent if
(a) destination MAC address in the frame matches the CMU MAC address, and (b) the
VLAN ID in the frame matches the VLAN configuration of the management agent.

If Local Packet Filtering is enabled, unicast frames forwarded to the management agent
are filtered, that is, not forwarded in the customer network.

In-band quality of service

Frames generated within the management agent may be assigned a configured Ethernet
priority. Management frames are multiplexed with customer frames of the same priority
for transmission at the wireless port.

Source address learning

If Local Packet Filtering is enabled, the system learns the location of end stations from the
source addresses in received management frames. The agent filters transmitted
management frames to ensure that the frame is transmitted at the Ethernet port, or over
the wireless link as appropriate. If the end station address is unknown, then management
traffic is transmitted at the Ethernet port and over the wireless link.

Wireless link down alert

The PTP 500 provides an optional indication of failure of the wireless link by means of a
brief disconnection of the data port. The Wireless link down alert can be used to trigger
protection switching by Spanning Tree Protocol (STP) or Ethernet Automatic Protection
Switching (EAPS) in a redundant network.

Back-to-back links

PTP 500 will not operate correctly if a direct cabled connection is made between two
PIDUs. Where two or more links are deployed in a chain, always use an Ethernet switch or
router to interconnect the links at the relay points.

1-36

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Ethernet bridging

Protocol model

Ethernet bridging behavior at each end of the wireless link is equivalent to a two-port,
managed, transparent MAC bridge where the two ports are:

• Ethernet Port

• Wireless Port

Frames are transmitted at the Wireless port over a proprietary point-to-point circuit-mode
link layer between ends of the link. Ethernet frames received at the Ethernet port, or
generated internally within the management agent, are encapsulated within a lightweight
MAC layer for transmission over the wireless link.

Protocol layers involved in bridging between Ethernet and wireless interfaces are shown in

Figure 16. Protocol layers involved in bridging between external interfaces and the

management agent are shown in Figure 17. In these figures, the layers have the meanings
defined in IEEE 802.1Q-2005.

Figure 16 Protocol layers between Ethernet and wireless interfaces

phn-2511_005v000 (Mar 2013)

1-37

Ethernet bridging Chapter 1: Product description

Figure 17 Protocol layers between external interfaces and the management agent

Further reading on Ethernet bridging

For more information on Ethernet bridging, refer to the following:

• Data network planning on page 2-35 describes factors to be considered when planning

PTP 500 data networks.

• Data network specifications on page 4-21 contains specifications of the PTP 500

Ethernet interfaces.

• Data throughput tables on page 4-41 provides instructions, tables and graphs to allow

calculation of the data rate capacity that can be provided by alternative PTP 500
configurations.

• Task 6: Configuring wireless and telecoms interfaces on page 6-40 describes how to

configure the IP and Ethernet attributes of the PTP 500.

1-38

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Ethernet bridging

• Reviewing system configuration attributes on page 6-87 describes how to review the IP

and Ethernet attributes of the PTP 500.

phn-2511_005v000 (Mar 2013)

1-39

Telecoms circuits Chapter 1: Product d es cription

Telecoms circuits

This section describes how telecoms traffic (E1 or T1) may be carried over PTP 500 links.

PTP 500 does not allow TDD synchronization to be enabled when telecoms (E1 or T1) is
enabled.

The PTP 500 provides native support for one E1 link, or one T1 link. The link relays
unstructured E1 or T1 data and provides accurate timing transfer.

Lowest telecoms modulation mode

In narrow channel bandwidth and lower modulation modes, the link may have insufficient
capacity to relay the E1/T1 payload; in this case, the wireless link continues to carry timing
information in order to maintain accurate clock synchronization. The relay of telecoms
data resumes automatically when the link reaches a suitable modulation mode.

Links that are able to operate consistently in a high modulation mode can take advantage
of lower link latency. This option is configured by setting the "Lowest Telecoms
Modulation Mode" during installation. Appropriate settings for this control may be
determined by using the PTP LINKPlanner tool. The reduction in latency is achieved by
disabling the relay of telecoms data in lower modulation modes, and this necessarily
results in somewhat lower availability for the telecoms circuit. The loss of availability can
be estimated using the PTP LINKPlanner.

The unit will override the user setting of Lowest Telecoms Modulation Mode if the selected
mode has insufficient capacity to carry the telecoms data, or if the mode demands very
high latency and requires more buffering than the link can provide. When the effective
mode differs for Single and Dual Payload operation two modes will be displayed: "Lowest

Dual Payload Modulation Mode" and "Lowest Single Payload Modulation Mode".

Fixed frequency operation

In a PTP 500 link, data errors may occur during channel changes on an operational link. It
may be appropriate to minimize channel-change-related errors in a link carrying Telecoms
traffic by preventing channel changes initiated by DSO. This can be achieved by barring all
channels except one in the Spectrum Management page, or alternately by selecting Fixed
Frequency mode. These steps unavoidably disable interference avoidance mechanisms,
and should not be taken if the risk of errors due to interference is more severe than the
risk due to channel changes.

1-40

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Telecoms circuits

Fixed frequency operation is not available when radar detection requirements exist in the
frequency band. Channel barring is allowed in radar regions, but it is unwise to bar all
channels except one, as any radar signals detected on that channel will drop the link for up
to 30 minutes.

Further reading on telecoms circuits

For more information on telecoms circuits, refer to the following:

• Installing an E1 or T1 interface on page 5-47 describes how to install the hardware for

an E1 or T1 interface.

• Task 6: Configuring wireless and telecoms interfaces on page 6-40 describes how to

configure the telecoms interfaces using the installation wizard.

• Testing a telecoms link on page 8-15 describes how to test and E1 or T1 link when a

fault is suspected.

phn-2511_005v000 (Mar 2013)

1-41

System management Chapter 1: Product d es cription

System management

This section introduces the PTP 500 management system, including the web interface,
installation, configuration, alerts and upgrades.

Management agent

PTP 500 equipment is managed through an embedded management agent. Management
workstations, network management systems or PCs can be connected to this agent using
standard management protocols multiplexed with user traffic at the Ethernet data port.

The management agent supports the following interfaces:

• Hyper text transfer protocol (HTTP)

• HTTP over transport layer security (HTTPS/TLS)

• RADIUS authentication

• TELNET

• Simple network management protocol (SNMP)

• Simple mail transfer protocol (SMTP)

• Simple network time protocol (SNTP)

• System logging (syslog)

Web server

The PTP 500 management agent contains a web server. The web server supports the HTTP
and HTTPS/TLS interfaces.

Web-based management offers a convenient way to manage the equipment from a locally
connected computer or from a network management workstation connected through a
management network, without requiring any special management software. The web­based interfaces are the only interfaces supported for system installation, and for the
majority of configuration management tasks.

1-42

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide System management

Web pages

The web-based management interfaces provide comprehensive web-based fault,
configuration, performance and security management functions organized into the
following web-pages and groups:

• Home: The Home web-page reports Wireless Link Status and basic information needed

to identify the link. The Home page additionally lists all active alarm conditions

• Status: The Status web-page reports the detailed status of the system.

• System: These web-pages are used for configuration management, including IP and

Ethernet, AES encryption keys, quality of service, software upgrade and installation of
license keys. The System pages additionally provide detailed counters and diagnostic
measurements used for performance management.

• Installation: The Installation Wizard is used in the initial configuration of the system

and arming the unit ready for alignment.

• Management: These web-pages are used to configure the network management

interfaces.

• Security: The Security Wizard is used to configure the HTTPS/TLS interface. The

Security Wizard is disabled until AES encryption is enabled by license key.

• Change Password: The Change Password web-page changes the web-interface

password of the active user. Users use this screen to change their own password.

• Logout: Allows a user to log out from the web-based interface.

Transport layer security

The HTTPS/TLS interface provides the same set of web-pages as the HTTP interface, but
allows HTTP traffic to be encrypted using Transport Layer Security (TLS). PTP 500 uses
AES encryption for HTTPS/TLS. Operation of HTTPS/TLS is enabled by purchase of an
optional AES upgrade as described in Task 3: Installing license keys on page 6-11.

HTTPS/TLS requires installation of a private key and a public key certificate where the
common name of the subject in the public key certificate is the IP address or host name of
the PTP 500 unit.

HTTPS/TLS operation is configured through the web-based interfaces using the Security
Wizard.

Details of the security material needed for HTTPS/TLS are provided in Security planning
on page 2-37.

The PTP 500 has no default public key certificate, and Cambium is not able to generate
private keys or public key certificates for specific network applications.

phn-2511_005v000 (Mar 2013)

1-43

System management Chapter 1: Product d es cription

User account management

PTP 500 allows a network operator to configure a policy for login attempts, the period of
validity of passwords and the action taken on expiry of passwords. See Configuring local

user accounts on page 6-30 for further details.

Identity-based user accounts

The PTP 500 web-based interface provides two methods of authenticating users:

• Role-based user authentication allows the user, on entry of a valid password, to access

all configuration capabilities and controls. This is the default method.

• Identity-based user authentication supports up to 10 users with individual usernames

and passwords.

When identity-based user accounts are enabled, a security officer can define from one to
ten user accounts, each of which may have one of the three possible roles:

• Security officer.

• System administrator.

• Read only.

Identity-based user accounts are enabled in the Local User Accounts page of the web­based interface.

Password complexity

PTP 500 allows a network operator to enforce a configurable policy for password
complexity. Password complexity configuration additionally allows a pre-determined best
practice configuration to be set. See Configuring local user accounts on page 6-30 for
further details.

1-44

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide System management

RADIUS authentication

PTP 500 supports remote authentication for users of the web interface using the Remote
Authentication Dial-In User Service (RADIUS) with one of the following authentication
methods:

• Challenge-Handshake Authentication Protocol (CHAP).

• Microsoft CHAP Version 2 (MS-CHAPv2).

PTP 500 supports connections to primary and secondary RADIUS servers. The RADIUS
interface is configured through the RADIUS Authentication page of the web-based
interfaces.

PTP 500 RADIUS supports the standard Service Type attribute to indicate authentication
roles of System Administrator and Read Only together with a vendor specific attribute to
indicate authentication roles of Security Officer, System Administrator, and Read Only.

Remote authentication can be used in addition to local authentication, or can be used as a
replacement for local authentication. If remote and local authentications are used
together, PTP 500 checks log in attempts against locally stored user credentials before
submitting a challenge and response for remote authentication. Remote authentication is
not attempted if the username and password match locally stored credentials.

RADIUS is only available when PTP 500 is configured for Identity-based User Accounts.
For more information, refer to Planning for RADIUS operation on page 2-44.

SNMP

The management agent supports fault and performance management by means of an
SNMP interface. The management agent is compatible with SNMP v1, SNMP v2c, and
SNMPv3 using the following Management Information Bases (MIBs):

• RFC-1493. BRIDGE-MIB. dot1dBase group.

• RFC-2233. IF-MIB. Interfaces group, and ifXTable table.

• RFC-3411. SNMP-FRAMEWORK-MIB. snmpEngine group.

• RFC-3412. SNMP-MPD-MIB. snmpMPDStats group.

• RFC-3413. SNMP-TARGET-MIB. snmpTargetObjects group and SNMP-NOTIFICATION-

MIB snmpNotifyTable table.

• RFC-3414. SNMP-USER-BASED-SM-MIB. usmStats group and usmUser group.

• RFC-3415. SNMP-VIEW-BASED-ACM-MIB vacmMIBObjects group.

• RFC-3418. SNMPv2-MIB. System group, SNMP group, and set group.

• RFC-3826. SNMP-USM-AES-MIB. usmAesCfb128Protocol OID.

• RFC-4293 IP-MIB, ipForwarding, ipAdEntAddr, ipAdEntIfIndex, ipAdEntNetMask

phn-2511_005v000 (Mar 2013)

1-45

System management Chapter 1: Product description

• PTP 500 Series proprietary MIB.

Simple Network Time Protocol (SNTP)

The clock supplies accurate date and time information to the system. It can be set to run
with or without a connection to a network time server (SNTP). It can be configured to
display local time by setting the time zone and daylight saving in the Time web page. If an
SNTP server connection is available, the clock can be set to synchronize with the server
time at regular intervals.

SNMPv3 security

SNMP Engine ID

PTP 500 supports three different formats for SNMP Engine ID:

• MAC address

• IP address

• Configurable text string

SNMPv3 security configuration is re-initialized when the SNMP Engine ID is changed.

User-based security model

PTP 500 supports the SNMPv3 user-based security model (USM) for up to 10 users, with
MD5, SHA-1, DES and (subject to the license key) AES protocols in the following
combinations:

• No authentication, no privacy,

• MD5, no privacy,

• SHA-1, no privacy,

• MD5, DES,

• SHA-1, DES,

• MD5, AES,

• SHA-1, AES.

Use of AES privacy requires the AES upgrade described in AES license on page 1-50. The
ODU will allow the creation of users configured with AES privacy protocol, regardless of
license key. However, a user configured to use AES privacy protocol will not be able to
transmit and receive encrypted messages unless the license key enables the AES
capability.

1-46

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide System management

View-based access control model

PTP 500 supports the SNMPv3 view-based access control model (VACM) with a single
context. The context name is the empty string. The context table is read-only, and cannot
be modified by users.

Access to critical security parameters

The SNMPv3 management interface does not provide access to critical security
parameters (CSPs). It is not possible to read or modify AES keys used to encrypt data
transmitted at the wireless interface.

MIB-based management of SNMPv3 security

PTP 500 supports a standards-based approach to configuring SNMPv3 users and views
through the SNMP MIB. This approach provides maximum flexibility in terms of defining
views and security levels appropriate for different types of user.

The system provides a default SNMPv3 configuration. This initial configuration is not
secure, but it provides the means by which a secure configuration can be created using
SNMPv3.

The secure configuration should be configured in a controlled environment to prevent
disclosure of the initial security keys necessarily sent as plaintext, or sent as encrypted
data using a predictable key. The initial security information should not be configured over
an insecure network.

The default configuration is restored when any of the following occurs:

• All ODU configuration data is erased.

• All SNMP users are deleted using the SNMP management interface.

• The SNMP Engine ID Format has been changed.

• The SNMP Engine ID Format is IP Address AND the IP Address has been changed.

• The SNMP Engine ID Format is Text String AND the text string has been changed.

• The SNMP Engine ID Format is MAC Address AND configuration has been restored

using a file saved from a different unit.

• SNMPv3 Security Management is changed from web-based to MIB-based.

The default user configuration is specified in SNMPv3 default configuration (MIB-based)
on page 2-43.

The system creates the initial user and template users with localized authentication and
privacy keys derived from the passphrase string 123456789. Authentication keys for the
templates users are fixed and cannot be changed. Any or all of the template users can be
deleted.

phn-2511_005v000 (Mar 2013)

1-47

System management Chapter 1: Product d es cription

The default user initial is created with a view of the entire MIB, requiring authentication
for SET operations. There is no access for template users.

VACM grants access for requests sent with more than the configured security level.

The default user initial will have read/write access to the whole of the MIB. This is
described in further detail in View-based access control model on page 1-47. The template
users have no access to the MIB in the default configuration. User

initial will normally be

used to create one or more additional users with secret authentication and privacy keys,
and with appropriate access to the whole of the MIB or to particular views of the MIB
according to the operator’s security policy. New users must be created by cloning template
users. The user
name and keys. Alternatively, the keys associated with

initial may then be deleted to prevent access using the well-known user

initial may be set to some new

secret value.

Web-based management of SNMPv3 security

PTP 500 supports an alternative, web-based approach for configuring SNMPv3 security. In
this case, the web-based interface allows users to specify SNMPv3 users, security levels,
privacy and authentication protocols, and passphrases. Web-based management will be
effective for many network applications, but the capabilities supported are somewhat less
flexible than those supported using the MIB-based security management.

Selection of web-based management for SNMPv3 security disables the MIB-based security
management.

Web-based management of SNMPv3 security allows for two security roles:

• Read Only

• System Administrator

Read Only and System Administrator users are associated with fixed views allowing access
to the whole of the MIB, excluding the objects associated with SNMPv3 security. System
Administrators have read/write access as defined in the standard and proprietary MIBs.

Web-based management of SNMPv3 security allows an operator to define the security
levels and protocols for each of the security roles; all users with the same role share a
common selection of security level and protocols.

Web-based security configuration is re-initialized when any of the following occurs:

• All ODU configuration data is erased.

• The SNMP Engine ID Format has been changed.

• The SNMP Engine ID Format is IP Address and the IP Address has been changed.

• The SNMP Engine ID Format is Text String and the text string has been changed.

• The SNMP Engine ID Format is MAC Address and configuration has been restored

using a file saved from a different unit.

1-48

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide System management

• SNMPv3 Security Management is changed from MIB-based to web-based.

Additionally, all SNMP user accounts are disabled when the authentication protocol, the
privacy protocol, or the security level is changed.

Downgrade of the license key

A possible lockout condition exists if a user downgrades the license key so as to disable the
AES capability when SNMPv3 users are configured with AES privacy and VACM is
configured to require privacy. In this case, recovery is by either (a) restoring the correct
license key, or (b) using recovery mode to erase all configuration and entering new
configuration.

Option (b) will cause default users and access configuration to be re-created.

System logging (syslog)

PTP 500 supports the standard syslog protocol to log important configuration changes,
status changes and events. The protocol complies with RFC 3164.

PTP 500 creates syslog messages for configuration changes to any attribute that is
accessible via the web-based interface, or via the enterprise MIB at the SNMP interface.

PTP 500 additionally creates syslog messages for changes in any status variable displayed
in the web-based interface.

PTP 500 creates syslog messages on a number of events (for example successful and
unsuccessful attempts to log in to the web-based interface).

PTP 500 can be configured to send syslog messages to one or two standard syslog servers.

Additionally, PTP 500 can be configured to log event notification messages locally. Locally­stored event messages survive reboot of the unit, and are overwritten only when the
storage capacity is exhausted (approximately 2000 messages). The locally stored events
can be reviewed using the web-based user interface.

Only users with ‘Security Officer’ role are permitted to configure the syslog client. Users
with Security Officer or System Administrator roles are permitted to review the locally
logged event messages.

phn-2511_005v000 (Mar 2013)

1-49

System management Chapter 1: Product d es cription

AES license

PTP 500 provides optional encryption using the Advanced Encryption Standard (AES).
Encryption is not available in the standard system.

AES upgrades are supplied as an access key purchased from your Cambium Point-to-Point
distributor or solutions provider. The access key authorizes AES operation for one ODU.
Two access keys are needed to operate AES on a link. The upgrade is applied by entering
an access key together with the MAC address of the target ODU into the PTP License Key
Generator web page, which may be accessed from the support web page (see Contacting

Cambium Networks on page 2).

The License Key Generator creates a new license key that is delivered by email. The
license key must be installed on the ODU. When the license key is installed, the ODU must
be rebooted before AES can be enabled. Once applied, the AES upgrade is bound to a
single ODU and is not transferrable.

AES encryption may be used in the following ways:

• At the wireless port to encrypt data transmitted over the wireless link.

• At the SNMP management interface in the SNMPv3 mode.

• At the HTTPS/TLS management interface.

Two levels of encryption are available to purchase:

• 128-bit: This allows an operator to encrypt all traffic sent over the wireless link using

128-bit encryption.

• 256-bit: This allows an operator to encrypt traffic using either 128-bit or 256-bit

encryption.

Encryption must be configured with the same size key in each direction.

AES encryption at the wireless port is based on pre-shared keys. An identical key must be
entered at each end of the link.

AES encryption for SNMPv3 is always based on a 128-bit key, regardless of level enabled
in the license key.

For more information, see:

• Task 3: Installing license keys on page 6-11

• Task 5: Configuring security on page 6-19

1-50

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide System management

Critical security parameters

Critical security parameters (CSPs) are as follows:

• Key of keys.

• AES encryption keys for the wireless interface.

• Private key for the HTTPS/TLS interface.

• Entropy value for the HTTPS/TLS interface.

• User account passwords for the web-based interface.

CSPs can be erased (zeroized) using the Zeroize CSPs page of the web-based interface or
by selecting the Zeroize CSPs option in Recovery mode.

Login information

PTP 500 optionally provides details of the most recent successful login, and the most
recent unsuccessful login attempt, for each user of the web-based interface.

Capacity upgrades

All PTP 500 product variants are supplied with a licensed data throughput capacity limit of
25 Mbps. This limit is based on the approximate aggregate (transmit plus receive) capacity
in the widest bandwidth and most efficient modulation mode. The following capacity
upgrades are available:

• From 25 Mbps to 52 Mbps

• From 52 Mbps to 105 Mbps

• From 25 Mbps to 105 Mbps

A capacity upgrade is supplied as an access key purchased from your Cambium Point-to­Point distributor or solutions provider. The upgrade is applied by entering an access key
together with the MAC address of the target ODU into the PTP License Key Generator web
page, which may be accessed from the support webpage (see Contacting Cambium

Networks on page 2). The License Key Generator creates a new license key delivered by

email. This is then applied via the web interface. Once applied, a capacity upgrade is
bound to a single ODU and is not transferrable.

phn-2511_005v000 (Mar 2013)

1-51

System management Chapter 1: Product description

Full capacity trial period: New PTP 500 ODUs can be configured to operate with full
transmit capacity (105 Mbps) during a trial period of duration 60 days, reverting to the
licensed capacity when the trial period expires. This trial period is also available on
existing ODUs that are upgraded to System Relelease to 500-05-01 (or later) from an
earlier release.

Task 3: Installing license keys on page 6-11 describes the procedures for checking licensed

capabilities, generating a license key, entering a license key and starting the full capacity
trial period.

Software upgrade

The management agent supports application software upgrade using either the web-based
interface or the SNMP interface.

PTP 500 software images are digitally signed, and the ODU will accept only images that
contain a valid Cambium PTP digital signature. The ODU always requires a reboot to
complete a software upgrade.

Obtain the application software and this user guide from the support website BEFORE
warranty expires.

ODU software version must be the same at both ends of the link. Limited operation may
sometimes be possible with dissimilar software versions, but such operation is not
supported by Cambium.

The management process for software upgrade is described in detail in Task 4: Upgrading

software version on page 6-15.

Software can be downgraded using Recovery mode as described in Recovery mode on
page 1-52.

Recovery mode

The PTP 500 recovery mode provides a means to recover from serious configuration errors
including lost or forgotten passwords and unknown IP addresses.

Recovery mode also allows new main application software to be loaded even when the
integrity of the existing main application software image has been compromised. The most
likely cause of an integrity problem with the installed main application software is where
the power supply has been interrupted during an earlier software upgrade.

The ODU operates in recovery mode in the following circumstances:

1-52

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide System management

• When a checksum error occurs for the main application software image.

• When the PIDU recovery button is pressed at the same time as the ODU is rebooted or

power cycled.

Recovery mode options

Options in recovery mode are as follows:

• Load new main application software.

• Reset all configuration data to factory default. This option resets IP and Ethernet

configuration.

• Reset IP and Ethernet configuration to factory default.

• Reboot with existing software and configuration.

If recovery mode has been entered because of a checksum error, by default the ODU will
reboot with existing software and configuration, following a 30 second wait.

The recovery software image is installed during manufacture of the ODU and cannot be
upgraded by operators.

For detailed instructions on using the recovery mode, see Using recovery mode on page 7-

53.

Further reading on system management

For more information on system management, refer to the following:

• Security planning on page 2-37: Describes how to plan for PTP 500 links to operate in

secure modes, including SNMP and SNMPv3.

• Chapter 6: Configuration and alignment describes all configuration and alignment

tasks that are performed when a PTP 500 link is deployed.

• Chapter 7: Operation provides instructions for operators of the PTP 500 web user

interface.

phn-2511_005v000 (Mar 2013)

1-53

System management Chapter 1: Product d es cription

1-54

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide

Chapter 2: Planning considerations

This chapter provides information to help the user to plan a PTP 500 link.

The following topics are described in this chapter:

• Regulatory planning on page 2-2 describes how to plan PTP 500 links to conform to the

regulatory restrictions that apply in the country of operation.

• Site planning on page 2-6 describes factors to be considered when choosing sites for

the ODU, PIDU and PTP-SYNC unit (if installed).

• Link planning on page 2-10 describes factors to be taken into account when planning

links, such as range, path loss and throughput. Introduces the PTP LINKPlanner.

• Planning for connectorized units on page 2-15 describes factors to be taken into

account when planning to use connectorized ODUs with external antennas in PTP 500
links.

• Grounding and lightning protection on page 2-19 describes the grounding and

lightning protection requirements of a PTP 500 installation.

• Configuration options for TDD synchronization on page 2-28 describes the different

TDD synchronization methods that may be implemented.

• Mounting options for the PTP-SYNC GPS receiver on page 2-32 describes the

requirements of the (optional) GPS receiver for PTP-SYNC.

• Data network planning on page 2-35: describes factors to be considered when planning

PTP 500 data networks.

• Security planning on page 2-37 describes how to plan for PTP 500 links to operate in

secure mode.

• Ordering components on page 2-46 describes how to select components for a planned

PTP 500 link (as an alternative to PTP LINKPlanner). It specifies Cambium part
numbers for PTP 500 components.

phn-2511_005v000 (Mar 2013)

2-1

Regulatory planning Chapter 2: Plannin g considerations

Regulatory planning

This section describes how to plan PTP 500 links to conform to the regulatory restrictions
that apply in the country of operation.

It is the responsibility of the user to ensure that the PTP product is operated in
accordance with local regulatory limits.

Contact the applicable radio regulator to find out whether or not registration of the
PTP 500 link is required.

Regulatory limits

The local regulator may restrict frequency usage and channel width, and may limit the
amount of conducted or radiated transmitter power. For details of these restrictions, refer
to Examples of regulatory limits on page 4-31.

Many countries impose EIRP limits (Allowed EIRP) on products operating in the bands
used by the PTP 500 Series. For example, in the 5.4 GHz and 5.8 GHz bands, these limits
are calculated as follows:

• In the 5.4 GHz band (5470 MHz to 5725 MHz), the EIRP must not exceed the lesser of

30 dBm or (17 + 10 x Log Channel width in MHz) dBm.

• In the 5.8 GHz band (5725 MHz to 5875 MHz), the EIRP must not exceed the lesser of

36 dBm or (23 + 10 x Log Channel width in MHz) dBm.

Some countries (for example the USA) impose conducted power limits on products
operating in the 5.8 GHz band.

Conforming to the limits

Ensure the link is configured to conform to local regulatory requirements by installing
license keys for the correct region code. In the following situations, the license key does
not automatically prevent operation outside the regulations:

• When using connectorized ODUs with external antennas, the regulations may require

the maximum transmit power to be reduced. To ensure that regulatory requirements
are met for connectorized installations, refer to Calculating maximum power level for

connectorized units on page 2-16.

2-2

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Re gulatory plannin g

• When installing 5.4 GHz links in the USA, it may be necessary to avoid frequencies

used by Terminal Doppler Weather Radar (TDWR) systems. For more information, refer
to Avoidance of weather radars (USA only) on page 2-5.

Available spectrum

The available spectrum for operation depends on the region. When configured with the
appropriate license key, the unit will only allow operation on those channels which are
permitted by the regulations.

In Italy, there is a regulation which requires a general authorization of any 5.4 GHz radio
link which is used outside the operator’s own premises. It is the responsibility of the
installer or operator to have the link authorized. Details may be found at:

http://www.sviluppoeconomico.gov.it/index.php?option=com_content&view=article&idme
nu=672&idarea1=593&andor=AND&idarea2=1052&id=68433§ionid=1,16&viewTy
pe=1&showMenu=1&showCat=1&idarea3=0&andorcat=AND&partebassaType=0&idar
eaCalendario1=0&MvediT=1&idarea4=0&showArchiveNewsBotton=0&directionidUser
=0

The form to be used for general authorization may be found at:

http://www.sviluppoeconomico.gov.it/images/stories/mise_extra/Allegato%20n19.doc

Certain regulations have allocated certain channels as unavailable for use:

• ETSI has allocated part of the 5.4 GHz band to weather radar.

• UK and some other European countries have allocated part of the 5.8 GHz band to

Road Transport and Traffic Telematics (RTTT) systems.

For details of these restrictions, refer to Examples of regulatory limits on page 4-31.

Where regulatory restrictions apply to certain channels, these channels are barred
automatically by the use of the correct licence key and region code. For example, at

5.8 GHz in the UK and some other European countries, the RTTT band 5795 MHz to 5815
MHz is barred. With the appropriate license key installed for this region, the PTP 500 will
not operate on channels within this band.

The number and identity of channels barred by the licence key and region code is
dependent on the channel bandwidth and channel raster selected.

Barred channels are indicated by a ‘No Entry’ symbol displayed on the Spectrum
Management web page, see Spectrum management in radar avoidance mode on page 7-29.

phn-2511_005v000 (Mar 2013)

2-3

Regulatory planning Chapter 2: Plannin g considerations

Channel bandwidth

Select the required channel bandwidth for the link. The selection depends upon the
frequency variant and region code, as specified in Examples of regulatory limits on page 4-

31.

The wider the channel bandwidth, the greater the capacity. As narrower channel
bandwidths take up less spectrum, selecting a narrow channel bandwidth may be a better
choice when operating in locations where the spectrum is very busy.

Both ends of the link must be configured to operate on the same channel bandwidth.

Frequency selection

Regions without mandatory radar detection

In regions that do not mandate DFS, choose ‘DSO’ or ‘Fixed Frequency’:

• Dynamic Spectrum Optimization (DSO): In this mode, the unit continually

continually monitors the spectrum looking for the channel with the lowest level of
interference. Statistical techniques are used to select the most appropriate transmit
and receive channels. The unit can be configured such that it operates in DSO mode,
but does not operate on selected channels. This allows a frequency plan to be

implemented in cases where multiple links are installed in close proximity.

• Fixed Frequency: In this mode, the unit must be configured with a single fixed

transmit frequency and a single fixed receive frequency. These may set to the same
value or to different values. This mode should only be considered in exceptional
circumstances, for example where it is known that are no sources of interference on
the selected channels.

Regions with mandatory radar detection

The PTP 500 fully conforms to regional regulatory requirements for radar avoidance.

In regions that mandate DFS, the unit first ensures that there is no radar activity on a
given channel for a period of 60 seconds before radiating on that channel. Once a channel
has been selected for operation, the unit will continually monitor for radar activity on the
operating channel. If detected, it will immediately cease radiating and attempt to find a
new channel.

In DFS regions, choose ‘DFS’ or ‘DFS with DSO’:

• Dynamic Frequency Selection (DFS): Once a channel is selected, the unit will only

attempt to find an alternative channel if radar activity has been detected on the
operating channel.

2-4

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Re gulatory plannin g

• DFS with DSO: In addition to switching channels on detection of radar, the unit will

also switch to a channel which has a significantly lower level of interference than the
current channel of operation. Before radiating on the newly selected channel, the unit
must again ensure that there is no radar activity on the new channel for a period of 60
seconds. This mode therefore provides the benefit of switching to a channel with lower
interference but at the expense of an an outage of approximately 60 to 120 seconds.
For this reason, the threshold for switching channels is greater than when DSO is
operating in a non-radar region.

Radar avoidance requirements in the 5.4 GHz band are defined as follows:

• For the EU: in specification EN 301-893 version V1.5.1.

• For the US: in the specification FCC part 15.407 plus the later requirements covered in

Important Regulatory Information in this User Guide.

• For Canada: in the specification RSS210 Annex 9 (Issue 7).

Radar avoidance at 5.8 GHz is applicable to EU operation (not FCC/IC) and the
requirements are defined in EN 302 502.

Avoidance of weather radars (USA only)

To comply with FCC rules (KDB 443999: Interim Plans to Approve UNII Devices Operating
in the 5470 - 5725 MHz Band with Radar Detection and DFS Capabilities), units which are
installed within 35 km (22 miles) of a Terminal Doppler Weather Radar (TDWR) system (or
have a line of sight propagation path to such a system) must be configured to avoid any
frequency within +30 MHz or –30 MHz of the frequency of the TDWR device.
requirement applies even if the master is outside the 35 km (22 miles) radius but
communicates with outdoor clients which may be within the 35 km (22 miles) radius of the
TDWRs.

The requirement for ensuring 30 MHz frequency separation is based on the best
information available to date. If interference is not eliminated, a distance limitation based
on line-of-sight from TDWR will need to be used. In addition, devices with bandwidths
greater than 20 MHz may require greater frequency separation.

When planning a link in the USA, visit http://spectrumbridge.com/udia/home.aspx
the location of the planned link and search for TDWR radars. If a TDWR system is located
within 35 km (22 miles) or has line of sight propagation to the PTP device, perform the
following tasks:

• Register the installation on http://spectrumbridge.com/udia/home.aspx.

This

, enter

• Make a list of channel center frequencies that must be barred, that is, those falling

within +30 MHz or –30 MHz of the frequency of the TDWR radars.

To comply with FCC rules, the affected channels must be barred during staging, before
the units are allowed to radiate on site, as described in Barring channels on page 6-57.

phn-2511_005v000 (Mar 2013)

2-5

Site planning Chapter 2: Planning conside r a tions

Site planning

This section describes factors to be taken into account when choosing sites for the ODU,
PIDU and PTP-SYNC unit (if installed).

ODU site selection

When selecting a site for the ODU, consider the following factors:

• Height and location to ensure that people are kept away from the antenna; see

Calculated distances and power compliance margins on page 4-28.

• Height and location to achieve the best radio path.

• Ability to meet the requirements specified in Grounding and lightning protection on

page 2-19.

• Aesthetics and planning permission issues.

• Cable lengths; see Maximum cable lengths on page 2-7.

• The effect of strong winds on the installation; see Wind loading on page 2-8.

PIDU site selection

When selecting a site for the PIDU, consider the following factors:

• Indoor location with no possibility of condensation.

• Availability of a mains electricity supply.

• Accessibility for viewing status indicators and pressing Recovery switch.

• Cable lengths; see Maximum cable lengths on page 2-7.

PTP-SYNC site selection

If PTP-SYNC is to be installed, consider the following factors when selecting a site:

• Indoor location with no possibility of condensation.

• Accessibility for viewing status indicators.

• Cable lengths; see Maximum cable lengths on page 2-7.

A rack mounting adaptor is available for the PTP-SYNC unit.

2-6

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Site planning

Maximum cable lengths

When PTP-SYNC is not installed, the maximum permitted length of the copper Ethernet
interface cable is 100 m (330 ft) from ODU to network terminating equipment.

When PTP-SYNC is installed, the maximum permitted lengths of each section of the copper
Ethernet interface cable are as specified in (Figure 18).

Figure 18 Cable length restrictions when PTP-SYNC is installed

The maximum permitted length of the GPS drop cable (GPS receiver to PTP-SYNC) is
100 m (330 ft).

phn-2511_005v000 (Mar 2013)

2-7

Site planning Chapter 2: Planning consider a tions

Wind loading

Ensure that the site will not be prone to excessive wind loading.

Antennas and equipment mounted on towers or buildings will subject the mounting
structure to significant lateral forces when there is appreciable wind. Antennas are
normally specified by the amount of force (in pounds) for specific wind strengths. The
magnitude of the force depends on both the wind strength and size of the antenna.

The ODU, with or without the integral antenna, is essentially a flat structure. The
magnitude of the lateral force can be estimated from surface area and wind speed.

Calculation of lateral force (metric)

The magnitude of the lateral force can be estimated from:

Force (in kilogrammes) = 0.1045aV2

Where:

The lateral force produced by a single PTP 500 ODU (integrated or connectorized model)
at different wind speeds is shown in Table 8.

Table 8 Lateral force – metric

Type of ODU Largest

Integrated 0.130 12 22 34 49 66

Connectorized 0.093 9 16 24 35 48

a

V

surface area
(square meters)

Is:

surface area in square meters

wind speed in meters per second

Lateral force (Kg) at win d speed
(meters per second)

30 40 50 60 70

2-8

phn-2511_005v000 (Mar 2013)

PTP 500 and PTP 300 Series User G uide Site planning

Calculation of lateral force (US)

The magnitude of the lateral force can be estimated from:

Force (in pounds) = 0.0042Av

2

Where:

The lateral force produced by a single PTP 500 ODU (integrated or connectorized model)
at different wind speeds is shown in Table 9.

Table 9 Lateral force – US

Type of ODU Largest

Integrated 1.36 36.6 57.1 82.3 146.2 228.5

Connectorized 1.00 26.9 42 60.5 107.5 168.0

When the connectorized ODU is used with external antennas, the figures from the
antenna manufacturer for lateral force should be included to calculate the total loading
on the mounting structure.

A

v

surface area
(square feet)

Is:

surface area in square feet

wind speed in miles per hour

Lateral force (lb) at wind sp eed
(miles per hour)

80 100 120 140 150

Capabilities of the PTP 500 Series

The structure and mounting brackets of the ODU are capable of withstanding wind speeds
up to 242 kph (151 mph). Ensure that the structure to which the ODU is fixed to is also
capable of withstanding the prevalent wind speeds and loads.

Wind speed statistics

Contact the national meteorological office for the country concerned to identify the likely
wind speeds prevalent at the proposed location. Use this data to estimate the total wind
loading on the support structures. Sources of information:

• US National Weather Service, http://www.nws.noaa.gov/

• UK Meteorological Office, www.meto.gov.uk

phn-2511_005v000 (Mar 2013)

2-9

Link planning Chapter 2: Plannin g considerations

Link planning

This section describes factors to be taken into account when planning links, such as range,
obstacles path loss and throughput. PTP LINKPlanner is recommended.

PTP LINKPlanner

Cambium Networks provide a free tool to help plan your PTP links. Download your copy of
LinkPlanner from the support website (see Contacting Cambium Networks on page 2).

PTP LINKPlanner imports path profiles and predicts data rates and reliability over the
path. It allows the system designer to try different antenna heights and RF power settings.
It outputs an installation report that defines the parameters to be used for configuration,
alignment and operation. The installation report can be used to compare the predicted and
actual performance of the link.

Range and obstacles

Calculate the range of the link and identify any obstacles that may affect radio
performance.

Performed a survey to identify all the obstructions (such as trees or buildings) in the path
and to assess the risk of interference. This information is necessary in order to achieve an
accurate link feasibility assessment.

The PTP 500 is designed to operate in Non-Line-of-Sight (NLoS) and Line-of-Sight (LoS)
environments. An NLOS environment is one in which there is no optical line-of-sight, that
is, there are obstructions between the antennas.

The bridge operates at ranges from 100 m (330 ft) to 250 km (155 miles). Operation of the
system will depend on obstacles in the path between the units. Operation at 40 km
(25 miles) or above requires a near line of sight path. Operation at 100m (330 ft) may 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.

2-10

phn-2511_005v000 (Mar 2013)