User's Guide Part 1
Table Of Contents
- Cambium PTP 700 Series User Guide
- Contents
- About This User Guide
- Contacting Cambium Networks
- Purpose
- Cross references
- Feedback
- Important regulatory information
- Radar avoidance
- USA and Canada specific information
- Renseignements specifiques aux USA et au Canada
- EU Declaration of Conformity
- Application firmware
- Specific expertise and training for professional installers
- Avoidance of weather radars
- External antennas
- Antennas externes
- Ethernet networking skills
- Lightning protection
- Training
- Problems and warranty
- Security advice
- Warnings, cautions, and notes
- Caring for the environment
- Chapter 1: Product description
- Overview of the PTP 700 Series
- Wireless operation
- Ethernet bridging
- TDM bridging
- System management
- FIPS 140-2 mode
- Chapter 2: System hardware
- Outdoor unit (ODU)
- Power supply units (PSU)
- Antennas and antenna cabling
- Ethernet cabling
- PTP-SYNC unit
- GPS receiver
- Network indoor unit (NIDU)
- Chapter 3: System planning
- Typical deployment
- Site planning
- Grounding and lightning protection
- Lightning protection zones
- Site grounding system
- ODU and external antenna location
- ODU ambient temperature limits
- ODU wind loading
- Hazardous locations
- PSU DC power supply
- PSU location
- PTP-SYNC location
- GPS receiver location
- NIDU location
- Drop cable grounding points
- LPU location
- Multiple LPUs
- Radio spectrum planning
- Link planning
- Planning for connectorized units
- Configuration options for TDD synchronization
- Data network planning
- TDM network planning
- Network management planning
- Security planning
- System threshold, output power and link loss
- Data throughput capacity tables
- Chapter 4: Legal and regulatory information
- Cambium Networks end user license agreement
- Definitions
- Acceptance of this agreement
- Grant of license
- Conditions of use
- Title and restrictions
- Confidentiality
- Right to use Cambium’s name
- Transfer
- Updates
- Maintenance
- Disclaimer
- Limitation of liability
- U.S. government
- Term of license
- Governing law
- Assignment
- Survival of provisions
- Entire agreement
- Third party software
- Compliance with safety standards
- Compliance with radio regulations
- Type approvals
- FCC/IC compliance
- FCC product labels
- Industry Canada product labels
- 4.9 GHz FCC and IC notification
- Utilisation de la bande 4.9 GHz FCC et IC
- 5.1 GHz FCC notification
- 5.2 GHz and 5.4 GHz FCC and IC notification
- Utilisation de la bande 5.4 GHz FCC et IC
- 5.8 GHz FCC notification
- 5.8 GHz IC notification
- 5.1 GHz band edge channel power reduction
- 5.2 GHz band edge channel power reduction
- 5.4 GHz band edge channel power reduction
- Réduction de puissance aux bords de la bande 5.4 GHz
- 5.8 GHz band edge channel power reduction
- Réduction de puissance aux bords de la bande 5.8 GHz
- Selection of antennas
- European Union compliance
- Cambium Networks end user license agreement
Chapter 3: System planning Security planning
Security planning
This section describes how to plan for PTP 700 links to operate in secure mode.
Planning for SNTP operation
Note
PTP 700 does not have a battery-powered clock, so the set time is lost each time the
ODU is powered down. To avoid the need to manually set the time after each reboot,
use SNTP server synchronization.
Before starting to configure Simple Network Time Protocol (SNTP):
• Identify the time zone and daylight saving requirements that apply to the system.
• If SNTP server synchronization is required, identify the details of one or two SNTP servers:
IP address, port number and server key.
• Decide whether or not to authenticate received NTP messages using an MD5 signature.
Planning for HTTPS/TLS operation
Before starting to configure HTTPS/TLS operation, ensure that the cryptographic material listed
in Table 59 is available.
Table 59
HTTPS/TLS security material
Item
Description
Quantity required
Key of Keys An encryption key generated using a
cryptographic key generator. The key length is
dictated by the installed license key. License keys
with AES-128 will require a key of keys of 128-
bits. License keys with AES-256 will require a key
of keys of 256-bits. The key output should be in
ASCII hexadecimal characters.
Two per link. For greater
security, each link end
should be allocated a
unique Key of Keys.
Page 3-51