FCC ID: QWP-50450M 5GHz Point to MultiPoint Multi User MIMO Access Point

 

Cambium 450 Platform User Guide System Release 15.0 33F pass Accuracy While reasonable efforts have been made to assure the accuracy of this document, Cambium Networks assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein. Cambium reserves the right to make changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Cambium does not assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey license under its patent rights or the rights of others. It is possible that this publication may contain references to, or information about Cambium products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that Cambium intends to announce such Cambium products, programming, or services in your country. Copyrights This document, Cambium products, and 3rd Party software products described in this document may include or describe copyrighted Cambium and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Cambium, its licensors, and other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any copyrighted material of Cambium, its licensors, or the 3rd Party software supplied material contained in the Cambium products described in this document may not be copied, reproduced, reverse engineered, distributed, merged or modified in any manner without the express written permission of Cambium. Furthermore, the purchase of Cambium products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Cambium or other 3rd Party supplied software, except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a product. 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 Cambium. License Agreements The software described in this document is the property of Cambium and its licensors. It is furnished by express license agreement only and may be used only in accordance with the terms of such an agreement. High Risk Materials Cambium and its supplier(s) specifically disclaim any express or implied warranty of fitness for any high risk activities or uses of its products including, but not limited to, the operation of nuclear facilities, aircraft navigation or aircraft communication systems, air traffic control, life support, or weapons systems (High Risk Use). Any High Risk Use is unauthorized, is made at your own risk and you shall be responsible for any and all losses, damage or claims arising out of any High Risk Use. 2016 Cambium Networks Limited. All Rights Reserved. pmp-0957_006v002 (August 2016) Contents About This User Guide .......................................................................................................................... 1 Contacting Cambium Networks .................................................................................................... 1 Purpose ........................................................................................................................................... 2 Cross references ............................................................................................................................. 2 Feedback ......................................................................................................................................... 2 Important regulatory information........................................................................................................ 3 Application firmware ..................................................................................................................... 3 USA specific information............................................................................................................... 3 Canada specific information ......................................................................................................... 4 Renseignements specifiques au Canada ..................................................................................... 5 EU Declaration of Conformity ....................................................................................................... 6 Specific expertise and training for professional installers ......................................................... 6 Ethernet networking skills ............................................................................................................. 6 Lightning protection ....................................................................................................................... 7 Training ........................................................................................................................................... 7 Problems and warranty ........................................................................................................................ 8 Reporting problems ....................................................................................................................... 8 Repair and service .......................................................................................................................... 8 Hardware warranty ........................................................................................................................ 8 Security advice ...................................................................................................................................... 9 Warnings, cautions, and notes .......................................................................................................... 10 Warnings ....................................................................................................................................... 10 Cautions ........................................................................................................................................ 10 Notes ............................................................................................................................................. 10 Caring for the environment ................................................................................................................ 11 In EU countries ............................................................................................................................. 11 In non-EU countries ..................................................................................................................... 11 Chapter 1: Product description ....................................................................................................... 1-1 Overview of the PMP/PTP 450 platform ........................................................................................... 1-2 Purpose ........................................................................................................................................ 1-2 PMP 450m Series ........................................................................................................................ 1-2 PMP/PTP 450i Series ................................................................................................................... 1-4 PMP/PTP 450 Series .................................................................................................................... 1-7 Supported interoperability for 450m/450i/450/430 platforms ............................................... 1-10 Typical deployment ................................................................................................................... 1-11 Product variants ........................................................................................................................ 1-13 Wireless operation ........................................................................................................................... 1-14 Page i Contents Time division duplexing ........................................................................................................... 1-14 MIMO .......................................................................................................................................... 1-17 Encryption .................................................................................................................................. 1-17 System management ....................................................................................................................... 1-18 Management agent ................................................................................................................... 1-18 Web server ................................................................................................................................. 1-18 Remote Authentication Dial-in User Service (RADIUS) ......................................................... 1-20 SNMP.......................................................................................................................................... 1-20 Network Time Protocol (NTP) .................................................................................................. 1-20 Wireless Manager (WM) ........................................................................................................... 1-21 Radio recovery mode ................................................................................................................ 1-22 Chapter 2: System hardware .......................................................................................................... 2-1 System Components ......................................................................................................................... 2-2 Point-to-Multipoint (PMP) ........................................................................................................... 2-2 Backhaul (PTP) ............................................................................................................................. 2-5 PMP/PTP 450 platform interfaces .............................................................................................. 2-7 Diagnostic LEDs ......................................................................................................................... 2-12 Power supply options ............................................................................................................... 2-15 ODU mounting brackets & accessories ................................................................................... 2-21 Lightning protection .................................................................................................................. 2-21 Cabling and lightning protection .................................................................................................... 2-22 ODU interfaces PMP 450m AP .............................................................................................. 2-22 ODU interfaces PMP/PTP 450i ............................................................................................... 2-23 Ethernet standards and cable lengths ..................................................................................... 2-24 Outdoor copper Cat5e Ethernet cable ..................................................................................... 2-26 Main Ethernet port .................................................................................................................... 2-27 Aux port ..................................................................................................................................... 2-27 Cable grounding kit ................................................................................................................... 2-29 Lightning protection unit (LPU) and grounding kit ................................................................ 2-29 Antennas and antenna cabling ....................................................................................................... 2-31 Antenna requirements .............................................................................................................. 2-31 Supported external AP antennas ............................................................................................. 2-31 Supported external BH/SM antenna ........................................................................................ 2-31 RF cable and connectors........................................................................................................... 2-32 Antenna accessories ................................................................................................................. 2-32 RJ45 connectors and spare glands .......................................................................................... 2-32 GPS synchronization ........................................................................................................................ 2-34 GPS synchronization description ............................................................................................. 2-34 Universal GPS (uGPS) .............................................................................................................. 2-34 CMM5 ......................................................................................................................................... 2-34 CMM4 (Rack Mount) ................................................................................................................ 2-35 CMM4 (Cabinet with switch) .................................................................................................. 2-38 CMM4 (Cabinet without switch) ............................................................................................ 2-38 Page ii Contents CMM3/CMMmicro ..................................................................................................................... 2-38 Installing a GPS receiver ................................................................................................................. 2-40 GPS receiver location................................................................................................................ 2-40 Mounting the GPS receiver ...................................................................................................... 2-41 Cabling the GPS Antenna ......................................................................................................... 2-42 Installing and connecting the GPS LPU .................................................................................. 2-42 Ordering the components ............................................................................................................... 2-43 Chapter 3: System planning ........................................................................................................... 3-1 Typical deployment ........................................................................................................................... 3-2 ODU with PoE interface to PSU ................................................................................................. 3-2 Site planning....................................................................................................................................... 3-7 Site selection for PMP/PTP radios ............................................................................................. 3-7 Calculated distances and power compliance margin .............................................................. 3-7 Power supply site selection ........................................................................................................ 3-8 Maximum cable lengths ............................................................................................................. 3-8 Grounding and lightning protection .......................................................................................... 3-8 ODU and external antenna location ........................................................................................ 3-10 ODU ambient temperature limits ............................................................................................ 3-10 ODU wind loading ..................................................................................................................... 3-11 Drop cable grounding points ................................................................................................... 3-14 Lightning Protection Unit(LPU) location ................................................................................. 3-15 Radio Frequency planning .............................................................................................................. 3-16 Regulatory limits ....................................................................................................................... 3-16 Conforming to the limits........................................................................................................... 3-16 Available spectrum ................................................................................................................... 3-16 Analyzing the RF Environment ................................................................................................ 3-17 Channel bandwidth ................................................................................................................... 3-17 Anticipating Reflection of Radio Waves .................................................................................. 3-17 Obstructions in the Fresnel Zone ............................................................................................. 3-18 Planning for co-location............................................................................................................ 3-18 Multiple OFDM Access Point Clusters ..................................................................................... 3-18 Link planning .................................................................................................................................... 3-21 Range and obstacles ................................................................................................................. 3-21 Path loss ..................................................................................................................................... 3-21 Calculating Link Loss ................................................................................................................ 3-22 Calculating Rx Signal Level ...................................................................................................... 3-22 Calculating Fade Margin ........................................................................................................... 3-23 Adaptive modulation ................................................................................................................ 3-23 Planning for connectorized units .................................................................................................... 3-24 When to install connectorized units ........................................................................................ 3-24 Choosing external antennas .................................................................................................... 3-24 Calculating RF cable length (5.8 GHz FCC only) ..................................................................... 3-24 Data network planning .................................................................................................................... 3-26 Page iii Contents Understanding addresses......................................................................................................... 3-26 Dynamic or static addressing ................................................................................................... 3-26 DNS Client .................................................................................................................................. 3-27 Network Address Translation (NAT) ....................................................................................... 3-27 Developing an IP addressing scheme ..................................................................................... 3-28 Address Resolution Protocol .................................................................................................... 3-28 Allocating subnets ..................................................................................................................... 3-29 Selecting non-routable IP addresses ....................................................................................... 3-29 Translation bridging .................................................................................................................. 3-30 Engineering VLANs ................................................................................................................... 3-30 Network management planning ..................................................................................................... 3-34 Planning for SNMP operation .................................................................................................. 3-34 Enabling SNMP ......................................................................................................................... 3-34 Security planning ............................................................................................................................. 3-35 Isolating AP/BHM from the Internet ........................................................................................ 3-35 Encrypting radio transmissions ............................................................................................... 3-35 Planning for HTTPS operation ................................................................................................. 3-36 Planning for SNMPv3 operation .............................................................................................. 3-36 Managing module access by passwords ................................................................................ 3-37 Planning for RADIUS operation ............................................................................................... 3-38 Filtering protocols and ports .................................................................................................... 3-38 Encrypting downlink broadcasts ............................................................................................. 3-42 Isolating SMs in PMP ................................................................................................................ 3-42 Filtering management through Ethernet ................................................................................ 3-42 Allowing management from only specified IP addresses ..................................................... 3-43 Configuring management IP by DHCP .................................................................................... 3-43 Controlling PPPoE PADI Downlink Forwarding ...................................................................... 3-44 Legal and regulatory information ................................................................................ 4-1 Cambium Networks end user license agreement ........................................................................... 4-2 Definitions .................................................................................................................................... 4-2 Acceptance of this agreement ................................................................................................... 4-2 Grant of license ........................................................................................................................... 4-2 Conditions of use ........................................................................................................................ 4-3 Title and restrictions ................................................................................................................... 4-4 Confidentiality ............................................................................................................................. 4-4 Right to use Cambiums name ................................................................................................... 4-5 Transfer ........................................................................................................................................ 4-5 Updates ........................................................................................................................................ 4-5 Maintenance ................................................................................................................................ 4-5 Disclaimer .................................................................................................................................... 4-6 Limitation of liability ................................................................................................................... 4-6 U.S. government ......................................................................................................................... 4-6 Term of license ............................................................................................................................ 4-7 Chapter 4:

Page iv Contents Governing law ............................................................................................................................. 4-7 Assignment .................................................................................................................................. 4-7 Survival of provisions ................................................................................................................. 4-7 Entire agreement ......................................................................................................................... 4-7 Third party software .................................................................................................................... 4-7 Compliance with safety standards ................................................................................................. 4-22 Electrical safety compliance ..................................................................................................... 4-22 Electromagnetic compatibility (EMC) compliance ................................................................. 4-22 Human exposure to radio frequency energy .......................................................................... 4-22 Compliance with radio regulations ................................................................................................ 4-31 Type approvals .......................................................................................................................... 4-32 Brazil specific information ........................................................................................................ 4-33 Australia Notification ................................................................................................................ 4-33 Regulatory Requirements for CEPT Member States (www.cept.org) .................................. 4-33 Chapter 5: Preparing for installation .............................................................................................. 5-1 Safety .................................................................................................................................................. 5-2 Power lines .................................................................................................................................. 5-2 Working at heights ...................................................................................................................... 5-2 Power supply ............................................................................................................................... 5-2 Grounding and protective earth ................................................................................................ 5-2 Powering down before servicing ............................................................................................... 5-2 Primary disconnect device ......................................................................................................... 5-3 External cables ............................................................................................................................ 5-3 RF exposure near the antenna ................................................................................................... 5-3 Minimum separation distances ................................................................................................. 5-3 Grounding and lightning protection requirements .................................................................. 5-3 Grounding cable installation methods ...................................................................................... 5-3 Siting ODUs and antennas ......................................................................................................... 5-4 Thermal Safety ............................................................................................................................ 5-4 Preparing for installation ................................................................................................................... 5-5 ODU pre-configuration ............................................................................................................... 5-5 Preparing personnel .................................................................................................................... 5-5 Preparing inventory .................................................................................................................... 5-5 Preparing tools ............................................................................................................................ 5-6 Testing system components ............................................................................................................. 5-7 Unpacking Components ............................................................................................................. 5-7 Preparing the ODU ...................................................................................................................... 5-7 Configuring Link for Test ................................................................................................................. 5-15 Configuring the management PC ............................................................................................ 5-15 Logging into the web interface AP/SM/BH........................................................................... 5-16 Using the Quick Start Configuration Wizard of the AP/BHM ................................................ 5-16 Installation .................................................................................................................... 6-1 ODU variants and mounting bracket options .................................................................................. 6-2 Chapter 6:

Page v Contents Mount the ODU, LPU and surge suppressor ................................................................................... 6-3 Attach ground cables to the ODU .............................................................................................. 6-3 Mount the ODU on the mast ...................................................................................................... 6-6 Mount the top LPU ...................................................................................................................... 6-9 Mount the Surge Suppressor ..................................................................................................... 6-9 General protection installation ................................................................................................ 6-12 Installing the copper Cat5e Ethernet interface .............................................................................. 6-17 Install the main drop cable ....................................................................................................... 6-17 Install the bottom LPU to PSU drop cable .............................................................................. 6-19 Installing external antennas to a connectorized ODU .................................................................. 6-21 PMP 450i Series ......................................................................................................................... 6-21 PMP 450 Series .......................................................................................................................... 6-29 Attaching the PMP 450 platform AP and antenna to the mount point ................................. 6-35 PMP 450i Series 900 MHz AP ................................................................................................... 6-38 PMP 450 Series 900 MHz SM ................................................................................................... 6-45 Installing an integrated ODU........................................................................................................... 6-49 PMP 450m Series AP .............................................................................................................. 6-49 PMP/PTP 450i Series AP/SM/BH ............................................................................................ 6-52 Connecting Cat5e Ethernet cable.................................................................................................... 6-53 Connecting an RJ45 and gland to a unit ................................................................................. 6-53 Disconnecting an RJ45 and gland from a unit ....................................................................... 6-55 Installing ODU .................................................................................................................................. 6-56 Installing an PMP 450 platform AP .......................................................................................... 6-56 Installing a PMP 450 platform SM ........................................................................................... 6-57 Installing a PTP 450 platform BHM .......................................................................................... 6-58 Installing a PTP 450 platform BHS ........................................................................................... 6-59 Configuring the Link .................................................................................................................. 6-60 Monitoring the Link ................................................................................................................... 6-60 Installing the AC Power Injector ..................................................................................................... 6-61 Installing the AC Power Injector .............................................................................................. 6-61 Installing CMM4 ............................................................................................................................... 6-62 Supplemental installation information .......................................................................................... 6-64 Stripping drop cable ................................................................................................................. 6-64 Creating a drop cable grounding point ................................................................................... 6-65 Attaching and weatherproofing an N type connector ........................................................... 6-68 Chapter 7: Configuration .............................................................................................................. 7-71 Preparing for configuration ............................................................................................................. 7-72 Safety precautions .................................................................................................................... 7-72 Regulatory compliance ............................................................................................................. 7-72 Connecting to the unit ..................................................................................................................... 7-73 Configuring the management PC ............................................................................................ 7-73 Connecting to the PC and powering up .................................................................................. 7-74 Using the web interface ................................................................................................................... 7-75 Page vi Contents Logging into the web interface ................................................................................................ 7-75 Web GUI ..................................................................................................................................... 7-76 Using the menu options ........................................................................................................... 7-77 Quick link setup ................................................................................................................................ 7-81 Initiating Quick Start Wizard .................................................................................................... 7-81 Configuring time settings ......................................................................................................... 7-87 Powering the SM/BHS for test ................................................................................................. 7-88 Viewing the Session Status of the AP/BHM to determine test registration ......................... 7-89 Configuring IP and Ethernet interfaces .......................................................................................... 7-92 Configuring the IP interface ..................................................................................................... 7-93 Auxiliary port ............................................................................................................................. 7-96 NAT, DHCP Server, DHCP Client and DMZ ............................................................................. 7-97 DHCP BHS ............................................................................................................................. 7-114 Reconnecting to the management PC ................................................................................... 7-114 VLAN configuration for PMP ...................................................................................................... 7-114 VLAN configuration for PTP ...................................................................................................... 7-124 PPPoE page of SM ................................................................................................................... 7-128 IP4 and IPv6 ............................................................................................................................. 7-131 Upgrading the software version and using CNUT ...................................................................... 7-135 Checking the installed software version ............................................................................... 7-135 Upgrading to a new software version ................................................................................... 7-135 General configuration .................................................................................................................... 7-139 PMP 450m and PMP/PTP 450i Series .................................................................................... 7-139 PMP/PTP 450 Series ................................................................................................................ 7-152 Configuring Unit Settings page .................................................................................................... 7-157 Setting up time and date ............................................................................................................... 7-161 Time page of PMP/PTP 450 platform AP/BHM ..................................................................... 7-161 Configuring synchronization ......................................................................................................... 7-163 Configuring security ...................................................................................................................... 7-165 Managing module access by password ................................................................................ 7-166 Isolating from the internet APs/BHMs ................................................................................ 7-169 Encrypting radio transmissions ............................................................................................. 7-169 Requiring SM Authentication ................................................................................................. 7-170 Filtering protocols and ports .................................................................................................. 7-171 Encrypting downlink broadcasts ........................................................................................... 7-174 Isolating SMs ........................................................................................................................... 7-174 Filtering management through Ethernet .............................................................................. 7-175 Allowing management only from specified IP addresses ................................................... 7-175 Restricting radio Telnet access over the RF interface .......................................................... 7-175 Configuring SNMP Access ..................................................................................................... 7-178 Configuring Security ............................................................................................................... 7-180 Configuring radio parameters....................................................................................................... 7-192 PMP 450m Configurating radio ........................................................................................... 7-193 Page vii Contents PMP/PTP 450i Configurating radio ...................................................................................... 7-199 PMP/PTP 450 Configurating radio ....................................................................................... 7-217 Custom Frequencies page ...................................................................................................... 7-234 DFS for 5 GHz Radios .............................................................................................................. 7-237 MIMO-A mode of operation .................................................................................................... 7-239 Improved PPS performance of PMP 450 and 450i SMs ......................................................... 7-241 Setting up SNMP agent ................................................................................................................. 7-242 Configuring SM/BHSs IP over-the-air access ...................................................................... 7-243 Configuring SNMP .................................................................................................................. 7-244 Configuring syslog ......................................................................................................................... 7-249 Syslog event logging .............................................................................................................. 7-250 Configuring system logging ................................................................................................... 7-250 Configuring remote access ........................................................................................................... 7-255 Accessing SM/BHS over-the-air by Web Proxy .................................................................... 7-255 Monitoring the Link ........................................................................................................................ 7-256 Link monitoring procedure ..................................................................................................... 7-256 Exporting Session Status page of AP/BHM .......................................................................... 7-258 Configuring quality of service ....................................................................................................... 7-259 Maximum Information Rate (MIR) Parameters .................................................................... 7-259 Token Bucket Algorithm ......................................................................................................... 7-259 MIR Data Entry Checking ........................................................................................................ 7-260 Committed Information Rate (CIR) ........................................................................................ 7-260 Bandwidth from the SM Perspective ..................................................................................... 7-261 Interaction of Burst Allocation and Sustained Data Rate Settings ..................................... 7-261 High-priority Bandwidth ......................................................................................................... 7-261 Traffic Scheduling ................................................................................................................... 7-263 Setting the Configuration Source .......................................................................................... 7-264 Configuring Quality of Service (QoS) .................................................................................... 7-266 Installation Color Code .................................................................................................................. 7-272 Zero Touch Configuration Using DHCP Option 66...................................................................... 7-273 Configuration Steps ................................................................................................................ 7-273 Troubleshooting ...................................................................................................................... 7-278 Configuring Radio via config file .................................................................................................. 7-279 Import and Export of config file ............................................................................................. 7-279 Configuring a RADIUS server ....................................................................................................... 7-281 Understanding RADIUS for PMP 450 platform .................................................................... 7-281 Choosing Authentication Mode and Configuring for Authentication Servers - AP ..... 7-282 SM Authentication Mode Require RADIUS or Follow AP ............................................ 7-287 Handling Certificates ............................................................................................................... 7-292 Configuring RADIUS servers for SM authentication ........................................................... 7-293 Assigning SM management IP addressing via RADIUS ...................................................... 7-295 Configuring RADIUS server for SM configuration ............................................................... 7-295 Configuring RADIUS server for SM configuration using Zero Touch feature ................... 7-298 Page viii Contents Using RADIUS for centralized AP and SM user name and password management ........ 7-299 RADIUS Device Data Accounting ........................................................................................... 7-303 RADIUS Device Re-authentication ......................................................................................... 7-306 RADIUS Change of Authorization and Disconnect Message .............................................. 7-307 Microsoft RADIUS support ..................................................................................................... 7-308 Cisco ACS RADIUS Server Support ....................................................................................... 7-312 Configuring VSA ...................................................................................................................... 7-315 Chapter 8: Tools .............................................................................................................................. 8-1 Using Spectrum Analyzer tool .......................................................................................................... 8-2 Mapping RF Neighbor Frequencies ........................................................................................... 8-2 Spectrum Analyzer tool .............................................................................................................. 8-3 Remote Spectrum Analyzer tool .............................................................................................. 8-12 Using the Alignment Tool ............................................................................................................... 8-15 Aiming page and Diagnostic LED SM/BHS .......................................................................... 8-16 Alignment Tone ......................................................................................................................... 8-20 Using the Link Capacity Test tool ................................................................................................... 8-21 Performing RF Link Test, Link Test with Bridge or Link Test with Bridge and MIR 8-22 Performing Extrapolated Link Test .......................................................................................... 8-23 Link Capacity Test page of AP .................................................................................................. 8-24 Link Capacity Test page of BHM/BHS/SM ............................................................................... 8-26 Using AP Evaluation tool ................................................................................................................. 8-27 AP Evaluation page of AP ......................................................................................................... 8-27 Using BHM Evaluation tool ............................................................................................................. 8-31 BHM Evaluation page of BHS .................................................................................................. 8-31 Using the OFDM Frame Calculator tool ......................................................................................... 8-35 Using the Subscriber Configuration tool ....................................................................................... 8-39 Using the Link Status tool ............................................................................................................... 8-40 Link Status AP/BHM ............................................................................................................... 8-40 Link Status SM/BHS ............................................................................................................... 8-42 Using BER Results tool .................................................................................................................... 8-45 Using the Sessions tool ................................................................................................................... 8-46 Chapter 9: Operation ...................................................................................................................... 9-1 System information ........................................................................................................................... 9-2 Viewing General Status .............................................................................................................. 9-2 Viewing Session Status ............................................................................................................ 9-16 Viewing Remote Subscribers ................................................................................................... 9-22 Interpreting messages in the Event Log ................................................................................. 9-23 Viewing the Network Interface ................................................................................................. 9-25 Viewing the Layer 2 Neighbors ................................................................................................ 9-26 System statistics .............................................................................................................................. 9-27 Viewing the Scheduler statistics .............................................................................................. 9-27 Viewing list of Registration Failures statistics ........................................................................ 9-29 Interpreting Bridging Table statistics ...................................................................................... 9-30 Page ix Contents Interpreting Translation Table statistics.................................................................................. 9-31 Interpreting Ethernet statistics ................................................................................................. 9-32 Interpreting RF Control Block statistics ................................................................................... 9-35 Interpreting VLAN statistics ..................................................................................................... 9-36 Interpreting Data VC statistics .................................................................................................. 9-38 Interpreting Throughput statistics ........................................................................................... 9-40 Interpreting Overload statistics ................................................................................................ 9-43 Interpreting DHCP Relay statistics ........................................................................................... 9-44 Interpreting Filter statistics ....................................................................................................... 9-46 Viewing ARP statistics .............................................................................................................. 9-47 Viewing NAT statistics .............................................................................................................. 9-47 Viewing NAT DHCP Statistics .................................................................................................. 9-49 Interpreting Sync Status statistics ........................................................................................... 9-50 Interpreting PPPoE Statistics for Customer Activities ........................................................... 9-51 Interpreting Bridge Control Block statistics ............................................................................ 9-52 Interpreting Pass Through Statistics ....................................................................................... 9-54 Interpreting SNMPv3 Statistics ................................................................................................ 9-55 Interpreting syslog statistics .................................................................................................... 9-57 Interpreting Frame Utilization statistics .................................................................................. 9-57 Radio Recovery ................................................................................................................................ 9-61 Radio Recovery Console PMP/PTP 450i ................................................................................ 9-61 Default Mode (or Default/Override Plug) - PMP/PTP 450 ....................................................... 9-63 Reference Information ............................................................................................. 10-1 Equipment specifications ................................................................................................................ 10-2 Specifications for PMP 450m AP ............................................................................................. 10-2 Specifications for PMP 450i AP ................................................................................................ 10-5 Specifications for PMP 450i SM ............................................................................................... 10-9 Specifications for PTP 450i BH ............................................................................................... 10-13 Specifications for PMP 450 AP ............................................................................................... 10-17 Specifications for PMP 450 SM .............................................................................................. 10-22 Specifications for PTP 450 BH ................................................................................................ 10-26 PSU specifications ................................................................................................................... 10-31 Data network specifications .......................................................................................................... 10-33 Ethernet interface .................................................................................................................... 10-33 Wireless specifications .................................................................................................................. 10-34 General wireless specifications ............................................................................................. 10-34 Link Range and Throughput ................................................................................................... 10-34 Country specific radio regulations ............................................................................................... 10-35 Type approvals ........................................................................................................................ 10-35 DFS for 2.4 and 5 GHz Radios ................................................................................................ 10-36 Equipment Disposal ....................................................................................................................... 10-37 Waste (Disposal) of Electronic and Electric Equipment ....................................................... 10-37 Country specific maximum transmit power ......................................................................... 10-37 Chapter 10:

Page x Contents Chapter 11:

Country specific frequency range .......................................................................................... 10-48 FCC specific information......................................................................................................... 10-55 Innovation Science and Economic Development Canada (ISEDC) specific information . 10-59 Troubleshooting .................................................................................................... 11-64 General troubleshooting procedure ............................................................................................. 11-65 General planning for troubleshooting ................................................................................... 11-65 General fault isolation process .............................................................................................. 11-66 Secondary Steps ..................................................................................................................... 11-67 Troubleshooting procedures ......................................................................................................... 11-68 Module has lost or does not establish connectivity ............................................................ 11-68 NAT/DHCP-configured SM has lost or does not establish connectivity ............................ 11-70 SM Does Not Register to an AP ............................................................................................. 11-72 Module has lost or does not gain sync ................................................................................. 11-73 Module does not establish Ethernet connectivity ................................................................ 11-74 CMM4 does not pass proper GPS sync to connected modules.......................................... 11-75 Module Software Cannot be Upgraded ................................................................................ 11-76 Module Functions Properly, Except Web Interface Became Inaccessible ......................... 11-76 Power-up troubleshooting ............................................................................................................ 11-77 Registration and connectivity troubleshooting ........................................................................... 11-78 SM/BMS Registration .............................................................................................................. 11-78 Glossary .................................................................................................................................................. I Page xi List of Figures List of Figures Figure 1 PMP/PTP 450 platform typical bridge deployment .............................................................. 1-11 Figure 2 TDD frame division.................................................................................................................. 1-14 Figure 3 PMP/PTP 450 interfaces - AP .................................................................................................... 2-9 Figure 4 PMP/PTP 450 interfaces SM/BH ........................................................................................... 2-10 Figure 5 PMP/PTP 450 interfaces SM/BH Connectorized ................................................................. 2-10 Figure 6 PMP 450d SM - Integrated Dish ............................................................................................. 2-11 Figure 7 PMP 450 Series 3 GHz Integrated SM ................................................................................. 2-11 Figure 8 PTP 450 Series BHM/BHS .................................................................................................... 2-11 Figure 9 AP/BHM diagnostic LEDs, viewed from unit front ............................................................... 2-12 Figure 10 AP/BH diagnostic LEDs, viewed from unit front ................................................................. 2-14 Figure 11 AC Power Injector interfaces ................................................................................................ 2-17 Figure 12 AC+DC Enhanced Power Injector interfaces ....................................................................... 2-18 Figure 13 -48 V DC Power Injector interfaces ...................................................................................... 2-19 Figure 14 Gigabit Enet Capable power supply .................................................................................... 2-20 Figure 15 ODU rear interfaces ............................................................................................................... 2-22 Figure 16 ODU rear interfaces ............................................................................................................... 2-23 Figure 17 Connectorized ODU antenna interfaces .............................................................................. 2-24 Figure 18 Outdoor drop cable ............................................................................................................... 2-26 Figure 19 Alignment Tone Cable .......................................................................................................... 2-28 Figure 20 Cable grounding kit ............................................................................................................... 2-29 Figure 21 Cable gland (part number #N000065L033) ......................................................................... 2-33 Figure 22 uGPS ....................................................................................................................................... 2-34 Figure 23 CMM4 (Rack Mount).............................................................................................................. 2-35 Figure 24 CMM4 56V power adapter (dongle)..................................................................................... 2-36 Figure 25 CMM4 power adapter cabling diagram .............................................................................. 2-36 Figure 26 CMM4 (Cabinet with switch) ................................................................................................ 2-38 Figure 27 CMM3 ..................................................................................................................................... 2-39 Figure 28 Pole mounted CMM3 ............................................................................................................ 2-39 Figure 29 GPS antenna mounting ........................................................................................................ 2-41 Figure 30 Mast or tower installation ....................................................................................................... 3-2 Figure 31 Wall installation ....................................................................................................................... 3-3 Figure 32 Roof installation....................................................................................................................... 3-4 Figure 33 GPS receiver wall installation ................................................................................................ 3-5 Figure 34 GPS receiver tower or mast installation ............................................................................... 3-6 Figure 35 Rolling sphere method to determine the lightning protection zones ................................ 3-9 Figure 36 Example layout of 16 Access Point sectors (ABCD), 90 degree sectors ........................... 3-19 Figure 37 Example layout of 6 Access Point sectors (ABC), 60 degree sectors ............................... 3-20 Figure 38 Determinants in Rx signal level ........................................................................................... 3-22 Page xii List of Figures Figure 39 Cambium networks management domain ......................................................................... 3-27 Figure 40 Example of IP address in Class B subnet ............................................................................ 3-29 Figure 41 Categorical protocol filtering ................................................................................................ 3-40 Figure 42 Pin 1 location ......................................................................................................................... 5-10 Figure 43 Straight-through Ethernet Cable .......................................................................................... 5-12 Figure 44 AP/BHM to UGPS cable ........................................................................................................ 5-13 Figure 45 Alignment tone cable pin configuration ............................................................................. 5-14 Figure 46 RJ-11 pinout for the default plug ......................................................................................... 5-14 Figure 47 PMP 450 900 MHz SM grounding .......................................................................................... 6-6 Figure 48 Gigabit Surge Suppressor .................................................................................................... 6-10 Figure 49 600SSH Surge Suppressor inside .................................................................................... 6-11 Figure 50 Grounding cable minimum bend radius and angle ........................................................... 6-13 Figure 51 Grounding and lightning protection on mast or tower ..................................................... 6-14 Figure 52 Grounding and lightning protection on wall ...................................................................... 6-15 Figure 53 Grounding and lightning protection on building ............................................................... 6-16 Figure 54 RJ45 cable .............................................................................................................................. 6-18 Figure 55 AP antenna parts ................................................................................................................... 6-23 Figure 56 Antenna top plate .................................................................................................................. 6-24 Figure 57 Attaching antenna plate to the AP ....................................................................................... 6-24 Figure 58 Attaching the plate ................................................................................................................ 6-25 Figure 59 Connect the port A and B to the PMP 450i AP .................................................................... 6-25 Figure 60 AP antenna upper bracket assembly ................................................................................... 6-26 Figure 61 AP antenna upper bracket attached to upper adjustment arms ....................................... 6-26 Figure 62 Rear strap connected to upper AP antenna bracket........................................................... 6-27 Figure 63 Assembled upper bracket connected to AP antenna ......................................................... 6-27 Figure 64 AP Antenna Lower Bracket Assembly ................................................................................. 6-27 Figure 65 Lower bracket attached to AP antenna................................................................................ 6-28 Figure 66 Completed AP and antenna assembly ................................................................................ 6-28 Figure 67 PMP 450 AP antenna parts ................................................................................................... 6-29 Figure 68 AP antenna upper bracket assembly .................................................................................. 6-30 Figure 69 AP antenna upper bracket attached to upper adjustment arms ...................................... 6-30 Figure 70 Rear strap connected to upper AP antenna bracket.......................................................... 6-31 Figure 71 Assembled upper bracket connected to AP antenna ........................................................ 6-31 Figure 72 AP Antenna Lower Bracket Assembly ................................................................................ 6-32 Figure 73 Lower bracket attached to AP antenna .............................................................................. 6-32 Figure 74 Attaching bracket to the rear of the AP .............................................................................. 6-33 Figure 75 Lower bracket attached to AP antenna .............................................................................. 6-33 Figure 76 Mounted PMP 450 AP and antenna assembly, viewed from back and back .................. 6-34 Figure 77 Attaching the AP antenna upper bracket to the pole ......................................................... 6-35 Figure 78 Attaching the AP antenna lower bracket to the pole ......................................................... 6-35 Figure 79 Variables for calculating angle of elevation (and depression) .......................................... 6-37 Figure 80 PMP 450i 900 MHz AP antenna unbox view ...................................................................... 6-38 Figure 81 PMP 450i 900 MHz AP antenna inventory .......................................................................... 6-38 Page xiii List of Figures Figure 82 Attaching radio mounting PMP 450i 900 MHz AP antenna to the pole ........................... 6-43 Figure 83 900 MHz sector antenna alignment .................................................................................... 6-44 Figure 84 PMP 450i 900 MHz SM external directional antenna ......................................................... 6-45 Figure 85 Attach the antenna to the pole ............................................................................................ 6-45 Figure 86 Fixing the nuts ...................................................................................................................... 6-46 Figure 87 Fixing the radio to the antenna ............................................................................................ 6-47 Figure 88 Connecting RF cable to the radio ......................................................................................... 6-47 Figure 89 Yagi antenn alignment - horizentaly.................................................................................... 6-48 Figure 90 Yagi antenna alignment - upward tilt ................................................................................. 6-48 Figure 91 Yagi antenna alignment - downward tilt ............................................................................ 6-48 Figure 92 PMP 450m Series - AP unbox view..................................................................................... 6-49 Figure 93 Fixing the mounting plate to the back of the ODU ............................................................. 6-52 Figure 94 Attaching the bracket body .................................................................................................. 6-52 Figure 95 Ethernet cable gland for PMP/PTP 450 Series ................................................................... 6-54 Figure 96 Ethernet cable gland for PMP/PTP 450i Series .................................................................. 6-54 Figure 97 Ethernet cable gland for PMP 450m Series ....................................................................... 6-55 Figure 98 CMM4 cabled to support PMP/PTP 450 platform ............................................................... 6-63 Figure 99 Disarm Installation page (top and bottom of page shown) .............................................. 7-81 Figure 100 Regional Settings tab of AP/BHM ...................................................................................... 7-82 Figure 101 Radio Carrier Frequency tab of AP/BHM ........................................................................... 7-83 Figure 102 Synchronization tab of AP/BHM ......................................................................................... 7-84 Figure 103 LAN IP Address tab of the AP/BHM ................................................................................... 7-85 Figure 104 Review and Save Configuration tab of the AP/BHM ........................................................ 7-86 Figure 105 Time tab of the AP/BHM ..................................................................................................... 7-87 Figure 106 Time and date entry formats .............................................................................................. 7-88 Figure 107 Session Status tab of AP .................................................................................................... 7-90 Figure 108 NAT disabled implementation ........................................................................................... 7-98 Figure 109 NAT with DHCP client and DHCP server implementation ............................................... 7-99 Figure 110 NAT with DHCP client implementation ............................................................................. 7-99 Figure 111 NAT with DHCP server implementation .......................................................................... 7-100 Figure 112 NAT without DHCP implementation ................................................................................ 7-100 Figure 113 General page attributes - PMP 450 AP ............................................................................ 7-153 Figure 114 General page of PMP 450 SM .......................................................................................... 7-154 Figure 115 General page of PTP 450 BHM ......................................................................................... 7-155 Figure 116 General page of PTP 450 BHS .......................................................................................... 7-156 Figure 117 Sync Setting configuration ............................................................................................... 7-163 Figure 118 AP Evaluation Configuration parameter of Security tab for PMP ................................. 7-168 Figure 119 BHM Evaluation Configuration parameter of Security tab for PTP .............................. 7-168 Figure 120 RF Telnet Access Restrictions (orange) and Flow through (green) .............................. 7-175 Figure 121 RF Telnet Access Restriction (orange) and Potential Security Hole (green) ................ 7-176 Figure 122 Multicast VC statistics ....................................................................................................... 7-232 Figure 123 Multicast scheduler statistics ........................................................................................... 7-233 Figure 124 AP DFS Status ................................................................................................................... 7-237 Page xiv List of Figures Figure 125 AP Session Status page .................................................................................................... 7-255 Figure 126 AP Remote Subscribers page ........................................................................................... 7-255 Figure 127 Session Status page .......................................................................................................... 7-256 Figure 128 Exporting Session Status page of PMP 450i AP ............................................................. 7-258 Figure 129 Uplink and downlink rate caps adjusted to apply aggregate cap ................................. 7-260 Figure 130 Uplink and downlink rate cap adjustment example ....................................................... 7-260 Figure 131 Installation Color Code of AP ........................................................................................... 7-272 Figure 132 Configuration File upload and download page .............................................................. 7-279 Figure 133 SM Certificate Management ............................................................................................. 7-293 Figure 134 User Authentication and Access Tracking tab of the AP ............................................... 7-299 Figure 135 User Authentication and Access Tracking tab of the SM .............................................. 7-301 Figure 136 RADIUS accounting messages configuration ................................................................. 7-305 Figure 137 Device re-authentication configuration ........................................................................... 7-306 Figure 138 RADIUS CoA configuration for AP ................................................................................... 7-307 Figure 139 EAPPEAP settings .............................................................................................................. 7-308 Figure 140 Importing certificate in NPS ............................................................................................. 7-309 Figure 141 Selecting MD5 from NPS console.................................................................................... 7-310 Figure 142 User configuration ............................................................................................................ 7-310 Figure 143 RADIUS VSA configuration .............................................................................................. 7-311 Figure 144 Adding RADIUS client ....................................................................................................... 7-312 Figure 145 Creating users .................................................................................................................... 7-312 Figure 146 Creating RADIUS instance ................................................................................................ 7-313 Figure 147 RADIUS protocols.............................................................................................................. 7-313 Figure 148 Service selection ............................................................................................................... 7-314 Figure 149 Adding Trusted CA ............................................................................................................ 7-314 Figure 150 Installing Server Certificate .............................................................................................. 7-314 Figure 151 Mornitoring logs ................................................................................................................ 7-315 Figure 152 VSA list ............................................................................................................................... 7-316 Figure 153 Spectrum analysis - Results ................................................................................................. 8-3 Figure 154 Spectrum Analyzer page result PMP 450 SM ................................................................ 8-11 Figure 155 Alignment Tool tab of SM Receive Power Level > -70 dBm ......................................... 8-15 Figure 156 Alignment Tool tab of SM Receive Power Level between -70 to -80 dBm ................. 8-15 Figure 157 Alignment Tool tab of SM Receive Power Level < -80 dBm ......................................... 8-15 Figure 158 PMP/PTP 450i link alignment tone ..................................................................................... 8-20 Figure 159 Link Capacity Test - AP ....................................................................................................... 8-21 Figure 160 Link Capacity Test tab with 1714-byte packet length ....................................................... 8-22 Figure 161 Extrapolated Link Test results ............................................................................................ 8-24 Figure 162 SM Configuration page of AP ............................................................................................ 8-39 Figure 163 BER Results tab of the SM .................................................................................................. 8-45 Figure 164 Sessions tab of the AP ........................................................................................................ 8-46 Figure 165 Remote Subscribers page of AP ........................................................................................ 9-22 Figure 166 Event log data ...................................................................................................................... 9-24 Figure 167 Network Interface tab of the AP ......................................................................................... 9-25 Page xv List of Figures Figure 168 Network Interface tab of the SM ........................................................................................ 9-26 Figure 169 Layer 2 Neighbors page ...................................................................................................... 9-26 Figure 170 Bridging Table page ............................................................................................................ 9-31 Figure 171 Translation Table page of SM ............................................................................................ 9-31 Figure 172 ARP page of the SM ............................................................................................................ 9-47 Figure 173 Recovery Options page ....................................................................................................... 9-62 Page xvi List of Tables List of Tables Table 1 Main characteristics of the PMP 450m Series AP .................................................................... 1-3 Table 2 PMP 450m Series hardware configurations ............................................................................. 1-3 Table 3 Main characteristics of the PMP/PTP 450i Series ..................................................................... 1-4 Table 4 PMP/PTP 450i Series hardware configurations ........................................................................ 1-6 Table 5 Main characteristics of the PMP/PTP 450 Series ...................................................................... 1-8 Table 6 PMP/PTP 450 Series hardware configurations ......................................................................... 1-9 Table 7 Supported Interoperability for PMP ....................................................................................... 1-10 Table 8 Supported Interoperability for PTP ........................................................................................ 1-10 Table 9 Modulation levels ..................................................................................................................... 1-16 Table 10 PMP 450m variants ................................................................................................................... 2-2 Table 11 PMP 450i variants ..................................................................................................................... 2-3 Table 12 PMP 450 variants ...................................................................................................................... 2-4 Table 13 PTP 450i variants....................................................................................................................... 2-5 Table 14 PTP 450 variants........................................................................................................................ 2-6 Table 15 450m AP interface descriptions and cabling .......................................................................... 2-7 Table 16 AP/SM/BH interface descriptions and cabling ....................................................................... 2-8 Table 17 AP interface descriptions and cabling 2.4 GHz, 5 GHz ....................................................... 2-9 Table 18 AP/BHM LED descriptions ...................................................................................................... 2-13 Table 19 SM/BHS LED descriptions ...................................................................................................... 2-14 Table 20 PSU part numbers for PMP 450m AP ................................................................................... 2-15 Table 21 PSU part numbers for PMP/PTP 450i .................................................................................... 2-16 Table 22 AC Power Injector interface functions .................................................................................. 2-17 Table 23 AC+DC Enhanced Power Injector interface functions ......................................................... 2-18 Table 24 -48V DC Power Injector interfaces ......................................................................................... 2-19 Table 25 PSU part numbers for PMP/PTP 450 ..................................................................................... 2-20 Table 26 Gigabit Enet Capable power supply .................................................................................... 2-20 Table 27 Accessories part numbers ..................................................................................................... 2-21 Table 28 Lightning protection part numbers ....................................................................................... 2-21 Table 29 ODU rear interfaces ................................................................................................................ 2-22 Table 30 ODU rear interfaces ................................................................................................................ 2-23 Table 31 PSU drop cable length restrictions ....................................................................................... 2-25 Table 32 Drop cable part numbers ....................................................................................................... 2-26 Table 33 Main port PoE cable pinout ................................................................................................... 2-27 Table 34 Aux port PoE cable pinout ..................................................................................................... 2-27 Table 35 Aux port PoE cable pinout ..................................................................................................... 2-28 Table 36 Alignment tone adapter third party product details ............................................................ 2-28 Table 37 Cable grounding kit part numbers ........................................................................................ 2-29 Table 38 LPU and grounding kit contents ............................................................................................ 2-30 Table 39 LPU and grounding kit part number ..................................................................................... 2-30 Page xvii List of Tables Table 40 List of AP external antennas .................................................................................................. 2-31 Table 41 PTP 450i BH or PMP 450/450i SM external antenna ............................................................ 2-31 Table 42 RF cable and connector part numbers .................................................................................. 2-32 Table 43 RJ45 connector and spare gland part numbers ................................................................... 2-33 Table 44 CMM4 power adapter cable pinout....................................................................................... 2-37 Table 45 PMP 450m ODU part numbers .............................................................................................. 2-43 Table 46 PMP 450i ODU part numbers ................................................................................................. 2-43 Table 47 PTP 450i ODU part numbers .................................................................................................. 2-44 Table 48 PMP 450 ODU part numbers .................................................................................................. 2-44 Table 49 PTP 450 ODU part numbers ................................................................................................... 2-47 Table 50 PMP/PTP 450/450i Accessories .............................................................................................. 2-47 Table 51 PMP 450m wind loading (Newton) ....................................................................................... 3-12 Table 52 PMP/PTP 450i wind loading (Newton) .................................................................................. 3-12 Table 53 PMP 450m wind loading (lb force) ........................................................................................ 3-12 Table 54 PMP/PTP 450i wind loading (lb force) ................................................................................... 3-13 Table 55 PMP/PTP 450 wind loading (Newton) ................................................................................... 3-13 Table 56 PMP/PTP 450 wind loading (lb force) .................................................................................... 3-14 Table 57 Example 5.8 GHz 4-channel assignment by access site ...................................................... 3-19 Table 58 Example 5.8 GHz 3-channel assignment by access site ...................................................... 3-20 Table 59 RF cable lengths required to achieve 1.2 dB loss at 5.8 GHz .............................................. 3-25 Table 60 Special case VLAN IDs ........................................................................................................... 3-31 Table 61 VLAN filters in point-to-multipoint modules ........................................................................ 3-32 Table 62 Q-in-Q Ethernet frame ............................................................................................................ 3-33 Table 63 HTTPS security material ......................................................................................................... 3-36 Table 64 Ports filtered per protocol selections .................................................................................... 3-41 Table 65 Device default port numbers ................................................................................................. 3-41 Table 66 PMP 450 platform safety compliance specifications ........................................................... 4-22 Table 67 EMC emissions compliance ................................................................................................... 4-22 Table 68 FCC minimum safe distances PMP 450m 5.1 GHz, 5.2 GHz, 5.4 GHz and 5.8 GHz ........ 4-25 Table 69 FCC minimum safe distances PMP/PTP 450i 900 MHz, 4.9 GHz, 5.1 GHz, 5.2 GHz, 5.4 GHz and 5.8 GHz ...................................................................................................................................... 4-26 Table 70 ISEDC minimum safe distances PMP 450m 5.1, 5.2, 5.4 and 5.8 GHz............................ 4-27 Table 71 ISEDC minimum safe distances PMP/PTP 450i 4.9 GHz and 5.8 GHz ............................ 4-27 Table 72 FCC minimum safe distances PMP/PTP 450 900 MHz, 2.4 GHz, 3.65 GHz and 5 GHz ... 4-28 Table 73 ISEDC minimum safe distances PMP/PTP 450 900 MHz, 2.4 GHz, 3.5/3.65 GHz and 5 GHz

........................................................................................................................................................... 4-29 Table 74 Radio certifications ................................................................................................................. 4-32 Table 75 Tools for PMP and PTP 450 platform equipment installation .............................................. 5-8 Table 76 Main port pinout ..................................................................................................................... 5-11 Table 77 Aux port pinout ....................................................................................................................... 5-11 Table 78 RJ-45 pinout for straight-through Ethernet cable ................................................................ 5-12 Table 79 RJ-45 pinout for crossover Ethernet cable ........................................................................... 5-13 Table 80 AP/BHM to UGPS cable pinout .............................................................................................. 5-13 Page xviii List of Tables Table 81 PMP/PTP 450i ODU mounting bracket part numbers ............................................................ 6-2 Table 82 RJ45 connector and cable color code ................................................................................... 6-18 Table 83 Menu options and web pages ............................................................................................... 7-77 Table 84 Session Status Attributes AP .............................................................................................. 7-91 Table 85 IP interface attributes ............................................................................................................. 7-94 Table 86 SM/BHS private IP and LUID .................................................................................................. 7-95 Table 87 Aux port attributs .................................................................................................................... 7-96 Table 88 IP attributes - SM with NAT disabled .................................................................................. 7-102 Table 89 IP attributes - SM with NAT enabled................................................................................... 7-104 Table 90 NAT attributes - SM with NAT disabled ............................................................................. 7-105 Table 91 NAT attributes - SM with NAT enabled .............................................................................. 7-108 Table 92 SM DNS Options with NAT Enabled ................................................................................... 7-113 Table 93 NAT Port Mapping attributes - SM ...................................................................................... 7-113 Table 94 VLAN Remarking Example ................................................................................................... 7-115 Table 95 AP/BHM VLAN tab attributes ............................................................................................... 7-117 Table 96 Q-in-Q Ethernet frame .......................................................................................................... 7-118 Table 97 SM VLAN attributes .............................................................................................................. 7-120 Table 98 SM VLAN Membership attributes ....................................................................................... 7-124 Table 99 BHM VLAN page attributes .................................................................................................. 7-124 Table 100 BHS VLAN page attributes ................................................................................................. 7-127 Table 101 SM PPPoE attributes ........................................................................................................... 7-129 Table 102 DiffServ attributes AP/BHM ............................................................................................. 7-131 Table 103 Packet Filter Configuration attributes ............................................................................... 7-133 Table 104 General page attributes PMP 450i AP / PMP 450m AP ................................................. 7-140 Table 105 General page attributes PMP 450i SM ........................................................................... 7-145 Table 106 General page attributes PTP 450i BHM .......................................................................... 7-148 Table 107 General page attributes PTP 450i BHS ........................................................................... 7-150 Table 108 Unit Settings attributes PMP/PTP 450 platform AP/BHM ............................................. 7-158 Table 109 SM Unit Settings attributes ............................................................................................... 7-160 Table 110 PMP/PTP 450 platform AP/BHM Time attributes ............................................................ 7-161 Table 111 Add User page of account page - AP/ SM/BH .................................................................. 7-166 Table 112 Delete User page - PMP/PTP 450 platform AP/ SM/BH ................................................... 7-167 Table 113 Change User Setting page - PMP/PTP 450 platform AP/ SM/BH .................................... 7-167 Table 114 User page PMP/PTP 450 platform AP/SM/BH ................................................................ 7-168 Table 115 AP/BHM Protocol Filtering attributes ................................................................................ 7-171 Table 116 SM/BHS Protocol Filtering attributes ................................................................................ 7-173 Table 117 Port Configuration attributes AP/SM/BHM/BMS ........................................................... 7-174 Table 118 Security tab of the AP ......................................................................................................... 7-180 Table 119 Security attributes PMP 450 platform SM ..................................................................... 7-185 Table 120 Security attributes for PTP 450/450i BHS ......................................................................... 7-190 Table 121 PMP 450m AP Radio attributes - 5 GHz ............................................................................ 7-193 Table 122 PMP 450i AP Radio attributes - 5 GHz ............................................................................... 7-199 Table 123 PMP 450i SM Radio attributes 5 GHz ............................................................................. 7-206 Page xix List of Tables Table 124 PMP 450i AP Radio attributes - 900 MHz .......................................................................... 7-210 Table 125 PTP 450i BHM Radio page attributes 5 GHz .................................................................. 7-212 Table 126 PTP 450i BHS Radio attributes 5 GHz ............................................................................. 7-215 Table 127 PMP 450 AP Radio attributes - 5 GHz ................................................................................ 7-217 Table 128 PMP 450 AP Radio attributes - 3.65 GHz ........................................................................... 7-219 Table 129 PMP 450 AP Radio attributes - 3.5 GHz ............................................................................. 7-220 Table 130 PMP 450 AP Radio attributes - 2.4 GHz ............................................................................. 7-221 Table 131 PMP 450 SM Radio attributes 5 GHz .............................................................................. 7-222 Table 132 PMP 450 SM Radio attributes 3.65 GHz ......................................................................... 7-224 Table 133 PMP 450 SM Radio attributes 3.5 GHz ........................................................................... 7-225 Table 134 PMP 450 SM Radio attributes 2.4 GHz ........................................................................... 7-226 Table 135 PMP 450 SM Radio attributes 900 MHz .......................................................................... 7-227 Table 136 PTP 450 BHM Radio attributes 5 GHz .............................................................................. 7-229 Table 137 PTP 450 BHM Radio attributes 5 GHz .............................................................................. 7-230 Table 138 Example for mix of multicast and unicast traffic scenarios ............................................ 7-232 Table 139 PMP/PTP 450 platform AP/SM/BH Custom Frequencies page 5 GHz .......................... 7-234 Table 140 PMP/PTP 450 SM/BH Custom Frequencies page 3.65 GHz .......................................... 7-235 Table 141 PMP/PTP 450 SM/BH Custom Frequencies page 3.5 GHz ............................................ 7-236 Table 142 Contention slots and number of VCs ................................................................................ 7-238 Table 143 PMP/PTP 450 platform Modulation levels ........................................................................ 7-239 Table 144 Co-channel Interference per (CCI) MCS ............................................................................ 7-240 Table 145 Adjacent Channel Interference (ACI) per MCS ................................................................. 7-240 Table 146 LAN1 Network Interface Configuration tab of IP page attributes ................................... 7-243 Table 147 SNMP page attributes ........................................................................................................ 7-245 Table 148 Syslog parameters .............................................................................................................. 7-250 Table 149 Syslog Configuration attributes - AP ................................................................................ 7-251 Table 150 Syslog Configuration attributes - SM ............................................................................... 7-252 Table 151 Syslog Configuration attributes - BHS .............................................................................. 7-253 Table 152 Characteristics of traffic scheduling .................................................................................. 7-263 Table 153 Recommended combined settings for typical operations .............................................. 7-264 Table 154 Where feature values are obtained for a SM with authentication required .................. 7-265 Table 155 MIR, VLAN, HPC, and CIR Configuration Sources, Authentication Disabled ................ 7-265 Table 156 QoS page attributes - AP .................................................................................................... 7-266 Table 157 QoS page attributes - SM ................................................................................................... 7-268 Table 158 QoS page attributes - BHM ................................................................................................ 7-270 Table 159 QoS page attributes - BHS ................................................................................................. 7-271 Table 160 Security tab attributes ........................................................................................................ 7-283 Table 161 SM Security tab attributes ................................................................................................. 7-287 Table 162 RADIUS Vendor Specific Attributes (VSAs) ..................................................................... 7-296 Table 163 AP User Authentication and Access Tracking attributes ................................................ 7-300 Table 164 SM User Authentication and Access Tracking attributes ............................................... 7-302 Table 165 Device data accounting RADIUS attributes ...................................................................... 7-303 Table 166 Spectrum Analyzer page attributes - AP .............................................................................. 8-5 Page xx List of Tables Table 167 Spectrum Analyzer page attributes - SM ............................................................................. 8-6 Table 168 Spectrum Analyzer page attributes - BHM ........................................................................... 8-8 Table 169 Spectrum Analyzer page attributes - BHS ............................................................................ 8-9 Table 170 Remote Spectrum Analyzer attributes - AP ........................................................................ 8-13 Table 171 Remote Spectrum Analyzer attributes - BHM .................................................................... 8-14 Table 172 Aiming page attributes SM ............................................................................................... 8-17 Table 173 Aiming page attributes - BHS .............................................................................................. 8-19 Table 174 Link Capacity Test page attributes AP ............................................................................. 8-25 Table 175 Link Capacity Test page attributes BHM/BHS ................................................................. 8-26 Table 176 AP Evaluation tab attributes - AP ........................................................................................ 8-27 Table 177 BHM Evaluation tab attributes - BHS .................................................................................. 8-31 Table 178 OFDM Frame Calculator page attributes ............................................................................ 8-36 Table 179 OFDM Calculated Frame Results attributes ....................................................................... 8-37 Table 180 Color code vers uplink/downlink rate column ................................................................... 8-40 Table 181 Link Status page attributes AP/BHM ................................................................................ 8-40 Table 182 Link Status page attributes SM/BHS ................................................................................ 8-43 Table 183 General Status page attributes - AP ...................................................................................... 9-3 Table 184 General Status page attributes - SM ..................................................................................... 9-7 Table 185 General Status page attributes - BHM ................................................................................ 9-11 Table 186 General Status page attributes - BHS ................................................................................. 9-14 Table 187 Device tab attributes ............................................................................................................. 9-16 Table 188 Session tab attributes ........................................................................................................... 9-17 Table 189 Power tab attributes ............................................................................................................. 9-19 Table 190 Configuration tab attributes ................................................................................................. 9-20 Table 191 Session Status > Configuration CIR configuration denotations ....................................... 9-22 Table 192 Event Log messages for abnormal events ......................................................................... 9-24 Table 193 Event Log messages for normal events ............................................................................. 9-25 Table 194 Scheduler tab attributes ....................................................................................................... 9-27 Table 195 SM Registration Failures page attributes - AP ................................................................... 9-29 Table 196 BHS Registration Failures page attributes - BHM .............................................................. 9-29 Table 197 Flags status ............................................................................................................................ 9-30 Table 198 Ethernet tab attributes .......................................................................................................... 9-32 Table 199 Radio (Statistics) page attributes ........................................................................................ 9-35 Table 200 VLAN page attributes ........................................................................................................... 9-36 Table 201 Data VC page attributes ....................................................................................................... 9-38 Table 202 RF overload Configuration attributes AP/BHM ............................................................... 9-40 Table 203 Overload page attributes AP/SM/BHM/BHS .................................................................... 9-43 Table 204 DHCP Relay page attributes AP/SM ................................................................................. 9-44 Table 205 Filter page attributes - SM ................................................................................................... 9-46 Table 206 NAT page attributes - SM .................................................................................................... 9-48 Table 207 NAT DHCP Statistics page attributes - SM ......................................................................... 9-49 Table 208 Sync Status page attributes - AP ......................................................................................... 9-50 Table 209 PPPoE Statistics page attributes - SM ................................................................................ 9-51 Page xxi List of Tables Table 210 Bridge Control Block page attributes AP/SM/BHM/BHS................................................. 9-52 Table 211 Pass Through Statistics page attributes AP .................................................................... 9-54 Table 212 SNMPv3 Statistics page attributes AP ............................................................................. 9-55 Table 213 Syslog statistics page attributes AP/SM/BH .................................................................... 9-57 Table 214 Frame utilization statistics ................................................................................................... 9-58 Table 215 Recovery Options attributes ................................................................................................ 9-62 Table 216 PMP 450m AP specifications ............................................................................................... 10-2 Table 217 PMP 450i AP specifications .................................................................................................. 10-5 Table 218 PMP 450i SM specifications ................................................................................................. 10-9 Table 219 PTP 450i BH specifications ................................................................................................. 10-13 Table 220 PMP 450 AP specifications ................................................................................................. 10-17 Table 221 PMP 450 SM specifications ................................................................................................ 10-22 Table 222 PTP 450i BH specifications ................................................................................................. 10-26 Table 223 PMP/PTP 450i AC power Injector specifications .............................................................. 10-31 Table 224 PMP/PTP 450 power supply specifications (part number: N000900L001A) .................. 10-31 Table 225 PMP/PTP 450i Main and Aux Ethernet bridging specifications ...................................... 10-33 Table 226 PMP/PTP 450 Ethernet bridging specifications ................................................................ 10-33 Table 227 PMP/PTP 450 platform wireless specifications ................................................................ 10-34 Table 228 Radio certifications ............................................................................................................ 10-35 Table 229 Country & Bands DFS setting ............................................................................................ 10-36 Table 230 Default combined transmit power per country 900 MHz band PMP 450i................... 10-37 Table 231 Default combined transmit power per country 2.4 GHz band PMP/PTP 450 ............. 10-38 Table 232 Default combined transmit power per country 3.5 GHz band PMP/PTP 450 ............. 10-38 Table 233 Default combined transmit power per country 3.65 GHz band PMP/PTP 450 ........... 10-38 Table 234 Default combined transmit power per country 4.9 GHz band PMP/PTP 450/450i ..... 10-39 Table 235 Default combined transmit power per Country 5.1 GHz band PMP/PTP 450i ............ 10-40 Table 236 Default combined transmit power per Country 5.1 GHz band PMP 450m ................. 10-41 Table 237 Default combined transmit power per country 5.2 GHz band ..................................... 10-41 Table 238 Default combined transmit power per Country 5.2 GHz band PMP 450m ................. 10-42 Table 239 Default combined transmit power per country 5.4 GHz band PMP/PTP 450i ............ 10-43 Table 240 Default combined transmit power per Country 5.4 GHz band PMP 450m ................. 10-44 Table 241 Default combined transmit power per country 5.4 GHz band PMP 450 ..................... 10-45 Table 242 Default combined transmit power per country 5.8 GHz band PMP/PTP 450i ............ 10-46 Table 243 Default combined transmit power per Country 5.8 GHz band PMP 450m ................. 10-46 Table 244 Default combined transmit power per country 5.8 GHz band PMP 450 ..................... 10-46 Table 245 Frequency range per country 900 MHz band ................................................................ 10-48 Table 246 Frequency range per country 2.4 GHz band PMP/PTP 450 .......................................... 10-49 Table 247 Frequency range per country 3.5 GHz band PMP/PTP 450 .......................................... 10-49 Table 248 Frequency range per country 3.65 GHz band PMP/PTP 450 ........................................ 10-50 Table 249 Frequency range per country 4.9 GHz band PMP/PTP 450i ......................................... 10-50 Table 250 Frequency range per country 5.4 GHz band PMP/PTP 450i ......................................... 10-51 Table 251 Frequency range per country 5.4 GHz band PMP/PTP 450 .......................................... 10-52 Table 252 Frequency range per country 5.8 GHz band PMP/PTP 450i ......................................... 10-53 Page xxii List of Tables Table 253 Frequency range per country 5.8 GHz band PMP/PTP 450 .......................................... 10-53 Table 254 US FCC IDs .......................................................................................................................... 10-55 Table 255 USA approved antenna list 4.9 GHz .................................................................................. 10-57 Table 256 USA approved antenna list 5.1 and 5.2 GHz .................................................................... 10-58 Table 257 USA approved antenna list 5.4 GHz .................................................................................. 10-58 Table 258 USA approved antenna list 5.8 GHz .................................................................................. 10-59 Table 259 ISEDC Certification Numbers ............................................................................................ 10-61 Table 260 Canada approved antenna list 4.9 and 5.8 GHz ............................................................... 10-62 Table 261 Canada approved antenna list 5.2 and 5.4 GHz .............................................................. 10-63 Page xxiii About This User Guide This guide describes the planning, installation, configuration and operation of the Cambium point-

to-point and point-to-multipoint wireless Ethernet bridges. It covers PMP/PTP 450, 450i, 450d and PMP 450m platform Series. It is intended for use by the system designer, system installer and system administrator. For radio network design, refer to the following chapters:

Chapter 1: Product description Chapter 2: System hardware Chapter 3: System planning Chapter 4: Legal and regulatory information Chapter 5: Preparing for installation Chapter 6: Installation For system configuration, tools and troubleshooting, refer to the following chapters:

Chapter 7: Configuration Chapter 8: Tools Chapter 9: Operation Chapter 10: Reference Information Chapter 11: Troubleshooting Contacting Cambium Networks Support website:

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

http://www.cambiumnetworks.com Sales enquiries:

solutions@cambiumnetworks.com Support enquiries:

support@cambiumnetworks.com Repair enquiries:

rma@cambiumnetworks.com Telephone number list:

http://www.cambiumnetworks.com/contact Address:

Cambium Networks Limited, Global Headquarters, 3800 Golf Road, Suite 360, Rolling Meadows, IL 60008 USA Page 1 Chapter 1: Product description Important regulatory information Purpose Cambium Networks Point-to-Multi-Point (PMP)/Point-To-Point (PTP) 450 documents are intended to instruct and assist personnel in the operation, installation and maintenance of the Cambium PMP/PTP equipment and ancillary devices of 450 platforms. It is recommended that all personnel engaged in such activities be properly trained. Cambium disclaims all liability whatsoever, implied or express, for any risk of damage, loss or reduction in system performance arising directly or indirectly out of the failure of the customer, or anyone acting on the customer's behalf, to abide by the instructions, system parameters, or recommendations made in this document. Cross references References to external publications are shown in italics. Other cross references, emphasized in blue text in electronic versions, are active links to the references. This document is divided into numbered chapters that are divided into sections. Sections are not numbered, but are individually named at the top of each page, and are listed in the table of contents. Feedback We appreciate feedback from the users of our documents. This includes feedback on the structure, content, accuracy, or completeness of our documents. Send feedback to support@cambiumnetworks.com. Page 2 Chapter 1: Product description Important regulatory information Important regulatory information The 450 platfrom products are certified as an unlicensed device in frequency bands where it is not allowed to cause interference to licensed services (called primary users of the bands). Application firmware Download the latest 450 platform firmware and install it in the Outdoor Units (ODUs) before deploying the equipment. Instructions for installing firmware are provided in Upgrading the software version and using CNUT on page 7-135. USA specific information Caution This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

This device may not cause harmful interference, and This device must accept any interference received, including interference that may cause undesired operation The USA Federal Communications Commission (FCC) requires manufacturers to implement special features to prevent interference to weather radar systems that operate in the band 5600 MHz to 5650 MHz. These features must be implemented in all products able to operate outdoors in the band 5470 MHz to 5725 MHz. Manufacturers must ensure that such radio products cannot be configured to operate outside of FCC rules; specifically it must not be possible to disable or modify the radar protection functions that have been demonstrated to the FCC. Cambium supplies variants of the PMP/PTP 450i specifically for operation in the USA in order to comply with FCC requirements (KDB 905462 D02 UNII DFS Compliance Procedures New Rules v01r02). These variants are only allowed to operate with license keys that comply with FCC rules. Similarly, Cambium supplies variants of the PMP/PTP 450 specifically for operation in the USA in order to comply with FCC requirements (KDB 443999 D01 Approval of DFS UNII Devices v01r04). These variants are only allowed to operate with license keys that comply with FCC rules. To ensure compliance when using PMP 450 and PTP 450, follow the recommendation in Avoidance of weather radars (USA only). Page 3 Chapter 1: Product description Important regulatory information External antennas When using a connectorized version of the product, the conducted transmit power may need to be reduced to ensure the regulatory limit on transmitter EIRP is not exceeded. The installer must have an understanding of how to compute the effective antenna gain from the actual antenna gain and the feeder cable losses. The range of permissible values for maximum antenna gain and feeder cable losses are included in this user guide together with a sample calculation. The product GUI automatically applies the correct conducted power limit to ensure that it is not possible for the installation to exceed the EIRP limit, when the appropriate values for antenna gain and feeder cable losses are entered into the GUI. Avoidance of weather radars (USA only) To comply with FCC rules (KDB 443999: Interim Plans to Approve UNII Devices Operating in the 5470 - 5725 MHz Band with Radar Detection and DFS Capabilities), units which are installed within 35 km (22 miles) of a Terminal Doppler Weather Radar (TDWR) system (or have a line of sight propagation path to such a system) must be configured to avoid any frequency within +30 MHz or 30 MHz of the frequency of the TDWR device. This requirement applies even if the master is outside the 35 km (22 miles) radius but communicates with outdoor clients which may be within the 35 km (22 miles) radius of the TDWRs. If interference is not eliminated, a distance limitation based on line-of-sight from TDWR will need to be used. Devices with bandwidths greater than 20 MHz may require greater frequency separation. When planning a link in the USA, visit http://spectrumbridge.com/udia/home.aspx, enter the location of the planned link and search for TDWR radars. If a TDWR system is located within 35 km

(22 miles) or has line of sight propagation to the PTP device, perform the following tasks:

Register the installation on http://spectrumbridge.com/udia/home.aspx. Make a list of channel center frequencies that must be barred, that is, those falling within

+30 MHz or 30 MHz of the frequency of the TDWR radars. The PMP 450 platform AP must be configured to not operate on the affected channels. Canada specific information Caution This device complies with ISEDC s license-exempt RSSs. Operation is subject to the following two conditions:

(1) This device may not cause interference; and

(2) This device must accept any interference, including interference that may cause undesired operation of the device. ISEDC requires manufacturers to implement special features to prevent interference to weather radar systems that operate in the band 5600 MHz to 5650 MHz. These features must be implemented in all products able to operate outdoors in the band 5470 MHz to 5725 MHz. Page 4 Chapter 1: Product description Important regulatory information Manufacturers must ensure that such radio products cannot be configured to operate outside of ISEDC rules; specifically it must not be possible to disable or modify the radar protection functions that have been demonstrated to ISEDC . In order to comply with these ISEDC requirements, Cambium supplies variants of the PMP/PTP 450 platform for operation in Canada. These variants are only allowed to operate with license keys that comply with ISEDC rules. In particular, operation of radio channels overlapping the band 5600 MHz to 5650 MHz is not allowed and these channels are permanently barred. In addition, other channels may also need to be barred when operating close to weather radar installations. Other variants of the PMP/PTP 450 platform are available for use in the rest of the world, but these variants are not supplied to Canada except under strict controls, when they are needed for export and deployment outside Canada. Renseignements specifiques au Canada Attention Le prsent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorise aux deux conditions suivantes :

(1) l'appareil ne doit pas produire de brouillage, et

(2) l'utilisateur de l'appareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible d'en compromettre le fonctionnement. ISEDC (ISEDC ) a demand aux fabricants de mettre en uvre des mcanismes spcifiques pour viter dinterfrer avec des systmes radar fonctionnant dans la bande 5600 MHz 5650 MHz. Ces mcanismes doivent tre mis en uvre dans tous les produits capables de fonctionner l'extrieur dans la bande 5470 MHz 5725 MHz. Les fabricants doivent s'assurer que les produits de radiocommunications ne peuvent pas tre configurs pour fonctionner en dehors des rgles ISEDC , en particulier, il ne doit pas tre possible de dsactiver ou modifier les fonctions de protection des radars qui ont t dmontrs ISEDC . Afin de se conformer ces exigences de ISEDC , Cambium fournit des variantes du PMP/PTP 450 platform exclusivement pour le Canada. Ces variantes ne permettent pas lquipement de fonctionner en dehors des rgles de ISEDC . En particulier, le fonctionnement des canaux de radio qui chevauchent la bande 5600-5650 MHz est interdite et ces canaux sont dfinitivement exclus. ISEDC Approved Antennas The list of antennas used to obtain ISEDC approvals is provided in section Country specific radio regulations, Innovation Science and Economic Development Canada (ISEDC) , Table 260. Page 5 Chapter 1: Product description Important regulatory information Antennas externes Lorsque vous utilisez une version du produit sans antenne intgre, il peut tre ncessaire de rduire la puissance d'mission pour garantir que la limite rglementaire de puissance isotrope rayonne quivalente (PIRE) n'est pas dpasse. L'installateur doit avoir une bonne comprhension de la faon de calculer le gain de l'antenne relle et les pertes dans les cbles de connections. La plage de valeurs admissibles pour un gain maximal de l'antenne et des pertes de cbles de connections sont inclus dans ce guide d'utilisation avec un exemple de calcul. L'interface utilisateur du produit applique automatiquement la limite de puissance mene correct afin de s'assurer qu'il ne soit pas possible pour l'installation de dpasser la limite PIRE, lorsque les valeurs appropries pour le gain d'antenne et les pertes de cbles d'alimentation sont entres dans linterface utilisateur. Antennes approuves par ISEDC La liste des antennas approves pour loperation au Canada est founie dans le chapitre Country specific radio regulations, Innovation Science and Economic Development Canada (ISEDC) tableaux Table 260. EU Declaration of Conformity Hereby, Cambium Networks declares that the Cambium PMP/PTP 450i, 450d and 450 Series Wireless Ethernet Bridge complies with the essential requirements and other relevant provisions of Directive 1999/5/EC. The declaration of conformity may be consulted at:

http://www.cambiumnetworks.com/support/ec-doc Specific expertise and training for professional installers To ensure that the PMP/PTP 450 platform equipment is installed and configured in compliance with the requirements of ISEDC and the FCC, installers must have the radio engineering skills and training described in this section. The Cambium Networks technical training program details can be accessed from below link:

http://www.cambiumnetworks.com/training/category/technical-training/

Ethernet networking skills The installer must have the ability to configure IP addressing on a PC and to set up and control products using a web browser interface. Page 6 Chapter 1: Product description Important regulatory information Lightning protection To protect outdoor radio installations from the impact of lightning strikes, the installer must be familiar with the normal procedures for site selection, bonding and grounding. Installation guidelines for the 450 platform can be found in Chapter 2: System hardware and Chapter 3:

System planning. Training The installer needs to have basic competence in radio and IP network installation. The specific requirements applicable to the 450 platform should be gained by reading Chapter 5: Preparing for installation, Chapter 6: Installation, Chapter 7: Configuration, Chapter 8: Tools and Chapter 9:

Operation; and by performing sample set ups at base workshop before live deployments. The Cambium Networks technical training program details can be accessed from below link:

http://www.cambiumnetworks.com/training/category/technical-training/

Page 7 Chapter 1: Product description Problems and warranty Problems and warranty Reporting problems If any problems are encountered when installing or operating this equipment, follow this procedure to investigate and report:

1 Search this document and the software release notes of supported releases. 2 Visit the support website. 3 Ask for assistance from the Cambium product supplier. 4 Gather information from affected units, such as any available diagnostic downloads. 5 Escalate the problem by emailing or telephoning support. Repair and service If unit failure is suspected, obtain details of the Return Material Authorization (RMA) process from the support website (http://www.cambiumnetworks.com/support). Hardware warranty Cambiums standard hardware warranty is for one (1) year from date of shipment from Cambium Networks or a Cambium distributor. Cambium Networks warrants that hardware will conform to the relevant published specifications and will be free from material defects in material and workmanship under normal use and service. Cambium shall within this time, at its own option, either repair or replace the defective product within thirty (30) days of receipt of the defective product. Repaired or replaced product will be subject to the original warranty period but not less than thirty (30) days. To register PMP and PTP products or activate warranties, visit the support website. For warranty assistance, contact the reseller or distributor. The removal of the tamper-evident seal will void the warranty. Caution Using non-Cambium parts for repair could damage the equipment or void warranty. Contact Cambium for service and repair instructions. Portions of Cambium equipment may be damaged from exposure to electrostatic discharge. Use precautions to prevent damage. Page 8 Chapter 1: Product description Security advice Security advice Cambium Networks systems and equipment provide security parameters that can be configured by the operator based on their particular operating environment. Cambium recommends setting and using these parameters following industry recognized security practices. Security aspects to be considered are protecting the confidentiality, integrity, and availability of information and assets. Assets include the ability to communicate, information about the nature of the communications, and information about the parties involved. In certain instances Cambium makes specific recommendations regarding security practices, however the implementation of these recommendations and final responsibility for the security of the system lies with the operator of the system. Page 9 Chapter 1: Product description Warnings, cautions, and notes Warnings, cautions, and notes The following describes how warnings and cautions are used in this document and in all documents of the Cambium Networks document set. Warnings Warnings precede instructions that contain potentially hazardous situations. Warnings are used to alert the reader to possible hazards that could cause loss of life or physical injury. A warning has the following format:

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

Caution Caution text and consequence for not following the instructions in the caution. Notes A note means that there is a possibility of an undesirable situation or provides additional information to help the reader understand a topic or concept. A note has the following format:

Note Note text. Page 10 Chapter 1: Product description Caring for the environment Caring for the environment The following information describes national or regional requirements for the disposal of Cambium Networks supplied equipment and for the approved disposal of surplus packaging. In EU countries The following information is provided to enable regulatory compliance with the European Union

(EU) directives identified and any amendments made to these directives when using Cambium equipment in EU countries. Disposal of Cambium equipment European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE) Do not dispose of Cambium equipment in landfill sites. For disposal instructions, refer to http://www.cambiumnetworks.com/support/weee-compliance Disposal of surplus packaging Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipients responsibility to ensure that packaging materials are collected and recycled according to the requirements of EU environmental law. In non-EU countries In non-EU countries, dispose of Cambium equipment and all surplus packaging in accordance with national and regional regulations. Page 11 Chapter 1: Product description This chapter provides a high level description of 450 platform Series products. It describes in general terms the function of the product, the main product variants and the main hardware components. The following topics are described in this chapter:

Overview of the PMP/PTP 450 platform on page 1-2 introduces the key features, typical uses, product variants and components of the PMP/PTP 450i and 450 series platform. Wireless operation on page 1-14 describes how the PMP/PTP 450 platform wireless link is operated, including modulation modes and spectrum management. System management on page 1-18 introduces the PMP/PTP 450 platform management system, including the web interface, configuration, security, alerts and recovery. Page 1-1 Chapter 1: Product description Overview of the PMP/PTP 450 platform Overview of the PMP/PTP 450 platform This section introduces the key features, typical uses, product variants and components of the PMP/PTP 450 platform. Purpose Cambium PMP/PTP 450 platform Series products are designed for Ethernet bridging over point-to-

point and point-to-multipoint microwave links in unlicensed and lightly-licensed frequency bands 900MHz, 2.4 GHz, 3.5/3.65 GHz and 4.9 to 5.925 GHz. Users must ensure that the 450 platform Series complies with local operating regulations. The 450 platform Series acts as a transparent bridge between two or more segments of the operators network. In this sense, it can be treated as a virtual wired connection among points. The 450 platform Series forwards 802.3 Ethernet frames destined for the other part of the network and filters frames it does not need to forward. The system is transparent to higher-level protocols such as VLANs. PMP/PTP 450 platform Series The 450 platform supports following series:

PMP 450m Series PMP/PTP 450i Series PMP/PTP 450 Series PMP 450d Series PMP 430 Series PMP 450m Series The PMP 450m Series AP is a revolutionary product which is based on Multi-User Multiple-input and Multiple-Output (MU-MIMO) technology. By combining a sophisticated beam forming antenna array with multiple transreceiver, Cambium Networks is using leading edge technology to provide a substantial shift upward in capacity per sector. Key features The Cambium 450m platform AP offers the following benefits:

MU-MIMO Access Point is a technologically cutting edge device providing more than 300 Mbps depending upon SMs position within sector. PMP 450m AP compatible with existing PMP 450/450i SM which help in upgrading existing network 10x higher throughput packet rate Page 1-2 Chapter 1: Product description Overview of the PMP/PTP 450 platform Integrated with 14x14 MU-MIMO antenna Gigabit copper/power port combined, 100BaseT port with power outm SFP Table 1 gives a summary of the main PMP 450m AP characteristics. Table 1 Main characteristics of the PMP 450m Series AP Characteristic Topology Value PMP Wireless link condition LOS, near LOS or non-LOS Range Duplexing PMP: Up to 40 mi (or 64 km) TDD (symmetric and asymmetric) Connectivity 1000Base-T Ethernet Main port with PoE input Operating frequencies 5.150 to 5.925 GHz Tx Power max 24 dBm Channel bandwidth 20 MHz Timing synchronization CMM5 or uGPS Data rate Up to 300 Mbps (20 MHz channel BW) Frequency bands The PMP 450m AP ODU operates in 5150 to 5825 MHz bands. Hardware components The ODU (Outdoor unit) is a self-contained transceiver unit that houses both radio and networking electronics. The main hardware components of the PMP 450m Series is:

PMP 450m AP The PMP 450m AP is supplied in the following configurations:

Table 2 PMP 450m Series hardware configurations ODU Frequency ODU type PMP 450m AP 5150 to 5925 MHz Integrated 14 dBi, 90 sector antenna Page 1-3 Chapter 1: Product description Overview of the PMP/PTP 450 platform PMP/PTP 450i Series The PMP/PTP 450i is a high performance wireless bridge for Ethernet traffic. It is capable of operating in line-of-sight (LOS), near-LOS and non-LOS propagation condition. It supports 900 MHz and 4.9 to 5.925 GHz frequency band. Key features The PMP/PTP 450i Series has extensive quality of service (QoS) classification capability. The Cambium PMP/PTP 450i Series offers the following benefits:

Cambiums highest performing point-to-multipoint solution, with up to 277 Mbps usable throughput for PMP and PTP State-of-the-art MIMO (Multi-In Multi-Out) technology Upto 7.5 bps/Hz spectral efficiency Increased Packet Processing rate Efficient GPS synchronized, scheduled TDD operation for easy AP/BHM site deployment and performance that is consistent regardless of SM/BHS loading A range of cost-effective subscriber device solutions to meet the business case of any network application MIMO Matrix B: This technique provides for the ability to double the throughput of a radio transmission under proper RF conditions. Different data streams are transmitted simultaneously on two different antennas MIMO-A mode: This mode of operation has same modulation levels as the MIMO-B mode, namely: QPSK, 16-QAM, 64-QAM and 256-QAM. This mode increases system reliability in the links. Timing synchronization via CMM4 or uGPS Table 3 gives a summary of the main PMP/PTP 450i characteristics. Table 3 Main characteristics of the PMP/PTP 450i Series Characteristic Topology Value PMP/PTP Wireless link condition LOS, near LOS or non-LOS Range PTP Up to 186 mi (or 299 km) depending on configuration for Duplexing Connectivity all bands PMP: Up to 40 mi (or 64 km) for 5.x GHz band PMP: Up to 120 mi (or 193 km) for 900 MHz band TDD (symmetric and asymmetric) 1000Base-T Ethernet Main port with PoE input Operating frequencies 902 to 928 MHz Page 1-4 Chapter 1: Product description Overview of the PMP/PTP 450 platform Tx Power 4.9 to 5.925 GHz max 27 dBm (5 GHz) max 25 dBm (900 MHz) Channel bandwidth 5, 7, 10, 15, 20 and 30 MHz High spectral efficiency Up to 7.5 bps/Hz Timing synchronization CMM4 or uGPS Data rate Up to 277 Mbps (30 MHz channel BW) for PMP/PTP Page 1-5 Chapter 1: Product description Overview of the PMP/PTP 450 platform Frequency bands The PMP/PTP 450i ODU can operate in the following bands:

900 MHz band: 902 to 928 MHz 5 GHz band: 4900 to 5925 MHz o 5.1 GHz band: 5150 to 5250 MHz o 5.2 GHz band: 5250 to 5350 MHz o 5.4 GHz band: 5470 to 5725 MHz o 5.8 GHz band: 5725 to 5925 MHz Note 900 MHz band requires different hardware. Hardware components The ODU (Outdoor unit) is a self-contained transceiver unit that houses both radio and networking electronics. The main hardware components of the PMP/PTP 450i are as follows:

PMP 450i AP PMP 450i SM PTP 450i BH (BHM/BHS) The PMP/PTP 450i is supplied in the following configurations:

Table 4 PMP/PTP 450i Series hardware configurations ODU Frequency ODU type PMP 450i AP 902 to 928 MHz Connectorized Use with an external antenna 4.9 to 5.925 GHz Integrated 16 dBi, 90 sector antenna

(support 4.9, 5.1, 5.2, 5.4 and 5.8 GHz) Connectorized Use with an external antenna PMP 450i SM 4.9 to 5.925 GHz Integrated 23 dBi flat panel antenna

(support 4.9, 5.1, 5.2, 5.4 and 5.8 GHz) Connectorized Use with an external antenna PTP 450i BH 902 to 928 MHz Connectorized Use with an external antenna 4.9 to 5.925 GHz Integrated 23 dBi flat panel antenna

(support 4.9, 5.1, 5.2, 5.4 and 5.8 GHz) Connectorized Use with an external antenna Page 1-6 Chapter 1: Product description Overview of the PMP/PTP 450 platform Note The BH ODU can be configured as a BHM or a BHS in PTP mode. Warning The PMP 450i AP 16 dBi, 90 sector antenna does not support frequency reuse between collocated APs because of poor F/B ratio. To achieve frequency re-use between collocated APs, please use the PMP 450i AP Connectorized and external antennas. For details on frequency planning, please see Radio Frequency planning on page 3-16. PMP/PTP 450 Series Cambium PMP/PTP 450 Series networks are designed for wireless point-to-multipoint and point-to-

point links in the unlicensed/licensed 900 MHz, 2.4 GHz, 3.5 GHz, 3.65 GHz, 5.4 GHz and 5.8 GHz bands. Users must ensure that the PMP/PTP 450 Series complies with local operating regulations. The PMP/PTP 450 Series enables network operators to grow their business by offering more capacity for data, voice and video applications. Key features The Cambium PMP/PTP 450 Series offers the following benefits:

Cambiums highest performing point-to-multipoint solution, with up to 227 Mbps usable throughput State-of-the-art MIMO (Multi-In Multi-Out) technology Better spectral efficiency than other MIMO alternatives Efficient GPS synchronized, scheduled TDD operation for easy Access Point site deployment and performance that is consistent regardless of subscriber loading A range of cost-effective subscriber device solutions to meet the business case of any network application MIMO Matrix B: This technique provides for the ability to double the throughput of a radio transmission under proper RF conditions. Different data streams are transmitted simultaneously on two different antennas. MIMO-A mode: This mode of operation using the same modulation levels as the MIMO-B mode, namely: QPSK, 16-QAM, 64-QAM and 256-QAM. Table 5 gives a summary of the main PMP/PTP 450 characteristics. Page 1-7 Chapter 1: Product description Overview of the PMP/PTP 450 platform Table 5 Main characteristics of the PMP/PTP 450 Series Characteristic Topology Value PMP/PTP Wireless link condition LOS, near LOS or non-LOS Range PTP: Up to 40 mi (or 64 km) depending on configuration for Duplexing Connectivity all bands PMP: Up to 40 mi (or 64 km) for 5.x GHz band TDD (symmetric and asymmetric) 100Base-T Ethernet Main port with PoE input Operating frequencies 900 MHz, 2.4 GHz, 3.5 GHz, 3.65 GHz and 5 GHz Tx Power max 27 dBm (2.4 GHz and 5 GHz) max 25 dBm (3.5 GHz and 3.65 GHz max 25 dBm (900 MHz - PMP 450 SM only) Channel bandwidth 5, 7, 10, 15, 20 and 30 MHz High spectral efficiency Up to 7.5 bps/Hz Data rate Up to 227 Mbps (30 MHz channel BW) for PMP/PTP Frequency bands The PMP/PTP 450 Series ODU can operate in the following bands:

900 MHz band: 902 to 928 MHz (SM only) 2.4 GHz band: 2400 to 2483 MHz 3.5 GHz band: 3300 to 3600 MHz 3.65 GHz band: 3500 to 3850 MHz 5.4 GHz band: 5470 to 5725 MHz 5.8 GHz band: 5725 to 5875 MHz Note The 900 MHz, 2.4 GHz, 3.5 GHz, 3.65 GHz and 5 GHz bands require different hardware. The 5 GHz band (either 5.4 or 5.8 GHz) can be configured on same hardware. Page 1-8 Chapter 1: Product description Overview of the PMP/PTP 450 platform Hardware components The main hardware components of the PMP/PTP 450 are as follows:

PMP 450 AP PMP 450 SM PTP 450 BH (BHM/BHS) The PMP/PTP 450 is supplied in the following configurations:

Table 6 PMP/PTP 450 Series hardware configurations ODU Frequency ODU type PMP 450 AP 2.4 GHz Connectorized Use with an external antenna Integrated 18 dBi Dual Slant 3.5/3.65 GHz Connectorized Use with an external antenna Integrated 16 dBi Dual Slant 5 GHz Connectorized Use with an external antenna

(5.4 and 5.8 GHz) Integrated 17 dBi H+V PMP 450 SM 900 MHz Connectorized Use with an external antenna 2.4 GHz Connectorized Use with an external antenna Integrated 7 dBi Dual Slant, integrated patch 3.5/3.65 GHz Connectorized Use with an external antenna Integrated 8 dBi Dual Slant, integrated patch Integrated 19 dBi Flat Plate, integrated patch 5 GHz Connectorized Use with an external antenna

(5.4 and 5.8 GHz) Integrated 9 dBi H+V, integrated patch Integrated 25 dBi H+V, Integrated dish PTP 450 BH 3.5/3.65 GHz Connectorized Use with an external antenna Integrated 8 dBi Dual Slant 5 GHz Connectorized Use with an external antenna

(5.4 and 5.8 GHz) Integrated 9 dBi H+V Note The BH ODU can be configured as a BHM or a BHS in PTP mode Page 1-9 Chapter 1: Product description Overview of the PMP/PTP 450 platform Supported interoperability for 450m/450i/450/430 platforms The supported interoperability among various 450m/450i/450/430 hardware platforms are listed below:

Table 7 Supported Interoperability for PMP Band AP platform SM platform 5.1, 5.2, 5.4 and 5.8 GHz PMP 450m AP PMP 450i SM, PMP 450 SM 4.9, 5.1, 5.2 and 5.9 GHz PMP 450i AP PMP 450i SM (Greenfield) 5.4 and 5.8 GHz PMP 450i AP PMP 450 AP PMP 450i SM, PMP 450 SM, PMP 450d SM and PMP 430 SM 2.4, 3.5 and 3.65 GHz PMP 450 AP PMP 450 SM 900 MHz PMP 450i AP PMP 450 SM Table 8 Supported Interoperability for PTP Band 900 MHz BH platform PTP 450i BHM and BHS 3.5 and 3.65 GHz PTP 450 BHM and BHS 4.9, 5.1, 5.2, 5.4 and 5.8 GHz PTP 450i BHM and BHS 5.4 and 5.8 GHz PTP 450 BHM and BHS Page 1-10 Chapter 1: Product description Overview of the PMP/PTP 450 platform Typical deployment The 450 platform is an all outdoor solution consisting of a wireless bridge across sites. Each site installation consists of an Integrated or Connectorized outdoor unit (ODU) and a power supply

(PSU) (see Figure 1). The ODU provides the following interfaces:

Ethernet port: This provides proprietary power over Ethernet and connection to the management and/or data networks. Figure 1 PMP/PTP 450 platform typical bridge deployment Page 1-11 Building 1ODUAC supplyPSUNetworkequipmentBuilding 2ODUPSUNetworkequipmentAC supplyPower over Ethernet interfaceLightning protection unitsLightning protection units Chapter 1: Product description Overview of the PMP/PTP 450 platform Point-to-Multipoint The PMP 450 platform Series consists of Access Point (AP) and Subscriber Module (SM) ODU. The radio link operates on a single frequency channel in each direction using Time Division Duplex

(TDD). Applications for the PMP Series include:

High throughput enterprise applications nLOS video surveillance in metro areas Urban area network extension Network extension into areas with foliage Point-to-Point (Backhaul) The PTP 450 platform Series consists of two BH (Backhaul) ODUs. The customer can decide, via software configuration, if this unit is a BHM (Backhaul Master) or a BHS (Backhaul Slave). The radio link operates on a single frequency channel using Time Division Duplex (TDD). Applications for the PTP Series include:

Enterprise Access nLOS video surveillance Leased line replacements and backup solutions Network extension Page 1-12 Chapter 1: Product description Overview of the PMP/PTP 450 platform Product variants The PMP 450 platform Series is available in the following product variants:

The ODU is supplied in the following regional variants:

o FCC, intended for deployment in the USA o EU, intended for deployment in countries of the European Union or other countries following ETSI regulations o Rest of the World (RoW), intended for deployment in countries other than USA and EU countries. o IC, intended for deployment in Canada A ruggedized ODU Subscriber Module designed to meet IP-66 and IP-67 standards to withstand harsh environments for 3 GHz band An integrated Dish ODU Subscriber Module in a new, rugged and high gain design for 5 GHz band An indoor power supply module providing Power-over-Ethernet (PoE) supply to ODU

(AP/SM/BH) Antennas and antenna cabling: Connectorized ODUs require external antennas connected using RF cable Ethernet cabling: All configurations require a copper Ethernet Cat5e connection from the ODU

(Ethernet port) to the PoE Lightning protection unit (LPU): LPUs are installed in the ports copper drop cables to provide transient voltage surge suppression Surge Suppression: The Gigabit Surge Suppressor provides a path to ground (Protective Earth) that protects connected radio equipment from near-miss lightning strikes. Ground cables: ODU, LPUs and outdoor copper Ethernet cables are bonded to the site grounding system using ground cables. For more information about these components, including interfaces, specifications and Cambium part numbers, refer to Chapter 2: System hardware. Page 1-13 Chapter 1: Product description Wireless operation Wireless operation This section describes how the PMP/PTP 450 platform wireless link is operated, including modulation modes, power control and security. Time division duplexing The system uses Time Division Duplexing (TDD) one channel alternately transmits and receives rather than using one channel for transmitting and a second channel for receiving. To accomplish TDD, the AP/BHM must provide sync to its SM/BHS. Furthermore, collocated APs/BHMs must be synced together an unsynchronized AP/BHM that transmits during the receive cycle of a collocated AP/BHM can prevent a second AP/BHM from being able to decode the signals from its APs/BHSs. In addition, across a geographical area, APs/BHMs that can hear each other benefit from using a common sync to further reduce self-interference within the network. Modules use TDD on a common frequency to divide frames for uplink (orange) and downlink

(green) usage, as shown in the figure below. For more information on synchronization configuration options, see GPS synchronization on page 2-34. Figure 2 TDD frame division Time Page 1-14 Chapter 1: Product description Wireless operation TDD frame parameters The TDD burst duration varies depending on the following:

Channel Bandwidth Cyclic Prefix Frame Period Frame configuration - Downlink Data Link operation Dynamic Rate Adaptation OFDM and channel bandwidth The PMP/PTP 450 platform 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 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 the following values: 5, 7, 10, 15, 20 and 30 MHz. Higher bandwidths provide greater link capacity at the expense of using more bandwidth. 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. Note The channel bandwidth must be configured to the same value at both ends of the link. Not all channel bandwidths are available in all regulatory bands. Cyclic Prefix OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol (slot) to allow multi-pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. For your convenience, the 450 and 450i products have been locked to a 1/16 CP. Frame Period The frame period or frame duration is the time between the beginning of a frame and the end of the frame. The PMP/PTP 450 platform Series supports two frame periods: 2.5 ms and 5 ms. The 5ms frame period configuration provides higher throughput as a result of reduced frame overhead during transmission. In turn, the 2.5 ms frame period configuration affords reduced latency in the system, half of that introduced by the 5 ms frame configuration. Page 1-15 Chapter 1: Product description Wireless operation Frame configuration - Downlink Data The percentage of frame assigned to transport downlink data. The downlink data specifies the percentage of the aggregate throughput for the downlink (frames transmitted from the AP/BHM to the subscriber). The configurable range is 15 to 85 percent. Link operation Dynamic Rate Adapt PMP/PTP 450 platform Series products offer eight levels or speeds of operation 2X MIMO-B and 1X MIMO-A (QPSK), 4X MIMO-B and 2X MIMO-A (16-QAM), 6x MIMO-B and 3X MIMO-A (64-QAM) and 8X MIMO-B and 4X MIMO-A (265-QAM). If received power is less due to distance between the AP/BHM and the SM/BHS or due to obstructions, or if interference affects the RF environment, the system automatically and dynamically adjusts the links to the best operation level. The system chooses its modulation rate dynamically, based on an internal ARQ (Automatic Repeat reQuest) error control method. With ARQ, every data slot of every frame sent over the air (except downlink broadcast) is expected to be acknowledged by the receiver, and if acknowledgement is not received, the data is resent. The sending unit monitors these re-sends and adjusts the modulation rate accordingly. It is normal to have links that change levels of operation as the RF environment changes. Furthermore, the uplink or downlink portions of TDD duty cycle operate independently; normal operation can have a downlink running at 6x while the uplink RF environment only supports 2x. The various modulation levels used by the PMP/PTP 450 platform are shown in Table 9. Table 9 Modulation levels Rate MIMO-B MIMO-A QPSK 2X MIMO-B 1X MIMO-A 16-QAM 4X MIMO-B 2X MIMO-A 64-QAM 6X MIMO-B 3X MIMO-A 256-QAM 8X MIMO-B 4X MIMO-A Note MIMO-A achieves half the throughput of MIMO-B but adds a combining diversity (gain) which enhances the link budget or availability. Page 1-16 Chapter 1: Product description Wireless operation MIMO Multiple-Input Multiple-Output (MIMO) techniques provide protection against fading and increase the probability that the receiver decodes 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 sub-features that comprises the MIMO techniques utilized in the PMP/PTP 450 platform product are:

Matrix A: This technique enables the 450 platform radio to use a scheme that optimizes coverage by transmitting the same data over both antennas. This redundancy improves the signal to noise ratio at the receiver making it more robust, at the cost of throughput. Matrix B: This technique provides for the ability to double the throughput of a radio transmission under proper RF conditions. Different data streams are transmitted simultaneously on two different antennas. Encryption The Cambium 450 platform Series supports optional encryption for data transmitted over the wireless link. The PTP 450 platform Series supports the following forms of encryption for security of the wireless link:

DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys and 256-bit key size to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. The default setting on an AP is "Disabled". Page 1-17 Chapter 1: Product description System management System management This section introduces the PMP/PTP 450 platform management system, including the web interface, installation, configuration, alerts and upgrades. Management agent PMP/PTP 450 platform equipment is managed through an embedded management agent. Management workstations, network management systems or PCs can be connected to this agent using the modules Ethernet port or over-the air (SM/BHS) The management agent supports the following interfaces:

Hypertext transfer protocol (HTTP) Hypertext transfer protocol secure (HTTPS) RADIUS authentication Simple network management protocol (SNMP) v2c and v3 Network time protocol (NTP) System logging (Syslog) Wireless Manager (WM) software Canopy Network Updater Tool (CNUT) software Web server The PMP/PTP 450 platform management agent contains a web server. The web server supports access via the HTTP/HTTPS interface. Web-based management offers a convenient way to manage the PMP/PTP 450 platform equipment from a locally connected computer or from a network management workstation connected through a management network, without requiring any special management software. The web and SNMP are the interfaces supported for installation of 450 platform equipment and for the majority of configuration management tasks. Page 1-18 Chapter 1: Product description System management Web pages The web-based management interfaces provide comprehensive web-based fault, configuration, performance and security management functions organized into the following groups:

Access Point or Backhaul Master:

Home Configuration Statistics Tools Logs Accounts Quick Start Copyright Subscriber Module or Backhaul Slave Home Configuration Statistics Tools Logs Accounts PDA Copyright Identity-based user accounts When identity-based user accounts are configured, a security officer can define from one to four user accounts, each of which may have one of the four possible roles:

ADMINISTRATOR, who has full read and write permissions. This is the level of the root and admin users, as well as any other administrator accounts that one of them creates. INSTALLER, who has permissions identical to those of ADMINISTRATOR except that the installer cannot add or delete users or change the password of any other user. TECHNICIAN, who has permissions to modify basic radio parameters and view informational web pages GUEST, who has no write permissions and only a limited view of General Status tab Admin, Installer and Tech accounts can be configured as READ-ONLY. This will allow the account to only see the items. See Managing module access by passwords for detailed information on account permissions. Page 1-19 Chapter 1: Product description System management Remote Authentication Dial-in User Service (RADIUS) The PMP 450 platform system includes support for RADIUS (Remote Authentication Dial In User Service) protocol functionality including:

Authentication: Allows only known SMs onto the network (blocking rogue SMs), and can be configured to ensure SMs are connecting to a known network (preventing SMs from connecting to rogue APs). RADIUS authentication is used for SMs, but not used for APs. SM Configuration: Configures authenticated SMs with MIR (Maximum Information Rate), High Priority, and VLAN (Virtual LAN) parameters from the RADIUS server when a SM registers to an AP. SM Accounting provides support for RADIUS accounting messages for usage-based billing. This accounting includes indications for subscriber session establishment, subscriber session disconnection, and bandwidth usage per session for each SM that connects to the AP. Centralized AP and SM user name and password management: Allows AP and SM usernames and access levels (Administrator, Installer, Technician and Read-Only) to be centrally administered in the RADIUS server instead of on each radio and tracks access events

(logon/logoff) for each username on the RADIUS server. This accounting does not track and report specific configuration actions performed on radios or pull statistics such as bit counts from the radios. Such functions require an Element Management System (EMS) such as Cambium Wireless Manager. This accounting is not the ability to perform accounting functions on the subscriber/end user/customer account. Framed-IP-Address: Operators may use a RADIUS server to assign management IP addressing to SM modules. SNMP The management agent supports fault and performance management by means of an SNMP interface. The management agent is compatible with SNMP v2c and SNMP v3 using Management Information Base (MIB) files which are available for download from the Cambium Networks Support website:

https://support.cambiumnetworks.com/files/ptp450 https://support.cambiumnetworks.com/files/pmp450 Network Time Protocol (NTP) The clock supplies accurate date and time information to the system. It can be set to run with or without a connection to a network time server (NTP). It can be configured to display local time by setting the time zone and daylight saving in the Time web page. If an NTP server connection is available, the clock can be set to synchronize with the server time at regular intervals. PMP/PTP 450 platform devices may receive NTP data from a CMM4 module or an NTP server configured in the systems management network. Page 1-20 Chapter 1: Product description System management The Time Zone option is configurable on the APs/BHMs Time Configuration page, and may be used to offset the received NTP time to match the operators local time zone. When set on the AP/BHM, the offset is set for the entire sector (AP/BHSs is notified of the current Time Zone upon initial registration). If a Time Zone change is applied, the AP/BHSs are notified of the change in a best effort fashion, meaning some AP/BHSs may not pick up the change until the next re-

registration. Time Zone changes are noted in the Event Log. An AP/BHM which is receiving NTP date and time information from an NTP server or from a GPS synchronization source may be used as an NTP server. Any client which has IP connectivity to the BHM may request NTP date and time information from the AP/BHM. No additional configuration

(other than the AP/BHM receiving valid NTP data) is required to use the AP/BHM as an NTP server. Wireless Manager (WM) Cambium Networks Wireless Manager 4.0 is recommended for managing PMP/PTP 450 platform networks. You can achieve better uptime through better visibility of your network with the Cambium Wireless Manager. This network management software tool offers breakthrough map-

based visualization capabilities using embedded Google maps, and combined with advanced configuration, provisioning, alerting and reporting features you can control your entire outdoor wireless network including Point-to-Multipoint and Point-to-Point solutions as well as other SNMP enabled devices. With its powerful user interface you can not only be able to control your network's access, distribution and backhaul layers, but can also have visibility to WLAN sites and be able to quickly launch indoor network management systems. Some key features of Wireless Manager are:

Template-Based Configuration: With Wireless Manager's user-defined templates you can accelerate the process for the configuration of the devices you add to your network resulting in quicker and easier deployments. The template-based functionality provides an automated way to configure large numbers of network devices with just a few mouse clicks, and can be scheduled to occur at any time via Wireless Manager's Task Scheduler. Ultralight Thin Client: With the growing mobile workforce it is important to have access to the status of your network at any time. With Wireless Manager you can view the status and performance of your entire wireless network via a compact web interface accessible by your smart phone. Map-Based Visualization: Wireless Manager overlays sophisticated real-time information about your network elements onto building layouts and dynamic Google maps. Visuals can be scaled to view an entire city or building or a specific area, floor or link. High Availability Architecture Support: Wireless Manager offers a high availability option, providing a highly reliable and redundant network management solution that ensures you always have management access to your network. High Scalability: The enhanced Wireless Manager offers you server scalability with support for up to 10,000 nodes as well as support for distributed server architecture. Cambiums Wireless Manager 4.0 available for download at:

http://www.cambiumnetworks.com/support/management-tools/wireless-manager/

Page 1-21 Chapter 1: Product description System management Canopy Network Updater Tool (CNUT) CNUT (Canopy Network Updater Tool) is the stand-alone software update tool for 450 platform Series products. The CNUT 4.9.12 or greater should be used for 450 platform radios. The Canopy Network Updater Tool has the following features:

Automatically discovers all network elements HTTP and HTTPS Executes UDP command that initiates and terminates the Auto-update mode within APs/BHMs. This command is both secure and convenient:

o For security, the AP/BHM accepts this command from only the IP address that specified in the Configuration page of ODU. o For convenience, Network Updater automatically sets this Configuration parameter in the AP/BHM to the IP address of the Network Updater server when the server performs any of the update commands. Allows you to choose among updating:

o Entire network. o Only elements that you select. o Only network branches that you select. Provides a Script Engine that you can use with any script which:

o The user can define. o Cambium supplies. CNUT is available at:

http://www.cambiumnetworks.com/support/management-tools/cnut/

Radio recovery mode The 450 platform recovery mode provides a means to recover from serious configuration errors including lost or forgotten passwords and unknown IP addresses. The recovery procedure for PMP/PTP 450i series and PMP/PTP 450 series differs due to difference in hardwares. This procedure for PMP/PTP 450i is known as Radio Recovery Console and for PMP/PTP 450 is known as Default mode (or Default/Override Plug). Radio Recovery Console PMP/PTP 450i Series The Radio Recovery Console mode supports:

Restoring factory default IP address 169.254.1.1 and password Boot with factory default Canopy system software settings Load previously installed SW images See Radio Recovery Console PMP/PTP 450i on page 9-61. Page 1-22 Chapter 1: Product description System management Default Mode (or Default Plug) PMP/PTP 450 Series A default plug is available to provide access to a module whose password and/or IP address have been forgotten. This plug allows the PMP/PTP 450 to be accessed using IP address 169.254.1.1 and no password. During the override session, you can assign any new IP address and set either or both user passwords (display-only and/or full access) as well as make other parameter changes. See Default Mode (or Default/Override Plug) - PMP/PTP 450 on page 9-63. Page 1-23 Chapter 2: System hardware This chapter describes the hardware components of a PMP/PTP 450 platform link. The following topics are described in this chapter:

System Components on page 2-2 describes system components of PTP and PMP including its accessories Cabling and lightning protection on page 2-22 describes various cable and lightning protection Antennas and antenna cabling on page 2-31 describes supported antennas and its accessories GPS synchronization on page 2-34 describes UGPS and CMM4. Ordering the components on page 2-43 specifies Cambium part numbers for PMP/PTP 450 platform components Page 2-1 Chapter 2: System hardware System Components System Components Point-to-Multipoint (PMP) The PMP radio is a transceiver device. It is a connectorized or radiated outdoor unit containing all the radio, networking, and surge suppression electronics. It can be purchased as:

Access Point Module (AP) Subscriber Module (SM) PMP 450 platform Integrated or Connectorized ODU The PMP 450m and PMP 450i and PMP 450 ODUs are supplied in Integrated or Connectorized configurations. See Table 2 PMP 450m Series hardware configurations on page 1-3 See Table 4 PMP/PTP 450i Series hardware configurations on page 1-6 See Table 6 PMP/PTP 450 Series hardware configurations on page 1-9 Product variants Table 10 PMP 450m variants Variant Region Antenna Frequency Channel Range Bandwidth Max Tx Power FCC RoW EU DES only IC 5 GHz PMP 450m AP 90 integrated 5150 5925 sector MHz 20 MHz 24 dBm Page 2-2 Chapter 2: System hardware System Components Table 11 PMP 450i variants Variant Region Antenna Frequency Channel Range Bandwidth Max Tx Power 900 MHz PMP 450i AP FCC Connectorized 902 - 928 MHz 5, 7, 10, 20 MHz 25 dBm 5 GHz PMP 450i AP 5 GHz PMP 450i SM FCC RoW Canada RoW DES FCC RoW Canada RoW DES 4900 5925 5, 10, 15, 20, 30 MHz MHz 27 dBm Connectorized Integrated 16 dBi 90 degree Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi 4900 5925 5, 10, 15, 20, 30 Connectorized MHz MHz 27 dBm Integrated 23 dBi Connectorized Integrated 23 dBi Note The Transmit power is limited based on regional setting. Page 2-3 Chapter 2: System hardware System Components Table 12 PMP 450 variants Variant Region Antenna Frequency Channel Range Bandwidth Max Tx Power 900 MHz PMP 450 SM FCC Connectorized 902 - 928 MHz 5, 7, 10, 20 MHz 25 dBm 2.4 GHz PMP 450 AP FCC ISM Connectorized 2400 2483.5 5, 10, 15, 20, 30 Integrated 18 dBi MHz MHz 2.4 GHz PMP 450 SM FCC ISM Connectorized 2400 2483.5 5, 10, 15, 20, 30 Integrated 7 dBi MHz MHz 3.5 GHz PMP 450 AP FCC ISM Connectorized 3300 3600 5, 7, 10, 15, 20, Integrated 16 dBi MHz 30 MHz 22 dBm 22 dBm 25 dBm 3.5 GHz PMP 450 SM Connectorized FCC ISM Integrated 8 dBi 3300 3600 5, 7, 10, 15, 20, MHz 30 MHz 25 dBm 3.65 GHz PMP 450 AP FCC ISM Integrated 19 dBi Connectorized 3500 3850 5, 7, 10, 15, 20, Integrated 16 dBi MHz 30 MHz Connectorized 25 dBm 3.65 GHz PMP 450 SM FCC ISM Integrated 8 dBi 3500 3850 5, 7, 10, 15, 20, MHz 30 MHz 25 dBm 5.4/5.8 GHz PMP 450 AP FCC RoW Canada RoW DES Integrated 19 dBi Connectorized Integrated 17 dBi Connectorized Integrated 17 dBi 5470 5875 15 and 30 MHz 10, 20 MHz (5, Connectorized MHz not available in DFS regions) 22 dBm Integrated 17 dBi Connectorized Integrated 23 dBi 5.4/5.8 GHz PMP 450 SM FCC, ROW, Canada, RoW DES Connectorized 10, 20 MHz (5, 5470 5875 15 and 30 MHz Integrated 9 dBi MHz Integrated 25 dBi not available in DFS regions) 22 dBm Page 2-4 Chapter 2: System hardware System Components Note The Transmit power is limited based on regional setting. Backhaul (PTP) The Backhaul radio is a transceiver device. It is a connectorized or integrated outdoor unit containing all the radio, networking, and surge suppression electronics. It can be configured as:

Backhaul Master (BHM) Backhaul Slave (BHS) PTP 450 platform Integrated or Connectorized ODU See Table 4 PMP/PTP 450i Series hardware configurations on page 1-6 See Table 6 PMP/PTP 450 Series hardware configurations on page 1-9 Product variants Table 13 PTP 450i variants Variant Region Antenna Frequency Channel Max Tx Notes Range Bandwid Power th FCC RoW Canada RoW DES Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi 4900 5925 MHz 5, 10, 15, 20, 30 MHz Transmit power 27 dBm limited based on regional setting FCC Connectorized 902 - 928 MHz 5, 7, 10, 20 MHz 25 dBm 5 GHz PTP 450i 900 MHz PTP 450i Page 2-5 Chapter 2: System hardware System Components Table 14 PTP 450 variants Variant Region Antenna Frequency Channel Max Tx Range Bandwidth Power 3.5 GHz PTP 450 BH Connectorized ROW Integrated 16 dBi 3300 3600 5, 7, 10, 15, MHz 20, 30 MHz 25 dBm 3.65 GHz PTP 450 BH 5.4/5.8 GHZ PTP 450 BH 5 GHz PTP 450 BH Integrated 19 dBi Connectorized ROW Integrated 16 dBi 3500 3850 5, 7, 10, 15, MHz 20, 30 MHz 25 dBm FCC FCC RoW Canada RoW DES Integrated 19 dBi Connectorized Integrated 17 dBi Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi 5470 5875 5, 10, 15, 20, MHz 30 MHz 22 dBm 4900 5875 5, 10, 15, 20, MHz 30 MHz 22 dBm Note The Transmit power is limited based on regional setting. Page 2-6 Chapter 2: System hardware System Components PMP/PTP 450 platform interfaces PMP 450m interfaces AP The 450m AP interfaces is illustrated below. Figure 5 PMP 450m interfaces Carabiner clip Ground Lugs SFP AUX PSU/Ethernet Table 15 PMP 450m AP interface descriptions and cabling Interface Function Cabling PSU/Ethernet Power-over-Ethernet, Ethernet communications (management and data), RJ45 Cable CMM sync-over-power synchronization See Table 76 on page 5-11 input Aux/Sync GPS synchronization input and output, UGPS power output Audio tones RJ 45 Cable See Table 77 on page 5-11 SFP Data Data Ground Lugs For grounding the unit 10 AWG copper wire Page 2-7 Chapter 2: System hardware System Components PMP/PTP 450i interfaces AP/SM/BH The AP/SM/BH interfaces are illustrated below. Figure 5 PMP/PTP 450i interfaces Carabiner clip Ground Lug RF port A Aux ENET RF port B Gland Table 16 AP/SM/BH interface descriptions and cabling Interface Function Cabling PSU/Ethernet Power-over-Ethernet, Ethernet communications (management and data), RJ45 Cable CMM sync-over-power synchronization See Table 76 on page 5-11 input Aux/Sync GPS synchronization input and output, UGPS power output Audio tones Data RJ 45 Cable See Table 77 on page 5-11 RF Port A RF Port B Vertical RF connection to antenna 50 ohm RF cable, N-type Horizontal RF connection to antenna 50 ohm RF cable, N-type Ground Lugs For grounding the unit 10 AWG copper wire Note If the Aux port will be used, a second ethernet Gland will need to be ordered (Part Number: N000065L033A). Page 2-8 Chapter 2: System hardware System Components PMP/PTP 450 interfaces - AP The PMP 450 AP interfaces are illustrated below. Figure 3 PMP/PTP 450 interfaces - AP RF Port A Sync/Default Ethernet RF port B Table 17 AP interface descriptions and cabling 2.4 GHz, 5 GHz Interface PSU/Ethernet Sync/Default Function Cabling Power-over-Ethernet, Ethernet communications (management and RJ45 Cable data) GPS synchronization signaling, provides power to UGPS module. Default plug port. RJ11 cable, default plug. 2.4 GHz

-45 degree RF connection to AP RF Port A antenna 5 GHz Vertical RF connection to AP antenna RF Port B 2.4 GHz +45 degree RF connection to AP antenna 5 GHz Horizontal RF connection to AP antenna 50 ohm RF cable, N-type 50 ohm RF cable, N-type Ground Lugs For grounding the unit 10 AWG copper wire Page 2-9 Chapter 2: System hardware System Components PMP/PTP 450 interfaces SM/BH The PMP 450 SM/BH interfaces are illustrated below. Figure 4 PMP/PTP 450 interfaces SM/BH Ethernet Sync/Default Figure 5 PMP/PTP 450 interfaces SM/BH Connectorized External antenna cable path A

(labeled A) External antenna cable path B

(labeled B) Ground (connectorized models) Note As per UL guidelines, the Ground Lug on the radiated SM is not required. Page 2-10 Chapter 2: System hardware System Components Figure 6 PMP 450d SM - Integrated Dish Figure 7 PMP 450 Series 3 GHz Integrated SM Figure 8 PTP 450 Series BHM/BHS Page 2-11 Chapter 2: System hardware System Components Diagnostic LEDs The diagnostic LEDs of PMP/PTP 450 platform Series are as shown below. Note The LED color helps distinguish the position of LED. The LED color does not indicate any status. AP/BHM LEDs The diagnostic LEDs report the information about the status of the AP/BHM. Figure 9 AP/BHM diagnostic LEDs, viewed from unit front ODU LED Display LED Labels PMP 450m AP LNK/5 ACT/4 GPS/3 SES/2 SYN/1 PWR PMP 450i AP/BHM LNK/5 ACT/4 GPS/3 SES/2 SYN/1 PWR PMP 450 AP/BHM LNK/5 ACT/4 GPS/3 SES/2 SYN/1 PWR Page 2-12 Chapter 2: System hardware System Components Table 18 AP/BHM LED descriptions LED Color when active Status information Notes provided PWR Red DC power SYN/1 Yellow Presence of sync SES/2 Green Unused Always lit after 10-20 seconds of power on.

-

-

GPS/3 Red Pulse of sync pulse from a GPS source goes along Lit when the AP/BHM is getting a sync with SYN/1 Presence of data activity on the Ethernet link Flashes during data transfer. Frequency of flash is not a diagnostic indication. Continuously lit when link is present. Ethernet link 10Base-T : Red Ethernet link 100Base-T : Green 1000Base-T : Orange Continuously lit when link is present. ACT/4 Yellow For PMP/PTP 450i and 450m LNK/5 Red/ Green/Orange

(bi-colored for 10/100/1000) For PMP/PTP 450 Green SM/BHS LEDs The SM/BHS LEDs provide different status of radio based on the operating modes. A SM/BHS in operating mode registers and passes traffic normally. A SM/BHS in aiming mode does not register or pass the traffic, but displays (via LED panel) the strength of received radio signals

(based on radio channel selected via Tools -> Alignment). Page 2-13 Chapter 2: System hardware System Components Figure 10 AP/BH diagnostic LEDs, viewed from unit front ODU LED Display LED Labels PMP 450i SM/BHS LNK/5 ACT/4 GPS/3 SES/2 SYN/1 PWR PMP 450 SM/BHS LNK/5 ACT/4 GPS/3 SES/2 SYN/1 PWR Table 19 SM/BHS LED descriptions Status information provided LED Color when SM / BHS in SM / BHS in Notes active OperatingMode Aiming Mode PWR Red DC power SYN/1 Yellow Presence of sync SES/2 Green Session Indicator GPS/3 Red Unused ACT/4 Yellow Presence of data activity on the Ethernet link Ethernet link For PMP/PTP 450i and 450m Red/ Green/

Orange

(bi-colored for 10/100/1000) For PMP/PTP 450 Green LNK/5 Always lit after 10-20 seconds of power on. Lit when SM/BHS is in sync with an AP/BHM. Lit when SM/BHS is in session. On - high interference. Blinking - medium interference. Off - low interference. Flashes during data transfer. Frequency of flash is not a diagnostic indication. Continuously lit when link is present. 10Base-T : Red 100Base-T : Green 1000Base-T : Orange These five LEDs act as a bar graph to indicate the relative quality of alignment. As power level improves during alignment, more of these LEDs are lit. Ethernet link Continuously lit when link is present. Page 2-14 Chapter 2: System hardware System Components Operating Mode Scanning: If the SM/BHS is not registered to AP/BHM, then these three LEDs cycle on and off from left to right (SYN/1, SES/2 and GPS/3). Ethernet Link: The LNK/5 LED lit continuously when link is present. Data Transfer: The ACT/4 LED lit on the presence of data activity on the Ethernet link. Aiming Mode The 5 LEDs (SYN/1, SES/2, GPS/3, ACT/4 and LNK/5) are turned into a 5-position bar graph. The more LEDs that are lit, the better the received power the module is seeing. The colors of the LEDS have no particular meaning other than to assist is distinguishing one position from the next. Power supply options The PMP 450m and PMP/PTP 450i/450 are powered over its Main Ethernet cable using Power Over Ethernet (POE). The power injector is connected to the ODU and network terminating equipment using Cat5e cable with RJ45 connectors. Power supply PMP 450m AP The PMP 450m AP supports powering from AC+DC Enhanced Power Injector. Table 20 PSU part numbers for PMP 450m AP Cambium description Cambium part number AC+DC Enhanced Power Injector C000065L002B Power supply PMP/PTP 450i The PMP/PTP 450i supports powering from the following powering sources:

Power Suppy, 60 W, 56 V with Gbps support AC+DC Enhanced Power Injector Power over Ethernet midspan, 60 W, -48 VDC Input CMM4 with external 56 V power supply CMM4 to 450i cable (Dongle) IEEE802.3at power injector Page 2-15 Chapter 2: System hardware System Components Note The 900 MHz SM is based off the 450 platform, please see Power supply PMP/PTP 450 on page 2-19. Warning Always use an appropriately rated and approved AC supply cord-set in accordance with the regulations of the country of use. Warning The PMP 450 Ruggedized High Gain Integrated Subscriber Module (Cambium part numbers C035045C014A and C036045C014A), while encapsulated in a 450i-

type enclosure, contains 450 circuitry which must be powered via 30VDC. Powering these SMs with a 56 VDC will damage the device. Please refer to Ethernet standards and cable lengths on Page 2-24 for details on maximum cable lengths between power injector and PMP/PTP 450i. Table 21 PSU part numbers for PMP/PTP 450i Cambium description Cambium part number Power supply, 60 W, 56 V with Gbps support AC+DC Enhanced Power Injector Power over Ethernet midspan, 60 W, -48 VDC Input Line Cord, Fig 8 US Line Cord, Fig 8 UK Line Cord, Fig 8 EU Power supply, 30 W, 56 V Gbps support N000065L001B C000065L002B N000000L036A N000065L003A N000065L004A N000065L005A N000000L034A Page 2-16 Chapter 2: System hardware System Components The AC Power Injector interfaces are shown in Figure 11 and described in Table 22. Figure 11 AC Power Injector interfaces Table 22 AC Power Injector interface functions Interface Function AC power in AC power input (main supply) ODU LAN RJ45 socket for connecting Cat5e cable to ODU RJ45 socket for connecting Cat5e cable to network Power (green) LED Power supply detection Page 2-17 Chapter 2: System hardware System Components The AC+DC Enhanced Power Injector interfaces are shown in Figure 12 and described in Table 23. Figure 12 AC+DC Enhanced Power Injector interfaces Table 23 AC+DC Enhanced Power Injector interface functions Interface Function 100-240V 47-63Hz 1.5A AC power input (main supply) DC In DC Out ODU LAN Alternative DC power supply input DC power output to a second PSU (for power supply redundancy) or to a NIDU RJ45 socket for connecting Cat5e cable to ODU RJ45 socket for connecting Cat5e cable to network Power (green) LED Power supply detection Ethernet (yellow) LED Ethernet traffic detection Page 2-18 Chapter 2: System hardware System Components The DC Power Injector interfaces are shown in Figure 13 and described in Table 24. Figure 13 -48 V DC Power Injector interfaces Table 24 -48V DC Power Injector interfaces Interface DC input Function 36 to 60V, 2A RJ 45 Sockets Two (Data In and Data & Power Out) LEDs Two (AC and Port) Power supply PMP/PTP 450 The PMP/PTP 450 support powering from the following powering sources:

Gigabit Enet Capable Power Supply - 30VDC, 15W Power Supply,120W 30VDC AT 60C 100-240VAC EL5 Warning The PMP 450 Ruggedized High Gain Integrated Subscriber Module (Cambium part numbers C035045C014A and C036045C014A), while encapsulated in a 450i-type enclosure, contains 450 circuitry which must be powered via 30VDC. Powering these SMs with a 56 VDC will damage the device. Page 2-19 Chapter 2: System hardware System Components Table 25 PSU part numbers for PMP/PTP 450 Cambium description Cambium part number Gigabit Enet Capable Power Supply - 30VDC, 15W Cable, UL Power Supply Cord Set, US Cable, UL Power Supply Cord Set, EU Cable, UL Power Supply Cord Set, UK Cable, UL Power Supply Cord Set, Brazil N000900L001A N000900L007A N000900L008A N000900L009A N000900L010A The Gigabit Enet Capable power supply interfaces are described in Table 26. This power supply requires procurement of an AC line cord that connects the outlet of the same (using IEC-60320 Type 5 connector). A list of available power supply cord options from Cambium Networks are givne in Table 25. Table 26 Gigabit Enet Capable power supply Interface AC Input Function 90-264 VAC, 0.5A rms @120VAC/ 0.25A rms @240VAC, 47 to 63 Hz DC Output 30.0 Vdc +/-5%, 15W, 500 mA max RJ 45 Sockets Two (Data In and Data & Power Out) LEDs Green, :LED Intensity determined by Level 5 efficiency Figure 14 Gigabit Enet Capable power supply Page 2-20 Chapter 2: System hardware System Components ODU mounting brackets & accessories The list of supported brackets is provided in Table 27. The "Tilt bracket assembly" is the recommended bracket for the AP, SM or BH integrated units. The "Mounting Bracket (Connectorized)" can be used where a low profile and ease of assembly of Connectorized AP, SM or BH is required. The "Mounting Bracket (Integrated)" provide a wider range of adjustment for AP, SM and BH integrated devices. Table 27 Accessories part numbers Cambium description Mounting brackets Tilt Bracket Assembly Mounting Bracket (Integrated) Mounting Bracket (Connectorized) Miscellaneous Ethernet cable adapter for CMM4 (Dongle) RJ-45 Gland Spare PG16 style (QTY 10) Blanking Plug Pack (Qty 10) Lightning protection Cambium part number N000045L002A N000065L031A N000065L032A N000045L001A N000065L033A N000065L036A The PMP/PTP 450i Series supports the lightning protection units listed in Table 28. The LPU offers the highest level of protection and is the recommended device. Where low cost deployment is essential, for example for SM in residential application, the Gigabit Surge Suppressor may be used instead. Table 28 Lightning protection part numbers Cambium description Cambium part number LPU and Grounding Kit (1 kit per ODU) Surge Suppressor (30 VDC) Gigabit Surge Suppressor (56 VDC) C000065L007A 600SSH C000000L033A Page 2-21 Chapter 2: System hardware Cabling and lightning protection Cabling and lightning protection ODU interfaces PMP 450m AP These interfaces are described in Table 30. Figure 15 ODU rear interfaces Ground Lug LED SFP Aux PSU (Main) Ground Lug Table 29 ODU rear interfaces Port name Connector Interface Description PSU (Main) RJ45 PoE input Power over Ethernet (PoE). 10/100/1000BASE-T Data Ethernet Aux RJ45 10/100/100BASE-T Ethernet Data PoE output Standard IEEE802.3at PoE. Sync input/output Connection and powering of UGPS Sync input SFP RJ45 10/100/100BASE-T Ethernet Data Ground Lugs 10 AWG copper wire For grounding the unit Page 2-22 Chapter 2: System hardware Cabling and lightning protection ODU interfaces PMP/PTP 450i The Ethernet and Sync/AUX ports are on the rear of the integrated and connectorized ODUs

(Figure 16). These interfaces are described in Table 30. Figure 16 ODU rear interfaces LED Ground Lug Ground Lug Aux Main RF port B RF port A Table 30 ODU rear interfaces Port name Connector Interface Description Main PSU RJ45 PoE input Power over Ethernet (PoE). 10/100/1000BASE-T Data Ethernet Sync/AUX RJ45 10/100/100BASE-T Ethernet Data (see Note below) PoE output Standard IEEE802.3at PoE. Sync input/output Connection and powering of UGPS Sync input The front of the connectorized ODU (Figure 17 Connectorized ODU antenna interfaces) provides N type female connectors for RF cable interfaces to antennas with ports A and B for vertical and horizontal polarization respectively. Page 2-23 Chapter 2: System hardware Cabling and lightning protection Figure 17 Connectorized ODU antenna interfaces Ethernet standards and cable lengths All configurations require a copper Ethernet connection from the ODU (Ethernet port) to the PoE. Table 31 specifies, for each type of PSU and configuration, the maximum permitted PSU drop cable length. Page 2-24 Chapter 2: System hardware Cabling and lightning protection Table 31 PSU drop cable length restrictions System configuration Maximum cable length (m/ft) Power supply PoE powered device From power supply From ODU to PoE on AUX/SYNC port to ODU

(see Note below) device on AUX/SYNC port (see Note below) Power supply (30W) None 100 m N/A IEEE 802.3at Type 2 100 m in total AC Power Injector (60W) None 100 m N/A IEEE 802.3at Type 2 100 m in total AC+DC enhanced Power Injector (90W) None 100 m N/A IEEE 802.3at Type 2 100 m in total

-48 V DC power injector None 100 m N/A IEEE 802.3at Type 2 100 m in total CMM4 with 56 V supply None 100 m N/A IEEE 802.3at Type 2 Not supported IEEE802.3at compliant supply None 100 m N/A IEEE 802.3at Type 2 Not supported Note The Ethernet connectivity for CMM4 requires the part Ethernet cable adapter for CMM4 N000045L001A. Page 2-25 Chapter 2: System hardware Cabling and lightning protection Outdoor copper Cat5e Ethernet cable Outdoor Cat5e cable is used for all connections that terminate outside the building. For example, connections between the ODU, surge suppressors (if installed), UGPS receivers (if installed) and the power supply injector. This is known as a drop cable (Figure 18). The following practices are essential to the reliability and longevity of cabled connections:

Use only shielded cables and connectors to resist interference and corrosion. For vertical runs, provide cable support and strain relief. Include a 2 ft (0.6 m) service loop on each end of the cable to allow for thermal expansion and contraction and to facilitate terminating the cable again when needed. Include a drip loop to shed water so that most of the water does not reach the connector at the device. Properly crimp all connectors. Use dielectric grease on all connectors to resist corrosion. Order Superior Essex type BBDGe cable from Cambium Networks (Table 32). Other lengths of this cable are available from Superior Essex. Figure 18 Outdoor drop cable Table 32 Drop cable part numbers Cambium description Cambium part number 1000 ft Reel Outdoor Copper Clad CAT5E 328 ft (100 m) Reel Outdoor Copper Clad CAT5E WB3175 WB3176 Page 2-26 Chapter 2: System hardware Cabling and lightning protection Main Ethernet port The PoE cable pinout diagram for Main port is given below. Table 33 Main port PoE cable pinout RJ45 pin Interface Ethernet description 1 2 3 6 5 4 7 8 1000 BaseT Ethernet with PoE In

+TxRx0 TxRx0

+TxRx1 TxRx1 TxRx2

+TxRx2

+TxRx3 TxRx3 PoE input description

+Ve or -Ve

+Ve or Ve

+Ve or Ve

+Ve or Ve Note The PoE input on the Main port accepts any polarity as long as there is at least one pair at +Ve and at least one at Ve. Aux port Table 34 Aux port PoE cable pinout RJ45 pin Interface Signal description PoE output description 1 2 3 6 5 4 7 8 100 BaseT Ethernet with PoE Out (see note below)

+TxRx0 TxRx0

+TxRx1 TxRx1 GPS power out, Alignment tone out, GPS data out GPS and alignment tone GPS data in GPS 0v GPS Sync in

-Ve

+Ve N/A Page 2-27 Chapter 2: System hardware Cabling and lightning protection Note Only alignment and sync functionalities are supported on the Aux port in current release 14.1.1. Aux port to alignment tone headset wiring A standard 32 ohms stereo headset can be connected to the AUX port to use the audio alignment tool. The diagram of the adapter is provided in Figure 19. The recommended values for both resistors are 220 ohm, 0.25W. Different resistor value can be used to optimize the level of the audio signal depending on the headset characteristics and the level of ambient noise Figure 19 Alignment Tone Cable

#8 Pin 7 Pin 4 Table 35 Aux port PoE cable pinout Resistors 220 220 Left / tip Right / ring Sleeve /Common RJ45 pin

(AUX port) 5 7 Signal description Serial component Jack socket

(to jack plug of headset) Alignment tone out 220 ohms resistor 220 ohm resistor GPS 0v None Ring Tip Sleeve Alternatively, a readymade headset adapter can be ordered from Best-Tronics

(http://btpa.com/Cambium-Products/) with the following part number:

Table 36 Alignment tone adapter third party product details Reference Product description BT-1277 Headset alignment cable for the Cambium Networks PMP450i and PTP450i product lines Page 2-28 Chapter 2: System hardware Cabling and lightning protection Cable grounding kit Copper drop cable shields must be bonded to the grounding system in order to prevent lightning-

strike arcing (resulting in fire risk and damage to equipment). One grounding kit (Figure 20) is required for each grounding point on the PSU. Order cable grounding kits from Cambium Networks (Table 37). Caution To provide adequate protection, all grounding cables must be a minimum size of 10 mm2 csa (8AWG), preferably 16 mm2 csa (6AWG), or 25 mm2 csa (4AWG). Figure 20 Cable grounding kit Table 37 Cable grounding kit part numbers Cambium description Cambium part number Cable Grounding Kits For 1/4" And 3/8" Cable 01010419001 Lightning protection unit (LPU) and grounding kit PMP/PTP 450i LPUs provide transient voltage surge suppression for ODU installations. Each PSU requires two LPUs, one near the ODU and the other near the linked device, usually at the building entry point (Table 38). Page 2-29 Chapter 2: System hardware Cabling and lightning protection Table 38 LPU and grounding kit contents Lightning protection units (LPUs) ODU to top LPU drop cable (600 mm) LPU grounding point nuts and washers EMC strain relief cable glands U-bolts, nuts and washers for mounting LPUs ODU to top LPU ground cable (M6-M6) Bottom LPU ground cable (M6-M10) ODU to ground cable (M6-M10 One LPU and grounding kit (Table 38) is required for the PSU drop cable connection to the ODU. If the ODU is to be connected to an auxiliary device, one additional LPU and grounding kit is required for the Aux drop cable. Order the kits from Cambium Networks (Table 39). Table 39 LPU and grounding kit part number Cambium description Cambium part number PMP/PTP 450i LPU and Grounding Kit (One Kit Per End) C000065L007 Page 2-30 Chapter 2: System hardware Antennas and antenna cabling Antennas and antenna cabling Antenna requirements Each connectorized ODU requires one external antenna (normally dual-polar). For connectorized units operating in the USA or Canada 900 MHz, 4.9 GHz, 5.1 GHz, 5.2 GHz, 5.4 GHz or 5.8 GHz bands, choose external antennas which are recommended by Cambium Networks. Do not install any other antennas. Supported external AP antennas The recommended AP external antennas are listed in Table 40. Table 40 List of AP external antennas Cambium description Cambium part number 900 MHz 13 dBi 65 degree Sector Antenna (Dual Slant) N009045D001A 5 GHz Horizontal and Vertical Polarization Antenna for 90 Degree 85009324001 Sector 5 GHz Horizontal and Vertical Polarization Antenna for 60 Degree 85009325001 Sector Note LINKPlanner, Cambium Networks planning tool, contains an up-to-date, exhaustive list of antennas that can be used with Cambium Products. Supported external BH/SM antenna The recommended PTP 450i BH or PMP 450/450i SM external antenna is listed in Table 41. Table 41 PTP 450i BH or PMP 450/450i SM external antenna Cambium description Cambium part number 900 MHz 12 dBi gain directional antenna (Dual Slant) N009045D003A Page 2-31 Chapter 2: System hardware Antennas and antenna cabling RF cable and connectors RF cable of generic type LMR-400 is required for connecting the ODU to the antenna. N type male connectors are required for connecting the RF cables to the connectorized ODU. Two connectors are required per ODU. Use weatherproof connectors, preferably ones that are supplied with adhesive lined heat shrink sleeves that are fitted over the interface between the cable and connector. Order CNT-400 RF cable and N type male connectors from Cambium Networks (Table 42). Table 42 RF cable and connector part numbers Cambium description Cambium part number 50 Ohm Braided Coaxial Cable - 75 meter 50 Ohm Braided Coaxial Cable - 500 meter 30010194001 30010195001 RF Connector, N, Male, Straight for CNT-400 Cable 09010091001 Antenna accessories Connectorized ODUs require the following additional components:

Cable grounding kits: Order one cable grounding kit for each grounding point on the antenna cables. Refer to Lightning protection unit (LPU) and grounding kit on 2-29 Self-amalgamating and PVC tape: Order these items to weatherproof the RF connectors Lightning arrestors: When the connectorized ODU is mounted indoors, lightning arrestors (not LPUs) are required for protecting the antenna RF cables at building entry. One arrestor is required per antenna cable. One example of a compatible lightning arrestor is the Polyphaser LSXL-ME or LSXL (not supplied by Cambium Networks). RJ45 connectors and spare glands RJ45 connectors are required for plugging Cat5e cables into ODUs, LPUs, PoEs and other devices. Order RJ45 connectors and crimp tool from Cambium Networks (Table 43). The ODU is supplied with one environmental sealing gland for the drop cable. The cable clamping range for gland is 5 mm to 9 mm. Page 2-32 Chapter 2: System hardware Antennas and antenna cabling Figure 21 Cable gland (part number #N000065L033) Table 43 RJ45 connector and spare gland part numbers Cambium description Cambium part number Tyco/AMP, Mod Plug RJ45, 100 pack Tyco/AMP Crimp Tool WB3177 WB3211 RJ-45 Spare Grounding Gland - PG16 size (Qty. 10) N000065L033 Page 2-33 Chapter 2: System hardware GPS synchronization GPS synchronization GPS synchronization description Cambium offers GPS synchronization to limit the networks own self-interference. The Cluster Management CMM provides Global Positioning System (GPS) synchronization to the Access Point

(AP) and all associated Subscriber Modules (SM). Network operators have a choice of UGPS and CMM solutions to select the option that works best for the environment. Universal GPS (uGPS) The uGPS provides network synchronization for smaller networks where a CMM may not be cost effective. The uGPS provides synchronization for one or two modules so that even remote areas at the edge of the network can operate with synchronization for improved performance. The uGPS works with all Cambium PMP radios. The uGPS has a small footprint and is easy to deploy. Figure 22 uGPS Note PMP 450 and 450i APs can power up a uGPS via the Aux/Timing port. CMM5 The Cluster Management Module (CMM) 5 supports following features:

12 + 24 port versions. DC input. Midspan or rack mount. SFP ports Page 2-34 Chapter 2: System hardware GPS synchronization CMM4 (Rack Mount) The Cluster Management Module (CMM) is the heart of the Cambium systems synchronization capability, which allows network operators to reuse frequencies and add capacity while ensuring consistency in the quality of service to customers. For operators who prefer indoor CMM mounting, Cambium offers the Rack-Mounted Cluster Management Module 4. The unit is designed to be mounted onto a standard 19-inch telecommunications rack and to allow the Cambium CMM4 to be co-located with other telecommunications equipment. Figure 23 CMM4 (Rack Mount) The CMM4 has two DC power inputs, one 29 V and one 56V. It can be used to power and synchronize both 29V legacy products such as the PMP 450 and 56V products such as the PMP 450i simultaneously. If the 29V legacy products are connected to the CMM4, a 29V power supply needs to be connected. If PMP/PTP 450/450i are connected to the CMM4, a 56V power supply needs to be connected.. The CMM4 supports having two of the 56V and two of the 24V supplies for redundancy. Warning PMP 450i requires different wiring between the CMM4 and device. If a PMP450 is replaced by a PMP 450i and the existing drop cable needs to be re-used, the adapter

"CMM4 56V power adapter, #N000045L001A" must be used between the CMM4 and the existing drop cable. Note If only a 56V supply is used, it can not power up 29V radios. Page 2-35 Chapter 2: System hardware GPS synchronization Figure 24 CMM4 56V power adapter (dongle) CMM4 56V power adapter cable pinout Figure 25 CMM4 power adapter cabling diagram J1 1 5 7 8 RJ45 Plug Shield J2 1 5 7 8 RJ45 Jack Page 2-36 Chapter 2: System hardware GPS synchronization Table 44 CMM4 power adapter cable pinout Plug J1 pin Jack J2 pin 1 2 3 4 5 6 7 8 1 2 3 4 7 6 5 8 Screen Screen Note Pins 5 and 7 are flipped. Page 2-37 Chapter 2: System hardware GPS synchronization CMM4 (Cabinet with switch) Designed to deliver consistent and reliable wireless broadband service, the PMP/PTP system gracefully scales to support large deployments. The cluster management module is the heart of the systems synchronization capability which allows network operators to re-use frequencies and add capacity while ensuring consistency in the quality of service to customers. As a result, subscribers can experience carrier-grade service even at the outer edge of the network. Figure 26 CMM4 (Cabinet with switch) CMM4 (Cabinet without switch) This CMM includes all of the functionality listed above but there is no switch. This provides the network operator the flexibility to use the switch of their choice with the power and synchronization capabilities of the CMM4. CMM3/CMMmicro The CMM3 or CMMmicro (Cluster Management Module micro) provides power, GPS timing, and networking connections for an AP cluster. The CMM3 is configurable through a web interface. Page 2-38 Chapter 2: System hardware GPS synchronization The CMM3 contains an 8-port managed switch that supports Power over Ethernet (PoE this is cambium PoE, not the standard PoE) on each port and connects any combination of APs, BHMs, BHSs, or Ethernet feed. The Cambium fixed wireless broadband IP networks PoE differs from IEEE Standard 803.3af PoE, and the two should not be intermixed. The CMM3 can auto-negotiate speed to match inputs that are either 100Base-TX or 10Base-T, and either full duplex or half duplex, where the connected device is set to auto-negotiate. Alternatively, these parameters are settable. A CMM3 requires only one cable, terminating in an RJ-45 connector, for each connected module to distribute Ethernet signaling. power to as many as 8 co-located modulesAPs, BHMs, or BHSs. Through a browser interface to the managed switch, ports can be powered or not. sync to APs and BHMs. The CMM3 receives 1-pulse per second timing information from Global Positioning System (GPS) satellites through an antenna (included) and passes the timing pulse embedded in the 24-V power to the connected modules. GPS status information is available at the CMM3, however CMM3 provides time and date information to BHMs and APs if both the CMMmicro is operating on CMMmicro Release 2.1 or later and the AP/BHM is operating on System Release 4.2 or later. See Configuring time settings on Page 7-87. CMM3 does not provide time and date information to BHMs and APs if either the CMM3 is operating on a release earlier than CMMmicro Release 2.1 or the AP/BHM is operating on a release earlier than System Release 4.2. A CMM3/CMMicro is shown in Figure 27 and Figure 28. Figure 27 CMM3 Figure 28 Pole mounted CMM3 Note A CMM3 can not be used to power up a 450i radio. Page 2-39 Chapter 2: System hardware Installing a GPS receiver Installing a GPS receiver To install a GPS receiver as the timing reference source, use the following procedures:

Mounting the GPS receiver on page 2-41 Cabling the GPS Antenna on page 2-42 Installing and connecting the GPS LPU on page 2-42 Caution Prior to power-up of equipment, ensure that all cables are connected to the correct interfaces of the CMM4 unit and the UGPS receiver module. Failure to do so may result in damage to the equipment. GPS receiver location Mount the GPS receiver at a location that meets the following requirements:

It must be possible to protect the installation as described in Grounding and lightning protection on page 3-8. It must have an un-interrupted view of at least half of the southern (resp. northern) sky in the northern (resp. southern) hemisphere. For a receiver mounted on a wall there must be no other significant obstructions in the view of the sky. It must be mounted at least 1 m (3 ft), preferably 2 m (6 ft), away from other GPS receiving equipment. It must not be sited in the field of radiation of co-located radio communications equipment and should be positioned at a distance of at least 3 m (10 ft) away. Mount the UGPS receiver on the wall of the equipment building if there is a suitable location on the wall that can meet these requirements. Mounting the GPS receiver module on the equipment building If mounting the GPS receiver on the equipment building (Figure 33), select a position on the wall that meets the following requirements:

It must be below the roof height of the equipment building or below the height of any roof-

mounted equipment (such as air conditioning plant). It must be below the lightning air terminals. It must not project more than 600mm (24 inches) from the wall of the building. If these requirements cannot all be met, then the module must be mounted on a metal tower or mast. Page 2-40 Chapter 2: System hardware Installing a GPS receiver Mounting the GPS receiver module on a metal tower or mast If mounting the GPS receiver module on a metal tower or mast (Figure 34), select a position that meets the following requirements:

It must not be mounted any higher than is necessary to receive an adequate signal from four GPS satellites. It must be protected by a nearby lightning air terminal that projects farther out from the tower than the GPS receiver module. Mounting the GPS receiver Mount the UGPS receiver (following manufacturers instructions) upon either an external wall

(Figure 33) or a metal tower or mast (Figure 34). Figure 29 GPS antenna mounting Page 2-41 Chapter 2: System hardware Installing a GPS receiver Procedure 1 Mounting the GPS receiver 1 Ensure that the mounting position has an unobstructed view of the sky to 20 above the horizon. is not the highest object at the site. (The GPS antenna does not need to be particularly high on a site, which would give it more exposure to lightning. It just needs to have an unobstructed view of the sky.) is not further than 100 feet (30.4 meters) of cable from the CMM. 2 Select a pole that has an outside diameter of 1.25 to 1.5 inches (3 to 4 cm) to which the GPS antenna bracket can be mounted. 3 4 5 6 7 Place the U-bolts (provided) around the pole as shown in Figure 28.. Slide the GPS antenna bracket onto the U-bolts. Slide the ring washers (provided) onto the U-bolts. Slide the lock washers (provided) onto the U-bolts. Use the nuts (provided) to securely fasten the bracket to the U-bolts. Please refer to the PMP Synchronization Solutions User Guide located on the Cambium website

(http://www.cambiumnetworks.com/resources/pmp-synchronization-solutions ). Cabling the GPS Antenna Connect the GPS coax cable to the female N-connector on the GPS antenna. Please refer to the PMP Synchronization Solutions User Guide located on the Cambium website

(http://www.cambiumnetworks.com/resources/pmp-synchronization-solutions ). Installing and connecting the GPS LPU Install and ground the GPS drop cable LPU at the building (or cabinet) entry point, as described in Install the bottom LPU on page 6-19. Page 2-42 Chapter 2: System hardware Ordering the components Ordering the components This section describes how to select components for PMP 450m, PMP/PTP 450i and PMP/PTP 450 Greenfield network or 450m/450i network migration. It specifies Cambium part numbers for PMP/PTP 450 platform components. Order PMP 450m, PMP/PTP 450i and PMP/PTP 450 Series products from Cambium Networks. PMP 450m Table 45 PMP 450m ODU part numbers Cambium description Cambium part number PMP 450m AP (Access Point) 5 GHz PMP 450m Integrated Access Point, 90 Degree (ROW) C050045A101A 5 GHz PMP 450m Integrated Access Point, 90 Degree (FCC) C050045A102A 5 GHz PMP 450m Integrated Access Point, 90 Degree (EU) C050045A103A 5 GHz PMP 450m Integrated Access Point, 90 Degree (DES Only) C050045A104A 5 GHz PMP 450m Integrated Access Point, 90 Degree (IC) C050045A105A PMP 450i Table 46 PMP 450i ODU part numbers Cambium description PMP 450i AP (Access Point) 900 MHz PMP 450i Connectorized Access Point 5 GHz PMP 450i Connectorized Access Point (RoW) 5 GHz PMP 450i Connectorized Access Point (FCC) 5 GHz PMP 450i Connectorized Access Point (EU) Cambium part number C009045A001A C050045A001A C050045A002A C050045A003A 5 GHz PMP 450i Connectorized Access Point (DES Only) C050045A004A 5 GHz PMP 450i Connectorized Access Point (IC) C050045A015A 5 GHz PMP 450i AP, Integrated 90sector antenna (RoW) C050045A005A 5 GHz PMP 450i AP, Integrated 90sector antenna (FCC) C050045A006A 5 GHz PMP 450i Integrated Access Point, 90 degree (EU) C050045A007A Page 2-43 Chapter 2: System hardware Ordering the components Cambium description Cambium part number 5 GHz PMP 450i AP, Integrated 90sector antenna (DES only) C050045A008A 5 GHz PMP 450i AP, Integrated 90sector antenna (IC) C050045A016A PMP 450i SM (Subscriber Module) 5 GHz PMP 450i Connectorized Subscriber Module 5 GHz PMP 450i SM, Integrated High Gain Antenna C050045C001A C050045C002A Note The 450i SM does not have license keys. PTP 450i Table 47 PTP 450i ODU part numbers Cambium description Cambium part number 5 GHz PTP 450i END, Connectorized (RoW) C050045B001A 5 GHz PTP 450i END, Integrated High Gain Antenna (RoW) C050045B002A 5 GHz PTP 450i END, Connectorized (FCC) 5 GHz PTP 450i END, Connectorized (EU) 5 GHz PTP 450i END, Connectorized (DES only) 5 GHz PTP 450i END, Connectorized (IC) C050045B003A C050045B005A C050045B007A C050045B015A 5 GHz PTP 450i END, Integrated High Gain Antenna (FCC) C050045B004A 5 GHz PTP 450i END, Integrated High Gain Antenna (EU) C050045B006A 5 GHz PTP 450i END, Integrated High Gain Antenna (DES only) C050045B008A 5 GHz PTP 450i END, Integrated High Gain Antenna (IC) C050045B016A Ethernet cable adapter for CMM4 N000045L001A PMP 450 Table 48 PMP 450 ODU part numbers Cambium description PMP 450 AP (Access Point) Cambium part number 2.4 GHz PMP 450 Connectorized Access Point C024045A001A Page 2-44 Chapter 2: System hardware Ordering the components Cambium description Cambium part number 2.4 GHz PMP 450 Connectorized Access Point (DES) 3.5 GHz PMP 450 Connectorized Access Point 3.5 GHz PMP 450 Connectorized Access Point (DES) 3.6 GHz PMP 450 Connectorized Access Point 3.6 GHz PMP 450 Connectorized Access Point (DES) 5 GHz PMP 450 Connectorized Access Point C024045A003A C035045A001A C035045A003A C036045A001A C036045A003A C054045A001A 5 GHz PMP 450 Connectorized Access Point (US only) C054045A002A 5 GHz PMP 450 Connectorized Access Point (DES) C054045A003A PMP 450 AP Lite 2.4 GHz PMP 450 Connectorized Access Point - Lite C024045A011A 3.3-3.6 GHz PMP 450 Connectorized Access Point - Lite C035045A011A 3.55-3.8 GHz PMP 450 Connectorized Access Point - Lite C036045A011A 5 GHz PMP 450 Connectorized Access Point - Lite C054045A011A 5 GHz PMP 450 Connectorized Access Point (FCC) - Lite C054045A012A PMP 450 SM (Subscriber Module) 900 MHz PMP 450 Connectorized Subscriber Module C009045C001A 2.4 GHz PMP 450 Subscriber Module, 4 Mbps 2.4 GHz PMP 450 Subscriber Module, 10 Mbps 2.4 GHz PMP 450 Subscriber Module, 20 Mbps 2.4 GHz PMP 450 Subscriber Module, Uncapped C024045C001A C024045C002A C024045C003A C024045C004A 2.4 GHz PMP 450 Connectorized Subscriber Module, 4 Mbps C024045C005A 2.4 GHz PMP 450 Connectorized Subscriber Module, 10 Mbps C024045C006A 2.4 GHz PMP 450 Connectorized Subscriber Module, 20 Mbps C024045C007A 2.4 GHz PMP 450 Connectorized Subscriber Module, Uncapped C024045C008A 3.5 GHz PMP 450 High Gain Directional Integrated Subscriber C035045C014A 3.5 GHz PMP 450 Subscriber Module, 4 Mbps 3.5 GHz PMP 450 Subscriber Module, 10 Mbps 3.5 GHz PMP 450 Subscriber Module, 20 Mbps 3.5 GHz PMP 450 Subscriber Module, Uncapped C035045C001A C035045C002A C035045C003A C035045C004A 3.5 GHz PMP 450 Connectorized Subscriber Module, 4 Mbps C035045C005A Page 2-45 Chapter 2: System hardware Ordering the components Cambium description Cambium part number 3.5 GHz PMP 450 Connectorized Subscriber Module, 10 Mbps C035045C006A 3.5 GHz PMP 450 Connectorized Subscriber Module, 20 Mbps C035045C007A 3.5 GHz PMP 450 Connectorized Subscriber Module, Uncapped C035045C008A 3.6 GHz PMP 450 High Gain Directional Integrated Subscriber C036045C014A 3.6 GHz PMP 450 Subscriber Module, 4 Mbps 3.6 GHz PMP 450 Subscriber Module, 10 Mbps 3.6 GHz PMP 450 Subscriber Module, 20 Mbps 3.6 GHz PMP 450 Subscriber Module, Uncapped C036045C001A C036045C002A C036045C003A C036045C004A 3.6 GHz PMP 450 Connectorized Subscriber Module, 4 Mbps C036045C005A 3.6 GHz PMP 450 Connectorized Subscriber Module, 10 Mbps C036045C006A 3.6 GHz PMP 450 Connectorized Subscriber Module, 20 Mbps C036045C007A 3.6 GHz PMP 450 Connectorized Subscriber Module, Uncapped C036045C008A 5 GHz PMP 450 Connectorized Subscriber Module, 4 Mbps C054045C005A 5 GHz PMP 450 Connectorized Subscriber Module, 10 Mbps C054045C006A 5 GHz PMP 450 Connectorized Subscriber Module, 20 Mbps C054045C007A 5 GHz PMP 450 Connectorized Subscriber Module, Uncapped C054045C008A 5 GHz PMP 450 Integrated Subscriber Module, 4 Mbps C054045C001B 5 GHz PMP 450 Integrated Subscriber Module, 10 Mbps C054045C002B 5 GHz PMP 450 Integrated Subscriber Module, 20 Mbps C054045C003B 5 GHz PMP 450 Integrated Subscriber Module, Uncapped C054045C004B 5 GHz PMP 450 Connectorized Subscriber Module, 4 Mbps C054045C005B 5 GHz PMP 450 Connectorized Subscriber Module, 10 Mbps C054045C006B 5 GHz PMP 450 Connectorized Subscriber Module, 20 Mbps C054045C007B 5 GHz PMP 450 Connectorized Subscriber Module, Uncapped C054045C008B 5 GHz PMP 450d Subscriber Module, 20 Mbps 4-pack C054045H013B 5 GHz PMP 450d Subscriber Module, Uncapped 4-pack C054045H014B Page 2-46 Chapter 2: System hardware Ordering the components PTP 450 Table 49 PTP 450 ODU part numbers Cambium description Cambium part number PTP 450 3.5 GHz END Integrated PTP 450 3.5 GHz END Connectorized PTP 450 3.5 GHz END Integrated DES Only PTP 450 3.5 GHz END Connectorized DES Only PTP 450 3.65 GHz END Integrated PTP 450 3.65 GHz END Connectorized PTP 450 3.65 GHz END Integrated DES Only PTP 450 3.65 GHz END Connectorized DES Only PTP 450 5 GHz END Integrated (ROW) PTP 450 5 GHz END Connectorized (ROW) PTP 450 5 GHz END Integrated (ROW) DES Only C035045B001A C035045B002A C035045B003A C035045B004A C036045B001A C036045B002A C036045B003A C036045B004A C054045B001A C054045B002A C054045B003A PTP 450 5 GHz END Connectorized (ROW) DES Only C054045B004A PTP 450 5 GHz END Integrated (FCC) PTP 450 5 GHz END Connectorized (FCC) C054045B005A C054045B006A PMP/PTP 450/450i Accessories Table 50 PMP/PTP 450/450i Accessories Cambium description Cambium part number PMP 450 AP Antenna Options 900 MHz 65 degree Sector Antenna (Dual Slant) N009045D001A 900 MHz 12 dBi gain directional antenna (Dual Slant) N009045D003A 2.4 GHz Dual Slant Antenna for 60 Degree Sector C024045D601A 3.5 GHz and 3.6 GHz Dual Slant Antenna for 90 Degree Sector C030045D901A 5 GHz Antenna for 60 Degree Sector 5 GHz Antenna for 90 Degree Sector N-type to N-type cable (16 inch length) Power supplies 85009325001 85009324001 30009406002 Page 2-47 Chapter 2: System hardware Ordering the components Cambium description Cambium part number Power supply, 60 W, 56 V with Gbps support AC+DC Enhanced Power Injector Line Cord, Fig 8 US Line Cord, Fig 8 UK Line Cord, Fig 8 EU N000065L001B C000065L002B N000065L003A N000065L004A N000065L005A Power over Ethernet midspan, 60 W, -48 VDC Input N000000L036A Power Supply, 30 W, 56 V Gbps support Gigabit Enet Capable Power Supply - 30VDC, 15W Cable, UL Power Supply Cord Set, US Cable, UL Power Supply Cord Set, EU Cable, UL Power Supply Cord Set, UK AP Optional Equipment CMM MICRO (Outdoor Enclosure) (450 only) CMM4 W/RUGGEDIZED Switch and GPS CMM4 NO Switch CMM4 Rack Mount Assembly Ethernet cable adapter for CMM4 Universal GPS Module RJ-45 Gland Spare PG16 style (QTY 10) Blanking Plug Pack (Qty 10) SM Optional Equipment Power Supply, 30 W, 56 V Gbps support Gigabit Enet Capable Power Supply 30 VDC, 15 W Cable, UL Power Supply Cord Set, US Cable, UL Power Supply Cord Set, EU Cable, UL Power Supply Cord Set, UK 53CM Offset, Reflector Dish Kit, 4PK Accessories Surge Suppressor (30 VDC) N000000L034A N000900L001A N000900L007A N000900L008A N000900L009A 1070CKHH 1090CKHH 1091HH 1092HH N000045L001A 1096H N000065L033A N000065L036A N000000L034A N000900L001A N000900L007A N000900L008A N000900L009A HK2022A 600SSH Gigabit Surge Suppressor (56 VDC) C000000L033A Page 2-48 Chapter 2: System hardware Ordering the components Cambium description Cambium part number LPU and Grounding Kit (1 kit per ODU) 50 Ohm Braided Coaxial Cable - 75 meter 50 Ohm Braided Coaxial Cable - 500 meter RF Connector, N, Male, Straight for CNT-400 Cable Mounting brackets Tilt Bracket Assembly Mounting Bracket (Integrated) Mounting Bracket (Connectorized) Upgrade Keys PMP 450 4 To 10 Mbps Upgrade Key PMP 450 4 To 20 Mbps Upgrade Key PMP 450 4 To Uncapped Upgrade Key PMP 450 10 To 20 Mbps Upgrade Key PMP 450 10 To Uncapped MBPS Upgrade Key PMP 450 20 To Uncapped MBPS Upgrade Key PMP 450 Lite AP to Full AP Upgrade Key Extended Warranty C000065L007A 30010194001 30010195001 09010091001 N000045L002A N000065L031A N000065L032A C000045K002A C000045K003A C000045K004A C000045K005A C000045K006A C000045K007A C000045K008A PMP 450 platform AP Extended Warranty, 1 Additional Year SG00TS4009A PMP 450 platform AP Extended Warranty, 2 Additional Years SG00TS4017A PMP 450 platform AP Extended Warranty, 4 Additional Years SG00TS4025A PMP 450 platform SM Extended Warranty, 1 Additional Year SG00TS4010A PMP 450 platform SM Extended Warranty, 2 Additional Years SG00TS4018A PMP 450 platform SM Extended Warranty, 4 Additional Years SG00TS4026A Page 2-49 Chapter 3: System planning This chapter provides information to help the user to plan a PMP/PTP 450 platform link. The following topics are described in this chapter:

Typical deployment on page 3-2 contains diagrams illustrating typical PMP/PTP 450 platform site deployments. Site planning on page 3-7 describes factors to be considered when planning the proposed link end sites, including grounding, lightning protection and equipment location. Radio Frequency planning on page 3-16 describes how to plan PMP/PTP 450 platform links to conform to the regulatory restrictions that apply in the country of operation. Link planning on page 3-21 describes factors to be taken into account when planning links, such as range, path loss and throughput. Planning for connectorized units on page 3-24 describes factors to be taken into account when planning to use connectorized ODUs with external antennas in PMP/PTP 450 platform links. Data network planning on page 3-26 describes factors to be considered when planning PMP/PTP 450 platform data networks. Network management planning on page 3-34 describes how to plan for PMP/PTP 450 platform links to be managed remotely using SNMP. Security planning on page 3-35 describes how to plan for PMP/PTP 450 platform links to operate in secure mode. Page 3-1 Chapter 3: System planning Typical deployment Typical deployment This section contains diagrams illustrating typical PMP/PTP 450 platform site deployments. ODU with PoE interface to PSU In the basic configuration, there is only one Ethernet interface, a copper Cat5e power over Ethernet

(POE) from the PSU to the ODU (PSU port), as shown in the following diagrams: mast or tower installation (Figure 30 ), wall installation (Figure 31) and roof installation (Figure 32). Figure 30 Mast or tower installation Page 3-2 ODUAC supplyPSUNetworkequipmentODU ground cablesPower over Ethernet CAT5e cable (gel-filled, shielded with copper-plated steel)Network CAT5e cableSite grounding systemBottom LPUFirst point of contact between drop cable and towerTower ground barGround ringIntermediate ground cable(s) as requiredBuilding entryEquipment building or cabinet Chapter 3: System planning Typical deployment Figure 31 Wall installation Page 3-3 ODUPSUNetworkequipmentODU ground cablesSite grounding systemBottom LPUGround ringFirst point of contact between drop cable and wallBuilding entryPower over Ethernet CAT5e cable (gel-filled, shielded with copper-plated steel)Network Cat5e cableAC supply Chapter 3: System planning Typical deployment Figure 32 Roof installation Page 3-4 Air terminals (finials)Tower grounding conductorBuilding ground ringAC serviceEquipment roomODUODU ground cablesNetwork CAT5e cableSite grounding systemAC supplyPSUNetworkequipmentBottom LPUBuilding entry pointDrop cable inside buildingEquipment room entry pointPower over Ethernet CAT5e cable (gel-filled, shielded with copper-plated steel) Chapter 3: System planning Typical deployment Figure 33 GPS receiver wall installation Note The CMM3 or CMM4 can be used for PMP/PTP 450 platform. Page 3-5 PSUNetworkequipmentODU/ GPSGround cablesSite grounding systemDrop cable to top LPU and ODUGround ringPower over Ethernet CAT5e cable (gel-filled, shielded with copper-plated steel)Network Cat5e cableAC supplyCMM 4GPS receiverAC+DC Power InjectorFirst point of contact between drop cable and wall Chapter 3: System planning Typical deployment Figure 34 GPS receiver tower or mast installation Note The CMM3 or CMM4 can be used for PMP/PTP 450 platform. Page 3-6 ODU/GPS ground cablesPower over Ethernet CAT5e cable (gel-filled, shielded with copper-plated steel)Network CAT5e cableSite grounding systemTower ground barGround ringEquipment building or cabinetPSUNetworkequipmentAC supplyCMM 4Power InjectorDrop cable to top LPU and ODUGPS receiverFirst point of contact between drop cable and towerIntermediate ground cable(s) as required Chapter 3: System planning Site planning Site planning This section describes factors to be considered when choosing sites for PMP or PTP radios, power supplies, CMM4 (if applicable) and UGPS (if applicable). Site selection for PMP/PTP radios When selecting a site for the ODU, consider the following factors:

Height and location to ensure that people are kept away from the antenna; see Calculated distances and power compliance margins on page 4-24. Height and location to achieve the best radio path. Indoor location where power supply LED indicators accessible and cable length should not exceed maximum recommended length; see Power supply site selection Ability to meet the requirements specified in Grounding and lightning protection on page 3-8. Aesthetics and planning permission issues. Cable lengths; see ODU interfaces on page 2-23. The effect of strong winds on the installation; see ODU wind loading on page 3-11. Calculated distances and power compliance margin The calculated minimum separation distances, recommended distances and resulting margins for each frequency band and antenna combination. These are conservative distances that include compliance margins. At these and greater separation distances, the power density from the RF field is below generally accepted limits for the general population. PMP/PTP 450 platform equipment adheres to all applicable EIRP limits for transmit power when operating in MIMO mode. Separation distances and compliance margins include compensation for both transmitters. Page 3-7 Chapter 3: System planning Site planning Power supply site selection When selecting a site for the ODU power supply, consider the following factors:

Indoor location with no possibility of condensation, flooding or high humidity. Availability of a mains electricity supply. Located in an environment where it is not likely to exceed its operational temperature rating, allowing for natural convection cooling. Accessibility for viewing status indicator LED and connecting Ethernet cables. Cable lengths; see ODU interfaces on page 2-23. Maximum cable lengths When installing PMP/PTP 450i Series ODU, the maximum permitted length of the shielded copper Ethernet interface cable is 330 feet (100m) from AP/BHM/SM/BHS to their associated power supplies or CMM4. Grounding and lightning protection Warning Electro-magnetic discharge (lightning) damage is not covered under warranty. The recommendations in this guide, when followed correctly, give the user the best protection from the harmful effects of EMD. However 100% protection is neither implied nor possible. Structures, equipment and people must be protected against power surges (typically caused by lightning) by conducting the surge current to ground via a separate preferential solid path. The actual degree of protection required depends on local conditions and applicable local regulations. To adequately protect a PMP/PTP 450 platform installation, both ground bonding and transient voltage surge suppression are required. Full details of lightning protection methods and requirements can be found in the international standards IEC 61024-1 and IEC 61312-1, the U.S. National Electric Code ANSI/NFPA No. 70-1984 or section 54 of the Canadian Electric Code. Warning International and national standards take precedence over the requirements in this guide. Page 3-8 Chapter 3: System planning Site planning Lightning protection zones Use the rolling sphere method (Figure 35) to determine where it is safe to mount equipment. An imaginary sphere, typically 50 meters in radius, is rolled over the structure. Where the sphere rests against the ground and a strike termination device (such as a finial or ground bar), all the space under the sphere is considered to be in the zone of protection (Zone B). Similarly, where the sphere rests on two finials, the space under the sphere is considered to be in the zone of protection. Figure 35 Rolling sphere method to determine the lightning protection zones Zone A: In this zone a direct lightning strike is possible. Do not mount equipment in this zone. Zone B: In this zone, direct EMD (lightning) effects are still possible, but mounting in this zone significantly reduces the possibility of a direct strike. Mount equipment in this zone. Warning Never mount equipment in Zone A. Mounting in Zone A may put equipment, structures and life at risk. Page 3-9 Chapter 3: System planning Site planning Site grounding system Confirm that the site has a correctly installed grounding system on a common ground ring with access points for grounding PMP/PTP 450 platform equipment. If the outdoor equipment is to be installed on the roof of a high building (Figure 32), confirm that the following additional requirements are met:

A grounding conductor is installed around the roof perimeter to form the main roof perimeter lightning protection ring. Air terminals are installed along the length of the main roof perimeter lightning protection ring, typically every 6.1m (20ft). The main roof perimeter lightning protection ring contains at least two down conductors connected to the grounding electrode system. The down conductors should be physically separated from one another, as far as practical. ODU and external antenna location Find a location for the ODU (and external antenna for connectorized units) that meets the following requirements:

The equipment is high enough to achieve the best radio path. People can be kept a safe distance away from the equipment when it is radiating. The safe separation distances are defined in Calculated distances and power compliance margins on page 4-24. The equipment is lower than the top of the supporting structure (tower, mast or building) or its lightning air terminal. If the ODU is connectorized, select a mounting position that gives it maximum protection from the elements, but still allows easy access for connecting and weatherproofing the cables. To minimize cable losses, select a position where the antenna cable lengths can be minimized. If diverse or two external antennas are being deployed, it is not necessary to mount the ODU at the midpoint of the antennas. ODU ambient temperature limits Select a location where the ODU can operate within safe ambient temperature limits. The following points need to be considered while selecting a location for the ODU:

The ODU must be mounted in a Restricted Access Location (as defined in EN 60950-1) if the operating ambient temperature may exceed 40C, including solar radiation. If the ambient temperature never exceeds 40C, the temperature of the external metal case parts of the ODU will not exceed the touch temperature limit of 70C. If the ambient temperature never exceeds 60C, the temperature of the external metal case parts of the ODU will not exceed the touch temperature limit of 90C. Page 3-10 Chapter 3: System planning Site planning Note A restricted access location is defined (in EN 60950-1) as one where access may only be gained by use of a tool or lock and key, or other means of security, and access is controlled by the authority responsible for the location. Access must only be gained by persons who have been instructed about the reasons for the restrictions applied to the location and about any precautions that must be taken. Examples of permissible restricted access locations are a lockable equipment room or a lockable cabinet. ODU wind loading Ensure that the ODU and the structure on which it is mounted are capable of withstanding the prevalent wind speeds at a proposed PMP/PTP 450 platform site. Wind speed statistics are available from national meteorological offices. The ODU and its mouting bracket are capable of withstanding wind speeds of:

Up to 200 mph (322 kph) for PMP 450m 5 GHz AP Up to 200 mph (322 kph) for PMP/PTP 450i - 5 GHz all models Up to 200 mph (322 kph) for PMP/PTP 450 - all models Up to 200 mph (322 kph) for PMP 450 - Ruggedized Up to 200 mph (322 kph) for PMP 450i - 900 MHz all models Up to 90 mph (145 kph) for PMP 450d Note The 900 MHz Antennas are tested up to 100mph wind loading. Wind blowing on the ODU will subject the mounting structure to significant lateral force. The magnitude of the force depends on both wind strength and surface area of the ODU. Wind loading is estimated using the following formulae:

Force (in kilogrammes) = 0.1045aV2 where:

o a is the surface area in square meters, and o V is the wind speed in meters per second. Force (in pounds) = 0.0042Av2 where:

o A is the surface area in square feet, and o v is the wind speed in miles per hour. Applying these formulae to the 450 platformat different wind speeds, the resulting wind loadings are shown in below tables. Page 3-11 Chapter 3: System planning Site planning Table 51 PMP 450m wind loading (Newton) Type of ODU Max surface area Wind speed (kilometer per hour)

(square meters) 160 170 180 190 200 Integrated 90 sector antenna 0.331 671 757 849 946 1048 Table 52 PMP/PTP 450i wind loading (Newton) Type of ODU Max surface area Wind speed (kilometer per hour)

(square meters) Connectorized 0.035 Directional antenna 0.093 5.x GHz 160 94 249 170 106 281 180 119 315 190 132 351 200 146 389 Integrated 90 sector 0.126 337 381 427 475 527 antenna -5.x GHz Directional Yagi 0.025 67 76 85 94 105 antenna - 900 MHz External 65 sector 0.253 677 764 857 954 1058 antenna 900 MHz Table 53 PMP 450m wind loading (lb force) Type of ODU Max surface area Wind speed (miles per hour)

(square feet) 100 105 110 115 120 Integrated 90 sector antenna 3.565 150 165 181 198 216 Page 3-12 Chapter 3: System planning Site planning Table 54 PMP/PTP 450i wind loading (lb force) Type of ODU Max surface area Wind speed (miles per hour)

(square feet) Connectorized 0.377 Directional antenna 1.001 5.x GHz 100 105 110 115 120 16 42 17 46 19 51 21 56 23 61 Integrated 90 sector 1.356 57 63 69 75 82 antenna -5.x GHz Directional Yagi 0.27 11 13 14 15 16 antenna - 900 MHz External 65 sector 2.72 114 126 138 151 165 antenna 900 MHz For a connectorized ODU, add the wind loading of the external antenna to that of the ODU. The antenna manufacturer should be able to quote wind loading. Table 55 PMP/PTP 450 wind loading (Newton) Type of ODU Max surface area Wind speed (kilometer per hour)

(square meters) External 60 sector 0.27 antenna 2.4 GHz AP 160 722 170 815 180 914 190 200 1019 1129 External 60 sector 0.066 177 199 223 249 276 antenna 5 GHz AP External 90 sector 0.083 222 251 281 313 347 antenna 5 GHz AP SM 0.027 72 82 91 Integrated High-Gain, 0.093 249 281 315 102 351 113 389 Ruggedized Integrated Dish 0.14 375 423 474 528 585 Page 3-13 Chapter 3: System planning Site planning Table 56 PMP/PTP 450 wind loading (lb force) Type of ODU Max surface area Wind speed (miles per hour)

(square feet) External 60 sector 2.9 antenna 2.4 GHz AP 100 122 105 134 110 147 115 161 120 175 External 60 sector 0.71 29.8 33 37 39 43 antenna 5 GHz AP External 90 sector 0.89 37 41 45 49 54 antenna 5 GHz AP SM 0.29 Integrated High-

1 Gain, Ruggedized 12 42 13 46 15 51 16 56 18 60 Integrated Dish 1.49 63 69 76 83 90 Drop cable grounding points To estimate how many grounding kits are required for each drop cable, refer to the site installation diagrams (Figure 30 , Figure 31 and Figure 32) and use the following criteria:

The drop cable shield must be grounded near the ODU at the first point of contact between the drop cable and the mast, tower or building. The drop cable shield must be grounded at the building entry point. For mast or tower installations (Figure 30), use the following additional criteria:

The drop cable shield must be grounded at the bottom of the tower, near the vertical to horizontal transition point. This ground cable must be bonded to the tower or tower ground bus bar (TGB), if installed. If the tower is greater than 61 m (200 ft) in height, the drop cable shield must be grounded at the tower midpoint, and at additional points as necessary to reduce the distance between ground cables to 61 m (200 ft) or less. In high lightning-prone geographical areas, the drop cable shield must be grounded at spacing between 15 to 22 m (50 to 75 ft). This is especially important on towers taller than 45 m (150 ft). For roof installations (Figure 32), use the following additional criteria:

The drop cable shield must be bonded to the building grounding system at its top entry point

(usually on the roof). The drop cable shield must be bonded to the building grounding system at the entry point to the equipment room. Page 3-14 Chapter 3: System planning Site planning Lightning Protection Unit(LPU) location Find a location for the bottom LPU that meets the following requirements:

The bottom LPU can be connected to the drop cable from the ODU. The bottom LPU is within 600 mm (24 in) of the point at which the drop cable enters the building, enclosure or equipment room within a larger building. The bottom LPU can be bonded to the grounding system. Page 3-15 Chapter 3: System planning Radio Frequency planning Radio Frequency planning This section describes how to plan PMP/PTP 450 platform links to conform to analysis of spectrum and the regulatory restrictions that apply in the country of operation. Regulatory limits Many countries impose EIRP limits (Allowed EIRP) on products operating in the bands used by the PMP/PTP 450 platform Series. Refer to Equipment Disposal (Chapter 10: Reference Information) on page 10-37 to determine what the maximum transmitted power and EIRP for PMP/PTP 450/450i Series that can be used in each of countries and frequency band. Caution It is the responsibility of the user to ensure that the PMP/PTP product is operated in accordance with local regulatory limits. Note Contact the applicable radio regulator to find out whether or not registration of the PMP/PTP 450/450i link is required. Conforming to the limits Ensure the link is configured to conform to local regulatory requirements by configuring the PMP 450/450i AP or PTP 450/450iBHM for the correct country. In the following situations, this does not prevent operation outside the regulations:

When using connectorized ODUs with external antennas, the regulations may require the maximum transmit power to be reduced. Available spectrum The available spectrum for operation depends on the regulatory band. When configured appropriately, the unit will only allow operation on those channels which are permitted by the regulations. Page 3-16 Chapter 3: System planning Radio Frequency planning Certain regulations have allocated certain channels as unavailable for use:

FCC has allocated part of the 5.1 & 5.2 GHz ETSI has allocated part of the 5.4 GHz band to weather radar. UK and some other European countries have allocated part of the 5.8 GHz band to Road Transport and Traffic Telematics (RTTT) systems. The number and identity of channels barred in a given regulatory band is dependent on the channel bandwidth and channel raster selected. Analyzing the RF Environment An essential element in RF network planning is the analysis of spectrum usage and the strength of the signals that occupy the spectrum. Regardless of how these parameters are measured and log or chart the results (through the Spectrum Analyzer feature or by using a spectrum analyzer), ensure measurements are performed:

At various times of day. On various days of the week. Periodically into the future. As new RF neighbors move in or consumer devices proliferate in currently used spectrum, this keeps the user aware of the dynamic possibilities for interference within the network. Channel bandwidth Select the required channel bandwidth for the link. The selection depends upon the regulatory band selected. The wider the channel bandwidth, the greater the capacity. As narrower channel bandwidths take up less spectrum, selecting a narrow channel bandwidth may be a better choice when operating in locations where the spectrum is very busy. Both ends of the link must be configured to operate on the same channel bandwidth. Anticipating Reflection of Radio Waves In the signal path, any object that is larger than the wavelength of the signal can reflect the signal. Such an object can even be the surface of the earth or of a river, bay or lake. The wavelength of the signal is approximately 2 inches (or 5 cm) for 5.4 GHz and 5.8 GHz signals. 12 inches for 900 MHz signals A reflected signal can arrive at the antenna of the receiver later than the non-reflected signal arrives. These two or more signals cause the condition known as multipath. Multipath may increase or decrease the signal level, resulting in overall attenuation that may be higher or lower than that caused by the link distance. This is problematic at the margin of the link budget, where the standard operating margin (fade margin) may be compromised. Page 3-17 Chapter 3: System planning Radio Frequency planning Obstructions in the Fresnel Zone The Fresnel (pronounced freNEL) Zone is a three-dimensional volume around the line of sight of an antenna transmission. Objects that penetrate this area can cause the received strength of the transmitted signal to fade. Out-of-phase reflections and absorption of the signal result in signal cancellation. The foliage of trees and plants in the Fresnel Zone can cause signal loss. Seasonal density, moisture content of the foliage, and other factors such as wind may change the amount of loss. Plan to perform frequent and regular link tests if you must transmit through foliage. Planning for co-location The first step to avoid interference in wireless systems is to set all AP/BHMs to receive timing from a synchronization source (Cluster Management Module, or Universal Global Positioning System). This ensures that the modules are in sync and start transmitting at the same time each frame. The second step to avoid interference is to configure parameters on all AP/BHMs of the same frequency band in proximity such that they have compatible transmit/receive ratios (all stop transmitting each frame before any start receiving). This avoids the problem of one AP/BHM attempting to receive the signal from a distant SM/BHS while a nearby AP/BHM transmits, which could overpower that signal. The following parameters on the AP/BHM determine the transmit/receive ratio:

Downlink Data percentage

(reserved) Contention slots If OFDM (PMP/PTP 450 platform, PMP/PTP 230) and FSK (PMP/PTP 1x0) APs/BHMs of the same frequency band are in proximity, or if you want BHMs set to different parameters then you must use the Frame Calculator to identify compatible settings for APs/BHMs. The co-location is also supported for 900 MHz PMP 450i APs (OFDM) and PMP 100 APs (FSK). The Frame Calculator is available on the web management interface Tools > Frame Calculator. To use the Frame Calculator, type into the calculator various configurable parameter values for each proximal AP/BHM and then record the resulting AP/BHM Receive Start value. Next vary the Downlink Data percentage in each calculation and iterate until a calculated AP/BHM Receive Start for all co-located AP/BHMs where the transmit end does not come before the receive start. For more information on PMP/PTP 450 platform co-location, see http://www.cambiumnetworks.com/solution-papers Multiple OFDM Access Point Clusters When deploying multiple AP clusters in a dense area, consider aligning the clusters as shown below. However, this is only a recommendation. An installation may dictate a different pattern of channel assignments. Page 3-18 Chapter 3: System planning Radio Frequency planning Figure 36 Example layout of 16 Access Point sectors (ABCD), 90 degree sectors An example for assignment of frequency channels is provided in the following table. Table 57 Example 5.8 GHz 4-channel assignment by access site Symbol Frequency A B C D 5.740 GHz 5.760 GHz 5.780 GHz 5.800 GHz Page 3-19 Chapter 3: System planning Radio Frequency planning Figure 37 Example layout of 6 Access Point sectors (ABC), 60 degree sectors An example for assignment of frequency channels and sector IDs is provided in the following table. Table 58 Example 5.8 GHz 3-channel assignment by access site Symbol Frequency A B C 5.740 GHz 5.760 GHz 5.780 GHz Page 3-20 Chapter 3: System planning Link planning Link planning This section describes factors to be taken into account when planning links, such as range, obstacles path loss and throughput. LINKPlanner is recommended. Range and obstacles Calculate the range of the link and identify any obstacles that may affect radio performance. Perform a survey to identify all the obstructions (such as trees or buildings) in the path and to assess the risk of interference. This information is necessary in order to achieve an accurate link feasibility assessment. The PMP/PTP 450 platform Series is designed to operate in Non-Line-of-Sight (NLoS) and Line-of-

Sight (LoS) environments. An NLOS environment is one in which there is no optical line-of-sight, that is, there are obstructions between the antennas. OFDM technology can often use multi-pathing to an advantage to overcome nLOS, especially in cases where the Fresnel zone is only partially blocked by buildings, urban canyons, or foliage. OFDM tends to help especially when obstacles are near the middle of the link, and less so when the obstacles are very near the ODU. However, attenuation through walls and trees is substantial for any use of the 5.4 GHz and 5.8 GHz frequency bands. The lower frequency radio waves of 900 MHz radios provide greater penetration through walls, trees and other obstacles, making it optimal for most non-line-of-sight applications. Even with OFDM, these products are not expected to penetrate walls or extensive trees and foliage. Path loss Path loss is the amount of attenuation the radio signal undergoes between the two ends of the link. The path loss is the sum of the attenuation of the path if there were no obstacles in the way

(Free Space Path Loss), the attenuation caused by obstacles (Excess Path Loss) and a margin to allow for possible fading of the radio signal (Fade Margin). The following calculation needs to be performed to judge whether a particular link can be installed:

Where:

Is:

Free Space Path Loss (dB) Excess Path Loss (dB) Fade Margin Required (dB) Seasonal Fading (dB) Page 3-21 capabilityseasonalfadeexcessspacefreeLLLLL_spacefreeL_excessLfadeLseasonalL Chapter 3: System planning Link planning Equipment Capability (dB) Calculating Link Loss The link loss is the total attenuation of the wireless signal between two point-to-multipoint units. The link loss calculation is presented below:

Link Loss (dB) = Transmit power of the remote wireless unit (dBm) Tx Cable loss

(dB) Received power at the local unit (dBm) Rx cable loss (dB) +

Antenna gain at the remote unit (dBi) + Antenna gain at the local unit

(dBi) Calculating Rx Signal Level The determinants in Rx signal level are illustrated in Figure 38. Figure 38 Determinants in Rx signal level Rx signal level is calculated as follows:

Rx signal level dB = Tx power Tx cable loss + Tx antenna gain free space path loss + Rx antenna gain Rx cable loss Note This Rx signal level calculation presumes that a clear line of sight is established between the transmitter and receiver and that no objects encroach in the Fresnel zone. Page 3-22 capabilityL Chapter 3: System planning Link planning Calculating Fade Margin Free space path loss is a major determinant in Rx (received) signal level. Rx signal level, in turn, is a major factor in the system operating margin (fade margin), which is calculated as follows:

System operating margin (fade margin) dB = Rx signal level dB Rx sensitivity dB Thus, fade margin is the difference between strength of the received signal and the strength that the receiver requires for maintaining a reliable link. A higher fade margin is characteristic of a more reliable link. Adaptive modulation Adaptive modulation ensures that the highest throughput that can be achieved instantaneously will be obtained, taking account of propagation and interference. When the link has been installed, web pages provide information about the link loss currently measured by the equipment, both instantaneously and averaged. The averaged value will require maximum seasonal fading to be added, and then the radio reliability of the link can be computed. For details of the system throughput, link loss and maximum distance for each frequency band in all modulation modes, see Link on page 10-34. Page 3-23 Chapter 3: System planning Planning for connectorized units Planning for connectorized units This section describes factors to be taken into account when planning to use connectorized ODUs with external antennas in PMP/PTP 450 platform links. When to install connectorized units The majority of radio links can be successfully deployed with the integrated ODU. However the integrated units may not be sufficient in some areas, for example:

Where the path is heavily obscured by dense woodland on an NLOS link. Where long LOS links are required. Where there are known to be high levels of interference. In these areas, connectorized ODUs and external antennas should be used. Choosing external antennas When selecting external antennas, consider the following factors:

The required antenna gain. Ease of mounting and alignment. Use dual-polarization antenna (as the integrated antenna). Note Enter the antenna gain and cable loss into the Installation Wizard, if the country selected has an EIRP limit, the corresponding maximum transmit power will be calculated automatically by the unit. Calculating RF cable length (5.8 GHz FCC only) The 5.8 GHz band FCC approval for the product is based on tests with a cable loss between the ODU and antenna of not less than 1.2 dB. If cable loss is below 1.2 dB with a 1.3 m (4 ft) diameter external antenna, the connectorized PMP/PTP 450 platform may exceed the maximum radiated spurious emissions allowed under FCC 5.8 GHz rules. Cable loss depends mainly upon cable type and length. To meet or exceed the minimum loss of 1.2 dB, use cables of the type and length specified in Table 59 (source: Times Microwave). This data excludes connector losses. Page 3-24 Chapter 3: System planning Planning for connectorized units Table 59 RF cable lengths required to achieve 1.2 dB loss at 5.8 GHz RF cable type Minimum cable length 0.6 m (1.9 ft) 1.4 m (4.6 ft) 2.2 m (7.3 ft) 3.4 m (11.1 ft) 5.0 m (16.5 ft) LMR100 LMR200 LMR300 LMR400 LMR600 Page 3-25 Chapter 3: System planning Data network planning Data network planning This section describes factors to be considered when planning PMP/PTP 450 platform data networks. Understanding addresses A basic understanding of Internet Protocol (IP) address and subnet mask concepts is required for engineering your IP network. IP address The IP address is a 32-bit binary number that has four parts (octets). This set of four octets has two segments, depending on the class of IP address. The first segment identifies the network. The second identifies the hosts or devices on the network. The subnet mask marks a boundary between these two sub-addresses. Dynamic or static addressing For any computer to communicate with a module, the computer must be configured to either use DHCP (Dynamic Host Configuration Protocol). In this case, when not connected to the network, the computer derives an IP address on the 169.254 network within two minutes. have an assigned static IP address (for example, 169.254.1.5) on the 169.254 network. Note If an IP address that is set in the module is not the 169.254.x.x network address, then the network operator must assign the computer a static IP address in the same subnet. When a DHCP server is not found To operate on a network, a computer requires an IP address, a subnet mask, and possibly a gateway address. Either a DHCP server automatically assigns this configuration information to a computer on a network or an operator must input these items. When a computer is brought on line and a DHCP server is not accessible (such as when the server is down or the computer is not plugged into the network), Microsoft and Apple operating systems default to an IP address of 169.254.x.x and a subnet mask of 255.255.0.0 (169.254/16, where /16 indicates that the first 16 bits of the address range are identical among all members of the subnet). Page 3-26 Chapter 3: System planning Data network planning DNS Client The DNS Client is used to resolve names of management servers within the operators management domain (see Figure 39). This feature allows hostname configuration for NTP servers, Authorization Servers, DHCP relay servers, and SNMP trap servers. Operators may choose to either enter in the FQDN (Fully Qualified Domain Name) for the host name or to manually enter the IP addresses of the servers. Figure 39 Cambium networks management domain Network Address Translation (NAT) NAT, DHCP Server, DHCP Client and DMZ in SM The system provides NAT (network address translation) for SMs in the following combinations of NAT and DHCP (Dynamic Host Configuration Protocol):

NAT Disabled NAT with DHCP Client (DHCP selected as the Connection Type of the WAN interface) and DHCP Server NAT with DHCP Client(DHCP selected as the Connection Type of the WAN interface) NAT with DHCP Server NAT without DHCP NAT NAT isolates devices connected to the Ethernet/wired side of a SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic

(separate from its address for management), terminates transport traffic, and allows you to assign a range of IP addresses to devices that are connected to the Ethernet/wired side of the SM. Page 3-27 Chapter 3: System planning Data network planning In the Cambium system, NAT supports many protocols, including HTTP, ICMP (Internet Control Message Protocols), and FTP (File Transfer Protocol). For virtual private network (VPN) implementation, L2TP over IPSec (Level 2 Tunneling Protocol over IP Security) and PPTP (Point to Point Tunneling Protocol) are supported. DHCP DHCP enables a device to be assigned a new IP address and TCP/IP parameters, including a default gateway, whenever the device reboots. Thus DHCP reduces configuration time, conserves IP addresses, and allows modules to be moved to a different network within the Cambium system. In conjunction with the NAT features, each SM provides:

A DHCP server that assigns IP addresses to computers connected to the SM by Ethernet protocol. A DHCP client that receives an IP address for the SM from a network DHCP server. DMZ In conjunction with the NAT features, a DMZ (demilitarized zone) allows the assignment of one IP address behind the SM for a device to logically exist outside the firewall and receive network traffic. The first three octets of this IP address must be identical to the first three octets of the NAT private IP address. Developing an IP addressing scheme Network elements are accessed through IP Version 4 (IPv4) addressing. A proper IP addressing method is critical to the operation and security of a network. Each module requires an IP address on the network. This IP address is for only management purposes. For security, you must either:

Assign a non-routable IP address. Assign a routable IP address only if a firewall is present to protect the module. You assign an IP addresses to computers and network components by either static or dynamic IP addressing. You will also assign the appropriate subnet mask and network gateway to each module. Address Resolution Protocol As previously stated, the MAC address identifies a module in:

Communications between modules. The data that modules store about each other. Page 3-28 Chapter 3: System planning Data network planning The IP address is essential for data delivery through a router interface. Address Resolution Protocol (ARP) correlates MAC addresses to IP addresses. For communications to outside the network segment, ARP reads the network gateway address of the router and translates it into the MAC address of the router. Then the communication is sent to MAC address (physical network interface card) of the router. For each router between the sending module and the destination, this sequence applies. The ARP correlation is stored until the ARP cache times out. Allocating subnets The subnet mask is a 32-bit binary number that filters the IP address. Where a subnet mask contains a bit set to 1, the corresponding bit in the IP address is part of the network address. Example IP address and subnet mask In Figure 40, the first 16 bits of the 32-bit IP address identify the network:

Figure 40 Example of IP address in Class B subnet Octet 1 Octet 2 Octet 3 Octet 4 IP address 169.254.1.1 10101001 11111110 00000001 00000001 Subnet mask 255.255.0.0 11111111 11111111 00000000 00000000 In this example, the network address is 169.254 and 216 (65,536) hosts are addressable. Selecting non-routable IP addresses The factory default assignments for network elements are:

Unique MAC address IP address of 169.254.1.1 Subnet mask of 255.255.0.0 Network gateway address of 169.254.0.0 For each radio and CMM4, assign an IP address that is both consistent with the IP addressing plan for your network and cannot be accessed from the Internet. IP addresses within the following ranges are not routable from the Internet, regardless of whether a firewall is configured:

10.0.0.0 10.255.255.255 172.16.0.0 172.31.255.255 192.168.0.0 192.168.255.255 Also, the subnet mask and network gateway for each CMM4 can be assigned. Page 3-29 Chapter 3: System planning Data network planning Translation bridging Optionally, the AP can be configured to change the source MAC address in every packet it receives from its SMs to the MAC address of the SM/BHS that bridged the packet, before forwarding the packet toward the public network. In this case:

Not more than 128 IP devices at any time are valid to send data to the AP from behind the SM. SM populates the Translation Table tab of its Statistics web page, displaying the MAC address and IP address of all the valid connected devices. Each entry in the Translation Table is associated with the number of minutes that have elapsed since the last packet transfer between the connected device and the SM. If 128 are connected, and another attempts to connect:

o o If no Translation Table entry is older than 255 minutes, the attempt is ignored. If an entry is older than 255 minutes, the oldest entry is removed and the attempt is successful. The Send Untranslated ARP parameter in the General tab of the Configuration page can be:

o Disabled, so that the AP overwrites the MAC address in ARP packets before forwarding them. o Enabled, so that the AP forwards ARP packets regardless of whether it has overwritten the MAC address. This is the Translation Bridging feature, which you can enable in the General page of the Configuration web page in the AP. When this feature is disabled, the setting of the Send Untranslated ARP parameter has no effect, because all packets are forwarded untranslated

(with the source MAC address intact). See Address Resolution Protocol on Page 3-28. Engineering VLANs The radios support VLAN functionality as defined in the 802.1Q (Virtual LANs) specification, except for the following aspects of that specification:

Protocols:

o Generic Attribute Registration Protocol (GARP) GARV o Spanning Tree Protocol (STP) o Multiple Spanning Tree Protocol (MSTP) o GARP Multicast Registration Protocol (GMRP) Embedded source routing (ERIF) in the 802.1Q header Multicast pruning Flooding unknown unicast frames in the downlink As an additional exception, the AP/BHM does not flood downward the unknown unicast frames to the SM/BHS. A VLAN configuration in Layer 2 establishes a logical group within the network. Each computer in the VLAN, regardless of initial or eventual physical location, has access to the same data. For the network operator, this provides flexibility in network segmentation, simpler management, and enhanced security. Page 3-30 Chapter 3: System planning Data network planning Special case VLAN numbers This system handles special case VLAN numbers according to IEEE specifications:

Table 60 Special case VLAN IDs VLAN Number Purpose Usage Constraint 0 1 These packets have 802.1p priority, but are Must not be used as a otherwise handled as untagged. management VLAN. Although not noted as special case by IEEE specifications, these packets identify traffic that was untagged upon ingress into the SM and must remain untagged upon egress. This policy is hard-coded in the AP. Must not be used for system VLAN traffic. 4095 This VLAN is reserved for internal use. Must not be used at all. SM membership in VLANs With the supported VLAN functionality, the radios determine bridge forwarding on the basis of not only the destination MAC address, but also the VLAN ID of the destination. This provides flexibility in how SMs are used:

Each SM can be a member in its own VLAN. Each SM can be in its own broadcast domain, such that only the radios that are members of the VLAN can see broadcast and multicast traffic to and from the SM. The network operator can define a work group of SMs, regardless of the AP(s) to which they register. Page 3-31 Chapter 3: System planning Data network planning PMP 450 platform modules provide the VLAN frame filters that are described in Table 61. Table 61 VLAN filters in point-to-multipoint modules then a frame is discarded if Where VLAN is active, if this parameter value is selected entering the bridge/

NAT switch through Ethernet TCP/IP because of this VLAN filter in the software:

any combination of VLAN parameter settings any combination of with a VID not in the membership table Ingress with a VID not in VLAN the Local Ingress parameter settings Allow Frame Types:

Tagged Frames Only with no 802.1Q tag Allow Frame Types:

with an 802.1Q tag, Untagged Frames Only regardless of VID Local SM Management:

Disable in the SM, or with an 802.1Q tag All Local SM Management:

Disable in the AP and a VID in the membership table membership table Only Tagged Only Untagged Local SM Management any combination of VLAN parameter settings any combination of leaving the bridge/

NAT switch through Ethernet TCP/IP with a VID not in the membership table Egress with a VID not in VLAN the Local Egress parameter settings membership table Priority on VLANs (802.1p) The radios can prioritize traffic based on the eight priorities described in the IEEE 802.1p specification. When the high-priority channel is enabled on a SM, regardless of whether VLAN is enabled on the AP for the sector, packets received with a priority of 4 through 7 in the 802.1p field are forwarded onto the high-priority channel. Page 3-32 Chapter 3: System planning Data network planning Operators may configure priority precedence as 802.1p Then Diffserv (Default) or Diffserv Then 802.1p. Since these priority precedence configurations are independent between the AP and SM, this setting must be configured on both the AP and SM to ensure that the precedence is adhered to by both sides of the link. VLAN settings can also cause the module to convert received non-VLAN packets into VLAN packets. In this case, the 802.1p priority in packets leaving the module is set to the priority established by the DiffServ configuration. If VLAN is enabled, immediately monitor traffic to ensure that the results are as desired. For example, high-priority traffic may block low-priority. Q-in-Q DVLAN (Double-VLAN) Tagging (802.1ad) PMP and PTP modules can be configured with 802.1ad Q-in-Q DVLAN (Double-VLAN) tagging which is a way for an operator to put an 802.1Q VLAN inside of an 802.1ad VLAN. A nested VLAN, which is the original 802.1Q tag and a new second 802.1ad tag, allows for bridging of VLAN traffic across a network and segregates the broadcast domains of 802.1Q VLANs. Q-in-Q can be used with PPPoE and/or NAT. The 802.1ad standard defines the S-VLAN as the Service Provider VLAN and the C-VLAN as the customer VLAN. The radio software does 2 layer Q-in-Q whereby the C-VLAN is the 802.1Q tag and the S-VLAN is the second layer Q tag as shown in Table 62. Table 62 Q-in-Q Ethernet frame Ethernet Header S-VLAN EthType C-VLAN EthType 0x88a8 0x8100 IP Data EthType 0x0800 The 802.1ad S-VLAN is the outer VLAN that is configurable on the Configuration > VLAN web page of the AP/BHM. The Q-in-Q EtherType parameter is configured with a default EtherType of 0x88a8 in addition to four alternate EtherTypes that can be configured to aid in interoperability with existing networks that use a different EtherType than the default. The C-VLAN is the inner VLAN tag, which is the same as 802.1Q. As a top level concept, this operates on the outermost tag at any given time, either pushing a tag on or popping a tag off. This means packets will at most transition from an 802.1Q frame to an 801.ad frame (with a tag pushed on) or an untagged 802.1 frame (with the tag popped off. Similarly, for an 802.1ad frame, this can only transition from an 802.1ad frame to an 802.1Q frame (with the tag popped off) since the radio software only supports 2 levels of tags. Page 3-33 Chapter 3: System planning Network management planning Network management planning This section describes how to plan for PMP/PTP 450 platform links to be managed remotely using SNMP. Planning for SNMP operation Cambium modules provide the following SNMP traps for automatic notifications to the NMS:

coldStart, which signals that the SNMPv2c element is reinitializing itself and that its configuration may have been altered. warmStart, which signals that the SNMPv2c element is reinitializing such that its configuration is unaltered. authenticationFailure, which signals that the SNMPv2c element has received a protocol message that is not properly authenticated (contingent on the snmpEnableAuthenTraps object setting). linkDown, as defined in RFC 1573 linkUp, as defined in RFC 1573 egpNeighborLoss, as defined in RFC 1213 whispGPSInSync, which signals a transition from not synchronized to synchronized. whispGPSOutSync, which signals a transition from synchronized to not synchronized. whispRegComplete, which signals registration completed. whispRegLost, which signals registration lost. whispRadarDetected, which signals that the one-minute scan has been completed, radar has been detected and the radio will shut down. whispRadarEnd, which signals that the one-minute scan has been completed, radar has not been detected and the radio will resume normal operation. Note The proprietary MIBs are provided in the PMP/PTP 450 platform Series software download files in the support website (see Contacting Cambium Networks on page 1). Enabling SNMP Enable the SNMP interface for use by configuring the following attributes in the SNMP Configuration page:

SNMP State (default disabled) SNMP Version (default SNMPv2c) SNMP Port Number (default 161) Page 3-34 Chapter 3: System planning Security planning Security planning This section describes how to plan for PMP/PTP 450 platform links to operate in secure mode. Managing module access by passwords Filtering protocols and ports Port Configuration Isolating AP/BHM from the Internet Ensure that the IP addresses of the AP/BHM in the network:

are not routable over the Internet. do not share the subnet of the IP address of your user. RFC 1918, Address Allocation for Private Subnets, reserves for private IP networks three blocks of IP addresses that are not routable over the Internet:

/8 subnets have one reserved network, 10.0.0.0 to 10.255.255.255.

/16 subnets have 16 reserved networks, 172.16.0.0 to 172.31.255.255.

/24 subnets have 256 reserved networks, 192.168.0.0 to 192.168.255.255. Encrypting radio transmissions Cambium fixed wireless broadband IP systems employ the following form of encryption for security of the wireless link:

DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. The default encryption setting for 450 platform is "None". Page 3-35 Chapter 3: System planning Security planning Planning for HTTPS operation Before starting to configure HTTPS operation, ensure that the cryptographic material listed in Table 63 is available. Table 63 HTTPS security material Item Description Quantity required User Defined Security The banner provides warnings and notices Normally one per link. Banner to be read by the user before logging in to This depends upon the ODU. Use text that is appropriate to network policy. the network security policy. Port numbers for HTTP, Port numbers allocated by the network. As allocated by HTTPS and Telnet network. Planning for SNMPv3 operation SNMP security mode Decide how SNMPv3 security will be configured. MIB-based security management uses standard SNMPv3 MIBs to configure the user-based security model and the view-based access control model. This approach provides considerable flexibility, allowing a network operator to tailor views and security levels appropriate for different types of user. MIB-based security management may allow a network operator to take advantage of built-in security management capabilities of existing network managers. Web-based security management allows an operator to configure users, security levels, privacy and authentication protocols, and passphrases using the PMP/PTP 450 platform web-based management interface. The capabilities supported are somewhat less flexible than those supported using the MIB-based security management, but will be sufficient in many applications. Selection of web-based management for SNMPv3 security disables the MIB-based security management. PMP/PTP 450 platform does not support concurrent use of MIB-based and web-

based management of SNMPv3 security. Web-based management of SNMPv3 security Initial configuration of SNMPv3 security is available only to HTTP or HTTPS user accounts with security role of Security Officer. Identify the format used for SNMP Engine ID. The following formats are available:

MAC address (default) 5 and 32 hex characters (the hex character input is driven by RFC 3411 recommendations on the Engine ID) Page 3-36 Chapter 3: System planning Security planning Identify the user names and security roles of initial SNMPv3 users. Two security roles are available:

Read Only System Administrator Identify the security level for each of the security roles. Three security levels are available:

(a) No authentication, no privacy

(b) Authentication, no privacy

(c) Authentication, privacy If authentication is required, identify the protocol. The authentication protocol available is MD5. If privacy will be used, identify the protocol. The privacy protocol available is cbc-des. Managing module access by passwords From the factory, each module has a preconfigured administrator-level account in the name root, which initially requires no associated password. When you upgrade a module:

An account is created in the name admin. Both admin and root inherit the password that was previously used to access the module, if:

o Full Access password, if one was set. o Display-Only Access password, if one was set and no Full Access password was set. Caution If you use Wireless Manager, do not delete the root account from any module. If you use a NMS that communicates with modules through SNMP, do not delete the root account from any module unless you first can confirm that the NMS does not rely on the root account for access to the modules. Each module supports four or fewer user accounts, regardless of account levels. The available levels are ADMINISTRATOR, who has full read and write permissions. This is the level of the root and admin users, as well as any other administrator accounts that one of them creates. INSTALLER, who has permissions identical to those of ADMINISTRATOR except that the installer cannot add or delete users or change the password of any other user. TECHNICIAN, who has permissions to modify basic radio parameters and view informational web pages. GUEST, who has no write permissions and only a limited view of General Status tab. Admin, Installer and Tech accounts can be configured as READ-ONLY. This will allow the account to only see the items. The ability to view information of General Status tab can be controlled by the "Site Information Viewable to Guest Users" under the SNMP tab. Page 3-37 Chapter 3: System planning Security planning From the factory default state, configure passwords for both the root and admin account at the ADMINISTRATOR permission level, using the Account > Change Users Password page. (If configure only one of these, then the other will still require no password for access into it and thus remain a security risk.) If you are intent on configuring only one of them, delete the admin account. The root account is the only account that CNUT uses to update the module. After a password has been set for any ADMINISTRATOR-level account, initial access to the module GUI opens the view of GUEST level. Planning for RADIUS operation Configure RADIUS where remote authentication is required for users of the web-based interface. Remote authentication has the following advantages:

Control of passwords can be centralized. Management of user accounts can be more sophisticated. For example; users can be prompted by a network manager to change passwords at regular intervals. As another example, passwords can be checked for inclusion of dictionary words and phrases. Passwords can be updated without reconfiguring multiple network elements. User accounts can be disabled without reconfiguring multiple network elements. Remote authentication has one significant disadvantage in a wireless link product such as PMP/PTP 450 platform. If the wireless link is down, a unit on the remote side of the broken link may be prevented from contacting a RADIUS Server, with the result that users are unable to access the web-based interface. One useful strategy would be to combine RADIUS authentication for normal operation with a single locally-authenticated user account for emergency use. PMP 450 platform SM provides a choice of the following authentication methods:

EAP-MSCHAPv2 EAP-TTLS Ensure that the authentication method selected in PMP/PTP 450 platform is supported by the RADIUS server. Filtering protocols and ports Configure filters for specified protocols and ports from leaving the AP/BHM and SM/BHS and entering the network. This protects the network from both intended and inadvertent packet loading or probing by network users. By keeping the specified protocols or ports off the network, this feature also provides a level of protection to users from each other. Protocol and port filtering is set per AP/SM/BH. Except for filtering of SNMP ports, filtering occurs as packets leave the AP/SM/BH. For example, if SM is configured to filter SNMP, then SNMP packets are blocked from entering the SM and, thereby, from interacting with the SNMP portion of the protocol stack on the SM. Page 3-38 Chapter 3: System planning Security planning Port Filtering with NAT Enabled Where NAT is enabled on the SM/BHS, the filtering can be enabled for only the user-defined ports. The following are examples for situations where the configure port can be filtered where NAT is enabled:

To block a subscriber from using FTP, you can filter Ports 20 and 21 (the FTP ports) for both the TCP and UDP protocols. To block a subscriber from access to SNMP, you can filter Ports 161 and 162 (the SNMP ports) for both the TCP and UDP protocols. Note In only the SNMP case, filtering occurs before the packet interacts with the protocol stack. Protocol and Port Filtering with NAT Disabled Where NAT is disabled on the SM/BHS, the filtering can be enabled for both protocols and the three user-defined ports. Using the check boxes on the interface, it can be either:

Allow all protocols except those that user wish to block. Block all protocols except those that user wish to allow. Allow or block any of the following protocols:

PPPoE (Point to Point Protocol over Ethernet) Any or all of the following IPv4 (Internet Protocol version 4) protocols:

Any or all of the following IPv4 (Internet Protocol version 4) protocols:

o SMB (Network Neighborhood) o SNMP o Bootp Client o Bootp Server o Up to 3 user-defined ports o All other IPv4 traffic (see Figure 29) Any or all of the following IPv6 (Internet Protocol version 6) protocols:

o SMB (Network Neighborhood) o SNMP o Bootp Client o Bootp Server o Up to 3 user-defined ports o All other IPv6 traffic (see Figure 29) Filter Direction Upstream and Downstream ARP (Address Resolution Protocol) Page 3-39 Chapter 3: System planning Security planning Figure 41 Categorical protocol filtering The following are example situations in which the protocol filtering is configured where NAT is disabled:

If a subscriber is blocked from only PPPoE and SNMP, then the subscriber retains access to all other protocols and all ports. If PPPoE, IPv4, and Uplink Broadcast are blocked, and also check the All others selection, then only Address Resolution Protocol is not filtered. The ports filtered as a result of protocol selections in the Protocol Filtering tab of the SM/BHS are listed in Table 64. Page 3-40 BootP ClientBootP ServerSNMPIPv4 MulticastUser Defined Port 1SMBUser Defined Port 3User Defined Port 2PPPoEARPAll OthersAll Other IPv4 Chapter 3: System planning Security planning Table 64 Ports filtered per protocol selections Protocol Selected Port Filtered (Blocked) SMB SNMP Destination Ports UDP : 137, 138, 139, 445, 3702 and 1900 Destination Ports TCP : 137, 138, 139, 445, 2869, 5357 and 5358 Destination Ports TCP and UDP : 161 and 162 Bootp Client Source Port 68 UDP Bootp Server Source Port 67 UDP User Defined Port 1..3 User defined ports for filtering UDP and TCP IPv4 Multicast Block IPv4 packet types except other filters defined IPv6 Multicast Block IPv6 packet types except other filters defined ARP Filter all Ethernet packet type 806 Upstream Applies packet filtering to traffic coming into the FEC interface Applies packet filtering to traffic destined to exit the FEC interface Downstream Port Configuration PMP/PTP 450 platform supports access to various communication protocols and only the ports required for these protocols are available for access by external entities. Operators may change the port numbers for these protocols via the radio GUI or SNMP. Table 65 Device default port numbers Port Usage Port Usage Device 21 80 443 161 162 514 FTP HTTP HTTPS Listen Port AP, SM Listen Port AP, SM Listen Port AP, SM SNMP port Listen Port AP, SM SNMP trap port Destination Port AP, SM Syslog Server port Destination Port AP, SM 1812 Standard RADIUS port Destination Port AP 1813 Standard RADIUS accounting port Destination Port AP, SM Page 3-41 Chapter 3: System planning Security planning Encrypting downlink broadcasts An AP can be enabled to encrypt downlink broadcast packets such as the following:

ARP NetBIOS broadcast packets containing video data on UDP. The encryption used is DES for a DES-configured module and AES for an AES-configured module. Before the Encrypt Downlink Broadcast feature is enabled on the AP, air link security must be enabled on the AP. Isolating SMs in PMP In an AP, SMs in the sector can be prevented from directly communicating with each other. In CMM4, the connected APs can be prevented from directly communicating with each other, which prevents SMs that are in different sectors of a cluster from communicating with each other. In the AP, the SM Isolation parameter is available in the General tab of the Configuration web page. Configure the SM Isolation feature by any of the following selections from drop-down menu:

Disable SM Isolation (the default selection). This allows full communication between SMs. Enable Option 1 - Block SM destined packets from being forwarded. This prevents both multicast/broadcast and unicast SM-to-SM communication. Enable Option 2 - Forward SM destined packets upstream. This not only prevents multicast/broadcast and unicast SM-to-SM communication but also sends the packets, which otherwise may have been handled SM to SM, through the Ethernet port of the AP. In the CMM and the CMM4, SM isolation treatment is the result of how to manage the port-based VLAN feature of the embedded switch, where all traffic can be switched from any AP to a specified uplink port. However, this is not packet level switching. It is not based on VLAN IDs. Filtering management through Ethernet Configure the SM to disallow any device that is connected to its Ethernet port from accessing the IP address of the SM. If the Ethernet Access Control parameter is set to Enabled, then:

No attempt to access the SM management interface (by http, SNMP, ftp, or tftp) through Ethernet is granted. Any attempt to access the SM management interface over the air (by IP address, presuming that LAN1 Network Interface Configuration, Network Accessibility is set to Public, or by link from the Session Status or Remote Subscribers tab in the AP) is unaffected. Page 3-42 Chapter 3: System planning Security planning Allowing management from only specified IP addresses The Security sub-menu of the Configuration web page in the AP/BHM and SM/BHS includes the IP Access Control parameter. Specify one, two, or three IP addresses that must be allowed to access the management interface (by HTTP, SNMP, FTP or TFTP). If the selection is:

IP Access Filtering Disabled, then management access is allowed from any IP address, even if the Allowed Source IP 1 to 3 parameters are populated. IP Access Filtering Enabled, and specify at least one address in the Allowed Source IP 1 to 3 parameter, then management access is limited to the specified address(es). Configuring management IP by DHCP The Configuration > IP web page of every radio contains a LAN1 Network Interface Configuration, DHCP State parameter that, if enabled, causes the IP configuration (IP address, subnet mask, and gateway IP address) to be obtained through DHCP instead of the values of those individual parameters. The setting of this DHCP state parameter is also viewable, but is not settable, in the Network Interface tab of the Home page. In the SM/BHS, this parameter is settable in the NAT tab of the Configuration web page, but only if NAT is enabled. in the IP tab of the Configuration web page, but only if the Network Accessibility parameter in the IP tab is set to Public. DHCP option 81 The DHCP server can be used to register and update the pointer (PTR) and host (A) DNS resource records on behalf of its DHCP-enabled clients. The DHCP option 81 permits the client to provide its fully qualified domain name (FQDN) as well as instructions to the DHCP server on how it would like the server to process DNS dynamic updates

(if any) on its behalf. The hostname is poplulated as SiteName.DomainName depending upon following conditions:

If Sitename is default i.e. No Site Name , mac address will be used instead. The SiteName should only be a-z | A-Z | 0-9 and period(.) and dash(-). The domain name part should not start or end with dash (-). The underscore or space in domain name part will be converted to dash(-), anything else apart from valid characters will be skipped. Page 3-43 Chapter 3: System planning Security planning Controlling PPPoE PADI Downlink Forwarding The AP supports the control of forwarding of PPPoE PADI (PPPoE Active Discovery Initiation) packets. This forwarding is configured on the AP GUI Configuration > Radio page by parameter PPPoE PADI Downlink Forwarding. When set to Enabled, the AP allows downstream and upstream transmission of PPPoE PADI packets. When set to Disabled, the AP does NOT allow PPPoE PADI packets to be sent out of the AP RF interface (downstream) but will allow PPPoE PADI packets to enter the RF interface (upstream) and exit the Ethernet interface. Page 3-44 Chapter 4: Legal and regulatory information This chapter provides end user license agreements and regulatory notifications. Caution Intentional or unintentional changes or modifications to the equipment must not be made unless under the express consent of the party responsible for compliance. Any such modifications could void the users authority to operate the equipment and will void the manufacturers warranty. Attention Changements ou modifications Intentionnels ou non de l'quipement ne doivent pas tre entrepris sans l'autorisation de lorganisme responsable de la dclaration de conformit. Ces modifications ou changements pourraient invalider le droit de l'utilisateur utiliser cet appareil et annuleraient la garantie du fabricant. The following topics are described in this chapter:

Cambium Networks end user license agreement on page 4-2 contains the Cambium and third party license agreements for the PMP/PTP 450 platform Series products. Compliance with safety standards on page 4-22 lists the safety specifications against which the PMP/PTP 450 platform has been tested and certified. It also describes how to keep RF exposure within safe limits. Compliance with radio regulations on page 4-31 describes how the PMP/PTP 450 platform complies with the radio regulations that are in force in various countries, and contains notifications made to regulatory bodies for the PMP/PTP 450 platform. Page 4-1 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Cambium Networks end user license agreement Definitions In this Agreement, the word Software refers to the set of instructions for computers, in executable form and in any media, (which may include diskette, CD-ROM, downloadable internet, hardware, or firmware) licensed to you. The word Documentation refers to electronic or printed manuals and accompanying instructional aids licensed to you. The word Product refers to Cambium Networks fixed wireless broadband devices for which the Software and Documentation is licensed for use. Acceptance of this agreement In connection with Cambium Networks delivery of certain proprietary software or products containing embedded or pre-loaded proprietary software, or both, Cambium Networks is willing to license this certain proprietary software and the accompanying documentation to you only on the condition that you accept all the terms in this End User License Agreement (Agreement). IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, DO NOT USE THE PRODUCT OR INSTALL THE SOFTWARE. INSTEAD, YOU MAY, FOR A FULL REFUND, RETURN THIS PRODUCT TO THE LOCATION WHERE YOU ACQUIRED IT OR PROVIDE WRITTEN VERIFICATION OF DELETION OF ALL COPIES OF THE SOFTWARE. ANY USE OF THE SOFTWARE, INCLUDING BUT NOT LIMITED TO USE ON THE PRODUCT, WILL CONSTITUTE YOUR ACCEPTANCE TO THE TERMS OF THIS AGREEMENT. Grant of license Cambium Networks Limited (Cambium) grants you (Licensee or you) a personal, nonexclusive, non-transferable license to use the Software and Documentation subject to the Conditions of Use set forth in Conditions of use and the terms and conditions of this Agreement. Any terms or conditions relating to the Software and Documentation appearing on the face or reverse side of any purchase order, purchase order acknowledgment or other order document that are different from, or in addition to, the terms of this Agreement will not be binding on the parties, even if payment is accepted. Page 4-2 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Conditions of use Any use of the Software and Documentation outside of the conditions set forth in this Agreement is strictly prohibited and will be deemed a breach of this Agreement. 1. Only you, your employees or agents may use the Software and Documentation. You will take all necessary steps to insure that your employees and agents abide by the terms of this Agreement. 2. You will use the Software and Documentation (i) only for your internal business purposes; (ii) only as described in the Software and Documentation; and (iii) in strict accordance with this Agreement. 3. You may use the Software and Documentation, provided that the use is in conformance with the terms set forth in this Agreement. 4. Portions of the Software and Documentation are protected by United States copyright laws, international treaty provisions, and other applicable laws. Therefore, you must treat the Software like any other copyrighted material (for example, a book or musical recording) except that you may either: (i) make 1 copy of the transportable part of the Software (which typically is supplied on diskette, CD-ROM, or downloadable internet), solely for back-up purposes; or (ii) copy the transportable part of the Software to a PC hard disk, provided you keep the original solely for back-

up purposes. If the Documentation is in printed form, it may not be copied. If the Documentation is in electronic form, you may print out 1 copy, which then may not be copied. With regard to the copy made for backup or archival purposes, you agree to reproduce any Cambium Networks copyright notice, and other proprietary legends appearing thereon. Such copyright notice(s) may appear in any of several forms, including machine-readable form, and you agree to reproduce such notice in each form in which it appears, to the extent it is physically possible to do so. Unauthorized duplication of the Software or Documentation constitutes copyright infringement, and in the United States is punishable in federal court by fine and imprisonment. 5. You will not transfer, directly or indirectly, any product, technical data or software to any country for which the United States Government requires an export license or other governmental approval without first obtaining such license or approval. Page 4-3 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Title and restrictions If you transfer possession of any copy of the Software and Documentation to another party outside of the terms of this agreement, your license is automatically terminated. Title and copyrights to the Software and Documentation and any copies made by you remain with Cambium Networks and its licensors. You will not, and will not permit others to: (i) modify, translate, decompile, bootleg, reverse engineer, disassemble, or extract the inner workings of the Software or Documentation,

(ii) copy the look-and-feel or functionality of the Software or Documentation; (iii) remove any proprietary notices, marks, labels, or logos from the Software or Documentation; (iv) rent or transfer all or some of the Software or Documentation to any other party without Cambiums prior written consent; or (v) utilize any computer software or hardware which is designed to defeat any copy protection device, should the Software and Documentation be equipped with such a protection device. If the Software and Documentation is provided on multiple types of media (such as diskette, CD-ROM, downloadable internet), then you will only use the medium which best meets your specific needs, and will not loan, rent, lease, or transfer the other media contained in the package without Cambiums written consent. Unauthorized copying of the Software or Documentation, or failure to comply with any of the provisions of this Agreement, will result in automatic termination of this license. Confidentiality You acknowledge that all Software and Documentation contain valuable proprietary information and trade secrets and that unauthorized or improper use of the Software and Documentation will result in irreparable harm to Cambium Networks for which monetary damages would be inadequate and for which Cambium Networks will be entitled to immediate injunctive relief. If applicable, you will limit access to the Software and Documentation to those of your employees and agents who need to use the Software and Documentation for your internal business purposes, and you will take appropriate action with those employees and agents to preserve the confidentiality of the Software and Documentation, using the same degree of care to avoid unauthorized or improper disclosure as you use for the protection of your own proprietary software, but in no event less than reasonable care. You have no obligation to preserve the confidentiality of any proprietary information that: (i) was in the public domain at the time of disclosure; (ii) entered the public domain through no fault of yours; (iii) was given to you free of any obligation to keep it confidential; (iv) is independently developed by you; or (v) is disclosed as required by law provided that you notify Cambium Networks prior to such disclosure and provide Cambium Networks with a reasonable opportunity to respond. Page 4-4 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Right to use Cambiums name Except as required in Conditions of use, you will not, during the term of this Agreement or thereafter, use any trademark of Cambium Networks, or any word or symbol likely to be confused with any Cambium Networks trademark, either alone or in any combination with another word or words. Transfer The Software and Documentation may not be transferred to another party without the express written consent of Cambium Networks, regardless of whether or not such transfer is accomplished by physical or electronic means. Cambiums consent may be withheld at its discretion and may be conditioned upon transferee paying all applicable license fees and agreeing to be bound by this Agreement. Updates During the first 12 months after purchase of a Product, or during the term of any executed Maintenance and Support Agreement for the Product, you are entitled to receive Updates. An Update means any code in any form which is a bug fix, patch, error correction, or minor enhancement, but excludes any major feature added to the Software. Updates are available for download at the support website. Major features may be available from time to time for an additional license fee. If Cambium Networks makes available to you major features and no other end user license agreement is provided, then the terms of this Agreement will apply. Maintenance Except as provided above, Cambium Networks is not responsible for maintenance or field service of the Software under this Agreement. Page 4-5 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Disclaimer CAMBIUM NETWORKS DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY, OR IN ANY COMMUNICATION WITH YOU. CAMBIUM NETWORKS SPECIFICALLY DISCLAIMS ANY WARRANTY INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILTY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED AS IS. CAMBIUM NETWORKS DOES NOT WARRANT THAT THE SOFTWARE WILL MEET YOUR REQUIREMENTS, OR THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR FREE, OR THAT DEFECTS IN THE SOFTWARE WILL BE CORRECTED. CAMBIUM NETWORKS MAKES NO WARRANTY WITH RESPECT TO THE CORRECTNESS, ACCURACY, OR RELIABILITY OF THE SOFTWARE AND DOCUMENTATION. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. Limitation of liability IN NO EVENT SHALL CAMBIUM NETWORKS BE LIABLE TO YOU OR ANY OTHER PARTY FOR ANY DIRECT, INDIRECT, GENERAL, SPECIAL, INCIDENTAL, CONSEQUENTIAL, EXEMPLARY OR OTHER DAMAGE ARISING OUT OF THE USE OR INABILITY TO USE THE PRODUCT (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION OR ANY OTHER PECUNIARY LOSS, OR FROM ANY BREACH OF WARRANTY, EVEN IF CAMBIUM NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. (Some states do not allow the exclusion or limitation of incidental or consequential damages, so the above exclusion or limitation may not apply to you.) IN NO CASE SHALL CAMBIUMS LIABILITY EXCEED THE AMOUNT YOU PAID FOR THE PRODUCT. U.S. government If you are acquiring the Product on behalf of any unit or agency of the U.S. Government, the following applies. Use, duplication, or disclosure of the Software and Documentation is subject to the restrictions set forth in subparagraphs (c) (1) and (2) of the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 (JUNE 1987), if applicable, unless being provided to the Department of Defense. If being provided to the Department of Defense, use, duplication, or disclosure of the Products is subject to the restricted rights set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 (OCT 1988), if applicable. Software and Documentation may or may not include a Restricted Rights notice, or other notice referring specifically to the terms and conditions of this Agreement. The terms and conditions of this Agreement will each continue to apply, but only to the extent that such terms and conditions are not inconsistent with the rights provided to you under the aforementioned provisions of the FAR and DFARS, as applicable to the particular procuring agency and procurement transaction. Page 4-6 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Term of license Your right to use the Software will continue in perpetuity unless terminated as follows. Your right to use the Software will terminate immediately without notice upon a breach of this Agreement by you. Within 30 days after termination of this Agreement, you will certify to Cambium Networks in writing that through your best efforts, and to the best of your knowledge, the original and all copies, in whole or in part, in any form, of the Software and all related material and Documentation, have been destroyed, except that, with prior written consent from Cambium Networks, you may retain one copy for archival or backup purposes. You may not sublicense, assign or transfer the license or the Product, except as expressly provided in this Agreement. Any attempt to otherwise sublicense, assign or transfer any of the rights, duties or obligations hereunder is null and void. Governing law This Agreement is governed by the laws of the United States of America to the extent that they apply and otherwise by the laws of the State of Illinois. Assignment This agreement may not be assigned by you without Cambiums prior written consent. Survival of provisions The parties agree that where the context of any provision indicates an intent that it survives the term of this Agreement, then it will survive. Entire agreement This agreement contains the parties entire agreement regarding your use of the Software and may be amended only in writing signed by both parties, except that Cambium Networks may modify this Agreement as necessary to comply with applicable laws. Third party software The software may contain one or more items of Third-Party Software supplied by other third-party suppliers. The terms of this Agreement govern your use of any Third-Party Software UNLESS A SEPARATE THIRD-PARTY SOFTWARE LICENSE IS INCLUDED, IN WHICH CASE YOUR USE OF THE THIRD-PARTY SOFTWARE WILL THEN BE GOVERNED BY THE SEPARATE THIRD-PARTY LICENSE. Page 4-7 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Net SNMP Various copyrights apply to this package, listed in various separate parts below. Please make sure that you read all the parts.

---- Part 1: CMU/UCD copyright notice: (BSD like) -----

Copyright 1989, 1991, 1992 by Carnegie Mellon University Derivative Work - 1996, 1998-2000 Copyright 1996, 1998-2000 The Regents of the University of California All Rights Reserved Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission. CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

---- Part 2: Networks Associates Technology, Inc copyright notice (BSD) -----

Copyright 2001-2003, Networks Associates Technology, Inc All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the Networks Associates Technology, Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. Page 4-8 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) -----

Portions of this code are copyright 2001-2003, Cambridge Broadband Ltd. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

---- Part 4: Sun Microsystems, Inc. copyright notice (BSD) -----

Copyright 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Use is subject to license terms below. This distribution may include materials developed by third parties. Sun, Sun Microsystems, the Sun logo and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Page 4-9 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the Sun Microsystems, Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

---- Part 5: Sparta, Inc copyright notice (BSD) -----

Copyright 2003-2008, Sparta, Inc All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of Sparta, Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

---- Part 6: Cisco/BUPTNIC copyright notice (BSD) -----

Copyright 2004, Cisco, Inc and Information Network Center of Beijing University of Posts and Telecommunications. Page 4-10 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of Cisco, Inc, Beijing University of Posts and Telecommunications, nor the names of their contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

---- Part 7: Fabasoft R&D Software GmbH & Co KG copyright notice (BSD) -----

Copyright Fabasoft R&D Software GmbH & Co KG, 2003 oss@fabasoft.com Author: Bernhard Penz Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. The name of Fabasoft R&D Software GmbH & Co KG or any of its subsidiaries, brand or product names may not be used to endorse or promote products derived from this software without specific prior written permission. Page 4-11 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. OpenSSL Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgment:

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/) 4. The names OpenSSL Toolkit and OpenSSL Project must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org. 5. Products derived from this software may not be called OpenSSL nor may OpenSSL appear in their names without prior written permission of the OpenSSL Project. 6. Redistributions of any form whatsoever must retain the following acknowledgment:

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit

(http://www.openssl.org/) THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Page 4-12 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com). Original SSLeay License Copyright 1995-1998 Eric Young (eay@cryptsoft.com) All rights reserved. This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was written so as to conform with Netscapes SSL. This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson

(tjh@cryptsoft.com). Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com) The word cryptographic can be left out if the routines from the library being used are not cryptographic related. 4. If you include any Windows specific code (or a derivative thereof) from the apps directory

(application code) you must include an acknowledgement:

This product includes software written by Tim Hudson (tjh@cryptsoft.com) THIS SOFTWARE IS PROVIDED BY ERIC YOUNG AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Page 4-13 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement The license and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License.]

Zlib Copyright 1995-2005 Jean-loup Gailly and Mark Adler This software is provided as-is, without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. Jean-loup Gailly jloup@gzip.org Mark Adler madler@alumni.caltech.edu Libpng libpng versions 1.2.6, August 15, 2004, through 1.2.35, February 14, 2009, are Copyright 2004, 2006-2008 Glenn Randers-Pehrson, and are distributed according to the same disclaimer and license as libpng-1.2.5 with the following individual added to the list of Contributing Authors Cosmin Truta libpng versions 1.0.7, July 1, 2000, through 1.2.5 - October 3, 2002, are Copyright 2000-2002 Glenn Randers-Pehrson, and are distributed according to the same disclaimer and license as libpng-1.0.6 with the following individuals added to the list of Contributing Authors Simon-Pierre Cadieux Eric S. Raymond Gilles Vollant and with the following additions to the disclaimer:

There is no warranty against interference with your enjoyment of the library or against infringement. There is no warranty that our efforts or the library will fulfil any of your particular purposes or needs. This library is provided with all faults, and the entire risk of satisfactory quality, performance, accuracy, and effort is with the user. libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, are Copyright 1998, 1999 Glenn Randers-Pehrson, and are distributed according to the same disclaimer and license as libpng-0.96, with the following individuals added to the list of Contributing Authors:

Tom Lane Glenn Randers-Pehrson Page 4-14 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Willem van Schaik libpng versions 0.89, June 1996, through 0.96, May 1997, are Copyright 1996, 1997 Andreas Dilger Distributed according to the same disclaimer and license as libpng-0.88, with the following individuals added to the list of Contributing Authors:

John Bowler Kevin Bracey Sam Bushell Magnus Holmgren Greg Roelofs Tom Tanner libpng versions 0.5, May 1995, through 0.88, January 1996, are Copyright 1995, 1996 Guy Eric Schalnat, Group 42, Inc. For the purposes of this copyright and license, Contributing Authors is defined as the following set of individuals:

Andreas Dilger Dave Martindale Guy Eric Schalnat Paul Schmidt Tim Wegner The PNG Reference Library is supplied AS IS. The Contributing Authors and Group 42, Inc. disclaim all warranties, expressed or implied, including, without limitation, the warranties of merchantability and of fitness for any purpose. The Contributing Authors and Group 42, Inc. assume no liability for direct, indirect, incidental, special, exemplary, or consequential damages, which may result from the use of the PNG Reference Library, even if advised of the possibility of such damage. Permission is hereby granted to use, copy, modify, and distribute this source code, or portions hereof, for any purpose, without fee, subject to the following restrictions:

1. The origin of this source code must not be misrepresented. 2. Altered versions must be plainly marked as such and must not be misrepresented as being the original source. 3. This Copyright notice may not be removed or altered from any source or altered source distribution. The Contributing Authors and Group 42, Inc. specifically permit, without fee, and encourage the use of this source code as a component to supporting the PNG file format in commercial products. If you use this source code in a product, acknowledgment is not required but would be appreciated. A png_get_copyright function is available, for convenient use in about boxes and the like:

printf("%s",png_get_copyright(NULL));

Also, the PNG logo (in PNG format, of course) is supplied in the files "pngbar.png" and "pngbar.jpg

(88x31) and "pngnow.png" (98x31). Page 4-15 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Libpng is OSI Certified Open Source Software. OSI Certified Open Source is a certification mark of the Open Source Initiative. Glenn Randers-Pehrson glennrp at users.sourceforge.net February 14, 2009 Bzip2 This program, "bzip2", the associated library "libbzip2", and all documentation, are copyright (C) 1996-2007 Julian R Seward. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 3. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 4. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Julian Seward, jseward@bzip.org USB library functions Atmel Corporation 2325 Orchard Parkway San Jose, Ca 95131 Copyright (c) 2004 Atmel Page 4-16 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Apache Apache License Version 2.0, January 2004 http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition,

"control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work

(an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted"

Page 4-17 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable

(except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one Page 4-18 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, Page 4-19 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]"

replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License");

you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Page 4-20 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement D3 JS library Copyright (c) 2013, Michael Bostock All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

* The name Michael Bostock may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"

AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL MICHAEL BOSTOCK BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE Page 4-21 Chapter 4: Legal and regulatory information Compliance with safety standards Compliance with safety standards This section lists the safety specifications against which the PMP/PTP 450 platform has been tested and certified. It also describes how to keep RF exposure within safe limits. Electrical safety compliance The PMP/PTP 450 platform hardware has been tested for compliance to the electrical safety specifications listed in Table 66. Table 66 PMP 450 platform safety compliance specifications Region USA Canada Specification UL 60950 CSA C22.2 No.60950 International CB certified & certificate to IEC 60950 Electromagnetic compatibility (EMC) compliance The EMC specification type approvals that have been granted for PMP/PTP 450 platform are listed under Table 67. Table 67 EMC emissions compliance Region USA Canada Specification FCC Part 15 Class B RSS Gen and RSS 210 International EN 301 489-1 V1.9.2 EN 301 489-17 V2.1.1 Human exposure to radio frequency energy Relevant standards (USA and EC) applicable when working with RF equipment are:

ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz. Council recommendation of 12 July 1999 on the limitation of exposure of the general public to electromagnetic fields (0 Hz to 300 GHz) (1999/519/EC) and respective national regulations. Page 4-22 Chapter 4: Legal and regulatory information Compliance with safety standards Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 on the minimum health and safety requirements regarding the exposure of workers to the risks arising from physical agents (electromagnetic fields) (18th individual Directive within the meaning of Article 16(1) of Directive 89/391/EEC). US FCC limits for the general population. See the FCC web site at http://www.fcc.gov, and the policies, guidelines, and requirements in Part 1 of Title 47 of the Code of Federal Regulations, as well as the guidelines and suggestions for evaluating compliance in FCC OET Bulletin 65. Health Canada limits for the general population. See the Health Canada web site at http://www.hc-sc.gc.ca/ewh-semt/pubs/radiation/99ehd-dhm237/limits-limites_e.html and Safety Code 6. EN 50383:2002 to 2010 Basic standard for the calculation and measurement of electromagnetic field strength and SAR related to human exposure from radio base stations and fixed terminal stations for wireless telecommunication systems (110 MHz - 40 GHz). BS EN 50385:2002 Product standard to demonstrate the compliances of radio base stations and fixed terminal stations for wireless telecommunication systems with the basic restrictions or the reference levels related to human exposure to radio frequency electromagnetic fields (110 MHz 40 GHz) general public. ICNIRP (International Commission on Non-Ionizing Radiation Protection) guidelines for the general public. See the ICNIRP web site at http://www.icnirp.de/ and Guidelines for Limiting Exposure to Time-Varying Electric, Magnetic, and Electromagnetic Fields. Power density exposure limit Install the radios for the PMP/PTP 450 platform family of wireless solutions so as to provide and maintain the minimum separation distances from all persons. The applicable FCC power density exposure limit for RF energy in the 4.9, 5.4 and 5.8 GHz frequency bands is 10 W/m2 and in 900 MHz frequency band is 6 W/m2. For more information, see Human exposure to radio frequency energy on page 4-22. The applicable ISEDC power density exposure limit for RF energy in unlicensed bands is 0.02619 *

(f^(0.6834)), where f is the lowest frequency of the supported band. For licensed bands, the power density exposure limit is 0.6455 * (f^(0.5)), where f is the lowest frequency of the supported band. Page 4-23 Chapter 4: Legal and regulatory information Compliance with safety standards Calculation of power density The following calculation is based on the ANSI IEEE C95.1-1991 method, as that provides a worst case analysis. Details of the assessment to EN50383:2002 can be provided, if required. Peak power density in the far field of a radio frequency point source is calculated as follows:

Where:

S P G d Is:

power density in W/m2 maximum average transmit power capability of the radio, in W total Tx gain as a factor, converted from dB distance from point source, in m Rearranging terms to solve for distance yields:

Calculated distances and power compliance margins Table 69 and Table 71 shows calculated minimum separation distances, recommended distances and resulting margins for each frequency band and antenna combination for the USA and Canada. These are conservative distances that include compliance margins. At these and greater separation distances, the power density from the RF field is below generally accepted limits for the general population. PMP 450 platform equipment adheres to all applicable EIRP limits for transmit power when operating in MIMO mode. Separation distances and compliance margins include compensation for both transmitters. Explanation of terms used in Table 69 and Table 71:

P burst maximum average transmit power during transmit burst (Watt) P maximum average transmit power of the radio (Watt) G total transmit gain as a factor, converted from dB S power density (Watt/m2) d minimum safe separation distance from point source (meters) Page 4-24 24.dGPSSGPd.4. Chapter 4: Legal and regulatory information Compliance with safety standards Table 68 FCC minimum safe distances PMP 450m 5.1 GHz, 5.2 GHz, 5.4 GHz and 5.8 GHz Band (GHz) Antenna PG (W) S (W/ m2) d (m) 5.1 5.2 5.4 5.8 90 sector 90 sector 90 sector 90 sector 3.38 0.85 0.85 3.38 10 10 10 10 0.16 0.08 0.08 0.16 Page 4-25 Chapter 4: Legal and regulatory information Compliance with safety standards Table 69 FCC minimum safe distances PMP/PTP 450i 900 MHz, 4.9 GHz, 5.1 GHz, 5.2 GHz, 5.4 GHz and 5.8 GHz Band Antenna P burst P

(W)

(W) G

(dBi) S d

(W/ m2)

(m) Sector antenna

-

0.19 22.75 (13 dBi) 6.0 0.27 Omni-directional 0.2138 0.2512 20.0 (13 dBi) 10.0 0.17 90 sector antenna 0.2138 0.2512 50.0 (17 dBi) 10.0 0.26 2ft directional flat plate 0.2138 0.2512 631.0 (28 dBi) 10.0 0.93 4ft directional parabolic 0.851 0.1000 2344.0 (34.9 dBi) 10.0 1.14 6ft directional parabolic 0.1413 0.1659 5248.0 (37.2 dBi) 10.0 2.19 Omni-directional 0.170 0.200 20.0 (13.0 dBi) 90 sector 0.034 0.040 50.1 (17.0 dBi) 2ft directional flat plate 0.002 0.002 707.9 (28.5 dBi) 4ft directional parabolic 0.011 0.013 2818.4 (34.5 dBi) Omni-directional 0.036 0.042 20.0 (13.0 dBi) 90 sector 0.014 0.017 50.1 (17.0 dBi) 2ft directional flat plate 0.001 0.001 707.9 (28.5 dBi) 4ft directional parabolic 0.000 0.000 2818.4 (34.5 dBi) Omni-directional 0.036 0.042 20.0 (13.0 dBi) 90 sector 0.014 0.017 50.1 (17.0 dBi) 2ft directional flat plate 0.001 0.001 707.9 (28.5 dBi) 2ft directional parabolic 0.001 0.001 707.9 (28.5 dBi) 10 10 10 10 10 10 10 10 10 10 10 10 0.15 0.10 0.09 0.44 0.07 0.07 0.07 0.06 0.07 0.07 0.07 0.08 Omni-directional 0.24 0.28 20.0 (13 dBi) 10.0 0.18 90 sector 0.10 0.12 50.0 (17 dBi) 10.0 0.18 2ft directional flat plate 0.54 0.63 708.0 (28.5 dBi) 10.0 1.57 4ft directional parabolic 0.54 0.63 3388.0 (35.3 dBi) 10.0 3.43 6ft directional parabolic 0.54 0.63 6457.0 (38.1 dBi) 10.0 4.74 900 MHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz Page 4-26 Chapter 4: Legal and regulatory information Compliance with safety standards Table 70 ISEDC minimum safe distances PMP 450m 5.1, 5.2, 5.4 and 5.8 GHz Band (GHz) Antenna PG (W) S (W/ m2) d (m) 5.1 5.2 5.4 5.8 90 sector 90 sector 90 sector 90 sector 0.85 0.85 3.38 0.85 9.13 9.39 9.69 9.13 0.09 0.08 0.17 0.09 Table 71 ISEDC minimum safe distances PMP/PTP 450i 4.9 GHz and 5.8 GHz Band Antenna P burst P

(W)

(W) G

(dBi) S d

(W/ m2)

(m) 900 MHz 4.9 GHz 5.2 GHz 5.4 GHz 5.8 GHz Sector

-

.02 20.0 (13 dBi) 2.74 0.11 Omni-directional 0.214 0.251 20.0 (13 dBi) 8.71 0.20 90 sector 0.214 0.251 50.1 (17 dBi) 8.71 0.31 2ft directional flat plate 0.214 0.251 631.0 (28 dBi) 8.71 1.11 6ft directional parabolic 0.141 0.166 5248.0 (37.2 dBi) 8.71 Omni-directional 0.009 0.011 20.0 (13.0 dBi) 9.13 2.60 0.04 90 sector 0.012 0.014 50.1 (17.0 dBi) 9.13 0.06 2ft directional flat plate 0.001 0.001 707.9 (28.5 dBi) 9.13 0.07 2ft directional parabolic 0.001 0.001 707.9 (28.5 dBi) 9.13 0.06 Omni-directional 0.036 0.042 20.0 (13.0 dBi) 9.39 0.07 90 sector 0.014 0.017 50.1 (17.0 dBi) 2ft directional flat plate 0.001 0.001 707.9 (28.5 dBi) 9.39 9.39 0.07 0.07 2ft directional parabolic 0.001 0.001 707.9 (28.5 dBi) 9.39 0.06 Omni-directional 0.24 0.28 20.0 (13 dBi) 9.69 0.20 90 sector 0.10 0.12 50.1 (17 dBi) 9.69 0.20 2ft directional flat plate 0.54 0.63 707.9 (28.5 dBi) 9.69 1.67 4ft directional parabolic 0.54 0.63 3388.4 (35.3 dBi) 9.69 4.82 Page 4-27 Chapter 4: Legal and regulatory information Compliance with safety standards Table 72 FCC minimum safe distances PMP/PTP 450 900 MHz, 2.4 GHz, 3.65 GHz and 5 GHz P burst

(W) G

(dBi) S d

(W/ m2)

(m) 6 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 0.07 0.18 0.09 0.18 0.28 0.12 0.45 0.40 0.09 0.09 0.09 0.09 0.08 0.09 0.16 0.10 0.63 0.25 0.19 0.63 Band Antenna 900 MHz Yagi Sector Antenna 2.4 GHz Integrated Reflector Sector Antenna 3.65 GHz Integrated Reflector 0.032 0.079 0.158 0.040 0.316 0.316 0.25 13 (11 dBi) 50 (17 dBi) 6 (8 dBi) 100 (20 dBi) 32 (15 dBi) 6 (8 dBi) 100 (20 dBi) High-gain Ruggedized 0.25 79 (19 dBi) Sector Integrated Reflector CLIP LENS 0.025 0.126 0.003 0.020 0.032 40 (16 dBi) 8 (9 dBi) 316 (25 dBi) 50 (17 dBi) 28 (14.5 dBi) Integrated Dish (450d) 0.0032 316 (25 dBi) Sector Integrated Reflector CLIP LENS 0.079 0.158 0.158 0.158 0.158 40 (16 dBi) 8 (9 dBi) 316 (25 dBi) 50 (17 dBi) 28 (14.5 dBi) Integrated Dish (450d) 0.158 316 (25 dBi) 5.4 GHz 5.8 GHz Page 4-28 Chapter 4: Legal and regulatory information Compliance with safety standards Table 73 ISEDC minimum safe distances PMP/PTP 450 900 MHz, 2.4 GHz, 3.5/3.65 GHz and 5 GHz S

(W/ m2) 2.74 5.35 5.35 37.10 37.10 37.10 37.10 38.20 38.20 38.20 38.20 38.20 38.20 38.20 38.20 9.39 9.39 Band Antenna 900 MHz Yagi Sector Antenna 2.4 GHz 3.5 GHz Integrated Reflector Sector Integrated Reflector P burst

(W) G

(dBi) 0.316 0.079 0.158 0.040 0.316 0.316 0.316 13 (11 dBi) 50 (17 dBi) 6 (8 dBi) 32 (15 dBi) 6 (8 dBi) 100 (20 dBi) 100 (20 dBi) 5.35 3.65 GHz

(lower Canada) 3.65 GHz

(upper Canada) 5.4 GHz 5.8 GHz High-gain Ruggedized 0.316 79 (19 dBi) Sector Integrated Reflector 0.316 0.316 0.316 High-gain Ruggedized 0.316 Sector Integrated Reflector 0.316 0.316 0.20 32 (15 dBi) 6 (8 dBi) 100 (20 dBi) 79 (19 dBi) 32 (15 dBi) 6 (8 dBi) 100 (20 dBi) High-gain Ruggedized 0.003 79 (19 dBi) Integrated Dish (450d) 0.0032 316 (25 dBi) 9.39 Sector Integrated Reflector CLIP LENS 0.025 0.126 0.003 0.020 0.032 Sector Integrated Reflector CLIP LENS

.079 0.158 0.158 0.158 0.158 40 (16 dBi) 8 (9 dBi) 316 (25 dBi) 9.39 50 (17 dBi) 9.39 28 (14.5 dBi) 9.39 40 (16 dBi) 8 (9 dBi) 9.69 9.69 50 (17 dBi) 9.69 28 (14.5 dBi) 9.69 Integrated Dish (450d) 0.158 316 (25 dBi) 9.69 Page 4-29 d

(m) 0.35 0.24 0.12 0.24 0.15 0.06 0.26 0.23 0.15 0.06 0.26 0.23 0.14 0.06 0.20 0.23 0.09 0.09 0.09 0.09 0.09 0.09 0.16 0.10 0.25 0.19 0.64 316 (25 dBi) 9.69 0.064 Chapter 4: Legal and regulatory information Compliance with safety standards

(*1) P: maximum average transmit power capability of the radio including cable loss (Watt) Capacit de puissance d'mission moyenne maximale de la radio comprenant la perte dans les cble de connexion (W)

(*2) G: total transmit gain as a factor, converted from dB Gain total d'mission, converti partir de la valeur en dB

(*3) S: power density (W/m2) Densit de puissance (W/m2)

(*4) d: minimum distance from point source (meters) Distance minimale de source ponctuelle (en mtres) Note Gain of antenna in dBi = 10 * log(G). The regulations require that the power used for the calculations is the maximum power in the transmit burst subject to allowance for source-based time-averaging. At 5.4 GHz and EU 5.8 GHz, the products are generally limited to a fixed EIRP which can be achieved with the Integrated Antenna. The calculations above assume that the maximum EIRP allowed by the regulations is being transmitted. Remarque Gain de l'antenne en dBi = 10 * log(G). Les rglements exigent que la puissance utilise pour les calculs soit la puissance maximale de la rafale de transmission soumis une rduction pour prendre en compte le rapport cyclique pour les signaux moduls dans le temps. Pour une opration dans la CEE dans les bandes 5,4 GHz et 5,8 GHz, les produits sont gnralement limits une PIRE qui peut tre atteinte avec l'antenne intgre. Les calculs ci-dessus supposent que la PIRE maximale autorise par la rglementation est atteinte. Note If there are no EIRP limits in the country of deployment, use the distance calculations for FCC 5.8 GHz for all frequency bands. At FCC 5.8 GHz, for antennas between 0.6m (2ft) and 1.8m (6ft), alter the distance proportionally to the antenna gain. Remarque Si aucune limite de PIRE existe pour le pays de dploiement, utilisez les calculs de distance pour FCC 5,8 GHz pour toutes les bandes de frquence. Pour la band FCC 5,8 GHz et les antennes entre 0,6 m (2 pieds) et 1,8 m (6 pieds), modifier la distance proportionnellement au gain de l'antenne. Page 4-30 Chapter 4: Legal and regulatory information Compliance with radio regulations Compliance with radio regulations This section describes how the PMP/PTP 450 platform complies with the radio regulations that are in force in various countries. Caution Where necessary, the end user is responsible for obtaining any National licenses required to operate this product and these must be obtained before using the product in any particular country. Contact the appropriate national administrations for details of the conditions of use for the bands in question and any exceptions that might apply. Caution Changes or modifications not expressly approved by Cambium Networks could void the users authority to operate the system. Caution For the connectorized version of the product and in order to reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the Effective Isotropically Radiated Power (EIRP) is not more than that permitted for successful communication. Attention Le cas chant, l'utilisateur final est responsable de l'obtention des licences nationales ncessaires pour faire fonctionner ce produit. Celles-ci doivent tre obtenus avant d'utiliser le produit dans un pays particulier. Contactez les administrations nationales concernes pour les dtails des conditions d'utilisation des bandes en question, et toutes les exceptions qui pourraient s'appliquer Attention Les changements ou modifications non expressment approuvs par les rseaux de Cambium pourraient annuler l'autorit de l'utilisateur faire fonctionner le systme. Attention Pour la version du produit avec une antenne externe, et afin de rduire le risque d'interfrence avec d'autres utilisateurs, le type d'antenne et son gain doivent tre choisis afin que la puissance isotrope rayonne quivalente (PIRE) ne soit pas suprieure au minimum ncessaire pour tablir une liaison de la qualit requise. Page 4-31 Chapter 4: Legal and regulatory information Compliance with radio regulations Type approvals This system has achieved Type Approval in various countries around the world. This means that the system has been tested against various local technical regulations and found to comply. The frequency bands in which the system operates may be unlicensed and, in these bands, the system can be used provided it does not cause interference. The system is not guaranteed protection against interference from other products and installations. The radio specification type approvals that have been granted for 450 platform frequency variants are listed under Table 74. Table 74 Radio certifications Region/Country Band Specification Brazil 4.9 GHz ANATEL, RESOLUO N 633, DE 14 DE MARO DE 2014 5.4 GHz ANATEL, RESOLUTION No. 506, FROM JULY 1, 2008 5.8 GHz ANATEL, RESOLUTION No. 506, FROM JULY 1, 2008 Mexico 900 MHz NOM-121-SCT1-2009 4.9 GHz Protocol Between the UNITED STATES OF AMERICA and MEXICO Use of 4940 to 4990 MHz band. 5.4 GHz Acuerdo del 27 de noviembre de 2012 5.8 GHz NOM-121-SCT1-2009 USA 900 MHz FCC Part 15.247 2.4 GHz FCC Part 15 Class B 3.6 GHz FCC Part 15 Class B 4.9 GHz FCC 47 CFR Part 90 5.1 GHz FCC 47 CFR Part 15 E 5.2 GHz 5.4 GHz FCC 47 CFR Part 15 E FCC 47 CFR Part 15 E 5.8 GHz FCC 47 CFR Part 15 C Canada 900 MHz RSS Gen and RSS 210 2.4 GHz RSS Gen and RSS 210 3.5 /3.6 GHz RSS Gen and RSS 192 4.9 GHz 5.8 GHz IC RSS-111, Issue 5 IC RSS-247, Issue 1 Europe 3.5 GHz ETSI EN 302 326-2 V1.2.2 Page 4-32 Chapter 4: Legal and regulatory information Compliance with radio regulations 4.9 GHz ETSI EN302 625; V1.1.1 Broadband Disaster Relief 5.4 GHz ETSI EN 301 893 V1.7.1 5.8 GHz ETSI EN 302 502 V1.2.1 Brazil specific information Brazil notification For compliant operation in the 5.4 GHz band, the Equivalent Isotropic Radiated Power from the integrated antenna or connectorized antenna shall not exceed 30 dBm (0.5 W). The operator is responsible for enabling the DFS feature on any Canopy 5.4 GHz radio by setting the Country Code to Brazil, including after the module is reset to factory defaults. Important Note: This equipment operates as a secondary application, so it has no rights against harmful interference, even if generated by similar equipment, and cannot cause harmful interference on systems operating as primary applications. Brazil certification numbers The Anatel certification number for Brazil for the PMP/PTP 450i is 2426-15-7745. Australia Notification 900 MHz modules must be set to transmit and receive only on center channels of 920, 922, or 923 MHz so as to stay within the ACMA approved band of 915 MHz to 928 MHz for the class license and not interfere with other approved users. After taking into account antenna gain (in dBi), 900 MHz modules transmitter output power (in dBm) must be set to stay within the legal regulatory limit of 30 dBm (1 W) EIRP for this 900 MHz frequency band. Regulatory Requirements for CEPT Member States

(www.cept.org) When operated in accordance with the instructions for use, Cambium Wireless equipment operating in the 5.1 GHz and 5.4 GHz bands is compliant with CEPT Resolution 229 (REV. WRC-12). Operating the PMP/PTP 450 platform in the bands 5150 to 5350 MHz and 5470 to 5725 MHz is granted providing it is not causing interference to the existing primary services allocated to those bands. For compliant operation in the 5250 to 5350 MHz band, the transmit power from the integrated antenna or a connectorized antenna shall be limited to a maximum mean EIRP of 200 mW and a maximum mean EIRP density of 10 mW/MHz in any 1 MHz band. Page 4-33 Chapter 4: Legal and regulatory information Compliance with radio regulations For compliant operation in the 5470 to 5725 MHz band, the transmit power shall be restricted to a maximum of 250 mW with a maximum mean EIRP of 1 W and a maximum mean EIRP density of 50 mW/MHz in any 1 MHz band. For compliant operation in the bands 5 250-5 350 MHz and 5 470-5 725 MHz, the PMP/PTP 450 platform employs transmitter power control. For EU member states, RLAN equipment in the 5.4GHz bands is exempt from individual licensing under Commission Recommendation 2003/203/EC. Contact the appropriate national administrations for details on the conditions of use for the bands in question and any exceptions that might apply. Also see www.ero.dk for further information. Cambium Radio equipment operating in the 5470 to 5725 MHz band are categorized as Class 1 devices within the EU in accordance with ECC DEC(04)08 and are CE marked to show compliance with the European Radio & Telecommunications Terminal Equipment

(R&TTE) directive 1999/5/EC. The relevant Declaration of Conformity can be found at http://www.cambiumnetworks.com/support/ec_doc/ . A European Commission decision, implemented by Member States on 31 October 2005, makes the frequency band 5470-5725 MHz available in all EU Member States for wireless access systems. Under this decision, the designation of Canopy 5.4GHz products become Class 1 devices and these do not require notification under article 6, section 4 of the R&TTE Directive. Consequently, these 5.4GHz products are only marked with the symbol and may be used in any member state. Page 4-34 Chapter 5: Preparing for installation This chapter describes how to stage and test the hardware for a PMP 450 platform network. This chapter is arranged as follows:

Safety on page 5-2: Describes the precautions to be observed and checks to be performed before proceeding with the installation Preparing for installation on page 5-5: Describes the pre-configuration procedure before proceed with installation. Testing system components on page 5-7: Describes the procedures for unpacking and performing and initial staging of the PMP/PTP 450 platform equipment Configuring Link for Test on page 5-15: Describes the procedures for testing the equipments radio links. Page 5-1 Chapter 5: Preparing for installation Safety Safety Warning To prevent loss of life or physical injury, observe the following safety guidelines. In no event shall Cambium Networks be liable for any injury or damage caused during the installation of the Cambium PMP/PTP 450 platform. Ensure that only qualified personnel install a PMP/PTP 450 platform link. Power lines Exercise extreme care when working near power lines. Working at heights Exercise extreme care when working at heights. Power supply Always use one of the Cambium PMP/PTP 450 platform Series power supply units (PSU) to power the ODU. Failure to use a Cambium supplied PoE could result in equipment damage and will invalidate the safety certification and may cause a safety hazard. Grounding and protective earth The Outdoor Unit (ODU) must be properly grounded to protect against lightning. It is the users responsibility to install the equipment in accordance with national regulations. In the USA follow the requirements of the National Electrical code NFPA 70-2005 and 780-2004 Installation of Lightning Protection Systems. In Canada, follow Section 54 of the Canadian Electrical Code. 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. Powering down before servicing Always power down and unplug the equipment before servicing. Page 5-2 Chapter 5: Preparing for installation Safety Primary disconnect device The ODU power supply is the primary disconnect device. External cables Safety may be compromised if outdoor rated cables are not used for connections that will be exposed to the outdoor environment. For outdoor copper Cat5e Ethernet interfaces, always use Cat5e cable that is gel-filled and shielded with copper-plated steel. RF exposure near the antenna Strong radio frequency (RF) fields will be present close to the antenna when the transmitter is on. Always turn off the power to the ODU before undertaking maintenance activities in front of the antenna. Minimum separation distances Ensure that personnel are not exposed to unsafe levels of RF energy. The units start to radiate RF energy as soon as they are powered up. Never work in front of the antenna when the ODU is powered. Install the ODUs so as to provide and maintain the minimum separation distances from all persons. For minimum separation distances, see Calculated distances and power compliance margins on page 4-24. Grounding and lightning protection requirements Ensure that the installation meets the requirements defined in Grounding and lightning protection on page 3-8. Grounding cable installation methods To provide effective protection against lightning induced surges, observe these requirements:

Grounding conductor runs are as short, straight and smooth as possible, with bends and curves kept to a minimum. Grounding cables must not be installed with drip loops. All bends must have a minimum radius of 200 mm (8 in) and a minimum angle of 90. A diagonal run is preferable to a bend, even though it does not follow the contour or run parallel to the supporting structure. All bends, curves and connections must be routed towards the grounding electrode system, ground rod, or ground bar. Page 5-3 Chapter 5: Preparing for installation Safety Grounding conductors must be securely fastened. Braided grounding conductors must not be used. Approved bonding techniques must be used for the connection of dissimilar metals. Siting ODUs and antennas ODUs, external antennas and GPS receivers are not designed to survive direct lightning strikes. For this reason they must be installed in Zone B as defined in Lightning protection zones on page 3-9. Mounting in Zone A may put equipment, structures and life at risk. Thermal Safety The ODU enclosure may be hot to the touch when in operation. The ODU must not be operated in ambient temperatures exceeding 40C unless mounted in a Restricted Access Location. For more information, see ODU ambient temperature limits on page 3-10. Warning Do not install the ODU in a location where the ambient temperature could exceed 40C unless this is a Restricted Access Location as defined by EN 60950-1. Alerte Lunit externe ne doit pas tre installe dans un endroit o la temprature ambiante est suprieure 40C moins que laccs soit limit au personnel autoris. Page 5-4 Chapter 5: Preparing for installation Preparing for installation Preparing for installation ODU pre-configuration It is common practice to pre-configure the units during staging before site installation by performing the following tasks:

Connecting to the unit Configuring IP and Ethernet interfaces Upgrading the software version and using CNUT General configuration Configuring security Configuring radio parameters Setting up SNMP agent Configuring syslog Configuring remote access Monitoring the Link Configuring quality of service Zero Touch Configuration Using DHCP Option 66 Configuring Radio via config file Configuring a RADIUS server If the units are to be pre-configured during staging, the safety precautions below MUST be observed. Preparing personnel In no event shall Cambium Networks be liable for any injury or damage caused during the installation of the Cambium PMP/PTP 450 platform equipment. Ensure that only qualified personnel undertake the installation of a PMP/PTP 450 platform system. Ensure that all safety precautions are observed. Preparing inventory Perform the following inventory checks:

Check that the correct components are available, as described in Ordering the components on page 2-43. Check the contents of all packages against their packing lists. Page 5-5 Chapter 5: Preparing for installation Preparing for installation Preparing tools Check that following specific tools are available, in addition to general tools:

RJ45 crimp tool (it must be the correct tool for the type of RJ45 being used). Personal Computer (PC) with 10 or 100 or 1000 BaseT Ethernet port Internet Explorer or Firefox Ethernet patch cables Page 5-6 Chapter 5: Preparing for installation Testing system components Testing system components The best practice is to connect all componentsAP/BHM, SMs/BHS, GPS antenna (if applicable) and CMM (if applicable)in a test setting and initially configure and verify them before deploying them to an installation. In this way, any configuration issues are worked out before going on-site, on a tower, in the weather, where the discovery of configuration issues or marginal hardware is more problematic and work-flow affecting. Unpacking Components When a delivery arrives, inspect all packages immediately for damages. Carefully unpack the equipment, verify that all the components have arrived as per order and are in good condition. Save all packaging materials for equipment transportation to the installation site. Preparing the ODU After the equipment is unpacked, the units may be configured for staging tests. Use either of two methods to configure an AP/BHM:

Use the Quick Start feature of the product (via GUI menu Quick Start) Manually set each parameter After changing configuration parameters on a GUI web page:

Before you leave a web page, click the Save button to save the change(s) After making change(s) on multiple web pages, click the Reboot button to reboot the module and implement the change(s) Configuring the Computing Device for Test If the computer is configured for Dynamic Host Configuration Protocol (DHCP), disconnect the computer from the network. If the computer is instead configured for static IP addressing Set the static address in the 169.254 network Set the subnet mask to 255.255.0.0. For detailed instructions, see section Configuring the management PC on page 5-15. Page 5-7 Chapter 5: Preparing for installation Testing system components Factory default Configuration From the factory, the APs/BHMs and SMs/BHSs are all configured to not transmit on any frequency. This configuration ensures that equipment operators do not accidentally turn on an unsynchronized module. Site synchronization of modules is required because modules:

o cannot transmit and receive signals at the same time. o use TDD (Time Division Duplexing) to distribute signal access of the downlink and uplink frames. when one module transmits while an unintended module nearby receives signal, the transmitting module may interfere with or desense the receiving module. In this context, interference is self-interference (within the same network). ODU interfaces See section PMP/PTP 450 platform interfaces on page 2-7 ODU diagnostic LEDs See section AP/BHM LEDs on page 2-12. See section SM/BHS LEDs on page 2-13. Recommended Tools for Installation The following tools may be needed for installation:

Table 75 Tools for PMP and PTP 450 platform equipment installation Equipment to Be Tools Required Installed AP or BHM 3 mm Allen Wrench Used for connecting the antenna mating bracket to the rear of the AP housing Crescent Wrench Pair Used for tightening cable glands Self-amalgamating and PVC Tape Used for weatherproofing N-type connections Page 5-8 Chapter 5: Preparing for installation Testing system components Equipment to Be Tools Required Installed AP or BHM or BHS 13 mm Spanner Wrench (or Ratchet Spanner Wrench) Pair Antenna Used for connecting the antenna (sector or omni for AP, or directional for BH)base to the pole/mast mounting bracket Self-amalgamating and PVC Tape Used for weatherproofing N-type connections N-type Torque Wrench (not required but recommended) Used for assuring proper tightening of N-type connectors terminating the RF cables SM Wrench/driver (depending on operators choice of clamps) Used for tightening clamps to the pole Alignment tone adapter / headset Used for aligning the SM to the AP Universal Global Philips Screwdriver Positioning System Used for attaching the UGPS unit to the pole/mast mounting bracket 13mm Spanner Wrench (or Ratchet Spanner Wrench) Used for connecting the mounting brackets U-bolt to the antenna or mast Cabling Electricians Scissors or Wire Cutters Used for cutting wire to length RJ-11/RJ-45 Crimping Tool Used for stripping RJ-11/RJ-45 cables and for terminating cable ends Cable Testing Device Used to ensure that cables are properly constructed Standards for Wiring Modules automatically sense whether the Ethernet cable in a connection is wired as straight-

through or crossover. Operators may use either straight-through or crossover cable to connect a network interface card (NIC), hub, router, or switch to these modules. For a straight-through cable, use the EIA/TIA-568B wire color-code standard on both ends. For a crossover cable, use the EIA/TIA-568B wire color-code standard on one end, and the EIA/TIA-568A wire color-code standard on the other end. Page 5-9 Chapter 5: Preparing for installation Testing system components Best Practices for Cabling The following practices are essential to the reliability and longevity of cabled connections:

Use only shielded cables to resist interference. For vertical runs, provide cable support and strain relief. Include a 2-ft (0.6-m) service loop on each end of the cable to allow for thermal expansion and contraction and to facilitate terminating the cable again when needed. Include a drip loop to shed water so that most of the water does not reach the connector at the device. Properly crimp all connectors. Use dielectric grease on all connectors to resist corrosion. Use only shielded connectors to resist interference and corrosion. Wiring Connectors The following diagrams correlate pins to wire colors and illustrate crossovers where applicable. Pin 1, relative to the lock tab on the connector of a straight-through cable is located as shown below. Figure 42 Pin 1 location Page 5-10 Chapter 5: Preparing for installation Testing system components Main port pinout Table 76 Main port pinout RJ45 pin Description 1 2 3 4 5 6 7 8

+TxRx0 TxRx0

+TxRx1

+TxRx2 TxRx2 TxRx1

+TxRx3 TxRx3 Aux port pinout Table 77 Aux port pinout RJ45 pin Description 1 2 3 4 5 6 7 8

+TxRx0 TxRx0

+TxRx1 GPS power out, Alignment tone out, GPS data out GPS data in TxRx1 GPS 0v GPS Sync in Page 5-11 Chapter 5: Preparing for installation Testing system components RJ-45 Pinout for Straight-through Ethernet Cable Figure 43 Straight-through Ethernet Cable RJ45 Connector (Bottom) Straight-Through Cable

``

8 7 6 5 4 3 2 1 RJ45 Connector (Top) 8 7 6 5 4 3 2 1 Table 78 RJ-45 pinout for straight-through Ethernet cable Pin Signal Pair Color TP1+

TP1-

TP2+

TP3-

TP3+

TP2-

TP4+

TP4-

2 2 3 1 1 3 4 4 White/orange stripe Orange solid White/green stripe Blue solid White/blue stripe Green solid White/brown stripe Brown solid 1 2 3 4 5 6 7 8 RJ-45 Pinout for Crossover Ethernet Cable Page 5-12 Chapter 5: Preparing for installation Testing system components Table 79 RJ-45 pinout for crossover Ethernet cable Connection 1 Connection 2 Signal Pair Color Signal Pair Color TP2+

TP2-

TP1+

TP3-

TP3+

TP1-

TP4+

TP4-

3 3 2 1 1 2 4 4 White/green stripe TP1+

Green solid TP1-

White/orange stripe TP2+

Blue solid TP3-

White/blue stripe TP3+

Orange solid TP2-

White/brown stripe TP4+

Brown solid TP4-

2 2 3 1 1 3 4 4 White/orange stripe Orange solid White/green stripe Blue solid White/blue stripe Green solid White/brown stripe Brown solid Pin 1 2 3 4 5 6 7 8 AP/BHM to UGPS cable The AP/BHM to UGPS cable can be constructed from RJ12 to RJ 45 cable using the ping configuration described in Table 80. Figure 44 AP/BHM to UGPS cable RJ45 Connector (Bottom) Straight-Through Cable RJ12 Connector (Top)

``

8 7 6 5 4 3 2 1 Table 80 AP/BHM to UGPS cable pinout Pin 450i AP RJ 45 Connector Pin UGPS RJ 12 Connector Connector 1 2 3 4 5 NC NC NC 4 on RJ 12 3 on RJ 12 1 2 3 4 5 8 on RJ 45 NC 5 on RJ 45 4 on RJ 45 NC Page 5-13 6 NC 5 4 3 NC 2 1 Chapter 5: Preparing for installation Testing system components 6 7 8 NC 6 7 on RJ 45 6 on RJ 12 1 on RJ 12 Note The AP/BHM will only power up the UGPS if it configured to do so. Alignment tone cable The alignment tone cable is constructed using RJ45 plug and Stereo plug. The pin configuration is shown inFigure 45 Figure 45 Alignment tone cable pin configuration

#8

#1 Pin 7 Pin 4 Resistors 220 220 Left Right Common Override plug cable To construct an override plug, perform the following steps:

Crip a RJ-11 6 pin connector onto a 6 inch length of CAT 5 cable Pin out all 6 pins Short (solder together) pins 4 and 6 on the other end. Do not connect any other wires to anything. Figure 46 RJ-11 pinout for the default plug RJ12 Connector (Bottom) Override plug cable wiring 6 5 4 3 2 1

``

Not used Not used Tie together Not used Page 5-14 Chapter 5: Preparing for installation Configuring Link for Test Configuring Link for Test It is important to stage the AP/BHM and SM/BHS units first to verify proper registration before deploying the modules to the site. To begin configuring the modules for test, see the sections below:

Configuring the management PC To configure the local management PC to communicate with the AP, SM, BHM or BHS, proceed as follows:

Powering the AP/SM/BH for test configuration Perform the following steps to power on the ODU. Procedure 2 Powering the ODU 1 2 3 Plug one end of a CAT 5 Ethernet cable into the ODU. Plug the Ethernet cable connector labeled To Radio into the jack in the pig tail that hangs from the power supply. Plug the other connector of the pig tail (this connector labeled To Computer) into the Ethernet jack of the computing device. 4 Plug the power supply into an electrical outlet. Warning From this point until you remove power from the ODU, stay at least as far from the AP as the minimum separation distance specified in Minimum separation distances on page 5-3. 5 6 Power up the computing device Start the browser in the computing device The AP/BHM interface provides a series of web pages to configure and monitor the unit. Access web-based interface through a computing device that is either directly connected or connected through a network to the AP/BHM. If the computing device is not connected to a network when it is being configured for test environment, and if the computer has used a proxy server address and port to configure a module, then the operator may need to first disable the proxy setting in the computer. Page 5-15 Chapter 5: Preparing for installation Configuring Link for Test Perform the following procedure to toggle the computer to not use the proxy setting. Procedure 3 Bypassing browser proxy settings to access module web pages 1 2 Launch Microsoft Internet Explorer Select Tools, Internet Options, Connections, LAN Settings. Alternate web browser menu selections may differ. 3 Uncheck the Use a proxy server box. In the address bar of your browser, enter the IP address of the AP/BHM. (For example, enter http://169.254.1.1 to access the AP/BHM through its default IP address). The AP/BHM responds by opening the General Status tab of its Home page. Logging into the web interface AP/SM/BH Procedure 4 Logging into the web interface 1 2 3 Plug one end of a CAT 5 Ethernet cable into the AP/BHM Plug the Ethernet cable connector labeled To Radio into the jack in the pig tail that hangs from the power supply. Plug the other connector of the pig tail (this connector labeled To Computer) into the Ethernet jack of the computing device. 4 Plug the power supply into an electrical outlet. Warning From this point until you remove power from the ODU, stay at least as far from the ODU as the minimum separation distance specified in Minimum separation distances on page 5-3. Using the Quick Start Configuration Wizard of the AP/BHM See section Quick link setup on page 7-81. Page 5-16

 

 

Chapter 6: Installation This chapter describes how to install and test the hardware for a PMP/PTP 450 platform link. It contains the following topics:

ODU variants and mounting bracket options on page 6-2 provides details of six different bracket options, including the type of ODU and range of pole diameters supported by each option. Mount the ODU, LPU and surge suppressor on page 6-3 describes how to mount and ground an integrated or connectorized ODU, how to mount and ground the top LPU. Installing the copper Cat5e Ethernet interface on page 6-17 describes how to install the copper Cat5e power over Ethernet interface from the ODU to the PSU. Installing external antennas to a connectorized ODU on page 6-21 describes how to install external antennas for a connectorized ODU. Installing ODU on page 6-56 describes how to install PTP and PMP ODU radios. Installing the AC Power Injector on page 6-61 describes how to install a power supply unit for the PMP/PTP 450 platform, either the AC Power Injector. Supplemental installation information on page 6-64 contains detailed installation procedures that are not included in the above topics, such as how to strip cables, create grounding points and weatherproof connectors. Note These instructions assume that LPUs are being installed from the PMP/PTP 450 platform LPU and grounding kit (Cambium part number C000065L007). If the installation does not require LPUs, adapt these instructions as appropriate. If LPUs are being installed, only use the five black-capped EMC cable glands supplied in the LPU and grounding kit. The silver-capped cable glands supplied in the ODU kits must only be used in PMP/PTP 450 platform installations which do not require LPUs. Page 6-1 Chapter 6: Installation ODU variants and mounting bracket options ODU variants and mounting bracket options Mounting bracket PMP/PTP 450i The PMP/PTP 450i series supports below mentioned mounting bracket option:

Table 81 PMP/PTP 450i ODU mounting bracket part numbers Cambium description Cambium part number Mounting bracket low profile adjustable N000045L002A The low profile bracket provides elevation adjustment with the PMP/PTP 450i Integrated ODUs of

+10 to 5 or +5 to 10. A larger adjustment range is available using the standard integrated mounting bracket. The connectorized mounting bracket does not provide elevation adjustment. Mounting bracket PMP 450 900 MHz SM The PMP 450i 900 MHz SM has special mounting bracket option. The PMP 450i 900 MHz AP mounting procedure is the same as the other 450i radios. The 900 450 SM has a different mounting bracket which is supplied along with yagi antenna. Page 6-2 Chapter 6: Installation Mount the ODU, LPU and surge suppressor Mount the ODU, LPU and surge suppressor To install the ODU and top LPU, use the following procedures:

Attach ground cables to the ODU on page 6-3 Mount the ODU on the mast on page 6-6 Mount the top LPU on page 6-9 Mount the Surge Suppressor on page 6-9 Attach ground cables to the ODU PMP 450m Series AP 1 Fasten an AWG 10 (or 6mm2) copper ground cable to each ODU grounding point using the M6 (small) lugs. 2 Tighten the Ground post screws. 3 Securely connect the copper wires to the grounding system (Protective Earth) and the LPU or Gigabit Ethernet Surge Suppressor according to applicable regulations. Page 6-3 Chapter 6: Installation Mount the ODU, LPU and surge suppressor PMP/PTP 450i Series AP/SM/BH, PMP 450 3GHz Ruggedized SM 1 Fasten an AWG 10 (or 6mm2) copper ground cable to each ODU grounding point using the 1 M6 (small) lugs. 2 Tighten the Ground post screws. 2 3 Securely connect the copper wires to the grounding system (Protective Earth) and the LPU or Gigabit Ethernet Surge Suppressor according to applicable regulations. Page 6-4 Chapter 6: Installation Mount the ODU, LPU and surge suppressor PMP 450 AP 1 Fasten an AWG 10 (or 6mm2) copper ground cable to each ODU grounding point using the M6 (small) lugs 2 Tighten the Ground post locking nut in the copper wire 1 2 3 Securely connect the copper wire to the grounding system (Protective Earth) according to applicable regulations. PMP 450 SM 1 Fasten an AWG 10 (or 6mm2) copper ground cable to each ODU grounding point using the 1 M6 (small) lugs 2 Tighten the Ground post locking nut in the copper wire 2 Page 6-5 Chapter 6: Installation Mount the ODU, LPU and surge suppressor 3 Securely connect the copper wire to the grounding system (Protective Earth) according to applicable regulations. The grounding point on PMP 450 900 MHz SM is different from 2.4, 3.5/3.65 and 5 GHz PMP 450 SMs as shown in Figure 47. Figure 47 PMP 450 900 MHz SM grounding Mount the ODU on the mast PMP 450m Series AP 1 See - PMP 450m Series AP on page 6-49 for Installion for an integrated ODU 2 Remove the rear bracket strap from upper and lower brackets of ODU 3 Attach the upper and lower bracket of ODU to the mount point by closing the rear strap around the pole 4 Tighten the four serrated flange M10 nuts on upper and lower rear strap using a 17 mm spanner wrench. These must be tightened evenly on the pol to avoid jumping/stripping threads Page 6-6 Chapter 6: Installation Mount the ODU, LPU and surge suppressor PMP/PTP 450i Series AP/SM/BH, PMP 450 3 GHz Ruggedized SM Caution Do not reverse the bracket clamp, as this arrangement may lead to failure of the assembly. Do not over-tighten the bolts as this may lead to failure of the assembly. 1 Fix the mounting plate to the back of the ODU using the four bolts, and spring and plain washers provided. Tighten the bolts. 2 Attach the bracket body to the mounting plate using the M8 bolt, spring and plain washers. 3 Hoist the ODU to the mounting position 4 Attach the bracket body to the pole using the bracket clamp, M8 bolts, and spring and plain washers. 5 Adjust the elevation and azimuth to achieve visual alignment. PMP 450 AP 1 Using an 8mm nut driver, attach the pole mounts AP housing bracket to the unit using the 4 M5 x 16mm bolts included with the AP. 2 Using the included (depending on pole diameter):

M8 x 70mm hex cap bolts ( 2 quantity) or M8 x 40mm hex cap bolts ( 2 quantity) and M8 flat washers ( 2 quantity) M8 coil washers ( 2 quantity) Attach the mounting bracket to the pole/mast. The mounting bracket is designed to attach to poles with diameters in the range of 2 in. (50mm) to 3in. (75mm). Page 6-7 Chapter 6: Installation Mount the ODU, LPU and surge suppressor 3 Complete the AP mounting assembly by attaching the included:

8mm hex cap bolt ( one quantity) Through the APs attached mounting bracket and pole mount. At this time the AP may be adjusted to the desired position and tightened with a 1/2 inch spanner wrench to 11 lb/ft (14Nm). PMP 450 SM (except PMP 450 SM - 900 MHz) 1 Use stainless steel hose clamps for the attachment. 2 Attach the mounting bracket to the structure. Tighten the locking nut. PMP 450 900 MHz SM (connectorized) The PMP 450 900 MHz connectorized SM mounting procedure is different from other radios. It does not get directly mounted on pole. 1 Align the 900 MHz SM to E bracket of Yagi antenna 2 Slide the radio towards right to lock on the antenna Slide towards right to lock Page 6-8 Stainless steel hose clamps Reflector dish arm Chapter 6: Installation Mount the ODU, LPU and surge suppressor Mount the top LPU 1 For separate LPU mounting, use the U-bolt bracket from the LPU kit to mount the top LPU on the pole below the ODU. Tighten to a torque setting of 7.0 Nm (5.2 lb ft). Please refer Gigabit LPU and Grounding Kit Installation Guide for more details. Mount the Surge Suppressor PMP/PTP 450i Series Gigabit Ethernet Surge Suppressors are installed at both ends of the drop cable. One within 600 mm (24) space of and under the ODU. The other located within 600 mm (24) space of the building entry point. Quick procedure:

The quick procedure for the Surge Suppressor for PMP/PTP 450i Series mounting is as follows:

1 Ground using the terminal on the back of the units. Use the supplied Tubular Lug and 6 mm2

(10 AWG) stranded cable, max length 600 mm

(24). I. Waterproof the cable lug with heat shrink sleeving. II. Secure the Cable assembly to the unit using the supplied screw and washer. 2 Mounting the Gigabit Ethernet Surge Suppressor on wall or pole Page 6-9 Chapter 6: Installation Mount the ODU, LPU and surge suppressor 3 Connecting the two CAT5e cables to the Gigabit Ethernet Surge Suppressor 4 Slide the end cap over the bottom of the Gigabit Surge Suppressor, ensuring it clicks firmly in place Please refer Gigabit Ethernet Surge Suppressor Installation Guide for more details. Figure 48 Gigabit Surge Suppressor Page 6-10 Chapter 6: Installation Mount the ODU, LPU and surge suppressor PMP/PTP 450 Series The PMP/PTP 450 Series uses 600SSH Surge Suppressor. The inside of the surge suppressor is shown in Figure 49. Caution The PMP 450 900 MHz SM is based off the 450 platform, be sure to use a 600SS to protect this radio type. Figure 49 600SSH Surge Suppressor inside Key to Callouts 600SSH 1 Holesfor mounting the Surge Suppressor to a flat surface (such as an outside wall). The distance between centers is 4.25 inches (108 mm). 2 RJ-45 connectorsOne side (neither side is better than the other for this purpose) connects to the product (AP, SM, or cluster management module). The other connects to the AC adaptors Ethernet connector. 3 Ground post and washeruse heavy gauge (10 AWG or 6 mm2) copper wire for connection. Refer to local electrical codes for exact specifications. 4 Ground Cable Openingroute the 10 AWG (6 mm2) ground cable through this opening. 5 CAT-5 Cable Knockoutsroute the two CAT-5 cables through these openings, or alternatively through the Conduit Knockouts. 6 Conduit Knockoutson the back of the case, near the bottom. Available for installations where cable is routed through building conduit. Note The 600SSH surge suppressor is shipped in the isolated position (pin 4 isolated by 68V from protective earth). If packet error issues occur over the Ethernet link (verify by pinging the device through the 600SSH), configure the 600SSH to grounded position (by moving the 600SSH switch from isolated to ground) to avoid ground loops that may be present in the system. Page 6-11 Chapter 6: Installation Mount the ODU, LPU and surge suppressor The mounting procedure for the Surge Suppressor for PMP/PTP 450 Series is as follows:

1 Remove the cover of the 600SSH Surge Suppressor. 2 With the cable openings facing downward, mount the 600SSH to the outside of the subscriber premises, as close to the point where the Ethernet cable penetrates the residence or building as possible, and as close to the grounding system (Protective Earth) as possible. 3 Wrap an AWG 10 (or 6mm2) copper wire around the Ground post of the 600SSH. 4 5 Tighten the Ground post locking nut in the 600SSH onto the copper wire. Securely connect the copper wire to the grounding system (Protective Earth) according to applicable regulations. 6 Using diagonal cutters or long nose pliers, remove the knockouts that cover the cable openings to the 600SSH. 7 Pack both of the surge suppressor Ethernet jacks with dielectric grease. 8 Wrap an AWG 10 (or 6mm2) copper wire around the Ground post of the 600SSH. 9 Tighten the Ground post locking nut in the 600SSH onto the copper wire. 10 Securely connect the copper wire to the grounding system (Protective Earth) according to applicable regulations. 11 Using diagonal cutters or long nose pliers, remove the knockouts that cover the cable openings to the 600SSH. 12 Pack both of the surge suppressor Ethernet jacks with dielectric grease. 13 Wrap a splice loop in the loose end of the Ethernet cable from the SM. 14 Connect that cable to one of the Ethernet jacks. 15 Connect an Ethernet cable to the other Ethernet jack of the 600SSH and to the power adapter. 16 Replace the cover of the 600SSH. General protection installation To adequately protect a 450 platform installation, both ground bonding and transient voltage surge suppression are required. Basic requirements The following basic protection requirements must be implemented:

ODU must be in Zone B (see Lightning protection zones on page 3-9). ODU must be grounded to the supporting structure. A surge suppression unit must be installed on the outside of the building. Page 6-12 Chapter 6: Installation Mount the ODU, LPU and surge suppressor The distance between the ODU and Gigabit Surge Suppressor should be kept to a minimum. The drop cable must not be laid alongside a lightning air terminal. All grounding cables must be a minimum size of 10 mm2 csa (8AWG), preferably 16 mm2 csa

(6AWG), or 25 mm2 csa (4AWG). Grounding cable requirements When routing, fastening and connecting grounding cables, the following requirements must be implemented:

Grounding conductors must be run as short, straight, and smoothly as possible, with the fewest possible number of bends and curves. Grounding cables must not be installed with drip loops. All bends must have a minimum radius of 203 mm (8 in) and a minimum angle of 90 (Figure 50). A diagonal run is preferable to a bend, even though it does not follow the contour or run parallel to the supporting structure. All bends, curves and connections must be routed towards the grounding electrode system, ground rod, or ground bar. Grounding conductors must be securely fastened. Braided grounding conductors must not be used. Approved bonding techniques must be used for the connection of dissimilar metals. Figure 50 Grounding cable minimum bend radius and angle Caution Do not attach grounding cables to the ODU mounting bracket bolts, as this arrangement will not provide full protection. Page 6-13 Chapter 6: Installation Mount the ODU, LPU and surge suppressor Protection requirements for a mast or tower installation If the ODU is to be mounted on a metal tower or mast, then in addition to the general protection requirements (above), the following requirements must be observed:

The equipment must be lower than the top of the tower or its lightning air terminal. The metal tower or mast must be correctly grounded. Schematic examples of mast or tower installations are shown in Figure 51. Figure 51 Grounding and lightning protection on mast or tower Protection requirements for a wall installation If the ODU is to be mounted on the wall of a building, then in addition to the general protection requirements (above), the following requirements must be observed:

The equipment must be lower than the top of the building or its lightning air terminal. The building must be correctly grounded. Page 6-14 External ground barGround ringOutdoor CAT5e cablePower supplyEquipment buildingNetwork switchAP/BHMGround CableTower/building ground systemCat5e cableGigabit surge suppressorGigabit surge suppressorGround to opposite side ODU grounding lug Chapter 6: Installation Mount the ODU, LPU and surge suppressor Schematic examples of wall installations are shown in Figure 52. Figure 52 Grounding and lightning protection on wall Page 6-15 External ground barGround cableGround ringOutdoor CAT5e cablePower SupplyEquipment buildingNetwork switchBuilding ground systemSM/BHSCat5e cableGigabit Surge SuppressorGigabit Surge SuppressorGround to opposite-side ODU grounding lug Chapter 6: Installation Mount the ODU, LPU and surge suppressor Protection requirements on a multifloor building If the ODU is to be mounted on a high rise building, it is likely that cable entry is at roof level

(Figure 32) and the equipment room is several floors below. The following additional requirements must be observed:

The ODU must be below the lightning terminals and finials. A grounding conductor must be installed around the roof perimeter to form the main roof perimeter lightning protection ring. Air terminals are typically installed along the length of the main roof perimeter lightning protection ring typically every 6.1m (20ft). The main roof perimeter lightning protection ring must contain at least two down conductors connected to the grounding electrode system. The down conductors should be physically separated from one another, as far as practical. Figure 53 Grounding and lightning protection on building Page 6-16 Chapter 6: Installation Installing the copper Cat5e Ethernet interface Installing the copper Cat5e Ethernet interface To install the copper Cat5e Ethernet interface, use the following procedures:

Install the main drop cable on page 6-17 Install the bottom LPU to PSU drop cable on page 6-19 Installing external antennas to a connectorized ODU on page 6-21 Caution To avoid damage to the installation, do not connect or disconnect the drop cable when power is applied to the PSU or network terminating equipment. Caution Always use Cat5e cable that is gel-filled and shielded with copper-plated steel. Alternative types of Cat5e cable are not supported by Cambium Networks. Cambium Networks supply this cable (Cambium part numbers WB3175 and WB3176), RJ45 connectors (Cambium part number WB3177) and a crimp tool (Cambium part number WB3211). The LPU and grounding kit contains a 600 mm length of this cable. Install the main drop cable Warning The metal screen of the drop cable is very sharp and may cause personal injury. ALWAYS wear cut-resistant gloves (check the label to ensure they are cut resistant). ALWAYS wear protective eyewear. ALWAYS use a rotary blade tool to strip the cable (DO NOT use a bladed knife). Warning Failure to obey the following precautions may result in injury or death:

Use the proper hoisting grip for the cable being installed. If the wrong hoisting grip is used, slippage or insufficient gripping strength will result. Do not reuse hoisting grips. Used grips may have lost elasticity, stretched, or become weakened. Reusing a grip can cause the cable to slip, break, or fall. The minimum requirement is one hoisting grip for each 60 m (200 ft) of cable. Page 6-17 Chapter 6: Installation Installing the copper Cat5e Ethernet interface Cut to length and fit hoisting grips 1 Cut the main drop cable to length from the top LPU to the bottom LPU. 2 Slide one or more hoisting grips onto the top end of the drop cable. 3 Secure the hoisting grip to the cable using a special tool, as recommended by the manufacturer. Terminate with RJ45 connectors Caution Check that the crimp tool matches the RJ45 connector, otherwise the cable or connector may be damaged. 1 Strip the cable outer sheath and fit the RJ45 connector load bar. 2 Fit the RJ45 connector housing as shown. To ensure there is effective strain relief, locate the cable inner sheath under the connector housing tang. Table 82 RJ45 connector and cable color code Pin Color (Supplied Color Pins on plug face cable)

(Conventional) Light Orange White/Orange Orange Orange Light Green White/Green Blue Blue Light Blue White/Blue Green Green Light Brown White/Brown Brown Brown 1 2 3 4 5 6 7 8 Figure 54 RJ45 cable RJ45 Connector (Bottom) Straight-Through Cable

``

8 7 6 5 4 3 2 1 Page 6-18 Chapter 6: Installation Installing the copper Cat5e Ethernet interface Install the bottom LPU to PSU drop cable Install the bottom LPU Install the bottom LPU, ground it, and connect it to the main drop cable. 1 Select a mounting point for the bottom LPU within 600 mm (24 in) of the building entry point. Mount the LPU vertically with cable glands facing downwards. 2 3 Connect the main drop cable to the bottom LPU. Fasten one ground cable to the bottom LPU using the M6 (small) lug. Tighten both nuts to a torque of 5 Nm (3.9 lb ft):

Locking nut Washer M6 lug Washer Nut Toothed washer M10 lug to ground 4 Select a building grounding point near the LPU bracket. Remove paint from the surface and apply anti-oxidant compound. Fasten the LPU ground cable using the M10 (large) lug. Page 6-19 Maximum 600 mm (24 inches)Bottom LPUGrounding systemBuilding entry pointLPU to grounding systemPSU drop cablePSUAC supplyNetwork terminatingequipmentGround cablesPower over Ethernet CAT5e cable (gel-filled, shielded with copper-plated steel)Network CAT5e cableSite grounding system Chapter 6: Installation Installing the copper Cat5e Ethernet interface Install the LPU to PSU drop cable Use this procedure to terminate the bottom LPU to PSU drop cable with RJ45 connectors at both ends, and with a cable gland at the LPU end. Warning The metal screen of the drop cable is very sharp and may cause personal injury. ALWAYS wear cut-resistant gloves (check the label to ensure they are cut resistant). ALWAYS wear protective eyewear. ALWAYS use a rotary blade tool to strip the cable, not a bladed knife. Caution Check that the crimp tool matches the RJ45 connector, otherwise the cable or connector may be damaged. 1 Cut the drop cable to the length required from bottom LPU to PSU. 2 At the LPU end only:

Fit one cable gland and one RJ45 connector by following the procedure Terminate with RJ45 connectors on page 6-18. Connect this cable and gland to the bottom LPU. 3 At the PSU end only: Do not fit a cable gland. Strip the cable outer sheath and fit the RJ45 connector load bar. Fit the RJ45 connector housing. To ensure there is effective strain relief, locate the cable inner sheath under the connector housing tang:

Page 6-20 Chapter 6: Installation Installing external antennas to a connectorized ODU Installing external antennas to a connectorized ODU PMP 450i Series To mount and connect an external antenna to the connectorized ODU, proceed as follows:

1 Mount the antenna(s) according to manufacturers instructions. 2 Connect the ODU A and B interfaces to the antenna(s) with RF cable of type LMR-400 (Cambium part numbers 30010194001 and 30010195001) and N type connectors (Cambium part number 09010091001). Tighten the N type connectors to a torque setting of 1.7 Nm (1.3 lb ft). 3 If the ODU is mounted indoors, install lightning arrestors at the building entry point:

4 Form drip loops near the lower ends of the antenna cables. These ensure that water is not channeled towards the connectors. 5 If the ODU is mounted outdoors, weatherproof the N type connectors (when antenna alignment is complete) using PVC tape and self-amalgamating rubber tape. 6 Weatherproof the antenna connectors in the same way (unless the antenna manufacturer specifies a different method). Page 6-21 PSUNetworkequipmentCAT5e cableGround ringRF cables to antennaAC supplyLightning arrestorsEquipment building or cabinetRF cableConnectorized ODUAB Chapter 6: Installation Installing external antennas to a connectorized ODU 7 Ground the antenna cables to the supporting structure within 0.3 meters (1 foot) of the ODU and antennas using the Cambium grounding kit (part number 01010419001):

8 Fix the antenna cables to the supporting structure using site approved methods. Ensure that no undue strain is placed on the ODU or antenna connectors. Ensure that the cables do not flap in the wind, as flapping cables are prone to damage and induce unwanted vibrations in the supporting structure. Note A video on weatherproofing procedure can be found at:

https://www.youtube.com/watch?v=a-twPfCVq4A Page 6-22 Connectorized ODUABPMP/PTP 450i ground cableRF cableAntenna Chapter 6: Installation Installing external antennas to a connectorized ODU Assembling the PMP 450i 5.x GHz AP sector antenna and attaching to the radio To assemble a PMP 450i Series AP antenna, perform the following steps. Note Cambium recommends to assemble the antenna, attach the AP and cabling, and to seal the RF connections before installing the unit at the deployment site. 1 Inventory the parts to ensure that you have them all before you begin. The full set of parts is shown below. Figure 55 AP antenna parts Page 6-23 Chapter 6: Installation Installing external antennas to a connectorized ODU 2 Remove top plate from the antenna as shown in Figure 56. Figure 56 Antenna top plate 3 Attach the antenna plate to the AP as shown in Figure 57. Note Please use the four thin neck M6 bolts and split washers provided with the connectorized units rather that the ones provided in the antenna kit. Figure 57 Attaching antenna plate to the AP Page 6-24 Chapter 6: Installation Installing external antennas to a connectorized ODU 4 Attach the plate mounted AP to the antenna and tighten the (4) serrated flange nuts using a spanner wrench Figure 58 Attaching the plate 5 Connect the port A of AP to vertical and port B of AP to horizontal polarization interfaces of the antenna with RF cable. Tighten the N type connectors to a torque setting of 1.7 Nm (1.3 lb ft). Figure 59 Connect the port A and B to the PMP 450i AP Page 6-25 Chapter 6: Installation Installing external antennas to a connectorized ODU 6 Assemble the upper bracket by attaching the (2) 7 hex bolts to the bracket using (2) serrated flange nuts Figure 60 AP antenna upper bracket assembly Figure 61 AP antenna upper bracket attached to upper adjustment arms 7 Attach the upper bracket to the adjustment arms using (2) hex bolts, (2) flat washers and

(2) lock washers. Feed the bolt through the lock washer then flat washer, then thread the bolt into the upper brackets threaded receptacle. Page 6-26 Chapter 6: Installation Installing external antennas to a connectorized ODU 8 Attach the rear strap to the upper bracket Figure 62 Rear strap connected to upper using (2) serrated flange nuts and (1) AP antenna bracket retaining bracket. Do not tighten the nuts now. 9 Attach the entire upper bracket to the Figure 63 Assembled upper bracket antenna using (2) hex bolts, (2) flat washers connected to AP antenna and (2) lock washers. Feed the bolt through the lock washer then flat washer, then thread the bolt into the upper brackets threaded receptacle. 10 Begin assembling the lower bracket by attaching the (2) 7 hex bolts to the bracket using (2) serrated flange nuts Figure 64 AP Antenna Lower Bracket Assembly 11 Attach the rear strap to the bracket using (2) serrated flange nuts and (1) retaining bracket. Do not tighten the nuts now. Attach the entire lower bracket to the antenna using (2) hex bolts, (2) flat washers and (2) lock washers. Page 6-27 Chapter 6: Installation Installing external antennas to a connectorized ODU Figure 65 Lower bracket attached to AP Figure 66 Completed AP and antenna antenna assembly Page 6-28 Chapter 6: Installation Installing external antennas to a connectorized ODU PMP 450 Series Assembling the PMP 450 AP antenna To assemble a PMP 450 Series AP antenna, perform the following steps. Note Cambium recommends to assemble the antenna, attach the AP and cabling, and to seal the RF connections before installing the unit at the deployment site. 1 Inventory the parts to ensure that you have them all before you begin. The full set of parts is shown below. Figure 67 PMP 450 AP antenna parts Page 6-29 Chapter 6: Installation Installing external antennas to a connectorized ODU 2 Begin assembling the upper bracket by attaching the (2) 7 hex bolts to the bracket using

(2) serrated flange nuts Figure 68 AP antenna upper bracket assembly 3 Attach the upper bracket to the adjustment Figure 69 AP antenna upper bracket arms using (2) hex bolts, (2) flat washers attached to upper adjustment arms and (2) lock washers. Feed the bolt through the lock washer then flat washer, then thread the bolt into the upper brackets threaded receptacle. Page 6-30 Chapter 6: Installation Installing external antennas to a connectorized ODU 4 Attach the rear strap to the upper bracket using (2) serrated flange nuts and (1) retaining bracket. Do not tighten the nuts now. Figure 70 Rear strap connected to upper AP antenna bracket 5 Attach the entire upper bracket to the Figure 71 Assembled upper bracket antenna using (2) hex bolts, (2) flat washers connected to AP antenna and (2) lock washers. Feed the bolt through the lock washer then flat washer, then thread the bolt into the upper brackets threaded receptacle. Page 6-31 Chapter 6: Installation Installing external antennas to a connectorized ODU 6 Begin assembling the lower bracket by Figure 72 AP Antenna Lower Bracket attaching the (2) 7 hex bolts to the bracket Assembly using (2) serrated flange nuts 7 Attach the rear strap to the bracket using (2) serrated flange nuts and (1) retaining bracket. Do not tighten the nuts now. Figure 73 Lower bracket attached to AP antenna Attach the entire lower bracket to the antenna using (2) hex bolts, (2) flat washers and (2) lock washers. Attaching the PMP 450 AP to the antenna To attach a PMP 450 Series AP to the antenna, perform the following steps. Page 6-32 Chapter 6: Installation Installing external antennas to a connectorized ODU Note Use shielded cable for all infrastructure connections associated with APs, SMs, and CMMs. The environment that these modules operate in often has significant unknown or varying RF energy. Operator experience consistently indicates that the additional cost of shielded cables is more than compensated by predictable operation and reduced costs for troubleshooting and support. 1 Attach the included bracket to the rear of the AP using the (4) M5 x 7mm bolts Figure 74 Attaching bracket to the rear of the AP 2 Attach the AP to the antenna by sliding the bracket onto the bolts and tighten the (4) serrated flange nuts using a 13 mm spanner wrench. Figure 75 Lower bracket attached to AP antenna Page 6-33 Chapter 6: Installation Installing external antennas to a connectorized ODU Note If using a non-standard antenna, do not cover the equilibrium membrane vent located on the back of the unit. Equilibrium Membrane Vent Figure 76 Mounted PMP 450 AP and antenna assembly, viewed from back and back Page 6-34 Chapter 6: Installation Installing external antennas to a connectorized ODU Attaching the PMP 450 platform AP and antenna to the mount point 1 Attach the upper bracket of the antenna to the mount point by closing the rear strap around the pole and tightening the (2) serrated flange nuts using a 13mm spanner wrench. These must be tightened evenly on the pol to avoid jumping/stripping threads. Figure 77 Attaching the AP antenna upper bracket to the pole 2 Attach the lower bracket of the antenna to the mount point by closing the rear strap around the pole and tightening the (2) serrated flange nuts using a 13mm spanner wrench. These must be tightened evenly on the pole to avoid jumping/stripping threads. Figure 78 Attaching the AP antenna lower bracket to the pole 3 Use a local map, compass, and/or GPS device as needed to determine the direction that one or more APs require to each cover the 90 sector. Page 6-35 Chapter 6: Installation Installing external antennas to a connectorized ODU 4 Choose the best mounting location for your particular application. 5 6 7 Note Use the embedded spectrum analyzer or a commercial analyzer to evaluate the frequencies present in various locations. OFDM APs need not be mounted next to each other. They can be distributed throughout a given site. However, the 90 offset must be maintained. If you want to collocate these APs with PMP 100 Series APs of the 5.4-GHz frequency band range, plan to allow at least 25 MHz of separation between their center channels. Secure a ground strap to the ground lug on the back of the AP. Secure the ground strap to the pole, tower, or other trusted ground. The bracket of the standard antenna has provision for measured down tilt. The recommended practice is to use one of the many radio analysis and mapping tools or on-

line tools to calculate down tilt based on antenna height above the service area. The proper angle of tilt can be calculated as a factor of both the difference in elevation and the distance that the link spans. Even in this case, a plumb line and a protractor can be helpful to ensure the proper tilt. This tilt is typically minimal. The number of degrees to offset (from vertical) the mounting hardware leg of the support tube is equal to the angle of elevation from the lower module to the higher module (<B in the example provided in Figure 43). Page 6-36 Chapter 6: Installation Installing external antennas to a connectorized ODU Figure 79 Variables for calculating angle of elevation (and depression) Where:

b B A Is:

angle of elevation vertical difference in elevation horizontal distance between modules To use metric units to find the angle of elevation, use the following formula:

Where:

B A Is:

expressed in meters expressed in kilometers To use English standard units to find the angle of elevation, use the following formula:

Where:

B A Is:

expressed in feet expressed in miles The angle of depression from the higher module is identical to the angle of elevation from the lower module. Connect the coax cables to the antenna and to the AP Weatherproof the connector on the coax cables (see section Attaching and weatherproofing an N type connector on page 6-68). Page 6-37 8 9 tan b = B1000Atan b = B5280A Chapter 6: Installation Installing external antennas to a connectorized ODU PMP 450i Series 900 MHz AP Mounting of PMP 450i 900 MHz AP 1 Inventory the parts to ensure that you have them all before you begin. The full set of parts is shown in Figure 81. Figure 80 PMP 450i 900 MHz AP antenna unbox view Figure 81 PMP 450i 900 MHz AP antenna inventory Upper bracket Adjustable arm Lower bracket Nuts and bolts Radio assembly plate Page 6-38 Chapter 6: Installation Installing external antennas to a connectorized ODU 2

(1) Unfold the upper bracket assembly of the antenna.

(2) Unfold the lower bracket assembly.

(3) Loose the radio assembly plate by untightening M8 four bolds.

(4) Remove the radio assembly top plate by sliding towards upper bracket assembly. Page 6-39 1 2 3 4 Chapter 6: Installation Installing external antennas to a connectorized ODU 3

(1) Place the radio assembly plate on the radio and align holes with radio enclosure. Note Ensure that the radio plate notch opening and RF port of radio in same direction. It is also important to make sure you attach the radio assembly plate in the proper orientation as shown in figure.

(2) Insert M8 bolts through plate into radio enclosure

(3) Fix the plate by tightening four bolts with a toreque setting on 2 0.5 Nm Page 6-40 1 2 3 Chapter 6: Installation Installing external antennas to a connectorized ODU 4

(1) Place the radio mounted plate on sector antenna as show figure. Ensure that the orinentation of RF port of antenna and radio are in same direction

(2) Line up the radio assembly to four bolts and slide towards lower bracket assembly to lock.

(3) Tighten the radio assembly plate using four M8 bolts to a toreque setting on 2 0.5 Nm Page 6-41 1 2 3 Chapter 6: Installation Installing external antennas to a connectorized ODU 5

(1) Connect the port A of AP to vertical and Port A Port B port B of AP to horizontal polarization interfaces of the antenna with RF cable. Ensure that the RF cables are passthrough inside the lower bracket assembly

(2) Hand tighten the N type connectors and the torque should not exceed more than 1 Nm Mounting of PMP 450i 900 MHz AP antenna to the pole The mounting procedure of PMP 450i 900 MHz AP and antenna to the pole is given below:

1 Remove the upper and lower rear bracket strap from the sector antenna. 1 2 Page 6-42 Chapter 6: Installation Installing external antennas to a connectorized ODU 2 Attach the upper and lower bracket of the antenna to the mount point by closing the rear strap around the pole. Note Before mounting the radio on pole, secure upper and lower bracket assembly with a torque setting of 3 to 4 Nm as shown in Figure 1 . Also, ensure that inner strap of upper bracket is set to zero degree marking. Figure 82 Attaching radio mounting PMP 450i 900 MHz AP antenna to the pole Inner strap 1 2 Rear strap Rear strap 3 Page 6-43 Chapter 6: Installation Installing external antennas to a connectorized ODU 3 Tightening the four serrated flange M10 nuts on upper and lower rear strap using a 17 mm spanner wrench. These must be tightened evenly on the pol to avoid jumping/stripping threads ODU ground cable Building ground system Sector antenna alignment The 900 MHz sector antenna horizontal and vertical alignment procedure is shown in Figure 83. The antenna can be aligned from +5 to -10 degree by adjusting inner strap of upper bracket assembly. Figure 83 900 MHz sector antenna alignment Horizontal alignemtn Vertical alignment Vertical alignment upward Inner strap downlward tilt tilt Upper bracket assembly ODU ground cable Building ground system Page 6-44 Chapter 6: Installation Installing external antennas to a connectorized ODU PMP 450 Series 900 MHz SM Attaching the SM 900 MHz directional antenna to the pole 1 Unbox the directional yagi antenna. Figure 84 PMP 450i 900 MHz SM external directional antenna 2 Attach the directional atenna to the pole and insert the two U clamps into the mounting bracket of the antenna Figure 85 Attach the antenna to the pole Page 6-45 Chapter 6: Installation Installing external antennas to a connectorized ODU 3 Tighten all nuts to approximately 6 to 7 Nm or less to avoid deforming the pole. Figure 86 Fixing the nuts Page 6-46 Chapter 6: Installation Installing external antennas to a connectorized ODU Radio mounting to the antenna 1 Align the radio to E bracket and slide towards right to lock on the antenna as shown in figure. Figure 87 Fixing the radio to the antenna Slide towards right to lock 2 Connect the port A of SM to vertical and port B of SM to horizontal polarization interfaces of the antenna with RF cable. Figure 88 Connecting RF cable to the radio ODU ground cable Building ground system Page 6-47 Chapter 6: Installation Installing external antennas to a connectorized ODU Directional Yagi antenna alignment The directional Yagi antenna horizontal and vertical alignment procedure is shown below. The Yagi antenna can be aligned for +15 to -15 degree. Figure 89 Yagi antenn alignment - horizentaly Figure 90 Yagi antenna alignment - upward tilt Figure 91 Yagi antenna alignment - downward tilt Page 6-48 Chapter 6: Installation Installing an integrated ODU Installing an integrated ODU Caution Do not reverse the bracket clamp, as this arrangement may lead to failure of the assembly. Do not over-tighten the bolts as this may lead to failure of the assembly. PMP 450m Series AP To mount and connect an integrated ODU, proceed as follows:

1 Inventory the parts to ensure that you have them all before you begin. The full set of parts is shown in Figure 92. Figure 92 PMP 450m Series - AP unbox view Top bracket PMP 450m AP Bottom bracket Page 6-49 Chapter 6: Installation Installing an integrated ODU 2 Attach the bottom bracket to ODU using (2) hex bolts and tighten the bolts. 3 Insert the top bracket to projected two bolts of ODU and and tighten the top bracket using two nuts. 4 Fix the front and rear strap assembly to the upper bracket using two bolts. Do not tighten the nuts now. 5 Fix the front and rear strap assembly to the bottom bracket using two bolts. Do not tighten the nuts now. Page 6-50 Chapter 6: Installation Installing an integrated ODU 6 See PMP 450m Series AP on page 6-3 for grounding procedure See PMP 450m Series AP on page 6-6 for mounting procedure Page 6-51 Chapter 6: Installation Installing an integrated ODU PMP/PTP 450i Series AP/SM/BH To mount and connect an integrated ODU, proceed as follows:

1 Fix the mounting plate to the back of the ODU using the four M6 bolts, and spring and plain washers provided. Tighten the bolts to a torque setting of 5.0 Nm (3.7 lb ft). Figure 93 Fixing the mounting plate to the back of the ODU 2 Attach the bracket body to the mounting plate using the M8 bolt, spring and plain washers. 3 Hoist the ODU to the mounting position. 4 Attach the bracket body to the pole using the bracket clamp, M8 bolts, and spring and plain washers. 5 If the ODU is mounted outdoors, weatherproof the N type connectors (when antenna alignment is complete) using PVC tape and self-amalgamating rubber tape. Figure 94 Attaching the bracket body Page 6-52 Chapter 6: Installation Connecting Cat5e Ethernet cable Connecting Cat5e Ethernet cable Connecting an RJ45 and gland to a unit Perform this task to connect the Ethernet cable to an AP. To connect the Ethernet cable with a gland to an AP unit, proceed as follows:

1 2 Insert the RJ45 cable through the gland components Insert the RJ45 plug into the socket in the unit, making sure that the locking tab snaps home. 3 Support the drop cable and gently hand screw the gland body into the unit until the bushing seal is flush to the unit body. Note Do not fit the back shell prior to securing the gland body. 4 Once the gland is fully hand screwed into the unit, tighten it one full rotation only with a 1 1/8 inch spanner wrench. 5 When the gland body has been fitted, tighten the gland back shell. Caution Do not over-tighten the gland back shell, as the internal seal and structure or RJ45 port may be damaged. Page 6-53 Chapter 6: Installation Connecting Cat5e Ethernet cable Figure 95 Ethernet cable gland for PMP/PTP 450 Series Figure 96 Ethernet cable gland for PMP/PTP 450i Series Page 6-54 Chapter 6: Installation Connecting Cat5e Ethernet cable Figure 97 Ethernet cable gland for PMP 450m Series Disconnecting an RJ45 and gland from a unit Perform this task to disconnect the Ethernet cable and watertight gland from ODU. To disconnect the Ethernet cable and gland from a unit, proceed as follows:

1 2 Hold Ethernet cable and remove the gland back shell Use a small flathead screwdriver (0.2/5mm wide or greater) to gently release the black plastic watertight bushing from the compression fins, being careful not to damage the bushing. 3 Unscrew the gland body from the AP, making sure that the Ethernet cable is not rotating while disengaging the gland body from the AP housing Use a small screwdriver to depress the RJ45 locking clip Unplug the RJ45 cable Remove the gland from the cable, if necessary 4 5 6 Page 6-55 Chapter 6: Installation Installing ODU Installing ODU Installing an PMP 450 platform AP To install a PMP 450 platform Series AP, perform the following steps. Procedure 5 Installing an AP 1 2 Begin with the AP in the powered-down state. Choose the best mounting location for your particular application. Modules need not be mounted next to each other. They can be distributed throughout a given site. However, the 60 offset must be maintained. Mounting can be done with supplied clamps. See Installing external antennas to a connectorized ODU on page 6-21 for connecting external antenna to PMP 450i Series, PMP 450 Series, PMP 450i Series 900 MHz AP and PMP 450 Series 900 MHz SM See Installing an integrated ODU on page 6-49 3 Align the AP as follows:

a. Move the module to where the link will be unobstructed by the radio horizon and no objects penetrate the Fresnel zone. b. Use a local map, compass, and/or GPS device as needed to determine the direction that one or more APs require to each cover the intended 60 sector. c. Apply the appropriate degree of downward tilt. d. Ensure that the nearest and furthest SMs that must register to this AP are within the beam coverage area. 4 Adjust the azimuth to achieve visual alignment, lock the AP in the proper direction and downward tilt. 5 Attach the cables to the AP (See Powering the AP/SM/BH for test configuration on Page 5-15) 6 W aterproof the cables (See section Attaching and weatherproofing an N type connector on page 6-68). Page 6-56 Chapter 6: Installation Installing a PMP 450 platform SM Installing ODU Installing a PMP 450 platform Series SM consists of two procedures:

Physically installing the SM on a residence or other location and performing a coarse alignment using the alignment tool or alignment tone. Verifying the AP to SM link and finalizing alignment using review of power level, link tests, and review of registration and session counts. Procedure 6 Installing an SM 1 Choose the best mounting location for the SM based on section ODU and external antenna location on page 3-10. 2 Use stainless steel hose clamps or equivalent fasteners to lock the SM into position. See Installing external antennas to a connectorized ODU on page 6-21 for connecting external antenna See Installing an integrated ODU on page 6-49 Remove the base cover of the SM. Terminate the UV outside grade Category 5 Ethernet cable with an RJ-45 connector, and connect the cable to the SM. Wrap a drip loop in the cable. For Connectorized Models, Install the external antenna according to the manufacturers instructions. 3 4 5 6 7 For Connectorized Models, connect the SMs N-type antenna connectors to the external antenna, ensuring that the polarity matches between the SM cable labeling and the antenna port labels. Connectorized SM Antenna Cable Label Antenna Connection A B Vertical Horizontal 8 For Connectorized Models, weatherproof the N-type antenna connectors following section Attaching and weatherproofing an N type connector on page 6-68. 9 Wrap an AWG 10 (or 6mm2) copper wire around the Ground post of the SM 10 Securely connect the copper wire to the grounding system (Protective Earth) according to applicable regulations. 11 Install an surge suppressor as describe in section Mount the Surge Suppressor on page 6-9 12 Connect the power supply to a power source. 13 Connect the Ethernet output from the power supply to the Ethernet port of your laptop. Page 6-57 Chapter 6: Installation Installing ODU 14 Launch your web browser. In the URL address bar, enter 169.254.1.1. then press Enter. 15 If the browser in laptop fails to access the interface of the SM, follow the procedure Radio recovery mode on page 1-22 16 Log in as admin on the ODU. Configure a password for the admin account and log off. 17 Log back into the SM as admin or root, using the password that you configured. 18 For coarse alignment of the SM, use the Alignment Tool located at Tools, Alignment Tool. Optionally, connect a headset to the AUX/SYNC port the SM and listen to the alignment tone, which indicates greater SM receive signal power by pitch. By adjusting the SMs position until the highest frequency pitch is obtained operators and installers can be confident that the SM is properly positioned. For information on device GUI tools available for alignment, see sections Using the Alignment Tool, Using the Link Capacity Test tool, and Using AP Evaluation tool below. 19 When the highest power achieved, lock the SM mounting bracket in place. 20 Log off of the SM web interface. 21 Disconnect the Ethernet cable from your laptop. 22 Replace the base cover of the SM. 23 Connect the Ethernet cable to the computer that the subscriber will be using. Installing a PTP 450 platform BHM To install a PTP 450 platform Series BHM, perform the following steps. Procedure 7 Installing a BHM 1 2 3 Access the General tab of the Configuration page in the BHM Choose the best mounting location for your particular application. Align the BHM as follows:

a. Move the module to where the link will be unobstructed by the radio horizon and no objects penetrate the Fresnel zone. b. Use a local map, compass, and/or GPS device as needed to determine the direction to the BHS. c. Apply the appropriate degree of downward or upward tilt. d. Ensure that the BHS is within the beam coverage area. Page 6-58 Chapter 6: Installation Installing ODU 4 Using stainless steel hose clamps or equivalent fasteners, lock the BHM into position. See Installing external antennas to a connectorized ODU on page 6-21 for connecting external antenna 5 If this BHM will not be connected to a CMM, optionally connect a utility cable to a GPS timing source and then to the SYNC port of the BHM. 6 Either connect the BHMs Aux to the CMM or connect the DC power converter to the BHM and then to an AC power source. RESULT: When power is applied to a module or the unit is reset on the web-based interface, the module requires approximately 25 seconds to boot. During this interval, self-tests and other diagnostics are being performed. 7 8 Access Configuration > General page of the BHM for Synchronization configuration. If a CMM4 is connected, set the Sync Input parameter to the AutoSync or Autosync

+ Free Run selection. Installing a PTP 450 platform BHS To install a PTP 450 platform Series BHS, perform the following steps. Procedure 8 Installing a BHS 1 2 Choose the best mounting location for the BHS. Terminate the UV outside grade Category 5 Ethernet cable with an RJ-45 connector, and connect the cable to the BHS. (See Powering the AP/SM/BH for test configuration on Page 5-15) 3 Use stainless steel hose clamps or equivalent fasteners to lock the BHS into position. 4 Install an surge suppressor as describe in section Mount the Surge Suppressor on page 6-9 5 For coarse alignment of the BHS, use the Audible Alignment Tone feature as follows:

a. At the BHS, connect the RJ-45 connector of the Alignment Tool Headset to the Aux port via alignment tone adapter as shown in Figure 158 on page 8-20. b. Listen to the alignment tone for pitch, which indicates greater signal power

(RSSI/dBm) by higher pitch. Adjust the module slightly until you hear the highest pitch and highest volume 6 When you have achieved the best signal (highest pitch, loudest volume), lock the BHS in place with the mounting hardware Page 6-59 Installing ODU Chapter 6: Installation Configuring the Link See Configuring remote access on page 7-255. Monitoring the Link See Monitoring the Link on page 7-256. Page 6-60 Chapter 6: Installation Installing the AC Power Injector Installing the AC Power Injector Caution As the PSU is not waterproof, locate it away from sources of moisture, either in the equipment building or in a ventilated moisture-proof enclosure. Do not locate the PSU in a position where it may exceed its temperature rating. Caution Do not plug any device other than a PMP/PTP 450i ODU into the ODU port of the PSU. Other devices may be damaged due to the non-standard techniques employed to inject DC power into the Ethernet connection between the PSU and the ODU. Do not plug any device other than a Cambium PMP/PTP 450 platform PSU into the PSU port of the ODU. Plugging any other device into the PSU port of the ODU may damage the ODU and device. Installing the AC Power Injector Follow this procedure to install the AC Power Injector:

1 Form a drip loop on the PSU end of the LPU to PSU drop cable. The drip loop ensures that any moisture that runs down the cable cannot enter the PSU. 2

(a) Place the AC Power Injector on a horizontal surface. Plug the LPU to PSU drop cable into the PSU port labeled ODU. (b) When the system is ready for network connection, connect the network Cat5e cable to the LAN port of the PSU:

(a)

(b) Page 6-61 Chapter 6: Installation Installing CMM4 Installing CMM4 Note For instructions on CMM3 (CMMmicro) or CMM4 installation, including the outdoor temperature range in which it is acceptable to install the unit, tools required, mounting and cabling instructions, and connectivity verification, please see the PMP Synchronization Solutions User Guide located on the Cambium website. The Cluster Management Module 4 (CMM4) provides power, sync, and network connectivity for up to eight APs, backhauls, and Ethernet terrestrial feeds in a variety of configurations. The CMM4 provides Sync over Power over Ethernet and integrated surge suppression on the controller board for up to 8 APs or BHs. Both a custom 30 VDC power scheme and a custom 56 VDC power scheme are available. Neither is the same as the later IEEE Standard 802.3af, and neither is compatible with it. Managed switching using a hardened EtherWAN switch (1090CKHH models). The CMM4 ships with a 14-port EtherWAN switch and is also available without a switch. The CMM4 originally shipped with a 9-port EtherWAN switch. Surge suppression on the controller board for the incoming 30V DC and 56V DC power lines and GPS coax cable. Auto-negotiation on the Ethernet ports. Ports will auto-negotiate to match inputs that are either 100Base-T or 10Base-T, and either full duplex or half duplex, when the connected device is set to auto-negotiate. Alternatively, these parameters are settable. An always-on NTP (Network Time Protocol) server that can provide date and time to any radio that can reach the CMMs management IP address. CNUT can be used to upgrade the CMM-4 software. PMP/PTP 450 platform can use the CMM4s EtherWan switch for their network connectivity. Note The 56V of a CMM4 needs to go through the adapter cable (part number N000045L001A) as shown in Figure 24 on page 2-36. The CMM4 56V power adapter cable can be prepared by swapping pins 5 and 7. See CMM4 56V power adapter cable pinout on page 2-36 for power adapter cable pinout. Page 6-62 Chapter 6: Installation Figure 98 CMM4 cabled to support PMP/PTP 450 platform Installing CMM4 To PMP/PTP 450 platform Radio Page 6-63 Chapter 6: Installation Supplemental installation information Supplemental installation information This section contains detailed installation procedures that are not included in the above topics, such as how to strip cables, create grounding points and weatherproof connectors. Stripping drop cable When preparing drop cable for connection to the PMP/PTP 450 platform ODU or LPU, use the following measurements:

When preparing drop cable for connection to the PMP/PTP 450 platform PSU (without a cable gland), use the following measurements:

Page 6-64 Chapter 6: Installation Supplemental installation information Creating a drop cable grounding point Use this procedure to connect the screen of the main drop cable to the metal of the supporting structure using the cable grounding kit (Cambium part number 01010419001). To identify suitable grounding points, refer to Drop cable grounding points on page 3-14. 1 Remove 60 mm (2.5 inches) of the drop cable outer sheath. 2 Cut 38mm (1.5 inches) of rubber tape (self-amalgamating) and fit to the ground cable lug. Wrap the tape completely around the lug and cable. 3 Fold the ground wire strap around the drop cable screen and fit cable ties. Page 6-65 Chapter 6: Installation Supplemental installation information 4 Tighten the cable ties with pliers. Cut the surplus from the cable ties. 5 Cut a 38mm (1.5 inches) section of self-amalgamating tape and wrap it completely around the joint between the drop and ground cables. 6 Use the remainder of the self-amalgamating tape to wrap the complete assembly. Press the tape edges together so that there are no gaps. Page 6-66 Chapter 6: Installation Supplemental installation information 7 Wrap a layer of PVC tape from bottom to top, starting from 25 mm (1 inch) below and finishing 25 mm (1 inch) above the edge of the self-amalgamating tape, overlapping at half width. 8 Repeat with a further four layers of PVC tape, always overlapping at half width. Wrap the layers in alternate directions (top to bottom, then bottom to top). The edges of each layer should be 25mm (1 inch) above (A) and 25 mm (1 inch) below (B) the previous layer. 9 Prepare the metal grounding point of the supporting structure to provide a good electrical contact with the grounding cable clamp. Remove paint, grease or dirt, if present. Apply anti-

oxidant compound liberally between the two metals. 10 Clamp the bottom lug of the grounding cable to the supporting structure using site approved methods. Use a two-hole lug secured with fasteners in both holes. This provides better protection than a single-hole lug. Page 6-67 Chapter 6: Installation Supplemental installation information Attaching and weatherproofing an N type connector The following procedure should be used to weatherproof the N type connectors fitted to the connectorized ODU (AP/SM/BH) and antenna. This procedure must be followed to ensure that there is no moisture ingress at the radio ports. Failure to properly seal N-type antenna connectors can result in poor link performance or complete loss of radio communication. Note Cambium recommends to assemble the antenna, attach the ODU and cabling, and to seal the RF connections before installing the unit at the deployment site. Note N type connectors should be tightened using a torque wrench, set to 15 lb in or 1.7 Nm. If a torque wrench is not available, N type connectors may be finger tightened. Use this procedure to weatherproof the N type connectors fitted to the connectorized ODU and external antenna (if recommended by the antenna manufacturer). 1 Ensure the connection is tight. A torque wrench should be used if available:

2 Wrap the connection with a layer of 19 mm (0.75 inch) PVC tape, starting 25 mm (1 inch) below the connector body. Overlap the tape to half-width and extend the wrapping to the body of the LPU. Avoid making creases or wrinkles:

Page 6-68 Chapter 6: Installation Supplemental installation information 3 Smooth the tape edges:

4 Cut a 125mm (5 inches) length of rubber tape (self-amalgamating):

5 Expand the width of the tape by stretching it so that it will wrap completely around the connector and cable:

6 Press the tape edges together so that there are no gaps. The tape should extend 25 mm

(1 inch) beyond the PVC tape:

Page 6-69 Chapter 6: Installation Supplemental installation information 7 Wrap a layer of 50 mm (2 inch) PVC tape from bottom to top, starting from 25 mm (1 inch) below the edge of the self-amalgamating tape, overlapping at half width. 8 Repeat with a further four layers of 19 mm (0.75 inch) PVC tape, always overlapping at half width. Wrap the layers in alternate directions:

Second layer: top to bottom. Third layer: bottom to top. Fourth layer: top to bottom. Fifth layer: bottom to top. The bottom edge of each layer should be 25 mm (1 inch) below the previous layer. 9 Check the completed weatherproof connection:

Note A video of this procedure can be found at:

https://www.youtube.com/watch?v=a-twPfCVq4A Page 6-70

 

 

Chapter 7: Configuration This chapter describes how to use the web interface to configure the PMP/PTP 450 platform link. This chapter contains the following topics:

Preparing for configuration on page 7-72 Connecting to the unit on page 7-73 Using the web interface on page 7-75 Quick link setup on page 7-81 Configuring IP and Ethernet interfaces on page 7-92 Upgrading the software version and using CNUT on page 7-135 General configuration on page 7-139 Configuring Unit Settings page on page 7-157 Setting up time and date on page 7-161 Configuring synchronization on page 7-163 Configuring security on page 7-165 Configuring radio parameters on page 7-192 Setting up SNMP agent on page 7-242 Configuring syslog on page 7-249 Configuring remote access on page 7-255 Monitoring the Link on page 7-256 Configuring quality of service on page 7-259 Installation Color Code on page 7-272 Zero Touch Configuration Using DHCP Option 66 on page 7-273 Configuring Radio via config file on page 7-279 Configuring a RADIUS server on page 7-281 Page 7-71 Chapter 7: Configuration Preparing for configuration Preparing for configuration This section describes the checks to be performed before proceeding with unit configuration and antenna alignment. Safety precautions All national and local safety standards must be followed while configuring the units and aligning the antennas. Warning Ensure that personnel are not exposed to unsafe levels of RF energy. The units start to radiate RF energy as soon as they are powered up. Respect the safety standards defined in Compliance with safety standards on page 4-22, in particular the minimum separation distances. Observe the following guidelines:

Never work in front of the antenna when the ODU is powered. Always power down the PSU before connecting or disconnecting the drop cable from the PSU, ODU or LPU. Regulatory compliance All applicable radio regulations must be followed while configuring the units and aligning the antennas. For more information, refer to Compliance with radio regulations on page 4-31. Caution If the system designer has provided a list of channels to be barred for TDWR radar avoidance, the affected channels must be barred before the units are allowed to radiate on site, otherwise the regulations will be infringed. Attention Si le concepteur du systme a fourni une liste de canaux interdire pour viter les radars TDWR, les cannaux concernes doivent tre interdits avant que les units sont autorises mettre sur le site, sinon la rglementation peut tre enfreinte. Page 7-72 Chapter 7: Configuration Connecting to the unit Connecting to the unit This section describes how to connect the unit to a management PC and power it up. Configuring the management PC Use this procedure to configure the local management PC to communicate with the PMP/PTP 450 platform. Procedure 9 Configuring the management PC 1 Select Properties for the Ethernet port. In Windows 7 this is found in Control Panel

> Network and Internet > Network Connections > Local Area Connection. 2 Select Internet Protocol (TCP/IP):

3 Click Properties. Page 7-73 Chapter 7: Configuration Connecting to the unit 4 Enter an IP address that is valid for the 169.254.X.X network, avoiding 169.254.0.0 and 169.254.1.1. A good example is 169.254.1.3:

5 Enter a subnet mask of 255.255.0.0. Leave the default gateway blank. Connecting to the PC and powering up Use this procedure to connect a management PC and power up the PMP/PTP 450 platform. Procedure 10 Connecting to the PC and powering up 1 2 Check that the ODU and PSU are correctly connected. Connect the PC Ethernet port to the LAN port of the PSU using a standard (not crossed) Ethernet cable. 3 Apply mains or battery power to the PSU. The green Power LED should illuminate continuously. 4 After about several seconds, check that the orange Ethernet LED starts with 10 slow flashes. 5 Check that the Ethernet LED then illuminates continuously. Page 7-74 Chapter 7: Configuration Using the web interface Using the web interface This section describes how to log into the PMP/PTP 450 platform web interface and use its menus. Logging into the web interface Use this procedure to log into the web interface as a system administrator. Procedure 11 Logging into the web interface 1 Start the web browser from the management PC. 2 Type the IP address of the unit into the address bar. The factory default IP address is 169.254.1.1. Press ENTER. The web interface menu and System Summary page are displayed:

Page 7-75 Chapter 7: Configuration Using the web interface 3 On left hand side of home page, the login information is displayed:

4 Enter Username (factory default username is admin) and Password (factory default password is admin) and click Login. Web GUI 1 1 2 3 Field Name Main Manu Menu Option Description Click an option in side navigation bar (area marked as 1). Multiple options in sub-navigation bars appear Click top sub-navigation bar to choose one configuration page (area marked as 2) Parameter To configure the parameters (e.g. area marked as 3) Press "Save Changes" to confirm and save the changes To reboot the ODU Page 7-76 Chapter 7: Configuration Using the web interface Using the menu options Use the menu navigation bar in the left panel to navigate to each web page. Some of the menu options are only displayed for specific system configurations. Use Table 83 to locate information about using each web page. Table 83 Menu options and web pages Main Menu options Applicable Description menu General Status Session Status Event Log Network Interface Layer 2 Neighbors General IP Radio SNMP Qaulity of Service (QoS) Security Time VLAN module All Viewing General Status on page 9-2 AP, BHM Viewing Session Status on page 9-16 All Interpreting messages in the Event Log on page 9-23 AP, BHM Viewing the Network Interface on page 9-25 All All All All All All All Viewing the Layer 2 Neighbors on page 9-26 General configuration on page 7-139 Configuring IP and Ethernet interfaces on page 7-92 Configuring radio parameters on page 7-193 Setting up SNMP agent on page 7-242 Configuring quality of service on page 7-259 Configuring security on page 7-165 AP, BHM Setting up time and date Time page of PMP/PTP 450 platform AP/BHM on page 7-161 All VLAN configuration for PMP on page 7-114 VLAN configuration for PTP on page 7-124 Page 7-77 Chapter 7: Configuration Using the web interface Main Menu options Applicable Description menu module DiffServ Protocol Filtering Syslog Unit Setting Scheduler All All All All All IPv4 and IPv6 Prioritization on page 7-

131 Filtering protocols and ports on page 7-132 Configuring syslog on page 7-249 Configuring Unit Settings page on page 7-157 Viewing the Scheduler statistics on page 9-27 Registration Failures AP, BHM Viewing list of Registration Failures Bridge Control Block Bridging Table Ethernet Radio VLAN Data VC All All All All All All statistics on page 9-29 Interpreting Bridge Control Block statistics on page 9-52 Interpreting Bridging Table statistics on page 9-30 Interpreting Ethernet statistics on page 9-32 Interpreting RF Control Block statistics on page 9-35 Interpreting VLAN statistics on page 9-36 Interpreting Data VC statistics on page 9-38 Throughput AP, BHM Interpreting Throughput statistics on page 9-40 Filter ARP Overload SM Interpreting Filter statistics on page 9-

46 SM All Viewing ARP statistics on page 9-47 Interpreting Overload statistics on page 9-43 Syslog Statistics All Interpreting syslog statistics on page 9-57 Translation Table SM Interpreting Translation Table statistics on page 9-31 Page 7-78 Chapter 7: Configuration Using the web interface Main Menu options Applicable Description menu module DHCP Relay NAT Stats NAT DHCP Pass Through Statistics Sync Status PPPoE SM Interpreting DHCP Relay statistics on page 9-44 SM SM AP AP Viewing NAT statistics on page 9-47 Viewing NAT DHCP Statistics on page 9-49 Interpreting Pass Through Statistics on page 9-54 Interpreting Sync Status statistics on page 9-50 SM Interpreting PPPoE Statistics for Customer Activities on page 9-51 SNMPv3 Statistics All Interpreting SNMPv3 Statistics on Frame Utilization Link Capacity Test Spectrum Analyzer Remote Spectrum Analyzer All All All page 9-55 Interpreting SNMPv3 Statistics on page 9-55 Using the Link Capacity Test tool on page 8-21 Spectrum Analyzer tool on page 8-3 Remote Spectrum Analyzer tool on page 8-12 AP/BHM Evaluation SM, BHS Using AP Evaluation tool on page 8-27 Using BHM Evaluation tool on page 8-

31 Subscriber Configuration AP Using the Subscriber Configuration tool on page 8-39 OFDM Frame Calculator AP, BHM Using the OFDM Frame Calculator tool on page 8-35 BER results Alignment Tool Link Status Sessions SM Using BER Results tool on page 8-45 SM, BHS Using the Alignment Tool on page 8-

15 AP AP Using the Link Status tool on page 8-

40 Using the Sessions tool on page 8-46 Page 7-79 Chapter 7: Configuration Using the web interface Main Menu options Applicable Description menu module Change User Setting Add user Delete User User Quick Start Region Settings Changing a User Setting on page 7-

167 Adding a User for Access to a module on page 7-166 Deleting a User from Access to a module on page 7-167 Users account on page 7-168 AP, BHM Quick link setup on page 7-81 AP, BHM Quick link setup on page 7-81 Radio Carrier Frequency AP, BHM Quick link setup on page 7-81 Synchronization LAN IP Address AP, BHM Quick link setup on page 7-81 AP, BHM Quick link setup on page 7-81 Review and Save Configuration AP, BHM Quick link setup on page 7-81 Quick Status Spectrum Results (PDA) Information BHM Evaluation AIM Copyright Notices SM SM SM SM SM All The PDA web-page includes 320 x 240 pixel formatted displays of information important to installation and alignment for installers using legacy PDA devices. All device web pages are compatible with touch devices such as smart phones and tablets. The Copyright web-page displays pertinent device copyright information. All Page 7-80 Chapter 7: Configuration Quick link setup Quick link setup This section describes how to use the Quick Start Wizard to complete the essential system configuration tasks that must be performed on a PMP/PTP configuration. Note If the IP address of the AP or BHM is not known, See Radio recovery mode on page 1-

22. Initiating Quick Start Wizard Applicable products PMP : AP PTP: BHM To start with Quick Start Wizard: after logging into the web management interface click the Quick Start button on the left side of main menu bar. The AP/BHM responds by opening the Quick Start page. Figure 99 Disarm Installation page (top and bottom of page shown) Quick Start is a wizard that helps you to perform a basic configuration that places an AP/BHM into service. Only the following parameters must be configured:

Region Code RF Carrier Frequency Synchronization LAN (Network) IP Address Page 7-81 Chapter 7: Configuration Quick link setup In each Quick Start page, you can specify the settings to satisfy the requirements of the network. review the configuration selected. save the configuration to non-volatile memory. Procedure 12 Quick start wizard 1 2 At the bottom of the Quick Start tab, click the Go To Next Page button. From the pull-down menu, select the region in which the AP will operate. Figure 100 Regional Settings tab of AP/BHM 3 Click the Go To Next Page button. Page 7-82 Chapter 7: Configuration Quick link setup 4 From the pull-down menu, select a frequency for the test. Figure 101 Radio Carrier Frequency tab of AP/BHM 5 Click the Go To Next Page button. Page 7-83 Chapter 7: Configuration Quick link setup 6 At the bottom of this tab, select Generate Sync Signal. Figure 102 Synchronization tab of AP/BHM 7 Click the Go To Next Page button. Page 7-84 Chapter 7: Configuration Quick link setup 8 At the bottom of the IP address configuration tab, either specify an IP Address, a Subnet Mask, and a Gateway IP Address for management of the AP and leave the DHCP state set to Disabled. set the DHCP state to Enabled to have the IP address, subnet mask, and gateway IP address automatically configured by a domain name server (DNS). Figure 103 LAN IP Address tab of the AP/BHM Note Cambium encourages you to experiment with the interface. Unless you save a configuration and reboot the AP after you save the configuration, none of the changes are affected. 9 Click the Go To Next Page => button. Page 7-85 Chapter 7: Configuration Quick link setup 10 Ensure that the initial parameters for the AP are set as you intended. Figure 104 Review and Save Configuration tab of the AP/BHM 11 Click the Save Changes button. 12 Click the Reboot button. RESULT: The AP responds with the message Reboot Has Been Initiated Page 7-86 Chapter 7: Configuration Quick link setup 13 Wait until the indicator LEDs are not red. 14 Trigger your browser to refresh the page until the AP redisplays the General Status tab. 15 Wait until the red indicator LEDs are not lit. Configuring time settings Applicable products PMP : AP PTP: BHM To proceed with the test setup, click the Configuration link on the left side of the General Status page. When the AP responds by opening the Configuration page to the General page, click the Time tab. Figure 105 Time tab of the AP/BHM To have each log in the AP/BHM correlated to a meaningful time and date, either a reliable network element must pass time and date to the AP/BHM or you must set the time and date whenever a power cycle of the AP/BHM has occurred. A network element passes time and date in any of the following scenarios:

A connected CMM4 passes time and date (GPS time and date, if received). A separate NTP server is addressable from the AP/BHM. If the AP/BHM should obtain time and date from a CMM4, or a separate NTP server, enter the IP address of the CMM4 or NTP server on this tab. To force the AP/BHM to obtain time and date before the first (or next) 15-minute interval query of the NTP server, click Get Time through NTP. Page 7-87 Chapter 7: Configuration Quick link setup If you enter a time and date, the format for entry is Figure 106 Time and date entry formats Time :

hh Date :

MM

/

/

mm dd

/

/

ss yyyy where hh represents the two-digit hour in the range 00 to 24 mm represents the two-digit minute ss represents the two-digit second MM represents the two-digit month dd represents the two-digit day yyyy represents the four-digit year Proceed with the time setup as follows. Procedure 13 Entering AP/BHM time setup information 1 2 Enter the appropriate information in the format shown above. Then click the Set Time and Date button. Note The time displayed at the top of this page is static unless your browser is set to automatically refresh Powering the SM/BHS for test Procedure 14 Powering the SM/BHS for test 1 In one hand, securely hold the top (larger shell) of the SM/BHS. With the other hand, depress the lever in the back of the base cover (smaller shell). Remove the base cover. 2 3 4 5 Plug one end of a CAT 5 Ethernet cable into the SM PSU port Plug the other end of the Ethernet cable into the jack in the pig tail that hangs from the power supply Roughly aim the SM/BHS toward the AP/BHM Plug the power supply into an electrical outlet Warning From this point until you remove power from the AP/BHM, stay at least as far from the AP/BHM as the minimum separation distance specified in Calculated distances and power compliance margins. 6 Repeat the foregoing steps for each SM/BHS that you wish to include in the test. Page 7-88 Chapter 7: Configuration Quick link setup Viewing the Session Status of the AP/BHM to determine test registration Once the SMs/BHS under test are powered on, return to the computing device to determine if the SM/BHS units have registered to the AP/BHM. Note In order for accurate power level readings to be displayed, traffic must be present on the radio link. The Session Status tab provides information about each SM/BHS that has registered to the AP/BHM. This information is useful for managing and troubleshooting a system. All information that you have entered in the Site Name field of the SM/BHS displays in the Session Status tab of the linked AP/BHM. The Session Status tab also includes the current active values on each SM( or BHS) (LUID) for MIR, and VLAN, as well as the source of these values (representing the SM/BHS itself, Authentication Server, or the AP/BHM and cap, if anyfor example, APCAP as shown above).. As an SM/BHS registers to the AP/BHM, the configuration source that this page displays for the associated LUID may change. After registration, however, the displayed source is stable and can be trusted. Idle subscribers may be included or removed from the session status display by enabling or disabling, respectively, the Show Idle Sessions parameter. Enabling or disabling this parameter only affects the GUI display of subscribers, not the registration status. The SessionStatus.xml hyperlink allows user to export session status page from web management interface of AP/BHM. The session status page will be exported in xml file. Page 7-89 Chapter 7: Configuration Quick link setup Procedure 15 Viewing the AP Session Status page 1 On the AP web management GUI, navigate to Home, Session Status:

Figure 107 Session Status tab of AP Note Session status page for BHM is same as AP. 2 Verify that for each SM (or BHS) MAC address (printed on the SM/BHS housing) the AP/BHM has established a registered session by verifying the State status of each entry. The Session Status page of the AP/BHM is explained in Table 84. Page 7-90 Chapter 7: Configuration Quick link setup Table 84 Session Status Attributes AP Attribute Meaning Show Idle Sessions Idle subscribers may be included or removed from the session status display by enabling or disabling, respectively, the Show Idle Sessions parameter. Enabling or disabling this parameter only affects the GUI display of subscribers, not the registration status. Last Session Counter This field displays date and time stamp of last session counter reset. Reset Last Time Idle SMs This field displays date and time stamp of last Idle SMs Removed. On Removed click of Remove Idle SMs button, all the SMs which are in Idle state are flushed out. Data See Exporting Session Status page of AP/BHM on page 7-270 Device tab See Device tab on page 9-16 Session tab See Session tab on page 9-17 Power tab See Power tab on page 9-19 Configuration tab See Configuration tab on page 9-20 Page 7-91 Chapter 7: Configuration Configuring IP and Ethernet interfaces Configuring IP and Ethernet interfaces This task consists of the following sections:

Configuring the IP interface on page 7-93 Auxiliary port on page 7-96 NAT, DHCP Server, DHCP Client and DMZ on page 7-97 IP interface with NAT disabled on page 7-102 IP interface with NAT enabled on page NAT tab with NAT disabled on page 7-105 NAT tab with NAT enabled on page 7-108 NAT DNS Considerations on page 7-113 DHCP BHS on page 7-114 VLAN configuration for PMP on page 7-114 VLAN page of AP on page 7-117 VLAN page of SM on page 7-120 VLAN Membership tab of SM on page 7-124 VLAN configuration for PTP on page 7-124 NAT Port Mapping tab - SM on page 7-113 Page 7-92 Chapter 7: Configuration Configuring IP and Ethernet interfaces Configuring the IP interface The IP interface allows users to connect to the PMP/PTP 450 platform web interface, either from a locally connected computer or from a management network. Applicable products PMP : AP SM PTP: BHM BMS To configure the IP interface, follow these instructions:

Procedure 16 Configuring the AP/BHM IP interface 1 Select menu option Configuration > IP. The LAN configuration page is displayed:

2 3 4 Update IP Address, Subnet Mask and Gateway IP Address to meet network requirements (as specified by the network administrator). Review the other IP interface attributes and update them, if necessary (see Table 85 IP interface attributes). Click Save. Reboot Required message is displayed:

5 Click Reboot. The IP page of AP/SM/BHM/BHS is explained in Table 85. Page 7-93 Chapter 7: Configuration Configuring IP and Ethernet interfaces Table 85 IP interface attributes Attribute Meaning IP Address Internet Protocol (IP) address. This address is used by family of Internet protocols to uniquely identify this unit on a network. Subnet Mask Defines the address range of the connected IP network. The IP address of a computer on the current network that acts as a gateway. A gateway acts as an entrance and exit to packets from and to other networks. DHCP state If Enabled is selected, the DHCP server automatically assigns the IP configuration (IP address, subnet mask, and gateway IP address) and the values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable (read only), in the Network Interface tab of the Home page. DNS IP Address Canopy devices allow for configuration of a preferred and alternate DNS server IP address either automatically or manually. Devices must set DNS server IP address manually when DHCP is disabled for the management interface of the device. DNS servers may be configured automatically from the DHCP response when DHCP is enabled for the management interface of the device. Optionally devices may be configured to set the DNS server IP address manually when DHCP is enabled for the management interface. The default DNS IP addresses are 0.0.0.0 when configured manually. Preferred DNS The first address used for DNS resolution. Server Alternate DNS If the Preferred DNS server cannot be reached, the Alternate DNS Server Server is used. Domain Name The operators management domain name may be configured for DNS. The domain name configuration can be used for configuration of the servers in the operators network. The default domain name is example.com, and is only used if configured as such. Page 7-94 Chapter 7: Configuration Configuring IP and Ethernet interfaces LAN2 Network It is recommended not to change this parameter from the default Interface AP/BHM private IP address of 192.168.101.1. A /24 CIDR subnet is used to Configuration (Radio communicate with each of the SMs/BHS that are registered. The AP/BHM Private Interface) IP uses a combination of the private IP and the LUID (logical unit ID) of the Address SM/BHS. It is only displayed for AP and BHM. Table 86 SM/BHS private IP and LUID SM/BHS LUID Private IP First SM/BHS registered Second SM/BHS registered 2 3 192.168.101.2 192.168.101.3 Page 7-95 Chapter 7: Configuration Configuring IP and Ethernet interfaces Auxiliary port An additional Ethernet port labeled Aux for Auxiliary port is implemented for downstream traffic. This feature is supported only for PTP/PMP 450i series devices. To enable the Aux port, follow these instructions:

Procedure 17 Enabling Aux port interface 1 Select menu option Configuration > IP > Aux Network Interface tab.:

Click Enable button of Aux Ethernet Port parameter to enable Aux Ethernet port Click Enable button of Aux Ethernet Port PoE parameter to enable Aux port PoE out. Click Save. Reboot Required message is displayed. Click Reboot. 2 3 4 5 Table 87 Aux port attributs Attribute Meaning Aux Ethernet Port Enabled: Data is enabled for Auxiliary port Disabled: Data is disabled for Auxiliary port Aux Ethernet Port Enabled: PoE out is enable for Auxiliary port PoE Disabled: PoE out is disabled for Auxiliary port By disabling this feature, the data at the Auxiliary port will be disabled. Page 7-96 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT, DHCP Server, DHCP Client and DMZ Applicable products PMP :

SM The system provides NAT (Network Address Translation) for SMs in the following combinations of NAT and DHCP (Dynamic Host Configuration Protocol):

NAT Disabled NAT with DHCP Client (DHCP selected as the Connection Type of the WAN interface) and DHCP Server NAT with DHCP Client(DHCP selected as the Connection Type of the WAN interface) NAT with DHCP Server NAT without DHCP NAT NAT isolates devices connected to the Ethernet or wired side of a SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic

(separate from its address for management), terminates transport traffic and allows you to assign a range of IP addresses to devices that are connected to the Ethernet or wired side of the SM. In the Cambium system, NAT supports many protocols, including HTTP, ICMP (Internet Control Message Protocols), and FTP (File Transfer Protocol). For virtual private network (VPN) implementation, L2TP over IPSec (Level 2 Tunneling Protocol over IP Security) and PPTP (Point to Point Tunneling Protocol) are supported. Note When NAT is enabled, a reduction in throughput is introduced in the system (due to processing overhead). DHCP DHCP enables a device to be assigned a new IP address and TCP/IP parameters, including a default gateway, whenever the device reboots. Thus DHCP reduces configuration time, conserves IP addresses, and allows modules to be moved to a different network within the Cambium system. In conjunction with the NAT features, each SM provides the following:

A DHCP server that assigns IP addresses to computers connected to the SM by Ethernet protocol. A DHCP client that receives an IP address for the SM from a network DHCP server. Page 7-97 Chapter 7: Configuration Configuring IP and Ethernet interfaces DMZ In conjunction with the NAT features, a DMZ (Demilitarized Zone) allows the allotment of one IP address behind the SM for a device to logically exist outside the firewall and receive network traffic. The first three octets of this IP address must be identical to the first three octets of the NAT private IP address. A DHCP server that assigns IP addresses to computers connected to the SM by Ethernet protocol. A DHCP client that receives an IP address for the SM from a network DHCP server. NAT Disabled The NAT Disabled implementation is illustrated in Figure 108. Figure 108 NAT disabled implementation NAT with DHCP Client and DHCP Server The NAT with DHCP Client and DHCP server is illustrated in Figure 109. Page 7-98 Chapter 7: Configuration Configuring IP and Ethernet interfaces Figure 109 NAT with DHCP client and DHCP server implementation NAT with DHCP Client Figure 110 NAT with DHCP client implementation Page 7-99 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT with DHCP Server Figure 111 NAT with DHCP server implementation NAT without DHCP Figure 112 NAT without DHCP implementation Page 7-100 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT and VPNs VPN technology provides the benefits of a private network during communication over a public network. One typical use of a VPN is to connect employees remotely (who are at home or in a different city), with their corporate network through a public Internet. Any of several VPN implementation schemes is possible. By design, NAT translates or changes addresses, and thus interferes with a VPN that is not specifically supported by a given NAT implementation. With NAT enabled, SM supports L2TP over IPSec (Level 2 Tunneling Protocol over IP Security) VPNs and PPTP (Point to Point Tunneling Protocol) VPNs. With NAT disabled, SM supports all types of VPNs. Page 7-101 Chapter 7: Configuration Configuring IP and Ethernet interfaces IP interface with NAT disabled - SM The IP page of SM with NAT disabled is explained in Table 88. Table 88 IP attributes - SM with NAT disabled Attribute Meaning IP Address Enter the non-routable IP address to associate with the Ethernet connection on this SM. (The default IP address from the factory is 169.254.1.1.) If you forget this parameter, you must both:

physically access the module. use recovery mode to access the module configuration parameters at 169.254.1.1. See Radio recovery mode on page 1-22 Note Note or print the IP settings from this page. Ensure that you can readily associate these IP settings both with the module and with the other data that you store about the module. Network Specify whether the IP address of the SM must be visible to only a Accessibility device connected to the SM by Ethernet (Local) or be visible to the AP/BHM as well (Public). Subnet Mask Enter an appropriate subnet mask for the SM to communicate on the network. The default subnet mask is 255.255.0.0. Gateway IP Address Enter the appropriate gateway for the SM to communicate with the network. The default gateway is 169.254.0.0. DHCP state If you select Enabled, the DHCP server automatically assigns the IP configuration (IP address, subnet mask, and gateway IP address) and the values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable, but not settable, in the Network Interface tab of the Home page. Page 7-102 Chapter 7: Configuration Configuring IP and Ethernet interfaces In this tab, DHCP State is settable only if the Network Accessibility parameter in the IP tab is set to Public. This parameter is also settable in the NAT tab of the Configuration web page, but only when NAT is enabled. If the DHCP state parameter is set to Enabled in the Configuration > IP sub-menu of the SM/BHS, do not check the BootpClient option for Packet Filter Types in its Protocol Filtering tab, because doing so can block the DHCP request. (Filters apply to all packets that leave the SM via its RF interface, including those that the SM itself generates.) If you want to keep DHCP enabled and avoid the blocking scenario, select the Bootp Server option instead. This will result in responses being appropriately filtered and discarded. DHCP DNS IP Canopy devices allow for configuration of a preferred and alternate DNS Address server IP address either automatically or manually. Devices must set DNS server IP address manually when DHCP is disabled for the management interface of the device. DNS servers may be configured automatically from the DHCP response when DHCP is enabled for the management interface of the device. Optionally devices may be configured to set the DNS server IP address manually when DHCP is enabled for the management interface. The default DNS IP addresses are 0.0.0.0 when configured manually. Preferred DNS The first DNS server used for DNS resolution. Server Alternate DNS The second DNS server used for DNS resolution. Server Domain Name The operators management domain name may be configured for DNS. The domain name configuration can be used for configuration of the servers in the operators network. The default domain name is example.com, and is only used if configured as such. Page 7-103 Chapter 7: Configuration Configuring IP and Ethernet interfaces IP interface with NAT enabled - SM The IP page of SM with NAT enabled is explained in Table 89. Table 89 IP attributes - SM with NAT enabled Attribute Meaning IP Address Assign an IP address for SM/BHS management through Ethernet access to the SM/BHS. Set only the first three bytes. The last byte is permanently set to 1. This address becomes the base for the range of DHCP-assigned addresses. Subnet Mask Assign a subnet mask of 255.255.255.0 or a more restrictive subnet mask. Set only the last byte of this subnet mask. Each of the first three bytes is permanently set to 255. Page 7-104 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT tab with NAT disabled - SM The NAT tab of SM with NAT disabled is explained in Table 90. Table 90 NAT attributes - SM with NAT disabled Page 7-105 Chapter 7: Configuration Configuring IP and Ethernet interfaces Attribute Meaning NAT Enable/Disable This parameter enables or disables the Network Address Translation

(NAT) feature for the SM. NAT isolates devices connected to the Ethernet or wired side of a SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic separate from its address for management, terminates transport traffic, and allows you to assign a range of IP addresses to devices that are connected to the Ethernet or wired side of the SM. When NAT is enabled, VLANs are not supported on the wired side of that SM. You can enable NAT in SMs within a sector where VLAN is enabled in the AP/BHM, but this may constrain network design. IP Address This field displays the IP address for the SM. DHCP Server will not automatically assign this address when NAT is disabled. Subnet Mask This field displays the subnet mask for the SM. DHCP Server will not automatically assign this address when NAT is disabled. Gateway IP Address This field displays the gateway IP address for the SM. DHCP Server will not automatically assign this address when NAT is disabled. ARP Cache Timeout If a router upstream has an ARP cache of longer duration (as some use 30 minutes), enter a value of longer duration than the router ARP cache. The default value of this field is 20 minutes. TCP Session Where a large network exists behind the SM, you can set this parameter Garbage Timeout to lower than the default value of 120 minutes. This action makes additional resources available for greater traffic than the default value accommodates. UDP Session You may adjust this parameter in the range of 1 to 1440 minutes, based Garbage Timeout on network performance. The default value of this parameter is 4 minutes. Translation Table Total number of minutes that have elapsed since the last packet transfer Size between the connected device and the SM/BHS. Page 7-106 Chapter 7: Configuration Configuring IP and Ethernet interfaces Note When NAT is disabled, the following parameters are not required to be configurable:

WAN Inter face > Connection Type, IP Address, Subnet Mask, Gateway IP address LAN Interface > IP Address LAN DHCP Server > DHCP Server Enable/Disable, DHCP Server Lease Timeout, Number of IPs to Lease, DNS Server Proxy, DNS IP Address, Preferred DNS IP address, Alternate DNS IP address Remote Management Interface > Remote Management Interface, IP address, Subnet Mask, DHCP DNS IP Address, Preferred DNS Server, Alternate DNS Server, Domain Name NAT Protocol Parameters > ARP Cache Timeout, TCP Session Garbage Timeout, UDP Session Garbage Timeout, Translation Table Size Page 7-107 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT tab with NAT enabled - SM The NAT tab of SM with NAT enabled is explained in Table 91. Table 91 NAT attributes - SM with NAT enabled Page 7-108 Chapter 7: Configuration Configuring IP and Ethernet interfaces Attribute Meaning NAT Enable/Disable This parameter enables or disabled the Network Address Translation

(NAT) feature for the SM. NAT isolates devices connected to the Ethernet or wired side of a SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic separate from its address for management, terminates transport traffic, and allows you to assign a range of IP addresses to devices that are connected to the Ethernet or wired side of the SM. When NAT is enabled, VLANs are not supported on the wired side of that SM. You can enable NAT in SMs within a sector where VLAN is enabled in the AP, but this may constrain network design. WAN Interface The WAN interface is the RF-side address for transport traffic. Connection Type This parameter may be set to Static IPwhen this is the selection, all three parameters (IP Address, Subnet Mask, and Gateway IP Address) must be properly populated. DHCPwhen this is the selection, the information from the DHCP server configures the interface. PPPoEwhen this is the selection, the information from the PPPoE server configures the interface. Subnet Mask If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the subnet mask of the SM for RF transport traffic. Gateway IP Address If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the gateway IP address for the SM for RF transport traffic. Reply to Ping on By default, the radio interface does not respond to pings. If you use a WAN Interface management system (such as WM) that will occasionally ping the SM, set this parameter to Enabled. LAN Interface The LAN interface is both the management access through the Ethernet port and the Ethernet-side address for transport traffic. When NAT is enabled, this interface is redundantly shown as the NAT Network Interface Configuration on the IP tab of the Configuration web page in the SM. IP Address Assign an IP address for SM/BHS management through Ethernet access to the SM. This address becomes the base for the range of DHCP-

assigned addresses. Subnet Mask Assign a subnet mask of 255.255.255.0 or a more restrictive subnet mask. Set only the last byte of this subnet mask. Each of the first three bytes is permanently set to 255. DMZ Enable Either enable or disable DMZ for this SM/BHS. Page 7-109 Chapter 7: Configuration Configuring IP and Ethernet interfaces DMZ IP Address If you enable DMZ in the parameter above, set the last byte of the DMZ host IP address to use for this SM when DMZ is enabled. Only one such address is allowed. The first three bytes are identical to those of the NAT private IP address. Ensure that the device that receives network traffic behind this SM is assigned this address. The system provides a warning if you enter an address within the range that DHCP can assign. DHCP Server This is the server (in the SM) that provides an IP address to the device DHCP Server Enable/Disable connected to the Ethernet port of the SM. Select either Enabled or Disabled. Enable to:

Allow this SM to assign IP addresses, subnet masks, and gateway IP addresses to attached devices. Assign a start address for DHCP. Designate how many IP addresses may be temporarily used (leased). Disable to:

Restrict SM/BHS from assigning addresses to attached devices. DHCP Server Lease Based on network performance, enter the number of days between Timeout when the DHCP server assigns an IP address and when that address expires. The range of values for this parameter is 1 to 30 days. The default value is 30 days. DHCP Start IP If you enable DHCP Server below, set the last byte of the starting IP address that the DHCP server assigns. The first three bytes are identical to those of the NAT private IP address. Number of IPs to Enter how many IP addresses the DHCP server is allowed to assign. The Lease default value is 50 addresses. DNS Server Proxy This parameter enables or disables advertisement of the SM/BHS as the DNS server. On initial boot up of a SM with the NAT WAN interface configured as DHCP or PPPoE, the SM module will not have DNS information immediately. With DNS Server Proxy disabled, the clients will renew their lease about every minute until the SM has the DNS information to give out. At this point the SM will go to the full configured lease time period which is 30 days by default. With DNS Server Proxy enabled, the SM will give out full term leases with its NAT LAN IP as the DNS server. DNS IP Address Select either:

Obtain Automatically to allow the system to set the IP address of the DNS server or Set Manually to enable yourself to set both a preferred and an alternate DNS IP address. Preferred DNS IP Enter the preferred DNS IP address to use when the DNS IP Address Address parameter is set to Set Manually. Page 7-110 Chapter 7: Configuration Configuring IP and Ethernet interfaces Alternate DNS IP Enter the DNS IP address to use when the DNS IP Address parameter is Address set to Set Manually and no response is received from the preferred DNS IP address. Remote To offer greater flexibility in IP address management, the NAT-enabled Management SMs configured WAN Interface IP address may now be used as the Interface device Remote Management Interface (unless the SMs PPPoE client is set to Enabled) Disable: When this interface is set to Disable, the SM is not directly accessible by IP address. Management access is only possible through either the LAN (Ethernet) interface or a link from an AP web page into the WAN (RF-side) interface. Enable (Standalone Config): When this interface is set to Enable

(Standalone Config), to manage the SM/BHS the device must be accessed by the IP addressing information provided in the Remote Configuration Interface section. Note When configuring PPPoE over the link, use this configuration option (PPPoE traffic is routed via the IP addressing specified in section Remote Configuration Interface). Enable (Use WAN Interface): When this interface is set to Enable (Use WAN Interface), the Remote Configuration Interface information is greyed out, and the SM is managed via the IP addressing specified in section WAN Interface). Note When using this configuration, the ports defined in section Configuration, Port Configuration are consumed by the device. For example, if FTP Port is configured as 21 by the SM, an FTP server situated below the SM must use a port other than 21. This also applies to DMZ devices; any ports specified in section Configuration, Port Configuration will not be translated through the NAT, they is consumed by the devices network stack for management. Connection Type This parameter can be set to:

Static IPwhen this is the selection, all three parameters (IP Address, Subnet Mask, and Gateway IP Address) must be properly populated. DHCPwhen this is the selection, the information from the DHCP server configures the interface. IP Address If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the IP address of the SM for RF management traffic. Subnet Mask If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the subnet mask of the SM for RF management traffic. Page 7-111 Chapter 7: Configuration Configuring IP and Ethernet interfaces Gateway IP Address If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the gateway IP address for the SM for RF management traffic. Note or print the IP settings from this page. Ensure that you can readily associate these IP settings both with the module and with the other data that you store about the module. DHCP DNS IP Select either:

Address Obtain Automatically to allow the system to set the IP address of the DNS server. or Set Manually to enable yourself to set both a preferred and an alternate DNS IP address. Preferred DNS Enter the preferred DNS IP address to use when the DNS IP Address Server parameter is set to Set Manually. Alternate DNS Enter the DNS IP address to use when the DNS IP Address parameter is Server set to Set Manually and no response is received from the preferred DNS IP address. Domain Name Domain Name to use for management DNS configuration. This domain name may be concatenated to DNS names used configured for the remote configuration interface. ARP Cache Timeout If a router upstream has an ARP cache of longer duration (as some use 30 minutes), enter a value of longer duration than the router ARP cache. The default value of this field is 20 (minutes). TCP Session Where a large network exists behind the SM, you can set this parameter Garbage Timeout to lower than the default value of 120 (minutes). This action makes additional resources available for greater traffic than the default value accommodates. UDP Session You may adjust this parameter in the range of 1 to 1440 minutes, based Garbage Timeout on network performance. The default value of this parameter is 4

(minutes). Page 7-112 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT DNS Considerations - SM SM DNS behavior is different depending on the accessibility of the SM. When NAT is enabled the DNS configuration that is discussed in this document is tied to the RF Remote Configuration Interface, which must be enabled to utilize DNS Client functionality. Note that the WAN DNS settings when NAT is enabled are unchanged with the addition of the management DNS feature discussed in this document. Table 92 SM DNS Options with NAT Enabled NAT Management Interface DHCP Status DNS Status Configuration Accessibility RF Remote N/A DNS Disabled Management Interface Disabled NAT Enabled RF Remote DHCP Disabled DNS Static Configuration Management Interface Enabled DHCP Enabled DNS from DHCP or DNS Static Configuration NAT Port Mapping tab - SM The NAT Port Mapping tab of the SM is explained in Table 93. Table 93 NAT Port Mapping attributes - SM Attribute Meaning Port Map 1 to 10 Separate parameters allow you to distinguish NAT ports from each other by assigning a unique combination of port number, protocol for traffic through the port, and IP address for access to the port Page 7-113 Chapter 7: Configuration Configuring IP and Ethernet interfaces DHCP BHS Applicable products PTP: BHM DHCP enables a device to be assigned a new IP address and TCP/IP parameters, including a default gateway, whenever the device reboots. Thus DHCP reduces configuration time, conserves IP addresses, and allows modules to be moved to a different network within the Cambium system. In conjunction with the NAT features, each BHS provides:

A DHCP server that assigns IP addresses to computers connected to the BHS by Ethernet protocol. A DHCP client that receives an IP address for the BHS from a network DHCP server. Reconnecting to the management PC If the IP Address, Subnet Mask and Gateway IP Address of the unit have been updated to meet network requirements, then reconfigure the local management PC to use an IP address that is valid for the network. See Configuring the management PC on page 7-73. Once the unit reboots, log in using the new IP address. See Logging into the web interface on page 7-75. VLAN configuration for PMP Applicable products PMP : AP SM VLAN Remarking VLAN Remarking feature allows the user to change the VLAN ID and priority of both upstream and downstream packets at the Ethernet Interface. The remarking configuration is available for:

1. VLAN ID re-marking 2. 802.1p priority re-marking Note For Q-in-Q VLAN tagged frame, re-marking is performed on the outer tag. Page 7-114 Chapter 7: Configuration Configuring IP and Ethernet interfaces VLAN ID Remarking SM supports the ability to re-mark the VLAN ID on both upstream and downstream VLAN frames at the Ethernet interface. For instance, a configuration can be added to re-mark VLAN ID x to VLAN ID y as shown in Table 94. AP does not support VLAN ID remarking. Table 94 VLAN Remarking Example VLAN frame direction Remarking SM receives VLAN ID x frame at the Ethernet interface, checks the configuration and re-marks to VLAN ID y. So VLAN ID y frame Upstream comes out of APs Ethernet interface. When SM re-marks, a dynamic entry in VLAN membership table for y is added to allow reception of VLAN ID y downstream packet. AP receives VLAN ID y frame at the Ethernet interface and sends to SM. SM accepts the frame as it has an entry in the membership table and re-marks to VLAN ID x. This reverse re- marking is necessary because the downstream devices do not know of re-

marking and are expecting VLAN x frames. This remarking is done just before sending the packet out on Ethernet interface. Downstream 802.1P Remarking AP/BHM and SM/BHS allow re-marking of 802.1p priority bits for the frames received at the Ethernet interface. Priority bits are not re-marked for the packets sent out of Ethernet interface

(reverse direction). Configuration must be added at SM/BHS for upstream frames and at AP/BHM for downstream frames. VLAN Priority Bits configuration VLAN Priority Bits Configuration feature allows the user to configure the three 802.1p bits upon assigning VLAN to an ingress packet. The priority bits configuration is available for:

Default Port VID Provider VID MAC Address mapped Port VID Management VID Default Port VID This VID is used for untagged frames and will correspond to the Q-Tag for 802.1Q frames (if VLAN Port Type is Q), or the C-Tag for 802.1ad frames (if the VLAN Port Type is QinQ). The priority bits used in the Q-tag/C-tag are configurable. The configuration can be:

Page 7-115 Chapter 7: Configuration Configuring IP and Ethernet interfaces Promote IPv4/IPv6 priority The priority in the IP header is copied to the Q-tag/C-tag. Define priority Specify the priority in the range of 0 to 7. This value is used as priority in the Q-tag/C-tag. MAC Address Mapped VID If a packet arrives at the SM/BHS that is sourced from a device whose MAC address is in the table, then the corresponding VID is used for that frames Q-tag (Q port) or C-tag (QinQ port). The priority bits used in the Q-tag/C-tag are configurable similar to default port VID. Provider VID The provider VID is used for the S-tag. The priority bits used in the S-tag are configurable similar to default port VID. Provider VID has an extra priority configuration:

Copy inner tag 802.1p priority The priority in the C-tag is copied to the S-tag. Management VID This VID is used to communicate with AP/BHM and SM/BHS for management purposes. The priority bits used in the Q-tag are configurable similar to default port VID. Use APs Management VID for ICC connected SM This feature allows the SM to use the APs management VLAN ID when the SM is registered to the AP via ICC. This feature is useful for the customer who uses a different management VID for the SM and AP and Zero Touch feature is enabled for configuration. This parameter may be accessed via the Configuration > VLAN page on the APs web management interface. Page 7-116 Chapter 7: Configuration VLAN page of AP The VLAN tab of the AP/BHM is explained in Table 95. Table 95 AP/BHM VLAN tab attributes Configuring IP and Ethernet interfaces Attribute Meaning VLAN Specify whether VLAN functionality for the AP and all linked SMs must

(Enabled) or may not (Disabled) be allowed. The default value is Disabled. Always use Local Enable this option before you reboot this AP as a SM to use it to perform VLAN Config spectrum analysis. Once the spectrum analysis completes, disable this option before you reboot the module as an AP, Allow Frame Types Select the type of arriving frames that the AP must tag, using the VID that is stored in the Untagged Ingress VID parameter. The default value is All Frames. Dynamic Learning Specify whether the AP must (Enabled) or not (Disabled) add the VLAN IDs (VIDs) of upstream frames to the VID table. (The AP passes frames with VIDs that are stored in the table both upstream and downstream.). The default value is Enabled. Page 7-117 Chapter 7: Configuration Configuring IP and Ethernet interfaces VLAN Aging Timeout Specify how long the AP must keep dynamically learned VIDs. The range of values is 5 to 1440 (minutes). The default value is 25 (minutes). Note VIDs that you enter for the Management VID and VLAN Membership parameters do not time out. Management VID Enter the VID that the operator wishes to use to communicate with the module manager. The range of values is 1 to 4095. The default value is 1. QinQ EtherType Modules can be configured with 802.1ad Q-in-Q DVLAN (Double-VLAN) tagging which is a way for an operator to put an 802.1Q VLAN inside of an 802.1ad VLAN. A nested VLAN, which is the original 802.1Q tag and a new second 802.1ad tag, allows for bridging of VLAN traffic across a network and segregates the broadcast domains of 802.1Q VLANs. Q-in-Q can be used with PPPoE and/or NAT. The 802.1ad standard defines the S-VLAN as the Service Provider VLAN and the C-VLAN as the customer VLAN. The radio software does 2 layer Q-in-Q whereby the C-VLAN is the 802.1Q tag and the S-VLAN is the second layer Q tag as shown below:

Table 96 Q-in-Q Ethernet frame Ethernet S-VLAN C-VLAN EthType IP Data EthType Header EthType 0x88a8 0x8100 0x0800 The 802.1ad S-VLAN is the outer VLAN that is configurable on the Configuration > VLAN web page of the AP. The Q-in-Q EtherType parameter is configured with a default EtherType of 0x88a8 in addition to four alternate EtherTypes that can be configured to aid in interoperability with existing networks that use a different EtherType than the default. The C-VLAN is the inner VLAN tag, which is the same as 802.1Q. As a top level concept, this operates on the outermost tag at any given time, either pushing a tag on or popping a tag off. This means packets will at most transition from an 802.1Q frame to an 801.ad frame (with a tag pushed on) or an untagged 802.1 frame (with the tag popped off. Similarly, for an 802.1ad frame, this can only transition from an 802.1ad frame to an 802.1Q frame (with the tag popped off) since the radio software only supports 2 levels of tags Use AP's This field allows the SM to use the APs management VLAN ID when the Management VID for SM is registered to the AP via ICC. ICC connected SM Page 7-118 Chapter 7: Configuration Configuring IP and Ethernet interfaces VLAN Not Active When VLAN is enabled in the AP, the Active Configuration block provides the following details as read-only information in this tab. In the Cambium fixed wireless broadband IP network, each device of any type is automatically a permanent member of VID 1. This facilitates deployment of devices that have VLAN enabled with those that do not. VLAN Membership For each VLAN in which you want the AP to be a member, enter the Table Configuration VLAN ID and then click the Add Member button. Similarly, for any VLAN in which you want the AP to no longer be a member, enter the VLAN ID and then click the Remove Member button. VLAN Membership This field lists the VLANs that an AP is a member of. As the user adds a table number between 1 and 4094, this number is populated here. Source VLAN

(Range: 1-4094) Enter the VID for which the operator wishes to remark the 802.1p priority for the downstream packets. The range of values is 1 to 4094. The default value is 1. Remark Priority This is the priority you can assign to the VLAN Tagged packet. Priority of

(Range 0-7) 0 is the highest. VLAN Remarking As the user enters a VLAN and a Remarking priority, this information is table added in this table. Page 7-119 Chapter 7: Configuration VLAN page of SM The VLAN tab of SM/BHS is explained in Table 97. Table 97 SM VLAN attributes Configuring IP and Ethernet interfaces Attribute Meaning VLAN Port Type By default this is Q, indicating that it is to operate in the existing manner. The other option is Q-in-Q, which indicates that it must be adding and removing the S-Tag, and adding a C-Tag if necessary for untagged packets. The VLAN Port type corresponds to the Ethernet port of the SM/BHS. Currently, the internal management interfaces will always operate as Q ports. Page 7-120 Chapter 7: Configuration Configuring IP and Ethernet interfaces Accept QinQ Frames This option is valid for the Q-in-Q port so that the user may force blocking of existing 802.1ad Q-in-Q frames. This way, only untagged or single tagged packets will come in and out of the Ethernet interface. If a Q-in-Q frame is about ingress or egress the Ethernet interface and this is disabled, it is dropped and a filter entry will show up on the VLAN Statistics page as DVLAN Egress or DVLAN Ingress. Allow Frame Types Select the type of arriving frames that the SM must tag, using the VID that is stored in the Untagged Ingress VID parameter. The default value is All Frames. Tagged Frames Only: The SM only tags incoming VLAN-tagged frames Untagged Frames Only: The SM will only tag incoming untagged frames Dynamic Learning Specify whether the SM must (Enable) or not (Disable) add the VIDs of upstream frames (that enter the SM through the wired Ethernet interface) to the VID table. The default value is Enable. VLAN Aging Timeout Specify how long the SM/BHS must keep dynamically learned VIDs. The range of values is 5 to 1440 (minutes). The default value is 25 (minutes). Note VIDs that you enter for the Untagged Ingress VID and Management VID parameters do not time out. Management VID Enter the VID that the SM/BHS must share with the AP/BHM. The range of values is 1 to 4095. The default value is 1. SM Management Specify whether to allow the SM/BHS (Enabled) or the AP/RADIUS VID Pass-through

(Disabled) to control the VLAN settings of this SM. The default value is Enabled. When VLAN is enabled in the AP to whom this SM is registered, the Active Configuration block provides the following details as read-only information in this tab. In the Cambium fixed wireless broadband IP network, each device of any type is automatically a permanent member of VID 1. This facilitates deployment of devices that have VLAN enabled with those that do not. If disabled, MVID traffic is not allowed to or from the SM wired interface. Also, if Management VID is the same as a Port VID (Default or MAC-

based), then this setting is ignored and assumed to be Enabled. Default Port VID This is the VID that is used for untagged frames and will correspond to the Q-Tag for 802.1Q frames (if VLAN Port Type is Q), or the C-Tag for 802.1ad frames (if the VLAN Port Type is Q-in- Q). Page 7-121 Chapter 7: Configuration Configuring IP and Ethernet interfaces Port VID MAC These parameters allow operators to place specific devices onto Address Mapping different VLANs (802.1Q tag or 802.1ad C-tag) based on the source MAC address of the packet. If the MAC address entry is 00-00-00-00-00-

00 then that entry is not used. If a packet arrives at the SM that is sourced from a device whose MAC address is in the table, then the corresponding VID is used for that frames Q-tag (Q port) or C-tag (Q-

in-Q port). If there is no match, then the Default Port VID is used. This table is also used in the downstream direction for removal of the tag based on the destination MAC address so that an untagged (for Q port) or Q-Tagged (for Q-in-Q port) frame is delivered to the end device. You may use wildcards for the non-OUI (Organizationally Unique Identifier) portion of the MAC address, which is the last 3 bytes. MAC addresses contain 6 bytes, the first 3 of which are the OUI of the vendor that manufactured the device and the last 3 are unique to that vendor OUI. If you want to cover all devices from a known vendors OUI, you have to specify 0xFF for the remaining 3 bytes. So, for example, if you wanted all devices from a specific vendor with an OUI of 00-95-5b

(which is a Netgear OUI) to be on the same VID of 800, you have to specify an entry with MAC address 00-95-5b-ff-ff-ff. Then, any device underneath of the SM with MAC addresses starting with 00-95-5b is put on VLAN 800. Provider VID The provider VID is used for the S-tag. It is only used if the Port Type is Q-in-Q and will always be used for the S-tag. If an existing 802.1Q frame arrives, the Provider VID is what is used for adding and removing of the outer S-tag. If an untagged frame arrives to a Q-in-Q port, then the Provider VID is the S-tag and the Default Port VID (or Port VID MAC Address Mapping, if valid) is used for the C-tag. Active Configuration, This is the value of the parameter of the same name, configured above. Default Port VID Active Configuration, This is the listing of the MAC address VIDs configured in Port VID MAC MAC Address VID Address Mapping. Map Active Configuration, This is the value of the parameter of the same name, configured above. Management VID Active Configuration, This is the value of the parameter of the same name, configured above. SM Management VID Pass-Through Active Configuration, This is the value of the VLAN Aging Timeout parameter configured Dynamic Aging above. Timeout Active Configuration, Yes is displayed if the value of the Dynamic Learning parameter above is Allow Learning Enabled. No is displayed if the value of Dynamic Learning is Disabled. Page 7-122 Chapter 7: Configuration Configuring IP and Ethernet interfaces Active Configuration, This displays the selection that was made from the drop-down list at the Allow Frame Type Allow Frame Types parameter above. Active Configuration, This is set to Enabled if VLAN Port Type is set to QinQ, and is set to QinQ Disabled if VLAN Port Type is set to Q. Active Configuration, This is the value of the QinQ EtherType configured in the AP. QinQ EthType Active Configuration, This is the value of Accept QinQ Frames, configured above. Allow QinQ Tagged Frames Active Configuration, This column lists the ID numbers of the VLANs in which this module is a Current VID Member member, whether through assignment or through dynamic learning. Set, VID Number Active Configuration, For each VID number in the first column, the entry in this column Current VID Member correlates the way in which the module became and continues to be a Set, Type member:

PermanentThis indicates that the module was assigned the VID number through direct configuration by the operator. DynamicThis indicates that the module adopted the VID number through enabled dynamic learning, when a tagged packet from a SM behind it in the network or from a customer equipment that is behind the SM in this case, was read. Active Configuration, For each VID number in the first column of the table, the entry in this Current VID Member column reflects whether or when the VID number will time out:

Set, Age Permanent type - Number never times out and this is indicated by the digit 0. Dynamic type - Age reflects what is configured in the VLAN Aging Timeout parameter in the Configuration => VLAN tab of the AP or reflects a fewer number of minutes that represents the difference between what was configured and what has elapsed since the VID was learned. Each minute, the Age decreases by one until, at zero, the AP deletes the learned VID, but can it again from packets sent by elements that are beneath it in the network. Note Values in this Active Configuration block can differ from attempted values in configurations:

The AP can override the value that the SM has configured for SM Management VID Pass-Through. Page 7-123 Chapter 7: Configuration Configuring IP and Ethernet interfaces VLAN Membership tab of SM The Configuration > VLAN > VLAN Membership tab is explained in Table 98. Table 98 SM VLAN Membership attributes Attribute Meaning VLAN Membership For each VLAN in which you want the AP to be a member, enter the Table Configuration VLAN ID and then click the Add Member button. Similarly, for any VLAN in which you want the AP to no longer be a member, enter the VLAN ID and then click the Remove Member button. VLAN configuration for PTP Applicable products PTP: BHM BMS VLAN page of BHM The VLAN tab of BHS is explained in Table 99. Table 99 BHM VLAN page attributes Page 7-124 Chapter 7: Configuration Configuring IP and Ethernet interfaces Attribute Meaning VLAN Specify whether VLAN functionality for the BHM and all linked BHS must be (Enabled) or may not (Disabled) be allowed. The default value is Disabled. VLAN Port Type By default this is Q, indicating that it is to operate in the existing manner. The other option is Q-in-Q, which indicates that it must be adding and removing the S-Tag, and adding a C-Tag if necessary for untagged packets. The VLAN Port type corresponds to the Ethernet port of the BHS. Currently, the internal management interfaces will always operate as Q ports. Accept QinQ Frames This option is valid for the Q-in-Q port so that the user may force blocking of existing 802.1ad Q-in-Q frames. This way, only untagged or single tagged packets will come in and out of the Ethernet interface. If a Q-in-Q frame is about ingress or egress the Ethernet interface and this is disabled, it is dropped and a filter entry will show up on the VLAN Statistics page as DVLAN Egress or DVLAN Ingress. Management VID Enter the VID that the BHS must share with the BHM. The range of

(Range 1-4094) values is 1 to 4095. The default value is 1. Default Port VID This is the VID that is used for untagged frames and corresponds to the

(Range 1-4094) Q-Tag for 802.1Q frames (if VLAN Port Type is Q), or the C-Tag for 802.1ad frames (if the VLAN Port Type is Q-in- Q). QinQ Ether Type Modules can be configured with 802.1ad Q-in-Q DVLAN (Double-VLAN) tagging which is a way for an operator to put an 802.1Q VLAN inside of an 802.1ad VLAN. A nested VLAN, which is the original 802.1Q tag and a new second 802.1ad tag, allows for bridging of VLAN traffic across a network and segregates the broadcast domains of 802.1Q VLANs. Q-in-Q can be used with PPPoE and/or NAT. The 802.1ad standard defines the S-VLAN as the Service Provider VLAN and the C-VLAN as the customer VLAN. The radio software does 2 layer Q-in-Q whereby the C-VLAN is the 802.1Q tag and the S-VLAN is the second layer Q tag as shown below:

Ethernet Header S-VLAN EthType C-VLAN IP Data EthType 0x88a8 EthType 0x8100 0x0800 The 802.1ad S-VLAN is the outer VLAN that is configurable on the Configuration > VLAN web page of the BHM. The Q-in-Q EtherType parameter is configured with a default EtherType of 0x88a8 in addition to four alternate EtherTypes that can be configured to aid in interoperability with existing networks that use a different EtherType than the default. Page 7-125 Chapter 7: Configuration Configuring IP and Ethernet interfaces The C-VLAN is the inner VLAN tag, which is the same as 802.1Q. As a top level concept, this operates on the outermost tag at any given time, either pushing a tag on or popping a tag off. This means packets will at most transition from an 802.1Q frame to an 801.ad frame (with a tag pushed on) or an untagged 802.1 frame (with the tag popped off. Similarly, for an 802.1ad frame, this can only transition from an 802.1ad frame to an 802.1Q frame (with the tag popped off) since the radio software only supports 2 levels of tags. VLAN Not Active When VLAN is enabled in the BHM, the Active Configuration block provides the following details as read-only information in this tab. In the Cambium fixed wireless broadband IP network, each device of any type is automatically a permanent member of VID 1. This facilitates deployment of devices that have VLAN enabled with those that do not. Page 7-126 Chapter 7: Configuration VLAN page of BHS The VLAN tab of BHS is explained in Table 100. Table 100 BHS VLAN page attributes Configuring IP and Ethernet interfaces Attribute Meaning VLAN Specify whether VLAN functionality for the BHM and all linked BHS must be (Enabled) or may not (Disabled) be allowed. The default value is Disabled. VLAN Port Type By default this is Q, indicating that it is to operate in the existing manner. The other option is Q-in-Q, which indicates that it must be adding and removing the S-Tag, and adding a C-Tag if necessary for untagged packets. The VLAN Port type corresponds to the Ethernet port of the BHS. Currently, the internal management interfaces will always operate as Q ports. Accept QinQ Frames This option is valid for the Q-in-Q port so that the user may force blocking of existing 802.1ad Q-in-Q frames. This way, only untagged or single tagged packets will come in and out of the Ethernet interface. If a Q-in-Q frame is about ingress or egress the Ethernet interface and this is disabled, it is dropped and a filter entry will show up on the VLAN Statistics page as DVLAN Egress or DVLAN Ingress. Management VID Enter the VID that the BHS must share with the BHM. The range of

(Range 1-4094) values is 1 to 4095. The default value is 1. Default Port VID This is the VID that is used for untagged frames and corresponds to the

(Range 1-4094) Q-Tag for 802.1Q frames (if VLAN Port Type is Q), or the C-Tag for 802.1ad frames (if the VLAN Port Type is Q-in- Q). VLAN Not Active When VLAN is enabled in the BHM, the Active Configuration block provides the following details as read-only information in this tab. In the Cambium fixed wireless broadband IP network, each device of any type is automatically a permanent member of VID 1. This facilitates deployment of devices that have VLAN enabled with those that do not. Page 7-127 Chapter 7: Configuration Configuring IP and Ethernet interfaces PPPoE page of SM Applicable products PMP :

SM Point-to-Point Protocol over Ethernet (PPPoE) is a protocol that encapsulates PPP frames inside Ethernet frames (at Ethernet speeds). Benefits to the network operator may include Access control Service monitoring Generation of statistics about activities of the customer Re-use of infrastructure and operational practices by operators who already use PPP for other networks PPPoE options are configurable for the SM only, and the AP indicates whether or not PPPoE is enabled for a specific subscriber. When PPPoE is enabled, once the RF session comes up between the SM and the AP, the SM will immediately attempt to connect to the PPPoE Server. You can monitor the status of this by viewing the PPPoE Session Log in the Logs section (Administrator only). Every time the RF session comes up, the SM will check the status of the link and if it is down, the SM will attempt to redial the link if necessary depending on the Timer Type. Also, on the Configuration page, the user may Connect or Disconnect the session manually. This can be used to override the session to force a manual disconnect and/or reconnect if there is a problem with the session. In order to enable PPPoE, NAT MUST be enabled on the SM and Translation Bridging MUST be disabled on the AP. These items is strictly enforced for you when you are trying to enable PPPoE. A message will indicate any prerequisites not being met. Also, the NAT Public IP DHCP client cannot be enabled, because the NAT Public IP is received through the IPCP process of the PPPoE discovery stages. The pre-requisites are:

NAT MUST be enabled on the SM o NAT DHCP Client is disabled automatically. The NAT public IP is received from the PPPoE Server. o NAT Public Network Interface Configuration will not be used and must be left to defaults. Also NAT Public IP DHCP is disabled if it is enabled. Translation Bridging MUST be DISABLED on the AP o This will only be determined if the SM is in session since the SM wont know the AP configuration otherwise. If the SM is not in session, PPPoE can be enabled but if the SM goes into session to a Translation Bridge-enabled AP, then PPPoE will not be enabled. The PPPoE configuration parameters are explained in Table 101. Page 7-128 Chapter 7: Configuration Configuring IP and Ethernet interfaces Table 101 SM PPPoE attributes Attribute Meaning Access Concentrator An optional entry to set a specific access concentrator to connect to for the PPPoE session. If this is blank, the SM will accept the first access concentrator which matches the service name (if specified). This is limited to 32 characters. Service Name An optional entry to set a specific service name to connect to for the PPPoE session. If this is left blank the SM will accept the first service option that comes back from the access concentrator specified above, if any. This is limited to 32 characters. Authentication Type None means that no PPPoE authentication is implemented CHAP/PAP means that CHAP authentication is attempted first, then PAP authentication. The same password is used for both types. User Name This is the CHAP/PAP user name that is used if CHAP/PAP authentication is selected. If None is selected for authentication then this field is unused. This is limited to 32 characters. Password This is the CHAP/PAP password that is used if PAP authentication is selected. If None is selected for authentication then this field is unused. This is limited to 32 characters. MTU Use MTU Received from PPPoE Server causes the SM to use the MRU of the PPPoE server received in LCP as the MTU for the PPPoE link. Page 7-129 Chapter 7: Configuration Configuring IP and Ethernet interfaces Use User Defined MTU allows the operator to specify an MTU value to use to override any MTU that may be determined in the LCP phase of PPPoE session setup. If this is selected, the user is able to enter an MTU value up to 1492. However, if the MTU determined in LCP negotiations is less than this user-specified value, the SM will use the smaller value as its MTU for the PPPoE link. Timer Type Keep Alive is the default timer type. This timer will enable a keepalive that will check the status of the link periodically. The user can set a keepalive period. If no data is seen from the PPPoE server for that period, the link is taken down and a reconnection attempt is started. For marginal links, the keep alive timer can be useful so that the session will stay alive over periodic dropouts. The keepalive timer must be set such that the session can outlast any session drop. Some PPPoE servers will have a session check timer of their own so that the timeouts of the server and the SM are in sync, to ensure one side does not drop the session prematurely. Idle Timeout enables an idle timer that checks the usage of the link from the customer side. If there is no data seen from the customer for the idle timeout period, the PPPoE session is dropped. Once data starts flowing from the customer again, the session is started up again. This timer is useful for users who may not be using the connection frequently. If the session is idle for long periods of time, this timer will allow the resources used by the session to be returned to the server. Once the connection is used again by the customer, the link is reestablished automatically. Timer Period The length in seconds of the PPPoE keepalive timer. TCP MSS Clamping If this is enabled, then the SM will alter TCP SYN and SYN-ACK packets by changing the Maximum Segment Size to be compatible with the current MTU of the PPPoE link. This way, the user does not have to worry about MTU on the client side for TCP packets. The MSS is set to the current MTU 40 (20 bytes for IP headers and 20 bytes for TCP headers). This will cause the application on the client side to not send any TCP packets larger than the MTU. If the network is exhibiting large packet loss, try enabling this option. This may not be an option on the PPPoE server itself. The SM will NOT reassemble IP fragments, so if the MTUs are incorrect on the end stations, then MSS clamping will solve the problem for TCP connections. Page 7-130 Chapter 7: Configuration Configuring IP and Ethernet interfaces IP4 and IPv6 Applicable products PMP : AP SM PTP: BHM BMS IPv4 and IPv6 Prioritization PMP/PTP 450 platform provides operators the ability to prioritize IPv6 traffic in addition to IPv4 traffic. IPv6/IPv4 prioritization can be configured by selecting a CodePoint and the corresponding priority from the GUI of the AP/BHM and the IPv6/IPv4 packet is set up accordingly. There is no GUI option for selecting IPv6 or IPv4 priority. Once the priority is set, it is set for IPv4 and IPv6 packets. Configuring IPv4 and IPv6 Priority IPv4 and IPv6 prioritization is set using the DiffServ tab on the AP/BHM and SM/BHS (located at Configuration > DiffServ). A priority set to a specific CodePoint will apply to both IPv4 and IPv6 traffic. Table 102 DiffServ attributes AP/BHM Attribute Meaning CodePoint 1 through Priorities of 0 through 3 map to the low-priority channel; 4 through 7 to CodePoint 47 the high- priority channel. The mappings are the same as 802.1p VLAN CodePoint 49 priorities. Consistent with RFC 2474 through CodePoint CodePoint 0 is predefined to a fixed priority value of 0 (low-priority 55 CodePoint 57 through CodePoint 63 channel). CodePoint 48 is predefined to a fixed priority value of 6 (high-priority channel). CodePoint 56 is predefined to a fixed priority value of 7 (high-

priority channel). Page 7-131 Chapter 7: Configuration Configuring IP and Ethernet interfaces Operator cannot change any of these three fixed priority values. Among the settable parameters, the priority values (and therefore the handling of packets in the high or low priority channel) are set in the AP/BHM for all downlinks within the sector and in the SM/BHS for each uplink. CodePoint Select This represents the CodePoint Selection to be modified via Priority Select Priority Select The priority setting input for the CodePoint selected in CodePoint Select Priority Precedence Allows operator to decide if 802.1p or DiffServ priority bits must be used first when making priority decisions. PPPoE Control Operators may configure the AP/BHM to utilize the high priority channel Message Priority for PPPoE control messages. Configuring the AP/BHM in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the AP/BHM. IPv4 and IPv6 Filtering The operator can filter (block) specified IPv6 protocols including IPv4 and ports from leaving the AP/BHM and SM/BHS and entering the network. This protects the network from both intended and inadvertent packet loading or probing by network users. By keeping the specified protocols or ports off the network, this feature also provides a level of protection to users from each other. Configuring IPv4 and IPv6 Filtering IPv6 filters are set using the Protocol Filtering tab on the AP/BHM and SM/BHS (at Configuration >

Protocol Filtering). Once a filter is set for a packet type, those packets will not be sent over the RF interface depending on Filter Direction setting. Page 7-132 Chapter 7: Configuration Configuring IP and Ethernet interfaces Table 103 Packet Filter Configuration attributes Attribute Meaning Packet Filter Types For any box selected, the Protocol and Port Filtering feature blocks the associated protocol type. To filter packets in any of the user-defined ports, you must do all of the following:

Check the box for User Defined Port n (See Below) in the Packet Filter Types section of this tab. Provide a port number at Port #n. in the User Defined Port Filtering Configuration section of this tab Page 7-133 Chapter 7: Configuration Configuring IP and Ethernet interfaces Enable TCP and/or UDP by clicking the associated radio button Filter Direction Operators may choose to filter upstream (uplink) RF packets or downstream (downlink) RF packets. User Defined Port You can specify ports for which to block subscriber access, regardless of Filtering Configuration whether NAT is enabled. Page 7-134 Chapter 7: Configuration Upgrading the software version and using CNUT Upgrading the software version and using CNUT This section consists of the following procedures:

Checking the installed software version on page 7-135 Upgrading to a new software version on page 7-135 Caution If the link is operational, ensure that the remote end of the link is upgraded first using the wireless connection, and then the local end can be upgraded. Otherwise, the remote end may not be accessible. Use CNUT 4.9.12 or later version and always refer to the software release notes before upgrading system software. The release notes are available at:

https://support.cambiumnetworks.com/files/pmp450 https://support.cambiumnetworks.com/files/ptp450 Checking the installed software version To check the installed software version, follow these instructions:

Procedure 18 Checking the installed software version 1 2 Click on General tab under Home menu. Note the installed Software Version (under Device Information):

PMP/PTP 450/450i 3 Go to the support website (see Contacting Cambium Networks on page 1) and find Point-to-Multipoint software updates. Check that the latest PMP/PTP 450 platform software version is the same as the installed Software Version. 4 To upgrade software to the latest version, see Upgrading to a new software version on page 7-135. Upgrading to a new software version PMP/PTP 450i modules are upgraded using the Canopy Network Updater Tool. The Canopy Network Updater Tool (CNUT) manages and automates the software and firmware upgrade process for a Canopy radio, or CMM4 (but not its 14-port switch) across the network. This eliminates the need for an administrator to visit each radio in the network (or each AP/BHM while using the Autoupdate feature) to upgrade the modules. Page 7-135 Chapter 7: Configuration Upgrading the software version and using CNUT Note Please ensure that you have the most up-to-date version of CNUT by browsing to the Customer Support Web Page located:

http://www.cambiumnetworks.com/support/management-tools/cnut This section includes an example of updating a single unit before deployment. System-wide upgrading procedures may be found in the CNUT Online Help manual, which can be found on the Cambium support website (see Contacting Cambium Networks on page 1). CNUT functions The Canopy Network Updater tool has the following functions:

Automatically discovers all network elements Executes a UDP command that initiates and terminates the Auto-update mode within APs/BHMs. This command is both secure and convenient:

o For security, the AP/BHM accepts this command from only the IP address that you specify in the Configuration page of the AP/BHM. o For convenience, Network Updater automatically sets this Configuration parameter in the APs/BHMs to the IP address of the Network Updater server when the server performs any of the update commands. CNUT supports HTTP and HTTPS Allows you to choose the following among updating:

o Your entire network. o Only elements that you select. o Only network branches that you select. Provides a Script Engine that you can use with any script that:

o You define. o Cambium supplies. Configurability of any of the following to be the file server for image files:

o The AP/BHM, for traditional file serving via UDP commands and monitoring vai UDP messaging o CNUT HTTP/HTTPS Server, for upgrading via SNMP commands and monitoring via SNMP messaging. This also supports an option to either set the image order specifically for this file server or to allow the AP to determine the order. o Local TFTP Server, for traditional file serving via UDP commands and monitoring via UDP messaging. This supports setting the number of simultaneous image transfers per AP/BHM The capability to launch a test of connectivity and operational status of the local HTTP, HTTPS and TFTP file servers An interface that supports efficient specification of the proper IP address for the local file server(s) where Network Updater resides on a multi-homed computer An md5 checksum calculator utility for identifying corruption of downloaded image files before Network Updater is set to apply them. Page 7-136 Chapter 7: Configuration Upgrading the software version and using CNUT Network element groups With the Canopy Network Updater Tool, you can identify element groups composed of network elements that you select. Identifying these element groups does the following:

Organizes the display of elements (for example, by region or by AP/BHM cluster). Allows to:

o Perform an operation on all elements in the group simultaneously. o Set group-level defaults for ftp password access and SNMP Community String (defaults that can be overridden in an individual element when necessary). Network layers A typical network contains multiple layers of elements, with each layer farther from the Point of Presence. For example, SMs (or BHS) are behind an AP/BHM and thus, in this context, at a lower layer than the AP/BHM. Correctly portraying these layers in Network Updater is essential so that Network Updater can perform radio and AP/BHM cluster upgrades in an appropriate order. Script engine Script Engine is the capability in Network Updater that executes any user-defined script against any network element or element group. This capability is useful for network management, especially for scripts that you repetitively execute across your network. The Autodiscovery capability in Network Updater finds all of your network elements. This comprehensive discovery:

Ensures that, when you intend to execute a script against all elements, the script is indeed executed against all elements. Maintains master lists of elements (element groups) against which you selectively execute scripts. The following scripts are included with CNUT:

Gather Customer Support Information Set Access Point Authentication Mode Set Autoupdate Address on APs/BHMs Set SNMP Accessibility Reset Unit Page 7-137 Chapter 7: Configuration Upgrading the software version and using CNUT Software dependencies for CNUT CNUT functionality requires one of the following operating systems o Windows 2000 o Windows Server 2003 o Windows 7 and Windows 8 o Windows XP or XP Professional o Red Hat Enterprise Linux (32-bit) Version 4 or 5 Java Runtime Version 2.0 or later (installed by the CNUT installation tool) CNUT download CNUT can be downloaded together with each system release that supports CNUT. Software for these system releases is available from http://www.cambiumnetworks.com/support/management-

tools/cnut/, as either:

A .zip file for use without the CNUT application. A .pkg file that the CNUT application can open. Upgrading a module prior to deployment To upgrade to a new software version, follow this:

Procedure 19 Upgrading a module prior to deployment 1 Go to the support website (see Contacting Cambium Networks on page 1) and find Point-

to-Multipoint software updates. Download and save the required software image. 2 3 Start CNUT If you dont start up with a blank new network file in CNUT, then open a new network file with the New Network Archive operation (located at File > New Network). 4 Enter a new network element to the empty network tree5-9 using the Add Elements to Network Root operation (located at Edit > Add Elements to Network Root). 5 In the Add Elements dialogue, select a type of Access Point or Subscriber Module and enter the IP address of 169.254.1.1. 6 Make sure that the proper Installation Package is active with the Package Manager dialogue (located at Update > Manage Packages). 7 To verify connectivity with the radio, perform a Refresh, Discover Entire Network operation (located at View > Refresh/Discover Entire Network). You must see the details columns for the new element filled in with ESN and software version information. 8 Initiate the upgrade of the radio using Update Entire Network Root operation (located at Update > Update Entire Network Root). When this operation finishes, the radio is done being upgraded. Page 7-138 Chapter 7: Configuration General configuration General configuration The Configuration > General page of the AP/BMH or BHM/BHS contains many of the configurable parameters that define how the ratios operate in sector or backhaul. Applicable products PMP : AP SM PTP: BHM BMS PMP 450m and PMP/PTP 450i Series General page - PMP 450m AP / PMP 450i AP The General page of AP is explained in Table 104. The General page of PMP 450 SM looks same as PMP 450i AP. Page 7-139 Chapter 7: Configuration General configuration Table 104 General page attributes PMP 450i AP / PMP 450m AP Page 7-140 Chapter 7: Configuration General configuration Attribute Meaning Device Setting Allows the Spectrum Analyzer to be run directly from AP now. Link Speeds From the drop-down list of options, select the type of link speed for the 802.3at Type 2 PoE Status and PoE Classification Ethernet connection. The default for this parameter is that all speeds are selected: Auto 100F/100H/10F/10H. In this setting, the two ends of the link automatically negotiate with each other whether the speed that they will use is 10 Mbps or 100 Mbps and whether the Ethernet traffic is full duplex or half duplex. However,137 Ethernet links work best when either:

both ends are set to the same forced selection both ends are set to auto-negotiate and both have capability in least one common speed and traffic type combination. When the PoE Classification functionality is enabled and if Type 2 power is not present, the PAs do not power up and draw too much power. By default, the PoE Classification feature is disabled and the PAs will power up regardless of the classification presented by the power source. This is supported only on 450i series devices. PoE Classification configuration status also can be check under home >

General > Device Information tab:

Configuration See Setting the Configuration Source on page 7-264. Source Sync Input See Configuring synchronization on page 7-163 Page 7-141 Chapter 7: Configuration General configuration Device Type Standard: The Autosync mechanism will source GPS synchronization from the APs RJ-11 port, the APs power port, or from the device on-

board GPS module. Remote: The Autosync mechanism will source GPS synchronization from the APs RJ-11 port or from the device on-board GPS module. Region From the drop-down list, select the region in which the radio is operating. Country From the drop-down list, select the country in which the radio is operating. Unlike selections in other parameters, your Country selection requires a Save Changes and a Reboot cycle before it will force the context-

sensitive GUI to display related options (for example, Alternate Frequency Carrier 1 and 2 in the Configuration > Radio tab). PMP 450i equipment shipped to the United States is locked to a Region Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. Country Code settings affect the radios in the following ways:

Maximum transmit power limiting (based on radio transmitter power plus configured antenna gain) DFS operation is enabled based on the configured region code, if applicable For more information on how transmit power limiting and DFS is implemented for each country, see the PMP 450 Planning Guide. Webpage Auto Enter the frequency (in seconds) for the web browser to automatically Update refresh the web-based interface. The default setting is 0. The 0 setting causes the web-based interface to never be automatically refreshed. Bridge Entry Specify the appropriate bridge timeout for correct network operation Timeout with the existing network infrastructure. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Caution An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. Translation Bridging Optionally, you can configure the AP to change the source MAC address in every packet it receives from its SMs to the MAC address of the SM that bridged the packet, before forwarding the packet toward the public network. If you do, then:

Not more than 10 IP devices at any time are valid to send data to the AP from behind the SM. Page 7-142 Chapter 7: Configuration General configuration SM populates the Translation Table tab of its Statistics web page, displaying the MAC address and IP address of all the valid connected devices. Each entry in the Translation Table is associated with the number of minutes that have elapsed since the last packet transfer between the connected device and the SM. If 10 are connected and another attempts to connect:

If no Translation Table entry is older than 255 minutes, the attempt is ignored. If an entry is older than 255 minutes, the oldest entry is removed and the attempt is successful. the Send Untranslated ARP parameter in the General tab of the Configuration page can be:

Disabled, so that the AP overwrites the MAC address in Address Resolution Protocol (ARP) packets before forwarding them. Enabled, so that the AP forwards ARP packets regardless of whether it has overwritten the MAC address. When this feature is disabled, the setting of the Send Untranslated ARP parameter has no effect, because all packets are forwarded untranslated

(with the source MAC address intact). Send Untranslated If the Translation Bridging parameter is set to Enabled, then the Send ARP Untranslated ARP parameter can be:

Disabled - so that the AP will overwrite the MAC address in Address Resolution Protocol (ARP) packets before forwarding them. Enabled - so that the AP will forward ARP packets regardless of whether it has overwritten the MAC address. If the Translation Bridging parameter is set to Disabled, then the Send Untranslated ARP parameter has no effect. SM Isolation Prevent or allow SM-to-SM communication by selecting from the following drop-down menu items:

Disable SM Isolation (the default selection). This allows full communication between SMs. Block SM Packets from being forwarded. This prevents both multicast/broadcast and unicast SM-to-SM communication. Block and Forward SM Packets to Backbone. This not only prevents multicast/broadcast and unicast SM-to-SM communication but also sends the packets, which otherwise are handled SM to SM, through the Ethernet port of the AP. Page 7-143 Chapter 7: Configuration General configuration Forward Unknown Enabled: All unknown Unicast packets (no entry in the APs bridge table) Unicast Packets received via the APs Ethernet LAN interface are forwarded to registered SMs. If the target device is situated beneath a particular SM, when the device responds the SM and AP will learn and add the device to their bridge tables so that subsequent packets to that device is bridged to the proper SM. Disabled: All unknown Unicast packets (no entry in the APs bridge table) received via the APs Ethernet LAN interface are discarded at the AP. Update Application Enter the address of the server to access for software updates on this AP Address and registered SMs. Prioritize TCP ACK To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. This parameter, when enabled, can be particularly useful when running bi-direction FTP sessions over the link. If a link is primarily used for video surveillance, it is recommended to set this parameter to Disable. Multicast Destination Using Link Layer Discovery Protocol (LLDP), a module exchanges Address multicast addresses with the device to which it is wired on the Ethernet interface. Although some switches (CMM4, for example) do not pass LLDP addresses upward in the network, a radio can pass it as the value of the Multicast Destination Address parameter value in the connected device that has it populated. DHCP Relay Agent The AP may act as a DHCP relay for SMs and CPEs underneath it. The AP will make use of the DHCP Option 82 (DHCP Relay Agent Information) from RFC 3046 when performing relay functions. The AP offers two types of DHCP relay functionality:

Full Relay Information. Configuring the DHCP Full Relay Operation will take broadcast DHCP packets and send them to a Unicast server in unicast mode. This way the DHCP requests and replies can be routed like any other UDP packet. Only Insert Option 82. This option leaves the DHCP request on its broadcast domain as opposed to DHCP Full Relay Operation which will turn it into a unicast packet. In order to accommodate setting up pools or classes for different VLANs, the Option 82 field will include information to tell the server what VLAN the client is on. DHCP Server (Name The DHCP relay server may be either a DNS name or a static IP address or IP Address) in dotted decimal notation. Additionally the management DNS domain name may be toggled such that the name of the DHCP relay server only needs to be specified and the DNS domain name is automatically appended to that name. The default DHCP relay server addresses is 255.255.255.255 with the appending of the DNS domain name disabled. Page 7-144 Chapter 7: Configuration General configuration Latitude Longitude Height Physical radio location data may be configured via the Latitude, Longitude and Height fields. Latitude and Longitude is measured in Decimal Degree while the Height is calculated in Meters. General page - PMP 450i SM The General page of PMP 450i SM is explained in Table 105. The General page of PMP 450 SM looks same as PMP 450i SM. Table 105 General page attributes PMP 450i SM Page 7-145 Chapter 7: Configuration General configuration Attribute Meaning Link Speeds From the drop-down list of options, select the type of link speed for the 802.3at Type 2 PoE Status and PoE Classification Ethernet connection. The default for this parameter is that all speeds are selected. The recommended setting is a single speed selection for all APs and SMs in the operator network. When the PoE Classification functionality is enabled and if Type 2 power is not present, the PAs do not power up and draw too much power. By default, the PoE Classification feature is disabled and the PAs will power up regardless of the classification presented by the power source. This is supported only on 450i series devices. PoE Classification configuration status also can be check under home >

General > Device Information tab:

Ethernet Link Specify whether to enable or disable Ethernet/802.3 connectivity on the Enable/Disable wired port of the SM. This parameter has no effect on the wireless link. When you select Enable, this feature allows traffic on the Ethernet/802.3 port. This is the factory default state of the port. When you select Disable, this feature prevents traffic on the port. Typical cases of when you may want to select Disable include:

The subscriber is delinquent with payment(s). You suspect that the subscriber is sending or flooding undesired broadcast packets into the network, such as when a virus is present in the subscriber's computing device. the subscriber's home router is improperly configured. Region This parameter allows you to set the region in which the radio will operate. The SM radio automatically inherits the Region type of the master. This behavior ignores the value of the Region parameter in the SM, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-

sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. Country This parameter allows you to set the country in which the radio will operate. The SM radio automatically inherits the Country Code type of the master. This behavior ignores the value of the Country parameter in the SM, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. Page 7-146 Chapter 7: Configuration General configuration PMP/PTP 450i equipment shipped to the United States is locked to a Region Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. Webpage Auto See Table 104 General page attributes PMP 450i AP on page 7-140 Update Bridge Entry Specify the appropriate bridge timeout for correct network operation Timeout with the existing network infrastructure. Timeout occurs when the AP encounters no activity with the SM (whose MAC address is the bridge entry) within the interval that this parameter specifies. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Caution This parameter governs the timeout interval, even if a router in the system has a longer timeout interval. The default value of this field is 25 (minutes). An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. Frame Timing Pulse If this SM extends the sync pulse to a BH master or an AP, select either Gated EnableIf this SM loses sync from the AP, then do not propagate a sync pulse to the BH timing master or other AP. This setting prevents interference in the event that the SM loses sync. DisableIf this SM loses sync from the AP, then propagate the sync pulse to the BH timing master or other AP. Multicast Destination Using Link Layer Discovery Protocol (LLDP), a module exchanges Address multicast addresses with the device to which it is wired on the Ethernet interface. Although some switches (CMM4, for example) do not pass LLDP addresses upward in the network, a radio can pass it as the value of the Multicast Destination Address parameter value in the connected device that has it populated. Coordinates Physical radio location data may be configured via the Latitude, Longitude and Height fields. Page 7-147 Chapter 7: Configuration General configuration General page - PTP 450i BHM The General page of BHM is explained in Table 106. The General page of PTP 450 BHM looks same as PTP 450i BHM. Table 106 General page attributes PTP 450i BHM Page 7-148 Chapter 7: Configuration General configuration Attribute Meaning Timing Mode Allows the user to choose the mode between Timing Master and Timing Slave. Link Speed See Table 104 General page attributes PMP 450i AP on page 7-140 802.3at Type 2 PoE Status and PoE Classification When the PoE Classification functionality is enabled and if Type 2 power is not present, the PAs do not power up and draw too much power. By default, the PoE Classification feature is disabled and the PAs will power up regardless of the classification presented by the power source. This is supported only on 450i series devices. PoE Classification configuration status also can be check under home

> General > Device Information tab:

Sync Input See Configuring synchronization on page 7-163 Region Country Webpage Auto Update Bridge Entry Timeout See Table 104 General page attributes PMP 450i AP on page 7-140 Bridging Functionality Select whether you want bridge table filtering active (Enable) or not

(Disable) on this BH. Disable: allows user to use redundant BHs without causing network addressing problems. Through a spanning tree protocol, this reduces the convergence time from 25 minutes to few seconds. However, you must disable bridge table filtering as only a deliberate part of your overall network design since disabling it allows unwanted traffic across the wireless interface. Enable: Allows user to enable bridge functionality. Note Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. See Table 104 General page attributes PMP 450i AP on page 7-140 Page 7-149 Prioritize TCP ACK Multicast Destination Address Chapter 7: Configuration General configuration Latitude Longitude Height General page - PTP 450i BHS The General page of PTP 450i BHS is explained in Table 107. The General page of PTP 450 BHS looks same as PTP 450i BHS. Table 107 General page attributes PTP 450i BHS Page 7-150 Chapter 7: Configuration General configuration Attribute Meaning Timing Mode Allows the user to choose the mode between Timing Master and Timing Slave. Link Speed From the drop-down list of options, select the type of link speed for the 802.3at Type 2 PoE Status and PoE Classification Ethernet connection. The default for this parameter is that all speeds are selected. The recommended setting is a single speed selection for all BHMs and BHSs in the operator network. When the PoE Classification functionality is enabled and if Type 2 power is not present, the PAs do not power up and draw too much power. By default, the PoE Classification feature is disabled and the PAs will power up regardless of the classification presented by the power source. This is supported only on 450i series devices. PoE Classification configuration status also can be check under home >

General > Device Information tab:

Region This parameter allows you to set the region in which the radio will operate. The BHS radio automatically inherits the Region type of the master. This behavior ignores the value of the Region parameter in the BHS, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-

sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. Country This parameter allows you to set the country in which the radio will operate. The BHS radio automatically inherits the Country Code type of the master. This behavior ignores the value of the Country parameter in the BHS, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. PMP/PTP 450i equipment shipped to the United States is locked to a Region Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. Webpage Auto See Table 104 General page attributes PMP 450i AP on page 7-140 Update Bridge Entry Specify the appropriate bridge timeout for correct network operation Timeout with the existing network infrastructure. Timeout occurs when the BHM encounters no activity with the BHS (whose MAC address is the bridge entry) within the interval that this parameter specifies. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Page 7-151 Chapter 7: Configuration General configuration Caution This parameter governs the timeout interval, even if a router in the system has a longer timeout interval. The default value of this field is 25 (minutes). An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. See Table 104 General page attributes PMP 450i AP on page 7-140 Bridging Functionality Frame Timing Pulse If this BHS extends the sync pulse to a BH master or an BHM, select Gated either EnableIf this BHS loses sync from the BHM, then do not propagate a sync pulse to the BH timing master or other BHM. This setting prevents interference in the event that the BHS loses sync. DisableIf this BHS loses sync from the BHM, then propagate the sync pulse to the BH timing master or other BHM. Multicast Destination See Table 104 General page attributes PMP 450i AP on page 7-140 Address Latitude Longitude Height See Table 104 General page attributes PMP 450i AP on page 7-140 PMP/PTP 450 Series Note Refer Table 104 and Table 105 for PMP 450 AP/SM General page parameters details. Page 7-152 Chapter 7: Configuration General configuration General page - PMP 450 AP Figure 113 General page attributes - PMP 450 AP Page 7-153 Chapter 7: Configuration General configuration General page - PMP 450 SM Figure 114 General page of PMP 450 SM Page 7-154 Chapter 7: Configuration General configuration General page PTP 450 BHM Figure 115 General page of PTP 450 BHM Page 7-155 Chapter 7: Configuration General configuration General page PTP 450 BHS Figure 116 General page of PTP 450 BHS Page 7-156 Chapter 7: Configuration Configuring Unit Settings page Configuring Unit Settings page Applicable products PMP : AP SM PTP: BHM BMS The Unit Settings page of the PMP/PTP 450 platform contains following options:

Unit-Wide Changes Download Configuration File Upload and Apply Configuration File (for AP and BHM) LED Panel Settings (for SM and BHS) Note LED Pannel setting is applicable for SM and BHS only. Upload and Apply Configuration File attributes are not supported for SM and BHS. The PMP/PTP 450 platform also supports import and export of configuration from the AP/BHM/SM/BHS as a text file. The configuration file is in JSON format. The logged in user must be an ADMINISTRATOR in order to export or import the configuration file. The exported configuration file contains the complete configuration including all the default values. To keep a backup of the current configuration, the file can be saved as-is and imported later. The configuration file supports encrypted password. The exported configuration file will contain encrypted password. The import of configuration can have either encrypted or plain text password in Configuration fie. A new tab Encrypt the Password is added under Encrypted Password tab to generate encrypted password for a given password. The Import and Export procedure of configuration file is described in Import and Export of config file on page 7-279. LED Panel Mode has options select Revised mode and Legacy mode. The Legacy mode configures the radio to operate with standard LED behavior. Page 7-157 Chapter 7: Configuration Configuring Unit Settings page Unit Settings page of PMP/PTP 450 platform AP/BHM The Unit Setting page of AP/BHM is explained in Table 108. Table 108 Unit Settings attributes PMP/PTP 450 platform AP/BHM Attribute Meaning Set to Factory Defaults Upon Default Mode Detection If Enabled is checked, then the default mode functions is enabled. When the module is rebooted with Default mode enabled, it can be accessed at the IP address 169.254.1.1 and no password, and all parameter values are reset to defaults. A subscriber, technician, or other person who gains physical access to the module and uses an override cannot see or learn the settings that were previously configured in it. If Disabled is checked, then the default mode functions is disabled. See Radio recovery mode on page 1-22 Caution When Set to Factory Defaults Upon Default Mode is set to Enable, the radio does not select all of the frequencies for Radio Frequency Scan Selection List. It needs to be selected manually. Undo Unit-Wide When you click this button, any changes that you made in any tab but Saved Changes did not commit by a reboot of the module are undone. Page 7-158 Chapter 7: Configuration Configuring Unit Settings page Set to Factory When you click this button, all configurable parameters on all tabs are Defaults reset to the factory settings. Note This can be reverted by selecting "Undo Unit-Wide Saved Changes", before rebooting the radio, though this is not recommended. Password This allows to provide encrypted password for a given password. On click of Encrypt the password button, the Encrypted Password field will display encrypted value of entered plain text password in Password field. Configuration File This allows to download the configuration file of the radio. This configuration file contains the complete configuration including all the default values. The configuration file is highlighted as downloadable link and the naming convention is <mac address of AP>.cfg. Apply Configuration This allows to import and apply configuration to the AP. File Chose File: Select the file to upload the configuration. The configuration file is named as <file name>.cfg. Upload: Import the configuration to the AP. Apply Configuration File: Apply the imported configuration file to the AP. The imported configuration file may either contain a full device configuration or a partial device configuration. If a partial configuration file is imported, only the items contained in the file will be updated, the rest of the device configuration parameters will remain the same. Operators may also include a special flag in the configure file to instruct the device to first revert to factory defaults then to apply the imported configuration. Status of This section shows the results of the upload. Configuration file Page 7-159 Chapter 7: Configuration Configuring Unit Settings page Unit Settings page of PMP/PTP 450i SM/BHS The Unit Settings page of PMP/PTP 450i SM/BHS is explained in Table 109. Table 109 SM Unit Settings attributes Attribute Meaning Set to Factory Defaults Upon Default Plug Detection See Table 108 Unit Settings attributes PMP/PTP 450 platform AP/BHM on page 7-158 LED Panel Settings Legacy Mode configures the radio to operate with standard LED behavior. Undo Unit-Wide Saved Changes Password Set to Factory See Table 108 Unit Settings attributes PMP/PTP 450 platform AP/BHM Defaults on page 7-158 Configuration File Status of Configuration file Page 7-160 Chapter 7: Configuration Setting up time and date Setting up time and date Time page of PMP/PTP 450 platform AP/BHM Applicable products PMP : AP PTP: BHM The Time page of PMP/PTP 450 platform AP/BHM is explained in Table 110. Table 110 PMP/PTP 450 platform AP/BHM Time attributes Attribute Meaning NTP Server (Name The management DNS domain name may be toggled such that the or IP Address) name of the NTP server only needs to be specified and the DNS domain name is automatically appended to that name. NTP Server 1 (Name To have each log in the AP/BHM correlated to a meaningful time and or IP Address) date, either a reliable network element must pass time and date to the NTP Server 2 (Name or IP Address) NTP Server 3 (Name or IP Address) AP/BHM or must set the time and date whenever a power cycle of the AP/BHM has occurred. A network element passes time and date in any of the following scenarios:

A connected CMM4 passes time and date (GPS time and date, if received). A connected CMM4 passes the time and date (GPS time and date, if received), but only if both the CMMr is operating on CMMr Release 2.1 or later release. (These releases include NTP server functionality.) Page 7-161 Chapter 7: Configuration Setting up time and date A separate NTP server (including APs/BHMs receiving NTP data) is addressable from the AP/BHM. If the AP/BHM needs to obtain time and date from a CMM4, or a separate NTP server, enter the IP address or DNS name of the CMM4 or NTP server on this tab. To force the AP/BHM to obtain time and date before the first (or next) 15-minute interval query of the NTP server, click Get Time via NTP. The polling of the NTP servers is done in a sequential fashion, and the polling status of each server is displayed in the NTP Update Log section of the Time Configuration page. An entry of 0.0.0.0 in any of the NTP Server fields indicates an unused server configuration. NTP Server(s) in Use Lists the IP addresses of servers used for NTP retrieval. Time Zone The Time Zone option may be used to offset the received NTP time to match the operators local time zone. When set on the AP/BHM, the offset is set for the entire sector SMs (or BHS) are notified of the current Time Zone upon initial registration). If a Time Zone change is applied, the SMs(or BHS) is notified of the change in a best effort fashion, meaning some SMs//BHSs may not pick up the change until the next re-

registration. Time Zone changes are noted in the Event Log of the AP/BHM and SM/BHS. System Time The current time used by the system. Last NTP Time The last time that the system time was set via NTP. Update Time Date This field may be used to manually set the system time of the radio. This field may be used to manually set the system date of the radio. NTP Update Log This field shows NTP clock update log. It includes NTP clock update Date and Time stamp along with server name. Page 7-162 Chapter 7: Configuration Configuring synchronization Configuring synchronization Applicable products PMP : AP PTP: BHM This section describe synchronization options for PMP and PTP configuration. This Sync Input parameter can be configured under Sync Setting tab of Configure > General page

(see General configuration on page 7-139). PMP/PTP 450i has following sysnchronization options:

AutoSync AutoSync + Free Run Generate Sync Figure 117 Sync Setting configuration AutoSync For PTP, the BHM automatically receives sync from one of the following sources:

GPS Sync over Timing Port (UGPS, co-located AP GPS sync output, or Remote Device feed from a registered SMs GPS sync output) GPS Sync over Power Port (CMM4) Upon AP/BM power on, the AP/BHM does not transmit until a valid synchronization pulse is received from one of the sources above. If there is a loss of GPS synchronization pulse, within two seconds the AP/BHM automatically attempts to source GPS signaling from another source. In case of PMP, when there are synchronization sources on both the timing port and the power port, the power port GPS source is chosen first. If no valid GPS signal is received, the AP/BHM ceases transmission and SM/BHS registration is lost until a valid GPS signal is received again on the AP or BHM. AutoSync + Free Run This mode operates similarly to mode AutoSync, but if a previously received synchronization signal is lost and no GPS signaling alternative is achieved, the AP/BHM automatically changes to synchronization mode Generate Sync. While SM registration ins maintained, in this mode there is no synchronization of APs/BHMs that can hear each other; the AP/BHM will only generate a sync signal for the local AP/BHM and its associated SMs/BHS. Once a valid GPS signal is obtained again, the AP/BHM automatically switches to receiving synchronization via the GPS source and SM/BHS registration is maintained. Page 7-163 Chapter 7: Configuration Configuring synchronization When the Sync Input field is set to Autosync or Autosync + Free Run, other options become available to be set e.g. UGPS Power and other fields. This is true on APs and BHMs. Note In mode AutoSync + Free Run, if a GPS signal is never achieved initially, the system will not switch to Free Run mode, and SMs/BHS will not register to the AP/BHM. A valid GPS signal must be present initially for the AP to switch into Free Run mode

(and to begin self-generating a synchronization pulse). Also, When an AP/BHM is operating in Free Run mode, over a short time it will no longer be synchronized with co-located or nearby APs/BHMs (within radio range). Due to this lack of transmit and receive synchronization across APs/BHMs or across systems, performance while in Free Run mode may be degraded until the APs/BHMs operating in Free Run mode regain a external GPS synchronization source. Careful attention is required to ensure that all systems are properly receiving an external GPS synchronization pulse, and please consider Free Run mode as an emergency option. Generate Sync (factory default) This option may be used when the AP/BHM is not receiving GPS synchronization pulses from either a CMM4 or UGPS module, and there are no other APs/BHMs active within the link range. Using this option will not synchronize transmission of APs/BHMs that can hear each other; it will only generate a sync signal for the local AP/BHM and its associated SMs/BHS. Note When an AP/BHM has its "Regional Code" set to "None", The radio will not provide valid Sync Pulse Information. There is a RED warning that the radio will not transmit, but the user might expect to see a valid sync if the radio is connected to a working CMM4 or UGPS. Page 7-164 Chapter 7: Configuration Configuring security Configuring security Perform this task to configure the PMP/PTP 450 platform system in accordance with the network operators security policy. Choose from the following procedures:

Managing module access by password on page 7-166: to configure the unit access password and access level Isolating from the internet on page 7-169: to ensure that APs are properly secured from external networks Encrypting radio transmissions on page 7-169: to configure the unit to operate with AES or DES wireless link security Requiring SM Authentication on page 7-170: to set up the AP to require SMs to authenticate via the AP, WM, or RADIUS server Filtering protocols and ports on page 7-171: to filter (block) specified protocols and ports from leaving the system Encrypting downlink broadcasts on page 7-174: to encrypt downlink broadcast transmissions Isolating SMs on page 7-174: to prevent SMs in the same sector from directly communicating with each other Filtering management through Ethernet on page 7-175: to prevent management access to the SM via the radios Ethernet port Allowing management only from specified IP addresses on page 7-175: to only allow radio management interface access from specified IP addresses Restricting radio Telnet access over the RF interface on page 7-175: to restrict Telnet access to the AP Configuring SNMP Access on page 7-178 Configuring Security on page 7-180 Page 7-165 Chapter 7: Configuration Configuring security Managing module access by password Applicable products PMP : AP SM PTP: BHM BMS See Managing module access by passwords on page 3-37. Adding a User for Access to a module The Account > Add User page allows to create a new user for accessing PMP/PTP 450 platform AP/SM/BHM/BHS. The Add User page is explained in Table 111. Table 111 Add User page of account page - AP/ SM/BH Attribute Meaning User Name User Account name. Level Select appropriate level for new account. It can be INSTALLER, ADMINISTRATOR or TECHNICIAN. See Managing module access by passwords on page 3-37. New Password Assign the password for new user account Confirm Password This new password must be confirmed in the Confirm Password field. User Mode User Mode is used to create an account which are mainly used for viewing the configurations. The local and remote Read-Only user account can be created by Admin, Installer or Tech logins. To create a Read-Only user, the read-only check box needs to be checked. Note The Read-Only user cannot perform any service impacting operations like creating read-only accounts, editing and viewing read-only user accounts, changes in login page, read-only user login, Telnet access, SNMP, RADIUS and upgrade/downgrade. Page 7-166 Chapter 7: Configuration Configuring security Deleting a User from Access to a module The Account > Delete User page provides a drop down list of configured users from which to select the user you want to delete. The Delele User page is explained in Table 112. Table 112 Delete User page - PMP/PTP 450 platform AP/ SM/BH Attribute Meaning User Select a user from drop down list which has to be deleted and click Delete button. Accounts that cannot be deleted are the current user's own account. the last remaining account of ADMINISTRATOR level. Changing a User Setting The Account > Change User Setting page allows to update password, mode update and general status permission for a user. From the factory default state, configure passwords for both the root and admin account at the ADMINISTRATOR permission level, using Update Password tab of Change Users Setting page. The Change User Setting page is explained in Table 113. Table 113 Change User Setting page - PMP/PTP 450 platform AP/ SM/BH Page 7-167 Chapter 7: Configuration Configuring security Attribute Meaning Update Password This tab provides a drop down list of configured users from which a user tab is selected to change password. Update Mode tab This tab facilitates to convert a configured user to a Read-Only user. General Status This tab enables and disables visibility of General Status Page for all Permission tab Guest user. To display of Radio data on SMs/BHS main Login page for Guest login, it can be enabled or disabled in Security tab of Configuration page. Figure 118 AP Evaluation Configuration parameter of Security tab for PMP Figure 119 BHM Evaluation Configuration parameter of Security tab for PTP Users account The Account > Users page allows to view all configured users account for accessing the module. The Users page is explained in Table 114. Table 114 User page PMP/PTP 450 platform AP/SM/BH Attribute Meaning Username User access account name Permission Permission of configured user INSTALLER, ADMINISTRATOR or TECHNICIAN Mode This field indicate access mode of user Read-Write or Read-Only. Page 7-168 Chapter 7: Configuration Configuring security Overriding Forgotten IP Addresses or Passwords on AP and SM See Radio recovery mode on page 1-22 Isolating from the internet APs/BHMs Applicable products PMP : AP PTP: BHM See Isolating AP/BHM from the Internet on page 3-35. Encrypting radio transmissions Applicable products PMP : AP SM PTP: BHM BMS See Encrypting radio transmissions on page 3-35. Page 7-169 Chapter 7: Configuration Configuring security Requiring SM Authentication Applicable products PMP : AP SM Through the use of a shared AP key, or an external RADIUS (Remote Authentication Dial In User Service) server, it enhances network security by requiring SMs to authenticate when they register. For descriptions of each of the configurable security parameters on the AP, see Configuring Security on page 7-180. For descriptions of each of the configurable security parameters on the SM, see Security on page 7-185. Operators may use the APs Authentication Mode field to select from among the following authentication modes:

Disabledthe AP requires no SMs to authenticate (factory default setting). Authentication Server the AP requires any SM that attempts registration to be authenticated in Wireless Manager before registration AP PreShared Key - The AP acts as the authentication server to its SMs and will make use of a user-configurable pre-shared authentication key. The operator enters this key on both the AP and all SMs desired to register to that AP. There is also an option of leaving the AP and SMs at their default setting of using the Default Key. Due to the nature of the authentication operation, if you want to set a specific authentication key, then you MUST configure the key on all of the SMs and reboot them BEFORE enabling the key and option on the AP. Otherwise, if you configure the AP first, none of the SMs is able to register. RADIUS AAA - When RADIUS AAA is selected, up to 3 Authentication Server (RADIUS Server) IP addresses and Shared Secrets can be configured. The IP address(s) configured here must match the IP address(s) of the RADIUS server(s). The shared secret(s) configured here must match the shared secret(s) configured in the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not for splitting the database. If Server 1 doesnt respond, Server 2 is tried, and then server 3. If Server 1 rejects authentication, the SM is denied entry to the network, and does not progress trying the other servers. For more information on configuring the PMP 450 network to utilize a RADIUS server, see Configuring a RADIUS server on page 7-281. Page 7-170 Chapter 7: Configuration Configuring security Filtering protocols and ports Applicable products PMP : AP SM PTP: BHM BMS The filtering protocols and ports allows to configure filters for specified protocols and ports from leaving the AP/SM/BHM/BHS and entering the network. See Filtering protocols and ports on page 3-38. Protocol filtering page of PMP/PTP 450 platform AP/BHM The Protocol Filtering page of PMP/PTP 450 platform AP/BHM is explained in Table 115. Table 115 AP/BHM Protocol Filtering attributes Page 7-171 Chapter 7: Configuration Configuring security Attribute Meaning Packet Filter Types For any box selected, the Protocol and Port Filtering feature blocks the associated protocol type. To filter packets in any of the user-defined ports, must do all of the following:

Check the box for User Defined Port n (See Below) in the Packet Filter Types section of this tab. In the User Defined Port Filtering Configuration section of this tab:

provide a port number at Port #n. enable TCP and/or UDP by clicking the associated radio button Filter Direction Operators may choose to filter upstream (uplink) RF packets or downstream (downlink) RF packets. User Defined Port You can specify ports for which to block subscriber access, regardless of Filtering Configuration whether NAT is enabled. RF Telnet Access RF Telnet Access restricts Telnet access to the AP/BHM from a device PPPoE PADI Downlink Forwarding situated below a network SM/BHS (downstream from the AP/BHM). This is a security enhancement to restrict RF-interface sourced AP access specifically to the LAN1 IP address and LAN2 IP address (Radio Private Address, typically 192.168.101.[LUID]). This restriction disallows unauthorized users from running Telnet commands on the AP/BHM that can change AP/BHM configuration or modifying network-critical components such as routing and ARP tables. Enabled: the AP/BHM allows downstream and upstream transmission of PPPoE PADI packets. By default, PPPoE PADI Downlink Forwarding is set to Enabled. Disabled: the AP/BHM disallows PPPoE PADI packets from entering the Ethernet interface and exiting the RF interface (downstream to the SM/BHS). PPPoE PADI packets are still allowed to enter the APs RF interface and exit the APs /BHMs Ethernet interface (upstream). Page 7-172 Chapter 7: Configuration Configuring security Protocol filtering page of SM/BHS The Protocol Filtering page of SM/BHS is explained in Table 116. Table 116 SM/BHS Protocol Filtering attributes Attribute Meaning Packet Filter See Table 115 AP/BHM Protocol Filtering attributes on page 7-171 Configuration tab User Defined Port See Table 115 AP/BHM Protocol Filtering attributes on page 7-171 Filtering Configuration tab Page 7-173 Chapter 7: Configuration Port configuration Configuring security PMP/PTP 450 platform devices support access to various communication protocols and only the ports required for these protocols are available for access by external entities. Operators may change the port numbers for these protocols via the radio GUI or SNMP. The Port Configuration page of the AP/SM/BHM/BHS is explained in Table 117. Table 117 Port Configuration attributes AP/SM/BHM/BMS Attribute FTP Port Meaning The listen port on the device used for FTP communication. HTTP Port The listen port on the device used for HTTP communication. HTTPS Port The listen port on the device used for HTTPS communication Radius Port The destination port used by the device for RADIUS communication. Radius Accounting The destination port used by the device for RADIUS accounting Port communication. SNMP Port The listen port on the device used for SNMP communication. SNMP Trap Port The destination port used by the device to which SNMP traps are sent. Syslog Server Port The destination port used by the device to which Syslog messaging is sent. Encrypting downlink broadcasts See Encrypting downlink broadcasts on page 3-42. Isolating SMs See Isolating SMs in PMP on page 3-42. Page 7-174 Chapter 7: Configuration Configuring security Filtering management through Ethernet See Filtering management through Ethernet on page 3-42. Allowing management only from specified IP addresses See Allowing management from only specified IP addresses on page 3-43. Restricting radio Telnet access over the RF interface RF Telnet Access restricts Telnet access to the AP from a device situated below a network SM

(downstream from the AP). This is a security enhancement to restrict RF-interface sourced AP access specifically to the LAN1 IP address and LAN2 IP address (Radio Private Address, typically 192.168.101. [LUID]). This restriction disallows unauthorized users from running Telnet commands on the AP that can change AP configuration or modifying network-critical components such as routing and ARP tables. The RF Telnet Access may be configured via the AP GUI or via SNMP commands, and RF Telnet Access is set to Enabled by default. Once RF Telnet Access is set to Disabled, if there is a Telnet session attempt to the AP originating from a device situated below the SM (or any downstream device), the attempt is dropped. This also includes Telnet session attempts originated from the SMs management interface (if a user has initiated a Telnet session to a SM and attempts to Telnet from the SM to the AP). In addition, if there are any active Telnet connections to the AP originating from a device situated below the SM (or any downstream device), the connection is dropped. This behavior must be considered if system administrators use Telnet downstream from an AP (from a registered SM) to modify system parameters. Setting RF Telnet Access to Disabled does not affect devices situated above the AP from accessing the AP via Telnet, including servers running the CNUT (Canopy Network Updater tool) application. Also, setting RF Telnet Access to Disabled does not affect any Telnet access into upstream devices (situated above or adjacent to the AP) through the AP (see Figure 120). The figure below depicts a user attempting two telnet sessions. One is targeted for the AP (orange) and one is targeted for the network upstream from the AP (green). If RF Telnet Access is set to Disabled (factory default setting), the Telnet attempt from the user to the AP is blocked, but the attempt from the user to Network is allowed to pass through the Cambium network. Figure 120 RF Telnet Access Restrictions (orange) and Flow through (green) Page 7-175 Chapter 7: Configuration Configuring security Key Security Considerations when using the RF Telnet Access Feature To ensure that the network is fully protected from unauthorized AP Telnet sessions, the following topics must be considered:

Securing AP Clusters When working with a cluster of AP units, to eliminate potential security holes allowing Telnet access, ensure that the RF Telnet Access parameter is set to Disabled for every AP in the cluster. In addition, since users situated below the AP are able to pass Telnet sessions up through the SM and AP to the upstream network (while AP RF Telnet Access is set to Disabled), ensure that all CMM4 or other networking equipment is secured with strong passwords. Otherwise, users may Telnet to the CMM4 or other networking equipment, and subsequently access network APs (see Figure 121) via their Ethernet interfaces (since RF Telnet Access only prevents Telnet sessions originating from the APs wireless interface). Figure 121 RF Telnet Access Restriction (orange) and Potential Security Hole (green) As a common practice, AP administrator usernames and passwords must be secured with strong, non-default passwords. Restricting AP RF Telnet Access AP Telnet access via the RF interface may be configured in two ways the AP GUI and SNMP. Controlling RF Telnet Access via the AP GUI To restrict all Telnet access to the AP via the RF interface from downstream devices, follow these instructions using the AP GUI:

Procedure 20 Restricting RF Telnet access 1 Log into the AP GUI using administrator credentials 2 On the AP GUI, navigate to Configuration > Protocol Filtering Page 7-176 Chapter 7: Configuration Configuring security 3 Under GUI heading Telnet Access over RF Interface, set RF Telnet Access to Disabled 4 Click the Save button 5 Once the Save button is clicked, all RF Telnet Access to the AP from devices situated below the AP is blocked. Note The factory detafult setting for RF Telnet Access is disabled and PPPoE PADI Downlink Forwarding is enabled. Page 7-177 Chapter 7: Configuration Configuring security Configuring SNMP Access The SNMPv3 interface provides a more secure method to perform SNMP operations. This standard provides services for authentication, data integrity and message encryption over SNMP. Refer to Planning for SNMPv3 operation on page 3-36 for details. Note The factory detafult setting for SNMP is SNMPv2c Only. Procedure 21 Configuring SNMPv3 1 Log into the AP GUI using administrator credentials 2 On the AP/SM GUI, navigate to Configuration > Security Page 3 Under GUI heading Security Mode, set SNMP to SNMPv3 Only 4 Click the Save Changes button 5 Go to Configuration > SNMP Page 6 Under GUI heading SNMPv3 setting, set Engine ID, SNMPv3 Security Level, SNMPv3 Authentication Protocol, SNMPv3 Privacy Protocol, SNMPv3 Read-Only User, SNMPv3 Read/Write User, SNMPv3 Trap Configuration parameters:

Engine ID :

Each radio (AP/SM/BHM/BHS) has a distinct SNMP authoritative engine identified by a unique Engine ID. While the Engine ID is configurable to the operator it is expected that the operator follow the guidelines of the SNMPEngineID defined in the SNMP-

FRAMEWORK-MIB (RFC 3411). The default Engine ID is the MAC address of the device. SNMPv3 security level, Authentication and Privacy Protocol The authentication allows authentication of SNMPv3 user and privacy allows for encryption of SNMPv3 message. PMP/PTP 450 platform supports MD5 authentication and CBC-DES privacy protocols. Page 7-178 Chapter 7: Configuration Configuring security SNMPv3 Read-Only and Read/Write User The user can defined by configurable attributes. The attributes and default values are:

Read-only user o Username = Canopyro o Authentication Password = authCanopyro o Privacy Password = privacyCanopyro Read-write user (by default read-write user is disabled) o Username = Canopy o Authentication Password = authCanopy o Privacy Password = privacyCanopy SNMPv3 Trap Configuration The traps may be sent from radios in SNMPv3 format based on parameter settings. It can be configured for Disabled, Enabled for Read-Only User, Enable for Read/Write User. Page 7-179 Chapter 7: Configuration Configuring Security Configuring security Applicable products PMP : AP SM PTP: BHM BMS Security page PMP/PTP 450 platform AP/BHM The security page of AP/BHM is explained in Table 118. Table 118 Security tab of the AP Page 7-180 Chapter 7: Configuration Configuring security Attribute Meaning Authentication Mode Operators may use this field to select from among the following authentication modes:

Disabledthe AP/BHM requires no SMs/BHS to authenticate. (Factory default). Authentication Server the AP/BHM requires any SM/BHS that attempts registration to be authenticated in Wireless Manager before registration. AP PreShared Key - The AP/BHM acts as the authentication server to its SMs/BHS and will make use of a user-configurable pre-shared authentication key. The operator enters this key on both the AP/BHM and all SMs/BHS desired to register to that AP/BHM. There is also an option of leaving the AP/BHM and SMs/BHS at their default setting of using the Default Key. Due to the nature of the authentication operation, if you want to set a specific authentication key, then you MUST configure the key on all of the SMs/BHS and reboot them BEFORE enabling the key and option on the AP/BHM. Otherwise, if you configure the AP/BHM first, none of the SMs/BHS is able to register. RADIUS AAA - When RADIUS AAA is selected, up to 3 Authentication Server (RADIUS Server) IP addresses and Shared Secrets can be configured. The IP address(s) configured here must match the IP address(s) of the RADIUS server(s). The shared secret(s) configured here must match the shared secret(s) configured in the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not for splitting the database. If Server 1 doesnt respond, Server 2 is tried, and then server 3. If Server 1 rejects authentication, the SM is denied entry to the network, and does not progress trying the other servers. Note This parameter is applicable to BHM. Page 7-181 Chapter 7: Configuration Configuring security Authentication The management DNS domain name may be toggled such that the Server DNS Usage name of the authentication server only needs to be specified and the DNS domain name is automatically appended to that name. Note This parameter is applicable to BHM. Authentication Enter the IP address or server name of the authentication server Server 1 to 5

(RADIUS or WM) and the Shared Secret configured in the authentication server. When Authentication Mode RADIUS AAA is selected, the default value of Shared Secret is CanopySharedSecret. The Shared Secret may consist of up to 32 ASCII characters. Note This parameter is applicable to BHM. Radius Port This field allows the operator to configure a custom port for RADIUS server communication. The default value is 1812. Note This parameter is applicable to BHM. Authentication Key The authentication key is a 32-character hexadecimal string used when Authentication Mode is set to AP PreShared Key. By default, this key is set to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF. Note This parameter is applicable to BHM. Select Key This option allows operators to choose which authentication key is used:

Use Key above means that the key specified in Authentication Key is used for authentication Use Default Key means that a default key (based off of the SMs MAC address) is used for authentication Note This parameter is applicable to BHM. Dyanamic Authorization Extensions for RADIUS Enable CoA and Disconnect Message: Allows to control configuration parameters of SM using RADIUS CoA and Disconnect Message feature. Disable CoA and Disconnect Message: Disables RADIUS CoA and Disconnect Message feature. To enable CoA and Disconnect feature, the Authentication Mode should be set to RADIUS AAA. Bypass Enabled: SM authentication is disabled when SM connects via ICC Authentication for

(Installation Color Code). ICC SMs Disabled: SM authentication is enabled. Encryption Setting Specify the type of airlink security to apply to this AP. The encryption setting must match the encryption setting of the SMs. Page 7-182 Chapter 7: Configuration Configuring security None provides no encryption on the air link. DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. Note This parameter is applicable to BHM. SM Display of AP Allows operators to suppress the display of data about this AP/BHM on Evaluation Data the AP/BHM Evaluation tab of the Tools page in all SMs/BHS that Or BHS Display of BHM register. The factory default setting for SM Display of AP Evaluation Data or BHS Display of BHM Evaluation Data is enabled display. Evaluation Data PMP 450/450i SM display of AP Evaluation Data parameter PTP 450/450i BHS display of BHM Evaluation Data parameter Web, Telnet, FTP Enter the expiry in seconds for remote management sessions via HTTP, Session Timeout telnet, or ftp access to the AP/BHM. IP Access Control You can permit access to the AP/BHM from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address Allowed Source IP 1 If you selected IP Access Filtering Enabled for the IP Access Control to 3 parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the AP from any IP address. You may populate as many as all three. If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. Page 7-183 Chapter 7: Configuration Configuring security Web Access The Radio supports secured and non-secured web access protocols. Select suitable web access from drop down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. SNMP This option allows to configure SNMP agent communication version. It can be selected from drop down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is a secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. Telnet FTP TFTP This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. Page 7-184 Chapter 7: Configuration Configuring security Security page - PMP 450 platform SM The security page of PMP 450 platform SM is explained in Table 119. Table 119 Security attributes PMP 450 platform SM Page 7-185 Chapter 7: Configuration Configuring security Attribute Meaning Authentication Key Only if the AP to which this SM will register requires authentication, specify the key that the SM will use when authenticating. For alpha characters in this hex key, use only upper case. Select Key The Use Default Key selection specifies the predetermined key for authentication in Wireless Manager The Use Key above selection specifies the 32-digit hexadecimal key that is permanently stored on both the SM and the WM Enforce The SM may enforce authentication types of AAA and AP Pre-

Authentication sharedKey. The SM will not finish the registration process if the AP is not using the configured authentication method (and the SM locks out the AP for 15 minutes). Phase 1 The protocols supported for the Phase 1 (Outside Identity) phase of authentication are EAPTTLS (Extensible Authentication Protocol Tunneled Transport Layer Security) or MSCHAPv2 (Microsoft Challenge-Handshake Authentication Protocol version 2). Page 7-186 Chapter 7: Configuration Configuring security Phase 2 Select the desired Phase 2 (Inside Identity) authentication protocol from the Phase 2 options of PAP (Password Authentication Protocol), CHAP

(Challenge Handshake Authentication Protocol), and MSCHAP

(Microsofts version of CHAP, version 2 is used). The protocol must be consistent with the authentication protocol configured on the RADIUS server. Identity/Realm If Realms are being used, select Enable Realm and configure an outer identity in the Identity field and a Realm in the Realm field. These must match the Phase 1/Outer Identity and Realm configured in the RADIUS server. The default Identity is anonymous. The Identity can be up to 128 non-special (no diacritical markings) alphanumeric characters. The default Realm is canopy.net. The Realm can also be up to 128 non-

special alphanumeric characters. Configure an outer Identity in the Username field. This must match the Phase 1/Outer Identity username configured in the RADIUS server. The default Phase 1/Outer Identity Username is anonymous. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. Username Enter a Username for the SM. This must match the username configured for the SM on the RADIUS server. The default Username is the SMs MAC address. The Username can be up to 128 non-special

(no diacritical markings) alphanumeric characters. Password Enter the desired password for the SM in the Password and Confirm Password fields. The Password must match the password configured for the SM on the RADIUS server. The default Password is password. The Password can be up to 128 non-special (no diacritical markings) alphanumeric characters Upload Certificate To upload a certificate manually to a SM, first load it in a known place File on your PC or network drive, then click on a Delete button on one of the Certificate description blocks to delete a certificate to provide space for your certificate. Click on Choose File, browse to the location of the certificate, and click the Import Certificate button, and then reboot the radio to use the new certificate. When a certificate is in use, after the SM successfully registers to an AP, an indication of In Use will appear in the description block of the certificate being used. The public certificates installed on the SMs are used with the private certificate on the RADIUS server to provide a public/private key encryption system. Up to 2 certificates can be resident on a SM. An installed certificate can be deleted by clicking the Delete button in the certificates description block on the Configuration > Security tab. To restore the 2 default certificates, click the Use Default Certificates button in the RADIUS Certificate Settings parameter block and reboot the radio. Page 7-187 Chapter 7: Configuration Configuring security Encryption Setting Specify the type of airlink security to apply to this SM. The encryption setting must match the encryption setting of the AP. None provides no encryption on the air link. DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. Web, Telnet, FTP Enter the expiry in seconds for remote management sessions via HTTP, Session Timeout telnet, or FTP access to the SM. Ethernet Access If you want to prevent any device that is connected to the Ethernet port of the SM from accessing the management interface of the SM, select Ethernet Access Disabled. This selection disables access through this port to via HTTP (the GUI), SNMP, telnet, FTP, and TFTP. With this selection, management access is available through only the RF interface via either an IP address (if Network Accessibility is set to Public on the SM) or the Session Status or Remote Subscribers tab of the AP. Note This setting does not prevent a device connected to the Ethernet port from accessing the management interface of other SMs in the network. To prevent this, use the IP Access Filtering Enabled selection in the IP Access Control parameter of the SMs in the network. See IP Access Control below. If you want to allow management access through the Ethernet port, select Ethernet Access Enabled. This is the factory default setting for this parameter. IP Access Control You can permit access to the SM from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address Allowed Source IP 1 If you selected IP Access Filtering Enabled for the IP Access Control to 3 parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the SM from any IP address. You may populate as many as all three. Page 7-188 Chapter 7: Configuration Configuring security If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. A subnet mask may be defined for each entry to allow for filtering control based on a range of IP addresses. Web Access The Radio supports secured and non-secured web access protocols. Select suitable web access from drop down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. SNMP This option allows to configure SNMP agent communication version. It can be selected from drop down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. Telnet FTP TFTP This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. Site Name Specify a string to associate with the physical module. Site Contact Enter contact information for the module administrator. Site Location Enter information about the physical location of the module. Enable Security Enable: The Security Banner Notice will be displayed before login. Banner during Login Disable: The Security Banner Notice will not be displayed before login. Security Banner User can enter ASCII (0-9a-zA-Z newline, line-feed are allowed) text up-to Notice 1300 characters. User must accept Enable: login area (username and password) will be disabled unless user security banner accepts the security banner. before login Disable: User cant login to radio without accepting security banner. Page 7-189 Chapter 7: Configuration Configuring security Security page PTP 450/450i BHS The Security page of PTP 450/450i BHS is explained in Table 120. Table 120 Security attributes for PTP 450/450i BHS Attribute Meaning Authentication Key Only if the BHM to which this BHS registers requires an authentication, specify the key that the BHS will use when authenticating. For alpha characters in this hex key, use only upper case. Encryption Setting Specify the type of airlink security to apply to this BHS. The encryption setting must match the encryption setting of the BHM. None provides no encryption on the air link. DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. It is factory default setting. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. Page 7-190 Chapter 7: Configuration Configuring security Web, Telnet, FTP Enter the expiry in seconds for remote management sessions via HTTP, Session Timeout telnet, or FTP access to the BHS. IP Access Control You can permit access to the BHS from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address Allowed Source IP 1 If you selected IP Access Filtering Enabled for the IP Access Control to 3 parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the BHS from any IP address. You may populate as many as all three. If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. A subnet mask may be defined for each entry to allow for filtering control based on a range of IP addresses. Web Access The Radio supports secured and non-secured web access protocols. Select suitable web access from drop down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. SNMP This option allows to configure SNMP agent communication version. It can be selected from drop down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. Telnet FTP TFTP Page 7-191 Chapter 7: Configuration Configuring radio parameters Configuring radio parameters PMP 450m Configurating radio on page 7-193 PMP/PTP 450i Configurating radio on page 7-193 PMP/PTP 450 Configurating radio on page 7-217 Custom Frequencies page on page 7-234 DFS for 5 GHz Radios on page 7-237 MIMO-A mode of operation on page 7-239 Improved PPS performance of PMP 450 and 450i SMs on page 7-241 Page 7-192 Chapter 7: Configuration Configuring radio parameters PMP 450m Configurating radio Radio page - PMP 450m AP 5 GHz The Radio tab of the PMP 450m AP contains some of the configurable parameters that define how an AP operates. Note Only the frequencies available for your region and the selected Channel bandwidth are displayed. Table 121 PMP 450m AP Radio attributes - 5 GHz Page 7-193 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Frequency Band Select the desired operating frequency band. Frequency Carrier Specify the frequency for the module to transmit. The default for this parameter is None. For a list of channels in the band, see the drop-down list on the radio GUI. Alternate Frequency These parameters are displayed based on Regional Settings. Refer Carrier 1 and 2 Country on page 7-142 Channel Bandwidth The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the AP and the SM. The supported Channel Bandwidths are 5, 10 and 20 MHz. Cyclic Prefix OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol to allow multi-

pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. Color Code Specify a value from 0 to 254. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Subscriber Color This timer may be utilized to initiate SM rescans in order to register to an Code Rescan (When AP configured with the SMs primary color code. not on a Primary Color Code) Page 7-194 Chapter 7: Configuration Configuring radio parameters The time (in minutes) for a subscriber to rescan (if this AP is not configured with the SMs primary color code). This timer will only fire once if the Subscriber Color Code Wait Period for Idle timer is configured with a nonzero value and the Subscriber Color Code Rescan expires, the Subscriber Color Code Wait Period for Idle is started. If the Subscriber Color Code Wait Period for Idle timer is configured with a zero value and the Subscriber Color Code Rescan timer expires, the SM will immediately go into rescan mode Subscriber Color The time (in minutes) for a subscriber to rescan while idle (if this AP is Code Wait Period for not configured with the SMs primary color code). This timer will fire Idle periodic events. The fired event determines if any RF unicast traffic

(either inbound or outbound) has occurred since the last event. If the results of the event determine that no RF unicast traffic has occurred

(SM is idle), then the subscriber will rescan. Installation Color With this feature enabled on the AP and SM, operators may install and Code remotely configure SMs without having to configure matching color codes between the modules. While the SM is accessible for configuration from above the AP (for remote provisioning) and below the SM (for local site provisioning), no user data is passed over the radio link. When using the Installation Color Code feature, ensure that the SM is configured with the factory default Color Code configuration (Color Code 1 is 0, Color Code 2-10 set to 0 and Disable). The status of the Installation Color Code can be viewed on the AP Eval web GUI page, and when the SM is registered using the Installation Color Code the message SM is registered via ICC Bridging Disabled! is displayed in red on every SM GUI page. The Installation Color Code parameter is configurable without a radio reboot for both the AP and SM. If a SM is registered via Installation Color Code and the feature is then disabled, operators will need to reboot the SM or force it to reregister (i.e. using Rescan APs functionality on the AP Eval page). Max Range Enter a number of miles (or kilometers divided by 1.61, then rounded to an integer) for the furthest distance from which a SM is allowed to register to this AP. Do not set the distance to any greater number of miles. A greater distance does not increase the power of transmission from the AP. can reduce aggregate throughput. Regardless of this distance, the SM must meet the minimum requirements for an acceptable link. If the AP is in cluster, then you must set this parameter on all other APs in the cluster exactly the same, except as described in the NOTE admonition below. The default value of this parameter is 2 miles (3.2 km). Page 7-195 Chapter 7: Configuration Configuring radio parameters Downlink Data Specify the percentage of the aggregate throughput for the downlink

(frames transmitted from the AP to the subscriber). For example, if the aggregate (uplink and downlink total) throughput on the AP is 90 Mb, then 75% specified for this parameter allocates 67.5 Mb for the downlink and 22.5 Mb for the uplink. The default for this parameter is 75%. This parameter must be set in the range of 15% - 85%, otherwise the invalid input will not be accepted and the previously-entered valid setting is used. Note This setting does not prevent a device connected to the Ethernet port from accessing the management interface of other SMs in the network. To prevent this, use the IP Access Filtering Enabled selection in the IP Access Control parameter of the SMs in the network. See IP Access Control below. Contention Slots This field indicates the number of (reserved) Contention slots configured

(a.k.a. Control Slots) by the operator. The SM uses reserved Contention slots and unused data slots for bandwidth requests. See Contention slots on page7-238. Broadcast Repeat The default is 2 repeats (in addition to the original broadcast packet, for Count a total of 3 packets sent for every one needed), and is settable to 1 or 0 repeats (2 or 1 packets for every broadcast). ARQ (Automatic Repeat reQuest) is not present in downlink broadcast packets, since it can cause unnecessary uplink traffic from every SM for each broadcast packet. For successful transport without ARQ, the AP repeats downlink broadcast packets. The SMs filter out all repeated broadcast packets and, thus, do not transport further. The default of 2 repeats is optimum for typical uses of the network as an internet access system. In applications with heavy download broadcast such as video distribution, overall throughput is significantly improved by setting the repeat count to 1 or 0. This avoids flooding the downlink with repeat broadcast packets. Transmitter Output This value represents the combined power of the APs two transmitters. Power Nations and regions may regulate transmitter output power. For example 900 MHz, 5.4 GHz and 5.8 GHz modules are available as connectorized radios, which require the operator to adjust power to ensure regulatory compliance. The professional installer of the equipment has the responsibility to maintain awareness of applicable regulations. calculate the permissible transmitter output power for the module. confirm that the initial power setting is compliant with national or regional regulations. Page 7-196 Chapter 7: Configuration Configuring radio parameters confirm that the power setting is compliant following any reset of the module to factory defaults. External Gain This value needs to correspond to the published gain of the antenna used to ensure the radio will meet regulatory requirements. SM Receive Target Each SMs Transmitter Output Power is automatically set by the AP. The Level AP monitors the received power from each SM, and adjusts each SMs Transmitter Output Power so that the received power at the AP from that SM is not greater what is set in this field. This value represents the transmitted and received power (combined power) perceived on the SM. Multicast VC Data This pull down menu of the Multicast Data Control screen helps in Rate configuring multicast packets to be transmitted over a dedicated channel at a configurable rate of 1X, 2X, 4X or 6X. The default value is Disable. If set to the default value, all multicast packets are transmitted over the Broadcast VC data path. This feature is available only for the PMP 450 and is not backward compatible with PMP 430 series of radios. Multicast Repeat This value is the number of packets that are repeated for every multicast Count VC packet received on the AP (located under Radio tab of Configuration). Multicast (like Broadcast) packets go over a VC that is shared by all SMs, so there is no guaranteed delivery. The repeat count is an attempt to improve the odds of the packets getting over the link. If the user has issues with packets getting dropped, they can use this parameter to improve the performance at the cost of the overall throughput possible on that channel. The default value is 0. Multicast Downlink This value is the committed information rate for the multicast downlink CIR VC (located under the Radio tab of Configuration). The default value is 0 kbps. The range of this parameter is based on the number of repeat counts. The higher the repeat count, the lower the range for the multicast downlink CIR. SM Registration All This field allows to control registration of all type 450 platform SM

(450i/450/430) or 450i Series SM only. PMP 430 SM Registration This field allows to control of PMP 430 SMs whether PMP 430 SMs are allowed to register to PMP 450 APs. By default, it is enabled and PMP 430 SM registrations are accepted. When this field is set to disabled, PMP 430 SMs registrations fail with reject reason 8. This will cause SMs to lock out the AP for 15 minutes. Note This option is not displayed if the Frame Period is set to 5 ms. This option applies only to PMP 450 5 GHz APs. Control Message Controls whether the control messages are sent in MIMO-B or MIMO-

A mode. MIMO-A is recommended. However, if an AP on 13.2 is attempting to connect to an SM on 13.1.3 or before, changing to MIMO-B may aid in getting the SM registered. Page 7-197 Chapter 7: Configuration Configuring radio parameters PMP 450/430 Legacy Disabled: It is factory default setting. It allows to operate in 450i platform mode capabilities. Enabled: It allows to operate radio in Legacy mode PMP 450 or 430. PMP 430 Interop For n-1 compatibility, In SISO mode this forces the AP to only send Mode Control and Beacons over one of the RF paths. Receive Quality To aid in link performance monitoring, the AP and SM now report the Debug number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-

QAM) and per channel (polarization). Note Due to CPU load, this will slightly degrade packet per second processing. Frame Alignment Legacy Mode Mode Behavior (non-900 MHz Behavior (FSK 900 MHz radios) radios) OFF By default frame start is aligned with devices with Timing Port synchronization If the synchronization source changes (due to Autosync or otherwise) the radio will dynamically adjust its frame start to maintain alignment with the default frame start timing The radio will align with ON devices running

(Mode 1) software versions from 12.0 to 13.4. ON

(Mode 2) N/A By default frame start is aligned with FSK 900 MHz devices with Timing Port synchronization If the synchronization source changes (due to Autosync or otherwise) the radio will dynamically adjust its frame start to maintain alignment with the default frame start timing The radio will align with FSK 900 MHz devices running software versions from 12.0 to 13.4. The radio will align with FSK 900 MHz devices with software versions 11.2 or older. Page 7-198 Chapter 7: Configuration Configuring radio parameters PMP/PTP 450i Configurating radio Radio page - PMP 450i AP 5 GHz The Radio tab of the PMP 450i AP contains some of the configurable parameters that define how an AP operates. Note Only the frequencies available for your region and the selected Channel bandwidth

(5/10/20) are displayed. Table 122 PMP 450i AP Radio attributes - 5 GHz Page 7-199 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Frequency Band Select the desired operating frequency band. Frequency Carrier Specify the frequency for the module to transmit. The default for this parameter is None. For a list of channels in the band, see the drop-down list on the radio GUI. Alternate Frequency These parameters are displayed based on Regional Settings. Refer Carrier 1 and 2 Country on page 7-142 Channel Bandwidth The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the AP and the SM. The supported Channel Bandwidths are 5, 10 and 20 MHz. Cyclic Prefix OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol to allow multi-

pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. Frame Period Select the Frame Period in of the radio. The support Frame Periods are 5 ms and 2.5 ms. Color Code Specify a value from 0 to 254. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Page 7-200 Chapter 7: Configuration Configuring radio parameters Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Subscriber Color This timer may be utilized to initiate SM rescans in order to register to an Code Rescan (When AP configured with the SMs primary color code. not on a Primary Color Code) The time (in minutes) for a subscriber to rescan (if this AP is not configured with the SMs primary color code). This timer will only fire once if the Subscriber Color Code Wait Period for Idle timer is configured with a nonzero value and the Subscriber Color Code Rescan expires, the Subscriber Color Code Wait Period for Idle is started. If the Subscriber Color Code Wait Period for Idle timer is configured with a zero value and the Subscriber Color Code Rescan timer expires, the SM will immediately go into rescan mode Subscriber Color The time (in minutes) for a subscriber to rescan while idle (if this AP is Code Wait Period for not configured with the SMs primary color code). This timer will fire Idle periodic events. The fired event determines if any RF unicast traffic

(either inbound or outbound) has occurred since the last event. If the results of the event determine that no RF unicast traffic has occurred

(SM is idle), then the subscriber will rescan. Installation Color With this feature enabled on the AP and SM, operators may install and Code remotely configure SMs without having to configure matching color codes between the modules. While the SM is accessible for configuration from above the AP (for remote provisioning) and below the SM (for local site provisioning), no user data is passed over the radio link. When using the Installation Color Code feature, ensure that the SM is configured with the factory default Color Code configuration (Color Code 1 is 0, Color Code 2-10 set to 0 and Disable). The status of the Installation Color Code can be viewed on the AP Eval web GUI page, and when the SM is registered using the Installation Color Code the message SM is registered via ICC Bridging Disabled! is displayed in red on every SM GUI page. The Installation Color Code parameter is configurable without a radio reboot for both the AP and SM. If a SM is registered via Installation Color Code and the feature is then disabled, operators will need to reboot the SM or force it to reregister (i.e. using Rescan APs functionality on the AP Eval page). Max Range Enter a number of miles (or kilometers divided by 1.61, then rounded to an integer) for the furthest distance from which a SM is allowed to register to this AP. Do not set the distance to any greater number of miles. A greater distance does not increase the power of transmission from the AP. can reduce aggregate throughput. Page 7-201 Chapter 7: Configuration Configuring radio parameters Regardless of this distance, the SM must meet the minimum requirements for an acceptable link. If the AP is in cluster, then you must set this parameter on all other APs in the cluster exactly the same, except as described in the NOTE admonition below. The default value of this parameter is 2 miles (3.2 km). Downlink Data Specify the percentage of the aggregate throughput for the downlink

(frames transmitted from the AP to the subscriber). For example, if the aggregate (uplink and downlink total) throughput on the AP is 90 Mb, then 75% specified for this parameter allocates 67.5 Mb for the downlink and 22.5 Mb for the uplink. The default for this parameter is 75%. This parameter must be set in the range of 15% - 85%, otherwise the invalid input will not be accepted and the previously-entered valid setting is used. Note This setting does not prevent a device connected to the Ethernet port from accessing the management interface of other SMs in the network. To prevent this, use the IP Access Filtering Enabled selection in the IP Access Control parameter of the SMs in the network. See IP Access Control below. Contention Slots This field indicates the number of (reserved) Contention slots configured

(a.k.a. Control Slots) by the operator. The SM uses reserved Contention slots and unused data slots for bandwidth requests. See Contention slots on page7-238. Broadcast Repeat The default is 2 repeats (in addition to the original broadcast packet, for Count a total of 3 packets sent for every one needed), and is settable to 1 or 0 repeats (2 or 1 packets for every broadcast). ARQ (Automatic Repeat reQuest) is not present in downlink broadcast packets, since it can cause unnecessary uplink traffic from every SM for each broadcast packet. For successful transport without ARQ, the AP repeats downlink broadcast packets. The SMs filter out all repeated broadcast packets and, thus, do not transport further. The default of 2 repeats is optimum for typical uses of the network as an internet access system. In applications with heavy download broadcast such as video distribution, overall throughput is significantly improved by setting the repeat count to 1 or 0. This avoids flooding the downlink with repeat broadcast packets. Transmitter Output This value represents the combined power of the APs two transmitters. Power Nations and regions may regulate transmitter output power. For example 900 MHz, 5.4 GHz and 5.8 GHz modules are available as connectorized radios, which require the operator to adjust power to ensure regulatory compliance. The professional installer of the equipment has the responsibility to maintain awareness of applicable regulations. Page 7-202 Chapter 7: Configuration Configuring radio parameters calculate the permissible transmitter output power for the module. confirm that the initial power setting is compliant with national or regional regulations. confirm that the power setting is compliant following any reset of the module to factory defaults. External Gain This value needs to correspond to the published gain of the antenna used to ensure the radio will meet regulatory requirements. SM Receive Target Each SMs Transmitter Output Power is automatically set by the AP. The Level AP monitors the received power from each SM, and adjusts each SMs Transmitter Output Power so that the received power at the AP from that SM is not greater what is set in this field. This value represents the transmitted and received power (combined power) perceived on the SM. Multicast VC Data This pull down menu of the Multicast Data Control screen helps in Rate configuring multicast packets to be transmitted over a dedicated channel at a configurable rate of 1X, 2X, 4X or 6X. The default value is Disable. If set to the default value, all multicast packets are transmitted over the Broadcast VC data path. This feature is available only for the PMP 450 and is not backward compatible with PMP 430 series of radios. Multicast Repeat This value is the number of packets that are repeated for every multicast Count VC packet received on the AP (located under Radio tab of Configuration). Multicast (like Broadcast) packets go over a VC that is shared by all SMs, so there is no guaranteed delivery. The repeat count is an attempt to improve the odds of the packets getting over the link. If the user has issues with packets getting dropped, they can use this parameter to improve the performance at the cost of the overall throughput possible on that channel. The default value is 0. Multicast Downlink This value is the committed information rate for the multicast downlink CIR VC (located under the Radio tab of Configuration). The default value is 0 kbps. The range of this parameter is based on the number of repeat counts. The higher the repeat count, the lower the range for the multicast downlink CIR. Page 7-203 Chapter 7: Configuration Configuring radio parameters SM Registration All This field allows to control registration of all type 450 platform SM

(450i/450/430) or 450i Series SM only. PMP 430 SM Registration This field allows to control of PMP 430 SMs whether PMP 430 SMs are allowed to register to PMP 450 APs. By default, it is enabled and PMP 430 SM registrations are accepted. When this field is set to disabled, PMP 430 SMs registrations fail with reject reason 8. This will cause SMs to lock out the AP for 15 minutes. Note This option is not displayed if the Frame Period is set to 5 ms. This option applies only to PMP 450 5 GHz APs. Control Message Controls whether the control messages are sent in MIMO-B or MIMO-

A mode. MIMO-A is recommended. However, if an AP on 13.2 is attempting to connect to an SM on 13.1.3 or before, changing to MIMO-B may aid in getting the SM registered. PMP 450/430 Legacy Disabled: It is factory default setting. It allows to operate in 450i platform mode capabilities. Enabled: It allows to operate radio in Legacy mode PMP 450 or 430. PMP 430 Interop For n-1 compatibility, In SISO mode this forces the AP to only send Mode Control and Beacons over one of the RF paths. Receive Quality To aid in link performance monitoring, the AP and SM now report the Debug number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-

QAM) and per channel (polarization). Note Due to CPU load, this will slightly degrade packet per second processing. Frame Alignment Legacy Mode Mode Behavior (non-900 MHz Behavior (FSK 900 MHz radios) radios) OFF By default frame start is aligned with devices with Timing Port synchronization If the synchronization source changes (due to Autosync or otherwise) the radio will dynamically adjust its frame start to maintain alignment with the By default frame start is aligned with FSK 900 MHz devices with Timing Port synchronization If the synchronization source changes (due to Autosync or otherwise) the radio will dynamically adjust its frame start to maintain alignment with the Page 7-204 Chapter 7: Configuration Configuring radio parameters default frame start default frame start timing timing The radio will align with ON devices running

(Mode 1) software versions from 12.0 to 13.4. ON

(Mode 2) N/A The radio will align with FSK 900 MHz devices running software versions from 12.0 to 13.4. The radio will align with FSK 900 MHz devices with software versions 11.2 or older. Page 7-205 Chapter 7: Configuration Configuring radio parameters Radio page PMP 450i SM 5 GHz The Radio page of PMP 450i SM is explained in Table 123. Table 123 PMP 450i SM Radio attributes 5 GHz Page 7-206 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Custom Radio Check the frequencies that SM has to scan for AP transmissions. See Frequency Scan Radio Frequency Scan Selection List on page 7-231. Selection List Channel Bandwidth The channel size used by the radio for RF transmission. Scan Note Selecting multiple channel bandwidths will increase registration and re-registration times. Cyclic Prefix Scan The cyclic prefix for which AP scanning is executed. AP Selection Method Operators may configure the method by which a scanning SM selects an AP. By default, AP Selection Method is set to Optimize for Throughput, which has been the mode of operation in releases prior to 12.0.3.1. Power Level: AP selection based solely on power level or Optimize for Throughput: AP selection based on throughput optimization the selection decision is based on power level (which affects the modulation state), channel bandwidth (which affects throughput) and number of SM registrations to the AP (which affects system contention performance). Color Code 1 Color code allows you to force the SM to register to only a specific AP, even where the SM can communicate with multiple APs. For registration to occur, the color code of the SM and the AP must match. Specify a value from 0 to 254. Page 7-207 Chapter 7: Configuration Configuring radio parameters Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). SMs may be configured with up to 20 color codes. These color codes can be tagged as Primary, Secondary, or Tertiary, or Disable. When the SM is scanning for APs, it will first attempt to register to an AP that matches one of the SMs primary color codes. Failing that, the SM will continue scanning and attempt to register to an AP that matches one of the SMs secondary color codes. Failing that, the SM will continue scanning and attempt to register to an AP that matches one of the SMs tertiary color codes. This is all done in the scanning mode of the SM and will repeat until a registration has occurred. Color codes in the same priority group are treated equally. For example, all APs matching one of the SMs primary color codes are analyzed equally. Likewise, this evaluation is done for the secondary and tertiary groups in order. The analysis for selecting an AP within a priority group is based on various inputs, including signal strength and number of SMs already registered to each AP. The first color code in the configuration is the pre-Release 9.5 color code. Thus, it is always a primary color code for legacy reasons. The color codes can be disabled, with the exception of the first color code. Installation Color With this feature enabled on the AP and SM, operators may install and Code remotely configure SMs without having to configure matching color codes between the modules. When using the Installation Color Code feature, ensure that the SM is configured with the factory default Color Code configuration (Color Code 1 is 0, Color Code 2-10 set to 0 and Disable). The status of the Installation Color Code can be viewed on the AP Eval web GUI page, and when the SM is registered using the Installation Color Code the message SM is registered via ICC Bridging Disabled! is displayed in red on every SM GUI page. The Installation Color Code parameter is configurable without a radio reboot for both the AP and SM. External Gain This value represents the antenna gain. For ODUs with integrated antenna, this is set at te correct value in the factory. For Connectorized ODUs with external antenna, the user must set this value to the overall antenna gain, including any RF cable loss between the ODU and the antenna. Large VC data Queue AP and BH have a configurable option used to prevent packet loss in the uplink due to bursting IP traffic. This is designed for IP burst traffic particular to video surveillance applications. Page 7-208 Chapter 7: Configuration Configuring radio parameters Receive Quality To aid in link performance monitoring, the AP and SM now report the Debug number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-

QAM) and per channel (polarization). Note Due to CPU load, this will slightly degrade packet per second processing. Note The frequencies that a user can select are controlled by the country or a region and the Channel Bandwidth selected. There can be a case where a user adds a custom frequency (from the Custom Frequencies page on page 7-234) and cannot see it in the pull down menu. Page 7-209 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450i AP 900 MHz The Radio tab of the PMP 450i AP 900 MHz is described in below table.Table 124. Table 124 PMP 450i AP Radio attributes - 900 MHz Page 7-210 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Frequency Carrier Specify the frequency for the module to transmit. The default for this parameter is None. For a list of channels in the band, see the drop-

down list on the radio GUI. Channel Bandwidth The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the AP and the SM. The supported Channel Bandwidths are 5, 7, 10 and 20 MHz. Cyclic Prefix Frame Period Color Code Subscriber Color Code Rescan (When not on a Primary Color Code) Subscriber Color Code Wait Period for Idle Installation Color Code Max Range Downlink Data Contention Slots

(a.k.a. Control Slots) Broadcast Repeat Count Transmitter Output Power External Gain SM Receive Target Level Multicast VC Data Rate Multicast Repeat Count See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. Multicast Downlink CIR See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. Control Message Receive Quality Debug Pager Reject Filter In 900 MHz, Pager Reject filter is placed on the AP to block Pager signals which could cause interference to the whole band. The Pager signals typically operate in the 928-930 frequency range. When the filter is enabled, the signals of 920 MHz and above are attenuated which enables better reception of signals in the rest of the band. Note that the AP/SM should not be configured on the frequencies of 920 MHz and above when this filter is enabled. Page 7-211 Chapter 7: Configuration Configuring radio parameters Frame Alignment Legacy Mode See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. Radio page - PTP 450i BHM 5 GHz The Radio page of PTP 450i BHM is explained in Table 125. Table 125 PTP 450i BHM Radio page attributes 5 GHz Page 7-212 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Frequency Band Select the operating frequency band of the radio. The supported bands are 4.9 GHz, 5.4 GHz and 5.7 GHz. Frequency Carrier Specify the frequency for the module to transmit. The default for this parameter is None. For a list of channels in the band, see the drop-down list on the radio GUI. Channel Bandwidth The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the BHM and the BHS. Cyclic Prefix OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol to allow multi-

pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. Frame Period Select the Frame Period of the radio. The support Frame Periods are : 5 ms and 2.5 ms. Color Code Specify a value from 0 to 254. For registration to occur, the color code of the BHM and the BHS must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each link a different color code. Color code allows you to force a BHS to register to only a specific BHM. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Large VC data Q Enable Large VC Q for applications that burst data high rates. Large Qs may decrease effective throughput for TCP application. Disable Large VC Q if application need not handle bursts of data. Large Qs may decrease effective throughput for TCP application. Downlink Data Specify the percentage of the aggregate throughput for the downlink

(frames transmitted from the BHM to the subscriber). For example, if the aggregate (uplink and downlink total) throughput on the BHM is 132 Mbps, then 75% specified for this parameter allocates 99 Mbps for the downlink and 33 Mbps for the uplink. The default for this parameter is 50%. This parameter must be set in the range of 15% - 85%, otherwise the invalid input will not be accepted and the previously-entered valid setting is used. Note In order to prevent self-interference, the frame configuration needs to align. This includes Downlink Data, Max Range and Contention slots. Transmit Power This value represents the combined power of the BHMs two transmitters. Nations and regions may regulate transmit power. For example Page 7-213 Chapter 7: Configuration Configuring radio parameters PTP 450i modules are available as connectorized radios, which require the operator to adjust power to ensure regulatory compliance. The professional installer of the equipment has the responsibility to:

Maintain awareness of applicable regulations. Calculate the permissible transmitter output power for the module. Confirm that the initial power setting is compliant with national or regional regulations. Confirm that the power setting is compliant following any reset of the module to factory defaults. External Gain This value needs to correspond to the published gain of the antenna used to ensure the radio will meet regulatory requirements. Receive Quality To aid in link performance monitoring, the BHM and BHS now report the Debug number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-

QAM, 256-QAM) and per channel (polarization). Note Due to CPU load, this slightly degrades the packet during per second processing. See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. Frame Alignment Legacy Mode Page 7-214 Chapter 7: Configuration Configuring radio parameters Radio page PTP 450i BHS 5 GHz The Radio page of PTP 450i BHS is explained in Table 126. Table 126 PTP 450i BHS Radio attributes 5 GHz Page 7-215 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Custom Radio Check any frequency that you want the BHS to scan for BHM Frequency Scan transmissions. See Radio Frequency Scan Selection List on page 7-231. Selection List Channel Bandwidth The channel size used by the radio for RF transmission. Scan Note Selecting multiple channel bandwidths will increase registration and re-registration times. Cyclic Prefix Scan The cyclic prefix for which BHM scanning is executed. Color Code Color code allows to force the BHS to register to only a specific BHM, even where the BHS can communicate with multiple BHMs. For registration to occur, the color code of the BHS and the BHM must match. Specify a value from 0 to 254. The color codes can be disabled, with the exception of the first color code. Large VC data Q BHM and BHS have a configurable option used to prevent packet loss in the uplink due to bursting IP traffic. This is designed for IP burst traffic particular to video surveillance applications. Transmit Power Refer Table 125 PTP 450i BHM Radio page attributes 5 GHz on page 7-

212 External Gain Receive Quality Debug Page 7-216 Chapter 7: Configuration Configuring radio parameters PMP/PTP 450 Configurating radio Radio page - PMP 450 AP 5 GHz The Radio tab of the AP for 5 GHz is as shown in.Table 127. Table 127 PMP 450 AP Radio attributes - 5 GHz Page 7-217 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Radio Configuration, See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. Frame Configuration, Power Control, Multicast Data Control and Advance tab PMP 430 SM Registration PMP 450/430 Legacy Mode Control Messages PMP 430 Interop Mode Receive Quality Debug Frame Alignment Legacy Mode See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. Page 7-218 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 AP 3.65 GHz Table 128 PMP 450 AP Radio attributes - 3.65 GHz Attribute Meaning Radio Configuration, See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. Frame Configuration, Power Control, Multicast Data Control and Advance tab Page 7-219 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 AP 3.5 GHz Table 129 PMP 450 AP Radio attributes - 3.5 GHz Attribute Meaning Radio Configuration, See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. Frame Configuration, Power Control, Multicast Data Control and Advance tab Page 7-220 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 AP 2.4 GHz Table 130 PMP 450 AP Radio attributes - 2.4 GHz Attribute Meaning Radio Configuration, See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. Frame Configuration, Power Control, Multicast Data Control and Advance tab Page 7-221 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 SM 5 GHz Table 131 PMP 450 SM Radio attributes 5 GHz Page 7-222 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Custom Radio Check the frequencies that SM has to scan for AP transmissions. See Frequency Scan Radio Frequency Scan Selection List on page 7-231. Selection List See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. Page 7-223 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 SM 3.65 GHz Table 132 PMP 450 SM Radio attributes 3.65 GHz Attribute Meaning Custom Radio Check the frequencies that SM has to scan for AP transmissions. See Frequency Scan Radio Frequency Scan Selection List on page 7-231. Selection List See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. Page 7-224 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 SM 3.5 GHz Table 133 PMP 450 SM Radio attributes 3.5 GHz Attribute Meaning Custom Radio Check the frequencies that SM has to scan for AP transmissions. See Frequency Scan Radio Frequency Scan Selection List on page 7-231. Selection List See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. Page 7-225 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 SM 2.4 GHz Table 134 PMP 450 SM Radio attributes 2.4 GHz Page 7-226 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Custom Radio Check the frequencies that SM has to scan for AP transmissions. See Frequency Scan Radio Frequency Scan Selection List on page 7-231. Selection List See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. Radio page - PMP 450 SM 900 MHz Table 135 PMP 450 SM Radio attributes 900 MHz Page 7-227 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Custom Radio See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. Frequency Scan Selection List Channel Bandwidth See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. Scan Cyclic Prefix Scan AP Selection Method Color Code 1 Installation Color Code Large VC data Queue Color Code External Gain See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199 Receive Quality See Table 122 PMP 450i AP Radio attributes - 5 GHz on page 7-199. Debug Note The frequencies that a user can select are controlled by the country or a region and the Channel Bandwidth selected. There can be a case where a user adds a custom frequency (from the Custom Frequencies page on page 7-234) and cannot see it in the pull down menu. Page 7-228 Chapter 7: Configuration Configuring radio parameters Radio page - PTP 450 BHM 5 GHz Table 136 PTP 450 BHM Radio attributes 5 GHz Attribute Meaning Refer Table 125 PTP 450i BHM Radio page attributes 5 GHz on page 7-212 for all parameters details. Page 7-229 Chapter 7: Configuration Configuring radio parameters Radio page - PTP 450 BHS 5 GHz Table 137 PTP 450 BHM Radio attributes 5 GHz Attribute Meaning Refer Table 126 PTP 450i BHS Radio attributes 5 GHz on page 7-215 for all parameters detals. Page 7-230 Chapter 7: Configuration Configuring radio parameters Radio Frequency Scan Selection List The SM or BHS scans complete spectrum as per Full Spectrum Band Scan feature. SMs or BHS first boot into the smallest selected channel bandwidth (10 MHz, if selected) and scan all selected frequencies across both the 5.4 GHz and 5.7 GHz frequency bands. After this scan, if a wider channel bandwidth is selected (20 MHz), the SM/BHS automatically changes to 20 MHz channel bandwidth and then scans for APs/BHSs. After the SM/BHS finishes this final scan it will evaluate the best AP/BHM with which to register. If required for registration, the SM/BHS changes its channel bandwidth back to 10 MHz to match the best AP/BHM. The SM/BHS will attempt to connect to an AP/BHM based on power level (which affects the modulation state), channel bandwidth (which affects throughput) and number of SM/BHS registrations to the AP/BHM (which affects system contention performance). If it is desired to prioritize a certain AP/BHM over other available APs/BHMs, operators may use the Color Code Priority feature on the SM/BHS. Utilization of the Color Code feature on the AP/BHM is recommended to further constrain the AP selection. If the SM does not find any suitable APs/BHMs for registration after scanning all channel bandwidths, the SM restarts the scanning process beginning with the smallest configured channel bandwidth. Selecting multiple frequencies and multiple channel bandwidths impacts the SM/BHS scanning time. The biggest consumption of time is in the changing of the SM/BHS channel bandwidth setting. The worst case scanning time is approximately two minutes after boot up (SM/BHS with all frequencies and channel bandwidths selected and registering to an AP/BHM at 10 MHz). If only one channel bandwidth is selected the time to scan all the available frequencies and register to an AP/BHM is approximately one minute after boot up. Other scanning features such as Color Code, Installation Color Code, and RADIUS authentication are unaffected by the Full Band Scan feature. Dedicated Multicast Virtual Circuit (VC) A Multicast VC allows to configure multicast packets to be transmitted over a dedicated channel at a configurable rate of 1X, 2X, 4X or 8X. This feature is available only for the PMP 450 and PMP 450i and is not backward compatible with PMP 430 series of radios. To configure Multicast VC, the AP must have this enabled. This can be enabled in the Multicast Data Control section (under Configuration > Radio page). The default value is Disable. If set to the default value, all multicast packets are transmitted over the Broadcast VC data path. To enable, select the data rate that is desired for the Multicast VC Data Rate parameter and click Save Changes button. The radio requires no reboot after any changes to this parameter. The multicast VC allows three different parameters to be configured on the AP. These can be changed on the fly and are saved on the flash memory. Page 7-231 Chapter 7: Configuration Configuring radio parameters Note If the Multicast VC Data Rate is set to a modulation that the radio is not currently capable of or operates in non-permitted channel conditions, multicast data is sent but not received. Ex: If Multicast VC Data Rate is set to 6x and the channel conditions only permit 4x mode of operation, then multicast data is sent at 6x modulation but the SM will not receive the data. Note The PMP 450 AP supports up to 119 VCs (instead of 238 VCs) when configured for 30 MHz channel bandwidth or 5 ms Frame Period. This limitation is not applicable for PMP 450i platform. Note Actual Multicast CIR honored by the AP = Configured Multicast CINR/ (Multicast Repeat Count + 1). Increasing the Multicast data rate has no impact on the Unicast data rate. For multicast and unicast traffic mix scenario examples, see Table 138. Table 138 Example for mix of multicast and unicast traffic scenarios Repeat Count Multicast Data Unicast Data Aggregate DL Data Rate (Mbps) Rate (Mbps) Rate (Mbps) 0 1 2 10 5 3.33 40 40 40 50 45 43.33 The statistics have been added to the Data VC page (under Statistics > Data VC). The table displays the multicast row on the PMP 450 platform AP. The SM displays the multicast row if it is a PMP 450 platform. Figure 122 Multicast VC statistics The AP and SM display Transmit and Receive Multicast Data Count (under the Statistics >

Scheduler page), as shown in Figure 123. Page 7-232 Chapter 7: Configuration Configuring radio parameters Figure 123 Multicast scheduler statistics Page 7-233 Chapter 7: Configuration Configuring radio parameters Custom Frequencies page In addition to the Radio tab, AP/SM/BH has another tab called Custom Frequencies as shown in Table 139. The custom frequency tab allows to configure custom frequency at 1 KHz raster. It means that the custom frequencies can be at granularity of 1 KHz e.g. 4910.123 MHz, 4922.333 MHz, 4933.421 MHz etc. Note Ensure that a customer frequency exists before using SNMP to set the radio to a Custom Frequency. Table 139 PMP/PTP 450 platform AP/SM/BH Custom Frequencies page 5 GHz Attribute Meaning Custom Frequency Custom frequencies with a channel raster of 1 KHz can be added from Configuration the available range by keying in the frequency and then clicking the Add Frequency button. Click Remove Frequency button to delete a specific frequency keyed in the text box. Click Default Frequencies button to add a pre-defined list of frequencies that can be used in this band. This list can be reduced or increased by manually removing or adding other custom frequencies. Custom Frequencies Displays the complete list of user configured custom frequencies. Page 7-234 Chapter 7: Configuration Configuring radio parameters Table 140 PMP/PTP 450 SM/BH Custom Frequencies page 3.65 GHz Attribute Meaning Custom Frequency Custom frequencies with a channel raster of 1 KHz can be added from Configuration the available range by keying in the frequency and then clicking the Add Frequency button. Click Remove Frequency button to delete a specific frequency keyed in the text box. Click Default Frequencies button to add a pre-defined list of frequencies that can be used in this band. This list can be reduced or increased by manually removing or adding other custom frequencies. Custom Frequencies Displays the complete list of user configured custom frequencies. Page 7-235 Chapter 7: Configuration Configuring radio parameters Table 141 PMP/PTP 450 SM/BH Custom Frequencies page 3.5 GHz Attribute Meaning Custom Frequency Custom frequencies with a channel raster of 1 KHz can be added from Configuration the available range by keying in the frequency and then clicking the Add Frequency button. Click Remove Frequency button to delete a specific frequency keyed in the text box. Click Default Frequencies button to add a pre-defined list of frequencies that can be used in this band. This list can be reduced or increased by manually removing or adding other custom frequencies. Page 7-236 Chapter 7: Configuration Configuring radio parameters DFS for 5 GHz Radios Dynamic Frequency Selection (DFS) is a requirement in several countries and regions for 5 GHz unlicensed systems to detect radar systems and avoid co-channel operation. DFS and other regulatory requirements drive the settings for the following parameters, as discussed in this section:

Country Code Primary Frequency Alternate 1 and Alternate 2 Frequencies External Antenna Gain On the AP, the Home > DFS Status page shows current DFS status of all three frequencies and a DFS log of past DFS events. Figure 124 AP DFS Status DFS operation The ODUs use region-specific DFS based on the Country Code selected on the modules Configuration, General page. By directing installers and technicians to set the Country Code correctly, the operator gains confidence the module is operating according to national or regional regulations without having to deal with the details for each region. The details of DFS operation for each Country Code, including whether DFS is active on the AP, SM, and which DFS regulations apply is shown in Table 229 on page 10-36. Page 7-237 Chapter 7: Configuration Contention slots Configuring radio parameters The SM uses reserved Contention slots and unused data slots for bandwidth requests. Uplink Data Slots are used first for data. If they are not needed for data in a given frame, the remaining data slots can be used by the SMs for bandwidth requests. This allows SMs in sectors with a small number of Contention slots configured to still successfully transmit bandwidth requests using unused data slots. A higher number of Contention slots give higher probability that a SMs bandwidth request is correctly received when the system is heavily loaded, but with the tradeoff that sector capacity is reduced, so there is less capacity to handle the request. The sector capacity reduction is about 200 kbps for each Contention slot configured in a 20 MHz channel at QPSK MIMO-A modulation. The reduction in sector capacity is proportionally higher at MIMO-B modulations (2 times at QPSK MIMO-B, 4 times at 16 QAM MIMO-B, 6 times at 64 QAM MIMO-B and 8 times at 256 QAM MIMO-

B). If very few reserved Contention slots are specified, then latency increases in high traffic periods. If too many are specified, then the maximum capacity is unnecessarily reduced. The suggested Contention slot settings as a function of the number of active VCs in the sector are shown in the table below. Table 142 Contention slots and number of VCs Number of VCs Recommended Number of Contention slots 1 to 10 11 to 50 51 to 150 151 and above 3 4 6 8 Note that each SM uses one or two VCs. All SMs have a Low Priority Channel that uses one VC; if the High Priority Channel is enabled for the SM, then the SM uses a second VC. Therefore the number of active VCs in a sector is greater than or equal to the number of SMs registered to the AP in the sector. For example, a network including 20 SMs with High Priority Channel disabled and 20 SMs with High Priority Channel enabled has 60 active VCs and may be configured with 6 Contention slots. In a typical cluster, each AP must be set to the same number of Contention slots to assure proper timing in the send and receive cycles. However, where high incidence of small packets exists, as in a sector that serves several VoIP streams, additional Contention slots may provide better results. For APs in a cluster of mismatched Contention slots setting, or where PMP 450 is collocated with radios using different technologies, like PMP 430 or FSK, in the same frequency band, use the frame calculator. To download the PMP 450 Contention Slots Paper, see http://www.cambiumnetworks.com/solution-papers/pmp-450-contention-slots. Page 7-238 Chapter 7: Configuration Configuring radio parameters MIMO-A mode of operation PMP/PTP 450 platform supports MIMO-B mode using the following modulation levels: QPSK, 16-

QAM, 64-QAM and 256-QAM. System Release 13.2 introduces MIMO-A mode of operation using the same modulation levels as the MIMO-B mode. With MIMO-B, the radio sends different streams of data over the two antennas whereas with MIMO-A, the radio uses a scheme that tries to optimize coverage by transmitting the same data over both antennas. This redundancy improves the signal to noise ratio at the receiver making it more robust, at the cost of throughput. In addition to introducing MIMO-A modes, improvements have been made to the existing rate adapt algorithm to switch between MIMO-A and MIMO-B seamlessly without any intervention or added configuration by the operator. The various modulation levels used by the PMP 450 are shown in Table 143. Table 143 PMP/PTP 450 platform Modulation levels Rate QPSK MIMO-B MIMO-A 2X MIMO-B 1X MIMO-A 16-QAM 4X MIMO-B 2X MIMO-A 64-QAM 6X MIMO-B 3X MIMO-A 265-QAM 8X MIMO-B 4X MIMO-A System Performance For System Performance details of all the PMP/PTP 450 platform Series products please refer the Link Capacity Planner at:

https://support.cambiumnetworks.com/files/pmp450. Page 7-239 Chapter 7: Configuration Configuring radio parameters Table 144 Co-channel Interference per (CCI) MCS MCS of Victim MCS of Interferer Channel BW (MHz) CCI 1X (QPSK SISO) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30 10 dB 2X (16-QAM SISO) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30 17 dB 3X (64-QAM SISO) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30 25 dB 1X (QPSK MIMO-A) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30 7 dB 2X (16-QAM MIMO-A) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30 14 dB 3X (64-QAM MIMO-A) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30 22 dB 4X (256-QAM MIMO-A) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30 30 dB 2X (QPSK MIMO-B) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30 10 dB 4X (16-QAM MIMO-B) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30 17 dB 6X (64-QAM MIMO-B) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30 25 dB 8X (256-QAM MIMO-B) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30 33 dB Table 145 Adjacent Channel Interference (ACI) per MCS MCS of Victim MCS of Interferer Channel BW (MHz) ACI Guard Band 1X (QPSK SISO) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30

-16 dB None 2X (16-QAM SISO) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30

-16 dB None 3X (64-QAM SISO) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30

-16 dB None 1X (QPSK MIMO-A) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30

-13 dB None 2X (16-QAM MIMO-A) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30

-13 dB None 3X (64-QAM MIMO-A) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30

-13 dB None 4X (256-QAM MIMO-A) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30

-10 dB None 2X (QPSK MIMO-B) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30

-16 dB None 4X (16-QAM MIMO-B) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30

-16 dB None 6X (64-QAM MIMO-B) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30

-16 dB None 8X (256-QAM MIMO-B) 6X (64-QAM MIMO-B) 5, 10, 15, 20 or 30

-10 dB None Guard Band No Guard Bands are needed for the 5.4 GHz and 5.8 GHz bands. Page 7-240 Chapter 7: Configuration Configuring radio parameters Improved PPS performance of PMP 450 and 450i SMs The PMP 450 platforms Series provides improved packets per second (PPS) performance with regards to the PMP 450. Through hardware and software enhancements, the PPS performance of the PMP 450i AP has been improved to 40000 packets/second, measured through a standard RFC2544 test using 64 bytes packets. With this enhancement, operators are able to provide higher bandwidth including better VoIP and video services to end customers using existing SM deployments. Page 7-241 Chapter 7: Configuration Setting up SNMP agent Setting up SNMP agent Operators may use SNMP commands to set configuration parameters and retrieve data from the AP and SM modules. Also, if enabled, when an event occurs, the SNMP agent on the PMP/PTP 450 platform sends a trap to whatever SNMP trap receivers configured in the management network. SNMPv2c SNMPv3 Page 7-242 Chapter 7: Configuration Setting up SNMP agent Configuring SM/BHSs IP over-the-air access To access the SM/BHS management interface from a device situated above the AP, the SM/BHSs Network Accessibility parameter (under the web GUI at Configuration > IP) may be set to Public. Table 146 LAN1 Network Interface Configuration tab of IP page attributes Attribute Meaning IP Address Internet Protocol (IP) address. This address is used by family of Internet protocols to uniquely identify this unit on a network. Network Accessibility Specify whether the IP address of the SM/BHS must be visible to only a device connected to the SM/BHS by Ethernet (Local) or be visible to the AP/BHM as well (Public). Subnet Mask parameter configures the subnet mask of the SM/BHS for RF If Static IP is set as the Connection Type of the WAN interface, then this management traffic. Gateway IP Address parameter configures the gateway IP address for the SM/BHS for RF If Static IP is set as the Connection Type of the WAN interface, then this management traffic. If Enabled is selected, the DHCP server automatically assigns the IP configuration (IP address, subnet mask, and gateway IP address) and the DHCP state values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable (read only), in the Network Interface tab of the Home page. Canopy devices allow for configuration of a preferred and alternate DNS server IP address either automatically or manually. Devices must set DNS IP Address DNS server IP address manually when DHCP is disabled for the management interface of the device. The default DNS IP addresses are 0.0.0.0 when configured manually. Preferred DNS Server The first address used for DNS resolution. Page 7-243 Chapter 7: Configuration Setting up SNMP agent Alternate DNS If the Preferred DNS server cannot be reached, the Alternate DNS Server Server is used. Domain Name The operators management domain name may be configured for DNS. The domain name configuration can be used for configuration of the servers in the operators network. The default domain name is example.com, and is only used if configured as such. Configuring SNMP The SNMP page configuration is explained below. Note The SNMP page for AP, SM, BHM and BHS has the same parameter attributes. SNMP page AP/SM/BHM/BHS The SNMP page is explained in Table 147. Page 7-244 Chapter 7: Configuration Setting up SNMP agent Table 147 SNMP page attributes Page 7-245 Chapter 7: Configuration Setting up SNMP agent Attribute Meaning SNMP Community Specify a control string that can allow a Network Management Station String 1

(NMS) to access SNMP information. No spaces are allowed in this string. The default string is Canopy. SNMP Community You can designate the SNMP Community String 1 to be the password String 1 Permissions for WM, for example, to have Read / Write access to the module via SNMP or for all SNMP access to the module to be Read Only. SNMP Community Specify an additional control string that can allow a Network String 2 (Read Only) Management Station (NMS) to read SNMP information. No spaces are allowed in this string. The default string is Canopyro. This password will never authenticate a user or an NMS to read/write access. The Community String value is clear text and is readable by a packet monitor. Additional security derives from the configuration of the Accessing Subnet, Trap Address, and Permission parameters. Engine ID The Engine ID may be between 5 and 32 hex characters. The hex character input is driven by RFC 3411 recommendations on the Engine ID. The default Engine ID is the MAC address of the device SNMPv3 Security Specify security model where users are defined and authenticated Level before granting access to any SNMP service. Each device can configure the security level of SNMPv3 to No authentication/No privacy, Authentication/No privacy, or Authentication/Privacy. Currently, the SNMPv3 authentication protocol MD5 is supported. SNMPv3 Authentication Protocol SNMPv3 Privacy Currently, the SNMPv3 privacy protocol CBC-DES is supported. Protocol SNMPv3 Read-Only This filed allows for a read-only user per devices. The default values for User the Read-Only users is:

Username = Canopyro Authentication Password = authCanopyro Privacy Password = privacyCanopyro SNMPv3 Read/Write Read-write user by default is disabled. The default values for the User Read/Write users is :

Username = Canopy Authentication Password = authCanopy Privacy Password = privacyCanopy SNMPv3 Trap Configuration When enabling transmission of SNMPv3 traps the read-only or read-

write user credentials must be used and selected properly in order for the SNMP manager to correctly interpret the traps. By default transmission of SNMPv3 traps is disabled and all traps sent from the radios are in SNMPv2c format. Page 7-246 Chapter 7: Configuration Setting up SNMP agent Accessing IP /

Specify the addresses that are allowed to send SNMP requests to this Subnet Mask 1 to 10 AP. The NMS has an address that is among these addresses (this subnet). You must enter both The network IP address in the form xxx.xxx.xxx.xxx The CIDR (Classless Interdomain Routing) prefix length in the form

/xx For example:

the /16 in 198.32.0.0/16 specifies a subnet mask of 255.255.0.0 (the first 16 bits in the address range are identical among all members of the subnet). 192.168.102.0 specifies that any device whose IP address is in the range 192.168.102.0 to 192.168.102.254 can send SNMP requests to the AP, presuming that the device supplies the correct Community String value. The default treatment is to allow all networks access. For more information on CIDR, execute an Internet search on Classless Interdomain Routing. You are allowed to specify as many as 10 different accessing IP address, subnet mask combinations. RECOMMENDATION:

The subscriber can access the SM/BHS by changing the subscriber device to the accessing subnet. This hazard exists because the Community String and Accessing Subnet are both visible parameters. To avoid this hazard, configure the SM/BHS to filter (block) SNMP requests. SNMP Trap Server The management DNS domain name may be toggled such that the DNS Usage name of the trap server only needs to be specified and the DNS domain name is automatically appended to that name. The default SNMP trap server addresses for all 10 available servers is 0.0.0.0 with the appending of the DNS domain name disabled. Trap Address 1 to 10 Specify ten or fewer IP addresses (xxx.xxx.xxx.xxx) or DNS names to which SNMP traps must be sent. Traps inform Wireless Manager or an NMS that something has occurred. For example, trap information is sent after a reboot of the module. when an NMS attempts to access agent information but either supplied an inappropriate community string or SNMP version number. is associated with a subnet to which access is disallowed. Trap Enable, Sync If the sync status traps (sync lost and sync regained) have to be sent to Status Wireless Manager or an NMS, select Enabled. If these traps have to be suppressed, select Disabled. Trap Enable, Session If you want session status traps sent to Wireless Manager or an NMS, Status select Enabled. Page 7-247 Chapter 7: Configuration Setting up SNMP agent Site Information Operators can enable or disable site information from appearing when a Viewable to Guest user is in GUEST account mode. Users Site Name Specify a string to associate with the physical module. This parameter is written into the sysName SNMP MIB-II object and can be polled by Wireless Manager or an NMS. The buffer size for this field is 128 characters. Site Contact Enter contact information for the module administrator. This parameter is written into the sysContact SNMP MIB-II object and can be polled by Wireless Manager or an NMS. The buffer size for this field is 128 characters. Site Location Enter information about the physical location of the module. This parameter is written into the sysLocation SNMP MIB-II object and can be polled by Wireless Manager or an NMS. The buffer size for this field is 128 characters. Page 7-248 Chapter 7: Configuration Configuring syslog Configuring syslog PMP/PTP 450 platform Series includes below sections. Syslog event logging Configuring system logging Page 7-249 Chapter 7: Configuration Syslog event logging Following events are logged in syslog as explained in Table 148. Table 148 Syslog parameters Attribute Meaning Configuring syslog Timestamp All syslog messages captured from the radio have a timestamp. Configuration This includes any device setting that has changed and includes the old Changes or new parameter value, including the device reboots. User Login and Logout Add or Delete of user Syslog records each user login and logout, with username. accounts through Syslog captures any user accounts that are added or deleted. GUI and SNMP Spectrum Analysis Syslog records a message every time Spectrum Analysis runs. Note Since the AP/BHM must be set to a SM/BHS for Spectrum Analysis, syslog messages are not reported from the radio until the scan is done and the radio mode is switched back to AP/BHM. Link Test Syslog records a message every time a Link Test is run. Clear Statistics SM Register or De-

register BHS Connect or Disconnect Syslog sends a message when Statistics are cleared. This is done individually for each statistics page that is cleared. Syslog records a message when a SM registers or deregisters. Syslog records a message when a BHS connects or disconnects. Configuring system logging To configure system logging, select the menu option Configuration > Syslog. Syslog page of AP/BHM The Syslog Configuration page for AP/BHM is shown in Table 149. Page 7-250 Chapter 7: Configuration Configuring syslog Table 149 Syslog Configuration attributes - AP Attribute Meaning Syslog DNS Server Usage To configure the AP/BHM to append or not append the DNS server name to the syslog server name. Syslog Server The dotted decimal or DNS name of the syslog server address. Syslog Server Port AP Syslog Transmit Or BHM Syslog Transmit The syslog server port (default 514) to which syslog messaging is sent. When enabled, syslog messages are sent from the AP/BHM. SM Syslog Transmit When enabled, syslog messages are sent from all the registered Or BHS Syslog Transmit SMs/BHS, unless they are individually set to override this. This provides a selection for the minimum syslog message severity that is sent to the syslog server. Values range from fatal (highest severity and least verbose) to info (lowest severity, maximum verbosity). For example: If the Syslog Minimum Level is set to notice, then only messages with severity notice and above are sent. Syslog Minimum Level Syslog page of SM To configure system logging, select the menu option Configuration > Syslog. The Syslog Configuration page is shown in Table 150. Page 7-251 Chapter 7: Configuration Configuring syslog Table 150 Syslog Configuration attributes - SM Attribute Meaning Syslog Configuration This control determines whether the SM will attempt to use the syslog Source server definition from the AP, or whether it will use a local server definition. When set to AP preferred, use local when AP configuration unavailable, and if the SM can register with an AP, then it uses the syslog server defined on that AP. If the SM cannot register then it will syslog to its locally defined syslog server through its wired connection, if any. When set to Local only the SM ignores the APs definition of the syslog server and allows the syslog server to be configured individually for each SM. Syslog DNS Server To configure the SM to append or not the DNS server name to the Usage syslog server name. Syslog Server The dotted decimal or DNS name of the syslog server address. Syslog Server Port The syslog server port (default 514) to which syslog messaging is sent. Syslog Transmission Controls the SMs ability to transmit syslog messages. When set to Learn from AP the AP will control whether this SM transmits syslog messages. When set to enable or disable the SM will control whether it sends syslog messages. This allows an operator to override the AP settings for individual SMs in a sector. This control determines whether the SM attempts to use the minimum syslog level defined by the AP, or whether it uses a local defined value using the Syslog Minimum Level parameter. Syslog Minimum Level Source When set to AP preferred, use local when AP configuration unavailable, and if the SM can register with an AP, then it uses the Syslog Minimum Level defined on that AP. If the SM cannot register then it uses its own Syslog Minimum Level setting. When set to Local only the SM will always use its own Syslog Minimum Level setting and ignores the APs setting. Page 7-252 Chapter 7: Configuration Configuring syslog Syslog Minimum Level This provides a selection for the minimum syslog message severity that is sent to the syslog server. Values range from fatal (highest severity and least verbose) to info (lowest severity, maximum verbosity). For example: If the Syslog Minimum Level is set to notice, then only messages with severity notice and above are sent. Syslog page of BHS The Syslog Configuration page is shown in Table 151. Table 151 Syslog Configuration attributes - BHS Attribute Meaning Syslog Configuration This control determines whether the BHS will attempt to use the syslog Source server definition from the BHM, or whether it will use a local server definition. When set to BHM preferred, use local when BHM configuration unavailable, and if the BHS can register with a BHM, then it uses the syslog server defined on that BHM. If the BHS cannot register then it will syslog to its locally defined syslog server through its wired connection, if any. When set to Local only the BHS ignores the BHMs definition of the syslog server and allows the syslog server to be configured individually for each BHS. Syslog DNS Server To configure the BHS to append or not to append the DNS server name Usage to the syslog server name. Syslog Server The dotted decimal or DNS name of the syslog server address. Syslog Server Port The syslog server port (default 514) to which syslog messaging is sent. Syslog Transmission Controls the BHSs ability to transmit syslog messages. When set to Learn from BHM the BHM will control whether this BHS transmits syslog messages. When set to enable or disable the BHS will control Page 7-253 Chapter 7: Configuration Configuring syslog Syslog Minimum Level Source Syslog Minimum Level whether it sends syslog messages. This allows an operator to override the BHM settings for individual BHSs in a sector. This control determines whether the BHS attempts to use the minimum syslog level defined by the BHM, or whether it uses a local defined value using the Syslog Minimum Level parameter. When set to BHM preferred, use local when BHM configuration unavailable, and if the BHS can register with a BHM, then it uses the Syslog Minimum Level defined on that BHM. If the BHS cannot register then it uses its own Syslog Minimum Level setting. When set to Local only the BHS will always use its own Syslog Minimum Level setting and ignores the BHMs setting. This provides a selection for the minimum syslog message severity that is sent to the syslog server. Values range from fatal (highest severity and least verbose) to info (lowest severity, maximum verbosity). For example: If the Syslog Minimum Level is set to notice, then only messages with severity notice and above are sent. Page 7-254 Chapter 7: Configuration Configuring remote access Configuring remote access Accessing SM/BHS over-the-air by Web Proxy The SM/BHS may be accessed via the AP/BHM management GUI by navigating to Home > Session Status (or Home > Remote Subscribers for AP only) and clicking on the SMs hyperlink. For example, to access one of the SMs, click LUID: 002 [0a-00-3e-37-b9-fd], as shown in Figure 125. Figure 125 AP Session Status page The SessionStatus.xml hyper link allows user to export all displayed SM data in Session Status table into an xml file. To access any one of the SMs, click PMP450 platform SM hyperlink, as shown in Figure 126. Figure 126 AP Remote Subscribers page Page 7-255 Chapter 7: Configuration Monitoring the Link Monitoring the Link Link monitoring procedure After configuring the link, either an operator in the network office or the SM/BHS INSTALLER user in the field (if read access to the AP/BHM is available to the INSTALLER) must perform the following procedure. Who is authorized and able to do this depends on local operator password policy, management VLAN setup and operational practices. To monitor the link for performance, follow these instructions:

Procedure 22 Monitoring the AP-SM link 1 Access the web interface of the AP/BHM 2 In the left-side menu of the AP/BHM interface, select Home. 3 Click the Session Status tab. Figure 127 Session Status page 4 The Device tab of Session Status List display all displayed SMs MAC address, PMP/PTP Hardware, Software Version, FPGA Version and State Page 7-256 Chapter 7: Configuration Monitoring the Link 5 Click Session Count tab of Session Status List to display values for Session Count, Reg Count, and Re-Reg Count. Session Count: This field displays how many sessions the SM/BHS has had with the AP/BHM. Typically, this is the sum of Reg Count and Re-Reg Count. However, the result of internal calculation may display here as a value that slightly differs from the sum. Reg Count: When a SM/BHS makes a Registration Request, the AP/BHM checks its local session database to see whether it was registered earlier. If the AP/BHM concludes that the SM/BHS is not currently in session database and it is valid Registration Request, then the request increments the value of this field. Re-Reg Count: When a SM/BHS makes a Registration Request, the AP/BHM checks its local session database to see whether it was registered earlier. If the AP/BHM concludes that the SM/BHS is currently in session database, then the request increments the value of this field. Typically, a Re-Reg is the case where both o SM/BHS attempts to reregister for having lost communication with the AP/BHM. o AP/BHM has not yet observed the link to the SM/BHS as being down. See Session tab on page 9-17 6 Click Power tab of Session Status list to display Downlink Rate, AP Rx Power (dBm), Signal Strength Radio (dB) for Uplink and Signal to Noise Radio (dB) for Uplink. See Power tab on page 9-19 7 Click Configuration tab of Session Status list to get QoS configuration details:

Sustained Data Rate (kbps) Burst Allocation (kbit) Max Burst Rate (kbit) Low Priority CIR (kbps) See Configuration tab on page 9-20 8 Briefly monitor these values, occasionally refreshing this page by clicking another tab and then the Session Status tab again. 9 If these values are low (for example, 1, 1, and 0, respectively, meaning that the SM/BHS registered and started a stable session once) and are not changing:

Consider the installation successful. Monitor these values from the network office over the next several hours and days. If these values are greater than 1, 1, and 0, or they increase while you are monitoring them, troubleshoot the link. (For example, Use Receive Power Level for aiming and then use Link Tests to confirm alignment). Refer Viewing Session Status on page 9-16 for more details. Page 7-257 Chapter 7: Configuration Monitoring the Link Exporting Session Status page of AP/BHM The SessionStatus.xml hyper link allows user to export all displayed SMs or BHS data in Session Status table into an xml file. Figure 128 Exporting Session Status page of PMP 450i AP In case of PMP, if the session status page does not list any SM, the SessionStatus.xml will still be visible but the file would be empty. The file will contain data from all of the 5 different tables. Export from command line The scripts users can also get this file from command line, you have to authenticate successfully in order to download the file. Wget http://169.254.1.1/SessionStatus.xml?CanopyUsername=test&CanopyPassword=test Page 7-258 Chapter 7: Configuration Configuring quality of service Configuring quality of service Maximum Information Rate (MIR) Parameters Point-to-multipoint links use the following MIR parameters for bandwidth management:

Sustained Uplink Data Rate (kbps) Uplink Burst Allocation (kb) Sustained Downlink Data Rate (kbps) Downlink Burst Allocation (kb) Max Burst Downlink Data Rate (kbps) Max Burst Uplink Data Rate (kbps) Set each of these parameters per AP or per SM independently. Token Bucket Algorithm The software uses a token bucket algorithm that has the following features:

Stores credits (tokens) for the SM to spend on bandwidth for reception or transmission. Drains tokens during reception or transmission. Refills with tokens at the sustained rate set by the network operator. For each token, the SM can send toward the network in the uplink (or the AP can send toward the SM in the downlink) an equivalent number of kilobits. Two buckets determine the permitted throughput: one in the SM for uplink and one in the AP for downlink. The applicable set of Uplink Burst Allocation and Downlink Burst Allocation parameters determine the number of tokens that can fill each bucket. When the SM transmits (or the AP transmits) a packet, the equivalent number of tokens is removed from the uplink (or downlink) bucket. Except when full, the bucket is continuously being refilled with tokens at rates that the applicable set of Sustained Uplink Data Rate and Sustained Downlink Data Rate parameters specify. The bucket often drains at a rate that is much faster than the sustained data rate but can refill at only the sustained data rate. Thus, the effects of the allocation and rate parameters on packet delay are as follows:

The burst allocation affects how many kilobits are processed before packet delay is imposed. The sustained data rate affects the packet delay that is imposed. Page 7-259 Chapter 7: Configuration Configuring quality of service MIR Data Entry Checking Uplink and downlink MIR is enforced as shown in Figure 129. Note In these figures, entry refers to the setting in the data rate parameter, not the burst allocation parameter. Figure 129 Uplink and downlink rate caps adjusted to apply aggregate cap For example, in the SM, if you set the Sustained Uplink Data Rate parameter to 2,000 kbps and the Sustained Downlink Data Rate parameter to 10,000 kbps, then the uplink and downlink MIR that is enforced for the SM can be calculated as shown in Figure 130. Figure 130 Uplink and downlink rate cap adjustment example

`

In this example case, the derived 1,167-kbps uplink and 5,833-kbps downlink MIR sum to the fixed 7,000-kbps aggregate cap of the SM. Committed Information Rate (CIR) The Committed Information Rate (CIR) capability feature enables the service provider to guarantee to any subscriber that bandwidth will never decrease to below a specified minimum unless CIR is oversubscribed or RF conditions are degraded. CIR is oversubscribed when there is not enough available bandwidth to support CIR configuration for all subscribers. In this condition, SMs which are configured with a nonzero CIR will all operate at the maximum data rate supported by the link

(subject to Maximum Information Rate and Burst Rate/Allocations). SMs which are configured with a CIR of 0 kbps will not transmit until CIR-configured SMs have completed transmission. CIR may be configured independently for high priority traffic and for low priority traffic. CIR parameters may be configured in the following ways:

Web-based management GUI SNMP Authentication Server (RADIUS) - when a SM successfully registers and authenticates, CIR information is retrieved from the RADIUS server. Page 7-260 uplink cap enforced =uplink entry x aggregate cap for the SMuplink entry + downlink entrydownlink cap enforced =downlink entry x aggregate cap for the SMuplink entry + downlink entryuplink cap enforced =2,000 kbps x 7,000 kbps2,000 kbps + 10,000 kbps= 1,167 kbpsdownlink cap enforced =10,000 kbps x 7,000 kbps2,000 kbps + 10,000 kbps= 5,833 kbps Chapter 7: Configuration Configuring quality of service Active CIR configuration can be verified via the APs Home > Session Status page. Bandwidth from the SM Perspective In the SM, normal web browsing, e-mail, small file transfers and short streaming video are rarely rate limited with practical bandwidth management (QoS) settings. When the SM processes large downloads such as software upgrades and long streaming video or a series of medium-size downloads, the bucket rapidly drains, the burst limit is reached, and some packets are delayed. The subscriber experience is more affected in cases where the traffic is more latency sensitive. Interaction of Burst Allocation and Sustained Data Rate Settings If the Burst Allocation is set to 1200 kb and the Sustained Data Rate is set to 128 kbps, a data burst of 1000 kb is transmitted at full speed because the Burst Allocation is set high enough. After the burst, the bucket experiences a significant refill at the Sustained Data Rate. This configuration uses the advantage of the settable Burst Allocation. If both the Burst Allocation and the Sustained Data Rate are set to 128 kb, a burst is limited to the Burst Allocation value. This configuration does not take advantage of the settable Burst Allocation. If the Burst Allocation is set to 128 kb and the Sustained Data Rate is set to 256 kbps, the actual rate is the burst allocation (but in kbps). As above, this configuration does not take advantage of the settable Burst Allocation. High-priority Bandwidth To support low-latency traffic such as VoIP (Voice over IP) or video, the system implements a high-

priority channel. This channel does not affect the inherent latencies in the system but allows high-

priority traffic to be immediately served. The high-priority pipe separates low-latency traffic from traffic that is latency tolerant, such as standard web traffic and file downloads. The number of channels available on the AP is reduced by the number of SMs configured for the high-priority channel (each SM operating with high-priority enabled uses two channels (virtual circuits) instead of one). A module prioritizes traffic by reading the Low Latency bit (Bit 3) in the IPv4 Type of Service (ToS) byte in a received packet. Bit 3 is set by a device outside the system. reading the 802.1p field of the 802.1Q header in a received packet, where VLAN is enabled on the module. comparing the 6-bit Differentiated Services Code Point (DSCP) field in the ToS byte of a received packet to a corresponding value in the Diffserv tab of the Configuration page of the module. A packet contains no flag that indicates whether the encoding is for the Low Latency bit or the DSCP field. For this reason, you must ensure that all elements in your trusted domain, including routers and endpoints, set and read the ToS byte with the same scheme. Modules monitor ToS bytes with DSCP fields, but with the following differences:

The 6-bit length of the field allows it to specify one of 64 service differentiations. Page 7-261 Chapter 7: Configuration Configuring quality of service These correlate to 64 individual (CodePoint) parameters in the Diffserv tab of the Configuration page. Per RFC 2474, 3 of these 64 are preset and cannot be changed. (See http://www.faqs.org/rfcs/rfc1902.html.) For any or all of the remaining 61 CodePoint parameters, you can specify a value of o 0 through 3 for low-priority handling. o 4 through 7 for high-priority handling. Note Ensure that your Differentiated Services domain boundary nodes mark any entering packet, as needed, so that it specifies the appropriate Code Point for that traffic and domain. This prevents theft of service level. An example of the Diffserv page in the Configuration menu and parameter descriptions are provided under DiffServ attributes AP/BHM on page 7-131. This tab and its rules are identical from module type to module type. However, any of the 61 configurable Code Points can be set to a different value from module to module, thus defining unique per-hop behavior for some traffic. This tab in the AP sets the priorities for the various packets in the downstream (sent from the public network). This tab in the SM sets the priorities for the various packets in the upstream (sent to the public network). Typically, some SMs attach to older devices that use the ToS byte as originally formatted, and others to newer devices that use the DSCP field. The default values in the Diffserv page allow your modules to prioritize traffic from the older devices roughly the same as they traditionally have. However, these default values may result in more high-priority traffic as DSCP fields from the newer devices are read and handled. So, after making changes in the Diffserv page, carefully monitor the high-priority channel for high packet rates in SMs that you have identified as those to initially set and watch. across your network when you have broadly implemented Code Point values, such as via SNMP. Page 7-262 Chapter 7: Configuration Traffic Scheduling Configuring quality of service The characteristics of traffic scheduling in a sector are summarized in Table 152. Table 152 Characteristics of traffic scheduling Category Factor Throughput Aggregate throughput, less additional overhead Latency Number of frames required for the scheduling process Round-trip latency Treatment 132 Mbps 1 6 ms AP broadcast the download schedule No High-priority Allocation for uplink high-priority traffic Dynamic, based on amount of high-

Channel on amount of high-priority traffic priority traffic Allocation for downlink high-priority traffic Dynamic, based on amount of high-

on amount of high-priority traffic priority traffic Order of transmission CIR high-priority CIR low-priority Other high-priority Other low-priority Caution Power requirements affect the recommended maximums for power cord length feeding the CMM4. See the dedicated user guide that supports the CMM that you are deploying. Packets that have a priority of 4 to 7 in either the DSCP or a VLAN 802.1p tag are automatically sent on the high-priority channel, but only where the high-priority channel is enabled. Page 7-263 Chapter 7: Configuration Configuring quality of service Setting the Configuration Source The AP includes a Configuration Source parameter, which sets where SMs that register to the AP are controlled for MIR, CIR, VLAN, and the high-priority channel as follows. The Configuration Source parameter affects the source of:

all MIR settings:

o Sustained Uplink Data Rate o Uplink Burst Allocation o Max Burst Uplink Data Rate o Sustained Downlink Data Rate o Downlink Burst Allocation o Max Burst Downlink Data Rate all CIR settings:

o Low Priority Uplink CIR o Low Priority Downlink CIR o Hi Priority Uplink CIR o Hi Priority Downlink CIR all SM VLAN settings o Dynamic Learning o Allow Only Tagged Frames o VLAN Aging Timeout o Untagged Ingress VID o Management VID o VLAN Membership the Hi Priority Channel setting Table 153 Recommended combined settings for typical operations Most operators who must set this in this web page/tab in the AP to use parameter no authentication server Authentication Mode Configuration/ Security Disabled Configuration Source Configuration/ General SM Wireless Manager Authentication Mode Configuration/ Security Authentication Server

(Authentication Server) RADIUS AAA server Configuration Source Configuration/ General Authentication Server Authentication Mode Configuration/ Security RADIUS AAA Configuration Source Configuration/ General Authentication Server Page 7-264 Chapter 7: Configuration Configuring quality of service Table 154 Where feature values are obtained for a SM with authentication required Configuration Source Setting in the AP Values are obtained from MIR Values VLAN Values High Priority Channel State Authentication Authentication Authentication Authentication Server SM Server SM Server SM Server SM Authentication Authentication Authentication Authentication Server+SM Server Server, then SM Server, then SM Note HPC represents the Hi Priority Channel (enable or disable). Where Authentication Server, then SM is the indication, parameters for which Authentication Server does not send values are obtained from the SM. This is the case where the Authentication Server server is operating on a Authentication Server release that did not support the feature. This is also the case where the feature enable/disable flag in Authentication Server is set to disabled. The values are those previously set or, if none ever were, then the default values. Where Authentication Server is the indication, values in the SM are disregarded. Where SM is the indication, values that Authentication Server sends for the SM are disregarded. For any SM whose Authentication Mode parameter is not set to Authentication Required, the listed settings are derived as shown in Table 155. Table 155 MIR, VLAN, HPC, and CIR Configuration Sources, Authentication Disabled Configuration Source Setting in the AP Values are obtained from MIR Values VLAN Values High Priority CIR Values Channel State AP SM SM AP SM SM AP SM SM Authentication AP Server SM Authentication Server+SM SM SM Page 7-265 Chapter 7: Configuration Configuring quality of service Configuring Quality of Service (QoS) Quality of Service (QoS) page of AP The QoS page of AP is explained in Table 156. Table 156 QoS page attributes - AP Attribute Meaning Max Burst Uplink These parameters allow operators to specify the data rate at which a SM Data Rate is allowed to transmit (until burst allocation limit is reached) before being recharged at the Sustained Uplink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. Sustained Uplink Specify the rate that each SM registered to this AP is replenished with Data Rate credits for transmission. This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on page 7-259 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-261 Configuration Source on page 7-141 Uplink Burst Allocation Specify the maximum amount of data to allow each SM to transmit before being recharged at the Sustained Uplink Data Rate with credits to transmit more. See Maximum Information Rate (MIR) Parameters on page 7-259 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-261 Configuration Source on page 7-141 Page 7-266 Chapter 7: Configuration Configuring quality of service Max Burst Downlink These parameters allow operators to specify the data rate at which a SM Data Rate is allowed to transmit (until burst allocation limit is reached) before being recharged at the Sustained Downlink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. Sustained Downlink Specify the rate at which the AP is replenished with credits (tokens) for Data Rate transmission to each of the SMs in its sector. This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on page 7-259 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-261 Configuration Source on page 7-141 Downlink Burst Specify the maximum amount of data to allow the AP to transmit to any Allocation registered SM before the AP is replenished with transmission credits at the Sustained Downlink Data Rate. See Maximum Information Rate (MIR) Parameters on page 7-259 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-261 Configuration Source on page 7-141 Broadcast Downlink Broadcast Downlink CIR (Committed Information Rate, a minimum) CIR supports system designs where downlink broadcast is desired to have higher priority than other traffic. For many other system designs, especially typical internet access networks, leave the Broadcast Downlink CIR at the default. Broadcast Downlink CIR is closely related to the Broadcast Repeat Count parameter, which is settable in the Radio tab of the Configuration page in the AP: when the Broadcast Repeat Count is changed, the total of available bandwidth is also changed, since packets are being sent one, two, or three times, according to the setting in the Broadcast Repeat Count parameter. Priority Precedence Allows operator to decide if 802.1p or DiffServ priority bits must be used first when making priority decisions. PPPoE Control Operators may configure the SM to utilize the high priority channel for Message Priority PPPoE control messages. Configuring the SM in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the SM. Prioritize TCP ACK To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. Page 7-267 Chapter 7: Configuration Configuring quality of service Quality of Service (QoS) page of SM The QoS page of SM is explained in Table 157. Table 157 QoS page attributes - SM Attribute Meaning Sustained Uplink Specify the rate that this SM is replenished with credits for transmission. Data Rate This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on page 7-259 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-261 Configuration Source on page 7-141 Sustained Downlink Specify the rate at which the AP is replenished with credits (tokens) for Data Rate transmission to this SM. This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on Page 7-259 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-261 Configuration Source on page 7-141 Uplink Burst Allocation Specify the maximum amount of data to allow this SM to transmit before being recharged at the Sustained Uplink Data Rate with credits to transmit more. See Maximum Information Rate (MIR) Parameters on page 7-259 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-261 Page 7-268 Chapter 7: Configuration Configuring quality of service Configuration Source on page 7-141 Downlink Burst Specify the maximum amount of data to allow the AP to transmit to this Allocation SM before the AP is replenished at the Sustained Downlink Data Rate with transmission credits. See Maximum Information Rate (MIR) Parameters on page 7-259 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-261 Configuration Source on page 7-141 Max Burst Uplink These parameters allow operators to specify the data rate at which a SM Data Rate is allowed to transmit (until burst allocation limit is reached) before being recharged at the Sustained Uplink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. Max Burst Downlink These parameters allow operators to specify the data rate at which a SM Data Rate is allowed to transmit (until burst allocation limit is reached) before being recharged at the Sustained Downlink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. Enable Broadcast /

This parameter allows the operator to specify if Broadcast and Multicast Multicast Data Rate data is rate-limited. This data rate can be entered in Kbps or PPS

(Packets Per Second). Broadcast / Multicast This parameter allows the operator to specify a data rate at which Data Rate Broadcast and Multicast traffic is sent via the radio link. Low Priority Uplink This field indicates the minimum rate at which low priority traffic is sent CIR over the uplink (unless CIR is oversubscribed or RF link quality is degraded). Committed Information Rate (CIR) on page 7-260 Setting the Configuration Source on page 7-264 Low Priority Downlink CIR This field indicates the minimum rate at which low priority traffic is sent over the downlink (unless CIR is oversubscribed or RF link quality is degraded). Committed Information Rate (CIR) on page 7-260 Setting the Configuration Source on page 7-264 Hi Priority Channel See High-priority Bandwidth on page 7-261 Configuration Source on page 7-141 Hi Priority Uplink CIR This field indicates the minimum rate at which high priority traffic is sent over the uplink (unless CIR is oversubscribed or RF link quality is degraded). Committed Information Rate (CIR) on page 7-260 Setting the Configuration Source on page 7-264 Page 7-269 Chapter 7: Configuration Configuring quality of service Hi Priority Downlink This field indicates the minimum rate at which high priority traffic is sent CIR over the downlink (unless CIR is oversubscribed or RF link quality is degraded). Committed Information Rate (CIR) on page 7-260 Setting the Configuration Source on page 7-264 Priority Precedence Allows operator to decide if 802.1p or DiffServ priority bits must be used first when making priority decisions. PPPoE Control Operators may configure the SM to utilize the high priority channel for Message Priority PPPoE control messages. Configuring the SM in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the SM. Prioritize TCP ACK To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. This parameter, when enabled, can be particularly useful when running bi-direction FTP sessions over the link. If a link is primarily used for video surveillance, it is recommended to configure this parameter to Disabled. Quality of Service (QoS) page of BHM The QoS page of BHM is explained in Table 158. Table 158 QoS page attributes - BHM Attribute Meaning PPPoE Control Operators may configure the BHM to utilize the high priority channel for Message Priority PPPoE control messages. Configuring the BHM in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the BHS. Prioritize TCP ACK To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. This parameter, when enabled, can be particularly useful when running bi-direction FTP sessions over the link. If a link is primarily used for video surveillance, it is recommended to configure this parameter to Disabled. Page 7-270 Chapter 7: Configuration Configuring quality of service Quality of Service (QoS) page of BHS The QoS page of BHS is explained in Table 159. Table 159 QoS page attributes - BHS Attribute Meaning PPPoE Control Operators may configure the BHS to utilize the high priority channel for Message Priority PPPoE control messages. Configuring the BHS in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the BHS. Prioritize TCP ACK To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. This parameter, when enabled, can be particularly useful when running bi-direction FTP sessions over the link. If a link is primarily used for video surveillance, it is recommended to configure this parameter to Disabled. Page 7-271 Chapter 7: Configuration Installation Color Code Installation Color Code With this feature enabled on the AP and SM, operators may install and remotely configure SMs without having to configure matching color codes between the modules. While the SM is accessible for configuration from above the AP (for remote provisioning) and below the SM (for local site provisioning), no user data is passed over the radio link. When using the Installation Color Code feature, ensure that the SM is configured with the factory default Color Code configuration (Color Code 1 is 0, Color Code 2-10 set to 0 and Disable). The status of the Installation Color Code can be viewed on the AP Eval web GUI page, and when the SM is registered using the Installation Color Code the message SM is registered via ICC Bridging Disabled! is displayed in red on every SM GUI page. The Installation Color Code parameter is configurable without a radio reboot for both the AP and SM. If an SM is registered via Installation Color Code and the feature is then disabled, operators will need to reboot the SM or force it to reregister (i.e. using the Rescan APs functionality on the AP Eval page). Figure 131 Installation Color Code of AP Page 7-272 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66 Zero Touch Configuration Using DHCP Option 66 This feature allows an SM to get its configuration via DHCP option 66. This can be used for the initial configuration of an SM as well as managing the configuration of SMs on an ongoing basis. Here is how it works in brief:

When the SM boots up, if it is set to use DHCP client, it will send out a DHCP Discover packet which includes a request for DHCP Option 66. In case of a brand new SM out of the box, the DHCP Discover packet is sent out if the SM connects to an AP using Installation Color Code (ICC), even though DHCP client is not enabled in factory default config. An appropriately configured DHCP server will respond with a DHCP Offer and include a URL in response to the Option 66 request. The URL should point to the configuration file. The device will download the configuration file and apply it. The device will reboot automatically if needed. (Note: this requires rebootIfRequired flag to be added to the config file. See Creating a Golden config file on page 7-274. Configuration Steps Procedure 23 Zero Touch Configuration steps 1 Create the golden config file(s) 2 Host it on an TFTP/FTP/HTTP/HTTPS server 3 Configure the DHCP server to return the URL of the golden config file in option 66 When the SM boots up, it will get the URL for the golden config from the DHCP server via option 66, download it and apply it. If all the SMs are configured exactly the same, then you can create just new golden config file that can be used with all SMs. If the SMs are not configured the same, see if it is possible to group the SMs such that SMs with the same configuration are served by the same DHCP pool. User can then create multiple golden config files and configure the DHCP server to use the appropriate config file for each pool. User can also create one config file per SM. This provides the most flexibility, but is practical only if you have a software tool/script to generate the config files for each MAC address. The files should be named <mac>.cfg where <mac> is the MAC address of the SM, and stored in the same directory on the file server. The DHCP server should be configured to return the directory name ending with a / in option 66. The SM will automatically add <mac>.cfg to the path and get its config file. Page 7-273 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66 If some configuration is unique per SM, but rest of the configuration is common, the SMs can be staged with the unique part, and use option 66 to manage the common part. For example, if each SM needs to have its coordinates set, dont include the coordinates in the golden config file. Instead, configure the coordinates for each SM manually. Manage the rest of the configuration using DHCP option 66. Creating a Golden config file The easiest way to create the golden config file is to configure an SM, export its configuration and edit it. To export the configuration file from the GUI of the SM, go to Configuration > Unit Settings tab, go to the Download Configuration File section and click on the <mac>.cfg link. This will give you a text file in JSON format. You can edit this file in a text editor but its easier to use a JSON editor like https://www.jsoneditoronline.org/. Strip down the config file to remove sections and entries that dont care about, and keep only the items that require changes. If there are many required changes, it can easily get confusing. To identify the exact items changes, first reset the SM to factory default, export the config file, make the necessary changes, export a second config file, then use a tool like WinMerge

(http://winmerge.org/) to identify the differences. The config file contains the following informational entries at the top level.

"cfgUtcTimestamp": "cfgUtcTimestamp",

"swVersion": "CANOPY 13.3 (Build 15) SM-AES",

"cfgFileString": "Canopy configuration file",

"srcMacAddress": "0a-00-3e-a2-c2-74",

"deviceType": "5.4/5.7GHz MIMO OFDM - Subscriber Module",

"cfgFileVersion": "1.0"

The cfgUtcTimestamp, swVersion, srcMacAddress and deviceType lines can be deleted. Do not delete the cfgFileString and cfgFileVersion entries. Next, create an object named configFileParameters at the top level. Under that, add a parameter called rebootIfRequired and set it to true. This tells the SM to reboot automatically if a reboot is needed to apply the new configuration. A sample configuration file that has been edited for use via DHCP option 66 is given below.

{

"userParameters": {

"smNetworkConfig": {

"networkAccess": 1

},

"location": {

"siteName": "Test site"

},

"smRadioConfig": {

Page 7-274 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66

"frequencyScanList": [

5475000, 5480000

],

"colorCodeList": [

{

"colorCode": 42,

"priority": 1

}

]

},

"networkConfig": {

"lanDhcpState": 1

}

},

"cfgFileVersion": "1.0",

"cfgFileString": "Canopy configuration file",

"configFileParameters": {

"rebootIfRequired": true

}

}

When configuration is imported, only the items that exist in the configuration file are modified. Parameters that are not in the imported file are not changed. If user wish to revert those settings to their factory default values, please add a setToDefaults item under configFileParameters section with a value of true.

"cfgFileVersion": "1.0",

"cfgFileString": "Canopy configuration file",

"configFileParameters": {

"rebootIfRequired": true,

"setToDefaults": true

}

In case, the SM needs to fetch the configuration file on each boot up even when not connecting to AP via ICC, set Network Accessibility to Public and DHCP State to Enabled in the Configuration > IP page before exporting the configuration. Hosting the config file Copy the golden configuration file to an FTP, TFTP, HTTP or HTTPS server. This location can be password protected; you just have to include the user name and password in the URL. DHCP server configuration Configure DHCP server to return the full URL to the golden config file as the value of DHCP option 66. Page 7-275 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66 The following example explains how to make the change for Windows Server 2008. Adapt it to your specific DHCP server. Procedure 24 DHCP server configuration 1 Click Start > Administrative Tools > DHCP 2 If you have multiple Scopes defined, identify the correct Scope that will serve IP addresses for the SMs 3 Right click on Scope Option under the correct Scope and select Configure Options Page 7-276 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66 4 In the Scope Options dialog, scroll down to 066 Boot Server Host Name, select the checkbox and enter the full URL to the golden config file as the String value. Then click OK. 5 In the DHCP snap-in window, right click and Refresh to see the DHCP option 66 in the list of DHCP options Supported URL Formats FTP, TFTP, HTTP and HTTPS URLs are supported. Some examples are given below. ftp://10.120.163.253/canopy.cfg ftp://admin:admin123@10.120.163.253/canopy.cfg (login as admin with password admin123) tftp://10.120.163.253/canopy.cfg http://10.120.163.253/golden-config.cfg https://10.120.163.253/smconfig/golden-config.cfg User can also specify the URL pointing to a directory and not a specific file. Terminate the URL with a / to indicate that it is a directory and not a file. Use this format when each SM has its own individual config file. The directory should contain files named <mac>.cfg, one for each SM. For example:

ftp://10.120.163.253/smconfig/

Page 7-277 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66 In this case, the SM will append <mac>.cfg to the path and try to get that file. For example, if the SMs MAC address is 0a-00-3e-a2-c2-74, it will request for ftp://10.120.163.253/smconfig/0a003ea2c274.cfg. This mechanism can be used to serve individual config file for each SM. Troubleshooting 1 Ensure that te SM is running 13.3 or newer version of software. 2 If the SM has factory default config, confirm ICC is enabled on the AP, so the SM can connect to it. 3 If the SM is connecting to the AP using a color code other than ICC, make sure the SM has Network Accessibility set to Public and DHCP State set to Enabled in the Configuration > IP page. 4 Make sure the golden config file does not turn off Network Accessibility or DHCP State. If it does, the SM will no longer request the config file when it is rebooted. 5 Check the event log of the SM to see the status of the configuration file import including any errors that prevented it from importing the file. 6 Capture the DHCP Offer packet from the DHCP server to the SM and verify that Option 66 has the expected URL. Page 7-278 Chapter 7: Configuration Configuring Radio via config file Configuring Radio via config file The PMP/PTP 450 platform supports export and import of a configuration file from the AP or SM as a text file. The configuration file is in JSON format. To export or import the configuration file, the logged in user needs to be an ADMINISTRATOR and it must not be a read-only account. The exported configuration file contains the complete configuration including all the default values. To keep a backup of the current configuration, the file can be saved as-is and imported later. While importing a configuration file, it can be either imported the full configuration or a sparse configuration containing only the items that need to be changed. If a sparse configuration file is imported, only the items in the file will be imported. Other configuration will remain unchanged. There could also be used a special flag in the configuration file to tell the device to apply the configuration starting from factory default (Refer Special Headers for configuration file on page 7-

280). Import and Export of config file The config file import and export is supported in Configuration > Unit Settings page. The procedure for importing and exporting config file is explained below. Figure 132 Configuration File upload and download page The DHCP server configuration procedure is as follows:

Procedure 25 DHCP server configuration 1 Login to the GUI and go to Configuration > Unit Settings. 2 Under Download Configuration File tab, click on the <mac>.cfg link, where <mac> is the MAC address of the device (for example, 01003ea2c274.cfg). 3 Save the file to the local disk. The below procedure is to be followed for Importing a config file Page 7-279 Chapter 7: Configuration Configuring Radio via config file Procedure 26 Import the configuration from the GUI 1 Login to the GUI and go to Configuration Unit Settings. 2 Click on Browse button under Upload and Apply Configuration File tab and select the configuration file from disk. 3 Click Upload followed by Apply Configuration File button click. 4 The Status of Configuration File section will show the results of the upload. 5 Review it to make sure there are no errors. Then click on Reboot to reboot with the imported configuration The special headers for config file is explained below:

Procedure 27 Special Headers for configuration file 1 A "configFileParameters" section can be added to the header to control the behaviour of the device when importing configuration. 2 The "setToDefaults" when set to "true" tell the device to reset to factory default configuration and apply the configuration in the file on top of that. So any attribute not in the configuration file will be set to its factory default value. By default, the configuration in the file is merged with the existing configuration on the device. The "rebootIfRequired" flag when set to "true" tell the device to reboot automatically if needed to apply the configuration change. By default, the device will not reboot automatically.

{

"cfgFileString": "Canopy configuration file",

"cfgFileVersion": "1.0",

"configFileParameters": {

"setToDefaults":true,

"rebootIfRequired":true,

}

}

Page 7-280 Chapter 7: Configuration Configuring a RADIUS server Configuring a RADIUS server Configuring a RADIUS server in a PMP 450 platform network is optional, but can provide added security, increase ease of network management and provide usage-based billing data. Understanding RADIUS for PMP 450 platform PMP 450 platform modules include support for the RADIUS (Remote Authentication Dial In User Service) protocol supporting Authentication and Accounting. RADIUS Functions RADIUS protocol support provides the following functions:

SM Authentication allows only known SMs onto the network (blocking rogue SMs), and can be configured to ensure SMs are connecting to a known network (preventing SMs from connecting to rogue APs). RADIUS authentication is used for SMs, but is not used for APs. SM Configuration: Configures authenticated SMs with MIR (Maximum Information Rate), CIR

(Committed Information Rate), High Priority, and VLAN (Virtual LAN) parameters from the RADIUS server when a SM registers to an AP. SM Accounting provides support for RADIUS accounting messages for usage-based billing. This accounting includes indications for subscriber session establishment, subscriber session disconnection, and bandwidth usage per session for each SM that connects to the AP. Centralized AP and SM user name and password management allows AP and SM usernames and access levels (Administrator, Installer, Technician) to be centrally administered in the RADIUS server instead of on each radio and tracks access events

(logon/logoff) for each username on the RADIUS server. This accounting does not track and report specific configuration actions performed on radios or pull statistics such as bit counts from the radios. Such functions require an Element Management System (EMS) such as Cambium Networks Wireless Manager. This accounting is not the ability to perform accounting functions on the subscriber/end user/customer account. Framed IP allows operators to use a RADIUS server to assign management IP addressing to SM modules (framed IP address). Tested RADIUS Servers The Canopy RADIUS implementation has been tested and is supported on FreeRADIUS, Version 2.1.8 Aradial RADIUS, Version 5.1.12 Microsoft RADIUS (Windows Server 2012 R2 version) Cisco ACS, Version 5.7.0.15 Page 7-281 Chapter 7: Configuration Configuring a RADIUS server Note Aradial 5.3 has a bug that prevents remote device login, so doesnt support the user name and password management feature. Choosing Authentication Mode and Configuring for Authentication Servers - AP On the APs Configuration > Security tab, select the RADIUS AAA Authentication Mode. The following describes the other Authentication Mode options for reference, and then the RADIUS AAA option. Disabled: Requires no authentication. Any SM (except a SM that itself has been configured to require RADIUS authentication by enabling Enforce Authentication as described below) is allowed to register to the AP. Authentication Server: Authentication Server in this instance refers to Wireless Manager in BAM-only mode. Authentication is required for a SM to register to the AP. Only SMs listed by MAC address in the Wireless Manager database is allowed to register to the AP. AP Pre-Shared Key: Canopy offers a pre-shared key authentication option. In this case, an identical key must be entered in the Authentication Key field on the APs Configuration >

Security tab and in the Authentication Key field on each desired SMs Configuration >

Security tab. RADIUS AAA: To support RADIUS authentication of SMs, on the APs Configuration >

Security tab select RADIUS AAA. Only properly configured SMs with a valid certificate is allowed to register to the AP. When RADIUS AAA is selected, up to 3 Authentication Server (RADIUS Server) IP addresses and Shared Secrets can be configured. The IP address(s) configured here must match the IP address(s) of the RADIUS server(s). The shared secret(s) configured here must match the shared secret(s) configured in the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not splitting the database. If Server 1 doesnt respond, Server 2 is tried, and then server 3. If Server 1 rejects authentication, the SM is denied entry to the network, and does not progress trying the other servers. The default IP address is 0.0.0.0. The default Shared Secret is CanopySharedSecret. The Shared Secret can be up to 32 ASCII characters (no diacritical marks or ligatures, for example). Page 7-282 Chapter 7: Configuration Configuring a RADIUS server Table 160 Security tab attributes Page 7-283 Chapter 7: Configuration Configuring a RADIUS server Attribute Meaning Authentication Mode Operators may use this field to select the following authentication modes:

Disabledthe AP requires no SMs to authenticate. Authentication Server the AP requires any SM that attempts registration to be authenticated in Wireless Manager before registration. AP PreShared Key - The AP acts as the authentication server to its SMs and will make use of a user-configurable pre-shared authentication key. The operator enters this key on both the AP and all SMs desired to register to that AP. There is also an option of leaving the AP and SMs at their default setting of using the Default Key. Due to the nature of the authentication operation, if you want to set a specific authentication key, then you MUST configure the key on all of the SMs and reboot them BEFORE enabling the key and option on the AP. Otherwise, if you configure the AP first, none of the SMs is able to register. RADIUS AAA - When RADIUS AAA is selected, up to 3 Authentication Server (RADIUS Server) IP addresses and Shared Secrets can be configured. The IP address(s) configured here must match the IP address(s) of the RADIUS server(s). The shared secret(s) configured here must match the shared secret(s) configured in the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not for splitting the database. If Server 1 doesnt respond, Server 2 is tried, and then server 3. If Server 1 rejects authentication, the SM is denied entry to the network and does not progress trying the other servers. Authentication Server DNS Usage The management DNS domain name may be toggled such that the name of the authentication server only needs to be specified and the DNS domain name is automatically appended to that name. Authentication Server 1 Authentication Server 2 Authentication Server 3 Enter the IP address or server name of the authentication server

(RADIUS or WM) and the Shared Secret configured in the authentication server. When Authentication Mode RADIUS AAA is selected, the default value of Shared Secret is CanopySharedSecret. The Shared Secret Authentication may consist of up to 32 ASCII characters. Server 4 (BAM Only) Authentication Server 5 (BAM Only) Radius Port This field allows the operator to configure a custom port for RADIUS server communication. The default value is 1812. Authentication Key The authentication key is a 32-character hexadecimal string used when Authentication Mode is set to AP Pre-Shared Key. By default, this key is set to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF. Page 7-284 Chapter 7: Configuration Configuring a RADIUS server Selection Key This option allows operators to choose which authentication key is used:

Use Key above means that the key specified in Authentication Key is used for authentication Use Default Key means that a default key (based off of the SMs MAC address) is used for authentication Encryption Key Specify the type of airlink security to apply to this AP. The encryption setting must match the encryption setting of the SMs. None provides no encryption on the air link. DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. SM Display of AP You can use this field to suppress the display of data about this AP on Evaluation Data the AP Evaluation tab of the Tools page in all SMs that register. Web, Telnet, FTP Enter the expiry in seconds for remote management sessions via HTTP, Session Timeout telnet, or ftp access to the AP. IP Access Control You can permit access to the AP from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address Allowed Source IP 1 If you selected IP Access Filtering Enabled for the IP Access Control parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the AP from any IP address. You may populate as many as all three. Allowed Source IP 2 If you selected IP Access Filtering Disabled for the IP Access Control Allowed Source IP 3 parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. Web Access The Radio supports secured and non-secured web access protocols. Select suitable web access from drop down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https1://<IP of Radio>. Page 7-285 Chapter 7: Configuration Configuring a RADIUS server HTTP and HTTPS If enabled, the radio can be accessed via both http and https. SNMP This option allows to configure SNMP agent communication version. It can be selected from drop down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. Telnet FTP TFTP This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. Page 7-286 Chapter 7: Configuration Configuring a RADIUS server SM Authentication Mode Require RADIUS or Follow AP If it is desired that a SM will only authenticate to an AP that is using RADIUS, on the SMs Configuration Security tab set Enforce Authentication to AAA. With this enabled, SM does not register to an AP that has any Authentication Mode other than RADIUS AAA selected. If it is desired that a SM use the authentication method configured on the AP it is registering to, set Enforce Authentication to Disabled. With Enforce Authentication disabled, a SM will attempt to register using whichever Authentication Mode is configured on the AP it is attempting to register to. Note Having SMs to use RADIUS by enabling Enforce Authentication avoids the security issue of SMs possibly registering to rogue APs, which have authentication disabled. Table 161 SM Security tab attributes Page 7-287 Chapter 7: Configuration Configuring a RADIUS server Attribute Meaning Authentication Key Authentication Mode is set to AP PreShared Key. By default, this key is The authentication key is a 32-character hexadecimal string used when set to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF. This option allows operators to choose which authentication key is used:

Use Key above means that the key specified in Authentication Key is Select Key used for authentication Use Default Key means that a default key (based off of the SMs MAC address) is used for authentication The SM may enforce authentication types of AAA and AP Pre-

Enforce sharedKey. The SM will not finish the registration process if the AP is not Authentication using the configured authentication method (and the SM locks out the AP for 15 minutes). Enforce Authentication default setting is Disable. The protocols supported for the Phase 1 (Outside Identity) phase of authentication are EAPTTLS (Extensible Authentication Protocol Tunneled Transport Layer Security) or MSCHAPv2 (Microsoft Challenge-Handshake Authentication Protocol version 2). Select the desired Phase 2 (Inside Identity) authentication protocol from the Phase 2 options of PAP (Password Authentication Protocol), CHAP

(Challenge Handshake Authentication Protocol), and MSCHAP

(Microsofts version of CHAP, version 2 is used). The protocol must be consistent with the authentication protocol configured on the RADIUS server. Phase 1 Phase 2 Page 7-288 Chapter 7: Configuration Configuring a RADIUS server Identity/Realm Username If Realms are being used, select Enable Realm and configure an outer identity in the Identity field and a Realm in the Realm field. These must match the Phase 1/Outer Identity and Realm configured in the RADIUS server. The default Identity is anonymous. The Identity can be up to 128 non-special (no diacritical markings) alphanumeric characters. The default Realm is canopy.net. The Realm can also be up to 128 non-

special alphanumeric characters. Configure an outer Identity in the Username field. This must match the Phase 1/Outer Identity username configured in the RADIUS server. The default Phase 1/Outer Identity Username is anonymous. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. Enter a Username for the SM. This must match the username configured for the SM on the RADIUS server. The default Username is the SMs MAC address. The Username can be up to 128 non-special

(no diacritical markings) alphanumeric characters. Password Enter the desired password for the SM in the Password and Confirm Password fields. The Password must match the password configured for the SM on the RADIUS server. The default Password is password. Confirm Password The Password can be up to 128 non-special (no diacritical markings) alphanumeric characters. Upload Certificate File To upload a certificate manually to a SM, first load it in a known place on your PC or network drive, then click on a Delete button on one of the Certificate description blocks to delete a certificate to provide space for your certificate. Click on Choose File, browse to the location of the certificate, and click the Import Certificate button, and then reboot the radio to use the new certificate. When a certificate is in use, after the SM successfully registers to an AP, an indication of In Use will appear in the description block of the certificate being used. The public certificates installed on the SMs are used with the private certificate on the RADIUS server to provide a public/private key encryption system. Up to 2 certificates can be resident on a SM. An installed certificate can be deleted by clicking the Delete button in the certificates description block on the Configuration > Security tab. To restore the 2 default certificates, click the Use Default Certificates button in the RADIUS Certificate Settings parameter block and reboot the radio. Page 7-289 Chapter 7: Configuration Configuring a RADIUS server Specify the type of airlink security to apply to this AP. The encryption setting must match the encryption setting of the SMs. None provides no encryption on the air link. DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of Encryption Setting data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. Web, Telnet, FTP Enter the expiry in seconds for remote management sessions via HTTP, Session Timeout telnet or ftp access to the AP. If you want to prevent any device that is connected to the Ethernet port of the SM from accessing the management interface of the SM, select Ethernet Access Disabled. This selection disables access through this port to via HTTP (the GUI), SNMP, telnet, FTP, and TFTP. With this selection, management access is available through only the RF interface Ethernet Access via either an IP address (if Network Accessibility is set to Public on the SM) or the Session Status or Remote Subscribers tab of the AP.. See IP Access Control below. If you want to allow management access through the Ethernet port, select Ethernet Access Enabled. This is the factory default setting for this parameter. You can permit access to the AP from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses IP Access Control that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address Allowed Source IP 1 If you selected IP Access Filtering Enabled for the IP Access Control Allowed Source IP 2 parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the AP from any IP address. You may populate as many as all three. Allowed Source IP 3 If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. Web Access The Radio supports secured and non-secured web access protocols. Select suitable web access from drop down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. Page 7-290 Chapter 7: Configuration Configuring a RADIUS server HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. SNMP This option allows to configure SNMP agent communication version. It can be selected from drop down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. Telnet FTP TFTP This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. SM - Phase 1 (Outside Identity) parameters and settings The protocols supported for the Phase 1 (Outside Identity) phase of authentication are eapttls (Extensible Authentication Protocol Tunneled Transport Layer Security) and eapMSChapV2 (Extensible Authentication Protocol Microsoft Challenge-Handshake Authentication Protocol). Configure an outer Identity in the Username field. This must match the Phase 1/Outer Identity username configured in the RADIUS server. The default Phase 1/Outer Identity Username is anonymous. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. If Realms are being used in the RADIUS system (eapttls only), select Enable Realm and configure an outer identity in the Identity field and a Realm in the Realm field. These must match the Phase 1/Outer Identity and Realm configured in the RADIUS server. The default Identity is anonymous. The Identity can be up to 128 non-special (no diacritical markings) alphanumeric characters. The default Realm is canopy.net. The Realm can also be up to 128 non-

special alphanumeric characters. SM - Phase 2 (Inside Identity) parameters and settings If using eapttls for Phase 1 authentication, select the desired Phase 2 (Inside Identity) authentication protocol from the Phase 2 options of PAP (Password Authentication Protocol), CHAP (Challenge Handshake Authentication Protocol), and MSCHAPv2 (Microsofts version of CHAP). The protocol must be consistent with the authentication protocol configured on the RADIUS server. Enter a Username for the SM. This must match the username configured for the SM on the RADIUS server. The default Username is the SMs MAC address. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. Enter the desired password for the SM in the Password and Confirm Password fields. The Password must match the password configured for the SM on the RADIUS server. The default Password is password. The Password can be up to 128 non-special (no diacritical markings) alphanumeric characters. Page 7-291 Chapter 7: Configuration Configuring a RADIUS server Handling Certificates Managing SM Certificates via the SM GUI The default public Canopy certificates are loaded into SMs upon factory software installation. The default certificates are not secure and are intended for use during lab and field trials as part of gaining experience with the RADIUS functionalities or as an option during debug. For secure operation, an operator will want to create or procure their own certificates. Resetting a SM to its factory defaults will remove the current certificates and restore the default certificates. Up to two certificates can be resident on a SM. An installed certificate can be deleted by clicking the Delete button in the certificates description block on the Configuration > Security tab. To restore the 2 default certificates, click the Use Default Certificates button in the RADIUS Certificate Settings parameter block and reboot the radio. To upload a certificate manually to a SM, first load it in a known place on your PC or network drive, then click on a Delete button on one of the Certificate description blocks to delete a certificate to provide space for your certificate. Click on Choose File, browse to the location of the certificate, and click the Import Certificate button, and then reboot the radio to use the new certificate. When a certificate is in use, after the SM successfully registers to an AP, an indication of In Use will appear in the description block of the certificate being used. The public certificates installed on the SMs are used with the private certificate on the RADIUS server to provide a public/private key encryption system. Note Root certificates of more than one level (Example - a certificate from someone who received their CA from Verisign) fails. Certificates must be either root or self-signed. Page 7-292 Chapter 7: Configuration Configuring a RADIUS server Figure 133 SM Certificate Management Configuring RADIUS servers for SM authentication Your RADIUS server must be configured to use the following:

EAPTTLS or MSCHAPv2 as the Phase 1/Outer Identity protocol. If Enable Realm is selected on the SMs Configuration > Security tab, then the same Realm appears there (or access to it). The same Phase 2 (Inner Identity) protocol as configured on the SMs Configuration >

Security tab under Phase 2 options. The username and password for each SM configured on each SMs Configuration > Security tab. An IP address and NAS shared secret that is the same as the IP address and Shared Secret configured on the APs Configuration > Security tab for that RADIUS server. Page 7-293 Chapter 7: Configuration Configuring a RADIUS server A server private certificate, server key, and CA certificate that complement the public certificates distributed to the SMs, as well as the Canopy dictionary file that defines Vendor Specific Attributes (VSAa). Default certificate files and the dictionary file are available from the software site: https://support.cambiumnetworks.com/files/pmp450 after entering your name, email address, and either Customer Contract Number or the MAC address of a module covered under the 12 month warranty. Optionally, operators may configure the RADIUS server response messages (Accept or Reject) so that the user has information as to why they have been rejected. The AP displays the RADIUS Authentication Reply message strings in the Session Status list as part of each SMs information. The SM will show this string (listed as Authentication Response on the SM GUI) on the main Status page in the Subscriber Module Stats section. Note Aradial AAA servers only support operator-configurable Authentication Accept responses, not Authentication Reject responses. Page 7-294 Chapter 7: Configuration Configuring a RADIUS server Assigning SM management IP addressing via RADIUS Operators may use a RADIUS AAA server to assign management IP addressing to SM modules

(framed IP address). SMs now interpret attributes Framed-IP-Address, Framed-IP-Netmask, and Cambium-Canopy-Gateway from RADIUS. The RADIUS dictionary file has been updated to include the Cambium-Canopy-Gateway attribute and is available on the Cambium Software Support website. In order for these attributes to be assigned and used by the SM, the following must be true:

The system is configured for AAA authentication The SM is not configured for DHCP on its management interface. If DHCP is enabled and these attributes are configured in the RADIUS server, the attributes is ignored by the SM. The SM management interface must be configured to be publically accessible. If the SM is configured to have local accessibility, the management interface will still be assigned the framed addressing, and the SM iscome publicly accessible via the assigned framed IP addressing. When using these attributes, for the addressing to be implemented by the SM operators must configure Framed-IP-Address in RADIUS. If Framed-IP-Address is not configured but Framed-

IP-Netmask and/or Cambium-Canopy-Gateway is configured, the attributes is ignored. In the case where only the Framed-IP-Address is configured, Framed-IP-Netmask defaults to 255.255.0.0 (NAT disabled) / 255.255.255.0 (NAT enabled) and Cambium-Canopy-Gateway defaults to 0.0.0.0. Configuring RADIUS server for SM configuration Canopy Vendor Specific Attributes (VSAs) along with VSA numbers and other details are listed in Table 162. The associated SM GUI page, tab and parameter are listed to aid cross-referencing and understanding of the VSAs. A RADIUS dictionary file is available from the software site:

https://support.cambiumnetworks.com/files/pmp450 The RADIUS dictionary file defines the VSAs and their values and is usually imported into the RADIUS server as part of server and database setup. Page 7-295 Chapter 7: Configuration Configuring a RADIUS server Note Beginning with System Release 12.0.2, two RADIUS dictionary files are available on the Cambium website RADIUS Dictionary file Cambium and RADIUS Dictionary file Motorola. In addition to a renaming of attributes, the Cambium-branded dictionary file contains two new VSAs for controlling uplink and downlink Maximum Burst Data Rate (these VSAs are listed below in Table 162). If you are transitioning from the Motorola-branded dictionary file to the Cambium-

branded dictionary file, ensure that all RADIUS profiles containing Motorola-Canopy attribute references are updated to include Cambium-Canopy attribute references (for all applicable VSAs listed in Table 162). Also, ensure that all RADIUS configuration files reference the new dictionary file (as an alternative, operators may rename the Cambium-branded dictionary file to the filename currently in use by the RADIUS server). Once the profiles are updated and the new Cambium-branded dictionary file is installed on the RADIUS server, restart the RADIUS server to ensure that the new VSAs and attribute names are enabled. Table 162 RADIUS Vendor Specific Attributes (VSAs) Name MS-MPPE-Send-Key

*

-

MS-MPPE-Recv-Key

*

-

Number Type Required Value 26.311.16

-

26.311.17

-

Y Y

-

-

-

-

Cambium-Canopy-LPULCIR 26.161.1 integer N 0-65535 kbps

-

-

Configuration > Quality of Service > Low Priority Uplink CIR 0 kbps 32 bits Cambium-Canopy-LPDLCIR 26.161.2 integer N 0-65535 kbps Configuration > Quality of Service > Low Priority Downlink CIR 0 kbps 32 bits Cambium-Canopy-HPULCIR 26.161.3 integer N 0-65535 kbps Configuration > Quality of Service > Hi Priority Uplink CIR 0 kbps 32 bits Cambium-Canopy-HPDLCIR 26.161.4 integer N 0-65535 kbps Configuration > Quality of Service > Hi Priority Uplink CIR 0 kbps 32 bits Cambium-Canopy-HPENABLE 26.161.5 integer N 0-disable, 1-enable Configuration > Quality of Service > Hi Priority Channel 0 32 bits Enable/Disable 26.161.6 integer N 0-100000 kbps Page 7-296 Chapter 7: Configuration Configuring a RADIUS server Configuration > Quality of Service > Sustained Uplink Data Rate dependent on radio 32 bits feature set Cambium-Canopy-ULBL 26.161.7 integer N 0-2500000 kbps Configuration > Quality of Service > Uplink Burst Allocation dependent on radio 32 bits feature set Cambium-Canopy-DLBR 26.161.8 integer N 0-100000 kbps Configuration > Quality of Service > Sustained Downlink Data dependent on radio 32 bits Rate feature set Cambium-Canopy-DLBL 26.161.9 integer N 0-2500000 kbps Configuration > Quality of Service > Downlink Burst Allocation dependent on radio 32 bits feature set Cambium-Canopy-

26.161.14 integer N 0-disable, 1-enable VLLEARNEN Configuration > VLAN > Dynamic Learning 1 32 bits Cambium-Canopy-

26.161.15 integer N 0-all, 1-tagged, 2-

VLFRAMES Configuration > VLAN > Allow Frame Types untagged 0 32 bits Cambium-Canopy-VLIDSET 26.161.16 integer N VLAN Membership Configuration > VLAN Membership

(1-4094) 0 32 bits Cambium-Canopy-VLAGETO 26.161.20 integer N 5 - 1440 minutes Configuration > VLAN > VLAN Aging Timeout 25 mins 32 bits Cambium-Canopy-VLIGVID 26.161.21 integer N 1 4094 Configuration > VLAN > Default Port VID 1 32 bits Cambium-Canopy-VLMGVID 26.161.22 integer N 1 4094 Configuration > VLAN > Management VID 1 32 bits Cambium-Canopy-

VLSMMGPASS 26.161.23 integer N 0-disable, 1-enable Configuration > VLAN > SM Management VID Pass-through 1 32 bits Cambium-Canopy-BCASTMIR 26.161.24 integer N 0-100000 kbps, 0=disabled Configuration > Quality of Service > Broadcast/Multicast Uplink dependent on radio 32 bits Data Rate feature set Cambium-Canopy-Gateway 26.161.25 ipaddr N

-

Configuration > IP > Gateway IP Address 0.0.0.0

-

Page 7-297 Chapter 7: Configuration Configuring a RADIUS server Cambium-Canopy-ULMB 26.161.26 integer N 0-100000 kbps Configuration > Quality of Service > Max Burst Uplink Data 0 32 bits Rate Cambium-Canopy-DLMB 26.161.27 integer N 0-100000 kbps Configuration > Quality of Service > Max Burst Downlink Data 0 32 bits Rate Cambium-Canopy-UserLevel 26.161.50 integer N 1-Technician, 2-

Installer, 3-

Administrator Account > Add User > Level 0 32 bits

(*) Contains key for encrypting packets sent by the NAS to the remote host (for Microsoft Point-

to-Point Encryption Protocol). Note VSA numbering:

26 connotes Vendor Specific Attribute, per RFC 2865 26.311 is Microsoft Vendor Code, per IANA Configuring RADIUS server for SM configuration using Zero Touch feature The RADIUS VSA (Vendor Specific Attributes) is updated for Zero Touch feature. This feature enables the ability for a SM to get its configuration via RADIUS VSA. The RADIUS VSA is updated for an URL which points to the configuration file of SM (see Table 162 for list of VSA). The RADIUS will push the vendor specific attribute to SM after successful authentication. The VSA contains URL of config file which will redirect SM to download configuration. If there is any change in SM confirmation, the SM will reboot automatically after applying the configuration. The RADIUS VSA attributes concerning Zero Touch are as follows:

VSA Type String Cambium-Canopy-ConfigFileImportUrl (29) string Maximum Length 127 characters. Cambium-Canopy-ConfigFileExportUrl (30) string Maximum Length 127 characters. The updated RADIUS dictionary can be downloaded from below link:

https://support.cambiumnetworks.com/files/pmp450/

Page 7-298 Chapter 7: Configuration Configuring a RADIUS server Note The feature is not applicable to the AP. Using RADIUS for centralized AP and SM user name and password management AP Technician/Installer/Administrator Authentication To control technician, installer, and administrator access to the AP from a centralized RADIUS server:

Procedure 28 Centralized user name and password management for AP 1 2 Set Authentication Mode on the APs Configuration > Security tab to RADIUS AAA Set User Authentication Mode on the APs Account > User Authentication tab (the tab only appears after the AP is set to RADIUS authentication) to Remote or Remote then Local. Local: The local SM is checked for accounts. No centralized RADIUS accounting

(access control) is performed. Remote: Authentication by the centralized RADIUS server is required to gain access to the SM if the SM is registered to an AP that has RADIUS AAA Authentication Mode selected. For up to 2 minutes a test pattern is displayed until the server responds or times out. Remote then Local: Authentication using the centralized RADIUS server is attempted. If the server sends a reject message, then the setting of Allow Local Login after Reject from AAA determines if the local user database is checked or not. If the configured servers do not respond within 2 minutes, then the local user database is used. The successful login method is displayed in the navigation column of the SM. Figure 134 User Authentication and Access Tracking tab of the AP Page 7-299 Chapter 7: Configuration Configuring a RADIUS server Table 163 AP User Authentication and Access Tracking attributes Attribute Meaning User Authentication Mode Local: The local SM is checked for accounts. No centralized RADIUS accounting (access control) is performed. Remote: Authentication by the centralized RADIUS server is required to gain access to the AP. For up to 2 minutes a test pattern is displayed until the server responds or times out. Remote then Local: Authentication using the centralized RADIUS server is attempted. If the server sends a reject message, then the setting of Allow Local Login after Reject from AAA determines if the local user database is checked or not. If the configured servers do not respond within 2 minutes, then the local user database is used. The successful login method is displayed in the navigation column of the AP. User Authentication The user authentication method employed by the radios is EAP-MD5. Method Allow Local Login after If a user authentication is rejected from the AAA server, the user is Reject from AAA allowed to login locally to the radios management interface. Radius Accounting The destination port on the AAA server used for Radius accounting Port communication. disable no accounting messages are sent to the RADIUS server deviceAccess accounting messages are sent to the RADIUS server Accounting Messages regarding device access (see Table 165). dataUsage accounting messages are sent to the RADIUS server regarding data usage (see Table 165). Page 7-300 Chapter 7: Configuration Configuring a RADIUS server Accounting Data Usage Interval The interval for which accounting data messages are sent from the radio to the RADIUS server. If 0 is configured for this parameter, no data usage messages are sent. SM Re-authentication The interval for which the SM will re-authenticate to the RADIUS server. Interval SM Technician/Installer/Administrator Authentication The centralized user name and password management for SM is same as AP. Follow AP Technician/Installer/Administrator Authentication on page 7-299 procedure. Note Remote access control is enabled only after the SM registers to an AP that has Authentication Mode set to RADIUS AAA. Local access control will always be used before registration and is used after registration if the AP is not configured for RADIUS. Figure 135 User Authentication and Access Tracking tab of the SM Page 7-301 Chapter 7: Configuration Configuring a RADIUS server Table 164 SM User Authentication and Access Tracking attributes Attribute Meaning User Authentication Mode Local: The local SM is checked for accounts. No centralized RADIUS accounting (access control) is performed. Remote: Authentication by the centralized RADIUS server is required to gain access to the SM if the SM is registered to an AP that has RADIUS AAA Authentication Mode selected. For up to 2 minutes a test pattern is displayed until the server responds or times out. Remote then Local: Authentication using the centralized RADIUS server is attempted. If the server sends a reject message, then the setting of Allow Local Login after Reject from AAA determines if the local user database is checked or not. If the configured servers do not respond within 2 minutes, then the local user database is used. The successful login method is displayed in the navigation column of the SM. If a user authentication is rejected from the AAA server, the user is allowed to login locally to the radios management interface. It is applicable ONLY when the User Authentication Mode is set to Remote Allow Local Login after Reject from AAA then Local. Note When the radio User Authentication Mode is set to Local or Remote, the Allow Local Login after Reject from AAA does not any effect. disable no accounting messages are sent to the RADIUS server deviceAccess accounting messages are sent to the RADIUS server regarding device access (see Table 165). Accounting Messages Page 7-302 Chapter 7: Configuration Access Tracking Configuring a RADIUS server To track logon and logoff times on individual radios by technicians, installers, and administrators, on the AP or SMs Account > User Authentication and Access Tracking tab under Accounting (Access Tracking) set Accounting Messages to deviceAccess. Device Access Tracking is enabled separately from User Authentication Mode. A given AP or SM can be configured for both, either, or neither. RADIUS Device Data Accounting PMP 450 systems include support for RADIUS accounting messages for usage-based billing. This accounting includes indications for subscriber session establishment, subscriber session disconnection, and bandwidth usage per session for each SM that connects to the AP. The attributes included in the RADIUS accounting messages are shown in the table below. Table 165 Device data accounting RADIUS attributes Sender Message Attribute Value Description AP Accounting-

Acct-Status-Type 1 - Start Request Unique per AP session. Initial value is SM MAC, and Acct-Session-Id increments after every start message sent of an in session SM. UTC time the event occurred on the AP Event-Timestamp Acct-Status-Type 2 - Stop Unique per AP session. Initial value is SM MAC, and Acct-Session-Id increments after every start AP Accounting-

Request Acct-Input-Octets message sent of an in session SM. Sum of the input octets received at the SM over regular data VC and the high priority data VC (if enabled). Will not include broadcast. Sum of the output octets sent from the SM over This message is sent every time a SM registers with an AP, and after the SM stats are cleared. This message is sent every time a SM becomes unregistered with an AP, and when the SM stats are cleared. Acct-Output-Octets regular data VC and the high priority data VC (if enabled). Page 7-303 Chapter 7: Configuration Configuring a RADIUS server Sender Message Attribute Value Description Acct-Input-

Gigawords Acct-Output-

Gigawords Number of times the Acct-

Input-Octets counter has wrapped around 2^32 over the course of the session Number of times the Acct-

Output-Octets counter has wrapped around 2^32 over the course of the session Sum of unicast and multicast packets that are sent to a particular SM over Acct-Input-Packets the regular data VC and the high priority data VC (if enabled). It will not include broadcast. Sum of unicast and multicast packets that are Acct-Output-

sent from a particular SM Packets over the regular data VC and the high priority data VC (if enabled). Acct-Session-Time Uptime of the SM session. Acct-Terminate-

Reason code for session Cause termination AP Accounting-

Acct-Status-Type 3 - Interim-Update Request Unique per AP session. Initial value is SM MAC, and Acct-Session-Id increments after every start This message is sent periodically per the operator configuration on the AP in seconds. message sent of an in session SM. Interim update Sum of the input octets sent counts are to the SM over regular data cumulative over Acct-Input-Octets VC and the high priority the course of the data VC (if enabled). Will session not include broadcast. Sum of the output octets set from the SM over Acct-Output-Octets regular data VC and the high priority data VC (if enabled). Page 7-304 Chapter 7: Configuration Configuring a RADIUS server Sender Message Attribute Value Description Acct-Input-

Gigawords Acct-Output-

Gigawords Number of times the Acct-

Input-Octets counter has wrapped around 2^32 over the course of the session Number of times the Acct-

Output-Octets counter has wrapped around 2^32 over the course of the session Acct-Session-Time Uptime of the SM session. Sum of unicast and multicast packets that are sent to a particular SM over Acct-Input-Packets the regular data VC and the high priority data VC (if enabled). It will not include broadcast. Sum of unicast and multicast packets that are Acct-Output-

sent from a particular SM Packets over the regular data VC and the high priority data VC (if enabled). The data accounting configuration is located on the APs Accounts > User Authentication and Access Tracking GUI menu, and the APs Authentication Mode must be set to Radius AAA for the menu to appear. The accounting may be configured via the AP GUI as shown in the figures below. By default accounting messages are not sent and the operator has the choice of configuring to send only Device Access accounting messages (when a user logs in or out of the radio), only Data Usage messages, or both. When Data Accounting is enabled, the operator must specify the interval of when the data accounting messages are sent (0 disabled, or in the range of 30-10080 minutes). The default interval is 30 minutes. Figure 136 RADIUS accounting messages configuration Page 7-305 Chapter 7: Configuration Configuring a RADIUS server The data accounting message data is based on the SM statistics that the AP maintains, and these statistics may be cleared on the AP by an operator. If an operator clears these messages and data accounting is enabled, an accounting stop message is sent followed by an accounting start message to notify the AAA of the change. If an operator clears the VC statistics on the device through the management GUI, a RADIUS stop message and data start message is issued for each device affected. The start and stop messages will only be sent once every 5 minutes, so if an operator clears these statistics multiple times within 5 minutes, only one set of data stop/start messages is sent. This may result in inaccurate data accumulation results. RADIUS Device Re-authentication PMP 450 platform systems include support for periodic SM re-authentication in a network without requiring the SM to re-register (and drop the session). The re-authentication may be configured to occur in the range of every 30 minutes to weekly. Figure 137 Device re-authentication configuration The re-authentication interval is only configurable on the AP. When this feature is enabled, each SM that enters the network will re-authenticate each the interval time has expired without dropping the session. The response that the SM receives from the AAA server upon re-

authentication is one of the following:

Success: The SM continues normal operation Reject: The SM de-registers and will attempt network entry again after 1 minute and then if rejected will attempt re-entry every 15 minutes Timeout or other error: The SM remains in session and attempt 5 times to re-authenticate with the RADIUS-REQUEST message. If these attempts fail, then the SM will go out of session and proceed to re-authenticate after 5 minutes, then every 15 minutes. Although re-authentication is an independent feature, it was designed to work alongside with the RADIUS data usage accounting messages. If a user is over their data usage limit the network operator can reject the user from staying in the network. Operators may configure the RADIUS Reply-Message attribute with an applicable message (i.e. Data Usage Limit Reached) that is sent to the subscriber module and displayed on the general page. Page 7-306 Chapter 7: Configuration Configuring a RADIUS server RADIUS Change of Authorization and Disconnect Message Prior to this feature, SM will get configuration parameters from a RADIUS server during authentication process. This feature allows an administrator to control configuration parameters in the SM while SM is in session. The configuration changes in SM are done using RADIUS Change of Authorization method (RFC 3576) on the existing RADIUS authentication framework for AP and SM. A typical use case could be changing the QOS parameters after a certain amount of bandwidth usage by a SM. Figure 138 RADIUS CoA configuration for AP The RADIUS CoA feature enables initiating a bi-directional communication from the RADIUS server(s) to the AP and SM. The AP listens on UDP port 3799 and accepts CoA requests from the configured RADIUS servers. This CoA request should contain SM MAC address in User-Name attribute as identifier and all other attributes which control the SM config parameters. For security reasons, a timestamp also needs to be added as Event-Timestamp attribute. Hence the time should also be synchronized between the RADIUS server(s) and the AP to fit within a window of 300 seconds. Once the configuration changes are applied on the SM, CoA-ACK message is sent back to RADIUS server. If the validation fails, the AP sends a CoA-NACK response to the RADIUS server with proper error code. A Disconnect-Message is sent by the RADIUS server to NAS in order to terminate a user session on a NAS and discard all associated session context. It is used when the authentication AAA server wants to disconnect the user after the session has been accepted by the RADIUS. In response of Disconnect-Request from RADIUS server, the NAS sends a Disconnect-ACK if all associated session context is discarded, or a Disconnect-NACK, if the NAS is unable to disconnect the session. Note The RADIUS CoA feature will only enabled if Authentication mode is set to RADIUS AAA. Page 7-307

 

 

Chapter 7: Configuration Configuring a RADIUS server Microsoft RADIUS support This feature allows to configure Microsoft RADIUS (Network Policy and Access Services a.k.a NPS) as Authentication server for SM and User authentication. For SM Authentication, SM will user PEAP-MSCHAPv2 since NPS doesn't support TTLS protocol. For User Authentication, the Canopy software will use EAP-MD5 but the user has to do certain configuration in order to enable EAP-MD5 on NPS. Note All this configuration has been tested on Windows Server 2012 R2 version. This feature is not supported on hardware board type P9 or lower platforms. SM Authentication Configuration There are no new configuration on AP. However SM has to be configured for PEAP authentication protocol. 1. 2. Go to Configuration > Security page Select eappeap for Phase 1 attribute under tab AAA Authentication Settings. Figure 139 EAPPEAP settings The Phase 2 will change automatically to MSCHAPv2 on select of Phase 1 attribute as EAP-PEAP. Other parameters of Phase 2 protocols like PAP/CHAP will be disabled. Import Certificate The SM certificate has to be imported to Windows Server for certificate authentication. 1. 2. Copy the certificate which is configured in SM under Configuration > Security -> Certificate1 to Windows Server machine. Right click and select 'Install Certificate'. This will install the certificate and it's ready for use. This certificate will be used while configuring PEAP-MSCHAPv2 in NPS. Page 7-308 Chapter 7: Configuration Configuring a RADIUS server NPS Configuration (https://technet.microsoft.com/en-us/network/bb545879.aspx) Following items should be configured in NPS Console:

RADIUS Client o https://technet.microsoft.com/en-us/library/cc732929 Connection Request Policies o https://technet.microsoft.com/en-us/library/cc730866 o Choose 'Wireless-Other' in NAS-Port-Type Network Policy o https://technet.microsoft.com/en-us/library/cc755309 o Choose 'Wireless-Other' in NAS-Port-Type. o While configuring PEAP, select the above imported certificate. Figure 140 Importing certificate in NPS User Authentication Configuration As mentioned earlier, Microsoft has deprecated the support for MD5 from versions of Windows. To enable MD5, the following steps to be followed:

1. Follow the instructions:

https://support.microsoft.com/en-us/kb/922574/en-us?wa=wsignin1.0 Optionally, the registry file can be downloaded. It can be installed by double-click it in Windows Registry. From NPS Console Network Policy > <Policy Name> > Properties > Constrains >

Authentication Method and click Add. Select MD5 and click OK. 2. Page 7-309 Chapter 7: Configuration Configuring a RADIUS server Figure 141 Selecting MD5 from NPS console Next open 'Active Directory Users and Computers' and create user. Make sure user property is configured as shown below. Figure 142 User configuration Page 7-310 Chapter 7: Configuration Configuring a RADIUS server Before using VSA, the Cambium-Canopy-UserLevel(50) VSA must be configured with some access level say ADMIN(3), Follow below link for configuring VSA:

https://technet.microsoft.com/en-us/library/cc731611 The Cambiums vendor code is 161. Figure 143 RADIUS VSA configuration User can enable accounting in NPS under NPS Console > Accounting >

Configure Accounting. For more details refer https://technet.microsoft.com/library/dd197475 Page 7-311 Chapter 7: Configuration Configuring a RADIUS server Cisco ACS RADIUS Server Support This briefly explains how to configure CIsco ACS RADIUS server for PEAP-MSCHAPv2 authentication. The configuration had been tested on CISCO ACS Version : 5.7.0.15 Adding RADIUS client Figure 144 Adding RADIUS client Creating Users Figure 145 Creating users Page 7-312 Chapter 7: Configuration Configuring a RADIUS server Creating RADIUS instance Figure 146 Creating RADIUS instance RADIUS protocols Figure 147 RADIUS protocols Page 7-313 Chapter 7: Configuration Service selection Figure 148 Service selection Adding Trusted CA Figure 149 Adding Trusted CA Configuring a RADIUS server Note that certificate has to be in DER form, so if you have in PEM format convert using openssl. openssl.exe x509 -in <path-to->/cacert_aaasvr.pem -outform DER -out <path-

to>/cacert_aaasvr.der Installing Server Certificate After installing trusted CA, you need to add a server certificate which will be used for TLS tunnel.Generally you have to install same certificate which is installed in your AP, so that AP can trust the radius server. Figure 150 Installing Server Certificate Page 7-314 Chapter 7: Configuration Monitoring Logs Figure 151 Mornitoring logs Configuring a RADIUS server Configuring VSA Before using VSA , user has to add Cambium Vendor Specific Attribute Navigate to System Administration > Configuration > Dictionaries > Protocols > RADIUS > RADIUS VSA > Motorola If Motorola is not present you can create Vendor with ID 161 Add all the VSA one by one Page 7-315 Chapter 7: Configuration Figure 152 VSA list Configuring a RADIUS server Using VSA for users Navigate to Access Policies > Access Services > Cambium ACS > Authorization 1. Change condition to User name Page 7-316 Chapter 7: Configuration Configuring a RADIUS server 2. Next click Create and then click Select see diagram below 3. Click Create from the screen you get following screen Chose some name and then move to RADIUS Attributes tab 4. Fill attribute which all you want for that particular user Important: Click Add for each attribute and when done click Submit. Page 7-317 Chapter 7: Configuration Configuring a RADIUS server 5. Now you are ready to use this Authorization profile for the use Select and Press OK 6. Finally press Save Changes and you are ready to use it. Page 7-318 Chapter 8: Tools The AP and SM GUIs provide several tools to analyze the operating environment, system performance and networking, including:

Using Spectrum Analyzer tool on page 8-2 Using the Alignment Tool on page 8-15 Using the Link Capacity Test tool on page 8-21 Using AP Evaluation tool on page 8-27 Using BHM Evaluation tool on page 8-31 Using the OFDM Frame Calculator tool on page 8-35 Using the Subscriber Configuration tool on page 8-39 Using the Link Status tool on page 8-40 Using BER Results tool on page 8-45 Using the Sessions tool on page 8-46 Page 8-1 Chapter 8: Tools Using Spectrum Analyzer tool Using Spectrum Analyzer tool The integrated spectrum analyzer can be very useful as a tool for troubleshooting and RF planning, but is not intended to replicate the accuracy and programmability of a high-end spectrum analyzer, which sometime can be used for other purposes. The AP/BHM and SM/BHS perform spectrum analysis together in the Sector Spectrum Analyzer tool. Caution On start of the Spectrum Analyzer on a module, it enters a scan mode and drops any RF connection it may have had. When choosing Start Timed Spectrum Analysis, the scan is run for the amount of time specified in the Duration configuration parameter. When choosing Start Continuous Spectrum Analysis, the scan is run continuously for 24 hours, or until stopped manually (using the Stop Spectrum Analysis button). Any module can be used to see the frequency and power level of any detectable signal that is within, just above, or just below the frequency band range of the module. Note Vary the days and times when you analyze the spectrum in an area. The RF environment can change throughout the day or throughout the week. Mapping RF Neighbor Frequencies The neighbor frequencies can be analyzed using Spectrum Analyzer tool. Following modules allow user to:

Use a BHS or BHM for PTP and SM or AP for PMP as a Spectrum Analyzer. View a graphical display that shows power level in RSSI and dBm at 5 MHz increments throughout the frequency band range, regardless of limited selections in the Custom Radio Frequency Scan Selection List parameter of the SM/BHS. Select an AP/BHM channel that minimizes interference from other RF equipment. Caution The following procedure causes the SM/BHS to drop any active RF link. If a link is dropped when the spectrum analysis begins, the link can be re-established when either a 15 minute interval has elapsed or the spectrum analyzer feature is disabled. Page 8-2 Chapter 8: Tools Using Spectrum Analyzer tool Temporarily deploy a SM/BHS for each frequency band range that need to monitor and access the Spectrum Analyzer tab in the Tools web page of the module. Using Spectrum Analyzer tool Using the Remote Spectrum Analyzer tool Spectrum Analyzer tool Analyzing the spectrum To use the built-in spectrum analyzer functionality of the AP/SM/BH, proceed as follows:

Procedure 29 Analyzing the spectrum 1 2 3 4 5 6 7 8 Predetermine a power source and interface that works for the AP/SM/BH in the area to be analyzed. Take the AP/SM/BH, power source and interface device to the area. Access the Tools web page of the AP/SM/BH. Enter Duration in Timed Spectrum Analyzer Tab. Default value is 10 Seconds Click Start Timed Sector Spectrum Analysis The results are displayed:

Figure 153 Spectrum analysis - Results Note AP/SM/BH scans for extra 40 seconds in addition to configured Duration Travel to another location in the area to BHS. Click Start Timed Spectrum Analysis Page 8-3 Chapter 8: Tools Using Spectrum Analyzer tool 9 Repeat Steps 4 and 6 until the area has been adequately scanned and logged. As with any other data that pertains to your business, a decision today to put the data into a retrievable database may grow in value to you over time. Note Wherever the operator find the measured noise level is greater than the sensitivity of the radio that is plan to deploy, use the noise level (rather than the link budget) for your link feasibility calculations. The AP/SM/BH perform spectrum analysis together in the Sector Spectrum Analyzer feature. Graphical spectrum analyzer display The AP/SM/BH display the graphical spectrum analyzer. An example of the Spectrum Analyzer page is shown in Figure 153. The navigation feature includes:

Results may be panned left and right through the scanned spectrum by clicking and dragging the graph left and right Results may be zoomed in and out using mouse When the mouse is positioned over a bar, the receive power level, frequency, maximum and mean receive power levels are displayed above the graph To keep the displayed data current, either set Auto Refresh on the modules Configuration >

General. Spectrum Analyzer page of AP The Spectrum Analyzer page of AP is explained in Table 166. Page 8-4 Chapter 8: Tools Table 166 Spectrum Analyzer page attributes - AP Using Spectrum Analyzer tool Attribute Meaning Display Data Path Both means that the vertical and horizontal paths are displayed or an individual path may be selected to display only a single-path reading. Data For ease of parsing data and to facilitate automation, the spectrum analyzer results may be saved as an XML file. To save the results in an XML formatted file, right-click the SpectrumAnalysis.xml link and save the file. Display Instantaneous means that each reading (vertical bar) is displayed with two horizontal lines above it representing the max power level received

(top horizontal line) and the average power level received (lower horizontal line) at that frequency. Averaging means that each reading (vertical bar) is displayed with an associated horizontal line above it representing the max power level received at that frequency. Registered SM Count This field displays the MAC address and Site Name of the registered SM. Maximum Count of This field displays the maximum number of registered SMs. Registered SMs Page 8-5 Chapter 8: Tools Using Spectrum Analyzer tool Duration This field allows operators to configure a specified time for which the spectrum is scanned. If the entire spectrum is scanned prior to the end of the configured duration, the analyzer will restart at the beginning of the spectrum. Continuous Start Continuous Spectrum Analysis button ensures that when the SM is Spectrum Analyzer powered on, it automatically scans the spectrum for 10 seconds. These results may then be accessed via the Tools > Spectrum Analyzer GUI page. Spectrum Analyzer page of SM The Spectrum Analyzer page of SM is explained in Table 167. Table 167 Spectrum Analyzer page attributes - SM Page 8-6 Chapter 8: Tools Using Spectrum Analyzer tool Attribute Meaning Display Data Path Refer Table 166 on page 8-5 Data Display Refer Table 166 on page 8-5 Refer Table 166 on page 8-5 Min and Max To scan min to max range of frequencies, enter min and max Frequencies in KHz frequencies in KHz and press Set Min and Max to Full Scan button. To scan +/- 40 MHz from center frequency, enter center frequency in KHz and press Set Min And Max To Center Scan +/- 40KHz button. Registered SM Count Refer Table 166 on page 8-5 Maximum Count to Refer Table 166 on page 8-5 Registered SMs Duration Refer Table 166 on page 8-5 Spectrum Analyzer page of BHM The Spectrum Analyzer page of BHM is explained in Table 168. Page 8-7 Chapter 8: Tools Table 168 Spectrum Analyzer page attributes - BHM Using Spectrum Analyzer tool Attribute Meaning Data Display Refer Table 166 on page 8-5 Refer Table 166 on page 8-5 Duration Refer Table 166 on page 8-5 Continuous Refer Table 166 on page 8-5 Spectrum Analyzer Page 8-8 Chapter 8: Tools Using Spectrum Analyzer tool Spectrum Analyzer page of BHS The Spectrum Analyzer page of BHS is explained in Table 169. Table 169 Spectrum Analyzer page attributes - BHS Attribute Meaning Data Display Refer Table 166 on page 8-5 Refer Table 166 on page 8-5 Session Status This field displays current session status and rates. The session states can be Scanning, Syncing, Registering or Registered. Registered Backhaul This field displays MAC address of BHM and PTP model number Duration Refer Table 166 on page 8-5 Page 8-9 Chapter 8: Tools Using Spectrum Analyzer tool Perform Spectrum This field allows to Enable or Disable to start Spectrum Analysis on boot Analysis on Boot Up up of module for one scan. for one scan Continuous Refer Table 166 on page 8-5 Spectrum Analyzer Page 8-10 Chapter 8: Tools Using Spectrum Analyzer tool Spectrum Analyzer page result of PMP 450 SM Figure 154 Spectrum Analyzer page result PMP 450 SM Page 8-11 Chapter 8: Tools Remote Spectrum Analyzer tool Using Spectrum Analyzer tool The Remote Spectrum Analyzer tool in the AP/BHM provides additional flexibility in the use of the spectrum analyzer in the SM/BHS. Set the duration of 10 to 1000 seconds, then click the Start Remote Spectrum Analysis button to launch the analysis from that SM/BHS. In PMP configuration, a SM has to be selected from the drop-down list before launching Start Remote Spectrum Analysis. Analyzing the spectrum remotely Procedure 30 Remote Spectrum Analyzer procedure 1 2 3 4 The AP/BHM de-registers the target SM/BHS. The SM/BHS scans (for the duration set in the AP/BHM tool) to collect data for the bar graph. The SM/BHS re-registers to the AP/BHM. The AP/BHM displays the bar graph. The bar graph is an HTML file, but can be changed to an XML file, which is then easy to analyze through the use of scripts that you may write for parsing the data. To transform the file to XML, click the SpectrumAnalysis.xml link below the spectrum results. Although the resulting display appears mostly unchanged, the bar graph is now coded in XML. You can now right-click on the bar graph for a Save Target As option to save the Spectrum Analysis.xml file. Remote Spectrum Analyzer page of AP The Remote Spectrum Analyzer page of AP is explained in Table 170. Page 8-12 Chapter 8: Tools Table 170 Remote Spectrum Analyzer attributes - AP Using Spectrum Analyzer tool Attribute Meaning Registered SM Count This field displays the number of SMs that were registered to the AP before the SA was started. This helps the user know all the SMs re-

registered after performing a SA. Maximum Count of This field displays the largest number of SMs that have been Registered SMs simultaneously registered in the AP since it was last rebooted. This count can provide some insight into sector history and provide comparison between current and maximum SM counts at a glance. Current Subscriber The SM with which the Link Capacity Test is run. Module Duration This field allows operators to configure a specified time for which the spectrum is scanned. If the entire spectrum is scanned prior to the end of the configured duration, the analyzer will restart at the beginning of the spectrum. Scanning Bandwidth This parameter defines the size of the channel scanned when running the analyzer. Page 8-13 Chapter 8: Tools Using Spectrum Analyzer tool Remote Spectrum Analyzer page of BHM The Remote Spectrum Analyzer page of BHM is explained in Table 171. Table 171 Remote Spectrum Analyzer attributes - BHM Attribute Duration Meaning Refer Table 166 on page 8-5 Page 8-14 Chapter 8: Tools Using the Alignment Tool Using the Alignment Tool The SMs or BHSs Alignment Tool may be used to maximize Receive Power Level, Signal Strength Ratio and Signal to Noise Ratio to ensure a stable link. The Tool provides color coded readings to facilitate in judging link quality. Note To get best performance of the link, the user has to ensure the maximum Receive Power Level during alignment by pointing correctly. The proper alignment is important to prevent interference in other cells. The achieving Receive Power Level green (>- 70 dBm) is not sufficient for the link. Figure 155 Alignment Tool tab of SM Receive Power Level > -70 dBm Figure 156 Alignment Tool tab of SM Receive Power Level between -70 to -80 dBm Figure 157 Alignment Tool tab of SM Receive Power Level < -80 dBm Page 8-15 Chapter 8: Tools Using the Alignment Tool Aiming page and Diagnostic LED SM/BHS The SMs/BHSs Alignment Tool (located in GUI Tools -> Aiming) may be used to configure the SMs/BHSs LED panel to indicate received signal strength and to display decoded beacon information/power levels. The SM/BHS LEDs provide different status based on the mode of the SM/BHS. A SM/BHS in operating mode will register and pass traffic normally. A SM/BHS in aiming mode will not register or pass traffic, but will display (via LED panel) the strength of received radio signals (based on radio channel selected via Tools ->Aiming).. See SM/BHS LEDs on page 2-13. Note In order for accurate power level readings to be displayed, traffic must be present on the radio link. Refer Table 19 SM/BHS LED descriptions on page 2-14 for SM/BHS LED details. Aiming page of SM The Aiming page is similar to Spectrum Analyzer where it scans the spectrum but it does not establish any session with any Aps. It has two modes Single Frequency Only and Normal Frequency Scan List. The Aiming page of SM is explained in Table 172. Page 8-16 Chapter 8: Tools Table 172 Aiming page attributes SM Using the Alignment Tool Attribute Meaning Aiming Mode Single Frequency Only: scans only selected single frequency. Normal Frequency Scan List: scans: scans all frequency of scan list. Single Frequency Select a particular frequency from drop down menu for scanning. Scan Radio Enabled: the radio is configured to aiming or alignment mode, Frequency Only wherein the LED panel displays an indication of receive power level. See Mode Table 19 SM/BHS LED descriptions on page 2-14. Disabled: the radio is configured to operating mode, wherein the SM registers and passes traffic normally. Aiming Results The Aiming Results are displayed in two sections Current entry and Other entries. Frequency: this field indicates the frequency of the AP which is transmitting the beacon information. Page 8-17 Chapter 8: Tools Using the Alignment Tool Power: This field indicates the current receive power level (vertical channel) for the frequency configured in parameter Radio Frequency. Users: This field indicates the number of SMs currently registered to the AP which is transmitting the beacon information. ESN: This field indicates the MAC, or hardware address of the AP/BHM which is transmitting the beacon information. Color Code: This field displays a value from 0 to 254 indicating the APs configured color code. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Multipoint or Backhaul: this field indicates type of configuration - point-

Multipoint(PMP) or Backhaul(PTP). Page 8-18 Chapter 8: Tools Aiming page of BHS The Alignment page of BHS is explained in Table 173. Table 173 Aiming page attributes - BHS Using the Alignment Tool Attribute Meaning Refer Table 161 for Atributes details. Page 8-19 Chapter 8: Tools Alignment Tone Using the Alignment Tool For coarse alignment of the SM/BHS, use the Alignment Tool located at Tools -> Alignment Tool. Optionally, connect a headset alignment tone kit to the AUX/SYNC port of the SM/BHS and listen to the alignment tone, which indicates greater SM/BHS receive signal power by pitch. By adjusting the SMs/BHSs position until the highest frequency pitch is obtained operators and installers can be confident that the SM/BHS is properly positioned. For information on device GUI tools available for alignment, see sections Aiming page and Diagnostic LED SM/BHS on page 8-16, Using the Link Capacity Test tool on page 8-21 and Using AP Evaluation tool on page 8-27. Figure 158 PMP/PTP 450i link alignment tone 450i Alignment tone adapter Headphones Note The Alignment Tone cable for a 450i uses an RJ-45 to headset cable where the 450 alignment tone cable uses an RJ-12 to headset cable. Page 8-20 Chapter 8: Tools Using the Link Capacity Test tool Using the Link Capacity Test tool The Link Capacity Test tab allows you to measure the throughput and efficiency of the RF link between two modules. Many factors, including packet length, affect throughput. The Link Capacity Test tool has following modes:

RF Link Test: Fully tests radio-to-radio communication, but does not bridge traffic. Link Test with Bridge: Bridges traffic to simulated Ethernet ports, providing a status of the bridged link. Link Test with Bridge and MIR: Bridges the traffic during test and also adheres to any MIR

(Maximum Information Rate) settings for the link. Extrapolated Link Test: Estimates the link capacity by sending few packets and measuring link quality. The Link Capacity Test tab contains the settable parameter Packet Length with a range of 64 to 1714 bytes. This allows you to compare throughput levels that result from various packet sizes. The Current Results Status also displayed date and time of last performed Link Capacity Test. If there is any change in time zone, the date and time will be adjusted accordingly. Figure 159 Link Capacity Test - AP Note The Extrapolated Link Test can be run by Read-Only login also.. Page 8-21 Chapter 8: Tools Using the Link Capacity Test tool Performing RF Link Test, Link Test with Bridge or Link Test with Bridge and MIR To run a simple link capacity test, perform the following procedure:

Procedure 31 Performing a simple Link Capacity Test 1 Access the Link Capacity Test tab in the Tools web page of the module. 2 Select Link Test Mode RF Link Test, Link Test with Bridge or Link Test with Bridge and MIR. 3 4 Set Signal to Noise Ratio Calculation during Link Test attribute to enable to disable. Set Link Test VC Priority attribute to either High and Low Priority VCs or Low Priority VC only. 5 Select the subscriber module to test using the Current Subscriber Module parameter. This parameter is not available in BHM. 6 7 8 Type into the Duration field how long (in seconds) the RF link must be tested. Select the Direction Bi-directional, Uplink Only or Downlink Only. Type into the Number of Packets field a value of 0 to flood the link for the duration of the test. 6 Type into the Packet Length field a value of 1714 to send 1714-byte packets during the 7 8 test. Click the Start Test button. In the Current Results Status block of this tab, view the results of the test. See Figure 160 on page 8-22. Figure 160 Link Capacity Test tab with 1714-byte packet length Page 8-22 Chapter 8: Tools Performing Extrapolated Link Test Using the Link Capacity Test tool The Extraploated Link Test estimates the link capacity by sending few packets and measuring link quality. Once the test is initiated, the radio starts session at the lower modulation, 1X, As traffic is passed sucessfuly across the link, the radio decides to try the next modulation, 2X. This process repeats until it find best throughput to estimate capacity of link. Note It is recommended to run Extrapolated Link Test where the session must have been up and have traffic present on it in order to get accurate test results. This is essentail for the radio to modulate up to get an accurate measurement. Running the Extrapolated test just after establishing session will not provide accurate results. The procedure for performing Extrapolated Link Test is as follows:

Procedure 32 Performing an Extrapolated Link Test 1 Access the Link Capacity Test tab in the Tools web page of the module. 2 Select Link Test Mode Extrapolated Link Test 3 Click the Start Test button. 4 In the Current Results Status block of this tab, view the results of the test. Page 8-23 Chapter 8: Tools Figure 161 Extrapolated Link Test results Using the Link Capacity Test tool Link Capacity Test page of AP The Link Capacity Test page of AP is explained in Table 174. Page 8-24 Chapter 8: Tools Table 174 Link Capacity Test page attributes AP Using the Link Capacity Test tool Attribute Meaning Select Link Test Mode from drop down menu :

RF Link Test Link Test Mode Link Test with Bridging Link Test with Bridging and MIR Extrapolated Link Test Signal to Noise Ratio Calculation during Link Test Link Test VC Priority Enable this attribute to display Signal-to-Noise information for the downlink and uplink when running the link test. This attribute may be used to enable/disable usage of the high priority virtual channel during the link test. Current Subscriber The SM with which the Link Capacity Test is run. This field is only Module applicable for AP (not SM page). Duration This field allows operators to configure a specified time for which the spectrum is scanned. If the entire spectrum is scanned prior to the end of the configured duration, the analyzer will restart at the beginning of the spectrum. Direction the test only in the corresponding direction only. Specific Bi-Directional Configure the direction of the link test. Specify Downlink or Uplink to run to run the test in both directions. Number of Packets The total number of packets to send during the Link Capacity Test. When Link Test Mode is set to RF Link Test this field is not configurable. Packet Length The size of the packets in Bytes to send during the Link Capacity Test Page 8-25 Chapter 8: Tools Using the Link Capacity Test tool Link Capacity Test page of BHM/BHS/SM The Link Capacity Test page of BHM/BHS is explained in Table 175. Table 175 Link Capacity Test page attributes BHM/BHS Attribute Meaning Link Test Mode See Table 174 on page 8-25 Signal to Noise Ratio Calculation during Link Test See Table 174 on page 8-25 Link Test VC Priority See Table 174 on page 8-25 Duration Direction See Table 174 on page 8-25 See Table 174 on page 8-25 Number of Packets See Table 174 on page 8-25 Packet Length See Table 174 on page 8-25 Page 8-26 Chapter 8: Tools Using AP Evaluation tool Using AP Evaluation tool The AP Evaluation tab on Tools web page of the SM provides information about the AP that the SM sees. Note The data for this page may be suppressed by the SM Display of AP Evaluation Data setting in the Configuration > Security tab of the AP. The AP Eval results can be accessed via SNMP and config file. AP Evaluation page of AP The AP Evaluation page of AP is explained in Table 176. Table 176 AP Evaluation tab attributes - AP Attribute Meaning Index This field displays the index value that the system assigns (for only this page) to the AP where this SM is registered. Frequency This field displays the frequency that the AP transmits. Channel Bandwidth The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the AP and the SM. Page 8-27 Chapter 8: Tools Using AP Evaluation tool Cyclic Prefix OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol to allow multi-

pathing to settle before receiving the desired data. A 1/16 cyclic prefixes mean that for every 16 bits of throughput data transmitted, an additional bit is used. The Cyclic Prefix 1/16 only can be selected at this time. ESN This field displays the MAC address (electronic serial number) of the AP. For operator convenience during SM aiming, this tab retains each detected ESN for up to 15 minutes. If the broadcast frequency of a detected AP changes during a 15-minute interval in the aiming operation, then a multiple instance of the same ESN is possible in the list. Eventually, the earlier instance expires and disappears and the later instance remains to the end of its interval, but you can ignore the early instance(s) whenever two or more are present. Region This field displays the APs configured Country Code setting. Power Level This field displays the SMs combined received power level from the APs transmission. Beacon Count A count of the beacons seen in a given time period. FECEn This field contains the SNMP value from the AP that indicates whether the Forward Error Correction feature is enabled. 0: FEC is disabled 1: FEC is enabled Type Age Multipoint indicates that the listing is for an AP. This is a counter for the number of minutes that the AP has been inactive. At 15 minutes of inactivity for the AP, this field is removed from the AP Evaluation tab in the SM. Lockout This field displays how many times the SM has been temporarily locked out of making registration attempts. RegFail Range This field displays how many registration attempts by this SM failed. This field displays the distance in feet for this link. To derive the distance in meters, multiply the value of this parameter by 0.3048. MaxRange This field indicates the configured value for the APs Max Range parameter. TxBER EBcast A 1 in this field indicates the AP is sending Radio BER. A 1 in this field indicates the AP or BHM is encrypting broadcast packets. A 0 indicates it is not. Page 8-28 Chapter 8: Tools Using AP Evaluation tool Session Count This field displays how many sessions the SM (or BHS) has had with the AP (or BHM). Typically, this is the sum of Reg Count and Re-Reg Count. However, the result of internal calculation may display here as a value that slightly differs from the sum. In the case of a multipoint link, if the number of sessions is significantly greater than the number for other SMs, then this may indicate a link problem or an interference problem. NoLUIDs This field indicates how many times the AP has needed to reject a registration request from a SM because its capacity to make LUID assignments is full. This then locks the SM out of making any valid attempt for the next 15 minutes. It is extremely unlikely that a non-zero number would be displayed here. OutOfRange This field indicates how many times the AP has rejected a registration request from a SM because the SM is a further distance away than the range that is currently configured in the AP. This then locks the SM out of making any valid attempt for the next 15 minutes. AuthFail This field displays how many times authentication attempts from this SM have failed in the AP. EncryptFail This field displays how many times an encryption mismatch has occurred between the SM and the AP. Rescan Req This field displays how many times a re-range request has occurred for the BHM that is being evaluated in the AP Eval page of a BHS. SMLimitReached This field displays 0 if additional SMs may be registered to the AP. If a 1 is displayed, the AP will not accept additional SM registrations. NoVCs This counter is incremented when the SM is registering to an AP which determines that no VC resources are available for allocation. This could be a primary data VC or a high priority data VC. VCRsvFail This counter is incremented when the SM is registering to an AP which has a VC resource available for allocation but cannot reserve the resource for allocation. VCActFail This counter is incremented when the SM is registering to an AP which has a VC resource available for allocation and has reserved the VC, but cannot activate the resource for allocation. AP Gain RcvT This field displays the total external gain (antenna) used by the AP. This field displays the APs configured receive target for receiving SM transmissions (this field affects automatic SM power adjust). Sector ID This field displays the value of the Sector ID field that is provisioned for the AP. Page 8-29 Chapter 8: Tools Using AP Evaluation tool Color Code This field displays a value from 0 to 254 indicating the APs configured color code. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). BeaconVersion This field indicates that the beacon is OFDM (value of 1). Sector User Count This field displays how many SMs are registered on the AP. NumULHalfSlots This is the number of uplink slots in the frame for this AP. NumDLHalfSlots This is the number of downlink slots in the frame for this. NumULContSlots This field displays how many Contention Slots are being used in the uplink portion of the frame. WhiteSched Flag to display if schedule whitening is supported via FPGA ICC This field lists the SMs that have registered to the AP with their Installation Color Code (ICC), Primary CC, Secondary CC or Tertiary CC. SM PPPoE This filed provides information to the user whether the SM is supporting PPPoE or not. Frame Period This field displays the configured Frame Period of the radio. Page 8-30 Chapter 8: Tools Using BHM Evaluation tool Using BHM Evaluation tool The BHM Evaluation tab on Tools web page of the BHS provides information about the BHM that the BHS sees. BHM Evaluation page of BHS The BHM Evaluation page of BHS is explained in Table 177. Table 177 BHM Evaluation tab attributes - BHS Attribute Meaning Index This field displays the index value that the system assigns (for only this page) to the BHM where this BHS is registered. Frequency This field displays the frequency that the BHM transmits. Channel Bandwidth The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the BHM and the BHS. Cyclic Prefix OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol to allow multi-

pathing to settle before receiving the desired data. A 1/16 cyclic prefixes mean that for every 16 bits of throughput data transmitted, an additional bit is used. Page 8-31 Chapter 8: Tools Using BHM Evaluation tool ESN This field displays the MAC address (electronic serial number) of the BHM. For operator convenience during BHS aiming, this tab retains each detected ESN for up to 15 minutes. If the broadcast frequency of a detected BHM changes during a 15-minute interval in the aiming operation, then a multiple instance of the same ESN is possible in the list. Eventually, the earlier instance expires and disappears and the later instance remains to the end of its interval, but you can ignore the early instance(s) whenever two or more are present. Region This field displays the BHMs configured Country Code setting. Power Level This field displays the BHSs combined received power level from the BHMs transmission. Beacon Count A count of the beacons seen in a given time period. FECEn This field contains the SNMP value from the BHM that indicates whether the Forward Error Correction feature is enabled. 0: FEC is disabled 1: FEC is enabled Type Age Multipoint indicates that the listing is for a BHM. This is a counter for the number of minutes that the BHM has been inactive. At 15 minutes of inactivity for the BHS, this field is removed from the BHM Evaluation tab in the BHS. Lockout This field displays how many times the BHS has been temporarily locked out of making registration attempts. RegFail Range This field displays how many registration attempts by this BHS failed. This field displays the distance in feet for this link. To derive the distance in meters, multiply the value of this parameter by 0.3048. MaxRange This field indicates the configured value for the APs Max Range parameter. TxBER EBcast A 1 in this field indicates the BHM is sending Radio BER. A 1 in this field indicates the BHM is encrypting broadcast packets. A 0 indicates it is not. Session Count This field displays how many sessions the BHS has had with the BHM. Typically, this is the sum of Reg Count and Re-Reg Count. However, the result of internal calculation may display here as a value that slightly differs from the sum. In the case of a multipoint link, if the number of sessions is significantly greater than the number for other BHSs, then this may indicate a link problem or an interference problem. Page 8-32 Chapter 8: Tools Using BHM Evaluation tool NoLUIDs This field indicates how many times the BHM has needed to reject a registration request from a BHS because its capacity to make LUID assignments is full. This then locks the BHS out of making any valid attempt for the next 15 minutes. It is extremely unlikely that a non-zero number would be displayed here. OutOfRange This field indicates how many times the BHM has rejected a registration request from a BHS because the BHS is a further distance away than the range that is currently configured in the BHM. This then locks the BHS out of making any valid attempt for the next 15 minutes. AuthFail This field displays how many times authentication attempts from this SM have failed in the BHM. EncryptFail This field displays how many times an encryption mismatch has occurred between the BHS and the BHM. Rescan Req This field displays how many times a re-range request has occurred for the BHM that is being evaluated in the BHM Eval page of a BHM. SMLimitReached This field displays 0 if additional BHSs may be registered to the BHM. If a 1 is displayed, the BHM will not accept additional BHS registrations. NoVCs This counter is incremented when the BHS is registering to a BHM which determines that no VC resources are available for allocation. This could be a primary data VC or a high priority data VC. VCRsvFail This counter is incremented when the BHS is registering to a BHM which has a VC resource available for allocation but cannot reserve the resource for allocation. VCActFail This counter is incremented when the BHS is registering to a BHM which has a VC resource available for allocation and has reserved the VC, but cannot activate the resource for allocation. AP Gain RcvT This field displays the total external gain (antenna) used by the BHM. This field displays the APs configured receive target for receiving BHS transmissions (this field affects automatic BHS power adjust). Sector ID This field displays the value of the Sector ID field that is provisioned for the BHM. Color Code This field displays a value from 0 to 254 indicating the BHMs configured color code. For registration to occur, the color code of the BHS and the BHM must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a BHS to register to only a specific BHM, even where the BHS can communicate with multiple BHMs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Page 8-33 Chapter 8: Tools Using BHM Evaluation tool BeaconVersion This field indicates that the beacon is OFDM (value of 1). Sector User Count This field displays how many BHSs are registered on the BHM. NumULHalfSlots This is the number of uplink slots in the frame for this BHM. NumDLHalfSlots This is the number of downlink slots in the frame for this. NumULContSlots This field displays how many Contention Slots are being used in the uplink portion of the frame. WhiteSched Flag to display if schedule whitening is supported via FPGA ICC This field lists the BHSs that have registered to the BHM with their Installation Color Code (ICC), Primary CC, Secondary CC or Tertiary CC. SM PPPoE This filed provides information to the user whether the BHS is supporting PPPoE or not. Frame Period This field displays the configured Frame Period of the radio. Page 8-34 Chapter 8: Tools Using the OFDM Frame Calculator tool Using the OFDM Frame Calculator tool The first step to avoid interference in wireless systems is to set all APs/BHMs to receive timing from a synchronization source (Cluster Management Module, or Universal Global Positioning System). This ensures that the modules are in sync and start transmitting at the same time each frame. The second step to avoid interference is to configure parameters on all APs/BHMs of the same frequency band in proximity such that they have compatible transmit/receive ratios (all stop transmitting each frame before any start receiving). This avoids the problem of one AP/BHM attempting to receive the signal from a distant SM/BHS while a nearby AP transmits, which could overpower that signal. The following parameters on the AP determine the transmit/receive ratio:

Max Range Downlink Data percentage

(reserved) Contention Slots If OFDM (PMP 430, PMP 450, PTP 230) and FSK (PMP 1x0) APs/BHMs of the same frequency band are in proximity, or if APs/BHMs set to different parameters (differing in their Max Range values, for example), then operator must use the Frame Calculator to identify compatible settings. The frame calculator is available on the Frame Calculator tab of the Tools web page. To use the Frame Calculator, type various configurable parameter values into the calculator for each proximal AP and then record the resulting AP/BHM Receive Start value. Next vary the Downlink Data percentage in each calculation and iterate until the calculated AP/BHM Receive Start for all collocated AP/BHMs where the transmit end does not come before the receive start. The calculator does not use values in the module or populate its parameters. It is merely a convenience application that runs on a module. For this reason, you can use any FSK module (AP, SM, BHM, BHS) to perform FSK frame calculations for setting the parameters on an FSK AP and any OFDM module (AP, SM, BHM, BHS) to perform OFDM frame calculations for setting the parameters on an OFDM AP/BHM. For more information on PMP/PTP 450 platform co-location, see http://www.cambiumnetworks.com/solution-papersThe co-location is also supported for 900 MHz PMP 450i APs (OFDM) and PMP 100 APs (FSK). Please refer Co-location of PMP 450 and PMP 100 systems in the 900 MHz band and migration recommendations document for details. Caution APs/BHMs that have slightly mismatched transmit-to-receive ratios and low levels of data traffic may see little effect on throughput. A system that was not tuned for co-

location may work fine at low traffic levels, but encounter problems at higher traffic levels. The conservative practice is to tune for co-location before traffic ultimately increases. This prevents problems that occur as sectors are built. The OFDM Frame Calculator page is explained in Table 178. Page 8-35 Chapter 8: Tools Table 178 OFDM Frame Calculator page attributes Using the OFDM Frame Calculator tool Attribute Meaning Link Mode For AP to SM frame calculations, select Multipoint Link For BHM to BHS frame calculations, select Point-To-Point Link Platform Type Use the drop-down list to select the hardware series (board type) of the AP/BHM AP/BHM. Platform Type Use the drop-down list to select the hardware series (board type) of the SM/BHS SM/BHS. Channel Bandwidth Set this to the channel bandwidth used in the AP/BHM. Cyclic Prefix Set this to the cyclic prefix used in the AP/BHM. Max Range Set to the same value as the Max Range parameter is set in the AP(s) or BHM(s). Frame Period Set to the same value as the Frame Period parameter is set in the AP(s) or BHM(s). Page 8-36 Chapter 8: Tools Using the OFDM Frame Calculator tool Downlink Data Initially set this parameter to the same value that the AP/BHM has for its Downlink Data parameter (percentage). Then, use the Frame Calculator tool procedure as described in Using the Frame Calculator on page 8-38, you will vary the value in this parameter to find the proper value to write into the Downlink Data parameter of all APs or BHMs in the cluster. PMP 450 platform Series APs or BHMs offer a range of 15% to 85% and default to 75%. The value that you set in this parameter has the following interaction with the value of the Max Range parameter

(above):

The default Max Range value is 5 miles and, at that distance, the maximum Downlink Data value (85% in PMP 450 platform) is functional. Contention Slots This field indicates the number of (reserved) Contention Slots configured by the operator. Set this parameter to the value of the Contention Slot parameter is set in the APs or BHMs. SM/BHS One Way This field displays the time in ns (nano seconds), that a SM/BHS is away Air Delay from the AP/BHM. The Calculated Frame Results display several items of interest:

Table 179 OFDM Calculated Frame Results attributes Attribute Meaning Modulation The type of radio modulation used in the calculation (OFDM for PMP/

PTP 450 platform) Total Frame Bits The total number of bits used in the calculated frames Data Slots

(Down/Up) This field is based on the Downlink Data setting. For example, a result within the typical range for a Downlink Data setting of 75% is 61/21, meaning 61 data slots down and 21 data slots up. Contention Slots This field indicates the number of (reserved) Contention Slots configured by the operator. Air Delay for Max This is the roundtrip air delay in bit times for the Max Range value set in Range the calculator Approximate The Max Range value used for frame calculation distance for Max Range AP Transmit End In bit times, this is the frame position at which the AP/BHM ceases transmission. AP Receive Start In bit times, this is the frame position at which the AP/BHM is ready to receive transmission from the SM/BHS. Page 8-37 Chapter 8: Tools Using the OFDM Frame Calculator tool AP Receive End In bit times, this is the frame position at which the AP/BHM will cease receiving transmission from the SM/BHS. SM Receive End In bit times, this is the frame position at which the SM/BHS will cease receiving transmission from the AP/BHM. SM Transmit Start In bit times, this is the frame position at which the SM/BHS starts the transmission. SM One Way Air This filed displays the time in ns, that SM/BHS is away from the AP/BHM. Delay SM Approximate This field displays an approximate distance in miles (feet) that the distance SM/BHS is away from the AP/BHM. To use the Frame Calculator to ensure that all APs or BHMs are configured to transmit and receive at the same time, follow the procedure below:

Procedure 33 Using the Frame Calculator 1 Populate the OFDM Frame Calculator parameters with appropriate values as 2 3 4 5 6 7 8 described above. Click the Calculate button. Scroll down the tab to the Calculated Frame Results section Record the value of the AP Receive Start field Enter a parameter set from another AP in the system for example, an AP in the same cluster that has a higher Max Range value configured. Click the Calculate button. Scroll down the tab to the Calculated Frame Results section If the recorded values of the AP Receive Start fields are within 150 bit times of each other, skip to step 10. If the recorded values of the AP Receive Start fields are not within 150 bit times of each other, modify the Downlink Data parameter until the calculated results for AP Receive Start are within 300 bit time of each other, if possible, 150 bit time. 10 Access the Radio tab in the Configuration web page of each AP in the cluster and change its Downlink Data parameter (percentage) to the last value that was used in the Frame Calculator. Page 8-38 Chapter 8: Tools Using the Subscriber Configuration tool Using the Subscriber Configuration tool The Subscriber Configuration page in the Tools page of the AP displays:

The current values whose control may be subject to the setting in the Configuration Source parameter. An indicator of the source for each value. This page may be referenced for information on how the link is behaving based on where the SM is retrieving certain QoS and VLAN parameters. Figure 162 SM Configuration page of AP The AP displays one of the following for the configuration source:

(SM) QoS/VLAN parameters are derived from the SMs settings

(APCAP) QoS/VLAN parameters are derived from the APs settings, including any keyed capping (for radios capped at 4 Mbps, 10 Mbps, or 20 Mbps)

(D) QoS/VLAN parameters are retrieved from the device, due to failed retrieval from the AAA or WM server.

(AAA) QoS/VLAN parameters are retrieved from the RADIUS server

(BAM) QoS/VLAN parameters are retrieved from a WM BAM server Page 8-39 Chapter 8: Tools Using the Link Status tool Using the Link Status tool The Link Status Tool displays information about the most-recent Link Test initiated on the SM or BHS. Link Tests initiated from the AP or BHM are not included in the Link Status table. This table is useful for monitoring link test results for all SMs or BHS in the system. The Link Status table is color coded to display health of link between AP/BHM and SM/BHS. The current Modulation Level Uplink/Downlink is chosen to determine link health and color coded accordingly. Uplink/Downlink Rate Column will be color coded using current Rate as per the table below:

Table 180 Color code vers uplink/downlink rate column Actual Rate 1x 2x 3x 4x SISO RED ORANGE GREEN BLUE 6x NA MIMO-A RED ORANGE GREEN BLUE NA 8x NA NA MIMO B NA RED NA ORANGE GREEN BLUE Link Status AP/BHM The current Uplink Rate (both low and high VC) for each SM or BHS in Session in now available on AP or BHM Link Status Page. The Link Status tool results include values for the following fields for AP/BHM. Table 181 Link Status page attributes AP/BHM Page 8-40 Chapter 8: Tools Attribute Meaning Using the Link Status tool Subscriber This field displays the LUID (logical unit ID), MAC address and Site Name of the SM. As each SM registers to the AP, the system assigns an LUID of 2 or a higher unique number to the SM. If a SM loses registration with the AP and then regains registration, the SM will retain the same LUID. Note The LUID associated is lost when a power cycle of the AP occurs. Both the LUID and the MAC are hot links to open the interface to the SM. In some instances, depending on network activity and network design, this route to the interface yields a blank web page. If this occurs, refresh your browser view. Site Name indicates the name of the SM. You can assign or change this name on the Configuration web page of the SM. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Uplink Statistics -

This field represents the combined received power level at the AP/BHM Power Level: Signal as well as the ratio of horizontal path signal strength to vertical path Strength Ratio signal strength. Uplink Statistics This field represents the percentage of fragments received at each Fragments Modulation modulation state, per path (polarization). Uplink Statistics This field represents the signal to noise ratio for the uplink (displayed Signal to Noise Ratio when parameter Signal to Noise Ratio Calculation during Link Test is enabled) expressed for both the horizontal and vertical channels. Uplink Statistics This field displays the efficiency of the radio link, expressed as a Link Test Efficiency percentage, for the radio uplink. Downlink Statistics This field represents the received power level at the SM/BHS as well as Power Level: Signal the ratio of horizontal path signal strength to vertical path signal Strength Ratio strength at the SM/BHS. Downlink Statistics This field represents the signal to noise ratio for the downlink (displayed Signal to Noise Ratio when parameter Signal to Noise Ratio Calculation during Link Test is enabled) expressed for both the horizontal and vertical channels. Downlink Statistics This field displays the efficiency of the radio link, expressed as a Link Test Efficiency percentage, for the radio downlink. Page 8-41 Chapter 8: Tools Using the Link Status tool BER Results This field displays the over-the-air Bit Error Rates for each downlink.

(The ARQ [Automatic Resend reQuest] ensures that the transport BER

[the BER seen end-to-end through a network] is essentially zero.) The level of acceptable over-the-air BER varies, based on operating requirements, but a reasonable value for a good link is a BER of 1e-4 (1 x 10-4) or better, approximately a packet resend rate of 5%. BER is generated using unused bits in the downlink. During periods of peak load, BER data is not updated as often, because the system puts priority on transport rather than on BER calculation. Reg Requests A Reg Requests count is the number of times the SM/BHS registered after the AP/BHM determined that the link had been down. If the number of sessions is significantly greater than the number for other SMs/BHS, then this may indicate a link problem (check mounting, alignment, receive power levels) or an interference problem (conduct a spectrum scan). ReReg Requests A ReReg Requests count is the number of times the AP/BHM received a SM/BHS registration request while the AP/BHM considered the link to be still up (and therefore did not expect registration requests). If the number of sessions is significantly greater than the number for other SMs/BHS, then this may indicate a link problem (check mounting, alignment, receive power levels) or an interference problem (conduct a spectrum scan). Link Status SM/BHS The Link Status tool of SM/BHS displays Downlink Status and Uplink Status information. Page 8-42 Chapter 8: Tools Table 182 Link Status page attributes SM/BHS Using the Link Status tool Attribute Meaning Downlink Status Receive Power This field lists the current combined receive power level, in dBm. Signal Strength This field displays the difference of the Vertical path received signal Ratio power to the Horizontal path received signal power for downlink. Signal to Noise Ratio This field lists the current signal-to-noise level, an indication of the separation of the received power level vs. noise floor for downlink. Beacons Displays a count of beacons received by the SM in percentage. This value must be typically between 99-100%. If lower than 99%, it indicates a problematic link. This statistic is updated every 16 seconds. Received Fragments This field represents the percentage of fragments received at each Modulation modulation state, per path (polarization) Latest Remote Link This field is not applicable. Test Efficiency Percentage BER Total Avg This field displays the over-the-air average Bit Error Rates (BER) for Results downlink. Beacons Received The beacon count on the SM can be used to estimate the interference in Last 15 minutes the channel. The min/avg/max beacon percentage displayed based on this value for the last 15 mins. Page 8-43 Chapter 8: Tools Using the Link Status tool Uplink Status Transmit Power This field displays the current combined transmit power level, in dBm. Max Transmit Power This field displays the maximum transmit power of SM. Power Level This field indicates the combined power level at which the SM is set to transmit, based on the Country Code and Antenna Gain settings. Signal Strength This field displays the difference of the Vertical path received signal Ratio power to the Horizontal path received signal power for uplink. Signal to Noise Ratio This field lists the current signal-to-noise level, an indication of the separation of the received power level vs. noise floor for uplink. Latest Remote Link This field is not applicable. Test Efficiency Percentage Session Status This field displays the current state, Virtual channel, high-priority/ low priority channel rate adaptation and MIMO-A/MIMO-B/SISO status of SM. Run Link Test See Exploratory Test section of Performing Extrapolated Link Test on page 8-23 Page 8-44 Chapter 8: Tools Using BER Results tool Using BER Results tool Radio BER data represents bit errors at the RF link level. Due to CRC checks on fragments and packets and ARQ (Automatic Repeat reQuest), the BER of customer data is essentially zero. Radio BER gives one indication of link quality. Other important indications to consider includes the received power level, signal to noise ratio and link tests. BER is only instrumented on the downlink and is displayed on the BER Results tab of the Tools page in any SM. Each time the tab is clicked, the current results are read and counters are reset to zero. The BER Results tab can be helpful in troubleshooting poor link performance. The link is acceptable if the value of this field is less than 104. If the BER is greater than 104, re-

evaluate the installation of both modules in the link. The BER test signal is broadcast by the AP/BHM (and compared to the expected test signal by the SM/BHS) only when capacity in the sector allows it. This signal is the lowest priority for AP/BHM transmissions. Figure 163 BER Results tab of the SM Page 8-45 Chapter 8: Tools Using the Sessions tool Using the Sessions tool The PMP 450 platform AP has a tab Sessions under the Tools category which allows operators to drop one or all selected SM sessions and force a SM re-registration. This operation is useful to force QoS changes for SMs without losing AP logs or statistics. This operation may take 5 minutes to regain all SM registrations. Figure 164 Sessions tab of the AP Page 8-46 Chapter 9: Operation This chapter provides instructions for operators of the PMP/PTP 450 platform wireless Ethernet Bridge. The following topics are described in this chapter:

System information on page 9-2 o Viewing General Status on page 9-2 o Viewing Session Status on page 9-16 o Viewing Remote Subscribers on page 9-22 o Interpreting messages in the Event Log on page 9-23 o Viewing the Network Interface on page 9-25 o Viewing the Layer 2 Neighbors on page 9-26 System statistics on page 9-27 o Viewing the Scheduler statistics on page 9-27 o Viewing list of Registration Failures statistics on page 9-29 o o o o o o o o o o Interpreting Bridging Table statistics on page 9-30 Interpreting Translation Table statistics on page 9-31 Interpreting Ethernet statistics on page 9-32 Interpreting RF Control Block statistics on page 9-35 Interpreting VLAN statistics on page 9-36 Interpreting Data VC statistics on page 9-38 Interpreting Throughput statistics on page 9-40 Interpreting Overload statistics on page 9-43 Interpreting DHCP Relay statistics on page 9-44 Interpreting Filter statistics on page 9-46 o Viewing ARP statistics on page 9-47 o Viewing NAT statistics on page 9-47 o Viewing NAT DHCP Statistics on page 9-49 o o o o o o o Interpreting Sync Status statistics on page 9-50 Interpreting PPPoE Statistics for Customer Activities on page 9-51 Interpreting Bridge Control Block statistics on page 9-52 Interpreting Pass Through Statistics on page 9-54 Interpreting SNMPv3 Statistics on page 9-55 Interpreting syslog statistics on page 9-57 Interpreting Frame Utilization statistics on page 9-57 Radio Recovery on page 9-61 Page 9-1 Chapter 9: Operation System information System information This section describes how to use the summary and status pages to monitor the status of the Ethernet ports and wireless link. Viewing General Status on page 9-2 Viewing Session Status on page 9-16 Viewing Remote Subscribers on page 9-22 Interpreting messages in the Event Log on page 9-23 Viewing the Network Interface on page 9-25 Viewing the Layer 2 Neighbors on page 9-26 Viewing General Status The General Status tab provides information on the operation of this AP/BHM and SM/BHS. This is the page that opens by default when you access the GUI of the radio. Page 9-2 Chapter 9: Operation General Status page of AP The APs General Status page is explained in Table 183. Table 183 General Status page attributes - AP System information Attribute Meaning Device Type This field indicates the type of the module. Values include the frequency band of the SM, its module type and its MAC address. Page 9-3 Chapter 9: Operation System information Software Version This field indicates the system release, the time and date of the release and whether communications involving the module are secured by DES or AES encryption. If you request technical support, provide the information from this field. Board Type This field indicates the series of hardware. Combo Radio Mode This field indicates the mode of operation, currently only MIMO OFDM Only is supported. FPGA Version This field indicates the version of the field-programmable gate array

(FPGA) on the module. If you request technical support, provide the value of this field. FPGA Type Where the type of logic as a subset of the logic version in the module as manufactured distinguishes its circuit board, this field is present to indicate that type. If you request technical support, provide the value of this field. PLD Version This field indicates the version of the programmable logic device (PLD) on the module. If you request technical support, provide the value of this field. Uptime This field indicates how long the module has operated since power was applied. System Time This field provides the current time. If the AP is connected to a CMM4, then this field provides GMT (Greenwich Mean Time). Any SM that registers to the AP inherits the system time. Last NTP Time This field displays when the AP last used time sent from an NTP server. Update If the AP has not been configured in the Time tab of the Configuration page to request time from an NTP server, then this field is populated by 00:00:00 00/00/00. Ethernet Interface This field indicates the speed and duplex state of the Ethernet interface to the AP. Region Code A parameter that offers multiple fixed selections, each of which automatically implements frequency band range restrictions for the selected region. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. Regulatory This field indicates whether the configured Country Code and radio frequency are compliant with respect to their compatibility. PMP 450 equipment shipped to the United States is locked to a Country Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Country Code to comply with local regulatory requirements. Antenna Type The current antenna type that has been selected. Page 9-4 Chapter 9: Operation System information Channel Center This field indicates the current operating center frequency, in MHz. Frequency Channel Bandwidth This field indicates the current size of the channel band used for radio transmission. Cyclic Prefix OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol to allow multi-

pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. Frame Period This field indicates the current Frame Period setting of the radio in ms. Color Code This field displays a value from 0 to 254 indicating the APs configured color code. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Max Range This field indicates the setting of the Max Range parameter, which contributes to the way the radio transmits. Verify that the Max Range parameter is set to a distance slightly greater than the distance between the AP and the furthest SM that must register to this AP. Transmitter Output This field indicates the combined power level at which the AP is set to Power transmit, based on the Country Code and Antenna Gain settings. Temperature This field indicates the current operating temperature of the device board. Registered SM Count This field indicates how many SMs are registered to the AP. Sync Pulse Status This field indicates the status of synchronization as follows:

Generating Sync indicates that the module is set to generate the sync pulse. Receiving Sync indicates that the module is set to receive a sync pulse from an outside source and is receiving the pulse. No Sync Since Boot up / ERROR: No Sync Pulse indicates that the module is set to receive a sync pulse from an outside source and is not receiving the pulse. Note When this message is displayed, the AP transmitter is turned off to avoid self-interference within the system. Page 9-5 Chapter 9: Operation System information Sync Pulse Source This field indicates the status of the synchronization source:

Searching indicates that the unit is searching for a GPS fix Timing Port/UGPS indicates that the module is receiving sync via the timing AUX/SYNC timing port Power Port indicates that the module is receiving sync via the power port (Ethernet port). On-board GPS indicates that the module is receiving sync via the units internal GPS module Maximum Count of This field displays the largest number of SMs that have been Registered SMs simultaneously registered in the AP since it was last rebooted. This count can provide some insight into sector history and provide comparison between current and maximum SM counts at a glance. Data Slots Down This field indicates the number of frame slots that are designated for use by data traffic in the downlink (sent from the AP to the SM). The AP calculates the number of data slots based on the Max Range, Downlink Data and (reserved) Contention Slots configured by the operator. Data Slots Up This field indicates the number of frame slots that are designated for use by data traffic in the uplink (sent from the SM to the AP). The AP calculates the number of data slots based on the Max Range, Downlink Data and (reserved) Contention Slots configured by the operator. Contention Slots This field indicates the number of (reserved) Contention Slots configured by the operator. See Contention slots on page7-238. Site Name This field indicates the name of the physical module. You can assign or change this name in the SNMP tab of the AP Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Site Contact This field indicates contact information for the physical module. You can provide or change this information in the SNMP tab of the AP Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Site Location This field indicates site information for the physical module. You can provide or change this information in the SNMP tab of the AP Configuration page. Time Updated and This field displays information about the keying of the radio. Location Code Page 9-6 Chapter 9: Operation General Status page - SM The SMs General Status page is explained in Table 184. Note System information In order for accurate power level readings to be displayed, traffic must be present on the radio link. Table 184 General Status page attributes - SM Page 9-7 Chapter 9: Operation Attribute Meaning System information Device Type This field indicates the type of the module. Values include the frequency band of the SM, its module type and its MAC address. Board Type This field indicates the series of hardware. Software Version This field indicates the system release, the time and date of the release. If you request technical support, provide the information from this field. FPGA Version This field indicates the version of the field-programmable gate array

(FPGA) on the module. When you request technical support, provide the information from this field. PLD Version This field indicates the version of the programmable logic device (PLD) on the module. If you request technical support, provide the value of this field. Uptime This field indicates how long the module has operated since power was applied. System Time This field provides the current time. Any SM that registers to an AP inherits the system time, which is displayed in this field as GMT

(Greenwich Mean Time). Ethernet Interface This field indicates the speed and duplex state of Ethernet interface to the SM. Regional Code A parameter that offers multiple fixed selections, each of which automatically implements frequency band range restrictions for the selected region. Units shipped to regions other than the United States must be configured with the corresponding Country Code to comply with local regulatory requirements. DFS This field indicates that DFS operation is enabled based on the configured region code, if applicable. Antenna Type The current antenna type that has been selected. Frame Period This field indicates the current Frame Period setting of the radio in ms. Temperature The current operating temperature of the board. Session Status This field displays the following information about the current session:

Scanning indicates that this SM currently cycles through the radio frequencies that are selected in the Radio tab of the Configuration page. Syncing indicates that this SM currently attempts to receive sync. Registering indicates that this SM has sent a registration request message to the AP and has not yet received a response. Registered indicates that this SM is both:

registered to an AP. ready to transmit and receive data packets. Page 9-8 Chapter 9: Operation System information Session Uptime This field displays the duration of the current link. The syntax of the displayed time is hh:mm:ss. Registered AP Displays the MAC address and site name of the AP to which the SM is registered to. This parameter provides click-through proxy access to the APs management interface. Color Code This field displays a value from 0 to 254 indicating the SMs configured color code. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Channel Frequency This field lists the current operating frequency of the radio. Channel Bandwidth The size in MHz of the operating channel. Cyclic Prefix OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol to allow multi-

pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. Air Delay This field displays the distance in feet between this SM and the AP. To derive the distance in meters, multiply the value of this parameter by 0.3048. Distances reported as less than 200 feet (61 meters) are unreliable. Receive Power This field lists the current combined receive power level, in dBm. Signal Strength This field displays the difference of the Vertical path received signal Ratio power to the Horizontal path received signal power. Signal to Noise Ratio This field lists the current signal-to-noise level, an indication of the separation of the received power level vs. noise floor. Beacons Displays a count of beacons received by the SM in percentage. This value must be typically between 99-100%. If lower than 99%, it indicates a problematic link. This statistic is updated every 16 seconds. Transmit Power This field lists the current combined transmit power level, in dBm. Note The red SM message "target power exceeded maximum"

does not necessarily indicate a problem. Page 9-9 Chapter 9: Operation System information In this case, the AP is requesting the SM to transmit at a higher power level, but the SM is restricted due to EIRP limits or hardware capabilities. This message can be an indication that the SM is deployed further from the AP than optimal, causing the AP to adjust the SM to maximum transmit power. Data Slots Down This field lists the number of slots used for downlink data transmission. Data Slots Up This field lists the number of slots used for uplink data transmission. Contention Slots This field indicates the number of (reserved) Contention Slots configured by the operator. See Contention slots on page7-238. Site Name This field indicates the name of the physical module. You can assign or change this name in the SNMP tab of the SM Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Site Contact This field indicates contact information for the physical module. You can provide or change this information in the SNMP tab of the SM Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Site Location This field indicates site information for the physical module. You can provide or change this information in the SNMP tab of the SM Configuration page. Maximum Throughput This field indicates the limit of aggregate throughput for the SM and is based on the default (factory) limit of the SM and any floating license that is currently assigned to it. Time Updated and This field displays information about the keying of the radio. Location Code Note For PMP 450 900 MHz SM, there is additional parameter Path Info (under Subscriber Module Stats) which displays polarization path(A & B) information. Page 9-10 Chapter 9: Operation General Status page of BHM The BHMs General Status page is explained in Table 185. Table 185 General Status page attributes - BHM System information Attribute Meaning Device Type This field indicates the type of the module. Values include the frequency band of the BHM, its module type and its MAC address. Board Type This field indicates the series of hardware. Software Version This field indicates the system release, the time and date of the release. If you request technical support, provide the information from this field. Board MSN This field indicates the Manufactures Serial number. A unique serial number assigned to each radio at the factory for inventory and quality control. Page 9-11 Chapter 9: Operation System information FPGA Version This field indicates the version of the field-programmable gate array

(FPGA) on the module. When you request technical support, provide the information from this field. Uptime This field indicates how long the module has operated since power was applied. System Time This field provides the current time. Any BHS that registers to a BHM inherits the system time, which is displayed in this field as GMT

(Greenwich Mean Time). Ethernet Interface This field indicates the speed and duplex state of Ethernet interface to the BHM. Antenna Type The current antenna type that has been selected. Temperature The current operating temperature of the board. Session Status This field displays the following information about the current session:

Scanning indicates that this BHS currently cycles through the radio frequencies that are selected in the Radio tab of the Configuration page. Syncing indicates that this BHM currently attempts to receive sync. Registering indicates that this BHM has sent a registration request message to the BHM and has not yet received a response. Registered indicates that this BHM is both:

Registered to a BHM. Ready to transmit and receive data packets. Session Uptime This field displays the duration of the current link. The syntax of the displayed time is hh:mm:ss. Registered Backhaul Displays the MAC address and site name of the BHM to which the BHS is registered to. This parameter provides click-through proxy access to the BHMs management interface. Channel Frequency This field lists the current operating frequency of the radio. Receive Power This field lists the current combined receive power level, in dBm. Signal Strength This field displays the difference of the Vertical path received signal Ratio power to the Horizontal path received signal power. Transmit Power This field lists the current combined transmit power level, in dBm. Signal to Noise Ratio This field lists the current signal-to-noise level, an indication of the separation of the received power level vs. noise floor. Beacons Displays a count of beacons received by the BHM in percentage. This value must be typically between 99-100%. If lower than 99%, it indicates a problematic link. This statistic is updated every 16 seconds. Page 9-12 Chapter 9: Operation System information Air Delay This field displays the distance in feet between this BHS and the BHM. To derive the distance in meters, multiply the value of this parameter by 0.3048. Distances reported as less than 200 feet (61 meters) are unreliable. Data Slots Down This field lists the number of slots used for downlink data transmission. Data Slots Up This field lists the number of slots used for uplink data transmission. Regional Code A parameter that offers multiple fixed selections, each of which automatically implements frequency band range restrictions for the selected region. Units shipped to regions other than the United States must be configured with the corresponding Country Code to comply with local regulatory requirements. Site Name This field indicates the name of the physical module. Assign or change this name in the Configuration > SNMP page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Page 9-13 Chapter 9: Operation General Status page of BHS The BHSs General Status page is explained in Table 186. Table 186 General Status page attributes - BHS System information Attribute Meaning Device Type Board Type Software Version See Table 186 on page 9-14 Board MSN FPGA Version Page 9-14 Chapter 9: Operation System information Uptime System Time Ethernet Interface Antenna Type Temperature Session Status Session Uptime Registered Backhaul Channel Frequency Receive Power Signal Strength Ratio Transmit Power Signal to Noise Ratio Beacons Air Delay Data Slots Down Data Slots Up Regional Code Site Name Site Contact Site Location Time Updated and Location Code See Table 186 on page 9-14 Page 9-15 Chapter 9: Operation Viewing Session Status System information The Session Status page in the Home page provides information about each SM or BHS that has registered to the AP or BHM. This information is useful for managing and troubleshooting a system. This page also includes the current active values on each SM or BHS for MIR and VLAN, as well as the source of these values, representing the SM/BHS itself, Authentication Server, or the Authentication Server and SM/BHS. Note In order for accurate power level readings to be displayed, traffic must be present on the radio link. The Session Status List has four tab: Device, Session, Power and Configuration. The SessionStatus.xml hyper link allows user to export session status page from web management interface of AP or BHM. The session status page will be exported in xml file. Device tab The Device tab provides information on the Subscribers LUID and MAC, Hardware, Software, FPGA versions and the state of the SM/BHS (Registered and/or encrypted). Table 187 Device tab attributes Attribute Meaning Subscriber This field displays the LUID (logical unit ID), MAC address and Site Name of the SM/BHS. As each SM or BHS registers to the AP/BHM, the system assigns an LUID of 2 or a higher unique number to the SM/BHS. If a SM/BHS loses registration with the AP/BHS and then regains registration, the SM/BHS will retain the same LUID. Note The LUID associated is lost when a power cycle of the AP/BHM occurs. Page 9-16 Chapter 9: Operation System information Both the LUID and the MAC are hot links to open the interface to the SM/BHS. In some instances, depending on network activity and network design, this route to the interface yields a blank web page. If this occurs, refresh your browser view. Site Name indicates the name of the SM/BHS. Change this name on the Configuration web page of the SM/BHS. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Hardware This field displays the SMs or BHS hardware type. Software Version This field displays the software release that operates on the SM/BHS, the release date and time of the software. FPGA Version This field displays the version of FPGA that runs on the SM/BHS State This field displays the current status of the SM/BHS as either IN SESSION to indicate that the SM/BHS is currently registered to the AP/BHM. IDLE to indicate that the SM/BHS was registered to the AP/BHM at one time, but now is not. This field also indicates whether the encryption scheme in the module is enabled. Session tab The Session tab provides information on the SMs or BHS Session Count, Reg Count, Re-Reg Count, Uptime, Air delay, PPPoE State and Timeouts. Table 188 Session tab attributes Attribute Meaning Subscriber See Table 187 on page 9-16. Page 9-17 Chapter 9: Operation System information Count This field displays how many sessions the SM/BHS has had with the AP/BHM. Typically, this is the sum of Reg Count and Re-Reg Count. However, the result of internal calculation may display here as a value that slightly differs from the sum. If the number of sessions is significantly greater than the number for other SMs or BHS, then this may indicate a link problem or an interference problem. Reg Count When a SM/BHS makes a Registration Request, the AP/BHM checks its local session database to see whether it was registered earlier. If the AP/BHM concludes that the SM/BHS is not currently in session database and it is valid Registration Request, then the request increments the value of this field. In ideal situation, the Reg Count indicates total number of connected SMs to an AP. Note The user can clear Reg Count by droping all current sessions of SM (or BHS) from Configuration > Tools > Sessions menu. Re-Reg Count When a SM/BHS makes a Registration Request, the AP/BHM checks its local session database to see whether it was registered earlier. If the AP/BHM concludes that the SM/BHS is currently in session database, then the request increments the value of this field. Typically, a Re-Reg is the case where both:

SM/BHS attempts to reregister for having lost communication with the AP/BHM. AP/BHM has not yet observed the link to the SM/BHS as being down. It is possible for a small period of time if there is no downlink traffic and AP/BHM still assumes the session is up, but the SM/BHS, loses session and quickly re-connects before the AP/BHM knew the session had dropped. This is how a re-registration happens. If the number of sessions is significantly greater than the number for other SMs or BHS, then this may indicate a link problem (check mounting, alignment, receive power levels) or an interference problem

(conduct a spectrum scan). Uptime Once a SM/BHS successfully registers to an AP/BHM, this timer is started. If a session drops or is interrupted, this timer is reactivated once re-registration is complete. CC Priority The field displays Color Code Priority (ICC, Primary, Secondary or Tertiary) of all connected SM. Page 9-18 Chapter 9: Operation System information AirDelay This field displays the distance of the SM/BHS from the AP/BHM in meters, nanoseconds and bits. At close distances, the value in this field is unreliable. PPPoE state This field displays the current PPPoE state (whether configured) of the SM/BHS. Timeout This field displays the timeout in seconds for management sessions via HTTP, ftp access to the SM/BHS. 0 indicates that no limit is imposed. Power tab Table 189 Power tab attributes Attribute Meaning Subscriber See Table 187 on page 9-16. Hardware This field displays the SMs or BHS hardware type. Rate This field displays whether the high-priority channel is enabled in the SM/BHS and the status of rate adapt. For example, if 8X/4X is listed, the radio is capable of operating at 8X but is currently operating at 4X, due to RF conditions. This field also states whether it is MIMO-A or MIMO-B radio e.g. 8X/8X MIMO-B indicates MIMO-B and 8X/4X MIMO-A indicates MIMO-A. A VC starts at its lowest modulation and slowly rate adapts up, as traffic is successfully transmitted over the VC. It is normal for one VC to have a different modulation rate than another VC, if only one VC has traffic on it. For example if High Priority VC is enabled, but only low priority VC has traffic the reading will show:

REGISTERED VC 18 Rate 8X/8X MIMO-B VC 255 Rate 8X/1X MIMO-B AP Rx Power (dBm) This field indicates the APs or BHMs combined receive power level for the listed SM/BHS. Page 9-19 Chapter 9: Operation System information Signal Strength This field displays the ratio of the Vertical path received signal power to Ratio (dB) the Horizontal path received signal power. This ratio can be useful for determining multipathing conditions (high vertical to horizontal ratio) for Uplink. Signal to Noise Ratio This field lists the current signal-to-noise level, an indication of the

(dB) separation of the received power level vs. noise floor. In other words, it indicates signal to noise ratio for Uplink. Configuration tab The Configuration tab provides information on the SMs or BHS Uplink or Downlink (UL/DL) Sustained Data Rate, UL/DL Burst Allocation, UL/DL Burst Rate, UL/DL Low Priority CIR, UL/DL High CIR, UL/DL High Priority Queue Information and the UL/DL Broadcast or Multicast Allocation. This data is refreshed based on the Web Page Auto Update setting on the APs or BHSs General Configuration page. Table 190 Configuration tab attributes Attribute Meaning Subscriber See Table 187 on page 9-16. Sustained Data Rate This field displays the value that is currently in effect for the SM/BHS,

(kbps) - Uplink with the source of that value in parentheses. This is the specified rate at which each SM/BHS registered to this AP/BHM is replenished with credits for transmission. The configuration source of the value is indicated in parentheses. See Maximum Information Rate (MIR) Parameters on page 7-259. Sustained Data Rate This field displays the value that is currently in effect for the SM/BHS,

(kbps) - Downlink with the source of that value in parentheses. This is the specified the rate at which the AP/BHM should be replenished with credits (tokens) for transmission to each of the SMs/BHSs in its sector. The configuration source of the value is indicated in parentheses. See Maximum Information Rate (MIR) Parameters on page 7-259. Page 9-20 Chapter 9: Operation System information Burst Allocation This field displays the value that is currently in effect for the SM/BHS,

(kbit) - Uplink with the source of that value in parentheses. This is the specified maximum amount of data that each SM/BHS is allowed to transmit before being recharged at the Sustained Uplink Data Rate with credits to transmit more. The configuration source of the value is indicated in parentheses. See Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-261 Burst Allocation This field displays the value that is currently in effect for the SM/BHS,

(kbit) - Downlink with the source of that value in parentheses. This is the specified the rate at which the AP/BHM should be replenished with credits (tokens) for transmission to each of the SMs/BHSs in its sector. The configuration source of the value is indicated in parentheses. See Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-261 Max Burst Rate (kbit) The data rate at which an SM/BHS is allowed to burst (until burst

- Uplink allocation limit is reached) before being recharged at the Sustained Uplink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. See Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-261 Max Burst Rate (kbit) The data rate at which an SM/BHS is allowed to burst (until burst

- Downlink allocation limit is reached) before being recharged at the Sustained Downlink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. See Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-261 Low Priority CIR This field indicates the minimum rate at which low priority traffic is sent over the uplink and downlink (unless CIR is oversubscribed or RF link quality is degraded). High CIR This field indicates the minimum rate at which high priority traffic is sent over the uplink and downlink (unless CIR is oversubscribed or RF link quality is degraded). Broadcast/Multicast This field displays the data rate at which Broadcast and Multicast traffic Allocation is sent via the radio link. RADIUS This field displays whether RADIUS server is reachable or not. Authentication Reply Page 9-21 Chapter 9: Operation System information RADIUS This field displays the associated RADIUS Authentication Server for each Authentication SM where it was authenticated. This information is useful when there Server are multiple RADIUS servers (maximum three servers supported by Cambium). If one server is not reachable, other configured servers are tried in sequential order as a fall-back. In this scenario, the Session Status is useful to identify associate RADIUS Authentication Server for all connected SMs. Table 191 Session Status > Configuration CIR configuration denotations Attribute Meaning

(SM) QoS/VLAN parameters are derived from the SMs/BHSs settings

(APCAP) QoS/VLAN parameters are derived from the APs settings, including any keyed capping (for radios capped at 4 Mbps, 10 Mbps, or 20 Mbps)

(D) QoS/VLAN parameters are retrieved from the device, due to failed retrieval from the AAA or WM server. QoS/VLAN parameters are retrieved from the RADIUS server QoS/VLAN parameters are retrieved from a WM BAM server

(AAA)

(BAM) Viewing Remote Subscribers This page allows to view the web pages of registered SMs or BHS over the RF link. To view the pages for a selected SM/BHS, click its link. The General Status page of the SM opens. Figure 165 Remote Subscribers page of AP Page 9-22 Chapter 9: Operation System information Interpreting messages in the Event Log Each line in the Event Log of a module Home page begins with a time and date stamp. However, some of these lines wrap as a combined result of window width, browser preferences and line length. You may find this tab easiest to use if you expand the window till all lines are shown beginning with time and date stamp. Time and Date Stamp The time and date stamp reflect one of the following:

GPS time and date directly or indirectly received from the CMM4. NTP time and date from a NTP server (CMM4 may serve as an NTP server) The running time and date that you have set in the Time & Date web page. Note In the Time & Date web page, if you have left any time field or date field unset and clicked the Set Time and Date button, then the time and date default to 00:00:00 UT

: 01/01/00. A reboot causes the preset time to pause or, in some cases, to run in reverse. Additionally, a power cycle resets the running time and date to the default 00:00:00 UT : 01/01/00. Thus, whenever either a reboot or a power cycle has occurred, must reset the time and date in the Time & Date web page of any module that is not set to receive sync. Event Log Data Collection The collection of event data continues through reboots and power cycles. When the buffer allowance for event log data is reached, the system adds new data into the log and discards an identical amount of the oldest data. Each line that contains the expression WatchDog flags an event that was both:

considered by the system software to have been an exception recorded in the preceding line. Conversely, a Fatal Error () message flags an event that is recorded in the next line. Some exceptions and fatal errors may be significant and require either operator action or technical support. Page 9-23 Chapter 9: Operation Figure 166 Event log data System information Messages that Flag Abnormal Events The messages listed below flag abnormal events and, case by case, may signal the need for corrective action or technical support. Table 192 Event Log messages for abnormal events Event Message Meaning Expected LUID = 6 Something is interfering with the control messaging of the module. Also Actual LUID = 7 ensure that you are using shielded cables to minimize interference. Consider trying different frequency options to eliminate or reduce interference. FatalError() The event recorded on the line immediately beneath this message triggered the Fatal Error (). Loss of GPS Sync Pulse Module has lost GPS sync signal. Machine Check This is a symptom of a possible hardware failure. If this is a recurring Exception message, begin the RMA process for the module. RcvFrmNum =

Something is interfering with the control messaging of the module. Also 0x00066d ensure that you are using shielded cables to minimize interference. ExpFrmNum =

Consider trying different frequency options to eliminate or reduce 0x000799 interference. System Reset Exception -- External The unit lost power or was power cycled. Hard Reset Page 9-24 Chapter 9: Operation System information System Reset Exception -- External The event recorded on the preceding line triggered this WatchDog Hard Reset WatchDog message. Messages that Flag Normal Events The messages listed below record normal events and typically do not signal a need for any corrective action or technical support. Table 193 Event Log messages for normal events Event Message Meaning Acquired GPS Sync Pulse. Module has acquired GPS sync signal. FPGA Features Type of encryption. FPGA Version FPGA (JBC) version in the module. GPS Date/Time Set Module is now on GPS time. Reboot from Webpage Module was rebooted from management interface. Software Boot Version Boot version in the module. Software Version The software release and authentication method for the unit. System Log Cleared Event log was manually cleared. Viewing the Network Interface In any module, the LAN1 Network Interface section of this tab displays the defined Internet Protocol scheme for the Ethernet interface to the module. In SM/BHS devices, this page also provides an RF Public Network Interface section, which displays the Internet Protocol scheme defined for network access through the master device (AP/BHM). Figure 167 Network Interface tab of the AP Page 9-25 Chapter 9: Operation Figure 168 Network Interface tab of the SM System information Viewing the Layer 2 Neighbors In the Layer 2 Neighbors tab, a module reports any device from which it has received a message in Link Layer Discovery Protocol within the previous two minutes. Given the frequency of LLDP messaging, this means that the connected device will appear in this tab 30 seconds after it is booted and remain until two minutes after its shutdown. Figure 169 Layer 2 Neighbors page Page 9-26 Chapter 9: Operation System statistics System statistics This section describes how to use the system statistics pages to manage the performance of the PMP/PTP 450 platform link. Viewing the Scheduler statistics The Statistics > Scheduler page is applicable for all modules (AP/SM/BHM/BHS) and the parameters are displayed as shown below:

Table 194 Scheduler tab attributes Attribute Meaning Transmit Unicast Data Count Transmit Broadcast Data Count Transmit Multicast Data Count Receive Unicast Data Count The total amount of unicast packets transmitted from the radio The total amount of broadcast packets transmitted from the radio The total amount of multicast packets transmitted by the radio The total amount of unicast packets received by the radio Page 9-27 Chapter 9: Operation Receive Broadcast Data Count System statistics The total amount of broadcast packets received by the radio Transmit Control The amount of radio control type messages transmitted (registration Count requests and grants, power adjust, etc.). Receive Control The amount of radio control type messages received (registration Count requests and grants, power adjust, etc.). In Sync Count Number of times the radio has acquired sync. In the case of an AP generating sync this is when generated sync has been locked, or if GPS synchronization is used it is number of times GPS sync acquired. For the SM, it is the number of times the SM successfully obtained sync with an AP. Out of Sync Count Number of times the radio lost same sync lock. Overrun Count Number of times FPGA frame has overrun its TX Frame Underrun Count Number of times FPGAs TX Frame aborted prematurely. Receive Corrupt Data Count Receive Bad Broadcast Control Count Bad In Sync ID Received Number of times a corrupt fragment has been received at the FPGA. Number of times the radio has received an invalid control message via broadcast (SM only). Currently unused Rcv LT Start Number of Link Test Start messages received. A remote radio has requested that this radio start a link test to it. Rcv LT Start HS Number of Link Test Start Handshake messages received. This radio requested that a remote radio start a link test and the remote radio has sent a handshake back acknowledging the start. Rcv LT Result This radio received Link Test results from the remote radio under test. When this radio initiates a link test, the remote radio will send its results to this radio for display. Xmt LT Result This radio transmitted its link test results to the remote radio under test. When the remote radio initiates a link test, this radio must send its results to the remote radio for display there. Frame Too Big This statistics indicates the number of packets received and processed by the radios which were greater than max packet size 1700 bytes. Bad This statistics indicates the number of packets received as bad Acknowledgment acknowledgment. It is for engineering use only. Bad Fragment This statistic indicates number of fragments tagged internally as bad. It is for engineering use only. Page 9-28 Chapter 9: Operation System statistics Viewing list of Registration Failures statistics SM Registration Failures page of AP The SM Registration Failures tab identifies SMs that have recently attempted and failed to register to this AP. With its time stamps, these instances may suggest that a new or transient source of interference exists. Table 195 SM Registration Failures page attributes - AP Attribute Meaning Status 17 Flag 0 No response was received from the AAA server and hence SM is trying to send a session request again. BHS Registration Failures page of BHM Table 196 BHS Registration Failures page attributes - BHM Attribute Meaning Status 17 Flag 0 No response was received from the AAA server and hence SM is trying to send a session request again. There is a list of flags from 0 to 20 as shown in Table 197 and the Flags can be ignored. Page 9-29 Chapter 9: Operation Table 197 Flags status Flag Meaning Flag Meaning System statistics 0 1 2 3 4 5 6 7 8 9 Normal Out of Range No Luids BH ReRange Auth Fail Encrypt Fail Power Adjust No VCs Reserve VC Fail Activate VC Fail 10 Hi VC Setup Fail 11 12 13 14 15 16 17 18 19 20

-

AP Lite Limit Reached Only Ver 9.5+ Allowed Temporary Data VC for AAA AAA Authentication Failure Registration Grant Reject Blank AAA Session Retry AAA Reauth Failure RegReq at zero power RegReq no time ref

-

Interpreting Bridging Table statistics If NAT (network address translation) is not active on the SM/BHS, then the Bridging Table page provides the MAC address of all devices that are attached to registered SMs/BHS (identified by LUIDs). The SM/BHS management MAC addresses are also added in bridge table upon SMs/BHS registration. These entries will be remove automically from the table once SMs/BHS is de-

registered. This alleviates the arp cache > bridge cache timeout problems. The bridging table allows data to be sent to the correct module as follows:

For the AP/BHM, the uplink is from RF to Ethernet. Thus, when a packet arrives in the RF interface to the AP/BHM, the AP/BHM reads the MAC address from the inbound packet and creates a bridging table entry of the source MAC address on the other end of the RF interface. For the SM/BHS, the uplink is from Ethernet to RF. Thus, when a packet arrives in the Ethernet interface to one of these modules, the module reads the MAC address from the inbound packet and creates a bridging table entry of the source MAC address on the other end of the Ethernet interface. Page 9-30 Chapter 9: Operation Figure 170 Bridging Table page System statistics The Bridging Table supports up to 4096 entries. Interpreting Translation Table statistics When Translation Bridging is enabled in the AP, each SM keeps a table mapping MAC addresses of devices attached to the AP to IP addresses, as otherwise the mapping of end-user MAC addresses to IP addresses is lost. (When Translation Bridging is enabled, an AP modifies all uplink traffic originating from registered SMs such that the source MAC address of every packet is changed to that of the SM which bridged the packet in the uplink direction.) Figure 171 Translation Table page of SM Page 9-31 Chapter 9: Operation Interpreting Ethernet statistics System statistics The Statistics > Ethernet page reports TCP throughput and error information for the Ethernet connection of the module. This page is applicable for all modules (AP/SM/BHM/BHS). The Ethernet page displays the following fields. Table 198 Ethernet tab attributes Attribute Meaning Ethernet Link 1 indicates that an Ethernet link is established to the radio, 0 indicates Detected that no Ethernet link is established Ethernet Link Lost This field indicates a count of how many times the Ethernet link was lost. Undersized Toss This field indicates the number of packets that were too small to process Count and hence discarded. inoctets Count This field displays how many octets were received on the interface, including those that deliver framing information. inucastpkts Count This field displays how many inbound subnetwork-unicast packets were delivered to a higher-layer protocol. Innucastpkts Count This field displays how many inbound non-unicast (subnetwork-

broadcast or subnetwork-multicast) packets were delivered to a higher-

layer protocol. Page 9-32 Chapter 9: Operation System statistics indiscards Count This field displays how many inbound packets were discarded without errors that would have prevented their delivery to a higher-layer protocol. (Some of these packets may have been discarded to increase buffer space.) inerrors Count This field displays how many inbound packets contained errors that prevented their delivery to a higher-layer protocol. inunknownprotos This field displays how many inbound packets were discarded because Count of an unknown or unsupported protocol. outoctets Count This field displays how many octets were transmitted out of the interface, including those that deliver framing information. outucastpkts Count This field displays how many packets for which the higher-level protocols requested transmission to a subnetwork-unicast address. The number includes those that were discarded or not sent. outnucastpkts Count This field displays how many packets for which the higher-level protocols requested transmission to a non-unicast (subnetwork-

broadcast or subnetwork-multicast) address. The number includes those that were discarded or not sent. outdiscards Count This field displays how many outbound packets were discarded without errors that would have prevented their transmission. (Some of these packets may have been discarded to increase buffer space.) outerrrors Count This field displays how many outbound packets contained errors that prevented their transmission. RxBabErr This field displays how many receiver babble errors occurred. TxHbErr This field displays how many transmit heartbeat errors have occurred. EthBusErr This field displays how many Ethernet bus errors occurred on the Ethernet controller. CRCError This field displays how many CRC errors occurred on the Ethernet controller. RcvFifoNoBuf This field displays the number of times no FIFO buffer space was able to be allocated RxOverrun This field displays how many receiver overrun errors occurred on the Ethernet controller. Late Collision This field displays how many late collisions occurred on the Ethernet controller. A normal collision occurs during the first 512 bits of the frame transmission. A collision that occurs after the first 512 bits is considered a late collision. Page 9-33 Chapter 9: Operation System statistics Caution A late collision is a serious network problem because the frame being transmitted is discarded. A late collision is most commonly caused by a mismatch between duplex configurations at the ends of a link segment. RetransLimitExp This field displays how many times the retransmit limit has expired. TxUnderrun This field displays how many transmission-underrun errors occurred on the Ethernet controller. CarSenseLost This field displays how many carrier sense lost errors occurred on the Ethernet controller. No Carrier This field displays how many no carrier errors occurred on the Ethernet controller. Page 9-34 Chapter 9: Operation System statistics Interpreting RF Control Block statistics The Statistics > Radio page is applicable for all module (AP/SM/BHM/BHS). The Radio page of the Statistics page displays the following fields. Table 199 Radio (Statistics) page attributes Attribute Meaning inoctets Count This field displays how many octets were received on the interface, including those that deliver framing information. inucastpkts Count This field displays how many inbound subnetwork-unicast packets were delivered to a higher-layer protocol. Innucastpkts Count This field displays how many inbound non-unicast (subnetwork-

broadcast or subnetwork-multicast) packets were delivered to a higher-

layer protocol. indiscards Count This field displays how many inbound packets were discarded without errors that would have prevented their delivery to a higher-layer protocol. This stat is pegged whenever corrupt data is received by software or whenever the RF Software Bridge queue is full. Corrupt data is a very unusual event because all packets are CRC checked by hardware before being passed into software. The likely case for indiscards is if the RF bridge queue is full. If this is the case the radio is most likely PPS limited due to excessive small packet traffic or a problem at the Ethernet interface. If there is a problem at the Ethernet interface there is likely to be discards at the Ethernet as well. inerrors Count This field displays how many inbound packets contained errors that prevented their delivery to a higher-layer protocol. inunknownprotos This field displays how many inbound packets were discarded because Count of an unknown or unsupported protocol. Page 9-35 Chapter 9: Operation System statistics outoctets Count This field displays how many octets were transmitted out of the interface, including those that deliver framing information. outucastpkts Count This field displays how many packets for which the higher-level protocols requested transmission to a subnetwork-unicast address. The number includes those that were discarded or not sent. outnucastpkts Count This field displays how many packets for which the higher-level protocols requested transmission to a non-unicast (subnetwork-

broadcast or subnetwork-multicast) address. The number includes those that were discarded or not sent. outdiscards Count This field displays how many outbound packets were discarded without errors that would have prevented their transmission. (Some of these packets may have been discarded to increase buffer space.) outerrrors Count This field displays how many outbound packets contained errors that prevented their transmission. Interpreting VLAN statistics The Statistics > VLAN page provides a list of the most recent packets that were filtered because of VLAN membership violations. It is applicable for all modules (AP/SM/BHM/BHS). Table 200 VLAN page attributes Attribute Meaning Unknown This must not occur. Contact Technical Support. Only Tagged The packet was filtered because the configuration is set to accept only packets that have an 802.1Q header and this packet did not. Page 9-36 Chapter 9: Operation System statistics Ingress When the packet entered through the wired Ethernet interface, the packet was filtered because it indicated an incorrect VLAN membership. Local Ingress When the packet was received from the local TCP/IP stack, the packet was filtered because it indicated an incorrect VLAN membership. This must not occur. Contact Technical Support. Egress When the packet attempted to leave through the wired Ethernet interface, the packet was filtered because it indicated an incorrect VLAN membership. Local Egress When the packet attempted to reach the local TCP/IP stack, the packet was filtered because it indicated an incorrect VLAN membership. Page 9-37 Chapter 9: Operation Interpreting Data VC statistics System statistics The Statistics > Data VC page displays information about Virtual Channel (VC) used in data communications. This page is applicable for all modules (AP/SM/BHM/BHS). The Data VC tab displays the fields as explained in Table 201. Table 201 Data VC page attributes Attribute Meaning Subscriber This field displays the LUID (logical unit ID), MAC address and Site Name of the SM/BHS. As each SM or BHS registers to the AP/BHM, the system assigns an LUID of 2 or a higher unique number to the SM/BHS. If a SM/BHS loses registration with the AP/BHM and then regains registration, the SM/BHS retains the same LUID. VC This field displays the virtual channel number. Low priority channels start at VC18 and count up. High priority channels start at VC255 and count down. If one VC is displayed, the high-priority channel is disabled. If two are displayed, the high-priority channel is enabled. CoS This field displays the Class of Service for the virtual channel. The low priority channel is a CoS of 00 and the high priority channel is a CoS of 01. CoS of 02 through 07 are not currently used. Inbound Statistics, This field displays how many octets were received on the interface, octets including those that deliver framing information. Inbound Statistics, This field displays how many inbound subnetwork-unicast packets were ucastpkts delivered to a higher-layer protocol. Inbound Statistics, This field displays how many inbound non-unicast (subnetwork-

nucastpkts broadcast or subnetwork-multicast) packets were delivered to a higher-

layer protocol. Page 9-38 Chapter 9: Operation System statistics Inbound Statistics, This field displays how many inbound packets were discarded without discards errors that would have prevented their delivery to a higher-layer protocol. Inbound discard statistics are incremented similar to the indiscards stat on the RF control block stats page. The sum of all data VC indiscards must be close to the RF control block in discards. If indiscards are evenly distributed across SMs, then the radio is PPS limited due to either excessive small packet transmissions, or a problem at the Ethernet link. If indiscards are contained to one or a few SMs, then there is likely a problem at or underneath the SM which is incrementing the count. Inbound Statistics, This field displays how many inbound packets contained errors that errors prevented their delivery to a higher-layer protocol. Inbound Statistics, This field displays how many inbound fragments were received via the QPSK frgmts QPSK modulation scheme. Inbound Statistics, This field displays how many inbound fragments were received via the 16-QAM frgmts 16-QAM modulation scheme. Inbound Statistics, This field displays how many inbound fragments were received via the 64-QAM frgmts 64-QAM modulation scheme. Inbound Statistics, This field displays how many inbound fragments were received via the 256-QAM frgmts 256-QAM modulation scheme. Outbound Statistics, This field displays how many octets were transmitted out of the octets interface, including those that deliver framing information. Outbound Statistics, This field displays how many packets for which the higher-level ucastpkts protocols requested transmission to a subnetwork-unicast address. The number includes those that were discarded or not sent. Outbound Statistics, This field displays how many packets for which the higher-level nucastpkts protocols requested transmission to a non-unicast (subnetwork-

broadcast or subnetwork-multicast) address. The number includes those that were discarded or not sent. Outbound Statistics, This field displays how many outbound packets were discarded without discards errors that would have prevented their transmission. Outbound discard statistics are incremented if a VC is not active when a packet is ready to send. This is a rare condition. Outbound Statistics, This field displays how many outbound packets contained errors that errors prevented their transmission. Page 9-39 Chapter 9: Operation System statistics Queue Overflow This is a count of packets that were discarded because the queue for the VC was already full. If Queue Overflows are being seen across most or all SMs, then there is either an interferer local to the AP or the APs RF link is at capacity. If Queue Overflows are being seen at one or only a few SMs, then it is likely that there is a problem with those specific links whether it is insufficient signal strength, interferer, or a problem with the actual SM hardware. High Priority Queue This is a count of packets that were received on high priority queue. Interpreting Throughput statistics The PMP/PTP 450 platform has a Statistics > Throughput page which shows historical information about sector or backhaul throughput and packet discards. This page is applicable for AP and BHM modules. This information can be useful to identify an overloaded sector or heavy bandwidth users. This page also shows the user throughput in terms of data rate (kbps) and packet rate

(packets per second, or PPS), as well as the average packet size during the sample period. Operators may set the AP/BHM to send an SNMP trap when it detects an RF overload condition based on a configurable threshold. The following configuration parameters are available on the Throughput tab GUI pane and a radio reboot is not required when configuring these parameters:

Table 202 RF overload Configuration attributes AP/BHM Attribute Meaning Throughput Monitoring This enables or disables the monitoring of sector throughput and packet discards. This parameter is disabled by default. SNMP Trap on RF This enables or disables the sending of an SNMP trap when an AP/BHM Overload overload condition is reached (based on Downlink RF Overload Threshold). Downlink RF This parameter determines the overload threshold in percent of packets Overload Threshold discarded that triggers the generation of an SNMP trap. Page 9-40 Chapter 9: Operation System statistics Downlink RF Link This field displays the status of the capacity of the RF link. Status Time Period Length These two configuration parameters determine what set of collection Time Period Ending samples to show on the GUI display. The Time Period Length can be set from one to three hours. Time Period Ending allows the operator to set the end time for the set of collection samples to display. Below the configuration settings are three tables that display the statistics that are collected. Board Performance statistics This table contains a row that corresponds to each 1 minute statistics collection interval. Each row contains the following data aggregated for the entire AP/BHM:

Ethernet Throughput - Statistics collected at the Ethernet port:

o kbps in average throughput over the collection interval in Kbps into the AP/BHM on the Ethernet Interface o kbps out average throughput over the collection interval in Kbps out of the AP/BHM on the Ethernet Interface o PPS in average packets per second over the collection interval into the AP/BHM on the Ethernet Interface o PPS out average packets per second over the collection interval out of the AP/BHM on the Ethernet Interface RF Throughput - Statistics collected at the RF Interface:

o kbps in average throughput over the collection interval in Kbps into the AP/BHM on the RF Interface o kbps out average throughput over the collection interval in Kbps out of the AP/BHM on the RF Interface o PPS in average packets per second over the collection interval into the AP/BHM on the RF Interface o PPS out average packets per second over the collection interval out of the AP/BHM on the RF Interface Aggregate Through Board Sum of bidirectional data transferred through (not originating or terminating at) the AP/BHM:

o kbps average bidirectional throughput over the collection interval in Kbps o PPS average bidirectional packets per second over the collection interval o Ave Pkt Size Average Packet size over the collection interval of bidirectional data transferred Board Throughput statistics This table contains a row that corresponds to each one minute statistics collection interval. This table may be used to determine if there are problems with any of the interfaces. For example, if the Ethernet in packets is much higher than the RF out packets it could indicate a denial of service

(DoS) attack on the AP/BHM. Each row contains the following data aggregated for the entire AP/BHM:

Page 9-41 Chapter 9: Operation System statistics Ethernet Statistics - Statistics collected at the Ethernet port:

o inOctets Number of octets (bytes) received by the AP/BHM at the Ethernet Interface over the collection interval o outOctets Number of octets (bytes) sent by the AP/BHM at the Ethernet Interface over the collection interval o inPkts Number of packets received by the AP/BHM at the Ethernet Interface over the collection interval o outPkts Number of packets sent by the AP/BHM at the Ethernet Interface over the collection interval o Discards (in/out) Number of packets that had to be discarded by the AP/BHM at the respective Ethernet Interface Queue RF Statistics - Statistics collected at the RF Interface:

o inOctets Number of octets (bytes) received by the AP/BHM at the RF Interface over the collection interval o outOctets Number of octets (bytes) sent by the AP/BHM at the RF Interface over the collection interval o inPkts Number of packets received by the AP/BHM at the RF Interface over the collection interval o outPkts Number of packets sent by the AP/BHM at the RF Interface over the collection interval o Discards (in/out) Number of packets that had to be discarded by the AP/BHM at the respective RF Interface Queue during the collection interval o Discards % (in/out) Percent of the total packets received / transmitted that had to be discarded during the collection interval LUID RF Throughput statistics This table contains a row that corresponds to each active LUID served by the AP/BHM. Note that an LUID may be assigned 1 or 2 VCs. If the LUID is assigned 2 VCs, then the data in the table is the sum of the activity for both VCs. This table may be used to determine which LUIDs are experiencing overload so that corrective action can be taken (i.e. fixing a poor RF link or moving a heavily loaded link to a less congested AP/BHM). Each row contains counters and statistics related to the RF Interface that are updated once per minute:

Inbound Statistics - Statistics collected at the RF Interface for the Uplink:

o octets Number of octets (bytes) received by the AP/BHM at the RF Interface for this LUID over the collection interval o pkts Number of packets received by the AP/BHM at the RF Interface for this LUID over the collection interval o Ave Pkt Size Average size of the packets received by the AP/BHM at the RF Interface for this LUID over the collection interval o discards Number of packets received by the AP/BHM at the RF Interface for this LUID over the collection interval that had to be discarded because the RF In Queue was full o discards % Percent of the total packets received by the AP/BHM at the RF Interface for this LUID over the collection interval that had to be discarded because the RF In Queue was full Outbound Statistics - Statistics collected at the RF Interface for the Downlink:

o octets Number of octets (bytes) transmitted by the AP/BHM at the RF Interface for this LUID over the collection interval Page 9-42 Chapter 9: Operation System statistics o pkts Number of packets transmitted by the AP/BHM at the RF Interface for this LUID over the collection interval o Ave Pkt Size Average size of the packets transmitted by the AP/BHM at the RF Interface for this LUID over the collection interval o discards Number of packets to be transmitted by the AP/BHM at the RF Interface for this LUID over the collection interval that had to be discarded because the RF Out Queue was full o discards % Percent of the total packets to be transmitted by the AP/BHM at the RF Interface for this LUID over the collection interval that had to be discarded because the RF Out Queue was full. Interpreting Overload statistics The Statistics > Overload page displays statistics on packet overload and resultant packet discards. Unlike the other fields, the Total Packets Overload Count is expressed in only this page. It is not a count of how many packets have been lost, but rather of how many discard events (packet loss bursts) have been detected due to overload condition. This statistics page is applicable for all modules (AP/SM/BHM/BHS) and explained in Table 203. Table 203 Overload page attributes AP/SM/BHM/BHS Attribute Meaning Total Packets This field represents the sum of all RF and Ethernet in/out discards. Overload Count Ethernet In Discards This field represents the number of packets tossed due to the Ethernet queue being full. If a climb in this stat accompanies a climb in RF Out Discards stat, then most likely the board is at RF capacity either due to traffic exceeding the RF pipe, or interference temporarily limiting the RF throughput. If this stat climbs without the RF Out Discards stat climbing, then the radio is most likely PPS limited. Page 9-43 Chapter 9: Operation System statistics Ethernet Out This field represents the number of packets tossed due to an Ethernet Discards out overload. This stat must not climb in normal operation because the Ethernet link is much higher capacity than the RF link. If this stat is incrementing, then either the Ethernet link is established at a low speed

(i.e. 10Mbps half duplex), or there is a problem with cabling/Ethernet hardware. RF In Discards This field indicates the number of packets tossed due to no resources available within the radio to process them. This stat also must not be increasing because the system is designed to shed packets on the RF Out interface. If this stat is incrementing the board, it is most likely congested due to high PPS rate in combination with an Ethernet Out problem, which limits packet flow off the device. RF Out Discards This field indicates the number of packets tossed due to RF link at capacity. This stat will increase whenever the RF link is at capacity. When the internal FPGA RF input queue overflows, this stat is incremented. If this stat is seen to be incrementing at the AP, then the sector is congested. If seen at the SM, the number of Contention Slots must be looked at to ensure that enough Contention Slots are allocated to allow for bandwidth requests to be seen at the AP. Interpreting DHCP Relay statistics The Statistics > DHCP Relay page displays requests and replies received, relayed and discarded when the AP is configured as a DHCP relay. Typically, in a working DHCP relay configuration a one-to-one ratio is established between requests and replies that are received and relayed. This statistics page is only applicable for PMP (AP and SM modules) and it is explained in Table 204. Table 204 DHCP Relay page attributes AP/SM Page 9-44 Chapter 9: Operation System statistics Attribute Meaning Requests Received This field represents the number of DHCP relay requests received by the AP. Requests Relayed This field represents the number of DHCP relay requests relayed by the AP. Requests Discarded This field represents the number of DHCP relay requests discarded by the AP due to errors in the request. Replies Received This field represents the number of DHCP relay replies received by the AP. Replies Relayed This field represents the number of DHCP relay replies relayed by the AP. Replies Discarded This field represents the number of DHCP relay replies discarded by the AP due to errors in the reply. Untrusted Message This field indicates messages that were discarded because the message Discards already contained Option 82 information with no Relay Agent specified. Max Hop Exceeded This field indicates messages that have been relayed too many times, Discards exceeding the max hop count (16). Invalid Relay Agent This field indicates messages that have been discarded because the Address Discards message relay agent address is already in place (relay agent address does not equal address of the AP). Relay Info Exceeding This field indicates DHCP messages too large to fit Option 82 data. These Max Message Size messages are sent on without Option 82 information.

(DHCP message relayed without Option 82) Page 9-45 Chapter 9: Operation Interpreting Filter statistics System statistics The Statistics > Filter page displays statistics on packets that have been filtered (dropped) due to the filters set on the Protocol Filtering page. The filter page of SM is explained in Table 205. Table 205 Filter page attributes - SM Attribute Meaning PPPoE Count Number of PPoE packets filtered. All IPv4 Count Number of IPv4 packets filtered. All Other IPv4 Count Any IPv4 message that was not SMB, SNMP, Bootp, Multicast or one of the user defined filters, that was filtered out. SMB Count Number of IPv4 Server Message Block (file sharing) packets filtered. SNMP Count Number of IPv4 SNMP packets filtered. Bootp Client Count Total number of IPv4 DHCP requests filtered. Bootp Server Count Total number of IPv4 DHCP replies filtered. IPv4 Multicast Count Number of IPv4 Multicast messages filtered. All IPv6 Count Number of IPv6 messages filtered. All Other IPv6 Count Any IPv6 message that was not SMB, SNMP, Bootp, Multicast or one of the user defined filters, that was filtered out. IPv6 SMB Count Number of IPv6 Server Message Block (file sharing) packets filtered IPv6 SNMP Count Number of IPv6 SNMP messages filtered IPv6 Bootp Client Count Total number of IPv6 DHCP replies filtered IPv6 Bootp Server Count Total number of IPv6 DHCP replies filtered IPv6 Multicast Count Number of IPv6 Multicast messages filtered Page 9-46 Chapter 9: Operation System statistics ARP Count Total number of ARP packets filtered. All other Count The count of any messages that did not fit above that were filtered out User Defined Port1 Count Number of packets defined by the user port1 that were filtered. User Defined Port2 Count Number of packets defined by the user port2 that were filtered. User Defined Port3 Count Number of packets defined by the user port3 that were filtered. Viewing ARP statistics The Statistics > ARP page in a SM module correlated the IP address of the Ethernet-connected device to its MAC address and provides data about the connection. Figure 172 ARP page of the SM Viewing NAT statistics When NAT is enabled on a SM, statistics are kept on the Public and Private (WAN and LAN) sides of the NAT and displayed on the Statistics > NAT Stats page. The NAT page of SM is explained in Table 206. Page 9-47 Chapter 9: Operation Table 206 NAT page attributes - SM System statistics Attribute Meaning Private NAT Statistics, This field represents the number of packets received on the SMs Packet In Count LAN/Ethernet interface Private NAT Statistics, This field represents the number of packets sent from the SMs Packet Out Count LAN/Ethernet interface Private NAT Statistics, This field represents the number of packets that we not sent from the Packet Out Toss Count SMs LAN/Ethernet interface due to addressing issues. Private NAT Statistics, This field represents the number of times the NAT table for the SMs Out of Resources Count LAN/Ethernet interfaces has been filled. Private NAT Statistics, This field represents the number of times that the device failed to Failed Hash Insert Count insert an address binding into the NAT hash table. Public NAT Statistics, This field represents the number of packets received on the SMs Packet In Count WAN/wireless interface Public NAT Statistics, This field represents the number of packets sent from the SMs Packet Out Count WAN/wireless interface Public NAT Statistics, This field represents the number of packets that we not sent from the Out of Resources Count SMs WAN/wireless interface due to addressing issues. Public NAT Statistics, This field represents the number of times the NAT table for the SMs Failed Hash Insert Count WAN/wireless interfaces has been filled. Page 9-48 Chapter 9: Operation Viewing NAT DHCP Statistics System statistics The Statistics > NAT DHCP page displays NAT enabled DHCP client statistics. This is statistics page is applicable for SM only. When NAT is enabled on a SM with DHCP client (DHCP selected as the Connection Type of the WAN interface) and/or DHCP Server, statistics are kept for packets transmitted, received and tossed, as well as a table of lease information for the DHCP server (Assigned IP Address, Hardware Address and Lease Remained/State). Table 207 NAT DHCP Statistics page attributes - SM Attribute Meaning PktXmt Count Represents the number of DHCP packets transmitted from the client PktRcv Count This field represents the number of DHCP packets received by the client PktToss This field represents the number of packets tossed due to failed attempts ARPUnresolved to resolve an IP address into a physical MAC address Overflow Count PktToss This field represents the number of packets tossed due to the receipt of Unsupported an unsupported message type (cannot be interpreted by DHCP client) MsgType Count PktToss XID The field represents the number of packets that were tossed due to a Mismatch Count transaction ID mismatch PktToss NoSID This field represents the number of packets that were tossed due to lack Count of a DHCP session ID PktToss SID Represents the number of packets tossed due to a session ID mismatch Mismatch Count Page 9-49 Chapter 9: Operation System statistics Failure to Reset This field represents the number of times the DHCP client was unable to Client Count be reset (resulting in no IP address being served). Interpreting Sync Status statistics The Statistics > Sync Status page of AP is only displayed when the Sync Input is set to AutoSync or AutoSync+Free Run. The Sync Status page is explained in Table 208. Table 208 Sync Status page attributes - AP Attribute Meaning Sync Pulse Source This field indicates the status of the synchronization source:

Searching indicates that the unit is searching for a GPS fix Timing Port/UGPS indicates that the module is receiving sync via the timing AUX/SYNC timing port Power Port indicates that the module is receiving sync via the power port (Ethernet port). Sync Pulse Status This field indicates synchronization source pulse status. Sync Pulse Status This field indicates synchronization pulse status over Timing Port/UGPS Timing Port/UGPS port. Sync Pulse Status -

This field indicates synchronization pulse status over power port. Power Port UGPS Power Status This field indicates UGPS power up status (on or off). This information may be helpful in a decision of whether to climb a tower to diagnose a perceived antenna problem. Page 9-50 Chapter 9: Operation System statistics Interpreting PPPoE Statistics for Customer Activities The page can be access under Statistics > PPPoE of SM GUI. When the PPPoE feature is enabled on the SM, PPPoE statistics provide data about activities of the customer. The PPPoE Statistics of SM is explained in Table 209. Table 209 PPPoE Statistics page attributes - SM Attribute Meaning IP address This field displays the IP address of the PPPoE session initiator (situated below the SM) PPPoE Session This field displays the operational status of the PPPoE Session Status PPPoE AC Name This field displays access concentrator name used in the PPPoE session PPPoE Service Name This field displays the PPPoE service name associated with the PPPoE server in use PPPoE Session ID This field displays the current PPPoE session ID PPPoE Session This field displays the total session uptime for the PPPoE session Uptime PPPoE Session Idle This field displays the total idle time for the PPPoE session Time PPPoE Session MTU This field displays Maximum Transmission Unit configured for the PPPoE session Primary DNS This field displays the primary DNS server used by the PPPoE session Address Secondary DNS This field displays the secondary DNS server used by the PPPoE session Address Page 9-51 Chapter 9: Operation System statistics PPPoE Control Bytes Displays the total number of PPPoE session control bytes sent from SM Sent PPPoE Control Bytes This field displays the total number of PPPoE session control bytes Received received by the SM PPPoE Data Session This field displays the total number of PPPoE data session (non-

Bytes Sent control/non-session management user data) sent by the SM PPPoE Data Session This field displays the total number of PPPoE data session (non-

Bytes Received control/non-session management user data) Interpreting Bridge Control Block statistics The Statistics > Bridge Control Block page displays statistics of Bridge FEC, Bridge ratio and Bridge error. The page is applicable for all modules (AP/SM/BHM/BHS). The Bridge Control Block Statistics page is explained in Table 210. Table 210 Bridge Control Block page attributes AP/SM/BHM/BHS Page 9-52 Chapter 9: Operation System statistics Attribute FEC bin Meaning This field indicates the number of broadcast packets received by the bridge control block on the Ethernet interface FEC bout This field indicates the number of broadcast packets sent by the bridge control block on the Ethernet interface FEC btoss This field indicates the number of broadcast packets tossed out by the bridge control block on the Ethernet interface FEC btosscap This field indicates the number of broadcast packets tossed out at the Ethernet interface due to MIR cap being exceeded. FEC uin This field indicates the number of unicast packets received by the bridge control block on the Ethernet interface FEC uout This field indicates the number of unicast packets sent by the bridge control block on the Ethernet interface FEC utoss This field indicates the number of unicast packets tossed by the bridge control block on the Ethernet interface FEC utosscap This field indicates the number of unicast packets tossed out at the Ethernet interface due to MIR cap being exceeded. RF bin This field indicates the number of broadcast packets received by the bridge control block on the radio interface RF bout This field indicates the number of broadcast packets sent by the bridge control block on the radio interface RF btoss This field indicates the number of broadcast packets tossed by the bridge control block on the radio interface RF btosscap This field indicates the number of broadcast packets tossed out at the radio interface due to MIR cap being exceeded. RF uin This field indicates the number of unicast packets received by the bridge control block on the radio interface RF uout This field indicates the number of unicast packets sent by the bridge control block on the radio interface RF utoss This field indicates the number of unicast packets tossed by the bridge control block on the radio interface RF utosscap This field indicates the number of unicast packets tossed out at the radio interface due to MIR cap being exceeded. ErrNI1QSend This field indicates that a packet which was sourced from the radio network stack interface 1 (Ethernet interface) could not be sent because the radio bridge queue was full. The packet was tossed out. Page 9-53 Chapter 9: Operation System statistics ErrNI2QSend This field indicates that a packet which was sourced from the radio network stack interface 2 (RF interface) could not be sent because the radio bridge queue was full. The packet was tossed out. ErrBridgeFull This field indicates the total number of times the bridging table was full and could not accept new entries. ErrSendMsg This field displays the error message from bridge core call back routine. ErrApFecQSend This field indicates that a packet which was received on the Ethernet interface could not be processed because the radio bridge queue was full and packet was tossed out. ErrApRfQSend This field indicates that a packet which was received on the RF interface could not be processed because the radio bridge queue was full. The packet was tossed out. Interpreting Pass Through Statistics The Statistics > Pass Through Statistics page displays radius related statistics. The page is applicable for PMP 450 platform AP only. The Pass Through Statistics page is explained in Table 211. Table 211 Pass Through Statistics page attributes AP Attribute Meaning IdentityReqSent This field indicates the number of EAP Identity requests sent through the AP with respect to an SM. PktsEncapsulated This field indicates no of packets received from the SM which are encapsulated by the AP. PktsDecasulated This field indicates no of packets received from the radius server and are decapsulated by the AP with respect to an SM AccessAcceptRcvd This field indicates no of RADIUS Access Accept message received by the AP with respect to an SM. Page 9-54 Chapter 9: Operation Interpreting SNMPv3 Statistics System statistics The Statistics > SNMPv3 Statistics page displays all SNMPv3 related statistics. The page is applicable for all platform of PMP 450 platform. The SNMPv3 Statistics page is explained in Table 212. Table 212 SNMPv3 Statistics page attributes AP Attribute Meaning Statistics for snmpMPDStats group SNMP Message Processing and Dispatching RFC 3412 Page 9-55 Chapter 9: Operation System statistics snmpUnknownSecurityM The total number of packets received by the SNMP engine which odels were dropped because they referenced a securityModel that was not known to or supported by the SNMP engine. snmpInvalidMsgs The total number of packets received by the SNMP engine which were dropped because there were invalid or inconsistent components in the SNMP message. snmpUnknownPDUHandl The total number of packets received by the SNMP engine which ers were dropped because the PDU contained in the packet could not be passed to an application responsible for handling the pduType, e.g. no SNMP application had registered for the proper combination of the contextEngineID and the pduType. usmStatsUnsupportedSec The total number of packets received by the SNMP engine which Levels were dropped because they requested a securityLevel that was unknown to the SNMP engine or otherwise unavailable. usmStatsNotInTimeWind The total number of packets received by the SNMP engine which ows were dropped because they appeared outside of the authoritative SNMP engine's window. usmStatsUnknownUserN The total number of packets received by the SNMP engine which ames were dropped because they referenced a user that was not known to the SNMP engine. usmStatsUnknownEngine The total number of packets received by the SNMP engine which IDs were dropped because they referenced a snmpEngineID that was not known to the SNMP engine. usmStatsWrongDigests The total number of packets received by the SNMP engine which were dropped because they didn't contain the expected digest value. usmStatsDecryptionError The total number of packets received by the SNMP engine which s were dropped because they could not be decrypted. snmpTargetSpinLock This object is used to facilitate modification of table entries in the SNMP-TARGET-MIB module by multiple managers. snmpUnavailableContext The total number of packets received by the SNMP engine which s were dropped because the context contained in the message was unavailable. snmpUnknownContexts The total number of packets received by the SNMP engine which were dropped because the context contained in the message was unknown. usmUserSpinLock The use of usmUserSpinlock is to avoid conflicts with another SNMP command generator application which may also be acting on the usmUserTable. Page 9-56 Chapter 9: Operation System statistics vacmViewSpinLock An advisory lock used to allow cooperating SNMP Command Generator applications to coordinate their use of the Set operation in creating or modifying views. snmpEngineBoots It is a count of the number of times the SNMP engine has re-

booted/re-initialized since snmpEngineID was last configured snmpEngineTime which is the number of seconds since the snmpEngineBoots time since engine is up counter was last incremented Interpreting syslog statistics The Statistics > Syslog Statistics page displays statistics of syslog messages. The page is applicable for all modules (AP/SM/BHM/BHS). The Syslog Statistics page is explained in Table 213. Table 213 Syslog statistics page attributes AP/SM/BH Attribute Meaning Syslog Server This displays dotted decimal or DNS name (if the DNS is enabled) of the syslog server address. Syslog Server Port The syslog server port (default 514) to which syslog messaging is sent. Syslog Status This indicates status of syslog messaging. It can be Enable or Disabled based on configuration Syslog Message Transmissions This field indicates the count of syslog messages sent to UDP layer. Syslog Message Dropped This field indicates the count of dropped syslog messages. Interpreting Frame Utilization statistics The Frame Utilization Statistics is a feature helps user to understand how effectively the RF channel is being utilized. This feature allows to check Time Division Duplex (TDD) frame utilization pattern and diagnose for any excessive usage in uplink or downlink direction. This forms the first step of identifying the TDD frame utilization information. If the user finds excessive utilization based on this stats, the second step would be to take several actions like sectorization, tuning the uplink/downlink ratio etc. to improve RF channel utilization. Efficient use of the TDD frame will help to achieve optimum performance of link. Page 9-57 Chapter 9: Operation Note:

System statistics The backhauls (BHM and BHS) will have only the downlink scheduler based statistics Table 214 Frame utilization statistics Attribute Meaning Frame Utilization Interval Statistics Display interval This allows to configure timer interval to monitor and display the frame utilization statistics. It can be configured for 30 seconds

(low interval), 3 minutes (medium interval) or 15 minutes (high interval) based on requirement. Frame Utilization Downlink This indicates the percentage of downlink data slots used against the maximum number of slots possible in configured interval. Page 9-58 Chapter 9: Operation System statistics Uplink This indicates the percentage of uplink data slots used against the maximum number of uplink slots possible in configured Downlink Counts interval. Total This indicates the sum of all downlink data slots used in the configured interval. Low Priority The number of downlink data slots used for low priority downlink traffic. High Priority The number of downlink data slots used for high priority downlink traffic. Broadcast/Multicast The number of downlink data slots used for broadcast and multicast traffic. Canopy MAC The number of downlink data slots used as ACKs. Acknowledgements Registration and Control The number of downlink data slots used for registration and message slots other control messages. Uplink Counts Total This indicates the sum of all uplink data slots used in configured interval. Low Priority The number of uplink data slots used for low priority uplink traffic. High Priority The number of uplink data slots used for high priority uplink traffic. Canopy MAC The number of uplink data slots used as ACKs. Acknowledgements Contention Slots The number of (reserved) Contention slots configured by the operator. Contention Slots Average It is the average number of contention slots in a frame for the Per Frame last duration. Duration is 1/5/15 mins. Maximum possible counts Downlink This indicates the maximum possible downlink data slots. This is based on the configuration of Channel Bandwidth, Frame period, uplink/downlink allocation, contention slots and configured Statistics Display interval. Page 9-59 Chapter 9: Operation System statistics Uplink This indicates the maximum possible uplink data slots. This is based on the configuration of Channel Bandwidth, Frame period, uplink/downlink allocation, contention slots and configured Statistics Display interval. Packet Discard counts Ethernet indiscards This indicates the number of Ethernet packets discarded in the IN queue. Ethernet outdiscards This indicates the number of Ethernet packets discarded in the OUT queue. Radio indiscards This indicates the number of packets discarded over radio in the IN queue. Radio outdiscards This indicates the number of packets discarded over radio in the OUT queue. Page 9-60 Chapter 9: Operation Radio Recovery This section describes:

Radio Recovery How to recover a PMP/PTP 450i unit from configuration errors or software image corruption How to override a PMP/PTP 450 unit from forgotten IP address and password to factory default Radio Recovery Console PMP/PTP 450i Recovery mode allows to restore IP address and password. Also, it 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 a software upgrade. Note When Recovery has been entered through a power on/off/on cycle, the ODU will revert to normal operation if no web access has been made to the unit within 30 seconds. This prevents the unit remaining inadvertently in recovery following a power outage. Options in recovery mode are:

Boot with normal operation Boot with default Canopy system software settings Load a previous SW image The last most recent software images loaded to the board are retained. However the factory image is not retained. Boot with default Canopy system software settings (similar to the hardware Ddefault Plug based on PMP/PTP 450 platforms). Note The unit may enter recovery console automatically, in response to some failures. Note Once the unit has entered recovery, it will switch back to normal operation if no access has been made to the recovery web page within 30 seconds. Use below procedure to enter in recovery console manually. Page 9-61 Chapter 9: Operation Procedure 34 Radio Recovery Console 1 Apply power to PSU for at least 10 seconds. 2 Remove power for two seconds. 3 Re-apply power to the PSU. Radio Recovery 4 When the unit is in recovery mode, access the web interface by entering the default IP address 169.254.1.1. The Recovery Image Warning page is displayed. 5 Review the Boot Selection (Table 215). 6 Select a recovery option Figure 173 Recovery Options page Table 215 Recovery Options attributes Attribute Meaning Boot Selection Boot Default Mode: Use this option to temporarily set the IP and Ethernet attributes to factory defaults until the next reboot. Boot Normal: Use this option to reboot the unit. IP address, Netmask, These fields display IP address, Netmask and Gateway of the radio while Gateway it is in recovery or default mode. Page 9-62 Chapter 9: Operation Radio Recovery Default Mode (or Default/Override Plug) - PMP/PTP 450 The default mode allows to temporarily override some PMP/PTP 450 ODU settings and thereby regain control of the module by powering the module on with the Default Plug inserted into the units synchronization (RJ11) port. This override plug is needed for access to the module in any of the following cases:

You have forgotten either o o the IP address assigned to the ODU. the password that provides access to the ODU. The ODU has been locked by the No Remote Access feature. You want local access to a module that has had the 802.3 link disabled in the Configuration page. You can configure the module such that, when it senses the override plug, it responds by either resetting the LAN1 IP address to 169.254.1.1, allowing access through the default configuration without changing the configuration, whereupon you will be able to view and reset any non-

default values as you wish. resetting all configurable parameters to their factory default values. Note The Default Plug is available from Best-Tronics Manufacturing, Inc. See http://www.best-tronics.com/cambium.htm as Part BT-0583 (RJ-11 Default Plug). Alternatively, you can fabricate an override plug. See Override plug cable on page 5-14 for pinout. Using the Default/Override Plug The following section details usage of the override plug to regain access to PMP/PTP 450 ODU. Note While the override plug is connected to a PMP/PTP 450 ODU, the ODU can neither register nor allow registration of another ODU. Note Since the 900 MHz SM is based on the 450 platform, it only supports the "Default Plug"

mode of overriding. Page 9-63 Chapter 9: Operation Use below procedure to enter in default mode manually. Procedure 35 Default mode Radio Recovery 1 2 Insert the override plug into the RJ-11 GPS utility port of the module. Power cycle by removing, then re-inserting, the Ethernet cable. RESULT: The module boots with the default IP address of 169.254.1.1, password fields blank, and all other configuration values as previously set. 3 Wait approximately 30 seconds for the boot to complete. 4 5 6 7 8 Remove the override plug. Set passwords and IP address as desired. Change configuration values if desired. Click the Save Changes button. Click the Reboot button. Page 9-64 Chapter 10: Reference Information This chapter contains reference information and regulatory notices that apply to the PMP/PTP 450 platform Series products. The following topics are described in this chapter:

Equipment specifications on page 10-2 contains specifications of the PMP/PTP 450 platform, ODU specifications including RF bands, channel width and link loss. Data network specifications on page 10-33 shows the PMP/PTP 450 platform Ethernet interface specifications. Compliance with safety standards on page 4-22 lists the safety specifications against which the PMP/PTP 450 platform has been tested and certified. It also describes how to keep RF exposure within safe limits. Country specific radio regulations on page 10-35 describes how the PMP/PTP 450 platform complies with the radio regulations that are enforced in various countries. Equipment Disposal on page 10-37 describes the Equipment Disposal system for Electronic and Electric Equipment. Page 10-1 Chapter 10: Reference Information Equipment specifications Equipment specifications This section contains specifications of the AP, SM, BHM and BHS associated supplies required for PMP/PTP 450 platform installations. Specifications for PMP 450m AP The PMP 450m AP conforms to the specifications listed in Table 216. Table 216 PMP 450m AP specifications Category Model Number Spectrum Channel Spacing Frequency Range Channel Bandwidth Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Specification PMP 450m AP Configurable on 2.5 MHz increments 5150 to 5925 MHz 20 MHz Cambium Proprietary 14x14 Multi-User MIMO OFDM 100/1000BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID Nominal Receive 5.1 GHz 1x-A = -88 dBm, 2x-A = -81 dBm, 3x-A = -75 dBm, 4x-A Sensitivity (w/ FEC) @

20 MHz Channel

= -67 dBm, 2x-B = -85 dBm, 4x-B = -78 dBm, 6x-B = -72 dBm, 8x-B = -64 dBm 5.2 GHz 1x-A = -88 dBm, 2x-A = -81 dBm, 3x-A = -75 dBm, 4x-A

= -67 dBm, 2x-B = -85 dBm, 4x-B = -78 dBm, 6x-B = -72 dBm, 8x-B = -64 dBm Page 10-2 Chapter 10: Reference Information Equipment specifications 5.4 GHz 1x-A = -88 dBm, 2x-A = -81 dBm, 3x-A = -75 dBm, 4x-A

= -67 dBm, 2x-B = -85 dBm, 4x-B = -78 dBm, 6x-B = -72 dBm, 8x-B = -64 dBm 5.8 GHz 1x-A = -88 dBm, 2x-A = -81 dBm, 3x-A = -75 dBm, 4x-A

= -67 dBm, 2x-B = -85 dBm, 4x-B = -78 dBm, 6x-B = -72 Performance Subscriber Per Sector ARQ Cyclic Prefix Frame Period dBm, 8x-B = -64 dBm Up to 238 Yes 1/16 2.5 ms or 5.0 ms Modulation Levels (Adaptive) Modution Levels MCS SNR (in dB) 2x 4x 6x 8x QPSK 16QAM 64QAM 256QAM 10 17 24 32 Latency 10 ms, typical Maximum Deployment Range Up to 40 miles (64 km) GPS Synchronization Quality of Service Link Budget Yes, via Autosync (CMM5 or UGPS) Diffserv QoS Antenna Beam Width 5 GHz 90 integrated sector (Dual polarity, H+V) Antenna Gain Maximum Transmit Power Physical

+14 dBi

+24 dBm combined Data, Sync/AUX and RJ45 1000BASE-T Ethernet Data SFP port AUX port for uGPS or PoE out to 802.3at SFP Single-mide fiber, multi-mode fiber and copper Gigabit Ethernet option Antenna Connection Integrated Sector Array Page 10-3 Chapter 10: Reference Information Equipment specifications Surge Suppression

(with LPU) Mean Time Between Failure Environmental Temperature /

Humidity EN61000-4-5: 1.2 us/50 us, 500 V voltage waveform Recommended external surge suppressor:

Cambium Networks Model # C000065L007A

> 40 Years IP66, IP67

-40C to +60C (-40F to +140F) 0-95% non-condensing Weight Integrated Approx. 14.2 kg (31 bs) Wind Loading Front

@90 mph / 144 kph 460 N Facing

@110 mph /177 kph 700 N Dimension (HxWxD) Integrated 52 x 65 x 11 cm (20.3 x 25.7 x 4.4) Power Consumption Input Voltage Mounting Security Encryption 70 W typical, 80 W peak

(up to 110 W max with AUX port PoE enabled) 58 V, 1.7 A Pole mount with included brackets 56-bit DES, FIPS-197 128-bit AES Page 10-4 Chapter 10: Reference Information Equipment specifications Specifications for PMP 450i AP The PMP 450i AP conforms to the specifications listed in Table 217. Table 217 PMP 450i AP specifications Category Model Number Spectrum Channel Spacing Frequency Range Specification PMP 450i AP 5, 7, 10, 15, 20 and 30 MHz Channel Bandwidth Configurable on 2.5 MHz increments 902 to 928 MHz 4900 - 5925 MHz Channel Bandwidth 902 928 MHz 5, 7, 10 and 20 MHz 4900 5925 5, 7, 10, 15, 20 and 30 MHz MHz Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Cambium Proprietary 2x2 MIMO OFDM 10/100/1000BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID Nominal Receive 900 MHz 1x = -91.9 dBm, 2x = -86.7 dBm, 4x = -80.9 dBm, 6x = -

Sensitivity (w/ FEC) @

5 MHz Channel 75 dBm, 8x = -68.8 dBm 4.9 GHz 1x = -91.6 dBm, 2x = -87.6 dBm, 4x = -80.4 dBm, 6x = -

73.2 dBm, 8x = -66 dBm 5.4 GHz 1x = -92 dBm, 2x = -87 dBm, 4x = -80.8 dBm, 6x = -73.7 dBm, 8x = -66.6 dBm 5.8 GHz 1x = -91.5 dBm, 2x = -87 dBm, 4x = -80.2 dBm, 6x = -

73.1 dBm, 8x = -66 dBm Page 10-5 Chapter 10: Reference Information Equipment specifications Nominal Receive 900 MHz 1x = -90 dBm, 2x = -85.9 dBm, 4x = -79.8 dBm, 6x = -

Sensitivity (w/ FEC) @

7 MHz Channel 73.6 dBm, 8x = -67.9 dBm Nominal Receive 900 MHz 1x = -90.6 dBm, 2x = -85.2 dBm, 4x = -79.1 dBm, 6x = -

Sensitivity (w/ FEC) @

10 MHz Channel 73.2 dBm, 8x = -66.2 dBm 4.9 GHz 1x = -89.1 dBm, 2x = -85 dBm, 4x = -77.9 dBm, 6x = -

71.8 dBm, 8x = -64.6 dBm 5.4 GHz 1x = -89.5 dBm, 2x = -85.4 dBm, 4x = -78.2 dBm, 6x = -

72.2 dBm, 8x = -64.8 dBm 5.8 GHz 1x = -89.5 dBm, 2x = -84.7 dBm, 4x = -77.8 dBm, 6x = -

71.6 dBm, 8x = -64 dBm Nominal Receive 4.9 GHz 1x = -87.2 dBm, 2x = -83 dBm, 4x = -75.8 dBm, 6x = -

Sensitivity (w/ FEC) @

15 MHz Channel 69.6 dBm, 8x = -62.6 dBm 5.4 GHz 1x = -87.2 dBm, 2x = -83.3 dBm, 4x = -76.2 dBm, 6x = -

70.1 dBm, 8x = -63 dBm 5.8 GHz 1x = -87.7 dBm, 2x = -82.7 dBm, 4x = -75.5 dBm, 6x = -

69.6 dBm, 8x = -62.4 dBm Nominal Receive 900 MHz 1x = -86.99 dBm, 2x = -82 dBm, 4x = -75.9 dBm, 6x = -

Sensitivity (w/ FEC) @

20 MHz Channel 69.9 dBm, 8x = -62.9 dBm 4.9 GHz 1x = -86.1 dBm, 2x = -82.1 dBm, 4x = -74.8 dBm, 6x = -

68.8 dBm, 8x = -61.7 dBm 5.4 GHz 1x = -86.6 dBm, 2x = -81.3 dBm, 4x = -75.5 dBm, 6x = -

68.6 dBm, 8x = -62 dBm 5.8 GHz 1x = -85.8 dBm, 2x = -80.7 dBm, 4x = -74.6 dBm, 6x = -

68.7 dBm, 8x = -61 dBm Nominal Receive 4.9 GHz 1x = -84.1 dBm, 2x = -80 dBm, 4x = -73 dBm, 6x = -66.4 Sensitivity (w/ FEC) @

30 MHz Channel dBm, 8x = -59.6 dBm 5.4 GHz 1x = -84.5 dBm, 2x = -82 dBm, 4x = -75 3.5Bm, 6x = -

67.4 dBm, 8x = -60.2 dBm 5.8 GHz 1x = -84.1 dBm, 2x = -80 dBm, 4x = -73 dBm, 6x = -66.5 dBm, 8x = -59.4 dBm Page 10-6 Chapter 10: Reference Information Equipment specifications Performance ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Latency Maximum Deployment Range GPS Synchronization Quality of Service Link Budget Yes 1/16 2.5 ms or 5.0 ms Modution Levels MCS SNR (in dB) 2x 4x 6x 8x QPSK 16QAM 64QAM 256QAM 10 17 24 32 3 - 5 ms Up to 40 miles (64 km) Yes, via Autosync (CMM4), via UGPS Diffserv QoS Antenna Beam Width 900 MHz 65 sector antenna (Dual Slant) 5 GHz 90 (3dB rolloff) sector for integrated (Dual polarity, H+V) Antenna Gain (Does 900 MHz 13 dBi not include cable loss,

~1dB) Transmit Power Range Maximum Transmit Power Physical 5 GHz 17 dBi integrated 90 sector or external 40 dB dynamic range (to EIRP limit by region) (1 dB step)

+27 dBm combined output (for 5 GHz)

+25 dBm combined output (for 900MHz) Sync/AUX port RJ45 10/100/100BASE-T Ethernet Data PoE output (planned for future release) Sync input or output (Connection and powering of UGPS Sync input) Antenna Connection 50 ohm, N-type (Connectorized version only) Page 10-7 Chapter 10: Reference Information Equipment specifications Surge Suppression EN61000-4-5 Mean Time Between Failure Environmental Temperature /

Humidity EN61000-4-5: 1.2 us/50 us, 500 V voltage waveform Recommended external surge suppressor: Cambium Networks Model # C000000L033A

> 40 Years IP66, IP67

-40C to +60C (-40F to +140F), 0-95% non-

condensing Weight Connectorized Approx. 2.0 kg (4.5 lbs) Integrated Approx. 2.5 kg (5.5 lbs) Wind Survival Connectorized 322 km/h (200 mi/h) Integrated 200 km/h (124 mi/h) Dimension(HxWxD) Connectorized 26.0 x 13.4 x 6.4 cm (10.3 x 5.3 x 3.3) Integrated 37.0 x 37.0 x 6.3 cm (14.5 x 14.5 x 3.2) Power Consumption Input Voltage Mounting Security Encryption 15 W typical, 25 W max, 55 W max with Aux port PoE out enabled 48-59 V DC, 802.3at compliant Wall or Pole mount with Cambium Networks Model #

N000045L002A 56-bit DES, FIPS-197 128-bit AES Page 10-8 Chapter 10: Reference Information Equipment specifications Specifications for PMP 450i SM The PMP 450i SM conforms to the specifications listed in Table 218. Table 218 PMP 450i SM specifications Category Model Number Spectrum Channel Spacing Frequency Range Specification PMP 450i SM 5, 10, 15, 20 and 30 Channel Bandwidth Configurable on 2.5 MHz increments 4900 - 5925 MHz Channel Bandwidth 4900 5925 5, 10, 15, 20 and 30 MHz MHz Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Cambium Proprietary 2x2 MIMO OFDM 10/100/1000BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v2c and v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID Nominal Receive 4.9 GHz 1x = -92.5 dBm, 2x = -88.5 dBm, 4x = -81 dBm, 6x = -

Sensitivity (w/ FEC) @

5 MHz Channel 74.2 dBm, 8x = -66 dBm 5.4 GHz 1x = -93 dBm, 2x = -89.1 dBm, 4x = -81.5 dBm, 6x = -

74.8 dBm, 8x = -67.4 dBm 5.8 GHz 1x = -92 dBm, 2x = -88.3 dBm, 4x = -80.8 dBm, 6x = -74 dBm, 8x = -66.2 dBm Nominal Receive 4.9 GHz 1x = -90.2 dBm, 2x = -85.2 dBm, 4x = -78.8 dBm, 6x = -

Sensitivity (w/ FEC) @

10 MHz Channel 71.4 dBm, 8x = -64.5 dBm 5.4 GHz 1x = -90d Bm, 2x = -85.8 dBm, 4x = -78.5 dBm, 6x = -

72.2 dBm, 8x = -65.8 dBm Page 10-9 Chapter 10: Reference Information Equipment specifications 5.8 GHz 1x = -89.9 dBm, 2x = -84.9 dBm, 4x = -78.5 dBm, 6x = -

71.2 dBm, 8x = -63.8 dBm Nominal Receive 4.9 GHz 1x = -88.2 dBm, 2x = -83.1 dBm, 4x = -76.9 dBm, 6x = -

Sensitivity (w/ FEC) @

15 MHz Channel 70.5 dBm, 8x = -62.3 dBm 5.4 GHz 1x = -87.7 dBm, 2x = -83.9 dBm, 4x = -76.6 dBm, 6x = -

70.4 dBm, 8x = -63 dBm 5.8 GHz 1x = -88 dBm, 2x = -82.9 dBm, 4x = -76.7 dBm, 6x = -

69.4 dBm, 8x = -62.3 dBm Nominal Receive 4.9 GHz 1x = -87 dBm, 2x = -81.8 dBm, 4x = -75.8 dBm, 6x = -

Sensitivity (w/ FEC) @

20 MHz Channel 68.5 dBm, 8x = -61.4 dBm 5.4 GHz 1x = -87 dBm, 2x = -82.8 dBm, 4x = -75.6 dBm, 6x = -

69.3 dBm, 8x = -61.6 dBm 5.8 GHz 1x = -85.9 dBm, 2x = -81.5 dBm, 4x = -74.8 dBm, 6x = -

68.7 dBm, 8x = -61.2 dBm Nominal Receive 4.9 GHz 1x = -84.9 dBm, 2x = -80.9 dBm, 4x = -73.2 dBm, 6x = -

Sensitivity (w/ FEC) @

30 MHz Channel 67.4 dBm, 8x = -59.3 dBm 5.4 GHz 1x = -85.2 dBm, 2x = -80.2 dBm, 4x = -74.1 dBm, 6x = -

67.9 dBm, 8x = -59.8 dBm 5.8 GHz 1x = -84.9 dBm, 2x = -80 dBm, 4x = -73.2 dBm, 6x = -

67.4 dBm, 8x = -59.4 dBm Performance ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Latency Yes 1/16 2.5 ms or 5.0 ms Modulation Levels MCS SNR (in dB) QPSK 16QAM 64QAM 256QAM 10 17 24 32 2x 4x 6x 8x 3 - 5 ms Page 10-10 Chapter 10: Reference Information Equipment specifications Maximum Deployment Range GPS Synchronization Quality of Service Link Budget Antenna Beam Width Up to 40 miles (64 km) Yes, via Autosync (CMM4) Diffserv QoS 10 azimuth for 23 dBi integrated antenna Antenna Gain (Does 5 GHz

+23 dBi H+V, integrated or external not include cable loss,

~1dB) Transmit Power Range Maximum Transmit Power Physical 40 dB dynamic range (to EIRP limit by region) (1 dB step)

+27 dBm combined output (for 5 GHz) Sync/AUX port RJ45 10/100/1000BASE-T Ethernet Data Antenna Connection Surge Suppression EN61000-4-5 Mean Time Between Failure Environmental Temperature /

Humidity PoE output (planned for future release) Sync input or output (Connection and powering of UGPS Sync input) 50 ohm, N-type (Connectorized version only) EN61000-4-5: 1.2us/50us, 500 V voltage waveform Recommended external surge suppressor: Cambium Networks Model # C000000L033A

> 40 Years IP66, IP67

-40C to +60C (-40F to +140F), 0-95% non-

condensing Weight Connectorized Approx. 2.0 kg (4.5 lbs) Integrated Approx. 2.5 kg (5.5 lbs) Wind Survival Connectorized 322 km/h (200 mi/h) Integrated 200 km/h (124 mi/h) Dimension(HxWxD) Connectorized 26.0 x 13.4 x 6.4 cm (10.3 x 5.3 x 3.3) Integrated 31.0 x 31.0 x 6.4 cm (12 x 12 x 2.5) Page 10-11 Chapter 10: Reference Information Equipment specifications Power Consumption Input Voltage Mounting Security Encryption 15 W typical, 25 W max, 55 W max with Aux port PoE out enabled 48-59 V DC, 802.3at compliant Wall or Pole mount with Cambium Networks Model #

N000045L002A 56-bit DES, FIPS-197 128-bit AES Page 10-12 Chapter 10: Reference Information Equipment specifications Specifications for PTP 450i BH The PTP 450i BH conforms to the specifications listed in Table 219. Table 219 PTP 450i BH specifications Category Model Number Spectrum Channel Spacing Frequency Range Specification PTP 450i BH 5, 10, 15, 20 and 30 MHz Channel Bandwidth Configurable on 2.5 MHz increments 902 to 928 MHz 4900 - 5925 MHz Channel Bandwidth 902 928 MHz 5, 7, 10 and 20 MHz 4900 5925 5, 10, 15, 20 and 30 MHz MHz Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Cambium Proprietary 2x2 MIMO OFDM 10/100/1000BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v2c and v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID Nominal Receive 900 MHz Sensitivity (w/ FEC) @

5 MHz Channel 4.9 GHz 1x = -93 dBm, 2x = -88 dBm, 4x = -81 dBm, 6x = -75 dBm, 8x = -68 dBm 1x = -93 dBm, 2x = -88.3 dBm, 4x = -82 dBm, 6x = -74.4 dBm, 8x = -67.9 dBm 5.4 GHz 5.8 GHz 1x = -93 dBm, 2x = -88.4 dBm, 4x = -81.3 dBm, 6x = -

75.5 dBm, 8x = -67.8 dBm 1x = -93.2 dBm, 2x = -88.3 dBm, 4x = -80.8 dBm, 6x = -

74.3 dBm, 8x = -66.8 dBm Page 10-13 Chapter 10: Reference Information Equipment specifications Nominal Receive 900 MHz Sensitivity (w/ FEC) @

7 MHz Channel Nominal Receive 900 MHz Sensitivity (w/ FEC) @

10 MHz Channel 4.9 GHz 1x = -91 dBm, 2x = -86 dBm, 4x = -80 dBm, 6x = -74 dBm, 8x = -67 dBm 1x = -90 dBm, 2x = -84 dBm, 4x = -79 dBm, 6x = -73 dBm, 8x = -66 dBm 1x = -90 dBm, 2x = -85 dBm, 4x = -78.6 dBm, 6x = -

72.5dBm, 8x = -65 dBm 5.4 GHz 5.8 GHz 1x = -87.6 dBm, 2x = -82.5 dBm, 4x = -76.5 dBm, 6x = -

70.5 dBm, 8x = -61.5dBm 1x = -89.9 dBm, 2x = -84.8 dBm, 4x = -78.5 dBm, 6x = -

71.4 dBm, 8x = -64 dBm Nominal Receive 4.9 GHz Sensitivity (w/ FEC) @

15 MHz Channel 5.4 GHz 5.8 GHz Nominal Receive 900 MHz Sensitivity (w/ FEC) @

20 MHz Channel 4.9 GHz 5.4 GHz 5.8 GHz 1x = -88 dBm, 2x = -83.9 dBm, 4x = -76.9 dBm, 6x = -

70.7 dBm, 8x = -63.6 dBm 1x = -88 dBm, 2x = -84.2 dBm, 4x = -76.9 dBm, 6x = -

70.8 dBm, 8x = -62.7 dBm 1x = -87.8 dBm, 2x = -82.8 dBm, 4x = -6.6 dBm, 6x =

69.3 dBm, 8x = -62.1 dBm 1x = -86 dBm, 2x = -82 dBm, 4x = -75 dBm, 6x = -69 dBm, 8x = -62 dBm 1x = -86.9 dBm, 2x = -82.5 dBm, 4x = -75.7 dBm, 6x = -

69.4 dBm, 8x = -62.3 dBm 1x = -84.5 dBm, 2x = -80.5 dBm, 4x = -73.4 dBm, 6x = -

66.4 dBm, 8x = -56.4 dBm 1x = -85.8 dBm, 2x = -81.7 dBm, 4x = -75 dBm, 6x = -

68.4 dBm, 8x = -61.2 dBm Nominal Receive 4.9 GHz 1x = -85 dBm, 2x = -80.7 dBm, 4x = -73.7 dBm, 6x = -

Sensitivity (w/ FEC) @

30 MHz Channel 66.5 dBm, 8x = -60 dBm 5.4 GHz 1x = -85.3 dBm, 2x = -80.5 dBm, 4x = -74.2 dBm, 6x = -

67.2 dBm, 8x = -60 dBm 5.8 GHz 1x = -84.6 dBm, 2x = -80 dBm, 4x = -73,3 dBm, 6x = -

66.5 dBm, 8x = -59.1 dBm Performance ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Yes 1/16 2.5 ms or 5.0 ms Modulation Levels MCS SNR (in dB) 2x QPSK 10 Page 10-14 Chapter 10: Reference Information Equipment specifications 4x 6x 8x 3 - 5 ms 16QAM 64QAM 256QAM 17 24 32 Up to 40 miles (64 km) Yes, via Autosync (CMM4) Diffserv QoS Latency Maximum Deployment Range GPS Synchronization Quality of Service Link Budget Antenna Beam Width 900 MHz 37 azimuth for 12 dBi Yagi antenna 5 GHz 10 azimuth for 23 dBi integrated antenna Antenna Gain (Does 900 MHz 12 dBi Yagi antenna not include cable loss,

~1dB) Transmit Power Range Maximum Transmit Power Physical 5 GHz

+23 dBi H+V, integrated or external 40 dB dynamic range (to EIRP limit by region) (1 dB step)

+27 dBm combined output Sync/AUX port RJ45 10/100/1000BASE-T Ethernet Data Antenna Connection Surge Suppression EN61000-4-5 Mean Time Between Failure Environmental Temperature /

Humidity PoE output Sync input or output (Connection and powering of UGPS Sync input) 50 ohm, N-type (Connectorized version only) EN61000-4-5: 1.2us/50us, 500 V voltage waveform Recommended external surge suppressor: Cambium Networks Model # C000000L033A

> 40 Years IP66, IP67

-40C to +60C (-40F to +140F), 0-95% non-

condensing Weight Connectorized Approx. 2.0 kg (4.5 lbs) Page 10-15 Chapter 10: Reference Information Equipment specifications Integrated Approx. 2.5 kg (5.5 lbs) Wind Survival Connectorized 322 km/h (200 mi/h) Integrated 200 km/h (124 mi/h) Dimension(HxWxD) Connectorized 26.0 x 13.4 x 6.4 cm (10.25 x 5.25 x 3.25) Integrated 31.0 x 31.0 x 6.4 cm (12 x 12 x 2.5) Power Consumption Input Voltage Mounting Security Encryption 15 W typical, 25 W max, 55 W max with Aux port PoE out enabled 48-59 V DC, 802.3at compliant Wall or Pole mount with Cambium Networks Model #

N000045L002A 56-bit DES, FIPS-197 128-bit AES Page 10-16 Chapter 10: Reference Information Equipment specifications Specifications for PMP 450 AP The PMP 450 AP conforms to the specifications listed in Table 220. Table 220 PMP 450 AP specifications Category Model Number Spectrum Channel Spacing Specification PMP 450 AP 5, 7, 10, 15, 20 and 30 MHz Channel Bandwidth Configurable on 2.5 MHz increments Frequency Range 2.4 GHz 2400 2483.5 MHz 3.5 GHz 3300 3600 MHz 3.65 GHz 3500 3850 MHz 5 GHz 5470 5875 MHz Channel Bandwidth 3.5 and 3.65 GHz 5, 7, 10, 15, 20 and 30 MHz 2.4 and 5 GHz 5, 10, 15, 20 and 30 MHz OFDM Subcarriers Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity 512 FFT Cambium Proprietary 2x2 MIMO OFDM 10/100/1000BaseT, half/full duplex, rate auto negotiated (802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP, TFTP, RADIUS HTTP, HTTPS, Telnet, FTP, SNMP v3, TFTP, Syslog 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID Nominal Receive 2.4 GHz 1x = -92 dBm, 2x = -87.8 dBm, 4x = -80.4 dBm, 6x =

Sensitivity (w/ FEC) @

5 MHz Channel

-74.4 dBm, 8x = -66.5 dBm 3.5 GHz 1x = -92.4 dBm, 2x = -88.3 dBm, 4x = -81.3 dBm, 6x

= -75.3 dBm, 8x = -67.7 dBm Page 10-17 Chapter 10: Reference Information Equipment specifications 3.65 GHz 1x = -10 dBm, 2x = -86.1 dBm, 4x = -80.2 dBm, 6x =

-73.1 dBm, 8x = -66 dBm 5.4 GHz 1x = -88.7 dBm, 2x = -84 dBm, 4x = -77.6 dBm, 6x =

-71.6 dBm, 8x = -63.7 dBm 5.8 GHz 1x = -91.5 dBm, 2x = -87 dBm, 4x = -80.2 dBm, 6x =

-73.1 dBm, 8x = -66 dBm Nominal Receive 3.5 GHz 1x = -90.5 dBm, 2x = -86.4 dBm, 4x = -80.3 dBm, 6x Sensitivity (w/ FEC) @

7 MHz Channel

= -73.4 dBm, 8x = -66.9 dBm 3.65 GHz 1x = -89.1 dBm, 2x = -85.1 dBm, 4x = -78.1 dBm, 6x

= -72.1 dBm, 8x = -64.5 dBm Nominal Receive 2.4 GHz 1x = -89.9 dBm, 2x = -85.6 dBm, 4x = -80 dBm, 6x =

Sensitivity (w/ FEC) @

10 MHz Channel

-73.5 dBm, 8x = -66.9 dBm 3.5 GHz 1x = -89.8 dBm, 2x = -85.6 dBm, 4x = -80 dBm, 6x =

-73 dBm, 8x = -66.3 dBm 3.65 GHz 1x = -89 dBm, 2x = -85.2 dBm, 4x = -78.1 dBm, 6x =

-72.1 dBm, 8x = -64.5 dBm 5.4 GHz 1x = -86.1 dBm, 2x = -82.2 dBm, 4x = -75.3 dBm, 6x

= -69.3 dBm, 8x = -61.3 dBm 5.8 GHz 1x = -86 dBm, 2x = -82.2 dBm, 4x = -75.1 dBm, 6x =

-69 dBm, 8x = -60 dBm Nominal Receive 2.4 GHz 1x = -88.4 dBm, 2x = -84.1 dBm, 4x = -77.1 dBm, 6x Sensitivity (w/ FEC) @

15 MHz Channel

= -71.4 dBm, 8x = -65 dBm 3.5 GHz 1x = -88.5 dBm, 2x = -84.5 dBm, 4x = -77.5 dBm, 6x

= -71.5 dBm, 8x = -64.3 dBm 3.65 GHz 1x = -87.4 dBm, 2x = -83.7 dBm, 4x = -76.3 dBm, 6x

= -69.7 dBm, 8x = -62.2 dBm 5.4 GHz 1x = -84.2 dBm, 2x = -80.2 dBm, 4x = -73.2 dBm, 6x

= -67.2 dBm, 8x = -60 dBm 5.8 GHz 1x = -85 dBm, 2x = -80 dBm, 4x = -74.3 dBm, 6x = -

67 dBm, 8x = -58 dBm Nominal Receive 2.4 GHz 1x = -85 dBm, 2x = -85 dBm, 4x = -79 dBm, 6x = -72 Sensitivity (w/ FEC) @

20 MHz Channel dBm, 8x = -66 dBm 3.5 GHz 1x = -85 dBm, 2x = -85 dBm, 4x = -79 dBm, 6x = -72 dBm, 8x = -65 dBm 3.65 GHz 1x = -86 dBm, 2x = -86 dBm, 4x = -78 dBm, 6x = -71 dBm, 8x = -63 dBm Page 10-18 Chapter 10: Reference Information Equipment specifications 5.4 GHz 1x = -81 dBm, 2x = -81 dBm, 4x = -75 dBm, 6x = -68 dBm, 8x = -59 dBm 5.8 GHz 1x = -82 dBm, 2x = -82 dBm, 4x = -75 dBm, 6x = -69 dBm, 8x = -60 dBm Nominal Receive 2.4 GHz 1x = -85.4 dBm, 2x = -80.4 dBm, 4x = -74 dBm, 6x =

Sensitivity (w/ FEC) @

30 MHz Channel

-68 dBm, 8x = -61 dBm 3.5 GHz 1x = -85.5 dBm, 2x = -81.5 dBm, 4x = -74.5 dBm, 6x

= -68.2 dBm, 8x = -61.3 dBm 3.65 GHz 1x = -84 dBm, 2x = -79.5 dBm, 4x = -73.4 dBm, 6x =

-66.4 dBm, 8x = -59.2 dBm 5.4 GHz 1x = -81 dBm, 2x = -76.9 dBm, 4x = -70.9 dBm, 6x =

-63.8 dBm, 8x = -55.8 dBm 5.8 GHz 1x = -80.9 dBm, 2x = -76.8 dBm, 4x = -70 dBm, 6x =

-63.8 dBm, 8x = -55 dBm Performance Subscribers Per Sector ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Latency Up to 238 Yes 1/16 2.5 ms or 5.0 ms Modulation MCS SNR (in dB) Levels 2x 4x 6x 8x QPSK 16QAM 64QAM 256QAM 10 17 24 32 3 - 5 ms for 2.5 ms Frame Period 6-10 ms for 5.0 ms Frame Period Maximum Deployment Range Up to 40 miles (64 km) Packets Per Second GPS Synchronization Quality of Service Link Budget 12,500 Yes, via CMM3, CMM4 or UGPS Diffserv QoS Page 10-19 Chapter 10: Reference Information Equipment specifications Antenna Gain (Does 2.4 GHz 18 dBi Dual Slant not include cable loss,

~1dB) 3.5 GHz 16 dBi Dual Slant 3.65 GHz 16 dBi Dual Slant 5 GHz 17 dBi Horizontal and Vertical Combined Transmit

-30 to +22 dBm (to EIRP limit by region) in 1 dB-

Power configurable intervals (2.4 GHz, 5 GHz) Maximum Transmit Power Physical Wind Survival Antenna Connection Environmental

-30 to +25 dBm (to EIRP limit by region) in 1 dB-

configurable intervals (3.5 GHz)

-30 to +25 dBm (to EIRP limit by region and channel bandwidth) in 1 dB-configurable intervals (3.6 GHz) 22 dBm combined OFDM (2.4 GHz, 5 GHz)

(dependent upon Region Code setting) 25 dBm combined OFDM (3.5 GHz, 3.6 GHz),

(dependent upon Region Code setting) 200 mph (322 kph) 50 ohm, N-type (Connectorized version only) IP66, IP67 Temperature / Humidity

-40C to +60C (-40F to +140F) /

0-95% non-condensing Weight 2.4 GHz 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 3.5 GHz 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 3.6 GHz 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 5 GHz 5.9 kg (13 lbs) with antenna 2.5 kg (5.5 lbs) without antenna Dimension(HxWxD) 2.4 GHz Radio: 27 x 21 x 7 cm (10.6 x 8.3 x 2.8) Antenna: 112.2 x 24.5 x 11.7 cm (44.2 x 9.6 x 4.6) 3.5 GHz Radio: 27 x 21 x 7 cm (10.6 x 8.3 x 2.8) 3.6 GHz Radio: 27 x 21 x 7 cm (10.6 x 8.3 x 2.8) 5 GHz Radio: 27 x 21 x 7 cm (10.6 x 8.3 x 2.8) Page 10-20 Chapter 10: Reference Information Equipment specifications Power Consumption Input Voltage Security Encryption Antenna: 51 x 13 x 7.3 cm (20.2 x 5.1 x 2.9) 14 W 22 to 32 VDC 56-bit DES, AES Page 10-21 Chapter 10: Reference Information Equipment specifications Specifications for PMP 450 SM The PMP 450 SM conforms to the specifications listed in Table 221. Table 221 PMP 450 SM specifications Category Model Number Spectrum Channel Spacing Specification PMP 450 SM 5, 7, 10, 15, 20 and 30 MHz Channel Bandwidth Configurable on 2.5 MHz increments Frequency Range 900 MHz 902 928 MHz 2.4 GHz 2400 2483.5 MHz 3.5 GHz 3300 3600 MHz 3.65 GHz 3500 3850 MHz 5 GHz 5470 5875 MHz Channel Bandwidth 900 MHz, 5, 7, 10 and 20 MHz 2.4, 3.5 GHz, 3.65 5, 10, 15, 20 and 30 MHz GHz and 5 GHz OFDM Subcarriers Interface 512 FFT MAC (Media Access Control) Layer Cambium Proprietary Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity 2x2 MIMO OFDM 10/100 BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID 900 MHz 1x = -91 dBm, 2x = -91 dBm, 4x = -85 dBm, 6x = -78 dBm, 8x = -70 dBm Page 10-22 Chapter 10: Reference Information Equipment specifications Nominal Receive 2.4 GHz 1x = -92.5 dBm, 2x = -89.9 dBm, 4x = -82.9 dBm, 6x Sensitivity (w/ FEC) @

5 MHz Channel

= -75.9, dBm, 8x = -67.9 dBm 3.5 GHz 1x = -93.5 dBm, 2x = -89.4 dBm, 4x = -83.5 dBm, 6x

= -76.4 dBm, 8x = -68.3 dBm 3.65 GHz 1x = -91.3 dBm, 2x = -89.1 dBm, 4x = -82.2 dBm, 6x

= -75.2 dBm, 8x = -67.3 dBm 5.4 GHz 1x = -89.3 dBm, 2x = -87.3 dBm, 4x = -80.3 dBm, 6x

= -74.3 dBm, 8x = -66.3 dBm 5.8 GHz 1x = -89 dBm, 2x = -87 dBm, 4x = -80 dBm, 6x = -

73.9 dBm, 8x = -64.9 dBm Nominal Receive 900 MHz 1x = -91 dBm, 2x = -84 dBm, 4x = -83 dBm, 6x = -77 Sensitivity (w/ FEC) @

7 MHz Channel dBm, 8x = -71 dBm 3.5 GHz 1x = -92.2 dBm, 2x = -88.5 dBm, 4x = -81.4 dBm, 6x

= -74.5 dBm, 8x = -67.6 dBm 3.65 GHz 1x = -90.4 dBm, 2x = -87.3 dBm, 4x = -80.6 dBm, 6x

= -73 dBm, 8x = -65.6 dBm Nominal Receive 900 MHz 1x = -90 dBm, 2x = -83 dBm, 4x = -80 dBm, 6x = -74 Sensitivity (w/ FEC) @

10 MHz Channel dBm, 8x = -68 dBm 2.4 GHz 1x = -88 dBm, 2x = -88 dBm, 4x = -81 dBm, 6x = -75 dBm, 8x = -69 dBm 3.5 GHz 1x = -88 dBm, 2x = -88 dBm, 4x = -81 dBm, 6x = -76 dBm, 8x = -68 dBm 3.65 GHz 1x = -86 dBm, 2x = -86 dBm, 4x = -80 dBm, 6x = -73 dBm, 8x = -66 dBm 5.4 GHz 1x = -84 dBm, 2x = -84 dBm, 4x = -78 dBm, 6x = -72 dBm, 8x = -63 dBm 5.8 GHz 1x = -84 dBm, 2x = -84 dBm, 4x = -77 dBm, 6x = -71 dBm, 8x = -63 dBm Nominal Receive 2.4 GHz 1x = -88.5 dBm, 2x = -84.5 dBm, 4x = -77.5 dBm, 6x Sensitivity (w/ FEC) @

15 MHz Channel

= -71.5 dBm, 8x = -64.5 dBm 3.5 GHz 1x = -89.5 dBm, 2x = -84.5 dBm, 4x = -78.5 dBm, 6x

= -71.5 dBm, 8x = -65.1 dBm 3.65 GHz 1x = -87.3 dBm, 2x = -84.3 dBm, 4x = -77.3 dBm, 6x

= -70.3 dBm, 8x = -62.2 dBm 5.4 GHz 1x = -84.5dBm, 2x = -82.5 dBm, 4x = -75.5 dBm, 6x =

-69.5 dBm, 8x = -59.5 dBm Page 10-23 Chapter 10: Reference Information Equipment specifications 5.8 GHz 1x = -84 dBm, 2x = -84 dBm, 4x = -77 dBm, 6x = -71 dBm, 8x = -63 dBm Nominal Receive 900 MHz 1x = -87 dBm, 2x = -80 dBm, 4x = -77 dBm, 6x = -72 Sensitivity (w/ FEC) @

20 MHz Channel dBm, 8x = -65 dBm 2.4 GHz 1x = -86.9 dBm, 2x = -82.9 dBm, 4x = -75.9 dBm, 6x

= -69.9 dBm, 8x = -63.5 dBm 3.5 GHz 1x = -87.5 dBm, 2x = -83.5 dBm, 4x = -76.5 dBm, 6x

= -69.5 dBm, 8x = -63.1 dBm 3.65 GHz 1x = -86 dBm, 2x = -83 dBm, 4x = -76.2 dBm, 6x = -

68.2 dBm, 8x = -61 dBm 5.4 GHz 1x = -83.4 dBm, 2x = -81.7 dBm, 4x = -74.4 dBm, 6x

= -67.2 dBm, 8x = -57.3 dBm 5.8 GHz 1x = -84 dBm, 2x = -80.5 dBm, 4x = -74 dBm, 6x = -

66.9 dBm, 8x = -56 dBm Nominal Receive 2.4 GHz 1x = -85.9 dBm, 2x = -80.9 dBm, 4x = -73.9 dBm, 6x Sensitivity (w/ FEC) @

30 MHz Channel

= -67.8 dBm, 8x = -60.9 dBm 3.5 GHz 1x = -86.5 dBm, 2x = -81.5 dBm, 4x = -74.5 dBm, 6x

= -68.2 dBm, 8x = -61.3 dBm 3.65 GHz 1x = -84.3 dBm, 2x = -80.3 dBm, 4x = -74.3 dBm, 6x

= -66.2 dBm, 8x = -58 dBm 5.4 GHz 1x = -82 dBm, 2x = -78.3 dBm, 4x = -72.3 dBm, 6x =

-65.3 dBm, 8x = -55.3 dBm 5.8 GHz 1x = -81.7 dBm, 2x = -78.6 dBm, 4x = -71.6 dBm, 6x

= -64.4 dBm, 8x = -54 dBm Performance Subscribers Per Sector ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Up to 238 Yes 1/16 2.5 ms or 5.0 ms Modulation Levels MCS SNR (in dB) 2x 4x 6x QPSK 16QAM 64QAM 10 17 24 Page 10-24 Chapter 10: Reference Information Equipment specifications 8x 256QAM 32 Latency 3 - 5 ms for 2.5 ms Frame Period 6-10 ms for 5.0 ms Frame Period Maximum Deployment Range Up to 40 miles (64 km) GPS Synchronization Quality of Service Link Budget Yes Diffserv QoS Antenna Gain (Does 900 MHz 12 dBi Yagi antenna not include cable loss,

~1dB) 2.4 GHz 7 dBi Dual Slant, integrated patch 3.5 GHz 8 dBi Dual Slant, integrated patch 19 dBi Flat Plate, integrated patch 3.65 GHz 8 dBi Dual Slant, integrated patch 19 dBi Flat Plate, integrated patch 5 GHz 9 dBi H+V, integrated patch 25 dBi H+V, integrated dish Combined Transmit Power

-30 to +22 dBm (to EIRP limit by region) 2.4, 5 GHz

-30 to +25 dBm (to EIRP limit by region) 3.5, 3.6 GHz Maximum Transmit 22 dBm combined OFDM (2.4 GHz, 5 GHz) Power

(dependent upon Region Code setting) 25 dBm combined OFDM (900 MHz, 3.5 GHz, 3.6 GHz), (dependent upon Region Code setting) Reflector antenna gain 2.4 GHz

+12 dBi 3.5 GHz

+11 dBi 3.65 GHz

+11 dBi 5 GHz

+15 dBi Other antenna (5 GHz CLIP Gain

+8 dBi only) Physical Wind Survival LENS Gain

+5.5 dBi 200 mph (322 kph) Page 10-25 Chapter 10: Reference Information Equipment specifications Antenna Connection Environmental Temperature /

Humidity 50 ohm, N-type (Connectorized version only) IP55

-40C to +60C (-40F to +140F) /

0-95% non-condensing Weight 2.4 GHz 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 3.5 GHz 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 2.5 kg (5.5 lbs) for 450 ruggedized 3.6 GHz 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 2.5 kg (5.5 lbs) for 450 ruggedized 5 GHz 5.9 kg (13 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 3.5 kg (7.7 lbs) for 450d Dimensions (H x W x D) 30 x 9 x 9 cm (11.75 x 3.4 x 3.4) 50 x 50 x 38 cm (19.69 x 19.69 x 14.96) for 450d 31.0 x 31.0 x 6.4 cm (12 x 12 x 2.5) for 450 ruggedized Power Consumption Input Voltage Security Encryption 12 W 20 to 32 VDC 56-bit DES, AES Specifications for PTP 450 BH The PTP 450 BH conforms to the specifications listed in Table 222. Table 222 PTP 450i BH specifications Category Model Number Spectrum Channel Spacing Specification PTP 450 BH 5, 7, 10, 15, 20 and 30 MHz Channel Bandwidth Configurable on 2.5 MHz increments Page 10-26 Chapter 10: Reference Information Equipment specifications Frequency Range 3.5 GHz 3300 3600 MHz 3.65 GHz 3500 3850 MHz 5 GHz 5470 5875 MHz Channel Bandwidth OFDM Subcarriers Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Nominal Receive 3.5 GHz Sensitivity (w/ FEC) @

5 MHz Channel 3.6 GHz 5.4 GHz 5.8 GHz Nominal Receive 3.5 GHz Sensitivity (w/ FEC) @7 MHz Channel 3.6 GHz Nominal Receive 3.5 GHz Sensitivity (w/ FEC)

@10 MHz Channel 5, 7, 10, 15, 20 and 30 MHz 7 MHz Channel bandwidth configurable for 3.5 GHz and 3.65 GHz band only. 512 FFT Cambium Proprietary 2x2 MIMO OFDM 10/100 BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP, TFTP, RADIUS HTTP, HTTPS, Telnet, FTP, SNMP v2c and v3, TFTP, Syslog 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID OFDM: 1x = -92 dBm, 2x = -90 dBm, 4x = -83 dBm, 6x =

-76 dBm, 8x = -69 dBm OFDM: 1x = -94 dBm, 2x = -89.3 dBm, 4x = -82.3 dBm, 6x = -75.2 dBm, 8x = -68.4 dBm OFDM: 1x = -90.4 dBm, 2x = -86 dBm, 4x = -79.4 dBm, 6x = -73.2 dBm, 8x = -65.4 dBm OFDM: 1x = -90 dBm, 2x = -85.4 dBm, 4x = -79.4 dBm, 6x = -73.4 dBm, 8x = -64.9 dBm OFDM: 1x = -90 dBm, 2x = -88 dBm, 4x = -81 dBm, 6x =

-74 dBm, 8x = -67 dBm OFDM: 1x = -92 dBm, 2x = -87.3 dBm, 4x = -81.3 dBm, 6x = -74.3 dBm, 8x = -66.4 dBm OFDM: 1x =-91 dBm, 2x = -87.2 dBm, 4x = -80 dBm, 6x

= -73 dBm, 8x = -65.6 dBm 3.6 GHz OFDM: 1x =-90.4 dBm, 2x = -86.3 dBm, 4x = -80 dBm, 6x =

-73 dBm, 8x = -64.5 dBm Page 10-27 Chapter 10: Reference Information Equipment specifications 5.4 GHz 5.8 GHz OFDM: 1x =-87.6 dBm, 2x = -82.5 dBm, 4x = -76.5 dBm, 6x

= -70.5 dBm, 8x = -61.5 dBm OFDM: 1x =-87.5 dBm, 2x = -82.7 dBm, 4x = -76.8 dBm, 6x

= -70.5 dBm, 8x = -61.4 dBm Nominal Receive 3.5 GHz Sensitivity (w/ FEC)

@15 MHz Channel 3.6 GHz 5.4 GHz 5.8 GHz Nominal Receive 3.5 GHz Sensitivity (w/ FEC) @

20 MHz Channel 3.6 GHz 5.4 GHz 5.8 GHz Nominal Receive 3.5 GHz Sensitivity (w/ FEC) @

30 MHz Channel 3.6 GHz 5.4 GHz 5.8 GHz Performance ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) OFDM: 1x =-89 dBm, 2x = -85 dBm, 4x = -78 dBm, 6x = -

71.1 dBm, 8x = -64.7 dBm OFDM: 1x =-89 dBm, 2x = -84.3 dBm, 4x = -78 dBm, 6x = -

71 dBm, 8x = -63 dBm OFDM: 1x =-85.6 dBm, 2x = -81.6 dBm, 4x = -74.5 dBm, 6x

= -68.5 dBm, 8x = -57.5 dBm OFDM: 1x =-85.6 dBm, 2x = -80.9 dBm, 4x = -75 dBm, 6x =

-68 dBm, 8x = -58 dBm OFDM: 1x =-88 dBm, 2x = -84 dBm, 4x = -77 dBm, 6x = -70 dBm, 8x = -62.2 dBm OFDM: 1x =-87.3 dBm, 2x = -83.3 dBm, 4x = -76.3 dBm, 6x

= -69.3 dBm, 8x = -62 dBm OFDM: 1x =-84.5 dBm, 2x = -80.5 dBm, 4x = -73.4 dBm, 6x

= -66.4 dBm, 8x = -56.4 dBm OFDM: 1x =-84.8 dBm, 2x = -80.8 dBm, 4x = -74.7 dBm, 6x

= -66.4 dBm, 8x = -56 dBm OFDM: 1x =-86 dBm, 2x = -82 dBm, 4x = -75 dBm, 6x = -68 dBm, 8x = -60 dBm OFDM: 1x =-86 dBm, 2x = -81.3 dBm, 4x = -74.3 dBm, 6x =

-67.3 dBm, 8x = -59 dBm OFDM: 1x =-82.5 dBm, 2x = -78.5 dBm, 4x = -71.5 dBm, 6x

= -64.4 dBm, 8x = -53.4 dBm OFDM: 1x =-82.5 dBm, 2x = -78.5 dBm, 4x = -71.5 dBm, 6x

= -64.4 dBm, 8x = -54 dBm Yes 1/16 2.5 ms or 5.0 ms Modulation Levels MCS SNR (in dB) 2x QPSK 10 Page 10-28 Chapter 10: Reference Information Equipment specifications 4x 6x 8x 16QAM 64QAM 256QAM 17 24 32 3 - 5 ms for 2.5 ms frame period 6 - 10 ms for 5.0 ms frame period 12,500 Up to 40 miles (64 km) Yes, via Autosync (CMM4) Diffserv QoS Latency Packets Per Second Maximum Deployment Range GPS Synchronization Quality of Service Link Budget Combined Transmit

-

30 to +22 dBm (to EIRP limit by region) in 1 dB-

Power configurable intervals (5 GHz)

-30 to +25 dBm (to EIRP limit by region) in 1 dB-

configurable intervals (3.5 GHz)

-30 to +25 dBm (to EIRP limit by region and channel bandwidth) in 1 dB-configurable intervals (3.6 GHz) Antenna Gain (Does 3.5 GHz 8 dBi Dual Slant, integrated patch not include cable loss,

~1dB) 19 dBi Flat Plate, integrated patch 3.65 GHz 8 dBi Dual Slant, integrated patch 19 dBi Flat Plate, integrated patch 5 GHz 9 dBi H+V, integrated patch 25 dBi H+V, integrated dish Transmit Power Range Maximum Transmit Power 40 dB dynamic range (to EIRP limit by region) (1 dB step) 22 dBm combined OFDM (5 GHz) (dependent upon Region Code setting) 25 dBm combined OFDM (3.5 GHz, 3.6 GHz),

(dependent upon Region Code setting) Reflector antenna gain 3.5 GHz

+11 dBi 3.65 GHz

+11 dBi 5 GHz

+15 dBi Page 10-29 Chapter 10: Reference Information Equipment specifications Other antenna (5 GHz CLIP Gain

+8 dBi only) LENS Gain

+5.5 dBi Physical Sync/AUX port RJ45 10/100/1000BASE-T Ethernet Data Antenna Connection Surge Suppression EN61000-4-5 Mean Time Between Failure Environmental Temperature /

Humidity Weight Wind Survival Dimension(HxWxD) Maximum Power Consumption Input Voltage Security Encryption PoE output Sync input or output (Connection and powering of UGPS Sync input) 50 ohm, N-type (Connectorized version only) EN61000-4-5: 1.2us/50us, 500 V voltage waveform Recommended external surge suppressor: Cambium Networks Model # C000000L033A

> 40 Years IP66, IP67

-40C to +60C (-40F to +140F), 0-95% non-

condensing 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 200 mph (322 kph) 30 x 9 x 9 cm (11.75 x 3.4 x 3.4) 14 W 22 to 32 VDC 56-bit DES, AES Page 10-30 Chapter 10: Reference Information Equipment specifications PSU specifications The PMP/PTP 450i AC+DC Enhanced Power Injector conforms to the specifications listed in Table 223. Table 223 PMP/PTP 450i AC power Injector specifications Category Dimensions Weight Specification 137 mm (5.4 in) x 56 mm (2.2 in) x 38 mm (1.5 in) 0.240 Kg (0.5 lbs) Temperature 0C to +40C Humidity 90% non-condensing Waterproofing Not waterproof Altitude AC Input Sea level to 5000 meters (16000 ft) Min 90 V AC, 57 63 Hz, max 264 V AC, 47 53 Hz. DC output voltage to the ODU 55V +/- 5%

AC connector IEC-320-C8 Efficiency Better than 85%, efficiency level V Over Current Protection Hiccup current limiting, trip point set between 120% to Hold up time At least 10 milliseconds 150% of full load current Warning Do not use above PSU to power up other than 450 platform radios. The PMP/PTP 450 power supply conforms to the specifications listed in Table 224. Table 224 PMP/PTP 450 power supply specifications (part number: N000900L001A) Category Dimensions Weight Specification 118 mm (4.66 in) x 45 mm (1.75 in) x 32 mm (1.25 in) 0.240 Kg (0.5 lbs) Temperature 0C to +40C Humidity AC Input 20 to 90%

90-264 VAC, 47 63 Hz, 0.5 A rms at 120 VAC, 0.25 A rms at 240 VAC. Page 10-31 Chapter 10: Reference Information Equipment specifications DC output voltage to the ODU 30 V 5%

AC connector IEC-320-C8 Efficiency Better than 85%, efficiency level V Over Current Protection Short circuit, with auto recovery; Should restart between every 0.5 to 2 sec. Hold up time 10mS min at max load, 120VAC Note The 30V PSU (part number: #N000900L001A) has to be used for PMP 450 900 MHz SM. Warning The PMP 450 Ruggedized High Gain Integrated Subscriber Module (Cambium part numbers C035045C014A and C036045C014A), while encapsulated in a 450i-type enclosure, contains 450 circuitry which must be powered via 30VDC. Powering these SMs with a 56 VDC will damage the device. Page 10-32 Chapter 10: Reference Information Data network specifications Data network specifications This section contains specifications of the PMP/PTP 450 platform Ethernet interface. Ethernet interface PMP/PTP 450i The PMP/PTP 450i Ethernet port conforms to the specifications listed in Table 225. Table 225 PMP/PTP 450i Main and Aux Ethernet bridging specifications Ethernet Bridging Specification Protocol QoS IEEE 802.3 compatible IEEE 802.1p, IEEE 802.1Q, IEEE 802.1ad, DSCP IPv4 Main Ethernet port 10/100/1000 BaseT, half/full duplex, rate auto negotiated Aux Ethernet port 10/100 BaseT, half/full duplex, rate auto negotiated Maximum Ethernet Frame 1700 Bytes Size PMP/PTP 450 Table 226 PMP/PTP 450 Ethernet bridging specifications Ethernet Bridging Specification Protocol QoS Interface IEEE 802.3 compatible IEEE 802.1p, IEEE 802.1Q, IEEE 802.1ad, DSCP IPv4 10/100/1000 BaseT, half/full duplex, rate auto negotiated Maximum Ethernet Frame 1700 Bytes Size Note Practical Ethernet rates depend on network configuration, higher layer protocols and platforms used. Over the air throughput is restricted to the rate of the Ethernet interface at the receiving end of the link. Page 10-33 Chapter 10: Reference Information Wireless specifications Wireless specifications This section contains specifications of the PMP/PTP 450 platform wireless interface. These specifications include RF bands, channel bandwidth, spectrum settings, maximum power and link loss. General wireless specifications The wireless specifications that apply to all PMP/PTP 450 platform variants are listed under Table 227. Table 227 PMP/PTP 450 platform wireless specifications Item Specification Channel selection Manual selection (fixed frequency). Manual power control To avoid interference to other users of the band, maximum power can be set lower than the default power limit. Duplex scheme Adaptive TDD Range Band Platform Range 900 MHz PMP 450i AP and PMP 450 SM 40 mi / 64 km 2.4 GHz PMP 450 3.5 GHz PMP/PTP 450 3.65 GHz PMP/PTP 450 40 mi / 64 km 40 mi / 64 km 40 mi / 64 km 5 GHz PMP/PTP 450/450i and 40 mi / 64 km PMP 450m AP Over-the-air encryption DES, AES Error Correction Rate 3/4 RS coder Link Range and Throughput Link range and throughput estimates are based on site-specific attributes and configuration parameters. For the most up-to-date information on link range and throughput for your equipment see the Capacity Planner and LINKPlanner software tools:

For average-deployment link range and throughput planning information, see:

https://support.cambiumnetworks.com/files/pmp450 For site-specific link range and throughput planning information, see:

https://support.cambiumnetworks.com/files/linkplanner Page 10-34 Chapter 10: Reference Information Country specific radio regulations Country specific radio regulations This section describes how the PMP/PTP 450 platform complies with the radio regulations that are enforced in various countries. Caution Changes or modifications not expressly approved by Cambium could void the users authority to operate the system. Type approvals This system has achieved Type Approval in various countries around the world. This means that the system has been tested against various local technical regulations and found to comply. The frequency bands in which the system operates may be unlicensed and, in these bands, the system can be used provided it does not cause interference. The system is not guaranteed protection against interference from other products and installations. The radio specification type approvals that have been granted for 450 platform frequency variants are listed in Table 228. Table 228 Radio certifications Variant Region Specification (Type Approvals) 900 MHz PMP 450i Canada RSS Gen and RSS 210 2.4 GHz PMP 450 USA Mexico Canada USA FCC Part 15.247 NOM-121-SCT1-2009 RSS Gen and RSS 210 FCC Part 15 Class B 3.5 GHz PMP/PTP 450 Canada RSS Gen and RSS 192 3.6 GHz PMP/PTP 450 Canada RSS Gen and RSS 192 Europe ETSI EN 302 326-2 V1.2.2 5.4 GHz PMP/PTP 450 and 450i 5.8 GHz PMP/PTP 450 and 450i USA Europe USA Canada USA Europe FCC Part 15 Class B ETSI EN 301 893 v1.6.1 FCC Part 15 Class B RSS Gen and RSS 210 FCC Part 15 Class B ETSI EN 302 502 v1.2.1 Page 10-35 Chapter 10: Reference Information Country specific radio regulations DFS for 2.4 and 5 GHz Radios Dynamic Frequency Selection (DFS) is a requirement in several countries and regions for 2.4 and 5 GHz unlicensed systems to detect radar systems and avoid co-channel operation. The details of DFS operation and channels available for each Country Code, including whether DFS is active on the AP, SM, which DFS regulation apply, and any channel restrictions are shown in Table 229 on page 10-36. Table 229 Country & Bands DFS setting Region Code Country Code Band AP SM North Mexico 2.4 GHz No effect No effect America 5.4 GHz ANATEL Res506-

No effect 2008 5.8 GHz No effect No effect South Brazil America 5.4 GHz ETSI EN 301 893 v1.7.1 DFS No effect 5.8 GHz No effect No effect Weather Radar Notch-Out No No No No No Europe ETSI 5.4 GHz ETSI EN 301 893 ETSI EN 301 893 Yes v1.7.1 DFS v1.7.1 DFS 5.8 GHz ETSI EN 302 502 ETSI EN 302 502 Yes v1.2.1 DFS v1.2.1 DFS Other-

Other-FCC 2.4 GHz No effect No effect Regulatory Other-ETSI 5.4 GHz FCC DFS No effect 5.8-GHz No effect No effect 5.4 GHz 5.8 GHz ETSI EN 301 893 ETSI EN 301 893 v1.7.1 DFS v1.7.1 DFS ETSI EN 302 502 ETSI EN 302 502 v1.2.1 DFS v1.2.1 DFS No No No No No Page 10-36 Chapter 10: Reference Information Equipment Disposal Equipment Disposal Waste (Disposal) of Electronic and Electric Equipment Waste

(Disposal) of Electronic and Electric Equipment Please do not dispose of Electronic and Electric Equipment or Electronic and Electric Accessories with your household waste. In some countries or regions, collection systems have been set up to handle waste of electrical and electronic equipment. In European Union countries, please contact your local equipment supplier representative or service center for information about the waste collection system in your country. Country specific maximum transmit power Maximum transmit power 900 MHz band Table 230 Default combined transmit power per country 900 MHz band PMP 450i Countries Device Type Antenna

(AP/SM/BH) Type Conducted Channel BW Power Limit

(dBm) EIRP Limit

(dBm) USA, Mexico, Canada, Other FCC Any Any Brazil Any Any 5 MHz 7 MHz 10 MHz 20 MHz 5 MHz 7 MHz 10 MHz 20 MHz Other Any Any Any

-

-

-

-

-

-

-

-

-

36 36 36 36 36 36 36 36

-

Page 10-37 Chapter 10: Reference Information Equipment Disposal Maximum transmit power 2.4 GHz band Table 231 Default combined transmit power per country 2.4 GHz band PMP/PTP 450 Countries Device Type Antenna Type Channel BW Power Limit Conducted AP Sector USA, Canada, Other FCC SM, BH Integrated Reflector Integrated Dish

(450d) Other Any Any Any Any Any Any Any Maximum transmit power 3.5 GHz band

(dBm) 18

-

24 11 30 EIRP Limit

(dBm) 36 36 36 36

-

Table 232 Default combined transmit power per country 3.5 GHz band PMP/PTP 450 Countries Device Type Antenna Type Channel BW Power Limit Conducted

(dBm) EIRP Limit

(dBm) AP Sector SM, BH Any Any Any Any Any Any Other-ETSI Brazil, China, India, Indonesia, Mexico, Other Canada Australia Any Any Any Any Any Any Maximum transmit power 3.65 GHz band

-

-

-

-

-

66 63

-

62 63 Table 233 Default combined transmit power per country 3.65 GHz band PMP/PTP 450 Countries Device Type Antenna Type Channel BW Power Limit Conducted

(dBm) EIRP Limit

(dBm) Page 10-38 Chapter 10: Reference Information Equipment Disposal Australia, India, Indonesia, Any Any Any Mexico, Other Other-ETSI AP SM, BH Any Any AP Sector Canada, USA, Other-FCC SM, BH Integrated Reflector Any Integrated Dish

(450d)

-

-

25

-

-

18

-

66 63 43 Maximum transmit power 4.9 GHz band Table 234 Default combined transmit power per country 4.9 GHz band PMP/PTP 450/450i Countries Device Type Antenna Type Channel BW Power Limit Conducted

(dBm) EIRP Limit

(dBm) USA, Mexico, Canada, Other FCC AP Sector Omni 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5 MHz Flate plate 10 MHz 20 MHz 5 MHz SM, BH 4ft parabolic 10 MHz 20 MHz 5 MHz 6ft parabolic 10 MHz Brazil Any Any 20 MHz 5 MHz Page 10-39 24 24 23 24 24 23 24 24 23 24 24 23 24 24 23 23 40 40 39 35 36 35 51 51 50 52 55 56 52 55 58 54 Chapter 10: Reference Information Equipment Disposal Other Any Any Any 10 MHz 20 MHz 27 27 27 57 60

-

Maximum transmit power 5.1 GHz band Table 235 Default combined transmit power per Country 5.1 GHz band PMP/PTP 450i Countries Device Antenna Type Conducted Type Channel BW Power Limit

(dBm) EIRP Limit

(dBm) USA, Other FCC AP Sector 5 MHz Omni 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz SM, BH Flat plate 5 MHz 10 MHz 20 MHz 4ft parabolic 5 MHz Mexico Any Any 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 12 15 16 16 19 22

-2 1 3 6 9 9

-

-

-

Other Any Any Any 27 28 31 32 28 31 34 25 28 30 39 42 43 17 20 23

-

Page 10-40 Chapter 10: Reference Information Equipment Disposal Table 236 Default combined transmit power per Country 5.1 GHz band PMP 450m Countries Device Antenna Type Conducted Type Channel BW Power Limit

(dBm) USA, Other FCC Mexico Other AP Sector 20 MHz NA Any Any Any Any 20 MHz Any NA NA Maximum transmit power 5.2 GHz band Table 237 Default combined transmit power per country 5.2 GHz band Countries Device Antenna Type Conducted Type Channel BW Power Limit USA, Other FCC AP Sector 5 MHz Omni 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz SM, BH Flat plate 5 MHz 10 MHz 20 MHz 4ft parabolic 5 MHz Mexico Any Any 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz

(dBm) 6 9 12 10 13 16

-7

-4

-1

-13

-11

-8

-

-

-

Other Any Any Any 27 EIRP Limit

(dBm) 32 23

-

EIRP Limit

(dBm) 22 25 28 22 25 28 20 23 26 19 22 25 24 27 30

-

Page 10-41 Chapter 10: Reference Information Equipment Disposal Table 238 Default combined transmit power per Country 5.2 GHz band PMP 450m Countries Device Antenna Type Conducted Type Channel BW Power Limit

(dBm) USA, Other FCC Mexico Other AP Sector 20 MHz NA Any Any Any Any 20 MHz Any NA NA EIRP Limit

(dBm) 32 32

-

Page 10-42 Chapter 10: Reference Information Equipment Disposal Maximum transmit power 5.4 GHz band Table 239 Default combined transmit power per country 5.4 GHz band PMP/PTP 450i Device Type Antenna Type Channel BW Power Limit Conducted

(dBm) EIRP Limit

(dBm) Countries USA, Other FCC 6 9 12 10 13 16

-7

-4

-1

-6

-3 0 19 23

-

-

27

-

-

-

-

-

22 25 28 22 25 28 20 23 26 21 24 27 27 30 27 30

-

24 27 30 30 30 AP Sector 5 MHz Omni 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz SM, BH Flat plate 5 MHz 10 MHz 20 MHz 4ft parabolic 5 MHz Brazil Any Any Mexico Any Any Other ETSI Any Any Any Any Australia Any Any 10 MHz 20 MHz 10 MHz 20 MHz 10 MHz 20 MHz Any 5 MHz 10 MHz 20 MHz 10 MHz 20 MHz Page 10-43 Chapter 10: Reference Information Equipment Disposal Table 240 Default combined transmit power per Country 5.4 GHz band PMP 450m Countries Device Antenna Type Conducted Type Channel BW Power Limit

(dBm) USA, Other FCC Mexico Other AP Sector 20 MHz NA Any Any Any Any 20 MHz Any NA NA EIRP Limit

(dBm) 32 23

-

Page 10-44 Chapter 10: Reference Information Equipment Disposal Table 241 Default combined transmit power per country 5.4 GHz band PMP 450 Device Antenna Type Type Conducted EIRP Channel BW Power Limit Limit

(dBm)

(dBm) AP Sector (18 10 MHz 10 dBi 1dB cable loss) 20 MHz 13 AP Sector (18 10 MHz 10 dBi 1dB cable loss) 27 30

*

27 20 MHz 13 30 Countries United States, Canada, Brazil, Australia, Denmark, Finaland, Germany, Greece, Liechtenstein, Norway, Portugal, Spain, UK, Vietnam Austria, Belgium, Bosnia &

Herzegovina, Bulgaria, Croatia, Cyprus, Czech Republic, France, , Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Macedonia, Malta, Netherlands, Poland, Romania, Slovakia, Slovenia , Sweden Algeria AP Sector (18 10 MHz dBi 1dB cable loss) 20 MHz Other AP Sector (18 dBi 1dB cable loss) 10 MHz 10 13 19 20 MHz 19 27 30 No EIRP limit No EIRP limit

(*) At 5.4 GHz, EU regulations are harmonized. 5600 5650 MHz excluded, as ten minute Channel Availability Check (CAC) is required Page 10-45 Chapter 10: Reference Information Equipment Disposal Maximum transmit power 5.8 GHz band Table 242 Default combined transmit power per country 5.8 GHz band PMP/PTP 450i Antenna Type Channel BW Conducted Power EIRP Limit Limit (dBm)

(dBm) Device Type AP Countries USA, Canada, Brazil, Other FCC Sector, Omni 5 MHz 10 MHz 20 MHz SM, BH Flat plate, 5 MHz 4ft parabolic, 6ft parabolic Mexico Any Any

-

-

-

27 27 10 MHz

(26 for 5733 MHz and below) 20 MHz 27 5 MHz 10 MHz 20 MHz

-

-

-

36 36 36

-

-

-

30 33 36

-

Other Any Any 5 MHz 27 Table 243 Default combined transmit power per Country 5.8 GHz band PMP 450m Countries Device Antenna Type Conducted Type Channel BW Power Limit

(dBm) AP Sector 20 MHz NA Any Any Any Any 20 MHz Any NA NA USA, Other FCC Mexico Other EIRP Limit

(dBm) 32 23

-

Table 244 Default combined transmit power per country 5.8 GHz band PMP 450 Countries Device Type AP Antenna Type Channel BW Conducted Power Limit

(dBm) EIRP Limit

(dBm) 5 MHz 19 36 Page 10-46 Chapter 10: Reference Information Equipment Disposal Australia, India, United Sector (18 dBi 10 MHz States 1dB cable loss) 20 MHz Brazil, Vietnam AP Sector (18 dBi 5 MHz 1dB cable loss) 10 MHz 20 MHz Canada AP Sector (18 dBi 5 MHz 1dB cable loss) 10 MHz 20 MHz 19 19 7 10 13 9 19 19 Denmakr, Finland, AP Sector (18 dBi 5 MHz

-

Germany, Greece, Iceland, Ireland, Liechtenstein, Norway, Portugal, Serbia, Spain, Switzerland, United Kingdom, Indonesia 1dB cable loss) 10 MHz 16 20 MHz 19 AP Sector (18 dBi 5 MHz 1dB cable loss) 10 MHz 20 MHz 13 19 19 36 36 24 27 30 26 36 36

-

33 36 30 36 36 Page 10-47 Chapter 10: Reference Information Equipment Disposal Country specific frequency range Frequency range 900 MHz band Table 245 Frequency range per country 900 MHz band Region Country Other Other Other-FCC North America Canada United States Mexico Puerto Rico Oceania Australia Channel center Frequency limits (MHz) Lower Upper 902 902 902 902 902 902 918 928 928 928 928 928 928 926 New Zealand 921 (7 MHz) 928 (7 MHz) 921.5 (5 MHz) 928 (5 MHz) Brazil Ecuador Colombia Venezuela 902 915 902 902 902 907.5 928 928 928 928 Page 10-48 Chapter 10: Reference Information Equipment Disposal Frequency range 2.4 GHz band Table 246 Frequency range per country 2.4 GHz band PMP/PTP 450 Countries Antenna Type Channel BW Channel center Frequency limits (MHz) Canada, Any United States, Other, Other-

FCC 5 MHz 10 MHz 20 MHz Frequency range 3.5 GHz band Lower 2402.5 2405 2417.5 Upper 2475 2470 2460 Table 247 Frequency range per country 3.5 GHz band PMP/PTP 450 Countries Antenna Type Channel BW Channel center Frequency limits (MHz) Brazil, Other-

Any ETSI Any China, Indonesia 5 MHz 7 MHz 10 MHz 20 MHz 5 MHz 7 MHz 10 MHz 20 MHz Lower 3402.5 3403.5 3405 3410 3302.5 3303.5 3305 3310 Upper 3597.5 3596.5 3595 3590 3397.5 3396.5 3395 3390 Page 10-49 Chapter 10: Reference Information Equipment Disposal Frequency range 3.65 GHz band Table 248 Frequency range per country 3.65 GHz band PMP/PTP 450 Countries Antenna Type Channel BW Channel center Frequency limits (MHz) Australia, Any India, Other Other ETSI Any Indonesia Any Mexico Any 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz Lower 3502.5 3505 3510 3552.5 3555 3560 3602.5 3605 3610 3552.5 3555 3560 Upper 3847.5 3845 3840 3797.5 3795 3790 3797.5 3795 3790 3747.5 3745 3740 Frequency range 4.9 GHz band Table 249 Frequency range per country 4.9 GHz band PMP/PTP 450i Countries Antenna Type Channel BW Channel center Frequency limits (MHz) Any USA, Mexico, Canada, Other FCC Brazil Any Other Any Upper 4987.5 4985 4980 4987.5 4985 4980 4997.5 4995 4990 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz Lower 4942.5 4945 4950 4912.5 4915 4920 4902.5 4905 4910 Page 10-50 Chapter 10: Reference Information Equipment Disposal Frequency range 5.4 GHz band Table 250 Frequency range per country 5.4 GHz band PMP/PTP 450i Countries Antenna Type Channel BW Channel center Frequency limits (MHz) Lower Upper Brazil Any Mexico Any 10 MHz 20 MHz 10 MHz 20 MHz 5475 5480 5475 5655 5480 5660 Other Any 5 MHz 5742.5 10 MHz 20 MHz 5475 5480 5720 5715 5595 5720 5590 5710 5722.5 5720 5715 Page 10-51 Chapter 10: Reference Information Equipment Disposal Table 251 Frequency range per country 5.4 GHz band PMP/PTP 450 Channel center Frequency limits (MHz) Region code Country Code Channel BW Lower Other Any Other-FCC (Any non-US country that follows FCC rules Other-ETSI (Any country that follows ETSI rules Oceania Australia North America Canada South America Brazil Asia Vietnam 5 MHz 5472.5 10 MHz 5475 20 MHz 5480 10 MHz 20 MHz 10 MHz 20 MHz 10 MHz 20 MHz 10 MHz 20 MHz 5475 5645 5465 5640 5475 5645 5465 5640 5475 5645 5465 5640 5475 5645 5465 5640 10 MHz 5475 20 MHz 5480 10 MHz 5475 20 MHz 5480 Upper 5722.5 5720 5715 5595 5720 5490 5715 5595 5720 5490 5715 5595 5720 5490 5715 5595 5720 5490 5715 5720 5715 5720 5715 5 MHz 5472.5 5597.5 Africa Algeria 10 MHz 5475 20 MHz 5465 Europe (Denmark, Finland, France, Germany, Greece, 10 MHz Iceland, Ireland, Italy, Liechtenstein, Norway, Portugal, Serbia, Spain, Switzerland, United Kingdom) 20 MHz 5475 5645 5465 5640 Europe 5595 5490 5595 5720 5490 5715 Page 10-52 Chapter 10: Reference Information Equipment Disposal Frequency range 5.8 GHz band Table 252 Frequency range per country 5.8 GHz band PMP/PTP 450i Countries Antenna Type Channel BW Channel center Frequency limits (MHz) Any USA, Canada, Brazil, Other FCC 5 MHz 10 MHz 20 MHz Lower 5730 5730 5735 Mexico Any 5 MHz 5727.5 Other Any 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5730 5735 5727.5 5730 5735 Upper 5845 5845 5840 5847.5 5845 5840 5897.5 5895 5890 Table 253 Frequency range per country 5.8 GHz band PMP/PTP 450 Countries Antenna Type Channel BW Channel center Frequency limits (MHz) Lower Upper Denmark, Any Norway, United Kingdom, Finland Germany Any Spain Any Greece Any Portugal, Any Iceland, Serbia 10 MHz 20 MHz 10 MHz 20 MHz 10 MHz 20 MHz 10 MHz 20 MHz 10 MHz 20 MHz 5730 5820 5735 5825 5760 5765 5730 5820 5735 5825 5730 5735 5730 5735 Page 10-53 5790 5845 5785 5840 5870 5865 5790 5850 5785 5845 5790 5785 5870 5865 Chapter 10: Reference Information Equipment Disposal 5730 5820 5735 5825 5790 5870 5785 5865 5727.5 5847.5 5845 5840 5845 5845 5845 5872.5 5870 5865 5847.5 5845 5840 5822.5 5820 5815 5872.5 5870 5865 Switzerland, Any Liechtenstein Australia Any Canada, United Any States India Any 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5730 5735 5730 5730 5735 5727.5 5730 5735 Brazil, Vietnam Any 5 MHz 5727.5 Indonesia Any 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5730 5735 5727.5 5730 5735 Malaysia Any 5 MHz 5727.5 10 MHz 20 MHz 5830 5835 Page 10-54 Chapter 10: Reference Information Equipment Disposal FCC specific information FCC compliance testing With GPS synchronization installed, the system has been tested for compliance to US (FCC) specifications. It has been shown to comply with the limits for emitted spurious radiation for a Class B digital device, pursuant to Part 15 of the FCC Rules in the USA. These limits have been designed to provide reasonable protection against harmful interference. However the equipment can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to other radio communications. There is no guarantee that interference does not occur in a particular installation. Note A Class B Digital Device is a device that is marketed for use in a residential environment, notwithstanding use in commercial, business and industrial environments. Note Notwithstanding that Cambium has designed (and qualified) the PMP/PTP 450 platform products to generally meet the Class B requirement to minimize the potential for interference, the PMP/PTP 450 platform product range is not marketed for use in a residential environment. FCC IDs Table 254 US FCC IDs FCC ID Product Frequency Channel Frequencies Maximum Band Bandwidth Combined Tx Output Power Z8H89FT 900 MHz 0021 and PMP 450i Z8H89FT AP & PMP 0022 450 SM 900 MHz Z8H89FT 0003 and Z8H89FT 004 2.4 GHz AP & SM Z8H89FT 3.5 GHz 5 MHz 904.5 - 925.5 MHz 25 dBm 7 MHz 905.5 - 924.5 MHz 25 dBm 10 MHz 907 923 MHz 25 dBm 20 MHz 912 918 MHz 25 dBm 5 MHz 2402.5 2475 MHz 19 dBm 20 MHz 2417.5 2460 MHz 19 dBm 5 MHz 3452.5 -3647.5 MHz 25 dBm PMP 450 2.4 GHz 10 MHz 2405 2470 MHz 19 dBm 0009 and PMP 450 3.5 GHz 10 MHz 3455 3645 MHz 25 dBm AP & SM 20 MHz 3460 3640 MHz 25 dBm Page 10-55 Chapter 10: Reference Information Equipment Disposal FCC ID Product Frequency Channel Frequencies Maximum Band Bandwidth Combined Tx Output Power 5 MHz 3652.5 -3697.5 MHz 19 dBm Z8H89FT 0010 3.65 GHz PMP 450 3.65 GHz 10 MHz 3655 3695 MHz 22 dBm AP & SM Z8H89FT 0001, Z8H89FT 0002 and QWP-

50450I 5 GHz PMP 450/

450i/450m AP, SM &

PTP 450/450i BH 20 MHz 3660 3690 MHz 25 dBm 5 MHz 4942.5 4987.5 MHz 24 dBm 10 MHz 4945.0 4985.0 MHz 24 dBm 20 MHz 4950.0 4980.0 MHz 23.5 dBm 5 MHz 5156.0 5247.5 MHz 16 dBm 4.9 GHz

(PMP/PTP 450i only) 5.1 GHz

(PMP/PTP 10 MHz 5160.0 5164.75 MHz 17 dBm 450i only) 5.2 GHz 20 MHz 5165.0 5245.0 MHz 19 dBm 5 MHz 5252.5 5343.0 MHz 10 dBm

(PMP/PTP 10 MHz 5255.0 5340.5 MHz 13 dBm 450i only) 20 MHz 5260.0 5333.75 MHz 16 dBm 5 MHz 5473.0 5721.25 MHz 10 dBm 5.4 GHz 10 MHz 5475.5 5719.25 MHz 13 dBm 20 MHz 5480.0 5715.0 MHz 16 dBm 5 MHz 5730.0 5845.0 MHz 28 dBm 5.8 GHz 10 MHz 5730.0 5845.0 MHz 28 dBm 20 MHz 5735.0 5840.0 MHz 28 dBm Page 10-56 Chapter 10: Reference Information Equipment Disposal FCC approved antenna list The lists of antennas which have been approved for operation by the FCC are provided in:

Table 255 for 4.9 GHz Table 256 for 5.1 and 5.2 GHz Table 257 for 5.4 GHz Table 258 for 5.8 GHz Note Any antenna of the same type and of gain equal or lower than the one approved by the FCC can be used in the countries following the FCC rules. Table 255 USA approved antenna list 4.9 GHz Directivity Type Manufacturer Reference Stated Gain Integrated flat plate Cambium Networks N/A

(dBi) 23.0 2 ft dual polarised Mars Antennas MA-WA56-DP-28N 28.0 Directional flat plate 4 ft parabolic dual Gabriel Dual QuickFire QFD4-49-N 33.7 polarised Antennas 6 ft parabolic dual Gabriel QuickFire QF6-49-N 37.2 polarised Antennas Integrated 90 Cambium A005240 sector flat plate Networks Sector 90 sectorised 60 sectorised Cambium Networks Cambium Networks 85009324001 85009325001 16.0 17.0 17.0 Omni-

Dual polar omni-

KP KPPA-5.7-DPOMA 13.0 directional directional Page 10-57 Chapter 10: Reference Information Equipment Disposal Table 256 USA approved antenna list 5.1 and 5.2 GHz Directivity Type Manufacturer Reference Integrated flat plate Cambium Networks N/A Stated Gain

(dBi) 23.0 Directional 2ft dual polarised Mars Antennas MA-WA56-DP-28N 28.5 flat plate 4ft parabolic dual Gabriel PX4F-52-N7A/A polarised Antennas Integrated 90 Cambium A005240 Sector sector flat plate Networks 90 sectorised Cambium Networks 85009324001 34.5 16.0 17.0 Dual polar omni-

KP KPPA-5.7-DPOMA 13.0 directional Dual polar omni-

Mars Antennas MA-WO56-DP10 10.0 directional Omni-

directional Table 257 USA approved antenna list 5.4 GHz Directivity Type Manufacturer Reference Integrated flat plate Cambium Networks N/A Stated Gain

(dBi) 23.0 Directional 2 ft dual polarised Mars Antennas MA-WA56-DP-28N 28.5 flat plate 2 ft dual polarised MTI MT-486013-NVH 28.5 parabolic Integrated 90 Cambium A005240 Sector sector flat plate Networks 90 sectorised Cambium Networks 85009324001 16.0 17.0 Omni-

Dual polar omni-

KP KPPA-5.7-DPOMA 13.0 directional directional Dual polar omni-

Mars Antennas MA-WO56-DP10 10.0 directional Page 10-58 Chapter 10: Reference Information Equipment Disposal Table 258 USA approved antenna list 5.8 GHz Directivity Type Manufacturer Reference Integrated flat plate Cambium Networks N/A Stated Gain

(dBi) 23.0 2 ft dual polarised Mars Antennas MA-WA56-DP-28N 28.0 Directional flat plate 4 ft parabolic dual Gabriel PX4F-52-N7A/A polarised Antennas 6 ft Parabolic dual Gabriel PX6F-52/A polarised Antennas Integrated 90 Cambium A005240 sector flat plate Networks Sector 90 sectorised 60 sectorised Cambium Networks Cambium Networks 85009324001 85009325001 35.3 38.1 16.0 17.0 17.0 Omni-

Dual polar omni-

KP KPPA-5.7-DPOMA 13.0 directional directional Innovation Science and Economic Development Canada (ISEDC) specific information 900 MHz ISEDC notification Radio Standards Specification RSS-247, Issue 1, Digital Transmission Systems (DTSs), Frequency Hopping Systems (FHSs) and Licence-Exempt Local Area Network (LE-LAN) Devices, is a new standard to replace annexes 8 and 9 of RSS-210, Issue 8. 4.9 GHz ISEDC notification The system has been approved under ISEDC RSS-111 for Public Safety Agency usage. The installer or operator is responsible for obtaining the appropriate site licenses before installing or using the system. Utilisation de la bande 4.9 GHz FCC et ISEDC Le systme a t approuv en vertu d ISEDC RSS-111 pour l'utilisation par l'Agence de la Scurit publique. L'installateur ou l'exploitant est responsable de l'obtention des licences de appropries avant d'installer ou d'utiliser le systme. Page 10-59 Chapter 10: Reference Information Equipment Disposal 5.2 GHz and 5.4 GHz ISEDC notification This device complies with ISEDC RSS-247. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation. Users should be cautioned to take note that high power radars are allocated as primary users (meaning they have priority) of 5250 5350 MHz and 5650 5850 MHz and these radars could cause interference and/or damage to license-exempt local area networks (LELAN). For the connectorized version of the product and in order to reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (EIRP) is not more than that permitted by the regulations. The transmitted power must be reduced to achieve this requirement. Utilisation de la bande 5.2 and 5.4 GHz ISEDC Cet appareil est conforme ISEDC RSS-247. Son fonctionnement est soumis aux deux conditions suivantes: (1) Ce dispositif ne doit pas causer d'interfrences nuisibles, et (2) Cet appareil doit tolrer toute interfrence reue, y compris les interfrences pouvant entraner un fonctionnement indsirable. Les utilisateurs doivent prendre garde au fait que les radars haute puissance sont considres comme les utilisateurs prioritaires de 5250 5350 MHz et 5650 5850 MHz et ces radars peuvent causer des interfrences et / ou interfrer avec un rseau local ne ncessitant pas de licence. Pour la version du produit avec antenne externe et afin de rduire le risque d'interfrence avec d'autres utilisateurs, le type d'antenne et son gain doivent tre choisis afin que la puissance isotrope rayonne quivalente (PIRE) ne soit pas suprieure celle permise par la rglementation. Il peut tre ncessaire de rduire la puissance transmise doit tre rduite pour satisfaire cette exigence. ISEDC notification 5.8 GHz RSS-GEN issue 3 (7.1.3) Licence-Exempt Radio Apparatus:

This device complies with ISEDC license-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device. In Canada, high power radars are allocated as primary users (meaning they have priority) of the 5600 5650 MHz spectrum. These radars could cause interference or damage to license-exempt local area network (LE-LAN) devices. Utilisation de la bande 5.8 GHz ISEDC RSS-GEN issue 3 (7.1.3) appareil utilisant la bande sans licence:

Page 10-60 Chapter 10: Reference Information Equipment Disposal Le prsent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorise aux deux conditions suivantes : (1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible d'en compromettre le fonctionnement. Au Canada, les radars haute puissance sont dsigns comme utilisateurs principaux (ils ont la priorit) dans la bande 5600 5650 MHz. Ces radars peuvent causer des interfrences et / ou interfrer avec un rseau local ne ncessitant pas de licence. ISEDC certification numbers Table 259 ISEDC Certification Numbers ISEDC Product Frequency Channel Frequencies Maximum Cert. Band Bandwidth Combined Tx Output Power 109AO-

50450I 5 GHz AP, SM &

(Pending) BHM 5 MHz 4942.5 4987.5 MHz 24 dBm 4.9 GHz 10 MHz 4945.0 4985.0 MHz 24 dBm 20 MHz 4950.0 4980.0 MHz 23.5 dBm 5 MHz 5730.0 5845.0 MHz 28 dBm 5.8 GHz 10 MHz 5730.0 5845.0 MHz 28 dBm 20 MHz 5735.0 5840.0 MHz 28 dBm Canada approved antenna list Under ISEDC regulations, this radio transmitter may only operate using an antenna of a type and maximum (or lesser) gain approved for the transmitter by ISEDC . To reduce potential radio interference to other users, the antenna type and its gain must be so chosen that the equivalent isotropically radiated power (EIRP) is not more than that necessary for successful communication. Conformment la rglementation d'Industrie Canada, le prsent metteur radio peut fonctionner avec une antenne d'un type et d'un gain maximal (ou infrieur) approuv pour l'metteur par Industrie Canada. Dans le but de rduire les risques de brouillage radiolectrique l'intention des autres utilisateurs, il faut choisir le type d'antenne et son gain de sorte que la puissance isotrope rayonne quivalente (PIRE) ne dpasse pas l'intensit ncessaire l'tablissement d'une communication satisfaisante. This radio transmitter (identify the device by certification number) has been approved by ISEDC to operate with the antenna types listed in Country specific radio regulations, Innovation Science and Economic Development Canada (ISEDC) , Table 260 with the maximum permissible gain and required antenna impedance for each antenna type indicated. Antenna types not included in this list, having a gain greater than the maximum gain indicated for that type, are strictly prohibited for use with this device. Page 10-61 Chapter 10: Reference Information Equipment Disposal Le prsent metteur radio (identifier le dispositif par son numro de certification) a t approuv par Industrie Canada pour fonctionner avec les types d'antenne numrs dans la section Country specific radio regulations, Innovation Science and Economic Development Canada (ISEDC) , Table 260 et ayant un gain admissible maximal et l'impdance requise pour chaque type d'antenne. Les types d'antenne non inclus dans cette liste, ou dont le gain est suprieur au gain maximal indiqu, sont strictement interdits pour l'exploitation de l'metteur. Table 260 Canada approved antenna list 4.9 and 5.8 GHz Antenna type Description Manufacturer Reference Integrated flat Cambium N/A plate Networks Gain (dBi) 4.9 GHz 5.8 GHz 23 23 2 ft dual MARS MA-WA56-DP-28N polarised flat Antennas 28.5 28 Directional plate 4 ft parabolic Andrews PX4F-52-N7A/A dual polarised Antennas 6 ft Parabolic Gabriel QF6-49-N dual polarised Antennas Integrated Cambium A005240 N/A 35.3 37.2 N/A 90 sector flat Networks 16 16 plate Sector 90sector Cambium Networks 85009324001 60 sectorised Cambium 85009325001 Networks Omni-

Omni-

directional KP Antennas KPPA-5.7-DPOMA directional Omni-

MARS MA-WO56-DP10 directional Antennas 17 16 13 10 17 16 13 10 Page 10-62 Chapter 10: Reference Information Equipment Disposal Table 261 Canada approved antenna list 5.2 and 5.4 GHz Directivity Type Manufacturer Reference Integrated flat plate Cambium Networks N/A Stated Gain

(dBi) 23.0 Directional 2ft dual polarised Mars Antennas MA-WA56-DP-28N 28.5 flat plate 2ft dual polarised MTI MT-486013-NVH 28.5 parabolic Integrated 90 Cambium A005240 Sector sector flat plate Networks 90 sectorised Cambium Networks 85009324001 16.0 17.0 Dual polar omni-

KP KPPA-5.7-DPOMA 13.0 directional Dual polar omni-

Mars Antennas MA-WO56-DP10 10.0 directional Omni-

directional Page 10-63 Chapter 11: Troubleshooting Equipment Disposal Chapter 11: Troubleshooting This chapter contains procedures for identifying and correcting faults in a PMP/PTP 450 platform link. These procedures can be performed either on a newly installed link, or on an operational link if communication is lost, or after a lightning strike. The following topics are described in this chapter:

General troubleshooting procedure on page 11-65 Troubleshooting procedures on page 11-68 Power-up troubleshooting on page 11-77 Registration and connectivity troubleshooting on page 11-78 Page 11-64 Chapter 11: Troubleshooting General troubleshooting procedure General troubleshooting procedure General planning for troubleshooting Effective troubleshooting depends in part on measures that you take before you experience trouble in your network. Cambium recommends the following measures for each site:

Identify troubleshooting tools that are available at your site (such as a protocol analyzer). Identify commands and other sources that can capture baseline data for the site. These may include:

o Ping o Tracert or traceroute o Link Capacity Test results o Throughput data o Configuration tab captures o Status tab captures o Session logs o Web browser used Start a log for the site. Include the following information in the log:

o Operating procedures o Site-specific configuration records o Network topology o Software releases, boot versions and FPGA firmware versions o Types of hardware deployed o Site-specific troubleshooting processes o Escalation procedures Capture baseline data into the log from the sources listed above Page 11-65 Chapter 11: Troubleshooting General troubleshooting procedure General fault isolation process Effective troubleshooting also requires an effective fault isolation methodology that includes the following:

Attempting to isolate the problem to the level of a system, subsystem, or link, such as o AP to SM o AP to CMM4 o AP to GPS o Backhaul(BH) o Backhaul(BH) to CMM4 o Power Researching Event Logs of the involved equipment Interpreting messages in the Event Log Answering the questions listed in the following sections. Reversing the last previous corrective attempt before proceeding to the next. Performing only one corrective attempt at a time. Questions to help isolate the problem When a problem occurs, attempt to answer the following questions:

What is the history of the problem?

o Have we changed something recently?

o Have we seen other symptoms before this?

How wide-spread is the symptom?

o o Is the problem on only a single SM? (If so, focus on that SM.) Is the problem on multiple SMs? If so is the problem on one AP in the cluster? (If so, focus on that AP) is the problem on multiple, but not all, APs in the cluster? (If so, focus on those APs) is the problem on all APs in the cluster? (If so, focus on the CMM4 and the GPS signal.) Based on data in the Event Log o does the problem correlate to External Hard Resets with no WatchDog timers? (If so, this indicates a loss of power. Correct your power problem.) o is intermittent connectivity indicated? (If so, verify your configuration, power level, cables and connections and the speed duplex of both ends of the link). o does the problem correlate to loss-of-sync events?

Are connections made via shielded cables?

Does the GPS antenna have an unobstructed view of the entire horizon?

Has the site grounding been verified?

Page 11-66 Chapter 11: Troubleshooting General troubleshooting procedure Secondary Steps After preliminary fault isolation is completed through the above steps, follow these:

Check the Canopy knowledge base (https://support.cambiumnetworks.com/forum) to find whether other network operators have encountered a similar problem. Proceed to any appropriate set of diagnostic steps. These are organized as follows:

o Module has lost or does not establish connectivity on page 11-68 o NAT/DHCP-configured SM has lost or does not establish connectivity on page 11-70 o SM Does Not Register to an AP on page 11-72 o Module has lost or does not gain sync on page 11-73 o Module does not establish Ethernet connectivity on page 11-74 o CMM4 does not pass proper GPS sync to connected modules on page 11-75 o Module Software Cannot be Upgraded on page 11-76 o Module Functions Properly, Except Web Interface Became Inaccessible on page 11-76 Page 11-67 Chapter 11: Troubleshooting Troubleshooting procedures Troubleshooting procedures Proceed to any appropriate set of diagnostic steps. These are organized as follows:

Module has lost or does not establish connectivity on page 11-68 NAT/DHCP-configured SM has lost or does not establish connectivity on page 11-70 SM Does Not Register to an AP on page 11-72 Module has lost or does not gain sync on page 11-73 Module does not establish Ethernet connectivity on page 11-74 CMM4 does not pass proper GPS sync to connected modules on page 11-75 Module Software Cannot be Upgraded on page 11-76 Module Functions Properly, Except Web Interface Became Inaccessible on page 11-76 Module has lost or does not establish connectivity To troubleshoot a loss of connectivity, perform the following steps:

Procedure 36 Troubleshooting loss of connectivity 1 2 3 Isolate the end user/SM from peripheral equipment and variables such as routers, switches and firewalls. Set up the minimal amount of equipment. On each end of the link:

Check the cables and connections. Verify that the cable/connection schemestraight-through or crossoveris correct. Verify that the LED labeled LNK is green. Access the General Status tab in the Home page of the module. Verify that the SM is registered. Verify that Received Power Level is -87 dBm or higher. Access the IP tab in the Configuration page of the module. Verify that IP addresses match and are in the same subnet. If RADIUS authentication is configured, ensure that the RADIUS server is operational Page 11-68 Chapter 11: Troubleshooting Troubleshooting procedures 4 On the SM end of the link:

Verify that the PC that is connected to the SM is correctly configured to obtain an IP address through DHCP. Execute ipconfig (Windows) or ifconfig (linux) Verify that the PC has an assigned IP address. 5 On each end of the link:

Access the General tab in the Configuration page of each module. Verify that the setting for Link Speeds (or negotiation) matches that of the other module. Access the Radio tab in the Configuration page of each module. Verify that the Radio Frequency Carrier setting is checked in the Custom Radio Frequency Scan Selection List. Verify that the Color Code setting matches that of the other module. Access the browser LAN settings (for example, at Tools > Internet Options > Connections > LAN Settings in Internet Explorer). Verify that none of the settings are selected. Access the Link Capacity Test tab in the Tools page of the module. Perform a link test Verify that the link test results show efficiency greater than 90% in both the uplink and downlink Execute ping. o Verify that no packet loss was experienced. o Verify that response times are not significantly greater than 4 ms from AP to SM 15 ms from SM to AP o Replace any cables that you suspect may be causing the problem. Note A ping size larger than 1494 Bytes to a module times out and fails. However, a ping of this size or larger to a system that is behind a Canopy module typically succeeds. It is generally advisable to ping such a system, since Canopy handles that ping with the same priority as is given all other transport traffic. The results are unaffected by ping size and by the load on the Canopy module that brokers this traffic. 6 After connectivity has been re-established, reinstall network elements and variables that you removed in Step 1. Page 11-69 Chapter 11: Troubleshooting Troubleshooting procedures NAT/DHCP-configured SM has lost or does not establish connectivity Before troubleshooting this problem, identify the NAT/DHCP configuration from the following list:

NAT with DHCP Client (DHCP selected as the Connection Type of the WAN interface) and DHCP Server NAT with DHCP Client (DHCP selected as the Connection Type of the WAN interface) NAT with DHCP Server NAT without DHCP To troubleshoot a loss of connectivity for a SM configured for NAT/DHCP, perform the following steps. Page 11-70 Chapter 11: Troubleshooting Troubleshooting procedures Procedure 37 Troubleshooting loss of connectivity for NAT/DHCP-configured SM 1 2 3 Isolate the end user/SM from peripheral equipment and variables such as routers, switches and firewalls. Set up the minimal amount of equipment. On each end of the link:

Check the cables and connections. Verify that the cable/connection schemestraight-through or crossoveris correct. Verify that the LED labeled LNK is green. 4 At the SM:

Access the NAT Table tab in the Logs web page. Verify that the correct NAT translations are listed. RESULT: NAT is eliminated as a possible cause if these translations are correct. 5 If this SM is configured for NAT with DHCP, then at the SM:

Execute ipconfig (Windows) or ifconfig (Linux) Verify that the PC has an assigned IP address. If the PC does not have an assigned IP address, then o enter ipconfig /release Adapter Name. o enter ipconfig /renew Adapter Name. o reboot the PC. o after the PC has completed rebooting, execute ipconfig o if the PC has an assigned IP address, then o access the NAT DHCP Statistics tab in the Statistics web page of the SM. o verify that DHCP is operating as configured. 6 After connectivity has been re-established, reinstall network elements and variables that you removed in Step 1. Page 11-71 Chapter 11: Troubleshooting Troubleshooting procedures SM Does Not Register to an AP To troubleshoot a SM failing to register to an AP, perform the following steps. Procedure 38 Troubleshooting SM failing to register to an AP 1 2 3 4 5 6 7 8 9 10 11 Access the Radio tab in the Configuration page of the SM. Note the Color Code of the SM. Access the Radio tab in the Configuration page of the AP. Verify that the Color Code of the AP matches that of the SM. Note the Radio Frequency Carrier of the AP. Verify that the value of the RF Frequency Carrier of the AP is selected in the Custom Radio Frequency Scan Selection List parameter in the SM. In the AP, verify that the Max Range parameter is set to a distance slightly greater than the distance between the AP and the furthest SM that must register to this AP. Verify that no obstruction significantly penetrates the Fresnel zone of the attempted link. Access the General Status tab in the Home page of each module. Remove the bottom cover of the SM to expose the LEDs. Power cycle the SM. RESULT: Approximately 25 seconds after the power cycle, the green LED labeled LNK must light to indicate that the link has been established. If the orange LED labeled SYN is lit instead, then the SM is in Alignment mode because the SM failed to establish the link. 12 If the AP is configured to require authentication, ensure proper configuration of RADIUS or Pre-shared AP key. 13 In this latter case and if the SM has encountered no customer-inflicted damage, then request an RMA for the SM. Page 11-72 Chapter 11: Troubleshooting Troubleshooting procedures Module has lost or does not gain sync To troubleshoot a loss of sync, perform the following steps. Procedure 39 Troubleshooting loss of sync 1 2 3 4 Access the Event Log tab in the Home page of the SM Check for messages with the following format:

RcvFrmNum =

ExpFrmNum =

If these messages are present, check the Event Log tab of another SM that is registered to the same AP for messages of the same type. If the Event Log of this second SM does not contain these messages, then the fault is isolated to the first SM. If the Event Log page of this second SM contains these messages, access the GPS Status page of the AP. 5 If the Satellites Tracked field in the GPS Status page of the AP indicates fewer than 4 or the Pulse Status field does not indicate Generating Sync, check the GPS Status page of another AP in the same AP cluster for these indicators. GPS signal acquisition must not take longer than 5 minutes from unit startup. 6 If these indicators are present in the second AP, then:

Verify that the GPS antenna still has an unobstructed view of the entire horizon. Visually inspect the cable and connections between the GPS antenna and the CMM4. If this cable is not shielded, replace the cable with shielded cable 7 If these indicators are not present in the second AP, visually inspect the cable and connections between the CMM4 and the AP antenna. If this cable is not shielded, replace the cable with shielded cable. Page 11-73 Chapter 11: Troubleshooting Troubleshooting procedures Module does not establish Ethernet connectivity To troubleshoot a loss of Ethernet connectivity, perform the following steps:

Procedure 40 Troubleshooting loss of Ethernet connectivity 1 2 3 4 5 6 7 Verify that the connector crimps on the Ethernet cable are not loose. Verify that the Ethernet cable is not damaged. If the Ethernet cable connects the module to a network interface card (NIC), verify that the cable is pinned out as a straight-through cable. If the Ethernet cable connects the module to a hub, switch, or router, verify that the cable is pinned out as a crossover cable. Verify that the Ethernet port to which the cable connects the module is set to auto-

negotiate speed. Verify VLAN configuration in the network, which may cause loss of module access if the accessing device is on a separate VLAN from the radio. Power cycle the module. RESULT: Approximately 25 seconds after the power cycle, the green LED labeled LNK must light up to indicate that the link has been established. If the orange LED labeled SYN is lit instead, then the module is in Alignment mode because the module failed to establish the link. 8 In this latter case and if the module has encountered no customer-inflicted damage, then request an RMA for the module. Page 11-74 Chapter 11: Troubleshooting Troubleshooting procedures CMM4 does not pass proper GPS sync to connected modules If the Event Log tabs in all connected modules contain Loss of GPS Sync Pulse messages, perform the following steps. Procedure 41 Troubleshooting CMM4 not passing sync 1 2 3 4 Verify that the GPS antenna has an unobstructed view of the entire horizon. Verify that the GPS coaxial cable meets specifications. Verify that the GPS sync cable meets specifications for wiring and length. If the web pages of connected modules indicate any of the following, then find and eliminate the source of noise that is being coupled into the GPS sync cable:

In the GPS Status page:

o anomalous number of Satellites Tracked (greater than 12, for example) o incorrect reported Latitude and/or Longitude of the antenna In the Event Log page:

o garbled GPS messages o large number of Acquired GPS Sync Pulse messages GPS signal acquisition must not take longer than 5 minutes from unit startup. 5 If these efforts fail to resolve the problem, then request an RMA for the CMM4. Page 11-75 Chapter 11: Troubleshooting Troubleshooting procedures Module Software Cannot be Upgraded If your attempt to upgrade the software of a module fails, perform the following steps. Procedure 42 Troubleshooting an unsuccessful software upgrade 1 2 3 4 5 6 Download the latest issue of the target release and the associated release notes. Verify that the latest version of CNUT is installed. Compare the files used in the failed attempt to the newly downloaded software. Compare the procedure used in the failed attempt to the procedure in the newly downloaded release notes. If these comparisons reveal a difference, retry the upgrade, this time with the newer file or newer procedure. If, during attempts to upgrade the FPGA firmware, the following message is repeatable, then request an RMA for the module:

Error code 6, unrecognized device Module Functions Properly, Except Web Interface Became Inaccessible If a module continues to pass traffic and the SNMP interface to the module continues to function, but the web interface to the module does not display, perform the following steps:

Procedure 43 Restoring web management GUI access 1 2 3 4 Enter telnet DottedIPAddress. RESULT: A telnet session to the module is invoked. At the Login prompt, enter root. At the Password prompt, enter PasswordIfConfigured. At the Telnet +> prompt, enter reset. RESULT: The web interface is accessible again and this telnet connection is closed. Note The module may also be rebooted via an SNMP-based NMS (Wireless Manager, for example) 5 If the issue persists, turn off any SNMP-based network/radio monitoring software and repeat steps 1-4. Page 11-76 Chapter 11: Troubleshooting Power-up troubleshooting Power-up troubleshooting Page 11-77 Module does not power ONIs the LED always red?Is there AC power going to the supply?NoSwitch ON AC mains powerTest cable, use known good cable. Could the radio be in default modeYesYesTest cable?NoIs cable length < 300 meters?YesConnect to a known power supplyIs the modules red LED ON?YesYesModule is powered ONYesEthernet cable repairedContact Cambium Support for RMANoIs Modules power LED ON?NoAYesCable wire and pin out correctedCable length within 300 metersYesNoNoAConnect to known good module Is module getting powered ON?NoYes Chapter 11: Troubleshooting Registration and connectivity troubleshooting Registration and connectivity troubleshooting SM/BMS Registration If no SMs are registered to this AP, then the Session Status tab displays the simple message No sessions. In this case, try the following steps. 1 More finely aim the SM or SMs toward the AP. 2 3 4 5 6 7 8 9 Recheck the Session Status tab of the AP for the presence of LUIDs. If still no LUIDs are reported on the Session Status tab, click the Configuration button on the left side of the Home page. RESULT: The AP responds by opening the AP Configuration page. Click the Radio tab. Find the Color Code parameter and note the setting. In the same sequence as you did for the AP directly under Configuring Link for Test on Page 5-15, connect the SM to a computing device and to power. On the left side of the SM Home page, click the Configuration button. RESULT: The Configuration page of the SM opens. Click the Radio tab. If the transmit frequency of the AP is not selected in the Custom Radio Frequency Scan Selection List parameter, select the frequency that matches. 10 If the Color Code parameter on this page is not identical to the Color Code parameter you noted from the AP, change one of them so that they match. 11 At the bottom of the Radio tab for the SM, click the Save Changes button. 12 Click the Reboot button. 13 Allow several minutes for the SM to reboot and register to the AP. 14 Return to the computing device that is connected to the AP. 15 Recheck the Session Status tab of the AP for the presence of LUIDs. Page 11-78 Glossary Term 10Base-T Definition Technology in Ethernet communications that can deliver 10 Mb of data across 328 feet (100 meters) of CAT 5 cable. 169.254.0.0 Gateway IP address default in Cambium fixed wireless broadband IP network modules. 169.254.1.1 IP address default in Cambium fixed wireless broadband IP network modules. 255.255.0.0 Subnet mask default in Cambium fixed wireless broadband IP network modules and in Microsoft and Apple operating systems. 802.3 An IEEE standard that defines the contents of frames that are transferred through Ethernet connections. Each of these frames contains a preamble, the address to which the frame is sent, the address that sends the frame, the length of the data to expect, the data, and a checksum to validate that no contents were lost. Access Point Cluster Two to six Access Point Modules that together distribute network or Internet services to a community of subscribers. Each Access Point Module covers a 60 or 90 sector. This cluster covers as much as 360. Also known as AP cluster. Access Point Module Also known as AP. One module that distributes network or Internet services in a 60 or 90 sector. ACT/4 Second-from-left LED in the module. In the operating mode, this LED is lit when data activity is present on the Ethernet link. Address Resolution Protocol defined in RFC 826 to allow a network element to correlate Protocol a host IP address to the Ethernet address of the host. See http://www.faqs.org/rfcs/rfc826.html. Aggregate Throughput The sum of the throughputs in the uplink and the downlink. AP ARP Access Point Module. One module that distributes network or Internet services to subscriber modules. Address Resolution Protocol. A protocol defined in RFC 826 to allow a network element to correlate a host IP address to the Ethernet address of the host. See http://www.faqs.org/rfcs/rfc826.html. Page I Chapter 11: Troubleshooting Registration and connectivity troubleshooting Term APs MIB Definition Management Information Base file that defines objects that are specific to the Access Point Module. See also Management Information Base. ASN.1 Abstract Syntax Notation One language. The format of the text files that compose the Management Information Base. Attenuation Reduction of signal strength caused by the travel from the transmitter to the receiver, and caused by any object between. In the absence of objects between, a signal that has a short wavelength experiences a high degree of attenuation nevertheless. BER Bit Error Rate. The ratio of incorrect data received to correct data received. Bit Error Rate Ratio of incorrect data received to correct data received. Box MIB Management Information Base file that defines module-level objects. See also Management Information Base. Bridge Network element that uses the physical address (not the logical address) of another to pass data. The bridge passes the data to either the destination address, if found in the simple routing table, or to all network segments other than the one that transmitted the data. Modules are Layer 2 bridges except that, where NAT is enabled for an SM, the SM is a Layer 3 switch. Compare to Switch and Router, and see also NAT. Buckets Theoretical data repositories that can be filled at preset rates or emptied when preset conditions are experienced, such as when data is transferred. Burst Preset amount limit of data that may be continuously transferred. CAT 5 Cable Cable that delivers Ethernet communications from module to module. Later modules auto-sense whether this cable is wired in a straight-through or crossover scheme. CIR Committed Information Rate. For an SM or specified group of SMs, a level of bandwidth that can be guaranteed to never fall below a specified minimum (unless oversubscribed). In the Cambium implementation, this is controlled by the Low Priority Uplink CIR, Low Priority Downlink CIR, High Priority Uplink CIR, and High Priority Downlink CIR parameters. Cluster Management Module that provides power, GPS timing, and networking Module CMM connections for an AP cluster. Also known as CMM4. Cluster Management Module. A module that provides power, GPS timing, and networking connections for an Access Point cluster. Page II Chapter 11: Troubleshooting Registration and connectivity troubleshooting Term Definition CodePoint See DiffServ. Color Code Field Module parameter that identifies the other modules with which communication is allowed. The range of valid values is 0 to 255. Community String Field Control string that allows a network management station to access MIB information about the module. Country Code A parameter that offers multiple fixed selections, each of which automatically implements frequency band range restrictions for the selected country. Units shipped to countries other than the United States must be configured with the corresponding Region Code and Country Code to comply with local regulatory requirements. CRCError Field This field displays how many CRC errors occurred on the Ethernet controller. Data Encryption Standard Over-the-air link option that uses secret 56-bit keys and 8 parity bits. Data Encryption Standard (DES) performs a series of bit permutations, substitutions, and recombination operations on blocks of data. Demilitarized Zone Internet Protocol area outside of a firewall. Defined in RFC 2647. See http://www.faqs.org/rfcs/rfc2647.html. DES Data Encryption Standard. An over-the-air link option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on DFS DHCP blocks of data. See Dynamic Frequency Selection Dynamic Host Configuration Protocol, defined in RFC 2131. Protocol that enables a device to be assigned a new IP address and TCP/IP parameters, including a default gateway, whenever the device reboots. Thus DHCP reduces configuration time, conserves IP addresses, and allows modules to be moved to a different network within the system. See http://www.faqs.org/rfcs/rfc2131.html. See also Static IP Address Assignment. Page III Chapter 11: Troubleshooting Registration and connectivity troubleshooting Term DiffServ Definition Differentiated Services, consistent with RFC 2474. A byte in the type of service (TOS) field of packets whose values correlates to the channel on which the packet should be sent. The value is a numeric code point. Cambium modules map each of 64 code points to values of 0 through 7. Three of these code points have fixed values, and the remaining 61 are settable. Values of 0 through 3 map to the low-priority channel; 4 through 7 to the high-priority channel. The mappings are the same as 802.1p VLAN priorities. (However, configuring DiffServ does not automatically enable the VLAN feature.) Among the settable parameters, the values are set in the AP for all downlinks within the sector and in the SM for each uplink. DMZ Demilitarized Zone as defined in RFC 2647. An Internet Protocol area Dynamic Frequency Selection outside of a firewall. See http://www.faqs.org/rfcs/rfc2647.html. A requirement in certain countries and regions for systems to detect interference from other systems, notably radar systems, and to avoid co-channel operation with these systems. Dynamic Host See DHCP. Configuration Protocol Electronic Serial Number Hardware address that the factory assigns to the module for identification in the Data Link layer interface of the Open Systems Interconnection system. This address serves as an electronic serial number. Same as MAC Address. ESN Electronic Serial Number. The hardware address that the factory assigns to the module for identification in the Data Link layer interface of the Open Systems Interconnection system. This address serves as an electronic serial number. Same as MAC Address. Ethernet Protocol Any of several IEEE standards that define the contents of frames that are transferred from one network element to another through Ethernet connections. ETSI European Telecommunications Standards Institute Fade Margin The difference between strength of the received signal and the strength that the receiver requires for maintaining a reliable link. A higher fade margin is characteristic of a more reliable link. Standard operating margin. FCC Federal Communications Commission of the U.S.A. Field-programmable Gate Array of logic, relational data, and wiring data that is factory Array programmed and can be reprogrammed. Page IV Chapter 11: Troubleshooting Registration and connectivity troubleshooting Term Definition File Transfer Protocol Utility that transfers of files through TCP (Transport Control Protocol) between computing devices that do not operate on the same platform. Defined in RFC 959. See http://www.faqs.org/rfcs/rfc959.html. FPGA Field-programmable Gate Array. An array of logic, relational data, and wiring data that is factory programmed and can be reprogrammed. Free Space Path Loss Signal attenuation that is naturally caused by atmospheric conditions and by the distance between the antenna and the receiver. Fresnel Zone Space in which no object should exist that can attenuate, diffract, or reflect a transmitted signal before the signal reaches the target receiver. FTP File Transfer Protocol, defined in RFC 959. Utility that transfers of files through TCP (Transport Control Protocol) between computing devices that do not operate on the same platform. See http://www.faqs.org/rfcs/rfc959.html. Global Positioning Network of satellites that provides absolute time to networks on System earth, which use the time signal to synchronize transmission and reception cycles (to avoid interference) and to provide reference for troubleshooting activities. GPS Global Positioning System. A network of satellites that provides absolute time to networks on earth, which use the time signal to synchronize transmission and reception cycles (to avoid interference) and to provide reference for troubleshooting activities. GPS/3 Third-from-left LED in the module. In the operating mode for an Access Point Module, this LED is continuously lit as the module receives sync pulse. In the operating mode for a Subscriber, this LED flashes on and off to indicate that the module is not registered. GUI Graphical user interface. High-priority Channel Channel that supports low-latency traffic (such as Voice over IP) over low-latency traffic (such as standard web traffic and file downloads). To recognize the latency tolerance of traffic, this channel reads the IPv4 Type of Service DiffServ Control Point

(DSCP) bits. Enabling the high-priority channel reduces the maximum number of SMs that can be served in the sector. HTTP Hypertext Transfer Protocol, used to make the Internet resources available on the World Wide Web. Defined in RFC 2068. See http://www.faqs.org/rfcs/rfc2068.html. Page V Chapter 11: Troubleshooting Registration and connectivity troubleshooting Term HTTPS ICMP Definition Hypertext Transfer Protocol Secure (HTTPS) Internet Control Message Protocols defined in RFC 792, used to identify Internet Protocol (IP)-level problems and to allow IP links to be tested. See http://www.faqs.org/rfcs/rfc792.html. IP Internet Protocol defined in RFC 791. The Network Layer in the TCP/IP protocol stack. This protocol is applied to addressing, routing, and delivering, and re-assembling data packets into the Data Link layer of the protocol stack. See http://www.faqs.org/rfcs/rfc791.html. IP Address 32-bit binary number that identifies a network element by both network and host. See also Subnet Mask. IPv4 ISM Traditional version of Internet Protocol, which defines 32-bit fields for data transmission. Industrial, Scientific, and Medical Equipment radio frequency band, in the 900-MHz, 2.4-GHz, and 5.8-GHz ranges. L2TP over IPSec Level 2 Tunneling Protocol over IP Security. One of several virtual private network (VPN) implementation schemes. Regardless of whether Subscriber Modules have the Network Address Translation feature (NAT) enabled, they support VPNs that are based on this protocol. Late Collision Field This field displays how many late collisions occurred on the Ethernet controller. A normal collision occurs during the first 512 bits of the frame transmission. A collision that occurs after the first 512 bits is considered a late collision. A late collision is a serious network problem because the frame being transmitted is discarded. A late collision is most commonly caused by a mismatch between duplex configurations at the ends of a link segment. Line of Sight Wireless path (not simply visual path) direct from module to module. The path that results provides both ideal aim and an ideal Fresnel zone. LNK/5 Furthest left LED in the module. In the operating mode, this LED is continuously lit when the Ethernet link is present. In the aiming mode for a Subscriber Module, this LED is part of a bar graph that indicates the quality of the RF link. Logical Unit ID Final octet of the 4-octet IP address of the module. LOS Line of sight. The wireless path (not simply visual path) direct from module to module. The path that results provides both ideal aim and an ideal Fresnel zone. Page VI Chapter 11: Troubleshooting Registration and connectivity troubleshooting Term LUID Definition Logical Unit ID. The final octet of the 4-octet IP address of the module. MAC Address Media Access Control address. The hardware address that the factory assigns to the module for identification in the Data Link layer interface of the Open Systems Interconnection system. This address serves as an electronic serial number. Management Information Space that allows a program (agent) in the network to relay Base information to a network monitor about the status of defined variables (objects). Maximum Information The cap applied to the bandwidth of an SM or specified group of Rate (MIR) SMs. In the Cambium implementation, this is controlled by the MIB MIR NAT NEC Sustained Uplink Data Rate, Uplink Burst Allocation, Sustained Downlink Data Rate, and Downlink Burst Allocation parameters. Management Information Base. Space that allows a program

(agent) in the network to relay information to a network monitor about the status of defined variables (objects). See Maximum Information Rate. Network Address Translation defined in RFC 1631. A scheme that isolates Subscriber Modules from the Internet. See http://www.faqs.org/rfcs/rfc1631.html. National Electrical Code. The set of national wiring standards that are enforced in the U.S.A. NetBIOS Protocol defined in RFC 1001 and RFC 1002 to support an applications programming interface in TCP/IP. This interface allows a computer to transmit and receive data with another host computer on the network. RFC 1001 defines the concepts and methods. RFC 1002 defines the detailed specifications. See http://www.faqs.org/rfcs/rfc1001.html and http://www.faqs.org/rfcs/rfc1002.html. Network Address Scheme that defines the Access Point Module as a proxy server to Translation isolate registered Subscriber Modules from the Internet. Defined in RFC 1631. See http://www.faqs.org/rfcs/rfc1631.html. Network Management See NMS. Station NMS Network Management Station. A monitor device that uses Simple Network Management Protocol (SNMP) to control, gather, and report information about predefined network variables (objects). See also Simple Network Management Protocol. Page VII Chapter 11: Troubleshooting Registration and connectivity troubleshooting Term Definition Default Mode Device that enables the operator to regain control of a module that has been locked by the No Remote Access feature, the 802.3 Link Disable feature, or a password or IP address that cannot be recalled. This device can be either fabricated on site or ordered. PMP See Point-to-Multipoint Protocol. Point-to-Multipoint Defined in RFC 2178, which specifies that data that originates from a Protocol central network element can be received by all other network elements, but data that originates from a non-central network element can be received by only the central network element. See http://www.faqs.org/rfcs/rfc2178.html. Also referenced as PMP. PPPoE Point to Point Protocol over Ethernet. Supported on SMs for operators who use PPPoE in other parts of their network operators who want to deploy PPPoE to realize per-subscriber authentication, PPS PPTP metrics, and usage control. Packet Per Second Point to Point Tunneling Protocol. One of several virtual private network implementations. Regardless of whether the Network Address Translation (NAT) feature enabled, Subscriber Modules support VPNs that are based on this protocol. Protective Earth Connection to earth (which has a charge of 0 volts). Also known as ground. Proxy Server Network computer that isolates another from the Internet. The proxy server communicates for the other computer, and sends replies to only the appropriate computer, which has an IP address that is not unique or not registered. Radio Signal Strength Relative measure of the strength of a received signal. An acceptable Indicator link displays a Radio Signal Strength Indicator (RSSI) value of greater than 700. Reflection Change of direction and reduction of amplitude of a signal that encounters an object larger than the wavelength. Reflection may cause an additional copy of the wavelength to arrive after the original, unobstructed wavelength arrives. This causes partial cancellation of the signal and may render the link unacceptable. However, in some instances where the direct signal cannot be received, the reflected copy may be received and render an otherwise unacceptable link acceptable. Page VIII Chapter 11: Troubleshooting Registration and connectivity troubleshooting Term Definition Region Code A parameter that offers multiple fixed selections, each of which automatically implements frequency band range restrictions for the selected region. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. RF Radio frequency. How many times each second a cycle in the antenna occurs, from positive to negative and back to positive amplitude. RJ-12 RJ-45 Standard cable that is typically used for telephone line or modem connection. Standard cable that is typically used for Ethernet connection. This cable may be wired as straight-through or as crossover. Later modules auto-sense whether the cable is straight-through or crossover. Router Network element that uses the logical (IP) address of another to pass data to only the intended recipient. Compare to Switch and Bridge. RSSI Radio Signal Strength Indicator. A relative measure of the strength of a received signal. An acceptable link displays an RSSI value of greater than 700. Self-interference Interference with a module from another module in the same network. Simple Network Standard that is used for communications between a program Management Protocol

(agent) in the network and a network management station

(monitor). Defined in RFC 1157. See http://www.faqs.org/rfcs/rfc1157.html. SM Customer premises equipment (CPE) device that extends network or Internet services by communication with an Access Point Module or SNMP SNMPv3 an Access Point cluster. See Simple Network Management Protocol, defined in RFC 1157. SNMP version 3 SNMP Trap Capture of information that informs the network monitor through Simple Network Management Protocol of a monitored occurrence in the module. Page IX Chapter 11: Troubleshooting Registration and connectivity troubleshooting Term Definition Static IP Address Assignment of Internet Protocol address that can be changed only Assignment manually. Thus static IP address assignment requires more configuration time and consumes more of the available IP addresses than DHCP address assignment does. RFC 2050 provides guidelines for the static allocation of IP addresses. See http://www.faqs.org/rfcs/rfc2050.html. See also DHCP. Subnet Mask 32-bit binary number that filters an IP address to reveal what part identifies the network and what part identifies the host. The number of subnet mask bits that are set to 1 indicates how many leading bits of the IP address identify the network. The number of subnet mask bits that are set 0 indicate how many trailing bits of the IP address identify the host. Subscriber Module Customer premises equipment (CPE) device that extends network or Internet services by communication with an Access Point Module or an Access Point cluster. Sustained Data Rate Preset rate limit of data transfer. Switch Network element that uses the port that is associated with the physical address of another to pass data to only the intended recipient. Compare to Bridge and Router. Sync GPS (Global Positioning System) absolute time, which is passed from one module to another. Sync enables timing that prevents modules from transmitting or receiving interference. Sync also provides correlative time stamps for troubleshooting efforts. TCP Alternatively known as Transmission Control Protocol or Transport Control Protocol. The Transport Layer in the TCP/IP protocol stack. This protocol is applied to assure that data packets arrive at the target network element and to control the flow of data through the Internet. Defined in RFC 793. See http://www.faqs.org/rfcs/rfc793.html. TDD Time Division Duplexing. Synchronized data transmission with some time slots allocated to devices transmitting on the uplink and some to the device transmitting on the downlink. telnet Utility that allows a client computer to update a server. A firewall can prevent the use of the telnet utility to breach the security of the server. See http://www.faqs.org/rfcs/rfc818.html, http://www.faqs.org/rfcs/rfc854.html and http://www.faqs.org/rfcs/rfc855.html. Tokens Theoretical amounts of data. See also Buckets. Page X Chapter 11: Troubleshooting Registration and connectivity troubleshooting Term Definition TxUnderrun Field This field displays how many transmission-underrun errors occurred on the Ethernet controller. UDP User Datagram Protocol. A set of Network, Transport, and Session udp U-NII VID VLAN Layer protocols that RFC 768 defines. These protocols include checksum and address information but does not retransmit data or process any errors. See http://www.faqs.org/rfcs/rfc768.html. User-defined type of port. Unlicensed National Information Infrastructure radio frequency band, in the 5.1GHz through 5.8 GHz ranges. VLAN identifier. See also VLAN. Virtual local area network. An association of devices through software that contains broadcast traffic, as routers would, but in the switch-level protocol. VPN Virtual private network for communication over a public network. One typical use is to connect remote employees, who are at home or in a different city, to their corporate network over the Internet. Any of several VPN implementation schemes is possible. SMs support L2TP over IPSec (Level 2 Tunneling Protocol over IP Security) VPNs and PPTP (Point to Point Tunneling Protocol) VPNs, regardless of whether the Network Address Translation (NAT) feature enabled. Page XI

 

 

Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 SM 3.5 GHz Table 154 PMP 450 SM Radio attributes 3.5 GHz Attribute Custom Radio Frequency Scan Selection List See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132. Meaning Check the frequencies that SM has to scan for AP transmissions. See Radio Frequency Scan Selection List on page 7-169. Page 7-164 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 SM 2.4 GHz Table 155 PMP 450 SM Radio attributes 2.4 GHz Attribute Custom Radio Frequency Scan Selection List See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132. Meaning Check the frequencies that SM has to scan for AP transmissions. See Radio Frequency Scan Selection List on page 7-169. Page 7-165 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 SM 900 MHz Table 156 PMP 450 SM Radio attributes 900 MHz Meaning See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132. See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132. Attribute Custom Radio Frequency Scan Selection List Channel Bandwidth Scan Cyclic Prefix Scan AP Selection Method Page 7-166 Chapter 7: Configuration Configuring radio parameters Color Code 1 Installation Color Code Large VC data Queue Color Code External Gain Receive Quality Debug See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132 See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132. Note The frequencies that a user can select are controlled by the country or a region and the Channel Bandwidth selected. There can be a case where a user adds a custom frequency

(from the Custom Frequencies page on page 7-172) and cannot see it in the pull down menu. Page 7-167 Chapter 7: Configuration Configuring radio parameters Radio page - PTP 450 BHM 5 GHz Table 157 PTP 450 BHM Radio attributes 5 GHz Attribute Refer Table 145 PTP 450i BHM Radio page attributes 5 GHz on page 7-145 for all parameters details. Meaning Page 7-168 Chapter 7: Configuration Configuring radio parameters Radio page - PTP 450 BHS 5 GHz Table 158 PTP 450 BHM Radio attributes 5 GHz Page 7-169 Chapter 7: Configuration Configuring radio parameters Meaning Attribute Refer Table 146 PTP 450i BHS Radio attributes 5 GHz on page 7-148 for all parameters details. Radio Frequency Scan Selection List The SM or BHS scans complete spectrum as per Full Spectrum Band Scan feature. SMs or BHS first boot into the smallest selected channel bandwidth (10 MHz, if selected) and scan all selected frequencies across both the 5.4 GHz and 5.7 GHz frequency bands. After this scan, if a wider channel bandwidth is selected (20 MHz), the SM/BHS automatically changes to 20 MHz channel bandwidth and then scans for APs/BHSs. After the SM/BHS finishes this final scan it will evaluate the best AP/BHM with which to register. If required for registration, the SM/BHS changes its channel bandwidth back to 10 MHz to match the best AP/BHM. The SM/BHS will attempt to connect to an AP/BHM based on power level (which affects the modulation state), channel bandwidth (which affects throughput) and number of SM/BHS registrations to the AP/BHM

(which affects system contention performance). If it is desired to prioritize a certain AP/BHM over other available APs/BHMs, operators may use the Color Code Priority feature on the SM/BHS. Utilization of the Color Code feature on the AP/BHM is recommended to further constrain the AP selection. If the SM does not find any suitable APs/BHMs for registration after scanning all channel bandwidths, the SM restarts the scanning process beginning with the smallest configured channel bandwidth. Selecting multiple frequencies and multiple channel bandwidths impacts the SM/BHS scanning time. The biggest consumption of time is in the changing of the SM/BHS channel bandwidth setting. The worst case scanning time is approximately two minutes after boot up (SM/BHS with all frequencies and channel bandwidths selected and registering to an AP/BHM at 10 MHz). If only one channel bandwidth is selected the time to scan all the available frequencies and register to an AP/BHM is approximately one minute after boot up. Other scanning features such as Color Code, Installation Color Code, and RADIUS authentication are unaffected by the Full Band Scan feature. Page 7-170 Chapter 7: Configuration Configuring radio parameters Dedicated Multicast Virtual Circuit (VC) A Multicast VC allows to configure multicast packets to be transmitted over a dedicated channel at a configurable rate of 1X, 2X, 4X or 8X. This feature is available only for the PMP 450 and PMP 450i and is not backward compatible with PMP 430 series of radios. To configure Multicast VC, the AP must have this enabled. This can be enabled in the Multicast Data Control section (under Configuration > Radio page). The default value is Disable. If set to the default value, all multicast packets are transmitted over the Broadcast VC data path. To enable, select the data rate that is desired for the Multicast VC Data Rate parameter and click Save Changes button. The radio requires no reboot after any changes to this parameter. The multicast VC allows three different parameters to be configured on the AP. These can be changed on the fly and are saved on the flash memory. Note If the Multicast VC Data Rate is set to a modulation that the radio is not currently capable of or operates in non-permitted channel conditions, multicast data is sent but not received. Ex: If Multicast VC Data Rate is set to 6x and the channel conditions only permit 4x mode of operation, then multicast data is sent at 6x modulation but the SM will not receive the data. Note The PMP 450 AP supports up to 119 VCs (instead of 238 VCs) when configured for 30 MHz channel bandwidth or 5 ms Frame Period. This limitation is not applicable for PMP 450i/450m Series. Note Actual Multicast CIR honored by the AP = Configured Multicast CIR/ (Multicast Repeat Count + 1). Increasing the Multicast data rate has no impact on the Unicast data rate. For multicast and unicast traffic mix scenario examples, see Table 159. Table 159 Example for mix of multicast and unicast traffic scenarios Repeat Count 0 1 2 Multicast Data Rate (Mbps) 10 5 Unicast Data Rate (Mbps) 40 40 Aggregate DL Data Rate (Mbps) 50 45 3.33 40 43.33 The statistics have been added to the Data VC page (under Statistics > Data VC). The table displays the multicast row on the PMP 450 Platform Family AP. The SM displays the multicast row if it is a PMP 450 Platform Family. Page 7-171 Chapter 7: Configuration Figure 144 Multicast VC statistics Configuring radio parameters The AP and SM display Transmit and Receive Multicast Data Count (under the Statistics > Scheduler page), as shown in Figure 145. Figure 145 Multicast scheduler statistics Page 7-172 Chapter 7: Configuration Configuring radio parameters Custom Frequencies page In addition to the Radio tab, AP/SM/BH has another tab called Custom Frequencies as shown in Table 160. The custom frequency tab allows to configure custom frequency at 1 KHz raster. It means that the custom frequencies can be at granularity of 1 KHz e.g. 4910.123 MHz, 4922.333 MHz, 4933.421 MHz etc. Note Ensure that a customer frequency exists before using SNMP to set the radio to a Custom Frequency. Table 160 450 Platform Family AP/SM/BH Custom Frequencies page 5 GHz Attribute Custom Frequency Configuration Meaning Custom frequencies with a channel raster of 1 KHz can be added from the available range by keying in the frequency and then clicking the Add Frequency button. Click Remove Frequency button to delete a specific frequency keyed in the text box. Click Default Frequencies button to add a pre-defined list of frequencies that can be used in this band. This list can be reduced or increased by manually removing or adding other custom frequencies. Custom Frequencies Displays the complete list of user configured custom frequencies. Page 7-173 Chapter 7: Configuration Configuring radio parameters Table 161 PMP/PTP 450 SM/BH Custom Frequencies page 3.65 GHz Attribute Custom Frequency Configuration Meaning Custom frequencies with a channel raster of 1 KHz can be added from the available range by keying in the frequency and then clicking the Add Frequency button. Click Remove Frequency button to delete a specific frequency keyed in the text box. Click Default Frequencies button to add a pre-defined list of frequencies that can be used in this band. This list can be reduced or increased by manually removing or adding other custom frequencies. Custom Frequencies Displays the complete list of user configured custom frequencies. Page 7-174 Chapter 7: Configuration Configuring radio parameters Table 162 PMP/PTP 450 SM/BH Custom Frequencies page 3.5 GHz Attribute Custom Frequency Configuration Meaning Custom frequencies with a channel raster of 1 KHz can be added from the available range by keying in the frequency and then clicking the Add Frequency button. Click Remove Frequency button to delete a specific frequency keyed in the text box. Click Default Frequencies button to add a pre-defined list of frequencies that can be used in this band. This list can be reduced or increased by manually removing or adding other custom frequencies. Page 7-175 Chapter 7: Configuration Configuring radio parameters DFS for 5 GHz Radios Dynamic Frequency Selection (DFS) is a requirement in several countries and regions for 5 GHz unlicensed systems to detect radar systems and avoid co-channel operation. DFS and other regulatory requirements drive the settings for the following parameters, as discussed in this section:

Country Code Primary Frequency Alternate 1 and Alternate 2 Frequencies External Antenna Gain On the AP, the Home > DFS Status page shows current DFS status of all three frequencies and a DFS log of past DFS events. Figure 146 AP DFS Status DFS operation The ODUs use region-specific DFS based on the Country Code selected on the modules Configuration, General page. By directing installers and technicians to set the Country Code correctly, the operator gains confidence the module is operating according to national or regional regulations without having to deal with the details for each region. The details of DFS operation for each Country Code, including whether DFS is active on the AP, SM, and which DFS regulations apply is shown in Table 259 on page 10-47. Page 7-176 Chapter 7: Configuration Configuring radio parameters Contention slots The SM uses reserved Contention slots and unused data slots for bandwidth requests. Uplink Data Slots are used first for data. If they are not needed for data in a given frame, the remaining data slots can be used by the SMs for bandwidth requests. This allows SMs in sectors with a small number of Contention slots configured to still successfully transmit bandwidth requests using unused data slots. A higher number of Contention slots give higher probability that a SMs bandwidth request is correctly received when the system is heavily loaded, but with the tradeoff that sector capacity is reduced, so there is less capacity to handle the request. The sector capacity reduction is about 200 kbps for each Contention slot configured in a 20 MHz channel at QPSK MIMO-A modulation. The reduction in sector capacity is proportionally higher at MIMO-B modulations (2 times at QPSK MIMO-B, 4 times at 16 QAM MIMO-B, 6 times at 64 QAM MIMO-B and 8 times at 256 QAM MIMO-B). If very few reserved Contention slots are specified, then latency increases in high traffic periods. If too many are specified, then the maximum capacity is unnecessarily reduced. The suggested Contention slot settings as a function of the number of active SMs in the sector are shown in the table below. Table 163 Contention slots and number of SMs Number of SMs 1 to 10 Recommended Number of Contention slots 11 to 50 51 to 150 3 4 6 8 151 and above In a typical cluster, each AP must be set to the same number of Contention slots to assure proper timing in the send and receive cycles. However, where high incidence of small packets exists, as in a sector that serves several VoIP streams, additional Contention slots may provide better results. For APs in a cluster of mismatched Contention slots setting, or where PMP 450/450i Series is collocated with radios using different technologies, like PMP 430 or FSK, in the same frequency band, use the frame calculator. To download the PMP 450 Contention Slots Paper, see http://www.cambiumnetworks.com/solution-papers/pmp-450-contention-slots. For co-location of radios with mismatched configuration parameters, see the co-location tool available here:

https://support.cambiumnetworks.com/files/colocationtool/

Page 7-177 Chapter 7: Configuration Configuring radio parameters MIMO-A mode of operation 450 Platform Family supports MIMO-B mode using the following modulation levels: QPSK, 16-QAM, 64-

QAM and 256-QAM. System Release 13.2 introduces MIMO-A mode of operation using the same modulation levels as the MIMO-B mode. With MIMO-B, the radio sends different streams of data over the two antennas whereas with MIMO-A, the radio uses a scheme that tries to optimize coverage by transmitting the same data over both antennas. This redundancy improves the signal to noise ratio at the receiver making it more robust, at the cost of throughput. In addition to introducing MIMO-A modes, improvements have been made to the existing rate adapt algorithm to switch between MIMO-A and MIMO-B seamlessly without any intervention or added configuration by the operator. The various modulation levels used by the 450 Platform Family are shown in Table 164. Table 164 450 Platform Family Modulation levels MIMO-A Rate QPSK 1X MIMO-A 2X MIMO-A 16-QAM 64-QAM 3X MIMO-A MIMO-B 2X MIMO-B 4X MIMO-B 6X MIMO-B 265-QAM 8X MIMO-B 4X MIMO-A System Performance For System Performance details of all the 450 Platform Family ODUs, refer to the tools listed below:

Link Capacity Planner for PMP/PTP 450 and 450i:

https://support.cambiumnetworks.com/files/capacityplanner/

LINKPlanner for PMP/PTP 450/450i and PMP 450m:

https://support.cambiumnetworks.com/files/linkplanner/

Page 7-178 Chapter 7: Configuration Configuring radio parameters Table 165 Co-channel Interference per (CCI) MCS MCS of Victim 1X (QPSK SISO) MCS of Interferer 6X (64-QAM MIMO-B) 2X (16-QAM SISO) 6X (64-QAM MIMO-B) 3X (64-QAM SISO) 6X (64-QAM MIMO-B) 1X (QPSK MIMO-A) 6X (64-QAM MIMO-B) 2X (16-QAM MIMO-A) 6X (64-QAM MIMO-B) 3X (64-QAM MIMO-A) 6X (64-QAM MIMO-B) 4X (256-QAM MIMO-A) 6X (64-QAM MIMO-B) 2X (QPSK MIMO-B) 6X (64-QAM MIMO-B) 4X (16-QAM MIMO-B) 6X (64-QAM MIMO-B) 6X (64-QAM MIMO-B) 6X (64-QAM MIMO-B) 8X (256-QAM MIMO-B) 6X (64-QAM MIMO-B) 7 dB 10 dB 17 dB 25 dB Channel BW (MHz) CCI 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 14 dB 22 dB 30 dB 10 dB 17 dB 25 dB 33 dB Table 166 Adjacent Channel Interference (ACI) per MCS MCS of Victim 1X (QPSK SISO) MCS of Interferer 6X (64-QAM MIMO-B) Channel BW (MHz) ACI 5, 7, 10, 15, 20, 30, or 40

-16 dB Guard Band None 2X (16-QAM SISO) 6X (64-QAM MIMO-B) 3X (64-QAM SISO) 6X (64-QAM MIMO-B) 1X (QPSK MIMO-A) 6X (64-QAM MIMO-B) 2X (16-QAM MIMO-A) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40

-16 dB

-16 dB

-13 dB

-13 dB None None None None Page 7-179 Chapter 7: Configuration 3X (64-QAM MIMO-A) 6X (64-QAM MIMO-B) 4X (256-QAM MIMO-A) 6X (64-QAM MIMO-B) 2X (QPSK MIMO-B) 6X (64-QAM MIMO-B) 4X (16-QAM MIMO-B) 6X (64-QAM MIMO-B) 6X (64-QAM MIMO-B) 6X (64-QAM MIMO-B) 8X (256-QAM MIMO-B) 6X (64-QAM MIMO-B) Configuring radio parameters 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40

-13 dB

-10 dB

-16 dB

-16 dB

-16 dB

-10 dB None None None None None None Guard Band When synchronized, no Guard Bands are needed for the 450* and 450i Series.

* For PMP 450 AP (3.6 GHz) and 450 platform APs with 450b SM (5 GHz) connected, Configuration -> Radio ->

Power Control -> Adjacent Channel Support must be enabled. Improved PPS performance of 450 Platform Family The 450m, 450i, and 450b Series provides improved packets per second (PPS) performance compared to 450 Series. Through hardware and software enhancements, the PPS performance of the PMP 450i Series AP and PMP 450b SM has been improved to 40k packets/second, measured through a standard RFC2544 test using 64 bytes packets. With this enhancement, operators are able to provide higher bandwidth including better VoIP and video services to end customers using existing SM deployments. PMP 450m supports 100k packets/second. Page 7-180 Chapter 7: Configuration Setting up SNMP agent Setting up SNMP agent Operators may use SNMP commands to set configuration parameters and retrieve data from the AP and SM modules. Also, if enabled, when an event occurs, the SNMP agent on the 450 Platform Family sends a trap to whatever SNMP trap receivers configured in the management network. SNMPv2c SNMPv3 Page 7-181 Chapter 7: Configuration Setting up SNMP agent Configuring SM/BHSs IP over-the-air access To access the SM/BHS management interface from a device situated above the AP, the SM/BHSs Network Accessibility parameter (under the web GUI at Configuration > IP) may be set to Public. Table 167 LAN1 Network Interface Configuration tab of IP page attributes Attribute IP Address Meaning Internet Protocol (IP) address. This address is used by family of Internet protocols to uniquely identify this unit on a network. Network Accessibility Subnet Mask Gateway IP Address DHCP state DNS IP Address Specify whether the IP address of the SM/BHS must be visible to only a device connected to the SM/BHS by Ethernet (Local) or be visible to the AP/BHM as well (Public). If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the subnet mask of the SM/BHS for RF management traffic. If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the gateway IP address for the SM/BHS for RF management traffic. If Enabled is selected, the DHCP server automatically assigns the IP configuration (IP address, subnet mask, and gateway IP address) and the values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable (read only), in the Network Interface tab of the Home page. Canopy devices allow for configuration of a preferred and alternate DNS server IP address either automatically or manually. Devices must set DNS server IP address manually when DHCP is disabled for the management interface of the device. The default DNS IP addresses are 0.0.0.0 when configured manually. Preferred DNS Server The first address used for DNS resolution. Alternate DNS Server If the Preferred DNS server cannot be reached, the Alternate DNS Server is used. Page 7-182 Chapter 7: Configuration Setting up SNMP agent Domain Name The operators management domain name may be configured for DNS. The domain name configuration can be used for configuration of the servers in the operators network. The default domain name is example.com, and is only used if configured as such. Page 7-183 Chapter 7: Configuration Setting up SNMP agent Configuring SNMP The SNMP page configuration is explained below. Note The SNMP page for AP, SM, BHM and BHS has the same parameter attributes. SNMP page AP/SM/BHM/BHS The SNMP page is explained in Table 168. Table 168 SNMP page attributes Page 7-184 Chapter 7: Configuration Setting up SNMP agent Attribute SNMP Community String 1 SNMP Community String 1 Permissions SNMP Community String 2 (Read Only) Meaning Specify a control string that can allow a Network Management Station (NMS) to access SNMP information. No spaces are allowed in this string. The default string is Canopy. You can designate the SNMP Community String 1 to be the password for WM, for example, to have Read / Write access to the module via SNMP or for all SNMP access to the module to be Read Only. Specify an additional control string that can allow a Network Management Station (NMS) to read SNMP information. No spaces are allowed in this string. The default string is Canopyro. This password will never authenticate a user or an NMS to read/write access. Page 7-185 Chapter 7: Configuration Engine ID SNMPv3 Security Level SNMPv3 Authentication Protocol SNMPv3 Privacy Protocol SNMPv3 Read-Only User SNMPv3 Read/Write User Additional SNMP v3 User 1 Setting up SNMP agent The Community String value is clear text and is readable by a packet monitor. Additional security derives from the configuration of the Accessing Subnet, Trap Address, and Permission parameters. The Engine ID may be between 5 and 32 hex characters. The hex character input is driven by RFC 3411 recommendations on the Engine ID. The default Engine ID is the MAC address of the device Specify security model where users are defined and authenticated before granting access to any SNMP service. Each device can configure the security level of SNMPv3 to No authentication/No privacy, Authentication/No privacy, or Authentication/Privacy. Currently, the SNMPv3 authentication protocol MD5 is supported. Currently, the SNMPv3 privacy protocol CBC-DES is supported. This field allows for a read-only user per devices. The default values for the Read-Only users is:

Username = Canopyro Authentication Password = authCanopyro Privacy Password = privacyCanopyro Read-write user by default is disabled. The default values for the Read/Write users is :

Username = Canopy Authentication Password = authCanopy Privacy Password = privacyCanopy This field allows to configure the Additional SNMP v3 User 1. The configurations include:

Enable/Disable User: These fields allow to enable or disable the user using the Enable User or Disable User radio buttons. Authorizaton Key: This field allows to configure an authorization key for the user. Privacy Key: This field allows to configure a privacy key for the user. Note:

Set SNMP v3 Security Level field to :auth,priv to enable the Authorization Key and Privacy Key fields. Enabled User can be set with following privacy settings:

ReadWrite User ReadOnly User Page 7-186 Chapter 7: Configuration Additional SNMP v3 User 2 Additional SNMP v3 User 3 SNMPv3 Trap Configuration Accessing IP / Subnet Mask 1 to 10 Setting up SNMP agent This field allows to configure the Additional SNMP v3 User 2. The configurations include:

Enable/Disable User: These fields allow to enable or disable the user using the Enable User or Disable User radio buttons. Authorizaton Key: This field allows to configure an authorization key for the user. Privacy Key: This field allows to configure a privacy key for the user. Set SNMP v3 Security Level field to :auth,priv to enable the Authorization Key and Privacy Key fields. Enabled User can be set with following Privacy settings:

ReadWrite User ReadOnly User This field allows to configure the Additional SNMP v3 User 3. The configurations include:

Enable/Disable User: These fields allow to enable or disable the user using the Enable User or Disable User radio buttons. Authorizaton Key: This field allows to configure an authorization key for the user. Privacy Key: This field allows to configure a privacy key for the user. Set SNMP v3 Security Level field to :auth,priv to enable the Authorization Key and Privacy Key fields. Enabled User can be set with following Privacy settings:

ReadWrite User ReadOnly User When enabling transmission of SNMPv3 traps the read-only or read-write user credentials must be used and selected properly in order for the SNMP manager to correctly interpret the traps. By default transmission of SNMPv3 traps is disabled and all traps sent from the radios are in SNMPv2c format. Specify the addresses that are allowed to send SNMP requests to this AP. The NMS has an address that is among these addresses (this subnet). You must enter both The network IP address in the form xxx.xxx.xxx.xxx The CIDR (Classless Interdomain Routing) prefix length in the form /xx For example:

the /16 in 198.32.0.0/16 specifies a subnet mask of 255.255.0.0 (the first 16 bits in the address range are identical among all members of the subnet). 192.168.102.0 specifies that any device whose IP address is in the range 192.168.102.0 to 192.168.102.254 can send SNMP requests to the AP, presuming that the device supplies the correct Community String value. Page 7-187 Chapter 7: Configuration Setting up SNMP agent SNMP Trap Server DNS Usage Trap Address 1 to 10 Trap Enable, Sync Status Trap Enable, Session Status Site Information Viewable to Guest Users Site Name Site Contact Site Location The default treatment is to allow all networks access. For more information on CIDR, execute an Internet search on Classless Interdomain Routing. You are allowed to specify as many as 10 different accessing IP address, subnet mask combinations. RECOMMENDATION:

The subscriber can access the SM/BHS by changing the subscriber device to the accessing subnet. This hazard exists because the Community String and Accessing Subnet are both visible parameters. To avoid this hazard, configure the SM/BHS to filter (block) SNMP requests. The management DNS domain name may be toggled such that the name of the trap server only needs to be specified and the DNS domain name is automatically appended to that name. The default SNMP trap server addresses for all 10 available servers is 0.0.0.0 with the appending of the DNS domain name disabled. Specify ten or fewer IP addresses (xxx.xxx.xxx.xxx) or DNS names to which SNMP traps must be sent. Traps inform Wireless Manager or an NMS that something has occurred. For example, trap information is sent after a reboot of the module. when an NMS attempts to access agent information but either If the sync status traps (sync lost and sync regained) have to be sent to Wireless Manager or an NMS, select Enabled. If these traps have to be suppressed, select Disabled. supplied an inappropriate community string or SNMP version number. is associated with a subnet to which access is disallowed. If you want session status traps sent to Wireless Manager or an NMS, select Enabled. Operators can enable or disable site information from appearing when a user is in GUEST account mode. Specify a string to associate with the physical module. This parameter is written into the sysName SNMP MIB-II object and can be polled by Wireless Manager or an NMS. The buffer size for this field is 128 characters. Enter contact information for the module administrator. This parameter is written into the sysContact SNMP MIB-II object and can be polled by Wireless Manager or an NMS. The buffer size for this field is 128 characters. Enter information about the physical location of the module. This parameter is written into the sysLocation SNMP MIB-II object and can be polled by Wireless Manager or an NMS. The buffer size for this field is 128 characters. Page 7-188 Configuring syslog Chapter 7: Configuration Configuring syslog 450 Platform Family includes:

Syslog event logging Configuring system logging Page 7-189 Chapter 7: Configuration Configuring syslog Syslog event logging Following events are logged in syslog as explained in Table 169. Table 169 Syslog parameters Attribute Timestamp Configuration Changes User Login and Logout Add or Delete of user accounts through GUI and SNMP Meaning All syslog messages captured from the radio have a timestamp. This includes any device setting that has changed and includes the old or new parameter value, including the device reboots. Syslog records each user login and logout, with username. Syslog captures any user accounts that are added or deleted. Spectrum Analysis Syslog records a message every time Spectrum Analysis runs. Note Since the AP/BHM must be set to a SM/BHS for Spectrum Analysis, syslog messages are not reported from the radio until the scan is done and the radio mode is switched back to AP/BHM. Syslog records a message every time a Link Test is run. Syslog sends a message when Statistics are cleared. This is done individually for each statistics page that is cleared. Syslog records a message when a SM registers or deregisters. Syslog records a message when a BHS connects or disconnects. Link Test Clear Statistics SM Register or De-

register BHS Connect or Disconnect Configuring system logging To configure system logging, select the menu option Configuration > Syslog. Syslog page of AP/BHM The Syslog Configuration page for AP/BHM is shown in Table 170. Page 7-190 Chapter 7: Configuration Table 170 Syslog Configuration attributes - AP Configuring syslog Attribute Syslog DNS Server Usage Syslog Server Meaning To configure the AP/BHM to append or not append the DNS server name to the syslog server name. The dotted decimal or DNS name of the syslog server address. Syslog Server Port The syslog server port (default 514) to which syslog messaging is sent. AP Syslog Transmit Or BHM Syslog Transmit SM Syslog Transmit Or BHS Syslog Transmit Syslog Minimum Level When enabled, syslog messages are sent from the AP/BHM. When enabled, syslog messages are sent from all the registered SMs/BHS, unless they are individually set to override this. This provides a selection for the minimum syslog message severity that is sent to the syslog server. Values range from fatal (highest severity and least verbose) to info (lowest severity, maximum verbosity). For example: If the Syslog Minimum Level is set to notice, then only messages with severity notice and above are sent. Syslog page of SM To configure system logging, select the menu option Configuration > Syslog. The Syslog Configuration page is shown in Table 171. Page 7-191 Chapter 7: Configuration Table 171 Syslog Configuration attributes - SM Configuring syslog Attribute Syslog Configuration Source Meaning This control determines whether the SM will attempt to use the syslog server definition from the AP, or whether it will use a local server definition. When set to AP preferred, use local when AP configuration unavailable, and if the SM can register with an AP, then it uses the syslog server defined on that AP. If the SM cannot register then it will syslog to its locally defined syslog server through its wired connection, if any. When set to Local only the SM ignores the APs definition of the syslog server and allows the syslog server to be configured individually for each SM. Syslog DNS Server Usage To configure the SM to append or not the DNS server name to the syslog server name. Syslog Server Syslog Server Port Syslog Transmission Syslog Minimum Level Source The dotted decimal or DNS name of the syslog server address. The syslog server port (default 514) to which syslog messaging is sent. Controls the SMs ability to transmit syslog messages. When set to Learn from AP the AP will control whether this SM transmits syslog messages. When set to enable or disable the SM will control whether it sends syslog messages. This allows an operator to override the AP settings for individual SMs in a sector. This control determines whether the SM attempts to use the minimum syslog level defined by the AP, or whether it uses a local defined value using the Syslog Minimum Level parameter. When set to AP preferred, use local when AP configuration unavailable, and if the SM can register with an AP, then it uses the Syslog Minimum Level defined on that AP. If the SM cannot register then it uses its own Syslog Minimum Level setting. When set to Local only the SM will always use its own Syslog Minimum Level setting and ignores the APs setting. Page 7-192 Chapter 7: Configuration Syslog Minimum Level Configuring syslog This provides a selection for the minimum syslog message severity that is sent to the syslog server. Values range from fatal (highest severity and least verbose) to info (lowest severity, maximum verbosity). For example: If the Syslog Minimum Level is set to notice, then only messages with severity notice and above are sent. Syslog page of BHS The Syslog Configuration page is shown in Table 172. Table 172 Syslog Configuration attributes - BHS Attribute Syslog Configuration Source Meaning This control determines whether the BHS will attempt to use the syslog server definition from the BHM, or whether it will use a local server definition. When set to BHM preferred, use local when BHM configuration unavailable, and if the BHS can register with a BHM, then it uses the syslog server defined on that BHM. If the BHS cannot register then it will syslog to its locally defined syslog server through its wired connection, if any. When set to Local only the BHS ignores the BHMs definition of the syslog server and allows the syslog server to be configured individually for each BHS. Syslog DNS Server Usage To configure the BHS to append or not to append the DNS server name to the syslog server name. Syslog Server Syslog Server Port Syslog Transmission The dotted decimal or DNS name of the syslog server address. The syslog server port (default 514) to which syslog messaging is sent. Controls the BHSs ability to transmit syslog messages. When set to Learn from BHM the BHM will control whether this BHS transmits syslog messages. When set to enable or disable the BHS will control whether it Page 7-193 Chapter 7: Configuration Configuring syslog sends syslog messages. This allows an operator to override the BHM settings for individual BHSs in a sector. This control determines whether the BHS attempts to use the minimum syslog level defined by the BHM, or whether it uses a local defined value using the Syslog Minimum Level parameter. When set to BHM preferred, use local when BHM configuration unavailable, and if the BHS can register with a BHM, then it uses the Syslog Minimum Level defined on that BHM. If the BHS cannot register then it uses its own Syslog Minimum Level setting. When set to Local only the BHS will always use its own Syslog Minimum Level setting and ignores the BHMs setting. This provides a selection for the minimum syslog message severity that is sent to the syslog server. Values range from fatal (highest severity and least verbose) to info (lowest severity, maximum verbosity). For example: If the Syslog Minimum Level is set to notice, then only messages with severity notice and above are sent. Syslog Minimum Level Source Syslog Minimum Level Page 7-194 Chapter 7: Configuration Configuring remote access Configuring remote access Accessing SM/BHS over-the-air by Web Proxy The SM/BHS may be accessed via the AP/BHM management GUI by navigating to Home > Session Status (or Home > Remote Subscribers for AP only) and clicking on the SMs hyperlink. For example, to access one of the SMs, click LUID: 002 [0a-00-3e-37-b9-fd], as shown in Figure 147. Figure 147 AP Session Status page The SessionStatus.xml hyper link allows user to export all displayed SM data in Session Status table into an xml file. To access any one of the SMs, click 450 Platform Family - SM hyperlink, as shown in Figure 148. Figure 148 AP Remote Subscribers page Page 7-195 Chapter 7: Configuration Monitoring the Link Monitoring the Link Link monitoring procedure After configuring the link, either an operator in the network office or the SM/BHS INSTALLER user in the field (if read access to the AP/BHM is available to the INSTALLER) must perform the following procedure. Who is authorized and able to do this depends on local operator password policy, management VLAN setup and operational practices. To monitor the link for performance, follow these instructions:

Procedure 22 Monitoring the AP-SM link 1 Access the web interface of the AP/BHM 2 3 Click the Session Status tab. In the left-side menu of the AP/BHM interface, select Home. Figure 149 Session Status page 4 The Device tab of Session Status List display all displayed SMs MAC address, PMP/PTP Hardware, Software Version, FPGA Version and State Page 7-196 Chapter 7: Configuration Monitoring the Link 5 Click Session Count tab of Session Status List to display values for Session Count, Reg Count, and Re-Reg Count. Session Count: This field displays how many sessions the SM/BHS has had with the AP/BHM. Typically, this is the sum of Reg Count and Re-Reg Count. However, the result of internal calculation may display here as a value that slightly differs from the sum. Reg Count: When a SM/BHS makes a Registration Request, the AP/BHM checks its local session database to see whether it was registered earlier. If the AP/BHM concludes that the SM/BHS is not currently in session database and it is valid Registration Request, then the request increments the value of this field. Re-Reg Count: When a SM/BHS makes a Registration Request, the AP/BHM checks its local session database to see whether it was registered earlier. If the AP/BHM concludes that the SM/BHS is currently in session database, then the request increments the value of this field. Typically, a Re-Reg is the case where both o SM/BHS attempts to reregister for having lost communication with the AP/BHM. o AP/BHM has not yet observed the link to the SM/BHS as being down. See Session tab on page 9-21 6 Click Power tab of Session Status list to display Downlink Rate, AP Rx Power (dBm), Signal Strength Radio (dB) for Uplink and Signal to Noise Radio (dB) for Uplink. See Power tab on page 9-23 7 Click Configuration tab of Session Status list to get QoS configuration details:

Sustained Data Rate (kbps) Burst Allocation (kbit) Max Burst Rate (kbit) Low Priority CIR (kbps) See Configuration tab on page 9-25 8 Briefly monitor these values, occasionally refreshing this page by clicking another tab and 9 then the Session Status tab again. If these values are low (for example, 1, 1, and 0, respectively, meaning that the SM/BHS registered and started a stable session once) and are not changing:

Consider the installation successful. Monitor these values from the network office over the next several hours and days. If these values are greater than 1, 1, and 0, or they increase while you are monitoring them, troubleshoot the link. (For example, Use Receive Power Level for aiming and then use Link Tests to confirm alignment). Refer Viewing Session Status on page 9-20 for more details. Page 7-197 Chapter 7: Configuration Monitoring the Link Exporting Session Status page of AP/BHM The SessionStatus.xml hyper link allows user to export all displayed SMs or BHS data in Session Status table into an xml file. Figure 150 Exporting Session Status page of PMP 450m AP In case of PMP, if the session status page does not list any SM, the SessionStatus.xml will still be visible but the file would be empty. The file will contain data from all of the 5 different tables. Export from command line The scripts users can also get this file from command line, you have to authenticate successfully in order to download the file. Wget http://169.254.1.1/SessionStatus.xml?CanopyUsername=test&CanopyPassword=test Page 7-198 Chapter 7: Configuration Configuring quality of service Configuring quality of service Maximum Information Rate (MIR) Parameters Point-to-multipoint links use the following MIR parameters for bandwidth management:

Sustained Uplink Data Rate (kbps) Uplink Burst Allocation (kb) Sustained Downlink Data Rate (kbps) Downlink Burst Allocation (kb) Max Burst Downlink Data Rate (kbps) Max Burst Uplink Data Rate (kbps) Set each of these parameters per AP or per SM independently. Note You can refer below whitepaper for 450 Platform Family Max Burst MIR:

http://www.cambiumnetworks.com/resources/pmp-450-maxburst/

Token Bucket Algorithm The software uses a token bucket algorithm that has the following features:

Stores credits (tokens) for the SM to spend on bandwidth for reception or transmission. Drains tokens during reception or transmission. Refills with tokens at the sustained rate set by the network operator. For each token, the SM can send toward the network in the uplink (or the AP can send toward the SM in the downlink) an equivalent number of kilobits. Two buckets determine the permitted throughput: one in the SM for uplink and one in the AP for downlink. The applicable set of Uplink Burst Allocation and Downlink Burst Allocation parameters determine the number of tokens that can fill each bucket. When the SM transmits (or the AP transmits) a packet, the equivalent number of tokens is removed from the uplink (or downlink) bucket. Except when full, the bucket is continuously being refilled with tokens at rates that the applicable set of Sustained Uplink Data Rate and Sustained Downlink Data Rate parameters specify. The bucket often drains at a rate that is much faster than the sustained data rate but can refill at only the sustained data rate. Thus, the effects of the allocation and rate parameters on packet delay are as follows:

The burst allocation affects how many kilobits are processed before packet delay is imposed. The sustained data rate affects the packet delay that is imposed. Page 7-199 Chapter 7: Configuration Configuring quality of service MIR Data Entry Checking Uplink and downlink MIR is enforced as shown in Figure 151. Note In these figures, entry refers to the setting in the data rate parameter, not the burst allocation parameter. Figure 151 Uplink and downlink rate caps adjusted to apply aggregate cap uplink cap enforced =

downlink cap enforced =

uplink entry x aggregate cap for the SM uplink entry + downlink entry downlink entry x aggregate cap for the SM uplink entry + downlink entry For example, in the SM, if you set the Sustained Uplink Data Rate parameter to 2,000 kbps and the Sustained Downlink Data Rate parameter to 10,000 kbps, then the uplink and downlink MIR that is enforced for the SM can be calculated as shown in Figure 152. Figure 152 Uplink and downlink rate cap adjustment example uplink cap enforced =

2,000 kbps x 7,000 kbps 2,000 kbps + 10,000 kbps

= 1,167 kbps downlink cap enforced =

`

10,000 kbps x 7,000 kbps 2,000 kbps + 10,000 kbps

= 5,833 kbps In this example case, the derived 1,167-kbps uplink and 5,833-kbps downlink MIR sum to the fixed 7,000-

kbps aggregate cap of the SM. Committed Information Rate (CIR) The Committed Information Rate (CIR) capability feature enables the service provider to guarantee to any subscriber that bandwidth will never decrease to below a specified minimum unless CIR is oversubscribed or RF conditions are degraded. CIR is oversubscribed when there is not enough available bandwidth to support CIR configuration for all subscribers. In this condition, SMs which are configured with a nonzero CIR will all operate at the maximum data rate supported by the link (subject to Maximum Information Rate and Burst Rate/Allocations). SMs which are configured with a CIR of 0 kbps will not transmit until CIR-configured SMs have completed transmission. CIR may be configured independently for high priority traffic and for low priority traffic. CIR parameters may be configured in the following ways:

Web-based management GUI SNMP Authentication Server (RADIUS) - when an SM successfully registers and authenticates, CIR information is retrieved from the RADIUS server. Page 7-200 Chapter 7: Configuration Configuring quality of service Active CIR configuration can be verified via the APs Home > Session Status page. Bandwidth from the SM Perspective In the SM, normal web browsing, e-mail, small file transfers and short streaming video are rarely rate limited with practical bandwidth management (QoS) settings. When the SM processes large downloads such as software upgrades and long streaming video or a series of medium-size downloads, the bucket rapidly drains, the burst limit is reached, and some packets are delayed. The subscriber experience is more affected in cases where the traffic is more latency sensitive. Interaction of Burst Allocation and Sustained Data Rate Settings If the Burst Allocation is set to 1200 kb and the Sustained Data Rate is set to 128 kbps, a data burst of 1000 kb is transmitted at full speed because the Burst Allocation is set high enough. After the burst, the bucket experiences a significant refill at the Sustained Data Rate. This configuration uses the advantage of the settable Burst Allocation. If both the Burst Allocation and the Sustained Data Rate are set to 128 kb, a burst is limited to the Burst Allocation value. This configuration does not take advantage of the settable Burst Allocation. If the Burst Allocation is set to 128 kb and the Sustained Data Rate is set to 256 kbps, the actual rate is the burst allocation (but in kbps). As above, this configuration does not take advantage of the settable Burst Allocation. High-priority Bandwidth To support low-latency traffic such as VoIP (Voice over IP) or video, the system implements a high-priority channel. This channel does not affect the inherent latencies in the system but allows high-priority traffic to be immediately served. The high-priority pipe separates low-latency traffic from traffic that is latency tolerant, such as standard web traffic and file downloads. The number of channels available on the AP is reduced by the number of SMs configured for the high-

priority channel (each SM operating with high-priority enabled uses two channels (virtual circuits) instead of one). A module prioritizes traffic by reading the Low Latency bit (Bit 3) in the Ipv4 Type of Service (ToS) byte in a received packet. Bit 3 is set by a device outside the system. reading the 802.1p field of the 802.1Q header in a received packet, where VLAN is enabled on the module. comparing the 6-bit Differentiated Services Code Point (DSCP) field in the ToS byte of a received packet to a corresponding value in the Diffserv tab of the Configuration page of the module. A packet contains no flag that indicates whether the encoding is for the Low Latency bit or the DSCP field. For this reason, you must ensure that all elements in your trusted domain, including routers and endpoints, set and read the ToS byte with the same scheme. Modules monitor ToS bytes with DSCP fields, but with the following differences:

The 6-bit length of the field allows it to specify one of 64 service differentiations. These correlate to 64 individual (CodePoint) parameters in the Diffserv tab of the Configuration page. Page 7-201 Chapter 7: Configuration Configuring quality of service Per RFC 2474, 3 of these 64 are preset and cannot be changed. (See http://www.faqs.org/rfcs/rfc1902.html.) For any or all of the remaining 61 CodePoint parameters, you can specify a value of o 0 through 3 for low-priority handling. o 4 through 7 for high-priority handling. Note Ensure that your Differentiated Services domain boundary nodes mark any entering packet, as needed, so that it specifies the appropriate Code Point for that traffic and domain. This prevents theft of service level. An example of the Diffserv page in the Configuration menu and parameter descriptions are provided under DiffServ attributes AP/BHM on page 7-60. This tab and its rules are identical from module type to module type. However, any of the 61 configurable Code Points can be set to a different value from module to module, thus defining unique per-hop behavior for some traffic. This tab in the AP sets the priorities for the various packets in the downstream (sent from the public network). This tab in the SM sets the priorities for the various packets in the upstream (sent to the public network). Typically, some SMs attach to older devices that use the ToS byte as originally formatted, and others to newer devices that use the DSCP field. The default values in the Diffserv page allow your modules to prioritize traffic from the older devices roughly the same as they traditionally have. However, these default values may result in more high-priority traffic as DSCP fields from the newer devices are read and handled. So, after making changes in the Diffserv page, carefully monitor the high-priority channel for high packet rates across your network when you have broadly implemented Code Point values, such as via SNMP. in SMs that you have identified as those to initially set and watch. Page 7-202 Chapter 7: Configuration Configuring quality of service Traffic Scheduling The characteristics of traffic scheduling in a sector are summarized in Table 173. Table 173 Characteristics of traffic scheduling Category Throughput Latency Factor Aggregate throughput, less additional overhead Number of frames required for the scheduling process Round-trip latency AP broadcast the download schedule Treatment 132 Mbps 1 6 ms No High-priority Channel Allocation for uplink high-priority traffic on amount of high-priority traffic Dynamic, based on amount of high-

priority traffic Allocation for downlink high-priority traffic on amount of high-priority traffic Dynamic, based on amount of high-

priority traffic Order of transmission CIR high-priority CIR low-priority Other high-priority Other low-priority Caution Power requirements affect the recommended maximums for power cord length feeding the CMM4. See the dedicated user guide that supports the CMM that you are deploying. Packets that have a priority of 4 to 7 in either the DSCP or a VLAN 802.1p tag are automatically sent on the high-priority channel, but only where the high-priority channel is enabled. Page 7-203 Chapter 7: Configuration Configuring quality of service Setting the Configuration Source The AP includes a Configuration Source parameter, which sets where SMs that register to the AP are controlled for MIR, CIR, VLAN, and the high-priority channel as follows. The Configuration Source parameter affects the source of:

all MIR settings:

o Sustained Uplink Data Rate o Uplink Burst Allocation o Max Burst Uplink Data Rate o Sustained Downlink Data Rate o Downlink Burst Allocation o Max Burst Downlink Data Rate all CIR settings:

o Low Priority Uplink CIR o Low Priority Downlink CIR o Hi Priority Uplink CIR o Hi Priority Downlink CIR all SM VLAN settings o Dynamic Learning o Allow Only Tagged Frames o VLAN Aging Timeout o Untagged Ingress VID o Management VID o VLAN Membership the Hi Priority Channel setting Table 174 Recommended combined settings for typical operations Most operators who use in this web page/tab must set this parameter Authentication Mode Configuration/ Security Configuration Source Configuration/ General Authentication Mode Configuration/ Security Configuration Source Configuration/ General Authentication Mode Configuration/ Security Configuration Source Configuration/ General in the AP to Disabled SM Authentication Server Authentication Server RADIUS AAA Authentication Server no authentication server Wireless Manager

(Authentication Server) RADIUS AAA server Table 175 Where feature values are obtained for a SM with authentication required Values are obtained from Page 7-204 Chapter 7: Configuration Configuring quality of service Configuration Source Setting in the AP Authentication Server SM Authentication Server+SM MIR Values VLAN Values High Priority Channel State Authentication Server Authentication Server Authentication Server SM SM SM Authentication Server Authentication Server, then SM Authentication Server, then SM Note HPC represents the Hi Priority Channel (enable or disable). Where Authentication Server, then SM is the indication, parameters for which Authentication Server does not send values are obtained from the SM. This is the case where the Authentication Server is operating on an Authentication Server release that did not support the feature. This is also the case where the feature enable/disable flag in Authentication Server is set to disabled. The values are those previously set or, if none ever were, then the default values. Where Authentication Server is the indication, values in the SM are disregarded. Where SM is the indication, values that Authentication Server sends for the SM are disregarded. For any SM whose Authentication Mode parameter is not set to Authentication Required, the listed settings are derived as shown in Table 176. Table 176 MIR, VLAN, HPC, and CIR Configuration Sources, Authentication Disabled Configuration Source Setting in the AP Values are obtained from VLAN Values MIR Values CIR Values High Priority Channel State AP SM SM AP SM SM Authentication Server SM Authentication Server+SM AP SM SM AP SM SM Page 7-205 Chapter 7: Configuration Configuring quality of service Configuring Quality of Service (QoS) Quality of Service (QoS) page of AP The QoS page of AP is explained in Table 177. Table 177 QoS page attributes - AP Attribute Max Burst Uplink Data Rate Sustained Uplink Data Rate Uplink Burst Allocation Max Burst Downlink Data Rate Meaning These parameters allow operators to specify the data rate at which a SM is allowed to transmit (until burst allocation limit is reached) before being recharged at the Sustained Uplink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. Specify the rate that each SM registered to this AP is replenished with credits for transmission. This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on page 7-198 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-200 Configuration Source on page 7-69 Specify the maximum amount of data to allow each SM to transmit before being recharged at the Sustained Uplink Data Rate with credits to transmit more. See Maximum Information Rate (MIR) Parameters on page 7-198 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-200 Configuration Source on page 7-69 These parameters allow operators to specify the data rate at which a SM is allowed to transmit (until burst allocation limit is reached) before being recharged at the Sustained Downlink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. Page 7-206 Chapter 7: Configuration Sustained Downlink Data Rate Downlink Burst Allocation Broadcast Downlink CIR Priority Precedence PPPoE Control Message Priority Prioritize TCP ACK Configuring quality of service Specify the rate at which the AP is replenished with credits (tokens) for transmission to each of the SMs in its sector. This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on page 7-198 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-200 Configuration Source on page 7-69 Specify the maximum amount of data to allow the AP to transmit to any registered SM before the AP is replenished with transmission credits at the Sustained Downlink Data Rate. See Maximum Information Rate (MIR) Parameters on page 7-198 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-200 Configuration Source on page 7-69 Broadcast Downlink CIR (Committed Information Rate, a minimum) supports system designs where downlink broadcast is desired to have higher priority than other traffic. For many other system designs, especially typical internet access networks, leave the Broadcast Downlink CIR at the default. Broadcast Downlink CIR is closely related to the Broadcast Repeat Count parameter, which is settable in the Radio tab of the Configuration page in the AP: when the Broadcast Repeat Count is changed, the total of available bandwidth is also changed, since packets are being sent one, two, or three times, according to the setting in the Broadcast Repeat Count parameter. Allows operator to decide if 802.1p or DiffServ priority bits must be used first when making priority decisions. Operators may configure the SM to utilize the high priority channel for PPPoE control messages. Configuring the SM in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the SM. To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. Quality of Service (QoS) page of SM The QoS page of SM is explained in Table 178. Page 7-207 Chapter 7: Configuration Table 178 QoS page attributes - SM Configuring quality of service Attribute Sustained Uplink Data Rate Sustained Downlink Data Rate Uplink Burst Allocation Meaning Specify the rate that this SM is replenished with credits for transmission. This default imposes no restriction on the uplink. See Maximum Information Rate

(MIR) Parameters on page 7-198 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-200 Configuration Source on page 7-69 Specify the rate at which the AP is replenished with credits (tokens) for transmission to this SM. This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on Page 7-198 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-200 Configuration Source on page 7-69 Specify the maximum amount of data to allow this SM to transmit before being recharged at the Sustained Uplink Data Rate with credits to transmit more. See Maximum Information Rate (MIR) Parameters on page 7-198 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-200 Configuration Source on page 7-69 Page 7-208 Chapter 7: Configuration Configuring quality of service Downlink Burst Allocation Max Burst Uplink Data Rate Max Burst Downlink Data Rate Enable Broadcast /

Multicast Data Rate Broadcast / Multicast Data Rate Low Priority Uplink CIR Low Priority Downlink CIR Hi Priority Channel Hi Priority Uplink CIR Hi Priority Downlink CIR Specify the maximum amount of data to allow the AP to transmit to this SM before the AP is replenished at the Sustained Downlink Data Rate with transmission credits. See Maximum Information Rate (MIR) Parameters on page 7-198 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-200 Committed Information Rate (CIR) on page 7-199 Configuration Source on page 7-69 These parameters allow operators to specify the data rate at which a SM is allowed to transmit (until burst allocation limit is reached) before being recharged at the Sustained Uplink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. These parameters allow operators to specify the data rate at which a SM is allowed to transmit (until burst allocation limit is reached) before being recharged at the Sustained Downlink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. This parameter allows the operator to specify if Broadcast and Multicast data is rate-limited. This data rate can be entered in Kbps or PPS (Packets Per Second). This parameter allows the operator to specify a data rate at which Broadcast and Multicast traffic is sent via the radio link. This field indicates the minimum rate at which low priority traffic is sent over the uplink (unless CIR is oversubscribed or RF link quality is degraded). Setting the Configuration Source on page 7-203 This field indicates the minimum rate at which low priority traffic is sent over the downlink (unless CIR is oversubscribed or RF link quality is degraded). Committed Information Rate (CIR) on page 7-199 Setting the Configuration Source on page 7-203 See High-priority Bandwidth on page 7-200 Configuration Source on page 7-69 This field indicates the minimum rate at which high priority traffic is sent over the uplink (unless CIR is oversubscribed or RF link quality is degraded). Committed Information Rate (CIR) on page 7-199 Setting the Configuration Source on page 7-203 This field indicates the minimum rate at which high priority traffic is sent over the downlink (unless CIR is oversubscribed or RF link quality is degraded). Committed Information Rate (CIR) on page 7-199 Setting the Configuration Source on page 7-203 Page 7-209 Chapter 7: Configuration Priority Precedence PPPoE Control Message Priority Prioritize TCP ACK Configuring quality of service Allows operator to decide if 802.1p or DiffServ priority bits must be used first when making priority decisions. Operators may configure the SM to utilize the high priority channel for PPPoE control messages. Configuring the SM in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the SM. To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. This parameter, when enabled, can be particularly useful when running bi-direction FTP sessions over the link. If a link is primarily used for video surveillance, it is recommended to configure this parameter to Disabled. Quality of Service (QoS) page of BHM The QoS page of BHM is explained in Table 179. Table 179 QoS page attributes - BHM Attribute PPPoE Control Message Priority Prioritize TCP ACK Meaning Operators may configure the BHM to utilize the high priority channel for PPPoE control messages. Configuring the BHM in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the BHS. To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. This parameter, when enabled, can be particularly useful when running bi-direction FTP sessions over the link. If a link is primarily used for video surveillance, it is recommended to configure this parameter to Disabled. Quality of Service (QoS) page of BHS The QoS page of BHS is explained in Table 180. Page 7-210 Chapter 7: Configuration Table 180 QoS page attributes - BHS Configuring quality of service Attribute PPPoE Control Message Priority Prioritize TCP ACK Meaning Operators may configure the BHS to utilize the high priority channel for PPPoE control messages. Configuring the BHS in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the BHS. To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. This parameter, when enabled, can be particularly useful when running bi-direction FTP sessions over the link. If a link is primarily used for video surveillance, it is recommended to configure this parameter to Disabled. Page 7-211 Chapter 7: Configuration Installation Color Code Installation Color Code With this feature enabled on the AP and SM, operators may install and remotely configure SMs without having to configure matching color codes between the modules. While the SM is accessible for configuration from above the AP (for remote provisioning) and below the SM (for local site provisioning), no user data is passed over the radio link. When using the Installation Color Code feature, ensure that the SM is configured with the factory default Color Code configuration (Color Code 1 is 0, Color Code 2-10 set to 0 and Disable). The status of the Installation Color Code can be viewed on the AP Eval web GUI page, and when the SM is registered using the Installation Color Code the message SM is registered via ICC Bridging Disabled! is displayed in red on every SM GUI page. The Installation Color Code parameter is configurable without a radio reboot for both the AP and SM. If an SM is registered via Installation Color Code and the feature is then disabled, operators will need to reboot the SM or force it to reregister (i.e. using the Rescan APs functionality on the AP Eval page). Figure 153 Installation Color Code of AP Page 7-212 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66 Zero Touch Configuration Using DHCP Option 66 This feature allows an SM to get its configuration via DHCP option 66. This can be used for the initial configuration of an SM as well as managing the configuration of SMs on an ongoing basis. Here is how it works in brief:

When the SM boots up, if it is set to use DHCP client, it will send out a DHCP Discover packet which includes a request for DHCP Option 66. In case of a brand new SM out of the box, the DHCP Discover packet is sent out if the SM connects to an AP using Installation Color Code (ICC), even though DHCP client is not enabled in factory default config. An appropriately configured DHCP server will respond with a DHCP Offer and include a URL in response to the Option 66 request. The URL should point to the configuration file. The device will download the configuration file and apply it. The device will reboot automatically if needed. (Note: this requires rebootIfRequired flag to be added to the config file. See Creating a Golden config file on page 7-213. Configuration Steps Procedure 23 Zero Touch Configuration steps 1 Create the golden config file(s) 2 Host it on an TFTP/FTP/HTTP/HTTPS server 3 Configure the DHCP server to return the URL of the golden config file in option 66 When the SM boots up, it will get the URL for the golden config from the DHCP server via option 66, download it and apply it. If all the SMs are configured exactly the same, then you can create just new golden config file that can be used with all SMs. If the SMs are not configured the same, see if it is possible to group the SMs such that SMs with the same configuration are served by the same DHCP pool. User can then create multiple golden config files and configure the DHCP server to use the appropriate config file for each pool. User can also create one config file per SM. This provides the most flexibility, but is practical only if you have a software tool/script to generate the config files for each MAC address. The files should be named

<mac>.cfg where <mac> is the MAC address of the SM, and stored in the same directory on the file server. The DHCP server should be configured to return the directory name ending with a / in option 66. The SM will automatically add <mac>.cfg to the path and get its config file. Page 7-213 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66 If some configuration is unique per SM, but rest of the configuration is common, the SMs can be staged with the unique part, and use option 66 to manage the common part. For example, if each SM needs to have its coordinates set, dont include the coordinates in the golden config file. Instead, configure the coordinates for each SM manually. Manage the rest of the configuration using DHCP option 66. Creating a Golden config file The easiest way to create the golden config file is to configure an SM, export its configuration and edit it. To export the configuration file from the GUI of the SM, go to Configuration > Unit Settings tab, go to the Download Configuration File section and click on the <mac>.cfg link. This will give you a text file in JSON format. You can edit this file in a text editor but its easier to use a JSON editor like https://www.jsoneditoronline.org/. Strip down the config file to remove sections and entries that dont care about, and keep only the items that require changes. If there are many required changes, it can easily get confusing. To identify the exact items changes, first reset the SM to factory default, export the config file, make the necessary changes, export a second config file, then use a tool like WinMerge (http://winmerge.org/) to identify the differences. The config file contains the following informational entries at the top level. cfgUtcTimestamp: cfgUtcTimestamp, swVersion: CANOPY 15.1 SM-AES, cfgFileString: Canopy configuration file, srcMacAddress: 0a-00-3e-a2-c2-74, deviceType: 5.4/5.7GHz MIMO OFDM - Subscriber Module, cfgFileVersion: 1.0 The cfgUtcTimestamp, swVersion, srcMacAddress and deviceType lines can be deleted. Do not delete the cfgFileString and cfgFileVersion entries. Next, create an object named configFileParameters at the top level. Under that, add a parameter called rebootIfRequired and set it to true. This tells the SM to reboot automatically if a reboot is needed to apply the new configuration. A sample configuration file that has been edited for use via DHCP option 66 is given below.

{

userParameters: {

smNetworkConfig: {

networkAccess: 1

}, location: {

siteName: Test site

}, smRadioConfig: {

frequencyScanList: [

Page 7-214 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66 5475000, 5480000

], colorCodeList: [

{

colorCode: 42, priority: 1

}

]

}, networkConfig: {

lanDhcpState: 1

}

}, cfgFileVersion: 1.0, cfgFileString: Canopy configuration file, configFileParameters: {

rebootIfRequired: true

}

}

When configuration is imported, only the items that exist in the configuration file are modified. Parameters that are not in the imported file are not changed. If user wish to revert those settings to their factory default values, please add a setToDefaults item under configFileParameters section with a value of true. cfgFileVersion: 1.0, cfgFileString: Canopy configuration file, configFileParameters: {

rebootIfRequired: true, setToDefaults: true

}

In case, the SM needs to fetch the configuration file on each boot up even when not connecting to AP via ICC, set Network Accessibility to Public and DHCP State to Enabled in the Configuration > IP page before exporting the configuration. Hosting the config file Copy the golden configuration file to an FTP, TFTP, HTTP or HTTPS server. This location can be password protected; you just have to include the user name and password in the URL. DHCP server configuration Configure DHCP server to return the full URL to the golden config file as the value of DHCP option 66. The following example explains how to make the change for Windows Server 2008. Adapt it to your specific DHCP server. Page 7-215 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66 Procedure 24 DHCP server configuration 1 Click Start > Administrative Tools > DHCP 2 If you have multiple Scopes defined, identify the correct Scope that will serve IP addresses for the SMs 3 Right click on Scope Option under the correct Scope and select Configure Options Page 7-216 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66 4 In the Scope Options dialog, scroll down to 066 Boot Server Host Name, select the checkbox and enter the full URL to the golden config file as the String value. Then click OK. 5 In the DHCP snap-in window, right click and Refresh to see the DHCP option 66 in the list of DHCP options ftp://10.120.163.253/canopy.cfg ftp://admin:admin123@10.120.163.253/canopy.cfg (login as admin with password admin123) tftp://10.120.163.253/canopy.cfg Supported URL Formats FTP, TFTP, HTTP and HTTPS URLs are supported. Some examples are given below. http://10.120.163.253/golden-config.cfg https://10.120.163.253/smconfig/golden-config.cfg User can also specify the URL pointing to a directory and not a specific file. Terminate the URL with a /

to indicate that it is a directory and not a file. Use this format when each SM has its own individual config file. The directory should contain files named <mac>.cfg, one for each SM. For example:

ftp://10.120.163.253/smconfig/

In this case, the SM will append <mac>.cfg to the path and try to get that file. For example, if the SMs MAC address is 0a-00-3e-a2-c2-74, it will request for ftp://10.120.163.253/smconfig/0a003ea2c274.cfg. This mechanism can be used to serve individual config file for each SM. Page 7-217 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66 Troubleshooting 1 Ensure that the___14 SM is running 13.3 or newer version of software. 2 If the SM has factory default config, confirm ICC is enabled on the AP, so the SM can connect to it. If the SM is connecting to the AP using a color code other than ICC, make sure the SM has Network Accessibility set to Public and DHCP State set to Enabled in the Configuration > IP page. 3 4 Make sure the golden config file does not turn off Network Accessibility or DHCP State. If it does, the SM will no longer request the config file when it is rebooted. 5 Check the event log of the SM to see the status of the configuration file import including any errors that prevented it from importing the file. 6 Capture the DHCP Offer packet from the DHCP server to the SM and verify that Option 66 has the expected URL. Page 7-218 Chapter 7: Configuration Configuring Radio via config file Configuring Radio via config file The 450 Platform Family supports export and import of a configuration file from the AP or SM as a text file. The configuration file is in JSON format. To export or import the configuration file, the logged in user needs to be an ADMINISTRATOR and it must not be a read-only account. The exported configuration file contains the complete configuration including all the default values. To keep a backup of the current configuration, the file can be saved as-is and imported later. While importing a configuration file, it can be either imported the full configuration or a sparse configuration containing only the items that need to be changed. If a sparse configuration file is imported, only the items in the file will be imported. Other configuration will remain unchanged. There could also be used a special flag in the configuration file to tell the device to apply the configuration starting from factory default (Refer Special Headers for configuration file on page 7-219). Import and Export of config file The config file import and export is supported in Configuration > Unit Settings page. The procedure for importing and exporting config file is explained below. Figure 154 Configuration File upload and download page The DHCP server configuration procedure is as follows:

Procedure 25 DHCP server configuration 1 Login to the GUI and go to Configuration > Unit Settings. 2 Under Download Configuration File tab, click on the <mac>.cfg link, where <mac> is the MAC address of the device (for example, 01003ea2c274.cfg). 3 Save the file to the local disk. The below procedure is to be followed for Importing a config file Procedure 26 Import the configuration from the GUI 1 Login to the GUI and go to Configuration Unit Settings. Page 7-219 Chapter 7: Configuration Configuring Radio via config file 2 Click on Browse button under Upload and Apply Configuration File tab and select the configuration file from disk. 3 Click Upload followed by Apply Configuration File button click. 4 The Status of Configuration File section will show the results of the upload. 5 Review it to make sure there are no errors. Then click on Reboot to reboot with the imported configuration The special headers for config file is explained below:

Procedure 27 Special Headers for configuration file 1 A configFileParameters section can be added to the header to control the behavior of the device when importing configuration. 2 The setToDefaults when set to true tell the device to reset to factory default configuration and apply the configuration in the file on top of that. So any attribute not in the configuration file will be set to its factory default value. By default, the configuration in the file is merged with the existing configuration on the device. The rebootIfRequired flag when set to true tell the device to reboot automatically if needed to apply the configuration change. By default, the device will not reboot automatically.

{

cfgFileString: Canopy configuration file, cfgFileVersion: 1.0, configFileParameters: {

setToDefaults:true, rebootIfRequired:true,

}

}

Page 7-220 Chapter 7: Configuration Configuring cnMaestroTM Connectivity Configuring cnMaestroTM Connectivity 450 Platform Family network can be onboarded, configured and managed using cnMaestro Cloud or On Premises Server. Onboarding Onboarding can be done in one of several ways:

Using Cambium ID and Onboarding key Using Manufacturers Serial Number (Only if it starts with an M and is 12 characters long) On Premises Zero Touch onboarding of AP/SM using DHCP option 43 and 15 PMP SM Zero touch onboarding to the cnMaestro server where PMP AP is onboarded. To configure the PMP devices, enable Remote Management under Configuration->cnMaestro as shown in Table 181. Table 181 Configuring cnMaestro Attribute Remote Management cnMaestro URL Meaning This field enables/disables remote management of 450 Platform Family products. This field allows to enter cnMaestro URL e.g. https://cloud.cambiumnetworks.com Or cnMaestro on premises URL Connection Status Cambium ID This field indicates cnMaestro connectivity status. This field allows to enter Cambium ID for onboarding 450 Platform devices. Onboarding Key AccountID Device Agent Version This field allows to enter Onboarding Key for onboarding. This field indicates Account ID of the customer. This field shows device agent version. Page 7-221 Chapter 7: Configuration Configuring cnMaestroTM Connectivity Prerequisites for onboarding to cnMaestro Devices types must be PMP 450m Series, PMP/PTP 450 Series, PMP/PTP 450i/450b Series or PMP 430 Series SMs (interoperability mode only). Minimum required software version of 14.2.1. Device software images can be downloaded from http://support.cambiumnetworks.com or from the On Premises cnMaestro server by navigating to Operate >Software Update->Manage Images. Select Device type to display the available images and then click the download icon as shown in Figure 155. Figure 155 Software Upgrade from cnMaestro IP connectivity between PMP Device and the cnMaestro server is established. Ensure Port 443 is open in the firewall as this port is used for secure communication between the PMP device and the cnMaestro server through web sockets. In addition, if the PMP device and cnMaestro server are on different subnets, proper routes should be established for communication. For PMP AP, a valid DNS setting is required so that the AP will be able to resolve the cnMaestro URL. DNS settings can be verified by performing a DNS lookup under Tools->DNS Test on the AP as shown in Figure 156. Page 7-222 Chapter 7: Configuration Configuring cnMaestroTM Connectivity Figure 156 DNS Test for cnMaestro connectivity If the SM is in Bridge mode, then LAN1 must have public 7-223equest7-223ility with a public IP assigned and corresponding DNS setting. If the SM is in NAT mode, then Remote Management should be enabled with the standalone configuration option and DNS settings. Knowledge Based articles for onboarding For onboarding the devices to cloud server and troubleshooting the onboarding issues in cloud server please see the following link:

http://community.cambiumnetworks.com/t5/cnMaestro/Device-On-boarding/td-p/51484 For onboarding the devices to on Premises server and configuring the DHCP server options for on boarding please see the following link:

http://community.cambiumnetworks.com/t5/cnMaestro/Device-Onboarding-and-Linux-DHCP-Options-for-

cnMaestro-On/m-p/55187#U55187 Order of Device Onboarding The device discovery order is as follows in On Permises cnMaestro Server. If any of the options is not configured, the discovery method will fallback to the next option:

1. Static cnMaestro URL 2. Zero Touch token (on boarding of PMP SMs when the corresponding AP is on boarded) 3. DHCP Option 43 4. DHCP Option 15 5. https://cloud.cambiumnetworks.com Page 7-223 Chapter 7: Configuration Configuring cnMaestroTM Connectivity Device Agent Logs For debugging any onboarding issues please check the device agent logs by navigating to Logs->Device Agent Logs on the PMP device GUI as shown in Figure 157. In addition, a tech support dump can for the PMP device can be obtained from cnMaestro by navigating to Monitor->Tools menu after selecting the particular PMP device in the tree and clicking the tech support file icon. This can be send to Cambium support for further troubleshooting. Figure 157 Device Agent Logs Monitoring Tools for PMP Devices on cnMaestro cnMaestro as of this release offers several debugging tools for PMP devices. Some examples are:

Pictorial view of network hierarchy Device status Tech support file Throughput Alarms Reboot Debug Logs Network connectivity ping and DNS lookup Page 7-224 Chapter 7: Configuration Configuring cnMaestroTM Connectivity Figure 158 Example cnMaestro screenshot For more information on these tools please see http://community.cambiumnetworks.com/t5/cnMaestro/How-to-use-the-cnMaestro-Tools-for-

Troubleshooting-Device-or/m-p/54503#U54503 Zero Touch on boarding of the PMP SMs when the corresponding AP is on boarded First a link should be established between the PMP AP and SM either by configuring manually or using the ICC. Once the AP and SM link is established, the AP must be onboarded to cnMaestro using one of several ways detailed above under the Onboarding section. Once the AP is onboarded to cnMaestro Cloud or On premises cnMaestroserver, the SMs under the AP will automatically onboard to cnMaestro using a Zero touch token that is communicated between the AP and SMs. This is applicable to existing SMs registered to the AP as well as new SMs registering to the AP for the first time. The SMs appear on the onboarding queue of cnMaestro and the operator must Approve the devices in order to manage them. The following operations for PMP Devices are available on cnMaestro Monitor the device details in the Dashboard page by navigating to the Monitor >Dashboard menu and selecting the PMP AP/SM in the tree. Monitor notifications related to the PMP AP/SM by navigating to the Monitor >Notifications Menu and selecting the PMP AP/SM in the tree. Monitor device statistics on the statistics page by navigating to the Monitor >Statistics menu and selecting the PMP AP/SM in the tree, then selecting the PMP AP or PMP SM in the Device type dropdown. Monitor Performance graphs related to the PMP AP/SM by navigating to the Monitor >Performance menu and selecting the required performance graph (i.e Throughput, SMs, Modulation) and selecting the PMP AP/SM in the tree. Troubleshoot the device on the Troubleshooting page by navigating to the Monitor >Tools menu and selecting the PMP AP/SM in the tree. Page 7-225 Chapter 7: Configuration Configuring cnMaestroTM Connectivity Configure the devices by navigating to the Configure >Devices menu and selecting the PMP AP/SM in the tree and selecting the config template that needs to be pushed to the device. Configuration templates need to be created before the configuration can be pushed to the device. The template can be created by copying the existing configuration from the view device configuration link provided in the same page and then modifying the template as needed and then pushing to the same device or other similar devices. Template needs to be properly reviewed for IP Address and other critical parameters to avoid stranding SMs (resulting in a truck roll) by pushing an incorrect configuration. Configuration templates can be created by navigating to the Configure->Templates page and selecting the PMP device type while creating the template. Once on 14.2.1, PMP devices can be upgraded to future supported versions from cnMaestro by navigating to the Operate > Software Update page and selecting the PMP Sectors option from the device type drop down and the version to which the device needs to be upgraded. It is recommended to upgrade the AP first, then the SMs. PMP Device Inventory details can be reviewed by navigating to the Monitor >Inventory page. Page 7-226 Chapter 7: Configuration Configuring a RADIUS server Configuring a RADIUS server Configuring a RADIUS server in a PMP 450 Platform network is optional, but can provide added security, increase ease of network management and provide usage-based billing data. Understanding RADIUS for PMP 450 Platform Family PMP 450 Platform modules include support for the RADIUS (Remote Authentication Dial In User Service) protocol supporting Authentication and Accounting. RADIUS Functions RADIUS protocol support provides the following functions:

SM Authentication allows only known SMs onto the network (blocking rogue SMs), and can be configured to ensure SMs are connecting to a known network (preventing SMs from connecting to rogue APs). RADIUS authentication is used for SMs, but is not used for APs. SM Configuration: Configures authenticated SMs with MIR (Maximum Information Rate), CIR

(Committed Information Rate), High Priority, and VLAN (Virtual LAN) parameters from the RADIUS server when a SM registers to an AP. User Authentication allows users to configure a separate User authentication server along with the SM authentication server. If firmware is upgraded while using this functionality and no User authentication servers are configured, then AP continues to use the SM authentication server for User authentication SM Accounting provides support for RADIUS accounting messages for usage-based billing. This accounting includes indications for subscriber session establishment, subscriber session disconnection, and bandwidth usage per session for each SM that connects to the AP. Centralized AP and SM user name and password management allows AP and SM usernames and access levels (Administrator, Installer, Technician) to be centrally administered in the RADIUS server instead of on each radio and tracks access events (logon/logoff) for each username on the RADIUS server. This accounting does not track and report specific configuration actions performed on radios or pull statistics such as bit counts from the radios. Such functions require an Element Management System (EMS) such as Cambium Networks Wireless Manager. This accounting is not the ability to perform accounting functions on the subscriber/end user/customer account. Framed IP allows operators to use a RADIUS server to assign management IP addressing to SM modules (framed IP address). Tested RADIUS Servers The Canopy RADIUS implementation has been tested and is supported on FreeRADIUS, Version 2.1.8 Aradial RADIUS, Version 5.1.12 Microsoft RADIUS (Windows Server 2012 R2 version) Cisco ACS, Version 5.7.0.15 Page 7-227 Chapter 7: Configuration Configuring a RADIUS server Note Aradial 5.3 has a bug that prevents remote device login, so doesnt support the user name and password management feature. Choosing Authentication Mode and Configuring for Authentication Servers - AP On the APs Configuration > Security tab, select the RADIUS AAA Authentication Mode. The following describes the other Authentication Mode options for reference, and then the RADIUS AAA option. Disabled: Requires no authentication. Any SM (except a SM that itself has been configured to require RADIUS authentication by enabling Enforce Authentication as described below) is allowed to register to the AP. Authentication Server: Authentication Server in this instance refers to Wireless Manager in BAM-

only mode. Authentication is required for a SM to register to the AP. Only SMs listed by MAC address in the Wireless Manager database is allowed to register to the AP. AP Pre-Shared Key: Canopy offers a pre-shared key authentication option. In this case, an identical key must be entered in the Authentication Key field on the APs Configuration > Security tab and in the Authentication Key field on each desired SMs Configuration > Security tab. RADIUS AAA: To support RADIUS authentication of SMs, on the APs Configuration > Security tab select RADIUS AAA. Only properly configured SMs with a valid certificate is allowed to register to the AP. When RADIUS AAA is selected, up to 3 Authentication Server (RADIUS Server) IP addresses and Shared Secrets can be configured. The IP address(s) configured here must match the IP address(s) of the RADIUS server(s). The shared secret(s) configured here must match the shared secret(s) configured in the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not splitting the database. If Server 1 doesnt respond, Server 2 is tried, and then server 3. If Server 1 rejects authentication, the SM is denied entry to the network, and does not progress trying the other servers. The default IP address is 0.0.0.0. The default Shared Secret is CanopySharedSecret. The Shared Secret can be up to 32 ASCII characters (no diacritical marks or ligatures, for example). Page 7-228 Chapter 7: Configuration Table 182 Security tab attributes Configuring a RADIUS server Page 7-229 Chapter 7: Configuration Attribute Authentication Mode Authentication Server DNS Usage Authentication Server 1 Authentication Server 2 Authentication Server 3 Authentication Server 4 (BAM Only) Authentication Server 5 (BAM Only) Radius Port Authentication Key Configuring a RADIUS server Meaning Operators may use this field to select the following authentication modes:

Disabledthe AP requires no SMs to authenticate. Authentication Server the AP requires any SM that attempts registration to be authenticated in Wireless Manager before registration. AP PreShared Key - The AP acts as the authentication server to its SMs and will make use of a user-configurable pre-shared authentication key. The operator enters this key on both the AP and all SMs desired to register to that AP. There is also an option of leaving the AP and SMs at their default setting of using the Default Key. Due to the nature of the authentication operation, if you want to set a specific authentication key, then you MUST configure the key on all of the SMs and reboot them BEFORE enabling the key and option on the AP. Otherwise, if you configure the AP first, none of the SMs is able to register. RADIUS AAA - When RADIUS AAA is selected, up to 3 Authentication Server (RADIUS Server) IP addresses and Shared Secrets can be configured. The IP address(s) configured here must match the IP address(s) of the RADIUS server(s). The shared secret(s) configured here must match the shared secret(s) configured in the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not for splitting the database. If Server 1 doesnt respond, Server 2 is tried, and then server 3. If Server 1 rejects authentication, the SM is denied entry to the network and does not progress trying the other servers. The management DNS domain name may be toggled such that the name of the authentication server only needs to be specified and the DNS domain name is automatically appended to that name. Enter the IP address or server name of the authentication server (RADIUS or WM) and the Shared Secret configured in the authentication server. When Authentication Mode RADIUS AAA is selected, the default value of Shared Secret is CanopySharedSecret. The Shared Secret may consist of up to 32 ASCII characters. This field allows the operator to configure a custom port for RADIUS server communication. The default value is 1812. The authentication key is a 32-character hexadecimal string used when Authentication Mode is set to AP Pre-Shared Key. By default, this key is set to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF. Selection Key This option allows operators to choose which authentication key is used:

Page 7-230 Chapter 7: Configuration Encryption Key SM Display of AP Evaluation Data Web, Telnet, FTP Session Timeout IP Access Control Allowed Source IP 1 Allowed Source IP 2 Allowed Source IP 3 Web Access SNMP Configuring a RADIUS server Use Key above means that the key specified in Authentication Key is used for authentication Use Default Key means that a default key (based off of the SMs MAC address) is used for authentication Specify the type of airlink security to apply to this AP. The encryption setting must match the encryption setting of the SMs. None provides no encryption on the air link. DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. You can use this field to suppress the display of data about this AP on the AP Evaluation tab of the Tools page in all SMs that register. Enter the expiry in seconds for remote management sessions via HTTP, telnet, or ftp access to the AP. You can permit access to the AP from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address If you selected IP Access Filtering Enabled for the IP Access Control parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the AP from any IP address. You may populate as many as all three. If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. The Radio supports secured and non-secured web access protocols. Select suitable web access from drop down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https1://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. This option allows to configure SNMP agent communication version. It can be selected from drop down list :

SNMPv2c Only Enables SNMP v2 community protocol. Page 7-231 Chapter 7: Configuration Configuring a RADIUS server Telnet FTP TFTP SNMPv3 Only Enables SNMP v3 protocol. It is secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. Page 7-232 Chapter 7: Configuration Configuring a RADIUS server SM Authentication Mode Require RADIUS or Follow AP If it is desired that a SM will only authenticate to an AP that is using RADIUS, on the SMs Configuration Security tab set Enforce Authentication to AAA. With this enabled, SM does not register to an AP that has any Authentication Mode other than RADIUS AAA selected. If it is desired that a SM use the authentication method configured on the AP it is registering to, set Enforce Authentication to Disabled. With Enforce Authentication disabled, a SM will attempt to register using whichever Authentication Mode is configured on the AP it is attempting to register to. Note Having SMs to use RADIUS by enabling Enforce Authentication avoids the security issue of SMs possibly registering to rogue APs, which have authentication disabled. Table 183 SM Security tab attributes Page 7-233 Chapter 7: Configuration Configuring a RADIUS server Attribute Authentication Key Select Key Enforce Authentication Phase 1 Phase 2 Meaning The authentication key is a 32-character hexadecimal string used when Authentication Mode is set to AP PreShared Key. By default, this key is set to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF. This option allows operators to choose which authentication key is used:

Use Key above means that the key specified in Authentication Key is used for authentication Use Default Key means that a default key (based off of the SMs MAC address) is used for authentication The SM may enforce authentication types of AAA and AP Pre-sharedKey. The SM will not finish the registration process if the AP is not using the configured authentication method (and the SM locks out the AP for 15 minutes). Enforce Authentication default setting is Disable. The protocols supported for the Phase 1 (Outside Identity) phase of authentication are EAPTTLS (Extensible Authentication Protocol Tunneled Transport Layer Security) or MSCHAPv2 (Microsoft Challenge-Handshake Authentication Protocol version 2). Select the desired Phase 2 (Inside Identity) authentication protocol from the Phase 2 options of PAP (Password Authentication Protocol), CHAP

(Challenge Handshake Authentication Protocol), and MSCHAP (Microsofts version of CHAP, version 2 is used). The protocol must be consistent with the authentication protocol configured on the RADIUS server. Page 7-234 Chapter 7: Configuration Configuring a RADIUS server Identity/Realm Username Password Confirm Password Upload Certificate File If Realms are being used, select Enable Realm and configure an outer identity in the Identity field and a Realm in the Realm field. These must match the Phase 1/Outer Identity and Realm configured in the RADIUS server. The default Identity is anonymous. The Identity can be up to 128 non-special (no diacritical markings) alphanumeric characters. The default Realm is canopy.net. The Realm can also be up to 128 non-special alphanumeric characters. Configure an outer Identity in the Username field. This must match the Phase 1/Outer Identity username configured in the RADIUS server. The default Phase 1/Outer Identity Username is anonymous. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. Enter a Username for the SM. This must match the username configured for the SM on the RADIUS server. The default Username is the SMs MAC address. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. Enter the desired password for the SM in the Password and Confirm Password fields. The Password must match the password configured for the SM on the RADIUS server. The default Password is password. The Password can be up to 128 non-special (no diacritical markings) alphanumeric characters. To upload a certificate manually to a SM, first load it in a known place on your PC or network drive, then click on a Delete button on one of the Certificate description blocks to delete a certificate to provide space for your certificate. Click on Choose File, browse to the location of the certificate, and click the Import Certificate button, and then reboot the radio to use the new certificate. When a certificate is in use, after the SM successfully registers to an AP, an indication of In Use will appear in the description block of the certificate being used. The public certificates installed on the SMs are used with the private certificate on the RADIUS server to provide a public/private key encryption system. Up to 2 certificates can be resident on a SM. An installed certificate can be deleted by clicking the Delete button in the certificates description block on the Configuration > Security tab. To restore the 2 default certificates, click the Use Default Certificates button in the RADIUS Certificate Settings parameter block and reboot the radio. Page 7-235 Chapter 7: Configuration Configuring a RADIUS server Encryption Setting Web, Telnet, FTP Session Timeout Ethernet Access IP Access Control Allowed Source IP 1 Allowed Source IP 2 Allowed Source IP 3 Web Access Specify the type of airlink security to apply to this AP. The encryption setting must match the encryption setting of the SMs. None provides no encryption on the air link. DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. Enter the expiry in seconds for remote management sessions via HTTP, telnet or ftp access to the AP. If you want to prevent any device that is connected to the Ethernet port of the SM from accessing the management interface of the SM, select Ethernet Access Disabled. This selection disables access through this port to via HTTP (the GUI), SNMP, telnet, FTP, and TFTP. With this selection, management access is available through only the RF interface via either an IP address (if Network Accessibility is set to Public on the SM) or the Session Status or Remote Subscribers tab of the AP. See IP Access Control below. If you want to allow management access through the Ethernet port, select Ethernet Access Enabled. This is the factory default setting for this parameter. You can permit access to the AP from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address If you selected IP Access Filtering Enabled for the IP Access Control parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the AP from any IP address. You may populate as many as all three. If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. The Radio supports secured and non-secured web access protocols. Select suitable web access from drop down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. Page 7-236 Chapter 7: Configuration Configuring a RADIUS server SNMP Telnet FTP TFTP HTTP and HTTPS If enabled, the radio can be accessed via both http and https. This option allows to configure SNMP agent communication version. It can be selected from drop down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. SM - Phase 1 (Outside Identity) parameters and settings The protocols supported for the Phase 1 (Outside Identity) phase of authentication are eapttls (Extensible Authentication Protocol Tunneled Transport Layer Security) and eapMSChapV2

(Extensible Authentication Protocol Microsoft Challenge-Handshake Authentication Protocol). Configure an outer Identity in the Username field. This must match the Phase 1/Outer Identity username configured in the RADIUS server. The default Phase 1/Outer Identity Username is anonymous. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. If Realms are being used in the RADIUS system (eapttls only), select Enable Realm and configure an outer identity in the Identity field and a Realm in the Realm field. These must match the Phase 1/Outer Identity and Realm configured in the RADIUS server. The default Identity is anonymous. The Identity can be up to 128 non-special (no diacritical markings) alphanumeric characters. The default Realm is canopy.net. The Realm can also be up to 128 non-special alphanumeric characters. SM - Phase 2 (Inside Identity) parameters and settings If using eapttls for Phase 1 authentication, select the desired Phase 2 (Inside Identity) authentication protocol from the Phase 2 options of PAP (Password Authentication Protocol), CHAP (Challenge Handshake Authentication Protocol), and MSCHAPv2 (Microsofts version of CHAP). The protocol must be consistent with the authentication protocol configured on the RADIUS server. Enter a Username for the SM. This must match the username configured for the SM on the RADIUS server. The default Username is the SMs MAC address. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. Enter the desired password for the SM in the Password and Confirm Password fields. The Password must match the password configured for the SM on the RADIUS server. The default Password is password. The Password can be up to 128 non-special (no diacritical markings) alphanumeric characters. Page 7-237 Chapter 7: Configuration Configuring a RADIUS server Handling Certificates Managing SM Certificates via the SM GUI The default public Canopy certificates are loaded into SMs upon factory software installation. The default certificates are not secure and are intended for use during lab and field trials as part of gaining experience with the RADIUS functionalities or as an option during debug. For secure operation, an operator will want to create or procure their own certificates. Resetting a SM to its factory defaults will remove the current certificates and restore the default certificates. Up to two certificates can be resident on a SM. An installed certificate can be deleted by clicking the Delete button in the certificates description block on the Configuration > Security tab. To restore the 2 default certificates, click the Use Default Certificates button in the RADIUS Certificate Settings parameter block and reboot the radio. To upload a certificate manually to a SM, first load it in a known place on your PC or network drive, then click on a Delete button on one of the Certificate description blocks to delete a certificate to provide space for your certificate. Click on Choose File, browse to the location of the certificate, and click the Import Certificate button, and then reboot the radio to use the new certificate. When a certificate is in use, after the SM successfully registers to an AP, an indication of In Use will appear in the description block of the certificate being used. The public certificates installed on the SMs are used with the private certificate on the RADIUS server to provide a public/private key encryption system. Note Root certificates of more than one level (Example - a certificate from someone who received their CA from Verisign) fails. Certificates must be either root or self-signed. Page 7-238 Chapter 7: Configuration Figure 159 SM Certificate Management Configuring a RADIUS server Configuring RADIUS servers for SM authentication Your RADIUS server must be configured to use the following:

EAPTTLS or MSCHAPv2 as the Phase 1/Outer Identity protocol. If Enable Realm is selected on the SMs Configuration > Security tab, then the same Realm appears there (or access to it). The same Phase 2 (Inner Identity) protocol as configured on the SMs Configuration > Security tab under Phase 2 options. The username and password for each SM configured on each SMs Configuration > Security tab. An IP address and NAS shared secret that is the same as the IP address and Shared Secret configured on the APs Configuration > Security tab for that RADIUS server. Page 7-239 Chapter 7: Configuration Configuring a RADIUS server A server private certificate, server key, and CA certificate that complement the public certificates distributed to the SMs, as well as the Canopy dictionary file that defines Vendor Specific Attributes

(VSAa). Default certificate files and the dictionary file are available from the software site:

https://support.cambiumnetworks.com/files/pmp450 after entering your name, email address, and either Customer Contract Number or the MAC address of a module covered under the 12 month warranty. Optionally, operators may configure the RADIUS server response messages (Accept or Reject) so that the user has information as to why they have been rejected. The AP displays the RADIUS Authentication Reply message strings in the Session Status list as part of each SMs information. The SM will show this string (listed as Authentication Response on the SM GUI) on the main Status page in the Subscriber Module Stats section. Note Aradial AAA servers only support operator-configurable Authentication Accept responses, not Authentication Reject responses. Page 7-240 Chapter 7: Configuration Configuring a RADIUS server Assigning SM management IP addressing via RADIUS Operators may use a RADIUS AAA server to assign management IP addressing to SM modules (framed IP address). SMs now interpret attributes Framed-IP-Address, Framed-IP-Netmask, and Cambium-

Canopy-Gateway from RADIUS. The RADIUS dictionary file has been updated to include the Cambium-

Canopy-Gateway attribute and is available on the Cambium Software Support website. In order for these attributes to be assigned and used by the SM, the following must be true:

The system is configured for AAA authentication The SM is not configured for DHCP on its management interface. If DHCP is enabled and these attributes are configured in the RADIUS server, the attributes is ignored by the SM. The SM management interface must be configured to be publically accessible. If the SM is configured to have local accessibility, the management interface will still be assigned the framed addressing, and the SM iscome publicly accessible via the assigned framed IP addressing. When using these attributes, for the addressing to be implemented by the SM operators must configure Framed-IP-Address in RADIUS. If Framed-IP-Address is not configured but Framed-IP-

Netmask and/or Cambium-Canopy-Gateway is configured, the attributes is ignored. In the case where only the Framed-IP-Address is configured, Framed-IP-Netmask defaults to 255.255.0.0 (NAT disabled) / 255.255.255.0 (NAT enabled) and Cambium-Canopy-Gateway defaults to 0.0.0.0. Configuring RADIUS server for SM configuration Canopy Vendor Specific Attributes (VSAs) along with VSA numbers and other details are listed in Table 184. The associated SM GUI page, tab and parameter are listed to aid cross-referencing and understanding of the VSAs. A RADIUS dictionary file is available from the software site:

https://support.cambiumnetworks.com/files/pmp450 The RADIUS dictionary file defines the VSAs and their values and is usually imported into the RADIUS server as part of server and database setup. Page 7-241 Chapter 7: Configuration Configuring a RADIUS server Note Beginning with System Release 12.0.2, two RADIUS dictionary files are available on the Cambium website RADIUS Dictionary file Cambium and RADIUS Dictionary file Motorola. In addition to a renaming of attributes, the Cambium-branded dictionary file contains two new VSAs for controlling uplink and downlink Maximum Burst Data Rate (these VSAs are listed below in Table 184). If you are transitioning from the Motorola-branded dictionary file to the Cambium-branded dictionary file, ensure that all RADIUS profiles containing Motorola-Canopy attribute references are updated to include Cambium-Canopy attribute references (for all applicable VSAs listed in Table 184). Also, ensure that all RADIUS configuration files reference the new dictionary file (as an alternative, operators may rename the Cambium-branded dictionary file to the filename currently in use by the RADIUS server). Once the profiles are updated and the new Cambium-branded dictionary file is installed on the RADIUS server, restart the RADIUS server to ensure that the new VSAs and attribute names are enabled. Table 184 RADIUS Vendor Specific Attributes (VSAs) Name Number Type Required Value

-

26.311.16 MS-MPPE-Send-Key*

-

MS-MPPE-Recv-Key*

-

Cambium-Canopy-LPULCIR Configuration > Quality of Service > Low Priority Uplink CIR 26.161.1 integer 26.311.17

-

Y Y N Cambium-Canopy-LPDLCIR N Configuration > Quality of Service > Low Priority Downlink CIR Cambium-Canopy-HPULCIR N 26.161.3 26.161.2 integer integer Configuration > Quality of Service > Hi Priority Uplink CIR Cambium-Canopy-HPDLCIR Configuration > Quality of Service > Hi Priority Uplink CIR 26.161.4 integer N 26.161.5 Cambium-Canopy-HPENABLE integer Configuration > Quality of Service > Hi Priority Channel Enable/Disable 26.161.6 Configuration > Quality of Service > Sustained Uplink Data Rate integer N N Page 7-242

-

-

-

-

0-65535 kbps 0 kbps 0-65535 kbps 0 kbps 0-65535 kbps 0 kbps 0-65535 kbps 0 kbps 0-disable, 1-enable 0 0-100000 kbps dependent on radio feature set

-

-

32 bits 32 bits 32 bits 32 bits 32 bits 32 bits Chapter 7: Configuration Configuring a RADIUS server Cambium-Canopy-ULBL 26.161.7 integer N 0-2500000 kbps Configuration > Quality of Service > Uplink Burst Allocation Cambium-Canopy-DLBR Configuration > Quality of Service > Sustained Downlink Data Rate 26.161.8 integer N Cambium-Canopy-DLBL N Configuration > Quality of Service > Downlink Burst Allocation 26.161.9 integer Cambium-Canopy-

VLLEARNEN 26.161.14 integer N Configuration > VLAN > Dynamic Learning Cambium-Canopy-VLFRAMES 26.161.15 integer N Configuration > VLAN > Allow Frame Types Cambium-Canopy-VLIDSET 26.161.16 integer N Configuration > VLAN Membership 26.161.20 Cambium-Canopy-VLAGETO Configuration > VLAN > VLAN Aging Timeout Cambium-Canopy-VLIGVID 26.161.21 integer N integer N Configuration > VLAN > Default Port VID Cambium-Canopy-VLMGVID Configuration > VLAN > Management VID Cambium-Canopy-

VLSMMGPASS 26.161.22 26.161.23 integer N integer N Configuration > VLAN > SM Management VID Pass-through N Cambium-Canopy-BCASTMIR 26.161.24 integer Configuration > Quality of Service > Broadcast/Multicast Uplink Data Rate dependent on radio feature set 0-100000 kbps dependent on radio feature set 0-2500000 kbps dependent on radio feature set 0-disable, 1-enable 1 0-all, 1-tagged, 2-

untagged 0 VLAN Membership (1-

4094) 0 5 - 1440 minutes 25 mins 1 4094 1 1 4094 1 0-disable, 1-enable 1 0-100000 kbps, 0=disabled dependent on radio feature set Cambium-Canopy-Gateway 26.161.25 ipaddr N

-

Configuration > IP > Gateway IP Address Cambium-Canopy-ULMB 26.161.26 integer N 0.0.0.0 0-100000 kbps 32 bits 32 bits 32 bits 32 bits 32 bits 32 bits 32 bits 32 bits 32 bits 32 bits 32 bits

-

Configuration > Quality of Service > Max Burst Uplink Data Rate 0 32 bits Page 7-243 Chapter 7: Configuration Configuring a RADIUS server Cambium-Canopy-DLMB 26.161.27 integer N 0-100000 kbps Configuration > Quality of Service > Max Burst Downlink Data Rate Cambium-Canopy-UserLevel 26.161.50 integer N 0 1-Technician, 2-

Installer, 3-

Administrator Account > Add User > Level 0 Cambium-Canopy-DHCP-State 26.161.31 integer N 1-Enable Configuration > IP > DHCP state Cambium-Canopy-

BCASTMIRUNITS Configuration > QoS >

Broadcast Downlink CIR Cambium-Canopy-

ConfigFileImportUrl Configuration > Unit Settings Cambium-Canopy-

ConfigFileExportUrl Configuration > Unit Settings 26.161.28 integer N 26.161.29 string 26.161.30 string N N N 1 0 0 0 1=Read-Only 0=Read-

Write 0 Cambium-Canopy-UserMode 26.161.51 integer Account > Add User > User Mode 32 bits 32 bits 32 bits 32 bits 32 bits 32 bits 32 bits

(*) Contains key for encrypting packets sent by the NAS to the remote host (for Microsoft Point-to-Point Encryption Protocol). Note VSA numbering:

26 connotes Vendor Specific Attribute, per RFC 2865 26.311 is Microsoft Vendor Code, per IANA Page 7-244 Chapter 7: Configuration Configuring a RADIUS server Configuring RADIUS server for SM configuration using Zero Touch feature The RADIUS VSA (Vendor Specific Attributes) is updated for Zero Touch feature. This feature enables the ability for a SM to get its configuration via RADIUS VSA. The RADIUS VSA is updated for an URL which points to the configuration file of SM (see Table 184 for list of VSA). The RADIUS will push the vendor specific attribute to SM after successful authentication. The VSA contains URL of config file which will redirect SM to download configuration. If there is any change in SM confirmation, the SM will reboot automatically after applying the configuration. The RADIUS VSA attributes concerning Zero Touch are as follows:

VSA Type String Cambium-Canopy-ConfigFileImportUrl (29) string Maximum Length 127 characters. Cambium-Canopy-ConfigFileExportUrl (30) string Maximum Length 127 characters. The updated RADIUS dictionary can be downloaded from below link:

https://support.cambiumnetworks.com/files/pmp450/

Note The feature is not applicable to the AP. Page 7-245 Chapter 7: Configuration Configuring a RADIUS server Using RADIUS for centralized AP and SM user name and password management AP Technician/Installer/Administrator Authentication To control technician, installer, and administrator access to the AP from a centralized RADIUS server:

Procedure 28 Centralized user name and password management for AP 1 2 Set Authentication Mode on the APs Configuration > Security tab to RADIUS AAA Set User Authentication Mode on the APs Account > User Authentication tab (the tab only appears after the AP is set to RADIUS authentication) to Remote or Remote then Local. Local: The local SM is checked for accounts. No centralized RADIUS accounting

(access control) is performed. Remote: Authentication by the centralized RADIUS server is required to gain access to the SM if the SM is registered to an AP that has RADIUS AAA Authentication Mode selected. For up to 2 minutes a test pattern is displayed until the server responds or times out. Remote then Local: Authentication using the centralized RADIUS server is attempted. If the server sends a reject message, then the setting of Allow Local Login after Reject from AAA determines if the local user database is checked or not. If the configured servers do not respond within 2 minutes, then the local user database is used. The successful login method is displayed in the navigation column of the SM. User administration and authentication separation On the AP, it is possible to configure up to three User Authentication servers, along with their Shared Secret. If none of the User Authentication servers are configured, the AP continues to use SM Authorization servers for User Authentication. If at least one of the IP addresses is configured, all Authentication, Authorization, and Accounting requests now follow the newly configured User Authorization server. To configure separate User Authentication and SM Authentication:

Page 7-246 Chapter 7: Configuration Configuring a RADIUS server Procedure 29 User administration and authentication separation 1 2 3 4 Go to the APs Account > User Authentication And Access Tracking tab Set User Authentication Mode to Remote or Remote then Local. Set User Authentication Method to EAP-MD5 or EAP-PEAP-MSCHAPv2 Configure the Shared Secrets and IP Addresses of:

User Authentication Server 1 User Authentication Server 2 User Authentication Server 3 Note: If none of the above User Authentication servers are configured, only SM authentication will be performed. 5 Under RADIUS Certificate Settings, click Browse to upload the RADIUS Certificate files. Page 7-247 Chapter 7: Configuration Configuring a RADIUS server Table 185 AP User Authentication and Access Tracking attributes Attribute User Authentication Mode Meaning Local: The local SM is checked for accounts. No centralized RADIUS accounting (access control) is performed. Remote: Authentication by the centralized RADIUS server is required to gain access to the AP. For up to 2 minutes a test pattern is displayed until the server responds or times out. Page 7-248 Chapter 7: Configuration Configuring a RADIUS server Remote then Local: Authentication using the centralized RADIUS server is attempted. If the server sends a reject message, then the setting of Allow Local Login after Reject from AAA determines if the local user database is checked or not. If the configured servers do not respond within 2 minutes, then the local user database is used. The successful login method is displayed in the navigation column of the AP. User Authentication Method Allow Local Login after Reject from AAA The user authentication method employed by the radios:

EAP-MD5 EAP-PEAP-MSCHAPv2 If a user authentication is rejected from the AAA server, the user is allowed to login locally to the radios management interface. User Authentication Server 1 User Authentication Server 2 User Authentication Server 3 RADIUS Certificate Settings User Authentication Certificate 1 User Authentication Certificate 2 Radius Accounting Port Accounting Messages Accounting Data Usage Interval SM Re-authentication Interval Account Status The IP address and the shared secret key of the User authentication RADIUS server 1. The IP address and the shared secret key of the User Authentication Server 2 configured in RADIUS Server. The IP address and the shared secret key of the User Authentication Server 3 configured in RADIUS Server. Import Cetificate browse and select the file to be uploaded and click on Import Certificate to import a new certificate. Use Default Certificates use the preloaded default certificates. Cerificate provided by default for User authentication. Cerificate provided by default for User authentication. The destination port on the AAA server used for Radius accounting communication. disable no accounting messages are sent to the RADIUS server. deviceAccess accounting messages regarding device access are sent to the RADIUS server (see Table 187). dataUsage accounting messages regarding data usage are sent to the RADIUS server (see Table 187). All accounting messages regarding device access and data usage are sent to the RADIUS server. The interval for which accounting data messages are sent from the radio to the RADIUS server. If 0 is configured for this parameter, no data usage messages are sent. The interval for which the SM will re-authenticate to the RADIUS server. Displays the account status. Page 7-249 Chapter 7: Configuration Configuring a RADIUS server SM Technician/Installer/Administrator Authentication The centralized user name and password management for SM is same as AP. Follow AP Technician/Installer/Administrator Authentication on page 7-245 procedure. Note Remote access control is enabled only after the SM registers to an AP that has Authentication Mode set to RADIUS AAA. Local access control will always be used before registration and is used after registration if the AP is not configured for RADIUS. Figure 160 User Authentication and Access Tracking tab of the SM Table 186 SM User Authentication and Access Tracking attributes Attribute User Authentication Mode Meaning Local: The local SM is checked for accounts. No centralized RADIUS accounting (access control) is performed. Page 7-250 Chapter 7: Configuration Configuring a RADIUS server Remote: Authentication by the centralized RADIUS server is required to gain access to the SM if the SM is registered to an AP that has RADIUS AAA Authentication Mode selected. For up to 2 minutes a test pattern is displayed until the server responds or times out. Remote then Local: Authentication using the centralized RADIUS server is attempted. If the server sends a reject message, then the setting of Allow Local Login after Reject from AAA determines if the local user database is checked or not. If the configured servers do not respond within 2 minutes, then the local user database is used. The successful login method is displayed in the navigation column of the SM. If a user authentication is rejected from the AAA server, the user is allowed to login locally to the radios management interface. It is applicable ONLY when the User Authentication Mode is set to Remote then Local. Note When the radio User Authentication Mode is set to Local or Remote, the Allow Local Login after Reject from AAA does not any effect. Allow Local Login after Reject from AAA Accounting Messages disable no accounting messages are sent to the RADIUS server deviceAccess accounting messages are sent to the RADIUS server regarding device access (see Table 187). Access Tracking To track logon and logoff times on individual radios by technicians, installers, and administrators, on the AP or SMs Account > User Authentication and Access Tracking tab under Accounting (Access Tracking) set Accounting Messages to deviceAccess. Device Access Tracking is enabled separately from User Authentication Mode. A given AP or SM can be configured for both, either, or neither. RADIUS Device Data Accounting PMP 450 Platform systems include support for RADIUS accounting messages for usage-based billing. This accounting includes indications for subscriber session establishment, subscriber session disconnection, and bandwidth usage per session for each SM that connects to the AP. The attributes included in the RADIUS accounting messages are shown in the table below. Table 187 Device data accounting RADIUS attributes Sender Message Attribute AP Acct-Status-Type Value 1 - Start Description Page 7-251 Configuring a RADIUS server Description This message is sent every time a SM registers with an AP, and after the SM stats are cleared. This message is sent every time a SM becomes unregistered with an AP, and when the SM stats are cleared. Chapter 7: Configuration Sender Message Attribute Value Acct-Session-Id Accounting-

Request Event-Timestamp Unique per AP session. Initial value is SM MAC, and increments after every start message sent of an in session SM. UTC time the event occurred on the AP Acct-Status-Type 2 - Stop Acct-Session-Id Acct-Input-Octets Acct-Output-Octets AP Accounting-

Request Acct-Input-

Gigawords Acct-Output-

Gigawords Acct-Input-Packets Acct-Output-Packets Unique per AP session. Initial value is SM MAC, and increments after every start message sent of an in session SM. Sum of the input octets received at the SM over regular data VC and the high priority data VC (if enabled). Will not include broadcast. Sum of the output octets sent from the SM over regular data VC and the high priority data VC (if enabled). Number of times the Acct-

Input-Octets counter has wrapped around 2^32 over the course of the session Number of times the Acct-

Output-Octets counter has wrapped around 2^32 over the course of the session Sum of unicast and multicast packets that are sent to a particular SM over the regular data VC and the high priority data VC (if enabled). It will not include broadcast. Sum of unicast and multicast packets that are sent from a particular SM over the regular data VC and the high priority data VC (if enabled). Page 7-252 Chapter 7: Configuration Configuring a RADIUS server Sender Message Attribute Value Description Acct-Session-Time Uptime of the SM session. Acct-Terminate-

Cause Reason code for session termination AP Accounting-

Request Acct-Status-Type Acct-Session-Id Acct-Input-Octets Acct-Output-Octets Acct-Input-

Gigawords Acct-Output-

Gigawords This message is sent periodically per the operator configuration on the AP in seconds. Interim update counts are cumulative over the course of the session 3 - Interim-Update Unique per AP session. Initial value is SM MAC, and increments after every start message sent of an in session SM. Sum of the input octets sent to the SM over regular data VC and the high priority data VC (if enabled). Will not include broadcast. Sum of the output octets set from the SM over regular data VC and the high priority data VC (if enabled). Number of times the Acct-

Input-Octets counter has wrapped around 2^32 over the course of the session Number of times the Acct-

Output-Octets counter has wrapped around 2^32 over the course of the session Acct-Session-Time Uptime of the SM session. Acct-Input-Packets Acct-Output-Packets Sum of unicast and multicast packets that are sent to a particular SM over the regular data VC and the high priority data VC (if enabled). It will not include broadcast. Sum of unicast and multicast packets that are sent from a particular SM over the regular data VC and the high priority data VC (if enabled). Page 7-253 Chapter 7: Configuration Configuring a RADIUS server The data accounting configuration is located on the APs Accounts > User Authentication and Access Tracking GUI menu, and the APs Authentication Mode must be set to Radius AAA for the menu to appear. The accounting may be configured via the AP GUI as shown in the figures below. By default accounting messages are not sent and the operator has the choice of configuring to send only Device Access accounting messages (when a user logs in or out of the radio), only Data Usage messages, or both. When Data Accounting is enabled, the operator must specify the interval of when the data accounting messages are sent (0 disabled, or in the range of 30-10080 minutes). The default interval is 30 minutes. Figure 161 RADIUS accounting messages configuration The data accounting message data is based on the SM statistics that the AP maintains, and these statistics may be cleared on the AP by an operator. If an operator clears these messages and data accounting is enabled, an accounting stop message is sent followed by an accounting start message to notify the AAA of the change. If an operator clears the VC statistics on the device through the management GUI, a RADIUS stop message and data start message is issued for each device affected. The start and stop messages will only be sent once every 5 minutes, so if an operator clears these statistics multiple times within 5 minutes, only one set of data stop/start messages is sent. This may result in inaccurate data accumulation results. RADIUS Device Re-authentication PMP 450 Platform systems include support for periodic SM re-authentication in a network without requiring the SM to re-register (and drop the session). The re-authentication may be configured to occur in the range of every 30 minutes to weekly. Figure 162 Device re-authentication configuration The re-authentication interval is only configurable on the AP. When this feature is enabled, each SM that enters the network will re-authenticate each the interval time has expired without dropping the session. The response that the SM receives from the AAA server upon re-authentication is one of the following:

Success: The SM continues normal operation Reject: The SM de-registers and will attempt network entry again after 1 minute and then if rejected will attempt re-entry every 15 minutes Page 7-254 Chapter 7: Configuration Configuring a RADIUS server Timeout or other error: The SM remains in session and attempt 5 times to re-authenticate with the RADIUS-REQUEST message. If these attempts fail, then the SM will go out of session and proceed to re-authenticate after 5 minutes, then every 15 minutes. Although re-authentication is an independent feature, it was designed to work alongside with the RADIUS data usage accounting messages. If a user is over their data usage limit the network operator can reject the user from staying in the network. Operators may configure the RADIUS Reply-Message attribute with an applicable message (i.e. Data Usage Limit Reached) that is sent to the subscriber module and displayed on the general page. Page 7-255 Chapter 7: Configuration Configuring a RADIUS server RADIUS Change of Authorization and Disconnect Message Prior to this feature, SM will get configuration parameters from a RADIUS server during authentication process. This feature allows an administrator to control configuration parameters in the SM while SM is in session. The configuration changes in SM are done using RADIUS Change of Authorization method

(RFC 3576) on the existing RADIUS authentication framework for AP and SM. A typical use case could be changing the QOS parameters after a certain amount of bandwidth usage by a SM. Figure 163 RADIUS CoA configuration for AP The RADIUS CoA feature enables initiating a bi-directional communication from the RADIUS server(s) to the AP and SM. The AP listens on UDP port 3799 and accepts CoA requests from the configured RADIUS servers. This CoA request should contain SM MAC address in User-Name attribute as identifier and all other attributes which control the SM config parameters. For security reasons, a timestamp also needs to be added as Event-Timestamp attribute. Hence the time should also be synchronized between the RADIUS server(s) and the AP to fit within a window of 300 seconds. Once the configuration changes are applied on the SM, CoA-ACK message is sent back to RADIUS server. If the validation fails, the AP sends a CoA-NACK response to the RADIUS server with proper error code. A Disconnect-Message is sent by the RADIUS server to NAS in order to terminate a user session on a NAS and discard all associated session context. It is used when the authentication AAA server wants to disconnect the user after the session has been accepted by the RADIUS. In response of Disconnect-Request from RADIUS server, the NAS sends a Disconnect-ACK if all associated session context is discarded, or a Disconnect-NACK, if the NAS is unable to disconnect the session. Note The RADIUS CoA feature will only enabled if Authentication mode is set to RADIUS AAA. Page 7-256 Chapter 7: Configuration Configuring a RADIUS server Microsoft RADIUS support This feature allows to configure Microsoft RADIUS (Network Policy and Access Services a.k.a NPS) as Authentication server for SM and User authentication. For SM Authentication, SM will user PEAP-MSCHAPv2 since NPS doesnt support TTLS protocol. For User Authentication, the Canopy software will use EAP-MD5 but the user has to do certain configuration in order to enable EAP-MD5 on NPS. Note All this configuration has been tested on Windows Server 2012 R2 version. This feature is not supported on hardware board type P9 or lower platforms. SM Authentication Configuration There are no new configuration on AP. However SM has to be configured for PEAP authentication protocol. 1. 2. Go to Configuration > Security page Select eappeap for Phase 1 attribute under tab AAA Authentication Settings. Figure 164 EAPPEAP settings The Phase 2 will change automatically to MSCHAPv2 on select of Phase 1 attribute as EAP-PEAP. Other parameters of Phase 2 protocols like PAP/CHAP will be disabled. Windows Server Configuration Import Certificate The SM certificate has to be imported to Windows Server for certificate authentication. 1. Copy the certificate which is configured in SM under Configuration > Security -> Certificate1 to Windows Server machine. Right click and select Install Certificate. This will install the certificate and its ready for use. This certificate will be used while configuring PEAP-MSCHAPv2 in NPS. 2. Page 7-257 Chapter 7: Configuration Configuring a RADIUS server NPS Configuration (https://technet.microsoft.com/en-us/network/bb545879.aspx) Following items should be configured in NPS Console:

RADIUS Client o https://technet.microsoft.com/en-us/library/cc732929 Connection Request Policies o https://technet.microsoft.com/en-us/library/cc730866 o Choose Wireless-Other in NAS-Port-Type Network Policy o https://technet.microsoft.com/en-us/library/cc755309 o Choose Wireless-Other in NAS-Port-Type. o While configuring PEAP, select the above imported certificate. Figure 165 Importing certificate in NPS User Authentication Configuration Enabling EAP-MD5 As mentioned earlier, Microsoft has deprecated the support for MD5 from versions of Windows. To enable MD5, the following steps to be followed:

1. Follow the instructions:

https://support.microsoft.com/en-us/kb/922574/en-us?wa=wsignin1.0 Optionally, the registry file can be downloaded. It can be installed by double-click it in Windows Registry. From NPS Console Network Policy > <Policy Name> > Properties > Constrains >

Authentication Method and click Add. Select MD5 and click OK. 2. Page 7-258 Chapter 7: Configuration Configuring a RADIUS server Figure 166 Selecting MD5 from NPS console User Configuration in Active Directory Next open Active Directory Users and Computers and create user. Make sure user property is configured as shown below. Figure 167 User configuration Page 7-259 Chapter 7: Configuration Configuring a RADIUS server RADIUS VSA Configuration Before using VSA, the Cambium-Canopy-UserLevel(50) VSA must be configured with some access level say ADMIN(3). Follow below link for configuring VSA:

https://technet.microsoft.com/en-us/library/cc731611 The Cambiums vendor code is 161. Figure 168 RADIUS VSA configuration Accounting User can enable accounting in NPS under NPS Console > Accounting >

Configure Accounting. For more details refer https://technet.microsoft.com/library/dd197475 Page 7-260 Chapter 7: Configuration Configuring a RADIUS server Cisco ACS RADIUS Server Support This briefly explains how to configure Cisco ACS RADIUS server for PEAP-MSCHAPv2 authentication. The configuration had been tested on CISCO ACS Version : 5.7.0.15 Adding RADIUS client Figure 169 Adding RADIUS client Creating Users Figure 170 Creating users Page 7-261 Chapter 7: Configuration Configuring a RADIUS server Creating RADIUS instance Figure 171 Creating RADIUS instance RADIUS protocols Figure 172 RADIUS protocols Page 7-262 Chapter 7: Configuration Service selection Figure 173 Service selection Adding Trusted CA Figure 174 Adding Trusted CA Configuring a RADIUS server Note that certificate has to be in DER form, so if you have in PEM format convert using openssl. Openssl.exe x509 -in <path-to->/cacert_aaasvr.pem -outform DER -out <path-

to>/cacert_aaasvr.der Installing Server Certificate After installing trusted CA, you need to add a server certificate which will be used for TLS tunnel. Generally you have to install same certificate which is installed in your AP, so that AP can trust the radius server. Figure 175 Installing Server Certificate Page 7-263 Chapter 7: Configuration Monitoring Logs Figure 176 Monitoring logs Configuring a RADIUS server Configuring VSA Before using VSA , user has to add Cambium Vendor Specific Attribute Navigate to System Administration > Configuration > Dictionaries > Protocols > RADIUS > RADIUS VSA > Motorola If Motorola is not present you can create Vendor with ID 161 and add all the VSA one by one. Page 7-264 Chapter 7: Configuration Figure 177 VSA list Configuring a RADIUS server Using VSA for users Navigate to Access Policies > Access Services > Cambium ACS > Authorization 1. Change condition to User name Page 7-265 Chapter 7: Configuration Configuring a RADIUS server 2. Next click Create and then click Select see diagram below 3. Click Create from the screen you get following screen Chose some name and then move to RADIUS Attributes tab 4. Fill attribute which all you want for that particular user Important: Click Add for each attribute and when done click Submit. Page 7-266 Chapter 7: Configuration Configuring a RADIUS server 5. Now you are ready to use this Authorization profile for the use Select and Press OK 6. Finally press Save Changes and you are ready to use it. Page 7-267 Chapter 7: Configuration Configuring Ping Watchdog Configuring Ping Watchdog This feature allows administrator to automatically reboot an AP/SM when there is a network issue to avoid power on reset of radios. This feature is disabled by default. To enable Ping Watchdog feature, select the menu option Configuration > Ping Watchdog, and configure the parameters listed in the following table. Table 188 Ping Watchdog attributes Attribute Ping Watchdog IP Address To Ping Ping Interval Ping Failure Count To Reboot Meaning This filed enables or disbales Ping Watchdog feature. This field specifies the IPV4 address of the device which needs to be pinged. This field specifies the time interval at which ping needs to be initiated. The time interval needs to be specified in seconds. This field specifies the count of ping failures at which reboot needs to be initiated. Page 7-268 Chapter 8: Tools The AP and SM GUIs provide several tools to analyze the operating environment, system performance and networking, including:

Using Spectrum Analyzer tool on page 8-2 Using the Alignment Tool on page 8-14 Using the Link Capacity Test tool on page 8-21 Using AP Evaluation tool on page 8-31 Using BHM Evaluation tool on page 8-35 Using the OFDM Frame Calculator tool on page 8-39 Using the Subscriber Configuration tool on page 8-43 Using the Link Status tool on page 8-44 Using BER Results tool on page 8-49 Using the Sessions tool on page 8-50 Using the Ping Test tool on page 8-51 Page 8-1 Chapter 8: Tools Using Spectrum Analyzer tool Using Spectrum Analyzer tool The integrated spectrum analyzer can be very useful as a tool for troubleshooting and RF planning, but is not intended to replicate the accuracy and programmability of a high-end spectrum analyzer, which sometime can be used for other purposes. The AP/BHM and SM/BHS perform spectrum analysis together in the Sector Spectrum Analyzer tool. Caution On start of the Spectrum Analyzer on a module, it enters a scan mode and drops any RF connection it may have had. When choosing Start Timed Spectrum Analysis, the scan is run for the amount of time specified in the Duration configuration parameter. When choosing Start Continuous Spectrum Analysis, the scan is run continuously for 24 hours, or until stopped manually (using the Stop Spectrum Analysis button). Any module can be used to see the frequency and power level of any detectable signal that is within, just above, or just below the frequency band range of the module. Note Vary the days and times when you analyze the spectrum in an area. The RF environment can change throughout the day or throughout the week. Mapping RF Neighbor Frequencies The neighbor frequencies can be analyzed using Spectrum Analyzer tool. Following modules allow user to:

Use a BHS or BHM for PTP and SM or AP for PMP as a Spectrum Analyzer. View a graphical display that shows power level in RSSI and dBm at 5 MHz increments throughout the frequency band range, regardless of limited selections in the Custom Radio Frequency Scan Selection List parameter of the SM/BHS. Select an AP/BHM channel that minimizes interference from other RF equipment. Caution The following procedure causes the SM/BHS to drop any active RF link. If a link is dropped when the spectrum analysis begins, the link can be re-established when either a 15 minute interval has elapsed or the spectrum analyzer feature is disabled. Temporarily deploy a SM/BHS for each frequency band range that need to monitor and access the Spectrum Analyzer tab in the Tools web page of the module. Page 8-2 Chapter 8: Tools Using Spectrum Analyzer tool Using the Remote Spectrum Analyzer tool Using Spectrum Analyzer tool Spectrum Analyzer tool Analyzing the spectrum To use the built-in spectrum analyzer functionality of the AP/SM/BH, proceed as follows:

Procedure 30 Analyzing the spectrum 1 2 3 4 5 6 Predetermine a power source and interface that works for the AP/SM/BH in the area to be analyzed. Take the AP/SM/BH, power source and interface device to the area. Access the Tools web page of the AP/SM/BH. Enter Duration in Timed Spectrum Analyzer Tab. Default value is 10 Seconds Click Start Timed Sector Spectrum Analysis The results are displayed:

Figure 178 Spectrum analysis - Results Note AP/SM/BH scans for extra 40 seconds in addition to configured Duration 7 8 9 Travel to another location in the area to BHS. Click Start Timed Spectrum Analysis Repeat Steps 4 and 6 until the area has been adequately scanned and logged. As with any other data that pertains to your business, a decision today to put the data into a retrievable database may grow in value to you over time. Page 8-3 Chapter 8: Tools Using Spectrum Analyzer tool Note Wherever the operator find the measured noise level is greater than the sensitivity of the radio that is plan to deploy, use the noise level (rather than the link budget) for your link feasibility calculations. The AP/SM/BH perform spectrum analysis together in the Sector Spectrum Analyzer feature. Graphical spectrum analyzer display The AP/SM/BH display the graphical spectrum analyzer. An example of the Spectrum Analyzer page is shown in Figure 178. The navigation feature includes:

Results may be panned left and right through the scanned spectrum by clicking and dragging the graph left and right Results may be zoomed in and out using mouse When the mouse is positioned over a bar, the receive power level, frequency, maximum and mean receive power levels are displayed above the graph To keep the displayed data current, either set Auto Refresh on the modules Configuration > General. Spectrum Analyzer page of AP The Spectrum Analyzer page of AP is explained in Table 189. Table 189 Spectrum Analyzer page attributes - AP Page 8-4 Chapter 8: Tools Attribute Display Data Path Data Display Min and Max Frequencies in KHz Set Min And Max to Full Scan Set Min And Max to Center Scan +/-40 MHz Registered SM Count Maximum Count of Registered SMs SM Scanning Bandwidth Duration Continuous Spectrum Analyzer Using Spectrum Analyzer tool Meaning Both means that the vertical and horizontal paths are displayed or an individual path may be selected to display only a single-path reading. For ease of parsing data and to facilitate automation, the spectrum analyzer results may be saved as an XML file. To save the results in an XML formatted file, right-click the SpectrumAnalysis.xml link and save the file. Instantaneous means that each reading (vertical bar) is displayed with two horizontal lines above it representing the max power level received (top horizontal line) and the average power level received (lower horizontal line) at that frequency. Averaging means that each reading (vertical bar) is displayed with an associated horizontal line above it representing the max power level received at that frequency. Enter minimum and maximum frequencies to be scanned. On the button press, it sets mimimum and maximum allowed frequencies for scanning. On the button press, it sets mimium and maximum frequencies to 40 MHz of center frequency for scanning. This field displays the MAC address and Site Name of the registered SM. This field displays the maximum number of registered SMs. This field allows to select SMs scanning bandwidth. This field allows operators to configure a specified time for which the spectrum is scanned. If the entire spectrum is scanned prior to the end of the configured duration, the analyzer will restart at the beginning of the spectrum. Start Continuous Spectrum Analysis button ensures that when the SM is powered on, it automatically scans the spectrum for 10 seconds. These results may then be accessed via the Tools > Spectrum Analyzer GUI page. Spectrum Analyzer page of SM The Spectrum Analyzer page of SM is explained in Table 190. Page 8-5 Chapter 8: Tools Using Spectrum Analyzer tool Note Spectrum Analyzer is not currently supported by 450m. Table 190 Spectrum Analyzer page attributes - SM Attribute Display Data Path Data Display Min and Max Frequencies in KHz Meaning Refer Table 189 on page 8-4 Refer Table 189 on page 8-4 Refer Table 189 on page 8-4 To scan min to max range of frequencies, enter min and max frequencies in KHz and press Set Min and Max to Full Scan button. To scan +/- 40 MHz from center frequency, enter center frequency in KHz and press Set Min And Max To Center Scan +/- 40KHz button. Registered SM Count Refer Table 189 on page 8-4 Page 8-6 Chapter 8: Tools Using Spectrum Analyzer tool Refer Table 189 on page 8-4 Maximum Count to Registered SMs Duration Refer Table 189 on page 8-4 Spectrum Analyzer page of BHM The Spectrum Analyzer page of BHM is explained in Table 191. Table 191 Spectrum Analyzer page attributes - BHM Attribute Data Meaning Refer Table 189 on page 8-4 Page 8-7 Using Spectrum Analyzer tool Chapter 8: Tools Display Duration Continuous Spectrum Analyzer Refer Table 189 on page 8-4 Refer Table 189 on page 8-4 Refer Table 189 on page 8-4 Spectrum Analyzer page of BHS The Spectrum Analyzer page of BHS is explained in Table 192. Table 192 Spectrum Analyzer page attributes - BHS Attribute Meaning Page 8-8 Chapter 8: Tools Data Display Session Status Registered Backhaul Duration Perform Spectrum Analysis on Boot Up for one scan Continuous Spectrum Analyzer Using Spectrum Analyzer tool Refer Table 189 on page 8-4 Refer Table 189 on page 8-4 This field displays current session status and rates. The session states can be Scanning, Syncing, Registering or Registered. This field displays MAC address of BHM and PTP model number Refer Table 189 on page 8-4 This field allows to Enable or Disable to start Spectrum Analysis on boot up of module for one scan. Refer Table 189 on page 8-4 Page 8-9 Chapter 8: Tools Using Spectrum Analyzer tool Spectrum Analyzer page result of PMP 450 SM Figure 179 Spectrum Analyzer page result PMP 450 SM Page 8-10 Chapter 8: Tools Using Spectrum Analyzer tool Remote Spectrum Analyzer tool The Remote Spectrum Analyzer tool in the AP/BHM provides additional flexibility in the use of the spectrum analyzer in the SM/BHS. Set the duration of 10 to 1000 seconds, then click the Start Remote Spectrum Analysis button to launch the analysis from that SM/BHS. In PMP configuration, a SM has to be selected from the drop-down list before launching Start Remote Spectrum Analysis. Analyzing the spectrum remotely Procedure 31 Remote Spectrum Analyzer procedure 1 2 3 4 The AP/BHM de-registers the target SM/BHS. The SM/BHS scans (for the duration set in the AP/BHM tool) to collect data for the bar graph. The SM/BHS re-registers to the AP/BHM. The AP/BHM displays the bar graph. The bar graph is an HTML file, but can be changed to an XML file, which is then easy to analyze through the use of scripts that you may write for parsing the data. To transform the file to XML, click the SpectrumAnalysis.xml link below the spectrum results. Although the resulting display appears mostly unchanged, the bar graph is now coded in XML. You can now right-click on the bar graph for a Save Target As option to save the Spectrum Analysis.xml file. Remote Spectrum Analyzer page of AP The Remote Spectrum Analyzer page of AP is explained in Table 193. Page 8-11 Chapter 8: Tools Table 193 Remote Spectrum Analyzer attributes - AP Using Spectrum Analyzer tool Attribute Registered SM Count Maximum Count of Registered SMs Current Subscriber Module Duration Scanning Bandwidth Meaning This field displays the number of SMs that were registered to the AP before the SA was started. This helps the user know all the SMs re-registered after performing a SA. This field displays the largest number of SMs that have been simultaneously registered in the AP since it was last rebooted. This count can provide some insight into sector history and provide comparison between current and maximum SM counts at a glance. The SM with which the Link Capacity Test is run. This field allows operators to configure a specified time for which the spectrum is scanned. If the entire spectrum is scanned prior to the end of the configured duration, the analyzer will restart at the beginning of the spectrum. This parameter defines the size of the channel scanned when running the analyzer. Page 8-12 Chapter 8: Tools Using Spectrum Analyzer tool Remote Spectrum Analyzer page of BHM The Remote Spectrum Analyzer page of BHM is explained in Table 194. Table 194 Remote Spectrum Analyzer attributes - BHM Attribute Duration Meaning Refer Table 189 on page 8-4 Page 8-13 Chapter 8: Tools Using the Alignment Tool Using the Alignment Tool The SMs or BHSs Alignment Tool may be used to maximize Receive Power Level, Signal Strength Ratio and Signal to Noise Ratio to ensure a stable link. The Tool provides color coded readings to facilitate in judging link quality. Note To get best performance of the link, the user has to ensure the maximum Receive Power Level during alignment by pointing correctly. The proper alignment is important to prevent interference in other cells. The achieving Receive Power Level green (>- 70 dBm) is not sufficient for the link. Figure 180 Alignment Tool tab of SM Receive Power Level > -70 dBm Figure 181 Alignment Tool tab of SM Receive Power Level between -70 to -80 dBm Figure 182 Alignment Tool tab of SM Receive Power Level < -80 dBm Page 8-14 Chapter 8: Tools Using the Alignment Tool Aiming page and Diagnostic LED SM/BHS The SMs/BHSs Alignment Tool (located in GUI Tools -> Aiming) may be used to configure the SMs/BHSs LED panel to indicate received signal strength and to display decoded beacon information/power levels. The SM/BHS LEDs provide different status based on the mode of the SM/BHS. A SM/BHS in operating mode will register and pass traffic normally. A SM/BHS in aiming mode will not register or pass traffic, but will display (via LED panel) the strength of received radio signals (based on radio channel selected via Tools ->Aiming). See SM/BHS LEDs on page 2-17. Note In order for accurate power level readings to be displayed, traffic must be present on the radio link. Refer Table 23 SM/BHS LED descriptions on page 2-18 for SM/BHS LED details. Aiming page of SM The Aiming page is similar to Spectrum Analyzer where it scans the spectrum but it does not establish any session with any APs. It has two modes Single Frequency Only and Normal Frequency Scan List. The Aiming page of SM is explained in Table 195. Page 8-15 Chapter 8: Tools Table 195 Aiming page attributes SM Using the Alignment Tool Attribute Aiming Mode Single Frequency Scan Radio Frequency Only Mode Aiming Results Meaning Single Frequency Only: scans only selected single frequency. Normal Frequency Scan List: scans: scans all frequency of scan list. Select a particular frequency from drop down menu for scanning. Enabled: the radio is configured to aiming or alignment mode, wherein the LED panel displays an indication of receive power level. See Table 23 SM/BHS LED descriptions on page 2-18. Disabled: the radio is configured to operating mode, wherein the SM registers and passes traffic normally. The Aiming Results are displayed in two sections Current entry and Other entries. Frequency: this field indicates the frequency of the AP which is transmitting the beacon information. Page 8-16 Chapter 8: Tools Using the Alignment Tool Power: This field indicates the current receive power level (vertical channel) for the frequency configured in parameter Radio Frequency. Users: This field indicates the number of SMs currently registered to the AP which is transmitting the beacon information. ESN: This field indicates the MAC, or hardware address of the AP/BHM which is transmitting the beacon information. Color Code: This field displays a value from 0 to 254 indicating the APs configured color code. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Multipoint or Backhaul: this field indicates type of configuration - point-

Multipoint(PMP) or Backhaul (PTP). Page 8-17 Chapter 8: Tools Using the Alignment Tool Aiming page of BHS The Alignment page of BHS is explained in Table 196. Table 196 Aiming page attributes - BHS Attribute Refer Table 161 for Atributes details. Meaning Page 8-18 Chapter 8: Tools Using the Alignment Tool Alignment Tone For coarse alignment of the SM/BHS, use the Alignment Tool located at Tools -> Alignment Tool. Optionally, connect a headset alignment tone kit to the AUX/SYNC port of the SM/BHS and listen to the alignment tone, which indicates greater SM/BHS receive signal power by pitch. By adjusting the SMs/BHSs position until the highest frequency pitch is obtained operators and installers can be confident that the SM/BHS is properly positioned. For information on device GUI tools available for alignment, see sections Aiming page and Diagnostic LED SM/BHS on page 8-15, Using the Link Capacity Test tool on page 8-21 and Using AP Evaluation tool on page 8-31. Figure 183 PMP/PTP 450i Series link alignment tone 450i Alignment tone adapter Headphones Note The Alignment Tone cable for a 450i Series uses an RJ-45 to headset cable where as the 450 Series alignment tone cable uses an RJ-12 to headset cable. Alignment Tool Headset and alignment tone adapters can be ordered from Cambium and Best-Tronics

(http://btpa.com/Cambium-Products/) respectively using the following part numbers:

Page 8-19 Chapter 8: Tools Using the Alignment Tool Table 197 Alignment Tool Headsets and Alignment tone adapter third party product details Reference ACATHS-01A BT-1277 BT-0674 Product description Alignment tool headset for the PMP/PTP 450 and 450i Series products Headset alignment cable (RJ-45) for the PMP/PTP 450i Series products Headset alignment cable (RJ-12) for the PMP/PTP 450 Series products. Page 8-20 Chapter 8: Tools Using the Link Capacity Test tool Using the Link Capacity Test tool The Link Capacity Test tab allows you to measure the throughput and efficiency of the RF link between two modules. Many factors, including packet length, affect throughput. The Link Capacity Test tool has following modes:

Link Test with Multiple VCs: Tests radio-to-radio communication across selected or all registered VCs, but does not bridge traffic (PMP 450m Series AP only). Link Test without Bridging: Tests radio-to-radio communication, but does not bridge traffic. Link Test with Bridging: Bridges traffic to simulated Ethernet ports, providing a status of the bridged link. Link Test with Bridging and MIR: Bridges the traffic during test and also adheres to any MIR

(Maximum Information Rate) settings for the link. Extrapolated Link Test: Estimates the link capacity by sending few packets and measuring link quality. The Link Capacity Test tab contains the settable parameter Packet Length with a range of 64 to 1714 bytes. This allows you to compare throughput levels that result from various packet sizes. The Current Results Status also displayed date and time of last performed Link Capacity Test. If there is any change in time zone, the date and time will be adjusted accordingly. Note The Extrapolated Link Test can be run by Read-Only login also. Performing Link Test The link test is a tool that allows the user to test the performance of the RF link. Packets are added to one or more queues in the AP in order to fill the frame. Throughput and efficiency are then calculated during the test. The 450 and 450i APs offer link test options to one SM at a time. The 450m AP offers the option of a link test to multiple VCs at the same time. This allows the user to test throughput in MU-MIMO mode, in which multiple SMs are served at the same time. This new link test can be found under Tools > Link Capacity Test Page 8-21 Chapter 8: Tools Using the Link Capacity Test tool Link Test with Multiple VCs Note The Link Test with Multiple VCs Link Capacity Test is supported for PMP 450m Series AP only. Figure 184 Link Capacity Test PMP 450m Series AP Procedure 32 Performing a Link Capacity Test - Link Test with Multiple VCs Link Test Configurations parameters 1 2 Access the Link Capacity Test tab in the Tools web page of the module. Select Link Test Mode Options are: Link Test with Multiple VCs, Link Test without Bridging, Link Test with Bridging, Link Test with Bridging and MIR, Extrapolated Link Test All options except for the Link Test with Multiple VCs are available also for the 450 and 450i APs. Set the SM Link Test Mode Restriction attribute to enable or disable. Setting this to enabled, prevents activation of SM initated link tests. Set Signal to Noise Ratio Calculation during Link Test attribute to enable or disable. Set Link Test VC Priority attribute to either High and Low Priority VCs or Low Priority VC only. 3 4 5 Page 8-22 Chapter 8: Tools Using the Link Capacity Test tool 6 7 Select Flood Test Mode Options are: Internal and External Default is Internal. When set to Internal, packets are sent from AP -> SM over RF. When set to External, packets will all flow out the Ethernet port. Set MU-MIMO attribute to enable or disable . Note: The MU-MIMO feature is enabled on the Low Priority VC only Link Test Settings parameters 6 7 Select the subscriber module to test using the Current Subscriber Module parameter. Note:

This parameter is not available in BHM. Enter VC List (applicable for PMP 450m AP only) The Current Subscriber Module and VC List are valid only when selecting Link Test with Multiple VCs. Current Subscriber Module: select the VC to perform the link test with VC list: select a list or range of VCs to include in the link test with multiple VCs If left blank, all VCs will be included in the link test Type into the Duration field how long (in seconds) the RF link must be tested. Select the Direction Bi-directional, Uplink Only or Downlink Only. 8 9 10 Type into the Number of Packets field a value of 0 to flood the link for the duration of the test. 11 Type into the Packet Length field a value of 1714 to send 1714-byte packets during the test. 12 Click the Start Test button. Page 8-23 Chapter 8: Tools Figure 185 Link Test with Multiple VCs (1518-byte packet length) Using the Link Capacity Test tool Link Test without Bridging, Link Test with Bridging or Link Test with Bridging and MIR Figure 186 Link Capacity Test PMP 450/450i Series AP Page 8-24 Chapter 8: Tools Using the Link Capacity Test tool Refer Link Test with Multiple VCs on page 8-22 for Link Test procedure. Figure 187 Link Test without Bridging (1714-byte packet length) Page 8-25 Chapter 8: Tools Using the Link Capacity Test tool Performing Extrapolated Link Test The Extrapolated Link Test estimates the link capacity by sending few packets and measuring link quality. Once the test is initiated, the radio starts session at the lower modulation, 1X, as traffic is passed successfully across the link, the radio decides to try the next modulation, 2X. This process repeats until it find best throughput to estimate capacity of link. Note It is recommended to run Extrapolated Link Test where the session must have been up and have traffic present on it in order to get accurate test results. This is essential for the radio to modulate up to get an accurate measurement. Running the Extrapolated test just after establishing session will not provide accurate results. The procedure for performing Extrapolated Link Test is as follows:

Procedure 33 Performing an Extrapolated Link Test 1 Access the Link Capacity Test tab in the Tools web page of the module. 2 Select Link Test Mode Extrapolated Link Test 3 Click the Start Test button. 4 In the Current Results Status block of this tab, view the results of the test. Page 8-26 Chapter 8: Tools Figure 188 Extrapolated Link Test results Using the Link Capacity Test tool Page 8-27 Chapter 8: Tools Using the Link Capacity Test tool Link Capacity Test page of AP The Link Capacity Test page of AP is explained in Table 198. Table 198 Link Capacity Test page attributes AP Attribute Link Test Mode Meaning Select Link Test Mode from drop down menu :

Link Test with Multiple VCs (PMP 450m Series AP only) Link Test without Bridging Link Test with Bridging Link Test with Bridging and MIR Extrapolated Link Test Signal to Noise Ratio Calculation during Link Test Link Test VC Priority Flood Test Mode MU-MIMO Enable this attribute to display Signal-to-Noise information for the downlink and uplink when running the link test. This attribute may be used to enable/disable usage of the high and low priority virtual channel during the link test. This field determines whether a packet is sent out of the SMs Ethernet port

(external) or not (internal). Note: This field is applicable only when the Link Test Mode field is set to Link Test with Multiple VCs option. This field determines whether the DL flood test packets use MU-MIMO grouping or not. Page 8-28 Chapter 8: Tools Using the Link Capacity Test tool Display results for untested VCs Current Subscriber Module VC List Duration Direction Number of Packets Packet Length Note: This field is applicable only when the Link Test Mode field is set to Link Test with Multiple VCs option. If Link test with multiple VCs is run and a subset of registered VCs enters into the VC List field, then enabling this field produces a table that displays results for VCs with traffic which are in session; but not tested as part of the link test. The SM with which the Link Capacity Test is run. This field is only applicable for AP (not SM page). This field is displayed for PMP 450m Series AP. It is only applicable for Link Test with Multiple VCs Test mode. Enter VC List (e.g. 18 or above for low priority VCs and 255 or above for high priority VCs or 0 for all registered VCs) which needs to be used for link test traffic. This field allows operators to configure a specified time for which the spectrum is scanned. If the entire spectrum is scanned prior to the end of the configured duration, the analyzer will restart at the beginning of the spectrum. Configure the direction of the link test. Specify Downlink or Uplink to run the test only in the corresponding direction only. Specific Bi-Directional to run the test in both directions. The total number of packets to send during the Link Capacity Test. When Link Test Mode is set to RF Link Test this field is not configurable. The size of the packets in Bytes to send during the Link Capacity Test Link Capacity Test page of BHM/BHS/SM The Link Capacity Test page of BHM/BHS is explained in Table 199. Page 8-29 Chapter 8: Tools Table 199 Link Capacity Test page attributes BHM/BHS Using the Link Capacity Test tool Attribute Link Test Mode Signal to Noise Ratio Calculation during Link Test Link Test VC Priority Duration Direction Number of Packets Packet Length Meaning See Table 198 on page 8-28 See Table 198 on page 8-28 See Table 198 on page 8-28 See Table 198 on page 8-28 See Table 198 on page 8-28 See Table 198 on page 8-28 See Table 198 on page 8-28 Page 8-30 Chapter 8: Tools Using AP Evaluation tool Using AP Evaluation tool The AP Evaluation tab on Tools web page of the SM provides information about the AP that the SM sees. Note The data for this page may be suppressed by the SM Display of AP Evaluation Data setting in the Configuration > Security tab of the AP. The AP Eval results can be accessed via SNMP and config file. AP Evaluation page The AP Evaluation page of AP is explained in Table 200. Table 200 AP Evaluation tab attributes - AP Attribute Index Frequency Channel Bandwidth Meaning This field displays the index value that the system assigns (for only this page) to the AP where this SM is registered. This field displays the frequency that the AP transmits. The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the AP and the SM. Page 8-31 Chapter 8: Tools Cyclic Prefix ESN Region Power Level Beacon Count FECEn Type Age Lockout RegFail Range MaxRange TxBER Ebcast Session Count Using AP Evaluation tool OFDM technology uses a cyclic prefix, where a portion of the end of a symbol

(slot) is repeated at the beginning of the symbol to allow multi-pathing to settle before receiving the desired data. A 1/16 cyclic prefixes mean that for every 16 bits of throughput data transmitted, an additional bit is used. The Cyclic Prefix 1/16 only can be selected at this time. This field displays the MAC address (electronic serial number) of the AP. For operator convenience during SM aiming, this tab retains each detected ESN for up to 15 minutes. If the broadcast frequency of a detected AP changes during a 15-minute interval in the aiming operation, then a multiple instance of the same ESN is possible in the list. Eventually, the earlier instance expires and disappears and the later instance remains to the end of its interval, but you can ignore the early instance(s) whenever two or more are present. This field displays the APs configured Country Code setting. This field displays the SMs combined received power level from the APs transmission. A count of the beacons seen in a given time period. This field contains the SNMP value from the AP that indicates whether the Forward Error Correction feature is enabled. 0: FEC is disabled 1: FEC is enabled Multipoint indicates that the listing is for an AP. This is a counter for the number of minutes that the AP has been inactive. At 15 minutes of inactivity for the AP, this field is removed from the AP Evaluation tab in the SM. This field displays how many times the SM has been temporarily locked out of making registration attempts. This field displays how many registration attempts by this SM failed. This field displays the distance in feet for this link. To derive the distance in meters, multiply the value of this parameter by 0.3048. This field indicates the configured value for the APs Max Range parameter. A 1 in this field indicates the AP is sending Radio BER. A 1 in this field indicates the AP or BHM is encrypting broadcast packets. A 0 indicates it is not. This field displays how many sessions the SM (or BHS) has had with the AP

(or BHM). Typically, this is the sum of Reg Count and Re-Reg Count. However, the result of internal calculation may display here as a value that slightly differs from the sum. Page 8-32 Chapter 8: Tools NoLUIDs OutOfRange AuthFail EncryptFail Rescan Req SMLimitReached NoVCs VCRsvFail VCActFail AP Gain RcvT Sector ID Color Code Using AP Evaluation tool In the case of a multipoint link, if the number of sessions is significantly greater than the number for other SMs, then this may indicate a link problem or an interference problem. This field indicates how many times the AP has needed to reject a registration request from a SM because its capacity to make LUID assignments is full. This then locks the SM out of making any valid attempt for the next 15 minutes. It is extremely unlikely that a non-zero number would be displayed here. This field indicates how many times the AP has rejected a registration request from a SM because the SM is a further distance away than the range that is currently configured in the AP. This then locks the SM out of making any valid attempt for the next 15 minutes. This field displays how many times authentication attempts from this SM have failed in the AP. This field displays how many times an encryption mismatch has occurred between the SM and the AP. This field displays how many times a re-range request has occurred for the BHM that is being evaluated in the AP Eval page of a BHS. This field displays 0 if additional SMs may be registered to the AP. If a 1 is displayed, the AP will not accept additional SM registrations. This counter is incremented when the SM is registering to an AP which determines that no VC resources are available for allocation. This could be a primary data VC or a high priority data VC. This counter is incremented when the SM is registering to an AP which has a VC resource available for allocation but cannot reserve the resource for allocation. This counter is incremented when the SM is registering to an AP which has a VC resource available for allocation and has reserved the VC, but cannot activate the resource for allocation. This field displays the total external gain (antenna) used by the AP. This field displays the APs configured receive target for receiving SM transmissions (this field affects automatic SM power adjust). This field displays the value of the Sector ID field that is provisioned for the AP. This field displays a value from 0 to 254 indicating the APs configured color code. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Page 8-33 Chapter 8: Tools Using AP Evaluation tool BeaconVersion Sector User Count NumULHalfSlots NumDLHalfSlots NumULContSlots WhiteSched ICC SM PPPoE Frame Period Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). This field indicates that the beacon is OFDM (value of 1). This field displays how many SMs are registered on the AP. This is the number of uplink slots in the frame for this AP. This is the number of downlink slots in the frame for this. This field displays how many Contention Slots are being used in the uplink portion of the frame. Flag to display if schedule whitening is supported via FPGA This field lists the SMs that have registered to the AP with their Installation Color Code (ICC), Primary CC, Secondary CC or Tertiary CC. This filed provides information to the user whether the SM is supporting PPPoE or not. This field displays the configured Frame Period of the radio. Page 8-34 Chapter 8: Tools Using BHM Evaluation tool Using BHM Evaluation tool The BHM Evaluation tab on Tools web page of the BHS provides information about the BHM that the BHS sees. BHM Evaluation page of BHS The BHM Evaluation page of BHS is explained in Table 201. Table 201 BHM Evaluation tab attributes - BHS Attribute Index Frequency Channel Bandwidth Cyclic Prefix Meaning This field displays the index value that the system assigns (for only this page) to the BHM where this BHS is registered. This field displays the frequency that the BHM transmits. The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the BHM and the BHS. OFDM technology uses a cyclic prefix, where a portion of the end of a symbol

(slot) is repeated at the beginning of the symbol to allow multi-pathing to settle before receiving the desired data. A 1/16 cyclic prefixes mean that for every 16 bits of throughput data transmitted, an additional bit is used. Page 8-35 Chapter 8: Tools ESN Region Power Level Beacon Count FECEn Type Age Lockout RegFail Range MaxRange TxBER Ebcast Session Count Using BHM Evaluation tool This field displays the MAC address (electronic serial number) of the BHM. For operator convenience during BHS aiming, this tab retains each detected ESN for up to 15 minutes. If the broadcast frequency of a detected BHM changes during a 15-minute interval in the aiming operation, then a multiple instance of the same ESN is possible in the list. Eventually, the earlier instance expires and disappears and the later instance remains to the end of its interval, but you can ignore the early instance(s) whenever two or more are present. This field displays the BHMs configured Country Code setting. This field displays the BHSs combined received power level from the BHMs transmission. A count of the beacons seen in a given time period. This field contains the SNMP value from the BHM that indicates whether the Forward Error Correction feature is enabled. 0: FEC is disabled 1: FEC is enabled Multipoint indicates that the listing is for a BHM. This is a counter for the number of minutes that the BHM has been inactive. At 15 minutes of inactivity for the BHS, this field is removed from the BHM Evaluation tab in the BHS. This field displays how many times the BHS has been temporarily locked out of making registration attempts. This field displays how many registration attempts by this BHS failed. This field displays the distance in feet for this link. To derive the distance in meters, multiply the value of this parameter by 0.3048. This field indicates the configured value for the APs Max Range parameter. A 1 in this field indicates the BHM is sending Radio BER. A 1 in this field indicates the BHM is encrypting broadcast packets. A 0 indicates it is not. This field displays how many sessions the BHS has had with the BHM. Typically, this is the sum of Reg Count and Re-Reg Count. However, the result of internal calculation may display here as a value that slightly differs from the sum. In the case of a multipoint link, if the number of sessions is significantly greater than the number for other BHSs, then this may indicate a link problem or an interference problem. Page 8-36 Chapter 8: Tools NoLUIDs OutOfRange AuthFail EncryptFail Rescan Req Using BHM Evaluation tool This field indicates how many times the BHM has needed to reject a registration request from a BHS because its capacity to make LUID assignments is full. This then locks the BHS out of making any valid attempt for the next 15 minutes. It is extremely unlikely that a non-zero number would be displayed here. This field indicates how many times the BHM has rejected a registration request from a BHS because the BHS is a further distance away than the range that is currently configured in the BHM. This then locks the BHS out of making any valid attempt for the next 15 minutes. This field displays how many times authentication attempts from this SM have failed in the BHM. This field displays how many times an encryption mismatch has occurred between the BHS and the BHM. This field displays how many times a re-range request has occurred for the BHM that is being evaluated in the BHM Eval page of a BHM. SMLimitReached This field displays 0 if additional BHSs may be registered to the BHM. If a 1 is displayed, the BHM will not accept additional BHS registrations. NoVCs VCRsvFail VCActFail AP Gain RcvT Sector ID Color Code This counter is incremented when the BHS is registering to a BHM which determines that no VC resources are available for allocation. This could be a primary data VC or a high priority data VC. This counter is incremented when the BHS is registering to a BHM which has a VC resource available for allocation but cannot reserve the resource for allocation. This counter is incremented when the BHS is registering to a BHM which has a VC resource available for allocation and has reserved the VC, but cannot activate the resource for allocation. This field displays the total external gain (antenna) used by the BHM. This field displays the APs configured receive target for receiving BHS transmissions (this field affects automatic BHS power adjust). This field displays the value of the Sector ID field that is provisioned for the BHM. This field displays a value from 0 to 254 indicating the BHMs configured color code. For registration to occur, the color code of the BHS and the BHM must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a BHS to register to only a specific BHM, even where the BHS can communicate with multiple BHMs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Page 8-37 Chapter 8: Tools Using BHM Evaluation tool BeaconVersion This field indicates that the beacon is OFDM (value of 1). Sector User Count NumULHalfSlots NumDLHalfSlots NumULContSlots WhiteSched ICC SM PPPoE This field displays how many BHSs are registered on the BHM. This is the number of uplink slots in the frame for this BHM. This is the number of downlink slots in the frame for this. This field displays how many Contention Slots are being used in the uplink portion of the frame. Flag to display if schedule whitening is supported via FPGA This field lists the BHSs that have registered to the BHM with their Installation Color Code (ICC), Primary CC, Secondary CC or Tertiary CC. This filed provides information to the user whether the BHS is supporting PPPoE or not. Frame Period This field displays the configured Frame Period of the radio. Page 8-38 Chapter 8: Tools Using the OFDM Frame Calculator tool Using the OFDM Frame Calculator tool The first step to avoid interference in wireless systems is to set all APs/BHMs to receive timing from a synchronization source (Cluster Management Module, or Universal Global Positioning System). This ensures that the modules are in sync and start transmitting at the same time each frame. The second step to avoid interference is to configure parameters on all APs/BHMs of the same frequency band in proximity such that they have compatible transmit/receive ratios (all stop transmitting each frame before any start receiving). This avoids the problem of one AP/BHM attempting to receive the signal from a distant SM/BHS while a nearby AP transmits, which could overpower that signal. The following parameters on the AP determine the transmit/receive ratio:

Max Range Frame Period Downlink Data percentage

(reserved) Contention Slots If OFDM (PMP 430, PMP 450, PTP 230) and FSK (PMP 1x0) APs/BHMs of the same frequency band are in proximity, or if APs/BHMs set to different parameters (differing in their Max Range values, for example), then operator must use the Frame Calculator to identify compatible settings. The frame calculator is available on the Frame Calculator tab of the Tools web page. To use the Frame Calculator, type various configurable parameter values into the calculator for each proximal AP and then record the resulting AP/BHM Receive Start value. Next vary the Downlink Data percentage in each calculation and iterate until the calculated AP/BHM Receive Start for all collocated AP/BHMs where the transmit end does not come before the receive start. The calculator does not use values in the module or populate its parameters. It is merely a convenience application that runs on a module. For this reason, you can use any FSK module (AP, SM, BHM, BHS) to perform FSK frame calculations for setting the parameters on an FSK AP and any OFDM module (AP, SM, BHM, BHS) to perform OFDM frame calculations for setting the parameters on an OFDM AP/BHM. For more information on PMP/PTP 450 Platform co-location, see http://www.cambiumnetworks.com/solution-papers The co-location is also supported for 900 MHz PMP 450i APs (OFDM) and PMP 100 APs (FSK). Please refer Co-location of PMP 450 and PMP 100 systems in the 900 MHz band and migration recommendations document for details. Caution APs/BHMs that have slightly mismatched transmit-to-receive ratios and low levels of data traffic may see little effect on throughput. A system that was not tuned for co-location may work fine at low traffic levels, but encounter problems at higher traffic levels. The conservative practice is to tune for co-location before traffic ultimately increases. This prevents problems that occur as sectors are built. The OFDM Frame Calculator page is explained in Table 202. Page 8-39 Chapter 8: Tools Table 202 OFDM Frame Calculator page attributes Using the OFDM Frame Calculator tool Attribute Link Mode Platform Type AP/BHM Platform Type SM/BHS Meaning For AP to SM frame calculations, select Multipoint Link For BHM to BHS frame calculations, select Point-To-Point Link Use the drop-down list to select the hardware series (board type) of the AP/BHM. Use the drop-down list to select the hardware series (board type) of the SM/BHS. Channel Bandwidth Cyclic Prefix Max Range Set this to the channel bandwidth used in the AP/BHM. Set this to the cyclic prefix used in the AP/BHM. Set to the same value as the Max Range parameter is set in the AP(s) or BHM(s). Page 8-40 Chapter 8: Tools Frame Period Downlink Data Contention Slots SM/BHS One Way Air Delay Using the OFDM Frame Calculator tool Set to the same value as the Frame Period parameter is set in the AP(s) or BHM(s). Initially set this parameter to the same value that the AP/BHM has for its Downlink Data parameter (percentage). Then, use the Frame Calculator tool procedure as described in Using the Frame Calculator on page 8-42, you will vary the value in this parameter to find the proper value to write into the Downlink Data parameter of all APs or BHMs in the cluster. PMP 450 Platform Family APs or BHMs offer a range of 15% to 85% and default to 75%. The value that you set in this parameter has the following interaction with the value of the Max Range parameter (above):

The default Max Range value is 5 miles and, at that distance, the maximum Downlink Data value (85% in PMP 450 Platform) is functional. This field indicates the number of (reserved) Contention Slots configured by the operator. Set this parameter to the value of the Contention Slot parameter is set in the APs or BHMs. This field displays the time in ns (nano seconds), that a SM/BHS is away from the AP/BHM. The Calculated Frame Results display several items of interest:

Table 203 OFDM Calculated Frame Results attributes Attribute Modulation Meaning The type of radio modulation used in the calculation (OFDM for 450 Platform Family) The total number of bits used in the calculated frames Total Frame Bits Data Slots (Down/Up) This field is based on the Downlink Data setting. For example, a result within the typical range for a Downlink Data setting of 75% is 61/21, meaning 61 data slots down and 21 data slots up. Contention Slots Air Delay for Max Range Approximate distance for Max Range AP Transmit End AP Receive Start This field indicates the number of (reserved) Contention Slots configured by the operator. This is the roundtrip air delay in bit times for the Max Range value set in the calculator The Max Range value used for frame calculation In bit times, this is the frame position at which the AP/BHM ceases transmission. In bit times, this is the frame position at which the AP/BHM is ready to receive transmission from the SM/BHS. Page 8-41 Chapter 8: Tools AP Receive End SM Receive End SM Transmit Start SM One Way Air Delay SM Approximate distance Using the OFDM Frame Calculator tool In bit times, this is the frame position at which the AP/BHM will cease receiving transmission from the SM/BHS. In bit times, this is the frame position at which the SM/BHS will cease receiving transmission from the AP/BHM. In bit times, this is the frame position at which the SM/BHS starts the transmission. This filed displays the time in ns, that SM/BHS is away from the AP/BHM. This field displays an approximate distance in miles (feet) that the SM/BHS is away from the AP/BHM. To use the Frame Calculator to ensure that all APs or BHMs are configured to transmit and receive at the same time, follow the procedure below:

Procedure 34 Using the Frame Calculator 1 Populate the OFDM Frame Calculator parameters with appropriate values as described above. Scroll down the tab to the Calculated Frame Results section 2 Click the Calculate button. 3 4 Record the value of the AP Receive Start field 5 Enter a parameter set from another AP in the system for example, an AP in the same cluster that has a higher Max Range value configured. 6 Click the Calculate button. 7 8 Scroll down the tab to the Calculated Frame Results section If the recorded values of the AP Receive Start fields are within 150 bit times of each other, skip to step 10. If the recorded values of the AP Receive Start fields are not within 150 bit times of each other, modify the Downlink Data parameter until the calculated results for AP Receive Start are within 300 bit time of each other, if possible, 150 bit time. 10 Access the Radio tab in the Configuration web page of each AP in the cluster and change its Downlink Data parameter (percentage) to the last value that was used in the Frame Calculator. Page 8-42 Chapter 8: Tools Using the Subscriber Configuration tool Using the Subscriber Configuration tool The Subscriber Configuration page in the Tools page of the AP displays:

The current values whose control may be subject to the setting in the Configuration Source parameter. An indicator of the source for each value. This page may be referenced for information on how the link is behaving based on where the SM is retrieving certain QoS and VLAN parameters. Figure 189 SM Configuration page of AP The AP displays one of the following for the configuration source:

(SM) QoS/VLAN parameters are derived from the SMs settings

(APCAP) QoS/VLAN parameters are derived from the APs settings, including any keyed capping

(for radios capped at 4 Mbps, 10 Mbps, or 20 Mbps)

(D) QoS/VLAN parameters are retrieved from the device, due to failed retrieval from the AAA or WM server.

(AAA) QoS/VLAN parameters are retrieved from the RADIUS server

(BAM) QoS/VLAN parameters are retrieved from a WM BAM server Page 8-43 Chapter 8: Tools Using the Link Status tool Using the Link Status tool The Link Status Tool displays information about the most-recent Link Test initiated on the SM or BHS. Link Tests initiated from the AP or BHM are not included in the Link Status table. This table is useful for monitoring link test results for all SMs or BHS in the system. The Link Status table is color coded to display health of link between AP/BHM and SM/BHS. The current Modulation Level Uplink/Downlink is chosen to determine link health and color coded accordingly. Uplink/Downlink Rate Column will be color coded using current Rate as per the table below:

Table 204 Color code versus uplink/downlink rate column Actual Rate 1x 2x 3x 4x ORANGE GREEN BLUE ORANGE GREEN BLUE 6x NA NA 8x NA NA RED NA ORANGE GREEN BLUE SISO MIMO-A MIMO B RED RED NA Link Status AP/BHM The current Uplink Rate (both low and high VC) for each SM or BHS in Session in now available on AP or BHM Link Status Page. The Link Status tool results include values for the following fields for AP/BHM. Page 8-44 Chapter 8: Tools Table 205 Link Status page attributes AP/BHM Using the Link Status tool Attribute Subscriber Meaning This field displays the LUID (logical unit ID), MAC address and Site Name of the SM. As each SM registers to the AP, the system assigns an LUID of 2 or a higher unique number to the SM. If a SM loses registration with the AP and then regains registration, the SM will retain the same LUID. Note The LUID associated is lost when a power cycle of the AP occurs. Both the LUID and the MAC are hot links to open the interface to the SM. In some instances, depending on network activity and network design, this route to the interface yields a blank web page. If this occurs, refresh your browser view. Site Name indicates the name of the SM. You can assign or change this name on the Configuration web page of the SM. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Uplink Statistics -

Power Level: Signal Strength Ratio This field represents the combined received power level at the AP/BHM as well as the ratio of horizontal path signal strength to vertical path signal strength. Uplink Statistics Fragments Modulation This field represents the percentage of fragments received at each modulation state, per path (polarization). Page 8-45 Chapter 8: Tools Using the Link Status tool Uplink Statistics Signal to Noise Ratio This field represents the signal to noise ratio for the uplink (displayed when parameter Signal to Noise Ratio Calculation during Link Test is enabled) expressed for both the horizontal and vertical channels. Uplink Statistics Link Test Efficiency This field displays the efficiency of the radio link, expressed as a percentage, for the radio uplink. Downlink Statistics Beacon % Received Curr/Min/Max/Avg This field displays a count of beacons received by the SM in percentage. This value must be between 99-100%. If it is lower than 99%, it indicates a problematic link. This statistic is updated every 16 seconds. Downlink Statistics Power Level: Signal Strength Ratio Downlink Statistics Signal to Noise Ratio Downlink Statistics Link Test Efficiency Downlink Statistics SU-MIMO Rate Downlink Statistics MU-MIMO Rate BER Results Reg Requests This field represents the received power level at the SM/BHS as well as the ratio of horizontal path signal strength to vertical path signal strength at the SM/BHS. This field represents the signal to noise ratio for the downlink (displayed when parameter Signal to Noise Ratio Calculation during Link Test is enabled) expressed for both the horizontal and vertical channels. This field displays the efficiency of the radio link, expressed as a percentage, for the radio downlink. The SU-MIMO rate applies to all AP platforms. For 450m, this field indicates the rate being used for symbols where this particular VC is not being MU-MIMO grouped with other SMs. For 450 and 450i platforms, there is no grouping and this field indicates the modulation rate for all symbols. The MU-MIMO rate applies only to the 450m AP. This field indicates the modulation rate used for symbols where this particular low priority VC is MU-

MIMO scheduled by grouping it in the same slot with other low priority VCs. This field displays the over-the-air Bit Error Rates for each downlink. (The ARQ [Automatic Resend 8-46equest] ensures that the transport BER [the BER seen end-to-end through a network] is essentially zero.) The level of acceptable over-the-air BER varies, based on operating requirements, but a reasonable value for a good link is a BER of 1e-4 (1 x 10-4) or better, approximately a packet resend rate of 5%. BER is generated using unused bits in the downlink. During periods of peak load, BER data is not updated as often, because the system puts priority on transport rather than on BER calculation. A Reg Requests count is the number of times the SM/BHS registered after the AP/BHM determined that the link had been down. If the number of sessions is significantly greater than the number for other SMs/BHS, then this may indicate a link problem (check mounting, alignment, receive power levels) or an interference problem (conduct a spectrum scan). Page 8-46 Chapter 8: Tools ReReg Requests Using the Link Status tool A ReReg Requests count is the number of times the AP/BHM received a SM/BHS registration request while the AP/BHM considered the link to be still up (and therefore did not expect registration requests). If the number of sessions is significantly greater than the number for other SMs/BHS, then this may indicate a link problem (check mounting, alignment, receive power levels) or an interference problem (conduct a spectrum scan). Link Status SM/BHS The Link Status tool of SM/BHS displays Downlink Status and Uplink Status information. Table 206 Link Status page attributes SM/BHS Attribute Downlink Status Receive Power Signal Strength Ratio Signal to Noise Ratio Meaning This field lists the current combined receive power level, in dBm. This field displays the difference of the Vertical path received signal power to the Horizontal path received signal power for downlink. This field lists the current signal-to-noise level, an indication of the separation of the received power level vs. noise floor for downlink. Page 8-47 Chapter 8: Tools Beacons Using the Link Status tool Displays a count of beacons received by the SM in percentage. This value must be typically between 99-100%. If lower than 99%, it indicates a problematic link. This statistic is updated every 16 seconds. Received Fragments Modulation This field represents the percentage of fragments received at each modulation state, per path (polarization) Latest Remote Link Test Efficiency Percentage BER Total Avg Results Beacons Received Last 15 minutes Uplink Status Transmit Power Max Transmit Power Power Level Signal Strength Ratio Signal to Noise Ratio Latest Remote Link Test Efficiency Percentage Session Status Spatial Frequency Run Link Test This field is not applicable. This field displays the over-the-air average Bit Error Rates (BER) for downlink. The beacon count on the SM can be used to estimate the interference in the channel. The min/avg/max beacon percentage displayed based on this value for the last 15 mins. This field displays the current combined transmit power level, in dBm. This field displays the maximum transmit power of SM. This field indicates the combined power level at which the SM is set to transmit, based on the Country Code and Antenna Gain settings. This field displays the difference of the Vertical path received signal power to the Horizontal path received signal power for uplink. This field lists the current signal-to-noise level, an indication of the separation of the received power level vs. noise floor for uplink. This field is not applicable. This field displays the current state, Virtual channel, high-priority/ low priority channel rate adaptation and MIMO-A/MIMO-B/SISO status of SM. This filed displays the spatial frequency value of the VC or SM. See Exploratory Test section of Performing Extrapolated Link Test on page 8-

26 Page 8-48 Chapter 8: Tools Using BER Results tool Using BER Results tool Radio BER data represents bit errors at the RF link level. Due to CRC checks on fragments and packets and ARQ (Automatic Repeat 8-49equest), the BER of customer data is essentially zero. Radio BER gives one indication of link quality. Other important indications to consider includes the received power level, signal to noise ratio and link tests. BER is only instrumented on the downlink and is displayed on the BER Results tab of the Tools page in any SM. Each time the tab is clicked, the current results are read and counters are reset to zero. The BER Results tab can be helpful in troubleshooting poor link performance. The link is acceptable if the value of this field is less than 104. If the BER is greater than 104, re-evaluate the installation of both modules in the link. The BER test signal is broadcast by the AP/BHM (and compared to the expected test signal by the SM/BHS) only when capacity in the sector allows it. This signal is the lowest priority for AP/BHM transmissions. Figure 190 BER Results tab of the SM Page 8-49 Chapter 8: Tools Using the Sessions tool Using the Sessions tool The PMP 450 Platform Family AP has a tab Sessions under the Tools category which allows operators to drop one or all selected SM sessions and force a SM re-registration. This operation is useful to force QoS changes for SMs without losing AP logs or statistics. This operation may take 5 minutes to regain all SM registrations. Figure 191 Sessions tab of the AP Page 8-50 Chapter 8: Tools Using the Ping Test tool Using the Ping Test tool The PMP 450 Platform Family AP has a tab Ping Test under the Tools category which allows users to check the accessibility of the given IP V4 address or a valid domain name Figure 192 Ping Test tab of the AP Note When a domain name (for example, www.google.com) is used for ping test, make sure that Preferred DNS Server and Alternate DNS Server parameters are configured in the Configuration > IP tab of the AP. Page 8-51 Chapter 9: Operation This chapter provides instructions for operators of the 450 Platform Family wireless Ethernet Bridge. The following topics are described in this chapter:

System information on page 9-2 o Viewing General Status on page 9-2 o Viewing Session Status on page 9-20 o Viewing Remote Subscribers on page 9-29 o o Viewing the Network Interface on page 9-32 o Viewing the Layer 2 Neighbors on page 9-32 Interpreting messages in the Event Log on page 9-29 System statistics on page 9-33 Interpreting Bridging Table statistics on page 9-37 Interpreting Translation Table statistics on page 9-37 Interpreting Ethernet statistics on page 9-38 Interpreting RF Control Block statistics on page 9-41 Interpreting VLAN statistics on page 9-2 Interpreting Data VC statistics on page 9-4 Interpreting Throughput statistics on page 9-6 Interpreting Overload statistics on page 9-9 Interpreting DHCP Relay statistics on page 9-10 Interpreting Filter statistics on page 9-12 o Viewing the Scheduler statistics on page 9-33 o Viewing list of Registration Failures statistics on page 9-35 o o o o o o o o o o o Viewing ARP statistics on page 9-13 o Viewing NAT statistics on page 9-13 o Viewing NAT DHCP Statistics on page 9-15 o o o o o o o Interpreting Sync Status statistics on page 9-16 Interpreting PPPoE Statistics for Customer Activities on page 9-17 Interpreting Bridge Control Block statistics on page 9-19 Interpreting Pass Through Statistics on page 9-22 Interpreting SNMPv3 Statistics on page 9-23 Interpreting syslog statistics on page 9-25 Interpreting Frame Utilization statistics on page 9-25 Radio Recovery on page 9-36 Page 9-1 Chapter 9: Operation System information System information This section describes how to use the summary and status pages to monitor the status of the Ethernet ports and wireless link. Viewing General Status on page 9-2 Viewing Session Status on page 9-20 Viewing Remote Subscribers on page 9-29 Viewing the Network Interface on page 9-32 Viewing the Layer 2 Neighbors on page 9-32 Interpreting messages in the Event Log on page 9-29 Viewing General Status The General Status tab provides information on the operation of this AP/BHM and SM/BHS. This is the page that opens by default when you access the GUI of the radio. Page 9-2 Chapter 9: Operation System information General Status page of AP The General Status page of PMP 450m AP is explained in Table 207 The General Status page of PMP 450/450i AP is explained in Table 208. Table 207 General Status page attributes PMP 450m AP Page 9-3 Chapter 9: Operation System information Attribute Device Type Board Type Software Version Bootloader Version Product Type Board MSN FPGA Version Uptime System Time Last NTP Time Update Main Ethernet Interface Meaning This field indicates the type of the module. Values include the frequency band of the device, its module type and its MAC address. This field indicates the series of hardware. This field indicates the system release, the time and date of the release and whether communications involving the module are secured by DES or AES encryption. If you request technical support, provide the information from this field. This field indicates the version of Uboot running on the 450m AP platform. The field indicates model number of 450m device. The 450m Series has two model variants. PMP 450m: This model works in SU-MIMO mode which is default limited mode. The MU-MIMO license can be purchased from Cambium Networks and applied. MU-MIMO: This model works in MU-MIMO mode. This field indicates the Manufactures Serial number. A unique serial number assigned to each radio at the factory for inventory and quality control. This field indicates the version of the field-programmable gate array (FPGA) on the module. If you request technical support, provide the value of this field. This field indicates how long the module has operated since power was applied. This field provides the current time. If the AP is connected to a CMM4, then this field provides GMT (Greenwich Mean Time). Any SM that registers to the AP inherits the system time. This field displays when the AP last used time sent from an NTP server. If the AP has not been configured in the Time tab of the Configuration page to request time from an NTP server, then this field is populated by 00:00:00 00/00/00. This field indicates the speed and duplex state of the Ethernet interface to the AP. Page 9-4 Chapter 9: Operation System information Aux Ethernet Interface This field displays Aux Ethernet Data and PoE-out interface enable/disable Region Code Regulatory Channel Frequency Channel Bandwidth Cyclic Prefix Frame Period Color Code Max Range EIRP Temperature status. It is not supported in current release of PMP 450m Seriea AP. A parameter that offers multiple fixed selections, each of which automatically implements frequency band range for the selected region. Units shipped to regions other than restrictions the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. This field indicates whether the configured Country Code and radio frequency are compliant with respect to their compatibility. 450 Platform Family products shipped to the United States is locked to a Country Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Country Code to comply with local regulatory requirements. This field indicates the current operating center frequency, in MHz. This field indicates the current size of the channel band used for radio transmission. OFDM technology uses a cyclic prefix, where a portion of the end of a symbol

(slot) is repeated at the beginning of the symbol to allow multi-pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. This field indicates the current Frame Period setting of the radio in ms. This field displays a value from 0 to 254 indicating the APs configured color code. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). This field indicates the setting of the Max Range parameter, which contributes to the way the radio transmits. Verify that the Max Range parameter is set to a distance slightly greater than the distance between the AP and the furthest SM that must register to this AP. This field indicates the combined power level at which the AP will transmit, based on the Country Code. This field indicates the current operating temperature of the device board. Registered SM Count Sync Pulse Status This field indicates how many SMs are registered to the AP. This field indicates the status of synchronization as follows:

Generating Sync indicates that the module is set to generate the sync pulse. Page 9-5 Chapter 9: Operation System information Receiving Sync indicates that the module is set to receive a sync pulse from an outside source and is receiving the pulse. No Sync Since Boot up / ERROR: No Sync Pulse indicates that the module is set to receive a sync pulse from an outside source and is not receiving the pulse. Note When this message is displayed, the AP transmitter is turned off to avoid self-interference within the system. This field indicates the status of the synchronization source:

Searching indicates that the unit is searching for a GPS fix Timing Port/UGPS indicates that the module is receiving sync via the timing AUX/SYNC timing port Power Port indicates that the module is receiving sync via the power port

(Ethernet port). On-board GPS indicates that the module is receiving sync via the units internal GPS module This field displays the largest number of SMs that have been simultaneously registered in the AP since it was last rebooted. This count can provide some insight into sector history and provide comparison between current and maximum SM counts at a glance. This field indicates the number of frame slots that are designated for use by data traffic in the downlink (sent from the AP to the SM). The AP calculates the number of data slots based on the Max Range, Downlink Data and

(reserved) Contention Slots configured by the operator. This field indicates the number of frame slots that are designated for use by data traffic in the uplink (sent from the SM to the AP). The AP calculates the number of data slots based on the Max Range, Downlink Data and (reserved) Contention Slots configured by the operator. This field indicates the number of (reserved) Contention Slots configured by the operator. See Contention slots on page7-176. This field indicates the device connectivity to cnMaestro (Cambiums cloud-

based network management system). This field shows Account ID which is registered with Cambium Networks and it allows operator to manage devices using cnMaestro. This field indicates the name of the physical module. You can assign or change this name in the SNMP tab of the AP Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Sync Pulse Source Maximum Count of Registered SMs Data Slots Down Data Slots Up Contention Slots Connection Status Account ID Site Name Page 9-6 Chapter 9: Operation Site Contact Site Location MU-MIMO Mode Time Updated and Location Code System information This field indicates contact information for the physical module. You can provide or change this information in the SNMP tab of the AP Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. This field indicates site information for the physical module. You can provide or change this information in the SNMP tab of the AP Configuration page. This field displays information about MU-MIMO mode. If AP is keyed as MU-

MIMO, it will display MU-MIMO(Multi User - MIMO) otherwise it will display SU-MIMO(Single User - MIMO). This field displays information about the keying of the radio. Page 9-7 Chapter 9: Operation Table 208 General Status page attributes PMP 450/450i AP System information Attribute Device Type Software Version Board Type Meaning See Table 207 General Status page attributes PMP 450m AP on page 9-3 for details See Table 207 General Status page attributes PMP 450m AP on page 9-3 for details Page 9-8 System information This indicates model of the device. See Table 207 General Status page attributes PMP 450m AP on page 9-3 for details It is not supported for PMP 450 Series devices. See Table 207 General Status page attributes PMP 450m AP on page 9-3 for details See Table 207 General Status page attributes PMP 450m AP on page 9-3 for details Chapter 9: Operation Product Type FPGA Version PLD Version Uptime System Time Main Ethernet Interface Aux Ethernet Interface Region Code Regulatory Antenna Type Channel Center Frequency Channel Bandwidth Cyclic Prefix Frame Period Color Code Max Range Transmitter Output Power Temperature 802.3at Type 2 PoE Status This field indicates the combined power level at which the AP is set to transmit, based on the Country Code and Antenna Gain settings. See Table 207 General Status page attributes PMP 450m AP on page 9-3 for details The field displays whether PoE Classification functionality is enabled or disabled. It is only applicable for 450i Series devices. Registered SM Count See Table 207 General Status page attributes PMP 450m AP on page 9-3 Sync Pulse Status for details Sync Pulse Source Maximum Count of Registered SMs Data Slots Down Data Slots Up Page 9-9 Chapter 9: Operation System information Contention Slots Connection Status Account ID Site Name Site Contact Site Location Time Updated and Location Code See Table 207 General Status page attributes PMP 450m AP on page 9-3 for details Page 9-10 Chapter 9: Operation System information General Status page - SM The SMs General Status page is explained in Table 209. Note In order for accurate power level readings to be displayed, traffic must be present on the radio link. Table 209 General Status page attributes - SM Attribute Device Type Meaning This field indicates the type of the module. Values include the frequency band of the SM, its module type and its MAC address. Page 9-11 Chapter 9: Operation System information Board Type This field indicates the series of hardware. Product Type Software Version FPGA Version PLD Version Uptime System Time Ethernet Interface Regional Code DFS Antenna Type Frame Period Temperature Session Status Session Uptime This indicates model of the device. This field indicates the system release, the time and date of the release. If you request technical support, provide the information from this field. This field indicates the version of the field-programmable gate array (FPGA) on the module. When you request technical support, provide the information from this field. This field indicates the version of the programmable logic device (PLD) on the module. If you request technical support, provide the value of this field. This field indicates how long the module has operated since power was applied. This field provides the current time. Any SM that registers to an AP inherits the system time, which is displayed in this field as GMT (Greenwich Mean Time). This field indicates the speed and duplex state of Ethernet interface to the SM. A parameter that offers multiple fixed selections, each of which automatically implements frequency band range restrictions for the selected region. Units shipped to regions other than the United States must be configured with the corresponding Country Code to comply with local regulatory requirements. This field indicates that DFS operation is enabled based on the configured region code, if applicable. The current antenna type that has been selected. This field indicates the current Frame Period setting of the radio in ms. The current operating temperature of the board. This field displays the following information about the current session:

Scanning indicates that this SM currently cycles through the radio frequencies that are selected in the Radio tab of the Configuration page. Syncing indicates that this SM currently attempts to receive sync. Registering indicates that this SM has sent a registration request message to the AP and has not yet received a response. Registered indicates that this SM is both:

This field displays the duration of the current link. The syntax of the displayed time is hh:mm:ss. registered to an AP. ready to transmit and receive data packets. Page 9-12 Chapter 9: Operation Registered AP Color Code Channel Frequency Channel Bandwidth Cyclic Prefix Air Delay Receive Power Signal Strength Ratio System information Displays the MAC address and site name of the AP to which the SM is registered to. This parameter provides click-through proxy access to the APs management interface. This field displays a value from 0 to 254 indicating the SMs configured color code. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). This field lists the current operating frequency of the radio. The size in MHz of the operating channel. OFDM technology uses a cyclic prefix, where a portion of the end of a symbol

(slot) is repeated at the beginning of the symbol to allow multi-pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. This field displays the distance in feet between this SM and the AP. To derive the distance in meters, multiply the value of this parameter by 0.3048. Distances reported as less than 200 feet (61 meters) are unreliable. This field lists the current combined receive power level, in dBm. This field displays the difference of the Vertical path received signal power to the Horizontal path received signal power. Signal to Noise Ratio This field lists the current signal-to-noise level, an indication of the separation of the received power level vs. noise floor. Beacons Transmit Power Displays a count of beacons received by the SM in percentage. This value must be typically between 99-100%. If lower than 99%, it indicates a problematic link. This statistic is updated every 16 seconds. This field lists the current combined transmit power level, in dBm. Note The red SM message target power exceeded maximum does not necessarily indicate a problem. In this case, the AP is requesting the SM to transmit at a higher power level, but the SM is restricted due to EIRP limits or hardware capabilities. This message can be an indication that the SM is deployed further from the AP than optimal, causing the AP to adjust the SM to maximum transmit power. Page 9-13 Chapter 9: Operation System information Data Slots Down This field lists the number of slots used for downlink data transmission. Data Slots Up This field lists the number of slots used for uplink data transmission. Contention Slots Site Name Site Contact This field indicates the number of (reserved) Contention Slots configured by the operator. See Contention slots on page7-176. This field indicates the name of the physical module. You can assign or change this name in the SNMP tab of the SM Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. This field indicates contact information for the physical module. You can provide or change this information in the SNMP tab of the SM Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Site Location This field indicates site information for the physical module. You can provide or change this information in the SNMP tab of the SM Configuration page. Maximum Throughput This field indicates the limit of aggregate throughput for the SM and is based on the default (factory) limit of the SM and any floating license that is currently assigned to it. This field displays information about the keying of the radio. Time Updated and Location Code Note For PMP 450 SM 900 MHz, there is additional parameter Path Info (under Subscriber Module Stats) which displays polarization path(A & B) information. Page 9-14 Chapter 9: Operation System information General Status page of BHM The BHMs General Status page is explained in Table 210. Table 210 General Status page attributes - BHM Attribute Device Type Board Type Product Type Meaning This field indicates the type of the module. Values include the frequency band of the BHM, its module type and its MAC address. This field indicates the series of hardware. This indicates model of the device. Page 9-15 Chapter 9: Operation Software Version Board MSN FPGA Version Uptime System Time Ethernet Interface Antenna Type Temperature Session Status Session Uptime Registered Backhaul Channel Frequency Receive Power Signal Strength Ratio Transmit Power Signal to Noise Ratio System information This field indicates the system release, the time and date of the release. If you request technical support, provide the information from this field. This field indicates the Manufactures Serial number. A unique serial number assigned to each radio at the factory for inventory and quality control. This field indicates the version of the field-programmable gate array (FPGA) on the module. When you request technical support, provide the information from this field. This field indicates how long the module has operated since power was applied. This field provides the current time. Any BHS that registers to a BHM inherits the system time, which is displayed in this field as GMT (Greenwich Mean Time). This field indicates the speed and duplex state of Ethernet interface to the BHM. The current antenna type that has been selected. The current operating temperature of the board. This field displays the following information about the current session:

Scanning indicates that this BHS currently cycles through the radio frequencies that are selected in the Radio tab of the Configuration page. Syncing indicates that this BHM currently attempts to receive sync. Registering indicates that this BHM has sent a registration request message to the BHM and has not yet received a response. Registered indicates that this BHM is both:

Registered to a BHM. Ready to transmit and receive data packets. This field displays the duration of the current link. The syntax of the displayed time is hh:mm:ss. Displays the MAC address and site name of the BHM to which the BHS is registered to. This parameter provides click-through proxy access to the BHMs management interface. This field lists the current operating frequency of the radio. This field lists the current combined receive power level, in dBm. This field displays the difference of the Vertical path received signal power to the Horizontal path received signal power. This field lists the current combined transmit power level, in dBm. This field lists the current signal-to-noise level, an indication of the separation of the received power level vs. noise floor. Page 9-16 Chapter 9: Operation System information Beacons Air Delay Data Slots Down Data Slots Up Regional Code Site Name Displays a count of beacons received by the BHM in percentage. This value must be typically between 99-100%. If lower than 99%, it indicates a problematic link. This statistic is updated every 16 seconds. This field displays the distance in feet between this BHS and the BHM. To derive the distance in meters, multiply the value of this parameter by 0.3048. Distances reported as less than 200 feet (61 meters) are unreliable. This field lists the number of slots used for downlink data transmission. This field lists the number of slots used for uplink data transmission. A parameter that offers multiple fixed selections, each of which automatically implements frequency band range restrictions for the selected region. Units shipped to regions other than the United States must be configured with the corresponding Country Code to comply with local regulatory requirements. This field indicates the name of the physical module. Assign or change this name in the Configuration > SNMP page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Page 9-17 Chapter 9: Operation System information General Status page of BHS The BHSs General Status page is explained in Table 211. Table 211 General Status page attributes - BHS Page 9-18 Chapter 9: Operation System information Attribute Device Type Board Type Software Version Board MSN FPGA Version Uptime System Time Ethernet Interface Antenna Type Temperature Session Status Session Uptime Registered Backhaul Channel Frequency Receive Power Signal Strength Ratio Transmit Power Signal to Noise Ratio Beacons Air Delay Data Slots Down Data Slots Up Regional Code Site Name Site Contact Site Location Time Updated and Location Code Meaning See Table 211 on page 9-18 See Table 211 on page 9-18 Page 9-19 Chapter 9: Operation System information Viewing Session Status The Session Status page in the Home page provides information about each SM or BHS that has registered to the AP or BHM. This information is useful for managing and troubleshooting a system. This page also includes the current active values on each SM or BHS for MIR and VLAN, as well as the source of these values, representing the SM/BHS itself, Authentication Server, or the Authentication Server and SM/BHS. Note In order for accurate power level readings to be displayed, traffic must be present on the radio link. The Session Status List has four tab: Device, Session, Power and Configuration. The SessionStatus.xml hyper link allows user to export session status page from web management interface of AP or BHM. The session status page will be exported in xml file. Device tab The Device tab provides information on the Subscribers LUID and MAC, Hardware, Software, FPGA versions and the state of the SM/BHS (Registered and/or encrypted). Table 212 Device tab attributes Attribute Subscriber Meaning This field displays the LUID (logical unit ID), MAC address and Site Name of the SM/BHS. As each SM or BHS registers to the AP/BHM, the system assigns an LUID of 2 or a higher unique number to the SM/BHS. If a SM/BHS loses registration with the AP/BHS and then regains registration, the SM/BHS will retain the same LUID. Page 9-20 Chapter 9: Operation System information Note The LUID associated is lost when a power cycle of the AP/BHM occurs. Both the LUID and the MAC are hot links to open the interface to the SM/BHS. In some instances, depending on network activity and network design, this route to the interface yields a blank web page. If this occurs, refresh your browser view. Site Name indicates the name of the SM/BHS. Change this name on the Configuration web page of the SM/BHS. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. This field displays the SMs or BHS hardware type. This field displays the software release that operates on the SM/BHS, the release date and time of the software. This field displays the version of FPGA that runs on the SM/BHS This field displays the current status of the SM/BHS as either IN SESSION to indicate that the SM/BHS is currently registered to the AP/BHM. IDLE to indicate that the SM/BHS was registered to the AP/BHM at one time, but now is not. Hardware Software Version FPGA Version State This field also indicates whether the encryption scheme in the module is enabled. Session tab The Session tab provides information on the SMs or BHS Session Count, Reg Count, Re-Reg Count, Uptime, Air delay, PPPoE State and Timeouts. Table 213 Session tab attributes Attribute Subscriber Meaning See Table 212 on page 9-20. Page 9-21 Chapter 9: Operation Count Reg Count Re-Reg Count Uptime CC Priority AirDelay System information This field displays how many sessions the SM/BHS has had with the AP/BHM. Typically, this is the sum of Reg Count and Re-Reg Count. However, the result of internal calculation may display here as a value that slightly differs from the sum. If the number of sessions is significantly greater than the number for other SMs or BHS, then this may indicate a link problem or an interference problem. When a SM/BHS makes a Registration Request, the AP/BHM checks its local session database to see whether it was registered earlier. If the AP/BHM concludes that the SM/BHS is not currently in session database and it is valid Registration Request, then the request increments the value of this field. In ideal situation, the Reg Count indicates total number of connected SMs to an AP. Note The user can clear Reg Count by dropping all current sessions of SM (or BHS) from Configuration > Tools > Sessions menu. When a SM/BHS makes a Registration Request, the AP/BHM checks its local session database to see whether it was registered earlier. If the AP/BHM concludes that the SM/BHS is currently in session database, then the request increments the value of this field. Typically, a Re-Reg is the case where both:

SM/BHS attempts to reregister for having lost communication with the AP/BHM. AP/BHM has not yet observed the link to the SM/BHS as being down. It is possible for a small period of time if there is no downlink traffic and AP/BHM still assumes the session is up, but the SM/BHS, loses session and quickly re-connects before the AP/BHM knew the session had dropped. This is how a re-registration happens. If the number of sessions is significantly greater than the number for other SMs or BHS, then this may indicate a link problem (check mounting, alignment, receive power levels) or an interference problem (conduct a spectrum scan). Once a SM/BHS successfully registers to an AP/BHM, this timer is started. If a session drops or is interrupted, this timer is reactivated once re-registration is complete. The field displays Color Code Priority (ICC, Primary, Secondary or Tertiary) of all connected SM. This field displays the distance of the SM/BHS from the AP/BHM in meters, nanoseconds and bits. At close distances, the value in this field is unreliable. Page 9-22 Chapter 9: Operation PPPoE state Timeout System information This field displays the current PPPoE state (whether configured) of the SM/BHS. This field displays the timeout in seconds for management sessions via HTTP, ftp access to the SM/BHS. 0 indicates that no limit is imposed. Power tab Table 214 Power tab attributes Attribute Subscriber Hardware Downlink Rate SU-

MIMO Downlink Rate MU-

MIMO Meaning See Table 212 on page 9-20. This field displays the SMs or BHS hardware type. This field displays whether the high-priority channel is enabled in the SM/BHS and the status of rate adapt. For example, if 8X/4X is listed, the radio is capable of operating at 8X but is currently operating at 4X, due to RF conditions. This field also states whether it is MIMO-A or MIMO-B radio e.g. 8X/8X MIMO-B indicates MIMO-B and 8X/4X MIMO-A indicates MIMO-A. A VC starts at its lowest modulation and slowly rate adapts up, as traffic is successfully transmitted over the VC. It is normal for one VC to have a different modulation rate than another VC, if only one VC has traffic on it. For example if High Priority VC is enabled, but only low priority VC has traffic the reading will show:

REGISTERED VC 18 Rate 8X/8X MIMO-B VC 255 Rate 8X/1X MIMO-B Note: The SU-MIMO rate applies to all AP platforms. For 450m, this field indicates the rate being used for symbols where this particular VC is not being MU-MIMO grouped with other SMs. The MU-MIMO rate applies only to the 450m AP. This rate indicates the modulation used for symbols where this particular low priority VC is MU-

MIMO scheduled, by grouping it in the same slot with other low priority VCs AP Rx Power (dBm) This field indicates the APs or BHMs combined receive power level for the listed SM/BHS. Page 9-23 Chapter 9: Operation System information Signal Strength Ratio

(dB) Signal to Noise Ratio

(dB) This field displays the ratio of the Vertical path received signal power to the Horizontal path received signal power. This ratio can be useful for determining multipathing conditions (high vertical to horizontal ratio) for Uplink. This field lists the current signal-to-noise level, an indication of the separation of the received power level vs. noise floor. In other words, it indicates signal to noise ratio for Uplink. Page 9-24 Chapter 9: Operation System information Configuration tab The Configuration tab provides information on the SMs or BHS Uplink or Downlink (UL/DL) Sustained Data Rate, UL/DL Burst Allocation, UL/DL Burst Rate, UL/DL Low Priority CIR, UL/DL High CIR, UL/DL High Priority Queue Information and the UL/DL Broadcast or Multicast Allocation. This data is refreshed based on the Web Page Auto Update setting on the APs or BHSs General Configuration page. Table 215 Configuration tab attributes Attribute Subscriber Sustained Data Rate Cap (kbps) Sustained Data Rate

(kbps) - Uplink Sustained Data Rate

(kbps) - Downlink Meaning See Table 212 on page 9-20. This field specifies the maximum sustained data rate between SM/BHS and AP/BHM. If this field displays Uncapped, then there is no limit set for data rate. If this field displays 4000, then the maximum sustained data rate between SM/BHS and AP/BHM is limited to 4000 kbps. This field displays the value that is currently in effect for the SM/BHS, with the source of that value in parentheses. This is the specified rate at which each SM/BHS registered to this AP/BHM is replenished with credits for transmission. The configuration source of the value is indicated in parentheses. See Maximum Information Rate (MIR) Parameters on page 7-198. This field displays the value that is currently in effect for the SM/BHS, with the source of that value in parentheses. This is the specified the rate at which the AP/BHM should be replenished with credits (tokens) for transmission to each of the SMs/BHSs in its sector. The configuration source of the value is indicated in parentheses. See Maximum Information Rate (MIR) Parameters on page 7-198. Page 9-25 Chapter 9: Operation Burst Allocation (kbit) -

Uplink Burst Allocation (kbit) -

Downlink Max Burst Rate (kbit) -

Uplink Max Burst Rate (kbit) -

Downlink Low Priority CIR High CIR System information This field displays the value that is currently in effect for the SM/BHS, with the source of that value in parentheses. This is the specified maximum amount of data that each SM/BHS is allowed to transmit before being recharged at the Sustained Uplink Data Rate with credits to transmit more. The configuration source of the value is indicated in parentheses. See Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-200 This field displays the value that is currently in effect for the SM/BHS, with the source of that value in parentheses. This is the specified the rate at which the AP/BHM should be replenished with credits (tokens) for transmission to each of the SMs/BHSs in its sector. The configuration source of the value is indicated in parentheses. See Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-200 The data rate at which an SM/BHS is allowed to burst (until burst allocation limit is reached) before being recharged at the Sustained Uplink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. See Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-200 The data rate at which an SM/BHS is allowed to burst (until burst allocation limit is reached) before being recharged at the Sustained Downlink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. See Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-200 This field indicates the minimum rate at which low priority traffic is sent over the uplink and downlink (unless CIR is oversubscribed or RF link quality is degraded). This field indicates the minimum rate at which high priority traffic is sent over the uplink and downlink (unless CIR is oversubscribed or RF link quality is degraded). Broadcast/Multicast Allocation This field displays the data rate at which Broadcast and Multicast traffic is sent via the radio link. RADIUS Authentication Reply RADIUS Authentication Server This field displays whether RADIUS server is reachable or not. This field displays the associated RADIUS Authentication Server for each SM where it was authenticated. This information is useful when there are multiple RADIUS servers (maximum three servers supported by Cambium). If one server is not reachable, other configured servers are tried in sequential order as a fall-back. In this scenario, the Session Status is useful to identify associate RADIUS Authentication Server for all connected SMs. Page 9-26 Chapter 9: Operation System information Table 216 Session Status > Configuration CIR configuration denotations Attribute

(SM)

(APCAP) Meaning QoS/VLAN parameters are derived from the SMs/BHSs settings QoS/VLAN parameters are derived from the APs settings, including any keyed capping (for radios capped at 4 Mbps, 10 Mbps, or 20 Mbps) QoS/VLAN parameters are retrieved from the device, due to failed retrieval from the AAA or WM server. QoS/VLAN parameters are retrieved from the RADIUS server

(D)

(AAA)

(BAM) QoS/VLAN parameters are retrieved from a WM BAM server Page 9-27

 

 

Chapter 9: Operation System information Link Quality tab The Link Quality tab provides information on the Subscribers UID, Link quality, Downlink, Uplink, Beacon, ReReg, and the Uptime. This data is refreshed based on the Link Quality Update Interval parameter configuration under the Sessions Status page. The Link Quality tab displays the calculated Link Quality Indicator (LQI) for the configured interval (Link Quality Update Interval parameter). Table 217 Link Quality tab attributes Attribute Subscriber Link Quality Indicator Downlink - Quality Index Downlink -Actual Average Rate Downlink - Expected Rate Uplink - Quality Index Uplink -Actual Average Rate Meaning See Table 212 on page 9-20. This field displays quality of the link. It is calculated based on receive power, modulation rate, re-registrations and beacon percentage. This field displays the downlink quality in percentage. It is calculated based on Downlink receiver power, modulation rate, and beacon percentage. This field displays the average Downlink modulation rate. For 450m, this field specifies the SU-MIMO Modulation Rate. This field displays the expected modulation rate based on receive power in Downlink. This field displays the uplink quality in percentage. It is calculated based on Uplink receiver power and modulation rate. This field displays the average Uplink modulation rate. Uplink - Expected Rate This field displays the expected modulation rate based on receive power in Uplink. Page 9-28 Chapter 9: Operation Beacon - Quality Index Beacon - Received Percent Re-Reg - Quality Index Re-Reg Count Uptime System information This field displays the beacon quality index. It is calculated based on beacon percentage. This field displays the received beacon percentage. This field displays the re-registration quality. It is calculated based on the re-

registration count. This field displays the number of re-registrations. This field displays the uptime of the device. Viewing Remote Subscribers This page allows to view the web pages of registered SMs or BHS over the RF link. To view the pages for a selected SM/BHS, click its link. The General Status page of the SM opens. Figure 193 Remote Subscribers page of AP Interpreting messages in the Event Log Each line in the Event Log of a module Home page begins with a time and date stamp. However, some of these lines wrap as a combined result of window width, browser preferences and line length. You may find this tab easiest to use if you expand the window till all lines are shown beginning with time and date stamp. Time and Date Stamp The time and date stamp reflect one of the following:

GPS time and date directly or indirectly received from the CMM4. NTP time and date from a NTP server (CMM4 may serve as an NTP server) The running time and date that you have set in the Time & Date web page. Page 9-29 Chapter 9: Operation System information Note In the Time & Date web page, if you have left any time field or date field unset and clicked the Set Time and Date button, then the time and date default to 00:00:00 UT :

01/01/00. A reboot causes the preset time to pause or, in some cases, to run in reverse. Additionally, a power cycle resets the running time and date to the default 00:00:00 UT : 01/01/00. Thus, whenever either a reboot or a power cycle has occurred, must reset the time and date in the Time & Date web page of any module that is not set to receive sync. Event Log Data Collection The collection of event data continues through reboots and power cycles. When the buffer allowance for event log data is reached, the system adds new data into the log and discards an identical amount of the oldest data. Each line that contains the expression WatchDog flags an event that was both:

Conversely, a Fatal Error () message flags an event that is recorded in the next line. Some exceptions and fatal errors may be significant and require either operator action or technical support. considered by the system software to have been an exception recorded in the preceding line. Figure 194 Event log data Messages that Flag Abnormal Events The messages listed below flag abnormal events and, case by case, may signal the need for corrective action or technical support. Table 218 Event Log messages for abnormal events Event Message Meaning Page 9-30 Chapter 9: Operation System information Expected LUID = 6 Actual LUID = 7 Something is interfering with the control messaging of the module. Also ensure that you are using shielded cables to minimize interference. Consider trying different frequency options to eliminate or reduce interference. FatalError() The event recorded on the line immediately beneath this message triggered the Fatal Error (). Loss of GPS Sync Pulse Machine Check Exception RcvFrmNum =

0x00066d ExpFrmNum =

0x000799 System Reset Exception -- External Hard Reset System Reset Exception -- External Hard Reset WatchDog Module has lost GPS sync signal. This is a symptom of a possible hardware failure. If this is a recurring message, begin the RMA process for the module. Something is interfering with the control messaging of the module. Also ensure that you are using shielded cables to minimize interference. Consider trying different frequency options to eliminate or reduce interference. The unit lost power or was power cycled. The event recorded on the preceding line triggered this WatchDog message. Messages that Flag Normal Events The messages listed below record normal events and typically do not signal a need for any corrective action or technical support. Table 219 Event Log messages for normal events Event Message Acquired GPS Sync Pulse. Meaning Module has acquired GPS sync signal. FPGA Features FPGA Version GPS Date/Time Set Type of encryption. FPGA (JBC) version in the module. Module is now on GPS time. Reboot from Webpage Software Boot Version Module was rebooted from management interface. Boot version in the module. Software Version The software release and authentication method for the unit. System Log Cleared Event log was manually cleared. Page 9-31 Chapter 9: Operation System information Viewing the Network Interface In any module, the LAN1 Network Interface section of this tab displays the defined Internet Protocol scheme for the Ethernet interface to the module. In SM/BHS devices, this page also provides an RF Public Network Interface section, which displays the Internet Protocol scheme defined for network access through the master device (AP/BHM). Figure 195 Network Interface tab of the AP Figure 196 Network Interface tab of the SM Viewing the Layer 2 Neighbors In the Layer 2 Neighbors tab, a module reports any device from which it has received a message in Link Layer Discovery Protocol within the previous two minutes. Given the frequency of LLDP messaging, this means that the connected device will appear in this tab 30 seconds after it is booted and remain until two minutes after its shutdown. Figure 197 Layer 2 Neighbors page Page 9-32 Chapter 9: Operation System statistics System statistics This section describes how to use the system statistics pages to manage the performance of the PMP/PTP 450 Platform Family link. Viewing the Scheduler statistics The Statistics > Scheduler page is applicable for all modules (AP/SM/BHM/BHS) and the parameters are displayed as shown below:

Table 220 Scheduler tab attributes Page 9-33 Chapter 9: Operation Attribute Transmit Unicast Data Count Transmit Broadcast Data Count Transmit Multicast Data Count Receive Unicast Data Count Receive Broadcast Data Count Receive Multicast Data Count Transmit Control Count System statistics Meaning Total amount of unicast packets transmitted from the radio Total amount of broadcast packets transmitted from the radio Total amount of multicast packets transmitted by the radio Total amount of unicast packets received by the radio Total amount of broadcast packets received by the radio Total amount of multicast packets received by the radio Amount of radio control type messages transmitted (registration requests and grants, etc.) Receive Control Count Amount of radio control type messages received (registration requests and In Sync Count Out of Sync Count Overrun Count Underrun Count Receive Corrupt Data Count Receive Corrupt Control Data Count Receive Bad Broadcast Control Count Rcv LT Start Rcv LT Start HS grants, etc.) Number of times the radio has acquired sync. When GPS synchronization is used it is number of times GPS sync acquired. For the SM, itis the number of times the SM successfully obtained sync with an AP. Number of times the radio lost same sync lock Number of times FPGA frame has overrun its TX Frame Number of times FPGAs TX Frame aborted prematurely Number of times a corrupt packet has been received at the FPGA. Number of times a corrupt control data packet has been received at the FPGA. Number of times the radio has received an invalid control message via broadcast (SM only). Number of Link Test Start messages received. A remote radio has requested that this radio start a link test to it. Number of Link Test Start Handshake messages received. This radio requested that a remote radio start a link test and the remote radio has sent a handshake back acknowledging the start. Page 9-34 Chapter 9: Operation Rcv LT Result Xmt LT Result System statistics This radio received Link Test results from the remote radio under test. When this radio initiates a link test, the remote radio will send its results to this radio for display. This radio transmitted its link test results to the remote radio under test. When the remote radio initiates a link test, this radio must send its results to the remote radio for display there. Frame Too Big This statistics indicates the number of packets received and processed by the radios which were greater than max packet size 1700 bytes. Bad Acknowledgment This statistics indicates the number of packets received as bad acknowledgment. It is for engineering use only. Bad Fragment VC Clear Error Count Rx No Buffer Count Scheduler Error This statistic indicates number of fragments tagged internally as bad. It is for engineering use only. This statistic indicates number of times VC clear failed. Currently unused This error is incremented when the scheduler cannot send or get scheduled to send a packet. t is also general called a VC Error. Viewing list of Registration Failures statistics SM Registration Failures page of AP The SM Registration Failures tab identifies SMs that have recently attempted and failed to register to this AP. With its time stamps, these instances may suggest that a new or transient source of interference exists. Table 221 SM Registration Failures page attributes - AP Attribute Status 17 Flag 0 Meaning No response was received from the AAA server and hence SM is trying to send a session request again. Page 9-35 Chapter 9: Operation System statistics BHS Registration Failures page of BHM Table 222 BHS Registration Failures page attributes - BHM Attribute Status 17 Flag 0 Meaning No response was received from the AAA server and hence SM is trying to send a session request again. There is a list of flags from 0 to 20 as shown in Table 223 and the Flags can be ignored. Table 223 Flags status Flag Meaning Flag Meaning 0 1 2 3 4 5 6 7 8 9 Normal Out of Range No Luids BH ReRange Auth Fail Encrypt Fail Power Adjust No VCs Reserve VC Fail Activate VC Fail 10 Hi VC Setup Fail 11 12 13 14 15 16 17 18 19 20

-

AP Lite Limit Reached Only Ver 9.5+ Allowed Temporary Data VC for AAA AAA Authentication Failure Registration Grant Reject Blank AAA Session Retry AAA Reauth Failure RegReq at zero power RegReq no time ref

-

Page 9-36 Chapter 9: Operation System statistics Interpreting Bridging Table statistics If NAT (network address translation) is not active on the SM/BHS, then the Bridging Table page provides the MAC address of all devices that are attached to registered SMs/BHS (identified by LUIDs). The SM/BHS management MAC addresses are also added in bridge table upon SMs/BHS registration. These entries will be remove automically from the table once SMs/BHS is de-registered. This alleviates the arp cache > bridge cache timeout problems. The bridging table allows data to be sent to the correct module as follows:

For the AP/BHM, the uplink is from RF to Ethernet. Thus, when a packet arrives in the RF interface to the AP/BHM, the AP/BHM reads the MAC address from the inbound packet and creates a bridging table entry of the source MAC address on the other end of the RF interface. For the SM/BHS, the uplink is from Ethernet to RF. Thus, when a packet arrives in the Ethernet interface to one of these modules, the module reads the MAC address from the inbound packet and creates a bridging table entry of the source MAC address on the other end of the Ethernet interface. Figure 198 Bridging Table page The Bridging Table supports up to 4096 entries. Interpreting Translation Table statistics When Translation Bridging is enabled in the AP, each SM keeps a table mapping MAC addresses of devices attached to the AP to IP addresses, as otherwise the mapping of end-user MAC addresses to IP addresses is lost. (When Translation Bridging is enabled, an AP modifies all uplink traffic originating from registered SMs such that the source MAC address of every packet is changed to that of the SM which bridged the packet in the uplink direction.) Page 9-37 Chapter 9: Operation Figure 199 Translation Table page of SM System statistics Interpreting Ethernet statistics The Statistics > Ethernet page reports TCP throughput and error information for the Ethernet connection of the module. This page is applicable for all modules (AP/SM/BHM/BHS). The Ethernet page displays the following fields. Table 224 Ethernet tab attributes Attribute Ethernet Link Detected Meaning 1 indicates that an Ethernet link is established to the radio, 0 indicates that no Ethernet link is established Page 9-38 Chapter 9: Operation System statistics Ethernet Link Lost This field indicates a count of how many times the Ethernet link was lost. Undersized Toss Count inoctets Count inucastpkts Count Innucastpkts Count indiscards Count inerrors Count inunknownprotos Count outoctets Count outucastpkts Count outnucastpkts Count outdiscards Count This field indicates the number of packets that were too small to process and hence discarded. This field displays how many octets were received on the interface, including those that deliver framing information. This field displays how many inbound subnetwork-unicast packets were delivered to a higher-layer protocol. This field displays how many inbound non-unicast (subnetwork-broadcast or subnetwork-multicast) packets were delivered to a higher-layer protocol. This field displays how many inbound packets were discarded without errors that would have prevented their delivery to a higher-layer protocol. (Some of these packets may have been discarded to increase buffer space.) This field displays how many inbound packets contained errors that prevented their delivery to a higher-layer protocol. This field displays how many inbound packets were discarded because of an unknown or unsupported protocol. This field displays how many octets were transmitted out of the interface, including those that deliver framing information. This field displays how many packets for which the higher-level protocols requested transmission to a subnetwork-unicast address. The number includes those that were discarded or not sent. This field displays how many packets for which the higher-level protocols requested transmission to a non-unicast (subnetwork-broadcast or subnetwork-multicast) address. The number includes those that were discarded or not sent. This field displays how many outbound packets were discarded without errors that would have prevented their transmission. (Some of these packets may have been discarded to increase buffer space.) outerrrors Count This field displays how many outbound packets contained errors that prevented their transmission. RxBabErr TxHbErr EthBusErr CRCError RcvFifoNoBuf This field displays how many receiver babble errors occurred. This field displays how many transmit heartbeat errors have occurred. This field displays how many Ethernet bus errors occurred on the Ethernet controller. This field displays how many CRC errors occurred on the Ethernet controller. This field displays the number of times no FIFO buffer space was able to be allocated. Page 9-39 Chapter 9: Operation System statistics Note:

PMP 450 AP running in Gigabit Ethernet Mode displays error RcfFifoNoBuf which indicates packet loss. For 450 AP platforms, if ethernet auto-negotation is set to Gigabit, then it is a known limitation that RcfFifoNoBuf error will be seen. This issue is not seen if autonegotation is set to 100Mbps or lower, and the issue is not seen on 450i or 450m AP's. RxOverrun Late Collision This field displays how many receiver overrun errors occurred on the Ethernet controller. This field displays how many late collisions occurred on the Ethernet controller. A normal collision occurs during the first 512 bits of the frame transmission. A collision that occurs after the first 512 bits is considered a late collision. Caution A late collision is a serious network problem because the frame being transmitted is discarded. A late collision is most commonly caused by a mismatch between duplex configurations at the ends of a link segment. RetransLimitExp This field displays how many times the retransmit limit has expired. TxUnderrun CarSenseLost No Carrier This field displays how many transmission-underrun errors occurred on the Ethernet controller. This field displays how many carrier sense lost errors occurred on the Ethernet controller. This field displays how many no carrier errors occurred on the Ethernet controller. Page 9-40 Chapter 9: Operation System statistics Interpreting RF Control Block statistics The Statistics > Radio page is applicable for all module (AP/SM/BHM/BHS). The Radio page of the Statistics page displays the following fields. Table 225 Radio (Statistics) page attributes RF Control Block Attribute inoctets Count inucastpkts Count Innucastpkts Count indiscards Count Meaning This field displays how many octets were received on the interface, including those that deliver framing information. This field displays how many inbound subnetwork-unicast packets were delivered to a higher-layer protocol. This field displays how many inbound non-unicast (subnetwork-broadcast or subnetwork-multicast) packets were delivered to a higher-layer protocol. This field displays how many inbound packets were discarded without errors that would have prevented their delivery to a higher-layer protocol. This stat is pegged whenever corrupt data is received by software or whenever the RF Software Bridge queue is full. Corrupt data is a very unusual event because all packets are CRC checked by hardware before being passed into software. The likely case for indiscards is if the RF bridge queue is full. If this is the case the radio is most likely PPS limited due to excessive small packet traffic or a problem at the Ethernet interface. If there is a problem at the Ethernet interface there is likely to be discards at the Ethernet as well. inerrors Count This field displays how many inbound packets contained errors that prevented their delivery to a higher-layer protocol. inunknownprotos Count This field displays how many inbound packets were discarded because of an unknown or unsupported protocol. Page 9-41 Chapter 9: Operation outoctets Count outucastpkts Count outnucastpkts Count outdiscards Count System statistics This field displays how many octets were transmitted out of the interface, including those that deliver framing information. This field displays how many packets for which the higher-level protocols requested transmission to a subnetwork-unicast address. The number includes those that were discarded or not sent. This field displays how many packets for which the higher-level protocols requested transmission to a non-unicast (subnetwork-broadcast or subnetwork-multicast) address. The number includes those that were discarded or not sent. This field displays how many outbound packets were discarded without errors that would have prevented their transmission. (Some of these packets may have been discarded to increase buffer space.) outerrrors Count This field displays how many outbound packets contained errors that prevented their transmission. Page 9-42 Interpreting Sounding statistics for AP In the AP GUI, sounding statistics can be found under Statistics > Radio. Table 226 Radio (Statistics - AP) page attributes - Sounding Attribute reference SF soundingState Meaning Spatial Frequency of VC. Values 0 to 1023 are valid and value 2048 is considered as invalid. Different types of Sounding states are:

UNKNOWN: VC has recently registered to the AP but not registered with the channel manager yet. NEW: VC has been registered with the channel manager and will soon transition to ASSESSING. ASSESSING: AP will instruct SM to take the channel measurements. Channel estimates and spatial frequencies will be calculated. TRACKING: Valid measurements resulted in good channel estimates and spatial frequency. This VC can now be used for MU-MIMO. INVALID: Inconsistent measurements resulting in no channel estimate or spatial frequency. This VC cannot be used for MU-MIMO and it will ultimately be re-assessed. Page 9-1 Chapter 9: Operation soundingFault System statistics Generally if VC is UNTRUSTED, this means something went wrong. The fault codes can help to describe what is wrong with this channel (If VC is TRACKING this will generally indicate 0 (SOUNDING_FAULT_NONE)). Error codes are:

SOUNDING_FAULT_VC_CEST: Channel Estimate Error, could be due to issues with the channel.. SOUNDING_FAULT_NULLING_SNR: Channel Estimate Error, could be due to issues with the channel. SOUNDING_FAULT_SM_ERROR: SM returned Error code when taking channel measurements. SOUNDING_FAULT_CHANNEL_DISTORTION: Channel Distortion is beyond tolerance, could be due to issues with the channel. SOUNDING_FAULT_UNSTABLE_SF: Inconsistent Spatial Frequency, could be due to issues with the channel. SOUNDING_FAULT_SF_DEVIATION: Inconsistent Spatial Frequency, could be due to issues with the channel. SOUNDING_FAULT_INTERNAL_ERROR: Could be due to incompatible software (AP SM), or other catastrophic software issue. mumimoVetoCount If excessive channel distortion is observed during condensed nulling (tracking state) this count will increment and VC will transition back to assessing state. channelDistortion nullingSNR cnResponseCountSM Channel distortion readings. Signal to noise ratio of condensed nulling error response. The SM adds a counter to the CN (Condensed Nulling) response. This indicates how many responses were sent by that SM. cnResponseCountAP The AP increments a count for each CN response received. missedTagCount This is the number of CN responses transmitted by SM but not received at AP. Page 9-2 Chapter 9: Operation System statistics Page 9-3 Interpreting Sounding statistics for SM In the SM GUI, sounding statistics can be found under Statistics > Radio. The top section, RF Control Block Statistics, is applicable to the SM communicating to any AP (450, 450i, or 450m), and it is always visible. The bottom section, Sounding Statistics, is visible only if the SM is communicating with a 450m AP. Table 227 Radio (Statistics - SM) page attributes - Sounding Attribute Responses Responses Suppressed Errors Version Mismatch Meaning Number of sounding responses (full VC assessments or condensed nulling) sent from the SM to the AP Number of sounding requests suppressed by the SM. The reason why a sounding response is suppressed is because the error calculated during the sounding process is lower than the threshold set by the AP. In this case, the SM does not need to transmit a sounding response to the AP Number of errors in the sounding process at the SM Examples of events that count as errors:

Sounding type is not supported IQ capture not enabled: for example, if sounding requested too soon after SM boot IQ capture did not complete Sounding processing took too long Number of sounding requests with mismatched version numbers The Sounding Acquisition Command contains a version number. The SM checks its own version number and flags any mismatch. Currently, AP and SMs use V1. Max Request Interval Avg Request Interval Largest time between two sounding requests received from the 450m AP Average time between two sounding requests received from the 450m AP Page 9-1 Chapter 9: Operation System statistics The following attributes are applicable only for 450m:

Attribute mumimoVetoCount Meaning If excessive channel distortion is observed during condensed nulling (tracking state) this count will increment and VC will transition back to assessing state. Channel distortion readings. channelDistortion nullingSNR cnResponseCountSM The SM adds a counter to the CN (Condensed Nulling) response. This Signal to noise ratio of condensed nulling error response. indicates how many responses were sent by that SM. The AP increments a count for each CN response received. This is the number of CN responses transmitted by SM but not received at AP. cnResponseCountAP missedTagCount Interpreting VLAN statistics The Statistics > VLAN page provides a list of the most recent packets that were filtered because of VLAN membership violations. It is applicable for all modules (AP/SM/BHM/BHS). Table 228 VLAN page attributes Attribute Unknown Only Tagged Ingress Meaning This must not occur. Contact Technical Support. The packet was filtered because the configuration is set to accept only packets that have an 802.1Q header and this packet did not. When the packet entered through the wired Ethernet interface, the packet was filtered because it indicated an incorrect VLAN membership. Page 9-2 Chapter 9: Operation System statistics Local Ingress Egress Local Egress When the packet was received from the local TCP/IP stack, the packet was filtered because it indicated an incorrect VLAN membership. This must not occur. Contact Technical Support. When the packet attempted to leave through the wired Ethernet interface, the packet was filtered because it indicated an incorrect VLAN membership. When the packet attempted to reach the local TCP/IP stack, the packet was filtered because it indicated an incorrect VLAN membership. Page 9-3 Chapter 9: Operation System statistics Interpreting Data VC statistics The Statistics > Data VC page displays information about Virtual Channel (VC) used in data communications. This page is applicable for all modules (AP/SM/BHM/BHS). The Data VC tab displays the fields as explained in Table 229. Table 229 Data VC page attributes Attribute Subscriber VC CoS Inbound Statistics, octets Inbound Statistics, ucastpkts Inbound Statistics, nucastpkts Inbound Statistics, discards Meaning This field displays the LUID (logical unit ID), MAC address and Site Name of the SM/BHS. As each SM or BHS registers to the AP/BHM, the system assigns an LUID of 2 or a higher unique number to the SM/BHS. If a SM/BHS loses registration with the AP/BHM and then regains registration, the SM/BHS retains the same LUID. This field displays the virtual channel number. Low priority channels start at VC18 and count up. High priority channels start at VC255 and count down. If one VC is displayed, the high-priority channel is disabled. If two are displayed, the high-priority channel is enabled. This field displays the Class of Service for the virtual channel. The low priority channel is a CoS of 00 and the high priority channel is a CoS of 01. CoS of 02 through 07 are not currently used. This field displays how many octets were received on the interface, including those that deliver framing information. This field displays how many inbound subnetwork-unicast packets were delivered to a higher-layer protocol. This field displays how many inbound non-unicast (subnetwork-broadcast or subnetwork-multicast) packets were delivered to a higher-layer protocol. This field displays how many inbound packets were discarded without errors that would have prevented their delivery to a higher-layer protocol. Inbound discard statistics are incremented similar to the indiscards stat on the RF control block stats page. The sum of all data VC indiscards must be close to the RF control block in discards. If indiscards are evenly distributed across SMs, then the radio is PPS limited due to either excessive small packet transmissions, or a problem at the Ethernet link. If indiscards are contained to one or a few SMs, then there is likely a problem at or underneath the SM which is incrementing the count. Page 9-4 Chapter 9: Operation System statistics Inbound Statistics, errors Inbound Statistics, QPSK frgmts Inbound Statistics, 16-

QAM frgmts Inbound Statistics, 64-

QAM frgmts Inbound Statistics, 256-QAM frgmts Outbound Statistics, octets Outbound Statistics, ucastpkts Outbound Statistics, nucastpkts Outbound Statistics, discards This field displays how many inbound packets contained errors that prevented their delivery to a higher-layer protocol. This field displays how many inbound fragments were received via the QPSK modulation scheme. This field displays how many inbound fragments were received via the 16-

QAM modulation scheme. This field displays how many inbound fragments were received via the 64-

QAM modulation scheme. This field displays how many inbound fragments were received via the 256-

QAM modulation scheme. This field displays how many octets were transmitted out of the interface, including those that deliver framing information. This field displays how many packets for which the higher-level protocols requested transmission to a subnetwork-unicast address. The number includes those that were discarded or not sent. This field displays how many packets for which the higher-level protocols requested transmission to a non-unicast (subnetwork-broadcast or subnetwork-multicast) address. The number includes those that were discarded or not sent. This field displays how many outbound packets were discarded without errors that would have prevented their transmission. Outbound discard statistics are incremented if a VC is not active when a packet is ready to send. This is a rare condition. Outbound Statistics, errors This field displays how many outbound packets contained errors that prevented their transmission. Queue Overflow This is a count of packets that were discarded because the queue for the VC was already full. If Queue Overflows are being seen across most or all SMs, then there is either an interferer local to the AP or the APs RF link is at capacity. If Queue Overflows are being seen at one or only a few SMs, then it is likely that there is a problem with those specific links whether it is insufficient signal strength, interferer, or a problem with the actual SM hardware. High Priority Queue This is a count of packets that were received on high priority queue. Page 9-5 Chapter 9: Operation System statistics Interpreting Throughput statistics The 450 Platform Family has a Statistics > Throughput page which shows historical information about sector or backhaul throughput and packet discards. This page is applicable for AP and BHM modules. This information can be useful to identify an overloaded sector or heavy bandwidth users. This page also shows the user throughput in terms of data rate (kbps) and packet rate (packets per second, or PPS), as well as the average packet size during the sample period. Operators may set the AP/BHM to send an SNMP trap when it detects an RF overload condition based on a configurable threshold. The following configuration parameters are available on the Throughput tab GUI pane and a radio reboot is not required when configuring these parameters:

Table 230 RF overload Configuration attributes AP/BHM Attribute Throughput Monitoring This enables or disables the monitoring of sector throughput and packet Meaning discards. This parameter is disabled by default. SNMP Trap on RF Overload Downlink RF Overload Threshold Downlink RF Link Status Time Period Length Time Period Ending This enables or disables the sending of an SNMP trap when an AP/BHM overload condition is reached (based on Downlink RF Overload Threshold). This parameter determines the overload threshold in percent of packets discarded that triggers the generation of an SNMP trap. This field displays the status of the capacity of the RF link. These two configuration parameters determine what set of collection samples to show on the GUI display. The Time Period Length can be set from one to three hours. Time Period Ending allows the operator to set the end time for the set of collection samples to display. Below the configuration settings are three tables that display the statistics that are collected. Board Performance statistics This table contains a row that corresponds to each 1 minute statistics collection interval. Each row contains the following data aggregated for the entire AP/BHM:

Page 9-6 Chapter 9: Operation System statistics Ethernet Throughput - Statistics collected at the Ethernet port:

o kbps in average throughput over the collection interval in Kbps into the AP/BHM on the o kbps out average throughput over the collection interval in Kbps out of the AP/BHM on the o PPS in average packets per second over the collection interval into the AP/BHM on the o PPS out average packets per second over the collection interval out of the AP/BHM on the Ethernet Interface Ethernet Interface Ethernet Interface Ethernet Interface RF Throughput - Statistics collected at the RF Interface:

o kbps in average throughput over the collection interval in Kbps into the AP/BHM on the RF o kbps out average throughput over the collection interval in Kbps out of the AP/BHM on the RF o PPS in average packets per second over the collection interval into the AP/BHM on the RF o PPS out average packets per second over the collection interval out of the AP/BHM on the RF Interface Interface Interface Interface Aggregate Through Board Sum of bidirectional data transferred through (not originating or terminating at) the AP/BHM:

o kbps average bidirectional throughput over the collection interval in Kbps o PPS average bidirectional packets per second over the collection interval o Ave Pkt Size Average Packet size over the collection interval of bidirectional data transferred Board Throughput statistics This table contains a row that corresponds to each one minute statistics collection interval. This table may be used to determine if there are problems with any of the interfaces. For example, if the Ethernet in packets is much higher than the RF out packets it could indicate a denial of service (DoS) attack on the AP/BHM. Each row contains the following data aggregated for the entire AP/BHM:

Ethernet Statistics - Statistics collected at the Ethernet port:

o inOctets Number of octets (bytes) received by the AP/BHM at the Ethernet Interface over the collection interval o o outOctets Number of octets (bytes) sent by the AP/BHM at the Ethernet Interface over the collection interval inPkts Number of packets received by the AP/BHM at the Ethernet Interface over the collection interval o outPkts Number of packets sent by the AP/BHM at the Ethernet Interface over the collection o Discards (in/out) Number of packets that had to be discarded by the AP/BHM at the respective interval Ethernet Interface Queue RF Statistics - Statistics collected at the RF Interface:

o inOctets Number of octets (bytes) received by the AP/BHM at the RF Interface over the collection interval o outOctets Number of octets (bytes) sent by the AP/BHM at the RF Interface over the collection interval inPkts Number of packets received by the AP/BHM at the RF Interface over the collection interval o Page 9-7 Chapter 9: Operation System statistics o outPkts Number of packets sent by the AP/BHM at the RF Interface over the collection interval o Discards (in/out) Number of packets that had to be discarded by the AP/BHM at the respective RF Interface Queue during the collection interval o Discards % (in/out) Percent of the total packets received / transmitted that had to be discarded during the collection interval LUID RF Throughput statistics This table contains a row that corresponds to each active LUID served by the AP/BHM. Note that an LUID may be assigned 1 or 2 VCs. If the LUID is assigned 2 VCs, then the data in the table is the sum of the activity for both VCs. This table may be used to determine which LUIDs are experiencing overload so that corrective action can be taken (i.e. fixing a poor RF link or moving a heavily loaded link to a less congested AP/BHM). Each row contains counters and statistics related to the RF Interface that are updated once per minute:

Inbound Statistics - Statistics collected at the RF Interface for the Uplink:

o octets Number of octets (bytes) received by the AP/BHM at the RF Interface for this LUID over the collection interval collection interval o pkts Number of packets received by the AP/BHM at the RF Interface for this LUID over the o Ave Pkt Size Average size of the packets received by the AP/BHM at the RF Interface for this LUID over the collection interval o discards Number of packets received by the AP/BHM at the RF Interface for this LUID over the collection interval that had to be discarded because the RF In Queue was full o discards % Percent of the total packets received by the AP/BHM at the RF Interface for this LUID over the collection interval that had to be discarded because the RF In Queue was full Outbound Statistics - Statistics collected at the RF Interface for the Downlink:

o octets Number of octets (bytes) transmitted by the AP/BHM at the RF Interface for this LUID over the collection interval collection interval o pkts Number of packets transmitted by the AP/BHM at the RF Interface for this LUID over the o Ave Pkt Size Average size of the packets transmitted by the AP/BHM at the RF Interface for this LUID over the collection interval o discards Number of packets to be transmitted by the AP/BHM at the RF Interface for this LUID over the collection interval that had to be discarded because the RF Out Queue was full o discards % Percent of the total packets to be transmitted by the AP/BHM at the RF Interface for this LUID over the collection interval that had to be discarded because the RF Out Queue was full. Page 9-8 Chapter 9: Operation System statistics Interpreting Overload statistics The Statistics > Overload page displays statistics on packet overload and resultant packet discards. Unlike the other fields, the Total Packets Overload Count is expressed in only this page. It is not a count of how many packets have been lost, but rather of how many discard events (packet loss bursts) have been detected due to overload condition. This statistics page is applicable for all modules (AP/SM/BHM/BHS) and explained in Table 231. Table 231 Overload page attributes AP/SM/BHM/BHS Attribute Total Packets Overload Count Ethernet In Discards Meaning This field represents the sum of all RF and Ethernet in/out discards. This field represents the number of packets tossed due to the Ethernet queue being full. If a climb in this stat accompanies a climb in RF Out Discards stat, then most likely the board is at RF capacity either due to traffic exceeding the RF pipe, or interference temporarily limiting the RF throughput. If this stat climbs without the RF Out Discards stat climbing, then the radio is most likely PPS limited. Ethernet Out Discards This field represents the number of packets tossed due to an Ethernet out RF In Discards overload. This stat must not climb in normal operation because the Ethernet link is much higher capacity than the RF link. If this stat is incrementing, then either the Ethernet link is established at a low speed (i.e. 10Mbps half duplex), or there is a problem with cabling/Ethernet hardware. This field indicates the number of packets tossed due to no resources available within the radio to process them. This stat also must not be increasing because the system is designed to shed packets on the RF Out interface. If this stat is incrementing the board, it is most likely congested due to high PPS rate in combination with an Ethernet Out problem, which limits packet flow off the device. Page 9-9 Chapter 9: Operation RF Out Discards System statistics This field indicates the number of packets tossed due to RF link at capacity. This stat will increase whenever the RF link is at capacity. When the internal FPGA RF input queue overflows, this stat is incremented. If this stat is seen to be incrementing at the AP, then the sector is congested. If seen at the SM, the number of Contention Slots must be looked at to ensure that enough Contention Slots are allocated to allow for bandwidth requests to be seen at the AP. Note 450m Overload:

The 450m Series AP is designed to handle high load in terms of high throughput and high PPS. In terms of throughput, 450m is designed to achieve 3x or more throughput improvement over 450 and 450i Series products. In terms of packets per second (PPS), 450m is designed to handle up to 100k PPS. Overload occurs when the offered load exceeds the above limits. When overload occurs, 450m will start discarding packets and TCP throughput will degrade due to packet loss. Its worth noting that Frame Utilization statistics (Statistics > Frame Utilization tab: Frame Utilization: Downlink and Uplink) are not necessarily indicative of overload condition. They show how much the TDD frame is utilized. High frame utilization depends on:

High traffic during busy periods: those statistics will be close to 100% and almost all slots will be utilized. In this case if the Overload statistics show that packets are discarded then this is an indication of overload condition. High percentage of VCs with low modulation with moderate traffic. Those VCs will require more slots to service them (due to low modulation) and the frame utilization will be high. In this case the TDD frame is fully utilized but the system is at low capacity and is not in an overload condition. 450m has higher PPS than 450 and 450i and supports higher throughput through spatial multiplexing, therefore when a 450m replaces an overloaded 450 or 450i AP the 450m will not be overloaded under the same conditions but the frame utilization may still show close to 100%; this should not alarm the customer. The overload statistics shall be monitored on 450m to see if it is overloaded or not. Interpreting DHCP Relay statistics The Statistics > DHCP Relay page displays requests and replies received, relayed and discarded when the AP is configured as a DHCP relay. Typically, in a working DHCP relay configuration a one-to-one ratio is established between requests and replies that are received and relayed. This statistics page is only applicable for PMP (AP and SM modules) and it is explained in Table 232. Page 9-10 Chapter 9: Operation Table 232 DHCP Relay page attributes AP/SM System statistics Attribute Requests Received Requests Relayed Requests Discarded Replies Received Replies Relayed Replies Discarded Meaning This field represents the number of DHCP relay requests received by the AP. This field represents the number of DHCP relay requests relayed by the AP. This field represents the number of DHCP relay requests discarded by the AP due to errors in the request. This field represents the number of DHCP relay replies received by the AP. This field represents the number of DHCP relay replies relayed by the AP. This field represents the number of DHCP relay replies discarded by the AP due to errors in the reply. Untrusted Message Discards This field indicates messages that were discarded because the message already contained Option 82 information with no Relay Agent specified. Max Hop Exceeded Discards This field indicates messages that have been relayed too many times, exceeding the max hop count (16). This field indicates messages that have been discarded because the message relay agent address is already in place (relay agent address does not equal address of the AP). This field indicates DHCP messages too large to fit Option 82 data. These messages are sent on without Option 82 information. Invalid Relay Agent Address Discards Relay Info Exceeding Max Message Size

(DHCP message relayed without Option 82) Page 9-11 Chapter 9: Operation System statistics Interpreting Filter statistics The Statistics > Filter page displays statistics on packets that have been filtered (dropped) due to the filters set on the Protocol Filtering page. The filter page of SM is explained in Table 233. Table 233 Filter page attributes - SM Attribute PPPoE Count All IPv4 Count All Other IPv4 Count SMB Count SNMP Count Bootp Client Count Meaning Number of PPPoE packets filtered. Number of IPv4 packets filtered. Any IPv4 message that was not SMB, SNMP, Bootp, Multicast or one of the user defined filters, that was filtered out. Number of IPv4 Server Message Block (file sharing) packets filtered. Number of IPv4 SNMP packets filtered. Total number of IPv4 DHCP requests filtered. Bootp Server Count Total number of IPv4 DHCP replies filtered. IPv4 Multicast Count All IPv6 Count All Other IPv6 Count IPv6 SMB Count Number of IPv4 Multicast messages filtered. Number of IPv6 messages filtered. Any IPv6 message that was not SMB, SNMP, Bootp, Multicast or one of the user defined filters, that was filtered out. Number of IPv6 Server Message Block (file sharing) packets filtered IPv6 SNMP Count IPv6 Bootp Client Count Number of IPv6 SNMP messages filtered Total number of IPv6 DHCP replies filtered IPv6 Bootp Server Count Total number of IPv6 DHCP replies filtered IPv6 Multicast Count Number of IPv6 Multicast messages filtered Page 9-12 Chapter 9: Operation System statistics ARP Count Total number of ARP packets filtered. All other Count User Defined Port1 Count User Defined Port2 Count User Defined Port3 Count The count of any messages that did not fit above that were filtered out Number of packets defined by the user port1 that were filtered. Number of packets defined by the user port2 that were filtered. Number of packets defined by the user port3 that were filtered. Viewing ARP statistics The Statistics > ARP page in a SM module correlated the IP address of the Ethernet-connected device to its MAC address and provides data about the connection. Figure 200 ARP page of the SM Viewing NAT statistics When NAT is enabled on a SM, statistics are kept on the Public and Private (WAN and LAN) sides of the NAT and displayed on the Statistics > NAT Stats page. The NAT page of SM is explained in Table 234. Page 9-13 Chapter 9: Operation Table 234 NAT page attributes - SM System statistics Attribute Private NAT Statistics, Packet In Count Private NAT Statistics, Packet Out Count Private NAT Statistics, Packet Out Toss Count Meaning This field represents the number of packets received on the SMs LAN/Ethernet interface This field represents the number of packets sent from the SMs LAN/Ethernet interface This field represents the number of packets that we not sent from the SMs LAN/Ethernet interface due to addressing issues. Private NAT Statistics, Out of Resources Count This field represents the number of times the NAT table for the SMs LAN/Ethernet interfaces has been filled. Private NAT Statistics, Failed Hash Insert Count This field represents the number of times that the device failed to insert an address binding into the NAT hash table. Public NAT Statistics, Packet In Count Public NAT Statistics, Packet Out Count Public NAT Statistics, Out of Resources Count This field represents the number of packets received on the SMs WAN/wireless interface This field represents the number of packets sent from the SMs WAN/wireless interface This field represents the number of packets that we not sent from the SMs WAN/wireless interface due to addressing issues. Public NAT Statistics, Failed Hash Insert Count This field represents the number of times the NAT table for the SMs WAN/wireless interfaces has been filled. Page 9-14 Chapter 9: Operation System statistics Viewing NAT DHCP Statistics The Statistics > NAT DHCP page displays NAT enabled DHCP client statistics. This is statistics page is applicable for SM only. When NAT is enabled on a SM with DHCP client (DHCP selected as the Connection Type of the WAN interface) and/or DHCP Server, statistics are kept for packets transmitted, received and tossed, as well as a table of lease information for the DHCP server (Assigned IP Address, Hardware Address and Lease Remained/State). Table 235 NAT DHCP Statistics page attributes - SM Attribute PktXmt Count PktRcv Count PktToss ARPUnresolved Overflow Count Meaning Represents the number of DHCP packets transmitted from the client This field represents the number of DHCP packets received by the client This field represents the number of packets tossed due to failed attempts to resolve an IP address into a physical MAC address PktToss Unsupported MsgType Count PktToss XID Mismatch Count PktToss NoSID Count This field represents the number of packets that were tossed due to lack of a This field represents the number of packets tossed due to the receipt of an unsupported message type (cannot be interpreted by DHCP client) The field represents the number of packets that were tossed due to a transaction ID mismatch DHCP session ID PktToss SID Mismatch Count Represents the number of packets tossed due to a session ID mismatch Page 9-15 Chapter 9: Operation System statistics Failure to Reset Client Count This field represents the number of times the DHCP client was unable to be reset (resulting in no IP address being served). Interpreting Sync Status statistics The Statistics > Sync Status page of AP is only displayed when the Sync Input is set to AutoSync or AutoSync+Free Run. The Sync Status page is explained in Table 236. Table 236 Sync Status page attributes - AP Attribute Sync Pulse Source Meaning This field indicates the status of the synchronization source:

Searching indicates that the unit is searching for a GPS fix Timing Port/UGPS indicates that the module is receiving sync via the timing AUX/SYNC timing port Power Port indicates that the module is receiving sync via the power port

(Ethernet port). Sync Pulse Status This field indicates synchronization source pulse status. Sync Pulse Status Timing Port/UGPS Sync Pulse Status -

Power Port UGPS Power Status This field indicates synchronization pulse status over Timing Port/UGPS port. This field indicates synchronization pulse status over power port. This field indicates UGPS power up status (on or off). This information may be helpful in a decision of whether to climb a tower to diagnose a perceived antenna problem. Page 9-16 Chapter 9: Operation System statistics Interpreting PPPoE Statistics for Customer Activities The page can be access under Statistics > PPPoE of SM GUI. When the PPPoE feature is enabled on the SM, PPPoE statistics provide data about activities of the customer. The PPPoE Statistics of SM is explained in Table 237. Table 237 PPPoE Statistics page attributes - SM Attribute IP address Meaning This field displays the IP address of the PPPoE session initiator (situated below the SM) This field displays the operational status of the PPPoE Session PPPoE Session Status PPPoE AC Name This field displays access concentrator name used in the PPPoE session PPPoE Service Name This field displays the PPPoE service name associated with the PPPoE PPPoE Session ID PPPoE Session Uptime PPPoE Session Idle Time PPPoE Session MTU server in use This field displays the current PPPoE session ID This field displays the total session uptime for the PPPoE session This field displays the total idle time for the PPPoE session This field displays Maximum Transmission Unit configured for the PPPoE session Primary DNS Address This field displays the primary DNS server used by the PPPoE session Secondary DNS Address This field displays the secondary DNS server used by the PPPoE session Page 9-17 Chapter 9: Operation System statistics PPPoE Control Bytes Sent PPPoE Control Bytes Received PPPoE Data Session Bytes Sent PPPoE Data Session Bytes Received Displays the total number of PPPoE session control bytes sent from SM This field displays the total number of PPPoE session control bytes received by the SM This field displays the total number of PPPoE data session (non-control/non-

session management user data) sent by the SM This field displays the total number of PPPoE data session (non-control/non-

session management user data) Page 9-18 Chapter 9: Operation System statistics Interpreting Bridge Control Block statistics The Statistics > Bridge Control Block page displays statistics of Bridge FEC, Bridge ratio and Bridge error. The page is applicable for all modules (AP/SM/BHM/BHS). The Bridge Control Block Statistics page is explained in Table 238. Table 238 Bridge Control Block page attributes AP/SM/BHM/BHS Attribute Bridge FEC Stats Meaning Page 9-19 Chapter 9: Operation FEC bin FEC bout FEC btoss FEC btosscap FEC uin FEC uout FEC utoss FEC utosscap Bridge Eth Aux Stats FEC bin FEC bout FEC btoss FEC btosscap FEC uin FEC uout FEC utoss FEC utosscap Bridge Radio Stats RF bin System statistics This field indicates the number of broadcast packets received by the bridge control block on the Main Ethernet interface This field indicates the number of broadcast packets sent by the bridge control block on the Main Ethernet interface This field indicates the number of broadcast packets tossed out by the bridge control block on the Main Ethernet interface This field indicates the number of broadcast packets tossed out at the Main Ethernet interface due to MIR cap being exceeded. This field indicates the number of unicast packets received by the bridge control block on the Main Ethernet interface This field indicates the number of unicast packets sent by the bridge control block on the Main Ethernet interface This field indicates the number of unicast packets tossed by the bridge control block on the Main Ethernet interface This field indicates the number of unicast packets tossed out at the Main Ethernet interface due to MIR cap being exceeded. This field indicates the number of broadcast packets received by the bridge control block on the Aux Ethernet interface This field indicates the number of broadcast packets sent by the bridge control block on the Aux Ethernet interface This field indicates the number of broadcast packets tossed out by the bridge control block on the Aux Ethernet interface This field indicates the number of broadcast packets tossed out at the Aux Ethernet interface due to MIR cap being exceeded. This field indicates the number of unicast packets received by the bridge control block on the Aux Ethernet interface This field indicates the number of unicast packets sent by the bridge control block on the Aux Ethernet interface This field indicates the number of unicast packets tossed by the bridge control block on the Aux Ethernet interface This field indicates the number of unicast packets tossed out at the Aux Ethernet interface due to MIR cap being exceeded. This field indicates the number of broadcast packets received by the bridge control block on the radio interface Page 9-20 Chapter 9: Operation System statistics RF bout RF btoss RF btosscap RF uin RF uout RF utoss RF utosscap Bridge Error Stats ErrNI1QSend ErrNI2QSend ErrBridgeFull ErrSendMsg ErrApFecQSend ErrApRfQSend This field indicates the number of broadcast packets sent by the bridge control block on the radio interface This field indicates the number of broadcast packets tossed by the bridge control block on the radio interface This field indicates the number of broadcast packets tossed out at the radio interface due to MIR cap being exceeded. This field indicates the number of unicast packets received by the bridge control block on the radio interface This field indicates the number of unicast packets sent by the bridge control block on the radio interface This field indicates the number of unicast packets tossed by the bridge control block on the radio interface This field indicates the number of unicast packets tossed out at the radio interface due to MIR cap being exceeded. This field indicates that a packet which was sourced from the radio network stack interface 1 (Ethernet interface) could not be sent because the radio bridge queue was full. The packet was tossed out. This field indicates that a packet which was sourced from the radio network stack interface 2 (RF interface) could not be sent because the radio bridge queue was full. The packet was tossed out. This field indicates the total number of times the bridging table was full and could not accept new entries. This field displays the error message from bridge core call back routine. This field indicates that a packet which was received on the Ethernet interface could not be processed because the radio bridge queue was full and packet was tossed out. This field indicates that a packet which was received on the RF interface could not be processed because the radio bridge queue was full. The packet was tossed out. Note:

PMP 450m Series AP does not support Aux port in current release of 15.0/15.0.0.1. Page 9-21 Chapter 9: Operation System statistics Interpreting Pass Through Statistics The Statistics > Pass Through Statistics page displays radius related statistics. The page is applicable for PMP 450 Platform Family - AP only. The Pass Through Statistics page is explained in Table 239. Table 239 Pass Through Statistics page attributes AP Attribute IdentityReqSent PktsEncapsulated PktsDecasulated AccessAcceptRcvd Meaning This field indicates the number of EAP Identity requests sent through the AP with respect to an SM. This field indicates no of packets received from the SM which are encapsulated by the AP. This field indicates no of packets received from the radius server and are decapsulated by the AP with respect to an SM This field indicates no of RADIUS Access Accept message received by the AP with respect to an SM. Page 9-22 Chapter 9: Operation System statistics Interpreting SNMPv3 Statistics The Statistics > SNMPv3 Statistics page displays all SNMPv3 related statistics. The page is applicable for all type of ODUs of PMP 450 Platform. The SNMPv3 Statistics page is explained in Table 240. Table 240 SNMPv3 Statistics page attributes AP Attribute Statistics for snmpMPDStats group Meaning SNMP Message Processing and Dispatching RFC 3412 Page 9-23 Chapter 9: Operation System statistics snmpUnknownSecurityMod els The total number of packets received by the SNMP engine which were dropped because they referenced a securityModel that was not known to or supported by the SNMP engine. snmpInvalidMsgs snmpUnknownPDUHandler s usmStatsUnsupportedSecL evels usmStatsNotInTimeWindow s usmStatsUnknownUserNa mes usmStatsUnknownEngineI Ds usmStatsWrongDigests usmStatsDecryptionErrors snmpTargetSpinLock snmpUnavailableContexts snmpUnknownContexts usmUserSpinLock The total number of packets received by the SNMP engine which were dropped because there were invalid or inconsistent components in the SNMP message. The total number of packets received by the SNMP engine which were dropped because the PDU contained in the packet could not be passed to an application responsible for handling the pduType, e.g. no SNMP application had registered for the proper combination of the contextEngineID and the pduType. The total number of packets received by the SNMP engine which were dropped because they requested a securityLevel that was unknown to the SNMP engine or otherwise unavailable. The total number of packets received by the SNMP engine which were dropped because they appeared outside of the authoritative SNMP engine's window. The total number of packets received by the SNMP engine which were dropped because they referenced a user that was not known to the SNMP engine. The total number of packets received by the SNMP engine which were dropped because they referenced a snmpEngineID that was not known to the SNMP engine. The total number of packets received by the SNMP engine which were dropped because they didn't contain the expected digest value. The total number of packets received by the SNMP engine which were dropped because they could not be decrypted. This object is used to facilitate modification of table entries in the SNMP-TARGET-MIB module by multiple managers. The total number of packets received by the SNMP engine which were dropped because the context contained in the message was unavailable. The total number of packets received by the SNMP engine which were dropped because the context contained in the message was unknown. The use of usmUserSpinlock is to avoid conflicts with another SNMP command generator application which may also be acting on the usmUserTable. Page 9-24 Chapter 9: Operation vacmViewSpinLock System statistics An advisory lock used to allow cooperating SNMP Command Generator applications to coordinate their use of the Set operation in creating or modifying views. snmpEngineBoots It is a count of the number of times the SNMP engine has re-

booted/re-initialized since snmpEngineID was last configured snmpEngineTime time since engine is up which is the number of seconds since the snmpEngineBoots counter was last incremented Interpreting syslog statistics The Statistics > Syslog Statistics page displays statistics of syslog messages. The page is applicable for all modules (AP/SM/BHM/BHS). The Syslog Statistics page is explained in Table 241. Table 241 Syslog statistics page attributes AP/SM/BH Attribute Syslog Server Syslog Server Port Syslog Status Syslog Message Transmissions Syslog Message Dropped Meaning This displays dotted decimal or DNS name (if the DNS is enabled) of the syslog server address. The syslog server port (default 514) to which syslog messaging is sent. This indicates status of syslog messaging. It can be Enable or Disabled based on configuration This field indicates the count of syslog messages sent to UDP layer. This field indicates the count of dropped syslog messages. Interpreting Frame Utilization statistics The Frame Utilization Statistics is a feature helps user to understand how effectively the RF channel is being utilized. This feature allows to check Time Division Duplex (TDD) frame utilization pattern and diagnose for any excessive usage in uplink or downlink direction. This forms the first step of identifying the TDD frame utilization information. If the user finds excessive utilization based on this stats, the second step would be to take several actions like sectorization, tuning the uplink/downlink ratio etc. to improve RF channel utilization. Efficient use of the TDD frame will help to achieve optimum performance of link. Page 9-25 Chapter 9: Operation System statistics Note The backhauls (BHM and BHS) will have only the downlink scheduler based statistics Table 242 Frame utilization statistics for PMP 450m AP Page 9-26 Chapter 9: Operation System statistics Page 9-27 Chapter 9: Operation Attribute Frame Utilization Interval Statistics Display interval MU-MIMO Utilization Spatial Utilization Spatial Utilization System statistics Meaning This allows to configure timer interval to monitor and display the frame utilization statistics. It can be configured for 1 minute (low interval), 5 minutes (medium interval) or 15 minutes (high interval) based on requirement. This is a table (32 rows) that lists frame utilization for each spatial frequency (SF) range with following information:

Spatial frequency: Range of spatial frequency for each bin. Each bin includes 32 consecutive spatial frequency values. Azimuth (degrees): Azimuth range in degrees corresponding to the spatial frequencies of the bin. The zero degree azimuth is boresight. Note:

Some SF ranges correspond to multiple azimuth ranges. This is due to the fact that for some spatial frequencies the AP generates beams in multiple azimuth directions. The SM can be physically located in any of the azimuth ranges. Instantaneous (%): Frame utilization for the SF bin, updated every 500 ms. The frame utilization percentage accounts for all traffic, both sector mode and MU-MIMO transmissions. Total (%): Average utilization in the SF bin for the past 1/5/15 minutes, as selected in the Statistics Display Interval. Max (%): Maximum Instantaneous utilization in the 1/5/15 minute interval Min (%): Minimum Instantaneous utilization in the 1/5/15 minute interval VCs in Range: List of VCs with spatial frequency falling in the bin. Note:

The size of each SF bin is smaller than the beam generated by the AP during a MU-MIMO transmission. This means that when a VC in a bin is scheduled for a MU-MIMO transmission, the adjacent bins also receive the signal, and the transmission is counted towards their utilization as well. Bins with consistent low utilization indicate the areas of the sector where more SMs could be installed, or the customers that could be offered higher data plans. Page 9-28 Chapter 9: Operation Grouping Instantaneous Distribution System statistics This specifies the distribution of group size for the past 1/5/15 minutes. For each group size, from 0 to 7, the table shows the percentage of slots using that group size. A group size of 0 corresponds to unused slots. A group size of 1 corresponds to sector mode transmissions

(ungrouped). A group size of 2 to 7 corresponds to MU-MIMO transmissions. This table is updated every 500 ms and displays the following:

Group: Each row corresponds to the top (most active) 1, 2, 4, 8, 16, 32, 64, 128, and 256 VCs. Median Slot Count: Median value of the average number of slots scheduled for the VCs in each group in the past 500 ms. VCs in Group: List of VCs belonging to each bin where each bin includes all VCs listed in preceding rows along with the VCs listed in the corresponding row. For example, the row labeled Top 32 VCs considers up to 32 VCs, which are: one VC listed in Top VC row, plus one VC listed in Top 2 VCs row, plus 2 VCs listed in Top 4 VCs row, plus four VCs listed in Top 8 VCs row, plus 8 VCs listed in Top 16 VCs rows, plus up to 16 VCs listed in Top 32 VCs row. If the number of VCs in the sector is less than 32, this row will include less than 16 VCs; if the number of VCs in the sector is equal to or greater than 32, this row will include 16 VCs. Note:

For best MU-MIMO operation, the distribution of the median values in this table should be as close to flat as possible. If many VCs are equally active, there is a higher probability of being able to group their transmissions. If only a few VCs are active, the probability of grouping transmissions is lower, and both the Average MU-MIMO Group size and the Multiplexing Gain are expected to be lower. Average MU-MIMO Group Size Sector Utilization MU-MIMO Utilization SU-MIMO Utilization This specifes the average number of users in the MU-MIMO groups formed in the last 1/5/15 minutes. This specifes the average of the 32 values of the Spatial Utilization table. This specifies the portion of the Sector Utilization used for MU-MIMO transmissions. This specifies the portion of the Sector Utilization used for SU-MIMO transmissions. Page 9-29 Chapter 9: Operation Canopy MAC Acknowledgment Utilization Broadcast/Multicast Utilization Multiplexing Gain Frame Utilization Downlink Uplink Bandwidth Requests System statistics This specifies the portion of the Sector Utilization used for acknowledgments transmission. This specifies the portion of the Sector Utilization used for broadcast and multicast transmissions. This specifies the ratio between the number of logical slots and the number of physical slots used. A physical slot is an OFDM symbol. In non MU-MIMO mode, each logical slot is sent during one physical slot. In MU-MIMO mode a number of logical slots are sent during a physical slot, equal to the number of VCs in the group. A logical slot carries new information; if data is repeated in a group, because some VCs have more data to send then others, then the repeated transmissions are not counted as a logical slots. Without MU-MIMO operation, the multiplexing gain would always be equal to 1. With MU-MIMO operation, this number accounts for parallel transmissions to multiple users in the MU-MIMO group. The difference between the Average MU-MIMO Group Size and the Multiplexing Gain is that the Average MU-MIMO Group Size only considers the MU-MIMO groups, and it averages the number of VCs in the Group. The Multiplexing Gain also considers non MU-MIMO transmissions, which are counted as groups of size 1. This indicates the percentage of downlink data slots used against the maximum number of slots possible in the configured interval. This indicates the percentage of uplink data slots used against the maximum number of uplink slots possible in the configured interval. The "Bandwidth Request" is a message sent from the SM to the AP asking to be scheduled for bandwidth to send in the uplink. This gets transmitted in the unscheduled portion of the uplink. Unscheduled uplink is defined as Contention Slots + unscheduled uplink slots. Since this is sent in the unscheduled portion of the uplink, it will result in collisions when SMs randomly pick the same slot. The "Bandwidth Request Missed" metrics are to add data to know how many of requests are colliding. If it is near 100%, then near all of the SMs bandwidth requests are getting through to the AP, so this a is near perfect scenario. If it is significantly less than that, you may be experiencing uplink latency as your SMs are attempting to request bandwidth and are unable to do so. Also note that if it is consistently at 100% the AP may be able to reduce its contention slots to a lower value and gain more data slots. Page 9-30 Chapter 9: Operation Downlink Counts Total Per Frame Average Low Priority High Priority Broadcast/Multicast Canopy MAC Acknowledgements Registration Messages Uplink Counts Total Per Frame Average Low Priority High Priority Canopy MAC Acknowledgements Contention Slots Contention Slots Average Per Frame Bandwidth Requests Received Bandwidth Requests Missed Maximum possible counts Downlink System statistics This indicates the sum of all downlink data slots used in the configured interval. This indicates the average data per frame in the downlink traffic. The number of downlink data slots used for low priority downlink traffic. The number of downlink data slots used for high priority downlink traffic. The number of downlink data slots used for broadcast and multicast traffic. The number of downlink data slots used as ACKs. The number of downlink data slots used for registration messages. This indicates the sum of all uplink data slots used in configured interval. This indicates the average data per frame in the uplink traffic. The number of uplink data slots used for low priority uplink traffic. The number of uplink data slots used for high priority uplink traffic. The number of uplink data slots used as ACKs. The number of (reserved contention slots + unscheduled symbols that can be used as contention slots) Contention slots configured by the operator. It is the average number of contention slots in a frame for the last duration. Duration is 1/5/15 mins. This indicates the number of Bandwidth Requests received from SMs. This indicates how many of Bandwidth Requests are colliding. This indicates the maximum possible downlink data slots in the configured interval. This is based on the configuration of Channel Bandwidth, Frame period, uplink/downlink allocation, contention slots and configured Statistics Display interval. Page 9-31 Chapter 9: Operation System statistics Uplink Contention Packet Discard counts Ethernet indiscards Ethernet outdiscards Radio indiscards Radio outdiscards This indicates the maximum possible uplink data slots in the configured interval. This is based on the configuration of Channel Bandwidth, Frame period, uplink/downlink allocation, contention slots and configured Statistics Display interval. This indicates the maximum possible contention slots. This indicates the number of Ethernet packets discarded in the IN queue. This indicates the number of Ethernet packets discarded in the OUT queue. This indicates the number of packets discarded over radio in the IN queue. This indicates the number of packets discarded over radio in the OUT queue. Page 9-32 Chapter 9: Operation Table 243 Frame utilization statistics for 450/450i/450m System statistics Attribute Frame Utilization Interval Statistics Display interval Meaning This allows to configure timer interval to monitor and display the frame utilization statistics. It can be configured for 1 minute (low interval), 5 minutes (medium interval) or 15 minutes (high interval) based on requirement. Frame Utilization Page 9-33 Chapter 9: Operation System statistics Downlink Uplink Bandwidth Requests Downlink Counts Total Per Frame Average Low Priority High Priority Broadcast/Multicast Canopy MAC Acknowledgements Registration Messages Uplink Counts Total Per Frame Average Low Priority High Priority This indicates the percentage of downlink data slots used against the maximum number of slots possible in the configured interval. This indicates the percentage of uplink data slots used against the maximum number of uplink slots possible in the configured interval. The "Bandwidth Request" is a message sent from the SM to the AP asking to be scheduled for bandwidth to send in the uplink. This gets transmitted in the unscheduled portion of the uplink. Unscheduled uplink is defined as Contention Slots + unscheduled uplink slots. Since this is sent in the unscheduled portion of the uplink, it will result in collisions when SMs randomly pick the same slot. The "Bandwidth Request Missed" metrics are to add data to know how many of requests are colliding. If it is near 100%, then near all of the SMs bandwidth requests are getting through to the AP, so this a is near perfect scenario. If it is significantly less than that, you may be experiencing uplink latency as your SMs are attempting to request bandwidth and are unable to do so. Also note that if it is consistently at 100% the AP may be able to reduce its contention slots to a lower value and gain more data slots. This indicates the sum of all downlink data slots used in the configured interval. This indicates the average data per frame in the downlink traffic. The number of downlink data slots used for low priority downlink traffic. The number of downlink data slots used for high priority downlink traffic. The number of downlink data slots used for broadcast and multicast traffic. The number of downlink data slots used as ACKs. The number of downlink data slots used for registration messages. This indicates the sum of all uplink data slots used in configured interval. This indicates the average data per frame in the uplink traffic. The number of uplink data slots used for low priority uplink traffic. The number of uplink data slots used for high priority uplink traffic. Page 9-34 Chapter 9: Operation Canopy MAC Acknowledgements Contention Slots Contention Slots Average Per Frame Bandwidth Requests Received Bandwidth Requests Missed Maximum possible counts Downlink Uplink Contention Packet Discard counts Ethernet indiscards Ethernet outdiscards Radio indiscards Radio outdiscards System statistics The number of uplink data slots used as ACKs. The number of (reserved contention slots + unscheduled symbols that can be used as contention slots) Contention slots configured by the operator. It is the average number of contention slots in a frame for the last duration. Duration is 1/5/15 mins. This indicates the number of Bandwidth Requests received from SMs. This indicates how many of Bandwidth Requests are colliding. This indicates the maximum possible downlink data slots in the configured interval. This is based on the configuration of Channel Bandwidth, Frame period, uplink/downlink allocation, contention slots and configured Statistics Display interval. This indicates the maximum possible uplink data slots in the configured interval. This is based on the configuration of Channel Bandwidth, Frame period, uplink/downlink allocation, contention slots and configured Statistics Display interval. This indicates the maximum possible contention slots. This indicates the number of Ethernet packets discarded in the IN queue. This indicates the number of Ethernet packets discarded in the OUT queue. This indicates the number of packets discarded over radio in the IN queue. This indicates the number of packets discarded over radio in the OUT queue. Page 9-35 Chapter 9: Operation Radio Recovery Radio Recovery This section describes:

How to recover a PMP/PTP 450i and PMP 450m Series ODUs from configuration errors or software image corruption How to override a PMP/PTP 450 Series ODUs from forgotten IP address and password to factory default Radio Recovery Console PMP/PTP 450i/450b and PMP 450m Recovery mode allows to restore IP address and password. Also, it 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 a software upgrade. Note When Recovery has been entered through a power on/off/on cycle, the ODU will revert to normal operation if no web access has been made to the unit within 30 seconds. This prevents the unit remaining inadvertently in recovery following a power outage. Options in recovery mode are:

Boot with normal operation Boot with default Canopy system software settings Load a previous SW image The last most recent software images loaded to the board are retained. However the factory image is not retained. Boot with default Canopy system software settings (similar to the hardware Default Plug based on 450 Platforms Family). Note The unit may enter recovery console automatically, in response to some failures. Note Once the unit has entered recovery, it will switch back to normal operation if no access has been made to the recovery web page within 30 seconds. Use below procedure to enter in recovery console manually. Page 9-36 Chapter 9: Operation Radio Recovery Page 9-37 Chapter 9: Operation Procedure 35 Radio Recovery Console Radio Recovery 1 Apply power to PSU for at least 10 seconds. 2 Remove power from the PSU, and then re-apply it as soon as the power indicator light goes out (about 1 - 2 seconds). 3 When the unit is in recovery mode, access the web interface by entering the default IP address 169.254.1.1. The Recovery Image Warning page is displayed. 4 Review the Boot Selection (Table 244). 5 Select a recovery option Figure 201 Recovery Options page Attribute Boot Selection Table 244 Recovery Options attributes Meaning Boot Default Mode: Use this option to temporarily set the IP and Ethernet attributes to factory defaults until the next reboot. Boot Normal: Use this option to reboot the unit. These fields display IP address, Netmask and Gateway of the radio while it is in recovery or default mode. IP address, Netmask, Gateway Page 9-38 Chapter 9: Operation Radio Recovery Note The radio enters recovery mode when a short power cycle is used. The radio will boot normally if power has been removed for a longer period (typically 5 - 10 seconds). Default Mode (or Default/Override Plug) - PMP/PTP 450 Series The default modeallows to temporarily override some PMP/PTP 450 Series ODU settings and thereby regain control of the module by powering the module on with the Default Plug inserted into the units synchronization (RJ11) port. This override plug is needed for access to the module in any of the following cases:

You have forgotten either o o the IP address assigned to the ODU. the password that provides access to the ODU. The ODU has been locked by the No Remote Access feature. You want local access to a module that has had the 802.3 link disabled in the Configuration page. You can configure the module such that, when it senses the override plug, it responds by either resetting the LAN1 IP address to 169.254.1.1, allowing access through the default configuration without changing the configuration, whereupon you will be able to view and reset any non-default values as you wish. resetting all configurable parameters to their factory default values. Note The Default Plug is available from Best-Tronics Manufacturing, Inc. See http://www.best-tronics.com/cambium.htm as Part BT-0583 (RJ-11 Default Plug). Alternatively, you can fabricate an override plug. See Override plug cable on page 5-15 for pinout. Page 9-39 Chapter 9: Operation Radio Recovery Using the Default/Override Plug The following section details usage of the override plug to regain access to PMP/PTP 450 Series ODU. Note While the override plug is connected to a PMP/PTP 450 Series ODU, the ODU can neither register nor allow registration of another ODU. Note Since the 900 MHz SM is based on the 450 Series, it only supports the "Default Plug" mode of overriding. Use below procedure to enter in default mode manually. Procedure 36 Default mode 1 2 Insert the override plug into the RJ-11 GPS utility port of the module. Power cycle by removing, then re-inserting, the Ethernet cable. RESULT: The module boots with the default IP address of 169.254.1.1, password fields blank, and all other configuration values as previously set. 3 Wait approximately 30 seconds for the boot to complete. 4 Remove the override plug. 5 6 Change configuration values if desired. 7 Click the Save Changes button. 8 Click the Reboot button. Set passwords and IP address as desired. Page 9-40 Chapter 10: Reference information This chapter contains reference information and regulatory notices that apply to the 450 Platform Family ODUs. The following topics are described in this chapter:

Equipment specifications on page 10-2 contains specifications of the 450 Platform Family, ODU specifications including RF bands, channel width and link loss. Data network specifications on page 10-43 shows the 450 Platform Family Ethernet interface specifications. Compliance with safety standards on page 4-22 lists the safety specifications against which 450 Platform Family ODU has been tested and certified. It also describes how to keep RF exposure within safe limits. Country specific radio regulations on page 10-46 describes how the 450 Platform Family complies with the radio regulations that are enforced in various countries. Equipment Disposal on page 10-49 describes the Equipment Disposal system for Electronic and Electric Equipment. Page 10-1 Chapter 10: Reference information Equipment specifications Equipment specifications This section contains specifications of the AP, SM, BHM and BHS associated supplies required for 450 Platform Family installations. Specifications for PMP 450m Series - AP The PMP 450m AP conforms to the specifications listed in Table 245. Table 245 PMP 450m Series - AP specifications Category Model Number Spectrum Channel Spacing Frequency Range Channel Bandwidth Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Nominal Receive Sensitivity (w/ FEC) @ 5 MHz Channel 5.1 GHz 5.2 GHz 5.4 GHz Specification PMP 450m AP Configurable on 2.5 MHz increments 5150 to 5925 MHz 5, 10, 15, 20, and 40 MHz Cambium Proprietary 14x14 Multi-User MIMO OFDM 100/1000BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID 1x=-101.6 dBm, 2x=-96.2 dBm, 4x=-90.2 dBm, 6x=-84 dBm, 8x=-76.6 dBm 1x=-101.3 dBm, 2x=-96.3 dBm, 4x=-89.7 dBm, 6x=-83.3 dBm, 8x=-75.7 dBm 1x=-101.1 dBm, 2x=-96.8 dBm, 4x=-90 dBm, 6x=-83.9 dBm, 8x=-76.2 dBm Page 10-2 Chapter 10: Reference information Equipment specifications Nominal Receive Sensitivity (w/ FEC) @

10 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

15 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel 5.8 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz Performance Subscriber Per Sector ARQ Cyclic Prefix Frame Period 1x=-101.6 dBm, 2x=-96.6 dBm, 4x=-89.9 dBm, 6x=-83.7 dBm, 8x=-76.3 dBm 1x=-99 dBm, 2x=-94.6 dBm, 4x=-87.8 dBm, 6x=-81.6 dBm, 8x=-74.6 dBm 1x=-98.8 dBm, 2x=-93.8 dBm, 4x=-87.6 dBm, 6x=-81.4 dBm, 8x=-73.6 dBm 1x=-98.1 dBm, 2x=-94.1 dBm, 4x=-87.5 dBm, 6x=-81.5 dBm, 8x=-73.8 dBm 1x=-98.5 dBm, 2x=-93.6 dBm, 4x=-87.5 dBm, 6x=-81.2 dBm, 8x=-73.7 dBm 1x=-97.3 dBm, 2x=-92.5 dBm, 4x=-86.3 dBm, 6x=-79.9 dBm, 8x=-72.9 dBm 1x=-96.7 dBm, 2x=-91.9 dBm, 4x=-85.7 dBm, 6x=-79.5 dBm, 8x=-72.5 dBm 1x=-96.2 dBm, 2x=-92.1 dBm, 4x=-85.5 dBm, 6x=-79.4 dBm, 8x=-72.4 dBm 1x=-97.2 dBm, 2x=-92.4 dBm, 4x=-85.5 dBm, 6x=-79.4 dBm, 8x=-72.5 dBm 1x=-96.3 dBm, 2x=-91.9 dBm, 4x=-85.3 dBm, 6x=-79.3 dBm, 8x=-71.3 dBm 1x=-95.8 dBm, 2x=-91.8 dBm, 4x=-84.8 dBm, 6x=-78.8 dBm, 8x=-71.8 dBm 1x=-95.1 dBm, 2x=-91.4 dBm, 4x=-84.8 dBm, 6x=-78.3 dBm, 8x=-71.1 dBm 1x=-95.8 dBm, 2x=-91.3 dBm, 4x=-84.7 dBm, 6x=-78.3 dBm, 8x=-70.8 dBm Up to 238 Yes 1/16 2.5 ms Page 10-3 Chapter 10: Reference information Equipment specifications Modulation Levels (Adaptive) Modulation Levels 2x 4x 6x 8x MCS SNR (in dB) QPSK 16QAM 64QAM 256QAM 10 17 24 32 Latency 10 ms, typical (MU-MIMO introduces additional latency only for the low priority traffic) Maximum Deployment Range Up to 40 miles (64 km) GPS Synchronization Quality of Service Link Budget Yes, via Autosync (UGPS) Diffserv QoS Antenna Beam Width 5 GHz 90 integrated sector (Dual polarity, H+V) Antenna Gain Maximum Transmit Power Physical

+14 dBi

+24 dBm combined Data, Sync/AUX and SFP port RJ45 1000BASE-T Ethernet Data AUX port for UGPS or PoE out to 802.3at Antenna Connection Surge Suppression (with LPU) Mean Time Between Failure Environmental Temperature / Humidity Weight Integrated Integrated Sector Array EN61000-4-5: 1.2 us/50 us, 500 V voltage waveform Recommended external surge suppressor:

Cambium Networks Model # C000065L007A

> 40 Years IP66, IP67

-40C to +60C (-40F to +140F) 0-95% non-condensing Approx. 14.2 kg (31 bs)

@90 mph / 144 kph 460 N Page 10-4 Chapter 10: Reference information Equipment specifications Wind Loading Front Facing Dimension (HxWxD) Power Consumption Input Voltage Mounting Security Encryption

@110 mph /177 kph 700 N Integrated 52 x 65 x 11 cm (20.3 x 25.7 x 4.4) 70 W typical, 80 W peak

(up to 110 W max with AUX port PoE enabled) 58 V, 1.7 A Pole mount with included brackets 56-bit DES, FIPS-197 128-bit AES Page 10-5 Chapter 10: Reference information Equipment specifications Specifications for PMP 450i Series - AP The PMP 450i AP conforms to the specifications listed in Table 246. Table 246 PMP 450i Series - AP specifications Category Model Number Spectrum Channel Spacing Frequency Range Specification PMP 450i AP 5, 7, 10, 15, 20, 30, and 40 MHz Channel Bandwidth Configurable on 2.5 MHz increments 902 to 928 MHz Channel Bandwidth Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity 902 928 MHz 3300 - 3900 MHz 4900 5925 MHz 3300 - 3900 MHz 4900 - 5925 MHz 5, 7, 10, 15, and 20 MHz 5, 7, 10, 15, 20, 30, and 40 MHz 5, 10, 15, 20, 30, and 40 MHz Cambium Proprietary 2x2 MIMO OFDM 10/100/1000BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID Nominal Receive Sensitivity (w/ FEC) @ 5 MHz Channel 900 MHz 3.5 GHz 1x = -91.9 dBm, 2x = -86.7 dBm, 4x = -80.9 dBm, 6x = -75 dBm, 8x = -68.8 dBm 1x = -92.7 dBm, 2x = -88.7 dBm, 4x = -82.7 dBm, 6x = -

75.8 dBm, 8x = -69 dBm Page 10-6 Chapter 10: Reference information Equipment specifications 3.6 GHz 4.9 GHz 5.4 GHz 5.8 GHz 900 MHz 3.5 GHz 3.6 GHz 900 MHz 3.5 GHz 3.6 GHz 4.9 GHz 5.4 GHz 5.8 GHz 900 MHz 3.5 GHz 3.6 GHz 1x=-91 dBm, 2x=-86.1 dBm, 4x=-80.2 dBm, 6x=-73.1 dBm, 8x=-66 dBm 1x = -91.6 dBm, 2x = -87.6 dBm, 4x = -80.4 dBm, 6x = -

73.2 dBm, 8x = -66 dBm 1x = -92 dBm, 2x = -87 dBm, 4x = -80.8 dBm, 6x = -73.7 dBm, 8x = -66.6 dBm 1x = -91.5 dBm, 2x = -87 dBm, 4x = -80.2 dBm, 6x = -73.1 dBm, 8x = -66 dBm 1x = -90 dBm, 2x = -85.9 dBm, 4x = -79.8 dBm, 6x = -73.6 dBm, 8x = -67.9 dBm 1x=-91.8 dBm, 2x=-87.7 dBm, 4x=-80.8 dBm, 6x=-74.7 dBm, 8x=-67.3 dBm 1x=-90 dBm, 2x=-87 dBm, 4x=-79.8 dBm, 6x=-73.8 dBm, 8x=-67.2 dBm 1x = -90.6 dBm, 2x = -85.2 dBm, 4x = -79.1 dBm, 6x = -

73.2 dBm, 8x = -66.2 dBm 1x=-90.2 dBm, 2x=-86.2 dBm, 4x=-80 dBm, 6x=-73.1 dBm, 8x=-66.7 dBm 1x=-89.5 dBm, 2x=-85.7 dBm, 4x=-79.8 dBm, 6x=-72.8 dBm, 8x=-66.3 dBm 1x = -89.1 dBm, 2x = -85 dBm, 4x = -77.9 dBm, 6x = -71.8 dBm, 8x = -64.6 dBm 1x = -89.5 dBm, 2x = -85.4 dBm, 4x = -78.2 dBm, 6x = -

72.2 dBm, 8x = -64.8 dBm 1x = -89.5 dBm, 2x = -84.7 dBm, 4x = -77.8 dBm, 6x = -

71.6 dBm, 8x = -64 dBm 1x=-88.2 dBm, 2x=-83.2 dBm, 4x=-76.3 dBm, 6x=-70.2 dBm, 8x=-64.3 dBm 1x=-89 dBm, 2x=-84 dBm, 4x=-77.9 dBm, 6x=-72 dBm, 8x=-64.8 dBm 1x=-87.6 dBm, 2x=-83.7 dBm, 4x=-77.5 dBm, 6x=-71.6 dBm, 8x=-64.5 dBm Nominal Receive Sensitivity (w/ FEC) @ 7 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

10 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

15 MHz Channel Page 10-7 Chapter 10: Reference information Equipment specifications Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel 4.9 GHz 5.4 GHz 5.8 GHz 900 MHz 3.5 GHz 3.6 GHz 4.9 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 4.9 GHz 5.4 GHz 5.8 GHz 3.5 GHz 1x = -87.2 dBm, 2x = -83 dBm, 4x = -75.8 dBm, 6x = -69.6 dBm, 8x = -62.6 dBm 1x = -87.2 dBm, 2x = -83.3 dBm, 4x = -76.2 dBm, 6x = -

70.1 dBm, 8x = -63 dBm 1x = -87.7 dBm, 2x = -82.7 dBm, 4x = -75.5 dBm, 6x = -

69.6 dBm, 8x = -62.4 dBm 1x = -86.99 dBm, 2x = -82 dBm, 4x = -75.9 dBm, 6x = -

69.9 dBm, 8x = -62.9 dBm 1x=-87.4 dBm, 2x=-83 dBm, 4x=-76.9 dBm, 6x=-69.9 dBm, 8x=-63 dBm 1x=-86.4 dBm, 2x=-82.5 dBm, 4x=-76.4 dBm, 6x=-69.4 dBm, 8x=-62.9 dBm 1x = -86.1 dBm, 2x = -82.1 dBm, 4x = -74.8 dBm, 6x = -

68.8 dBm, 8x = -61.7 dBm 1x = -86.6 dBm, 2x = -81.3 dBm, 4x = -75.5 dBm, 6x = -

68.6 dBm, 8x = -62 dBm 1x = -85.8 dBm, 2x = -80.7 dBm, 4x = -74.6 dBm, 6x = -

68.7 dBm, 8x = -61 dBm 1x=-85.6 dBm, 2x=-81.7 dBm, 4x=-74.5 dBm, 6x=-68 dBm, 8x=-61.5 dBm 1x=-85.5 dBm, 2x=-80.5 dBm, 4x=-74.4 dBm, 6x=-68.4 dBm, 8x=-61.5 dBm 1x = -84.1 dBm, 2x = -80 dBm, 4x = -73 dBm, 6x = -66.4 dBm, 8x = -59.6 dBm 1x = -84.5 dBm, 2x = -82 dBm, 4x = -75 3.5Bm, 6x = -67.4 dBm, 8x = -60.2 dBm 1x = -84.1 dBm, 2x = -80 dBm, 4x = -73 dBm, 6x = -66.5 dBm, 8x = -59.4 dBm 1x=-83.9 dBm, 2x=-79.5 dBm, 4x=-73 dBm, 6x=-66 dBm, 8x=-58.5 dBm Page 10-8 Chapter 10: Reference information Equipment specifications Nominal Receive Sensitivity (w/ FEC) @

40 MHz Channel 3.6 GHz 4.9 GHz 5.4 GHz 5.8 GHz 1x=-82.8 dBm, 2x=-79 dBm, 4x=-73 dBm, 6x=-66 dBm, 8x=-59 dBm 1x=-83.9 dBm, 2x=-78.9 dBm, 4x=-72 dBm, 6x=-66 dBm, 8x=-56.6 dBm 1x=-83.7 dBm, 2x=-78.5 dBm, 4x=-72.4 dBm, 6x=-66 dBm, 8x=-58 dBm 1x=-83.8 dBm, 2x=-78.4 dBm, 4x=-72 dBm, 6x=-66 dBm, 8x=-57 dBm Performance ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Latency Maximum Deployment Range GPS Synchronization Quality of Service Link Budget Yes 1/16 2.5 ms or 5.0 ms Modulation Levels 2x 4x 6x 8x 3 - 5 ms MCS SNR (in dB) QPSK 16QAM 64QAM 256QAM 10 17 24 32 Up to 40 miles (64 km) Up to 120 miles (190 km) for 900 MHz Yes, via Autosync (CMM4), via UGPS Diffserv QoS Antenna Beam Width 900 MHz 65 sector antenna (Dual Slant) 3 GHz 5 GHz 90 sector for integrated (Dual polarity, slant +45 and -

45) 90 (3 dB roll off) sector for integrated (Dual polarity, H+V) Page 10-9 Chapter 10: Reference information Equipment specifications 900 MHz 13 dBi 3 GHz 5 GHz 17 dBi integrated 90 sector or external 17 dBi integrated 90 sector or external Antenna Gain (Does not include cable loss,

~1dB) Transmit Power Range Maximum Transmit Power Physical Sync/AUX port RJ45 Antenna Connection Surge Suppression EN61000-4-5 Mean Time Between Failure Environmental Temperature / Humidity 40 dB dynamic range (to EIRP limit by region) (1 dB step)

+27 dBm combined output (for 5 GHz)

+25 dBm combined output (for 3 GHz)

+25 dBm combined output (for 900MHz) 10/100/100BASE-T Ethernet Data PoE output (planned for future release) Sync input or output (Connection and powering of UGPS Sync input) 50 ohm, N-type (Connectorized version only) EN61000-4-5: 1.2 us/50 us, 500 V voltage waveform Recommended external surge suppressor: Cambium Networks Model # C000000L033A

> 40 Years IP66, IP67

-40C to +60C (-40F to +140F), 0-95% non-condensing Weight Connectorized Approx. 2.0 kg (4.5 lbs) Integrated Approx. 2.5 kg (5.5 lbs) Wind Survival Connectorized 322 km/h (200 mi/h) Integrated 200 km/h (124 mi/h) Dimension(HxWxD) Connectorized 26.0 x 13.4 x 6.4 cm (10.3 x 5.3 x 3.3) Integrated 37.0 x 37.0 x 6.3 cm (14.5 x 14.5 x 3.2) Power Consumption Input Voltage Mounting 15 W typical, 25 W max, 55 W max with Aux port PoE out enabled 48-59 V DC, 802.3at compliant Wall or Pole mount with Cambium Networks Model #

N000045L002A Page 10-10 Chapter 10: Reference information Equipment specifications Security Encryption 56-bit DES, FIPS-197 128-bit AES Page 10-11 Chapter 10: Reference information Equipment specifications Specifications for PMP 450i Series - SM The PMP 450i SM conforms to the specifications listed in Table 247. Table 247 PMP 450i Series - SM specifications Category Model Number Spectrum Channel Spacing Frequency Range Channel Bandwidth Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Nominal Receive Sensitivity (w/ FEC) @ 5 MHz Channel 3300 3900 MHz 4900 5925 MHz 3.5 GHz 3.6 GHz 4.9 GHz Specification PMP 450i SM 5, 7, 10, 15, 20, 30, and 40 Channel Bandwidth Configurable on 2.5 MHz increments 3300 3900 MHz 4900 - 5925 MHz 5, 7, 10, 15, 20, 30, and 40 MHz 5, 10, 15, 20, 30, and 40 MHz Cambium Proprietary 2x2 MIMO OFDM 10/100/1000BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v2c and v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID 1x = -92.6 dBm, 2x =-89.22 dBm, 4x = -83.19 dBm, 6x = -

76.5 dBm, 8x = -69.1 dBm 1x = -92 dBm, 2x = -88.08 dBm, 4x = -82.3 dBm, 6x = -

75.9 dBm, 8x = -68.6 dBm 1x = -92.5 dBm, 2x = -88.5 dBm, 4x = -81 dBm, 6x = -74.2 dBm, 8x = -66 dBm Page 10-12 Chapter 10: Reference information Equipment specifications 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 3.5 GHz 3.6 GHz 4.9 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 4.9 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz Nominal Receive Sensitivity (w/ FEC) @ 7 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

10 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

15 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel 1x = -93 dBm, 2x = -89.1 dBm, 4x = -81.5 dBm, 6x = -74.8 dBm, 8x = -67.4 dBm 1x = -92 dBm, 2x = -88.3 dBm, 4x = -80.8 dBm, 6x = -74 dBm, 8x = -66.2 dBm 1x = -92 dBm, 2x = -88.4 dBm, 4x = -81.4 dBm, 6x = -

75.37 dBm, 8x = -68.1 dBm 1x = -91.02 dBm, 2x = -87.87 dBm, 4x = -80.82 dBm, 6x =

-73.6 dBm, 8x = -67.32 dBm 1x = -90.787 dBm, 2x = -86.6 dBm, 4x = -80.2 dBm, 6x = -

73.52 dBm, 8x = -66.34 dBm 1x = -89.8 dBm, 2x = -86 dBm, 4x = -79.84 dBm, 6x = -

72.92 dBm, 8x = -66 dBm 1x = -90.2 dBm, 2x = -85.2 dBm, 4x = -78.8 dBm, 6x = -

71.4 dBm, 8x = -64.5 dBm 1x = -90 dBm, 2x = -85.8 dBm, 4x = -78.5 dBm, 6x = -72.2 dBm, 8x = -65.8 dBm 1x = -89.9 dBm, 2x = -84.9 dBm, 4x = -78.5 dBm, 6x = -

71.2 dBm, 8x = -63.8 dBm 1x = -88.57 dBm, 2x = -84.5 dBm, 4x = -78.4 dBm, 6x = -

71.47 dBm, 8x = -65.22 dBm 1x = -87.6 dBm, 2x = -84.1 dBm, 4x = -77.1 dBm, 6x = -

71.03 dBm, 8x = -64.8 dBm 1x = -88.2 dBm, 2x = -83.1 dBm, 4x = -76.9 dBm, 6x = -

70.5 dBm, 8x = -62.3 dBm 1x = -87.7 dBm, 2x = -83.9 dBm, 4x = -76.6 dBm, 6x = -

70.4 dBm, 8x = -63 dBm 1x = -88 dBm, 2x = -82.9 dBm, 4x = -76.7 dBm, 6x = -69.4 dBm, 8x = -62.3 dBm 1x = -87 dBm, 2x = -83.45 dBm, 4x = -76.25 dBm, 6x = -

70.33 dBm, 8x = -63.23 dBm 1x = -86.9 dBm, 2x = -82.9 dBm, 4x = -76.9 dBm, 6x = -

69.8 dBm, 8x = -62.8 dBm Page 10-13 Chapter 10: Reference information Equipment specifications Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

40 MHz Channel Performance ARQ Cyclic Prefix 4.9 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 4.9 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 4.9 GHz 5.4 GHz 5.8 GHz 1x = -87 dBm, 2x = -81.8 dBm, 4x = -75.8 dBm, 6x = -68.5 dBm, 8x = -61.4 dBm 1x = -87 dBm, 2x = -82.8 dBm, 4x = -75.6 dBm, 6x = -69.3 dBm, 8x = -61.6 dBm 1x = -85.9 dBm, 2x = -81.5 dBm, 4x = -74.8 dBm, 6x = -

68.7 dBm, 8x = -61.2 dBm 1x = -86 dBm, 2x = -80.9 dBm, 4x = -75 dBm, 6x = -67.9 dBm, 8x = -61.1 dBm 1x = -85.5 dBm, 2x = -80.6 dBm, 4x = -74.5 dBm, 6x = -

67.5 dBm, 8x = -61 dBm 1x = -84.9 dBm, 2x = -80.9 dBm, 4x = -73.2 dBm, 6x = -

67.4 dBm, 8x = -59.3 dBm 1x = -85.2 dBm, 2x = -80.2 dBm, 4x = -74.1 dBm, 6x = -

67.9 dBm, 8x = -59.8 dBm 1x = -84.9 dBm, 2x = -80 dBm, 4x = -73.2 dBm, 6x = -67.4 dBm, 8x = -59.4 dBm 1x = -83.2 dBm, 2x = -79 dBm, 4x = -72.4 dBm, 6x = -66 dBm, 8x = -58.4 dBm 1x = -82.5 dBm, 2x = -79 dBm, 4x = -71.3 dBm, 6x = -65.4 dBm, 8x = -58.3 dBm 1x=-84.2 dBm, 2x=-79.3 dBm, 4x=-72.3 dBm, 6x=-66 dBm, 8x=-56.8 dBm 1x=-84.2 dBm, 2x=-79.1 dBm, 4x=-73.1 dBm, 6x=-66 dBm, 8x=-56.9 dBm 1x=-83.6 dBm, 2x=-78.7 dBm, 4x=-72.5 dBm, 6x=-66.4 dBm, 8x=-56.3 dBm Yes 1/16 Page 10-14 Chapter 10: Reference information Equipment specifications Frame Period Modulation Levels

(Adaptive) Latency Maximum Deployment Range GPS Synchronization Quality of Service Link Budget Antenna Beam Width Antenna Gain (Does not include cable loss,

~1dB) 5 GHz 3 GHz Transmit Power Range Maximum Transmit Power Physical Sync/AUX port RJ45 Antenna Connection Surge Suppression EN61000-4-5 Mean Time Between Failure Environmental 2.5 ms or 5.0 ms Modulation Levels MCS SNR (in dB) 2x 4x 6x 8x QPSK 16QAM 64QAM 256QAM 10 17 24 32 3 - 5 ms Up to 40 miles (64 km) Yes, via Autosync (CMM4) Diffserv QoS 10 azimuth for 23 dBi integrated antenna

+23 dBi H+V, integrated or external

+19 dBi dual slant, integrated or external 40 dB dynamic range (to EIRP limit by region) (1 dB step)

+27 dBm combined output (for 5 GHz)

+25 dBm combined output (for 3 GHz) 10/100/1000BASE-T Ethernet Data PoE output (planned for future release) Sync input or output (Connection and powering of UGPS Sync input) 50 ohm, N-type (Connectorized version only) EN61000-4-5: 1.2us/50us, 500 V voltage waveform Recommended external surge suppressor: Cambium Networks Model # C000000L033A

> 40 Years IP66, IP67 Page 10-15 Chapter 10: Reference information Equipment specifications Temperature / Humidity

-40C to +60C (-40F to +140F), 0-95% non-condensing Weight Connectorized Approx. 2.0 kg (4.5 lbs) Integrated Approx. 2.5 kg (5.5 lbs) Wind Survival Connectorized 322 km/h (200 mi/h) Integrated 200 km/h (124 mi/h) Dimension(HxWxD) Connectorized 26.0 x 13.4 x 6.4 cm (10.3 x 5.3 x 3.3) Integrated 31.0 x 31.0 x 6.4 cm (12 x 12 x 2.5) Power Consumption Input Voltage Mounting Security Encryption 15 W typical, 25 W max, 55 W max with Aux port PoE out enabled 48-59 V DC, 802.3at compliant Wall or Pole mount with Cambium Networks Model #

N000045L002A 56-bit DES, FIPS-197 128-bit AES Page 10-16 Chapter 10: Reference information Equipment specifications Specifications for PTP 450i Series - BH The PTP 450i BH conforms to the specifications listed in Table 248. Table 248 PTP 450i Series - BH specifications Category Model Number Spectrum Channel Spacing Frequency Range Channel Bandwidth Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Nominal Receive Sensitivity (w/ FEC) @ 5 MHz Channel Nominal Receive Sensitivity (w/ FEC) @ 7 MHz Channel Specification PTP 450i BH 5, 10, 15, 20, 30, and 40 MHz Channel Bandwidth Configurable on 2.5 MHz increments 4900 - 5925 MHz 4900 5925 MHz 5, 10, 15, 20, 30, and 40 MHz 900 MHz 4.9 GHz 5.4 GHz 5.8 GHz 900 MHz Cambium Proprietary 2x2 MIMO OFDM 10/100/1000BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v2c and v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID 1x = -92.2 dBm, 2x = -90.2 dBm, 4x = -83.2 dBm, 6x = -

77.2 dBm, 8x = -71.2 dBm 1x = -93 dBm, 2x = -88.3 dBm, 4x = -82 dBm, 6x = -74.4 dBm, 8x = -67.9 dBm 1x = -93 dBm, 2x = -88.4 dBm, 4x = -81.3 dBm, 6x = -75.5 dBm, 8x = -67.8 dBm 1x = -93.2 dBm, 2x = -88.3 dBm, 4x = -80.8 dBm, 6x = -

74.3 dBm, 8x = -66.8 dBm 1x = -91 dBm, 2x = -86 dBm, 4x = -80 dBm, 6x = -74 dBm, 8x = -67 dBm Page 10-17 Chapter 10: Reference information Equipment specifications Nominal Receive Sensitivity (w/ FEC) @

10 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

15 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

40 MHz Channel Performance ARQ Cyclic Prefix Frame Period 900 MHz 4.9 GHz 5.4 GHz 5.8 GHz 4.9 GHz 5.4 GHz 5.8 GHz 900 MHz 4.9 GHz 5.4 GHz 5.8 GHz 4.9 GHz 5.4 GHz 5.8 GHz 4.9 GHz 5.4 GHz 5.8 GHz 1x = -90 dBm, 2x = -84 dBm, 4x = -79 dBm, 6x = -73 dBm, 8x = -66 dBm 1x = -90 dBm, 2x = -85 dBm, 4x = -78.6 dBm, 6x = -

72.5dBm, 8x = -65 dBm 1x = -87.6 dBm, 2x = -82.5 dBm, 4x = -76.5 dBm, 6x = -

70.5 dBm, 8x = -61.5dBm 1x = -89.9 dBm, 2x = -84.8 dBm, 4x = -78.5 dBm, 6x = -

71.4 dBm, 8x = -64 dBm 1x = -88 dBm, 2x = -83.9 dBm, 4x = -76.9 dBm, 6x = -70.7 dBm, 8x = -63.6 dBm 1x = -88 dBm, 2x = -84.2 dBm, 4x = -76.9 dBm, 6x = -70.8 dBm, 8x = -62.7 dBm 1x = -87.8 dBm, 2x = -82.8 dBm, 4x = -6.6 dBm, 6x = 69.3 dBm, 8x = -62.1 dBm 1x = -86 dBm, 2x = -82 dBm, 4x = -75 dBm, 6x = -69 dBm, 8x = -62 dBm 1x = -86.9 dBm, 2x = -82.5 dBm, 4x = -75.7 dBm, 6x = -

69.4 dBm, 8x = -62.3 dBm 1x = -84.5 dBm, 2x = -80.5 dBm, 4x = -73.4 dBm, 6x = -

66.4 dBm, 8x = -56.4 dBm 1x = -85.8 dBm, 2x = -81.7 dBm, 4x = -75 dBm, 6x = -68.4 dBm, 8x = -61.2 dBm 1x = -85 dBm, 2x = -80.7 dBm, 4x = -73.7 dBm, 6x = -66.5 dBm, 8x = -60 dBm 1x = -85.3 dBm, 2x = -80.5 dBm, 4x = -74.2 dBm, 6x = -

67.2 dBm, 8x = -60 dBm 1x = -84.6 dBm, 2x = -80 dBm, 4x = -73,3 dBm, 6x = -66.5 dBm, 8x = -59.1 dBm 1x=-84.1 dBm, 2x=-79.3 dBm, 4x=-73 dBm, 6x=-66 dBm, 8x=-58.8 dBm 1x=-84.5 dBm, 2x=-79.4 dBm, 4x=-73.3 dBm, 6x=-66.5 dBm, 8x=-58 dBm 1x=-84 dBm, 2x=-79 dBm, 4x=-72 dBm, 6x=-66 dBm, 8x=-

58 dBm Yes 1/16 2.5 ms or 5.0 ms Page 10-18 Chapter 10: Reference information Equipment specifications Modulation Levels

(Adaptive) Latency Maximum Deployment Range GPS Synchronization Quality of Service Link Budget Modulation Levels MCS SNR (in dB) 2x 4x 6x 8x QPSK 16QAM 64QAM 256QAM 10 17 24 32 3 - 5 ms Up to 40 miles (64 km) Yes, via Autosync (CMM4) Diffserv QoS Antenna Beam Width 900 MHz 37 azimuth for 12 dBi Yagi antenna 5 GHz 10 azimuth for 23 dBi integrated antenna 900 MHz 12 dBi Yagi antenna 5 GHz

+23 dBi H+V, integrated or external Antenna Gain (Does not include cable loss,

~1dB) Transmit Power Range Maximum Transmit Power Physical Sync/AUX port RJ45 Antenna Connection Surge Suppression EN61000-4-5 Mean Time Between Failure Environmental Temperature / Humidity 40 dB dynamic range (to EIRP limit by region) (1 dB step)

+27 dBm combined output 10/100/1000BASE-T Ethernet Data PoE output Sync input or output (Connection and powering of UGPS Sync input) 50 ohm, N-type (Connectorized version only) EN61000-4-5: 1.2us/50us, 500 V voltage waveform Recommended external surge suppressor: Cambium Networks Model # C000000L033A

> 40 Years IP66, IP67

-40C to +60C (-40F to +140F), 0-95% non-condensing Page 10-19 Chapter 10: Reference information Equipment specifications Weight Connectorized Approx. 2.0 kg (4.5 lbs) Integrated Approx. 2.5 kg (5.5 lbs) Wind Survival Connectorized 322 km/h (200 mi/h) Integrated 200 km/h (124 mi/h) Dimension(HxWxD) Connectorized 26.0 x 13.4 x 6.4 cm (10.25 x 5.25 x 3.25) Integrated 31.0 x 31.0 x 6.4 cm (12 x 12 x 2.5) Power Consumption Input Voltage Mounting Security Encryption 15 W typical, 25 W max, 55 W max with Aux port PoE out enabled 48-59 V DC, 802.3at compliant Wall or Pole mount with Cambium Networks Model #

N000045L002A 56-bit DES, FIPS-197 128-bit AES Page 10-20 Chapter 10: Reference information Equipment specifications Specifications for PMP 450b Series - SM The PMP 450b SM conforms to the specifications listed in Table 247. Table 249 PMP 450b Series - SM specifications Category Model Number Spectrum Channel Spacing Frequency Range Channel Bandwidth Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Nominal Receive Sensitivity (w/ FEC) @ 5 MHz Channel 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz Specification PMP 450b SM Configurable in 2.5 MHz increments 4900 - 5925 MHz 5, 10, 15, 20, 30, and 40 MHz Cambium Proprietary 2x2 MIMO OFDM 100/1000BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v2c and v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID 1x = -92.5 dBm, 2x = -88.5 dBm, 4x = -81 dBm, 6x = -74.2 dBm, 8x = -66 dBm 1x = -93 dBm, 2x = -89.1 dBm, 4x = -81.5 dBm, 6x = -74.8 dBm, 8x = -67.4 dBm 1x = -92 dBm, 2x = -88.3 dBm, 4x = -80.8 dBm, 6x = -74 dBm, 8x = -66.2 dBm 1x = -93 dBm, 2x = -89.1 dBm, 4x = -81.5 dBm, 6x = -74.8 dBm, 8x = -67.4 dBm 1x = -92 dBm, 2x = -88.3 dBm, 4x = -80.8 dBm, 6x = -74 dBm, 8x = -66.2 dBm 1x = -90.2 dBm, 2x = -85.2 dBm, 4x = -78.8 dBm, 6x = -

71.4 dBm, 8x = -64.5 dBm Page 10-21 Chapter 10: Reference information Equipment specifications Nominal Receive Sensitivity (w/ FEC) @

10 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

15 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz 1x = -90 dBm, 2x = -85.8 dBm, 4x = -78.5 dBm, 6x = -72.2 dBm, 8x = -65.8 dBm 1x = -89.9 dBm, 2x = -84.9 dBm, 4x = -78.5 dBm, 6x = -

71.2 dBm, 8x = -63.8 dBm 1x = -90 dBm, 2x = -85.8 dBm, 4x = -78.5 dBm, 6x = -72.2 dBm, 8x = -65.8 dBm 1x = -89.9 dBm, 2x = -84.9 dBm, 4x = -78.5 dBm, 6x = -

71.2 dBm, 8x = -63.8 dBm 1x = -88.2 dBm, 2x = -83.1 dBm, 4x = -76.9 dBm, 6x = -

70.5 dBm, 8x = -62.3 dBm 1x = -87.7 dBm, 2x = -83.9 dBm, 4x = -76.6 dBm, 6x = -

70.4 dBm, 8x = -63 dBm 1x = -88 dBm, 2x = -82.9 dBm, 4x = -76.7 dBm, 6x = -69.4 dBm, 8x = -62.3 dBm 1x = -87.7 dBm, 2x = -83.9 dBm, 4x = -76.6 dBm, 6x = -

70.4 dBm, 8x = -63 dBm 1x = -88 dBm, 2x = -82.9 dBm, 4x = -76.7 dBm, 6x = -69.4 dBm, 8x = -62.3 dBm 1x = -87 dBm, 2x = -81.8 dBm, 4x = -75.8 dBm, 6x = -68.5 dBm, 8x = -61.4 dBm 1x = -87 dBm, 2x = -82.8 dBm, 4x = -75.6 dBm, 6x = -69.3 dBm, 8x = -61.6 dBm 1x = -85.9 dBm, 2x = -81.5 dBm, 4x = -74.8 dBm, 6x = -

68.7 dBm, 8x = -61.2 dBm 1x = -87 dBm, 2x = -82.8 dBm, 4x = -75.6 dBm, 6x = -69.3 dBm, 8x = -61.6 dBm 1x = -85.9 dBm, 2x = -81.5 dBm, 4x = -74.8 dBm, 6x = -

68.7 dBm, 8x = -61.2 dBm 1x = -84.9 dBm, 2x = -80.9 dBm, 4x = -73.2 dBm, 6x = -

67.4 dBm, 8x = -59.3 dBm Page 10-22 Chapter 10: Reference information Equipment specifications Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

40 MHz Channel 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 1x = -85.2 dBm, 2x = -80.2 dBm, 4x = -74.1 dBm, 6x = -

67.9 dBm, 8x = -59.8 dBm 1x = -84.9 dBm, 2x = -80 dBm, 4x = -73.2 dBm, 6x = -67.4 dBm, 8x = -59.4 dBm 1x = -85.2 dBm, 2x = -80.2 dBm, 4x = -74.1 dBm, 6x = -

67.9 dBm, 8x = -59.8 dBm 1x = -84.9 dBm, 2x = -80 dBm, 4x = -73.2 dBm, 6x = -67.4 dBm, 8x = -59.4 dBm 1x=-84.2 dBm, 2x=-79.3 dBm, 4x=-72.3 dBm, 6x=-66 dBm, 8x=-56.8 dBm 1x=-84.2 dBm, 2x=-79.1 dBm, 4x=-73.1 dBm, 6x=-66 dBm, 8x=-56.9 dBm 1x=-83.6 dBm, 2x=-78.7 dBm, 4x=-72.5 dBm, 6x=-66.4 dBm, 8x=-56.3 dBm 1x=-84.2 dBm, 2x=-79.1 dBm, 4x=-73.1 dBm, 6x=-66 dBm, 8x=-56.9 dBm 1x=-83.6 dBm, 2x=-78.7 dBm, 4x=-72.5 dBm, 6x=-66.4 dBm, 8x=-56.3 dBm Performance ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Latency Yes 1/16 2.5 ms or 5.0 ms Modulation Levels MCS SNR (in dB) QPSK 16QAM 64QAM 256QAM 10 17 24 32 2x 4x 6x 8x 3 - 5 ms Page 10-23 Chapter 10: Reference information Equipment specifications Maximum Deployment Range GPS Synchronization Quality of Service Link Budget Antenna Beam Width Antenna Gain (Does not include cable loss,

~1dB) Transmit Power Range Maximum Transmit Power Physical 5 GHz Sync/AUX port RJ45 Antenna Connection Surge Suppression EN61000-4-5 Mean Time Between Failure Environmental Temperature / Humidity Up to 40 miles (64 km) Yes, via Autosync (CMM4) Diffserv QoS 15 azimuth for 17 dBi integrated antenna 30 elevation for 17 dBi integrated antenna

+17 dBi H+V, integrated 40 dB dynamic range (to EIRP limit by region) (1 dB step)

+27 dBm combined output 100/1000BASE-T Ethernet Data PoE output (planned for future release) Sync input or output (Connection and powering of UGPS Sync input) 50 ohm, N-type (Connectorized version only) EN61000-4-5: 1.2us/50us, 500 V voltage waveform

> 40 Years IP55

-40C to +60C (-40F to +140F), 0-95% non-condensing Weight Integrated Approx. 0.5 kg (1.1 lb. including mounting bracket) Wind Survival Integrated 190 km/h (118 mi/h) Dimension(HxWxD) Integrated 12.4 x 25.1 x 11.9 cm (4.9 x 9.9 x 4.7) Power Consumption Input Voltage Mounting Security 9 W nominal, 12 W peak 20 - 32 V DC, Wall or Pole mount Page 10-24 Chapter 10: Reference information Equipment specifications Encryption 56-bit DES, FIPS-197 128-bit AES Page 10-25 Chapter 10: Reference information Equipment specifications Specifications for PMP 450 Series - AP The PMP 450 AP conforms to the specifications listed in Table 250. Table 250 PMP 450 Series - AP specifications Category Model Number Spectrum Channel Spacing Frequency Range 2.4 GHz 3.5 GHz 3.65 GHz 5 GHz Specification PMP 450 AP 5, 7, 10, 15, 20 and 30 MHz Channel Bandwidth Configurable on 2.5 MHz increments 2400 2483.5 MHz 3300 3600 MHz 3500 3850 MHz 5470 5875 MHz Channel Bandwidth 3.5 and 3.65 GHz 5, 7, 10, 15, 20 and 30 MHz 2.4 and 5 GHz 5, 10, 15, 20 and 30 MHz OFDM Subcarriers Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Nominal Receive Sensitivity (w/ FEC) @ 5 MHz Channel 2.4 GHz 3.5 GHz 512 FFT Cambium Proprietary 2x2 MIMO OFDM 10/100/1000BaseT, half/full duplex, rate auto negotiated (802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP, TFTP, RADIUS HTTP, HTTPS, Telnet, FTP, SNMP v3, TFTP, Syslog 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID 1x = -92 dBm, 2x = -87.8 dBm, 4x = -80.4 dBm, 6x = -

74.4 dBm, 8x = -66.5 dBm 1x = -92.4 dBm, 2x = -88.3 dBm, 4x = -81.3 dBm, 6x =

-75.3 dBm, 8x = -67.7 dBm Page 10-26 Chapter 10: Reference information Equipment specifications 3.65 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.65 GHz 2.4 GHz 3.5 GHz 3.65 GHz 5.4 GHz 5.8 GHz 2.4 GHz 3.5 GHz 3.65 GHz 5.4 GHz 5.8 GHz 2.4 GHz 3.5 GHz 3.65 GHz Nominal Receive Sensitivity (w/ FEC) @ 7 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

10 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

15 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel 1x = -91 dBm, 2x = -86.1 dBm, 4x = -80.2 dBm, 6x = -

73.1 dBm, 8x = -66 dBm 1x = -88.7 dBm, 2x = -84 dBm, 4x = -77.6 dBm, 6x = -

71.6 dBm, 8x = -63.7 dBm 1x = -91.5 dBm, 2x = -87 dBm, 4x = -80.2 dBm, 6x = -

73.1 dBm, 8x = -66 dBm 1x = -90.5 dBm, 2x = -86.4 dBm, 4x = -80.3 dBm, 6x =

-73.4 dBm, 8x = -66.9 dBm 1x = -89.1 dBm, 2x = -85.1 dBm, 4x = -78.1 dBm, 6x =

-72.1 dBm, 8x = -64.5 dBm 1x = -89.9 dBm, 2x = -85.6 dBm, 4x = -80 dBm, 6x = -

73.5 dBm, 8x = -66.9 dBm 1x = -89.8 dBm, 2x = -85.6 dBm, 4x = -80 dBm, 6x = -

73 dBm, 8x = -66.3 dBm 1x = -89 dBm, 2x = -85.2 dBm, 4x = -78.1 dBm, 6x = -

72.1 dBm, 8x = -64.5 dBm 1x = -86.1 dBm, 2x = -82.2 dBm, 4x = -75.3 dBm, 6x =

-69.3 dBm, 8x = -61.3 dBm 1x = -86 dBm, 2x = -82.2 dBm, 4x = -75.1 dBm, 6x = -

69 dBm, 8x = -60 dBm 1x = -88.4 dBm, 2x = -84.1 dBm, 4x = -77.1 dBm, 6x =

-71.4 dBm, 8x = -65 dBm 1x = -88.5 dBm, 2x = -84.5 dBm, 4x = -77.5 dBm, 6x =

-71.5 dBm, 8x = -64.3 dBm 1x = -87.4 dBm, 2x = -83.7 dBm, 4x = -76.3 dBm, 6x =

-69.7 dBm, 8x = -62.2 dBm 1x = -84.2 dBm, 2x = -80.2 dBm, 4x = -73.2 dBm, 6x =

-67.2 dBm, 8x = -60 dBm 1x = -85 dBm, 2x = -80 dBm, 4x = -74.3 dBm, 6x = -67 dBm, 8x = -58 dBm 1x = -85 dBm, 2x = -85 dBm, 4x = -79 dBm, 6x = -72 dBm, 8x = -66 dBm 1x = -85 dBm, 2x = -85 dBm, 4x = -79 dBm, 6x = -72 dBm, 8x = -65 dBm 1x = -86 dBm, 2x = -86 dBm, 4x = -78 dBm, 6x = -71 dBm, 8x = -63 dBm Page 10-27 Chapter 10: Reference information Equipment specifications Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel 5.4 GHz 5.8 GHz 2.4 GHz 3.5 GHz 3.65 GHz 5.4 GHz 5.8 GHz Performance Subscribers Per Sector ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Latency Maximum Deployment Range Packets Per Second GPS Synchronization Quality of Service Link Budget 1x = -81 dBm, 2x = -81 dBm, 4x = -75 dBm, 6x = -68 dBm, 8x = -59 dBm 1x = -82 dBm, 2x = -82 dBm, 4x = -75 dBm, 6x = -69 dBm, 8x = -60 dBm 1x = -85.4 dBm, 2x = -80.4 dBm, 4x = -74 dBm, 6x = -

68 dBm, 8x = -61 dBm 1x = -85.5 dBm, 2x = -81.5 dBm, 4x = -74.5 dBm, 6x =

-68.2 dBm, 8x = -61.3 dBm 1x = -84 dBm, 2x = -79.5 dBm, 4x = -73.4 dBm, 6x = -

66.4 dBm, 8x = -59.2 dBm 1x = -81 dBm, 2x = -76.9 dBm, 4x = -70.9 dBm, 6x = -

63.8 dBm, 8x = -55.8 dBm 1x = -80.9 dBm, 2x = -76.8 dBm, 4x = -70 dBm, 6x = -

63.8 dBm, 8x = -55 dBm Up to 238 Yes 1/16 2.5 ms or 5.0 ms Modulation Levels MCS SNR (in dB) 2x 4x 6x 8x QPSK 16QAM 64QAM 256QAM 10 17 24 32 3 - 5 ms for 2.5 ms Frame Period 6-10 ms for 5.0 ms Frame Period Up to 40 miles (64 km) 12,500 Yes, via CMM3, CMM4 or UGPS Diffserv QoS Page 10-28 Chapter 10: Reference information Equipment specifications Antenna Gain (Does not include cable loss,

~1dB) 2.4 GHz 3.5 GHz 3.65 GHz 5 GHz Combined Transmit Power Maximum Transmit Power Physical Wind Survival Antenna Connection Environmental Temperature / Humidity Weight 2.4 GHz 3.5 GHz 3.6 GHz 5 GHz 18 dBi Dual Slant 16 dBi Dual Slant 16 dBi Dual Slant 17 dBi Horizontal and Vertical

-30 to +22 dBm (to EIRP limit by region) in 1 dB-

configurable intervals (2.4 GHz, 5 GHz)

-30 to +25 dBm (to EIRP limit by region) in 1 dB-

configurable intervals (3.5 GHz)

-30 to +25 dBm (to EIRP limit by region and channel bandwidth) in 1 dB-configurable intervals (3.6 GHz) 22 dBm combined OFDM (2.4 GHz, 5 GHz)

(dependent upon Region Code setting) 25 dBm combined OFDM (3.5 GHz, 3.6 GHz),

(dependent upon Region Code setting) 200 mph (322 kph) 50 ohm, N-type (Connectorized version only) IP66, IP67

-40C to +60C (-40F to +140F) /

0-95% non-condensing 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 5.9 kg (13 lbs) with antenna 2.5 kg (5.5 lbs) without antenna Dimension(HxWxD) 2.4 GHz Radio: 27 x 21 x 7 cm (10.6 x 8.3 x 2.8) Antenna: 112.2 x 24.5 x 11.7 cm (44.2 x 9.6 x 4.6) 3.5 GHz 3.6 GHz 5 GHz Radio: 27 x 21 x 7 cm (10.6 x 8.3 x 2.8) Radio: 27 x 21 x 7 cm (10.6 x 8.3 x 2.8) Radio: 27 x 21 x 7 cm (10.6 x 8.3 x 2.8) Page 10-29 Chapter 10: Reference information Equipment specifications Power Consumption Input Voltage Security Encryption Antenna: 51 x 13 x 7.3 cm (20.2 x 5.1 x 2.9) 14 W 22 to 32 VDC 56-bit DES, AES Page 10-30 Chapter 10: Reference information Equipment specifications Specifications for PMP 450 Series - SM The PMP 450 SM conforms to the specifications listed in Table 251. Table 251 PMP 450 Series - SM specifications Category Model Number Spectrum Channel Spacing Frequency Range 900 MHz Specification PMP 450 SM 5, 7, 10, 15, 20, 30, and 40 MHz Channel Bandwidth Configurable on 2.5 MHz increments 902 928 MHz 2.4 GHz 3.5 GHz 3.65 GHz 5 GHz 2400 2483.5 MHz 3300 3600 MHz 3500 3850 MHz 5470 5875 MHz Channel Bandwidth 900 MHz, 5, 7, 10, 15, and 20 MHz 2.4 GHz, 3.5 GHz, 3.65 GHz and 5 GHz OFDM Subcarriers Interface 5, 10, 15, 20, 30, and 40 MHz 2.4 GHz band does not support 40 MHz. 512 FFT MAC (Media Access Control) Layer Cambium Proprietary Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity 2x2 MIMO OFDM 10/100 BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID 900 MHz 1x = -91 dBm, 2x = -91 dBm, 4x = -85 dBm, 6x = -78 dBm, 8x = -70 dBm Page 10-31 Chapter 10: Reference information Equipment specifications Nominal Receive Sensitivity (w/ FEC) @ 5 MHz Channel Nominal Receive Sensitivity (w/ FEC) @ 7 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

10 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

15 MHz Channel 2.4 GHz 3.5 GHz 3.65 GHz 5.4 GHz 5.8 GHz 900 MHz 3.5 GHz 3.65 GHz 900 MHz 2.4 GHz 3.5 GHz 3.65 GHz 5.4 GHz 5.8 GHz 900 MHz 2.4 GHz 3.5 GHz 3.65 GHz 1x = -92.5 dBm, 2x = -89.9 dBm, 4x = -82.9 dBm, 6x =

-75.9, dBm, 8x = -67.9 dBm 1x = -93.5 dBm, 2x = -89.4 dBm, 4x = -83.5 dBm, 6x =

-76.4 dBm, 8x = -68.3 dBm 1x = -91.3 dBm, 2x = -89.1 dBm, 4x = -82.2 dBm, 6x =

-75.2 dBm, 8x = -67.3 dBm 1x = -89.3 dBm, 2x = -87.3 dBm, 4x = -80.3 dBm, 6x =

-74.3 dBm, 8x = -66.3 dBm 1x = -89 dBm, 2x = -87 dBm, 4x = -80 dBm, 6x = -73.9 dBm, 8x = -64.9 dBm 1x = -91 dBm, 2x = -84 dBm, 4x = -83 dBm, 6x = -77 dBm, 8x = -71 dBm 1x = -92.2 dBm, 2x = -88.5 dBm, 4x = -81.4 dBm, 6x =

-74.5 dBm, 8x = -67.6 dBm 1x = -90.4 dBm, 2x = -87.3 dBm, 4x = -80.6 dBm, 6x =

-73 dBm, 8x = -65.6 dBm 1x = -90 dBm, 2x = -83 dBm, 4x = -80 dBm, 6x = -74 dBm, 8x = -68 dBm 1x = -88 dBm, 2x = -88 dBm, 4x = -81 dBm, 6x = -75 dBm, 8x = -69 dBm 1x = -88 dBm, 2x = -88 dBm, 4x = -81 dBm, 6x = -76 dBm, 8x = -68 dBm 1x = -86 dBm, 2x = -86 dBm, 4x = -80 dBm, 6x = -73 dBm, 8x = -66 dBm 1x = -84 dBm, 2x = -84 dBm, 4x = -78 dBm, 6x = -72 dBm, 8x = -63 dBm 1x = -84 dBm, 2x = -84 dBm, 4x = -77 dBm, 6x = -71 dBm, 8x = -63 dBm 1x = -88.6 dBm, 2x = -85.4 dBm, 4x = -78.1 dBm, 6x =

-72.2 dBm, 8x = -65.2 dBm 1x = -88.5 dBm, 2x = -84.5 dBm, 4x = -77.5 dBm, 6x =

-71.5 dBm, 8x = -64.5 dBm 1x = -89.5 dBm, 2x = -84.5 dBm, 4x = -78.5 dBm, 6x =

-71.5 dBm, 8x = -65.1 dBm 1x = -87.3 dBm, 2x = -84.3 dBm, 4x = -77.3 dBm, 6x =

-70.3 dBm, 8x = -62.2 dBm Page 10-32 Chapter 10: Reference information Equipment specifications Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

40 MHz Channel 5.4 GHz 5.8 GHz 900 MHz 2.4 GHz 3.5 GHz 3.65 GHz 5.4 GHz 5.8 GHz 2.4 GHz 3.5 GHz 3.65 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.65 GHz 5.4 GHz 5.8 GHz Performance Subscribers Per Sector 1x = -84.5dBm, 2x = -82.5 dBm, 4x = -75.5 dBm, 6x = -

69.5 dBm, 8x = -59.5 dBm 1x = -84 dBm, 2x = -84 dBm, 4x = -77 dBm, 6x = -71 dBm, 8x = -63 dBm 1x = -87 dBm, 2x = -80 dBm, 4x = -77 dBm, 6x = -72 dBm, 8x = -65 dBm 1x = -86.9 dBm, 2x = -82.9 dBm, 4x = -75.9 dBm, 6x =

-69.9 dBm, 8x = -63.5 dBm 1x = -87.5 dBm, 2x = -83.5 dBm, 4x = -76.5 dBm, 6x =

-69.5 dBm, 8x = -63.1 dBm 1x = -86 dBm, 2x = -83 dBm, 4x = -76.2 dBm, 6x = -

68.2 dBm, 8x = -61 dBm 1x = -83.4 dBm, 2x = -81.7 dBm, 4x = -74.4 dBm, 6x =

-67.2 dBm, 8x = -57.3 dBm 1x = -84 dBm, 2x = -80.5 dBm, 4x = -74 dBm, 6x = -

66.9 dBm, 8x = -56 dBm 1x = -85.9 dBm, 2x = -80.9 dBm, 4x = -73.9 dBm, 6x =

-67.8 dBm, 8x = -60.9 dBm 1x = -86.5 dBm, 2x = -81.5 dBm, 4x = -74.5 dBm, 6x =

-68.2 dBm, 8x = -61.3 dBm 1x = -84.3 dBm, 2x = -80.3 dBm, 4x = -74.3 dBm, 6x =

-66.2 dBm, 8x = -58 dBm 1x = -82 dBm, 2x = -78.3 dBm, 4x = -72.3 dBm, 6x = -

65.3 dBm, 8x = -55.3 dBm 1x = -81.7 dBm, 2x = -78.6 dBm, 4x = -71.6 dBm, 6x =

-64.4 dBm, 8x = -54 dBm 1x=-83.1 dBm, 2x=-79.3 dBm, 4x=-72.9 dBm, 6x=-66 dBm, 8x=-56.3 dBm 1x=-83.6 dBm, 2x=-79.6 dBm, 4x=-72.3 dBm, 6x=-65.3 dBm, 8x=-54.4 dBm 1x=-82.4 dBm, 2x=-78 dBm, 4x=-71.2 dBm, 6x=-64.3 dBm, 8x=-51 dBm 1x=-82.5 dBm, 2x=-78.8 dBm, 4x=-70.7 dBm, 6x=-64.8 dBm, 8x=-51 dBm Up to 238 Page 10-33 Chapter 10: Reference information Equipment specifications ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Latency Yes 1/16 2.5 ms or 5.0 ms Modulation Levels MCS SNR (in dB) 2x 4x 6x 8x QPSK 16QAM 64QAM 256QAM 10 17 24 32 3 - 5 ms for 2.5 ms Frame Period 6-10 ms for 5.0 ms Frame Period Maximum Deployment Range Up to 40 miles (64 km) GPS Synchronization Quality of Service Link Budget Yes Diffserv QoS Antenna Gain (Does not include cable loss,

~1dB) 900 MHz 2.4 GHz 3.5 GHz 3.65 GHz 12 dBi Yagi antenna 7 dBi Dual Slant, integrated patch 8 dBi Dual Slant, integrated patch 19 dBi Flat Plate, integrated patch 8 dBi Dual Slant, integrated patch 19 dBi Flat Plate, integrated patch 5 GHz 9 dBi H+V, integrated patch 25 dBi H+V, integrated dish Combined Transmit Power Maximum Transmit Power Reflector antenna gain 2.4 GHz

-30 to +22 dBm (to EIRP limit by region) 2.4, 5 GHz

-30 to +25 dBm (to EIRP limit by region) 3.5, 3.6 GHz 25 dBm - 3 GHz 22 dBm combined OFDM (2.4 GHz, 5 GHz)

(dependent upon Region Code setting) 25 dBm combined OFDM (900 MHz, 3.5 GHz, 3.6 GHz), (dependent upon Region Code setting)

+12 dBi Page 10-34 Chapter 10: Reference information Equipment specifications 3.5 GHz 3.65 GHz 5 GHz CLIP Gain LENS Gain Other antenna (5 GHz only) Physical Wind Survival Antenna Connection Environmental Temperature / Humidity Weight 2.4 GHz 3.5 GHz 3.6 GHz 5 GHz Dimensions (H x W x D) Power Consumption Input Voltage Security Encryption

+11 dBi

+11 dBi

+15 dBi

+8 dBi

+5.5 dBi 200 mph (322 kph) 50 ohm, N-type (Connectorized version only) IP55

-40C to +60C (-40F to +140F) /

0-95% non-condensing 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 2.5 kg (5.5 lbs) for 450 ruggedized 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 2.5 kg (5.5 lbs) for 450 ruggedized 5.9 kg (13 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 3.5 kg (7.7 lbs) for 450d 30 x 9 x 9 cm (11.75 x 3.4 x 3.4) 50 x 50 x 38 cm (19.69 x 19.69 x 14.96) for 450d 31.0 x 31.0 x 6.4 cm (12 x 12 x 2.5) for 450 ruggedized 12 W 20 to 32 VDC 56-bit DES, AES Page 10-35 Chapter 10: Reference information Equipment specifications Specifications for PTP 450 Series - BH The PTP 450 BH conforms to the specifications listed in Table 252. Table 252 PTP 450 Series - BH specifications Category Model Number Spectrum Channel Spacing Frequency Range Specification PTP 450 BH 5, 7, 10, 15, 20, 30, and 40 MHz Channel Bandwidth Configurable on 2.5 MHz increments 902 to 928 MHz 3300 3600 MHz 3500 3850 MHz 5470 5875 MHz Channel Bandwidth 900 MHz 5, 7, 10, 15, and 20 MHz 3.5 GHz, 3.6 GHz, and 5 GHz 5, 7, 10, 15, 20 and 30 MHz 7 MHz Channel bandwidth configurable for 3.5 GHz and 3.65 GHz band only. OFDM Subcarriers Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity 512 FFT Cambium Proprietary 2x2 MIMO OFDM 10/100 BaseT, half/full duplex, rate auto negotiated (802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP, TFTP, RADIUS HTTP, HTTPS, Telnet, FTP, SNMP v2c and v3, TFTP, Syslog 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID 3.5 GHz OFDM: 1x = -92 dBm, 2x = -90 dBm, 4x = -83 dBm, 6x = -

76 dBm, 8x = -69 dBm Page 10-36 Chapter 10: Reference information Equipment specifications Nominal Receive Sensitivity (w/ FEC) @ 5 MHz Channel 3.6 GHz 5.4 GHz Nominal Receive Sensitivity (w/ FEC) @7 MHz Channel Nominal Receive Sensitivity (w/ FEC)

@10 MHz Channel Nominal Receive Sensitivity (w/ FEC)

@15 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel 5.8 GHz 3.5 GHz 3.6 GHz 3.5 GHz 3.6 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 5.4 GHz 5.8 GHz 3.5 GHz OFDM: 1x = -94 dBm, 2x = -89.3 dBm, 4x = -82.3 dBm, 6x

= -75.2 dBm, 8x = -68.4 dBm OFDM: 1x = -90.4 dBm, 2x = -86 dBm, 4x = -79.4 dBm, 6x

= -73.2 dBm, 8x = -65.4 dBm OFDM: 1x = -90 dBm, 2x = -85.4 dBm, 4x = -79.4 dBm, 6x

= -73.4 dBm, 8x = -64.9 dBm OFDM: 1x = -90 dBm, 2x = -88 dBm, 4x = -81 dBm, 6x = -

74 dBm, 8x = -67 dBm OFDM: 1x = -92 dBm, 2x = -87.3 dBm, 4x = -81.3 dBm, 6x

= -74.3 dBm, 8x = -66.4 dBm OFDM: 1x =-91 dBm, 2x = -87.2 dBm, 4x = -80 dBm, 6x = -

73 dBm, 8x = -65.6 dBm OFDM:1x=90.4dBm,2x=86.3dBm,4x=80dBm,6x=

73dBm,8x=64.5dBm OFDM:1x=87.6dBm,2x=82.5dBm,4x=76.5dBm,6x

=70.5dBm,8x=61.5dBm OFDM:1x=87.5dBm,2x=82.7dBm,4x=76.8dBm,6x

=70.5dBm,8x=61.4dBm OFDM:1x=89dBm,2x=85dBm,4x=78dBm,6x=

71.1dBm,8x=64.7dBm OFDM:1x=89dBm,2x=84.3dBm,4x=78dBm,6x=

71dBm,8x=63dBm OFDM:1x=85.6dBm,2x=81.6dBm,4x=74.5dBm,6x

=68.5dBm,8x=57.5dBm OFDM:1x=85.6dBm,2x=80.9dBm,4x=75dBm,6x=

68dBm,8x=58dBm OFDM:1x=88dBm,2x=84dBm,4x=77dBm,6x=70 dBm,8x=62.2dBm OFDM:1x=87.3dBm,2x=83.3dBm,4x=76.3dBm,6x

=69.3dBm,8x=62dBm OFDM:1x=84.5dBm,2x=80.5dBm,4x=73.4dBm,6x

=66.4dBm,8x=56.4dBm OFDM:1x=84.8dBm,2x=80.8dBm,4x=74.7dBm,6x

=66.4dBm,8x=56dBm OFDM:1x=86dBm,2x=82dBm,4x=75dBm,6x=68 dBm,8x=60dBm Page 10-37 Chapter 10: Reference information Equipment specifications Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel 3.6 GHz 5.4 GHz 5.8 GHz 5.4 GHz 5.8 GHz Performance ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Latency Packets Per Second Maximum Deployment Range GPS Synchronization Quality of Service Link Budget Combined Transmit Power

-

OFDM:1x=86dBm,2x=81.3dBm,4x=74.3dBm,6x=

67.3dBm,8x=59dBm OFDM:1x=82.5dBm,2x=78.5dBm,4x=71.5dBm,6x

=64.4dBm,8x=53.4dBm OFDM:1x=82.5dBm,2x=78.5dBm,4x=71.5dBm,6x

=64.4dBm,8x=54dBm OFDM:1x=81.8dBm,2x=77.5dBm,4x=71.5dBm,6x

=63.5dBm,8x=52.6dBm OFDM:1x=83.0dBm,2x=78.0dBm,4x=71.0dBm,6x

=63.3dBm Yes 1/16 2.5 ms or 5.0 ms Modulation Levels MCS SNR (in dB) 2x 4x 6x 8x QPSK 16QAM 64QAM 256QAM 10 17 24 32 3 - 5 ms for 2.5 ms frame period 6 - 10 ms for 5.0 ms frame period 12,500 Up to 40 miles (64 km) Yes, via Autosync (CMM4) Diffserv QoS 30 to +22 dBm (to EIRP limit by region) in 1 dB-

configurable intervals (5 GHz)

-30 to +25 dBm (to EIRP limit by region) in 1 dB-

configurable intervals (3.5 GHz)

-30 to +25 dBm (to EIRP limit by region and channel bandwidth) in 1 dB-configurable intervals (3.6 GHz) 3.5 GHz 8 dBi Dual Slant, integrated patch Page 10-38 Chapter 10: Reference information Equipment specifications Antenna Gain (Does not include cable loss,

~1dB) 3.65 GHz 19 dBi Flat Plate, integrated patch 8 dBi Dual Slant, integrated patch 19 dBi Flat Plate, integrated patch 5 GHz 9 dBi H+V, integrated patch 25 dBi H+V, integrated dish Transmit Power Range Maximum Transmit Power Reflector antenna gain 3.5 GHz 40 dB dynamic range (to EIRP limit by region) (1 dB step) 22 dBm combined OFDM (5 GHz) (dependent upon Region Code setting) 25 dBm combined OFDM (3.5 GHz, 3.6 GHz), (dependent upon Region Code setting)

+11 dBi Other antenna (5 GHz only) 3.65 GHz 5 GHz

+11 dBi

+15 dBi CLIP Gain

+8 dBi LENS Gain

+5.5 dBi Physical Sync/AUX port RJ45 Antenna Connection Surge Suppression EN61000-4-5 Mean Time Between Failure Environmental Temperature / Humidity Weight Wind Survival 10/100/1000BASE-T Ethernet Data PoE output Sync input or output (Connection and powering of UGPS Sync input) 50 ohm, N-type (Connectorized version only) EN61000-4-5: 1.2us/50us, 500 V voltage waveform Recommended external surge suppressor: Cambium Networks Model # C000000L033A

> 40 Years IP66, IP67

-40C to +60C (-40F to +140F), 0-95% non-condensing 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 200 mph (322 kph) Page 10-39 Chapter 10: Reference information Equipment specifications Dimension(HxWxD) Maximum Power Consumption Input Voltage Security Encryption 30 x 9 x 9 cm (11.75 x 3.4 x 3.4) 14 W 22 to 32 VDC 56-bit DES, AES Page 10-40 Chapter 10: Reference information Equipment specifications PSU specifications The PMP/PTP 450i AC+DC Enhanced Power Injector conforms to the specifications listed in Table 253. Table 253 PMP/PTP 450i AC power Injector specifications Category Dimensions Weight Temperature Humidity Waterproofing Altitude Specification 137 mm (5.4 in) x 56 mm (2.2 in) x 38 mm (1.5 in) 0.240 Kg (0.5 lbs)

-40C to +60C 90% non-condensing Not waterproof Sea level to 5000 meters (16000 ft) AC Input DC output voltage to the ODU AC connector Min 90 V AC, 57 63 Hz, max 264 V AC, 47 53 Hz. 58V +2V/- 0V IEC-320-C8 Efficiency Over Current Protection Hold up time Better than 85%, efficiency level VI Hiccup current limiting, trip point set between 120% to 150%

of full load current At least 10 milliseconds Warning Use the above PSU to only power up 450i and 450m products. Page 10-41 Chapter 10: Reference information Equipment specifications The PMP/PTP 450 power supply conforms to the specifications listed in Table 254. Table 254 PMP/PTP 450 power supply specifications (part number: N000900L001A) Category Dimensions Weight Temperature Humidity AC Input Specification 118 mm (4.66 in) x 45 mm (1.75 in) x 32 mm (1.25 in) 0.240 Kg (0.5 lbs) 0C to +40C 20 to 90%

90-264 VAC, 47 63 Hz, 0.5 A rms at 120 VAC, 0.25 A rms at 240 VAC. DC output voltage to the ODU AC connector 30 V 5%

IEC-320-C8 Efficiency Over Current Protection Better than 85%, efficiency level V Short circuit, with auto recovery; Should restart between every 0.5 to 2 sec. Hold up time 10mS min at max load, 120VAC Note The 30V PSU (part number: #N000900L001A) has to be used for PMP 450 900 MHz SM. Warning The PMP 450 Ruggedized High Gain Integrated Subscriber Module (Cambium part numbers C035045C014A and C036045C014A), while encapsulated in a 450i-type enclosure, contains 450 circuitry which must be powered via 30VDC. Powering these SMs with 56 VDC will damage the device. Page 10-42 Chapter 10: Reference information Data network specifications Data network specifications This section contains specifications of the PMP/PTP 450 platform Ethernet interface. Ethernet interface 450m/450i Series The 450m/450i Series Ethernet port conforms to the specifications listed in Table 255. Table 255 450m/450i Series Main and Aux Ethernet bridging specifications Ethernet Bridging Protocol QoS Main Ethernet port Aux Ethernet port Specification IEEE 802.3 compatible IEEE 802.1p, IEEE 802.1Q, IEEE 802.1ad, DSCP IPv4 10/100/1000 BaseT, half/full duplex, rate auto negotiated 10/100 BaseT, half/full duplex, rate auto negotiated 1700 Bytes Maximum Ethernet Frame Size 450/450b Series Table 256 450 Series Ethernet bridging specifications Ethernet Bridging Protocol QoS Interface Specification IEEE 802.3 compatible IEEE 802.1p, IEEE 802.1Q, IEEE 802.1ad, DSCP IPv4 10/100/1000 BaseT, half/full duplex, rate auto negotiated Maximum Ethernet Frame Size 1700 Bytes Note Practical Ethernet rates depend on network configuration, higher layer protocols and platforms used. Over the air throughput is restricted to the rate of the Ethernet interface at the receiving end of the link. Page 10-43 Chapter 10: Reference information Wireless specifications Wireless specifications This section contains specifications of the 450 Platform Family wireless interface. These specifications include RF bands, channel bandwidth, spectrum settings, maximum power and link loss. General wireless specifications The wireless specifications that apply to all 450 Platform variants are listed under Table 257. Table 257 450 Platform Family - wireless specifications Item Channel selection Manual power control Duplex scheme Range Specification Manual selection (fixed frequency). To avoid interference to other users of the band, maximum power can be set lower than the default power limit. Adaptive TDD Band 900 MHz Range 120 mi / 193 km Platform PMP 450i Series - AP and PMP 450 Series - SM PMP 450 Series PMP/PTP 450 Series 2.4 GHz 3.5 GHz 40 mi / 64 km 40 mi / 64 km (PMP) 186 mi/ 299 km (PTP) 40 mi / 64 km (PMP) 186 mi/ 299 km (PTP) 40 mi / 64 km (PMP) 186 mi/ 299 km (PTP) 3.65 GHz PMP/PTP 450 Series 5 GHz PMP/PTP 450/450i/450b Series and PMP 450m Series AP Over-the-air encryption Error Correction DES, AES Rate 3/4 RS coder Page 10-44 Chapter 10: Reference information Wireless specifications Link Range and Throughput Link range and throughput estimates are based on site-specific attributes and configuration parameters. For the most up-to-date information on link range and throughput for your equipment see the Capacity Planner and LINKPlanner software tools:

For average-deployment link range and throughput planning information, see:

https://support.cambiumnetworks.com/files/capacityplanner/

For site-specific link range and throughput planning information, see:

https://support.cambiumnetworks.com/files/linkplanner Page 10-45 Chapter 10: Reference information Country specific radio regulations Country specific radio regulations This section describes how the 450 Platform Family complies with the radio regulations that are enforced in various countries. Caution Changes or modifications not expressly approved by Cambium could void the users authority to operate the system. Type approvals This system has achieved Type Approval in various countries around the world. This means that the system has been tested against various local technical regulations and found to comply. The frequency bands in which the system operates may be unlicensed and, in these bands, the system can be used provided it does not cause interference. The system is not guaranteed protection against interference from other ODUs and installations. The radio specification type approvals that have been granted for 450 Platform frequency variants are listed in Table 258. Table 258 Radio certifications Variant 900 MHz PMP 450i Region Canada Specification (Type Approvals) RSS Gen and RSS 210 USA Mexico Canada USA Canada Europe Canada USA USA Canada USA 2.4 GHz PMP 450 3.5 GHz PMP/PTP 450 3.6 GHz PMP/PTP 450 4.9 GHz PMP/PTP 450i/450b 5.1 GHz PMP/PTP 450i/450b 5.1 GHz PMP/PTP 450m USA 5.2 GHz PMP/PTP 450m USA Europe FCC Part 15.247 NOM-121-SCT1-2009 RSS Gen and RSS 210 FCC Part 15 Class B RSS Gen and RSS 192 ETSI EN 302 326-2 V1.2.2 RSS Gen and RSS 197 FCC Part 15 Class B FCC Part 90 Subpart Y RSS Gen and RSS 111 FCC Part 15 Class B FCC Part 15E and Part 15B ETSI EN 302 625 V1.1.1 FCC Part 15E and Part 15B Page 10-46 Chapter 10: Reference information Country specific radio regulations Variant 5.2 GHz PMP/PTP 450i/450b Region USA Canada Europe USA 5.4 GHz PMP/PTP 450m USA 5.4 GHz PMP/PTP 450 and 450i 5.8 GHz PMP/PTP 450 and 450i Canada Europe Canada USA Europe 5.8 GHz PMP/PTP 450m USA Canada Europe Specification (Type Approvals) FCC Part 15 Class B RSS Gen and RSS 247 ETSI EN 301 893 v1.6.1 FCC Part 15 Class B FCC Part 15E and Part 15B RSS Gen and RSS 247 ETSI EN 301 893 v1.8.1 ETSI EN 301 893 v2.1.1 Clause 4.8 RSS Gen and RSS 210 FCC Part 15 Class B ETSI EN 302 502 v1.2.1 FCC Part 15E and Part 15B RSS Gen and RSS 247 ETSI EN 302 502 v2.1.1 DFS for 2.4 and 5 GHz Radios Dynamic Frequency Selection (DFS) is a requirement in several countries and regions for 2.4 and 5 GHz unlicensed systems to detect radar systems and avoid co-channel operation. The details of DFS operation and channels available for each Country Code, including whether DFS is active on the AP, SM, which DFS regulation apply, and any channel restrictions are shown in Table 259 on page 10-47. Table 259 Country & Bands DFS setting Region Code North America Country Code Band AP SM USA Canada 2.4 GHz 5.2 GHz 5.4 GHz 5.8 GHz 2.4 GHz 5.2 GHz 5.4 GHz No effect FCC DFS FCC DFS No effect No effect FCC DFS FCC DFS Page 10-47 No effect No effect No effect No effect No effect No effect No effect Weather Radar Notch-Out No No No No No No No Chapter 10: Reference information Country specific radio regulations Mexico South America Brazil Europe ETSI Other-

Regulatory Other-FCC Other-ETSI 5.8 GHz 2.4 GHz 5.2 GHz 5.4 GHz 5.8 GHz 5.4 GHz 5.8 GHz 5.4 GHz 5.8 GHz 2.4 GHz 5.2 GHz 5.4 GHz 5.8-GHz 5.4 GHz 5.8 GHz No effect No effect ANATEL Res506-

2008 ANATEL Res506-

2008 No effect ETSI EN 301 893 v1.7.1 DFS No effect ETSI EN 301 893 v1.7.1 DFS ETSI EN 302 502 v1.2.1 DFS No effect FCC DFS FCC DFS No effect No effect No effect No effect No effect No effect No effect No effect ETSI EN 301 893 v1.7.1 DFS ETSI EN 302 502 v1.2.1 DFS No effect No effect No effect No effect ETSI EN 301 893 v1.7.1 DFS ETSI EN 301 893 v1.7.1 DFS ETSI EN 302 502 v1.2.1 DFS ETSI EN 302 502 v1.2.1 DFS No No No No No No No Yes Yes No No No No No No Page 10-48 Chapter 10: Reference information Equipment Disposal Equipment Disposal Waste (Disposal) of Electronic and Electric Equipment Waste (Disposal) of Electronic and Electric Equipment Please do not dispose of Electronic and Electric Equipment or Electronic and Electric Accessories with your household waste. In some countries or regions, collection systems have been set up to handle waste of electrical and electronic equipment. In European Union countries, please contact your local equipment supplier representative or service center for information about the waste collection system in your country. Country specific maximum transmit power Maximum transmit power 900 MHz band Table 260 Default combined transmit power per country 900 MHz band PMP 450i Series Countries Device Type

(AP/SM/BH) Antenna Type Channel BW Conducted Power Limit

(dBm) EIRP Limit

(dBm) USA, Mexico, Canada, Other FCC Brazil, Panama, Colombia, Venezuela Any Any Any Any Ecuador Any Any 5 MHz 7 MHz 10 MHz 15 MHz 20 MHz 5 MHz 7 MHz 10 MHz 15 MHz 20 MHz

-

-

-

-

-

-

-

-

-

-

Page 10-49 36 36 36 36 36 36 36 36 36 36 Chapter 10: Reference information Equipment Disposal Countries Device Type

(AP/SM/BH) Antenna Type Channel BW Conducted Power Limit

(dBm) EIRP Limit

(dBm) 5 MHz 7 MHz 10 MHz 15 MHz 20 MHz Any 5 MHz 7 MHz 10 MHz 15 MHz 25 dBm 25 dBm 25 dBm 25 dBm 25 dBm

-

19 dBm 19 dBm 19 dBm 19 dBm

-

-

-

-

-

-

30 30 30 36 Other Any Australia, New Zealand Any Any Any Maximum transmit power 2.4 GHz band Table 261 Default combined transmit power per country 2.4 GHz band PMP/PTP 450 Series Countries USA, Canada, Other FCC Device Type AP SM, BH Antenna Type Channel BW Conducted Power Limit

(dBm) EIRP Limit

(dBm) Sector Integrated Reflector Integrated Dish

(450d) Any Any Any Any Any 18

-

24 11 30 36 36 36 36

-

Other Any Any Page 10-50 Chapter 10: Reference information Equipment Disposal Maximum transmit power 3.5 GHz band Table 262 Default combined transmit power per country 3.5 GHz band PMP/PTP 450 Series Countries Device Type Antenna Type Channel BW Conducted Power Limit

(dBm) EIRP Limit

(dBm) Other-ETSI Brazil, China, India, Indonesia, Mexico, Other Canada Australia AP Sector SM, BH Any Any Any Any Any Any Any Any Any Any Any Any

-

-

-

-

-

66 63

-

62 63 Page 10-51 Chapter 10: Reference information Equipment Disposal Maximum transmit power 3.65 GHz band Table 263 Default combined transmit power per country 3.65 GHz band PMP/PTP 450 Countries Device Type Antenna Type Channel BW Conducted Power Limit

(dBm) EIRP Limit

(dBm) Australia, India, Indonesia, Mexico, Other Other-ETSI Canada, USA, Other-FCC Any Any AP SM, BH AP SM, BH Any Sector Integrated Reflector Integrated Dish

(450d) Any Any Any

-

-

25

-

-

18

-

66 63 43 Maximum transmit power 4.9 GHz band Table 264 Default combined transmit power per country 4.9 GHz band PMP/PTP 450i Series Countries Device Type Antenna Type Channel BW Conducted Power Limit

(dBm) EIRP Limit

(dBm) USA, Mexico, Canada, Other FCC AP Sector Omni Flate plate SM, BH 4ft parabolic 40 40 39 35 36 35 51 51 50 52 55 24 24 23 24 24 23 24 24 23 24 24 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz Page 10-52 Chapter 10: Reference information Equipment Disposal 6ft parabolic Brazil Other Any Any Any Any 20 MHz 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz Any 23 24 24 23 23 27 27 27 56 52 55 58 54 57 60

-

Table 265 Default combined transmit power per country 4.9 GHz band PMP 450b Series Countries Device Type Antenna Type Channel BW Conducted Power Limit

(dBm) EIRP Limit

(dBm) 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 26 26 26 24

-

-

51 51 51 51 51 51 FCC SM 16 dBi Page 10-53 Chapter 10: Reference information Equipment Disposal Maximum transmit power 5.1 GHz band Table 266 Default combined transmit power per Country 5.1 GHz band PMP/PTP 450i Series Countries Device Type Antenna Type Channel BW Conducted Power Limit

(dBm) EIRP Limit

(dBm) USA, Other FCC AP Sector Omni SM, BH Flat plate 4ft parabolic Mexico Any Any 12 15 14 16 16 16 16 19 22 23

-2 1

-

3 3 3 6 9 9 11

-

-

-

-

-

-

5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 20 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 20 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Page 10-54 30 33 34 36 36 36 28 31 34 35 47 50 51 31 31 31 39 42 43 45 17 20 21 23 23 23 Chapter 10: Reference information Equipment Disposal Countries Device Type Antenna Type Channel BW Other ETSI Any Any Any Any Other ETSI Any Any Any 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz Conducted Power Limit

(dBm) 27

-

-

-

-

-

-

-

-

EIRP Limit

(dBm)

-

33 36 37 39 33 36 37 39 Table 267 Default combined transmit power per country 5.1 GHz band PMP 450b Series Countries Device Type Antenna Type Channel BW Conducted Power Limit

(dBm) EIRP Limit

(dBm) 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 24 27 27 27 27 27 47 50 51 53 53 53 FCC SM 16 dBi Page 10-55 Chapter 10: Reference information Equipment Disposal Table 268 Default combined transmit power per Country 5.1 GHz band PMP 450m Series Countries Device Type Antenna Type Channel BW EIRP Limit

(dBm) USA AP Sector ETSI AP Sector Other Any Any Other ETSI Any Any Mexico Any Any 5 MHz 10 MHz 15 MHz 20 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 33 34 36 36 33 36 37 39 42 42 42 42 36 36 36 36 17 20 21 23 Page 10-56 Chapter 10: Reference information Equipment Disposal Maximum transmit power 5.2 GHz band Note The selection of 5 MHz channel is not available for the PMP 450 AP and the PTP 450 BHM. It is available for the PMP/PTP 450i AP/SM and the PMP 450m AP. Table 269 Default combined transmit power per country 5.2 GHz band PMP/PTP 450i Series Countries Device Type Antenna Type Channel BW Conducted Power Limit

(dBm) EIRP Limit

(dBm) USA, Other FCC AP Sector Omni SM, BH Flat plate 4ft parabolic Mexico Any Any Other Any Any 6 9

-

12

-

-

10 13 16

-7

-4

-1

-13

-11

-8

-

-

-

-

-

-

27 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Any Page 10-57 24 27 28 30 30 30 22 25 28 20 23 26 19 22 25 24 27 28 30 30 30

-

Chapter 10: Reference information Equipment Disposal Table 270 Default combined transmit power per country 5.2 GHz band PMP 450b Series Countries Device Type Antenna Type Channel BW Conducted Power Limit

(dBm) EIRP Limit

(dBm) FCC SM 16 dBi Other SM 16 dBi 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz

-

22 22 22 22 22 27 27 27 27 27 27 24 27 28 30 30 30

-

-

-

-

-

-

Page 10-58 Chapter 10: Reference information Equipment Disposal Table 271 Default combined transmit power per Country 5.2 GHz band PMP 450m Series Countries Device Type Antenna Type Channel BW EIRP Limit

(dBm) USA, Other FCC AP Sector Mexico Any Any Other Any Any 5 MHz 10 MHz 15 MHz 20 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 40 MHz 24 27 28 30 30 24 27 28 30 30 42 42 42 42 42 Page 10-59 Chapter 10: Reference information Equipment Disposal Maximum transmit power 5.4 GHz band Table 272 Default combined transmit power per country 5.4 GHz band PMP 450m Series Countries Device Type Antenna Type Channel BW EIRP Limit (dBm) FCC AP Sector ETSI AP Sector RoW AP Sector RoW Other

-

-

5 MHz 10 MHz 15 MHz 20 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 40 MHz

-

24 27 28 30 30 24 27 28 30 30 42 42 42 42 42 No EIRP Limit Note The selection of 5 MHz channel is not available for the PMP 450 AP and the PTP 450 BHM. It is available for the PMP/PTP 450i AP/SM and the PMP 450m AP. Power reduction at the band edges is required in some cases. Page 10-60 Chapter 10: Reference information Equipment Disposal Table 273 Default combined transmit power per country 5.4 GHz band PMP/PTP 450i Series Device Type Antenna Type Channel BW Conducted Power Limit

(dBm) EIRP Limit

(dBm) Countries USA, Other FCC AP Sector Omni SM, BH Flat plate 4ft parabolic Brazil Any Any Mexico Any Any Other Any Any 24 27 28 30 30 30 22 25 28 20 23 26 21 24 27 24 27 28 30 30 30 24 27 28 30 30 30

-

6 9

-

12

-

-

10 13 16

-7

-4

-1

-6

-3 0

-

19

-

23

-

-

-

-

-

-

-

-

27 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Any Page 10-61 Chapter 10: Reference information Equipment Disposal Countries Device Type Antenna Type Channel BW Conducted Power Limit

(dBm) EIRP Limit

(dBm) ETSI Any Any Australia Any Any 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz

-

-

-

-

-

-

-

-

-

-

-

-

24 27 28 30 30 30 24 27 28 30 30 30 Page 10-62 Chapter 10: Reference information Equipment Disposal Table 274 Default combined transmit power per country 5.4 GHz band PMP 450b Series Countries Device Type Antenna Type Channel BW Conducted Power Limit

(dBm) EIRP Limit

(dBm) 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz

-

22 22 22 22 13 27 27 27 27 27 27 24 27 28 30 30 30 24 27 28 30 30 30 FCC SM 16 dBi ETSI SM 16 dBi Page 10-63 Chapter 10: Reference information Equipment Disposal Table 275 Default combined transmit power per country 5.4 GHz band PMP 450 Series Conducted Power Limit

(dBm) Antenna Type Device Type Channel BW Countries United States, Canada, Brazil, Australia, Denmark, Finland, Germany, Greece, Liechtenstein, Norway, Portugal, Spain, UK, Vietnam Austria, Belgium, Bosnia &

Herzegovina, Bulgaria, Croatia, Cyprus, Czech Republic, France, , Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Macedonia, Malta, Netherlands, Poland, Romania, Slovakia, Slovenia , Sweden Algeria AP Sector (18 dBi 1dB cable loss) AP Sector (18 dBi 1dB cable loss) AP Sector (18 dBi 1dB cable loss) Other AP Sector (18 dBi 1dB cable loss) 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MH 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MH

-

10

-

13

-

-

-

10

-

13

-

-

-

10

-

13

-

-

-

19

-

19

-

-

EIRP Limit

(dBm) 24 27 28 30 30 30 24 27*

28 30 30 30 30 30 30 30 30 30 No EIRP limit

(*) At 5.4 GHz, EU regulations are harmonized. 5600 5650 MHz excluded, as ten minute Channel Availability Check (CAC) is required Page 10-64 Chapter 10: Reference information Equipment Disposal Maximum transmit power 5.8 GHz band Table 276 Default combined transmit power per Country 5.8 GHz band PMP 450m Series Countries Device Type Antenna Type Channel BW EIRP Limit (dBm) USA, Other FCC AP Sector Mexico AP Sector Other AP Sector ETSI AP Sector 5 MHz 10 MHz 15 MHz 20 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 40 MHz 36 36 36 36 36 30 33 34 36 36 42 42 42 42 42 30 33 34 36 36 Table 277 Default combined transmit power per country 5.8 GHz band PMP/PTP 450i Series Countries Device Type AP Antenna Type Channel BW Conducted Power Limit (dBm) EIRP Limit

(dBm) Sector, Omni 5 MHz 10 MHz 15 MHz

-

-

-

36 36 36 Page 10-65 Chapter 10: Reference information Equipment Disposal Device Type Antenna Type Channel BW Conducted Power Limit (dBm) EIRP Limit

(dBm) Countries USA, Canada, Brazil, Other FCC SM, BH Flat plate, 4ft parabolic, 6ft parabolic Mexico Any Any Other Any Any 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz

-

-

-

27 27

(26 for 5733 MHz and below) 27 27 27 27

-

-

-

-

-

-

27 36 36 36

-

-

-

-

-

-

30 33 34 36 36 36

-

Table 278 Default combined transmit power per country 5.8 GHz band PMP 450b Series Countries Device Type Antenna Type Channel BW Conducted Power Limit

(dBm) EIRP Limit

(dBm) FCC SM 16 dBi ETSI SM 16 dBi 43 43 43 43 43 43 30 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 27 27 27 27 27 27 27 Page 10-66 Chapter 10: Reference information Equipment Disposal Other ETSI SM 16 dBi 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 27 27 27 27 27 19 19 19 19 19 19 33 34 36 36 36 30 33 34 36 36 36 Table 279 Default combined transmit power per country 5.8 GHz band PMP 450 Series Conducted Power Limit

(dBm) Device Type Antenna Type Countries Channel BW Australia, India, United States AP Sector (18 dBi 1dB cable loss) Vietnam AP Sector (18 dBi 1dB cable loss) Brazil AP Sector (18 dBi 1dB cable loss) 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 19 19

-

19

-

7 10

-

13

-

-

-

-

-

-

-

Page 10-67 EIRP Limit

(dBm) 36 36 36 36 36 24 27 28 30 30 30 36 36 36 36 36 Chapter 10: Reference information Equipment Disposal Canada AP Sector (18 dBi 1dB cable loss) AP Sector (18 dBi 1dB cable loss) Denmark, Finland, Germany, Greece, Iceland, Ireland, Liechtenstein, Norway, Portugal, Serbia, Spain, Switzerland, United Kingdom, Indonesia AP Sector (18 dBi 1dB cable loss) 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz

-

9 19

-

19

-

-

-

16

-

19

-

-

13 19

-

19 36 26 36 36 36 36 36 30 33 34 36 36 36 30 33 34 36 Page 10-68 Chapter 10: Reference information Equipment Disposal Country specific frequency range Frequency range 900 MHz band Table 280 Frequency range per country 900 MHz band Region Country Other North America Oceania South America Other Other-FCC Canada United States Mexico Puerto Rico Australia New Zealand Brazil Ecuador Colombia Panama Venezuela Channel center Frequency limits (MHz) Lower 902 902 902 902 Upper 928 928 928 928 902 902 915 928 928 928 915 920.5 (7 MHz) 919.5 (5 MHz) 928 924.5 (7 MHz) 925.5 (5 MHz) 902 915 902 902 902 902 907.5 928 928 928 928 928 Page 10-69 Chapter 10: Reference information Equipment Disposal Frequency range 2.4 GHz band Table 281 Frequency range per country 2.4 GHz band PMP/PTP 450 Series Countries Antenna Type Channel BW Any Canada, United States, Other, Other-

FCC 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz Channel center Frequency limits (MHz) Lower 2402.5 2405 2407.5 2410 Upper 2481 2478.5 2476 2473.5 2415 2468.5 Frequency range 3.5 GHz band Table 282 Frequency range per country 3.5 GHz band PMP/PTP 450/450i Series Countries Antenna Type Channel BW Brazil, Other-

ETSI Any Any China, Indonesia 5 MHz 7 MHz 10 MHz 20 MHz 5 MHz 7 MHz 10 MHz 20 MHz Channel center Frequency limits (MHz) Lower 3402.5 3403.5 Upper 3597.5 3596.5 3405 3410 3302.5 3303.5 3305 3310 3595 3590 3397.5 3396.5 3395 3390 Page 10-70 Chapter 10: Reference information Equipment Disposal Frequency range 3.65 GHz band Table 283 Frequency range per country 3.65 GHz band PMP/PTP 450/450i Series Countries Antenna Type Channel BW Australia, India, Other Any Other ETSI Any Indonesia Any Mexico Any 5 MHz 7 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 7 MHz 10 MHz 20 MHz 40 MHz 5 MHz 10 MHz 20 MHz 40 MHz Channel center Frequency limits (MHz) Lower 3302.5 3303.5 3305 3307.5 Upper 3797.5 3796.5 3795 3792.5 3310 3315 3320 3402.5 3405 3407.5 3410 3415 3420 3602.5 3603.5 3605 3610 3620 3302.5 3305 3310 3320 3790 3785 3780 3847.5 3845 3842.5 3840 3835 3830 3797.5 3796.5 3795 3790 3780 3747.5 3745 3740 3730 Page 10-71 Chapter 10: Reference information Equipment Disposal Frequency range 4.9 GHz band Table 284 Frequency range per country 4.9 GHz band PMP/PTP 450i/450b Series Countries Antenna Type Channel BW Any USA, Mexico, Canada, Other FCC Brazil Any Other Any 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower 4942.5 4945 4947.5 4950 Upper 4987.5 4985 4982.5 4980 4912.5 4915 4917.5 4920 4942.5 4945 4947.5 4950 4955 4960 4987.5 4985 4982.5 4980 4987.5 4985 4982.5 4980 4975 4970 Table 285 Frequency range per country 4.9 GHz band PMP 450b Series Channel center Frequency limits (MHz) Lower 4942.5 Upper 4987.5 4945 4947.5 4950 4955 4960 4985 4982.5 4980 4975 4970 Countries Antenna Type Channel BW FCC 16 dBi 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Page 10-72 Chapter 10: Reference information Equipment Disposal Frequency range 5.1 GHz band Table 286 Frequency range per country 5.1 GHz band PMP/PTP 450i Series Countries Antenna Type Channel BW United States, FCC Any ETSI Any Other Any 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower 5157.5 5160 5170 5170 5182.5 5187.5 5155 5155 5157.5 5160 5152.5 5155 5157.5 5160 5165 5170 Upper 5247.5 5245 5242.5 5240 5235 5230 5245 5245 5242.5 5240 5247.5 5245 5242.5 5240 5235 5230 Table 287 Frequency range per country 5.1 GHz band PMP 450b Series Channel center Frequency limits (MHz) Lower 5155 5155 Upper 5247.5 5245 5157.5 5160 5165 5170 5242.5 5240 5235 5230 Countries Antenna Type Channel BW FCC 16 dBi 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Page 10-73 Chapter 10: Reference information Equipment Disposal Table 288 Frequency range per country 5.1 GHz band PMP 450m Series Countries Antenna Type Channel BW United States, FCC Any ETSI Any Other Any 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz Channel center Frequency limits (MHz) Lower 5162.5 5160 5200 5165 5200 5170 5200 5152.5 (1) 5155 5157.5 5160 5152.5 5155 5157.5 5160 Upper 5247.5 5197.5 5245 5197.5 5242.5 5197.5 5240 5247.5 (1) 5245 5242.5 5240 5247.5 5245 5242.5 5240 Page 10-74 Chapter 10: Reference information Equipment Disposal Frequency range 5.2 GHz band Table 289 Frequency range per country 5.2 GHz band PMP/PTP 450i Series Countries Antenna Type Channel BW United States, FCC Any Other Any 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower 5252.5 5255 5257.5 5260 5265 5270 5252.5 5255 5257.5 5260 5265 5270 Upper 5342.5 5340 5335 5332.5 5332.5 5330 5347.5 5345 5342.5 5340 5335 5330 Table 290 Frequency range per country 5.2 GHz band PMP 450b Series Countries Antenna Type Channel BW FCC 16 dBi 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower

-

5255 5257.5 Upper

-

5340 5337.5 5260 5265 5270 5337.5 5330 5330 (*)

(*) Last channel at full power is 5325. Channel centers 5327.5 and 5330 need a power backoff of 5 dB. Page 10-75 Chapter 10: Reference information Equipment Disposal Table 291 Frequency range per country 5.2 GHz band PMP 450m Series Countries Antenna Type Channel BW United States, FCC Any Other Any 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz Channel center Frequency limits (MHz) Lower 5252.5 5255 5302.5 5257.5 5302.5 5260 5302.5 5252.5 5255 5257.5 5260 Upper 5347.5 5300 5340 5300 5335 5300 5340 5347.5 5345 5342.5 5340 Page 10-76 Chapter 10: Reference information Equipment Disposal Frequency range 5.4 GHz band Table 292 Frequency range per country 5.4 GHz band PMP/PTP 450i Series Countries Antenna Type Channel BW Mexico Any Other Any Other FCC Other ETSI 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz Channel center Frequency limits (MHz) Lower 5472.5 5475 5477.5 5480 5485 5490 5472.5 5475 5477.5 5480 5485 5490 5475 5477.5 5477.5 5480 5485 5490 5472.5 5652.5 5475 5655 5477.5 5657.5 5480 5660 Upper 5722.5 5720 5717.5 5715 5710 5685 5722.5 5720 5717.5 5715 5710 5705 5720 5717.5 5717.5 5715 5710 5705 5597.5 5722.5 5595 5720 5592.5 5717.5 5590 5715 Page 10-77 Chapter 10: Reference information Equipment Disposal Countries Antenna Type Channel BW Other ETSI 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower 5485 5665 5490 5670 Upper 5585 5710 5580 5705 Table 293 Frequency range per country 5.4 GHz band PMP 450b Series Countries Antenna Type Channel BW FCC 16 dBi 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower

-

5477.5 5480 Upper

-

5720 5717.5 5482.5 5487.5 5490 (*) 5715 5710 5705

(*) First channel at full power is 5495. Channel centers 5490 and 5492.5 need a power backoff of 5 dB. Page 10-78 Chapter 10: Reference information Equipment Disposal Table 294 Frequency range per country 5.4 GHz band PMP/PTP 450 Series Region code Other Country Code Any Other-FCC (Any non-US country that follows FCC rules Other-ETSI (Any country that follows ETSI rules Oceania Australia Channel BW 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz Channel center Frequency limits (MHz) Lower 5472.5 5475 5477.5 5480 5485 5490 5475 5477.5 5477.5 5480 5485 5490 5472.5 5652.5 5475 5655 5477.5 5657.5 5460 5640 5485 5665 5490 5670 5472.5 5652.5 5475 5645 Upper 5722.5 5720 5717.5 5715 5710 5705 5720 5717.5 5717.5 5715 5710 5705 5597.5 5722.5 5595 5720 5592.5 5717.5 5590 5715 5585 5710 5580 5705 5597.5 5722.5 5595 5720 Page 10-79 Chapter 10: Reference information Equipment Disposal Region code Country Code Oceania Australia North America Canada South America Brazil Asia Vietnam Channel BW 15 MHz 20 MHz 30 MHz 40 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower 5477.5 5657.5 5465 5640 5485 5665 5490 5670 5475 5655 5477.5 5657.5 5480 5660 5485 5665 5490 5670 5475 5477.5 5480 5485 5490 5475 5477.5 5480 5485 5490 Upper 5592.5 5717.5 5490 5715 5585 5710 5580 5705 5597.5 5722.5 5592.5 5717.5 5590 5715 5585 5710 5580 5705 5720 5717.5 5715 5710 5705 5720 5717.5 5715 5710 5705 Page 10-80 Chapter 10: Reference information Equipment Disposal Region code Country Code Africa Algeria Europe Europe (Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Liechtenstein, Norway, Portugal, Serbia, Spain, Switzerland, United Kingdom) Channel BW 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower 5472.5 5475 5477.5 5480 5485 5490 5475 5655 5477.5 5657.5 5465 5660 5485 5665 5490 5670 Upper 5667.5 5665 5662.5 5660 5655 5650 5595 5720 5592.5 5717.5 5490 5715 5585 5710 5580 5705 Page 10-81 Chapter 10: Reference information Equipment Disposal Table 295 Frequency range per country 5.4 GHz band PMP 450m Series Countries Antenna Type Channel BW United States, FCC Any ETSI Any Other Any 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz Channel center Frequency limits (MHz) Lower 5475 5475 5480 5477.5 5485 5480 5490 5472.5 5652.5 5475 5655 5477.5 5657.5 5480 5660 5472.5 5475 5477.5 5480 Upper 5720 5477.5 5720 5482.5 5717.5 5487.5 5715 5597.5 5722.5 5595 5720 5592.5 5717.5 5590 5715 5722.5 5720 5717.5 5715 Page 10-82 Chapter 10: Reference information Equipment Disposal Frequency range 5.8 GHz band Table 296 Frequency range per country 5.8 GHz band PMP/PTP 450i Series Countries Antenna Type Channel BW Any USA, Canada, Brazil, Other FCC Mexico Any Other Any ETSI Any 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower 5730 5730 5732.5 5735 Upper 5845 5845 5842.5 5840 5740 5745 5727.5 5730 5732.5 5735 5740 5745 5727.5 5730 5732.5 5735 5740 5745 5727.5 5730 5735 5737.5 5740 5745 5835 5830 5847.5 5845 5842.5 5840 5835 5830 5922.5 5920 5917.5 5915 5910 5905 5872.5 5870 5867.5 5865 5860 5855 Page 10-83 Chapter 10: Reference information Equipment Disposal Table 297 Frequency range per country 5.8 GHz band PMP 450b Series Countries Antenna Type Channel BW FCC 16 dBi 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower 5730 5730 Upper 5845 5845 5732.5 5735 5740 5745 5842.5 5840 5835 5830 Table 298 Frequency range per country 5.8 GHz band PMP/PTP 450 Series Channel center Frequency limits (MHz) Lower 5730 Upper 5790 5820 5732.5 5822.5 5735 5825 5740 5830 5745 5835 5760 5762.5 5765 5770 5775 5730 5820 5732.5 5845 5787.5 5842.5 5785 5840 5780 5835 5775 5830 5870 5867.5 5865 5860 5855 5790 5850 5787.5 Countries Antenna Type Channel BW Any Denmark, Norway, United Kingdom, Finland Germany Any Spain Any 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 10 MHz 15 MHz Page 10-84 Chapter 10: Reference information Equipment Disposal 5822.5 5847.5 Greece Any Portugal, Iceland, Serbia Any Switzerland, Liechtenstein Any Australia Any 5785 5845 5780 5840 5775 5835 5790 5787.5 5785 5780 5775 5870 5867.5 5865 5860 5855 5790 5870 5787.5 5867.5 5785 5865 5780 5860 5775 5855 5847.5 5845 5842.5 5840 20 MHz 30 MHz 40 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5735 5825 5740 5830 5745 5835 5730 5732.5 5735 5740 5745 5730 5732.5 5735 5740 5745 5730 5820 5732.5 5822.5 5735 5825 5740 5830 5745 5835 5727.5 5730 5732.5 5735 Page 10-85 Chapter 10: Reference information Equipment Disposal Canada, United States Any India Any Brazil, Vietnam Any Indonesia Any Malaysia Any 5835 5830 5847.5 5845 5842.5 5840 5835 5830 5872.5 5870 5867.5 5865 5860 5855 5847.5 5845 5842.5 5840 5835 5830 5822.5 5820 5817.5 5815 5872.5 5870 5865 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5740 5745 5727.5 5730 5732.5 5735 5740 5745 5727.5 5730 5832.5 5735 5840 5845 5727.5 5730 5732.5 5735 5740 5745 5727.5 5730 5732.5 5735 5727.5 5830 5835 Page 10-86 Chapter 10: Reference information Equipment Disposal Table 299 Frequency range per country 5.8 GHz band PMP 450m Series Countries Antenna Type Channel BW United States, FCC Any ETSI Any Other Any 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz Channel center Frequency limits (MHz) Lower 5730 5730 5732.5 5735 5727.5 5730 5735 5737.5 5727.5 5730 5732.5 5735 Upper 5845 5845 5842.5 5840 5872.5 5870 5867.5 5865 5922.5 5920 5917.5 5915 Page 10-87 Chapter 10: Reference information Equipment Disposal FCC specific information FCC compliance testing With GPS synchronization installed, the system has been tested for compliance to US (FCC) specifications. It has been shown to comply with the limits for emitted spurious radiation for a Class B digital device, pursuant to Part 15 of the FCC Rules in the USA. These limits have been designed to provide reasonable protection against harmful interference. However the equipment can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to other radio communications. There is no guarantee that interference does not occur in a particular installation. Note A Class B Digital Device is a device that is marketed for use in a residential environment, notwithstanding use in commercial, business and industrial environments. Note Notwithstanding that Cambium has designed (and qualified) the 450 Platform Family ODUs to generally meet the Class B requirement to minimize the potential for interference, the 450 Platform Family ODU range is not marketed for use in a residential environment. FCC IDs Table 300 US FCC IDs FCC ID Product Frequency Band Channel Bandwidth Frequencies Z8H89FT 0021 and Z8H89FT 0022 900 MHz PMP 450i AP & PMP 450 SM 900 MHz Z8H89FT 0003 and Z8H89FT 004 2.4 GHz PMP 450 AP & SM 2.4 GHz 3.5 GHz 5 MHz 7 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 5 MHz Maximum Combined Tx Output Power 25 dBm 25 dBm 25 dBm 25 dBm 25 dBm 19 dBm 904.5 925.5 MHz 905.5 924.5 MHz 907.0 923.0 MHz 909.5 920.5 MHz 912.0 918.0 MHz 2402.5 2480.0 MHz 2405.0 2477.5 MHz 19 dBm 2407.5 2475.0 MHz 2410.0 2472.5 MHz 2415.0 2467.5 MHz 3452.5 3647.5 MHz 19 dBm 19 dBm 19 dBm 25 dBm Page 10-88 Chapter 10: Reference information Equipment Disposal FCC ID Product Frequency Band Channel Bandwidth Frequencies Maximum Combined Tx Output Power 25 dBm 25 dBm 3.5 GHz PMP 450i AP & SM Z8H89FT 0009 and Z8H89FT 0010 3.65 GHz PMP 450i AP & SM 3.65 GHz Z8H89FT 0009 and Z8H89FT 0010 3.5 GHz PMP 450 AP & SM 3.5 GHz 3.65 GHz PMP 450 AP & SM 3.65 GHz 5 GHz 4.9 GHz 7 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 7 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 7 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 7 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 3453.5 3646.5 MHz 3455.0 3645 MHz 3457.5 3642.5 MHz 25 dBm 3460.0 3640 MHz 3465.0 3635 MHz 3470.0 3630 MHz 3652.5 -3697.5 MHz 3653.5 3696.5 MHz 3655.0 3695.0 MHz 3657.5 3692.5 MHz 3660.0 3690.0 MHz 3665.0 3685.0 MHz 3670.0 3680.0 MHz 3452.5 3647.5 MHz 3453.5 3646.5 MHz 3455.0 3645 MHz 3457.5 3642.5 MHz 3460.0 3640 MHz 3465.0 3635 MHz 3470.0 3630 MHz 3652.5 -3697.5 MHz 3653.5 3696.5 MHz 3655.0 3695.0 MHz 3657.5 3692.5 MHz 3660.0 3690.0 MHz 3665.0 3685.0 MHz 3670.0 3680.0 MHz 4942.5 4987.5 MHz 25 dBm 25 dBm 25 dBm 19 dBm 21 dBm 22 dBm 24 dBm 25 dBm 25 dBm 25 dBm 22 dBm 22 dBm 22 dBm 22 dBm 22 dBm 22 dBm 22 dBm 19 dBm 21 dBm 22 dBm 22 dBm 22 dBm 22 dBm 22 dBm 27 dBm Page 10-89 Chapter 10: Reference information Equipment Disposal FCC ID Product Frequency Band Channel Bandwidth Frequencies

(PMP/PTP 450i only) PMP 450/

450i AP, SM & PTP 450/450i BH Z8H89FT 0001, Z8H89FT 0002 and QWP-

50450I 5.1 GHz

(PMP/PTP 450i only) 5.2 GHz

(PMP/PTP 450i only) Maximum Combined Tx Output Power 27 dBm 27 dBm 27 dBm 4945.0 4985.0 MHz 4947.5 4982.5 MHz 4950.0 4980.0 MHz 4955.0 4975.0 MHz 4960.0 4970.0 MHz 27 dBm 27 dBm Maximum transmission power for US is 19 dBm. 5157.5 5247.5 MHz 5160.0 5245.0 MHz 5162.5 5242.5 MHz 5165.0 5240.0 MHz 5170.0 5235.0 MHz 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 5175.0 5230.0 MHz 27 dBm 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Maximum transmission power for FCC/US/Mexico is 19 dBm. 5 MHz 10 MHz 15 MHz 5252.5 5347.5 MHz 5255.0 5345.0 MHz 5257.5 5342.5 MHz 20 MHz 30 MHz 40 MHz 5260.0 5340.0 MHz 5265.0 5335.0 MHz 5270.0 5330.0 MHz 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 5 GHz 5.4 GHz Maximum transmission power for:

US/FCC is 19 dBm Page 10-90 Chapter 10: Reference information Equipment Disposal FCC ID Product Frequency Band Channel Bandwidth Frequencies Maximum Combined Tx Output Power Australia/ETSI is 25 for 5 MHz Channel bandwidth as a result of restricted EIRP limit PMP 450i AP, SM &

PTP 450i BH Z8H89FT 0001, Z8H89FT 0002 and QWP-

50450I Z8H89FT 0032 5 GHz PMP 450b SM Z8H89FT 0032 5 GHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5.8 GHz 4.9 GHz 5.1 GHz 5475.0 5720.0 MHz 5477.5 5717.5 MHz 5477.5 5717.5 MHz 5480.0 5715.0 MHz 5485.0 5710 MHz 5490.0 5705 MHz 5730.0 5872.5 MHz 5730.0 5870.0 MHz 5732.5 5867.5 MHz 5735.0 5865.0 MHz 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 5740.0 5860.0 MHz 27 dBm 5745.0 5855.0 MHz 27 dBm 4942.5 4987.5 MHz 4945.0 4985.0 MHz 4947.5 4982.5 MHz 4950.0 4980.0 MHz 27 dBm 27 dBm 27 dBm 27 dBm 4955.0 4975.0 MHz 27 dBm 4960.0 4970.0 MHz 27 dBm 5157.5 5247.5 MHz 5160.0 5245.0 MHz 5162.5 5242.5 MHz 5165.0 5240.0 MHz 5170.0 5235.0 MHz 5175.0 5230.0 MHz 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 5.2 GHz 5 MHz 5252.5 5347.5 MHz Page 10-91 Chapter 10: Reference information Equipment Disposal FCC ID Product Frequency Band Channel Bandwidth Frequencies Maximum Combined Tx Output Power PMP 450b SM 5.4 GHz 5.8 GHz Z8H89FT 0001, Z8H89FT 0002 and QWP-

50450I 5 GHz PMP 450 AP, SM &

PTP 450 BH 5.4 GHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5255.0 5345.0 MHz 5257.5 5342.5 MHz 5260.0 5340.0 MHz 5265.0 5335.0 MHz 5270.0 5330.0 MHz 5475.0 5720.0 MHz 5477.5 5717.5 MHz 5477.5 5717.5 MHz 5480.0 5715.0 MHz 5485.0 5710 MHz 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 27 dBm 5490.0 5705 MHz 27 dBm 5730.0 5872.5 MHz 27 dBm 5730.0 5870.0 MHz 27 dBm 5732.5 5867.5 MHz 27 dBm 5735.0 5865.0 MHz 27 dBm 30 MHz 5740.0 5860.0 MHz 27 dBm 40 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 40 MHz 5745.0 5855.0 MHz 27 dBm 4945.0 4985.0 MHz 4947.5 4982.5 MHz 4950.0 4980.0 MHz 27 dBm 27 dBm 27 dBm 4955.0 4975.0 MHz 27 dBm 4960.0 4970.0 MHz 27 dBm 5490.0 5705 MHz 22 dBm 5.8 GHz Maximum transmission power for FCC/US/Mexico is 19 dBm. Page 10-92 Chapter 10: Reference information Equipment Disposal FCC ID Product Frequency Band Channel Bandwidth Frequencies Maximum Combined Tx Output Power 22 dBm 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Z8H89FT 0001, Z8H89FT 0002 and QWP-

50450I 5 GHz PMP 450 AP, SM &

PTP 450 BH 5.8 GHz 5730.0 5872.5 MHz 5730.0 5870.0 MHz 22 dBm 5732.5 5867.5 MHz 22 dBm 5735.0 5865.0 MHz 22 dBm 5740.0 5860.0 MHz 22 dBm 5745.0 5855.0 MHz 22 dBm

(*) 27 dBm conducted power for 450i Series and 22 dBm conducted power for 450 Series Page 10-93 Chapter 10: Reference information Equipment Disposal FCC approved antenna list The lists of antennas which have been approved for operation by the FCC are provided in:

Table 301 for 4.9 GHz Table 302 for 5.1 and 5.2 GHz Table 303 for 5.4 GHz Table 304 for 5.8 GHz Note Any antenna of the same type and of gain equal or lower than the one approved by the FCC can be used in the countries following the FCC rules. Table 301 USA approved antenna list 4.9 GHz Directivity Type Manufacturer Reference Integrated flat plate Cambium Networks N/A Stated Gain

(dBi) 23.0 Directional Sector 2 ft dual polarised flat plate 4 ft parabolic dual polarised 6 ft parabolic dual polarised Integrated 90 sector flat plate 90 sectorised 60 sectorised Omni-

directional Dual polar omni-

directional Mars Antennas MA-WA56-DP-28N 28.0 Gabriel Antennas Gabriel Antennas Cambium Networks Cambium Networks Cambium Networks KP Dual QuickFire QFD4-49-N 33.7 QuickFire QF6-49-N A005240 85009324001 85009325001 KPPA-5.7-DPOMA 37.2 16.0 17.0 17.0 13.0 Page 10-94 Chapter 10: Reference information Equipment Disposal Table 302 USA approved antenna list 5.1 and 5.2 GHz Directivity Type Manufacturer Reference Integrated flat plate Cambium Networks N/A Directional Sector Omni-

directional 2ft dual polarised flat plate 4ft parabolic dual polarised Integrated 90 sector flat plate 90 sectorised Dual polar omni-

directional Dual polar omni-

directional Mars Antennas MA-WA56-DP-28N Gabriel Antennas Cambium Networks Cambium Networks KP PX4F-52-N7A/A A005240 85009324001 KPPA-5.7-DPOMA Mars Antennas MA-WO56-DP10 Table 303 USA approved antenna list 5.4 GHz Directivity Type Manufacturer Reference Integrated flat plate Cambium Networks N/A Directional Sector Omni-

directional 2 ft dual polarised flat plate 2 ft dual polarised parabolic Integrated 90 sector flat plate 90 sectorised Dual polar omni-

directional Dual polar omni-

directional Mars Antennas MA-WA56-DP-28N MTI MT-486013-NVH Cambium Networks Cambium Networks KP A005240 85009324001 KPPA-5.7-DPOMA Mars Antennas MA-WO56-DP10 Page 10-95 Stated Gain

(dBi) 23.0 28.5 34.5 16.0 17.0 13.0 10.0 Stated Gain

(dBi) 23.0 28.5 28.5 16.0 17.0 13.0 10.0 Chapter 10: Reference information Equipment Disposal Table 304 USA approved antenna list 5.8 GHz Directivity Type Manufacturer Reference Integrated flat plate Cambium Networks N/A Directional Sector 2 ft dual polarised flat plate 4 ft parabolic dual polarised 6 ft Parabolic dual polarised Integrated 90 sector flat plate 90 sectorised 60 sectorised Omni-

directional Dual polar omni-

directional Mars Antennas MA-WA56-DP-28N Gabriel Antennas Gabriel Antennas Cambium Networks Cambium Networks Cambium Networks KP PX4F-52-N7A/A PX6F-52/A A005240 85009324001 85009325001 KPPA-5.7-DPOMA Stated Gain

(dBi) 23.0 28.0 35.3 38.1 16.0 17.0 17.0 13.0 Innovation Science and Economic Development Canada (ISEDC) specific information 900 MHz ISEDC notification Radio Standards Specification RSS-247, Issue 1, Digital Transmission Systems (DTSs), Frequency Hopping Systems (FHSs) and License-Exempt Local Area Network (LE-LAN) Devices, is a new standard to replace annexes 8 and 9 of RSS-210, Issue 8. 4.9 GHz ISEDC notification The system has been approved under ISEDC RSS-111 for Public Safety Agency usage. The installer or operator is responsible for obtaining the appropriate site licenses before installing or using the system. Utilisation de la bande 4.9 GHz FCC et ISEDC Le systme a t approuv en vertu d ISEDC RSS-111 pour l'utilisation par l'Agence de la Scurit publique. L'installateur ou l'exploitant est responsable de l'obtention des licences de appropries avant d'installer ou d'utiliser le systme. Page 10-96 Chapter 10: Reference information Equipment Disposal 5.2 GHz and 5.4 GHz ISEDC notification This device complies with ISEDC RSS-247. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation. Users should be cautioned to take note that high power radars are allocated as primary users (meaning they have priority) of 5250 5350 MHz and 5650 5850 MHz and these radars could cause interference and/or damage to license-exempt local area networks (LELAN). For the connectorized version of the product and in order to reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power

(EIRP) is not more than that permitted by the regulations. The transmitted power must be reduced to achieve this requirement. Utilisation de la bande 5.2 and 5.4 GHz ISEDC Cet appareil est conforme ISEDC RSS-247. Son fonctionnement est soumis aux deux conditions suivantes: (1) Ce dispositif ne doit pas causer d'interfrences nuisibles, et (2) Cet appareil doit tolrer toute interfrence reue, y compris les interfrences pouvant entraner un fonctionnement indsirable. Les utilisateurs doivent prendre garde au fait que les radars haute puissance sont considres comme les utilisateurs prioritaires de 5250 5350 MHz et 5650 5850 MHz et ces radars peuvent causer des interfrences et / ou interfrer avec un rseau local ne ncessitant pas de licence. Pour la version du produit avec antenne externe et afin de rduire le risque d'interfrence avec d'autres utilisateurs, le type d'antenne et son gain doivent tre choisis afin que la puissance isotrope rayonne quivalente (PIRE) ne soit pas suprieure celle permise par la rglementation. Il peut tre ncessaire de rduire la puissance transmise doit tre rduite pour satisfaire cette exigence. ISEDC notification 5.8 GHz RSS-GEN issue 3 (7.1.3) Licence-Exempt Radio Apparatus:

This device complies with ISEDC license-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device. In Canada, high power radars are allocated as primary users (meaning they have priority) of the 5600 5650 MHz spectrum. These radars could cause interference or damage to license-exempt local area network (LE-LAN) devices. Utilisation de la bande 5.8 GHz ISEDC RSS-GEN issue 3 (7.1.3) appareil utilisant la bande sans licence:

Le prsent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorise aux deux conditions suivantes : (1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible d'en compromettre le fonctionnement. Au Canada, les radars haute puissance sont dsigns comme utilisateurs principaux (ils ont la priorit) dans la bande 5600 5650 MHz. Ces radars peuvent causer des interfrences et / ou interfrer avec un rseau local ne ncessitant pas de licence. Page 10-97 Chapter 10: Reference information Equipment Disposal ISEDC certification numbers Table 305 ISEDC Certification Numbers Frequency ISEDC Cert. Band Product Channel Bandwidth Frequencies 109AO-

50450I

(Pending) 5 GHz AP, SM &

BHM 4.9 GHz 5.8 GHz 5 MHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 4942.5 4987.5 MHz 4945.0 4985.0 MHz 4950.0 4980.0 MHz 5730.0 5845.0 MHz 5730.0 5845.0 MHz 5735.0 5840.0 MHz Maximum Combined Tx Output Power 24 dBm 24 dBm 23.5 dBm 28 dBm 28 dBm 28 dBm Canada approved antenna list Under ISEDC regulations, this radio transmitter may only operate using an antenna of a type and maximum (or lesser) gain approved for the transmitter by ISEDC . To reduce potential radio interference to other users, the antenna type and its gain must be so chosen that the equivalent isotropically radiated power (EIRP) is not more than that necessary for successful communication. Conformment la rglementation d'Industrie Canada, le prsent metteur radio peut fonctionner avec une antenne d'un type et d'un gain maximal (ou infrieur) approuv pour l'metteur par Industrie Canada. Dans le but de rduire les risques de brouillage radiolectrique l'intention des autres utilisateurs, il faut choisir le type d'antenne et son gain de sorte que la puissance isotrope rayonne quivalente (PIRE) ne dpasse pas l'intensit ncessaire l'tablissement d'une communication satisfaisante. This radio transmitter (identify the device by certification number) has been approved by ISEDC to operate with the antenna types listed in Country specific radio regulations, Innovation Science and Economic Development Canada (ISEDC) , Table 306 with the maximum permissible gain and required antenna impedance for each antenna type indicated. Antenna types not included in this list, having a gain greater than the maximum gain indicated for that type, are strictly prohibited for use with this device. Le prsent metteur radio (identifier le dispositif par son numro de certification) a t approuv par Industrie Canada pour fonctionner avec les types d'antenne numrs dans la section Country specific radio regulations, Innovation Science and Economic Development Canada (ISEDC) , Table 306 et ayant un gain admissible maximal et l'impdance requise pour chaque type d'antenne. Les types d'antenne non inclus dans cette liste, ou dont le gain est suprieur au gain maximal indiqu, sont strictement interdits pour l'exploitation de l'metteur. Page 10-98 Chapter 10: Reference information Equipment Disposal Table 306 Canada approved antenna list 4.9 and 5.8 GHz Antenna type Description Manufacturer Reference Gain (dBi) 4.9 GHz 5.8 GHz Directional Integrated flat plate 2 ft dual polarised flat plate 4 ft parabolic dual polarised 6 ft Parabolic dual polarised Integrated 90 sector flat plate Sector 90sector 60 sectorised Cambium Networks MARS Antennas Andrews Antennas Gabriel Antennas Cambium Networks Cambium Networks Cambium Networks N/A MA-WA56-DP-28N PX4F-52-N7A/A QF6-49-N A005240 85009324001 85009325001 Omni-directional KP Antennas KPPA-5.7-DPOMA Omni-directional MARS MA-WO56-DP10 Antennas Omni-

directional 23 28.5 N/A 37.2 16 17 16 13 10 23 28 35.3 N/A 16 17 16 13 10 Page 10-99 Chapter 10: Reference information Equipment Disposal Table 307 Canada approved antenna list 5.2 and 5.4 GHz Directivity Type Manufacturer Reference Integrated flat plate Cambium Networks N/A 2ft dual polarised flat plate 2ft dual polarised parabolic Integrated 90 sector flat plate 90 sectorised Dual polar omni-

directional Dual polar omni-

directional Directional Sector Omni-

directional Mars Antennas MA-WA56-DP-28N MTI MT-486013-NVH Cambium Networks Cambium Networks KP A005240 85009324001 KPPA-5.7-DPOMA Mars Antennas MA-WO56-DP10 Stated Gain

(dBi) 23.0 28.5 28.5 16.0 17.0 13.0 10.0 Page 10-100 Chapter 11: Troubleshooting This chapter contains procedures for identifying and correcting faults in a 450 Platform Family link. These procedures can be performed either on a newly installed link, or on an operational link if communication is lost, or after a lightning strike. The following topics are described in this chapter:

General troubleshooting procedure on page 11-2 Troubleshooting procedures on page 11-5 Power-up troubleshooting on page 11-13 Registration and connectivity troubleshooting on page 11-14 Page 11-1 Chapter 11: Troubleshooting General troubleshooting procedure General troubleshooting procedure General planning for troubleshooting Effective troubleshooting depends in part on measures that you take before you experience trouble in your network. Cambium recommends the following measures for each site:

Identify troubleshooting tools that are available at your site (such as a protocol analyzer). Identify commands and other sources that can capture baseline data for the site. These may include:

o Ping o Tracert or traceroute o Link Capacity Test results o Throughput data o Configuration tab captures o Status tab captures o Session logs o Web browser used Start a log for the site. Include the following information in the log:

o Operating procedures o Site-specific configuration records o Network topology o Software releases, boot versions and FPGA firmware versions o Types of hardware deployed o Site-specific troubleshooting processes o Escalation procedures Capture baseline data into the log from the sources listed above Page 11-2 Chapter 11: Troubleshooting General troubleshooting procedure General fault isolation process Effective troubleshooting also requires an effective fault isolation methodology that includes the following:

Attempting to isolate the problem to the level of a system, subsystem, or link, such as o AP to SM o AP to CMM4 o AP to GPS o Backhaul(BH) o Backhaul(BH) to CMM4 o Power Interpreting messages in the Event Log Researching Event Logs of the involved equipment Answering the questions listed in the following sections. Reversing the last previous corrective attempt before proceeding to the next. Performing only one corrective attempt at a time. Questions to help isolate the problem When a problem occurs, attempt to answer the following questions:

What is the history of the problem?

o Have we changed something recently?

o Have we seen other symptoms before this?

How wide-spread is the symptom?

o o Is the problem on only a single SM? (If so, focus on that SM.) Is the problem on multiple SMs? If so is the problem on one AP in the cluster? (If so, focus on that AP) is the problem on multiple, but not all, APs in the cluster? (If so, focus on those APs) is the problem on all APs in the cluster? (If so, focus on the CMM4 and the GPS signal.) Based on data in the Event Log o does the problem correlate to External Hard Resets with no WatchDog timers? (If so, this indicates a loss of power. Correct your power problem.) is intermittent connectivity indicated? (If so, verify your configuration, power level, cables and connections and the speed duplex of both ends of the link). o o does the problem correlate to loss-of-sync events?

Are connections made via shielded cables?

Does the GPS antenna have an unobstructed view of the entire horizon?

Has the site grounding been verified?

Secondary Steps After preliminary fault isolation is completed through the above steps, follow these:

Page 11-3 Chapter 11: Troubleshooting General troubleshooting procedure Check the Canopy knowledge base (https://support.cambiumnetworks.com/forum) to find whether other network operators have encountered a similar problem. Proceed to any appropriate set of diagnostic steps. These are organized as follows:

o Module has lost or does not establish connectivity on page 11-5 o NAT/DHCP-configured SM has lost or does not establish connectivity on page 11-7 o SM Does Not Register to an AP on page 11-8 o Module has lost or does not gain sync on page 11-9 o Module does not establish Ethernet connectivity on page 11-10 o CMM4 does not pass proper GPS sync to connected modules on page 11-11 o Module Software Cannot be Upgraded on page 11-12 o Module Functions Properly, Except Web Interface Became Inaccessible on page 11-12 Page 11-4 Chapter 11: Troubleshooting Troubleshooting procedures Troubleshooting procedures Proceed to any appropriate set of diagnostic steps. These are organized as follows:

Module has lost or does not establish connectivity on page 11-5 NAT/DHCP-configured SM has lost or does not establish connectivity on page 11-7 SM Does Not Register to an AP on page 11-8 Module has lost or does not gain sync on page 11-9 Module does not establish Ethernet connectivity on page 11-10 CMM4 does not pass proper GPS sync to connected modules on page 11-11 Module Software Cannot be Upgraded on page 11-12 Module Functions Properly, Except Web Interface Became Inaccessible on page 11-12 Module has lost or does not establish connectivity To troubleshoot a loss of connectivity, perform the following steps:

Procedure 37 Troubleshooting loss of connectivity 1 2 3 Isolate the end user/SM from peripheral equipment and variables such as routers, switches and firewalls. Set up the minimal amount of equipment. On each end of the link:

Check the cables and connections. Verify that the cable/connection schemestraight-through or crossoveris correct. Verify that the LED labeled LNK is green. Access the General Status tab in the Home page of the module. Verify that the SM is registered. Verify that Received Power Level is -87 dBm or higher. Access the IP tab in the Configuration page of the module. Verify that IP addresses match and are in the same subnet. If RADIUS authentication is configured, ensure that the RADIUS server is operational Page 11-5 Chapter 11: Troubleshooting Troubleshooting procedures 4 5 On the SM end of the link:

Verify that the PC that is connected to the SM is correctly configured to obtain an IP address through DHCP. Execute ipconfig (Windows) or ifconfig (linux) Verify that the PC has an assigned IP address. On each end of the link:

Access the General tab in the Configuration page of each module. Verify that the setting for Link Speeds (or negotiation) matches that of the other module. Access the Radio tab in the Configuration page of each module. Verify that the Radio Frequency Carrier setting is checked in the Custom Radio Frequency Scan Selection List. Verify that the Color Code setting matches that of the other module. Access the browser LAN settings (for example, at Tools > Internet Options > Connections > LAN Settings in Internet Explorer). Verify that none of the settings are selected. Access the Link Capacity Test tab in the Tools page of the module. Perform a link test Verify that the link test results show efficiency greater than 90% in both the uplink and downlink Execute ping. o Verify that no packet loss was experienced. o Verify that response times are not significantly greater than 4 ms from AP to SM 15 ms from SM to AP o Replace any cables that you suspect may be causing the problem. Note A ping size larger than 1494 Bytes to a module times out and fails. However, a ping of this size or larger to a system that is behind a Canopy module typically succeeds. It is generally advisable to ping such a system, since Canopy handles that ping with the same priority as is given all other transport traffic. The results are unaffected by ping size and by the load on the Canopy module that brokers this traffic. 6 After connectivity has been re-established, reinstall network elements and variables that you removed in Step 1. Page 11-6 Chapter 11: Troubleshooting Troubleshooting procedures NAT/DHCP-configured SM has lost or does not establish connectivity Before troubleshooting this problem, identify the NAT/DHCP configuration from the following list:

NAT with DHCP Client (DHCP selected as the Connection Type of the WAN interface) and DHCP Server NAT with DHCP Client (DHCP selected as the Connection Type of the WAN interface) NAT with DHCP Server NAT without DHCP To troubleshoot a loss of connectivity for a SM configured for NAT/DHCP, perform the following steps. Procedure 38 Troubleshooting loss of connectivity for NAT/DHCP-configured SM 1 2 3 4 5 Isolate the end user/SM from peripheral equipment and variables such as routers, switches and firewalls. Set up the minimal amount of equipment. On each end of the link:

Check the cables and connections. Verify that the cable/connection schemestraight-through or crossoveris correct. Verify that the LED labeled LNK is green. At the SM:

Access the NAT Table tab in the Logs web page. Verify that the correct NAT translations are listed. RESULT: NAT is eliminated as a possible cause if these translations are correct. If this SM is configured for NAT with DHCP, then at the SM:

Execute ipconfig (Windows) or ifconfig (Linux) Verify that the PC has an assigned IP address. reboot the PC. If the PC does not have an assigned IP address, then o enter ipconfig /release Adapter Name. o enter ipconfig /renew Adapter Name. o o after the PC has completed rebooting, execute ipconfig o o access the NAT DHCP Statistics tab in the Statistics web page of the SM. o verify that DHCP is operating as configured. if the PC has an assigned IP address, then 6 After connectivity has been re-established, reinstall network elements and variables that you removed in Step 1. Page 11-7 Chapter 11: Troubleshooting Troubleshooting procedures SM Does Not Register to an AP To troubleshoot a SM failing to register to an AP, perform the following steps. Procedure 39 Troubleshooting SM failing to register to an AP 1 2 3 4 5 6 7 8 9 10 11 12 13 Access the Radio tab in the Configuration page of the SM. Note the Color Code of the SM. Access the Radio tab in the Configuration page of the AP. Verify that the Color Code of the AP matches that of the SM. Note the Radio Frequency Carrier of the AP. Verify that the value of the RF Frequency Carrier of the AP is selected in the Custom Radio Frequency Scan Selection List parameter in the SM. In the AP, verify that the Max Range parameter is set to a distance slightly greater than the distance between the AP and the furthest SM that must register to this AP. Verify that no obstruction significantly penetrates the Fresnel zone of the attempted link. Access the General Status tab in the Home page of each module. Remove the bottom cover of the SM to expose the LEDs. Power cycle the SM. RESULT: Approximately 25 seconds after the power cycle, the green LED labeled LNK must light to indicate that the link has been established. If the orange LED labeled SYN is lit instead, then the SM is in Alignment mode because the SM failed to establish the link. If the AP is configured to require authentication, ensure proper configuration of RADIUS or Pre-shared AP key. In this latter case and if the SM has encountered no customer-inflicted damage, then request an RMA for the SM. Page 11-8 Chapter 11: Troubleshooting Troubleshooting procedures Module has lost or does not gain sync To troubleshoot a loss of sync, perform the following steps. Procedure 40 Troubleshooting loss of sync 1 2 3 4 5 6 7 Access the Event Log tab in the Home page of the SM Check for messages with the following format:

RcvFrmNum =

ExpFrmNum =

If these messages are present, check the Event Log tab of another SM that is registered to the same AP for messages of the same type. If the Event Log of this second SM does not contain these messages, then the fault is isolated to the first SM. If the Event Log page of this second SM contains these messages, access the GPS Status page of the AP. If the Satellites Tracked field in the GPS Status page of the AP indicates fewer than 4 or the Pulse Status field does not indicate Generating Sync, check the GPS Status page of another AP in the same AP cluster for these indicators. GPS signal acquisition must not take longer than 5 minutes from unit startup. If these indicators are present in the second AP, then:

Verify that the GPS antenna still has an unobstructed view of the entire horizon. Visually inspect the cable and connections between the GPS antenna and the CMM4. If this cable is not shielded, replace the cable with shielded cable If these indicators are not present in the second AP, visually inspect the cable and connections between the CMM4 and the AP antenna. If this cable is not shielded, replace the cable with shielded cable. Page 11-9 Chapter 11: Troubleshooting Troubleshooting procedures Module does not establish Ethernet connectivity To troubleshoot a loss of Ethernet connectivity, perform the following steps:

Procedure 41 Troubleshooting loss of Ethernet connectivity 1 2 3 4 5 6 7 8 Verify that the connector crimps on the Ethernet cable are not loose. Verify that the Ethernet cable is not damaged. If the Ethernet cable connects the module to a network interface card (NIC), verify that the cable is pinned out as a straight-through cable. If the Ethernet cable connects the module to a hub, switch, or router, verify that the cable is pinned out as a crossover cable. Verify that the Ethernet port to which the cable connects the module is set to auto-

negotiate speed. Verify VLAN configuration in the network, which may cause loss of module access if the accessing device is on a separate VLAN from the radio. Power cycle the module. RESULT: Approximately 25 seconds after the power cycle, the green LED labeled LNK must light up to indicate that the link has been established. If the orange LED labeled SYN is lit instead, then the module is in Alignment mode because the module failed to establish the link. In this latter case and if the module has encountered no customer-inflicted damage, then request an RMA for the module. Page 11-10 Chapter 11: Troubleshooting Troubleshooting procedures CMM4 does not pass proper GPS sync to connected modules If the Event Log tabs in all connected modules contain Loss of GPS Sync Pulse messages, perform the following steps. Procedure 42 Troubleshooting CMM4 not passing sync 1 2 3 4 Verify that the GPS antenna has an unobstructed view of the entire horizon. Verify that the GPS coaxial cable meets specifications. Verify that the GPS sync cable meets specifications for wiring and length. If the web pages of connected modules indicate any of the following, then find and eliminate the source of noise that is being coupled into the GPS sync cable:

incorrect reported Latitude and/or Longitude of the antenna In the GPS Status page:

o anomalous number of Satellites Tracked (greater than 12, for example) o In the Event Log page:

o garbled GPS messages o large number of Acquired GPS Sync Pulse messages GPS signal acquisition must not take longer than 5 minutes from unit startup. If these efforts fail to resolve the problem, then request an RMA for the CMM4. 5 Page 11-11 Chapter 11: Troubleshooting Troubleshooting procedures Module Software Cannot be Upgraded If your attempt to upgrade the software of a module fails, perform the following steps. Procedure 43 Troubleshooting an unsuccessful software upgrade 1 2 3 4 5 6 Download the latest issue of the target release and the associated release notes. Verify that the latest version of CNUT is installed. Compare the files used in the failed attempt to the newly downloaded software. Compare the procedure used in the failed attempt to the procedure in the newly downloaded release notes. If these comparisons reveal a difference, retry the upgrade, this time with the newer file or newer procedure. If, during attempts to upgrade the FPGA firmware, the following message is repeatable, then request an RMA for the module:

Error code 6, unrecognized device Module Functions Properly, Except Web Interface Became Inaccessible If a module continues to pass traffic and the SNMP interface to the module continues to function, but the web interface to the module does not display, perform the following steps:

Procedure 44 Restoring web management GUI access 1 2 3 4 5 Enter telnet DottedIPAddress. RESULT: A telnet session to the module is invoked. At the Login prompt, enter root. At the Password prompt, enter PasswordIfConfigured. At the Telnet +> prompt, enter reset. RESULT: The web interface is accessible again and this telnet connection is closed. Note The module may also be rebooted via an SNMP-based NMS (Wireless Manager, for example) If the issue persists, turn off any SNMP-based network/radio monitoring software and repeat steps 1-4. Page 11-12 Chapter 11: Troubleshooting Power-up troubleshooting Power-up troubleshooting ModuledoesnotpowerON IsModulespower LEDON?

Yes A No Isthe LEDalwaysred?

No Yes IsthereACpower goingtothesupply?

Ethernetcable repaired Yes Testcable,useknown goodcable.Couldtheradiobe indefaultmode SwitchONACmainspower No Yes Cablewireandpinout corrected No Testcable?

Yes Connecttoknowngood module Yes Cablelengthwithin 300meters No Iscablelength<300meters?

Yes Connecttoaknownpower supply Ismodulegetting poweredON?

Yes No Isthemodules redLEDON?

No ContactCambiumSupportfor RMA A Yes ModuleispoweredON Page 11-13 Chapter 11: Troubleshooting Registration and connectivity troubleshooting Registration and connectivity troubleshooting SM/BMS Registration If no SMs are registered to this AP, then the Session Status tab displays the simple message No sessions. In this case, try the following steps. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 More finely aim the SM or SMs toward the AP. Recheck the Session Status tab of the AP for the presence of LUIDs. If still no LUIDs are reported on the Session Status tab, click the Configuration button on the left side of the Home page. RESULT: The AP responds by opening the AP Configuration page. Click the Radio tab. Find the Color Code parameter and note the setting. In the same sequence as you did for the AP directly under Configuring Link for Test on Page 5-16, connect the SM to a computing device and to power. On the left side of the SM Home page, click the Configuration button. RESULT: The Configuration page of the SM opens. Click the Radio tab. If the transmit frequency of the AP is not selected in the Custom Radio Frequency Scan Selection List parameter, select the frequency that matches. If the Color Code parameter on this page is not identical to the Color Code parameter you noted from the AP, change one of them so that they match. At the bottom of the Radio tab for the SM, click the Save Changes button. Click the Reboot button. Allow several minutes for the SM to reboot and register to the AP. Return to the computing device that is connected to the AP. Recheck the Session Status tab of the AP for the presence of LUIDs. Page 11-14 Chapter 11: Troubleshooting Logs Logs Persistent Logging PMP 450 SM supports logging information such as session logs, authentication logs, and authorization logs that are persistent through reboots and connectivity losses. Navigate to Logs to view:

SM Session SM Authentication SM Authorization All the SM logs are saved to flash and displayed upon reboot. Figure 202 SM Logs Figure 203 SM Session log Figure 204 SM Authentication log Page 11-15 Chapter 11: Troubleshooting Figure 205 SM Authorization log Logs Page 11-16 Appendix A - 450m information Specifications Reference Please see the Specification sheets listed on the Cambium Networks website for the most up-to-date 450m Series cnMedusa AP specifications:

http://www.cambiumnetworks.com/resources/pmp-450m/

450m overload The 450m Series AP is designed to handle high load in terms of high throughput and high PPS. In terms of throughput, 450m is designed to achieve 3x or more throughput improvement over 450 and 450i Series products. In terms of packets per second (PPS), 450m is designed to handle up to 100k PPS. Overload occurs when the offered load exceeds the above limits. When overload occurs, 450m will start discarding packets and TCP throughput will degrade due to packet loss. The 450 family of products have a set of overload statistics that can be used to monitor overload conditions (Statistics >Overload tab). Page I Chapter 11: Troubleshooting Logs The above statistics shall be monitored over time for overload conditions over consecutive periods. Refer to Interpreting Overload statistics for description of those statistics. Its worth noting that Frame Utilization statistics (Statistics >Frame Utilization tab: Frame Utilization:

Downlink and Uplink) are not necessarily indicative of overload condition. They show how much the TDD frame is utilized. High frame utilization depends on:

1. high traffic during busy periods: those statistics will be close to 100% and almost all slots will be utilized. In this case if the Overload statistics show that packets are discarded then this is an indication of overload condition. 2. high percentage of VCs with low modulation with moderate traffic. Those VCs will require more slots to service them (due to low modulation) and the frame utilization will be high. In this case the TDD frame is fully utilized but the system is at low capacity and is not in an overload condition. 450m has higher PPS than 450 and 450i and supports higher throughput through spatial multiplexing, therefore when a 450m replaces an overloaded 450 or 450i AP the 450m will not be overloaded under the same conditions but the frame utilization may still show close to 100%; this should not alarm the customer. The overload statistics shall be monitored on 450m to see if it is overloaded or not. Page II Chapter 11: Troubleshooting Glossary Term 10Base-T 169.254.0.0 169.254.1.1 255.255.0.0 802.3 Access Point Cluster Access Point Module ACT/4 Address Resolution Protocol Aggregate Throughput AP ARP APs MIB Logs Definition Technology in Ethernet communications that can deliver 10 Mb of data across 328 feet (100 meters) of CAT 5 cable. Gateway IP address default in Cambium fixed wireless broadband IP network modules. IP address default in Cambium fixed wireless broadband IP network modules. Subnet mask default in Cambium fixed wireless broadband IP network modules and in Microsoft and Apple operating systems. An IEEE standard that defines the contents of frames that are transferred through Ethernet connections. Each of these frames contains a preamble, the address to which the frame is sent, the address that sends the frame, the length of the data to expect, the data, and a checksum to validate that no contents were lost. Two to six Access Point Modules that together distribute network or Internet services to a community of subscribers. Each Access Point Module covers a 60 or 90 sector. This cluster covers as much as 360. Also known as AP cluster. Also known as AP. One module that distributes network or Internet services in a 60 or 90 sector. Second-from-left LED in the module. In the operating mode, this LED is lit when data activity is present on the Ethernet link. Protocol defined in RFC 826 to allow a network element to correlate a host IP address to the Ethernet address of the host. See http://www.faqs.org/rfcs/rfc826.html. The sum of the throughputs in the uplink and the downlink. Access Point Module. One module that distributes network or Internet services to subscriber modules. Address Resolution Protocol. A protocol defined in RFC 826 to allow a network element to correlate a host IP address to the Ethernet address of the host. See http://www.faqs.org/rfcs/rfc826.html. Management Information Base file that defines objects that are specific to the Access Point Module. See also Management Information Base. Page III Chapter 11: Troubleshooting Logs Term ASN.1 Attenuation BER BHM BHS Bit Error Rate Box MIB Bridge Buckets Burst CAT 5 Cable CIR Cluster Management Module CMM Definition Abstract Syntax Notation One language. The format of the text files that compose the Management Information Base. Reduction of signal strength caused by the travel from the transmitter to the receiver, and caused by any object between. In the absence of objects between, a signal that has a short wavelength experiences a high degree of attenuation nevertheless. Bit Error Rate. The ratio of incorrect data received to correct data received. Backhaul Timing Master (BHM)- a module that is used in a point to point link. This module controls the air protocol and configurations for the link.. Backhaul Timing Slave (BHS)- a module that is used in a point to point link. This module accepts configuration and timing from the master module. Ratio of incorrect data received to correct data received. Management Information Base file that defines module-level objects. See also Management Information Base. Network element that uses the physical address (not the logical address) of another to pass data. The bridge passes the data to either the destination address, if found in the simple routing table, or to all network segments other than the one that transmitted the data. Modules are Layer 2 bridges except that, where NAT is enabled for an SM, the SM is a Layer 3 switch. Compare to Switch and Router, and see also NAT. Theoretical data repositories that can be filled at preset rates or emptied when preset conditions are experienced, such as when data is transferred. Preset amount limit of data that may be continuously transferred. Cable that delivers Ethernet communications from module to module. Later modules auto-sense whether this cable is wired in a straight-

through or crossover scheme. Committed Information Rate. For an SM or specified group of SMs, a level of bandwidth that can be guaranteed to never fall below a specified minimum (unless oversubscribed). In the Cambium implementation, this is controlled by the Low Priority Uplink CIR, Low Priority Downlink CIR, High Priority Uplink CIR, and High Priority Downlink CIR parameters. Module that provides power, GPS timing, and networking connections for an AP cluster. Also known as CMM4. Cluster Management Module. A module that provides power, GPS timing, and networking connections for an Access Point cluster. Page IV Chapter 11: Troubleshooting Term CodePoint Color Code Field Community String Field Connectorized Country Code CRCError Field Data Encryption Standard Demilitarized Zone DES DFS DHCP Logs Definition See DiffServ. Module parameter that identifies the other modules with which communication is allowed. The range of valid values is 0 to 255. Control string that allows a network management station to access MIB information about the module. The 450 Platform Family Connectorized Radio solution provide RF port to connect external antenna. It gives flexibility to connect to a variety of external antennas. A parameter that offers multiple fixed selections, each of which automatically implements frequency band range restrictions for the selected country. Units shipped to countries other than the United States must be configured with the corresponding Region Code and Country Code to comply with local regulatory requirements. This field displays how many CRC errors occurred on the Ethernet controller. Over-the-air link option that uses secret 56-bit keys and 8 parity bits. Data Encryption Standard (DES) performs a series of bit permutations, substitutions, and recombination operations on blocks of data. Internet Protocol area outside of a firewall. Defined in RFC 2647. See http://www.faqs.org/rfcs/rfc2647.html. Data Encryption Standard. An over-the-air link option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. See Dynamic Frequency Selection Dynamic Host Configuration Protocol, defined in RFC 2131. Protocol that enables a device to be assigned a new IP address and TCP/IP parameters, including a default gateway, whenever the device reboots. Thus DHCP reduces configuration time, conserves IP addresses, and allows modules to be moved to a different network within the system. See http://www.faqs.org/rfcs/rfc2131.html. See also Static IP Address Assignment. Page V Chapter 11: Troubleshooting Logs Term DiffServ DMZ Dynamic Frequency Selection Dynamic Host Configuration Protocol Electronic Serial Number ESN Ethernet Protocol ETSI Fade Margin Definition Differentiated Services, consistent with RFC 2474. A byte in the type of service (TOS) field of packets whose values correlates to the channel on which the packet should be sent. The value is a numeric code point. Cambium modules map each of 64 code points to values of 0 through 7. Three of these code points have fixed values, and the remaining 61 are settable. Values of 0 through 3 map to the low-priority channel; 4 through 7 to the high-priority channel. The mappings are the same as 802.1p VLAN priorities. (However, configuring DiffServ does not automatically enable the VLAN feature.) Among the settable parameters, the values are set in the AP for all downlinks within the sector and in the SM for each uplink. Demilitarized Zone as defined in RFC 2647. An Internet Protocol area outside of a firewall. See http://www.faqs.org/rfcs/rfc2647.html. A requirement in certain countries and regions for systems to detect interference from other systems, notably radar systems, and to avoid co-

channel operation with these systems. See DHCP. Hardware address that the factory assigns to the module for identification in the Data Link layer interface of the Open Systems Interconnection system. This address serves as an electronic serial number. Same as MAC Address. Electronic Serial Number. The hardware address that the factory assigns to the module for identification in the Data Link layer interface of the Open Systems Interconnection system. This address serves as an electronic serial number. Same as MAC Address. Any of several IEEE standards that define the contents of frames that are transferred from one network element to another through Ethernet connections. European Telecommunications Standards Institute The difference between strength of the received signal and the strength that the receiver requires for maintaining a reliable link. A higher fade margin is characteristic of a more reliable link. Standard operating margin. FCC Field-programmable Gate Array Federal Communications Commission of the U.S.A. Array of logic, relational data, and wiring data that is factory programmed and can be reprogrammed. Page VI Chapter 11: Troubleshooting Term File Transfer Protocol FPGA Free Space Path Loss Fresnel Zone FTP Global Positioning System GPS GPS/3 GUI High-priority Channel HTTP HTTPS Logs Definition Utility that transfers of files through TCP (Transport Control Protocol) between computing devices that do not operate on the same platform. Defined in RFC 959. See http://www.faqs.org/rfcs/rfc959.html. Field-programmable Gate Array. An array of logic, relational data, and wiring data that is factory programmed and can be reprogrammed. Signal attenuation that is naturally caused by atmospheric conditions and by the distance between the antenna and the receiver. Space in which no object should exist that can attenuate, diffract, or reflect a transmitted signal before the signal reaches the target receiver. File Transfer Protocol, defined in RFC 959. Utility that transfers of files through TCP (Transport Control Protocol) between computing devices that do not operate on the same platform. See http://www.faqs.org/rfcs/rfc959.html. Network of satellites that provides absolute time to networks on earth, which use the time signal to synchronize transmission and reception cycles (to avoid interference) and to provide reference for troubleshooting activities. Global Positioning System. A network of satellites that provides absolute time to networks on earth, which use the time signal to synchronize transmission and reception cycles (to avoid interference) and to provide reference for troubleshooting activities. Third-from-left LED in the module. In the operating mode for an Access Point Module, this LED is continuously lit as the module receives sync pulse. In the operating mode for a Subscriber, this LED flashes on and off to indicate that the module is not registered. Graphical user interface. Channel that supports low-latency traffic (such as Voice over IP) over low-latency traffic (such as standard web traffic and file downloads). To recognize the latency tolerance of traffic, this channel reads the IPv4 Type of Service DiffServ Control Point (DSCP) bits. Enabling the high-

priority channel reduces the maximum number of SMs that can be served in the sector. Hypertext Transfer Protocol, used to make the Internet resources available on the World Wide Web. Defined in RFC 2068. See http://www.faqs.org/rfcs/rfc2068.html. Hypertext Transfer Protocol Secure (HTTPS) Page VII Chapter 11: Troubleshooting Logs Term ICMP Integrated IP IP Address IPv4 ISM L2TP over IPSec Late Collision Field Line of Sight LNK/5 Logical Unit ID LOS LUID Definition Internet Control Message Protocols defined in RFC 792, used to identify Internet Protocol (IP)-level problems and to allow IP links to be tested. See http://www.faqs.org/rfcs/rfc792.html. The 450 Platform Family Integrated Radio solution provides integrated antenna.. Internet Protocol defined in RFC 791. The Network Layer in the TCP/IP protocol stack. This protocol is applied to addressing, routing, and delivering, and re-assembling data packets into the Data Link layer of the protocol stack. See http://www.faqs.org/rfcs/rfc791.html. 32-bit binary number that identifies a network element by both network and host. See also Subnet Mask. Traditional version of Internet Protocol, which defines 32-bit fields for data transmission. Industrial, Scientific, and Medical Equipment radio frequency band, in the 900-MHz, 2.4-GHz, and 5.8-GHz ranges. Level 2 Tunneling Protocol over IP Security. One of several virtual private network (VPN) implementation schemes. Regardless of whether Subscriber Modules have the Network Address Translation feature

(NAT) enabled, they support VPNs that are based on this protocol. This field displays how many late collisions occurred on the Ethernet controller. A normal collision occurs during the first 512 bits of the frame transmission. A collision that occurs after the first 512 bits is considered a late collision. A late collision is a serious network problem because the frame being transmitted is discarded. A late collision is most commonly caused by a mismatch between duplex configurations at the ends of a link segment. Wireless path (not simply visual path) direct from module to module. The path that results provides both ideal aim and an ideal Fresnel zone. Furthest left LED in the module. In the operating mode, this LED is continuously lit when the Ethernet link is present. In the aiming mode for a Subscriber Module, this LED is part of a bar graph that indicates the quality of the RF link. Final octet of the 4-octet IP address of the module. Line of sight. The wireless path (not simply visual path) direct from module to module. The path that results provides both ideal aim and an ideal Fresnel zone. Logical Unit ID. The final octet of the 4-octet IP address of the module. Page VIII Chapter 11: Troubleshooting Logs Term MAC Address Management Information Base Maximum Information Rate

(MIR) MIB MIR MU-MIMO NAT NEC NetBIOS Network Address Translation Definition Media Access Control address. The hardware address that the factory assigns to the module for identification in the Data Link layer interface of the Open Systems Interconnection system. This address serves as an electronic serial number. Space that allows a program (agent) in the network to relay information to a network monitor about the status of defined variables (objects). The cap applied to the bandwidth of an SM or specified group of SMs. In the Cambium implementation, this is controlled by the Sustained Uplink Data Rate, Uplink Burst Allocation, Sustained Downlink Data Rate, and Downlink Burst Allocation parameters. Management Information Base. Space that allows a program (agent) in the network to relay information to a network monitor about the status of defined variables (objects). See Maximum Information Rate. Multi User- Multiple Input Multiple Output Network Address Translation defined in RFC 1631. A scheme that isolates Subscriber Modules from the Internet. See http://www.faqs.org/rfcs/rfc1631.html. National Electrical Code. The set of national wiring standards that are enforced in the U.S.A. Protocol defined in RFC 1001 and RFC 1002 to support an applications programming interface in TCP/IP. This interface allows a computer to transmit and receive data with another host computer on the network. RFC 1001 defines the concepts and methods. RFC 1002 defines the detailed specifications. See http://www.faqs.org/rfcs/rfc1001.html and http://www.faqs.org/rfcs/rfc1002.html. Scheme that defines the Access Point Module as a proxy server to isolate registered Subscriber Modules from the Internet. Defined in RFC 1631. See http://www.faqs.org/rfcs/rfc1631.html. Network Management Station See NMS. NMS Network Management Station. A monitor device that uses Simple Network Management Protocol (SNMP) to control, gather, and report information about predefined network variables (objects). See also Simple Network Management Protocol. Page IX Chapter 11: Troubleshooting Logs Term Default Mode Definition Device that enables the operator to regain control of a module that has been locked by the No Remote Access feature, the 802.3 Link Disable feature, or a password or IP address that cannot be recalled. This device can be either fabricated on site or ordered. PMP Point-to-Multipoint Protocol Defined in RFC 2178, which specifies that data that originates from a See Point-to-Multipoint Protocol. PPPoE PPS PPTP Protective Earth Proxy Server PTP Radio Signal Strength Indicator Reflection central network element can be received by all other network elements, but data that originates from a non-central network element can be received by only the central network element. See http://www.faqs.org/rfcs/rfc2178.html. Also referenced as PMP. Point to Point Protocol over Ethernet. Supported on SMs for operators who use PPPoE in other parts of their network operators who want to deploy PPPoE to realize per-subscriber authentication, metrics, and usage control. Packet Per Second Point to Point Tunneling Protocol. One of several virtual private network implementations. Regardless of whether the Network Address Translation (NAT) feature enabled, Subscriber Modules support VPNs that are based on this protocol. Connection to earth (which has a charge of 0 volts). Also known as ground. Network computer that isolates another from the Internet. The proxy server communicates for the other computer, and sends replies to only the appropriate computer, which has an IP address that is not unique or not registered. A Point-to-Point connection refers to a communications connection between two nodes or endpoints. Relative measure of the strength of a received signal. An acceptable link displays a Radio Signal Strength Indicator (RSSI) value of greater than 700. Change of direction and reduction of amplitude of a signal that encounters an object larger than the wavelength. Reflection may cause an additional copy of the wavelength to arrive after the original, unobstructed wavelength arrives. This causes partial cancellation of the signal and may render the link unacceptable. However, in some instances where the direct signal cannot be received, the reflected copy may be received and render an otherwise unacceptable link acceptable. Page X Chapter 11: Troubleshooting Logs Term Region Code RF RJ-12 RJ-45 Router RSSI Self-interference SFP Simple Network Management Protocol SM SNMP SNMPv3 SNMP Trap Static IP Address Assignment Definition A parameter that offers multiple fixed selections, each of which automatically implements frequency band range restrictions for the selected region. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. Radio frequency. How many times each second a cycle in the antenna occurs, from positive to negative and back to positive amplitude. Standard cable that is typically used for telephone line or modem connection. Standard cable that is typically used for Ethernet connection. This cable may be wired as straight-through or as crossover. Later modules auto-

sense whether the cable is straight-through or crossover. Network element that uses the logical (IP) address of another to pass data to only the intended recipient. Compare to Switch and Bridge. Radio Signal Strength Indicator. A relative measure of the strength of a received signal. An acceptable link displays an RSSI value of greater than 700. Interference with a module from another module in the same network. Small Form-factor Pluggable Standard that is used for communications between a program (agent) in the network and a network management station (monitor). Defined in RFC 1157. See http://www.faqs.org/rfcs/rfc1157.html. Customer premises equipment (CPE) device that extends network or Internet services by communication with an Access Point Module or an Access Point cluster. See Simple Network Management Protocol, defined in RFC 1157. SNMP version 3 Capture of information that informs the network monitor through Simple Network Management Protocol of a monitored occurrence in the module. Assignment of Internet Protocol address that can be changed only manually. Thus static IP address assignment requires more configuration time and consumes more of the available IP addresses than DHCP address assignment does. RFC 2050 provides guidelines for the static allocation of IP addresses. See http://www.faqs.org/rfcs/rfc2050.html. See also DHCP. Page XI Chapter 11: Troubleshooting Logs Term Subnet Mask Subscriber Module Sustained Data Rate Switch Sync TCP TDD telnet Tokens TxUnderrun Field UDP udp Definition 32-bit binary number that filters an IP address to reveal what part identifies the network and what part identifies the host. The number of subnet mask bits that are set to 1 indicates how many leading bits of the IP address identify the network. The number of subnet mask bits that are set 0 indicate how many trailing bits of the IP address identify the host. Customer premises equipment (CPE) device that extends network or Internet services by communication with an Access Point Module or an Access Point cluster. Preset rate limit of data transfer. Network element that uses the port that is associated with the physical address of another to pass data to only the intended recipient. Compare to Bridge and Router. GPS (Global Positioning System) absolute time, which is passed from one module to another. Sync enables timing that prevents modules from transmitting or receiving interference. Sync also provides correlative time stamps for troubleshooting efforts. Alternatively known as Transmission Control Protocol or Transport Control Protocol. The Transport Layer in the TCP/IP protocol stack. This protocol is applied to assure that data packets arrive at the target network element and to control the flow of data through the Internet. Defined in RFC 793. See http://www.faqs.org/rfcs/rfc793.html. Time Division Duplexing. Synchronized data transmission with some time slots allocated to devices transmitting on the uplink and some to the device transmitting on the downlink. Utility that allows a client computer to update a server. A firewall can prevent the use of the telnet utility to breach the security of the server. See http://www.faqs.org/rfcs/rfc818.html, http://www.faqs.org/rfcs/rfc854.html and http://www.faqs.org/rfcs/rfc855.html. Theoretical amounts of data. See also Buckets. This field displays how many transmission-underrun errors occurred on the Ethernet controller. User Datagram Protocol. A set of Network, Transport, and Session Layer protocols that RFC 768 defines. These protocols include checksum and address information but does not retransmit data or process any errors. See http://www.faqs.org/rfcs/rfc768.html. User-defined type of port. Page XII Chapter 11: Troubleshooting Logs Term U-NII VID VLAN VPN Definition Unlicensed National Information Infrastructure radio frequency band, in the 5.1GHz through 5.8 GHz ranges. VLAN identifier. See also VLAN. Virtual local area network. An association of devices through software that contains broadcast traffic, as routers would, but in the switch-level protocol. Virtual private network for communication over a public network. One typical use is to connect remote employees, who are at home or in a different city, to their corporate network over the Internet. Any of several VPN implementation schemes is possible. SMs support L2TP over IPSec

(Level 2 Tunneling Protocol over IP Security) VPNs and PPTP (Point to Point Tunneling Protocol) VPNs, regardless of whether the Network Address Translation (NAT) feature enabled. Page XIII

 

 

Cambium 450 Platform User Guide System Release 15.2 33F pass Accuracy While reasonable efforts have been made to assure the accuracy of this document, Cambium Networks assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein. Cambium reserves the right to make changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Cambium does not assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey license under its patent rights or the rights of others. It is possible that this publication may contain references to, or information about Cambium products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that Cambium intends to announce such Cambium products, programming, or services in your country. Copyrights This document, Cambium products, and 3rd Party software products described in this document may include or describe copyrighted Cambium and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Cambium, its licensors, and other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any copyrighted material of Cambium, its licensors, or the 3rd Party software supplied material contained in the Cambium products described in this document may not be copied, reproduced, reverse engineered, distributed, merged or modified in any manner without the express written permission of Cambium. Furthermore, the purchase of Cambium products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Cambium or other 3rd Party supplied software, except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a product. 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 Cambium. License Agreements The software described in this document is the property of Cambium and its licensors. It is furnished by express license agreement only and may be used only in accordance with the terms of such an agreement. High Risk Materials Cambium and its supplier(s) specifically disclaim any express or implied warranty of fitness for any high risk activities or uses of its products including, but not limited to, the operation of nuclear facilities, aircraft navigation or aircraft communication systems, air traffic control, life support, or weapons systems (High Risk Use). Any High Risk Use is unauthorized, is made at your own risk and you shall be responsible for any and all losses, damage or claims arising out of any High Risk Use. 2017 Cambium Networks Limited. All Rights Reserved. pmp-2020 (October 2017) Contents Cambium 450 Platform User Guide ......................................................................................................... 1 Contents ........................................................................................................................................................ i List of Figures .......................................................................................................................................... xiii List of Tables .......................................................................................................................................... xviii About This User Guide ............................................................................................................................... 1 Contacting Cambium Networks ....................................................................................................... 1 Purpose ............................................................................................................................................ 2 Product notation conventions in document ...................................................................................... 2 Cross references .............................................................................................................................. 3 Feedback ......................................................................................................................................... 3 Important regulatory information ............................................................................................................. 4 Application software ......................................................................................................................... 4 USA specific information .................................................................................................................. 4 Canada specific information ............................................................................................................. 5 Renseignements specifiques au Canada ........................................................................................ 6 EU Declaration of Conformity .......................................................................................................... 7 Specific expertise and training for professional installers ................................................................ 7 Ethernet networking skills ................................................................................................................ 7 Lightning protection .......................................................................................................................... 7 Training ............................................................................................................................................ 8 Problems and warranty ........................................................................................................................... 9 Reporting problems .......................................................................................................................... 9 Repair and service ........................................................................................................................... 9 Hardware warranty ........................................................................................................................... 9 Security advice ...................................................................................................................................... 10 Warnings, cautions, and notes .............................................................................................................. 11 Warnings ........................................................................................................................................ 11 Cautions ......................................................................................................................................... 11 Notes .............................................................................................................................................. 11 Caring for the environment ................................................................................................................... 12 In EU countries ............................................................................................................................... 12 In non-EU countries ....................................................................................................................... 12 Chapter 1: Product description .......................................................................................................... 1-1 Overview of the 450 Platform Family ................................................................................................... 1-2 Purpose ......................................................................................................................................... 1-2 PMP 450m Series ......................................................................................................................... 1-2 PMP/PTP 450i Series ................................................................................................................... 1-4 PMP 450b Series .......................................................................................................................... 1-7 PMP/PTP 450 Series .................................................................................................................... 1-9 Page i Contents Supported interoperability for 450m/450i/450b/450 Series ......................................................... 1-12 Typical deployment ..................................................................................................................... 1-13 Product variants .......................................................................................................................... 1-15 Wireless operation ............................................................................................................................. 1-16 Time division duplexing ............................................................................................................... 1-16 Encryption ................................................................................................................................... 1-19 MIMO........................................................................................................................................... 1-19 MU-MIMO .................................................................................................................................... 1-19 System management ......................................................................................................................... 1-21 Management agent ..................................................................................................................... 1-21 Web server .................................................................................................................................. 1-21 Remote Authentication Dial-in User Service (RADIUS) .............................................................. 1-23 Network Time Protocol (NTP) ..................................................................................................... 1-23 Wireless Manager (WM) ............................................................................................................. 1-24 cnMaestro ................................................................................................................................ 1-25 Radio recovery mode .................................................................................................................. 1-26 Chapter 2: System hardware ............................................................................................................... 2-1 System Components ............................................................................................................................ 2-2 Point-to-Multipoint (PMP) .............................................................................................................. 2-2 Backhaul (PTP) ............................................................................................................................. 2-5 450 Platform Family interfaces ..................................................................................................... 2-7 ATEX/HAZLOC variants.............................................................................................................. 2-14 Diagnostic LEDs .......................................................................................................................... 2-15 Power supply options .................................................................................................................. 2-19 ODU mounting brackets & accessories ...................................................................................... 2-28 Lightning protection ..................................................................................................................... 2-28 ODU interfaces................................................................................................................................... 2-29 PMP 450m Series AP ................................................................................................................. 2-29 PMP/PTP 450i ............................................................................................................................. 2-30 PMP 450b ................................................................................................................................... 2-32 Cabling ............................................................................................................................................... 2-33 Ethernet standards and cable lengths ........................................................................................ 2-33 Outdoor copper Cat5e Ethernet cable ........................................................................................ 2-34 SFP module kits .......................................................................................................................... 2-35 Main Ethernet port ....................................................................................................................... 2-37 Aux port ....................................................................................................................................... 2-37 Lightning protection unit (LPU) and grounding kit .............................................................................. 2-41 Cable grounding kit ..................................................................................................................... 2-42 Antennas and antenna cabling .......................................................................................................... 2-43 Antenna requirements ................................................................................................................. 2-43 Supported external AP antennas ................................................................................................ 2-43 Supported external BH/SM antenna ........................................................................................... 2-43 RF cable and connectors ............................................................................................................ 2-44 Antenna accessories ................................................................................................................... 2-44 Page ii Contents GPS synchronization ......................................................................................................................... 2-45 GPS synchronization description ................................................................................................ 2-45 Universal GPS (UGPS) .............................................................................................................. 2-45 CMM5 .......................................................................................................................................... 2-46 CMM5 Controller Module ............................................................................................................ 2-48 CMM5 Injector Module ................................................................................................................ 2-49 CMM5 Injector Compatibility Matrix ............................................................................................ 2-49 CMM5 Specifications .................................................................................................................. 2-50 CMM4 (Rack Mount) .................................................................................................................. 2-51 CMM4 (Cabinet with switch) ..................................................................................................... 2-54 CMM4 (Cabinet without switch) ................................................................................................ 2-54 CMM3/CMMmicro ....................................................................................................................... 2-55 Installing a GPS receiver ................................................................................................................... 2-57 GPS receiver location ................................................................................................................. 2-57 Mounting the GPS receiver ......................................................................................................... 2-58 Cabling the GPS Antenna ........................................................................................................... 2-59 Installing and connecting the GPS LPU ...................................................................................... 2-59 Ordering the components .................................................................................................................. 2-60 Chapter 3: System planning ................................................................................................................ 3-1 Typical deployment .............................................................................................................................. 3-2 ODU with PoE interface to PSU .................................................................................................... 3-2 Site planning ........................................................................................................................................ 3-7 Site selection for PMP/PTP radios ................................................................................................ 3-7 Power supply site selection ........................................................................................................... 3-8 Maximum cable lengths ................................................................................................................ 3-8 Grounding and lightning protection ............................................................................................... 3-8 ODU and external antenna location ............................................................................................ 3-10 ODU ambient temperature limits ................................................................................................. 3-10 ODU wind loading ....................................................................................................................... 3-11 Hazardous locations .................................................................................................................... 3-15 Drop cable grounding points ....................................................................................................... 3-15 Lightning Protection Unit (LPU) location ..................................................................................... 3-16 Radio Frequency planning ................................................................................................................. 3-17 Regulatory limits .......................................................................................................................... 3-17 Conforming to the limits .............................................................................................................. 3-17 Available spectrum ...................................................................................................................... 3-17 Analyzing the RF Environment ................................................................................................... 3-18 Channel bandwidth ..................................................................................................................... 3-18 Anticipating Reflection of Radio Waves ...................................................................................... 3-18 Obstructions in the Fresnel Zone ................................................................................................ 3-19 Planning for co-location............................................................................................................... 3-19 Multiple OFDM Access Point Clusters ........................................................................................ 3-20 Considerations on back-to-back frequency reuse ...................................................................... 3-22 PMP 450m Series planning ........................................................................................................ 3-26 Page iii Contents Link planning ...................................................................................................................................... 3-28 Range and obstacles .................................................................................................................. 3-28 Path loss ..................................................................................................................................... 3-28 Calculating Link Loss .................................................................................................................. 3-29 Calculating Rx Signal Level ........................................................................................................ 3-29 Calculating Fade Margin ............................................................................................................. 3-30 Adaptive modulation .................................................................................................................... 3-30 Planning for connectorized units ........................................................................................................ 3-31 When to install connectorized units ............................................................................................ 3-31 Choosing external antennas ....................................................................................................... 3-31 Calculating RF cable length (5.8 GHz FCC only) ....................................................................... 3-31 Data network planning ....................................................................................................................... 3-33 Understanding addresses ........................................................................................................... 3-33 Dynamic or static addressing ...................................................................................................... 3-33 DNS Client .................................................................................................................................. 3-34 Network Address Translation (NAT) ........................................................................................... 3-34 Developing an IP addressing scheme ........................................................................................ 3-35 Address Resolution Protocol ....................................................................................................... 3-35 Allocating subnets ....................................................................................................................... 3-36 Selecting non-routable IP addresses .......................................................................................... 3-36 Translation bridging ..................................................................................................................... 3-36 Engineering VLANs ..................................................................................................................... 3-37 Network management planning ......................................................................................................... 3-41 Planning for SNMP operation ..................................................................................................... 3-41 Enabling SNMP ........................................................................................................................... 3-41 Security planning ............................................................................................................................... 3-42 Isolating AP/BHM from the Internet ............................................................................................ 3-42 Encrypting radio transmissions ................................................................................................... 3-42 Planning for HTTPS operation .................................................................................................... 3-43 Planning for SNMPv3 operation .................................................................................................. 3-43 Managing module access by passwords .................................................................................... 3-44 Planning for RADIUS operation .................................................................................................. 3-45 Filtering protocols and ports ........................................................................................................ 3-45 Encrypting downlink broadcasts ................................................................................................. 3-49 Isolating SMs in PMP .................................................................................................................. 3-49 Filtering management through Ethernet ..................................................................................... 3-49 Allowing management from only specified IP addresses ........................................................... 3-50 Configuring management IP by DHCP ....................................................................................... 3-50 Controlling PPPoE PADI Downlink Forwarding .......................................................................... 3-51 Remote AP Deployment .................................................................................................................... 3-52 Remote AP (RAP) Performance ................................................................................................. 3-53 Example Use Case for RF Obstructions ..................................................................................... 3-53 Example Use Case for Passing Sync ......................................................................................... 3-54 Physical Connections Involving the Remote AP ......................................................................... 3-55 Page iv Contents Passing Sync signal .................................................................................................................... 3-57 Wiring to Extend Network Sync .................................................................................................. 3-60 Chapter 4: Legal and regulatory information .................................................................................... 4-1 Cambium Networks end user license agreement ................................................................................ 4-2 Definitions ..................................................................................................................................... 4-2 Acceptance of this agreement ...................................................................................................... 4-2 Grant of license ............................................................................................................................. 4-2 Conditions of use .......................................................................................................................... 4-3 Title and restrictions ...................................................................................................................... 4-4 Confidentiality ................................................................................................................................ 4-4 Right to use Cambiums name ...................................................................................................... 4-5 Transfer ......................................................................................................................................... 4-5 Updates ......................................................................................................................................... 4-5 Maintenance .................................................................................................................................. 4-5 Disclaimer ..................................................................................................................................... 4-6 Limitation of liability ....................................................................................................................... 4-6 U.S. government ........................................................................................................................... 4-6 Term of license .............................................................................................................................. 4-7 Governing law ............................................................................................................................... 4-7 Assignment ................................................................................................................................... 4-7 Survival of provisions .................................................................................................................... 4-7 Entire agreement ........................................................................................................................... 4-7 Third party software ...................................................................................................................... 4-7 Compliance with safety standards ..................................................................................................... 4-22 Electrical safety compliance ........................................................................................................ 4-22 Electromagnetic compatibility (EMC) compliance ....................................................................... 4-22 Human exposure to radio frequency energy ............................................................................... 4-22 Hazardous location compliance .................................................................................................. 4-32 Compliance with radio regulations ..................................................................................................... 4-34 Type approvals ............................................................................................................................ 4-35 Brazil specific information ........................................................................................................... 4-36 Australia Notification ................................................................................................................... 4-36 Regulatory Requirements for CEPT Member States (www.cept.org) ........................................ 4-36 Chapter 5: Preparing for installation .................................................................................................. 5-1 Safety ................................................................................................................................................... 5-2 Hazardous locations ...................................................................................................................... 5-2 Power lines .................................................................................................................................... 5-2 Working at heights ........................................................................................................................ 5-2 Power supply ................................................................................................................................. 5-2 Grounding and protective earth .................................................................................................... 5-2 Powering down before servicing ................................................................................................... 5-3 Primary disconnect device ............................................................................................................ 5-3 External cables .............................................................................................................................. 5-3 RF exposure near the antenna ..................................................................................................... 5-3 Page v Contents Chapter 6:

Minimum separation distances ..................................................................................................... 5-3 Grounding and lightning protection requirements ......................................................................... 5-3 Grounding cable installation methods ........................................................................................... 5-3 Siting ODUs and antennas ........................................................................................................... 5-4 Thermal Safety .............................................................................................................................. 5-4 Preparing for installation ...................................................................................................................... 5-5 ODU pre-configuration .................................................................................................................. 5-5 Preparing personnel ...................................................................................................................... 5-5 Preparing inventory ....................................................................................................................... 5-5 Preparing tools .............................................................................................................................. 5-6 Testing system components ................................................................................................................ 5-7 Unpacking Components ................................................................................................................ 5-7 Preparing the ODU ........................................................................................................................ 5-7 Configuring Link for Test .................................................................................................................... 5-16 Configuring the management PC ................................................................................................ 5-16 Logging into the web interface AP/SM/BH ............................................................................... 5-17 Using the Quick Start Configuration Wizard of the AP/BHM ...................................................... 5-17 Installation ......................................................................................................................... 6-1 ODU variants and mounting bracket options ....................................................................................... 6-2 Mount the ODU, LPU and surge suppressor ....................................................................................... 6-3 Attach ground cables to the ODU ................................................................................................. 6-3 Mount the ODU on the mast ......................................................................................................... 6-6 Mount the top LPU ...................................................................................................................... 6-10 Mount the Surge Suppressor ...................................................................................................... 6-10 General protection installation .................................................................................................... 6-13 Installing the copper Cat5e Ethernet interface ................................................................................... 6-19 Install the main drop cable .......................................................................................................... 6-19 Install the bottom LPU to PSU drop cable .................................................................................. 6-21 Installing external antennas to a connectorized ODU ....................................................................... 6-23 PMP 450i Series ......................................................................................................................... 6-23 PMP 450 Series .......................................................................................................................... 6-32 PMP 450i Series AP 900 MHz .................................................................................................... 6-41 PMP 450 Series SM 900 MHz .................................................................................................... 6-48 Installing an integrated ODU .............................................................................................................. 6-52 PMP 450m Series AP .............................................................................................................. 6-52 PMP/PTP 450i Series AP/SM/BH ............................................................................................ 6-55 Connecting Cat5e Ethernet cable ...................................................................................................... 6-56 Connecting an RJ45 and gland to a unit ..................................................................................... 6-56 Disconnecting an RJ45 and gland from a unit ............................................................................ 6-58 Installing ODU .................................................................................................................................... 6-59 Installing a 450 Platform Family AP ............................................................................................ 6-59 Installing a 450 Platform Family SM ........................................................................................... 6-60 Installing a 450 Platform Family BHM ......................................................................................... 6-61 Installing a 450 platform BHS ..................................................................................................... 6-62 Page vi Contents Configuring the Link .................................................................................................................... 6-62 Monitoring the Link ...................................................................................................................... 6-62 Installing the AC Power Injector ......................................................................................................... 6-63 Installing the AC Power Injector .................................................................................................. 6-63 Installing CMM4 ................................................................................................................................. 6-64 Supplemental installation information ................................................................................................ 6-65 Stripping drop cable .................................................................................................................... 6-65 Creating a drop cable grounding point ........................................................................................ 6-66 Attaching and weatherproofing an N type connector .................................................................. 6-69 Chapter 7: Configuration ..................................................................................................................... 7-1 Preparing for configuration ................................................................................................................... 7-2 Safety precautions ........................................................................................................................ 7-2 Regulatory compliance.................................................................................................................. 7-2 Connecting to the unit .......................................................................................................................... 7-3 Configuring the management PC .................................................................................................. 7-3 Connecting to the PC and powering up ........................................................................................ 7-4 Using the web interface ....................................................................................................................... 7-5 Logging into the web interface ...................................................................................................... 7-5 Web GUI ....................................................................................................................................... 7-6 Using the menu options ................................................................................................................ 7-7 Quick link setup .................................................................................................................................. 7-11 Initiating Quick Start Wizard ........................................................................................................ 7-11 Configuring time settings............................................................................................................. 7-17 Powering the SM/BHS for test .................................................................................................... 7-18 Viewing the Session Status of the AP/BHM to determine test registration ................................. 7-19 Configuring IP and Ethernet interfaces .............................................................................................. 7-22 Configuring the IP interface ........................................................................................................ 7-23 Auxiliary port ............................................................................................................................... 7-26 NAT, DHCP Server, DHCP Client and DMZ ............................................................................... 7-27 DHCP BHS ............................................................................................................................... 7-43 Reconnecting to the management PC ........................................................................................ 7-43 VLAN configuration for PMP ............................................................................................................ 7-43 VLAN configuration for PTP ........................................................................................................... 7-53 PPPoE page of SM ..................................................................................................................... 7-57 IP4 and IPv6 ................................................................................................................................ 7-60 Upgrading the software version and using CNUT ............................................................................. 7-64 Checking the installed software version ...................................................................................... 7-64 Upgrading to a new software version .......................................................................................... 7-64 General configuration ......................................................................................................................... 7-68 PMP 450m and PMP/PTP 450i Series ....................................................................................... 7-68 PMP/PTP 450 Series .................................................................................................................. 7-86 Configuring Unit Settings page .......................................................................................................... 7-91 Setting up time and date .................................................................................................................... 7-95 Time page of 450 Platform Family - AP/BHM ............................................................................. 7-95 Page vii Contents Configuring synchronization ............................................................................................................... 7-97 Configuring security ........................................................................................................................... 7-99 Managing module access by password .................................................................................... 7-100 Isolating from the internet APs/BHMs .................................................................................... 7-103 Encrypting radio transmissions ................................................................................................. 7-103 Requiring SM Authentication .................................................................................................... 7-104 Filtering protocols and ports ...................................................................................................... 7-105 Encrypting downlink broadcasts ............................................................................................... 7-108 Isolating SMs ............................................................................................................................. 7-108 Filtering management through Ethernet ................................................................................... 7-109 Allowing management only from specified IP addresses ......................................................... 7-109 Restricting radio Telnet access over the RF interface .............................................................. 7-109 Configuring SNMP Access ........................................................................................................ 7-112 Configuring Security .................................................................................................................. 7-114 Configuring radio parameters .......................................................................................................... 7-126 PMP 450m Series configuring radio ...................................................................................... 7-127 PMP/PTP 450i Series configuring radio................................................................................. 7-131 PMP 450b Series - configuring radio ........................................................................................ 7-151 PMP/PTP 450 Series configuring radio ................................................................................ 7-155 Custom Frequencies page ........................................................................................................ 7-172 DFS for 5 GHz Radios .............................................................................................................. 7-175 MIMO-A mode of operation ....................................................................................................... 7-177 Improved PPS performance of 450 Platform Family .................................................................... 7-179 Setting up SNMP agent ................................................................................................................... 7-180 Configuring SM/BHSs IP over-the-air access .......................................................................... 7-181 Configuring SNMP .................................................................................................................... 7-183 Configuring syslog ........................................................................................................................... 7-188 Syslog event logging ................................................................................................................. 7-189 Configuring system logging ....................................................................................................... 7-189 Configuring remote access .............................................................................................................. 7-194 Accessing SM/BHS over-the-air by Web Proxy ........................................................................ 7-194 Monitoring the Link ........................................................................................................................... 7-195 Link monitoring procedure ........................................................................................................ 7-195 Exporting Session Status page of AP/BHM .............................................................................. 7-197 Configuring quality of service ........................................................................................................... 7-198 Maximum Information Rate (MIR) Parameters ......................................................................... 7-198 Token Bucket Algorithm ............................................................................................................ 7-198 MIR Data Entry Checking.......................................................................................................... 7-199 Committed Information Rate (CIR) ........................................................................................... 7-199 Bandwidth from the SM Perspective ......................................................................................... 7-200 Interaction of Burst Allocation and Sustained Data Rate Settings ............................................ 7-200 High-priority Bandwidth ............................................................................................................. 7-200 Traffic Scheduling ..................................................................................................................... 7-202 Setting the Configuration Source .............................................................................................. 7-203 Page viii Contents Configuring Quality of Service (QoS) ........................................................................................ 7-205 Installation Color Code ..................................................................................................................... 7-211 Zero Touch Configuration Using DHCP Option 66 .......................................................................... 7-212 Configuration Steps ................................................................................................................... 7-212 Troubleshooting ........................................................................................................................ 7-217 Configuring Radio via config file ...................................................................................................... 7-218 Import and Export of config file ................................................................................................. 7-218 Configuring cnMaestroTM Connectivity ............................................................................................. 7-220 Configuring a RADIUS server .......................................................................................................... 7-226 Understanding RADIUS for PMP 450 Platform Family ............................................................ 7-226 Choosing Authentication Mode and Configuring for Authentication Servers - AP ............... 7-227 SM Authentication Mode Require RADIUS or Follow AP ................................................. 7-232 Handling Certificates ................................................................................................................. 7-237 Configuring RADIUS servers for SM authentication ................................................................. 7-238 Assigning SM management IP addressing via RADIUS ........................................................... 7-240 Configuring RADIUS server for SM configuration ..................................................................... 7-240 Configuring RADIUS server for SM configuration using Zero Touch feature ........................... 7-244 Using RADIUS for centralized AP and SM user name and password management ............... 7-245 RADIUS Device Data Accounting ............................................................................................. 7-250 RADIUS Device Re-authentication ........................................................................................... 7-253 RADIUS Change of Authorization and Disconnect Message ................................................... 7-255 Microsoft RADIUS support ........................................................................................................ 7-256 Cisco ACS RADIUS Server Support ......................................................................................... 7-260 Configuring VSA ........................................................................................................................ 7-263 Configuring Ping Watchdog ............................................................................................................. 7-267 Chapter 8: Tools ................................................................................................................................... 8-1 Using Spectrum Analyzer tool .............................................................................................................. 8-2 Mapping RF Neighbor Frequencies .............................................................................................. 8-2 Spectrum Analyzer tool ................................................................................................................. 8-3 Remote Spectrum Analyzer tool ................................................................................................. 8-11 Using the Alignment Tool ................................................................................................................... 8-14 Aiming page and Diagnostic LED SM/BHS ............................................................................. 8-15 Alignment Tone ........................................................................................................................... 8-19 Using the Link Capacity Test tool ...................................................................................................... 8-21 Performing Link Test ................................................................................................................... 8-21 Performing Extrapolated Link Test .............................................................................................. 8-26 Link Capacity Test page of AP .................................................................................................... 8-28 Link Capacity Test page of BHM/BHS/SM .................................................................................. 8-29 Using AP Evaluation tool ................................................................................................................... 8-31 AP Evaluation page ..................................................................................................................... 8-31 Using BHM Evaluation tool ................................................................................................................ 8-35 BHM Evaluation page of BHS ..................................................................................................... 8-35 Using the OFDM Frame Calculator tool ............................................................................................. 8-39 Using the Subscriber Configuration tool ............................................................................................ 8-43 Page ix Contents Using the Link Status tool .................................................................................................................. 8-44 Link Status AP/BHM ................................................................................................................. 8-44 Link Status SM/BHS ................................................................................................................. 8-47 Using BER Results tool ...................................................................................................................... 8-49 Using the Sessions tool ..................................................................................................................... 8-50 Using the Ping Test tool ..................................................................................................................... 8-51 Chapter 9: Operation ........................................................................................................................... 9-1 System information .............................................................................................................................. 9-2 Viewing General Status................................................................................................................. 9-2 Viewing Session Status ............................................................................................................... 9-20 Viewing Remote Subscribers ...................................................................................................... 9-29 Interpreting messages in the Event Log ..................................................................................... 9-29 Viewing the Network Interface .................................................................................................... 9-32 Viewing the Layer 2 Neighbors ................................................................................................... 9-32 System statistics ................................................................................................................................ 9-33 Viewing the Scheduler statistics ................................................................................................. 9-33 Viewing list of Registration Failures statistics ............................................................................. 9-35 Interpreting Bridging Table statistics ........................................................................................... 9-37 Interpreting Translation Table statistics ...................................................................................... 9-37 Interpreting Ethernet statistics .................................................................................................... 9-38 Interpreting RF Control Block statistics ....................................................................................... 9-41 Interpreting Sounding statistics for AP .......................................................................................... 9-1 Interpreting Sounding statistics for SM ......................................................................................... 9-1 Interpreting VLAN statistics ........................................................................................................... 9-2 Interpreting Data VC statistics ...................................................................................................... 9-4 Interpreting Throughput statistics .................................................................................................. 9-6 Interpreting Overload statistics ..................................................................................................... 9-9 Interpreting DHCP Relay statistics .............................................................................................. 9-10 Interpreting Filter statistics .......................................................................................................... 9-12 Viewing ARP statistics ................................................................................................................ 9-13 Viewing NAT statistics ................................................................................................................. 9-13 Viewing NAT DHCP Statistics ..................................................................................................... 9-15 Interpreting Sync Status statistics ............................................................................................... 9-16 Interpreting PPPoE Statistics for Customer Activities ................................................................. 9-17 Interpreting Bridge Control Block statistics ................................................................................. 9-19 Interpreting Pass Through Statistics ........................................................................................... 9-22 Interpreting SNMPv3 Statistics ................................................................................................... 9-23 Interpreting syslog statistics ........................................................................................................ 9-25 Interpreting Frame Utilization statistics ....................................................................................... 9-25 Radio Recovery ................................................................................................................................. 9-36 Radio Recovery Console PMP/PTP 450i/450b and PMP 450m .............................................. 9-36 Default Mode (or Default/Override Plug) - PMP/PTP 450 Series ............................................... 9-39 Reference information ................................................................................................. 10-1 Equipment specifications ................................................................................................................... 10-2 Chapter 10:

Page x Contents Specifications for PMP 450m Series - AP ................................................................................... 10-2 Specifications for PMP 450i Series - AP ..................................................................................... 10-6 Specifications for PMP 450i Series - SM .................................................................................. 10-12 Specifications for PTP 450i Series - BH ................................................................................... 10-17 Specifications for PMP 450b Series - SM ................................................................................. 10-21 Specifications for PMP 450 Series - AP .................................................................................... 10-26 Specifications for PMP 450 Series - SM ................................................................................... 10-31 Specifications for PTP 450 Series - BH .................................................................................... 10-36 PSU specifications .................................................................................................................... 10-41 Data network specifications ............................................................................................................. 10-43 Ethernet interface ...................................................................................................................... 10-43 Wireless specifications ..................................................................................................................... 10-44 General wireless specifications ................................................................................................. 10-44 Link Range and Throughput ..................................................................................................... 10-45 Country specific radio regulations .................................................................................................... 10-46 Type approvals .......................................................................................................................... 10-46 DFS for 2.4 and 5 GHz Radios ................................................................................................. 10-47 Equipment Disposal ......................................................................................................................... 10-49 Waste (Disposal) of Electronic and Electric Equipment ............................................................ 10-49 Country specific maximum transmit power ............................................................................... 10-49 Country specific frequency range ............................................................................................. 10-69 FCC specific information ........................................................................................................... 10-88 Innovation Science and Economic Development Canada (ISEDC) specific information ......... 10-96 Troubleshooting ........................................................................................................... 11-1 General troubleshooting procedure ................................................................................................... 11-2 General planning for troubleshooting .......................................................................................... 11-2 General fault isolation process .................................................................................................... 11-3 Secondary Steps ......................................................................................................................... 11-3 Troubleshooting procedures .............................................................................................................. 11-5 Module has lost or does not establish connectivity ..................................................................... 11-5 NAT/DHCP-configured SM has lost or does not establish connectivity ..................................... 11-7 SM Does Not Register to an AP ................................................................................................. 11-8 Module has lost or does not gain sync ........................................................................................ 11-9 Module does not establish Ethernet connectivity ...................................................................... 11-10 CMM4 does not pass proper GPS sync to connected modules ............................................... 11-11 Module Software Cannot be Upgraded ..................................................................................... 11-12 Module Functions Properly, Except Web Interface Became Inaccessible ............................... 11-12 Power-up troubleshooting ................................................................................................................ 11-13 Registration and connectivity troubleshooting ................................................................................. 11-14 SM/BMS Registration ................................................................................................................ 11-14 Logs ................................................................................................................................................. 11-15 Persistent Logging .................................................................................................................... 11-15 Appendix A - 450m Reference information ............................................................................................... I Specifications .................................................................................................................................... I Chapter 11:

Page xi Contents 450m overload ................................................................................................................................... I Glossary ...................................................................................................................................................... III Page xii List of Figures List of Figures Figure 1 PMP/PTP 450 Platform Family typical bridge deployment ........................................................ 1-13 Figure 2 TDD frame division .................................................................................................................... 1-16 Figure 3 PMP 450b Series - SM interfaces ................................................................................................ 2-9 Figure 4 PMP/PTP 450 Series - AP interfaces ........................................................................................ 2-10 Figure 5 PMP/PTP 450 Series SM/BH interfaces ................................................................................. 2-11 Figure 6 PMP/PTP 450 Series SM/BH Connectorized interfaces ........................................................ 2-12 Figure 7 PMP 450d Series - SM Integrated Dish ..................................................................................... 2-13 Figure 8 PMP 450 Series SM 3 GHz Integrated ................................................................................... 2-13 Figure 9 PTP 450 Series BHM/BHS ..................................................................................................... 2-13 Figure 10 AP/BHM diagnostic LEDs, viewed from unit front ................................................................... 2-15 Figure 11 AP/BH diagnostic LEDs, viewed from unit front ...................................................................... 2-17 Figure 12 AC Power Injector interfaces ................................................................................................... 2-21 Figure 13 AC+DC Enhanced Power Injector interfaces ........................................................................... 2-22 Figure 14 -48 V DC Power Injector interfaces ......................................................................................... 2-24 Figure 15 -20 to 32 VDC Power Injector interfaces ................................................................................. 2-25 Figure 16 Gigabit Enet Capable power supply ........................................................................................ 2-27 Figure 17 PMP 450m Series - AP rear interfaces .................................................................................... 2-29 Figure 18 PMP/PTP 450i Series - ODU rear interfaces ........................................................................... 2-30 Figure 19 PMP/PTP 450i Series Connectorized ODU antenna interfaces ........................................... 2-31 Figure 20 PMP 450b Series - ODU rear interfaces ................................................................................. 2-32 Figure 21 Outdoor drop cable .................................................................................................................. 2-34 Figure 22 Optical SFP transceiver module ............................................................................................. 2-36 Figure 23 Long cable gland..................................................................................................................... 2-36 Figure 24 Alignment Tone Cable ............................................................................................................. 2-38 Figure 25 RJ12 Alignment Tone Cable .................................................................................................... 2-38 Figure 26 Cable gland (part number #N000065L033) ............................................................................. 2-39 Figure 27 Cable grounding kit .................................................................................................................. 2-42 Figure 28 UGPS ....................................................................................................................................... 2-45 Figure 29 Cluster Management: Scenario 1 ............................................................................................ 2-47 Figure 30 Cluster Management: Scenario 2 ............................................................................................ 2-48 Figure 31 Controller Module..................................................................................................................... 2-48 Figure 32 Injector Module ........................................................................................................................ 2-49 Figure 33 CMM4 (Rack Mount) ................................................................................................................ 2-51 Figure 34 CMM4 56 V power adapter (dongle)........................................................................................ 2-52 Figure 35 CMM4 power adapter cabling diagram .................................................................................... 2-52 Figure 36 CMM4 (Cabinet with switch) .................................................................................................... 2-54 Figure 37 CMM3 ...................................................................................................................................... 2-56 Figure 38 Pole mounted CMM3 ............................................................................................................... 2-56 Figure 39 GPS antenna mounting ........................................................................................................... 2-58 Figure 40 Mast or tower installation ........................................................................................................... 3-2 Page xiii List of Figures Figure 41 Wall installation .......................................................................................................................... 3-3 Figure 42 Roof installation ......................................................................................................................... 3-4 Figure 43 GPS receiver wall installation .................................................................................................... 3-5 Figure 44 GPS receiver tower or mast installation .................................................................................... 3-6 Figure 45 Rolling sphere method to determine the lightning protection zones .......................................... 3-9 Figure 46 Example layout of 16 Access Point sectors (ABCD), 90 degree sectors ................................ 3-20 Figure 47 Example layout of 6 Access Point sectors (ABC), 60 degree sectors ..................................... 3-21 Figure 48 Reflection ................................................................................................................................. 3-23 Figure 49 Sector Antenna ........................................................................................................................ 3-24 Figure 50 cnMedusa Antenna .................................................................................................................. 3-25 Figure 51 PMP 450m Series AP antenna beam ...................................................................................... 3-26 Figure 52 Determinants in Rx signal level ............................................................................................... 3-29 Figure 53 Cambium networks management domain ............................................................................... 3-34 Figure 54 Example of IP address in Class B subnet ............................................................................... 3-36 Figure 55 Categorical protocol filtering .................................................................................................... 3-47 Figure 56 Remote AP deployment ........................................................................................................... 3-52 Figure 57 Example for 900-MHz remote AP behind 5 GHz SM .............................................................. 3-54 Figure 58 Remote AP wired to SM that also serves a customer ............................................................. 3-55 Figure 59 Remote AP wired to SM that serves as a relay ....................................................................... 3-56 Figure 60 Additional link to extend network sync, Design 3 .................................................................... 3-57 Figure 61 Additional link to extend network sync, Design 4 .................................................................... 3-58 Figure 62 Additional link to extend network sync, Design 5 .................................................................... 3-59 Figure 63 Co-located AP or BH timing master Sync Setting configuration .............................................. 3-60 Figure 64 Pin 1 location ........................................................................................................................... 5-10 Figure 65 Straight-through Ethernet Cable .............................................................................................. 5-12 Figure 66 AP/BHM to UGPS cable .......................................................................................................... 5-14 Figure 67 Alignment tone cable pin configuration .................................................................................... 5-15 Figure 68 RJ-12 pinout for the default plug .............................................................................................. 5-15 Figure 69 PMP 450 900 MHz SM grounding ............................................................................................. 6-6 Figure 70 Gigabit Etherner Surge Suppressor ........................................................................................ 6-11 Figure 71 600SSH Surge Suppressor inside ....................................................................................... 6-12 Figure 72 Grounding cable minimum bend radius and angle .................................................................. 6-14 Figure 73 Grounding and lightning protection on wall ............................................................................. 6-15 Figure 74 Grounding and lightning protection on mast or tower .............................................................. 6-17 Figure 75 Grounding and lightning protection on building ....................................................................... 6-18 Figure 76 RJ45 cable ............................................................................................................................... 6-20 Figure 77 AP antenna parts ..................................................................................................................... 6-26 Figure 78 Antenna top plate ..................................................................................................................... 6-27 Figure 79 Attaching antenna plate to the AP ........................................................................................... 6-27 Figure 80 Attaching the plate ................................................................................................................... 6-28 Figure 81 Connect the port A and B to the PMP 450i AP ........................................................................ 6-28 Figure 82 AP antenna upper bracket assembly ....................................................................................... 6-29 Figure 83 AP antenna upper bracket attached to upper adjustment arms .............................................. 6-29 Figure 84 Rear strap connected to upper AP antenna bracket ............................................................... 6-30 Page xiv List of Figures Figure 85 Assembled upper bracket connected to AP antenna .............................................................. 6-30 Figure 86 AP Antenna Lower Bracket Assembly ..................................................................................... 6-30 Figure 87 Lower bracket attached to AP antenna ................................................................................... 6-31 Figure 88 Completed AP and antenna assembly .................................................................................... 6-31 Figure 89 PMP 450 AP antenna parts ..................................................................................................... 6-32 Figure 90 AP antenna upper bracket assembly ...................................................................................... 6-33 Figure 91 AP antenna upper bracket attached to upper adjustment arms ............................................. 6-33 Figure 92 Rear strap connected to upper AP antenna bracket .............................................................. 6-34 Figure 93 Assembled upper bracket connected to AP antenna ............................................................. 6-34 Figure 94 AP Antenna Lower Bracket Assembly .................................................................................... 6-35 Figure 95 Lower bracket attached to AP antenna .................................................................................. 6-35 Figure 96 Attaching bracket to the rear of the AP ................................................................................... 6-36 Figure 97 Lower bracket attached to AP antenna .................................................................................. 6-36 Figure 98 Mounted PMP 450 AP and antenna assembly, viewed from back and back ......................... 6-37 Figure 99 Attaching the AP antenna upper bracket to the pole ............................................................... 6-38 Figure 100 Attaching the AP antenna lower bracket to the pole.............................................................. 6-38 Figure 101 Variables for calculating angle of elevation (and depression) ............................................... 6-40 Figure 102 PMP 450i AP 900 MHz antenna unbox view ........................................................................ 6-41 Figure 103 PMP 450i AP 900 MHz antenna inventory ........................................................................... 6-41 Figure 104 Attaching radio mounting PMP 450i AP 900 MHz antenna to the pole ................................ 6-46 Figure 105 900 MHz sector antenna alignment ...................................................................................... 6-47 Figure 106 PMP 450i SM 900 MHz external directional antenna ............................................................ 6-48 Figure 107 Attach the antenna to the pole .............................................................................................. 6-48 Figure 108 Fixing the nuts ....................................................................................................................... 6-49 Figure 109 Fixing the radio to the antenna .............................................................................................. 6-50 Figure 110 Connecting RF cable to the radio .......................................................................................... 6-50 Figure 111 Yagi antenna alignment - horizontally ................................................................................... 6-51 Figure 112 Yagi antenna alignment - upward tilt .................................................................................... 6-51 Figure 113 Yagi antenna alignment - downward tilt ................................................................................ 6-51 Figure 114 PMP 450m Series - AP unbox view ...................................................................................... 6-52 Figure 115 Fixing the mounting plate to the back of the ODU ................................................................. 6-55 Figure 116 Attaching the bracket body .................................................................................................... 6-55 Figure 117 Ethernet cable gland for PMP/PTP 450 Series .................................................................... 6-57 Figure 118 Ethernet cable gland for PMP/PTP 450i Series .................................................................... 6-57 Figure 119 Disarm Installation page (top and bottom of page shown) .................................................... 7-11 Figure 120 Regional Settings tab of AP/BHM .......................................................................................... 7-12 Figure 121 Radio Carrier Frequency tab of AP/BHM .............................................................................. 7-13 Figure 122 Synchronization tab of AP/BHM ............................................................................................ 7-14 Figure 123 LAN IP Address tab of the AP/BHM ...................................................................................... 7-15 Figure 124 Review and Save Configuration tab of the AP/BHM ............................................................. 7-16 Figure 125 Time tab of the AP/BHM ........................................................................................................ 7-17 Figure 126 Time and date entry formats .................................................................................................. 7-18 Figure 127 Session Status tab of AP ....................................................................................................... 7-20 Figure 128 NAT disabled implementation ................................................................................................ 7-28 Page xv List of Figures Figure 129 NAT with DHCP client and DHCP server implementation ..................................................... 7-29 Figure 130 NAT with DHCP client implementation .................................................................................. 7-29 Figure 131 NAT with DHCP server implementation ................................................................................ 7-30 Figure 132 NAT without DHCP implementation ....................................................................................... 7-30 Figure 133 General page attributes - PMP 450 AP ................................................................................. 7-87 Figure 134 General page attributes - PMP 450 SM ................................................................................. 7-88 Figure 135 General page attributes - PTP 450 BHM ............................................................................... 7-89 Figure 136 General page attributes - PTP 450 BHS ............................................................................... 7-90 Figure 137 Sync Setting configuration ..................................................................................................... 7-97 Figure 138 AP Evaluation Configuration parameter of Security tab for PMP ........................................ 7-102 Figure 139 BHM Evaluation Configuration parameter of Security tab for PTP ...................................... 7-102 Figure 140 RF Telnet Access Restrictions (orange) and Flow through (green) .................................... 7-109 Figure 141 RF Telnet Access Restriction (orange) and Potential Security Hole (green) ...................... 7-110 Figure 142 PMP 450i AP Radio attributes - 3 GHz ................................................................................ 7-131 Figure 143 PMP 450i SM Radio attributes - 3 GHz ............................................................................... 7-137 Figure 144 Multicast VC statistics .......................................................................................................... 7-171 Figure 145 Multicast scheduler statistics ............................................................................................... 7-171 Figure 146 AP DFS Status .................................................................................................................... 7-175 Figure 147 AP Session Status page ...................................................................................................... 7-194 Figure 148 AP Remote Subscribers page ............................................................................................. 7-194 Figure 149 Session Status page ............................................................................................................ 7-195 Figure 150 Exporting Session Status page of PMP 450m AP ............................................................... 7-197 Figure 151 Uplink and downlink rate caps adjusted to apply aggregate cap ........................................ 7-199 Figure 152 Uplink and downlink rate cap adjustment example ............................................................. 7-199 Figure 153 Installation Color Code of AP ............................................................................................... 7-211 Figure 154 Configuration File upload and download page .................................................................... 7-218 Figure 155 Software Upgrade from cnMaestro .................................................................................. 7-221 Figure 156 DNS Test for cnMaestro connectivity ............................................................................... 7-222 Figure 157 Device Agent Logs ............................................................................................................... 7-223 Figure 158 Example cnMaestro screenshot ....................................................................................... 7-224 Figure 159 SM Certificate Management ................................................................................................ 7-238 Figure 160 User Authentication and Access Tracking tab of the SM .................................................... 7-249 Figure 161 RADIUS accounting messages configuration ...................................................................... 7-253 Figure 162 Device re-authentication configuration ................................................................................ 7-253 Figure 163 RADIUS CoA configuration for AP ....................................................................................... 7-255 Figure 164 EAPPEAP settings ............................................................................................................... 7-256 Figure 165 Importing certificate in NPS ................................................................................................. 7-257 Figure 166 Selecting MD5 from NPS console ....................................................................................... 7-258 Figure 167 User configuration ................................................................................................................ 7-258 Figure 168 RADIUS VSA configuration ................................................................................................. 7-259 Figure 169 Adding RADIUS client .......................................................................................................... 7-260 Figure 170 Creating users ...................................................................................................................... 7-260 Figure 171 Creating RADIUS instance .................................................................................................. 7-261 Figure 172 RADIUS protocols ................................................................................................................ 7-261 Page xvi List of Figures Figure 173 Service selection .................................................................................................................. 7-262 Figure 174 Adding Trusted CA .............................................................................................................. 7-262 Figure 175 Installing Server Certificate .................................................................................................. 7-262 Figure 176 Monitoring logs ..................................................................................................................... 7-263 Figure 177 VSA list ................................................................................................................................ 7-264 Figure 178 Spectrum analysis - Results .................................................................................................... 8-3 Figure 179 Spectrum Analyzer page result PMP 450 SM .................................................................... 8-10 Figure 180 Alignment Tool tab of SM Receive Power Level > -70 dBm ............................................... 8-14 Figure 181 Alignment Tool tab of SM Receive Power Level between -70 to -80 dBm ......................... 8-14 Figure 182 Alignment Tool tab of SM Receive Power Level < -80 dBm ............................................... 8-14 Figure 183 PMP/PTP 450i Series link alignment tone ............................................................................. 8-19 Figure 184 Link Capacity Test PMP 450m Series AP .......................................................................... 8-22 Figure 185 Link Test with Multiple VCs (1518-byte packet length).......................................................... 8-24 Figure 186 Link Capacity Test PMP 450/450i Series AP ..................................................................... 8-24 Figure 187 Link Test without Bridging (1714-byte packet length)............................................................ 8-25 Figure 188 Extrapolated Link Test results ............................................................................................... 8-27 Figure 189 SM Configuration page of AP ................................................................................................ 8-43 Figure 190 BER Results tab of the SM .................................................................................................... 8-49 Figure 191 Sessions tab of the AP .......................................................................................................... 8-50 Figure 192 Ping Test tab of the AP .......................................................................................................... 8-51 Figure 193 Remote Subscribers page of AP ........................................................................................... 9-29 Figure 194 Event log data ........................................................................................................................ 9-30 Figure 195 Network Interface tab of the AP ............................................................................................. 9-32 Figure 196 Network Interface tab of the SM ............................................................................................ 9-32 Figure 197 Layer 2 Neighbors page ........................................................................................................ 9-32 Figure 198 Bridging Table page ............................................................................................................... 9-37 Figure 199 Translation Table page of SM ................................................................................................ 9-38 Figure 200 ARP page of the SM .............................................................................................................. 9-13 Figure 201 Recovery Options page ......................................................................................................... 9-38 Figure 202 SM Logs ............................................................................................................................... 11-15 Figure 203 SM Session log .................................................................................................................... 11-15 Figure 204 SM Authentication log .......................................................................................................... 11-15 Figure 205 SM Authorization log ............................................................................................................ 11-16 Page xvii List of Tables List of Tables Table 1 Main characteristics of the PMP 450m Series AP ........................................................................ 1-3 Table 2 PMP 450m Series hardware configurations ................................................................................. 1-3 Table 3 Main characteristics of the PMP/PTP 450i Series ........................................................................ 1-4 Table 4 PMP/PTP 450i Series hardware configurations ............................................................................ 1-5 Table 5 Main characteristics of the PMP 450b Series ............................................................................... 1-7 Table 6 PMP 450b Series hardware configurations .................................................................................. 1-8 Table 7 Main characteristics of the PMP/PTP 450 Series ....................................................................... 1-10 Table 8 PMP/PTP 450 Series hardware configurations .......................................................................... 1-11 Table 9 Supported Interoperability for PMP ............................................................................................ 1-12 Table 10 Supported Interoperability for PTP ........................................................................................... 1-12 Table 11 Modulation levels ...................................................................................................................... 1-18 Table 12 PMP 450m Series variants ......................................................................................................... 2-2 Table 13 PMP 450i Series variants ............................................................................................................ 2-3 Table 14 PMP 450b Series variants .......................................................................................................... 2-3 Table 15 PMP 450 Series variants ............................................................................................................ 2-4 Table 16 PTP 450i Series variants ............................................................................................................ 2-5 Table 17 PTP 450 Series variants ............................................................................................................. 2-6 Table 18 PMP 450m Series AP interface descriptions and cabling .......................................................... 2-7 Table 19 PMP/PTP 450i Series - AP/SM/BH interface descriptions and cabling ...................................... 2-9 Table 20 PMP 450b Series - SM interface descriptions and cabling ....................................................... 2-10 Table 21 PMP/PTP 450 Series - AP interface descriptions and cabling 2.4 GHz and 5 GHz .............. 2-11 Table 22 AP/BHM LED descriptions ........................................................................................................ 2-16 Table 23 SM/BHS LED descriptions ........................................................................................................ 2-18 Table 24 PSU part numbers for PMP 450m AP....................................................................................... 2-19 Table 25 PSU part numbers for PMP/PTP 450i Series ........................................................................... 2-20 Table 26 AC Power Injector interface functions ....................................................................................... 2-21 Table 27 AC+DC Enhanced Power Injector interface functions .............................................................. 2-23 Table 28 -48V DC Power Injector interfaces ............................................................................................ 2-24 Table 29 -Power Injector interfaces ......................................................................................................... 2-25 Table 30 PSU part numbers for PMP 450b SM ....................................................................................... 2-25 Table 31 PSU part numbers for PMP/PTP 450 Series ............................................................................ 2-26 Table 32 Gigabit Enet Capable power supply........................................................................................ 2-26 Table 33 Accessories part numbers ........................................................................................................ 2-28 Table 34 Lightning protection part numbers ............................................................................................ 2-28 Table 35 PMP 450m Series AP rear interfaces .................................................................................... 2-29 Table 36 PMP/PTP 450i Series ODU rear interfaces ........................................................................... 2-30 Table 37 PMP 450b Series ODU rear interfaces .................................................................................. 2-32 Table 38 PSU drop cable length restrictions ............................................................................................ 2-33 Table 39 Drop cable part numbers .......................................................................................................... 2-34 Table 40 SFP module kit part numbers .................................................................................................. 2-35 Page xviii List of Tables Table 41 Single Mode Optical SFP Interface per ODU (part number C000065L008) ............................ 2-35 Table 42 Multi-mode Optical SFP Interface per ODU (part number C000065L009) .............................. 2-35 Table 43 Main port PoE cable pinout ....................................................................................................... 2-37 Table 44 Aux port PoE cable pinout ........................................................................................................ 2-37 Table 45 Aux port PoE cable pinout ........................................................................................................ 2-38 Table 46 RJ12 Aux port PoE cable pinout ............................................................................................... 2-39 Table 47 Alignment tone adapter third party product details ................................................................... 2-39 Table 48 RJ45 connector and spare gland part numbers ........................................................................ 2-39 Table 49 LPU and grounding kit contents ................................................................................................ 2-41 Table 50 LPU and grounding kit part number .......................................................................................... 2-42 Table 51 Cable grounding kit part numbers ............................................................................................. 2-42 Table 52 List of AP external antennas ..................................................................................................... 2-43 Table 53 PTP 450i Series BH or PMP 450/450i Series SM external antenna ........................................ 2-43 Table 54 RF cable and connector part numbers...................................................................................... 2-44 Table 55 CMM5 Cluster Management Scenario 1 ................................................................................... 2-46 Table 56 CMM5 Cluster Management Scenario 2 ................................................................................... 2-47 Table 57 Injector Compatibility Matrix ...................................................................................................... 2-49 Table 58 CMM5 Specifications ................................................................................................................ 2-50 Table 59 CMM4 power adapter cable pinout ........................................................................................... 2-53 Table 60 PMP 450m Series ODU part numbers ...................................................................................... 2-60 Table 61 PMP 450i Series ODU part numbers ........................................................................................ 2-60 Table 62 PMP 450i ATEX/HAZLOC ODU models/part numbers ............................................................ 2-61 Table 63 PTP 450i Series ODU part numbers ......................................................................................... 2-62 Table 64 PTP 450i ATEX/HAZLOC ODU models/part numbers ............................................................ 2-63 Table 65 PMP 450b Series ODU part numbers ....................................................................................... 2-63 Table 66 PMP 450 Series ODU part numbers ......................................................................................... 2-64 Table 67 PTP 450 Series ODU part numbers .......................................................................................... 2-66 Table 68 PMP/PTP 450/450I Series Accessories ................................................................................... 2-66 Table 69 PMP 450m Series wind loading (Newton) ................................................................................ 3-12 Table 70 PMP/PTP 450i Series wind loading (Newton) .......................................................................... 3-12 Table 71 PMP 450m Series wind loading (lb force) ................................................................................. 3-12 Table 72 PMP/PTP 450i Series wind loading (lb force) ........................................................................... 3-13 Table 73 PMP/PTP 450 Series wind loading (Newton) ........................................................................... 3-13 Table 74 PMP/PTP 450 Series wind loading (lb force) ............................................................................ 3-14 Table 75 EIRP limits from ATEX and HAZLOC standards ..................................................................... 3-15 Table 76 Example 5.8 GHz 4-channel assignment by access site .......................................................... 3-20 Table 77 Example 5.8 GHz 3-channel assignment by access site .......................................................... 3-21 Table 78 RF cable lengths required to achieve 1.2 dB loss at 5.8 GHz .................................................. 3-31 Table 79 Special case VLAN IDs ............................................................................................................. 3-38 Table 80 VLAN filters in point-to-multipoint modules ............................................................................... 3-39 Table 81 Q-in-Q Ethernet frame .............................................................................................................. 3-40 Table 82 HTTPS security material ........................................................................................................... 3-43 Table 83 Ports filtered per protocol selections ......................................................................................... 3-48 Table 84 Device default port numbers ..................................................................................................... 3-48 Page xix List of Tables Table 85 Safety compliance specifications .............................................................................................. 4-22 Table 86 EMC emissions compliance ...................................................................................................... 4-22 Table 87 FCC minimum safe distances PMP 450m 5.1 GHz, 5.2 GHz, 5.4 GHz and 5.8 GHz ........... 4-25 Table 88 FCC minimum safe distances PMP/PTP 450i 900 MHz, 3.65 GHz, 4.9 GHz, 5.1 GHz, 5.2 GHz, 5.4 GHz and 5.8 GHz ............................................................................................................... 4-26 Table 89 ISEDC minimum safe distances PMP/PTP 450i, 900 MHz, 3.5 GHz, 3.65 GHz, 4.9 GHz, 5.2 GHz, 5.4 GHz, and 5.8 GHz .............................................................................................................. 4-27 Table 90 FCC minimum safe distances PMP/PTP 450 900 MHz, 2.4 GHz, 3.65 GHz and 5 GHz ...... 4-29 Table 91 ISEDC minimum safe distances PMP/PTP 450 900 MHz, 2.4 GHz, 3.5/3.65 GHz and 5 GHz 4-

30 Table 92 Radio certifications .................................................................................................................... 4-35 Table 93 Tools for PMP and PTP 450 Platform ODU installation .............................................................. 5-8 Table 94 Main port pinout ........................................................................................................................ 5-11 Table 95 Aux port pinout .......................................................................................................................... 5-11 Table 96 RJ-45 pinout for straight-through Ethernet cable ...................................................................... 5-12 Table 97 RJ-45 pinout for crossover Ethernet cable ............................................................................... 5-13 Table 98 AP/BHM to UGPS cable pinout ................................................................................................. 5-14 Table 99 PMP/PTP 450i Series - ODU mounting bracket part numbers ................................................... 6-2 Table 100 RJ45 connector and cable color code .................................................................................... 6-20 Table 101 Menu options and web pages ................................................................................................... 7-7 Table 102 Session Status Attributes AP ............................................................................................... 7-21 Table 103 IP interface attributes .............................................................................................................. 7-24 Table 104 SM/BHS private IP and LUID .................................................................................................. 7-25 Table 105 Aux port attributes ................................................................................................................... 7-26 Table 106 IP attributes - SM with NAT disabled ...................................................................................... 7-32 Table 107 IP attributes - SM with NAT enabled ....................................................................................... 7-34 Table 108 NAT attributes - SM with NAT disabled .................................................................................. 7-35 Table 109 NAT attributes - SM with NAT enabled ................................................................................... 7-37 Table 110 SM DNS Options with NAT Enabled ....................................................................................... 7-42 Table 111 NAT Port Mapping attributes - SM .......................................................................................... 7-42 Table 112 VLAN Remarking Example ..................................................................................................... 7-44 Table 113 AP/BHM VLAN tab attributes .................................................................................................. 7-46 Table 114 Q-in-Q Ethernet frame ............................................................................................................ 7-47 Table 115 SM VLAN attributes ................................................................................................................ 7-49 Table 116 SM VLAN Membership attributes ............................................................................................ 7-53 Table 117 BHM VLAN page attributs ....................................................................................................... 7-53 Table 118 BHS VLAN page attributes ..................................................................................................... 7-56 Table 119 SM PPPoE attributes .............................................................................................................. 7-58 Table 120 DiffServ attributes AP/BHM .................................................................................................. 7-60 Table 121 Packet Filter Configuration attributes ...................................................................................... 7-62 Table 122 General page attributes PMP 450i AP ................................................................................. 7-68 Table 123 General page attributes PMP 450m AP ................................................................................ 7-73 Table 124 General page attributes PMP 450i SM ................................................................................ 7-75 Table 125 General page attributes PTP 450i BHM .............................................................................. 7-78 Table 126 General page attributes PTP 450i BHS ............................................................................... 7-80 Page xx List of Tables Table 127 General page attributes PMP 450i SM ................................................................................ 7-83 Table 128 Unit Settings attributes 450 Platform Family AP/BHM ......................................................... 7-92 Table 129 SM Unit Settings attributes ..................................................................................................... 7-94 Table 130 450 Platform Family - AP/BHM Time attributes ..................................................................... 7-95 Table 131 Add User page of account page - AP/ SM/BH ...................................................................... 7-100 Table 132 Delete User page - 450 Platform Family - AP/ SM/BH ......................................................... 7-101 Table 133 Change User Setting page - 450 Platform Family AP/ SM/BH ............................................. 7-101 Table 134 User page 450 Platform Family AP/SM/BH ........................................................................ 7-102 Table 135 AP/BHM Protocol Filtering attributes .................................................................................... 7-105 Table 136 SM/BHS Protocol Filtering attributes .................................................................................... 7-107 Table 137 Port Configuration attributes AP/SM/BHM/BMS ................................................................ 7-108 Table 138 Security attributes 450 Platform Family AP ........................................................................ 7-114 Table 139 Security attributes 450 Platform Family SM ........................................................................ 7-119 Table 140 Security attributes - 450 Platform Family BHS ..................................................................... 7-124 Table 141 PMP 450m AP Radio attributes - 5 GHz ............................................................................... 7-127 Table 142 PMP 450i AP Radio attributes - 5 GHz ................................................................................. 7-132 Table 143 PMP 450i SM Radio attributes 5 GHz ............................................................................... 7-138 Table 144 PMP 450i AP Radio attributes - 900 MHz ............................................................................. 7-143 Table 145 PTP 450i BHM Radio page attributes 5 GHz ..................................................................... 7-145 Table 146 PTP 450i BHS Radio attributes 5 GHz .............................................................................. 7-148 Table 147 PMP 450i SM Radio attributes 5 GHz ............................................................................... 7-151 Table 148 PMP 450 AP Radio attributes - 5 GHz .................................................................................. 7-155 Table 149 PMP 450 AP Radio attributes - 3.65 GHz ............................................................................. 7-157 Table 150 PMP 450 AP Radio attributes - 3.5 GHz ............................................................................... 7-158 Table 151 PMP 450 AP Radio attributes - 2.4 GHz ............................................................................... 7-159 Table 152 PMP 450 SM Radio attributes 5 GHz ................................................................................ 7-160 Table 153 PMP 450 SM Radio attributes 3.65 GHz ........................................................................... 7-162 Table 154 PMP 450 SM Radio attributes 3.5 GHz ............................................................................. 7-163 Table 155 PMP 450 SM Radio attributes 2.4 GHz ............................................................................. 7-164 Table 156 PMP 450 SM Radio attributes 900 MHz ............................................................................. 7-165 Table 157 PTP 450 BHM Radio attributes 5 GHz ............................................................................... 7-167 Table 158 PTP 450 BHM Radio attributes 5 GHz ............................................................................... 7-168 Table 159 Example for mix of multicast and unicast traffic scenarios ................................................... 7-170 Table 160 450 Platform Family AP/SM/BH Custom Frequencies page 5 GHz .................................. 7-172 Table 161 PMP/PTP 450 SM/BH Custom Frequencies page 3.65 GHz ............................................ 7-173 Table 162 PMP/PTP 450 SM/BH Custom Frequencies page 3.5 GHz .............................................. 7-174 Table 163 Contention slots and number of SMs .................................................................................... 7-176 Table 164 450 Platform Family Modulation levels ................................................................................. 7-177 Table 165 Co-channel Interference per (CCI) MCS .............................................................................. 7-178 Table 166 Adjacent Channel Interference (ACI) per MCS ..................................................................... 7-178 Table 167 LAN1 Network Interface Configuration tab of IP page attributes .......................................... 7-181 Table 168 SNMP page attributes ........................................................................................................... 7-183 Table 169 Syslog parameters ................................................................................................................ 7-189 Table 170 Syslog Configuration attributes - AP ..................................................................................... 7-190 Page xxi List of Tables Table 171 Syslog Configuration attributes - SM .................................................................................... 7-191 Table 172 Syslog Configuration attributes - BHS .................................................................................. 7-192 Table 173 Characteristics of traffic scheduling ...................................................................................... 7-202 Table 174 Recommended combined settings for typical operations ..................................................... 7-203 Table 175 Where feature values are obtained for a SM with authentication required ........................... 7-203 Table 176 MIR, VLAN, HPC, and CIR Configuration Sources, Authentication Disabled ...................... 7-204 Table 177 QoS page attributes - AP ...................................................................................................... 7-205 Table 178 QoS page attributes - SM ..................................................................................................... 7-207 Table 179 QoS page attributes - BHM ................................................................................................... 7-209 Table 180 QoS page attributes - BHS ................................................................................................... 7-210 Table 181 Configuring cnMaestro .......................................................................................................... 7-220 Table 182 Security tab attributes ........................................................................................................... 7-228 Table 183 SM Security tab attributes ..................................................................................................... 7-232 Table 184 RADIUS Vendor Specific Attributes (VSAs) ......................................................................... 7-241 Table 185 AP User Authentication and Access Tracking attributes ...................................................... 7-247 Table 186 SM User Authentication and Access Tracking attributes ...................................................... 7-249 Table 187 Device data accounting RADIUS attributes .......................................................................... 7-250 Table 188 Ping Watchdog attributes ...................................................................................................... 7-267 Table 189 Spectrum Analyzer page attributes - AP ................................................................................... 8-4 Table 190 Spectrum Analyzer page attributes - SM .................................................................................. 8-6 Table 191 Spectrum Analyzer page attributes - BHM ............................................................................... 8-7 Table 192 Spectrum Analyzer page attributes - BHS ................................................................................ 8-8 Table 193 Remote Spectrum Analyzer attributes - AP ............................................................................ 8-12 Table 194 Remote Spectrum Analyzer attributes - BHM ......................................................................... 8-13 Table 195 Aiming page attributes SM ................................................................................................... 8-16 Table 196 Aiming page attributes - BHS .................................................................................................. 8-18 Table 197 Alignment Tool Headsets and Alignment tone adapter third party product details ................. 8-20 Table 198 Link Capacity Test page attributes AP ................................................................................. 8-28 Table 199 Link Capacity Test page attributes BHM/BHS ..................................................................... 8-30 Table 200 AP Evaluation tab attributes - AP ............................................................................................ 8-31 Table 201 BHM Evaluation tab attributes - BHS ...................................................................................... 8-35 Table 202 OFDM Frame Calculator page attributes ................................................................................ 8-40 Table 203 OFDM Calculated Frame Results attributes ........................................................................... 8-41 Table 204 Color code versus uplink/downlink rate column ...................................................................... 8-44 Table 205 Link Status page attributes AP/BHM ................................................................................... 8-45 Table 206 Link Status page attributes SM/BHS ................................................................................... 8-47 Table 207 General Status page attributes PMP 450m AP ..................................................................... 9-3 Table 208 General Status page attributes PMP 450/450i AP ................................................................. 9-8 Table 209 General Status page attributes - SM....................................................................................... 9-11 Table 210 General Status page attributes - BHM .................................................................................... 9-15 Table 211 General Status page attributes - BHS .................................................................................... 9-18 Table 212 Device tab attributes ............................................................................................................... 9-20 Table 213 Session tab attributes ............................................................................................................. 9-21 Table 214 Power tab attributes ................................................................................................................ 9-23 Page xxii List of Tables Table 215 Configuration tab attributes ..................................................................................................... 9-25 Table 216 Session Status > Configuration CIR configuration denotations .............................................. 9-27 Table 217 Link Quality tab attributes ....................................................................................................... 9-28 Table 218 Event Log messages for abnormal events ............................................................................. 9-30 Table 219 Event Log messages for normal events ................................................................................. 9-31 Table 220 Scheduler tab attributes .......................................................................................................... 9-33 Table 221 SM Registration Failures page attributes - AP ........................................................................ 9-35 Table 222 BHS Registration Failures page attributes - BHM .................................................................. 9-36 Table 223 Flags status ............................................................................................................................. 9-36 Table 224 Ethernet tab attributes ............................................................................................................. 9-38 Table 225 Radio (Statistics) page attributes RF Control Block ............................................................. 9-41 Table 226 Radio (Statistics - AP) page attributes - Sounding ................................................................... 9-1 Table 227 Radio (Statistics - SM) page attributes - Sounding ................................................................... 9-1 Table 228 VLAN page attributes ................................................................................................................ 9-2 Table 229 Data VC page attributes ............................................................................................................ 9-4 Table 230 RF overload Configuration attributes AP/BHM ...................................................................... 9-6 Table 231 Overload page attributes AP/SM/BHM/BHS .......................................................................... 9-9 Table 232 DHCP Relay page attributes AP/SM ................................................................................... 9-11 Table 233 Filter page attributes - SM ....................................................................................................... 9-12 Table 234 NAT page attributes - SM ....................................................................................................... 9-14 Table 235 NAT DHCP Statistics page attributes - SM ............................................................................. 9-15 Table 236 Sync Status page attributes - AP ............................................................................................ 9-16 Table 237 PPPoE Statistics page attributes - SM ................................................................................... 9-17 Table 238 Bridge Control Block page attributes AP/SM/BHM/BHS ..................................................... 9-19 Table 239 Pass Through Statistics page attributes AP ........................................................................ 9-22 Table 240 SNMPv3 Statistics page attributes AP ................................................................................. 9-23 Table 241 Syslog statistics page attributes AP/SM/BH ........................................................................ 9-25 Table 242 Frame utilization statistics for PMP 450m AP ......................................................................... 9-26 Table 243 Frame utilization statistics for 450/450i/450m ......................................................................... 9-33 Table 244 Recovery Options attributes .................................................................................................... 9-38 Table 245 PMP 450m Series - AP specifications .................................................................................... 10-2 Table 246 PMP 450i Series - AP specifications....................................................................................... 10-6 Table 247 PMP 450i Series - SM specifications .................................................................................... 10-12 Table 248 PTP 450i Series - BH specifications ..................................................................................... 10-17 Table 249 PMP 450b Series - SM specifications ................................................................................... 10-21 Table 250 PMP 450 Series - AP specifications ..................................................................................... 10-26 Table 251 PMP 450 Series - SM specifications ..................................................................................... 10-31 Table 252 PTP 450 Series - BH specifications ...................................................................................... 10-36 Table 253 PMP/PTP 450i AC power Injector specifications .................................................................. 10-41 Table 254 PMP/PTP 450 power supply specifications (part number: N000900L001A) ........................ 10-42 Table 255 450m/450i Series Main and Aux Ethernet bridging specifications ........................................ 10-43 Table 256 450 Series Ethernet bridging specifications .......................................................................... 10-43 Table 257 450 Platform Family - wireless specifications ....................................................................... 10-44 Table 258 Radio certifications ............................................................................................................... 10-46 Page xxiii List of Tables Table 259 Country & Bands DFS setting ............................................................................................... 10-47 Table 260 Default combined transmit power per country 900 MHz band PMP 450i Series ............... 10-49 Table 261 Default combined transmit power per country 2.4 GHz band PMP/PTP 450 Series ......... 10-50 Table 262 Default combined transmit power per country 3.5 GHz band PMP/PTP 450 Series ......... 10-51 Table 263 Default combined transmit power per country 3.65 GHz band PMP/PTP 450 .................. 10-52 Table 264 Default combined transmit power per country 4.9 GHz band PMP/PTP 450/450i/450b Series

......................................................................................................................................................... 10-52 Table 265 Default combined transmit power per Country 5.1 GHz band PMP/PTP 450i/450b Series .. 10-

54 Table 266 Default combined transmit power per Country 5.1 GHz band PMP 450m Series ............. 10-55 Table 267 Default combined transmit power per country 5.2 GHz band ............................................ 10-57 Table 268 Default combined transmit power per Country 5.2 GHz band PMP 450m Series ............. 10-59 Table 269 Default combined transmit power per country 5.4 GHz band PMP 450m Series .............. 10-60 Table 270 Default combined transmit power per country 5.4 GHz band PMP/PTP 450i Series ........ 10-61 Table 271 Default combined transmit power per country 5.4 GHz band PMP 450 Series ................. 10-64 Table 272 Default combined transmit power per Country 5.8 GHz band PMP 450m Series ............. 10-65 Table 273 Default combined transmit power per country 5.8 GHz band PMP/PTP 450i Series ........ 10-65 Table 274 Default combined transmit power per country 5.8 GHz band PMP 450 Series ................. 10-67 Table 275 Frequency range per country 900 MHz band .................................................................... 10-69 Table 276 Frequency range per country 2.4 GHz band PMP/PTP 450 Series .................................. 10-70 Table 277 Frequency range per country 3.5 GHz band PMP/PTP 450 Series .................................. 10-70 Table 278 Frequency range per country 3.65 GHz band PMP/PTP 450 Series ................................ 10-71 Table 279 Frequency range per country 4.9 GHz band PMP/PTP 450i/450b Series ........................ 10-72 Table 280 Frequency range per country 5.4 GHz band PMP/PTP 450i/450b Series ........................ 10-77 Table 281 Frequency range per country 5.4 GHz band PMP/PTP 450 Series ............... 10-79 Table 282 Frequency range per country 5.8 GHz band PMP/PTP 450i Series ................................. 10-83 Table 283 Frequency range per country 5.8 GHz band PMP/PTP 450 Series .................................. 10-84 Table 284 US FCC IDs .......................................................................................................................... 10-88 Table 285 USA approved antenna list 4.9 GHz ..................................................................................... 10-94 Table 286 USA approved antenna list 5.1 and 5.2 GHz ........................................................................ 10-95 Table 287 USA approved antenna list 5.4 GHz ..................................................................................... 10-95 Table 288 USA approved antenna list 5.8 GHz ..................................................................................... 10-96 Table 289 ISEDC Certification Numbers .............................................................................................. 10-98 Table 290 Canada approved antenna list 4.9 and 5.8 GHz ................................................................... 10-99 Table 291 Canada approved antenna list 5.2 and 5.4 GHz ................................................................ 10-100 Page xxiv About This User Guide This guide describes the planning, installation, configuration and operation of the Cambium point-to-point and point-to-multipoint wireless Ethernet bridges. It covers PMP/PTP 450, 450i, 450b, 450d and PMP 450m platform Series. It is intended for use by the system designer, system installer and system administrator. For radio network design, refer to the following chapters:

Chapter 1: Product description Chapter 2: System hardware Chapter 3: System planning Chapter 4: Legal and regulatory information Chapter 5: Preparing for installation Chapter 6: Installation For system configuration, tools and troubleshooting, refer to the following chapters:

Chapter 7: Configuration Chapter 8: Tools Chapter 9: Operation Chapter 10: Reference information Chapter 11: Troubleshooting Contacting Cambium Networks Support website:

Main website:

Sales enquiries:

Support enquiries:

Repair enquiries:

Telephone number list:

Address:

https://support.cambiumnetworks.com http://www.cambiumnetworks.com solutions@cambiumnetworks.com https://support.cambiumnetworks.com https://support.cambiumnetworks.com http://www.cambiumnetworks.com/contact Cambium Networks Limited, Global Headquarters, 3800 Golf Road, Suite 360, Rolling Meadows, IL 60008 USA Page 1 Purpose Cambium Networks Point-to-Multi-Point (PMP)/Point-To-Point (PTP) 450 documents are intended to instruct and assist personnel in the operation, installation and maintenance of the Cambium PMP/PTP equipment and ancillary devices of 450 Platform Family. It is recommended that all personnel engaged in such activities be properly trained. Cambium disclaims all liability whatsoever, implied or express, for any risk of damage, loss or reduction in system performance arising directly or indirectly out of the failure of the customer, or anyone acting on the customer's behalf, to abide by the instructions, system parameters, or recommendations made in this document. Product notation conventions in document This document covers Cambium 450 Series, 450i Series and 450m Series products. The following notation conventions are followed while referring to product series and product family:

Product notation 450 Platform Family Description Refers to the complete 450 Series family, which includes 450 Series, 450i Series and 450m Series 450 Series 450i Series Refers to 450 Series devices in the following configurations:

- PMP 450

- AP [2.4GHz/3.5 GHz/3.65 GHz /5 GHz]

- Connectorized

- SM [900 MHz/2.4GHz/3.5 GHz/3.65 GHz /5 GHz]

- Connectorized/ Integrated

- PTP 450 BHM/ BHS [900 MHz/3.5 GHz/3.65 GHz/5 GHz]

- Connectorized/ Integrated

- PMP 450d SM [5 GHz]

Refers to 450i Series devices in the following configurations:

- PMP 450i

- AP [900 MHz/3 GHz/5 GHz]

- Connectorized/ Integrated

- SM [3 GHz/5 GHz]

- Connectorized/ Integrated

- PTP 450i BHM/ BHS [3 GHz/5 GHz]

- Connectorized/ Integrated 450b Series Refers to 450b Series devices in the following configurations:

- PMP 450b

- SM [5 GHz]

-

Integrated Page 2 450m Series Refers to 450m Series device configuration:

- PMP 450m AP 5 GHz

-

Integrated Cross references References to external publications are shown in italics. Other cross references, emphasized in blue text in electronic versions, are active links to the references. This document is divided into numbered chapters that are divided into sections. Sections are not numbered, but are individually named at the top of each page, and are listed in the table of contents. Feedback We appreciate feedback from the users of our documents. This includes feedback on the structure, content, accuracy, or completeness of our documents. To provide feedback, visit our support website.https://support.cambiumnetworks.com. Page 3 Important regulatory information The 450 Platform Family products are certified as an unlicensed device in frequency bands where it is not allowed to cause interference to licensed services (called primary users of the bands). Application software Download the latest 450 Platform Family software and install it in the Outdoor Units (ODUs) before deploying the equipment. Instructions for installing software are provided in Upgrading the software version and using CNUT on page 7-64. USA specific information Caution This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

This device may not cause harmful interference, and This device must accept any interference received, including interference that may cause undesired operation The USA Federal Communications Commission (FCC) requires manufacturers to implement special features to prevent interference to weather radar systems that operate in the band 5600 MHz to 5650 MHz. These features must be implemented in all products able to operate outdoors in the band 5470 MHz to 5725 MHz. Manufacturers must ensure that such radio products cannot be configured to operate outside of FCC rules; specifically it must not be possible to disable or modify the radar protection functions that have been demonstrated to the FCC. Cambium supplies variants of the 450i and 450m Series specifically for operation in the USA in order to comply with FCC requirements (KDB 905462 D02 UNII DFS Compliance Procedures New Rules v01r02). These variants are only allowed to operate with license keys that comply with FCC rules. Similarly, Cambium supplies variants of the 450 Series specifically for operation in the USA in order to comply with FCC requirements (KDB 443999 D01 Approval of DFS UNII Devices v01r04). These variants are only allowed to operate with license keys that comply with FCC rules. To ensure compliance when using PMP 450 Series and PTP 450 Series, follow the recommendation in Avoidance of weather radars

(USA only). Page 4 External antennas When using a connectorized version of the product, the conducted transmit power may need to be reduced to ensure the regulatory limit on transmitter EIRP is not exceeded. The installer must have an understanding of how to compute the effective antenna gain from the actual antenna gain and the feeder cable losses. The range of permissible values for maximum antenna gain and feeder cable losses are included in this user guide together with a sample calculation. The product GUI automatically applies the correct conducted power limit to ensure that it is not possible for the installation to exceed the EIRP limit, when the appropriate values for antenna gain and feeder cable losses are entered into the GUI. Avoidance of weather radars (USA only) To comply with FCC rules (KDB 443999: Interim Plans to Approve UNII Devices Operating in the 5470 -

5725 MHz Band with Radar Detection and DFS Capabilities), units which are installed within 35 km (22 miles) of a Terminal Doppler Weather Radar (TDWR) system (or have a line of sight propagation path to such a system) must be configured to avoid any frequency within +30 MHz or 30 MHz of the frequency of the TDWR device. This requirement applies even if the master is outside the 35 km (22 miles) radius but communicates with outdoor clients which may be within the 35 km (22 miles) radius of the TDWRs. If interference is not eliminated, a distance limitation based on line-of-sight from TDWR will need to be used. Devices with bandwidths greater than 20 MHz may require greater frequency separation. When planning a link in the USA, visit http://spectrumbridge.com/udia/home.aspx, enter the location of the planned link and search for TDWR radars. If a TDWR system is located within 35 km (22 miles) or has line of sight propagation to the PTP device, perform the following tasks:

Register the installation on http://spectrumbridge.com/udia/home.aspx. Make a list of channel center frequencies that must be barred, that is, those falling within +30 MHz or 30 MHz of the frequency of the TDWR radars. The 450 Platform Family AP must be configured to not operate on the affected channels. Canada specific information Caution This device complies with ISEDC s license-exempt RSSs. Operation is subject to the following two conditions:

(1) This device may not cause interference; and

(2) This device must accept any interference, including interference that may cause undesired operation of the device. ISEDC requires manufacturers to implement special features to prevent interference to weather radar systems that operate in the band 5600 MHz to 5650 MHz. These features must be implemented in all products able to operate outdoors in the band 5470 MHz to 5725 MHz. Page 5 Manufacturers must ensure that such radio products cannot be configured to operate outside of ISEDC rules; specifically it must not be possible to disable or modify the radar protection functions that have been demonstrated to ISEDC . In order to comply with these ISEDC requirements, Cambium supplies variants of the 450 Platform Family for operation in Canada. These variants are only allowed to operate with license keys that comply with ISEDC rules. In particular, operation of radio channels overlapping the band 5600 MHz to 5650 MHz is not allowed and these channels are permanently barred. In addition, other channels may also need to be barred when operating close to weather radar installations. Other variants of the 450 Platform Family are available for use in the rest of the world, but these variants are not supplied to Canada except under strict controls, when they are needed for export and deployment outside Canada. Renseignements specifiques au Canada Attention Le prsent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorise aux deux conditions suivantes :

(1) l'appareil ne doit pas produire de brouillage, et

(2) l'utilisateur de l'appareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible d'en compromettre le fonctionnement. ISEDC a demand aux fabricants de mettre en uvre des mcanismes spcifiques pour viter dinterfrer avec des systmes radar fonctionnant dans la bande 5600 MHz 5650 MHz. Ces mcanismes doivent tre mis en uvre dans tous les produits capables de fonctionner l'extrieur dans la bande 5470 MHz 5725 MHz. Les fabricants doivent s'assurer que les produits de radiocommunications ne peuvent pas tre configurs pour fonctionner en dehors des rgles ISEDC , en particulier, il ne doit pas tre possible de dsactiver ou modifier les fonctions de protection des radars qui ont t dmontrs ISEDC . Afin de se conformer ces exigences de ISEDC , Cambium fournit des variantes du 450 Platform Family exclusivement pour le Canada. Ces variantes ne permettent pas lquipement de fonctionner en dehors des rgles de ISEDC . En particulier, le fonctionnement des canaux de radio qui chevauchent la bande 5600-5650 MHz est interdite et ces canaux sont dfinitivement exclus. ISEDC Approved Antennas The list of antennas used to obtain ISEDC approvals is provided in section Country specific radio regulations, Innovation Science and Economic Development Canada (ISEDC) , Table 306. Page 6 Antennas externes Lorsque vous utilisez une version du produit sans antenne intgre, il peut tre ncessaire de rduire la puissance d'mission pour garantir que la limite rglementaire de puissance isotrope rayonne quivalente (PIRE) n'est pas dpasse. L'installateur doit avoir une bonne comprhension de la faon de calculer le gain de l'antenne relle et les pertes dans les cbles de connections. La plage de valeurs admissibles pour un gain maximal de l'antenne et des pertes de cbles de connections sont inclus dans ce guide d'utilisation avec un exemple de calcul. L'interface utilisateur du produit applique automatiquement la limite de puissance mene correct afin de s'assurer qu'il ne soit pas possible pour l'installation de dpasser la limite PIRE, lorsque les valeurs appropries pour le gain d'antenne et les pertes de cbles d'alimentation sont entres dans linterface utilisateur. Antennes approuves par ISEDC La liste des antennas approves pour loperation au Canada est founie dans le chapitre Country specific radio regulations, Innovation Science and Economic Development Canada (ISEDC) tableaux Table 306. EU Declaration of Conformity Hereby, Cambium Networks declares that the Cambium 450 Series, 450i Series and 450m Series Wireless Ethernet Bridge complies with the essential requirements and other relevant provisions of Directive 1999/5/EC. The declaration of conformity may be consulted at:

http://www.cambiumnetworks.com/support/ec-doc Specific expertise and training for professional installers To ensure that the 450 Platform Family products PMP/PTP 450 Series, PMP/PTP 450i Series, PMP 450m Series are installed and configured in compliance with the requirements of ISEDC and the FCC, installers must have the radio engineering skills and training described in this section. The Cambium Networks technical training program details can be accessed from below link:

http://www.cambiumnetworks.com/training/category/technical-training/

Ethernet networking skills The installer must have the ability to configure IP addressing on a PC and to set up and control products using a web browser interface. Lightning protection To protect outdoor radio installations from the impact of lightning strikes, the installer must be familiar with the normal procedures for site selection, bonding and grounding. Installation guidelines for the 450 Platform Family can be found in Chapter 2: System hardware and Chapter 3: System planning. Page 7 Training The installer needs to have basic competence in radio and IP network installation. The specific requirements applicable to the 450 Platform should be gained by reading Chapter 5: Preparing for installation, Chapter 6: Installation, Chapter 7: Configuration, Chapter 8: Tools and Chapter 9: Operation;

and by performing sample set ups at base workshop before live deployments. The Cambium Networks technical training program details can be accessed from below link:

http://www.cambiumnetworks.com/training/category/technical-training/

Page 8 Problems and warranty Reporting problems If any problems are encountered when installing or operating this equipment, follow this procedure to investigate and report:

1 Search this document and the software release notes of supported releases. 2 Visit the support website. 3 Ask for assistance from the Cambium product supplier. 4 Gather information from affected units, such as any available diagnostic downloads. 5 Escalate the problem by emailing or telephoning support. Repair and service If unit failure is suspected, obtain details of the Return Material Authorization (RMA) process from the support website (http://www.cambiumnetworks.com/support). Hardware warranty Cambiums standard hardware warranty is for one (1) year from date of shipment from Cambium Networks or a Cambium distributor. Cambium Networks warrants that hardware will conform to the relevant published specifications and will be free from material defects in material and workmanship under normal use and service. Cambium shall within this time, at its own option, either repair or replace the defective product within thirty (30) days of receipt of the defective product. Repaired or replaced product will be subject to the original warranty period but not less than thirty (30) days. To register PMP and PTP products or activate warranties, visit the support website. For warranty assistance, contact the reseller or distributor. The removal of the tamper-evident seal will void the warranty. Caution Using non-Cambium parts for repair could damage the equipment or void warranty. Contact Cambium for service and repair instructions. Portions of Cambium equipment may be damaged from exposure to electrostatic discharge. Use precautions to prevent damage. Page 9 Security advice Cambium Networks systems and equipment provide security parameters that can be configured by the operator based on their particular operating environment. Cambium recommends setting and using these parameters following industry recognized security practices. Security aspects to be considered are protecting the confidentiality, integrity, and availability of information and assets. Assets include the ability to communicate, information about the nature of the communications, and information about the parties involved. In certain instances Cambium makes specific recommendations regarding security practices, however the implementation of these recommendations and final responsibility for the security of the system lies with the operator of the system. Page 10 Warnings, cautions, and notes The following describes how warnings and cautions are used in this document and in all documents of the Cambium Networks document set. Warnings Warnings precede instructions that contain potentially hazardous situations. Warnings are used to alert the reader to possible hazards that could cause loss of life or physical injury. A warning has the following format:

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

Caution Caution text and consequence for not following the instructions in the caution. Notes A note means that there is a possibility of an undesirable situation or provides additional information to help the reader understand a topic or concept. A note has the following format:

Note Note text. Page 11 Caring for the environment The following information describes national or regional requirements for the disposal of Cambium Networks supplied equipment and for the approved disposal of surplus packaging. In EU countries The following information is provided to enable regulatory compliance with the European Union (EU) directives identified and any amendments made to these directives when using Cambium equipment in EU countries. Disposal of Cambium equipment European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE) Do not dispose of Cambium equipment in landfill sites. For disposal instructions, refer to http://www.cambiumnetworks.com/support/weee-compliance Disposal of surplus packaging Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipients responsibility to ensure that packaging materials are collected and recycled according to the requirements of EU environmental law. In non-EU countries In non-EU countries, dispose of Cambium equipment and all surplus packaging in accordance with national and regional regulations. Page 12 Chapter 1: Product description This chapter provides a high level description of 450 Platform Family products. It describes in general terms the function of the product, the main product variants and the main hardware components. The following topics are described in this chapter:

Overview of the 450 Platform Family on page 1-2 introduces the key features, typical uses, product variants and components of the 450 Platform Family. Wireless operation on page 1-16 describes how the 450 Platform Family wireless link is operated, including modulation modes and spectrum management. System management on page 1-21 introduces the 450 Platform Family management system, including the web interface, configuration, security, alerts and recovery. Page 1-1 Chapter 1: Product description Overview of the 450 Platform Family Overview of the 450 Platform Family This section introduces the key features, typical uses, product variants and components of the 450 Platform Family. Purpose Cambium 450 Platform Family products are designed for Ethernet bridging over point-to-point and point-

to-multipoint microwave links in unlicensed and lightly-licensed frequency bands 900MHz, 2.4 GHz, 3.5/3.65 GHz and 4.9 to 5.925 GHz. Users must ensure that the 450 Platform Family complies with local operating regulations. The 450 Platform Family acts as a transparent bridge between two or more segments of the operators network. In this sense, it can be treated as a virtual wired connection among points. The 450 Series platform forwards 802.3 Ethernet frames destined for the other part of the network and filters frames it does not need to forward. 450 Platform Family The 450 Series platform supports following:

PMP 450m Series PMP/PTP 450i Series PMP 450b Series PMP/PTP 450 Series PMP 450m Series The PMP 450m Series AP is a revolutionary product which is based on Multi-User Multiple-Input and Multiple-Output (MU-MIMO) technology. By combining a sophisticated beam forming antenna array with multiple transceivers, Cambium Networks is using leading edge technology to provide a substantial shift upward in capacity per sector. Key features The Cambium PMP 450m Series AP offers the following benefits:

MU-MIMO Access Point is a technologically cutting edge device providing more than 400 Mbps in 20 MHz Channel bandwidth depending upon SMs position within sector PMP 450m AP is compatible with existing PMP 450/450i Series Subscriber Modules(SM), providing an easy network upgrade path. This benefits to re-use existing SMs (i.e. capital investment). 3x higher throughput packet rate compare 450 Series Gigabit copper/power port combined, 1000BaseT port with power out and SFP port Integrated with 14x14 MU-MIMO antenna Page 1-2 Chapter 1: Product description Overview of the 450 Platform Family More than 20 bps/Hz spectral efficiency and over 40 bps/Hz when deployed in frequency re-use configuration Table 1 gives a summary of the main PMP 450m Series AP characteristics. Table 1 Main characteristics of the PMP 450m Series AP Characteristic Topology Wireless link condition Range Duplexing Connectivity Operating frequencies Tx Power Channel bandwidth High spectral efficiency Timing synchronization Data rate Value PMP LOS, near LOS or non-LOS PMP: Up to 40 mi (or 64 km) TDD (symmetric and asymmetric) 1000Base-T Ethernet Main port with PoE input 5.150 to 5.925 GHz 38 dBm EIRP 5, 10, 15, 20, and 40 MHz More than 40 bps/Hz1 CMM5 or UGPS more than 400 Mbps (20 MHz channel BW) Frequency bands The PMP 450m Series AP operates from 5150 to 5925 MHz bands. Hardware components The ODU (Outdoor unit) is a self-contained transceiver unit that houses both radio and networking electronics. The PMP 450m Series is supplied in the following configurations:

Table 2 PMP 450m Series hardware configurations ODU Frequency PMP 450m AP 5150 to 5925 MHz ODU type Integrated 14 dBi, 90 MU-MIMO sector antenna 1 This is achieved in an ABAB frequency reuse AP deployment model. Page 1-3 Chapter 1: Product description Overview of the 450 Platform Family PMP/PTP 450i Series The PMP/PTP 450i Series is a high performance wireless bridge for Ethernet traffic. It is capable of operating in line-of-sight (LOS), near-LOS and non-LOS propagation conditions. It supports 900 MHz, 3 GHz, and 4.9 to 5.925 GHz frequency band. Key features The PMP/PTP 450i Series has extensive quality of service (QoS) involving traffic classification, traffic policy and shaping capability. The Cambium PMP/PTP 450i Series offers the following benefits:

Cambiums high performing point-to-multipoint solution, with up to 310 Mbps (40 MHz Channel Bandwidth and 5 ms Frame Period) usable throughput for PMP and PTP State-of-the-art MIMO (Multi In Multi Out) technology Upto 7.5 bps/Hz spectral efficiency Increased Packet Processing rate Efficient GPS synchronized, scheduled TDD operation for easy AP/BHM site deployment and performance that is consistent regardless of SM/BHS loading A range of cost-effective subscriber device solutions to meet the business case of any network application MIMO B Mode: This technique provides for the ability to double the throughput of a radio transmission under proper RF conditions. Different data streams are transmitted simultaneously on two different antennas MIMO-A mode: This mode of operation has same modulation levels as the MIMO-B mode, namely:

QPSK, 16-QAM, 64-QAM and 256-QAM. This mode increases system reliability in the links. Timing synchronization via CMM4, CMM5, or UGPS Table 3 gives a summary of the main PMP/PTP 450i Series characteristics. Table 3 Main characteristics of the PMP/PTP 450i Series Characteristic Value Topology Wireless link condition Range Duplexing Connectivity Operating frequencies PMP/PTP LOS, near LOS or non-LOS PTP Up to 186 mi (or 299 km) depending on configuration for all bands PMP: Up to 40 mi (or 64 km) for 5 GHz band PMP: Up to 120 mi (or 193 km) for 900 MHz band TDD (symmetric and asymmetric) 1000Base-T Ethernet Main port with PoE input 902 to 928 MHz 3.3 to 3.9 GHz Page 1-4 Chapter 1: Product description Overview of the 450 Platform Family Tx Power Channel bandwidth Spectral efficiency Timing synchronization Data rate 4.9 to 5.925 GHz Max 25 dBm (3 GHz) max 27 dBm (5 GHz) max 25 dBm (900 MHz) 5, 7, 10, 15, 20, 30, and 40 MHz Note All bands do not support all channel bandwidths. For more information, refer to this link. Up to 7.5 bps/Hz CMM4, CMM5, or UGPS Up to 310 Mbps (40 MHz channel BW) for PMP/PTP Frequency bands The PMP/PTP 450i Series ODU can operate in the following bands:

900 MHz band: 902 to 928 MHz 3 GHz band: 3300 to 3900 MHz 5 GHz band: 4900 to 5925 MHz Note 900 MHz, 3 GHz, and 5 GHz bands with different frequencies require different hardware components. Hardware components The ODU (Outdoor unit) is a self-contained transceiver unit that houses both radio and networking electronics. The main hardware components of the PMP/PTP 450i Series are as follows:

PMP 450i AP PMP 450i SM PTP 450i BH (BHM/BHS) The PMP/PTP 450i Series is supplied in the following configurations:

Table 4 PMP/PTP 450i Series hardware configurations ODU Frequency ODU type Page 1-5 Chapter 1: Product description Overview of the 450 Platform Family PMP 450i AP 902 to 928 MHz Connectorized Use with an external antenna 3.3 to 3.9 GHz 4.9 to 5.925 GHz

(support 4.9, 5.1, 5.2, 5.4 and 5.8 GHz) PMP 450i SM 3.3 to 3.9 GHz PTP 450i BH 4.9 to 5.925 GHz

(support 4.9, 5.1, 5.2, 5.4 and 5.8 GHz) 3.3 to 3.9 GHz 4.9 to 5.925 GHz

(support 4.9, 5.1, 5.2, 5.4 and 5.8 GHz) 17 dBi, 90 sector dual slant antenna Integrated Connectorized Use with an external antenna Integrated Connectorized Use with an external antenna 16 dBi, 90 sector antenna 19 dBi, SM/BH with MARS antenna Integrated Connectorized Use with an external antenna Integrated 23 dBi flat panel antenna Connectorized Use with an external antenna Integrated Connectorized Use with an external antenna 19 dBi, SM/BH with MARS antenna Integrated Connectorized Use with an external antenna 23 dBi flat panel antenna Note The BH ODU can be configured as a BHM or a BHS in PTP mode. Page 1-6 Chapter 1: Product description Overview of the 450 Platform Family PMP 450b Series The PMP 450b Series is a high performance wireless Subscriber Module. It supports 4.9 to 5.925 GHz frequency band. Key features The Cambium PMP 450b Series offers the following benefits:

Ultra-wide band radios support the entire band from 4.9 to 5.925 GHz. Gigabit Ethernet Interface provides the maximum transfer rates to the device. 3.5 mm audio jack allows direct connection of headphones without any adapters. Updated FPGA enhances Packet Processing Power more than 4 times that of the 450 SM. Capable of up to 310 Mbps aggregate in a 40 MHz channel. Table 5 gives a summary of the main PMP 450b Series characteristics. Table 5 Main characteristics of the PMP 450b Series Characteristic Value Topology PMP Wireless link condition Range Duplexing LOS, near LOS or non-LOS PMP: Up to 40 mi (or 64 km) TDD (symmetric and asymmetric) Connectivity 100/1000Base-T Ethernet Main port with PoE input Operating frequencies Tx Power Channel bandwidth 4.9 to 5.925 GHz Max 27 dBm 5, 10, 15, 20, 30, and 40 MHz Note All bands do not support all channel bandwidths. For more information, refer to this link. Spectral efficiency Timing synchronization Up to 7.5 bps/Hz CMM4, CMM5, or UGPS Data rate Up to 310 Mbps (40 MHz channel BW) for PMP Page 1-7 Chapter 1: Product description Overview of the 450 Platform Family Frequency bands The PMP 450b Series ODU can operate in the following band:

5 GHz band: 4900 to 5925 MHz Hardware components The ODU (Outdoor unit) is a self-contained transceiver unit that houses both radio and networking electronics. The main hardware components of the PMP 450b Series are as follows:

PMP 450b SM The PMP 450b Series is supplied in the following configurations:

Table 6 PMP 450b Series hardware configurations ODU Frequency PMP 450b SM 4.9 to 5.925 GHz

(support 4.9, 5.1, 5.2, 5.4 and 5.8 GHz) ODU type Integrated 17 dBi flat panel antenna Page 1-8 Chapter 1: Product description Overview of the 450 Platform Family PMP/PTP 450 Series Cambium PMP/PTP 450 Series networks are designed for wireless point-to-multipoint and point-to-point links in the unlicensed/licensed 900 MHz, 2.4 GHz, 3.5 GHz, 3.65 GHz, 5.4 GHz and 5.8 GHz bands. Users must ensure that the PMP/PTP 450 Series complies with local operating regulations. The PMP/PTP 450 Series enables network operators to grow their business by offering more capacity for data, voice and video applications. Key features The Cambium PMP/PTP 450 Series offers the following benefits:

Cambiums point-to-multipoint and point-to-point solution, with up to 310 Mbps usable throughput State-of-the-art MIMO (Multi In Multi Out) technology Efficient GPS synchronized, scheduled TDD operation for easy Access Point site deployment and performance that is consistent regardless of subscriber loading A range of cost-effective subscriber device solutions to meet the business case of a network application MIMO-B Mode: This technique provides for the ability to double the throughput of a radio transmission under proper RF conditions. Different data streams are transmitted simultaneously on two different antennas. MIMO-A mode: This mode of operation using the same modulation levels as the MIMO-B mode, namely: QPSK, 16-QAM, 64-QAM and 256-QAM but it provides an additional combining gain. Table 7 gives a summary of PMP/PTP 450 Series products main characteristics . Page 1-9 Chapter 1: Product description Overview of the 450 Platform Family Table 7 Main characteristics of the PMP/PTP 450 Series Characteristic Topology Wireless link condition Range Value PMP/PTP LOS, near LOS or non-LOS Up to 40 mi (or 64 km) for PMP Up to 186 mi (or 299 km) for PTP Duplexing Connectivity TDD (symmetric and asymmetric) 100Base-T Ethernet Main port with PoE input Operating frequencies 900 MHz, 2.4 GHz, 3.5 GHz, 3.65 GHz and 5 GHz Tx Power max 22 dBm (2.4 GHz and 5 GHz) max 25 dBm (3.5 GHz and 3.65 GHz) max 25 dBm (900 MHz - PMP 450 SM and BH) Channel bandwidth 5, 7, 10, 15, 20, 30, and 40 MHz High spectral efficiency Timing synchronization Data rate All bands do not support all channel bandwidths. For more information, refer to this link. Up to 7.5 bps/Hz CMM4 or UGPS Up to 310 Mbps (40 MHz channel BW) for PMP/PTP Frequency bands The PMP/PTP 450 Series ODU can operate in the following bands:

900 MHz band: 902 to 928 MHz (SM and BH) 2.4 GHz band: 2400 to 2483 MHz 3.5 GHz band: 3300 to 3600 MHz 3.65 GHz band: 3500 to 3850 MHz 5 GHz band: 5470 to 5875 MHz Page 1-10 Chapter 1: Product description Overview of the 450 Platform Family Hardware components The main hardware components of the PMP/PTP 450 are as follows:

PMP 450 AP PMP 450 SM PTP 450 BH (BHM/BHS) The PMP/PTP 450 is supplied in the following configurations:

Table 8 PMP/PTP 450 Series hardware configurations ODU Frequency ODU type PMP 450 AP 2.4 GHz 3.5/3.65 GHz 5 GHz

(5.4 and 5.8 GHz) 900 MHz PMP 450 SM Connectorized Integrated Connectorized Integrated Connectorized Use with an external antenna 18 dBi Dual Slant Use with an external antenna 16 dBi Dual Slant Use with an external antenna Connectorized Use with an external antenna 2.4 GHz Connectorized Use with an external antenna 3.5/3.65 GHz 5 GHz

(5.4 and 5.8 GHz) PTP 450 BH 902 to 928 MHz 3.5/3.65 GHz 5 GHz

(5.4 and 5.8 GHz) Integrated Connectorized Integrated Integrated Connectorized Integrated Integrated Connectorized Connectorized Integrated Connectorized Integrated 7 dBi Dual Slant, integrated patch Use with an external antenna 8 dBi Dual Slant, integrated patch 19 dBi Flat Plate, integrated patch Use with an external antenna 9 dBi H+V, integrated patch 25 dBi H+V, Integrated dish Use with an external antenna Use with an external antenna 8 dBi Dual Slant Use with an external antenna 9 dBi H+V Note The BH ODU can be configured as a BHM or a BHS in PTP mode Page 1-11 Chapter 1: Product description Overview of the 450 Platform Family Supported interoperability for 450m/450i/450b/450 Series The supported interoperability among various 450m/450i/450 Series hardwares are listed below:

Table 9 Supported Interoperability for PMP Band AP SM 5.1, 5.2 and 5.9 GHz PMP 450m AP PMP 450i SM, PMP 450b SM 4.9, 5.1, 5.2 and 5.9 GHz 5.4 and 5.8 GHz 3.5 and 3.65 GHz 2.4 GHz 900 MHz PMP 450i AP PMP 450m AP PMP 450i AP PMP 450 AP PMP 450 AP PMP 450i AP PMP 450 AP PMP 450i AP PMP 450i SM, PMP 450b SM PMP 450i SM, PMP 450 SM, PMP 450d SM, and PMP 450b SM PMP 450 SM, PMP 450i SM PMP 450i SM, PMP 450 SM PMP 450 SM PMP 450 SM Table 10 Supported Interoperability for PTP Band 900 MHz 3.5 and 3.65 GHz 4.9, 5.1, 5.2, 5.4 and 5.8 GHz 5.4 and 5.8 GHz BH PTP 450 BHM and BHS PTP 450/450i BHM and BHS PTP 450i BHM and BHS PTP 450/450i BHM and BHS Page 1-12 Chapter 1: Product description Overview of the 450 Platform Family Typical deployment The 450 Platform Family is an all outdoor solution consisting of a wireless bridge across sites. Each site installation consists of an Integrated or Connectorized outdoor unit (ODU) and a power supply (PSU) (see Figure 1). The ODU provides the following interfaces:

Ethernet port: This provides proprietary power over Ethernet and connection to the management and/or data networks. Figure 1 PMP/PTP 450 Platform Family typical bridge deployment Building 1 Building 2 ODU ODU Lightning protection units Power over Ethernet interface Lightning protection units PSU AC supply Network equipment PSU AC supply Network equipment Page 1-13 Chapter 1: Product description Overview of the 450 Platform Family Point-to-Multipoint The PMP configuration of 450 Platform Family consists of Access Point (AP) and Subscriber Module (SM) ODU. The radio link operates on a single frequency channel in each direction using Time Division Duplex

(TDD). Applications for the PMP Series include:

High throughput enterprise applications nLOS video surveillance in metro areas Urban area network extension Network extension into areas with foliage Point-to-Point (Backhaul) The PTP configuration of 450 Platform Family consists of two BH (Backhaul) ODUs. The customer can decide, via software configuration, if this unit is a BHM (Backhaul Master) or a BHS (Backhaul Slave). The radio link operates on a single frequency channel using Time Division Duplex (TDD). Applications for the PTP Series include:

Enterprise Access nLOS video surveillance Leased line replacements and backup solutions Network extension Page 1-14 Chapter 1: Product description Overview of the 450 Platform Family Product variants The 450 Platform Family is available in the following product variants:

The ODU is supplied in the following regional variants:

o FCC, intended for deployment in the USA o EU, intended for deployment in countries of the European Union or other countries following ETSI regulations o Rest of the World (RoW), intended for deployment in countries other than USA and EU countries. o IC, intended for deployment in Canada A ruggedized ODU Subscriber Module designed to meet IP-66 and IP-67 standards to withstand harsh environments An integrated Dish ODU Subscriber Module in a new, rugged and high gain design for 5 GHz band An indoor power supply module providing Power-over-Ethernet (PoE) supply to ODU (AP/SM/BH) Antennas and antenna cabling: Connectorized ODUs require external antennas connected using RF cable Ethernet cabling: All configurations require a copper Ethernet Cat5e connection from the ODU

(Ethernet port) to the PoE Lightning protection unit (LPU): LPUs are installed in the ports copper drop cables to provide transient voltage surge suppression Surge Suppression: The Gigabit Surge Suppressor provides a path to ground (Protective Earth) that protects connected radio equipment from near-miss lightning strikes. Ground cables: ODU, LPUs and outdoor copper Ethernet cables are bonded to the site grounding system using ground cables. For more information about these components, including interfaces, specifications and Cambium part numbers, refer to Chapter 2: System hardware. Page 1-15 Chapter 1: Product description Wireless operation Wireless operation This section describes how the 450 Platform Family wireless link is operated, including modulation modes, power control and security. Time division duplexing The system uses Time Division Duplexing (TDD) one channel alternately transmits and receives rather than using one channel for transmitting and a second channel for receiving. To accomplish TDD, the AP/BHM must provide sync to its SM/BHS. Furthermore, collocated APs/BHMs must be synced together an unsynchronized AP/BHM that transmits during the receive cycle of a collocated AP/BHM can prevent a second AP/BHM from being able to decode the signals from its APs/BHSs. In addition, across a geographical area, APs/BHMs that can hear each other benefit from using a common sync to further reduce self-interference within the network. Modules use TDD on a common frequency to divide frames for uplink (orange) and downlink (green) usage, as shown in the figure below. For more information on synchronization configuration options, see GPS synchronization on page 2-45. Figure 2 TDD frame division Time Page 1-16 Chapter 1: Product description Wireless operation TDD frame parameters The TDD burst duration varies depending on the following:

Channel Bandwidth Cyclic Prefix Frame Period Frame configuration - Downlink Data Link operation Dynamic Rate Adaptation OFDM and channel bandwidth The PMP/PTP 450 Platform Family 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 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 the following values: 5, 7, 10, 15, 20 and 30 MHz. Higher bandwidths provide greater link capacity at the expense of using more bandwidth. 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. Note The channel bandwidth must be configured to the same value at both ends of the link. Not all channel bandwidths are available in all regulatory bands. Cyclic Prefix OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol (slot) to allow multi-pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. For your convenience, the 450 Platform Family ODUs have been locked to a 1/16 CP. Frame Period The frame period or frame duration is the time between the beginning of a frame and the end of the frame. The 450 Platform Family supports two frame periods: 2.5 ms and 5 ms. Note PMP 450m AP supports 2.5 ms Frame Period only. The 5ms frame period configuration provides higher throughput as a result of reduced frame overhead during transmission. In turn, the 2.5 ms frame period configuration affords reduced latency in the system, half of that introduced by the 5 ms frame configuration. Page 1-17 Chapter 1: Product description Wireless operation Frame configuration - Downlink Data The percentage of frame assigned to transport downlink data. The downlink data specifies the percentage of the aggregate throughput for the downlink (frames transmitted from the AP/BHM to the subscriber). The configurable range is 15% to 85%. Note The maximum configurable range is 34% to 66% for 40 MHz with 5 ms frame. Link operation Dynamic Rate Adapt The 450 Platform Family ODUs offer eight levels or speeds of operation 2X MIMO-B and 1X MIMO-A

(QPSK), 4X MIMO-B and 2X MIMO-A (16-QAM), 6x MIMO-B and 3X MIMO-A (64-QAM) and 8X MIMO-B and 4X MIMO-A (265-QAM). If received power varies due to distance between the AP/BHM and the SM/BHS or due to obstructions, or if interference affects the RF environment, the system automatically and dynamically adjusts the links to the best operation level. The system chooses its modulation rate dynamically, based on an internal ARQ (Automatic Repeat reQuest) error control method. With ARQ, every data slot of every frame sent over the air (except downlink broadcast) is expected to be acknowledged by the receiver, and if acknowledgement is not received, the data is resent. The sending unit monitors these re-sends and adjusts the modulation rate accordingly. It is normal to have links that change levels of operation as the RF environment changes. Furthermore, the uplink or downlink portions of TDD duty cycle operate independently. The various modulation levels used by 450 Platform Family are shown in Table 11. Table 11 Modulation levels Rate QPSK MIMO-B MIMO-A 2X MIMO-B 1X MIMO-A 16-QAM 4X MIMO-B 2X MIMO-A 64-QAM 6X MIMO-B 3X MIMO-A 256-QAM 8X MIMO-B 4X MIMO-A Note MIMO-A achieves half the throughput of MIMO-B but adds a combining diversity (gain) which enhances the link budget or availability. Page 1-18 Chapter 1: Product description Wireless operation Encryption The 450 Platform Family supports optional encryption for data transmitted over the wireless link. The 450 Platform Family supports the following forms of encryption for security of the wireless link:

DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys and 256-bit key size to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. The default setting on an AP is "Disabled". MIMO Multiple-Input Multiple-Output (MIMO) techniques provide protection against fading and increase the probability that the receiver decodes 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 sub-features that comprises the MIMO techniques utilized in the 450 Platform Family ODUs are:

MIMO-A: This technique enables 450 Platform Family radio to use a scheme that optimizes coverage by transmitting the same data over both antennas. This redundancy improves the signal to noise ratio at the receiver making it more robust. MIMO-B: This technique provides the ability to double the throughput of a radio transmission under proper RF conditions. Different data streams are transmitted simultaneously on two different antennas. MU-MIMO Multiple-input multiple-output, or MIMO, is a range of technologies used to multiply the capacity of a wireless connection without requiring more spectrum. Although traditional MIMO techniques are focused on increasing the bandwidth available between two wireless nodes, multi-user MIMO (MU-MIMO) applies these technologies to increase overall wireless network capacity by allowing an access point to communicate wirelessly with more than one wireless node at once. A MU-MIMO access point features an array of antennas. When the AP decides to communicate with multiple nodes at the same time, it creates multiple simultaneous beams each directed to a specific node. This is contrast to a traditional wireless system, where two wireless nodes cannot communicate on the same channel to the same access point at the same time, without causing significant self-interference and degrading the overall wireless network performance. Page 1-19 Chapter 1: Product description Wireless operation A MU-MIMO access point estimates and measures what a transmission from each wireless node sounds like, by applying knowledge of the wireless path characteristics between the access point and node. Known as channel estimation, this process is of vital importance; without it, the access point cannot distinguish properly between wireless nodes, affecting performance. Channel estimation is achieved by the access point sending a specific signal to a wireless node, which the node then reflects back. By measuring how the signal was received back from the node, the access point can estimate the wireless conditions between itself and the node, and know to expect these same conditions to be applied to other communications from that node. This is known as channel sounding. Channel estimation and sounding must be regularly repeated to ensure wireless network performance remains high; the speed at which a system is able to accurately estimate the channel has a large impact on performance. Once channel estimation is completed for a wireless node, the MU-MIMO access point can electrically tune each antenna to provide the highest performance for that node. The access point uses beamforming to create a radio beam to that node which is tuned for optimum performance and avoids beams directed to other nodes, reducing interference and helping to improve overall wireless network capacity. A MU-MIMO access point can communicate to multiple wireless nodes simultaneously using this process. As the majority of nodes are unable to make full use of the whole access point capacity at once, communicating with several nodes simultaneously can greatly improve the overall capacity achieved in the wireless network. Page 1-20 Chapter 1: Product description System management System management This section introduces the 450 Platform Family management system, including the web interface, installation, configuration, alerts and upgrades. Management agent The 450 Platform Family radios are managed through an embedded management agent. Management workstations, network management systems or PCs can be connected to this agent using the modules Ethernet port or over-the air (SM/BHS) The management agent supports the following interfaces:

Hypertext transfer protocol (HTTP) Hypertext transfer protocol secure (HTTPS) RADIUS authentication Simple network management protocol (SNMP) v2c and v3 Network time protocol (NTP) System logging (Syslog) Wireless Manager (WM) software Canopy Network Updater Tool (CNUT) software cnMaestro Web server The 450 Platform Family management agent contains a web server. The web server supports access via the HTTP/HTTPS interface. Web-based management offers a convenient way to manage the 450 Platform Family radios from a locally connected computer or from a network management workstation connected through a management network, without requiring any special management software. The web and SNMP are the interfaces supported for installation of 450 Platform Family radios and for the majority of configuration management tasks. Page 1-21 Chapter 1: Product description System management Web pages The web-based management interfaces provide comprehensive web-based fault, configuration, performance and security management functions organized into the following groups:

Access Point or Backhaul Master:

Home Configuration Statistics Tools Logs Accounts Quick Start Copyright Subscriber Module or Backhaul Slave Home Configuration Statistics Tools Logs Accounts PDA Copyright Identity-based user accounts When identity-based user accounts are configured, a security officer can define from one to four user accounts, each of which may have one of the four possible roles:

ADMINISTRATOR, who has full read and write permissions. This is the level of the root and admin users, as well as any other administrator accounts that one of them creates. INSTALLER, who has permissions identical to those of ADMINISTRATOR except that the installer cannot add or delete users or change the password of any other user. TECHNICIAN, who has permissions to modify basic radio parameters and view informational web pages GUEST, who has no write permissions and only a limited view of General Status tab Admin, Installer and Tech accounts can be configured as READ-ONLY. This will allow the account to only see the items. See Managing module access by passwords for detailed information on account permissions. Page 1-22 Chapter 1: Product description System management Remote Authentication Dial-in User Service (RADIUS) The PMP configuration of 450 Platform Family includes support for RADIUS (Remote Authentication Dial In User Service) protocol functionality including:

SM Authentication: Allows only known SMs onto the network (blocking rogue SMs), and can be configured to ensure SMs are connecting to a known network (preventing SMs from connecting to rogue APs). RADIUS authentication is used for SMs, but not used for APs. SM Configuration: Configures authenticated SMs with MIR (Maximum Information Rate), High Priority, and VLAN (Virtual LAN) parameters from the RADIUS server when a SM registers to an AP. User Authentication allows users to configure a separate User authentication server along with the SM authentication server. If firmware is upgraded while using this functionality and no User authentication servers are configured, then AP continues to use the SM authentication server for User authentication SM Accounting provides support for RADIUS accounting messages for usage-based billing. This accounting includes indications for subscriber session establishment, subscriber session disconnection, and bandwidth usage per session for each SM that connects to the AP. Centralized AP and SM user name and password management: Allows AP and SM usernames and access levels (Administrator, Installer, Technician and Read-Only) to be centrally administered in the RADIUS server instead of on each radio and tracks access events (logon/logoff) for each username on the RADIUS server. This accounting does not track and report specific configuration actions performed on radios or pull statistics such as bit counts from the radios. Such functions require an Element Management System (EMS) such as Cambium Wireless Manager. This accounting is not the ability to perform accounting functions on the subscriber/end user/customer account. Framed-IP-Address: Operators may use a RADIUS server to assign management IP addressing to SM modules. SNMP The management agent supports fault and performance management by means of an SNMP interface. The management agent is compatible with SNMP v2c and SNMP v3 using Management Information Base (MIB) files which are available for download from the Cambium Networks Support website:

https://support.cambiumnetworks.com/files/ptp450 https://support.cambiumnetworks.com/files/pmp450 Network Time Protocol (NTP) The clock supplies accurate date and time information to the system. It can be set to run with or without a connection to a network time server (NTP). It can be configured to display local time by setting the time zone and daylight saving in the Time web page. If an NTP server connection is available, the clock can be set to synchronize with the server time at regular intervals. The 450 Platform Family radios may receive NTP data from a CMM4 module or an NTP server configured in the systems management network. Page 1-23 Chapter 1: Product description System management The Time Zone option is configurable on the APs/BHMs Time Configuration page, and may be used to offset the received NTP time to match the operators local time zone. When set on the AP/BHM, the offset is set for the entire sector (AP/BHSs is notified of the current Time Zone upon initial registration). If a Time Zone change is applied, the AP/BHSs are notified of the change in a best effort fashion, meaning some AP/BHSs may not pick up the change until the next re-registration. Time Zone changes are noted in the Event Log. An AP/BHM which is receiving NTP date and time information from an NTP server or from a GPS synchronization source may be used as an NTP server. Any client which has IP connectivity to the BHM may request NTP date and time information from the AP/BHM. No additional configuration (other than the AP/BHM receiving valid NTP data) is required to use the AP/BHM as an NTP server. Wireless Manager (WM) Cambium Networks Wireless Manager 4.0 is recommended for managing 450 Platform Family networks. You can achieve better uptime through better visibility of your network with the Cambium Wireless Manager. This network management software tool offers breakthrough map-based visualization capabilities using embedded Google maps, and combined with advanced configuration, provisioning, alerting and reporting features you can control your entire outdoor wireless network including Point-to-

Multipoint and Point-to-Point solutions as well as other SNMP enabled devices. With its powerful user interface you can not only be able to control your network's access, distribution and backhaul layers, but can also have visibility to WLAN sites and be able to quickly launch indoor network management systems. Some key features of Wireless Manager are:

Template-Based Configuration: With Wireless Manager's user-defined templates you can accelerate the process for the configuration of the devices you add to your network resulting in quicker and easier deployments. The template-based functionality provides an automated way to configure large numbers of network devices with just a few mouse clicks, and can be scheduled to occur at any time via Wireless Manager's Task Scheduler. Ultralight Thin Client: With the growing mobile workforce it is important to have access to the status of your network at any time. With Wireless Manager you can view the status and performance of your entire wireless network via a compact web interface accessible by your smart phone. Map-Based Visualization: Wireless Manager overlays sophisticated real-time information about your network elements onto building layouts and dynamic Google maps. Visuals can be scaled to view an entire city or building or a specific area, floor or link. High Availability Architecture Support: Wireless Manager offers a high availability option, providing a highly reliable and redundant network management solution that ensures you always have management access to your network. High Scalability: The enhanced Wireless Manager offers you server scalability with support for up to 10,000 nodes as well as support for distributed server architecture. Cambiums Wireless Manager 4.0 available for download at:

http://www.cambiumnetworks.com/support/management-tools/wireless-manager/

Page 1-24 Chapter 1: Product description System management Canopy Network Updater Tool (CNUT) CNUT (Canopy Network Updater Tool) is the stand-alone software update tool for 450 Platform Family ODUs. The CNUT 4.10.4 or greater should be used for 450 Platform Family ODUs. The Canopy Network Updater Tool has the following features:

Automatically discovers all network elements HTTP and HTTPS Executes UDP command that initiates and terminates the Auto-update mode within APs/BHMs. This command is both secure and convenient:

o For security, the AP/BHM accepts this command from only the IP address that specified in the Configuration page of ODU. o For convenience, Network Updater automatically sets this Configuration parameter in the AP/BHM to the IP address of the Network Updater server when the server performs any of the update commands. Allows you to choose among updating:

o Entire network. o Only elements that you select. o Only network branches that you select. Provides a Script Engine that you can use with any script which:

o The user can define. o Cambium supplies. CNUT is available at:

http://www.cambiumnetworks.com/support/management-tools/cnut/

cnMaestro cnMaestro is a cloud-based or on-premises platform specialized for secure, end-to-end network lifecycle management: inventory management, device onboarding, daily operations, and maintenance. The cnMaestro wireless network manager simplifies device management by offering full network visibility. Network operators can have a real-time view of their complete end-to-end network and perform a full suite of wireless network management functions to optimize system availability, maximize throughput, and meet emerging needs of business and residential customers. In addition, the cnMaestro wireless network manager collects and displays compliance with service level agreements. To learn about cnMaestro, please visit http://www.cambiumnetworks.com/products/software-

tools/cnmaestro/

See Configuring cnMaestroTM Connectivity on 7-220 for details. Page 1-25 Chapter 1: Product description System management Radio recovery mode The 450 Platform Family recovery mode provides a means to recover from serious configuration errors including lost or forgotten passwords and unknown IP addresses. The recovery procedure for 450m/450i/450b series and 450 series ODUs differ due to difference in hardwares. This procedure for 450i/450m Series is known as Radio Recovery Console and for 450 Series is known as Default mode (or Default/Override Plug). Radio Recovery Console 450i, 450b and 450m Series The Radio Recovery Console mode supports:

Restoring factory default IP address 169.254.1.1 and password Boot with factory default Canopy system software settings Load previously installed SW images See Radio Recovery Console PMP/PTP 450i/450b and PMP 450m on page 9-36. Default Mode (or Default Plug) 450 Series A default plug is available to provide access to a module whose password and/or IP address have been forgotten. This plug allows the 450 Series ODUs to be accessed using IP address 169.254.1.1 and no password. During the override session, you can assign any new IP address and set either or both user passwords

(display-only and/or full access) as well as make other parameter changes. See Default Mode (or Default/Override Plug) - PMP/PTP 450 on page 9-39. Page 1-26 Chapter 2: System hardware This chapter describes the hardware components of a 450 Platform link. The following topics are described in this chapter:

System Components on page 2-2 describes system components of PTP and PMP including its accessories Cabling on page 2-33 describes about various cables. Lightning protection unit (LPU) and grounding kit on page 2-41 describes about lightning protection and grounding kit Antennas and antenna cabling on page 2-43 describes supported antennas and its accessories GPS synchronization on page 2-45 describes UGPS and CMM4. Ordering the components on page 2-60 specifies Cambium part numbers for 450 Platform Family components Page 2-1 Chapter 2: System hardware System Components System Components Point-to-Multipoint (PMP) The PMP radio is a transceiver device. It is a connectorized or radiated outdoor unit containing all the radio, networking, and surge suppression electronics. It can be purchased as:

Access Point Module (AP) Subscriber Module (SM) PMP 450 Platform Family Integrated or Connectorized ODU The PMP 450i Series and PMP 450 Series ODUs are supplied in Integrated or Connectorized configurations. The PMP 450m Series AP is supplied in Integrated configuration only. See Table 2 PMP 450m Series hardware configurations on page 1-3 See Table 4 PMP/PTP 450i Series hardware configurations on page 1-5 See Table 6 PMP 450b Series hardware configurations on page 1-8 See Table 8 PMP/PTP 450 Series hardware configurations on page 1-11 Product variants Table 12 PMP 450m Series variants Variant Region Antenna Frequency Range Channel Bandwidth Max EIRP FCC RoW EU DES only IC 5 GHz PMP 450m AP 90 integrated sector array, 14x14 MIMO system, 5150 5925 MHz 5, 10, 15, 20, 40 MHz 42 dBm Page 2-2 Chapter 2: System hardware Table 13 PMP 450i Series variants Variant Region Antenna Frequency Range System Components Channel Bandwidth 5, 7, 10, 15, 20 MHz Max Tx Power 25 dBm 900 MHz PMP 450i AP 3 GHz PMP 450i AP 5 GHz PMP 450i AP FCC Connectorized 902 - 928 MHz FCC, RoW, Canada, RoW DES, Europe FCC, RoW, Canada, RoW DES, Europe Connectorized Integrated 16 dBi Connectorized Integrated 16 dBi 90 degree 3300 3900 MHz 5, 7, 10, 15, 20, 30, 40 MHz 25 dBm 4900 5925 MHz 5, 10, 15, 20, 30, 40 MHz 27 dBm Table 14 PMP 450b Series variants Variant Region Antenna Frequency Range Channel Bandwidth Max Tx Power 5 GHz PMP 450b SM FCC, RoW, Canada, RoW DES, Europe Integrated 16 dBi 4900 5925 MHz 5, 10, 15, 20, 30, 40 MHz 27 dBm Note The Transmit power is limited based on regional setting. Page 2-3 Chapter 2: System hardware Table 15 PMP 450 Series variants Variant Region Antenna Frequency Range FCC Connectorized 902 - 928 MHz 900 MHz PMP 450 SM 2.4 GHz PMP 450 AP 2.4 GHz PMP 450 SM 3.5 GHz PMP 450 AP FCC ISM FCC ISM FCC ISM 3.5 GHz PMP 450 SM FCC ISM 3.65 GHz PMP 450 AP FCC ISM System Components Channel Bandwidth 5, 7, 10, 15, 20 MHz Max Tx Power 25 dBm 22 dBm 22 dBm 2400 2483.5 MHz 5, 10, 15, 20 MHz 2400 2483.5 MHz 5, 10, 15, 20 MHz 3300 3600 MHz 5, 7, 10, 15, 20, 30, 40 MHz 25 dBm 3300 3600 MHz 5, 7, 10, 15, 20, 30, 40 MHz 25 dBm 3500 3850 MHz 5, 7, 10, 15, 20, 30, 40 MHz 25 dBm 3500 3850 MHz 5, 7, 10, 15, 20, 30, 40 MHz 25 dBm 5470 5875 MHz 5470 5875 MHz 10, 20 MHz (5, 15 and 30 MHz not available in DFS regions) 10, 20 MHz (5, 15 and 30 MHz not available in DFS regions) 22 dBm 22 dBm Connectorized Integrated 18 dBi Connectorized Integrated 7 dBi Connectorized Integrated 16 dBi Connectorized Integrated 8 dBi Integrated 19 dBi Connectorized Integrated 16 dBi Connectorized Integrated 19 dBi Connectorized Integrated 17 dBi Connectorized Integrated 9 dBi Integrated 25 dBi 3.65 GHz PMP 450 SM FCC ISM Integrated 8 dBi 5.4/5.8 GHz PMP 450 AP FCC, RoW, RoW DES 5.4/5.8 GHz PMP 450 SM FCC, ROW, RoW DES Note The Transmit power is limited based on regional setting. Page 2-4 Chapter 2: System hardware System Components Backhaul (PTP) The Backhaul radio is a transceiver device. It is a connectorized or integrated outdoor unit containing all the radio, networking, and surge suppression electronics. It can be configured as:

Backhaul Master (BHM) Backhaul Slave (BHS) PTP 450 Platform Family Integrated or Connectorized ODU See Table 4 PMP/PTP 450i Series hardware configurations on page 1-5 See Table 8 PMP/PTP 450 Series hardware configurations on page 1-11 Product variants Table 16 PTP 450i Series variants Variant Region Antenna Frequency Range Connectorized Integrated 23 dBi 3300 - 3900 MHz Channel Bandwid th 5, 7, 10, 15, 20, 30, 40 MHz Max Tx Power Notes 25 dBm Transmit power limited based on regional setting Connectorized Integrated 23 dBi 4900 5925 MHz 5, 10, 15, 20, 30, 40 MHz 27 dBm Transmit power limited based on regional setting 3 GHz PTP 450i 5 GHz PTP 450i FCC, RoW, Canada, Row DES, Europe FCC, RoW, Canada, Row DES, Europe Page 2-5 Chapter 2: System hardware Table 17 PTP 450 Series variants Variant Region Antenna 900 MHz PTP 450 BH 3.5 GHz PTP 450 BH 3.65 GHz PTP 450 BH FCC Connectorized Connectorized ROW Integrated 16 dBi Integrated 19 dBi Connectorized ROW Integrated 16 dBi 5.4/5.8 GHz PTP 450 BH FCC, RoW, RoW DES Integrated 19 dBi Connectorized Integrated 9 dBi Integrated 25 dBi System Components Frequency Range 902 928 MHz 3300 3600 MHz 3500 3850 MHz Channel Bandwidth 5, 7, 10, 15, 20 MHz 5, 7, 10, 15, 20, 30, 40 MHz 5, 7, 10, 15, 20, 30, 40 MHz Max Tx Power 25 dBm 25 dBm 25 dBm 5470 5875 MHz 5, 10, 15, 20, 30, 40 MHz 22 dBm Note The Transmit power is limited based on regional setting. Page 2-6 System Components Chapter 2: System hardware 450 Platform Family interfaces PMP 450m Series interfaces AP The 450m Series AP interfaces is illustrated below. Figure 5 PMP 450m Series interfaces Carabiner clip Ground Lugs SFP AUX PSU/Ethernet Table 18 PMP 450m Series AP interface descriptions and cabling Interface PSU/Ethernet Aux/Sync SFP Ground Lugs Function Power-over-Ethernet, Ethernet communications (management and data), CMM5 sync-over-power synchronization input GPS synchronization input and output, UGPS power output Audio tones Data Read Ethernet communications (management and data) For grounding the unit Cabling RJ45 Cable See Table 94 on page 5-11 RJ 45 Cable See Table 95 on page 5-11 10 AWG copper wire Page 2-7 Chapter 2: System hardware System Components Note For PMP 450m AP, the Sync-Over-Power is supported with CMM5 only. For PMP 450m AP, the Sync-Over-Power will not work with CMM4 like PMP 450/450i Series. Note SFP kits (part numbers C000065L008A and C000065L009A) are required for SFP port connectivity. SFP port is not supported in system release 15.0/15.0.0.1. PMP/PTP 450i Series interfaces AP/SM/BH The AP/SM/BH interfaces are illustrated below. Figure 5 PMP/PTP 450i interfaces Carabiner clip Ground Lug RF port A RF port B Aux Gland ENET Page 2-8 Chapter 2: System hardware Table 19 PMP/PTP 450i Series - AP/SM/BH interface descriptions and cabling System Components Interface PSU/Ethernet Aux/Sync Function Power-over-Ethernet, Ethernet communications (management and data), CMM sync-over-power synchronization input GPS synchronization input and output, UGPS power output Audio tones Data Cabling RJ45 Cable See Table 94 on page 5-11 RJ 45 Cable See Table 95 on page 5-11 RF Port A RF Port B Vertical RF connection to antenna 50 ohm RF cable, N-type Horizontal RF connection to antenna 50 ohm RF cable, N-type Ground Lugs For grounding the unit 10 AWG copper wire Note If the Aux port will be used, a second Ethernet Gland will need to be ordered (Part Number:

N000065L033A). PMP 450b Series interfaces - SM The PMP 450b Series - SM interfaces are illustrated below. Figure 3 PMP 450b Series - SM interfaces PSU/Ethernet Port Audio AUX Port Page 2-9 Chapter 2: System hardware System Components Table 20 PMP 450b Series - SM interface descriptions and cabling Interface PSU/Ethernet Function Power-over-Ethernet, Ethernet communications (management and data) Cabling RJ45 Cable Audio AUX Port 3.5 mm audio jack for alignment tone Standard 3.5 mm TRRS headphones PMP/PTP 450 Series interfaces - AP The PMP 450 Series - AP interfaces are illustrated below. Figure 4 PMP/PTP 450 Series - AP interfaces RF Port A Sync/Default Ethernet RF port B Page 2-10 Chapter 2: System hardware System Components Table 21 PMP/PTP 450 Series - AP interface descriptions and cabling 2.4 GHz and 5 GHz Interface PSU/Ethernet Sync/Default 2.4 GHz 5 GHz RF Port A RF Port B Function Power-over-Ethernet, Ethernet communications (management and data) Cabling RJ45 Cable GPS synchronization signaling, provides power to UGPS module. Default plug port.

-45 degree RF connection to AP antenna 50 ohm RF cable, N-

Vertical RF connection to AP antenna RJ11 cable, default plug. type 2.4 GHz +45 degree RF connection to AP antenna 5 GHz Horizontal RF connection to AP antenna 50 ohm RF cable, N-

type Ground Lugs For grounding the unit 10 AWG copper wire PMP/PTP 450 Series interfaces SM/BH The PMP 450 Series SM/BH interfaces are illustrated below. Figure 5 PMP/PTP 450 Series SM/BH interfaces Ethernet Sync/Default Page 2-11 Chapter 2: System hardware Figure 6 PMP/PTP 450 Series SM/BH Connectorized interfaces System Components External antenna cable path A

(labeled A) External antenna cable path B (labeled B) Ground (connectorized models) Note As per Underwriters Laboratory (UL) guidelines, the Ground Lug on the radiated SM is not required. Page 2-12 Chapter 2: System hardware Figure 7 PMP 450d Series - SM Integrated Dish System Components Figure 8 PMP 450 Series SM 3 GHz Integrated Figure 9 PTP 450 Series BHM/BHS Page 2-13 Chapter 2: System hardware System Components ATEX/HAZLOC variants PTP/PMP 450i series products are available in ATEX/Hazloc variants for operation in locations where explosive gas hazards exist, as defined by Hazloc (USA) and ATEX (Europe). ATEX/HAZLOC variants are similar to the standard product except that:

ODUs are supplied with the Full capacity license The frequency range is restricted to 4940 MHz to 5850 MHz The maximum EIRP generated by ODU is restricted to comply with the ATEX and HAZLOC standards In order to meet specific radio regulations in the USA, Canada and the EU, Cambium supplies products approved for USA, Canada, EU and the rest of the world under different models and part numbers. These models and part numbers are shown in Table 62 and Table 63. Page 2-14 Chapter 2: System hardware Diagnostic LEDs The diagnostic LEDs of 450 Platform Family ODUs are as shown below. System Components Note The colors shown in the diagram may differ from the actual color displayed by the AP/BHM, depending on its current status. AP/BHM LEDs The diagnostic LEDs report the information about the status of the AP/BHM. Figure 10 AP/BHM diagnostic LEDs, viewed from unit front ODU LED Display LED Labels PMP 450m Series - AP MAIN LNK+ACT/5 AUX LNK+ACT/4 GPS/3 PMP/PTP 450i Series - AP/BHM SES/2 SYN/1 PWR MAIN LNK/5 ACT/4 GPS/3 SES/2 SYN/1 PWR PMP/PTP 450 Series - AP/BHM MAIN LNK/5 ACT/4 GPS/3 SES/2 SYN/1 PWR Page 2-15 Chapter 2: System hardware Table 22 AP/BHM LED descriptions LED Color when active PWR Red SYN/1 Yellow SES/2 Green Status information provided DC power Presence of sync Unused GPS/3 Red Pulse of sync ACT/4 For 450 and 450i Series Yellow Presence of data activity on the Ethernet link AUX LNK +

ACT/4 For 450m Series Red/ Green

(bi-colored for 10/100) Aux port link speed and activity MAIN LNK/5 For 450i Series Red/ Green/Orange

(bi-colored for 10/100/1000) For 450 AP Orange/Green/Yellow

(10/100/1000) For 450 BHM Green Activity on Main port link Ethernet link MAIN LNK +

ACT/5 For 450m Series Red/ Green/Orange

(bi-colored for 10/100/1000) Main port link speed and activity Page 2-16 System Components Notes Always lit after 10-20 seconds of power on.

-

-

Lit when the AP/BHM is getting a sync pulse from a GPS source goes along with SYN/1 Flashes during data transfer. Frequency of flash is not a diagnostic indication. Flashes to indicate Ethernet activity on Aux port. Indicates speed based on the following colors:

10Base-T : Red 100Base-T : Green Continuously lit when link is present. Indicates speed based on the following colors:

10Base-T : Red 100Base-T : Green 1000Base-T : Orange Continuously lit when link is present. 10Base-T : Orange 100Base-T : Green 1000Base-T : Yellow Continuously lit when link is present. 10Base-T : Green 100Base-T : Green Flashes to indicate data transfer speed and activity. Chapter 2: System hardware System Components SM/BHS LEDs The SM/BHS LEDs provide different status of radio based on the operating modes. A SM/BHS in operating mode registers and passes traffic normally. A SM/BHS in aiming mode does not register or pass the traffic, but displays (via LED panel) the strength of received radio signals (based on radio channel selected via Tools -> Alignment). Figure 11 AP/BH diagnostic LEDs, viewed from unit front ODU LED Display LED Labels PMP/PTP 450i Series - SM/BHS MAIN LNK/5 ACT/4 GPS/3 SES/2 SYN/1 PWR PMP 450b Series - SM LNK/SPD/

ACT/4 GPS/3 SES/2 SYN/1 STDBY/

PWR PMP/PTP 450 Series - SM/BHS MAIN LNK/5 ACT/4 GPS/3 SES/2 SYN/1 PWR Page 2-17 Chapter 2: System hardware Table 23 SM/BHS LED descriptions System Components LED Color when active Status information provided SM / BHS in Operating Mode SM / BHS in Aiming Mode Notes PWR Red STDBY/

PWR Yellow/Blue DC power DC power SYN/1 Yellow Presence of sync SES/2 Green Session Indicator GPS/3 Red Unused ACT/4 Yellow Presence of data activity on the Ethernet link These three LEDs act as a bar graph to indicate the relative quality of alignment. As power level improves during alignment, more of these LEDs are lit. Presence of data activity on the Ethernet link For 450b Series Red/Green/Oran ge

(10/100/1000) For 450i Series Red/ Green/

Orange

(bi-colored for 10/100/1000) For 450 Series Green LNK/SP D/ACT/4 MAIN LNK/5 Ethernet Link Ethernet Link Ethernet link Ethernet link Ethernet link Ethernet link Always lit after 10-20 seconds of power on. Flashes Yellow during boot-up. Flashes Blue when operating. Lit when SM/BHS is in sync with an AP/BHM. Lit when SM/BHS is in session. Unused Flashes during data transfer. Frequency of flash is not a diagnostic indication. Flashes during data transfer. Frequency of flash is not a diagnostic indication. 10Base-T : Red 100Base-T : Green 1000Base-T : Orange Flashes during data transfer. 10Base-T : Red 100Base-T : Green 1000Base-T : Orange Continuously lit when link is present. Page 2-18 Chapter 2: System hardware System Components Operating Mode Scanning: If the SM/BHS is not registered to AP/BHM, then these three LEDs cycle on and off from left to right (SYN/1, SES/2 and GPS/3). Ethernet Link:

o For 450m AP, the MAIN LNK + ACT/5 LED is active when the Main port link is present and the AUX LNK + ACT/4 LED is active when the Aux port link is present. o For 450/450i AP/BHM, the MAIN LNK/5 LED is lit continuously when the link is present. o For 450/450i SM/BHS, the MAIN LNK/5 LED is lit continuously when the link is present. Data Transfer:

o For 450m AP, the MAIN LNK + ACT/5 LED flashes to indicate data transfer speed and activity on the Main port and the AUX LNK + ACT/4 LED flashes to indicate data transfer speed and activity on the Aux port. o For 450/450i AP/BHM, the ACT/4 LED flashes during data transfer. o For 450/450i SM/BHS, the ACT/4 LED flashes during data transfer. o For 450b SM, the LNK/SPD/ACT/4 LED flashes during data transfer. Aiming Mode The 3 LEDs (SYN/1, SES/2, and GPS/3) are turned into a 3-position bar graph. The more LEDs that are lit, the better the received power the module is seeing. The colors of the LEDS have no particular meaning other than to assist is distinguishing one position from the next. Power supply options The 450 Platform Family ODUs are powered over its Main Ethernet cable using Power Over Ethernet

(POE). The power injector is connected to the ODU and network terminating equipment using Cat5e cable with RJ45 connectors. Power supply PMP 450m Series The PMP 450m Series - AP supports powering from AC+DC Enhanced Power Injector (see AC+DC Enhanced Power Injector on page 2-22) PSU part numbers Table 24 PSU part numbers for PMP 450m AP Cambium description AC+DC Enhanced Power Injector Cambium part number C000065L002C Page 2-19 Chapter 2: System hardware System Components Power supply PMP/PTP 450i Series The PMP/PTP 450i Series supports powering from the following powering sources:

Power Supply, 60 W, 56 V with 1000BASE-T or GigE AC+DC Enhanced Power Injector Power over Ethernet midspan, 60 W, -48 VDC Input CMM4 with external 56 V power supply and CMM4 to 450i Series ODU cable (Dongle) IEEE802.3at power injector Note The 900 MHz SM is based off of the 450 Series , please see Power supply PMP/PTP 450 Series on page 2-26. Warning Always use an appropriately rated and approved AC supply cord-set in accordance with the regulations of the country of use. Warning The PMP 450 Ruggedized High Gain Integrated Subscriber Module (Cambium part numbers C035045C014A and C036045C014A), while encapsulated in a 450i-

type enclosure, contains 450 circuitry which must be powered via 30 VDC. Powering these SMs with a 56 VDC will damage the device. Please refer to Cabling on Page 2-33 for details on maximum cable lengths between power injector and PMP/PTP 450i. PSU part numbers Table 25 PSU part numbers for PMP/PTP 450i Series Cambium description Power supply, 60 W, 56 V with Gbps support AC+DC Enhanced Power Injector Line Cord, Fig 8 US Line Cord, Fig 8 UK Line Cord, Fig 8 EU Power over Ethernet midspan, 60 W, -48 VDC Input Power supply, 30 W, 56 V Gbps support Cambium part number N000065L001B C000065L002C N000065L003A N000065L004A N000065L005A N000000L036A N000000L034A Page 2-20 Chapter 2: System hardware System Components AC Power Injector N000065L001B The AC Power Injector interfaces are shown in Figure 12 and described in Table 26. Figure 12 AC Power Injector interfaces Table 26 AC Power Injector interface functions Interface AC power in ODU Function AC power input (main supply) RJ45 socket for connecting Cat5e cable to ODU LAN Power (green) LED RJ45 socket for connecting Cat5e cable to network Power supply detection Page 2-21 Chapter 2: System hardware System Components AC+DC Enhanced Power Injector C000065L002C The AC+DC Enhanced Power Injector interfaces are shown in Figure 13 and described in Table 27. Figure 13 AC+DC Enhanced Power Injector interfaces Page 2-22 Chapter 2: System hardware System Components Table 27 AC+DC Enhanced Power Injector interface functions Interface 100-240V 47-63Hz 1.7A DC In DC Out ODU Function AC power input (main supply) Alternative DC power supply input DC power output to a second PSU (for power supply redundancy) or to a NIDU RJ45 socket for connecting Cat5e cable to ODU LAN Power - AC (green) LED Power - DC (green) LED RJ45 socket for connecting Cat5e cable to network Indicates power is applied at the AC power input Indicates power is applied at the DC In port Ethernet (yellow) LED Detects Ethernet traffic and it is used with PTP650 and PTP700 families only. It does not operate with the 450 platform products. Note The earlier power injector models only had a single power LED that combined the AC+DC indications. Page 2-23 Chapter 2: System hardware System Components

-48 VDC Power Injector N000000L036A The DC Power Injector interfaces are shown in Figure 14 and described in Table 28. Figure 14 -48 V DC Power Injector interfaces Table 28 -48V DC Power Injector interfaces Function 36 to 60V, 2A Two (Data In and Data & Power Out) Interface DC input RJ 45 Sockets LEDs Two (AC and Port) Page 2-24 Chapter 2: System hardware System Components Power supply PMP 450b Series The PMP 450b Series support powering from the following powering sources:

Gigabit Enet Capable Power Supply 20 to 32 V DC, 15W CMM4 with external 29 V power supply Figure 15 -20 to 32 VDC Power Injector interfaces Table 29 -Power Injector interfaces Interface PSU/Ethernet Function 20 to 32 VDC, 2A PSU part numbers Table 30 PSU part numbers for PMP 450b SM Cambium description Gigabit Enet Capable Power Supply - 20 - 32VDC, 15W Cambium part number N000900L001C Page 2-25 Chapter 2: System hardware System Components Power supply PMP/PTP 450 Series The PMP/PTP 450 Series support powering from the following powering sources:

Gigabit Enet Capable Power Supply 30 VDC, 15W CMM4 with external 29 V power supply Warning The PMP 450 Ruggedized High Gain Integrated Subscriber Module (Cambium part numbers C035045C014A and C036045C014A), while encapsulated in a 450i-type enclosure, contains 450 circuitry which must be powered via 30VDC. Powering these SMs with a 56 VDC will damage the device. PSU part numbers Table 31 PSU part numbers for PMP/PTP 450 Series Cambium description Gigabit Enet Capable Power Supply - 30VDC, 15W Cable, UL Power Supply Cord Set, US Cable, UL Power Supply Cord Set, EU Cable, UL Power Supply Cord Set, UK Cable, UL Power Supply Cord Set, Brazil Cambium part number N000900L001C N000900L007A N000900L008A N000900L009A N000900L010A Gigabit Enet Capable Power Supply The Gigabit Enet Capable power supply interfaces are described in Table 32. This power supply requires procurement of an AC line cord that connects the outlet of the same (using IEC-60320 Type 5 connector). A list of available power supply cord options from Cambium Networks are given in Table 31. Table 32 Gigabit Enet Capable power supply Interface AC Input DC Output Function 90-264 VAC, 0.5A rms @120VAC/ 0.25A rms @240VAC, 47 to 63 Hz 30.0 Vdc +/-5%, 15W, 500 mA max RJ 45 Sockets Two (Data In and Data & Power Out) LEDs Green, :LED Intensity determined by Level 5 efficiency Page 2-26 Chapter 2: System hardware Figure 16 Gigabit Enet Capable power supply System Components Page 2-27 Chapter 2: System hardware System Components ODU mounting brackets & accessories The list of supported brackets is provided in Table 33. The "Tilt bracket assembly" is the recommended bracket for the AP, SM or BH integrated units. The "Mounting Bracket (Connectorized)" can be used where a low profile and ease of assembly of Connectorized AP, SM or BH is required. The "Mounting Bracket (Integrated)" provide a wider range of adjustment for AP, SM and BH integrated devices. Table 33 Accessories part numbers Cambium description Mounting brackets Tilt Bracket Assembly Mounting Bracket (Integrated) Mounting Bracket (Connectorized) Miscellaneous Ethernet cable adapter for CMM4 (Dongle) RJ-45 Gland Spare PG16 style (QTY 10) Blanking Plug Pack (Qty 10) Cambium part number N000045L002A N000065L031A N000065L032A N000045L001A N000065L033A N000065L036A Lightning protection The 450 Platform Family supports the lightning protection units listed in Table 34. The LPU offers the highest level of protection and is the recommended device. Where low cost deployment is essential, for example for SM in residential application, the Gigabit Surge Suppressor may be used instead. Table 34 Lightning protection part numbers Cambium description 450 Series (Including 450b and 450d) Surge Suppressor (30 VDC) 450i and 450m Series LPU and Grounding Kit (1 kit per ODU) Gigabit Surge Suppressor (56 VDC) Cambium part number 600SSH C000065L007A C000000L033A Page 2-28 ODU interfaces Chapter 2: System hardware ODU interfaces PMP 450m Series AP These interfaces are described in Table 36. Figure 17 PMP 450m Series - AP rear interfaces Ground Lug LED SFP Aux PSU (Main) Ground Lug Table 35 PMP 450m Series AP rear interfaces Port name PSU (Main) Connector RJ45 Aux RJ45 Interface PoE input 10/100/1000 BaseT Ethernet Data 10/100 BaseT Ethernet Data Description Power over Ethernet (PoE). PoE output Sync input/output SFP RJ45 Ground Lugs 1000 BaseX Ethernet (LX or SX) 10 AWG copper wire Standard IEEE802.3at PoE. Connection and powering of UGPS Sync input Data For grounding the unit Page 2-29 Chapter 2: System hardware ODU interfaces PMP/PTP 450i The Ethernet and Sync/AUX ports are on the rear of the integrated and connectorized ODUs (Figure 18). These interfaces are described in Table 36. Figure 18 PMP/PTP 450i Series - ODU rear interfaces LED Ground Lug Ground Lug Aux Main RF port B RF port A Table 36 PMP/PTP 450i Series ODU rear interfaces Port name Main PSU Connector RJ45 Interface PoE input Description Power over Ethernet (PoE). Sync/AUX RJ45 10/100/1000BASE-T Ethernet Data 10/100/100BASE-T Ethernet Data (see Note below) PoE output Sync input/output Standard IEEE802.3at PoE. Connection and powering of UGPS Sync input The front of the connectorized ODU (Figure 19 PMP/PTP 450i Series Connectorized ODU antenna interfaces) provides N type female connectors for RF cable interfaces to antennas with ports A and B for vertical and horizontal polarization respectively. Page 2-30 Chapter 2: System hardware Figure 19 PMP/PTP 450i Series Connectorized ODU antenna interfaces ODU interfaces Page 2-31 Chapter 2: System hardware ODU interfaces PMP 450b The Ethernet and AUX ports are on the rear of the integrated and connectorized ODUs (Figure 20). These interfaces are described in Table 37. Figure 20 PMP 450b Series - ODU rear interfaces Table 37 PMP 450b Series ODU rear interfaces Port name PSU/Ethernet Port Audio AUX Port Connector RJ45 Interface PoE input Description Power over Ethernet (PoE). 10/100/1000BASE-T Ethernet Data Alignment tone input 3.5 mm audio jack for alignment tone Standard 3.5 mm headphones Page 2-32 Chapter 2: System hardware Cabling Cabling Ethernet standards and cable lengths All configurations require a copper Ethernet connection from the ODU (Main PSU port) to the Power supply. Table 38 specifies, for each type of PSU and configuration, the maximum permitted PSU drop cable length. Table 38 PSU drop cable length restrictions System configuration Power supply Maximum cable length (m/ft) PoE powered device on AUX/SYNC port From power supply to ODU From ODU to PoE device on AUX/SYNC port Power supply (30W) None 100 m IEEE 802.3at Type 2 Not supported AC Power Injector (60W) None 100 m N/A N/A IEEE 802.3at Type 2 100 m in total AC+DC enhanced Power Injector None 100 m N/A IEEE 802.3at Type 2 100 m in total

-48 V DC power injector None 100 m N/A IEEE 802.3at Type 2 100 m in total CMM4 with 56 V supply None 100 m N/A IEEE 802.3at Type 2 Not supported IEEE802.3at compliant supply None 100 m N/A IEEE 802.3at Type 2 Not supported Note The Ethernet connectivity for CMM4 requires the part Ethernet cable adapter for CMM4 N000045L001A. Page 2-33 Chapter 2: System hardware Cabling Outdoor copper Cat5e Ethernet cable Outdoor Cat5e cable is used for all connections that terminate outside the building. For example, connections between the ODU, surge suppressors (if installed), UGPS receivers (if installed) and the power supply injector. This is known as a drop cable (Figure 21). The following practices are essential to the reliability and longevity of cabled connections:

Use only shielded cables and connectors to resist interference and corrosion. For vertical runs, provide cable support and strain relief. Include a 2 ft (0.6 m) service loop on each end of the cable to allow for thermal expansion and contraction and to facilitate terminating the cable again when needed. Include a drip loop to shed water so that most of the water does not reach the connector at the device. Properly crimp all connectors. Use dielectric grease on all connectors to resist corrosion. Order Superior Essex type BBDGe cable from Cambium Networks (Table 39). Other lengths of this cable are available from Superior Essex. Figure 21 Outdoor drop cable Table 39 Drop cable part numbers Cambium description 1000 ft Reel Outdoor Copper Clad CAT5E Cambium part number WB3175 328 ft (100 m) Reel Outdoor Copper Clad CAT5E WB3176 Page 2-34 Chapter 2: System hardware Cabling SFP module kits SFP module kits allow connection of a PMP 450 Series ODU to a network over an Optical Gigabit Ethernet interface (1000BASE-LX or 1000BASE-SX) full-duplex mode. Note PMP 450m supports Fiber SFPs from system release 15.0.3. Order SFP module kits from Cambium Networks (Table 40). Table 40 SFP module kit part numbers Cambium description Single Mode Optical SFP Interface per ODU Cambium part number C000065L008 Multi-mode Optical SFP Interface per ODU C000065L009 To compare the capabilities of the two optical SFP modules, refer to Table 41 and Table 42. Table 41 Single Mode Optical SFP Interface per ODU (part number C000065L008) Core/

cladding

(microns) 62.5/125 50/125 50/125 10/125 Mode Multi Multi Multi Single Bandwidth at 1310 nm (MHz/km) 500 400 500 N/A Maximum length of optical interface 550 m (1800 ft) 550 m (1800 ft) 550 m (1800 ft) 5000 m (16400 ft) Table 42 Multi-mode Optical SFP Interface per ODU (part number C000065L009) Core/

cladding

(microns) 62.5/125 62.5/125 50/125 50/125 Mode Multi Multi Multi Multi Bandwidth at 850 nm (MHz/km) 160 200 400 500 Maximum length of optical interface 220 m (720 ft) 275 m (900 ft) 500 m (1640 ft) 550 m (1800 ft) The upgrade kits contain the following components:

Optical SFP transceiver module (Figure 22) Insertion loss

(dB) 1.67 0.07 1.19 0.16 Insertion loss

(dB) 2.38 2.6 3.37 3.56 Page 2-35 Chapter 2: System hardware Long EMC strain relief cable gland (Figure 23) The Ethernet SFP Module Installation Guide License key instructions and an entitlement key Figure 22 Optical SFP transceiver module Cabling Figure 23 Long cable gland Page 2-36 Cabling Chapter 2: System hardware Main Ethernet port The PoE cable pinout diagram for Main port is given below. Table 43 Main port PoE cable pinout RJ45 pin Interface 1 2 3 6 4 5 7 8 1000 BaseT Ethernet with PoE In Ethernet description

+TxRx0 TxRx0

+TxRx1 TxRx1

+TxRx2 TxRx2

+TxRx3 TxRx3 PoE input description

+Ve or -Ve

+Ve or Ve

+Ve or Ve

+Ve or Ve Note The PoE input on the Main port accepts any polarity. Aux port Table 44 Aux port PoE cable pinout RJ45 pin Interface Signal description PoE output description 1 2 3 6 4 5 7 8 100 BaseT Ethernet with PoE Out (see note below) GPS and alignment tone

+TxRx0 TxRx0

+TxRx1 TxRx1 GPS power out, Alignment tone out, GPS data out GPS data in GPS 0v GPS Sync in

-Ve

+Ve N/A Page 2-37 Chapter 2: System hardware Cabling Note PMP 450m Series - AP Aux port supports only alignment and sync functionalities in current 15.0/15.0.3 release. Note If the Aux port will be used, a second Ethernet gland will need to be ordered (Part Number:

N000065L033A). Aux port to alignment tone headset wiring A standard 32 ohms stereo headset can be connected to the AUX port to use the audio alignment tool. The diagrams of the adapters for RJ45 and RJ12 are provided in Figure 24 and Figure 25 respectively. The recommended values for both resistors are 220 ohm, 0.25W. Different resistor values can be used to optimize the level of the audio signal depending on the headset characteristics and the level of ambient noise. Figure 24 Alignment Tone Cable

#8 Pin 7 Pin 4 Table 45 Aux port PoE cable pinout RJ45 pin

(AUX port) Signal description 4 7 Alignment tone out GPS 0v Figure 25 RJ12 Alignment Tone Cable Resistors 220 220 Left / tip Right / ring Sleeve /Common Serial component 220 ohms resistor 220 ohm resistor None Jack socket

(to jack plug of headset) Ring Tip Sleeve

#8 Pin 5 Pin 6 Left / tip Right / ring Page 2-38 Chapter 2: System hardware Cabling Table 46 RJ12 Aux port PoE cable pinout RJ12 pin (AUX port) 5 6 Signal description Alignment tone out Alignment tone out Jack socket

(to jack plug of headset) Tip Ring Alternatively, a readymade headset adapter can be ordered from Best-Tronics (http://btpa.com/Cambium-

Products/) with the following part number:

Table 47 Alignment tone adapter third party product details Reference BT-1277 BT-0674 Product description Headset alignment cable (RJ-45) for the PMP/PTP 450i Series products Headset alignment cable (RJ-12) for the PMP/PTP 450 Series products. RJ45 connectors and spare glands RJ45 connectors are required for plugging Cat5e cables into ODUs, LPUs, PSUs and other devices. Order RJ45 connectors and crimp tool from Cambium Networks (Table 48). The ODU is supplied with one environmental sealing gland for the drop cable. This gland is suitable for cable diameters from 5 mm to 9 mm. Figure 26 Cable gland (part number #N000065L033) Table 48 RJ45 connector and spare gland part numbers Cambium description Tyco/AMP, Mod Plug RJ45, 100 pack Tyco/AMP Crimp Tool RJ-45 Spare Grounding Gland - PG16 size (Qty. 10) Cambium part number WB3177 WB3211 N000065L033 Page 2-39 Chapter 2: System hardware Cabling Page 2-40 Chapter 2: System hardware Lightning protection unit (LPU) and grounding kit Lightning protection unit (LPU) and grounding kit 450i and 450m Series LPUs provide transient voltage surge suppression for ODU installations. Each cable requires two LPUs, one near the ODU and the other near the linked device, usually at the building entry point (Table 49). Table 49 LPU and grounding kit contents Lightning protection units (LPUs) LPU grounding point nuts and washers ODU to top LPU drop cable (600 mm) EMC strain relief cable glands U-bolts, nuts and washers for mounting LPUs ODU to top LPU ground cable (M6-M6) Bottom LPU ground cable (M6-M10) ODU to ground cable (M6-M10 Page 2-41 Chapter 2: System hardware Lightning protection unit (LPU) and grounding kit One LPU and grounding kit (Table 49) is required for the PSU drop cable connection to the ODU. If the ODU is to be connected to an auxiliary device, one additional LPU and grounding kit is required for the Aux drop cable. Order the kits from Cambium Networks (Table 50). Table 50 LPU and grounding kit part number Cambium description Aux ports LPU and Grounding Kit (One Kit Per End) Cambium part number C000065L007B Cable grounding kit Copper drop cable shields must be bonded to the grounding system in order to prevent lightning-strike arcing (resulting in fire risk and damage to equipment). One grounding kit (Figure 27) is required for each grounding point on the cable. Order cable grounding kits from Cambium Networks (Table 51). Caution To provide adequate protection, all grounding cables must be a minimum size of 10 mm2 csa (8AWG), preferably 16 mm2 csa (6AWG), or 25 mm2 csa (4AWG). Figure 27 Cable grounding kit Table 51 Cable grounding kit part numbers Cambium description Cable Grounding Kits For 1/4" And 3/8" Cable Cambium part number 01010419001 Page 2-42 Chapter 2: System hardware Antennas and antenna cabling Antennas and antenna cabling Antenna requirements Each connectorized ODU requires one external antenna (normally dual-polar). For connectorized units operating in the USA or Canada 900 MHz, 4.9 GHz, 5.1 GHz, 5.2 GHz, 5.4 GHz or 5.8 GHz bands, choose external antennas which are recommended by Cambium Networks. Do not install any other antennas. Supported external AP antennas The recommended AP external antennas are listed in Table 52. Table 52 List of AP external antennas Cambium description 900 MHz 13 dBi 65 degree Sector Antenna (Dual Slant) 5 GHz Horizontal and Vertical Polarization Antenna for 90 Degree Sector 5 GHz Horizontal and Vertical Polarization Antenna for 60 Degree Sector Cambium part number N009045D001A 85009324001 85009325001 Note LINKPlanner, Cambium Networks, planning tool, contains an up-to-date, exhaustive list of antennas that can be used with Cambium Products. Supported external BH/SM antenna The recommended PTP 450i Series BH or PMP 450/450i Series SM external antenna is listed in Table 53. Table 53 PTP 450i Series BH or PMP 450/450i Series SM external antenna Cambium description 900 MHz 12 dBi gain directional antenna (Dual Slant) Cambium part number N009045D003A Page 2-43 Chapter 2: System hardware Antennas and antenna cabling RF cable and connectors RF cable of generic type LMR-400 is required for connecting the ODU to the antenna. N type male connectors are required for connecting the RF cables to the connectorized ODU. Two connectors are required per ODU. Use weatherproof connectors, preferably ones that are supplied with adhesive lined heat shrink sleeves that are fitted over the interface between the cable and connector. Order CNT-400 RF cable and N type male connectors from Cambium Networks (Table 54). Table 54 RF cable and connector part numbers Cambium description 50 Ohm Braided Coaxial Cable - 75 meter 50 Ohm Braided Coaxial Cable - 500 meter RF Connector, N, Male, Straight for CNT-400 Cable Cambium part number 30010194001 30010195001 09010091001 Antenna accessories Connectorized ODUs require the following additional components:

Cable grounding kits: Order one cable grounding kit for each grounding point on the antenna cables. Refer to Lightning protection unit (LPU) and grounding kit on 2-41 Self-amalgamating and PVC tape: Order these items to weatherproof the RF connectors Lightning arrestors: When the connectorized ODU is mounted indoors, lightning arrestors (not LPUs) are required for protecting the antenna RF cables at building entry. One arrestor is required per antenna cable. One example of a compatible lightning arrestor is the Polyphaser LSXL-ME or LSXL

(not supplied by Cambium Networks). Page 2-44 Chapter 2: System hardware GPS synchronization GPS synchronization GPS synchronization description Cambium offers GPS synchronization to limit the networks own self-interference. The Cluster Management CMM provides Global Positioning System (GPS) synchronization to the Access Point (AP) and all associated Subscriber Modules (SM). Network operators have a choice of UGPS and CMM solutions to select the option that works best for the environment. Universal GPS (UGPS) The UGPS provides network synchronization for smaller networks where a CMM may not be cost effective. The UGPS provides synchronization for one or two modules so that even remote areas at the edge of the network can operate with synchronization for improved performance. The UGPS works with all Cambium PMP radios. The UGPS has a small footprint and is easy to deploy. Figure 28 UGPS Note PMP 450/450i/450m Series - APs can power up a UGPS via the Aux/Timing port. Page 2-45 Chapter 2: System hardware GPS synchronization CMM5 The CMM5 (Cluster Management Module) is the latest generation of solutions for the distribution of TDD Sync signals and Power-over-Ethernet (PoE) in the field. The CMM5 is a modular design with individual 4-port power injectors and an optional controller used for remote management. Key features of the CMM5 include:

Support for Gigabit Ethernet (1000BaseT) Modular and scalable from 4 ports to 32 ports Direct +/- 48VDC input (optional AC/DC power supplies are available from Cambium Networks) Uses Cambium Networks UGPS for a synchronization source Dual resilient power inputs Rack mountable Secure remote management when used with the optional CMM5 Controller Module Support for PMP 450m (cnMedusa) Future support for integration into (cnMedusa) for cloud or NOC-based management It consists of four subsystems, described in the following sections:

CMM5 Controller Module CMM5 Injector (29 volt and 56 volt versions) Power supply(s) (240/600 watt) UGPS Cluster Management: Scenario 1 The following is a CMM5 Cluster Management scenario using four PMP 450i Access Points. Table 55 CMM5 Cluster Management Scenario 1 Scenario Equipment Needed Features Four PMP 450i Access Points 56 Volt Injector Gigabit Ethernet Local Management Interface

+/- 48VDC Input Broad Device Support Rack Mountable UGPS

-

48 VDC Available No management or resilience required Page 2-46 Chapter 2: System hardware Figure 29 Cluster Management: Scenario 1 GPS synchronization Cluster Management: Scenario 2 The following is a CMM5 Cluster Management scenario using four PMP 450i Access Points and four PMP 450 Access Points. Table 56 CMM5 Cluster Management Scenario 2 Scenario Equipment Needed Features Four PMP 450i Access Points Four PMP 450 Access Points 56 Volt Injector 29 Volt Injector 1 CMM5 Controller One UGPS AC only environments Two UGPS AC-to-48 VDC Power Supplies Management required Resilence required.

-

Gigabit Ethernet support Local Management Interface

+/- 48VDC Input Broad Device Support Rack Mountable Resilent power sources Secure, Remote Management

(https) Scalable to 32 devices Page 2-47 Chapter 2: System hardware GPS synchronization Figure 30 Cluster Management: Scenario 2 CMM5 Controller Module The major features of the CMM5 Controller Module are:

Auto-detect/control up to 8 Power Injectors Monitor SYNC/Power/GPS status Manage (up/down ports) Web (HTTPS) and SNMPv2/v3 management (SNMP on roadmap) 1U/ half-width rack-mount Figure 31 Controller Module Page 2-48 GPS synchronization Chapter 2: System hardware CMM5 Injector Module The CMM5 Injector Module has the following features:

Stand-alone mode or used with controller for mgmt.

+/- 48VDC input with green/amber LEDs for status 2U / half-width rack-mount Injects SYNC pulse from UGPS Note There are two different versions of the injector module (56V and 29V). You must select the correct injector for the types of radios that you will be powering. In both cases, the injectors use the same input power supplies or can be powered with +/- 48VDC. The output power is different and the type of SYNC signal used is different between the two types of injectors. Systems can have 29V and 56V injectors deployed alongside each other. Figure 32 Injector Module CMM5 Injector Compatibility Matrix The following table provides the Injector compatibility matrix. Table 57 Injector Compatibility Matrix Product PMP 450m PMP/PTP 450i Power/Injector Module Yes/56V Yes/56V PMP 450b PMP 450/PTP 450 PMP 100/PTP 100 Yes/29V Yes/29V Yes/29V Sync Yes Yes Yes Yes Yes Page 2-49 Chapter 2: System hardware GPS synchronization CMM5 Specifications The following table provides specifications for the CMM5 Power & Sync Injector (56 Volts). Table 58 CMM5 Specifications CMM5 Power and Sync Injector 56 Volts Model Number C000000L556A Data Interface Surge Suppresion Power Cabinet Temperature Physical Dimensions Unit Weight Power Interface Terminals 4 each RJ45 Gigabit Powered output ports To Radios 4 each RJ45 Gigabit Data input ports To Switch Array 1 each GPS timing port (RJ-12) 1 each CMM5 USB Serial port for local administration 1 each RJ12 Daisy Chain port IN 1 each RJ12 Daisy Chain port OUT Lightning Suppression for each To Radios RJ45 Port Input Voltage: + or - 48 VDC Input Power Consumption: 400 watts Output Voltage: + or - 55 VDC Output Current: 0 - 1.8A per channel Output Power: 0 - 90 Watts per channel

-40 C to +55C (-40 F to +131 F), 90%

humidity, condensing Max Distance from Managed Radios: 328 cable feet (100m) Max Distance to GPS Antenna: 100 cable feet

(30.5m) 8.85 W x 15.75 D x 1.65 H (225mm x 400mm x 42mm) 6.6 pounds (3kg) 2 Power input ports for 48 VDC Power (Power supplies sold separately) Page 2-50 Chapter 2: System hardware GPS synchronization CMM4 (Rack Mount) The Cluster Management Module (CMM) is the heart of the Cambium systems synchronization capability, which allows network operators to reuse frequencies and add capacity while ensuring consistency in the quality of service to customers. For operators who prefer indoor CMM mounting, Cambium offers the Rack-Mounted Cluster Management Module 4. The unit is designed to be mounted onto a standard 19-inch telecommunications rack and to allow the Cambium CMM4 to be co-located with other telecommunications equipment. Figure 33 CMM4 (Rack Mount) The CMM4 has two DC power inputs, one 29 V and one 56V. It can be used to power and synchronize both 29 V legacy products such as the PMP 450 Series and 56V products such as the PMP 450i Series simultaneously. If the 29 V legacy products are connected to the CMM4, a 29 V power supply needs to be connected. If the 450i Series is connected to the CMM4, a 56 V power supply needs to be connected. The CMM4 supports having two of the 56 V and two of the 29 V supplies for redundancy. Warning PMP 450i Series requires different wiring between the CMM4 and device. If a PMP450 Series ODU is replaced by a PMP 450i Series and the existing drop cable needs to be re-

used, the Ethernet cable adapter for CMM4 - N000045L001A" must be used between the CMM4 and the existing drop cable. Page 2-51 Chapter 2: System hardware Figure 34 CMM4 56 V power adapter (dongle) GPS synchronization CMM4 56 V power adapter cable pinout Figure 35 CMM4 power adapter cabling diagram J1 1 5 7 8 RJ45 Plug J2 1 5 7 8 Shield RJ45 Jack Page 2-52 GPS synchronization Chapter 2: System hardware Table 59 CMM4 power adapter cable pinout Plug J1 pin 1 2 3 Jack J2 pin 1 2 3 4 5 6 7 8 4 7 6 5 8 Screen Screen Note Pins 5 and 7 are wired in a cross-over configuration. Page 2-53 Chapter 2: System hardware GPS synchronization CMM4 (Cabinet with switch) Designed to deliver consistent and reliable wireless broadband service, the PMP/PTP system gracefully scales to support large deployments. The cluster management module is the heart of the systems synchronization capability which allows network operators to re-use frequencies and add capacity while ensuring consistency in the quality of service to customers. As a result, subscribers can experience carrier-grade service even at the outer edge of the network. Figure 36 CMM4 (Cabinet with switch) CMM4 (Cabinet without switch) This CMM includes all of the functionality listed above but there is no switch. This provides the network operator the flexibility to use the switch of their choice with the power and synchronization capabilities of the CMM4. Page 2-54 Chapter 2: System hardware GPS synchronization CMM3/CMMmicro The CMM3 or CMMmicro (Cluster Management Module micro) provides power, GPS timing, and networking connections for an AP cluster. The CMM3 is configurable through a web interface. The CMM3 contains an 8-port managed switch that supports Power over Ethernet (PoE this is Cambium PoE, not the standard PoE) on each port and connects any combination of APs, BHMs, BHSs, or Ethernet feed. The Cambium fixed wireless broadband IP networks PoE differs from IEEE Standard 803.3af PoE, and the two should not be intermixed. The CMM3 can auto-negotiate speed to match inputs that are either 100Base-TX or 10Base-T, and either full duplex or half duplex, where the connected device is set to auto-negotiate. Alternatively, these parameters are settable. A CMM3 requires only one cable, terminating in an RJ-45 connector, for each connected module to distribute Ethernet signaling. power to as many as 8 co-located modulesAPs, BHMs, or BHSs. Through a browser interface to the managed switch, ports can be powered or not. sync to APs and BHMs. The CMM3 receives 1-pulse per second timing information from Global Positioning System (GPS) satellites through an antenna (included) and passes the timing pulse embedded in the 24-V power to the connected modules. GPS status information is available at the CMM3, however CMM3 provides time and date information to BHMs and APs if both the CMMmicro is operating on CMMmicro Release 2.1 or later and the AP/BHM is operating on System Release 4.2 or later. See Configuring time settings on Page 7-17. CMM3 does not provide time and date information to BHMs and APs if either the CMM3 is operating on a release earlier than CMMmicro Release 2.1 or the AP/BHM is operating on a release earlier than System Release 4.2. A CMM3/CMMicro is shown in Figure 37 and Figure 38. Page 2-55 Chapter 2: System hardware GPS synchronization Figure 37 CMM3 Figure 38 Pole mounted CMM3 Note A CMM3 cannot be used to power up a 450i or 450m Series ODUs. Page 2-56 Chapter 2: System hardware Installing a GPS receiver Installing a GPS receiver To install a GPS receiver as the timing reference source, use the following procedures:

Mounting the GPS receiver on page 2-58 Cabling the GPS Antenna on page 2-59 Installing and connecting the GPS LPU on page 2-59 Caution Prior to power-up of equipment, ensure that all cables are connected to the correct interfaces of the CMM4 unit and the UGPS receiver module. Failure to do so may result in damage to the equipment. GPS receiver location Mount the GPS receiver at a location that meets the following requirements:

It must be possible to protect the installation as described in Grounding and lightning protection on page 3-8. It must have an un-interrupted view of at least half of the southern (resp. northern) sky in the northern

(resp. southern) hemisphere. For a receiver mounted on a wall there must be no other significant obstructions in the view of the sky. It must be mounted at least 1 m (3 ft), preferably 2 m (6 ft), away from other GPS receiving equipment. It must not be sited in the field of radiation of co-located radio communications equipment and should be positioned at a distance of at least 3 m (10 ft) away. Mount the UGPS receiver on the wall of the equipment building if there is a suitable location on the wall that can meet these requirements. Caution The GPS receiver is not approved for operation in locations where gas hazards exist, as defined by HAZLOC (USA) and ATEX (Europe). Mounting the GPS receiver module on the equipment building If mounting the GPS receiver on the equipment building (Figure 43), select a position on the wall that meets the following requirements:

It must be below the roof height of the equipment building or below the height of any roof-mounted equipment (such as air conditioning plant). It must be below the lightning air terminals. Page 2-57 Chapter 2: System hardware Installing a GPS receiver It must not project more than 600mm (24 inches) from the wall of the building. If these requirements cannot all be met, then the module must be mounted on a metal tower or mast. Mounting the GPS receiver module on a metal tower or mast If mounting the GPS receiver module on a metal tower or mast (Figure 44), select a position that meets the following requirements:

It must not be mounted any higher than is necessary to receive an adequate signal from four GPS satellites. It must be protected by a nearby lightning air terminal that projects farther out from the tower than the GPS receiver module. Mounting the GPS receiver Mount the UGPS receiver (following manufacturers instructions) upon either an external wall (Figure 43) or a metal tower or mast (Figure 44). Figure 39 GPS antenna mounting Page 2-58 Chapter 2: System hardware Procedure 1 Mounting the GPS receiver Installing a GPS receiver 1 2 3 4 5 6 7 Ensure that the mounting position has an unobstructed view of the sky to 20 above the horizon. is not the highest object at the site. (The GPS antenna does not need to be particularly high on a site, which would give it more exposure to lightning. It just needs to have an unobstructed view of the sky.) is not further than 100 feet (30.4 meters) of cable from the CMM. Select a pole that has an outside diameter of 1.25 to 1.5 inches (3 to 4 cm) to which the GPS antenna bracket can be mounted. Place the U-bolts (provided) around the pole as shown in Figure 28. Slide the GPS antenna bracket onto the U-bolts. Slide the ring washers (provided) onto the U-bolts. Slide the lock washers (provided) onto the U-bolts. Use the nuts (provided) to securely fasten the bracket to the U-bolts. Please refer to the PMP Synchronization Solutions User Guide located on the Cambium website

(http://www.cambiumnetworks.com/resources/pmp-synchronization-solutions ). Cabling the GPS Antenna Connect the GPS coax cable to the female N-connector on the GPS antenna. Please refer to the PMP Synchronization Solutions User Guide located on the Cambium website

(http://www.cambiumnetworks.com/resources/pmp-synchronization-solutions ). Installing and connecting the GPS LPU Install and ground the GPS drop cable LPU at the building (or cabinet) entry point, as described in Install the bottom LPU on page 6-21. Page 2-59 Chapter 2: System hardware Ordering the components Ordering the components This section describes how to select components for 450m Series, 450i Series and 450 Series Greenfield network or 450m/450i Series network migration. It specifies Cambium part numbers for 450 Platform Family components. Order PMP 450m Series, PMP/PTP 450i Series and PMP/PTP 450 Series ODUs from Cambium Networks. PMP 450m Table 60 PMP 450m Series ODU part numbers Cambium description PMP 450m AP (Access Point) 5 GHz PMP 450m Integrated Access Point, 90 Degree (ROW) 5 GHz PMP 450m Integrated Access Point, 90 Degree (FCC) 5 GHz PMP 450m Integrated Access Point, 90 Degree (EU) 5 GHz PMP 450m Integrated Access Point, 90 Degree (DES Only) 5 GHz PMP 450m Integrated Access Point, 90 Degree (IC) Cambium part number C050045A101A C050045A102A C050045A103A C050045A104A C050045A105A PMP 450i Table 61 PMP 450i Series ODU part numbers Cambium description PMP 450i AP (Access Point) 900 MHz PMP 450i Connectorized Access Point 3 GHz PMP 450i Connectorized Access Point 3 GHz PMP 450i Integrated Access Point, 90 Degree 3 GHz PMP 450i Connectorized Access Point, DES Only 3 GHz PMP 450i Integrated Access Point, 90 Degree, DES Only 5 GHz PMP 450i Connectorized Access Point (RoW) 5 GHz PMP 450i Connectorized Access Point (FCC) 5 GHz PMP 450i Connectorized Access Point (EU) 5 GHz PMP 450i Connectorized Access Point (DES Only) Page 2-60 Cambium part number C009045A001A C030045A001A C030045A002A C030045A003A C030045A004A C050045A001A C050045A002A C050045A003A C050045A004A Chapter 2: System hardware Ordering the components Cambium description 5 GHz PMP 450i Connectorized Access Point (IC) 5 GHz PMP 450i AP, Integrated 90sector antenna (RoW) 5 GHz PMP 450i AP, Integrated 90sector antenna (FCC) 5 GHz PMP 450i Integrated Access Point, 90 degree (EU) 5 GHz PMP 450i AP, Integrated 90sector antenna (DES only) 5 GHz PMP 450i AP, Integrated 90sector antenna (IC) PMP 450i SM (Subscriber Module) 3 GHz PMP 450i Connectorized Subscriber Module 3 GHz PMP 450i SM, Integrated High Gain Antenna 5 GHz PMP 450i Connectorized Subscriber Module 5 GHz PMP 450i SM, Integrated High Gain Antenna Note The 450i SM does not have license keys. Cambium part number C050045A015A C050045A005A C050045A006A C050045A007A C050045A008A C050045A016A C030045C001A C030045C002A C050045C001A C050045C002A Description Table 62 PMP 450i ATEX/HAZLOC ODU models/part numbers ODU model /

part number ODU model 5085CHH 5085HH 5095HH Part Number C050045A009A C050045A010A C050045A011A 450i Connectorized ATEX/HAZLOC 450i Integrated 90 Deg Sector ATEX/HAZLOC 450i Integrated High Gain Directional ATEX/HAZLOC 5 GHz PMP 450i Conn Access Point (ROW), ATEX/HAZLOC 5 GHz PMP 450i Conn Access Point (FCC), ATEX/HAZLOC 5 GHz PMP 450i Conn Access Point (EU), ATEX/HAZLOC C050045A012A C050045A013A 5 GHz PMP 450i Integrated Access Point, 90 degree (ROW), ATEX/HAZLOC 5 GHz PMP 450i Integrated Access Point, 90 degree (FCC), ATEX/HAZLOC C050045A014A 5 GHz PMP 450i Integrated Access Point, 90 degree (EU), ATEX/HAZLOC C050045A017A 5 GHz PMP 450i Conn Access Point (IC), ATEX/HAZLOC Page 2-61 Chapter 2: System hardware Ordering the components C050045A018A 5 GHz PMP 450i Integrated Access Point, 90 degree (IC), ATEX/HAZLOC C050045A019A C050045A020A C050045C003A C050045C004A 5 GHz PMP 450i Conn Access Point (DES Only), ATEX/HAZLOC 5 GHz PMP 450i Integrated Access Point, 90 degree (DES Only), ATEX/HAZLOC 5 GHz PMP 450i Conn Subscriber Module, ATEX/HAZLOC 5 GHz PMP 450i Integrated High Gain Antenna, ATEX/HAZLOC PTP 450i Table 63 PTP 450i Series ODU part numbers Cambium description 3 GHz PTP 450i END, Connectorized 3 GHz PTP 450i END, Integrated High Gain Antenna Cambium part number C030045B001A C030045B002A 3 GHz PTP 450i END, Connectorized (DES only) 3 GHz PTP 450i END, Integrated Access Point, 90 degree (DES only) 5 GHz PTP 450i END, Connectorized (RoW) 5 GHz PTP 450i END, Connectorized (FCC) 5 GHz PTP 450i END, Connectorized (EU) 5 GHz PTP 450i END, Connectorized (DES only) 5 GHz PTP 450i END, Connectorized (IC) 5 GHz PTP 450i END, Integrated High Gain Antenna (RoW) 5 GHz PTP 450i END, Integrated High Gain Antenna (FCC) 5 GHz PTP 450i END, Integrated High Gain Antenna (EU) 5 GHz PTP 450i END, Integrated High Gain Antenna (DES only) 5 GHz PTP 450i END, Integrated High Gain Antenna (IC) Ethernet cable adapter for CMM4 C030045B003A C035045B004A C050045B001A C050045B003A C050045B005A C050045B007A C050045B015A C050045B002A C050045B004A C050045B006A C050045B008A C050045B016A N000045L001A Page 2-62 Chapter 2: System hardware Ordering the components Description Table 64 PTP 450i ATEX/HAZLOC ODU models/part numbers ODU model /

part number ODU model 5085CHH 450i Connectorized ATEX/HAZLOC 5085HH 5095HH 450i Integrated 90 Deg Sector ATEX/HAZLOC 450i Integrated High Gain Directional ATEX/HAZLOC C050045B009A 5 GHz PTP 450i END, Connectorized (ROW), ATEX/HAZLOC C050045B010A C050045B011A 5 GHz PTP 450i END, Integrated High Gain Antenna (ROW), ATEX/HAZLOC 5 GHz PTP 450i END, Connectorized (FCC), ATEX/HAZLOC C050045B012A C050045B013A C050045B014A C050045B017A C050045B018A C050045B019A C050045B020A 5 GHz PTP 450i END, Integrated High Gain Antenna (FCC), ATEX/HAZLOC 5 GHz PTP 450i END, Connectorized (EU), ATEX/HAZLOC 5 GHz PTP 450i END, Integrated High Gain Antenna (EU), ATEX/HAZLOC 5 GHz PTP 450i END, Connectorized (IC), ATEX/HAZLOC 5 GHz PTP 450i END, Integrated High Gain Antenna (IC), ATEX/HAZLOC 5 GHz PTP 450i END, Connectorized (DES Only), ATEX/HAZLOC 5 GHz PTP 450i END, Integrated High Gain Antenna (DES Only), ATEX/HAZLOC PMP 450b Table 65 PMP 450b Series ODU part numbers Cambium description PMP 450b SM (Subscriber Module) 5 GHz 450b Mid Gain WB SM Cambium part number C050045C011A Page 2-63 Chapter 2: System hardware Ordering the components PMP 450 Table 66 PMP 450 Series ODU part numbers Cambium description PMP 450 AP (Access Point) 2.4 GHz PMP 450 Connectorized Access Point 2.4 GHz PMP 450 Connectorized Access Point (DES) 3.5 GHz PMP 450 Connectorized Access Point 3.5 GHz PMP 450 Connectorized Access Point (DES) 3.6 GHz PMP 450 Connectorized Access Point 3.6 GHz PMP 450 Connectorized Access Point (DES) 5 GHz PMP 450 Connectorized Access Point 5 GHz PMP 450 Connectorized Access Point (US only) 5 GHz PMP 450 Connectorized Access Point (DES) PMP 450 AP Lite 2.4 GHz PMP 450 Connectorized Access Point - Lite 3.3-3.6 GHz PMP 450 Connectorized Access Point - Lite 3.55-3.8 GHz PMP 450 Connectorized Access Point - Lite 5 GHz PMP 450 Connectorized Access Point - Lite 5 GHz PMP 450 Connectorized Access Point (FCC) - Lite PMP 450 SM (Subscriber Module) 900 MHz PMP 450 Connectorized Subscriber Module 2.4 GHz PMP 450 Subscriber Module, 4 Mbps 2.4 GHz PMP 450 Subscriber Module, 10 Mbps 2.4 GHz PMP 450 Subscriber Module, 20 Mbps 2.4 GHz PMP 450 Subscriber Module, Uncapped 2.4 GHz PMP 450 Connectorized Subscriber Module, 4 Mbps 2.4 GHz PMP 450 Connectorized Subscriber Module, 10 Mbps 2.4 GHz PMP 450 Connectorized Subscriber Module, 20 Mbps 2.4 GHz PMP 450 Connectorized Subscriber Module, Uncapped 3.5 GHz PMP 450 High Gain Directional Integrated Subscriber 3.5 GHz PMP 450 Subscriber Module, 4 Mbps Page 2-64 Cambium part number C024045A001A C024045A003A C035045A001A C035045A003A C036045A001A C036045A003A C054045A001A C054045A002A C054045A003A C024045A011A C035045A011A C036045A011A C054045A011A C054045A012A C009045C001A C024045C001A C024045C002A C024045C003A C024045C004A C024045C005A C024045C006A C024045C007A C024045C008A C035045C014A C035045C001A Chapter 2: System hardware Cambium description 3.5 GHz PMP 450 Subscriber Module, 10 Mbps 3.5 GHz PMP 450 Subscriber Module, 20 Mbps 3.5 GHz PMP 450 Subscriber Module, Uncapped 3.5 GHz PMP 450 Connectorized Subscriber Module, 4 Mbps 3.5 GHz PMP 450 Connectorized Subscriber Module, 10 Mbps 3.5 GHz PMP 450 Connectorized Subscriber Module, 20 Mbps 3.5 GHz PMP 450 Connectorized Subscriber Module, Uncapped 3.6 GHz PMP 450 High Gain Directional Integrated Subscriber 3.6 GHz PMP 450 Subscriber Module, 4 Mbps 3.6 GHz PMP 450 Subscriber Module, 10 Mbps 3.6 GHz PMP 450 Subscriber Module, 20 Mbps 3.6 GHz PMP 450 Subscriber Module, Uncapped 3.6 GHz PMP 450 Connectorized Subscriber Module, 4 Mbps 3.6 GHz PMP 450 Connectorized Subscriber Module, 10 Mbps 3.6 GHz PMP 450 Connectorized Subscriber Module, 20 Mbps 3.6 GHz PMP 450 Connectorized Subscriber Module, Uncapped 5 GHz PMP 450 Connectorized Subscriber Module, 4 Mbps 5 GHz PMP 450 Connectorized Subscriber Module, 10 Mbps 5 GHz PMP 450 Connectorized Subscriber Module, 20 Mbps 5 GHz PMP 450 Connectorized Subscriber Module, Uncapped 5 GHz PMP 450 Integrated Subscriber Module, 4 Mbps 5 GHz PMP 450 Integrated Subscriber Module, 10 Mbps 5 GHz PMP 450 Integrated Subscriber Module, 20 Mbps 5 GHz PMP 450 Integrated Subscriber Module, Uncapped 5 GHz PMP 450 Connectorized Subscriber Module, 4 Mbps 5 GHz PMP 450 Connectorized Subscriber Module, 10 Mbps 5 GHz PMP 450 Connectorized Subscriber Module, 20 Mbps 5 GHz PMP 450 Connectorized Subscriber Module, Uncapped 5 GHz PMP 450d Subscriber Module, 20 Mbps 4-pack 5 GHz PMP 450d Subscriber Module, Uncapped 4-pack Page 2-65 Ordering the components Cambium part number C035045C002A C035045C003A C035045C004A C035045C005A C035045C006A C035045C007A C035045C008A C036045C014A C036045C001A C036045C002A C036045C003A C036045C004A C036045C005A C036045C006A C036045C007A C036045C008A C054045C005A C054045C006A C054045C007A C054045C008A C054045C001B C054045C002B C054045C003B C054045C004B C054045C005B C054045C006B C054045C007B C054045C008B C054045H013B C054045H014B Chapter 2: System hardware Ordering the components PTP 450 Table 67 PTP 450 Series ODU part numbers Cambium description PTP 450 900 MHz END Connectorized PTP 450 3.5 GHz END Integrated PTP 450 3.5 GHz END Connectorized PTP 450 3.5 GHz END Integrated DES Only PTP 450 3.5 GHz END Connectorized DES Only PTP 450 3.65 GHz END Integrated PTP 450 3.65 GHz END Connectorized PTP 450 3.65 GHz END Integrated DES Only PTP 450 3.65 GHz END Connectorized DES Only PTP 450 5 GHz END Integrated (ROW) PTP 450 5 GHz END Connectorized (ROW) PTP 450 5 GHz END Integrated (ROW) DES Only PTP 450 5 GHz END Connectorized (ROW) DES Only PTP 450 5 GHz END Integrated (FCC) PTP 450 5 GHz END Connectorized (FCC) PMP/PTP 450/450i Series Accessories Table 68 PMP/PTP 450/450I Series Accessories Cambium description PMP 450 AP Antenna Options 900 MHz 65 degree Sector Antenna (Dual Slant) 900 MHz 12 dBi gain directional antenna (Dual Slant) 2.4 GHz Dual Slant Antenna for 60 Degree Sector 3.5 GHz and 3.6 GHz Dual Slant Antenna for 90 Degree Sector 5 GHz Antenna for 60 Degree Sector 5 GHz Antenna for 90 Degree Sector N-type to N-type cable (16 inch length) Page 2-66 Cambium part number C009045B001A C035045B001A C035045B002A C035045B003A C035045B004A C036045B001A C036045B002A C036045B003A C036045B004A C054045B001A C054045B002A C054045B003A C054045B004A C054045B005A C054045B006A Cambium part number N009045D001A N009045D003A C024045D601A C030045D901A 85009325001 85009324001 30009406002 Chapter 2: System hardware Cambium description Power supplies Power supply, 60 W, 56 V with Gbps support AC+DC Enhanced Power Injector Line Cord, Fig 8 US Line Cord, Fig 8 UK Line Cord, Fig 8 EU Power over Ethernet midspan, 60 W, -48 VDC Input Power Supply, 30 W, 56 V Gbps support Gigabit Enet Capable Power Supply - 30VDC, 15W Cable, UL Power Supply Cord Set, US Cable, UL Power Supply Cord Set, EU Cable, UL Power Supply Cord Set, UK AP Optional Equipment CMM MICRO (Outdoor Enclosure) (450 only) CMM5 Controller CMM5 Power and Sync Injector 56V UGPS CMM5 Power Supply, AC, 56V 240W CMM5 Power Supply AC, 48V, 640W CMM5 Spare Controller Cable 1m CMM5 to UGPS Shielded Cable (20 meter) CMM5 Spare DC Power Connector (10 pack) CMM4 W/RUGGEDIZED Switch and GPS CMM4 NO Switch CMM4 Rack Mount Assembly Ethernet cable adapter for CMM4 Universal GPS Module RJ-45 Gland Spare PG16 style (QTY 10) Blanking Plug Pack (Qty 10) SM Optional Equipment Page 2-67 Ordering the components Cambium part number N000065L001B C000065L002C N000065L003A N000065L004A N000065L005A N000000L036A N000000L034A N000900L001A N000900L007A N000900L008A N000900L009A 1070CKHH C000000L500A C000000L556A 1096H N000000L054B N000000L101A N000000L102A N000000L103A N000000L104A 1090CKHH 1091HH 1092HH N000045L001A 1096H N000065L033A N000065L036A Chapter 2: System hardware Cambium description Power Supply, 30 W, 56 V Gbps support Gigabit Enet Capable Power Supply 30 VDC, 15 W Cable, UL Power Supply Cord Set, US Cable, UL Power Supply Cord Set, EU Cable, UL Power Supply Cord Set, UK 53CM Offset, Reflector Dish Kit, 4PK Alignment Tool Headset Accessories Surge Suppressor (30 VDC) Gigabit Surge Suppressor (56 VDC) LPU and Grounding Kit (1 kit per ODU) Single Mode Optical SFP Interface per ODU Multimode Kit 50 Ohm Braided Coaxial Cable - 75 meter 50 Ohm Braided Coaxial Cable - 500 meter RF Connector, N, Male, Straight for CNT-400 Cable Tyco/AMP, Mod Plug RJ45, 100 pack Tyco/AMP Crimp Tool RJ-45 Spare Grounding Gland - PG16 size (Qty. 10) Mounting brackets Tilt Bracket Assembly Mounting Bracket (Integrated) Mounting Bracket (Connectorized) Upgrade Keys PMP 450 4 To 10 Mbps Upgrade Key PMP 450 4 To 20 Mbps Upgrade Key PMP 450 4 To Uncapped Upgrade Key PMP 450 10 To 20 Mbps Upgrade Key PMP 450 10 To Uncapped MBPS Upgrade Key PMP 450 20 To Uncapped MBPS Upgrade Key Page 2-68 Ordering the components Cambium part number N000000L034A N000900L001A N000900L007A N000900L008A N000900L009A HK2022A ACATHS-01A 600SSH C000000L033A C000065L007B C000065L008A C000065L009A 30010194001 30010195001 09010091001 WB3177 WB3211 N000065L033 N000045L002A N000065L031A N000065L032A C000045K002A C000045K003A C000045K004A C000045K005A C000045K006A C000045K007A Chapter 2: System hardware Ordering the components Cambium description PMP 450 Lite AP to Full AP Upgrade Key Extended Warranty PMP 450 Platform AP Extended Warranty, 1 Additional Year PMP 450 Platform AP Extended Warranty, 2 Additional Years PMP 450 Platform AP Extended Warranty, 4 Additional Years PMP 450 Platform SM Extended Warranty, 1 Additional Year PMP 450 Platform SM Extended Warranty, 2 Additional Years PMP 450 Platform SM Extended Warranty, 4 Additional Years Cambium part number C000045K008A SG00TS4009A SG00TS4017A SG00TS4025A SG00TS4010A SG00TS4018A SG00TS4026A Page 2-69 Chapter 3: System planning This chapter provides information to help the user to plan a PMP/PTP 450 Platform link. The following topics are described in this chapter:

Typical deployment on page 3-2 contains diagrams illustrating typical PMP/PTP 450 Platform site deployments. Site planning on page 3-7 describes factors to be considered when planning the proposed link end sites, including grounding, lightning protection and equipment location. Radio Frequency planning on page 3-17 describes how to plan PMP/PTP 450 Platform links to conform to the regulatory restrictions that apply in the country of operation. Link planning on page 3-28 describes factors to be taken into account when planning links, such as range, path loss and throughput. Planning for connectorized units on page 3-31 describes factors to be taken into account when planning to use connectorized ODUs with external antennas in PMP/PTP 450 Platform links. Data network planning on page 3-33 describes factors to be considered when planning PMP/PTP 450 Platform data networks. Network management planning on page 3-41 describes how to plan for PMP/PTP 450 Platform links to be managed remotely using SNMP. Security planning on page 3-42 describes how to plan for PMP/PTP 450 Platform links to operate in secure mode. Remote AP Deployment on page 3-52 describes how to deploy Remote AP. Page 3-1 Chapter 3: System planning Typical deployment Typical deployment This section contains diagrams illustrating typical PMP/PTP 450 Platform site deployments. ODU with PoE interface to PSU In the basic configuration, there is only one Ethernet interface, a copper cable for power over Ethernet

(POE) from the PSU to the ODU (PSU port), as shown in the following diagrams: mast or tower installation (Figure 40 ), wall installation (Figure 41) and roof installation (Figure 42). Figure 40 Mast or tower installation Power over Ethernet CAT5e cable (gel-filled, shielded with copper-plated steel) Network CAT5e cable ODU grou nd cables Site grounding system Equipm ent building or cabinet Bottom LPU PSU AC supply Network equipment Build ing entry Tower ground bar ODU First point of contact between drop cable and tower Intermediate grou nd cable(s) as required Ground ring Page 3-2 Chapter 3: System planning Figure 41 Wall installation Typical deployment Power over Ethernet CAT5e cable (gel-

filled, shielded with copper-plated steel) Network Cat5e cable ODU ground cables Site grounding system ODU First point of contact between drop cable and w all Bottom LPU PSU AC supply Network equipment Building entry Ground ring Page 3-3 Chapter 3: System planning Figure 42 Roof installation Air term inals (finials) ODU Typical deployment Power over Ethernet CAT5e cable

(gel-filled, shielded with copper-

plated steel) Network CAT5e cable ODU ground cables Site grounding system Tower grounding conductor Building entry point Drop cable inside b uilding Equipm ent room Bottom LPU PSU AC supply Network equip ment Build ing ground ring Equipm ent room entry point AC service Page 3-4 Chapter 3: System planning Figure 43 GPS receiver wall installation Typical deployment Power over Ethernet CAT5e cable (gel-filled, shielded with copper-

plated steel) Network Cat5e cable ODU/ GPS Ground cables Site grounding system Drop cable to top LPU and ODU GPS receiver First point of contact between drop cable and wall CMM 4 Network equipment Ground ring Page 3-5 Chapter 3: System planning Figure 44 GPS receiver tower or mast installation Typical deployment Page 3-6 Chapter 3: System planning Site planning Site planning This section describes factors to be considered when choosing sites for PMP or PTP radios, power supplies, CMM4 (if applicable) and UGPS (if applicable). Site selection for PMP/PTP radios When selecting a site for the ODU, consider the following factors:

Height and location to ensure that people are kept away from the antenna; see Calculated distances and power compliance margins on page 4-24. Height and location to achieve the best radio path. Indoor location where the power supply LED indicators will be visible, so the drop cable length will not exceed the maximum recommended length; see Power supply site selection on page 3-8. Ability to meet the requirements specified in Grounding and lightning protection on page 3-8. Aesthetics and planning permission issues. Cable lengths; see Ethernet standards and cable lengths on page 2-33. The effect of strong winds on the installation; see ODU wind loading on page 3-11. Page 3-7 Chapter 3: System planning Site planning Power supply site selection When selecting a site for the ODU power supply, consider the following factors:

Indoor location with no possibility of condensation, flooding or high humidity. Availability of a mains electricity supply. Located in an environment where it is not likely to exceed its operational temperature rating, allowing for natural convection cooling. Accessibility for viewing status indicator LED and connecting Ethernet cables. Cable lengths; see Ethernet standards and cable lengths on page 2-33. Maximum cable lengths When installing PMP/PTP 450i Series ODU, the maximum permitted length of the shielded copper Ethernet interface cable is 330 feet (100m) from AP/BHM/SM/BHS to their associated power supplies or CMM4. When installing PMP 450m Series ODU, the maximum permitted length of the shielded copper Ethernet interface cable is 330 feet ( 100m) from ODU to the network interface equipment. Grounding and lightning protection Warning Electro-magnetic discharge (lightning) damage is not covered under warranty. The recommendations in this guide, when followed correctly, give the user the best protection from the harmful effects of EMD. However 100% protection is neither implied nor possible. Structures, equipment and people must be protected against power surges (typically caused by lightning) by conducting the surge current to ground via a separate preferential solid path. The actual degree of protection required depends on local conditions and applicable local regulations. To adequately protect a PMP/PTP 450 Platform installation, both ground bonding and transient voltage surge suppression are required. Full details of lightning protection methods and requirements can be found in the international standards IEC 61024-1 and IEC 61312-1, the U.S. National Electric Code ANSI/NFPA No. 70-1984 or section 54 of the Canadian Electric Code. Warning International and national standards take precedence over the requirements in this guide. Page 3-8 Chapter 3: System planning Site planning Lightning protection zones Use the rolling sphere method (Figure 45) to determine where it is safe to mount equipment. An imaginary sphere, typically 50 meters in radius, is rolled over the structure. Where the sphere rests against the ground and a strike termination device (such as a finial or ground bar), all the space under the sphere is considered to be in the zone of protection (Zone B). Similarly, where the sphere rests on two finials, the space under the sphere is considered to be in the zone of protection. Figure 45 Rolling sphere method to determine the lightning protection zones Zone A: In this zone a direct lightning strike is possible. Do not mount equipment in this zone. Zone B: In this zone, direct EMD (lightning) effects are still possible, but mounting in this zone significantly reduces the possibility of a direct strike. Mount equipment in this zone. Warning Never mount equipment in Zone A. Mounting in Zone A may put equipment, structures and life at risk. Page 3-9 Chapter 3: System planning Site planning Site grounding system Confirm that the site has a correctly installed grounding system on a common ground ring with access points for grounding the 450 Platform Family ODU. If the outdoor equipment is to be installed on the roof of a high building (Figure 42), confirm that the following additional requirements are met:

A grounding conductor is installed around the roof perimeter to form the main roof perimeter lightning protection ring. Air terminals are installed along the length of the main roof perimeter lightning protection ring, typically every 6.1m (20ft). The main roof perimeter lightning protection ring contains at least two down conductors connected to the grounding electrode system. The down conductors should be physically separated from one another, as far as practical. ODU and external antenna location Find a location for the ODU (and external antenna for connectorized units) that meets the following requirements:

The equipment is high enough to achieve the best radio path. People can be kept a safe distance away from the equipment when it is radiating. The safe separation distances are defined in Calculated distances and power compliance margins on page 4-

24. The equipment is lower than the top of the supporting structure (tower, mast or building) or its lightning air terminal. If the ODU is connectorized, select a mounting position that gives it maximum protection from the elements, but still allows easy access for connecting and weatherproofing the cables. To minimize cable losses, select a position where the antenna cable lengths can be minimized. If diverse or two external antennas are being deployed, it is not necessary to mount the ODU at the midpoint of the antennas. ODU ambient temperature limits Select a location where the ODU can operate within safe ambient temperature limits. The following points need to be considered while selecting a location for the ODU:

The ODU must be mounted in a Restricted Access Location (as defined in EN 60950-1) if the operating ambient temperature may exceed 40C, including solar radiation. If the ambient temperature never exceeds 40C, the temperature of the external metal case parts of the ODU will not exceed the touch temperature limit of 70C. If the ambient temperature never exceeds 60C, the temperature of the external metal case parts of the ODU will not exceed the touch temperature limit of 90C. Page 3-10 Chapter 3: System planning Site planning Note A restricted access location is defined (in EN 60950-1) as one where access may only be gained by use of a tool or lock and key, or other means of security, and access is controlled by the authority responsible for the location. Access must only be gained by persons who have been instructed about the reasons for the restrictions applied to the location and about any precautions that must be taken. Examples of permissible restricted access locations are a lockable equipment room or a lockable cabinet. ODU wind loading Ensure that the ODU and the structure on which it is mounted are capable of withstanding the prevalent wind speeds at a proposed 450 Platform site. Wind speed statistics are available from national meteorological offices. The ODU and its mounting bracket are capable of withstanding wind speeds of:

Up to 200 mph (322 kph) for PMP 450m Series AP 5 GHz Up to 124 mph (Integrated) for PMP/PTP 450i all models 3 GHz and 5 GHz Up to 200 mph (Connectorized) for PMP/PTP 450i all models 3 GHz and 5 GHz Up to 200 mph (322 kph) for PMP/PTP 450 all models Up to 200 mph (322 kph) for PMP 450 Ruggedized Up to 200 mph (322 kph) for PMP 450i all models 900 MHz Up to 118 mph (191 kph) for PMP 450b Up to 90 mph (145 kph) for PMP 450d Up to 100 mph (161 kph) for 900 MHz antennas Wind blowing on the ODU will subject the mounting structure to significant lateral force. The magnitude of the force depends on both wind strength and surface area of the ODU. Wind loading is estimated using the following formulae:

Force (in kilograms) = 0.1045aV2 where:

o o a is the surface area in square meters, and V is the wind speed in meters per second. Force (in pounds) = 0.0042Av2 where:

o o A is the surface area in square feet, and v is the wind speed in miles per hour. Applying these formulae to the 450 platform at different wind speeds, the resulting wind loadings are shown in below tables. Page 3-11 Chapter 3: System planning Table 69 PMP 450m Series wind loading (Newton) Site planning Type of ODU Max surface area

(square meters) Integrated 90 sector antenna 0.331 Wind speed (kilometer per hour) 160 671 170 757 180 849 190 946 200 1048 Table 70 PMP/PTP 450i Series wind loading (Newton) Type of ODU Max surface area

(square meters) Connectorized Directional Yagi antenna - 900 MHz External 65 sector antenna 900 MHz Directional antenna 3.x GHz Integrated 90 sector antenna -3.x GHz Directional antenna 5 GHz Integrated 90 sector antenna - 5 GHz 0.035 0.025 0.253 0.1 0.18 0.093 0.126 Wind speed (kilometer per hour) 160 94 67 170 106 76 180 119 85 190 132 94 200 146 105 677 764 857 954 1058 142 160 180 200 222 83 94 105 117 130 249 281 315 351 389 337 381 427 475 527 Table 71 PMP 450m Series wind loading (lb force) Type of ODU Max surface area

(square feet) Integrated 90 sector antenna 3.565 Wind speed (miles per hour) 100 150 105 165 110 181 115 198 120 216 Page 3-12 Chapter 3: System planning Table 72 PMP/PTP 450i Series wind loading (lb force) Site planning Type of ODU Max surface area

(square feet) Connectorized Directional antenna 5 GHz Integrated 90 sector antenna - 5 GHz Directional Yagi antenna - 900 MHz External 65 sector antenna 900 MHz 0.377 1.001 1.356 0.27 2.72 Wind speed (miles per hour) 100 16 42 57 11 105 17 46 63 13 110 19 51 69 14 115 21 56 75 15 120 23 61 82 16 114 126 138 151 165 For a connectorized ODU, add the wind loading of the external antenna to that of the ODU. The antenna manufacturer should be able to quote wind loading. Table 73 PMP/PTP 450 Series wind loading (Newton) Type of ODU Max surface area

(square meters) External 60 sector antenna 2.4 GHz AP 0.27 External 60 sector antenna 5 GHz AP External 90 sector antenna 5 GHz AP SM Integrated High-Gain, Ruggedized 0.066 0.083 0.027 0.093 Wind speed (kilometer per hour) 160 722 177 170 815 180 914 190 1019 200 1129 199 223 249 276 222 251 281 313 347 72 249 82 281 91 315 102 351 113 389 Integrated Dish 0.14 375 423 474 528 585 Page 3-13 Chapter 3: System planning Table 74 PMP/PTP 450 Series wind loading (lb force) Site planning Type of ODU Max surface area

(square feet) External 60 sector antenna 2.4 GHz AP External 60 sector antenna 5 GHz AP External 90 sector antenna 5 GHz AP SM Integrated High-

Gain, Ruggedized Integrated Dish 2.9 0.71 0.89 0.29 1 1.49 Wind speed (miles per hour) 100 122 105 134 110 147 115 161 120 175 29.8 37 12 42 63 33 41 13 46 69 37 45 15 51 76 39 49 16 56 83 43 54 18 60 90 Page 3-14 Chapter 3: System planning Site planning Hazardous locations Check that the ODUs will not be exposed to hazardous gases, as defined by HAZLOC (USA) and ATEX

(Europe) regulations. If there is a risk of such exposure, then order the PTP/PMP 450i ATEX/Hazloc product variants, as these are intended for operation in locations with gas hazards. The ATEX and HAZLOC standards limit the EIRP as shown in Table 75. Table 75 EIRP limits from ATEX and HAZLOC standards ATEX gas group HAZLOC gas group Typical gas type Maximum EIRP

(Watt) IIA IIB IIC IIC D C B A Propane Ethylene Hydrogen Acetylene Further reading For information about Ordering Connectorized/ Integrated ATEX/HAZLOC ODUs ATEX/HAZLOC standards and type approval Deployment of ATEX/HAZLOC ODUs 6 3.5 2 2 Refer to Table 62 and Table 63 on pages 2-61 and 2-62 Hazardous location compliance on page 4-32 PMP/PTP 450i Hazardous Location Safety Guidance (pmp-1712) Drop cable grounding points To estimate how many grounding kits are required for each drop cable, refer to the site installation diagrams (Figure 40 , Figure 41, and Figure 42) and use the following criteria:

The drop cable shield must be grounded near the ODU at the first point of contact between the drop cable and the mast, tower or building. The drop cable shield must be grounded at the building entry point. For mast or tower installations (Figure 40), use the following additional criteria:

The drop cable shield must be grounded at the bottom of the tower, near the vertical to horizontal transition point. This ground cable must be bonded to the tower or tower ground bus bar (TGB), if installed. Page 3-15 Chapter 3: System planning Site planning If the tower is greater than 61 m (200 ft) in height, the drop cable shield must be grounded at the tower midpoint, and at additional points as necessary to reduce the distance between ground cables to 61 m (200 ft) or less. In high lightning-prone geographical areas, the drop cable shield must be grounded at spacing between 15 to 22 m (50 to 75 ft). This is especially important on towers taller than 45 m (150 ft). For roof installations (Figure 42), use the following additional criteria:

The drop cable shield must be bonded to the building grounding system at its top entry point (usually on the roof). The drop cable shield must be bonded to the building grounding system at the entry point to the equipment room. Lightning Protection Unit (LPU) location Find a location for the bottom LPU that meets the following requirements:

The bottom LPU can be connected to the drop cable from the ODU. The bottom LPU is within 600 mm (24 in) of the point at which the drop cable enters the building, enclosure or equipment room within a larger building. The bottom LPU can be bonded to the grounding system. Page 3-16 Chapter 3: System planning Radio Frequency planning Radio Frequency planning This section describes how to plan 450 Platform Family links to conform to analysis of spectrum and the regulatory restrictions that apply in the country of operation. Regulatory limits Many countries impose EIRP limits (Allowed EIRP) on products operating in the bands used by the 450 Platform Family. Refer to Equipment Disposal (Chapter 10: Reference information) on page 10-49 to determine what the maximum transmitted power and EIRP for PMP/PTP 450 Plaftrom that can be used in each of countries and frequency band. Caution It is the responsibility of the user to ensure that the PMP/PTP ODU is operated in accordance with local regulatory limits. Note Contact the applicable radio regulator to find out whether or not registration of the PMP/PTP 450 Platform link is required. Conforming to the limits Ensure the link is configured to conform to local regulatory requirements by configuring the PMP 450/450i Series AP or PTP 450/450i Series BHM for the correct country. In the following situations, this does not prevent operation outside the regulations:

When using connectorized ODUs with external antennas, the regulations may require the maximum transmit power to be reduced. Available spectrum The available spectrum for operation depends on the regulatory band. When configured appropriately, the unit will only allow operation on those channels which are permitted by the regulations. Page 3-17 Chapter 3: System planning Radio Frequency planning Certain regulations have allocated certain channels as unavailable for use:

FCC has allocated part of the 5.1 & 5.2 GHz ETSI has allocated part of the 5.4 GHz band to weather radar. UK and some other European countries have allocated part of the 5.8 GHz band to Road Transport and Traffic Telematics (RTTT) systems. The number and identity of channels barred in a given regulatory band is dependent on the channel bandwidth and channel raster selected. Analyzing the RF Environment An essential element in RF network planning is the analysis of spectrum usage and the strength of the signals that occupy the spectrum. Regardless of how these parameters are measured and log or chart the results (through the Spectrum Analyzer feature or by using a spectrum analyzer), ensure measurements are performed:

At various times of day. On various days of the week. Periodically into the future. As new RF neighbors move in or consumer devices proliferate in currently used spectrum, this keeps the user aware of the dynamic possibilities for interference within the network. Channel bandwidth Select the required channel bandwidth for the link. The selection depends upon the regulatory band selected. The wider the channel bandwidth, the greater the capacity. As narrower channel bandwidths take up less spectrum, selecting a narrow channel bandwidth may be a better choice when operating in locations where the spectrum is very busy. Both ends of the link must be configured to operate on the same channel bandwidth. Anticipating Reflection of Radio Waves In the signal path, any object that is larger than the wavelength of the signal can reflect the signal. Such an object can even be the surface of the earth or of a river, bay or lake. The wavelength of the signal is approximately 2 inches (or 5 cm) for 5.4 GHz and 5.8 GHz signals. 12 inches for 900 MHz signals A reflected signal can arrive at the antenna of the receiver later than the non-reflected signal arrives. These two or more signals cause the condition known as multipath. Multipath may increase or decrease the signal level, resulting in overall attenuation that may be higher or lower than that caused by the link distance. This is problematic at the margin of the link budget, where the standard operating margin (fade margin) may be compromised. Page 3-18 Chapter 3: System planning Radio Frequency planning Obstructions in the Fresnel Zone The Fresnel (pronounced freNEL) Zone is a three-dimensional volume around the line of sight of an antenna transmission. Objects that penetrate this area can cause the received strength of the transmitted signal to fade. Out-of-phase reflections and absorption of the signal result in signal cancellation. The foliage of trees and plants in the Fresnel Zone can cause signal loss. Seasonal density, moisture content of the foliage, and other factors such as wind may change the amount of loss. Plan to perform frequent and regular link tests if you must transmit through foliage. Planning for co-location The first step to avoid interference in wireless systems is to set all AP/BHMs to receive timing from a synchronization source (Cluster Management Module, or Universal Global Positioning System). This ensures that the modules are in sync and start transmitting at the same time each frame. The second step to avoid interference is to configure parameters on all AP/BHMs of the same frequency band in proximity such that they have compatible transmit/receive ratios (all stop transmitting each frame before any start receiving). This avoids the problem of one AP/BHM attempting to receive the signal from a distant SM/BHS while a nearby AP/BHM transmits, which could overpower that signal. Note Refer to Frame Alignment Legacy Mode parameter of Configuration > Radio > Adavance tab for legacy product settings (See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132).

(reserved) Contention slots The following parameters on the AP/BHM determine the transmit/receive ratio:

Downlink Data percentage Frame Period Max Range If OFDM (450 Platform Family, PMP/PTP 230) and FSK (PMP/PTP 1x0) APs/BHMs of the same frequency band and channel bandwidth are in proximity, or if you want BHMs set to different parameters then you must use the Frame Calculator to identify compatible settings for APs/BHMs. The co-location is also supported for 900 MHz PMP 450i Series APs (OFDM) and PMP 100 Series APs

(FSK). The Frame Calculator is available on the web management interface Tools > Frame Calculator. To use the Frame Calculator, type into the calculator various configurable parameter values for each proximal AP/BHM and then record the resulting AP/BHM Receive Start value. Next vary the Downlink Data percentage in each calculation and iterate until a calculated AP/BHM Receive Start for all co-located AP/BHMs where the transmit end does not come before the receive start. Cambium also provides co-location tool which helps in co-location planning:

https://support.cambiumnetworks.com/files/colocationtool Page 3-19 Chapter 3: System planning For more information on 450 Platform Family co-location, see http://www.cambiumnetworks.com/solution-papers Radio Frequency planning Multiple OFDM Access Point Clusters When deploying multiple AP clusters in a dense area, consider aligning the clusters as shown below. However, this is only a recommendation. An installation may dictate a different pattern of channel assignments. Figure 46 Example layout of 16 Access Point sectors (ABCD), 90 degree sectors An example for assignment of frequency channels is provided in the following table. Table 76 Example 5.8 GHz 4-channel assignment by access site Symbol Frequency A B C D 5.740 GHz 5.780 GHz 5.760 GHz 5.800 GHz Page 3-20 Chapter 3: System planning Figure 47 Example layout of 6 Access Point sectors (ABC), 60 degree sectors Radio Frequency planning An example for assignment of frequency channels and sector IDs is provided in the following table. Table 77 Example 5.8 GHz 3-channel assignment by access site Symbol Frequency A B C 5.740 GHz 5.760 GHz 5.780 GHz Page 3-21 Chapter 3: System planning Radio Frequency planning Considerations on back-to-back frequency reuse Cambium Networks recommends to use back-to-back (ABAB) frequency reuse, as shown in Figure 46. This means that a base site of four sectors can be created using two frequencies, which works very well and helps define networks in situations where high capacity is required in a limited amount of spectrum. The conditions necessary to implement this plan are:

GPS synchronization: all the access points transmit at the same time Uplink and Downlink timings across APs do not overlap: they can be adjusted using the frame calculators and co-location tools provided by Cambium Uplink power control to ensure that all signals are received on the uplink at the same level: this is automatically enabled on all sectors There are no reflecting objects which are too large in the exclusion zones defined in this section. The SMs do not normally have line-of-sight (LoS) to an interfering base station. The worst case range ratio in Figure 46 is 5:1 which in LoS only gives 14 dB protection. Greater than 30 dB is required for 256QAM capability. Down tilt can be used to advantage when the elevation beamwidth is low. Also the range ratio applies to the longest distance SM, shorter distance SMs have a better range ratio. This frequency reuse plan may not always give 256QAM for the longest distance SMs. It is usually a good compromise between using more spectrum and guaranteed modulation rate. Reflecting objects Figure 48 shows two diagrams of the same reflecting object. Uplink interference demonstrates the situation when the two SMs are transmitting at the same time. SM2 should be received cleanly by the AP for Sector 3. At the same time interference can arise from SM1 via the reflecting object and cause a lower Signal-to-Interference ratio than required at AP3. This may either cause transmission errors which are corrected by ARQ or cause the selected modulation rate to be lowered. Either may cause a lower throughput from SM2 and therefore sector 3. Downlink interference shows the situation when AP3 interferes with SM1. Again the transmission may be reduced by errors or a reduction in modulation rate. Page 3-22 Chapter 3: System planning Figure 48 Reflection Radio Frequency planning Reflection likelihood guidance As shown in the previous section, reflection can cause a decrease in throughput in an ABAB base site. This section provides guidance on whether a reflection is likely to cause interference. The first condition for whether a reflection can cause the data rate to reduce is that the reflecting object must be in view of the AP and the SM in order to re-transmit the signal. If this is not the case, then the object cannot cause interference. Given that the potential reflecting object is seen by the AP and the SM, there are a range of object sizes and a range of zones where we can predict that interference will occur which may reduce the throughput when both sector 1 and sector 3 are carrying traffic. Figure 49 and Figure 50 show regions enumerated A, B, C, and D. We also need to consider objects of size 1, 2, 3 and 4 and define the areas where the objects may interfere. object size 1: a flat building face with a clear reflecting property from sector to AP object size 2: random metalwork such as a wireless tower object size 3: a 0.5 X 0.5m flat metallic face or tree object size 4: a 0.2 X 0.2m random metal structure or 0.5 X 0.5m foliage. The conditions for no interference are:

The size 1 object can interfere at large distances. It is necessary to look at the geometry by which reflection could occur and cause interference. Typically, this will occur at a restricted range of azimuths and ranges. size 2 outside zone B size 3 outside zone C size 4 outside zone D Page 3-23 Chapter 3: System planning Figure 49 Sector Antenna Radio Frequency planning Page 3-24 Chapter 3: System planning Figure 50 cnMedusa Antenna Radio Frequency planning Page 3-25 Chapter 3: System planning Radio Frequency planning Figure 49 and Figure 50 each have three diagrams scaled in meters where Figure 49 is for the sector antenna and Figure 50 is for cnMedusa. In each figure the distances and heights assume a typical down tilt of 4. In each figure the top diagram represents the clearances required at zero azimuth. The middle diagram represents the scaling required to the top diagram to allow for differences in azimuth of the considered reflecting object. The bottom diagram is the scaled version of the top diagram allowing for the dotted azimuth line in the middle diagram.PMP 450m Series planning PMP 450m Series AP is based on Massive MU-MIMO technology. It is a 14x14 MIMO system which allows simultaneous communication to up to seven SMs. Figure 51 PMP 450m Series AP antenna beam PMP 450m installation recommendations

. Page 3-26 Chapter 3: System planning Radio Frequency planning For best performance it is recommended to have a clearance zone around the mast. The clearance zone depends on the surrounding environment and the antennas down tilt. If the mast is surrounded by metal then larger clearance is required compared to an environment where the antenna is surrounded by foliage SMs should be spread in azimuth of AP antenna 450m is susceptible to movement, for best MU-MIMO performance it is recommended that the 450m AP is mounted/installed on a mast that is extremely rigid (no movement and is 100% vertical). LINKPlanner can be used to plan SMs across the AP antenna azimuth Page 3-27 Chapter 3: System planning Link planning Link planning This section describes factors to be taken into account when planning links, such as range, obstacles path loss and throughput. LINKPlanner is recommended. Range and obstacles Calculate the range of the link and identify any obstacles that may affect radio performance. Perform a survey to identify all the obstructions (such as trees or buildings) in the path and to assess the risk of interference. This information is necessary in order to achieve an accurate link feasibility assessment. The 450 Platform Family is designed to operate in Non-Line-of-Sight (NLoS) and Line-of-Sight (LoS) environments. An NLOS environment is one in which there is no optical line-of-sight, that is, there are obstructions between the antennas. OFDM technology can often use multi-pathing to an advantage to overcome nLOS, especially in cases where the Fresnel zone is only partially blocked by buildings, urban canyons, or foliage. OFDM tends to help especially when obstacles are near the middle of the link, and less so when the obstacles are very near the ODU. However, attenuation through walls and trees is substantial for any use of the 5.4 GHz and 5.8 GHz frequency bands. The lower frequency radio waves of 900 MHz radios provide greater penetration through walls, trees and other obstacles, making it optimal for most non-line-of-sight applications. Even with OFDM, these products are not expected to penetrate walls or extensive trees and foliage. Path loss Path loss is the amount of attenuation the radio signal undergoes between the two ends of the link. The path loss is the sum of the attenuation of the path if there were no obstacles in the way (Free Space Path Loss), the attenuation caused by obstacles (Excess Path Loss) and a margin to allow for possible fading of the radio signal (Fade Margin). The following calculation needs to be performed to judge whether a particular link can be installed:

L free _ space L excess L fade L seasonal L capability Where:

Is:

space _ freeL L excess L fade L seasona Free Space Path Loss (dB) Excess Path Loss (dB) Fade Margin Required (dB) Seasonal Fading (dB) Page 3-28 Chapter 3: System planning L capability Equipment Capability (dB) Link planning Calculating Link Loss The link loss is the total attenuation of the wireless signal between two point-to-multipoint units. The link loss calculation is presented below:

Link Loss (dB) = Transmit power of the remote wireless unit (dBm) Tx Cable loss (dB) Received power at the local unit (dBm) Rx cable loss (dB) + Antenna gain at the remote unit (dBi) + Antenna gain at the local unit (dBi) Calculating Rx Signal Level The determinants in Rx signal level are illustrated in Figure 52. Figure 52 Determinants in Rx signal level Rx signal level is calculated as follows:

Rx signal level dB = Tx power Tx cable loss + Tx antenna gain free space path loss + Rx antenna gain Rx cable loss Note This Rx signal level calculation presumes that a clear line of sight is established between the transmitter and receiver and that no objects encroach in the Fresnel zone. Page 3-29 Chapter 3: System planning Link planning Calculating Fade Margin Free space path loss is a major determinant in Rx (received) signal level. Rx signal level, in turn, is a major factor in the system operating margin (fade margin), which is calculated as follows:

System operating margin (fade margin) dB = Rx signal level dB Rx sensitivity dB Thus, fade margin is the difference between strength of the received signal and the strength that the receiver requires for maintaining a reliable link. A higher fade margin is characteristic of a more reliable link. Adaptive modulation Adaptive modulation ensures that the highest throughput that can be achieved instantaneously will be obtained, taking account of propagation and interference. When the link has been installed, web pages provide information about the link loss currently measured by the equipment, both instantaneously and averaged. The averaged value will require maximum seasonal fading to be added, and then the radio reliability of the link can be computed. For details of the system throughput, link loss and maximum distance for each frequency band in all modulation modes, see Link on page 10-45. Page 3-30 Chapter 3: System planning Planning for connectorized units Planning for connectorized units This section describes factors to be taken into account when planning to use connectorized ODUs with external antennas in 450 Platform Family links. When to install connectorized units The majority of radio links can be successfully deployed with the integrated ODU. However the integrated units may not be sufficient in some areas, for example:

Where the path is heavily obscured by dense woodland on an NLOS link. Where long LOS links are required. Where there are known to be high levels of interference. In these areas, connectorized ODUs and external antennas should be used. Choosing external antennas When selecting external antennas, consider the following factors:

The required antenna gain. Ease of mounting and alignment. Use dual-polarization antenna (as the integrated antenna). Note Enter the antenna gain and cable loss into the Installation Wizard, if the country selected has an EIRP limit, the corresponding maximum transmit power will be calculated automatically by the unit. Calculating RF cable length (5.8 GHz FCC only) The 5.8 GHz band FCC approval for the product is based on tests with a cable loss between the ODU and antenna of not less than 1.2 dB. If cable loss is below 1.2 dB with a 1.3 m (4 ft) diameter external antenna, the connectorized 450 Platform Family may exceed the maximum radiated spurious emissions allowed under FCC 5.8 GHz rules. Cable loss depends mainly upon cable type and length. To meet or exceed the minimum loss of 1.2 dB, use cables of the type and length specified in Table 78 (source: Times Microwave). This data excludes connector losses. Table 78 RF cable lengths required to achieve 1.2 dB loss at 5.8 GHz RF cable type Minimum cable length Page 3-31 Chapter 3: System planning Planning for connectorized units LMR100 LMR200 LMR300 LMR400 LMR600 0.6 m (1.9 ft) 1.4 m (4.6 ft) 2.2 m (7.3 ft) 3.4 m (11.1 ft) 5.0 m (16.5 ft) Page 3-32 Chapter 3: System planning Data network planning Data network planning This section describes factors to be considered when planning 450 Platform Family data networks. Understanding addresses A basic understanding of Internet Protocol (IP) address and subnet mask concepts is required for engineering your IP network. IP address The IP address is a 32-bit binary number that has four parts (octets). This set of four octets has two segments, depending on the class of IP address. The first segment identifies the network. The second identifies the hosts or devices on the network. The subnet mask marks a boundary between these two sub-addresses. Dynamic or static addressing For any computer to communicate with a module, the computer must be configured to either use DHCP (Dynamic Host Configuration Protocol). In this case, when not connected to the network, the computer derives an IP address on the 169.254 network within two minutes. have an assigned static IP address (for example, 169.254.1.5) on the 169.254 network. Note If an IP address that is set in the module is not the 169.254.x.x network address, then the network operator must assign the computer a static IP address in the same subnet. When a DHCP server is not found To operate on a network, a computer requires an IP address, a subnet mask, and possibly a gateway address. Either a DHCP server automatically assigns this configuration information to a computer on a network or an operator must input these items. When a computer is brought on line and a DHCP server is not accessible (such as when the server is down or the computer is not plugged into the network), Microsoft and Apple operating systems default to an IP address of 169.254.x.x and a subnet mask of 255.255.0.0 (169.254/16, where /16 indicates that the first 16 bits of the address range are identical among all members of the subnet). Page 3-33 Chapter 3: System planning Data network planning DNS Client The DNS Client is used to resolve names of management servers within the operators management domain (see Figure 53). This feature allows hostname configuration for NTP servers, Authorization Servers, DHCP relay servers, and SNMP trap servers. Operators may choose to either enter in the FQDN

(Fully Qualified Domain Name) for the host name or to manually enter the IP addresses of the servers. Figure 53 Cambium networks management domain Network Address Translation (NAT) NAT, DHCP Server, DHCP Client and DMZ in SM The system provides NAT (network address translation) for SMs in the following combinations of NAT and DHCP (Dynamic Host Configuration Protocol):

NAT Disabled NAT with DHCP Client (DHCP selected as the Connection Type of the WAN interface) and DHCP Server NAT with DHCP Client(DHCP selected as the Connection Type of the WAN interface) NAT with DHCP Server NAT without DHCP NAT NAT isolates devices connected to the Ethernet/wired side of a SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic (separate from its address for management), terminates transport traffic, and allows you to assign a range of IP addresses to devices that are connected to the Ethernet/wired side of the SM. Page 3-34 Chapter 3: System planning Data network planning In the Cambium system, NAT supports many protocols, including HTTP, ICMP (Internet Control Message Protocols), and FTP (File Transfer Protocol). For virtual private network (VPN) implementation, L2TP over IPSec (Level 2 Tunneling Protocol over IP Security) and PPTP (Point to Point Tunneling Protocol) are supported. DHCP DHCP enables a device to be assigned a new IP address and TCP/IP parameters, including a default gateway, whenever the device reboots. Thus DHCP reduces configuration time, conserves IP addresses, and allows modules to be moved to a different network within the Cambium system. In conjunction with the NAT features, each SM provides:

A DHCP server that assigns IP addresses to computers connected to the SM by Ethernet protocol. A DHCP client that receives an IP address for the SM from a network DHCP server. DMZ In conjunction with the NAT features, a DMZ (demilitarized zone) allows the assignment of one IP address behind the SM for a device to logically exist outside the firewall and receive network traffic. The first three octets of this IP address must be identical to the first three octets of the NAT private IP address. Developing an IP addressing scheme Network elements are accessed through IP Version 4 (IPv4) addressing. A proper IP addressing method is critical to the operation and security of a network. Each module requires an IP address on the network. This IP address is for only management purposes. For security, you must either:

Assign a non-routable IP address. Assign a routable IP address only if a firewall is present to protect the module. You assign an IP addresses to computers and network components by either static or dynamic IP addressing. You will also assign the appropriate subnet mask and network gateway to each module. Address Resolution Protocol As previously stated, the MAC address identifies a module in:

Communications between modules. The data that modules store about each other. The IP address is essential for data delivery through a router interface. Address Resolution Protocol

(ARP) correlates MAC addresses to IP addresses. Page 3-35 Chapter 3: System planning Data network planning For communications to outside the network segment, ARP reads the network gateway address of the router and translates it into the MAC address of the router. Then the communication is sent to MAC address (physical network interface card) of the router. For each router between the sending module and the destination, this sequence applies. The ARP correlation is stored until the ARP cache times out. Allocating subnets The subnet mask is a 32-bit binary number that filters the IP address. Where a subnet mask contains a bit set to 1, the corresponding bit in the IP address is part of the network address. Example IP address and subnet mask In Figure 54, the first 16 bits of the 32-bit IP address identify the network:

Figure 54 Example of IP address in Class B subnet Octet 1 Octet 4 IP address 169.254.1.1 10101001 11111110 00000001 00000001 Subnet mask 255.255.0.0 11111111 11111111 00000000 00000000 Octet 2 Octet 3 In this example, the network address is 169.254 and 216 (65,536) hosts are addressable. IP address of 169.254.1.1 Selecting non-routable IP addresses The factory default assignments for network elements are:

Unique MAC address Subnet mask of 255.255.0.0 Network gateway address of 169.254.0.0 For each radio and CMM4, assign an IP address that is both consistent with the IP addressing plan for your network and cannot be accessed from the Internet. IP addresses within the following ranges are not routable from the Internet, regardless of whether a firewall is configured:

10.0.0.0 10.255.255.255 172.16.0.0 172.31.255.255 192.168.0.0 192.168.255.255 Also, the subnet mask and network gateway for each CMM4 can be assigned. Translation bridging Optionally, the AP can be configured to change the source MAC address in every packet it receives from its SMs to the MAC address of the SM/BHS that bridged the packet, before forwarding the packet toward the public network. In this case:

Page 3-36 Chapter 3: System planning Data network planning Not more than 128 IP devices at any time are valid to send data to the AP from behind the SM. SM populates the Translation Table tab of its Statistics web page, displaying the MAC address and IP address of all the valid connected devices. Each entry in the Translation Table is associated with the number of minutes that have elapsed since the last packet transfer between the connected device and the SM. If 128 are connected, and another attempts to connect:

o o If no Translation Table entry is older than 255 minutes, the attempt is ignored. If an entry is older than 255 minutes, the oldest entry is removed and the attempt is successful. The Send Untranslated ARP parameter in the General tab of the Configuration page can be:

o Disabled, so that the AP overwrites the MAC address in ARP packets before forwarding them. o Enabled, so that the AP forwards ARP packets regardless of whether it has overwritten the MAC address. This is the Translation Bridging feature, which you can enable in the General page of the Configuration web page in the AP. When this feature is disabled, the setting of the Send Untranslated ARP parameter has no effect, because all packets are forwarded untranslated (with the source MAC address intact). See Address Resolution Protocol on Page 3-35. Engineering VLANs The radios support VLAN functionality as defined in the 802.1Q (Virtual LANs) specification, except for the following aspects of that specification:

Protocols:

o Generic Attribute Registration Protocol (GARP) GARV o Spanning Tree Protocol (STP) o Multiple Spanning Tree Protocol (MSTP) o GARP Multicast Registration Protocol (GMRP) Embedded source routing (ERIF) in the 802.1Q header Multicast pruning Flooding unknown unicast frames in the downlink As an additional exception, the AP/BHM does not flood downward the unknown unicast frames to the SM/BHS. A VLAN configuration in Layer 2 establishes a logical group within the network. Each computer in the VLAN, regardless of initial or eventual physical location, has access to the same data. For the network operator, this provides flexibility in network segmentation, simpler management, and enhanced security. Page 3-37 Chapter 3: System planning Data network planning Special case VLAN numbers This system handles special case VLAN numbers according to IEEE specifications:

Table 79 Special case VLAN IDs VLAN Number 0 1 Purpose These packets have 802.1p priority, but are otherwise handled as untagged. Usage Constraint Must not be used as a management VLAN. Although not noted as special case by IEEE specifications, these packets identify traffic that was untagged upon ingress into the SM and must remain untagged upon egress. This policy is hard-coded in the AP. Must not be used for system VLAN traffic. 4095 This VLAN is reserved for internal use. Must not be used at all. SM membership in VLANs With the supported VLAN functionality, the radios determine bridge forwarding on the basis of not only the destination MAC address, but also the VLAN ID of the destination. This provides flexibility in how SMs are used:

Each SM can be a member in its own VLAN. Each SM can be in its own broadcast domain, such that only the radios that are members of the VLAN can see broadcast and multicast traffic to and from the SM. The network operator can define a work group of SMs, regardless of the AP(s) to which they register. Page 3-38 Chapter 3: System planning Data network planning PMP 450 Platform Family modules provide the VLAN frame filters that are described in Table 80. Table 80 VLAN filters in point-to-multipoint modules Where VLAN is active, if this parameter value is selected any combination of VLAN parameter settings any combination of VLAN parameter settings Allow Frame Types:

Tagged Frames Only Allow Frame Types:

Untagged Frames Only Local SM Management:

Disable in the SM, or All Local SM Management:

Disable in the AP any combination of VLAN parameter settings any combination of VLAN parameter settings then a frame is discarded if entering the bridge/

NAT switch through Ethernet with a VID not in the membership table TCP/IP because of this VLAN filter in the software:

Ingress with a VID not in the membership table Local Ingress with no 802.1Q tag with an 802.1Q tag, regardless of VID with an 802.1Q tag and a VID in the membership table Only Tagged Only Untagged Local SM Management leaving the bridge/

NAT switch through Ethernet with a VID not in the membership table TCP/IP Egress with a VID not in the membership table Local Egress Priority on VLANs (802.1p) The radios can prioritize traffic based on the eight priorities described in the IEEE 802.1p specification. When the high-priority channel is enabled on a SM, regardless of whether VLAN is enabled on the AP for the sector, packets received with a priority of 4 through 7 in the 802.1p field are forwarded onto the high-

priority channel. Operators may configure priority precedence as 802.1p Then Diffserv (Default) or Diffserv Then 802.1p. Since these priority precedence configurations are independent between the AP and SM, this setting must be configured on both the AP and SM to ensure that the precedence is adhered to by both sides of the link. Page 3-39 Chapter 3: System planning Data network planning VLAN settings can also cause the module to convert received non-VLAN packets into VLAN packets. In this case, the 802.1p priority in packets leaving the module is set to the priority established by the DiffServ configuration. If VLAN is enabled, immediately monitor traffic to ensure that the results are as desired. For example, high-priority traffic may block low-priority. Q-in-Q DVLAN (Double-VLAN) Tagging (802.1ad) PMP and PTP modules can be configured with 802.1ad Q-in-Q DVLAN (Double-VLAN) tagging which is a way for an operator to put an 802.1Q VLAN inside of an 802.1ad VLAN. A nested VLAN, which is the original 802.1Q tag and a new second 802.1ad tag, allows for bridging of VLAN traffic across a network and segregates the broadcast domains of 802.1Q VLANs. Q-in-Q can be used with PPPoE and/or NAT. The 802.1ad standard defines the S-VLAN as the Service Provider VLAN and the C-VLAN as the customer VLAN. The radio software does 2 layer Q-in-Q whereby the C-VLAN is the 802.1Q tag and the S-VLAN is the second layer Q tag as shown in Table 81. Table 81 Q-in-Q Ethernet frame Ethernet Header S-VLAN EthType 0x88a8 C-VLAN EthType 0x8100 IP Data EthType 0x0800 The 802.1ad S-VLAN is the outer VLAN that is configurable on the Configuration > VLAN web page of the AP/BHM. The Q-in-Q EtherType parameter is configured with a default EtherType of 0x88a8 in addition to four alternate EtherTypes that can be configured to aid in interoperability with existing networks that use a different EtherType than the default. The C-VLAN is the inner VLAN tag, which is the same as 802.1Q. As a top level concept, this operates on the outermost tag at any given time, either pushing a tag on or popping a tag off. This means packets will at most transition from an 802.1Q frame to an 801.ad frame (with a tag pushed on) or an untagged 802.1 frame (with the tag popped off. Similarly, for an 802.1ad frame, this can only transition from an 802.1ad frame to an 802.1Q frame (with the tag popped off) since the radio software only supports 2 levels of tags. Page 3-40 Chapter 3: System planning Network management planning Network management planning This section describes how to plan for 450 Platform Family links to be managed remotely using SNMP. Planning for SNMP operation Cambium modules provide the following SNMP traps for automatic notifications to the NMS:

coldStart, which signals that the SNMPv2c element is reinitializing itself and that its configuration may have been altered. warmStart, which signals that the SNMPv2c element is reinitializing such that its configuration is unaltered. authenticationFailure, which signals that the SNMPv2c element has received a protocol message that is not properly authenticated (contingent on the snmpEnableAuthenTraps object setting). linkDown, as defined in RFC 1573 linkUp, as defined in RFC 1573 egpNeighborLoss, as defined in RFC 1213 whispGPSInSync, which signals a transition from not synchronized to synchronized. whispGPSOutSync, which signals a transition from synchronized to not synchronized. whispRegComplete, which signals registration completed. whispRegLost, which signals registration lost. whispRadarDetected, which signals that the one-minute scan has been completed, radar has been detected and the radio will shut down. whispRadarEnd, which signals that the one-minute scan has been completed, radar has not been detected and the radio will resume normal operation. Note The proprietary MIBs are provided in the 450 Platform Family software download files in the support website (see Contacting Cambium Networks on page 1). Enabling SNMP Enable the SNMP interface for use by configuring the following attributes in the SNMP Configuration page:

SNMP State (default disabled) SNMP Version (default SNMPv2c) SNMP Port Number (default 161) Page 3-41 Chapter 3: System planning Security planning Security planning This section describes how to plan for 450 Platform Family links to operate in secure mode. Managing module access by passwords Filtering protocols and ports Port Configuration Isolating AP/BHM from the Internet Ensure that the IP addresses of the AP/BHM in the network:

are not routable over the Internet. do not share the subnet of the IP address of your user. RFC 1918, Address Allocation for Private Subnets, reserves for private IP networks three blocks of IP addresses that are not routable over the Internet:

/8 subnets have one reserved network, 10.0.0.0 to 10.255.255.255.

/16 subnets have 16 reserved networks, 172.16.0.0 to 172.31.255.255.

/24 subnets have 256 reserved networks, 192.168.0.0 to 192.168.255.255. Encrypting radio transmissions Cambium fixed wireless broadband IP systems employ the following form of encryption for security of the wireless link:

DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. The default encryption setting for 450 Platform Family ODU is "None". Page 3-42 Chapter 3: System planning Security planning Planning for HTTPS operation Before starting to configure HTTPS operation, ensure that the cryptographic material listed in Table 82 is available. Table 82 HTTPS security material Item User Defined Security Banner Port numbers for HTTP, HTTPS and Telnet Description The banner provides warnings and notices to be read by the user before logging in to the ODU. Use text that is appropriate to the network security policy. Quantity required Normally one per link. This depends upon network policy. Port numbers allocated by the network. As allocated by network. Planning for SNMPv3 operation SNMP security mode Decide how SNMPv3 security will be configured. MIB-based security management uses standard SNMPv3 MIBs to configure the user-based security model and the view-based access control model. This approach provides considerable flexibility, allowing a network operator to tailor views and security levels appropriate for different types of user. MIB-based security management may allow a network operator to take advantage of built-in security management capabilities of existing network managers. Web-based security management allows an operator to configure users, security levels, privacy and authentication protocols, and passphrases using the 450 Platform Family web-based management interface. The capabilities supported are somewhat less flexible than those supported using the MIB-

based security management, but will be sufficient in many applications. Selection of web-based management for SNMPv3 security disables the MIB-based security management. 450 Platform Family does not support concurrent use of MIB-based and web-based management of SNMPv3 security. Web-based management of SNMPv3 security Initial configuration of SNMPv3 security is available only to HTTP or HTTPS user accounts with security role of Security Officer. Identify the format used for SNMP Engine ID. The following formats are available:

MAC address (default) 5 and 32 hex characters (the hex character input is driven by RFC 3411 recommendations on the Engine ID) Identify the user names and security roles of initial SNMPv3 users. Two security roles are available:

Page 3-43 Chapter 3: System planning Security planning Read Only System Administrator Identify the security level for each of the security roles. Three security levels are available:

(a) No authentication, no privacy

(b) Authentication, no privacy

(c) Authentication, privacy If authentication is required, identify the protocol. The authentication protocol available is MD5. If privacy will be used, identify the protocol. The privacy protocol available is cbc-des. Managing module access by passwords From the factory, each module has a preconfigured administrator-level account in the name root, which initially requires no associated password. When you upgrade a module:

An account is created in the name admin. Both admin and root inherit the password that was previously used to access the module, if:

o Full Access password, if one was set. o Display-Only Access password, if one was set and no Full Access password was set. Caution If you use Wireless Manager, do not delete the root account from any module. If you use a NMS that communicates with modules through SNMP, do not delete the root account from any module unless you first can confirm that the NMS does not rely on the root account for access to the modules. Each module supports four or fewer user accounts, regardless of account levels. The available levels are ADMINISTRATOR, who has full read and write permissions. This is the level of the root and admin users, as well as any other administrator accounts that one of them creates. INSTALLER, who has permissions identical to those of ADMINISTRATOR except that the installer cannot add or delete users or change the password of any other user. TECHNICIAN, who has permissions to modify basic radio parameters and view informational web pages. GUEST, who has no write permissions and only a limited view of General Status tab. Admin, Installer and Tech accounts can be configured as READ-ONLY. This will allow the account to only see the items. The ability to view information of General Status tab can be controlled by the "Site Information Viewable to Guest Users" under the SNMP tab. From the factory default state, configure passwords for both the root and admin account at the ADMINISTRATOR permission level, using the Account > Change Users Password page. (If configure only one of these, then the other will still require no password for access into it and thus remain a security risk.) If you are intent on configuring only one of them, delete the admin account. The root account is the only account that CNUT uses to update the module. Page 3-44 Chapter 3: System planning Security planning After a password has been set for any ADMINISTRATOR-level account, initial access to the module GUI opens the view of GUEST level. Planning for RADIUS operation Configure RADIUS where remote authentication is required for users of the web-based interface. Remote authentication has the following advantages:

Control of passwords can be centralized. Management of user accounts can be more sophisticated. For example; users can be prompted by a network manager to change passwords at regular intervals. As another example, passwords can be checked for inclusion of dictionary words and phrases. Passwords can be updated without reconfiguring multiple network elements. User accounts can be disabled without reconfiguring multiple network elements. Remote authentication has one significant disadvantage in a wireless link product such as 450 Platform Family. If the wireless link is down, a unit on the remote side of the broken link may be prevented from contacting a RADIUS Server, with the result that users are unable to access the web-based interface. One useful strategy would be to combine RADIUS authentication for normal operation with a single locally-authenticated user account for emergency use. PMP 450 Platform Family SM provides a choice of the following authentication methods:

Phase 1:

o EAP-MSCHAPv2 o EAP-TTLS o EAP PEAP Phase 2:

o PAP o CHAP o MSCHAPv2 Ensure that the authentication method selected in 450 Platform Family is supported by the RADIUS server. Filtering protocols and ports Configure filters for specified protocols and ports from leaving the AP/BHM and SM/BHS and entering the network. This protects the network from both intended and inadvertent packet loading or probing by network users. By keeping the specified protocols or ports off the network, this feature also provides a level of protection to users from each other. Protocol and port filtering is set per AP/SM/BH. Except for filtering of SNMP ports, filtering occurs as packets leave the AP/SM/BH. For example, if SM is configured to filter SNMP, then SNMP packets are blocked from entering the SM and, thereby, from interacting with the SNMP portion of the protocol stack on the SM. Page 3-45 Chapter 3: System planning Security planning Port Filtering with NAT Enabled Where NAT is enabled on the SM/BHS, the filtering can be enabled for only the user-defined ports. The following are examples for situations where the configure port can be filtered where NAT is enabled:

To block a subscriber from using FTP, you can filter Ports 20 and 21 (the FTP ports) for both the TCP and UDP protocols. To block a subscriber from access to SNMP, you can filter Ports 161 and 162 (the SNMP ports) for both the TCP and UDP protocols. Note In only the SNMP case, filtering occurs before the packet interacts with the protocol stack. Protocol and Port Filtering with NAT Disabled Where NAT is disabled on the SM/BHS, the filtering can be enabled for both protocols and the three user-

defined ports. Using the check boxes on the interface, it can be either:

Allow all protocols except those that user wish to block. Block all protocols except those that user wish to allow. Allow or block any of the following protocols:

PPPoE (Point to Point Protocol over Ethernet) Any or all of the following IPv4 (Internet Protocol version 4) protocols:

Any or all of the following IPv4 (Internet Protocol version 4) protocols:

o SMB (Network Neighborhood) o SNMP o Bootp Client o Bootp Server o Up to 3 user-defined ports o All other IPv4 traffic (see Figure 29) Any or all of the following IPv6 (Internet Protocol version 6) protocols:

o SMB (Network Neighborhood) o SNMP o Bootp Client o Bootp Server o Up to 3 user-defined ports o All other IPv6 traffic (see Figure 29) Filter Direction Upstream and Downstream ARP (Address Resolution Protocol) Page 3-46 Chapter 3: System planning Figure 55 Categorical protocol filtering Security planning BootP Client BootP Server SNMP User Defined Port 1 All Other IPv4 User Defined Port 2 User Defined Port 3 PPPoE All Others IPv4 Multica st SMB ARP The following are example situations in which the protocol filtering is configured where NAT is disabled:

If a subscriber is blocked from only PPPoE and SNMP, then the subscriber retains access to all other protocols and all ports. If PPPoE, IPv4, and Uplink Broadcast are blocked, and also check the All others selection, then only Address Resolution Protocol is not filtered. The ports filtered as a result of protocol selections in the Protocol Filtering tab of the SM/BHS are listed in Table 83. Page 3-47 Chapter 3: System planning Security planning Table 83 Ports filtered per protocol selections Protocol Selected SMB SNMP Bootp Client Port Filtered (Blocked) Destination Ports UDP : 137, 138, 139, 445, 3702 and 1900 Destination Ports TCP : 137, 138, 139, 445, 2869, 5357 and 5358 Destination Ports TCP and UDP : 161 and 162 Source Port 68 UDP Bootp Server User Defined Port 1..3 IPv4 Multicast Source Port 67 UDP User defined ports for filtering UDP and TCP Block IPv4 packet types except other filters defined IPv6 Multicast ARP Upstream Downstream Block IPv6 packet types except other filters defined Filter all Ethernet packet type 806 Applies packet filtering to traffic coming into the FEC interface Applies packet filtering to traffic destined to exit the FEC interface Port Configuration 450 Platform Family supports access to various communication protocols and only the ports required for these protocols are available for access by external entities. Operators may change the port numbers for these protocols via the radio GUI or SNMP. Table 84 Device default port numbers Port 21 Usage FTP HTTP HTTPS SNMP port SNMP trap port Syslog Server port Standard RADIUS port Standard RADIUS accounting port 80 443 161 162 514 1812 1813 Port Usage Listen Port Listen Port Listen Port Listen Port Destination Port Destination Port Destination Port Destination Port Device AP, SM AP, SM AP, SM AP, SM AP, SM AP, SM AP AP, SM Page 3-48 Chapter 3: System planning Security planning Encrypting downlink broadcasts An AP can be enabled to encrypt downlink broadcast packets such as the following:

ARP NetBIOS broadcast packets containing video data on UDP. The encryption used is DES for a DES-configured module and AES for an AES-configured module. Before the Encrypt Downlink Broadcast feature is enabled on the AP, air link security must be enabled on the AP. Isolating SMs in PMP In an AP, SMs in the sector can be prevented from directly communicating with each other. In CMM4, the connected APs can be prevented from directly communicating with each other, which prevents SMs that are in different sectors of a cluster from communicating with each other. In the AP, the SM Isolation parameter is available in the General tab of the Configuration web page. Configure the SM Isolation feature by any of the following selections from drop-down menu:

Disable SM Isolation (the default selection). This allows full communication between SMs. Enable Option 1 - Block SM destined packets from being forwarded. This prevents both multicast/broadcast and unicast SM-to-SM communication. Enable Option 2 - Forward SM destined packets upstream. This not only prevents multicast/broadcast and unicast SM-to-SM communication but also sends the packets, which otherwise may have been handled SM to SM, through the Ethernet port of the AP. In the CMM and the CMM4, SM isolation treatment is the result of how to manage the port-based VLAN feature of the embedded switch, where all traffic can be switched from any AP to a specified uplink port. However, this is not packet level switching. It is not based on VLAN IDs. Filtering management through Ethernet Configure the SM to disallow any device that is connected to its Ethernet port from accessing the IP address of the SM. If the Ethernet Access Control parameter is set to Enabled, then:

No attempt to access the SM management interface (by http, SNMP, ftp, or tftp) through Ethernet is granted. Any attempt to access the SM management interface over the air (by IP address, presuming that LAN1 Network Interface Configuration, Network Accessibility is set to Public, or by link from the Session Status or Remote Subscribers tab in the AP) is unaffected. Page 3-49 Chapter 3: System planning Security planning Allowing management from only specified IP addresses The Security sub-menu of the Configuration web page in the AP/BHM and SM/BHS includes the IP Access Control parameter. Specify one, two, or three IP addresses that must be allowed to access the management interface (by HTTP, SNMP, FTP or TFTP). If the selection is:

IP Access Filtering Disabled, then management access is allowed from any IP address, even if the Allowed Source IP 1 to 3 parameters are populated. IP Access Filtering Enabled, and specify at least one address in the Allowed Source IP 1 to 3 parameter, then management access is limited to the specified address(es). Configuring management IP by DHCP The Configuration > IP web page of every radio contains a LAN1 Network Interface Configuration, DHCP State parameter that, if enabled, causes the IP configuration (IP address, subnet mask, and gateway IP address) to be obtained through DHCP instead of the values of those individual parameters. The setting of this DHCP state parameter is also viewable, but is not settable, in the Network Interface tab of the Home page. In the SM/BHS, this parameter is settable in the NAT tab of the Configuration web page, but only if NAT is enabled. in the IP tab of the Configuration web page, but only if the Network Accessibility parameter in the IP tab is set to Public. DHCP option 81 The DHCP server can be used to register and update the pointer (PTR) and host (A) DNS resource records on behalf of its DHCP-enabled clients. The DHCP option 81 permits the client to provide its fully qualified domain name (FQDN) as well as instructions to the DHCP server on how it would like the server to process DNS dynamic updates (if any) on its behalf. The hostname is poplulated as SiteName.DomainName depending upon following conditions:

The SiteName should only be a-z | A-Z | 0-9 and period(.) and dash(-). The domain name part should not start or end with dash (-). The underscore or space in domain name part will be converted to dash(-), anything else apart from If Sitename is default i.e. No Site Name , mac address will be used instead. valid characters will be skipped. Page 3-50 Chapter 3: System planning Security planning Controlling PPPoE PADI Downlink Forwarding The AP supports the control of forwarding of PPPoE PADI (PPPoE Active Discovery Initiation) packets. This forwarding is configured on the AP GUI Configuration > Radio page by parameter PPPoE PADI Downlink Forwarding. When set to Enabled, the AP allows downstream and upstream transmission of PPPoE PADI packets. When set to Disabled, the AP does NOT allow PPPoE PADI packets to be sent out of the AP RF interface (downstream) but will allow PPPoE PADI packets to enter the RF interface

(upstream) and exit the Ethernet interface. Page 3-51 Chapter 3: System planning Remote AP Deployment Remote AP Deployment reach around obstructions or penetrate foliage with non-LoS throughput. reach new, especially widely distributed, residential subscribers with broadband service. In cases where the subscriber population is widely distributed, or conditions such as geography restrict network deployment, you can add a Remote AP to:

provide high-throughput service to near LoS business subscribers. pass sync to an additional RF hop. In the remote AP configuration, a remote AP is co-located with an SM. The remote AP distributes the signal to SMs that are logically behind the co-located SM. A remote AP deployment is illustrated in Figure 56. Figure 56 Remote AP deployment The co-located SM receives data in one channel, and the remote AP must redistribute the data in a different channel. The two channels need to have a frequency gap equal to at least two times the used channel bandwidth. Base your selection of frequency band ranges on regulatory restrictions, environmental conditions, and throughput requirements. Note Each relay hop (additional daisy-chained remote AP) adds approximately 5-7 msec round trip latency. Page 3-52 Chapter 3: System planning Remote AP Deployment Remote AP (RAP) Performance The performance of a remote AP is identical to the AP performance in cluster. Throughputs, ranges, and antenna coverage are identical. As with all equipment operating in the unlicensed spectrum, Cambium strongly recommends that you perform site surveys before you add network elements. These will indicate that spectrum is available in the area where you want to grow. Keep in mind that:

non-LoS ranges heavily depend on environmental conditions. in most regions, not all frequencies are available. your deployments must be consistent with local regulatory restrictions. Example Use Case for RF Obstructions A remote AP can be used to provide last-mile access to a community where RF obstructions prevent SMs from communicating with the higher-level AP in cluster. For example, you may be able to use 900 MHz for the last mile between a remote AP and the outlying SMs where these subscribers cannot form good links to a higher-level 5 GHz AP. In this case, the ability of the 900-MHz wavelength to be effective around foliage at short range solves the foliage penetration problem. An example of this use case is shown in Figure 57. In this example, the 5 GHz AP is a PMP 450i AP in the 5.8 GHz band operating on a 20 MHz channel with a 2.5 ms frame; the SMs are 5 GHz PMP 450 integrated SMs. The SM connected to the remote AP is a PMP 450i SM. The remote AP is a PMP 450i AP in the 900 MHz band, also operating in a 20 MHz channel with a 2.5 ms frame; the SMs are 900 MHz PMP 450 connectorized SMs using the Cambium 23 dBi gain antenna. Page 3-53 Chapter 3: System planning Figure 57 Example for 900-MHz remote AP behind 5 GHz SM Remote AP Deployment The 5 GHz modules provide a sustained aggregate throughput of up to 126 Mbps to the sector. One of the SMs in the sector is wired to a 900-MHz remote AP, which provides NLoS sustained aggregate throughput2 of:

126 Mbps to 900-MHz SMs up to 4 miles away in the sector. 94 Mbps to 900-MHz SMs between 4 and 10 miles away in the sector. Example Use Case for Passing Sync All radios support the remote AP functionality. The BHS and the SM can reliably pass the sync pulse, and the BHM and AP can reliably receive it. However, not all devices are compatible with all other devices. The following table shows which SMs can be connected to which APs. Devices PMP 450 AP/BHM PMP 450i AP/BHM PMP 450m AP PMP 450 SM/BHS PMP 450i SM/BHS X X X Examples of passing sync over cable are shown under Passing Sync in an Additional Hop on page 3-57. 2 NLoS ranges depend on environmental conditions. Your results may vary from these. Page 3-54 Chapter 3: System planning Remote AP Deployment For PMP 450, the sync is passed in a cable that connects Pins 1 and 6 of the RJ-11 timing ports of the two modules. For PMP 450i/450m the sync is passed in a cable that connects Pins7 and 8 of the RJ-45 timing ports of the two modules. When connecting modules in this way, make sure the AP and SM are properly configured, as described in the Wiring to Extend Network Sync. Physical Connections Involving the Remote AP The SM to which a remote AP is connected to can be either an SM that serves a customer or an SM that simply serves as a relay. If the SM serves a customer, wire the remote AP to the SM as shown in Figure 58. Figure 58 Remote AP wired to SM that also serves a customer If the SM simply serves as a relay, you must use a straight-through RJ-45 female-to-female coupler and wire the SM to the remote AP as shown in Figure 59. Page 3-55 Chapter 3: System planning Figure 59 Remote AP wired to SM that serves as a relay Remote AP Deployment Page 3-56 Remote AP Deployment Chapter 3: System planning Passing Sync signal Passing Sync in a Single Hop Network sync can be passed in a single hop in the following network designs:

Design 1 o A CMM provides sync to a co-located AP. o This AP sends the sync over the air to SMs. Design 2 o A CMM provides sync to a co-located BH timing master. o This BH timing master sends the sync over the air to a BH timing slave. Passing Sync in an Additional Hop Network sync can be extended by one additional link in any of the following network designs:

Note In each of these following designs, Link 2 is not on the same frequency band as Link 4. (For example, Link 2 may be a 5.2 GHz link while Link 4 is a 5.7 or 2.4 GHz link.) Design 3 o A CMM provides sync to a co-located AP. o This AP sends the sync over the air to an SM. o This SM delivers the sync to a co-located AP. o This AP passes the sync in the additional link over the air to SMs. This design is illustrated in Figure 60. Figure 60 Additional link to extend network sync, Design 3 Design 4 Page 3-57 Remote AP Deployment Chapter 3: System planning o A CMM provides sync to a co-located AP. o This AP sends the sync over the air to an SM. o This SM delivers the sync to a co-located BHM. o This BHM passes the sync in the additional link over the air to a BHS. This design is illustrated in Figure 61. Figure 61 Additional link to extend network sync, Design 4 Page 3-58 Chapter 3: System planning Remote AP Deployment Design 5 o A CMM provides sync to a co-located BHM or the BHM generates timing. o This BHM sends the sync over the air to a BHS. o This BHS delivers the sync to a co-located AP. This AP passes the sync in the additional link over the air to SMs. This design is illustrated in Figure 62. Figure 62 Additional link to extend network sync, Design 5 Wiring and configuration information for this sync extension is described under Wiring to Extend Network Sync on page 3-60. Page 3-59 Chapter 3: System planning Remote AP Deployment Wiring to Extend Network Sync The following procedure can be used to extend network sync by one additional hop, as described under Passing Sync in an Additional Hop on page 3-57. When a co-located module receives sync over the air, the co-located modules can be wired to pass the sync as follows:

1. Connect the GPS Utility ports of the co-located modules using a sync cable with RJ-11 (for 450) or RJ-45 (for 450i/450m) connectors. 2. Set the Sync Input parameter on the Configuration page of the co-located AP or BH timing master to AutoSync. 3. Set the Device Type parameter on the Configuration page of the co-located AP or BH timing master to Remote. 4. Set the Sync Output to Aux Port parameter on the Configuration page of the co-located AP or BH timing master to Disabled. 5. Set the UGPS Power parameter on the Configuration page of the co-located AP or BH timing master to Disabled. 6. Set the Frame Timing Pulse Gated parameter on the Configuration page of the co-located SM or BH timing slave to Enable. Note This setting prevents interference in the event that the SM or BH timing slave loses sync. Figure 63 Co-located AP or BH timing master Sync Setting configuration Page 3-60 Chapter 4: Legal and regulatory information This chapter provides end user license agreements and regulatory notifications. Caution Intentional or unintentional changes or modifications to the equipment must not be made unless under the express consent of the party responsible for compliance. Any such modifications could void the users authority to operate the equipment and will void the manufacturers warranty. Attention Changements ou modifications Intentionnels ou non de l'quipement ne doivent pas tre entrepris sans l'autorisation de lorganisme responsable de la dclaration de conformit. Ces modifications ou changements pourraient invalider le droit de l'utilisateur utiliser cet appareil et annuleraient la garantie du fabricant. The following topics are described in this chapter:

Cambium Networks end user license agreement on page 4-2 contains the Cambium and third party license agreements for the 450 Platform Family ODUs. Compliance with safety standards on page 4-22 lists the safety specifications against which the 450 Platform Family has been tested and certified. It also describes how to keep RF exposure within safe limits. Compliance with radio regulations on page 4-34 describes how the 450 Platform Family complies with the radio regulations that are in force in various countries, and contains notifications made to regulatory bodies for the 450 Platform Family. Page 4-1 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Cambium Networks end user license agreement Definitions In this Agreement, the word Software refers to the set of instructions for computers, in executable form and in any media, (which may include diskette, CD-ROM, downloadable internet, hardware, or firmware) licensed to you. The word Documentation refers to electronic or printed manuals and accompanying instructional aids licensed to you. The word Product refers to Cambium Networks fixed wireless broadband devices for which the Software and Documentation is licensed for use. Acceptance of this agreement In connection with Cambium Networks delivery of certain proprietary software or products containing embedded or pre-loaded proprietary software, or both, Cambium Networks is willing to license this certain proprietary software and the accompanying documentation to you only on the condition that you accept all the terms in this End User License Agreement (Agreement). IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, DO NOT USE THE PRODUCT OR INSTALL THE SOFTWARE. INSTEAD, YOU MAY, FOR A FULL REFUND, RETURN THIS PRODUCT TO THE LOCATION WHERE YOU ACQUIRED IT OR PROVIDE WRITTEN VERIFICATION OF DELETION OF ALL COPIES OF THE SOFTWARE. ANY USE OF THE SOFTWARE, INCLUDING BUT NOT LIMITED TO USE ON THE PRODUCT, WILL CONSTITUTE YOUR ACCEPTANCE TO THE TERMS OF THIS AGREEMENT. Grant of license Cambium Networks Limited (Cambium) grants you (Licensee or you) a personal, nonexclusive, non-

transferable license to use the Software and Documentation subject to the Conditions of Use set forth in Conditions of use and the terms and conditions of this Agreement. Any terms or conditions relating to the Software and Documentation appearing on the face or reverse side of any purchase order, purchase order acknowledgment or other order document that are different from, or in addition to, the terms of this Agreement will not be binding on the parties, even if payment is accepted. Page 4-2 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Conditions of use Any use of the Software and Documentation outside of the conditions set forth in this Agreement is strictly prohibited and will be deemed a breach of this Agreement. 1. Only you, your employees or agents may use the Software and Documentation. You will take all necessary steps to insure that your employees and agents abide by the terms of this Agreement. 2. You will use the Software and Documentation (i) only for your internal business purposes; (ii) only as described in the Software and Documentation; and (iii) in strict accordance with this Agreement. 3. You may use the Software and Documentation, provided that the use is in conformance with the terms set forth in this Agreement. 4. Portions of the Software and Documentation are protected by United States copyright laws, international treaty provisions, and other applicable laws. Therefore, you must treat the Software like any other copyrighted material (for example, a book or musical recording) except that you may either: (i) make 1 copy of the transportable part of the Software (which typically is supplied on diskette, CD-ROM, or downloadable internet), solely for back-up purposes; or (ii) copy the transportable part of the Software to a PC hard disk, provided you keep the original solely for back-up purposes. If the Documentation is in printed form, it may not be copied. If the Documentation is in electronic form, you may print out 1 copy, which then may not be copied. With regard to the copy made for backup or archival purposes, you agree to reproduce any Cambium Networks copyright notice, and other proprietary legends appearing thereon. Such copyright notice(s) may appear in any of several forms, including machine-readable form, and you agree to reproduce such notice in each form in which it appears, to the extent it is physically possible to do so. Unauthorized duplication of the Software or Documentation constitutes copyright infringement, and in the United States is punishable in federal court by fine and imprisonment. 5. You will not transfer, directly or indirectly, any product, technical data or software to any country for which the United States Government requires an export license or other governmental approval without first obtaining such license or approval. Page 4-3 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Title and restrictions If you transfer possession of any copy of the Software and Documentation to another party outside of the terms of this agreement, your license is automatically terminated. Title and copyrights to the Software and Documentation and any copies made by you remain with Cambium Networks and its licensors. You will not, and will not permit others to: (i) modify, translate, decompile, bootleg, reverse engineer, disassemble, or extract the inner workings of the Software or Documentation, (ii) copy the look-and-feel or functionality of the Software or Documentation; (iii) remove any proprietary notices, marks, labels, or logos from the Software or Documentation; (iv) rent or transfer all or some of the Software or Documentation to any other party without Cambiums prior written consent; or (v) utilize any computer software or hardware which is designed to defeat any copy protection device, should the Software and Documentation be equipped with such a protection device. If the Software and Documentation is provided on multiple types of media (such as diskette, CD-ROM, downloadable internet), then you will only use the medium which best meets your specific needs, and will not loan, rent, lease, or transfer the other media contained in the package without Cambiums written consent. Unauthorized copying of the Software or Documentation, or failure to comply with any of the provisions of this Agreement, will result in automatic termination of this license. Confidentiality You acknowledge that all Software and Documentation contain valuable proprietary information and trade secrets and that unauthorized or improper use of the Software and Documentation will result in irreparable harm to Cambium Networks for which monetary damages would be inadequate and for which Cambium Networks will be entitled to immediate injunctive relief. If applicable, you will limit access to the Software and Documentation to those of your employees and agents who need to use the Software and Documentation for your internal business purposes, and you will take appropriate action with those employees and agents to preserve the confidentiality of the Software and Documentation, using the same degree of care to avoid unauthorized or improper disclosure as you use for the protection of your own proprietary software, but in no event less than reasonable care. You have no obligation to preserve the confidentiality of any proprietary information that: (i) was in the public domain at the time of disclosure; (ii) entered the public domain through no fault of yours; (iii) was given to you free of any obligation to keep it confidential; (iv) is independently developed by you; or (v) is disclosed as required by law provided that you notify Cambium Networks prior to such disclosure and provide Cambium Networks with a reasonable opportunity to respond. Page 4-4 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Right to use Cambiums name Except as required in Conditions of use, you will not, during the term of this Agreement or thereafter, use any trademark of Cambium Networks, or any word or symbol likely to be confused with any Cambium Networks trademark, either alone or in any combination with another word or words. Transfer The Software and Documentation may not be transferred to another party without the express written consent of Cambium Networks, regardless of whether or not such transfer is accomplished by physical or electronic means. Cambiums consent may be withheld at its discretion and may be conditioned upon transferee paying all applicable license fees and agreeing to be bound by this Agreement. Updates During the first 12 months after purchase of a Product, or during the term of any executed Maintenance and Support Agreement for the Product, you are entitled to receive Updates. An Update means any code in any form which is a bug fix, patch, error correction, or minor enhancement, but excludes any major feature added to the Software. Updates are available for download at the support website. Major features may be available from time to time for an additional license fee. If Cambium Networks makes available to you major features and no other end user license agreement is provided, then the terms of this Agreement will apply. Maintenance Except as provided above, Cambium Networks is not responsible for maintenance or field service of the Software under this Agreement. Page 4-5 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Disclaimer CAMBIUM NETWORKS DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY, OR IN ANY COMMUNICATION WITH YOU. CAMBIUM NETWORKS SPECIFICALLY DISCLAIMS ANY WARRANTY INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILTY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED AS IS. CAMBIUM NETWORKS DOES NOT WARRANT THAT THE SOFTWARE WILL MEET YOUR REQUIREMENTS, OR THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR FREE, OR THAT DEFECTS IN THE SOFTWARE WILL BE CORRECTED. CAMBIUM NETWORKS MAKES NO WARRANTY WITH RESPECT TO THE CORRECTNESS, ACCURACY, OR RELIABILITY OF THE SOFTWARE AND DOCUMENTATION. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. Limitation of liability IN NO EVENT SHALL CAMBIUM NETWORKS BE LIABLE TO YOU OR ANY OTHER PARTY FOR ANY DIRECT, INDIRECT, GENERAL, SPECIAL, INCIDENTAL, CONSEQUENTIAL, EXEMPLARY OR OTHER DAMAGE ARISING OUT OF THE USE OR INABILITY TO USE THE PRODUCT (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION OR ANY OTHER PECUNIARY LOSS, OR FROM ANY BREACH OF WARRANTY, EVEN IF CAMBIUM NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. (Some states do not allow the exclusion or limitation of incidental or consequential damages, so the above exclusion or limitation may not apply to you.) IN NO CASE SHALL CAMBIUMS LIABILITY EXCEED THE AMOUNT YOU PAID FOR THE PRODUCT. U.S. government If you are acquiring the Product on behalf of any unit or agency of the U.S. Government, the following applies. Use, duplication, or disclosure of the Software and Documentation is subject to the restrictions set forth in subparagraphs (c) (1) and (2) of the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 (JUNE 1987), if applicable, unless being provided to the Department of Defense. If being provided to the Department of Defense, use, duplication, or disclosure of the Products is subject to the restricted rights set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 (OCT 1988), if applicable. Software and Documentation may or may not include a Restricted Rights notice, or other notice referring specifically to the terms and conditions of this Agreement. The terms and conditions of this Agreement will each continue to apply, but only to the extent that such terms and conditions are not inconsistent with the rights provided to you under the aforementioned provisions of the FAR and DFARS, as applicable to the particular procuring agency and procurement transaction. Page 4-6 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Term of license Your right to use the Software will continue in perpetuity unless terminated as follows. Your right to use the Software will terminate immediately without notice upon a breach of this Agreement by you. Within 30 days after termination of this Agreement, you will certify to Cambium Networks in writing that through your best efforts, and to the best of your knowledge, the original and all copies, in whole or in part, in any form, of the Software and all related material and Documentation, have been destroyed, except that, with prior written consent from Cambium Networks, you may retain one copy for archival or backup purposes. You may not sublicense, assign or transfer the license or the Product, except as expressly provided in this Agreement. Any attempt to otherwise sublicense, assign or transfer any of the rights, duties or obligations hereunder is null and void. Governing law This Agreement is governed by the laws of the United States of America to the extent that they apply and otherwise by the laws of the State of Illinois. Assignment This agreement may not be assigned by you without Cambiums prior written consent. Survival of provisions The parties agree that where the context of any provision indicates an intent that it survives the term of this Agreement, then it will survive. Entire agreement This agreement contains the parties entire agreement regarding your use of the Software and may be amended only in writing signed by both parties, except that Cambium Networks may modify this Agreement as necessary to comply with applicable laws. Third party software The software may contain one or more items of Third-Party Software supplied by other third-party suppliers. The terms of this Agreement govern your use of any Third-Party Software UNLESS A SEPARATE THIRD-PARTY SOFTWARE LICENSE IS INCLUDED, IN WHICH CASE YOUR USE OF THE THIRD-PARTY SOFTWARE WILL THEN BE GOVERNED BY THE SEPARATE THIRD-PARTY LICENSE. Page 4-7 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Net SNMP Various copyrights apply to this package, listed in various separate parts below. Please make sure that you read all the parts.

---- Part 1: CMU/UCD copyright notice: (BSD like) -----

Copyright 1989, 1991, 1992 by Carnegie Mellon University Derivative Work - 1996, 1998-2000 Copyright 1996, 1998-2000 The Regents of the University of California All Rights Reserved Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission. CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

---- Part 2: Networks Associates Technology, Inc copyright notice (BSD) -----

Copyright 2001-2003, Networks Associates Technology, Inc All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the Networks Associates Technology, Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. Page 4-8 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) -----

Portions of this code are copyright 2001-2003, Cambridge Broadband Ltd. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

---- Part 4: Sun Microsystems, Inc. copyright notice (BSD) -----

Copyright 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Use is subject to license terms below. This distribution may include materials developed by third parties. Sun, Sun Microsystems, the Sun logo and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Page 4-9 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the Sun Microsystems, Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

---- Part 5: Sparta, Inc copyright notice (BSD) -----

Copyright 2003-2008, Sparta, Inc All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of Sparta, Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

---- Part 6: Cisco/BUPTNIC copyright notice (BSD) -----

Copyright 2004, Cisco, Inc and Information Network Center of Beijing University of Posts and Telecommunications. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Page 4-10 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of Cisco, Inc, Beijing University of Posts and Telecommunications, nor the names of their contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

---- Part 7: Fabasoft R&D Software GmbH & Co KG copyright notice (BSD) -----

Copyright Fabasoft R&D Software GmbH & Co KG, 2003 oss@fabasoft.com Author: Bernhard Penz Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. The name of Fabasoft R&D Software GmbH & Co KG or any of its subsidiaries, brand or product names may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. OpenSSL Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved. Page 4-11 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgment:

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit.

(http://www.openssl.org/) 4. The names OpenSSL Toolkit and OpenSSL Project must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org. 5. Products derived from this software may not be called OpenSSL nor may OpenSSL appear in their names without prior written permission of the OpenSSL Project. 6. Redistributions of any form whatsoever must retain the following acknowledgment:

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit

(http://www.openssl.org/) THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com). Original SSLeay License Copyright 1995-1998 Eric Young (eay@cryptsoft.com) All rights reserved. This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was written so as to conform with Netscapes SSL. This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com). Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. Page 4-12 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation

(online or textual) provided with the package. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com) The word cryptographic can be left out if the routines from the library being used are not cryptographic related. 4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement:

This product includes software written by Tim Hudson (tjh@cryptsoft.com) THIS SOFTWARE IS PROVIDED BY ERIC YOUNG AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The license and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License.]

Zlib Copyright 1995-2005 Jean-loup Gailly and Mark Adler This software is provided as-is, without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. Page 4-13 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement 3. This notice may not be removed or altered from any source distribution. Jean-loup Gailly jloup@gzip.org Mark Adler madler@alumni.caltech.edu Libpng libpng versions 1.2.6, August 15, 2004, through 1.2.35, February 14, 2009, are Copyright 2004, 2006-

2008 Glenn Randers-Pehrson, and are distributed according to the same disclaimer and license as libpng-1.2.5 with the following individual added to the list of Contributing Authors Cosmin Truta libpng versions 1.0.7, July 1, 2000, through 1.2.5 - October 3, 2002, are Copyright 2000-2002 Glenn Randers-Pehrson, and are distributed according to the same disclaimer and license as libpng-1.0.6 with the following individuals added to the list of Contributing Authors Simon-Pierre Cadieux Eric S. Raymond Gilles Vollant and with the following additions to the disclaimer:

There is no warranty against interference with your enjoyment of the library or against infringement. There is no warranty that our efforts or the library will fulfil any of your particular purposes or needs. This library is provided with all faults, and the entire risk of satisfactory quality, performance, accuracy, and effort is with the user. libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, are Copyright 1998, 1999 Glenn Randers-Pehrson, and are distributed according to the same disclaimer and license as libpng-0.96, with the following individuals added to the list of Contributing Authors:

Tom Lane Glenn Randers-Pehrson Willem van Schaik libpng versions 0.89, June 1996, through 0.96, May 1997, are Copyright 1996, 1997 Andreas Dilger Distributed according to the same disclaimer and license as libpng-0.88, with the following individuals added to the list of Contributing Authors:

John Bowler Kevin Bracey Sam Bushell Magnus Holmgren Greg Roelofs Tom Tanner libpng versions 0.5, May 1995, through 0.88, January 1996, are Copyright 1995, 1996 Guy Eric Schalnat, Group 42, Inc. For the purposes of this copyright and license, Contributing Authors is defined as the following set of individuals:

Page 4-14 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Andreas Dilger Dave Martindale Guy Eric Schalnat Paul Schmidt Tim Wegner The PNG Reference Library is supplied AS IS. The Contributing Authors and Group 42, Inc. disclaim all warranties, expressed or implied, including, without limitation, the warranties of merchantability and of fitness for any purpose. The Contributing Authors and Group 42, Inc. assume no liability for direct, indirect, incidental, special, exemplary, or consequential damages, which may result from the use of the PNG Reference Library, even if advised of the possibility of such damage. Permission is hereby granted to use, copy, modify, and distribute this source code, or portions hereof, for any purpose, without fee, subject to the following restrictions:

1. The origin of this source code must not be misrepresented. 2. Altered versions must be plainly marked as such and must not be misrepresented as being the original source. 3. This Copyright notice may not be removed or altered from any source or altered source distribution. The Contributing Authors and Group 42, Inc. specifically permit, without fee, and encourage the use of this source code as a component to supporting the PNG file format in commercial products. If you use this source code in a product, acknowledgment is not required but would be appreciated. A png_get_copyright function is available, for convenient use in about boxes and the like:

printf("%s",png_get_copyright(NULL));

Also, the PNG logo (in PNG format, of course) is supplied in the files "pngbar.png" and "pngbar.jpg

(88x31) and "pngnow.png" (98x31). Libpng is OSI Certified Open Source Software. OSI Certified Open Source is a certification mark of the Open Source Initiative. Glenn Randers-Pehrson glennrp at users.sourceforge.net February 14, 2009 Bzip2 This program, "bzip2", the associated library "libbzip2", and all documentation, are copyright (C) 1996-

2007 Julian R Seward. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 3. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. Page 4-15 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement 4. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Julian Seward, jseward@bzip.org USB library functions Atmel Corporation 2325 Orchard Parkway San Jose, Ca 95131 Copyright (c) 2004 Atmel Page 4-16 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement Apache Apache License Version 2.0, January 2004 http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition,

"control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work

(an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted"

means any form of electronic, verbal, or written communication sent Page 4-17 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable

(except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed Page 4-18 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this Page 4-19 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]"

replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License");

you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Page 4-20 Chapter 4: Legal and regulatory information Cambium Networks end user license agreement D3 JS library Copyright (c) 2013, Michael Bostock All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

* The name Michael Bostock may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"

AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL MICHAEL BOSTOCK BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE Page 4-21 Chapter 4: Legal and regulatory information Compliance with safety standards Compliance with safety standards This section lists the safety specifications against which the 450 Platform Family has been tested and certified. It also describes how to keep RF exposure within safe limits. Electrical safety compliance The 450 Platform Family hardware has been tested for compliance to the electrical safety specifications listed in Table 85. Table 85 Safety compliance specifications Region USA Canada International Specification UL 60950 CSA C22.2 No.60950 CB certified & certificate to IEC 60950 Electromagnetic compatibility (EMC) compliance The EMC specification type approvals that have been granted for 450 Platform Family are listed under Table 86. Table 86 EMC emissions compliance Region USA Canada International Specification FCC Part 15 Class B RSS Gen and RSS 210 EN 301 489-1 V1.9.2 EN 301 489-17 V2.1.1 Human exposure to radio frequency energy Relevant standards (USA and EC) applicable when working with RF equipment are:

ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz. Council recommendation of 12 July 1999 on the limitation of exposure of the general public to electromagnetic fields (0 Hz to 300 GHz) (1999/519/EC) and respective national regulations. Page 4-22 Chapter 4: Legal and regulatory information Compliance with safety standards Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 on the minimum health and safety requirements regarding the exposure of workers to the risks arising from physical agents (electromagnetic fields) (18th individual Directive within the meaning of Article 16(1) of Directive 89/391/EEC). US FCC limits for the general population. See the FCC web site at http://www.fcc.gov, and the policies, guidelines, and requirements in Part 1 of Title 47 of the Code of Federal Regulations, as well as the guidelines and suggestions for evaluating compliance in FCC OET Bulletin 65. Health Canada limits for the general population. See the Health Canada web site at http://www.hc-

sc.gc.ca/ewh-semt/pubs/radiation/99ehd-dhm237/limits-limites_e.html and Safety Code 6. EN 50383:2002 to 2010 Basic standard for the calculation and measurement of electromagnetic field strength and SAR related to human exposure from radio base stations and fixed terminal stations for wireless telecommunication systems (110 MHz - 40 GHz). BS EN 50385:2002 Product standard to demonstrate the compliances of radio base stations and fixed terminal stations for wireless telecommunication systems with the basic restrictions or the reference levels related to human exposure to radio frequency electromagnetic fields (110 MHz 40 GHz) general public. ICNIRP (International Commission on Non-Ionizing Radiation Protection) guidelines for the general public. See the ICNIRP web site at http://www.icnirp.de/ and Guidelines for Limiting Exposure to Time-Varying Electric, Magnetic, and Electromagnetic Fields. Power density exposure limit Install the radios for the 450 Platform Family of wireless solutions so as to provide and maintain the minimum separation distances from all persons. The applicable FCC power density exposure limit for RF energy in the 4.9, 5.4 and 5.8 GHz frequency bands is 10 W/m2 and in 900 MHz frequency band is 6 W/m2. For more information, see Human exposure to radio frequency energy on page 4-22. The applicable ISEDC power density exposure limit for RF energy in unlicensed bands is 0.02619 *

(f^(0.6834)), where f is the lowest frequency of the supported band. For licensed bands, the power density exposure limit is 0.6455 * (f^(0.5)), where f is the lowest frequency of the supported band. Page 4-23 Chapter 4: Legal and regulatory information Compliance with safety standards Calculation of power density The following calculation is based on the ANSI IEEE C95.1-1991 method, as that provides a worst case analysis. Details of the assessment to EN50383:2002 can be provided, if required. Peak power density in the far field of a radio frequency point source is calculated as follows:

S

. GP 4 d 2 Where:

S P G d Is:

power density in W/m2 maximum average transmit power capability of the radio, in W total Tx gain as a factor, converted from dB distance from point source, in m d

. GP

.4 S Rearranging terms to solve for distance yields:

Calculated distances and power compliance margins Table 88 and Table 89 shows calculated minimum separation distances, recommended distances and resulting margins for each frequency band and antenna combination for the USA and Canada. These are conservative distances that include compliance margins. At these and greater separation distances, the power density from the RF field is below generally accepted limits for the general population. 450 Platform Family ODU adheres to all applicable EIRP limits for transmit power when operating in MIMO mode. Separation distances and compliance margins include compensation for both transmitters. Explanation of terms used in Table 88 and Table 89:

P burst maximum average transmit power during transmit burst (Watt) P maximum average transmit power of the radio (Watt) G total transmit gain as a factor, converted from dB S power density (Watt/m2) d minimum safe separation distance from point source (meters) Page 4-24 Chapter 4: Legal and regulatory information Compliance with safety standards Table 87 FCC minimum safe distances PMP 450m 5.1 GHz, 5.2 GHz, 5.4 GHz and 5.8 GHz Band

(GHz) 5.1 5.2 5.4 5.8 Antenna 90 sector 90 sector 90 sector 90 sector PG (W) S (W/ m2) d (m) 3.38 0.85 0.85 3.38 10 10 10 10 0.16 0.08 0.08 0.16 Page 4-25 Chapter 4: Legal and regulatory information Compliance with safety standards Table 88 FCC minimum safe distances PMP/PTP 450i 900 MHz, 3.65 GHz, 4.9 GHz, 5.1 GHz, 5.2 GHz, 5.4 GHz and 5.8 GHz Band Antenna P burst

(W) P

(W) G

(dBi) S

(W/ m2) d

(m) 0.19 22.75 (13 dBi) 6.0 0.27 0.316 50.0 (17 dBi) 10.0 0.36 900 MHz 3.65 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz Sector antenna 90 sector antenna, integrated 90 sector antenna, connectorized Panel, integrated Omni-directional

-

-

-

0.316 40.0 (16 dBi)

-

0.2138 0.251 0.2512 79.0 (19 dBi) 20.0 (13 dBi) 90 sector antenna 0.2138 0.2512 50.0 (17 dBi) 2ft directional flat plate 4ft directional parabolic 6ft directional parabolic Omni-directional 90 sector 2ft directional flat plate 4ft directional parabolic Omni-directional 90 sector 2ft directional flat plate 4ft directional parabolic Omni-directional 90 sector 2ft directional flat plate 2ft directional parabolic Omni-directional 90 sector 2ft directional flat plate 4ft directional parabolic 6ft directional parabolic 631.0 (28 dBi) 2344.0 (34.9 dBi) 5248.0 (37.2 dBi) 20.0 (13.0 dBi) 50.1 (17.0 dBi) 707.9 (28.5 dBi) 2818.4 (34.5 dBi) 20.0 (13.0 dBi) 50.1 (17.0 dBi) 707.9 (28.5 dBi) 2818.4 (34.5 dBi) 20.0 (13.0 dBi) 50.1 (17.0 dBi) 707.9 (28.5 dBi) 707.9 (28.5 dBi) 20.0 (13 dBi) 50.0 (17 dBi) 708.0 (28.5 dBi) 3388.0 (35.3 dBi) 6457.0 (38.1 dBi) 0.2138 0.851 0.1413 0.170 0.034 0.2512 0.1000 0.1659 0.200 0.040 0.002 0.011 0.036 0.014 0.001 0.000 0.036 0.014 0.001 0.001 0.24 0.10 0.54 0.54 0.54 0.002 0.013 0.042 0.017 0.001 0.000 0.042 0.017 0.001 0.001 0.28 0.12 0.63 0.63 0.63 Page 4-26 10.0 10.0 10.0 10.0 10.0 10.0 10.0 10 10 10 10 10 10 10 10 10 10 10 10 10.0 10.0 10.0 10.0 10.0 0.32 0.40 0.17 0.26 0.93 1.14 2.19 0.15 0.10 0.09 0.44 0.07 0.07 0.07 0.06 0.07 0.07 0.07 0.08 0.18 0.18 1.57 3.43 4.74 Chapter 4: Legal and regulatory information Compliance with safety standards Table 89 ISEDC minimum safe distances PMP/PTP 450i, 900 MHz, 3.5 GHz, 3.65 GHz, 4.9 GHz, 5.2 GHz, 5.4 GHz, and 5.8 GHz Band Antenna 900 MHz Sector 90 sector antenna, integrated 90 sector antenna, connectorized Panel, integrated 90 sector antenna, integrated 90 sector antenna, connectorized Panel, integrated 90 sector antenna, integrated 90 sector antenna, connectorized Panel, integrated Omni-directional 90 sector 2ft directional flat plate 6ft directional parabolic Omni-directional 90 sector 2ft directional flat plate 2ft directional parabolic 3.5 GHz 3.65 GHz

(Lower Canada) 3.65 GHz

(Upper Canada) 4.9 GHz 5.2 GHz P burst

(W)

-

-

-

-

-

-

-

-

-

P

(W)

.02 G

(dBi) S

(W/ m2) d

(m) 20.0 (13 dBi) 2.74 0.11 0.794 50.0 (17 dBi) 37.10 0.29 40.0 (16 dBi) 37.10 0.23 79.0 (19 dBi) 37.10 0.37 0.794 0.794 0.794 0.794 50.0 (17 dBi) 40.0 (16 dBi) 0.794 79.0 (19 dBi) 0.316 50.0 (17 dBi) 0.316 40.0 (16 dBi) 7.13 7.13 7.13 7.13 7.13 7.13 8.71 8.71 8.71 8.71 9.13 9.13 9.13 9.13 0.67 0.59 0.84 0.42 0.37 0.47 0.20 0.31 1.11 2.60 0.04 0.06 0.07 0.06

-

0.214 0.214 0.214 0.141 0.009 0.012 0.001 0.001 0.251 0.251 0.251 0.251 0.166 0.011 0.014 0.001 0.001 79.0 (19 dBi) 20.0 (13 dBi) 50.1 (17 dBi) 631.0 (28 dBi) 5248.0 (37.2 dBi) 20.0 (13.0 dBi) 50.1 (17.0 dBi) 707.9 (28.5 dBi) 707.9 (28.5 dBi) Page 4-27 Chapter 4: Legal and regulatory information Compliance with safety standards Band Antenna 5.4 GHz 5.8 GHz Omni-directional 90 sector 2ft directional flat plate 2ft directional parabolic Omni-directional 90 sector 2ft directional flat plate 4ft directional parabolic P burst

(W) 0.036 0.014 0.001 0.001 0.24 0.10 0.54 0.54 P

(W) 0.042 0.017 0.001 0.001 0.28 0.12 0.63 0.63 G

(dBi) 20.0 (13.0 dBi) 50.1 (17.0 dBi) 707.9 (28.5 dBi) 707.9 (28.5 dBi) 20.0 (13 dBi) 50.1 (17 dBi) 707.9 (28.5 dBi) 3388.4 (35.3 dBi) S

(W/ m2) 9.39 9.39 9.39 9.39 9.69 9.69 9.69 9.69 d

(m) 0.07 0.07 0.07 0.06 0.20 0.20 1.67 4.82 Page 4-28 Chapter 4: Legal and regulatory information Compliance with safety standards Table 90 FCC minimum safe distances PMP/PTP 450 900 MHz, 2.4 GHz, 3.65 GHz and 5 GHz Band Antenna 900 MHz Yagi 2.4 GHz 3.65 GHz Sector Antenna Integrated Reflector Sector Antenna Integrated Reflector High-gain Ruggedized Sector Integrated Reflector CLIP 5.4 GHz LENS Integrated Dish (450d) Sector 5.8 GHz Integrated Reflector CLIP LENS Integrated Dish (450d) P burst

(W) 0.032 0.079 0.158 0.040 0.316 0.316 0.25 0.25 0.025 0.126 0.003 0.020 0.032 0.0032 0.079 0.158 0.158 0.158 0.158 0.158 G

(dBi) 13 (11 dBi) 50 (17 dBi) 6 (8 dBi) 100 (20 dBi) 32 (15 dBi) 6 (8 dBi) 100 (20 dBi) 79 (19 dBi) 40 (16 dBi) 8 (9 dBi) 316 (25 dBi) 50 (17 dBi) 28 (14.5 dBi) 316 (25 dBi) 40 (16 dBi) 8 (9 dBi) 316 (25 dBi) 50 (17 dBi) 28 (14.5 dBi) 316 (25 dBi) S

(W/ m2) 6 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 d

(m) 0.07 0.18 0.09 0.18 0.28 0.12 0.45 0.40 0.09 0.09 0.09 0.09 0.08 0.09 0.16 0.10 0.63 0.25 0.19 0.63 Page 4-29 Chapter 4: Legal and regulatory information Compliance with safety standards Table 91 ISEDC minimum safe distances PMP/PTP 450 900 MHz, 2.4 GHz, 3.5/3.65 GHz and 5 GHz Band Antenna 900 MHz Yagi 2.4 GHz Sector Antenna Integrated Reflector Sector Integrated Reflector High-gain Ruggedized Sector Integrated Reflector High-gain Ruggedized Sector Integrated Reflector High-gain Ruggedized Sector Integrated Reflector CLIP LENS Integrated Dish (450d) Sector Integrated Reflector CLIP LENS Integrated Dish (450d) 3.5 GHz 3.65 GHz

(lower Canada) 3.65 GHz

(upper Canada) 5.4 GHz 5.8 GHz P burst

(W) 0.316 0.079 0.158 0.040 0.316 0.316 0.316 0.316 0.316 0.316 0.316 0.316 0.316 0.316 0.20 0.003 0.025 0.126 0.003 0.020 0.032 0.0032

.079 0.158 0.158 0.158 0.158 0.158 G

(dBi) 13 (11 dBi) 50 (17 dBi) 6 (8 dBi) 100 (20 dBi) 32 (15 dBi) 6 (8 dBi) 100 (20 dBi) 79 (19 dBi) 32 (15 dBi) 6 (8 dBi) 100 (20 dBi) 79 (19 dBi) 32 (15 dBi) 6 (8 dBi) 100 (20 dBi) 79 (19 dBi) 40 (16 dBi) 8 (9 dBi) 316 (25 dBi) 50 (17 dBi) 28 (14.5 dBi) 316 (25 dBi) 40 (16 dBi) 8 (9 dBi) 316 (25 dBi) 50 (17 dBi) 28 (14.5 dBi) 316 (25 dBi) S

(W/ m2) 2.74 5.35 5.35 5.35 37.10 37.10 37.10 37.10 38.20 38.20 38.20 38.20 38.20 38.20 38.20 38.20 9.39 9.39 9.39 9.39 9.39 9.39 9.69 9.69 9.69 9.69 9.69 9.69 d

(m) 0.35 0.24 0.12 0.24 0.15 0.06 0.26 0.23 0.15 0.06 0.26 0.23 0.14 0.06 0.20 0.23 0.09 0.09 0.09 0.09 0.09 0.09 0.16 0.10 0.064 0.25 0.19 0.64 Page 4-30 Chapter 4: Legal and regulatory information Compliance with safety standards

(*1) P: maximum average transmit power capability of the radio including cable loss (Watt) Capacit de puissance d'mission moyenne maximale de la radio comprenant la perte dans les cble de connexion (W)

(*2) G: total transmit gain as a factor, converted from dB Gain total d'mission, converti partir de la valeur en dB

(*3) S: power density (W/m2) Densit de puissance (W/m2)

(*4) d: minimum distance from point source (meters) Distance minimale de source ponctuelle (en mtres) Page 4-31 Chapter 4: Legal and regulatory information Compliance with safety standards Note Gain of antenna in dBi = 10 * log(G). The regulations require that the power used for the calculations is the maximum power in the transmit burst subject to allowance for source-based time-averaging. At 5.4 GHz and EU 5.8 GHz, the products are generally limited to a fixed EIRP which can be achieved with the Integrated Antenna. The calculations above assume that the maximum EIRP allowed by the regulations is being transmitted. Remarque Gain de l'antenne en dBi = 10 * log(G). Les rglements exigent que la puissance utilise pour les calculs soit la puissance maximale de la rafale de transmission soumis une rduction pour prendre en compte le rapport cyclique pour les signaux moduls dans le temps. Pour une opration dans la CEE dans les bandes 5,4 GHz et 5,8 GHz, les produits sont gnralement limits une PIRE qui peut tre atteinte avec l'antenne intgre. Les calculs ci-dessus supposent que la PIRE maximale autorise par la rglementation est atteinte. Note If there are no EIRP limits in the country of deployment, use the distance calculations for FCC 5.8 GHz for all frequency bands. At FCC 5.8 GHz, for antennas between 0.6m (2ft) and 1.8m (6ft), alter the distance proportionally to the antenna gain. Remarque Si aucune limite de PIRE existe pour le pays de dploiement, utilisez les calculs de distance pour FCC 5,8 GHz pour toutes les bandes de frquence. Pour la band FCC 5,8 GHz et les antennes entre 0,6 m (2 pieds) et 1,8 m (6 pieds), modifier la distance proportionnellement au gain de l'antenne. Hazardous location compliance The PMP/PTP 450i series ATEX/HAZLOC ODUs have been certified for operation in the following hazardous locations:

ATEX The products have been approved under an Intrinsic Safety assessment as defined in EN60079-

11:2007. The approval is given by certificate number TRAC09ATEX31224X, issued by TRaC Global, with the specific level of coverage shown below:

3 - Equipment category (infrequent exposure) II 3 G Ex ic IIC T4 II - Equipment group (surface applications) Page 4-32 Chapter 4: Legal and regulatory information Compliance with safety standards ic - Protection concept (intrinsic safety) IIC - Gas group (up to and including Hydrogen and Acetylene) G - Atmosphere (Gas) T4 - Temperature class (135C) Page 4-33 Chapter 4: Legal and regulatory information Compliance with radio regulations Compliance with radio regulations This section describes how the 450 Platform Family complies with the radio regulations that are in force in various countries. Caution Where necessary, the end user is responsible for obtaining any National licenses required to operate this product and these must be obtained before using the product in any particular country. Contact the appropriate national administrations for details of the conditions of use for the bands in question and any exceptions that might apply. Caution Changes or modifications not expressly approved by Cambium Networks could void the users authority to operate the system. Caution For the connectorized version of the product and in order to reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the Effective Isotropically Radiated Power (EIRP) is not more than that permitted for successful communication. Attention Le cas chant, l'utilisateur final est responsable de l'obtention des licences nationales ncessaires pour faire fonctionner ce produit. Celles-ci doivent tre obtenus avant d'utiliser le produit dans un pays particulier. Contactez les administrations nationales concernes pour les dtails des conditions d'utilisation des bandes en question, et toutes les exceptions qui pourraient s'appliquer Attention Les changements ou modifications non expressment approuvs par les rseaux de Cambium pourraient annuler l'autorit de l'utilisateur faire fonctionner le systme. Attention Pour la version du produit avec une antenne externe, et afin de rduire le risque d'interfrence avec d'autres utilisateurs, le type d'antenne et son gain doivent tre choisis afin que la puissance isotrope rayonne quivalente (PIRE) ne soit pas suprieure au minimum ncessaire pour tablir une liaison de la qualit requise. Page 4-34 Chapter 4: Legal and regulatory information Compliance with radio regulations Type approvals This system has achieved Type Approval in various countries around the world. This means that the system has been tested against various local technical regulations and found to comply. The frequency bands in which the system operates may be unlicensed and, in these bands, the system can be used provided it does not cause interference. The system is not guaranteed protection against interference from other products and installations. The radio specification type approvals that have been granted for 450 Platform Family frequency variants are listed under Table 92. Table 92 Radio certifications Region/Country Band Brazil 4.9 GHz 5.4 GHz 5.8 GHz 900 MHz 4.9 GHz 5.4 GHz 5.8 GHz 900 MHz 2.4 GHz 3.6 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 900 MHz 2.4 GHz 3.5 /3.6 GHz 4.9 GHz 5.8 GHz 3.5 GHz Mexico USA Canada Europe Specification ANATEL, RESOLUO N 633, DE 14 DE MARO DE 2014 ANATEL, RESOLUTION No. 506, FROM JULY 1, 2008 ANATEL, RESOLUTION No. 506, FROM JULY 1, 2008 NOM-121-SCT1-2009 Protocol Between the UNITED STATES OF AMERICA and MEXICO Use of 4940 to 4990 MHz band. Acuerdo del 27 de noviembre de 2012 NOM-121-SCT1-2009 FCC Part 15.247 FCC Part 15 Class B FCC Part 15 Class B FCC 47 CFR Part 90 FCC 47 CFR Part 15 E FCC 47 CFR Part 15 E FCC 47 CFR Part 15 E FCC 47 CFR Part 15 C RSS Gen and RSS 210 RSS Gen and RSS 210 RSS Gen and RSS 192 IC RSS-111, Issue 5 IC RSS-247, Issue 1 ETSI EN 302 326-2 V1.2.2 Page 4-35 Chapter 4: Legal and regulatory information Compliance with radio regulations 4.9 GHz 5.4 GHz 5.8 GHz ETSI EN302 625; V1.1.1 Broadband Disaster Relief ETSI EN 301 893 V1.8.1 ETSI EN 302 502 V2.1.1 Brazil specific information Brazil notification For compliant operation in the 5.4 GHz band, the Equivalent Isotropic Radiated Power from the integrated antenna or connectorized antenna shall not exceed 30 dBm (0.5 W). The operator is responsible for enabling the DFS feature on any Canopy 5.4 GHz radio by setting the Country Code to Brazil, including after the module is reset to factory defaults. Important Note: This equipment operates as a secondary application, so it has no rights against harmful interference, even if generated by similar equipment, and cannot cause harmful interference on systems operating as primary applications. Brazil certification numbers The Anatel certification number for Brazil for the PMP/PTP 450i Series is 2426-15-7745. Australia Notification 900 MHz modules must be set to transmit and receive only on center channels of 920, 922, or 923 MHz so as to stay within the ACMA approved band of 915 MHz to 928 MHz for the class license and not interfere with other approved users. After taking into account antenna gain (in dBi), 900 MHz modules transmitter output power (in dBm) must be set to stay within the legal regulatory limit of 30 dBm (1 W) EIRP for this 900 MHz frequency band. Regulatory Requirements for CEPT Member States

(www.cept.org) When operated in accordance with the instructions for use, Cambium Wireless equipment operating in the 5.1 GHz and 5.4 GHz bands is compliant with CEPT Resolution 229 (REV. WRC-12). Operating the 450 Platform Family in the bands 5150 to 5350 MHz and 5470 to 5725 MHz is granted providing it is not causing interference to the existing primary services allocated to those bands. For compliant operation in the 5250 to 5350 MHz band, the transmit power from the integrated antenna or a connectorized antenna shall be limited to a maximum mean EIRP of 200 mW and a maximum mean EIRP density of 10 mW/MHz in any 1 MHz band. For compliant operation in the 5470 to 5725 MHz band, the transmit power shall be restricted to a maximum of 250 mW with a maximum mean EIRP of 1 W and a maximum mean EIRP density of 50 mW/MHz in any 1 MHz band. Page 4-36 Chapter 4: Legal and regulatory information Compliance with radio regulations For compliant operation in the bands 5 250-5 350 MHz and 5 470-5 725 MHz, the 450 Platform Family employs transmitter power control. For EU member states, RLAN equipment in the 5.4GHz bands is exempt from individual licensing under Commission Recommendation 2003/203/EC. Contact the appropriate national administrations for details on the conditions of use for the bands in question and any exceptions that might apply. Also see www.ero.dk for further information. Cambium Radio equipment operating in the 5470 to 5725 MHz band are categorized as Class 1 devices within the EU in accordance with ECC DEC(04)08 and are CE marked to show compliance with the European Radio & Telecommunications Terminal Equipment (R&TTE) directive 1999/5/EC. The relevant Declaration of Conformity can be found at http://www.cambiumnetworks.com/support/ec_doc/ . A European Commission decision, implemented by Member States on 31 October 2005, makes the frequency band 5470-5725 MHz available in all EU Member States for wireless access systems. Under this decision, the designation of Canopy 5.4GHz products become Class 1 devices and these do not require notification under article 6, section 4 of the R&TTE Directive. Consequently, these 5.4GHz products are only marked with the symbol and may be used in any member state. Page 4-37 Chapter 5: Preparing for installation This chapter describes how to stage and test the hardware for a 450 Platform network. This chapter is arranged as follows:

Safety on page 5-2: Describes the precautions to be observed and checks to be performed before proceeding with the installation Preparing for installation on page 5-5: Describes the pre-configuration procedure before proceed with installation. Testing system components on page 5-7: Describes the procedures for unpacking and performing and initial staging of the 450 Platform Family ODU. Configuring Link for Test on page 5-16: Describes the procedures for testing the equipments radio links. Page 5-1 Chapter 5: Preparing for installation Safety Safety Warning To prevent loss of life or physical injury, observe the following safety guidelines. In no event shall Cambium Networks be liable for any injury or damage caused during the installation of the Cambium 450 Platform Family. Ensure that only qualified personnel install a 450 Platform link. Hazardous locations Warning When installing the PMP/PTP 450i ATEX/HAZLOC product variants in hazardous locations, follow the instructions contained in the PMP/PTP 450i Series Hazardous Location Guide

(supplied in box with the products), in addition to the instructions in this user guide. Power lines Exercise extreme care when working near power lines. Working at heights Exercise extreme care when working at heights. Power supply Always use one of the Cambium 450 Platform Family power supply units (PSU) to power the ODU. Failure to use a Cambium supplied PoE could result in equipment damage and will invalidate the safety certification and may cause a safety hazard. Grounding and protective earth The Outdoor Unit (ODU) must be properly grounded to protect against lightning. It is the users responsibility to install the equipment in accordance with national regulations. In the USA follow the requirements of the National Electrical code NFPA 70-2005 and 780-2004 Installation of Lightning Protection Systems. In Canada, follow Section 54 of the Canadian Electrical Code. 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. Page 5-2 Safety Chapter 5: Preparing for installation Powering down before servicing Always power down and unplug the equipment before servicing. Primary disconnect device The ODU power supply is the primary disconnect device. External cables Safety may be compromised if outdoor rated cables are not used for connections that will be exposed to the outdoor environment. For outdoor copper Cat5e Ethernet interfaces, always use Cat5e cable that is gel-filled and shielded with copper-plated steel. RF exposure near the antenna Strong radio frequency (RF) fields will be present close to the antenna when the transmitter is on. Always turn off the power to the ODU before undertaking maintenance activities in front of the antenna. Minimum separation distances Ensure that personnel are not exposed to unsafe levels of RF energy. The units start to radiate RF energy as soon as they are powered up. Never work in front of the antenna when the ODU is powered. Install the ODUs so as to provide and maintain the minimum separation distances from all persons. For minimum separation distances, see Calculated distances and power compliance margins on page 4-24. Grounding and lightning protection requirements Ensure that the installation meets the requirements defined in Grounding and lightning protection on page 3-8. Grounding cable installation methods To provide effective protection against lightning induced surges, observe these requirements:

Grounding conductor runs are as short, straight and smooth as possible, with bends and curves kept to a minimum. Grounding cables must not be installed with drip loops. Page 5-3 Chapter 5: Preparing for installation Safety All bends must have a minimum radius of 200 mm (8 in) and a minimum angle of 90. A diagonal run is preferable to a bend, even though it does not follow the contour or run parallel to the supporting structure. All bends, curves and connections must be routed towards the grounding electrode system, ground rod, or ground bar. Grounding conductors must be securely fastened. Braided grounding conductors must not be used. Approved bonding techniques must be used for the connection of dissimilar metals. Siting ODUs and antennas ODUs, external antennas and GPS receivers are not designed to survive direct lightning strikes. For this reason they must be installed in Zone B as defined in Lightning protection zones on page 3-9. Mounting in Zone A may put equipment, structures and life at risk. Thermal Safety The ODU enclosure may be hot to the touch when in operation. The ODU must not be operated in ambient temperatures exceeding 40C unless mounted in a Restricted Access Location. For more information, see ODU ambient temperature limits on page 3-10. Warning Do not install the ODU in a location where the ambient temperature could exceed 40C unless this is a Restricted Access Location as defined by EN 60950-1. Alerte Lunit externe ne doit pas tre installe dans un endroit o la temprature ambiante est suprieure 40C moins que laccs soit limit au personnel autoris. Page 5-4 Chapter 5: Preparing for installation Preparing for installation Preparing for installation ODU pre-configuration It is common practice to pre-configure the units during staging before site installation by performing the following tasks:

Connecting to the unit Configuring IP and Ethernet interfaces Upgrading the software version and using CNUT General configuration Configuring security Configuring radio parameters Setting up SNMP agent Configuring syslog Configuring remote access Monitoring the Link Configuring quality of service Zero Touch Configuration Using DHCP Option 66 Configuring Radio via config file Configuring a RADIUS server If the units are to be pre-configured during staging, the safety precautions below MUST be observed. Preparing personnel In no event shall Cambium Networks be liable for any injury or damage caused during the installation of the Cambium 450 Platform Family ODU. Ensure that only qualified personnel undertake the installation of a 450 Platform system. Ensure that all safety precautions are observed. Preparing inventory Perform the following inventory checks:

Check that the correct components are available, as described in Ordering the components on page 2-60. Check the contents of all packages against their packing lists. Page 5-5 Chapter 5: Preparing for installation Preparing for installation Preparing tools Check that following specific tools are available, in addition to general tools:

RJ45 crimp tool (it must be the correct tool for the type of RJ45 being used). Personal Computer (PC) with 10 or 100 or 1000 BaseT Ethernet port Web browser Ethernet patch cables Page 5-6 Chapter 5: Preparing for installation Testing system components Testing system components The best practice is to connect all componentsAP/BHM, SMs/BHS, GPS antenna (if applicable) and CMM (if applicable)in a test setting and initially configure and verify them before deploying them to an installation. In this way, any configuration issues are worked out before going on-site, on a tower, in the weather, where the discovery of configuration issues or marginal hardware is more problematic and work-

flow affecting. Unpacking Components When a delivery arrives, inspect all packages immediately for damages. Carefully unpack the equipment, verify that all the components have arrived as per order and are in good condition. Save all packaging materials for equipment transportation to the installation site. Preparing the ODU After the equipment is unpacked, the units may be configured for staging tests. Use either of two methods to configure an AP/BHM:

Use the Quick Start feature of the product (via GUI menu Quick Start) Manually set each parameter After changing configuration parameters on a GUI web page:

Before you leave a web page, click the Save button to save the change(s) After making change(s) on multiple web pages, click the Reboot button to reboot the module and implement the change(s) Configuring the Computing Device for Test If the computer is configured for Dynamic Host Configuration Protocol (DHCP), disconnect the computer from the network. If the computer is instead configured for static IP addressing Set the static address in the 169.254 network Set the subnet mask to 255.255.0.0. For detailed instructions, see section Configuring the management PC on page 5-16. Page 5-7 Chapter 5: Preparing for installation Testing system components Factory default Configuration From the factory, the APs/BHMs and SMs/BHSs are all configured to not transmit on any frequency. This configuration ensures that equipment operators do not accidentally turn on an unsynchronized module. Site synchronization of modules is required because modules:

o cannot transmit and receive signals at the same time. o use TDD (Time Division Duplexing) to distribute signal access of the downlink and uplink frames. when one module transmits while an unintended module nearby receives signal, the transmitting module may interfere with or desense the receiving module. In this context, interference is self-

interference (within the same network). ODU interfaces See section 450 Platform Family interfaces on page 2-7 ODU diagnostic LEDs See section AP/BHM LEDs on page 2-15. See section SM/BHS LEDs on page 2-17. Recommended Tools for Installation The following tools may be needed for installation:

Table 93 Tools for PMP and PTP 450 Platform ODU installation Equipment to Be Installed AP or BHM AP or BHM or BHS Antenna Tools Required 3 mm Allen Wrench Used for connecting the antenna mating bracket to the rear of the AP housing Crescent Wrench Pair Used for tightening cable glands Self-amalgamating and PVC Tape Used for weatherproofing N-type connections 13 mm Spanner Wrench (or Ratchet Spanner Wrench) Pair Used for connecting the antenna (sector or omni for AP, or directional for BH)base to the pole/mast mounting bracket Self-amalgamating and PVC Tape Used for weatherproofing N-type connections N-type Torque Wrench (not required but recommended) Used for assuring proper tightening of N-type connectors terminating the RF cables Page 5-8 Chapter 5: Preparing for installation Testing system components Equipment to Be Installed SM Universal Global Positioning System Cabling Tools Required Wrench/driver (depending on operators choice of clamps) Used for tightening clamps to the pole Alignment tone adapter / headset Used for aligning the SM to the AP Philips Screwdriver Used for attaching the UGPS unit to the pole/mast mounting bracket 13mm Spanner Wrench (or Ratchet Spanner Wrench) Used for connecting the mounting brackets U-bolt to the antenna or mast Electricians Scissors or Wire Cutters Used for cutting wire to length RJ-11/RJ-45 Crimping Tool Used for stripping RJ-11/RJ-45 cables and for terminating cable ends Cable Testing Device Used to ensure that cables are properly constructed Standards for Wiring Modules automatically sense whether the Ethernet cable in a connection is wired as straight-through or crossover. Operators may use either straight-through or crossover cable to connect a network interface card (NIC), hub, router, or switch to these modules. This guide follows the EIA/TIA-568B colour code standard. Page 5-9 Chapter 5: Preparing for installation Testing system components Best Practices for Cabling The following practices are essential to the reliability and longevity of cabled connections:

Use only shielded cables to resist interference. For vertical runs, provide cable support and strain relief. Include a 2-ft (0.6-m) service loop on each end of the cable to allow for thermal expansion and contraction and to facilitate terminating the cable again when needed. Include a drip loop to shed water so that most of the water does not reach the connector at the device. Properly crimp all connectors. Use dielectric grease on all connectors to resist corrosion. Use only shielded connectors to resist interference and corrosion. Wiring Connectors The following diagrams correlate pins to wire colors and illustrate crossovers where applicable. Pin 1, relative to the lock tab on the connector of a straight-through cable is located as shown below. Figure 64 Pin 1 location Page 5-10 Testing system components Chapter 5: Preparing for installation Main port pinout Table 94 Main port pinout RJ45 pin Description 1 2 3 4 5 6 7 8

+TxRx0 TxRx0

+TxRx1

+TxRx2 TxRx2 TxRx1

+TxRx3 TxRx3 Aux port pinout Table 95 Aux port pinout RJ45 pin Description 1 2 3 4 5 6 7 8

+TxRx0 TxRx0

+TxRx1 GPS power out, Alignment tone out, GPS data out GPS data in TxRx1 GPS 0v GPS Sync in Page 5-11 Chapter 5: Preparing for installation Testing system components RJ-45 Pinout for Straight-through Ethernet Cable Figure 65 Straight-through Ethernet Cable RJ45 Connector (Bottom) 8 7 6 5 4 3 2 1

``

Straight-Through Cable RJ45 Connector (Top) 8 7 6 5 4 3 2 1 Table 96 RJ-45 pinout for straight-through Ethernet cable Pin Signal Pair Color 1 2 3 4 5 6 7 8 TP1+

TP1-

TP2+

TP3+

TP3-

TP2-

TP4+

TP4-

2 2 3 1 1 3 4 4 White/orange stripe Orange solid White/green stripe Blue solid White/blue stripe Green solid White/brown stripe Brown solid RJ-45 Pinout for Crossover Ethernet Cable Hook Underneath Crossover Cable Hook On Top 8 7 6 5 4 3 2 1 UTP Category 5/6 Cable Page 5-12 8 7 6 5 4 3 2 1 Hook Chapter 5: Preparing for installation Testing system components Table 97 RJ-45 pinout for crossover Ethernet cable Pin 1 2 3 4 5 6 7 8 Connection 1 Connection 2 Signal Pair Color Signal Pair Color TP1+

TP1-

TP2+

TP3+

TP3-

TP2-

TP4+

TP4-

White/orange stripe Orange solid White/green stripe White/blue stripe Blue solid Green solid White/brown stripe Brown solid 2 2 3 1 1 3 4 4 TP2+

TP2-

TP1+

TP4+

TP4-

TP1-

TP3+

TP3-

3 3 2 4 4 2 1 1 White/green stripe Green solid White/orange stripe White/brown stripe Brown solid Orange solid Blue solid White/blue stripe Page 5-13 Chapter 5: Preparing for installation Testing system components AP/BHM to UGPS cable The AP/BHM to UGPS cable can be constructed from RJ12 to RJ 45 cable using the pin configuration described in Table 98. Note This is only applicable for 450 AP/BHM. The AP/BHM will only power up the UGPS if it configured to do so. Figure 66 AP/BHM to UGPS cable RJ45 Connector (Bottom) Straight-Through Cable 8 7 6 5 4 3 2 1

``

RJ12 Connector (Top) 6 NC 5 4 3 NC 2 1 Table 98 AP/BHM to UGPS cable pinout Pin 450i Series AP RJ 45 Connector Pin UGPS RJ 12 Connector Connector NC NC NC 4 on RJ 12 3 on RJ 12 NC 6 on RJ 12 1 on RJ 12 1 2 3 4 5 6 7 8 1 2 3 4 5 6 8 on RJ 45 NC 5 on RJ 45 4 on RJ 45 NC 7 on RJ 45 Page 5-14 Chapter 5: Preparing for installation Testing system components Alignment tone cable (for PMP/PTP 450i) The alignment tone cable is constructed using RJ45 plug and Stereo plug. The pin configuration is shown in Figure 67 Figure 67 Alignment tone cable pin configuration

#8

#1 Pin 7 Pin 4 Resistors 220 220 Left Right Common For more information, refer Aux port to alignment tone headset wiring. Override plug cable (for PMP 450 only) To construct an override plug, perform the following steps:

Crimp an RJ-12 6 pin connector onto a 6 inch length of CAT 5 cable Pin out all 6 pins Short (solder together) pins 4 and 6 on the other end. Do not connect any other wires to anything. Figure 68 RJ-12 pinout for the default plug RJ12 Connector (Bottom) Override plug cable wiring 6 5 4 3 2 1

``

Not used Not used Not used Tie together Page 5-15 Chapter 5: Preparing for installation Configuring Link for Test Configuring Link for Test It is important to stage the AP/BHM and SM/BHS units first to verify proper registration before deploying the modules to the site. To begin configuring the modules for test, see the sections below:

Configuring the management PC To configure the local management PC to communicate with the AP, SM, BHM or BHS, proceed as follows:

Powering the AP/SM/BH for test configuration Perform the following steps to power on the ODU. Procedure 2 Powering the ODU 1 2 3 4 5 6 Plug one end of a CAT 5 Ethernet cable into the ODU. Plug the Ethernet cable connector labeled To Radio into the jack in the pig tail that hangs from the power supply. Plug the other connector of the pig tail (this connector labeled To Computer) into the Ethernet jack of the computing device. Plug the power supply into an electrical outlet. Warning From this point until you remove power from the ODU, stay at least as far from the AP as the minimum separation distance specified in Minimum separation distances on page 5-3. Power up the computing device Start the browser in the computing device The AP/BHM interface provides a series of web pages to configure and monitor the unit. Access web-

based interface through a computing device that is either directly connected or connected through a network to the AP/BHM. If the computing device is not connected to a network when it is being configured for test environment, and if the computer has used a proxy server address and port to configure a module, then the operator may need to first disable the proxy setting in the computer. Page 5-16 Chapter 5: Preparing for installation Configuring Link for Test Perform the following procedure to toggle the computer to not use the proxy setting. Procedure 3 Bypassing browser proxy settings to access module web pages 1 2 3 Launch Microsoft Internet Explorer Select Tools, Internet Options, Connections, LAN Settings. Alternate web browser menu selections may differ. Uncheck the Use a proxy server box. In the address bar of your browser, enter the IP address of the AP/BHM. (For example, enter http://169.254.1.1 to access the AP/BHM through its default IP address). The AP/BHM responds by opening the General Status tab of its Home page. Logging into the web interface AP/SM/BH Procedure 4 Logging into the web interface 1 2 3 4 Plug one end of a CAT 5 Ethernet cable into the AP/BHM Plug the Ethernet cable connector labeled To Radio into the jack in the pig tail that hangs from the power supply. Plug the other connector of the pig tail (this connector labeled To Computer) into the Ethernet jack of the computing device. Plug the power supply into an electrical outlet. Warning From this point until you remove power from the ODU, stay at least as far from the ODU as the minimum separation distance specified in Minimum separation distances on page 5-3. Using the Quick Start Configuration Wizard of the AP/BHM See section Quick link setup on page 7-11. Page 5-17 Chapter 6: Installation This chapter describes how to install and test the hardware for a 450 Platform link. It contains the following topics:

ODU variants and mounting bracket options on page 6-2 provides details of six different bracket options, including the type of ODU and range of pole diameters supported by each option. Mount the ODU, LPU and surge suppressor on page 6-3 describes how to mount and ground an integrated or connectorized ODU, how to mount and ground the top LPU. Installing the copper Cat5e Ethernet interface on page 6-19 describes how to install the copper Cat5e power over Ethernet interface from the ODU to the PSU. Installing external antennas to a connectorized ODU on page 6-23 describes how to install external antennas for a connectorized ODU. Installing ODU on page 6-59 describes how to install PTP and PMP ODU radios. Installing the AC Power Injector on page 6-63 describes how to install a power supply unit for the PMP/PTP 450 platform, either the AC Power Injector. Supplemental installation information on page 6-65 contains detailed installation procedures that are not included in the above topics, such as how to strip cables, create grounding points and weatherproof connectors. Note These instructions assume that LPUs are being installed from the 450 Platform Family LPU and grounding kit (Cambium part number C000065L007). If the installation does not require LPUs, adapt these instructions as appropriate. If LPUs are being installed, only use the five black-capped EMC cable glands supplied in the LPU and grounding kit. The silver-capped cable glands supplied in the ODU kits must only be used in 450 Platform installations which do not require LPUs. Page 6-1 Chapter 6: Installation ODU variants and mounting bracket options ODU variants and mounting bracket options Mounting bracket PMP/PTP 450i Series The PMP/PTP 450i Series supports below mentioned mounting bracket option:

Table 99 PMP/PTP 450i Series - ODU mounting bracket part numbers Cambium description Mounting bracket low profile adjustable Cambium part number N000045L002A The low profile bracket provides elevation adjustment with the PMP/PTP 450i Series Integrated ODUs of

+10 to 5 or +5 to 10. A larger adjustment range is available using the standard integrated mounting bracket. The connectorized mounting bracket does not provide elevation adjustment. Mounting bracket PMP 450 Series SM 900 MHz The PMP 450i Series SM 900 MHz has special mounting bracket option. The PMP 450i Series AP - 900 MHz mounting procedure is the same as the other 450i Series radios. The 450 Series SM 900 MHz has a different mounting bracket which is supplied along with Yagi antenna. Page 6-2 Chapter 6: Installation Mount the ODU, LPU and surge suppressor Mount the ODU, LPU and surge suppressor To install the ODU and top LPU, use the following procedures:

Attach ground cables to the ODU on page 6-3 Mount the ODU on the mast on page 6-6 Mount the top LPU on page 6-10 Mount the Surge Suppressor on page 6-10 Attach ground cables to the ODU PMP 450m Series AP 1 Fasten an AWG 10 (or 6mm2) copper ground cable to each ODU grounding point using the M6

(small) lugs. 2 Secure the M6 grounding bolts by applying 3 Nm torque.. 3 Securely connect the copper wires to the grounding system (Protective Earth) and the LPU or Gigabit Ethernet Surge Suppressor according to applicable regulations. Page 6-3 Chapter 6: Installation Mount the ODU, LPU and surge suppressor PMP/PTP 450i Series AP/SM/BH, PMP 450 3GHz Ruggedized SM 1 Fasten an AWG 10 (or 6mm2) copper ground 1 cable to each ODU grounding point using the M6

(small) lugs. 2 Tighten the Ground post screws. 2 3 Securely connect the copper wires to the grounding system (Protective Earth) and the LPU or Gigabit Ethernet Surge Suppressor according to applicable regulations. Page 6-4 Chapter 6: Installation PMP 450 AP 1 Fasten an AWG 10 (or 6mm2) copper ground cable to each ODU grounding point using the M6

(small) lugs 2 Tighten the Ground post locking nut in the copper wire Mount the ODU, LPU and surge suppressor 1 2 3 Securely connect the copper wire to the grounding system (Protective Earth) according to applicable regulations. PMP 450 SM 1 Fasten an AWG 10 (or 6mm2) copper ground cable to each ODU grounding point using the M6

(small) lugs 1 2 Tighten the Ground post locking nut in the copper wire 2 Page 6-5 Chapter 6: Installation Mount the ODU, LPU and surge suppressor 3 Securely connect the copper wire to the grounding system (Protective Earth) according to applicable regulations. The grounding point on PMP 450 Series SM 900 MHz is different from 2.4, 3.5/3.65 and 5 GHz PMP 450 SMs as shown in Figure 69. Figure 69 PMP 450 900 MHz SM grounding Mount the ODU on the mast PMP 450m Series AP 1 See - PMP 450m Series AP on page 6-52 for Installation for an integrated ODU 2 Remove the rear bracket strap from upper and lower brackets of ODU 3 Attach the upper and lower bracket of ODU to the mount point by closing the rear strap around the pole 4 Secure the four serrated flange M8 nuts by applying 10 Nm torque on upper and lower rear strap using a 13 mm spanner wrench. These must be tightened evenly on the pole to avoid jumping/stripping threads Secure the bolts on four sides by applying 8 Nm torque as per the angle of the antenna. Page 6-6 Chapter 6: Installation Mount the ODU, LPU and surge suppressor PMP/PTP 450i Series AP/SM/BH, PMP 450 3 GHz Ruggedized SM Caution Do not reverse the bracket clamp, as this arrangement may lead to failure of the assembly. Do not over-tighten the bolts as this may lead to failure of the assembly. 1 Fix the mounting plate to the back of the ODU using the four bolts, and spring and plain washers provided. Tighten the bolts. 2 Attach the bracket body to the mounting plate using the M8 bolt, spring and plain washers. 3 Hoist the ODU to the mounting position 4 Attach the bracket body to the pole using the bracket clamp, M8 bolts, and spring and plain washers. 5 Adjust the elevation and azimuth to achieve visual alignment. PMP 450b SM 1 Use a stainless steel hose clamp for the attachment. 2 Attach the mounting bracket to the structure with the release tab facing downward. Tighten the hose clamp. 3 Slide the 450b SM onto the mounting bracket. Press downwards until it clicks into place. 4 Loosen the adjuster wingnut on the bracket and set the required SM tilt angle. Retighten the adjuster wingnut by hand to secure the SM at the chosen angle. Page 6-7 Mount the ODU, LPU and surge suppressor Chapter 6: Installation PMP 450 AP 1 Using an 8mm nut driver, attach the pole mounts AP housing bracket to the unit using the 4 M5 x 16mm bolts included with the AP. 2 Using the included (depending on pole diameter):

M8 x 70mm hex cap bolts ( 2 quantity) or M8 x 40mm hex cap bolts ( 2 quantity) and M8 flat washers ( 2 quantity) M8 coil washers ( 2 quantity) Attach the mounting bracket to the pole/mast. The mounting bracket is designed to attach to poles with diameters in the range of 2 in. (50mm) to 3in.

(75mm). 3 Complete the AP mounting assembly by attaching the included:

8mm hex cap bolt ( one quantity) Through the APs attached mounting bracket and pole mount. At this time the AP may be adjusted to the desired position and tightened with a 1/2 inch spanner wrench to 11 lb/ft (14Nm). Page 6-8 Chapter 6: Installation Mount the ODU, LPU and surge suppressor PMP 450 SM (except PMP 450 SM - 900 MHz) 1 Use stainless steel hose clamps for the attachment. 2 Attach the mounting bracket to the structure. Tighten the locking nut. Stainless steel hose clamps Reflector dish arm PMP 450 SM 900 MHz (connectorized) The PMP 450 900 MHz connectorized SM mounting procedure is different from other radios. It does not get directly mounted on pole. 1 Align the 900 MHz SM to E bracket of Yagi antenna 2 Slide the radio towards right to lock on the antenna Slide towards right to lock Page 6-9 Mount the ODU, LPU and surge suppressor Chapter 6: Installation Mount the top LPU 1 For separate LPU mounting, use the U-bolt bracket from the LPU kit to mount the top LPU on the pole below the ODU. Tighten to a torque setting of 7.0 Nm (5.2 lb ft). Please refer Gigabit LPU and Grounding Kit Installation Guide for more details. Mount the Surge Suppressor PMP/PTP 450i/450b Series Gigabit Ethernet Surge Suppressors are installed at both ends of the drop cable. One within 600 mm

(24) of and under the ODU. The other located within 600 mm (24) of the building entry point. Quick procedure:

The quick procedure for the Surge Suppressor for PMP/PTP 450i/450b Series mounting is as follows:

1 Ground using the terminal on the back of the units. Use the supplied Tubular Lug and 6 mm2 (10 AWG) stranded cable, max length 600 mm (24). 2 I. Waterproof the cable lug with heat II. shrink sleeving. Secure the Cable assembly to the unit using the supplied screw and washer. Mount the Gigabit Ethernet Surge Suppressor on the wall or pole Page 6-10 Chapter 6: Installation Mount the ODU, LPU and surge suppressor 3 Connect the two CAT5e cables to the Gigabit Ethernet Surge Suppressor 4 Slide the end cap over the bottom of the Gigabit Ethernet Surge Suppressor, ensuring it clicks firmly in place Refer to the Gigabit Ethernet Surge Suppressor Installation Guide for more details. Figure 70 Gigabit Etherner Surge Suppressor Page 6-11 Chapter 6: Installation Mount the ODU, LPU and surge suppressor PMP/PTP 450 Series The PMP/PTP 450 Series uses 600SSH Surge Suppressor. The inside of the surge suppressor is shown in Figure 71. Caution The PMP 450 SM 900 MHz is based off of the 450 Series, be sure to use a 600SS to protect this radio type. Figure 71 600SSH Surge Suppressor inside Key to Callouts 600SSH 1 Holesfor mounting the Surge Suppressor to a flat surface (such as an outside wall). The distance between centers is 4.25 inches

(108 mm). 2 RJ-45 connectorsOne side (neither side is better than the other for this purpose) connects to the product (AP, SM, AC Adapter, or cluster management module). The other connects to the drop cable. 3 Ground post and washeruse heavy gauge

(10 AWG or 6 mm2) copper wire for connection. Refer to local electrical codes for exact specifications. 4 Ground Cable Openingroute the 10 AWG

(6 mm2) ground cable through this opening. 5 CAT-5 Cable Knockoutsroute the two CAT-

5 cables through these openings, or alternatively through the Conduit Knockouts. 6 Conduit Knockoutson the back of the case, near the bottom. Available for installations where cable is routed through building conduit. Note The 600SSH surge suppressor is shipped in the isolated position (pin 4 isolated by 68V from protective earth). If packet error issues occur over the Ethernet link (verify by pinging the device through the 600SSH), configure the 600SSH to grounded position (by moving the 600SSH switch from isolated to ground) to avoid ground loops that may be present in the system. The mounting procedure for the Surge Suppressor for PMP/PTP 450 Series is as follows:

1 Remove the cover of the 600SSH Surge Suppressor. Page 6-12 Chapter 6: Installation Mount the ODU, LPU and surge suppressor 2 3 4 5 6 With the cable openings facing downward, mount the 600SSH to the outside of the subscriber premises, as close to the point where the Ethernet cable penetrates the residence or building as possible, and as close to the grounding system (Protective Earth) as possible. Wrap an AWG 10 (or 6mm2) copper wire around the Ground post of the 600SSH. Tighten the Ground post locking nut in the 600SSH onto the copper wire. Securely connect the copper wire to the grounding system (Protective Earth) according to applicable regulations. Using diagonal cutters or long nose pliers, remove the knockouts that cover the cable openings to the 600SSH. Pack both of the surge suppressor Ethernet jacks with dielectric grease. Wrap a splice loop in the loose end of the Ethernet cable from the SM. Connect that cable to one of the Ethernet jacks. 7 8 9 10 Connect an Ethernet cable to the other Ethernet jack of the 600SSH and to the power adapter. 11 Replace the cover of the 600SSH. General protection installation To adequately protect a 450 Platform Family installation, both ground bonding and transient voltage surge suppression are required. Grounding cable requirements When routing, fastening and connecting grounding cables, the following requirements must be implemented:

Grounding conductors must be run as short, straight, and smoothly as possible, with the fewest possible number of bends and curves. Grounding cables must not be installed with drip loops. All bends must have a minimum radius of 203 mm (8 in) and a minimum angle of 90 (Figure 72). A diagonal run is preferable to a bend, even though it does not follow the contour or run parallel to the supporting structure. All bends, curves and connections must be routed towards the grounding electrode system, ground rod, or ground bar. Grounding conductors must be securely fastened. Braided grounding conductors must not be used. Approved bonding techniques must be used for the connection of dissimilar metals. Page 6-13 Chapter 6: Installation Figure 72 Grounding cable minimum bend radius and angle Mount the ODU, LPU and surge suppressor Caution Do not attach grounding cables to the ODU mounting bracket bolts, as this arrangement will not provide full protection. Page 6-14 Chapter 6: Installation Mount the ODU, LPU and surge suppressor Basic requirements The following basic protection requirements must be implemented:

ODU must be in Zone B (see Lightning protection zones on page 3-9). ODU must be grounded to the supporting structure. A surge suppression unit must be installed on the outside of the building. The distance between the ODU and Gigabit Surge Suppressor should be kept to a minimum. The drop cable must not be laid alongside a lightning air terminal. All grounding cables must be a minimum size of 10 mm2 csa (8AWG), preferably 16 mm2 csa

(6AWG), or 25 mm2 csa (4AWG). Protection requirements for a wall installation If the ODU is to be mounted on the wall of a building, then in addition to the general protection requirements (above), the following requirements must be observed:

The equipment must be lower than the top of the building or its lightning air terminal. The building must be correctly grounded. Schematic examples of wall installations are shown in Figure 73. Figure 73 Grounding and lightning protection on wall Page 6-15 Chapter 6: Installation Mount the ODU, LPU and surge suppressor Protection requirements for a mast or tower installation If the ODU is to be mounted on a metal tower or mast, then in addition to the general protection requirements (above), the following requirements must be observed:

The equipment must be lower than the top of the tower or its lightning air terminal. The metal tower or mast must be correctly grounded. Schematic examples of mast or tower installations are shown in Figure 74. Page 6-16 Chapter 6: Installation Figure 74 Grounding and lightning protection on mast or tower Mount the ODU, LPU and surge suppressor Outdoor CAT5e cable Cat5e cable Ground Cable Tower/building ground system AP/BHM Ground to opposite side ODU grounding lug Gigabit surge suppressor Equipment building Gigabit surge suppressor External ground bar Power supply Network switch Ground ring Page 6-17 Chapter 6: Installation Mount the ODU, LPU and surge suppressor Protection requirements on a multifloor building If the ODU is to be mounted on a high rise building, it is likely that cable entry is at roof level (Figure 42) and the equipment room is several floors below. The following additional requirements must be observed:

The ODU must be below the lightning terminals and finials. A grounding conductor must be installed around the roof perimeter to form the main roof perimeter lightning protection ring. Air terminals are typically installed along the length of the main roof perimeter lightning protection ring typically every 6.1m (20ft). The main roof perimeter lightning protection ring must contain at least two down conductors connected to the grounding electrode system. The down conductors should be physically separated from one another, as far as practical. Figure 75 Grounding and lightning protection on building Page 6-18 Chapter 6: Installation Installing the copper Cat5e Ethernet interface Installing the copper Cat5e Ethernet interface To install the copper Cat5e Ethernet interface, use the following procedures:

Install the main drop cable on page 6-19 Install the bottom LPU to PSU drop cable on page 6-21 Installing external antennas to a connectorized ODU on page 6-23 Caution To avoid damage to the installation, do not connect or disconnect the drop cable when power is applied to the PSU or network terminating equipment. Caution Always use Cat5e cable that is gel-filled and shielded with copper-plated steel. Alternative types of Cat5e cable are not supported by Cambium Networks. Cambium Networks supply this cable (Cambium part numbers WB3175 and WB3176), RJ45 connectors (Cambium part number WB3177) and a crimp tool (Cambium part number WB3211). The LPU and grounding kit contains a 600 mm length of this cable. Install the main drop cable Warning The metal screen of the drop cable is very sharp and may cause personal injury. ALWAYS wear cut-resistant gloves (check the label to ensure they are cut resistant). ALWAYS wear protective eyewear. ALWAYS use a rotary blade tool to strip the cable (DO NOT use a bladed knife). Warning Failure to obey the following precautions may result in injury or death:

Use the proper hoisting grip for the cable being installed. If the wrong hoisting grip is used, slippage or insufficient gripping strength will result. Do not reuse hoisting grips. Used grips may have lost elasticity, stretched, or become weakened. Reusing a grip can cause the cable to slip, break, or fall. The minimum requirement is one hoisting grip for each 60 m (200 ft) of cable. Page 6-19 Chapter 6: Installation Installing the copper Cat5e Ethernet interface Cut to length and fit hoisting grips 1 Cut the main drop cable to length from the top LPU to the bottom LPU. 2 Slide one or more hoisting grips onto the top end of the drop cable. 3 Secure the hoisting grip to the cable using a special tool, as recommended by the manufacturer. Terminate with RJ45 connectors Caution Check that the crimp tool matches the RJ45 connector, otherwise the cable or connector may be damaged. 1 Strip the cable outer sheath and fit the RJ45 connector load bar. 2 Fit the RJ45 connector housing as shown. To ensure there is effective strain relief, locate the cable inner sheath under the connector housing tang. Table 100 RJ45 connector and cable color code Pin 1 2 3 4 5 6 7 8 Color (Supplied cable) Light Orange Orange Light Green Blue Light Blue Green Light Brown Brown Figure 76 RJ45 cable Color

(Conventional) White/Orange Orange White/Green Blue White/Blue Green White/Brown Brown Pins on plug face RJ45 Connector (Bottom) Straight-Through Cable 8 7 6 5 4 3 2 1

``

Page 6-20 Chapter 6: Installation Installing the copper Cat5e Ethernet interface Install the bottom LPU to PSU drop cable Install the bottom LPU Install the bottom LPU, ground it, and connect it to the main drop cable. 1 Select a mounting point for the bottom LPU within 600 mm (24 in) of the building entry point. Mount the LPU vertically with cable glands facing downwards. Power over Ethernet CAT5e cable (gel-filled, shielded with copper-plated steel) Network CAT5e cable AC supply Bottom LPU M axim um 600 m m

(24 inches) Groun d cables Site gro unding system PSU Network term inating eq uipment Grounding system LPU to grou nding system PSU dro p cable Building entry point 2 3 Connect the main drop cable using the EMC cable gland to the bottom LPU. Fasten one ground cable to the bottom LPU using the M6 (small) lug. Tighten both nuts to a torque of 5 Nm (3.9 lb ft):

Locking nut Washer M6 lug Washer Nut Toothed washer Other end of ground cable has M10 lug to ground 4 Select a building grounding point near the LPU bracket. Remove paint from the surface and apply anti-oxidant compound. Fasten the LPU ground cable using the M10 (large) lug. Page 6-21 Chapter 6: Installation Installing the copper Cat5e Ethernet interface Install the LPU to PSU drop cable Use this procedure to terminate the bottom LPU to PSU drop cable with RJ45 connectors at both ends, and with a cable gland at the LPU end. Warning The metal screen of the drop cable is very sharp and may cause personal injury. ALWAYS wear cut-resistant gloves (check the label to ensure they are cut resistant). ALWAYS wear protective eyewear. ALWAYS use a rotary blade tool to strip the cable, not a bladed knife. Caution Check that the crimp tool matches the RJ45 connector, otherwise the cable or connector may be damaged. 1 Cut the drop cable to the length required from bottom LPU to PSU. 2 At the LPU end only:

Fit one cable gland and one RJ45 connector by following the procedure Terminate with RJ45 connectors on page 6-20. Connect this cable and gland to the bottom LPU. 3 At the PSU end only: Do not fit a cable gland. Strip the cable outer sheath and fit the RJ45 connector load bar. Fit the RJ45 connector housing. To ensure there is effective strain relief, locate the cable inner sheath under the connector housing tang:

Page 6-22 Chapter 6: Installation Installing external antennas to a connectorized ODU Installing external antennas to a connectorized ODU PMP 450i Series To mount and connect an external antenna to the connectorized ODU, proceed as follows:

1 Mount the antenna(s) according to manufacturers instructions. 2 Connect the ODU A and B interfaces to the antenna(s) with RF cable of type LMR-400 (Cambium part numbers 30010194001 and 30010195001) and N type connectors (Cambium part number 09010091001). Tighten the N type connectors to a torque setting of 1.7 Nm (1.3 lb ft). If the ODU is mounted indoors, install lightning arrestors at the building entry point:

3 4 Form drip loops near the lower ends of the antenna cables. These ensure that water is not channeled towards the connectors. If the ODU is mounted outdoors, weatherproof the N type connectors (when antenna alignment is complete) using PVC tape and self-amalgamating rubber tape. 5 Page 6-23 Chapter 6: Installation Installing external antennas to a connectorized ODU 6 Weatherproof the antenna connectors in the same way (unless the antenna manufacturer specifies a different method). Equipm ent building or cabinet RF cables to antenna RF cable CAT5e cable Connectorized ODU AC supply A B PSU Network equipment Lightning arrestors Ground ring Page 6-24 Chapter 6: Installation Installing external antennas to a connectorized ODU 7 Ground the antenna cables to the supporting structure within 0.3 meters (1 foot) of the ODU and antennas using the Cambium grounding kit (part number 01010419001):

Antenna RF cable PM P/PTP 450i grou nd cable Connectorized ODU A B 8 Fix the antenna cables to the supporting structure using site approved methods. Ensure that no undue strain is placed on the ODU or antenna connectors. Ensure that the cables do not flap in the wind, as flapping cables are prone to damage and induce unwanted vibrations in the supporting structure. Note A video on weatherproofing procedure can be found at:

https://www.youtube.com/watch?v=a-twPfCVq4A Page 6-25 Chapter 6: Installation Installing external antennas to a connectorized ODU Assembling the PMP 450i AP 5 GHz sector antenna and attaching to the radio To assemble a PMP 450i Series AP antenna, perform the following steps. Note Cambium recommends to assemble the antenna, attach the AP and cabling, and to seal the RF connections before installing the unit at the deployment site. 1 Inventory the parts to ensure that you have them all before you begin. The full set of parts is shown below. Figure 77 AP antenna parts Page 6-26 Chapter 6: Installation Installing external antennas to a connectorized ODU 2 Remove top plate from the antenna as shown in Figure 78. Figure 78 Antenna top plate 3 Attach the antenna plate to the AP as shown in Figure 79. Note Please use the four thin neck M6 bolts and split washers provided with the connectorized units rather that the ones provided in the antenna kit. Figure 79 Attaching antenna plate to the AP Page 6-27 Chapter 6: Installation Installing external antennas to a connectorized ODU 4 Attach the plate mounted AP to the antenna and tighten the (4) serrated flange nuts using a spanner wrench Figure 80 Attaching the plate 5 Connect the port A of AP to vertical and port B of AP to horizontal polarization interfaces of the antenna with RF cable. Tighten the N type connectors to a torque setting of 1.7 Nm (1.3 lb ft). Figure 81 Connect the port A and B to the PMP 450i AP Page 6-28 Chapter 6: Installation Installing external antennas to a connectorized ODU 6 Assemble the upper bracket by attaching the (2) 7 hex bolts to the bracket using (2) serrated flange nuts Figure 82 AP antenna upper bracket assembly Figure 83 AP antenna upper bracket attached to upper adjustment arms 7 Attach the upper bracket to the adjustment arms using (2) hex bolts, (2) flat washers and (2) lock washers. Feed the bolt through the lock washer then flat washer, then thread the bolt into the upper brackets threaded receptacle. Page 6-29 Chapter 6: Installation Installing external antennas to a connectorized ODU 8 Attach the rear strap to the upper bracket using

(2) serrated flange nuts and (1) retaining bracket. Do not tighten the nuts now. Figure 84 Rear strap connected to upper AP antenna bracket 9 Attach the entire upper bracket to the antenna using (2) hex bolts, (2) flat washers and (2) lock washers. Feed the bolt through the lock washer then flat washer, then thread the bolt into the upper brackets threaded receptacle. Figure 85 Assembled upper bracket connected to AP antenna 10 Begin assembling the lower bracket by attaching the (2) 7 hex bolts to the bracket using (2) serrated flange nuts Figure 86 AP Antenna Lower Bracket Assembly 11 Attach the rear strap to the bracket using (2) serrated flange nuts and (1) retaining bracket. Do not tighten the nuts now. Attach the entire lower bracket to the antenna using (2) hex bolts, (2) flat washers and (2) lock washers. Page 6-30 Chapter 6: Installation Installing external antennas to a connectorized ODU Figure 87 Lower bracket attached to AP antenna Figure 88 Completed AP and antenna assembly Page 6-31 Chapter 6: Installation Installing external antennas to a connectorized ODU PMP 450 Series Assembling the PMP 450 AP antenna To assemble a PMP 450 Series AP antenna, perform the following steps. Note Cambium recommends to assemble the antenna, attach the AP and cabling, and to seal the RF connections before installing the unit at the deployment site. 1 Inventory the parts to ensure that you have them all before you begin. The full set of parts is shown below. Figure 89 PMP 450 AP antenna parts Page 6-32 Chapter 6: Installation Installing external antennas to a connectorized ODU 2 Begin assembling the upper bracket by attaching the (2) 7 hex bolts to the bracket using (2) serrated flange nuts Figure 90 AP antenna upper bracket assembly Figure 91 AP antenna upper bracket attached to upper adjustment arms 3 Attach the upper bracket to the adjustment arms using (2) hex bolts, (2) flat washers and

(2) lock washers. Feed the bolt through the lock washer then flat washer, then thread the bolt into the upper brackets threaded receptacle. Page 6-33 Chapter 6: Installation Installing external antennas to a connectorized ODU 4 Attach the rear strap to the upper bracket using (2) serrated flange nuts and (1) retaining bracket. Do not tighten the nuts now. Figure 92 Rear strap connected to upper AP antenna bracket Figure 93 Assembled upper bracket connected to AP antenna 5 Attach the entire upper bracket to the antenna using (2) hex bolts, (2) flat washers and (2) lock washers. Feed the bolt through the lock washer then flat washer, then thread the bolt into the upper brackets threaded receptacle. Page 6-34 Chapter 6: Installation Installing external antennas to a connectorized ODU 6 Begin assembling the lower bracket by attaching the (2) 7 hex bolts to the bracket using (2) serrated flange nuts Figure 94 AP Antenna Lower Bracket Assembly 7 Attach the rear strap to the bracket using (2) serrated flange nuts and (1) retaining bracket. Do not tighten the nuts now. Attach the entire lower bracket to the antenna using (2) hex bolts, (2) flat washers and (2) lock washers. Figure 95 Lower bracket attached to AP antenna Attaching the PMP 450 AP to the antenna To attach a PMP 450 Series AP to the antenna, perform the following steps. Page 6-35 Chapter 6: Installation Installing external antennas to a connectorized ODU Note Use shielded cable for all infrastructure connections associated with APs, SMs, and CMMs. The environment that these modules operate in often has significant unknown or varying RF energy. Operator experience consistently indicates that the additional cost of shielded cables is more than compensated by predictable operation and reduced costs for troubleshooting and support. 1 Attach the included bracket to the rear of the AP using the (4) M5 x 7mm bolts Figure 96 Attaching bracket to the rear of the AP 2 Attach the AP to the antenna by sliding the bracket onto the bolts and tighten the (4) serrated flange nuts using a 13 mm spanner wrench. Figure 97 Lower bracket attached to AP antenna Page 6-36 Chapter 6: Installation Installing external antennas to a connectorized ODU Note If using a non-standard antenna, do not cover the equilibrium membrane vent located on the back of the unit. Equilibrium Membrane Vent Figure 98 Mounted PMP 450 AP and antenna assembly, viewed from back and back Page 6-37 Chapter 6: Installation Installing external antennas to a connectorized ODU Attaching the PMP 450 Series AP and antenna to the mount point 1 Attach the upper bracket of the antenna to the mount point by closing the rear strap around the pole and tightening the (2) serrated flange nuts using a 13mm spanner wrench. These must be tightened evenly on the pol to avoid jumping/stripping threads. Figure 99 Attaching the AP antenna upper bracket to the pole 2 3 Attach the lower bracket of the antenna to the mount point by closing the rear strap around the pole and tightening the (2) serrated flange nuts using a 13mm spanner wrench. These must be tightened evenly on the pole to avoid jumping/stripping threads. Figure 100 Attaching the AP antenna lower bracket to the pole Use a local map, compass, and/or GPS device as needed to determine the direction that one or more APs require to each cover the 90 sector. Page 6-38 Chapter 6: Installation Installing external antennas to a connectorized ODU 4 5 6 7 Choose the best mounting location for your particular application. Note Use the embedded spectrum analyzer or a commercial analyzer to evaluate the frequencies present in various locations. OFDM APs need not be mounted next to each other. They can be distributed throughout a given site. However, the 90 offset must be maintained. If you want to collocate these APs with PMP 100 Series APs of the 5.4-GHz frequency band range, plan to allow at least 25 MHz of separation between their center channels. Secure a ground strap to the ground lug on the back of the AP. Secure the ground strap to the pole, tower, or other trusted ground. The bracket of the standard antenna has provision for measured down tilt. The recommended practice is to use one of the many radio analysis and mapping tools or on-line tools to calculate down tilt based on antenna height above the service area. The proper angle of tilt can be calculated as a factor of both the difference in elevation and the distance that the link spans. Even in this case, a plumb line and a protractor can be helpful to ensure the proper tilt. This tilt is typically minimal. The number of degrees to offset (from vertical) the mounting hardware leg of the support tube is equal to the angle of elevation from the lower module to the higher module (<B in the example provided in Figure 65). Page 6-39 Chapter 6: Installation Installing external antennas to a connectorized ODU 8 9 Figure 101 Variables for calculating angle of elevation (and depression) Where:

b B A Is:

angle of elevation vertical difference in elevation horizontal distance between modules To use metric units to find the angle of elevation, use the following formula:

tan b =

tan b =

B 1000A Where:

B 5280A Where:

B A Is:

expressed in meters expressed in kilometers B A Is:

expressed in feet expressed in miles To use English standard units to find the angle of elevation, use the following formula:

The angle of depression from the higher module is identical to the angle of elevation from the lower module. Connect the coax cables to the antenna and to the AP Weatherproof the connector on the coax cables (see section Attaching and weatherproofing an N type connector on page 6-69). Page 6-40 Chapter 6: Installation Installing external antennas to a connectorized ODU PMP 450i Series AP 900 MHz Mounting of PMP 450i AP 900 MHz 1 Inventory the parts to ensure that you have them all before you begin. The full set of parts is shown in Figure 103. Figure 102 PMP 450i AP 900 MHz antenna unbox view Figure 103 PMP 450i AP 900 MHz antenna inventory Upper bracket Adjustable arm Lower bracket Nuts and bolts Radio assembly plate Page 6-41 Chapter 6: Installation Installing external antennas to a connectorized ODU 2

(1) Unfold the upper bracket assembly of the antenna.

(2) Unfold the lower bracket assembly.

(3) Loose the radio assembly plate by untightening M8 four bolds.

(4) Remove the radio assembly top plate by sliding towards upper bracket assembly. Page 6-42 1 2 3 4 Chapter 6: Installation Installing external antennas to a connectorized ODU 3

(1) Place the radio assembly plate on the radio and align holes with radio enclosure. Note Ensure that the radio plate notch opening and RF port of radio in same direction. It is also important to make sure you attach the radio assembly plate in the proper orientation as shown in figure.

(2) Insert M6 bolts through plate into radio enclosure

(3) Fix the plate by tightening four bolts with a torque setting on 2 0.5 Nm Page 6-43 1 2 3 Chapter 6: Installation Installing external antennas to a connectorized ODU 4

(1) Place the radio mounted plate on sector antenna as shown in the figure. Ensure that the orientation of RF port of antenna and radio are in same direction

(2) Line up the radio assembly to four bolts and slide towards lower bracket assembly to lock.

(3) Tighten the radio assembly plate using four M8 bolts to a torque setting of 2 0.5 Nm Page 6-44 1 2 3 Chapter 6: Installation Installing external antennas to a connectorized ODU 5

(1) Connect the port A of AP to vertical and port B of AP to horizontal polarization interfaces of the antenna with RF cable. Ensure that the RF cables are pass-through inside the lower bracket assembly Port A Port B

(2) Hand tighten the N type connectors and the torque should not exceed more than 1 Nm Mounting of PMP 450i AP 900 MHz antenna to the pole The mounting procedure of PMP 450i AP 900 MHz and antenna to the pole is given below:

1 Remove the upper and lower rear bracket strap from the sector antenna. 1 2 Page 6-45 Chapter 6: Installation Installing external antennas to a connectorized ODU 2 Attach the upper and lower bracket of the antenna to the mount point by closing the rear strap around the pole. Note Before mounting the radio on the pole, secure the upper and lower bracket assemblies with a torque setting of 3 to 4 Nm as shown in Figure 1 . Also, ensure that inner strap of upper bracket is set to zero degree marking. Figure 104 Attaching radio mounting PMP 450i AP 900 MHz antenna to the pole Inner strap 1 2 Rear strap Rear strap 3 Page 6-46 Chapter 6: Installation Installing external antennas to a connectorized ODU 3 Tighten the four serrated flange M10 nuts on the upper and lower rear straps using a 17 mm spanner wrench. These must be tightened evenly on the pole to avoid jumping/stripping threads ODU ground cable Building ground system Sector antenna alignment The 900 MHz sector antenna horizontal and vertical alignment procedure is shown in Figure 105. The antenna can be aligned from +5 to -10 degree by adjusting the inner strap of the upper bracket assembly. Figure 105 900 MHz sector antenna alignment Horizontal alignment Vertical alignment Vertical alignment upward Inner strap downward tilt tilt Upper bracket assembly ODU ground cable Building ground system Page 6-47 Chapter 6: Installation Installing external antennas to a connectorized ODU PMP 450 Series SM 900 MHz Attaching the SM 900 MHz directional antenna to the pole 1 Unbox the directional Yagi antenna. Figure 106 PMP 450i SM 900 MHz external directional antenna 2 Attach the directional antenna to the pole and insert the two U clamps into the mounting bracket of the antenna Figure 107 Attach the antenna to the pole Page 6-48 Chapter 6: Installation Installing external antennas to a connectorized ODU 3 Tighten all nuts to approximately 6 to 7 Nm or less to avoid deforming the pole. Figure 108 Fixing the nuts Page 6-49 Chapter 6: Installation Installing external antennas to a connectorized ODU Radio mounting to the antenna 1 Align the radio to E bracket and slide towards right to lock on the antenna as shown in figure. Figure 109 Fixing the radio to the antenna Slide towards right to lock 2 Connect the port A of SM to vertical and port B of SM to horizontal polarization interfaces of the antenna with RF cable. Figure 110 Connecting RF cable to the radio ODU ground cable Building ground system Page 6-50 Chapter 6: Installation Installing external antennas to a connectorized ODU Directional Yagi antenna alignment The directional Yagi antenna horizontal and vertical alignment procedure is shown below. The Yagi antenna can be aligned for +15 to -15 degree. Figure 111 Yagi antenna alignment - horizontally Figure 112 Yagi antenna alignment - upward tilt Figure 113 Yagi antenna alignment - downward tilt Page 6-51 Chapter 6: Installation Installing an integrated ODU Installing an integrated ODU Caution Do not reverse the bracket clamp, as this arrangement may lead to failure of the assembly. Do not over-tighten the bolts as this may lead to failure of the assembly. PMP 450m Series AP To mount and connect an integrated ODU, proceed as follows:

1 Inventory the parts to ensure that you have them all before you begin. The full set of parts is shown in Figure 114. Figure 114 PMP 450m Series - AP unbox view Top bracket

(Additional nuts) PMP 450m AP Bottom bracket

(Additional nuts) Note The additional nuts provided for top and bottom brackets are used to hold the long bolts in position during installation. Page 6-52 Chapter 6: Installation Installing an integrated ODU 2 Attach the bottom bracket to the ODU using (2) hex bolts and secure the M8 bolts by applying 5 Nm torque. 3 Attach the top bracket to the projecting studs on the ODU and secure the top bracket using two M8 nuts by applying 5 Nm torque. 4 Fix the front and rear strap assembly to the upper bracket using two bolts. Do not tighten the nuts now. Note: The PMP 450m antenna operates with 2 degrees of electrical down-tilt. 5 Fix the front and rear strap assembly to the bottom bracket using two bolts. Do not tighten the nuts now. Page 6-53 Chapter 6: Installation Installing an integrated ODU 6 See PMP 450m Series AP on page 6-3 for the grounding procedure. See PMP 450m Series AP on page 6-6 for the mounting procedure. Page 6-54

 

 

Chapter 6: Installation PMP/PTP 450i Series AP/SM/BH To mount and connect an integrated ODU, proceed as follows:

Installing an integrated ODU 1 Fix the mounting plate to the back of the ODU using the four M6 bolts, and spring and plain washers provided. Tighten the bolts to a torque setting of 5.0 Nm (3.7 lb ft). Figure 115 Fixing the mounting plate to the back of the ODU 2 Attach the bracket body to the mounting plate using the M8 bolt, spring and plain washers. 3 Hoist the ODU to the mounting position. 4 Attach the bracket body to the pole using the bracket clamp, M8 bolts, and spring and plain washers. 5 If the ODU is mounted outdoors, weatherproof the N type connectors (when antenna alignment is complete) using PVC tape and self-amalgamating rubber tape. Figure 116 Attaching the bracket body Page 6-55 Chapter 6: Installation Connecting Cat5e Ethernet cable Connecting Cat5e Ethernet cable Connecting an RJ45 and gland to a unit Perform this task to connect the Ethernet cable to an AP. To connect the Ethernet cable with a gland to an AP unit, proceed as follows:

1 Insert the RJ45 cable through the gland components Insert the RJ45 plug into the socket in the unit, making sure that the locking tab snaps home. Support the drop cable and gently hand screw the gland body into the unit until the bushing seal is flush to the unit body. Note Do not fit the back shell prior to securing the gland body. Once the gland is fully hand screwed into the unit, tighten it one full rotation only with a 1 1/8 inch spanner wrench. When the gland body has been fitted, tighten the gland back shell. Caution Do not over-tighten the gland back shell, as the internal seal and structure or RJ45 port may be damaged. 2 3 4 5 Page 6-56 Chapter 6: Installation Figure 117 Ethernet cable gland for PMP/PTP 450 Series Connecting Cat5e Ethernet cable Figure 118 Ethernet cable gland for PMP/PTP 450i Series Page 6-57 Chapter 6: Installation Connecting Cat5e Ethernet cable Disconnecting an RJ45 and gland from a unit To disconnect the Ethernet cable and gland from a unit, proceed as follows:

1 2 Hold the Ethernet cable and remove the gland back shell. Use a small flathead screwdriver (0.2/5mm wide or greater) to gently release the black plastic watertight bushing from the compression fins, being careful not to damage the bushing. Unscrew the gland body from the AP, making sure that the Ethernet cable is not rotating while disengaging the gland body from the AP housing. Use a small screwdriver to depress the RJ45 locking clip. Unplug the RJ45 cable. Remove the gland from the cable, if necessary. 3 4 5 6 Page 6-58 Installing ODU Chapter 6: Installation Installing ODU Installing a 450 Platform Family AP To install a 450 Platform Family AP, perform the following steps. Procedure 5 Installing an AP 1 2 3 4 5 6 Begin with the AP in the powered-down state. Choose the best mounting location for your particular application. Modules need not be mounted next to each other. They can be distributed throughout a given site. However, the 60 offset must be maintained. Mounting can be done with supplied clamps. See Installing external antennas to a connectorized ODU on page 6-23 for connecting an external antenna to PMP 450i Series, PMP 450 Series, PMP 450i Series AP 900 MHz and PMP 450 Series SM See Installing an integrated ODU on page 6-52 Align the AP as follows:

a. Move the module to where the link will be unobstructed by the radio horizon and no objects penetrate the Fresnel zone. b. Use a local map, compass, and/or GPS device as needed to determine the direction that one or more APs require to each cover the intended 60 sector. c. Apply the appropriate degree of downward tilt. d. Ensure that the nearest and furthest SMs that must register to this AP are within the beam coverage area. Adjust the azimuth to achieve visual alignment, lock the AP in the proper direction and downward tilt. Attach the cables to the AP (See Powering the AP/SM/BH for test configuration on Page 5-

16) Waterproof the cables (See section Attaching and weatherproofing an N type connector on page 6-69). Page 6-59 Chapter 6: Installation Installing ODU Installing a 450 Platform Family SM Installing a 450 Platform Family SM consists of two procedures:

Physically installing the SM on a residence or other location and performing a coarse alignment using the alignment tool or alignment tone. Verifying the AP to SM link and finalizing alignment using review of power level, link tests, and review of registration and session counts. Procedure 6 Installing an SM 1 2 3 4 5 6 7 8 9 10 11 12 13 Choose the best mounting location for the SM based on section ODU and external antenna location on page 3-10. Use stainless steel hose clamps or equivalent fasteners to lock the SM into position. See Installing external antennas to a connectorized ODU on page 6-23 for connecting external antenna See Installing an integrated ODU on page 6-52 Remove the base cover of the SM. Terminate the UV outside grade Category 5 Ethernet cable with an RJ-45 connector, and connect the cable to the SM. Wrap a drip loop in the cable. For Connectorized Models, Install the external antenna according to the manufacturers instructions. For Connectorized Models, connect the SMs N-type antenna connectors to the external antenna, ensuring that the polarity matches between the SM cable labeling and the antenna port labels. Connectorized SM Antenna Cable Label Antenna Connection A Vertical B Horizontal For Connectorized Models, weatherproof the N-type antenna connectors following section Attaching and weatherproofing an N type connector on page 6-69. Wrap an AWG 10 (or 6mm2) copper wire around the Ground post of the SM Securely connect the copper wire to the grounding system (Protective Earth) according to applicable regulations. Install a surge suppressor as described in the section Mount the Surge Suppressor on page 6-10. Connect the power supply to a power source. Connect the Ethernet output from the Data port of the power supply to the Ethernet port of your laptop. Page 6-60 Chapter 6: Installation Installing ODU 14 15 16 17 18 19 Connect the drop cable from ODU to the Data+power port of the power suppy. Launch your web browser. In the URL address bar, enter 169.254.1.1. then press Enter. If the browser in laptop fails to access the interface of the SM, follow the procedure Radio recovery mode on page 1-26 Log in as admin on the ODU. Configure a password for the admin account and log off. Log back into the SM as admin or root, using the password that you configured. For coarse alignment of the SM, use the Alignment Tool located at Tools, Alignment Tool. Optionally, connect a headset to the AUX/SYNC port on the SM and listen to the alignment tone, which indicates greater SM receive signal power by pitch. By adjusting the SMs position until the highest frequency pitch is obtained operators and installers can be confident that the SM is properly positioned. For information on device GUI tools available for alignment, see sections Using the Alignment Tool, Using the Link Capacity Test tool, and Using AP Evaluation tool below. 20 When the highest power is achieved, lock the SM mounting bracket in place. 21 22 23 24 Log off of the SM web interface. Disconnect the Ethernet cable from your laptop. Replace the base cover of the SM. Connect the Ethernet cable to the computer that the subscriber will be using. Installing a 450 Platform Family BHM To install a 450 Platform Family BHM, perform the following steps. Procedure 7 Installing a BHM 1 2 3 4 Choose the best mounting location for your particular application. Align the BHM as follows:

a. Move the module to where the link will be unobstructed by the radio horizon and no objects penetrate the Fresnel zone. b. Use a local map, compass, and/or GPS device as needed to determine the direction to the BHS. c. Apply the appropriate degree of downward or upward tilt. d. Ensure that the BHS is within the beam coverage area. Using stainless steel hose clamps or equivalent fasteners, lock the BHM into position. See Installing external antennas to a connectorized ODU on page 6-23 for connecting external antenna If this BHM will not be connected to a CMM, optionally connect a cable to a GPS timing source and then to the SYNC port of the BHM. Page 6-61 Chapter 6: Installation Installing ODU 5 6 7 Either connect the BHMs Aux to the CMM or connect the DC power converter to the BHM and then to an AC power source. RESULT: When power is applied to a module or the unit is reset on the web-based interface, the module requires approximately 25 seconds to boot. During this interval, self-

tests and other diagnostics are being performed. Access Configuration > General page of the BHM for Synchronization configuration. If a CMM4 is connected, set the Sync Input parameter to the AutoSync or Autosync +

Free Run selection. Installing a 450 platform BHS To install a PTP 450 platform Series BHS, perform the following steps. Procedure 8 Installing a BHS 1 2 3 4 5 6 Choose the best mounting location for the BHS. Terminate the UV outside grade Category 5 Ethernet cable with an RJ-45 connector, and connect the cable to the BHS. (See Powering the AP/SM/BH for test configuration on Page 5-16) Use stainless steel hose clamps or equivalent fasteners to lock the BHS into position. Install a surge suppressor as described in the section Mount the Surge Suppressor on page 6-10 For coarse alignment of the BHS, use the Audible Alignment Tone feature as follows:

a. At the BHS, connect the RJ-45 connector of the Alignment Tool Headset to the Aux port via an alignment tone adapter as shown in Figure 183 on page 8-19. b. Listen to the alignment tone for pitch, which indicates greater signal power

(RSSI/dBm) by higher pitch. Adjust the module slightly until you hear the highest pitch and highest volume When you have achieved the best signal (highest pitch, loudest volume), lock the BHS in place with the mounting hardware Configuring the Link See Configuring remote access on page 7-194. Monitoring the Link See Monitoring the Link on page 7-195. Page 6-62 Chapter 6: Installation Installing the AC Power Injector Installing the AC Power Injector Caution As the PSU is not waterproof, locate it away from sources of moisture, either in the equipment building or in a ventilated moisture-proof enclosure. Do not locate the PSU in a position where it may exceed its temperature rating. Caution Do not plug any device other than a PMP/PTP 450i Series ODU into the ODU port of the PSU. Other devices may be damaged due to the non-standard techniques employed to inject DC power into the Ethernet connection between the PSU and the ODU. Do not plug any device other than a Cambium 450 Platform PSU into the PSU port of the ODU. Plugging any other device into the PSU port of the ODU may damage the ODU and device. Installing the AC Power Injector Follow this procedure to install the AC Power Injector:

1 Form a drip loop on the PSU end of the LPU to PSU drop cable. The drip loop ensures that any moisture that runs down the cable cannot enter the PSU.

(a) Place the AC Power Injector on a horizontal surface. Plug the LPU to PSU drop cable into the PSU port labeled ODU. (b) When the system is ready for network connection, connect the network Cat5e cable to the LAN port of the PSU:

(a)

(b) 2 Page 6-63 Chapter 6: Installation Installing CMM4 Installing CMM4 Note For instructions on CMM3 (CMMmicro) or CMM4 installation, including the outdoor temperature range in which it is acceptable to install the unit, tools required, mounting and cabling instructions, and connectivity verification, please see the PMP Synchronization Solutions User Guide located on the Cambium website. The Cluster Management Module 4 (CMM4) provides power, sync, and network connectivity for up to eight APs, backhauls, and Ethernet terrestrial feeds in a variety of configurations. The CMM4 provides Sync over Power over Ethernet and integrated surge suppression on the controller board for up to 8 APs or BHs. Both a custom 30 VDC power scheme and a custom 56 VDC power scheme are available. Neither is the same as the later IEEE Standard 802.3af, and neither is compatible with it. Managed switching using a hardened EtherWAN switch (1090CKHH models). The CMM4 ships with a 14-port EtherWAN switch and is also available without a switch. The CMM4 originally shipped with a 9-port EtherWAN switch. Surge suppression on the controller board for the incoming 30V DC and 56V DC power lines and GPS coax cable. Auto-negotiation on the Ethernet ports. Ports will auto-negotiate to match inputs that are either 100Base-T or 10Base-T, and either full duplex or half duplex, when the connected device is set to auto-negotiate. Alternatively, these parameters are settable. An always-on NTP (Network Time Protocol) server that can provide date and time to any radio that can reach the CMMs management IP address. CNUT can be used to upgrade the CMM-4 software. 450 Series and 450i Series can use the CMM4s EtherWan switch for their network connectivity. Note The 56 V of a CMM4 needs to go through the adapter cable (part number N000045L001A) as shown in Figure 34 on page 2-52. A CMM4 56V power adapter cable can be prepared by swapping pins 5 and 7. See CMM4 56 V power adapter cable pinout on page 2-52 for power adapter cable pinout. Page 6-64 Chapter 6: Installation Supplemental installation information Supplemental installation information This section contains detailed installation procedures that are not included in the above topics, such as how to strip cables, create grounding points and weatherproof connectors. Stripping drop cable When preparing the drop cable for connection to the 450 Platform Family ODU or LPU, use the following measurements:

When preparing the drop cable for connection to the 450 Platform PSU (without a cable gland), use the following measurements:

Page 6-65 Chapter 6: Installation Supplemental installation information Creating a drop cable grounding point Use this procedure to connect the screen of the main drop cable to the metal of the supporting structure using the cable grounding kit (Cambium part number 01010419001). To identify suitable grounding points, refer to Hazardous locations on page 3-15. 1 Remove 60 mm (2.5 inches) of the drop cable outer sheath. 2 Cut 38mm (1.5 inches) of rubber tape (self-amalgamating) and fit to the ground cable lug. Wrap the tape completely around the lug and cable. 3 Fold the ground wire strap around the drop cable screen and fit cable ties. Page 6-66 Chapter 6: Installation Supplemental installation information 4 Tighten the cable ties with pliers. Cut the surplus from the cable ties. 5 Cut a 38mm (1.5 inches) section of self-amalgamating tape and wrap it completely around the joint between the drop and ground cables. 6 Use the remainder of the self-amalgamating tape to wrap the complete assembly. Press the tape edges together so that there are no gaps. Page 6-67 Chapter 6: Installation Supplemental installation information 7 Wrap a layer of PVC tape from bottom to top, starting from 25 mm (1 inch) below and finishing 25 mm (1 inch) above the edge of the self-amalgamating tape, overlapping at half width. 8 Repeat with a further four layers of PVC tape, always overlapping at half width. Wrap the layers in alternate directions (top to bottom, then bottom to top). The edges of each layer should be 25mm (1 inch) above (A) and 25 mm (1 inch) below (B) the previous layer. 9 Prepare the metal grounding point of the supporting structure to provide a good electrical contact with the grounding cable clamp. Remove paint, grease or dirt, if present. Apply anti-oxidant compound liberally between the two metals. 10 Clamp the bottom lug of the grounding cable to the supporting structure using site approved methods. Use a two-hole lug secured with fasteners in both holes. This provides better protection than a single-hole lug. Page 6-68 Chapter 6: Installation Supplemental installation information Attaching and weatherproofing an N type connector The following procedure should be used to weatherproof the N type connectors fitted to the connectorized ODU (AP/SM/BH) and antenna. This procedure must be followed to ensure that there is no moisture ingress at the radio ports. Failure to properly seal N-type antenna connectors can result in poor link performance or complete loss of radio communication. Note Cambium recommends to assemble the antenna, attach the ODU and cabling, and to seal the RF connections before installing the unit at the deployment site. Note N type connectors should be tightened using a torque wrench, set to 15 lb in or 1.7 Nm. If a torque wrench is not available, N type connectors may be finger tightened. Use this procedure to weatherproof the N type connectors fitted to the connectorized ODU and external antenna (if recommended by the antenna manufacturer). 1 Ensure the connection is tight. A torque wrench should be used if available:

2 Wrap the connection with a layer of 19 mm (0.75 inch) PVC tape, starting 25 mm (1 inch) below the connector body. Overlap the tape to half-width and extend the wrapping to the body of the LPU. Avoid making creases or wrinkles:

Page 6-69 Chapter 6: Installation 3 Smooth the tape edges:

Supplemental installation information 4 Cut a 125mm (5 inches) length of rubber tape (self-amalgamating):

5 Expand the width of the tape by stretching it so that it will wrap completely around the connector and cable:

6 Press the tape edges together so that there are no gaps. The tape should extend 25 mm (1 inch) beyond the PVC tape:

Page 6-70 Chapter 6: Installation Supplemental installation information 7 Wrap a layer of 50 mm (2 inch) PVC tape from bottom to top, starting from 25 mm (1 inch) below the edge of the self-amalgamating tape, overlapping at half width. 8 Repeat with a further four layers of 19 mm (0.75 inch) PVC tape, always overlapping at half width. Wrap the layers in alternate directions:

Second layer: top to bottom. Third layer: bottom to top. Fourth layer: top to bottom. Fifth layer: bottom to top. The bottom edge of each layer should be 25 mm (1 inch) below the previous layer. 9 Check the completed weatherproof connection:

Note A video of this procedure can be found at:

https://www.youtube.com/watch?v=a-twPfCVq4A Page 6-71 Chapter 7: Configuration This chapter describes how to use the web interface to configure the 450 Platform link. This chapter contains the following topics:

Preparing for configuration on page 7-2 Connecting to the unit on page 7-3 Using the web interface on page 7-5 Quick link setup on page 7-11 Configuring IP and Ethernet interfaces on page 7-22 Upgrading the software version and using CNUT on page 7-64 General configuration on page 7-68 Configuring Unit Settings page on page 7-91 Setting up time and date on page 7-95 Configuring synchronization on page 7-97 Configuring security on page 7-99 Configuring radio parameters on page 7-126 Setting up SNMP agent on page 7-180 Configuring syslog on page 7-188 Configuring remote access on page 7-194 Monitoring the Link on page 7-195 Configuring quality of service on page 7-198 Zero Touch Configuration Using DHCP Option 66 on page 7-212 Configuring Radio via config file on page 7-218 Configuring a RADIUS server on page 7-226 Installation Color Code on page 7-211 Page 7-1 Chapter 7: Configuration Preparing for configuration Preparing for configuration This section describes the checks to be performed before proceeding with unit configuration and antenna alignment. Safety precautions All national and local safety standards must be followed while configuring the units and aligning the antennas. Warning Ensure that personnel are not exposed to unsafe levels of RF energy. The units start to radiate RF energy as soon as they are powered up. Respect the safety standards defined in Compliance with safety standards on page 4-22, in particular the minimum separation distances. Observe the following guidelines:

Never work in front of the antenna when the ODU is powered. Always power down the PSU before connecting or disconnecting the drop cable from the PSU, ODU or LPU. Regulatory compliance All applicable radio regulations must be followed while configuring the units and aligning the antennas. For more information, refer to Compliance with radio regulations on page 4-34. Caution If the system designer has provided a list of channels to be barred for TDWR radar avoidance, the affected channels must be barred before the units are allowed to radiate on site, otherwise the regulations will be infringed. Attention Si le concepteur du systme a fourni une liste de canaux interdire pour viter les radars TDWR, les cannaux concernes doivent tre interdits avant que les units sont autorises mettre sur le site, sinon la rglementation peut tre enfreinte. Page 7-2 Chapter 7: Configuration Connecting to the unit Connecting to the unit This section describes how to connect the unit to a management PC and power it up. Configuring the management PC Use this procedure to configure the local management PC to communicate with the 450 Platform ODU. Procedure 9 Configuring the management PC 1 2 Select Properties for the Ethernet port. In Windows 7 this is found in Control Panel >

Network and Internet > Network Connections > Local Area Connection. Select Internet Protocol (TCP/IP):

3 Click Properties. Page 7-3 Chapter 7: Configuration Connecting to the unit 4 Enter an IP address that is valid for the 169.254.X.X network, avoiding 169.254.0.0 and 169.254.1.1. A good example is 169.254.1.3:

5 Enter a subnet mask of 255.255.0.0. Leave the default gateway blank. Connecting to the PC and powering up Use this procedure to connect a management PC and power up the 450 platform ODU. Procedure 10 Connecting to the PC and powering up 1 Check that the ODU and PSU are correctly connected. 2 Connect the PC Ethernet port to the LAN port of the PSU using a standard (not crossed) 3 4 Ethernet cable. Apply mains or battery power to the PSU. The green Power LED should illuminate continuously. After about several seconds, check that the orange Ethernet LED starts with 10 slow flashes. 5 Check that the Ethernet LED then illuminates continuously. Page 7-4 Chapter 7: Configuration Using the web interface Using the web interface This section describes how to log into the 450 Platform Family web interface and use its menus. Logging into the web interface Use this procedure to log into the web interface as a system administrator. Procedure 11 Logging into the web interface 1 Start the web browser from the management PC. 2 Type the IP address of the unit into the address bar. The factory default IP address is 169.254.1.1. Press ENTER. The web interface menu and System Summary page are displayed:

Page 7-5 Chapter 7: Configuration 3 On left hand side of home page, the login information is displayed:

Using the web interface 4 Enter Username (factory default username is admin) and Password (factory default password is admin) and click Login. Web GUI 1 1 2 3 Field Name Main Manu Menu Option Description Click an option in side navigation bar (area marked as 1). Multiple options in sub-navigation bars appear Click top sub-navigation bar to choose one configuration page (area marked as 2) Parameter To configure the parameters (e.g. area marked as 3) Press "Save Changes" to confirm and save the changes To reboot the ODU Page 7-6 Chapter 7: Configuration Using the web interface Using the menu options Use the menu navigation bar in the left panel to navigate to each web page. Some of the menu options are only displayed for specific system configurations. Use Table 101 to locate information about using each web page. Table 101 Menu options and web pages Main menu Menu options General Status Session Status Event Log Network Interface Layer 2 Neighbors General IP Radio SNMP cnMaestro Quality of Service (QoS) Security Time Applicable module Description All Viewing General Status on page 9-2 AP, BHM Viewing Session Status on page 9-20 All Interpreting messages in the Event Log on page 9-29 AP, BHM Viewing the Network Interface on page 9-32 All All All All All All All All Viewing the Layer 2 Neighbors on page 9-32 General configuration on page 7-68 Configuring IP and Ethernet interfaces on page 7-22 Configuring radio parameters on page 7-

127 Setting up SNMP agent on page 7-180 Configuring cnMaestroTM Connectivity on page 7-220 Configuring quality of service on page 7-

198 Configuring security on page 7-99 AP, BHM Setting up time and date Time page of 450 Platform Family -

AP/BHM on page 7-95 Page 7-7 Chapter 7: Configuration Using the web interface Menu options VLAN DiffServ Protocol Filtering Syslog Ping Watchdog Unit Setting Scheduler Main menu Registration Failures AP, BHM Bridge Control Block Bridging Table Ethernet Radio VLAN Data VC All All All All All All Throughput AP, BHM Filter ARP Overload SM SM All Page 7-8 Applicable module All All All All All All All Description VLAN configuration for PMP on page 7-

43 VLAN configuration for PTP on page 7-

53 IPv4 and IPv6 Prioritization on page 7-60 Filtering protocols and ports on page 7-

61 Configuring syslog on page 7-188 Configuring Ping Watchdog on page 7-

267 Configuring Unit Settings page on page 7-91 Viewing the Scheduler statistics on page 9-33 Viewing list of Registration Failures statistics on page 9-35 Interpreting Bridge Control Block statistics on page 9-19 Interpreting Bridging Table statistics on page 9-37 Interpreting Ethernet statistics on page 9-38 Interpreting RF Control Block statistics on page 9-41 Interpreting VLAN statistics on page 9-2 Interpreting Data VC statistics on page 9-4 Interpreting Throughput statistics on page 9-6 Interpreting Filter statistics on page 9-12 Viewing ARP statistics on page 9-13 Interpreting Overload statistics on page 9-9 Chapter 7: Configuration Using the web interface Menu options Syslog Statistics Translation Table DHCP Relay NAT Stats NAT DHCP Pass Through Statistics Sync Status PPPoE SNMPv3 Statistics Frame Utilization Link Capacity Test Spectrum Analyzer Remote Spectrum Analyzer Main menu Applicable module All SM SM SM SM AP AP SM All All All All Description Interpreting syslog statistics on page 9-

25 Interpreting Translation Table statistics on page 9-37 Interpreting DHCP Relay statistics on page 9-10 Viewing NAT statistics on page 9-13 Viewing NAT DHCP Statistics on page 9-15 Interpreting Pass Through Statistics on page 9-22 Interpreting Sync Status statistics on page 9-16 Interpreting PPPoE Statistics for Customer Activities on page 9-17 Interpreting SNMPv3 Statistics on page 9-23 Interpreting Frame Utilization statistics on page 9-23 Using the Link Capacity Test tool on page 8-21 Spectrum Analyzer tool on page 8-3 Remote Spectrum Analyzer tool on page 8-11 Using AP Evaluation tool on page 8-31 Using BHM Evaluation tool on page 8-35 Using the Subscriber Configuration tool on page 8-43 Using the OFDM Frame Calculator tool on page 8-39 AP/BHM Evaluation SM, BHS Subscriber Configuration AP OFDM Frame Calculator AP, BHM BER results Alignment Tool SM Using BER Results tool on page 8-49 SM, BHS Using the Alignment Tool on page 8-14 Page 7-9 Chapter 7: Configuration Using the web interface Main menu Menu options Link Status Sessions Ping Test Change User Setting Add user Delete User User Quick Start Applicable module AP Description Using the Link Status tool on page 8-44 AP All Using the Sessions tool on page 8-50 Using the Ping Test tool on page 8-51 Changing a User Setting on page 7-101 Adding a User for Access to a module on page 7-100 Deleting a User from Access to a module on page 7-101 Users account on page 7-102 AP, BHM Quick link setup on page 7-11 Region Settings AP, BHM Quick link setup on page 7-11 Radio Carrier Frequency AP, BHM Quick link setup on page 7-11 Synchronization LAN IP Address AP, BHM Quick link setup on page 7-11 AP, BHM Quick link setup on page 7-11 Review and Save Configuration AP, BHM Quick link setup on page 7-11 Quick Status Spectrum Results (PDA) Information BHM Evaluation AIM SM SM SM SM SM Page 7-10 The PDA web-page includes 320 x 240 pixel formatted displays of information important to installation and alignment for installers using legacy PDA devices. All device web pages are compatible with touch devices such as smart phones and tablets. Chapter 7: Configuration Using the web interface Main menu Menu options Copyright Notices Applicable module All All Description The Copyright web-page displays pertinent device copyright information. Page 7-11 Chapter 7: Configuration Quick link setup Quick link setup This section describes how to use the Quick Start Wizard to complete the essential system configuration tasks that must be performed on a PMP/PTP configuration. Note If the IP address of the AP or BHM is not known, See Radio recovery mode on page 1-26. Initiating Quick Start Wizard Applicable products PMP : AP PTP: BHM To start with Quick Start Wizard: after logging into the web management interface click the Quick Start button on the left side of main menu bar. The AP/BHM responds by opening the Quick Start page. Figure 119 Disarm Installation page (top and bottom of page shown) Quick Start is a wizard that helps you to perform a basic configuration that places an AP/BHM into service. Only the following parameters must be configured:

Region Code RF Carrier Frequency Synchronization LAN (Network) IP Address In each Quick Start page, you can specify the settings to satisfy the requirements of the network. review the configuration selected. Page 7-12 Chapter 7: Configuration save the configuration to non-volatile memory. Procedure 12 Quick start wizard 1 2 At the bottom of the Quick Start tab, click the Go To Next Page button. From the pull-down menu, select the region in which the AP will operate. Figure 120 Regional Settings tab of AP/BHM Quick link setup 3 Click the Go To Next Page button. Page 7-13 Chapter 7: Configuration Quick link setup 4 From the pull-down menu, select a frequency for the test. Figure 121 Radio Carrier Frequency tab of AP/BHM 5 Click the Go To Next Page button. Page 7-14 Chapter 7: Configuration Quick link setup 6 At the bottom of this tab, select Generate Sync Signal. Figure 122 Synchronization tab of AP/BHM 7 Click the Go To Next Page button. Page 7-15 Chapter 7: Configuration Quick link setup 8 At the bottom of the IP address configuration tab, either specify an IP Address, a Subnet Mask, and a Gateway IP Address for management of the AP and leave the DHCP state set to Disabled. set the DHCP state to Enabled to have the IP address, subnet mask, and gateway IP address automatically configured by a domain name server (DNS). Figure 123 LAN IP Address tab of the AP/BHM Note Cambium encourages you to experiment with the interface. Unless you save a configuration and reboot the AP after you save the configuration, none of the changes are affected. 9 Click the Go To Next Page => button. Page 7-16 Chapter 7: Configuration Quick link setup 10 Ensure that the initial parameters for the AP are set as you intended. Figure 124 Review and Save Configuration tab of the AP/BHM 11 Click the Save Changes button. 12 Click the Reboot button. RESULT: The AP responds with the message Reboot Has Been Initiated Page 7-17 Chapter 7: Configuration Quick link setup 13 Wait until the indicator LEDs are not red. 14 15 Wait until the red indicator LEDs are not lit. Trigger your browser to refresh the page until the AP redisplays the General Status tab. Configuring time settings Applicable products PMP : AP PTP: BHM To proceed with the test setup, click the Configuration link on the left side of the General Status page. When the AP responds by opening the Configuration page to the General page, click the Time tab. Figure 125 Time tab of the AP/BHM To have each log in the AP/BHM correlated to a meaningful time and date, either a reliable network element must pass time and date to the AP/BHM or you must set the time and date whenever a power cycle of the AP/BHM has occurred. A network element passes time and date in any of the following scenarios:

A connected CMM4 passes time and date (GPS time and date, if received). A separate NTP server is addressable from the AP/BHM. If the AP/BHM should obtain time and date from a CMM4, or a separate NTP server, enter the IP address of the CMM4 or NTP server on this tab. To force the AP/BHM to obtain time and date before the first (or next) 15-minute interval query of the NTP server, click Get Time through NTP. Page 7-18 Chapter 7: Configuration If you enter a time and date, the format for entry is Figure 126 Time and date entry formats Quick link setup Time :

hh MM

/

/

mm dd

/

/

ss yyyy Date :

where hh mm ss MM dd yyyy represents the two-digit hour in the range 00 to 24 represents the two-digit minute represents the two-digit second represents the two-digit month represents the two-digit day represents the four-digit year Proceed with the time setup as follows. Procedure 13 Entering AP/BHM time setup information 1 2 Enter the appropriate information in the format shown above. Then click the Set Time and Date button. Note The time displayed at the top of this page is static unless your browser is set to automatically refresh Powering the SM/BHS for test Procedure 14 Powering the SM/BHS for test 1 2 3 4 5 In one hand, securely hold the top (larger shell) of the SM/BHS. With the other hand, depress the lever in the back of the base cover (smaller shell). Remove the base cover. Plug one end of a CAT 5 Ethernet cable into the SM PSU port Plug the other end of the Ethernet cable into the jack in the pig tail that hangs from the power supply Roughly aim the SM/BHS toward the AP/BHM Plug the power supply into an electrical outlet Warning From this point until you remove power from the AP/BHM, stay at least as far from the AP/BHM as the minimum separation distance specified in Calculated distances and power compliance margins. 6 Repeat the foregoing steps for each SM/BHS that you wish to include in the test. Page 7-19 Chapter 7: Configuration Quick link setup Viewing the Session Status of the AP/BHM to determine test registration Once the SMs/BHS under test are powered on, return to the computing device to determine if the SM/BHS units have registered to the AP/BHM. Note In order for accurate power level readings to be displayed, traffic must be present on the radio link. The Session Status tab provides information about each SM/BHS that has registered to the AP/BHM. This information is useful for managing and troubleshooting a system. All information that you have entered in the Site Name field of the SM/BHS displays in the Session Status tab of the linked AP/BHM. The Session Status tab also includes the current active values on each SM( or BHS) (LUID) for MIR, and VLAN, as well as the source of these values (representing the SM/BHS itself, Authentication Server, or the AP/BHM and cap, if anyfor example, APCAP as shown above).. As an SM/BHS registers to the AP/BHM, the configuration source that this page displays for the associated LUID may change. After registration, however, the displayed source is stable and can be trusted. Idle subscribers may be included or removed from the session status display by enabling or disabling, respectively, the Show Idle Sessions parameter. Enabling or disabling this parameter only affects the GUI display of subscribers, not the registration status. The SessionStatus.xml hyperlink allows user to export session status page from web management interface of AP/BHM. The session status page will be exported in xml file. Page 7-20 Chapter 7: Configuration Procedure 15 Viewing the AP Session Status page Quick link setup 1 On the AP web management GUI, navigate to Home, Session Status:

Figure 127 Session Status tab of AP Note Session status page for BHM is same as AP. 2 Verify that for each SM (or BHS) MAC address (printed on the SM/BHS housing) the AP/BHM has established a registered session by verifying the State status of each entry. The Session Status page of the AP/BHM is explained in Table 102. Page 7-21 Chapter 7: Configuration Table 102 Session Status Attributes AP Quick link setup Meaning Idle subscribers may be included or removed from the session status display by enabling or disabling, respectively, the Show Idle Sessions parameter. Enabling or disabling this parameter only affects the GUI display of subscribers, not the registration status. This field displays date and time stamp of last session counter reset. This field displays date and time stamp of last Idle SMs Removed. On click of Remove Idle SMs button, all the SMs which are in Idle state are flushed out. See Exporting Session Status page of AP/BHM on page 7-209 See Device tab on page 9-20 See Session tab on page 9-21 See Power tab on page 9-23 See Configuration tab on page 9-25 Attribute Show Idle Sessions Last Session Counter Reset Last Time Idle SMs Removed Data Device tab Session tab Power tab Configuration tab Page 7-22 Chapter 7: Configuration Configuring IP and Ethernet interfaces Configuring IP and Ethernet interfaces IP interface with NAT disabled on page 7-32 IP interface with NAT enabled on page This task consists of the following sections:

Configuring the IP interface on page 7-23 Auxiliary port on page 7-26 NAT, DHCP Server, DHCP Client and DMZ on page 7-27 NAT tab with NAT disabled on page 7-35 NAT tab with NAT enabled on page 7-37 NAT DNS Considerations on page 7-42 DHCP BHS on page 7-43 VLAN configuration for PMP on page 7-43 VLAN page of AP on page 7-46 VLAN page of SM on page 7-49 VLAN Membership tab of SM on page 7-53 VLAN configuration for PTP on page 7-53 NAT Port Mapping tab - SM on page 7-42 Page 7-23 Chapter 7: Configuration Configuring IP and Ethernet interfaces Configuring the IP interface The IP interface allows users to connect to the 450 Platform Family web interface, either from a locally connected computer or from a management network. Applicable products PTP: BHM BMS PMP : AP SM To configure the IP interface, follow these instructions:

Procedure 16 Configuring the AP/BHM IP interface 1 Select menu option Configuration > IP. The LAN configuration page is displayed:

2 3 4 Update IP Address, Subnet Mask and Gateway IP Address to meet network requirements (as specified by the network administrator). Review the other IP interface attributes and update them, if necessary (see Table 103 IP interface attributes). Click Save. Reboot Required message is displayed:

5 Click Reboot. The IP page of AP/SM/BHM/BHS is explained in Table 103. Page 7-24 Chapter 7: Configuration Table 103 IP interface attributes Configuring IP and Ethernet interfaces Attribute IP Address Subnet Mask Gateway IP Address DHCP state DNS IP Address Meaning Internet Protocol (IP) address. This address is used by family of Internet protocols to uniquely identify this unit on a network. Defines the address range of the connected IP network. The IP address of a computer on the current network that acts as a gateway. A gateway acts as an entrance and exit to packets from and to other networks. If Enabled is selected, the DHCP server automatically assigns the IP configuration (IP address, subnet mask, and gateway IP address) and the values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable (read only), in the Network Interface tab of the Home page. Canopy devices allow for configuration of a preferred and alternate DNS server IP address either automatically or manually. Devices must set DNS server IP address manually when DHCP is disabled for the management Page 7-25 Chapter 7: Configuration Configuring IP and Ethernet interfaces interface of the device. DNS servers may be configured automatically from the DHCP response when DHCP is enabled for the management interface of the device. Optionally devices may be configured to set the DNS server IP address manually when DHCP is enabled for the management interface. The default DNS IP addresses are 0.0.0.0 when configured manually. Preferred DNS Server The first address used for DNS resolution. Alternate DNS Server Domain Name Advanced LAN1 IP Configuration Default alternate LAN1 IP address If the Preferred DNS server cannot be reached, the Alternate DNS Server is used. The operators management domain name may be configured for DNS. The domain name configuration can be used for configuration of the servers in the operators network. The default domain name is example.com, and is only used if configured as such. Hardcoded default alternate IP address (169.254.1.1) that is available only when connected to the Ethernet port. When enabled, user can configure a second IP address for the bridge which is other than the hardcoded IP address (169.254.1.1). AUX Ethernet Port AUX Ethernet Port Enabled: Data is enabled for Auxiliary port Disabled: Data is disabled for Auxiliary port AUX Ethernet Port AUX Ethernet Port PoE LAN2 Network Interface Configuration (Radio Private Interface) IP Address Enabled: PoE out is enable for Auxiliary port Disabled: PoE out is disabled for Auxiliary port It is recommended not to change this parameter from the default AP/BHM private IP address of 192.168.101.1. A /24 CIDR subnet is used to communicate with each of the SMs/BHS that are registered. The AP/BHM uses a combination of the private IP and the LUID (logical unit ID) of the SM/BHS. It is only displayed for AP and BHM. Table 104 SM/BHS private IP and LUID LUID SM/BHS First SM/BHS registered 2 Private IP 192.168.101.2 Second SM/BHS registered 3 192.168.101.3 Page 7-26 Chapter 7: Configuration Configuring IP and Ethernet interfaces Auxiliary port An additional Ethernet port labeled Aux for Auxiliary port is implemented for downstream traffic. This feature is supported only for PTP/PMP 450i ODUs. To enable the Aux port, follow these instructions:

Procedure 17 Enabling Aux port interface 1 Select menu option Configuration > IP > Aux Network Interface tab.:

Click Enable button of Aux Ethernet Port parameter to enable Aux Ethernet port Click Enable button of Aux Ethernet Port PoE parameter to enable Aux port PoE out. Click Save. Reboot Required message is displayed. Click Reboot. 2 3 4 5 Table 105 Aux port attributes Attribute Aux Ethernet Port Meaning Enabled: Data is enabled for Auxiliary port Disabled: Data is disabled for Auxiliary port Aux Ethernet Port PoE Enabled: PoE out is enable for Auxiliary port Disabled: PoE out is disabled for Auxiliary port By disabling this feature, the data at the Auxiliary port will be disabled. Page 7-27 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT, DHCP Server, DHCP Client and DMZ Applicable products PMP :

SM The system provides NAT (Network Address Translation) for SMs in the following combinations of NAT and DHCP (Dynamic Host Configuration Protocol):

NAT Disabled NAT with DHCP Client (DHCP selected as the Connection Type of the WAN interface) and DHCP Server NAT with DHCP Client(DHCP selected as the Connection Type of the WAN interface) NAT with DHCP Server NAT without DHCP NAT NAT isolates devices connected to the Ethernet or wired side of a SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic (separate from its address for management), terminates transport traffic and allows you to assign a range of IP addresses to devices that are connected to the Ethernet or wired side of the SM. In the Cambium system, NAT supports many protocols, including HTTP, ICMP (Internet Control Message Protocols), and FTP (File Transfer Protocol). For virtual private network (VPN) implementation, L2TP over IPSec (Level 2 Tunneling Protocol over IP Security) and PPTP (Point to Point Tunneling Protocol) are supported. Note When NAT is enabled, a reduction in throughput is introduced in the system (due to processing overhead). DHCP DHCP enables a device to be assigned a new IP address and TCP/IP parameters, including a default gateway, whenever the device reboots. Thus DHCP reduces configuration time, conserves IP addresses, and allows modules to be moved to a different network within the Cambium system. In conjunction with the NAT features, each SM provides the following:

A DHCP server that assigns IP addresses to computers connected to the SM by Ethernet protocol. A DHCP client that receives an IP address for the SM from a network DHCP server. DMZ In conjunction with the NAT features, a DMZ (Demilitarized Zone) allows the allotment of one IP address behind the SM for a device to logically exist outside the firewall and receive network traffic. The first three octets of this IP address must be identical to the first three octets of the NAT private IP address. A DHCP server that assigns IP addresses to computers connected to the SM by Ethernet protocol. A DHCP client that receives an IP address for the SM from a network DHCP server. Page 7-28 Configuring IP and Ethernet interfaces Chapter 7: Configuration NAT Disabled The NAT Disabled implementation is illustrated in Figure 128. Figure 128 NAT disabled implementation NAT with DHCP Client and DHCP Server The NAT with DHCP Client and DHCP server is illustrated in Figure 129. Page 7-29 Chapter 7: Configuration Configuring IP and Ethernet interfaces Figure 129 NAT with DHCP client and DHCP server implementation NAT with DHCP Client Figure 130 NAT with DHCP client implementation Page 7-30 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT with DHCP Server Figure 131 NAT with DHCP server implementation NAT without DHCP Figure 132 NAT without DHCP implementation Page 7-31 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT and VPNs VPN technology provides the benefits of a private network during communication over a public network. One typical use of a VPN is to connect employees remotely (who are at home or in a different city), with their corporate network through a public Internet. Any of several VPN implementation schemes is possible. By design, NAT translates or changes addresses, and thus interferes with a VPN that is not specifically supported by a given NAT implementation. With NAT enabled, SM supports L2TP over IPSec (Level 2 Tunneling Protocol over IP Security) VPNs and PPTP (Point to Point Tunneling Protocol) VPNs. With NAT disabled, SM supports all types of VPNs. Page 7-32 Chapter 7: Configuration Configuring IP and Ethernet interfaces IP interface with NAT disabled - SM The IP page of SM with NAT disabled is explained in Table 106. Table 106 IP attributes - SM with NAT disabled Attribute IP Address Network Accessibility Subnet Mask Gateway IP Address DHCP state Meaning Enter the non-routable IP address to associate with the Ethernet connection on this SM. (The default IP address from the factory is 169.254.1.1.) If you forget this parameter, you must both:

physically access the module. use recovery mode to access the module configuration parameters at 169.254.1.1. See Radio recovery mode on page 1-26 Note Note or print the IP settings from this page. Ensure that you can readily associate these IP settings both with the module and with the other data that you store about the module. Specify whether the IP address of the SM must be visible to only a device connected to the SM by Ethernet (Local) or be visible to the AP/BHM as well

(Public). Enter an appropriate subnet mask for the SM to communicate on the network. The default subnet mask is 255.255.0.0. Enter the appropriate gateway for the SM to communicate with the network. The default gateway is 169.254.0.0. If you select Enabled, the DHCP server automatically assigns the IP configuration (IP address, subnet mask, and gateway IP address) and the values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable, but not settable, in the Network Interface tab of the Home page. In this tab, DHCP State is settable only if the Network Accessibility parameter in the IP tab is set to Public. This parameter is also settable in the NAT tab of the Configuration web page, but only when NAT is enabled. Page 7-33 Chapter 7: Configuration Configuring IP and Ethernet interfaces DHCP DNS IP Address If the DHCP state parameter is set to Enabled in the Configuration > IP sub-menu of the SM/BHS, do not check the BootpClient option for Packet Filter Types in its Protocol Filtering tab, because doing so can block the DHCP request. (Filters apply to all packets that leave the SM via its RF interface, including those that the SM itself generates.) If you want to keep DHCP enabled and avoid the blocking scenario, select the Bootp Server option instead. This will result in responses being appropriately filtered and discarded. Canopy devices allow for configuration of a preferred and alternate DNS server IP address either automatically or manually. Devices must set DNS server IP address manually when DHCP is disabled for the management interface of the device. DNS servers may be configured automatically from the DHCP response when DHCP is enabled for the management interface of the device. Optionally devices may be configured to set the DNS server IP address manually when DHCP is enabled for the management interface. The default DNS IP addresses are 0.0.0.0 when configured manually. Preferred DNS Server The first DNS server used for DNS resolution. Alternate DNS Server Domain Name The second DNS server used for DNS resolution. The operators management domain name may be configured for DNS. The domain name configuration can be used for configuration of the servers in the operators network. The default domain name is example.com, and is only used if configured as such. Page 7-34 Chapter 7: Configuration Configuring IP and Ethernet interfaces IP interface with NAT enabled - SM The IP page of SM with NAT enabled is explained in Table 107. Table 107 IP attributes - SM with NAT enabled Meaning Assign an IP address for SM/BHS management through Ethernet access to the SM/BHS. Set only the first three bytes. The last byte is permanently set to 1. This address becomes the base for the range of DHCP-assigned addresses. Assign a subnet mask of 255.255.255.0 or a more restrictive subnet mask. Set only the last byte of this subnet mask. Each of the first three bytes is permanently set to 255. Attribute IP Address Subnet Mask Page 7-35 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT tab with NAT disabled - SM The NAT tab of SM with NAT disabled is explained in Table 108. Table 108 NAT attributes - SM with NAT disabled Page 7-36 Chapter 7: Configuration Configuring IP and Ethernet interfaces Attribute NAT Enable/Disable IP Address Subnet Mask Gateway IP Address ARP Cache Timeout TCP Session Garbage Timeout Meaning This parameter enables or disables the Network Address Translation (NAT) feature for the SM. NAT isolates devices connected to the Ethernet or wired side of a SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic separate from its address for management, terminates transport traffic, and allows you to assign a range of IP addresses to devices that are connected to the Ethernet or wired side of the SM. When NAT is enabled, VLANs are not supported on the wired side of that SM. You can enable NAT in SMs within a sector where VLAN is enabled in the AP/BHM, but this may constrain network design. This field displays the IP address for the SM. DHCP Server will not automatically assign this address when NAT is disabled. This field displays the subnet mask for the SM. DHCP Server will not automatically assign this address when NAT is disabled. This field displays the gateway IP address for the SM. DHCP Server will not automatically assign this address when NAT is disabled. If a router upstream has an ARP cache of longer duration (as some use 30 minutes), enter a value of longer duration than the router ARP cache. The default value of this field is 20 minutes. Where a large network exists behind the SM, you can set this parameter to lower than the default value of 120 minutes. This action makes additional resources available for greater traffic than the default value accommodates. You may adjust this parameter in the range of 1 to 1440 minutes, based on network performance. The default value of this parameter is 4 minutes. UDP Session Garbage Timeout Translation Table Size Total number of minutes that have elapsed since the last packet transfer between the connected device and the SM/BHS. Note When NAT is disabled, the following parameters are not required to be configurable:

WAN Inter face > Connection Type, IP Address, Subnet Mask, Gateway IP address LAN Interface > IP Address LAN DHCP Server > DHCP Server Enable/Disable, DHCP Server Lease Timeout, Number of IPs to Lease, DNS Server Proxy, DNS IP Address, Preferred DNS IP address, Alternate DNS IP address Remote Management Interface > Remote Management Interface, IP address, Subnet Mask, DHCP DNS IP Address, Preferred DNS Server, Alternate DNS Server, Domain Name NAT Protocol Parameters > ARP Cache Timeout, TCP Session Garbage Timeout, UDP Session Garbage Timeout, Translation Table Size Page 7-37 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT tab with NAT enabled - SM The NAT tab of SM with NAT enabled is explained in Table 109. Table 109 NAT attributes - SM with NAT enabled Page 7-38 Chapter 7: Configuration Attribute NAT Enable/Disable WAN Interface Connection Type Subnet Mask Gateway IP Address Reply to Ping on WAN Interface LAN Interface IP Address Subnet Mask DMZ Enable Configuring IP and Ethernet interfaces Meaning This parameter enables or disabled the Network Address Translation (NAT) feature for the SM. NAT isolates devices connected to the Ethernet or wired side of a SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic separate from its address for management, terminates transport traffic, and allows you to assign a range of IP addresses to devices that are connected to the Ethernet or wired side of the SM. When NAT is enabled, VLANs are not supported on the wired side of that SM. You can enable NAT in SMs within a sector where VLAN is enabled in the AP, but this may constrain network design. The WAN interface is the RF-side address for transport traffic. This parameter may be set to Static IPwhen this is the selection, all three parameters (IP Address, Subnet Mask, and Gateway IP Address) must be properly populated. DHCPwhen this is the selection, the information from the DHCP server configures the interface. PPPoEwhen this is the selection, the information from the PPPoE server configures the interface. If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the subnet mask of the SM for RF transport traffic. If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the gateway IP address for the SM for RF transport traffic. By default, the radio interface does not respond to pings. If you use a management system (such as WM) that will occasionally ping the SM, set this parameter to Enabled. The LAN interface is both the management access through the Ethernet port and the Ethernet-side address for transport traffic. When NAT is enabled, this interface is redundantly shown as the NAT Network Interface Configuration on the IP tab of the Configuration web page in the SM. Assign an IP address for SM/BHS management through Ethernet access to the SM. This address becomes the base for the range of DHCP-assigned addresses. Assign a subnet mask of 255.255.255.0 or a more restrictive subnet mask. Set only the last byte of this subnet mask. Each of the first three bytes is permanently set to 255. Either enable or disable DMZ for this SM/BHS. Page 7-39 Chapter 7: Configuration DMZ IP Address DHCP Server DHCP Server Enable/Disable DHCP Server Lease Timeout DHCP Start IP Number of IPs to Lease DNS Server Proxy DNS IP Address Preferred DNS IP Address Configuring IP and Ethernet interfaces If you enable DMZ in the parameter above, set the last byte of the DMZ host IP address to use for this SM when DMZ is enabled. Only one such address is allowed. The first three bytes are identical to those of the NAT private IP address. Ensure that the device that receives network traffic behind this SM is assigned this address. The system provides a warning if you enter an address within the range that DHCP can assign. This is the server (in the SM) that provides an IP address to the device connected to the Ethernet port of the SM. Select either Enabled or Disabled. Enable to:

Allow this SM to assign IP addresses, subnet masks, and gateway IP addresses to attached devices. Assign a start address for DHCP. Designate how many IP addresses may be temporarily used (leased). Disable to:

Restrict SM/BHS from assigning addresses to attached devices. Based on network performance, enter the number of days between when the DHCP server assigns an IP address and when that address expires. The range of values for this parameter is 1 to 30 days. The default value is 30 days. If you enable DHCP Server below, set the last byte of the starting IP address that the DHCP server assigns. The first three bytes are identical to those of the NAT private IP address. Enter how many IP addresses the DHCP server is allowed to assign. The default value is 50 addresses. This parameter enables or disables advertisement of the SM/BHS as the DNS server. On initial boot up of a SM with the NAT WAN interface configured as DHCP or PPPoE, the SM module will not have DNS information immediately. With DNS Server Proxy disabled, the clients will renew their lease about every minute until the SM has the DNS information to give out. At this point the SM will go to the full configured lease time period which is 30 days by default. With DNS Server Proxy enabled, the SM will give out full term leases with its NAT LAN IP as the DNS server. Select either:

Obtain Automatically to allow the system to set the IP address of the DNS server or Set Manually to enable yourself to set both a preferred and an alternate DNS IP address. Enter the preferred DNS IP address to use when the DNS IP Address parameter is set to Set Manually. Page 7-40 Chapter 7: Configuration Alternate DNS IP Address Remote Management Interface Configuring IP and Ethernet interfaces Enter the DNS IP address to use when the DNS IP Address parameter is set to Set Manually and no response is received from the preferred DNS IP address. To offer greater flexibility in IP address management, the NAT-enabled SMs configured WAN Interface IP address may now be used as the device Remote Management Interface (unless the SMs PPPoE client is set to Enabled) Disable: When this interface is set to Disable, the SM is not directly accessible by IP address. Management access is only possible through either the LAN (Ethernet) interface or a link from an AP web page into the WAN

(RF-side) interface. Enable (Standalone Config): When this interface is set to Enable

(Standalone Config), to manage the SM/BHS the device must be accessed by the IP addressing information provided in the Remote Configuration Interface section. Note When configuring PPPoE over the link, use this configuration option (PPPoE traffic is routed via the IP addressing specified in section Remote Configuration Interface). Enable (Use WAN Interface): When this interface is set to Enable (Use WAN Interface), the Remote Configuration Interface information is greyed out, and the SM is managed via the IP addressing specified in section WAN Interface). Note When using this configuration, the ports defined in section Configuration, Port Configuration are consumed by the device. For example, if FTP Port is configured as 21 by the SM, an FTP server situated below the SM must use a port other than 21. This also applies to DMZ devices; any ports specified in section Configuration, Port Configuration will not be translated through the NAT, they is consumed by the devices network stack for management. Connection Type IP Address Subnet Mask This parameter can be set to:

Static IPwhen this is the selection, all three parameters (IP Address, Subnet Mask, and Gateway IP Address) must be properly populated. DHCPwhen this is the selection, the information from the DHCP server configures the interface. If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the IP address of the SM for RF management traffic. If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the subnet mask of the SM for RF management traffic. Page 7-41 Chapter 7: Configuration Configuring IP and Ethernet interfaces Gateway IP Address DHCP DNS IP Address If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the gateway IP address for the SM for RF management traffic. Note or print the IP settings from this page. Ensure that you can readily associate these IP settings both with the module and with the other data that you store about the module. Select either:

Obtain Automatically to allow the system to set the IP address of the DNS server. or Set Manually to enable yourself to set both a preferred and an alternate DNS IP address. Preferred DNS Server Enter the preferred DNS IP address to use when the DNS IP Address parameter is set to Set Manually. Alternate DNS Server Enter the DNS IP address to use when the DNS IP Address parameter is set to Set Manually and no response is received from the preferred DNS IP address. Domain Name ARP Cache Timeout TCP Session Garbage Timeout Domain Name to use for management DNS configuration. This domain name may be concatenated to DNS names used configured for the remote configuration interface. If a router upstream has an ARP cache of longer duration (as some use 30 minutes), enter a value of longer duration than the router ARP cache. The default value of this field is 20 (minutes). Where a large network exists behind the SM, you can set this parameter to lower than the default value of 120 (minutes). This action makes additional resources available for greater traffic than the default value accommodates. UDP Session Garbage Timeout You may adjust this parameter in the range of 1 to 1440 minutes, based on network performance. The default value of this parameter is 4 (minutes). Page 7-42 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT DNS Considerations - SM SM DNS behavior is different depending on the accessibility of the SM. When NAT is enabled the DNS configuration that is discussed in this document is tied to the RF Remote Configuration Interface, which must be enabled to utilize DNS Client functionality. Note that the WAN DNS settings when NAT is enabled are unchanged with the addition of the management DNS feature discussed in this document. NAT Configuration Table 110 SM DNS Options with NAT Enabled Management Interface Accessibility RF Remote Management Interface Disabled NAT Enabled DHCP Status DNS Status N/A DNS Disabled RF Remote Management Interface Enabled DHCP Disabled DNS Static Configuration DHCP Enabled DNS from DHCP or DNS Static Configuration NAT Port Mapping tab - SM The NAT Port Mapping tab of the SM is explained in Table 111. Table 111 NAT Port Mapping attributes - SM Attribute Port Map 1 to 10 Meaning Separate parameters allow you to distinguish NAT ports from each other by assigning a unique combination of port number, protocol for traffic through the port, and IP address for access to the port Page 7-43 Chapter 7: Configuration DHCP BHS Configuring IP and Ethernet interfaces Applicable products PTP: BHM DHCP enables a device to be assigned a new IP address and TCP/IP parameters, including a default gateway, whenever the device reboots. Thus DHCP reduces configuration time, conserves IP addresses, and allows modules to be moved to a different network within the Cambium system. In conjunction with the NAT features, each BHS provides:

A DHCP server that assigns IP addresses to computers connected to the BHS by Ethernet protocol. A DHCP client that receives an IP address for the BHS from a network DHCP server. Reconnecting to the management PC If the IP Address, Subnet Mask and Gateway IP Address of the unit have been updated to meet network requirements, then reconfigure the local management PC to use an IP address that is valid for the network. See Configuring the management PC on page 7-3. Once the unit reboots, log in using the new IP address. See Logging into the web interface on page 7-5. VLAN configuration for PMP Applicable products PMP : AP SM VLAN Remarking VLAN Remarking feature allows the user to change the VLAN ID and priority of both upstream and downstream packets at the Ethernet Interface. The remarking configuration is available for:

1. VLAN ID re-marking 2. 802.1p priority re-marking Note For Q-in-Q VLAN tagged frame, re-marking is performed on the outer tag. Page 7-44 Chapter 7: Configuration Configuring IP and Ethernet interfaces VLAN ID Remarking SM supports the ability to re-mark the VLAN ID on both upstream and downstream VLAN frames at the Ethernet interface. For instance, a configuration can be added to re-mark VLAN ID x to VLAN ID y as shown in Table 112. AP does not support VLAN ID remarking. Table 112 VLAN Remarking Example VLAN frame direction Upstream Downstream Remarking SM receives VLAN ID x frame at the Ethernet interface, checks the configuration and re-marks to VLAN ID y. So VLAN ID y frame comes out of APs Ethernet interface. When SM re-marks, a dynamic entry in VLAN membership table for y is added to allow reception of VLAN ID y downstream packet. AP receives VLAN ID y frame at the Ethernet interface and sends to SM. SM accepts the frame as it has an entry in the membership table and re-marks to VLAN ID x. This reverse re- marking is necessary because the downstream devices do not know of re-marking and are expecting VLAN x frames. This remarking is done just before sending the packet out on Ethernet interface. 802.1P Remarking AP/BHM and SM/BHS allow re-marking of 802.1p priority bits for the frames received at the Ethernet interface. Priority bits are not re-marked for the packets sent out of Ethernet interface (reverse direction). Configuration must be added at SM/BHS for upstream frames and at AP/BHM for downstream frames. VLAN Priority Bits configuration VLAN Priority Bits Configuration feature allows the user to configure the three 802.1p bits upon assigning VLAN to an ingress packet. The priority bits configuration is available for:

Default Port VID Provider VID MAC Address mapped Port VID Management VID Default Port VID This VID is used for untagged frames and will correspond to the Q-Tag for 802.1Q frames (if VLAN Port Type is Q), or the C-Tag for 802.1ad frames (if the VLAN Port Type is QinQ). The priority bits used in the Q-tag/C-tag are configurable. The configuration can be:

Promote IPv4/IPv6 priority The priority in the IP header is copied to the Q-tag/C-tag. Page 7-45 Chapter 7: Configuration Configuring IP and Ethernet interfaces Define priority Specify the priority in the range of 0 to 7. This value is used as priority in the Q-

tag/C-tag. MAC Address Mapped VID If a packet arrives at the SM/BHS that is sourced from a device whose MAC address is in the table, then the corresponding VID is used for that frames Q-tag (Q port) or C-tag (QinQ port). The priority bits used in the Q-tag/C-tag are configurable similar to default port VID. Provider VID The provider VID is used for the S-tag. The priority bits used in the S-tag are configurable similar to default port VID. Provider VID has an extra priority configuration:

Copy inner tag 802.1p priority The priority in the C-tag is copied to the S-tag. Management VID This VID is used to communicate with AP/BHM and SM/BHS for management purposes. The priority bits used in the Q-tag are configurable similar to default port VID. Use APs Management VID for ICC connected SM This feature allows the SM to use the APs management VLAN ID when the SM is registered to the AP via ICC. This feature is useful for the customer who uses a different management VID for the SM and AP and Zero Touch feature is enabled for configuration. This parameter may be accessed via the Configuration > VLAN page on the APs web management interface. Page 7-46 Chapter 7: Configuration Configuring IP and Ethernet interfaces VLAN page of AP The VLAN tab of the AP/BHM is explained in Table 113. Table 113 AP/BHM VLAN tab attributes Attribute VLAN Always use Local VLAN Config Allow Frame Types Dynamic Learning Meaning Specify whether VLAN functionality for the AP and all linked SMs must

(Enabled) or may not (Disabled) be allowed. The default value is Disabled. Enable this option before you reboot this AP as a SM to use it to perform spectrum analysis. Once the spectrum analysis completes, disable this option before you reboot the module as an AP, Select the type of arriving frames that the AP must tag, using the VID that is stored in the Untagged Ingress VID parameter. The default value is All Frames. Specify whether the AP must (Enabled) or not (Disabled) add the VLAN IDs

(VIDs) of upstream frames to the VID table. (The AP passes frames with VIDs that are stored in the table both upstream and downstream.). The default value is Enabled. Page 7-47 Chapter 7: Configuration Configuring IP and Ethernet interfaces VLAN Aging Timeout Specify how long the AP must keep dynamically learned VIDs. The range of values is 5 to 1440 (minutes). The default value is 25 (minutes). Management VID QinQ EtherType Use AP's Management VID for ICC connected SM VLAN Not Active Note VIDs that you enter for the Management VID and VLAN Membership parameters do not time out. Enter the VID that the operator wishes to use to communicate with the module manager. The range of values is 1 to 4095. The default value is 1. Modules can be configured with 802.1ad Q-in-Q DVLAN (Double-VLAN) tagging which is a way for an operator to put an 802.1Q VLAN inside of an 802.1ad VLAN. A nested VLAN, which is the original 802.1Q tag and a new second 802.1ad tag, allows for bridging of VLAN traffic across a network and segregates the broadcast domains of 802.1Q VLANs. Q-in-Q can be used with PPPoE and/or NAT. The 802.1ad standard defines the S-VLAN as the Service Provider VLAN and the C-VLAN as the customer VLAN. The radio software does 2 layer Q-in-Q whereby the C-VLAN is the 802.1Q tag and the S-VLAN is the second layer Q tag as shown below:

Table 114 Q-in-Q Ethernet frame S-VLAN EthType Ethernet Header 0x88a8 C-VLAN EthType 0x8100 IP Data EthType 0x0800 The 802.1ad S-VLAN is the outer VLAN that is configurable on the Configuration > VLAN web page of the AP. The Q-in-Q EtherType parameter is configured with a default EtherType of 0x88a8 in addition to four alternate EtherTypes that can be configured to aid in interoperability with existing networks that use a different EtherType than the default. The C-VLAN is the inner VLAN tag, which is the same as 802.1Q. As a top level concept, this operates on the outermost tag at any given time, either pushing a tag on or popping a tag off. This means packets will at most transition from an 802.1Q frame to an 801.ad frame (with a tag pushed on) or an untagged 802.1 frame (with the tag popped off. Similarly, for an 802.1ad frame, this can only transition from an 802.1ad frame to an 802.1Q frame (with the tag popped off) since the radio software only supports 2 levels of tags This field allows the SM to use the APs management VLAN ID when the SM is registered to the AP via ICC. When VLAN is enabled in the AP, the Active Configuration block provides the following details as read-only information in this tab. In the Cambium fixed wireless broadband IP network, each device of any type is automatically a permanent member of VID 1. This facilitates deployment of devices that have VLAN enabled with those that do not. Page 7-48 Chapter 7: Configuration Configuring IP and Ethernet interfaces VLAN Membership Table Configuration VLAN Membership table Source VLAN (Range:

1-4094) Remark Priority

(Range 0-7) VLAN Remarking table For each VLAN in which you want the AP to be a member, enter the VLAN ID and then click the Add Member button. Similarly, for any VLAN in which you want the AP to no longer be a member, enter the VLAN ID and then click the Remove Member button. This field lists the VLANs that an AP is a member of. As the user adds a number between 1 and 4094, this number is populated here. Enter the VID for which the operator wishes to remark the 802.1p priority for the downstream packets. The range of values is 1 to 4094. The default value is 1. This is the priority you can assign to the VLAN Tagged packet. Priority of 0 is the highest. As the user enters a VLAN and a Remarking priority, this information is added in this table. Page 7-49 Chapter 7: Configuration Configuring IP and Ethernet interfaces VLAN page of SM The VLAN tab of SM/BHS is explained in Table 115. Table 115 SM VLAN attributes Attribute VLAN Port Type Meaning By default this is Q, indicating that it is to operate in the existing manner. The other option is Q-in-Q, which indicates that it must be adding and removing the S-Tag, and adding a C-Tag if necessary for untagged packets. The VLAN Port type corresponds to the Ethernet port of the SM/BHS. Currently, the internal management interfaces will always operate as Q ports. Page 7-50 Chapter 7: Configuration Accept QinQ Frames Allow Frame Types Dynamic Learning VLAN Aging Timeout Management VID SM Management VID Pass-through Default Port VID Configuring IP and Ethernet interfaces This option is valid for the Q-in-Q port so that the user may force blocking of existing 802.1ad Q-in-Q frames. This way, only untagged or single tagged packets will come in and out of the Ethernet interface. If a Q-in-Q frame is about ingress or egress the Ethernet interface and this is disabled, it is dropped and a filter entry will show up on the VLAN Statistics page as DVLAN Egress or DVLAN Ingress. Select the type of arriving frames that the SM must tag, using the VID that is stored in the Untagged Ingress VID parameter. The default value is All Frames. Tagged Frames Only: The SM only tags incoming VLAN-tagged frames Untagged Frames Only: The SM will only tag incoming untagged frames Specify whether the SM must (Enable) or not (Disable) add the VIDs of upstream frames (that enter the SM through the wired Ethernet interface) to the VID table. The default value is Enable. Specify how long the SM/BHS must keep dynamically learned VIDs. The range of values is 5 to 1440 (minutes). The default value is 25 (minutes). Note VIDs that you enter for the Untagged Ingress VID and Management VID parameters do not time out. Enter the VID that the SM/BHS must share with the AP/BHM. The range of values is 1 to 4095. The default value is 1. Specify whether to allow the SM/BHS (Enabled) or the AP/RADIUS

(Disabled) to control the VLAN settings of this SM. The default value is Enabled. When VLAN is enabled in the AP to whom this SM is registered, the Active Configuration block provides the following details as read-only information in this tab. In the Cambium fixed wireless broadband IP network, each device of any type is automatically a permanent member of VID 1. This facilitates deployment of devices that have VLAN enabled with those that do not. If disabled, MVID traffic is not allowed to or from the SM wired interface. Also, if Management VID is the same as a Port VID (Default or MAC-based), then this setting is ignored and assumed to be Enabled. This is the VID that is used for untagged frames and will correspond to the Q-

Tag for 802.1Q frames (if VLAN Port Type is Q), or the C-Tag for 802.1ad frames (if the VLAN Port Type is Q-in- Q). Page 7-51 Chapter 7: Configuration Port VID MAC Address Mapping Provider VID Active Configuration, Default Port VID Active Configuration, MAC Address VID Map Active Configuration, Management VID Active Configuration, SM Management VID Pass-Through Active Configuration, Dynamic Aging Timeout Active Configuration, Allow Learning Active Configuration, Allow Frame Type Configuring IP and Ethernet interfaces These parameters allow operators to place specific devices onto different VLANs (802.1Q tag or 802.1ad C-tag) based on the source MAC address of the packet. If the MAC address entry is 00-00-00-00-00-00 then that entry is not used. If a packet arrives at the SM that is sourced from a device whose MAC address is in the table, then the corresponding VID is used for that frames Q-tag (Q port) or C-tag (Q-in-Q port). If there is no match, then the Default Port VID is used. This table is also used in the downstream direction for removal of the tag based on the destination MAC address so that an untagged (for Q port) or Q-Tagged (for Q-in-Q port) frame is delivered to the end device. You may use wildcards for the non-OUI (Organizationally Unique Identifier) portion of the MAC address, which is the last 3 bytes. MAC addresses contain 6 bytes, the first 3 of which are the OUI of the vendor that manufactured the device and the last 3 are unique to that vendor OUI. If you want to cover all devices from a known vendors OUI, you have to specify 0xFF for the remaining 3 bytes. So, for example, if you wanted all devices from a specific vendor with an OUI of 00-95-5b (which is a Netgear OUI) to be on the same VID of 800, you have to specify an entry with MAC address 00-95-5b-ff-ff-ff. Then, any device underneath of the SM with MAC addresses starting with 00-95-5b is put on VLAN 800. The provider VID is used for the S-tag. It is only used if the Port Type is Q-

in-Q and will always be used for the S-tag. If an existing 802.1Q frame arrives, the Provider VID is what is used for adding and removing of the outer S-tag. If an untagged frame arrives to a Q-in-Q port, then the Provider VID is the S-tag and the Default Port VID (or Port VID MAC Address Mapping, if valid) is used for the C-tag. This is the value of the parameter of the same name, configured above. This is the listing of the MAC address VIDs configured in Port VID MAC Address Mapping. This is the value of the parameter of the same name, configured above. This is the value of the parameter of the same name, configured above. This is the value of the VLAN Aging Timeout parameter configured above. Yes is displayed if the value of the Dynamic Learning parameter above is Enabled. No is displayed if the value of Dynamic Learning is Disabled. This displays the selection that was made from the drop-down list at the Allow Frame Types parameter above. Page 7-52 Chapter 7: Configuration Configuring IP and Ethernet interfaces Active Configuration, QinQ Active Configuration, QinQ EthType Active Configuration, Allow QinQ Tagged Frames Active Configuration, Current VID Member Set, VID Number Active Configuration, Current VID Member Set, Type Active Configuration, Current VID Member Set, Age This is set to Enabled if VLAN Port Type is set to QinQ, and is set to Disabled if VLAN Port Type is set to Q. This is the value of the QinQ EtherType configured in the AP. This is the value of Accept QinQ Frames, configured above. This column lists the ID numbers of the VLANs in which this module is a member, whether through assignment or through dynamic learning. For each VID number in the first column, the entry in this column correlates the way in which the module became and continues to be a member:

PermanentThis indicates that the module was assigned the VID number through direct configuration by the operator. DynamicThis indicates that the module adopted the VID number through enabled dynamic learning, when a tagged packet from a SM behind it in the network or from a customer equipment that is behind the SM in this case, was read. For each VID number in the first column of the table, the entry in this column reflects whether or when the VID number will time out:

Permanent type - Number never times out and this is indicated by the digit 0. Dynamic type - Age reflects what is configured in the VLAN Aging Timeout parameter in the Configuration => VLAN tab of the AP or reflects a fewer number of minutes that represents the difference between what was configured and what has elapsed since the VID was learned. Each minute, the Age decreases by one until, at zero, the AP deletes the learned VID, but can it again from packets sent by elements that are beneath it in the network. Note Values in this Active Configuration block can differ from attempted values in configurations:

The AP can override the value that the SM has configured for SM Management VID Pass-Through. Page 7-53 Chapter 7: Configuration Configuring IP and Ethernet interfaces VLAN Membership tab of SM The Configuration > VLAN > VLAN Membership tab is explained in Table 116. Table 116 SM VLAN Membership attributes Attribute VLAN Membership Table Configuration Meaning For each VLAN in which you want the AP to be a member, enter the VLAN ID and then click the Add Member button. Similarly, for any VLAN in which you want the AP to no longer be a member, enter the VLAN ID and then click the Remove Member button. VLAN configuration for PTP Applicable products PTP: BHM BMS VLAN page of BHM The VLAN tab of BHS is explained in Table 117. Table 117 BHM VLAN page attributs Page 7-54 Chapter 7: Configuration Configuring IP and Ethernet interfaces Attribute VLAN VLAN Port Type Accept QinQ Frames Management VID

(Range 1-4094) Default Port VID

(Range 1-4094) QinQ Ether Type Meaning Specify whether VLAN functionality for the BHM and all linked BHS must be

(Enabled) or may not (Disabled) be allowed. The default value is Disabled. By default this is Q, indicating that it is to operate in the existing manner. The other option is Q-in-Q, which indicates that it must be adding and removing the S-Tag, and adding a C-Tag if necessary for untagged packets. The VLAN Port type corresponds to the Ethernet port of the BHS. Currently, the internal management interfaces will always operate as Q ports. This option is valid for the Q-in-Q port so that the user may force blocking of existing 802.1ad Q-in-Q frames. This way, only untagged or single tagged packets will come in and out of the Ethernet interface. If a Q-in-Q frame is about ingress or egress the Ethernet interface and this is disabled, it is dropped and a filter entry will show up on the VLAN Statistics page as DVLAN Egress or DVLAN Ingress. Enter the VID that the BHS must share with the BHM. The range of values is 1 to 4095. The default value is 1. This is the VID that is used for untagged frames and corresponds to the Q-Tag for 802.1Q frames (if VLAN Port Type is Q), or the C-Tag for 802.1ad frames

(if the VLAN Port Type is Q-in- Q). Modules can be configured with 802.1ad Q-in-Q DVLAN (Double-VLAN) tagging which is a way for an operator to put an 802.1Q VLAN inside of an 802.1ad VLAN. A nested VLAN, which is the original 802.1Q tag and a new second 802.1ad tag, allows for bridging of VLAN traffic across a network and segregates the broadcast domains of 802.1Q VLANs. Q-in-Q can be used with PPPoE and/or NAT. The 802.1ad standard defines the S-VLAN as the Service Provider VLAN and the C-VLAN as the customer VLAN. The radio software does 2 layer Q-in-Q whereby the C-VLAN is the 802.1Q tag and the S-VLAN is the second layer Q tag as shown below:

Ethernet Header S-VLAN EthType 0x88a8 C-VLAN EthType 0x8100 IP Data EthType 0x0800 The 802.1ad S-VLAN is the outer VLAN that is configurable on the Configuration > VLAN web page of the BHM. The Q-in-Q EtherType parameter is configured with a default EtherType of 0x88a8 in addition to four alternate EtherTypes that can be configured to aid in interoperability with existing networks that use a different EtherType than the default. Page 7-55 Chapter 7: Configuration Configuring IP and Ethernet interfaces VLAN Not Active The C-VLAN is the inner VLAN tag, which is the same as 802.1Q. As a top level concept, this operates on the outermost tag at any given time, either pushing a tag on or popping a tag off. This means packets will at most transition from an 802.1Q frame to an 801.ad frame (with a tag pushed on) or an untagged 802.1 frame (with the tag popped off. Similarly, for an 802.1ad frame, this can only transition from an 802.1ad frame to an 802.1Q frame (with the tag popped off) since the radio software only supports 2 levels of tags. When VLAN is enabled in the BHM, the Active Configuration block provides the following details as read-only information in this tab. In the Cambium fixed wireless broadband IP network, each device of any type is automatically a permanent member of VID 1. This facilitates deployment of devices that have VLAN enabled with those that do not. Page 7-56 Chapter 7: Configuration Configuring IP and Ethernet interfaces VLAN page of BHS The VLAN tab of BHS is explained in Table 118. Table 118 BHS VLAN page attributes Attribute VLAN VLAN Port Type Accept QinQ Frames Management VID

(Range 1-4094) Default Port VID

(Range 1-4094) VLAN Not Active Meaning Specify whether VLAN functionality for the BHM and all linked BHS must be

(Enabled) or may not (Disabled) be allowed. The default value is Disabled. By default this is Q, indicating that it is to operate in the existing manner. The other option is Q-in-Q, which indicates that it must be adding and removing the S-Tag, and adding a C-Tag if necessary for untagged packets. The VLAN Port type corresponds to the Ethernet port of the BHS. Currently, the internal management interfaces will always operate as Q ports. This option is valid for the Q-in-Q port so that the user may force blocking of existing 802.1ad Q-in-Q frames. This way, only untagged or single tagged packets will come in and out of the Ethernet interface. If a Q-in-Q frame is about ingress or egress the Ethernet interface and this is disabled, it is dropped and a filter entry will show up on the VLAN Statistics page as DVLAN Egress or DVLAN Ingress. Enter the VID that the BHS must share with the BHM. The range of values is 1 to 4095. The default value is 1. This is the VID that is used for untagged frames and corresponds to the Q-

Tag for 802.1Q frames (if VLAN Port Type is Q), or the C-Tag for 802.1ad frames (if the VLAN Port Type is Q-in- Q). When VLAN is enabled in the BHM, the Active Configuration block provides the following details as read-only information in this tab. In the Cambium fixed wireless broadband IP network, each device of any type is automatically a permanent member of VID 1. This facilitates deployment of devices that have VLAN enabled with those that do not. Page 7-57 Chapter 7: Configuration PPPoE page of SM Configuring IP and Ethernet interfaces Applicable products PMP :

SM Point-to-Point Protocol over Ethernet (PPPoE) is a protocol that encapsulates PPP frames inside Ethernet frames (at Ethernet speeds). Benefits to the network operator may include Access control Service monitoring Generation of statistics about activities of the customer Re-use of infrastructure and operational practices by operators who already use PPP for other networks PPPoE options are configurable for the SM only, and the AP indicates whether or not PPPoE is enabled for a specific subscriber. When PPPoE is enabled, once the RF session comes up between the SM and the AP, the SM will immediately attempt to connect to the PPPoE Server. You can monitor the status of this by viewing the PPPoE Session Log in the Logs section (Administrator only). Every time the RF session comes up, the SM will check the status of the link and if it is down, the SM will attempt to redial the link if necessary depending on the Timer Type. Also, on the Configuration page, the user may Connect or Disconnect the session manually. This can be used to override the session to force a manual disconnect and/or reconnect if there is a problem with the session. In order to enable PPPoE, NAT MUST be enabled on the SM and Translation Bridging MUST be disabled on the AP. These items is strictly enforced for you when you are trying to enable PPPoE. A message will indicate any prerequisites not being met. Also, the NAT Public IP DHCP client cannot be enabled, because the NAT Public IP is received through the IPCP process of the PPPoE discovery stages. The pre-requisites are:

NAT MUST be enabled on the SM o NAT DHCP Client is disabled automatically. The NAT public IP is received from the PPPoE Server. o NAT Public Network Interface Configuration will not be used and must be left to defaults. Also NAT Public IP DHCP is disabled if it is enabled. Translation Bridging MUST be DISABLED on the AP o This will only be determined if the SM is in session since the SM wont know the AP configuration otherwise. If the SM is not in session, PPPoE can be enabled but if the SM goes into session to a Translation Bridge-enabled AP, then PPPoE will not be enabled. The PPPoE configuration parameters are explained in Table 119. Page 7-58 Chapter 7: Configuration Table 119 SM PPPoE attributes Configuring IP and Ethernet interfaces Attribute Access Concentrator Service Name Authentication Type User Name Password MTU Meaning An optional entry to set a specific access concentrator to connect to for the PPPoE session. If this is blank, the SM will accept the first access concentrator which matches the service name (if specified). This is limited to 32 characters. An optional entry to set a specific service name to connect to for the PPPoE session. If this is left blank the SM will accept the first service option that comes back from the access concentrator specified above, if any. This is limited to 32 characters. None means that no PPPoE authentication is implemented CHAP/PAP means that CHAP authentication is attempted first, then PAP authentication. The same password is used for both types. This is the CHAP/PAP user name that is used if CHAP/PAP authentication is selected. If None is selected for authentication then this field is unused. This is limited to 32 characters. This is the CHAP/PAP password that is used if PAP authentication is selected. If None is selected for authentication then this field is unused. This is limited to 32 characters. Use MTU Received from PPPoE Server causes the SM to use the MRU of the PPPoE server received in LCP as the MTU for the PPPoE link. Page 7-59 Chapter 7: Configuration Configuring IP and Ethernet interfaces Timer Type Timer Period TCP MSS Clamping Use User Defined MTU allows the operator to specify an MTU value to use to override any MTU that may be determined in the LCP phase of PPPoE session setup. If this is selected, the user is able to enter an MTU value up to 1492. However, if the MTU determined in LCP negotiations is less than this user-specified value, the SM will use the smaller value as its MTU for the PPPoE link. Keep Alive is the default timer type. This timer will enable a keepalive that will check the status of the link periodically. The user can set a keepalive period. If no data is seen from the PPPoE server for that period, the link is taken down and a reconnection attempt is started. For marginal links, the keep alive timer can be useful so that the session will stay alive over periodic dropouts. The keepalive timer must be set such that the session can outlast any session drop. Some PPPoE servers will have a session check timer of their own so that the timeouts of the server and the SM are in sync, to ensure one side does not drop the session prematurely. Idle Timeout enables an idle timer that checks the usage of the link from the customer side. If there is no data seen from the customer for the idle timeout period, the PPPoE session is dropped. Once data starts flowing from the customer again, the session is started up again. This timer is useful for users who may not be using the connection frequently. If the session is idle for long periods of time, this timer will allow the resources used by the session to be returned to the server. Once the connection is used again by the customer, the link is reestablished automatically. The length in seconds of the PPPoE keepalive timer. If this is enabled, then the SM will alter TCP SYN and SYN-ACK packets by changing the Maximum Segment Size to be compatible with the current MTU of the PPPoE link. This way, the user does not have to worry about MTU on the client side for TCP packets. The MSS is set to the current MTU 40 (20 bytes for IP headers and 20 bytes for TCP headers). This will cause the application on the client side to not send any TCP packets larger than the MTU. If the network is exhibiting large packet loss, try enabling this option. This may not be an option on the PPPoE server itself. The SM will NOT reassemble IP fragments, so if the MTUs are incorrect on the end stations, then MSS clamping will solve the problem for TCP connections. Page 7-60 Chapter 7: Configuration IP4 and IPv6 Configuring IP and Ethernet interfaces Applicable products PMP : AP SM PTP: BHM BMS IPv4 and IPv6 Prioritization 450 Platform Family provides operators the ability to prioritize IPv6 traffic in addition to IPv4 traffic. IPv6/IPv4 prioritization can be configured by selecting a CodePoint and the corresponding priority from the GUI of the AP/BHM and the IPv6/IPv4 packet is set up accordingly. There is no GUI option for selecting IPv6 or IPv4 priority. Once the priority is set, it is set for IPv4 and IPv6 packets. Configuring IPv4 and IPv6 Priority IPv4 and IPv6 prioritization is set using the DiffServ tab on the AP/BHM and SM/BHS (located at Configuration > DiffServ). A priority set to a specific CodePoint will apply to both IPv4 and IPv6 traffic. Table 120 DiffServ attributes AP/BHM Attribute CodePoint 1 through CodePoint 47 CodePoint 49 through CodePoint 55 CodePoint 57 through CodePoint 63 Meaning Priorities of 0 through 3 map to the low-priority channel; 4 through 7 to the high- priority channel. The mappings are the same as 802.1p VLAN priorities. Consistent with RFC 2474 CodePoint 0 is predefined to a fixed priority value of 0 (low-priority channel). CodePoint 48 is predefined to a fixed priority value of 6 (high-priority channel). CodePoint 56 is predefined to a fixed priority value of 7 (high-

priority channel). Operator cannot change any of these three fixed priority values. Among the settable parameters, the priority values (and therefore the handling of packets in the high or low priority channel) are set in the AP/BHM for all downlinks within the sector and in the SM/BHS for each uplink. Page 7-61 Chapter 7: Configuration Configuring IP and Ethernet interfaces CodePoint Select This represents the CodePoint Selection to be modified via Priority Select Priority Select Priority Precedence PPPoE Control Message Priority The priority setting input for the CodePoint selected in CodePoint Select Allows operator to decide if 802.1p or DiffServ priority bits must be used first when making priority decisions. Operators may configure the AP/BHM to utilize the high priority channel for PPPoE control messages. Configuring the AP/BHM in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the AP/BHM. IPv4 and IPv6 Filtering The operator can filter (block) specified IPv6 protocols including IPv4 and ports from leaving the AP/BHM and SM/BHS and entering the network. This protects the network from both intended and inadvertent packet loading or probing by network users. By keeping the specified protocols or ports off the network, this feature also provides a level of protection to users from each other. Configuring IPv4 and IPv6 Filtering IPv6 filters are set using the Protocol Filtering tab on the AP/BHM and SM/BHS (at Configuration >

Protocol Filtering). Once a filter is set for a packet type, those packets will not be sent over the RF interface depending on Filter Direction setting. Page 7-62 Chapter 7: Configuration Configuring IP and Ethernet interfaces Table 121 Packet Filter Configuration attributes Attribute Packet Filter Types Meaning For any box selected, the Protocol and Port Filtering feature blocks the associated protocol type. To filter packets in any of the user-defined ports, you must do all of the following:

Check the box for User Defined Port n (See Below) in the Packet Filter Types section of this tab. Provide a port number at Port #n. in the User Defined Port Filtering Configuration section of this tab Page 7-63 Chapter 7: Configuration Configuring IP and Ethernet interfaces Filter Direction User Defined Port Filtering Configuration Enable TCP and/or UDP by clicking the associated radio button Operators may choose to filter upstream (uplink) RF packets or downstream

(downlink) RF packets. You can specify ports for which to block subscriber access, regardless of whether NAT is enabled. Page 7-64 Chapter 7: Configuration Upgrading the software version and using CNUT Upgrading the software version and using CNUT This section consists of the following procedures:

Checking the installed software version on page 7-64 Upgrading to a new software version on page 7-64 Caution If the link is operational, ensure that the remote end of the link is upgraded first using the wireless connection, and then the local end can be upgraded. Otherwise, the remote end may not be accessible. Use CNUT 4.10.4 or later version and always refer to the software release notes before upgrading system software. The release notes are available at:

https://support.cambiumnetworks.com/files/pmp450 https://support.cambiumnetworks.com/files/ptp450 Checking the installed software version To check the installed software version, follow these instructions:

Procedure 18 Checking the installed software version 1 2 3 4 Click on General tab under Home menu. Note the installed Software Version (under Device Information):

PMP/PTP 450/450i/450m Go to the support website (see Contacting Cambium Networks on page 1) and find Point-to-

Multipoint software updates. Check that the latest 450 Platform Family software version is the same as the installed Software Version. To upgrade software to the latest version, see Upgrading to a new software version on page 7-

64. Upgrading to a new software version All 450 platform modules are upgraded using the Canopy Network Updater Tool. The Canopy Network Updater Tool (CNUT) manages and automates the software upgrade process for a Canopy radio, or CMM4 (but not its 14-port switch) across the network. This eliminates the need for an administrator to visit each radio in the network (or each AP/BHM while using the Autoupdate feature) to upgrade the modules. Page 7-65 Chapter 7: Configuration Upgrading the software version and using CNUT Note Please ensure that you have the most up-to-date version of CNUT by browsing to the Customer Support Web Page located:

http://www.cambiumnetworks.com/support/management-tools/cnut This section includes an example of updating a single unit before deployment. System-wide upgrading procedures may be found in the CNUT Online Help manual, which can be found on the Cambium support website (see Contacting Cambium Networks on page 1). CNUT functions The Canopy Network Updater tool has the following functions:

Automatically discovers all network elements Executes a UDP command that initiates and terminates the Auto-update mode within APs/BHMs. This command is both secure and convenient:

o For security, the AP/BHM accepts this command from only the IP address that you specify in the Configuration page of the AP/BHM. o For convenience, Network Updater automatically sets this Configuration parameter in the APs/BHMs to the IP address of the Network Updater server when the server performs any of the update commands. CNUT supports HTTP and HTTPS Allows you to choose the following among updating:

o Your entire network. o Only elements that you select. o Only network branches that you select. Provides a Script Engine that you can use with any script that:

o You define. o Cambium supplies. Configurability of any of the following to be the file server for image files:

o The AP/BHM, for traditional file serving via UDP commands and monitoring via UDP messaging o CNUT HTTP/HTTPS Server, for upgrading via SNMP commands and monitoring via SNMP messaging. This also supports an option to either set the image order specifically for this file server or to allow the AP to determine the order. o Local TFTP Server, for traditional file serving via UDP commands and monitoring via UDP messaging. This supports setting the number of simultaneous image transfers per AP/BHM The capability to launch a test of connectivity and operational status of the local HTTP, HTTPS and TFTP file servers An interface that supports efficient specification of the proper IP address for the local file server(s) where Network Updater resides on a multi-homed computer An md5 checksum calculator utility for identifying corruption of downloaded image files before Network Updater is set to apply them. Network element groups With the Canopy Network Updater Tool, you can identify element groups composed of network elements that you select. Identifying these element groups does the following:

Page 7-66 Chapter 7: Configuration Upgrading the software version and using CNUT Organizes the display of elements (for example, by region or by AP/BHM cluster). Allows to:

o Perform an operation on all elements in the group simultaneously. o Set group-level defaults for ftp password access and SNMP Community String (defaults that can be overridden in an individual element when necessary). Network layers A typical network contains multiple layers of elements, with each layer farther from the Point of Presence. For example, SMs (or BHS) are behind an AP/BHM and thus, in this context, at a lower layer than the AP/BHM. Correctly portraying these layers in Network Updater is essential so that Network Updater can perform radio and AP/BHM cluster upgrades in an appropriate order. Script engine Script Engine is the capability in Network Updater that executes any user-defined script against any network element or element group. This capability is useful for network management, especially for scripts that you repetitively execute across your network. The Autodiscovery capability in Network Updater finds all of your network elements. This comprehensive discovery:

Ensures that, when you intend to execute a script against all elements, the script is indeed executed against all elements. Maintains master lists of elements (element groups) against which you selectively execute scripts. The following scripts are included with CNUT:

Gather Customer Support Information Set Access Point Authentication Mode Set Autoupdate Address on APs/BHMs Set SNMP Accessibility Reset Unit Page 7-67 Chapter 7: Configuration Upgrading the software version and using CNUT Software dependencies for CNUT CNUT functionality requires one of the following operating systems o Windows 2000 o Windows Server 2003 o Windows 7 and Windows 8 o Windows XP or XP Professional o Red Hat Enterprise Linux (32-bit) Version 4 or 5 Java Runtime Version 2.0 or later (installed by the CNUT installation tool) CNUT download CNUT can be downloaded together with each system release that supports CNUT. Software for these system releases is available from http://www.cambiumnetworks.com/support/management-tools/cnut/, as either:

A .zip file for use without the CNUT application. A .pkg file that the CNUT application can open. Upgrading a module prior to deployment To upgrade to a new software version, follow this:

Procedure 19 Upgrading a module prior to deployment 1 2 3 4 5 6 7 8 Go to the support website (see Contacting Cambium Networks on page 1) and find Point-to-

Multipoint software updates. Download and save the required software image. Start CNUT If you dont start up with a blank new network file in CNUT, then open a new network file with the New Network Archive operation (located at File > New Network). Enter a new network element to the empty network tree5-9 using the Add Elements to Network Root operation (located at Edit > Add Elements to Network Root). In the Add Elements dialogue, select a type of Access Point or Subscriber Module and enter the IP address of 169.254.1.1. Make sure that the proper Installation Package is active with the Package Manager dialogue

(located at Update > Manage Packages). To verify connectivity with the radio, perform a Refresh, Discover Entire Network operation

(located at View > Refresh/Discover Entire Network). You must see the details columns for the new element filled in with ESN and software version information. Initiate the upgrade of the radio using Update Entire Network Root operation (located at Update > Update Entire Network Root). When this operation finishes, the radio is done being upgraded. Page 7-68 Chapter 7: Configuration General configuration General configuration The Configuration > General page of the AP/BMH or BHM/BHS contains many of the configurable parameters that define how the ratios operate in sector or backhaul. Applicable products PTP: BHM BMS PMP : AP SM PMP 450m and PMP/PTP 450i Series General page - PMP 450i AP The General page of AP is explained in Table 122. Table 122 General page attributes PMP 450i AP Page 7-69 Chapter 7: Configuration General configuration Attribute Ethernet Port Selection Link Speeds 802.3at Type 2 PoE Status and PoE Classification

(PMP 450i Series only) Meaning Ethernet Port selection is applicable to the 450m platform only with two choices in the drop-down list:

Main: A selection of main indicates that link connectivity and power to the 450m is provided through the RF45 connection on the Main port of the AP SFP: A selection of SFP indicates that link connectivity will be provided through the SFP port on the 450m Power continues to be provided via the RJ45 Main port From the drop-down list of options, select the type of link speed for the Ethernet connection. The Auto settings allow the two ends of the link to automatically negotiate with each other the best possible speed, and check whether the Ethernet traffic is full duplex or half duplex. However, some Ethernet links work best when either:

both ends are set to the same forced selection both ends are set to auto-negotiate and both have capability in least one common speed and traffic type combination. When the PoE Classification functionality is enabled and if Type 2 power is not present, the PAs do not power up and draw too much power. By default, the PoE Classification feature is disabled and the PAs will power up regardless of the classification presented by the power source. This is supported only on 450i series devices. PoE Classification configuration status also can be check under home >

General > Device Information tab:

Configuration Source Sync Input See Setting the Configuration Source on page 7-203. See Configuring synchronization on page 7-97 Page 7-70 Chapter 7: Configuration Device Type Region Country Webpage Auto Update Bridge Entry Timeout Translation Bridging General configuration Standard: The Autosync mechanism will source GPS synchronization from the APs RJ-11 port, the APs power port, or from the device on-board GPS module. Remote: The Autosync mechanism will source GPS synchronization from the APs RJ-11 port or from the device on-board GPS module. From the drop-down list, select the region in which the radio is operating. From the drop-down list, select the country in which the radio is operating. Unlike selections in other parameters, your Country selection requires a Save Changes and a Reboot cycle before it will force the context-sensitive GUI to display related options (for example, Alternate Frequency Carrier 1 and 2 in the Configuration > Radio tab). PMP 450i Series ODUs shipped to the United States is locked to a Region Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. Country Code settings affect the radios in the following ways:

Maximum transmit power limiting (based on radio transmitter power plus configured antenna gain) DFS operation is enabled based on the configured region code, if applicable For more information on how transmit power limiting and DFS is implemented for each country, see the PMP 450 Planning Guide. Enter the frequency (in seconds) for the web browser to automatically refresh the web-based interface. The default setting is 0. The 0 setting causes the web-based interface to never be automatically refreshed. Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Caution An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. Optionally, you can configure the AP to change the source MAC address in every packet it receives from its SMs to the MAC address of the SM that bridged the packet, before forwarding the packet toward the public network. If you do, then:

Not more than 128 IP devices at any time are valid to send data to the AP from behind the SM. SM populates the Translation Table tab of its Statistics web page, displaying the MAC address and IP address of all the valid connected devices. Page 7-71 Chapter 7: Configuration General configuration Each entry in the Translation Table is associated with the number of minutes that have elapsed since the last packet transfer between the connected device and the SM. If 128 are connected and another attempts to connect:

If no Translation Table entry is older than 255 minutes, the attempt is ignored. If an entry is older than 255 minutes, the oldest entry is removed and the attempt is successful. the Send Untranslated ARP parameter in the General tab of the Configuration page can be:

Disabled, so that the AP overwrites the MAC address in Address Resolution Protocol (ARP) packets before forwarding them. Enabled, so that the AP forwards ARP packets regardless of whether it has overwritten the MAC address. When this feature is disabled, the setting of the Send Untranslated ARP parameter has no effect, because all packets are forwarded untranslated

(with the source MAC address intact). If the Translation Bridging parameter is set to Enabled, then the Send Untranslated ARP parameter can be:

Disabled - so that the AP will overwrite the MAC address in Address Resolution Protocol (ARP) packets before forwarding them. Enabled - so that the AP will forward ARP packets regardless of whether it has overwritten the MAC address. If the Translation Bridging parameter is set to Disabled, then the Send Untranslated ARP parameter has no effect. Prevent or allow SM-to-SM communication by selecting from the following drop-down menu items:

Disable SM Isolation (the default selection). This allows full communication between SMs. Block SM Packets from being forwarded. This prevents both multicast/broadcast and unicast SM-to-SM communication. Block and Forward SM Packets to Backbone. This not only prevents multicast/broadcast and unicast SM-to-SM communication but also sends the packets, which otherwise are handled SM to SM, through the Ethernet port of the AP. Enabled: All unknown Unicast packets (no entry in the APs bridge table) received via the APs Ethernet LAN interface are forwarded to registered SMs. If the target device is situated beneath a particular SM, when the device responds the SM and AP will learn and add the device to their bridge tables so that subsequent packets to that device is bridged to the proper SM. Disabled: All unknown Unicast packets (no entry in the APs bridge table) received via the APs Ethernet LAN interface are discarded at the AP. Enter the address of the server to access for software updates on this AP and registered SMs. Page 7-72 Send Untranslated ARP SM Isolation Forward Unknown Unicast Packets Update Application Address Chapter 7: Configuration Prioritize TCP ACK Multicast Destination Address DHCP Relay Agent DHCP Server (Name or IP Address) Latitude Longitude Height General configuration To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. This parameter, when enabled, can be particularly useful when running bi-direction FTP sessions over the link. If a link is primarily used for video surveillance, it is recommended to set this parameter to Disable. Using Link Layer Discovery Protocol (LLDP), a module exchanges multicast addresses with the device to which it is wired on the Ethernet interface. Although some switches (CMM4, for example) do not pass LLDP addresses upward in the network, a radio can pass it as the value of the Multicast Destination Address parameter value in the connected device that has it populated. The AP may act as a DHCP relay for SMs and CPEs underneath it. The AP will make use of the DHCP Option 82 (DHCP Relay Agent Information) from RFC 3046 when performing relay functions. The AP offers two types of DHCP relay functionality:

Full Relay Information. Configuring the DHCP Full Relay Operation will take broadcast DHCP packets and send them to a Unicast server in unicast mode. This way the DHCP requests and replies can be routed like any other UDP packet. Only Insert Option 82. This option leaves the DHCP request on its broadcast domain as opposed to DHCP Full Relay Operation which will turn it into a unicast packet. In order to accommodate setting up pools or classes for different VLANs, the Option 82 field will include information to tell the server what VLAN the client is on. The DHCP relay server may be either a DNS name or a static IP address in dotted decimal notation. Additionally the management DNS domain name may be toggled such that the name of the DHCP relay server only needs to be specified and the DNS domain name is automatically appended to that name. The default DHCP relay server addresses is 255.255.255.255 with the appending of the DNS domain name disabled. Physical radio location data may be configured via the Latitude, Longitude and Height fields. Latitude and Longitude is measured in Decimal Degree while the Height is calculated in Meters. Page 7-73 Chapter 7: Configuration General configuration General page - PMP 450m AP The General page of AP is explained in Table 123. Table 123 General page attributes PMP 450m AP Page 7-74 Chapter 7: Configuration General configuration Attribute Trial Mode Meaning This parameters allows to enable or disable Trial mode for radios with a Limited key. Once the trial key is applied, the 30-day trial can be enabled or disabled at any time. For information about remaining attributes, refer Table 122. Page 7-75 Chapter 7: Configuration General configuration General page - PMP 450i SM The General page of PMP 450i SM is explained in Table 124. The General page of PMP 450 SM looks the same as PMP 450i SM. Table 124 General page attributes PMP 450i SM Attribute Link Speeds 802.3at Type 2 PoE Status and PoE Classification Meaning From the drop-down list of options, select the type of link speed for the Ethernet connection. The default for this parameter is that all speeds are selected. The recommended setting is a single speed selection for all APs and SMs in the operator network. When the PoE Classification functionality is enabled and if Type 2 power is not present, the Pas do not power up and draw too much power. By default, the PoE Classification feature is disabled and the Pas will power up regardless of the classification presented by the power source. This is supported only on 450i series ODUs. PoE Classification configuration status also can be check under home >

General > Device Information tab:

Page 7-76 Chapter 7: Configuration Ethernet Link Enable/Disable Region Country Webpage Auto Update Show Idle Sessions Bridge Entry Timeout General configuration Specify whether to enable or disable Ethernet/802.3 connectivity on the wired port of the SM. This parameter has no effect on the wireless link. When you select Enable, this feature allows traffic on the Ethernet/802.3 port. This is the factory default state of the port. When you select Disable, this feature prevents traffic on the port. Typical cases of when you may want to select Disable include:

The subscriber is delinquent with payment(s). You suspect that the subscriber is sending or flooding undesired broadcast packets into the network, such as when a virus is present in the subscribers computing device. the subscribers home router is improperly configured. This parameter allows you to set the region in which the radio will operate. The SM radio automatically inherits the Region type of the master. This behavior ignores the value of the Region parameter in the SM, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. This parameter allows you to set the country in which the radio will operate. The SM radio automatically inherits the Country Code type of the master. This behavior ignores the value of the Country parameter in the SM, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. PMP/PTP 450i Series ODU shipped to the United States is locked to a Region Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. See Table 122 General page attributes PMP 450i AP on page 7-68 This parameter allows to enable or disable displaying idle sessions. Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. Timeout occurs when the AP encounters no activity with the SM (whose MAC address is the bridge entry) within the interval that this parameter specifies. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Page 7-77 Chapter 7: Configuration General configuration Caution This parameter governs the timeout interval, even if a router in the system has a longer timeout interval. The default value of this field is 25 (minutes). An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. Bridge Table Size This parameter allows to restrict devices to connect to the SM. It is configurable from 4 to 4096. Note Configure Bridge Table Restriction parameter to Drop packets if MAC address is not in bridge table option to restrict the number of devices configured from connecting to SM. Bridge Table Restriction Frame Timing Pulse Gated Multicast Destination Address Coordinates This parameter allows to either allow or restrict devices to connect to SM using the following options:

Drop packets if MAC address is not in bridge table: Select this option to restrict communication from devices not listed in bridge table. Forward packets even if MAC address is not in bridge table: Select this option to allow communication from any device. If this SM extends the sync pulse to a BH master or an AP, select either EnableIf this SM loses sync from the AP, then do not propagate a sync pulse to the BH timing master or other AP. This setting prevents interference in the event that the SM loses sync. DisableIf this SM loses sync from the AP, then propagate the sync pulse to the BH timing master or other AP. Using Link Layer Discovery Protocol (LLDP), a module exchanges multicast addresses with the device to which it is wired on the Ethernet interface. Although some switches (CMM4, for example) do not pass LLDP addresses upward in the network, a radio can pass it as the value of the Multicast Destination Address parameter value in the connected device that has it populated. Physical radio location data may be configured via the Latitude, Longitude and Height fields. Page 7-78 Chapter 7: Configuration General configuration General page - PTP 450i BHM The General page of BHM is explained in Table 125. The General page of PTP 450 BHM looks the same as PTP 450i BHM. Table 125 General page attributes PTP 450i BHM Page 7-79 General configuration Meaning Allows the user to choose the mode between Timing Master and Timing Slave. See Table 122 General page attributes PMP 450i AP on page 7-68 When the PoE Classification functionality is enabled and if Type 2 power is not present, the PAs do not power up and draw too much power. By default, the PoE Classification feature is disabled and the PAs will power up regardless of the classification presented by the power source. This is supported only on 450i Series ODUs. PoE Classification configuration status also can be check under home >

General > Device Information tab:

See Configuring synchronization on page 7-97 See Table 122 General page attributes PMP 450i AP on page 7-68 Select whether you want bridge table filtering active (Enable) or not

(Disable) on this BH. Disable: allows user to use redundant BHs without causing network addressing problems. Through a spanning tree protocol, this reduces the convergence time from 25 minutes to few seconds. However, you must disable bridge table filtering as only a deliberate part of your overall network design since disabling it allows unwanted traffic across the wireless interface. Enable: Allows user to enable bridge functionality. Note Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. The Bridge Entry Timeout must be a longer period than the ARP

(Address Resolution Protocol) cache timeout of the router that feeds the network. See Table 122 General page attributes PMP 450i AP on page 7-68 Chapter 7: Configuration Attribute Timing Mode Link Speed 802.3at Type 2 PoE Status and PoE Classification Sync Input Region Country Webpage Auto Update Bridge Entry Timeout Bridging Functionality Prioritize TCP ACK Multicast Destination Address Latitude Longitude Height Page 7-80 Chapter 7: Configuration General configuration General page - PTP 450i BHS The General page of PTP 450i BHS is explained in Table 126. The General page of PTP 450 BHS looks the same as PTP 450i BHS. Table 126 General page attributes PTP 450i BHS Attribute Timing Mode Link Speed Meaning Allows the user to choose the mode between Timing Master and Timing Slave. From the drop-down list of options, select the type of link speed for the Ethernet connection. The default for this parameter is that all speeds are selected. The recommended setting is a single speed selection for all BHMs and BHSs in the operator network. Page 7-81 Chapter 7: Configuration 802.3at Type 2 PoE Status and PoE Classification Region Country Webpage Auto Update Bridge Entry Timeout General configuration When the PoE Classification functionality is enabled and if Type 2 power is not present, the PAs do not power up and draw too much power. By default, the PoE Classification feature is disabled and the PAs will power up regardless of the classification presented by the power source. This is supported only on 450i Series ODUs. PoE Classification configuration status also can be check under home >

General > Device Information tab:

This parameter allows you to set the region in which the radio will operate. The BHS radio automatically inherits the Region type of the master. This behavior ignores the value of the Region parameter in the BHS, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. This parameter allows you to set the country in which the radio will operate. The BHS radio automatically inherits the Country Code type of the master. This behavior ignores the value of the Country parameter in the BHS, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. PMP/PTP 450i Series ODU shipped to the United States is locked to a Region Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. See Table 122 General page attributes PMP 450i AP on page 7-68 Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. Timeout occurs when the BHM encounters no activity with the BHS (whose MAC address is the bridge entry) within the interval that this parameter specifies. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Caution This parameter governs the timeout interval, even if a router in the system has a longer timeout interval. The default value of this field is 25 (minutes). An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. Bridging Functionality See Table 122 General page attributes PMP 450i AP on page 7-68 Frame Timing Pulse Gated If this BHS extends the sync pulse to a BH master or an BHM, select either Page 7-82 Chapter 7: Configuration General configuration Multicast Destination Address Latitude Longitude Height EnableIf this BHS loses sync from the BHM, then do not propagate a sync pulse to the BH timing master or other BHM. This setting prevents interference in the event that the BHS loses sync. DisableIf this BHS loses sync from the BHM, then propagate the sync pulse to the BH timing master or other BHM. See Table 122 General page attributes PMP 450i AP on page 7-68 See Table 122 General page attributes PMP 450i AP on page 7-68 Page 7-83 Chapter 7: Configuration General configuration General page - PMP 450b SM The General page of PMP 450b SM is explained in Table 127. The General page of PMP 450b SM looks the same as PMP 450i SM. Table 127 General page attributes PMP 450i SM Page 7-84 Chapter 7: Configuration General configuration Attribute Link Speed Ethernet Link Enabled/Disbaled Region Country Webpage Auto Update Meaning From the drop-down list of options, select the type of link speed for the Ethernet connection. The default for this parameter is that all speeds are selected. The recommended setting is a single speed selection for all APs and SMs in the operator network. Specify whether to enable or disable Ethernet/802.3 connectivity on the wired port of the SM. This parameter has no effect on the wireless link. When you select Enable, this feature allows traffic on the Ethernet/802.3 port. This is the factory default state of the port. When you select Disable, this feature prevents traffic on the port. Typical cases of when you may want to select Disable include:

The subscriber is delinquent with payment(s). You suspect that the subscriber is sending or flooding undesired broadcast packets into the network, such as when a virus is present in the subscribers computing device. the subscribers home router is improperly configured. This parameter allows you to set the region in which the radio will operate. The SM radio automatically inherits the Region type of the master. This behavior ignores the value of the Region parameter in the SM, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. This parameter allows you to set the country in which the radio will operate. The SM radio automatically inherits the Country Code type of the master. This behavior ignores the value of the Country parameter in the SM, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. PMP/PTP 450i Series ODU shipped to the United States is locked to a Region Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. Enter the frequency (in seconds) for the web browser to automatically refresh the web-based interface. The default setting is 0. The 0 setting causes the web-based interface to never be automatically refreshed. Page 7-85 Chapter 7: Configuration Bridge Entry Timeout General configuration Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. Timeout occurs when the AP encounters no activity with the SM (whose MAC address is the bridge entry) within the interval that this parameter specifies. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Caution This parameter governs the timeout interval, even if a router in the system has a longer timeout interval. The default value of this field is 25 (minutes). An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. Bridge Table Size This parameter allows to restrict devices to connect to the SM. It is configurable from 4 to 4096. Note Configure Bridge Table Restriction parameter to Drop packets if MAC address is not in bridge table option to restrict the number of devices configured from connecting to SM. Bridge Table Restriction Frame Timing Pulse Gated Multicast Destination Address This parameter allows to either allow or restrict devices to connect to SM using the following options:

Drop packets if MAC address is not in bridge table: Select this option to restrict communication from devices not listed in bridge table. Forward packets even if MAC address is not in bridge table: Select this option to allow communication from any device. If this SM extends the sync pulse to a BH master or an AP, select either EnableIf this SM loses sync from the AP, then do not propagate a sync pulse to the BH timing master or other AP. This setting prevents interference in the event that the SM loses sync. DisableIf this SM loses sync from the AP, then propagate the sync pulse to the BH timing master or other AP. Using Link Layer Discovery Protocol (LLDP), a module exchanges multicast addresses with the device to which it is wired on the Ethernet interface. Although some switches (CMM4, for example) do not pass LLDP addresses upward in the network, a radio can pass it as the value of the Multicast Destination Address parameter value in the connected device that has it populated. Latitude Longitude Height Physical radio location data may be configured via the Latitude, Longitude and Height fields. Latitude and Longitude is measured in Decimal Degree while the Height is calculated in Meters. Page 7-86 Chapter 7: Configuration General configuration PMP/PTP 450 Series Note Refer Table 122 and Table 124 for PMP 450 AP/SM General page parameters details. Page 7-87 Chapter 7: Configuration General configuration General page - PMP 450 AP Figure 133 General page attributes - PMP 450 AP Page 7-88 Chapter 7: Configuration General configuration General page - PMP 450 SM Figure 134 General page attributes - PMP 450 SM Page 7-89 Chapter 7: Configuration General configuration General page PTP 450 BHM Figure 135 General page attributes - PTP 450 BHM Page 7-90 Chapter 7: Configuration General configuration General page PTP 450 BHS Figure 136 General page attributes - PTP 450 BHS Page 7-91 Chapter 7: Configuration Configuring Unit Settings page Configuring Unit Settings page Applicable products PMP : AP SM PTP: BHM BMS The Unit Settings page of the 450 Platform Family contains following options:

Unit-Wide Changes Download Configuration File Upload and Apply Configuration File (for AP and BHM) LED Panel Settings (for SM and BHS) Note LED Panel setting is applicable for SM and BHS only. Upload and Apply Configuration File attributes are not supported for SM and BHS. The 450 Platform Family also supports import and export of configuration from the AP/BHM/SM/BHS as a text file. The configuration file is in JSON format. The logged in user must be an ADMINISTRATOR in order to export or import the configuration file. The exported configuration file contains the complete configuration including all the default values. To keep a backup of the current configuration, the file can be saved as-is and imported later. The configuration file supports encrypted password. The exported configuration file will contain encrypted password. The import of configuration can have either encrypted or plain text password in Configuration fie. A new tab Encrypt the Password is added under Encrypted Password tab to generate encrypted password for a given password. The Import and Export procedure of configuration file is described in Import and Export of config file on page 7-218. LED Panel Mode has options select Revised mode and Legacy mode. The Legacy mode configures the radio to operate with standard LED behavior. Page 7-92 Chapter 7: Configuration Configuring Unit Settings page Unit Settings page of 450 Platform Family - AP/BHM The Unit Setting page of AP/BHM is explained in Table 128. Table 128 Unit Settings attributes 450 Platform Family AP/BHM Attribute Set to Factory Defaults Upon Default Mode Detection Meaning If Enabled is checked, then the default mode functions is enabled. When the module is rebooted with Default mode enabled, it can be accessed at the IP address 169.254.1.1 and no password, and all parameter values are reset to defaults. A subscriber, technician, or other person who gains physical access to the module and uses an override cannot see or learn the settings that were previously configured in it. If Disabled is checked, then the default mode functions is disabled. See Radio recovery mode on page 1-26 Caution When Set to Factory Defaults Upon Default Mode is set to Enable, the radio does not select all of the frequencies for Radio Frequency Scan Selection List. It needs to be selected manually. Undo Unit-Wide Saved Changes Set to Factory Defaults When you click this button, any changes that you made in any tab but did not commit by a reboot of the module are undone. When you click this button, all configurable parameters on all tabs are reset to the factory settings. Page 7-93 Chapter 7: Configuration Configuring Unit Settings page Note This can be reverted by selecting "Undo Unit-Wide Saved Changes", before rebooting the radio, though this is not recommended. Password This allows to provide encrypted password for a given password. On click of Encrypt the password button, the Encrypted Password field will display encrypted value of entered plain text password in Password field. Configuration File Apply Configuration File Status of Configuration file This allows to download the configuration file of the radio. This configuration file contains the complete configuration including all the default values. The configuration file is highlighted as downloadable link and the naming convention is <mac address of AP>.cfg. This allows to import and apply configuration to the AP. Chose File: Select the file to upload the configuration. The configuration file is named as <file name>.cfg. Upload: Import the configuration to the AP. Apply Configuration File: Apply the imported configuration file to the AP. The imported configuration file may either contain a full device configuration or a partial device configuration. If a partial configuration file is imported, only the items contained in the file will be updated, the rest of the device configuration parameters will remain the same. Operators may also include a special flag in the configure file to instruct the device to first revert to factory defaults then to apply the imported configuration. This section shows the results of the upload. Page 7-94 Chapter 7: Configuration Configuring Unit Settings page Unit Settings page of PMP/PTP 450i SM/BHS The Unit Settings page of PMP/PTP 450i SM/BHS is explained in Table 129. Table 129 SM Unit Settings attributes Meaning See Table 128 Unit Settings attributes 450 Platform Family AP/BHM on page 7-92 Legacy Mode configures the radio to operate with standard LED behavior. See Table 128 Unit Settings attributes 450 Platform Family AP/BHM on page 7-92 Attribute Set to Factory Defaults Upon Default Plug Detection LED Panel Settings Undo Unit-Wide Saved Changes Password Set to Factory Defaults Configuration File Status of Configuration file Page 7-95 Chapter 7: Configuration Setting up time and date Setting up time and date Time page of 450 Platform Family - AP/BHM Applicable products PMP : AP PTP: BHM The Time page of 450 Platform Family AP/BHM is explained in Table 130. Table 130 450 Platform Family - AP/BHM Time attributes Attribute NTP Server (Name or IP Address) NTP Server 1 (Name or IP Address) NTP Server 2 (Name or IP Address) NTP Server 3 (Name or IP Address) Meaning The management DNS domain name may be toggled such that the name of the NTP server only needs to be specified and the DNS domain name is automatically appended to that name. To have each log in the AP/BHM correlated to a meaningful time and date, either a reliable network element must pass time and date to the AP/BHM or must set the time and date whenever a power cycle of the AP/BHM has occurred. A network element passes time and date in any of the following scenarios:

A connected CMM4 passes time and date (GPS time and date, if received). A connected CMM4 passes the time and date (GPS time and date, if received), but only if both the CMMr is operating on CMMr Release 2.1 or later release. (These releases include NTP server functionality.) Page 7-96 Chapter 7: Configuration Setting up time and date NTP Server(s) in Use Time Zone System Time Last NTP Time Update Time Date NTP Update Log A separate NTP server (including APs/BHMs receiving NTP data) is addressable from the AP/BHM. If the AP/BHM needs to obtain time and date from a CMM4, or a separate NTP server, enter the IP address or DNS name of the CMM4 or NTP server on this tab. To force the AP/BHM to obtain time and date before the first (or next) 15-minute interval query of the NTP server, click Get Time via NTP. The polling of the NTP servers is done in a sequential fashion, and the polling status of each server is displayed in the NTP Update Log section of the Time Configuration page. An entry of 0.0.0.0 in any of the NTP Server fields indicates an unused server configuration. Lists the IP addresses of servers used for NTP retrieval. The Time Zone option may be used to offset the received NTP time to match the operators local time zone. When set on the AP/BHM, the offset is set for the entire sector SMs (or BHS) are notified of the current Time Zone upon initial registration). If a Time Zone change is applied, the SMs(or BHS) is notified of the change in a best effort fashion, meaning some SMs//BHSs may not pick up the change until the next re-registration. Time Zone changes are noted in the Event Log of the AP/BHM and SM/BHS. The current time used by the system. The last time that the system time was set via NTP. This field may be used to manually set the system time of the radio. This field may be used to manually set the system date of the radio. This field shows NTP clock update log. It includes NTP clock update Date and Time stamp along with server name. Page 7-97 Chapter 7: Configuration Configuring synchronization Configuring synchronization Applicable products PMP : AP PTP: BHM This section describe synchronization options for PMP and PTP configuration. This Sync Input parameter can be configured under Sync Setting tab of Configure > General page (see General configuration on page 7-68). PMP/PTP 450i Series has following synchronization options:

AutoSync AutoSync + Free Run Generate Sync Free Run Before GPS Sync Figure 137 Sync Setting configuration AutoSync For PTP, the BHM automatically receives sync from one of the following sources:

GPS Sync over Timing Port (UGPS, co-located AP GPS sync output, or Remote Device feed from a registered SMs GPS sync output) GPS Sync over Power Port (CMM4) Upon AP/BM power on, the AP/BHM does not transmit until a valid synchronization pulse is received from one of the sources above. If there is a loss of GPS synchronization pulse, within two seconds the AP/BHM automatically attempts to source GPS signaling from another source. In case of PMP, when there are synchronization sources on both the timing port and the power port, the power port GPS source is chosen first. If no valid GPS signal is received, the AP/BHM ceases transmission and SM/BHS registration is lost until a valid GPS signal is received again on the AP or BHM. Note After an AP reboot, the sync acquisition takes a little longer than it had on 450i (anywhere from 40 seconds to 120 seconds difference). Page 7-98 Chapter 7: Configuration Configuring synchronization AutoSync + Free Run This mode operates similarly to mode AutoSync, but if a previously received synchronization signal is lost and no GPS signaling alternative is achieved, the AP/BHM automatically changes to synchronization mode Generate Sync. While SM registration ins maintained, in this mode there is no synchronization of APs/BHMs that can hear each other; the AP/BHM will only generate a sync signal for the local AP/BHM and its associated SMs/BHS. Once a valid GPS signal is obtained again, the AP/BHM automatically switches to receiving synchronization via the GPS source and SM/BHS registration is maintained. When the Sync Input field is set to Autosync or Autosync + Free Run, other options become available to be set e.g. UGPS Power and other fields. This is true on APs and BHMs. Note In mode AutoSync + Free Run, if a GPS signal is never achieved initially, the system will not switch to Free Run mode, and SMs/BHS will not register to the AP/BHM. A valid GPS signal must be present initially for the AP to switch into Free Run mode (and to begin self-generating a synchronization pulse). Also, When an AP/BHM is operating in Free Run mode, over a short time it will no longer be synchronized with co-located or nearby APs/BHMs (within radio range). Due to this lack of transmit and receive synchronization across APs/BHMs or across systems, performance while in Free Run mode may be degraded until the APs/BHMs operating in Free Run mode regain a external GPS synchronization source. Careful attention is required to ensure that all systems are properly receiving an external GPS synchronization pulse, and please consider Free Run mode as an emergency option. Generate Sync (factory default) This option may be used when the AP/BHM is not receiving GPS synchronization pulses from either a CMM4 or UGPS module, and there are no other APs/BHMs active within the link range. Using this option will not synchronize transmission of APs/BHMs that can hear each other; it will only generate a sync signal for the local AP/BHM and its associated SMs/BHS. Note When an AP/BHM has its "Regional Code" set to "None", The radio will not provide valid Sync Pulse Information. There is a RED warning that the radio will not transmit, but the user might expect to see a valid sync if the radio is connected to a working CMM4 or UGPS. Page 7-99 Chapter 7: Configuration Configuring security Configuring security Perform this task to configure the 450 Platform system in accordance with the network operators security policy. Choose from the following procedures:

Managing module access by password on page 7-100: to configure the unit access password and access level Isolating from the internet on page 7-103: to ensure that APs are properly secured from external networks Encrypting radio transmissions on page 7-103: to configure the unit to operate with AES or DES wireless link security Requiring SM Authentication on page 7-104: to set up the AP to require SMs to authenticate via the AP, WM, or RADIUS server Filtering protocols and ports on page 7-105: to filter (block) specified protocols and ports from leaving the system Encrypting downlink broadcasts on page 7-108: to encrypt downlink broadcast transmissions Isolating SMs on page 7-108: to prevent SMs in the same sector from directly communicating with each other Filtering management through Ethernet on page 7-109: to prevent management access to the SM via the radios Ethernet port Allowing management only from specified IP addresses on page 7-109: to only allow radio management interface access from specified IP addresses Restricting radio Telnet access over the RF interface on page 7-109: to restrict Telnet access to the AP Configuring SNMP Access on page 7-112 Configuring Security on page 7-114 Page 7-100 Chapter 7: Configuration Configuring security Managing module access by password Applicable products PMP : AP SM PTP: BHM BMS See Managing module access by passwords on page 3-44. Adding a User for Access to a module The Account > Add User page allows to create a new user for accessing 450 Platform Family -

AP/SM/BHM/BHS. The Add User page is explained in Table 131. Table 131 Add User page of account page - AP/ SM/BH Attribute User Name Level New Password Confirm Password User Mode Meaning User Account name. Select appropriate level for new account. It can be INSTALLER, ADMINISTRATOR or TECHNICIAN. See Managing module access by passwords on page 3-44. Assign the password for new user account This new password must be confirmed in the Confirm Password field. User Mode is used to create an account which are mainly used for viewing the configurations. The local and remote Read-Only user account can be created by Admin, Installer or Tech logins. To create a Read-Only user, the read-only check box needs to be checked. Note The Read-Only user cannot perform any service impacting operations like creating read-

only accounts, editing and viewing read-only user accounts, changes in login page, read-

only user login, Telnet access, SNMP, RADIUS and upgrade/downgrade. Page 7-101 Chapter 7: Configuration Configuring security Deleting a User from Access to a module The Account > Delete User page provides a drop down list of configured users from which to select the user you want to delete. The Delele User page is explained in Table 132. Table 132 Delete User page - 450 Platform Family - AP/ SM/BH Attribute User Meaning Select a user from drop down list which has to be deleted and click Delete button. Accounts that cannot be deleted are the current user's own account. the last remaining account of ADMINISTRATOR level. Changing a User Setting The Account > Change User Setting page allows to update password, mode update and general status permission for a user. From the factory default state, configure passwords for both the root and admin account at the ADMINISTRATOR permission level, using Update Password tab of Change Users Setting page. The Change User Setting page is explained in Table 133. Table 133 Change User Setting page - 450 Platform Family AP/ SM/BH Attribute Meaning Page 7-102 Chapter 7: Configuration Configuring security Update Password tab This tab provides a drop down list of configured users from which a user is Update Mode tab General Status Permission tab selected to change password. This tab facilitates to convert a configured user to a Read-Only user. This tab enables and disables visibility of General Status Page for all Guest user. To display of Radio data on SMs/BHS main Login page for Guest login, it can be enabled or disabled in Security tab of Configuration page. Figure 138 AP Evaluation Configuration parameter of Security tab for PMP Figure 139 BHM Evaluation Configuration parameter of Security tab for PTP Users account The Account > Users page allows to view all configured users account for accessing the module. The Users page is explained in Table 134. Table 134 User page 450 Platform Family AP/SM/BH Attribute Username Permission Mode Meaning User access account name Permission of configured user INSTALLER, ADMINISTRATOR or TECHNICIAN This field indicate access mode of user Read-Write or Read-Only. Page 7-103 Chapter 7: Configuration Configuring security Overriding Forgotten IP Addresses or Passwords on AP and SM See Radio recovery mode on page 1-26 Isolating from the internet APs/BHMs Applicable products PMP : AP PTP: BHM See Isolating AP/BHM from the Internet on page 3-42. Encrypting radio transmissions Applicable products PMP : AP SM PTP: BHM BMS See Encrypting radio transmissions on page 3-42. Page 7-104 Chapter 7: Configuration Configuring security Requiring SM Authentication Applicable products PMP : AP SM Through the use of a shared AP key, or an external RADIUS (Remote Authentication Dial In User Service) server, it enhances network security by requiring SMs to authenticate when they register. For descriptions of each of the configurable security parameters on the AP, see Configuring Security on page 7-114. For descriptions of each of the configurable security parameters on the SM, see Security on page 7-119. Operators may use the APs Authentication Mode field to select from among the following authentication modes:

Disabledthe AP requires no SMs to authenticate (factory default setting). Authentication Server the AP requires any SM that attempts registration to be authenticated in Wireless Manager before registration AP PreShared Key - The AP acts as the authentication server to its SMs and will make use of a user-configurable pre-shared authentication key. The operator enters this key on both the AP and all SMs desired to register to that AP. There is also an option of leaving the AP and SMs at their default setting of using the Default Key. Due to the nature of the authentication operation, if you want to set a specific authentication key, then you MUST configure the key on all of the SMs and reboot them BEFORE enabling the key and option on the AP. Otherwise, if you configure the AP first, none of the SMs is able to register. RADIUS AAA - When RADIUS AAA is selected, up to 3 Authentication Server (RADIUS Server) IP addresses and Shared Secrets can be configured. The IP address(s) configured here must match the IP address(s) of the RADIUS server(s). The shared secret(s) configured here must match the shared secret(s) configured in the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not for splitting the database. If Server 1 doesnt respond, Server 2 is tried, and then server 3. If Server 1 rejects authentication, the SM is denied entry to the network, and does not progress trying the other servers. For more information on configuring the PMP 450 Platform network to utilize a RADIUS server, see Configuring a RADIUS server on page 7-226. Page 7-105 Chapter 7: Configuration Configuring security Filtering protocols and ports Applicable products PMP : AP SM PTP: BHM BMS The filtering protocols and ports allows to configure filters for specified protocols and ports from leaving the AP/SM/BHM/BHS and entering the network. See Filtering protocols and ports on page 3-45. Protocol filtering page of 450 Platform Family AP/BHM The Protocol Filtering page of 450 Platform Family - AP/BHM is explained in Table 135. Table 135 AP/BHM Protocol Filtering attributes Page 7-106 Chapter 7: Configuration Attribute Packet Filter Types Filter Direction Configuring security Meaning For any box selected, the Protocol and Port Filtering feature blocks the associated protocol type. To filter packets in any of the user-defined ports, must do all of the following:

Check the box for User Defined Port n (See Below) in the Packet Filter Types section of this tab. In the User Defined Port Filtering Configuration section of this tab:

provide a port number at Port #n. enable TCP and/or UDP by clicking the associated radio button Operators may choose to filter upstream (uplink) RF packets or downstream

(downlink) RF packets. User Defined Port Filtering Configuration You can specify ports for which to block subscriber access, regardless of whether NAT is enabled. RF Telnet Access PPPoE PADI Downlink Forwarding RF Telnet Access restricts Telnet access to the AP/BHM from a device situated below a network SM/BHS (downstream from the AP/BHM). This is a security enhancement to restrict RF-interface sourced AP access specifically to the LAN1 IP address and LAN2 IP address (Radio Private Address, typically 192.168.101.[LUID]). This restriction disallows unauthorized users from running Telnet commands on the AP/BHM that can change AP/BHM configuration or modifying network-critical components such as routing and ARP tables. Enabled: the AP/BHM allows downstream and upstream transmission of PPPoE PADI packets. By default, PPPoE PADI Downlink Forwarding is set to Enabled. Disabled: the AP/BHM disallows PPPoE PADI packets from entering the Ethernet interface and exiting the RF interface (downstream to the SM/BHS). PPPoE PADI packets are still allowed to enter the APs RF interface and exit the APs /BHMs Ethernet interface (upstream). Page 7-107 Chapter 7: Configuration Configuring security Protocol filtering page of SM/BHS The Protocol Filtering page of SM/BHS is explained in Table 136. Table 136 SM/BHS Protocol Filtering attributes Meaning See Table 135 AP/BHM Protocol Filtering attributes on page 7-105 See Table 135 AP/BHM Protocol Filtering attributes on page 7-105 Attribute Packet Filter Configuration tab User Defined Port Filtering Configuration tab Page 7-108 Chapter 7: Configuration Configuring security Port configuration 450 Platform Family ODUs support access to various communication protocols and only the ports required for these protocols are available for access by external entities. Operators may change the port numbers for these protocols via the radio GUI or SNMP. The Port Configuration page of the AP/SM/BHM/BHS is explained in Table 137. Table 137 Port Configuration attributes AP/SM/BHM/BMS Attribute FTP Port HTTP Port HTTPS Port Meaning The listen port on the device used for FTP communication. The listen port on the device used for HTTP communication. The listen port on the device used for HTTPS communication Radius Port Radius Accounting Port SNMP Port SNMP Trap Port The destination port used by the device for RADIUS communication. The destination port used by the device for RADIUS accounting communication. The listen port on the device used for SNMP communication. The destination port used by the device to which SNMP traps are sent. Syslog Server Port The destination port used by the device to which Syslog messaging is sent. Encrypting downlink broadcasts See Encrypting downlink broadcasts on page 3-49. Isolating SMs See Isolating SMs in PMP on page 3-49. Page 7-109 Chapter 7: Configuration Configuring security Filtering management through Ethernet See Filtering management through Ethernet on page 3-49. Allowing management only from specified IP addresses See Allowing management from only specified IP addresses on page 3-50. Restricting radio Telnet access over the RF interface RF Telnet Access restricts Telnet access to the AP from a device situated below a network SM

(downstream from the AP). This is a security enhancement to restrict RF-interface sourced AP access specifically to the LAN1 IP address and LAN2 IP address (Radio Private Address, typically 192.168.101.

[LUID]). This restriction disallows unauthorized users from running Telnet commands on the AP that can change AP configuration or modifying network-critical components such as routing and ARP tables. The RF Telnet Access may be configured via the AP GUI or via SNMP commands, and RF Telnet Access is set to Enabled by default. Once RF Telnet Access is set to Disabled, if there is a Telnet session attempt to the AP originating from a device situated below the SM (or any downstream device), the attempt is dropped. This also includes Telnet session attempts originated from the SMs management interface (if a user has initiated a Telnet session to a SM and attempts to Telnet from the SM to the AP). In addition, if there are any active Telnet connections to the AP originating from a device situated below the SM (or any downstream device), the connection is dropped. This behavior must be considered if system administrators use Telnet downstream from an AP (from a registered SM) to modify system parameters. Setting RF Telnet Access to Disabled does not affect devices situated above the AP from accessing the AP via Telnet, including servers running the CNUT (Canopy Network Updater tool) application. Also, setting RF Telnet Access to Disabled does not affect any Telnet access into upstream devices (situated above or adjacent to the AP) through the AP (see Figure 140). The figure below depicts a user attempting two telnet sessions. One is targeted for the AP (orange) and one is targeted for the network upstream from the AP (green). If RF Telnet Access is set to Disabled

(factory default setting), the Telnet attempt from the user to the AP is blocked, but the attempt from the user to Network is allowed to pass through the Cambium network. Figure 140 RF Telnet Access Restrictions (orange) and Flow through (green) Page 7-110 Chapter 7: Configuration Configuring security Key Security Considerations when using the RF Telnet Access Feature To ensure that the network is fully protected from unauthorized AP Telnet sessions, the following topics must be considered:

Securing AP Clusters When working with a cluster of AP units, to eliminate potential security holes allowing Telnet access, ensure that the RF Telnet Access parameter is set to Disabled for every AP in the cluster. In addition, since users situated below the AP are able to pass Telnet sessions up through the SM and AP to the upstream network (while AP RF Telnet Access is set to Disabled), ensure that all CMM4 or other networking equipment is secured with strong passwords. Otherwise, users may Telnet to the CMM4 or other networking equipment, and subsequently access network APs (see Figure 141) via their Ethernet interfaces (since RF Telnet Access only prevents Telnet sessions originating from the APs wireless interface). Figure 141 RF Telnet Access Restriction (orange) and Potential Security Hole (green) As a common practice, AP administrator usernames and passwords must be secured with strong, non-

default passwords. Restricting AP RF Telnet Access AP Telnet access via the RF interface may be configured in two ways the AP GUI and SNMP. Controlling RF Telnet Access via the AP GUI To restrict all Telnet access to the AP via the RF interface from downstream devices, follow these instructions using the AP GUI:

Procedure 20 Restricting RF Telnet access Log into the AP GUI using administrator credentials 1 2 On the AP GUI, navigate to Configuration > Protocol Filtering Page 7-111 Chapter 7: Configuration Configuring security 3 Under GUI heading Telnet Access over RF Interface, set RF Telnet Access to Disabled Click the Save button 4 5 Once the Save button is clicked, all RF Telnet Access to the AP from devices situated below the AP is blocked. Note The factory default setting for RF Telnet Access is disabled and PPPoE PADI Downlink Forwarding is enabled. Page 7-112 Chapter 7: Configuration Configuring security Configuring SNMP Access The SNMPv3 interface provides a more secure method to perform SNMP operations. This standard provides services for authentication, data integrity and message encryption over SNMP. Refer to Planning for SNMPv3 operation on page 3-43 for details. Note The factory default setting for SNMP is SNMPv2c Only. Procedure 21 Configuring SNMPv3 1 Log into the AP GUI using administrator credentials 2 On the AP/SM GUI, navigate to Configuration > Security Page 3 Under GUI heading Security Mode, set SNMP to SNMPv3 Only 4 Click the Save Changes button 5 Go to Configuration > SNMP Page 6 Under GUI heading SNMPv3 setting, set Engine ID, SNMPv3 Security Level, SNMPv3 Authentication Protocol, SNMPv3 Privacy Protocol, SNMPv3 Read-Only User, SNMPv3 Read/Write User, SNMPv3 Trap Configuration parameters:

Engine ID :

Each radio (AP/SM/BHM/BHS) has a distinct SNMP authoritative engine identified by a unique Engine ID. While the Engine ID is configurable to the operator it is expected that the operator follow the guidelines of the SNMPEngineID defined in the SNMP-FRAMEWORK-

MIB (RFC 3411). The default Engine ID is the MAC address of the device. SNMPv3 security level, Authentication and Privacy Protocol The authentication allows authentication of SNMPv3 user and privacy allows for encryption of SNMPv3 message. 450 Platform Family supports MD5 authentication and CBC-DES privacy protocols. Page 7-113 Chapter 7: Configuration Configuring security SNMPv3 Read-Only and Read/Write User The user can defined by configurable attributes. The attributes and default values are:

Read-only user o Username = Canopyro o Authentication Password = authCanopyro o Privacy Password = privacyCanopyro Read-write user (by default read-write user is disabled) o Username = Canopy o Authentication Password = authCanopy o Privacy Password = privacyCanopy SNMPv3 Trap Configuration The traps may be sent from radios in SNMPv3 format based on parameter settings. It can be configured for Disabled, Enabled for Read-Only User, Enable for Read/Write User. Page 7-114 Chapter 7: Configuration Configuring Security Configuring security Applicable products PMP : AP SM PTP: BHM BMS Security page 450 Platform Family AP/BHM The security page of AP/BHM is explained in Table 138. Table 138 Security attributes 450 Platform Family AP Page 7-115 Chapter 7: Configuration Configuring security Attribute Authentication Mode Meaning Operators may use this field to select from among the following authentication modes:

Disabledthe AP/BHM requires no SMs/BHS to authenticate. (Factory default). Authentication Server the AP/BHM requires any SM/BHS that attempts registration to be authenticated in Wireless Manager before registration. AP PreShared Key - The AP/BHM acts as the authentication server to its SMs/BHS and will make use of a user-configurable pre-shared authentication key. The operator enters this key on both the AP/BHM and all SMs/BHS desired to register to that AP/BHM. There is also an option of leaving the AP/BHM and SMs/BHS at their default setting of using the Default Key. Due to the nature of the authentication operation, if you want to set a specific authentication key, then you MUST configure the key on all of the SMs/BHS and reboot them BEFORE enabling the key and option on the AP/BHM. Otherwise, if you configure the AP/BHM first, none of the SMs/BHS is able to register. RADIUS AAA - When RADIUS AAA is selected, up to 3 Authentication Server (RADIUS Server) IP addresses and Shared Secrets can be configured. The IP address(s) configured here must match the IP address(s) of the RADIUS server(s). The shared secret(s) configured here must match the shared secret(s) configured in the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not for splitting the database. If Server 1 doesnt respond, Server 2 is tried, and then server 3. If Server 1 rejects authentication, the SM is denied entry to the network, and does not progress trying the other servers. Note This parameter is applicable to BHM. Page 7-116 Chapter 7: Configuration Configuring security Authentication Server DNS Usage The management DNS domain name may be toggled such that the name of the authentication server only needs to be specified and the DNS domain name is automatically appended to that name. Authentication Server 1 to 5 Radius Port Note This parameter is applicable to BHM. Enter the IP address or server name of the authentication server (RADIUS or WM) and the Shared Secret configured in the authentication server. When Authentication Mode RADIUS AAA is selected, the default value of Shared Secret is CanopySharedSecret. The Shared Secret may consist of up to 32 ASCII characters. Note This parameter is applicable to BHM. This field allows the operator to configure a custom port for RADIUS server communication. The default value is 1812. Note This parameter is applicable to BHM. Authentication Key The authentication key is a 32-character hexadecimal string used when Authentication Mode is set to AP PreShared Key. By default, this key is set to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF. Note This parameter is applicable to BHM. Select Key This option allows operators to choose which authentication key is used:

Use Key above means that the key specified in Authentication Key is used for authentication Use Default Key means that a default key (based off of the SMs MAC address) is used for authentication Note This parameter is applicable to BHM. Dynamic Authorization Extensions for RADIUS Bypass Authentication for ICC SMs Encryption Setting Enable CoA and Disconnect Message: Allows to control configuration parameters of SM using RADIUS CoA and Disconnect Message feature. Disable CoA and Disconnect Message: Disables RADIUS CoA and Disconnect Message feature. To enable CoA and Disconnect feature, the Authentication Mode should be set to RADIUS AAA. Enabled: SM authentication is disabled when SM connects via ICC

(Installation Color Code). Disabled: SM authentication is enabled. Specify the type of airlink security to apply to this AP. The encryption setting must match the encryption setting of the SMs. Page 7-117 Chapter 7: Configuration Configuring security None provides no encryption on the air link. DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. Note This parameter is applicable to BHM. SM Display of AP Evaluation Data Or BHS Display of BHM Evaluation Data Allows operators to suppress the display of data about this AP/BHM on the AP/BHM Evaluation tab of the Tools page in all SMs/BHS that register. The factory default setting for SM Display of AP Evaluation Data or BHS Display of BHM Evaluation Data is enabled display. PMP 450/450i Series SM display of AP Evaluation Data parameter PTP 450/450i Series BHS display of BHM Evaluation Data parameter Web, Telnet, FTP Session Timeout IP Access Control Allowed Source IP 1 to 3 Web Access Enter the expiry in seconds for remote management sessions via HTTP, telnet, or ftp access to the AP/BHM. You can permit access to the AP/BHM from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address If you selected IP Access Filtering Enabled for the IP Access Control parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the AP from any IP address. You may populate as many as all three. If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. The Radio supports secured and non-secured web access protocols. Select suitable web access from drop down list:

Page 7-118 Chapter 7: Configuration Configuring security HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. This option allows to configure SNMP agent communication version. It can be selected from drop down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is a secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. SNMP Telnet FTP TFTP Page 7-119 Chapter 7: Configuration Configuring security Security page - 450 Platform Family SM The security page of 450 Platform Family SM is explained in Table 139. Table 139 Security attributes 450 Platform Family SM Page 7-120 Chapter 7: Configuration Configuring security Attribute Authentication Key Select Key Meaning Only if the AP to which this SM will register requires authentication, specify the key that the SM will use when authenticating. For alpha characters in this hex key, use only upper case. The Use Default Key selection specifies the predetermined key for authentication in Wireless Manager The Use Key above selection specifies the 32-digit hexadecimal key that is permanently stored on both the SM and the WM Enforce Authentication The SM may enforce authentication types of AAA and AP Pre-sharedKey. Phase 1 The SM will not finish the registration process if the AP is not using the configured authentication method (and the SM locks out the AP for 15 minutes). The protocols supported for the Phase 1 (Outside Identity) phase of authentication are EAPTTLS (Extensible Authentication Protocol Tunneled Transport Layer Security) or MSCHAPv2 (Microsoft Challenge-Handshake Authentication Protocol version 2). Page 7-121 Chapter 7: Configuration Phase 2 Identity/Realm Username Password Configuring security Select the desired Phase 2 (Inside Identity) authentication protocol from the Phase 2 options of PAP (Password Authentication Protocol), CHAP

(Challenge Handshake Authentication Protocol), and MSCHAP (Microsofts version of CHAP, version 2 is used). The protocol must be consistent with the authentication protocol configured on the RADIUS server. If Realms are being used, select Enable Realm and configure an outer identity in the Identity field and a Realm in the Realm field. These must match the Phase 1/Outer Identity and Realm configured in the RADIUS server. The default Identity is anonymous. The Identity can be up to 128 non-special (no diacritical markings) alphanumeric characters. The default Realm is canopy.net. The Realm can also be up to 128 non-special alphanumeric characters. Configure an outer Identity in the Username field. This must match the Phase 1/Outer Identity username configured in the RADIUS server. The default Phase 1/Outer Identity Username is anonymous. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. Enter a Username for the SM. This must match the username configured for the SM on the RADIUS server. The default Username is the SMs MAC address. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. Enter the desired password for the SM in the Password and Confirm Password fields. The Password must match the password configured for the SM on the RADIUS server. The default Password is password. The Password can be up to 128 non-special (no diacritical markings) alphanumeric characters Upload Certificate File To upload a certificate manually to a SM, first load it in a known place on your PC or network drive, then click on a Delete button on one of the Certificate description blocks to delete a certificate to provide space for your certificate. Click on Choose File, browse to the location of the certificate, and click the Import Certificate button, and then reboot the radio to use the new certificate. When a certificate is in use, after the SM successfully registers to an AP, an indication of In Use will appear in the description block of the certificate being used. The public certificates installed on the SMs are used with the private certificate on the RADIUS server to provide a public/private key encryption system. Up to 2 certificates can be resident on a SM. An installed certificate can be deleted by clicking the Delete button in the certificates description block on the Configuration > Security tab. To restore the 2 default certificates, click the Use Default Certificates button in the RADIUS Certificate Settings parameter block and reboot the radio. Page 7-122 Chapter 7: Configuration Encryption Setting Web, Telnet, FTP Session Timeout Ethernet Access IP Access Control Allowed Source IP 1 to 3 Configuring security Specify the type of airlink security to apply to this SM. The encryption setting must match the encryption setting of the AP. None provides no encryption on the air link. DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. Enter the expiry in seconds for remote management sessions via HTTP, telnet, or FTP access to the SM. If you want to prevent any device that is connected to the Ethernet port of the SM from accessing the management interface of the SM, select Ethernet Access Disabled. This selection disables access through this port to via HTTP (the GUI), SNMP, telnet, FTP, and TFTP. With this selection, management access is available through only the RF interface via either an IP address (if Network Accessibility is set to Public on the SM) or the Session Status or Remote Subscribers tab of the AP. Note This setting does not prevent a device connected to the Ethernet port from accessing the management interface of other SMs in the network. To prevent this, use the IP Access Filtering Enabled selection in the IP Access Control parameter of the SMs in the network. See IP Access Control below. If you want to allow management access through the Ethernet port, select Ethernet Access Enabled. This is the factory default setting for this parameter. You can permit access to the SM from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address If you selected IP Access Filtering Enabled for the IP Access Control parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the SM from any IP address. You may populate as many as all three. If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. A subnet mask may be defined for each entry to allow for filtering control based on a range of IP addresses. Page 7-123 Chapter 7: Configuration Web Access SNMP Telnet FTP TFTP Site Name Site Contact Configuring security The Radio supports secured and non-secured web access protocols. Select suitable web access from drop down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. This option allows to configure SNMP agent communication version. It can be selected from drop down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. Specify a string to associate with the physical module. Enter contact information for the module administrator. Site Location Enable Security Banner during Login Security Banner Notice User must accept security banner before login Enter information about the physical location of the module. Enable: The Security Banner Notice will be displayed before login. Disable: The Security Banner Notice will not be displayed before login. User can enter ASCII (0-9a-zA-Z newline, line-feed are allowed) text up-to 1300 characters. Enable: login area (username and password) will be disabled unless user accepts the security banner. Disable: User cant login to radio without accepting security banner. Page 7-124 Chapter 7: Configuration Configuring security Security page 450 Platform Family BHS The Security page of 450 Platform Family BHS is explained in Table 140. Table 140 Security attributes - 450 Platform Family BHS Attribute Authentication Key Encryption Setting Meaning Only if the BHM to which this BHS registers requires an authentication, specify the key that the BHS will use when authenticating. For alpha characters in this hex key, use only upper case. Specify the type of airlink security to apply to this BHS. The encryption setting must match the encryption setting of the BHM. None provides no encryption on the air link. DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. It is factory default setting. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. Page 7-125 Chapter 7: Configuration Web, Telnet, FTP Session Timeout IP Access Control Allowed Source IP 1 to 3 Web Access SNMP Telnet FTP TFTP Configuring security Enter the expiry in seconds for remote management sessions via HTTP, telnet, or FTP access to the BHS. You can permit access to the BHS from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address If you selected IP Access Filtering Enabled for the IP Access Control parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the BHS from any IP address. You may populate as many as all three. If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. A subnet mask may be defined for each entry to allow for filtering control based on a range of IP addresses. The Radio supports secured and non-secured web access protocols. Select suitable web access from drop down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. This option allows to configure SNMP agent communication version. It can be selected from drop down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. Page 7-126 Chapter 7: Configuration Configuring radio parameters Configuring radio parameters PMP 450m Series configuring radio on page 7-127 PMP/PTP 450i Series configuring radio on page 7-127 PMP 450b Series - configuring radio on page 7-151 PMP/PTP 450 Series configuring radio on page 7-155 Custom Frequencies page on page 7-172 DFS for 5 GHz Radios on page 7-175 MIMO-A mode of operation on page 7-177 Improved PPS performance of 450 Platform Family on page 7-179 Page 7-127 Chapter 7: Configuration Configuring radio parameters PMP 450m Series configuring radio Radio page - PMP 450m AP 5 GHz The Radio tab of the PMP 450m AP contains some of the configurable parameters that define how an AP operates. Note Only the frequencies available for your region and the selected Channel bandwidth are displayed. Table 141 PMP 450m AP Radio attributes - 5 GHz Page 7-128 Chapter 7: Configuration Attribute Frequency Band Frequency Carrier Channel Bandwidth Cyclic Prefix Color Code Subscriber Color Code Rescan (When not on a Primary Color Code) Subscriber Color Code Wait Period for Idle Configuring radio parameters Meaning Select the desired operating frequency band. Specify the frequency for the module to transmit. The default for this parameter is None. For a list of channels in the band, see the drop-down list on the radio GUI. The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the AP and the SM. The supported Channel Bandwidths are 5MHz, 10 MHz, 15 MHz, 20 MHz, and 40 MHz. OFDM technology uses a cyclic prefix, where a portion of the end of a symbol

(slot) is repeated at the beginning of the symbol to allow multi-pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. Specify a value from 0 to 254. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). This timer may be utilized to initiate SM rescans in order to register to an AP configured with the SMs primary color code. The time (in minutes) for a subscriber to rescan (if this AP is not configured with the SMs primary color code). This timer will only fire once if the Subscriber Color Code Wait Period for Idle timer is configured with a nonzero value and the Subscriber Color Code Rescan expires, the Subscriber Color Code Wait Period for Idle is started. If the Subscriber Color Code Wait Period for Idle timer is configured with a zero value and the Subscriber Color Code Rescan timer expires, the SM will immediately go into rescan mode The time (in minutes) for a subscriber to rescan while idle (if this AP is not configured with the SMs primary color code). This timer will fire periodic events. The fired event determines if any RF unicast traffic (either inbound or outbound) has occurred since the last event. If the results of the event determine that no RF unicast traffic has occurred (SM is idle), then the subscriber will rescan. Page 7-129 Chapter 7: Configuration Installation Color Code Max Range Downlink Data Configuring radio parameters With this feature enabled on the AP and SM, operators may install and remotely configure SMs without having to configure matching color codes between the modules. While the SM is accessible for configuration from above the AP (for remote provisioning) and below the SM (for local site provisioning), no user data is passed over the radio link. When using the Installation Color Code feature, ensure that the SM is configured with the factory default Color Code configuration (Color Code 1 is 0, Color Code 2-

10 set to 0 and Disable). The status of the Installation Color Code can be viewed on the AP Eval web GUI page, and when the SM is registered using the Installation Color Code the message SM is registered via ICC Bridging Disabled! is displayed in red on every SM GUI page. The Installation Color Code parameter is configurable without a radio reboot for both the AP and SM. If a SM is registered via Installation Color Code and the feature is then disabled, operators will need to reboot the SM or force it to reregister (i.e. using Rescan APs functionality on the AP Eval page). Enter a number of miles (or kilometers divided by 1.61, then rounded to an integer) for the furthest distance from which a SM is allowed to register to this AP. Do not set the distance to any greater number of miles. A greater distance does not increase the power of transmission from the AP. For example, with a 20 MHz channel and 2.5 ms frame, every additional 2.24 miles reduces the data air time by one symbol (around 1% of the frame). Regardless of this distance, the SM must meet the minimum requirements for an acceptable link. The parameters have to be selected so that there is no overlap between one AP transmitting and another AP receiving. A co-location tool is provided to help with selecting sets of parameters that allow co-

location. The default value of this parameter is 2 miles (3.2 km). Specify the percentage of the aggregate throughput for the downlink (frames transmitted from the AP to the subscriber). For example, if the aggregate

(uplink and downlink total) throughput on the AP is 90 Mb, then 75% specified for this parameter allocates 67.5 Mb for the downlink and 22.5 Mb for the uplink. The default for this parameter is 75%. This parameter must be set in the range of 15% - 85%, otherwise the invalid input will not be accepted and the previously-entered valid setting is used. can reduce aggregate throughput. Note In order to prevent self-interference, the frame configuration needs to align which includes Downlink Data, Max Range and Contention slots. For DFS regions, the maximum Downlink % for a 5.4 GHz radio is 75% only. Contention Slots

(a.k.a. Control Slots) This field indicates the number of (reserved) Contention slots configured by the operator. The SM uses reserved Contention slots and unused data slots for bandwidth requests. See Contention slots on page 7-176. Page 7-130 Chapter 7: Configuration Configuring radio parameters EIRP SM Receive Target Level Receive Quality Debug Near Field Operation This field indicates the combined power level at which the AP will transmit, based on the Country Code. It also includes the antenna gain and array gain. Each SMs Transmitter Output Power is automatically set by the AP. The AP monitors the received power from each SM, and adjusts each SMs Transmitter Output Power so that the received power at the AP from that SM is not greater what is set in this field. This value represents the transmitted and received power (combined power) perceived on the SM. To aid in link performance monitoring, the AP and SM now report the number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-QAM and 256-

QAM) and per channel (polarization). Note Due to CPU load, this will slightly degrade packet per second processing. This parameter is enabled by the Near Field Operation control. This is only available when the EIRP is set to 22 dBm or below. When Near Field Operation is enabled, the Near Field Range is used to apply compensation to the units calibration to support operation in the near field. Page 7-131 Chapter 7: Configuration Configuring radio parameters PMP/PTP 450i Series configuring radio Radio page - PMP 450i AP 3 GHz The Radio tab of the PMP 450i AP 3 GHz is shown in Figure 142. Figure 142 PMP 450i AP Radio attributes - 3 GHz Page 7-132 Chapter 7: Configuration Configuring radio parameters Note Refer Table 143 PMP 450i SM Radio attributes 5 GHz on page 7-138 for parameter details Radio page - PMP 450i AP 5 GHz The Radio tab of the PMP 450i AP contains some of the configurable parameters that define how an AP operates. Note Only the frequencies available for your region and the selected Channel bandwidth are displayed. Table 142 PMP 450i AP Radio attributes - 5 GHz Page 7-133 Chapter 7: Configuration Configuring radio parameters Meaning See Table 141 PMP 450m AP Radio attributes - 5 GHz on page 7-127 These parameters are displayed based on Regional Settings. Refer Country on page 7-70 See Table 141 PMP 450m AP Radio attributes - 5 GHz on page 7-127 Attribute Frequency Band Frequency Carrier Alternate Frequency Carrier 1 and 2 Channel Bandwidth Cyclic Prefix Frame Period Color Code Subscriber Color Code Rescan (When not on a Primary Color Code) Subscriber Color Code Wait Period for Idle Installation Color Code Max Range Downlink Data See Table 141 PMP 450m AP Radio attributes - 5 GHz on page 7-127 Page 7-134 Chapter 7: Configuration Contention Slots

(a.k.a. Control Slots) Broadcast Repeat Count Transmitter Output Power Configuring radio parameters This field indicates the number of (reserved) Contention slots configured by the operator. The SM uses reserved Contention slots and unused data slots for bandwidth requests. See Contention slots on page7-176. The default is 2 repeats (in addition to the original broadcast packet, for a total of 3 packets sent for every one needed), and is settable to 1 or 0 repeats

(2 or 1 packets for every broadcast). ARQ (Automatic Repeat reQuest) is not present in downlink broadcast packets, since it can cause unnecessary uplink traffic from every SM for each broadcast packet. For successful transport without ARQ, the AP repeats downlink broadcast packets. The SMs filter out all repeated broadcast packets and, thus, do not transport further. The default of 2 repeats is optimum for typical uses of the network as an internet access system. In applications with heavy download broadcast such as video distribution, overall throughput is significantly improved by setting the repeat count to 1 or 0. This avoids flooding the downlink with repeat broadcast packets. This value represents the combined power of the APs two transmitters. Nations and regions may regulate transmitter output power. For example 900 MHz, 5.4 GHz and 5.8 GHz modules are available as connectorized radios, which require the operator to adjust power to ensure regulatory compliance. The professional installer of the equipment has the responsibility to maintain awareness of applicable regulations. calculate the permissible transmitter output power for the module. confirm that the initial power setting is compliant with national or regional regulations. confirm that the power setting is compliant following any reset of the module to factory defaults. External Gain SM Receive Target Level Multicast VC Data Rate This value needs to correspond to the published gain of the antenna used to ensure the radio will meet regulatory requirements. See Table 141 PMP 450m AP Radio attributes - 5 GHz on page 7-127 This pull down menu of the Multicast Data Control screen helps in configuring multicast packets to be transmitted over a dedicated channel at a configurable rate of 1X, 2X, 4X or 6X. The default value is Disable. If set to the default value, all multicast packets are transmitted over the Broadcast VC data path. This feature is available only for the PMP 450 Series and is not backward compatible with PMP 430 series of radios. Page 7-135 Chapter 7: Configuration Multicast Repeat Count Multicast Downlink CIR SM Registration All PMP 430 SM Registration Control Message PMP 450/430 Legacy mode PMP 430 Interop Mode Receive Quality Debug Configuring radio parameters This value is the number of packets that are repeated for every multicast VC packet received on the AP (located under Radio tab of Configuration). Multicast (like Broadcast) packets go over a VC that is shared by all SMs, so there is no guaranteed delivery. The repeat count is an attempt to improve the odds of the packets getting over the link. If the user has issues with packets getting dropped, they can use this parameter to improve the performance at the cost of the overall throughput possible on that channel. The default value is 0. This value is the committed information rate for the multicast downlink VC

(located under the Radio tab of Configuration). The default value is 0 kbps. The range of this parameter is based on the number of repeat counts. The higher the repeat count, the lower the range for the multicast downlink CIR. This field allows to control registration of all type 450 Platform Family SM including 430 Series SM(450i/450/430) or 450i Series SM only. This field allows to control of PMP 430 SMs whether PMP 430 SMs are allowed to register to PMP 450i APs. By default, it is enabled and PMP 430 SM registrations are accepted. When this field is set to disabled, PMP 430 SMs registrations fail with reject reason 8. This will cause SMs to lock out the AP for 15 minutes. Note This option is not displayed if the Frame Period is set to 5 ms. This option applies only to PMP 450/450i Series APs -

5 GHz. Controls whether the control messages are sent in MIMO-B or MIMO-A mode. MIMO-A is recommended. However, if an AP on 13.2 is attempting to connect to an SM on 13.1.3 or before, changing to MIMO-B may aid in getting the SM registered. Disabled: It is factory default setting. It allows to operate in 450i Series capabilities. Enabled: It allows to operate radio in Legacy mode PMP 450 or 430. For n-1 compatibility, In SISO mode this forces the AP to only send Control and Beacons over one of the RF paths. To aid in link performance monitoring, the AP and SM now report the number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-QAM) and per channel (polarization). Note Due to CPU load, this will slightly degrade packet per second processing. Frame Alignment Legacy Mode Mode Behavior (non-900 MHz radios) Behavior (FSK 900 MHz radios) Page 7-136 Chapter 7: Configuration Configuring radio parameters OFF By default frame start is aligned with devices with Timing Port synchronization By default frame start is aligned with FSK 900 MHz devices with Timing Port synchronization If the synchronization source changes (due to Autosync or otherwise) the radio will dynamically adjust its frame start to maintain alignment with the default frame start timing If the synchronization source changes (due to Autosync or otherwise) the radio will dynamically adjust its frame start to maintain alignment with the default frame start timing ON

(Mode 1) The radio will align with devices running software versions from 12.0 to 13.4. The radio will align with FSK 900 MHz devices running software versions from 12.0 to 13.4. ON

(Mode 2) N/A The radio will align with FSK 900 MHz devices with software versions 11.2 or older. Page 7-137 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450i SM 3 GHz The Radio tab of the PMP 450i SM 3 GHz is shown in Figure 143. Figure 143 PMP 450i SM Radio attributes - 3 GHz Note Refer Table 143 PMP 450i SM Radio attributes 5 GHz on page 7-138 for parameter details Page 7-138 Chapter 7: Configuration Configuring radio parameters Radio page PMP 450i SM 5 GHz The Radio page of PMP 450i SM is explained in Table 143. Table 143 PMP 450i SM Radio attributes 5 GHz Page 7-139 Chapter 7: Configuration Configuring radio parameters Page 7-140 Chapter 7: Configuration Configuring radio parameters Page 7-141 Chapter 7: Configuration Attribute Custom Radio Frequency Scan Selection List Channel Bandwidth Scan Configuring radio parameters Meaning Check the frequencies that SM has to scan for AP transmissions. See Radio Frequency Scan Selection List on page 7-169. The channel size used by the radio for RF transmission. Note Selecting multiple channel bandwidths will increase registration and re-registration times. Cyclic Prefix Scan The cyclic prefix for which AP scanning is executed. AP Selection Method Operators may configure the method by which a scanning SM selects an AP. Color Code 1 By default, AP Selection Method is set to Optimize for Throughput, which has been the mode of operation in releases prior to 12.0.3.1. Power Level: AP selection based solely on power level Note For operation with a PMP 450m AP, select the Power Level option or Optimize for Throughput: AP selection based on throughput optimization the selection decision is based on power level (which affects the modulation state), channel bandwidth (which affects throughput) and number of SM registrations to the AP (which affects system contention performance). Color code allows you to force the SM to register to only a specific AP, even where the SM can communicate with multiple APs. For registration to occur, the color code of the SM and the AP must match. Specify a value from 0 to 254. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). SMs may be configured with up to 20 color codes. These color codes can be tagged as Primary, Secondary, or Tertiary, or Disable. When the SM is scanning for APs, it will first attempt to register to an AP that matches one of the SMs primary color codes. Failing that, the SM will continue scanning and attempt to register to an AP that matches one of the SMs secondary color codes. Failing that, the SM will continue scanning and attempt to register to an AP that matches one of the SMs tertiary color codes. This is all done in the scanning mode of the SM and will repeat until a registration has occurred. Page 7-142 Chapter 7: Configuration Configuring radio parameters Color codes in the same priority group are treated equally. For example, all APs matching one of the SMs primary color codes are analyzed equally. Likewise, this evaluation is done for the secondary and tertiary groups in order. The analysis for selecting an AP within a priority group is based on various inputs, including signal strength and number of SMs already registered to each AP. The first color code in the configuration is the pre-Release 9.5 color code. Thus, it is always a primary color code for legacy reasons. The color codes can be disabled, with the exception of the first color code. With this feature enabled on the AP and SM, operators may install and remotely configure SMs without having to configure matching color codes between the modules. When using the Installation Color Code feature, ensure that the SM is configured with the factory default Color Code configuration

(Color Code 1 is 0, Color Code 2-10 set to 0 and Disable). The status of the Installation Color Code can be viewed on the AP Eval web GUI page, and when the SM is registered using the Installation Color Code the message SM is registered via ICC Bridging Disabled! is displayed in red on every SM GUI page. The Installation Color Code parameter is configurable without a radio reboot for both the AP and SM. This value represents the antenna gain. For ODUs with integrated antenna, this is set at the correct value in the factory. For Connectorized ODUs with external antenna, the user must set this value to the overall antenna gain, including any RF cable loss between the ODU and the antenna. Installation Color Code External Gain Large VC data Queue SM and BH have a configurable option used to prevent packet loss in the Receive Quality Debug uplink due to bursting IP traffic. This is designed for IP burst traffic particular to video surveillance applications. To aid in link performance monitoring, the AP and SM now report the number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-QAM) and per channel (polarization). Note Due to CPU load, this will slightly degrade packet per second processing. Note The frequencies that a user can select are controlled by the country or a region and the Channel Bandwidth selected. There can be a case where a user adds a custom frequency

(from the Custom Frequencies page on page 7-172) and cannot see it in the pull down menu. Page 7-143 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450i AP 900 MHz The Radio tab of the PMP 450i AP 900 MHz is described in below table Table 144. Table 144 PMP 450i AP Radio attributes - 900 MHz Page 7-144 Chapter 7: Configuration Attribute Frequency Carrier Channel Bandwidth Cyclic Prefix Frame Period Color Code Subscriber Color Code Rescan (When not on a Primary Color Code) Subscriber Color Code Wait Period for Idle Installation Color Code Max Range Downlink Data Contention Slots

(a.k.a. Control Slots) Broadcast Repeat Count Transmitter Output Power External Gain SM Receive Target Level Multicast VC Data Rate Multicast Repeat Count Multicast Downlink CIR Control Message Receive Quality Debug Pager Reject Filter Configuring radio parameters Meaning Specify the frequency for the module to transmit. The default for this parameter is None. For a list of channels in the band, see the drop-down list on the radio GUI. The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the AP and the SM. The supported Channel Bandwidths are 5, 7, 10 and 20 MHz. See Table 141 PMP 450m AP Radio attributes - 5 GHz on page 7-127. See Table 141 PMP 450m AP Radio attributes - 5 GHz on page 7-127. See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132. See Table 141 PMP 450m AP Radio attributes - 5 GHz on page 7-127 In 900 MHz, Pager Reject filter is placed on the AP to block Pager signals which could cause interference to the whole band. The Pager signals typically operate in the 928-930 frequency range. When the filter is enabled, the signals of 920 MHz and above are attenuated which enables better reception of signals in the rest of the band. Note that the AP/SM should not be configured on the frequencies of 920 MHz and above when this filter is enabled. Page 7-145 Chapter 7: Configuration Frame Alignment Legacy Mode Configuring radio parameters See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132. Radio page - PTP 450i BHM 5 GHz The Radio page of PTP 450i BHM is explained in Table 145. Table 145 PTP 450i BHM Radio page attributes 5 GHz Page 7-146 Chapter 7: Configuration Attribute Frequency Band Frequency Carrier Configuring radio parameters Meaning Select the operating frequency band of the radio. The supported bands are 4.9 GHz, 5.4 GHz and 5.7 GHz. Specify the frequency for the module to transmit. The default for this parameter is None. For a list of channels in the band, see the drop-down list on the radio GUI. Channel Bandwidth The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the BHM and the BHS. Cyclic Prefix Frame Period Color Code Large VC data Q Downlink Data OFDM technology uses a cyclic prefix, where a portion of the end of a symbol

(slot) is repeated at the beginning of the symbol to allow multi-pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. Select the Frame Period of the radio. The support Frame Periods are : 5 ms and 2.5 ms. Specify a value from 0 to 254. For registration to occur, the color code of the BHM and the BHS must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each link a different color code. Color code allows you to force a BHS to register to only a specific BHM. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Enable Large VC Q for applications that burst data high rates. Large Qs may decrease effective throughput for TCP application. Disable Large VC Q if application need not handle bursts of data. Large Qs may decrease effective throughput for TCP application. Specify the percentage of the aggregate throughput for the downlink (frames transmitted from the BHM to the subscriber). For example, if the aggregate

(uplink and downlink total) throughput on the BHM is 132 Mbps, then 75%

specified for this parameter allocates 99 Mbps for the downlink and 33 Mbps for the uplink. The default for this parameter is 50%. This parameter must be set in the range of 15% - 85%, otherwise the invalid input will not be accepted and the previously-entered valid setting is used. Note In order to prevent self-interference, the frame configuration needs to align. This includes Downlink Data, Max Range and Contention slots. Transmit Power This value represents the combined power of the BHMs two transmitters. Nations and regions may regulate transmit power. For example PTP 450i Series modules are available as connectorized radios, which require the operator to adjust power to ensure regulatory compliance. Page 7-147 Chapter 7: Configuration Configuring radio parameters The professional installer of the equipment has the responsibility to:

Maintain awareness of applicable regulations. Calculate the permissible transmitter output power for the module. Confirm that the initial power setting is compliant with national or regional regulations. Confirm that the power setting is compliant following any reset of the module to factory defaults. This value needs to correspond to the published gain of the antenna used to ensure the radio will meet regulatory requirements. To aid in link performance monitoring, the BHM and BHS now report the number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-QAM and 256-QAM) and per channel (polarization). Note Due to CPU load, this slightly degrades the packet during per second processing. External Gain Receive Quality Debug Frame Alignment Legacy Mode See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132. Page 7-148 Chapter 7: Configuration Configuring radio parameters Radio page PTP 450i BHS 5 GHz The Radio page of PTP 450i BHS is explained in Table 146. Table 146 PTP 450i BHS Radio attributes 5 GHz Page 7-149 Chapter 7: Configuration Configuring radio parameters Attribute Custom Radio Frequency Scan Selection List Channel Bandwidth Scan Meaning Check any frequency that you want the BHS to scan for BHM transmissions. See Radio Frequency Scan Selection List on page 7-169. The channel size used by the radio for RF transmission. Note Selecting multiple channel bandwidths will increase registration and re-registration times. Page 7-150 Chapter 7: Configuration Configuring radio parameters Cyclic Prefix Scan The cyclic prefix for which BHM scanning is executed. Color code allows to force the BHS to register to only a specific BHM, even where the BHS can communicate with multiple BHMs. For registration to occur, the color code of the BHS and the BHM must match. Specify a value from 0 to 254. The color codes can be disabled, with the exception of the first color code. BHM and BHS have a configurable option used to prevent packet loss in the uplink due to bursting IP traffic. This is designed for IP burst traffic particular to video surveillance applications. Refer Table 145 PTP 450i BHM Radio page attributes 5 GHz on page 7-145 Color Code Large VC data Q Transmit Power External Gain Receive Quality Debug Page 7-151 Chapter 7: Configuration Configuring radio parameters PMP 450b Series - configuring radio Radio page PMP 450b SM 5 GHz The Radio page of PMP 450b SM is explained in Table 147. Table 147 PMP 450b SM Radio attributes 5 GHz Page 7-152 Chapter 7: Configuration Configuring radio parameters Page 7-153 Chapter 7: Configuration Attribute Custom Radio Frequency Scan Selection List Channel Bandwidth Scan Configuring radio parameters Meaning Check the frequencies that SM has to scan for AP transmissions. See Radio Frequency Scan Selection List on page 7-169. The channel size used by the radio for RF transmission. Note Selecting multiple channel bandwidths will increase registration and re-registration times. Cyclic Prefix Scan The cyclic prefix for which AP scanning is executed. AP Selection Method Operators may configure the method by which a scanning SM selects an AP. Color Code 1 By default, AP Selection Method is set to Optimize for Throughput, which has been the mode of operation in releases prior to 12.0.3.1. Power Level: AP selection based solely on power level Note For operation with a PMP 450m AP, select the Power Level option or Optimize for Throughput: AP selection based on throughput optimization the selection decision is based on power level (which affects the modulation state), channel bandwidth (which affects throughput) and number of SM registrations to the AP (which affects system contention performance). Color code allows you to force the SM to register to only a specific AP, even where the SM can communicate with multiple APs. For registration to occur, the color code of the SM and the AP must match. Specify a value from 0 to 254. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). SMs may be configured with up to 20 color codes. These color codes can be tagged as Primary, Secondary, or Tertiary, or Disable. When the SM is scanning for APs, it will first attempt to register to an AP that matches one of the SMs primary color codes. Failing that, the SM will continue scanning and attempt to register to an AP that matches one of the SMs secondary color codes. Failing that, the SM will continue scanning and attempt to register to an AP that matches one of the SMs tertiary color codes. This is all done in the scanning mode of the SM and will repeat until a registration has occurred. Page 7-154 Chapter 7: Configuration Configuring radio parameters Color codes in the same priority group are treated equally. For example, all APs matching one of the SMs primary color codes are analyzed equally. Likewise, this evaluation is done for the secondary and tertiary groups in order. The analysis for selecting an AP within a priority group is based on various inputs, including signal strength and number of SMs already registered to each AP. The first color code in the configuration is the pre-Release 9.5 color code. Thus, it is always a primary color code for legacy reasons. The color codes can be disabled, with the exception of the first color code. With this feature enabled on the AP and SM, operators may install and remotely configure SMs without having to configure matching color codes between the modules. When using the Installation Color Code feature, ensure that the SM is configured with the factory default Color Code configuration

(Color Code 1 is 0, Color Code 2-10 set to 0 and Disable). The status of the Installation Color Code can be viewed on the AP Eval web GUI page, and when the SM is registered using the Installation Color Code the message SM is registered via ICC Bridging Disabled! is displayed in red on every SM GUI page. The Installation Color Code parameter is configurable without a radio reboot for both the AP and SM. This value represents the antenna gain. For ODUs with integrated antenna, this is set at the correct value in the factory. For Connectorized ODUs with external antenna, the user must set this value to the overall antenna gain, including any RF cable loss between the ODU and the antenna. Installation Color Code External Gain Large VC data Queue SM and BH have a configurable option used to prevent packet loss in the Receive Quality Debug uplink due to bursting IP traffic. This is designed for IP burst traffic particular to video surveillance applications. To aid in link performance monitoring, the AP and SM now report the number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-QAM) and per channel (polarization). Note Due to CPU load, this will slightly degrade packet per second processing. Note The frequencies that a user can select are controlled by the country or a region and the Channel Bandwidth selected. There can be a case where a user adds a custom frequency

(from the Custom Frequencies page on page 7-172) and cannot see it in the pull down menu. Page 7-155 Chapter 7: Configuration Configuring radio parameters PMP/PTP 450 Series configuring radio Radio page - PMP 450 AP 5 GHz The Radio tab of the AP for 5 GHz is as shown in Table 148. Table 148 PMP 450 AP Radio attributes - 5 GHz Page 7-156 Chapter 7: Configuration Configuring radio parameters Attribute Radio Configuration, Frame Configuration, Power Control, Multicast Data Control and Advance tab PMP 430 SM Registration PMP 450/430 Legacy Mode Control Messages PMP 430 Interop Mode Receive Quality Debug Frame Alignment Legacy Mode Meaning See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132. See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132. Page 7-157 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 AP 3.65 GHz Table 149 PMP 450 AP Radio attributes - 3.65 GHz Meaning Attribute Radio Configuration, Frame Configuration, Power Control, Multicast Data Control and Advance tab See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132. Note When the Channel bandwidth is updated from 20 MHz to 30 MHz not more than 59 subscriber can be registered. Page 7-158 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 AP 3.5 GHz Table 150 PMP 450 AP Radio attributes - 3.5 GHz Meaning Attribute Radio Configuration, Frame Configuration, Power Control, Multicast Data Control and Advance tab See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132. Page 7-159 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 AP 2.4 GHz Table 151 PMP 450 AP Radio attributes - 2.4 GHz Meaning Attribute Radio Configuration, Frame Configuration, Power Control, Multicast Data Control and Advance tab See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132. Page 7-160 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 SM 5 GHz Table 152 PMP 450 SM Radio attributes 5 GHz Page 7-161 Chapter 7: Configuration Configuring radio parameters Attribute Custom Radio Frequency Scan Selection List See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132. Meaning Check the frequencies that SM has to scan for AP transmissions. See Radio Frequency Scan Selection List on page 7-169. Page 7-162 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 SM 3.65 GHz Table 153 PMP 450 SM Radio attributes 3.65 GHz Attribute Custom Radio Frequency Scan Selection List See Table 142 PMP 450i AP Radio attributes - 5 GHz on page 7-132. Meaning Check the frequencies that SM has to scan for AP transmissions. See Radio Frequency Scan Selection List on page 7-169. Page 7-163

 

 

333333333 CONFIGURATION GUIDE PMP/PTP 450 Series System Release 16.2 Covers:

PMP 450 AP / PMP 450 SM / PTP 450 / PMP 450d PMP 450i / PTP 450i PMP 450b / PTP 450b PMP 450m Accuracy While reasonable efforts have been made to assure the accuracy of this document, Cambium Networks assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein. Cambium reserves the right to make changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Cambium does not assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey license under its patent rights or the rights of others. It is possible that this publication may contain references to, or information about Cambium products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that Cambium intends to announce such Cambium products, programming, or services in your country. Copyrights This document, Cambium products, and 3rd Party software products described in this document may include or describe copyrighted Cambium and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Cambium, its licensors, and other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any copyrighted material of Cambium, its licensors, or the 3rd Party software supplied material contained in the Cambium products described in this document may not be copied, reproduced, reverse engineered, distributed, merged or modified in any manner without the express written permission of Cambium. Furthermore, the purchase of Cambium products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Cambium or other 3rd Party supplied software, except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a product. 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 Cambium. License Agreements The software described in this document is the property of Cambium and its licensors. It is furnished by express license agreement only and may be used only in accordance with the terms of such an agreement. High Risk Materials Cambium and its supplier(s) specifically disclaim any express or implied warranty of fitness for any high risk activities or uses of its products including, but not limited to, the operation of nuclear facilities, aircraft navigation or aircraft communication systems, air traffic control, life support, or weapons systems (High Risk Use). Any High Risk Use is unauthorized, is made at your own risk and you shall be responsible for any and all losses, damage or claims arising out of any High Risk Use. 2019 Cambium Networks Limited. All Rights Reserved. 2838_001v000 (November 2019) Contents Contents ................................................................................................................................................... i List of Figures ...................................................................................................................................... viii List of Tables ......................................................................................................................................... xi About This User Guide .......................................................................................................................... 1 Contacting Cambium Networks ................................................................................................. 1 Purpose ........................................................................................................................................... 2 Product notation conventions in document ............................................................................ 2 Cross references ........................................................................................................................... 3 Feedback ........................................................................................................................................ 3 Important regulatory information ..................................................................................................... 4 Application software .................................................................................................................... 4 USA specific information ............................................................................................................. 4 Canada specific information ....................................................................................................... 5 Renseignements specifiques au Canada .................................................................................. 6 EU Declaration of Conformity .................................................................................................... 7 Specific expertise and training for professional installers ..................................................... 7 Ethernet networking skills ........................................................................................................... 7 Lightning protection .................................................................................................................... 7 Training ........................................................................................................................................... 7 Problems and warranty ...................................................................................................................... 8 Reporting problems ..................................................................................................................... 8 Repair and service ........................................................................................................................ 8 Hardware warranty ....................................................................................................................... 8 Security advice ..................................................................................................................................... 9 Warnings, cautions, and notes ........................................................................................................ 10 Warnings ...................................................................................................................................... 10 Cautions ........................................................................................................................................ 10 Notes ............................................................................................................................................. 10 Caring for the environment ............................................................................................................. 11 In EU countries ............................................................................................................................ 11 In non-EU countries .................................................................................................................... 11 Chapter 1: Configuration .................................................................................................................... 1-2 Preparing for configuration ............................................................................................................ 1-3 Safety precautions ..................................................................................................................... 1-3 Regulatory compliance ............................................................................................................. 1-3 Connecting to the unit ..................................................................................................................... 1-4 Configuring the management PC ........................................................................................... 1-4 Connecting to the PC and powering up ................................................................................ 1-5 Page 1 Contents Using the web interface .................................................................................................................. 1-6 Logging into the web interface ............................................................................................... 1-6 Web GUI ...................................................................................................................................... 1-7 Using the menu options ............................................................................................................ 1-8 Quick link setup .............................................................................................................................. 1-13 Initiating Quick Start Wizard ................................................................................................. 1-13 Configuring time settings ....................................................................................................... 1-18 Powering the SM/BHS for test .............................................................................................. 1-19 Viewing the Session Status of the AP/BHM to determine test registration ................. 1-20 Configuring IP and Ethernet interfaces ...................................................................................... 1-23 Configuring the IP interface ................................................................................................... 1-24 Auxiliary port ............................................................................................................................ 1-27 NAT, DHCP Server, DHCP Client and DMZ ......................................................................... 1-28 DHCP BHS .............................................................................................................................. 1-44 Reconnecting to the management PC ................................................................................. 1-45 VLAN configuration for PMP ...................................................................................................... 1-45 VLAN configuration for PTP ..................................................................................................... 1-56 PPPoE page of SM ................................................................................................................... 1-59 IP4 and IPv6 .............................................................................................................................. 1-62 Upgrading the software version and using CNUT .................................................................... 1-67 Checking the installed software version .............................................................................. 1-67 Upgrading to a new software version .................................................................................. 1-67 General configuration .................................................................................................................... 1-71 PMP 450m and PMP/PTP 450i Series ................................................................................. 1-71 PMP/PTP 450 Series ............................................................................................................... 1-95 Configuring Unit Settings page .................................................................................................... 1-99 Setting up time and date ............................................................................................................ 1-103 Time page of 450 Platform Family - AP/BHM ................................................................. 1-103 Configuring synchronization ...................................................................................................... 1-105 Sync Input ............................................................................................................................... 1-105 Free Run Before GPS Sync .................................................................................................. 1-107 Device Type ............................................................................................................................ 1-107 Verify GPS Message Checksum ........................................................................................... 1-107 Sync Aux Port Config ............................................................................................................ 1-107 Aux Port Power to UGPS ...................................................................................................... 1-108 Configuring security ..................................................................................................................... 1-109 Managing module access by password ............................................................................. 1-110 Isolating from the internet APs/BHMs ............................................................................ 1-113 Encrypting radio transmissions ........................................................................................... 1-113 Requiring SM Authentication ............................................................................................... 1-114 Filtering protocols and ports ............................................................................................... 1-115 Encrypting downlink broadcasts ........................................................................................ 1-118 Isolating SMs ........................................................................................................................... 1-118 Page ii Contents Filtering management through Ethernet........................................................................... 1-119 Allowing management only from specified IP addresses .............................................. 1-119 Restricting radio Telnet access over the RF interface .................................................... 1-119 Configuring SNMP Access ................................................................................................... 1-123 Configuring Security ............................................................................................................. 1-125 Configuring 802.1X authentication ............................................................................................ 1-143 Configuring radio parameters .................................................................................................... 1-145 PMP 450m Series configuring radio ................................................................................ 1-146 PMP/PTP 450i Series configuring radio ......................................................................... 1-154 PMP/PTP 450b Series - configuring radio ........................................................................ 1-180 PMP/PTP 450 Series configuring radio .......................................................................... 1-185 Custom Frequencies page ................................................................................................... 1-204 DFS for 5 GHz Radios ........................................................................................................... 1-207 MIMO-A mode of operation.................................................................................................. 1-213 Improved PPS performance of 450 Platform Family .......................................................... 1-216 Setting up SNMP agent ............................................................................................................... 1-218 Configuring SM/BHSs IP over-the-air access .................................................................. 1-219 Configuring SNMP ................................................................................................................. 1-221 Configuring syslog........................................................................................................................ 1-227 Syslog event logging ............................................................................................................ 1-227 Configuring system logging ................................................................................................ 1-227 Configuring remote access ......................................................................................................... 1-232 Accessing SM/BHS over-the-air by Web Proxy ............................................................... 1-232 Monitoring the Link ...................................................................................................................... 1-233 Link monitoring procedure .................................................................................................. 1-233 Exporting Session Status page of AP/BHM ...................................................................... 1-235 Configuring quality of service .................................................................................................... 1-236 Maximum Information Rate (MIR) Parameters ................................................................. 1-236 Token Bucket Algorithm ...................................................................................................... 1-236 MIR Data Entry Checking ..................................................................................................... 1-237 Committed Information Rate (CIR) .................................................................................... 1-237 Bandwidth from the SM Perspective ................................................................................. 1-238 Interaction of Burst Allocation and Sustained Data Rate Settings ............................... 1-238 SM Prioritization ..................................................................................................................... 1-238 Weighted Fair Queuing (WFQ) ........................................................................................... 1-241 Proportional Scheduler ......................................................................................................... 1-244 High-priority Bandwidth Traffic .......................................................................................... 1-244 Traffic Scheduling .................................................................................................................. 1-246 Setting the Configuration Source ....................................................................................... 1-247 Configuring Quality of Service (QoS) ................................................................................ 1-250 Installation Color Code ................................................................................................................ 1-261 Zero Touch Configuration Using DHCP Option 66 ................................................................ 1-262 Configuration Steps .............................................................................................................. 1-262 Page iii Contents Troubleshooting ..................................................................................................................... 1-267 Configuring Radio via config file ............................................................................................... 1-268 Import and Export of config file ......................................................................................... 1-268 Configuring cnMaestroTM Connectivity ..................................................................................... 1-270 Configuring a RADIUS server ..................................................................................................... 1-275 Understanding RADIUS for PMP 450 Platform Family ................................................... 1-275 Choosing Authentication Mode and Configuring for Authentication Servers - AP ... 1-276 SM Authentication Mode Require RADIUS or Follow AP ............................................ 1-280 Handling Certificates ............................................................................................................. 1-285 Configuring RADIUS servers for SM authentication ........................................................ 1-286 Assigning SM management IP addressing via RADIUS .................................................. 1-288 Configuring RADIUS server for SM configuration ........................................................... 1-288 Configuring RADIUS server for SM configuration using Zero Touch feature ............. 1-291 Using RADIUS for centralized AP and SM user name and password management .. 1-292 RADIUS Device Data Accounting ....................................................................................... 1-297 RADIUS Device Re-authentication ..................................................................................... 1-300 RADIUS Change of Authorization and Disconnect Message ......................................... 1-302 Microsoft RADIUS support ................................................................................................... 1-304 Cisco ACS RADIUS Server Support .................................................................................... 1-308 Configuring VSA .................................................................................................................... 1-311 Configuring Ping Watchdog ....................................................................................................... 1-315 Chapter 2: Tools .............................................................................................................................. 2-316 Using Spectrum Analyzer tool ................................................................................................... 2-317 Mapping RF Neighbor Frequencies .................................................................................... 2-317 Spectrum Analyzer tool ........................................................................................................ 2-318 Remote Spectrum Analyzer tool ........................................................................................ 2-328 Using the Alignment Tool ........................................................................................................... 2-331 Aiming page and Diagnostic LED SM/BHS .................................................................... 2-332 Alignment Tone ...................................................................................................................... 2-336 Using the Link Capacity Test tool .............................................................................................. 2-338 Performing Link Test ............................................................................................................. 2-338 Performing Extrapolated Link Test .................................................................................... 2-342 Link Capacity Test page of AP ............................................................................................ 2-343 Link Capacity Test page of BHM/BHS/SM ........................................................................ 2-346 Using AP Evaluation tool ............................................................................................................. 2-347 AP Evaluation page ............................................................................................................... 2-347 Using BHM Evaluation tool ......................................................................................................... 2-352 BHM Evaluation page of BHS .............................................................................................. 2-352 Using the OFDM Frame Calculator tool ................................................................................... 2-356 Using the Subscriber Configuration tool .................................................................................. 2-360 Using the Link Status tool ........................................................................................................... 2-361 Link Status AP/BHM ........................................................................................................... 2-362 Link Status SM/BHS ........................................................................................................... 2-365 Page iv Contents Using BER Results tool ................................................................................................................ 2-369 Using the Sessions tool ................................................................................................................ 2-370 Using the Ping Test tool .............................................................................................................. 2-371 Chapter 3: Operation ......................................................................................................................... 3-1 System information .......................................................................................................................... 3-2 Viewing General Status ............................................................................................................ 3-2 Viewing Session Status ........................................................................................................... 3-24 Viewing Remote Subscribers ................................................................................................ 3-35 Interpreting messages in the Event Log ............................................................................. 3-35 Viewing the Network Interface ............................................................................................. 3-38 Viewing the Layer 2 Neighbors ............................................................................................. 3-38 System statistics ............................................................................................................................. 3-39 Viewing the Scheduler statistics ........................................................................................... 3-39 Viewing list of Registration Failures statistics .................................................................... 3-41 Interpreting Bridging Table statistics .................................................................................. 3-43 Interpreting Translation Table statistics .............................................................................. 3-43 Interpreting Ethernet statistics ............................................................................................. 3-44 Interpreting RF Control Block statistics .............................................................................. 3-47 Interpreting Sounding statistics for AP ............................................................................... 3-49 Interpreting VLAN statistics .................................................................................................. 3-51 Interpreting Data Channels statistics ................................................................................... 3-52 Interpreting Proportional Scheduler .................................................................................... 3-55 Interpreting MIR/Burst statistics ........................................................................................... 3-55 Interpreting Throughput statistics ........................................................................................ 3-58 Interpreting Overload statistics ............................................................................................ 3-61 Interpreting DHCP Relay statistics ....................................................................................... 3-63 Interpreting Filter statistics .................................................................................................... 3-65 Viewing ARP statistics ............................................................................................................ 3-66 Viewing NAT statistics ............................................................................................................ 3-66 Viewing NAT DHCP Statistics ............................................................................................... 3-68 Interpreting Sync Status statistics ........................................................................................ 3-69 Interpreting PPPoE Statistics for Customer Activities ...................................................... 3-70 Interpreting Bridge Control Block statistics ....................................................................... 3-72 Interpreting Pass Through Statistics .................................................................................... 3-75 Interpreting SNMPv3 Statistics ............................................................................................. 3-76 Interpreting syslog statistics ................................................................................................. 3-78 Interpreting Frame Utilization statistics .............................................................................. 3-79 Interpreting Spatial Utilization statistics ............................................................................. 3-85 Radio Recovery ............................................................................................................................... 3-89 Radio Recovery Console PMP/PTP 450i/450b and PMP 450m ................................... 3-89 Default Mode (or Default/Override Plug) - PMP/PTP 450 Series .................................. 3-91 Chapter 4: Reference information ................................................................................................... 4-1 Equipment specifications ................................................................................................................ 4-2 Page v Contents Specifications for 5 GHz PMP 450m Series - AP ................................................................. 4-2 Specifications for 3 GHz PMP 450m Series - AP ................................................................. 4-6 Specifications for PMP 450i Series - AP .............................................................................. 4-10 Specifications for PMP 450i Series - SM .............................................................................. 4-17 Specifications for PTP 450i Series - BH ............................................................................... 4-23 Specifications for PMP/PTP 450b Mid-Gain Series - SM .................................................. 4-28 Specifications for PMP/PTP 450b High Gain Series - SM................................................. 4-33 Specifications for PMP 450 Series - AP ............................................................................... 4-38 Specifications for PMP 450 Series - SM ............................................................................... 4-43 Specifications for PTP 450 Series - BH................................................................................ 4-49 PSU specifications ................................................................................................................... 4-54 Data network specifications ......................................................................................................... 4-56 Ethernet interface .................................................................................................................... 4-56 Wireless specifications .................................................................................................................. 4-57 General wireless specifications ............................................................................................. 4-57 Link Range and Throughput .................................................................................................. 4-58 Country specific radio regulations .............................................................................................. 4-59 Type approvals ......................................................................................................................... 4-59 DFS for 2.4 and 5 GHz Radios ............................................................................................... 4-61 Equipment Disposal ....................................................................................................................... 4-63 Waste (Disposal) of Electronic and Electric Equipment .................................................. 4-63 Country specific band range maximum transmit power ......................................................... 4-64 Maximum transmit power 900 MHz band ........................................................................... 4-64 Maximum transmit power 2.4 GHz band ............................................................................. 4-65 Maximum transmit power 3 GHz band ................................................................................ 4-66 Maximum transmit power 4.9 GHz band ............................................................................. 4-67 Maximum transmit power 5.1 GHz band .............................................................................. 4-70 Maximum transmit power 5.2 GHz band ............................................................................. 4-73 Maximum transmit power 5.4 GHz band ............................................................................. 4-78 Maximum transmit power 5.8 GHz band ............................................................................. 4-83 Country specific frequency range ............................................................................................... 4-88 Frequency range 900 MHz band .......................................................................................... 4-88 Frequency range 2.4 GHz band ............................................................................................ 4-89 Frequency range 3.5 GHz band ............................................................................................ 4-89 Frequency range 3.65 GHz band .......................................................................................... 4-90 Frequency range 4.9 GHz band ............................................................................................ 4-91 Frequency range 5.1 GHz band ............................................................................................. 4-93 Frequency range 5.2 GHz band ............................................................................................ 4-96 Frequency range 5.4 GHz band ............................................................................................ 4-99 Frequency range 5.8 GHz band .......................................................................................... 4-105 FCC specific information ............................................................................................................. 4-111 FCC compliance testing ....................................................................................................... 4-111 FCC IDs .................................................................................................................................... 4-111 Page vi Contents FCC approved antenna list .................................................................................................. 4-120 Innovation Science and Economic Development Canada (ISEDC) specific information 4-124 900 MHz ISEDC notification ................................................................................................ 4-124 4.9 GHz ISEDC notification .................................................................................................. 4-124 Utilisation de la bande 4.9 GHz FCC et ISEDC ................................................................. 4-124 5.2 GHz and 5.4 GHz ISEDC notification ........................................................................... 4-124 Utilisation de la bande 5.2 and 5.4 GHz ISEDC ................................................................ 4-124 ISEDC notification 5.8 GHz .................................................................................................. 4-125 Utilisation de la bande 5.8 GHz ISEDC ............................................................................... 4-125 ISEDC certification numbers ................................................................................................ 4-125 Canada approved antenna list ............................................................................................ 4-127 Chapter 5: Troubleshooting .............................................................................................................. 5-1 General troubleshooting procedure .............................................................................................. 5-2 General planning for troubleshooting .................................................................................... 5-2 General fault isolation process ................................................................................................ 5-3 Secondary Steps ........................................................................................................................ 5-4 Troubleshooting procedures .......................................................................................................... 5-5 Module has lost or does not establish connectivity ............................................................ 5-5 NAT/DHCP-configured SM has lost or does not establish connectivity ......................... 5-7 SM Does Not Register to an AP .............................................................................................. 5-8 Module has lost or does not gain sync .................................................................................. 5-9 Module does not establish Ethernet connectivity ............................................................. 5-10 CMM4 does not pass proper GPS sync to connected modules ...................................... 5-11 Module Software Cannot be Upgraded ............................................................................... 5-12 Module Functions Properly, Except Web Interface Became Inaccessible .................... 5-12 Power-up troubleshooting ............................................................................................................ 5-13 Registration and connectivity troubleshooting ........................................................................ 5-14 SM/BMS Registration .............................................................................................................. 5-14 Logs .................................................................................................................................................. 5-15 Persistent Logging .................................................................................................................. 5-15 A.1 Specifications ................................................................................................................................. 1 A.2 450m overload .............................................................................................................................. 1 Page vii List of Figures List of Figures Figure 1 Disarm Installation page (top and bottom of page shown) .......................................... 1-13 Figure 2 Regional Settings tab of AP/BHM ..................................................................................... 1-14 Figure 3 Radio Carrier Frequency tab of AP/BHM ......................................................................... 1-14 Figure 4 Synchronization tab of AP/BHM ........................................................................................ 1-15 Figure 5 LAN IP Address tab of the AP/BHM ................................................................................. 1-16 Figure 6 Review and Save Configuration tab of the AP/BHM ..................................................... 1-17 Figure 7 Time tab of the AP/BHM ..................................................................................................... 1-18 Figure 8 Time and date entry formats .............................................................................................. 1-19 Figure 9 Session Status tab of AP ..................................................................................................... 1-21 Figure 10 NAT disabled implementation .......................................................................................... 1-29 Figure 11 NAT with DHCP client and DHCP server implementation ............................................ 1-30 Figure 12 NAT with DHCP client implementation ........................................................................... 1-30 Figure 13 NAT with DHCP server implementation .......................................................................... 1-31 Figure 14 NAT without DHCP implementation ................................................................................ 1-31 Figure 15 General page attributes - PMP 450 AP ........................................................................... 1-95 Figure 16 General page attributes - PMP 450 SM ........................................................................... 1-96 Figure 17 General page attributes - PTP 450 BHM ......................................................................... 1-97 Figure 18 General page attributes - PTP 450 BHS .......................................................................... 1-98 Figure 19 Sync Setting configuration .............................................................................................. 1-105 Figure 20 AP Evaluation Configuration parameter of Security tab for PMP ........................... 1-112 Figure 21 BHM Evaluation Configuration parameter of Security tab for PTP .......................... 1-112 Figure 22 RF Telnet Access Restrictions (orange) and Flow through (green) ....................... 1-121 Figure 23 RF Telnet Access Restriction (orange) and Potential Security Hole (green) ........ 1-121 Figure 24 PMP 450i AP Radio attributes - 3 GHz ......................................................................... 1-154 Figure 25 PMP 450i SM Radio attributes - 3 GHz ......................................................................... 1-161 Figure 26 Multicast VC statistics ...................................................................................................... 1-202 Figure 27 Multicast scheduler statistics .......................................................................................... 1-203 Figure 28 AP DFS Status .................................................................................................................. 1-207 Figure 29 Frame structure ............................................................................................................... 1-208 Figure 30 AP Session Status page .................................................................................................. 1-232 Figure 31 AP Remote Subscribers page ......................................................................................... 1-232 Figure 32 Session Status page ......................................................................................................... 1-233 Figure 33 Exporting Session Status page of PMP 450m AP ...................................................... 1-235 Figure 34 Uplink and downlink rate caps adjusted to apply aggregate cap ........................... 1-237 Figure 35 Uplink and downlink rate cap adjustment example ................................................... 1-237 Figure 36 SM Prioritization on SM ................................................................................................... 1-239 Figure 37 SM Prioritization on AP .................................................................................................... 1-239 Figure 38 Weighted Fair Queuing Configuration ......................................................................... 1-241 Figure 39 WFQ with SM Prioritization ............................................................................................ 1-243 Figure 40 Scheduler Settings on AP ............................................................................................... 1-244 Page viii List of Figures Figure 41 Proportional Scheduler Settings on AP......................................................................... 1-244 Figure 42 Installation Color Code of AP ......................................................................................... 1-261 Figure 43 Configuration File upload and download page .......................................................... 1-268 Figure 44 Software Upgrade from cnMaestro ............................................................................ 1-271 Figure 45 DNS Test for cnMaestro connectivity ........................................................................ 1-272 Figure 46 Device Agent Logs ........................................................................................................... 1-273 Figure 47 Example cnMaestro screenshot .................................................................................. 1-273 Figure 48 SM Certificate Management ........................................................................................... 1-286 Figure 49 User Authentication and Access Tracking tab of the SM ......................................... 1-296 Figure 50 RADIUS accounting messages configuration ............................................................. 1-300 Figure 51 Device re-authentication configuration ......................................................................... 1-301 Figure 52 RADIUS CoA configuration for AP ................................................................................ 1-302 Figure 53 EAPPEAP settings ............................................................................................................ 1-304 Figure 54 Importing certificate in NPS ........................................................................................... 1-305 Figure 55 Selecting MD5 from NPS console .................................................................................. 1-306 Figure 56 User configuration ............................................................................................................ 1-306 Figure 57 RADIUS VSA configuration ............................................................................................. 1-307 Figure 58 Adding RADIUS client ..................................................................................................... 1-308 Figure 59 Creating users ................................................................................................................... 1-308 Figure 60 Creating RADIUS instance .............................................................................................. 1-309 Figure 61 RADIUS protocols ............................................................................................................. 1-309 Figure 62 Service selection ............................................................................................................... 1-310 Figure 63 Adding Trusted CA .......................................................................................................... 1-310 Figure 64 Installing Server Certificate ............................................................................................ 1-310 Figure 65 Monitoring logs ................................................................................................................. 1-311 Figure 66 VSA list ............................................................................................................................... 1-312 Figure 67 Spectrum analysis - Results ............................................................................................ 2-318 Figure 68 Spectrum Analyzer page result PMP 450 SM .......................................................... 2-327 Figure 69 Alignment Tool tab of SM Receive Power Level > -70 dBm ................................. 2-331 Figure 70 Alignment Tool tab of SM Receive Power Level between -70 to -80 dBm ....... 2-331 Figure 71 Alignment Tool tab of SM Receive Power Level < -80 dBm .................................. 2-331 Figure 72 PMP/PTP 450i Series link alignment tone .................................................................... 2-336 Figure 73 Link Capacity Test PMP 450m Series AP ............................................................. 2-339 Figure 74 Link Test with Multiple LUIDs ......................................................................................... 2-340 Figure 75 Link Test without Bridging .............................................................................................. 2-340 Figure 76 Link Test with Bridging and MIR .................................................................................... 2-340 Figure 77 Link Test without Bridging (1518-byte packet length) ............................................... 2-341 Figure 78 Extrapolated Link Test results ....................................................................................... 2-342 Figure 79 SM Configuration page of AP ......................................................................................... 2-360 Figure 80 BER Results tab of the SM .............................................................................................. 2-369 Figure 81 Sessions tab of the AP ...................................................................................................... 2-370 Figure 82 Ping Test tab of the AP ................................................................................................... 2-371 Figure 83 Remote Subscribers page of AP ...................................................................................... 3-35 Page ix List of Figures Figure 84 Event log data ..................................................................................................................... 3-36 Figure 85 Network Interface tab of the AP ...................................................................................... 3-38 Figure 86 Network Interface tab of the SM ..................................................................................... 3-38 Figure 87 Layer 2 Neighbors page .................................................................................................... 3-38 Figure 88 Bridging Table page .......................................................................................................... 3-43 Figure 89 Translation Table page of SM ........................................................................................... 3-44 Figure 90 ARP page of the SM .......................................................................................................... 3-66 Figure 91 Recovery Options page ..................................................................................................... 3-90 Figure 92 SM Logs ................................................................................................................................ 5-15 Figure 93 SM Session log .................................................................................................................... 5-15 Figure 94 SM Authentication log ....................................................................................................... 5-15 Figure 95 SM Authorization log ......................................................................................................... 5-16 Page x List of Tables List of Tables Table 1 Menu options and web pages ................................................................................................. 1-8 Table 2 Session Status Attributes AP ............................................................................................ 1-22 Table 3 IP interface attributes ............................................................................................................ 1-25 Table 4 SM/BHS private IP and LUID ................................................................................................ 1-26 Table 5 Aux port attributes ................................................................................................................. 1-27 Table 6 IP attributes - SM with NAT disabled.................................................................................. 1-33 Table 7 IP attributes - SM with NAT enabled .................................................................................. 1-35 Table 8 NAT attributes - SM with NAT disabled ............................................................................. 1-36 Table 9 NAT attributes - SM with NAT enabled .............................................................................. 1-39 Table 10 SM DNS Options with NAT Enabled .................................................................................. 1-44 Table 11 NAT Port Mapping attributes - SM ..................................................................................... 1-44 Table 12 VLAN Remarking Example .................................................................................................. 1-46 Table 13 AP/BHM VLAN tab attributes ............................................................................................. 1-48 Table 14 Q-in-Q Ethernet frame ......................................................................................................... 1-49 Table 15 SM VLAN attributes .............................................................................................................. 1-51 Table 16 SM VLAN Membership attributes ....................................................................................... 1-55 Table 17 BHM VLAN page attributes ................................................................................................. 1-56 Table 18 BHS VLAN page attributes .................................................................................................. 1-58 Table 19 SM PPPoE attributes............................................................................................................. 1-60 Table 20 DiffServ attributes AP/BHM ............................................................................................ 1-62 Table 21 Packet Filter Configuration attributes ............................................................................... 1-65 Table 22 General page attributes PMP 450i AP ........................................................................... 1-71 Table 23 General page attributes PMP 450m AP ......................................................................... 1-77 Table 24 General page attributes PMP 450i SM .......................................................................... 1-79 Table 25 General page attributes PTP 450i BHM ........................................................................ 1-82 Table 26 General page attributes PTP 450i BHS ......................................................................... 1-84 Table 27 General page attributes PMP 450b SM ......................................................................... 1-87 Table 28 General page attributes PMP 450b BHM ...................................................................... 1-90 Table 29 General page attributes PMP 450b BHS ....................................................................... 1-92 Table 30 Unit Settings attributes 450 Platform Family AP/BHM ........................................... 1-100 Table 31 SM Unit Settings attributes ............................................................................................... 1-102 Table 32 450 Platform Family - AP/BHM Time attributes ......................................................... 1-103 Table 33 Add User page of account page - AP/ SM/BH ............................................................. 1-110 Table 34 Delete User page - 450 Platform Family - AP/ SM/BH .............................................. 1-111 Table 35 Change User Setting page - 450 Platform Family AP/ SM/BH ................................. 1-111 Table 36 User page 450 Platform Family AP/SM/BH ................................................................ 1-112 Table 37 AP/BHM Protocol Filtering attributes ............................................................................ 1-115 Table 38 SM/BHS Protocol Filtering attributes ............................................................................. 1-117 Table 39 Port Configuration attributes AP/SM/BHM/BMS ...................................................... 1-118 Table 40 Security attributes 450 Platform Family AP ............................................................... 1-125 Page xi List of Tables Table 41 Security attributes 450 Platform Family BHM ............................................................. 1-131 Table 42 Security attributes 450 Platform Family SM ............................................................... 1-133 Table 43 Security attributes - 450 Platform Family BHS ............................................................ 1-140 Table 44 802.1X authentication attributes 450 Platform Family AP ....................................... 1-143 Table 45 802.1X authentication attributes 450 Platform Family SM ....................................... 1-144 Table 46 PMP 450m AP Radio attributes - 5 GHz ........................................................................ 1-146 Table 47 PMP 450m AP Radio attributes - 3 GHz ........................................................................ 1-151 Table 48 PMP 450i AP Radio attributes - 5 GHz .......................................................................... 1-156 Table 49 PMP 450i SM Radio attributes 5 GHz .......................................................................... 1-163 Table 50 PMP 450i AP Radio attributes - 900 MHz ..................................................................... 1-170 Table 51 PTP 450i BHM Radio page attributes 5 GHz .............................................................. 1-173 Table 52 PTP 450i BHS Radio attributes 5 GHz ......................................................................... 1-176 Table 53 PMP/PTP 450b Mid-Gain/High Gain SM Radio attributes 5 GHz ........................... 1-180 Table 54 PMP 450 AP Radio attributes - 5 GHz ........................................................................... 1-185 Table 55 PMP 450 AP Radio attributes - 3.65 GHz ...................................................................... 1-187 Table 56 PMP 450 AP Radio attributes - 3.5 GHz ........................................................................ 1-188 Table 57 PMP 450 AP Radio attributes - 2.4 GHz ........................................................................ 1-189 Table 58 PMP 450 SM Radio attributes 5 GHz ........................................................................... 1-190 Table 59 PMP 450 SM Radio attributes 3.65 GHz ..................................................................... 1-192 Table 60 PMP 450 SM Radio attributes 3.5 GHz ....................................................................... 1-193 Table 61 PMP 450 SM Radio attributes 2.4 GHz ........................................................................ 1-194 Table 62 PMP 450 SM Radio attributes 900 MHz ...................................................................... 1-196 Table 63 PTP 450 BHM Radio attributes 5 GHz .......................................................................... 1-198 Table 64 PTP 450 BHM Radio attributes 5 GHz ......................................................................... 1-199 Table 65 Example for mix of multicast and unicast traffic scenarios........................................ 1-202 Table 66 450 Platform Family AP/SM/BH Custom Frequencies page 5 GHz ...................... 1-204 Table 67 PMP/PTP 450 SM/BH Custom Frequencies page 3.65 GHz ................................... 1-205 Table 68 PMP/PTP 450 SM/BH Custom Frequencies page 3.5 GHz ..................................... 1-206 Table 69 Throughput penalty per modulation .............................................................................. 1-209 Table 70 Contention slot settings ................................................................................................... 1-209 Table 71 450 Platform Family Modulation levels........................................................................... 1-214 Table 72 Co-channel Interference per (CCI) MCS ......................................................................... 1-215 Table 73 Adjacent Channel Interference (ACI) per MCS ............................................................. 1-216 Table 74 LAN1 Network Interface Configuration tab of IP page attributes ............................. 1-219 Table 75 SNMP page attributes ....................................................................................................... 1-221 Table 76 Syslog parameters ............................................................................................................. 1-227 Table 77 Syslog Configuration attributes - AP .............................................................................. 1-228 Table 78 Syslog Configuration attributes - SM ............................................................................. 1-229 Table 79 Syslog Configuration attributes - BHS ........................................................................... 1-230 Table 80 Characteristics of traffic scheduling ............................................................................... 1-246 Table 81 Recommended combined settings for typical operations .......................................... 1-248 Table 82 Where feature values are obtained for an SM registered under an AP with Authentication Mode set to something other than "DISABLED" ........................................ 1-248 Page xii List of Tables Table 83 MIR, VLAN, HPC, and CIR Configuration Sources, Authentication Disabled ........... 1-248 Table 84 QoS page attributes - AP ................................................................................................. 1-250 Table 85 QoS page attributes - SM ................................................................................................. 1-255 Table 86 QoS page attributes - BHM .............................................................................................. 1-259 Table 87 QoS page attributes - BHS ............................................................................................... 1-260 Table 88 Configuring cnMaestro ...................................................................................................... 1-270 Table 89 Security tab attributes ...................................................................................................... 1-277 Table 90 SM Security tab attributes ............................................................................................... 1-281 Table 91 RADIUS Vendor Specific Attributes (VSAs) .................................................................. 1-289 Table 92 AP User Authentication and Access Tracking attributes ........................................... 1-294 Table 93 SM User Authentication and Access Tracking attributes ........................................... 1-296 Table 94 Device data accounting RADIUS attributes .................................................................. 1-297 Table 95 Ping Watchdog attributes ................................................................................................ 1-315 Table 96 Spectrum Analyzer page attributes - AP ...................................................................... 2-320 Table 97 Spectrum Analyzer page attributes - SM ...................................................................... 2-322 Table 98 Spectrum Analyzer page attributes - BHM ................................................................... 2-324 Table 99 Spectrum Analyzer page attributes - BHS .................................................................... 2-326 Table 100 Remote Spectrum Analyzer attributes - AP................................................................ 2-329 Table 101 Remote Spectrum Analyzer attributes - BHM .............................................................. 2-330 Table 102 Aiming page attributes SM .......................................................................................... 2-333 Table 103 Aiming page attributes - BHS ........................................................................................ 2-335 Table 104 Alignment Tool Headsets and Alignment tone adapter third party product details . 2-

336 Table 105 Link Capacity Test page attributes 450m AP .......................................................... 2-343 Table 106 Link Capacity Test page attributes BHM/BHS ......................................................... 2-346 Table 107 AP Evaluation tab attributes - AP ................................................................................. 2-347 Table 108 BHM Evaluation tab attributes - BHS ............................................................................ 2-352 Table 109 OFDM Frame Calculator page attributes ..................................................................... 2-357 Table 110 OFDM Calculated Frame Results attributes ................................................................. 2-358 Table 111 Color code versus uplink/downlink rate column .......................................................... 2-361 Table 112 Link Status page attributes AP/BHM .......................................................................... 2-362 Table 113 Link Status page attributes SM/BHS ........................................................................... 2-365 Table 114 General Status page attributes PMP 450m AP ............................................................. 3-3 Table 115 General Status page attributes PMP 450 AP ................................................................. 3-8 Table 116 General Status page attributes PMP 450i AP .............................................................. 3-10 Table 117 General Status page attributes - SM ................................................................................ 3-13 Table 118 General Status page attributes - BHM ............................................................................. 3-18 Table 119 General Status page attributes - BHS .............................................................................. 3-21 Table 120 Device tab attributes ......................................................................................................... 3-24 Table 121 Session tab attributes ......................................................................................................... 3-26 Table 122 Power tab attributes ........................................................................................................... 3-27 Table 123 Configuration tab attributes ............................................................................................. 3-30 Table 124 Session Status > Configuration CIR configuration denotations ................................. 3-32 Page xiii List of Tables Table 125 Link Quality tab attributes ................................................................................................ 3-33 Table 126 Event Log messages for abnormal events ..................................................................... 3-37 Table 127 Event Log messages for normal events .......................................................................... 3-37 Table 128 Scheduler tab attributes .................................................................................................... 3-39 Table 129 SM Registration Failures page attributes - AP .............................................................. 3-41 Table 130 BHS Registration Failures page attributes - BHM ........................................................ 3-42 Table 131 Flags status ........................................................................................................................... 3-42 Table 132 Ethernet tab attributes ...................................................................................................... 3-44 Table 133 Radio (Statistics) page attributes RF Control Block ................................................. 3-47 Table 134 Sounding Statistics - 450m AP page attributes ........................................................... 3-49 Table 135 VLAN page attributes ........................................................................................................ 3-51 Table 136 Data Channel page attributes ........................................................................................... 3-52 Table 137 MIR/Burst page attributes for AP .................................................................................... 3-55 Table 138 MIR/Burst page attributes for AP .................................................................................... 3-56 Table 139 MIR/Burst page attributes for SM .................................................................................... 3-57 Table 140 RF overload Configuration attributes AP/BHM ......................................................... 3-58 Table 141 Overload page attributes AP/SM/BHM/BHS .............................................................. 3-61 Table 142 DHCP Relay page attributes AP/SM ............................................................................ 3-64 Table 143 Filter page attributes - SM ................................................................................................ 3-65 Table 144 NAT page attributes - SM ................................................................................................. 3-67 Table 145 NAT DHCP Statistics page attributes - SM .................................................................... 3-68 Table 146 Sync Status page attributes - AP .................................................................................... 3-69 Table 147 PPPoE Statistics page attributes - SM ............................................................................ 3-70 Table 148 Bridge Control Block page attributes AP/SM/BHM/BHS ........................................ 3-72 Table 149 Pass Through Statistics page attributes AP ............................................................... 3-75 Table 150 SNMPv3 Statistics page attributes AP ......................................................................... 3-76 Table 151 Syslog statistics page attributes AP/SM/BH ............................................................... 3-78 Table 152 Frame utilization statistics for 450m .............................................................................. 3-79 Table 153 Frame utilization statistics for 450, 450i ........................................................................ 3-84 Table 154 Spatial Utilization statistics ............................................................................................... 3-85 Table 155 Recovery Options attributes ............................................................................................. 3-90 Table 156 5 GHz PMP 450m Series - AP specifications ................................................................... 4-2 Table 157 3GHz PMP 450m Series - AP specifications ................................................................... 4-6 Table 158 PMP 450i Series - AP specifications ................................................................................ 4-10 Table 159 PMP 450i Series - SM specifications ............................................................................... 4-17 Table 160 PTP 450i Series - BH specifications ................................................................................ 4-23 Table 161 PMP/PTP 450b Mid-Gain Series - SM specifications ..................................................... 4-28 Table 162 PMP/PTP 450b High Gain Series - SM specifications .................................................. 4-33 Table 163 PMP 450 Series - AP specifications ................................................................................. 4-38 Table 164 PMP 450 Series - SM specifications ................................................................................ 4-43 Table 165 PTP 450 Series - BH specifications ................................................................................. 4-49 Table 166 PMP/PTP 450i AC power Injector specifications ......................................................... 4-54 Table 167 PMP/PTP 450 power supply specifications (part number: N000900L001A) ........ 4-55 Page xiv List of Tables Table 168 450m/450i Series Main and Aux Ethernet bridging specifications .......................... 4-56 Table 169 450 Series Ethernet bridging specifications ................................................................. 4-56 Table 170 450 Platform Family - wireless specifications ............................................................... 4-57 Table 171 Radio certifications ............................................................................................................. 4-59 Table 172 Country & Bands DFS setting ........................................................................................... 4-61 Table 173 Frequency range and Maximum transmit power 900 MHz band PMP 450i Series . 4-

64 Table 174 Frequency range and Maximum transmit power 2.4GHz band PMP/PTP 450 Series

........................................................................................................................................................... 4-65 Table 175 Frequency range and Maximum transmit power 3 GHz band PMP/PTP 450 Series

........................................................................................................................................................... 4-66 Table 176 Default combined transmit power per country 4.9 GHz band PMP/PTP 450i Series

........................................................................................................................................................... 4-67 Table 177 Default combined transmit power per country 4.9 GHz band PMP 450b Series 4-69 Table 178 Default combined transmit power per country 4.9 GHz band PMP 450m Series 4-69 Table 179 Default combined transmit power per Country 5.1 GHz band PMP/PTP 450i Series

........................................................................................................................................................... 4-70 Table 180 Default combined transmit power per country 5.1 GHz band PMP 450b Mid Gain and High Gain .................................................................................................................................. 4-71 Table 181 Default combined transmit power per Country 5.1 GHz band PMP 450m Series . 4-72 Table 182 Default combined transmit power per country 5.2 GHz band PMP/PTP 450i Series

........................................................................................................................................................... 4-74 Table 183 Default combined transmit power per country 5.2 GHz band PMP 450b Mid-Gain and High Gain .................................................................................................................................. 4-75 Table 184 Default combined transmit power per Country 5.2 GHz band PMP 450m Series ... 4-

77 Table 185 Default combined transmit power per country 5.4 GHz band PMP 450m Series 4-78 Table 186 Default combined transmit power per country 5.4 GHz band PMP/PTP 450i Series

........................................................................................................................................................... 4-79 Table 187 Default combined transmit power per country 5.4 GHz band PMP 450b Mid-Gain and High Gain .................................................................................................................................. 4-80 Table 188 Default combined transmit power per country 5.4 GHz band PMP 450 Series ... 4-81 Table 189 Default combined transmit power per Country 5.8 GHz band PMP 450m Series ... 4-

83 Table 190 Default combined transmit power per country 5.8 GHz band PMP/PTP 450i Series

........................................................................................................................................................... 4-84 Table 191 Default combined transmit power per country 5.8 GHz band PMP 450b Mid-Gain and High Gain .................................................................................................................................. 4-85 Table 192 Default combined transmit power per country 5.8 GHz band PMP 450 Series ... 4-86 Table 193 Frequency range per country 900 MHz band ............................................................ 4-88 Table 194 Frequency range per country 2.4 GHz band PMP/PTP 450 Series ........................ 4-89 Table 195 Frequency range per country 3.5 GHz band PMP/PTP 450/450i Series .............. 4-89 Table 196 Frequency range per country 3.65 GHz band PMP/PTP 450/450i Series ........... 4-90 Table 197 Frequency range per country 4.9 GHz band PMP/PTP 450i Series ....................... 4-91 Table 198 Frequency range per country 4.9 GHz band PMP 450b Series .............................. 4-91 Table 199 Frequency range per country 4.9 GHz band PMP 450m Series ............................. 4-92 Page xv List of Tables Table 200 Frequency range per country 5.1 GHz band PMP/PTP 450i Series ...................... 4-93 Table 201 Frequency range per country 5.1 GHz band PMP 450b Mid-Gain Series .............. 4-94 Table 202 Frequency range per country 5.1 GHz band PMP 450b High Gain Series ............ 4-94 Table 203 Frequency range per country 5.1 GHz band PMP 450m Series ............................. 4-95 Table 204 Frequency range per country 5.2 GHz band PMP/PTP 450i Series ...................... 4-96 Table 205 Frequency range per country 5.2 GHz band PMP 450b Mid-Gain Series ............ 4-97 Table 206 Frequency range per country 5.2 GHz band PMP 450b High Gain Series ........... 4-97 Table 207 Frequency range per country 5.2 GHz band PMP 450m Series ............................. 4-98 Table 208 Frequency range per country 5.4 GHz band PMP/PTP 450i Series ...................... 4-99 Table 209 Frequency range per country 5.4 GHz band PMP 450b Mid-Gain Series .......... 4-100 Table 210 Frequency range per country 5.4 GHz band PMP 450b High Gain Series .......... 4-100 Table 211 Frequency range per country 5.4 GHz band PMP/PTP 450 Series ....................... 4-101 Table 212 Frequency range per country 5.4 GHz band PMP 450m Series ............................ 4-104 Table 213 Frequency range per country 5.8 GHz band PMP/PTP 450i Series ..................... 4-105 Table 214 Frequency range per country 5.8 GHz band PMP 450b Mid-GainSeries ............ 4-106 Table 215 Frequency range per country 5.8 GHz band PMP 450b High Gain Series .......... 4-106 Table 216 Frequency range per country 5.8 GHz band PMP/PTP 450 Series ...................... 4-106 Table 217 Frequency range per country 5.8 GHz band PMP 450m Series ............................ 4-110 Table 218 US FCC IDs ......................................................................................................................... 4-111 Table 219 USA approved antenna list 4.9 GHz .............................................................................. 4-120 Table 220 USA approved antenna list 5.1 and 5.2 GHz ................................................................ 4-121 Table 221 USA approved antenna list 5.4 GHz .............................................................................. 4-122 Table 222 USA approved antenna list 5.8 GHz ............................................................................. 4-123 Table 223 ISEDC Certification Numbers PMP 450i ................................................................... 4-125 Table 224 ISEDC Certification Numbers PMP 450m ................................................................. 4-126 Table 225 Canada approved antenna list 4.9 and 5.8 GHz ......................................................... 4-129 Table 226 Canada approved antenna list 5.2 and 5.4 GHz ......................................................... 4-130 Page xvi About This User Guide This guide describes configuration and operation of the Cambium point-to-point and point-to-

multipoint wireless Ethernet bridges. It covers PMP/PTP 450, 450i, 450b, 450d and PMP 450m platform Series. It is intended for use by the system designer, system installer and system administrator. For system configuration, tools and troubleshooting, refer to the following chapters:

Chapter 1: Configuration Chapter 2: :Tools Chapter 3: Operation Chapter 4: Reference information Chapter 5: Troubleshooting Contacting Cambium Networks Support website:

Main website:

Sales enquiries:

https://support.cambiumnetworks.com http://www.cambiumnetworks.com solutions@cambiumnetworks.com Support/Repair enquiries:

https://support.cambiumnetworks.com Telephone number list:

http://www.cambiumnetworks.com/contact Address:

Cambium Networks Limited, Linhay Business Park, Eastern Road, Ashburton, Devon, TQ13 7UP United Kingdom Page 1 Purpose Cambium Networks Point-to-Multi-Point (PMP)/Point-To-Point (PTP) 450 documents are intended to instruct and assist personnel in the operation, installation and maintenance of the Cambium PMP/PTP equipment and ancillary devices of 450 Platform Family. It is recommended that all personnel engaged in such activities be properly trained. Cambium disclaims all liability whatsoever, implied or express, for any risk of damage, loss or reduction in system performance arising directly or indirectly out of the failure of the customer, or anyone acting on the customer's behalf, to abide by the instructions, system parameters, or recommendations made in this document. Product notation conventions in document This document covers Cambium 450 Series, 450b series, 450i Series and 450m Series products. The following notation conventions are followed while referring to product series and product family:

Product notation Description 450 Platform Family Refers to the complete 450 Series family, which includes 450 Series, 450i Series, 450b Series and 450m Series 450 Series 450i Series 450b Series Refers to 450 Series devices in the following configurations:

-

PMP 450

-

AP [2.4, 3.5, 3.65, 5 GHz]

- Connectorized SM [900 MHz and 2.4, 3.5, 3.65, 5 GHz]

- Connectorized/ Integrated

-

-

PTP 450 BHM/ BHS [900 MHz and 3.5, 3.65, 5 GHz]

- Connectorized/ Integrated PMP 450d SM [5 GHz]

-

Refers to 450i Series devices in the following configurations:

-

PMP 450i

- AP [900 MHz and 3, 5 GHz]

-

- Connectorized/ Integrated SM [3 GHz and 5 GHz]

- Connectorized/ Integrated

-

PTP 450i BHM/ BHS [3 GHz and 5 GHz]

- Connectorized/ Integrated Refers to 450b Series devices in the following configurations:

-

PMP 450b Mid-Gain

-

SM [5 GHz]

-

Integrated

-

PMP/PTP 450b High Gain

-

SM [5 GHz] - Dish Page 2 Product notation Description 450m Series Refers to 450m Series device configuration:

-

-

PMP 450m AP 5 GHz Integrated PMP 450m AP 3 GHz Integrated

-

-

Cross references References to external publications are shown in italics. Other cross references, emphasized in blue text in electronic versions, are active links to the references. This document is divided into numbered chapters that are divided into sections. Sections are not numbered but are individually named at the top of each page, and are listed in the table of contents. Feedback We appreciate feedback from the users of our documents. This includes feedback on the structure, content, accuracy, or completeness of our documents. To provide feedback, visit our support website.https://support.cambiumnetworks.com. Caution This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

This device may not cause harmful interference, and This device must accept any interference received, including interference that may cause undesired operation Page 3 Important regulatory information The 450 Platform Family products are certified as an unlicensed device in frequency bands where it is not allowed to cause interference to licensed services (called primary users of the bands). Application software Download the latest 450 Platform Family software and install it in the Outdoor Units (ODUs) before deploying the equipment. Instructions for installing software are provided in Upgrading the software version and using CNUT on page 1-67. USA specific information The USA Federal Communications Commission (FCC) requires manufacturers to implement special features to prevent interference to weather radar systems that operate in the band 5600 MHz to 5650 MHz. These features must be implemented in all products able to operate outdoors in the band 5470 MHz to 5725 MHz. Manufacturers must ensure that such radio products cannot be configured to operate outside of FCC rules; specifically, it must not be possible to disable or modify the radar protection functions that have been demonstrated to the FCC. Cambium supplies variants of the 5 GHz 450, 450i, 450b, and 450m Series specifically for operation in the USA to comply with FCC requirements (KDB 905462 D02 UNII DFS Compliance Procedures New Rules v02). These variants are only allowed to operate with license keys that comply with FCC rules. To ensure compliance when using PMP 450 Series and PTP 450 Series, follow the recommendation in Avoidance of weather radars (USA only). External antennas When using a connectorized version of the product, the conducted transmit power may need to be reduced to ensure the regulatory limit on transmitter EIRP is not exceeded. The installer must have an understanding of how to compute the effective antenna gain from the actual antenna gain and the feeder cable losses. The range of permissible values for maximum antenna gain and feeder cable losses are included in this user guide together with a sample calculation. The product GUI automatically applies the correct conducted power limit to ensure that it is not possible for the installation to exceed the EIRP limit, when the appropriate values for antenna gain and feeder cable losses are entered into the GUI. Page 4 Avoidance of weather radars (USA only) To comply with FCC rules (KDB 443999: Interim Plans to Approve UNII Devices Operating in the 5470 -

5725 MHz Band with Radar Detection and DFS Capabilities), units which are installed within 35 km (22 miles) of a Terminal Doppler Weather Radar (TDWR) system (or have a line of sight propagation path to such a system) must be configured to avoid any frequency within +30 MHz or 30 MHz of the frequency of the TDWR device. This requirement applies even if the master is outside the 35 km (22 miles) radius but communicates with outdoor clients which may be within the 35 km (22 miles) radius of the TDWRs. If interference is not eliminated, a distance limitation based on line-of-sight from TDWR will need to be used. Devices with bandwidths greater than 20 MHz may require greater frequency separation. When planning a link in the USA, visit http://spectrumbridge.com/udia/home.aspx, enter the location of the planned link and search for TDWR radars. If a TDWR system is located within 35 km (22 miles) or has line of sight propagation to the PTP device, perform the following tasks:

Register the installation on http://spectrumbridge.com/udia/home.aspx. Make a list of channel center frequencies that must be barred, that is, those falling within

+30 MHz or 30 MHz of the frequency of the TDWR radars. The 450 Platform Family AP must be configured to not operate on the affected channels. Canada specific information Caution This device complies with ISEDC s license-exempt RSSs. Operation is subject to the following two conditions:

(1) This device may not cause interference; and

(2) This device must accept any interference, including interference that may cause undesired operation of the device. ISEDC requires manufacturers to implement special features to prevent interference to weather radar systems that operate in the band 5600 MHz to 5650 MHz. These features must be implemented in all products able to operate outdoors in the band 5470 MHz to 5725 MHz. Manufacturers must ensure that such radio products cannot be configured to operate outside of ISEDC rules; specifically it must not be possible to disable or modify the radar protection functions that have been demonstrated to ISEDC . In order to comply with these ISEDC requirements, Cambium supplies variants of the 450 Platform Family for operation in Canada. These variants are only allowed to operate with license keys that comply with ISEDC rules. In particular, operation of radio channels overlapping the band 5600 MHz to 5650 MHz is not allowed and these channels are permanently barred. In addition, other channels may also need to be barred when operating close to weather radar installations. Other variants of the 450 Platform Family are available for use in the rest of the world, but these variants are not supplied to Canada except under strict controls, when they are needed for export and deployment outside Canada. Page 5 Renseignements specifiques au Canada Attention Le prsent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorise aux deux conditions suivantes :

(1) l'appareil ne doit pas produire de brouillage, et

(2) l'utilisateur de l'appareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible d'en compromettre le fonctionnement. ISEDC a demand aux fabricants de mettre en uvre des mcanismes spcifiques pour viter dinterfrer avec des systmes radar fonctionnant dans la bande 5600 MHz 5650 MHz. Ces mcanismes doivent tre mis en uvre dans tous les produits capables de fonctionner l'extrieur dans la bande 5470 MHz 5725 MHz. Les fabricants doivent s'assurer que les produits de radiocommunications ne peuvent pas tre configurs pour fonctionner en dehors des rgles ISEDC, en particulier, il ne doit pas tre possible de dsactiver ou modifier les fonctions de protection des radars qui ont t dmontrs ISEDC. Afin de se conformer ces exigences de ISEDC, Cambium fournit des variantes du 450 Platform Family exclusivement pour le Canada. Ces variantes ne permettent pas lquipement de fonctionner en dehors des rgles de ISEDC. En particulier, le fonctionnement des canaux de radio qui chevauchent la bande 5600-5650 MHz est interdite et ces canaux sont dfinitivement exclus. ISEDC Approved Antennas The list of antennas used to obtain ISEDC approvals is provided in section Country specific radio regulations, Innovation Science and Economic Development Canada (ISEDC) , Table 225. Antennas externes Lorsque vous utilisez une version du produit sans antenne intgre, il peut tre ncessaire de rduire la puissance d'mission pour garantir que la limite rglementaire de puissance isotrope rayonne quivalente (PIRE) n'est pas dpasse. L'installateur doit avoir une bonne comprhension de la faon de calculer le gain de l'antenne relle et les pertes dans les cbles de connections. La plage de valeurs admissibles pour un gain maximal de l'antenne et des pertes de cbles de connections sont inclus dans ce guide d'utilisation avec un exemple de calcul. L'interface utilisateur du produit applique automatiquement la limite de puissance mene correct afin de s'assurer qu'il ne soit pas possible pour l'installation de dpasser la limite PIRE, lorsque les valeurs appropries pour le gain d'antenne et les pertes de cbles d'alimentation sont entres dans linterface utilisateur. Antennes approuves par ISEDC La liste des antennas approves pour loperation au Canada est founie dans le chapitre Country specific radio regulations, Innovation Science and Economic Development Canada (ISEDC) tableaux Table 225. Page 6 EU Declaration of Conformity Hereby, Cambium Networks declares that the Cambium 450 Series, 450b Series, 450i Series and 450m Series Wireless Ethernet Bridge complies with the essential requirements and other relevant provisions of Radio Equipment Directive 2014/53/EU. The declaration of conformity may be consulted at:

https://www.cambiumnetworks.com/eu_dofc Specific expertise and training for professional installers To ensure that the 450 Platform Family products PMP/PTP 450 Series, PMP/PTP 450i Series, PMP 450m Series are installed and configured in compliance with the requirements of ISEDC and the FCC, installers must have the radio engineering skills and training described in this section. The Cambium Networks technical training program details can be accessed from below link:

https://www.cambiumnetworks.com/training/

Ethernet networking skills The installer must have the ability to configure IP addressing on a PC and to set up and control products using a web browser interface. Lightning protection To protect outdoor radio installations from the impact of lightning strikes, the installer must be familiar with the normal procedures for site selection, bonding and grounding. Installation guidelines for the 450 Platform Family can be found in Chapter 2: System hardware and Chapter 3: System planning of 450 Platform Planning and Installation Guide. Training The installer needs to have basic competence in radio and IP network installation. The specific requirements applicable to the 450 Platform should be gained by reading:

Chapter 4: Preparing for installation and Chapter 5: Installation of 450 Platform Planning and Installation Guide, Chapter 1: Configuration, Chapter 2: :Tools, and Chapter 3: Operation of 450 Platform Configuration Guide (this document), And by performing sample set ups at base workshop before live deployments. The Cambium Networks technical training program details can be accessed from below link:

https://www.cambiumnetworks.com/training/

Page 7 Problems and warranty Reporting problems If any problems are encountered when installing or operating this equipment, follow this procedure to investigate and report:

1 Search this document and the software release notes of supported releases. 2 Visit the support website. 3 Ask for assistance from the Cambium product supplier. 4 Gather information from affected units, such as any available diagnostic downloads. 5 Escalate the problem by emailing or telephoning support. Repair and service If unit failure is suspected, obtain details of the Return Material Authorization (RMA) process from the support website (http://www.cambiumnetworks.com/support). Hardware warranty Cambiums standard hardware warranty is for one (1) year from date of shipment from Cambium Networks or a Cambium distributor. Cambium Networks warrants that hardware will conform to the relevant published specifications and will be free from material defects in material and workmanship under normal use and service. Cambium shall within this time, at its own option, either repair or replace the defective product within thirty (30) days of receipt of the defective product. Repaired or replaced product will be subject to the original warranty period but not less than thirty (30) days. To register PMP and PTP products or activate warranties, visit the support website. For warranty assistance, contact the reseller or distributor. The removal of the tamper-evident seal will void the warranty. Caution Using non-Cambium parts for repair could damage the equipment or void warranty. Contact Cambium for service and repair instructions. Portions of Cambium equipment may be damaged from exposure to electrostatic discharge. Use precautions to prevent damage. Page 8 Security advice Cambium Networks systems and equipment provide security parameters that can be configured by the operator based on their particular operating environment. Cambium recommends setting and using these parameters following industry recognized security practices. Security aspects to be considered are protecting the confidentiality, integrity, and availability of information and assets. Assets include the ability to communicate, information about the nature of the communications, and information about the parties involved. In certain instances Cambium makes specific recommendations regarding security practices, however the implementation of these recommendations and final responsibility for the security of the system lies with the operator of the system. Page 9 Warnings, cautions, and notes The following describes how warnings and cautions are used in this document and in all documents of the Cambium Networks document set. Warnings Warnings precede instructions that contain potentially hazardous situations. Warnings are used to alert the reader to possible hazards that could cause loss of life or physical injury. A warning has the following format:

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

Caution Caution text and consequence for not following the instructions in the caution. Notes A note means that there is a possibility of an undesirable situation or provides additional information to help the reader understand a topic or concept. A note has the following format:

Note Note text. Page 10 Caring for the environment The following information describes national or regional requirements for the disposal of Cambium Networks supplied equipment and for the approved disposal of surplus packaging. In EU countries The following information is provided to enable regulatory compliance with the European Union (EU) directives identified and any amendments made to these directives when using Cambium equipment in EU countries. Disposal of Cambium equipment European Union (EU) Directive 2012/19/EU Waste Electrical and Electronic Equipment (WEEE) Do not dispose of Cambium equipment in landfill sites. For disposal instructions, refer to https://www.cambiumnetworks.com/support/compliance/

Disposal of surplus packaging Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipients responsibility to ensure that packaging materials are collected and recycled according to the requirements of EU environmental law. In non-EU countries In non-EU countries, dispose of Cambium equipment and all surplus packaging in accordance with national and regional regulations. Page 11 Chapter 1: Configuration This chapter describes how to use the web interface to configure the 450 Platform link. This chapter contains the following topics:

Preparing for configuration on page 1-3 Connecting to the unit on page 1-4 Using the web interface on page 1-6 Quick link setup on page 1-13 Configuring IP and Ethernet interfaces on page 1-23 Upgrading the software version and using CNUT on page 1-67 General configuration on page 1-71 Configuring Unit Settings page on page 1-99 Setting up time and date on page 1-103 Configuring synchronization on page 1-105 Configuring security on page 1-109 Configuring 802.1X authentication on page 1-143 Configuring radio parameters on page 1-145 Setting up SNMP agent on page 1-218 Configuring syslog on page 1-227 Configuring remote access on page 1-232 Monitoring the Link on page 1-233 Configuring quality of service on page 1-236 Zero Touch Configuration Using DHCP Option 66 on page 1-262 Configuring Radio via config file on page 1-268 Configuring a RADIUS server on page 1-275 Installation Color Code on page 1-261 Page 1-2 Chapter 1: Configuration Preparing for configuration Preparing for configuration This section describes the checks to be performed before proceeding with unit configuration and antenna alignment. Safety precautions All national and local safety standards must be followed while configuring the units and aligning the antennas. Warning Ensure that personnel are not exposed to unsafe levels of RF energy. The units start to radiate RF energy as soon as they are powered up. Respect the safety standards defined in Legal and Open Sources Guide, in particular the minimum separation distances. Observe the following guidelines:

Never work in front of the antenna when the ODU is powered. Always power down the PSU before connecting or disconnecting the drop cable from the PSU, ODU or LPU. Regulatory compliance All applicable radio regulations must be followed while configuring the units and aligning the antennas. For more information, refer to chapter Compliance with radio regulations in Legal and Open Sources Guide. Page 1-3 Chapter 1: Configuration Connecting to the unit Connecting to the unit This section describes how to connect the unit to a management PC and power it up. Configuring the management PC Use this procedure to configure the local management PC to communicate with the 450 Platform ODU. Procedure 1 Configuring the management PC 1 Select Properties for the Ethernet port. In Windows 7 this is found in Control Panel >

Network and Internet > Network Connections > Local Area Connection. 2 Select Internet Protocol (TCP/IP):

3 Click Properties. Page 1-4 Chapter 1: Configuration Connecting to the unit 4 Enter an IP address that is valid for the 169.254.X.X network, avoiding 169.254.0.0 and 169.254.1.1. A good example is 169.254.1.3:

5 Enter a subnet mask of 255.255.0.0. Leave the default gateway blank. Connecting to the PC and powering up Use this procedure to connect a management PC and power up the 450 platform ODU. Procedure 2 Connecting to the PC and powering up 1 2 Check that the ODU and PSU are correctly connected. Connect the PC Ethernet port to the LAN port of the PSU using a standard (not crossed) Ethernet cable. 3 Apply mains or battery power to the PSU. The green Power LED should illuminate continuously. 4 After about several seconds, check that the orange Ethernet LED starts with 10 slow flashes. 5 Check that the Ethernet LED then illuminates continuously. Page 1-5 Chapter 1: Configuration Using the web interface Using the web interface This section describes how to log into the 450 Platform Family web interface and use its menus. Logging into the web interface Use this procedure to log into the web interface as a system administrator. Procedure 3 Logging into the web interface 1 Start the web browser from the management PC. 2 Type the IP address of the unit into the address bar. The factory default IP address is 169.254.1.1. Press ENTER. The web interface menu and System Summary page are displayed:

Page 1-6 Chapter 1: Configuration Using the web interface 3 On left hand side of home page, the login information is displayed:

4 Enter Username (factory default username is admin) and Password (factory default password is admin) and click Login. Web GUI 1 1 2 3 Field Name Main Menu Menu Options Description Click an option in side navigation bar (area marked as 1). Multiple options in sub-navigation bars appear Click top sub-navigation bar to choose one configuration page (area marked as 2) Parameters To configure the parameters (e.g. area marked as 3) Press "Save Changes" to confirm and save the changes To reboot the ODU Page 1-7 Chapter 1: Configuration Using the web interface Using the menu options Use the menu navigation bar in the left panel to navigate to each web page. Some of the menu options are only displayed for specific system configurations. Use Table 1 to locate information about using each web page. Table 1 Menu options and web pages Main menu Menu options Applicable module Description General Status Session Status Event Log Network Interface Layer 2 Neighbors General IP Radio SNMP cnMaestro Quality of Service (QoS) Security Time All Viewing General Status on page 3-2 AP, BHM Viewing Session Status on page 3-24 All All All All All All All All All All Interpreting messages in the Event Log on page 3-35 Viewing the Network Interface on page 3-38 Viewing the Layer 2 Neighbors on page 3-38 General configuration on page 1-71 Configuring IP and Ethernet interfaces on page 1-23 Configuring radio parameters on page 1-

145. Setting up SNMP agent on page 1-218 Configuring cnMaestroTM Connectivity on page 1-270 Configuring quality of service on page 1-

236 Configuring security on page 1-109 AP, BHM Setting up time and date Time page of 450 Platform Family -

AP/BHM on page 1-103 Page 1-8 Chapter 1: Configuration Using the web interface Main menu Menu options Applicable module Description VLAN DiffServ Protocol Filtering Syslog Ping Watchdog Unit Setting Scheduler Registration Failures Bridge Control Block Bridging Table Ethernet Radio VLAN Data Channels MIR/Burst Throughput All All All All All All All VLAN configuration for PMP on page 1-

45 VLAN configuration for PTP on page 1-

56 IPv4 and IPv6 Prioritization on page 1-

62 Filtering protocols and ports on page 1-

63 Configuring syslog on page 1-227 Configuring Ping Watchdog on page 1-

315 Configuring Unit Settings page on page 1-99 Viewing the Scheduler statistics on page 3-39 AP, BHM Viewing list of Registration Failures statistics on page 3-41 All All All All All All Interpreting Bridge Control Block statistics on page 3-72 Interpreting Bridging Table statistics on page 3-43 Interpreting Ethernet statistics on page 3-44 Interpreting RF Control Block statistics on page 3-47 Interpreting VLAN statistics on page 3-

51 Interpreting Data Channels statistics on page 3-52 AP, SM AP, BHM Interpreting MIR/Burst statistics on page 9-6 Interpreting Throughput statistics on page 3-58 Page 1-9 Chapter 1: Configuration Using the web interface Main menu Menu options Applicable module Description Filter ARP Overload Syslog Statistics Translation Table DHCP Relay NAT Stats NAT DHCP Pass Through Statistics Sync Status PPPoE SNMPv3 Statistics Frame Utilization Link Capacity Test Spectrum Analyzer Remote Spectrum Analyzer All All All All SM AP SM SM AP AP SM All Interpreting Filter statistics on page 3-

65 Viewing ARP statistics on page 3-66 Interpreting Overload statistics on page 3-61 Interpreting syslog statistics on page 3-

78 Interpreting Translation Table statistics on page 3-43 Interpreting DHCP Relay statistics on page 3-63 Viewing NAT statistics on page 3-66 Viewing NAT DHCP Statistics on page 3-68 Interpreting Pass Through Statistics on page 3-75 Interpreting Sync Status statistics on page 3-69 Interpreting PPPoE Statistics for Customer Activities on page 3-70 Interpreting SNMPv3 Statistics on page 3-76 AP, BH Interpreting Frame Utilization statistics on page 3-76 All All All Using the Link Capacity Test tool on page 2-338 Spectrum Analyzer tool on page 2-318 Remote Spectrum Analyzer tool on page 2-328 AP/BHM Evaluation SM, BHS Using AP Evaluation tool on page 2-347 Using BHM Evaluation tool on page 2-

352 Page 1-10 Chapter 1: Configuration Using the web interface Main menu Menu options Subscriber Configuration OFDM Frame Calculator BER results Alignment Tool Link Status Sessions Ping Test Change User Setting Add user Delete User User Quick Start Region Settings Applicable module Description AP All Using the Subscriber Configuration tool on page 2-360 Using the OFDM Frame Calculator tool on page 2-356 SM, BHS Using BER Results tool on page 2-369 SM, BHS Using the Alignment Tool on page 2-331 All Using the Link Status tool on page 2-361 AP, BHM Using the Sessions tool on page 2-370 All Using the Ping Test tool on page 2-371 All All All All Changing a User Setting on page 1-111 Adding a User for Access to a module on page 1-110 Deleting a User from Access to a module on page 1-111 Users account on page 1-112 AP, BHM Quick link setup on page 1-13 AP, BHM Quick link setup on page 1-13 Radio Carrier Frequency AP, BHM Quick link setup on page 1-13 Synchronization LAN IP Address AP, BHM Quick link setup on page 1-13 AP, BHM Quick link setup on page 1-13 Review and Save Configuration AP, BHM Quick link setup on page 1-13 Quick Status Spectrum Results (PDA) SM SM Page 1-11 Chapter 1: Configuration Using the web interface Main menu Menu options Applicable module Description Information BHM Evaluation AIM Copyright Notices SM SM SM All All The PDA web-page includes 320 x 240 pixel formatted displays of information important to installation and alignment for installers using legacy PDA devices. All device web pages are compatible with touch devices such as smart phones and tablets. The Copyright web-page displays pertinent device copyright information. Page 1-12 Chapter 1: Configuration Quick link setup Quick link setup This section describes how to use the Quick Start Wizard to complete the essential system configuration tasks that must be performed on a PMP/PTP configuration. Initiating Quick Start Wizard Applicable products PMP: AP PTP: BHM To start with Quick Start Wizard: after logging into the web management interface click the Quick Start button on the left side of main menu bar. The AP/BHM responds by opening the Quick Start page. Figure 1 Disarm Installation page (top and bottom of page shown) Quick Start is a wizard that helps you to perform a basic configuration that places an AP/BHM into service. Only the following parameters must be configured:

Region Code RF Carrier Frequency Synchronization In each Quick Start page, you can specify the settings to satisfy the requirements of the network. save the configuration to non-volatile memory. review the configuration selected. LAN (Network) IP Address Procedure 4 Quick start wizard 1 At the bottom of the Quick Start tab, click the Go To Next Page button. Page 1-13 Chapter 1: Configuration Quick link setup 2 3 4 From the pull-down menu, select the region in which the AP will operate. Figure 2 Regional Settings tab of AP/BHM Click the Go To Next Page button. From the pull-down menu, select a frequency for the test. Figure 3 Radio Carrier Frequency tab of AP/BHM Page 1-14 Chapter 1: Configuration Quick link setup 5 6 Click the Go To Next Page button. At the bottom of this tab, select Generate Sync Signal. Figure 4 Synchronization tab of AP/BHM 7 Click the Go To Next Page button. Page 1-15 Chapter 1: Configuration Quick link setup 8 At the bottom of the IP address configuration tab, either specify an IP Address, a Subnet Mask, and a Gateway IP Address for management of the AP and leave the DHCP state set to Disabled. set the DHCP state to Enabled to have the IP address, subnet mask, and gateway IP address automatically configured by a domain name server (DNS). Figure 5 LAN IP Address tab of the AP/BHM Note Cambium encourages you to experiment with the interface. Unless you save a configuration and reboot the AP after you save the configuration, none of the changes are affected. 9 Click the Go To Next Page button. Page 1-16 Chapter 1: Configuration Quick link setup 10 Ensure that the initial parameters for the AP are set as you intended. Figure 6 Review and Save Configuration tab of the AP/BHM 11 Click Save Changes button. Page 1-17 Chapter 1: Configuration Quick link setup 12 Click the Reboot button. RESULT: The AP responds with the message Reboot Has Been Initiated 13 Wait until the indicator LEDs are not red. 14 Trigger your browser to refresh the page until the AP redisplays the General Status tab. 15 Wait until the red indicator LEDs are not lit. Configuring time settings Applicable products PMP: AP PTP: BHM To proceed with the test setup, click the Configuration link on the left side of the General Status page. When the AP responds by opening the Configuration page to the General page, click the Time tab. Figure 7 Time tab of the AP/BHM To have each log in the AP/BHM correlated to a meaningful time and date, either a reliable network element must pass time and date to the AP/BHM or you must set the time and date whenever a power cycle of the AP/BHM has occurred. A network element passes time and date in any of the following scenarios:

A connected CMM4 passes time and date (GPS time and date, if received). A separate NTP server is addressable from the AP/BHM. If the AP/BHM should obtain time and date from a CMM4, or a separate NTP server, enter the IP address of the CMM4 or NTP server on this tab. To force the AP/BHM to obtain time and date before the first (or next) 15-minute interval query of the NTP server, click Get Time through NTP. Page 1-18 Chapter 1: Configuration If you enter a time and date, the format for entry is Figure 8 Time and date entry formats Time:

hh / mm / ss Quick link setup Date:

where MM / dd / yyyy hh represents the two-digit hour in the range 00 to 24 mm represents the two-digit minute ss represents the two-digit second MM represents the two-digit month dd represents the two-digit day yyyy represents the four-digit year Proceed with the time setup as follows. Procedure 5 Entering AP/BHM time setup information 1 2 Enter the appropriate information in the format shown above. Then click the Set Time and Date button. Note The time displayed at the top of this page is static unless your device is set to automatically refresh Powering the SM/BHS for test Procedure 6 Powering the SM/BHS for test 1 2 3 4 5 In one hand, securely hold the top (larger shell) of the SM/BHS. With the other hand, depress the lever in the back of the base cover (smaller shell). Remove the base cover. Plug one end of a CAT5 Ethernet cable into the SM PSU port Plug the other end of the Ethernet cable into the jack in the pig tail that hangs from the power supply Roughly aim the SM/BHS toward the AP/BHM Plug the power supply into an electrical outlet Warning From this point until you remove power from the AP/BHM, stay at least as far from the AP/BHM as the minimum separation distance specified in Calculated distances and power compliance margins in chapter 11. 6 Repeat the foregoing steps for each SM/BHS that you wish to include in the test. Page 1-19 Chapter 1: Configuration Quick link setup Viewing the Session Status of the AP/BHM to determine test registration Once the SMs/BHS under test are powered on, return to the computing device to determine if the SM/BHS units have registered to the AP/BHM. Note In order for accurate power level readings to be displayed, traffic must be present on the radio link. The Session Status tab provides information about each SM/BHS that has registered to the AP/BHM. This information is useful for managing and troubleshooting a system. All information that you have entered in the Site Name field of the SM/BHS displays in the Session Status tab of the linked AP/BHM. The Session Status tab also includes the current active values on each SM( or BHS) (LUID) for MIR, and VLAN, as well as the source of these values (representing the SM/BHS itself, Authentication Server, or the AP/BHM and cap, if anyfor example, APCAP as shown above).. As an SM/BHS registers to the AP/BHM, the configuration source that this page displays for the associated LUID may change. After registration, however, the displayed source is stable and can be trusted. Idle subscribers may be included or removed from the session status display by enabling or disabling, respectively, the Show Idle Sessions parameter. Enabling or disabling this parameter only affects the GUI display of subscribers, not the registration status. The SessionStatus.xml hyperlink allows user to export session status page from web management interface of AP/BHM. The session status page will be exported in xml file. Page 1-20 Chapter 1: Configuration Quick link setup Procedure 7 Viewing the AP Session Status page 1 On the AP web management GUI, navigate to Home, Session Status:

Figure 9 Session Status tab of AP Note Session status page for BHM is same as AP. 2 Verify that for each SM (or BHS) MAC address (printed on the SM/BHS housing) the AP/BHM has established a registered session by verifying the State status of each entry. The Session Status page of the AP/BHM is explained in Table 2. Page 1-21 Chapter 1: Configuration Table 2 Session Status Attributes AP Quick link setup Attribute Meaning Show Idle Sessions Last Session Counter Reset Reference EVM setting option Idle subscribers may be included or removed from the session status display by enabling or disabling, respectively, the Show Idle Sessions parameter. Enabling or disabling this parameter only affects the GUI display of subscribers, not the registration status. This field displays date and time stamp of last session counter reset. Option to configure reference EVM for all connected SMs. Last Time Idle SMs Removed This field displays date and time stamp of last Idle SMs Removed. On click of Remove Idle SMs button, all the SMs which are in Idle state are flushed out. Data Device tab Session tab Power tab See Exporting Session Status page of AP/BHM on page 1-259 See Device tab on page 3-24 See Session tab on page 3-26 See Power tab on page 3-27 Configuration tab See Configuration tab on page 3-30 Link Quality See Link Quality tab on page 3-33 Page 1-22 Chapter 1: Configuration Configuring IP and Ethernet interfaces Configuring IP and Ethernet interfaces IP interface with NAT enabled on page IP interface with NAT disabled on page 1-33 This task consists of the following sections:

Configuring the IP interface on page 1-24 Auxiliary port on page 1-27 NAT, DHCP Server, DHCP Client and DMZ on page 1-28 NAT tab with NAT disabled on page 1-36 NAT tab with NAT enabled on page 1-39 NAT DNS Considerations on page 1-44 DHCP BHS on page 1-44 VLAN configuration for PMP on page 1-45 VLAN page of AP on page 1-48 VLAN page of SM on page 1-51 VLAN Membership tab of SM on page 1-55 VLAN configuration for PTP on page 1-56 NAT Port Mapping tab - SM on page 1-44 Page 1-23 Chapter 1: Configuration Configuring IP and Ethernet interfaces Configuring the IP interface The IP interface allows users to connect to the 450 Platform Family web interface, either from a locally connected computer or from a management network. Applicable products PMP: AP SM PTP: BHM BMS To configure the IP interface, follow these instructions:

Procedure 8 Configuring the AP/BHM IP interface 1 Select menu option Configuration > IP. The LAN configuration page is displayed:

2 3 4 Update IP Address, Subnet Mask and Gateway IP Address to meet network requirements (as specified by the network administrator). Review the other IP interface attributes and update them, if necessary (see Table 3 IP interface attributes). Click Save. Reboot Required message is displayed:

5 Click Reboot button. The IP page of AP/SM/BHM/BHS is explained in Table 3. Page 1-24 Chapter 1: Configuration Table 3 IP interface attributes Configuring IP and Ethernet interfaces Attribute IP Address Meaning Internet Protocol (IP) address. This address is used by family of Internet protocols to uniquely identify this unit on a network. Subnet Mask Defines the address range of the connected IP network. Gateway IP Address DHCP state DNS IP Address The IP address of a computer on the current network that acts as a gateway. A gateway acts as an entrance and exit to packets from and to other networks. If Enabled is selected, the DHCP server automatically assigns the IP configuration (IP address, subnet mask, and gateway IP address) and the values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable (read only), in the Network Interface tab of the Home page. Canopy devices allow for configuration of a preferred and alternate DNS server IP address either automatically or manually. Devices must set DNS server IP address manually when DHCP is disabled for Page 1-25 Chapter 1: Configuration Configuring IP and Ethernet interfaces the management interface of the device. DNS servers may be configured automatically from the DHCP response when DHCP is enabled for the management interface of the device. Optionally devices may be configured to set the DNS server IP address manually when DHCP is enabled for the management interface. The default DNS IP addresses are 0.0.0.0 when configured manually. Preferred DNS Server The first address used for DNS resolution. Alternate DNS Server If the Preferred DNS server cannot be reached, the Alternate DNS Server is used. Domain Name The operators management domain name may be configured for DNS. The domain name configuration can be used for configuration of the servers in the operators network. The default domain name is example.com, and is only used if configured as such. Advanced LAN1 IP Configuration Default alternate LAN1 IP address Hardcoded default alternate IP address (169.254.1.1) that is available only when connected to the Ethernet port. When enabled, user can configure a second IP address for the bridge which is other than the hardcoded IP address (169.254.1.1). AUX Ethernet Port AUX Ethernet Port Enabled: Data is enabled for Auxiliary port Disabled: Data is disabled for Auxiliary port AUX Ethernet Port AUX Ethernet Port PoE LAN2 Network Interface Configuration (Radio Private Interface) IP Address Enabled: PoE out is enable for Auxiliary port Disabled: PoE out is disabled for Auxiliary port It is recommended not to change this parameter from the default AP/BHM private IP address of 192.168.101.1. A /24 CIDR subnet is used to communicate with each of the SMs/BHS that are registered. The AP/BHM uses a combination of the private IP and the LUID

(logical unit ID) of the SM/BHS. It is only displayed for AP and BHM. Table 4 SM/BHS private IP and LUID SM/BHS LUID Private IP First SM/BHS registered Second SM registered 2 3 192.168.101.2 192.168.101.3 Page 1-26 Chapter 1: Configuration Configuring IP and Ethernet interfaces Auxiliary port An additional Ethernet port labeled Aux for Auxiliary port is implemented for downstream traffic. This feature is supported only for PTP/PMP 450i ODUs. To enable the Aux port, follow these instructions:

Procedure 9 Enabling Aux port interface 1 Select menu option Configuration > IP > Aux Network Interface tab.:

Click Enable button of Aux Ethernet Port parameter to enable Aux Ethernet port Click Enable button of Aux Ethernet Port PoE parameter to enable Aux port PoE out. Click Save. Reboot Required message is displayed. Click Reboot. 2 3 4 5 Table 5 Aux port attributes Attribute Meaning Aux Ethernet Port Enabled: Data is enabled for Auxiliary port Disabled: Data is disabled for Auxiliary port Aux Ethernet Port PoE Enabled: PoE out is enable for Auxiliary port Disabled: PoE out is disabled for Auxiliary port By disabling this feature, the data at the Auxiliary port will be disabled. Page 1-27 Chapter 1: Configuration Configuring IP and Ethernet interfaces NAT, DHCP Server, DHCP Client and DMZ Applicable products PMP:

SM The system provides NAT (Network Address Translation) for SMs in the following combinations of NAT and DHCP (Dynamic Host Configuration Protocol):

NAT Disabled NAT with DHCP Client (DHCP selected as the Connection Type of the WAN interface) and DHCP Server NAT with DHCP Client(DHCP selected as the Connection Type of the WAN interface) NAT with DHCP Server NAT without DHCP NAT NAT isolates devices connected to the Ethernet or wired side of a SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic (separate from its address for management), terminates transport traffic and allows you to assign a range of IP addresses to devices that are connected to the Ethernet or wired side of the SM. In the Cambium system, NAT supports many protocols, including HTTP, ICMP (Internet Control Message Protocols), and FTP (File Transfer Protocol). For virtual private network (VPN) implementation, L2TP over IPSec (Level 2 Tunneling Protocol over IP Security) and PPTP (Point to Point Tunneling Protocol) are supported. Note When NAT is enabled, a reduction in throughput is introduced in the system (due to processing overhead). DHCP DHCP enables a device to be assigned a new IP address and TCP/IP parameters, including a default gateway, whenever the device reboots. Thus, DHCP reduces configuration time, conserves IP addresses, and allows modules to be moved to a different network within the Cambium system. In conjunction with the NAT features, each SM provides the following:

A DHCP server that assigns IP addresses to computers connected to the SM by Ethernet protocol. A DHCP client that receives an IP address for the SM from a network DHCP server. DMZ In conjunction with the NAT features, a DMZ (Demilitarized Zone) allows the allotment of one IP address behind the SM for a device to logically exist outside the firewall and receive network traffic. The first three octets of this IP address must be identical to the first three octets of the NAT private IP address. A DHCP server that assigns IP addresses to computers connected to the SM by Ethernet protocol. A DHCP client that receives an IP address for the SM from a network DHCP server. Page 1-28 Chapter 1: Configuration Configuring IP and Ethernet interfaces NAT Disabled The NAT Disabled implementation is illustrated in Figure 10. Figure 10 NAT disabled implementation NAT with DHCP Client and DHCP Server The NAT with DHCP Client and DHCP server is illustrated in Figure 11. Page 1-29 Chapter 1: Configuration Configuring IP and Ethernet interfaces Figure 11 NAT with DHCP client and DHCP server implementation NAT with DHCP Client Figure 12 NAT with DHCP client implementation Page 1-30 Chapter 1: Configuration Configuring IP and Ethernet interfaces NAT with DHCP Server Figure 13 NAT with DHCP server implementation NAT without DHCP Figure 14 NAT without DHCP implementation Page 1-31 Chapter 1: Configuration Configuring IP and Ethernet interfaces NAT and VPNs VPN technology provides the benefits of a private network during communication over a public network. One typical use of a VPN is to connect employees remotely (who are at home or in a different city), with their corporate network through a public Internet. Any of several VPN implementation schemes is possible. By design, NAT translates or changes addresses, and thus interferes with a VPN that is not specifically supported by a given NAT implementation. With NAT enabled, SM supports L2TP over IPSec (Level 2 Tunneling Protocol over IP Security) VPNs and PPTP (Point to Point Tunneling Protocol) VPNs. With NAT disabled, SM supports all types of VPNs. Page 1-32 Chapter 1: Configuration Configuring IP and Ethernet interfaces IP interface with NAT disabled - SM The IP page of SM with NAT disabled is explained in Table 6. Table 6 IP attributes - SM with NAT disabled Attribute IP Address Meaning Enter the non-routable IP address to associate with the Ethernet connection on this SM. (The default IP address from the factory is 169.254.1.1.) If you forget this parameter, you must both:

physically access the module. use recovery mode to access the module configuration parameters at 169.254.1.1. Note Note or print the IP settings from this page. Ensure that you can readily associate these IP settings both with the module and with the other data that you store about the module. Network Accessibility Specify whether the IP address of the SM must be visible to only a device connected to the SM by Ethernet (Local) or be visible to the AP/BHM as well

(Public). Subnet Mask Enter an appropriate subnet mask for the SM to communicate on the network. The default subnet mask is 255.255.0.0. Gateway IP Address Enter the appropriate gateway for the SM to communicate with the network. The default gateway is 169.254.0.0. DHCP state If you select Enabled, the DHCP server automatically assigns the IP configuration (IP address, subnet mask, and gateway IP address) and the values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable, but not settable, in the Network Interface tab of the Home page. In this tab, DHCP State is settable only if the Network Accessibility parameter in the IP tab is set to Public. This parameter is also settable in the NAT tab of the Configuration web page, but only when NAT is enabled. Page 1-33 Chapter 1: Configuration Configuring IP and Ethernet interfaces If the DHCP state parameter is set to Enabled in the Configuration > IP sub-

menu of the SM/BHS, do not check the BootpClient option for Packet Filter Types in its Protocol Filtering tab, because doing so can block the DHCP request. (Filters apply to all packets that leave the SM via its RF interface, including those that the SM itself generates.) If you want to keep DHCP enabled and avoid the blocking scenario, select the Bootp Server option instead. This will result in responses being appropriately filtered and discarded. DHCP DNS IP Address Canopy devices allow for configuration of a preferred and alternate DNS server IP address either automatically or manually. Devices must set DNS server IP address manually when DHCP is disabled for the management interface of the device. DNS servers may be configured automatically from the DHCP response when DHCP is enabled for the management interface of the device. Optionally devices may be configured to set the DNS server IP address manually when DHCP is enabled for the management interface. The default DNS IP addresses are 0.0.0.0 when configured manually. Preferred DNS Server The first DNS server used for DNS resolution. Alternate DNS Server The second DNS server used for DNS resolution. Domain Name The operators management domain name may be configured for DNS. The domain name configuration can be used for configuration of the servers in the operators network. The default domain name is example.com, and is only used if configured as such. Page 1-34 Chapter 1: Configuration Configuring IP and Ethernet interfaces IP interface with NAT enabled - SM The IP page of SM with NAT enabled is explained in Table 7. Table 7 IP attributes - SM with NAT enabled Meaning Assign an IP address for SM/BHS management through Ethernet access to the SM/BHS. Set only the first three bytes. The last byte is permanently set to 1. This address becomes the base for the range of DHCP-assigned addresses. Assign a subnet mask of 255.255.255.0 or a more restrictive subnet mask. Set only the last byte of this subnet mask. Each of the first three bytes is permanently set to 255. Attribute IP Address Subnet Mask Page 1-35 Chapter 1: Configuration Configuring IP and Ethernet interfaces NAT tab with NAT disabled - SM The NAT tab of SM with NAT disabled is explained in Table 8. Table 8 NAT attributes - SM with NAT disabled Page 1-36 Chapter 1: Configuration Configuring IP and Ethernet interfaces Attribute Meaning NAT Enable/Disable This parameter enables or disables the Network Address Translation (NAT) feature for the SM. NAT isolates devices connected to the Ethernet or wired side of a SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic separate from its address for management, terminates transport traffic, and allows you to assign a range of IP addresses to devices that are connected to the Ethernet or wired side of the SM. When NAT is enabled, VLANs are not supported on the wired side of that SM. You can enable NAT in SMs within a sector where VLAN is enabled in the AP/BHM, but this may constrain network design. IP Address Subnet Mask This field displays the IP address for the SM. DHCP Server will not automatically assign this address when NAT is disabled. This field displays the subnet mask for the SM. DHCP Server will not automatically assign this address when NAT is disabled. Gateway IP Address This field displays the gateway IP address for the SM. DHCP Server will not automatically assign this address when NAT is disabled. ARP Cache Timeout If a router upstream has an ARP cache of longer duration (as some use 30 minutes), enter a value of longer duration than the router ARP cache. The default value of this field is 20 minutes. TCP Session Garbage Timeout Where a large network exists behind the SM, you can set this parameter to lower than the default value of 120 minutes. This action makes additional resources available for greater traffic than the default value accommodates. UDP Session Garbage Timeout You may adjust this parameter in the range of 1 to 1440 minutes, based on network performance. The default value of this parameter is 4 minutes. Translation Table Size Total number of minutes that have elapsed since the last packet transfer between the connected device and the SM/BHS. Page 1-37 Chapter 1: Configuration Configuring IP and Ethernet interfaces Note When NAT is disabled, the following parameters are not required to be configurable:

WAN Inter face > Connection Type, IP Address, Subnet Mask, Gateway IP address LAN Interface > IP Address LAN DHCP Server > DHCP Server Enable/Disable, DHCP Server Lease Timeout, Number of IPs to Lease, DNS Server Proxy, DNS IP Address, Preferred DNS IP address, Alternate DNS IP address Remote Management Interface > Remote Management Interface, IP address, Subnet Mask, DHCP DNS IP Address, Preferred DNS Server, Alternate DNS Server, Domain Name NAT Protocol Parameters > ARP Cache Timeout, TCP Session Garbage Timeout, UDP Session Garbage Timeout, Translation Table Size Page 1-38 Chapter 1: Configuration Configuring IP and Ethernet interfaces NAT tab with NAT enabled - SM The NAT tab of SM with NAT enabled is explained in Table 9. Table 9 NAT attributes - SM with NAT enabled Page 1-39 Chapter 1: Configuration Configuring IP and Ethernet interfaces Attribute Meaning NAT Enable/Disable This parameter enables or disabled the Network Address Translation (NAT) feature for the SM. NAT isolates devices connected to the Ethernet or wired side of a SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic separate from its address for management, terminates transport traffic, and allows you to assign a range of IP addresses to devices that are connected to the Ethernet or wired side of the SM. When NAT is enabled, VLANs are not supported on the wired side of that SM. You can enable NAT in SMs within a sector where VLAN is enabled in the AP, but this may constrain network design. WAN Interface The WAN interface is the RF-side address for transport traffic. Connection Type This parameter may be set to Static IPwhen this is the selection, all three parameters (IP Address, Subnet Mask, and Gateway IP Address) must be properly populated. DHCPwhen this is the selection, the information from the DHCP server configures the interface. PPPoEwhen this is the selection, the information from the PPPoE server configures the interface. Subnet Mask If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the subnet mask of the SM for RF transport traffic. Gateway IP Address Reply to Ping on WAN Interface LAN Interface IP Address Subnet Mask If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the gateway IP address for the SM for RF transport traffic. By default, the radio interface does not respond to pings. If you use a management system (such as WM) that will occasionally ping the SM, set this parameter to Enabled. The LAN interface is both the management access through the Ethernet port and the Ethernet-side address for transport traffic. When NAT is enabled, this interface is redundantly shown as the NAT Network Interface Configuration on the IP tab of the Configuration web page in the SM. Assign an IP address for SM/BHS management through Ethernet access to the SM. This address becomes the base for the range of DHCP-assigned addresses. Assign a subnet mask of 255.255.255.0 or a more restrictive subnet mask. Set only the last byte of this subnet mask. Each of the first three bytes is permanently set to 255. DMZ Enable Either enable or disable DMZ for this SM/BHS. Page 1-40 Chapter 1: Configuration Configuring IP and Ethernet interfaces DMZ IP Address DHCP Server DHCP Server Enable/Disable DHCP Server Lease Timeout DHCP Start IP If you enable DMZ in the parameter above, set the last byte of the DMZ host IP address to use for this SM when DMZ is enabled. Only one such address is allowed. The first three bytes are identical to those of the NAT private IP address. Ensure that the device that receives network traffic behind this SM is assigned this address. The system provides a warning if you enter an address within the range that DHCP can assign. This is the server (in the SM) that provides an IP address to the device connected to the Ethernet port of the SM. Select either Enabled or Disabled. Enable to:

Allow this SM to assign IP addresses, subnet masks, and gateway IP addresses to attached devices. Assign a start address for DHCP. Designate how many IP addresses may be temporarily used (leased). Disable to:

Restrict SM/BHS from assigning addresses to attached devices. Based on network performance, enter the number of days between when the DHCP server assigns an IP address and when that address expires. The range of values for this parameter is 1 to 30 days. The default value is 30 days. If you enable DHCP Server below, set the last byte of the starting IP address that the DHCP server assigns. The first three bytes are identical to those of the NAT private IP address. Number of IPs to Lease Enter how many IP addresses the DHCP server is allowed to assign. The default value is 50 addresses. DNS Server Proxy This parameter enables or disables advertisement of the SM/BHS as the DNS server. On initial boot up of a SM with the NAT WAN interface configured as DHCP or PPPoE, the SM module will not have DNS information immediately. With DNS Server Proxy disabled, the clients will renew their lease about every minute until the SM has the DNS information to give out. At this point the SM will go to the full configured lease time period which is 30 days by default. With DNS Server Proxy enabled, the SM will give out full term leases with its NAT LAN IP as the DNS server. DNS IP Address Select either:

Obtain Automatically to allow the system to set the IP address of the DNS server or Set Manually to enable yourself to set both a preferred and an alternate DNS IP address. Preferred DNS IP Address Enter the preferred DNS IP address to use when the DNS IP Address parameter is set to Set Manually. Page 1-41 Chapter 1: Configuration Configuring IP and Ethernet interfaces Alternate DNS IP Address Remote Management Interface Enter the DNS IP address to use when the DNS IP Address parameter is set to Set Manually and no response is received from the preferred DNS IP address. To offer greater flexibility in IP address management, the NAT-enabled SMs configured WAN Interface IP address may now be used as the device Remote Management Interface (unless the SMs PPPoE client is set to Enabled) Disable: When this interface is set to Disable, the SM is not directly accessible by IP address. Management access is only possible through either the LAN (Ethernet) interface or a link from an AP web page into the WAN

(RF-side) interface. Enable (Standalone Config): When this interface is set to Enable

(Standalone Config), to manage the SM/BHS the device must be accessed by the IP addressing information provided in the Remote Configuration Interface section. Note When configuring PPPoE over the link, use this configuration option (PPPoE traffic is routed via the IP addressing specified in section Remote Configuration Interface). Enable (Use WAN Interface): When this interface is set to Enable (Use WAN Interface), the Remote Configuration Interface information is greyed out, and the SM is managed via the IP addressing specified in section WAN Interface). Note When using this configuration, the ports defined in section Configuration, Port Configuration are consumed by the device. For example, if FTP Port is configured as 21 by the SM, an FTP server situated below the SM must use a port other than 21. This also applies to DMZ devices; any ports specified in section Configuration, Port Configuration will not be translated through the NAT, they are consumed by the devices network stack for management. Connection Type This parameter can be set to:

IP Address Subnet Mask Static IPwhen this is the selection, all three parameters (IP Address, Subnet Mask, and Gateway IP Address) must be properly populated. DHCPwhen this is the selection, the information from the DHCP server configures the interface. If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the IP address of the SM for RF management traffic. If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the subnet mask of the SM for RF management traffic. Page 1-42 Chapter 1: Configuration Configuring IP and Ethernet interfaces Gateway IP Address If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the gateway IP address for the SM for RF management traffic. Note or print the IP settings from this page. Ensure that you can readily associate these IP settings both with the module and with the other data that you store about the module. DHCP DNS IP Address Select either:

Obtain Automatically to allow the system to set the IP address of the DNS server. or Set Manually to enable yourself to set both a preferred and an alternate DNS IP address. Preferred DNS Server Enter the preferred DNS IP address to use when the DNS IP Address parameter is set to Set Manually. Alternate DNS Server Enter the DNS IP address to use when the DNS IP Address parameter is set to Set Manually and no response is received from the preferred DNS IP address. Domain Name Domain Name to use for management DNS configuration. This domain name may be concatenated to DNS names used configured for the remote configuration interface. ARP Cache Timeout If a router upstream has an ARP cache of longer duration (as some use 30 minutes), enter a value of longer duration than the router ARP cache. The default value of this field is 20 (minutes). TCP Session Garbage Timeout Where a large network exists behind the SM, you can set this parameter to lower than the default value of 120 (minutes). This action makes additional resources available for greater traffic than the default value accommodates. UDP Session Garbage Timeout You may adjust this parameter in the range of 1 to 1440 minutes, based on network performance. The default value of this parameter is 4 (minutes). Page 1-43 Chapter 1: Configuration Configuring IP and Ethernet interfaces NAT DNS Considerations - SM SM DNS behavior is different depending on the accessibility of the SM. When NAT is enabled the DNS configuration that is discussed in this document is tied to the RF Remote Configuration Interface, which must be enabled to utilize DNS Client functionality. Note that the WAN DNS settings when NAT is enabled are unchanged with the addition of the management DNS feature discussed in this document. Table 10 SM DNS Options with NAT Enabled NAT Configuration Management Interface Accessibility NAT Enabled RF Remote Management Interface Disabled RF Remote Management Interface Enabled DHCP Status DNS Status N/A DNS Disabled DHCP Disabled DNS Static Configuration DHCP Enabled DNS from DHCP or DNS Static Configuration NAT Port Mapping tab - SM The NAT Port Mapping tab of the SM is explained in Table 11. Table 11 NAT Port Mapping attributes - SM Attribute Meaning Port Map 1 to 10 Separate parameters allow you to distinguish NAT ports from each other by assigning a unique combination of port number, protocol for traffic through the port, and IP address for access to the port DHCP BHS Applicable products PTP: BHM Page 1-44 Chapter 1: Configuration Configuring IP and Ethernet interfaces DHCP enables a device to be assigned a new IP address and TCP/IP parameters, including a default gateway, whenever the device reboots. Thus, DHCP reduces configuration time, conserves IP addresses, and allows modules to be moved to a different network within the Cambium system. In conjunction with the NAT features, each BHS provides:

A DHCP server that assigns IP addresses to computers connected to the BHS by Ethernet protocol. A DHCP client that receives an IP address for the BHS from a network DHCP server. Reconnecting to the management PC If the IP Address, Subnet Mask and Gateway IP Address of the unit have been updated to meet network requirements, then reconfigure the local management PC to use an IP address that is valid for the network. See Configuring the management PC on page 1-4. Once the unit reboots, log in using the new IP address. See Logging into the web interface on page 1-6. VLAN configuration for PMP Applicable products PMP: AP SM VLAN Remarking VLAN Remarking feature allows the user to change the VLAN ID and priority of both upstream and downstream packets at the Ethernet Interface. The remarking configuration is available for:

1. VLAN ID re-marking 2. 802.1p priority re-marking Note For Q-in-Q VLAN tagged frame, re-marking is performed on the outer tag. Page 1-45 Chapter 1: Configuration Configuring IP and Ethernet interfaces VLAN ID Remarking SM supports the ability to re-mark the VLAN ID on both upstream and downstream VLAN frames at the Ethernet interface. For instance, a configuration can be added to re-mark VLAN ID x to VLAN ID y as shown in Table 12. AP does not support VLAN ID remarking. Table 12 VLAN Remarking Example VLAN frame direction Remarking Upstream SM receives VLAN ID x frame at the Ethernet interface, checks the configuration and re-marks to VLAN ID y. So VLAN ID y frame comes out of APs Ethernet interface. When SM re-marks, a dynamic entry in VLAN membership table for y is added to allow reception of VLAN ID y downstream packet. AP receives VLAN ID y frame at the Ethernet interface and sends to SM. SM accepts the frame as it has an entry in the membership table and re-

marks to VLAN ID x. This reverse re- marking is necessary because the downstream devices do not know of re-marking and are expecting VLAN x frames. This remarking is done just before sending the packet out on Ethernet interface. Downstream 802.1P Remarking AP/BHM and SM/BHS allow re-marking of 802.1p priority bits for the frames received at the Ethernet interface. Priority bits are not re-marked for the packets sent out of Ethernet interface (reverse direction). Configuration must be added at SM/BHS for upstream frames and at AP/BHM for downstream frames. VLAN Priority Bits configuration VLAN Priority Bits Configuration feature allows the user to configure the three 802.1p bits upon assigning VLAN to an ingress packet. The priority bits configuration is available for:

Default Port VID Provider VIDs MAC Address mapped Port VID Management VID Default Port VID This VID is used for untagged frames and will correspond to the Q-Tag for 802.1Q frames (if VLAN Port Type is Q), or the C-Tag for 802.1ad frames (if the VLAN Port Type is QinQ). Page 1-46 Chapter 1: Configuration Configuring IP and Ethernet interfaces The priority bits used in the Q-tag/C-tag are configurable. The configuration can be:

Promote IPv4/IPv6 priority The priority in the IP header is copied to the Q-tag/C-tag. Define priority Specify the priority in the range of 0 to 7. This value is used as priority in the Q-

tag/C-tag. MAC Address Mapped VID If a packet arrives at the SM/BHS that is sourced from a device whose MAC address is in the table, then the corresponding VID is used for that frames Q-tag (Q port) or C-tag

(QinQ port). The priority bits used in the Q-tag/C-tag are configurable similar to default port VID. Provider VID The provider VID is used for the S-tag. The priority bits used in the S-tag are configurable similar to default port VID. Provider VID has an extra priority configuration:

Copy inner tag 802.1p priority The priority in the C-tag is copied to the S-tag. Management VID This VID is used to communicate with AP/BHM and SM/BHS for management purposes. The priority bits used in the Q-tag are configurable similar to default port VID. Use APs Management VID for ICC connected SM This feature allows the SM to use the APs management VLAN ID when the SM is registered to the AP via ICC. This feature is useful for the customer who uses a different management VID for the SM and AP and Zero Touch feature is enabled for configuration. This parameter may be accessed via the Configuration > VLAN page on the APs web management interface. Page 1-47 Chapter 1: Configuration VLAN page of AP The VLAN tab of the AP/BHM is explained in Table 13. Table 13 AP/BHM VLAN tab attributes Configuring IP and Ethernet interfaces Attribute VLAN Always use Local VLAN Config Allow Frame Types Dynamic Learning Meaning Specify whether VLAN functionality for the AP and all linked SMs must

(Enabled) or may not (Disabled) be allowed. The default value is Disabled. Enable this option before you reboot this AP as a SM to use it to perform spectrum analysis. Once the spectrum analysis completes, disable this option before you reboot the module as an AP, Select the type of arriving frames that the AP must tag, using the VID that is stored in the Untagged Ingress VID parameter. The default value is All Frames. Specify whether the AP must (Enabled) or not (Disabled) add the VLAN IDs

(VIDs) of upstream frames to the VID table. (The AP passes frames with VIDs that are stored in the table both upstream and downstream.). The default value is Enabled. Page 1-48 Chapter 1: Configuration Configuring IP and Ethernet interfaces Attribute Meaning VLAN Aging Timeout Specify how long the AP must keep dynamically learned VIDs. The range of values is 5 to 1440 (minutes). The default value is 25 (minutes). Note VIDs that you enter for the Management VID and VLAN Membership parameters do not time out. Management VID Enter the VID that the operator wishes to use to communicate with the module manager. The range of values is 1 to 4095. The default value is 1. QinQ EtherType Use AP's Management VID for ICC connected SM Modules can be configured with 802.1ad Q-in-Q DVLAN (Double-

VLAN) tagging which is a way for an operator to put an 802.1Q VLAN inside of an 802.1ad VLAN. A nested VLAN, which is the original 802.1Q tag and a new second 802.1ad tag, allows for bridging of VLAN traffic across a network and segregates the broadcast domains of 802.1Q VLANs. Q-in-Q can be used with PPPoE and/or NAT. The 802.1ad standard defines the S-VLAN as the Service Provider VLAN and the C-VLAN as the customer VLAN. The radio software does 2 layer Q-in-Q whereby the C-VLAN is the 802.1Q tag and the S-VLAN is the second layer Q tag as shown below:

Table 14 Q-in-Q Ethernet frame Ethernet Header S-VLAN EthType 0x88a8 C-VLAN EthType 0x8100 IP Data EthType 0x0800 The 802.1ad S-VLAN is the outer VLAN that is configurable on the Configuration > VLAN web page of the AP. The Q-in-Q EtherType parameter is configured with a default EtherType of 0x88a8 in addition to four alternate EtherTypes that can be configured to aid in interoperability with existing networks that use a different EtherType than the default. The C-VLAN is the inner VLAN tag, which is the same as 802.1Q. As a top-

level concept, this operates on the outermost tag at any given time, either pushing a tag on or popping a tag off. This means packets will at most transition from an 802.1Q frame to an 801.ad frame (with a tag pushed on) or an untagged 802.1 frame (with the tag popped off. Similarly, for an 802.1ad frame, this can only transition from an 802.1ad frame to an 802.1Q frame (with the tag popped off) since the radio software only supports 2 levels of tags. This field allows the SM to use the APs management VLAN ID when the SM is registered to the AP via ICC. Page 1-49 Chapter 1: Configuration Configuring IP and Ethernet interfaces VLAN Not Active VLAN Membership Table Configuration When VLAN is enabled in the AP, the Active Configuration block provides the following details as read-only information in this tab. In the Cambium fixed wireless broadband IP network, each device of any type is automatically a permanent member of VID 1. This facilitates deployment of devices that have VLAN enabled with those that do not. For each VLAN in which you want the AP to be a member, enter the VLAN ID and then click the Add Member button. Similarly, for any VLAN in which you want the AP to no longer be a member, enter the VLAN ID and then click the Remove Member button. VLAN Membership table This field lists the VLANs that an AP is a member of. As the user adds a number between 1 and 4094, this number is populated here. Source VLAN (Range:

1-4094) Enter the VID for which the operator wishes to remark the 802.1p priority for the downstream packets. The range of values is 1 to 4094. The default value is 1. Remark Priority

(Range 0-7) This is the priority you can assign to the VLAN Tagged packet. Priority of 0 is the highest. VLAN Remarking table As the user enters a VLAN and a Remarking priority, this information is added in this table. Page 1-50 Chapter 1: Configuration VLAN page of SM The VLAN tab of SM/BHS is explained in Table 15. Table 15 SM VLAN attributes Configuring IP and Ethernet interfaces Page 1-51 Chapter 1: Configuration Configuring IP and Ethernet interfaces Attribute Meaning VLAN Port Type Accept QinQ Frames Allow Frame Types Dynamic Learning By default, this is Q, indicating that it is to operate in the existing manner. The other option is Q-in-Q, which indicates that it must be adding and removing the S-Tag, and adding a C-Tag if necessary for untagged packets. The VLAN Port type corresponds to the Ethernet port of the SM/BHS. Currently, the internal management interfaces will always operate as Q ports. This option is valid for the Q-in-Q port so that the user may force blocking of existing 802.1ad Q-in-Q frames. This way, only untagged or single tagged packets will come in and out of the Ethernet interface. If a Q-in-Q frame is about ingress or egress the Ethernet interface and this is disabled, it is dropped and a filter entry will show up on the VLAN Statistics page as DVLAN Egress or DVLAN Ingress. Select the type of arriving frames that the SM must tag, using the VID that is stored in the Untagged Ingress VID parameter. The default value is All Frames. Tagged Frames Only: The SM only tags incoming VLAN-tagged frames Untagged Frames Only: The SM will only tag incoming untagged frames Specify whether the SM must (Enable) or not (Disable) add the VIDs of upstream frames (that enter the SM through the wired Ethernet interface) to the VID table. The default value is Enable. VLAN Aging Timeout Specify how long the SM/BHS must keep dynamically learned VIDs. The range of values is 5 to 1440 (minutes). The default value is 25 (minutes). Note VIDs that you enter for the Untagged Ingress VID and Management VID parameters do not time out. Management VID Enter the VID that the SM/BHS must share with the AP/BHM. The range of values is 1 to 4095. The default value is 1. Page 1-52 Chapter 1: Configuration Configuring IP and Ethernet interfaces SM Management VID Pass-through Specify whether to allow the SM/BHS (Enabled) or the AP/RADIUS

(Disabled) to control the VLAN settings of this SM. The default value is Enabled. When VLAN is enabled in the AP to whom this SM is registered, the Active Configuration block provides the following details as read-only information in this tab. In the Cambium fixed wireless broadband IP network, each device of any type is automatically a permanent member of VID 1. This facilitates deployment of devices that have VLAN enabled with those that do not. If disabled, MVID traffic is not allowed to or from the SM wired interface. Also, if Management VID is the same as a Port VID (Default or MAC-based), then this setting is ignored and assumed to be Enabled. This is the VID that is used for untagged frames and will correspond to the Q-

Tag for 802.1Q frames (if VLAN Port Type is Q), or the C-Tag for 802.1ad frames (if the VLAN Port Type is Q-in- Q). These parameters allow operators to place specific devices onto different VLANs (802.1Q tag or 802.1ad C-tag) based on the source MAC address of the packet. If the MAC address entry is 00-00-00-00-00-00 then that entry is not used. If a packet arrives at the SM that is sourced from a device whose MAC address is in the table, then the corresponding VID is used for that frames Q-tag (Q port) or C-tag (Q-in-Q port). If there is no match, then the Default Port VID is used. This table is also used in the downstream direction for removal of the tag based on the destination MAC address so that an untagged (for Q port) or Q-Tagged (for Q-in-Q port) frame is delivered to the end device. You may use wildcards for the non-OUI

(Organizationally Unique Identifier) portion of the MAC address, which is the last 3 bytes. MAC addresses contain 6 bytes, the first 3 of which are the OUI of the vendor that manufactured the device and the last 3 are unique to that vendor OUI. If you want to cover all devices from a known vendors OUI, you have to specify 0xFF for the remaining 3 bytes. So, for example, if you wanted all devices from a specific vendor with an OUI of 00-95-5b

(which is a Netgear OUI) to be on the same VID of 800, you have to specify an entry with MAC address 00-95-5b-ff-ff-ff. Then, any device underneath of the SM with MAC addresses starting with 00-95-5b is put on VLAN 800. The provider VID is used for the S-tag. It is only used if the Port Type is Q-

in-Q and will always be used for the S-tag. If an existing 802.1Q frame arrives, the Provider VID is what is used for adding and removing of the outer S-tag. If an untagged frame arrives to a Q-in-Q port, then the Provider VID is the S-tag and the Default Port VID (or Port VID MAC Address Mapping, if valid) is used for the C-tag. Default Port VID Port VID MAC Address Mapping Provider VID Support 802.1p Frames This parameter allows the operator to enable or disable 802.1p frames. When 802.1p feature is enabled on SM, the packets are added with VID=0 and priority bits are set. Page 1-53 Chapter 1: Configuration Configuring IP and Ethernet interfaces Active Configuration, Default Port VID Active Configuration, MAC Address VID Map Active Configuration, Management VID Active Configuration, SM Management VID Pass-Through Active Configuration, Dynamic Aging Timeout This is the value of the parameter of the same name, configured above. This is the listing of the MAC address VIDs configured in Port VID MAC Address Mapping. This is the value of the parameter of the same name, configured above. This is the value of the parameter of the same name, configured above. This is the value of the VLAN Aging Timeout parameter configured above. Active Configuration, Allow Learning Yes is displayed if the value of the Dynamic Learning parameter above is Enabled. No is displayed if the value of Dynamic Learning is Disabled. Active Configuration, Allow Frame Type This displays the selection that was made from the drop-down list at the Allow Frame Types parameter above. Active Configuration, QinQ This is set to Enabled if VLAN Port Type is set to QinQ, and is set to Disabled if VLAN Port Type is set to Q. Active Configuration, QinQ EthType Active Configuration, Allow QinQ Tagged Frames Active Configuration, Current VID Member Set, VID Number Active Configuration, Current VID Member Set, Type This is the value of the QinQ EtherType configured in the AP. This is the value of Accept QinQ Frames, configured above. This column lists the ID numbers of the VLANs in which this module is a member, whether through assignment or through dynamic learning. For each VID number in the first column, the entry in this column correlates the way in which the module became and continues to be a member:

PermanentThis indicates that the module was assigned the VID number through direct configuration by the operator. DynamicThis indicates that the module adopted the VID number through enabled dynamic learning, when a tagged packet from a SM behind it in the network or from a customer equipment that is behind the SM in this case, was read. Active Configuration, Current VID Member Set, Age For each VID number in the first column of the table, the entry in this column reflects whether or when the VID number will time out:

Permanent type - Number never times out and this is indicated by the digit 0. Page 1-54 Chapter 1: Configuration Configuring IP and Ethernet interfaces Dynamic type - Age reflects what is configured in the VLAN Aging Timeout parameter in the Configuration => VLAN tab of the AP or reflects a fewer number of minutes that represents the difference between what was configured and what has elapsed since the VID was learned. Each minute, the Age decreases by one until, at zero, the AP deletes the learned VID, but can it again from packets sent by elements that are beneath it in the network. Note Values in this Active Configuration block can differ from attempted values in configurations:

The AP can override the value that the SM has configured for SM Management VID Pass-Through. IP Lookup Direction This parameter supports following options. Use Source IP: Mapping is done based on the source IP of the incoming packet. Use Destination IP: Mapping is done based on the Destination IP of the incoming packet. IP Address / Subnet Mask This parameter specifies the IP Address and the Subnet Mask which needs to be matched. VID This parameter specifies the VLAN which is tagged to the packet. Priority Mode This parameter specifies the priority precedence to decide if 802.1p or DSCP Priority bits need to be used when making priority decisions. Priority This parameter specifies the 802.1p Priority bits in the VLAN tag. L3 Port VID Map This field displays the Map key, IP address/subnet mask, VID, Priority mode, Priority, and Hash key information of the tagged packets. VLAN Membership tab of SM The Configuration > VLAN > VLAN Membership tab is explained in Table 16. Table 16 SM VLAN Membership attributes Page 1-55 Chapter 1: Configuration Configuring IP and Ethernet interfaces Attribute Meaning VLAN Membership Table Configuration For each VLAN in which you want the AP to be a member, enter the VLAN ID and then click the Add Member button. Similarly, for any VLAN in which you want the AP to no longer be a member, enter the VLAN ID and then click the Remove Member button. VLAN configuration for PTP Applicable products PTP: BHM BMS VLAN page of BHM The VLAN tab of BHS is explained in Table 17. Table 17 BHM VLAN page attributes Attribute VLAN VLAN Port Type Accept QinQ Frames Meaning Specify whether VLAN functionality for the BHM and all linked BHS must be

(Enabled) or may not (Disabled) be allowed. The default value is Disabled. By default, this is Q, indicating that it is to operate in the existing manner. The other option is Q-in-Q, which indicates that it must be adding and removing the S-Tag, and adding a C-Tag if necessary for untagged packets. The VLAN Port type corresponds to the Ethernet port of the BHS. Currently, the internal management interfaces will always operate as Q ports. This option is valid for the Q-in-Q port so that the user may force blocking of existing 802.1ad Q-in-Q frames. This way, only untagged or single tagged packets will come in and out of the Ethernet interface. If a Q-in-Q frame is about ingress or egress the Ethernet interface and this is disabled, it is dropped and a filter entry will show up on the VLAN Statistics page as DVLAN Egress or DVLAN Ingress. Page 1-56 Chapter 1: Configuration Configuring IP and Ethernet interfaces Management VID

(Range 1-4094) Enter the VID that the BHS must share with the BHM. The range of values is 1 to 4095. The default value is 1. Default Port VID

(Range 1-4094) QinQ Ether Type This is the VID that is used for untagged frames and corresponds to the Q-

Tag for 802.1Q frames (if VLAN Port Type is Q), or the C-Tag for 802.1ad frames (if the VLAN Port Type is Q-in- Q). Modules can be configured with 802.1ad Q-in-Q DVLAN (Double-VLAN) tagging which is a way for an operator to put an 802.1Q VLAN inside of an 802.1ad VLAN. A nested VLAN, which is the original 802.1Q tag and a new second 802.1ad tag, allows for bridging of VLAN traffic across a network and segregates the broadcast domains of 802.1Q VLANs. Q-in-Q can be used with PPPoE and/or NAT. The 802.1ad standard defines the S-VLAN as the Service Provider VLAN and the C-VLAN as the customer VLAN. The radio software does 2-layer Q-in-Q whereby the C-VLAN is the 802.1Q tag and the S-VLAN is the second layer Q tag as shown below:

Ethernet Header S-VLAN EthType 0x88a8 C-VLAN EthType 0x8100 IP Data EthType 0x0800 The 802.1ad S-VLAN is the outer VLAN that is configurable on the Configuration > VLAN web page of the BHM. The Q-in-Q EtherType parameter is configured with a default EtherType of 0x88a8 in addition to four alternate EtherTypes that can be configured to aid in interoperability with existing networks that use a different EtherType than the default. The C-VLAN is the inner VLAN tag, which is the same as 802.1Q. As a top-

level concept, this operates on the outermost tag at any given time, either pushing a tag on or popping a tag off. This means packets will at most transition from an 802.1Q frame to an 801.ad frame (with a tag pushed on) or an untagged 802.1 frame (with the tag popped off. Similarly, for an 802.1ad frame, this can only transition from an 802.1ad frame to an 802.1Q frame (with the tag popped off) since the radio software only supports 2 levels of tags. When VLAN is enabled in the BHM, the Active Configuration block provides the following details as read-only information in this tab. In the Cambium fixed wireless broadband IP network, each device of any type is automatically a permanent member of VID 1. This facilitates deployment of devices that have VLAN enabled with those that do not. VLAN Not Active Page 1-57 Chapter 1: Configuration VLAN page of BHS The VLAN tab of BHS is explained in Table 18. Table 18 BHS VLAN page attributes Configuring IP and Ethernet interfaces Attribute VLAN VLAN Port Type Accept QinQ Frames Meaning Specify whether VLAN functionality for the BHM and all linked BHS must be

(Enabled) or may not (Disabled) be allowed. The default value is Disabled. By default, this is Q, indicating that it is to operate in the existing manner. The other option is Q-in-Q, which indicates that it must be adding and removing the S-Tag, and adding a C-Tag if necessary for untagged packets. The VLAN Port type corresponds to the Ethernet port of the BHS. Currently, the internal management interfaces will always operate as Q ports. This option is valid for the Q-in-Q port so that the user may force blocking of existing 802.1ad Q-in-Q frames. This way, only untagged or single tagged packets will come in and out of the Ethernet interface. If a Q-in-Q frame is about ingress or egress the Ethernet interface and this is disabled, it is dropped and a filter entry will show up on the VLAN Statistics page as DVLAN Egress or DVLAN Ingress. Management VID

(Range 1-4094) Enter the VID that the BHS must share with the BHM. The range of values is 1 to 4095. The default value is 1. Default Port VID

(Range 1-4094) VLAN Not Active This is the VID that is used for untagged frames and corresponds to the Q-

Tag for 802.1Q frames (if VLAN Port Type is Q), or the C-Tag for 802.1ad frames (if the VLAN Port Type is Q-in- Q). When VLAN is enabled in the BHM, the Active Configuration block provides the following details as read-only information in this tab. In the Cambium fixed wireless broadband IP network, each device of any type is automatically a permanent member of VID 1. This facilitates deployment of devices that have VLAN enabled with those that do not. Page 1-58 Chapter 1: Configuration PPPoE page of SM Configuring IP and Ethernet interfaces Applicable products PMP:

SM Point-to-Point Protocol over Ethernet (PPPoE) is a protocol that encapsulates PPP frames inside Ethernet frames (at Ethernet speeds). Benefits to the network operator may include Access control Service monitoring Generation of statistics about activities of the customer Re-use of infrastructure and operational practices by operators who already use PPP for other networks PPPoE options are configurable for the SM only, and the AP indicates whether or not PPPoE is enabled for a specific subscriber. When PPPoE is enabled, once the RF session comes up between the SM and the AP, the SM will immediately attempt to connect to the PPPoE Server. You can monitor the status of this by viewing the PPPoE Session Log in the Logs section (Administrator only). Every time the RF session comes up, the SM will check the status of the link and if it is down, the SM will attempt to redial the link if necessary depending on the Timer Type. Also, on the Configuration page, the user may Connect or Disconnect the session manually. This can be used to override the session to force a manual disconnect and/or reconnect if there is a problem with the session. In order to enable PPPoE, NAT MUST be enabled on the SM and Translation Bridging MUST be disabled on the AP. These items are strictly enforced for you when you are trying to enable PPPoE. A message will indicate any prerequisites not being met. Also, the NAT Public IP DHCP client cannot be enabled, because the NAT Public IP is received through the IPCP process of the PPPoE discovery stages. The pre-requisites are:

NAT MUST be enabled on the SM o NAT DHCP Client is disabled automatically. The NAT public IP is received from the PPPoE Server. o NAT Public Network Interface Configuration will not be used and must be left to defaults. Also NAT Public IP DHCP is disabled if it is enabled. Translation Bridging MUST be DISABLED on the AP o This will only be determined if the SM is in session since the SM wont know the AP configuration otherwise. If the SM is not in session, PPPoE can be enabled but if the SM goes into session to a Translation Bridge-enabled AP, then PPPoE will not be enabled. The PPPoE configuration parameters are explained in Table 19. Page 1-59 Chapter 1: Configuration Table 19 SM PPPoE attributes Configuring IP and Ethernet interfaces Attribute Meaning Access Concentrator Service Name An optional entry to set a specific access concentrator to connect to for the PPPoE session. If this is blank, the SM will accept the first access concentrator which matches the service name (if specified). This is limited to 32 characters. An optional entry to set a specific service name to connect to for the PPPoE session. If this is left blank the SM will accept the first service option that comes back from the access concentrator specified above, if any. This is limited to 32 characters. Authentication Type None means that no PPPoE authentication is implemented User Name Password MTU CHAP/PAP means that CHAP authentication is attempted first, then PAP authentication. The same password is used for both types. This is the CHAP/PAP user name that is used if CHAP/PAP authentication is selected. If None is selected for authentication, then this field is unused. This is limited to 32 characters. This is the CHAP/PAP password that is used if PAP authentication is selected. If None is selected for authentication, then this field is unused. This is limited to 32 characters. Use MTU Received from PPPoE Server causes the SM to use the MRU of the PPPoE server received in LCP as the MTU for the PPPoE link. Page 1-60 Chapter 1: Configuration Configuring IP and Ethernet interfaces Timer Type Use User Defined MTU allows the operator to specify an MTU value to use to override any MTU that may be determined in the LCP phase of PPPoE session setup. If this is selected, the user is able to enter an MTU value up to 1492. However, if the MTU determined in LCP negotiations is less than this user-specified value, the SM will use the smaller value as its MTU for the PPPoE link. Keep Alive is the default timer type. This timer will enable a keepalive that will check the status of the link periodically. The user can set a keepalive period. If no data is seen from the PPPoE server for that period, the link is taken down and a reconnection attempt is started. For marginal links, the keep alive timer can be useful so that the session will stay alive over periodic dropouts. The keepalive timer must be set such that the session can outlast any session drop. Some PPPoE servers will have a session check timer of their own so that the timeouts of the server and the SM are in sync, to ensure one side does not drop the session prematurely. Idle Timeout enables an idle timer that checks the usage of the link from the customer side. If there is no data seen from the customer for the idle timeout period, the PPPoE session is dropped. Once data starts flowing from the customer again, the session is started up again. This timer is useful for users who may not be using the connection frequently. If the session is idle for long periods of time, this timer will allow the resources used by the session to be returned to the server. Once the connection is used again by the customer, the link is reestablished automatically. Timer Period The length in seconds of the PPPoE keepalive timer. TCP MSS Clamping If this is enabled, then the SM will alter TCP SYN and SYN-ACK packets by changing the Maximum Segment Size to be compatible with the current MTU of the PPPoE link. This way, the user does not have to worry about MTU on the client side for TCP packets. The MSS is set to the current MTU 40

(20 bytes for IP headers and 20 bytes for TCP headers). This will cause the application on the client side to not send any TCP packets larger than the MTU. If the network is exhibiting large packet loss, try enabling this option. This may not be an option on the PPPoE server itself. The SM will NOT reassemble IP fragments, so if the MTUs are incorrect on the end stations, then MSS clamping will solve the problem for TCP connections. Page 1-61 Chapter 1: Configuration Configuring IP and Ethernet interfaces IP4 and IPv6 Applicable products PMP: AP SM PTP: BHM BMS IPv4 and IPv6 Prioritization 450 Platform Family provides operators the ability to prioritize IPv6 traffic in addition to IPv4 traffic. IPv6/IPv4 prioritization can be configured by selecting a CodePoint and the corresponding priority from the GUI of the AP/BHM and the IPv6/IPv4 packet is set up accordingly. There is no GUI option for selecting IPv6 or IPv4 priority. Once the priority is set, it is set for IPv4 and IPv6 packets. Configuring IPv4 and IPv6 Priority IPv4 and IPv6 prioritization is set using the DiffServ tab on the AP/BHM and SM/BHS

(located at Configuration > DiffServ). A priority set to a specific CodePoint will apply to both IPv4 and IPv6 traffic. Table 20 DiffServ attributes AP/BHM Page 1-62 Chapter 1: Configuration Configuring IP and Ethernet interfaces Attribute Meaning Codepoints 1 through 63 The PMP family of APs support four levels of QoS. The mapping of these eight priority values to data channels is determined by the number of data channels configured per SM as shown in the table below:

For example, for an AP that uses the default table shown above has configured 3 QoS levels per SM, would see codepoints 0 through 15 mapped to the Low Priority data channels, codepoint 16 would be mapped to the Medium Priority data channels, and so on. Note that CodePoints 0, 8, 16, 24, 32, 48, and 56 are predefined to the fixed values shown in Table 20 above and are not user configurable. Operator cannot change any of these three fixed priority values. Among the configurable parameters, the priority values (and therefore the handling of packets in the high or low priority channel) are set in the AP/BHM for all downlinks within the sector and in the SM/BHS for each uplink. CodePoint Select This represents the CodePoint Selection to be modified via Priority Select. Priority Select The priority setting input for the CodePoint selected in CodePoint Select. Priority Precedence Allows operator to decide if 802.1p or DiffServ priority bits must be used first when making priority decisions. PPPoE Control Message Priority Operators may configure the AP/BHM to utilize the high priority channel for PPPoE control messages. Configuring the AP/BHM in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the AP/BHM. MPLS Traffic Class

(TC) 0 through MPLS Traffic Class (TC) 7 The Multi-Protocol Label Switching (MPLS) protocol is used to route traffic based on the priority setting configured each MPLS Traffic Class. MPLS Traffic Class (TC) 0 through MPLS Traffic Class (TC) 7 can be configured with 0 through 7 priority settings. IPv4 and IPv6 Filtering The operator can filter (block) specified IPv6 protocols including IPv4 and ports from leaving the AP/BHM and SM/BHS and entering the network. This protects the network from both intended and inadvertent packet loading or probing by network users. By keeping the specified protocols or ports off the network, this feature also provides a level of protection to users from each other. Page 1-63 Chapter 1: Configuration Configuring IP and Ethernet interfaces Configuring IPv4 and IPv6 Filtering IPv6 filters are set using the Protocol Filtering tab on the AP/BHM and SM/BHS (at Configuration >

Protocol Filtering). Once a filter is set for a packet type, those packets will not be sent over the RF interface depending on Filter Direction setting. Page 1-64 Chapter 1: Configuration Configuring IP and Ethernet interfaces Table 21 Packet Filter Configuration attributes Attribute Meaning Packet Filter Types For any box selected, the Protocol and Port Filtering feature blocks the associated protocol type. To filter packets in any of the user-defined ports, you must do all of the following:

Check the box for User Defined Port n (See Below) in the Packet Filter Types section of this tab. Provide a port number at Port #n. in the User Defined Port Filtering Configuration section of this tab Page 1-65 Chapter 1: Configuration Configuring IP and Ethernet interfaces Enable TCP and/or UDP by clicking the associated radio button Filter Direction Operators may choose to filter upstream (uplink) RF packets or downstream (downlink) RF packets. User Defined Port Filtering Configuration You can specify ports for which to block subscriber access, regardless of whether NAT is enabled. Page 1-66 Chapter 1: Configuration Upgrading the software version and using CNUT Upgrading the software version and using CNUT This section consists of the following procedures:

Checking the installed software version on page 1-67 Upgrading to a new software version on page 1-67 Caution If the link is operational, ensure that the remote end of the link is upgraded first using the wireless connection, and then the local end can be upgraded. Otherwise, the remote end may not be accessible. Use CNUT 4.11.2 or later version and always refer to the software release notes before upgrading system software. The release notes are available at:

https://support.cambiumnetworks.com/files/pmp450 https://support.cambiumnetworks.com/files/ptp450 Checking the installed software version To check the installed software version, follow these instructions:

Procedure 10 Checking the installed software version 1 2 3 4 Click on General tab under Home menu. Note the installed Software Version (under Device Information):

PMP/PTP 450/450i/450m Go to the support website (see Contacting Cambium Networks on page 1) and find Point-to-

Multipoint software updates. Check that the latest 450 Platform Family software version is the same as the installed Software Version. To upgrade software to the latest version, see Upgrading to a new software version on page 1-67. Upgrading to a new software version All 450 platform modules are upgraded using the Canopy Network Updater Tool. The Canopy Network Updater Tool (CNUT) manages and automates the software upgrade process for a Canopy radio, or CMM4 (but not its 14-port switch) across the network. This eliminates the need for an administrator to visit each radio in the network (or each AP/BHM while using the Auto update feature) to upgrade the modules. Page 1-67 Chapter 1: Configuration Upgrading the software version and using CNUT Note Please ensure that you have the most up-to-date version of CNUT by browsing to the Customer Support Web Page located:

https://www.cambiumnetworks.com/products/software-tools/cambium-network-

updater-tool/

This section includes an example of updating a single unit before deployment. System-wide upgrading procedures may be found in the CNUT Online Help manual, which can be found on the Cambium support website (see Contacting Cambium Networks on page 1). CNUT functions The Canopy Network Updater tool has the following functions:

Automatically discovers all network elements Executes a UDP command that initiates and terminates the Auto-update mode within APs/BHMs. This command is both secure and convenient:

o For security, the AP/BHM accepts this command from only the IP address that you specify in the Configuration page of the AP/BHM. o For convenience, Network Updater automatically sets this Configuration parameter in the APs/BHMs to the IP address of the Network Updater server when the server performs any of the update commands. CNUT supports HTTP and HTTPS Allows you to choose the following among updating:

o Your entire network. o Only elements that you select. o Only network branches that you select. Provides a Script Engine that you can use with any script that:

o You define. o Cambium supplies. Configurability of any of the following to be the file server for image files:

o The AP/BHM, for traditional file serving via UDP commands and monitoring via UDP messaging o CNUT HTTP/HTTPS Server, for upgrading via SNMP commands and monitoring via SNMP messaging. This also supports an option to either set the image order specifically for this file server or to allow the AP to determine the order. o Local TFTP Server, for traditional file serving via UDP commands and monitoring via UDP messaging. This supports setting the number of simultaneous image transfers per AP/BHM The capability to launch a test of connectivity and operational status of the local HTTP, HTTPS and TFTP file servers An interface that supports efficient specification of the proper IP address for the local file server(s) where Network Updater resides on a multi-homed computer Page 1-68 Chapter 1: Configuration Upgrading the software version and using CNUT An md5 checksum calculator utility for identifying corruption of downloaded image files before Network Updater is set to apply them. Network element groups With the Canopy Network Updater Tool, you can identify element groups composed of network elements that you select. Identifying these element groups does the following:

Organizes the display of elements (for example, by region or by AP/BHM cluster). Allows to:

o Perform an operation on all elements in the group simultaneously. o Set group-level defaults for ftp password access and SNMP Community String

(defaults that can be overridden in an individual element when necessary). Network layers A typical network contains multiple layers of elements, with each layer farther from the Point of Presence. For example, SMs (or BHS) are behind an AP/BHM and thus, in this context, at a lower layer than the AP/BHM. Correctly portraying these layers in Network Updater is essential so that Network Updater can perform radio and AP/BHM cluster upgrades in an appropriate order. Script engine Script Engine is the capability in Network Updater that executes any user-defined script against any network element or element group. This capability is useful for network management, especially for scripts that you repetitively execute across your network. The Autodiscovery capability in Network Updater finds all of your network elements. This comprehensive discovery:

Ensures that, when you intend to execute a script against all elements, the script is indeed executed against all elements. Maintains master lists of elements (element groups) against which you selectively execute scripts. The following scripts are included with CNUT:

Gather Customer Support Information Set Access Point Authentication Mode Set Autoupdate Address on APs/BHMs Set SNMP Accessibility Reset Unit Page 1-69 Chapter 1: Configuration Upgrading the software version and using CNUT Software dependencies for CNUT CNUT functionality requires one of the following operating systems o Windows 2000 o Windows Server 2003 o Windows 7 and Windows 8 o Windows XP or XP Professional o Red Hat Enterprise Linux (32-bit) Version 4 or 5 Java Runtime Version 2.0 or later (installed by the CNUT installation tool) CNUT download CNUT can be downloaded together with each system release that supports CNUT. Software for these system releases is available from https://www.cambiumnetworks.com/products/software-

tools/cambium-network-updater-tool/, as either:

A .zip file for use without the CNUT application. A .pkg file that the CNUT application can open. Upgrading a module prior to deployment To upgrade to a new software version, follow this:

Procedure 11 Upgrading a module prior to deployment 1 2 3 4 5 6 7 8 Go to the support website (see Contacting Cambium Networks on page 1) and find Point-to-

Multipoint software updates. Download and save the required software image. Start CNUT If you dont start up with a blank new network file in CNUT, then open a new network file with the New Network Archive operation (located at File > New Network). Enter a new network element to the empty network tree using the Add Elements to Network Root operation (located at Edit > Add Elements to Network Root). In the Add Elements dialogue, select a type of Access Point or Subscriber Module and enter the IP address of 169.254.1.1. Make sure that the proper Installation Package is active with the Package Manager dialogue

(located at Update > Manage Packages). To verify connectivity with the radio, perform a Refresh, Discover Entire Network operation

(located at View > Refresh/Discover Entire Network). You must see the details columns for the new element filled in with ESN and software version information. Initiate the upgrade of the radio using Update Entire Network Root operation (located at Update > Update Entire Network Root). When this operation finishes, the radio is done being upgraded. Page 1-70 Chapter 1: Configuration General configuration General configuration The Configuration > General page of the AP/BMH or BHM/BHS contains many of the configurable parameters that define how the ratios operate in sector or backhaul. Applicable products PMP: AP SM PTP: BHM BMS PMP 450m and PMP/PTP 450i Series General page - PMP 450i AP The General page of AP is explained in Table 22. Table 22 General page attributes PMP 450i AP Page 1-71 Chapter 1: Configuration General configuration Attribute Meaning Ethernet Port Selection Link Speeds Ethernet Port selection is applicable to the 450m platform only with two choices in the drop-down list:

Main: A selection of main indicates that link connectivity and power to the 450m is provided through the RF45 connection on the Main port of the AP SFP: A selection of SFP indicates that link connectivity will be provided through the SFP port on the 450m Power continues to be provided via the RJ45 Main port From the drop-down list of options, select the type of link speed for the Ethernet connection. The Auto settings allow the two ends of the link to automatically negotiate with each other the best possible speed, and check whether the Ethernet traffic is full duplex or half duplex. However, some Ethernet links work best when either:

both ends are set to the same forced selection both ends are set to auto-negotiate and both have capability in least one common speed and traffic type combination. Ethernet Link This parameter allows the operator to enable or disable Ethernet Link. Ethernet Bounce Timeout This parameter allows the operator to configure Ethernet bouce timeout ranging from 0 to 60 minutes. Value 0 disables Ethernet bounce timeout. 802.3at Type 2 PoE Status and When the PoE Classification functionality is enabled and if Type 2 power is not present, the PAs do not power up and draw too much power. By default, the PoE Classification feature is disabled and the PAs will power up regardless of the classification presented by the power source. Page 1-72 Chapter 1: Configuration General configuration PoE Classification

(PMP 450i Series only) This is supported only on 450i series devices. PoE Classification configuration status also can be check under home >

General > Device Information tab:

Configuration Source See Setting the Configuration Source on page 1-246. Sync Input See Configuring synchronization on page 1-105 Free Run Before GPS Sync Region Country See Configuring synchronization on page 1-107 From the drop-down list, select the region in which the radio is operating. From the drop-down list, select the country in which the radio is operating. Unlike selections in other parameters, your Country selection requires a Save Changes and a Reboot cycle before it will force the context-sensitive GUI to display related options (for example, Alternate Frequency Carrier 1 and 2 in the Configuration > Radio tab). PMP 450i Series ODUs shipped to the United States is locked to a Region Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. Country Code settings affect the radios in the following ways:

Maximum transmit power limiting (based on radio transmitter power plus configured antenna gain) DFS operation is enabled based on the configured region code, if applicable For more information on how transmit power limiting and DFS is implemented for each country, see the PMP 450 Planning Guide. Webpage Auto Update Enter the frequency (in seconds) for the web browser to automatically refresh the web-based interface. The default setting is 0. The 0 setting causes the web-based interface to never be automatically refreshed. Bridge Entry Timeout Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Caution An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. Page 1-73 Chapter 1: Configuration General configuration Translation Bridging Optionally, you can configure the AP to change the source MAC address in every packet it receives from its SMs to the MAC address of the SM that bridged the packet, before forwarding the packet toward the public network. If you do, then:

Not more than 128 IP devices at any time are valid to send data to the AP from behind the SM. SM populates the Translation Table tab of its Statistics web page, displaying the MAC address and IP address of all the valid connected devices. Each entry in the Translation Table is associated with the number of minutes that have elapsed since the last packet transfer between the connected device and the SM. If 128 are connected and another attempts to connect:

If no Translation Table entry is older than 255 minutes, the attempt is ignored. If an entry is older than 255 minutes, the oldest entry is removed and the attempt is successful. The Send Untranslated ARP parameter in the General tab of the Configuration page can be:

Disabled, so that the AP overwrites the MAC address in Address Resolution Protocol (ARP) packets before forwarding them. Enabled, so that the AP forwards ARP packets regardless of whether it has overwritten the MAC address. When this feature is disabled, the setting of the Send Untranslated ARP parameter has no effect, because all packets are forwarded untranslated

(with the source MAC address intact). Send Untranslated ARP If the Translation Bridging parameter is set to Enabled, then the Send Untranslated ARP parameter can be:

SM Isolation Disabled - so that the AP will overwrite the MAC address in Address Resolution Protocol (ARP) packets before forwarding them. Enabled - so that the AP will forward ARP packets regardless of whether it has overwritten the MAC address. If the Translation Bridging parameter is set to Disabled, then the Send Untranslated ARP parameter has no effect. Prevent or allow SM-to-SM communication by selecting from the following drop-down menu items:

Disable SM Isolation (the default selection). This allows full communication between SMs. Block SM Packets from being forwarded - This prevents both multicast/broadcast and unicast SM-to-SM communication. Page 1-74 Chapter 1: Configuration General configuration Forward Unknown Unicast Packets Block and Forward SM Packets to Backbone - This not only prevents multicast/broadcast and unicast SM-to-SM communication but also sends the packets, which otherwise are handled SM to SM, through the Ethernet port of the AP. Enabled: All unknown Unicast packets (no entry in the APs bridge table) received via the APs Ethernet LAN interface are forwarded to registered SMs. If the target device is situated beneath a particular SM, when the device responds the SM and AP will learn and add the device to their bridge tables so that subsequent packets to that device is bridged to the proper SM. Disabled: All unknown Unicast packets (no entry in the APs bridge table) received via the APs Ethernet LAN interface are discarded at the AP. Update Application Address Enter the address of the server to access for software updates on this AP and registered SMs. Prioritize TCP ACK Multicast Destination Address DHCP Relay Agent To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. This parameter, when enabled, can be particularly useful when running bi-direction FTP sessions over the link. If a link is primarily used for video surveillance, it is recommended to set this parameter to Disable. Using Link Layer Discovery Protocol (LLDP), a module exchanges multicast addresses with the device to which it is wired on the Ethernet interface. Although some switches (CMM4, for example) do not pass LLDP addresses upward in the network, a radio can pass it as the value of the Multicast Destination Address parameter value in the connected device that has it populated. The AP may act as a DHCP relay for SMs and CPEs underneath it. The AP will make use of the DHCP Option 82 (DHCP Relay Agent Information) from RFC 3046 when performing relay functions. The AP offers two types of DHCP relay functionality:

Full Relay Information - Configuring the DHCP Full Relay Operation will take broadcast DHCP packets and send them to a Unicast server in unicast mode. This way the DHCP requests and replies can be routed like any other UDP packet. Only Insert Option 82 - This option leaves the DHCP request on its broadcast domain as opposed to DHCP Full Relay Operation which will turn it into a unicast packet. In order to accommodate setting up pools or classes for different VLANs, the Option 82 field will include information to tell the server what VLAN the client is on. Page 1-75 Chapter 1: Configuration General configuration DHCP Server (Name or IP Address) Option 82 Circuit ID Option 82 Remote ID The DHCP relay server may be either a DNS name or a static IP address in dotted decimal notation. Additionally, the management DNS domain name may be toggled such that the name of the DHCP relay server only needs to be specified and the DNS domain name is automatically appended to that name. The default DHCP relay server addresses are 255.255.255.255 with the appending of the DNS domain name disabled. This parameter specifies the Circuit ID for DHCP Relay Option 82 data. Following wildcards are supported:

$apmac$ - AP MAC adddress in ascii format, no delimiters

$apmacbi$ - AP MAC address in hex format (6 bytes)

$smmac$ - SM MAC adddress in ascii format, no delimiters

$smmacbi$ - SM MAC address in hex format (6 bytes)

$apsn$ - AP Site Name (may be truncated to 32 chars)

$smsn$ - SM Site Name (may be truncated to 32 chars)

$smvid$ - SM Port VID in ascii format, leading 0 included, 4 chars long

$smvidbi$ - SM Port VID in hex format (2 bytes)

$smluid$ - SM LUID Default value is $apmacbi$

Note: Overall expanded Option 82 data is limited to 255 bytes. This parameter specifies the Remote ID for DHCP Relay Option 82 data. Following wildcards are supported:

$apmac$ - AP MAC adddress in ascii format, no delimiters

$apmacbi$ - AP MAC address in hex format (6 bytes)

$smmac$ - SM MAC adddress in ascii format, no delimiters

$smmacbi$ - SM MAC address in hex format (6 bytes)

$apsn$ - AP Site Name (may be truncated to 32 chars)

$smsn$ - SM Site Name (may be truncated to 32 chars)

$smvid$ - SM Port VID in ascii format, leading 0 included, 4 chars long

$smvidbi$ - SM Port VID in hex format (2 bytes)

$smluid$ - SM LUID Default value is $smmacbi$

Note: Overall expanded Option 82 data is limited to 255 bytes. Option 82 Vendor Specific ID This parameter specifies the Vendor Specific ID for DHCP Relay Option 82 data. Following wildcards are supported:

$apmac$ - AP MAC adddress in ascii format, no delimiters

$apmacbi$ - AP MAC address in hex format (6 bytes)

$smmac$ - SM MAC adddress in ascii format, no delimiters

$smmacbi$ - SM MAC address in hex format (6 bytes) Page 1-76 Chapter 1: Configuration General configuration Latitude Longitude Height

$apsn$ - AP Site Name (may be truncated to 32 chars)

$smsn$ - SM Site Name (may be truncated to 32 chars)

$smvid$ - SM Port VID in ascii format, leading 0 included, 4 chars long

$smvidbi$ - SM Port VID in hex format (2 bytes)

$smluid$ - SM LUID Default value is $smvidbi$

Note: Overall expanded Option 82 data is limited to 255 bytes. Physical radio location data may be configured via the Latitude, Longitude and Height fields. Latitude and Longitude is measured in Decimal Degree while the Height is calculated in Meters. General page - PMP 450m AP The General page of AP is explained in Table 23. Table 23 General page attributes PMP 450m AP Page 1-77 Chapter 1: Configuration General configuration Attribute Trial Mode Meaning This parameter allows to enable or disable Trial mode for radios with a Limited key. Once the trial key is applied, the 30-day trial can be enabled or disabled at any time. For information about remaining attributes, refer Table 22. Page 1-78 Chapter 1: Configuration General configuration General page - PMP 450i SM The General page of PMP 450i SM is explained in Table 24. The General page of PMP 450 SM looks the same as PMP 450i SM. Table 24 General page attributes PMP 450i SM Attribute Link Speeds 802.3at Type 2 PoE Status and PoE Classification Meaning From the drop-down list of options, select the type of link speed for the Ethernet connection. The default for this parameter is that all speeds are selected. The recommended setting is a single speed selection for all APs and SMs in the operator network. When the PoE Classification functionality is enabled and if Type 2 power is not present, the Pas do not power up and draw too much power. By default, the PoE Classification feature is disabled, and the Pas will power up regardless of the classification presented by the power source. This is supported only on 450i series ODUs. Page 1-79 Chapter 1: Configuration General configuration Ethernet Link Enable/Disable PoE Classification configuration status also can be check under home

> General > Device Information tab:

Specify whether to enable or disable Ethernet/802.3 connectivity on the wired port of the SM. This parameter has no effect on the wireless link. When you select Enable, this feature allows traffic on the Ethernet/802.3 port. This is the factory default state of the port. When you select Disable, this feature prevents traffic on the port. Typical cases of when you may want to select Disable include:

The subscriber is delinquent with payment(s). You suspect that the subscriber is sending or flooding undesired broadcast packets into the network, such as when a virus is present in the subscribers computing device. the subscribers home router is improperly configured. Region This parameter allows you to set the region in which the radio will operate. The SM radio automatically inherits the Region type of the master. This behavior ignores the value of the Region parameter in the SM, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. This parameter allows you to set the country in which the radio will operate. The SM radio automatically inherits the Country Code type of the master. This behavior ignores the value of the Country parameter in the SM, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. PMP/PTP 450i Series ODU shipped to the United States is locked to a Region Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. See Table 22 General page attributes PMP 450i AP on page 1-71 Country Webpage Auto Update Show Idle Sessions This parameter allows to enable or disable displaying idle sessions. Bridge Entry Timeout Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. Timeout occurs when the AP encounters no activity with the SM (whose MAC address is the bridge entry) within the interval that this parameter specifies. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Page 1-80 Chapter 1: Configuration General configuration Caution This parameter governs the timeout interval, even if a router in the system has a longer timeout interval. The default value of this field is 25 (minutes). An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. Bridge Table Size This parameter allows to restrict devices to connect to the SM. It is configurable from 4 to 4096. Note Configure Bridge Table Restriction parameter to Drop packets if MAC address is not in bridge table option to restrict the number of devices configured from connecting to SM. Bridge Table Restriction This parameter allows to either allow or restrict devices to connect to SM using the following options:

Drop packets if MAC address is not in bridge table: Select this option to restrict communication from devices not listed in bridge table. Forward packets even if MAC address is not in bridge table: Select this option to allow communication from any device. Frame Timing Pulse Gated If this SM extends the sync pulse to a BH master or an AP, select either EnableIf this SM loses sync from the AP, then do not propagate a sync pulse to the BH timing master or another AP. This setting prevents interference in the event that the SM loses sync. Multicast Destination Address DisableIf this SM loses sync from the AP, then propagate the sync pulse to the BH timing master or another AP. Using Link Layer Discovery Protocol (LLDP), a module exchanges multicast addresses with the device to which it is wired on the Ethernet interface. Although some switches (CMM4, for example) do not pass LLDP addresses upward in the network, a radio can pass it as the value of the Multicast Destination Address parameter value in the connected device that has it populated. Coordinates Physical radio location data may be configured via the Latitude, Longitude and Height fields. Page 1-81 Chapter 1: Configuration General configuration General page - PTP 450i BHM The General page of BHM is explained in Table 25. The General page of PTP 450 BHM looks the same as PTP 450i BHM. Table 25 General page attributes PTP 450i BHM Page 1-82 Chapter 1: Configuration General configuration Attribute Timing Mode Meaning Allows the user to choose the mode between Timing Master and Timing Slave. Link Speed See Table 22 General page attributes PMP 450i AP on page 1-71 802.3at Type 2 PoE Status and PoE Classification When the PoE Classification functionality is enabled and if Type 2 power is not present, the PAs do not power up and draw too much power. By default, the PoE Classification feature is disabled and the PAs will power up regardless of the classification presented by the power source. This is supported only on 450i Series ODUs. PoE Classification configuration status also can be check under home >

General > Device Information tab:

Sync Input See Configuring synchronization on page 1-105 Free Run Before GPS Sync Region Country Webpage Auto Update Bridge Entry Timeout Bridging Functionality Prioritize TCP ACK Multicast Destination Address See Configuring synchronization on page 1-107 See Table 22 General page attributes PMP 450i AP on page 1-71 Select whether you want bridge table filtering active (Enable) or not

(Disable) on this BH. Disable: allows user to use redundant BHs without causing network addressing problems. Through a spanning tree protocol, this reduces the convergence time from 25 minutes to few seconds. However, you must disable bridge table filtering as only a deliberate part of your overall network design since disabling it allows unwanted traffic across the wireless interface. Enable: Allows user to enable bridge functionality. Note Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. See Table 22 General page attributes PMP 450i AP on page 1-71 Page 1-83 Chapter 1: Configuration General configuration Latitude Longitude Height General page - PTP 450i BHS The General page of PTP 450i BHS is explained in Table 26. The General page of PTP 450 BHS looks the same as PTP 450i BHS. Table 26 General page attributes PTP 450i BHS Page 1-84 Chapter 1: Configuration General configuration Attribute Meaning Timing Mode Link Speed 802.3at Type 2 PoE Status and PoE Classification Allows the user to choose the mode between Timing Master and Timing Slave. From the drop-down list of options, select the type of link speed for the Ethernet connection. The default for this parameter is that all speeds are selected. The recommended setting is a single speed selection for all BHMs and BHSs in the operator network. When the PoE Classification functionality is enabled and if Type 2 power is not present, the PAs do not power up and draw too much power. By default, the PoE Classification feature is disabled and the PAs will power up regardless of the classification presented by the power source. This is supported only on 450i Series ODUs. PoE Classification configuration status also can be check under home

> General > Device Information tab:

Region This parameter allows you to set the region in which the radio will operate. Country Webpage Auto Update Bridge Entry Timeout The BHS radio automatically inherits the Region type of the master. This behavior ignores the value of the Region parameter in the BHS, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. This parameter allows you to set the country in which the radio will operate. The BHS radio automatically inherits the Country Code type of the master. This behavior ignores the value of the Country parameter in the BHS, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. PMP/PTP 450i Series ODU shipped to the United States is locked to a Region Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. See Table 22 General page attributes PMP 450i AP on page 1-71 Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. Timeout occurs when the BHM encounters no activity with the BHS (whose MAC address is the bridge entry) within the interval that this parameter specifies. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Page 1-85 Chapter 1: Configuration General configuration Caution This parameter governs the timeout interval, even if a router in the system has a longer timeout interval. The default value of this field is 25 (minutes). An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. Bridging Functionality See Table 22 General page attributes PMP 450i AP on page 1-71 Frame Timing Pulse Gated Multicast Destination Address Latitude Longitude Height If this BHS extends the sync pulse to a BH master or an BHM, select either EnableIf this BHS loses sync from the BHM, then do not propagate a sync pulse to the BH timing master or other BHM. This setting prevents interference in the event that the BHS loses sync. DisableIf this BHS loses sync from the BHM, then propagate the sync pulse to the BH timing master or other BHM. See Table 22 General page attributes PMP 450i AP on page 1-71 See Table 22 General page attributes PMP 450i AP on page 1-71 Page 1-86 Chapter 1: Configuration General configuration General page PMP 450b SM The General page of PMP 450b SM is explained in Table 27. The General page of PMP 450b SM looks the same as PMP 450i SM. Table 27 General page attributes PMP 450b SM Page 1-87 Chapter 1: Configuration General configuration Attribute Link Mode Meaning Multipoint: Select this option to configure the device as a multipoint SM. Backhaul: Select this option to configure the device as a Backhaul. Timing Mode Timing Master: Select this option when Link Mode parameter is set to Link Speed Ethernet Link Enabled/Disabled Backhaul. Timing Slave: Select this option when Link Mode parameter is set to Multipoint. From the drop-down list of options, select the type of link speed for the Ethernet connection. The default for this parameter is that all speeds are selected. The recommended setting is a single speed selection for all APs and SMs in the operator network. Specify whether to enable or disable Ethernet/802.3 connectivity on the wired port of the SM. This parameter has no effect on the wireless link. When you select Enable, this feature allows traffic on the Ethernet/802.3 port. This is the factory default state of the port. When you select Disable, this feature prevents traffic on the port. Typical cases of when you may want to select Disable include:

The subscriber is delinquent with payment(s). You suspect that the subscriber is sending or flooding undesired broadcast packets into the network, such as when a virus is present in the subscribers computing device. the subscribers home router is improperly configured. Region This parameter allows you to set the region in which the radio will operate. The SM radio automatically inherits the Region type of the master. This behavior ignores the value of the Region parameter in the SM, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. Country This parameter allows you to set the country in which the radio will operate. The SM radio automatically inherits the Country Code type of the master. This behavior ignores the value of the Country parameter in the SM, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. PMP/PTP 450i Series ODU shipped to the United States is locked to a Region Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. Page 1-88 Chapter 1: Configuration General configuration Webpage Auto Update Bridge Entry Timeout Enter the frequency (in seconds) for the web browser to automatically refresh the web-based interface. The default setting is 0. The 0 setting causes the web-based interface to never be automatically refreshed. Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. Timeout occurs when the AP encounters no activity with the SM (whose MAC address is the bridge entry) within the interval that this parameter specifies. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Caution This parameter governs the timeout interval, even if a router in the system has a longer timeout interval. The default value of this field is 25 (minutes). An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. Bridge Table Size This parameter allows to restrict devices to connect to the SM. It is configurable from 4 to 4096. Note Configure Bridge Table Restriction parameter to Drop packets if MAC address is not in bridge table option to restrict the number of devices configured from connecting to SM. Bridge Table Restriction Frame Timing Pulse Gated Multicast Destination Address This parameter allows to either allow or restrict devices to connect to SM using the following options:

Drop packets if MAC address is not in bridge table: Select this option to restrict communication from devices not listed in bridge table. Forward packets even if MAC address is not in bridge table: Select this option to allow communication from any device. If this SM extends the sync pulse to a BH master or an AP, select either EnableIf this SM loses sync from the AP, then do not propagate a sync pulse to the BH timing master or another AP. This setting prevents interference in the event that the SM loses sync. DisableIf this SM loses sync from the AP, then propagate the sync pulse to the BH timing master or another AP. Using Link Layer Discovery Protocol (LLDP), a module exchanges multicast addresses with the device to which it is wired on the Ethernet interface. Although some switches (CMM4, for example) do not pass LLDP addresses upward in the network, a radio can pass it as the value of the Multicast Destination Address parameter value in the connected device that has it populated. Page 1-89 Chapter 1: Configuration General configuration Latitude Longitude Height Physical radio location data may be configured via the Latitude, Longitude and Height fields. Latitude and Longitude is measured in Decimal Degree while the Height is calculated in Meters. PTP 450b BHM Table 28 General page attributes PMP 450b BHM Attribute Meaning Link Speed Ethernet Link Enabled/Disabled From the drop-down list of options, select the type of link speed for the Ethernet connection. The default for this parameter is that all speeds are selected. The recommended setting is a single speed selection for all APs and SMs in the operator network. Specify whether to enable or disable Ethernet/802.3 connectivity on the wired port of the SM. This parameter has no effect on the wireless link. When you select Enable, this feature allows traffic on the Ethernet/802.3 port. This is the factory default state of the port. When you select Disable, this feature prevents traffic on the port. Typical cases of when you may want to select Disable include:

The subscriber is delinquent with payment(s). You suspect that the subscriber is sending or flooding undesired broadcast packets into the network, such as when See Configuring synchronization on page 1-105 a virus is present in the subscribers computing device. the subscribers home router is improperly configured. Sync Input Page 1-90 Chapter 1: Configuration General configuration Attribute Meaning Free Run Before GPS Sync Region Country See Configuring synchronization on page 1-107 This field displays the APs configured Country Code setting. This parameter allows you to set the country in which the radio will operate. The SM radio automatically inherits the Country Code type of the master. This behavior ignores the value of the Country parameter in the SM, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-

sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. PMP/PTP 450i Series ODU shipped to the United States is locked to a Region Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. Webpage Auto Update Enter the frequency (in seconds) for the web browser to Bridge Entry Timeout Bridging Functionality automatically refresh the web-based interface. The default setting is 0. The 0 setting causes the web-based interface to never be automatically refreshed. Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Select whether you want bridge table filtering active (Enable) or not

(Disable) on this BH. Disable: allows user to use redundant BHs without causing network addressing problems. Through a spanning tree protocol, this reduces the convergence time from 25 minutes to few seconds. However, you must disable bridge table filtering as only a deliberate part of your overall network design since disabling it allows unwanted traffic across the wireless interface. Enable: Allows user to enable bridge functionality. Note Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Page 1-91 Chapter 1: Configuration General configuration Attribute Meaning Update Application Address Prioritize TCP ACK Multicast Destination Address Latitude Longitude Height PTP 450b BHS Enter the address of the server to access for software updates on this BHM and registered BHS. To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. Using Link Layer Discovery Protocol (LLDP), a module exchanges multicast addresses with the device to which it is wired on the Ethernet interface. Although some switches (CMM4, for example) do not pass LLDP addresses upward in the network, a radio can pass it as the value of the Multicast Destination Address parameter value in the connected device that has it populated. Physical radio location data may be configured via the Latitude, Longitude and Height fields. Latitude and Longitude is measured in Decimal Degree while the Height is calculated in Meters. Table 29 General page attributes PMP 450b BHS Page 1-92 Chapter 1: Configuration General configuration Attribute Meaning Link Mode Timing Mode Frequency Band Frequency Carrier Channel Bandwidth Frame Period Cyclic Prefix Color Code Sector ID Large VC data Q Backhaul to run the radio in PTP mode. Multipoint to run radio in PMP SM mode. Allows the user to choose the mode between Timing Master and Timing Slave. Select the desired operating frequency band. Specify the frequency for the module to transmit. The default for this parameter is None. For a list of channels in the band, see the drop-

down list on the radio GUI. The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the AP and the SM. The supported Channel Bandwidths are 5 MHz, 10 MHz, 15 MHz, 20 MHz, 30 MHz, and 40 MHz. Select the Frame Period of the radio. The supported Frame Periods are:

5 ms and 2.5 ms. OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol to allow multi-pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. Specify a value from 0 to 254. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). This pull-down menu helps in configuring the Sector ID at a configurable value from 0 to 15. SM and BH have a configurable option used to prevent packet loss in the uplink due to bursting IP traffic. This is designed for IP burst traffic particular to video surveillance applications. MIMO Rate Adapt Algorithm This pull-down menu helps in configuring the Rate Adapt Algorithm to MIMO-

A/B, MIMO-B only, or MIMO-A only. Downlink Maximum Modulation Rate This pull-down menu helps in configuring the Downlink Maximum Modulation Rate at a configurable rate of 1X, 2X, 3X, 4X, 6X, or 8X. The default value is 8X. The Rate Adapt Algorithm does not allow the modulation to go beyond this limit. Page 1-93 Chapter 1: Configuration General configuration Attribute Meaning Uplink Maximum Modulation Rate Minimum Modulation Rate Downlink Data This pull-down menu helps in configuring the Uplink Maximum Modulation Rate at a configurable rate of 1X, 2X, 3X, 4X, 6X, or 8X. The default value is 8X. The Rate Adapt Algorithm does not allow the modulation to go beyond this limit. This pull-down menu helps in configuring the Minimum Modulation Rate at a configurable rate of 1X, 2X, 3X, 4X, 6X, or 8X. The default value is 1X. If the Rate Adapt Algorithm is below this limit, then bridging is disabled. This is used if PTP network can route the traffic through another path. Specify the percentage of the aggregate throughput for the downlink (frames transmitted from the AP to the subscriber). For example, if the aggregate

(uplink and downlink total) throughput on the AP is 90 Mb, then 75%

specified for this parameter allocates 67.5 Mb for the downlink and 22.5 Mb for the uplink. The default for this parameter is 75%. This parameter must be set in the range of 15% - 85%, otherwise the invalid input will not be accepted and the previously-entered valid setting is used. Transmit Power This value represents the combined power of the BHMs two transmitters. Nations and regions may regulate transmit power. For example PTP 450i Series modules are available as connectorized radios, which require the operator to adjust power to ensure regulatory compliance. The professional installer of the equipment has the responsibility to:

Maintain awareness of applicable regulations. Calculate the permissible transmitter output power for the module. Confirm that the initial power setting is compliant with national or regional regulations. Confirm that the power setting is compliant following any reset of the module to factory defaults. External Gain Fixed Receive Quality Debug This value needs to correspond to the published gain of the antenna used to ensure the radio will meet regulatory requirements. To aid in link performance monitoring, the BHM and BHS now report the number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-QAM and 256-QAM) and per channel (polarization). Note Due to CPU load, this slightly degrades the packet during per second processing. See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156. Frame Alignment Legacy Mode Page 1-94 Chapter 1: Configuration PMP/PTP 450 Series Note General configuration Refer Table 22 and Table 24 for PMP 450 AP/SM General page parameters details. General page - PMP 450 AP Figure 15 General page attributes - PMP 450 AP Page 1-95 Chapter 1: Configuration General configuration General page - PMP 450 SM Figure 16 General page attributes - PMP 450 SM Page 1-96 Chapter 1: Configuration General configuration General page PTP 450 BHM Figure 17 General page attributes - PTP 450 BHM Page 1-97 Chapter 1: Configuration General configuration General page PTP 450 BHS Figure 18 General page attributes - PTP 450 BHS Page 1-98 Chapter 1: Configuration Configuring Unit Settings page Configuring Unit Settings page Applicable products PMP: AP SM PTP: BHM BMS The Unit Settings page of the 450 Platform Family contains following options:

Unit-Wide Changes Download Configuration File Upload and Apply Configuration File (for AP and BHM) LED Panel Settings (for SM and BHS) Note LED Panel setting is applicable for SM and BHS only. Upload and Apply Configuration File attributes are not supported for SM and BHS. The 450 Platform Family also supports import and export of configuration from the AP/BHM/SM/BHS as a text file. The configuration file is in JSON format. The logged in user must be an ADMINISTRATOR in order to export or import the configuration file. The exported configuration file contains the complete configuration including all the default values. To keep a backup of the current configuration, the file can be saved as-is and imported later. The configuration file supports encrypted password. The exported configuration file will contain encrypted password. The import of configuration can have either encrypted or plain text password in Configuration fie. A new tab Encrypt the Password is added under Encrypted Password tab to generate encrypted password for a given password. The Import and Export procedure of configuration file is described in Import and Export of config file on page 1-268. LED Panel Mode has options select Revised mode and Legacy mode. The Legacy mode configures the radio to operate with standard LED behavior. Page 1-99 Chapter 1: Configuration Configuring Unit Settings page Unit Settings page of 450 Platform Family - AP/BHM The Unit Setting page of AP/BHM is explained in Table 30. Table 30 Unit Settings attributes 450 Platform Family AP/BHM Attribute Meaning Set to Factory Defaults Upon Default Mode Detection If Enabled is checked, then the default mode functions is enabled. When the module is rebooted with Default mode enabled, it can be accessed at the IP address 169.254.1.1 and no password, and all parameter values are reset to defaults. A subscriber, technician, or other person who gains physical access to the module and uses an override cannot see or learn the settings that were previously configured in it. If Disabled is checked, then the default mode functions are disabled. Caution When Set to Factory Defaults Upon Default Mode is set to Enable, the radio does not select all of the frequencies for Radio Frequency Scan Selection List. It needs to be selected manually. Undo Unit-Wide Saved Changes When you click this button, any changes that you made in any tab but did not commit by a reboot of the module are undone. Set to Factory Defaults When you click this button, all configurable parameters on all tabs are reset to the factory settings. Page 1-100 Chapter 1: Configuration Configuring Unit Settings page Note This can be reverted by selecting "Undo Unit-Wide Saved Changes", before rebooting the radio, though this is not recommended. Password This allows to provide encrypted password for a given password. On click of Encrypt the password button, the Encrypted Password field will display encrypted value of entered plain text password in Password field. Configuration File This allows to download the configuration file of the radio. This configuration file contains the complete configuration including all the default values. The configuration file is highlighted as downloadable link and the naming convention is <mac address of AP>.cfg. Apply Configuration File This allows to import and apply configuration to the AP. Chose File: Select the file to upload the configuration. The configuration file is named as <file name>.cfg. Upload: Import the configuration to the AP. Apply Configuration File: Apply the imported configuration file to the AP. The imported configuration file may either contain a full device configuration or a partial device configuration. If a partial configuration file is imported, only the items contained in the file will be updated, the rest of the device configuration parameters will remain the same. Operators may also include a special flag in the configure file to instruct the device to first revert to factory defaults then to apply the imported configuration. Status of Configuration file This section shows the results of the upload. Page 1-101 Chapter 1: Configuration Configuring Unit Settings page Unit Settings page of PMP/PTP 450i SM/BHS The Unit Settings page of PMP/PTP 450i SM/BHS is explained in Table 31. Table 31 SM Unit Settings attributes Attribute Meaning Set to Factory Defaults Upon Default Plug Detection See Table 30 Unit Settings attributes 450 Platform Family AP/BHM on page 1-100 LED Panel Settings Legacy Mode configures the radio to operate with standard LED behavior. Undo Unit-Wide Saved Changes Password Set to Factory Defaults Configuration File Status of Configuration file See Table 30 Unit Settings attributes 450 Platform Family AP/BHM on page 1-100 Page 1-102 Chapter 1: Configuration Setting up time and date Setting up time and date Time page of 450 Platform Family - AP/BHM Applicable products PMP: AP PTP: BHM The Time page of 450 Platform Family AP/BHM is explained in Table 32. Table 32 450 Platform Family - AP/BHM Time attributes Attribute Meaning NTP Server (Name or IP Address) NTP Server 1 (Name or IP Address) NTP Server 2 (Name or IP Address) NTP Server 3 (Name or IP Address) The management DNS domain name may be toggled such that the name of the NTP server only needs to be specified and the DNS domain name is automatically appended to that name. To have each log in the AP/BHM correlated to a meaningful time and date, either a reliable network element must pass time and date to the AP/BHM or must set the time and date whenever a power cycle of the AP/BHM has occurred. A network element passes time and date in any of the following scenarios:

A connected CMM4 passes time and date (GPS time and date, if received). A connected CMM4 passes the time and date (GPS time and date, if received), but only if both the CMMr is operating on CMMr Release 2.1 or later release. (These releases include NTP server functionality.) Page 1-103 Chapter 1: Configuration Setting up time and date A separate NTP server (including APs/BHMs receiving NTP data) is addressable from the AP/BHM. If the AP/BHM needs to obtain time and date from a CMM4, or a separate NTP server, enter the IP address or DNS name of the CMM4 or NTP server on this tab. To force the AP/BHM to obtain time and date before the first (or next) 15-minute interval query of the NTP server, click Get Time via NTP. The polling of the NTP servers is done in a sequential fashion, and the polling status of each server is displayed in the NTP Update Log section of the Time Configuration page. An entry of 0.0.0.0 in any of the NTP Server fields indicates an unused server configuration. NTP Server(s) in Use Lists the IP addresses of servers used for NTP retrieval. Time Zone The Time Zone option may be used to offset the received NTP time to match the operators local time zone. When set on the AP/BHM, the offset is set for the entire sector SMs (or BHS) are notified of the current Time Zone upon initial registration). If a Time Zone change is applied, the SMs (or BHS) is notified of the change in a best effort fashion, meaning some SMs//BHSs may not pick up the change until the next re-registration. Time Zone changes are noted in the Event Log of the AP/BHM and SM/BHS. System Time The current time used by the system. Last NTP Time Update Time Date The last time that the system time was set via NTP. This field may be used to manually set the system time of the radio. This field may be used to manually set the system date of the radio. NTP Update Log This field shows NTP clock update log. It includes NTP clock update Date and Time stamp along with server name. Page 1-104 Chapter 1: Configuration Configuring synchronization Configuring synchronization Applicable products PMP: AP PTP: BHM Sync Input This section describes synchronization options for PMP and PTP configuration. Figure 19 Sync Setting configuration The Sync Input parameter can be configured under Sync Setting tab of Configure > General page (see General configuration on page 1-71). PMP/PTP 450i Series has following synchronization input options:

AutoSync AutoSync + Free Run Generate Sync AutoSync For 450i AP/BHM and 450m AP, the AP/BHM automatically receives sync from one of the following sources:

GPS Sync over Timing Port (UGPS, cnPulse, co-located AP GPS sync output, or Remote Device feed from a registered SMs GPS sync output) GPS Sync over Power Port (CMM4), CMM5, cnPulse module ODU Sync Port. For 450 AP, the internal GPS is available in addition to the above sync sources. For a 450 BHM the only available sync source is the Timing Port, as GPS Sync Over Power Port is not supported. For a 450b BHM only GPS Sync Over Power Port is available. Upon AP/BHM power on with the Free Run Before GPS Sync parameter set to disabled, the AP/BHM does not transmit until a valid synchronization pulse is received from one of the sources above. If there is a loss of GPS synchronization pulse after sync is initially established, within two seconds the AP/BHM automatically attempts to source GPS signaling from another source. Page 1-105 Chapter 1: Configuration Configuring synchronization In case of PMP, when there are synchronization sources on both the timing port and the power port, the power port GPS source is chosen first. If no valid GPS signal is received, the AP/BHM ceases transmission and SM/BHS registration is lost until a valid GPS signal is received again on the AP or BHM. Note After a reboot of 450m AP, the sync acquisition takes a little longer than it had on 450i

(anywhere from 40 seconds to 120 seconds difference). When the Sync Input field is set to Autosync or Autosync + Free Run, other options become available to be set e.g. UGPS Power and other fields. This is true on APs and BHMs. AutoSync + Free Run This mode operates similarly to mode AutoSync, but if a previously received synchronization signal is lost and no GPS signaling alternative is achieved, the AP/BHM automatically changes to synchronization mode Generate Sync. While BHS/SM registration is maintained, in this mode there is no synchronization of APs/BHMs that can hear each other; the AP/BHM will only generate a sync signal for the local AP/BHM and its associated SMs/BHS. Once a valid GPS signal is obtained again, the AP/BHM automatically switches to receiving synchronization via the GPS source and SM/BHS registration is maintained. Note In mode AutoSync + Free Run with the Free Run Before GPS Sync parameter set to disabled, if a GPS signal is never achieved initially, the system will not switch to Free Run mode, and SMs/BHS will not register to the AP/BHM. A valid GPS signal must be present initially for the AP to switch into Free Run mode (and to begin self-generating a synchronization pulse). Also, when an AP/BHM is operating in Free Run mode, over a short time it will no longer be synchronized with co-located or nearby APs/BHMs (within radio range). Due to this lack of transmit and receive synchronization across APs/BHMs or across systems, performance while in Free Run mode may be degraded until the APs/BHMs operating in Free Run mode regain a external GPS synchronization source. Careful attention is required to ensure that all systems are properly receiving an external GPS synchronization pulse, and please consider Free Run mode as an emergency option. Generate Sync (Factory default) This option may be used when the AP/BHM is not receiving GPS synchronization pulses from either a CMM4/CMM5 or UGPS/cnPulse module, and there are no other APs/BHMs active within the link range. Using this option will not synchronize transmission of APs/BHMs that can hear each other; it will only generate a sync signal for the local AP/BHM and its associated SMs/BHS. Note Page 1-106 Chapter 1: Configuration Configuring synchronization When an AP/BHM has its "Regional Code" set to "None", The radio will not provide valid Sync Pulse Information. There is a RED warning that the radio will not transmit, but the user might expect to see a valid sync if the radio is connected to a working CMM4 or UGPS. Free Run Before GPS Sync This option is available when the Sync Input parameter is configured for either AutoSync mode or AutoSync + Free Run mode. When Free Run Before GPS Sync is set to Enabled, if the radio does not detect a valid GPS synchronization pulse after booting up then it will operate in Generate Sync Free Run mode until a valid source is detected. While the AP/BHM is in Generate Sync Free Run mode SMs/BHS will be able to register, but there is no synchronization of APs/BHMs that can hear each other; the AP/BHM will only generate a sync signal for the local AP/BHM and its associated SMs/BHS. Once a valid synchronization source is found, the AP/BHM automatically switches to receiving synchronization from the source and SM/BHS registration is maintained. If Free Run Before GPS Sync is set to Disabled, the AP/BHM does not transmit and SMs/BHS will be unable to register until a valid GPS synchronization source is connected. Device Type This parameter determines whether the device is configured as a Remote AP, receiving GPS sync from a co-located AP GPS sync output or Remote Device feed from a registered SMs GPS sync output, or as a Standard AP. This parameter applies in AutoSync or AutoSync + Free Run modes only. Synchronization behavior is as follows:

Standard: The AutoSync mechanism will source GPS synchronization from the APs Aux/Timing port, the APs power port, or from the device on-board GPS module (if present). Remote: The AutoSync mechanism will source GPS synchronization from the APs Aux/Timing port or from the device on-board GPS module (if present). GPS synchronization pulses on the Power Port are ignored. Verify GPS Message Checksum The Verify GPS Message Checksum parameter enables or disables validation of incoming GPS location messages from a UGPS or cnPulse module connected to the APs Aux Port. When enabled the AP will discard messages found to have an incorrect checksum and will increment the Invalid Message Count display of the Sync Status tab of the Home GUI page accordingly. Sync Aux Port Config The Sync Output to Aux Port parameter takes effect when the AP is operating in either AutoSync or AutoSync + Free Run modes. When enabled, the AP will output the GPS timing pulse on the Aux/Timing Port. In this configuration the AP may serve as a GPS synchronization source for a co-located AP. Page 1-107 Chapter 1: Configuration Configuring synchronization Aux Port Power to UGPS The 450 series APs are capable of supplying power to a connected UGPS or cnPulse module via the Aux/Timing Port. Enable the Aux Port Power to UGPS parameter to output power on the port. Note The AP is able to receive GPS sync pulses and satellite data via the Aux Port regardless of whether this parameter is Enabled or Disabled. However, on the 450m AP and 450i AP/BHM, the satellite data is displayed on the Sync Status page only when the Aux Port power is enabled. Caution When a UGPS module is used to provide GPS sync to two 450m or 450i APs simultaneously, it is recommended to install a separate power supply for the UGPS to prevent the possibility of sync interruption upon reboot of the APs. Page 1-108 Chapter 1: Configuration Configuring security Configuring security Perform this task to configure the 450 Platform system in accordance with the network operators security policy. Choose from the following procedures:

Managing module access by password on page 1-110: to configure the unit access password and access level See Radio Recovery on page 3-87 Isolating from the internet on page 1-113: to ensure that APs are properly secured from external networks Encrypting radio transmissions on page 1-113: to configure the unit to operate with AES wireless link security Requiring SM Authentication on page 1-114: to set up the AP to require SMs to authenticate via the AP, WM, or RADIUS server Filtering protocols and ports on page 1-115: to filter (block) specified protocols and ports from leaving the system Encrypting downlink broadcasts on page 1-118: to encrypt downlink broadcast transmissions Isolating SMs on page 1-118: to prevent SMs in the same sector from directly communicating with each other Filtering management through Ethernet on page 1-119: to prevent management access to the SM via the radios Ethernet port Allowing management only from specified IP addresses on page 1-119: to only allow radio management interface access from specified IP addresses Restricting radio Telnet access over the RF interface on page 1-119: to restrict Telnet access to the AP Configuring SNMP Access on page 1-123 Configuring Security on page 1-125 Page 1-109 Chapter 1: Configuration Configuring security Managing module access by password Applicable products PMP: AP SM PTP: BHM BMS See Managing module access by password in Planning and installation Guide. Adding a User for Access to a module The Account > Add User page allows to create a new user for accessing 450 Platform Family -

AP/SM/BHM/BHS. The Add User page is explained in Table 33. Table 33 Add User page of account page - AP/ SM/BH Attribute User Name Level Meaning User Account name. Select appropriate level for new account. It can be INSTALLER, ADMINISTRATOR or TECHNICIAN. See Managing module Access by passwords in Planning and Installation Guide. New Password Assign the password for new user account Confirm Password This new password must be confirmed in the Confirm Password field. User Mode User Mode is used to create an account which are mainly used for viewing the configurations. The local and remote Read-Only user account can be created by Admin, Installer or Tech logins. To create a Read-Only user, the read-only check box needs to be checked. Note The Read-Only user cannot perform any service impacting operations like creating read-

only accounts, editing and viewing read-only user accounts, changes in login page, read-

only user login, Telnet access, SNMP, RADIUS and upgrade/downgrade. Page 1-110 Chapter 1: Configuration Configuring security Deleting a User from Access to a module The Account > Delete User page provides a drop-down list of configured users from which to select the user you want to delete. The Delete User page is explained in Table 34. Table 34 Delete User page - 450 Platform Family - AP/ SM/BH Attribute User Meaning Select a user from drop-down list which has to be deleted and click Delete button. Accounts that cannot be deleted are the current user's own account. the last remaining account of ADMINISTRATOR level. Changing a User Setting The Account > Change User Setting page allows to update password, mode update and general status permission for a user. From the factory default state, configure passwords for both the root and admin account at the ADMINISTRATOR permission level, using Update Password tab of Change Users Setting page. The Change User Setting page is explained in Table 35. Table 35 Change User Setting page - 450 Platform Family AP/ SM/BH Attribute Meaning Page 1-111 Chapter 1: Configuration Configuring security Update Password tab This tab provides a drop-down list of configured users from which a user is selected to change password. Update Mode tab This tab facilitates to convert a configured user to a Read-Only user. General Status Permission tab This tab enables and disables visibility of General Status Page for all Guest users. To display of Radio data on SMs/BHS main Login page for Guest login, it can be enabled or disabled in Security tab of Configuration page. Figure 20 AP Evaluation Configuration parameter of Security tab for PMP Figure 21 BHM Evaluation Configuration parameter of Security tab for PTP Users account The Account > Users page allows to view all configured users account for accessing the module. The Users page is explained in Table 36. Table 36 User page 450 Platform Family AP/SM/BH Attribute Username Permission Meaning User access account name Permission of configured user INSTALLER, ADMINISTRATOR or TECHNICIAN Mode This field indicate access mode of user Read-Write or Read-Only. Page 1-112 Chapter 1: Configuration Configuring security Overriding Forgotten IP Addresses or Passwords on AP and SM See Radio Recovery on page 3-89 Isolating from the internet APs/BHMs Applicable products PMP: AP PTP: BHM See Isolating AP/BHM from the Internet in Planning and Installation Guide. Encrypting radio transmissions Applicable products PMP: AP SM PTP: BHM BMS See Encryption radio transmission in Planning and Installation Guide. Page 1-113 Chapter 1: Configuration Configuring security Requiring SM Authentication Applicable products PMP: AP SM Through the use of a shared AP key, or an external RADIUS (Remote Authentication Dial In User Service) server, it enhances network security by requiring SMs to authenticate when they register. For descriptions of each of the configurable security parameters on the AP, see Configuring Security on page 1-125. For descriptions of each of the configurable security parameters on the SM, see Security page 450 Platform Family BHM on page 1-130. Operators may use the APs Authentication Mode field to select from among the following authentication modes:

Disabledthe AP requires no SMs to authenticate (factory default setting). Authentication Server the AP requires any SM that attempts registration to be authenticated in Wireless Manager before registration AP PreShared Key - The AP acts as the authentication server to its SMs and will make use of a user-

configurable pre-shared authentication key. The operator enters this key on both the AP and all SMs desired to register to that AP. There is also an option of leaving the AP and SMs at their default setting of using the Default Key. Due to the nature of the authentication operation, if you want to set a specific authentication key, then you MUST configure the key on all of the SMs and reboot them BEFORE enabling the key and option on the AP. Otherwise, if you configure the AP first, none of the SMs is able to register. RADIUS AAA - When RADIUS AAA is selected, up to 3 Authentication Server (RADIUS Server) IP addresses and Shared Secrets can be configured. The IP address(s) configured here must match the IP address(s) of the RADIUS server(s). The shared secret(s) configured here must match the shared secret(s) configured in the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not for splitting the database. If Server 1 doesnt respond, Server 2 is tried, and then server 3. If Server 1 rejects authentication, the SM is denied entry to the network, and does not progress trying the other servers. For more information on configuring the PMP 450 Platform network to utilize a RADIUS server, see Configuring a RADIUS server on page 1-275. Page 1-114 Chapter 1: Configuration Configuring security Filtering protocols and ports Applicable products PMP: AP SM PTP: BHM BMS The filtering protocols and ports allows to configure filters for specified protocols and ports from leaving the AP/SM/BHM/BHS and entering the network. See Filtering protocols ans ports in Planning and Installation Guide. Protocol filtering page of 450 Platform Family AP/BHM The Protocol Filtering page of 450 Platform Family - AP/BHM is explained in Table 37. Table 37 AP/BHM Protocol Filtering attributes Page 1-115 Chapter 1: Configuration Configuring security Attribute Meaning Packet Filter Types For any box selected, the Protocol and Port Filtering feature blocks the associated protocol type. To filter packets in any of the user-defined ports, must do all of the following:

Check the box for User Defined Port n (See Below) in the Packet Filter Types section of this tab. In the User Defined Port Filtering Configuration section of this tab:

provide a port number at Port #n. enable TCP and/or UDP by clicking the associated radio button Filter Direction Operators may choose to filter upstream (uplink) RF packets or downstream

(downlink) RF packets. User Defined Port Filtering Configuration RF Telnet Access You can specify ports for which to block subscriber access, regardless of whether NAT is enabled. RF Telnet Access restricts Telnet access to the AP/BHM from a device situated below a network SM/BHS (downstream from the AP/BHM). This is a security enhancement to restrict RF-interface sourced AP access specifically to the LAN1 IP address and LAN2 IP address (Radio Private Address, typically 192.168.101.[LUID]). This restriction disallows unauthorized users from running Telnet commands on the AP/BHM that can change AP/BHM configuration or modifying network-critical components such as routing and ARP tables. PPPoE PADI Downlink Forwarding Enabled: the AP/BHM allows downstream and upstream transmission of PPPoE PADI packets. By default, PPPoE PADI Downlink Forwarding is set to Enabled. Disabled: the AP/BHM disallows PPPoE PADI packets from entering the Ethernet interface and exiting the RF interface (downstream to the SM/BHS). PPPoE PADI packets are still allowed to enter the APs RF interface and exit the APs /BHMs Ethernet interface (upstream). Page 1-116 Chapter 1: Configuration Configuring security Protocol filtering page of SM/BHS The Protocol Filtering page of SM/BHS is explained in Table 38. Table 38 SM/BHS Protocol Filtering attributes Attribute Meaning See Table 37 AP/BHM Protocol Filtering attributes on page 1-115 See Table 37 AP/BHM Protocol Filtering attributes on page 1-115 Packet Filter Configuration tab User Defined Port Filtering Configuration tab Page 1-117 Chapter 1: Configuration Port configuration Configuring security 450 Platform Family ODUs support access to various communication protocols and only the ports required for these protocols are available for access by external entities. Operators may change the port numbers for these protocols via the radio GUI or SNMP. The Port Configuration page of the AP/SM/BHM/BHS is explained in Table 39. Table 39 Port Configuration attributes AP/SM/BHM/BMS Attribute FTP Port HTTP Port HTTPS Port Radius Port Meaning The listen port on the device used for FTP communication. The listen port on the device used for HTTP communication. The listen port on the device used for HTTPS communication The destination port used by the device for RADIUS communication. Radius Accounting Port The destination port used by the device for RADIUS accounting communication. SNMP Port The listen port on the device used for SNMP communication. SNMP Trap Port The destination port used by the device to which SNMP traps are sent. Syslog Server Port The destination port used by the device to which Syslog messaging is sent. Encrypting downlink broadcasts See Encryption downlink broadcast in Installation and Planning Guide. Isolating SMs See Isolating SMs in Installation and Planning Guide. Page 1-118 Chapter 1: Configuration Configuring security Filtering management through Ethernet See Filtering management through Ethernet in Installation and Planning Guide. Allowing management only from specified IP addresses See Allowing management only from specified IP address in Installation and Planning Guide. Restricting radio Telnet access over the RF interface RF Telnet Access restricts Telnet access to the AP from a device situated below a network SM

(downstream from the AP). This is a security enhancement to restrict RF-interface sourced AP access specifically to the LAN1 IP address and LAN2 IP address (Radio Private Address, typically 192.168.101.

[LUID]). This restriction disallows unauthorized users from running Telnet commands on the AP that can change AP configuration or modifying network-critical components such as routing and ARP tables. The RF Telnet Access may be configured via the AP GUI or via SNMP commands, and RF Telnet Access is set to Enabled by default. Once RF Telnet Access is set to Disabled, if there is a Telnet session attempt to the AP originating from a device situated below the SM (or any downstream device), the attempt is dropped. This also includes Telnet session attempts originated from the SMs management interface (if a user has initiated a Telnet session to a SM and attempts to Telnet from the SM to the AP). In addition, if there are any active Telnet connections to the AP originating from a device situated below the SM (or any downstream device), the connection is dropped. This behavior must be considered if system administrators use Telnet downstream from an AP (from a registered SM) to modify system parameters. Setting RF Telnet Access to Disabled does not affect devices situated above the AP from accessing the AP via Telnet, including servers running the CNUT (Canopy Network Updater tool) application. Also, setting RF Telnet Access to Disabled does not affect any Telnet access into upstream devices

(situated above or adjacent to the AP) through the AP (see Page 1-119 Chapter 1: Configuration Configuring security Figure 22). The figure below depicts a user attempting two telnet sessions. One is targeted for the AP (orange) and one is targeted for the network upstream from the AP (green). If RF Telnet Access is set to Disabled

(factory default setting), the Telnet attempt from the user to the AP is blocked, but the attempt from the user to Network is allowed to pass through the Cambium network. Page 1-120 Chapter 1: Configuration Configuring security Figure 22 RF Telnet Access Restrictions (orange) and Flow through (green) Key Security Considerations when using the RF Telnet Access Feature To ensure that the network is fully protected from unauthorized AP Telnet sessions, the following topics must be considered:

1. Securing AP Clusters When working with a cluster of AP units, to eliminate potential security holes allowing Telnet access, ensure that the RF Telnet Access parameter is set to Disabled for every AP in the cluster. In addition, since users situated below the AP are able to pass Telnet sessions up through the SM and AP to the upstream network (while AP RF Telnet Access is set to Disabled), ensure that all CMM4 or other networking equipment is secured with strong passwords. Otherwise, users may Telnet to the CMM4 or other networking equipment, and subsequently access network APs (see Figure 23) via their Ethernet interfaces (since RF Telnet Access only prevents Telnet sessions originating from the APs wireless interface). Figure 23 RF Telnet Access Restriction (orange) and Potential Security Hole (green) As a common practice, AP administrator usernames and passwords must be secured with strong, non-

default passwords. Page 1-121 Chapter 1: Configuration Configuring security 2. Restricting AP RF Telnet Access AP Telnet access via the RF interface may be configured in two ways the AP GUI and SNMP. 3. Controlling RF Telnet Access via the AP GUI To restrict all Telnet access to the AP via the RF interface from downstream devices, follow these instructions using the AP GUI:

Procedure 12 Restricting RF Telnet access 1 2 3 4 5 Log into the AP GUI using administrator credentials On the AP GUI, navigate to Configuration > Protocol Filtering Under GUI heading Telnet Access over RF Interface, set RF Telnet Access to Disabled Click the Save button Once the Save button is clicked, all RF Telnet Access to the AP from devices situated below the AP is blocked. Note The factory default setting for RF Telnet Access is disabled and PPPoE PADI Downlink Forwarding is enabled. Page 1-122 Chapter 1: Configuration Configuring security Configuring SNMP Access The SNMPv3 interface provides a more secure method to perform SNMP operations. This standard provides services for authentication, data integrity and message encryption over SNMP. Refer to Planning of SNMPv3 operation in Planning and Installation Guide. Note The factory default setting for SNMP is SNMPv2c Only. Procedure 13 Configuring SNMPv3 1 Log into the AP GUI using administrator credentials 2 On the AP/SM GUI, navigate to Configuration > Security Page 3 Under GUI heading Security Mode, set SNMP to SNMPv3 Only 4 Click the Save Changes button 5 Go to Configuration > SNMP Page Page 1-123 Chapter 1: Configuration Configuring security 6 Under GUI heading SNMPv3 setting, set Engine ID, SNMPv3 Security Level, SNMPv3 Authentication Protocol, SNMPv3 Privacy Protocol, SNMPv3 Read-Only User, SNMPv3 Read/Write User, SNMPv3 Trap Configuration parameters:

Engine ID:

Each radio (AP/SM/BHM/BHS) has a distinct SNMP authoritative engine identified by a unique Engine ID. While the Engine ID is configurable to the operator it is expected that the operator follows the guidelines of the SNMPEngineID defined in the SNMP-

FRAMEWORK-MIB (RFC 3411). The default Engine ID is the MAC address of the device. SNMPv3 security level, Authentication and Privacy Protocol The authentication allows authentication of SNMPv3 user and privacy allows for encryption of SNMPv3 message. 450 Platform Family supports MD5 authentication and CBC-DES privacy protocols. SNMPv3 Read-Only and Read/Write User The user can be defined by configurable attributes. The attributes and default values are:

Read-only user o Username = Canopyro o Authentication Password = authCanopyro o Privacy Password = privacyCanopyro Read-write user (by default read-write user is disabled) o Username = Canopy o Authentication Password = authCanopy o Privacy Password = privacyCanopy SNMPv3 Trap Configuration The traps may be sent from radios in SNMPv3 format based on parameter settings. It can be configured for Disabled, Enabled for Read-Only User, Enable for Read/Write User. Page 1-124 Chapter 1: Configuration Configuring Security Configuring security Applicable products PMP: AP SM PTP: BHM BMS Security page 450 Platform Family AP The security page of AP is explained in Table 40. Table 40 Security attributes 450 Platform Family AP Page 1-125 Chapter 1: Configuration Configuring security Page 1-126 Chapter 1: Configuration Attribute Meaning Configuring security Authentication Mode Operators may use this field to select from among the following authentication modes:

Disabledthe AP requires no SMs to authenticate. (Factory default). Authentication Server the AP/BHM requires any SM/BHS that attempts registration to be authenticated in Wireless Manager before registration. AP PreShared Key - The AP/BHM acts as the authentication server to its SMs/BHS and will make use of a user-configurable pre-shared authentication key. The operator enters this key on both the AP/BHM and all SMs/BHS desired to register to that AP/BHM. There is also an option of leaving the AP/BHM and SMs/BHS at their default setting of using the Default Key. Due to the nature of the authentication operation, if you want to set a specific authentication key, then you MUST configure the key on all of the SMs/BHS and reboot them BEFORE enabling the key and option on the AP/BHM. Otherwise, if you configure the AP/BHM first, none of the SMs/BHS is able to register. RADIUS AAA - When RADIUS AAA is selected, up to 3 Authentication Server (RADIUS Server) IP addresses and Shared Secrets can be configured. The IP address(s) configured here must match the IP address(s) of the RADIUS server(s). The shared secret(s) configured here must match the shared secret(s) configured in the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not for splitting the database. If Server 1 doesnt respond, Server 2 is tried, and then server 3. If Server 1 rejects authentication, the SM is denied entry to the network, and does not progress trying the other servers. Authentication Server DNS Usage The management DNS domain name may be toggled such that the name of the authentication server only needs to be specified and the DNS domain name is automatically appended to that name. Authentication Server 1 to 5 Enter the IP address or server name of the authentication server (RADIUS or WM) and the Shared Secret configured in the authentication server. When Authentication Mode RADIUS AAA is selected, the default value of Shared Secret is CanopySharedSecret. The Shared Secret may consist of up to 32 ASCII characters. Radius Port This field allows the operator to configure a custom port for RADIUS server communication. The default value is 1812. Authentication Key 128-bit This authentication key is a 32-character hexadecimal string used when Authentication Mode is set to AP PreShared Key. By default, this key is set to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF. Select Key 128-bit This option allows operators to choose which authentication key is used:

Use Key above means that the key specified in Authentication Key is used for authentication Use Default Key means that a default key (based off the SMs MAC address) is used for authentication Page 1-127 Chapter 1: Configuration Configuring security Disable AES 128-bit Authentication Key 256-bit This option allows to disable the AES-128 encryption. When AES-128 Encryption is disabled, it prevents the use of AES-128 when encryption is enabled. Since changes to other attributes (e.g. PreSharedKey authentication settings) could cause a need for 128-bit Auth and AES-128 upon next registration, Disable AES 128-bit parameter is prevented from being changed on the "Security" webpage while the "Reboot Required"

warning is present at the top of the Web GUI pages. The recommendation is to complete other changes first and to ensure that all links at an AP are running AES-256 before disabling the use of AES-128 on all units (AP and SMs) in the sector. When saving and loading a configuration file, Disable AES 128 is saved and loaded as a normal attribute. It will not take effect until a reboot is triggered. Since enabling this attribute could have the effect of preventing a link coming up, care should be taken on networks that enable this attribute on only some units. Select one of the following options to either disable or use AES-128 encryption. AES-128 Encryption Disabled:

AES-128 Encryption Available This authentication key is a 64-character hexadecimal string used when Authentication Mode is set to AP PreShared Key. By default, this key is set to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFF. Note The AES-256 parameters are visible only when the feature key is purchased. Select Key 256-bit This option allows operators to choose which authentication key is used:

Dynamic Authorization Extensions for RADIUS Use Key above means that the key specified in Authentication Key is used for authentication Use Default Key means that a default key (based off of the SMs MAC address) is used for authentication Note The AES-256 parameters are visible only when the feature key is purchased. Enable CoA and Disconnect Message: Allows to control configuration parameters of SM using RADIUS CoA and Disconnect Message feature. Disable CoA and Disconnect Message: Disables RADIUS CoA and Disconnect Message feature. To enable CoA and Disconnect feature, the Authentication Mode should be set to RADIUS AAA. Page 1-128 Chapter 1: Configuration Configuring security Bypass Authentication for ICC SMs Enabled: SM authentication is disabled when SM connects via ICC

(Installation Color Code). Disabled: SM authentication is enabled. Encryption Setting Specify the type of airlink security to apply to this AP. The encryption setting must match the encryption setting of the SMs. None provides no encryption on the air link. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. Note This parameter is applicable to BHM. SM Display of AP Evaluation Data Or BHS Display of BHM Evaluation Data Allows operators to suppress the display of data about this AP/BHM on the AP/BHM Evaluation tab of the Tools page in all SMs/BHS that register. The factory default setting for SM Display of AP Evaluation Data or BHS Display of BHM Evaluation Data is enabled display. PMP 450/450i Series SM display of AP Evaluation Data parameter PTP 450/450i Series BHS display of BHM Evaluation Data parameter Web, Telnet, FTP Session Timeout Enter the expiry in seconds for remote management sessions via HTTP, telnet, or ftp access to the AP/BHM. IP Access Control You can permit access to the AP/BHM from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address Allowed Source IP 1 to 3 If you selected IP Access Filtering Enabled for the IP Access Control parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the AP from any IP address. You may populate as many as all three. If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. Page 1-129 Chapter 1: Configuration Configuring security Web Access SNMP Telnet FTP TFTP The Radio supports secured and non-secured web access protocols. Select suitable web access from drop-down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. This option allows to configure SNMP agent communication version. It can be selected from drop-down list:

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is a secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. NTP Server This option allows to Enable and Disable NTP server access to the Radio. Site Information viewable to Guest Users This option allows to Enable or Disable displaying site information with Guest users. Site Name Specify a string to associate with the physical module. Site Contact Enter contact information for the module administrator. Site Location Enter information about the physical location of the module. Enable Security Banner during Login Enable: The Security Banner Notice will be displayed before login. Disable: The Security Banner Notice will not be displayed before login. Security Banner Notice User must accept security banner before login User can enter ASCII (0-9a-zA-Z newline, line-feed are allowed) text up-to 1300 characters. Enable: login area (username and password) will be disabled unless user accepts the security banner. Disable: User cant login to radio without accepting security banner. Security page 450 Platform Family BHM The security page of AP/BHM is explained in Table 41. Page 1-130 Chapter 1: Configuration Configuring security Table 41 Security attributes 450 Platform Family BHM Page 1-131 Chapter 1: Configuration Attribute Meaning Configuring security Authentication Mode Operators may use this field to select from among the following authentication modes:

Authentication Required: the BHS requires to be authenticated. Authentication Disabled: the BHM requires no BHS to authenticate. (Factory default). Authentication Key 128-bit Refer Table 40 Security attributes 450 Platform Family AP on page 1-125 for parameter details 24 Hour Encryption Refresh Encryption Setting BHS Display of BHM Evaluation Data Web, Telnet, FTP Session Timeout IP Access Control Allowed Source IP 1 to 3 Web Access SNMP Telnet FTP TFTP NTP Server Site Information viewable to Guest Users Site Name Site Contact Site Location Enable Security Banner during Login Operators may use this field to select from among the following options:

Enabled: Allows BHS re-registration every 24 hours. Disabled: Disables 24-hour encryption refresh. This parameter is disabled by default. Refer Table 40 Security attributes 450 Platform Family AP on page 1-125 for parameter details Refer Table 40 Security attributes 450 Platform Family AP on page 1-125 for parameter details Page 1-132 Chapter 1: Configuration Configuring security Security Banner Notice User must accept security banner before login Security page - 450 Platform Family SM The security page of 450 Platform Family SM is explained in Table 42. Table 42 Security attributes 450 Platform Family SM Page 1-133 Chapter 1: Configuration Configuring security Page 1-134 Chapter 1: Configuration Configuring security Page 1-135 Chapter 1: Configuration Configuring security Attribute Meaning Authentication Key 128-bit Select Key 128-bit Disable AES 128-bit Authentication Key 256-bit Select Key 256-bit Enforce Authentication Phase 1 Only if the AP to which this SM will register requires authentication, specify the 128-bit key that the SM will use when authenticating. For alpha characters in this 32-character hex key, use only upper case. Refer Table 40 Security attributes 450 Platform Family AP on 1-125 for parameter details. The SM may enforce authentication types of AAA and AP Pre-sharedKey. The SM will not finish the registration process if the AP is not using the configured authentication method (and the SM locks out the AP for 15 minutes). The protocols supported for the Phase 1 (Outside Identity) phase of authentication are EAPTTLS (Extensible Authentication Protocol Tunneled Transport Layer Security) or MSCHAPv2 (Microsoft Challenge-Handshake Authentication Protocol version 2). Page 1-136 Chapter 1: Configuration Configuring security Phase 2 Identity/Realm Username Password Select the desired Phase 2 (Inside Identity) authentication protocol from the Phase 2 options of PAP (Password Authentication Protocol), CHAP

(Challenge Handshake Authentication Protocol), and MSCHAP (Microsofts version of CHAP, version 2 is used). The protocol must be consistent with the authentication protocol configured on the RADIUS server. If Realms are being used, select Enable Realm and configure an outer identity in the Identity field and a Realm in the Realm field. These must match the Phase 1/Outer Identity and Realm configured in the RADIUS server. The default Identity is anonymous. The Identity can be up to 128 non-special (no diacritical markings) alphanumeric characters. The default Realm is canopy.net. The Realm can also be up to 128 non-special alphanumeric characters. Configure an outer Identity in the Username field. This must match the Phase 1/Outer Identity username configured in the RADIUS server. The default Phase 1/Outer Identity Username is anonymous. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. Enter a Username for the SM. This must match the username configured for the SM on the RADIUS server. The default Username is the SMs MAC address. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. Enter the desired password for the SM in the Password and Confirm Password fields. The Password must match the password configured for the SM on the RADIUS server. The default Password is password. The Password can be up to 128 non-special (no diacritical markings) alphanumeric characters Upload Certificate File To upload a certificate manually to a SM, first load it in a known place on your PC or network drive, then click on a Delete button on one of the Certificate description blocks to delete a certificate to provide space for your certificate. Click on Choose File, browse to the location of the certificate, and click the Import Certificate button, and then reboot the radio to use the new certificate. When a certificate is in use, after the SM successfully registers to an AP, an indication of In Use will appear in the description block of the certificate being used. The public certificates installed on the SMs are used with the private certificate on the RADIUS server to provide a public/private key encryption system. Up to 2 certificates can be resident on a SM. An installed certificate can be deleted by clicking the Delete button in the certificates description block on the Configuration > Security tab. To restore the 2 default certificates, click the Use Default Certificates button in the RADIUS Certificate Settings parameter block and reboot the radio. Page 1-137 Chapter 1: Configuration Configuring security Encryption Setting Specify the type of airlink security to apply to this SM. The encryption setting must match the encryption setting of the AP. Web, Telnet, FTP Session Timeout Ethernet Access IP Access Control None provides no encryption on the air link. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. Enter the expiry in seconds for remote management sessions via HTTP, telnet, or FTP access to the SM. If you want to prevent any device that is connected to the Ethernet port of the SM from accessing the management interface of the SM, select Ethernet Access Disabled. This selection disables access through this port to via HTTP (the GUI), SNMP, telnet, FTP, and TFTP. With this selection, management access is available through only the RF interface via either an IP address (if Network Accessibility is set to Public on the SM) or the Session Status or Remote Subscribers tab of the AP. Note This setting does not prevent a device connected to the Ethernet port from accessing the management interface of other SMs in the network. To prevent this, use the IP Access Filtering Enabled selection in the IP Access Control parameter of the SMs in the network. See IP Access Control below. If you want to allow management access through the Ethernet port, select Ethernet Access Enabled. This is the factory default setting for this parameter. You can permit access to the SM from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address Allowed Source IP 1 to 3 If you selected IP Access Filtering Enabled for the IP Access Control parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the SM from any IP address. You may populate as many as all three. If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. A subnet mask may be defined for each entry to allow for filtering control based on a range of IP addresses. Web Access The Radio supports secured and non-secured web access protocols. Select suitable web access from drop-down list:

Page 1-138 Chapter 1: Configuration Configuring security HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. This option allows to configure SNMP agent communication version. It can be selected from drop-down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. This option allows to Enable or Disable displaying site information with Guest users. SNMP Telnet FTP TFTP Site Information viewable to Guest Users Site Name Specify a string to associate with the physical module. Site Contact Enter contact information for the module administrator. Site Location Enter information about the physical location of the module. Enable Security Banner during Login Enable: The Security Banner Notice will be displayed before login. Disable: The Security Banner Notice will not be displayed before login. Security Banner Notice User must accept security banner before login User can enter ASCII (0-9a-zA-Z newline, line-feed are allowed) text up-to 1300 characters. Enable: login area (username and password) will be disabled unless user accepts the security banner. Disable: User cant login to radio without accepting security banner. Security page 450 Platform Family BHS The Security page of 450 Platform Family BHS is explained in Table 43. Page 1-139 Chapter 1: Configuration Configuring security Table 43 Security attributes - 450 Platform Family BHS Page 1-140 Chapter 1: Configuration Configuring security Attribute Meaning Authentication Key Disable AES 128-bit Authentication Key 256-bit Web, Telnet, FTP Session Timeout IP Access Control Only if the BHM to which this BHS registers requires an authentication, specify the key that the BHS will use when authenticating. For alpha characters in this hex key, use only upper case. Refer Table 40 Security attributes 450 Platform Family AP on 1-125 for parameter details. Enter the expiry in seconds for remote management sessions via HTTP, telnet, or FTP access to the BHS. You can permit access to the BHS from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address Allowed Source IP 1 to 3 If you selected IP Access Filtering Enabled for the IP Access Control parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the BHS from any IP address. You may populate as many as all three. Web Access If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. A subnet mask may be defined for each entry to allow for filtering control based on a range of IP addresses. The Radio supports secured and non-secured web access protocols. Select suitable web access from drop-down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. Page 1-141 Chapter 1: Configuration Configuring security This option allows to configure SNMP agent communication version. It can be selected from drop-down list:

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. Refer Table 40 Security attributes 450 Platform Family AP on 1-125 for parameter details. SNMP Telnet FTP TFTP Site Information viewable to Guest Users Site Name Site Contact Site Location Enable Security Banner during Login Security Banner Notice User must accept security banner before login Page 1-142 Chapter 1: Configuration Configuring 802.1X authentication Configuring 802.1X authentication IEEE 802.1x standard defines a client and server-based access control and authentication protocol. This protocol restricts unauthorized clients from connecting to a LAN through publicly accessible ports. The authentication server authenticates each client connected to SM's ethernet port and enables the port before making available any services offered by the SM, AP, and the network. Until the client is authenticated, 802.1x access control allows only Extensible Authentication Protocol over LAN (EAPoL) traffic through the port to which the client is connected. After authentication is successful, normal traffic can pass through the port. Two types of authentication mode are supported:

Port based authentication: This mode needs to be used when single host is connected to the SM. If the authentication is successful by the host connected to the SM, SM port is enabled, and all traffic will pass through. MAC Address Based Authentication: This mode needs to be used when multiple hosts are connected to the SM. Each host needs to be authenticated by 802.1X protocol to access the network. The traffic is filtered based on the source MAC Address of the host, only the traffic from authenticated host will be allowed to access the network. 802.1X authentication page of AP The 802.1X Authentication page of AP is explained in Table 44. Table 44 802.1X authentication attributes 450 Platform Family AP Attribute Meaning 802.1X Authentication This parameter is used to enable or disable 802.1Xauthentication. It is disabled by default. 802.1X Authentication Server DNS Usage This parameter is enabled when server address is in fully qualified domain name format. Shared Secret This parameter specifies the the shared secret which is configured for this client on RADIUS server. Maximum length of this parameter is 32 characters. 802.1X Authentication Server This parameter specifies either a dotted decimal notation (IP address) or fully qualified domain name (www.google.com). Maximum length of this parameter is 256 characters. Page 1-143 Chapter 1: Configuration Configuring 802.1X authentication 802.1x authentication page of SM The 802.1X Authentication page of SM is explained in Table 45. Table 45 802.1X authentication attributes 450 Platform Family SM Attribute Meaning 802.1x Bridging Mode This parameter specifies the bridging mode used by SM. It is disabled by default. Following are the available options for this parameter. Disable 802.1x: Disable 802.1x authentication. Require 802.1x for all traffic: 802.1x authentication should be successful for any traffic to pass through the SM (i.e. Authenticator). Require 802.1x for all non-management traffic: Management traffic will be allowed to pass through the SM without 802.1x Authentication. 802.1x Authentication Mode This parameter specifies the authentication mode used by SM. Port Based Authentication: SM port is activated once the 802.1x authentication is successful. This configuration needs to be used when single host is connected behind SM. If authentication is successful, SM port is enabled, and all traffic will pass through. MAC Address Based Authentication: This option needs to be used when multiple hosts are connected behind an SM. Each host needs to be authenticated by 802.1x protocol to access the network. The traffic is filtered based on the source MAC address of the host, only the traffic from authenticated host will be allowed to access the network. 802.1x VLAN (Range :

1 4094) This parameter specifies the number of VLAN configurations. It ranges from 1 to 4094. VLAN configuration is used for sending 802.1x packet on the configured VLAN. If a customer excepts EAPoL packets on a VLAN, customer needs to configure the VLAN. Once VLAN is configured, all EAPoL packets are exchanged on the configured VLAN. VLAN 1 is the default configuration which is equivalent to untagged traffic. Page 1-144 Chapter 1: Configuration Configuring radio parameters Configuring radio parameters PMP 450m Series configuring radio on page 1-146 PMP/PTP 450i Series configuring radio on page 1-146 PMP/PTP 450b Series - configuring radio on page 1-180 PMP/PTP 450 Series configuring radio on page 1-185 Custom Frequencies page on page 1-204 DFS for 5 GHz Radios on page 1-207 MIMO-A mode of operation on page 1-213 Improved PPS performance of 450 Platform Family on page 1-216 Page 1-145 Chapter 1: Configuration Configuring radio parameters PMP 450m Series configuring radio Radio page - PMP 450m AP 5 GHz The Radio tab of the PMP 450m AP contains some of the configurable parameters that define how an AP operates. Note Only the frequencies available for your region and the selected Channel bandwidth are displayed. Table 46 PMP 450m AP Radio attributes - 5 GHz Page 1-146 Chapter 1: Configuration Configuring radio parameters Attribute Meaning Frequency Band Select the desired operating frequency band. Frequency Carrier Channel Bandwidth Specify the frequency for the module to transmit. The default for this parameter is None. For a list of channels in the band, see the drop-down list on the radio GUI. The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the AP and the SM. The supported Channel Bandwidths are 5 MHz, 10 MHz, 15 MHz, 20 MHz, 30 MHz, and 40 MHz. Note:

40 MHz is not supported on PMP 450 AP, but is supported on PMP 450 SMs. Frame Period Select the Frame Period of the radio. The supported Frame Periods are:

5 ms and 2.5 ms. OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol to allow multi-

pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. Specify a value from 0 to 254. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). This timer may be utilized to initiate SM rescans in order to register to an AP configured with the SMs primary color code. Cyclic Prefix Color Code Subscriber Color Code Rescan (When not on a Primary Color Code) Page 1-147 Chapter 1: Configuration Configuring radio parameters Subscriber Color Code Wait Period for Idle Installation Color Code The time (in minutes) for a subscriber to rescan (if this AP is not configured with the SMs primary color code). This timer will only fire once if the Subscriber Color Code Wait Period for Idle timer is configured with a nonzero value and the Subscriber Color Code Rescan expires, the Subscriber Color Code Wait Period for Idle is started. If the Subscriber Color Code Wait Period for Idle timer is configured with a zero value and the Subscriber Color Code Rescan timer expires, the SM will immediately go into rescan mode The time (in minutes) for a subscriber to rescan while idle (if this AP is not configured with the SMs primary color code). This timer will fire periodic events. The fired event determines if any RF unicast traffic (either inbound or outbound) has occurred since the last event. If the results of the event determine that no RF unicast traffic has occurred (SM is idle), then the subscriber will rescan. With this feature enabled on the AP and SM, operators may install and remotely configure SMs without having to configure matching color codes between the modules. While the SM is accessible for configuration from above the AP (for remote provisioning) and below the SM (for local site provisioning), no user data is passed over the radio link. When using the Installation Color Code feature, ensure that the SM is configured with the factory default Color Code configuration (Color Code 1 is 0, Color Code 2-

10 set to 0 and Disable). The status of the Installation Color Code can be viewed on the AP Eval web GUI page, and when the SM is registered using the Installation Color Code the message SM is registered via ICC Bridging Disabled! is displayed in red on every SM GUI page. The Installation Color Code parameter is configurable without a radio reboot for both the AP and SM. If a SM is registered via Installation Color Code and the feature is then disabled, operators will need to reboot the SM or force it to reregister (i.e. using Rescan APs functionality on the AP Eval page). Sector ID This pull-down menu helps in configuring the Sector ID at a configurable value from 0 to 15. MIMO Rate Adapt Algorithm This pull-down menu helps in configuring the Rate Adapt Algorithm to MIMO-A/B, MIMO-B only, or MIMO-A only. Downlink Maximum Modulation Rate This pull-down menu helps in configuring the Downlink Maximum Modulation Rate at a configurable rate of 1X, 2X, 3X, 4X, 6X, or 8X. The default value is 8X. The Rate Adapt Algorithm does not allow the modulation to go beyond this limit. Uplink Maximum Modulation Rate This pull-down menu helps in configuring the Uplink Maximum Modulation Rate at a configurable rate of 1X, 2X, 3X, 4X, 6X, or 8X. The default value is 8X. The Rate Adapt Algorithm does not allow the modulation to go beyond this limit. Max Range Enter the number of miles or kilometers for the furthest distance from which a SM is allowed to register to this AP. Do not set the distance to any greater number of miles. A greater distance Page 1-148 Chapter 1: Configuration Configuring radio parameters can reduce aggregate throughput. does not increase the power of transmission from the AP. For example, with a 20 MHz channel and 2.5 ms frame, every additional 2.24 miles reduces the data air time by one symbol (around 1% of the frame). Regardless of this distance, the SM must meet the minimum requirements for an acceptable link. The parameters have to be selected so that there is no overlap between one AP transmitting and another AP receiving. A co-

location tool is provided to help with selecting sets of parameters that allow co-location. The default value of this parameter is 2 miles (3.2 km). Specify the percentage of the aggregate throughput for the downlink

(frames transmitted from the AP to the subscriber). For example, if the aggregate (uplink and downlink total) throughput on the AP is 90 Mb, then 75% specified for this parameter allocates 67.5 Mb for the downlink and 22.5 Mb for the uplink. The default for this parameter is 75%. This parameter must be set in the range of 15% - 85%, otherwise the invalid input will not be accepted and the previously-entered valid setting is used. Note In order to prevent self-interference, the frame configuration needs to align which includes Downlink Data, Max Range and Contention slots. For DFS regions, the maximum Downlink % for a 5.4 GHz radio is 75% only. This field indicates the number of (reserved) Contention slots configured by the operator. The SM uses reserved Contention slots and unused data slots for bandwidth requests. See Contention slots on page 1-208. For PMP systems broadcast packets are not acknowledged. So, they are sent at the lowest modulation rate 1X. This setting adds an automatic retransmission to broadcast packets to give SMs that have poor signal a higher chance to get the packet. This field indicates the number of (reserved) Contention slots configured by the operator. The SM uses reserved Contention slots and unused data slots for bandwidth requests. See Contention slots on page 1-208. This filed eliminates the need to configure optimal number of contention slots. When this feature is enabled, AP dynamically adjusts the number of contention slots resulting in improved performance. Downlink Data Contention Slots Broadcast Repeat Count Contention Slots Auto Contention EIRP This field indicates the combined power level at which the AP will transmit, based on the Country Code. It also includes the antenna gain and array gain. SM Receive Target Level Each SMs Transmitter Output Power is automatically set by the AP. The AP monitors the received power from each SM, and adjusts each SMs Transmitter Output Power so that the received power at the AP from that SM is not greater what is set in this field. This value represents the transmitted and received power (combined power) perceived on the SM. Page 1-149 Chapter 1: Configuration Configuring radio parameters Adjacent Channel Support For some frequency bands and products, this setting is needed if AP is operating on adjacent channels with zero guard band. Multicast VC Multicast Repeat Count Multicast Downlink CIR This pull-down menu of the Multicast VC screen helps in configuring multicast packets to be transmitted over a dedicated channel at a configurable rate of 2X, 4X or 6X. The default value is Disable. If set to the default value, all multicast packets are transmitted over the Broadcast VC data path. This feature is available only for the PMP 450 Series and is not backward compatible with PMP 430 series of radios. This value is the number of packets that are repeated for every multicast VC packet received on the AP (located under Radio tab of Configuration). Multicast (like Broadcast) packets go over a VC that is shared by all SMs, so there is no guaranteed delivery. The repeat count is an attempt to improve the odds of the packets getting over the link. If the user has issues with packets getting dropped, they can use this parameter to improve the performance at the cost of the overall throughput possible on that channel. The default value is 0. This value is the committed information rate for the multicast downlink VC

(located under the Radio tab of Configuration). The default value is 0 kbps. The range of this parameter is based on the number of repeat counts. The higher the repeat count, the lower the range for the multicast downlink CIR. Near Field Operation This parameter is enabled by the Near Field Operation control. This is only available when the EIRP is set to 22 dBm or below. When Near Field Operation is enabled, the Near Field Range is used to apply compensation to the units calibration to support operation in the near field. SM Registration Limit This parameter allows to configure the limit for maximum number of SMs that can register to a PMP AP. The configurable range is from 1 to 238. Note SM trying to register after the maximum configured limit has been reached is locked out for 15 minutes and a message is displayed at the SM. Receive Quality Debug To aid in link performance monitoring, the AP and SM now report the number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-QAM) and per channel (polarization). Note Due to CPU load, this will slightly degrade packet per second processing. Page 1-150 Chapter 1: Configuration Configuring radio parameters Radio page - PMP 450m AP 3 GHz Table 47 PMP 450m AP Radio attributes - 3 GHz Page 1-151 Chapter 1: Configuration Configuring radio parameters Attribute Meaning Frequency Band Frequency Carrier Channel Bandwidth Frame Period Cyclic Prefix Color Code Subscriber Color Code Rescan (When not on a Primary Color Code) Subscriber Color Code Wait Period for Idle Installation Color Code Sector ID MIMO Rate Adapt Algorithm Downlink Maximum Modulation Rate Uplink Maximum Modulation Rate Max Range Downlink Data Contention Slots

(a.k.a. Control Slots) Broadcast Repeat Count Contention Slots Auto contention EIRP SM Receive Target Level Adjacent Channel Support Refer Table 46 PMP 450m AP Radio attributes - 5 GHz for parameter details. Page 1-152 Chapter 1: Configuration Configuring radio parameters Multicast Data Channel Multicast Repeat Count Multicast Downlink CIR SM Registration Limit Reieve Quality Debug SM Link Test Mode Restriction Force Channel Reassessment Near Field Operation Refer Table 46 PMP 450m AP Radio attributes - 5 GHz for parameter details. Page 1-153 Chapter 1: Configuration Configuring radio parameters PMP/PTP 450i Series configuring radio Radio page - PMP 450i AP 3 GHz The Radio tab of the PMP 450i AP 3 GHz is shown in Figure 24. Figure 24 PMP 450i AP Radio attributes - 3 GHz Page 1-154 Chapter 1: Configuration Configuring radio parameters Note Refer Table 48 PMP 450i AP Radio attributes - 5 GHz and Table 49 PMP 450i SM Radio attributes 5 GHz on page 1-163 for parameter details Note Only the frequencies available for your region and the selected Channel bandwidth are displayed. Page 1-155 Chapter 1: Configuration Configuring radio parameters Radio page - PMP 450i AP 5 GHz The Radio tab of the PMP 450i AP contains some of the configurable parameters that define how an AP operates. Table 48 PMP 450i AP Radio attributes - 5 GHz Page 1-156

 

 

Chapter 1: Configuration Configuring radio parameters Attribute Meaning See Table 46 PMP 450m AP Radio attributes - 5 GHz on page 1-146 Whenever the radio detects a radar pulse in either Channel Availability Check or In-Service Monitoring Modes on carrier frequency it moves the operation to a frequency configured as Alternate Frequency Carrier 1. If the radio detects a radar pulse on Alternate Frequency Carrier 1, it moves the operation to a frequency configured as Alternate Frequency Carrier 2. If the radio detects a radar pulse on Alternate Frequency Carrier 2 it moves the operation back to carrier frequency. So, there are three options in round-robin formation. These parameters are displayed based on Regional Settings. Refer Country on page 1-73 See Table 46 PMP 450m AP Radio attributes - 5 GHz on page 1-146 Frequency Band Frequency Carrier Alternate Frequency Carrier 1 and 2 Channel Bandwidth Cyclic Prefix Frame Period Color Code Subscriber Color Code Rescan (When not on a Primary Color Code) Page 1-157 Chapter 1: Configuration Configuring radio parameters Subscriber Color Code Wait Period for Idle Installation Color Code Sector ID MMO Rate Adapt Algorithm Downlink Maximum Modulation Rate Uplink Maximum Modulation Rate Max Range See Table 46 PMP 450m AP Radio attributes - 5 GHz on page 1-146 Downlink Data See Table 46 PMP 450m AP Radio attributes - 5 GHz on page 1-146 Contention Slots

(a.k.a. Control Slots) This field indicates the number of (reserved) Contention slots configured by the operator. The SM uses reserved Contention slots and unused data slots for bandwidth requests. See Contention slots on page1-208. Auto Contention This parameter allows the operator to enable or disable Auto Contention. Broadcast Repeat Count The default is 2 repeats (in addition to the original broadcast packet, for a total of 3 packets sent for everyone needed), and is settable to 1 or 0 repeats (2 or 1 packets for every broadcast). ARQ (Automatic Repeat reQuest) is not present in downlink broadcast packets, since it can cause unnecessary uplink traffic from every SM for each broadcast packet. For successful transport without ARQ, the AP repeats downlink broadcast packets. The SMs filter out all repeated broadcast packets and, thus, do not transport further. The default of 2 repeats is optimum for typical uses of the network as an internet access system. In applications with heavy download broadcast such as video distribution, overall throughput is significantly improved by setting the repeat count to 1 or 0. This avoids flooding the downlink with repeat broadcast packets. Transmitter Power This value represents the combined power of the APs two transmitters. Nations and regions may regulate transmitter output power. For example 900 MHz, 5.4 GHz and 5.8 GHz modules are available as connectorized radios, which require the operator to adjust power to ensure regulatory compliance. The professional installer of the equipment has the responsibility to maintain awareness of applicable regulations. calculate the permissible transmitter output power for the module. Page 1-158 Chapter 1: Configuration Configuring radio parameters confirm that the initial power setting is compliant with national or regional regulations. confirm that the power setting is compliant following any reset of the module to factory defaults. External Gain This value needs to correspond to the published gain of the antenna used to ensure the radio will meet regulatory requirements. SM Receive Target Level See Table 46 PMP 450m AP Radio attributes - 5 GHz on page 1-146 Adjacent Channel Support For some frequency bands and products, this setting is needed if AP is operating on adjacent channels with zero guard band. Multicast VC Data Rate Multicast Repeat Count Multicast Downlink CIR This pull-down menu of the Multicast Data Control screen helps in configuring multicast packets to be transmitted over a dedicated channel at a configurable rate of 2X, 4X or 6X. The default value is Disable. If set to the default value, all multicast packets are transmitted over the Broadcast VC data path. This feature is available only for the PMP 450 Series and is not backward compatible with PMP 430 series of radios. This value is the number of packets that are repeated for every multicast VC packet received on the AP (located under Radio tab of Configuration). Multicast (like Broadcast) packets go over a VC that is shared by all SMs, so there is no guaranteed delivery. The repeat count is an attempt to improve the odds of the packets getting over the link. If the user has issues with packets getting dropped, they can use this parameter to improve the performance at the cost of the overall throughput possible on that channel. The default value is 0. This value is the committed information rate for the multicast downlink VC

(located under the Radio tab of Configuration). The default value is 0 kbps. The range of this parameter is based on the number of repeat counts. The higher the repeat count, the lower the range for the multicast downlink CIR. SM Registration Limit This parameter allows to configure the limit for maximum number of SMs that can register to a PMP AP. The configurable range is from 1 to 238. Note SM trying to register after the maximum configured limit has been reached is locked out for 15 minutes and a message is displayed at the SM.. SM Registration Control Message All: This field allows to control registration of all type 450 Platform Family SM including 450 Series SM (450i/450b/450/430) or 450i Series SM. 450i Only: This field allows to control registration of 450i Series SM only Controls whether the control messages are sent in MIMO-B or MIMO-A mode. MIMO-A is recommended. However, if an AP on 13.2 is attempting to connect to an SM on 13.1.3 or before, changing to MIMO-B may aid in getting the SM registered. Page 1-159 Chapter 1: Configuration Configuring radio parameters Receive Quality Debug To aid in link performance monitoring, the AP and SM now report the number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-QAM) and per channel (polarization). Frame Alignment Legacy Mode Note Due to CPU load, this will slightly degrade packet per second processing. Mode Behavior (non-900 MHz Behavior (FSK 900 MHz radios) radios) OFF By default, frame start is aligned with devices with Timing Port synchronization By default, frame start is aligned with FSK 900 MHz devices with Timing Port synchronization If the synchronization source changes (due to Autosync or otherwise) the radio will dynamically adjust its frame start to maintain alignment with the default frame start timing If the synchronization source changes (due to Autosync or otherwise) the radio will dynamically adjust its frame start to maintain alignment with the default frame start timing ON

(Mode 1) The radio will align with devices running software versions from 12.0 to 13.4. ON

(Mode 2) N/A The radio will align with FSK 900 MHz devices running software versions from 12.0 to 13.4. The radio will align with FSK 900 MHz devices with software versions 11.2 or older. Page 1-160 Chapter 1: Configuration Configuring radio parameters Radio page - PMP 450i SM 3 GHz The Radio tab of the PMP 450i SM 3 GHz is shown in Figure 25. Figure 25 PMP 450i SM Radio attributes - 3 GHz Page 1-161 Chapter 1: Configuration Configuring radio parameters Note Refer Table 49 PMP 450i SM Radio attributes 5 GHz on page 1-163 for parameter details Page 1-162 Chapter 1: Configuration Configuring radio parameters Radio page PMP 450i SM 5 GHz The Radio page of PMP 450i SM is explained in Table 49. Table 49 PMP 450i SM Radio attributes 5 GHz Page 1-163 Chapter 1: Configuration Configuring radio parameters Page 1-164 Chapter 1: Configuration Configuring radio parameters Page 1-165 Chapter 1: Configuration Configuring radio parameters Page 1-166 Chapter 1: Configuration Configuring radio parameters Attribute Meaning Custom Radio Frequency Scan Selection List Channel Bandwidth Scan Check the frequencies that SM has to scan for AP transmissions. See Radio Frequency Scan Selection List on page 1-200. The channel size used by the radio for RF transmission. Note Selecting multiple channel bandwidths will increase registration and re-registration times. Cyclic Prefix The cyclic prefix for which AP scanning is executed. AP Selection Method Operators may configure the method by which a scanning SM selects an AP. By default, AP Selection Method is set to Optimize for Throughput, which has been the mode of operation in releases prior to 12.0.3.1. Power Level: AP selection based solely on power level Color Code 1 Note For operation with a PMP 450m AP, select the Power Level option or Optimize for Throughput: AP selection based on throughput optimization the selection decision is based on power level (which affects the modulation state), channel bandwidth (which affects throughput) and number of SM registrations to the AP (which affects system contention performance). Color code allows you to force the SM to register to only a specific AP, even where the SM can communicate with multiple APs. For registration to occur, the color code of the SM and the AP must match. Specify a value from 0 to 254. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). SMs may be configured with up to 20 color codes. These color codes can be tagged as Primary, Secondary, or Tertiary, or Disable. When the SM is scanning for APs, it will first attempt to register to an AP that matches one of the SMs primary color codes. Failing that, the SM will continue scanning and attempt to register to an AP that matches one of the SMs secondary color codes. Failing that, the SM will continue scanning and attempt to register to an AP that matches one of the SMs tertiary color codes. This is all done in the scanning mode of the SM and will repeat until a registration has occurred. Page 1-167 Chapter 1: Configuration Configuring radio parameters Installation Color Code Color codes in the same priority group are treated equally. For example, all APs matching one of the SMs primary color codes are analyzed equally. Likewise, this evaluation is done for the secondary and tertiary groups in order. The analysis for selecting an AP within a priority group is based on various inputs, including signal strength and number of SMs already registered to each AP. The first color code in the configuration is the pre-Release 9.5 color code. Thus, it is always a primary color code for legacy reasons. The color codes can be disabled, with the exception of the first color code. With this feature enabled on the AP and SM, operators may install and remotely configure SMs without having to configure matching color codes between the modules. When using the Installation Color Code feature, ensure that the SM is configured with the factory default Color Code configuration (Color Code 1 is 0, Color Code 2-10 set to 0 and Disable). The status of the Installation Color Code can be viewed on the AP Eval web GUI page, and when the SM is registered using the Installation Color Code the message SM is registered via ICC Bridging Disabled! is displayed in red on every SM GUI page. The Installation Color Code parameter is configurable without a radio reboot for both the AP and SM. Large VC data Queue SM and BH have a configurable option used to prevent packet loss in the uplink due to bursting IP traffic. This is designed for IP burst traffic particular to video surveillance applications. Color Code Color code allows to force the BHS to register to only a specific BHM, even where the BHS can communicate with multiple BHMs. For registration to occur, the color code of the BHS and the BHM must match. Specify a value from 0 to 254. The color codes can be disabled, with the exception of the first color code. MIMO Rate Adapt Algorithm This pull-down menu helps in configuring the Rate Adapt Algorithm to MIMO-A/B, MIMO-B only, or MIMO-A only. Downlink Maximum Modulation Rate This pull-down menu helps in configuring the Downlink Maximum Modulation Rate at a configurable rate of 1X, 2X, 3X, 4X, 6X, or 8X. The default value is 8X. Uplink Maximum Modulation Rate This pull-down menu helps in configuring the Uplink Maximum Modulation Rate at a configurable rate of 1X, 2X, 3X, 4X, 6X, or 8X. The default value is 8X. External Gain This value represents the antenna gain. For ODUs with integrated antenna, this is set at the correct value in the factory. For Connectorized ODUs with external antenna, the user must set this value to the overall antenna gain, including any RF cable loss between the ODU and the antenna. Enable Max Tx Power This field allows to enable or disable maximum transmission power. Page 1-168 Chapter 1: Configuration Configuring radio parameters Reference Downlink EVM Current Downlink EVM Reference Uplink EVM Current Uplink EVM Access Point MAC Address Channel Frequency Channel Bandwidth Receive Quality Debug To aid in link performance monitoring, the AP and SM now report the number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-QAM) and per channel (polarization). Note Due to CPU load, this will slightly degrade packet per second processing. Note The frequencies that a user can select are controlled by the country or a region and the Channel Bandwidth selected. There can be a case where a user adds a custom frequency (from the Custom Frequencies page on page 1-204) and cannot see it in the pull down menu. Page 1-169 Chapter 1: Configuration Configuring radio parameters Radio page - PMP 450i AP 900 MHz The Radio tab of the PMP 450i AP 900 MHz is described in below Table 50. Table 50 PMP 450i AP Radio attributes - 900 MHz Page 1-170 Chapter 1: Configuration Configuring radio parameters Attribute Meaning Frequency Carrier Channel Bandwidth Cyclic Prefix Frame Period Color Code Subscriber Color Code Rescan (When not on a Primary Color Code) Subscriber Color Code Wait Period for Idle Installation Color Code MIMO Rate Adapt Algorithm Downlink Maximum Modulation Rate Uplink Maximum Modulation Rate Max Range Downlink Data Contention Slots

(a.k.a. Control Slots) Auto Contention Broadcast Repeat Count Transmitter Output Power External Gain SM Receive Target Level Specify the frequency for the module to transmit. The default for this parameter is None. For a list of channels in the band, see the drop-down list on the radio GUI. The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the AP and the SM. The supported Channel Bandwidths are 5, 7, 10 and 20 MHz. See Table 46 PMP 450m AP Radio attributes - 5 GHz on page 1-146. See Table 46 PMP 450m AP Radio attributes - 5 GHz on page 1-146. See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156. Multicast VC Data Rate See Table 46 PMP 450m AP Radio attributes - 5 GHz on page 1-146 Multicast Repeat Count Page 1-171 Chapter 1: Configuration Configuring radio parameters Multicast Downlink CIR Control Message Receive Quality Debug Pager Reject Filter In 900 MHz, Pager Reject filter is placed on the AP to block Pager signals which could cause interference to the whole band. The Pager signals typically operate in the 928-930 frequency range. When the filter is enabled, the signals of 920 MHz and above are attenuated which enables better reception of signals in the rest of the band. Note that the AP/SM should not be configured on the frequencies of 920 MHz and above when this filter is enabled. Frame Alignment Legacy Mode See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156. Page 1-172 Chapter 1: Configuration Configuring radio parameters Radio page - PTP 450i BHM 5 GHz The Radio page of PTP 450i BHM is explained in Table 51. Table 51 PTP 450i BHM Radio page attributes 5 GHz Page 1-173 Chapter 1: Configuration Configuring radio parameters Attribute Meaning Frequency Band Select the operating frequency band of the radio. The supported bands are 4.9 GHz, 5.4 GHz and 5.7 GHz. Frequency Carrier Specify the frequency for the module to transmit. The default for this parameter is None. For a list of channels in the band, see the drop-down list on the radio GUI. Channel Bandwidth The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the BHM and the BHS. Cyclic Prefix Frame Period Color Code OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol to allow multi-

pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. Select the Frame Period of the radio. The supported Frame Periods are: 5 ms and 2.5 ms. Specify a value from 0 to 254. For registration to occur, the color code of the BHM and the BHS must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each link a different color code. Color code allows you to force a BHS to register to only a specific BHM. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Sector ID This pull-down menu helps in configuring the Sector ID at a configurable value from 0 to 15. Large VC data Q Enable Large VC Q for applications that burst data high rates. Large Qs may decrease effective throughput for TCP application. Disable Large VC Q if application need not handle bursts of data. Large Qs may decrease effective throughput for TCP application. MIMO Rate Adapt Algorithm This pull-down menu helps in configuring the Rate Adapt Algorithm to MIMO-A/B, MIMO-B only, or MIMO-A only. Page 1-174 Chapter 1: Configuration Configuring radio parameters Downlink Maximum Modulation Rate This pull-down menu helps in configuring the Downlink Maximum Modulation Rate at a configurable rate of 1X, 2X, 3X, 4X, 6X, or 8X. The default value is 8X. The Rate Adapt Algorithm does not allow the modulation to go beyond this limit. Uplink Maximum Modulation Rate This pull-down menu helps in configuring the Uplink Maximum Modulation Rate at a configurable rate of 1X, 2X, 3X, 4X, 6X, or 8X. The default value is 8X. The Rate Adapt Algorithm does not allow the modulation to go beyond this limit. Minimum Modulation Rate This pull-down menu helps in configuring the Minimum Modulation Rate at a configurable rate of 1X, 2X, 3X, 4X, 6X, or 8X. The default value is 1X. If the Rate Adapt Algorithm is below this limit, then bridging is disabled. This is used if PTP network can route the traffic through another path. Downlink Data Transmit Power External Gain Receive Quality Debug Specify the percentage of the aggregate throughput for the downlink

(frames transmitted from the BHM to the subscriber). For example, if the aggregate (uplink and downlink total) throughput on the BHM is 132 Mbps, then 75% specified for this parameter allocates 99 Mbps for the downlink and 33 Mbps for the uplink. The default for this parameter is 50%. This parameter must be set in the range of 15% - 85%, otherwise the invalid input will not be accepted and the previously-entered valid setting is used. Note In order to prevent self-interference, the frame configuration needs to align. This includes Downlink Data, Max Range and Contention slots. This value represents the combined power of the BHMs two transmitters. Nations and regions may regulate transmit power. For example PTP 450i Series modules are available as connectorized radios, which require the operator to adjust power to ensure regulatory compliance. The professional installer of the equipment has the responsibility to:

Maintain awareness of applicable regulations. Calculate the permissible transmitter output power for the module. Confirm that the initial power setting is compliant with national or regional regulations. Confirm that the power setting is compliant following any reset of the module to factory defaults. This value needs to correspond to the published gain of the antenna used to ensure the radio will meet regulatory requirements. To aid in link performance monitoring, the BHM and BHS now report the number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-QAM and 256-QAM) and per channel (polarization). Page 1-175 Chapter 1: Configuration Configuring radio parameters Note Due to CPU load, this slightly degrades the packet during per second processing. See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156. Frame Alignment Legacy Mode Radio page PTP 450i BHS 5 GHz The Radio page of PTP 450i BHS is explained in Table 52. Table 52 PTP 450i BHS Radio attributes 5 GHz Page 1-176 Chapter 1: Configuration Configuring radio parameters Page 1-177 Chapter 1: Configuration Configuring radio parameters Attribute Meaning Custom Radio Frequency Scan Selection List Channel Bandwidth Scan Check any frequency that you want the BHS to scan for BHM transmissions. See Radio Frequency Scan Selection List on page 1-200. The channel size used by the radio for RF transmission. Note Selecting multiple channel bandwidths will increase registration and re-registration times. Cyclic Prefix Scan The cyclic prefix for which BHM scanning is executed. Color Code Color code allows to force the BHS to register to only a specific BHM, even where the BHS can communicate with multiple BHMs. For registration to occur, the color code of the BHS and the BHM must match. Specify a value from 0 to 254. The color codes can be disabled, with the exception of the first color code. Page 1-178 Chapter 1: Configuration Configuring radio parameters Large VC data Q BHM and BHS have a configurable option used to prevent packet loss in the uplink due to bursting IP traffic. This is designed for IP burst traffic particular to video surveillance applications. MIMO Rate Adapt Algorithm This pull-down menu helps in configuring the Rate Adapt Algorithm to MIMO-A/B, MIMO-B only, or MIMO-A only. Downlink Maximum Modulation Rate This pull-down menu helps in configuring the Downlink Maximum Modulation Rate at a configurable rate of 1X, 2X, 3X, 4X, 6X, or 8X. The default value is 8X. The Rate Adapt Algorithm does not allow the modulation to go beyond this limit. Uplink Maximum Modulation Rate This pull-down menu helps in configuring the Uplink Maximum Modulation Rate at a configurable rate of 1X, 2X, 3X, 4X, 6X, or 8X. The default value is 8X. The Rate Adapt Algorithm does not allow the modulation to go beyond this limit. Minimum Modulation Rate This pull-down menu helps in configuring the Minimum Modulation Rate at a configurable rate of 1X, 2X, 3X, 4X, 6X, or 8X. The default value is 1X. If the Rate Adapt Algorithm is below this limit, then bridging is disabled. This is used if PTP network can route the traffic through another path. Transmit Power Refer Table 51 PTP 450i BHM Radio page attributes 5 GHz on page 1-173 External Gain Receive Quality Debug Page 1-179 Chapter 1: Configuration Configuring radio parameters PMP/PTP 450b Series - configuring radio Radio page PMP/PTP 450b Mid-Gain/High Gain SM 5 GHz The Radio page of PMP/PTP 450b Mid-Gain/High Gain SM is explained in Table 53. Table 53 PMP/PTP 450b Mid-Gain/High Gain SM Radio attributes 5 GHz Page 1-180 Chapter 1: Configuration Configuring radio parameters Page 1-181 Chapter 1: Configuration Configuring radio parameters Attribute Meaning Custom Radio Frequency Scan Selection List Channel Bandwidth Scan Check the frequencies that SM has to scan for AP transmissions. See Radio Frequency Scan Selection List on page 1-200. The channel size used by the radio for RF transmission. Note Selecting multiple channel bandwidths will increase registration and re-registration times. Cyclic Prefix Scan The cyclic prefix for which AP scanning is executed. AP Selection Method Operators may configure the method by which a scanning SM selects an AP. By default, AP Selection Method is set to Optimize for Throughput, which has been the mode of operation in releases prior to 12.0.3.1. Power Level: AP selection based solely on power level Color Code 1 Note For operation with a PMP 450m AP, select the Power Level option or Optimize for Throughput: AP selection based on throughput optimization the selection decision is based on power level (which affects the modulation state), channel bandwidth (which affects throughput) and number of SM registrations to the AP (which affects system contention performance). Color code allows you to force the SM to register to only a specific AP, even where the SM can communicate with multiple APs. For registration to occur, the color code of the SM and the AP must match. Specify a value from 0 to 254. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Page 1-182 Chapter 1: Configuration Configuring radio parameters SMs may be configured with up to 20 color codes. These color codes can be tagged as Primary, Secondary, or Tertiary, or Disable. When the SM is scanning for APs, it will first attempt to register to an AP that matches one of the SMs primary color codes. Failing that, the SM will continue scanning and attempt to register to an AP that matches one of the SMs secondary color codes. Failing that, the SM will continue scanning and attempt to register to an AP that matches one of the SMs tertiary color codes. This is all done in the scanning mode of the SM and will repeat until a registration has occurred. Color codes in the same priority group are treated equally. For example, all APs matching one of the SMs primary color codes are analyzed equally. Likewise, this evaluation is done for the secondary and tertiary groups in order. The analysis for selecting an AP within a priority group is based on various inputs, including signal strength and number of SMs already registered to each AP. The first color code in the configuration is the pre-Release 9.5 color code. Thus, it is always a primary color code for legacy reasons. The color codes can be disabled, with the exception of the first color code. With this feature enabled on the AP and SM, operators may install and remotely configure SMs without having to configure matching color codes between the modules. When using the Installation Color Code feature, ensure that the SM is configured with the factory default Color Code configuration (Color Code 1 is 0, Color Code 2-10 set to 0 and Disable). The status of the Installation Color Code can be viewed on the AP Eval web GUI page, and when the SM is registered using the Installation Color Code the message SM is registered via ICC Bridging Disabled! is displayed in red on every SM GUI page. The Installation Color Code parameter is configurable without a radio reboot for both the AP and SM. Installation Color Code Large VC data Queue SM and BH have a configurable option used to prevent packet loss in the uplink due to bursting IP traffic. This is designed for IP burst traffic particular to video surveillance applications. MIMO Rate Adapt Algorithm This pull-down menu helps in configuring the Rate Adapt Algorithm to MIMO-A/B, MIMO-B only, or MIMO-A only. Downlink Maximum Modulation Rate This pull-down menu helps in configuring the Downlink Maximum Modulation Rate at a configurable rate of 1X, 2X, 3X, 4X, 6X, or 8X. The default value is 8X. Uplink Maximum Modulation Rate This pull-down menu helps in configuring the Uplink Maximum Modulation Rate at a configurable rate of 1X, 2X, 3X, 4X, 6X, or 8X. The default value is 8X. External Gain Fixed This value represents the fixed antenna gain. The fixed antenna gain for Mid-

Gain is 16 dBi and High Gain is 23 dBi. For ODUs with integrated antenna, this is set at the correct value in the factory. Page 1-183 Chapter 1: Configuration Configuring radio parameters For Connectorized ODUs with external antenna, the user must set this value to the overall antenna gain, including any RF cable loss between the ODU and the antenna. Enable Max Tx Power This field allows to enable or disable maximum transmission power. Receive Quality Debug To aid in link performance monitoring, the AP and SM now report the number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-QAM) and per channel (polarization). Note The frequencies that a user can select are controlled by the coun Channel Bandwidth selected. There can be a case where a user ad

(from the Custom Frequencies page on page 1-204) and cannot s menu. Page 1-184 Chapter 1: Configuration Configuring radio parameters PMP/PTP 450 Series configuring radio Radio page - PMP 450 AP 5 GHz The Radio tab of the AP for 5 GHz is as shown in Table 54. Table 54 PMP 450 AP Radio attributes - 5 GHz Page 1-185 Chapter 1: Configuration Configuring radio parameters Attribute Meaning See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156. Radio Configuration, Frame Configuration, Power Control, Multicast Data Control and Advance tab SM Registration Limit PMP 430 SM Registration PMP 450/430 Legacy Mode Control Messages See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156. PMP 430 Interop Mode Receive Quality Debug Frame Alignment Legacy Mode Page 1-186 Chapter 1: Configuration Configuring radio parameters Radio page - PMP 450 AP 3.65 GHz Table 55 PMP 450 AP Radio attributes - 3.65 GHz Attribute Meaning See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156. Radio Configuration, Frame Configuration, Power Control, Multicast Data Control and Advance tab Note When the Channel bandwidth is updated from 20 MHz to 30 MHz not more than 59 subscribers can be registered. Page 1-187 Chapter 1: Configuration Configuring radio parameters Radio page - PMP 450 AP 3.5 GHz Table 56 PMP 450 AP Radio attributes - 3.5 GHz Attribute Meaning See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156. Radio Configuration, Frame Configuration, Power Control, Multicast Data Control and Advance tab Page 1-188 Chapter 1: Configuration Configuring radio parameters Radio page - PMP 450 AP 2.4 GHz Table 57 PMP 450 AP Radio attributes - 2.4 GHz Page 1-189 Chapter 1: Configuration Configuring radio parameters Attribute Meaning See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156. Radio Configuration, Frame Configuration, Power Control, Multicast Data Control and Advance tab Radio page - PMP 450 SM 5 GHz Table 58 PMP 450 SM Radio attributes 5 GHz Page 1-190 Chapter 1: Configuration Configuring radio parameters Attribute Meaning Custom Radio Frequency Scan Selection List Check the frequencies that SM has to scan for AP transmissions. See Radio Frequency Scan Selection List on page 1-200. See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156. Page 1-191 Chapter 1: Configuration Configuring radio parameters Radio page - PMP 450 SM 3.65 GHz Table 59 PMP 450 SM Radio attributes 3.65 GHz Attribute Meaning Custom Radio Frequency Scan Selection List Check the frequencies that SM has to scan for AP transmissions. See Radio Frequency Scan Selection List on page 1-200. See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156. Page 1-192 Chapter 1: Configuration Configuring radio parameters Radio page - PMP 450 SM 3.5 GHz Table 60 PMP 450 SM Radio attributes 3.5 GHz Attribute Meaning Custom Radio Frequency Scan Selection List Check the frequencies that SM has to scan for AP transmissions. See Radio Frequency Scan Selection List on page 1-200. See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156. Page 1-193 Chapter 1: Configuration Configuring radio parameters Radio page - PMP 450 SM 2.4 GHz Table 61 PMP 450 SM Radio attributes 2.4 GHz Page 1-194 Chapter 1: Configuration Configuring radio parameters Attribute Meaning Custom Radio Frequency Scan Selection List Check the frequencies that SM has to scan for AP transmissions. See Radio Frequency Scan Selection List on page 1-200. See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156. Attribute Meaning Custom Radio Frequency Scan Selection List Check the frequencies that SM has to scan for AP transmissions. See Radio Frequency Scan Selection List on page 1-200. Page 1-195 Chapter 1: Configuration Configuring radio parameters Radio page - PMP 450 SM 900 MHz Table 62 PMP 450 SM Radio attributes 900 MHz Attribute Meaning Custom Radio Frequency Scan Selection List See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156. Page 1-196 Chapter 1: Configuration Configuring radio parameters See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156. Channel Bandwidth Scan Cyclic Prefix Scan AP Selection Method Color Code 1 Installation Color Code Large VC data Queue Color Code External Gain See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156 Enable Max Tx Power See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156 Receive Quality Debug See Table 48 PMP 450i AP Radio attributes - 5 GHz on page 1-156. Note The frequencies that a user can select are controlled by the country or a region and the Channel Bandwidth selected. There can be a case where a user adds a custom frequency

(from the Custom Frequencies page on page 1-204) and cannot see it in the pull down menu. Page 1-197 Chapter 1: Configuration Configuring radio parameters Radio page - PTP 450 BHM 5 GHz Table 63 PTP 450 BHM Radio attributes 5 GHz Attribute Meaning Refer Table 51 PTP 450i BHM Radio page attributes 5 GHz on page 1-173 for all parameters details. Page 1-198 Chapter 1: Configuration Configuring radio parameters Radio page - PTP 450 BHS 5 GHz Table 64 PTP 450 BHM Radio attributes 5 GHz Page 1-199 Chapter 1: Configuration Configuring radio parameters Attribute Meaning Refer Table 52 PTP 450i BHS Radio attributes 5 GHz on page 1-176 for all parameters details. Radio Frequency Scan Selection List The SM or BHS scans complete spectrum as per Full Spectrum Band Scan feature. SMs or BHS first boot into the smallest selected channel bandwidth (10 MHz, if selected) and scan all selected frequencies across both the 5.4 GHz and 5.7 GHz frequency bands. After this scan, if a wider channel bandwidth is selected (20 MHz), the SM/BHS automatically changes to 20 MHz channel bandwidth and then scans for APs/BHSs. After the SM/BHS finishes this final scan it will evaluate the best AP/BHM with which to register. If required for registration, the SM/BHS changes its channel bandwidth back to 10 MHz to match the best AP/BHM. The SM/BHS will attempt to connect to an AP/BHM based on power level (which affects the modulation state), channel bandwidth (which affects throughput) and number of SM/BHS registrations to the AP/BHM (which affects system contention performance). If it is desired to prioritize a certain AP/BHM over other available APs/BHMs, operators may use the Color Code Priority feature on the SM/BHS. Utilization of the Color Code feature on the AP/BHM is recommended to further constrain the AP selection. If the SM does not find any suitable APs/BHMs for registration after scanning all channel bandwidths, the SM restarts the scanning process beginning with the smallest configured channel bandwidth. Selecting multiple frequencies and multiple channel bandwidths impacts the SM/BHS scanning time. The biggest consumption of time is in the changing of the SM/BHS channel bandwidth setting. The worst case scanning time is approximately two minutes after boot up (SM/BHS with all frequencies and channel bandwidths selected and registering to an AP/BHM at 10 MHz). If only one channel bandwidth is selected the time to scan all the available frequencies and register to an AP/BHM is approximately one minute after boot up. Other scanning features such as Color Code, Installation Color Code, and RADIUS authentication are unaffected by the Full Band Scan feature. Page 1-200 Chapter 1: Configuration Configuring radio parameters Dedicated Multicast Virtual Circuit (VC) A Multicast VC allows to configure multicast packets to be transmitted over a dedicated channel at a configurable rate of 1X, 2X, 4X or 8X. This feature is available only for the PMP 450 and PMP 450i and is not backward compatible with PMP 430 series of radios. To configure Multicast VC, the AP must have this enabled. This can be enabled in the Multicast Data Control section (under Configuration > Radio page). The default value is Disable. If set to the default value, all multicast packets are transmitted over the Broadcast VC data path. To enable, select the data rate that is desired for the Multicast VC Data Rate parameter and click Save Changes button. The radio requires no reboot after any changes to this parameter. The multicast VC allows three different parameters to be configured on the AP. These can be changed on the fly and are saved on the flash memory. Note If the Multicast VC Data Rate is set to a modulation that the radio is not currently capable of or operates in non-permitted channel conditions, multicast data is sent but not received. Ex: If Multicast VC Data Rate is set to 6x and the channel conditions only permit 4x mode of operation, then multicast data is sent at 6x modulation but the SM will not receive the data. Note The PMP 450 AP supports up to 119 VCs (instead of 238 VCs) when configured for 30 MHz channel bandwidth or 5 ms Frame Period. This limitation is not applicable for PMP 450i/450m Series. Note Actual Multicast CIR honored by the AP = Configured Multicast CIR/ (Multicast Repeat Count + 1). Increasing the Multicast data rate has no impact on the Unicast data rate. For multicast and unicast traffic mix scenario examples, see Table 65. Page 1-201 Chapter 1: Configuration Configuring radio parameters Table 65 Example for mix of multicast and unicast traffic scenarios Repeat Count Multicast Data Rate (Mbps) Unicast Data Rate (Mbps) Aggregate DL Data Rate (Mbps) 0 1 2 10 5 3.33 40 40 40 50 45 43.33 The statistics have been added to the Data VC page (under Statistics > Data VC). The table displays the multicast row on the PMP 450 Platform Family AP. The SM displays the multicast row if it is a PMP 450 Platform Family. Figure 26 Multicast VC statistics The AP and SM display Transmit and Receive Multicast Data Count (under the Statistics > Scheduler page), as shown in Figure 27. Page 1-202 Chapter 1: Configuration Configuring radio parameters Figure 27 Multicast scheduler statistics Page 1-203 Chapter 1: Configuration Configuring radio parameters Custom Frequencies page In addition to the Radio tab, AP/SM/BH has another tab called Custom Frequencies as shown in Table 66. The custom frequency tab allows to configure custom frequency at 1 KHz raster. It means that the custom frequencies can be at granularity of 1 KHz e.g. 4910.123 MHz, 4922.333 MHz, 4933.421 MHz etc. Note Ensure that a customer frequency exists before using SNMP to set the radio to a Custom Frequency. Table 66 450 Platform Family AP/SM/BH Custom Frequencies page 5 GHz Attribute Meaning Custom Frequency Configuration Custom frequencies with a channel raster of 1 KHz can be added from the available range by keying in the frequency and then clicking the Add Frequency button. Click Remove Frequency button to delete a specific frequency keyed in the text box. Click Default Frequencies button to add a pre-defined list of frequencies that can be used in this band. This list can be reduced or increased by manually removing or adding other custom frequencies. Custom Frequencies Displays the complete list of user configured custom frequencies. Page 1-204 Chapter 1: Configuration Configuring radio parameters Table 67 PMP/PTP 450 SM/BH Custom Frequencies page 3.65 GHz Attribute Meaning Custom Frequency Configuration Custom frequencies with a channel raster of 1 KHz can be added from the available range by keying in the frequency and then clicking the Add Frequency button. Click Remove Frequency button to delete a specific frequency keyed in the text box. Click Default Frequencies button to add a pre-defined list of frequencies that can be used in this band. This list can be reduced or increased by manually removing or adding other custom frequencies. Custom Frequencies Displays the complete list of user configured custom frequencies. Page 1-205 Chapter 1: Configuration Configuring radio parameters Table 68 PMP/PTP 450 SM/BH Custom Frequencies page 3.5 GHz Attribute Meaning Custom Frequency Configuration Custom frequencies with a channel raster of 1 KHz can be added from the available range by keying in the frequency and then clicking the Add Frequency button. Click Remove Frequency button to delete a specific frequency keyed in the text box. Click Default Frequencies button to add a pre-defined list of frequencies that can be used in this band. This list can be reduced or increased by manually removing or adding other custom frequencies. Page 1-206 Chapter 1: Configuration Configuring radio parameters DFS for 5 GHz Radios Dynamic Frequency Selection (DFS) is a requirement in several countries and regions for 5 GHz unlicensed systems to detect radar systems and avoid co-channel operation. DFS and other regulatory requirements drive the settings for the following parameters, as discussed in this section:

Country Code Primary Frequency Alternate 1 and Alternate 2 Frequencies External Antenna Gain On the AP, the Home > DFS Status page shows current DFS status of all three frequencies and a DFS log of past DFS events. Figure 28 AP DFS Status DFS operation The ODUs use region-specific DFS based on the Country Code selected on the modules Configuration, General page. By directing installers and technicians to set the Country Code correctly, the operator gains confidence the module is operating according to national or regional regulations without having to deal with the details for each region. The details of DFS operation for each Country Code, including whether DFS is active on the AP, SM, and which DFS regulations apply is shown in Table 172 on page 4-61. Page 1-207 Chapter 1: Configuration Contention slots Configuring radio parameters Contention slots are symbols at the end of the uplink subframe that are reserved for random access

(network entry and bandwidth requests) and cannot be used for data transmission. These symbols form the contention space. The frame is 2.5 ms or 5 ms long, and it is divided into a downlink subframe (data transmitted from the AP to the SM) and an uplink subframe (data transmitted from the SM to the AP). Figure 29 Frame structure The symbols in the uplink subframe can be scheduled or unscheduled. All scheduled symbols come before all unscheduled symbols. The number of scheduled and unscheduled symbols changes frame by frame depending on the amount of uplink requests received by the AP. The contention slots number is selected by the operator and indicates the number of symbols that are reserved in the unscheduled portion of the uplink. The total number of unscheduled symbols in each frame is the sum of the contention slots and any additional symbol that was not used in uplink data transmission. This means that the unscheduled portion of the uplink can be as small as the number of contention slots, or as big as the whole uplink. This allows SMs in sectors with a small number of contention slots configured to still successfully transmit bandwidth requests using unused data slots. Random access When an SM needs to send an unscheduled message (for network entry or a bandwidth request), it randomly selects one symbol out of the unscheduled portion of the uplink subframe and uses that symbol for transmission. The higher the number of unscheduled symbols, the lower the probability two or more SMs will select the same symbol for transmission and their messages will collide. When two messages collide at the AP receiver, most likely neither will be decoded correctly, and both SMs need to start the random-access process one more time. If this happens frequently, the latency of the system increases. A higher number of contention slots give higher probability that an SMs bandwidth request will be correctly received when the system is heavily loaded, but with the tradeoff that sector capacity is reduced, so there will be less capacity to handle the request. The sector capacity reduction is about 200 kbps for each contention slot configured in a 20 MHz channel at QPSK SISO modulation, for 2.5 ms frame sizes. The reduction in sector capacity is proportionally higher at MIMO modulations, as shown in the following table. Page 1-208 Chapter 1: Configuration Configuring radio parameters Table 69 Throughput penalty per modulation Modulation mode Throughput penalty for each additional contention slot 2.5 ms frame 5 ms frame QPSK SISO (1X) QPSK MIMO (2X) 16-QAM MIMO (4X) 64-QAM MIMO (6X) 256-QAM MIMO (8X) 204 kbps 409 kbps 819 kbps 1.22 Mbps 1.63 Mbps 102 kbps 204 kbps 409 kbps 614 kbps 819 kbps Table 69 shows that the throughput penalty for each additional contention slot increases with modulation mode. The reason is that at higher modulation modes more fragments can be transmitted in a symbol. If additional symbols are reserved for random access, the number of fragments that cannot be sent in these symbols is higher at higher modulations, and therefore the throughput penalty is higher. However, the penalty expressed as a percentage of the throughput is the same for each modulation mode. For example, if a frame has 80 total symbols, each additional symbol reserved for random access reduces the sector throughput by 1.25%, regardless of the modulation mode. Selection of contention slots parameter The number of contention slots has to be selected according to the specific deployment parameters in each sector. If the number of contention slots is too small, then latency increases in high traffic periods. If the number of contention slots is too high, then the maximum capacity is unnecessarily reduced. The two main contributing factors to the selection of the number of contention slots are the number of SMs in a sector, and the type of traffic in the sector. Number of SMs in a sector If the number of SMs in a sector is large, it is recommended to increase the number of contention slots, in order to reduce the probability of two or more requests colliding. The suggested contention slot settings as a function of the number of active Data channels in the sector are shown in Table 70. Table 70 Contention slot settings Number of SMs Recommended Number of Contention slots 1 to 10 11 to 50 51 to 150 151 and above 3 4 6 8 Page 1-209 Chapter 1: Configuration Configuring radio parameters Type of traffic in a sector Besides the number of SMs, the other main factor in contention slots selection is the type of traffic. If the sector experiences a lot of uplink traffic composed of small packets, for example in a sector that serves several VoIP streams, the average number of bandwidth requests transmitted by each SM is high. Another scenario with constant uplink traffic is video surveillance, which also generate a large number of uplink bandwidth requests. In these cases, the probability of two or more SMs transmitting a request in the same symbol is high. When this happens, the latency of the system increases, and it is recommended to increase the number of contention slots from the number in Table 70. If an AP is experiencing latency or SM-servicing issues, increasing the number of contention slots may increase system performance, depending on traffic mix over time. Recommendation on Contention Slots number selection 1. Calculate the number of active SMs in the sector. 2. Evaluate the traffic mix that is expected in the sector, more specifically the expected percentage of real-time traffic (ex. VoIP, gaming, video conferencing, and video surveillance). 3. 4. If the expected amount of real-time traffic is small, select the number of contention slots according to Table 70. If the expected amount of real-time traffic is large, select a number of contention slots larger than the number in Table 70. 5. Monitor latency in your system. If the percentage of real-time traffic increases and the sector experiences increasing latency and SM-servicing issues, increase the number of contention slots from the current setting. This is the reason why the maximum number of contention slots is 15, even if Table 2 shows 8 contention slots for more than 150 data channels. If the number of data channels is more than 150 and a significant portion of the traffic is real-time, the frequency with which bandwidth request messages are transmitted requires a higher number of contention slots, potentially as high as 15. A sector with a high number of video surveillance cameras would also require a larger number of contention slots to reduce the probability of collision between requests. 6. Monitor the percentage of BW requests successfully received and the UL frame utilization: if the frame utilization is high (close to 100%), then it is not recommended to change the number of contention slots, even if the percentage success rate of BW requests is low. However, if the percentage success rate of BW requests is low and the frame utilization is also low, then increasing the number of contention slots is recommended. Page 1-210 Chapter 1: Configuration Configuring radio parameters Cluster of APs It is recommended to use care when changing the contention slots configuration of only some APs in a cluster, because changes affect the effective downlink/uplink ratio and can cause co-location issues. In a typical cluster, each AP should be configured with the same number of contention slots to assure proper timing in the send and receive cycles. The number of contention slots is used by the frame calculator to define the downlink and uplink times, which should not overlap from one AP to another. However, if the traffic experienced by two APs in the same cluster is different (for example, one supports significantly more VoIP traffic), the number of contention slots selected for each AP may not be the same. For APs in a cluster of mismatched contention slots setting, it is recommended to use the frame calculator to verify that send and receive times do not overlap (see the Frame calculator for co-

location). Note Change contention slot configuration in an operating, stable system cautiously and with a back-out plan. After changing a contention slot configuration, monitor the system closely for problems as well as improvements in system performance. Frame calculator for co-location The frame calculator is a tool available for the PMP 450 series systems, that calculates the length of the transmit and receive times, together with the number of downlink and uplink symbols, for a given set of configuration parameters. The frame calculator can be used to verify that co-location of APs using different contention slots settings does not create overlapping transmit and receive times. Basic rules For co-location of AP1 and AP2, we want to ensure that AP1 stops transmitting before AP2 starts receiving, and that AP2 stops transmitting before AP1 starts receiving. These are the rules that have to be satisfied for a correct co-location of the two APs:

AP1 Receive Start > AP2 Transmit End AP2 Receive Start > AP1 Transmit End Steps for co-location Let us assume that in a cluster of multiple APs with all the same settings, one APs settings are modified with a different number of contention slots. 1. Obtain all configuration settings for the APs that do not change parameters (duty cycle, contention slots, max distance) Input these configuration parameters into the OFDM Frame Calculator tool found under Tools. 2. 3. Click Calculate 4. Note the following values from the results:

AP Antenna Transmit End: ____________________ AP Antenna Receive Start: ____________________ 5. Access the AP that needs to have a different contention slots setting and use the frame calculator tool found under Tools Page 1-211 Chapter 1: Configuration Configuring radio parameters 6. Input the configuration parameters for this AP (same duty cycle and max distance as the other APs, different contention slots) 7. Click Calculate 8. Note the following values from the results:

AP Antenna Transmit End: ____________________ AP Antenna Receive Start: ____________________ 9. Check that the two following equations are both true:

AP1 Receive Start > AP2 Transmit End AP2 Receive Start > AP1 Transmit End 10. If one or both equations are not true, adjust the duty cycle until they become true (or the max distance if possible). Example Let us assume that all APs in a cluster have the same Max range settings, a 2.5 ms frame length and a 20 MHz channel BW, but the operator has fine-tuned the DL duty % per AP as follows:

AP1:

AP2:

Max range: 2 miles Contention slots: 3 DL duty cycle = 75%

Max range: 2 miles Contention slots: 3 DL duty cycle = 80%

Running the frame calculator as explained in the Steps for co-location, the AP1 Antenna Transmit End and Antenna Receive start times are:

AP1 Antenna Transmit End = 1.6440 ms AP1 Antenna Receive Start = 1.7972 ms AP2s Antenna Transmit End and Antenna Receive start times are:

AP2 Antenna Transmit End = 1.7411 ms AP2 Antenna Receive Start = 1.8943 ms The settings in AP1 in the cluster are now modified by changing the number of contention slots from 3 to 7, for example because this sector is constantly experiencing a higher volume of VoIP traffic. Running the frame calculator again, the new AP1 Antenna Transmit End and Antenna Receive start times are:

AP1 Antenna Transmit End = 1.5711 ms AP1 Antenna Receive Start = 1.7243 ms The two equations above have to be checked for correct co-location:

AP1 Antenna Receive Start > AP2 Antenna Transmit End 1.7243 ms >1.7411 ms NOT OK AP2 Antenna Receive Start > AP1 Antenna Transmit End 1.8943 ms >1.5711ms OK The first of the two equations are not true. AP2 is still transmitting when AP1 has already started receiving. This creates interference at the AP1 receiver. Page 1-212 Chapter 1: Configuration Configuring radio parameters To avoid this interference scenario, the duty cycle of AP2 can be further adjusted slightly. For example, changing the duty cycle of AP2 from 80% to 79% changes the AP2 Antenna Transmit End and Antenna Receive start times as follows:

AP2 Antenna Transmit End = 1.7168 ms AP2 Antenna Receive Start = 1.8700 ms The two equations have to be checked again for co-location:

AP1 Antenna Receive Start > AP2 Transmit End 1.7243 ms >1.7168 ms OK AP2 Receive Start > AP1 Transmit End 1.8700 ms >1.5711 ms OK Now both equations are true and the APs can be co-located. Cambium co-location tool As an alternative to using the frame calculator on the AP GUI, cambium provides a co-location tool for these calculations. This tool is a free download available on the Cambium website:

https://support.cambiumnetworks.com/files/colocationtool/#r2 PMP/PTP 450/450i/450m CO-LOCATION TOOL AND THROUGHPUT CALCULATOR Release 15.1.1 Device 1 Configuration Device 2 Configuration Mode Channel Bandwidth (MHz) Max Range (mi) One way air delay (ns) Calculated PTP range (mi) Dowlink Data Contention slots Frame Period (ms) PMP 20 2 10000 1.861 75%

3 2.5 Device 1 Timing (ms) DL end UL start DL/UL symbols DL/UL/Total Throughput (Mbps) 1.644 1.797 61/20 98.3/31.1/129.4 Mode Channel Bandwidth (MHz) Max Range (mi) One way air delay (ns) Calculated PTP range (mi) Downlink Data Contention Slots Frame Period (ms) PMP 20 2 10000 1.861 80%

3 2.5 Device 2 Timing (ms) DL end UL start DL/UL symbols DL/UL/Total Throughput (Mbps) 1.741 1.894 65/16 104.9/24.6/129.5 Co-location not possible with mismatched frame lengths Device 1 DL end Device 2 DL end 1.644 1.741

<

<

CHECKS Device 2 UL start Device 1 UL start 1.894 1.797 OK OK MIMO-A mode of operation 450 Platform Family supports MIMO-B mode using the following modulation levels: QPSK, 16-QAM, 64-

QAM and 256-QAM. System Release 13.2 introduces MIMO-A mode of operation using the same modulation levels as the MIMO-B mode. With MIMO-B, the radio sends different streams of data over the two antennas whereas with MIMO-A, the radio uses a scheme that tries to optimize coverage by transmitting the same data over both antennas. This redundancy improves the signal to noise ratio at the receiver making it more robust, at the cost of throughput. In addition to introducing MIMO-A modes, improvements have been made to the existing rate adapt algorithm to switch between MIMO-A and MIMO-B seamlessly without any intervention or added configuration by the operator. The various modulation levels used by the 450 Platform Family are shown in Table 71. Page 1-213 Chapter 1: Configuration Configuring radio parameters Table 71 450 Platform Family Modulation levels Rate QPSK 16-QAM 64-QAM MIMO-B MIMO-A 2X MIMO-B 1X MIMO-A 4X MIMO-B 2X MIMO-A 6X MIMO-B 3X MIMO-A 256-QAM 8X MIMO-B 4X MIMO-A System Performance For System Performance details of all the 450 Platform Family ODUs, refer to the tools listed below:

Link Capacity Planner for PMP/PTP 450 and 450i:

https://support.cambiumnetworks.com/files/capacityplanner/

LINKPlanner for PMP/PTP 450/450i and PMP 450m:

https://support.cambiumnetworks.com/files/linkplanner/

Page 1-214 Chapter 1: Configuration Configuring radio parameters Table 72 Co-channel Interference per (CCI) MCS MCS of Victim MCS of Interferer Channel BW (MHz) CCI 1X (QPSK SISO) 6X (64-QAM MIMO-B) 2X (16-QAM SISO) 6X (64-QAM MIMO-B) 3X (64-QAM SISO) 6X (64-QAM MIMO-B) 1X (QPSK MIMO-A) 6X (64-QAM MIMO-B) 2X (16-QAM MIMO-A) 6X (64-QAM MIMO-B) 3X (64-QAM MIMO-A) 6X (64-QAM MIMO-B) 4X (256-QAM MIMO-A) 6X (64-QAM MIMO-B) 2X (QPSK MIMO-B) 6X (64-QAM MIMO-B) 4X (16-QAM MIMO-B) 6X (64-QAM MIMO-B) 6X (64-QAM MIMO-B) 6X (64-QAM MIMO-B) 8X (256-QAM MIMO-B) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20, 30, or 40 10 dB 5, 7, 10, 15, 20, 30, or 40 17 dB 5, 7, 10, 15, 20, 30, or 40 25 dB 5, 7, 10, 15, 20, 30, or 40 7 dB 5, 7, 10, 15, 20, 30, or 40 14 dB 5, 7, 10, 15, 20, 30, or 40 22 dB 5, 7, 10, 15, 20, 30, or 40 30 dB 5, 7, 10, 15, 20, 30, or 40 10 dB 5, 7, 10, 15, 20, 30, or 40 17 dB 5, 7, 10, 15, 20, 30, or 40 25 dB 5, 7, 10, 15, 20, 30, or 40 33 dB Page 1-215 Chapter 1: Configuration Configuring radio parameters Table 73 Adjacent Channel Interference (ACI) per MCS MCS of Victim MCS of Interferer Channel BW (MHz) Guard Band 1X (QPSK SISO) 6X (64-QAM MIMO-B) 2X (16-QAM SISO) 6X (64-QAM MIMO-B) 3X (64-QAM SISO) 6X (64-QAM MIMO-B) 1X (QPSK MIMO-A) 6X (64-QAM MIMO-B) 2X (16-QAM MIMO-A) 6X (64-QAM MIMO-B) 3X (64-QAM MIMO-A) 6X (64-QAM MIMO-B) 4X (256-QAM MIMO-A) 6X (64-QAM MIMO-B) 2X (QPSK MIMO-B) 6X (64-QAM MIMO-B) 4X (16-QAM MIMO-B) 6X (64-QAM MIMO-B) 6X (64-QAM MIMO-B) 6X (64-QAM MIMO-B) 8X (256-QAM MIMO-B) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 5, 7, 10, 15, 20, 30, or 40 None None None None None None None None None None None Guard Band When synchronized, no Guard Bands are needed for the 450*, 450i, and 450m Series. For PMP 450 AP (3.6 GHz) and 450 series APs with 450b SM (5 GHz) connected, Configuration ->

Radio -> Power Control -> Adjacent Channel Support must be enabled. Improved PPS performance of 450 Platform Family The 450m, 450i, and 450b Series provides improved packets per second (PPS) performance compared to 450 Series. Page 1-216 Chapter 1: Configuration Configuring radio parameters Through hardware and software enhancements, the PPS performance of the PMP 450i Series AP and PMP 450b SM has been improved to 40k packets/second, measured through a standard RFC2544 test using 64 bytes packets. With this enhancement, operators are able to provide higher bandwidth including better VoIP and video services to end customers using existing SM deployments. PMP 450m is capable of supporting more than 100k PPS (packets per second). Page 1-217 Chapter 1: Configuration Setting up SNMP agent Setting up SNMP agent Operators may use SNMP commands to set configuration parameters and retrieve data from the AP and SM modules. Also, if enabled, when an event occurs, the SNMP agent on the 450 Platform Family sends a trap to whatever SNMP trap receivers configured in the management network. SNMPv2c SNMPv3 Page 1-218 Chapter 1: Configuration Setting up SNMP agent Configuring SM/BHSs IP over-the-air access To access the SM/BHS management interface from a device situated above the AP, the SM/BHSs Network Accessibility parameter (under the web GUI at Configuration > IP) may be set to Public. Table 74 LAN1 Network Interface Configuration tab of IP page attributes Attribute IP Address Network Accessibility Meaning Internet Protocol (IP) address. This address is used by family of Internet protocols to uniquely identify this unit on a network. Specify whether the IP address of the SM/BHS must be visible to only a device connected to the SM/BHS by Ethernet (Local) or be visible to the AP/BHM as well (Public). Subnet Mask If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the subnet mask of the SM/BHS for RF management traffic. Gateway IP Address DHCP state DNS IP Address If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the gateway IP address for the SM/BHS for RF management traffic. If Enabled is selected, the DHCP server automatically assigns the IP configuration (IP address, subnet mask, and gateway IP address) and the values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable (read only), in the Network Interface tab of the Home page. Canopy devices allow for configuration of a preferred and alternate DNS server IP address either automatically or manually. Devices must set DNS server IP address manually when DHCP is disabled for the management interface of the device. The default DNS IP addresses are 0.0.0.0 when configured manually. Preferred DNS Server The first address used for DNS resolution. Alternate DNS Server If the Preferred DNS server cannot be reached, the Alternate DNS Server is used. Page 1-219 Chapter 1: Configuration Setting up SNMP agent Domain Name The operators management domain name may be configured for DNS. The domain name configuration can be used for configuration of the servers in the operators network. The default domain name is example.com, and is only used if configured as such. Page 1-220 Chapter 1: Configuration Setting up SNMP agent Configuring SNMP The SNMP page configuration is explained below. Note The SNMP page for AP, SM, BHM and BHS has the same parameter attributes. SNMP page AP/SM/BHM/BHS The SNMP page is explained in Table 75. Table 75 SNMP page attributes Page 1-221 Chapter 1: Configuration Setting up SNMP agent Attribute Meaning SNMP Community String 1 Specify a control string that can allow a Network Management Station

(NMS) to access SNMP information. No spaces are allowed in this string. The default string is Canopy. SNMP Community String 1 Permissions You can designate the SNMP Community String 1 to be the password for WM, for example, to have Read / Write access to the module via SNMP or for all SNMP access to the module to be Read Only. Page 1-222 Chapter 1: Configuration Setting up SNMP agent SNMP Community String 2 (Read Only) Engine ID SNMPv3 Security Level SNMPv3 Authentication Protocol SNMPv3 Privacy Protocol SNMPv3 Read-Only User SNMPv3 Read/Write User Additional SNMP v3 User 1 Specify an additional control string that can allow a Network Management Station (NMS) to read SNMP information. No spaces are allowed in this string. The default string is Canopyro. This password will never authenticate a user or an NMS to read/write access. The Community String value is clear text and is readable by a packet monitor. Additional security derives from the configuration of the Accessing Subnet, Trap Address, and Permission parameters. The Engine ID may be between 5 and 32 hex characters. The hex character input is driven by RFC 3411 recommendations on the Engine ID. The default Engine ID is the MAC address of the device Specify security model where users are defined and authenticated before granting access to any SNMP service. Each device can configure the security level of SNMPv3 to No authentication/No privacy, Authentication/No privacy, or Authentication/Privacy. Currently, the SNMPv3 authentication protocol MD5 is supported. Currently, the SNMPv3 privacy protocol CBC-DES is supported. This field allows for a read-only user per devices. The default values for the Read-Only users is:

Username = Canopyro Authentication Password = authCanopyro Privacy Password = privacyCanopyro Read-write user by default is disabled. The default values for the Read/Write users is:

Username = Canopy Authentication Password = authCanopy Privacy Password = privacyCanopy This field allows to configure the Additional SNMP v3 User 1. The configurations include:

Enable/Disable User: These fields allow to enable or disable the user using the Enable User or Disable User radio buttons. Authorizaton Key: This field allows to configure an authorization key for the user. Privacy Key: This field allows to configure a privacy key for the user. Note Set SNMP v3 Security Level field to: auth, priv to enable the Authorization Key and Privacy Key fields. Page 1-223 Chapter 1: Configuration Setting up SNMP agent Additional SNMP v3 User 2 Additional SNMP v3 User 3 Enabled User can be set with following privacy settings:

ReadWrite User ReadOnly User This field allows to configure the Additional SNMP v3 User 2. The configurations include:

Enable/Disable User: These fields allow to enable or disable the user using the Enable User or Disable User radio buttons. Authorizaton Key: This field allows to configure an authorization key for the user. Privacy Key: This field allows to configure a privacy key for the user. Note Set SNMP v3 Security Level field to: auth, priv to enable the Authorization Key and Privacy Key fields. Enabled User can be set with following Privacy settings:

ReadWrite User ReadOnly User This field allows to configure the Additional SNMP v3 User 3. The configurations include:

Enable/Disable User: These fields allow to enable or disable the user using the Enable User or Disable User radio buttons. Authorizaton Key: This field allows to configure an authorization key for the user. Privacy Key: This field allows to configure a privacy key for the user. Note Set SNMP v3 Security Level field to: auth, priv to enable the Authorization Key and Privacy Key fields. Enabled User can be set with following Privacy settings:

ReadWrite User ReadOnly User SNMPv3 Trap Configuration Accessing IP / Subnet Mask 1 to 10 When enabling transmission of SNMPv3 traps the read-only or read-write user credentials must be used and selected properly in order for the SNMP manager to correctly interpret the traps. By default transmission of SNMPv3 traps is disabled and all traps sent from the radios are in SNMPv2c format. Specify the addresses that are allowed to send SNMP requests to this AP. The NMS has an address that is among these addresses (this subnet). You must enter both The network IP address in the form xxx.xxx.xxx.xxx The CIDR (Classless Interdomain Routing) prefix length in the form /xx For example:

Page 1-224 Chapter 1: Configuration Setting up SNMP agent the /16 in 198.32.0.0/16 specifies a subnet mask of 255.255.0.0 (the first 16 bits in the address range are identical among all members of the subnet). 192.168.102.0 specifies that any device whose IP address is in the range 192.168.102.0 to 192.168.102.254 can send SNMP requests to the AP, presuming that the device supplies the correct Community String value. The default treatment is to allow all networks access. For more information on CIDR, execute an Internet search on Classless Interdomain Routing. You are allowed to specify as many as 10 different accessing IP address, subnet mask combinations. RECOMMENDATION:

The subscriber can access the SM/BHS by changing the subscriber device to the accessing subnet. This hazard exists because the Community String and Accessing Subnet are both visible parameters. To avoid this hazard, configure the SM/BHS to filter (block) SNMP requests. The management DNS domain name may be toggled such that the name of the trap server only needs to be specified and the DNS domain name is automatically appended to that name. The default SNMP trap server addresses for all 10 available servers is 0.0.0.0 with the appending of the DNS domain name disabled. after a reboot of the module. Specify ten or fewer IP addresses (xxx.xxx.xxx.xxx) or DNS names to which SNMP traps must be sent. Traps inform Wireless Manager or an NMS that something has occurred. For example, trap information is sent when an NMS attempts to access agent information but either supplied an inappropriate community string or SNMP version number. is associated with a subnet to which access is disallowed. SNMP Trap Server DNS Usage Trap Address 1 to 10 Trap Enable, Sync Status If the sync status traps (sync lost and sync regained) have to be sent to Wireless Manager or an NMS, select Enabled. If these traps have to be suppressed, select Disabled. Trap Enable, Session Status If you want session status traps sent to Wireless Manager or an NMS, select Enabled. LQI Traps This field enables and disables traps for LQI. LQI threshold to raise trap (delta from reference LQI value) It is configured in percentage. The LQI trap is raised if the LQI values goes below the configured threshold to raise trap from reference LQI. For example, if the LQI threshold to raise trap is set as 30, the LQI trap will be raised once the LQI goes below 70% (100-30). LQI threshold to clear trap (delta from reference LQI value) It is configured in percentage. The LQI trap is cleared if the LQI values goes above the configured threshold to clear trap from reference LQI. For example, if the LQI threshold to clear trap is set as 25, the LQI trap will be clear once the LQI goes above 75% (100-25). Page 1-225 Chapter 1: Configuration Setting up SNMP agent Minimum observation period It is minimum observation period to raise and clear the traps after LQI threshold. It can be configured between 1 to 15 minutes. Site Information Viewable to Guest Users Site Name Site Contact Site Location Operators can enable or disable site information from appearing when a user is in GUEST account mode. Specify a string to associate with the physical module. This parameter is written into the sysName SNMP MIB-II object and can be polled by Wireless Manager or an NMS. The buffer size for this field is 128 characters. Enter contact information for the module administrator. This parameter is written into the sysContact SNMP MIB-II object and can be polled by Wireless Manager or an NMS. The buffer size for this field is 128 characters. Enter information about the physical location of the module. This parameter is written into the sysLocation SNMP MIB-II object and can be polled by Wireless Manager or an NMS. The buffer size for this field is 128 characters. Page 1-226 Configuring syslog Chapter 1: Configuration Configuring syslog 450 Platform Family includes:

Syslog event logging Configuring system logging Syslog event logging Following events are logged in syslog as explained in Table 76. Table 76 Syslog parameters Attribute Meaning Timestamp All syslog messages captured from the radio have a timestamp. Configuration Changes User Login and Logout Add or Delete of user accounts through GUI and SNMP This includes any device setting that has changed and includes the old or new parameter value, including the device reboots. Syslog records each user login and logout, with username. Syslog captures any user accounts that are added or deleted. Spectrum Analysis Syslog records a message every time Spectrum Analysis runs. Note Since the AP/BHM must be set to a SM/BHS for Spectrum Analysis, syslog messages are not reported from the radio until the scan is done and the radio mode is switched back to AP/BHM. Link Test Syslog records a message every time a Link Test is run. Clear Statistics SM Register or De-

register BHS Connect or Disconnect Syslog sends a message when Statistics are cleared. This is done individually for each statistics page that is cleared. Syslog records a message when a SM registers or deregisters. Syslog records a message when a BHS connects or disconnects. Configuring system logging To configure system logging, select the menu option Configuration > Syslog. Page 1-227 Chapter 1: Configuration Syslog page of AP/BHM The Syslog Configuration page for AP/BHM is shown in Table 77. Table 77 Syslog Configuration attributes - AP Configuring syslog Attribute Meaning Syslog DNS Server Usage To configure the AP/BHM to append or not append the DNS server name to the syslog server name. Syslog Server The dotted decimal or DNS name of the syslog server address. Syslog Server Port The syslog server port (default 514) to which syslog messaging is sent. AP Syslog Transmit Or BHM Syslog Transmit SM Syslog Transmit Or BHS Syslog Transmit Syslog Minimum Level Syslog page of SM When enabled, syslog messages are sent from the AP/BHM. When enabled, syslog messages are sent from all the registered SMs/BHS, unless they are individually set to override this. This provides a selection for the minimum syslog message severity that is sent to the syslog server. Values range from fatal (highest severity and least verbose) to info (lowest severity, maximum verbosity). For example: If the Syslog Minimum Level is set to notice, then only messages with severity notice and above are sent. To configure system logging, select the menu option Configuration > Syslog. The Syslog Configuration page is shown in Table 78. Page 1-228 Chapter 1: Configuration Configuring syslog Table 78 Syslog Configuration attributes - SM Attribute Meaning Syslog Configuration Source This control determines whether the SM will attempt to use the syslog server definition from the AP, or whether it will use a local server definition. When set to AP preferred, use local when AP configuration unavailable, and if the SM can register with an AP, then it uses the syslog server defined on that AP. If the SM cannot register then it will syslog to its locally defined syslog server through its wired connection, if any. When set to Local only the SM ignores the APs definition of the syslog server and allows the syslog server to be configured individually for each SM. Syslog DNS Server Usage To configure the SM to append or not the DNS server name to the syslog server name. Syslog Server The dotted decimal or DNS name of the syslog server address. Syslog Server Port The syslog server port (default 514) to which syslog messaging is sent. Syslog Transmission Syslog Minimum Level Source Controls the SMs ability to transmit syslog messages. When set to Learn from AP the AP will control whether this SM transmits syslog messages. When set to enable or disable the SM will control whether it sends syslog messages. This allows an operator to override the AP settings for individual SMs in a sector. This control determines whether the SM attempts to use the minimum syslog level defined by the AP, or whether it uses a local defined value using the Syslog Minimum Level parameter. When set to AP preferred, use local when AP configuration unavailable, and if the SM can register with an AP, then it uses the Syslog Minimum Level defined on that AP. If the SM cannot register then it uses its own Syslog Minimum Level setting. When set to Local only the SM will always use its own Syslog Minimum Level setting and ignores the APs setting. Page 1-229 Chapter 1: Configuration Configuring syslog Syslog Minimum Level This provides a selection for the minimum syslog message severity that is sent to the syslog server. Values range from fatal (highest severity and least verbose) to info (lowest severity, maximum verbosity). For example: If the Syslog Minimum Level is set to notice, then only messages with severity notice and above are sent. Syslog page of BHS The Syslog Configuration page is shown in Table 79. Table 79 Syslog Configuration attributes - BHS Attribute Meaning Syslog Configuration Source This control determines whether the BHS will attempt to use the syslog server definition from the BHM, or whether it will use a local server definition. When set to BHM preferred, use local when BHM configuration unavailable, and if the BHS can register with a BHM, then it uses the syslog server defined on that BHM. If the BHS cannot register then it will syslog to its locally defined syslog server through its wired connection, if any. When set to Local only the BHS ignores the BHMs definition of the syslog server and allows the syslog server to be configured individually for each BHS. Syslog DNS Server Usage To configure the BHS to append or not to append the DNS server name to the syslog server name. Syslog Server The dotted decimal or DNS name of the syslog server address. Syslog Server Port Syslog Transmission The syslog server port (default 514) to which syslog messaging is sent. Controls the BHSs ability to transmit syslog messages. When set to Learn from BHM the BHM will control whether this BHS transmits syslog messages. When set to enable or disable the BHS will Page 1-230 Chapter 1: Configuration Configuring syslog control whether it sends syslog messages. This allows an operator to override the BHM settings for individual BHSs in a sector. This control determines whether the BHS attempts to use the minimum syslog level defined by the BHM, or whether it uses a local defined value using the Syslog Minimum Level parameter. When set to BHM preferred, use local when BHM configuration unavailable, and if the BHS can register with a BHM, then it uses the Syslog Minimum Level defined on that BHM. If the BHS cannot register then it uses its own Syslog Minimum Level setting. When set to Local only the BHS will always use its own Syslog Minimum Level setting and ignores the BHMs setting. This provides a selection for the minimum syslog message severity that is sent to the syslog server. Values range from fatal (highest severity and least verbose) to info (lowest severity, maximum verbosity). For example: If the Syslog Minimum Level is set to notice, then only messages with severity notice and above are sent. Syslog Minimum Level Source Syslog Minimum Level Page 1-231 Chapter 1: Configuration Configuring remote access Configuring remote access Accessing SM/BHS over-the-air by Web Proxy The SM/BHS may be accessed via the AP/BHM management GUI by navigating to Home > Session Status (or Home > Remote Subscribers for AP only) and clicking on the SMs hyperlink. For example, to access one of the SMs, click LUID: 002 [0a-00-3e-37-b9-fd], as shown in Figure 30. Figure 30 AP Session Status page The SessionStatus.xml hyper link allows user to export all displayed SM data in Session Status table into an xml file. To access any one of the SMs, click 450 Platform Family - SM hyperlink, as shown in Figure 31. Figure 31 AP Remote Subscribers page Page 1-232 Chapter 1: Configuration Monitoring the Link Link monitoring procedure Monitoring the Link After configuring the link, either an operator in the network office or the SM/BHS INSTALLER user in the field (if read access to the AP/BHM is available to the INSTALLER) must perform the following procedure. Who is authorized and able to do this depends on local operator password policy, management VLAN setup and operational practices. To monitor the link for performance, follow these instructions:

Procedure 14 Monitoring the AP-SM link 1 Access the web interface of the AP/BHM 2 In the left-side menu of the AP/BHM interface, select Home. 3 Click the Session Status tab. Figure 32 Session Status page 4 The Device tab of Session Status List display all displayed SMs MAC address, PMP/PTP Hardware, Software Version, FPGA Version and State Page 1-233 Chapter 1: Configuration Monitoring the Link 5 Click Session Count tab of Session Status List to display values for Session Count, Reg Count, and Re-Reg Count. Session Count: This field displays how many sessions the SM/BHS has had with the AP/BHM. Typically, this is the sum of Reg Count and Re-Reg Count. However, the result of internal calculation may display here as a value that slightly differs from the sum. Reg Count: When a SM/BHS makes a Registration Request, the AP/BHM checks its local session database to see whether it was registered earlier. If the AP/BHM concludes that the SM/BHS is not currently in session database and it is valid Registration Request, then the request increments the value of this field. Re-Reg Count: When a SM/BHS makes a Registration Request, the AP/BHM checks its local session database to see whether it was registered earlier. If the AP/BHM concludes that the SM/BHS is currently in session database, then the request increments the value of this field. Typically, a Re-Reg is the case where both o SM/BHS attempts to reregister for having lost communication with the AP/BHM. o AP/BHM has not yet observed the link to the SM/BHS as being down. See Session tab on page 3-26 6 Click Power tab of Session Status list to display Downlink Rate, AP Rx Power (dBm), Signal Strength Radio (dB) for Uplink and Signal to Noise Radio (dB) for Uplink. See Power tab on page 3-27 7 Click Configuration tab of Session Status list to get QoS configuration details:

Sustained Data Rate (kbps) Burst Allocation (kbit) Max Burst Rate (kbit) See Low Priority CIR (kbps) Configuration tab on page 3-30 8 Briefly monitor these values, occasionally refreshing this page by clicking another tab and then the Session Status tab again. 9 If these values are low (for example, 1, 1, and 0, respectively, meaning that the SM/BHS registered and started a stable session once) and are not changing:

Consider the installation successful. Monitor these values from the network office over the next several hours and days. If these values are greater than 1, 1, and 0, or they increase while you are monitoring them, troubleshoot the link. (For example, Use Receive Power Level for aiming and then use Link Tests to confirm alignment). Refer Viewing Session Status on page 3-24 for more details. Page 1-234 Chapter 1: Configuration Monitoring the Link Exporting Session Status page of AP/BHM The SessionStatus.xml hyper link allows user to export all displayed SMs or BHS data in Session Status table into an xml file. Figure 33 Exporting Session Status page of PMP 450m AP In case of PMP, if the session status page does not list any SM, the SessionStatus.xml will still be visible but the file would be empty. The file will contain data from all of the 5 different tables. Export from command line The scripts users can also get this file from command line, you have to authenticate successfully in order to download the file. wget http://169.254.1.1/SessionStatus.xml?CanopyUsername=test&CanopyPassword=test Page 1-235 Chapter 1: Configuration Configuring quality of service Configuring quality of service Maximum Information Rate (MIR) Parameters Point-to-multipoint links use the following MIR parameters for bandwidth management:

Sustained Uplink Data Rate (kbps) Uplink Burst Allocation (kb) Sustained Downlink Data Rate (kbps) Downlink Burst Allocation (kb) Max Burst Downlink Data Rate (kbps) Max Burst Uplink Data Rate (kbps) Set each of these parameters per AP or per SM independently. Note You can refer below whitepaper for 450 Platform Family Max Burst MIR:

http://www.cambiumnetworks.com/resources/pmp-450-maxburst/

Token Bucket Algorithm The software uses a token bucket algorithm that has the following features:

Stores credits (tokens) for the SM to spend on bandwidth for reception or transmission. Drains tokens during reception or transmission. Refills with tokens at the sustained rate set by the network operator. For each token, the SM can send toward the network in the uplink (or the AP can send toward the SM in the downlink) an equivalent number of kilobits. Two buckets determine the permitted throughput: one in the SM for uplink and one in the AP for downlink. The applicable set of Uplink Burst Allocation and Downlink Burst Allocation parameters determine the number of tokens that can fill each bucket. When the SM transmits (or the AP transmits) a packet, the equivalent number of tokens is removed from the uplink (or downlink) bucket. Except when full, the bucket is continuously being refilled with tokens at rates that the applicable set of Sustained Uplink Data Rate and Sustained Downlink Data Rate parameters specify. The bucket often drains at a rate that is much faster than the sustained data rate but can refill at only the sustained data rate. Thus, the effects of the allocation and rate parameters on packet delay are as follows:

The burst allocation affects how many kilobits are processed before packet delay is imposed. The sustained data rate affects the packet delay that is imposed. Page 1-236 Chapter 1: Configuration Configuring quality of service MIR Data Entry Checking Uplink and downlink MIR is enforced as shown in Figure 34. Note In these figures, entry refers to the setting in the data rate parameter, not the burst allocation parameter. Figure 34 Uplink and downlink rate caps adjusted to apply aggregate cap uplink cap enforced =

downlink cap enforced =

uplink entry x aggregate cap for the SM uplink entry + downlink entry downlink entry x aggregate cap for the SM uplink entry + downlink entry For example, in the SM, if you set the Sustained Uplink Data Rate parameter to 2,000 kbps and the Sustained Downlink Data Rate parameter to 10,000 kbps, then the uplink and downlink MIR that is enforced for the SM can be calculated as shown in Figure 35. Figure 35 Uplink and downlink rate cap adjustment example uplink cap enforced =

2,000 kbps x 7,000 kbps 2,000 kbps + 10,000 kbps

= 1,167 kbps downlink cap enforced =

`

10,000 kbps x 7,000 kbps 2,000 kbps + 10,000 kbps

= 5,833 kbps In this example case, the derived 1,167-kbps uplink and 5,833-kbps downlink MIR sum to the fixed 7,000-

kbps aggregate cap of the SM. Committed Information Rate (CIR) The Committed Information Rate (CIR) capability feature enables the service provider to guarantee to any subscriber that bandwidth will never decrease to below a specified minimum unless CIR is oversubscribed or RF conditions are degraded. CIR is oversubscribed when there is not enough available bandwidth to support CIR configuration for all subscribers. In this condition, SMs which are configured with a nonzero CIR will all operate at the maximum data rate supported by the link (subject to Maximum Information Rate and Burst Rate/Allocations). SMs which are configured with a CIR of 0 kbps will not transmit until CIR-configured SMs have completed transmission. CIR may be configured independently for low priority traffic, medium priority traffic, high priority traffic, and ultra high priority traffic. Page 1-237 Chapter 1: Configuration Configuring quality of service Note CIR settings only apply to the Legacy scheduler. Starting in release 16.1 a new Proportional scheduler can optionally be enabled via Configuration -> Quality of Service -> Scheduler setting. If Proportional Scheduler is set, CIR's are not used. CIR parameters may be configured in the following ways:

Web-based management GUI SNMP Authentication Server (RADIUS) - when an SM successfully registers and authenticates, CIR information is retrieved from the RADIUS server. Active CIR configuration can be verified via the APs Home > Session Status page. Bandwidth from the SM Perspective In the SM, normal web browsing, e-mail, small file transfers and short streaming video are rarely rate limited with practical bandwidth management (QoS) settings. When the SM processes large downloads such as software upgrades and long streaming video or a series of medium-size downloads, the bucket rapidly drains, the burst limit is reached, and some packets are delayed. The subscriber experience is more affected in cases where the traffic is more latency sensitive. Interaction of Burst Allocation and Sustained Data Rate Settings If the Burst Allocation is set to 1200 kb and the Sustained Data Rate is set to 128 kbps, a data burst of 1000 kb is transmitted at full speed because the Burst Allocation is set high enough. After the burst, the bucket experiences a significant refill at the Sustained Data Rate. This configuration uses the advantage of the settable Burst Allocation. If both the Burst Allocation and the Sustained Data Rate are set to 128 kb, a burst is limited to the Burst Allocation value. This configuration does not take advantage of the settable Burst Allocation. If the Burst Allocation is set to 128 kb and the Sustained Data Rate is set to 256 kbps, the actual rate is the burst allocation (but in kbps). As above, this configuration does not take advantage of the settable Burst Allocation. SM Prioritization Note This feature is not supported on PMP 450m. SM Prioritization provides a way to designate a subset of a PMP sector's SMs with a guaranteed portion of air interface resources - slots, which are handled first during scheduling. SMs by default are configured in the SM Prioritization Low Group, and can be configured for the SM Prioritization High Group if desired. The selection of which prioritization group each SM is configured in Configuration -> Quality of Service tab -> SM Prioritization Configuration on the SM GUI, as shown in Figure 36. Page 1-238 Chapter 1: Configuration Figure 36 SM Prioritization on SM Configuring quality of service The feature does not take effect, however, until SM Prioritization is enabled on the AP, because the scheduler runs on the AP. Prioritization Allocation percentages per group are configured on the AP to determine how many timeslot resources are dedicated to each priority group. Enabling of the feature and allocation percentages per group are configured in Configuration ->

Quality of Service tab -> SM Prioritization Configuration on the AP GUI as shown in Figure 37. With Cambiums SM prioritization feature, we guarantee a percentage of slot resources to each prioritization group. If the resource allocation demands of the SMs in the High Priority allocation group are met without allocating all of that groups allocation percentage, the remaining resources can be used for any unmet demands for SMs in the Low Group. Similarly, if the resource allocation demands of the SMs in the Low Priority allocation group are met without allocating all of that groups allocation percentage, the remaining resources can be used for any unmet demands for SMs in the High Group. If the sector has 100% utilization, the resource allocation per group will equal the percentages configured on the AP. This feature can be used to provide guaranteed frame allocation to high priority clients, such as business customers. Although SM Prioritization Group 1 is called the High Priority group, and SM Prioritization Group 2 is called the Low Priority group, this does not mean that 1 group is scheduled resources before the other group. The intention is, by adjusting the number of SMs in the High Priority group and the allocation percentages per group, the SMs in the High Priority group will have a higher slots/SMs ratio. The following figure shows the SM Prioritization configuration at the AP with this feature enabled. Figure 37 SM Prioritization on AP In the example shown in Figure 37, 2 of the 8 SMs have been configured for the High Priority Group. The other 6 are in the Low Priority group. 45% of the air interface timeslot resources have been allocated to the Low Priority group. If, for example, all SMs are fully active and all resources in this sector are fully utilized, then 55% of the air interface slot resources will be shared between the 2 High Priority SMs, per direction, and the remaining 45% of the resources will be shared between the other 6 SMs. If, on the other hand, only 40% of the resources are needed to meet the scheduling demands of the 2 High Priority SMs, the additional 15% that was pre-allocated to the High Priority group can then be used for the Low Priority group, maintaining 100% slot utilization in the sector. Page 1-239 Chapter 1: Configuration SM Prioritization with CIR Configuring quality of service When the SM Prioritization feature is used with CIR, Cambiums scheduler will first prioritize scheduling of data channels configured with a CIR, but only within the limits of that SMs Prioritization Group allocation. In the example configuration shown in Figure 37, there are 6 SMs in the Low Prioritization group. If 3 of those 6 SMs each have a 1Mbps CIR configured, the Cambium scheduler will attempt to meet this 1Mbps CIR per SM before scheduling the other 3 SMs. But if both prioritization groups are overloaded, this 3Mbps committed load on these 3 SMs will only be achieved if it can be done with 55%

of the resources or less per direction. Page 1-240 Chapter 1: Configuration Configuring quality of service Weighted Fair Queuing (WFQ) Note This feature is not supported on PMP 450m. This feature lets the user assign a percentage of air interface resources to each of the Data Channel levels. The WFQ apply both to the DL and the UL. Note that there is no BC/MC traffic in the UL direction. One of the benefits of WFQ is that the configuration can be accomplished at the AP rather than at each individual SMs. This feature can be used with or in place of existing CIR settings. Unlike CIR, which is set in kbps independent of the modulation rate, the WFQ feature operates on a percentage of air interface resources, or timeslots. Figure 38 is an example of a WFQ configuration on the AP. This can be found in Configuration ->

Quality of Service tab -> Weighted Fair Queuing Configuration on the AP GUI. In this particular sector, we have 30 Data channels spread across 8 registered SMs. 4 levels of QoS have been configured on 7 of the SMs, 2 levels of QoS have been configured on 1 of the SMs. Figure 38 Weighted Fair Queuing Configuration The above figure shows that 4% of the air interface resources have been reserved for Broadcast/Multicast traffic, 22% of the available air interface timeslot have been reserved for the lowest priority traffic, 22% for medium priority traffic, 26% for high priority traffic, and 26% for the highest priority traffic (Ultra High Priority). If, at any point in the time, the aggregate traffic load across all SMs on 1 QoS level is less than that levels Weighted Fair Queue allocation, then those unused slots will be allocated for traffic in other QoS levels, based on strict priority. Page 1-241 Chapter 1: Configuration Configuring quality of service For example, if, during peak traffic hours, the Ultra High, High, and Low priority Data channels were experiencing heavy traffic loads, but the medium priority aggregate traffic load was light and only used 10% of the scheduling slots in a particular direction, the remaining unused 12% of the slots would be allocated first to the Ultra High priority traffic in queue. When all the Ultra High priority traffic has been scheduled, then any remaining unused slots would be used for High Priority traffic. Finally, after High Priority traffic has been serviced, any remaining slots would be used for Low Priority traffic. The Low Priority in the sub-heading Low Priority SMs WFQ Configuration shown above simply indicates that the SM Prioritization feature is turned off in this example above. The Valid indication in this screenshot is a simple software check to make sure that the configured percentages add up to 100%. WFQ with CIR Note This feature is not supported on PMP 450m. The WFQ feature can be used with, or as a replacement for, configuring Committed Information Rates

(CIR) per data channel. When the WFQ feature is used with CIRs, Cambiums scheduler will first prioritize scheduling of the Data channels configured with a CIR, but only within the limits of that QoS levels WFQ allocation. Using the example configuration show in Figure 38, there are 8 high priority Data channels. If 5 of those 8 Data channels have a CIR configured, then the Cambium scheduler will prioritize traffic on those 5 Data channels up to their CIR limits, for those 26% of the timeslots allocated to that QoS level. Operators should try to avoid oversubscription of CIRs. But if CIRs have been oversubscribed at any 1 QoS level such that the desired CIR rates cannot be met within the limits of that levels WFQ allocation, the scheduler will use unallocated slots from another QoS level in strict priority order. From the prior example, if there is less than 22% of timeslots worth of traffic on the medium priority Data channels, those unused slots would be allocated to Ultra High Priority traffic on Data channels that had not met their CIR commitment within the WFQ allocation, then on High Priority Data channels that had not met their CIR commitment within WFQ allocation, then on Low Priority Data channels that had not met their CIR commitment with WFQ allocation, then on Ultra High Priority traffic above and beyond any CIR configurations, and so on. Page 1-242 Chapter 1: Configuration Configuring quality of service WFQ with SM Prioritization Note This feature is not supported on PMP 450m. Figure 39 shows a WFQ configuration with the SM Prioritization feature also enabled. Figure 39 WFQ with SM Prioritization In the example shown in Figure 39, 2 of the 8 SMs have been configured for the High Priority Group. The other 6 are in the Low Priority group. 45% of air interface timeslot resources have been allocated to the Low priority group. The same allocation rules described above still apply to the WFQ allocation, but now these allocations are done within the confines of each Prioritization group. So, in this configuration shown in Figure 39, the 2 Medium Priority QoS level Data channels in the High Priority SM Prioritization Group together share 12% of the committed air interface resources per direction. (.55 x .22 = .12) The same CIR allocation rules apply. The Cambium scheduler will attempt to meet those CIR allocations within the confines of that 12% allocation. If the traffic load on those 2 data channels is light, for example using only 5% of the available slots, then the remaining 7% of resources can be used for other traffic in a strict priority manner. (i.e. attempt to honor CIRs first, then Ultra High Priority traffic, then High Priority traffic, and so on, as described previously). Page 1-243 Chapter 1: Configuration Configuring quality of service Proportional Scheduler This feature, also known as the Rate Plan feature, allows a user to set Plans per SM in units of Kbps. The proportional scheduler maintains the proportions of the SMs plans when the sector is congested. A default plan setting per direction also exists on the AP and is used in case an SM is not configured with a Plan (for example, the SM is not upgraded to system release 16.1 yet). Figure 40 Scheduler Settings on AP When selecting the Proportional scheduler, CIR is no longer applicable. In system release 16.1, the SM supports a Proportional Scheduler setting section in the Configuration->

Quality of Service (QoS) page. These settings are applicable only if the AP is configured to use the Proportional scheduler. Figure 41 Proportional Scheduler Settings on AP The above 6 settings parameters are described in detail in the Quality of Service (QoS) page of SM later in this document. The proportional scheduler works in conjunction with the Weighted Fair Queuing feature (in the products that support it), but preserving the plans ratios takes precedence in the scheduler decisions over honoring the WFQ percentages High-priority Bandwidth Traffic To support low-latency traffic such as VoIP (Voice over IP) or video, or critical traffic such as control packets, the system implements priority data channels. Prior to PMP 450 Release 15.2, the system allowed for a single High Priority Channel to be configured per SM and per direction, in addition to the default low priority channel. This channel did not affect the inherent latencies in the system but allowed high-priority traffic to be immediately served. The high-priority pipe separates low-latency traffic from traffic that is latency tolerant, such as standard web traffic and file downloads. From system release 15.2, the system supports up to 4 QoS levels, or data channels, per SM. These are called Low, Medium, High, and Ultra High data channels. Page 1-244 Chapter 1: Configuration Configuring quality of service The number of data channels available on the AP is still limited to 238 in release 15.2 This could be 238 SMs each configured with a single Low Priority channel, or, for example, 59 SMs with 4 data channels configured and 1 SM with 2 data channels configured. A module prioritizes traffic by:

reading the 802.1p field of the 802.1Q header in a received packet, where VLAN is enabled on the module. comparing the 6-bit Differentiated Services Code Point (DSCP) field in the ToS byte of a received packet to a corresponding value in the Diffserv tab of the Configuration page of the module. Modules monitor ToS bytes with DSCP fields, but with the following differences:

The 6-bit length of the field allows it to specify one of 64 service differentiations. These correlate to 64 individual (CodePoint) parameters in the Diffserv tab of the Configuration page. The 8 Class Selector code points are fixed in code and not user settable. For any or all of the remaining 56 CodePoint parameters, you can specify a value of o 0, 1 for low-priority handling. o 2, 3 for medium-priority handling. o 4,5 for high-priority handling. o 6, 7 for ultra-high-priority handling. The above mapping applies if 4 QoS levels are configured. If fewer than that are configured, see the mapping table in the IPv4 and IPv6 Prioritization of this document. Note Ensure that your Differentiated Services domain boundary nodes mark any entering packet, as needed, so that it specifies the appropriate Code Point for that traffic and domain. This prevents theft of service level. An example of the Diffserv page in the Configuration menu and parameter descriptions are provided under DiffServ attributes AP/BHM on page 1-62. This tab and its rules are identical from module type to module type. However, any of the 61 configurable Code Points can be set to a different value from module to module, thus defining unique per-hop behavior for some traffic. This tab in the AP sets the priorities for the various packets in the downstream (sent from the public network). This tab in the SM sets the priorities for the various packets in the upstream (sent to the public network). Typically, some SMs attach to older devices that use the ToS byte as originally formatted, and others to newer devices that use the DSCP field. The default values in the Diffserv page allow your modules to prioritize traffic from the older devices roughly the same as they traditionally have. However, these default values may result in more high-priority traffic as DSCP fields from the newer devices are read and handled. So, after making changes in the Diffserv page, carefully monitor the high-priority channel for high packet rates across your network when you have broadly implemented Code Point values, such as via SNMP. in SMs that you have identified as those to initially set and watch. Page 1-245 Chapter 1: Configuration Configuring quality of service Traffic Scheduling The characteristics of traffic scheduling in a sector are summarized in Table 80. Table 80 Characteristics of traffic scheduling Category Factor Throughput Aggregate throughput, less additional overhead Latency Number of frames required for the scheduling process Round-trip latency AP broadcast the download schedule Treatment 132 Mbps for 20 MHz Higher for 30 MHz or 40 MHz and lower for smaller bandwidths. 1 6 ms No Priority Data Channels Allocation for uplink high-priority data channel traffic on amount of traffic at these higher QoS levels. Dynamic, based on amount of high-

priority traffic Allocation for downlink high-priority data channel traffic on amount of traffic at these higher QoS levels Dynamic, based on amount of high-

priority traffic Order of transmission 1- Ultra High Priority data channels below CIR limit 2- High Priority data channel's below CIR limit 3- Medium Priority data channels below CIR limit 4- Low Priority data channels below CIR limit 5- Ultra High Priority data channels above CIR limit 6- High Priority data channels above CIR limit 7- Medium Priority data channels above CIR limit 8- Low Priority data channels above CIR limit Note This strict priority transmission order is only true in all cases if the SM Prioritization and Weighted Fair Queue features are disabled. If either feature is enabled, see the description of those features in this document for how they impact and interact with this transmission order. Page 1-246 Chapter 1: Configuration Configuring quality of service Setting the Configuration Source The AP includes a Configuration Source parameter, which sets where SMs that register to the AP are controlled for MIR, CIR, VLAN, and the high-priority channel as follows. The Configuration Source parameter affects the source of:

all MIR settings:

o Sustained Uplink Data Rate o Uplink Burst Allocation o Max Burst Uplink Data Rate o Sustained Downlink Data Rate o Downlink Burst Allocation o Max Burst Downlink Data Rate all CIR settings:

o Low Priority Uplink CIR o Low Priority Downlink CIR o Medium Priority Uplink CIR o Medium Priority Downlink CIR o High Priority Uplink CIR o High Priority Downlink CIR o Ultra High Priority Uplink CIR o Ultra High Priority Downlink CIR all SM VLAN settings o Dynamic Learning o Allow Only Tagged Frames o VLAN Aging Timeout o Untagged Ingress VID o Management VID o VLAN Membership the High Priority Channel setting Page 1-247 Chapter 1: Configuration Configuring quality of service Table 81 Recommended combined settings for typical operations Most operators who use must set this parameter in this web page/tab in the AP to no authentication server Wireless Manager

(Authentication Server) RADIUS AAA server Authentication Mode Configuration/ Security Disabled Configuration Source Configuration/ General SM Authentication Mode Configuration/ Security Authentication Server Configuration Source Configuration/ General Authentication Server Authentication Mode Configuration/ Security RADIUS AAA Configuration Source Configuration/ General Authentication Server Table 82 Where feature values are obtained for an SM registered under an AP with Authentication Mode set to something other than "DISABLED"

Configuration Source Setting in the AP Authentication Server Values are obtained from MIR Values VLAN Values Data Channel Count per SM Authentication Server Authentication Server Authentication Server SM SM SM SM Authentication Server+SM Authentication Server Authentication Server, then SM Authentication Server, then SM Note Where Authentication Server, then SM is the indication, parameters for which Authentication Server does not send values are obtained from the SM. This is the case where the Authentication Server is operating on an Authentication Server release that did not support the feature. This is also the case where the feature enable/disable flag in Authentication Server is set to disabled. The values are those previously set or, if none ever were, then the default values. Where Authentication Server is the indication, values in the SM are disregarded. Where SM is the indication, values that Authentication Server sends for the SM are disregarded. For any SM registered under an AP with Authentication Mode set to something other than "DISABLED", the listed settings are derived as shown in Table 83. Table 83 MIR, VLAN, HPC, and CIR Configuration Sources, Authentication Disabled Values are obtained from Page 1-248 Chapter 1: Configuration Configuring quality of service Configuration Source Setting in the AP MIR Values VLAN Values Data Channel Count per SM CIR Values Authentication Server AP SM Authentication Server+SM SM SM AP SM SM SM SM SM SM Note For the case where configuration source is set to Authentication Server, the Data Channel Count per SM, and the CIR values for those data channels, is defaulted to Low Priority data Channel only with no CIRs configured. Page 1-249 Chapter 1: Configuration Configuring quality of service Configuring Quality of Service (QoS) Quality of Service (QoS) page of AP The QoS page of AP is explained in Table 84. Table 84 QoS page attributes - AP Page 1-250 Chapter 1: Configuration Configuring quality of service Attribute Meaning Sustained Downlink Data Rate Sustained Uplink Data Rate Downlink Burst Allocation Uplink Burst Allocation Specify the rate at which the AP is replenished with credits (tokens) for transmission to each of the SMs in its sector. This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on page 1-236 Interaction of Burst Allocation and Sustained Data Rate Settings on page 1-238 Configuration Source on page 1-73 Specify the rate that each SM registered to this AP is replenished with credits for transmission. This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on page 1-236 Interaction of Burst Allocation and Sustained Data Rate Settings on page 1-238 Configuration Source on page 1-73 Specify the maximum amount of data to allow the AP to transmit to any registered SM before the AP is replenished with transmission credits at the Sustained Downlink Data Rate. See Maximum Information Rate (MIR) Parameters on page 1-236 Interaction of Burst Allocation and Sustained Data Rate Settings on page 1-238 Configuration Source on page 1-73 Specify the maximum amount of data to allow each SM to transmit before being recharged at the Sustained Uplink Data Rate with credits to transmit more. See Maximum Information Rate (MIR) Parameters on page 1-236 Interaction of Burst Allocation and Sustained Data Rate Settings on page 1-238 Page 1-251 Chapter 1: Configuration Configuring quality of service Configuration Source on page 1-73 Max Burst Downlink Data Rate These parameters allow operators to specify the data rate at which an SM is allowed to transmit (until burst allocation limit is reached) before being recharged at the Sustained Downlink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. Max Burst Uplink Data Rate These parameters allow operators to specify the data rate at which an SM is allowed to transmit (until burst allocation limit is reached) before being recharged at the Sustained Uplink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. Broadcast Downlink CIR Broadcast Downlink CIR (Committed Information Rate, a minimum) supports system designs where downlink broadcast is desired to have higher priority than other traffic. For many other system designs, especially typical internet access networks, leave the Broadcast Downlink CIR at the default. Broadcast Downlink CIR is closely related to the Broadcast Repeat Count parameter, which is settable in the Radio tab of the Configuration page in the AP: when the Broadcast Repeat Count is changed, the total of available bandwidth is also changed, since packets are being sent one, two, or three times, according to the setting in the Broadcast Repeat Count parameter. Scheduler This parameter allows the operator to either select the Proportional scheduler or the Legacy scheduler. Default Downlink Plan This parameter allows the operator to configure the default downlink plan. The value range for this parameter is 1 310000 kbps. Note: Configure this parameter when an SM is not configured with a plan or an SM is still running software older than system release 16.1. Default Uplink Plan This parameter allows the operator to configure the default uplink plan. The value range for this parameter is 1 310000 kbps. Note: Configure this parameter when an SM is not configured with a plan or an SM is still running software older than system release 16.1. Priority Precedence Allows operator to decide if 802.1p or DiffServ priority bits must be used first when making priority decisions. PPPoE Control Message Priority Prioritize TCP ACK Operators may configure the SM to utilize the high priority channel for PPPoE control messages. Configuring the SM in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the SM. To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. Management Data Priority Level This parameter allows to set the priority level of the VC used by Management data. Page 1-252 Chapter 1: Configuration Configuring quality of service Low: Management data uses low priority VC. High: Management data uses highest priority VC SM Prioritization Low Group Count This parameter displays the number and percentage of SMs allocated with low prioritization. SM Prioritization High Group Count This parameter displays the number and percentage of SMs allocated with high prioritization. SM Prioritization To associate a group of SMs at the same prioritization level with a guaranteed percentage of time for data to/from SMs in the group, enable this parameter. Low Prioritization Allocation and High Prioritization Allocation parameters are visible when SM Prioritization is enabled. Note: SM Prioritization is not applicable for proportional scheduler. Low Prioritization Allocation This parameter configures the percentage of timeslots dedicated to low prioritization group of SMs High Prioritization Allocation Once the Low Prioritization Allocation parameter is configured, this parameter automatically allocates the percentage of slots dedicated to high prioritization group of SMs such that the sum of parameters Low Prioritization Allocation and High Prioritization Allocation is 100%. Data Channel Count -

Low Priority This parameter displays the percentage of time committed to transfer data to/from VCs at Low Priority QoS level. Data Channel Count -

Medium Priority This parameter displays the percentage of time committed to transfer data to/from VCs at Medium Priority QoS level. Data Channel Count -

High Priority This parameter displays the percentage of time committed to transfer data to/from VCs at High Priority QoS level. Data Channel Count -

Ultra High Priority This parameter displays the percentage of time committed to transfer data to/from VCs at Ultra High Priority QoS level. Weighted Fair Queuing To provide a committed frame space for all QoS levels, enable this parameter. WFQ Configuration (SM Prioritization Low Group):

If the percentage of Low Priority SMs is configured as 100%, or SM Prioritization is disabled, or the WFQ feature is disabled, then the GUI displays the following set of five WFQ configuration parameters Page 1-253 Chapter 1: Configuration Configuring quality of service Data Channel Allocation -

Broadcast/Multicast Data Channel Allocation - Low Priority Data Channel Allocation - Medium Priority Data Channel Allocation - High Priority Data Channel Allocation - Ultra High Priority This parameter allows to configure the percentage of frame space allocated for broadcast/multicast. This parameter allows to configure the percentage of frame space allocated for low priority QoS level. This parameter allows to configure the percentage of frame space allocated for medium priority QoS level. This parameter allows to configure the percentage of frame space allocated for high priority QoS level. This parameter allows to configure the percentage of frame space allocated for ultra high priority QoS level. WFQ Configuration (SM Prioritization High Group):

If SM Prioritization is enabled and the percentage of Low Priority SMs is configured as anything less than 100%, which means that the percentage of High Priority SMs is not 0, and the WFQ feature is enabled, then the GUI displays the WFQ Configuration (SM Prioritization Low Group) and the following set of five WFQ configuration parameters for High group. Data Channel Allocation - Low Priority Data Channel Allocation - Medium Priority Data Channel Allocation - High Priority Data Channel Allocation - Ultra High Priority This parameter allows to configure the percentage of frame space allocated for low priority QoS level. This parameter allows to configure the percentage of frame space allocated for medium priority QoS level. This parameter allows to configure the percentage of frame space allocated for high priority QoS level. This parameter allows to configure the percentage of frame space allocated for ultra high priority QoS level. Page 1-254 Chapter 1: Configuration Configuring quality of service Quality of Service (QoS) page of SM The QoS page of SM is explained in Table 85. Table 85 QoS page attributes - SM Attribute Meaning Page 1-255 Chapter 1: Configuration Configuring quality of service Sustained Uplink Data Rate Specify the rate that this SM is replenished with credits for transmission. This default imposes no restriction on the uplink. See Maximum Information Rate

(MIR) Parameters on page 1-236 Interaction of Burst Allocation and Sustained Data Rate Settings on page 1-238 Configuration Source on page 1-73 Sustained Downlink Data Rate Specify the rate at which the AP is replenished with credits (tokens) for transmission to this SM. This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on Page 1-236 Interaction of Burst Allocation and Sustained Data Rate Settings on page 1-238 Downlink Burst Allocation Uplink Burst Allocation Configuration Source on page 1-73 Specify the maximum amount of data to allow the AP to transmit to this SM before the AP is replenished at the Sustained Downlink Data Rate with transmission credits. See Maximum Information Rate (MIR) Parameters on page 1-236 Interaction of Burst Allocation and Sustained Data Rate Settings on page 1-238 Configuration Source on page 1-73 Specify the maximum amount of data to allow this SM to transmit before being recharged at the Sustained Uplink Data Rate with credits to transmit more. See Maximum Information Rate (MIR) Parameters on page 1-236 Interaction of Burst Allocation and Sustained Data Rate Settings on page 1-238 Configuration Source on page 1-73 Max Burst Downlink Data Rate These parameters allow operators to specify the data rate at which a SM is allowed to transmit (until burst allocation limit is reached) before being recharged at the Sustained Downlink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. Max Burst Uplink Data Rate These parameters allow operators to specify the data rate at which a SM is allowed to transmit (until burst allocation limit is reached) before being recharged at the Sustained Uplink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. Enable Broadcast /

Multicast Data Rate This parameter allows the operator to specify if Broadcast and Multicast data is rate-limited. This data rate can be entered in Kbps or PPS (Packets Per Second). Broadcast / Multicast Data Rate This parameter allows the operator to specify a data rate at which Broadcast and Multicast traffic is sent via the radio link. Number of Data Channels This parameter allows the operator to specify the number of priority channels to be used for data transmission which is configurable from 1 to 4. 1: Select 1 to enable Low Priority channel. Page 1-256 Chapter 1: Configuration Configuring quality of service 2: Select 2 to enable Low and High Priority channels. 3: Select 3 to enable Low, Medium, and High Priority channels. 4: Select 4 to enable all channels. For each enabled channel, configure the respective Downlink CIR and Uplink CIR. Low Priority Channel This parameter shows whether low priority data channel is enabled or not. Its value is derived based on the number of data channels selected. Low Priority Downlink CIR Low Priority Uplink CIR Medium Priority Channel Medium Priority Downlink CIR Medium Priority Uplink CIR This parameter is enabled by default. This field indicates the minimum rate at which low priority traffic is sent over the downlink (unless CIR is oversubscribed or RF link quality is degraded). Committed Information Rate (CIR) on page 1-237 Setting the Configuration Source on page 1-246 Note: CIR values are not applicable for proportional scheduler. This field indicates the minimum rate at which low priority traffic is sent over the uplink (unless CIR is oversubscribed or RF link quality is degraded). Setting the Configuration Source on page 1-246 Note: CIR values are not applicable for proportional scheduler. Committed Information Rate (CIR) on page 1-237 This parameter shows whether medium priority data channel is enabled or not. Its value is derived based on the number of data channels selected. This field indicates the minimum rate at which medium priority traffic is sent over the downlink (unless CIR is oversubscribed or RF link quality is degraded). Committed Information Rate (CIR) on page 1-237 Setting the Configuration Source on page 1-246 Note: CIR values are not applicable for proportional scheduler. This field indicates the minimum rate at which medium priority traffic is sent over the uplink (unless CIR is oversubscribed or RF link quality is degraded). Committed Information Rate (CIR) on page 1-237 Setting the Configuration Source on page 1-246 Note: CIR values are not applicable for proportional scheduler. High Priority Channel High Priority Downlink CIR This field indicates the minimum rate at which high priority traffic is sent over the downlink (unless CIR is oversubscribed or RF link quality is degraded). Committed Information Rate (CIR) on page 1-237 Setting the Configuration Source on page 1-246 Page 1-257 Chapter 1: Configuration Configuring quality of service High Priority Uplink CIR Note: CIR values are not applicable for proportional scheduler. This field indicates the minimum rate at which high priority traffic is sent over the uplink (unless CIR is oversubscribed or RF link quality is degraded). Committed Information Rate (CIR) on page 1-237 Setting the Configuration Source on page 1-246 Note: CIR values are not applicable for proportional scheduler. Ultra High Priority Channel This parameter allows the operator to enable or disable one of the data channels with the highest priority bandwidth. Downlink Plan This parameter allows the operator to configure the default downlink plan. The value range for this parameter is 1 310000 kbps. Uplink Plan Weight This parameter allows the operator to configure the default uplink plan. The value range for this parameter is 1 310000 kbps. This parameter ranges from 0.1 to 9.9 to prioritize SM services. This is a scaling factor to be applied to the Downlink and Uplink plan. Note: There is only one weight used for a plan in both directions. The default value for this parameter is 1.0. User Lock Modulation This parameter contains the following three modes. Disable: When disabled, the Proportional scheduler allocates resources to meet the configured plan. When there is congestion, the Proportional scheduler allocates a reduced value proportional to the other plans regardless of the modulation. If the modulation of one SM degrades, the resources allocated to meet this SMs plan increases, affecting the overall sector capacity. The reduced capacity is divided among all SMs proportional to their plans affecting all SMs. Enable: When enabled, the Locked Modulation drop-down list is enabled supporting values from 1x to 8x. Enable Below Threshold: When enabled, the Threshold Modulation drop-

down list is enabled supporting values from 2x to 8x. In this mode, the proportional scheduler behaves as per the Disabled mode until SMs modulation is above the configured Threshold Modulation. If the modulation goes below the Threshold Modulation, then proportional scheduler behaves as per the Enabled mode using the Threshold Modulation as Locked Modulation. Using Locked Modulation, the proportional scheduler guarantees an amount of resources required to transfer data corresponding to the configured plan. If the SMs modulation decreases, the resource allocation is not changed but the SMs throughput is reduced which is no longer proportional to the configured plan. Therefore, the SMs plan is scaled down proportional to the reduced modulation resulting in not affecting other SMs throughput based on one SMs modulation degrading. Page 1-258 Locked Modulation Chapter 1: Configuration Configuring quality of service Threshold Modulation Using Threshold Modulation, if one SMs modulation degrades, then all other SMs throughputs are affected as long as the degraded modulation is above the threshold. Once the modulation goes below the threshold, the reaources are no longer increased for that SM, effectively capping the effect to other SMs. Priority Precedence Allows operator to decide if 802.1p or DiffServ priority bits must be used first when making priority decisions. PPPoE Control Message Priority Prioritize TCP ACK Operators may configure the SM to utilize the high priority channel for PPPoE control messages. Configuring the SM in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the SM. To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. This parameter, when enabled, can be particularly useful when running bi-direction FTP sessions over the link. If a link is primarily used for video surveillance, it is recommended to configure this parameter to Disabled. Prioritization Group This parameter allows to configure the SM with high or low prioritization. Quality of Service (QoS) page of BHM The QoS page of BHM is explained in Table 86. Table 86 QoS page attributes - BHM Attribute Meaning PPPoE Control Message Priority Operators may configure the BHM to utilize the high priority channel for PPPoE control messages. Configuring the BHM in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the BHS. Page 1-259 Chapter 1: Configuration Configuring quality of service Prioritize TCP ACK To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. This parameter, when enabled, can be particularly useful when running bi-direction FTP sessions over the link. If a link is primarily used for video surveillance, it is recommended to configure this parameter to Disabled. Quality of Service (QoS) page of BHS The QoS page of BHS is explained in Table 87. Table 87 QoS page attributes - BHS Attribute Meaning PPPoE Control Message Priority Prioritize TCP ACK Operators may configure the BHS to utilize the high priority channel for PPPoE control messages. Configuring the BHS in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the BHS. To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. This parameter, when enabled, can be particularly useful when running bi-direction FTP sessions over the link. If a link is primarily used for video surveillance, it is recommended to configure this parameter to Disabled. Page 1-260 Chapter 1: Configuration Installation Color Code Installation Color Code With this feature enabled on the AP and SM, operators may install and remotely configure SMs without having to configure matching color codes between the modules. While the SM is accessible for configuration from above the AP (for remote provisioning) and below the SM (for local site provisioning), no user data is passed over the radio link. When using the Installation Color Code feature, ensure that the SM is configured with the factory default Color Code configuration (Color Code 1 is 0, Color Code 2-10 set to 0 and Disable). The status of the Installation Color Code can be viewed on the AP Eval web GUI page, and when the SM is registered using the Installation Color Code the message SM is registered via ICC Bridging Disabled! is displayed in red on every SM GUI page. The Installation Color Code parameter is configurable without a radio reboot for both the AP and SM. If an SM is registered via Installation Color Code and the feature is then disabled, operators will need to reboot the SM or force it to reregister (i.e. using the Rescan APs functionality on the AP Eval page). Figure 42 Installation Color Code of AP Page 1-261 Chapter 1: Configuration Zero Touch Configuration Using DHCP Option 66 Zero Touch Configuration Using DHCP Option 66 This feature allows an SM to get its configuration via DHCP option 66. This can be used for the initial configuration of an SM as well as managing the configuration of SMs on an ongoing basis. Here is how it works in brief:

When the SM boots up, if it is set to use DHCP client, it will send out a DHCP Discover packet which includes a request for DHCP Option 66. In case of a brand new SM out of the box, the DHCP Discover packet is sent out if the SM connects to an AP using Installation Color Code (ICC), even though DHCP client is not enabled in factory default config. An appropriately configured DHCP server will respond with a DHCP Offer and include a URL in response to the Option 66 request. The URL should point to the configuration file. The device will download the configuration file and apply it. The device will reboot automatically if needed. (Note: this requires rebootIfRequired flag to be added to the config file. See Creating a Golden config file on page 1-263. Configuration Steps Procedure 15 Zero Touch Configuration steps 1 Create the golden config file(s) 2 Host it on an TFTP/FTP/HTTP/HTTPS server 3 Configure the DHCP server to return the URL of the golden config file in option 66 When the SM boots up, it will get the URL for the golden config from the DHCP server via option 66, download it and apply it. If all the SMs are configured exactly the same, then you can create just new golden config file that can be used with all SMs. If the SMs are not configured the same, see if it is possible to group the SMs such that SMs with the same configuration are served by the same DHCP pool. User can then create multiple golden config files and configure the DHCP server to use the appropriate config file for each pool. User can also create one config file per SM. This provides the most flexibility, but is practical only if you have a software tool/script to generate the config files for each MAC address. The files should be named <mac>.cfg where <mac> is the MAC address of the SM, and stored in the same directory on the file server. The DHCP server should be configured to return the directory name ending with a / in option 66. The SM will automatically add <mac>.cfg to the path and get its config file. If some configuration is unique per SM, but rest of the configuration is common, the SMs can be staged with the unique part, and use option 66 to manage the common part. For example, if each SM needs to have its coordinates set, dont include the coordinates in the golden config file. Instead, configure the coordinates for each SM manually. Manage the rest of the configuration using DHCP option 66. Page 1-262 Chapter 1: Configuration Zero Touch Configuration Using DHCP Option 66 Creating a Golden config file The easiest way to create the golden config file is to configure an SM, export its configuration and edit it. To export the configuration file from the GUI of the SM, go to Configuration > Unit Settings tab, go to the Download Configuration File section and click on the <mac>.cfg link. This will give you a text file in JSON format. You can edit this file in a text editor but its easier to use a JSON editor like https://www.jsoneditoronline.org/. Strip down the config file to remove sections and entries that dont care about, and keep only the items that require changes. If there are many required changes, it can easily get confusing. To identify the exact items changes, first reset the SM to factory default, export the config file, make the necessary changes, export a second config file, then use a tool like WinMerge (http://winmerge.org/) to identify the differences. The config file contains the following informational entries at the top level. cfgUtcTimestamp: cfgUtcTimestamp, swVersion: CANOPY 15.1 SM-AES, cfgFileString: Canopy configuration file, srcMacAddress: 0a-00-3e-a2-c2-74, deviceType: 5.4/5.7GHz MIMO OFDM - Subscriber Module, cfgFileVersion: 1.0 The cfgUtcTimestamp, swVersion, srcMacAddress and deviceType lines can be deleted. Do not delete the cfgFileString and cfgFileVersion entries. Next, create an object named configFileParameters at the top level. Under that, add a parameter called rebootIfRequired and set it to true. This tells the SM to reboot automatically if a reboot is needed to apply the new configuration. A sample configuration file that has been edited for use via DHCP option 66 is given below.

{

userParameters: {

smNetworkConfig: {

networkAccess: 1

}, location: {

siteName: Test site

}, smRadioConfig: {

frequencyScanList: [

5475000, 5480000

], colorCodeList: [

Page 1-263 Chapter 1: Configuration Zero Touch Configuration Using DHCP Option 66

{

colorCode: 42, priority: 1

}

]

}, networkConfig: {

lanDhcpState: 1

}

}, cfgFileVersion: 1.0, cfgFileString: Canopy configuration file, configFileParameters: {

rebootIfRequired: true

}

}

When configuration is imported, only the items that exist in the configuration file are modified. Parameters that are not in the imported file are not changed. If user wish to revert those settings to their factory default values, please add a setToDefaults item under configFileParameters section with a value of true. cfgFileVersion: 1.0, cfgFileString: Canopy configuration file, configFileParameters: {

rebootIfRequired: true, setToDefaults: true

}

In case, the SM needs to fetch the configuration file on each boot up even when not connecting to AP via ICC, set Network Accessibility to Public and DHCP State to Enabled in the Configuration >

IP page before exporting the configuration. Hosting the config file Copy the golden configuration file to an FTP, TFTP, HTTP or HTTPS server. This location can be password protected; you just have to include the user name and password in the URL. DHCP server configuration Configure DHCP server to return the full URL to the golden config file as the value of DHCP option 66. The following example explains how to make the change for Windows Server 2008. Adapt it to your specific DHCP server. Procedure 16 DHCP server configuration 1 Click Start > Administrative Tools > DHCP Page 1-264 Chapter 1: Configuration Zero Touch Configuration Using DHCP Option 66 2 If you have multiple Scopes defined, identify the correct Scope that will serve IP addresses for the SMs 3 Right click on Scope Option under the correct Scope and select Configure Options Page 1-265 Chapter 1: Configuration Zero Touch Configuration Using DHCP Option 66 4 In the Scope Options dialog, scroll down to 066 Boot Server Host Name, select the checkbox and enter the full URL to the golden config file as the String value. Then click OK. 5 In the DHCP snap-in window, right click and Refresh to see the DHCP option 66 in the list of DHCP options Supported URL Formats ftp://10.120.163.253/canopy.cfg ftp://admin:admin123@10.120.163.253/canopy.cfg (login as admin with password admin123) tftp://10.120.163.253/canopy.cfg FTP, TFTP, HTTP and HTTPS URLs are supported. Some examples are given below. http://10.120.163.253/golden-config.cfg https://10.120.163.253/smconfig/golden-config.cfg User can also specify the URL pointing to a directory and not a specific file. Terminate the URL with a /

to indicate that it is a directory and not a file. Use this format when each SM has its own individual config file. The directory should contain files named <mac>.cfg, one for each SM. For example:

ftp://10.120.163.253/smconfig/

Page 1-266 Chapter 1: Configuration Zero Touch Configuration Using DHCP Option 66 In this case, the SM will append <mac>.cfg to the path and try to get that file. For example, if the SMs MAC address is 0a-00-3e-a2-c2-74, it will request for ftp://10.120.163.253/smconfig/0a003ea2c274.cfg. This mechanism can be used to serve individual config file for each SM. Troubleshooting 1 Ensure that the___14 SM is running 13.3 or newer version of software. 2 3 If the SM has factory default config, confirm ICC is enabled on the AP, so the SM can connect to it. If the SM is connecting to the AP using a color code other than ICC, make sure the SM has Network Accessibility set to Public and DHCP State set to Enabled in the Configuration > IP page. 4 Make sure the golden config file does not turn off Network Accessibility or DHCP State. If it does, the SM will no longer request the config file when it is rebooted. 5 Check the event log of the SM to see the status of the configuration file import including any errors that prevented it from importing the file. 6 Capture the DHCP Offer packet from the DHCP server to the SM and verify that Option 66 has the expected URL. Page 1-267 Chapter 1: Configuration Configuring Radio via config file Configuring Radio via config file The 450 Platform Family supports export and import of a configuration file from the AP or SM as a text file. The configuration file is in JSON format. To export or import the configuration file, the logged in user needs to be an ADMINISTRATOR and it must not be a read-only account. The exported configuration file contains the complete configuration including all the default values. To keep a backup of the current configuration, the file can be saved as-is and imported later. While importing a configuration file, it can be either imported the full configuration or a sparse configuration containing only the items that need to be changed. If a sparse configuration file is imported, only the items in the file will be imported. Other configuration will remain unchanged. There could also be used a special flag in the configuration file to tell the device to apply the configuration starting from factory default (Refer Special Headers for configuration file on page 1-269). Import and Export of config file The config file import and export is supported in Configuration > Unit Settings page. The procedure for importing and exporting config file is explained below. Figure 43 Configuration File upload and download page The DHCP server configuration procedure is as follows:

Procedure 17 DHCP server configuration 1 Login to the GUI and go to Configuration > Unit Settings. 2 Under Download Configuration File tab, click on the <mac>.cfg link, where <mac> is the MAC address of the device (for example, 01003ea2c274.cfg). 3 Save the file to the local disk. The below procedure is to be followed for Importing a config file Procedure 18 Import the configuration from the GUI 1 Login to the GUI and go to Configuration Unit Settings. Page 1-268 Chapter 1: Configuration Configuring Radio via config file 2 Click on Browse button under Upload and Apply Configuration File tab and select the configuration file from disk. 3 Click Upload followed by Apply Configuration File button click. 4 The Status of Configuration File section will show the results of the upload. 5 Review it to make sure there are no errors. Then click on Reboot to reboot with the imported configuration The special headers for config file is explained below:

Procedure 19 Special Headers for configuration file 1 A configFileParameters section can be added to the header to control the behavior of the device when importing configuration. 2 The setToDefaults when set to true tell the device to reset to factory default configuration and apply the configuration in the file on top of that. So any attribute not in the configuration file will be set to its factory default value. By default, the configuration in the file is merged with the existing configuration on the device. The rebootIfRequired flag when set to true tell the device to reboot automatically if needed to apply the configuration change. By default, the device will not reboot automatically.

{

cfgFileString: Canopy configuration file, cfgFileVersion: 1.0, configFileParameters: {

setToDefaults:true, rebootIfRequired:true,

}

}

Page 1-269 Chapter 1: Configuration Configuring cnMaestroTM Connectivity Configuring cnMaestroTM Connectivity 450 Platform Family network can be onboarded, configured and managed using cnMaestro Cloud or On Premises Server. Onboarding Onboarding can be done in one of several ways:

Using Cambium ID and Onboarding key Using Manufacturers Serial Number (Only if it starts with an M and is 12 characters long) On Premises Zero Touch onboarding of AP/SM using DHCP option 43 and 15 PMP SM Zero touch onboarding to the cnMaestro server where PMP AP is onboarded. To configure the PMP devices, enable Remote Management under Configuration->cnMaestro as shown in Table 88. Table 88 Configuring cnMaestro Attribute Meaning Remote Management This field enables/disables remote management of 450 Platform Family products. cnMaestro URL This field allows to enter cnMaestro URL e.g. https://cloud.cambiumnetworks.com Or cnMaestro on premises URL Connection Status This field indicates cnMaestro connectivity status. Cambium ID This field allows to enter Cambium ID for onboarding 450 Platform devices. Onboarding Key This field allows to enter Onboarding Key for onboarding. AccountID This field indicates Account ID of the customer. Device Agent Version This field shows device agent version. Page 1-270 Chapter 1: Configuration Configuring cnMaestroTM Connectivity Prerequisites for onboarding to cnMaestro Devices types must be PMP 450m Series, PMP/PTP 450 Series, PMP/PTP 450i/450b Series or PMP 430 Series SMs (interoperability mode only). Minimum required software version of 14.2.1. Device software images can be downloaded from http://support.cambiumnetworks.com or from the On Premises cnMaestro server by navigating to Operate >Software Update->Manage Images. Select Device type to display the available images and then click the download icon as shown in Figure 44. Figure 44 Software Upgrade from cnMaestro IP connectivity between PMP Device and the cnMaestro server is established. Ensure Port 443 is open in the firewall as this port is used for secure communication between the PMP device and the cnMaestro server through web sockets. In addition, if the PMP device and cnMaestro server are on different subnets, proper routes should be established for communication. For PMP AP, a valid DNS setting is required so that the AP will be able to resolve the cnMaestro URL. DNS settings can be verified by performing a DNS lookup under Tools->DNS Test on the AP as shown in Figure 45. Page 1-271 Chapter 1: Configuration Configuring cnMaestroTM Connectivity Figure 45 DNS Test for cnMaestro connectivity If the SM is in Bridge mode, then LAN1 must have public 1-272equest1-272ility with a public IP assigned and corresponding DNS setting. If the SM is in NAT mode, then Remote Management should be enabled with the standalone configuration option and DNS settings. Knowledge Based articles for onboarding For onboarding the devices to cloud server and troubleshooting the onboarding issues in cloud server please see the following link:

http://community.cambiumnetworks.com/t5/cnMaestro/Device-On-boarding/td-p/51484 For onboarding the devices to on Premises server and configuring the DHCP server options for on boarding please see the following link:

http://community.cambiumnetworks.com/t5/cnMaestro/Device-Onboarding-and-Linux-DHCP-Options-

for-cnMaestro-On/m-p/55187#U55187 Order of Device Onboarding The device discovery order is as follows in On Permises cnMaestro Server. If any of the options is not configured, the discovery method will fallback to the next option:

1. Static cnMaestro URL 2. Zero Touch token (on boarding of PMP SMs when the corresponding AP is on boarded) 3. DHCP Option 43 4. DHCP Option 15 5. https://cloud.cambiumnetworks.com Device Agent Logs For debugging any onboarding issues please check the device agent logs by navigating to Logs->Device Agent Logs on the PMP device GUI as shown in Figure 46. In addition, a tech support dump can for the PMP device can be obtained from cnMaestro by navigating to Page 1-272 Chapter 1: Configuration Configuring cnMaestroTM Connectivity Monitor->Tools menu after selecting the particular PMP device in the tree and clicking the tech support file icon. This can be send to Cambium support for further troubleshooting. Figure 46 Device Agent Logs Monitoring Tools for PMP Devices on cnMaestro cnMaestro as of this release offers several debugging tools for PMP devices. Some examples are:

Pictorial view of network hierarchy Device status Tech support file Throughput Alarms Reboot Debug Logs Network connectivity ping and DNS lookup Figure 47 Example cnMaestro screenshot Page 1-273 Chapter 1: Configuration Configuring cnMaestroTM Connectivity For more information on these tools please see http://community.cambiumnetworks.com/t5/cnMaestro/How-to-use-the-cnMaestro-Tools-for-

Troubleshooting-Device-or/m-p/54503#U54503 Zero Touch on boarding of the PMP SMs when the corresponding AP is on boarded First a link should be established between the PMP AP and SM either by configuring manually or using the ICC. Once the AP and SM link is established, the AP must be onboarded to cnMaestro using one of several ways detailed above under the Onboarding section. Once the AP is onboarded to cnMaestro Cloud or On premises cnMaestroserver, the SMs under the AP will automatically onboard to cnMaestro using a Zero touch token that is communicated between the AP and SMs. This is applicable to existing SMs registered to the AP as well as new SMs registering to the AP for the first time. The SMs appear on the onboarding queue of cnMaestro and the operator must Approve the devices in order to manage them. The following operations for PMP Devices are available on cnMaestro:

Monitor the device details in the Dashboard page by navigating to the Monitor >Dashboard menu and selecting the PMP AP/SM in the tree. Monitor notifications related to the PMP AP/SM by navigating to the Monitor >Notifications Menu and selecting the PMP AP/SM in the tree. Monitor device statistics on the statistics page by navigating to the Monitor >Statistics menu and selecting the PMP AP/SM in the tree, then selecting the PMP AP or PMP SM in the Device type dropdown. Monitor Performance graphs related to the PMP AP/SM by navigating to the Monitor >Performance menu and selecting the required performance graph (i.e Throughput, SMs, Modulation) and selecting the PMP AP/SM in the tree. Troubleshoot the device on the Troubleshooting page by navigating to the Monitor >Tools menu and selecting the PMP AP/SM in the tree. Configure the devices by navigating to the Configure >Devices menu and selecting the PMP AP/SM in the tree and selecting the config template that needs to be pushed to the device. Configuration templates need to be created before the configuration can be pushed to the device. The template can be created by copying the existing configuration from the view device configuration link provided in the same page and then modifying the template as needed and then pushing to the same device or other similar devices. Template needs to be properly reviewed for IP Address and other critical parameters to avoid stranding SMs (resulting in a truck roll) by pushing an incorrect configuration. Configuration templates can be created by navigating to the Configure->Templates page and selecting the PMP device type while creating the template. Once on 14.2.1, PMP devices can be upgraded to future supported versions from cnMaestro by navigating to the Operate > Software Update page and selecting the PMP Sectors option from the device type drop-down and the version to which the device needs to be upgraded. It is recommended to upgrade the AP first, then the SMs. PMP Device Inventory details can be reviewed by navigating to the Monitor >Inventory page. Page 1-274 Chapter 1: Configuration Configuring a RADIUS server Configuring a RADIUS server Configuring a RADIUS server in a PMP 450 Platform network is optional, but can provide added security, increase ease of network management and provide usage-based billing data. Understanding RADIUS for PMP 450 Platform Family PMP 450 Platform modules include support for the RADIUS (Remote Authentication Dial In User Service) protocol supporting Authentication and Accounting. RADIUS Functions RADIUS protocol support provides the following functions:

SM Authentication allows only known SMs onto the network (blocking rogue SMs), and can be configured to ensure SMs are connecting to a known network (preventing SMs from connecting to rogue APs). RADIUS authentication is used for SMs, but is not used for APs. SM Configuration: Configures authenticated SMs with MIR (Maximum Information Rate), CIR

(Committed Information Rate), Medium Priority, High Priority, and Ultra High Priority Data channels, and VLAN (Virtual LAN) parameters from the RADIUS server when a SM registers to an AP. User Authentication allows users to configure a separate User authentication server along with the SM authentication server. If firmware is upgraded while using this functionality and no User authentication servers are configured, then AP continues to use the SM authentication server for User authentication SM Accounting provides support for RADIUS accounting messages for usage-based billing. This accounting includes indications for subscriber session establishment, subscriber session disconnection, and bandwidth usage per session for each SM that connects to the AP. Centralized AP and SM user name and password management allows AP and SM usernames and access levels (Administrator, Installer, Technician) to be centrally administered in the RADIUS server instead of on each radio and tracks access events (logon/logoff) for each username on the RADIUS server. This accounting does not track and report specific configuration actions performed on radios or pull statistics such as bit counts from the radios. Such functions require an Element Management System (EMS) such as Cambium Networks Wireless Manager. This accounting is not the ability to perform accounting functions on the subscriber/end user/customer account. Framed IP allows operators to use a RADIUS server to assign management IP addressing to SM modules (framed IP address). Tested RADIUS Servers The Canopy RADIUS implementation has been tested and is supported on FreeRADIUS, Version 2.1.8 Aradial RADIUS, Version 5.1.12 Microsoft RADIUS (Windows Server 2012 R2 version) Cisco ACS, Version 5.7.0.15 Page 1-275 Chapter 1: Configuration Configuring a RADIUS server Note Aradial 5.3 has a bug that prevents remote device login, so doesnt support the user name and password management feature. Choosing Authentication Mode and Configuring for Authentication Servers - AP On the APs Configuration > Security tab, select the RADIUS AAA Authentication Mode. The following describes the other Authentication Mode options for reference, and then the RADIUS AAA option. Disabled: Requires no authentication. Any SM (except a SM that itself has been configured to require RADIUS authentication by enabling Enforce Authentication as described below) is allowed to register to the AP. Authentication Server: Authentication Server in this instance refers to Wireless Manager in BAM-

only mode. Authentication is required for a SM to register to the AP. Only SMs listed by MAC address in the Wireless Manager database is allowed to register to the AP. AP Pre-Shared Key: Canopy offers a pre-shared key authentication option. In this case, an identical key must be entered in the Authentication Key field on the APs Configuration > Security tab and in the Authentication Key field on each desired SMs Configuration > Security tab. RADIUS AAA: To support RADIUS authentication of SMs, on the APs Configuration > Security tab select RADIUS AAA. Only properly configured SMs with a valid certificate is allowed to register to the AP. When RADIUS AAA is selected, up to 3 Authentication Server (RADIUS Server) IP addresses and Shared Secrets can be configured. The IP address(s) configured here must match the IP address(s) of the RADIUS server(s). The shared secret(s) configured here must match the shared secret(s) configured in the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not splitting the database. If Server 1 doesnt respond, Server 2 is tried, and then server 3. If Server 1 rejects authentication, the SM is denied entry to the network, and does not progress trying the other servers. The default IP address is 0.0.0.0. The default Shared Secret is CanopySharedSecret. The Shared Secret can be up to 32 ASCII characters (no diacritical marks or ligatures, for example). Page 1-276 Chapter 1: Configuration Table 89 Security tab attributes Configuring a RADIUS server Page 1-277 Chapter 1: Configuration Configuring a RADIUS server Attribute Meaning Authentication Mode Operators may use this field to select the following authentication modes:

Disabledthe AP requires no SMs to authenticate. Authentication Server the AP requires any SM that attempts registration to be authenticated in Wireless Manager before registration. AP PreShared Key - The AP acts as the authentication server to its SMs and will make use of a user-configurable pre-shared authentication key. The operator enters this key on both the AP and all SMs desired to register to that AP. There is also an option of leaving the AP and SMs at their default setting of using the Default Key. Due to the nature of the authentication operation, if you want to set a specific authentication key, then you MUST configure the key on all of the SMs and reboot them BEFORE enabling the key and option on the AP. Otherwise, if you configure the AP first, none of the SMs is able to register. RADIUS AAA - When RADIUS AAA is selected, up to 3 Authentication Server (RADIUS Server) IP addresses and Shared Secrets can be configured. The IP address(s) configured here must match the IP address(s) of the RADIUS server(s). The shared secret(s) configured here must match the shared secret(s) configured in the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not for splitting the database. If Server 1 doesnt respond, Server 2 is tried, and then server 3. If Server 1 rejects authentication, the SM is denied entry to the network and does not progress trying the other servers. The management DNS domain name may be toggled such that the name of the authentication server only needs to be specified and the DNS domain name is automatically appended to that name. Enter the IP address or server name of the authentication server (RADIUS or WM) and the Shared Secret configured in the authentication server. When Authentication Mode RADIUS AAA is selected, the default value of Shared Secret is CanopySharedSecret. The Shared Secret may consist of up to 32 ASCII characters. This field allows the operator to configure a custom port for RADIUS server communication. The default value is 1812. The authentication key is a 32-character hexadecimal string used when Authentication Mode is set to AP Pre-Shared Key. By default, this key is set to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF. Page 1-278 Authentication Server DNS Usage Authentication Server 1 Authentication Server 2 Authentication Server 3 Authentication Server 4 (BAM Only) Authentication Server 5 (BAM Only) Radius Port Authentication Key Chapter 1: Configuration Configuring a RADIUS server Selection Key This option allows operators to choose which authentication key is used:

Use Key above means that the key specified in Authentication Key is used for authentication Use Default Key means that a default key (based off of the SMs MAC address) is used for authentication Encryption Key Specify the type of airlink security to apply to this AP. The encryption setting must match the encryption setting of the SMs. None provides no encryption on the air link. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. You can use this field to suppress the display of data about this AP on the AP Evaluation tab of the Tools page in all SMs that register. Enter the expiry in seconds for remote management sessions via HTTP, telnet, or ftp access to the AP. You can permit access to the AP from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address If you selected IP Access Filtering Enabled for the IP Access Control parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the AP from any IP address. You may populate as many as all three. SM Display of AP Evaluation Data Web, Telnet, FTP Session Timeout IP Access Control Allowed Source IP 1 Allowed Source IP 2 Allowed Source IP 3 If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. Web Access SNMP The Radio supports secured and non-secured web access protocols. Select suitable web access from drop-down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. This option allows to configure SNMP agent communication version. It can be selected from drop-down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is secured communication protocol. Page 1-279 Chapter 1: Configuration Configuring a RADIUS server Telnet FTP TFTP SNMPv2c and SNMPv3 It enables both the protocols. This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. NTP server This option allows to Enable and Disable NTP server access to the Radio. SM Authentication Mode Require RADIUS or Follow AP If it is desired that a SM will only authenticate to an AP that is using RADIUS, on the SMs Configuration Security tab set Enforce Authentication to AAA. With this enabled, SM does not register to an AP that has any Authentication Mode other than RADIUS AAA selected. If it is desired that a SM use the authentication method configured on the AP it is registering to, set Enforce Authentication to Disabled. With Enforce Authentication disabled, a SM will attempt to register using whichever Authentication Mode is configured on the AP it is attempting to register to. Page 1-280 Chapter 1: Configuration Configuring a RADIUS server Note Having SMs to use RADIUS by enabling Enforce Authentication avoids the security issue of SMs possibly registering to rogue APs, which have authentication disabled. Table 90 SM Security tab attributes Page 1-281 Chapter 1: Configuration Configuring a RADIUS server Attribute Meaning Authentication Key Select Key Enforce Authentication Phase 1 Phase 2 The authentication key is a 32-character hexadecimal string used when Authentication Mode is set to AP PreShared Key. By default, this key is set to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF. This option allows operators to choose which authentication key is used:

Use Key above means that the key specified in Authentication Key is used for authentication Use Default Key means that a default key (based off of the SMs MAC address) is used for authentication The SM may enforce authentication types of AAA and AP Pre-sharedKey. The SM will not finish the registration process if the AP is not using the configured authentication method (and the SM locks out the AP for 15 minutes). Enforce Authentication default setting is Disable. The protocols supported for the Phase 1 (Outside Identity) phase of authentication are EAPTTLS (Extensible Authentication Protocol Tunneled Transport Layer Security) or MSCHAPv2 (Microsoft Challenge-Handshake Authentication Protocol version 2). Select the desired Phase 2 (Inside Identity) authentication protocol from the Phase 2 options of PAP (Password Authentication Protocol), CHAP

(Challenge Handshake Authentication Protocol), and MSCHAP (Microsofts version of CHAP, version 2 is used). The protocol must be consistent with the authentication protocol configured on the RADIUS server. Page 1-282 Chapter 1: Configuration Configuring a RADIUS server Identity/Realm Username Password Confirm Password Upload Certificate File Encryption Setting If Realms are being used, select Enable Realm and configure an outer identity in the Identity field and a Realm in the Realm field. These must match the Phase 1/Outer Identity and Realm configured in the RADIUS server. The default Identity is anonymous. The Identity can be up to 128 non-special (no diacritical markings) alphanumeric characters. The default Realm is canopy.net. The Realm can also be up to 128 non-special alphanumeric characters. Configure an outer Identity in the Username field. This must match the Phase 1/Outer Identity username configured in the RADIUS server. The default Phase 1/Outer Identity Username is anonymous. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. Enter a Username for the SM. This must match the username configured for the SM on the RADIUS server. The default Username is the SMs MAC address. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. Enter the desired password for the SM in the Password and Confirm Password fields. The Password must match the password configured for the SM on the RADIUS server. The default Password is password. The Password can be up to 128 non-special (no diacritical markings) alphanumeric characters. To upload a certificate manually to a SM, first load it in a known place on your PC or network drive, then click on a Delete button on one of the Certificate description blocks to delete a certificate to provide space for your certificate. Click on Choose File, browse to the location of the certificate, and click the Import Certificate button, and then reboot the radio to use the new certificate. When a certificate is in use, after the SM successfully registers to an AP, an indication of In Use will appear in the description block of the certificate being used. The public certificates installed on the SMs are used with the private certificate on the RADIUS server to provide a public/private key encryption system. Up to 2 certificates can be resident on a SM. An installed certificate can be deleted by clicking the Delete button in the certificates description block on the Configuration > Security tab. To restore the 2 default certificates, click the Use Default Certificates button in the RADIUS Certificate Settings parameter block and reboot the radio. Specify the type of airlink security to apply to this AP. The encryption setting must match the encryption setting of the SMs. None provides no encryption on the air link. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. Page 1-283 Chapter 1: Configuration Configuring a RADIUS server Web, Telnet, FTP Session Timeout Enter the expiry in seconds for remote management sessions via HTTP, telnet or ftp access to the AP. If you want to prevent any device that is connected to the Ethernet port of the SM from accessing the management interface of the SM, select Ethernet Access Disabled. This selection disables access through this port to via HTTP (the GUI), SNMP, telnet, FTP, and TFTP. With this selection, management access is available through only the RF interface via either an IP address (if Network Accessibility is set to Public on the SM) or the Session Status or Remote Subscribers tab of the AP. See IP Access Control below. If you want to allow management access through the Ethernet port, select Ethernet Access Enabled. This is the factory default setting for this parameter. You can permit access to the AP from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address If you selected IP Access Filtering Enabled for the IP Access Control parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the AP from any IP address. You may populate as many as all three. If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. The Radio supports secured and non-secured web access protocols. Select suitable web access from drop-down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. This option allows to configure SNMP agent communication version. It can be selected from drop-down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. Ethernet Access IP Access Control Allowed Source IP 1 Allowed Source IP 2 Allowed Source IP 3 Web Access SNMP Telnet FTP Page 1-284 Chapter 1: Configuration Configuring a RADIUS server TFTP This option allows to Enable and Disable TFTP access to the Radio. SM - Phase 1 (Outside Identity) parameters and settings The protocols supported for the Phase 1 (Outside Identity) phase of authentication are eapttls (Extensible Authentication Protocol Tunneled Transport Layer Security) and eapMSChapV2

(Extensible Authentication Protocol Microsoft Challenge-Handshake Authentication Protocol). Configure an outer Identity in the Username field. This must match the Phase 1/Outer Identity username configured in the RADIUS server. The default Phase 1/Outer Identity Username is anonymous. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. If Realms are being used in the RADIUS system (eapttls only), select Enable Realm and configure an outer identity in the Identity field and a Realm in the Realm field. These must match the Phase 1/Outer Identity and Realm configured in the RADIUS server. The default Identity is anonymous. The Identity can be up to 128 non-

special (no diacritical markings) alphanumeric characters. The default Realm is canopy.net. The Realm can also be up to 128 non-special alphanumeric characters. SM - Phase 2 (Inside Identity) parameters and settings If using eapttls for Phase 1 authentication, select the desired Phase 2 (Inside Identity) authentication protocol from the Phase 2 options of PAP (Password Authentication Protocol), CHAP (Challenge Handshake Authentication Protocol), and MSCHAPv2 (Microsofts version of CHAP). The protocol must be consistent with the authentication protocol configured on the RADIUS server. Enter a Username for the SM. This must match the username configured for the SM on the RADIUS server. The default Username is the SMs MAC address. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. Enter the desired password for the SM in the Password and Confirm Password fields. The Password must match the password configured for the SM on the RADIUS server. The default Password is password. The Password can be up to 128 non-special (no diacritical markings) alphanumeric characters. Handling Certificates Managing SM Certificates via the SM GUI The default public Canopy certificates are loaded into SMs upon factory software installation. The default certificates are not secure and are intended for use during lab and field trials as part of gaining experience with the RADIUS functionalities or as an option during debug. For secure operation, an operator will want to create or procure their own certificates. Resetting a SM to its factory defaults will remove the current certificates and restore the default certificates. Up to two certificates can be resident on a SM. An installed certificate can be deleted by clicking the Delete button in the certificates description block on the Configuration > Security tab. To restore the 2 default certificates, click the Use Default Certificates button in the RADIUS Certificate Settings parameter block and reboot the radio. To upload a certificate manually to a SM, first load it in a known place on your PC or network drive, then click on a Delete button on one of the Certificate description blocks to delete a certificate to provide space for your certificate. Click on Choose File, browse to the location of the certificate, and click the Import Certificate button, and then reboot the radio to use the new certificate. Page 1-285 Chapter 1: Configuration Configuring a RADIUS server When a certificate is in use, after the SM successfully registers to an AP, an indication of In Use will appear in the description block of the certificate being used. The public certificates installed on the SMs are used with the private certificate on the RADIUS server to provide a public/private key encryption system. Note Root certificates of more than one level (Example - a certificate from someone who received their CA from Verisign) fails. Certificates must be either root or self-signed. Figure 48 SM Certificate Management Configuring RADIUS servers for SM authentication Your RADIUS server must be configured to use the following:

EAPTTLS or MSCHAPv2 as the Phase 1/Outer Identity protocol. Page 1-286 Chapter 1: Configuration Configuring a RADIUS server If Enable Realm is selected on the SMs Configuration > Security tab, then the same Realm appears there (or access to it). The same Phase 2 (Inner Identity) protocol as configured on the SMs Configuration > Security tab under Phase 2 options. The username and password for each SM configured on each SMs Configuration > Security tab. An IP address and NAS shared secret that is the same as the IP address and Shared Secret configured on the APs Configuration > Security tab for that RADIUS server. A server private certificate, server key, and CA certificate that complement the public certificates distributed to the SMs, as well as the Canopy dictionary file that defines Vendor Specific Attributes (VSAa). Default certificate files and the dictionary file are available from the software site: https://support.cambiumnetworks.com/files/pmp450 after entering your name, email address, and either Customer Contract Number or the MAC address of a module covered under the 12 month warranty. Optionally, operators may configure the RADIUS server response messages (Accept or Reject) so that the user has information as to why they have been rejected. The AP displays the RADIUS Authentication Reply message strings in the Session Status list as part of each SMs information. The SM will show this string (listed as Authentication Response on the SM GUI) on the main Status page in the Subscriber Module Stats section. Note Aradial AAA servers only support operator-configurable Authentication Accept responses, not Authentication Reject responses. Page 1-287 Chapter 1: Configuration Configuring a RADIUS server Assigning SM management IP addressing via RADIUS Operators may use a RADIUS AAA server to assign management IP addressing to SM modules (framed IP address). SMs now interpret attributes Framed-IP-Address, Framed-IP-Netmask, and Cambium-

Canopy-Gateway from RADIUS. The RADIUS dictionary file has been updated to include the Cambium-

Canopy-Gateway attribute and is available on the Cambium Software Support website. In order for these attributes to be assigned and used by the SM, the following must be true:

The system is configured for AAA authentication The SM is not configured for DHCP on its management interface. If DHCP is enabled and these attributes are configured in the RADIUS server, the attributes is ignored by the SM. The SM management interface must be configured to be publically accessible. If the SM is configured to have local accessibility, the management interface will still be assigned the framed addressing, and the SM iscome publicly accessible via the assigned framed IP addressing. When using these attributes, for the addressing to be implemented by the SM operators must configure Framed-IP-Address in RADIUS. If Framed-IP-Address is not configured but Framed-IP-

Netmask and/or Cambium-Canopy-Gateway is configured, the attributes is ignored. In the case where only the Framed-IP-Address is configured, Framed-IP-Netmask defaults to 255.255.0.0 (NAT disabled) / 255.255.255.0 (NAT enabled) and Cambium-Canopy-Gateway defaults to 0.0.0.0. Configuring RADIUS server for SM configuration Canopy Vendor Specific Attributes (VSAs) along with VSA numbers and other details are listed in Table 91. The associated SM GUI page, tab and parameter are listed to aid cross-referencing and understanding of the VSAs. A RADIUS dictionary file is available from the software site:

https://support.cambiumnetworks.com/files/pmp450 The RADIUS dictionary file defines the VSAs and their values and is usually imported into the RADIUS server as part of server and database setup. Page 1-288 Chapter 1: Configuration Configuring a RADIUS server Note Beginning with System Release 12.0.2, two RADIUS dictionary files are available on the Cambium website RADIUS Dictionary file Cambium and RADIUS Dictionary file Motorola. In addition to a renaming of attributes, the Cambium-branded dictionary file contains two new VSAs for controlling uplink and downlink Maximum Burst Data Rate (these VSAs are listed below in Table 91). If you are transitioning from the Motorola-branded dictionary file to the Cambium-branded dictionary file, ensure that all RADIUS profiles containing Motorola-Canopy attribute references are updated to include Cambium-Canopy attribute references (for all applicable VSAs listed in Table 91). Also, ensure that all RADIUS configuration files reference the new dictionary file (as an alternative, operators may rename the Cambium-branded dictionary file to the filename currently in use by the RADIUS server). Once the profiles are updated and the new Cambium-branded dictionary file is installed on the RADIUS server, restart the RADIUS server to ensure that the new VSAs and attribute names are enabled. Table 91 RADIUS Vendor Specific Attributes (VSAs) Name Number Type Required Value MS-MPPE-Send-Key*

26.311.16

-

MS-MPPE-Recv-Key*

26.311.17

-

-

-

Cambium-Canopy-LPULCIR 26.161.1 integer Y Y N

-

-

-

-

0-65535 kbps

-

-

Configuration > Quality of Service > Low Priority Uplink CIR 0 kbps 32 bits Cambium-Canopy-LPDLCIR 26.161.2 integer N 0-65535 kbps Configuration > Quality of Service > Low Priority Downlink CIR 0 kbps 32 bits Cambium-Canopy-HPULCIR 26.161.3 integer N 0-65535 kbps Configuration > Quality of Service > High Priority Uplink CIR 0 kbps 32 bits Cambium-Canopy-HPDLCIR 26.161.4 integer N 0-65535 kbps Configuration > Quality of Service > High Priority Uplink CIR 0 kbps 32 bits Cambium-Canopy-HPENABLE 26.161.5 integer N 0-disable, 1-enable Configuration > Quality of Service > High Priority Channel Enable/Disable 0 32 bits 26.161.6 integer N 0-100000 kbps Configuration > Quality of Service > Sustained Uplink Data Rate dependent on radio feature set 32 bits Cambium-Canopy-ULBL 26.161.7 integer N 0-2500000 kbps Page 1-289 Chapter 1: Configuration Configuring a RADIUS server Configuration > Quality of Service > Uplink Burst Allocation dependent on radio feature set 32 bits Cambium-Canopy-DLBR 26.161.8 integer N 0-100000 kbps Configuration > Quality of Service > Sustained Downlink Data Rate dependent on radio feature set 32 bits Cambium-Canopy-DLBL 26.161.9 integer N 0-2500000 kbps Configuration > Quality of Service > Downlink Burst Allocation dependent on radio feature set 32 bits Cambium-Canopy-VLLEARNEN 26.161.14 integer N 0-disable, 1-enable Configuration > VLAN > Dynamic Learning 1 Cambium-Canopy-VLFRAMES 26.161.15 integer N 0-all, 1-tagged, 2-

untagged Configuration > VLAN > Allow Frame Types 0 32 bits 32 bits Cambium-Canopy-VLIDSET 26.161.16 integer N VLAN Membership (1-

4094) Configuration > VLAN Membership 0 32 bits Cambium-Canopy-VLAGETO 26.161.20 integer N 5 - 1440 minutes Configuration > VLAN > VLAN Aging Timeout Cambium-Canopy-VLIGVID 26.161.21 integer N Configuration > VLAN > Default Port VID 25 mins 1 4094 1 Cambium-Canopy-VLMGVID 26.161.22 integer N 1 4094 Configuration > VLAN > Management VID 1 32 bits 32 bits 32 bits Cambium-Canopy-

VLSMMGPASS 26.161.23 integer N 0-disable, 1-enable Configuration > VLAN > SM Management VID Pass-through 1 Cambium-Canopy-BCASTMIR 26.161.24 integer N 0-100000 kbps, 0=disabled Configuration > Quality of Service > Broadcast/Multicast Uplink Data Rate dependent on radio feature set Cambium-Canopy-Gateway 26.161.25 ipaddr N

-

Configuration > IP > Gateway IP Address 0.0.0.0 Cambium-Canopy-ULMB 26.161.26 integer N 0-100000 kbps 32 bits 32 bits

-

Configuration > Quality of Service > Max Burst Uplink Data Rate 0 32 bits Cambium-Canopy-DLMB 26.161.27 integer N 0-100000 kbps Configuration > Quality of Service > Max Burst Downlink Data Rate 0 32 bits Page 1-290 Chapter 1: Configuration Configuring a RADIUS server Cambium-Canopy-UserLevel 26.161.50 integer N Account > Add User > Level Cambium-Canopy-DHCP-State 26.161.31 integer Configuration > IP > DHCP state Cambium-Canopy-

BCASTMIRUNITS Configuration > QoS >

Broadcast Downlink CIR Cambium-Canopy-

ConfigFileImportUrl 26.161.28 integer 26.161.29 string Configuration > Unit Settings Cambium-Canopy-

ConfigFileExportUrl 26.161.30 string Configuration > Unit Settings N N N N 1-Technician, 2-

Installer, 3-

Administrator 0 1-Enable 1 0 0 0 32 bits 32 bits 32 bits 32 bits 32 bits Cambium-Canopy-UserMode 26.161.51 integer N 1=Read-Only 0=Read-

Write Account > Add User > User Mode 0 32 bits

(*) Contains key for encrypting packets sent by the NAS to the remote host (for Microsoft Point-to-Point Encryption Protocol). Note VSA numbering:

26 connotes Vendor Specific Attribute, per RFC 2865 26.311 is Microsoft Vendor Code, per IANA Configuring RADIUS server for SM configuration using Zero Touch feature The RADIUS VSA (Vendor Specific Attributes) is updated for Zero Touch feature. This feature enables the ability for a SM to get its configuration via RADIUS VSA. The RADIUS VSA is updated for an URL which points to the configuration file of SM (see Table 91 for list of VSA). The RADIUS will push the vendor specific attribute to SM after successful authentication. The VSA contains URL of config file which will redirect SM to download configuration. If there is any change in SM confirmation, the SM will reboot automatically after applying the configuration. Page 1-291 Chapter 1: Configuration Configuring a RADIUS server The RADIUS VSA attributes concerning Zero Touch are as follows:

VSA Type String Cambium-Canopy-ConfigFileImportUrl (29) string Maximum Length 127 characters. Cambium-Canopy-ConfigFileExportUrl (30) string Maximum Length 127 characters. The updated RADIUS dictionary can be downloaded from below link:

https://support.cambiumnetworks.com/files/pmp450/

Note The feature is not applicable to the AP. Using RADIUS for centralized AP and SM user name and password management AP Technician/Installer/Administrator Authentication To control technician, installer, and administrator access to the AP from a centralized RADIUS server:

Procedure 20 Centralized user name and password management for AP 1 2 Set Authentication Mode on the APs Configuration > Security tab to RADIUS AAA Set User Authentication Mode on the APs Account > User Authentication tab (the tab only appears after the AP is set to RADIUS authentication) to Remote or Remote then Local. Local: The local SM is checked for accounts. No centralized RADIUS accounting (access control) is performed. Remote: Authentication by the centralized RADIUS server is required to gain access to the SM if the SM is registered to an AP that has RADIUS AAA Authentication Mode selected. For up to 2 minutes a test pattern is displayed until the server responds or times out. Remote then Local: Authentication using the centralized RADIUS server is attempted. If the server sends a reject message, then the setting of Allow Local Login after Reject from AAA determines if the local user database is checked or not. If the configured servers do not respond within 2 minutes, then the local user database is used. The successful login method is displayed in the navigation column of the SM. 4. User administration and authentication separation On the AP, it is possible to configure up to three User Authentication servers, along with their Shared Secret. If none of the User Authentication servers are configured, the AP continues to use SM Authorization servers for User Authentication. If at least one of the IP addresses is configured, all Authentication, Authorization, and Accounting requests now follow the newly configured User Authorization server. To configure separate User Authentication and SM Authentication:

Page 1-292 Chapter 1: Configuration Configuring a RADIUS server Procedure 21 User administration and authentication separation 1 2 3 4 Go to the APs Account > User Authentication And Access Tracking tab Set User Authentication Mode to Remote or Remote then Local. Set User Authentication Method to EAP-MD5 or EAP-PEAP-MSCHAPv2 Configure the Shared Secrets and IP Addresses of:

User Authentication Server 1 User Authentication Server 2 User Authentication Server 3 Note: If none of the above User Authentication servers are configured, only SM authentication will be performed. 5 Under RADIUS Certificate Settings, click Browse to upload the RADIUS Certificate files. Page 1-293 Chapter 1: Configuration Configuring a RADIUS server Table 92 AP User Authentication and Access Tracking attributes Attribute Meaning User Authentication Mode Local: The local SM is checked for accounts. No centralized RADIUS accounting (access control) is performed. Remote: Authentication by the centralized RADIUS server is required to gain access to the AP. For up to 2 minutes a test pattern is displayed until the server responds or times out. Page 1-294 Chapter 1: Configuration Configuring a RADIUS server Remote then Local: Authentication using the centralized RADIUS server is attempted. If the server sends a reject message, then the setting of Allow Local Login after Reject from AAA determines if the local user database is checked or not. If the configured servers do not respond within 2 minutes, then the local user database is used. The successful login method is displayed in the navigation column of the AP. User Authentication Method The user authentication method employed by the radios:

EAP-MD5 EAP-PEAP-MSCHAPv2 Allow Local Login after Reject from AAA If a user authentication is rejected from the AAA server, the user is allowed to login locally to the radios management interface. User Authentication Server 1 The IP address and the shared secret key of the User authentication RADIUS server 1. User Authentication Server 2 The IP address and the shared secret key of the User Authentication Server 2 configured in RADIUS Server. User Authentication Server 3 The IP address and the shared secret key of the User Authentication Server 3 configured in RADIUS Server. RADIUS Certificate Settings User Authentication Certificate 1 User Authentication Certificate 2 Import Cetificate browse and select the file to be uploaded and click on Import Certificate to import a new certificate. Use Default Certificates use the preloaded default certificates. Cerificate provided by default for User authentication. Cerificate provided by default for User authentication. Radius Accounting Port The destination port on the AAA server used for Radius accounting communication. Accounting Messages disable no accounting messages are sent to the RADIUS server. deviceAccess accounting messages regarding device access are sent to the RADIUS server (see Table 94). dataUsage accounting messages regarding data usage are sent to the RADIUS server (see Table 94). All accounting messages regarding device access and data usage are sent to the RADIUS server. Accounting Data Usage Interval The interval for which accounting data messages are sent from the radio to the RADIUS server. If 0 is configured for this parameter, no data usage messages are sent. SM Re-authentication Interval The interval for which the SM will re-authenticate to the RADIUS server. Account Status Displays the account status. Page 1-295 Chapter 1: Configuration Configuring a RADIUS server SM Technician/Installer/Administrator Authentication The centralized user name and password management for SM is same as AP. Follow AP Technician/Installer/Administrator Authentication on page 1-292 procedure. Note Remote access control is enabled only after the SM registers to an AP that has Authentication Mode set to RADIUS AAA. Local access control will always be used before registration and is used after registration if the AP is not configured for RADIUS. Figure 49 User Authentication and Access Tracking tab of the SM Table 93 SM User Authentication and Access Tracking attributes Attribute Meaning User Authentication Mode Local: The local SM is checked for accounts. No centralized RADIUS accounting (access control) is performed. Page 1-296 Chapter 1: Configuration Configuring a RADIUS server Remote: Authentication by the centralized RADIUS server is required to gain access to the SM if the SM is registered to an AP that has RADIUS AAA Authentication Mode selected. For up to 2 minutes a test pattern is displayed until the server responds or times out. Remote then Local: Authentication using the centralized RADIUS server is attempted. If the server sends a reject message, then the setting of Allow Local Login after Reject from AAA determines if the local user database is checked or not. If the configured servers do not respond within 2 minutes, then the local user database is used. The successful login method is displayed in the navigation column of the SM. If a user authentication is rejected from the AAA server, the user is allowed to login locally to the radios management interface. It is applicable ONLY when the User Authentication Mode is set to Remote then Local. Note When the radio User Authentication Mode is set to Local or Remote, the Allow Local Login after Reject from AAA does not any effect. disable no accounting messages are sent to the RADIUS server deviceAccess accounting messages are sent to the RADIUS server regarding device access (see Table 94). Allow Local Login after Reject from AAA Accounting Messages Access Tracking To track logon and logoff times on individual radios by technicians, installers, and administrators, on the AP or SMs Account > User Authentication and Access Tracking tab under Accounting (Access Tracking) set Accounting Messages to deviceAccess. Device Access Tracking is enabled separately from User Authentication Mode. A given AP or SM can be configured for both, either, or neither. RADIUS Device Data Accounting PMP 450 Platform systems include support for RADIUS accounting messages for usage-based billing. This accounting includes indications for subscriber session establishment, subscriber session disconnection, and bandwidth usage per session for each SM that connects to the AP. The attributes included in the RADIUS accounting messages are shown in the table below. Table 94 Device data accounting RADIUS attributes Sender Message Attribute Value Description AP Acct-Status-Type 1 - Start Page 1-297 Chapter 1: Configuration Configuring a RADIUS server Sender Message Attribute Value Description Acct-Session-Id Accounting-

Request Event-Timestamp Unique per AP session. Initial value is SM MAC, and increments after every start message sent of an in session SM. UTC time the event occurred on the AP This message is sent every time a SM registers with an AP, and after the SM stats are cleared. This message is sent every time a SM becomes unregistered with an AP, and when the SM stats are cleared. Acct-Status-Type 2 - Stop Acct-Session-Id Acct-Input-Octets AP Accounting-

Request Acct-Output-Octets Acct-Input-

Gigawords Acct-Output-

Gigawords Acct-Input-Packets Unique per AP session. Initial value is SM MAC, and increments after every start message sent of an in session SM. Sum of the input octets received at the SM over the Low Priority data channel as well as any Medium, High, and Ultra High Priority data channels configured.. Will not include broadcast. Sum of the output octets sent from the SM over the Low Priority data channel as well as any Medium, High, and Ultra High Priority data channels configured.. Number of times the Acct-

Input-Octets counter has wrapped around 2^32 over the course of the session Number of times the Acct-

Output-Octets counter has wrapped around 2^32 over the course of the session Sum of unicast and multicast packets that are sent to a particular SM over the regular data VC and the high priority data VC (if enabled). It will not include broadcast. Page 1-298 Chapter 1: Configuration Configuring a RADIUS server Sender Message Attribute Value Description AP Accounting-

Request This message is sent periodically per the operator configuration on the AP in seconds. Interim update counts are cumulative over the course of the session Acct-Output-

Packets Sum of unicast and multicast packets that are sent from a particular SM over the Low Priority data channel as well as any Medium, High, and Ultra High Priority data channels configured.. Acct-Session-Time Uptime of the SM session. Acct-Terminate-

Cause Reason code for session termination Acct-Status-Type 3 - Interim-Update Acct-Session-Id Acct-Input-Octets Acct-Output-Octets Acct-Input-

Gigawords Acct-Output-

Gigawords Unique per AP session. Initial value is SM MAC, and increments after every start message sent of an in session SM. Sum of the input octets sent to the SM over the Low Priority data channel as well as any Medium, High, and Ultra High Priority data channels configured.. Will not include broadcast. Sum of the output octets set from the SM over the Low Priority data channel as well as any Medium, High, and Ultra High Priority data channels configured. Number of times the Acct-

Input-Octets counter has wrapped around 2^32 over the course of the session Number of times the Acct-

Output-Octets counter has wrapped around 2^32 over the course of the session Acct-Session-Time Uptime of the SM session. Page 1-299 Chapter 1: Configuration Configuring a RADIUS server Sender Message Attribute Value Description Acct-Input-Packets Acct-Output-

Packets Sum of unicast and multicast packets that are sent to a particular SM over the regular data VC and the high priority data VC (if enabled). It will not include broadcast. Sum of unicast and multicast packets that are sent from a particular SM over the regular data VC and the high priority data VC (if enabled). The data accounting configuration is located on the APs Accounts > User Authentication and Access Tracking GUI menu, and the APs Authentication Mode must be set to Radius AAA for the menu to appear. The accounting may be configured via the AP GUI as shown in the figures below. By default accounting messages are not sent and the operator has the choice of configuring to send only Device Access accounting messages (when a user logs in or out of the radio), only Data Usage messages, or both. When Data Accounting is enabled, the operator must specify the interval of when the data accounting messages are sent (0 disabled, or in the range of 30-10080 minutes). The default interval is 30 minutes. Figure 50 RADIUS accounting messages configuration The data accounting message data is based on the SM statistics that the AP maintains, and these statistics may be cleared on the AP by an operator. If an operator clears these messages and data accounting is enabled, an accounting stop message is sent followed by an accounting start message to notify the AAA of the change. If an operator clears the VC statistics on the device through the management GUI, a RADIUS stop message and data start message is issued for each device affected. The start and stop messages will only be sent once every 5 minutes, so if an operator clears these statistics multiple times within 5 minutes, only one set of data stop/start messages is sent. This may result in inaccurate data accumulation results. RADIUS Device Re-authentication PMP 450 Platform systems include support for periodic SM re-authentication in a network without requiring the SM to re-register (and drop the session). The re-authentication may be configured to occur in the range of every 30 minutes to weekly. Page 1-300 Chapter 1: Configuration Configuring a RADIUS server Figure 51 Device re-authentication configuration The re-authentication interval is only configurable on the AP. When this feature is enabled, each SM that enters the network will re-authenticate each the interval time has expired without dropping the session. The response that the SM receives from the AAA server upon re-authentication is one of the following:

Success: The SM continues normal operation Reject: The SM de-registers and will attempt network entry again after 1 minute and then if rejected will attempt re-entry every 15 minutes Timeout or other error: The SM remains in session and attempt 5 times to re-authenticate with the RADIUS-REQUEST message. If these attempts fail, then the SM will go out of session and proceed to re-authenticate after 5 minutes, then every 15 minutes. Although re-authentication is an independent feature, it was designed to work alongside with the RADIUS data usage accounting messages. If a user is over their data usage limit the network operator can reject the user from staying in the network. Operators may configure the RADIUS Reply-Message attribute with an applicable message (i.e. Data Usage Limit Reached) that is sent to the subscriber module and displayed on the general page. Page 1-301 Chapter 1: Configuration Configuring a RADIUS server RADIUS Change of Authorization and Disconnect Message Prior to this feature, SM will get configuration parameters from a RADIUS server during authentication process. This feature allows an administrator to control configuration parameters in the SM while SM is in session. The configuration changes in SM are done using RADIUS Change of Authorization method (RFC 3576) on the existing RADIUS authentication framework for AP and SM. A typical use case could be changing the QOS parameters after a certain amount of bandwidth usage by a SM. Figure 52 RADIUS CoA configuration for AP The RADIUS CoA feature enables initiating a bi-directional communication from the RADIUS server(s) to the AP and SM. The AP listens on UDP port 3799 and accepts CoA requests from the configured RADIUS servers. This CoA request should contain SM MAC address in User-Name attribute as identifier and all other attributes which control the SM config parameters. For security reasons, a timestamp also needs to be added as Event-Timestamp attribute. Hence the time should also be synchronized between the RADIUS server(s) and the AP to fit within a window of 300 seconds. Once the configuration changes are applied on the SM, CoA-ACK message is sent back to RADIUS server. If the validation fails, the AP sends a CoA-NACK response to the RADIUS server with proper error code. A Disconnect-Message is sent by the RADIUS server to NAS in order to terminate a user session on a NAS and discard all associated session context. It is used when the authentication AAA server wants to disconnect the user after the session has been accepted by the RADIUS. In response of Disconnect-Request from RADIUS server, the NAS sends a Disconnect-ACK if all associated session context is discarded, or a Disconnect-NACK, if the NAS is unable to disconnect the session. Page 1-302 Chapter 1: Configuration Configuring a RADIUS server Note The RADIUS CoA feature will only enabled if Authentication mode is set to RADIUS AAA. Page 1-303 Chapter 1: Configuration Configuring a RADIUS server Microsoft RADIUS support This feature allows to configure Microsoft RADIUS (Network Policy and Access Services a.k.a NPS) as Authentication server for SM and User authentication. For SM Authentication, SM will user PEAP-MSCHAPv2 since NPS doesnt support TTLS protocol. For User Authentication, the Canopy software will use EAP-MD5 but the user has to do certain configuration in order to enable EAP-MD5 on NPS. Note All this configuration has been tested on Windows Server 2012 R2 version. This feature is not supported on hardware board type P9 or lower platforms. SM Authentication Configuration There are no new configurations on AP. However, SM has to be configured for PEAP authentication protocol. 1. 2. Go to Configuration > Security page Select eappeap for Phase 1 attribute under tab AAA Authentication Settings. Figure 53 EAPPEAP settings The Phase 2 will change automatically to MSCHAPv2 on select of Phase 1 attribute as EAP-

PEAP. Other parameters of Phase 2 protocols like PAP/CHAP will be disabled. Import Certificate 5. Windows Server Configuration The SM certificate has to be imported to Windows Server for certificate authentication. 1. Copy the certificate which is configured in SM under Configuration > Security ->

Certificate1 to Windows Server machine. Right click and select Install Certificate. This will install the certificate and its ready for use. This certificate will be used while configuring PEAP-MSCHAPv2 in NPS. 2. Page 1-304 Chapter 1: Configuration Configuring a RADIUS server NPS Configuration (https://technet.microsoft.com/en-us/network/bb545879.aspx) Following items should be configured in NPS Console:

RADIUS Client o https://technet.microsoft.com/en-us/library/cc732929 Connection Request Policies o https://technet.microsoft.com/en-us/library/cc730866 o Choose Wireless-Other in NAS-Port-Type Network Policy o https://technet.microsoft.com/en-us/library/cc755309 o Choose Wireless-Other in NAS-Port-Type. o While configuring PEAP, select the above imported certificate. Figure 54 Importing certificate in NPS User Authentication Configuration 6. Enabling EAP-MD5 As mentioned earlier, Microsoft has deprecated the support for MD5 from versions of Windows. To enable MD5, the following steps to be followed:

1. Follow the instructions:

https://support.microsoft.com/en-us/kb/922574/en-us?wa=wsignin1.0 Optionally, the registry file can be downloaded. It can be installed by double-click it in Windows Registry. From NPS Console Network Policy > <Policy Name> > Properties > Constrains >

Authentication Method and click Add. Select MD5 and click OK. 2. Page 1-305 Chapter 1: Configuration Configuring a RADIUS server Figure 55 Selecting MD5 from NPS console 7. User Configuration in Active Directory Next open Active Directory Users and Computers and create user. Make sure user property is configured as shown below. Figure 56 User configuration Page 1-306 Chapter 1: Configuration Configuring a RADIUS server 8. RADIUS VSA Configuration Before using VSA, the Cambium-Canopy-UserLevel(50) VSA must be configured with some access level say ADMIN(3). Follow below link for configuring VSA:

https://technet.microsoft.com/en-us/library/cc731611 The Cambiums vendor code is 161. Figure 57 RADIUS VSA configuration 9. Accounting User can enable accounting in NPS under NPS Console > Accounting >

Configure Accounting. For more details refer https://technet.microsoft.com/library/dd197475 Page 1-307 Chapter 1: Configuration Configuring a RADIUS server Cisco ACS RADIUS Server Support This briefly explains how to configure Cisco ACS RADIUS server for PEAP-MSCHAPv2 authentication. The configuration had been tested on CISCO ACS Version : 5.7.0.15 Adding RADIUS client Figure 58 Adding RADIUS client Creating Users Figure 59 Creating users Page 1-308 Chapter 1: Configuration Configuring a RADIUS server Creating RADIUS instance Figure 60 Creating RADIUS instance RADIUS protocols Figure 61 RADIUS protocols Page 1-309 Configuring a RADIUS server Chapter 1: Configuration Service selection Figure 62 Service selection Adding Trusted CA Figure 63 Adding Trusted CA Note that certificate has to be in DER form, so if you have in PEM format convert using openssl. Openssl.exe x509 -in <path-to->/cacert_aaasvr.pem -outform DER -out <path-

to>/cacert_aaasvr.der Installing Server Certificate After installing trusted CA, you need to add a server certificate which will be used for TLS tunnel. Generally you have to install same certificate which is installed in your AP, so that AP can trust the radius server. Figure 64 Installing Server Certificate Page 1-310 Chapter 1: Configuration Monitoring Logs Figure 65 Monitoring logs Configuring a RADIUS server Configuring VSA Before using VSA , user has to add Cambium Vendor Specific Attribute Navigate to System Administration > Configuration > Dictionaries > Protocols > RADIUS > RADIUS VSA > Motorola If Motorola is not present you can create Vendor with ID 161 and add all the VSA one by one. Page 1-311 Chapter 1: Configuration Configuring a RADIUS server Figure 66 VSA list Using VSA for users Navigate to Access Policies > Access Services > Cambium ACS > Authorization 1. Change condition to User name 2. Next click Create and then click Select see diagram below Page 1-312 Chapter 1: Configuration Configuring a RADIUS server 3. Click Create from the screen you get following screen Chose some name and then move to RADIUS Attributes tab 4. Fill attribute which all you want for that particular user Important: Click Add for each attribute and when done click Submit. 5. Now you are ready to use this Authorization profile for the use Select and Press OK. Page 1-313 Chapter 1: Configuration Configuring a RADIUS server 6. Finally press Save Changes and you are ready to use it. Page 1-314 Chapter 1: Configuration Configuring Ping Watchdog This feature allows administrator to automatically reboot an AP/SM when there is a network issue to avoid power on reset of radios. This feature is disabled by default. To enable Ping Watchdog feature, select the menu option Configuration > Ping Watchdog, and configure the parameters listed in the following table. Table 95 Ping Watchdog attributes Attribute Meaning Ping Watchdog This filed enables or disbales Ping Watchdog feature. IP Address To Ping Ping Interval This field specifies the IPV4 address of the device which needs to be pinged. This field specifies the time interval at which ping needs to be initiated. The time interval needs to be specified in seconds. Ping Failure Count To Reboot This field specifies the count of ping failures at which reboot needs to be initiated. Page 1-315 Chapter 2: Tools Chapter 2: Tools The AP and SM GUIs provide several tools to analyze the operating environment, system performance and networking, including:

Using Spectrum Analyzer tool on page 2-317 Using the Alignment Tool on page 2-331 Using the Link Capacity Test tool on page 2-338 Using AP Evaluation tool on page 2-347 Using BHM Evaluation tool on page 2-352 Using the OFDM Frame Calculator tool on page 2-356 Using the Subscriber Configuration tool on page 2-360 Using the Link Status tool on page 2-361 Using BER Results tool on page 2-369 Using the Sessions tool on page 2-370 Using the Ping Test tool on page 2-371 Page 2-316 Chapter 2: Tools Using Spectrum Analyzer tool Using Spectrum Analyzer tool The integrated spectrum analyzer can be very useful as a tool for troubleshooting and RF planning, but is not intended to replicate the accuracy and programmability of a high-end spectrum analyzer, which sometime can be used for other purposes. The AP/BHM and SM/BHS perform spectrum analysis together in the Sector Spectrum Analyzer tool. Caution On start of the Spectrum Analyzer on a module, it enters a scan mode and drops any RF connection it may have had. When choosing Start Timed Spectrum Analysis, the scan is run for time specified in the Duration configuration parameter. When choosing Start Continuous Spectrum Analysis, the scan is run continuously for 24 hours, or until stopped manually (using the Stop Spectrum Analysis button). Any module can be used to see the frequency and power level of any detectable signal that is within, just above, or just below the frequency band range of the module. Note Vary the days and times when you analyze the spectrum in an area. The RF environment can change throughout the day or throughout the week. Mapping RF Neighbor Frequencies The neighbor frequencies can be analyzed using Spectrum Analyzer tool. Following modules allow user to:

Use a BHS or BHM for PTP and SM or AP for PMP as a Spectrum Analyzer. View a graphical display that shows power level in RSSI and dBm at 5 MHz increments throughout the frequency band range, regardless of limited selections in the Custom Radio Frequency Scan Selection List parameter of the SM/BHS. Select an AP/BHM channel that minimizes interference from other RF equipment. Caution The following procedure causes the SM/BHS to drop any active RF link. If a link is dropped when the spectrum analysis begins, the link can be re-established when either a 15 minute interval has elapsed or the spectrum analyzer feature is disabled. Temporarily deploy a SM/BHS for each frequency band range that need to monitor and access the Spectrum Analyzer tab in the Tools web page of the module. Using Spectrum Analyzer tool Page 2-317 Chapter 2: Tools Using the Remote Spectrum Analyzer tool Spectrum Analyzer tool Analyzing the spectrum Using Spectrum Analyzer tool To use the built-in spectrum analyzer functionality of the AP/SM/BH, proceed as follows:

Procedure 22 Analyzing the spectrum 1 2 3 4 5 6 7 8 9 Predetermine a power source and interface that works for the AP/SM/BH in the area to be analyzed. Take the AP/SM/BH, power source and interface device to the area. Access the Tools > Spectrum Analyzer web page of the AP/SM/BH. Enter Duration in Timed Spectrum Analyzer Tab. Default value is 10 Seconds Click Start Timed Sector Spectrum Analysis The results are displayed:

Figure 67 Spectrum analysis - Results Note AP/SM/BH scans for extra 40 seconds in addition to configured Duration Travel to another location in the area to BHS. Click Start Timed Spectrum Analysis Repeat Steps 4 and 6 until the area has been adequately scanned and logged. As with any other data that pertains to your business, a decision today to put the data into a retrievable database may grow in value to you over time. Page 2-318 Chapter 2: Tools Using Spectrum Analyzer tool Note Wherever the operator finds the measured noise level is greater than the sensitivity of the radio that is plan to deploy, use the noise level (rather than the link budget) for your link feasibility calculations. The AP/SM/BH perform spectrum analysis together in the Sector Spectrum Analyzer feature. Graphical spectrum analyzer display The AP/SM/BH display the graphical spectrum analyzer. An example of the Spectrum Analyzer page is shown in Figure 67. The navigation feature includes:

Results may be panned left and right through the scanned spectrum by clicking and dragging the graph left and right Results may be zoomed in and out using mouse When the mouse is positioned over a bar, the receive power level, frequency, maximum and mean receive power levels are displayed above the graph To keep the displayed data current, either set Auto Refresh on the modules Configuration > General. Page 2-319 Chapter 2: Tools Spectrum Analyzer page of AP The Spectrum Analyzer page of AP is explained in Table 96. Table 96 Spectrum Analyzer page attributes - AP Using Spectrum Analyzer tool Attribute Meaning Display Data Path Both means that the vertical and horizontal paths are displayed or an individual path may be selected to display only a single-path reading. Data Display For ease of parsing data and to facilitate automation, the spectrum analyzer results may be saved as an XML file. To save the results in an XML formatted file, right-click the SpectrumAnalysis.xml link and save the file. Instantaneous means that each reading (vertical bar) is displayed with two horizontal lines above it representing the max power level received (top horizontal line) and the average power level received (lower horizontal line) at that frequency. Averaging means that each reading (vertical bar) is displayed with an associated horizontal line above it representing the max power level received at that frequency. Page 2-320 Chapter 2: Tools Using Spectrum Analyzer tool Min and Max Frequencies in KHz Enter minimum and maximum frequencies to be scanned. Set Min And Max to Full Scan On the button press, it sets minimum and maximum allowed frequencies for scanning. Set Min And Max to Center Scan +/-40 MHz On the button press, it sets minimum and maximum frequencies to 40 MHz of center frequency for scanning. Registered SM Count This field displays the MAC address and Site Name of the registered SM. Maximum Count of Registered SMs SM Scanning Bandwidth Duration Perform Spectrum Analysis on Boot Up for One Scan Continuous Spectrum Analyzer This field displays the maximum number of registered SMs. This field allows to select SMs scanning bandwidth. This field allows operators to configure a specified time for which the spectrum is scanned. If the entire spectrum is scanned prior to the end of the configured duration, the analyzer will restart at the beginning of the spectrum. This field when enabled performs Spectrum Analysis on every boot up for one scan. Start Continuous Spectrum Analysis button ensures that when the SM is powered on, it automatically scans the spectrum for 10 seconds. These results may then be accessed via the Tools > Spectrum Analyzer GUI page. Page 2-321 Chapter 2: Tools Spectrum Analyzer page of SM The Spectrum Analyzer page of SM is explained in Table 99. Table 97 Spectrum Analyzer page attributes - SM Using Spectrum Analyzer tool Attribute Meaning Display Data Path Refer Table 96 on page 2-320 Data Display Refer Table 96 on page 2-320 Refer Table 96 on page 2-320 Min and Max Frequencies in KHz To scan min to max range of frequencies, enter min and max frequencies in KHz and press Set Min and Max to Full Scan button. To scan +/- 40 MHz from center frequency, enter center frequency in KHz and press Set Min And Max To Center Scan +/- 40KHz button. Session Status This field displays current session status and rates. The session states can be Scanning, Syncing, Registering or Registered. Registered AP This field displays the information of AP to which this device is registered. Scanning Bandwidth This field allows to select the scanning bandwidth when running Spectrum Analysis. Page 2-322 Chapter 2: Tools Using Spectrum Analyzer tool Duration Refer Table 96 on page 2-320 Perform Spectrum Analysis on Boot Up for One Scan This field when enabled performs Spectrum Analysis on every boot up for one scan. Power Up Mode With No 802.3 Link This field indicates whether the link has to operate in Aim mode or in operational mode on power up. Continuous Spectrum Analyzer Start Continuous Spectrum Analysis button starts the SM in Spectrum Analysis until manually stopped, or it has scanned for 24 hours. Page 2-323 Chapter 2: Tools Spectrum Analyzer page of BHM The Spectrum Analyzer page of BHM is explained in Table 98. Table 98 Spectrum Analyzer page attributes - BHM Using Spectrum Analyzer tool Attribute Data Display Duration Min and Max Frequencies in KHz Meaning Refer Table 96 on page 2-320 Refer Table 96 on page 2-320 Refer Table 96 on page 2-320 Enter minimum and maximum frequencies to be scanned. Set Min And Max to Full Scan On the button press, it sets minimum and maximum allowed frequencies for scanning. Set Min And Max to Center Scan +/-40 MHz On the button press, it sets minimum and maximum frequencies to 40 MHz of center frequency for scanning. Timing Slave Status This field displays the status of any registered Timing Slave. Page 2-324 Chapter 2: Tools Using Spectrum Analyzer tool BHS Scanning Bandwidth Duration Perform Spectrum Analysis on Boot Up for One Scan This field allows to select BHSs scanning bandwidth. This field allows operators to configure a specified time for which the spectrum is scanned. If the entire spectrum is scanned prior to the end of the configured duration, the analyzer will restart at the beginning of the spectrum. This field when enabled performs Spectrum Analysis on every boot up for one scan. Continuous Spectrum Analyzer Start Continuous Spectrum Analysis button starts the SM in Spectrum Analysis until manually stopped, or it has scanned for 24 hours. Page 2-325 Chapter 2: Tools Spectrum Analyzer page of BHS The Spectrum Analyzer page of BHS is explained in Table 99. Table 99 Spectrum Analyzer page attributes - BHS Using Spectrum Analyzer tool Attribute Data Display Session Status Meaning Refer Table 96 on page 2-320 Refer Table 96 on page 2-320 This field displays current session status and rates. The session states can be Scanning, Syncing, Registering or Registered. Registered Backhaul This field displays MAC address of BHM and PTP model number Duration Refer Table 96 on page 2-320 Perform Spectrum Analysis on Boot Up for one scan This field allows to Enable or Disable to start Spectrum Analysis on boot up of module for one scan. Page 2-326 Chapter 2: Tools Using Spectrum Analyzer tool Continuous Spectrum Analyzer Refer Table 96 on page 2-320 Spectrum Analyzer page result of PMP 450 SM Figure 68 Spectrum Analyzer page result PMP 450 SM Page 2-327 Chapter 2: Tools Using Spectrum Analyzer tool Remote Spectrum Analyzer tool The Remote Spectrum Analyzer tool in the AP/BHM provides additional flexibility in the use of the spectrum analyzer in the SM/BHS. Set the duration of 10 to 1000 seconds, then click the Start Remote Spectrum Analysis button to launch the analysis from that SM/BHS. In PMP configuration, a SM must be selected from the drop-down list before launching Start Remote Spectrum Analysis. Analyzing the spectrum remotely Procedure 23 Remote Spectrum Analyzer procedure 1 2 3 4 The AP/BHM de-registers the target SM/BHS. The SM/BHS scans (for the duration set in the AP/BHM tool) to collect data for the bar graph. The SM/BHS re-registers to the AP/BHM. The AP/BHM displays the bar graph. The bar graph is an HTML file, but can be changed to an XML file, which is then easy to analyze using scripts that you may write for parsing the data. To transform the file to XML, click the SpectrumAnalysis.xml link below the spectrum results. Although the resulting display appears mostly unchanged, the bar graph is now coded in XML. You can now right-click on the bar graph for a Save Target As option to save the Spectrum Analysis.xml file. Remote Spectrum Analyzer page of AP The Remote Spectrum Analyzer page of AP is explained in Table 100. Page 2-328 Chapter 2: Tools Table 100 Remote Spectrum Analyzer attributes - AP Using Spectrum Analyzer tool Attribute Meaning Registered SM Count This field displays the number of SMs that were registered to the AP before the SA was started. This helps the user know all the SMs re-registered after performing a SA. Maximum Count of Registered SMs Current Subscriber Module Duration This field displays the largest number of SMs that have been simultaneously registered in the AP since it was last rebooted. This count can provide some insight into sector history and provide comparison between current and maximum SM counts at a glance. The SM with which the Link Capacity Test is run. This field allows operators to configure a specified time for which the spectrum is scanned. If the entire spectrum is scanned prior to the end of the configured duration, the analyzer will restart at the beginning of the spectrum. Scanning Bandwidth This parameter defines the size of the channel scanned when running the analyzer. Page 2-329 Chapter 2: Tools Using Spectrum Analyzer tool Remote Spectrum Analyzer page of BHM The Remote Spectrum Analyzer page of BHM is explained in Table 101. Table 101 Remote Spectrum Analyzer attributes - BHM Attribute Duration Meaning Refer Table 96 on page 2-320 Note To get best performance of the link, the user has to ensure the maximum Receive Power Level during alignment by pointing correctly. The proper alignment is important to prevent interference in other cells. The achieving Receive Power Level green (>- 70 dBm) is not sufficient for the link. Page 2-330

 

 

Chapter 4: Reference information Country specific frequency range Frequency range 5.8 GHz band Table 213 Frequency range per country 5.8 GHz band PMP/PTP 450i Series Countries Antenna Type Channel BW Any USA, Canada, Brazil, Other FCC Mexico Any Other Any ETSI Any 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower 5730 5730 5732.5 5735 5740 5745 5727.5 5730 5732.5 5735 5740 5745 5727.5 5730 5732.5 5735 5740 5745 5727.5 5730 5735 5737.5 5740 5745 Upper 5845 5845 5842.5 5840 5835 5830 5847.5 5845 5842.5 5840 5835 5830 5922.5 5920 5917.5 5915 5910 5905 5872.5 5870 5867.5 5865 5860 5855 Page 4-105 Chapter 4: Reference information Country specific frequency range Table 214 Frequency range per country 5.8 GHz band PMP 450b Mid-GainSeries Countries Antenna Type Channel BW FCC 16 dBi Mid-Gain 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower 5730 5730 5732.5 5735 5740 5745 Upper 5845 5845 5842.5 5840 5835 5830 Table 215 Frequency range per country 5.8 GHz band PMP 450b High Gain Series Countries Antenna Type Channel BW FCC 23 dBi High Gain 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower 5730 5730 5732.5 5735 5740 5745 Upper 5845 5845 5842.5 5840 5835 5830 Table 216 Frequency range per country 5.8 GHz band PMP/PTP 450 Series Channel center Frequency limits (MHz) Lower 5730 5820 5732.5 5822.5 5735 5825 5740 5830 Upper 5790 5845 5787.5 5842.5 5785 5840 5780 5835 Countries Antenna Type Channel BW Any Denmark, Norway, United Kingdom, Finland 10 MHz 15 MHz 20 MHz 30 MHz Page 4-106 Chapter 4: Reference information Country specific frequency range Countries Antenna Type Channel BW Germany Any Spain Any Greece Any Portugal, Iceland, Serbia Any Switzerland, Liechtenstein Any 40 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 10 MHz Page 4-107 Channel center Frequency limits (MHz) Lower 5745 5835 5760 5762.5 5765 5770 5775 5730 5820 5732.5 5822.5 5735 5825 5740 5830 5745 5835 5730 5732.5 5735 5740 5745 5730 5732.5 5735 5740 5745 5730 5820 Upper 5775 5830 5870 5867.5 5865 5860 5855 5790 5850 5787.5 5847.5 5785 5845 5780 5840 5775 5835 5790 5787.5 5785 5780 5775 5870 5867.5 5865 5860 5855 5790 5870 Chapter 4: Reference information Country specific frequency range Countries Antenna Type Channel BW Australia Any Canada, United States Any India Any Brazil, Vietnam Any 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz Page 4-108 Channel center Frequency limits (MHz) Lower 5732.5 5822.5 5735 5825 5740 5830 5745 5835 5727.5 5730 5732.5 5735 5740 5745 5727.5 5730 5732.5 5735 5740 5745 5727.5 5730 5832.5 5735 5840 5845 5727.5 5730 5732.5 Upper 5787.5 5867.5 5785 5865 5780 5860 5775 5855 5847.5 5845 5842.5 5840 5835 5830 5847.5 5845 5842.5 5840 5835 5830 5872.5 5870 5867.5 5865 5860 5855 5847.5 5845 5842.5 Chapter 4: Reference information Country specific frequency range Countries Antenna Type Channel BW Indonesia Any Malaysia Any 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 20 MHz Channel center Frequency limits (MHz) Lower 5735 5740 5745 5727.5 5730 5732.5 5735 5727.5 5830 5835 Upper 5840 5835 5830 5822.5 5820 5817.5 5815 5872.5 5870 5865 Page 4-109 Chapter 4: Reference information Country specific frequency range Table 217 Frequency range per country 5.8 GHz band PMP 450m Series Countries Antenna Type Channel BW Channel center Frequency limits (MHz) United States, FCC Any ETSI Any Other Any 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Lower 5730 5730 5732.5 5735 5740 5745 5727.5 5730 5735 5737.5 5740 5745 5727.5 5730 5732.5 5735 5740 5745 Upper 5845 5845 5842.5 5840 5835 5830 5872.5 5870 5867.5 5865 5860 5855 5922.5 5920 5917.5 5915 5910 5905 Page 4-110 Chapter 4: Reference information FCC specific information FCC specific information FCC compliance testing With GPS synchronization installed, the system has been tested for compliance to US (FCC) specifications. It has been shown to comply with the limits for emitted spurious radiation for a Class B digital device, pursuant to Part 15 of the FCC Rules in the USA. These limits have been designed to provide reasonable protection against harmful interference. However, the equipment can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to other radio communications. There is no guarantee that interference does not occur in a particular installation. Note A Class B Digital Device is a device that is marketed for use in a residential environment, notwithstanding use in commercial, business and industrial environments. Note Notwithstanding that Cambium has designed (and qualified) the 450 Platform Family ODUs to generally meet the Class B requirement to minimize the potential for interference, the 450 Platform Family ODU range is not marketed for use in a residential environment. FCC IDs Table 218 US FCC IDs FCC ID Product Z8H89FT 0021 and Z8H89FT 0022 900 MHz PMP 450i AP & PMP 450 SM Z8H89FT 0003 and Z8H89FT 004 2.4 GHz PMP 450 AP & SM 2.4 GHz Frequency Band Channel Bandwidth Frequencies Maximum Combined Tx Output Power 5 MHz 7 MHz 904.5 925.5 MHz 25 dBm 905.5 924.5 MHz 25 dBm 900 MHz 10 MHz 907.0 923.0 MHz 25 dBm 15 MHz 909.5 920.5 MHz 25 dBm 20 MHz 912.0 918.0 MHz 25 dBm 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 2402.5 2480.0 MHz 19 dBm 2405.0 2477.5 MHz 19 dBm 2407.5 2475.0 MHz 19 dBm 2410.0 2472.5 MHz 19 dBm 2415.0 2467.5 MHz 19 dBm Page 4-111 Chapter 4: Reference information FCC specific information FCC ID Product Frequency Band Channel Bandwidth Frequencies Maximum Combined Tx Output Power Z8H89FT 0009 and Z8H89FT 0010 Z8H89FT 0009 and Z8H89FT 0010 3.5 GHz PMP 450i AP & SM 3.5 GHz 3.65 GHz PMP 450i AP & SM 3.65 GHz 3.5 GHz PMP 450 AP & SM 3.5 GHz 3.65 GHz PMP 450 AP & SM 3.65 GHz 5 MHz 7 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 7 MHz 10 MHz 15 MHz 20 MHz 3452.5 3647.5 MHz 25 dBm 3453.5 3646.5 MHz 25 dBm 3455.0 3645 MHz 25 dBm 3457.5 3642.5 MHz 25 dBm 3460.0 3640 MHz 25 dBm 3465.0 3635 MHz 25 dBm 3470.0 3630 MHz 25 dBm 3652.5 -3697.5 MHz 19 dBm 3653.5 3696.5 MHz 21 dBm 3655.0 3695.0 MHz 22 dBm 3657.5 3692.5 MHz 24 dBm 3660.0 3690.0 MHz 25 dBm 30 MHz 3665.0 3685.0 MHz 25 dBm 40 MHz 5 MHz 7 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 7 MHz 10 MHz 15 MHz 20 MHz 3670.0 3680.0 MHz 25 dBm 3452.5 3647.5 MHz 22 dBm 3453.5 3646.5 MHz 22 dBm 3455.0 3645 MHz 22 dBm 3457.5 3642.5 MHz 22 dBm 3460.0 3640 MHz 22 dBm 3465.0 3635 MHz 22 dBm 3470.0 3630 MHz 22 dBm 3652.5 -3697.5 MHz 19 dBm 3653.5 3696.5 MHz 21 dBm 3655.0 3695.0 MHz 22 dBm 3657.5 3692.5 MHz 22 dBm 3660.0 3690.0 MHz 22 dBm 30 MHz 3665.0 3685.0 MHz 22 dBm Page 4-112 Chapter 4: Reference information FCC specific information FCC ID Product Frequency Band Channel Bandwidth Frequencies 40 MHz 3670.0 3680.0 MHz Maximum Combined Tx Output Power 22 dBm Z8H89FT 0001, Z8H89FT 0002 and QWP-

50450I 5 GHz PMP 450/

450i AP, SM & PTP 450/450i BH 4.9 GHz

(PMP/PTP 450i only) 5.1 GHz

(PMP/PTP 450i only) 5.2 GHz

(PMP/PTP 450i only) 5 MHz 4942.5 4987.5 MHz 27 dBm 10 MHz 4945.0 4985.0 MHz 27 dBm 15 MHz 4947.5 4982.5 MHz 27 dBm 20 MHz 4950.0 4980.0 MHz 27 dBm 30 MHz 4955.0 4975.0 MHz 27 dBm 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 4960.0 4970.0 MHz 27 dBm 5160.0 5247.5 MHz 21 dBm 5165.0 5245.0 MHz 23 dBm 5170.0 5242.5 MHz 23 dBm 5177.5 5240.0 MHz 23 dBm 5190.0 5235.0 MHz 22 dBm 5205.0 5230.0 MHz 22 dBm 5252.5 5330.0 MHz 20 dBm 5255.0 5340.0 MHz 27 dBm 5257.5 5337.5 MHz 27 dBm 20 MHz 5330.0 5332.5 MHz 21 dBm 30 MHz 5317.5.0 5332.5 MHz 21 dBm 40 MHz 5310.0 5325.0 MHz 21 dBm 5 MHz 10 MHz 5475.0 5720.0 MHz 27 dBm 5477.5 5717.5 MHz 27 dBm 5.4 GHz Note For 10 MHz, lower frequency at 5475.0 is also allowed with a maximum power limited to 12 dBm. 15 MHz 5478.0 5717.5 MHz 27 dBm Page 4-113 Chapter 4: Reference information FCC specific information FCC ID Product Frequency Band Channel Bandwidth Frequencies Maximum Combined Tx Output Power 20 MHz 5482.5 5715.0 MHz 27 dBm 5.8 GHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz Note For 20 MHz, center frequency at 5495.0 is the lowest allowed at full power and the maximum power for edge frequency is limited to 17 dBm. 5487.5 5710 MHz 27 dBm Note For 30 MHz, center frequency at 5495.0 is the lowest allowed at full power and the maximum power for edge frequency is limited to 23 dBm. 5497.5 5705 MHz 27 dBm Note For 40 MHz, center frequency at 5507.5 is the lowest allowed and the maximum power for edge frequency is limited to 22 dBm. 5730.0 5872.5 MHz 27 dBm 5730.0 5870.0 MHz 27 dBm Note For 10 MHz, Tx power for lower frequencies at 5730 and 5732.5 is limited to 26 dBm. 5732.5 5867.5 MHz 27 dBm Note For 15 MHz, Tx power for lower frequency at 5732.5 and 5732 is limited to 26 dBm. Tx power for higher frequencies at 5842.5, 5840, 5837.5 is limited to 26 dBm. 20 MHz 5735.0 5865.0 MHz 27 dBm Note For 20 MHz, Tx power for lower frequencies at 5735 and 5737.5 is limited to 26 dBm. Page 4-114 Chapter 4: Reference information FCC specific information FCC ID Product Frequency Band Channel Bandwidth Frequencies Z8H89FT 0032 5 GHz PMP 450b Mid-Gain SM 4.9 GHz 5.1 GHz 5 GHz 5.2 GHz Z8H89FT 0032 PMP 450b Mid-Gain SM Maximum Combined Tx Output Power 27 dBm 30 MHz 40 MHz 5 MHz 10 MHz 5740.0 5860.0 MHz 5745.0 5855.0 MHz 26 dBm 4942.5 4987.5 MHz 26 dBm 4945.0 4985.0 MHz 26 dBm 15 MHz 4947.5 4982.5 MHz 26 dBm 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 4950.0 4980.0 MHz 5155 5247.5 MHz 5155 5245.0 MHz 24 dBm 9 dBm 6 dBm 5157.5 5242.5 MHz 6 dBm 5160.0 5240.0 MHz 6 dBm 5165.0 5235.0 MHz 6 dBm 40 MHz 5170.0 5230.0 MHz 6 dBm 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 5252.5 5347.5 MHz 27 dBm 5255.0 5340.0 MHz 3 dBm 5257.5 5337.5 MHz 6 dBm 5260.0 5337.5 MHz 6 dBm 5265.0 5330.0 MHz 6 dBm 40 MHz 5270.0 5325.0 MHz 6 dBm Note For 40 MHz, channel center frequencies 5327.5 and 5330 need a power back off of 5 dB. 5 MHz 5475.0 5720.0 MHz 27 dBm 5.4 GHz 10 MHz 5477.5 5720.5 MHz 3 dBm 15 MHz 5480.0 5717.5 MHz 8 dBm Page 4-115 Chapter 4: Reference information FCC specific information FCC ID Product Frequency Band Channel Bandwidth Frequencies Maximum Combined Tx Output Power 20 MHz 30 MHz 40 MHz 5482.5 5715.0 MHz 8 dBm 5487.5 5710 MHz 8 dBm 5495.0 5705 MHz 8 dBm Note For 40 MHz, channel center frequencies 5490 and 5492.5 need a power back off of 5 dB. 5 MHz 10 MHz 5730.0 5845.0 MHz 19 dBm 5730.0 5845.0 MHz 19 dBm 5.8 GHz 15 MHz 5732.5 5842.5 MHz 19 dBm 5 GHz PMP 450b High Gain SM 4.9 GHz 5 GHz 5.1 GHz PMP 450b High Gain SM 5.2 GHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 5735.0 5840.0 MHz 19 dBm 5740.0 5835.0 MHz 19 dBm 5745.0 5830.0 MHz 27 dBm 4942-5 4987.5 MHz 4945.0 4985.0 MHz 26 dBm 26 dBm 4947.5 4982.5 MHz 26 dBm 4950.0 4980.0 MHz 24 dBm 5155.0 5245.0 MHz 10 dBm 5155.0 5245.0 MHz 8 dBm 5157.5 5242.5 MHz 8 dBm 5160.0 5240.0 MHz 8 dBm 5165.0 5235.0 MHz 8 dBm 5170.0 5230.0 MHz 8 dBm

-

-

5255.0 5340.0 MHz 2 dBm Page 4-116 Chapter 4: Reference information FCC specific information FCC ID Product Frequency Band Channel Bandwidth Frequencies Maximum Combined Tx Output Power 15 MHz 20 MHz 30 MHz 40 MHz 5257.5 5337.5 MHz 3 dBm 5260.0 5337.5 MHz 3 dBm 5265.0 5332.5 MHz 3 dBm 5270.0 5330.0 MHz 3 dBm 5 MHz

-

5.4 GHz 5.8 GHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz

-

3 dBm 5480.0 5720.0 MHz 5480.0 5717.5 MHz 6 dBm 5482.5 5715.0 MHz 6 dBm 5487.5 5710.0 MHz 6 dBm 5490.0 5705.0 MHz 6 dBm 5730.0 5845.0 MHz 21 dBm 5730.0 5845.0 MHz 21 dBm 5732.5 5842.5 MHz 21 dBm 5735.0 5840.0 MHz 21 dBm 5740.0 5835.0 MHz 21 dBm 5745.0 5830.0 MHz 21 dBm 5 MHz 4945.0 4985.0 MHz 27 dBm Z8H89FT 0001, Z8H89FT 0002 and QWP-

50450I 5 GHz PMP 450 AP, SM &

PTP 450 BH 10 MHz 4947.5 4982.5 MHz 27 dBm 5.4 GHz 15 MHz 20 MHz 30 MHz 4950.0 4980.0 MHz 27 dBm 4955.0 4975.0 MHz 27 dBm 4960.0 4970.0 MHz 27 dBm Page 4-117 Chapter 4: Reference information FCC specific information FCC ID Product Frequency Band Channel Bandwidth Frequencies Maximum Combined Tx Output Power 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 5490.0 5705 MHz 22 dBm 5730.0 5872.5 MHz 22 dBm 5730.0 5870.0 MHz 22 dBm 5732.5 5867.5 MHz 22 dBm 5735.0 5865.0 MHz 22 dBm 5740.0 5860.0 MHz 22 dBm 40 MHz 5745.0 5855.0 MHz 22 dBm 5.8 GHz

(*) 27 dBm conducted power for 450i Series and 22 dBm conducted power for 450 Series Page 4-118 Chapter 4: Reference information FCC specific information FCC ID Product Frequency Band Channel Bandwidth Frequencies Maximum Combined Tx Output Power QWP-

30450M 3.65 GHz PMP 450m AP QWP-

50450M 5 GHz PMP 450m AP 5 MHz 3652.5 -3697.5 MHz 37 dBm 3.65 GHz 20 MHz 3660.0 3690.0 MHz 39 dBm 40 MHz 3670.0 3680.0 MHz 43 dBm 5 MHz 4942.5 4987.5 MHz 48 dBm 4.9 GHz 10 MHz 4945.0 4985.0 MHz 47 dBm 15 MHz 4952.5 - 4982.5 MHz 48 dBm 20 MHz 4950.0 4980.0 MHz 48 dBm 5 MHz 5152.5 -5247.5 MHz 36 dBm 5.1 GHz 20 MHz 5160.0 5240.0 MHz 36 dBm 40 MHz 5170.0 5230.0 MHz 36 dBm 5 MHz 5252.5 5347.5 MHz 30 dBm 5.2 GHz 20 MHz 5260.0 5340.0 MHz 30 dBm 40 MHz 5270.0 5330.0 MHz 30 dBm 5 MHz 5472.5 5722.5 MHz 30 dBm 5.4 GHz 20 MHz 5480.0 5715.0 MHz 30 dBm 40 MHz 5490.0 5705.0 MHz 30 dBm 5 MHz 5727.5 5845 MHz 36 dBm 5.8 GHz 20 MHz 5735.0 5840.0 MHz 36 dBm 40 MHz 5745.0 5830.0 MHz 36 dBm Page 4-119 Chapter 4: Reference information FCC specific information FCC approved antenna list The lists of antennas which have been approved for operation by the FCC are provided in:

Table 220 for 4.9 GHz Table 221 for 5.1 and 5.2 GHz Table 222 for 5.4 GHz Table 223 for 5.8 GHz Note Any antenna of the same type and of gain equal or lower than the one approved by the FCC can be used in the countries following the FCC rules. Table 219 USA approved antenna list 4.9 GHz Directivity Type Manufacturer Reference Integrated flat plate Cambium Networks N/A 2 ft dual polarised flat plate Mars Antennas MA-WA56-DP-28N Stated Gain

(dBi) 23.0 28.0 Directional Sector 4 ft parabolic dual polarised Gabriel Antennas 6 ft parabolic dual polarised Gabriel Antennas Integrated 90 sector flat plate Integrated 90 PMP 450i AP 90 sectorised 60 sectorised Omni-

directional Dual polar omni-

directional Dual QuickFire QFD4-49-N 33.7 QuickFire QF6-49-N A005240 N/A 85009324001 85009325001 KPPA-5.7-DPOMA 37.2 16.0 17.0 17.0 17.0 13.0 Cambium Networks Cambium Networks Cambium Networks Cambium Networks KP Page 4-120 Chapter 4: Reference information FCC specific information Table 220 USA approved antenna list 5.1 and 5.2 GHz Directivity Type Manufacturer Reference Stated Gain

(dBi) Integrated flat plate Cambium Networks N/A Directional 2ft dual polarised flat plate Mars Antennas MA-WA56-DP-28N 4ft parabolic dual polarised Gabriel Antennas PX4F-52-N7A/A Integrated 90 sector flat plate Integrated 90 PMP 450i AP 90 sectorised 60 sectorised Dual polar omni-

directional Dual polar omni-

directional Cambium Networks Cambium Networks Cambium Networks Cambium Networks KP A005240 N/A 85009324001 85009325001 KPPA-5.7-DPOMA Mars Antennas MA-WO56-DP10 Sector Omni-

directional 23.0 28.5 34.5 16.0 17.0 17.0 17.0 13.0 10.0 Page 4-121 Chapter 4: Reference information FCC specific information Table 221 USA approved antenna list 5.4 GHz Directivity Type Manufacturer Reference Stated Gain

(dBi) Integrated flat plate Cambium Networks N/A Directional 2 ft dual polarised flat plate Mars Antennas MA-WA56-DP-28N 2 ft dual polarised parabolic MTI MT-486013-NVH Sector Integrated 90 sector flat plate Integrated 90 PMP 450i AP 90 sectorised 60 sectorised Omni-

directional Dual polar omni-

directional Cambium Networks Cambium Networks Cambium Networks Cambium Networks KP A005240 N/A 85009324001 85009325001 KPPA-5.7-DPOMA Dual polar omni-

directional Mars Antennas MA-WO56-DP10 23.0 28.5 28.5 16.0 17.0 17.0 17.0 13.0 10.0 Page 4-122 Chapter 4: Reference information FCC specific information Table 222 USA approved antenna list 5.8 GHz Directivity Type Manufacturer Reference Stated Gain

(dBi) 23.0 28.0 35.3 38.1 16.0 17.0 17.0 17.0 13.0 Integrated flat plate Cambium Networks N/A 2 ft dual polarised flat plate Mars Antennas MA-WA56-DP-28N Directional Sector 4 ft parabolic dual polarised Gabriel Antennas 6 ft Parabolic dual polarised Gabriel Antennas Integrated 90 sector flat plate Integrated 90 PMP 450i AP 90 sectorised 60 sectorised Omni-

directional Dual polar omni-

directional PX4F-52-N7A/A PX6F-52/A A005240 N/A 85009324001 85009325001 KPPA-5.7-DPOMA Cambium Networks Cambium Networks Cambium Networks Cambium Networks KP Page 4-123 Chapter 4: Reference information Innovation Science and Economic Development Canada (ISEDC) specific information Innovation Science and Economic Development Canada

(ISEDC) specific information 900 MHz ISEDC notification Radio Standards Specification RSS-247, Issue 1, Digital Transmission Systems (DTSs), Frequency Hopping Systems (FHSs) and License-Exempt Local Area Network (LE-LAN) Devices, is a new standard to replace annexes 8 and 9 of RSS-210, Issue 8. 4.9 GHz ISEDC notification The system has been approved under ISEDC RSS-111 for Public Safety Agency usage. The installer or operator is responsible for obtaining the appropriate site licenses before installing or using the system. Utilisation de la bande 4.9 GHz FCC et ISEDC Le systme a t approuv en vertu d ISEDC RSS-111 pour l'utilisation par l'Agence de la Scurit publique. L'installateur ou l'exploitant est responsable de l'obtention des licences de appropries avant d'installer ou d'utiliser le systme. 5.2 GHz and 5.4 GHz ISEDC notification This device complies with ISEDC RSS-247. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation. Users should be cautioned to take note that high power radars are allocated as primary users (meaning they have priority) of 5250 5350 MHz and 5650 5850 MHz and these radars could cause interference and/or damage to license-exempt local area networks (LELAN). For the connectorized version of the product and in order to reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (EIRP) is not more than that permitted by the regulations. The transmitted power must be reduced to achieve this requirement. Utilisation de la bande 5.2 and 5.4 GHz ISEDC Cet appareil est conforme ISEDC RSS-247. Son fonctionnement est soumis aux deux conditions suivantes: (1) Ce dispositif ne doit pas causer d'interfrences nuisibles, et (2) Cet appareil doit tolrer toute interfrence reue, y compris les interfrences pouvant entraner un fonctionnement indsirable. Les utilisateurs doivent prendre garde au fait que les radars haute puissance sont considres comme les utilisateurs prioritaires de 5250 5350 MHz et 5650 5850 MHz et ces radars peuvent causer des interfrences et / ou interfrer avec un rseau local ne ncessitant pas de licence. Page 4-124 Chapter 4: Reference information Innovation Science and Economic Development Canada (ISEDC) specific information Pour la version du produit avec antenne externe et afin de rduire le risque d'interfrence avec d'autres utilisateurs, le type d'antenne et son gain doivent tre choisis afin que la puissance isotrope rayonne quivalente (PIRE) ne soit pas suprieure celle permise par la rglementation. Il peut tre ncessaire de rduire la puissance transmise doit tre rduite pour satisfaire cette exigence. ISEDC notification 5.8 GHz RSS-GEN issue 3 (7.1.3) Licence-Exempt Radio Apparatus:

This device complies with ISEDC license-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device. In Canada, high power radars are allocated as primary users (meaning they have priority) of the 5600 5650 MHz spectrum. These radars could cause interference or damage to license-exempt local area network (LE-LAN) devices. Utilisation de la bande 5.8 GHz ISEDC RSS-GEN issue 3 (7.1.3) appareil utilisant la bande sans licence:

Le prsent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorise aux deux conditions suivantes : (1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible d'en compromettre le fonctionnement. Au Canada, les radars haute puissance sont dsigns comme utilisateurs principaux (ils ont la priorit) dans la bande 5600 5650 MHz. Ces radars peuvent causer des interfrences et /

ou interfrer avec un rseau local ne ncessitant pas de licence. ISEDC certification numbers Table 223 ISEDC Certification Numbers PMP 450i ISEDC Cert. Product Frequency Band Channel Bandwidth Frequencies Maximum combined Tx output power 109W-

0028 3 GHz AP, SM &

BH 5 MHz 3452.5 3647.5 MHz 46 dBm 3.45 GHz 20 MHz 3460.0 3640.0 MHz 45 dBm 40 MHz 3470.0 3630.0 MHz 46 dBm 5 MHz 3652.5 3697.5 MHz 36 dBm 3.65 GHz 20 MHz 3660.0 3690.0 MHz 42 dBm 40 MHz 3670.0 3680.0 MHz 41 dBm Page 4-125 Chapter 4: Reference information Innovation Science and Economic Development Canada (ISEDC) specific information ISEDC Cert. Product Frequency Band Channel Bandwidth Frequencies Maximum combined Tx output power 109AO-

50450I 5 GHz AP, SM &

BH 4.9 GHz 5.2 GHz 5.4 GHz 5.8 GHz 5 MHz 4942.5 4987.5 MHz 24 dBm 10 MHz 4945.0 4985.0 MHz 24 dBm 15 MHz 4952.5 - 4982.5 MHz 24 dBm 20 MHz 4950.0 4980.0 MHz 24 dBm 5 MHz 5252.5 5342.5 MHz 11 dBm 10 MHz 5255.0 5340.0 MHz 11 dBm 15 MHz 5257.5 5337.5 MHz 11 dBm 20 MHz 5260.0 5332.5 MHz 11 dBm 30 MHz 5265.0 5332.5 MHz 11 dBm 40 MHz 5270.0 5325.0 MHz 11 dBm 5 MHz 5472.5 5722.5 MHz 11 dBm 10 MHz 5475.0 5720.0 MHz 14 dBm 15 MHz 5477.5 5717.5 MHz 14 dBm 20 MHz 5480.0 5715.0 MHz 16 dBm 30 MHz 5485.0 5710.0 MHz 16 dBm 40 MHz 5490.0 5705.0 MHz 16 dBm 5 MHz 5730.0 5845.0 MHz 28 dBm 10 MHz 5730.0 5845.0 MHz 28 dBm 15 MHz 5732.5 5842.5 MHz 28 dBm 20 MHz 30 MHz 40 MHz 5735.0 5840.0 MHz 28 dBm 5740.0 5825.0 MHz 28 dBm 5745.0 5820.MHz 28dBm Table 224 ISEDC Certification Numbers PMP 450m ISEDC Cert. Product Frequency Band Channel Bandwidth Frequencies Maximum EIRP 109AO-

30450m 3GHz PMP 450m AP 3.45 GHz 5 MHz 20 MHz 3452.5 3647.5 MHz 57 dBm 3460.0 3640.0 MHz 57 dBm Page 4-126 Chapter 4: Reference information Innovation Science and Economic Development Canada (ISEDC) specific information ISEDC Cert. Product Frequency Band Channel Bandwidth Frequencies Maximum EIRP 40 MHz 5 MHz 3470.0 3630.0 MHz 57 dBm 3652.5 3697.5 MHz 57dBm 3.65 GHz 20 MHz 3660.0 3690.0 MHz 57 dBm 4.9 GHz 5.4 GHz 109A0-

50450M 5 GHz PMP 450m AP 5.8 GHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 3670.0 3680.0 MHz 57dBm 4942.5 4987.5 MHz 48 dBm 4945.0 4985.0 MHz 48 dBm 4952.5 - 4982.5 MHz 48 dBm 4950.0 4980.0 MHz 48 dBm 5472.5 5722.5 MHz 23.5 dBm 5475.0 5720.0 MHz 27 dBm 5477.5 5717.5 MHz 29 dBm 5480.0 5715.0 MHz 30 dBm 5485.0 5710.0 MHz 30 dBm 5490.0 5705.0 MHz 30 dBm 5730.0 5845.0 MHz 36 dBm 5730.0 5845.0 MHz 36 dBm 5732.5 5842.5 MHz 36 dBm 5735.0 5840.0 MHz 36 dBm 5265.0 5332.5 MHz 36 dBm 5270.0 5325.0 MHz 36 dBm Canada approved antenna list Under ISEDC regulations, this radio transmitter may only operate using an antenna of a type and maximum (or lesser) gain approved for the transmitter by ISEDC . To reduce potential radio interference to other users, the antenna type and its gain must be so chosen that the equivalent isotropically radiated power (EIRP) is not more than that necessary for successful communication. Page 4-127 Chapter 4: Reference information Innovation Science and Economic Development Canada (ISEDC) specific information Conformment la rglementation d'Industrie Canada, le prsent metteur radio peut fonctionner avec une antenne d'un type et d'un gain maximal (ou infrieur) approuv pour l'metteur par Industrie Canada. Dans le but de rduire les risques de brouillage radiolectrique l'intention des autres utilisateurs, il faut choisir le type d'antenne et son gain de sorte que la puissance isotrope rayonne quivalente (PIRE) ne dpasse pas l'intensit ncessaire l'tablissement d'une communication satisfaisante. This radio transmitter (identify the device by certification number) has been approved by ISEDC to operate with the antenna types listed in Country specific radio regulations, Innovation Science and Economic Development Canada (ISEDC) , Table 225 with the maximum permissible gain and required antenna impedance for each antenna type indicated. Antenna types not included in this list, having a gain greater than the maximum gain indicated for that type, are strictly prohibited for use with this device. Le prsent metteur radio (identifier le dispositif par son numro de certification) a t approuv par Industrie Canada pour fonctionner avec les types d'antenne numrs dans la section Country specific radio regulations, Innovation Science and Economic Development Canada (ISEDC) , Table 225 et ayant un gain admissible maximal et l'impdance requise pour chaque type d'antenne. Les types d'antenne non inclus dans cette liste, ou dont le gain est suprieur au gain maximal indiqu, sont strictement interdits pour l'exploitation de l'metteur. Page 4-128 Chapter 4: Reference information Innovation Science and Economic Development Canada (ISEDC) specific information Table 225 Canada approved antenna list 4.9 and 5.8 GHz Antenna type Description Manufacturer Reference Gain (dBi) 4.9 GHz 5.8 GHz 23 28.5 23 28 N/A 35.3 37.2 N/A 16 17.0 17 16 13 10 16 17 16 13 10 Directional Sector Integrated flat plate 2 ft dual polarised flat plate 4 ft parabolic dual polarised 6 ft Parabolic dual polarised Integrated 90 sector flat plate Cambium Networks MARS Antennas Andrews Antennas Gabriel Antennas Cambium Networks Integrated 90 PMP 450i AP Cambium Networks 90sector 60 sectorised Cambium Networks Cambium Networks N/A MA-WA56-DP-28N PX4F-52-N7A/A QF6-49-N A005240 N/A 85009324001 85009325001 Omni-

directional Omni-

directional Omni-

directional KP Antennas KPPA-5.7-DPOMA MARS Antennas MA-WO56-DP10 Page 4-129 Chapter 4: Reference information Innovation Science and Economic Development Canada (ISEDC) specific information Table 226 Canada approved antenna list 5.2 and 5.4 GHz Directivity Type Manufacturer Reference Stated Gain

(dBi) Integrated flat plate Cambium Networks N/A Directional 2ft dual polarised flat plate Mars Antennas MA-WA56-DP-28N 2ft dual polarised parabolic MTI MT-486013-NVH Integrated 90 sector flat plate Integrated 90 PMP 450i AP 90 sectorised 60 sectorised Dual polar omni-

directional Dual polar omni-

directional Cambium Networks Cambium Networks Cambium Networks Cambium Networks KP A005240 N/A 85009324001 85009325001 KPPA-5.7-DPOMA Mars Antennas MA-WO56-DP10 Sector Omni-

directional 23.0 28.5 28.5 16.0 17.0 17.0 17.0 13.0 10.0 Page 4-130 Chapter 5: Troubleshooting Chapter 5: Troubleshooting This chapter contains procedures for identifying and correcting faults in a 450 Platform Family link. These procedures can be performed either on a newly installed link, or on an operational link if communication is lost, or after a lightning strike. The following topics are described in this chapter:

General troubleshooting procedure on page 5-2 Troubleshooting procedures on page 5-5 Power-up troubleshooting on page 5-13 Registration and connectivity troubleshooting on page 5-14 Logs on page 5-15 Page 5-1 Chapter 5: Troubleshooting General troubleshooting procedure General troubleshooting procedure General planning for troubleshooting Effective troubleshooting depends in part on measures that you take before you experience trouble in your network. Cambium recommends the following measures for each site:

Identify troubleshooting tools that are available at your site (such as a protocol analyzer). Identify commands and other sources that can capture baseline data for the site. These may include:

o Ping o Tracert or traceroute o Link Capacity Test results o Throughput data o Configuration tab captures o Status tab captures o Session logs o Web browser used Start a log for the site. Include the following information in the log:

o Operating procedures o Site-specific configuration records o Network topology o Software releases, boot versions and FPGA firmware versions o Types of hardware deployed o Site-specific troubleshooting processes o Escalation procedures Capture baseline data into the log from the sources listed above Page 5-2 Chapter 5: Troubleshooting General troubleshooting procedure General fault isolation process Effective troubleshooting also requires an effective fault isolation methodology that includes the following:

Attempting to isolate the problem to the level of a system, subsystem, or link, such as o AP to SM o AP to CMM4 o AP to GPS o Backhaul (BH) o Backhaul (BH) to CMM4 o Power Interpreting messages in the Event Log Researching Event Logs of the involved equipment Answering the questions listed in the following sections. Reversing the last previous corrective attempt before proceeding to the next. Performing only one corrective attempt at a time. Questions to help isolate the problem When a problem occurs, attempt to answer the following questions:

What is the history of the problem?

o Have we changed something recently?

o Have we seen other symptoms before this?

How wide-spread is the symptom?

o o Is the problem on only a single SM? (If so, focus on that SM.) Is the problem on multiple SMs? If so is the problem on one AP in the cluster? (If so, focus on that AP) is the problem on multiple, but not all, APs in the cluster? (If so, focus on those APs) is the problem on all APs in the cluster? (If so, focus on the CMM4 and the GPS signal.) Based on data in the Event Log o does the problem correlate to External Hard Resets with no WatchDog timers? (If so, this indicates a loss of power. Correct your power problem.) is intermittent connectivity indicated? (If so, verify your configuration, power level, cables and connections and the speed duplex of both ends of the link). o o does the problem correlate to loss-of-sync events?

Are connections made via shielded cables?

Does the GPS antenna have an unobstructed view of the entire horizon?

Has the site grounding been verified?

Page 5-3 Chapter 5: Troubleshooting General troubleshooting procedure Secondary Steps After preliminary fault isolation is completed through the above steps, follow these:

Check the Canopy knowledge base (http://community.cambiumnetworks.com/) to find whether other network operators have encountered a similar problem. Proceed to any appropriate set of diagnostic steps. These are organized as follows:

o Module has lost or does not establish connectivity on page 5-5 o NAT/DHCP-configured SM has lost or does not establish connectivity on page 5-7 o SM Does Not Register to an AP on page 5-8 o Module has lost or does not gain sync on page 5-9 o Module does not establish Ethernet connectivity on page 5-10 o CMM4 does not pass proper GPS sync to connected modules on page 5-11 o Module Software Cannot be Upgraded on page 5-12 o Module Functions Properly, Except Web Interface Became Inaccessible on page 5-12 Page 5-4 Chapter 5: Troubleshooting Troubleshooting procedures Troubleshooting procedures Proceed to any appropriate set of diagnostic steps. These are organized as follows:

Module has lost or does not establish connectivity on page 5-5 NAT/DHCP-configured SM has lost or does not establish connectivity on page 5-7 SM Does Not Register to an AP on page 5-8 Module has lost or does not gain sync on page 5-9 Module does not establish Ethernet connectivity on page 5-10 CMM4 does not pass proper GPS sync to connected modules on page 5-11 Module Software Cannot be Upgraded on page 5-12 Module Functions Properly, Except Web Interface Became Inaccessible on page 5-12 Module has lost or does not establish connectivity To troubleshoot a loss of connectivity, perform the following steps:

Procedure 29 Troubleshooting loss of connectivity 1 2 3 Isolate the end user/SM from peripheral equipment and variables such as routers, switches and firewalls. Set up the minimal amount of equipment. On each end of the link:

Check the cables and connections. Verify that the cable/connection schemestraight-through or crossoveris correct. Verify that the LED labeled LNK is green. Access the General Status tab in the Home page of the module. Verify that the SM is registered. Verify that Received Power Level is -87 dBm or higher. Access the IP tab in the Configuration page of the module. Verify that IP addresses match and are in the same subnet. If RADIUS authentication is configured, ensure that the RADIUS server is operational Page 5-5 Chapter 5: Troubleshooting Troubleshooting procedures 4 5 On the SM end of the link:

Verify that the PC that is connected to the SM is correctly configured to obtain an IP address through DHCP. Execute ipconfig (Windows) or ifconfig (linux) Verify that the PC has an assigned IP address. On each end of the link:

Access the General tab in the Configuration page of each module. Verify that the setting for Link Speeds (or negotiation) matches that of the other module. Access the Radio tab in the Configuration page of each module. Verify that the Radio Frequency Carrier setting is checked in the Custom Radio Frequency Scan Selection List. Verify that the Color Code setting matches that of the other module. Access the browser LAN settings (for example, at Tools > Internet Options > Connections > LAN Settings in Internet Explorer). Verify that none of the settings are selected. Access the Link Capacity Test tab in the Tools page of the module. Perform a link test Verify that the link test results show efficiency greater than 90% in both the uplink and downlink Execute ping. o Verify that no packet loss was experienced. o Verify that response times are not significantly greater than 4 ms from AP to SM 15 ms from SM to AP o Replace any cables that you suspect may be causing the problem. Note A ping size larger than 1494 Bytes to a module times out and fails. However, a ping of this size or larger to a system that is behind a Canopy module typically succeeds. It is generally advisable to ping such a system, since Canopy handles that ping with the same priority as is given all other transport traffic. The results are unaffected by ping size and by the load on the Canopy module that brokers this traffic. 6 After connectivity has been re-established, reinstall network elements and variables that you removed in Step 1. Page 5-6 Chapter 5: Troubleshooting Troubleshooting procedures NAT/DHCP-configured SM has lost or does not establish connectivity Before troubleshooting this problem, identify the NAT/DHCP configuration from the following list:

NAT with DHCP Client (DHCP selected as the Connection Type of the WAN interface) and DHCP Server NAT with DHCP Client (DHCP selected as the Connection Type of the WAN interface) NAT with DHCP Server NAT without DHCP To troubleshoot a loss of connectivity for a SM configured for NAT/DHCP, perform the following steps. Procedure 30 Troubleshooting loss of connectivity for NAT/DHCP-configured SM 1 2 3 4 5 Isolate the end user/SM from peripheral equipment and variables such as routers, switches and firewalls. Set up the minimal amount of equipment. On each end of the link:

Check the cables and connections. Verify that the cable/connection schemestraight-through or crossoveris correct. Verify that the LED labeled LNK is green. At the SM:

Access the NAT Table tab in the Logs web page. Verify that the correct NAT translations are listed. RESULT: NAT is eliminated as a possible cause if these translations are correct. If this SM is configured for NAT with DHCP, then at the SM:

Execute ipconfig (Windows) or ifconfig (Linux) Verify that the PC has an assigned IP address. reboot the PC. If the PC does not have an assigned IP address, then o enter ipconfig /release Adapter Name. o enter ipconfig /renew Adapter Name. o o after the PC has completed rebooting, execute ipconfig o o access the NAT DHCP Statistics tab in the Statistics web page of the SM. o verify that DHCP is operating as configured. if the PC has an assigned IP address, then 6 After connectivity has been re-established, reinstall network elements and variables that you removed in Step 1. Page 5-7 Chapter 5: Troubleshooting Troubleshooting procedures SM Does Not Register to an AP To troubleshoot a SM failing to register to an AP, perform the following steps. Procedure 31 Troubleshooting SM failing to register to an AP 1 2 3 4 5 6 7 8 9 10 11 12 13 Access the Radio tab in the Configuration page of the SM. Note the Color Code of the SM. Access the Radio tab in the Configuration page of the AP. Verify that the Color Code of the AP matches that of the SM. Note the Radio Frequency Carrier of the AP. Verify that the value of the RF Frequency Carrier of the AP is selected in the Custom Radio Frequency Scan Selection List parameter in the SM. In the AP, verify that the Max Range parameter is set to a distance slightly greater than the distance between the AP and the furthest SM that must register to this AP. Verify that no obstruction significantly penetrates the Fresnel zone of the attempted link. Access the General Status tab in the Home page of each module. Remove the bottom cover of the SM to expose the LEDs. Power cycle the SM. RESULT: Approximately 25 seconds after the power cycle, the green LED labeled LNK must light to indicate that the link has been established. If the orange LED labeled SYN is lit instead, then the SM is in Alignment mode because the SM failed to establish the link. If the AP is configured to require authentication, ensure proper configuration of RADIUS or Pre-shared AP key. In this latter case and if the SM has encountered no customer-inflicted damage, then request an RMA for the SM. Page 5-8 Chapter 5: Troubleshooting Troubleshooting procedures Module has lost or does not gain sync To troubleshoot a loss of sync, perform the following steps. Procedure 32 Troubleshooting loss of sync 1 2 3 4 5 6 7 Access the Event Log tab in the Home page of the SM Check for messages with the following format:

RcvFrmNum =

ExpFrmNum =

If these messages are present, check the Event Log tab of another SM that is registered to the same AP for messages of the same type. If the Event Log of this second SM does not contain these messages, then the fault is isolated to the first SM. If the Event Log page of this second SM contains these messages, access the GPS Status page of the AP. If the Satellites Tracked field in the GPS Status page of the AP indicates fewer than 4 or the Pulse Status field does not indicate Generating Sync, check the GPS Status page of another AP in the same AP cluster for these indicators. GPS signal acquisition must not take longer than 5 minutes from unit startup. If these indicators are present in the second AP, then:

Verify that the GPS antenna still has an unobstructed view of the entire horizon. Visually inspect the cable and connections between the GPS antenna and the CMM4. If this cable is not shielded, replace the cable with shielded cable If these indicators are not present in the second AP, visually inspect the cable and connections between the CMM4 and the AP antenna. If this cable is not shielded, replace the cable with shielded cable. Page 5-9 Chapter 5: Troubleshooting Troubleshooting procedures Module does not establish Ethernet connectivity To troubleshoot a loss of Ethernet connectivity, perform the following steps:

Procedure 33 Troubleshooting loss of Ethernet connectivity 1 2 3 4 5 6 7 8 Verify that the connector crimps on the Ethernet cable are not loose. Verify that the Ethernet cable is not damaged. If the Ethernet cable connects the module to a network interface card (NIC), verify that the cable is pinned out as a straight-through cable. If the Ethernet cable connects the module to a hub, switch, or router, verify that the cable is pinned out as a crossover cable. Verify that the Ethernet port to which the cable connects the module is set to auto-

negotiate speed. Verify VLAN configuration in the network, which may cause loss of module access if the accessing device is on a separate VLAN from the radio. Power cycle the module. RESULT: Approximately 25 seconds after the power cycle, the green LED labeled LNK must light up to indicate that the link has been established. If the orange LED labeled SYN is lit instead, then the module is in Alignment mode because the module failed to establish the link. In this latter case and if the module has encountered no customer-inflicted damage, then request an RMA for the module. Page 5-10 Chapter 5: Troubleshooting Troubleshooting procedures CMM4 does not pass proper GPS sync to connected modules If the Event Log tabs in all connected modules contain Loss of GPS Sync Pulse messages, perform the following steps. Procedure 34 Troubleshooting CMM4 not passing sync 1 2 3 4 Verify that the GPS antenna has an unobstructed view of the entire horizon. Verify that the GPS coaxial cable meets specifications. Verify that the GPS sync cable meets specifications for wiring and length. If the web pages of connected modules indicate any of the following, then find and eliminate the source of noise that is being coupled into the GPS sync cable:

incorrect reported Latitude and/or Longitude of the antenna In the GPS Status page:

o anomalous number of Satellites Tracked (greater than 12, for example) o In the Event Log page:

o garbled GPS messages o large number of Acquired GPS Sync Pulse messages GPS signal acquisition must not take longer than 5 minutes from unit startup. 5 If these efforts fail to resolve the problem, then request an RMA for the CMM4. Page 5-11 Chapter 5: Troubleshooting Troubleshooting procedures Module Software Cannot be Upgraded If your attempt to upgrade the software of a module fails, perform the following steps. Procedure 35 Troubleshooting an unsuccessful software upgrade 1 2 3 4 5 6 Download the latest issue of the target release and the associated release notes. Verify that the latest version of CNUT is installed. Compare the files used in the failed attempt to the newly downloaded software. Compare the procedure used in the failed attempt to the procedure in the newly downloaded release notes. If these comparisons reveal a difference, retry the upgrade, this time with the newer file or newer procedure. If, during attempts to upgrade the FPGA firmware, the following message is repeatable, then request an RMA for the module:

Error code 6, unrecognized device Module Functions Properly, Except Web Interface Became Inaccessible If a module continues to pass traffic and the SNMP interface to the module continues to function, but the web interface to the module does not display, perform the following steps:

Procedure 36 Restoring web management GUI access 1 2 3 4 5 Enter telnet DottedIPAddress. RESULT: A telnet session to the module is invoked. At the Login prompt, enter root. At the Password prompt, enter PasswordIfConfigured. At the Telnet +> prompt, enter reset. RESULT: The web interface is accessible again and this telnet connection is closed. Note The module may also be rebooted via an SNMP-based NMS (Wireless Manager, for example) If the issue persists, turn off any SNMP-based network/radio monitoring software and repeat steps 1-4. Page 5-12 Chapter 5: Troubleshooting Power-up troubleshooting Power-up troubleshooting Module does not power ON Is Modules power LED ON?

Yes A No Is the LED always red?

No Yes Is there AC power going to the supply?

Ethernet cable repaired Yes Test cable, use known good cable. Could the radio be in default mode Switch ON AC mains power No Yes Cable wire and pin out corrected No Test cable?

Yes Connect to known good module Yes Cable length within 300 meters No Is cable length < 300 meters?

Yes Connect to a known power supply Is module getting powered ON?

Yes No Is the modules red LED ON?

No Contact Cambium Support for RMA A Yes Module is powered ON Page 5-13 Chapter 5: Troubleshooting Registration and connectivity troubleshooting Registration and connectivity troubleshooting SM/BMS Registration If no SMs are registered to this AP, then the Session Status tab displays the simple message No sessions. In this case, try the following steps. 1 2 3 4 5 6 7 8 9 More finely aim the SM or SMs toward the AP. Recheck the Session Status tab of the AP for the presence of LUIDs. If still no LUIDs are reported on the Session Status tab, click the Configuration button on the left side of the Home page. RESULT: The AP responds by opening the AP Configuration page. Click the Radio tab. Find the Color Code parameter and note the setting. In the same sequence as you did for the AP directly under Configuration Link for Test in Planning and Installation Guide, connect the SM to a computing device and to power. On the left side of the SM Home page, click the Configuration button. RESULT: The Configuration page of the SM opens. Click the Radio tab. If the transmit frequency of the AP is not selected in the Custom Radio Frequency Scan Selection List parameter, select the frequency that matches. 10 If the Color Code parameter on this page is not identical to the Color Code parameter you noted from the AP, change one of them so that they match. 11 At the bottom of the Radio tab for the SM, click the Save Changes button. 12 Click the Reboot button. 13 Allow several minutes for the SM to reboot and register to the AP. 14 Return to the computing device that is connected to the AP. 15 Recheck the Session Status tab of the AP for the presence of LUIDs. Page 5-14 Chapter 5: Troubleshooting Logs Logs Persistent Logging PMP 450 SM supports logging information such as session logs, authentication logs, and authorization logs that are persistent through reboots and connectivity losses. Navigate to Logs to view:

SM Session SM Authentication SM Authorization All the SM logs are saved to flash and displayed upon reboot. Figure 92 SM Logs Figure 93 SM Session log Figure 94 SM Authentication log Page 5-15 Chapter 5: Troubleshooting Figure 95 SM Authorization log Logs Page 5-16 Chapter 5: Troubleshooting 450m Reference information A.1 Specifications Please see the Specification sheets listed on the Cambium Networks website for the most up-to-date 450m Series AP specifications:

http://www.cambiumnetworks.com/resource/pmp-450m/

A.2 450m overload The 450m Series AP is designed to handle high load in terms of high throughput and high PPS. In terms of throughput, 450m is designed to achieve 3x or more throughput improvement over 450 and 450i Series products. In terms of packets per second (PPS), 450m is designed to handle up to 100k PPS. Overload occurs when the offered load exceeds the above limits. When overload occurs, 450m will start discarding packets and TCP throughput will degrade due to packet loss. The 450 family of products have a set of overload statistics that can be used to monitor overload conditions (Statistics >Overload tab). The above statistics shall be monitored over time for overload conditions over consecutive periods. Refer to Interpreting Overload statistics for description of those statistics. Its worth noting that Frame Utilization statistics (Statistics >Frame Utilization tab: Frame Utilization:

Downlink and Uplink) are not necessarily indicative of overload condition. They show how much the TDD frame is utilized. High frame utilization depends on:

Page 1 Chapter 5: Troubleshooting Logs 1. high traffic during busy periods: those statistics will be close to 100% and almost all slots will be utilized. In this case if the Overload statistics show that packets are discarded then this is an indication of overload condition. 2. high percentage of VCs with low modulation with moderate traffic. Those VCs will require more slots to service them (due to low modulation) and the frame utilization will be high. In this case the TDD frame is fully utilized but the system is at low capacity and is not in an overload condition. 450m has higher PPS than 450 and 450i and supports higher throughput through spatial multiplexing, therefore when a 450m replaces an overloaded 450 or 450i AP the 450m will not be overloaded under the same conditions but the frame utilization may still show close to 100%; this should not alarm the customer. The overload statistics shall be monitored on 450m to see if it is overloaded or not. Page 2 Chapter 5: Troubleshooting Quality of Service (QoS) Glossary Logs Term 10Base-T 169.254.0.0 169.254.1.1 255.255.0.0 802.3 Access Point Cluster Definition Technology in Ethernet communications that can deliver 10 Mb of data across 328 feet (100 meters) of CAT 5 cable. Gateway IP address default in Cambium fixed wireless broadband IP network modules. IP address default in Cambium fixed wireless broadband IP network modules. Subnet mask default in Cambium fixed wireless broadband IP network modules and in Microsoft and Apple operating systems. An IEEE standard that defines the contents of frames that are transferred through Ethernet connections. Each of these frames contains a preamble, the address to which the frame is sent, the address that sends the frame, the length of the data to expect, the data, and a checksum to validate that no contents were lost. Two to six Access Point Modules that together distribute network or Internet services to a community of subscribers. Each Access Point Module covers a 60 or 90 sector. This cluster covers as much as 360. Also known as AP cluster. Access Point Module Also known as AP. One module that distributes network or Internet services in a 60 or 90 sector. ACT/4 Address Resolution Protocol Second-from-left LED in the module. In the operating mode, this LED is lit when data activity is present on the Ethernet link. Protocol defined in RFC 826 to allow a network element to correlate a host IP address to the Ethernet address of the host. See http://www.faqs.org/rfcs/rfc826.html. Aggregate Throughput The sum of the throughputs in the uplink and the downlink. AP ARP APs MIB ASN.1 Access Point Module. One module that distributes network or Internet services to subscriber modules. Address Resolution Protocol. A protocol defined in RFC 826 to allow a network element to correlate a host IP address to the Ethernet address of the host. See http://www.faqs.org/rfcs/rfc826.html. Management Information Base file that defines objects that are specific to the Access Point Module. See also Management Information Base. Abstract Syntax Notation One language. The format of the text files that compose the Management Information Base. Page 3 Chapter 5: Troubleshooting Logs Term Attenuation BER BHM BHS Definition Reduction of signal strength caused by the travel from the transmitter to the receiver, and caused by any object between. In the absence of objects between, a signal that has a short wavelength experiences a high degree of attenuation nevertheless. Bit Error Rate. The ratio of incorrect data received to correct data received. Backhaul Timing Master (BHM)- a module that is used in a point to point link. This module controls the air protocol and configurations for the link.. Backhaul Timing Slave (BHS)- a module that is used in a point to point link. This module accepts configuration and timing from the master module. Bit Error Rate Ratio of incorrect data received to correct data received. Box MIB Bridge Buckets Burst CAT 5 Cable CIR Management Information Base file that defines module-level objects. See also Management Information Base. Network element that uses the physical address (not the logical address) of another to pass data. The bridge passes the data to either the destination address, if found in the simple routing table, or to all network segments other than the one that transmitted the data. Modules are Layer 2 bridges except that, where NAT is enabled for an SM, the SM is a Layer 3 switch. Compare to Switch and Router, and see also NAT. Theoretical data repositories that can be filled at preset rates or emptied when preset conditions are experienced, such as when data is transferred. Preset amount limit of data that may be continuously transferred. Cable that delivers Ethernet communications from module to module. Later modules auto-sense whether this cable is wired in a straight-

through or crossover scheme. Committed Information Rate. For an SM or specified group of SMs, a level of bandwidth that can be guaranteed to never fall below a specified minimum (unless oversubscribed). In the Cambium implementation, this is controlled by the Low Priority Uplink CIR, Low Priority Downlink CIR, Medium Priority Uplink CIR, Medium Priority Downlink CIR parameters, High Priority Uplink CIR, High Priority Downlink CIR parameters, Ultra High Priority Uplink CIR, and Ultra High Priority Downlink CIR parameters. Cluster Management Module Module that provides power, GPS timing, and networking connections for an AP cluster. Also known as CMM4. Page 4 Chapter 5: Troubleshooting Logs Term CMM Definition Cluster Management Module. A module that provides power, GPS timing, and networking connections for an Access Point cluster. CodePoint See DiffServ. Color Code Field Module parameter that identifies the other modules with which communication is allowed. The range of valid values is 0 to 255. Community String Field Control string that allows a network management station to access MIB information about the module. Connectorized Country Code The 450 Platform Family Connectorized Radio solution provide RF port to connect external antenna. It gives flexibility to connect to a variety of external antennas. A parameter that offers multiple fixed selections, each of which automatically implements frequency band range restrictions for the selected country. Units shipped to countries other than the United States must be configured with the corresponding Region Code and Country Code to comply with local regulatory requirements. CRCError Field This field displays how many CRC errors occurred on the Ethernet controller. Data Encryption Standard Over-the-air link option that uses secret 56-bit keys and 8 parity bits. Data Encryption Standard (DES) performs a series of bit permutations, substitutions, and recombination operations on blocks of data. Demilitarized Zone Internet Protocol area outside of a firewall. Defined in RFC 2647. See http://www.faqs.org/rfcs/rfc2647.html. DES DFS DHCP Data Encryption Standard. An over-the-air link option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. See Dynamic Frequency Selection Dynamic Host Configuration Protocol, defined in RFC 2131. Protocol that enables a device to be assigned a new IP address and TCP/IP parameters, including a default gateway, whenever the device reboots. Thus DHCP reduces configuration time, conserves IP addresses, and allows modules to be moved to a different network within the system. See http://www.faqs.org/rfcs/rfc2131.html. See also Static IP Address Assignment. Page 5 Chapter 5: Troubleshooting Logs Term DiffServ Definition Differentiated Services, consistent with RFC 2474. A byte in the type of service (TOS) field of packets whose values correlates to the channel on which the packet should be sent. The value is a numeric code point. The PMP 450 APs support four levels of QoS. The mapping of these eight priority values to data channels is determined by the number of data channels configured per SM as shown in the table below:

For example, for an AP that uses the default table shown above has configured 3 QoS levels per SM, would see codepoints 0 through 15 mapped to the Low Priority data channels, codepoint 16 would be mapped to the Medium Priority data channels, and so on. Note that CodePoints 0, 8, 16, 24, 32, 48, and 56 are predefined to the fixed values shown in Table 20 and are not user configurable. Operator cannot change any of these fixed priority values. Among the configurable parameters, the priority values (and therefore the handling of packets in the high or low priority channel) are set in the AP/BHM for all downlinks within the sector and in the SM/BHS for each uplink. Demilitarized Zone as defined in RFC 2647. An Internet Protocol area outside of a firewall. See http://www.faqs.org/rfcs/rfc2647.html. A requirement in certain countries and regions for systems to detect interference from other systems, notably radar systems, and to avoid co-channel operation with these systems. See DHCP. Hardware address that the factory assigns to the module for identification in the Data Link layer interface of the Open Systems Interconnection system. This address serves as an electronic serial number. Same as MAC Address. Electronic Serial Number. The hardware address that the factory assigns to the module for identification in the Data Link layer interface of the Open Systems Interconnection system. This address serves as an electronic serial number. Same as MAC Address. Any of several IEEE standards that define the contents of frames that are transferred from one network element to another through Ethernet connections. Page 6 DMZ Dynamic Frequency Selection Dynamic Host Configuration Protocol Electronic Serial Number ESN Ethernet Protocol Chapter 5: Troubleshooting Logs Term ETSI Fade Margin Definition European Telecommunications Standards Institute The difference between strength of the received signal and the strength that the receiver requires for maintaining a reliable link. A higher fade margin is characteristic of a more reliable link. Standard operating margin. FCC Federal Communications Commission of the U.S.A. Field-programmable Gate Array Array of logic, relational data, and wiring data that is factory programmed and can be reprogrammed. File Transfer Protocol FPGA Utility that transfers of files through TCP (Transport Control Protocol) between computing devices that do not operate on the same platform. Defined in RFC 959. See http://www.faqs.org/rfcs/rfc959.html. Field-programmable Gate Array. An array of logic, relational data, and wiring data that is factory programmed and can be reprogrammed. Free Space Path Loss Signal attenuation that is naturally caused by atmospheric conditions and by the distance between the antenna and the receiver. Fresnel Zone FTP Global Positioning System GPS GPS/3 GUI HTTP Space in which no object should exist that can attenuate, diffract, or reflect a transmitted signal before the signal reaches the target receiver. File Transfer Protocol, defined in RFC 959. Utility that transfers of files through TCP (Transport Control Protocol) between computing devices that do not operate on the same platform. See http://www.faqs.org/rfcs/rfc959.html. Network of satellites that provides absolute time to networks on earth, which use the time signal to synchronize transmission and reception cycles (to avoid interference) and to provide reference for troubleshooting activities. Global Positioning System. A network of satellites that provides absolute time to networks on earth, which use the time signal to synchronize transmission and reception cycles (to avoid interference) and to provide reference for troubleshooting activities. Third-from-left LED in the module. In the operating mode for an Access Point Module, this LED is continuously lit as the module receives sync pulse. In the operating mode for a Subscriber, this LED flashes on and off to indicate that the module is not registered. Graphical user interface. Hypertext Transfer Protocol, used to make the Internet resources available on the World Wide Web. Defined in RFC 2068. See http://www.faqs.org/rfcs/rfc2068.html. Page 7 Chapter 5: Troubleshooting Logs Term HTTPS ICMP Integrated IP IP Address IPv4 ISM L2TP over IPSec Late Collision Field Line of Sight LNK/5 Definition Hypertext Transfer Protocol Secure (HTTPS) Internet Control Message Protocols defined in RFC 792, used to identify Internet Protocol (IP)-level problems and to allow IP links to be tested. See http://www.faqs.org/rfcs/rfc792.html. The 450 Platform Family Integrated Radio solution provides integrated antenna.. Internet Protocol defined in RFC 791. The Network Layer in the TCP/IP protocol stack. This protocol is applied to addressing, routing, and delivering, and re-assembling data packets into the Data Link layer of the protocol stack. See http://www.faqs.org/rfcs/rfc791.html. 32-bit binary number that identifies a network element by both network and host. See also Subnet Mask. Traditional version of Internet Protocol, which defines 32-bit fields for data transmission. Industrial, Scientific, and Medical Equipment radio frequency band, in the 900-MHz, 2.4-GHz, and 5.8-GHz ranges. Level 2 Tunneling Protocol over IP Security. One of several virtual private network (VPN) implementation schemes. Regardless of whether Subscriber Modules have the Network Address Translation feature

(NAT) enabled, they support VPNs that are based on this protocol. This field displays how many late collisions occurred on the Ethernet controller. A normal collision occurs during the first 512 bits of the frame transmission. A collision that occurs after the first 512 bits is considered a late collision. A late collision is a serious network problem because the frame being transmitted is discarded. A late collision is most commonly caused by a mismatch between duplex configurations at the ends of a link segment. Wireless path (not simply visual path) direct from module to module. The path that results provides both ideal aim and an ideal Fresnel zone. Furthest left LED in the module. In the operating mode, this LED is continuously lit when the Ethernet link is present. In the aiming mode for a Subscriber Module, this LED is part of a bar graph that indicates the quality of the RF link. Logical Unit ID Final octet of the 4-octet IP address of the module. LOS LUID Line of sight. The wireless path (not simply visual path) direct from module to module. The path that results provides both ideal aim and an ideal Fresnel zone. Logical Unit ID. The final octet of the 4-octet IP address of the module. Page 8 Chapter 5: Troubleshooting Logs Term MAC Address Definition Media Access Control address. The hardware address that the factory assigns to the module for identification in the Data Link layer interface of the Open Systems Interconnection system. This address serves as an electronic serial number. Management Information Base Space that allows a program (agent) in the network to relay information to a network monitor about the status of defined variables (objects). Maximum Information Rate

(MIR) MIB MIR MU-MIMO NAT NEC NetBIOS The cap applied to the bandwidth of an SM or specified group of SMs. In the Cambium implementation, this is controlled by the Sustained Uplink Data Rate, Uplink Burst Allocation, Sustained Downlink Data Rate, and Downlink Burst Allocation parameters. Management Information Base. Space that allows a program (agent) in the network to relay information to a network monitor about the status of defined variables (objects). See Maximum Information Rate. Multi User- Multiple Input Multiple Output Network Address Translation defined in RFC 1631. A scheme that isolates Subscriber Modules from the Internet. See http://www.faqs.org/rfcs/rfc1631.html. National Electrical Code. The set of national wiring standards that are enforced in the U.S.A. Protocol defined in RFC 1001 and RFC 1002 to support an applications programming interface in TCP/IP. This interface allows a computer to transmit and receive data with another host computer on the network. RFC 1001 defines the concepts and methods. RFC 1002 defines the detailed specifications. See http://www.faqs.org/rfcs/rfc1001.html and http://www.faqs.org/rfcs/rfc1002.html. Network Address Translation Scheme that defines the Access Point Module as a proxy server to isolate registered Subscriber Modules from the Internet. Defined in RFC 1631. See http://www.faqs.org/rfcs/rfc1631.html. Network Management Station See NMS. NMS Network Management Station. A monitor device that uses Simple Network Management Protocol (SNMP) to control, gather, and report information about predefined network variables (objects). See also Simple Network Management Protocol. Page 9 Chapter 5: Troubleshooting Logs Term Default Mode Definition Device that enables the operator to regain control of a module that has been locked by the No Remote Access feature, the 802.3 Link Disable feature, or a password or IP address that cannot be recalled. This device can be either fabricated on site or ordered. PMP See Point-to-Multipoint Protocol. Point-to-Multipoint Protocol Defined in RFC 2178, which specifies that data that originates from a central network element can be received by all other network elements, but data that originates from a non-central network element can be received by only the central network element. See http://www.faqs.org/rfcs/rfc2178.html. Also referenced as PMP. PPPoE Point to Point Protocol over Ethernet. Supported on SMs for PPS PPTP Protective Earth Proxy Server operators who use PPPoE in other parts of their network operators who want to deploy PPPoE to realize per-subscriber authentication, metrics, and usage control. Packet Per Second Point to Point Tunneling Protocol. One of several virtual private network implementations. Regardless of whether the Network Address Translation (NAT) feature enabled, Subscriber Modules support VPNs that are based on this protocol. Connection to earth (which has a charge of 0 volts). Also known as ground. Network computer that isolates another from the Internet. The proxy server communicates for the other computer, and sends replies to only the appropriate computer, which has an IP address that is not unique or not registered. PTP A Point-to-Point connection refers to a communications connection between two nodes or endpoints. Radio Signal Strength Indicator Relative measure of the strength of a received signal. An acceptable link displays a Radio Signal Strength Indicator (RSSI) value of greater than 700. Reflection Change of direction and reduction of amplitude of a signal that encounters an object larger than the wavelength. Reflection may cause an additional copy of the wavelength to arrive after the original, unobstructed wavelength arrives. This causes partial cancellation of the signal and may render the link unacceptable. However, in some instances where the direct signal cannot be received, the reflected copy may be received and render an otherwise unacceptable link acceptable. Page 10 Chapter 5: Troubleshooting Logs Term Region Code RF RJ-12 RJ-45 Router RSSI Definition A parameter that offers multiple fixed selections, each of which automatically implements frequency band range restrictions for the selected region. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. Radio frequency. How many times each second a cycle in the antenna occurs, from positive to negative and back to positive amplitude. Standard cable that is typically used for telephone line or modem connection. Standard cable that is typically used for Ethernet connection. This cable may be wired as straight-through or as crossover. Later modules auto-

sense whether the cable is straight-through or crossover. Network element that uses the logical (IP) address of another to pass data to only the intended recipient. Compare to Switch and Bridge. Radio Signal Strength Indicator. A relative measure of the strength of a received signal. An acceptable link displays an RSSI value of greater than 700. Self-interference Interference with a module from another module in the same network. SFP Small Form-factor Pluggable Simple Network Management Protocol Standard that is used for communications between a program (agent) in the network and a network management station (monitor). Defined in RFC 1157. See http://www.faqs.org/rfcs/rfc1157.html. SM SNMP SNMPv3 SNMP Trap Spatial Frequency Customer premises equipment (CPE) device that extends network or Internet services by communication with an Access Point Module or an Access Point cluster. See Simple Network Management Protocol, defined in RFC 1157. SNMP version 3 Capture of information that informs the network monitor through Simple Network Management Protocol of a monitored occurrence in the module. Spatial Frequency is associated with an LUID or SM registered with an AP and it is visible on both AP and SM GUIs. It is grouped into bins where each bin includes 32 consecutive spatial frequency values. Page 11 Chapter 5: Troubleshooting Logs Term Static IP Address Assignment Subnet Mask Subscriber Module Definition Assignment of Internet Protocol address that can be changed only manually. Thus, static IP address assignment requires more configuration time and consumes more of the available IP addresses than DHCP address assignment does. RFC 2050 provides guidelines for the static allocation of IP addresses. See http://www.faqs.org/rfcs/rfc2050.html. See also DHCP. 32-bit binary number that filters an IP address to reveal what part identifies the network and what part identifies the host. The number of subnet mask bits that are set to 1 indicates how many leading bits of the IP address identify the network. The number of subnet mask bits that are set 0 indicate how many trailing bits of the IP address identify the host. Customer premises equipment (CPE) device that extends network or Internet services by communication with an Access Point Module or an Access Point cluster. Sustained Data Rate Preset rate limit of data transfer. Switch Sync TCP TDD telnet Network element that uses the port that is associated with the physical address of another to pass data to only the intended recipient. Compare to Bridge and Router. GPS (Global Positioning System) absolute time, which is passed from one module to another. Sync enables timing that prevents modules from transmitting or receiving interference. Sync also provides correlative time stamps for troubleshooting efforts. Alternatively known as Transmission Control Protocol or Transport Control Protocol. The Transport Layer in the TCP/IP protocol stack. This protocol is applied to assure that data packets arrive at the target network element and to control the flow of data through the Internet. Defined in RFC 793. See http://www.faqs.org/rfcs/rfc793.html. Time Division Duplexing. Synchronized data transmission with some time slots allocated to devices transmitting on the uplink and some to the device transmitting on the downlink. Utility that allows a client computer to update a server. A firewall can prevent the use of the telnet utility to breach the security of the server. See http://www.faqs.org/rfcs/rfc818.html, http://www.faqs.org/rfcs/rfc854.html and http://www.faqs.org/rfcs/rfc855.html. Tokens Theoretical amounts of data. See also Buckets. TxUnderrun Field This field displays how many transmission-underrun errors occurred on the Ethernet controller. Page 12 Chapter 5: Troubleshooting Logs Term UDP udp U-NII VID VLAN VPN Definition User Datagram Protocol. A set of Network, Transport, and Session Layer protocols that RFC 768 defines. These protocols include checksum and address information but does not retransmit data or process any errors. See http://www.faqs.org/rfcs/rfc768.html. User-defined type of port. Unlicensed National Information Infrastructure radio frequency band, in the 5.1GHz through 5.8 GHz ranges. VLAN identifier. See also VLAN. Virtual local area network. An association of devices through software that contains broadcast traffic, as routers would, but in the switch-level protocol. Virtual private network for communication over a public network. One typical use is to connect remote employees, who are at home or in a different city, to their corporate network over the Internet. Any of several VPN implementation schemes is possible. SMs support L2TP over IPSec (Level 2 Tunneling Protocol over IP Security) VPNs and PPTP (Point to Point Tunneling Protocol) VPNs, regardless of whether the Network Address Translation (NAT) feature enabled. Page 13

 

 

Chapter 2: Tools Using the Alignment Tool Using the Alignment Tool The SMs or BHSs Alignment Tool may be used to maximize Receive Power Level, Signal Strength Ratio and Signal to Noise Ratio to ensure a stable link. The Tool provides color coded readings to facilitate in judging link quality. Figure 69 Alignment Tool tab of SM Receive Power Level > -70 dBm Figure 70 Alignment Tool tab of SM Receive Power Level between -70 to -80 dBm Figure 71 Alignment Tool tab of SM Receive Power Level < -80 dBm Page 2-331 Chapter 2: Tools Using the Alignment Tool Aiming page and Diagnostic LED SM/BHS The SMs/BHSs Alignment Tool (located in GUI Tools -> Aiming) may be used to configure the SMs/BHSs LED panel to indicate received signal strength and to display decoded beacon information/power levels. The SM/BHS LEDs provide different status based on the mode of the SM/BHS. A SM/BHS in operating mode will register and pass traffic normally. A SM/BHS in aiming mode will not register or pass traffic, but will display (via LED panel) the strength of received radio signals (based on radio channel selected via Tools ->Aiming). See SM/BHS LEDs in Planning and Installation Guide. Note For accurate power level readings to be displayed, traffic must be present on the radio link. Refer SM/BHS LED description in Planning and Installation Guide for SM/BHS LED details. Aiming page of SM The Aiming page is similar to Spectrum Analyzer where it scans the spectrum but it does not establish any session with any APs. It has two modes Single Frequency Only and Normal Frequency Scan List. The Aiming page of SM is explained in Table 102. Page 2-332 Chapter 2: Tools Table 102 Aiming page attributes SM Using the Alignment Tool Attribute Meaning Aiming Mode Single Frequency Only: scans only selected single frequency. Normal Frequency Scan List: scans: scans all frequency of scan list. Single Frequency Select a particular frequency from drop-down menu for scanning. Scan Radio Frequency Only Mode Enabled: the radio is configured to aiming or alignment mode, wherein the LED panel displays an indication of receive power level. See SM/BHS LED description in Planning and Installation Guide. Disabled: the radio is configured to operating mode, wherein the SM registers and passes traffic normally. Aiming Results The Aiming Results are displayed in two sections Current entry and Other entries. Frequency: this field indicates the frequency of the AP which is transmitting the beacon information. Page 2-333 Chapter 2: Tools Using the Alignment Tool Power: This field indicates the current receive power level (vertical channel) for the frequency configured in parameter Radio Frequency. Users: This field indicates the number of SMs currently registered to the AP which is transmitting the beacon information. ESN: This field indicates the MAC, or hardware address of the AP/BHM which is transmitting the beacon information. Color Code: This field displays a value from 0 to 254 indicating the APs configured color code. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Multipoint or Backhaul: this field indicates type of configuration - point-

Multipoint (PMP) or Backhaul (PTP). Page 2-334 Chapter 2: Tools Aiming page of BHS The Alignment page of BHS is explained in Table 103. Table 103 Aiming page attributes - BHS Using the Alignment Tool Attribute Refer Meaning Refer Table 102 Aiming page attributes SM for attribute details. Note The Alignment Tone cable for a 450i Series uses an RJ-45 to headset cable whereas the 450 Series alignment tone cable uses an RJ-12 to headset cable. Page 2-335 Chapter 2: Tools Alignment Tone Using the Alignment Tool For coarse alignment of the SM/BHS, use the Alignment Tool located at Tools -> Alignment Tool. Optionally, connect a headset alignment tone kit to the AUX/SYNC port of the SM/BHS and listen to the alignment tone, which indicates greater SM/BHS receive signal power by pitch. By adjusting the SMs/BHSs position until the highest frequency pitch is obtained operators and installers can be confident that the SM/BHS is properly positioned. For information on device GUI tools available for alignment, see sections Aiming page and Diagnostic LED SM/BHS on page 2-332, Using the Link Capacity Test tool on page 2-338 and Using AP Evaluation tool on page 2-347. Figure 72 PMP/PTP 450i Series link alignment tone 450i Alignment tone adapter Headphones Alignment Tool Headset and alignment tone adapters can be ordered from Cambium and Best-Tronics (http://btpa.com/Cambium-Products/) respectively using the following part numbers:

Table 104 Alignment Tool Headsets and Alignment tone adapter third party product details Reference Product description ACATHS-01A Alignment tool headset for the PMP/PTP 450 and 450i Series products Page 2-336 Chapter 2: Tools Using the Alignment Tool BT-1277 BT-0674 Headset alignment cable (RJ-45) for the PMP/PTP 450i Series products Headset alignment cable (RJ-12) for the PMP/PTP 450 Series products. Page 2-337 Chapter 2: Tools Using the Link Capacity Test tool Using the Link Capacity Test tool The Link Capacity Test tab allows you to measure the throughput and efficiency of the RF link between two modules. Many factors, including packet length, affect throughput. The Link Capacity Test tool has following modes:

Link Test with Multiple VCs: Tests radio-to-radio communication across selected or all registered VCs, but does not bridge traffic (PMP 450m Series AP only). Link Test without Bridging: Tests radio-to-radio communication, but does not bridge traffic. Link Test with Bridging: Bridges traffic to simulated Ethernet ports, providing a status of the bridged link. Link Test with Bridging and MIR: Bridges the traffic during test and also adheres to any MIR

(Maximum Information Rate) settings for the link. Extrapolated Link Test: Estimates the link capacity by sending few packets and measuring link quality. The Link Capacity Test tab contains the settable parameter Packet Length with a range of 64 to 1714 bytes. This allows you to compare throughput levels that result from various packet sizes. The Current Results Status also displayed date and time of last performed Link Capacity Test. If there is any change in time zone, the date and time will be adjusted accordingly. Note The Extrapolated Link Test can be run by Read-Only login also. Performing Link Test The link test is a tool that allows the user to test the performance of the RF link. Packets are added to one or more queues in the AP in order to fill the frame. Throughput and efficiency are then calculated during the test. The 450 and 450i APs offer link test options to one SM at a time. The 450m AP offers the option of a link test to multiple VCs at the same time. This allows the user to test throughput in MU-

MIMO mode, in which multiple SMs are served at the same time. This new link test can be found under Tools > Link Capacity Test Page 2-338 Chapter 2: Tools Link Test with Multiple LUIDs Using the Link Capacity Test tool Note The Link Test with Multiple LUIDs Link Capacity Test is supported for PMP 450m Series AP only. Figure 73 Link Capacity Test PMP 450m Series AP Procedure 24 Performing a Link Capacity Test - Link Test with Multiple LUIDs Link Test Configurations parameters 1 2 Access the Link Capacity Test tab in the Tools web page of the module. Set Link with Multiple Data Channels attribute to Link Test Low Priority Data Channels, Link Test Low and Medium Priority Data Channels, Link Test Low, Medium and High Priority Data Channels, or Link Test All Data Channels. 3 Set the MU-MIMO attribute to Enabled or Disabled. Note: The MU-MIMO feature is enabled on the Low Priority Data Channel only 4 5 Set the Ignore Configured CIR attribute to Enabled or Disabled. Set the User Traffic During Link Test attribute to Block User Traffic or Allow User Traffic. Link Test Settings parameters 6 7 8 9 Enter LUID List (applicable for PMP 450m AP only) The Current Subscriber Module and LUID List are valid only when selecting Link Test with Multiple LUIDs. Current Subscriber Module: select the LUID to perform the link test with LUID list: select a list or range of LUIDs to include in the link test with multiple LUIDs If left blank, all LUIDs will be included in the link test Type into the Duration field how long (in seconds) the RF link must be tested. Select the Direction attribute to Bi-directional, Uplink Only, or Downlink Only. Type into the Number of Packets field a value of 0 to flood the link for the duration of the test. 10 Type into the Packet Length field a value of 1714 to send 1714-byte packets during the test. 11 Click the Start Test button. Page 2-339 Chapter 2: Tools Figure 74 Link Test with Multiple LUIDs Using the Link Capacity Test tool Link Test without Bridging, Link Test with Bridging or Link Test with Bridging and MIR Figure 75 Link Test without Bridging Figure 76 Link Test with Bridging and MIR Page 2-340 Chapter 2: Tools Using the Link Capacity Test tool Refer Link Test with Multiple on page 2-339 for Link Test procedure. Figure 77 Link Test without Bridging (1518-byte packet length) Page 2-341 Chapter 2: Tools Performing Extrapolated Link Test Using the Link Capacity Test tool The Extrapolated Link Test estimates the link capacity by sending few packets and measuring link quality. Once the test is initiated, the radio starts session at the lower modulation, 1X, as traffic is passed successfully across the link, the radio decides to try the next modulation, 2X. This process repeats until it finds best throughput to estimate capacity of link. The procedure for performing Extrapolated Link Test is as follows:

Procedure 25 Performing an Extrapolated Link Test 1 Access the Link Capacity Test tab in the Tools web page of the module. 2 Select Link Test Mode Extrapolated Link Test 3 Click the Start Test button. 4 In the Current Results Status block of this tab, view the results of the test. Figure 78 Extrapolated Link Test results Page 2-342 Chapter 2: Tools Link Capacity Test page of AP The Link Capacity Test page of AP is explained in Table 105. Table 105 Link Capacity Test page attributes 450m AP Using the Link Capacity Test tool Attribute Meaning Link Test Mode Signal to Noise Ratio Calculation during Link Test Link Test with Multiple LUIDs (PMP 450m Series AP only) Link Test without Bridging Select Link Test Mode from drop-down menu:

Extrapolated Link Test Link Test with Bridging and MIR Link Test with Bridging Enable this attribute to display Signal-to-Noise information for the downlink and uplink when running the link test. Page 2-343 Chapter 2: Tools SM Link Test Mode Restriction Link Test with All Available Data Channels MU-MIMO Display results for untested Data Channels Ignore Configured CIR Using the Link Capacity Test tool Enable this parameter to restrict SM link test mode. This parameter is used to enable or disable usage of either all available data channels or low priority data channel only during the link test. This parameter determines whether the DL flood test packets use MU-MIMO grouping or not. Note: This field is applicable only when the Link Test Mode field is set to Link Test with Multiple VCs option. Note: This field is applicable for PMP 450m APs only. If Link test with multiple VCs is run and a subset of registered VCs enters into the VC List field, then enabling this field produces a table that displays results for VCs with traffic which are in session; but not tested as part of the link test. Note: This field is applicable for PMP 450m flood tests only. Enable this parameter to schedule flood data regardless of the CIR configuration for each SM. For system release 16.1 and beyond, the exact impact of this setting depends on which scheduler "mode" has been configured by the operator on the AP's QoS page. Enabled: Run Link Test with Multiple LUID's using Legacy scheduler, ignoring configured CIR's. Legacy scheduler is used here regardless of which scheduling mode has been configured. Disabled: If Legacy scheduler is enabled, test with legacy scheduler, using configured CIR's. If Proportional scheduler is enabled, test with proportional scheduler. Current Subscriber Module The SM with which the Link Capacity Test is run. This field is only applicable for AP (not SM page). LUID List Duration Direction This field is displayed for PMP 450m Series AP. It is only applicable for Link Test with Multiple LUIDs Test mode. Enter LUID List (e.g. 18 or above for low priority LUIDs and 255 or above for high priority LUIDs or 0 for all registered LUIDs) which needs to be used for link test traffic. This field allows operators to configure a specified time for which the spectrum is scanned. If the entire spectrum is scanned prior to the end of the configured duration, the analyzer will restart at the beginning of the spectrum. Configure the direction of the link test. Specify Downlink or Uplink to run the test only in the corresponding direction only. Specific Bi-Directional to run the test in both directions. Page 2-344 Chapter 2: Tools Using the Link Capacity Test tool Number of Packets The total number of packets to be sent during the Link Capacity Test. When Link Test Mode is set to Link Test Without Bridging this field is not configurable. Packet Length The size of the packets in Bytes to send during the Link Capacity Test Page 2-345 Chapter 2: Tools Link Capacity Test page of BHM/BHS/SM The Link Capacity Test page of BHM/BHS is explained in Table 106. Table 106 Link Capacity Test page attributes BHM/BHS Using the Link Capacity Test tool Attribute Link Test Mode Signal to Noise Ratio Calculation during Link Test Link Test with All Available Data Channels Duration Direction Number of Packets Packet Length Meaning See Table 105 on page 2-343 See Table 105 on page 2-343 See Table 105 on page 2-343 See Table 105 on page 2-343 See Table 105 on page 2-343 See Table 105 on page 2-343 See Table 105 on page 2-343 Page 2-346 Chapter 2: Tools Using AP Evaluation tool Using AP Evaluation tool The AP Evaluation tab on Tools web page of the SM provides information about the AP that the SM sees. Note The data for this page may be suppressed by the SM Display of AP Evaluation Data setting in the Configuration > Security tab of the AP. The AP Eval results can be accessed via SNMP and config file. AP Evaluation page The AP Evaluation page of AP is explained in Table 107. Table 107 AP Evaluation tab attributes - AP Page 2-347 Chapter 2: Tools Attribute Index Using AP Evaluation tool Meaning This field displays the index value that the system assigns (for only this page) to the AP where this SM is registered. Frequency This field displays the frequency that the AP transmits. Channel Bandwidth The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the AP and the SM. Cyclic Prefix ESN OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol to allow multi-

pathing to settle before receiving the desired data. A 1/16 cyclic prefixes mean that for every 16 bits of throughput data transmitted, an additional bit is used. The Cyclic Prefix 1/16 only can be selected at this time. This field displays the MAC address (electronic serial number) of the AP. For operator convenience during SM aiming, this tab retains each detected ESN for up to 15 minutes. If the broadcast frequency of a detected AP changes during a 15-minute interval in the aiming operation, then a multiple instance of the same ESN is possible in the list. Eventually, the earlier instance expires and disappears and the later instance remains to the end of its interval, but you can ignore the early instance(s) whenever two or more are present. Region Power Level This field displays the APs configured Country Code setting. This field displays the SMs combined received power level from the APs transmission. Beacon Count A count of the beacons seen in a given time period. FECEn Type Age This field contains the SNMP value from the AP that indicates whether the Forward Error Correction feature is enabled. 0: FEC is disabled 1: FEC is enabled Multipoint indicates that the listing is for an AP. This is a counter for the number of minutes that the AP has been inactive. At 15 minutes of inactivity for the AP, this field is removed from the AP Evaluation tab in the SM. Page 2-348 Chapter 2: Tools Using AP Evaluation tool Lockout RegFail Range This field displays how many times the SM has been temporarily locked out of making registration attempts. This field displays how many registration attempts by this SM failed. This field displays the distance in feet for this link. To derive the distance in meters, multiply the value of this parameter by 0.3048. MaxRange This field indicates the configured value for the APs Max Range parameter. TxBER Ebcast Session Count NoLUIDs OutOfRange AuthFail EncryptFail Rescan Req A 1 in this field indicates the AP is sending Radio BER. A 1 in this field indicates the AP or BHM is encrypting broadcast packets. A 0 indicates it is not. This field displays how many sessions the SM (or BHS) has had with the AP

(or BHM). Typically, this is the sum of Reg Count and Re-Reg Count. However, the result of internal calculation may display here as a value that slightly differs from the sum. In the case of a multipoint link, if the number of sessions is significantly greater than the number for other SMs, then this may indicate a link problem or an interference problem. This field indicates how many times the AP has needed to reject a registration request from a SM because its capacity to make LUID assignments is full. This then locks the SM out of making any valid attempt for the next 15 minutes. It is extremely unlikely that a non-zero number would be displayed here. This field indicates how many times the AP has rejected a registration request from a SM because the SM is a further distance away than the range that is currently configured in the AP. This then locks the SM out of making any valid attempt for the next 15 minutes. This field displays how many times authentication attempts from this SM have failed in the AP. This field displays how many times an encryption mismatch has occurred between the SM and the AP. This field displays how many times a re-range request has occurred for the BHM that is being evaluated in the AP Eval page of a BHS. SMLimitReached This field displays 0 if additional SMs may be registered to the AP. If a 1 is displayed, the AP will not accept additional SM registrations. NoVCs This counter is incremented when the SM is registering to an AP which determines that no VC resources are available for allocation. This could be a primary data channel (a low priority data channel) or one of the other possible data channel priorities (a Medium priority data channel, or High priority data channel, or Ultra High priority data channel) Page 2-349 Chapter 2: Tools VCRsvFail VCActFail AP Gain RcvT Sector ID Color Code Using AP Evaluation tool This counter is incremented when the SM is registering to an AP which has a VC resource available for allocation but cannot reserve the resource for allocation. This counter is incremented when the SM is registering to an AP which has a VC resource available for allocation and has reserved the VC, but cannot activate the resource for allocation. This field displays the total external gain (antenna) used by the AP. This field displays the APs configured receive target for receiving SM transmissions (this field affects automatic SM power adjust). This field displays the value of the Sector ID field that is provisioned for the AP. This field displays a value from 0 to 254 indicating the APs configured color code. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). BeaconVersion This field indicates that the beacon is OFDM (value of 1). Sector User Count This field displays how many SMs are registered on the AP. NumULHalfSlots This is the number of uplink slots in the frame for this AP. NumDLHalfSlots This is the number of downlink slots in the frame for this. NumULContSlots This field displays how many Contention Slots are being used in the uplink portion of the frame. WhiteSched Flag to display if schedule whitening is supported via FPGA ICC SM PPPoE This field lists the SMs that have registered to the AP with their Installation Color Code (ICC), Primary CC, Secondary CC or Tertiary CC. This filed provides information to the user whether the SM is supporting PPPoE or not. Frame Period This field displays the configured Frame Period of the radio. Last Registered Primary Color Code AP MAC Address This field displays the last registered APs MAC address. Frequency This field displays the last registered APs frequency. Channel Bandwidth This field displays the last registered APs channel bandwidth. Page 2-350 Chapter 2: Tools Using AP Evaluation tool Color Code Air Delay This field displays the last registered APs color code. This field displays the last registered APs air delay. Receive Power This field displays the last registered APs receive power. Scan Statitistics Scan Cycle Count Beacon Statistics Unsupported Feature Beacon Received The file displays the number of scan cycles. This increments after the SM completes scanning every configured frequency and channel bandwidth. Count of beacons that the SM has received that is from a beacon that it does not support, which will prevent registration. If encounter this, upgrade your SM to the latest supported software version. Unknown Feature Beacon Received Count of beacons that the SM has received that is from a beacon that is running a feature that is unknown, which will prevent registration. If this stat is encountered, upgrade your SM to the latest supported software version. Old Version Beacon Received Count of the beacons where the version in the beacon mismatched and prevented registration. Wrong Frequency Beacon Received Count of beacons that was reported on a different frequency than was received. Page 2-351 Chapter 2: Tools Using BHM Evaluation tool Using BHM Evaluation tool The BHM Evaluation tab on Tools web page of the BHS provides information about the BHM that the BHS sees. BHM Evaluation page of BHS The BHM Evaluation page of BHS is explained in Table 108. Table 108 BHM Evaluation tab attributes - BHS Attribute Index Meaning This field displays the index value that the system assigns (for only this page) to the BHM where this BHS is registered. Frequency This field displays the frequency that the BHM transmits. Channel Bandwidth The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the BHM and the BHS. Cyclic Prefix OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol to allow multi-

pathing to settle before receiving the desired data. A 1/16 cyclic prefixes mean that for every 16 bits of throughput data transmitted, an additional bit is used. Page 2-352 Chapter 2: Tools Using BHM Evaluation tool ESN Region Power Level This field displays the MAC address (electronic serial number) of the BHM. For operator convenience during BHS aiming, this tab retains each detected ESN for up to 15 minutes. If the broadcast frequency of a detected BHM changes during a 15-minute interval in the aiming operation, then a multiple instance of the same ESN is possible in the list. Eventually, the earlier instance expires and disappears and the later instance remains to the end of its interval, but you can ignore the early instance(s) whenever two or more are present. This field displays the BHMs configured Country Code setting. This field displays the BHSs combined received power level from the BHMs transmission. Beacon Count A count of the beacons seen in a given time period. FECEn Type Age Lockout RegFail Range This field contains the SNMP value from the BHM that indicates whether the Forward Error Correction feature is enabled. 0: FEC is disabled 1: FEC is enabled Multipoint indicates that the listing is for a BHM. This is a counter for the number of minutes that the BHM has been inactive. At 15 minutes of inactivity for the BHS, this field is removed from the BHM Evaluation tab in the BHS. This field displays how many times the BHS has been temporarily locked out of making registration attempts. This field displays how many registration attempts by this BHS failed. This field displays the distance in feet for this link. To derive the distance in meters, multiply the value of this parameter by 0.3048. MaxRange This field indicates the configured value for the APs Max Range parameter. TxBER Ebcast Session Count A 1 in this field indicates the BHM is sending Radio BER. A 1 in this field indicates the BHM is encrypting broadcast packets. A 0 indicates it is not. This field displays how many sessions the BHS has had with the BHM. Typically, this is the sum of Reg Count and Re-Reg Count. However, the result of internal calculation may display here as a value that slightly differs from the sum. In the case of a multipoint link, if the number of sessions is significantly greater than the number for other BHSs, then this may indicate a link problem or an interference problem. Page 2-353 Chapter 2: Tools NoLUIDs OutOfRange AuthFail EncryptFail Rescan Req Using BHM Evaluation tool This field indicates how many times the BHM has needed to reject a registration request from a BHS because its capacity to make LUID assignments is full. This then locks the BHS out of making any valid attempt for the next 15 minutes. It is extremely unlikely that a non-zero number would be displayed here. This field indicates how many times the BHM has rejected a registration request from a BHS because the BHS is a further distance away than the range that is currently configured in the BHM. This then locks the BHS out of making any valid attempt for the next 15 minutes. This field displays how many times authentication attempts from this SM have failed in the BHM. This field displays how many times an encryption mismatch has occurred between the BHS and the BHM. This field displays how many times a re-range request has occurred for the BHM that is being evaluated in the BHM Eval page of a BHM. SMLimitReached This field displays 0 if additional BHSs may be registered to the BHM. If a 1 is displayed, the BHM will not accept additional BHS registrations. NoVCs VCRsvFail VCActFail AP Gain RcvT Sector ID Color Code This counter is incremented when the BHS is registering to a BHM which determines that no data channel resources are available for allocation. This could be a primary data channel (a low priority data channel) or one of the other possible data channel priorities (a Medium priority data channel, or High priority data channel, or Ultra High priority data channel) This counter is incremented when the BHS is registering to a BHM which has a VC resource available for allocation but cannot reserve the resource for allocation. This counter is incremented when the BHS is registering to a BHM which has a VC resource available for allocation and has reserved the VC, but cannot activate the resource for allocation. This field displays the total external gain (antenna) used by the BHM. This field displays the APs configured receive target for receiving BHS transmissions (this field affects automatic BHS power adjust). This field displays the value of the Sector ID field that is provisioned for the BHM. This field displays a value from 0 to 254 indicating the BHMs configured color code. For registration to occur, the color code of the BHS and the BHM must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Page 2-354 Chapter 2: Tools Using BHM Evaluation tool Color code allows you to force a BHS to register to only a specific BHM, even where the BHS can communicate with multiple BHMs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). BeaconVersion This field indicates that the beacon is OFDM (value of 1). Sector User Count This field displays how many BHSs are registered on the BHM. NumULHalfSlots This is the number of uplink slots in the frame for this BHM. NumDLHalfSlots This is the number of downlink slots in the frame for this. NumULContSlots This field displays how many Contention Slots are being used in the uplink portion of the frame. WhiteSched Flag to display if schedule whitening is supported via FPGA ICC SM PPPoE This field lists the BHSs that have registered to the BHM with their Installation Color Code (ICC), Primary CC, Secondary CC or Tertiary CC. This filed provides information to the user whether the BHS is supporting PPPoE or not. Frame Period This field displays the configured Frame Period of the radio. Page 2-355 Chapter 2: Tools Using the OFDM Frame Calculator tool Using the OFDM Frame Calculator tool The first step to avoid interference in wireless systems is to set all APs/BHMs to receive timing from a synchronization source (Cluster Management Module, or Universal Global Positioning System). This ensures that the modules are in sync and start transmitting at the same time each frame. The second step to avoid interference is to configure parameters on all APs/BHMs of the same frequency band in proximity such that they have compatible transmit/receive ratios (all stop transmitting each frame before any start receiving). This avoids the problem of one AP/BHM attempting to receive the signal from a distant SM/BHS while a nearby AP transmits, which could overpower that signal. The following parameters on the AP determine the transmit/receive ratio:

Max Range Frame Period Downlink Data percentage

(reserved) Contention Slots If OFDM (PMP 430, PMP 450, PTP 230) and FSK (PMP 1x0) APs/BHMs of the same frequency band are in proximity, or if APs/BHMs set to different parameters (differing in their Max Range values, for example), then operator must use the Frame Calculator to identify compatible settings. The frame calculator is available on the Frame Calculator tab of the Tools web page. To use the Frame Calculator, type various configurable parameter values into the calculator for each proximal AP and then record the resulting AP/BHM Receive Start value. Next vary the Downlink Data percentage in each calculation and iterate until the calculated AP/BHM Receive Start for all collocated AP/BHMs where the transmit end does not come before the receive start. The calculator does not use values in the module or populate its parameters. It is merely a convenience application that runs on a module. For this reason, you can use any FSK module (AP, SM, BHM, BHS) to perform FSK frame calculations for setting the parameters on an FSK AP and any OFDM module (AP, SM, BHM, BHS) to perform OFDM frame calculations for setting the parameters on an OFDM AP/BHM. For more information on PMP/PTP 450 Platform co-location, see https://support.cambiumnetworks.com/files/colocationtool/ The co-location is also supported for 900 MHz PMP 450i APs (OFDM) and PMP 100 APs (FSK). Please refer Co-location of PMP 450 and PMP 100 systems in the 900 MHz band and migration recommendations document for details. Caution APs/BHMs that have slightly mismatched transmit-to-receive ratios and low levels of data traffic may see little effect on throughput. A system that was not tuned for co-

location may work fine at low traffic levels, but encounter problems at higher traffic levels. The conservative practice is to tune for co-location before traffic ultimately increases. This prevents problems that occur as sectors are built. The OFDM Frame Calculator page is explained in Table 109. Page 2-356 Chapter 2: Tools Table 109 OFDM Frame Calculator page attributes Using the OFDM Frame Calculator tool Attribute Link Mode Platform Type AP/BHM Platform Type SM/BHS Meaning For AP to SM frame calculations, select Multipoint Link For BHM to BHS frame calculations, select Point-To-Point Link Use the drop-down list to select the hardware series (board type) of the AP/BHM. Use the drop-down list to select the hardware series (board type) of the SM/BHS. Channel Bandwidth Set this to the channel bandwidth used in the AP/BHM. Cyclic Prefix Set this to the cyclic prefix used in the AP/BHM. Max Range Set to the same value as the Max Range parameter is set in the AP(s) or BHM(s). Page 2-357 Chapter 2: Tools Frame Period Downlink Data Contention Slots Using the OFDM Frame Calculator tool Set to the same value as the Frame Period parameter is set in the AP(s) or BHM(s). Initially set this parameter to the same value that the AP/BHM has for its Downlink Data parameter (percentage). Then, use the Frame Calculator tool procedure as described in Using the Frame Calculator on page 2-359, you will vary the value in this parameter to find the proper value to write into the Downlink Data parameter of all APs or BHMs in the cluster. PMP 450 Platform Family APs or BHMs offer a range of 15% to 85% and default to 75%. The value that you set in this parameter has the following interaction with the value of the Max Range parameter (above):

The default Max Range value is 5 miles and, at that distance, the maximum Downlink Data value (85% in PMP 450 Platform) is functional. This field indicates the number of (reserved) Contention Slots configured by the operator. Set this parameter to the value of the Contention Slot parameter is set in the APs or BHMs. SM/BHS One Way Air Delay This field displays the time in ns (nano seconds), that a SM/BHS is away from the AP/BHM. The Calculated Frame Results display several items of interest:

Table 110 OFDM Calculated Frame Results attributes Attribute Modulation Meaning The type of radio modulation used in the calculation (OFDM for 450 Platform Family) Total Frame Bits The total number of bits used in the calculated frames Data Slots (Down/Up) This field is based on the Downlink Data setting. For example, a result within the typical range for a Downlink Data setting of 75% is 61/21, meaning 61 data slots down and 21 data slots up. Contention Slots This field indicates the number of (reserved) Contention Slots configured by the operator. Air Delay for Max Range This is the roundtrip air delay in bit times for the Max Range value set in the calculator Approximate distance for Max Range AP Transmit End The Max Range value used for frame calculation In bit times, this is the frame position at which the AP/BHM ceases transmission. AP Receive Start In bit times, this is the frame position at which the AP/BHM is ready to receive transmission from the SM/BHS. Page 2-358 Chapter 2: Tools Using the OFDM Frame Calculator tool AP Receive End SM Receive End In bit times, this is the frame position at which the AP/BHM will cease receiving transmission from the SM/BHS. In bit times, this is the frame position at which the SM/BHS will cease receiving transmission from the AP/BHM. SM Transmit Start In bit times, this is the frame position at which the SM/BHS starts the transmission. SM One Way Air Delay SM Approximate distance This filed displays the time in ns, that SM/BHS is away from the AP/BHM. This field displays an approximate distance in miles (feet) that the SM/BHS is away from the AP/BHM. To use the Frame Calculator to ensure that all APs or BHMs are configured to transmit and receive at the same time, follow the procedure below:

Procedure 26 Using the Frame Calculator 1 2 3 Populate the OFDM Frame Calculator parameters with appropriate values as described above. Click the Calculate button. Scroll down the tab to the Calculated Frame Results section 4 Record the value of the AP Receive Start field 5 Enter a parameter set from another AP in the system for example, an AP in the same cluster that has a higher Max Range value configured. 6 Click the Calculate button. 7 8 Scroll down the tab to the Calculated Frame Results section If the recorded values of the AP Receive Start fields are within 150 bit times of each other, skip to step 10. If the recorded values of the AP Receive Start fields are not within 150 bit times of each other, modify the Downlink Data parameter until the calculated results for AP Receive Start are within 300 bit time of each other, if possible, 150 bit time. 10 Access the Radio tab in the Configuration web page of each AP in the cluster and change its Downlink Data parameter (percentage) to the last value that was used in the Frame Calculator. Page 2-359 Chapter 2: Tools Using the Subscriber Configuration tool Using the Subscriber Configuration tool The Subscriber Configuration page in the Tools page of the AP displays:

The current values whose control may be subject to the setting in the Configuration Source parameter. An indicator of the source for each value. This page may be referenced for information on how the link is behaving based on where the SM is retrieving certain QoS and VLAN parameters. Figure 79 SM Configuration page of AP The AP displays one of the following for the configuration source:

(SM) QoS/VLAN parameters are derived from the SMs settings

(APCAP) QoS/VLAN parameters are derived from the APs settings, including any keyed capping

(for radios capped at 4 Mbps, 10 Mbps, or 20 Mbps)

(D) QoS/VLAN parameters are retrieved from the device, due to failed retrieval from the AAA or WM server.

(AAA) QoS/VLAN parameters are retrieved from the RADIUS server

(BAM) QoS/VLAN parameters are retrieved from a WM BAM server Page 2-360 Chapter 2: Tools Using the Link Status tool Using the Link Status tool The Link Status Tool displays information about the most-recent Link Test initiated on the SM or BHS. Link Tests initiated from the AP or BHM are not included in the Link Status table. This table is useful for monitoring link test results for all SMs or BHS in the system. The Link Status table is color coded to display health of link between AP/BHM and SM/BHS. The current Modulation Level Uplink/Downlink is chosen to determine link health and color coded accordingly. Uplink/Downlink Rate Column will be color coded using current Rate as per the table below:

Table 111 Color code versus uplink/downlink rate column Actual Rate 1x 2x 3x 4x SISO MIMO-A MIMO B RED RED NA ORANGE GREEN BLUE ORANGE GREEN BLUE 6x NA NA 8x NA NA RED NA ORANGE GREEN BLUE Page 2-361 Chapter 2: Tools Link Status AP/BHM Using the Link Status tool The current Uplink Rate for each SM or BHS in Session in now available on AP or BHM Link Status Page. From system release 15.2, a single Rate is used and shown for all data channels of an SM. The Link Status tool results include values for the following fields for AP/BHM. Table 112 Link Status page attributes AP/BHM Attribute Subscriber Meaning This field displays the MAC address and Site Name of the SM. Note The MAC is hot link to open the interface to the SM. In some instances, depending on network activity and network design, this route to the interface yields a blank web page. If this occurs, refresh your browser view. Site Name indicates the name of the SM. You can assign or change this name on the Configuration web page of the SM. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. LUID This field displays the LUID (logical unit ID) of the SM/BHS. As each SM or BHS registers to the AP/BHM, the system assigns an LUID of 2 or a higher unique number to the SM/BHS. If a SM/BHS loses registration with the AP/BHS and then regains registration, the SM/BHS will retain the same LUID. Note Both the LUID and the MAC are hot links to open the interface to the SM/BHS. In some instances, depending on network activity and network design, this route to the interface yields a blank web page. If this occurs, refresh your browser view. Downlink Statistics Beacon % Received Curr/Min/Max/Avg This field displays a count of beacons received by the SM in percentage. This value must be between 99-100%. If it is lower than 99%, it indicates a problematic link. This statistic is updated every 16 seconds. Downlink Statistics Power Level: Signal Strength Ratio This field represents the received power level at the SM/BHS as well as the ratio of horizontal path signal strength to vertical path signal strength at the SM/BHS. Page 2-362 Chapter 2: Tools Using the Link Status tool Downlink Statistics Signal to Noise Ratio This field represents the signal to noise ratio for the downlink (displayed when parameter Signal to Noise Ratio Calculation during Link Test is enabled) expressed for both the horizontal and vertical channels. Downlink Statistics Average EVM (dB) This field displays the average EVM statistics that measures RF signal quality. Downlink Statistics Link Test Efficiency This field displays the efficiency of the radio link, expressed as a percentage, for the radio downlink. Downlink Statistics SU-MIMO Rate The SU-MIMO rate applies to all AP platforms. For 450m, this field indicates the rate being used for symbols where this particular VC is not being MU-MIMO grouped with other SMs. For 450 and 450i platforms, there is no grouping and this field indicates the modulation rate for all symbols. Downlink Statistics MU-MIMO Rate This field indicates the modulation rate used for symbols where the low or medium priority data channels are MU-MIMO scheduled by grouping it in the same slot with other low or Medium priority data channels from other SM's. Uplink Statistics -

Power Level: Signal Strength Ratio This field represents the combined received power level at the AP/BHM as well as the ratio of horizontal path signal strength to vertical path signal strength. Uplink Statistics Fragments Modulation Uplink Statistics Signal to Noise Ratio This field represents the percentage of fragments received at each modulation state, per path (polarization). This field represents the signal to noise ratio for the uplink (displayed when parameter Signal to Noise Ratio Calculation during Link Test is enabled) expressed for both the horizontal and vertical channels. Uplink Statistics Link Test Efficiency This field displays the efficiency of the radio link, expressed as a percentage, for the radio uplink. Uplink Statistics SU-

MIMO Rate Uplink Statistics MU-

MIMO Rate The SU-MIMO rate applies to all AP platforms. For 450m, this field indicates the rate being used for symbols where a VC is not being MU-MIMO grouped with other SMs. For 450 and 450i platforms, there is no grouping and this field indicates the modulation rate for all symbols. This field indicates the modulation rate used for symbols where the low or medium priority data channels are MU-MIMO scheduled by grouping it in the same slot with other high or ultra high priority data channels from other SM's. Page 2-363 Chapter 2: Tools Using the Link Status tool BER Results This field displays the over-the-air Bit Error Rates for each downlink. (The ARQ [Automatic Resend Request] ensures that the transport BER [the BER seen end-to-end through a network] is essentially zero.) The level of acceptable over-the-air BER varies, based on operating requirements, but a reasonable value for a good link is a BER of 1e-4 (1 x 10-4) or better, approximately a packet resend rate of 5%. BER is generated using unused bits in the downlink. During periods of peak load, BER data is not updated as often, because the system puts priority on transport rather than on BER calculation. Reg Requests A Reg Requests count is the number of times the SM/BHS registered after the AP/BHM determined that the link had been down. ReReg Requests If the number of sessions is significantly greater than the number for other SMs/BHS, then this may indicate a link problem (check mounting, alignment, receive power levels) or an interference problem (conduct a spectrum scan). A ReReg Requests count is the number of times the AP/BHM received a SM/BHS registration request while the AP/BHM considered the link to be still up (and therefore did not expect registration requests). If the number of sessions is significantly greater than the number for other SMs/BHS, then this may indicate a link problem (check mounting, alignment, receive power levels) or an interference problem (conduct a spectrum scan). Page 2-364 Chapter 2: Tools Link Status SM/BHS Using the Link Status tool The Link Status tool of SM/BHS displays Downlink Status and Uplink Status information. Table 113 Link Status page attributes SM/BHS Page 2-365 Chapter 2: Tools Using the Link Status tool Attribute Meaning Downlink Status Receive Power This field lists the current combined receive power level, in dBm. Path Info Signal Strength Ratio This field displays the difference of the Vertical path received signal power to the Horizontal path received signal power for downlink. Signal to Noise Ratio This field lists the current signal-to-noise level, an indication of the separation of the received power level vs. noise floor for downlink. Average EVM Beacons This field displays the average EVM statistics that measures RF signal quality. Displays a count of beacons received by the SM in percentage. This value must be typically between 99-100%. If lower than 99%, it indicates a problematic link. This statistic is updated every 16 seconds. Received Fragments Modulation This field represents the percentage of fragments received at each modulation state, per path (polarization) Latest Remote Link Test Efficiency Percentage This field is not applicable. BER Total Avg Results This field displays the over-the-air average Bit Error Rates (BER) for downlink. Beacons Received Last 15 minutes The beacon count on the SM can be used to estimate the interference in the channel. The min/avg/max beacon percentage displayed based on this value for the last 15 mins. Uplink Status Transmit Power This field displays the current combined transmit power level, in dBm. Max Transmit Power This field displays the maximum transmit power of SM. Power Level This field indicates the combined power level at which the SM is set to transmit, based on the Country Code and Antenna Gain settings. Signal Strength Ratio This field displays the difference of the Vertical path received signal power to the Horizontal path received signal power for uplink. Page 2-366 Chapter 2: Tools Using the Link Status tool Signal to Noise Ratio This field lists the current signal-to-noise level, an indication of the separation of the received power level vs. noise floor for uplink. Average EVM This field displays the average EVM statistics that measures RF signal quality. Latest Remote Link Test Efficiency Percentage Local Stats Session Status This field is not applicable. This field displays the current state, Virtual channel, channel rate adaptation and MIMO-A/MIMO-B/SISO status of SM. Spatial Frequency This filed displays the spatial frequency value of the VC or SM. Run Link Test See Exploratory Test section of Performing Extrapolated Link Test on page 2-342 Link Quality Indicator LQI Downlink LQI Downlink Actual Average Modulation Rate Downlink Expected Modulation Rate Beacon Quality Index Uplink LQI Uplink Actual Average Modulation Rate Uplink Expected Modulation Rate This field displays the quality of the link used for data communication between AP and SM. This value is derived by calculating:

Downlink LQI value * Uplink LQI value * Re-Registration Quality Index value This field displays the downlink quality of the link. It is the ratio of Actual Average Modulation Rate of the data packets and the expected modulation rate. This field displays the average value of the actual Downlink modulation rate. This field displays the expected Downlink modulation rate. This field displays the Beacon Quality Index. It is calculated based on the receive beacon percentage. This field displays the uplink quality of the link. It is the ratio of Actual Average Modulation Rate of the data packets and the expected modulation rate. This field displays the average value of the actual uplink modulation rate. This field displays the expected Uplink modulation rate. Page 2-367 Chapter 2: Tools Using the Link Status tool Re-Registration Quality Index This field displays the number of re-registrations of the SM. When there are no re-registrations, this quality index will be 100%. Re-Registration Count This field displays the re-registration count of the SM. Reference Downlink Quality Index Reference Uplink Quality Index Access Point MAC Address Downlink reference EVM used for LQI calculations. Uplink reference EVM used for LQI calculations. This field displays the MAC address of the AP to which this SM is registered. Page 2-368 Chapter 2: Tools Using BER Results tool Using BER Results tool Radio BER data represents bit errors at the RF link level. Due to CRC checks on fragments and packets and ARQ (Automatic Repeat Request), the BER of customer data is essentially zero. Radio BER gives one indication of link quality. Other important indications to consider includes the received power level, signal to noise ratio and link tests. BER is only instrumented on the downlink and is displayed on the BER Results tab of the Tools page in any SM. Each time the tab is clicked, the current results are read and counters are reset to zero. The BER Results tab can be helpful in troubleshooting poor link performance. The link is acceptable if the value of this field is less than 104. If the BER is greater than 104, re-evaluate the installation of both modules in the link. The BER test signal is broadcast by the AP/BHM (and compared to the expected test signal by the SM/BHS) only when capacity in the sector allows it. This signal is the lowest priority for AP/BHM transmissions. Figure 80 BER Results tab of the SM Page 2-369 Chapter 2: Tools Using the Sessions tool Using the Sessions tool The PMP 450 Platform Family AP has a tab Sessions under the Tools category which allows operators to drop one or all selected SM sessions and force a SM re-registration. This operation is useful to force QoS changes for SMs without losing AP logs or statistics. This operation may take 5 minutes to regain all SM registrations. Figure 81 Sessions tab of the AP Page 2-370 Chapter 2: Tools Using the Ping Test tool Using the Ping Test tool The PMP 450 Platform Family AP has a tab Ping Test under the Tools category which allows users to check the accessibility of the given IP V4 address or a valid domain name Figure 82 Ping Test tab of the AP Note When a domain name (for example, www.google.com) is used for ping test, make sure that Preferred DNS Server and Alternate DNS Server parameters are configured in the Configuration > IP tab of the AP. Page 2-371 Chapter 3: Operation Chapter 3: Operation This chapter provides instructions for operators of the 450 Platform Family wireless Ethernet Bridge. The following topics are described in this chapter:

System information on page 3-2 o Viewing General Status on page 3-2 o Viewing Session Status on page 3-24 o Viewing Remote Subscribers on page 3-35 o o Viewing the Network Interface on page 3-38 o Viewing the Layer 2 Neighbors on page 3-38 Interpreting messages in the Event Log on page 3-35 System statistics on page 3-39 Interpreting RF Control Block statistics Interpreting VLAN statistics on page 3-51 Interpreting Overload statistics on page 3-61 Interpreting Ethernet statistics on page 3-44 Interpreting MIR/Burst statistics on page 3-55 Interpreting Proportional Scheduler on page 3-55 Interpreting Data Channels statistics on page 3-52 Interpreting Bridging Table statistics on page 3-43 Interpreting Translation Table statistics on page 3-43 o Viewing the Scheduler statistics on page 3-39 o Viewing list of Registration Failures statistics on page 3-41 o o o o o o o o o o o o Viewing ARP statistics on page 3-66 o Viewing NAT statistics on page 3-66 o Viewing NAT DHCP Statistics on page 3-68 o o o o o o o Interpreting Bridge Control Block statistics on page 3-72 Interpreting Frame Utilization statistics on page 3-79 Interpreting Pass Through Statistics on page 3-75 Interpreting DHCP Relay statistics on page 3-63 Interpreting Sync Status statistics on page 3-69 Interpreting SNMPv3 Statistics on page 3-76 Interpreting syslog statistics on page 3-78 Interpreting Filter statistics on page 3-65 Interpreting PPPoE Statistics for Customer Activities on page 3-70 Radio Recovery on page 3-89 Page 3-1 Chapter 3: Operation System information System information This section describes how to use the summary and status pages to monitor the status of the Ethernet ports and wireless link. Viewing General Status on page 3-2 Viewing Session Status on page 3-24 Viewing Remote Subscribers on page 3-35 Viewing the Network Interface on page 3-38 Viewing the Layer 2 Neighbors on page 3-38 Interpreting messages in the Event Log on page 3-35 Viewing General Status The General Status tab provides information on the operation of this AP/BHM and SM/BHS. This is the page that opens by default when you access the GUI of the radio. Page 3-2 System information Chapter 3: Operation General Status page of AP The General Status page of PMP 450m AP is explained in Table 114 The General Status page of PMP 450 AP is explained in.Table 115 The General Status page of PMP 450i AP is explained in Table 116. Table 114 General Status page attributes PMP 450m AP Page 3-3 Chapter 3: Operation System information Attribute Device Type Meaning This field indicates the type of the module. Values include the frequency band of the device, its module type and its MAC address. Board Type This field indicates the series of hardware. Product Type Software Version The field indicates model number of 450m device. The 450m Series has two model variants. PMP 450m: This model works in SU-MIMO mode which is default limited mode. The MU-MIMO license can be purchased from Cambium Networks and applied. MU-MIMO: This model works in MU-MIMO mode. This field indicates the system release, the time and date of the release and whether communications involving the module are secured by AES encryption. If you request technical support, provide the information from this field. Bootloader Version This field indicates the version of Uboot running on the 450m AP platform. CPU Usage Board MSN Board Model FPGA Version Uptime System Time This field indicates the current CPU utilization of the device. This field indicates the Manufacturers Serial number. A unique serial number assigned to each radio at the factory for inventory and quality control. This field indicates the Manufacturers Model number. A unique serial number assigned to each for inventory and quality control. This field indicates the version of the field-programmable gate array (FPGA) on the module. If you request technical support, provide the value of this field. This field indicates how long the module has operated since power was applied. This field provides the current time. If the AP is connected to a CMM4, then this field provides GMT (Greenwich Mean Time). Any SM that registers to the AP inherits the system time. Main Ethernet Interface This field indicates the speed and duplex state of the Ethernet interface to the AP. Page 3-4 Chapter 3: Operation Region Code Regulatory DFS (Dynamic Frequency Selection) System information A parameter that offers multiple fixed selections, each of which automatically implements frequency band range for the selected region. Units shipped to regions other than restrictions the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. This field indicates whether the configured Country Code and radio frequency are compliant with respect to their compatibility. 450 Platform Family products shipped to the United States is locked to a Country Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Country Code to comply with local regulatory requirements. This field dynamically selects frequency based on detection of radar pulses. Channel Frequency This field indicates the current operating center frequency, in MHz. Channel Bandwidth This field indicates the current size of the channel band used for radio transmission. Cyclic Prefix OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol to allow multi-

pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. Frame Period This field indicates the current Frame Period setting of the radio in ms. Encryption Color Code Max Range This field indicates the capability and the encryption configuration of the device. This field displays a value from 0 to 254 indicating the APs configured color code. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). This field indicates the setting of the Max Range parameter, which contributes to the way the radio transmits. Verify that the Max Range parameter is set to a distance slightly greater than the distance between the AP and the furthest SM that must register to this AP. EIRP This field indicates the combined power level at which the AP will transmit, based on the Country Code. Temperature This field indicates the current operating temperature of the device board. Page 3-5 Chapter 3: Operation System information Registered SM Count This field indicates how many SMs are registered to the AP. Sync Pulse Status This field indicates the status of synchronization as follows:

Generating Sync indicates that the module is set to generate the sync pulse. Receiving Sync indicates that the module is set to receive a sync pulse from an outside source and is receiving the pulse. No Sync Since Boot up / ERROR: No Sync Pulse indicates that the module is set to receive a sync pulse from an outside source and is not receiving the pulse. Note When this message is displayed, the AP transmitter is turned off to avoid self-interference within the system. Sync Pulse Source This field indicates the status of the synchronization source:

Searching indicates that the unit is searching for a GPS fix Timing Port/UGPS indicates that the module is receiving sync via the timing AUX/SYNC timing port Power Port indicates that the module is receiving sync via the power port

(Ethernet port). On-board GPS indicates that the module is receiving sync via the units internal GPS module This field displays the largest number of SMs that have been simultaneously registered in the AP since it was last rebooted. This count can provide some insight into sector history and provide comparison between current and maximum SM counts at a glance. This field indicates the number of frame slots that are designated for use by data traffic in the downlink (sent from the AP to the SM). The AP calculates the number of data slots based on the Max Range, Downlink Data and

(reserved) Contention Slots configured by the operator. This field indicates the number of frame slots that are designated for use by data traffic in the uplink (sent from the SM to the AP). The AP calculates the number of data slots based on the Max Range, Downlink Data and (reserved) Contention Slots configured by the operator. Maximum Count of Registered SMs Data Slots Down Data Slots Up Contention Slots This field indicates the number of (reserved) Contention Slots configured by the operator. See Contention slots on page1-208. Connection Status This field indicates the device connectivity to cnMaestro (Cambiums cloud-

based network management system). Account ID This field shows Account ID which is registered with Cambium Networks and it allows operator to manage devices using cnMaestro. Page 3-6 Chapter 3: Operation System information Site Name Site Contact Site Location MU-MIMO Mode AES-256 Encryption Keyed Time Updated and Location Code This field indicates the name of the physical module. You can assign or change this name in the SNMP tab of the AP Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. This field indicates contact information for the physical module. You can provide or change this information in the SNMP tab of the AP Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. This field indicates site information for the physical module. You can provide or change this information in the SNMP tab of the AP Configuration page. This field displays information about MU-MIMO mode. If AP is keyed as MU-

MIMO, it will display MU-MIMO (Multi User - MIMO) otherwise it will display SU-MIMO (Single User - MIMO). This displays the status of the entered AES-256 Encryption Key. Note To enable AES-256 Encryption, a feature key needs to be purchased. This field displays information about the keying of the radio. Page 3-7 Chapter 3: Operation Table 115 General Status page attributes PMP 450 AP System information Page 3-8 Chapter 3: Operation System information Attribute Device Type Board Type Meaning See Table 114 General Status page attributes PMP 450m AP on page 3-3 for details Product Type This indicates model of the device. Software Version See Table 114 General Status page attributes PMP 450m AP on page 3-3 for details CPU Usage Board MSN FPGA Version This field indicates the current CPU utilization of the device. This field indicates the Manufacturers Serial number. A unique serial number assigned to each radio at the factory for inventory and quality control. See Table 114 General Status page attributes PMP 450m AP on page 3-3 for details PLD Version This field indicates the firmware version on the Programmable Logic Device. Uptime System Time Main Ethernet Interface Region Code Regulatory Antenna Type Channel Center Frequency Channel Bandwidth Cyclic Prefix Frame Period Color Code Max Range Transmit Power Temperature See Table 114 General Status page attributes PMP 450m AP on page 3-3 for details See Table 114 General Status page attributes PMP 450m AP on page 3-3 for details This field indicates the combined power level at which the AP is set to transmit, based on the Country Code and Antenna Gain settings. See Table 114 General Status page attributes PMP 450m AP on page 3-3 for details Total Antenna Gain This field indicates the total antenna gain. Sync Pulse Status Sync Pulse Source Page 3-9 Chapter 3: Operation System information See Table 114 General Status page attributes PMP 450m AP on page 3-3 for details Maximum Count of Registered SMs Data Slots Down Data Slots Up Contention Slots Connection Status Account ID Site Name Site Contact Site Location Time Updated and Location Code Table 116 General Status page attributes PMP 450i AP Page 3-10 Chapter 3: Operation System information Attribute Device Type Board Type Meaning See Table 114 General Status page attributes PMP 450m AP on page 3-3 for details Product Type This indicates model of the device. Software Version See Table 114 General Status page attributes PMP 450m AP on page 3-3 for details CPU Usage Board MSN This field indicates the current CPU utilization of the device. This field indicates the Manufacturers Serial number. A unique serial number assigned to each radio at the factory for inventory and quality control. Board Model This field indicates the Manufacturers Model number. FPGA Version Uptime System Time Main Ethernet Interface Aux Ethernet Interface Region Code Regulatory See Table 114 General Status page attributes PMP 450m AP on page 3-3 for details See Table 114 General Status page attributes PMP 450m AP on page 3-3 for details See Table 114 General Status page attributes PMP 450m AP on page 3-3 for details Page 3-11 Chapter 3: Operation System information Antenna Type Channel Center Frequency Channel Bandwidth Cyclic Prefix Frame Period Color Code Max Range Transmit Power This field indicates the combined power level at which the AP is set to transmit, based on the Country Code and Antenna Gain settings. Total Antenna Gain This field indicates the total antenna gain. Temperature See Table 114 General Status page attributes PMP 450m AP on page 3-3 for details 802.3at Type 2 PoE Status The field displays whether PoE Classification functionality is enabled or disabled. It is only applicable for 450i Series devices. Registered SM Count Sync Pulse Status Sync Pulse Source Maximum Count of Registered SMs Data Slots Down Data Slots Up Contention Slots Connection Status Account ID Site Name Site Contact Site Location Time Updated and Location Code See Table 114 General Status page attributes PMP 450m AP on page 3-3 for details See Table 114 General Status page attributes PMP 450m AP on page 3-3 for details Page 3-12 Chapter 3: Operation General Status page - SM The SMs General Status page is explained in Table 117. System information Note For accurate power level readings to be displayed, traffic must be present on the radio link. Table 117 General Status page attributes - SM Page 3-13 Chapter 3: Operation System information Attribute Meaning Device Type This field indicates the type of the module. Values include the frequency band of the SM, its module type and its MAC address. Board Type This field indicates the series of hardware. Product Type This indicates model of the device. Software Version This field indicates the system release, the time and date of the release. If you request technical support, provide the information from this field. CPU Usage Board MSN This field indicates the current CPU utilization of the device. This field indicates the Manufacturers Serial number. A unique serial number assigned to each radio at the factory for inventory and quality control. Board Model This field indicates the Manufacturers Model number. FPGA Version Uptime System Time This field indicates the version of the field-programmable gate array (FPGA) on the module. When you request technical support, provide the information from this field. This field indicates how long the module has operated since power was applied. This field provides the current time. Any SM that registers to an AP inherits the system time, which is displayed in this field as GMT (Greenwich Mean Time). Ethernet Interface This field indicates the speed and duplex state of Ethernet interface to the SM. Page 3-14 Chapter 3: Operation Regional Code System information A parameter that offers multiple fixed selections, each of which automatically implements frequency band range restrictions for the selected region. Units shipped to regions other than the United States must be configured with the corresponding Country Code to comply with local regulatory requirements. DFS This field indicates that DFS operation is enabled based on the configured region code, if applicable. Antenna Type The current antenna type that has been selected. Frame Period This field indicates the current Frame Period setting of the radio in ms. Encryption This field indicates the capability and the encryption configuration of the device. Temperature The current operating temperature of the board. Session Status This field displays the following information about the current session:

Scanning indicates that this SM currently cycles through the radio frequencies that are selected in the Radio tab of the Configuration page. Syncing indicates that this SM currently attempts to receive sync. Registering indicates that this SM has sent a registration request message to the AP and has not yet received a response. Registered indicates that this SM is both:

registered to an AP. ready to transmit and receive data packets. Session Uptime Registered AP Color Code This field displays the duration of the current link. The syntax of the displayed time is hh:mm:ss. Displays the MAC address and site name of the AP to which the SM is registered to. This parameter provides click-through proxy access to the APs management interface. This field displays a value from 0 to 254 indicating the SMs configured color code. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Channel Frequency This field lists the current operating frequency of the radio. Channel Bandwidth The size in MHz of the operating channel. Page 3-15 Chapter 3: Operation Cyclic Prefix Air Delay System information OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol to allow multi-

pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. This field displays the distance in feet between this SM and the AP. To derive the distance in meters, multiply the value of this parameter by 0.3048. Distances reported as less than 200 feet (61 meters) are unreliable. Receive Power This field lists the current combined receive power level, in dBm. Signal Strength Ratio This field displays the difference of the Vertical path received signal power to the Horizontal path received signal power. Signal to Noise Ratio This field lists the current signal-to-noise level, an indication of the separation of the received power level vs. noise floor. Beacons Displays a count of beacons received by the SM in percentage. This value must be typically between 99-100%. If lower than 99%, it indicates a problematic link. This statistic is updated every 16 seconds. Transmit Power This field lists the current combined transmit power level, in dBm. Note The red SM message target power exceeded maximum does not necessarily indicate a problem. In this case, the AP is requesting the SM to transmit at a higher power level, but the SM is restricted due to EIRP limits or hardware capabilities. This message can be an indication that the SM is deployed further from the AP than optimal, causing the AP to adjust the SM to maximum transmit power. Data Slots Down This field lists the number of slots used for downlink data transmission. Data Slots Up This field lists the number of slots used for uplink data transmission. Contention Slots This field indicates the number of (reserved) Contention Slots configured by the operator. See Contention slots on page1-208. Site Name Site Contact This field indicates the name of the physical module. You can assign or change this name in the SNMP tab of the SM Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. This field indicates contact information for the physical module. You can provide or change this information in the SNMP tab of the SM Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Page 3-16 Chapter 3: Operation System information Site Location This field indicates site information for the physical module. You can provide or change this information in the SNMP tab of the SM Configuration page. Maximum Throughput This field indicates the limit of aggregate throughput for the SM and is based on the default (factory) limit of the SM and any floating license that is currently assigned to it. This field displays information about the keying of the radio. Time Updated and Location Code Note For PMP 450 SM 900 MHz, there is additional parameter Path Info (under Subscriber Module Stats) which displays polarization path(A & B) information. Page 3-17 Chapter 3: Operation General Status page of BHM The BHMs General Status page is explained in Table 118. Table 118 General Status page attributes - BHM System information Attribute Meaning Device Type This field indicates the type of the module. Values include the frequency band of the BHM, its module type and its MAC address. Page 3-18 Chapter 3: Operation System information Board Type This field indicates the series of hardware. Product Type This indicates model of the device. Software Version This field indicates the system release, the time and date of the release. If you request technical support, provide the information from this field. CPU Usage Board MSN This field indicates the current CPU utilization of the device. This field indicates the Manufactures Serial number. A unique serial number assigned to each radio at the factory for inventory and quality control. Board Model This field indicates the Manufacturers Model number. FPGA Version Uptime System Time This field indicates the version of the field-programmable gate array (FPGA) on the module. When you request technical support, provide the information from this field. This field indicates how long the module has operated since power was applied. This field provides the current time. Any BHS that registers to a BHM inherits the system time, which is displayed in this field as GMT (Greenwich Mean Time). Ethernet Interface This field indicates the speed and duplex state of Ethernet interface to the BHM. Antenna Type The current antenna type that has been selected. Temperature The current operating temperature of the board. Session Status This field displays the following information about the current session:

Scanning indicates that this BHS currently cycles through the radio frequencies that are selected in the Radio tab of the Configuration page. Syncing indicates that this BHM currently attempts to receive sync. Registering indicates that this BHM has sent a registration request message to the BHM and has not yet received a response. Registered indicates that this BHM is both:

Registered to a BHM. Ready to transmit and receive data packets. Session Uptime This field displays the duration of the current link. The syntax of the displayed time is hh:mm:ss. Registered Backhaul Displays the MAC address and site name of the BHM to which the BHS is registered to. This parameter provides click-through proxy access to the BHMs management interface. Channel Frequency This field lists the current operating frequency of the radio. Receive Power This field lists the current combined receive power level, in dBm. Page 3-19 Chapter 3: Operation System information Signal Strength Ratio This field displays the difference of the Vertical path received signal power to the Horizontal path received signal power. Transmit Power This field lists the current combined transmit power level, in dBm. Signal to Noise Ratio This field lists the current signal-to-noise level, an indication of the separation of the received power level vs. noise floor. Beacons Air Delay Displays a count of beacons received by the BHM in percentage. This value must be typically between 99-100%. If lower than 99%, it indicates a problematic link. This statistic is updated every 16 seconds. This field displays the distance in feet between this BHS and the BHM. To derive the distance in meters, multiply the value of this parameter by 0.3048. Distances reported as less than 200 feet (61 meters) are unreliable. Data Slots Down This field lists the number of slots used for downlink data transmission. Data Slots Up This field lists the number of slots used for uplink data transmission. Regional Code Site Name Time Updated and Location Code A parameter that offers multiple fixed selections, each of which automatically implements frequency band range restrictions for the selected region. Units shipped to regions other than the United States must be configured with the corresponding Country Code to comply with local regulatory requirements. This field indicates the name of the physical module. Assign or change this name in the Configuration > SNMP page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. This field displays information about the keying of the radio. Page 3-20 Chapter 3: Operation General Status page of BHS The BHSs General Status page is explained in Table 119. Table 119 General Status page attributes - BHS System information Page 3-21 Chapter 3: Operation System information Attribute Meaning See Table 119 on page 3-21 Device Type Board Type Software Version CPU Usage Board MSN Board Model FPGA Version Uptime System Time Ethernet Interface Antenna Type Temperature Session Status Session Uptime Registered Backhaul Channel Frequency Receive Power See Table 119 on page 3-21 Signal Strength Ratio Transmit Power Signal to Noise Ratio Beacons Air Delay Data Slots Down Data Slots Up Regional Code Site Name Page 3-22 Chapter 3: Operation System information Site Contact Site Location Time Updated and Location Code Page 3-23 Chapter 3: Operation System information Viewing Session Status The Session Status page in the Home page provides information about each SM or BHS that has registered to the AP or BHM. This information is useful for managing and troubleshooting a system. This page also includes the current active values on each SM or BHS for MIR and VLAN, as well as the source of these values, representing the SM/BHS itself, Authentication Server, or the Authentication Server and SM/BHS. Note For accurate power level readings to be displayed, traffic must be present on the radio link. The Session Status List has four tabs: Device, Session, Power, Configuration, and Link Quality. The SessionStatus.xml hyper link allows user to export session status page from web management interface of AP or BHM. The session status page will be exported in xml file. Device tab The Device tab provides information on the Subscribers LUID and MAC, Hardware, Software, FPGA versions and the state of the SM/BHS (Registered and/or encrypted). Table 120 Device tab attributes Attribute Subscriber Meaning This field displays the LUID (logical unit ID), MAC address and Site Name of the SM/BHS. Note The MAC is a hot link to open the interface to the SM/BHS. In some instances, depending on network activity and network design, this route to the interface yields a blank web page. If this occurs, refresh your browser view. Site Name indicates the name of the SM/BHS. Change this name on the Configuration web page of the SM/BHS. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Page 3-24 Chapter 3: Operation System information LUID This field displays the LUID (logical unit ID) of the SM/BHS. As each SM or BHS registers to the AP/BHM, the system assigns an LUID of 2 or a higher unique number to the SM/BHS. If a SM/BHS loses registration with the AP/BHS and then regains registration, the SM/BHS will retain the same LUID. Note Both the LUID and the MAC are hot links to open the interface to the SM/BHS. In some instances, depending on network activity and network design, this route to the interface yields a blank web page. If this occurs, refresh your browser view. Hardware This field displays the SMs or BHS hardware type. Software Version This field displays the software release that operates on the SM/BHS, the release date and time of the software. FPGA Version This field displays the version of FPGA that runs on the SM/BHS State This field displays the current status of the SM/BHS as either IN SESSION to indicate that the SM/BHS is currently registered to the AP/BHM. IDLE to indicate that the SM/BHS was registered to the AP/BHM at one time, but now is not. This field also indicates whether the encryption scheme in the module is enabled. Page 3-25 Chapter 3: Operation Session tab System information The Session tab provides information on the SMs or BHS Session Count, Reg Count, Re-Reg Count, Uptime, Air delay, PPPoE State and Timeouts. Table 121 Session tab attributes Attribute Subscriber LUID State Meaning See Table 120 on page 3-24. See Table 120 on page 3-24. This filed displays the status of the registered SM. Uptime (Downtime) Once a SM/BHS successfully registers to an AP/BHM, this timer is started. If a session drops or is interrupted, this timer is reactivated once re-

registration is complete. Session Count This field displays how many sessions the SM/BHS has had with the AP/BHM. Typically, this is the sum of Registration Requests and Re-

Registration Requests. However, the result of internal calculation may display here as a value that slightly differs from the sum. If the number of sessions is significantly greater than the number for other SMs or BHS, then this may indicate a link problem or an interference problem. Registration Requests When a SM/BHS makes a Registration Request, the AP/BHM checks its local session database to see whether it was registered earlier. If the AP/BHM concludes that the SM/BHS is not currently in session database and it is valid Registration Request, then the request increments the value of this field. In ideal situation, the Registration Requests indicates total number of connected SMs to an AP. Note The user can clear Registration Requests by dropping all current sessions of SM (or BHS) from Configuration > Tools >

Sessions menu. Page 3-26 Chapter 3: Operation System information Re- Registration Requests CC Priority AirDelay PPPoE state Timeout When a SM/BHS makes a Registration Request, the AP/BHM checks its local session database to see whether it was registered earlier. If the AP/BHM concludes that the SM/BHS is currently in session database, then the request increments the value of this field. Typically, a Re-Registration Requests is the case where both:

SM/BHS attempts to reregister for having lost communication with the AP/BHM. AP/BHM has not yet observed the link to the SM/BHS as being down. It is possible for a small period of time if there is no downlink traffic and AP/BHM still assumes the session is up, but the SM/BHS, loses session and quickly re-connects before the AP/BHM knew the session had dropped. This is how a re-registration happens. If the number of sessions is significantly greater than the number for other SMs or BHS, then this may indicate a link problem (check mounting, alignment, receive power levels) or an interference problem (conduct a spectrum scan). The field displays Color Code Priority (ICC, Primary, Secondary or Tertiary) of all connected SM. This field displays the distance of the SM/BHS from the AP/BHM in meters, nanoseconds and bits. At close distances, the value in this field is unreliable. This field displays the current PPPoE state (whether configured) of the SM/BHS. This field displays the timeout in seconds for management sessions via HTTP, ftp access to the SM/BHS. 0 indicates that no limit is imposed. Power tab Table 122 Power tab attributes Page 3-27 Chapter 3: Operation System information Attribute Subscriber LUID Hardware Downlink Rate SU-MIMO Downlink Rate MU-MIMO Uplink Rate SU-MIMO Uplink Rate MU-MIMO Meaning See Table 120 on page 3-24. See Table 120 on page 3-24. This field displays the SMs or BHS hardware type. This field displays whether the high-priority channel is enabled in the SM/BHS and the status of rate adapt. For example, if 8X/4X is listed, the radio is capable of operating at 8X but is currently operating at 4X, due to RF conditions. This field also states whether it is MIMO-A or MIMO-B radio e.g. 8X/8X MIMO-B indicates MIMO-B and 8X/4X MIMO-A indicates MIMO-A. A data channel starts at its lowest modulation and slowly rate adapts up, as traffic is successfully transmitted over the data channel. From system release 15.2, all data channels in a single SM will have the same modulation rates. Note: The SU-MIMO rate applies to all AP platforms. For 450m, this field indicates the rate being used for symbols where this particular VC is not being MU-MIMO grouped with other SMs. This field indicates the modulation rate used for symbols where the low or medium priority data channels are MU-MIMO scheduled by grouping it in the same slot with other low or Medium priority data channels from other SM's. This field the status of rate adapt. For example, if 8X/4X is listed, the radio is capable of operating at 8X but is currently operating at 4X, due to RF conditions. This field also states whether it is MIMO-A or MIMO-B radio e.g. 8X/8X MIMO-B indicates MIMO-B and 8X/4X MIMO-A indicates MIMO-A. A data channel starts at its lowest modulation and slowly rate adapts up, as traffic is successfully transmitted over the data channel. From system release 15.2, all data channels in a single SM will have the same modulation rates. Note: The SU-MIMO rate applies to all AP platforms. For 450m, this field indicates the rate being used for symbols where this particular VC is not being MU-MIMO grouped with other SMs. This field indicates the modulation rate used for symbols where the MUMIMO groupable data channels are MU-MIMO scheduled by grouping it in the same slot with other MU-MIMO groupable data channels from other SM's. AP Rx Power (dBm) This field indicates the APs or BHMs combined receive power level for the listed SM/BHS. Page 3-28 Chapter 3: Operation Signal Strength Ratio (dB) System information This field displays the ratio of the Vertical path received signal power to the Horizontal path received signal power. This ratio can be useful for determining multipathing conditions (high vertical to horizontal ratio) for Uplink. Signal to Noise Ratio (dB) This field lists the current signal-to-noise level, an indication of the separation of the received power level vs. noise floor. In other words, it indicates signal to noise ratio for Uplink. Page 3-29 Chapter 3: Operation Configuration tab System information The Configuration tab provides information on the SMs or BHS Uplink or Downlink (UL/DL) Sustained Data Rate, UL/DL Burst Allocation, UL/DL Burst Rate, UL/DL Low Priority CIR, UL/DL Medium Priority CIR UL/DL High Priority CIR, UL/DL Ultra High Priority CIR, the UL/DL Broadcast or Multicast Allocation, SM Prioritization Group, RADIUS Authentication Reply, and RADIUS Authentication Server. This data is refreshed based on the Web Page Auto Update setting on the APs or BHSs General Configuration page. Table 123 Configuration tab attributes Attribute Subscriber LUID Sustained Data Rate Cap (kbps) Sustained Data Rate

(kbps) - Uplink Sustained Data Rate

(kbps) - Downlink Burst Allocation (kbit)

- Uplink Meaning See Table 120 on page 3-24. See Table 120 on page 3-24. This field specifies the maximum sustained data rate between SM/BHS and AP/BHM. If this field displays Uncapped, then there is no limit set for data rate. If this field displays 4000, then the maximum sustained data rate between SM/BHS and AP/BHM is limited to 4000 kbps. This field displays the value that is currently in effect for the SM/BHS, with the source of that value in parentheses. This is the specified rate at which each SM/BHS registered to this AP/BHM is replenished with credits for transmission. The configuration source of the value is indicated in parentheses. See Maximum Information Rate (MIR) Parameters on page 1-236. This field displays the value that is currently in effect for the SM/BHS, with the source of that value in parentheses. This is the specified the rate at which the AP/BHM should be replenished with credits (tokens) for transmission to each of the SMs/BHSs in its sector. The configuration source of the value is indicated in parentheses. See Maximum Information Rate (MIR) Parameters on page 1-236. This field displays the value that is currently in effect for the SM/BHS, with the source of that value in parentheses. This is the specified maximum amount of data that each SM/BHS is allowed to transmit before being recharged at the Sustained Uplink Data Rate with credits to transmit more. The configuration source of the value is indicated in parentheses. Page 3-30 Chapter 3: Operation Burst Allocation (kbit)

- Downlink Max Burst Rate (kbit)

- Uplink Max Burst Rate (kbit)

- Downlink Low Priority CIR Medium Priority CIR High Priority CIR System information See Interaction of Burst Allocation and Sustained Data Rate Settings on page 1-238 This field displays the value that is currently in effect for the SM/BHS, with the source of that value in parentheses. This is the specified the rate at which the AP/BHM should be replenished with credits (tokens) for transmission to each of the SMs/BHSs in its sector. The configuration source of the value is indicated in parentheses. See Interaction of Burst Allocation and Sustained Data Rate Settings on page 1-238 The data rate at which an SM/BHS is allowed to burst (until burst allocation limit is reached) before being recharged at the Sustained Uplink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. See Interaction of Burst Allocation and Sustained Data Rate Settings on page 1-238 The data rate at which an SM/BHS is allowed to burst (until burst allocation limit is reached) before being recharged at the Sustained Downlink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. See Interaction of Burst Allocation and Sustained Data Rate Settings on page 1-238 This field indicates the minimum rate at which low priority traffic is sent over the uplink and downlink (unless CIR is oversubscribed or RF link quality is degraded). This field indicates the minimum rate at which medium priority traffic is sent over the uplink and downlink (unless CIR is oversubscribed or RF link quality is degraded). This field indicates the minimum rate at which high priority traffic is sent over the uplink and downlink (unless CIR is oversubscribed or RF link quality is degraded). Ultra High Priority CIR This field indicates the minimum rate at which ultra high priority traffic is sent over the uplink and downlink (unless CIR is oversubscribed or RF link quality is degraded). Broadcast/Multicast Allocation This field displays the data rate at which Broadcast and Multicast traffic is sent via the radio link. SM Prioritization Group This field displays the priority level configured on the SM under SM Prioritization Group. RADIUS Authentication Reply This field displays whether RADIUS server is reachable or not. Page 3-31 Chapter 3: Operation System information RADIUS Authentication Server This field displays the associated RADIUS Authentication Server for each SM where it was authenticated. This information is useful when there are multiple RADIUS servers (maximum three servers supported by Cambium). If one server is not reachable, other configured servers are tried in sequential order as a fall-back. In this scenario, the Session Status is useful to identify associate RADIUS Authentication Server for all connected SMs. Table 124 Session Status > Configuration CIR configuration denotations Attribute

(SM)

(APCAP)

(D)

(AAA)

(BAM) Meaning QoS/VLAN parameters are derived from the SMs/BHSs settings QoS/VLAN parameters are derived from the APs settings, including any keyed capping (for radios capped at 4 Mbps, 10 Mbps, or 20 Mbps) QoS/VLAN parameters are retrieved from the device, due to failed retrieval from the AAA or WM server. QoS/VLAN parameters are retrieved from the RADIUS server QoS/VLAN parameters are retrieved from a WM BAM server Page 3-32 Chapter 3: Operation Link Quality tab System information The Link Quality tab provides information on the Subscribers UID, Link quality, Downlink, Uplink, Beacon, ReReg, and the Uptime. This data is refreshed based on the Link Quality Update Interval parameter configuration under the Sessions Status page. Link Quality Metric parameter offers an option to choose either EVM or Rate based LQI calculation. The Link Quality tab displays the calculated Link Quality Indicator (LQI) for the configured interval

(Link Quality Update Interval parameter). Table 125 Link Quality tab attributes Link Quality Metric: Rate Link Quality Metric: EVM Attribute Meaning Page 3-33 Chapter 3: Operation Subscriber See Table 120 on page 3-24. LUID See Table 120 on page 3-24. System information Link Quality Indicator This field displays quality of the link. It is calculated based on receive power, modulation rate, re-registrations and beacon percentage. Downlink - Quality Index This field displays the downlink quality in percentage. It is calculated based on Downlink receiver power, modulation rate, and beacon percentage. Downlink -Actual Average Rate This field displays the average Downlink modulation rate. For 450m, this field specifies the SU-MIMO Modulation Rate. When Rate based LQI is selected, only actual rate and expected rate will be displayed. Downlink -Actual Average EVM Downlink - Expected Rate This field displays the average Downlink EVM rate. This field displays the expected modulation rate based on receive power in Downlink. When EVM based LQI is selected, only actual EVM and expected EVM will be displayed. Downlink - Beacon Quality Index This field displays the beacon quality index. It is calculated based on beacon percentage. Downlink - Beacon %

This field displays the received beacon percentage. Uplink - Quality Index This field displays the uplink quality in percentage. It is calculated based on Uplink receiver power and modulation rate. Uplink -Actual Average Rate Uplink -Actual Average EVM This field displays the average Uplink modulation rate. This field displays the average Uplink EVM rate. Uplink - Expected Rate This field displays the expected modulation rate based on receive power in Uplink. Re-Reg - Quality Index This field displays the re-registration quality. It is calculated based on the re-

registration count. Re-Reg Count This field displays the number of re-registrations. Uptime This field displays the uptime of the device. Page 3-34 Chapter 3: Operation System information Viewing Remote Subscribers This page allows to view the web pages of registered SMs or BHS over the RF link. To view the pages for a selected SM/BHS, click its link. The General Status page of the SM opens. Figure 83 Remote Subscribers page of AP Interpreting messages in the Event Log Each line in the Event Log of a module Home page begins with a time and date stamp. However, some of these lines wrap as a combined result of window width, browser preferences and line length. You may find this tab easiest to use if you expand the window till all lines are shown beginning with time and date stamp. Time and Date Stamp The time and date stamp reflect one of the following:

GPS time and date directly or indirectly received from the CMM4. NTP time and date from a NTP server (CMM4 may serve as an NTP server) The running time and date that you have set in the Time & Date web page. Page 3-35 Chapter 3: Operation System information Note In the Time & Date web page, if you have left any time field or date field unset and clicked the Set Time and Date button, then the time and date default to 00:00:00 UT: 01/01/00. A reboot causes the preset time to pause or, in some cases, to run in reverse. Additionally, a power cycle resets the running time and date to the default 00:00:00 UT: 01/01/00. Thus, whenever either a reboot or a power cycle has occurred, must reset the time and date in the Time & Date web page of any module that is not set to receive sync. Event Log Data Collection The collection of event data continues through reboots and power cycles. When the buffer allowance for event log data is reached, the system adds new data into the log and discards an identical amount of the oldest data. considered by the system software to have been an exception Each line that contains the expression WatchDog flags an event that was both:

Conversely, a Fatal Error () message flags an event that is recorded in the next line. Some exceptions and fatal errors may be significant and require either operator action or technical support. recorded in the preceding line. Figure 84 Event log data Messages that Flag Abnormal Events The messages listed below flag abnormal events and, case by case, may signal the need for corrective action or technical support. Page 3-36 Chapter 3: Operation Table 126 Event Log messages for abnormal events Event Message Meaning System information Expected LUID = 6 Actual LUID = 7 Something is interfering with the control messaging of the module. Also ensure that you are using shielded cables to minimize interference. Consider trying different frequency options to eliminate or reduce interference. FatalError () Loss of GPS Sync Pulse Machine Check Exception RcvFrmNum =

0x00066d ExpFrmNum =

0x000799 System Reset Exception -- External Hard Reset System Reset Exception -- External Hard Reset WatchDog The event recorded on the line immediately beneath this message triggered the Fatal Error (). Module has lost GPS sync signal. This is a symptom of a possible hardware failure. If this is a recurring message, begin the RMA process for the module. Something is interfering with the control messaging of the module. Also ensure that you are using shielded cables to minimize interference. Consider trying different frequency options to eliminate or reduce interference. The unit lost power or was power cycled. The event recorded on the preceding line triggered this WatchDog message. Messages that Flag Normal Events The messages listed below record normal events and typically do not signal a need for any corrective action or technical support. Table 127 Event Log messages for normal events Event Message Meaning Acquired GPS Sync Pulse. Module has acquired GPS sync signal. FPGA Features Type of encryption. FPGA Version FPGA (JBC) version in the module. GPS Date/Time Set Module is now on GPS time. Reboot from Webpage Module was rebooted from management interface. Software Boot Version Boot version in the module. Software Version The software release and authentication method for the unit. System Log Cleared Event log was manually cleared. Page 3-37 Chapter 3: Operation System information Viewing the Network Interface In any module, the LAN1 Network Interface section of this tab displays the defined Internet Protocol scheme for the Ethernet interface to the module. In SM/BHS devices, this page also provides an RF Public Network Interface section, which displays the Internet Protocol scheme defined for network access through the master device (AP/BHM). Figure 85 Network Interface tab of the AP Figure 86 Network Interface tab of the SM Viewing the Layer 2 Neighbors In the Layer 2 Neighbors tab, a module reports any device from which it has received a message in Link Layer Discovery Protocol within the previous two minutes. Given the frequency of LLDP messaging, this means that the connected device will appear in this tab 30 seconds after it is booted and remain until two minutes after its shutdown. Figure 87 Layer 2 Neighbors page Page 3-38 Chapter 3: Operation System statistics System statistics This section describes how to use the system statistics pages to manage the performance of the PMP/PTP 450 Platform Family link. Viewing the Scheduler statistics The Statistics > Scheduler page is applicable for all modules (AP/SM/BHM/BHS) and the parameters are displayed as shown below:

Table 128 Scheduler tab attributes Attribute Meaning Page 3-39 Chapter 3: Operation Transmit Unicast Data Count Transmit Broadcast Data Count Transmit Multicast Data Count Receive Unicast Data Count Receive Broadcast Data Count Receive Multicast Data Count Transmit Control Count Receive Control Count In Sync Count System statistics Total amount of unicast packets transmitted from the radio Total amount of broadcast packets transmitted from the radio Total amount of multicast packets transmitted by the radio Total amount of unicast packets received by the radio Total amount of broadcast packets received by the radio Total amount of multicast packets received by the radio Amount of radio control type messages transmitted (registration requests and grants, etc.) Amount of radio control type messages received (registration requests and grants, etc.) Number of times the radio has acquired sync. When GPS synchronization is used it is number of times GPS sync acquired. For the SM, it is the number of times the SM successfully obtained sync with an AP. Out of Sync Count Number of times the radio lost same sync lock Overrun Count Number of times FPGA frame has overrun its TX Frame Underrun Count Number of times FPGAs TX Frame aborted prematurely Receive Corrupt Data Count Number of times a corrupt packet has been received at the FPGA. Receive Corrupt Control Data Count Number of times a corrupt control data packet has been received at the FPGA. Receive Bad Broadcast Control Count Rcv LT Start Rcv LT Start HS Rcv LT Result Number of times the radio has received an invalid control message via broadcast (SM only). Number of Link Test Start messages received. A remote radio has requested that this radio start a link test to it. Number of Link Test Start Handshake messages received. This radio requested that a remote radio start a link test and the remote radio has sent a handshake back acknowledging the start. This radio received Link Test results from the remote radio under test. When this radio initiates a link test, the remote radio will send its results to this radio for display. Page 3-40 Chapter 3: Operation Xmt LT Result System statistics This radio transmitted its link test results to the remote radio under test. When the remote radio initiates a link test, this radio must send its results to the remote radio for display there. Frame Too Big This statistic indicates the number of packets received and processed by the radios which were greater than max packet size 1700 bytes. Bad Acknowledgment This statistic indicates the number of packets received as bad acknowledgment. It is for engineering use only. Bad Fragment This statistic indicates number of fragments tagged internally as bad. It is for engineering use only. VC Clear Error Count This statistic indicates number of times VC clear failed. Rx No Buffer Count Currently unused Scheduler Error This error is incremented when the scheduler cannot send or get scheduled to send a packet. It is also called as VC Error. Transmit Ring Error This is a state that records when Canopys MAC Transmit Ring Error. One or more of these will cause the session to drop and be re-established. That static should be zero. If you are seeing this statistic increment, please contact Cambium support. TDD Slips TDD Slips indicate that the 450m AP processer is heavily loaded and could lead to buffer discards. Viewing list of Registration Failures statistics SM Registration Failures page of AP The SM Registration Failures tab identifies SMs that have recently attempted and failed to register to this AP. With its time stamps, these instances may suggest that a new or transient source of interference exists. Table 129 SM Registration Failures page attributes - AP Attribute Meaning Status 17 Flag 0 No response was received from the AAA server and hence SM is trying to send a session request again. Page 3-41 Chapter 3: Operation BHS Registration Failures page of BHM Table 130 BHS Registration Failures page attributes - BHM System statistics Attribute Meaning Status 17 Flag 0 No response was received from the AAA server and hence BHS is trying to send a session request again. There is a list of flags from 0 to 20 as shown in Table 131 and the Flags can be ignored. Table 131 Flags status Flag Meaning Flag Meaning 0 1 2 3 4 5 6 7 8 9 Normal Out of Range No Luids BH ReRange Auth Fail Encrypt Fail Power Adjust No VCs Reserve VC Fail Activate VC Fail 10 Hi VC Setup Fail 11 12 13 14 15 16 17 18 19 20

-

AP Lite Limit Reached Only Ver 9.5+ Allowed Temporary Data VC for AAA AAA Authentication Failure Registration Grant Reject Blank AAA Session Retry AAA Reauth Failure RegReq at zero power RegReq no time ref

-

Page 3-42 Chapter 3: Operation System statistics Interpreting Bridging Table statistics If NAT (network address translation) is not active on the SM/BHS, then the Bridging Table page provides the MAC address of all devices that are attached to registered SMs/BHS (identified by LUIDs). The SM/BHS management MAC addresses are also added in bridge table upon SMs/BHS registration. These entries will be remove automically from the table once SMs/BHS is de-registered. This alleviates the arp cache > bridge cache timeout problems. The bridging table allows data to be sent to the correct module as follows:

For the AP/BHM, the uplink is from RF to Ethernet. Thus, when a packet arrives in the RF interface to the AP/BHM, the AP/BHM reads the MAC address from the inbound packet and creates a bridging table entry of the source MAC address on the other end of the RF interface. For the SM/BHS, the uplink is from Ethernet to RF. Thus, when a packet arrives in the Ethernet interface to one of these modules, the module reads the MAC address from the inbound packet and creates a bridging table entry of the source MAC address on the other end of the Ethernet interface. Figure 88 Bridging Table page The Bridging Table supports up to 4096 entries. Interpreting Translation Table statistics When Translation Bridging is enabled in the AP, each SM keeps a table mapping MAC addresses of devices attached to the AP to IP addresses, as otherwise the mapping of end-user MAC addresses to IP addresses is lost. (When Translation Bridging is enabled, an AP modifies all uplink traffic originating from registered SMs such that the source MAC address of every packet is changed to that of the SM which bridged the packet in the uplink direction.) Page 3-43 Chapter 3: Operation Figure 89 Translation Table page of SM System statistics Interpreting Ethernet statistics The Statistics > Ethernet page reports TCP throughput and error information for the Ethernet connection of the module. This page is applicable for all modules (AP/SM/BHM/BHS). The Ethernet page displays the following fields. Table 132 Ethernet tab attributes Page 3-44 Chapter 3: Operation Attribute Meaning System statistics Ethernet Link Detected 1 indicates that an Ethernet link is established to the radio, 0 indicates that no Ethernet link is established Ethernet Link Lost This field indicates a count of how many times the Ethernet link was lost. Undersized Toss Count inoctets Count This field indicates the number of packets that were too small to process and hence discarded. This field displays how many octets were received on the interface, including those that deliver framing information. inucastpkts Count This field displays how many inbound subnetwork-unicast packets were delivered to a higher-layer protocol. Innucastpkts Count This field displays how many inbound non-unicast (subnetwork-broadcast or subnetwork-multicast) packets were delivered to a higher-layer protocol. indiscards Count This field displays how many inbound packets were discarded without errors that would have prevented their delivery to a higher-layer protocol. (Some of these packets may have been discarded to increase buffer space.) inerrors Count This field displays how many inbound packets contained errors that prevented their delivery to a higher-layer protocol. inunknownprotos Count This field displays how many inbound packets were discarded because of an unknown or unsupported protocol. outoctets Count This field displays how many octets were transmitted out of the interface, including those that deliver framing information. outucastpkts Count outnucastpkts Count This field displays how many packets for which the higher-level protocols requested transmission to a subnetwork-unicast address. The number includes those that were discarded or not sent. This field displays how many packets for which the higher-level protocols requested transmission to a non-unicast (subnetwork-broadcast or subnetwork-multicast) address. The number includes those that were discarded or not sent. outdiscards Count This field displays how many outbound packets were discarded without errors that would have prevented their transmission. (Some of these packets may have been discarded to increase buffer space.) outerrrors Count This field displays how many outbound packets contained errors that prevented their transmission. RxBabErr TxHbErr EthBusErr This field displays how many receiver babble errors occurred. This field displays how many transmit heartbeat errors have occurred. This field displays how many Ethernet bus errors occurred on the Ethernet controller. Page 3-45 Chapter 3: Operation System statistics CRCError This field displays how many CRC errors occurred on the Ethernet controller. RcvFifoNoBuf This field displays the number of times no FIFO buffer space was able to be allocated. Note:

PMP 450 AP running in Gigabit Ethernet Mode displays error RcfFifoNoBuf which indicates packet loss. For 450 AP platforms, if ethernet auto-negotation is set to Gigabit, then it is a known limitation that RcfFifoNoBuf error will be seen. This issue is not seen if autonegotation is set to 100Mbps or lower, and the issue is not seen on 450i or 450m AP's. RxOverrun Late Collision This field displays how many receiver overrun errors occurred on the Ethernet controller. This field displays how many late collisions occurred on the Ethernet controller. A normal collision occurs during the first 512 bits of the frame transmission. A collision that occurs after the first 512 bits is considered a late collision. Caution A late collision is a serious network problem because the frame being transmitted is discarded. A late collision is most commonly caused by a mismatch between duplex configurations at the ends of a link segment. RetransLimitExp This field displays how many times the retransmit limit has expired. TxUnderrun CarSenseLost No Carrier This field displays how many transmission-underrun errors occurred on the Ethernet controller. This field displays how many carrier sense lost errors occurred on the Ethernet controller. This field displays how many no carrier errors occurred on the Ethernet controller. Page 3-46 Chapter 3: Operation System statistics Interpreting RF Control Block statistics The Statistics > Radio page is applicable for all module (AP/SM/BHM/BHS). The Radio page of the Statistics page displays the following fields. Table 133 Radio (Statistics) page attributes RF Control Block Attribute Meaning inoctets Count This field displays how many octets were received on the interface, including those that deliver framing information. inucastpkts Count This field displays how many inbound subnetwork-unicast packets were delivered to a higher-layer protocol. Innucastpkts Count This field displays how many inbound non-unicast (subnetwork-broadcast or subnetwork-multicast) packets were delivered to a higher-layer protocol. indiscards Count This field displays how many inbound packets were discarded without errors that would have prevented their delivery to a higher-layer protocol. This stat is pegged whenever corrupt data is received by software or whenever the RF Software Bridge queue is full. Corrupt data is a very unusual event because all packets are CRC checked by hardware before being passed into software. The likely case for indiscards is if the RF bridge queue is full. If this is the case the radio is most likely PPS limited due to excessive small packet traffic or a problem at the Ethernet interface. If there is a problem at the Ethernet interface there is likely to be discards at the Ethernet as well. inerrors Count This field displays how many inbound packets contained errors that prevented their delivery to a higher-layer protocol. inunknownprotos Count This field displays how many inbound packets were discarded because of an unknown or unsupported protocol. outoctets Count This field displays how many octets were transmitted out of the interface, including those that deliver framing information. Page 3-47 Chapter 3: Operation System statistics outucastpkts Count outnucastpkts Count This field displays how many packets for which the higher-level protocols requested transmission to a subnetwork-unicast address. The number includes those that were discarded or not sent. This field displays how many packets for which the higher-level protocols requested transmission to a non-unicast (subnetwork-broadcast or subnetwork-multicast) address. The number includes those that were discarded or not sent. outdiscards Count This field displays how many outbound packets were discarded without errors that would have prevented their transmission. (Some of these packets may have been discarded to increase buffer space.) outerrrors Count This field displays how many outbound packets contained errors that prevented their transmission. Page 3-48 Chapter 3: Operation Interpreting Sounding statistics for AP System statistics In the 450m AP GUI, sounding statistics can be found under Statistics > Sounding Statistics. Table 134 Sounding Statistics - 450m AP page attributes Attribute Subscriber LUID Meaning This field displays the MAC address and Site Name of the SM/BHS. As each SM or BHS registers to the AP/BHM. This field displays the LUID (logical unit ID) of the SM/BHS. As each SM or BHS registers to the AP/BHM, the system assigns an LUID of 2 or a higher unique number to the SM/BHS. If a SM/BHS loses registration with the AP/BHS and then regains registration, the SM/BHS will retain the same LUID. Spatial Frequency This field displays the spatial frequency value of the LUID or SM. Values 0 to 1023 are valid and value 2048 is considered as invalid. Azimuth This field displays the Azimuth range in degrees corresponding to the spatial frequencies of the bin. The zero-degree azimuth is boresight. Note Some SF ranges correspond to multiple azimuth ranges. This is because for some spatial frequencies the AP generates beams in multiple azimuth directions. The SM can be physically located in any of the azimuth ranges. Downlink - Sounding State Different types of Sounding states are:

UNKNOWN: SM has recently registered to the AP but not registered with the channel manager yet. NEW: SM has been registered with the channel manager and will soon transition to ASSESSING. ASSESSING: AP will instruct SM to take the channel measurements. Channel estimates and spatial frequencies will be calculated. TRACKING: Valid measurements resulted in good channel estimates and spatial frequency. This SM can now be used for MU-MIMO. Page 3-49 Chapter 3: Operation System statistics INVALID: Inconsistent measurements resulting in no channel estimate or spatial frequency. This SM cannot be used for MU-MIMO and it will ultimately be re-assessed. NOT ELIGIBLE: Due to poor RF link conditions, the RF link as rate adapted down to SU-MIMO transmissions. Downlink - MU-MIMO Rate This field indicates the modulation rate used for symbols where this particular LUID is MU-MIMO scheduled by grouping it in the same slot with other LUIDs. Uplink - Sounding State This field indicates the status of uplink sounding. Uplink - MU-MIMO Rate This field indicates the modulation rate used for symbols where the MU-MIMO groupable data channels are MU-MIMO scheduled by grouping it in the same slot with other MU-MIMO groupable data channels from other SM's. Page 3-50 Chapter 3: Operation Interpreting VLAN statistics System statistics The Statistics > VLAN page provides a list of the most recent packets that were filtered because of VLAN membership violations. It is applicable for all modules (AP/SM/BHM/BHS). Table 135 VLAN page attributes Attribute Unknown Only Tagged Ingress Local Ingress Egress Local Egress Meaning This must not occur. Contact Technical Support. The packet was filtered because the configuration is set to accept only packets that have an 802.1Q header and this packet did not. When the packet entered through the wired Ethernet interface, the packet was filtered because it indicated an incorrect VLAN membership. When the packet was received from the local TCP/IP stack, the packet was filtered because it indicated an incorrect VLAN membership. This must not occur. Contact Technical Support. When the packet attempted to leave through the wired Ethernet interface, the packet was filtered because it indicated an incorrect VLAN membership. When the packet attempted to reach the local TCP/IP stack, the packet was filtered because it indicated an incorrect VLAN membership. Page 3-51 Chapter 3: Operation System statistics Interpreting Data Channels statistics The Statistics > Data Channels page displays information about data channels used in data communications. This page is applicable for all modules (AP/SM/BHM/BHS). The Data VC tab displays the fields as explained in Table 136. Table 136 Data Channel page attributes Attribute Subscriber LUID Meaning This field displays the MAC address and Site Name of the SM/BHS. This field displays the LUID (logical unit ID) of the SM/BHS. As each SM or BHS registers to the AP/BHM, the system assigns an LUID of 2 or a higher unique number to the SM/BHS. If a SM/BHS loses registration with the AP/BHS and then regains registration, the SM/BHS will retain the same LUID. Page 3-52 Chapter 3: Operation System statistics Note Both the LUID and the MAC are hot links to open the interface to the SM/BHS. In some instances, depending on network activity and network design, this route to the interface yields a blank web page. If this occurs, refresh your browser view. Channel Priority This field displays the channel priority for the virtual channel. The values supported are Low, Medium, High, and Ultra High. Inbound Statistics, octets This field displays how many octets were received on the interface, including those that deliver framing information. Inbound Statistics, ucastpkts This field displays how many inbound subnetwork-unicast packets were delivered to a higher-layer protocol. Inbound Statistics, nucastpkts This field displays how many inbound non-unicast (subnetwork-broadcast or subnetwork-multicast) packets were delivered to a higher-layer protocol. Inbound Statistics, discards This field displays how many inbound packets were discarded without errors that would have prevented their delivery to a higher-layer protocol. Inbound discard statistics are incremented similar to the indiscards stat on the RF control block stats page. The sum of all data VC indiscards must be close to the RF control block in discards. If indiscards are evenly distributed across SMs, then the radio is PPS limited due to either excessive small packet transmissions, or a problem at the Ethernet link. If indiscards are contained to one or a few SMs, then there is likely a problem at or underneath the SM which is incrementing the count. Outbound Statistics, octets This field displays how many octets were transmitted out of the interface, including those that deliver framing information. Outbound Statistics, ucastpkts This field displays how many packets for which the higher-level protocols requested transmission to a subnetwork-unicast address. The number includes those that were discarded or not sent. Outbound Statistics, nucastpkts Outbound Statistics, discards This field displays how many packets for which the higher-level protocols requested transmission to a non-unicast (subnetwork-broadcast or subnetwork-multicast) address. The number includes those that were discarded or not sent. This field displays how many outbound packets were discarded without errors that would have prevented their transmission. Outbound discard statistics are incremented if a VC is not active when a packet is ready to send. This is a rare condition. Outbound Statistics, errors This field displays how many outbound packets contained errors that prevented their transmission. Page 3-53 Chapter 3: Operation System statistics Queue Overflow This is a count of packets that were discarded because the queue for the VC was already full. If Queue Overflows are being seen across most or all SMs, then there is either an interferer local to the AP or the APs RF link is at capacity. If Queue Overflows are being seen at one or only a few SMs, then it is likely that there is a problem with those specific links whether it is insufficient signal strength, interferer, or a problem with the actual SM hardware. High Priority Queue This is a count of packets that were received on high priority queue. Fragments Modulation - Receive Fragments Modulation QPSK 16-QAM 64-QAM 256-QAM Retransmitted Fragments This field displays how many inbound fragments were received via the QPSK modulation scheme. This field displays how many inbound fragments were received via the 16-

QAM modulation scheme. This field displays how many inbound fragments were received via the 64-

QAM modulation scheme. This field displays how many inbound fragments were received via the 256-

QAM modulation scheme. This field displays how many outbound fragments were retransmitted. Page 3-54 Chapter 3: Operation Interpreting Proportional Scheduler The Statistics > Proportional Scheduler page displays information:

Table 137 MIR/Burst page attributes for AP System statistics Attribute Subscriber LUID Meaning See Table 120 on page 3-24. See Table 120 on page 3-24. Lock Modulation This field displays the Lock Modulation mode of all registered SMs. Modulation Weight The database configured Lock Modulation value if lock modulation is set to Enable below threshold or Enabled. This field displays the weight of each registered SM. For more information about Weight, See Table 84 on page 1-250. Downlink Statistics This field displays the Dowlink statistics of every registered SM. Uplink Statistics This field displays the Uplink statistics of every registered SM. Rate Plan This field displays the rate plan associated with each SM. Current Modulation The currently operating modulation of this SM. Slots Percentage This field displays the percentage of slot used by each SM. Guaranteed minimum throughput Guaranteed minimum throughput based on the SM's Rate Plan configuration, it's current modulation rate, and any Lock Modulation settings. For 450m AP's the maximum possible Throughput shown here assumes all SUMIMO scheduling. MUMIMO scheduling will result in higher TPUT. Sustained Data Rate This field displays the preset rate limit of data transfer for every SM. Interpreting MIR/Burst statistics The Statistics > MIR/Burst page displays information about MIR/Burst. This page is applicable for all modules (AP/SM). The MIR/Burst tab displays the fields as explained in Table 138 and Table 139. Page 3-55 Chapter 3: Operation Table 138 MIR/Burst page attributes for AP System statistics Attribute Subscriber Meaning This field displays the LUID (logical unit ID), MAC address and Site Name of the SM/BHS. As each SM or BHS registers to the AP/BHM, the system assigns an LUID of 2 or a higher unique number to the SM/BHS. As of release 15.2, if an SM/BHS loses registration with the AP/BHM and then regains registration, the SM/BHS retains the same LUID. Current Downlink Bucket Size This field displays the number of bits in the bucket to be potentially consumed at above-MIR rates, up to Max Burst MIR rate. Downlink MIR This field displays the active configured MIR rate per second. This is the rate that the bucket is filled with bits. Downlink MIR Per 500ms Interval This field displays the rate that the bucket is filled with bits at every 500 ms interval. Downlink Max Bucket Size This field displays the configured maximum bucket size, which is the maximum number of bits that can be in the bucket. The bucket fills at MIR rate and can hold this number of bits, which is a configuration value. Current Max Burst Bucket Size If Max Burst is enabled, there is a secondary bucket that controls the maximum rate of bit consumption. If Max Burst is not enabled (which means not limited), this will be 0 as the bucket is not used. Downlink Max Burst MIR This field displays the configured value of the Max Burst rate. This is the maximum rate at which bits can be consumed above MIR. Once excess (>

MIR) bits have been consumed, the link will be throttled to MIR. Downlink Max Burst MIR Per 500ms Interval This field displays the configured value of the Max Burst rate at every 500 ms interval. Uplink MIR This field displays the active configured MIR rate per second in the SM. Uplink Max Bucket Size This field displays the configured maximum bucket size of the SM, which is the maximum number of bits that can be in the bucket. The bucket fills at MIR rate and can hold this number of bits, which is a configuration value. Uplink Max Burst MIR This field displays the configured value of the MaxBurst rate of the SM. This is the maximum rate at which bits can be consumed above MIR. Once excess

(> MIR) bits have been consumed, the link will be throttled to MIR. Page 3-56 Chapter 3: Operation Table 139 MIR/Burst page attributes for SM Attribute Meaning System statistics Current Uplink Bucket Size This field displays the number of bits in the bucket to be potentially consumed at above-MIR rates, up to Max Burst MIR rate. Uplink MIR This field displays the active MIR rate per second. This is the rate that the bucket is filled with bits. Uplink MIR Per 100ms Interval This field displays the rate that the bucket is filled with bits at every 100 ms interval. Uplink Max Bucket Size Current Max Burst Bucket Size Uplink Max Burst MIR This field displays the maximum bucket size, which is the maximum number of bits that can be in the bucket. The bucket fills at MIR rate and can hold this number of bits, which is a configuration value. If Max Burst is enabled, there is a secondary bucket that controls the maximum rate of bit consumption. If Max Burst is not enabled (which means not limited), this will be 0 as the bucket is not used. This field displays the configured value of the Max Burst rate. This is the maximum rate at which bits can be consumed above MIR. Once excess (>

MIR) bits have been consumed, the link will be throttled to MIR. Uplink Max Burst MIR per 100ms Interval This field displays the configured value of the Max Burst rate at every 100 ms interval. Uplink Broadcast Credit This field displays the broadcast credit. Uplink Broadcast MIR This field displays the broadcast MIR rate per second. Uplink Broadcast MIR Type Downlink MIR This field displays the type of the broadcast MIR. This field displays the active configured MIR rate per second. This is the rate that the bucket is filled with bits. Downlink Max Bucket Size This field displays the configured maximum bucket size, which is the maximum number of bits that can be in the bucket. The bucket fills at MIR rate and can hold this number of bits, which is a configuration value. Downlink Max Burst MIR This field displays the configured value of the Max Burst rate. This is the maximum rate at which bits can be consumed above MIR. Once excess (>

MIR) bits have been consumed, the link will be throttled to MIR. Page 3-57 Chapter 3: Operation System statistics Interpreting Throughput statistics The 450 Platform Family has a Statistics > Throughput page which shows historical information about sector or backhaul throughput and packet discards. This page is applicable for AP and BHM modules. This information can be useful to identify an overloaded sector or heavy bandwidth users. This page also shows the user throughput in terms of data rate (kbps) and packet rate (packets per second, or PPS), as well as the average packet size during the sample period. Operators may set the AP/BHM to send an SNMP trap when it detects an RF overload condition based on a configurable threshold. The following configuration parameters are available on the Throughput tab GUI pane and a radio reboot is not required when configuring these parameters:

Table 140 RF overload Configuration attributes AP/BHM Attribute Throughput Monitoring Meaning This enables or disables the monitoring of sector throughput and packet discards. This parameter is disabled by default. SNMP Trap on RF Overload This enables or disables the sending of an SNMP trap when an AP/BHM overload condition is reached (based on Downlink RF Overload Threshold). Downlink RF Overload Threshold This parameter determines the overload threshold in percent of packets discarded that triggers the generation of an SNMP trap. Downlink RF Link Status Time Period Length Time Period Ending This field displays the status of the capacity of the RF link. These two configuration parameters determine what set of collection samples to show on the GUI display. The Time Period Length can be set from one to three hours. Time Period Ending allows the operator to set the end time for the set of collection samples to display. Following configuration settings are three tables that display the statistics that are collected. Page 3-58 Chapter 3: Operation Board Performance statistics System statistics This table contains a row that corresponds to each 1 minute statistics collection interval. Each row contains the following data aggregated for the entire AP/BHM:

Ethernet Throughput - Statistics collected at the Ethernet port:

o kbps in average throughput over the collection interval in Kbps into the AP/BHM on the Ethernet Interface o kbps out average throughput over the collection interval in Kbps out of the AP/BHM on the Ethernet Interface o PPS in average packets per second over the collection interval into the AP/BHM on the Ethernet Interface o PPS out average packets per second over the collection interval out of the AP/BHM on the Ethernet Interface RF Throughput - Statistics collected at the RF Interface:

o kbps in average throughput over the collection interval in Kbps into the AP/BHM on the RF Interface o kbps out average throughput over the collection interval in Kbps out of the AP/BHM on the RF Interface o PPS in average packets per second over the collection interval into the AP/BHM on the RF Interface o PPS out average packets per second over the collection interval out of the AP/BHM on the RF Interface Aggregate Through Board Sum of bidirectional data transferred through (not originating or terminating at) the AP/BHM:

o kbps average bidirectional throughput over the collection interval in Kbps o PPS average bidirectional packets per second over the collection interval o Ave Pkt Size Average Packet size over the collection interval of bidirectional data transferred Board Throughput statistics This table contains a row that corresponds to each one minute statistics collection interval. This table may be used to determine if there are problems with any of the interfaces. For example, if the Ethernet in packets is much higher than the RF out packets it could indicate a denial of service (DoS) attack on the AP/BHM. Each row contains the following data aggregated for the entire AP/BHM:

Ethernet Statistics - Statistics collected at the Ethernet port:

o inOctets Number of octets (bytes) received by the AP/BHM at the Ethernet Interface over the collection interval o outOctets Number of octets (bytes) sent by the AP/BHM at the Ethernet Interface over the collection interval inPkts Number of packets received by the AP/BHM at the Ethernet Interface over the collection interval o Page 3-59 Chapter 3: Operation System statistics o outPkts Number of packets sent by the AP/BHM at the Ethernet Interface over the collection interval o Discards (in/out) Number of packets that had to be discarded by the AP/BHM at the respective Ethernet Interface Queue RF Statistics - Statistics collected at the RF Interface:

o inOctets Number of octets (bytes) received by the AP/BHM at the RF Interface over the collection interval o outOctets Number of octets (bytes) sent by the AP/BHM at the RF Interface over the collection interval inPkts Number of packets received by the AP/BHM at the RF Interface over the collection interval o o outPkts Number of packets sent by the AP/BHM at the RF Interface over the collection interval o Discards (in/out) Number of packets that had to be discarded by the AP/BHM at the respective RF Interface Queue during the collection interval o Discards % (in/out) Percent of the total packets received / transmitted that had to be discarded during the collection interval LUID RF Throughput statistics This table contains a row that corresponds to each active LUID served by the AP/BHM. Note that an LUID may be assigned 1 or 2 VCs. If the LUID is assigned 2 VCs, then the data in the table is the sum of the activity for both VCs. This table may be used to determine which LUIDs are experiencing overload so that corrective action can be taken (i.e. fixing a poor RF link or moving a heavily loaded link to a less congested AP/BHM). Each row contains counters and statistics related to the RF Interface that are updated once per minute:

Inbound Statistics - Statistics collected at the RF Interface for the Uplink:

o octets Number of octets (bytes) received by the AP/BHM at the RF Interface for this LUID over the collection interval o pkts Number of packets received by the AP/BHM at the RF Interface for this LUID over the collection interval o Ave Pkt Size Average size of the packets received by the AP/BHM at the RF Interface for this LUID over the collection interval o discards Number of packets received by the AP/BHM at the RF Interface for this LUID over the collection interval that had to be discarded because the RF In Queue was full o discards % Percent of the total packets received by the AP/BHM at the RF Interface for this LUID over the collection interval that had to be discarded because the RF In Queue was full Outbound Statistics - Statistics collected at the RF Interface for the Downlink:

o octets Number of octets (bytes) transmitted by the AP/BHM at the RF Interface for this LUID over the collection interval o pkts Number of packets transmitted by the AP/BHM at the RF Interface for this LUID over the collection interval Page 3-60 Chapter 3: Operation System statistics o Ave Pkt Size Average size of the packets transmitted by the AP/BHM at the RF Interface for this LUID over the collection interval o discards Number of packets to be transmitted by the AP/BHM at the RF Interface for this LUID over the collection interval that had to be discarded because the RF Out Queue was full o discards % Percent of the total packets to be transmitted by the AP/BHM at the RF Interface for this LUID over the collection interval that had to be discarded because the RF Out Queue was full. Interpreting Overload statistics The Statistics > Overload page displays statistics on packet overload and resultant packet discards. Unlike the other fields, the Total Packets Overload Count is expressed in only this page. It is not a count of how many packets have been lost, but rather of how many discard events (packet loss bursts) have been detected due to overload condition. This statistics page is applicable for all modules (AP/SM/BHM/BHS) and explained in Table 141. Table 141 Overload page attributes AP/SM/BHM/BHS Attribute Meaning Total Packets Overload Count Ethernet In Discards This field represents the sum of all RF and Ethernet in/out discards. This field represents the number of packets tossed due to the Ethernet queue being full. If a climb in this stat accompanies a climb in RF Out Discards stat, then most likely the board is at RF capacity either due to traffic exceeding the RF pipe, or interference temporarily limiting the RF throughput. If this stat climbs without the RF Out Discards stat climbing, then the radio is most likely PPS limited. Page 3-61 Chapter 3: Operation System statistics Ethernet Out Discards This field represents the number of packets tossed due to an Ethernet out RF In Discards RF Out Discards overload. This stat must not climb in normal operation because the Ethernet link is much higher capacity than the RF link. If this stat is incrementing, then either the Ethernet link is established at a low speed (i.e. 10Mbps half duplex), or there is a problem with cabling/Ethernet hardware. This field indicates the number of packets tossed due to no resources available within the radio to process them. This stat also must not be increasing because the system is designed to shed packets on the RF Out interface. If this stat is incrementing the board, it is most likely congested due to high PPS rate in combination with an Ethernet Out problem, which limits packet flow off the device. This field indicates the number of packets tossed due to RF link at capacity. This stat will increase whenever the RF link is at capacity. When the internal FPGA RF input queue overflows, this stat is incremented. If this stat is seen to be incrementing at the AP, then the sector is congested. If seen at the SM, the number of Contention Slots must be looked at to ensure that enough Contention Slots are allocated to allow for bandwidth requests to be seen at the AP. Page 3-62 Chapter 3: Operation Note 450m Overload:

System statistics The 450m Series AP is designed to handle high load in terms of high throughput and high PPS. In terms of throughput, 450m is designed to achieve 3x or more throughput improvement over 450 and 450i Series products. In terms of packets per second (PPS), 450m is designed to handle up to 100k PPS. Overload occurs when the offered load exceeds the above limits. When overload occurs, 450m will start discarding packets and TCP throughput will degrade due to packet loss. Its worth noting that Frame Utilization statistics (Statistics > Frame Utilization tab:

Frame Utilization: Downlink and Uplink) are not necessarily indicative of overload condition. They show how much the TDD frame is utilized. High frame utilization depends on:

High traffic during busy periods: those statistics will be close to 100% and almost all slots will be utilized. In this case if the Overload statistics show that packets are discarded then this is an indication of overload condition. High percentage of VCs with low modulation with moderate traffic. Those VCs will require more slots to service them (due to low modulation) and the frame utilization will be high. In this case the TDD frame is fully utilized but the system is at low capacity and is not in an overload condition. 450m has higher PPS than 450 and 450i and supports higher throughput through spatial multiplexing, therefore when a 450m replaces an overloaded 450 or 450i AP the 450m will not be overloaded under the same conditions but the frame utilization may still show close to 100%; this should not alarm the customer. The overload statistics shall be monitored on 450m to see if it is overloaded or not. Interpreting DHCP Relay statistics The Statistics > DHCP Relay page displays requests and replies received, relayed and discarded when the AP is configured as a DHCP relay. Typically, in a working DHCP relay configuration a one-to-one ratio is established between requests and replies that are received and relayed. This statistics page is only applicable for PMP (AP and SM modules) and it is explained in Table 142. Page 3-63 Chapter 3: Operation Table 142 DHCP Relay page attributes AP/SM System statistics Attribute Meaning Requests Received This field represents the number of DHCP relay requests received by the AP. Requests Relayed This field represents the number of DHCP relay requests relayed by the AP. Requests Discarded This field represents the number of DHCP relay requests discarded by the AP due to errors in the request. Replies Received This field represents the number of DHCP relay replies received by the AP. Replies Relayed This field represents the number of DHCP relay replies relayed by the AP. Replies Discarded This field represents the number of DHCP relay replies discarded by the AP due to errors in the reply. Untrusted Message Discards This field indicates messages that were discarded because the message already contained Option 82 information with no Relay Agent specified. Max Hop Exceeded Discards This field indicates messages that have been relayed too many times, exceeding the max hop count (16). Invalid Relay Agent Address Discards This field indicates messages that have been discarded because the message relay agent address is already in place (relay agent address does not equal address of the AP). This field indicates DHCP messages too large to fit Option 82 data. These messages are sent on without Option 82 information. Relay Info Exceeding Max Message Size

(DHCP message relayed without Option 82) Page 3-64 Chapter 3: Operation System statistics Subscriber See Table 120 on page 3-24. See Table 120 on page 3-24. This field displays the option 82 data of the SM in binary and ASCII formats. LUID Circuit ID Remote ID Vendor Specific ID Interpreting Filter statistics The Statistics > Filter page displays statistics on packets that have been filtered (dropped) due to the filters set on the Protocol Filtering page. The filter page of SM is explained in Table 143. Table 143 Filter page attributes - SM Attribute PPPoE Count All IPv4 Count Meaning Number of PPPoE packets filtered. Number of IPv4 packets filtered. All Other IPv4 Count Any IPv4 message that was not SMB, SNMP, Bootp, Multicast or one of the user defined filters, that was filtered out. SMB Count SNMP Count Number of IPv4 Server Message Block (file sharing) packets filtered. Number of IPv4 SNMP packets filtered. Bootp Client Count Total number of IPv4 DHCP requests filtered. Bootp Server Count Total number of IPv4 DHCP replies filtered. IPv4 Multicast Count Number of IPv4 Multicast messages filtered. All IPv6 Count Number of IPv6 messages filtered. Page 3-65 Chapter 3: Operation System statistics All Other IPv6 Count Any IPv6 message that was not SMB, SNMP, Bootp, Multicast or one of the user defined filters, that was filtered out. IPv6 SMB Count Number of IPv6 Server Message Block (file sharing) packets filtered IPv6 SNMP Count Number of IPv6 SNMP messages filtered IPv6 Bootp Client Count Total number of IPv6 DHCP replies filtered IPv6 Bootp Server Count Total number of IPv6 DHCP replies filtered IPv6 Multicast Count Number of IPv6 Multicast messages filtered ARP Count Total number of ARP packets filtered. All other Count The count of any messages that did not fit above that were filtered out User Defined Port1 Count Number of packets defined by the user port1 that were filtered. User Defined Port2 Count Number of packets defined by the user port2 that were filtered. User Defined Port3 Count Number of packets defined by the user port3 that were filtered. Viewing ARP statistics The Statistics > ARP page in a SM module correlated the IP address of the Ethernet-connected device to its MAC address and provides data about the connection. Figure 90 ARP page of the SM Viewing NAT statistics When NAT is enabled on a SM, statistics are kept on the Public and Private (WAN and LAN) sides of the NAT and displayed on the Statistics > NAT Stats page. The NAT page of SM is explained in Table 144. Page 3-66 Chapter 3: Operation Table 144 NAT page attributes - SM System statistics Attribute Meaning Private NAT Statistics, Packet In Count This field represents the number of packets received on the SMs LAN/Ethernet interface Private NAT Statistics, Packet Out Count This field represents the number of packets sent from the SMs LAN/Ethernet interface Private NAT Statistics, Packet Out Toss Count This field represents the number of packets that we not sent from the SMs LAN/Ethernet interface due to addressing issues. Private NAT Statistics, Out of Resources Count This field represents the number of times the NAT table for the SMs LAN/Ethernet interfaces has been filled. Private NAT Statistics, Failed Hash Insert Count This field represents the number of times that the device failed to insert an address binding into the NAT hash table. Public NAT Statistics, Packet In Count This field represents the number of packets received on the SMs WAN/wireless interface Public NAT Statistics, Packet Out Count This field represents the number of packets sent from the SMs WAN/wireless interface Public NAT Statistics, Out of Resources Count This field represents the number of packets that we not sent from the SMs WAN/wireless interface due to addressing issues. Public NAT Statistics, Failed Hash Insert Count This field represents the number of times the NAT table for the SMs WAN/wireless interfaces has been filled. Page 3-67 Chapter 3: Operation System statistics Viewing NAT DHCP Statistics The Statistics > NAT DHCP page displays NAT enabled DHCP client statistics. This is statistics page is applicable for SM only. When NAT is enabled on a SM with DHCP client (DHCP selected as the Connection Type of the WAN interface) and/or DHCP Server, statistics are kept for packets transmitted, received and tossed, as well as a table of lease information for the DHCP server (Assigned IP Address, Hardware Address and Lease Remained/State). Table 145 NAT DHCP Statistics page attributes - SM Attribute Meaning PktXmt Count Represents the number of DHCP packets transmitted from the client PktRcv Count This field represents the number of DHCP packets received by the client PktToss ARPUnresolved Overflow Count This field represents the number of packets tossed due to failed attempts to resolve an IP address into a physical MAC address PktToss Unsupported MsgType Count This field represents the number of packets tossed due to the receipt of an unsupported message type (cannot be interpreted by DHCP client) PktToss XID Mismatch Count The field represents the number of packets that were tossed due to a transaction ID mismatch PktToss NoSID Count This field represents the number of packets that were tossed due to lack of a DHCP session ID PktToss SID Mismatch Count Represents the number of packets tossed due to a session ID mismatch Failure to Reset Client Count This field represents the number of times the DHCP client was unable to be reset (resulting in no IP address being served). Page 3-68 Chapter 3: Operation System statistics Interpreting Sync Status statistics The Statistics > Sync Status page of AP is only displayed when the Sync Input is set to AutoSync or AutoSync+Free Run. The Sync Status page is explained in Table 146. Table 146 Sync Status page attributes - AP Attribute Meaning Sync Pulse Source This field indicates the status of the synchronization source:

Searching indicates that the unit is searching for a GPS fix Timing Port/UGPS indicates that the module is receiving sync via the timing AUX/SYNC timing port Power Port indicates that the module is receiving sync via the power port (Ethernet port). Sync Pulse Status This field indicates synchronization source pulse status. Sync Pulse Status -

Timing Port/UGPS Sync Pulse Status -

Power Port This field indicates synchronization pulse status over Timing Port/UGPS port. This field indicates synchronization pulse status over power port. UGPS Power Status This field indicates UGPS power up status (on or off). This information may be helpful in a decision of whether to climb a tower to diagnose a perceived antenna problem. Page 3-69 Chapter 3: Operation System statistics Interpreting PPPoE Statistics for Customer Activities The page can be access under Statistics > PPPoE of SM GUI. When the PPPoE feature is enabled on the SM, PPPoE statistics provide data about activities of the customer. The PPPoE Statistics of SM is explained in Table 147. Table 147 PPPoE Statistics page attributes - SM Attribute IP address Meaning This field displays the IP address of the PPPoE session initiator (situated below the SM) PPPoE Session Status This field displays the operational status of the PPPoE Session PPPoE AC Name This field displays access concentrator name used in the PPPoE session PPPoE Service Name This field displays the PPPoE service name associated with the PPPoE server in use PPPoE Session ID This field displays the current PPPoE session ID PPPoE Session Uptime PPPoE Session Idle Time PPPoE Session MTU This field displays the total session uptime for the PPPoE session This field displays the total idle time for the PPPoE session This field displays Maximum Transmission Unit configured for the PPPoE session Primary DNS Address This field displays the primary DNS server used by the PPPoE session Secondary DNS Address PPPoE Control Bytes Sent This field displays the secondary DNS server used by the PPPoE session Displays the total number of PPPoE session control bytes sent from SM Page 3-70 Chapter 3: Operation System statistics PPPoE Control Bytes Received This field displays the total number of PPPoE session control bytes received by the SM PPPoE Data Session Bytes Sent This field displays the total number of PPPoE data session (non-control/non-

session management user data) sent by the SM PPPoE Data Session Bytes Received This field displays the total number of PPPoE data session (non-control/non-

session management user data) Page 3-71 Chapter 3: Operation System statistics Interpreting Bridge Control Block statistics The Statistics > Bridge Control Block page displays statistics of Bridge FEC, Bridge ratio and Bridge error. The page is applicable for all modules (AP/SM/BHM/BHS). The Bridge Control Block Statistics page is explained in Table 148. Table 148 Bridge Control Block page attributes AP/SM/BHM/BHS Page 3-72 Chapter 3: Operation Attribute Meaning Bridge FEC Stats System statistics FEC bin FEC bout FEC btoss This field indicates the number of broadcast packets received by the bridge control block on the Main Ethernet interface This field indicates the number of broadcast packets sent by the bridge control block on the Main Ethernet interface This field indicates the number of broadcast packets tossed out by the bridge control block on the Main Ethernet interface FEC btosscap This field indicates the number of broadcast packets tossed out at the Main Ethernet interface due to MIR cap being exceeded. FEC uin FEC uout FEC utoss This field indicates the number of unicast packets received by the bridge control block on the Main Ethernet interface This field indicates the number of unicast packets sent by the bridge control block on the Main Ethernet interface This field indicates the number of unicast packets tossed by the bridge control block on the Main Ethernet interface FEC utosscap This field indicates the number of unicast packets tossed out at the Main Ethernet interface due to MIR cap being exceeded. Bridge Eth Aux Stats FEC bin FEC bout FEC btoss This field indicates the number of broadcast packets received by the bridge control block on the Aux Ethernet interface This field indicates the number of broadcast packets sent by the bridge control block on the Aux Ethernet interface This field indicates the number of broadcast packets tossed out by the bridge control block on the Aux Ethernet interface FEC btosscap This field indicates the number of broadcast packets tossed out at the Aux Ethernet interface due to MIR cap being exceeded. FEC uin FEC uout FEC utoss This field indicates the number of unicast packets received by the bridge control block on the Aux Ethernet interface This field indicates the number of unicast packets sent by the bridge control block on the Aux Ethernet interface This field indicates the number of unicast packets tossed by the bridge control block on the Aux Ethernet interface FEC utosscap This field indicates the number of unicast packets tossed out at the Aux Ethernet interface due to MIR cap being exceeded. Bridge Radio Stats Page 3-73 Chapter 3: Operation System statistics RF bin RF bout RF btoss This field indicates the number of broadcast packets received by the bridge control block on the radio interface This field indicates the number of broadcast packets sent by the bridge control block on the radio interface This field indicates the number of broadcast packets tossed by the bridge control block on the radio interface RF btosscap This field indicates the number of broadcast packets tossed out at the radio interface due to MIR cap being exceeded. RF uin RF uout RF utoss This field indicates the number of unicast packets received by the bridge control block on the radio interface This field indicates the number of unicast packets sent by the bridge control block on the radio interface This field indicates the number of unicast packets tossed by the bridge control block on the radio interface RF utosscap This field indicates the number of unicast packets tossed out at the radio interface due to MIR cap being exceeded. Bridge Error Stats ErrNI1QSend ErrNI2QSend This field indicates that a packet which was sourced from the radio network stack interface 1 (Ethernet interface) could not be sent because the radio bridge queue was full. The packet was tossed out. This field indicates that a packet which was sourced from the radio network stack interface 2 (RF interface) could not be sent because the radio bridge queue was full. The packet was tossed out. ErrBridgeFull This field indicates the total number of times the bridging table was full and could not accept new entries. ErrSendMsg This field displays the error message from bridge core call back routine. ErrApFecQSend ErrApRfQSend This field indicates that a packet which was received on the Ethernet interface could not be processed because the radio bridge queue was full and packet was tossed out. This field indicates that a packet which was received on the RF interface could not be processed because the radio bridge queue was full. The packet was tossed out. Page 3-74 Chapter 3: Operation System statistics Interpreting Pass Through Statistics The Statistics > Pass Through Statistics page displays radius related statistics. The page is applicable for PMP 450 Platform Family - AP only. The Pass Through Statistics page is explained in Table 149. Table 149 Pass Through Statistics page attributes AP Attribute Meaning IdentityReqSent PktsEncapsulated PktsDecasulated This field indicates the number of EAP Identity requests sent through the AP with respect to an SM. This field indicates no of packets received from the SM which are encapsulated by the AP. This field indicates no of packets received from the radius server and are decapsulated by the AP with respect to an SM AccessAcceptRcvd This field indicates no of RADIUS Access Accept message received by the AP with respect to an SM. Page 3-75 Chapter 3: Operation System statistics Interpreting SNMPv3 Statistics The Statistics > SNMPv3 Statistics page displays all SNMPv3 related statistics. The page is applicable for all type of ODUs of PMP 450 Platform. The SNMPv3 Statistics page is explained in Table 150. Table 150 SNMPv3 Statistics page attributes AP Attribute Meaning Statistics for snmpMPDStats group SNMP Message Processing and Dispatching RFC 3412 Page 3-76 Chapter 3: Operation System statistics snmpUnknownSecurityMod els The total number of packets received by the SNMP engine which were dropped because they referenced a securityModel that was not known to or supported by the SNMP engine. snmpInvalidMsgs snmpUnknownPDUHandler s The total number of packets received by the SNMP engine which were dropped because there were invalid or inconsistent components in the SNMP message. The total number of packets received by the SNMP engine which were dropped because the PDU contained in the packet could not be passed to an application responsible for handling the pduType, e.g. no SNMP application had registered for the proper combination of the contextEngineID and the pduType. usmStatsUnsupportedSecL evels The total number of packets received by the SNMP engine which were dropped because they requested a securityLevel that was unknown to the SNMP engine or otherwise unavailable. usmStatsNotInTimeWindo ws The total number of packets received by the SNMP engine which were dropped because they appeared outside of the authoritative SNMP engine's window. usmStatsUnknownUserNa mes The total number of packets received by the SNMP engine which were dropped because they referenced a user that was not known to the SNMP engine. usmStatsUnknownEngineI Ds The total number of packets received by the SNMP engine which were dropped because they referenced a snmpEngineID that was not known to the SNMP engine. usmStatsWrongDigests The total number of packets received by the SNMP engine which were dropped because they didn't contain the expected digest value. usmStatsDecryptionErrors The total number of packets received by the SNMP engine which were dropped because they could not be decrypted. snmpTargetSpinLock This object is used to facilitate modification of table entries in the SNMP-TARGET-MIB module by multiple managers. snmpUnavailableContexts snmpUnknownContexts usmUserSpinLock The total number of packets received by the SNMP engine which were dropped because the context contained in the message was unavailable. The total number of packets received by the SNMP engine which were dropped because the context contained in the message was unknown. The use of usmUserSpinlock is to avoid conflicts with another SNMP command generator application which may also be acting on the usmUserTable. Page 3-77 Chapter 3: Operation vacmViewSpinLock System statistics An advisory lock used to allow cooperating SNMP Command Generator applications to coordinate their use of the Set operation in creating or modifying views. snmpEngineBoots It is a count of the number of times the SNMP engine has re-

booted/re-initialized since snmpEngineID was last configured snmpEngineTime time since engine is up which is the number of seconds since the snmpEngineBoots counter was last incremented Interpreting syslog statistics The Statistics > Syslog Statistics page displays statistics of syslog messages. The page is applicable for all modules (AP/SM/BHM/BHS). The Syslog Statistics page is explained in Table 151. Table 151 Syslog statistics page attributes AP/SM/BH Attribute Syslog Server Meaning This displays dotted decimal or DNS name (if the DNS is enabled) of the syslog server address. Syslog Server Port The syslog server port (default 514) to which syslog messaging is sent. Syslog Status Syslog Message Transmissions This indicates status of syslog messaging. It can be Enable or Disabled based on configuration This field indicates the count of syslog messages sent to UDP layer. Syslog Message Dropped This field indicates the count of dropped syslog messages. Page 3-78 Chapter 3: Operation System statistics Interpreting Frame Utilization statistics The Frame Utilization Statistics is a feature helps user to understand how effectively the RF channel is being utilized. This feature allows to check Time Division Duplex (TDD) frame utilization pattern and diagnose for any excessive usage in uplink or downlink direction. This forms the first step of identifying the TDD frame utilization information. If the user finds excessive utilization based on these stats, the second step would be to take several actions like sectorization, tuning the uplink/downlink ratio etc. to improve RF channel utilization. Efficient use of the TDD frame will help to achieve optimum performance of link. Note The backhauls (BHM and BHS) will have only the downlink scheduler-

based statistics Table 152 Frame utilization statistics for 450m Page 3-79 Chapter 3: Operation System statistics Attribute Meaning Frame Utilization Interval Statistics Display interval This allows to configure timer interval to monitor and display the frame utilization statistics. It can be configured for 1 minute (low interval), 5 minutes (medium interval) or 15 minutes (high interval) based on requirement. Next Update This field displays when the next update will occur. MU-MIMO Utilization Slot Grouping - Group Size This specifies the distribution of group size for the past 1/5/15 minutes. For each group size, from 1 to 7, the table shows the percentage of slots using that group size. A group size of 1 corresponds to beamformed transmissions. A group size of 2 to 7 corresponds to MU-MIMO transmissions. Additional Statistics Average MU-MIMO Group Size - Data This specifies the average number of users in the MU-MIMO groups formed in the last 1/5/15 minutes for data traffic only. Total Utilization This is a percentage of available timeslots used in the past 1/5/15 minutes. Page 3-80 Chapter 3: Operation Multiplexing Gain Sector Utilization SU-MIMO MU-MIMO ACK MU-MIMO ACK System statistics This specifies the ratio between the number of logical slots and the number of physical slots used. A physical slot is an OFDM symbol. In non MU-MIMO mode, each logical slot is sent during one physical slot. In MU-MIMO mode a number of logical slots are sent during a physical slot, equal to the number of VCs in the group. A logical slot carries new information; if data is repeated in a group, because some VCs have more data to send then others, then the repeated transmissions are not counted as a logical slots. Without MU-MIMO operation, the multiplexing gain would always be equal to 1. With MU-MIMO operation, this number accounts for parallel transmissions to multiple users in the MU-MIMO group. The difference between the Average MU-MIMO Group Size and the Multiplexing Gain is that the Average MU-MIMO Group Size only considers the MU-MIMO groups, and it averages the number of VCs in the Group. The Multiplexing Gain also considers non MU-MIMO transmissions, which are counted as groups of size 1. This specifies the portion of the Total Utilization used for SU-MIMO transmissions. This specifies the portion of the Total Utilization used for MU-MIMO transmissions. This specifies the portion of the Total Utilization used for acknowledgments transmission. This specifies the portion of the Total Utilization used for acknowledgements transmissions that are MU-MIMO scheduled. Currently only the UL direction supports MU-MIMO scheduling of ACK's. Broadcast & Multicast This specifies the portion of the Total Utilization used for broadcast and multicast transmissions. Slots Counts - Uplink and Downlink Slot Counts Per Frame Average This indicates the average data per frame in the downlink traffic. Low Priority Medium Priority High Priority The number of downlink data slots used for low priority downlink traffic. The number of downlink data slots used for medium priority downlink traffic. The number of downlink data slots used for high priority downlink traffic. Page 3-81 Chapter 3: Operation Ultra High Priority System statistics The number of downlink data slots used for ultra high priority downlink traffic. Note: The above Low, Medium, High, and Ultra High Priority Counts are physical slot transmissions. For MU-MIMO scheduling, some transmissions can contain data from more than 1 data channel priority. In those cases, the highest data channel used is "counted" in these statistics, and the other data channels are not, to avoid overcounting. Broadcast & Multicast The number of downlink data slots used for broadcast and multicast traffic. Authentication and Configuration The number of slots used for registration and control message transmissions Registration and control The number of slots used for Authentication and Configuration transmissions. MAC Acknowledgements The number of downlink data slots used as ACKs. Contention Slots Average Per Frame It is the average number of contention slots in a frame for the last duration. Duration is 1/5/15 mins. Bandwidth Requests Received Bandwidth Requests Missed Total This indicates the number of Bandwidth Requests received from SMs. This indicates how many of Bandwidth Requests are colliding. This indicates the sum of all downlink data slots used in the configured interval. Frame Utilization Downlink Uplink This indicates the percentage of downlink data slots used against the maximum number of slots possible in the configured interval. This indicates the percentage of uplink data slots used against the maximum number of uplink slots possible in the configured interval. Page 3-82 Chapter 3: Operation System statistics Bandwidth Request Success Maximum possible counts Downlink Uplink The "Bandwidth Request Success" is a message sent from the SM to the AP asking to be scheduled for bandwidth to send in the uplink. This gets transmitted in the unscheduled portion of the uplink. Unscheduled uplink is defined as Contention Slots + unscheduled uplink slots. Since this is sent in the unscheduled portion of the uplink, it will result in collisions when SMs randomly pick the same slot. The "Bandwidth Request Missed" metrics are to add data to know how many of requests are colliding. If it is near 100%, then near all of the SMs bandwidth requests are getting through to the AP, so this a is near perfect scenario. If it is significantly less than that, you may be experiencing uplink latency as your SMs are attempting to request bandwidth and are unable to do so. Also note that if it is consistently at 100% the AP may be able to reduce its contention slots to a lower value and gain more data slots. This indicates the maximum possible downlink data slots in the configured interval. This is based on the configuration of Channel Bandwidth, Frame period, uplink/downlink allocation, contention slots and configured Statistics Display interval. This indicates the maximum possible uplink data slots in the configured interval. This is based on the configuration of Channel Bandwidth, Frame period, uplink/downlink allocation, contention slots and configured Statistics Display interval. Contention This indicates the maximum possible contention slots. Packet Discard counts Ethernet indiscards This indicates the number of Ethernet packets discarded in the IN queue. Ethernet outdiscards This indicates the number of Ethernet packets discarded in the OUT queue. Radio indiscards Radio outdiscards This indicates the number of packets discarded over radio in the IN queue. This indicates the number of packets discarded over radio in the OUT queue. Page 3-83 Chapter 3: Operation Table 153 Frame utilization statistics for 450, 450i System statistics Attribute Meaning See Table 152 Frame utilization statistics for 450m. Page 3-84 Chapter 3: Operation Interpreting Spatial Utilization statistics Table 154 Spatial Utilization statistics System statistics Page 3-85 Chapter 3: Operation Spatial Frequency Heatmap System statistics Attribute Instantaneous Distribution Meaning This table is updated every 500 ms and displays the following:

Group: Each row corresponds to the top (most active) 1, 2, 8, 16, 32, 64, 128 and 256 VCs. Median Slot Count: Median value of the average number of slots scheduled for the VCs in each group in the past 500 ms. LUIDs in Group: List of LUIDs belonging to each bin. Spatial Utilization This is a table (32 rows) that lists frame utilization for each spatial frequency (SF) range with following information:

Page 3-86 Chapter 3: Operation Attribute Meaning System statistics Spatial Frequency: Range of spatial frequency for each bin. Each bin includes 32 consecutive spatial frequency values. Azimuth (degrees): Azimuth range in degrees corresponding to the spatial frequencies of the bin. The zero-degree Azimuth is boresight. 7. Note Some SF ranges correspond to multiple azimuth ranges. This is because for some spatial frequencies the AP generates beams in multiple azimuth directions. The SM can be physically located in any of the azimuth ranges. Instantaneous (%): Frame utilization for the SF bin, updated every 500 ms. The frame utilization percentage accounts for all traffic, sector mode, beamforming mode, and MU-MIMO mode. 8. Total (%): Average utilization in the SF bin for the past 1/5/15 minutes, as selected in the Statistics Display interval. 9. Max (%): Maximum instantaneous utilization in the 1/5/15 minute interval. 10. Min (%): Minimum instantaneous utilization in the 1/5/15 minute interval. 11. VCs in Range: List of VCs with spatial frequency falling in the bin. 12. LUIDs in Range: List of LUIDs with spatial frequency falling in the bin. Note The size of each SF bin is smaller than the beam generated by the AP during a MU-MIMO transmission. This means that when a VC in a bin is scheduled for a MU-MIMO transmission, the adjacent bins also receive the signal, and the transmission is counted towards their utilization as well. Bins with consistent low utilization indicate the areas of the sector where more SMs could be installed, or the cutomers that could be offered higher data plans. The spatial frequency heatmap allow the operator to see how the 450m spatial frequency have been occupied (utilised) over the previous hour of operation. There are two heatmaps the first displays downlink utilisation and the lower the uplink utilisation. The heatmaps are useful when operators are identifying:

congested spatial directions Page 3-87 Spatial Utilization

(Contd.) Spacial Frequency Heatmap Chapter 3: Operation System statistics Attribute Meaning spare capacity in spatial directions The heatmap uses a graduated colour scale to represent the percentage utilisation. The graphic to the right-hand side of the heatmap should be used as a key to interpret the GUI. Where dark blue represents zero percent utilisation and red represents 100% utilisation. Page 3-88 Chapter 3: Operation Radio Recovery Radio Recovery This section describes:

How to recover a PMP/PTP 450i and PMP 450m Series ODUs from configuration errors or software image corruption How to override a PMP/PTP 450 Series ODUs from forgotten IP address and password to factory default Radio Recovery Console PMP/PTP 450i/450b and PMP 450m Recovery mode allows to restore IP address and password. Also, it 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 a software upgrade. Note When Recovery has been entered through a power on/off/on cycle, the ODU will revert to normal operation if no web access has been made to the unit within 30 seconds. This prevents the unit remaining inadvertently in recovery following a power outage. Options in recovery mode are:

Boot with normal operation Boot with default Canopy system software settings The last most recent software images loaded to the board are retained. However the factory image is not retained. Load a previous SW image Boot with default Canopy system software settings (similar to the hardware Default Plug based on 450 Platforms Family). Note The unit may enter recovery console automatically, in response to some failures. Note Once the unit has entered recovery, it will switch back to normal operation if no access has been made to the recovery web page within 30 seconds. Use below procedure to enter in recovery console manually. Page 3-89 Chapter 3: Operation Procedure 27 Radio Recovery Console 1 Apply power to PSU for at least 10 seconds. Radio Recovery 2 Remove power from the PSU, and then re-apply it as soon as the power indicator light goes out (about 1 - 2 seconds). 3 When the unit is in recovery mode, access the web interface by entering the default IP address 169.254.1.1. The Recovery Image Warning page is displayed. 4 Review the Boot Selection (Table 155). 5 Select a recovery option Figure 91 Recovery Options page Table 155 Recovery Options attributes Attribute Meaning Boot Selection Boot Default Mode: Use this option to temporarily set the IP and Ethernet attributes to factory defaults until the next reboot. Boot Normal: Use this option to reboot the unit. IP address, Netmask, Gateway These fields display IP address, Netmask and Gateway of the radio while it is in recovery or default mode. Page 3-90 Chapter 3: Operation Radio Recovery Note The radio enters recovery mode when a short power cycle is used. The radio will boot normally if power has been removed for a longer period (typically 5 - 10 seconds). Default Mode (or Default/Override Plug) - PMP/PTP 450 Series The default mode allows to temporarily override some PMP/PTP 450 Series ODU settings and thereby regain control of the module by powering the module on with the Default Plug inserted into the units synchronization (RJ11) port. This override plug is needed for access to the module in any of the following cases:

You have forgotten either o o the IP address assigned to the ODU. the password that provides access to the ODU. The ODU has been locked by the No Remote Access feature. You want local access to a module that has had the 802.3 link disabled in the Configuration page. You can configure the module such that, when it senses the override plug, it responds by either resetting the LAN1 IP address to 169.254.1.1, allowing access through the default configuration without changing the configuration, whereupon you will be able to view and reset any non-default values as you wish. resetting all configurable parameters to their factory default values. Note The Default Plug is available from Best-Tronics Manufacturing, Inc. See https://btpa.com/Cambium-Products/ as Part BT-0583 (RJ-11 Default Plug). Alternatively, you can fabricate an override plug. See Override plug cable in Planning and Installation Guide for pinout. Using the Default/Override Plug The following section details usage of the override plug to regain access to PMP/PTP 450 Series ODU. Note While the override plug is connected to a PMP/PTP 450 Series ODU, the ODU can neither register nor allow registration of another ODU. Note Since the 900 MHz SM is based on the 450 Series, it only supports the "Default Plug"

mode of overriding. Page 3-91 Chapter 3: Operation Use below procedure to enter in default mode manually. Procedure 28 Default mode Radio Recovery 1 2 Insert the override plug into the RJ-11 GPS utility port of the module. Power cycle by removing, then re-inserting, the Ethernet cable. RESULT: The module boots with the default IP address of 169.254.1.1, password fields blank, and all other configuration values as previously set. 3 Wait approximately 30 seconds for the boot to complete. 4 5 6 7 8 Remove the override plug. Set passwords and IP address as desired. Change configuration values if desired. Click the Save Changes button. Click the Reboot button. Page 3-92 Chapter 4: Reference information Chapter 4: Reference information This chapter contains reference information and regulatory notices that apply to the 450 Platform Family ODUs. The following topics are described in this chapter:

Equipment specifications on page 4-2 contains specifications of the 450 Platform Family, ODU specifications including RF bands, channel width and link loss. Data network specifications on page 4-56 shows the 450 Platform Family Ethernet interface specifications. Wireless specifications on page 4-57 lists the safety specifications against which 450 Platform Family ODU has been tested and certified. It also describes how to keep RF exposure within safe limits. Country specific radio regulations on page 4-59 describes how the 450 Platform Family complies with the radio regulations that are enforced in various countries. Equipment Disposal on page 4-63 describes the Equipment Disposal system for Electronic and Electric Equipment. Page 4-1 Chapter 4: Reference information Equipment specifications Equipment specifications This section contains specifications of the AP, SM, BHM and BHS associated supplies required for 450 Platform Family installations. Specifications for 5 GHz PMP 450m Series - AP The 5 GHz PMP 450m AP conforms to the specifications listed in Table 156. Table 156 5 GHz PMP 450m Series - AP specifications Category Model Number Spectrum Channel Spacing Frequency Range Channel Bandwidth Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Nominal Receive Sensitivity (w/ FEC) @ 5 MHz Channel Specification PMP 450m AP Configurable on 2.5 MHz increments 4900 to 5925 MHz 5, 10, 15, 20, 30, and 40 MHz Cambium Proprietary 14x14 Multi-User MIMO OFDM 100/1000BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID 4.9 GHz 5.1 GHz 5.2 GHz 1x=-101.6 dBm, 2x=-96.2 dBm, 4x=-90.2 dBm, 6x=-84 dBm, 8x=-76.6 dBm 1x=-101.6 dBm, 2x=-96.2 dBm, 4x=-90.2 dBm, 6x=-84 dBm, 8x=-76.6 dBm 1x=-101.3 dBm, 2x=-96.3 dBm, 4x=-89.7 dBm, 6x=-83.3 dBm, 8x=-75.7 dBm Page 4-2 Chapter 4: Reference information Equipment specifications 5.4 GHz 5.8 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz 5.1 GHz Nominal Receive Sensitivity (w/ FEC) @

10 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

15 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel 1x=-101.1 dBm, 2x=-96.8 dBm, 4x=-90 dBm, 6x=-83.9 dBm, 8x=-76.2 dBm 1x=-101.6 dBm, 2x=-96.6 dBm, 4x=-89.9 dBm, 6x=-83.7 dBm, 8x=-76.3 dBm 1x=-99 dBm, 2x=-94.6 dBm, 4x=-87.8 dBm, 6x=-81.6 dBm, 8x=-74.6 dBm 1x=-98.8 dBm, 2x=-93.8 dBm, 4x=-87.6 dBm, 6x=-81.4 dBm, 8x=-73.6 dBm 1x=-98.1 dBm, 2x=-94.1 dBm, 4x=-87.5 dBm, 6x=-81.5 dBm, 8x=-73.8 dBm 1x=-98.5 dBm, 2x=-93.6 dBm, 4x=-87.5 dBm, 6x=-81.2 dBm, 8x=-73.7 dBm 1x=-97.3 dBm, 2x=-92.5 dBm, 4x=-86.3 dBm, 6x=-79.9 dBm, 8x=-72.9 dBm 1x=-97.3 dBm, 2x=-92.5 dBm, 4x=-86.3 dBm, 6x=-79.9 dBm, 8x=-72.9 dBm 1x=-96.7 dBm, 2x=-91.9 dBm, 4x=-85.7 dBm, 6x=-79.5 dBm, 8x=-72.5 dBm 1x=-96.2 dBm, 2x=-92.1 dBm, 4x=-85.5 dBm, 6x=-79.4 dBm, 8x=-72.4 dBm 1x=-97.2 dBm, 2x=-92.4 dBm, 4x=-85.5 dBm, 6x=-79.4 dBm, 8x=-72.5 dBm 1x=-96.3 dBm, 2x=-91.9 dBm, 4x=-85.3 dBm, 6x=-79.3 dBm, 8x=-71.3 dBm 1x=-96.3 dBm, 2x=-91.9 dBm, 4x=-85.3 dBm, 6x=-79.3 dBm, 8x=-71.3 dBm 1x=-95.8 dBm, 2x=-91.8 dBm, 4x=-84.8 dBm, 6x=-78.8 dBm, 8x=-71.8 dBm 1x=-95.1 dBm, 2x=-91.4 dBm, 4x=-84.8 dBm, 6x=-78.3 dBm, 8x=-71.1 dBm 1x=-95.8 dBm, 2x=-91.3 dBm, 4x=-84.7 dBm, 6x=-78.3 dBm, 8x=-70.8 dBm 1x=-93.1 dBm, 2x=-89.0 dBm, 4x=-83.0 dBm, 6x=-76.7 dBm, 8x=-69.8 dBm 1x=-93.1 dBm, 2x=-89.0 dBm, 4x=-83.0 dBm, 6x=-76.7 dBm, 8x=-69.8 dBm Page 4-3 Chapter 4: Reference information Equipment specifications Nominal Receive Sensitivity (w/ FEC) @

40 MHz Channel 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 1x=-93.1 dBm, 2x=-88.7 dBm, 4x=-82.5 dBm, 6x=-76.2 dBm, 8x=-69.4 dBm 1x=-93.6 dBm, 2x=-89.1 dBm, 4x=-82.9 dBm, 6x=-76.5 dBm, 8x=-69.7 dBm 1x=-94.1dBm, 2x=-89.4 dBm, 4x=-83.2 dBm, 6x=-76.8 dBm, 8x=-69.9 dBm 1x=-92.1 dBm, 2x=-88.1 dBm, 4x=-82.0 dBm, 6x=-75.5 dBm, 8x=-68.2 dBm 1x=-92.1 dBm, 2x=-88.1 dBm, 4x=-82.0 dBm, 6x=-75.5 dBm, 8x=-68.2 dBm 1x=-92.0 dBm, 2x=-87.7 dBm, 4x=-81.7 dBm, 6x=-75.3 dBm, 8x=-67.9 dBm 1x=-92.7 dBm, 2x=-87.4 dBm, 4x=-81.8 dBm, 6x=-75.4 dBm, 8x=-68.2 dBm 1x=-93.0 dBm, 2x=-87.9 dBm, 4x=-82.1 dBm, 6x=-75.6 dBm, 8x=-68.1 dBm Performance Subscriber Per Sector ARQ Cyclic Prefix Frame Period Modulation Levels (Adaptive) Up to 238 Yes 1/16 2.5 ms, 5 ms Modulation Levels 2x 4x 6x 8x MCS SNR (in dB) QPSK 16QAM 64QAM 256QAM 10 17 24 32 Latency 10 ms, typical (MU-MIMO introduces additional latency for the traffic that is MU-MIMO scheduled.) Maximum Deployment Range Up to 40 miles (64 km) GPS Synchronization Quality of Service Yes, via Autosync (UGPS) Diffserv QoS Page 4-4 Chapter 4: Reference information Equipment specifications Link Budget Antenna Beam Width 5 GHz 90 integrated sector (Dual polarity, H+V) Antenna Gain Maximum EIRP Physical Data, Sync/AUX and SFP port RJ45 Antenna Connection Surge Suppression (with LPU) Mean Time Between Failure Environmental Temperature / Humidity

+14 dBi

+48 dBm 1000BASE-T Ethernet Data AUX port for UGPS or PoE out to 802.3at Integrated Sector Array EN61000-4-5: 1.2 us/50 us, 500 V voltage waveform Recommended external surge suppressor:

Cambium Networks Model # C000065L007B

> 40 Years IP66, IP67

-40C to +60C (-40F to +140F) 0-95% non-condensing Weight Integrated Approx. 14.2 kg (31 bs) Wind Loading Front Facing

@90 mph / 144 kph

@110 mph /177 kph 376 N 562 N Dimension (HxWxD) Integrated 52 x 65 x 11 cm (20.3 x 25.7 x 4.4) Power Consumption Input Voltage Mounting Security Encryption 70 W typical, 80 W peak

(up to 110 W max with AUX port PoE enabled) 58 V, 1.7 A Pole mount with included brackets 128-bit AES and 256-bit AES Note AES-256 requires a license key. Page 4-5 Chapter 4: Reference information Equipment specifications Specifications for 3 GHz PMP 450m Series - AP The 3GHz PMP 450m AP conforms to the specifications listed in Table 157. Table 157 3GHz PMP 450m Series - AP specifications Category Model Number Spectrum Channel Spacing Frequency Range Channel Bandwidth Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Nominal Receive Sensitivity (w/ FEC) @ 5 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

10 MHz Channel 3.5 GHz 3.6 GHz 3.5 GHz 3.6 GHz 3.5 GHz Specification 3GHz PMP 450m AP Customizable channel selection to 50KHz raster 3300 3900 MHz 5, 7, 10, 15, 20, 30 and 40MHz Cambium Networks Proprietary 8x8 Multi-User MIMO OFDM 100/1000BaseT, full duplex, rate auto negotiated (802.3 compliant), dual SFP support for 1 Gbps optical IPv4, IPv6, UDP, TCP/IP, ICMP, Telnet, SNMP, HTTP, FTP IPv4/IPv6 (dual stack), HTTP, HTTPS, Telnet, FTP, SNMPv2c and v3, Cambium Networks cnMaestroTM 802.1ad (DVLAN Q-inQ), 802.1Q with 802.1p priority, dynamic port VID 1x=-97.3 dBm, 2x=-95.1 dBm, 4x=-88.7 dBm, 6x=-82.6 dBm, 8x=-74.9 dBm 1x=-96.6 dBm, 2x=-94.4 dBm, 4x=-88.0 dBm, 6x=-82.0 dBm, 8x=-74.2 dBm 1x=-94.9 dBm, 2x=-92.9 dBm, 4x=-86.4 dBm, 6x=-80.3 dBm, 8x=-73.2 dBm 1x=-94.3 dBm, 2x=-92.2 dBm, 4x=-85.8 dBm, 6x=-79.6 dBm, 8x=-72.3 dBm 1x=-93.1 dBm, 2x=-91.1 dBm, 4x=-84.6 dBm, 6x=-78.3 dBm, 8x=-71.9 dBm Page 4-6 Chapter 4: Reference information Equipment specifications Category Specification Nominal Receive Sensitivity (w/ FEC) @

15 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

40 MHz Channel Performance Subscriber Per Sector ARQ Cyclic Prefix Frame Period 3.6 GHz 3.5 GHz 3.6 GHz 3.5 GHz 3.6 GHz 3.5 GHz 3.6 GHz Modulation Levels (Adaptive) 1x=-92.6 dBm, 2x=-90.3 dBm, 4x=-84.0 dBm, 6x=-77.8 dBm, 8x=-71.2 dBm 1x=-92.0 dBm, 2x=-89.8 dBm, 4x=-83.3 dBm, 6x=-77.1 dBm, 8x=-68.7 dBm 1x=-91.3 dBm, 2x=-89.2 dBm, 4x=-82.7 dBm, 6x=-76.5 dBm, 8x=-69.9 dBm 1x=-90.2 dBm, 2x=-88.0 dBm, 4x=-81.5 dBm, 6x=-75.3 dBm, 8x=-68.7 dBm 1x=-89.5 dBm, 2x=-87.4 dBm, 4x=-80.9 dBm, 6x=-74.7 dBm, 8x=-68.1 dBm 1x=-89.0 dBm, 2x=-86.8 dBm, 4x=-80.3 dBm, 6x=-74.1 dBm, 8x=-67.5 dBm 1x=-88.3 dBm, 2x=-86.2 dBm, 4x=-79.7 dBm, 6x=-73.5 dBm, 8x=-66.9 dBm Up to 238 Yes 1/16 2.5 ms, 5 ms Modulation Levels 2x 4x 6x 8x MCS SNR (in dB) QPSK 16QAM 64QAM 256QAM 10 17 24 32 Latency 10 ms, typical Maximum Deployment Range Up to 40 miles (64 km) GPS Synchronization Quality of Service Link Budget Yes, via Autosync (UGPS, CMM5 (GPS only, no power)) Diffserv QoS Page 4-7 Chapter 4: Reference information Equipment specifications Category Antenna Beam Width

(Azimuth) Antenna Beam Width

(Elevation) Antenna Gain Maximum EIRP Physical Data ports Main port Aux port SFP port 1 SFP port 2 RJ45 RJ45 SFP SFP Specification 90 integrated sector (3dB rolloff), 120 (6dB rolloff),

(dual slant polarity, 45 2 Electrical Downtilt, 8 Elevation (with Null Fill)

+16 dBi

+52 dBm (or up to maximum allowed by regulation) 1000BASE-T Ethernet Data 100BASE-T with 802.3at PoE out; UGPS power/sync Single channel SFP, 1 Gbps Dual channel SFP, 1 Gbps Power 4-pin DC power input Antenna Connection Surge Suppression (with LPU) Mean Time Between Failure Environmental Temperature / Humidity Integrated Sector Array MAIN and AUX ports: EN61000-4-5: 10/700us, 4 kV voltage waveform. Recommended external surge suppressor: Model # C000065L007B DC IN port: EN61000-4-5: 1.2/50us, 2 kV/4 kV. Recommended external surge suppressor: Model #

C000000L114A

> 40 Years IP66, IP67

-40C to +60C (-40F to +140F) / 100% condensing Weight Integrated Without Mounting Brackets: 20.4 kg (45 lbs) With Mounting Brackets: 22.6 kg (49.8 lbs) Wind Loading Front Facing

@90 mph / 144 kph

@110 mph /177 kph

@124 mph/ 200kph 521 N 787 N 986 N Dimension (HxWxD) Integrated 69 x 61 x 17.5 cm (27.2 x 24 x 7) Page 4-8 Chapter 4: Reference information Equipment specifications Category Power Consumption Input Voltage Mounting Security Encryption Specification 140 W typical, 150 W peak (up to 180 W max with AUX port PoE enabled) 40 - 60 V DC Pole mount with included brackets (1.25" to 4" pole diameter) FIPS-197 128-bit AES, Optional 256-bit AES Note AES-256 requires a license key. Page 4-9 Chapter 4: Reference information Equipment specifications Specifications for PMP 450i Series - AP The PMP 450i AP conforms to the specifications listed in Table 158. Table 158 PMP 450i Series - AP specifications Category Model Number Spectrum Channel Spacing Frequency Range Specification PMP 450i AP 5, 7, 10, 15, 20, 30, and 40 MHz Channel Bandwidth Configurable on 2.5 MHz increments 902 to 928 MHz 3300 - 3900 MHz 4900 - 5925 MHz Channel Bandwidth 902 928 MHz 5, 7, 10, 15, and 20 MHz 3300 - 3900 MHz 4900 5925 MHz 5, 7, 10, 15, 20, 30, and 40 MHz 5, 10, 15, 20, 30, and 40 MHz Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Cambium Proprietary 2x2 MIMO OFDM 10/100/1000BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID Nominal Receive Sensitivity (w/ FEC) @ 5 MHz Channel 900 MHz 3.5 GHz 1x = -91.9 dBm, 2x = -86.7 dBm, 4x = -80.9 dBm, 6x = -75 dBm, 8x = -68.8 dBm 1x = -92.7 dBm, 2x = -88.7 dBm, 4x = -82.7 dBm, 6x = -

75.8 dBm, 8x = -69 dBm Page 4-10 Chapter 4: Reference information Equipment specifications Category 3.6 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz Nominal Receive Sensitivity (w/ FEC) @ 7 MHz Channel 900 MHz Nominal Receive Sensitivity (w/ FEC) @

10 MHz Channel 3.5 GHz 3.6 GHz 900 MHz 3.5 GHz 3.6 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz Specification 1x=-91 dBm, 2x=-86.1 dBm, 4x=-80.2 dBm, 6x=-73.1 dBm, 8x=-66 dBm 1x = -91.6 dBm, 2x = -87.6 dBm, 4x = -80.4 dBm, 6x = -

73.2 dBm, 8x = -66 dBm 1x = -91.4 dBm, 2x = -88 dBm, 4x = -80.8 dBm, 6x = -73.7 dBm, 8x = -67 dBm 1x = -91.8 dBm, 2x = -87.3 dBm, 4x = -80 dBm, 6x = -73.9 dBm, 8x = -66.6 dBm 1x = -92 dBm, 2x = -87 dBm, 4x = -80.8 dBm, 6x = -73.7 dBm, 8x = -66.6 dBm 1x = -91.5 dBm, 2x = -87 dBm, 4x = -80.2 dBm, 6x = -73.1 dBm, 8x = -66 dBm 1x = -90 dBm, 2x = -85.9 dBm, 4x = -79.8 dBm, 6x = -73.6 dBm, 8x = -67.9 dBm 1x=-91.8 dBm, 2x=-87.7 dBm, 4x=-80.8 dBm, 6x=-74.7 dBm, 8x=-67.3 dBm 1x=-90 dBm, 2x=-87 dBm, 4x=-79.8 dBm, 6x=-73.8 dBm, 8x=-67.2 dBm 1x = -90.6 dBm, 2x = -85.2 dBm, 4x = -79.1 dBm, 6x = -

73.2 dBm, 8x = -66.2 dBm 1x=-90.2 dBm, 2x=-86.2 dBm, 4x=-80 dBm, 6x=-73.1 dBm, 8x=-66.7 dBm 1x=-89.5 dBm, 2x=-85.7 dBm, 4x=-79.8 dBm, 6x=-72.8 dBm, 8x=-66.3 dBm 1x = -89.1 dBm, 2x = -85 dBm, 4x = -77.9 dBm, 6x = -71.8 dBm, 8x = -64.6 dBm 1x = -89.5 dBm, 2x = -85 dBm, 4x = -78.3 dBm, 6x = -72 dBm, 8x = -65 dBm 1x = -88.6 dBm, 2x = -84.7 dBm, 4x = -78 dBm, 6x = -71.5 dBm, 8x = -64.6 dBm 1x = -89.5 dBm, 2x = -85.4 dBm, 4x = -78.2 dBm, 6x = -

72.2 dBm, 8x = -64.8 dBm Page 4-11 Chapter 4: Reference information Equipment specifications Category Nominal Receive Sensitivity (w/ FEC) @

15 MHz Channel 5.8 GHz 900 MHz 3.5 GHz 3.6 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz Specification 1x = -89.5 dBm, 2x = -84.7 dBm, 4x = -77.8 dBm, 6x = -

71.6 dBm, 8x = -64 dBm 1x=-88.2 dBm, 2x=-83.2 dBm, 4x=-76.3 dBm, 6x=-70.2 dBm, 8x=-64.3 dBm 1x=-89 dBm, 2x=-84 dBm, 4x=-77.9 dBm, 6x=-72 dBm, 8x=-64.8 dBm 1x=-87.6 dBm, 2x=-83.7 dBm, 4x=-77.5 dBm, 6x=-71.6 dBm, 8x=-64.5 dBm 1x = -87.2 dBm, 2x = -83 dBm, 4x = -75.8 dBm, 6x = -69.6 dBm, 8x = -62.6 dBm 1x = -87.4 dBm, 2x = -83.5 dBm, 4x = -76.2 dBm, 6x = -

70.3 dBm, 8x = -63.1 dBm 1x = -87.5 dBm, 2x = -82.9 dBm, 4x = -76.5 dBm, 6x = -

69.5 dBm, 8x = -62.8 dBm 1x = -87.2 dBm, 2x = -83.3 dBm, 4x = -76.2 dBm, 6x = -

70.1 dBm, 8x = -63 dBm 1x = -87.7 dBm, 2x = -82.7 dBm, 4x = -75.5 dBm, 6x = -

69.6 dBm, 8x = -62.4 dBm Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel 900 MHz 1x = -86.99 dBm, 2x = -82 dBm, 4x = -75.9 dBm, 6x = -

69.9 dBm, 8x = -62.9 dBm 3.5 GHz 3.6 GHz 4.9 GHz 5.1 GHz 5.2 GHz 1x=-87.4 dBm, 2x=-83 dBm, 4x=-76.9 dBm, 6x=-69.9 dBm, 8x=-63 dBm 1x=-86.4 dBm, 2x=-82.5 dBm, 4x=-76.4 dBm, 6x=-69.4 dBm, 8x=-62.9 dBm 1x = -86.1 dBm, 2x = -82.1 dBm, 4x = -74.8 dBm, 6x = -

68.8 dBm, 8x = -61.7 dBm 1x = -86.9 dBm, 2x = -82 dBm, 4x = -75.2 dBm, 6x = -69.1 dBm, 8x = -61.8 dBm 1x = -85.5 dBm, 2x = -81.6 dBm, 4x = -75 dBm, 6x = -68.6 dBm, 8x = -61.6 dBm Page 4-12 Chapter 4: Reference information Equipment specifications Category Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

40 MHz Channel 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz Specification 1x = -86.6 dBm, 2x = -81.3 dBm, 4x = -75.5 dBm, 6x = -

68.6 dBm, 8x = -62 dBm 1x = -85.8 dBm, 2x = -80.7 dBm, 4x = -74.6 dBm, 6x = -

68.7 dBm, 8x = -61 dBm 1x=-85.6 dBm, 2x=-81.7 dBm, 4x=-74.5 dBm, 6x=-68 dBm, 8x=-61.5 dBm 1x=-85.5 dBm, 2x=-80.5 dBm, 4x=-74.4 dBm, 6x=-68.4 dBm, 8x=-61.5 dBm 1x = -84.1 dBm, 2x = -80 dBm, 4x = -73 dBm, 6x = -66.4 dBm, 8x = -59.6 dBm 1x = -84.5 dBm, 2x = -80 dBm, 4x = -73.2 dBm, 6x = -67.1 dBm, 8x = -60 dBm 1x = -84.5 dBm, 2x = -80 dBm, 4x = -73.4 dBm, 6x = -67.3 dBm, 8x = -58.3 dBm 1x = -84.5 dBm, 2x = -82 dBm, 4x = -73.5.5Bm, 6x = -67.4 dBm, 8x = -60.2 dBm 1x = -84.1 dBm, 2x = -80 dBm, 4x = -73 dBm, 6x = -66.5 dBm, 8x = -59.4 dBm 1x=-83.9 dBm, 2x=-79.5 dBm, 4x=-73 dBm, 6x=-66 dBm, 8x=-58.5 dBm 1x=-82.8 dBm, 2x=-79 dBm, 4x=-73 dBm, 6x=-66 dBm, 8x=-59 dBm 1x=-83.9 dBm, 2x=-78.9 dBm, 4x=-72 dBm, 6x=-66 dBm, 8x=-56.6 dBm 1x=-84.2 dBm, 2x=-79 dBm, 4x=-72.2 dBm, 6x=-66.3 dBm, 8x=-57.2 dBm 1x=-84 dBm, 2x=-79.8 dBm, 4x=-72.6 dBm, 6x=-66.4 dBm, 8x=-57 dBm 1x=-83.7 dBm, 2x=-78.5 dBm, 4x=-72.4 dBm, 6x=-66 dBm, 8x=-58 dBm Page 4-13 Chapter 4: Reference information Equipment specifications Category Performance ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Latency Maximum Deployment Range GPS Synchronization Quality of Service Link Budget 5.8 GHz Specification 1x=-83.8 dBm, 2x=-78.4 dBm, 4x=-72 dBm, 6x=-66 dBm, 8x=-57 dBm Yes 1/16 2.5 ms or 5.0 ms Modulation Levels 2x 4x 6x 8x 3 - 5 ms MCS SNR (in dB) QPSK 16QAM 64QAM 256QAM 10 17 24 32 Up to 40 miles (64 km) Up to 120 miles (190 km) for 900 MHz Yes, via Autosync (CMM4), via UGPS Diffserv QoS Antenna Beam Width 900 MHz 65 sector antenna (Dual Slant) 3 GHz 5 GHz 90 sector for integrated (Dual polarity, slant +45 and -

45) 90 (3 dB roll off) sector for integrated (Dual polarity, H+V) Antenna Gain (Does not include cable loss, ~1dB) 900 MHz 13 dBi 3 GHz 5 GHz 17 dBi integrated 90 sector or external 17 dBi integrated 90 sector or external Transmit Power Range 40 dB dynamic range (to EIRP limit by region) (1 dB step) Page 4-14 Chapter 4: Reference information Equipment specifications Category Maximum Transmit Power Physical Sync/AUX port RJ45 Antenna Connection Surge Suppression EN61000-4-5 Mean Time Between Failure Environmental Temperature / Humidity Specification

+27 dBm combined output (for 5 GHz)

+25 dBm combined output (for 3 GHz)

+25 dBm combined output (for 900MHz) 10/100/100BASE-T Ethernet Data PoE output (planned for future release) Sync input or output (Connection and powering of UGPS Sync input) 50 ohm, N-type (Connectorized version only) EN61000-4-5: 1.2 us/50 us, 500 V voltage waveform Recommended external surge suppressor: Cambium Networks Model # C000000L033A

> 40 Years IP66, IP67

-40C to +60C (-40F to +140F), 0-95% non-

condensing Weight Connectorized Approx. 2.0 kg (4.5 lbs) Integrated Approx. 2.5 kg (5.5 lbs) Wind Survival Connectorized 322 km/h (200 mi/h) Integrated 200 km/h (124 mi/h) Dimension (HxWxD) Connectorized 26.0 x 13.4 x 6.4 cm (10.3 x 5.3 x 3.3) Integrated 37.0 x 37.0 x 6.3 cm (14.5 x 14.5 x 3.2) Power Consumption Input Voltage Mounting Security Encryption 15 W typical, 25 W max, 55 W max with Aux port PoE out enabled 48-59 V DC, 802.3at compliant Wall or Pole mount with Cambium Networks Model #

N000045L002A 128-bit AES and 256-bit AES Page 4-15 Chapter 4: Reference information Equipment specifications Category Specification Note AES-256 requires a license key. Page 4-16 Chapter 4: Reference information Equipment specifications Specifications for PMP 450i Series - SM The PMP 450i SM conforms to the specifications listed in Table 159. Table 159 PMP 450i Series - SM specifications Category Model Number Spectrum Channel Spacing Frequency Range Channel Bandwidth Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Nominal Receive Sensitivity (w/ FEC) @ 5 MHz Channel Specification PMP 450i SM 5, 7, 10, 15, 20, 30, and 40 Channel Bandwidth Configurable on 2.5 MHz increments 3300 3900 MHz 4900 - 5925 MHz 3300 3900 MHz 4900 5925 MHz 5, 7, 10, 15, 20, 30, and 40 MHz 5, 10, 15, 20, 30, and 40 MHz Cambium Proprietary 2x2 MIMO OFDM 10/100/1000BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v2c and v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID 3.5 GHz 3.6 GHz 4.9 GHz 1x = -92.6 dBm, 2x =-89.22 dBm, 4x = -83.19 dBm, 6x = -

76.5 dBm, 8x = -69.1 dBm 1x = -92 dBm, 2x = -88.08 dBm, 4x = -82.3 dBm, 6x = -

75.9 dBm, 8x = -68.6 dBm 1x = -92.5 dBm, 2x = -88.5 dBm, 4x = -81 dBm, 6x = -74.2 dBm, 8x = -66 dBm Page 4-17 Chapter 4: Reference information Equipment specifications Category Nominal Receive Sensitivity (w/ FEC) @ 7 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

10 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

15 MHz Channel 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 3.5 GHz 3.6 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 4.9 GHz Specification 1x = -92 dBm, 2x = -88.7 dBm, 4x = -81.2 dBm, 6x = -74.4 dBm, 8x = -67 dBm 1x = -92 dBm, 2x = -88.8 dBm, 4x = -81.3 dBm, 6x = -74.7 dBm, 8x = -67 dBm 1x = -93 dBm, 2x = -89.1 dBm, 4x = -81.5 dBm, 6x = -74.8 dBm, 8x = -67.4 dBm 1x = -92 dBm, 2x = -88.3 dBm, 4x = -80.8 dBm, 6x = -74 dBm, 8x = -66.2 dBm 1x = -92 dBm, 2x = -88.4 dBm, 4x = -81.4 dBm, 6x = -

75.37 dBm, 8x = -68.1 dBm 1x = -91.02 dBm, 2x = -87.87 dBm, 4x = -80.82 dBm, 6x =

-73.6 dBm, 8x = -67.32 dBm 1x = -90.787 dBm, 2x = -86.6 dBm, 4x = -80.2 dBm, 6x = -

73.52 dBm, 8x = -66.34 dBm 1x = -89.8 dBm, 2x = -86 dBm, 4x = -79.84 dBm, 6x = -

72.92 dBm, 8x = -66 dBm 1x = -90.2 dBm, 2x = -85.2 dBm, 4x = -78.8 dBm, 6x = -

71.4 dBm, 8x = -64.5 dBm 1x = -90.4 dBm, 2x = -85.6 dBm, 4x = -79.2 dBm, 6x = -

71.7 dBm, 8x = -64.2 dBm 1x = -90.6 dBm, 2x = -85.5 dBm, 4x = -79 dBm, 6x = -71.8 dBm, 8x = -64.5 dBm 1x = -90 dBm, 2x = -85.8 dBm, 4x = -78.5 dBm, 6x = -72.2 dBm, 8x = -65.8 dBm 1x = -89.9 dBm, 2x = -84.9 dBm, 4x = -78.5 dBm, 6x = -

71.2 dBm, 8x = -63.8 dBm 1x = -88.57 dBm, 2x = -84.5 dBm, 4x = -78.4 dBm, 6x = -

71.47 dBm, 8x = -65.22 dBm 1x = -87.6 dBm, 2x = -84.1 dBm, 4x = -77.1 dBm, 6x = -

71.03 dBm, 8x = -64.8 dBm 1x = -88.2 dBm, 2x = -83.1 dBm, 4x = -76.9 dBm, 6x = -

70.5 dBm, 8x = -62.3 dBm Page 4-18 Chapter 4: Reference information Equipment specifications Category Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 4.9 GHz 5.1 GHz Specification 1x = -88.4 dBm, 2x = -83.6 dBm, 4x = -77.3 dBm, 6x = -71 dBm, 8x = -62.9 dBm 1x = -88.6 dBm, 2x = -83.6 dBm, 4x = -77.5 dBm, 6x = -

70.2 dBm, 8x = -62.9 dBm 1x = -87.7 dBm, 2x = -83.9 dBm, 4x = -76.6 dBm, 6x = -

70.4 dBm, 8x = -63 dBm 1x = -88 dBm, 2x = -82.9 dBm, 4x = -76.7 dBm, 6x = -69.4 dBm, 8x = -62.3 dBm 1x = -87 dBm, 2x = -83.45 dBm, 4x = -76.25 dBm, 6x = -

70.33 dBm, 8x = -63.23 dBm 1x = -86.9 dBm, 2x = -82.9 dBm, 4x = -76.9 dBm, 6x = -

69.8 dBm, 8x = -62.8 dBm 1x = -87 dBm, 2x = -81.8 dBm, 4x = -75.8 dBm, 6x = -68.5 dBm, 8x = -61.4 dBm 1x = -87.4 dBm, 2x = -82.5 dBm, 4x = -76 dBm, 6x = -69 dBm, 8x = -61.5 dBm 1x = -87 dBm, 2x = -82.6 dBm, 4x = -75.4 dBm, 6x = -69.1 dBm, 8x = -61.8 dBm 1x = -87 dBm, 2x = -82.8 dBm, 4x = -75.6 dBm, 6x = -69.3 dBm, 8x = -61.6 dBm 1x = -85.9 dBm, 2x = -81.5 dBm, 4x = -74.8 dBm, 6x = -

68.7 dBm, 8x = -61.2 dBm 1x = -86 dBm, 2x = -80.9 dBm, 4x = -75 dBm, 6x = -67.9 dBm, 8x = -61.1 dBm 1x = -85.5 dBm, 2x = -80.6 dBm, 4x = -74.5 dBm, 6x = -

67.5 dBm, 8x = -61 dBm 1x = -84.9 dBm, 2x = -80.9 dBm, 4x = -73.2 dBm, 6x = -

67.4 dBm, 8x = -59.3 dBm 1x = -85.1 dBm, 2x = -81 dBm, 4x = -74 dBm, 6x = -67.9 dBm, 8x = -59.8 dBm Page 4-19 Chapter 4: Reference information Equipment specifications Category Nominal Receive Sensitivity (w/ FEC) @

40 MHz Channel 5.2 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz Performance ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Specification 1x = -85.4 dBm, 2x = -80.4 dBm, 4x = -73.3 dBm, 6x = -68 dBm, 8x = -59.9 dBm 1x = -85.2 dBm, 2x = -80.2 dBm, 4x = -74.1 dBm, 6x = -

67.9 dBm, 8x = -59.8 dBm 1x = -84.9 dBm, 2x = -80 dBm, 4x = -73.2 dBm, 6x = -67.4 dBm, 8x = -59.4 dBm 1x = -83.2 dBm, 2x = -79 dBm, 4x = -72.4 dBm, 6x = -66 dBm, 8x = -58.4 dBm 1x = -82.5 dBm, 2x = -79 dBm, 4x = -71.3 dBm, 6x = -65.4 dBm, 8x = -58.3 dBm 1x=-84.2 dBm, 2x=-79.3 dBm, 4x=-72.3 dBm, 6x=-66 dBm, 8x=-56.8 dBm 1x=-84 dBm, 2x=-79.1 dBm, 4x=-73 dBm, 6x=-66 dBm, 8x=-57.8 dBm 1x=-84.2 dBm, 2x=-79.3 dBm, 4x=-73.1 dBm, 6x=-66 dBm, 8x=-56.9 dBm 1x=-84.2 dBm, 2x=-79.1 dBm, 4x=-73.1 dBm, 6x=-66 dBm, 8x=-56.9 dBm 1x=-83.6 dBm, 2x=-78.7 dBm, 4x=-72.5 dBm, 6x=-66.4 dBm, 8x=-56.3 dBm Yes 1/16 2.5 ms or 5.0 ms Modulation Levels MCS SNR (in dB) QPSK 16QAM 64QAM 256QAM 10 17 24 32 2x 4x 6x 8x Page 4-20 Chapter 4: Reference information Equipment specifications Category Latency Maximum Deployment Range GPS Synchronization Quality of Service Link Budget Antenna Beam Width Specification 3 - 5 ms Up to 40 miles (64 km) Yes, via Autosync (CMM4) Diffserv QoS 10 azimuth for 23 dBi integrated antenna Antenna Gain (Does not include cable loss, ~1dB) 5 GHz 3 GHz

+23 dBi H+V, integrated or external

+19 dBi dual slant, integrated or external Transmit Power Range Maximum Transmit Power Physical Sync/AUX port RJ45 Antenna Connection Surge Suppression EN61000-4-5 Mean Time Between Failure Environmental Temperature / Humidity 40 dB dynamic range (to EIRP limit by region) (1 dB step)

+27 dBm combined output (for 5 GHz)

+25 dBm combined output (for 3 GHz) 10/100/1000BASE-T Ethernet Data PoE output (planned for future release) Sync input or output (Connection and powering of UGPS Sync input) 50 ohm, N-type (Connectorized version only) EN61000-4-5: 1.2us/50us, 500 V voltage waveform Recommended external surge suppressor: Cambium Networks Model # C000000L033A

> 40 Years IP66, IP67

-40C to +60C (-40F to +140F), 0-95% non-

condensing Weight Connectorized Approx. 2.0 kg (4.5 lbs) Integrated Approx. 2.5 kg (5.5 lbs) Wind Survival Connectorized 322 km/h (200 mi/h) Page 4-21 Chapter 4: Reference information Equipment specifications Category Specification Integrated 200 km/h (124 mi/h) Dimension (HxWxD) Connectorized 26.0 x 13.4 x 6.4 cm (10.3 x 5.3 x 3.3) Integrated 31.0 x 31.0 x 6.4 cm (12 x 12 x 2.5) Power Consumption Input Voltage Mounting Security Encryption 15 W typical, 25 W max, 55 W max with Aux port PoE out enabled 48-59 V DC, 802.3at compliant Wall or Pole mount with Cambium Networks Model #

N000045L002A 128-bit AES and 256-bit AES Note AES-256 requires a license key. Page 4-22 Chapter 4: Reference information Equipment specifications Specifications for PTP 450i Series - BH The PTP 450i BH conforms to the specifications listed in Table 160. Table 160 PTP 450i Series - BH specifications Category Model Number Spectrum Channel Spacing Frequency Range Channel Bandwidth Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Nominal Receive Sensitivity (w/ FEC) @ 5 MHz Channel 4900 5925 MHz 3.5 GHz 3.6 GHz 4.9 GHz 5.1 GHz 5.2 GHz Specification PTP 450i BH 5, 7, 10, 15, 20, 30, and 40 MHz Channel Bandwidth Configurable on 2.5 MHz increments 4900 - 5925 MHz 5, 10, 15, 20, 30, and 40 MHz Cambium Proprietary 2x2 MIMO OFDM 10/100/1000BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v2c and v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID 1x = -92.7 dBm, 2x = -88.7 dBm, 4x = -82.7 dBm, 6x = -

75.8 dBm, 8x = -69 dBm 1x = -92.7 dBm, 2x = -87.3 dBm, 4x = -81 dBm, 6x = -74.9 dBm, 8x = -68.3 dBm 1x = -93 dBm, 2x = -88.3 dBm, 4x = -82 dBm, 6x = -74.4 dBm, 8x = -67.9 dBm 1x = -93 dBm, 2x = -88.7 dBm, 4x = -81.2 dBm, 6x = -74.7 dBm, 8x = -67.6 dBm 1x = -93 dBm, 2x = -89 dBm, 4x = -81.5 dBm, 6x = -75 dBm, 8x = -67.5 dBm Page 4-23 Chapter 4: Reference information Equipment specifications Category Specification Nominal Receive Sensitivity (w/ FEC) @ 7 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

10 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

15 MHz Channel 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 3.5 GHz 3.6 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 1x = -93 dBm, 2x = -88.4 dBm, 4x = -81.3 dBm, 6x = -75.5 dBm, 8x = -67.8 dBm 1x = -93.2 dBm, 2x = -88.3 dBm, 4x = -80.8 dBm, 6x = -

74.3 dBm, 8x = -66.8 dBm 1x = -91.8 dBm, 2x = -87.7 dBm, 4x = -80.8 dBm, 6x = -

74.7 dBm, 8x = -67.3 dBm 1x = -90.0 dBm, 2x = -87.0 dBm, 4x = -79.8 dBm, 6x = -

73.8 dBm, 8x = -67.2 dBm 1x = -90.2 dBm, 2x = -86.2 dBm, 4x = -80.0 dBm, 6x = -

73.1 dBm, 8x = -66.7 dBm 1x = -89.5 dBm, 2x = -85.7 dBm, 4x = -79.8 dBm, 6x = -

72.8 dBm, 8x = -66.3 dBm 1x = -90 dBm, 2x = -85 dBm, 4x = -78.6 dBm, 6x = -

72.5dBm, 8x = -65 dBm 1x = -90.4 dBm, 2x = -85.4 dBm, 4x = -79 dBm, 6x = -73 dBm, 8x = -65.5 dBm 1x = -90.4 dBm, 2x = -85.5 dBm, 4x = -79.2 dBm, 6x = -72 dBm, 8x = -65 dBm 1x = -87.6 dBm, 2x = -82.5 dBm, 4x = -76.5 dBm, 6x = -

70.5 dBm, 8x = -61.5dBm 1x = -89.9 dBm, 2x = -84.8 dBm, 4x = -78.5 dBm, 6x = -

71.4 dBm, 8x = -64 dBm 1x = -89.0 dBm, 2x = -84.0 dBm, 4x = -77.9 dBm, 6x = -

72.0 dBm, 8x = -64.8 dBm 1x = -87.6 dBm, 2x = -83.7 dBm, 4x = -77.5 dBm, 6x = -

71.6 dBm, 8x = -64.5 dBm 1x = -88 dBm, 2x = -83.9 dBm, 4x = -76.9 dBm, 6x = -70.7 dBm, 8x = -63.6 dBm 1x = -89.3 dBm, 2x = -83.3 dBm, 4x = -76.9 dBm, 6x = -

70.7 dBm, 8x = -63.6 dBm 1x = -88.5 dBm, 2x = -83.3 dBm, 4x = -76.9 dBm, 6x = -

70.7 dBm, 8x = -63 dBm 1x = -88 dBm, 2x = -84.2 dBm, 4x = -76.9 dBm, 6x = -70.8 dBm, 8x = -62.7 dBm 1x = -87.8 dBm, 2x = -82.8 dBm, 4x = -76.6 dBm, 6x =

69.3 dBm, 8x = -62.1 dBm Page 4-24 Chapter 4: Reference information Equipment specifications Category Specification Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

40 MHz Channel 3.5 GHz 3.6 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 4.9 GHz 5.1 GHz 1x = -87.4 dBm, 2x = -83.0 dBm, 4x = -76.9 dBm, 6x = -

69.9 dBm, 8x = -63.0 dBm 1x = -86.4 dBm, 2x = -82.5 dBm, 4x = -76.4 dBm, 6x = -

69.4 dBm, 8x = -62.9 dBm 1x = -86.9 dBm, 2x = -82.5 dBm, 4x = -75.7 dBm, 6x = -

69.4 dBm, 8x = -62.3 dBm 1x = -87.3 dBm, 2x = -83.3 dBm, 4x = -76 dBm, 6x = -69.9 dBm, 8x = -62.6 dBm 1x = -87.4 dBm, 2x = -82.6 dBm, 4x = -75.4 dBm, 6x = -

69.2 dBm, 8x = -62 dBm 1x = -84.5 dBm, 2x = -80.5 dBm, 4x = -73.4 dBm, 6x = -

66.4 dBm, 8x = -56.4 dBm 1x = -85.8 dBm, 2x = -81.7 dBm, 4x = -75 dBm, 6x = -68.4 dBm, 8x = -61.2 dBm 1x = -86.4 dBm, 2x = -81.7 dBm, 4x = -75.1 dBm, 6x = -68 dBm, 8x = -62 dBm 1x = -85.5 dBm, 2x = -80.6 dBm, 4x = -74.4 dBm, 6x = -

68.4 dBm, 8x = -61.5 dBm 1x = -85 dBm, 2x = -80.7 dBm, 4x = -73.7 dBm, 6x = -66.5 dBm, 8x = -60 dBm 1x = -85 dBm, 2x = -81 dBm, 4x = -74 dBm, 6x = -68 dBm, 8x = -60.7 dBm 1x = -85.2 dBm, 2x = -80.4 dBm, 4x = -74.2 dBm, 6x = -

67.1 dBm, 8x = -60 dBm 1x = -85.3 dBm, 2x = -80.5 dBm, 4x = -74.2 dBm, 6x = -

67.2 dBm, 8x = -60 dBm 1x = -84.6 dBm, 2x = -80 dBm, 4x = -73,3 dBm, 6x = -66.5 dBm, 8x = -59.1 dBm 1x=-83.7 dBm, 2x=-79.6 dBm, 4x=-73.5 dBm, 6x=-66.7 dBm, 8x=-58.6 dBm 1x=-83.4 dBm, 2x=-79.3 dBm, 4x=-72.3 dBm, 6x=-66 dBm, 8x=-58.0 dBm 1x=-84.1 dBm, 2x=-79.3 dBm, 4x=-73 dBm, 6x=-66 dBm, 8x=-58.8 dBm 1x=-84.4 dBm, 2x=-79.7 dBm, 4x=-73.5 dBm, 6x=-67.2 dBm, 8x=-59.2 dBm Page 4-25 Chapter 4: Reference information Equipment specifications Category Specification 5.2 GHz 5.4 GHz 5.8 GHz 1x=-84.7 dBm, 2x=-79.4 dBm, 4x=-73.2 dBm, 6x=-66.8 dBm, 8x=-59 dBm 1x=-84.5 dBm, 2x=-79.4 dBm, 4x=-73.3 dBm, 6x=-66.5 dBm, 8x=-58 dBm 1x=-84 dBm, 2x=-79 dBm, 4x=-72 dBm, 6x=-66 dBm, 8x=-58 dBm Performance ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Latency Maximum Deployment Range GPS Synchronization Quality of Service Link Budget Yes 1/16 2.5 ms or 5.0 ms Modulation Levels MCS SNR (in dB) 2x 4x 6x 8x QPSK 16QAM 64QAM 256QAM 10 17 24 32 3 - 5 ms Up to 40 miles (64 km) Yes, via Autosync (CMM4) Diffserv QoS Antenna Beam Width 900 MHz 37 azimuth for 12 dBi Yagi antenna Antenna Gain (Does not include cable loss, ~1dB) Transmit Power Range Maximum Transmit Power 5 GHz 10 azimuth for 23 dBi integrated antenna 900 MHz 12 dBi Yagi antenna 5 GHz

+23 dBi H+V, integrated or external 40 dB dynamic range (to EIRP limit by region) (1 dB step)

+27 dBm combined output Page 4-26 Chapter 4: Reference information Equipment specifications Category Physical Specification Sync/AUX port RJ45 Antenna Connection Surge Suppression EN61000-4-5 Mean Time Between Failure Environmental Temperature / Humidity 10/100/1000BASE-T Ethernet Data PoE output Sync input or output (Connection and powering of UGPS Sync input) 50 ohm, N-type (Connectorized version only) EN61000-4-5: 1.2 us/50us, 500 V voltage waveform Recommended external surge suppressor: Cambium Networks Model # C000000L033A

> 40 Years IP66, IP67

-40C to +60C (-40F to +140F), 0-95% non-condensing Weight Connectorized Approx. 2.0 kg (4.5 lbs) Integrated Approx. 2.5 kg (5.5 lbs) Wind Survival Connectorized 322 km/h (200 mi/h) Integrated 200 km/h (124 mi/h) Dimension (HxWxD) Connectorized 26.0 x 13.4 x 6.4 cm (10.25 x 5.25 x 3.25) Integrated 31.0 x 31.0 x 6.4 cm (12 x 12 x 2.5) Power Consumption Input Voltage Mounting Security Encryption 15 W typical, 25 W max, 55 W max with Aux port PoE out enabled 48-59 V DC, 802.3at compliant Wall or Pole mount with Cambium Networks Model

#N000045L002A 128-bit AES and 256-bit AES Note AES-256 requires a license key. Page 4-27 Chapter 4: Reference information Equipment specifications Specifications for PMP/PTP 450b Mid-Gain Series - SM The PMP/PTP 450b Mid-Gain SM conforms to the specifications listed in Table 161. Table 161 PMP/PTP 450b Mid-Gain Series - SM specifications Category Model Number Spectrum Channel Spacing Frequency Range Channel Bandwidth Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Nominal Receive Sensitivity (w/ FEC) @ 5 MHz Channel 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz Specification PMP 450b Mid-Gain SM Configurable in 2.5 MHz increments 4900 - 5925 MHz 5, 10, 15, 20, 30, and 40 MHz Cambium Proprietary 2x2 MIMO OFDM 100/1000BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v2c and v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID 1x = -92.5 dBm, 2x = -88.5 dBm, 4x = -81 dBm, 6x = -74.2 dBm, 8x = -66 dBm 1x = -93 dBm, 2x = -89.1 dBm, 4x = -81.5 dBm, 6x = -74.8 dBm, 8x = -67.4 dBm 1x = -92 dBm, 2x = -88.3 dBm, 4x = -80.8 dBm, 6x = -74 dBm, 8x = -66.2 dBm 1x = -93 dBm, 2x = -89.1 dBm, 4x = -81.5 dBm, 6x = -74.8 dBm, 8x = -67.4 dBm 1x = -92 dBm, 2x = -88.3 dBm, 4x = -80.8 dBm, 6x = -74 dBm, 8x = -66.2 dBm 1x = -90.2 dBm, 2x = -85.2 dBm, 4x = -78.8 dBm, 6x = -71.4 dBm, 8x = -64.5 dBm Page 4-28 Chapter 4: Reference information Equipment specifications Category Nominal Receive Sensitivity (w/ FEC) @

10 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

15 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz Specification 1x = -90 dBm, 2x = -85.8 dBm, 4x = -78.5 dBm, 6x = -72.2 dBm, 8x = -65.8 dBm 1x = -89.9 dBm, 2x = -84.9 dBm, 4x = -78.5 dBm, 6x = -71.2 dBm, 8x = -63.8 dBm 1x = -90 dBm, 2x = -85.8 dBm, 4x = -78.5 dBm, 6x = -72.2 dBm, 8x = -65.8 dBm 1x = -89.9 dBm, 2x = -84.9 dBm, 4x = -78.5 dBm, 6x = -71.2 dBm, 8x = -63.8 dBm 1x = -88.2 dBm, 2x = -83.1 dBm, 4x = -76.9 dBm, 6x = -70.5 dBm, 8x = -62.3 dBm 1x = -87.7 dBm, 2x = -83.9 dBm, 4x = -76.6 dBm, 6x = -

70.4 dBm, 8x = -63 dBm 1x = -88 dBm, 2x = -82.9 dBm, 4x = -76.7 dBm, 6x = -69.4 dBm, 8x = -62.3 dBm 1x = -87.7 dBm, 2x = -83.9 dBm, 4x = -76.6 dBm, 6x = -

70.4 dBm, 8x = -63 dBm 1x = -88 dBm, 2x = -82.9 dBm, 4x = -76.7 dBm, 6x = -69.4 dBm, 8x = -62.3 dBm 1x = -87 dBm, 2x = -81.8 dBm, 4x = -75.8 dBm, 6x = -68.5 dBm, 8x = -61.4 dBm 1x = -87 dBm, 2x = -82.8 dBm, 4x = -75.6 dBm, 6x = -69.3 dBm, 8x = -61.6 dBm 1x = -85.9 dBm, 2x = -81.5 dBm, 4x = -74.8 dBm, 6x = -68.7 dBm, 8x = -61.2 dBm 1x = -87 dBm, 2x = -82.8 dBm, 4x = -75.6 dBm, 6x = -69.3 dBm, 8x = -61.6 dBm 1x = -85.9 dBm, 2x = -81.5 dBm, 4x = -74.8 dBm, 6x = -68.7 dBm, 8x = -61.2 dBm 1x = -84.9 dBm, 2x = -80.9 dBm, 4x = -73.2 dBm, 6x = -

67.4 dBm, 8x = -59.3 dBm Page 4-29 Chapter 4: Reference information Equipment specifications Category Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

40 MHz Channel 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz Specification 1x = -85.2 dBm, 2x = -80.2 dBm, 4x = -74.1 dBm, 6x = -67.9 dBm, 8x = -59.8 dBm 1x = -84.9 dBm, 2x = -80 dBm, 4x = -73.2 dBm, 6x = -67.4 dBm, 8x = -59.4 dBm 1x = -85.2 dBm, 2x = -80.2 dBm, 4x = -74.1 dBm, 6x = -67.9 dBm, 8x = -59.8 dBm 1x = -84.9 dBm, 2x = -80 dBm, 4x = -73.2 dBm, 6x = -67.4 dBm, 8x = -59.4 dBm 1x=-84.2 dBm, 2x=-79.3 dBm, 4x=-72.3 dBm, 6x=-66 dBm, 8x=-56.8 dBm 1x=-84.2 dBm, 2x=-79.1 dBm, 4x=-73.1 dBm, 6x=-66 dBm, 8x=-56.9 dBm 1x=-83.6 dBm, 2x=-78.7 dBm, 4x=-72.5 dBm, 6x=-66.4 dBm, 8x=-56.3 dBm 1x=-84.2 dBm, 2x=-79.1 dBm, 4x=-73.1 dBm, 6x=-66 dBm, 8x=-56.9 dBm 1x=-83.6 dBm, 2x=-78.7 dBm, 4x=-72.5 dBm, 6x=-66.4 dBm, 8x=-56.3 dBm Performance ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Latency Yes 1/16 2.5 ms or 5.0 ms Modulation Levels MCS SNR (in dB) QPSK 16QAM 64QAM 256QAM 10 17 24 32 2x 4x 6x 8x 3 - 5 ms Page 4-30 Chapter 4: Reference information Equipment specifications Category Maximum Deployment Range GPS Synchronization Quality of Service Link Budget Antenna Beam Width Specification Up to 40 miles (64 km) Yes, via Autosync (CMM4) Diffserv QoS 15 azimuth for 16 dBi integrated antenna 30 elevation for 16 dBi integrated antenna Antenna Gain 5 GHz

+16 dBi H+V, integrated Transmit Power Range Maximum Transmit Power Physical Sync/AUX port RJ45 Antenna Connection Surge Suppression EN61000-4-5 Mean Time Between Failure Environmental Temperature / Humidity 40 dB dynamic range (to EIRP limit by region) (1 dB step)

+27 dBm combined output 100/1000BASE-T Ethernet Data PoE output (planned for future release) Sync input or output (Connection and powering of UGPS Sync input) 50 ohm, N-type (Connectorized version only) EN61000-4-5: 10us/700us, Level 4, 4kV voltage waveform Recommended surge suppressor: Cambium Networks Model # C000000L065A

> 40 Years IP55

-40C to +60C (-40F to +140F), 0-95% non-

condensing Weight Integrated Approx. 0.5 kg (1.1 lb. including mounting bracket) Wind Survival Integrated 190 km/h (118 mi/h) Dimension (HxWxD) Integrated 12.4 x 25.1 x 11.9 cm (4.9 x 9.9 x 4.7) Power Consumption Input Voltage 9 W nominal, 12 W peak 20 - 32 V DC, Page 4-31 Chapter 4: Reference information Equipment specifications Category Mounting Security Encryption Specification Wall or Pole mount 128-bit AES and 256-bit AES Note AES-256 requires a license key. Page 4-32 Chapter 4: Reference information Equipment specifications Specifications for PMP/PTP 450b High Gain Series - SM The PMP/PTP 450b High Gain SM conforms to the specifications listed in Table 162. Table 162 PMP/PTP 450b High Gain Series - SM specifications Category Model Number Spectrum Channel Spacing Frequency Range Channel Bandwidth Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Nominal Receive Sensitivity (w/ FEC) @ 5 MHz Channel 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz Specification PMP 450b High Gain SM Configurable in 2.5 MHz increments 4900 - 5925 MHz 5, 10, 15, 20, 30, and 40 MHz Cambium Proprietary 2x2 MIMO OFDM 100/1000BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v2c and v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID 1x = -92.5 dBm, 2x = -88.5 dBm, 4x = -81 dBm, 6x = -74.2 dBm, 8x = -66 dBm 1x = -93 dBm, 2x = -89.1 dBm, 4x = -81.5 dBm, 6x = -74.8 dBm, 8x = -67.4 dBm 1x = -92 dBm, 2x = -88.3 dBm, 4x = -80.8 dBm, 6x = -74 dBm, 8x = -66.2 dBm 1x = -93 dBm, 2x = -89.1 dBm, 4x = -81.5 dBm, 6x = -74.8 dBm, 8x = -67.4 dBm 1x = -92 dBm, 2x = -88.3 dBm, 4x = -80.8 dBm, 6x = -74 dBm, 8x = -66.2 dBm 1x = -90.2 dBm, 2x = -85.2 dBm, 4x = -78.8 dBm, 6x = -71.4 dBm, 8x = -64.5 dBm Page 4-33 Chapter 4: Reference information Equipment specifications Category Nominal Receive Sensitivity (w/ FEC) @

10 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

15 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz Specification 1x = -90 dBm, 2x = -85.8 dBm, 4x = -78.5 dBm, 6x = -72.2 dBm, 8x = -65.8 dBm 1x = -89.9 dBm, 2x = -84.9 dBm, 4x = -78.5 dBm, 6x = -71.2 dBm, 8x = -63.8 dBm 1x = -90 dBm, 2x = -85.8 dBm, 4x = -78.5 dBm, 6x = -72.2 dBm, 8x = -65.8 dBm 1x = -89.9 dBm, 2x = -84.9 dBm, 4x = -78.5 dBm, 6x = -71.2 dBm, 8x = -63.8 dBm 1x = -88.2 dBm, 2x = -83.1 dBm, 4x = -76.9 dBm, 6x = -70.5 dBm, 8x = -62.3 dBm 1x = -87.7 dBm, 2x = -83.9 dBm, 4x = -76.6 dBm, 6x = -

70.4 dBm, 8x = -63 dBm 1x = -88 dBm, 2x = -82.9 dBm, 4x = -76.7 dBm, 6x = -69.4 dBm, 8x = -62.3 dBm 1x = -87.7 dBm, 2x = -83.9 dBm, 4x = -76.6 dBm, 6x = -

70.4 dBm, 8x = -63 dBm 1x = -88 dBm, 2x = -82.9 dBm, 4x = -76.7 dBm, 6x = -69.4 dBm, 8x = -62.3 dBm 1x = -87 dBm, 2x = -81.8 dBm, 4x = -75.8 dBm, 6x = -68.5 dBm, 8x = -61.4 dBm 1x = -87 dBm, 2x = -82.8 dBm, 4x = -75.6 dBm, 6x = -69.3 dBm, 8x = -61.6 dBm 1x = -85.9 dBm, 2x = -81.5 dBm, 4x = -74.8 dBm, 6x = -68.7 dBm, 8x = -61.2 dBm 1x = -87 dBm, 2x = -82.8 dBm, 4x = -75.6 dBm, 6x = -69.3 dBm, 8x = -61.6 dBm 1x = -85.9 dBm, 2x = -81.5 dBm, 4x = -74.8 dBm, 6x = -68.7 dBm, 8x = -61.2 dBm 1x = -84.9 dBm, 2x = -80.9 dBm, 4x = -73.2 dBm, 6x = -

67.4 dBm, 8x = -59.3 dBm Page 4-34 Chapter 4: Reference information Equipment specifications Category Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

40 MHz Channel 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz 4.9 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.8 GHz Specification 1x = -85.2 dBm, 2x = -80.2 dBm, 4x = -74.1 dBm, 6x = -67.9 dBm, 8x = -59.8 dBm 1x = -84.9 dBm, 2x = -80 dBm, 4x = -73.2 dBm, 6x = -67.4 dBm, 8x = -59.4 dBm 1x = -85.2 dBm, 2x = -80.2 dBm, 4x = -74.1 dBm, 6x = -67.9 dBm, 8x = -59.8 dBm 1x = -84.9 dBm, 2x = -80 dBm, 4x = -73.2 dBm, 6x = -67.4 dBm, 8x = -59.4 dBm 1x=-84.2 dBm, 2x=-79.3 dBm, 4x=-72.3 dBm, 6x=-66 dBm, 8x=-56.8 dBm 1x=-84.2 dBm, 2x=-79.1 dBm, 4x=-73.1 dBm, 6x=-66 dBm, 8x=-56.9 dBm 1x=-83.6 dBm, 2x=-78.7 dBm, 4x=-72.5 dBm, 6x=-66.4 dBm, 8x=-56.3 dBm 1x=-84.2 dBm, 2x=-79.1 dBm, 4x=-73.1 dBm, 6x=-66 dBm, 8x=-56.9 dBm 1x=-83.6 dBm, 2x=-78.7 dBm, 4x=-72.5 dBm, 6x=-66.4 dBm, 8x=-56.3 dBm Performance ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Latency Yes 1/16 2.5 ms or 5.0 ms Modulation Levels MCS SNR (in dB) QPSK 16QAM 64QAM 256QAM 10 17 24 32 2x 4x 6x 8x 3 - 5 ms Page 4-35 Chapter 4: Reference information Equipment specifications Category Maximum Deployment Range GPS Synchronization Quality of Service Link Budget Antenna Beam Width Specification Up to 40 miles (64 km) Yes, via Autosync (CMM4) Diffserv QoS 7 azimuth for 23 dBi integrated antenna 7 elevation for 23 dBi integrated antenna Antenna Gain 5 GHz

+23 dBi H+V, integrated Transmit Power Range Maximum Transmit Power Physical Sync/AUX port RJ45 Antenna Connection Surge Suppression EN61000-4-5 Mean Time Between Failure Environmental Temperature / Humidity 22 dB dynamic range (to EIRP limit by region) (1 dB step)

+27 dBm combined output (+22 dBm @ 256QAM) 100/1000BASE-T Ethernet Data PoE output (planned for future release) Sync input or output (Connection and powering of UGPS Sync input) 50 ohm, N-type (Connectorized version only) EN61000-4-5: 10us/700us, Level 4, 4kV voltage waveform Recommended surge suppressor: Cambium Networks Model # C000000L065A

> 40 Years IP67

-40C to +60C (-40F to +140F), 0-95% non-

condensing Weight Integrated Approx. 3.1 kg (7 lb. including mounting bracket) Wind Survival Integrated 145 km/h (90 mi/h) Dimension (HxWxD) Integrated 47 cm diameter x 28 cm (18.5 diameter x 11.2) Power Consumption Input Voltage 9 W nominal, 12 W peak 20 - 32 V DC, Page 4-36 Chapter 4: Reference information Equipment specifications Category Mounting Security Encryption Specification Wall or Pole mount 128-bit AES and 256-bit AES Note AES-256 requires a license key. Page 4-37 Chapter 4: Reference information Equipment specifications Specifications for PMP 450 Series - AP The PMP 450 AP conforms to the specifications listed in Table 163. Table 163 PMP 450 Series - AP specifications Category Model Number Spectrum Channel Spacing Specification PMP 450 AP 5, 7, 10, 15, 20 and 30 MHz Channel Bandwidth Configurable on 2.5 MHz increments Frequency Range 2.4 GHz 2400 2483.5 MHz 3.5 GHz 3.65 GHz 5 GHz 3300 3600 MHz 3500 3850 MHz 5470 5875 MHz Channel Bandwidth 3.5 and 3.65 GHz 5, 7, 10, 15, 20 and 30 MHz 2.4 and 5 GHz 5, 10, 15, 20 and 30 MHz OFDM Subcarriers Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity Nominal Receive Sensitivity (w/ FEC) @

5 MHz Channel 2.4 GHz 3.5 GHz 512 FFT Cambium Proprietary 2x2 MIMO OFDM 10/100/1000BaseT, half/full duplex, rate auto negotiated (802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP, TFTP, RADIUS HTTP, HTTPS, Telnet, FTP, SNMP v3, TFTP, Syslog 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID 1x = -92 dBm, 2x = -87.8 dBm, 4x = -80.4 dBm, 6x = -

74.4 dBm, 8x = -66.5 dBm 1x = -92.4 dBm, 2x = -88.3 dBm, 4x = -81.3 dBm, 6x = -

75.3 dBm, 8x = -67.7 dBm Page 4-38 Chapter 4: Reference information Equipment specifications Category Specification 3.65 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.65 GHz 2.4 GHz 3.5 GHz 3.65 GHz 5.4 GHz 5.8 GHz 2.4 GHz 3.5 GHz 3.65 GHz 5.4 GHz 5.8 GHz 2.4 GHz 3.5 GHz Nominal Receive Sensitivity (w/ FEC) @

7 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

10 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

15 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel 1x = -91 dBm, 2x = -86.1 dBm, 4x = -80.2 dBm, 6x = -

73.1 dBm, 8x = -66 dBm 1x = -88.7 dBm, 2x = -84 dBm, 4x = -77.6 dBm, 6x = -

71.6 dBm, 8x = -63.7 dBm 1x = -91.5 dBm, 2x = -87 dBm, 4x = -80.2 dBm, 6x = -

73.1 dBm, 8x = -66 dBm 1x = -90.5 dBm, 2x = -86.4 dBm, 4x = -80.3 dBm, 6x =

-73.4 dBm, 8x = -66.9 dBm 1x = -89.1 dBm, 2x = -85.1 dBm, 4x = -78.1 dBm, 6x = -

72.1 dBm, 8x = -64.5 dBm 1x = -89.9 dBm, 2x = -85.6 dBm, 4x = -80 dBm, 6x = -

73.5 dBm, 8x = -66.9 dBm 1x = -89.8 dBm, 2x = -85.6 dBm, 4x = -80 dBm, 6x = -

73 dBm, 8x = -66.3 dBm 1x = -89 dBm, 2x = -85.2 dBm, 4x = -78.1 dBm, 6x = -

72.1 dBm, 8x = -64.5 dBm 1x = -86.1 dBm, 2x = -82.2 dBm, 4x = -75.3 dBm, 6x = -

69.3 dBm, 8x = -61.3 dBm 1x = -86 dBm, 2x = -82.2 dBm, 4x = -75.1 dBm, 6x = -69 dBm, 8x = -60 dBm 1x = -88.4 dBm, 2x = -84.1 dBm, 4x = -77.1 dBm, 6x = -

71.4 dBm, 8x = -65 dBm 1x = -88.5 dBm, 2x = -84.5 dBm, 4x = -77.5 dBm, 6x = -

71.5 dBm, 8x = -64.3 dBm 1x = -87.4 dBm, 2x = -83.7 dBm, 4x = -76.3 dBm, 6x = -

69.7 dBm, 8x = -62.2 dBm 1x = -84.2 dBm, 2x = -80.2 dBm, 4x = -73.2 dBm, 6x = -

67.2 dBm, 8x = -60 dBm 1x = -85 dBm, 2x = -80 dBm, 4x = -74.3 dBm, 6x = -67 dBm, 8x = -58 dBm 1x = -85 dBm, 2x = -85 dBm, 4x = -79 dBm, 6x = -72 dBm, 8x = -66 dBm 1x = -85 dBm, 2x = -85 dBm, 4x = -79 dBm, 6x = -72 dBm, 8x = -65 dBm Page 4-39 Chapter 4: Reference information Equipment specifications Category Specification Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel 3.65 GHz 5.4 GHz 5.8 GHz 2.4 GHz 3.5 GHz 3.65 GHz 5.4 GHz 5.8 GHz 1x = -86 dBm, 2x = -86 dBm, 4x = -78 dBm, 6x = -71 dBm, 8x = -63 dBm 1x = -81 dBm, 2x = -81 dBm, 4x = -75 dBm, 6x = -68 dBm, 8x = -59 dBm 1x = -82 dBm, 2x = -82 dBm, 4x = -75 dBm, 6x = -69 dBm, 8x = -60 dBm 1x = -85.4 dBm, 2x = -80.4 dBm, 4x = -74 dBm, 6x = -

68 dBm, 8x = -61 dBm 1x = -85.5 dBm, 2x = -81.5 dBm, 4x = -74.5 dBm, 6x = -

68.2 dBm, 8x = -61.3 dBm 1x = -84 dBm, 2x = -79.5 dBm, 4x = -73.4 dBm, 6x = -

66.4 dBm, 8x = -59.2 dBm 1x = -81 dBm, 2x = -76.9 dBm, 4x = -70.9 dBm, 6x = -

63.8 dBm, 8x = -55.8 dBm 1x = -80.9 dBm, 2x = -76.8 dBm, 4x = -70 dBm, 6x = -

63.8 dBm, 8x = -55 dBm Performance Subscribers Per Sector ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Latency Up to 238 Yes 1/16 2.5 ms or 5.0 ms Modulation Levels MCS SNR (in dB) 2x 4x 6x 8x QPSK 16QAM 64QAM 256QAM 10 17 24 32 3 - 5 ms for 2.5 ms Frame Period 6-10 ms for 5.0 ms Frame Period Maximum Deployment Range Up to 40 miles (64 km) Packets Per Second GPS Synchronization 12,500 Yes, via CMM3, CMM4 or UGPS Page 4-40 Chapter 4: Reference information Equipment specifications Category Quality of Service Link Budget Antenna Gain (Does not include cable loss, ~1dB) 2.4 GHz 3.5 GHz Specification Diffserv QoS 18 dBi Dual Slant 16 dBi Dual Slant 3.65 GHz 16 dBi Dual Slant 5 GHz 17 dBi Horizontal and Vertical Combined Transmit Power Maximum Transmit Power Physical Wind Survival Antenna Connection Surge Suppression EN61000-4-5 Environmental

-30 to +22 dBm (to EIRP limit by region) in 1 dB-

configurable intervals (2.4 GHz, 5 GHz)

-30 to +25 dBm (to EIRP limit by region) in 1 dB-

configurable intervals (3.5 GHz)

-30 to +25 dBm (to EIRP limit by region and channel bandwidth) in 1 dB-configurable intervals (3.6 GHz) 22 dBm combined OFDM (2.4 GHz, 5 GHz)

(dependent upon Region Code setting) 25 dBm combined OFDM (3.5 GHz, 3.6 GHz),

(dependent upon Region Code setting) 200 mph (322 kph) 50 ohm, N-type (Connectorized version only) EN61000-4-5: 10us/700us, Level 4, 4kV voltage waveform Recommended surge suppressor: Cambium Networks Model # C000000L065A IP66, IP67 Temperature / Humidity

-40C to +60C (-40F to +140F) /

0-95% non-condensing Weight 2.4 GHz 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 3.5 GHz 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 3.6 GHz 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna Page 4-41 Chapter 4: Reference information Equipment specifications Category 5 GHz Specification 5.9 kg (13 lbs) with antenna 2.5 kg (5.5 lbs) without antenna Dimension (HxWxD) 2.4 GHz Radio: 27 x 21 x 7 cm (10.6 x 8.3 x 2.8) 3.5 GHz 3.6 GHz 5 GHz Antenna: 112.2 x 24.5 x 11.7 cm (44.2 x 9.6 x 4.6) Radio: 27 x 21 x 7 cm (10.6 x 8.3 x 2.8) Radio: 27 x 21 x 7 cm (10.6 x 8.3 x 2.8) Radio: 27 x 21 x 7 cm (10.6 x 8.3 x 2.8) Antenna: 51 x 13 x 7.3 cm (20.2 x 5.1 x 2.9) Power Consumption Input Voltage Security Encryption 14 W 22 to 32 VDC 128-bit AES and 256-bit AES Note AES-256 requires a license key. Page 4-42 Chapter 4: Reference information Equipment specifications Specifications for PMP 450 Series - SM The PMP 450 SM conforms to the specifications listed in Table 164. Table 164 PMP 450 Series - SM specifications Category Model Number Spectrum Channel Spacing Specification PMP 450 SM 5, 7, 10, 15, 20, 30, and 40 MHz Channel Bandwidth Configurable on 2.5 MHz increments Frequency Range 900 MHz 902 928 MHz 2.4 GHz 3.5 GHz 2400 2483.5 MHz 3300 3600 MHz 3.65 GHz 3500 3850 MHz 5 GHz 5470 5875 MHz Channel Bandwidth 900 MHz, 5, 7, 10, 15, and 20 MHz 2.4 GHz, 3.5 GHz, 3.65 GHz and 5 GHz 5, 10, 15, 20, 30, and 40 MHz Note 2.4 GHz band does not support 40 MHz. OFDM Subcarriers Interface 512 FFT MAC (Media Access Control) Layer Cambium Proprietary Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity 2x2 MIMO OFDM 10/100 BaseT, half/full duplex, rate auto negotiated

(802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP HTTP, HTTPS, Telnet, FTP, SNMP v3 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID Page 4-43 Chapter 4: Reference information Equipment specifications Category Specification Nominal Receive Sensitivity (w/ FEC) @

5 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

7 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

10 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

15 MHz Channel 900 MHz 2.4 GHz 3.5 GHz 3.65 GHz 5.4 GHz 5.8 GHz 900 MHz 3.5 GHz 3.65 GHz 900 MHz 2.4 GHz 3.5 GHz 3.65 GHz 5.4 GHz 5.8 GHz 900 MHz 2.4 GHz 3.5 GHz 1x = -91 dBm, 2x = -91 dBm, 4x = -85 dBm, 6x = -78 dBm, 8x = -70 dBm 1x = -92.5 dBm, 2x = -89.9 dBm, 4x = -82.9 dBm, 6x = -

75.9, dBm, 8x = -67.9 dBm 1x = -93.5 dBm, 2x = -89.4 dBm, 4x = -83.5 dBm, 6x = -

76.4 dBm, 8x = -68.3 dBm 1x = -91.3 dBm, 2x = -89.1 dBm, 4x = -82.2 dBm, 6x = -

75.2 dBm, 8x = -67.3 dBm 1x = -89.3 dBm, 2x = -87.3 dBm, 4x = -80.3 dBm, 6x = -

74.3 dBm, 8x = -66.3 dBm 1x = -89 dBm, 2x = -87 dBm, 4x = -80 dBm, 6x = -73.9 dBm, 8x = -64.9 dBm 1x = -91 dBm, 2x = -84 dBm, 4x = -83 dBm, 6x = -77 dBm, 8x = -71 dBm 1x = -92.2 dBm, 2x = -88.5 dBm, 4x = -81.4 dBm, 6x = -

74.5 dBm, 8x = -67.6 dBm 1x = -90.4 dBm, 2x = -87.3 dBm, 4x = -80.6 dBm, 6x =

-73 dBm, 8x = -65.6 dBm 1x = -90 dBm, 2x = -83 dBm, 4x = -80 dBm, 6x = -74 dBm, 8x = -68 dBm 1x = -88 dBm, 2x = -88 dBm, 4x = -81 dBm, 6x = -75 dBm, 8x = -69 dBm 1x = -88 dBm, 2x = -88 dBm, 4x = -81 dBm, 6x = -76 dBm, 8x = -68 dBm 1x = -86 dBm, 2x = -86 dBm, 4x = -80 dBm, 6x = -73 dBm, 8x = -66 dBm 1x = -84 dBm, 2x = -84 dBm, 4x = -78 dBm, 6x = -72 dBm, 8x = -63 dBm 1x = -84 dBm, 2x = -84 dBm, 4x = -77 dBm, 6x = -71 dBm, 8x = -63 dBm 1x = -88.6 dBm, 2x = -85.4 dBm, 4x = -78.1 dBm, 6x = -

72.2 dBm, 8x = -65.2 dBm 1x = -88.5 dBm, 2x = -84.5 dBm, 4x = -77.5 dBm, 6x = -

71.5 dBm, 8x = -64.5 dBm 1x = -89.5 dBm, 2x = -84.5 dBm, 4x = -78.5 dBm, 6x = -

71.5 dBm, 8x = -65.1 dBm Page 4-44 Chapter 4: Reference information Equipment specifications Category Specification Nominal Receive Sensitivity (w/ FEC) @

20 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

40 MHz Channel 3.65 GHz 5.4 GHz 5.8 GHz 900 MHz 2.4 GHz 3.5 GHz 3.65 GHz 5.4 GHz 5.8 GHz 2.4 GHz 3.5 GHz 3.65 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.65 GHz 5.4 GHz 5.8 GHz 1x = -87.3 dBm, 2x = -84.3 dBm, 4x = -77.3 dBm, 6x = -

70.3 dBm, 8x = -62.2 dBm 1x = -84.5dBm, 2x = -82.5 dBm, 4x = -75.5 dBm, 6x = -

69.5 dBm, 8x = -59.5 dBm 1x = -84 dBm, 2x = -84 dBm, 4x = -77 dBm, 6x = -71 dBm, 8x = -63 dBm 1x = -87 dBm, 2x = -80 dBm, 4x = -77 dBm, 6x = -72 dBm, 8x = -65 dBm 1x = -86.9 dBm, 2x = -82.9 dBm, 4x = -75.9 dBm, 6x = -

69.9 dBm, 8x = -63.5 dBm 1x = -87.5 dBm, 2x = -83.5 dBm, 4x = -76.5 dBm, 6x = -

69.5 dBm, 8x = -63.1 dBm 1x = -86 dBm, 2x = -83 dBm, 4x = -76.2 dBm, 6x = -

68.2 dBm, 8x = -61 dBm 1x = -83.4 dBm, 2x = -81.7 dBm, 4x = -74.4 dBm, 6x = -

67.2 dBm, 8x = -57.3 dBm 1x = -84 dBm, 2x = -80.5 dBm, 4x = -74 dBm, 6x = -

66.9 dBm, 8x = -56 dBm 1x = -85.9 dBm, 2x = -80.9 dBm, 4x = -73.9 dBm, 6x = -

67.8 dBm, 8x = -60.9 dBm 1x = -86.5 dBm, 2x = -81.5 dBm, 4x = -74.5 dBm, 6x = -

68.2 dBm, 8x = -61.3 dBm 1x = -84.3 dBm, 2x = -80.3 dBm, 4x = -74.3 dBm, 6x = -

66.2 dBm, 8x = -58 dBm 1x = -82 dBm, 2x = -78.3 dBm, 4x = -72.3 dBm, 6x = -

65.3 dBm, 8x = -55.3 dBm 1x = -81.7 dBm, 2x = -78.6 dBm, 4x = -71.6 dBm, 6x = -

64.4 dBm, 8x = -54 dBm 1x=-83.1 dBm, 2x=-79.3 dBm, 4x=-72.9 dBm, 6x=-66 dBm, 8x=-56.3 dBm 1x=-83.6 dBm, 2x=-79.6 dBm, 4x=-72.3 dBm, 6x=-65.3 dBm, 8x=-54.4 dBm 1x=-82.4 dBm, 2x=-78 dBm, 4x=-71.2 dBm, 6x=-64.3 dBm, 8x=-51 dBm 1x=-82.5 dBm, 2x=-78.8 dBm, 4x=-70.7 dBm, 6x=-64.8 dBm, 8x=-51 dBm Page 4-45 Chapter 4: Reference information Equipment specifications Category Performance Subscribers Per Sector ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Latency Specification Up to 238 Yes 1/16 2.5 ms or 5.0 ms Modulation Levels MCS SNR (in dB) 2x 4x 6x 8x QPSK 16QAM 64QAM 256QAM 10 17 24 32 3 - 5 ms for 2.5 ms Frame Period 6-10 ms for 5.0 ms Frame Period Maximum Deployment Range Up to 40 miles (64 km) GPS Synchronization Quality of Service Link Budget Yes Diffserv QoS Antenna Gain (Does not include cable loss, ~1dB) 900 MHz 12 dBi Yagi antenna 2.4 GHz 3.5 GHz 7 dBi Dual Slant, integrated patch 8 dBi Dual Slant, integrated patch 19 dBi Flat Plate, integrated patch 3.65 GHz 8 dBi Dual Slant, integrated patch 19 dBi Flat Plate, integrated patch 5 GHz 9 dBi H+V, integrate d patch 25 dBi H+V, integrated dish Combined Transmit Power

-30 to +22 dBm (to EIRP limit by region) 2.4, 5 GHz

-30 to +25 dBm (to EIRP limit by region) 3.5, 3.6 GHz 25 dBm - 3 GHz Page 4-46 Chapter 4: Reference information Equipment specifications Category Maximum Transmit Power Reflector antenna gain 2.4 GHz 3.5 GHz 3.65 GHz 5 GHz CLIP Gain Specification 22 dBm combined OFDM (2.4 GHz, 5 GHz)

(dependent upon Region Code setting) 25 dBm combined OFDM (900 MHz, 3.5 GHz, 3.6 GHz), (dependent upon Region Code setting)

+12 dBi

+11 dBi

+11 dBi

+15 dBi

+8 dBi Other antenna (5 GHz only) Physical Wind Survival Antenna Connection Surge Suppression EN61000-4-5 Environmental Temperature / Humidity LENS Gain

+5.5 dBi 200 mph (322 kph) 50 ohm, N-type (Connectorized version only) EN61000-4-5: 10us/700us, Level 4, 4kV voltage waveform Recommended surge suppressor: Cambium Networks Model # 600SSH IP55

-40C to +60C (-40F to +140F) /

0-95% non-condensing Weight 2.4 GHz 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 3.5 GHz 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 2.5 kg (5.5 lbs) for 450 ruggedized 3.6 GHz 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 2.5 kg (5.5 lbs) for 450 ruggedized 5 GHz 5.9 kg (13 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 3.5 kg (7.7 lbs) for 450d Page 4-47 Chapter 4: Reference information Equipment specifications Category Dimensions (H x W x D) Power Consumption Input Voltage Security Encryption Specification 30 x 9 x 9 cm (11.75 x 3.4 x 3.4) 50 x 50 x 38 cm (19.69 x 19.69 x 14.96) for 450d 31.0 x 31.0 x 6.4 cm (12 x 12 x 2.5) for 450 ruggedized 12 W 20 to 32 VDC 128-bit AES and 256-bit AES Note AES-256 requires a license key. Page 4-48 Chapter 4: Reference information Equipment specifications Specifications for PTP 450 Series - BH The PTP 450 BH conforms to the specifications listed in Table 165. Table 165 PTP 450 Series - BH specifications Category Model Number Spectrum Channel Spacing Frequency Range Specification PTP 450 BH 5, 7, 10, 15, 20, 30, and 40 MHz Channel Bandwidth Configurable on 2.5 MHz increments 902 to 928 MHz 3300 3600 MHz 3500 3850 MHz 5470 5875 MHz Channel Bandwidth 900 MHz 5, 7, 10, 15, and 20 MHz 3.5 GHz, 3.6 GHz, and 5 GHz 5, 7, 10, 15, 20, 30 , and 40 MHz 7 MHz Channel bandwidth configurable for 3.5 GHz and 3.65 GHz band only. OFDM Subcarriers Interface MAC (Media Access Control) Layer Physical Layer Ethernet Interface Protocols Used Network Management VLAN Sensitivity 512 FFT Cambium Proprietary 2x2 MIMO OFDM 10/100 BaseT, half/full duplex, rate auto negotiated (802.3 compliant) IPv4, UDP, TCP, IP, ICMP, Telnet, SNMP, HTTP, FTP, TFTP, RADIUS HTTP, HTTPS, Telnet, FTP, SNMP v2c and v3, TFTP, Syslog 802.1ad (DVLAN Q-in-Q), 802.1Q with 802.1p priority, dynamic port VID Page 4-49 Chapter 4: Reference information Equipment specifications Category Specification Nominal Receive Sensitivity (w/ FEC) @ 5 MHz Channel Nominal Receive Sensitivity (w/ FEC) @7 MHz Channel Nominal Receive Sensitivity (w/ FEC)

@10 MHz Channel Nominal Receive Sensitivity (w/ FEC) @15 MHz Channel 900 MHz 1x = -92.2 dBm, 2x = -90.2 dBm, 4x = -83.2 dBm, 6x = -77.2 dBm, 8x = -71.2 dBm 3.5 GHz 3.6 GHz 5.4 GHz 5.8 GHz 900 MHz 3.5 GHz 3.6 GHz 900 MHz 3.5 GHz 3.6 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 5.4 GHz 5.8 GHz OFDM: 1x = -92 dBm, 2x = -90 dBm, 4x = -83 dBm, 6x = -

76 dBm, 8x = -69 dBm OFDM: 1x = -94 dBm, 2x = -89.3 dBm, 4x = -82.3 dBm, 6x

= -75.2 dBm, 8x = -68.4 dBm OFDM: 1x = -90.4 dBm, 2x = -86 dBm, 4x = -79.4 dBm, 6x

= -73.2 dBm, 8x = -65.4 dBm OFDM: 1x = -90 dBm, 2x = -85.4 dBm, 4x = -79.4 dBm, 6x

= -73.4 dBm, 8x = -64.9 dBm 1x = -91 dBm, 2x = -86 dBm, 4x = -80 dBm, 6x = -74 dBm, 8x = -67 dBm OFDM: 1x = -90 dBm, 2x = -88 dBm, 4x = -81 dBm, 6x = -

74 dBm, 8x = -67 dBm OFDM: 1x = -92 dBm, 2x = -87.3 dBm, 4x = -81.3 dBm, 6x =

-74.3 dBm, 8x = -66.4 dBm 1x = -90 dBm, 2x = -84 dBm, 4x = -79 dBm, 6x = -73 dBm, 8x = -66 dBm OFDM: 1x =-91 dBm, 2x = -87.2 dBm, 4x = -80 dBm, 6x = -

73 dBm, 8x = -65.6 dBm OFDM: 1x =-90.4 dBm, 2x = -86.3 dBm, 4x = -80 dBm, 6x =

-73 dBm, 8x = -64.5 dBm OFDM: 1x =-87.6 dBm, 2x = -82.5 dBm, 4x = -76.5 dBm, 6x

= -70.5 dBm, 8x = -61.5 dBm OFDM: 1x =-87.5 dBm, 2x = -82.7 dBm, 4x = -76.8 dBm, 6x

= -70.5 dBm, 8x = -61.4 dBm OFDM: 1x =-89 dBm, 2x = -85 dBm, 4x = -78 dBm, 6x = -

71.1 dBm, 8x = -64.7 dBm OFDM: 1x =-89 dBm, 2x = -84.3 dBm, 4x = -78 dBm, 6x = -

71 dBm, 8x = -63 dBm OFDM: 1x =-85.6 dBm, 2x = -81.6 dBm, 4x = -74.5 dBm, 6x

= -68.5 dBm, 8x = -57.5 dBm OFDM: 1x =-85.6 dBm, 2x = -80.9 dBm, 4x = -75 dBm, 6x =

-68 dBm, 8x = -58 dBm Page 4-50 Chapter 4: Reference information Equipment specifications Category Specification Nominal Receive Sensitivity (w/ FEC)

@20 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

30 MHz Channel Nominal Receive Sensitivity (w/ FEC) @

40 MHz Channel Performance ARQ Cyclic Prefix Frame Period Modulation Levels

(Adaptive) Latency 900 MHz 3.5 GHz 3.6 GHz 5.4 GHz 5.8 GHz 3.5 GHz 3.6 GHz 5.4 GHz 5.8 GHz 5.4 GHz 5.8 GHz 1x = -86 dBm, 2x = -82 dBm, 4x = -75 dBm, 6x = -69 dBm, 8x = -62 dBm OFDM: 1x =-88 dBm, 2x = -84 dBm, 4x = -77 dBm, 6x = -70 dBm, 8x = -62.2 dBm OFDM: 1x =-87.3 dBm, 2x = -83.3 dBm, 4x = -76.3 dBm, 6x

= -69.3 dBm, 8x = -62 dBm OFDM: 1x =-84.5 dBm, 2x = -80.5 dBm, 4x = -73.4 dBm, 6x

= -66.4 dBm, 8x = -56.4 dBm OFDM: 1x =-84.8 dBm, 2x = -80.8 dBm, 4x = -74.7 dBm, 6x

= -66.4 dBm, 8x = -56 dBm OFDM: 1x =-86 dBm, 2x = -82 dBm, 4x = -75 dBm, 6x = -68 dBm, 8x = -60 dBm OFDM: 1x =-86 dBm, 2x = -81.3 dBm, 4x = -74.3 dBm, 6x =

-67.3 dBm, 8x = -59 dBm OFDM: 1x =-82.5 dBm, 2x = -78.5 dBm, 4x = -71.5 dBm, 6x

= -64.4 dBm, 8x = -53.4 dBm OFDM: 1x =-82.5 dBm, 2x = -78.5 dBm, 4x = -71.5 dBm, 6x

= -64.4 dBm, 8x = -54 dBm OFDM: 1x =-81.8 dBm, 2x = -77.5 dBm, 4x = -71.5 dBm, 6x

= -63.5 dBm, 8x = -52.6 dBm OFDM: 1x =-83.0 dBm, 2x = -78.0 dBm, 4x = -71.0 dBm, 6x

= -63.3 dBm, 8x = -50 dBm Yes 1/16 2.5 ms or 5.0 ms Modulation Levels MCS SNR (in dB) 2x 4x 6x 8x QPSK 16QAM 64QAM 256QAM 10 17 24 32 3 - 5 ms for 2.5 ms frame period Page 4-51 Chapter 4: Reference information Equipment specifications Category Packets Per Second Maximum Deployment Range GPS Synchronization Quality of Service Link Budget Combined Transmit Power

-

Specification 6 - 10 ms for 5.0 ms frame period 12,500 Up to 40 miles (64 km) Yes, via Autosync (CMM4) Diffserv QoS 30 to +22 dBm (to EIRP limit by region) in 1 dB-

configurable intervals (5 GHz)

-30 to +25 dBm (to EIRP limit by region) in 1 dB-

configurable intervals (3.5 GHz)

-30 to +25 dBm (to EIRP limit by region and channel bandwidth) in 1 dB-configurable intervals (3.6 GHz) Antenna Gain (Does not include cable loss, ~1dB) 3.5 GHz 8 dBi Dual Slant, integrated patch 19 dBi Flat Plate, integrated patch 3.65 GHz 8 dBi Dual Slant, integrated patch 19 dBi Flat Plate, integrated patch 5 GHz 9 dBi H+V, integrated patch 25 dBi H+V, integrated dish Transmit Power Range Maximum Transmit Power 40 dB dynamic range (to EIRP limit by region) (1 dB step) 22 dBm combined OFDM (5 GHz) (dependent upon Region Code setting) 25 dBm combined OFDM (3.5 GHz, 3.6 GHz), (dependent upon Region Code setting) Reflector antenna gain 3.5 GHz 3.65 GHz 5 GHz

+11 dBi

+11 dBi

+15 dBi Other antenna (5 GHz only) CLIP Gain

+8 dBi LENS Gain

+5.5 dBi Physical Page 4-52 Chapter 4: Reference information Equipment specifications Category Specification Sync/AUX port RJ45 Antenna Connection Surge Suppression EN61000-4-5 Mean Time Between Failure Environmental Temperature / Humidity Weight Wind Survival Dimension (HxWxD) Maximum Power Consumption Input Voltage Security Encryption 10/100/1000BASE-T Ethernet Data PoE output Sync input or output (Connection and powering of UGPS Sync input) 50 ohm, N-type (Connectorized version only) EN61000-4-5: 1.2us/50us, 500 V voltage waveform Recommended external surge suppressor: Cambium Networks Model # C000000L033A

> 40 Years IP66, IP67

-40C to +60C (-40F to +140F), 0-95% non-

condensing 15 kg (33 lbs) with antenna 2.5 kg (5.5 lbs) without antenna 200 mph (322 kph) 30 x 9 x 9 cm (11.75 x 3.4 x 3.4) 14 W 22 to 32 VDC 128-bit AES and 256-bit AES Note AES-256 requires a license key. Page 4-53 Chapter 4: Reference information Equipment specifications PSU specifications The PMP/PTP 450i AC+DC Enhanced Power Injector conforms to the specifications listed in Table 166. Table 166 PMP/PTP 450i AC power Injector specifications Category Dimensions Weight Temperature Humidity Waterproofing Altitude AC Input Specification 137 mm (5.4 in) x 56 mm (2.2 in) x 38 mm (1.5 in) 0.240 Kg (0.5 lbs)

-40C to +60C 90% non-condensing Not waterproof Sea level to 5000 meters (16000 ft) Min 90 V AC, 57 63 Hz, max 264 V AC, 47 53 Hz. DC output voltage to the ODU 58V +2V/- 0V AC connector Efficiency Over Current Protection IEC-320-C8 Better than 85%, efficiency level VI Hiccup current limiting, trip point set between 120% to 150%

of full load current Hold up time At least 10 milliseconds Warning Use the above PSU to only power up 450i and 450m products. Page 4-54 Chapter 4: Reference information Equipment specifications The PMP/PTP 450 power supply conforms to the specifications listed in Table 167. Table 167 PMP/PTP 450 power supply specifications (part number: N000900L001A) Category Dimensions Weight Temperature Humidity AC Input Specification 118 mm (4.66 in) x 45 mm (1.75 in) x 32 mm (1.25 in) 0.240 Kg (0.5 lbs) 0C to +40C 20 to 90%

90-264 VAC, 47 63 Hz, 0.5 A rms at 120 VAC, 0.25 A rms at 240 VAC. DC output voltage to the ODU 30 V 5%

AC connector Efficiency Over Current Protection IEC-320-C8 Better than 85%, efficiency level V Short circuit, with auto recovery; Should restart between every 0.5 to 2 sec. Hold up time 10mS min at max load, 120VAC Note The 30V PSU (part number: #N000900L001A) has to be used for PMP 450 900 MHz SM. Warning The PMP 450 Ruggedized High Gain Integrated Subscriber Module (Cambium part numbers C035045C014A and C036045C014A), while encapsulated in a 450i-type enclosure, contains 450 circuitry which must be powered via 30VDC. Powering these SMs with 56 VDC will damage the device. Page 4-55 Chapter 4: Reference information Data network specifications Data network specifications This section contains specifications of the PMP/PTP 450 platform Ethernet interface. Ethernet interface 450m/450i Series The 450m/450i Series Ethernet port conforms to the specifications listed in Table 168. Table 168 450m/450i Series Main and Aux Ethernet bridging specifications Ethernet Bridging Specification Protocol QoS IEEE 802.3 compatible IEEE 802.1p, IEEE 802.1Q, IEEE 802.1ad, DSCP IPv4 Main Ethernet port 10/100/1000 BaseT, half/full duplex, rate auto negotiated Aux Ethernet port 10/100 BaseT, half/full duplex, rate auto negotiated Maximum Ethernet Frame Size 1700 Bytes 450/450b Series Table 169 450 Series Ethernet bridging specifications Ethernet Bridging Specification Protocol QoS Interface IEEE 802.3 compatible IEEE 802.1p, IEEE 802.1Q, IEEE 802.1ad, DSCP IPv4 10/100/1000* BaseT, half/full duplex, rate auto negotiated Maximum Ethernet Frame Size 1700 Bytes

* 450 SM does not support 1000 BaseT.

* 450 AP supports 1000 BaseT, but with known CRC errors and it is not recommended to use. Note Practical Ethernet rates depend on network configuration, higher layer protocols and platforms used. Over the air throughput is restricted to the rate of the Ethernet interface at the receiving end of the link. Page 4-56 Chapter 4: Reference information Wireless specifications Wireless specifications This section contains specifications of the 450 Platform Family wireless interface. These specifications include RF bands, channel bandwidth, spectrum settings, maximum power and link loss. General wireless specifications The wireless specifications that apply to all 450 Platform variants are listed under Table 170. Table 170 450 Platform Family - wireless specifications Item Specification Channel selection Manual power control Manual selection (fixed frequency). To avoid interference to other users of the band, maximum power can be set lower than the default power limit. Duplex scheme Adaptive TDD Range Band Platform Range 900 MHz PMP 450i Series - AP and 120 mi / 193 km PMP 450 Series - SM 2.4 GHz PMP 450 Series 40 mi / 64 km 3.5 GHz PMP/PTP 450 Series 40 mi / 64 km (PMP) 186 mi/ 299 km (PTP) 3.65 GHz PMP/PTP 450 Series 40 mi / 64 km (PMP) 5 GHz PMP/PTP 450/450i/450b Series and PMP 450m Series AP 186 mi/ 299 km (PTP) 40 mi / 64 km (PMP) 186 mi/ 299 km (PTP) Over-the-air encryption 128-bit AES and 256-bit AES Error Correction Rate 3/4 RS coder Page 4-57 Chapter 4: Reference information Wireless specifications Link Range and Throughput Link range and throughput estimates are based on site-specific attributes and configuration parameters. For the most up-to-date information on link range and throughput for your equipment see the Capacity Planner and LINKPlanner software tools:

For average-deployment link range and throughput planning information, see:

https://support.cambiumnetworks.com/files/capacityplanner/

For site-specific link range and throughput planning information, see:

https://support.cambiumnetworks.com/files/linkplanner Page 4-58 Chapter 4: Reference information Country specific radio regulations Country specific radio regulations This section describes how the 450 Platform Family complies with the radio regulations that are enforced in various countries. Caution Changes or modifications not expressly approved by Cambium could void the users authority to operate the system. Type approvals This system has achieved Type Approval in various countries around the world. This means that the system has been tested against various local technical regulations and found to comply. The frequency bands in which the system operates may be unlicensed and, in these bands, the system can be used provided it does not cause interference. The system is not guaranteed protection against interference from other ODUs and installations. The radio specification type approvals that have been granted for 450 Platform frequency variants are listed in Table 171. Table 171 Radio certifications Variant Region Specification (Type Approvals) 900 MHz PMP 450i Canada RSS Gen and RSS 210 2.4 GHz PMP 450 3.5 GHz PMP/PTP 450 USA Mexico Canada USA Canada Europe FCC Part 15.247 NOM-121-SCT1-2009 RSS Gen and RSS 210 FCC Part 15 Class B RSS Gen and RSS 192 ETSI EN 302 326-2 V1.2.2 3.6 GHz PMP/PTP 450 Canada RSS Gen and RSS 197 3.5 GHz PMP 450m 3.6 GHz PMP 450m 4.9 GHz PMP/PTP 450i/450b/450m USA Canada Europe Canada USA Europe USA FCC Part 15 Class B RSS Gen and RSS 192 ETSI EN 302 326-2 V1.2.2 RSS Gen and RSS 197 FCC Part 90Z and Part 15 Class B ETSI EN 302 326-2 V1.2.2 FCC Part 90 Subpart Y Canada RSS Gen and RSS 111 Page 4-59 Chapter 4: Reference information Country specific radio regulations Variant Region Specification (Type Approvals) 5.1 GHz PMP/PTP 450i/450b USA FCC Part 15 Class B 5.1 GHz PMP/PTP 450m USA FCC Part 15E and Part 15B Europe ETSI EN 302 625 V1.1.1 5.2 GHz PMP/PTP 450m USA FCC Part 15E and Part 15B 5.2 GHz PMP/PTP 450i/450b 5.4 GHz PMP/PTP 450 and 450i USA Canada Europe USA FCC Part 15 Class B RSS Gen and RSS 247 ETSI EN 301 893 v1.6.1 FCC Part 15 Class B 5.4 GHz PMP/PTP 450m USA FCC Part 15E and Part 15B 5.8 GHz PMP/PTP 450 and 450i Canada Europe Canada USA Europe RSS Gen and RSS 247 ETSI EN 301 893 v1.8.1 ETSI EN 301 893 v2.1.1 Clause 4.8 RSS Gen and RSS 210 FCC Part 15 Class B ETSI EN 302 502 v1.2.1 5.8 GHz PMP/PTP 450m USA FCC Part 15E and Part 15B RSS Gen and RSS 247 ETSI EN 302 502 v2.1.1 Canada Europe Page 4-60 Chapter 4: Reference information Country specific radio regulations DFS for 2.4 and 5 GHz Radios Dynamic Frequency Selection (DFS) is a requirement in several countries and regions for 2.4 and 5 GHz unlicensed systems to detect radar systems and avoid co-channel operation. The details of DFS operation and channels available for each Country Code, including whether DFS is active on the AP, SM, which DFS regulation apply, and any channel restrictions are shown in Table 172 on page 4-61. Table 172 Country & Bands DFS setting Region Code North America Country Code Band AP SM USA 2.4 GHz No effect 5.2 GHz FCC DFS 5.4 GHz FCC DFS 5.8 GHz No effect Canada 2.4 GHz No effect 5.2 GHz FCC DFS 5.4 GHz FCC DFS No effect No effect No effect No effect No effect No effect No effect Weather Radar Notch-Out No No No No No No No*

* Weather radar notch-out is required in Canada when the band range is between 5600 - 5650 5.8 GHz No effect Mexico 2.4 GHz No effect 5.2 GHz 5.4 GHz ANATEL Res506-

2008 ANATEL Res506-

2008 No effect No effect No effect No effect 5.8 GHz No effect No effect South America Brazil 5.4 GHz ETSI EN 301 893 v2.1.1DFS No effect 5.8 GHz No effect No effect Europe ETSI 5.4 GHz ETSI EN 301 893 v2.1.1 DFS ETSI EN 301 893 v1.7.1 DFS 5.8 GHz ETSI EN 302 502 v2.1.1 DFS ETSI EN 302 502 v1.2.1 DFS Other-FCC 2.4 GHz No effect No effect No No No No No No No Yes Yes No Page 4-61 Chapter 4: Reference information Country specific radio regulations Region Code Other-

Regulatory Country Code Band AP SM 5.2 GHz FCC DFS 5.4 GHz FCC DFS 5.8-GHz No effect No effect No effect No effect Other-ETSI 5.4 GHz 5.8 GHz ETSI EN 301 893 v2.1.1 DFS ETSI EN 301 893 v1.7.1 DFS ETSI EN 302 502 v2.1.1 DFS ETSI EN 302 502 v1.2.1 DFS Weather Radar Notch-Out No No No No No Page 4-62 Chapter 4: Reference information Equipment Disposal Equipment Disposal Waste (Disposal) of Electronic and Electric Equipment Waste

(Disposal) of Electronic and Electric Equipment Please do not dispose of Electronic and Electric Equipment or Electronic and Electric Accessories with your household waste. In some countries or regions, collection systems have been set up to handle waste of electrical and electronic equipment. In European Union countries, please contact your local equipment supplier representative or service center for information about the waste collection system in your country. Page 4-63 Chapter 4: Reference information Country specific band range maximum transmit power Country specific band range maximum transmit power Maximum transmit power 900 MHz band Table 173 Frequency range and Maximum transmit power 900 MHz band PMP 450i Series Region Country Bang range Lower Upper Device Type Antenna Type EIRP Limit /Conducted Power Limit (dBm) 5 MHz 7 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 902 928 Any Any EIRP 36 36 36 36 36 CPL North America Other FCC, USA, Canada, Mexico, Puerto, Rico Oceania Australia 915 928 Any Any New Zealand 915 928 Any Any Any Any Any Any 920.5

(7 MHz) 919.5

(5 MHz) 924.5

(7 MHz) 925.5

(5 MHz) EIRP CPL EIRP CPL EIRP CPL EIRP CPL 30 19 30 19 30 19 30 19 30 19 30 19 30 19 30 19 30 19 30 19 30 19 30 19 30 19 36 19 36 19 36 19 South America Brazil 902 907.5 Any Any EIRP 36 36 36 36 915 928 Any Any EIRP 36 36 36 36 CPL CPL EIRP CPL EIRP CPL EIRP CPL 27 36 27 36 27 36 27 36 Ecuador 902 928 Any Any 902 928 Any Any Colombia, Panama, Venezuela Others Others 902 928 Any Any CPL= Conducted Power Limit

-

-

-

-

-

-

-

-

-

-

-

27 36

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

Page 4-64 Chapter 4: Reference information Country specific band range maximum transmit power Maximum transmit power 2.4 GHz band Table 174 Frequency range and Maximum transmit power 2.4GHz band PMP/PTP 450 Series Bang range Device Type Upper Lowe r Antenna Type EIRP Limit /Conducted Power Limit (dBm) 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 36 18 36 36 24 36 11 30 36 18 36 36 24 36 11 30

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

30 30 Countr y Other FCC, USA, Canada 2400 2483. 5 AP Sector SM, BH Integrate d EIRP CPL EIRP 36 18 36 CPL Reflector EIRP CPL EIRP CPL Integrate d Dish

(450d) 36 24 36 11 36 18 36 36 24 36 11 Others 2400 2483. 5 Any Any EIRP CPL 30 30 CPL= Conducted Power Limit Page 4-65 Chapter 4: Reference information Country specific band range maximum transmit power Maximum transmit power 3 GHz band Table 175 Frequency range and Maximum transmit power 3 GHz band PMP/PTP 450 Series Country Bang range Lower Upper Device Type Antenna Type Other 3300

(1) 3850

(1) Any Any FCC 3650 3700 Any Any ETSI India 3410

(2) 3800

(2) 3300

(3) 3800

(3) Any Any Any Any Indonesia 3600 3800 Any Any China 3300 3400 Any Any Malaysia Pakistan EIRP CPL EIRP CPL EIRP CPL EIRP CPL EIRP CPL EIRP CPL EIRP CPL EIRP CPL EIRP Limit /Conducted Power Limit (dBm) 5 MHz 7 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 37 19 38.5 40 41.7 43 44.7 46 20.5 22 23.7 25 26.7 28 Canada 3450 3650 Any Any EIRP 62 62 62 62 62 62 62 CPL 3650 3700 Any Any USA 3550

(4) 3700

(4) Any Any 3650 3700 Any Any Mexico 3300 3750 Any Australia 3300 3800 Any Any Any Brazil 3400 3600 Any Any EIRP CPL EIRP CPL EIRP CPL EIRP CPL 37 19 44 24 37 19 38.5 40 41.7 43 44.7 46 20.5 22 23.7 25 26.7 28 45.5 47 48.7 50 25.5 27 38.5 40 28.1 41.7 30 43 51.7 30 53 30 44.7 46 20.5 22 23.7 25 26.7 28 EIRP 57 58.9 60 61.7 63 63 CPL EIRP CPL

-

-

-

-

-

-

-

CPL= Conducted Power Limit

(1) = Frequencies between 3850 and 3900 can also be selected, but performance is not guaranteed in this portion of the band. For example, sensitivity is degraded

(2) = No PTP support in ETSi region Page 4-66 Chapter 4: Reference information Country specific band range maximum transmit power

(3) = Either ETSI or FCCC

(4) = This band follows the CBRS rules (devices need to connect to a SAS to be granted a channel) Maximum transmit power 4.9 GHz band Table 176 Default combined transmit power per country 4.9 GHz band PMP/PTP 450i Series Countries Device Type Antenna Type Channel BW Antenna Gain (dBi) Conducted Power Limit

(dBm) EIRP Limit

(dBm) AP Sector Omni USA, Canada, Other FCC Flate plate SM, BH 4ft parabolic 6ft parabolic Brazil AP Sector 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 16 16 16 16 12 12 12 12 27 27 27 27 32 32 32 32 36 36 36 36 16 16 16 16 Page 4-67 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 23 24 24 24 24 27 27 27 27 40 40 40 40 36 36 36 36 51 51 51 51 56 56 56 52 60 60 60 60 43 43 43 43 Chapter 4: Reference information Country specific band range maximum transmit power Countries Device Type Antenna Type Channel BW Antenna Gain (dBi) Conducted Power Limit

(dBm) EIRP Limit

(dBm) 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Any 16 16 16 16 16 16

-

22 22 22 22 22 22 27 38 38 38 38 38 38

-

Mexico AP Sector Other Any Any Page 4-68 Chapter 4: Reference information Country specific band range maximum transmit power Table 177 Default combined transmit power per country 4.9 GHz band PMP 450b Series Countries Device Type Antenna Type Channel BW Antenna Gain (dBi) Conducted Power Limit

(dBm) EIRP Limit

(dBm) FCC SM 16 dBi Mid-

Gain 23 dBi High Gain 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 16 16 16 16 23 23 23 23 26 26 26 26 26 26 26 26 42 42 42 42 49 49 49 49 Table 178 Default combined transmit power per country 4.9 GHz band PMP 450m Series Countries Device Type Antenna Type Channel BW EIRP Limit (dBm) USA, Canada, Other FCC AP Sector Brazil AP Sector Mexico AP Sector 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Other AP Sector Any Page 4-69 42 dBm (in sector mode)/ 48 dBm (in beamforming mode) Chapter 4: Reference information Country specific band range maximum transmit power Maximum transmit power 5.1 GHz band Table 179 Default combined transmit power per Country 5.1 GHz band PMP/PTP 450i Series Countries Device Antenna Type Channel BW Type Antenna Gain

(dBi) Conducted Power Limit

(dBm) EIRP Limit

(dBm) 16 16 16 16 16 16 12 12 12 12 12 12 23 23 23 23 23 23 33 33 33 33 33 33 14 17 18 20 20 20 16 19 22 24 24 24 24 27 27 27 27 27 14 17 18 20 20 20 30 33 34 36 36 36 28 31 34 36 36 36 47 50 50 50 50 50 47 50 51 53 53 53 AP Sector USA, Other FCC and Canada Omni SM, BH Flat plate 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 4ft parabolic 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Page 4-70 Chapter 4: Reference information Country specific band range maximum transmit power Countries Device Antenna Type Channel BW Type 6ft parabolic 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Antenna Gain

(dBi) Conducted Power Limit

(dBm) EIRP Limit

(dBm) 36 36 36 36 36 36 11 14 15 17 17 17 47 50 51 53 53 53 Table 180 Default combined transmit power per country 5.1 GHz band PMP 450b Mid Gain and High Gain Countries Device Type Antenna Type Channel BW Antenna Gain

(dBi) Conducted Power Limit

(dBm) EIRP Limit

(dBm) 31 34 35 37 37 37 24 27 28 30 30 30 47 50 51 53 53 53 47 50 51 53 53 53 FCC SM 16 dBi Mid-

Gain 23 dBi High Gain 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 16 16 16 16 16 16 23 23 23 23 23 23 Page 4-71 Chapter 4: Reference information Country specific band range maximum transmit power Table 181 Default combined transmit power per Country 5.1 GHz band PMP 450m Series Countries Device Type Antenna Type Channel BW EIRP Limit (dBm) USA AP Sector ETSI AP Sector Mexico AP Sector Other Any Any 30 33 34 36 36 36 33 36 37 39 23 23 23 42 42 42 42 42 42 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Page 4-72 Chapter 4: Reference information Country specific band range maximum transmit power Note For releases 16.0 and later, although sector transmission mode EIRP is limited to 42 dBm, ROW GUI configuration limit allows a setting of up to 48 dBm. This allows the software to transmit as high as 48 dBm for ROW regions, depending on the modulation mode and transmission mode in use. For a detailed explanation, see the Release 16.0 training slides available at:

https://learning.cambiumnetworks.com/learn/course/121/PMP450SoftwareRelease16 Maximum transmit power 5.2 GHz band Note The selection of 5 MHz channel is not available for the PMP 450 AP and the PTP 450 BHM. It is available for the PMP/PTP 450i AP/SM and the PMP 450m AP. Page 4-73 Chapter 4: Reference information Country specific band range maximum transmit power Table 182 Default combined transmit power per country 5.2 GHz band PMP/PTP 450i Series Countries Device Type Antenna Type Channel BW Antenna Gain

(dBi) Conducted Power Limit

(dBm) EIRP Limit

(dBm) USA, Other FCC AP Sector 5 MHz Omni 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz SM, BH Flat plate 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 4ft parabolic 6ft parabolic Page 4-74 16 16 16 16 16 16 12 12 12 12 12 12 23 23 23 23 23 23 32 32 32 32 32 32 36 36 36 8 11 12 14 14 14 12 15 16 18 18 18 27 27 27 27 27 27 27 27 27 27 27 27 27 27 27 24 27 28 30 30 30 24 27 28 30 30 30 50 50 50 50 50 50 59 59 59 59 59 59 63 63 63 Chapter 4: Reference information Country specific band range maximum transmit power Countries Device Type Antenna Type Mexico Any Any Channel BW Antenna 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Gain

(dBi) 36 36 36

-

-

-

-

-

-

-

Conducted Power Limit

(dBm) EIRP Limit

(dBm) 27 27 27

-

-

-

-

-

-

27 63 63 63 24 27 28 30 30 30

-

Other Any Any Any Table 183 Default combined transmit power per country 5.2 GHz band PMP 450b Mid-Gain and High Gain Countries Device Type Antenna Type Channel BW Antenna Gain

(dBi) Conducted Power Limit

(dBm) EIRP Limit

(dBm) FCC SM 16 dBi Mid-

Gain 23 dBi High Gain 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 16 16 16 16 16 16 23 23 23 23 23 Page 4-75 8 11 12 14 14 14 1 4 5 7 7 24 27 28 30 30 30 24 27 28 30 30 Chapter 4: Reference information Country specific band range maximum transmit power 16 dBi Mid-

Gain Other SM 23 dBi High Gain 40 MHz 23 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 16 16 16 16 16 16 16 16 16 16 16 16 7 27 27 27 27 27 27 27 27 27 27 27 27 30 43 43 43 43 43 43 43 43 43 43 43 43 Page 4-76 Chapter 4: Reference information Country specific band range maximum transmit power Table 184 Default combined transmit power per Country 5.2 GHz band PMP 450m Series Countries Device Type Antenna Type Channel BW EIRP Limit (dBm) USA, Other FCC AP Sector Mexico AP Sector Other Any Any 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 24 27 28 30 30 30 24 27 28 30 30 30 42 42 42 42 42 42 Note For releases 16.0 and later, although sector transmission mode EIRP is limited to 42 dBm, ROW GUI configuration limit allows a setting of up to 48 dBm. This allows the software to transmit as high as 48 dBm for ROW regions, depending on the modulation mode and transmission mode in use. For a detailed explanation, see the Release 16.0 training slides available at:

https://learning.cambiumnetworks.com/learn/course/121/PMP450SoftwareRelease16 Page 4-77 Chapter 4: Reference information Country specific band range maximum transmit power Maximum transmit power 5.4 GHz band Table 185 Default combined transmit power per country 5.4 GHz band PMP 450m Series Countries Device Type Antenna Type Channel BW EIRP Limit (dBm) FCC AP Sector ETSI AP Sector RoW AP Sector 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz RoW Other AP Sector

-

24 27 28 29 30 30 24 27 28 30 30 30 42 42 42 42 42 42 42 Note The selection of 5 MHz channel is not available for the PMP 450 AP and the PTP 450 BHM. It is available for PMP/PTP 450i AP/SM, PMP 40b SM, and PMP 450m AP. Power reduction at the band edges is required in some cases. Page 4-78 Chapter 4: Reference information Country specific band range maximum transmit power Table 186 Default combined transmit power per country 5.4 GHz band PMP/PTP 450i Series Countries Device Type Antenna Type Channel BW Antenna Gain

(dBi) Conducted Power Limit

(dBm) EIRP Limit

(dBm) AP Sector USA, Other FCC Omni 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz SM, BH Flat plate 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 4ft parabolic 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 16 16 16 16 16 16 12 12 12 12 12 12 27 27 27 27 27 27 32 32 32 32 32 32 8 11 12 14 14 14 12 15 16 18 18 18 27 27 27 27 27 27 27 27 27 27 27 27 24 27 28 30 30 30 24 27 28 30 30 30 54 54 54 54 54 54 59 59 59 59 59 59 Page 4-79 Chapter 4: Reference information Country specific band range maximum transmit power Countries Device Type Antenna Type Channel BW Antenna Gain

(dBi) Conducted Power Limit

(dBm) EIRP Limit

(dBm) Any Any Brazil, Mexico, Australia, ETSI Other Any Any 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Any 36 36 36 36 36 36

-

27 27 27 27 27 27 27 63 63 63 63 63 63

-

Table 187 Default combined transmit power per country 5.4 GHz band PMP 450b Mid-Gain and High Gain Countries Device Type Antenna Type Antenna Gain Channel BW

(dBi) Conducted Power Limit

(dBm) EIRP Limit

(dBm) 8 11 12 14 14 14 1 4 5 9 9 9 24 27 28 30 30 30 24 27 28 30 30 30 FCC, ETSI SM 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 16 dBi Mid-Gain 23 dBi High Gain 16 16 16 16 16 16 23 23 23 23 23 23 Page 4-80 Chapter 4: Reference information Country specific band range maximum transmit power Table 188 Default combined transmit power per country 5.4 GHz band PMP 450 Series Countries Device Type Antenna Type Channel BW Antenna Gain

(dBi) Conducted Power Limit

(dBm) EIRP Limit

(dBm) AP Sector 5 MHz United States, Canada, Brazil, Australia, Denmark, Finland, Germany, Greece, Liechtenstein, Norway, Portugal, Spain, UK, Vietnam SM, BH 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Flat plate

(Gain: 27), 4ft parabolic

(Gain: 32), 6ft parabolic

(Gain: 36) Austria, Belgium, Bosnia &

Herzegovina, Bulgaria, Croatia, Cyprus, Czech Republic, France, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Macedonia, Malta, Netherlands, Poland, Romania, Slovakia, Slovenia, Sweden AP Sector 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 16 16 16 16 16 16

-

-

-

-

-

-

16 16 16 16 16 16 8 11 12 14 14 14 27 27 27 27 27 27 8 11 12 14 14 14 24 27 28 30 30 30

-

-

-

-

-

-

24 27*

28 30 30 30 Page 4-81 Chapter 4: Reference information Country specific band range maximum transmit power Countries Device Type Antenna Type Channel BW Antenna Gain

(dBi) Conducted Power Limit

(dBm) EIRP Limit

(dBm) Algeria AP Sector 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MH Other AP Sector 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 30 30 30 30 30 30 No EIRP limit 16 16 16 16 16 16 16 16 16 16 16 16 14 14 14 14 14 14

-

19

-

19

-

-

(*) At 5.4 GHz, EU regulations are harmonized. 5600 5650 MHz excluded, as ten-minute Channel Availability Check (CAC) is required. Note For releases 16.0 and later, although sector transmission mode EIRP is limited to 42 dBm, ROW GUI configuration limit allows a setting of up to 48 dBm. This allows the software to transmit as high as 48 dBm for ROW regions, depending on the modulation mode and transmission mode in use. For a detailed explanation, see the Release 16.0 training slides available at:

https://learning.cambiumnetworks.com/learn/course/121/PMP450SoftwareRelease16 Page 4-82 Chapter 4: Reference information Country specific band range maximum transmit power Maximum transmit power 5.8 GHz band Table 189 Default combined transmit power per Country 5.8 GHz band PMP 450m Series Countries USA, Other FCC Device Type AP Sector Antenna Type Channel BW EIRP Limit

(dBm) Mexico AP Sector ETSI AP Sector Other AP Sector 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 36 36 36 36 36 36 30 33 34 36 36 36 30 33 34 36 36 36 42 42 42 42 42 42 Page 4-83 Chapter 4: Reference information Country specific band range maximum transmit power Table 190 Default combined transmit power per country 5.8 GHz band PMP/PTP 450i Series Countries Device Type Antenna Type Channel BW Antenna Gain

(dBi) Conducted Power Limit

(dBm) EIRP Limit

(dBm) 20 20 20 20 20 20 27 27

(26 for 5733 MHz and below) 27 27 27 27

-

-

-

-

-

-

27 36 36 36 36 36 36

-

-

-

-

-

-

30 33 34 36 36 36

-

AP Sector, Omni USA, Canada, Brazil, Other FCC SM, BH Flat plate, 4ft parabolic, 6ft parabolic Note Canada is limited to 4ft parabolic Antenna type. Mexico Any Any Other Any Any 16 16 16 16 16 16

-

-

-

-

-

-

-

-

-

-

-

-

-

5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz Page 4-84 Chapter 4: Reference information Country specific band range maximum transmit power Table 191 Default combined transmit power per country 5.8 GHz band PMP 450b Mid-Gain and High Gain Countries Device Type Antenna Type Channel BW Antenna Gain

(dBi) Conducted Power Limit

(dBm) EIRP Limit

(dBm) 20 20 20 20 20 20 13 13 13 13 13 13 14 17 18 20 20 20 7 10 11 13 13 13 36 36 36 36 36 36 36 36 36 36 36 36 30 33 34 36 36 36 30 33 34 36 36 36 16 dBi Mid-

Gain 23 dBi High Gain 16 dBi Mid-

Gain 23 dBi High Gain FCC SM ETSI/Other ETSI SM 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 16 16 16 16 16 16 23 23 23 23 23 23 16 16 16 16 16 16 23 23 23 23 23 23 Page 4-85 Chapter 4: Reference information Country specific band range maximum transmit power Table 192 Default combined transmit power per country 5.8 GHz band PMP 450 Series Countries Device Type Antenna Type Channel BW Antenna Gain

(dBi) Conducted Power Limit

(dBm) EIRP Limit

(dBm) 20 20 20 20 20 20 8 11 12 14 14 14 20 20 20 20 20 20 10 20 20 20 20 20 36 36 36 36 36 36 24 27 28 30 30 30 36 36 36 36 36 36 26 36 36 36 36 36 AP Sector Australia, India, United States Vietnam AP Sector Brazil AP Sector Canada AP Sector 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 16 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Page 4-86 Chapter 4: Reference information Country specific band range maximum transmit power Countries Device Type Antenna Type Channel BW Antenna AP Sector Denmark, Finland, Germany, Greece, Iceland, Ireland, Liechtenstein, Norway, Portugal, Serbia, Spain, Switzerland, United Kingdom, Indonesia AP Sector Gain

(dBi) 16 16 16 16 16 16 16 16 16 16 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz Conducted Power Limit

(dBm) EIRP Limit

(dBm) 14 17 18 20 20 20 14 17 18 20 30 33 34 36 36 36 30 33 34 36 Note For releases 16.0 and later, although sector transmission mode EIRP is limited to 42 dBm, ROW GUI configuration limit allows a setting of up to 48 dBm. This allows the software to transmit as high as 48 dBm for ROW regions, depending on the modulation mode and transmission mode in use. For a detailed explanation, see the Release 16.0 training slides available at:

https://learning.cambiumnetworks.com/learn/course/121/PMP450SoftwareRelease16 Page 4-87 Chapter 4: Reference information Country specific frequency range Country specific frequency range Frequency range 900 MHz band Table 193 Frequency range per country 900 MHz band Region Country Other Other Other-FCC North America Canada United States Mexico Puerto Rico Oceania Australia Channel center Frequency limits (MHz) Lower Upper 902 902 902 902 902 902 915 915 928 928 928 928 928 928 928 928 New Zealand 920.5 (7 MHz) 919.5 (5 MHz) 924.5 (7 MHz) 925.5 (5 MHz) South America Brazil Ecuador Colombia Panama Venezuela 902 915 902 902 902 902 907.5 928 928 928 928 928 Page 4-88 Chapter 4: Reference information Country specific frequency range Frequency range 2.4 GHz band Table 194 Frequency range per country 2.4 GHz band PMP/PTP 450 Series Countries Antenna Type Channel BW Any Canada, United States, Other, Other-

FCC 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz Channel center Frequency limits (MHz) Lower 2402.5 2405 2407.5 2410 2415 Upper 2481 2478.5 2476 2473.5 2468.5 Frequency range 3.5 GHz band Table 195 Frequency range per country 3.5 GHz band PMP/PTP 450/450i Series Countries Antenna Type Channel BW Brazil, Other-

ETSI Any Any China, Indonesia 5 MHz 7 MHz 10 MHz 20 MHz 5 MHz 7 MHz 10 MHz 20 MHz Channel center Frequency limits (MHz) Lower 3402.5 3403.5 3405 3410 3302.5 3303.5 3305 3310 Upper 3597.5 3596.5 3595 3590 3397.5 3396.5 3395 3390 Page 4-89 Chapter 4: Reference information Country specific frequency range Frequency range 3.65 GHz band Table 196 Frequency range per country 3.65 GHz band PMP/PTP 450/450i Series Countries Antenna Type Channel BW Australia, India, Other Any Other ETSI Any Indonesia Any Mexico Any Channel center Frequency limits (MHz) Lower 3302.5 3303.5 3305 3307.5 3310 3315 3320 Upper 3797.5 3796.5 3795 3792.5 3790 3785 3780 5 MHz 7 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz*

Note Australia does not support 40 MHz channel bandwidth. 3847.5 3845 3842.5 3840 3835 3830 3797.5 3796.5 3795 3790 3780 3747.5 3745 3740 3730 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 7 MHz 10 MHz 20 MHz 40 MHz 5 MHz 10 MHz 20 MHz 40 MHz 3402.5 3405 3407.5 3410 3415 3420 3602.5 3603.5 3605 3610 3620 3302.5 3305 3310 3320 Page 4-90 Chapter 4: Reference information Country specific frequency range Frequency range 4.9 GHz band Table 197 Frequency range per country 4.9 GHz band PMP/PTP 450i Series Countries Antenna Type Channel BW Any USA, Mexico, Canada, Other FCC Brazil Any Other Any 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower 4942.5 4945 4947.5 4950 4912.5 4915 4917.5 4920 4942.5 4945 4947.5 4950 4955 4960 Upper 4987.5 4985 4982.5 4980 4987.5 4985 4982.5 4980 4987.5 4985 4982.5 4980 4975 4970 Table 198 Frequency range per country 4.9 GHz band PMP 450b Series Countries Antenna Type Channel BW FCC 16 dBi Mid-Gain 5 MHz 23 dBi High Gain 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower 4942.5 4945 4947.5 4950 4955 4960 Upper 4987.5 4985 4982.5 4980 4975 4970 Page 4-91 Chapter 4: Reference information Country specific frequency range Table 199 Frequency range per country 4.9 GHz band PMP 450m Series Countries Antenna Type Channel BW Any USA, Mexico, Canada, Other FCC Brazil Any Other Any 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower 4942.5 4945 4947.5 4950 4912.5 4915 4917.5 4920 4942.5 4945 4947.5 4950 4955 4960 Upper 4987.5 4985 4982.5 4980 4987.5 4985 4982.5 4980 4987.5 4985 4982.5 4980 4975 4970 Page 4-92 Chapter 4: Reference information Country specific frequency range Frequency range 5.1 GHz band Table 200 Frequency range per country 5.1 GHz band PMP/PTP 450i Series Countries Antenna Type Channel BW Channel center Frequency limits (MHz) United States, FCC Any ETSI Any Other Any 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Lower 5157.51 51602 51653 51704 51805 51806 5155 5155 5157.5 5160 5152.5 5155 5157.5 5160 5165 5170 Upper 5247.5 5245 5242.5 5240 5235 5230 5245 5245 5242.5 5240 5247.5 5245 5242.5 5240 5235 5230 1 Center frequency 5160 is the lowest allowed at full power. Max power for edge frequency is 20 dBm. 2 Center frequency 5165 is the lowest allowed at full power. Max power for edge frequencies is 22 dBm. 3 Center frequency 5170 is the lowest allowed at full power. Max power for edge frequencies is 23 dBm. 4 Center frequency 5177.5 is the lowest allowed at full power. Max power for edge frequency is 23 dBm. 5 Center frequency 5190 is the lowest allowed at full power. Max power for edge frequency is 22 dBm. 6 Center frequency 5205 is the lowest allowed at full power. Max power for edge frequency is 22 dBm. Page 4-93 Chapter 4: Reference information Country specific frequency range Table 201 Frequency range per country 5.1 GHz band PMP 450b Mid-Gain Series Countries Antenna Type Channel BW FCC 16 dBi 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower 5155 5155 5157.5 5160 5165 5170 Upper 5247.5 5245 5242.5 5240 5235 5230 Table 202 Frequency range per country 5.1 GHz band PMP 450b High Gain Series Countries Antenna Type Channel BW FCC 23 dBi 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower 5155 5155 5157.5 5160 5165 5170 Upper 5245 5245 5242.5 5235 5235 5230 Page 4-94 Chapter 4: Reference information Country specific frequency range Table 203 Frequency range per country 5.1 GHz band PMP 450m Series Countries Antenna Type Channel BW United States, FCC Any 5 MHz 10 MHz 15 MHz 20 MHz Channel center Frequency limits (MHz) Lower 5162.5 Upper 5247.5 5160 (26 dBm) 5197.5 (26 dBm) 5200 (33 dBm) 5245 (33 dBm) 5165 (26 dBm) 5197.5 (26 dBm) 5200 (34 dBm) 5242.5 (34 dBm) 5170 (26 dBm) 5197.5 (26 dBm) 5200 (36 dBm) 5240 (36 dBm) 5165 (30 dBm) 5180 (30 dBm) 30 MHz 5182.5 (33 dBm) 5192.5 (33 dBm) 5195 (36 dBm) 5235 (36 dBm) 5170 (30 dBm) 5185 (30 dBm) 40 MHz 5187.5 (33 dBm) 5197.5 (33 dBm) 5200 (36 dBm) 5230 (36 dBm) 5 MHz 10 MHz 15 MHz 20 MHz 5 MHz 10 MHz 15 MHz 20 MHz 5152.5 5155 5157.5 5160 5152.5 5155 5157.5 5160 5247.5 5245 5242.5 5240 5247.5 5245 5242.5 5240 ETSI Any Other Any Page 4-95 Chapter 4: Reference information Country specific frequency range Frequency range 5.2 GHz band Table 204 Frequency range per country 5.2 GHz band PMP/PTP 450i Series Countries Antenna Type Channel BW Channel center Frequency limits (MHz) United States, FCC Any Other Any 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Lower 5252.5 5255 5257.5 5260 5265 5270 5252.5 5255 5257.5 5260 5265 5270 Upper 5342.5 5340 5337.5 5332.57 5332.58 53259 5347.5 5345 5342.5 5340 5335 5330 7 Center frequency 5330 is the highest allowed at full power. Max power for edge frequency is 20 dBm. 8 Center frequency 5317.5 is the lowest allowed at full power. Max power for edge frequency is 20 dBm. 9 Center frequency 5310 is the lowest allowed at full power. Max power for edge frequencies is 20 dBm. Page 4-96 Chapter 4: Reference information Country specific frequency range Table 205 Frequency range per country 5.2 GHz band PMP 450b Mid-Gain Series Countries Antenna Type Channel BW FCC 16 dBi 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower

-

5255 5257.5 5260 5265 5270 Upper

-

5340 5337.5 5337.5 5330 5330 (*)

(*) Last channel at full power is 5325. Channel centers 5327.5 and 5330 need a power back off of 5 dB. Table 206 Frequency range per country 5.2 GHz band PMP 450b High Gain Series Countries Antenna Type Channel BW FCC 23 dBi 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower

-

5255 5257.5 5260 5265 5270 Upper

-

5340 5337.5 5335 5332.5 5330 Page 4-97 Chapter 4: Reference information Country specific frequency range Table 207 Frequency range per country 5.2 GHz band PMP 450m Series Countries Antenna Type Channel BW Channel center Frequency limits (MHz) United States, FCC Any Other Any 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Lower 5252.5 5255 5302.5 5257.5 5302.5 5260 5302.5 5265 5270 5252.5 5255 5257.5 5260 5265 5270 Upper 5347.5 5300 5340 5300 5335 5300 5340 5335 5330 5347.5 5345 5342.5 5340 5335 5330 Page 4-98 Chapter 4: Reference information Country specific frequency range Frequency range 5.4 GHz band Table 208 Frequency range per country 5.4 GHz band PMP/PTP 450i Series Countries Antenna Type Channel BW Channel center Frequency limits (MHz) Mexico Any Other Any Other FCC Other ETSI 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz Lower 5472.5 5475 5477.5 5480 5485 5490 5472.5 5475 5477.5 5480 5485 5490 5475 5475 5480 5482.5 5487.5 5497.5 5472.5 5652.5 5475 5655 5477.5 5657.5 5480 5660 Upper 5722.5 5720 5717.5 5715 5710 5685 5722.5 5720 5717.5 5715 5710 5705 5720 5717.5 5717.5 5715 5710 5705 5597.5 5720 5595 5720 5592.5 5717.5 5590 5715 Page 4-99 Chapter 4: Reference information Country specific frequency range Countries Antenna Type Channel BW Channel center Frequency limits (MHz) Other ETSI 30 MHz 40 MHz Lower 5485 5665 5490 5670 Upper 5585 5710 5580 5705 Table 209 Frequency range per country 5.4 GHz band PMP 450b Mid-Gain Series Countries Antenna Type Channel BW FCC 16 dBi 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower

-

5477.5 5480 5482.5 5487.5 5490 (*) Upper

-

5720 5717.5 5715 5710 5705

(*) First channel at full power is 5495. Channel centers 5490 and 5492.5 need a power backoff of 5 dB. Table 210 Frequency range per country 5.4 GHz band PMP 450b High Gain Series Countries Antenna Type Channel BW FCC 23 dBi 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Channel center Frequency limits (MHz) Lower

-

5480 5487.5 5490 5495 5490 Upper

-

5720 5717.5 5715 5710 5705 Page 4-100 Chapter 4: Reference information Country specific frequency range Table 211 Frequency range per country 5.4 GHz band PMP/PTP 450 Series Channel center Frequency limits (MHz) Region code Country Code Channel BW Lower Other Any Other-FCC (Any non-US country that follows FCC rules Other-ETSI (Any country that follows ETSI rules Oceania Australia 5 MHz 5472.5 10 MHz 5475 15 MHz 5477.5 20 MHz 5480 30 MHz 5485 40 MHz 5490 5 MHz 5475 10 MHz 5477.5 15 MHz 5477.5 20 MHz 5480 30 MHz 5485 40 MHz 5490 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 5472.5 5652.5 5475 5655 5477.5 5657.5 5460 5640 5485 5665 5490 5670 5472.5 5652.5 5475 5645 Page 4-101 Upper 5722.5 5720 5717.5 5715 5710 5705 5720 5717.5 5717.5 5715 5710 5705 5597.5 5722.5 5595 5720 5592.5 5717.5 5590 5715 5585 5710 5580 5705 5597.5 5722.5 5595 5720 Chapter 4: Reference information Country specific frequency range Channel center Frequency limits (MHz) Region code Country Code Oceania Australia North America Canada South America Brazil Asia Vietnam Channel BW 15 MHz 20 MHz 30 MHz 40 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Lower 5477.5 5657.5 5465 5640 5485 5665 5490 5670 5475 5655 5477.5 5657.5 5480 5660 5485 5665 5490 5670 10 MHz 5475 15 MHz 5477.5 20 MHz 5480 30 MHz 5485 40 MHz 5490 10 MHz 5475 15 MHz 5477.5 20 MHz 5480 30 MHz 5485 40 MHz 5490 Page 4-102 Upper 5592.5 5717.5 5490 5715 5585 5710 5580 5705 5597.5 5722.5 5592.5 5717.5 5590 5715 5585 5710 5580 5705 5720 5717.5 5715 5710 5705 5720 5717.5 5715 5710 5705 Chapter 4: Reference information Country specific frequency range Channel center Frequency limits (MHz) Upper 5667.5 5665 5662.5 5660 5655 5650 5595 5720 5592.5 5717.5 5490 5715 5585 5710 5580 5705 Region code Country Code Channel BW Lower Africa Algeria Europe Europe (Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Liechtenstein, Norway, Portugal, Serbia, Spain, Switzerland, United Kingdom) 5 MHz 5472.5 10 MHz 5475 15 MHz 5477.5 20 MHz 5480 30 MHz 5485 40 MHz 5490 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5475 5655 5477.5 5657.5 5465 5660 5485 5665 5490 5670 Page 4-103 Chapter 4: Reference information Country specific frequency range Table 212 Frequency range per country 5.4 GHz band PMP 450m Series Countries Antenna Type Channel BW Channel center Frequency limits (MHz) United States, FCC Any ETSI Any Other Any 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz 5 MHz 10 MHz 15 MHz 20 MHz 30 MHz 40 MHz Lower 5475 5475 5480 5477.5 5485 5480 5490 5485 5490 5472.5 5652.5 5475 5655 5477.5 5657.5 5480 5660 5485 5665 5490 5670 5472.5 5475 5477.5 5480 5485 5490 Page 4-104 Upper 5720 5477.5 5720 5482.5 5717.5 5487.5 5715 5710 5705 5597.5 5722.5 5595 5720 5592.5 5717.5 5590 5715 5585 5710 5585 5705 5722.5 5720 5717.5 5715 5710 5705

 

 

Cambium 450 Platform User Guide System Release 15.1 33F pass Accuracy While reasonable efforts have been made to assure the accuracy of this document, Cambium Networks assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein. Cambium reserves the right to make changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Cambium does not assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey license under its patent rights or the rights of others. It is possible that this publication may contain references to, or information about Cambium products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that Cambium intends to announce such Cambium products, programming, or services in your country. Copyrights This document, Cambium products, and 3rd Party software products described in this document may include or describe copyrighted Cambium and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Cambium, its licensors, and other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any copyrighted material of Cambium, its licensors, or the 3rd Party software supplied material contained in the Cambium products described in this document may not be copied, reproduced, reverse engineered, distributed, merged or modified in any manner without the express written permission of Cambium. Furthermore, the purchase of Cambium products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Cambium or other 3rd Party supplied software, except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a product. 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 Cambium. License Agreements The software described in this document is the property of Cambium and its licensors. It is furnished by express license agreement only and may be used only in accordance with the terms of such an agreement. High Risk Materials Cambium and its supplier(s) specifically disclaim any express or implied warranty of fitness for any high risk activities or uses of its products including, but not limited to, the operation of nuclear facilities, aircraft navigation or aircraft communication systems, air traffic control, life support, or weapons systems (High Risk Use). Any High Risk Use is unauthorized, is made at your own risk and you shall be responsible for any and all losses, damage or claims arising out of any High Risk Use. 2017 Cambium Networks Limited. All Rights Reserved. pmp-1470 (January March 2017) Contents Cambium 450 Platform User Guide .................................................................................................... 1 Contents .................................................................................................................................................. i List of Figures ...................................................................................................................................... xii List of Tables ...................................................................................................................................... xvii About This User Guide .......................................................................................................................... 1 Contacting Cambium Networks .................................................................................................... 1 http://www.cambiumnetworks.com/support ........................................................................................ 1 http://www.cambiumnetworks.com ...................................................................................................... 1 solutions@cambiumnetworks.com ...................................................................................................... 1 support@cambiumnetworks.com ......................................................................................................... 1 rma@cambiumnetworks.com ............................................................................................................... 1 http://www.cambiumnetworks.com/contact ......................................................................................... 1 Purpose .................................................................................................................................................. 2 Product notation conventions in document ................................................................................ 2 Cross references ............................................................................................................................. 3 Feedback ......................................................................................................................................... 3 Important regulatory information........................................................................................................ 4 Application software ...................................................................................................................... 4 USA specific information............................................................................................................... 4 Canada specific information ......................................................................................................... 5 Renseignements specifiques au Canada ..................................................................................... 6 EU Declaration of Conformity ....................................................................................................... 7 Specific expertise and training for professional installers ......................................................... 7 Ethernet networking skills ............................................................................................................. 7 Lightning protection ....................................................................................................................... 8 Training ........................................................................................................................................... 8 Problems and warranty ........................................................................................................................ 9 Reporting problems ....................................................................................................................... 9 Repair and service .......................................................................................................................... 9 Hardware warranty ........................................................................................................................ 9 Security advice .................................................................................................................................... 10 Warnings, cautions, and notes .......................................................................................................... 11 Warnings ....................................................................................................................................... 11 Cautions ........................................................................................................................................ 11 Notes ............................................................................................................................................. 11 Caring for the environment ................................................................................................................ 12 In EU countries ............................................................................................................................. 12 Page i Contents In non-EU countries ..................................................................................................................... 12 Chapter 1: Product description ....................................................................................................... 1-1 Overview of the 450 Platform Family ............................................................................................... 1-2 Purpose ........................................................................................................................................ 1-2 PMP 450m Series ........................................................................................................................ 1-2 PMP/PTP 450i Series ................................................................................................................... 1-4 PMP/PTP 450 Series .................................................................................................................... 1-7 Supported interoperability for 450m/450i/450 Series ............................................................ 1-10 Typical deployment ................................................................................................................... 1-11 Product variants ........................................................................................................................ 1-13 Wireless operation ........................................................................................................................... 1-14 Time division duplexing ........................................................................................................... 1-14 Encryption .................................................................................................................................. 1-17 MIMO .......................................................................................................................................... 1-17 MU-MIMO .................................................................................................................................. 1-17 System management ....................................................................................................................... 1-19 Management agent ................................................................................................................... 1-19 Web server ................................................................................................................................. 1-19 Remote Authentication Dial-in User Service (RADIUS) ......................................................... 1-21 SNMP.......................................................................................................................................... 1-21 Network Time Protocol (NTP) .................................................................................................. 1-21 Wireless Manager (WM) ........................................................................................................... 1-22 cnMaestro ............................................................................................................................... 1-23 Radio recovery mode ................................................................................................................ 1-24 Chapter 2: System hardware .......................................................................................................... 2-1 System Components ......................................................................................................................... 2-2 Point-to-Multipoint (PMP) ........................................................................................................... 2-2 Backhaul (PTP) ............................................................................................................................. 2-5 450 Platform Family interfaces .................................................................................................. 2-7 Diagnostic LEDs ......................................................................................................................... 2-13 Power supply options ............................................................................................................... 2-18 ODU mounting brackets & accessories ................................................................................... 2-25 Lightning protection .................................................................................................................. 2-25 ODU interfaces ................................................................................................................................. 2-26 PMP 450m Series AP ................................................................................................................. 2-26 PMP/PTP 450i ............................................................................................................................. 2-27 Cabling .............................................................................................................................................. 2-29 Ethernet standards and cable lengths ..................................................................................... 2-29 Outdoor copper Cat5e Ethernet cable ..................................................................................... 2-31 SFP module kits ......................................................................................................................... 2-32 Main Ethernet port .................................................................................................................... 2-34 Aux port ..................................................................................................................................... 2-34 Lightning protection unit (LPU) and grounding kit ....................................................................... 2-38 Page ii Contents Cable grounding kit ................................................................................................................... 2-39 Antennas and antenna cabling ....................................................................................................... 2-40 Antenna requirements .............................................................................................................. 2-40 Supported external AP antennas ............................................................................................. 2-40 Supported external BH/SM antenna ........................................................................................ 2-40 RF cable and connectors........................................................................................................... 2-41 Antenna accessories ................................................................................................................. 2-41 GPS synchronization ........................................................................................................................ 2-42 GPS synchronization description ............................................................................................. 2-42 Universal GPS (uGPS) .............................................................................................................. 2-42 CMM4 (Rack Mount) ................................................................................................................ 2-43 CMM4 (Cabinet with switch) .................................................................................................. 2-52 CMM4 (Cabinet without switch) ............................................................................................ 2-52 CMM3/CMMmicro ..................................................................................................................... 2-53 Installing a GPS receiver ................................................................................................................. 2-55 GPS receiver location................................................................................................................ 2-55 Mounting the GPS receiver ...................................................................................................... 2-56 Cabling the GPS Antenna ......................................................................................................... 2-57 Installing and connecting the GPS LPU .................................................................................. 2-57 Ordering the components ............................................................................................................... 2-58 Chapter 3: System planning ........................................................................................................... 3-1 Typical deployment ........................................................................................................................... 3-2 ODU with PoE interface to PSU ................................................................................................. 3-2 Site planning....................................................................................................................................... 3-7 Site selection for PMP/PTP radios ............................................................................................. 3-7 Power supply site selection ........................................................................................................ 3-8 Maximum cable lengths ............................................................................................................. 3-8 Grounding and lightning protection .......................................................................................... 3-8 ODU and external antenna location ........................................................................................ 3-10 ODU ambient temperature limits ............................................................................................ 3-10 ODU wind loading ..................................................................................................................... 3-11 Drop cable grounding points ................................................................................................... 3-15 Lightning Protection Unit (LPU) location ................................................................................ 3-16 Radio Frequency planning .............................................................................................................. 3-17 Regulatory limits ....................................................................................................................... 3-17 Conforming to the limits........................................................................................................... 3-17 Available spectrum ................................................................................................................... 3-17 Analyzing the RF Environment ................................................................................................ 3-18 Channel bandwidth ................................................................................................................... 3-18 Anticipating Reflection of Radio Waves .................................................................................. 3-18 Obstructions in the Fresnel Zone ............................................................................................. 3-19 Planning for co-location............................................................................................................ 3-19 Multiple OFDM Access Point Clusters ..................................................................................... 3-20 Page iii Contents PMP 450m Series planning ...................................................................................................... 3-22 Link planning .................................................................................................................................... 3-23 Range and obstacles ................................................................................................................. 3-23 Path loss ..................................................................................................................................... 3-23 Calculating Link Loss ................................................................................................................ 3-24 Calculating Rx Signal Level ...................................................................................................... 3-24 Calculating Fade Margin ........................................................................................................... 3-25 Adaptive modulation ................................................................................................................ 3-25 Planning for connectorized units .................................................................................................... 3-26 When to install connectorized units ........................................................................................ 3-26 Choosing external antennas .................................................................................................... 3-26 Calculating RF cable length (5.8 GHz FCC only) ..................................................................... 3-26 Data network planning .................................................................................................................... 3-28 Understanding addresses......................................................................................................... 3-28 Dynamic or static addressing ................................................................................................... 3-28 DNS Client .................................................................................................................................. 3-29 Network Address Translation (NAT) ....................................................................................... 3-29 Developing an IP addressing scheme ..................................................................................... 3-30 Address Resolution Protocol .................................................................................................... 3-30 Allocating subnets ..................................................................................................................... 3-31 Selecting non-routable IP addresses ....................................................................................... 3-31 Translation bridging .................................................................................................................. 3-32 Engineering VLANs ................................................................................................................... 3-32 Network management planning ..................................................................................................... 3-36 Planning for SNMP operation .................................................................................................. 3-36 Enabling SNMP ......................................................................................................................... 3-36 Security planning ............................................................................................................................. 3-37 Isolating AP/BHM from the Internet ........................................................................................ 3-37 Encrypting radio transmissions ............................................................................................... 3-37 Planning for HTTPS operation ................................................................................................. 3-38 Planning for SNMPv3 operation .............................................................................................. 3-38 Managing module access by passwords ................................................................................ 3-39 Planning for RADIUS operation ............................................................................................... 3-40 Filtering protocols and ports .................................................................................................... 3-40 Encrypting downlink broadcasts ............................................................................................. 3-44 Isolating SMs in PMP ................................................................................................................ 3-44 Filtering management through Ethernet ................................................................................ 3-44 Allowing management from only specified IP addresses ..................................................... 3-45 Configuring management IP by DHCP .................................................................................... 3-45 Controlling PPPoE PADI Downlink Forwarding ...................................................................... 3-46 Legal and regulatory information ................................................................................ 4-1 Cambium Networks end user license agreement ........................................................................... 4-2 Definitions .................................................................................................................................... 4-2 Chapter 4:

Page iv Contents Acceptance of this agreement ................................................................................................... 4-2 Grant of license ........................................................................................................................... 4-2 Conditions of use ........................................................................................................................ 4-3 Title and restrictions ................................................................................................................... 4-4 Confidentiality ............................................................................................................................. 4-4 Right to use Cambiums name ................................................................................................... 4-5 Transfer ........................................................................................................................................ 4-5 Updates ........................................................................................................................................ 4-5 Maintenance ................................................................................................................................ 4-5 Disclaimer .................................................................................................................................... 4-6 Limitation of liability ................................................................................................................... 4-6 U.S. government ......................................................................................................................... 4-6 Term of license ............................................................................................................................ 4-7 Governing law ............................................................................................................................. 4-7 Assignment .................................................................................................................................. 4-7 Survival of provisions ................................................................................................................. 4-7 Entire agreement ......................................................................................................................... 4-7 Third party software .................................................................................................................... 4-7 Compliance with safety standards ................................................................................................. 4-22 Electrical safety compliance ..................................................................................................... 4-22 Electromagnetic compatibility (EMC) compliance ................................................................. 4-22 Human exposure to radio frequency energy .......................................................................... 4-22 Compliance with radio regulations ................................................................................................ 4-34 Type approvals .......................................................................................................................... 4-35 Brazil specific information ........................................................................................................ 4-36 Australia Notification ................................................................................................................ 4-36 Regulatory Requirements for CEPT Member States (www.cept.org) .................................. 4-36 Chapter 5: Preparing for installation .............................................................................................. 5-1 Safety .................................................................................................................................................. 5-2 Power lines .................................................................................................................................. 5-2 Working at heights ...................................................................................................................... 5-2 Power supply ............................................................................................................................... 5-2 Grounding and protective earth ................................................................................................ 5-3 Powering down before servicing ............................................................................................... 5-3 Primary disconnect device ......................................................................................................... 5-3 External cables ............................................................................................................................ 5-3 RF exposure near the antenna ................................................................................................... 5-3 Minimum separation distances ................................................................................................. 5-3 Grounding and lightning protection requirements .................................................................. 5-4 Grounding cable installation methods ...................................................................................... 5-4 Siting ODUs and antennas ......................................................................................................... 5-4 Thermal Safety ............................................................................................................................ 5-4 Preparing for installation ................................................................................................................... 5-6 Page v Contents Chapter 6:

ODU pre-configuration ............................................................................................................... 5-6 Preparing personnel .................................................................................................................... 5-6 Preparing inventory .................................................................................................................... 5-6 Preparing tools ............................................................................................................................ 5-7 Testing system components ............................................................................................................. 5-8 Unpacking Components ............................................................................................................. 5-8 Preparing the ODU ...................................................................................................................... 5-8 Configuring Link for Test ................................................................................................................. 5-17 Configuring the management PC ............................................................................................ 5-17 Logging into the web interface AP/SM/BH........................................................................... 5-18 Using the Quick Start Configuration Wizard of the AP/BHM ................................................ 5-18 Installation .................................................................................................................... 6-1 ODU variants and mounting bracket options .................................................................................. 6-2 Mount the ODU, LPU and surge suppressor ................................................................................... 6-3 Attach ground cables to the ODU .............................................................................................. 6-3 Mount the ODU on the mast ...................................................................................................... 6-6 Mount the top LPU ...................................................................................................................... 6-9 Mount the Surge Suppressor ..................................................................................................... 6-9 General protection installation ................................................................................................ 6-12 Installing the copper Cat5e Ethernet interface .............................................................................. 6-18 Install the main drop cable ....................................................................................................... 6-18 Install the bottom LPU to PSU drop cable .............................................................................. 6-20 Installing external antennas to a connectorized ODU .................................................................. 6-22 PMP 450i Series ......................................................................................................................... 6-22 PMP 450 Series .......................................................................................................................... 6-30 Attaching the PMP 450 Series AP and antenna to the mount point ..................................... 6-36 PMP 450i Series AP 900 MHz ................................................................................................... 6-39 PMP 450 Series SM 900 MHz ................................................................................................... 6-46 Installing an integrated ODU........................................................................................................... 6-50 PMP 450m Series AP .............................................................................................................. 6-50 PMP/PTP 450i Series AP/SM/BH ............................................................................................ 6-53 Connecting Cat5e Ethernet cable.................................................................................................... 6-54 Connecting an RJ45 and gland to a unit ................................................................................. 6-54 Disconnecting an RJ45 and gland from a unit ....................................................................... 6-56 Installing ODU .................................................................................................................................. 6-57 Installing a 450 Platform Family AP ......................................................................................... 6-57 Installing a 450 Platform Family SM ........................................................................................ 6-58 Installing a 450 Platform Family BHM ..................................................................................... 6-59 Installing a 450 platform BHS .................................................................................................. 6-60 Configuring the Link .................................................................................................................. 6-61 Monitoring the Link ................................................................................................................... 6-61 Installing the AC Power Injector ..................................................................................................... 6-62 Installing the AC Power Injector .............................................................................................. 6-62 Page vi Contents Installing CMM4 ............................................................................................................................... 6-63 Supplemental installation information .......................................................................................... 6-65 Stripping drop cable ................................................................................................................. 6-65 Creating a drop cable grounding point ................................................................................... 6-66 Attaching and weatherproofing an N type connector ........................................................... 6-70 Chapter 7: Configuration ................................................................................................................ 7-1 Preparing for configuration ............................................................................................................... 7-2 Safety precautions ...................................................................................................................... 7-2 Regulatory compliance ............................................................................................................... 7-2 Connecting to the unit ....................................................................................................................... 7-3 Configuring the management PC .............................................................................................. 7-3 Connecting to the PC and powering up .................................................................................... 7-4 Using the web interface ..................................................................................................................... 7-5 Logging into the web interface .................................................................................................. 7-5 Web GUI ....................................................................................................................................... 7-6 Using the menu options ............................................................................................................. 7-7 Quick link setup ................................................................................................................................ 7-12 Initiating Quick Start Wizard .................................................................................................... 7-12 Configuring time settings ......................................................................................................... 7-18 Powering the SM/BHS for test ................................................................................................. 7-19 Viewing the Session Status of the AP/BHM to determine test registration ......................... 7-20 Configuring IP and Ethernet interfaces .......................................................................................... 7-23 Configuring the IP interface ..................................................................................................... 7-24 Auxiliary port ............................................................................................................................. 7-27 NAT, DHCP Server, DHCP Client and DMZ ............................................................................. 7-28 DHCP BHS ............................................................................................................................... 7-45 Reconnecting to the management PC ..................................................................................... 7-45 VLAN configuration for PMP ........................................................................................................ 7-45 VLAN configuration for PTP ........................................................................................................ 7-55 PPPoE page of SM ..................................................................................................................... 7-59 IP4 and IPv6 ............................................................................................................................... 7-62 Upgrading the software version and using CNUT ........................................................................ 7-66 Checking the installed software version ................................................................................. 7-66 Upgrading to a new software version ..................................................................................... 7-66 General configuration ...................................................................................................................... 7-70 PMP 450m and PMP/PTP 450i Series ...................................................................................... 7-70 PMP/PTP 450 Series .................................................................................................................. 7-84 Configuring Unit Settings page ...................................................................................................... 7-89 Setting up time and date ................................................................................................................. 7-93 Time page of 450 Platform Family - AP/BHM ......................................................................... 7-93 Configuring synchronization ........................................................................................................... 7-95 Configuring security ........................................................................................................................ 7-97 Managing module access by password .................................................................................. 7-98 Page vii Contents Isolating from the internet APs/BHMs ................................................................................ 7-101 Encrypting radio transmissions ............................................................................................. 7-101 Requiring SM Authentication ................................................................................................. 7-102 Filtering protocols and ports .................................................................................................. 7-103 Encrypting downlink broadcasts ........................................................................................... 7-106 Isolating SMs ........................................................................................................................... 7-106 Filtering management through Ethernet .............................................................................. 7-107 Allowing management only from specified IP addresses ................................................... 7-107 Restricting radio Telnet access over the RF interface .......................................................... 7-107 Configuring SNMP Access ..................................................................................................... 7-110 Configuring Security ............................................................................................................... 7-112 Configuring radio parameters....................................................................................................... 7-124 PMP 450m Series Configuring radio .................................................................................. 7-125 PMP/PTP 450i Series configuring radio .............................................................................. 7-129 PMP/PTP 450 Series configuring radio .............................................................................. 7-147 Custom Frequencies page ...................................................................................................... 7-164 DFS for 5 GHz Radios .............................................................................................................. 7-167 MIMO-A mode of operation .................................................................................................... 7-169 Improved PPS performance of 450 Platform Family ............................................................... 7-171 Setting up SNMP agent ................................................................................................................. 7-172 Configuring SM/BHSs IP over-the-air access ...................................................................... 7-173 Configuring SNMP .................................................................................................................. 7-174 Configuring syslog ......................................................................................................................... 7-179 Syslog event logging .............................................................................................................. 7-180 Configuring system logging ................................................................................................... 7-180 Configuring remote access ........................................................................................................... 7-185 Accessing SM/BHS over-the-air by Web Proxy .................................................................... 7-185 Monitoring the Link ........................................................................................................................ 7-186 Link monitoring procedure ..................................................................................................... 7-186 Exporting Session Status page of AP/BHM .......................................................................... 7-188 Configuring quality of service ....................................................................................................... 7-189 Maximum Information Rate (MIR) Parameters .................................................................... 7-189 Token Bucket Algorithm ......................................................................................................... 7-189 MIR Data Entry Checking ........................................................................................................ 7-190 Committed Information Rate (CIR) ........................................................................................ 7-190 Bandwidth from the SM Perspective ..................................................................................... 7-191 Interaction of Burst Allocation and Sustained Data Rate Settings ..................................... 7-191 High-priority Bandwidth ......................................................................................................... 7-191 Traffic Scheduling ................................................................................................................... 7-193 Setting the Configuration Source .......................................................................................... 7-194 Configuring Quality of Service (QoS) .................................................................................... 7-196 Installation Color Code .................................................................................................................. 7-202 Zero Touch Configuration Using DHCP Option 66...................................................................... 7-203 Page viii Contents Configuration Steps ................................................................................................................ 7-203 Troubleshooting ...................................................................................................................... 7-208 Configuring Radio via config file .................................................................................................. 7-209 Import and Export of config file ............................................................................................. 7-209 Configuring cnMaestroTM Connectivity ........................................................................................ 7-211 Configuring a RADIUS server ....................................................................................................... 7-217 Understanding RADIUS for PMP 450 Platform Family ....................................................... 7-217 Choosing Authentication Mode and Configuring for Authentication Servers - AP ..... 7-218 SM Authentication Mode Require RADIUS or Follow AP ............................................ 7-223 Handling Certificates ............................................................................................................... 7-228 Configuring RADIUS servers for SM authentication ........................................................... 7-229 Assigning SM management IP addressing via RADIUS ...................................................... 7-231 Configuring RADIUS server for SM configuration ............................................................... 7-231 Configuring RADIUS server for SM configuration using Zero Touch feature ................... 7-235 Using RADIUS for centralized AP and SM user name and password management ........ 7-236 RADIUS Device Data Accounting ........................................................................................... 7-240 RADIUS Device Re-authentication ......................................................................................... 7-244 RADIUS Change of Authorization and Disconnect Message .............................................. 7-245 Microsoft RADIUS support ..................................................................................................... 7-246 Cisco ACS RADIUS Server Support ....................................................................................... 7-250 Configuring VSA ...................................................................................................................... 7-253 Chapter 8: Tools .............................................................................................................................. 8-1 Using Spectrum Analyzer tool .......................................................................................................... 8-2 Mapping RF Neighbor Frequencies ........................................................................................... 8-2 Spectrum Analyzer tool .............................................................................................................. 8-3 Remote Spectrum Analyzer tool .............................................................................................. 8-12 Using the Alignment Tool ............................................................................................................... 8-15 Aiming page and Diagnostic LED SM/BHS .......................................................................... 8-16 Alignment Tone ......................................................................................................................... 8-20 Using the Link Capacity Test tool ................................................................................................... 8-22 Performing Link Test ................................................................................................................. 8-22 Performing Extrapolated Link Test .......................................................................................... 8-29 Link Capacity Test page of AP .................................................................................................. 8-31 Link Capacity Test page of BHM/BHS/SM ............................................................................... 8-33 Using AP Evaluation tool ................................................................................................................. 8-34 AP Evaluation page ................................................................................................................... 8-34 Using BHM Evaluation tool ............................................................................................................. 8-38 BHM Evaluation page of BHS .................................................................................................. 8-38 Using the OFDM Frame Calculator tool ......................................................................................... 8-42 Using the Subscriber Configuration tool ....................................................................................... 8-47 Using the Link Status tool ............................................................................................................... 8-48 Link Status AP/BHM ............................................................................................................... 8-48 Link Status SM/BHS ............................................................................................................... 8-51 Page ix Contents Using BER Results tool .................................................................................................................... 8-54 Using the Sessions tool ................................................................................................................... 8-55 Chapter 9: Operation ...................................................................................................................... 9-1 System information ........................................................................................................................... 9-2 Viewing General Status .............................................................................................................. 9-2 Viewing Session Status ............................................................................................................ 9-22 Viewing Remote Subscribers ................................................................................................... 9-29 Interpreting messages in the Event Log ................................................................................. 9-29 Viewing the Network Interface ................................................................................................. 9-32 Viewing the Layer 2 Neighbors ................................................................................................ 9-33 System statistics .............................................................................................................................. 9-34 Viewing the Scheduler statistics .............................................................................................. 9-34 Viewing list of Registration Failures statistics ........................................................................ 9-36 Interpreting Bridging Table statistics ...................................................................................... 9-37 Interpreting Translation Table statistics.................................................................................. 9-38 Interpreting Ethernet statistics ................................................................................................. 9-39 Interpreting RF Control Block statistics ................................................................................... 9-42 Interpreting Sounding statistics ............................................................................................... 9-44 Interpreting VLAN statistics ..................................................................................................... 9-45 Interpreting Data VC statistics .................................................................................................. 9-47 Interpreting Throughput statistics ........................................................................................... 9-49 Interpreting Overload statistics ................................................................................................ 9-52 Interpreting DHCP Relay statistics ........................................................................................... 9-54 Interpreting Filter statistics ....................................................................................................... 9-56 Viewing ARP statistics .............................................................................................................. 9-57 Viewing NAT statistics .............................................................................................................. 9-57 Viewing NAT DHCP Statistics .................................................................................................. 9-59 Interpreting Sync Status statistics ........................................................................................... 9-60 Interpreting PPPoE Statistics for Customer Activities ........................................................... 9-61 Interpreting Bridge Control Block statistics ............................................................................ 9-63 Interpreting Pass Through Statistics ....................................................................................... 9-66 Interpreting SNMPv3 Statistics ................................................................................................ 9-67 Interpreting syslog statistics .................................................................................................... 9-69 Interpreting Frame Utilization statistics .................................................................................. 9-69 Radio Recovery ................................................................................................................................ 9-74 Radio Recovery Console PMP/PTP 450i and PMP 450m ...................................................... 9-74 Default Mode (or Default/Override Plug) - PMP/PTP 450 Series ........................................... 9-76 Reference Information ............................................................................................. 10-1 Equipment specifications ................................................................................................................ 10-2 Specifications for PMP 450m Series - AP................................................................................ 10-2 Specifications for PMP 450i Series - AP .................................................................................. 10-5 Specifications for PMP 450i Series - SM ................................................................................. 10-9 Specifications for PTP 450i Series - BH ................................................................................. 10-13 Chapter 10:

Page x Contents Chapter 11:

Specifications for PMP 450 Series - AP ................................................................................. 10-17 Specifications for PMP 450 Series - SM ................................................................................ 10-22 Specifications for PTP 450 Series - BH .................................................................................. 10-26 PSU specifications ................................................................................................................... 10-31 Data network specifications .......................................................................................................... 10-33 Ethernet interface .................................................................................................................... 10-33 Wireless specifications .................................................................................................................. 10-34 General wireless specifications ............................................................................................. 10-34 Link Range and Throughput ................................................................................................... 10-35 Country specific radio regulations ............................................................................................... 10-36 Type approvals ........................................................................................................................ 10-36 DFS for 2.4 and 5 GHz Radios ................................................................................................ 10-37 Equipment Disposal ....................................................................................................................... 10-38 Waste (Disposal) of Electronic and Electric Equipment ....................................................... 10-38 Country specific maximum transmit power ......................................................................... 10-38 Country specific frequency range .......................................................................................... 10-48 FCC specific information......................................................................................................... 10-60 Innovation Science and Economic Development Canada (ISEDC) specific information . 10-65 Troubleshooting ...................................................................................................... 11-1 General troubleshooting procedure ............................................................................................... 11-2 General planning for troubleshooting ..................................................................................... 11-2 General fault isolation process ................................................................................................ 11-3 Secondary Steps ....................................................................................................................... 11-4 Troubleshooting procedures ........................................................................................................... 11-5 Module has lost or does not establish connectivity .............................................................. 11-5 NAT/DHCP-configured SM has lost or does not establish connectivity .............................. 11-7 SM Does Not Register to an AP ............................................................................................... 11-9 Module has lost or does not gain sync ................................................................................. 11-10 Module does not establish Ethernet connectivity ................................................................ 11-11 CMM4 does not pass proper GPS sync to connected modules.......................................... 11-12 Module Software Cannot be Upgraded ................................................................................ 11-13 Module Functions Properly, Except Web Interface Became Inaccessible ......................... 11-13 Power-up troubleshooting ............................................................................................................ 11-14 Registration and connectivity troubleshooting ........................................................................... 11-15 SM/BMS Registration .............................................................................................................. 11-15 Appendix A - 450m Reference Information ........................................................................................... I A.1 Specifications ................................................................................................................................... I A.2 450m overload ................................................................................................................................. I Glossary ................................................................................................................................................ III Page xi List of Figures List of Figures Figure 1 PMP/PTP 450 Platform Family typical bridge deployment.................................. 1-11 Figure 2 TDD frame division ............................................................................................... 1-14 Figure 3 PMP/PTP 450 Series - AP interfaces ...................................................................... 2-9 Figure 4 PMP/PTP 450 Series SM/BH interfaces ............................................................ 2-10 Figure 5 PMP/PTP 450 Series SM/BH Connectorized interfaces .................................... 2-11 Figure 6 PMP 450d Series - SM Integrated Dish ............................................................... 2-12 Figure 7 PMP 450 Series SM 3 GHz Integrated .............................................................. 2-12 Figure 8 PTP 450 Series BHM/BHS ................................................................................. 2-12 Figure 9 AP/BHM diagnostic LEDs, viewed from unit front .............................................. 2-15 Figure 10 AP/BH diagnostic LEDs, viewed from unit front ................................................ 2-17 Figure 11 AC Power Injector interfaces ............................................................................. 2-20 Figure 12 AC+DC Enhanced Power Injector interfaces ..................................................... 2-21 Figure 13 -48 V DC Power Injector interfaces .................................................................... 2-23 Figure 14 Gigabit Enet Capable power supply ................................................................... 2-24 Figure 15 PMP 450m Series - AP rear interfaces ............................................................... 2-26 Figure 16 PMP/PTP 450i Series - ODU rear interfaces ...................................................... 2-27 Figure 17 PMP/PTP 450i Series Connectorized ODU antenna interfaces ...................... 2-28 Figure 18 Outdoor drop cable ............................................................................................. 2-31 Figure 19 Alignment Tone Cable ........................................................................................ 2-35 Figure 21 Cable gland (part number #N000065L033) ...................................................... 2-37 Figure 20 Cable grounding kit ............................................................................................ 2-39 Figure 22 uGPS .................................................................................................................... 2-42 Figure 23 CMM4 (Rack Mount) .......................................................................................... 2-49 Figure 24 CMM4 56 V power adapter (dongle) .................................................................. 2-50 Figure 25 CMM4 power adapter cabling diagram ............................................................. 2-50 Figure 26 CMM4 (Cabinet with switch).............................................................................. 2-52 Figure 27 CMM3 ................................................................................................................. 2-53 Figure 28 Pole mounted CMM3 .......................................................................................... 2-53 Figure 29 GPS antenna mounting ....................................................................................... 2-56 Figure 30 Mast or tower installation .................................................................................... 3-2 Figure 31 Wall installation .................................................................................................... 3-3 Figure 32 Roof installation .................................................................................................... 3-4 Figure 33 GPS receiver wall installation .............................................................................. 3-5 Figure 34 GPS receiver tower or mast installation .............................................................. 3-6 Figure 35 Rolling sphere method to determine the lightning protection zones .................. 3-9 Figure 36 Example layout of 16 Access Point sectors (ABCD), 90 degree sectors ........... 3-20 Figure 37 Example layout of 6 Access Point sectors (ABC), 60 degree sectors ................ 3-21 Figure 38 PMP 450m Series AP antenna beam .................................................................. 3-22 Figure 39 Determinants in Rx signal level .......................................................................... 3-24 Figure 40 Cambium networks management domain .......................................................... 3-29 Page xii List of Figures Figure 41 Example of IP address in Class B subnet ........................................................... 3-31 Figure 42 Categorical protocol filtering ............................................................................. 3-42 Figure 43 Pin 1 location ...................................................................................................... 5-11 Figure 44 Straight-through Ethernet Cable ....................................................................... 5-13 Figure 45 AP/BHM to UGPS cable ...................................................................................... 5-15 Figure 46 Alignment tone cable pin configuration ............................................................. 5-16 Figure 47 RJ-12 pinout for the default plug ........................................................................ 5-16 Figure 48 PMP 450 900 MHz SM grounding........................................................................ 6-6 Figure 49 Gigabit Etherner Surge Suppressor ................................................................... 6-10 Figure 50 600SSH Surge Suppressor inside ................................................................... 6-11 Figure 51 Grounding cable minimum bend radius and angle ............................................ 6-13 Figure 52 Grounding and lightning protection on mast or tower ...................................... 6-14 Figure 53 Grounding and lightning protection on wall ...................................................... 6-15 Figure 54 Grounding and lightning protection on building ............................................... 6-17 Figure 55 RJ45 cable ........................................................................................................... 6-19 Figure 56 AP antenna parts ................................................................................................ 6-24 Figure 57 Antenna top plate ............................................................................................... 6-25 Figure 58 Attaching antenna plate to the AP ..................................................................... 6-25 Figure 59 Attaching the plate ............................................................................................. 6-26 Figure 60 Connect the port A and B to the PMP 450i AP .................................................. 6-26 Figure 61 AP antenna upper bracket assembly .................................................................. 6-27 Figure 62 AP antenna upper bracket attached to upper adjustment arms ....................... 6-27 Figure 63 Rear strap connected to upper AP antenna bracket .......................................... 6-28 Figure 64 Assembled upper bracket connected to AP antenna ......................................... 6-28 Figure 65 AP Antenna Lower Bracket Assembly ................................................................ 6-28 Figure 66 Lower bracket attached to AP antenna .............................................................. 6-29 Figure 67 Completed AP and antenna assembly ................................................................ 6-29 Figure 68 PMP 450 AP antenna parts ................................................................................. 6-30 Figure 69 AP antenna upper bracket assembly ................................................................. 6-31 Figure 70 AP antenna upper bracket attached to upper adjustment arms ...................... 6-31 Figure 71 Rear strap connected to upper AP antenna bracket ........................................ 6-32 Figure 72 Assembled upper bracket connected to AP antenna ........................................ 6-32 Figure 73 AP Antenna Lower Bracket Assembly ............................................................... 6-33 Figure 74 Lower bracket attached to AP antenna ............................................................. 6-33 Figure 75 Attaching bracket to the rear of the AP ............................................................ 6-34 Figure 76 Lower bracket attached to AP antenna ............................................................. 6-34 Figure 77 Mounted PMP 450 AP and antenna assembly, viewed from back and back .... 6-35 Figure 78 Attaching the AP antenna upper bracket to the pole ........................................ 6-36 Figure 79 Attaching the AP antenna lower bracket to the pole ......................................... 6-36 Figure 80 Variables for calculating angle of elevation (and depression) .......................... 6-38 Figure 81 PMP 450i AP 900 MHz antenna unbox view ..................................................... 6-39 Figure 82 PMP 450i AP 900 MHz antenna inventory ........................................................ 6-39 Figure 83 Attaching radio mounting PMP 450i AP 900 MHz antenna to the pole ........... 6-44 Figure 84 900 MHz sector antenna alignment .................................................................. 6-45 Page xiii List of Figures Figure 85 PMP 450i SM 900 MHz external directional antenna ....................................... 6-46 Figure 86 Attach the antenna to the pole .......................................................................... 6-46 Figure 87 Fixing the nuts ................................................................................................... 6-47 Figure 88 Fixing the radio to the antenna .......................................................................... 6-48 Figure 89 Connecting RF cable to the radio ....................................................................... 6-48 Figure 90 Yagi antenna alignment - horizontally ............................................................... 6-49 Figure 91 Yagi antenna alignment - upward tilt ................................................................ 6-49 Figure 92 Yagi antenna alignment - downward tilt ........................................................... 6-49 Figure 93 PMP 450m Series - AP unbox view ................................................................... 6-50 Figure 94 Fixing the mounting plate to the back of the ODU ............................................ 6-53 Figure 95 Attaching the bracket body ................................................................................ 6-53 Figure 96 Ethernet cable gland for PMP/PTP 450 Series ................................................. 6-55 Figure 97 Ethernet cable gland for PMP/PTP 450i Series ................................................ 6-55 Figure 99 Disarm Installation page (top and bottom of page shown)................................ 7-12 Figure 100 Regional Settings tab of AP/BHM .................................................................... 7-13 Figure 101 Radio Carrier Frequency tab of AP/BHM ........................................................ 7-14 Figure 102 Synchronization tab of AP/BHM ....................................................................... 7-15 Figure 103 LAN IP Address tab of the AP/BHM ................................................................. 7-16 Figure 104 Review and Save Configuration tab of the AP/BHM ........................................ 7-17 Figure 105 Time tab of the AP/BHM ................................................................................... 7-18 Figure 106 Time and date entry formats ............................................................................ 7-19 Figure 107 Session Status tab of AP ................................................................................... 7-21 Figure 108 NAT disabled implementation .......................................................................... 7-29 Figure 109 NAT with DHCP client and DHCP server implementation .............................. 7-30 Figure 110 NAT with DHCP client implementation ........................................................... 7-30 Figure 111 NAT with DHCP server implementation .......................................................... 7-31 Figure 112 NAT without DHCP implementation ................................................................ 7-31 Figure 113 General page attributes - PMP 450 AP ............................................................ 7-85 Figure 114 General page attributes - PMP 450 SM ........................................................... 7-86 Figure 115 General page attributes - PTP 450 BHM ......................................................... 7-87 Figure 116 General page attributes - PTP 450 BHS ........................................................... 7-88 Figure 117 Sync Setting configuration ............................................................................... 7-95 Figure 118 AP Evaluation Configuration parameter of Security tab for PMP ................. 7-100 Figure 119 BHM Evaluation Configuration parameter of Security tab for PTP .............. 7-100 Figure 120 RF Telnet Access Restrictions (orange) and Flow through (green) .............. 7-107 Figure 121 RF Telnet Access Restriction (orange) and Potential Security Hole (green) 7-108 Figure 122 Multicast VC statistics .................................................................................... 7-162 Figure 123 Multicast scheduler statistics ......................................................................... 7-163 Figure 124 AP DFS Status ................................................................................................ 7-167 Figure 125 AP Session Status page .................................................................................. 7-185 Figure 126 AP Remote Subscribers page ......................................................................... 7-185 Figure 127 Session Status page ........................................................................................ 7-186 Figure 128 Exporting Session Status page of PMP 450m AP .......................................... 7-188 Figure 129 Uplink and downlink rate caps adjusted to apply aggregate cap ................. 7-190 Page xiv List of Figures Figure 130 Uplink and downlink rate cap adjustment example ...................................... 7-190 Figure 131 Installation Color Code of AP ......................................................................... 7-202 Figure 132 Configuration File upload and download page .............................................. 7-209 Figure 133 Software Upgrade from cnMaestro ............................................................ 7-212 Figure 134 DNS Test for cnMaestro connectivity ......................................................... 7-213 Figure 135 Device Agent Logs .......................................................................................... 7-214 Figure 136 Example cnMaestro screenshot .................................................................. 7-215 Figure 137 SM Certificate Management .......................................................................... 7-229 Figure 138 User Authentication and Access Tracking tab of the AP ............................... 7-236 Figure 139 User Authentication and Access Tracking tab of the SM .............................. 7-239 Figure 140 RADIUS accounting messages configuration ................................................ 7-243 Figure 141 Device re-authentication configuration ......................................................... 7-244 Figure 142 RADIUS CoA configuration for AP ................................................................. 7-245 Figure 143 EAPPEAP settings ........................................................................................... 7-246 Figure 144 Importing certificate in NPS .......................................................................... 7-247 Figure 145 Selecting MD5 from NPS console .................................................................. 7-248 Figure 146 User configuration .......................................................................................... 7-248 Figure 147 RADIUS VSA configuration ............................................................................ 7-249 Figure 148 Adding RADIUS client .................................................................................... 7-250 Figure 149 Creating users ................................................................................................ 7-250 Figure 150 Creating RADIUS instance ............................................................................. 7-251 Figure 151 RADIUS protocols ........................................................................................... 7-251 Figure 152 Service selection ............................................................................................. 7-252 Figure 153 Adding Trusted CA ......................................................................................... 7-252 Figure 154 Installing Server Certificate ........................................................................... 7-252 Figure 155 Monitoring logs ............................................................................................... 7-253 Figure 156 VSA list ............................................................................................................ 7-254 Figure 157 Spectrum analysis - Results ............................................................................... 8-3 Figure 158 Spectrum Analyzer page result PMP 450 SM ............................................... 8-11 Figure 159 Alignment Tool tab of SM Receive Power Level > -70 dBm ......................... 8-15 Figure 160 Alignment Tool tab of SM Receive Power Level between -70 to -80 dBm ... 8-15 Figure 161 Alignment Tool tab of SM Receive Power Level < -80 dBm ......................... 8-15 Figure 162 PMP/PTP 450i Series link alignment tone ....................................................... 8-20 Figure 163 Link Capacity Test PMP 450m Series AP ...................................................... 8-23 Figure 164 Link Test with Multiple VCs (1518-byte packet length) .................................. 8-25 Figure 165 Link Capacity Test PMP 450/450i Series AP ................................................. 8-27 Figure 166 Link Test without Bridging (1714-byte packet length) .................................... 8-28 Figure 167 Extrapolated Link Test results ......................................................................... 8-30 Figure 168 SM Configuration page of AP ........................................................................... 8-47 Figure 169 BER Results tab of the SM ............................................................................... 8-54 Figure 170 Sessions tab of the AP ...................................................................................... 8-55 Figure 171 Remote Subscribers page of AP ....................................................................... 9-29 Figure 172 Event log data ................................................................................................... 9-30 Figure 173 Network Interface tab of the AP ...................................................................... 9-32 Page xv List of Figures Figure 174 Network Interface tab of the SM ..................................................................... 9-32 Figure 175 Layer 2 Neighbors page ................................................................................... 9-33 Figure 176 Bridging Table page ......................................................................................... 9-38 Figure 177 Translation Table page of SM .......................................................................... 9-38 Figure 178 ARP page of the SM .......................................................................................... 9-57 Figure 179 Recovery Options page ..................................................................................... 9-75 Page xvi List of Tables List of Tables Table 1 Main characteristics of the PMP 450m Series AP ................................................... 1-3 Table 2 PMP 450m Series hardware configurations ............................................................ 1-3 Table 3 Main characteristics of the PMP/PTP 450i Series ................................................... 1-4 Table 4 PMP/PTP 450i Series hardware configurations ....................................................... 1-6 Table 5 Main characteristics of the PMP/PTP 450 Series .................................................... 1-7 Table 6 PMP/PTP 450 Series hardware configurations ........................................................ 1-9 Table 7 Supported Interoperability for PMP ..................................................................... 1-10 Table 8 Supported Interoperability for PTP ...................................................................... 1-10 Table 9 Modulation levels ................................................................................................... 1-16 Table 10 PMP 450m Series variants ..................................................................................... 2-2 Table 11 PMP 450i Series variants ....................................................................................... 2-3 Table 12 PMP 450 Series variants ........................................................................................ 2-4 Table 13 PTP 450i Series variants ........................................................................................ 2-5 Table 14 PTP 450 Series variants ......................................................................................... 2-6 Table 15 PMP 450m Series AP interface descriptions and cabling ..................................... 2-7 Table 16 PMP/PTP 450i Series - AP/SM/BH interface descriptions and cabling ................. 2-9 Table 17 PMP/PTP 450 Series - AP interface descriptions and cabling 2.4 GHz and 5 GHz

........................................................................................................................................ 2-10 Table 18 PMP/PTP 450i ATEX/HAZLOC ODU models/part numbers ................................ 2-13 Table 18 AP/BHM LED descriptions ................................................................................... 2-16 Table 19 SM/BHS LED descriptions ................................................................................... 2-17 Table 20 PSU part numbers for PMP 450m AP .................................................................. 2-18 Table 21 PSU part numbers for PMP/PTP 450i Series ....................................................... 2-19 Table 22 AC Power Injector interface functions ................................................................. 2-20 Table 23 AC+DC Enhanced Power Injector interface functions ........................................ 2-22 Table 24 -48V DC Power Injector interfaces ...................................................................... 2-23 Table 25 PSU part numbers for PMP/PTP 450 Series ........................................................ 2-24 Table 26 Gigabit Enet Capable power supply ................................................................... 2-24 Table 27 Accessories part numbers .................................................................................... 2-25 Table 28 Lightning protection part numbers ...................................................................... 2-25 Table 29 PMP 450m Series AP rear interfaces ................................................................ 2-26 Table 30 PMP/PTP 450i Series ODU rear interfaces ....................................................... 2-27 Table 31 PSU drop cable length restrictions ...................................................................... 2-29 Table 32 Drop cable part numbers ..................................................................................... 2-31 Table 33 SFP module kit part numbers ............................................................................. 2-32 Table 34 Single Mode Optical SFP Interface per ODU (part number C000065L008) ..... 2-32 Table 35 Multi-mode Optical SFP Interface per ODU (part number C000065L009) ....... 2-32 Table 33 Main port PoE cable pinout .................................................................................. 2-34 Table 34 Aux port PoE cable pinout .................................................................................... 2-34 Table 35 Aux port PoE cable pinout .................................................................................... 2-35 Page xvii List of Tables Table 36 RJ12 Aux port PoE cable pinout ........................................................................... 2-36 Table 36 Alignment tone adapter third party product details ........................................... 2-36 Table 37 RJ45 connector and spare gland part numbers ................................................... 2-37 Table 38 LPU and grounding kit contents .......................................................................... 2-38 Table 39 LPU and grounding kit part number .................................................................... 2-39 Table 40 Cable grounding kit part numbers ....................................................................... 2-39 Table 41 List of AP external antennas ................................................................................ 2-40 Table 42 PTP 450i Series BH or PMP 450/450i Series SM external antenna ................... 2-40 Table 43 RF cable and connector part numbers ................................................................ 2-41 Table 47 CMM5 Cluster Management Scenario 1 ............................................................. 2-43 Table 47 CMM5 Cluster Management Scenario 2 ............................................................. 2-45 Table 47 Injector Compatibility Matrix ............................................................................... 2-47 Table 47 CMM5 Specifications ........................................................................................... 2-48 Table 44 CMM4 power adapter cable pinout ..................................................................... 2-51 Table 45 PMP 450m Series ODU part numbers ................................................................. 2-58 Table 46 PMP 450i Series ODU part numbers ................................................................... 2-58 Table 47 PTP 450i Series ODU part numbers .................................................................... 2-59 Table 48 PMP 450 Series ODU part numbers .................................................................... 2-60 Table 49 PTP 450 Series ODU part numbers ..................................................................... 2-62 Table 50 PMP/PTP 450/450I Series Accessories ................................................................ 2-62 Table 51 PMP 450m Series wind loading (Newton) ........................................................... 3-12 Table 52 PMP/PTP 450i Series wind loading (Newton) ...................................................... 3-12 Table 53 PMP 450m Series wind loading (lb force) ........................................................... 3-12 Table 54 PMP/PTP 450i Series wind loading (lb force) ...................................................... 3-13 Table 55 PMP/PTP 450 Series wind loading (Newton) ....................................................... 3-13 Table 56 PMP/PTP 450 Series wind loading (lb force) ....................................................... 3-14 Table 50 EIRP limits from ATEX and HAZLOC standards ................................................ 3-15 Table 57 Example 5.8 GHz 4-channel assignment by access site ...................................... 3-20 Table 58 Example 5.8 GHz 3-channel assignment by access site ...................................... 3-21 Table 59 RF cable lengths required to achieve 1.2 dB loss at 5.8 GHz ............................. 3-27 Table 60 Special case VLAN IDs ......................................................................................... 3-33 Table 61 VLAN filters in point-to-multipoint modules ........................................................ 3-34 Table 62 Q-in-Q Ethernet frame .......................................................................................... 3-35 Table 63 HTTPS security material ...................................................................................... 3-38 Table 64 Ports filtered per protocol selections ................................................................... 3-43 Table 65 Device default port numbers ................................................................................ 3-43 Table 66 Safety compliance specifications ......................................................................... 4-22 Table 67 EMC emissions compliance .................................................................................. 4-22 Table 68 FCC minimum safe distances PMP 450m 5.1 GHz, 5.2 GHz, 5.4 GHz and 5.8 GHz

........................................................................................................................................ 4-25 Table 69 FCC minimum safe distances PMP/PTP 450i 900 MHz, 3.65 GHz, 4.9 GHz, 5.1 GHz, 5.2 GHz, 5.4 GHz and 5.8 GHz ............................................................................. 4-26 Table 70 ISEDC minimum safe distances PMP/PTP 450i, 900 MHz, 3.5 GHz, 3.65 GHz, 4.9 GHz, 5.2 GHz, 5.4 GHz, and 5.8 GHz ............................................................................ 4-27 Page xviii List of Tables Table 71 FCC minimum safe distances PMP/PTP 450 900 MHz, 2.4 GHz, 3.65 GHz and 5 GHz ................................................................................................................................. 4-29 Table 72 ISEDC minimum safe distances PMP/PTP 450 900 MHz, 2.4 GHz, 3.5/3.65 GHz and 5 GHz....................................................................................................................... 4-30 Table 73 Radio certifications............................................................................................... 4-35 Table 74 Tools for PMP and PTP 450 Platform ODU installation ........................................ 5-9 Table 75 Main port pinout ................................................................................................... 5-12 Table 76 Aux port pinout ..................................................................................................... 5-12 Table 77 RJ-45 pinout for straight-through Ethernet cable ............................................... 5-13 Table 78 RJ-45 pinout for crossover Ethernet cable........................................................... 5-14 Table 79 AP/BHM to UGPS cable pinout ............................................................................ 5-15 Table 80 PMP/PTP 450i Series - ODU mounting bracket part numbers .............................. 6-2 Table 81 RJ45 connector and cable color code ................................................................... 6-19 Table 82 Menu options and web pages ................................................................................. 7-7 Table 83 Session Status Attributes AP ............................................................................. 7-22 Table 84 IP interface attributes .......................................................................................... 7-25 Table 85 SM/BHS private IP and LUID ............................................................................... 7-26 Table 86 Aux port attributes ............................................................................................... 7-27 Table 87 IP attributes - SM with NAT disabled .................................................................. 7-33 Table 88 IP attributes - SM with NAT enabled ................................................................... 7-35 Table 89 NAT attributes - SM with NAT disabled .............................................................. 7-36 Table 90 NAT attributes - SM with NAT enabled ............................................................... 7-39 Table 91 SM DNS Options with NAT Enabled .................................................................... 7-44 Table 92 NAT Port Mapping attributes - SM ...................................................................... 7-44 Table 93 VLAN Remarking Example ................................................................................... 7-46 Table 94 AP/BHM VLAN tab attributes .............................................................................. 7-48 Table 95 Q-in-Q Ethernet frame .......................................................................................... 7-49 Table 96 SM VLAN attributes ............................................................................................. 7-51 Table 97 SM VLAN Membership attributes ........................................................................ 7-55 Table 98 BHM VLAN page attributs ................................................................................... 7-55 Table 99 BHS VLAN page attributes .................................................................................. 7-58 Table 100 SM PPPoE attributes .......................................................................................... 7-60 Table 101 DiffServ attributes AP/BHM ............................................................................ 7-62 Table 102 Packet Filter Configuration attributes ............................................................... 7-64 Table 103 General page attributes PMP 450i AP / PMP 450m AP .................................. 7-70 Table 104 General page attributes PMP 450i SM ............................................................ 7-77 Table 105 General page attributes PTP 450i BHM .......................................................... 7-80 Table 106 General page attributes PTP 450i BHS ........................................................... 7-82 Table 107 Unit Settings attributes 450 Platform Family AP/BHM .................................. 7-90 Table 108 SM Unit Settings attributes ............................................................................... 7-92 Table 109 450 Platform Family - AP/BHM Time attributes ............................................... 7-93 Table 110 Add User page of account page - AP/ SM/BH .................................................... 7-98 Table 111 Delete User page - 450 Platform Family - AP/ SM/BH ...................................... 7-99 Table 112 Change User Setting page - 450 Platform Family AP/ SM/BH .......................... 7-99 Page xix List of Tables Table 113 User page 450 Platform Family AP/SM/BH ................................................... 7-100 Table 114 AP/BHM Protocol Filtering attributes.............................................................. 7-103 Table 115 SM/BHS Protocol Filtering attributes .............................................................. 7-105 Table 116 Port Configuration attributes AP/SM/BHM/BMS .......................................... 7-106 Table 117 Security attributes 450 Platform Family AP .................................................. 7-112 Table 118 Security attributes 450 Platform Family SM ................................................. 7-117 Table 119 Security attributes - 450 Platform Family BHS ............................................... 7-122 Table 120 PMP 450m AP Radio attributes - 5 GHz .......................................................... 7-125 Table 121 PMP 450i AP Radio attributes - 5 GHz ............................................................ 7-130 Table 122 PMP 450i SM Radio attributes 5 GHz ........................................................... 7-136 Table 123 PMP 450i AP Radio attributes - 900 MHz ........................................................ 7-140 Table 124 PTP 450i BHM Radio page attributes 5 GHz ................................................ 7-142 Table 125 PTP 450i BHS Radio attributes 5 GHz .......................................................... 7-145 Table 126 PMP 450 AP Radio attributes - 5 GHz ............................................................. 7-147 Table 127 PMP 450 AP Radio attributes - 3.65 GHz ........................................................ 7-149 Table 128 PMP 450 AP Radio attributes - 3.5 GHz .......................................................... 7-150 Table 129 PMP 450 AP Radio attributes - 2.4 GHz .......................................................... 7-151 Table 130 PMP 450 SM Radio attributes 5 GHz ............................................................ 7-152 Table 131 PMP 450 SM Radio attributes 3.65 GHz ....................................................... 7-154 Table 132 PMP 450 SM Radio attributes 3.5 GHz ......................................................... 7-155 Table 133 PMP 450 SM Radio attributes 2.4 GHz ......................................................... 7-156 Table 134 PMP 450 SM Radio attributes 900 MHz ........................................................ 7-157 Table 135 PTP 450 BHM Radio attributes 5 GHz ........................................................... 7-159 Table 136 PTP 450 BHM Radio attributes 5 GHz ........................................................... 7-160 Table 137 Example for mix of multicast and unicast traffic scenarios ............................ 7-162 Table 138 450 Platform Family AP/SM/BH Custom Frequencies page 5 GHz ............. 7-164 Table 139 PMP/PTP 450 SM/BH Custom Frequencies page 3.65 GHz ......................... 7-165 Table 140 PMP/PTP 450 SM/BH Custom Frequencies page 3.5 GHz ........................... 7-166 Table 141 Contention slots and number of VCs ............................................................... 7-168 Table 142 450 Platform Family Modulation levels ........................................................... 7-169 Table 143 Co-channel Interference per (CCI) MCS ......................................................... 7-170 Table 144 Adjacent Channel Interference (ACI) per MCS ............................................... 7-170 Table 145 LAN1 Network Interface Configuration tab of IP page attributes .................. 7-173 Table 146 SNMP page attributes ...................................................................................... 7-175 Table 147 Syslog parameters ............................................................................................ 7-180 Table 148 Syslog Configuration attributes - AP ............................................................... 7-181 Table 149 Syslog Configuration attributes - SM .............................................................. 7-182 Table 150 Syslog Configuration attributes - BHS ............................................................. 7-183 Table 151 Characteristics of traffic scheduling ................................................................ 7-193 Table 152 Recommended combined settings for typical operations................................ 7-194 Table 153 Where feature values are obtained for a SM with authentication required ... 7-195 Table 154 MIR, VLAN, HPC, and CIR Configuration Sources, Authentication Disabled 7-195 Table 155 QoS page attributes - AP .................................................................................. 7-196 Table 156 QoS page attributes - SM ................................................................................. 7-198 Page xx List of Tables Table 157 QoS page attributes - BHM .............................................................................. 7-200 Table 158 QoS page attributes - BHS ............................................................................... 7-201 Table 159 Configuring cnMaestro .................................................................................... 7-211 Table 160 Security tab attributes ..................................................................................... 7-219 Table 161 SM Security tab attributes ............................................................................... 7-223 Table 162 RADIUS Vendor Specific Attributes (VSAs) ..................................................... 7-232 Table 163 AP User Authentication and Access Tracking attributes ................................ 7-237 Table 164 SM User Authentication and Access Tracking attributes ............................... 7-239 Table 165 Device data accounting RADIUS attributes ..................................................... 7-240 Table 166 Spectrum Analyzer page attributes - AP .............................................................. 8-5 Table 167 Spectrum Analyzer page attributes - SM ............................................................. 8-7 Table 168 Spectrum Analyzer page attributes - BHM .......................................................... 8-8 Table 169 Spectrum Analyzer page attributes - BHS ........................................................... 8-9 Table 170 Remote Spectrum Analyzer attributes - AP ....................................................... 8-13 Table 171 Remote Spectrum Analyzer attributes - BHM ................................................... 8-14 Table 172 Aiming page attributes SM .............................................................................. 8-17 Table 173 Aiming page attributes - BHS ............................................................................ 8-19 Table 174 Alignment Tool Headsets and Alignment tone adapter third party product details

........................................................................................................................................ 8-21 Table 174 Link Capacity Test page attributes AP ............................................................ 8-31 Table 175 Link Capacity Test page attributes BHM/BHS ............................................... 8-33 Table 176 AP Evaluation tab attributes - AP ....................................................................... 8-34 Table 177 BHM Evaluation tab attributes - BHS ................................................................ 8-38 Table 178 OFDM Frame Calculator page attributes .......................................................... 8-43 Table 179 OFDM Calculated Frame Results attributes ..................................................... 8-44 Table 180 Color code versus uplink/downlink rate column ............................................... 8-48 Table 181 Link Status page attributes AP/BHM .............................................................. 8-49 Table 182 Link Status page attributes SM/BHS .............................................................. 8-52 Table 183 General Status page attributes PMP 450m AP ................................................. 9-3 Table 184 General Status page attributes PMP 450/450i AP .......................................... 9-10 Table 185 General Status page attributes - SM ................................................................. 9-13 Table 186 General Status page attributes - BHM .............................................................. 9-17 Table 187 General Status page attributes - BHS ................................................................ 9-20 Table 188 Device tab attributes .......................................................................................... 9-22 Table 189 Session tab attributes ......................................................................................... 9-23 Table 190 Power tab attributes ........................................................................................... 9-25 Table 191 Configuration tab attributes .............................................................................. 9-27 Table 192 Session Status > Configuration CIR configuration denotations ....................... 9-28 Table 193 Event Log messages for abnormal events ......................................................... 9-31 Table 194 Event Log messages for normal events ............................................................. 9-31 Table 195 Scheduler tab attributes .................................................................................... 9-34 Table 196 SM Registration Failures page attributes - AP .................................................. 9-36 Table 197 BHS Registration Failures page attributes - BHM ............................................ 9-36 Table 198 Flags status ......................................................................................................... 9-37 Page xxi List of Tables Table 199 Ethernet tab attributes ....................................................................................... 9-39 Table 200 Radio (Statistics) page attributes RF Control Block ....................................... 9-42 Table 201 Radio (Statistics) page attributes - Sounding .................................................... 9-44 Table 202 VLAN page attributes ......................................................................................... 9-45 Table 203 Data VC page attributes ..................................................................................... 9-47 Table 204 RF overload Configuration attributes AP/BHM .............................................. 9-49 Table 205 Overload page attributes AP/SM/BHM/BHS ................................................... 9-52 Table 206 DHCP Relay page attributes AP/SM ................................................................ 9-55 Table 207 Filter page attributes - SM ................................................................................. 9-56 Table 208 NAT page attributes - SM .................................................................................. 9-58 Table 209 NAT DHCP Statistics page attributes - SM ....................................................... 9-59 Table 210 Sync Status page attributes - AP ....................................................................... 9-60 Table 211 PPPoE Statistics page attributes - SM ............................................................... 9-61 Table 212 Bridge Control Block page attributes AP/SM/BHM/BHS ............................... 9-63 Table 213 Pass Through Statistics page attributes AP .................................................... 9-66 Table 214 SNMPv3 Statistics page attributes AP ............................................................ 9-67 Table 215 Syslog statistics page attributes AP/SM/BH ................................................... 9-69 Table 216 Frame utilization statistics ................................................................................. 9-70 Table 217 Recovery Options attributes .............................................................................. 9-75 Table 218 PMP 450m Series - AP specifications ................................................................ 10-2 Table 219 PMP 450i Series - AP specifications .................................................................. 10-5 Table 220 PMP 450i Series - SM specifications ................................................................. 10-9 Table 221 PTP 450i Series - BH specifications ................................................................. 10-13 Table 222 PMP 450 Series - AP specifications ................................................................. 10-17 Table 223 PMP 450 Series - SM specifications ................................................................ 10-22 Table 224 PTP 450i Series - BH specifications ................................................................. 10-26 Table 225 PMP/PTP 450i AC power Injector specifications ............................................. 10-31 Table 226 PMP/PTP 450 power supply specifications (part number: N000900L001A) .. 10-32 Table 227 450m/450i Series Main and Aux Ethernet bridging specifications ................. 10-33 Table 228 450 Series Ethernet bridging specifications ................................................... 10-33 Table 229 450 Platform Family - wireless specifications ................................................. 10-34 Table 230 Radio certifications ......................................................................................... 10-36 Table 231 Country & Bands DFS setting .......................................................................... 10-37 Table 232 Default combined transmit power per country 900 MHz band PMP 450i Series

...................................................................................................................................... 10-38 Table 233 Default combined transmit power per country 2.4 GHz band PMP/PTP 450 Series ........................................................................................................................... 10-39 Table 234 Default combined transmit power per country 3.5 GHz band PMP/PTP 450 Series ........................................................................................................................... 10-39 Table 235 Default combined transmit power per country 3.65 GHz band PMP/PTP 450 10-

40 Table 236 Default combined transmit power per country 4.9 GHz band PMP/PTP 450/450i Series ........................................................................................................................... 10-40 Table 237 Default combined transmit power per Country 5.1 GHz band PMP/PTP 450i Series ........................................................................................................................... 10-41 Page xxii List of Tables Table 238 Default combined transmit power per country 5.2 GHz band ...................... 10-42 Table 239 Default combined transmit power per Country 5.2 GHz band PMP 450m Series

...................................................................................................................................... 10-42 Table 240 Default combined transmit power per country 5.4 GHz band PMP 450m Series

...................................................................................................................................... 10-43 Table 241 Default combined transmit power per country 5.4 GHz band PMP/PTP 450i Series ........................................................................................................................... 10-44 Table 242 Default combined transmit power per country 5.4 GHz band PMP 450 Series10-

45 Table 243 Default combined transmit power per Country 5.8 GHz band PMP 450m Series

...................................................................................................................................... 10-46 Table 244 Default combined transmit power per country 5.8 GHz band PMP/PTP 450i Series ........................................................................................................................... 10-46 Table 245 Default combined transmit power per country 5.8 GHz band PMP 450 Series10-

47 Table 246 Frequency range per country 900 MHz band ............................................... 10-48 Table 247 Frequency range per country 2.4 GHz band PMP/PTP 450 Series .............. 10-49 Table 248 Frequency range per country 3.5 GHz band PMP/PTP 450 Series .............. 10-49 Table 249 Frequency range per country 3.65 GHz band PMP/PTP 450 Series ............ 10-50 Table 250 Frequency range per country 4.9 GHz band PMP/PTP 450i Series ............. 10-51 Table 251 Frequency range per country 5.4 GHz band PMP/PTP 450i Series ............. 10-52 Table 252 Frequency range per country 5.4 GHz band PMP/PTP 450 Series ........... 10-54 Table 253 Frequency range per country 5.8 GHz band PMP/PTP 450i Series ............. 10-56 Table 254 Frequency range per country 5.8 GHz band PMP/PTP 450 Series .............. 10-57 Table 255 US FCC IDs ....................................................................................................... 10-60 Table 256 USA approved antenna list 4.9 GHz ................................................................ 10-63 Table 257 USA approved antenna list 5.1 and 5.2 GHz ................................................... 10-64 Table 258 USA approved antenna list 5.4 GHz ................................................................ 10-64 Table 259 USA approved antenna list 5.8 GHz ................................................................ 10-65 Table 260 ISEDC Certification Numbers ......................................................................... 10-67 Table 261 Canada approved antenna list 4.9 and 5.8 GHz .............................................. 10-68 Table 262 Canada approved antenna list 5.2 and 5.4 GHz ............................................. 10-69 Page xxiii About This User Guide This guide describes the planning, installation, configuration and operation of the Cambium point-

to-point and point-to-multipoint wireless Ethernet bridges. It covers PMP/PTP 450, 450i, 450d and PMP 450m platform Series. It is intended for use by the system designer, system installer and system administrator. For radio network design, refer to the following chapters:

Chapter 1: Product description Chapter 2: System hardware Chapter 3: System planning Chapter 4: Legal and regulatory information Chapter 5: Preparing for installation Chapter 6: Installation For system configuration, tools and troubleshooting, refer to the following chapters:

Chapter 7: Configuration Chapter 8: Tools Chapter 9: Operation Chapter 10: Reference Information Chapter 11: Troubleshooting Contacting Cambium Networks Support website:

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

http://www.cambiumnetworks.com Sales enquiries:

solutions@cambiumnetworks.com Support enquiries:

support@cambiumnetworks.com Repair enquiries:

rma@cambiumnetworks.com Telephone number list:

http://www.cambiumnetworks.com/contact Address:

Cambium Networks Limited, Global Headquarters, 3800 Golf Road, Suite 360, Rolling Meadows, IL 60008 USA Page 1 Chapter 1: Product description Purpose Purpose Cambium Networks Point-to-Multi-Point (PMP)/Point-To-Point (PTP) 450 documents are intended to instruct and assist personnel in the operation, installation and maintenance of the Cambium PMP/PTP equipment and ancillary devices of 450 Platform Family. It is recommended that all personnel engaged in such activities be properly trained. Cambium disclaims all liability whatsoever, implied or express, for any risk of damage, loss or reduction in system performance arising directly or indirectly out of the failure of the customer, or anyone acting on the customer's behalf, to abide by the instructions, system parameters, or recommendations made in this document. Product notation conventions in document This document covers Cambium 450 Series, 450i Series and 450m Series products. The following notation conventions are followed while referring to product series and product family:

Product notation Description 450 Platform Family Refers complete 450 Series family includes 450 Series, 450i Series and 450m Series 450 Series Refers to 450 Series devices in following configurations:

- PMP 450

- AP [3.5 GHz/2.4GHz/3.65 GHz /5 GHz]

- Connectorized

- SM [900 MHz/ 3.5 GHz/2.4GHz/3.65 GHz /5 GHz]

- Connectorized/ Integrated

- PTP 450 BHM/ BHS [3.5 GHz/ 3.65 GHz / 5 GHz]

- Connectorized/ Integrated

- PMP 450d SM [5 GHz]

450i Series Refers to 450i Series devices in following configurations:

- PMP 450i

- AP [900 MHz/ 3 GHz/ 5 GHz]

- Connectorized/ Integrated

- SM [3 GHz/ 5 GHz]

- Connectorized/ Integrated

- PTP 450i BHM/ BHS [900 MHz/ 5 GHz]

- Connectorized/ Integrated 450m Series Refers to 450m Series device configuration:

- PMP 450m AP 5 GHz Integrated

-

Page 2 Chapter 1: Product description Purpose Cross references References to external publications are shown in italics. Other cross references, emphasized in blue text in electronic versions, are active links to the references. This document is divided into numbered chapters that are divided into sections. Sections are not numbered, but are individually named at the top of each page, and are listed in the table of contents. Feedback We appreciate feedback from the users of our documents. This includes feedback on the structure, content, accuracy, or completeness of our documents. Send feedback to support@cambiumnetworks.com. Page 3 Chapter 1: Product description Important regulatory information Important regulatory information The 450 Platform Family products are certified as an unlicensed device in frequency bands where it is not allowed to cause interference to licensed services (called primary users of the bands). Application software Download the latest 450 Platform Family software and install it in the Outdoor Units (ODUs) before deploying the equipment. Instructions for installing software are provided in Upgrading the software version and using CNUT on page 7-66. USA specific information Caution This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

This device may not cause harmful interference, and This device must accept any interference received, including interference that may cause undesired operation The USA Federal Communications Commission (FCC) requires manufacturers to implement special features to prevent interference to weather radar systems that operate in the band 5600 MHz to 5650 MHz. These features must be implemented in all products able to operate outdoors in the band 5470 MHz to 5725 MHz. Manufacturers must ensure that such radio products cannot be configured to operate outside of FCC rules; specifically it must not be possible to disable or modify the radar protection functions that have been demonstrated to the FCC. Cambium supplies variants of the 450i and 450m Series specifically for operation in the USA in order to comply with FCC requirements (KDB 905462 D02 UNII DFS Compliance Procedures New Rules v01r02). These variants are only allowed to operate with license keys that comply with FCC rules. Similarly, Cambium supplies variants of the 450 Series specifically for operation in the USA in order to comply with FCC requirements (KDB 443999 D01 Approval of DFS UNII Devices v01r04). These variants are only allowed to operate with license keys that comply with FCC rules. To ensure compliance when using PMP 450 Series and PTP 450 Series, follow the recommendation in Avoidance of weather radars (USA only). Page 4 Chapter 1: Product description Important regulatory information External antennas When using a connectorized version of the product, the conducted transmit power may need to be reduced to ensure the regulatory limit on transmitter EIRP is not exceeded. The installer must have an understanding of how to compute the effective antenna gain from the actual antenna gain and the feeder cable losses. The range of permissible values for maximum antenna gain and feeder cable losses are included in this user guide together with a sample calculation. The product GUI automatically applies the correct conducted power limit to ensure that it is not possible for the installation to exceed the EIRP limit, when the appropriate values for antenna gain and feeder cable losses are entered into the GUI. Avoidance of weather radars (USA only) To comply with FCC rules (KDB 443999: Interim Plans to Approve UNII Devices Operating in the 5470 - 5725 MHz Band with Radar Detection and DFS Capabilities), units which are installed within 35 km (22 miles) of a Terminal Doppler Weather Radar (TDWR) system (or have a line of sight propagation path to such a system) must be configured to avoid any frequency within +30 MHz or 30 MHz of the frequency of the TDWR device. This requirement applies even if the master is outside the 35 km (22 miles) radius but communicates with outdoor clients which may be within the 35 km (22 miles) radius of the TDWRs. If interference is not eliminated, a distance limitation based on line-of-sight from TDWR will need to be used. Devices with bandwidths greater than 20 MHz may require greater frequency separation. When planning a link in the USA, visit http://spectrumbridge.com/udia/home.aspx, enter the location of the planned link and search for TDWR radars. If a TDWR system is located within 35 km

(22 miles) or has line of sight propagation to the PTP device, perform the following tasks:

Register the installation on http://spectrumbridge.com/udia/home.aspx. Make a list of channel center frequencies that must be barred, that is, those falling within

+30 MHz or 30 MHz of the frequency of the TDWR radars. The 450 Platform Family AP must be configured to not operate on the affected channels. Canada specific information Caution This device complies with ISEDC s license-exempt RSSs. Operation is subject to the following two conditions:

(1) This device may not cause interference; and

(2) This device must accept any interference, including interference that may cause undesired operation of the device. ISEDC requires manufacturers to implement special features to prevent interference to weather radar systems that operate in the band 5600 MHz to 5650 MHz. These features must be implemented in all products able to operate outdoors in the band 5470 MHz to 5725 MHz. Page 5 Chapter 1: Product description Important regulatory information Manufacturers must ensure that such radio products cannot be configured to operate outside of ISEDC rules; specifically it must not be possible to disable or modify the radar protection functions that have been demonstrated to ISEDC . In order to comply with these ISEDC requirements, Cambium supplies variants of the 450 Platform Family for operation in Canada. These variants are only allowed to operate with license keys that comply with ISEDC rules. In particular, operation of radio channels overlapping the band 5600 MHz to 5650 MHz is not allowed and these channels are permanently barred. In addition, other channels may also need to be barred when operating close to weather radar installations. Other variants of the 450 Platform Family are available for use in the rest of the world, but these variants are not supplied to Canada except under strict controls, when they are needed for export and deployment outside Canada. Renseignements specifiques au Canada Attention Le prsent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorise aux deux conditions suivantes :

(1) l'appareil ne doit pas produire de brouillage, et

(2) l'utilisateur de l'appareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible d'en compromettre le fonctionnement. ISEDC a demand aux fabricants de mettre en uvre des mcanismes spcifiques pour viter dinterfrer avec des systmes radar fonctionnant dans la bande 5600 MHz 5650 MHz. Ces mcanismes doivent tre mis en uvre dans tous les produits capables de fonctionner l'extrieur dans la bande 5470 MHz 5725 MHz. Les fabricants doivent s'assurer que les produits de radiocommunications ne peuvent pas tre configurs pour fonctionner en dehors des rgles ISEDC , en particulier, il ne doit pas tre possible de dsactiver ou modifier les fonctions de protection des radars qui ont t dmontrs ISEDC . Afin de se conformer ces exigences de ISEDC , Cambium fournit des variantes du 450 Platform Family exclusivement pour le Canada. Ces variantes ne permettent pas lquipement de fonctionner en dehors des rgles de ISEDC . En particulier, le fonctionnement des canaux de radio qui chevauchent la bande 5600-5650 MHz est interdite et ces canaux sont dfinitivement exclus. ISEDC Approved Antennas The list of antennas used to obtain ISEDC approvals is provided in section Country specific radio regulations, Innovation Science and Economic Development Canada (ISEDC) , Table 272. Page 6 Chapter 1: Product description Important regulatory information Antennas externes Lorsque vous utilisez une version du produit sans antenne intgre, il peut tre ncessaire de rduire la puissance d'mission pour garantir que la limite rglementaire de puissance isotrope rayonne quivalente (PIRE) n'est pas dpasse. L'installateur doit avoir une bonne comprhension de la faon de calculer le gain de l'antenne relle et les pertes dans les cbles de connections. La plage de valeurs admissibles pour un gain maximal de l'antenne et des pertes de cbles de connections sont inclus dans ce guide d'utilisation avec un exemple de calcul. L'interface utilisateur du produit applique automatiquement la limite de puissance mene correct afin de s'assurer qu'il ne soit pas possible pour l'installation de dpasser la limite PIRE, lorsque les valeurs appropries pour le gain d'antenne et les pertes de cbles d'alimentation sont entres dans linterface utilisateur. Antennes approuves par ISEDC La liste des antennas approves pour loperation au Canada est founie dans le chapitre Country specific radio regulations, Innovation Science and Economic Development Canada (ISEDC) tableaux Table 272. EU Declaration of Conformity Hereby, Cambium Networks declares that the Cambium 450 Series, 450i Series and 450m Series Wireless Ethernet Bridge complies with the essential requirements and other relevant provisions of Directive 1999/5/EC. The declaration of conformity may be consulted at:

http://www.cambiumnetworks.com/support/ec-doc Specific expertise and training for professional installers To ensure that the 450 Platform Family products PMP/PTP 450 Series, PMP/PTP 450i Series, PMP 450m Series are installed and configured in compliance with the requirements of ISEDC and the FCC, installers must have the radio engineering skills and training described in this section. The Cambium Networks technical training program details can be accessed from below link:

http://www.cambiumnetworks.com/training/category/technical-training/

Ethernet networking skills The installer must have the ability to configure IP addressing on a PC and to set up and control products using a web browser interface. Page 7 Chapter 1: Product description Important regulatory information Lightning protection To protect outdoor radio installations from the impact of lightning strikes, the installer must be familiar with the normal procedures for site selection, bonding and grounding. Installation guidelines for the 450 Platform Family can be found in Chapter 2: System hardware and Chapter 3:

System planning. Training The installer needs to have basic competence in radio and IP network installation. The specific requirements applicable to the 450 Platform should be gained by reading Chapter 5: Preparing for installation, Chapter 6: Installation, Chapter 7: Configuration, Chapter 8: Tools and Chapter 9:

Operation; and by performing sample set ups at base workshop before live deployments. The Cambium Networks technical training program details can be accessed from below link:

http://www.cambiumnetworks.com/training/category/technical-training/

Page 8 Chapter 1: Product description Problems and warranty Problems and warranty Reporting problems If any problems are encountered when installing or operating this equipment, follow this procedure to investigate and report:

1 Search this document and the software release notes of supported releases. 2 Visit the support website. 3 Ask for assistance from the Cambium product supplier. 4 Gather information from affected units, such as any available diagnostic downloads. 5 Escalate the problem by emailing or telephoning support. Repair and service If unit failure is suspected, obtain details of the Return Material Authorization (RMA) process from the support website (http://www.cambiumnetworks.com/support). Hardware warranty Cambiums standard hardware warranty is for one (1) year from date of shipment from Cambium Networks or a Cambium distributor. Cambium Networks warrants that hardware will conform to the relevant published specifications and will be free from material defects in material and workmanship under normal use and service. Cambium shall within this time, at its own option, either repair or replace the defective product within thirty (30) days of receipt of the defective product. Repaired or replaced product will be subject to the original warranty period but not less than thirty (30) days. To register PMP and PTP products or activate warranties, visit the support website. For warranty assistance, contact the reseller or distributor. The removal of the tamper-evident seal will void the warranty. Caution Using non-Cambium parts for repair could damage the equipment or void warranty. Contact Cambium for service and repair instructions. Portions of Cambium equipment may be damaged from exposure to electrostatic discharge. Use precautions to prevent damage. Page 9 Chapter 1: Product description Security advice Security advice Cambium Networks systems and equipment provide security parameters that can be configured by the operator based on their particular operating environment. Cambium recommends setting and using these parameters following industry recognized security practices. Security aspects to be considered are protecting the confidentiality, integrity, and availability of information and assets. Assets include the ability to communicate, information about the nature of the communications, and information about the parties involved. In certain instances Cambium makes specific recommendations regarding security practices, however the implementation of these recommendations and final responsibility for the security of the system lies with the operator of the system. Page 10 Chapter 1: Product description Warnings, cautions, and notes Warnings, cautions, and notes The following describes how warnings and cautions are used in this document and in all documents of the Cambium Networks document set. Warnings Warnings precede instructions that contain potentially hazardous situations. Warnings are used to alert the reader to possible hazards that could cause loss of life or physical injury. A warning has the following format:

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

Caution Caution text and consequence for not following the instructions in the caution. Notes A note means that there is a possibility of an undesirable situation or provides additional information to help the reader understand a topic or concept. A note has the following format:

Note Note text. Page 11 Chapter 1: Product description Caring for the environment Caring for the environment The following information describes national or regional requirements for the disposal of Cambium Networks supplied equipment and for the approved disposal of surplus packaging. In EU countries The following information is provided to enable regulatory compliance with the European Union

(EU) directives identified and any amendments made to these directives when using Cambium equipment in EU countries. Disposal of Cambium equipment European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE) Do not dispose of Cambium equipment in landfill sites. For disposal instructions, refer to http://www.cambiumnetworks.com/support/weee-compliance Disposal of surplus packaging Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipients responsibility to ensure that packaging materials are collected and recycled according to the requirements of EU environmental law. In non-EU countries In non-EU countries, dispose of Cambium equipment and all surplus packaging in accordance with national and regional regulations. Page 12 Chapter 1: Product description This chapter provides a high level description of 450 Platform Family products. It describes in general terms the function of the product, the main product variants and the main hardware components. The following topics are described in this chapter:

Overview of the 450 Platform Family on page 1-2 introduces the key features, typical uses, product variants and components of the 450 Platform Family. Wireless operation on page 1-14 describes how the 450 Platform Family wireless link is operated, including modulation modes and spectrum management. System management on page 1-19 introduces the 450 Platform Family management system, including the web interface, configuration, security, alerts and recovery. Page 1-1 Chapter 1: Product description Overview of the 450 Platform Family Overview of the 450 Platform Family This section introduces the key features, typical uses, product variants and components of the 450 Platform Family. Purpose Cambium 450 Platform Family products are designed for Ethernet bridging over point-to-point and point-to-multipoint microwave links in unlicensed and lightly-licensed frequency bands 900MHz, 2.4 GHz, 3.5/3.65 GHz and 4.9 to 5.925 GHz. Users must ensure that the 450 Platform Family complies with local operating regulations. The 450 Platform Family acts as a transparent bridge between two or more segments of the operators network. In this sense, it can be treated as a virtual wired connection among points. The 450 Series platform forwards 802.3 Ethernet frames destined for the other part of the network and filters frames it does not need to forward. 450 Platform Family The 450 Series platform supports following:

PMP 450m Series PMP/PTP 450i Series PMP/PTP 450 Series PMP 450m Series The PMP 450m Series AP is a revolutionary product which is based on Multi-User Multiple-Input and Multiple-Output (MU-MIMO) technology. By combining a sophisticated beam forming antenna array with multiple transceivers, Cambium Networks is using leading edge technology to provide a substantial shift upward in capacity per sector. Key features The Cambium PMP 450m Series AP offers the following benefits:

MU-MIMO Access Point is a technologically cutting edge device providing more than 400 Mbps in 20 MHz Channel bandwidth depending upon SMs position within sector PMP 450m AP is compatible with existing PMP 450/450i Series Subscriber Modules(SM), providing an easy network upgrade path. This benefits to re-use existing SMs (i.e. capital investment). 3x higher throughput packet rate compare 450 Series Integrated with 14x14 MU-MIMO antenna Gigabit copper/power port combined, 1000BaseT port with power out and SFP port Page 1-2 Chapter 1: Product description Overview of the 450 Platform Family More than 20 bps/Hz spectral efficiency and over 40 bps/Hz when deployed in frequency re-use configuration Table 1 gives a summary of the main PMP 450m Series AP characteristics. Table 1 Main characteristics of the PMP 450m Series AP Characteristic Topology Value PMP Wireless link condition LOS, near LOS or non-LOS Range Duplexing PMP: Up to 40 mi (or 64 km) TDD (symmetric and asymmetric) Connectivity 1000Base-T Ethernet Main port with PoE input Operating frequencies 5.150 to 5.925 GHz Tx Power max 24 dBm Channel bandwidth 5 MHz, 20 MHz High spectral efficiency More than 40 bps/Hz. Timing synchronization CMM5 or uGPS Data rate more than 400 Mbps (20 MHz channel BW) Frequency bands The PMP 450m Series AP operates from 5150 to 5925 MHz bands. Hardware components The ODU (Outdoor unit) is a self-contained transceiver unit that houses both radio and networking electronics. The PMP 450m Series is supplied in the following configurations:

Table 2 PMP 450m Series hardware configurations ODU Frequency ODU type PMP 450m AP 5150 to 5925 MHz Integrated 14 dBi, 90 MU-MIMO sector antenna Page 1-3 Chapter 1: Product description Overview of the 450 Platform Family PMP/PTP 450i Series The PMP/PTP 450i Series is a high performance wireless bridge for Ethernet traffic. It is capable of operating in line-of-sight (LOS), near-LOS and non-LOS propagation conditions. It supports 900 MHz and 4.9 to 5.925 GHz frequency band. Key features The PMP/PTP 450i Series has extensive quality of service (QoS) involving traffic classification, traffic policy and shaping capability. The Cambium PMP/PTP 450i Series offers the following benefits:

Cambiums high performing point-to-multipoint solution, with up to 230 Mbps (30 MHz Channel Bandwidth and 5 ms Frame Period) usable throughput for PMP and PTP State-of-the-art MIMO (Multi In Multi Out) technology Upto 7.5 bps/Hz spectral efficiency Increased Packet Processing rate Efficient GPS synchronized, scheduled TDD operation for easy AP/BHM site deployment and performance that is consistent regardless of SM/BHS loading A range of cost-effective subscriber device solutions to meet the business case of any network application MIMO B Mode: This technique provides for the ability to double the throughput of a radio transmission under proper RF conditions. Different data streams are transmitted simultaneously on two different antennas MIMO-A mode: This mode of operation has same modulation levels as the MIMO-B mode, namely: QPSK, 16-QAM, 64-QAM and 256-QAM. This mode increases system reliability in the links. Timing synchronization via CMM4 or uGPS Table 3 gives a summary of the main PMP/PTP 450i Series characteristics. Table 3 Main characteristics of the PMP/PTP 450i Series Characteristic Topology Value PMP/PTP Wireless link condition LOS, near LOS or non-LOS Range PTP Up to 186 mi (or 299 km) depending on configuration for Duplexing Connectivity all bands PMP: Up to 40 mi (or 64 km) for 5 GHz band PMP: Up to 120 mi (or 193 km) for 900 MHz band TDD (symmetric and asymmetric) 1000Base-T Ethernet Main port with PoE input Operating frequencies 902 to 928 MHz Page 1-4 Chapter 1: Product description Overview of the 450 Platform Family Tx Power 4.9 to 5.925 GHz max 27 dBm (5 GHz) max 25 dBm (900 MHz) Channel bandwidth 5, 7, 10, 15, 20 and 30 MHz Spectral efficiency Up to 7.5 bps/Hz Timing synchronization CMM4 or uGPS Data rate Up to 230 Mbps (30 MHz channel BW) for PMP/PTP Frequency bands The PMP/PTP 450i Series ODU can operate in the following bands:

900 MHz band: 902 to 928 MHz 5 GHz band: 4900 to 5925 MHz o 4.9 GHz band: 4940 to 4990 MHz o 5.1 GHz band: 5150 to 5250 MHz o 5.2 GHz band: 5250 to 5350 MHz o 5.4 GHz band: 5470 to 5725 MHz o 5.8 GHz band: 5725 to 5925 MHz Note 900 MHz band requires different hardware. Hardware components The ODU (Outdoor unit) is a self-contained transceiver unit that houses both radio and networking electronics. The main hardware components of the PMP/PTP 450i Series are as follows:

PMP 450i AP PMP 450i SM PTP 450i BH (BHM/BHS) Page 1-5 Chapter 1: Product description Overview of the 450 Platform Family The PMP/PTP 450i Series is supplied in the following configurations:

Table 4 PMP/PTP 450i Series hardware configurations ODU Frequency ODU type PMP 450i AP 902 to 928 MHz Connectorized Use with an external antenna 3.3 to 3.9 GHz Integrated 17 dBi, 90 sector dual slant antenna Connectorized Use with an external antenna 4.9 to 5925 GHz Integrated 16 dBi, 90 sector antenna

(support 4.9, 5.1, 5.2, 5.4 and 5.8 GHz) Connectorized Use with an external antenna PMP 450i SM 3.3 to 3.9 GHz Integrated 19 dBi, SM/BH with MARS antenna 4.9 to 5925 GHz Integrated 23 dBi flat panel antenna

(support 4.9, 5.1, 5.2, 5.4 and 5.8 GHz) Connectorized Use with an external antenna PTP 450i BH 3.3 to 3.9 GHz Connectorized Use with an external antenna 4.9 to 5925 GHz Integrated 23 dBi flat panel antenna

(support 4.9, 5.1, 5.2, 5.4 and 5.8 GHz) Connectorized Use with an external antenna Note The BH ODU can be configured as a BHM or a BHS in PTP mode. Page 1-6 Chapter 1: Product description Overview of the 450 Platform Family PMP/PTP 450 Series Cambium PMP/PTP 450 Series networks are designed for wireless point-to-multipoint and point-to-

point links in the unlicensed/licensed 900 MHz, 2.4 GHz, 3.5 GHz, 3.65 GHz, 5.4 GHz and 5.8 GHz bands. Users must ensure that the PMP/PTP 450 Series complies with local operating regulations. The PMP/PTP 450 Series enables network operators to grow their business by offering more capacity for data, voice and video applications. Key features The Cambium PMP/PTP 450 Series offers the following benefits:

Cambiums point-to-multipoint and point-to-point solution, with up to 230 Mbps usable throughput State-of-the-art MIMO (Multi In Multi Out) technology Efficient GPS synchronized, scheduled TDD operation for easy Access Point site deployment and performance that is consistent regardless of subscriber loading A range of cost-effective subscriber device solutions to meet the business case of a network application MIMO-B Mode: This technique provides for the ability to double the throughput of a radio transmission under proper RF conditions. Different data streams are transmitted simultaneously on two different antennas. MIMO-A mode: This mode of operation using the same modulation levels as the MIMO-B mode, namely: QPSK, 16-QAM, 64-QAM and 256-QAM but it provides an additional combining gain. Table 5 gives a summary of PMP/PTP 450 Series products main characteristics . Table 5 Main characteristics of the PMP/PTP 450 Series Characteristic Topology Value PMP/PTP Wireless link condition LOS, near LOS or non-LOS Range Up to 40 mi (or 64 km) for PMP Duplexing Connectivity Up to 186 mi (or 299 km) for PTP TDD (symmetric and asymmetric) 100Base-T Ethernet Main port with PoE input Operating frequencies 900 MHz, 2.4 GHz, 3.5 GHz, 3.65 GHz and 5 GHz Tx Power max 27 dBm (2.4 GHz and 5 GHz) max 25 dBm (3.5 GHz and 3.65 GHz) max 25 dBm (900 MHz - PMP 450 SM only) Channel bandwidth 5, 7, 10, 15, 20 and 30 MHz Page 1-7 Chapter 1: Product description Overview of the 450 Platform Family High spectral efficiency Up to 7.5 bps/Hz Data rate Up to 230 Mbps (30 MHz channel BW) for PMP/PTP Frequency bands The PMP/PTP 450 Series ODU can operate in the following bands:

900 MHz band: 902 to 928 MHz (SM only) 2.4 GHz band: 2400 to 2483 MHz 3.5 GHz band: 3300 to 3600 MHz 3.65 GHz band: 3500 to 3850 MHz 5.4 GHz band: 5470 to 5725 MHz 5.8 GHz band: 5725 to 5875 MHz Note The 900 MHz, 2.4 GHz, 3.5 GHz, 3.65 GHz and 5 GHz bands require different hardware. The 5 GHz band (either 5.4 or 5.8 GHz) can be configured on same hardware. Page 1-8 Chapter 1: Product description Overview of the 450 Platform Family Hardware components The main hardware components of the PMP/PTP 450 are as follows:

PMP 450 AP PMP 450 SM PTP 450 BH (BHM/BHS) The PMP/PTP 450 is supplied in the following configurations:

Table 6 PMP/PTP 450 Series hardware configurations ODU Frequency ODU type PMP 450 AP 2.4 GHz Connectorized Use with an external antenna Integrated 18 dBi Dual Slant 3.5/3.65 GHz Connectorized Use with an external antenna Integrated 16 dBi Dual Slant 5 GHz Connectorized Use with an external antenna

(5.4 and 5.8 GHz) Integrated 17 dBi H+V PMP 450 SM 900 MHz Connectorized Use with an external antenna 2.4 GHz Connectorized Use with an external antenna Integrated 7 dBi Dual Slant, integrated patch 3.5/3.65 GHz Connectorized Use with an external antenna Integrated 8 dBi Dual Slant, integrated patch Integrated 19 dBi Flat Plate, integrated patch 5 GHz Connectorized Use with an external antenna

(5.4 and 5.8 GHz) Integrated 9 dBi H+V, integrated patch Integrated 25 dBi H+V, Integrated dish PTP 450 BH 902 to 928 MHz Connectorized Use with an external antenna 3.5/3.65 GHz Connectorized Use with an external antenna Integrated 8 dBi Dual Slant 5 GHz Connectorized Use with an external antenna

(5.4 and 5.8 GHz) Integrated 9 dBi H+V Note The BH ODU can be configured as a BHM or a BHS in PTP mode Page 1-9 Chapter 1: Product description Overview of the 450 Platform Family Supported interoperability for 450m/450i/450 Series The supported interoperability among various 450m/450i/450 Series hardwares are listed below:

Table 7 Supported Interoperability for PMP Band AP SM 5.1, 5.2 and 5.9 GHz PMP 450m AP PMP 450i SM (Greenfield) 4.9, 5.1, 5.2 and 5.9 GHz PMP 450i AP PMP 450i SM (Greenfield) 5.4 and 5.8 GHz PMP 450m AP PMP 450i SM, PMP 450 SM and PMP 450d PMP 450 AP SM 3 GHz PMP 450i AP 3 GHz PMP 450i SM, 3.5 GHz PMP 450 SM, and 3.65 GHz PMP 450 SM 2.4, 3.5 and 3.65 GHz PMP 450 AP PMP 450 SM 900 MHz PMP 450i AP PMP 450 SM Table 8 Supported Interoperability for PTP Band 900 MHz BH PTP 450i BHM and BHS 3.5 and 3.65 GHz PTP 450/450i BHM and BHS 4.9, 5.1, 5.2, 5.4 and 5.8 GHz PTP 450i BHM and BHS 5.4 and 5.8 GHz PTP 450 BHM and BHS Page 1-10 Chapter 1: Product description Overview of the 450 Platform Family Typical deployment The 450 Platform Family is an all outdoor solution consisting of a wireless bridge across sites. Each site installation consists of an Integrated or Connectorized outdoor unit (ODU) and a power supply (PSU) (see Figure 1). The ODU provides the following interfaces:

Ethernet port: This provides proprietary power over Ethernet and connection to the management and/or data networks. Figure 1 PMP/PTP 450 Platform Family typical bridge deployment Page 1-11 Building 1ODUAC supplyPSUNetworkequipmentBuilding 2ODUPSUNetworkequipmentAC supplyPower over Ethernet interfaceLightning protection unitsLightning protection units Chapter 1: Product description Overview of the 450 Platform Family Point-to-Multipoint The PMP configuration of 450 Platform Family consists of Access Point (AP) and Subscriber Module (SM) ODU. The radio link operates on a single frequency channel in each direction using Time Division Duplex (TDD). Applications for the PMP Series include:

High throughput enterprise applications nLOS video surveillance in metro areas Urban area network extension Network extension into areas with foliage Point-to-Point (Backhaul) The PTP configuration of 450 Platform Family consists of two BH (Backhaul) ODUs. The customer can decide, via software configuration, if this unit is a BHM (Backhaul Master) or a BHS (Backhaul Slave). The radio link operates on a single frequency channel using Time Division Duplex (TDD). Applications for the PTP Series include:

Enterprise Access nLOS video surveillance Leased line replacements and backup solutions Network extension Page 1-12 Chapter 1: Product description Overview of the 450 Platform Family Product variants The 450 Platform Family is available in the following product variants:

The ODU is supplied in the following regional variants:

o FCC, intended for deployment in the USA o EU, intended for deployment in countries of the European Union or other countries following ETSI regulations o Rest of the World (RoW), intended for deployment in countries other than USA and EU countries. o IC, intended for deployment in Canada A ruggedized ODU Subscriber Module designed to meet IP-66 and IP-67 standards to withstand harsh environments An integrated Dish ODU Subscriber Module in a new, rugged and high gain design for 5 GHz band An indoor power supply module providing Power-over-Ethernet (PoE) supply to ODU

(AP/SM/BH) Antennas and antenna cabling: Connectorized ODUs require external antennas connected using RF cable Ethernet cabling: All configurations require a copper Ethernet Cat5e connection from the ODU

(Ethernet port) to the PoE Lightning protection unit (LPU): LPUs are installed in the ports copper drop cables to provide transient voltage surge suppression Surge Suppression: The Gigabit Surge Suppressor provides a path to ground (Protective Earth) that protects connected radio equipment from near-miss lightning strikes. Ground cables: ODU, LPUs and outdoor copper Ethernet cables are bonded to the site grounding system using ground cables. For more information about these components, including interfaces, specifications and Cambium part numbers, refer to Chapter 2: System hardware. Page 1-13 Chapter 1: Product description Wireless operation Wireless operation This section describes how the 450 Platform Family wireless link is operated, including modulation modes, power control and security. Time division duplexing The system uses Time Division Duplexing (TDD) one channel alternately transmits and receives rather than using one channel for transmitting and a second channel for receiving. To accomplish TDD, the AP/BHM must provide sync to its SM/BHS. Furthermore, collocated APs/BHMs must be synced together an unsynchronized AP/BHM that transmits during the receive cycle of a collocated AP/BHM can prevent a second AP/BHM from being able to decode the signals from its APs/BHSs. In addition, across a geographical area, APs/BHMs that can hear each other benefit from using a common sync to further reduce self-interference within the network. Modules use TDD on a common frequency to divide frames for uplink (orange) and downlink

(green) usage, as shown in the figure below. For more information on synchronization configuration options, see GPS synchronization on page 2-42. Figure 2 TDD frame division Time Page 1-14 Chapter 1: Product description Wireless operation TDD frame parameters The TDD burst duration varies depending on the following:

Channel Bandwidth Cyclic Prefix Frame Period Frame configuration - Downlink Data Link operation Dynamic Rate Adaptation OFDM and channel bandwidth The PMP/PTP 450 Platform Family 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 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 the following values: 5, 7, 10, 15, 20 and 30 MHz. Higher bandwidths provide greater link capacity at the expense of using more bandwidth. 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. Note The channel bandwidth must be configured to the same value at both ends of the link. Not all channel bandwidths are available in all regulatory bands. Cyclic Prefix OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol (slot) to allow multi-pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. For your convenience, the 450 Platform Family ODUs have been locked to a 1/16 CP. Frame Period The frame period or frame duration is the time between the beginning of a frame and the end of the frame. The 450 Platform Family supports two frame periods: 2.5 ms and 5 ms. Note PMP 450m AP supports 2.5 ms Frame Period only. Page 1-15 Chapter 1: Product description Wireless operation The 5ms frame period configuration provides higher throughput as a result of reduced frame overhead during transmission. In turn, the 2.5 ms frame period configuration affords reduced latency in the system, half of that introduced by the 5 ms frame configuration. Frame configuration - Downlink Data The percentage of frame assigned to transport downlink data. The downlink data specifies the percentage of the aggregate throughput for the downlink (frames transmitted from the AP/BHM to the subscriber). The configurable range is 15 to 85 percent. Link operation Dynamic Rate Adapt The 450 Platform Family ODUs offer eight levels or speeds of operation 2X MIMO-B and 1X MIMO-A (QPSK), 4X MIMO-B and 2X MIMO-A (16-QAM), 6x MIMO-B and 3X MIMO-A (64-QAM) and 8X MIMO-B and 4X MIMO-A (265-QAM). If received power varies due to distance between the AP/BHM and the SM/BHS or due to obstructions, or if interference affects the RF environment, the system automatically and dynamically adjusts the links to the best operation level. The system chooses its modulation rate dynamically, based on an internal ARQ (Automatic Repeat reQuest) error control method. With ARQ, every data slot of every frame sent over the air (except downlink broadcast) is expected to be acknowledged by the receiver, and if acknowledgement is not received, the data is resent. The sending unit monitors these re-sends and adjusts the modulation rate accordingly. It is normal to have links that change levels of operation as the RF environment changes. Furthermore, the uplink or downlink portions of TDD duty cycle operate independently. The various modulation levels used by 450 Platform Family are shown in Table 9. Table 9 Modulation levels Rate MIMO-B MIMO-A QPSK 2X MIMO-B 1X MIMO-A 16-QAM 4X MIMO-B 2X MIMO-A 64-QAM 6X MIMO-B 3X MIMO-A 256-QAM 8X MIMO-B 4X MIMO-A Note MIMO-A achieves half the throughput of MIMO-B but adds a combining diversity (gain) which enhances the link budget or availability. Page 1-16 Chapter 1: Product description Wireless operation Encryption The 450 Platform Family supports optional encryption for data transmitted over the wireless link. The 450 Platform Family supports the following forms of encryption for security of the wireless link:

DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys and 256-bit key size to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. The default setting on an AP is "Disabled". MIMO Multiple-Input Multiple-Output (MIMO) techniques provide protection against fading and increase the probability that the receiver decodes 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 sub-features that comprises the MIMO techniques utilized in the 450 Platform Family ODUs are:

MIMO-A: This technique enables 450 Platform Family radio to use a scheme that optimizes coverage by transmitting the same data over both antennas. This redundancy improves the signal to noise ratio at the receiver making it more robust. MIMO-B: This technique provides for the ability to double the throughput of a radio transmission under proper RF conditions. Different data streams are transmitted simultaneously on two different antennas. MU-MIMO Multiple-input multiple-output, or MIMO, is a range of technologies used to multiply the capacity of a wireless connection without requiring more spectrum. Although traditional MIMO techniques are focused on increasing the bandwidth available between two wireless nodes, multi-user MIMO (MU-MIMO) applies these technologies to increase overall wireless network capacity by allowing an access point to communicate wirelessly with more than one wireless node at once. A MU-MIMO access point features an array of antennas.. When the AP decides to communicate with multiple nodes at the same time, it creates multiple simultaneous beams each directed to a specific node. Page 1-17 Chapter 1: Product description Wireless operation This is contrast to a traditional wireless system, where two wireless nodes cannot communicate on the same channel to the same access point at the same time, without causing significant self-

interference and degrading the overall wireless network performance. A MU-MIMO access point estimates and measures what a transmission from each wireless node sounds like, by applying knowledge of the wireless path characteristics between the access point and node. Known as channel estimation, this process is of vital importance; without it, the access point cannot distinguish properly between wireless nodes, affecting performance. Channel estimation is achieved by the access point sending a specific signal to a wireless node, which the node then reflects back. By measuring how the signal was received back from the node, the access point can estimate the wireless conditions between itself and the node, and know to expect these same conditions to be applied to other communications from that node. This is known as channel sounding. Channel estimation and sounding must be regularly repeated to ensure wireless network performance remains high; the speed at which a system is able to accurately estimate the channel has a large impact on performance. Once channel estimation is completed for a wireless node, the MU-MIMO access point can electrically tune each antenna to provide the highest performance for that node. The access point uses beamforming to create a radio beam to that node which is tuned for optimum performance and avoids beams directed to other nodes, reducing interference and helping to improve overall wireless network capacity. A MU-MIMO access point can communicate to multiple wireless nodes simultaneously using this process. As the majority of nodes are unable to make full use of the whole access point capacity at once, communicating with several nodes simultaneously can greatly improve the overall capacity achieved in the wireless network. Page 1-18 Chapter 1: Product description System management System management This section introduces the 450 Platform Family management system, including the web interface, installation, configuration, alerts and upgrades. Management agent The 450 Platform Family radios are managed through an embedded management agent. Management workstations, network management systems or PCs can be connected to this agent using the modules Ethernet port or over-the air (SM/BHS) The management agent supports the following interfaces:

Hypertext transfer protocol (HTTP) Hypertext transfer protocol secure (HTTPS) RADIUS authentication Simple network management protocol (SNMP) v2c and v3 Network time protocol (NTP) System logging (Syslog) Wireless Manager (WM) software Canopy Network Updater Tool (CNUT) software Web server The 450 Platform Family management agent contains a web server. The web server supports access via the HTTP/HTTPS interface. Web-based management offers a convenient way to manage the 450 Platform Family radios from a locally connected computer or from a network management workstation connected through a management network, without requiring any special management software. The web and SNMP are the interfaces supported for installation of 450 Platform Family radios and for the majority of configuration management tasks. Page 1-19 Chapter 1: Product description System management Web pages The web-based management interfaces provide comprehensive web-based fault, configuration, performance and security management functions organized into the following groups:

Access Point or Backhaul Master:

Home Configuration Statistics Tools Logs Accounts Quick Start Copyright Subscriber Module or Backhaul Slave Home Configuration Statistics Tools Logs Accounts PDA Copyright Identity-based user accounts When identity-based user accounts are configured, a security officer can define from one to four user accounts, each of which may have one of the four possible roles:

ADMINISTRATOR, who has full read and write permissions. This is the level of the root and admin users, as well as any other administrator accounts that one of them creates. INSTALLER, who has permissions identical to those of ADMINISTRATOR except that the installer cannot add or delete users or change the password of any other user. TECHNICIAN, who has permissions to modify basic radio parameters and view informational web pages GUEST, who has no write permissions and only a limited view of General Status tab Admin, Installer and Tech accounts can be configured as READ-ONLY. This will allow the account to only see the items. See Managing module access by passwords for detailed information on account permissions. Page 1-20 Chapter 1: Product description System management Remote Authentication Dial-in User Service (RADIUS) The PMP configuration of 450 Platform Family includes support for RADIUS (Remote Authentication Dial In User Service) protocol functionality including:

SM Authentication: Allows only known SMs onto the network (blocking rogue SMs), and can be configured to ensure SMs are connecting to a known network (preventing SMs from connecting to rogue APs). RADIUS authentication is used for SMs, but not used for APs. SM Configuration: Configures authenticated SMs with MIR (Maximum Information Rate), High Priority, and VLAN (Virtual LAN) parameters from the RADIUS server when a SM registers to an AP. User Authentication allows users to configure a separate User authentication server along with the SM authentication server. If firmware is upgraded while using this functionality and no User authentication servers are configured, then AP continues to use the SM authentication server for User authentication SM Accounting provides support for RADIUS accounting messages for usage-based billing. This accounting includes indications for subscriber session establishment, subscriber session disconnection, and bandwidth usage per session for each SM that connects to the AP. Centralized AP and SM user name and password management: Allows AP and SM usernames and access levels (Administrator, Installer, Technician and Read-Only) to be centrally administered in the RADIUS server instead of on each radio and tracks access events

(logon/logoff) for each username on the RADIUS server. This accounting does not track and report specific configuration actions performed on radios or pull statistics such as bit counts from the radios. Such functions require an Element Management System (EMS) such as Cambium Wireless Manager. This accounting is not the ability to perform accounting functions on the subscriber/end user/customer account. Framed-IP-Address: Operators may use a RADIUS server to assign management IP addressing to SM modules. SNMP The management agent supports fault and performance management by means of an SNMP interface. The management agent is compatible with SNMP v2c and SNMP v3 using Management Information Base (MIB) files which are available for download from the Cambium Networks Support website:

https://support.cambiumnetworks.com/files/ptp450 https://support.cambiumnetworks.com/files/pmp450 Network Time Protocol (NTP) The clock supplies accurate date and time information to the system. It can be set to run with or without a connection to a network time server (NTP). It can be configured to display local time by setting the time zone and daylight saving in the Time web page. Page 1-21 Chapter 1: Product description System management If an NTP server connection is available, the clock can be set to synchronize with the server time at regular intervals. The 450 Platform Family radios may receive NTP data from a CMM4 module or an NTP server configured in the systems management network. The Time Zone option is configurable on the APs/BHMs Time Configuration page, and may be used to offset the received NTP time to match the operators local time zone. When set on the AP/BHM, the offset is set for the entire sector (AP/BHSs is notified of the current Time Zone upon initial registration). If a Time Zone change is applied, the AP/BHSs are notified of the change in a best effort fashion, meaning some AP/BHSs may not pick up the change until the next re-

registration. Time Zone changes are noted in the Event Log. An AP/BHM which is receiving NTP date and time information from an NTP server or from a GPS synchronization source may be used as an NTP server. Any client which has IP connectivity to the BHM may request NTP date and time information from the AP/BHM. No additional configuration

(other than the AP/BHM receiving valid NTP data) is required to use the AP/BHM as an NTP server. Wireless Manager (WM) Cambium Networks Wireless Manager 4.0 is recommended for managing 450 Platform Family networks. You can achieve better uptime through better visibility of your network with the Cambium Wireless Manager. This network management software tool offers breakthrough map-

based visualization capabilities using embedded Google maps, and combined with advanced configuration, provisioning, alerting and reporting features you can control your entire outdoor wireless network including Point-to-Multipoint and Point-to-Point solutions as well as other SNMP enabled devices. With its powerful user interface you can not only be able to control your network's access, distribution and backhaul layers, but can also have visibility to WLAN sites and be able to quickly launch indoor network management systems. Some key features of Wireless Manager are:

Template-Based Configuration: With Wireless Manager's user-defined templates you can accelerate the process for the configuration of the devices you add to your network resulting in quicker and easier deployments. The template-based functionality provides an automated way to configure large numbers of network devices with just a few mouse clicks, and can be scheduled to occur at any time via Wireless Manager's Task Scheduler. Ultralight Thin Client: With the growing mobile workforce it is important to have access to the status of your network at any time. With Wireless Manager you can view the status and performance of your entire wireless network via a compact web interface accessible by your smart phone. Map-Based Visualization: Wireless Manager overlays sophisticated real-time information about your network elements onto building layouts and dynamic Google maps. Visuals can be scaled to view an entire city or building or a specific area, floor or link. High Availability Architecture Support: Wireless Manager offers a high availability option, providing a highly reliable and redundant network management solution that ensures you always have management access to your network. High Scalability: The enhanced Wireless Manager offers you server scalability with support for up to 10,000 nodes as well as support for distributed server architecture. Page 1-22 Chapter 1: Product description System management Cambiums Wireless Manager 4.0 available for download at:

http://www.cambiumnetworks.com/support/management-tools/wireless-manager/

Canopy Network Updater Tool (CNUT) CNUT (Canopy Network Updater Tool) is the stand-alone software update tool for 450 Platform Family ODUs. The CNUT 4.10.4 or greater should be used for 450 Platform Family ODUs. The Canopy Network Updater Tool has the following features:

Automatically discovers all network elements HTTP and HTTPS Executes UDP command that initiates and terminates the Auto-update mode within APs/BHMs. This command is both secure and convenient:

o For security, the AP/BHM accepts this command from only the IP address that specified in the Configuration page of ODU. o For convenience, Network Updater automatically sets this Configuration parameter in the AP/BHM to the IP address of the Network Updater server when the server performs any of the update commands. Allows you to choose among updating:

o Entire network. o Only elements that you select. o Only network branches that you select. Provides a Script Engine that you can use with any script which:

o The user can define. o Cambium supplies. CNUT is available at:

http://www.cambiumnetworks.com/support/management-tools/cnut/

cnMaestro cnMaestro is a cloud-based or on-premises platform specialized for secure, end-to-end network lifecycle management: inventory management, device onboarding, daily operations, and maintenance. The cnMaestro wireless network manager simplifies device management by offering full network visibility. Network operators can have a real-time view of their complete end-to-end network and perform a full suite of wireless network management functions to optimize system availability, maximize throughput, and meet emerging needs of business and residential customers. In addition, the cnMaestro wireless network manager collects and displays compliance with service level agreements. To learn about cnMaestro, please visit http://www.cambiumnetworks.com/products/software-

tools/cnmaestro/

See Configuring cnMaestroTM Connectivity on 7-211 for details. Page 1-23 Chapter 1: Product description System management Radio recovery mode The 450 Platform Family recovery mode provides a means to recover from serious configuration errors including lost or forgotten passwords and unknown IP addresses. The recovery procedure for 450i/450m series and 450 series ODUs differ due to difference in hardwares. This procedure for 450i/450m Series is known as Radio Recovery Console and for 450 Series is known as Default mode (or Default/Override Plug). Radio Recovery Console 450i and 450m Series The Radio Recovery Console mode supports:

Restoring factory default IP address 169.254.1.1 and password Boot with factory default Canopy system software settings Load previously installed SW images See Radio Recovery Console PMP/PTP 450i and PMP 450m on page 9-74. Default Mode (or Default Plug) 450 Series A default plug is available to provide access to a module whose password and/or IP address have been forgotten. This plug allows the 450 Series ODUs to be accessed using IP address 169.254.1.1 and no password. During the override session, you can assign any new IP address and set either or both user passwords (display-only and/or full access) as well as make other parameter changes. See Default Mode (or Default/Override Plug) - PMP/PTP 450 on page 9-76. Page 1-24 Chapter 2: System hardware This chapter describes the hardware components of a 450 Platform link. The following topics are described in this chapter:

System Components on page 2-2 describes system components of PTP and PMP including its accessories Error! Reference source not found. on page Error! Bookmark not defined. describes various cable and lightning protection Antennas and antenna cabling on page 2-40 describes supported antennas and its accessories GPS synchronization on page 2-42 describes UGPS and CMM4. Ordering the components on page 2-58 specifies Cambium part numbers for 450 Platform Family components Page 2-1 Chapter 2: System hardware System Components System Components Point-to-Multipoint (PMP) The PMP radio is a transceiver device. It is a connectorized or radiated outdoor unit containing all the radio, networking, and surge suppression electronics. It can be purchased as:

Access Point Module (AP) Subscriber Module (SM) PMP 450 Platform Family Integrated or Connectorized ODU The PMP 450i Series and PMP 450 Series ODUs are supplied in Integrated or Connectorized configurations. The PMP 450m Series AP is supplied in Integrated configuration only. See Table 2 PMP 450m Series hardware configurations on page 1-3 See Table 4 PMP/PTP 450i Series hardware configurations on page 1-6 See Table 6 PMP/PTP 450 Series hardware configurations on page 1-9 Product variants Table 10 PMP 450m Series variants Variant Region Antenna Frequency Channel Range Bandwidth Max EIRP FCC RoW EU DES only IC 5 GHz PMP 450m AP 90 integrated sector array, 14x14 MIMO system, 5150 5925 MHz 20 MHz 38 dBm Page 2-2 Chapter 2: System hardware System Components Table 11 PMP 450i Series variants Variant Region Antenna Frequency Channel Range Bandwidth Max Tx Power 900 MHz PMP 450i AP FCC Connectorized 902 - 928 MHz 5, 7, 10, 20 MHz 25 dBm 5 GHz PMP 450i AP 5 GHz PMP 450i SM FCC RoW Canada RoW DES FCC RoW Canada RoW DES 4900 5925 5, 10, 15, 20, 30 MHz MHz 27 dBm Connectorized Integrated 16 dBi 90 degree Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi 4900 5925 5, 10, 15, 20, 30 Connectorized MHz MHz 27 dBm Integrated 23 dBi Connectorized Integrated 23 dBi Note The Transmit power is limited based on regional setting. Page 2-3 Chapter 2: System hardware System Components Table 12 PMP 450 Series variants Variant Region Antenna Frequency Channel Range Bandwidth Max Tx Power 900 MHz PMP 450 SM FCC Connectorized 902 - 928 MHz 5, 7, 10, 20 MHz 25 dBm 2.4 GHz PMP 450 AP FCC ISM Connectorized 2400 2483.5 5, 10, 15, 20, 30 Integrated 18 dBi MHz MHz 2.4 GHz PMP 450 SM FCC ISM Connectorized 2400 2483.5 5, 10, 15, 20, 30 Integrated 7 dBi MHz MHz 3.5 GHz PMP 450 AP FCC ISM Connectorized 3300 3600 5, 7, 10, 15, 20, Integrated 16 dBi MHz 30 MHz 22 dBm 22 dBm 25 dBm 3.5 GHz PMP 450 SM Connectorized FCC ISM Integrated 8 dBi 3300 3600 5, 7, 10, 15, 20, MHz 30 MHz 25 dBm 3.65 GHz PMP 450 AP FCC ISM Integrated 19 dBi Connectorized 3500 3850 5, 7, 10, 15, 20, Integrated 16 dBi MHz 30 MHz Connectorized 25 dBm 3.65 GHz PMP 450 SM FCC ISM Integrated 8 dBi 3500 3850 5, 7, 10, 15, 20, MHz 30 MHz 25 dBm 5.4/5.8 GHz PMP 450 AP FCC RoW Canada RoW DES Integrated 19 dBi Connectorized Integrated 17 dBi Connectorized Integrated 17 dBi 5470 5875 15 and 30 MHz 10, 20 MHz (5, Connectorized MHz not available in DFS regions) 22 dBm Integrated 17 dBi Connectorized Integrated 23 dBi 5.4/5.8 GHz PMP 450 SM FCC, ROW, Canada, RoW DES Connectorized 10, 20 MHz (5, 5470 5875 15 and 30 MHz Integrated 9 dBi MHz Integrated 25 dBi not available in DFS regions) 22 dBm Page 2-4 Chapter 2: System hardware System Components Note The Transmit power is limited based on regional setting. Backhaul (PTP) The Backhaul radio is a transceiver device. It is a connectorized or integrated outdoor unit containing all the radio, networking, and surge suppression electronics. It can be configured as:

Backhaul Master (BHM) Backhaul Slave (BHS) PTP 450 Platform Family Integrated or Connectorized ODU See Table 4 PMP/PTP 450i Series hardware configurations on page 1-6 See Table 6 PMP/PTP 450 Series hardware configurations on page 1-9 Product variants Table 13 PTP 450i Series variants Variant Region Antenna Frequency Channel Max Tx Notes Range Bandwid Power th FCC RoW Canada RoW DES Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi 4900 5925 MHz 5, 10, 15, 20, 30 MHz Transmit power 27 dBm limited based on regional setting FCC Connectorized 902 - 928 MHz 5, 7, 10, 20 MHz 25 dBm 5 GHz PTP 450i 900 MHz PTP 450i Page 2-5 Chapter 2: System hardware System Components Table 14 PTP 450 Series variants Variant Region Antenna Frequency Channel Max Tx Range Bandwidth Power 3.5 GHz PTP 450 BH Connectorized ROW Integrated 16 dBi 3300 3600 5, 7, 10, 15, MHz 20, 30 MHz 25 dBm 3.65 GHz PTP 450 BH 5.4/5.8 GHZ PTP 450 BH 5 GHz PTP 450 BH Integrated 19 dBi Connectorized ROW Integrated 16 dBi 3500 3850 5, 7, 10, 15, MHz 20, 30 MHz 25 dBm FCC FCC RoW Canada RoW DES Integrated 19 dBi Connectorized Integrated 17 dBi Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi Connectorized Integrated 23 dBi 5470 5875 5, 10, 20 MHz MHz 22 dBm 4900 5875 5, 10, 15, 20, MHz 30 MHz 22 dBm Note The Transmit power is limited based on regional setting. Page 2-6 Chapter 2: System hardware System Components 450 Platform Family interfaces PMP 450m Series interfaces AP The 450m Series AP interfaces is illustrated below. Figure 5 PMP 450m Series interfaces Carabiner clip Ground Lugs SFP AUX PSU/Ethernet Table 15 PMP 450m Series AP interface descriptions and cabling Interface Function Cabling PSU/Ethernet Power-over-Ethernet, Ethernet communications (management and data), RJ45 Cable CMM5 sync-over-power synchronization See Table 85 on page 5-12 input Aux/Sync GPS synchronization input and output, UGPS power output Audio tones RJ 45 Cable See Table 86 on page 5-12 SFP Data Data Ground Lugs For grounding the unit 10 AWG copper wire Page 2-7 Chapter 2: System hardware System Components Note For PMP 450m AP, the Sync-Over-Power is supported with CMM5 only. For PMP 450m AP, the Sync-Over-Power will not work with CMM4 like PMP 450/450i Series. Note SFP kits (part numbers C000065L008A and C000065L009A) is are required for SFP port connectivity. SFP port is not supported in current system release of 15.0/15.0.0.1. PMP/PTP 450i Series interfaces AP/SM/BH The AP/SM/BH interfaces are illustrated below. Figure 5 PMP/PTP 450i interfaces Carabiner clip Ground Lug RF port A Aux ENET RF port B Gland Page 2-8 Chapter 2: System hardware System Components Table 16 PMP/PTP 450i Series - AP/SM/BH interface descriptions and cabling Interface Function Cabling PSU/Ethernet Power-over-Ethernet, Ethernet communications (management and data), RJ45 Cable CMM sync-over-power synchronization See Table 85 on page 5-12 input Aux/Sync GPS synchronization input and output, UGPS power output Audio tones Data RJ 45 Cable See Table 86 on page 5-12 RF Port A RF Port B Vertical RF connection to antenna 50 ohm RF cable, N-type Horizontal RF connection to antenna 50 ohm RF cable, N-type Ground Lugs For grounding the unit 10 AWG copper wire Note If the Aux port will be used, a second Ethernet Gland will need to be ordered (Part Number: N000065L033A). PMP/PTP 450 Series interfaces - AP The PMP 450 Series - AP interfaces are illustrated below. Figure 3 PMP/PTP 450 Series - AP interfaces RF Port A Sync/Default Ethernet RF port B Page 2-9 Chapter 2: System hardware System Components Table 17 PMP/PTP 450 Series - AP interface descriptions and cabling 2.4 GHz and 5 GHz Interface PSU/Ethernet Sync/Default Function Cabling Power-over-Ethernet, Ethernet communications (management and RJ45 Cable data) GPS synchronization signaling, provides power to UGPS module. Default plug port. RJ11 cable, default plug. 2.4 GHz

-45 degree RF connection to AP RF Port A antenna 5 GHz Vertical RF connection to AP antenna RF Port B 2.4 GHz +45 degree RF connection to AP antenna 5 GHz Horizontal RF connection to AP antenna 50 ohm RF cable, N-type 50 ohm RF cable, N-type Ground Lugs For grounding the unit 10 AWG copper wire PMP/PTP 450 Series interfaces SM/BH The PMP 450 Series SM/BH interfaces are illustrated below. Figure 4 PMP/PTP 450 Series SM/BH interfaces Ethernet Sync/Default Page 2-10 Chapter 2: System hardware System Components Figure 5 PMP/PTP 450 Series SM/BH Connectorized interfaces External antenna cable path A

(labeled A) External antenna cable path B

(labeled B) Ground (connectorized models) Note As per UL guidelines, the Ground Lug on the radiated SM is not required. Page 2-11 Chapter 2: System hardware System Components Figure 6 PMP 450d Series - SM Integrated Dish Figure 7 PMP 450 Series SM 3 GHz Integrated Figure 8 PTP 450 Series BHM/BHS Page 2-12 Chapter 2: System hardware System Components ATEX/HAZLOC variants PTP/PMP 450i series products are available in ATEX/Hazloc variants for operation in locations where explosive gas hazards exist, as defined by Hazloc (USA) and ATEX (Europe). ATEX/HAZLOC variants are similar to the standard product except that:

ODUs are supplied with the Full capacity license The frequency range is restricted to 4940 MHz to 5850 MHz The maximum EIRP generated by ODU is restricted to comply with the ATEX and HAZLOC standards In order to meet specific radio regulations in the USA, Canada and the EU, Cambium supplies products approved for USA, Canada, EU and the rest of the world under different models and part numbers. These models and part numbers are shown in Table 18 below. Table 18 PMP/PTP 450i ATEX/HAZLOC ODU models/part numbers ODU model /

Description part number ODU model 5085CHH 450i Connectorized ATEX/HAZLOC 5085HH 450i Integrated 90 Deg Sector ATEX/HAZLOC 5095HH 450i Integrated High Gain Directional ATEX/HAZLOC Part Number C050045A009A 5 GHz PMP 450i Conn Access Point (ROW), ATEX/HAZLOC C050045A010A 5 GHz PMP 450i Conn Access Point (FCC), ATEX/HAZLOC C050045A011A 5 GHz PMP 450i Conn Access Point (EU), ATEX/HAZLOC C050045A012A 5 GHz PMP 450i Integrated Access Point, 90 degree (ROW), ATEX/HAZLOC C050045A013A 5 GHz PMP 450i Integrated Access Point, 90 degree (FCC), ATEX/HAZLOC C050045A014A 5 GHz PMP 450i Integrated Access Point, 90 degree (EU), ATEX/HAZLOC C050045A017A 5 GHz PMP 450i Conn Access Point (IC), ATEX/HAZLOC C050045A018A 5 GHz PMP 450i Integrated Access Point, 90 degree (IC), ATEX/HAZLOC C050045A019A 5 GHz PMP 450i Conn Access Point (DES Only), ATEX/HAZLOC C050045A020A 5 GHz PMP 450i Integrated Access Point, 90 degree (DES Only), ATEX/HAZLOC C050045C003A 5 GHz PMP 450i Conn Subscriber Module, ATEX/HAZLOC C050045C004A 5 GHz PMP 450i Integrated High Gain Antenna, ATEX/HAZLOC C050045B009A 5 GHz PTP 450i END, Connectorized (ROW), ATEX/HAZLOC Page 2-13 Chapter 2: System hardware System Components C050045B010A 5 GHz PTP 450i END, Integrated High Gain Antenna (ROW), ATEX/HAZLOC C050045B011A 5 GHz PTP 450i END, Connectorized (FCC), ATEX/HAZLOC C050045B012A 5 GHz PTP 450i END, Integrated High Gain Antenna (FCC), ATEX/HAZLOC C050045B013A 5 GHz PTP 450i END, Connectorized (EU), ATEX/HAZLOC C050045B014A 5 GHz PTP 450i END, Integrated High Gain Antenna (EU), ATEX/HAZLOC C050045B017A 5 GHz PTP 450i END, Connectorized (IC), ATEX/HAZLOC C050045B018A 5 GHz PTP 450i END, Integrated High Gain Antenna (IC), ATEX/HAZLOC C050045B019A 5 GHz PTP 450i END, Connectorized (DES Only), ATEX/HAZLOC C050045B020A 5 GHz PTP 450i END, Integrated High Gain Antenna (DES Only), ATEX/HAZLOC Page 2-14 Chapter 2: System hardware System Components Diagnostic LEDs The diagnostic LEDs of 450 Platform Family ODUs are as shown below. Note The LED color helps distinguish the position of LED. The LED color does not indicate any status. AP/BHM LEDs The diagnostic LEDs report the information about the status of the AP/BHM. Figure 9 AP/BHM diagnostic LEDs, viewed from unit front ODU LED Display LED Labels PMP 450m Series - AP LNK/5 ACT/4 GPS/3 SES/2 SYN/1 PWR PMP/PTP 450i Series - AP/BHM LNK/5 ACT/4 GPS/3 SES/2 SYN/1 PWR PMP/PTP 450 Series - AP/BHM LNK/5 ACT/4 GPS/3 SES/2 SYN/1 PWR Page 2-15 Chapter 2: System hardware System Components Table 19 AP/BHM LED descriptions LED Color when active Status information Notes provided PWR Red DC power SYN/1 Yellow Presence of sync SES/2 Green Unused Always lit after 10-20 seconds of power on.

-

-

GPS/3 Red Pulse of sync pulse from a GPS source goes along Lit when the AP/BHM is getting a sync with SYN/1 Presence of data activity on the Ethernet link Flashes during data transfer. Frequency of flash is not a diagnostic indication. Continuously lit when link is present. Ethernet link 10Base-T : Red Ethernet link 100Base-T : Green 1000Base-T : Orange Continuously lit when link is present. ACT/4 Yellow For 450i and 450m Series LNK/5 Red/ Green/Orange

(bi-colored for 10/100/1000) For 450 Series Green SM/BHS LEDs The SM/BHS LEDs provide different status of radio based on the operating modes. A SM/BHS in operating mode registers and passes traffic normally. A SM/BHS in aiming mode does not register or pass the traffic, but displays (via LED panel) the strength of received radio signals

(based on radio channel selected via Tools -> Alignment). Page 2-16 Chapter 2: System hardware System Components Figure 10 AP/BH diagnostic LEDs, viewed from unit front ODU LED Display LED Labels PMP/PTP 450i Series - SM/BHS LNK/5 ACT/4 GPS/3 SES/2 SYN/1 PWR PMP/PTP 450 Series - SM/BHS LNK/5 ACT/4 GPS/3 SES/2 SYN/1 PWR Table 20 SM/BHS LED descriptions Status information provided LED Color when SM / BHS in SM / BHS in Notes active Operating Mode Aiming Mode PWR Red DC power SYN/1 Yellow Presence of sync SES/2 Green Session Indicator GPS/3 Red Unused ACT/4 Yellow Presence of data activity on the Ethernet link For 450i and 450m Series Red/ Green/

Orange

(bi-colored for 10/100/1000) For 450 Series Green Ethernet link Ethernet link LNK/5 These five LEDs act as a bar graph to indicate the relative quality of alignment. As power level improves during alignment, more of these LEDs are lit. Always lit after 10-20 seconds of power on. Lit when SM/BHS is in sync with an AP/BHM. Lit when SM/BHS is in session. On - high interference. Blinking - medium interference. Off - low interference. Flashes during data transfer. Frequency of flash is not a diagnostic indication. Continuously lit when link is present. 10Base-T : Red 100Base-T : Green 1000Base-T : Orange Continuously lit when link is present. Page 2-17 Chapter 2: System hardware System Components Operating Mode Scanning: If the SM/BHS is not registered to AP/BHM, then these three LEDs cycle on and off from left to right (SYN/1, SES/2 and GPS/3). Ethernet Link: The LNK/5 LED lit continuously when link is present. Data Transfer: The ACT/4 LED lit on the presence of data activity on the Ethernet link. Aiming Mode The 5 LEDs (SYN/1, SES/2, GPS/3, ACT/4 and LNK/5) are turned into a 5-position bar graph. The more LEDs that are lit, the better the received power the module is seeing. The colors of the LEDS have no particular meaning other than to assist is distinguishing one position from the next. Power supply options The 450 Platform Family ODUs are powered over its Main Ethernet cable using Power Over Ethernet (POE). The power injector is connected to the ODU and network terminating equipment using Cat5e cable with RJ45 connectors. Power supply PMP 450m Series The PMP 450m Series - AP supports powering from AC+DC Enhanced Power Injector (see AC+DC Enhanced Power Injector on page 2-21) Table 21 PSU part numbers for PMP 450m AP Cambium description Cambium part number AC+DC Enhanced Power Injector C000065L002B Power supply PMP/PTP 450i Series The PMP/PTP 450i Series supports powering from the following powering sources:

Power Supply, 60 W, 56 V with Gbps support AC+DC Enhanced Power Injector Power over Ethernet midspan, 60 W, -48 VDC Input CMM4 with external 56 V power supply and CMM4 to 450i Series ODU cable (Dongle) IEEE802.3at power injector Page 2-18 Chapter 2: System hardware System Components Note The 900 MHz SM is based off of the 450 Series , please see Power supply PMP/PTP 450 on page 2-23. Warning Always use an appropriately rated and approved AC supply cord-set in accordance with the regulations of the country of use. Warning The PMP 450 Ruggedized High Gain Integrated Subscriber Module (Cambium part numbers C035045C014A and C036045C014A), while encapsulated in a 450i-

type enclosure, contains 450 circuitry which must be powered via 30 VDC. Powering these SMs with a 56 VDC will damage the device. Please refer to Cabling Ethernet standards and cable lengths on Page 2-29 for details on maximum cable lengths between power injector and PMP/PTP 450i. Table 22 PSU part numbers for PMP/PTP 450i Series Cambium description Cambium part number Power supply, 60 W, 56 V with Gbps support AC+DC Enhanced Power Injector Line Cord, Fig 8 US Line Cord, Fig 8 UK Line Cord, Fig 8 EU Power over Ethernet midspan, 60 W, -48 VDC Input Power supply, 30 W, 56 V Gbps support N000065L001B C000065L002C N000065L003A N000065L004A N000065L005A N000000L036A N000000L034A Page 2-19 Chapter 2: System hardware System Components The AC Power Injector interfaces are shown in Figure 11 and described in Table 23. Figure 11 AC Power Injector interfaces Table 23 AC Power Injector interface functions Interface Function AC power in AC power input (main supply) ODU LAN RJ45 socket for connecting Cat5e cable to ODU RJ45 socket for connecting Cat5e cable to network Power (green) LED Power supply detection Page 2-20 Chapter 2: System hardware System Components The AC+DC Enhanced Power Injector interfaces are shown in Figure 12 and described in Table 24. Figure 12 AC+DC Enhanced Power Injector interfaces Page 2-21 DC Out and DC In portsLEDsAC Power InputODU PortLAN Port Chapter 2: System hardware System Components Table 24 AC+DC Enhanced Power Injector interface functions Interface Function 100-240V 47-63Hz 1.7A AC power input (main supply) DC In DC Out ODU LAN Alternative DC power supply input DC power output to a second PSU (for power supply redundancy) or to a NIDU RJ45 socket for connecting Cat5e cable to ODU RJ45 socket for connecting Cat5e cable to network Power - AC (green) LED Indicates power is applied at the AC power input Power - DC (green) LED Indicates power is applied at the DC In port Ethernet (yellow) LED Detects Ethernet traffic and it is used with PTP650 and PTP700 families only. It does not operate with the 450 platform products. Note The earlier power injector models only had a single power LED that combined the AC+DC indications. Page 2-22 Chapter 2: System hardware System Components The DC Power Injector interfaces are shown in Figure 13 and described in Table 25. Figure 13 -48 V DC Power Injector interfaces Table 25 -48V DC Power Injector interfaces Interface DC input Function 36 to 60V, 2A RJ 45 Sockets Two (Data In and Data & Power Out) LEDs Two (AC and Port) Power supply PMP/PTP 450 Series The PMP/PTP 450 Series support powering from the following powering sources:

Gigabit Enet Capable Power Supply 30 VDC, 15W CMM4 with external 29 V power supply Warning The PMP 450 Ruggedized High Gain Integrated Subscriber Module (Cambium part numbers C035045C014A and C036045C014A), while encapsulated in a 450i-type enclosure, contains 450 circuitry which must be powered via 30VDC. Powering these SMs with a 56 VDC will damage the device. Page 2-23 Chapter 2: System hardware System Components Table 26 PSU part numbers for PMP/PTP 450 Series Cambium description Cambium part number Gigabit Enet Capable Power Supply - 30VDC, 15W Cable, UL Power Supply Cord Set, US Cable, UL Power Supply Cord Set, EU Cable, UL Power Supply Cord Set, UK Cable, UL Power Supply Cord Set, Brazil N000900L001A N000900L007A N000900L008A N000900L009A N000900L010A The Gigabit Enet Capable power supply interfaces are described in Table 27. This power supply requires procurement of an AC line cord that connects the outlet of the same (using IEC-60320 Type 5 connector). A list of available power supply cord options from Cambium Networks are given in Table 26. Table 27 Gigabit Enet Capable power supply Interface AC Input Function 90-264 VAC, 0.5A rms @120VAC/ 0.25A rms @240VAC, 47 to 63 Hz DC Output 30.0 Vdc +/-5%, 15W, 500 mA max RJ 45 Sockets Two (Data In and Data & Power Out) LEDs Green, :LED Intensity determined by Level 5 efficiency Figure 14 Gigabit Enet Capable power supply Page 2-24 Chapter 2: System hardware System Components ODU mounting brackets & accessories The list of supported brackets is provided in Table 28. The "Tilt bracket assembly" is the recommended bracket for the AP, SM or BH integrated units. The "Mounting Bracket (Connectorized)" can be used where a low profile and ease of assembly of Connectorized AP, SM or BH is required. The "Mounting Bracket (Integrated)" provide a wider range of adjustment for AP, SM and BH integrated devices. Table 28 Accessories part numbers Cambium description Mounting brackets Tilt Bracket Assembly Mounting Bracket (Integrated) Mounting Bracket (Connectorized) Miscellaneous Ethernet cable adapter for CMM4 (Dongle) RJ-45 Gland Spare PG16 style (QTY 10) Blanking Plug Pack (Qty 10) Lightning protection Cambium part number N000045L002A N000065L031A N000065L032A N000045L001A N000065L033A N000065L036A The 450 Platform Family supports the lightning protection units listed in Table 29. The LPU offers the highest level of protection and is the recommended device. Where low cost deployment is essential, for example for SM in residential application, the Gigabit Surge Suppressor may be used instead. Table 29 Lightning protection part numbers Cambium description 450 Series Surge Suppressor (30 VDC) 450i and 450m Series LPU and Grounding Kit (1 kit per ODU) Gigabit Surge Suppressor (56 VDC) Page 2-25 Cambium part number 600SSH C000065L007A C000000L033A Chapter 2: System hardware ODU interfaces ODU interfaces PMP 450m Series AP These interfaces are described in Table 31. Figure 15 PMP 450m Series - AP rear interfaces Ground Lug LED SFP Aux PSU (Main) Ground Lug Table 30 PMP 450m Series AP rear interfaces Port name Connector Interface Description PSU (Main) RJ45 PoE input Power over Ethernet (PoE). 10/100/1000BASE-T Data Ethernet Aux RJ45 10/100/100BASE-T Ethernet Data PoE output Standard IEEE802.3at PoE. Sync input/output Connection and powering of UGPS Sync input SFP RJ45 10/100/100BASE-T Ethernet Data Ground Lugs 10 AWG copper wire For grounding the unit Page 2-26 Chapter 2: System hardware ODU interfaces PMP/PTP 450i The Ethernet and Sync/AUX ports are on the rear of the integrated and connectorized ODUs

(Figure 16). These interfaces are described in Table 31. Figure 16 PMP/PTP 450i Series - ODU rear interfaces LED Ground Lug Ground Lug Aux Main RF port B RF port A Table 31 PMP/PTP 450i Series ODU rear interfaces Port name Connector Interface Description Main PSU RJ45 PoE input Power over Ethernet (PoE). 10/100/1000BASE-T Data Ethernet Sync/AUX RJ45 10/100/100BASE-T Ethernet Data (see Note below) PoE output Standard IEEE802.3at PoE. Sync input/output Connection and powering of UGPS Sync input The front of the connectorized ODU (Figure 17 PMP/PTP 450i Series Connectorized ODU antenna interfaces) provides N type female connectors for RF cable interfaces to antennas with ports A and B for vertical and horizontal polarization respectively. Page 2-27 Chapter 2: System hardware ODU interfaces Figure 17 PMP/PTP 450i Series Connectorized ODU antenna interfaces Page 2-28 Chapter 2: System hardware Cabling Cabling Ethernet standards and cable lengths All configurations require a copper Ethernet connection from the ODU (Main PSU port) to the Power supply. Table 32 specifies, for each type of PSU and configuration, the maximum permitted PSU drop cable length. Table 32 PSU drop cable length restrictions System configuration Maximum cable length (m/ft) Power supply PoE powered device From power supply From ODU to PoE on AUX/SYNC port to ODU device on AUX/SYNC Power supply (30W) None 100 m IEEE 802.3at Type 2 Not supported port N/A AC Power Injector (60W) None 100 m N/A IEEE 802.3at Type 2 100 m in total AC+DC enhanced Power Injector None 100 m N/A IEEE 802.3at Type 2 100 m in total

-48 V DC power injector None 100 m N/A IEEE 802.3at Type 2 100 m in total CMM4 with 56 V supply None 100 m N/A IEEE 802.3at Type 2 Not supported IEEE802.3at compliant supply None 100 m N/A IEEE 802.3at Type 2 Not supported Note The Ethernet connectivity for CMM4 requires the part Ethernet cable adapter for CMM4 N000045L001A. Page 2-29 Chapter 2: System hardware Cabling Page 2-30 Chapter 2: System hardware Cabling Outdoor copper Cat5e Ethernet cable Outdoor Cat5e cable is used for all connections that terminate outside the building. For example, connections between the ODU, surge suppressors (if installed), UGPS receivers (if installed) and the power supply injector. This is known as a drop cable (Figure 18). The following practices are essential to the reliability and longevity of cabled connections:

Use only shielded cables and connectors to resist interference and corrosion. For vertical runs, provide cable support and strain relief. Include a 2 ft (0.6 m) service loop on each end of the cable to allow for thermal expansion and contraction and to facilitate terminating the cable again when needed. Include a drip loop to shed water so that most of the water does not reach the connector at the device. Properly crimp all connectors. Use dielectric grease on all connectors to resist corrosion. Order Superior Essex type BBDGe cable from Cambium Networks (Table 33). Other lengths of this cable are available from Superior Essex. Figure 18 Outdoor drop cable Table 33 Drop cable part numbers Cambium description Cambium part number 1000 ft Reel Outdoor Copper Clad CAT5E 328 ft (100 m) Reel Outdoor Copper Clad CAT5E WB3175 WB3176 Page 2-31 Chapter 2: System hardware Cabling SFP module kits SFP module kits allow connection of a PMP 450 Series ODU to a network over an Optical Gigabit Ethernet interface (1000BASE-LX or 1000BASE-SX) full-duplex mode. Note PMP 450m supports Fiber SFPs from system release 15.0.3. Order SFP module kits from Cambium Networks (Table 34). Table 34 SFP module kit part numbers Cambium description Cambium part number Single Mode Optical SFP Interface per ODU Multi-mode Optical SFP Interface per ODU C000065L008 C000065L009 To compare the capabilities of the two optical SFP modules, refer to Table 35 and Table 36. Table 35 Single Mode Optical SFP Interface per ODU (part number C000065L008) Mode Bandwidth at Maximum Insertion loss Core/

cladding

(microns) 62.5/125 Multi 50/125 50/125 Multi Multi 10/125 Single 1310 nm

(MHz/km) 500 400 500 N/A length of optical

(dB) interface 550 m (1800 ft) 550 m (1800 ft) 550 m (1800 ft) 5000 m (16400 ft) 1.67 0.07 1.19 0.16 Table 36 Multi-mode Optical SFP Interface per ODU (part number C000065L009) Core/

cladding

(microns) Mode Bandwidth at Maximum Insertion loss 850 nm (MHz/km) length of optical

(dB) interface 220 m (720 ft) 275 m (900 ft) 500 m (1640 ft) 550 m (1800 ft) 2.38 2.6 3.37 3.56 62.5/125 Multi 62.5/125 Multi 50/125 50/125 Multi Multi 160 200 400 500 The upgrade kits contain the following components:

Optical SFP transceiver module (Figure 19) Page 2-32 Chapter 2: System hardware Cabling Long EMC strain relief cable gland (Figure 20) The Ethernet SFP Module Installation Guide License key instructions and an entitlement key Figure 19 Optical SFP transceiver module Figure 20 Long cable gland Page 2-33 Chapter 2: System hardware Cabling Main Ethernet port The PoE cable pinout diagram for Main port is given below. Table 37 Main port PoE cable pinout RJ45 pin Interface Ethernet description 1 2 3 6 4 5 7 8 1000 BaseT Ethernet with PoE In

+TxRx0 TxRx0

+TxRx1 TxRx1

+TxRx2 TxRx2

+TxRx3 TxRx3 PoE input description

+Ve or -Ve

+Ve or Ve

+Ve or Ve

+Ve or Ve Note The PoE input on the Main port accepts any polarity. Aux port Table 38 Aux port PoE cable pinout RJ45 pin Interface Signal description PoE output description 1 2 3 6 4 5 7 8 100 BaseT Ethernet with PoE Out (see note below)

+TxRx0 TxRx0

+TxRx1 TxRx1 GPS power out, Alignment tone out, GPS data out GPS and alignment tone GPS data in GPS 0v GPS Sync in

-Ve

+Ve N/A Page 2-34 Chapter 2: System hardware Cabling Note PMP 450m Series - AP Aux port supports only alignment and sync functionalities in current 15.0/15.0.0.1 release. Note If the Aux port will be used, a second Ethernet gland will need to be ordered (Part Number: N000065L033A). Aux port to alignment tone headset wiring A standard 32 ohms stereo headset can be connected to the AUX port to use the audio alignment tool. The diagrams of the adapters for RJ45 and RJ12 are is provided in Figure 21 and Figure 22 respectively. The recommended values for both resistors are 220 ohm, 0.25W. Different resistor values can be used to optimize the level of the audio signal depending on the headset characteristics and the level of ambient noise. Figure 21 Alignment Tone Cable

#8 Pin 7 Pin 4 Resistors 220 220 Left / tip Right / ring Sleeve /Common Table 39 Aux port PoE cable pinout RJ45 pin

(AUX port) 4 7 Signal description Serial component Jack socket

(to jack plug of headset) Alignment tone out 220 ohms resistor 220 ohm resistor GPS 0v None Ring Tip Sleeve Page 2-35 Chapter 2: System hardware Cabling Figure 22 RJ12 Alignment Tone Cable

#8 Pin 5 Pin 6 Left / tip Right / ring Table 40 RJ12 Aux port PoE cable pinout RJ12 pin (AUX port) Signal description Jack socket

(to jack plug of headset) 5 6 Alignment tone out Alignment tone out Tip Ring Alternatively, a readymade headset adapter can be ordered from Best-Tronics

(http://btpa.com/Cambium-Products/) with the following part number:

Table 41 Alignment tone adapter third party product details Reference Product description BT-1277 BT-0674 Headset alignment cable (RJ-45) for the PMP/PTP 450i Series products Headset alignment cable (RJ-12) for the PMP/PTP 450 Series products. RJ45 connectors and spare glands RJ45 connectors are required for plugging Cat5e cables into ODUs, LPUs, PSUs and other devices. Order RJ45 connectors and crimp tool from Cambium Networks (Table 42Error! Reference source not found.). The ODU is supplied with one environmental sealing gland for the drop cable. This gland is suitable for cable diameters from 5 mm to 9 mm. Page 2-36 Chapter 2: System hardware Cabling Figure 23 Cable gland (part number #N000065L033) Table 42 RJ45 connector and spare gland part numbers Cambium description Cambium part number Tyco/AMP, Mod Plug RJ45, 100 pack Tyco/AMP Crimp Tool WB3177 WB3211 RJ-45 Spare Grounding Gland - PG16 size (Qty. 10) N000065L033 Page 2-37 Chapter 2: System hardware Lightning protection unit (LPU) and grounding kit Lightning protection unit (LPU) and grounding kit 450i and 450m Series LPUs provide transient voltage surge suppression for ODU installations. Each cable requires two LPUs, one near the ODU and the other near the linked device, usually at the building entry point (Table 43). Table 43 LPU and grounding kit contents Lightning protection units (LPUs) ODU to top LPU drop cable (600 mm) LPU grounding point nuts and washers EMC strain relief cable glands U-bolts, nuts and washers for mounting LPUs ODU to top LPU ground cable (M6-M6) Bottom LPU ground cable (M6-M10) ODU to ground cable (M6-M10 Page 2-38 Chapter 2: System hardware Lightning protection unit (LPU) and grounding kit One LPU and grounding kit (Table 43) is required for the PSU drop cable connection to the ODU. If the ODU is to be connected to an auxiliary device, one additional LPU and grounding kit is required for the Aux drop cable. Order the kits from Cambium Networks (Table 44). Table 44 LPU and grounding kit part number Cambium description Cambium part number Aux ports LPU and Grounding Kit (One Kit Per End) C000065L007 Cable grounding kit Copper drop cable shields must be bonded to the grounding system in order to prevent lightning-

strike arcing (resulting in fire risk and damage to equipment). One grounding kit (Figure 24Error! Reference source not found.) is required for each grounding point on the cable. Order cable grounding kits from Cambium Networks (Table 45Error! Reference source not found.). Caution To provide adequate protection, all grounding cables must be a minimum size of 10 mm2 csa (8AWG), preferably 16 mm2 csa (6AWG), or 25 mm2 csa (4AWG). Figure 24 Cable grounding kit Table 45 Cable grounding kit part numbers Cambium description Cambium part number Cable Grounding Kits For 1/4" And 3/8" Cable 01010419001 Page 2-39 Chapter 2: System hardware Antennas and antenna cabling Antennas and antenna cabling Antenna requirements Each connectorized ODU requires one external antenna (normally dual-polar). For connectorized units operating in the USA or Canada 900 MHz, 4.9 GHz, 5.1 GHz, 5.2 GHz, 5.4 GHz or 5.8 GHz bands, choose external antennas which are recommended by Cambium Networks. Do not install any other antennas. Supported external AP antennas The recommended AP external antennas are listed in Table 46. Table 46 List of AP external antennas Cambium description Cambium part number 900 MHz 13 dBi 65 degree Sector Antenna (Dual Slant) N009045D001A 5 GHz Horizontal and Vertical Polarization Antenna for 90 Degree 85009324001 Sector 5 GHz Horizontal and Vertical Polarization Antenna for 60 Degree 85009325001 Sector Note LINKPlanner, Cambium Networks, planning tool, contains an up-to-date, exhaustive list of antennas that can be used with Cambium Products. Supported external BH/SM antenna The recommended PTP 450i Series BH or PMP 450/450i Series SM external antenna is listed in Table 47. Table 47 PTP 450i Series BH or PMP 450/450i Series SM external antenna Cambium description Cambium part number 900 MHz 12 dBi gain directional antenna (Dual Slant) N009045D003A Page 2-40 Chapter 2: System hardware Antennas and antenna cabling RF cable and connectors RF cable of generic type LMR-400 is required for connecting the ODU to the antenna. N type male connectors are required for connecting the RF cables to the connectorized ODU. Two connectors are required per ODU. Use weatherproof connectors, preferably ones that are supplied with adhesive lined heat shrink sleeves that are fitted over the interface between the cable and connector. Order CNT-400 RF cable and N type male connectors from Cambium Networks (Table 48). Table 48 RF cable and connector part numbers Cambium description Cambium part number 50 Ohm Braided Coaxial Cable - 75 meter 50 Ohm Braided Coaxial Cable - 500 meter 30010194001 30010195001 RF Connector, N, Male, Straight for CNT-400 Cable 09010091001 Antenna accessories Connectorized ODUs require the following additional components:

Cable grounding kits: Order one cable grounding kit for each grounding point on the antenna cables. Refer to Lightning protection unit (LPU) and grounding kit on 2-38 Self-amalgamating and PVC tape: Order these items to weatherproof the RF connectors Lightning arrestors: When the connectorized ODU is mounted indoors, lightning arrestors (not LPUs) are required for protecting the antenna RF cables at building entry. One arrestor is required per antenna cable. One example of a compatible lightning arrestor is the Polyphaser LSXL-ME or LSXL (not supplied by Cambium Networks). Page 2-41 Chapter 2: System hardware GPS synchronization GPS synchronization GPS synchronization description Cambium offers GPS synchronization to limit the networks own self-interference. The Cluster Management CMM provides Global Positioning System (GPS) synchronization to the Access Point

(AP) and all associated Subscriber Modules (SM). Network operators have a choice of UGPS and CMM solutions to select the option that works best for the environment. Universal GPS (uGPS) The uGPS provides network synchronization for smaller networks where a CMM may not be cost effective. The uGPS provides synchronization for one or two modules so that even remote areas at the edge of the network can operate with synchronization for improved performance. The uGPS works with all Cambium PMP radios. The uGPS has a small footprint and is easy to deploy. Figure 25 uGPS Note PMP 450/450i/450m Series - APs can power up a uGPS via the Aux/Timing port. Page 2-42 Chapter 2: System hardware GPS synchronization CMM5 The CMM5 (Cluster Management Module) is the latest generation of solutions for the distribution of TDD Sync signals and Power-over-Ethernet (PoE) in the field. The CMM5 is a modular design with individual 4-port power injectors and an optional controller used for remote management. Key features of the CMM5 include:

Support for Gigabit Ethernet (1000BaseT) Modular and scalable from 4 ports to 32 ports Direct +/- 48VDC input (optional AC/DC power supplies are available from Cambium Networks) Uses Cambium Networks uGPS for a synchronization source Dual resilent power inputs Rack mountable Secure remote management when used with the optional CMM5 Controller Module Support for PMP 450m (cnMedusa) Future support for integration into (cnMedusa) for cloud or NOC-based management The CMM5 (Cluster Management Module) is the latest generation of solutions for the distribution of TDD Sync signals and Power-over-Ethernet (PoE) in the field.It consists of four subsystems, described in the following sections:

CMM5 Controller Module CMM5 Injector (29 volt and 56 volt versions) Power supply(s) (240/600 watt) uGPS Cluster Management: Scenario 1 The following is a CMM5 Cluster Management scenario using four PMP 450i Access Points. Table 49 CMM5 Cluster Management Scenario 14 power adapter cable pinout Plug J1 pinScenario Jack J2 Features Four PMP 450i Access Points1 pinEquipment Needed 56 Volt Injector1 Gigabit Ethernet Local Management Interface

+/- 48VDC Input Broad Device Support Rack Mountable 48 VDC Available uGPS2

----------------------------

Page 2-43 Chapter 2: System hardware GPS synchronization No management or resiliance required2 3 4 5 6 7 8 3 4 7 6 5 8 Screen Screen Figure 26 CMM5 Controllerluster Management: Scenario 1 Cluster Management: Scenario 2 The following is a CMM5 Cluster Management scenario using four PMP 450i Access Points and four PMP 450 Access Points. Page 2-44 Chapter 2: System hardware GPS synchronization Table 50 CMM5 Cluster Management Scenario 2 Scenario Equipment Needed Features Four PMP 450i Access Points Four PMP 450 Access Points 56 Volt Injector Gigabit Ethernet 29 Volt Injector 1 CMM5 Controller One uGPS support Local Management Interface

+/- 48VDC Input Broad Device Support Rack Mountable AC only u Two AC-to-48VDC Resilent power environments Power SuppliesGPS sources Management

----------------------------

Secure, Remote required. Resilence required. Management (https) Scalable to 32 devices Page 2-45 Chapter 2: System hardware GPS synchronization Figure 27 Cluster Management: Scenario 2CMM5 Controller CMM5 Controller Module The major features of the CMM5 Controller Module are:

Auto-detect/control up to 8 Power Injectors Monitor SYNC/Power/GPS status Manage (up/down ports) Web (HTTPS) and SNMPv2/v3 management (SNMP on roadmap) 1U/ half-width rack-mount Figure 28 Controller Module Page 2-46 Chapter 2: System hardware GPS synchronization CMM5 Injector Module The CMM5 Injector Module has the following features:

Stand-alone mode or used with controller for mgmt.

+/- 48VDC input with green/amber LEDs for status Injects SYNC pulse from uGPS 2U / half-width rack-mount Note There are two different versions of the injector module (56V and 29V). You must select the correct injector for the types of radios that you will be powering. In both cases, the injectors use the same input power supplies or can be powered with +/-

48VDC. The output power is different and the type of SYNC signal used is different between the two types of injectors. Systems can have 29V and 56V injectors deployed alongside each other. Figure 29 Injector Module CMM5 Injector Compatibility Matrix The following table provides the Injector compatibility matrix. Table 51 Injector Compatibility Matrix Product Power/Injector Module Sync PMP/PTP 450i Yes/56V PMP 450m Yes/56V PMP 450/PTP 450 Yes/29V PMP 100/PTP 100 Yes/29V Yes Yes Yes Yes Page 2-47 Chapter 2: System hardware GPS synchronization CMM5 Specifications The following table provides specifications for the CMM5 Power & Sync Injector (56 Volts). Table 52 CMM5 Specifications CMM5 Power and Sync Injector 56 Volts Model Number C000000L556A Data Interface 4 each RJ45 Gigabit Powered output ports To Radios 4 each RJ45 Gigabit Data input ports To Switch Array 1 each GPS timing port (RJ-12) 1 each CMM5 USB Serial port for local administration 1 each RJ12 Daisy Chain port IN 1 each RJ12 Daisy Chain port OUT Surge Suppresion Lightning Suppression for each To Radios RJ45 Port Power Input Voltage: + or - 48 VDC Input Power Consumption: 400 watts Output Voltage: + or - 55 VDC Output Current: 0 - 1.8A per channel Output Power: 0 - 90 Watts per channel Cabinet Temperature

-40 C to +55C (-40 F to +131 F), 90%

humidity, condensing Physical Max Distance from Managed Radios: 328 cable feet (100m) Max Distance to GPS Antenna: 100 cable feet

(30.5m) Dimensions 8.85 W x 15.75 D x 1.65 H (225mm x 400mm x 42mm) Unit Weight 6.6 pounds (3kg) Power Interface 2 Power input ports for 48 VDC Power (Power Terminals supplies sold separately) Page 2-48 Chapter 2: System hardware GPS synchronization CMM4 (Rack Mount) The Cluster Management Module (CMM) is the heart of the Cambium systems synchronization capability, which allows network operators to reuse frequencies and add capacity while ensuring consistency in the quality of service to customers. For operators who prefer indoor CMM mounting, Cambium offers the Rack-Mounted Cluster Management Module 4. The unit is designed to be mounted onto a standard 19-inch telecommunications rack and to allow the Cambium CMM4 to be co-located with other telecommunications equipment. Figure 30 CMM4 (Rack Mount) The CMM4 has two DC power inputs, one 29 V and one 56V. It can be used to power and synchronize both 29 V legacy products such as the PMP 450 Series and 56V products such as the PMP 450i Series simultaneously. If the 29 V legacy products are connected to the CMM4, a 29 V power supply needs to be connected. If the 450i Series is connected to the CMM4, a 56 V power supply needs to be connected. The CMM4 supports having two of the 56 V and two of the 29 V supplies for redundancy. Warning PMP 450i Series requires different wiring between the CMM4 and device. If a PMP450 Series ODU is replaced by a PMP 450i Series and the existing drop cable needs to be re-used, the Ethernet cable adapter for CMM4 - N000045L001A" must be used between the CMM4 and the existing drop cable. Page 2-49 Chapter 2: System hardware GPS synchronization Figure 31 CMM4 56 V power adapter (dongle) CMM4 56 V power adapter cable pinout Figure 32 CMM4 power adapter cabling diagram J1 1 5 7 8 RJ45 Plug Shield J2 1 5 7 8 RJ45 Jack Page 2-50 Chapter 2: System hardware GPS synchronization Table 53 CMM4 power adapter cable pinout Plug J1 pin Jack J2 pin 1 2 3 4 5 6 7 8 1 2 3 4 7 6 5 8 Screen Screen Note Pins 5 and 7 are wired in a cross-over configuration. Page 2-51 Chapter 2: System hardware GPS synchronization CMM4 (Cabinet with switch) Designed to deliver consistent and reliable wireless broadband service, the PMP/PTP system gracefully scales to support large deployments. The cluster management module is the heart of the systems synchronization capability which allows network operators to re-use frequencies and add capacity while ensuring consistency in the quality of service to customers. As a result, subscribers can experience carrier-grade service even at the outer edge of the network. Figure 33 CMM4 (Cabinet with switch) CMM4 (Cabinet without switch) This CMM includes all of the functionality listed above but there is no switch. This provides the network operator the flexibility to use the switch of their choice with the power and synchronization capabilities of the CMM4. Page 2-52 Chapter 2: System hardware GPS synchronization CMM3/CMMmicro The CMM3 or CMMmicro (Cluster Management Module micro) provides power, GPS timing, and networking connections for an AP cluster. The CMM3 is configurable through a web interface. The CMM3 contains an 8-port managed switch that supports Power over Ethernet (PoE this is Cambium PoE, not the standard PoE) on each port and connects any combination of APs, BHMs, BHSs, or Ethernet feed. The Cambium fixed wireless broadband IP networks PoE differs from IEEE Standard 803.3af PoE, and the two should not be intermixed. The CMM3 can auto-negotiate speed to match inputs that are either 100Base-TX or 10Base-T, and either full duplex or half duplex, where the connected device is set to auto-negotiate. Alternatively, these parameters are settable. A CMM3 requires only one cable, terminating in an RJ-45 connector, for each connected module to distribute Ethernet signaling. power to as many as 8 co-located modulesAPs, BHMs, or BHSs. Through a browser interface to the managed switch, ports can be powered or not. sync to APs and BHMs. The CMM3 receives 1-pulse per second timing information from Global Positioning System (GPS) satellites through an antenna (included) and passes the timing pulse embedded in the 24-V power to the connected modules. GPS status information is available at the CMM3, however CMM3 provides time and date information to BHMs and APs if both the CMMmicro is operating on CMMmicro Release 2.1 or later and the AP/BHM is operating on System Release 4.2 or later. See Configuring time settings on Page 7-18. CMM3 does not provide time and date information to BHMs and APs if either the CMM3 is operating on a release earlier than CMMmicro Release 2.1 or the AP/BHM is operating on a release earlier than System Release 4.2. A CMM3/CMMicro is shown in Figure 34 and Figure 35. Page 2-53 Chapter 2: System hardware GPS synchronization Figure 34 CMM3 Figure 35 Pole mounted CMM3 Note A CMM3 cannot be used to power up a 450i Series ODUs. Page 2-54 Chapter 2: System hardware Installing a GPS receiver Installing a GPS receiver To install a GPS receiver as the timing reference source, use the following procedures:

Mounting the GPS receiver on page 2-56 Cabling the GPS Antenna on page 2-57 Installing and connecting the GPS LPU on page 2-57 Caution Prior to power-up of equipment, ensure that all cables are connected to the correct interfaces of the CMM4 unit and the UGPS receiver module. Failure to do so may result in damage to the equipment. GPS receiver location Mount the GPS receiver at a location that meets the following requirements:

It must be possible to protect the installation as described in Grounding and lightning protection on page 3-8. It must have an un-interrupted view of at least half of the southern (resp. northern) sky in the northern (resp. southern) hemisphere. For a receiver mounted on a wall there must be no other significant obstructions in the view of the sky. It must be mounted at least 1 m (3 ft), preferably 2 m (6 ft), away from other GPS receiving equipment. It must not be sited in the field of radiation of co-located radio communications equipment and should be positioned at a distance of at least 3 m (10 ft) away. Mount the UGPS receiver on the wall of the equipment building if there is a suitable location on the wall that can meet these requirements. Caution The GPS receiver is not approved for operation in locations where gas hazards exist, as defined by HAZLOC (USA) and ATEX (Europe). Mounting the GPS receiver module on the equipment building If mounting the GPS receiver on the equipment building (Figure 40), select a position on the wall that meets the following requirements:

It must be below the roof height of the equipment building or below the height of any roof-

mounted equipment (such as air conditioning plant). It must be below the lightning air terminals. It must not project more than 600mm (24 inches) from the wall of the building. Page 2-55 Chapter 2: System hardware Installing a GPS receiver If these requirements cannot all be met, then the module must be mounted on a metal tower or mast. Mounting the GPS receiver module on a metal tower or mast If mounting the GPS receiver module on a metal tower or mast (Figure 41), select a position that meets the following requirements:

It must not be mounted any higher than is necessary to receive an adequate signal from four GPS satellites. It must be protected by a nearby lightning air terminal that projects farther out from the tower than the GPS receiver module. Mounting the GPS receiver Mount the UGPS receiver (following manufacturers instructions) upon either an external wall

(Figure 40) or a metal tower or mast (Figure 41). Figure 36 GPS antenna mounting Page 2-56 Chapter 2: System hardware Installing a GPS receiver Procedure 1 Mounting the GPS receiver 1 Ensure that the mounting position has an unobstructed view of the sky to 20 above the horizon. is not the highest object at the site. (The GPS antenna does not need to be particularly high on a site, which would give it more exposure to lightning. It just needs to have an unobstructed view of the sky.) is not further than 100 feet (30.4 meters) of cable from the CMM. 2 Select a pole that has an outside diameter of 1.25 to 1.5 inches (3 to 4 cm) to which the GPS antenna bracket can be mounted. 3 4 5 6 7 Place the U-bolts (provided) around the pole as shown in Figure 28. Slide the GPS antenna bracket onto the U-bolts. Slide the ring washers (provided) onto the U-bolts. Slide the lock washers (provided) onto the U-bolts. Use the nuts (provided) to securely fasten the bracket to the U-bolts. Please refer to the PMP Synchronization Solutions User Guide located on the Cambium website

(http://www.cambiumnetworks.com/resources/pmp-synchronization-solutions ). Cabling the GPS Antenna Connect the GPS coax cable to the female N-connector on the GPS antenna. Please refer to the PMP Synchronization Solutions User Guide located on the Cambium website

(http://www.cambiumnetworks.com/resources/pmp-synchronization-solutions ). Installing and connecting the GPS LPU Install and ground the GPS drop cable LPU at the building (or cabinet) entry point, as described in Install the bottom LPU on page 6-20. Page 2-57 Chapter 2: System hardware Ordering the components Ordering the components This section describes how to select components for 450m Series, 450i Series and 450 Series Greenfield network or 450m/450i Series network migration. It specifies Cambium part numbers for 450 Platform Family components. Order PMP 450m Series, PMP/PTP 450i Series and PMP/PTP 450 Series ODUs from Cambium Networks. PMP 450m Table 54 PMP 450m Series ODU part numbers Cambium description Cambium part number PMP 450m AP (Access Point) 5 GHz PMP 450m Integrated Access Point, 90 Degree (ROW) C050045A101A 5 GHz PMP 450m Integrated Access Point, 90 Degree (FCC) C050045A102A 5 GHz PMP 450m Integrated Access Point, 90 Degree (EU) C050045A103A 5 GHz PMP 450m Integrated Access Point, 90 Degree (DES Only) C050045A104A 5 GHz PMP 450m Integrated Access Point, 90 Degree (IC) C050045A105A PMP 450i Table 55 PMP 450i Series ODU part numbers Cambium description PMP 450i AP (Access Point) 900 MHz PMP 450i Connectorized Access Point 3 GHz PMP 450i Connectorized Access Point 3 GHz PMP 450i Integrated Access Point, 90 Degree Cambium part number C009045A001A C030045A001A C030045A002A 3 GHz PMP 450i Connectorized Access Point, DES Only C030045A003A 3 GHz PMP 450i Integrated Access Point, 90 Degree, DES Only C030045A004A 5 GHz PMP 450i Connectorized Access Point (RoW) 5 GHz PMP 450i Connectorized Access Point (FCC) 5 GHz PMP 450i Connectorized Access Point (EU) C050045A001A C050045A002A C050045A003A Page 2-58 Chapter 2: System hardware Ordering the components Cambium description Cambium part number 5 GHz PMP 450i Connectorized Access Point (DES Only) C050045A004A 5 GHz PMP 450i Connectorized Access Point (IC) C050045A015A 5 GHz PMP 450i AP, Integrated 90sector antenna (RoW) C050045A005A 5 GHz PMP 450i AP, Integrated 90sector antenna (FCC) C050045A006A 5 GHz PMP 450i Integrated Access Point, 90 degree (EU) C050045A007A 5 GHz PMP 450i AP, Integrated 90sector antenna (DES only) C050045A008A 5 GHz PMP 450i AP, Integrated 90sector antenna (IC) C050045A016A PMP 450i SM (Subscriber Module) 3 GHz PMP 450i Connectorized Subscriber Module 3 GHz PMP 450i SM, Integrated High Gain Antenna 5 GHz PMP 450i Connectorized Subscriber Module 5 GHz PMP 450i SM, Integrated High Gain Antenna Note The 450i SM does not have license keys. C030045C001A C030045C002A C050045C001A C050045C002A PTP 450i Table 56 PTP 450i Series ODU part numbers Cambium description Cambium part number 3 GHz PTP 450i END, Connectorized 3 GHz PTP 450i END, Integrated High Gain Antenna 5 GHz PTP 450i END, Connectorized (RoW) 5 GHz PTP 450i END, Connectorized (FCC) 5 GHz PTP 450i END, Connectorized (EU) 5 GHz PTP 450i END, Connectorized (DES only) 5 GHz PTP 450i END, Connectorized (IC) C030045B001A C030045B002A C050045B001A C050045B003A C050045B005A C050045B007A C050045B015A 5 GHz PTP 450i END, Integrated High Gain Antenna (RoW) C050045B002A 5 GHz PTP 450i END, Integrated High Gain Antenna (FCC) C050045B004A 5 GHz PTP 450i END, Integrated High Gain Antenna (EU) C050045B006A Page 2-59 Chapter 2: System hardware Ordering the components Cambium description Cambium part number 5 GHz PTP 450i END, Integrated High Gain Antenna (DES only) C050045B008A 5 GHz PTP 450i END, Integrated High Gain Antenna (IC) C050045B016A Ethernet cable adapter for CMM4 N000045L001A PMP 450 Table 57 PMP 450 Series ODU part numbers Cambium description PMP 450 AP (Access Point) 2.4 GHz PMP 450 Connectorized Access Point 2.4 GHz PMP 450 Connectorized Access Point (DES) 3.5 GHz PMP 450 Connectorized Access Point 3.5 GHz PMP 450 Connectorized Access Point (DES) 3.6 GHz PMP 450 Connectorized Access Point 3.6 GHz PMP 450 Connectorized Access Point (DES) 5 GHz PMP 450 Connectorized Access Point Cambium part number C024045A001A C024045A003A C035045A001A C035045A003A C036045A001A C036045A003A C054045A001A 5 GHz PMP 450 Connectorized Access Point (US only) C054045A002A 5 GHz PMP 450 Connectorized Access Point (DES) C054045A003A PMP 450 AP Lite 2.4 GHz PMP 450 Connectorized Access Point - Lite C024045A011A 3.3-3.6 GHz PMP 450 Connectorized Access Point - Lite C035045A011A 3.55-3.8 GHz PMP 450 Connectorized Access Point - Lite C036045A011A 5 GHz PMP 450 Connectorized Access Point - Lite C054045A011A 5 GHz PMP 450 Connectorized Access Point (FCC) - Lite C054045A012A PMP 450 SM (Subscriber Module) 900 MHz PMP 450 Connectorized Subscriber Module C009045C001A 2.4 GHz PMP 450 Subscriber Module, 4 Mbps 2.4 GHz PMP 450 Subscriber Module, 10 Mbps 2.4 GHz PMP 450 Subscriber Module, 20 Mbps 2.4 GHz PMP 450 Subscriber Module, Uncapped C024045C001A C024045C002A C024045C003A C024045C004A Page 2-60 Chapter 2: System hardware Ordering the components Cambium description Cambium part number 2.4 GHz PMP 450 Connectorized Subscriber Module, 4 Mbps C024045C005A 2.4 GHz PMP 450 Connectorized Subscriber Module, 10 Mbps C024045C006A 2.4 GHz PMP 450 Connectorized Subscriber Module, 20 Mbps C024045C007A 2.4 GHz PMP 450 Connectorized Subscriber Module, Uncapped C024045C008A 3.5 GHz PMP 450 High Gain Directional Integrated Subscriber C035045C014A 3.5 GHz PMP 450 Subscriber Module, 4 Mbps 3.5 GHz PMP 450 Subscriber Module, 10 Mbps 3.5 GHz PMP 450 Subscriber Module, 20 Mbps 3.5 GHz PMP 450 Subscriber Module, Uncapped C035045C001A C035045C002A C035045C003A C035045C004A 3.5 GHz PMP 450 Connectorized Subscriber Module, 4 Mbps C035045C005A 3.5 GHz PMP 450 Connectorized Subscriber Module, 10 Mbps C035045C006A 3.5 GHz PMP 450 Connectorized Subscriber Module, 20 Mbps C035045C007A 3.5 GHz PMP 450 Connectorized Subscriber Module, Uncapped C035045C008A 3.6 GHz PMP 450 High Gain Directional Integrated Subscriber C036045C014A 3.6 GHz PMP 450 Subscriber Module, 4 Mbps 3.6 GHz PMP 450 Subscriber Module, 10 Mbps 3.6 GHz PMP 450 Subscriber Module, 20 Mbps 3.6 GHz PMP 450 Subscriber Module, Uncapped C036045C001A C036045C002A C036045C003A C036045C004A 3.6 GHz PMP 450 Connectorized Subscriber Module, 4 Mbps C036045C005A 3.6 GHz PMP 450 Connectorized Subscriber Module, 10 Mbps C036045C006A 3.6 GHz PMP 450 Connectorized Subscriber Module, 20 Mbps C036045C007A 3.6 GHz PMP 450 Connectorized Subscriber Module, Uncapped C036045C008A 5 GHz PMP 450 Connectorized Subscriber Module, 4 Mbps C054045C005A 5 GHz PMP 450 Connectorized Subscriber Module, 10 Mbps C054045C006A 5 GHz PMP 450 Connectorized Subscriber Module, 20 Mbps C054045C007A 5 GHz PMP 450 Connectorized Subscriber Module, Uncapped C054045C008A 5 GHz PMP 450 Integrated Subscriber Module, 4 Mbps C054045C001B 5 GHz PMP 450 Integrated Subscriber Module, 10 Mbps C054045C002B 5 GHz PMP 450 Integrated Subscriber Module, 20 Mbps C054045C003B 5 GHz PMP 450 Integrated Subscriber Module, Uncapped C054045C004B Page 2-61 Chapter 2: System hardware Ordering the components Cambium description Cambium part number 5 GHz PMP 450 Connectorized Subscriber Module, 4 Mbps C054045C005B 5 GHz PMP 450 Connectorized Subscriber Module, 10 Mbps C054045C006B 5 GHz PMP 450 Connectorized Subscriber Module, 20 Mbps C054045C007B 5 GHz PMP 450 Connectorized Subscriber Module, Uncapped C054045C008B 5 GHz PMP 450d Subscriber Module, 20 Mbps 4-pack C054045H013B 5 GHz PMP 450d Subscriber Module, Uncapped 4-pack C054045H014B PTP 450 Table 58 PTP 450 Series ODU part numbers Cambium description Cambium part number PTP 450 3.5 GHz END Integrated PTP 450 3.5 GHz END Connectorized PTP 450 3.5 GHz END Integrated DES Only PTP 450 3.5 GHz END Connectorized DES Only PTP 450 3.65 GHz END Integrated PTP 450 3.65 GHz END Connectorized PTP 450 3.65 GHz END Integrated DES Only PTP 450 3.65 GHz END Connectorized DES Only PTP 450 5 GHz END Integrated (ROW) PTP 450 5 GHz END Connectorized (ROW) PTP 450 5 GHz END Integrated (ROW) DES Only C035045B001A C035045B002A C035045B003A C035045B004A C036045B001A C036045B002A C036045B003A C036045B004A C054045B001A C054045B002A C054045B003A PTP 450 5 GHz END Connectorized (ROW) DES Only C054045B004A PTP 450 5 GHz END Integrated (FCC) PTP 450 5 GHz END Connectorized (FCC) C054045B005A C054045B006A PMP/PTP 450/450i Series Accessories Table 59 PMP/PTP 450/450I Series Accessories Cambium description Cambium part number PMP 450 AP Antenna Options Page 2-62 Chapter 2: System hardware Ordering the components Cambium description Cambium part number 900 MHz 65 degree Sector Antenna (Dual Slant) N009045D001A 900 MHz 12 dBi gain directional antenna (Dual Slant) N009045D003A 2.4 GHz Dual Slant Antenna for 60 Degree Sector C024045D601A 3.5 GHz and 3.6 GHz Dual Slant Antenna for 90 Degree Sector C030045D901A 5 GHz Antenna for 60 Degree Sector 5 GHz Antenna for 90 Degree Sector N-type to N-type cable (16 inch length) Power supplies Power supply, 60 W, 56 V with Gbps support AC+DC Enhanced Power Injector Line Cord, Fig 8 US Line Cord, Fig 8 UK Line Cord, Fig 8 EU 85009325001 85009324001 30009406002 N000065L001B C000065L002B N000065L003A N000065L004A N000065L005A Power over Ethernet midspan, 60 W, -48 VDC Input N000000L036A Power Supply, 30 W, 56 V Gbps support Gigabit Enet Capable Power Supply - 30VDC, 15W Cable, UL Power Supply Cord Set, US Cable, UL Power Supply Cord Set, EU Cable, UL Power Supply Cord Set, UK AP Optional Equipment CMM MICRO (Outdoor Enclosure) (450 only) CMM5 Controller CMM5 Power and Sync Injector 56V CMM5 Power and Sync Injector 29V uGPS CMM5 Power Supply, AC, 56V 240W CMM5 Power Supply AC, 48V, 640W CMM5 Spare Controller Cable 1m CMM5 to uGPS Shielded Cable (20 meter) CMM5 Spare DC Power Connector (10 pack) Page 2-63 N000000L034A N000900L001A N000900L007A N000900L008A N000900L009A 1070CKHH C000000L500A C000000L556A C000000L529A 1096H N000000L054B N000000L101A N000000L102A N000000L103A N000000L104A Chapter 2: System hardware Ordering the components Cambium description Cambium part number CMM4 W/RUGGEDIZED Switch and GPS CMM4 NO Switch CMM4 Rack Mount Assembly Ethernet cable adapter for CMM4 Universal GPS Module RJ-45 Gland Spare PG16 style (QTY 10) Blanking Plug Pack (Qty 10) SM Optional Equipment Power Supply, 30 W, 56 V Gbps support Gigabit Enet Capable Power Supply 30 VDC, 15 W Cable, UL Power Supply Cord Set, US Cable, UL Power Supply Cord Set, EU Cable, UL Power Supply Cord Set, UK 53CM Offset, Reflector Dish Kit, 4PK Alignment Tool Headset Accessories Surge Suppressor (30 VDC) Gigabit Surge Suppressor (56 VDC) LPU and Grounding Kit (1 kit per ODU) Single Mode Optical SFP Interface per ODU Multimode Kit 50 Ohm Braided Coaxial Cable - 75 meter 50 Ohm Braided Coaxial Cable - 500 meter RF Connector, N, Male, Straight for CNT-400 Cable Tyco/AMP, Mod Plug RJ45, 100 pack Tyco/AMP Crimp Tool 1090CKHH 1091HH 1092HH N000045L001A 1096H N000065L033A N000065L036A N000000L034A N000900L001A N000900L007A N000900L008A N000900L009A HK2022A ACATHS-01A 600SSH C000000L033A C000065L007A C000065L008A C000065L009A 30010194001 30010195001 09010091001 WB3177 WB3211 RJ-45 Spare Grounding Gland - PG16 size (Qty. 10) N000065L033 Mounting brackets Tilt Bracket Assembly Mounting Bracket (Integrated) N000045L002A N000065L031A Page 2-64 Chapter 2: System hardware Ordering the components Cambium description Cambium part number Mounting Bracket (Connectorized) Upgrade Keys PMP 450 4 To 10 Mbps Upgrade Key PMP 450 4 To 20 Mbps Upgrade Key PMP 450 4 To Uncapped Upgrade Key PMP 450 10 To 20 Mbps Upgrade Key PMP 450 10 To Uncapped MBPS Upgrade Key PMP 450 20 To Uncapped MBPS Upgrade Key PMP 450 Lite AP to Full AP Upgrade Key Extended Warranty N000065L032A C000045K002A C000045K003A C000045K004A C000045K005A C000045K006A C000045K007A C000045K008A PMP 450 Platform AP Extended Warranty, 1 Additional Year SG00TS4009A PMP 450 Platform AP Extended Warranty, 2 Additional Years SG00TS4017A PMP 450 Platform AP Extended Warranty, 4 Additional Years SG00TS4025A PMP 450 Platform SM Extended Warranty, 1 Additional Year SG00TS4010A PMP 450 Platform SM Extended Warranty, 2 Additional Years SG00TS4018A PMP 450 Platform SM Extended Warranty, 4 Additional Years SG00TS4026A Page 2-65 Chapter 3: System planning This chapter provides information to help the user to plan a PMP/PTP 450 Platform link. The following topics are described in this chapter:

Typical deployment on page 3-2 contains diagrams illustrating typical PMP/PTP 450 Platform site deployments. Site planning on page 3-7 describes factors to be considered when planning the proposed link end sites, including grounding, lightning protection and equipment location. Radio Frequency planning on page 3-17 describes how to plan PMP/PTP 450 Platform links to conform to the regulatory restrictions that apply in the country of operation. Link planning on page 3-23 describes factors to be taken into account when planning links, such as range, path loss and throughput. Planning for connectorized units on page 3-26 describes factors to be taken into account when planning to use connectorized ODUs with external antennas in PMP/PTP 450 Platform links. Data network planning on page 3-28 describes factors to be considered when planning PMP/PTP 450 Platform data networks. Network management planning on page 3-36 describes how to plan for PMP/PTP 450 Platform links to be managed remotely using SNMP. Security planning on page 3-37 describes how to plan for PMP/PTP 450 Platform links to operate in secure mode. Page 3-1 Chapter 3: System planning Typical deployment Typical deployment This section contains diagrams illustrating typical PMP/PTP 450 Platform site deployments. ODU with PoE interface to PSU In the basic configuration, there is only one Ethernet interface, a copper cable for power over Ethernet (POE) from the PSU to the ODU (PSU port), as shown in the following diagrams: mast or tower installation (Figure 37 ), wall installation (Figure 38) and roof installation (Figure 39). Figure 37 Mast or tower installation Page 3-2 ODUAC supplyPSUNetworkequipmentODU ground cablesPower over Ethernet CAT5e cable (gel-filled, shielded with copper-plated steel)Network CAT5e cableSite grounding systemBottom LPUFirst point of contact between drop cable and towerTower ground barGround ringIntermediate ground cable(s) as requiredBuilding entryEquipment building or cabinet Chapter 3: System planning Typical deployment Figure 38 Wall installation Page 3-3 ODUPSUNetworkequipmentODU ground cablesSite grounding systemBottom LPUGround ringFirst point of contact between drop cable and wallBuilding entryPower over Ethernet CAT5e cable (gel-filled, shielded with copper-plated steel)Network Cat5e cableAC supply Chapter 3: System planning Typical deployment Figure 39 Roof installation Page 3-4 Air terminals (finials)Tower grounding conductorBuilding ground ringAC serviceEquipment roomODUODU ground cablesNetwork CAT5e cableSite grounding systemAC supplyPSUNetworkequipmentBottom LPUBuilding entry pointDrop cable inside buildingEquipment room entry pointPower over Ethernet CAT5e cable (gel-filled, shielded with copper-plated steel) Chapter 3: System planning Typical deployment Figure 40 GPS receiver wall installation Page 3-5 NetworkequipmentODU/ GPS Ground cablesSite grounding systemDrop cable to top LPU and ODUGround ringPower over Ethernet CAT5e cable (gel-filled, shielded with copper-plated steel)Network Cat5e cableCMM 4GPS receiverFirst point of contact between drop cable and wall Chapter 3: System planning Typical deployment Figure 41 GPS receiver tower or mast installation Page 3-6 ODU/GPS ground cablesPower over Ethernet CAT5e cable (gel-filled, shielded with copper-plated steel)Network CAT5e cableSite grounding systemTower ground barGround ringEquipment building or cabinetNetworkequipmentCMM 4Drop cable to top LPU and ODUGPS receiverFirst point of contact between drop cable and towerIntermediate ground cable(s) as required Chapter 3: System planning Site planning Site planning This section describes factors to be considered when choosing sites for PMP or PTP radios, power supplies, CMM4 (if applicable) and UGPS (if applicable). Site selection for PMP/PTP radios When selecting a site for the ODU, consider the following factors:

Height and location to ensure that people are kept away from the antenna; see Calculated distances and power compliance margins on page 4-24. Height and location to achieve the best radio path. Indoor location where the power supply LED indicators will be visible, so the drop cable length will not exceed the maximum recommended length; see Power supply site selection on page 3-8. Ability to meet the requirements specified in Grounding and lightning protection on page 3-8. Aesthetics and planning permission issues. Cable lengths; see Ethernet standards and cable lengthsError! Reference source not found. on p age 2-292-25. The effect of strong winds on the installation; see ODU wind loading on page 3-11. Page 3-7 Chapter 3: System planning Site planning Power supply site selection When selecting a site for the ODU power supply, consider the following factors:

Indoor location with no possibility of condensation, flooding or high humidity. Availability of a mains electricity supply. Located in an environment where it is not likely to exceed its operational temperature rating, allowing for natural convection cooling. Accessibility for viewing status indicator LED and connecting Ethernet cables. Cable lengths; see Error! Reference source not found.Ethernet standards and cable l engthsError! Reference source not found. on page 2-29. Maximum cable lengths When installing PMP/PTP 450i Series ODU, the maximum permitted length of the shielded copper Ethernet interface cable is 330 feet (100m) from AP/BHM/SM/BHS to their associated power supplies or CMM4. Grounding and lightning protection Warning Electro-magnetic discharge (lightning) damage is not covered under warranty. The recommendations in this guide, when followed correctly, give the user the best protection from the harmful effects of EMD. However 100% protection is neither implied nor possible. Structures, equipment and people must be protected against power surges (typically caused by lightning) by conducting the surge current to ground via a separate preferential solid path. The actual degree of protection required depends on local conditions and applicable local regulations. To adequately protect a PMP/PTP 450 Platform installation, both ground bonding and transient voltage surge suppression are required. Full details of lightning protection methods and requirements can be found in the international standards IEC 61024-1 and IEC 61312-1, the U.S. National Electric Code ANSI/NFPA No. 70-1984 or section 54 of the Canadian Electric Code. Warning International and national standards take precedence over the requirements in this guide. Page 3-8 Chapter 3: System planning Site planning Lightning protection zones Use the rolling sphere method (Figure 42) to determine where it is safe to mount equipment. An imaginary sphere, typically 50 meters in radius, is rolled over the structure. Where the sphere rests against the ground and a strike termination device (such as a finial or ground bar), all the space under the sphere is considered to be in the zone of protection (Zone B). Similarly, where the sphere rests on two finials, the space under the sphere is considered to be in the zone of protection. Figure 42 Rolling sphere method to determine the lightning protection zones Zone A: In this zone a direct lightning strike is possible. Do not mount equipment in this zone. Zone B: In this zone, direct EMD (lightning) effects are still possible, but mounting in this zone significantly reduces the possibility of a direct strike. Mount equipment in this zone. Warning Never mount equipment in Zone A. Mounting in Zone A may put equipment, structures and life at risk. Page 3-9 Chapter 3: System planning Site planning Site grounding system Confirm that the site has a correctly installed grounding system on a common ground ring with access points for grounding the 450 Platform Family ODU. If the outdoor equipment is to be installed on the roof of a high building (Figure 39), confirm that the following additional requirements are met:

A grounding conductor is installed around the roof perimeter to form the main roof perimeter lightning protection ring. Air terminals are installed along the length of the main roof perimeter lightning protection ring, typically every 6.1m (20ft). The main roof perimeter lightning protection ring contains at least two down conductors connected to the grounding electrode system. The down conductors should be physically separated from one another, as far as practical. ODU and external antenna location Find a location for the ODU (and external antenna for connectorized units) that meets the following requirements:

The equipment is high enough to achieve the best radio path. People can be kept a safe distance away from the equipment when it is radiating. The safe separation distances are defined in Calculated distances and power compliance margins on page 4-24. The equipment is lower than the top of the supporting structure (tower, mast or building) or its lightning air terminal. If the ODU is connectorized, select a mounting position that gives it maximum protection from the elements, but still allows easy access for connecting and weatherproofing the cables. To minimize cable losses, select a position where the antenna cable lengths can be minimized. If diverse or two external antennas are being deployed, it is not necessary to mount the ODU at the midpoint of the antennas. ODU ambient temperature limits Select a location where the ODU can operate within safe ambient temperature limits. The following points need to be considered while selecting a location for the ODU:

The ODU must be mounted in a Restricted Access Location (as defined in EN 60950-1) if the operating ambient temperature may exceed 40C, including solar radiation. If the ambient temperature never exceeds 40C, the temperature of the external metal case parts of the ODU will not exceed the touch temperature limit of 70C. If the ambient temperature never exceeds 60C, the temperature of the external metal case parts of the ODU will not exceed the touch temperature limit of 90C. Page 3-10 Chapter 3: System planning Site planning Note A restricted access location is defined (in EN 60950-1) as one where access may only be gained by use of a tool or lock and key, or other means of security, and access is controlled by the authority responsible for the location. Access must only be gained by persons who have been instructed about the reasons for the restrictions applied to the location and about any precautions that must be taken. Examples of permissible restricted access locations are a lockable equipment room or a lockable cabinet. ODU wind loading Ensure that the ODU and the structure on which it is mounted are capable of withstanding the prevalent wind speeds at a proposed 450 Platform site. Wind speed statistics are available from national meteorological offices. The ODU and its mounting bracket are capable of withstanding wind speeds of:

Up to 200 mph (322 kph) for PMP 450m Series AP 5 GHz Up to 200 mph (322 kph) for PMP/PTP 450i all models 5 GHz Up to 200 mph (322 kph) for PMP/PTP 450i 3 GHz all models Up to 200 mph (322 kph) for PMP/PTP 450 all models Up to 200 mph (322 kph) for PMP 450 Ruggedized Up to 200 mph (322 kph) for PMP 450i all models 900 MHz Up to 90 mph (145 kph) for PMP 450d Up to 100 mph (161 kph) for 900 MHz antennas Wind blowing on the ODU will subject the mounting structure to significant lateral force. The magnitude of the force depends on both wind strength and surface area of the ODU. Wind loading is estimated using the following formulae:

Force (in kilograms) = 0.1045aV2 where:

o a is the surface area in square meters, and o V is the wind speed in meters per second. Force (in pounds) = 0.0042Av2 where:

o A is the surface area in square feet, and o v is the wind speed in miles per hour. Applying these formulae to the 450 platform at different wind speeds, the resulting wind loadings are shown in below tables. Page 3-11 Chapter 3: System planning Site planning Table 60 PMP 450m Series wind loading (Newton) Type of ODU Max surface area Wind speed (kilometer per hour)

(square meters) 160 170 180 190 200 Integrated 90 sector antenna 0.331 671 757 849 946 1048 Table 61 PMP/PTP 450i Series wind loading (Newton) Type of ODU Max surface area Wind speed (kilometer per hour)

(square meters) Connectorized Directional Yagi antenna - 900 MHz 0.035 0.025 160 94 67 170 106 76 180 119 85 190 132 94 200 146 105 External 65 sector 0.253 677 764 857 954 1058 antenna 900 MHz Directional antenna 0.1 142 160 180 200 222 3.x GHz Integrated 90 sector 0.18 83 94 105 117 130 antenna -3.x GHz Directional antenna 0.093 249 281 315 351 389 5 GHz Integrated 90 sector 0.126 337 381 427 475 527 antenna - 5 GHz Table 62 PMP 450m Series wind loading (lb force) Type of ODU Max surface area Wind speed (miles per hour)

(square feet) 100 105 110 115 120 Integrated 90 sector antenna 3.565 150 165 181 198 216 Page 3-12 Chapter 3: System planning Site planning Table 63 PMP/PTP 450i Series wind loading (lb force) Type of ODU Max surface area Wind speed (miles per hour)

(square feet) Connectorized 0.377 Directional antenna 1.001 5 GHz 100 105 110 115 120 16 42 17 46 19 51 21 56 23 61 Integrated 90 sector 1.356 57 63 69 75 82 antenna - 5 GHz Directional Yagi 0.27 11 13 14 15 16 antenna - 900 MHz External 65 sector 2.72 114 126 138 151 165 antenna 900 MHz For a connectorized ODU, add the wind loading of the external antenna to that of the ODU. The antenna manufacturer should be able to quote wind loading. Table 64 PMP/PTP 450 Series wind loading (Newton) Type of ODU Max surface area Wind speed (kilometer per hour)

(square meters) External 60 sector 0.27 antenna 2.4 GHz AP 160 722 170 815 180 914 190 200 1019 1129 External 60 sector 0.066 177 199 223 249 276 antenna 5 GHz AP External 90 sector 0.083 222 251 281 313 347 antenna 5 GHz AP SM 0.027 72 82 91 Integrated High-Gain, 0.093 249 281 315 102 351 113 389 Ruggedized Integrated Dish 0.14 375 423 474 528 585 Page 3-13 Chapter 3: System planning Site planning Table 65 PMP/PTP 450 Series wind loading (lb force) Type of ODU Max surface area Wind speed (miles per hour)

(square feet) External 60 sector 2.9 antenna 2.4 GHz AP 100 122 105 134 110 147 115 161 120 175 External 60 sector 0.71 29.8 33 37 39 43 antenna 5 GHz AP External 90 sector 0.89 37 41 45 49 54 antenna 5 GHz AP SM 0.29 Integrated High-

1 Gain, Ruggedized 12 42 13 46 15 51 16 56 18 60 Integrated Dish 1.49 63 69 76 83 90 Page 3-14 Chapter 3: System planning Site planning Hazardous locations Check that the ODUs will not be exposed to hazardous gases, as defined by HAZLOC (USA) and ATEX (Europe) regulations. If there is a risk of such exposure, then order the PTP/PMP 450i ATEX/Hazloc product variants, as these are intended for operation in locations with gas hazards. The ATEX and HAZLOC standards limit the EIRP as shown in Table 66. Table 66 EIRP limits from ATEX and HAZLOC standards ATEX gas HAZLOC gas Typical gas type Maximum EIRP group group

(Watt) IIA IIB IIC IIC D C B A Propane Ethylene Hydrogen Acetylene 6 3.5 2 2 Further reading For information about Refer to Ordering Connectorized/ Integrated PMP/PTP 450i ATEX/HAZLOC ODU ATEX/HAZLOC ODUs models/part numbers on page 2-13 ATEX/HAZLOC standards and type approval Error! Reference source not found. on page 4-

32 Deployment of ATEX/HAZLOC ODUs PTP 700 Series Hazardous Location Guide Drop cable grounding points To estimate how many grounding kits are required for each drop cable, refer to the site installation diagrams (Figure 37 , Figure 38 and Figure 39) and use the following criteria:

The drop cable shield must be grounded near the ODU at the first point of contact between the drop cable and the mast, tower or building. The drop cable shield must be grounded at the building entry point. For mast or tower installations (Figure 37), use the following additional criteria:

The drop cable shield must be grounded at the bottom of the tower, near the vertical to horizontal transition point. This ground cable must be bonded to the tower or tower ground bus bar (TGB), if installed. Page 3-15 Chapter 3: System planning Site planning If the tower is greater than 61 m (200 ft) in height, the drop cable shield must be grounded at the tower midpoint, and at additional points as necessary to reduce the distance between ground cables to 61 m (200 ft) or less. In high lightning-prone geographical areas, the drop cable shield must be grounded at spacing between 15 to 22 m (50 to 75 ft). This is especially important on towers taller than 45 m (150 ft). For roof installations (Figure 39), use the following additional criteria:

The drop cable shield must be bonded to the building grounding system at its top entry point

(usually on the roof). The drop cable shield must be bonded to the building grounding system at the entry point to the equipment room. Lightning Protection Unit (LPU) location Find a location for the bottom LPU that meets the following requirements:

The bottom LPU can be connected to the drop cable from the ODU. The bottom LPU is within 600 mm (24 in) of the point at which the drop cable enters the building, enclosure or equipment room within a larger building. The bottom LPU can be bonded to the grounding system. Page 3-16 Chapter 3: System planning Radio Frequency planning Radio Frequency planning This section describes how to plan 450 Platform Family links to conform to analysis of spectrum and the regulatory restrictions that apply in the country of operation. Regulatory limits Many countries impose EIRP limits (Allowed EIRP) on products operating in the bands used by the 450 Platform Family. Refer to Equipment Disposal (Chapter 10: Reference Information) on page 10-38 to determine what the maximum transmitted power and EIRP for PMP/PTP 450/450i Series that can be used in each of countries and frequency band. Caution It is the responsibility of the user to ensure that the PMP/PTP ODU is operated in accordance with local regulatory limits. Note Contact the applicable radio regulator to find out whether or not registration of the PMP/PTP 450/450i Series link is required. Conforming to the limits Ensure the link is configured to conform to local regulatory requirements by configuring the PMP 450/450i Series AP or PTP 450/450i Series BHM for the correct country. In the following situations, this does not prevent operation outside the regulations:

When using connectorized ODUs with external antennas, the regulations may require the maximum transmit power to be reduced. Available spectrum The available spectrum for operation depends on the regulatory band. When configured appropriately, the unit will only allow operation on those channels which are permitted by the regulations. Page 3-17

 

 

PMP 450m PCB A005138 Front View (with RF Shields Fitted) PMP 450m PCB A005138 Front View (with RF Shields Removed) PMP 450m PCB A005138 Rear View (with RF Shields Fitted) PMP 450m PCB A005138 Rear View (with RF Shields Removed)

 

 

PMP 450m Front of Antenna PMP 450m Rear of Antenna PMP 450m Rear View PMP 450m View of Rear Casting PMP 450m Inside Casting PMP 450m Left Hand Side PMP 450m Right Hand Side

 

 

*C050045A101A*

Part No: C050045A102A

*5083HH*

Model: 5083HH

*6069NS006U*

MSN: ############

*0A003EA005B3*

ESN: ############

ELECTRICAL SAFETY LISTING No. E112443 COMPLIES WITH UL60950-1/22 - CSA 22.2 60950-1/22 CAUTION: Read theUser Guide before Installation ATTENTION : Lisez le Guide de l'utilisateur avant l'Installation Power Requirements : 58V 1.7A FCC ID: QWP-50450M Made in Mexico

 

 

*C050045A101A*

Part No: C050045A102A

*5083HH*

Model: 5083HH

*6069NS006U*

MSN: ############

*0A003EA005B3*

ESN: ############

ELECTRICAL SAFETY LISTING No. E112443 COMPLIES WITH UL60950-1/22 - CSA 22.2 60950-1/22 CAUTION: Read theUser Guide before Installation ATTENTION : Lisez le Guide de l'utilisateur avant l'Installation Power Requirements : 58V 1.7A FCC ID: QWP-50450M Made in Mexico

 

 

*C050045A1XXA*

Part No: C050045A105A

*5082CHH*

Model: 5083HH

*6069NS006U*

MSN: ############

*0A003EA005B3*

ESN: ############

Power Requirements : 58V 1.7A Made in Mexico IC: 109AO-50450M ELECTRICAL SAFETY LISTING No. E112443 COMPLIES WITH UL60950-1/22 - CSA 22.2 60950-1/22 CAUTION: Read theUser Guide before Installation ATTENTION : Lisez le Guide de l'utilisateur avant l'Installation

*C050045A1XXA*

Part No: C050045A115A

*5082CHH*

Model: 5083HH

*6069NS006U*

MSN: ############

*0A003EA005B3*

ESN: ############

Power Requirements : 58V 1.7A Made in Mexico IC: 109AO-50450M ELECTRICAL SAFETY LISTING No. E112443 COMPLIES WITH UL60950-1/22 - CSA 22.2 60950-1/22 CAUTION: Read theUser Guide before Installation ATTENTION : Lisez le Guide de l'utilisateur avant l'Installation

 

 

CLASS III PERMISSIVE CHANGE REQUEST Class III Permissive Change Request Element Materials Technology 100 Frobisher Business Park Malvern Worcestershire WR14 1BX UK Date: 19th November 2019 RE:

FCC ID: QWP-50450M To Whom It May Concern:

Please be advised that pursuant to FCC Rule 47CFR 2.1043 the manufacturer requests that the above referenced model be approved for class III permissive change. The reason for the class III change is an update in software to support operation in the Part 90Y 4.94 to 4.99 GHz Frequency Band. Software support of this frequency band can only be enabled by software controlled by Cambium Networks. Cambium Networks confirm that the PMP 450m FCC ID QWP-50450M used in this C3PC submission is electrically and mechanically identical to the PMP 450m used in other grant submissions. Cambium Networks confirm that there has been no change to the original Software, Distribution and Security Documentation to support this class III permissive change request. Thank you for your attention to this matter. Yours faithfully Donald W Reid CEng MIET Principal Regulatory Engineer Cambium Networks Ltd

 

 

Element Materials Technology 100 Frobisher Business Park Malvern Worcestershire WR14 1BX UK Date: 3rd December 2019 RE: Certification Application FCC ID: QWP-50450M Letter of Agency To Whom It May Concern:

We certify that we are not subject to denial of federal benefits, which includes FCC benefits, pursuant to Section 5301 of the Anti-Drug Abuse ACT of 1988, U.S.C. 862. Further, no party, as defined in 47 CFR 1.2002(b), to the application, is subject to denial of federal benefits, that includes FCC benefits. Thank you for your attention to this matter. Yours faithfully Donald W Reid CEng MIET Principal Regulatory Engineer Cambium Networks Ltd

 

 

Element Materials Technology 100 Frobisher Business Park Malvern Worcestershire WR14 1BX UK Date: 19th November 2019 RE: Software Attestation for Class III Permissive Change Request FCC ID: QWP-50450M To Whom It May Concern:

Subject Attestation of software used in Part 90Y submission for FCC ID: QWP-50450M. Cambium Networks confirm that: -

During certification test the PMP 450m uses internal development software which is identified as MEDUSA-BUILD-xxx, where xxx is a unique reference number; this development software is the building block for the final released software. On completion of certification test and internal System Integration Test this software will be released to customers with a customer facing traceable identification reference defined as CANOPY W.X.Y.Z :-

W = Major - designator for a major feature set X = Minor - designator for minor updates, bug fixes and enabling HW features Y = Point - designator for bug fixes Z = Dot designator for emergency bug fixes on a Point release CANOPY 16.0 would be the first release and a Major software version, CANOPY 16.1 would be a Minor modification to the major software release, CANOPY 16.1.1 would be a Point Release to the minor release and CANOPY 16.1.1.1 would be a Dot bug fix to the point release When comparing two software versions, the higher BUILD-xxx number used with internal development software indicates the later version and with customer facing software the later version is the one with the greater Major version or, if the Major versions are identical, the one with the greater Minor version or, if the Minor versions are identical, the one with the greater Point version or, if the Point versions are identical, the one with the greater Dot version indicates the later version. Any version later than the version modified by a Class III change will exhibit the modified behavior or features of the Class III change. Page 2 of 2 Software versions listed in the Original QWP-50450M Grant and subsequent Class III Permissive change requests are listed below. Software Version declared in the original Part UNII-3 submission: -

CANOPY 15.0 (Build 579) AP-DES CANOPY 15.0 (Build 619) AP-DES (30MHz to 1 GHz and AC Power Line conducted emissions) Software Version declared in the Part 15E UNII-2C Class III submission: -

CANOPY 15.0 (Build 619) AP-DES Software Version declared in the Part 15E UNII-1 and UNII-2A Class III submission: -

CANOPY 15.0.1 (Build 57) AP Software Version declared for DFS test in this Part 15E UNII-2A and UNII-2C Class III submission: -

CANOPY 15.0.1 AP Software Version declared in this Part 15E UNII-1, UNII-2A, UNII-2C and UNII-3 Class III submission: -

CANOPY 15.1 (W) AP Software Version declared in this Part 90Y submission: -

CANOPY 16.0.1.1 (Build DEV-40) AP We further state that there has been no change to the original Software, Distribution and Security Documentation to support this submission We state that software version CANOPY 16.0.1.1 is a progression from previous CANOPY 15.0 software that does not affect the performance of the product as previously tested. There are no changes in the Point software release CANOPY 16.0.1.1 that may affect any of the certification test cases. The customer release software to support compliant operation in the Part 15E UNII-1, UNII-2A and UNII-

2C (with DFS and TPC), UNII-3 and Part 90Y frequency bands will be from release CANOPY 16.2 Thank you for your attention to this matter. Yours faithfully Cambium Networks Ltd Donald W Reid CEng MIET Principal Regulatory Engineer

 

 

Unit B2 Linhay Business Park Eastern Road Ashburton Devon TQ13 7UP United Kingdom 20th November 2017 Element Materials Technology 100 Frobisher Business Park Malvern Worcestershire WR14 1BX UK Subject: Attestation of Compliance to FCC Rules Application for FCC ID: QWP-50450M Applicant: Cambium Networks Ltd Dear Examiner, Attestations:

Cambium Networks Ltd confirms that: -

The PMP 450m products comply with Section 15.407(a)(1)(i) including The maximum e.i.r.p. at any elevation angle above 30 degrees as measured from the horizon must not exceed 125 mW (21 dBm) requirement. Evidence of Compliance:

Calculations and antenna elevation plots upon which the calculations have been made are attached in: -

Annex A Highest EIRP above 30 Elevation Annex B PMP 450m Horizontal and Vertical Elevation at 5.2GHz If you have any questions regarding this application, please feel free to contact me. Sincerely yours, Donald W Reid CEng MIET, MInstLM Principal Regulatory Engineer Cambium Networks Ltd Page 1 Annex A Highest EIRP above 30 Elevation Antenna Plot Nominal angle of antenna lobe with highest gain at elevations above 30 Elevation

(Degrees) EIRP of Highest Antenna Lobe above 30 Elevation

(dBm) EIRP Limit

(dBm) EIRP Pass Margin PMP 450m Horizontal Elevation 32 17.78 21 3.22 Page 2 Annex B PMP 450m Horizontal and Vertical Elevation at 5.2GHz Page 3

 

 

Unit B2 Linhay Business Park Eastern Road Ashburton Devon TQ13 7UP United Kingdom CLASS III PERMISSIVE CHANGE REQUEST Element Materials Technology 100 Frobisher Business Park Malvern Worcestershire WR14 1BX UK Date: 17th November 2017 RE: Class III Permissive Change Request FCC ID: QWP-50450M To Whom It May Concern:

Please be advised that pursuant to FCC Rule 47CFR 2.1043 the manufacturer requests that the above-referenced model be approved for class III permissive change. The reason for the class III change is an update in software to support 40MHz Bandwidth operation in UNII-1, UNII-2A and UNII-2C Frequency Bands. Software support of these frequency bands can only be enabled by software controlled by Cambium Networks. Cambium Networks confirm that the same revision of RF unit hardware has been used in both the original UNII-1, UNII-2A, UNII-2C and UNII-3 submissions and in this class III permissive change request. Cambium Networks confirm that there has been no change to the original Software, Distribution and Security Documentation to support this class III permissive change request. Thank you for your attention to this matter. Yours faithfully Donald W Reid CEng MIET Principal Regulatory Engineer Cambium Networks Ltd Page 1

 

 

Unit B2 Linhay Business Park Eastern Road Ashburton Devon TQ13 7UP United Kingdom CLASS III PERMISSIVE CHANGE REQUEST Element Materials Technology 100 Frobisher Business Park Malvern Worcestershire WR14 1BX UK Date: 13th March 2017 RE: Class III Permissive Change Request FCC ID: QWP-50450M To Whom It May Concern:

Please be advised that pursuant to FCC Rule 47CFR 2.1043 the manufacturer requests that the above-referenced model be approved for class III permissive change. The reason for the class III change is an update in software to support 5MHz Bandwidth operation in UNII-1, UNII-2A, UNII-2C and UNII-3 Frequency Bands. Software support of these frequency bands can only be enabled by software controlled by Cambium Networks. Cambium Networks confirm that the same revision of RF unit hardware has been used in both the original UNII-1, UNII-2A, UNII-2C and UNII-3 submissions and in this class III permissive change request. Cambium Networks confirm that there has been no change to the original Software, Distribution and Security Documentation to support this class III permissive change request. Thank you for your attention to this matter. Yours faithfully Cambium Networks Ltd Donald W Reid CEng MIET Principal Regulatory Engineer Page 1

 

 

9.2 General Set-up Photograph The following photograph shows basic EUT set-up:

Report Number: TRA-029590-21-45-00A RF929 Page 15 of 60

 

 

Unit B2 Linhay Business Park Eastern Road Ashburton Devon TQ13 7UP United Kingdom CLASS III PERMISSIVE CHANGE REQUEST Element Materials Technology 100 Frobisher Business Park Malvern Worcestershire WR14 1BX UK Date: 12th December 2016 RE: Class III Permissive Change Request FCC ID: QWP-50450M To Whom It May Concern:

Please be advised that pursuant to FCC Rule 47CFR 2.1043 the manufacturer requests that the above-referenced model be approved for class III permissive change. The reason for the class III change is an update in software to support operation in UNII-1, UNII-2A and UNII-2C Frequency Bands. Software support of these frequency bands can only be enabled by software controlled by Cambium Networks. Cambium Networks confirm that the same revision of RF unit hardware has been used in both the original UNII-3 submission and in this class III permissive change request. Cambium Networks confirm that there has been no change to the original Software, Distribution and Security Documentation to support this class III permissive change request. In addition the location of the certification label has been changed for ease of manufacture, revised location and label information has been included in this class III submission. Thank you for your attention to this matter. Yours faithfully Cambium Networks Ltd Donald W Reid CEng MIET Principal Regulatory Engineer Page 1

 

 

Chapter 7: Configuration This chapter describes how to use the web interface to configure the 450 Platform link. This chapter contains the following topics:

Preparing for configuration on page 7-72 Connecting to the unit on page 7-73 Using the web interface on page 7-75 Quick link setup on page 7-82 Configuring IP and Ethernet interfaces on page 7-93 Upgrading the software version and using CNUT on page 7-136 General configuration on page 7-140 Configuring Unit Settings page on page 7-157 Setting up time and date on page 7-161 Configuring synchronization on page 7-163 Configuring security on page 7-165 Configuring radio parameters on page 7-192 Setting up SNMP agent on page 7-238 Configuring syslog on page 7-245 Configuring remote access on page 7-251 Monitoring the Link on page 7-252 Configuring quality of service on page 7-255 Installation Color Code on page 7-268 Zero Touch Configuration Using DHCP Option 66 on page 7-269 Configuring Radio via config file on page 7-275 Configuring a RADIUS server on page 7-283 Page 7-71 Chapter 7: Configuration Preparing for configuration Preparing for configuration This section describes the checks to be performed before proceeding with unit configuration and antenna alignment. Safety precautions All national and local safety standards must be followed while configuring the units and aligning the antennas. Warning Ensure that personnel are not exposed to unsafe levels of RF energy. The units start to radiate RF energy as soon as they are powered up. Respect the safety standards defined in Compliance with safety standards on page 4-22, in particular the minimum separation distances. Observe the following guidelines:

Never work in front of the antenna when the ODU is powered. Always power down the PSU before connecting or disconnecting the drop cable from the PSU, ODU or LPU. Regulatory compliance All applicable radio regulations must be followed while configuring the units and aligning the antennas. For more information, refer to Compliance with radio regulations on page 4-31. Caution If the system designer has provided a list of channels to be barred for TDWR radar avoidance, the affected channels must be barred before the units are allowed to radiate on site, otherwise the regulations will be infringed. Attention Si le concepteur du systme a fourni une liste de canaux interdire pour viter les radars TDWR, les cannaux concernes doivent tre interdits avant que les units sont autorises mettre sur le site, sinon la rglementation peut tre enfreinte. Page 7-72 Chapter 7: Configuration Connecting to the unit Connecting to the unit This section describes how to connect the unit to a management PC and power it up. Configuring the management PC Use this procedure to configure the local management PC to communicate with the 450 Platform ODU. Procedure 9 Configuring the management PC 1 Select Properties for the Ethernet port. In Windows 7 this is found in Control Panel

> Network and Internet > Network Connections > Local Area Connection. 2 Select Internet Protocol (TCP/IP):

3 Click Properties. Page 7-73 Chapter 7: Configuration Connecting to the unit 4 Enter an IP address that is valid for the 169.254.X.X network, avoiding 169.254.0.0 and 169.254.1.1. A good example is 169.254.1.3:

5 Enter a subnet mask of 255.255.0.0. Leave the default gateway blank. Connecting to the PC and powering up Use this procedure to connect a management PC and power up the 450 platform ODU. Procedure 10 Connecting to the PC and powering up 1 2 Check that the ODU and PSU are correctly connected. Connect the PC Ethernet port to the LAN port of the PSU using a standard (not crossed) Ethernet cable. 3 Apply mains or battery power to the PSU. The green Power LED should illuminate continuously. 4 After about several seconds, check that the orange Ethernet LED starts with 10 slow flashes. 5 Check that the Ethernet LED then illuminates continuously. Page 7-74 Chapter 7: Configuration Using the web interface Using the web interface This section describes how to log into the 450 Platform Family web interface and use its menus. Logging into the web interface Use this procedure to log into the web interface as a system administrator. Procedure 11 Logging into the web interface 1 Start the web browser from the management PC. 2 Type the IP address of the unit into the address bar. The factory default IP address is 169.254.1.1. Press ENTER. The web interface menu and System Summary page are displayed:

Page 7-75 Chapter 7: Configuration Using the web interface 3 On left hand side of home page, the login information is displayed:

4 Enter Username (factory default username is admin) and Password (factory default password is admin) and click Login. Web GUI 1 1 2 3 Field Name Main Manu Menu Option Description Click an option in side navigation bar (area marked as 1). Multiple options in sub-navigation bars appear Click top sub-navigation bar to choose one configuration page (area marked as 2) Parameter To configure the parameters (e.g. area marked as 3) Press "Save Changes" to confirm and save the changes To reboot the ODU Page 7-76 Chapter 7: Configuration Using the web interface Using the menu options Use the menu navigation bar in the left panel to navigate to each web page. Some of the menu options are only displayed for specific system configurations. Use Table 82 to locate information about using each web page. Table 82 Menu options and web pages Main Menu options Applicable Description menu General Status Session Status Event Log Network Interface Layer 2 Neighbors General IP Radio SNMP cnMaestro Quality of Service (QoS) Security Time module All Viewing General Status on page 9-2 AP, BHM Viewing Session Status on page 9-20 All Interpreting messages in the Event Log on page 9-27 AP, BHM Viewing the Network Interface on page 9-29 All All All All All All All All Viewing the Layer 2 Neighbors on page 9-30 General configuration on page 7-140 Configuring IP and Ethernet interfaces on page 7-93 Configuring radio parameters on page 7-193 Setting up SNMP agent on page 7-238 Configuring cnMaestroTM Connectivity on page 7-277 Configuring quality of service on page 7-255 Configuring security on page 7-165 AP, BHM Setting up time and date Time page of 450 Platform Family -

AP/BHM on page 7-161 Page 7-77 Chapter 7: Configuration Using the web interface Main Menu options Applicable Description menu module VLAN All VLAN configuration for PMP on page DiffServ Protocol Filtering Syslog Unit Setting Scheduler 7-115 VLAN configuration for PTP on page 7-125 IPv4 and IPv6 Prioritization on page 7-

132 Filtering protocols and ports on page 7-133 Configuring syslog on page 7-245 Configuring Unit Settings page on page 7-157 Viewing the Scheduler statistics on page 9-31 All All All All All Registration Failures AP, BHM Viewing list of Registration Failures Bridge Control Block Bridging Table Ethernet Radio VLAN Data VC All All All All All All statistics on page 9-33 Interpreting Bridge Control Block statistics on page 9-59 Interpreting Bridging Table statistics on page 9-34 Interpreting Ethernet statistics on page 9-36 Interpreting RF Control Block statistics on page 9-39 Interpreting VLAN statistics on page 9-41 Interpreting Data VC statistics on page 9-43 Throughput AP, BHM Interpreting Throughput statistics on page 9-45 Filter ARP Overload SM Interpreting Filter statistics on page 9-

52 SM All Viewing ARP statistics on page 9-53 Interpreting Overload statistics on page 9-48 Page 7-78 Chapter 7: Configuration Using the web interface Main Menu options Applicable Description menu module Syslog Statistics All Interpreting syslog statistics on page 9-65 Translation Table SM Interpreting Translation Table statistics on page 9-35 DHCP Relay NAT Stats NAT DHCP Pass Through Statistics Sync Status PPPoE SM Interpreting DHCP Relay statistics on page 9-50 SM SM AP AP Viewing NAT statistics on page 9-53 Viewing NAT DHCP Statistics on page 9-55 Interpreting Pass Through Statistics on page 9-62 Interpreting Sync Status statistics on page 9-56 SM Interpreting PPPoE Statistics for Customer Activities on page 9-57 SNMPv3 Statistics All Interpreting SNMPv3 Statistics on Frame Utilization Link Capacity Test Spectrum Analyzer Remote Spectrum Analyzer All All All page 9-63 Interpreting SNMPv3 Statistics on page 9-63 Using the Link Capacity Test tool on page 8-21 Spectrum Analyzer tool on page 8-3 Remote Spectrum Analyzer tool on page 8-12 AP/BHM Evaluation SM, BHS Using AP Evaluation tool on page 8-30 Using BHM Evaluation tool on page 8-

34 Subscriber Configuration AP Using the Subscriber Configuration tool on page 8-43 OFDM Frame Calculator AP, BHM Using the OFDM Frame Calculator tool on page 8-38 BER results Alignment Tool SM Using BER Results tool on page 8-49 SM, BHS Using the Alignment Tool on page 8-

15 Page 7-79 Chapter 7: Configuration Using the web interface Main Menu options Applicable Description menu Link Status Sessions Change User Setting Add user Delete User User Quick Start Region Settings module AP AP Using the Link Status tool on page 8-

44 Using the Sessions tool on page 8-50 Changing a User Setting on page 7-

167 Adding a User for Access to a module on page 7-166 Deleting a User from Access to a module on page 7-167 Users account on page 7-168 AP, BHM Quick link setup on page 7-82 AP, BHM Quick link setup on page 7-82 Radio Carrier Frequency AP, BHM Quick link setup on page 7-82 Synchronization LAN IP Address AP, BHM Quick link setup on page 7-82 AP, BHM Quick link setup on page 7-82 Review and Save Configuration AP, BHM Quick link setup on page 7-82 Quick Status Spectrum Results (PDA) Information BHM Evaluation AIM SM SM SM SM SM The PDA web-page includes 320 x 240 pixel formatted displays of information important to installation and alignment for installers using legacy PDA devices. All device web pages are compatible with touch devices such as smart phones and tablets. Page 7-80 Chapter 7: Configuration Using the web interface Main Menu options Applicable Description menu Copyright Notices All The Copyright web-page displays module pertinent device copyright information. All Page 7-81 Chapter 7: Configuration Quick link setup Quick link setup This section describes how to use the Quick Start Wizard to complete the essential system configuration tasks that must be performed on a PMP/PTP configuration. Note If the IP address of the AP or BHM is not known, See Radio recovery mode on page 1-

24. Initiating Quick Start Wizard Applicable products PMP : AP PTP: BHM To start with Quick Start Wizard: after logging into the web management interface click the Quick Start button on the left side of main menu bar. The AP/BHM responds by opening the Quick Start page. Figure 99 Disarm Installation page (top and bottom of page shown) Quick Start is a wizard that helps you to perform a basic configuration that places an AP/BHM into service. Only the following parameters must be configured:

Region Code RF Carrier Frequency Synchronization LAN (Network) IP Address Page 7-82 Chapter 7: Configuration Quick link setup In each Quick Start page, you can specify the settings to satisfy the requirements of the network. review the configuration selected. save the configuration to non-volatile memory. Procedure 12 Quick start wizard 1 2 At the bottom of the Quick Start tab, click the Go To Next Page button. From the pull-down menu, select the region in which the AP will operate. Figure 100 Regional Settings tab of AP/BHM 3 Click the Go To Next Page button. Page 7-83 Chapter 7: Configuration Quick link setup 4 From the pull-down menu, select a frequency for the test. Figure 101 Radio Carrier Frequency tab of AP/BHM 5 Click the Go To Next Page button. Page 7-84 Chapter 7: Configuration Quick link setup 6 At the bottom of this tab, select Generate Sync Signal. Figure 102 Synchronization tab of AP/BHM 7 Click the Go To Next Page button. Page 7-85 Chapter 7: Configuration Quick link setup 8 At the bottom of the IP address configuration tab, either specify an IP Address, a Subnet Mask, and a Gateway IP Address for management of the AP and leave the DHCP state set to Disabled. set the DHCP state to Enabled to have the IP address, subnet mask, and gateway IP address automatically configured by a domain name server (DNS). Figure 103 LAN IP Address tab of the AP/BHM Note Cambium encourages you to experiment with the interface. Unless you save a configuration and reboot the AP after you save the configuration, none of the changes are affected. 9 Click the Go To Next Page => button. Page 7-86 Chapter 7: Configuration Quick link setup 10 Ensure that the initial parameters for the AP are set as you intended. Figure 104 Review and Save Configuration tab of the AP/BHM 11 Click the Save Changes button. 12 Click the Reboot button. RESULT: The AP responds with the message Reboot Has Been Initiated Page 7-87 Chapter 7: Configuration Quick link setup 13 Wait until the indicator LEDs are not red. 14 Trigger your browser to refresh the page until the AP redisplays the General Status tab. 15 Wait until the red indicator LEDs are not lit. Configuring time settings Applicable products PMP : AP PTP: BHM To proceed with the test setup, click the Configuration link on the left side of the General Status page. When the AP responds by opening the Configuration page to the General page, click the Time tab. Figure 105 Time tab of the AP/BHM To have each log in the AP/BHM correlated to a meaningful time and date, either a reliable network element must pass time and date to the AP/BHM or you must set the time and date whenever a power cycle of the AP/BHM has occurred. A network element passes time and date in any of the following scenarios:

A connected CMM4 passes time and date (GPS time and date, if received). A separate NTP server is addressable from the AP/BHM. If the AP/BHM should obtain time and date from a CMM4, or a separate NTP server, enter the IP address of the CMM4 or NTP server on this tab. To force the AP/BHM to obtain time and date before the first (or next) 15-minute interval query of the NTP server, click Get Time through NTP. Page 7-88 Chapter 7: Configuration Quick link setup If you enter a time and date, the format for entry is Figure 106 Time and date entry formats Time :

hh Date :

MM

/

/

mm dd

/

/

ss yyyy where hh represents the two-digit hour in the range 00 to 24 mm represents the two-digit minute ss represents the two-digit second MM represents the two-digit month dd represents the two-digit day yyyy represents the four-digit year Proceed with the time setup as follows. Procedure 13 Entering AP/BHM time setup information 1 2 Enter the appropriate information in the format shown above. Then click the Set Time and Date button. Note The time displayed at the top of this page is static unless your browser is set to automatically refresh Powering the SM/BHS for test Procedure 14 Powering the SM/BHS for test 1 In one hand, securely hold the top (larger shell) of the SM/BHS. With the other hand, depress the lever in the back of the base cover (smaller shell). Remove the base cover. 2 3 4 5 Plug one end of a CAT 5 Ethernet cable into the SM PSU port Plug the other end of the Ethernet cable into the jack in the pig tail that hangs from the power supply Roughly aim the SM/BHS toward the AP/BHM Plug the power supply into an electrical outlet Warning From this point until you remove power from the AP/BHM, stay at least as far from the AP/BHM as the minimum separation distance specified in Calculated distances and power compliance margins. 6 Repeat the foregoing steps for each SM/BHS that you wish to include in the test. Page 7-89 Chapter 7: Configuration Quick link setup Viewing the Session Status of the AP/BHM to determine test registration Once the SMs/BHS under test are powered on, return to the computing device to determine if the SM/BHS units have registered to the AP/BHM. Note In order for accurate power level readings to be displayed, traffic must be present on the radio link. The Session Status tab provides information about each SM/BHS that has registered to the AP/BHM. This information is useful for managing and troubleshooting a system. All information that you have entered in the Site Name field of the SM/BHS displays in the Session Status tab of the linked AP/BHM. The Session Status tab also includes the current active values on each SM( or BHS) (LUID) for MIR, and VLAN, as well as the source of these values (representing the SM/BHS itself, Authentication Server, or the AP/BHM and cap, if anyfor example, APCAP as shown above).. As an SM/BHS registers to the AP/BHM, the configuration source that this page displays for the associated LUID may change. After registration, however, the displayed source is stable and can be trusted. Idle subscribers may be included or removed from the session status display by enabling or disabling, respectively, the Show Idle Sessions parameter. Enabling or disabling this parameter only affects the GUI display of subscribers, not the registration status. The SessionStatus.xml hyperlink allows user to export session status page from web management interface of AP/BHM. The session status page will be exported in xml file. Page 7-90 Chapter 7: Configuration Quick link setup Procedure 15 Viewing the AP Session Status page 1 On the AP web management GUI, navigate to Home, Session Status:

Figure 107 Session Status tab of AP Note Session status page for BHM is same as AP. 2 Verify that for each SM (or BHS) MAC address (printed on the SM/BHS housing) the AP/BHM has established a registered session by verifying the State status of each entry. The Session Status page of the AP/BHM is explained in Table 83. Page 7-91 Chapter 7: Configuration Quick link setup Table 83 Session Status Attributes AP Attribute Meaning Show Idle Sessions Idle subscribers may be included or removed from the session status display by enabling or disabling, respectively, the Show Idle Sessions parameter. Enabling or disabling this parameter only affects the GUI display of subscribers, not the registration status. Last Session Counter This field displays date and time stamp of last session counter reset. Reset Last Time Idle SMs This field displays date and time stamp of last Idle SMs Removed. On Removed click of Remove Idle SMs button, all the SMs which are in Idle state are flushed out. Data See Exporting Session Status page of AP/BHM on page 7-266 Device tab See Device tab on page 9-20 Session tab See Session tab on page 9-21 Power tab See Power tab on page 9-23 Configuration tab See Configuration tab on page 9-24 Page 7-92 Chapter 7: Configuration Configuring IP and Ethernet interfaces Configuring IP and Ethernet interfaces This task consists of the following sections:

Configuring the IP interface on page 7-94 Auxiliary port on page 7-97 NAT, DHCP Server, DHCP Client and DMZ on page 7-98 IP interface with NAT disabled on page 7-103 IP interface with NAT enabled on page NAT tab with NAT disabled on page 7-106 NAT tab with NAT enabled on page 7-109 NAT DNS Considerations on page 7-114 DHCP BHS on page 7-115 VLAN configuration for PMP on page 7-115 VLAN page of AP on page 7-118 VLAN page of SM on page 7-121 VLAN Membership tab of SM on page 7-125 VLAN configuration for PTP on page 7-125 NAT Port Mapping tab - SM on page 7-114 Page 7-93 Chapter 7: Configuration Configuring IP and Ethernet interfaces Configuring the IP interface The IP interface allows users to connect to the 450 Platform Family web interface, either from a locally connected computer or from a management network. Applicable products PMP : AP SM PTP: BHM BMS To configure the IP interface, follow these instructions:

Procedure 16 Configuring the AP/BHM IP interface 1 Select menu option Configuration > IP. The LAN configuration page is displayed:

2 3 4 Update IP Address, Subnet Mask and Gateway IP Address to meet network requirements (as specified by the network administrator). Review the other IP interface attributes and update them, if necessary (see Table 84 IP interface attributes). Click Save. Reboot Required message is displayed:

5 Click Reboot. The IP page of AP/SM/BHM/BHS is explained in Table 84. Page 7-94 Chapter 7: Configuration Configuring IP and Ethernet interfaces Table 84 IP interface attributes Attribute Meaning IP Address Internet Protocol (IP) address. This address is used by family of Internet protocols to uniquely identify this unit on a network. Subnet Mask Defines the address range of the connected IP network. The IP address of a computer on the current network that acts as a gateway. A gateway acts as an entrance and exit to packets from and to other networks. DHCP state If Enabled is selected, the DHCP server automatically assigns the IP configuration (IP address, subnet mask, and gateway IP address) and the values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable (read only), in the Network Interface tab of the Home page. DNS IP Address Canopy devices allow for configuration of a preferred and alternate DNS server IP address either automatically or manually. Devices must set DNS server IP address manually when DHCP is disabled for the management interface of the device. DNS servers may be configured automatically from the DHCP response when DHCP is enabled for the management interface of the device. Optionally devices may be configured to set the DNS server IP address manually when DHCP is enabled for the management interface. The default DNS IP addresses are 0.0.0.0 when configured manually. Preferred DNS The first address used for DNS resolution. Server Alternate DNS If the Preferred DNS server cannot be reached, the Alternate DNS Server Server is used. Domain Name The operators management domain name may be configured for DNS. The domain name configuration can be used for configuration of the servers in the operators network. The default domain name is example.com, and is only used if configured as such. Page 7-95 Chapter 7: Configuration Configuring IP and Ethernet interfaces LAN2 Network It is recommended not to change this parameter from the default Interface AP/BHM private IP address of 192.168.101.1. A /24 CIDR subnet is used to Configuration (Radio communicate with each of the SMs/BHS that are registered. The AP/BHM Private Interface) IP uses a combination of the private IP and the LUID (logical unit ID) of the Address SM/BHS. It is only displayed for AP and BHM. Table 85 SM/BHS private IP and LUID SM/BHS LUID Private IP First SM/BHS registered Second SM/BHS registered 2 3 192.168.101.2 192.168.101.3 Page 7-96 Chapter 7: Configuration Configuring IP and Ethernet interfaces Auxiliary port An additional Ethernet port labeled Aux for Auxiliary port is implemented for downstream traffic. This feature is supported only for PTP/PMP 450i ODUs. To enable the Aux port, follow these instructions:

Procedure 17 Enabling Aux port interface 1 Select menu option Configuration > IP > Aux Network Interface tab.:

Click Enable button of Aux Ethernet Port parameter to enable Aux Ethernet port Click Enable button of Aux Ethernet Port PoE parameter to enable Aux port PoE out. Click Save. Reboot Required message is displayed. Click Reboot. 2 3 4 5 Table 86 Aux port attributes Attribute Meaning Aux Ethernet Port Enabled: Data is enabled for Auxiliary port Disabled: Data is disabled for Auxiliary port Aux Ethernet Port Enabled: PoE out is enable for Auxiliary port PoE Disabled: PoE out is disabled for Auxiliary port By disabling this feature, the data at the Auxiliary port will be disabled. Page 7-97 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT, DHCP Server, DHCP Client and DMZ Applicable products PMP :

SM The system provides NAT (Network Address Translation) for SMs in the following combinations of NAT and DHCP (Dynamic Host Configuration Protocol):

NAT Disabled NAT with DHCP Client (DHCP selected as the Connection Type of the WAN interface) and DHCP Server NAT with DHCP Client(DHCP selected as the Connection Type of the WAN interface) NAT with DHCP Server NAT without DHCP NAT NAT isolates devices connected to the Ethernet or wired side of a SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic

(separate from its address for management), terminates transport traffic and allows you to assign a range of IP addresses to devices that are connected to the Ethernet or wired side of the SM. In the Cambium system, NAT supports many protocols, including HTTP, ICMP (Internet Control Message Protocols), and FTP (File Transfer Protocol). For virtual private network (VPN) implementation, L2TP over IPSec (Level 2 Tunneling Protocol over IP Security) and PPTP (Point to Point Tunneling Protocol) are supported. Note When NAT is enabled, a reduction in throughput is introduced in the system (due to processing overhead). DHCP DHCP enables a device to be assigned a new IP address and TCP/IP parameters, including a default gateway, whenever the device reboots. Thus DHCP reduces configuration time, conserves IP addresses, and allows modules to be moved to a different network within the Cambium system. In conjunction with the NAT features, each SM provides the following:

A DHCP server that assigns IP addresses to computers connected to the SM by Ethernet protocol. A DHCP client that receives an IP address for the SM from a network DHCP server. DMZ In conjunction with the NAT features, a DMZ (Demilitarized Zone) allows the allotment of one IP address behind the SM for a device to logically exist outside the firewall and receive network traffic. The first three octets of this IP address must be identical to the first three octets of the NAT private IP address. Page 7-98 Chapter 7: Configuration Configuring IP and Ethernet interfaces A DHCP server that assigns IP addresses to computers connected to the SM by Ethernet protocol. A DHCP client that receives an IP address for the SM from a network DHCP server. NAT Disabled The NAT Disabled implementation is illustrated in Figure 108. Figure 108 NAT disabled implementation NAT with DHCP Client and DHCP Server The NAT with DHCP Client and DHCP server is illustrated in Figure 109. Page 7-99 Chapter 7: Configuration Configuring IP and Ethernet interfaces Figure 109 NAT with DHCP client and DHCP server implementation NAT with DHCP Client Figure 110 NAT with DHCP client implementation Page 7-100 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT with DHCP Server Figure 111 NAT with DHCP server implementation NAT without DHCP Figure 112 NAT without DHCP implementation Page 7-101 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT and VPNs VPN technology provides the benefits of a private network during communication over a public network. One typical use of a VPN is to connect employees remotely (who are at home or in a different city), with their corporate network through a public Internet. Any of several VPN implementation schemes is possible. By design, NAT translates or changes addresses, and thus interferes with a VPN that is not specifically supported by a given NAT implementation. With NAT enabled, SM supports L2TP over IPSec (Level 2 Tunneling Protocol over IP Security) VPNs and PPTP (Point to Point Tunneling Protocol) VPNs. With NAT disabled, SM supports all types of VPNs. Page 7-102 Chapter 7: Configuration Configuring IP and Ethernet interfaces IP interface with NAT disabled - SM The IP page of SM with NAT disabled is explained in Table 87. Table 87 IP attributes - SM with NAT disabled Attribute Meaning IP Address Enter the non-routable IP address to associate with the Ethernet connection on this SM. (The default IP address from the factory is 169.254.1.1.) If you forget this parameter, you must both:

physically access the module. use recovery mode to access the module configuration parameters at 169.254.1.1. See Radio recovery mode on page 1-24 Note Note or print the IP settings from this page. Ensure that you can readily associate these IP settings both with the module and with the other data that you store about the module. Network Specify whether the IP address of the SM must be visible to only a Accessibility device connected to the SM by Ethernet (Local) or be visible to the AP/BHM as well (Public). Subnet Mask Enter an appropriate subnet mask for the SM to communicate on the network. The default subnet mask is 255.255.0.0. Gateway IP Address Enter the appropriate gateway for the SM to communicate with the network. The default gateway is 169.254.0.0. DHCP state If you select Enabled, the DHCP server automatically assigns the IP configuration (IP address, subnet mask, and gateway IP address) and the values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable, but not settable, in the Network Interface tab of the Home page. Page 7-103 Chapter 7: Configuration Configuring IP and Ethernet interfaces In this tab, DHCP State is settable only if the Network Accessibility parameter in the IP tab is set to Public. This parameter is also settable in the NAT tab of the Configuration web page, but only when NAT is enabled. If the DHCP state parameter is set to Enabled in the Configuration > IP sub-menu of the SM/BHS, do not check the BootpClient option for Packet Filter Types in its Protocol Filtering tab, because doing so can block the DHCP request. (Filters apply to all packets that leave the SM via its RF interface, including those that the SM itself generates.) If you want to keep DHCP enabled and avoid the blocking scenario, select the Bootp Server option instead. This will result in responses being appropriately filtered and discarded. DHCP DNS IP Canopy devices allow for configuration of a preferred and alternate DNS Address server IP address either automatically or manually. Devices must set DNS server IP address manually when DHCP is disabled for the management interface of the device. DNS servers may be configured automatically from the DHCP response when DHCP is enabled for the management interface of the device. Optionally devices may be configured to set the DNS server IP address manually when DHCP is enabled for the management interface. The default DNS IP addresses are 0.0.0.0 when configured manually. Preferred DNS The first DNS server used for DNS resolution. Server Alternate DNS The second DNS server used for DNS resolution. Server Domain Name The operators management domain name may be configured for DNS. The domain name configuration can be used for configuration of the servers in the operators network. The default domain name is example.com, and is only used if configured as such. Page 7-104 Chapter 7: Configuration Configuring IP and Ethernet interfaces IP interface with NAT enabled - SM The IP page of SM with NAT enabled is explained in Table 88. Table 88 IP attributes - SM with NAT enabled Attribute Meaning IP Address Assign an IP address for SM/BHS management through Ethernet access to the SM/BHS. Set only the first three bytes. The last byte is permanently set to 1. This address becomes the base for the range of DHCP-assigned addresses. Subnet Mask Assign a subnet mask of 255.255.255.0 or a more restrictive subnet mask. Set only the last byte of this subnet mask. Each of the first three bytes is permanently set to 255. Page 7-105 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT tab with NAT disabled - SM The NAT tab of SM with NAT disabled is explained in Table 89. Table 89 NAT attributes - SM with NAT disabled Page 7-106 Chapter 7: Configuration Configuring IP and Ethernet interfaces Attribute Meaning NAT Enable/Disable This parameter enables or disables the Network Address Translation

(NAT) feature for the SM. NAT isolates devices connected to the Ethernet or wired side of a SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic separate from its address for management, terminates transport traffic, and allows you to assign a range of IP addresses to devices that are connected to the Ethernet or wired side of the SM. When NAT is enabled, VLANs are not supported on the wired side of that SM. You can enable NAT in SMs within a sector where VLAN is enabled in the AP/BHM, but this may constrain network design. IP Address This field displays the IP address for the SM. DHCP Server will not automatically assign this address when NAT is disabled. Subnet Mask This field displays the subnet mask for the SM. DHCP Server will not automatically assign this address when NAT is disabled. Gateway IP Address This field displays the gateway IP address for the SM. DHCP Server will not automatically assign this address when NAT is disabled. ARP Cache Timeout If a router upstream has an ARP cache of longer duration (as some use 30 minutes), enter a value of longer duration than the router ARP cache. The default value of this field is 20 minutes. TCP Session Where a large network exists behind the SM, you can set this parameter Garbage Timeout to lower than the default value of 120 minutes. This action makes additional resources available for greater traffic than the default value accommodates. UDP Session You may adjust this parameter in the range of 1 to 1440 minutes, based Garbage Timeout on network performance. The default value of this parameter is 4 minutes. Translation Table Total number of minutes that have elapsed since the last packet transfer Size between the connected device and the SM/BHS. Page 7-107 Chapter 7: Configuration Configuring IP and Ethernet interfaces Note When NAT is disabled, the following parameters are not required to be configurable:

WAN Inter face > Connection Type, IP Address, Subnet Mask, Gateway IP address LAN Interface > IP Address LAN DHCP Server > DHCP Server Enable/Disable, DHCP Server Lease Timeout, Number of IPs to Lease, DNS Server Proxy, DNS IP Address, Preferred DNS IP address, Alternate DNS IP address Remote Management Interface > Remote Management Interface, IP address, Subnet Mask, DHCP DNS IP Address, Preferred DNS Server, Alternate DNS Server, Domain Name NAT Protocol Parameters > ARP Cache Timeout, TCP Session Garbage Timeout, UDP Session Garbage Timeout, Translation Table Size Page 7-108 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT tab with NAT enabled - SM The NAT tab of SM with NAT enabled is explained in Table 90. Table 90 NAT attributes - SM with NAT enabled Page 7-109 Chapter 7: Configuration Configuring IP and Ethernet interfaces Attribute Meaning NAT Enable/Disable This parameter enables or disabled the Network Address Translation

(NAT) feature for the SM. NAT isolates devices connected to the Ethernet or wired side of a SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic separate from its address for management, terminates transport traffic, and allows you to assign a range of IP addresses to devices that are connected to the Ethernet or wired side of the SM. When NAT is enabled, VLANs are not supported on the wired side of that SM. You can enable NAT in SMs within a sector where VLAN is enabled in the AP, but this may constrain network design. WAN Interface The WAN interface is the RF-side address for transport traffic. Connection Type This parameter may be set to Static IPwhen this is the selection, all three parameters (IP Address, Subnet Mask, and Gateway IP Address) must be properly populated. DHCPwhen this is the selection, the information from the DHCP server configures the interface. PPPoEwhen this is the selection, the information from the PPPoE server configures the interface. Subnet Mask If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the subnet mask of the SM for RF transport traffic. Gateway IP Address If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the gateway IP address for the SM for RF transport traffic. Reply to Ping on By default, the radio interface does not respond to pings. If you use a WAN Interface management system (such as WM) that will occasionally ping the SM, set this parameter to Enabled. LAN Interface The LAN interface is both the management access through the Ethernet port and the Ethernet-side address for transport traffic. When NAT is enabled, this interface is redundantly shown as the NAT Network Interface Configuration on the IP tab of the Configuration web page in the SM. IP Address Assign an IP address for SM/BHS management through Ethernet access to the SM. This address becomes the base for the range of DHCP-

assigned addresses. Subnet Mask Assign a subnet mask of 255.255.255.0 or a more restrictive subnet mask. Set only the last byte of this subnet mask. Each of the first three bytes is permanently set to 255. DMZ Enable Either enable or disable DMZ for this SM/BHS. Page 7-110 Chapter 7: Configuration Configuring IP and Ethernet interfaces DMZ IP Address If you enable DMZ in the parameter above, set the last byte of the DMZ host IP address to use for this SM when DMZ is enabled. Only one such address is allowed. The first three bytes are identical to those of the NAT private IP address. Ensure that the device that receives network traffic behind this SM is assigned this address. The system provides a warning if you enter an address within the range that DHCP can assign. DHCP Server This is the server (in the SM) that provides an IP address to the device DHCP Server Enable/Disable connected to the Ethernet port of the SM. Select either Enabled or Disabled. Enable to:

Allow this SM to assign IP addresses, subnet masks, and gateway IP addresses to attached devices. Assign a start address for DHCP. Designate how many IP addresses may be temporarily used (leased). Disable to:

Restrict SM/BHS from assigning addresses to attached devices. DHCP Server Lease Based on network performance, enter the number of days between Timeout when the DHCP server assigns an IP address and when that address expires. The range of values for this parameter is 1 to 30 days. The default value is 30 days. DHCP Start IP If you enable DHCP Server below, set the last byte of the starting IP address that the DHCP server assigns. The first three bytes are identical to those of the NAT private IP address. Number of IPs to Enter how many IP addresses the DHCP server is allowed to assign. The Lease default value is 50 addresses. DNS Server Proxy This parameter enables or disables advertisement of the SM/BHS as the DNS server. On initial boot up of a SM with the NAT WAN interface configured as DHCP or PPPoE, the SM module will not have DNS information immediately. With DNS Server Proxy disabled, the clients will renew their lease about every minute until the SM has the DNS information to give out. At this point the SM will go to the full configured lease time period which is 30 days by default. With DNS Server Proxy enabled, the SM will give out full term leases with its NAT LAN IP as the DNS server. DNS IP Address Select either:

Obtain Automatically to allow the system to set the IP address of the DNS server or Set Manually to enable yourself to set both a preferred and an alternate DNS IP address. Preferred DNS IP Enter the preferred DNS IP address to use when the DNS IP Address Address parameter is set to Set Manually. Page 7-111 Chapter 7: Configuration Configuring IP and Ethernet interfaces Alternate DNS IP Enter the DNS IP address to use when the DNS IP Address parameter is Address set to Set Manually and no response is received from the preferred DNS IP address. Remote To offer greater flexibility in IP address management, the NAT-enabled Management SMs configured WAN Interface IP address may now be used as the Interface device Remote Management Interface (unless the SMs PPPoE client is set to Enabled) Disable: When this interface is set to Disable, the SM is not directly accessible by IP address. Management access is only possible through either the LAN (Ethernet) interface or a link from an AP web page into the WAN (RF-side) interface. Enable (Standalone Config): When this interface is set to Enable

(Standalone Config), to manage the SM/BHS the device must be accessed by the IP addressing information provided in the Remote Configuration Interface section. Note When configuring PPPoE over the link, use this configuration option (PPPoE traffic is routed via the IP addressing specified in section Remote Configuration Interface). Enable (Use WAN Interface): When this interface is set to Enable (Use WAN Interface), the Remote Configuration Interface information is greyed out, and the SM is managed via the IP addressing specified in section WAN Interface). Note When using this configuration, the ports defined in section Configuration, Port Configuration are consumed by the device. For example, if FTP Port is configured as 21 by the SM, an FTP server situated below the SM must use a port other than 21. This also applies to DMZ devices; any ports specified in section Configuration, Port Configuration will not be translated through the NAT, they is consumed by the devices network stack for management. Connection Type This parameter can be set to:

Static IPwhen this is the selection, all three parameters (IP Address, Subnet Mask, and Gateway IP Address) must be properly populated. DHCPwhen this is the selection, the information from the DHCP server configures the interface. IP Address If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the IP address of the SM for RF management traffic. Subnet Mask If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the subnet mask of the SM for RF management traffic. Page 7-112 Chapter 7: Configuration Configuring IP and Ethernet interfaces Gateway IP Address If Static IP is set as the Connection Type of the WAN interface, then this parameter configures the gateway IP address for the SM for RF management traffic. Note or print the IP settings from this page. Ensure that you can readily associate these IP settings both with the module and with the other data that you store about the module. DHCP DNS IP Select either:

Address Obtain Automatically to allow the system to set the IP address of the DNS server. or Set Manually to enable yourself to set both a preferred and an alternate DNS IP address. Preferred DNS Enter the preferred DNS IP address to use when the DNS IP Address Server parameter is set to Set Manually. Alternate DNS Enter the DNS IP address to use when the DNS IP Address parameter is Server set to Set Manually and no response is received from the preferred DNS IP address. Domain Name Domain Name to use for management DNS configuration. This domain name may be concatenated to DNS names used configured for the remote configuration interface. ARP Cache Timeout If a router upstream has an ARP cache of longer duration (as some use 30 minutes), enter a value of longer duration than the router ARP cache. The default value of this field is 20 (minutes). TCP Session Where a large network exists behind the SM, you can set this parameter Garbage Timeout to lower than the default value of 120 (minutes). This action makes additional resources available for greater traffic than the default value accommodates. UDP Session You may adjust this parameter in the range of 1 to 1440 minutes, based Garbage Timeout on network performance. The default value of this parameter is 4

(minutes). Page 7-113 Chapter 7: Configuration Configuring IP and Ethernet interfaces NAT DNS Considerations - SM SM DNS behavior is different depending on the accessibility of the SM. When NAT is enabled the DNS configuration that is discussed in this document is tied to the RF Remote Configuration Interface, which must be enabled to utilize DNS Client functionality. Note that the WAN DNS settings when NAT is enabled are unchanged with the addition of the management DNS feature discussed in this document. Table 91 SM DNS Options with NAT Enabled NAT Management Interface DHCP Status DNS Status Configuration Accessibility RF Remote N/A DNS Disabled Management Interface Disabled NAT Enabled RF Remote DHCP Disabled DNS Static Configuration Management Interface Enabled DHCP Enabled DNS from DHCP or DNS Static Configuration NAT Port Mapping tab - SM The NAT Port Mapping tab of the SM is explained in Table 92. Table 92 NAT Port Mapping attributes - SM Attribute Meaning Port Map 1 to 10 Separate parameters allow you to distinguish NAT ports from each other by assigning a unique combination of port number, protocol for traffic through the port, and IP address for access to the port Page 7-114 Chapter 7: Configuration Configuring IP and Ethernet interfaces DHCP BHS Applicable products PTP: BHM DHCP enables a device to be assigned a new IP address and TCP/IP parameters, including a default gateway, whenever the device reboots. Thus DHCP reduces configuration time, conserves IP addresses, and allows modules to be moved to a different network within the Cambium system. In conjunction with the NAT features, each BHS provides:

A DHCP server that assigns IP addresses to computers connected to the BHS by Ethernet protocol. A DHCP client that receives an IP address for the BHS from a network DHCP server. Reconnecting to the management PC If the IP Address, Subnet Mask and Gateway IP Address of the unit have been updated to meet network requirements, then reconfigure the local management PC to use an IP address that is valid for the network. See Configuring the management PC on page 7-73. Once the unit reboots, log in using the new IP address. See Logging into the web interface on page 7-75. VLAN configuration for PMP Applicable products PMP : AP SM VLAN Remarking VLAN Remarking feature allows the user to change the VLAN ID and priority of both upstream and downstream packets at the Ethernet Interface. The remarking configuration is available for:

1. VLAN ID re-marking 2. 802.1p priority re-marking Note For Q-in-Q VLAN tagged frame, re-marking is performed on the outer tag. Page 7-115 Chapter 7: Configuration Configuring IP and Ethernet interfaces VLAN ID Remarking SM supports the ability to re-mark the VLAN ID on both upstream and downstream VLAN frames at the Ethernet interface. For instance, a configuration can be added to re-mark VLAN ID x to VLAN ID y as shown in Table 93. AP does not support VLAN ID remarking. Table 93 VLAN Remarking Example VLAN frame direction Remarking SM receives VLAN ID x frame at the Ethernet interface, checks the configuration and re-marks to VLAN ID y. So VLAN ID y frame Upstream comes out of APs Ethernet interface. When SM re-marks, a dynamic entry in VLAN membership table for y is added to allow reception of VLAN ID y downstream packet. AP receives VLAN ID y frame at the Ethernet interface and sends to SM. SM accepts the frame as it has an entry in the membership table and re-marks to VLAN ID x. This reverse re- marking is necessary because the downstream devices do not know of re-

marking and are expecting VLAN x frames. This remarking is done just before sending the packet out on Ethernet interface. Downstream 802.1P Remarking AP/BHM and SM/BHS allow re-marking of 802.1p priority bits for the frames received at the Ethernet interface. Priority bits are not re-marked for the packets sent out of Ethernet interface

(reverse direction). Configuration must be added at SM/BHS for upstream frames and at AP/BHM for downstream frames. VLAN Priority Bits configuration VLAN Priority Bits Configuration feature allows the user to configure the three 802.1p bits upon assigning VLAN to an ingress packet. The priority bits configuration is available for:

Default Port VID Provider VID MAC Address mapped Port VID Management VID Default Port VID This VID is used for untagged frames and will correspond to the Q-Tag for 802.1Q frames (if VLAN Port Type is Q), or the C-Tag for 802.1ad frames (if the VLAN Port Type is QinQ). The priority bits used in the Q-tag/C-tag are configurable. The configuration can be:

Page 7-116 Chapter 7: Configuration Configuring IP and Ethernet interfaces Promote IPv4/IPv6 priority The priority in the IP header is copied to the Q-tag/C-tag. Define priority Specify the priority in the range of 0 to 7. This value is used as priority in the Q-tag/C-tag. MAC Address Mapped VID If a packet arrives at the SM/BHS that is sourced from a device whose MAC address is in the table, then the corresponding VID is used for that frames Q-tag (Q port) or C-tag (QinQ port). The priority bits used in the Q-tag/C-tag are configurable similar to default port VID. Provider VID The provider VID is used for the S-tag. The priority bits used in the S-tag are configurable similar to default port VID. Provider VID has an extra priority configuration:

Copy inner tag 802.1p priority The priority in the C-tag is copied to the S-tag. Management VID This VID is used to communicate with AP/BHM and SM/BHS for management purposes. The priority bits used in the Q-tag are configurable similar to default port VID. Use APs Management VID for ICC connected SM This feature allows the SM to use the APs management VLAN ID when the SM is registered to the AP via ICC. This feature is useful for the customer who uses a different management VID for the SM and AP and Zero Touch feature is enabled for configuration. This parameter may be accessed via the Configuration > VLAN page on the APs web management interface. Page 7-117 Chapter 7: Configuration VLAN page of AP The VLAN tab of the AP/BHM is explained in Table 94. Table 94 AP/BHM VLAN tab attributes Configuring IP and Ethernet interfaces Attribute Meaning VLAN Specify whether VLAN functionality for the AP and all linked SMs must

(Enabled) or may not (Disabled) be allowed. The default value is Disabled. Always use Local Enable this option before you reboot this AP as a SM to use it to perform VLAN Config spectrum analysis. Once the spectrum analysis completes, disable this option before you reboot the module as an AP, Allow Frame Types Select the type of arriving frames that the AP must tag, using the VID that is stored in the Untagged Ingress VID parameter. The default value is All Frames. Dynamic Learning Specify whether the AP must (Enabled) or not (Disabled) add the VLAN IDs (VIDs) of upstream frames to the VID table. (The AP passes frames with VIDs that are stored in the table both upstream and downstream.). The default value is Enabled. Page 7-118 Chapter 7: Configuration Configuring IP and Ethernet interfaces VLAN Aging Timeout Specify how long the AP must keep dynamically learned VIDs. The range of values is 5 to 1440 (minutes). The default value is 25 (minutes). Note VIDs that you enter for the Management VID and VLAN Membership parameters do not time out. Management VID Enter the VID that the operator wishes to use to communicate with the module manager. The range of values is 1 to 4095. The default value is 1. QinQ EtherType Modules can be configured with 802.1ad Q-in-Q DVLAN (Double-VLAN) tagging which is a way for an operator to put an 802.1Q VLAN inside of an 802.1ad VLAN. A nested VLAN, which is the original 802.1Q tag and a new second 802.1ad tag, allows for bridging of VLAN traffic across a network and segregates the broadcast domains of 802.1Q VLANs. Q-in-Q can be used with PPPoE and/or NAT. The 802.1ad standard defines the S-VLAN as the Service Provider VLAN and the C-VLAN as the customer VLAN. The radio software does 2 layer Q-in-Q whereby the C-VLAN is the 802.1Q tag and the S-VLAN is the second layer Q tag as shown below:

Table 95 Q-in-Q Ethernet frame Ethernet S-VLAN C-VLAN EthType IP Data EthType Header EthType 0x88a8 0x8100 0x0800 The 802.1ad S-VLAN is the outer VLAN that is configurable on the Configuration > VLAN web page of the AP. The Q-in-Q EtherType parameter is configured with a default EtherType of 0x88a8 in addition to four alternate EtherTypes that can be configured to aid in interoperability with existing networks that use a different EtherType than the default. The C-VLAN is the inner VLAN tag, which is the same as 802.1Q. As a top level concept, this operates on the outermost tag at any given time, either pushing a tag on or popping a tag off. This means packets will at most transition from an 802.1Q frame to an 801.ad frame (with a tag pushed on) or an untagged 802.1 frame (with the tag popped off. Similarly, for an 802.1ad frame, this can only transition from an 802.1ad frame to an 802.1Q frame (with the tag popped off) since the radio software only supports 2 levels of tags Use AP's This field allows the SM to use the APs management VLAN ID when the Management VID for SM is registered to the AP via ICC. ICC connected SM Page 7-119 Chapter 7: Configuration Configuring IP and Ethernet interfaces VLAN Not Active When VLAN is enabled in the AP, the Active Configuration block provides the following details as read-only information in this tab. In the Cambium fixed wireless broadband IP network, each device of any type is automatically a permanent member of VID 1. This facilitates deployment of devices that have VLAN enabled with those that do not. VLAN Membership For each VLAN in which you want the AP to be a member, enter the Table Configuration VLAN ID and then click the Add Member button. Similarly, for any VLAN in which you want the AP to no longer be a member, enter the VLAN ID and then click the Remove Member button. VLAN Membership This field lists the VLANs that an AP is a member of. As the user adds a table number between 1 and 4094, this number is populated here. Source VLAN

(Range: 1-4094) Enter the VID for which the operator wishes to remark the 802.1p priority for the downstream packets. The range of values is 1 to 4094. The default value is 1. Remark Priority This is the priority you can assign to the VLAN Tagged packet. Priority of

(Range 0-7) 0 is the highest. VLAN Remarking As the user enters a VLAN and a Remarking priority, this information is table added in this table. Page 7-120 Chapter 7: Configuration VLAN page of SM The VLAN tab of SM/BHS is explained in Table 96. Table 96 SM VLAN attributes Configuring IP and Ethernet interfaces Attribute Meaning VLAN Port Type By default this is Q, indicating that it is to operate in the existing manner. The other option is Q-in-Q, which indicates that it must be adding and removing the S-Tag, and adding a C-Tag if necessary for untagged packets. The VLAN Port type corresponds to the Ethernet port of the SM/BHS. Currently, the internal management interfaces will always operate as Q ports. Page 7-121 Chapter 7: Configuration Configuring IP and Ethernet interfaces Accept QinQ Frames This option is valid for the Q-in-Q port so that the user may force blocking of existing 802.1ad Q-in-Q frames. This way, only untagged or single tagged packets will come in and out of the Ethernet interface. If a Q-in-Q frame is about ingress or egress the Ethernet interface and this is disabled, it is dropped and a filter entry will show up on the VLAN Statistics page as DVLAN Egress or DVLAN Ingress. Allow Frame Types Select the type of arriving frames that the SM must tag, using the VID that is stored in the Untagged Ingress VID parameter. The default value is All Frames. Tagged Frames Only: The SM only tags incoming VLAN-tagged frames Untagged Frames Only: The SM will only tag incoming untagged frames Dynamic Learning Specify whether the SM must (Enable) or not (Disable) add the VIDs of upstream frames (that enter the SM through the wired Ethernet interface) to the VID table. The default value is Enable. VLAN Aging Timeout Specify how long the SM/BHS must keep dynamically learned VIDs. The range of values is 5 to 1440 (minutes). The default value is 25 (minutes). Note VIDs that you enter for the Untagged Ingress VID and Management VID parameters do not time out. Management VID Enter the VID that the SM/BHS must share with the AP/BHM. The range of values is 1 to 4095. The default value is 1. SM Management Specify whether to allow the SM/BHS (Enabled) or the AP/RADIUS VID Pass-through

(Disabled) to control the VLAN settings of this SM. The default value is Enabled. When VLAN is enabled in the AP to whom this SM is registered, the Active Configuration block provides the following details as read-only information in this tab. In the Cambium fixed wireless broadband IP network, each device of any type is automatically a permanent member of VID 1. This facilitates deployment of devices that have VLAN enabled with those that do not. If disabled, MVID traffic is not allowed to or from the SM wired interface. Also, if Management VID is the same as a Port VID (Default or MAC-

based), then this setting is ignored and assumed to be Enabled. Default Port VID This is the VID that is used for untagged frames and will correspond to the Q-Tag for 802.1Q frames (if VLAN Port Type is Q), or the C-Tag for 802.1ad frames (if the VLAN Port Type is Q-in- Q). Page 7-122 Chapter 7: Configuration Configuring IP and Ethernet interfaces Port VID MAC These parameters allow operators to place specific devices onto Address Mapping different VLANs (802.1Q tag or 802.1ad C-tag) based on the source MAC address of the packet. If the MAC address entry is 00-00-00-00-00-

00 then that entry is not used. If a packet arrives at the SM that is sourced from a device whose MAC address is in the table, then the corresponding VID is used for that frames Q-tag (Q port) or C-tag (Q-

in-Q port). If there is no match, then the Default Port VID is used. This table is also used in the downstream direction for removal of the tag based on the destination MAC address so that an untagged (for Q port) or Q-Tagged (for Q-in-Q port) frame is delivered to the end device. You may use wildcards for the non-OUI (Organizationally Unique Identifier) portion of the MAC address, which is the last 3 bytes. MAC addresses contain 6 bytes, the first 3 of which are the OUI of the vendor that manufactured the device and the last 3 are unique to that vendor OUI. If you want to cover all devices from a known vendors OUI, you have to specify 0xFF for the remaining 3 bytes. So, for example, if you wanted all devices from a specific vendor with an OUI of 00-95-5b

(which is a Netgear OUI) to be on the same VID of 800, you have to specify an entry with MAC address 00-95-5b-ff-ff-ff. Then, any device underneath of the SM with MAC addresses starting with 00-95-5b is put on VLAN 800. Provider VID The provider VID is used for the S-tag. It is only used if the Port Type is Q-in-Q and will always be used for the S-tag. If an existing 802.1Q frame arrives, the Provider VID is what is used for adding and removing of the outer S-tag. If an untagged frame arrives to a Q-in-Q port, then the Provider VID is the S-tag and the Default Port VID (or Port VID MAC Address Mapping, if valid) is used for the C-tag. Active Configuration, This is the value of the parameter of the same name, configured above. Default Port VID Active Configuration, This is the listing of the MAC address VIDs configured in Port VID MAC MAC Address VID Address Mapping. Map Active Configuration, This is the value of the parameter of the same name, configured above. Management VID Active Configuration, This is the value of the parameter of the same name, configured above. SM Management VID Pass-Through Active Configuration, This is the value of the VLAN Aging Timeout parameter configured Dynamic Aging above. Timeout Active Configuration, Yes is displayed if the value of the Dynamic Learning parameter above is Allow Learning Enabled. No is displayed if the value of Dynamic Learning is Disabled. Page 7-123 Chapter 7: Configuration Configuring IP and Ethernet interfaces Active Configuration, This displays the selection that was made from the drop-down list at the Allow Frame Type Allow Frame Types parameter above. Active Configuration, This is set to Enabled if VLAN Port Type is set to QinQ, and is set to QinQ Disabled if VLAN Port Type is set to Q. Active Configuration, This is the value of the QinQ EtherType configured in the AP. QinQ EthType Active Configuration, This is the value of Accept QinQ Frames, configured above. Allow QinQ Tagged Frames Active Configuration, This column lists the ID numbers of the VLANs in which this module is a Current VID Member member, whether through assignment or through dynamic learning. Set, VID Number Active Configuration, For each VID number in the first column, the entry in this column Current VID Member correlates the way in which the module became and continues to be a Set, Type member:

PermanentThis indicates that the module was assigned the VID number through direct configuration by the operator. DynamicThis indicates that the module adopted the VID number through enabled dynamic learning, when a tagged packet from a SM behind it in the network or from a customer equipment that is behind the SM in this case, was read. Active Configuration, For each VID number in the first column of the table, the entry in this Current VID Member column reflects whether or when the VID number will time out:

Set, Age Permanent type - Number never times out and this is indicated by the digit 0. Dynamic type - Age reflects what is configured in the VLAN Aging Timeout parameter in the Configuration => VLAN tab of the AP or reflects a fewer number of minutes that represents the difference between what was configured and what has elapsed since the VID was learned. Each minute, the Age decreases by one until, at zero, the AP deletes the learned VID, but can it again from packets sent by elements that are beneath it in the network. Note Values in this Active Configuration block can differ from attempted values in configurations:

The AP can override the value that the SM has configured for SM Management VID Pass-Through. Page 7-124 Chapter 7: Configuration Configuring IP and Ethernet interfaces VLAN Membership tab of SM The Configuration > VLAN > VLAN Membership tab is explained in Table 97. Table 97 SM VLAN Membership attributes Attribute Meaning VLAN Membership For each VLAN in which you want the AP to be a member, enter the Table Configuration VLAN ID and then click the Add Member button. Similarly, for any VLAN in which you want the AP to no longer be a member, enter the VLAN ID and then click the Remove Member button. VLAN configuration for PTP Applicable products PTP: BHM BMS VLAN page of BHM The VLAN tab of BHS is explained in Table 98. Table 98 BHM VLAN page attributs Page 7-125 Chapter 7: Configuration Configuring IP and Ethernet interfaces Attribute Meaning VLAN Specify whether VLAN functionality for the BHM and all linked BHS must be (Enabled) or may not (Disabled) be allowed. The default value is Disabled. VLAN Port Type By default this is Q, indicating that it is to operate in the existing manner. The other option is Q-in-Q, which indicates that it must be adding and removing the S-Tag, and adding a C-Tag if necessary for untagged packets. The VLAN Port type corresponds to the Ethernet port of the BHS. Currently, the internal management interfaces will always operate as Q ports. Accept QinQ Frames This option is valid for the Q-in-Q port so that the user may force blocking of existing 802.1ad Q-in-Q frames. This way, only untagged or single tagged packets will come in and out of the Ethernet interface. If a Q-in-Q frame is about ingress or egress the Ethernet interface and this is disabled, it is dropped and a filter entry will show up on the VLAN Statistics page as DVLAN Egress or DVLAN Ingress. Management VID Enter the VID that the BHS must share with the BHM. The range of

(Range 1-4094) values is 1 to 4095. The default value is 1. Default Port VID This is the VID that is used for untagged frames and corresponds to the

(Range 1-4094) Q-Tag for 802.1Q frames (if VLAN Port Type is Q), or the C-Tag for 802.1ad frames (if the VLAN Port Type is Q-in- Q). QinQ Ether Type Modules can be configured with 802.1ad Q-in-Q DVLAN (Double-VLAN) tagging which is a way for an operator to put an 802.1Q VLAN inside of an 802.1ad VLAN. A nested VLAN, which is the original 802.1Q tag and a new second 802.1ad tag, allows for bridging of VLAN traffic across a network and segregates the broadcast domains of 802.1Q VLANs. Q-in-Q can be used with PPPoE and/or NAT. The 802.1ad standard defines the S-VLAN as the Service Provider VLAN and the C-VLAN as the customer VLAN. The radio software does 2 layer Q-in-Q whereby the C-VLAN is the 802.1Q tag and the S-VLAN is the second layer Q tag as shown below:

Ethernet Header S-VLAN EthType C-VLAN IP Data EthType 0x88a8 EthType 0x8100 0x0800 The 802.1ad S-VLAN is the outer VLAN that is configurable on the Configuration > VLAN web page of the BHM. The Q-in-Q EtherType parameter is configured with a default EtherType of 0x88a8 in addition to four alternate EtherTypes that can be configured to aid in interoperability with existing networks that use a different EtherType than the default. Page 7-126 Chapter 7: Configuration Configuring IP and Ethernet interfaces The C-VLAN is the inner VLAN tag, which is the same as 802.1Q. As a top level concept, this operates on the outermost tag at any given time, either pushing a tag on or popping a tag off. This means packets will at most transition from an 802.1Q frame to an 801.ad frame (with a tag pushed on) or an untagged 802.1 frame (with the tag popped off. Similarly, for an 802.1ad frame, this can only transition from an 802.1ad frame to an 802.1Q frame (with the tag popped off) since the radio software only supports 2 levels of tags. VLAN Not Active When VLAN is enabled in the BHM, the Active Configuration block provides the following details as read-only information in this tab. In the Cambium fixed wireless broadband IP network, each device of any type is automatically a permanent member of VID 1. This facilitates deployment of devices that have VLAN enabled with those that do not. Page 7-127 Chapter 7: Configuration VLAN page of BHS The VLAN tab of BHS is explained in Table 99. Table 99 BHS VLAN page attributes Configuring IP and Ethernet interfaces Attribute Meaning VLAN Specify whether VLAN functionality for the BHM and all linked BHS must be (Enabled) or may not (Disabled) be allowed. The default value is Disabled. VLAN Port Type By default this is Q, indicating that it is to operate in the existing manner. The other option is Q-in-Q, which indicates that it must be adding and removing the S-Tag, and adding a C-Tag if necessary for untagged packets. The VLAN Port type corresponds to the Ethernet port of the BHS. Currently, the internal management interfaces will always operate as Q ports. Accept QinQ Frames This option is valid for the Q-in-Q port so that the user may force blocking of existing 802.1ad Q-in-Q frames. This way, only untagged or single tagged packets will come in and out of the Ethernet interface. If a Q-in-Q frame is about ingress or egress the Ethernet interface and this is disabled, it is dropped and a filter entry will show up on the VLAN Statistics page as DVLAN Egress or DVLAN Ingress. Management VID Enter the VID that the BHS must share with the BHM. The range of

(Range 1-4094) values is 1 to 4095. The default value is 1. Default Port VID This is the VID that is used for untagged frames and corresponds to the

(Range 1-4094) Q-Tag for 802.1Q frames (if VLAN Port Type is Q), or the C-Tag for 802.1ad frames (if the VLAN Port Type is Q-in- Q). VLAN Not Active When VLAN is enabled in the BHM, the Active Configuration block provides the following details as read-only information in this tab. In the Cambium fixed wireless broadband IP network, each device of any type is automatically a permanent member of VID 1. This facilitates deployment of devices that have VLAN enabled with those that do not. Page 7-128 Chapter 7: Configuration Configuring IP and Ethernet interfaces PPPoE page of SM Applicable products PMP :

SM Point-to-Point Protocol over Ethernet (PPPoE) is a protocol that encapsulates PPP frames inside Ethernet frames (at Ethernet speeds). Benefits to the network operator may include Access control Service monitoring Generation of statistics about activities of the customer Re-use of infrastructure and operational practices by operators who already use PPP for other networks PPPoE options are configurable for the SM only, and the AP indicates whether or not PPPoE is enabled for a specific subscriber. When PPPoE is enabled, once the RF session comes up between the SM and the AP, the SM will immediately attempt to connect to the PPPoE Server. You can monitor the status of this by viewing the PPPoE Session Log in the Logs section (Administrator only). Every time the RF session comes up, the SM will check the status of the link and if it is down, the SM will attempt to redial the link if necessary depending on the Timer Type. Also, on the Configuration page, the user may Connect or Disconnect the session manually. This can be used to override the session to force a manual disconnect and/or reconnect if there is a problem with the session. In order to enable PPPoE, NAT MUST be enabled on the SM and Translation Bridging MUST be disabled on the AP. These items is strictly enforced for you when you are trying to enable PPPoE. A message will indicate any prerequisites not being met. Also, the NAT Public IP DHCP client cannot be enabled, because the NAT Public IP is received through the IPCP process of the PPPoE discovery stages. The pre-requisites are:

NAT MUST be enabled on the SM o NAT DHCP Client is disabled automatically. The NAT public IP is received from the PPPoE Server. o NAT Public Network Interface Configuration will not be used and must be left to defaults. Also NAT Public IP DHCP is disabled if it is enabled. Translation Bridging MUST be DISABLED on the AP o This will only be determined if the SM is in session since the SM wont know the AP configuration otherwise. If the SM is not in session, PPPoE can be enabled but if the SM goes into session to a Translation Bridge-enabled AP, then PPPoE will not be enabled. The PPPoE configuration parameters are explained in Table 100. Page 7-129 Chapter 7: Configuration Configuring IP and Ethernet interfaces Table 100 SM PPPoE attributes Attribute Meaning Access Concentrator An optional entry to set a specific access concentrator to connect to for the PPPoE session. If this is blank, the SM will accept the first access concentrator which matches the service name (if specified). This is limited to 32 characters. Service Name An optional entry to set a specific service name to connect to for the PPPoE session. If this is left blank the SM will accept the first service option that comes back from the access concentrator specified above, if any. This is limited to 32 characters. Authentication Type None means that no PPPoE authentication is implemented CHAP/PAP means that CHAP authentication is attempted first, then PAP authentication. The same password is used for both types. User Name This is the CHAP/PAP user name that is used if CHAP/PAP authentication is selected. If None is selected for authentication then this field is unused. This is limited to 32 characters. Password This is the CHAP/PAP password that is used if PAP authentication is selected. If None is selected for authentication then this field is unused. This is limited to 32 characters. MTU Use MTU Received from PPPoE Server causes the SM to use the MRU of the PPPoE server received in LCP as the MTU for the PPPoE link. Page 7-130 Chapter 7: Configuration Configuring IP and Ethernet interfaces Use User Defined MTU allows the operator to specify an MTU value to use to override any MTU that may be determined in the LCP phase of PPPoE session setup. If this is selected, the user is able to enter an MTU value up to 1492. However, if the MTU determined in LCP negotiations is less than this user-specified value, the SM will use the smaller value as its MTU for the PPPoE link. Timer Type Keep Alive is the default timer type. This timer will enable a keepalive that will check the status of the link periodically. The user can set a keepalive period. If no data is seen from the PPPoE server for that period, the link is taken down and a reconnection attempt is started. For marginal links, the keep alive timer can be useful so that the session will stay alive over periodic dropouts. The keepalive timer must be set such that the session can outlast any session drop. Some PPPoE servers will have a session check timer of their own so that the timeouts of the server and the SM are in sync, to ensure one side does not drop the session prematurely. Idle Timeout enables an idle timer that checks the usage of the link from the customer side. If there is no data seen from the customer for the idle timeout period, the PPPoE session is dropped. Once data starts flowing from the customer again, the session is started up again. This timer is useful for users who may not be using the connection frequently. If the session is idle for long periods of time, this timer will allow the resources used by the session to be returned to the server. Once the connection is used again by the customer, the link is reestablished automatically. Timer Period The length in seconds of the PPPoE keepalive timer. TCP MSS Clamping If this is enabled, then the SM will alter TCP SYN and SYN-ACK packets by changing the Maximum Segment Size to be compatible with the current MTU of the PPPoE link. This way, the user does not have to worry about MTU on the client side for TCP packets. The MSS is set to the current MTU 40 (20 bytes for IP headers and 20 bytes for TCP headers). This will cause the application on the client side to not send any TCP packets larger than the MTU. If the network is exhibiting large packet loss, try enabling this option. This may not be an option on the PPPoE server itself. The SM will NOT reassemble IP fragments, so if the MTUs are incorrect on the end stations, then MSS clamping will solve the problem for TCP connections. Page 7-131 Chapter 7: Configuration Configuring IP and Ethernet interfaces IP4 and IPv6 Applicable products PMP : AP SM PTP: BHM BMS IPv4 and IPv6 Prioritization 450 Platform Family provides operators the ability to prioritize IPv6 traffic in addition to IPv4 traffic. IPv6/IPv4 prioritization can be configured by selecting a CodePoint and the corresponding priority from the GUI of the AP/BHM and the IPv6/IPv4 packet is set up accordingly. There is no GUI option for selecting IPv6 or IPv4 priority. Once the priority is set, it is set for IPv4 and IPv6 packets. Configuring IPv4 and IPv6 Priority IPv4 and IPv6 prioritization is set using the DiffServ tab on the AP/BHM and SM/BHS (located at Configuration > DiffServ). A priority set to a specific CodePoint will apply to both IPv4 and IPv6 traffic. Table 101 DiffServ attributes AP/BHM Attribute Meaning CodePoint 1 through Priorities of 0 through 3 map to the low-priority channel; 4 through 7 to CodePoint 47 the high- priority channel. The mappings are the same as 802.1p VLAN CodePoint 49 priorities. Consistent with RFC 2474 through CodePoint CodePoint 0 is predefined to a fixed priority value of 0 (low-priority 55 CodePoint 57 through CodePoint 63 channel). CodePoint 48 is predefined to a fixed priority value of 6 (high-priority channel). CodePoint 56 is predefined to a fixed priority value of 7 (high-

priority channel). Page 7-132 Chapter 7: Configuration Configuring IP and Ethernet interfaces Operator cannot change any of these three fixed priority values. Among the settable parameters, the priority values (and therefore the handling of packets in the high or low priority channel) are set in the AP/BHM for all downlinks within the sector and in the SM/BHS for each uplink. CodePoint Select This represents the CodePoint Selection to be modified via Priority Select Priority Select The priority setting input for the CodePoint selected in CodePoint Select Priority Precedence Allows operator to decide if 802.1p or DiffServ priority bits must be used first when making priority decisions. PPPoE Control Operators may configure the AP/BHM to utilize the high priority channel Message Priority for PPPoE control messages. Configuring the AP/BHM in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the AP/BHM. IPv4 and IPv6 Filtering The operator can filter (block) specified IPv6 protocols including IPv4 and ports from leaving the AP/BHM and SM/BHS and entering the network. This protects the network from both intended and inadvertent packet loading or probing by network users. By keeping the specified protocols or ports off the network, this feature also provides a level of protection to users from each other. Configuring IPv4 and IPv6 Filtering IPv6 filters are set using the Protocol Filtering tab on the AP/BHM and SM/BHS (at Configuration >

Protocol Filtering). Once a filter is set for a packet type, those packets will not be sent over the RF interface depending on Filter Direction setting. Page 7-133 Chapter 7: Configuration Configuring IP and Ethernet interfaces Table 102 Packet Filter Configuration attributes Attribute Meaning Packet Filter Types For any box selected, the Protocol and Port Filtering feature blocks the associated protocol type. To filter packets in any of the user-defined ports, you must do all of the following:

Check the box for User Defined Port n (See Below) in the Packet Filter Types section of this tab. Provide a port number at Port #n. in the User Defined Port Filtering Configuration section of this tab Page 7-134 Chapter 7: Configuration Configuring IP and Ethernet interfaces Enable TCP and/or UDP by clicking the associated radio button Filter Direction Operators may choose to filter upstream (uplink) RF packets or downstream (downlink) RF packets. User Defined Port You can specify ports for which to block subscriber access, regardless of Filtering Configuration whether NAT is enabled. Page 7-135 Chapter 7: Configuration Upgrading the software version and using CNUT Upgrading the software version and using CNUT This section consists of the following procedures:

Checking the installed software version on page 7-136 Upgrading to a new software version on page 7-136 Caution If the link is operational, ensure that the remote end of the link is upgraded first using the wireless connection, and then the local end can be upgraded. Otherwise, the remote end may not be accessible. Use CNUT 4.10.4 or later version and always refer to the software release notes before upgrading system software. The release notes are available at:

https://support.cambiumnetworks.com/files/pmp450 https://support.cambiumnetworks.com/files/ptp450 Checking the installed software version To check the installed software version, follow these instructions:

Procedure 18 Checking the installed software version 1 2 Click on General tab under Home menu. Note the installed Software Version (under Device Information):

PMP/PTP 450/450i/450m 3 Go to the support website (see Contacting Cambium Networks on page 1) and find Point-

to-Multipoint software updates. Check that the latest 450 Platform Family software version is the same as the installed Software Version. 4 To upgrade software to the latest version, see Upgrading to a new software version on page 7-136. Upgrading to a new software version All 450 platform modules are upgraded using the Canopy Network Updater Tool. The Canopy Network Updater Tool (CNUT) manages and automates the software upgrade process for a Canopy radio, or CMM4 (but not its 14-port switch) across the network. This eliminates the need for an administrator to visit each radio in the network (or each AP/BHM while using the Autoupdate feature) to upgrade the modules. Page 7-136 Chapter 7: Configuration Upgrading the software version and using CNUT Note Please ensure that you have the most up-to-date version of CNUT by browsing to the Customer Support Web Page located:

http://www.cambiumnetworks.com/support/management-tools/cnut This section includes an example of updating a single unit before deployment. System-wide upgrading procedures may be found in the CNUT Online Help manual, which can be found on the Cambium support website (see Contacting Cambium Networks on page 1). CNUT functions The Canopy Network Updater tool has the following functions:

Automatically discovers all network elements Executes a UDP command that initiates and terminates the Auto-update mode within APs/BHMs. This command is both secure and convenient:

o For security, the AP/BHM accepts this command from only the IP address that you specify in the Configuration page of the AP/BHM. o For convenience, Network Updater automatically sets this Configuration parameter in the APs/BHMs to the IP address of the Network Updater server when the server performs any of the update commands. CNUT supports HTTP and HTTPS Allows you to choose the following among updating:

o Your entire network. o Only elements that you select. o Only network branches that you select. Provides a Script Engine that you can use with any script that:

o You define. o Cambium supplies. Configurability of any of the following to be the file server for image files:

o The AP/BHM, for traditional file serving via UDP commands and monitoring via UDP messaging o CNUT HTTP/HTTPS Server, for upgrading via SNMP commands and monitoring via SNMP messaging. This also supports an option to either set the image order specifically for this file server or to allow the AP to determine the order. o Local TFTP Server, for traditional file serving via UDP commands and monitoring via UDP messaging. This supports setting the number of simultaneous image transfers per AP/BHM The capability to launch a test of connectivity and operational status of the local HTTP, HTTPS and TFTP file servers An interface that supports efficient specification of the proper IP address for the local file server(s) where Network Updater resides on a multi-homed computer An md5 checksum calculator utility for identifying corruption of downloaded image files before Network Updater is set to apply them. Page 7-137 Chapter 7: Configuration Upgrading the software version and using CNUT Network element groups With the Canopy Network Updater Tool, you can identify element groups composed of network elements that you select. Identifying these element groups does the following:

Organizes the display of elements (for example, by region or by AP/BHM cluster). Allows to:

o Perform an operation on all elements in the group simultaneously. o Set group-level defaults for ftp password access and SNMP Community String (defaults that can be overridden in an individual element when necessary). Network layers A typical network contains multiple layers of elements, with each layer farther from the Point of Presence. For example, SMs (or BHS) are behind an AP/BHM and thus, in this context, at a lower layer than the AP/BHM. Correctly portraying these layers in Network Updater is essential so that Network Updater can perform radio and AP/BHM cluster upgrades in an appropriate order. Script engine Script Engine is the capability in Network Updater that executes any user-defined script against any network element or element group. This capability is useful for network management, especially for scripts that you repetitively execute across your network. The Autodiscovery capability in Network Updater finds all of your network elements. This comprehensive discovery:

Ensures that, when you intend to execute a script against all elements, the script is indeed executed against all elements. Maintains master lists of elements (element groups) against which you selectively execute scripts. The following scripts are included with CNUT:

Gather Customer Support Information Set Access Point Authentication Mode Set Autoupdate Address on APs/BHMs Set SNMP Accessibility Reset Unit Page 7-138 Chapter 7: Configuration Upgrading the software version and using CNUT Software dependencies for CNUT CNUT functionality requires one of the following operating systems o Windows 2000 o Windows Server 2003 o Windows 7 and Windows 8 o Windows XP or XP Professional o Red Hat Enterprise Linux (32-bit) Version 4 or 5 Java Runtime Version 2.0 or later (installed by the CNUT installation tool) CNUT download CNUT can be downloaded together with each system release that supports CNUT. Software for these system releases is available from http://www.cambiumnetworks.com/support/management-

tools/cnut/, as either:

A .zip file for use without the CNUT application. A .pkg file that the CNUT application can open. Upgrading a module prior to deployment To upgrade to a new software version, follow this:

Procedure 19 Upgrading a module prior to deployment 1 Go to the support website (see Contacting Cambium Networks on page 1) and find Point-

to-Multipoint software updates. Download and save the required software image. 2 3 Start CNUT If you dont start up with a blank new network file in CNUT, then open a new network file with the New Network Archive operation (located at File > New Network). 4 Enter a new network element to the empty network tree5-9 using the Add Elements to Network Root operation (located at Edit > Add Elements to Network Root). 5 In the Add Elements dialogue, select a type of Access Point or Subscriber Module and enter the IP address of 169.254.1.1. 6 Make sure that the proper Installation Package is active with the Package Manager dialogue (located at Update > Manage Packages). 7 To verify connectivity with the radio, perform a Refresh, Discover Entire Network operation (located at View > Refresh/Discover Entire Network). You must see the details columns for the new element filled in with ESN and software version information. 8 Initiate the upgrade of the radio using Update Entire Network Root operation (located at Update > Update Entire Network Root). When this operation finishes, the radio is done being upgraded. Page 7-139 Chapter 7: Configuration General configuration General configuration The Configuration > General page of the AP/BMH or BHM/BHS contains many of the configurable parameters that define how the ratios operate in sector or backhaul. Applicable products PMP : AP SM PTP: BHM BMS PMP 450m and PMP/PTP 450i Series General page - PMP 450m AP / PMP 450i AP The General page of AP is explained in Table 103. The General page of PMP 450 SM looks same as PMP 450i AP. Table 103 General page attributes PMP 450i AP / PMP 450m AP Page 7-140 Chapter 7: Configuration General configuration Attribute Meaning Link Speeds From the drop-down list of options, select the type of link speed for the 802.3at Type 2 PoE Status and PoE Classification

(PMP 450i Series only) Ethernet connection. The default for this parameter is that all speeds are selected: Auto 100F/100H/10F/10H. In this setting, the two ends of the link automatically negotiate with each other whether the speed that they will use is 10 Mbps or 100 Mbps and whether the Ethernet traffic is full duplex or half duplex. However,137 Ethernet links work best when either:

both ends are set to the same forced selection both ends are set to auto-negotiate and both have capability in least one common speed and traffic type combination. When the PoE Classification functionality is enabled and if Type 2 power is not present, the PAs do not power up and draw too much power. By default, the PoE Classification feature is disabled and the PAs will power up regardless of the classification presented by the power source. This is supported only on 450i series devices. PoE Classification configuration status also can be check under home >

General > Device Information tab:

Configuration See Setting the Configuration Source on page 7-260. Source Sync Input See Configuring synchronization on page 7-163 Device Type Standard: The Autosync mechanism will source GPS synchronization from the APs RJ-11 port, the APs power port, or from the device on-

board GPS module. Remote: The Autosync mechanism will source GPS synchronization from the APs RJ-11 port or from the device on-board GPS module. Page 7-141 Chapter 7: Configuration General configuration Region From the drop-down list, select the region in which the radio is operating. Country From the drop-down list, select the country in which the radio is operating. Unlike selections in other parameters, your Country selection requires a Save Changes and a Reboot cycle before it will force the context-

sensitive GUI to display related options (for example, Alternate Frequency Carrier 1 and 2 in the Configuration > Radio tab). PMP 450i Series ODUs shipped to the United States is locked to a Region Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. Country Code settings affect the radios in the following ways:

Maximum transmit power limiting (based on radio transmitter power plus configured antenna gain) DFS operation is enabled based on the configured region code, if applicable For more information on how transmit power limiting and DFS is implemented for each country, see the PMP 450 Planning Guide. Webpage Auto Enter the frequency (in seconds) for the web browser to automatically Update refresh the web-based interface. The default setting is 0. The 0 setting causes the web-based interface to never be automatically refreshed. Bridge Entry Specify the appropriate bridge timeout for correct network operation Timeout with the existing network infrastructure. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Caution An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. Translation Bridging Optionally, you can configure the AP to change the source MAC address in every packet it receives from its SMs to the MAC address of the SM that bridged the packet, before forwarding the packet toward the public network. If you do, then:

Not more than 10 IP devices at any time are valid to send data to the AP from behind the SM. SM populates the Translation Table tab of its Statistics web page, displaying the MAC address and IP address of all the valid connected devices. Page 7-142 Chapter 7: Configuration General configuration Each entry in the Translation Table is associated with the number of minutes that have elapsed since the last packet transfer between the connected device and the SM. If 10 are connected and another attempts to connect:

If no Translation Table entry is older than 255 minutes, the attempt is ignored. If an entry is older than 255 minutes, the oldest entry is removed and the attempt is successful. the Send Untranslated ARP parameter in the General tab of the Configuration page can be:

Disabled, so that the AP overwrites the MAC address in Address Resolution Protocol (ARP) packets before forwarding them. Enabled, so that the AP forwards ARP packets regardless of whether it has overwritten the MAC address. When this feature is disabled, the setting of the Send Untranslated ARP parameter has no effect, because all packets are forwarded untranslated

(with the source MAC address intact). Send Untranslated If the Translation Bridging parameter is set to Enabled, then the Send ARP Untranslated ARP parameter can be:

Disabled - so that the AP will overwrite the MAC address in Address Resolution Protocol (ARP) packets before forwarding them. Enabled - so that the AP will forward ARP packets regardless of whether it has overwritten the MAC address. If the Translation Bridging parameter is set to Disabled, then the Send Untranslated ARP parameter has no effect. SM Isolation Prevent or allow SM-to-SM communication by selecting from the following drop-down menu items:

Disable SM Isolation (the default selection). This allows full communication between SMs. Block SM Packets from being forwarded. This prevents both multicast/broadcast and unicast SM-to-SM communication. Block and Forward SM Packets to Backbone. This not only prevents multicast/broadcast and unicast SM-to-SM communication but also sends the packets, which otherwise are handled SM to SM, through the Ethernet port of the AP. Forward Unknown Enabled: All unknown Unicast packets (no entry in the APs bridge table) Unicast Packets received via the APs Ethernet LAN interface are forwarded to registered SMs. If the target device is situated beneath a particular SM, when the device responds the SM and AP will learn and add the device to their bridge tables so that subsequent packets to that device is bridged to the proper SM. Disabled: All unknown Unicast packets (no entry in the APs bridge table) received via the APs Ethernet LAN interface are discarded at the AP. Page 7-143 Chapter 7: Configuration General configuration Update Application Enter the address of the server to access for software updates on this AP Address and registered SMs. Prioritize TCP ACK To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. This parameter, when enabled, can be particularly useful when running bi-direction FTP sessions over the link. If a link is primarily used for video surveillance, it is recommended to set this parameter to Disable. Multicast Destination Using Link Layer Discovery Protocol (LLDP), a module exchanges Address multicast addresses with the device to which it is wired on the Ethernet interface. Although some switches (CMM4, for example) do not pass LLDP addresses upward in the network, a radio can pass it as the value of the Multicast Destination Address parameter value in the connected device that has it populated. DHCP Relay Agent The AP may act as a DHCP relay for SMs and CPEs underneath it. The AP will make use of the DHCP Option 82 (DHCP Relay Agent Information) from RFC 3046 when performing relay functions. The AP offers two types of DHCP relay functionality:

Full Relay Information. Configuring the DHCP Full Relay Operation will take broadcast DHCP packets and send them to a Unicast server in unicast mode. This way the DHCP requests and replies can be routed like any other UDP packet. Only Insert Option 82. This option leaves the DHCP request on its broadcast domain as opposed to DHCP Full Relay Operation which will turn it into a unicast packet. In order to accommodate setting up pools or classes for different VLANs, the Option 82 field will include information to tell the server what VLAN the client is on. DHCP Server (Name The DHCP relay server may be either a DNS name or a static IP address or IP Address) in dotted decimal notation. Additionally the management DNS domain name may be toggled such that the name of the DHCP relay server only needs to be specified and the DNS domain name is automatically appended to that name. The default DHCP relay server addresses is 255.255.255.255 with the appending of the DNS domain name disabled. Latitude Longitude Height Physical radio location data may be configured via the Latitude, Longitude and Height fields. Latitude and Longitude is measured in Decimal Degree while the Height is calculated in Meters. Page 7-144 Chapter 7: Configuration General configuration General page - PMP 450i SM The General page of PMP 450i SM is explained in Table 104. The General page of PMP 450 SM looks same as PMP 450i SM. Table 104 General page attributes PMP 450i SM Attribute Meaning Link Speeds From the drop-down list of options, select the type of link speed for the Ethernet connection. The default for this parameter is that all speeds are selected. The recommended setting is a single speed selection for all APs and SMs in the operator network. 802.3at Type 2 PoE Status and PoE Classification When the PoE Classification functionality is enabled and if Type 2 power is not present, the PAs do not power up and draw too much power. By default, the PoE Classification feature is disabled and the PAs will power up regardless of the classification presented by the power source. This is supported only on 450i series ODUs. Page 7-145 Chapter 7: Configuration General configuration PoE Classification configuration status also can be check under home >

General > Device Information tab:

Ethernet Link Specify whether to enable or disable Ethernet/802.3 connectivity on the Enable/Disable wired port of the SM. This parameter has no effect on the wireless link. When you select Enable, this feature allows traffic on the Ethernet/802.3 port. This is the factory default state of the port. When you select Disable, this feature prevents traffic on the port. Typical cases of when you may want to select Disable include:

The subscriber is delinquent with payment(s). You suspect that the subscriber is sending or flooding undesired broadcast packets into the network, such as when a virus is present in the subscriber's computing device. the subscriber's home router is improperly configured. Region This parameter allows you to set the region in which the radio will operate. The SM radio automatically inherits the Region type of the master. This behavior ignores the value of the Region parameter in the SM, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-

sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. Country This parameter allows you to set the country in which the radio will operate. The SM radio automatically inherits the Country Code type of the master. This behavior ignores the value of the Country parameter in the SM, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. PMP/PTP 450i Series ODU shipped to the United States is locked to a Region Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. Webpage Auto See Table 103 General page attributes PMP 450i AP on page 7-140 Update Bridge Entry Specify the appropriate bridge timeout for correct network operation Timeout with the existing network infrastructure. Timeout occurs when the AP encounters no activity with the SM (whose MAC address is the bridge entry) within the interval that this parameter specifies. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Page 7-146 Chapter 7: Configuration General configuration Caution This parameter governs the timeout interval, even if a router in the system has a longer timeout interval. The default value of this field is 25 (minutes). An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. Frame Timing Pulse If this SM extends the sync pulse to a BH master or an AP, select either Gated EnableIf this SM loses sync from the AP, then do not propagate a sync pulse to the BH timing master or other AP. This setting prevents interference in the event that the SM loses sync. DisableIf this SM loses sync from the AP, then propagate the sync pulse to the BH timing master or other AP. Multicast Destination Using Link Layer Discovery Protocol (LLDP), a module exchanges Address multicast addresses with the device to which it is wired on the Ethernet interface. Although some switches (CMM4, for example) do not pass LLDP addresses upward in the network, a radio can pass it as the value of the Multicast Destination Address parameter value in the connected device that has it populated. Coordinates Physical radio location data may be configured via the Latitude, Longitude and Height fields. Page 7-147 Chapter 7: Configuration General configuration General page - PTP 450i BHM The General page of BHM is explained in Table 105. The General page of PTP 450 BHM looks same as PTP 450i BHM. Table 105 General page attributes PTP 450i BHM Page 7-148 Chapter 7: Configuration General configuration Attribute Meaning Timing Mode Allows the user to choose the mode between Timing Master and Timing Slave. Link Speed See Table 103 General page attributes PMP 450i AP on page 7-140 802.3at Type 2 PoE Status and PoE Classification When the PoE Classification functionality is enabled and if Type 2 power is not present, the PAs do not power up and draw too much power. By default, the PoE Classification feature is disabled and the PAs will power up regardless of the classification presented by the power source. This is supported only on 450i Series ODUs. PoE Classification configuration status also can be check under home

> General > Device Information tab:

Sync Input See Configuring synchronization on page 7-163 Region Country Webpage Auto Update Bridge Entry Timeout See Table 103 General page attributes PMP 450i AP on page 7-140 Bridging Functionality Select whether you want bridge table filtering active (Enable) or not

(Disable) on this BH. Disable: allows user to use redundant BHs without causing network addressing problems. Through a spanning tree protocol, this reduces the convergence time from 25 minutes to few seconds. However, you must disable bridge table filtering as only a deliberate part of your overall network design since disabling it allows unwanted traffic across the wireless interface. Enable: Allows user to enable bridge functionality. Note Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. See Table 103 General page attributes PMP 450i AP on page 7-140 Page 7-149 Prioritize TCP ACK Multicast Destination Address Chapter 7: Configuration General configuration Latitude Longitude Height General page - PTP 450i BHS The General page of PTP 450i BHS is explained in Table 106. The General page of PTP 450 BHS looks same as PTP 450i BHS. Table 106 General page attributes PTP 450i BHS Page 7-150 Chapter 7: Configuration General configuration Attribute Meaning Timing Mode Allows the user to choose the mode between Timing Master and Timing Slave. Link Speed From the drop-down list of options, select the type of link speed for the 802.3at Type 2 PoE Status and PoE Classification Ethernet connection. The default for this parameter is that all speeds are selected. The recommended setting is a single speed selection for all BHMs and BHSs in the operator network. When the PoE Classification functionality is enabled and if Type 2 power is not present, the PAs do not power up and draw too much power. By default, the PoE Classification feature is disabled and the PAs will power up regardless of the classification presented by the power source. This is supported only on 450i Series ODUs. PoE Classification configuration status also can be check under home >

General > Device Information tab:

Region This parameter allows you to set the region in which the radio will operate. The BHS radio automatically inherits the Region type of the master. This behavior ignores the value of the Region parameter in the BHS, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-

sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. Country This parameter allows you to set the country in which the radio will operate. The BHS radio automatically inherits the Country Code type of the master. This behavior ignores the value of the Country parameter in the BHS, even when the value is None. Nevertheless, since future system software releases may read the value in order to configure some other region-sensitive feature(s), this parameter must be always set to the value that corresponds to the local region. PMP/PTP 450i Series ODU shipped to the United States is locked to a Region Code setting of United States. Units shipped to regions other than the United States must be configured with the corresponding Region Code to comply with local regulatory requirements. Webpage Auto See Table 103 General page attributes PMP 450i AP on page 7-140 Update Bridge Entry Specify the appropriate bridge timeout for correct network operation Timeout with the existing network infrastructure. Timeout occurs when the BHM encounters no activity with the BHS (whose MAC address is the bridge entry) within the interval that this parameter specifies. The Bridge Entry Timeout must be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Page 7-151 Chapter 7: Configuration General configuration Caution This parameter governs the timeout interval, even if a router in the system has a longer timeout interval. The default value of this field is 25 (minutes). An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. See Table 103 General page attributes PMP 450i AP on page 7-140 Bridging Functionality Frame Timing Pulse If this BHS extends the sync pulse to a BH master or an BHM, select Gated either EnableIf this BHS loses sync from the BHM, then do not propagate a sync pulse to the BH timing master or other BHM. This setting prevents interference in the event that the BHS loses sync. DisableIf this BHS loses sync from the BHM, then propagate the sync pulse to the BH timing master or other BHM. Multicast Destination See Table 103 General page attributes PMP 450i AP on page 7-140 Address Latitude Longitude Height See Table 103 General page attributes PMP 450i AP on page 7-140 PMP/PTP 450 Series Note Refer Table 103 and Table 104 for PMP 450 AP/SM General page parameters details. Page 7-152 Chapter 7: Configuration General configuration General page - PMP 450 AP Figure 113 General page attributes - PMP 450 AP Page 7-153 Chapter 7: Configuration General configuration General page - PMP 450 SM Figure 114 General page attributes - PMP 450 SM Page 7-154 Chapter 7: Configuration General configuration General page PTP 450 BHM Figure 115 General page attributes - PTP 450 BHM Page 7-155 Chapter 7: Configuration General configuration General page PTP 450 BHS Figure 116 General page attributes - PTP 450 BHS Page 7-156 Chapter 7: Configuration Configuring Unit Settings page Configuring Unit Settings page Applicable products PMP : AP SM PTP: BHM BMS The Unit Settings page of the 450 Platform Family contains following options:

Unit-Wide Changes Download Configuration File Upload and Apply Configuration File (for AP and BHM) LED Panel Settings (for SM and BHS) Note LED Panel setting is applicable for SM and BHS only. Upload and Apply Configuration File attributes are not supported for SM and BHS. The 450 Platform Family also supports import and export of configuration from the AP/BHM/SM/BHS as a text file. The configuration file is in JSON format. The logged in user must be an ADMINISTRATOR in order to export or import the configuration file. The exported configuration file contains the complete configuration including all the default values. To keep a backup of the current configuration, the file can be saved as-is and imported later. The configuration file supports encrypted password. The exported configuration file will contain encrypted password. The import of configuration can have either encrypted or plain text password in Configuration fie. A new tab Encrypt the Password is added under Encrypted Password tab to generate encrypted password for a given password. The Import and Export procedure of configuration file is described in Import and Export of config file on page 7-275. LED Panel Mode has options select Revised mode and Legacy mode. The Legacy mode configures the radio to operate with standard LED behavior. Page 7-157 Chapter 7: Configuration Configuring Unit Settings page Unit Settings page of 450 Platform Family - AP/BHM The Unit Setting page of AP/BHM is explained in Table 107. Table 107 Unit Settings attributes 450 Platform Family AP/BHM Attribute Meaning Set to Factory Defaults Upon Default Mode Detection If Enabled is checked, then the default mode functions is enabled. When the module is rebooted with Default mode enabled, it can be accessed at the IP address 169.254.1.1 and no password, and all parameter values are reset to defaults. A subscriber, technician, or other person who gains physical access to the module and uses an override cannot see or learn the settings that were previously configured in it. If Disabled is checked, then the default mode functions is disabled. See Radio recovery mode on page 1-24 Caution When Set to Factory Defaults Upon Default Mode is set to Enable, the radio does not select all of the frequencies for Radio Frequency Scan Selection List. It needs to be selected manually. Undo Unit-Wide When you click this button, any changes that you made in any tab but Saved Changes did not commit by a reboot of the module are undone. Page 7-158 Chapter 7: Configuration Configuring Unit Settings page Set to Factory When you click this button, all configurable parameters on all tabs are Defaults reset to the factory settings. Note This can be reverted by selecting "Undo Unit-Wide Saved Changes", before rebooting the radio, though this is not recommended. Password This allows to provide encrypted password for a given password. On click of Encrypt the password button, the Encrypted Password field will display encrypted value of entered plain text password in Password field. Configuration File This allows to download the configuration file of the radio. This configuration file contains the complete configuration including all the default values. The configuration file is highlighted as downloadable link and the naming convention is <mac address of AP>.cfg. Apply Configuration This allows to import and apply configuration to the AP. File Chose File: Select the file to upload the configuration. The configuration file is named as <file name>.cfg. Upload: Import the configuration to the AP. Apply Configuration File: Apply the imported configuration file to the AP. The imported configuration file may either contain a full device configuration or a partial device configuration. If a partial configuration file is imported, only the items contained in the file will be updated, the rest of the device configuration parameters will remain the same. Operators may also include a special flag in the configure file to instruct the device to first revert to factory defaults then to apply the imported configuration. Status of This section shows the results of the upload. Configuration file Page 7-159 Chapter 7: Configuration Configuring Unit Settings page Unit Settings page of PMP/PTP 450i SM/BHS The Unit Settings page of PMP/PTP 450i SM/BHS is explained in Table 108. Table 108 SM Unit Settings attributes Attribute Meaning Set to Factory Defaults Upon Default Plug Detection See Table 107 Unit Settings attributes 450 Platform Family AP/BHM on page 7-158 LED Panel Settings Legacy Mode configures the radio to operate with standard LED behavior. Undo Unit-Wide Saved Changes Password Set to Factory See Table 107 Unit Settings attributes 450 Platform Family AP/BHM on Defaults page 7-158 Configuration File Status of Configuration file Page 7-160 Chapter 7: Configuration Setting up time and date Setting up time and date Time page of 450 Platform Family - AP/BHM Applicable products PMP : AP PTP: BHM The Time page of 450 Platform Family AP/BHM is explained in Table 109. Table 109 450 Platform Family - AP/BHM Time attributes Attribute Meaning NTP Server (Name The management DNS domain name may be toggled such that the or IP Address) name of the NTP server only needs to be specified and the DNS domain name is automatically appended to that name. NTP Server 1 (Name To have each log in the AP/BHM correlated to a meaningful time and or IP Address) date, either a reliable network element must pass time and date to the NTP Server 2 (Name or IP Address) NTP Server 3 (Name or IP Address) AP/BHM or must set the time and date whenever a power cycle of the AP/BHM has occurred. A network element passes time and date in any of the following scenarios:

A connected CMM4 passes time and date (GPS time and date, if received). A connected CMM4 passes the time and date (GPS time and date, if received), but only if both the CMMr is operating on CMMr Release 2.1 or later release. (These releases include NTP server functionality.) Page 7-161 Chapter 7: Configuration Setting up time and date A separate NTP server (including APs/BHMs receiving NTP data) is addressable from the AP/BHM. If the AP/BHM needs to obtain time and date from a CMM4, or a separate NTP server, enter the IP address or DNS name of the CMM4 or NTP server on this tab. To force the AP/BHM to obtain time and date before the first (or next) 15-minute interval query of the NTP server, click Get Time via NTP. The polling of the NTP servers is done in a sequential fashion, and the polling status of each server is displayed in the NTP Update Log section of the Time Configuration page. An entry of 0.0.0.0 in any of the NTP Server fields indicates an unused server configuration. NTP Server(s) in Use Lists the IP addresses of servers used for NTP retrieval. Time Zone The Time Zone option may be used to offset the received NTP time to match the operators local time zone. When set on the AP/BHM, the offset is set for the entire sector SMs (or BHS) are notified of the current Time Zone upon initial registration). If a Time Zone change is applied, the SMs(or BHS) is notified of the change in a best effort fashion, meaning some SMs//BHSs may not pick up the change until the next re-

registration. Time Zone changes are noted in the Event Log of the AP/BHM and SM/BHS. System Time The current time used by the system. Last NTP Time The last time that the system time was set via NTP. Update Time Date This field may be used to manually set the system time of the radio. This field may be used to manually set the system date of the radio. NTP Update Log This field shows NTP clock update log. It includes NTP clock update Date and Time stamp along with server name. Page 7-162 Chapter 7: Configuration Configuring synchronization Configuring synchronization Applicable products PMP : AP PTP: BHM This section describe synchronization options for PMP and PTP configuration. This Sync Input parameter can be configured under Sync Setting tab of Configure > General page

(see General configuration on page 7-140). PMP/PTP 450i Series has following synchronization options:

AutoSync AutoSync + Free Run Generate Sync Free Run Before GPS Sync Figure 117 Sync Setting configuration AutoSync For PTP, the BHM automatically receives sync from one of the following sources:

GPS Sync over Timing Port (UGPS, co-located AP GPS sync output, or Remote Device feed from a registered SMs GPS sync output) GPS Sync over Power Port (CMM4) Upon AP/BM power on, the AP/BHM does not transmit until a valid synchronization pulse is received from one of the sources above. If there is a loss of GPS synchronization pulse, within two seconds the AP/BHM automatically attempts to source GPS signaling from another source. In case of PMP, when there are synchronization sources on both the timing port and the power port, the power port GPS source is chosen first. If no valid GPS signal is received, the AP/BHM ceases transmission and SM/BHS registration is lost until a valid GPS signal is received again on the AP or BHM. Page 7-163 Chapter 7: Configuration AutoSync + Free Run Configuring synchronization This mode operates similarly to mode AutoSync, but if a previously received synchronization signal is lost and no GPS signaling alternative is achieved, the AP/BHM automatically changes to synchronization mode Generate Sync. While SM registration ins maintained, in this mode there is no synchronization of APs/BHMs that can hear each other; the AP/BHM will only generate a sync signal for the local AP/BHM and its associated SMs/BHS. Once a valid GPS signal is obtained again, the AP/BHM automatically switches to receiving synchronization via the GPS source and SM/BHS registration is maintained. When the Sync Input field is set to Autosync or Autosync + Free Run, other options become available to be set e.g. UGPS Power and other fields. This is true on APs and BHMs. Note In mode AutoSync + Free Run, if a GPS signal is never achieved initially, the system will not switch to Free Run mode, and SMs/BHS will not register to the AP/BHM. A valid GPS signal must be present initially for the AP to switch into Free Run mode

(and to begin self-generating a synchronization pulse). Also, When an AP/BHM is operating in Free Run mode, over a short time it will no longer be synchronized with co-located or nearby APs/BHMs (within radio range). Due to this lack of transmit and receive synchronization across APs/BHMs or across systems, performance while in Free Run mode may be degraded until the APs/BHMs operating in Free Run mode regain a external GPS synchronization source. Careful attention is required to ensure that all systems are properly receiving an external GPS synchronization pulse, and please consider Free Run mode as an emergency option. Generate Sync (factory default) This option may be used when the AP/BHM is not receiving GPS synchronization pulses from either a CMM4 or UGPS module, and there are no other APs/BHMs active within the link range. Using this option will not synchronize transmission of APs/BHMs that can hear each other; it will only generate a sync signal for the local AP/BHM and its associated SMs/BHS. Note When an AP/BHM has its "Regional Code" set to "None", The radio will not provide valid Sync Pulse Information. There is a RED warning that the radio will not transmit, but the user might expect to see a valid sync if the radio is connected to a working CMM4 or UGPS. Page 7-164 Chapter 7: Configuration Configuring security Configuring security Perform this task to configure the 450 Platform system in accordance with the network operators security policy. Choose from the following procedures:

Managing module access by password on page 7-166: to configure the unit access password and access level Isolating from the internet on page 7-169: to ensure that APs are properly secured from external networks Encrypting radio transmissions on page 7-169: to configure the unit to operate with AES or DES wireless link security Requiring SM Authentication on page 7-170: to set up the AP to require SMs to authenticate via the AP, WM, or RADIUS server Filtering protocols and ports on page 7-171: to filter (block) specified protocols and ports from leaving the system Encrypting downlink broadcasts on page 7-174: to encrypt downlink broadcast transmissions Isolating SMs on page 7-174: to prevent SMs in the same sector from directly communicating with each other Filtering management through Ethernet on page 7-175: to prevent management access to the SM via the radios Ethernet port Allowing management only from specified IP addresses on page 7-175: to only allow radio management interface access from specified IP addresses Restricting radio Telnet access over the RF interface on page 7-175: to restrict Telnet access to the AP Configuring SNMP Access on page 7-178 Configuring Security on page 7-180 Page 7-165 Chapter 7: Configuration Configuring security Managing module access by password Applicable products PMP : AP SM PTP: BHM BMS See Managing module access by passwords on page 3-38. Adding a User for Access to a module The Account > Add User page allows to create a new user for accessing 450 Platform Family -

AP/SM/BHM/BHS. The Add User page is explained in Table 110. Table 110 Add User page of account page - AP/ SM/BH Attribute Meaning User Name User Account name. Level Select appropriate level for new account. It can be INSTALLER, ADMINISTRATOR or TECHNICIAN. See Managing module access by passwords on page 3-38. New Password Assign the password for new user account Confirm Password This new password must be confirmed in the Confirm Password field. User Mode User Mode is used to create an account which are mainly used for viewing the configurations. The local and remote Read-Only user account can be created by Admin, Installer or Tech logins. To create a Read-Only user, the read-only check box needs to be checked. Note The Read-Only user cannot perform any service impacting operations like creating read-only accounts, editing and viewing read-only user accounts, changes in login page, read-only user login, Telnet access, SNMP, RADIUS and upgrade/downgrade. Page 7-166 Chapter 7: Configuration Configuring security Deleting a User from Access to a module The Account > Delete User page provides a drop down list of configured users from which to select the user you want to delete. The Delele User page is explained in Table 111. Table 111 Delete User page - 450 Platform Family - AP/ SM/BH Attribute Meaning User Select a user from drop down list which has to be deleted and click Delete button. Accounts that cannot be deleted are the current user's own account. the last remaining account of ADMINISTRATOR level. Changing a User Setting The Account > Change User Setting page allows to update password, mode update and general status permission for a user. From the factory default state, configure passwords for both the root and admin account at the ADMINISTRATOR permission level, using Update Password tab of Change Users Setting page. The Change User Setting page is explained in Table 112. Table 112 Change User Setting page - 450 Platform Family AP/ SM/BH Page 7-167 Chapter 7: Configuration Configuring security Attribute Meaning Update Password This tab provides a drop down list of configured users from which a user tab is selected to change password. Update Mode tab This tab facilitates to convert a configured user to a Read-Only user. General Status This tab enables and disables visibility of General Status Page for all Permission tab Guest user. To display of Radio data on SMs/BHS main Login page for Guest login, it can be enabled or disabled in Security tab of Configuration page. Figure 118 AP Evaluation Configuration parameter of Security tab for PMP Figure 119 BHM Evaluation Configuration parameter of Security tab for PTP Users account The Account > Users page allows to view all configured users account for accessing the module. The Users page is explained in Table 113. Table 113 User page 450 Platform Family AP/SM/BH Attribute Meaning Username User access account name Permission Permission of configured user INSTALLER, ADMINISTRATOR or TECHNICIAN Mode This field indicate access mode of user Read-Write or Read-Only. Page 7-168 Chapter 7: Configuration Configuring security Overriding Forgotten IP Addresses or Passwords on AP and SM See Radio recovery mode on page 1-24 Isolating from the internet APs/BHMs Applicable products PMP : AP PTP: BHM See Isolating AP/BHM from the Internet on page 3-36. Encrypting radio transmissions Applicable products PMP : AP SM PTP: BHM BMS See Encrypting radio transmissions on page 3-36. Page 7-169 Chapter 7: Configuration Configuring security Requiring SM Authentication Applicable products PMP : AP SM Through the use of a shared AP key, or an external RADIUS (Remote Authentication Dial In User Service) server, it enhances network security by requiring SMs to authenticate when they register. For descriptions of each of the configurable security parameters on the AP, see Configuring Security on page 7-180. For descriptions of each of the configurable security parameters on the SM, see Security on page 7-185. Operators may use the APs Authentication Mode field to select from among the following authentication modes:

Disabledthe AP requires no SMs to authenticate (factory default setting). Authentication Server the AP requires any SM that attempts registration to be authenticated in Wireless Manager before registration AP PreShared Key - The AP acts as the authentication server to its SMs and will make use of a user-configurable pre-shared authentication key. The operator enters this key on both the AP and all SMs desired to register to that AP. There is also an option of leaving the AP and SMs at their default setting of using the Default Key. Due to the nature of the authentication operation, if you want to set a specific authentication key, then you MUST configure the key on all of the SMs and reboot them BEFORE enabling the key and option on the AP. Otherwise, if you configure the AP first, none of the SMs is able to register. RADIUS AAA - When RADIUS AAA is selected, up to 3 Authentication Server (RADIUS Server) IP addresses and Shared Secrets can be configured. The IP address(s) configured here must match the IP address(s) of the RADIUS server(s). The shared secret(s) configured here must match the shared secret(s) configured in the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not for splitting the database. If Server 1 doesnt respond, Server 2 is tried, and then server 3. If Server 1 rejects authentication, the SM is denied entry to the network, and does not progress trying the other servers. For more information on configuring the PMP 450 Platform network to utilize a RADIUS server, see Configuring a RADIUS server on page 7-283. Page 7-170 Chapter 7: Configuration Configuring security Filtering protocols and ports Applicable products PMP : AP SM PTP: BHM BMS The filtering protocols and ports allows to configure filters for specified protocols and ports from leaving the AP/SM/BHM/BHS and entering the network. See Filtering protocols and ports on page 3-39. Protocol filtering page of 450 Platform Family AP/BHM The Protocol Filtering page of 450 Platform Family - AP/BHM is explained in Table 114. Table 114 AP/BHM Protocol Filtering attributes Page 7-171 Chapter 7: Configuration Configuring security Attribute Meaning Packet Filter Types For any box selected, the Protocol and Port Filtering feature blocks the associated protocol type. To filter packets in any of the user-defined ports, must do all of the following:

Check the box for User Defined Port n (See Below) in the Packet Filter Types section of this tab. In the User Defined Port Filtering Configuration section of this tab:

provide a port number at Port #n. enable TCP and/or UDP by clicking the associated radio button Filter Direction Operators may choose to filter upstream (uplink) RF packets or downstream (downlink) RF packets. User Defined Port You can specify ports for which to block subscriber access, regardless of Filtering Configuration whether NAT is enabled. RF Telnet Access RF Telnet Access restricts Telnet access to the AP/BHM from a device PPPoE PADI Downlink Forwarding situated below a network SM/BHS (downstream from the AP/BHM). This is a security enhancement to restrict RF-interface sourced AP access specifically to the LAN1 IP address and LAN2 IP address (Radio Private Address, typically 192.168.101.[LUID]). This restriction disallows unauthorized users from running Telnet commands on the AP/BHM that can change AP/BHM configuration or modifying network-critical components such as routing and ARP tables. Enabled: the AP/BHM allows downstream and upstream transmission of PPPoE PADI packets. By default, PPPoE PADI Downlink Forwarding is set to Enabled. Disabled: the AP/BHM disallows PPPoE PADI packets from entering the Ethernet interface and exiting the RF interface (downstream to the SM/BHS). PPPoE PADI packets are still allowed to enter the APs RF interface and exit the APs /BHMs Ethernet interface (upstream). Page 7-172 Chapter 7: Configuration Configuring security Protocol filtering page of SM/BHS The Protocol Filtering page of SM/BHS is explained in Table 115. Table 115 SM/BHS Protocol Filtering attributes Attribute Meaning Packet Filter See Table 114 AP/BHM Protocol Filtering attributes on page 7-171 Configuration tab User Defined Port See Table 114 AP/BHM Protocol Filtering attributes on page 7-171 Filtering Configuration tab Page 7-173 Chapter 7: Configuration Port configuration Configuring security 450 Platform Family ODUs support access to various communication protocols and only the ports required for these protocols are available for access by external entities. Operators may change the port numbers for these protocols via the radio GUI or SNMP. The Port Configuration page of the AP/SM/BHM/BHS is explained in Table 116. Table 116 Port Configuration attributes AP/SM/BHM/BMS Attribute FTP Port Meaning The listen port on the device used for FTP communication. HTTP Port The listen port on the device used for HTTP communication. HTTPS Port The listen port on the device used for HTTPS communication Radius Port The destination port used by the device for RADIUS communication. Radius Accounting The destination port used by the device for RADIUS accounting Port communication. SNMP Port The listen port on the device used for SNMP communication. SNMP Trap Port The destination port used by the device to which SNMP traps are sent. Syslog Server Port The destination port used by the device to which Syslog messaging is sent. Encrypting downlink broadcasts See Encrypting downlink broadcasts on page 3-43. Isolating SMs See Isolating SMs in PMP on page 3-43. Page 7-174 Chapter 7: Configuration Configuring security Filtering management through Ethernet See Filtering management through Ethernet on page 3-43. Allowing management only from specified IP addresses See Allowing management from only specified IP addresses on page 3-44. Restricting radio Telnet access over the RF interface RF Telnet Access restricts Telnet access to the AP from a device situated below a network SM

(downstream from the AP). This is a security enhancement to restrict RF-interface sourced AP access specifically to the LAN1 IP address and LAN2 IP address (Radio Private Address, typically 192.168.101. [LUID]). This restriction disallows unauthorized users from running Telnet commands on the AP that can change AP configuration or modifying network-critical components such as routing and ARP tables. The RF Telnet Access may be configured via the AP GUI or via SNMP commands, and RF Telnet Access is set to Enabled by default. Once RF Telnet Access is set to Disabled, if there is a Telnet session attempt to the AP originating from a device situated below the SM (or any downstream device), the attempt is dropped. This also includes Telnet session attempts originated from the SMs management interface (if a user has initiated a Telnet session to a SM and attempts to Telnet from the SM to the AP). In addition, if there are any active Telnet connections to the AP originating from a device situated below the SM (or any downstream device), the connection is dropped. This behavior must be considered if system administrators use Telnet downstream from an AP (from a registered SM) to modify system parameters. Setting RF Telnet Access to Disabled does not affect devices situated above the AP from accessing the AP via Telnet, including servers running the CNUT (Canopy Network Updater tool) application. Also, setting RF Telnet Access to Disabled does not affect any Telnet access into upstream devices (situated above or adjacent to the AP) through the AP (see Figure 120). The figure below depicts a user attempting two telnet sessions. One is targeted for the AP (orange) and one is targeted for the network upstream from the AP (green). If RF Telnet Access is set to Disabled (factory default setting), the Telnet attempt from the user to the AP is blocked, but the attempt from the user to Network is allowed to pass through the Cambium network. Figure 120 RF Telnet Access Restrictions (orange) and Flow through (green) Page 7-175 Chapter 7: Configuration Configuring security Key Security Considerations when using the RF Telnet Access Feature To ensure that the network is fully protected from unauthorized AP Telnet sessions, the following topics must be considered:

Securing AP Clusters When working with a cluster of AP units, to eliminate potential security holes allowing Telnet access, ensure that the RF Telnet Access parameter is set to Disabled for every AP in the cluster. In addition, since users situated below the AP are able to pass Telnet sessions up through the SM and AP to the upstream network (while AP RF Telnet Access is set to Disabled), ensure that all CMM4 or other networking equipment is secured with strong passwords. Otherwise, users may Telnet to the CMM4 or other networking equipment, and subsequently access network APs (see Figure 121) via their Ethernet interfaces (since RF Telnet Access only prevents Telnet sessions originating from the APs wireless interface). Figure 121 RF Telnet Access Restriction (orange) and Potential Security Hole (green) As a common practice, AP administrator usernames and passwords must be secured with strong, non-default passwords. Restricting AP RF Telnet Access AP Telnet access via the RF interface may be configured in two ways the AP GUI and SNMP. Controlling RF Telnet Access via the AP GUI To restrict all Telnet access to the AP via the RF interface from downstream devices, follow these instructions using the AP GUI:

Procedure 20 Restricting RF Telnet access 1 Log into the AP GUI using administrator credentials 2 On the AP GUI, navigate to Configuration > Protocol Filtering Page 7-176 Chapter 7: Configuration Configuring security 3 Under GUI heading Telnet Access over RF Interface, set RF Telnet Access to Disabled 4 Click the Save button 5 Once the Save button is clicked, all RF Telnet Access to the AP from devices situated below the AP is blocked. Note The factory default setting for RF Telnet Access is disabled and PPPoE PADI Downlink Forwarding is enabled. Page 7-177 Chapter 7: Configuration Configuring security Configuring SNMP Access The SNMPv3 interface provides a more secure method to perform SNMP operations. This standard provides services for authentication, data integrity and message encryption over SNMP. Refer to Planning for SNMPv3 operation on page 3-37 for details. Note The factory default setting for SNMP is SNMPv2c Only. Procedure 21 Configuring SNMPv3 1 Log into the AP GUI using administrator credentials 2 On the AP/SM GUI, navigate to Configuration > Security Page 3 Under GUI heading Security Mode, set SNMP to SNMPv3 Only 4 Click the Save Changes button 5 Go to Configuration > SNMP Page 6 Under GUI heading SNMPv3 setting, set Engine ID, SNMPv3 Security Level, SNMPv3 Authentication Protocol, SNMPv3 Privacy Protocol, SNMPv3 Read-Only User, SNMPv3 Read/Write User, SNMPv3 Trap Configuration parameters:

Engine ID :

Each radio (AP/SM/BHM/BHS) has a distinct SNMP authoritative engine identified by a unique Engine ID. While the Engine ID is configurable to the operator it is expected that the operator follow the guidelines of the SNMPEngineID defined in the SNMP-

FRAMEWORK-MIB (RFC 3411). The default Engine ID is the MAC address of the device. SNMPv3 security level, Authentication and Privacy Protocol The authentication allows authentication of SNMPv3 user and privacy allows for encryption of SNMPv3 message. 450 Platform Family supports MD5 authentication and CBC-DES privacy protocols. Page 7-178 Chapter 7: Configuration Configuring security SNMPv3 Read-Only and Read/Write User The user can defined by configurable attributes. The attributes and default values are:

Read-only user o Username = Canopyro o Authentication Password = authCanopyro o Privacy Password = privacyCanopyro Read-write user (by default read-write user is disabled) o Username = Canopy o Authentication Password = authCanopy o Privacy Password = privacyCanopy SNMPv3 Trap Configuration The traps may be sent from radios in SNMPv3 format based on parameter settings. It can be configured for Disabled, Enabled for Read-Only User, Enable for Read/Write User. Page 7-179 Chapter 7: Configuration Configuring Security Configuring security Applicable products PMP : AP SM PTP: BHM BMS Security page 450 Platform Family AP/BHM The security page of AP/BHM is explained in Table 117. Table 117 Security attributes 450 Platform Family AP Page 7-180 Chapter 7: Configuration Configuring security Attribute Meaning Authentication Mode Operators may use this field to select from among the following authentication modes:

Disabledthe AP/BHM requires no SMs/BHS to authenticate. (Factory default). Authentication Server the AP/BHM requires any SM/BHS that attempts registration to be authenticated in Wireless Manager before registration. AP PreShared Key - The AP/BHM acts as the authentication server to its SMs/BHS and will make use of a user-configurable pre-shared authentication key. The operator enters this key on both the AP/BHM and all SMs/BHS desired to register to that AP/BHM. There is also an option of leaving the AP/BHM and SMs/BHS at their default setting of using the Default Key. Due to the nature of the authentication operation, if you want to set a specific authentication key, then you MUST configure the key on all of the SMs/BHS and reboot them BEFORE enabling the key and option on the AP/BHM. Otherwise, if you configure the AP/BHM first, none of the SMs/BHS is able to register. RADIUS AAA - When RADIUS AAA is selected, up to 3 Authentication Server (RADIUS Server) IP addresses and Shared Secrets can be configured. The IP address(s) configured here must match the IP address(s) of the RADIUS server(s). The shared secret(s) configured here must match the shared secret(s) configured in the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not for splitting the database. If Server 1 doesnt respond, Server 2 is tried, and then server 3. If Server 1 rejects authentication, the SM is denied entry to the network, and does not progress trying the other servers. Note This parameter is applicable to BHM. Page 7-181 Chapter 7: Configuration Configuring security Authentication The management DNS domain name may be toggled such that the Server DNS Usage name of the authentication server only needs to be specified and the DNS domain name is automatically appended to that name. Note This parameter is applicable to BHM. Authentication Enter the IP address or server name of the authentication server Server 1 to 5

(RADIUS or WM) and the Shared Secret configured in the authentication server. When Authentication Mode RADIUS AAA is selected, the default value of Shared Secret is CanopySharedSecret. The Shared Secret may consist of up to 32 ASCII characters. Note This parameter is applicable to BHM. Radius Port This field allows the operator to configure a custom port for RADIUS server communication. The default value is 1812. Note This parameter is applicable to BHM. Authentication Key The authentication key is a 32-character hexadecimal string used when Authentication Mode is set to AP PreShared Key. By default, this key is set to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF. Note This parameter is applicable to BHM. Select Key This option allows operators to choose which authentication key is used:

Use Key above means that the key specified in Authentication Key is used for authentication Use Default Key means that a default key (based off of the SMs MAC address) is used for authentication Note This parameter is applicable to BHM. Dynamic Authorization Extensions for RADIUS Enable CoA and Disconnect Message: Allows to control configuration parameters of SM using RADIUS CoA and Disconnect Message feature. Disable CoA and Disconnect Message: Disables RADIUS CoA and Disconnect Message feature. To enable CoA and Disconnect feature, the Authentication Mode should be set to RADIUS AAA. Bypass Enabled: SM authentication is disabled when SM connects via ICC Authentication for

(Installation Color Code). ICC SMs Disabled: SM authentication is enabled. Encryption Setting Specify the type of airlink security to apply to this AP. The encryption setting must match the encryption setting of the SMs. Page 7-182 Chapter 7: Configuration Configuring security None provides no encryption on the air link. DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. Note This parameter is applicable to BHM. SM Display of AP Allows operators to suppress the display of data about this AP/BHM on Evaluation Data the AP/BHM Evaluation tab of the Tools page in all SMs/BHS that Or BHS Display of BHM register. The factory default setting for SM Display of AP Evaluation Data or BHS Display of BHM Evaluation Data is enabled display. Evaluation Data PMP 450/450i Series SM display of AP Evaluation Data parameter PTP 450/450i Series BHS display of BHM Evaluation Data parameter Web, Telnet, FTP Enter the expiry in seconds for remote management sessions via HTTP, Session Timeout telnet, or ftp access to the AP/BHM. IP Access Control You can permit access to the AP/BHM from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address Allowed Source IP 1 If you selected IP Access Filtering Enabled for the IP Access Control to 3 parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the AP from any IP address. You may populate as many as all three. If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. Page 7-183 Chapter 7: Configuration Configuring security Web Access The Radio supports secured and non-secured web access protocols. Select suitable web access from drop down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. SNMP This option allows to configure SNMP agent communication version. It can be selected from drop down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is a secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. Telnet FTP TFTP This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. Page 7-184 Chapter 7: Configuration Configuring security Security page - 450 Platform Family SM The security page of 450 Platform Family SM is explained in Table 118. Table 118 Security attributes 450 Platform Family SM Page 7-185 Chapter 7: Configuration Configuring security Attribute Meaning Authentication Key Only if the AP to which this SM will register requires authentication, specify the key that the SM will use when authenticating. For alpha characters in this hex key, use only upper case. Select Key The Use Default Key selection specifies the predetermined key for authentication in Wireless Manager The Use Key above selection specifies the 32-digit hexadecimal key that is permanently stored on both the SM and the WM Enforce The SM may enforce authentication types of AAA and AP Pre-

Authentication sharedKey. The SM will not finish the registration process if the AP is not using the configured authentication method (and the SM locks out the AP for 15 minutes). Phase 1 The protocols supported for the Phase 1 (Outside Identity) phase of authentication are EAPTTLS (Extensible Authentication Protocol Tunneled Transport Layer Security) or MSCHAPv2 (Microsoft Challenge-Handshake Authentication Protocol version 2). Page 7-186 Chapter 7: Configuration Configuring security Phase 2 Select the desired Phase 2 (Inside Identity) authentication protocol from the Phase 2 options of PAP (Password Authentication Protocol), CHAP

(Challenge Handshake Authentication Protocol), and MSCHAP

(Microsofts version of CHAP, version 2 is used). The protocol must be consistent with the authentication protocol configured on the RADIUS server. Identity/Realm If Realms are being used, select Enable Realm and configure an outer identity in the Identity field and a Realm in the Realm field. These must match the Phase 1/Outer Identity and Realm configured in the RADIUS server. The default Identity is anonymous. The Identity can be up to 128 non-special (no diacritical markings) alphanumeric characters. The default Realm is canopy.net. The Realm can also be up to 128 non-

special alphanumeric characters. Configure an outer Identity in the Username field. This must match the Phase 1/Outer Identity username configured in the RADIUS server. The default Phase 1/Outer Identity Username is anonymous. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. Username Enter a Username for the SM. This must match the username configured for the SM on the RADIUS server. The default Username is the SMs MAC address. The Username can be up to 128 non-special

(no diacritical markings) alphanumeric characters. Password Enter the desired password for the SM in the Password and Confirm Password fields. The Password must match the password configured for the SM on the RADIUS server. The default Password is password. The Password can be up to 128 non-special (no diacritical markings) alphanumeric characters Upload Certificate To upload a certificate manually to a SM, first load it in a known place File on your PC or network drive, then click on a Delete button on one of the Certificate description blocks to delete a certificate to provide space for your certificate. Click on Choose File, browse to the location of the certificate, and click the Import Certificate button, and then reboot the radio to use the new certificate. When a certificate is in use, after the SM successfully registers to an AP, an indication of In Use will appear in the description block of the certificate being used. The public certificates installed on the SMs are used with the private certificate on the RADIUS server to provide a public/private key encryption system. Up to 2 certificates can be resident on a SM. An installed certificate can be deleted by clicking the Delete button in the certificates description block on the Configuration > Security tab. To restore the 2 default certificates, click the Use Default Certificates button in the RADIUS Certificate Settings parameter block and reboot the radio. Page 7-187 Chapter 7: Configuration Configuring security Encryption Setting Specify the type of airlink security to apply to this SM. The encryption setting must match the encryption setting of the AP. None provides no encryption on the air link. DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. Web, Telnet, FTP Enter the expiry in seconds for remote management sessions via HTTP, Session Timeout telnet, or FTP access to the SM. Ethernet Access If you want to prevent any device that is connected to the Ethernet port of the SM from accessing the management interface of the SM, select Ethernet Access Disabled. This selection disables access through this port to via HTTP (the GUI), SNMP, telnet, FTP, and TFTP. With this selection, management access is available through only the RF interface via either an IP address (if Network Accessibility is set to Public on the SM) or the Session Status or Remote Subscribers tab of the AP. Note This setting does not prevent a device connected to the Ethernet port from accessing the management interface of other SMs in the network. To prevent this, use the IP Access Filtering Enabled selection in the IP Access Control parameter of the SMs in the network. See IP Access Control below. If you want to allow management access through the Ethernet port, select Ethernet Access Enabled. This is the factory default setting for this parameter. IP Access Control You can permit access to the SM from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address Allowed Source IP 1 If you selected IP Access Filtering Enabled for the IP Access Control to 3 parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the SM from any IP address. You may populate as many as all three. Page 7-188 Chapter 7: Configuration Configuring security If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. A subnet mask may be defined for each entry to allow for filtering control based on a range of IP addresses. Web Access The Radio supports secured and non-secured web access protocols. Select suitable web access from drop down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. SNMP This option allows to configure SNMP agent communication version. It can be selected from drop down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. Telnet FTP TFTP This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. Site Name Specify a string to associate with the physical module. Site Contact Enter contact information for the module administrator. Site Location Enter information about the physical location of the module. Enable Security Enable: The Security Banner Notice will be displayed before login. Banner during Login Disable: The Security Banner Notice will not be displayed before login. Security Banner User can enter ASCII (0-9a-zA-Z newline, line-feed are allowed) text up-to Notice 1300 characters. User must accept Enable: login area (username and password) will be disabled unless user security banner accepts the security banner. before login Disable: User cant login to radio without accepting security banner. Page 7-189 Chapter 7: Configuration Configuring security Security page 450 Platform Family BHS The Security page of 450 Platform Family BHS is explained in Table 119. Table 119 Security attributes - 450 Platform Family BHS Attribute Meaning Authentication Key Only if the BHM to which this BHS registers requires an authentication, specify the key that the BHS will use when authenticating. For alpha characters in this hex key, use only upper case. Encryption Setting Specify the type of airlink security to apply to this BHS. The encryption setting must match the encryption setting of the BHM. None provides no encryption on the air link. DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. It is factory default setting. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. Page 7-190 Chapter 7: Configuration Configuring security Web, Telnet, FTP Enter the expiry in seconds for remote management sessions via HTTP, Session Timeout telnet, or FTP access to the BHS. IP Access Control You can permit access to the BHS from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address Allowed Source IP 1 If you selected IP Access Filtering Enabled for the IP Access Control to 3 parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the BHS from any IP address. You may populate as many as all three. If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. A subnet mask may be defined for each entry to allow for filtering control based on a range of IP addresses. Web Access The Radio supports secured and non-secured web access protocols. Select suitable web access from drop down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. SNMP This option allows to configure SNMP agent communication version. It can be selected from drop down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. Telnet FTP TFTP Page 7-191 Chapter 7: Configuration Configuring radio parameters Configuring radio parameters PMP 450m Series Configuring radio on page 7-193 PMP/PTP 450i Series configuring radio on page 7-193 PMP/PTP 450 Series configuring radio on page 7-213 Custom Frequencies page on page 7-230 DFS for 5 GHz Radios on page 7-233 MIMO-A mode of operation on page 7-235 Improved PPS performance of 450 Platform Family on page 7-237 Page 7-192 Chapter 7: Configuration Configuring radio parameters PMP 450m Series Configuring radio Radio page - PMP 450m AP 5 GHz The Radio tab of the PMP 450m AP contains some of the configurable parameters that define how an AP operates. Note Only the frequencies available for your region and the selected Channel bandwidth are displayed. Table 120 PMP 450m AP Radio attributes - 5 GHz Page 7-193 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Frequency Band Select the desired operating frequency band. Frequency Carrier Specify the frequency for the module to transmit. The default for this parameter is None. For a list of channels in the band, see the drop-down list on the radio GUI. Channel Bandwidth The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the AP and the SM. The supported Channel Bandwidth is 20 MHz. Cyclic Prefix OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol to allow multi-

pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. Color Code Specify a value from 0 to 254. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force a SM to register to only a specific AP, even where the SM can communicate with multiple APs. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Subscriber Color This timer may be utilized to initiate SM rescans in order to register to an Code Rescan (When AP configured with the SMs primary color code. not on a Primary Color Code) The time (in minutes) for a subscriber to rescan (if this AP is not configured with the SMs primary color code). This timer will only fire once if the Subscriber Color Code Wait Period for Idle timer is configured with a nonzero value and the Subscriber Color Code Rescan expires, the Subscriber Color Code Wait Period for Idle is started. If the Subscriber Color Code Wait Period for Idle timer is configured with a zero value and the Subscriber Color Code Rescan timer expires, the SM will immediately go into rescan mode Subscriber Color The time (in minutes) for a subscriber to rescan while idle (if this AP is Code Wait Period for not configured with the SMs primary color code). This timer will fire Idle periodic events. The fired event determines if any RF unicast traffic

(either inbound or outbound) has occurred since the last event. If the results of the event determine that no RF unicast traffic has occurred

(SM is idle), then the subscriber will rescan. Page 7-194 Chapter 7: Configuration Configuring radio parameters Installation Color With this feature enabled on the AP and SM, operators may install and Code remotely configure SMs without having to configure matching color codes between the modules. While the SM is accessible for configuration from above the AP (for remote provisioning) and below the SM (for local site provisioning), no user data is passed over the radio link. When using the Installation Color Code feature, ensure that the SM is configured with the factory default Color Code configuration (Color Code 1 is 0, Color Code 2-10 set to 0 and Disable). The status of the Installation Color Code can be viewed on the AP Eval web GUI page, and when the SM is registered using the Installation Color Code the message SM is registered via ICC Bridging Disabled! is displayed in red on every SM GUI page. The Installation Color Code parameter is configurable without a radio reboot for both the AP and SM. If a SM is registered via Installation Color Code and the feature is then disabled, operators will need to reboot the SM or force it to reregister (i.e. using Rescan APs functionality on the AP Eval page). Max Range Enter a number of miles (or kilometers divided by 1.61, then rounded to an integer) for the furthest distance from which a SM is allowed to register to this AP. Do not set the distance to any greater number of miles. A greater distance does not increase the power of transmission from the AP. can reduce aggregate throughput. Regardless of this distance, the SM must meet the minimum requirements for an acceptable link. If the AP is in cluster, then you must set this parameter on all other APs in the cluster exactly the same, except as described in the Downlink Data NOTE admonition below. The default value of this parameter is 2 miles (3.2 km). Downlink Data Specify the percentage of the aggregate throughput for the downlink

(frames transmitted from the AP to the subscriber). For example, if the aggregate (uplink and downlink total) throughput on the AP is 90 Mb, then 75% specified for this parameter allocates 67.5 Mb for the downlink and 22.5 Mb for the uplink. The default for this parameter is 75%. This parameter must be set in the range of 15% - 85%, otherwise the invalid input will not be accepted and the previously-entered valid setting is used. Note In order to prevent self-interference, the frame configuration needs to align which includes Downlink Data, Max Range and Contention slots. For North America Region, the maximum Downlink % for a 5.4 GHz radio is 75% only.. Contention Slots This field indicates the number of (reserved) Contention slots configured

(a.k.a. Control Slots) by the operator. The SM uses reserved Contention slots and unused data slots for bandwidth requests. See Contention slots on page 7-234. Page 7-195 Chapter 7: Configuration Configuring radio parameters EIRP This field indicates the combined power level at which the AP will transmit, based on the Country Code. It also includes the antenna gain and array gain. SM Receive Target Each SMs Transmitter Output Power is automatically set by the AP. The Level AP monitors the received power from each SM, and adjusts each SMs Transmitter Output Power so that the received power at the AP from that SM is not greater what is set in this field. This value represents the transmitted and received power (combined power) perceived on the SM. Receive Quality Debug To aid in link performance monitoring, the AP and SM now report the number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-

QAM and 256-QAM) and per channel (polarization). Note Due to CPU load, this will slightly degrade packet per second processing. Near Field Operation This parameter is enabled by the Near Field Operation control. This is only available when the EIRP is set to 22 dBm or below. When Near Field Operation is enabled, the Near Field Range is used to apply compensation to the units calibration to support operation in the near field. Note The following features are not supported on PMP 450m in current release:

Multicast VC Broadcast Repeat Count Page 7-196 Chapter 7: Configuration Configuring radio parameters PMP/PTP 450i Series configuring radio Radio page - PMP 450i AP 5 GHz The Radio tab of the PMP 450i AP contains some of the configurable parameters that define how an AP operates. Note Only the frequencies available for your region and the selected Channel bandwidth are displayed. Table 121 PMP 450i AP Radio attributes - 5 GHz Page 7-197 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Frequency Band Frequency Carrier See Table 120 PMP 450m AP Radio attributes - 5 GHz on page 7-193 Alternate Frequency These parameters are displayed based on Regional Settings. Refer Carrier 1 and 2 Country on page 7-142 Channel Bandwidth Cyclic Prefix Frame Period Color Code Subscriber Color Code Rescan (When not on a Primary Color Code) Subscriber Color Code Wait Period for Idle Installation Color Code Max Range See Table 120 PMP 450m AP Radio attributes - 5 GHz on page 7-193 Downlink Data See Table 120 PMP 450m AP Radio attributes - 5 GHz on page 7-193 Page 7-198 Chapter 7: Configuration Configuring radio parameters Contention Slots This field indicates the number of (reserved) Contention slots configured

(a.k.a. Control Slots) by the operator. The SM uses reserved Contention slots and unused data slots for bandwidth requests. See Contention slots on page7-234. Broadcast Repeat The default is 2 repeats (in addition to the original broadcast packet, for Count a total of 3 packets sent for every one needed), and is settable to 1 or 0 repeats (2 or 1 packets for every broadcast). ARQ (Automatic Repeat reQuest) is not present in downlink broadcast packets, since it can cause unnecessary uplink traffic from every SM for each broadcast packet. For successful transport without ARQ, the AP repeats downlink broadcast packets. The SMs filter out all repeated broadcast packets and, thus, do not transport further. The default of 2 repeats is optimum for typical uses of the network as an internet access system. In applications with heavy download broadcast such as video distribution, overall throughput is significantly improved by setting the repeat count to 1 or 0. This avoids flooding the downlink with repeat broadcast packets. Transmitter Output This value represents the combined power of the APs two transmitters. Power Nations and regions may regulate transmitter output power. For example 900 MHz, 5.4 GHz and 5.8 GHz modules are available as connectorized radios, which require the operator to adjust power to ensure regulatory compliance. The professional installer of the equipment has the responsibility to maintain awareness of applicable regulations. calculate the permissible transmitter output power for the module. confirm that the initial power setting is compliant with national or regional regulations. confirm that the power setting is compliant following any reset of the module to factory defaults. External Gain This value needs to correspond to the published gain of the antenna used to ensure the radio will meet regulatory requirements. SM Receive Target Level See Table 120 PMP 450m AP Radio attributes - 5 GHz on page 7-193 Multicast VC Data This pull down menu of the Multicast Data Control screen helps in Rate configuring multicast packets to be transmitted over a dedicated channel at a configurable rate of 1X, 2X, 4X or 6X. The default value is Disable. If set to the default value, all multicast packets are transmitted over the Broadcast VC data path. This feature is available only for the PMP 450 Series and is not backward compatible with PMP 430 series of radios. Page 7-199 Chapter 7: Configuration Configuring radio parameters Multicast Repeat This value is the number of packets that are repeated for every multicast Count VC packet received on the AP (located under Radio tab of Configuration). Multicast (like Broadcast) packets go over a VC that is shared by all SMs, so there is no guaranteed delivery. The repeat count is an attempt to improve the odds of the packets getting over the link. If the user has issues with packets getting dropped, they can use this parameter to improve the performance at the cost of the overall throughput possible on that channel. The default value is 0. Multicast Downlink This value is the committed information rate for the multicast downlink CIR VC (located under the Radio tab of Configuration). The default value is 0 kbps. The range of this parameter is based on the number of repeat counts. The higher the repeat count, the lower the range for the multicast downlink CIR. SM Registration All This field allows to control registration of all type 450 Platform Family SM including 430 Series SM(450i/450/430) or 450i Series SM only. PMP 430 SM Registration This field allows to control of PMP 430 SMs whether PMP 430 SMs are allowed to register to PMP 450i APs. By default, it is enabled and PMP 430 SM registrations are accepted. When this field is set to disabled, PMP 430 SMs registrations fail with reject reason 8. This will cause SMs to lock out the AP for 15 minutes. Note This option is not displayed if the Frame Period is set to 5 ms. This option applies only to PMP 450/450i Series APs - 5 GHz. Control Message Controls whether the control messages are sent in MIMO-B or MIMO-A mode. MIMO-A is recommended. However, if an AP on 13.2 is attempting to connect to an SM on 13.1.3 or before, changing to MIMO-

B may aid in getting the SM registered. PMP 450/430 Legacy Disabled: It is factory default setting. It allows to operate in 450i Series mode capabilities. Enabled: It allows to operate radio in Legacy mode PMP 450 or 430. PMP 430 Interop For n-1 compatibility, In SISO mode this forces the AP to only send Mode Control and Beacons over one of the RF paths. Receive Quality To aid in link performance monitoring, the AP and SM now report the Debug number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-

QAM) and per channel (polarization). Note Due to CPU load, this will slightly degrade packet per second processing. Page 7-200 Chapter 7: Configuration Configuring radio parameters Frame Alignment Legacy Mode Mode Behavior (non-900 MHz Behavior (FSK 900 MHz radios) radios) OFF By default frame start is aligned with devices with Timing Port synchronization If the synchronization source changes (due to Autosync or otherwise) the radio will dynamically adjust its frame start to maintain alignment with the default frame start timing The radio will align with ON devices running

(Mode 1) software versions from 12.0 to 13.4. ON

(Mode 2) N/A By default frame start is aligned with FSK 900 MHz devices with Timing Port synchronization If the synchronization source changes (due to Autosync or otherwise) the radio will dynamically adjust its frame start to maintain alignment with the default frame start timing The radio will align with FSK 900 MHz devices running software versions from 12.0 to 13.4. The radio will align with FSK 900 MHz devices with software versions 11.2 or older. Page 7-201 Chapter 7: Configuration Configuring radio parameters Radio page PMP 450i SM 5 GHz The Radio page of PMP 450i SM is explained in Table 122. Table 122 PMP 450i SM Radio attributes 5 GHz Page 7-202 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Custom Radio Check the frequencies that SM has to scan for AP transmissions. See Frequency Scan Radio Frequency Scan Selection List on page 7-227. Selection List Channel Bandwidth The channel size used by the radio for RF transmission. Scan Note Selecting multiple channel bandwidths will increase registration and re-registration times. Cyclic Prefix Scan The cyclic prefix for which AP scanning is executed. AP Selection Method Operators may configure the method by which a scanning SM selects an AP. By default, AP Selection Method is set to Optimize for Throughput, which has been the mode of operation in releases prior to 12.0.3.1. Power Level: AP selection based solely on power level or Optimize for Throughput: AP selection based on throughput optimization the selection decision is based on power level (which affects the modulation state), channel bandwidth (which affects throughput) and number of SM registrations to the AP (which affects system contention performance). Color Code 1 Color code allows you to force the SM to register to only a specific AP, even where the SM can communicate with multiple APs. For registration to occur, the color code of the SM and the AP must match. Specify a value from 0 to 254. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Page 7-203 Chapter 7: Configuration Configuring radio parameters SMs may be configured with up to 20 color codes. These color codes can be tagged as Primary, Secondary, or Tertiary, or Disable. When the SM is scanning for APs, it will first attempt to register to an AP that matches one of the SMs primary color codes. Failing that, the SM will continue scanning and attempt to register to an AP that matches one of the SMs secondary color codes. Failing that, the SM will continue scanning and attempt to register to an AP that matches one of the SMs tertiary color codes. This is all done in the scanning mode of the SM and will repeat until a registration has occurred. Color codes in the same priority group are treated equally. For example, all APs matching one of the SMs primary color codes are analyzed equally. Likewise, this evaluation is done for the secondary and tertiary groups in order. The analysis for selecting an AP within a priority group is based on various inputs, including signal strength and number of SMs already registered to each AP. The first color code in the configuration is the pre-Release 9.5 color code. Thus, it is always a primary color code for legacy reasons. The color codes can be disabled, with the exception of the first color code. Installation Color With this feature enabled on the AP and SM, operators may install and Code remotely configure SMs without having to configure matching color codes between the modules. When using the Installation Color Code feature, ensure that the SM is configured with the factory default Color Code configuration (Color Code 1 is 0, Color Code 2-10 set to 0 and Disable). The status of the Installation Color Code can be viewed on the AP Eval web GUI page, and when the SM is registered using the Installation Color Code the message SM is registered via ICC Bridging Disabled! is displayed in red on every SM GUI page. The Installation Color Code parameter is configurable without a radio reboot for both the AP and SM. External Gain This value represents the antenna gain. For ODUs with integrated antenna, this is set at the correct value in the factory. For Connectorized ODUs with external antenna, the user must set this value to the overall antenna gain, including any RF cable loss between the ODU and the antenna. Large VC data Queue AP and BH have a configurable option used to prevent packet loss in the uplink due to bursting IP traffic. This is designed for IP burst traffic particular to video surveillance applications. Receive Quality To aid in link performance monitoring, the AP and SM now report the Debug number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-

QAM) and per channel (polarization). Page 7-204 Chapter 7: Configuration Configuring radio parameters Note Due to CPU load, this will slightly degrade packet per second processing. Note The frequencies that a user can select are controlled by the country or a region and the Channel Bandwidth selected. There can be a case where a user adds a custom frequency (from the Custom Frequencies page on page 7-230) and cannot see it in the pull down menu. Page 7-205 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450i AP 900 MHz The Radio tab of the PMP 450i AP 900 MHz is described in below table Table 123. Table 123 PMP 450i AP Radio attributes - 900 MHz Page 7-206 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Frequency Carrier Specify the frequency for the module to transmit. The default for this parameter is None. For a list of channels in the band, see the drop-

down list on the radio GUI. Channel Bandwidth The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the AP and the SM. The supported Channel Bandwidths are 5, 7, 10 and 20 MHz. Cyclic Prefix Frame Period Color Code Subscriber Color Code Rescan (When not on a Primary Color Code) Subscriber Color Code Wait Period for Idle Installation Color Code Max Range Downlink Data Contention Slots

(a.k.a. Control Slots) Broadcast Repeat Count Transmitter Output Power External Gain SM Receive Target Level Multicast VC Data Rate Multicast Repeat Count Multicast Downlink CIR Control Message Receive Quality Debug See Table 120 PMP 450m AP Radio attributes - 5 GHz on page 7-193. See Table 120 PMP 450m AP Radio attributes - 5 GHz on page 7-193. See Table 121 PMP 450i AP Radio attributes - 5 GHz on page 7-197. See Table 120 PMP 450m AP Radio attributes - 5 GHz on page 7-193 Pager Reject Filter In 900 MHz, Pager Reject filter is placed on the AP to block Pager signals which could cause interference to the whole band. The Pager signals typically operate in the 928-930 frequency range. When the filter is enabled, the signals of 920 MHz and above are attenuated which enables better reception of signals in the rest of the band. Note that the AP/SM should not be configured on the frequencies of 920 MHz and above when this filter is enabled. Page 7-207 Chapter 7: Configuration Configuring radio parameters Frame Alignment Legacy Mode See Table 121 PMP 450i AP Radio attributes - 5 GHz on page 7-197. Radio page - PTP 450i BHM 5 GHz The Radio page of PTP 450i BHM is explained in Table 124. Table 124 PTP 450i BHM Radio page attributes 5 GHz Page 7-208 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Frequency Band Select the operating frequency band of the radio. The supported bands are 4.9 GHz, 5.4 GHz and 5.7 GHz. Frequency Carrier Specify the frequency for the module to transmit. The default for this parameter is None. For a list of channels in the band, see the drop-down list on the radio GUI. Channel Bandwidth The channel size used by the radio for RF transmission. The setting for the channel bandwidth must match between the BHM and the BHS. Cyclic Prefix OFDM technology uses a cyclic prefix, where a portion of the end of a symbol (slot) is repeated at the beginning of the symbol to allow multi-

pathing to settle before receiving the desired data. A 1/16 cyclic prefix means that for every 16 bits of throughput data transmitted, an additional bit is used. Frame Period Select the Frame Period of the radio. The support Frame Periods are : 5 ms and 2.5 ms. Color Code Specify a value from 0 to 254. For registration to occur, the color code of the BHM and the BHS must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each link a different color code. Color code allows you to force a BHS to register to only a specific BHM. The default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Large VC data Q Enable Large VC Q for applications that burst data high rates. Large Qs may decrease effective throughput for TCP application. Disable Large VC Q if application need not handle bursts of data. Large Qs may decrease effective throughput for TCP application. Downlink Data Specify the percentage of the aggregate throughput for the downlink

(frames transmitted from the BHM to the subscriber). For example, if the aggregate (uplink and downlink total) throughput on the BHM is 132 Mbps, then 75% specified for this parameter allocates 99 Mbps for the downlink and 33 Mbps for the uplink. The default for this parameter is 50%. This parameter must be set in the range of 15% - 85%, otherwise the invalid input will not be accepted and the previously-entered valid setting is used. Note In order to prevent self-interference, the frame configuration needs to align. This includes Downlink Data, Max Range and Contention slots. Transmit Power This value represents the combined power of the BHMs two transmitters. Nations and regions may regulate transmit power. For example Page 7-209 Chapter 7: Configuration Configuring radio parameters PTP 450i Series modules are available as connectorized radios, which require the operator to adjust power to ensure regulatory compliance. The professional installer of the equipment has the responsibility to:

Maintain awareness of applicable regulations. Calculate the permissible transmitter output power for the module. Confirm that the initial power setting is compliant with national or regional regulations. Confirm that the power setting is compliant following any reset of the module to factory defaults. External Gain This value needs to correspond to the published gain of the antenna used to ensure the radio will meet regulatory requirements. Receive Quality To aid in link performance monitoring, the BHM and BHS now report the Debug number of fragments received per modulation (i.e. QPSK, 16-QAM, 64-

QAM and 256-QAM) and per channel (polarization). Note Due to CPU load, this slightly degrades the packet during per second processing. See Table 121 PMP 450i AP Radio attributes - 5 GHz on page 7-197. Frame Alignment Legacy Mode Page 7-210 Chapter 7: Configuration Configuring radio parameters Radio page PTP 450i BHS 5 GHz The Radio page of PTP 450i BHS is explained in Table 125. Table 125 PTP 450i BHS Radio attributes 5 GHz Page 7-211 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Custom Radio Check any frequency that you want the BHS to scan for BHM Frequency Scan transmissions. See Radio Frequency Scan Selection List on page 7-227. Selection List Channel Bandwidth The channel size used by the radio for RF transmission. Scan Note Selecting multiple channel bandwidths will increase registration and re-registration times. Cyclic Prefix Scan The cyclic prefix for which BHM scanning is executed. Color Code Color code allows to force the BHS to register to only a specific BHM, even where the BHS can communicate with multiple BHMs. For registration to occur, the color code of the BHS and the BHM must match. Specify a value from 0 to 254. The color codes can be disabled, with the exception of the first color code. Large VC data Q BHM and BHS have a configurable option used to prevent packet loss in the uplink due to bursting IP traffic. This is designed for IP burst traffic particular to video surveillance applications. Transmit Power Refer Table 124 PTP 450i BHM Radio page attributes 5 GHz on page 7-

208 External Gain Receive Quality Debug Page 7-212 Chapter 7: Configuration Configuring radio parameters PMP/PTP 450 Series configuring radio Radio page - PMP 450 AP 5 GHz The Radio tab of the AP for 5 GHz is as shown in.Table 126. Table 126 PMP 450 AP Radio attributes - 5 GHz Page 7-213 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Radio Configuration, See Table 121 PMP 450i AP Radio attributes - 5 GHz on page 7-197. Frame Configuration, Power Control, Multicast Data Control and Advance tab PMP 430 SM Registration PMP 450/430 Legacy Mode Control Messages PMP 430 Interop Mode Receive Quality Debug Frame Alignment Legacy Mode See Table 121 PMP 450i AP Radio attributes - 5 GHz on page 7-197. Page 7-214 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 AP 3.65 GHz Table 127 PMP 450 AP Radio attributes - 3.65 GHz Attribute Meaning Radio Configuration, See Table 121 PMP 450i AP Radio attributes - 5 GHz on page 7-197. Frame Configuration, Power Control, Multicast Data Control and Advance tab Page 7-215 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 AP 3.5 GHz Table 128 PMP 450 AP Radio attributes - 3.5 GHz Attribute Meaning Radio Configuration, See Table 121 PMP 450i AP Radio attributes - 5 GHz on page 7-197. Frame Configuration, Power Control, Multicast Data Control and Advance tab Page 7-216 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 AP 2.4 GHz Table 129 PMP 450 AP Radio attributes - 2.4 GHz Attribute Meaning Radio Configuration, See Table 121 PMP 450i AP Radio attributes - 5 GHz on page 7-197. Frame Configuration, Power Control, Multicast Data Control and Advance tab Page 7-217 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 SM 5 GHz Table 130 PMP 450 SM Radio attributes 5 GHz Page 7-218 Chapter 7: Configuration Configuring radio parameters Attribute Meaning Custom Radio Check the frequencies that SM has to scan for AP transmissions. See Frequency Scan Radio Frequency Scan Selection List on page 7-227. Selection List See Table 121 PMP 450i AP Radio attributes - 5 GHz on page 7-197. Page 7-219 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 SM 3.65 GHz Table 131 PMP 450 SM Radio attributes 3.65 GHz Attribute Meaning Custom Radio Check the frequencies that SM has to scan for AP transmissions. See Frequency Scan Radio Frequency Scan Selection List on page 7-227. Selection List See Table 121 PMP 450i AP Radio attributes - 5 GHz on page 7-197. Page 7-220 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 SM 3.5 GHz Table 132 PMP 450 SM Radio attributes 3.5 GHz Attribute Meaning Custom Radio Check the frequencies that SM has to scan for AP transmissions. See Frequency Scan Radio Frequency Scan Selection List on page 7-227. Selection List See Table 121 PMP 450i AP Radio attributes - 5 GHz on page 7-197. Page 7-221 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 SM 2.4 GHz Table 133 PMP 450 SM Radio attributes 2.4 GHz Attribute Meaning Custom Radio Check the frequencies that SM has to scan for AP transmissions. See Frequency Scan Radio Frequency Scan Selection List on page 7-227. Selection List See Table 121 PMP 450i AP Radio attributes - 5 GHz on page 7-197. Page 7-222 Chapter 7: Configuration Configuring radio parameters Radio page - PMP 450 SM 900 MHz Table 134 PMP 450 SM Radio attributes 900 MHz Attribute Meaning Custom Radio See Table 121 PMP 450i AP Radio attributes - 5 GHz on page 7-197. Frequency Scan Selection List Channel Bandwidth See Table 121 PMP 450i AP Radio attributes - 5 GHz on page 7-197. Scan Cyclic Prefix Scan AP Selection Method Page 7-223 Chapter 7: Configuration Configuring radio parameters Color Code 1 Installation Color Code Large VC data Queue Color Code External Gain See Table 121 PMP 450i AP Radio attributes - 5 GHz on page 7-197 Receive Quality See Table 121 PMP 450i AP Radio attributes - 5 GHz on page 7-197. Debug Note The frequencies that a user can select are controlled by the country or a region and the Channel Bandwidth selected. There can be a case where a user adds a custom frequency (from the Custom Frequencies page on page 7-230) and cannot see it in the pull down menu. Page 7-224 Chapter 7: Configuration Configuring radio parameters Radio page - PTP 450 BHM 5 GHz Table 135 PTP 450 BHM Radio attributes 5 GHz Attribute Meaning Refer Table 124 PTP 450i BHM Radio page attributes 5 GHz on page 7-208 for all parameters details. Page 7-225 Chapter 7: Configuration Configuring radio parameters Radio page - PTP 450 BHS 5 GHz Table 136 PTP 450 BHM Radio attributes 5 GHz Attribute Meaning Refer Table 125 PTP 450i BHS Radio attributes 5 GHz on page 7-211 for all parameters details. Page 7-226 Chapter 7: Configuration Configuring radio parameters Radio Frequency Scan Selection List The SM or BHS scans complete spectrum as per Full Spectrum Band Scan feature. SMs or BHS first boot into the smallest selected channel bandwidth (10 MHz, if selected) and scan all selected frequencies across both the 5.4 GHz and 5.7 GHz frequency bands. After this scan, if a wider channel bandwidth is selected (20 MHz), the SM/BHS automatically changes to 20 MHz channel bandwidth and then scans for APs/BHSs. After the SM/BHS finishes this final scan it will evaluate the best AP/BHM with which to register. If required for registration, the SM/BHS changes its channel bandwidth back to 10 MHz to match the best AP/BHM. The SM/BHS will attempt to connect to an AP/BHM based on power level (which affects the modulation state), channel bandwidth (which affects throughput) and number of SM/BHS registrations to the AP/BHM (which affects system contention performance). If it is desired to prioritize a certain AP/BHM over other available APs/BHMs, operators may use the Color Code Priority feature on the SM/BHS. Utilization of the Color Code feature on the AP/BHM is recommended to further constrain the AP selection. If the SM does not find any suitable APs/BHMs for registration after scanning all channel bandwidths, the SM restarts the scanning process beginning with the smallest configured channel bandwidth. Selecting multiple frequencies and multiple channel bandwidths impacts the SM/BHS scanning time. The biggest consumption of time is in the changing of the SM/BHS channel bandwidth setting. The worst case scanning time is approximately two minutes after boot up (SM/BHS with all frequencies and channel bandwidths selected and registering to an AP/BHM at 10 MHz). If only one channel bandwidth is selected the time to scan all the available frequencies and register to an AP/BHM is approximately one minute after boot up. Other scanning features such as Color Code, Installation Color Code, and RADIUS authentication are unaffected by the Full Band Scan feature. Dedicated Multicast Virtual Circuit (VC) A Multicast VC allows to configure multicast packets to be transmitted over a dedicated channel at a configurable rate of 1X, 2X, 4X or 8X. This feature is available only for the PMP 450 and PMP 450i and is not backward compatible with PMP 430 series of radios. To configure Multicast VC, the AP must have this enabled. This can be enabled in the Multicast Data Control section (under Configuration > Radio page). The default value is Disable. If set to the default value, all multicast packets are transmitted over the Broadcast VC data path. To enable, select the data rate that is desired for the Multicast VC Data Rate parameter and click Save Changes button. The radio requires no reboot after any changes to this parameter. The multicast VC allows three different parameters to be configured on the AP. These can be changed on the fly and are saved on the flash memory. Page 7-227 Chapter 7: Configuration Configuring radio parameters Note If the Multicast VC Data Rate is set to a modulation that the radio is not currently capable of or operates in non-permitted channel conditions, multicast data is sent but not received. Ex: If Multicast VC Data Rate is set to 6x and the channel conditions only permit 4x mode of operation, then multicast data is sent at 6x modulation but the SM will not receive the data. Note The PMP 450 AP supports up to 119 VCs (instead of 238 VCs) when configured for 30 MHz channel bandwidth or 5 ms Frame Period. This limitation is not applicable for PMP 450i Series. Note Actual Multicast CIR honored by the AP = Configured Multicast CINR/ (Multicast Repeat Count + 1). Increasing the Multicast data rate has no impact on the Unicast data rate. For multicast and unicast traffic mix scenario examples, see Table 137. Table 137 Example for mix of multicast and unicast traffic scenarios Repeat Count Multicast Data Unicast Data Aggregate DL Data Rate (Mbps) Rate (Mbps) Rate (Mbps) 0 1 2 10 5 3.33 40 40 40 50 45 43.33 The statistics have been added to the Data VC page (under Statistics > Data VC). The table displays the multicast row on the PMP 450 Platform Family AP. The SM displays the multicast row if it is a PMP 450 Platform Family. Figure 122 Multicast VC statistics The AP and SM display Transmit and Receive Multicast Data Count (under the Statistics >

Scheduler page), as shown in Figure 123. Page 7-228 Chapter 7: Configuration Configuring radio parameters Figure 123 Multicast scheduler statistics Page 7-229 Chapter 7: Configuration Configuring radio parameters Custom Frequencies page In addition to the Radio tab, AP/SM/BH has another tab called Custom Frequencies as shown in Table 138. The custom frequency tab allows to configure custom frequency at 1 KHz raster. It means that the custom frequencies can be at granularity of 1 KHz e.g. 4910.123 MHz, 4922.333 MHz, 4933.421 MHz etc. Note Ensure that a customer frequency exists before using SNMP to set the radio to a Custom Frequency. Table 138 450 Platform Family AP/SM/BH Custom Frequencies page 5 GHz Attribute Meaning Custom Frequency Custom frequencies with a channel raster of 1 KHz can be added from Configuration the available range by keying in the frequency and then clicking the Add Frequency button. Click Remove Frequency button to delete a specific frequency keyed in the text box. Click Default Frequencies button to add a pre-defined list of frequencies that can be used in this band. This list can be reduced or increased by manually removing or adding other custom frequencies. Custom Frequencies Displays the complete list of user configured custom frequencies. Page 7-230 Chapter 7: Configuration Configuring radio parameters Table 139 PMP/PTP 450 SM/BH Custom Frequencies page 3.65 GHz Attribute Meaning Custom Frequency Custom frequencies with a channel raster of 1 KHz can be added from Configuration the available range by keying in the frequency and then clicking the Add Frequency button. Click Remove Frequency button to delete a specific frequency keyed in the text box. Click Default Frequencies button to add a pre-defined list of frequencies that can be used in this band. This list can be reduced or increased by manually removing or adding other custom frequencies. Custom Frequencies Displays the complete list of user configured custom frequencies. Page 7-231 Chapter 7: Configuration Configuring radio parameters Table 140 PMP/PTP 450 SM/BH Custom Frequencies page 3.5 GHz Attribute Meaning Custom Frequency Custom frequencies with a channel raster of 1 KHz can be added from Configuration the available range by keying in the frequency and then clicking the Add Frequency button. Click Remove Frequency button to delete a specific frequency keyed in the text box. Click Default Frequencies button to add a pre-defined list of frequencies that can be used in this band. This list can be reduced or increased by manually removing or adding other custom frequencies. Page 7-232 Chapter 7: Configuration Configuring radio parameters DFS for 5 GHz Radios Dynamic Frequency Selection (DFS) is a requirement in several countries and regions for 5 GHz unlicensed systems to detect radar systems and avoid co-channel operation. DFS and other regulatory requirements drive the settings for the following parameters, as discussed in this section:

Country Code Primary Frequency Alternate 1 and Alternate 2 Frequencies External Antenna Gain On the AP, the Home > DFS Status page shows current DFS status of all three frequencies and a DFS log of past DFS events. Figure 124 AP DFS Status DFS operation The ODUs use region-specific DFS based on the Country Code selected on the modules Configuration, General page. By directing installers and technicians to set the Country Code correctly, the operator gains confidence the module is operating according to national or regional regulations without having to deal with the details for each region. The details of DFS operation for each Country Code, including whether DFS is active on the AP, SM, and which DFS regulations apply is shown in Table 231 on page 10-37. Page 7-233 Chapter 7: Configuration Contention slots Configuring radio parameters The SM uses reserved Contention slots and unused data slots for bandwidth requests. Uplink Data Slots are used first for data. If they are not needed for data in a given frame, the remaining data slots can be used by the SMs for bandwidth requests. This allows SMs in sectors with a small number of Contention slots configured to still successfully transmit bandwidth requests using unused data slots. A higher number of Contention slots give higher probability that a SMs bandwidth request is correctly received when the system is heavily loaded, but with the tradeoff that sector capacity is reduced, so there is less capacity to handle the request. The sector capacity reduction is about 200 kbps for each Contention slot configured in a 20 MHz channel at QPSK MIMO-A modulation. The reduction in sector capacity is proportionally higher at MIMO-B modulations (2 times at QPSK MIMO-B, 4 times at 16 QAM MIMO-B, 6 times at 64 QAM MIMO-B and 8 times at 256 QAM MIMO-

B). If very few reserved Contention slots are specified, then latency increases in high traffic periods. If too many are specified, then the maximum capacity is unnecessarily reduced. The suggested Contention slot settings as a function of the number of active VCs in the sector are shown in the table below. Table 141 Contention slots and number of VCs Number of VCs Recommended Number of Contention slots 1 to 10 11 to 50 51 to 150 151 and above 3 4 6 8 Note that each SM uses one or two VCs. All SMs have a Low Priority Channel that uses one VC; if the High Priority Channel is enabled for the SM, then the SM uses a second VC. Therefore the number of active VCs in a sector is greater than or equal to the number of SMs registered to the AP in the sector. For example, a network including 20 SMs with High Priority Channel disabled and 20 SMs with High Priority Channel enabled has 60 active VCs and may be configured with 6 Contention slots. In a typical cluster, each AP must be set to the same number of Contention slots to assure proper timing in the send and receive cycles. However, where high incidence of small packets exists, as in a sector that serves several VoIP streams, additional Contention slots may provide better results. For APs in a cluster of mismatched Contention slots setting, or where PMP 450/450i Series is collocated with radios using different technologies, like PMP 430 or FSK, in the same frequency band, use the frame calculator. To download the PMP 450 Contention Slots Paper, see http://www.cambiumnetworks.com/solution-papers/pmp-450-contention-slots. Page 7-234 Chapter 7: Configuration Configuring radio parameters MIMO-A mode of operation 450 Platform Family supports MIMO-B mode using the following modulation levels: QPSK, 16-

QAM, 64-QAM and 256-QAM. System Release 13.2 introduces MIMO-A mode of operation using the same modulation levels as the MIMO-B mode. With MIMO-B, the radio sends different streams of data over the two antennas whereas with MIMO-A, the radio uses a scheme that tries to optimize coverage by transmitting the same data over both antennas. This redundancy improves the signal to noise ratio at the receiver making it more robust, at the cost of throughput. In addition to introducing MIMO-A modes, improvements have been made to the existing rate adapt algorithm to switch between MIMO-A and MIMO-B seamlessly without any intervention or added configuration by the operator. The various modulation levels used by the 450 Platform Family are shown in Table 142. Table 142 450 Platform Family Modulation levels Rate QPSK MIMO-B MIMO-A 2X MIMO-B 1X MIMO-A 16-QAM 4X MIMO-B 2X MIMO-A 64-QAM 6X MIMO-B 3X MIMO-A 265-QAM 8X MIMO-B 4X MIMO-A System Performance For System Performance details of all the 450 Platform Family ODUs please refer below tools:

Link Capacity Planner for PMP/PTP 450 and 450i:

https://support.cambiumnetworks.com/files/capacityplanner/

Link planner for PMP/PTP 450/450i and PMP 450m:

https://support.cambiumnetworks.com/files/linkplanner/

Page 7-235 Chapter 7: Configuration Configuring radio parameters Table 143 Co-channel Interference per (CCI) MCS MCS of Victim MCS of Interferer Channel BW (MHz) CCI 1X (QPSK SISO) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 10 dB 2X (16-QAM SISO) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 17 dB 3X (64-QAM SISO) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 25 dB 1X (QPSK MIMO-A) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 7 dB 2X (16-QAM MIMO-A) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 14 dB 3X (64-QAM MIMO-A) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 22 dB 4X (256-QAM MIMO-A) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 30 dB 2X (QPSK MIMO-B) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 10 dB 4X (16-QAM MIMO-B) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 17 dB 6X (64-QAM MIMO-B) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 25 dB 8X (256-QAM MIMO-B) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 33 dB Table 144 Adjacent Channel Interference (ACI) per MCS MCS of Victim MCS of Interferer Channel BW (MHz) ACI Guard Band 1X (QPSK SISO) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 -16 dB None 2X (16-QAM SISO) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 -16 dB None 3X (64-QAM SISO) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 -16 dB None 1X (QPSK MIMO-A) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 -13 dB None 2X (16-QAM MIMO-A) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 -13 dB None 3X (64-QAM MIMO-A) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 -13 dB None 4X (256-QAM MIMO-A) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 -10 dB None 2X (QPSK MIMO-B) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 -16 dB None 4X (16-QAM MIMO-B) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 -16 dB None 6X (64-QAM MIMO-B) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 -16 dB None 8X (256-QAM MIMO-B) 6X (64-QAM MIMO-B) 5, 7, 10, 15, 20 or 30 -10 dB None Guard Band When synchronized, no Guard Bands are needed for the 450* and 450i Series.

* For PMP 450 AP 3.6 GHz, Configuration -> Radio -> Power Control -> Adjacent Channel Support must be enabled. Page 7-236 Chapter 7: Configuration Configuring radio parameters Improved PPS performance of 450 Platform Family The 450m and 450i Series provides improved packets per second (PPS) performance compared to 450 Series. Through hardware and software enhancements, the PPS performance of the PMP 450i Series AP has been improved to 40k packets/second, measured through a standard RFC2544 test using 64 bytes packets. With this enhancement, operators are able to provide higher bandwidth including better VoIP and video services to end customers using existing SM deployments. PMP 450m supports 100k packets/second. Page 7-237 Chapter 7: Configuration Setting up SNMP agent Setting up SNMP agent Operators may use SNMP commands to set configuration parameters and retrieve data from the AP and SM modules. Also, if enabled, when an event occurs, the SNMP agent on the 450 Platform Family sends a trap to whatever SNMP trap receivers configured in the management network. SNMPv2c SNMPv3 Page 7-238 Chapter 7: Configuration Setting up SNMP agent Configuring SM/BHSs IP over-the-air access To access the SM/BHS management interface from a device situated above the AP, the SM/BHSs Network Accessibility parameter (under the web GUI at Configuration > IP) may be set to Public. Table 145 LAN1 Network Interface Configuration tab of IP page attributes Attribute Meaning IP Address Internet Protocol (IP) address. This address is used by family of Internet protocols to uniquely identify this unit on a network. Network Accessibility Specify whether the IP address of the SM/BHS must be visible to only a device connected to the SM/BHS by Ethernet (Local) or be visible to the AP/BHM as well (Public). Subnet Mask parameter configures the subnet mask of the SM/BHS for RF If Static IP is set as the Connection Type of the WAN interface, then this management traffic. Gateway IP Address parameter configures the gateway IP address for the SM/BHS for RF If Static IP is set as the Connection Type of the WAN interface, then this management traffic. If Enabled is selected, the DHCP server automatically assigns the IP configuration (IP address, subnet mask, and gateway IP address) and the DHCP state values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable (read only), in the Network Interface tab of the Home page. Canopy devices allow for configuration of a preferred and alternate DNS server IP address either automatically or manually. Devices must set DNS IP Address DNS server IP address manually when DHCP is disabled for the management interface of the device. The default DNS IP addresses are 0.0.0.0 when configured manually. Preferred DNS Server The first address used for DNS resolution. Page 7-239 Chapter 7: Configuration Setting up SNMP agent Alternate DNS If the Preferred DNS server cannot be reached, the Alternate DNS Server Server is used. Domain Name The operators management domain name may be configured for DNS. The domain name configuration can be used for configuration of the servers in the operators network. The default domain name is example.com, and is only used if configured as such. Configuring SNMP The SNMP page configuration is explained below. Note The SNMP page for AP, SM, BHM and BHS has the same parameter attributes. SNMP page AP/SM/BHM/BHS The SNMP page is explained in Table 146. Page 7-240 Chapter 7: Configuration Setting up SNMP agent Table 146 SNMP page attributes Page 7-241 Chapter 7: Configuration Setting up SNMP agent Attribute Meaning SNMP Community Specify a control string that can allow a Network Management Station String 1

(NMS) to access SNMP information. No spaces are allowed in this string. The default string is Canopy. SNMP Community You can designate the SNMP Community String 1 to be the password String 1 Permissions for WM, for example, to have Read / Write access to the module via SNMP or for all SNMP access to the module to be Read Only. SNMP Community Specify an additional control string that can allow a Network String 2 (Read Only) Management Station (NMS) to read SNMP information. No spaces are allowed in this string. The default string is Canopyro. This password will never authenticate a user or an NMS to read/write access. The Community String value is clear text and is readable by a packet monitor. Additional security derives from the configuration of the Accessing Subnet, Trap Address, and Permission parameters. Engine ID The Engine ID may be between 5 and 32 hex characters. The hex character input is driven by RFC 3411 recommendations on the Engine ID. The default Engine ID is the MAC address of the device SNMPv3 Security Specify security model where users are defined and authenticated Level before granting access to any SNMP service. Each device can configure the security level of SNMPv3 to No authentication/No privacy, Authentication/No privacy, or Authentication/Privacy. Currently, the SNMPv3 authentication protocol MD5 is supported. SNMPv3 Authentication Protocol SNMPv3 Privacy Currently, the SNMPv3 privacy protocol CBC-DES is supported. Protocol SNMPv3 Read-Only This filed allows for a read-only user per devices. The default values for User the Read-Only users is:

Username = Canopyro Authentication Password = authCanopyro Privacy Password = privacyCanopyro SNMPv3 Read/Write Read-write user by default is disabled. The default values for the User Read/Write users is :

Username = Canopy Authentication Password = authCanopy Privacy Password = privacyCanopy SNMPv3 Trap Configuration When enabling transmission of SNMPv3 traps the read-only or read-

write user credentials must be used and selected properly in order for the SNMP manager to correctly interpret the traps. By default transmission of SNMPv3 traps is disabled and all traps sent from the radios are in SNMPv2c format. Page 7-242 Chapter 7: Configuration Setting up SNMP agent Accessing IP /

Specify the addresses that are allowed to send SNMP requests to this Subnet Mask 1 to 10 AP. The NMS has an address that is among these addresses (this subnet). You must enter both The network IP address in the form xxx.xxx.xxx.xxx The CIDR (Classless Interdomain Routing) prefix length in the form

/xx For example:

the /16 in 198.32.0.0/16 specifies a subnet mask of 255.255.0.0 (the first 16 bits in the address range are identical among all members of the subnet). 192.168.102.0 specifies that any device whose IP address is in the range 192.168.102.0 to 192.168.102.254 can send SNMP requests to the AP, presuming that the device supplies the correct Community String value. The default treatment is to allow all networks access. For more information on CIDR, execute an Internet search on Classless Interdomain Routing. You are allowed to specify as many as 10 different accessing IP address, subnet mask combinations. RECOMMENDATION:

The subscriber can access the SM/BHS by changing the subscriber device to the accessing subnet. This hazard exists because the Community String and Accessing Subnet are both visible parameters. To avoid this hazard, configure the SM/BHS to filter (block) SNMP requests. SNMP Trap Server The management DNS domain name may be toggled such that the DNS Usage name of the trap server only needs to be specified and the DNS domain name is automatically appended to that name. The default SNMP trap server addresses for all 10 available servers is 0.0.0.0 with the appending of the DNS domain name disabled. Trap Address 1 to 10 Specify ten or fewer IP addresses (xxx.xxx.xxx.xxx) or DNS names to which SNMP traps must be sent. Traps inform Wireless Manager or an NMS that something has occurred. For example, trap information is sent after a reboot of the module. when an NMS attempts to access agent information but either supplied an inappropriate community string or SNMP version number. is associated with a subnet to which access is disallowed. Trap Enable, Sync If the sync status traps (sync lost and sync regained) have to be sent to Status Wireless Manager or an NMS, select Enabled. If these traps have to be suppressed, select Disabled. Trap Enable, Session If you want session status traps sent to Wireless Manager or an NMS, Status select Enabled. Page 7-243 Chapter 7: Configuration Setting up SNMP agent Site Information Operators can enable or disable site information from appearing when a Viewable to Guest user is in GUEST account mode. Users Site Name Specify a string to associate with the physical module. This parameter is written into the sysName SNMP MIB-II object and can be polled by Wireless Manager or an NMS. The buffer size for this field is 128 characters. Site Contact Enter contact information for the module administrator. This parameter is written into the sysContact SNMP MIB-II object and can be polled by Wireless Manager or an NMS. The buffer size for this field is 128 characters. Site Location Enter information about the physical location of the module. This parameter is written into the sysLocation SNMP MIB-II object and can be polled by Wireless Manager or an NMS. The buffer size for this field is 128 characters. Page 7-244 Chapter 7: Configuration Configuring syslog Configuring syslog 450 Platform Family includes:

Syslog event logging Configuring system logging Page 7-245 Chapter 7: Configuration Syslog event logging Following events are logged in syslog as explained in Table 147. Table 147 Syslog parameters Attribute Meaning Configuring syslog Timestamp All syslog messages captured from the radio have a timestamp. Configuration This includes any device setting that has changed and includes the old Changes or new parameter value, including the device reboots. User Login and Logout Add or Delete of user Syslog records each user login and logout, with username. accounts through Syslog captures any user accounts that are added or deleted. GUI and SNMP Spectrum Analysis Syslog records a message every time Spectrum Analysis runs. Note Since the AP/BHM must be set to a SM/BHS for Spectrum Analysis, syslog messages are not reported from the radio until the scan is done and the radio mode is switched back to AP/BHM. Link Test Syslog records a message every time a Link Test is run. Clear Statistics SM Register or De-

register BHS Connect or Disconnect Syslog sends a message when Statistics are cleared. This is done individually for each statistics page that is cleared. Syslog records a message when a SM registers or deregisters. Syslog records a message when a BHS connects or disconnects. Configuring system logging To configure system logging, select the menu option Configuration > Syslog. Syslog page of AP/BHM The Syslog Configuration page for AP/BHM is shown in Table 148. Page 7-246 Chapter 7: Configuration Configuring syslog Table 148 Syslog Configuration attributes - AP Attribute Meaning Syslog DNS Server Usage To configure the AP/BHM to append or not append the DNS server name to the syslog server name. Syslog Server The dotted decimal or DNS name of the syslog server address. Syslog Server Port AP Syslog Transmit Or BHM Syslog Transmit The syslog server port (default 514) to which syslog messaging is sent. When enabled, syslog messages are sent from the AP/BHM. SM Syslog Transmit When enabled, syslog messages are sent from all the registered Or BHS Syslog Transmit SMs/BHS, unless they are individually set to override this. This provides a selection for the minimum syslog message severity that is sent to the syslog server. Values range from fatal (highest severity and least verbose) to info (lowest severity, maximum verbosity). For example: If the Syslog Minimum Level is set to notice, then only messages with severity notice and above are sent. Syslog Minimum Level Syslog page of SM To configure system logging, select the menu option Configuration > Syslog. The Syslog Configuration page is shown in Table 149. Page 7-247 Chapter 7: Configuration Configuring syslog Table 149 Syslog Configuration attributes - SM Attribute Meaning Syslog Configuration This control determines whether the SM will attempt to use the syslog Source server definition from the AP, or whether it will use a local server definition. When set to AP preferred, use local when AP configuration unavailable, and if the SM can register with an AP, then it uses the syslog server defined on that AP. If the SM cannot register then it will syslog to its locally defined syslog server through its wired connection, if any. When set to Local only the SM ignores the APs definition of the syslog server and allows the syslog server to be configured individually for each SM. Syslog DNS Server To configure the SM to append or not the DNS server name to the Usage syslog server name. Syslog Server The dotted decimal or DNS name of the syslog server address. Syslog Server Port The syslog server port (default 514) to which syslog messaging is sent. Syslog Transmission Controls the SMs ability to transmit syslog messages. When set to Learn from AP the AP will control whether this SM transmits syslog messages. When set to enable or disable the SM will control whether it sends syslog messages. This allows an operator to override the AP settings for individual SMs in a sector. This control determines whether the SM attempts to use the minimum syslog level defined by the AP, or whether it uses a local defined value using the Syslog Minimum Level parameter. Syslog Minimum Level Source When set to AP preferred, use local when AP configuration unavailable, and if the SM can register with an AP, then it uses the Syslog Minimum Level defined on that AP. If the SM cannot register then it uses its own Syslog Minimum Level setting. When set to Local only the SM will always use its own Syslog Minimum Level setting and ignores the APs setting. Page 7-248 Chapter 7: Configuration Configuring syslog Syslog Minimum Level This provides a selection for the minimum syslog message severity that is sent to the syslog server. Values range from fatal (highest severity and least verbose) to info (lowest severity, maximum verbosity). For example: If the Syslog Minimum Level is set to notice, then only messages with severity notice and above are sent. Syslog page of BHS The Syslog Configuration page is shown in Table 150. Table 150 Syslog Configuration attributes - BHS Attribute Meaning Syslog Configuration This control determines whether the BHS will attempt to use the syslog Source server definition from the BHM, or whether it will use a local server definition. When set to BHM preferred, use local when BHM configuration unavailable, and if the BHS can register with a BHM, then it uses the syslog server defined on that BHM. If the BHS cannot register then it will syslog to its locally defined syslog server through its wired connection, if any. When set to Local only the BHS ignores the BHMs definition of the syslog server and allows the syslog server to be configured individually for each BHS. Syslog DNS Server To configure the BHS to append or not to append the DNS server name Usage to the syslog server name. Syslog Server The dotted decimal or DNS name of the syslog server address. Syslog Server Port The syslog server port (default 514) to which syslog messaging is sent. Syslog Transmission Controls the BHSs ability to transmit syslog messages. When set to Learn from BHM the BHM will control whether this BHS transmits syslog messages. When set to enable or disable the BHS will control Page 7-249 Chapter 7: Configuration Configuring syslog Syslog Minimum Level Source Syslog Minimum Level whether it sends syslog messages. This allows an operator to override the BHM settings for individual BHSs in a sector. This control determines whether the BHS attempts to use the minimum syslog level defined by the BHM, or whether it uses a local defined value using the Syslog Minimum Level parameter. When set to BHM preferred, use local when BHM configuration unavailable, and if the BHS can register with a BHM, then it uses the Syslog Minimum Level defined on that BHM. If the BHS cannot register then it uses its own Syslog Minimum Level setting. When set to Local only the BHS will always use its own Syslog Minimum Level setting and ignores the BHMs setting. This provides a selection for the minimum syslog message severity that is sent to the syslog server. Values range from fatal (highest severity and least verbose) to info (lowest severity, maximum verbosity). For example: If the Syslog Minimum Level is set to notice, then only messages with severity notice and above are sent. Page 7-250 Chapter 7: Configuration Configuring remote access Configuring remote access Accessing SM/BHS over-the-air by Web Proxy The SM/BHS may be accessed via the AP/BHM management GUI by navigating to Home > Session Status (or Home > Remote Subscribers for AP only) and clicking on the SMs hyperlink. For example, to access one of the SMs, click LUID: 002 [0a-00-3e-37-b9-fd], as shown in Figure 125. Figure 125 AP Session Status page The SessionStatus.xml hyper link allows user to export all displayed SM data in Session Status table into an xml file. To access any one of the SMs, click 450 Platform Family - SM hyperlink, as shown in Figure 126. Figure 126 AP Remote Subscribers page Page 7-251 Chapter 7: Configuration Monitoring the Link Monitoring the Link Link monitoring procedure After configuring the link, either an operator in the network office or the SM/BHS INSTALLER user in the field (if read access to the AP/BHM is available to the INSTALLER) must perform the following procedure. Who is authorized and able to do this depends on local operator password policy, management VLAN setup and operational practices. To monitor the link for performance, follow these instructions:

Procedure 22 Monitoring the AP-SM link 1 Access the web interface of the AP/BHM 2 In the left-side menu of the AP/BHM interface, select Home. 3 Click the Session Status tab. Figure 127 Session Status page 4 The Device tab of Session Status List display all displayed SMs MAC address, PMP/PTP Hardware, Software Version, FPGA Version and State Page 7-252 Chapter 7: Configuration Monitoring the Link 5 Click Session Count tab of Session Status List to display values for Session Count, Reg Count, and Re-Reg Count. Session Count: This field displays how many sessions the SM/BHS has had with the AP/BHM. Typically, this is the sum of Reg Count and Re-Reg Count. However, the result of internal calculation may display here as a value that slightly differs from the sum. Reg Count: When a SM/BHS makes a Registration Request, the AP/BHM checks its local session database to see whether it was registered earlier. If the AP/BHM concludes that the SM/BHS is not currently in session database and it is valid Registration Request, then the request increments the value of this field. Re-Reg Count: When a SM/BHS makes a Registration Request, the AP/BHM checks its local session database to see whether it was registered earlier. If the AP/BHM concludes that the SM/BHS is currently in session database, then the request increments the value of this field. Typically, a Re-Reg is the case where both o SM/BHS attempts to reregister for having lost communication with the AP/BHM. o AP/BHM has not yet observed the link to the SM/BHS as being down. See Session tab on page 9-21 6 Click Power tab of Session Status list to display Downlink Rate, AP Rx Power (dBm), Signal Strength Radio (dB) for Uplink and Signal to Noise Radio (dB) for Uplink. See Power tab on page 9-23 7 Click Configuration tab of Session Status list to get QoS configuration details:

Sustained Data Rate (kbps) Burst Allocation (kbit) Max Burst Rate (kbit) Low Priority CIR (kbps) See Configuration tab on page 9-24 8 Briefly monitor these values, occasionally refreshing this page by clicking another tab and then the Session Status tab again. 9 If these values are low (for example, 1, 1, and 0, respectively, meaning that the SM/BHS registered and started a stable session once) and are not changing:

Consider the installation successful. Monitor these values from the network office over the next several hours and days. If these values are greater than 1, 1, and 0, or they increase while you are monitoring them, troubleshoot the link. (For example, Use Receive Power Level for aiming and then use Link Tests to confirm alignment). Refer Viewing Session Status on page 9-20 for more details. Page 7-253 Chapter 7: Configuration Monitoring the Link Exporting Session Status page of AP/BHM The SessionStatus.xml hyper link allows user to export all displayed SMs or BHS data in Session Status table into an xml file. Figure 128 Exporting Session Status page of PMP 450m AP In case of PMP, if the session status page does not list any SM, the SessionStatus.xml will still be visible but the file would be empty. The file will contain data from all of the 5 different tables. Export from command line The scripts users can also get this file from command line, you have to authenticate successfully in order to download the file. Wget http://169.254.1.1/SessionStatus.xml?CanopyUsername=test&CanopyPassword=test Page 7-254 Chapter 7: Configuration Configuring quality of service Configuring quality of service Maximum Information Rate (MIR) Parameters Point-to-multipoint links use the following MIR parameters for bandwidth management:

Sustained Uplink Data Rate (kbps) Uplink Burst Allocation (kb) Sustained Downlink Data Rate (kbps) Downlink Burst Allocation (kb) Max Burst Downlink Data Rate (kbps) Max Burst Uplink Data Rate (kbps) Set each of these parameters per AP or per SM independently. Note You can refer below whitepaper for 450 Platform Family Max Burst MIR:

http://www.cambiumnetworks.com/resources/pmp-450-maxburst/

Token Bucket Algorithm The software uses a token bucket algorithm that has the following features:

Stores credits (tokens) for the SM to spend on bandwidth for reception or transmission. Drains tokens during reception or transmission. Refills with tokens at the sustained rate set by the network operator. For each token, the SM can send toward the network in the uplink (or the AP can send toward the SM in the downlink) an equivalent number of kilobits. Two buckets determine the permitted throughput: one in the SM for uplink and one in the AP for downlink. The applicable set of Uplink Burst Allocation and Downlink Burst Allocation parameters determine the number of tokens that can fill each bucket. When the SM transmits (or the AP transmits) a packet, the equivalent number of tokens is removed from the uplink (or downlink) bucket. Except when full, the bucket is continuously being refilled with tokens at rates that the applicable set of Sustained Uplink Data Rate and Sustained Downlink Data Rate parameters specify. The bucket often drains at a rate that is much faster than the sustained data rate but can refill at only the sustained data rate. Thus, the effects of the allocation and rate parameters on packet delay are as follows:

The burst allocation affects how many kilobits are processed before packet delay is imposed. The sustained data rate affects the packet delay that is imposed. Page 7-255 Chapter 7: Configuration Configuring quality of service MIR Data Entry Checking Uplink and downlink MIR is enforced as shown in Figure 129. Note In these figures, entry refers to the setting in the data rate parameter, not the burst allocation parameter. Figure 129 Uplink and downlink rate caps adjusted to apply aggregate cap For example, in the SM, if you set the Sustained Uplink Data Rate parameter to 2,000 kbps and the Sustained Downlink Data Rate parameter to 10,000 kbps, then the uplink and downlink MIR that is enforced for the SM can be calculated as shown in Figure 130. Figure 130 Uplink and downlink rate cap adjustment example

`

In this example case, the derived 1,167-kbps uplink and 5,833-kbps downlink MIR sum to the fixed 7,000-kbps aggregate cap of the SM. Committed Information Rate (CIR) The Committed Information Rate (CIR) capability feature enables the service provider to guarantee to any subscriber that bandwidth will never decrease to below a specified minimum unless CIR is oversubscribed or RF conditions are degraded. CIR is oversubscribed when there is not enough available bandwidth to support CIR configuration for all subscribers. In this condition, SMs which are configured with a nonzero CIR will all operate at the maximum data rate supported by the link

(subject to Maximum Information Rate and Burst Rate/Allocations). SMs which are configured with a CIR of 0 kbps will not transmit until CIR-configured SMs have completed transmission. CIR may be configured independently for high priority traffic and for low priority traffic. CIR parameters may be configured in the following ways:

Web-based management GUI SNMP Authentication Server (RADIUS) - when a SM successfully registers and authenticates, CIR information is retrieved from the RADIUS server. Page 7-256 uplink cap enforced =uplink entry x aggregate cap for the SMuplink entry + downlink entrydownlink cap enforced =downlink entry x aggregate cap for the SMuplink entry + downlink entryuplink cap enforced =2,000 kbps x 7,000 kbps2,000 kbps + 10,000 kbps= 1,167 kbpsdownlink cap enforced =10,000 kbps x 7,000 kbps2,000 kbps + 10,000 kbps= 5,833 kbps Chapter 7: Configuration Configuring quality of service Active CIR configuration can be verified via the APs Home > Session Status page. Bandwidth from the SM Perspective In the SM, normal web browsing, e-mail, small file transfers and short streaming video are rarely rate limited with practical bandwidth management (QoS) settings. When the SM processes large downloads such as software upgrades and long streaming video or a series of medium-size downloads, the bucket rapidly drains, the burst limit is reached, and some packets are delayed. The subscriber experience is more affected in cases where the traffic is more latency sensitive. Interaction of Burst Allocation and Sustained Data Rate Settings If the Burst Allocation is set to 1200 kb and the Sustained Data Rate is set to 128 kbps, a data burst of 1000 kb is transmitted at full speed because the Burst Allocation is set high enough. After the burst, the bucket experiences a significant refill at the Sustained Data Rate. This configuration uses the advantage of the settable Burst Allocation. If both the Burst Allocation and the Sustained Data Rate are set to 128 kb, a burst is limited to the Burst Allocation value. This configuration does not take advantage of the settable Burst Allocation. If the Burst Allocation is set to 128 kb and the Sustained Data Rate is set to 256 kbps, the actual rate is the burst allocation (but in kbps). As above, this configuration does not take advantage of the settable Burst Allocation. High-priority Bandwidth To support low-latency traffic such as VoIP (Voice over IP) or video, the system implements a high-

priority channel. This channel does not affect the inherent latencies in the system but allows high-

priority traffic to be immediately served. The high-priority pipe separates low-latency traffic from traffic that is latency tolerant, such as standard web traffic and file downloads. The number of channels available on the AP is reduced by the number of SMs configured for the high-priority channel (each SM operating with high-priority enabled uses two channels (virtual circuits) instead of one). A module prioritizes traffic by reading the Low Latency bit (Bit 3) in the IPv4 Type of Service (ToS) byte in a received packet. Bit 3 is set by a device outside the system. reading the 802.1p field of the 802.1Q header in a received packet, where VLAN is enabled on the module. comparing the 6-bit Differentiated Services Code Point (DSCP) field in the ToS byte of a received packet to a corresponding value in the Diffserv tab of the Configuration page of the module. A packet contains no flag that indicates whether the encoding is for the Low Latency bit or the DSCP field. For this reason, you must ensure that all elements in your trusted domain, including routers and endpoints, set and read the ToS byte with the same scheme. Modules monitor ToS bytes with DSCP fields, but with the following differences:

The 6-bit length of the field allows it to specify one of 64 service differentiations. Page 7-257 Chapter 7: Configuration Configuring quality of service These correlate to 64 individual (CodePoint) parameters in the Diffserv tab of the Configuration page. Per RFC 2474, 3 of these 64 are preset and cannot be changed. (See http://www.faqs.org/rfcs/rfc1902.html.) For any or all of the remaining 61 CodePoint parameters, you can specify a value of o 0 through 3 for low-priority handling. o 4 through 7 for high-priority handling. Note Ensure that your Differentiated Services domain boundary nodes mark any entering packet, as needed, so that it specifies the appropriate Code Point for that traffic and domain. This prevents theft of service level. An example of the Diffserv page in the Configuration menu and parameter descriptions are provided under DiffServ attributes AP/BHM on page 7-132. This tab and its rules are identical from module type to module type. However, any of the 61 configurable Code Points can be set to a different value from module to module, thus defining unique per-hop behavior for some traffic. This tab in the AP sets the priorities for the various packets in the downstream (sent from the public network). This tab in the SM sets the priorities for the various packets in the upstream (sent to the public network). Typically, some SMs attach to older devices that use the ToS byte as originally formatted, and others to newer devices that use the DSCP field. The default values in the Diffserv page allow your modules to prioritize traffic from the older devices roughly the same as they traditionally have. However, these default values may result in more high-priority traffic as DSCP fields from the newer devices are read and handled. So, after making changes in the Diffserv page, carefully monitor the high-priority channel for high packet rates in SMs that you have identified as those to initially set and watch. across your network when you have broadly implemented Code Point values, such as via SNMP. Page 7-258 Chapter 7: Configuration Traffic Scheduling Configuring quality of service The characteristics of traffic scheduling in a sector are summarized in Table 151. Table 151 Characteristics of traffic scheduling Category Factor Throughput Aggregate throughput, less additional overhead Latency Number of frames required for the scheduling process Round-trip latency Treatment 132 Mbps 1 6 ms AP broadcast the download schedule No High-priority Allocation for uplink high-priority traffic Dynamic, based on amount of high-

Channel on amount of high-priority traffic priority traffic Allocation for downlink high-priority traffic Dynamic, based on amount of high-

on amount of high-priority traffic priority traffic Order of transmission CIR high-priority CIR low-priority Other high-priority Other low-priority Caution Power requirements affect the recommended maximums for power cord length feeding the CMM4. See the dedicated user guide that supports the CMM that you are deploying. Packets that have a priority of 4 to 7 in either the DSCP or a VLAN 802.1p tag are automatically sent on the high-priority channel, but only where the high-priority channel is enabled. Page 7-259 Chapter 7: Configuration Configuring quality of service Setting the Configuration Source The AP includes a Configuration Source parameter, which sets where SMs that register to the AP are controlled for MIR, CIR, VLAN, and the high-priority channel as follows. The Configuration Source parameter affects the source of:

all MIR settings:

o Sustained Uplink Data Rate o Uplink Burst Allocation o Max Burst Uplink Data Rate o Sustained Downlink Data Rate o Downlink Burst Allocation o Max Burst Downlink Data Rate all CIR settings:

o Low Priority Uplink CIR o Low Priority Downlink CIR o Hi Priority Uplink CIR o Hi Priority Downlink CIR all SM VLAN settings o Dynamic Learning o Allow Only Tagged Frames o VLAN Aging Timeout o Untagged Ingress VID o Management VID o VLAN Membership the Hi Priority Channel setting Table 152 Recommended combined settings for typical operations Most operators who must set this in this web page/tab in the AP to use parameter no authentication server Authentication Mode Configuration/ Security Disabled Configuration Source Configuration/ General SM Wireless Manager Authentication Mode Configuration/ Security Authentication Server

(Authentication Server) RADIUS AAA server Configuration Source Configuration/ General Authentication Server Authentication Mode Configuration/ Security RADIUS AAA Configuration Source Configuration/ General Authentication Server Page 7-260 Chapter 7: Configuration Configuring quality of service Table 153 Where feature values are obtained for a SM with authentication required Configuration Source Setting in the AP Values are obtained from MIR Values VLAN Values High Priority Channel State Authentication Authentication Authentication Authentication Server SM Server SM Server SM Server SM Authentication Authentication Authentication Authentication Server+SM Server Server, then SM Server, then SM Note HPC represents the Hi Priority Channel (enable or disable). Where Authentication Server, then SM is the indication, parameters for which Authentication Server does not send values are obtained from the SM. This is the case where the Authentication Server is operating on an Authentication Server release that did not support the feature. This is also the case where the feature enable/disable flag in Authentication Server is set to disabled. The values are those previously set or, if none ever were, then the default values. Where Authentication Server is the indication, values in the SM are disregarded. Where SM is the indication, values that Authentication Server sends for the SM are disregarded. For any SM whose Authentication Mode parameter is not set to Authentication Required, the listed settings are derived as shown in Table 154. Table 154 MIR, VLAN, HPC, and CIR Configuration Sources, Authentication Disabled Configuration Source Setting in the AP Values are obtained from MIR Values VLAN Values High Priority CIR Values Channel State AP SM SM AP SM SM AP SM SM Authentication AP Server SM Authentication Server+SM SM SM Page 7-261 Chapter 7: Configuration Configuring quality of service Configuring Quality of Service (QoS) Quality of Service (QoS) page of AP The QoS page of AP is explained in Table 155. Table 155 QoS page attributes - AP Attribute Meaning Max Burst Uplink These parameters allow operators to specify the data rate at which a SM Data Rate is allowed to transmit (until burst allocation limit is reached) before being recharged at the Sustained Uplink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. Sustained Uplink Specify the rate that each SM registered to this AP is replenished with Data Rate credits for transmission. This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on page 7-255 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-257 Configuration Source on page 7-141 Uplink Burst Allocation Specify the maximum amount of data to allow each SM to transmit before being recharged at the Sustained Uplink Data Rate with credits to transmit more. See Maximum Information Rate (MIR) Parameters on page 7-255 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-257 Configuration Source on page 7-141 Page 7-262 Chapter 7: Configuration Configuring quality of service Max Burst Downlink These parameters allow operators to specify the data rate at which a SM Data Rate is allowed to transmit (until burst allocation limit is reached) before being recharged at the Sustained Downlink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. Sustained Downlink Specify the rate at which the AP is replenished with credits (tokens) for Data Rate transmission to each of the SMs in its sector. This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on page 7-255 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-257 Configuration Source on page 7-141 Downlink Burst Specify the maximum amount of data to allow the AP to transmit to any Allocation registered SM before the AP is replenished with transmission credits at the Sustained Downlink Data Rate. See Maximum Information Rate (MIR) Parameters on page 7-255 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-257 Configuration Source on page 7-141 Broadcast Downlink Broadcast Downlink CIR (Committed Information Rate, a minimum) CIR supports system designs where downlink broadcast is desired to have higher priority than other traffic. For many other system designs, especially typical internet access networks, leave the Broadcast Downlink CIR at the default. Broadcast Downlink CIR is closely related to the Broadcast Repeat Count parameter, which is settable in the Radio tab of the Configuration page in the AP: when the Broadcast Repeat Count is changed, the total of available bandwidth is also changed, since packets are being sent one, two, or three times, according to the setting in the Broadcast Repeat Count parameter. Priority Precedence Allows operator to decide if 802.1p or DiffServ priority bits must be used first when making priority decisions. PPPoE Control Operators may configure the SM to utilize the high priority channel for Message Priority PPPoE control messages. Configuring the SM in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the SM. Prioritize TCP ACK To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. Page 7-263 Chapter 7: Configuration Configuring quality of service Quality of Service (QoS) page of SM The QoS page of SM is explained in Table 156. Table 156 QoS page attributes - SM Attribute Meaning Sustained Uplink Specify the rate that this SM is replenished with credits for transmission. Data Rate This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on page 7-255 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-257 Configuration Source on page 7-141 Sustained Downlink Specify the rate at which the AP is replenished with credits (tokens) for Data Rate transmission to this SM. This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on Page 7-255 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-257 Configuration Source on page 7-141 Uplink Burst Allocation Specify the maximum amount of data to allow this SM to transmit before being recharged at the Sustained Uplink Data Rate with credits to transmit more. See Maximum Information Rate (MIR) Parameters on page 7-255 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-257 Page 7-264 Chapter 7: Configuration Configuring quality of service Configuration Source on page 7-141 Downlink Burst Specify the maximum amount of data to allow the AP to transmit to this Allocation SM before the AP is replenished at the Sustained Downlink Data Rate with transmission credits. See Maximum Information Rate (MIR) Parameters on page 7-255 Interaction of Burst Allocation and Sustained Data Rate Settings on page 7-257 Configuration Source on page 7-141 Max Burst Uplink These parameters allow operators to specify the data rate at which a SM Data Rate is allowed to transmit (until burst allocation limit is reached) before being recharged at the Sustained Uplink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. Max Burst Downlink These parameters allow operators to specify the data rate at which a SM Data Rate is allowed to transmit (until burst allocation limit is reached) before being recharged at the Sustained Downlink Data Rate with credits to transit more. When set to 0 (default), the burst rate is unlimited. Enable Broadcast /

This parameter allows the operator to specify if Broadcast and Multicast Multicast Data Rate data is rate-limited. This data rate can be entered in Kbps or PPS

(Packets Per Second). Broadcast / Multicast This parameter allows the operator to specify a data rate at which Data Rate Broadcast and Multicast traffic is sent via the radio link. Low Priority Uplink This field indicates the minimum rate at which low priority traffic is sent CIR over the uplink (unless CIR is oversubscribed or RF link quality is degraded). Committed Information Rate (CIR) on page 7-256 Setting the Configuration Source on page 7-260 Low Priority Downlink CIR This field indicates the minimum rate at which low priority traffic is sent over the downlink (unless CIR is oversubscribed or RF link quality is degraded). Committed Information Rate (CIR) on page 7-256 Setting the Configuration Source on page 7-260 Hi Priority Channel See High-priority Bandwidth on page 7-257 Configuration Source on page 7-141 Hi Priority Uplink CIR This field indicates the minimum rate at which high priority traffic is sent over the uplink (unless CIR is oversubscribed or RF link quality is degraded). Committed Information Rate (CIR) on page 7-256 Setting the Configuration Source on page 7-260 Page 7-265 Chapter 7: Configuration Configuring quality of service Hi Priority Downlink This field indicates the minimum rate at which high priority traffic is sent CIR over the downlink (unless CIR is oversubscribed or RF link quality is degraded). Committed Information Rate (CIR) on page 7-256 Setting the Configuration Source on page 7-260 Priority Precedence Allows operator to decide if 802.1p or DiffServ priority bits must be used first when making priority decisions. PPPoE Control Operators may configure the SM to utilize the high priority channel for Message Priority PPPoE control messages. Configuring the SM in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the SM. Prioritize TCP ACK To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. This parameter, when enabled, can be particularly useful when running bi-direction FTP sessions over the link. If a link is primarily used for video surveillance, it is recommended to configure this parameter to Disabled. Quality of Service (QoS) page of BHM The QoS page of BHM is explained in Table 157. Table 157 QoS page attributes - BHM Attribute Meaning PPPoE Control Operators may configure the BHM to utilize the high priority channel for Message Priority PPPoE control messages. Configuring the BHM in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the BHS. Prioritize TCP ACK To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. This parameter, when enabled, can be particularly useful when running bi-direction FTP sessions over the link. If a link is primarily used for video surveillance, it is recommended to configure this parameter to Disabled. Page 7-266 Chapter 7: Configuration Configuring quality of service Quality of Service (QoS) page of BHS The QoS page of BHS is explained in Table 158. Table 158 QoS page attributes - BHS Attribute Meaning PPPoE Control Operators may configure the BHS to utilize the high priority channel for Message Priority PPPoE control messages. Configuring the BHS in this fashion can benefit the continuity of PPPoE connections when there are issues with PPPoE sessions being dropped in the network. This prioritization may be configured in the DiffServ tab in the Configuration menu of the BHS. Prioritize TCP ACK To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. This parameter, when enabled, can be particularly useful when running bi-direction FTP sessions over the link. If a link is primarily used for video surveillance, it is recommended to configure this parameter to Disabled. Page 7-267 Chapter 7: Configuration Installation Color Code Installation Color Code With this feature enabled on the AP and SM, operators may install and remotely configure SMs without having to configure matching color codes between the modules. While the SM is accessible for configuration from above the AP (for remote provisioning) and below the SM (for local site provisioning), no user data is passed over the radio link. When using the Installation Color Code feature, ensure that the SM is configured with the factory default Color Code configuration (Color Code 1 is 0, Color Code 2-10 set to 0 and Disable). The status of the Installation Color Code can be viewed on the AP Eval web GUI page, and when the SM is registered using the Installation Color Code the message SM is registered via ICC Bridging Disabled! is displayed in red on every SM GUI page. The Installation Color Code parameter is configurable without a radio reboot for both the AP and SM. If an SM is registered via Installation Color Code and the feature is then disabled, operators will need to reboot the SM or force it to reregister (i.e. using the Rescan APs functionality on the AP Eval page). Figure 131 Installation Color Code of AP Page 7-268 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66 Zero Touch Configuration Using DHCP Option 66 This feature allows an SM to get its configuration via DHCP option 66. This can be used for the initial configuration of an SM as well as managing the configuration of SMs on an ongoing basis. Here is how it works in brief:

When the SM boots up, if it is set to use DHCP client, it will send out a DHCP Discover packet which includes a request for DHCP Option 66. In case of a brand new SM out of the box, the DHCP Discover packet is sent out if the SM connects to an AP using Installation Color Code (ICC), even though DHCP client is not enabled in factory default config. An appropriately configured DHCP server will respond with a DHCP Offer and include a URL in response to the Option 66 request. The URL should point to the configuration file. The device will download the configuration file and apply it. The device will reboot automatically if needed. (Note: this requires rebootIfRequired flag to be added to the config file. See Creating a Golden config file on page 7-270. Configuration Steps Procedure 23 Zero Touch Configuration steps 1 Create the golden config file(s) 2 Host it on an TFTP/FTP/HTTP/HTTPS server 3 Configure the DHCP server to return the URL of the golden config file in option 66 When the SM boots up, it will get the URL for the golden config from the DHCP server via option 66, download it and apply it. If all the SMs are configured exactly the same, then you can create just new golden config file that can be used with all SMs. If the SMs are not configured the same, see if it is possible to group the SMs such that SMs with the same configuration are served by the same DHCP pool. User can then create multiple golden config files and configure the DHCP server to use the appropriate config file for each pool. User can also create one config file per SM. This provides the most flexibility, but is practical only if you have a software tool/script to generate the config files for each MAC address. The files should be named <mac>.cfg where <mac> is the MAC address of the SM, and stored in the same directory on the file server. The DHCP server should be configured to return the directory name ending with a / in option 66. The SM will automatically add <mac>.cfg to the path and get its config file. Page 7-269 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66 If some configuration is unique per SM, but rest of the configuration is common, the SMs can be staged with the unique part, and use option 66 to manage the common part. For example, if each SM needs to have its coordinates set, dont include the coordinates in the golden config file. Instead, configure the coordinates for each SM manually. Manage the rest of the configuration using DHCP option 66. Creating a Golden config file The easiest way to create the golden config file is to configure an SM, export its configuration and edit it. To export the configuration file from the GUI of the SM, go to Configuration > Unit Settings tab, go to the Download Configuration File section and click on the <mac>.cfg link. This will give you a text file in JSON format. You can edit this file in a text editor but its easier to use a JSON editor like https://www.jsoneditoronline.org/. Strip down the config file to remove sections and entries that dont care about, and keep only the items that require changes. If there are many required changes, it can easily get confusing. To identify the exact items changes, first reset the SM to factory default, export the config file, make the necessary changes, export a second config file, then use a tool like WinMerge

(http://winmerge.org/) to identify the differences. The config file contains the following informational entries at the top level.

"cfgUtcTimestamp": "cfgUtcTimestamp",

"swVersion": "CANOPY 13.3 (Build 15) SM-AES",

"cfgFileString": "Canopy configuration file",

"srcMacAddress": "0a-00-3e-a2-c2-74",

"deviceType": "5.4/5.7GHz MIMO OFDM - Subscriber Module",

"cfgFileVersion": "1.0"

The cfgUtcTimestamp, swVersion, srcMacAddress and deviceType lines can be deleted. Do not delete the cfgFileString and cfgFileVersion entries. Next, create an object named configFileParameters at the top level. Under that, add a parameter called rebootIfRequired and set it to true. This tells the SM to reboot automatically if a reboot is needed to apply the new configuration. A sample configuration file that has been edited for use via DHCP option 66 is given below.

{

"userParameters": {

"smNetworkConfig": {

"networkAccess": 1

},

"location": {

"siteName": "Test site"

},

"smRadioConfig": {

Page 7-270 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66

"frequencyScanList": [

5475000, 5480000

],

"colorCodeList": [

{

"colorCode": 42,

"priority": 1

}

]

},

"networkConfig": {

"lanDhcpState": 1

}

},

"cfgFileVersion": "1.0",

"cfgFileString": "Canopy configuration file",

"configFileParameters": {

"rebootIfRequired": true

}

}

When configuration is imported, only the items that exist in the configuration file are modified. Parameters that are not in the imported file are not changed. If user wish to revert those settings to their factory default values, please add a setToDefaults item under configFileParameters section with a value of true.

"cfgFileVersion": "1.0",

"cfgFileString": "Canopy configuration file",

"configFileParameters": {

"rebootIfRequired": true,

"setToDefaults": true

}

In case, the SM needs to fetch the configuration file on each boot up even when not connecting to AP via ICC, set Network Accessibility to Public and DHCP State to Enabled in the Configuration > IP page before exporting the configuration. Hosting the config file Copy the golden configuration file to an FTP, TFTP, HTTP or HTTPS server. This location can be password protected; you just have to include the user name and password in the URL. DHCP server configuration Configure DHCP server to return the full URL to the golden config file as the value of DHCP option 66. Page 7-271 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66 The following example explains how to make the change for Windows Server 2008. Adapt it to your specific DHCP server. Procedure 24 DHCP server configuration 1 Click Start > Administrative Tools > DHCP 2 If you have multiple Scopes defined, identify the correct Scope that will serve IP addresses for the SMs 3 Right click on Scope Option under the correct Scope and select Configure Options Page 7-272 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66 4 In the Scope Options dialog, scroll down to 066 Boot Server Host Name, select the checkbox and enter the full URL to the golden config file as the String value. Then click OK. 5 In the DHCP snap-in window, right click and Refresh to see the DHCP option 66 in the list of DHCP options Supported URL Formats FTP, TFTP, HTTP and HTTPS URLs are supported. Some examples are given below. ftp://10.120.163.253/canopy.cfg ftp://admin:admin123@10.120.163.253/canopy.cfg (login as admin with password admin123) tftp://10.120.163.253/canopy.cfg http://10.120.163.253/golden-config.cfg https://10.120.163.253/smconfig/golden-config.cfg User can also specify the URL pointing to a directory and not a specific file. Terminate the URL with a / to indicate that it is a directory and not a file. Use this format when each SM has its own individual config file. The directory should contain files named <mac>.cfg, one for each SM. For example:

ftp://10.120.163.253/smconfig/

Page 7-273 Chapter 7: Configuration Zero Touch Configuration Using DHCP Option 66 In this case, the SM will append <mac>.cfg to the path and try to get that file. For example, if the SMs MAC address is 0a-00-3e-a2-c2-74, it will request for ftp://10.120.163.253/smconfig/0a003ea2c274.cfg. This mechanism can be used to serve individual config file for each SM. Troubleshooting 1 Ensure that the___14 SM is running 13.3 or newer version of software. 2 If the SM has factory default config, confirm ICC is enabled on the AP, so the SM can connect to it. 3 If the SM is connecting to the AP using a color code other than ICC, make sure the SM has Network Accessibility set to Public and DHCP State set to Enabled in the Configuration > IP page. 4 Make sure the golden config file does not turn off Network Accessibility or DHCP State. If it does, the SM will no longer request the config file when it is rebooted. 5 Check the event log of the SM to see the status of the configuration file import including any errors that prevented it from importing the file. 6 Capture the DHCP Offer packet from the DHCP server to the SM and verify that Option 66 has the expected URL. Page 7-274 Chapter 7: Configuration Configuring Radio via config file Configuring Radio via config file The 450 Platform Family supports export and import of a configuration file from the AP or SM as a text file. The configuration file is in JSON format. To export or import the configuration file, the logged in user needs to be an ADMINISTRATOR and it must not be a read-only account. The exported configuration file contains the complete configuration including all the default values. To keep a backup of the current configuration, the file can be saved as-is and imported later. While importing a configuration file, it can be either imported the full configuration or a sparse configuration containing only the items that need to be changed. If a sparse configuration file is imported, only the items in the file will be imported. Other configuration will remain unchanged. There could also be used a special flag in the configuration file to tell the device to apply the configuration starting from factory default (Refer Special Headers for configuration file on page 7-

276). Import and Export of config file The config file import and export is supported in Configuration > Unit Settings page. The procedure for importing and exporting config file is explained below. Figure 132 Configuration File upload and download page The DHCP server configuration procedure is as follows:

Procedure 25 DHCP server configuration 1 Login to the GUI and go to Configuration > Unit Settings. 2 Under Download Configuration File tab, click on the <mac>.cfg link, where <mac> is the MAC address of the device (for example, 01003ea2c274.cfg). 3 Save the file to the local disk. The below procedure is to be followed for Importing a config file Page 7-275 Chapter 7: Configuration Configuring Radio via config file Procedure 26 Import the configuration from the GUI 1 Login to the GUI and go to Configuration Unit Settings. 2 Click on Browse button under Upload and Apply Configuration File tab and select the configuration file from disk. 3 Click Upload followed by Apply Configuration File button click. 4 The Status of Configuration File section will show the results of the upload. 5 Review it to make sure there are no errors. Then click on Reboot to reboot with the imported configuration The special headers for config file is explained below:

Procedure 27 Special Headers for configuration file 1 A "configFileParameters" section can be added to the header to control the behavior of the device when importing configuration. 2 The "setToDefaults" when set to "true" tell the device to reset to factory default configuration and apply the configuration in the file on top of that. So any attribute not in the configuration file will be set to its factory default value. By default, the configuration in the file is merged with the existing configuration on the device. The "rebootIfRequired" flag when set to "true" tell the device to reboot automatically if needed to apply the configuration change. By default, the device will not reboot automatically.

{

"cfgFileString": "Canopy configuration file",

"cfgFileVersion": "1.0",

"configFileParameters": {

"setToDefaults":true,

"rebootIfRequired":true,

}

}

Page 7-276 Chapter 7: Configuration Configuring cnMaestroTM Connectivity Configuring cnMaestroTM Connectivity 450 Platform Family network can be onboarded, configured and managed using cnMaestro Cloud or On Premises Server. Note cnMaestro is not currently supported on 450m. Onboarding Onboarding can be done in one of several ways:

Using Cambium ID and Onboarding key Using Manufacturers Serial Number (Only if it starts with an M and is 12 characters long) On Premises Zero Touch onboarding of AP/SM using DHCP option 43 and 15 PMP SM Zero touch onboarding to the cnMaestro server where PMP AP is onboarded. To configure the PMP devices, enable Remote Management under Configuration->cnMaestro as shown in Table 159. Table 159 Configuring cnMaestro Attribute Remote Meaning This field enables/disables remote management of 450 Platform Family Management products. cnMaestro URL This field allows to enter cnMaestro URL e.g. https://cloud.cambiumnetworks.com Or cnMaestro on premises URL Connection Status This field indicates cnMaestro connectivity status. Cambium ID This field allows to enter Cambium ID for onboarding 450 Platform devices. Onboarding Key This field allows to enter Onboarding Key for onboarding. Page 7-277 Chapter 7: Configuration Configuring cnMaestroTM Connectivity AccountID This field indicates Account ID of the customer. Device Agent This field shows device agent version. Version Prerequisites for onboarding to cnMaestro Devices types must be PMP 450m Series, PMP/PTP 450 Series, PMP/PTP 450i Series or PMP 430 Series SMs (interoperability mode only). Minimum required software version of 14.2.1. Device software images can be downloaded from http://support.cambiumnetworks.com or from the On Premises cnMaestro server by navigating to Operate >Software Update->Manage Images. Select Device type to display the available images and then click the download icon as shown in Figure 133. Figure 133 Software Upgrade from cnMaestro IP connectivity between PMP Device and the cnMaestro server is established. Ensure Port 443 is open in the firewall as this port is used for secure communication between the PMP device and the cnMaestro server through web sockets. In addition, if the PMP device and cnMaestro server are on different subnets, proper routes should be established for communication. For PMP AP, a valid DNS setting is required so that the AP will be able to resolve the cnMaestro URL. DNS settings can be verified by performing a DNS lookup under Tools->DNS Test on the AP as shown in Figure 134. Page 7-278 Chapter 7: Configuration Configuring cnMaestroTM Connectivity Figure 134 DNS Test for cnMaestro connectivity If the SM is in Bridge mode, then LAN1 must have public accessbility with a public IP assigned and corresponding DNS setting. If the SM is in NAT mode, then Remote Management should be enabled with the standalone configuration option and DNS settings. Knowledge Based articles for onboarding For onboarding the devices to cloud server and troubleshooting the onboarding issues in cloud server please see the following link:

http://community.cambiumnetworks.com/t5/cnMaestro/Device-On-boarding/td-p/51484 For onboarding the devices to on Premises server and configuring the DHCP server options for on boarding please see the following link:

http://community.cambiumnetworks.com/t5/cnMaestro/Device-Onboarding-and-Linux-DHCP-

Options-for-cnMaestro-On/m-p/55187#U55187 Order of Device Onboarding The device discovery order is as follows in On Permises cnMaestro Server. If any of the options is not configured, the discovery method will fallback to the next option:

1. Static cnMaestro URL 2. Zero Touch token (on boarding of PMP SMs when the corresponding AP is on boarded) 3. DHCP Option 43 4. DHCP Option 15 5. https://cloud.cambiumnetworks.com Page 7-279 Chapter 7: Configuration Device Agent Logs Configuring cnMaestroTM Connectivity For debugging any onboarding issues please check the device agent logs by navigating to Logs-

>Device Agent Logs on the PMP device GUI as shown in Figure 135. In addition, a tech support dump can for the PMP device can be obtained from cnMaestro by navigating to Monitor->Tools menu after selecting the particular PMP device in the tree and clicking the tech support file icon. This can be send to Cambium support for further troubleshooting. Figure 135 Device Agent Logs Monitoring Tools for PMP Devices on cnMaestro cnMaestro as of this release offers several debugging tools for PMP devices. Some examples are:

Pictorial view of network hierarchy Device status Tech support file Throughput Alarms Reboot Debug Logs Network connectivity ping and DNS lookup Page 7-280 Chapter 7: Configuration Configuring cnMaestroTM Connectivity Figure 136 Example cnMaestro screenshot For more information on these tools please see http://community.cambiumnetworks.com/t5/cnMaestro/How-to-use-the-cnMaestro-Tools-for-

Troubleshooting-Device-or/m-p/54503#U54503 Zero Touch on boarding of the PMP SMs when the corresponding AP is on boarded First a link should be established between the PMP AP and SM either by configuring manually or using the ICC. Once the AP and SM link is established, the AP must be onboarded to cnMaestro using one of several ways detailed above under the Onboarding section. Once the AP is onboarded to cnMaestro Cloud or On premises cnMaestroserver, the SMs under the AP will automatically onboard to cnMaestro using a Zero touch token that is communicated between the AP and SMs. This is applicable to existing SMs registered to the AP as well as new SMs registering to the AP for the first time. The SMs appear on the onboarding queue of cnMaestro and the operator must Approve the devices in order to manage them. The following operations for PMP Devices are available on cnMaestro Monitor the device details in the Dashboard page by navigating to the Monitor >Dashboard menu and selecting the PMP AP/SM in the tree. Monitor notifications related to the PMP AP/SM by navigating to the Monitor >Notifications Menu and selecting the PMP AP/SM in the tree. Monitor device statistics on the statistics page by navigating to the Monitor >Statistics menu and selecting the PMP AP/SM in the tree, then selecting the PMP AP or PMP SM in the Device type dropdown. Monitor Performance graphs related to the PMP AP/SM by navigating to the Monitor

>Performance menu and selecting the required performance graph (i.e Throughput, SMs, Modulation) and selecting the PMP AP/SM in the tree. Troubleshoot the device on the Troubleshooting page by navigating to the Monitor >Tools menu and selecting the PMP AP/SM in the tree. Page 7-281 Chapter 7: Configuration Configuring cnMaestroTM Connectivity Configure the devices by navigating to the Configure >Devices menu and selecting the PMP AP/SM in the tree and selecting the config template that needs to be pushed to the device. Configuration templates need to be created before the configuration can be pushed to the device. The template can be created by copying the existing configuration from the view device configuration link provided in the same page and then modifying the template as needed and then pushing to the same device or other similar devices. Template needs to be properly reviewed for IP Address and other critical parameters to avoid stranding SMs

(resulting in a truck roll) by pushing an incorrect configuration. Configuration templates can be created by navigating to the Configure->Templates page and selecting the PMP device type while creating the template. Once on 14.2.1, PMP devices can be upgraded to future supported versions from cnMaestro by navigating to the Operate > Software Update page and selecting the PMP Sectors option from the device type drop down and the version to which the device needs to be upgraded. It is recommended to upgrade the AP first, then the SMs. PMP Device Inventory details can be reviewed by navigating to the Monitor >Inventory page. Page 7-282 Chapter 7: Configuration Configuring a RADIUS server Configuring a RADIUS server Configuring a RADIUS server in a PMP 450 Platform network is optional, but can provide added security, increase ease of network management and provide usage-based billing data. Understanding RADIUS for PMP 450 Platform Family PMP 450 Platform modules include support for the RADIUS (Remote Authentication Dial In User Service) protocol supporting Authentication and Accounting. RADIUS Functions RADIUS protocol support provides the following functions:

SM Authentication allows only known SMs onto the network (blocking rogue SMs), and can be configured to ensure SMs are connecting to a known network (preventing SMs from connecting to rogue APs). RADIUS authentication is used for SMs, but is not used for APs. SM Configuration: Configures authenticated SMs with MIR (Maximum Information Rate), CIR

(Committed Information Rate), High Priority, and VLAN (Virtual LAN) parameters from the RADIUS server when a SM registers to an AP. SM Accounting provides support for RADIUS accounting messages for usage-based billing. This accounting includes indications for subscriber session establishment, subscriber session disconnection, and bandwidth usage per session for each SM that connects to the AP. Centralized AP and SM user name and password management allows AP and SM usernames and access levels (Administrator, Installer, Technician) to be centrally administered in the RADIUS server instead of on each radio and tracks access events

(logon/logoff) for each username on the RADIUS server. This accounting does not track and report specific configuration actions performed on radios or pull statistics such as bit counts from the radios. Such functions require an Element Management System (EMS) such as Cambium Networks Wireless Manager. This accounting is not the ability to perform accounting functions on the subscriber/end user/customer account. Framed IP allows operators to use a RADIUS server to assign management IP addressing to SM modules (framed IP address). Tested RADIUS Servers The Canopy RADIUS implementation has been tested and is supported on FreeRADIUS, Version 2.1.8 Aradial RADIUS, Version 5.1.12 Microsoft RADIUS (Windows Server 2012 R2 version) Cisco ACS, Version 5.7.0.15 Page 7-283 Chapter 7: Configuration Configuring a RADIUS server Note Aradial 5.3 has a bug that prevents remote device login, so doesnt support the user name and password management feature. Choosing Authentication Mode and Configuring for Authentication Servers - AP On the APs Configuration > Security tab, select the RADIUS AAA Authentication Mode. The following describes the other Authentication Mode options for reference, and then the RADIUS AAA option. Disabled: Requires no authentication. Any SM (except a SM that itself has been configured to require RADIUS authentication by enabling Enforce Authentication as described below) is allowed to register to the AP. Authentication Server: Authentication Server in this instance refers to Wireless Manager in BAM-only mode. Authentication is required for a SM to register to the AP. Only SMs listed by MAC address in the Wireless Manager database is allowed to register to the AP. AP Pre-Shared Key: Canopy offers a pre-shared key authentication option. In this case, an identical key must be entered in the Authentication Key field on the APs Configuration >

Security tab and in the Authentication Key field on each desired SMs Configuration >

Security tab. RADIUS AAA: To support RADIUS authentication of SMs, on the APs Configuration >

Security tab select RADIUS AAA. Only properly configured SMs with a valid certificate is allowed to register to the AP. When RADIUS AAA is selected, up to 3 Authentication Server (RADIUS Server) IP addresses and Shared Secrets can be configured. The IP address(s) configured here must match the IP address(s) of the RADIUS server(s). The shared secret(s) configured here must match the shared secret(s) configured in the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not splitting the database. If Server 1 doesnt respond, Server 2 is tried, and then server 3. If Server 1 rejects authentication, the SM is denied entry to the network, and does not progress trying the other servers. The default IP address is 0.0.0.0. The default Shared Secret is CanopySharedSecret. The Shared Secret can be up to 32 ASCII characters (no diacritical marks or ligatures, for example). Page 7-284 Chapter 7: Configuration Configuring a RADIUS server Table 160 Security tab attributes Page 7-285 Chapter 7: Configuration Configuring a RADIUS server Attribute Meaning Authentication Mode Operators may use this field to select the following authentication modes:

Disabledthe AP requires no SMs to authenticate. Authentication Server the AP requires any SM that attempts registration to be authenticated in Wireless Manager before registration. AP PreShared Key - The AP acts as the authentication server to its SMs and will make use of a user-configurable pre-shared authentication key. The operator enters this key on both the AP and all SMs desired to register to that AP. There is also an option of leaving the AP and SMs at their default setting of using the Default Key. Due to the nature of the authentication operation, if you want to set a specific authentication key, then you MUST configure the key on all of the SMs and reboot them BEFORE enabling the key and option on the AP. Otherwise, if you configure the AP first, none of the SMs is able to register. RADIUS AAA - When RADIUS AAA is selected, up to 3 Authentication Server (RADIUS Server) IP addresses and Shared Secrets can be configured. The IP address(s) configured here must match the IP address(s) of the RADIUS server(s). The shared secret(s) configured here must match the shared secret(s) configured in the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not for splitting the database. If Server 1 doesnt respond, Server 2 is tried, and then server 3. If Server 1 rejects authentication, the SM is denied entry to the network and does not progress trying the other servers. Authentication Server DNS Usage The management DNS domain name may be toggled such that the name of the authentication server only needs to be specified and the DNS domain name is automatically appended to that name. Authentication Server 1 Authentication Server 2 Authentication Server 3 Enter the IP address or server name of the authentication server

(RADIUS or WM) and the Shared Secret configured in the authentication server. When Authentication Mode RADIUS AAA is selected, the default value of Shared Secret is CanopySharedSecret. The Shared Secret Authentication may consist of up to 32 ASCII characters. Server 4 (BAM Only) Authentication Server 5 (BAM Only) Radius Port This field allows the operator to configure a custom port for RADIUS server communication. The default value is 1812. Authentication Key The authentication key is a 32-character hexadecimal string used when Authentication Mode is set to AP Pre-Shared Key. By default, this key is set to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF. Page 7-286 Chapter 7: Configuration Configuring a RADIUS server Selection Key This option allows operators to choose which authentication key is used:

Use Key above means that the key specified in Authentication Key is used for authentication Use Default Key means that a default key (based off of the SMs MAC address) is used for authentication Encryption Key Specify the type of airlink security to apply to this AP. The encryption setting must match the encryption setting of the SMs. None provides no encryption on the air link. DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. SM Display of AP You can use this field to suppress the display of data about this AP on Evaluation Data the AP Evaluation tab of the Tools page in all SMs that register. Web, Telnet, FTP Enter the expiry in seconds for remote management sessions via HTTP, Session Timeout telnet, or ftp access to the AP. IP Access Control You can permit access to the AP from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address Allowed Source IP 1 If you selected IP Access Filtering Enabled for the IP Access Control parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the AP from any IP address. You may populate as many as all three. Allowed Source IP 2 If you selected IP Access Filtering Disabled for the IP Access Control Allowed Source IP 3 parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. Web Access The Radio supports secured and non-secured web access protocols. Select suitable web access from drop down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. HTTPS Only provides a secured web access. The radio to be accessed via https1://<IP of Radio>. Page 7-287 Chapter 7: Configuration Configuring a RADIUS server HTTP and HTTPS If enabled, the radio can be accessed via both http and https. SNMP This option allows to configure SNMP agent communication version. It can be selected from drop down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. Telnet FTP TFTP This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. Page 7-288 Chapter 7: Configuration Configuring a RADIUS server SM Authentication Mode Require RADIUS or Follow AP If it is desired that a SM will only authenticate to an AP that is using RADIUS, on the SMs Configuration Security tab set Enforce Authentication to AAA. With this enabled, SM does not register to an AP that has any Authentication Mode other than RADIUS AAA selected. If it is desired that a SM use the authentication method configured on the AP it is registering to, set Enforce Authentication to Disabled. With Enforce Authentication disabled, a SM will attempt to register using whichever Authentication Mode is configured on the AP it is attempting to register to. Note Having SMs to use RADIUS by enabling Enforce Authentication avoids the security issue of SMs possibly registering to rogue APs, which have authentication disabled. Table 161 SM Security tab attributes Page 7-289 Chapter 7: Configuration Configuring a RADIUS server Attribute Meaning Authentication Key Authentication Mode is set to AP PreShared Key. By default, this key is The authentication key is a 32-character hexadecimal string used when set to 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF. This option allows operators to choose which authentication key is used:

Use Key above means that the key specified in Authentication Key is Select Key used for authentication Use Default Key means that a default key (based off of the SMs MAC address) is used for authentication The SM may enforce authentication types of AAA and AP Pre-

Enforce sharedKey. The SM will not finish the registration process if the AP is not Authentication using the configured authentication method (and the SM locks out the AP for 15 minutes). Enforce Authentication default setting is Disable. The protocols supported for the Phase 1 (Outside Identity) phase of authentication are EAPTTLS (Extensible Authentication Protocol Tunneled Transport Layer Security) or MSCHAPv2 (Microsoft Challenge-Handshake Authentication Protocol version 2). Select the desired Phase 2 (Inside Identity) authentication protocol from the Phase 2 options of PAP (Password Authentication Protocol), CHAP

(Challenge Handshake Authentication Protocol), and MSCHAP

(Microsofts version of CHAP, version 2 is used). The protocol must be consistent with the authentication protocol configured on the RADIUS server. Phase 1 Phase 2 Page 7-290 Chapter 7: Configuration Configuring a RADIUS server Identity/Realm Username If Realms are being used, select Enable Realm and configure an outer identity in the Identity field and a Realm in the Realm field. These must match the Phase 1/Outer Identity and Realm configured in the RADIUS server. The default Identity is anonymous. The Identity can be up to 128 non-special (no diacritical markings) alphanumeric characters. The default Realm is canopy.net. The Realm can also be up to 128 non-

special alphanumeric characters. Configure an outer Identity in the Username field. This must match the Phase 1/Outer Identity username configured in the RADIUS server. The default Phase 1/Outer Identity Username is anonymous. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. Enter a Username for the SM. This must match the username configured for the SM on the RADIUS server. The default Username is the SMs MAC address. The Username can be up to 128 non-special

(no diacritical markings) alphanumeric characters. Password Enter the desired password for the SM in the Password and Confirm Password fields. The Password must match the password configured for the SM on the RADIUS server. The default Password is password. Confirm Password The Password can be up to 128 non-special (no diacritical markings) alphanumeric characters. Upload Certificate File To upload a certificate manually to a SM, first load it in a known place on your PC or network drive, then click on a Delete button on one of the Certificate description blocks to delete a certificate to provide space for your certificate. Click on Choose File, browse to the location of the certificate, and click the Import Certificate button, and then reboot the radio to use the new certificate. When a certificate is in use, after the SM successfully registers to an AP, an indication of In Use will appear in the description block of the certificate being used. The public certificates installed on the SMs are used with the private certificate on the RADIUS server to provide a public/private key encryption system. Up to 2 certificates can be resident on a SM. An installed certificate can be deleted by clicking the Delete button in the certificates description block on the Configuration > Security tab. To restore the 2 default certificates, click the Use Default Certificates button in the RADIUS Certificate Settings parameter block and reboot the radio. Page 7-291 Chapter 7: Configuration Configuring a RADIUS server Specify the type of airlink security to apply to this AP. The encryption setting must match the encryption setting of the SMs. None provides no encryption on the air link. DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of Encryption Setting data. DES encryption does not affect the performance or throughput of the system. AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES products are certified as compliant with the Federal Information Processing Standards (FIPS 197) in the U.S.A. Web, Telnet, FTP Enter the expiry in seconds for remote management sessions via HTTP, Session Timeout telnet or ftp access to the AP. If you want to prevent any device that is connected to the Ethernet port of the SM from accessing the management interface of the SM, select Ethernet Access Disabled. This selection disables access through this port to via HTTP (the GUI), SNMP, telnet, FTP, and TFTP. With this selection, management access is available through only the RF interface Ethernet Access via either an IP address (if Network Accessibility is set to Public on the SM) or the Session Status or Remote Subscribers tab of the AP. See IP Access Control below. If you want to allow management access through the Ethernet port, select Ethernet Access Enabled. This is the factory default setting for this parameter. You can permit access to the AP from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses IP Access Control that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address Allowed Source IP 1 If you selected IP Access Filtering Enabled for the IP Access Control Allowed Source IP 2 parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the AP from any IP address. You may populate as many as all three. Allowed Source IP 3 If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. Web Access The Radio supports secured and non-secured web access protocols. Select suitable web access from drop down list:

HTTP Only provides non-secured web access. The radio to be accessed via http://<IP of Radio>. Page 7-292 Chapter 7: Configuration Configuring a RADIUS server HTTPS Only provides a secured web access. The radio to be accessed via https://<IP of Radio>. HTTP and HTTPS If enabled, the radio can be accessed via both http and https. SNMP This option allows to configure SNMP agent communication version. It can be selected from drop down list :

SNMPv2c Only Enables SNMP v2 community protocol. SNMPv3 Only Enables SNMP v3 protocol. It is secured communication protocol. SNMPv2c and SNMPv3 It enables both the protocols. Telnet FTP TFTP This option allows to Enable and Disable Telnet access to the Radio. This option allows to Enable and Disable FTP access to the Radio. This option allows to Enable and Disable TFTP access to the Radio. SM - Phase 1 (Outside Identity) parameters and settings The protocols supported for the Phase 1 (Outside Identity) phase of authentication are eapttls (Extensible Authentication Protocol Tunneled Transport Layer Security) and eapMSChapV2 (Extensible Authentication Protocol Microsoft Challenge-Handshake Authentication Protocol). Configure an outer Identity in the Username field. This must match the Phase 1/Outer Identity username configured in the RADIUS server. The default Phase 1/Outer Identity Username is anonymous. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. If Realms are being used in the RADIUS system (eapttls only), select Enable Realm and configure an outer identity in the Identity field and a Realm in the Realm field. These must match the Phase 1/Outer Identity and Realm configured in the RADIUS server. The default Identity is anonymous. The Identity can be up to 128 non-special (no diacritical markings) alphanumeric characters. The default Realm is canopy.net. The Realm can also be up to 128 non-

special alphanumeric characters. SM - Phase 2 (Inside Identity) parameters and settings If using eapttls for Phase 1 authentication, select the desired Phase 2 (Inside Identity) authentication protocol from the Phase 2 options of PAP (Password Authentication Protocol), CHAP (Challenge Handshake Authentication Protocol), and MSCHAPv2 (Microsofts version of CHAP). The protocol must be consistent with the authentication protocol configured on the RADIUS server. Enter a Username for the SM. This must match the username configured for the SM on the RADIUS server. The default Username is the SMs MAC address. The Username can be up to 128 non-special (no diacritical markings) alphanumeric characters. Enter the desired password for the SM in the Password and Confirm Password fields. The Password must match the password configured for the SM on the RADIUS server. The default Password is password. The Password can be up to 128 non-special (no diacritical markings) alphanumeric characters. Page 7-293 Chapter 7: Configuration Configuring a RADIUS server Handling Certificates Managing SM Certificates via the SM GUI The default public Canopy certificates are loaded into SMs upon factory software installation. The default certificates are not secure and are intended for use during lab and field trials as part of gaining experience with the RADIUS functionalities or as an option during debug. For secure operation, an operator will want to create or procure their own certificates. Resetting a SM to its factory defaults will remove the current certificates and restore the default certificates. Up to two certificates can be resident on a SM. An installed certificate can be deleted by clicking the Delete button in the certificates description block on the Configuration > Security tab. To restore the 2 default certificates, click the Use Default Certificates button in the RADIUS Certificate Settings parameter block and reboot the radio. To upload a certificate manually to a SM, first load it in a known place on your PC or network drive, then click on a Delete button on one of the Certificate description blocks to delete a certificate to provide space for your certificate. Click on Choose File, browse to the location of the certificate, and click the Import Certificate button, and then reboot the radio to use the new certificate. When a certificate is in use, after the SM successfully registers to an AP, an indication of In Use will appear in the description block of the certificate being used. The public certificates installed on the SMs are used with the private certificate on the RADIUS server to provide a public/private key encryption system. Note Root certificates of more than one level (Example - a certificate from someone who received their CA from Verisign) fails. Certificates must be either root or self-signed. Page 7-294 Chapter 7: Configuration Configuring a RADIUS server Figure 137 SM Certificate Management Configuring RADIUS servers for SM authentication Your RADIUS server must be configured to use the following:

EAPTTLS or MSCHAPv2 as the Phase 1/Outer Identity protocol. If Enable Realm is selected on the SMs Configuration > Security tab, then the same Realm appears there (or access to it). The same Phase 2 (Inner Identity) protocol as configured on the SMs Configuration >

Security tab under Phase 2 options. The username and password for each SM configured on each SMs Configuration > Security tab. An IP address and NAS shared secret that is the same as the IP address and Shared Secret configured on the APs Configuration > Security tab for that RADIUS server. Page 7-295 Chapter 7: Configuration Configuring a RADIUS server A server private certificate, server key, and CA certificate that complement the public certificates distributed to the SMs, as well as the Canopy dictionary file that defines Vendor Specific Attributes (VSAa). Default certificate files and the dictionary file are available from the software site: https://support.cambiumnetworks.com/files/pmp450 after entering your name, email address, and either Customer Contract Number or the MAC address of a module covered under the 12 month warranty. Optionally, operators may configure the RADIUS server response messages (Accept or Reject) so that the user has information as to why they have been rejected. The AP displays the RADIUS Authentication Reply message strings in the Session Status list as part of each SMs information. The SM will show this string (listed as Authentication Response on the SM GUI) on the main Status page in the Subscriber Module Stats section. Note Aradial AAA servers only support operator-configurable Authentication Accept responses, not Authentication Reject responses. Page 7-296 Chapter 7: Configuration Configuring a RADIUS server Assigning SM management IP addressing via RADIUS Operators may use a RADIUS AAA server to assign management IP addressing to SM modules

(framed IP address). SMs now interpret attributes Framed-IP-Address, Framed-IP-Netmask, and Cambium-Canopy-Gateway from RADIUS. The RADIUS dictionary file has been updated to include the Cambium-Canopy-Gateway attribute and is available on the Cambium Software Support website. In order for these attributes to be assigned and used by the SM, the following must be true:

The system is configured for AAA authentication The SM is not configured for DHCP on its management interface. If DHCP is enabled and these attributes are configured in the RADIUS server, the attributes is ignored by the SM. The SM management interface must be configured to be publically accessible. If the SM is configured to have local accessibility, the management interface will still be assigned the framed addressing, and the SM iscome publicly accessible via the assigned framed IP addressing. When using these attributes, for the addressing to be implemented by the SM operators must configure Framed-IP-Address in RADIUS. If Framed-IP-Address is not configured but Framed-

IP-Netmask and/or Cambium-Canopy-Gateway is configured, the attributes is ignored. In the case where only the Framed-IP-Address is configured, Framed-IP-Netmask defaults to 255.255.0.0 (NAT disabled) / 255.255.255.0 (NAT enabled) and Cambium-Canopy-Gateway defaults to 0.0.0.0. Configuring RADIUS server for SM configuration Canopy Vendor Specific Attributes (VSAs) along with VSA numbers and other details are listed in Table 162. The associated SM GUI page, tab and parameter are listed to aid cross-referencing and understanding of the VSAs. A RADIUS dictionary file is available from the software site:

https://support.cambiumnetworks.com/files/pmp450 The RADIUS dictionary file defines the VSAs and their values and is usually imported into the RADIUS server as part of server and database setup. Page 7-297 Chapter 7: Configuration Configuring a RADIUS server Note Beginning with System Release 12.0.2, two RADIUS dictionary files are available on the Cambium website RADIUS Dictionary file Cambium and RADIUS Dictionary file Motorola. In addition to a renaming of attributes, the Cambium-branded dictionary file contains two new VSAs for controlling uplink and downlink Maximum Burst Data Rate (these VSAs are listed below in Table 162). If you are transitioning from the Motorola-branded dictionary file to the Cambium-

branded dictionary file, ensure that all RADIUS profiles containing Motorola-Canopy attribute references are updated to include Cambium-Canopy attribute references (for all applicable VSAs listed in Table 162). Also, ensure that all RADIUS configuration files reference the new dictionary file (as an alternative, operators may rename the Cambium-branded dictionary file to the filename currently in use by the RADIUS server). Once the profiles are updated and the new Cambium-branded dictionary file is installed on the RADIUS server, restart the RADIUS server to ensure that the new VSAs and attribute names are enabled. Table 162 RADIUS Vendor Specific Attributes (VSAs) Name MS-MPPE-Send-Key

*

-

MS-MPPE-Recv-Key

*

-

Number Type Required Value 26.311.16

-

26.311.17

-

Y Y

-

-

-

-

Cambium-Canopy-LPULCIR 26.161.1 integer N 0-65535 kbps

-

-

Configuration > Quality of Service > Low Priority Uplink CIR 0 kbps 32 bits Cambium-Canopy-LPDLCIR 26.161.2 integer N 0-65535 kbps Configuration > Quality of Service > Low Priority Downlink CIR 0 kbps 32 bits Cambium-Canopy-HPULCIR 26.161.3 integer N 0-65535 kbps Configuration > Quality of Service > Hi Priority Uplink CIR 0 kbps 32 bits Cambium-Canopy-HPDLCIR 26.161.4 integer N 0-65535 kbps Configuration > Quality of Service > Hi Priority Uplink CIR 0 kbps 32 bits Cambium-Canopy-HPENABLE 26.161.5 integer N 0-disable, 1-enable Configuration > Quality of Service > Hi Priority Channel 0 32 bits Enable/Disable 26.161.6 integer N 0-100000 kbps Page 7-298 Chapter 7: Configuration Configuring a RADIUS server Configuration > Quality of Service > Sustained Uplink Data Rate dependent on radio 32 bits feature set Cambium-Canopy-ULBL 26.161.7 integer N 0-2500000 kbps Configuration > Quality of Service > Uplink Burst Allocation dependent on radio 32 bits feature set Cambium-Canopy-DLBR 26.161.8 integer N 0-100000 kbps Configuration > Quality of Service > Sustained Downlink Data dependent on radio 32 bits Rate feature set Cambium-Canopy-DLBL 26.161.9 integer N 0-2500000 kbps Configuration > Quality of Service > Downlink Burst Allocation dependent on radio 32 bits feature set Cambium-Canopy-

26.161.14 integer N 0-disable, 1-enable VLLEARNEN Configuration > VLAN > Dynamic Learning 1 32 bits Cambium-Canopy-

26.161.15 integer N 0-all, 1-tagged, 2-

VLFRAMES Configuration > VLAN > Allow Frame Types untagged 0 32 bits Cambium-Canopy-VLIDSET 26.161.16 integer N VLAN Membership Configuration > VLAN Membership

(1-4094) 0 32 bits Cambium-Canopy-VLAGETO 26.161.20 integer N 5 - 1440 minutes Configuration > VLAN > VLAN Aging Timeout 25 mins 32 bits Cambium-Canopy-VLIGVID 26.161.21 integer N 1 4094 Configuration > VLAN > Default Port VID 1 32 bits Cambium-Canopy-VLMGVID 26.161.22 integer N 1 4094 Configuration > VLAN > Management VID 1 32 bits Cambium-Canopy-

VLSMMGPASS 26.161.23 integer N 0-disable, 1-enable Configuration > VLAN > SM Management VID Pass-through 1 32 bits Cambium-Canopy-BCASTMIR 26.161.24 integer N 0-100000 kbps, 0=disabled Configuration > Quality of Service > Broadcast/Multicast Uplink dependent on radio 32 bits Data Rate feature set Cambium-Canopy-Gateway 26.161.25 ipaddr N

-

Configuration > IP > Gateway IP Address 0.0.0.0

-

Page 7-299 Chapter 7: Configuration Configuring a RADIUS server Cambium-Canopy-ULMB 26.161.26 integer N 0-100000 kbps Configuration > Quality of Service > Max Burst Uplink Data 0 32 bits Rate Cambium-Canopy-DLMB 26.161.27 integer N 0-100000 kbps Configuration > Quality of Service > Max Burst Downlink Data 0 32 bits Rate Cambium-Canopy-UserLevel 26.161.50 integer N 1-Technician, 2-

Installer, 3-

Administrator Account > Add User > Level 0 32 bits Cambium-Canopy-DHCP-

26.161.31 integer N 1-Enable State Configuration > IP > DHCP state Cambium-Canopy-

BCASTMIRUNITS 26.161.28 integer N Configuration > QoS >

Broadcast Downlink CIR Cambium-Canopy-

ConfigFileImportUrl 26.161.29 string N Configuration > Unit Settings Cambium-Canopy-

ConfigFileExportUrl 26.161.30 string N Configuration > Unit Settings 1 0 0 0 32 bits 32 bits 32 bits 32 bits Cambium-Canopy-UserMode 26.161.51 integer N 1=Read-Only 0=Read-

Write Account > Add User > User 0 32 bits Mode

(*) Contains key for encrypting packets sent by the NAS to the remote host (for Microsoft Point-

to-Point Encryption Protocol). Note VSA numbering:

26 connotes Vendor Specific Attribute, per RFC 2865 26.311 is Microsoft Vendor Code, per IANA Page 7-300 Chapter 7: Configuration Configuring a RADIUS server Configuring RADIUS server for SM configuration using Zero Touch feature The RADIUS VSA (Vendor Specific Attributes) is updated for Zero Touch feature. This feature enables the ability for a SM to get its configuration via RADIUS VSA. The RADIUS VSA is updated for an URL which points to the configuration file of SM (see Table 162 for list of VSA). The RADIUS will push the vendor specific attribute to SM after successful authentication. The VSA contains URL of config file which will redirect SM to download configuration. If there is any change in SM confirmation, the SM will reboot automatically after applying the configuration. The RADIUS VSA attributes concerning Zero Touch are as follows:

VSA Type String Cambium-Canopy-ConfigFileImportUrl (29) string Maximum Length 127 characters. Cambium-Canopy-ConfigFileExportUrl (30) string Maximum Length 127 characters. The updated RADIUS dictionary can be downloaded from below link:

https://support.cambiumnetworks.com/files/pmp450/

Note The feature is not applicable to the AP. Page 7-301 Chapter 7: Configuration Configuring a RADIUS server Using RADIUS for centralized AP and SM user name and password management AP Technician/Installer/Administrator Authentication To control technician, installer, and administrator access to the AP from a centralized RADIUS server:

Procedure 28 Centralized user name and password management for AP 1 2 Set Authentication Mode on the APs Configuration > Security tab to RADIUS AAA Set User Authentication Mode on the APs Account > User Authentication tab (the tab only appears after the AP is set to RADIUS authentication) to Remote or Remote then Local. Local: The local SM is checked for accounts. No centralized RADIUS accounting

(access control) is performed. Remote: Authentication by the centralized RADIUS server is required to gain access to the SM if the SM is registered to an AP that has RADIUS AAA Authentication Mode selected. For up to 2 minutes a test pattern is displayed until the server responds or times out. Remote then Local: Authentication using the centralized RADIUS server is attempted. If the server sends a reject message, then the setting of Allow Local Login after Reject from AAA determines if the local user database is checked or not. If the configured servers do not respond within 2 minutes, then the local user database is used. The successful login method is displayed in the navigation column of the SM. Figure 138 User Authentication and Access Tracking tab of the AP Table 163 AP User Authentication and Access Tracking attributes Page 7-302 Chapter 7: Configuration Configuring a RADIUS server Attribute Meaning User Authentication Mode Local: The local SM is checked for accounts. No centralized RADIUS accounting (access control) is performed. Remote: Authentication by the centralized RADIUS server is required to gain access to the AP. For up to 2 minutes a test pattern is displayed until the server responds or times out. Remote then Local: Authentication using the centralized RADIUS server is attempted. If the server sends a reject message, then the setting of Allow Local Login after Reject from AAA determines if the local user database is checked or not. If the configured servers do not respond within 2 minutes, then the local user database is used. The successful login method is displayed in the navigation column of the AP. User Authentication The user authentication method employed by the radios is EAP-MD5. Method Allow Local Login after If a user authentication is rejected from the AAA server, the user is Reject from AAA allowed to login locally to the radios management interface. Radius Accounting The destination port on the AAA server used for Radius accounting Port communication. disable no accounting messages are sent to the RADIUS server deviceAccess accounting messages are sent to the RADIUS server Accounting Messages regarding device access (see Table 165). dataUsage accounting messages are sent to the RADIUS server regarding data usage (see Table 165). Accounting Data Usage Interval The interval for which accounting data messages are sent from the radio to the RADIUS server. If 0 is configured for this parameter, no data usage messages are sent. Page 7-303 Chapter 7: Configuration Configuring a RADIUS server SM Re-authentication The interval for which the SM will re-authenticate to the RADIUS server. Interval SM Technician/Installer/Administrator Authentication The centralized user name and password management for SM is same as AP. Follow AP Technician/Installer/Administrator Authentication on page 7-302 procedure. Note Remote access control is enabled only after the SM registers to an AP that has Authentication Mode set to RADIUS AAA. Local access control will always be used before registration and is used after registration if the AP is not configured for RADIUS. Figure 139 User Authentication and Access Tracking tab of the SM Page 7-304 Chapter 7: Configuration Configuring a RADIUS server Table 164 SM User Authentication and Access Tracking attributes Attribute Meaning User Authentication Mode Local: The local SM is checked for accounts. No centralized RADIUS accounting (access control) is performed. Remote: Authentication by the centralized RADIUS server is required to gain access to the SM if the SM is registered to an AP that has RADIUS AAA Authentication Mode selected. For up to 2 minutes a test pattern is displayed until the server responds or times out. Remote then Local: Authentication using the centralized RADIUS server is attempted. If the server sends a reject message, then the setting of Allow Local Login after Reject from AAA determines if the local user database is checked or not. If the configured servers do not respond within 2 minutes, then the local user database is used. The successful login method is displayed in the navigation column of the SM. If a user authentication is rejected from the AAA server, the user is allowed to login locally to the radios management interface. It is applicable ONLY when the User Authentication Mode is set to Remote Allow Local Login after Reject from AAA then Local. Note When the radio User Authentication Mode is set to Local or Remote, the Allow Local Login after Reject from AAA does not any effect. disable no accounting messages are sent to the RADIUS server deviceAccess accounting messages are sent to the RADIUS server regarding device access (see Table 165). Accounting Messages Page 7-305 Chapter 7: Configuration Access Tracking Configuring a RADIUS server To track logon and logoff times on individual radios by technicians, installers, and administrators, on the AP or SMs Account > User Authentication and Access Tracking tab under Accounting (Access Tracking) set Accounting Messages to deviceAccess. Device Access Tracking is enabled separately from User Authentication Mode. A given AP or SM can be configured for both, either, or neither. RADIUS Device Data Accounting PMP 450 Platform systems include support for RADIUS accounting messages for usage-based billing. This accounting includes indications for subscriber session establishment, subscriber session disconnection, and bandwidth usage per session for each SM that connects to the AP. The attributes included in the RADIUS accounting messages are shown in the table below. Table 165 Device data accounting RADIUS attributes Sender Message Attribute Value Description AP Accounting-

Acct-Status-Type 1 - Start Request Unique per AP session. Initial value is SM MAC, and Acct-Session-Id increments after every start message sent of an in session SM. UTC time the event occurred on the AP Event-Timestamp Acct-Status-Type 2 - Stop Unique per AP session. Initial value is SM MAC, and Acct-Session-Id increments after every start AP Accounting-

Request Acct-Input-Octets message sent of an in session SM. Sum of the input octets received at the SM over regular data VC and the high priority data VC (if enabled). Will not include broadcast. Sum of the output octets sent from the SM over This message is sent every time a SM registers with an AP, and after the SM stats are cleared. This message is sent every time a SM becomes unregistered with an AP, and when the SM stats are cleared. Acct-Output-Octets regular data VC and the high priority data VC (if enabled). Page 7-306 Chapter 7: Configuration Configuring a RADIUS server Sender Message Attribute Value Description Acct-Input-

Gigawords Acct-Output-

Gigawords Number of times the Acct-

Input-Octets counter has wrapped around 2^32 over the course of the session Number of times the Acct-

Output-Octets counter has wrapped around 2^32 over the course of the session Sum of unicast and multicast packets that are sent to a particular SM over Acct-Input-Packets the regular data VC and the high priority data VC (if enabled). It will not include broadcast. Sum of unicast and multicast packets that are Acct-Output-

sent from a particular SM Packets over the regular data VC and the high priority data VC (if enabled). Acct-Session-Time Uptime of the SM session. Acct-Terminate-

Reason code for session Cause termination AP Accounting-

Acct-Status-Type 3 - Interim-Update Request Unique per AP session. Initial value is SM MAC, and Acct-Session-Id increments after every start This message is sent periodically per the operator configuration on the AP in seconds. message sent of an in session SM. Interim update Sum of the input octets sent counts are to the SM over regular data cumulative over Acct-Input-Octets VC and the high priority the course of the data VC (if enabled). Will session not include broadcast. Sum of the output octets set from the SM over Acct-Output-Octets regular data VC and the high priority data VC (if enabled). Page 7-307 Chapter 7: Configuration Configuring a RADIUS server Sender Message Attribute Value Description Acct-Input-

Gigawords Acct-Output-

Gigawords Number of times the Acct-

Input-Octets counter has wrapped around 2^32 over the course of the session Number of times the Acct-

Output-Octets counter has wrapped around 2^32 over the course of the session Acct-Session-Time Uptime of the SM session. Sum of unicast and multicast packets that are sent to a particular SM over Acct-Input-Packets the regular data VC and the high priority data VC (if enabled). It will not include broadcast. Sum of unicast and multicast packets that are Acct-Output-

sent from a particular SM Packets over the regular data VC and the high priority data VC (if enabled). The data accounting configuration is located on the APs Accounts > User Authentication and Access Tracking GUI menu, and the APs Authentication Mode must be set to Radius AAA for the menu to appear. The accounting may be configured via the AP GUI as shown in the figures below. By default accounting messages are not sent and the operator has the choice of configuring to send only Device Access accounting messages (when a user logs in or out of the radio), only Data Usage messages, or both. When Data Accounting is enabled, the operator must specify the interval of when the data accounting messages are sent (0 disabled, or in the range of 30-10080 minutes). The default interval is 30 minutes. Figure 140 RADIUS accounting messages configuration Page 7-308 Chapter 7: Configuration Configuring a RADIUS server The data accounting message data is based on the SM statistics that the AP maintains, and these statistics may be cleared on the AP by an operator. If an operator clears these messages and data accounting is enabled, an accounting stop message is sent followed by an accounting start message to notify the AAA of the change. If an operator clears the VC statistics on the device through the management GUI, a RADIUS stop message and data start message is issued for each device affected. The start and stop messages will only be sent once every 5 minutes, so if an operator clears these statistics multiple times within 5 minutes, only one set of data stop/start messages is sent. This may result in inaccurate data accumulation results. RADIUS Device Re-authentication PMP 450 Platform systems include support for periodic SM re-authentication in a network without requiring the SM to re-register (and drop the session). The re-authentication may be configured to occur in the range of every 30 minutes to weekly. Figure 141 Device re-authentication configuration The re-authentication interval is only configurable on the AP. When this feature is enabled, each SM that enters the network will re-authenticate each the interval time has expired without dropping the session. The response that the SM receives from the AAA server upon re-

authentication is one of the following:

Success: The SM continues normal operation Reject: The SM de-registers and will attempt network entry again after 1 minute and then if rejected will attempt re-entry every 15 minutes Timeout or other error: The SM remains in session and attempt 5 times to re-authenticate with the RADIUS-REQUEST message. If these attempts fail, then the SM will go out of session and proceed to re-authenticate after 5 minutes, then every 15 minutes. Although re-authentication is an independent feature, it was designed to work alongside with the RADIUS data usage accounting messages. If a user is over their data usage limit the network operator can reject the user from staying in the network. Operators may configure the RADIUS Reply-Message attribute with an applicable message (i.e. Data Usage Limit Reached) that is sent to the subscriber module and displayed on the general page. Page 7-309 Chapter 7: Configuration Configuring a RADIUS server RADIUS Change of Authorization and Disconnect Message Prior to this feature, SM will get configuration parameters from a RADIUS server during authentication process. This feature allows an administrator to control configuration parameters in the SM while SM is in session. The configuration changes in SM are done using RADIUS Change of Authorization method (RFC 3576) on the existing RADIUS authentication framework for AP and SM. A typical use case could be changing the QOS parameters after a certain amount of bandwidth usage by a SM. Figure 142 RADIUS CoA configuration for AP The RADIUS CoA feature enables initiating a bi-directional communication from the RADIUS server(s) to the AP and SM. The AP listens on UDP port 3799 and accepts CoA requests from the configured RADIUS servers. This CoA request should contain SM MAC address in User-Name attribute as identifier and all other attributes which control the SM config parameters. For security reasons, a timestamp also needs to be added as Event-Timestamp attribute. Hence the time should also be synchronized between the RADIUS server(s) and the AP to fit within a window of 300 seconds. Once the configuration changes are applied on the SM, CoA-ACK message is sent back to RADIUS server. If the validation fails, the AP sends a CoA-NACK response to the RADIUS server with proper error code. A Disconnect-Message is sent by the RADIUS server to NAS in order to terminate a user session on a NAS and discard all associated session context. It is used when the authentication AAA server wants to disconnect the user after the session has been accepted by the RADIUS. In response of Disconnect-Request from RADIUS server, the NAS sends a Disconnect-ACK if all associated session context is discarded, or a Disconnect-NACK, if the NAS is unable to disconnect the session. Note The RADIUS CoA feature will only enabled if Authentication mode is set to RADIUS AAA. Page 7-310