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 1: Product description FIPS 140-2 mode
Enforced configuration in FIPS approved mode
When the PTP 700 ODU operates in the FIPS approved mode, the following configuration
settings are automatically enforced:
• Identity-based user accounts is Enabled.
• Telnet management interface is Disabled.
• SNMP control of HTTP and Telnet is Disabled.
• SNMP control of passwords is Disabled.
• TFTP client is Disabled.
Secure mode alarm
The Secure mode alarm indicates that the unit is operating in the FIPS approved mode, but that
it has not been configured correctly for FIPS 140-2 operation. The secure mode alarm appears
in the System Summary page as shown in Figure 6.
Figure 6
Secure mode alarm in the System Summary page
The Secure mode alarm is also displayed in the first page of the Security Wizard as shown in
Figure 7.
Figure 7
Secure mode alarm in the Security Wizard
Security configuration for FIPS approved mode
The security configuration for the FIPS approved mode consists of the following:
• The HTTPS/TLS management interface must be correctly configured, including:
o Key of keys (128-bit or 256-bit to match the AES license)
o Entropy (512-bit)
o Private key (2048-bit key size)
o Public key certificate (2048-bit key size)
Page 1-54










