User's Guide
Table Of Contents
- PTP 500 Series User Guide
- Copyright Information
- Disclaimer
- Contents
- List of Figures
- List of Tables
- List of Equations
- 1 About This User Guide
- 2 Product Description
- 2.1 Product Function
- 2.2 Typical Deployment
- 2.3 Frequency Variants
- 2.4 Other Product Variants
- 2.5 Network Connection
- 2.6 Outdoor Unit (ODU)
- 2.7 PIDU Plus PTP 300/500/600 Series
- 2.8 Redundancy and Alternative Powering Configurations
- 2.9 Remote LEDs and Recovery Switch
- 2.10 Cables and Connectors
- 2.11 PTP and Lightning Protection
- 2.12 Mounting Brackets
- 3 Product Features
- 4 Planning Considerations
- 5 Lightning Protection
- 6 Installation
- 6.1 Installation Support
- 6.2 Legal Disclaimer
- 6.3 Preparation
- 6.4 Mounting the ODUs
- 6.5 Connecting Up
- 6.5.1 Preparing the PIDU Plus To ODU Cable
- 6.5.2 Making the Connections at the ODU
- 6.5.3 Making the PIDU Plus Connection At The ODU
- 6.5.4 Routing the Cable
- 6.5.5 Fitting a Lightning Protection Unit
- 6.5.6 Grounding the Installation
- 6.5.7 Making the ODU Connection at the PIDU Plus
- 6.5.8 Making the Network Connection at the PIDU Plus
- 6.5.9 Mounting the PIDU Plus
- 6.5.10 Powering Up
- 6.6 Establishing a Radio Link
- 7 Web Page Reference
- 7.1 Menu Navigation Bar
- 7.2 Home (System Summary)
- 7.3 System Status
- 7.4 System Administration
- 7.5 Configuration
- 7.6 Statistics
- 7.7 Installation Wizard
- 7.8 Software Upgrade
- 7.9 Spectrum Management
- 7.9.1 Wireless Channels
- 7.9.2 Spectrum Management Measurements
- 7.9.3 Measurement Analysis
- 7.9.4 The Spectrum Management Master / Slave Relationship
- 7.9.5 Spectrum Management Configuration
- 7.9.6 Barring Channels
- 7.9.7 Master and Slave Channel Spectrum Graphics
- 7.9.8 Active Channel History
- 7.9.9 Viewing Historic Spectrum Management Metrics
- 7.9.10 Spectrum Management (Fixed Frequency)
- 7.9.11 Spectrum Management Control with Radar Avoidance
- 7.10 Remote Management
- 7.10.1 Control Access to HTTP Interface
- 7.10.2 Control Access to Telnet Interface
- 7.10.3 SNMP (Simple Network Management Protocol)
- 7.10.4 Supported Management Information Bases (MIBS)
- 7.10.5 Diagnostics Alarms
- 7.10.6 SNMP Configuration
- 7.10.7 SMTP (Simple Mail Transport Protocol)
- 7.10.8 SNTP (Simple Network Time Protocol)
- 7.10.9 Setting the clock
- 7.11 Diagnostics Plotter
- 7.12 Change Password
- 7.13 License Key
- 7.14 Properties
- 7.15 Reboot
- 8 Recovery Mode
- 9 Troubleshooting (Fault Finding)
- 10 Connectorized PTP 500 Series Bridge
- 10.1 Product Description
- 10.2 Software/Features
- 10.3 Deployment Considerations
- 10.4 Link Budget
- 10.5 Regulatory Issues with Connectorized Units
- 10.6 Antenna Choices
- 10.7 Installation
- 10.7.1 Cables and Connectors
- 10.7.2 Tools
- 10.7.3 Miscellaneous supplies
- 10.7.4 Mounting the Connectorized PTP 500 Series Bridge
- 10.7.5 Mounting the antennas
- 10.7.6 Alignment Process
- 10.7.7 Aligning Dual Polar Antennas
- 10.7.8 Aligning Separate Antennas
- 10.7.9 Completing the Installation
- 10.7.10 Antenna Cable Fixing
- 10.7.11 Antenna Connection Weatherproofing
- 10.8 Additional Lightning Protection
- 11 E1/T1 Installation Guide
- 12 Data Rate Calculations
- 13 AES Encryption
- 14 Remote Software Upgrade by TFTP
- 15 Legal Notices
- 15.1 Motorola Inc. End User License Agreement
- 15.1.1 Definitions
- 15.1.2 Grant of License
- 15.1.3 Conditions of Use
- 15.1.4 Title; Restrictions
- 15.1.5 Confidentiality
- 15.1.6 Right to Use Motorola’s Name
- 15.1.7 Transfer
- 15.1.8 Updates
- 15.1.9 Maintenance
- 15.1.10 Disclaimer
- 15.1.11 Limitation of Liability
- 15.1.12 U.S. Government
- 15.1.13 Term of License
- 15.1.14 Governing Law
- 15.1.15 Assignment
- 15.1.16 Survival of Provisions
- 15.1.17 Entire Agreement
- 15.1.18 Third Party Software
- 15.2 Hardware Warranty in U.S.
- 15.3 Limit of Liability
- 15.1 Motorola Inc. End User License Agreement
- 16 PTP 500 Reference Information
- 16.1 PTP 500 General Reference Information
- 16.2 PTP 54500 Reference Information
- 16.2.1 PTP 54500 Examples of Regulatory Limits
- 16.2.2 PTP 54500 Licenses and Region Codes
- 16.2.3 PTP 54500 Regulatory Compliance
- 16.2.4 PTP 54500 Radio System Specifications
- 16.2.5 PTP 54500 Emissions and Radio Certifications
- 16.2.6 PTP 54500 Available Spectrum Settings
- 16.2.7 PTP 54500 System Threshold, Output Power and Link Loss
- 16.2.8 PTP 54500 FCC Antenna Restrictions
- 16.3 PTP 58500 Reference Information
- 16.3.1 PTP 58500 Examples of Regulatory Limits
- 16.3.2 PTP 58500 Licenses and Region Codes
- 16.3.3 PTP 58500 Regulatory Compliance
- 16.3.4 PTP 58500 Radio System Specifications
- 16.3.5 PTP 58500 Emissions and Radio Certifications
- 16.3.6 PTP 58500 Available Spectrum Settings
- 16.3.7 PTP 58500 System Threshold, Output Power and Link Loss
- 16.3.8 PTP 58500 FCC Antenna Restrictions
- 17 FAQs
- 18 Glossary
7 Web Page Reference
125
7.8.2 Program Software Image into Memory
The user should ensure that the correct image is shown before pressing the “Program
Software Image into Non-Volatile Memory” button. Once this button has been pressed the
image is stored into non-volatile memory, this process can take up to 60 seconds and must
not be interrupted.
CAUTION
If the upgrade process is interrupted during the erasure of the image bank, or during
the reprogramming of the image bank, the image bank will be left in a corrupt state. If
this occurs the software must be reloaded. All software images that are stored in non-
volatile memory are protected via the use of CRCs. If the software detects an invalid
CRC the image bank is marked as ‘corrupt’ and the PTP 500 Series bridge boot code
will boot the fixed software image. If this occurs the user must attempt to reload the
correct version of software.
During the write process the progress of the upgrade is displayed on the progress tracking
page (Figure 68). The upgrade process should not be interru
pted. Interruption of this process
can result in a corrupt main software image, which will result in the recovery image been
booted at the next reset cycle.
Figure 68 - Software Download Progress Indicator
7.8.3 Software Upgrade Complete
When the software image has been written to non-volatile memory, Figure 69 is displayed
showing the status of the software upload.