While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no liability
resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein.
Motorola, Inc. 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. Motorola, Inc. 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
Motorola 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 Motorola intends to announce such Motorola products,
programming, or services in your country.
Copyrights
This document, Motorola products, and 3rd Party Software products described in this document may include or
describe copyrighted Motorola and other 3
rd
Party supplied computer programs stored in semiconductor memories or
other media. Laws in the United States and other countries preserve for Motorola, its licensors, and other 3
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
Motorola, its licensors, or the 3
rd
Party software supplied material contained in the Motorola 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 Motorola. Furthermore, the purchase of Motorola 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 Motorola 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.
Restrictions
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
Motorola, Inc.
License Agreements
The software described in this document is the property of Motorola, Inc 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.
High Risk Materials
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). Motorola and its supplier(s)
specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.
Trademarks
MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service
names are the property of their respective owners.
To prevent loss of life or physical injury, observe the safety guidelines
in this section.
Power lines
Exercise extreme care when installing antennas 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
No.70-1984
These codes describe correct installation procedures for grounding the outdoor unit,
mast, lead-in wire and discharge unit, size of grounding conductors and connection
requirements for grounding electrodes. Other regulations may apply in different
countries and therefore it is recommended that installation of the outdoor unit be
contracted to a professional installer.
The supplied Power Indoor Plus (PIDU Plus PTP 300/500/600 Series) is used to power
the ODU. Failure to use the Motorola supplied PIDU could result in equipment damage
and will invalidate the safety certification and may cause a safety hazard.
Powering down before servicing
Always power down and unplug the equipment before servicing.
Cable measuring card
A cable measuring card must NEVER be used at the ODU end connected to power
from the PIDU Plus. It must only be used at the bottom of the mast with a multimeter.
This is because the PIDU Plus voltage exceeds the limit allowed in some countries for
safe handling in wet conditions and therefore may create a safety hazard.
Non-Motorola power supply
Safety may be compromised if a different power supply is used than the one supplied
by Motorola as part of the system.
Alternative DC supplies
When using alternative DC supplies (via the PIDU Plus DC in terminals), such as
battery-backed DC power source, the supply MUST comply with the following
requirements:
•The voltage and polarity is correct and is applied to the correct terminals in the
PIDU Plus.
• The power source is rated as SELV.
• The power source is rated to supply at least 1A continuously.
• The power source cannot provide more than the Energy Hazard Limit as defined
by IEC/EN/UL6090, Clause 2.5, Limited Power (The Energy Hazard Limit is
240VA).
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 weather.
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.
RF exposure near the antenna
Strong radio frequency (RF) fields will be present close to the antenna when the
transmitter is on. Always mute the transmitter 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-
This guide describes the planning, installation and operation of the Motorola PTP 600
Series of Point-to-Point Wireless Ethernet Bridges. It is intended for use by the link
planner, system installer and the end-user IT professional. The users of this guide will
require expertise in the following areas:
•Outdoor radio equipment installation
.
.
.
.
• Network configuration
• Use of web browser for system configuration, monitoring and fault finding
Motorola Point-To-Point documents are intended to instruct and assist personnel in the
operation, installation and maintenance of the Motorola Point-To-Point equipment and
ancillary devices. It is recommended that all personnel engaged in such activities be
properly trained.
Motorola 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.
The following conventions are used in the Motorola Point-To-Point documents to
represent keyboard input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and
environmental variables that appear on the screen are shown like this.
Special key sequences
Special key sequences are represented as follows:
CTRL+C
CTRL+SHIFT+C
ALT+F
ALT+SHIFT+F11
|
RETURN or
ENTER
Press the Ctrl and C keys at the same time.
Press the Ctrl, Shift, and C keys at the same
time.
Press the Alt and F keys at the same time.
Press the Alt, Shift, and F11 keys at the same
time.
Press the pipe symbol key.
Press the Return or Enter key.
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
support.ptp@motorola.com
Motorola Point-to-Point
Postal Address:
.
Motorola, Inc.,
1303 E. Algonquin Road,
Schaumburg,
Illinois 60196
U.S.A.
Web Site:
Sales Enquiries:
Web Support:
Email Support:
All Other Enquiries:
http://www.motorola.com/ptp
sales.ptp@motorola.com
http://www.motorola.com/ptp/support
support.ptp@motorola.com
info.ptp@motorola.com
Wireless Broadband Technical Support telephone numbers
Motorola’s standard hardware warranty is for one (1) year from date of shipment from
Motorola or a Motorola Point-to-Point Distributor. Motorola warrants that hardware
will conform to the relevant published specifications and will be free from material
defects in material and workmanship under normal use and service. Motorola shall
within this time, at its own option, either repair or replace the defective product within
thirty (30) days of receipt of the defective product. Repaired or replaced product will
be subject to the original warranty period but not less than thirty (30) days.
To register PTP products or activate warranties, visit
http://www.motorola.com/ptp/support
For warranty assistance, contact the reseller or distributor.
.
CAUTION
Using non-Motorola parts for repair could damage the equipment or void
warranty. Contact Motorola Warranty and Repair for service and repair
instructions.
CAUTION
Portions of Motorola equipment may be damaged from exposure to
electrostatic discharge. Use precautions to prevent damage.
Motorola systems and equipment provide security parameters that can be configured
by the operator based on their particular operating environment. Motorola
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 Motorola 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.
The following describes how warnings and cautions are used in this document and in
all documents of this Motorola 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:
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:
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:
WARNING
Warning text and consequence for not following the instructions in
the warning.
CAUTION
Caution text and consequence for not following the instructions in the
caution.
The following information describes national or regional requirements for the disposal
of Motorola 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 Motorola equipment in EU countries.
Disposal of Motorola equipment
European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment
(WEEE)
Do not dispose of Motorola equipment in landfill sites. In the EU, Motorola in
conjunction with a recycling partner ensures that equipment is collected and recycled
according to the requirements of EU environmental law.
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 Motorola Networks equipment and all surplus
packaging in accordance with national and regional regulations.
This chapter provides a high level description of the PTP 600 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:
Motorola PTP 600 Series Bridge products are designed for Ethernet bridging over
point-to-point microwave links in the licensed bands 2.5 GHz, 4.5 GHz, 4.8 GHz and
4.9 GHz, and in the unlicensed bands 5.4 GHz (ETSI Band B), 5.8 GHz (ETSI Band C
and FCC ISM band) and 5.9 GHz. Users must ensure that the PTP 600 Series complies
with local operating regulations.
The PTP 600 Series acts as a transparent bridge between two segments of the
operator’s network. In this sense, it can be treated as a virtual wired connection
between two points. The PTP 600 Series forwards 802.3 Ethernet packets destined for
the other part of the network and filters packets it does not need to forward. The
system is transparent to higher-level protocols such as VLANs and Spanning Tree.
Key features
The key features of the PTP 600 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 200km (124 miles) in near line-of-sight conditions
and up to 10km (6 miles) in deep non-line-of-sight conditions.
•Coexistence with other users of the band using a combination of Automatic
Transmit Power Control (ATPC), 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 on ultra-fast digital signal processors but 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.
The PTP 600 operates 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 PTP 600 Series 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 PTP 600 Series will detect the 802.11a radio
signals and choose a clear channel away from any interference.
Avoiding interference from nearby devices
At initialization, the PTP 600 Series monitors the available frequency channels to find
a channel that is clear of interference. In operation, the PTP 600 Series continuously
monitors the spectrum to ensure it is operating on the cleanest channel.
Typical deployment
The PTP 600 Series Bridge consists of an identical pair of units deployed one at each
end of the link. The radio link operates on a single frequency channel in each direction
using Time Division Duplex (TDD). One unit is deployed as a master and the other as a
slave. The master unit takes responsibility for controlling the link in both directions.
The PTP 600 Series Bridge is aimed at a wide range of applications. An example
application is an enterprise that has a requirement to connect together the Local Area
Network (LAN) of two or more buildings as shown in Figure 1-1.
Figure 1-1 Typical PTP 600 Series bridge deployment
Product variants
Frequency variants
The PTP 600 Series has been developed to operate within license exempt frequency
bands as well as the licensed 2.5 GHz band in the USA. The frequency variants are
listed in Table 1-1.
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 1-2) or connec
Figure 1-2 PTP 600 Series integrated ODU (front and rear views)
torized (without an antenna, Figure 1-3).
Figure 1-3 PTP 600 Series connectorized ODU (front and rear views)
The connectorized ODU is designed to provide the system integrator and installer with
the ability to provide extra capability to cope with very difficult radio links compared
to the integrated model. This allows the use of externally mounted antennas that have
higher gains than provided by the integrated antenna.
ODU interfaces
The ODU interfaces are illustrated in Figure 1-4 and described in Table 1-2.
Figure 1-4 ODU interfaces
Table 1-2 ODU interfaces
Interface Function
Ground studs For grounding the ODU to the mast or building.
E1/T1 RJ45 socket for optional E1 or T1 network connection (not
via the PIDU Plus).
SYNC RJ45 socket for optional connection to UltraSync GPS timing
reference source.
FIBER Fiber optic socket for optional network connection (not via
the PIDU Plus) using a 1000BaseSX Fiber Optic cable.
PIDU+ RJ45 socket for connecting to power supply and network via
The connectorized ODU also has interfaces to connect to an external antenna (Figure
1-5) via a 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 1-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.
The network connection to a PTP 600 Series is made via a 1000BaseT Ethernet
connection. Power is provided to the ODU over the 1000BaseT Ethernet connection
using a patented non-standard powering technique.
Very early releases of the PTP 600 Series platform used different powering and
connection arrangements. Users of equipment prior to Mod Record 1 should refer to
the User Guide shipped with the original equipment. The Mod Record label can be
found on the back of the ODU as shown in Figure 1-6.
Figu
re 1-6 Mod record
label
Fiber optic connection
Alternatively, the network connection to a PTP 600 Series can be made using a
1000BaseSX Fiber Optic cable connected directly to the ODU. In this case power is
still provided over the 1000BaseT Ethernet connection. In the case of Fiber Optic cable
failure the PTP 600 Series will automatically fall back to the copper Ethernet
connection (provided the cable length <=100m [330 ft]). PTP 600 Series Optical
Interface Upgrade Kits can be obtained from your distributor, reseller or system
integrator.
1-10
phn-0896_012v000
Jul 2010
Page 53
User Guide: PTP 600 Series Powered indoor unit (PIDU Plus)
The PIDU Plus 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 Plus is connected to the ODU and network equipment using CAT5e cable
with RJ45 connectors. Refer to Cabling and lightning protection on page 1-16.
The ODU for the PTP 6
PTP 300/500/600 Series.
CAUTION
Care should be taken not to connect equipment other than an ODU, LPU or
PTP-SYNC for the PTP 600 Series to a PIDU Plus ODU port, as equipment
damage may occur. The PIDU Plus PTP 300/500/600 Series is not
interchangeable with the PIDU Plus PTP 400 Series.
PIDU Plus interfaces
The PIDU Plus interfaces are illustrated in Figure 1-7 and described in Table 1-3 and
Table 1-4.
Figure 1-7 PIDU Plus i
00 Series should only be deployed using the supplied PIDU Plus
nterfaces
phn-0896_012v000
Jul 2010
1-11
Page 54
Powered indoor unit (PIDU Plus) Chapter 1 Product description
The PIDU Plus provides a facility to connect remote LEDs and Recovery switch
allowing the PIDU Plus to be mounted inside an enclosure. At the left hand end of the
PIDU Plus under the ODU connection cover can be found a PCB header and three
jumpers. Jumpers J906 and J907 should be removed and connection to the remote
LEDs and Recovery switch made to J908 as shown in Figure 1-13.
Figu
re 1-13 Remote LED and
recovery switch wiring
PIDU Plus maximum cable lengths
The maximum distance from the ODU to the connected network equipment is 100m
(330 ft) when using Ethernet over copper. Powering distances over 100m (330 ft) are
only applicable when using a Fiber Optic connection. The maximum power distance is
230m.
phn-0896_012v000
Jul 2010
1-15
Page 58
Cabling and lightning protection Chapter 1 Product description
The cabling and lightning protection components of a PTP 600 installation are:
• Outdoor drop cable
• Indoor CAT5e cable
• Grounding cables
• Lightning protection units
PTP and lightning protection
The PIDU Plus meets the low level static discharge specifications identified in EMC
immunity compliance on page 4-90 but does not
suppression.
provide lightning or surge
The amount of lightning protection is dependent on regulatory requirements and the
end user requirements. The standard ODU for the PTP 600 Series 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.
CAUTION
The PTP 600 Series is not designed to survive direct lightning strikes. For
this reason the unit should not be installed as the highest point in a localized
area, unless specific precautions are taken. See Grounding and lightning
prot
ection on page 2-14.
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, LPUs (if installed),
GPS receiver (if installed) and the ODU port of the PIDU Plus.
CAUTION
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. See Cable and connector specifications on
pag
e 4-16.
1-16
phn-0896_012v000
Jul 2010
Page 59
User Guide: PTP 600 Series Cabling and lightning protection
The CAT5e cable that connects the PIDU Plus to the network equipment must meet the
screening requirements specified in Cable and connector specifications on page 4-16.
CAUTION
The connected network equipment must feature screened RJ45
connectors and must be connected to ground, otherwise the PIDU Plus will
not be grounded.
NOTE
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-14. One cable grounding kit (Figure 1-14
drop cable grounding point.
Figure 1-14 Cable grounding kit for 1/4” and 3/8” cable
) is required for each
phn-0896_012v000
Jul 2010
1-17
Page 60
Cabling and lightning protection Chapter 1 Product description
Separate Ethernet surge suppressors (lightning protection units) must be installed and
grounded. Lightning protection units can be sourced from Motorola Point-to-Point
distributors or solutions providers.
LPU double end kit
The LPU double end kit (Figure 1-15) is required for ODU drop cables. One LPU is
installed next to the ODU and the other is installed near the building entry point.
Figure 1-15 LPU double end kit
1-18
phn-0896_012v000
Jul 2010
Page 61
User Guide: PTP 600 Series Cabling and lightning protection
The LPU single end kit (Figure 1-16) is required for GPS drop cables, when GPS is the
timing reference source for PTP-SYNC (optional). The LPU is installed near the
building entry point.
The PTP-SYNC unit (Figure 1-17) 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
The PTP-SY
optional rack mounting adaptor) in a standard 19 inch rack. It is powered using
standard PTP 600 power-over-Ethernet from the PIDU Plus. One PTP-SYNC unit is
required for each synchronized link.
Figure 1-17 PTP-SYNC kit
NC is a compact indoor unit mounted on a wall or a shelf or (using an
PTP 600 series links operate using Time Division Duplexing (TDD). PTP 600 uses a
TDD cycle in which the ODUs alternately transmit and receive TDD bursts. The TDD
cycle is illustrated in Figure 1-19. The steps in the cycle are
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.
as follows:
4. A delay occurs as 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.
The propagation delay in Step 2 is necessarily equal to the propagation delay in Step
6, and is determined solely by the link range. The delay at Step 4 is fixed, except
where the link is operated with TDD synchronisation.
The PTP 600 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.
Link mode optimization allows the PTP 600 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
25).
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.
page 1-
Link symmetry
The PTP 600 series provides four configuration options for apportioning the available
capacity between the two link directions.
•Symmetric: The Master and Slave have equal capacity. The PTP 600 series
achieves this by allocating an equal Burst Duration for the Master and the Slave.
•2:1 The capacity in the direction Master to Slave is twice that of the direction
Slave to Master. The PTP 600 series achieves this by setting the Burst Duration
of the Master to twice that of the Slave. This mode is not available when TDD
synchronization is enabled.
•1:2 The capacity in the direction Slave to Master is twice that of the direction
Master to Slave. The PTP 600 series achieves this by setting the Burst Duration
of the Slave to twice that of the Master.
NOTE
This mode is not available when TDD synchronization is enabled.
•Adaptive: The capacity allocated to a given link direction is dependant 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 PTP 600 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 PTP 600 series 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.
NOTE
This mode is not available in the following configurations :
o When link mode optimization is set to TDM Traffic see Link mode
o When T
o In regions where radar avoidance is operational (see Radar avoidance on
optimizati
DD synchronizatio
pag
e 1-30).
on on page 1-25).
OFDM and channel bandwidth
The PTP 600 series 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
over a Non-Line-of-Sight (NLoS) channel.
The channel bandwidth of the OFDM signal is configurable to one of five values: 5
MHz, 10 MHz, 15 MHz, 20 MHz and 30 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.
n is enabled.
Each channel is offset in center frequency from its neighboring channel by 10 MHz or
6 MHz.
NOTE
1-26
The Channel Bandwidth must be configured to the same value at both ends
of the link.
Not all channel bandwidths are available in all regions or all frequency
variants.
The spectrum management feature of the PTP 600 Series 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.
Spectrum management measurements
The PTP 600 Series performs two mean signal measurements per TDD cycle, per
channel. This mean measurement represents the mean received signal power for the
40 microseconds measurement period.
The Spectrum Management algorithm collects measurements equally from all
channels. This process is called the Channel Availability Check (hereafter referred to
by the acronym CAC). The CAC uses a round-robin channel selection process to collect
an equal amount of measurements from each channel. 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 pa
27.
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.
The transmit and receive frequencies can be fixed in a PTP 600 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 adjacentchannel 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
also be taken to ens
compatible.
ure that the frequency allocations at each end of the link are
6-54). Care must
Adaptive modulation
The PTP 600 series can transport data over the wireless link using a number of
different modulation modes ranging from 256QAM 0.81 to BPSK 0.63. 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 256QAM 0.81 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 PTP 600 series 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
PTP 600 to operate in challenging none line of sight radio channels.
Specifications of capacity for all channel bandwidths, modulation modes and
configurations are provided in Data throughput capacity on
Specificati
interference) are provided in the various system threshold tables in Chapter 4
Reference information.
NOTE
ons of receive level thresholds for each modulation mode (assuming no
Link Planner should be used to estimate the performance of a given link.
Link Planner includes an estimate of mean data rate, the data rate provided
by each modulation and the percentage of time spent in each modulation
mode.
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 600 transmits two signals on the same radio frequency, one of which is
vertically polarized and the other horizontally polarized. The PTP 600 also has the
ability to adapt between two modes of operation:
•Dual Payload: When the radio channel conditions allow, the PTP 600 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 PTP 600.
•Single Payload: As the radio channel becomes more challenging, the PTP 600
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 PTP 600 to operate in challenging nonline 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.63 up to QPSK 0.87) are only available
as single payload modes. Each of the higher order modulations (16QAM 0.63 to
256QAM 0.81) 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-28.
Intelligent dynamic frequency selection
The PTP 600 series uses an interference mitigation technique known as Intelligent
Dynamic Frequency Selection (i-DFS). Both the PTP 600 Master and PTP 600 Slave
continually monitor for interference on all channels and then select the best frequency
of operation. This is a dynamic process where the PTP 600 can continually move
channels in response to changes in interference. Two modes of operation are available,
one where the two link directions are forced to select the same frequency. This is
determined by the Master. The second mode is where the frequency of operation can
be determined independently for each direction. This is a key feature which enables
the PTP 600 to operate successfully in areas where other radio equipments are
operating within the same band. i-DFS is not available in the 2.5 GHz band.
Radar avoidance requires that equipment used in the region:
•Detects interference from other systems and avoids co-channel operation with
these systems, notably radar systems.
•Provides a uniform loading of the spectrum across all devices, that is, fixed
frequency operation is not allowed.
To address the primary aims, the spectrum management algorithm implements a
radar detection function which looks for impulsive interference on the operating
channel only. If impulsive interference is detected, spectrum management will mark
the current operating channel as having detected radar (unavailable channel) and
initiate a channel hop to an available channel. The previous operating channel will
remain in the unavailable state for thirty minutes after the last impulsive interference
pulse was detected. After the thirty minutes have expired the channel will be returned
to the usable channel pool.
The equipment can only transmit on available channels, of which there are none at
initial power up. The radar detection algorithm will always scan a usable channel for
60 seconds for radar interference before making the channel an available channel.
This compulsory channel scan will mean that there is 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.
NOTE
On system installation or start-up, this extends the initial scan time of the
Master unit by 60 seconds. To address the requirement to provide aggregate
uniform loading of the spectrum across all devices, the channel selection
algorithm will choose a channel at random from a list of useable channels.
The channel selection algorithm is initiated at link initialization and when
radar interference is detected.
The Motorola PTP 600 Series 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 600 is approved to FIPS-197.
Encryption is enabled through the purchase of an upgrade. Refer to Remote software
upgrade by
TFTP on page 7-38.
Region codes
Some aspects of wireless operation are controlled, enforced or restricted according to
a Region Code. PTP 600 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
• Transmit power reduction in edge channels
• Frequency range
• Channel plan
A Region Code is encoded in the PTP 600 license key. The Region Code can be
changed by generating and entering a new license key. Refer to Remote software
upgrade by
NOTE
CAUTION
TFTP on page 7-38.
Some units are supplied with two alternative license keys for different
Region Codes, one of which is factory configured.
Always operate PTP 600 links in accordance with local regulations.
The Intelligent Dynamic Frequency Selection (i-DFS) feature allows a PTP 600 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
cont
act your Motor
Synchronized networks
TDD synchronization can be used to relax constraints on the frequency planning of
PTP 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.
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
Additional hardware
Additional hardware is needed to synchronize PTP 600 links. Two alternative
approaches are supported:
•MemoryLink UltraSync GPS receiver: This unit contains a GPS receiver
producing a 1 Hz timing reference locked to the GPS network. The UltraSync
unit is connected directly to the Sync input at the master ODU. One UltraSync
unit is required for each synchronized link.
•PTP-SYNC: This option is the preferred solution. 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 Plus and the ODU, and is collocated with the PIDU Plus. The
PTP-SYNC requires an external 1 Hz timing reference.
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 PTP 600 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 PTP 600 unit 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.
The PTP Link Planner provides a capability for computing suitable frame parameters
in a synchronized network. Please refer to the
on configuring TDD synchronization.
Link symmetry is always 1:1 in synchronized networks.
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.
The PTP 600 Series 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, 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 in the
customer network is 2000 octets.
Layer two control protocols
The PTP 600 Series 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 PTP 600 Series does not generate or respond to any L2CP traffic.
The PTP 600 Series 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.
PTP 600 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 600 Series 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 600 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.1 in the master ODU and 169.254.1.2 in the
slave ODU. The PTP 600 does 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.
The management agent can be configured to transmit and receive either untagged,
priority-tagged, C-tagged (IEEE 802.1Q) or S-tagged (IEEE 801.ad) 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.
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 ODU 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.
In-band local management
In the in-band local management mode, the management agent can be reached from
the Ethernet port at the local ODU, but not from 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 ODU MAC address, and (b)
the VLAN ID in the frame matches the VLAN configuration of the management agent.
All Ethernet frames in the management VLAN (regardless of destination address) are
filtered (discarded) at the wireless port.
In-band local management mode is useful in networks that require only local access
for network management. For correct operation of in-band local management mode,
ensure that the same management VLAN ID is configured at both ends of the link.
If Local Packet Filtering is enabled, the PTP 600 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 600 Series provides an optional indication of failure of the wireless link by
means of a brief disconnection of the Copper data port or the Fiber 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 600 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.
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 circuitmode link layer between ends of the PTP 600 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 1-20. Pro
and the management agent are shown in Figure 1-21. In these f
the meanings defined in IEEE 802.1Q-2005.
tocol
layers involved in bridging between external interfaces
The PTP 600 link provides native support for one or two E1 links, or one or two T1
links. 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 carries 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 Link Planner 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 Link Planner.
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 the PTP 600 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 i-DFS. 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.
Fixed frequency operation is not available when radar detection requirements exist in
the frequency band.
PTP 600 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 600 management agent contains a web server. The web server supports the
HTTP and HTTPS/TLS interfaces.
Operation of HTTPS/TLS is enabled by purchase of an optional AES upgrade as
described in Task 2: Install license keys on page 6-12.
Web-based management offers a convenient way t
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 installation of
PTP 600, and for the majority of PTP 600 configuration management tasks.
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 PTP 600.
• 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
PTP 600 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, and
to operate the PTP 600 unit in FIPS 140-2 operational mode. 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 600
uses AES encryption for HTTPS/TLS. Operation of HTTPS/TLS is enabled by purchase
of an optional AES upgrade as described in Task 2: Install license keys on page 6-12.
HTTPS
common name of the subject in the public key certificate is the IP address or host
name of the PTP 600 unit.
HTTPS/TLS operation is configured through the web-based interfaces using the
Security Wizard.
/TLS require
s installation of a private key and a public key certificate where the
Details of the security material needed for HTTPS/TLS are provided in Security
The PTP 600 has no default public key certificate, and Motorola is not able
to generate private keys or public key certificates for specific network
applications.
User account management
PTP 600 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
user accounts on page 6-36 for fu
Identity-based user accounts
The PTP 600 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.
•Identify-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:
rther details.
• Security officer.
• System administrator.
• Read only.
Identity-based user accounts are enabled in the Local User Accounts page of the webbased interface.
Password complexity
PTP 600 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 user accounts on page 6-36 for
further details.
PTP 600 supports remote authentication for users of the web interface using the
Challenge-Handshake Authentication Protocol (CHAP) over the Remote Authentication
Dial In User Service (RADIUS). PTP 600 supports connections to primary and
secondary RADIUS servers. The RADIUS interface is configured through the RADIUS
Authentication page of the web-based interfaces.
PTP 600 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 authentication are used
together, PTP 600 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.
SNMP
RADIUS is only available when PTP 600 is configured for Identity-based User
Accounts. For more information, refer to RADIUS protocols and attributes on page 4-
79.
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.
PTP 600 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 600 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 PTP 600 AES upgrade described in AES license on
pag
e 1-52. The ODU will allo
protocol, regar
protocol will not be able to transmit and receive encrypted messages unless the
license key enables the AES capability.
dless of license key. However, a user configured to use AES privacy
w the creation of users configured with AES privacy
View-based access control model
PTP 600 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.
The SNMPv3 management interface does not provide access to critical security
parameters (CSPs) of PTP 600. It is not possible to read or modify AES keys used to
encrypt data transmitted at the wireless interface. Neither is it possible to read or
modify security parameters associated with TLS protection of the web-based
management interface. The recovery mode option to zeroize CSPs does not affect
SNMPv3 configuration.
MIB-based management of SNMPv3 security
PTP 600 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.
PTP 600 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 p
age 4-77.
PTP 600 creates the initial user and template
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.
initialis created with a view of the entire MIB, requiring
authentication for SET operations. There is no access for template users.
NOTE
VACM grants access for requests sent with more than the configured
security level.
The default user
initialwill 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
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
initialmay then be deleted to prevent
access using the well-known user name and keys. Alternatively, the keys associated
with
initialmay be set to some new secret value.
Web-based management of SNMPv3 security
PTP 600 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.
initial
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 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.
•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 PTP 600 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.
PTP 600 supports the standard syslog protocol to log important events. The protocol
complies with RFC 3164.
PTP 600 reports syslog event notification messages in the following families:
• Local log
• Standard events
• SNMPv3
• Authentication
• Authentication configuration
• Telnet
• TFTP
• RADIUS
• Security configuration
• License key
• System
• Time
• Low resource
The individual event notification messages are listed in Event notification messages on
page 4-82.
PTP 600 can be configured to send event notificati
syslog servers.
Additionally, PTP 600 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.
PTP 600 provides optional encryption using the Advanced Encryption Standard (AES).
Encryption is not available in the standard PTP 600 system.
AES upgrades are supplied as an access key purchased from your Motorola Point-toPoint 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
http://www.motorola.com/ptp/support
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 PTP 600 wireless port is based on pre-shared keys. An identical
key must be entered at each end of the link.
AES encryption for SNMPv3 or TLS is always based on a 128-bit key, regardless of
level enabled in the PTP 600 license key.
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.
Capacity upgrades
Capacity upgrades are supplied as an access key purchased from your Motorola Pointto-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
http://www.motorola.com/ptp/support
The License Key Generator creates a new license key delivered by email. The license
key must be installed on the ODU as described in reference to Task 2: Install license
The management agent supports application software upgrade using either the webbased interface or the SNMP interface.
PTP 600 software images are digitally signed, and the ODU will accept only images
that contain a valid Motorola PTP digital signature. The ODU always requires a reboot
to complete a software upgrade.
NOTE
NOTE
The management process for software upgrade is described in detail in Task 3:
Upg
rade software versi
Software can be downg
page 1-54.
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 Motorola.
Recovery mode
The PTP 600 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.
on on page 6-16.
raded using Recovery mode as described in Recovery mode on
The ODU operates in recovery mode in the following circumstances:
• When a checksum error occurs for the main application software image.
• When the PIDU Plus recovery button is pressed at the same time as the ODU is
• Reset all configuration data to factory default. This option resets IP and Ethernet
configuration, and erases (zeroizes) critical security parameters.
• Reset IP and Ethernet configuration to factory default.
• Erase (zeroize) critical security parameters.
• Reboot with existing software and configuration.
NOTE
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
pag
e 8-21.
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.
PTP 600 provides an optional secure cryptographic mode of operation validated to
Level 2 of Federal Information Processing Standards Publication 140-2.
FIPS 140-2 capability
A PTP 600 unit is capable of operating in the FIPS 140-2 mode when all of the
following are true:
•The hardware security of the ODU is compatible with operation in the FIPS 140-2
mode.
• The ODU license key has AES encryption enabled.
• The ODU license key has FIPS operation enabled.
• The ODU software image is validated for FIPS operation.
Hardware security
The ODU has compatible hardware security if the part number suffix on the external
packaging is no earlier than the minimum listed in Table 1-7.
Table 1-7 Minimum part number suffix for FIPS 140-2
Frequency variant Part number suffix
PTP 25600 BB
PTP 45600 BB
PTP 48600 AA
PTP 49600 AA
PTP 54600 EE
PTP 58600 DD
PTP 59600 BB
The ODU will also have compatible hardware security if the part number suffix is
earlier and PTP 600 Hardware Security Upgrade has been applied. The Hardware
Security Upgrade Kit is available as Motorola part number WB3593AA.
mode
Units with compatible hardware security have tamper-evident labels fitted as shown in
Figure 1-22 Tamper evident label on side edge of ODU
Figure 1-23 Tamper evident label on top edge of ODU
The ODU will have hardware security compatible with FIPS 140-2 if the hardware
version displayed on the Status page contains the string ‘FPS’, as shown in Figure
1-24. Th
already been deployed, and is in a physical location that makes it difficult to observe
tamper-evident labels.
Figure 1-24 FIPS 140-2 hardware version identification
phn-0896_012v000
Jul 2010
is provid
es an alternative means of checking hardware where the ODU has
FIPS validated software images are indicated by a FIPS- prefix to the file name, for
example:
image are identical to those of the standard image with the same version number. For
example,
ability of the FIPS image to operate in FIPS mode.
FIPS-PTP600-09-01.DLD2. The general features of a FIPS validated software
FIPS-PTP600-09-01.DLD2 is equivalent to PTP600-09-01.DLD2 apart from the
Indication of FIPS 140-2 capability
The FIPS 140-2 capability is indicated by a distinctive symbol displayed at the top of
the navigation bar in the web-based interface, as shown in Figure 1-25.
Figure 1-25 Indicat
FIPS 140-2 mode
PTP 600 operates in the FIPS 140-2 mode when all of the following are true:
• The PTP 600 is FIPS 140-2 capable.
• The HTTPS/TLS management interface is enabled.
• The HTTP management interface is disabled.
ion of FIPS 140-2 capability
• The Telnet management interface is disabled.
• SNMP control of HTTP and Telnet is disabled.
• AES encryption is enabled at the wireless interface.
• The HTTPS/TLS management interface is configured for identity-based user
accounts.
•RADIUS authentication of web-based users is disabled.
1-58
phn-0896_012v000
Jul 2010
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.