FCC ID: QWP-60V2000 60 GHz Outdoor Wireless Ethernet Bridge

USER GUIDE 60 GHz cnWave System Release 1.2.2 Reservation of Rights 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 recommends reviewing the Cambium Networks website for the latest changes and updates to products. 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). This product is not restricted in the EU. Any High Risk 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. 2022 Cambium Networks Limited. All rights reserved phn-5196 005v003 August 2022 Contents Contents About This User Guide Purpose Cross-references Feedback Important regulatory information Complying with rules for the country of operation Application firmware Ethernet networking skills Lightning protection Specific expertise and training for professional installers Legal and Open-Source Software statements Problems and warranty Reporting problems Repair and service Hardware warranty Security advice Warnings, cautions, and notes Caring for the environment In the UK and EU countries In non-EU countries Product Description Introduction Frequency bands Characteristics of 60 GHz 802.11ay Standards and advantages Terragraph Overview of cnWave family Contents 3 10 10 10 10 10 10 12 12 12 13 13 13 13 13 13 14 14 14 15 15 16 16 16 17 18 20 21 3 Features Wireless operation Wireless topology Modulation Synchronization Time-division duplexing access mechanism Wireless encryption Designing wireless networks TDD synchronization System management Management agent Network management IPv6 System logging Software upgrade System Hardware Wireless nodes V1000 Client Node (CN) V2000 Client Node (CN) V3000 Client Node (CN) V5000 Distribution Node (DN) Radio mounting brackets Radio accessories Radio external interfaces Radio specifications Theory of operation Power supply units (PSU) PSU Options V1000 Power over Ethernet V2000 Power over Ethernet Contents 22 23 23 25 27 28 29 29 29 29 29 30 30 30 30 31 31 31 32 33 34 35 41 43 46 48 49 49 50 51 4 V3000, V5000 Power over Ethernet PSU Specifications Ethernet and DC cables Maximum cable lengths Outdoor copper CAT6A Ethernet cable Cable accessories SFP Module kits Optical cable and connectors System Planning Site planning Grounding and lightning protection Lightning protection zones Site grounding system ODU location Drop cable grounding points ODU wind loading PSU DC power supply PSU AC power supply PSU location Outdoor AC/DC PSU Lightning Surge Protection Units (LPU) Drop cable grounding points Lightning Surge Protection Units location Deployment Considerations Key deployment guidelines Sector and alignment Minimum CN spacing Near-far radio Early weak interference Avoiding the tight angle deployment Contents 53 57 57 57 59 60 61 64 67 67 67 67 68 68 68 69 70 70 70 70 71 71 71 72 72 73 74 75 76 77 5 Avoiding the straight line interference When two V5000 devices are co-located at a site Polarity Link Adaptation and Transmit Power Control (LATPC) Radio spectrum planning General wireless specifications Regulatory limits Link planning LINKPlanner Range and obstacles Path loss Data network planning Point to Point-based single link Ethernet bridge IPv4/L2 based PMP and mesh network planning Mixture of IPv4 and IPv6 support IPv6 Mode network planning IPv6 Network design consideration Reserved IPv6 address space E2E and cnMaestro deployment consideration Ethernet bridging or IP routing Layer two control protocols Ethernet port allocation IP Interface Daisy-chaining 60 GHz links Installation Safety Power lines Working at heights PSU Grounding and protective earth Contents 77 78 79 79 80 80 80 81 81 81 82 82 83 83 84 85 86 87 87 87 89 89 90 90 91 91 91 91 91 91 6 AC Supply Powering down before servicing Primary disconnect device External cables Drop cable tester RF Exposure near the antenna Minimum separation distances Grounding and lightning protection requirements Grounding cable installation methods Siting radios 60 GHz cnWave radios and mounting bracket options Mounting bracket options Installing the cnWave radio nodes ODU Interface with LPU on the pole Attach ground cables to the radio Mounting the ODU on the mast or wall Connect to the PSU port of the radio Using power over Ethernet (PoE) Using AC/DC PSU Install the PSU Installing the 60W DC power injector Installing the AC/DC PSU Installing the V1000 power injector Connecting to the SFP+ optical module or SFP+ to the copper module to ODU Removing the cable and SFP module Configuring 60 GHz cnWave Nodes deployment Connecting to the unit Configuring the management PC Connecting to the PC and powering up Contents 91 91 92 92 92 92 92 92 92 93 93 93 93 97 100 100 121 121 125 127 128 129 129 130 136 138 138 138 138 140 7 Using the web interface Logging into the web interface Enabling internal E2E Controller Topology Configuration Operation Software upgrade Events Statistics Links Ethernet GPS Radio Performance Prefix Zone Statistics Engineering Border Gateway Protocol (BGP) Maps Tools Antenna Alignment Ping tool Show SFP Power details cnMaestro support for Onboard Controller Auto Manage IPv6 Routes (External E2E Controller) Unconnected PoPs Regulatory Information Compliance with safety standards Electrical safety compliance Human exposure to radio frequency energy Compliance with radio regulations Contents 140 140 146 148 153 181 181 183 184 184 185 186 187 189 193 194 194 195 195 197 204 206 208 210 213 215 215 215 216 218 8 Type approvals Federal Communications Commission (FCC) compliance Innovation, Science and Economic Development Canada (ISEDC) compliance 60 GHz cnWave example product labels Troubleshooting Field diagnostics logs Setup issues in IPv4 tunneling Link is not established PoP not online from E2E/cnMaestro GUI Link is not coming up Link does not come up after some configuration change Link is not having expected throughput performance Factory reset Cambium Networks 219 219 220 220 223 223 225 228 231 231 232 232 232 234 Contents 9 About This User Guide This document provides detailed information about the 60 GHz cnWave products, hardware, and supported features. The guide also explains how to deploy the product along with important safety measures. It is intended for system designers, system installers, and system administrators. Purpose The 60 GHz cnWave product documents are intended to instruct and assist personnel in operation, installation, and maintenance of the equipment and ancillary devices. It is recommended that all personnel engaged in such activities must be properly trained. Cambium Networks 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. To provide feedback, visit our support website:

https://support.cambiumnetworks.com. Important regulatory information Complying with rules for the country of operation USA specific information Caution This device complies with Part 15 of the Federal Communications Commission (FCC) Rules. Operation is subject to the following two conditions:

l This device may not cause harmful interference, and l This device must accept any interference received, including interference that may cause undesired operation. About This User Guide 10 Note This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

l Reorient or relocate the receiving antenna. l Increase the separation between the equipment and receiver. l Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. l Consult the dealer or an experienced radio/TV technician for help. Canada specific information Caution This device complies with Innovation, Science and Economic Development Canada (ISEDC) license-exempt RSSs. Operation is subject to the following two conditions:

l This device may not cause interference; and l This device must accept any interference, including interference that may cause undesired operation of the device. 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 :

l l l'appareil ne doit pas produire de brouillage, et l'utilisateur de l'appareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible d'en compromettre le fonctionnement. European specific information Cambium Networks 60 GHz cnWave products are compliant with applicable European Directives required for CE marking:

l 2014/53/EU of the European Parliament and of the Council of 16 April 2014 on the harmonisation of the laws of the Member States relating to the making available on the market of radio equipment and repealing Directive 1999/5/EC; Radio Equipment Directive (RED). About This User Guide 11 l 2011/65/EU of the European Parliament and of the Council of 8 June 2011 on the restriction of the use of certain hazardous substances in electrical and electronic equipment (RoHS Directive). EU Declaration of conformity Hereby, Cambium Networks declares that the Cambium Networks 60 GHz cnWave Series of Wireless Ethernet Bridge complies with the essential requirements and other relevant provisions of Directive 2014/53/EU. The declaration of conformity may be consulted at https://www.cambiumnetworks.com/eu_dofc. United Kingdom (UK) specific information Cambium Networks 60 GHz cnWave products are compliant with applicable United Kingdom (UK) Regulations required for UKCA marking:

l Radio Equipment Regulations 2017 (SI 2017 No. 1206, as amended) l Restriction of the Use of Certain Hazardous Substances in Electrical and Electronic Equipment Regulations 2012 (SI 2012 No. 3032, as amended) (RoHS) The 59-63.9 GHz frequency band is subject to specific exclusion zones. For more information, see the 59

- 63.9 GHz transmission exclusion zones table. UK Unmetered Supplies Operational Charge Codes:

l V3000: 8820022000100 l V5000: 8820029000100 For more details, check https://www.elexon.co.uk/operations-settlement/unmetered-supplies/charge-

codes-and-switch-regimes/. UK Declaration of conformity Hereby, Cambium Networks declares that the Cambium Networks 60 GHz cnWave Series of Wireless Ethernet Bridge complies with the essential requirements and other relevant provisions of Radio Equipment Regulations 2017 (SI 2017 No. 1206, as amended) The declaration of conformity may be consulted at https://www.cambiumnetworks.com/ukca_dofc. Application firmware Download the latest 60 GHz products family software and install it in the Outdoor Units (ODUs) before deploying the equipment. Instructions for installing software are provided in this guide. 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 user interface (UI). 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 60 GHz platform of products are available in System Hardware and System Planning sections. About This User Guide 12 Specific expertise and training for professional installers To ensure that the 60 GHz cnWave Series is installed and configured in compliance with the requirements of the EU, 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 the following link:https://learning.cambiumnetworks.com/

Legal and Open-Source Software statements Refer to the 60GHzcnWaveLegalandOpen-SourceGuidefor:

l Cambium Networks end user license agreement l Open-Source Software Notices. 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 (http://www.cambiumnetworks.com/support). 3. Ask for assistance from the Cambium Networks 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 the 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 positioner 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. About This User Guide 13 Portions of Cambium equipment may be damaged from exposure to electrostatic discharge. Use precautions to prevent damage. 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. Warnings, cautions, and notes The following describes how warnings and cautions are used in this document and all Cambium Networks document sets:

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. 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. About This User Guide 14 In the UK and EU countries The following information is provided to enable regulatory compliance with the European Union (EU) directives and UK regulations identified and any amendments made to these directives and regulations when using Cambium equipment in the UK or EU countries:

Disposal of Cambium equipment European Union (EU) Directive 2012/19/EU Waste Electrical and Electronic Equipment (WEEE) and UK Statutory Instrument The Waste Electrical and Electronic Equipment Regulations 2013 No. 3113. 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 and UK, it is the individual recipients responsibility to ensure that packaging materials are collected and recycled according to the requirements of EU and UK 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. About This User Guide 15 Product Description This section provides information about the 60 GHz cnWave product (from Cambium Networks). It also describes about its features, characteristics, and other related concepts. Introduction The 60 GHz cnWave portfolio boasts a wide spectrum of up to 9 GHz (57-66 GHz) that is typically divided into channels of roughly 2 GHz each. The 60 GHz band is largely uncongested compared to the 2.5 GHz and 5 GHz public bands currently used for Wi-Fi. The 60 GHz band is an unlicensed millimeter-

wave band that can provide massive speeds and throughput with Line of Sight (LoS) applications. The 60 GHz band is located in the millimeter-wave (30 GHz to 300 GHz) portion of the electromagnetic spectrum. The millimeter-wave portion of the RF spectrum has been largely unexploited for commercial wireless applications. 60 GHz Wireless has used its well-established expertise in millimeter-wave products and technologies to develop wireless products operating in that spectrum that enable two-way wireless communications at data rates that previously could only be accomplished with fiber optic cable. In addition to the high-data rates that can be accomplished in this spectrum, energy propagation in the 60 GHz band has unique characteristics that make possible many other benefits such as excellent immunity to interference, high security, and frequency reuse. Frequency bands It is proposed that the 60 GHz band is divided into 11 channels each with a bandwidth of 2.16 GHz starting from 57.24 to 70.2 GHz. Channel 1 to 6 has 2.16 GHz bandwidth and are defined in 802.11ad, channel 9 to 13 has 4.32 GHz bandwidth and are added in 802.11ay. Figure 1: Frequencybands The following table describes the channels and corresponding bandwidths supported by 60 GHz cnWave:

Table 1: Channels and corresponding bandwidths Channel Bandwidth (GHz) Center (GHz) Minimum (GHz) Maximum (GHz) CH1 CH2 CH3 CH4 CH9 2.16 2.16 2.16 2.16 4.32 58.32 60.48 62.64 64.80 59.40 57.24 59.40 61.56 63.72 57.24 59.40 61.56 63.72 65.88 61.56 Product Description 16 Channel Bandwidth (GHz) Center (GHz) Minimum (GHz) Maximum (GHz) CH10 CH11 4.32 4.32 61.56 63.72 59.40 61.56 63.72 65.88 Characteristics of 60 GHz The following are the important characteristics of 60 GHz cnWave:

l High Throughput capability With multi-gigabit channel bandwidth, it is possible to gain multi-gigabit capacity, based on 802.11ad it is possible to get a 5 Gbps PHY rate and with 802.11ay it is possible to get a 10 Gbps PHY rate. cnWave products are capable of providing 15 Gbps Ethernet rates with channel bonding enabled. l Unlicensed and interference-free Typically, V Band is either an unlicensed or lightly licensed band, and since this band is a relatively new opening there will often be limited interference compared to 2.4 and 5 GHz bands. l Line of Sight (LoS) 60 GHz is affected by oxygen absorption, it varies throughout the band. The absorption gets reduced if the frequency gets increased. For example, the absorption is 15 dB/km in 60 GHz frequency, 5 dB/km in 64 GHz, and 0.5 dB/km in 68 GHz. If the total channel is divided into 6 channels, then the mid-channel that is channels 2 and 3 has more absorption loss. From channel 4, the absorption level starts to drop. So only Line of Sight links are available and Near LoS or non LoS does not work with 60 GHz. Figure 2: LineofSight l Rain fade The user can expect to see significant rain fade for 60 GHz links, particularly those pushing the longer distances. Attenuation depends on the rain rate which must be factored in while planning the network. Rain attenuation depends on the level of the rain. The following table describes the rain level and absorption loss:

Product Description 17 Table 2: Rain and attenuation Rain Drizzle (0.25 mm/hr) Light Rain (2.5 mm/hr) Medium Rain (12.5 mm/hr) Heavy Rain (25 mm/hr) Downpour (50 mm/hr) Tropical (100 mm/hr) Monsoon (200 mm/hr) Attenuation 0.2 dB/km 1.8 dB/km 5.6 dB/km 9.5 dB/km 17 dB/km 28 dB/km 38 dB/km The following figure shows the absorption loss due to the rain level (seasons):

Figure 3: VariationinLoss/kmwithfrequencyandrainrate Drizzle - 0.25 mm/hr; Light rain - 2.5 mm/hr; Medium rain - 12.5 mm/hr; Heavy rain - 25 mm/hr. l Short range The range of a 60 GHz cnWave link can be limited due to oxygen absorption and rain fade which needs to be factored in for link planning. One advantage of a shorter range is frequency re-

usability and security (since the signal does not travel long distances). 802.11ay Standards and advantages IEEE 802.11ay is an IEEE standard that covers 60 GHz cnWave, this standard is an amendment of the IEEE 802.11ad standard. There are IEEE 802.11ay is designed with a higher throughput capacity of over 10 Gbps data rate over distances of 200 to 500 meters. 802.11ay includes features such as Channel Bonding and Synchronization. 802.11ay based 60 GHz solution transforms fixed wireless access from a broadband option of last resort into a competitive alternative to fiber and cable-based solution. This standard is designed with a throughput capacity of over 10 Gbps data rate over distances of 200 to 500 meters. 802.11ay includes features such as Channel Bonding and Synchronization. 802.11ay is WLAN type in the IEEE 802.11. It has a frequency of 60 GHz. It has also been noted that it is likely to have Product Description 18 mechanisms for channel bonding and MU-MIMO technologies. 802.11ad uses a maximum of 2.16 GHz bandwidth, whereas 802.11ay bonds four of those channels together for a maximum bandwidth of 8.64 GHz. 802.11ay standard has the following advantages with the Terragraph solution:

l Channel Bonding 802.11ay standard has channel bonding capability to combines adjacent channels to form wider channels, in this case, wider channels combine to form 4.32 GHz, there are additional wider channels created which provide double capacity throughput compared to 802.11ad standard. l Network Synchronization Synchronization is used to control the transmit and receive signals to prevent self-interference. Radios assigned with the same polarity will be transmitting and receiving at the same time. There are four types of polarity:

l Odd Polarity l Even Polarity l Hybrid odd Polarity l Hybrid Even Polarity l Mesh Routing Mesh is an interconnection of devices that can have multiple paths between any two nodes, some advantages of using mesh are better connectivity, capacity sharing, load balancing, and re-routing in case of link failure. l Increased capacity 802.11ay supports Channel Bonding which allows two immediate channels to be merged into a single wide-band channel, thereby doubling the channel bandwidth to 4.32 GHz. l Supports a greater number of client nodes 802.11ay supports 15 client nodes per sector. Advantages l 802.11ay product, Terragraph certified The 60 GHz cnWave is an 802.11ay product and Terragraph certified. l Highest capacity It has highest the capacity in the industry, up to 7.2 Gbps per sector. l Low total cost ownership l cnWave V5000 is 280-degree coverage with dual-sector. Installation is simple, uses beam forming for installation. No need for a site router. Product Description 19 l cnWave V1000 and cnWave V3000 meet various range challenges. l Using beam forming, the V3000 has a super long range. l cnMaestro panel is used for device management. l cnHeat and LINKPlanner helps for easy planning. l Unlicensed and interference-free This spectrum spans 57 - 66 GHz and is widely available, especially when compared to the 2.4 and 5 GHz bands. This 9 GHz of the spectrum can be divided up into channels ranging between 1 and 2 GHz wide. l Massive throughput This band can allow for up to 15 Gbps of throughput from some products on the market today. Terragraph Terragraph is a connectivity solution from Facebook. The mission of Terragraph is to bring more people online to a faster internet. It is freely licensed technology that is designed to deliver cost-effective and reliable fiber like connectivity over a wireless mesh network (as shown in Figure 4). Figure 4: Terragraph 1- Controller 2- PoP (Fiber, RF) 3- Distribution Node 4- Client Node Key components Terragraph contains the following key components:

Product Description 20 l Distribution Node (DN) - DN connects with other DN to form a mesh in a distribution network. l Client Node (CN) - CN is a customer premise radio that connects with a DN node to provide high-

speed connectivity. l E2E Controller - The E2E Controller allows for configuration, control, and monitoring of the nodes and network. Cambium Networks supports two methods to utilize the E2E Controller:

l On-Premises installed as a VM and can be used for small or large deployment. l Onboard the PoP, for PTP, PMP, and small mesh networks the PoP can be configured to host the controller (limited to 31 nodes). Features The following are the features of Terragraph:

l 802.11ay - Delivers multi-gigabit speeds over wide frequency bands. l Mesh - Efficiently distributes capacity and improves availability, using Open/R. l Efficient MAC and PHY - Scheduled MAC (TDD / TDMA) for scalability and dense deployments. l Cloud management - Used for configuration, management, visualization, alarms, and monitoring. l Network planning - Automated design and optimization using imagery, population, and optionally other data sources. Responsibilities Terragraph software initializes and configures radios (DN and CN). It tracks and optimizes meshed routing paths. It also monitors and maintains Syslog, alarms, and Firmware upgrades. Overview of cnWave family The 60 GHz cnWave solution (from Cambium Networks) provides easy, fast, and cost-effective wireless Gigabit connectivity for edge access and/or high-capacity backhaul for edge access solutions at a significantly lower cost than fiber infrastructure. Service providers and enterprises now have access to Gigabit for business and residential connectivity, backhaul for Wi-Fi access. Certified for Facebook Terragraph, 60 GHz cnWave Mesh solutions are highly efficient at handling high-density deployments in cities and suburban areas. The 60 GHz solution consists of a Destination Node (DN), which acts as an Access Point (AP), and a Client Node (CN), which acts as a cnWave client. 60 GHz cnWave consists of the following four variants (as shown in Figure 5):

l V5000: A dual-sector Destination Node (DN) that contains two sectors covering up to 280 degrees with beamforming. A single V5000 can connect up to four other distribution nodes or up to 30 client nodes. V5000 can be used for PTP, PMP, and Mesh configurations. l V3000: A Client Node (CN) that is available in two sizes - 44.5 dBi high-gain antenna and 40.5 dBi lower gain antenna, both with beamforming. These client nodes can support up to 7.2 Gbps, with a channel bonding, for PTP and PMP configurations. Product Description 21 l V2000: A CN that contains a 34.5 dBi antenna with beamforming. This client node can support up to 3.6 Gbps, with a channel bonding, for PTP and PMP configurations. l V1000 : A CN that contains a wide-range, 80 degrees beamforming for easy installation. This CN is powered by 802.3af PoE and supports up to 2 Gbps for PTP and PMP configurations. Figure 5: 60GHzcnWaveproducts Features This section lists the features of each product of 60 GHz cnWave. V1000 Client Node (CN) l Supports modulations BPSK to 16 QAM (MCS1 to MCS12) l Integrated antenna with beam forming l 38 dBm EIRP l Gigabit Ethernet l 1 Gbps UL/1 Gbps DL throughput l Powered by passive PoE or 802.3af/at PoE l IP66/67 V2000 Client Node (CN) l Supports modulations BPSK to 16 QAM (MCS1 to MCS12) l 34.5 dBi Ultra gain antenna with beam forming 49 dBm EIRP l 2.5 Gigabit Ethernet Main interface l 2.5 Gigabit Ethernet Auxiliary interface l 1.8 Gbps UL/1.8 Gbps DL throughput l 802.3at POE (2-pair or 4-pair for higher wattage) Product Description 22 l Supports Aux PoE out (802.3af/at PoE) l IP66/67 V3000 Client Node (CN) l Supports modulations BPSK to 16 QAM (MCS1 to MCS12) l 44.5 dBi Ultra gain antenna with beam forming 60.5 dBm EIRP l 40.5 dBi UltraGain antenna with beam forming 54.5 dBm EIRP l 10 Gigabit Ethernet l Supports 10G SFP+ or 1G SFP l 1.8 Gbps UL/1.8 Gbps DL throughput l Gigabit Ethernet Auxiliary Interface l Powered by passive PoE l Supports Aux PoE out ( 802.3af/at PoE) l IP66/67 V5000 Distribution Node (DN) l Supports modulations BPSK to 16QAM (MCS1 to MCS12 ) l Dual sector 280-degree antenna with beamforming l 38 dBm EIRP l 10 Gigabit Ethernet l Supports 10G SFP or 1G SFP l 1.8 Gbps UL/1.8 Gbps DL throughput per sector l Gigabit Ethernet Auxiliary Interface l Powered by passive PoE l Supports Aux PoE out (802.3af/at PoE) l IP 66/67 Wireless operation This section describes how the 60 GHz cnWave is operated, including topology, modulation modes, power control, and security. Wireless topology 60 GHz cnWave supports operation in three topologies:

Product Description 23 l Point to point (PTP) l Point to Multipoint (PMP) l Mesh PTP The PTP topology provides a point-to-point link using V1000, V2000, V3000, and V5000. Note V1000 to V1000 point-to-point topology is supported. And, V2000 to V2000 point-to-point topology is also supported. Figure 6: PTPTopology PMP The PMP topology provides a point to multi-point where a V5000 acts as PoP DN and V5000, V3000, V1000 acts as APs. Product Description 24 Figure 7: PMPTopology Mesh Mesh efficiently distributes capacity and improves availability, using Open/R based layer 3 IPv6 meshing. It allows for route diversity which provides high network availability and supports up to 15 hops away from a PoP node. Network bandwidth is reduced at each hop, and the total bandwidth available in the network is limited to a PoP node's network reappearance. Mesh is distributed network application platform that determines appropriate routes between the mesh nodes. Figure 8: Meshtopology Modulation Following table lists modulation supported during L2 and L3 throughput:

Product Description 25 Table 3: Modulation MCS Modulation Coding Rate L2 Throughput (Mb/s)

(2.16 GHz Channel) L2 Throughput (Mb/s)

(4.32 GHz Channel) 2 3 4 5 6 7 8 9 10 11 BPSK BPSK BPSK BPSK QPSK QPSK QPSK QPSK 16-QAM 16-QAM Link adaption 1/2 5/8 3/4 4/5 1/2 5/8 3/4 4/5 5/8 3/4 733.0 914.0 1085.0 1175.0 1421.0 1748.0 2059.0 2221.0 3245.0 3737.0 1466.0 1828.0 2170.0 2350.0 2842.0 3496.0 4118.0 4442.0 6490.0 7474.0 Link adaptation is performed independently for each link for data traffic, and it is closed-loop based. Adjusting the Tx modulation and coding scheme from MCS2 to MCS12 selected for transmission. It is adjusted based on the following:

l Packet Error Ratio (PER), l SNR, l local measurements of successful and unsuccessful frame transmissions (e.g. count of frames ACKed or Not ACKed). Figure 9: Adjustinglinks Start from MCS2, adjust based on signal quality, when the session is idle, fall back to MCS-9 or any highest MCS achieved below MCS-9. Product Description 26 Synchronization Synchronization is used to control the transmit and receive signals to prevent self-interference. Radios assigned with the same polarity will be transmitting and receiving at the same time. There are two types of polarities:

l Odd (if Odd nodes are Tx) l Even (if Even nodes are Rx) Figure 10: Oddandevenpolarities The MAC synchronizes its timers to an external, accurate time source, such as GPS or IEEE 1588. A timing pulse that resets the Timing Synchronization Function (TSF) on the DN is repeated once every second. This timing pulse occurs exactly at the turn of each second. Product Description 27 Figure 11: TheMACsynchronization Time-division duplexing access mechanism 60 GHz cnWave uses a Time Division Duplex (TDD) channel access mechanism. All cnWave nodes are time-synchronized and this is achieved through internal GPS, IEEE 1588(roadmap), or Cambium Sync

(roadmap), and each sector of a node is assigned specific times during which it can transmit or receive. A timing pulse that resets the Timing Synchronization Function (TSF) on the DN is repeated once every second (1PPS). This timing pulse occurs exactly at the turn of each second and Sub-Frames begins every 200 microseconds. General operation of MAC layer MAC is highly modified from that in IEEE 802.11-2016. Use TDD MAC by substituting TDD access for all other access. 60 GHz cnWave supports a fixed 50-50 up/down ratio. 60 GHz cnWave uses only the following frames:

l Data l QoS-Null (frame does not carry any data) l Management Action (for example, beam-forming, and others.) l Block ACK (used for sending an ACK to multiple nodes/packets at once) l ACK Frame types Below are the types of frames in 60 GHz cnWave:

l Management frames - A node sends all management frames using the DMG control mode PHY, MCS 0. l Control frames - A node sends the ACK frame using the DMG control mode PHY, MCS 0. A node sends the Block ACK frame using the DMG single carrier PHY, MCS 1. Product Description 28 l Data frames - A node sends data frames using MCS 2 through MCS 12 of the DMG single carrier PHY, as determined by the link adaptation algorithm. Wireless encryption The 60 GHz cnWave supports optional encryption for data transmitted over the wireless link using a choice of three different encryption algorithms:

l TLS RSA: The ODUs exchange RSA certificates to authorize the remote unit and agree on a randomly-generated master secret. The TLS RSA option supports the unencrypted operation of the wireless link, or encryption with 128-bit AES. l TLS PSK 128-bit: Both ends of the link are configured with the same 128-bit pre-shared key as a master secret. The wireless link is encrypted using 128-bit AES. The Advanced Encryption Standard (AES) is a symmetric encryption algorithm approved by U.S. Government organizations (and others) to protect sensitive information. The AES implementation in 60 GHz cnWave is approved to FIPS 197. The use of AES encryption in 60 GHz cnWave is controlled by the AES license and enabled through the purchase of a capability upgrade. Note Encryption Algorithm cannot be configured as TLS RSA when Access Method is Link Name Access. In this case, only the TLS PSK algorithms are supported. Designing wireless networks For designing wireless networks, refer to LINKPlanner. TDD synchronization V3000 and V5000 have built-in GPS receivers. E2E Controller manages the TDD synchronization. System management This section introduces the 60 GHz cnWave management system, including the web interface, installation, configuration, alerts, and upgrades. Management agent The 60 GHz cnWave equipment is managed through an embedded management agent. Management workstations, network management systems, or PCs can be connected to this agent using a choice of in-

band or out-of-band network management modes. The management agent includes an IPv4/IPv6 interface at the management agent. The IP interface operates in the following modes:

l l IPv4 only IPv6 only l Dual IPv4/IPv6 Product Description 29 Network management cnMaestro is a Cambium Network Management System (NMS). This is a single plane to manage the complete Cambium product portfolio. It uses secure WebSocket for management traffic that can be used to manage all Cambium products on the same system. Configurations can be pushed from the cnMaestro through E2E to the end devices. cnMaestro NMS is used to:

l Manage cnWave network including E2E, CN, and DN. l Show the connection topologies. l Collect KPIs/statistics, alarms, logs (via the E2E device agent). l Performs software upgrade. IPv6 IPv6 address is 128 bits (16 Bytes) address. The subnet ID in IPv4, is called prefix in IPv6. In IPv6, Neighbor Discovery Protocol (NDP) is used with ICMPv6 to resolve the MAC address. IPV6 does not have broadcast but only has multicast. cnWave products use SLAAC (Stateless Address Autoconfiguration) for dynamic IPv6 address assignment. The system gets the IP address dynamically by listening to Router Advertisement (RA) and forms the address in EUI-64 format. RA also publishes DNS information to the devices. System logging Refer to Logging into the web interface for system logging. Software upgrade Refer to Software upgrade for more information. Product Description 30 System Hardware This topic provides information about the hardware of 60 GHz cnWave. Wireless nodes The 60 GHz cnWave solution includes three types of wireless nodes:

l V1000 Client Node l V2000 Client Node l V3000 (44.5 dBi and 40.5 dBi) Client Node l V5000 Distribution Node V1000 Client Node (CN) V1000 is an outdoor CN that can be connected to a distribution node wirelessly. V1000 supports a Gigabit Ethernet interface and is powered by 802.3af/at PoE compliant power supply or a passive PoE. Figure 12: V1000CN'sfrontandrearviews V1000 CN - Part numbers Order the V1000 CN from Cambium Networks (as listed in Table 4). Each V1000 CN is supplied with a mounting bracket for wall mount or pole mount, and an indoor power supply. Table 4: V1000 CN part numbers Product description 60GHz cnWave V1000 Client Node with US cord 60GHz cnWave V1000 Client Node with EU cord Part number C600500C001A C600500C003A System Hardware 31 Product description 60GHz cnWave V1000 Client Node with UK Cord 60GHz cnWave V1000 Client Node with ANZ Cord 60GHz cnWave V1000 Client Node with Brazil Cord 60GHz cnWave V1000 Client Node with Argentina Cord 60GHz cnWave V1000 Client Node with China Cord 60GHz cnWave V1000 Client Node with South Africa Cord 60GHz cnWave V1000 Client Node with India Cord 60GHz cnWave V1000 Client Node with no Cord Part number C600500C004A C600500C008A C600500C009A C600500C010A C600500C011A C600500C012A C600500C013A C600500C014A 60GHz cnWave V1000 Client Node with Israel cord - for Israel Only C600500C016A 60GHz cnWave V1000 Client Node with no Cord and no Power supply C600500C017A V2000 Client Node (CN) V2000 is an outdoor CN that can be connected (wireless) to a DN or another V2000 CN. V2000 supports a 2.5 Gigabit Ethernet Main interface and a 2.5 Gigabit Ethernet Aux interface. A V2000 CN can be powered using 30W passive POE or using 802.3at complaint POE switch. For more information about the supported power supply and cable lengths, refer to the Power supply units (PSU) section. A V2000 CN can also power 802.3af/at compliant auxiliary device through the Aux Ethernet interface. Figure 13: V2000CN'sfrontandrearviews System Hardware 32 V2000 CN - Part numbers Order the V2000 CN from Cambium Networks (as listed in Table 5). A V2000 CN radio is supplied without a mounting bracket and with or without power supply. Table 5: V2000 CN part numbers Product description 60GHz cnWave V2000 Client Node 30W with Israel Cord 60GHz cnWave V2000 Client Node 30W with South Africa Cord 60GHz cnWave V2000 Client Node 30W with India Cord 60GHz cnWave V2000 Client Node 30W with no Cord Part number C600500C026A C600500C027A C600500C028A C600500C029A 60GHz cnWave V2000 Client Node no power supply, no power cord C600500C030A 60GHz cnWave V2000 Client Node 30W with EU cord 60GHz cnWave V2000 Client Node 30W with UK Cord 60GHz cnWave V2000 Client Node 30W with ANZ Cord 60GHz cnWave V2000 Client Node 30W with Brazil Cord 60GHz cnWave V2000 Client Node 30W with Argentina Cord C600500C031A C600500C032A C600500C033A C600500C034A C600500C035A V3000 Client Node (CN) V3000 is an outdoor CN that can be connected (wireless) to a DN or another V3000 DN. V3000 supports a 10 Gigabit Ethernet interface, an 10G SFP+ interface port, and a Gigabit Ethernet Aux interface. V3000 can be powered using 60W passive POE or using an AC/DC PSU through a mini adapter (for more information, refer to the power supply and cable lengths supported in the Power supply units section). V3000 DN can also power 802.3af/at compliant auxiliary device through the Gigabit Aux interface. Figure 14: V3000ClientNodewithoutantennaassemblyandwith44.5dBiand40.5dBiantenna assemblies System Hardware 33

Figure 103: Fixingthemountingplateofbracketbodyandadjustingtheelevationangle V5000 Pole mount bracket 1. Pass the long screws through the bracket body. The screws are located in the recess in the bracket. 2. Fit two flanged nuts to the long screws on the back of the bracket. Tighten using a 13 mm spanner. 3. Fix the bracket to the back of the radio using the four short M6 bolts, ensuring that the arrow in the plate points towards the top of the radio. Tighten the four bolts to a torque setting of 5.0 Nm

(3.7 lb-ft) using a 13 mm spanner or socket. 4. Attach the pole-mount bracket to the pole using the clamp and the remaining flanged nuts. Adjust azimuth and tighten the nuts to 10 Nm (7.4 lbft) using a 13 mm spanner. Installation 118 Figure 104: FixingtheV5000polemountbracket V5000 Alignment The V5000 distribution node has two sectors, situated side by side, each covering a 140-degree range in azimuth, giving a combined coverage of 280 degrees. In elevation, the antenna can beam steer in a +/-

20-degree range. The boundary between where Sector 1 ends and Sector 2 begins is the centerline/boresight from the unit. Installation 119 Figure 105: V5000alignment-Topview V5000 Wall mount bracket 1. Install the mounting plate of the wall mount bracket securely on a vertical wall, using suitable fixing hardware. Note Fixing hardware is not supplied with the wall mount bracket. 2. Fix the bracket body to the back of the radio using the four short M6 bolts, ensure that the arrow in the plate points towards the top of the radio. Tighten the four bolts to a torque setting of 5.0 Nm (3.7 lb-ft) using a 13 mm spanner or socket. 3. Insert the four short M8 bolts into the sides of the bracket body. 4. Fit the bracket body to the mounting plate by positioning the short bolts into the open-ended slots. Tighten the bolts to a torque setting of 5.0 Nm (3.7 lb-ft) using a 13 mm spanner or socket. Installation 120 Figure 106: FixingtheV5000wallmountbracket Connect to the PSU port of the radio Using power over Ethernet (PoE) 1. Disassemble the gland and thread each part onto the cable (the rubber bung is split). Assemble the spring clip and the rubber bung. Figure 107: Assemblingthespringclipandtherubberbung 2. Fit the parts into the body and lightly screw on the gland nut (do not tighten it). Installation 121 Figure 108: Fixingtheglandnut 3. Connect the RJ45 plug into the main PSU port of the ODU. Figure 109: ConnectingtheRJ45plug 4. Rotate the gland clock wise to tightly fit the gland on the PSU port. Warning Ensure that the cable clamp is not attached/ tightened at this stage, this may cause damage to the RJ45 or PCB. Installation 122 Figure 110: Rotatingthegland 5. Tighten the gland (cap or nut), this must be done last. Otherwise, it may damage the RJ45 or PCB. Disconnecting drop cable from the radio 1. Loosen and remove the cable clamp by rotating anti-clockwise from the PSU port. Figure 111: Removingthecableclamp Warning Loosen the cable clamp completely and then unscrew the gland. Not releasing the cable may cause damage to the RJ45 socket and/or PCB. Installation 123 2. Remove the gland. Figure 112: Removingthegland 3. Press tab on RJ45 plug to remove the cable from PSU port. 4. Remove the latch of the RJ45 plug to remove the cable from the PSU port. Figure 113: RemovingthelatchoftheRJ45plug Installation 124 Using AC/DC PSU Cable joiner A cable joiner is used to connect the wires. Insert the wires into the cable joiner by loosening the screws on the joiner. Figure 114: Cablejoiningparts Connecting the mini adapter Figure 115: Miniadapterconnections Installation 125 Fitting the long cable gland Figure 116: Thelongcablegland Connecting the mini adapter to ODU 1. Plug and connect the input side of the AC/DC PSU to the AC power line and tighten the gland. Tighten the cable clamp cap. Figure 117: ConnectingtheinputsideofAC/DCPSU 2. Connect output side of DC PSU to ODU through cable joiner and DC mini adapter. Installation 126 Figure 118: ConnectingtheoutputsideofAC/DCPSU Install the PSU Install one of the following types of PSU:

l l l Installing the 60W DC power injector Installing the AC/DC PSU Installing the V1000 power injector Warning Always use an appropriately rated and approved AC supply cord-set in accordance with the regulations of the country of use. Attention As the 60W DC power injector and V1000 power injector are 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. Attention Do not plug any device other than a 60 GHz cnWave 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 60 GHz cnWave 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. Installation 127

Installing the 60W DC power injector 1. Connect the input side of the DC power injector to the AC power line. Figure 119: 60WDCpowerinjector 2. Connect 5 Gbe LAN port of the power injector to network equipment. 3. Connect 60 W 56V 5 GbE PoE port of the power injector to ODU drop cable. Figure 120: ConnectingthepowerinjectortoODUdropcable Installation 128 Installing the AC/DC PSU 1. Connect the input side of the AC/DC PSU to the AC power line. 2. Connect output side of DC PSU to ODU through cable joiner and DC mini adapter. Refer to the Cable joiner section for connecting, installing cable joiner and mini adapter. Figure 121: AC/DCPSU(N000000L179B) Figure 122: Cablejoiner Figure 123: DCtoRJ45 plug,Miniadaptor Figure 124: AC/DCpoweringdiagram Figure 125: AC/DCPSU For detailed assembly of cable joiner and mini adapter to ODU PSU port, refer to the Cable joiner section. Note Both short and long glands can be used to connect to outdoor PSU. Installing the V1000 power injector 1. Connect the 56V Gigabit Data + power port to ODU and Gigabit data port to the network equipment. Installation 129 Figure 126: V1000powerinjector Figure 127: V1000poweringdiagram Figure 128: ConnectingtheV1000powerinjector Connecting to the SFP+ optical module or SFP+ to the copper module to ODU When ODU is powered through AC/DC PSU, an optical or copper Cat6A Ethernet interface can be connected to the SFP port of the ODU for the data interface. Adapt the installation procedures in this section as appropriate for SFP interfaces, noting the following differences from a PSU interface. Installation 130 Fitting the long cable gland Optical SFP interface: Disassemble the long cable gland and thread its components over the LC connector at the ODU end as shown below. Copper CAT6A SFP interface: Disassemble the cable gland and thread its components over the RJ45 connector at the ODU end. 1. Disassemble the long cable gland used for the optical SFP interface. Figure 129: Disassemblingthelongcablegland-opticalSFPinterface You must also disassemble the long cable gland used for the copper SFP interface. Figure 130: Disassemblingthelongcablegland-copperSFPinterface 2. Thread each part onto the cable (the rubber bung is split). Figure 131: Threadingthepartontothecable 3. Fit the parts into the body and lightly screw on the gland nut (do not tighten it). Installation 131 Figure 132: Fixingpartstothegland Inserting the SFP module To insert the SFP module into the ODU, follow the below steps:

1. Remove the blanking plug from the SFP port of the ODU. Figure 133: RemovingtheblankingplugfromtheSFPport 2. Insert the SFP module into the SFP receptacle with the label on the bottom. Installation 132 Figure 134: InsertingtheSFPmodule 3. Push the module home until it clicks into place. Figure 135: Pushingthemodulehome 4. Rotate the latch to the locked position. Installation 133

Figure 136: Rotatingthelatch Connecting the cable Attention The Fiber optic cable assembly is very delicate. To avoid damage, handle it with extreme care. Ensure that the fiber optic cable does not twist during assembly, especially when fitting and tightening the weatherproofing gland. Do not insert the power over Ethernet drop cable from the PSU into the copper SFP module, as this will damage the module. 1. Remove the LC connector dust caps from the ODU end (optical cable only). Figure 137: RemovingtheLCconnectordustcaps 2. Plug the connector into the SFP module, ensuring that it snaps home. Installation 134 Figure 138: PluggingtheconnectorintotheSFPmodule Fitting the gland 1. Fit the gland body to the SFP port and tighten it to a torque of 5.5 Nm (4.3 lb-ft). Figure 139: Fittingthelandbody 2. Fit the gland nut and tighten until the rubber seal closes on the cable. Do not over-tighten the gland nut, as there is a risk of damage to its internal components. Installation 135 Figure 140: Fittingtheglandnut 3. Fit the gland nut to the rubble seal on the gland body and tighten it to a torque of 5.5 Nm (4.3 lb-

ft). Figure 141: Fittingtheglandnuttotherubbleseal Removing the cable and SFP module Do not attempt to remove the module without disconnecting the cable, otherwise, the locking mechanism in the ODU will be damaged. Installation 136 1. Remove the cable connector by pressing its release tab before pulling it out. Figure 142: Removingthecableconnector 2. Pull the bale clasp (latch) to the unlocked position. Extract the module by using a screwdriver. Figure 143: Pullingthebaleclasp(latch) Installation 137 Configuring 60 GHz cnWave Nodes deployment The configuration of cnWave nodes is handled automatically by the E2E service. However, the first PoP node must be configured manually since connectivity to the E2E controller has not yet been established. After establishing communication with the E2E controller, the nodes report a hash of their local configuration file and the controller automatically pushes configuration changes to the nodes upon seeing any mismatches. Centralized configuration management architecture implemented in which the E2E controller, serves as the single point of truth for configurations in the network. Figure 144: Nodesdeployment More details on deployment of the 60 GHz series of products are available here. 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 60 GHz cnWave devices. Configuring 60 GHz cnWave 138 Procedure:

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 Version 4 (TCP/IPv4). Figure 145: TheEthernetPropertiesdialogbox 3. Click Properties. 4. Enter an IP address that is valid for the 169.254.X.X/16 network, avoiding 169.254.1.1 (eg:

169.254.1.3). Configuring 60 GHz cnWave 139 Figure 146: TheInternetProtocolVersion4(TCP/IPv4)dialogbox 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 60 GHz cnWave devices. Procedure:

1. Check that the ODU is connected to the power supply (AC/DC according to the configuration). 2. Connect the PC Ethernet port to the LAN port of the PSU or AUX port (according to device configuration). 3. Open a web browser and type: 169.254.1.1. 4. When prompted, enter admin/admin to login to the GUI and complete the configuration. Using the web interface This section describes how to log into the 60 GHz cnWave 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:

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 and press Enter. Configuring 60 GHz cnWave 140 3. Type the username and password as admin and admin. Click Sign In. The Dashboard page appears. Configuring 60 GHz cnWave 141 Users can select the refresh time interval. Click admin at the top-right and select the Refresh Interval from the drop-down. The Dashboard contains the following options at the top:

l Uptime l Links l Channels l Wireless Throughput Uptime Displays the total running time of the device. Links Displays the total number of active links which are connected to the 60 GHz cnWave device. Channels Displays the total number of channels (Sector 1, Sector 2, etc.,) which are connected to the 60 GHz cnWave device. Configuring 60 GHz cnWave 142 Wireless Throughput Displays the transmitting and receiving throughput values. Dashboard elements Dashboard home page consist of the below elements:

l Device Information l GPS l Sectors l Ethernet Figure 147: Dashboard-DeviceInformation Table 35: Elements in the Device Information section Element Type Description Displays type of the device. The device types are:

l DN l PoP DN l CN Name Displays name of the device. E2E Connection Status Displays the connection status of the E2E controller. MACaddress Displays the MACaddress of the 60 GHz cnWave device. Serial Number Displays the serial number of the 60 GHz cnWave device Model Displays the model of the 60 GHz cnWave device. The models are:

Configuring 60 GHz cnWave 143 Element Description l V1000 l V3000 l V5000 Software version Displays the software version used in 60 GHz cnWave device. Firmware version Displays the Firmware version used in 60 GHz cnWave device. Wireless security Displays the security type. The types are:

l Disabled l PSK l 802.1X Layer 2 Bridge Displays bridge status. System Time Displays current time. GPS GPS table displays the positioning information of the site. Figure 148: Dashboard-GPS Table 36: Elements in the GPS section Element Fix Type Description Fix Type Satellites tracked Number of registered satellites Latitude Longitude Height Sectors Displays latitude of the site Displays longitude of the site Displays height of the device Sectors table displays the number of nodes added to the device and its information. Configuring 60 GHz cnWave 144 Figure 149: Dashboard-Sectors Table 37: Elements in the Sectors section Element Channel Description Displays the channel information used by the sector Sync mode Displays the sync mode of the sectors MAC address Displays the MAC address of the sectors Active links Displays the number of active links in connected sectors RX Throughput Displays RX Throughput of the individual sectors TX Throughput Displays TX Throughput of the individual sectors Ethernet Ethernet table displays the information about Aux, Main, and SFP ports. Figure 150: Dashboard-Ethernet Table 38: Elements in the Ethernet section Element Status RX Packets TX Packets Description Displays the speed of Ethernet ports Number of packets received Number of packets transmitted RX Throughput Displays the RX Throughput of the Ethernet TX Throughput Displays the TX Throughput of the Ethernet Configuring 60 GHz cnWave 145 Enabling internal E2E Controller E2E Controller handles important management functions such as link bring-up, software upgrades and configuration management, etc. Enable E2E Controller to configure and establish the connection. To enable E2E Controller, perform the following steps:

Note The internal E2E controller is not required if you intend to tun the E2E controller On-Premise

(refer E2EUserGuide) . Currently, the internal E2E controller is restricted to 31 nodes. 1. Click the E2E Controller option on the left pane of the Dashboard. 2. Click Enable E2E. The Enable Onboard E2E dialog box appears. Configuring 60 GHz cnWave 146 3. Enter the required details and click Enable. 4. After enabling E2E Controller, the dashboard displays the links which are connected to the device. Configuring 60 GHz cnWave 147 Figure 151: Dashboard You must right-click on the site pin to see more information about the site, as shown below:

Topology After enabling the E2E Controller, add Sites, Nodes and Links to establish the connection. To add sites, nodes and links, perform the following steps:

1. In the main dashboard page, click Topology on the left navigation pane. The Topology page appears. By default, the Sites tab is selected, as shown below:

Configuring 60 GHz cnWave 148 Figure 152: TheSitespage 2. To add a DN site, click Add New. The Add Site dialog box appears, as shown below:

Figure 153: TheAddSitedialogbox 3. Enter the Name, Latitude, Longitude, Altitude, Accuracy information, and click Save. The new DN site information gets added to to the topology, as shown below:

Configuring 60 GHz cnWave 149 Figure 154: TheupdatedSitespagewithnewsitedetails 4. To add a DN node, click on the Nodes tab in the Topology page. The Nodes page appears, as shown below:

Figure 155: TheNodespage 5. Click Add New and provide values in the Add Node dialog box, as shown below:

Configuring 60 GHz cnWave 150 Figure 156: TheAddNodedialogbox 6. Click Save. The DN node gets added to the topology. 7. To add a link, click on the Links tab in the Topology page. The Links page appears. 8. Click Add New and provide values in the Add Link dialog box, as shown below:

Configuring 60 GHz cnWave 151 Figure 157: TheAddLinkdialogbox 9. Click Save. The new link gets added to the topology, as shown below:

Figure 158: TheupdatedLinkspagewiththenewlinkdetails Support for renaming nodes A node can be renamed in the topology. To rename the node, perform the following steps:

1. From the dashboard page, navigate to Topology > Nodes. 2. Select the required node and click in the corresponding row. Then, select Edit Node. The Edit Node dialog box appears with information for the selected node. 3. Rename the node, as shown below:

Configuring 60 GHz cnWave 152 Figure 159: TheEditNodedialogbox 4. Click Save. Configuration The configuration page contains the following two configuration options:

l Network configuration l Node configuration Network configuration Network configuration is used to configure the network. User can modify the network settings. It has Basic, Management, Security and Advanced options for the configuration. Settings under Network apply to all the nodes in the network. Some apply to the E2E Controller. Enter the required information and click Submit to configure the network. Configuring 60 GHz cnWave 153 Figure 160: TheNetworkpagewithmultipletabs The Network page contains the following tabs:

l Basic tab l Management tab l Security tab l Advanced tab Configuring 60 GHz cnWave 154 Basic tab 1. By default, cnWave is an IPv6-only network. By selecting this checkbox, Layer 2 network bridging is enabled (via automatically created tunnels) across all nodes connected to a PoP. This facilitates the bridging of IPv4 traffic across the wireless networks. Figure 161: TheLayer2BridgesectionintheBasicpage The Tunnel Concentrator does encapsulation and de-encapsulation of GRE packets. If Best PoP is selected, then the node selects the best PoP as a Concentrator. If Static is selected, then the user can configure the external Concentrator that can be Linux machine/router/PoP. 2. Click Generate under Prefix Allocation to generate a unique local seed prefix automatically. cnWave networks are given an IPv6 seed prefix (e.g. face:b00c:cafe:ba00::/56 ) from which subnet prefixes are allocated to all DNs and CNs. There are two methods for allocating node prefixes with Open/R. Note PoP interface IPv6 address and seed prefix should not be in the same /64 prefix range to avoid the address conflict. l Centralized (default) - Centralized prefix allocation is handled by the E2E controller. The controller performs all prefix allocations, which prevents collisions and enables more sophisticated allocation algorithms. This is recommended for single PoP networks l Deterministic - Deterministic prefix allocation is also handled by the E2E controller. The controller assigns prefixes to nodes based on the network topology to allow PoP nodes to take advantage of route summarization and help load balance ingress traffic. This is recommended for multi-PoP networks. Configuring 60 GHz cnWave 155 Figure 162: ThePrefixAllocationsection l Seed Prefix The prefix of the entire cnWave network, is given in CIDR notation. 3. Select Prefix Length, Country, Channels, DNS Servers, and Time zone from the drop-down. Prefix Length Specifies the bit-length of prefixes allocated to each node. Country Country for regulatory settings like the EIRP limit, allowed channels, and other elements. Channels The comma separates the list of channels given to the controller for auto-configuration. Manual settings in Node > Radio page do not depend on this setting. This setting is useful especially for PTP and small meshes that use a single channel for the entire network. In such cases, set the required channel here and do not override in the node > Radio page. Changing this setting alone does the channel change, . DNS Servers DNS server list is used for :

l Resolution of NTP Server host name (can be IPv4 when Layer 2 bridge is enabled) l Given to IPv6 CPE as part of router advertisement Time Zone Time zone for all the nodes. System time in the dashboard, time field in the Events section, Log files use this timezone. NTP Servers This is NTP Server FQDN or IP Address. All nodes use this NTP Server to set the time. Node time is important when 802.1X radius authentication is used as it requires certificate validation. The time is reflected in the dashboard, time field in the Events section, and Log files . Configuring 60 GHz cnWave 156 4. Wireless Scans (Scheduled Beam Adjustment) - This feature runs a PBF scan at every defined Scan Interval. Navigate to Configuration > Network > Basic > Wireless Scans to run a PBF scan, as shown below:

Figure 163: TheWirelessScanssection The 60 GHz cnWave products can align the wireless link within an azimuth/elevation range by selecting from a number of fixed beams. A normal scan without Scheduled Beam Adjustment does the following operations:

l Beam selection occurs only on wireless link acquisition. l Disassociating and re-associating the link or otherwise causing the link to drop and re-

acquire is needed to perform a new beam selection. l Any degradation in the wireless conditions does not trigger a new beam selection unless the link drops and reacquires. The advantages of the Scheduled Beam Adjustment scan are:

l l If the link is to acquire during heavy rain, then the optimal beam at that time may be suboptimal when the weather changes. If snow accumulation is present on the unit during acquisition, the optimally selected beam may be different when the snow has melted. l Network-wide ignition in a dense deployment can cause interference when multiple nodes are acquiring. This interference can cause sub-optimal beam selection. l Any physical change to alignment that is not severe enough to cause a link drop and subsequent beam scan can be corrected for. The cost of Scheduled Beam Adjustment is:

l This feature causes a network-wide outage of approximately two minutes. For this reason, unless there is a specific issue being addressed, it is recommended to either disable this feature or configure an interval of >=24 hours. Configuring 60 GHz cnWave 157 l Simple deployments (especially PTP links) without significant external factors such as snow may not benefit from regular beam adjustment. CPE Prefix Zoning This feature restricts a PoP to advertise the IPv6 CPE prefixes of its zone alone, thereby allowing an upstream BGP router to select an optimal PoP for downstream traffic. Figure 164 is an example of multi-

PoP Layer 3 IPv6 topology, which is used to explain the feature in detail. Figure 164: Multi-PoPLayer3IPv6topology In Figure 164 (which is an example), consider the following points:

l Seed Prefix is 2001::/56. l Deterministic Prefix Allocation (DPA) is enabled and has three zones. l An operator wants CPE Address to be in different ranges than Seed Prefix. Therefore, the user traffic can be distinguished from the traffic generated by the cnWave nodes. l Customized CPE prefix is used with the range 3001:0:0:00XY::/64, where X contains values from 1 to 3. l IPv6 addresses of CPEs that fall in the range of 3001:0:0:00XY::/64 prefix. Prior to the introduction of this feature, all PoP BGP Peers advertised all the customized prefixes. Configuring 60 GHz cnWave 158 In this example (as shown in Figure 164), PoP1 BGP advertises 3001:0:0:11::/64, 3001:0:0:20::/64, and 3001:0:0:32::/64 prefixes. Similarly, PoP2 and PoP3 advertise all the three prefixes. The upstream BGP router is not able to route the packets to the best PoP. With this feature, PoP advertises the prefix of its zone alone. In the example:

l PoP1 BGP is advertising 3001:0:0:11::/64. l PoP2 BGP is advertising 3001:0:0:20::/64. l PoP3 is advertising 3001:0:0:32::/64. A summarized prefix (shorter prefix) comprising of all the customized prefixes must be configured. When a PoP is down, traffic flows through another PoP. In this example, the summarized prefix is 3001::/58 (six bits from 11 to 30). The same concept is applicable when the DHCPv6 relay is used. In that scenario, CPEs obtain IPv6 address or delegated prefix directly from the DHCPv6 server. Configuring Summarized CPE Prefix To configure the Summarized CPE Prefix feature, perform the following steps:

1. Navigate to Network > Basic from the home page. The Basic page appears. The Summarized CPE Prefix text box is available in the CPE Prefix Zoning section, as shown in Figure 165. Figure 165: TheSummarizedCPEPrefixtextbox Configuring 60 GHz cnWave 159 2. Type an appropriate value in the Summarized CPE Prefix text box. Note Using a customized CPE prefix and not configuring the summarized CPE prefix can result in routing loops. Management tab Click Management and select SNMP, SNMPv2 Settings, SNMPv3 Settings, GUIUsername and password. Figure 166: TheManagementpage l Enable SNMP - Statistics can be read from the nodes using SNMP. This setting enables SNMP. l System Contact - Sets the contact name as the System.sysContact.0 MIB-II variable. l System Location - Sets the location name as the System.sysLocation.0 MIB-II variable. l SNMPv2c Settings:

Configuring 60 GHz cnWave 160 l SNMP Community string - Supports read-only access to all OIDs. l l IPV4 Source address - Specified, SNMP queries are allowed from the hosts belonging to this IPv4 address subnet. IPV6 Source Address - Specified, SNMP queries are allowed from the hosts belonging to this IPv6 address prefix. l SNMPv3c Settings:

l SNMPv3 User - Name of the SNMPv3c user responsible for managing the system and networks. l Security Level - Following security levels are supported for the network communication:

l None - Implies that there is communication without authentication and privacy. l Authentication Only - Implies that there is communication with authentication only

(without privacy). l Authentication & Privacy - Implies that there is communication with authentication and privacy. l Authentication Type - Type of protocol used for the security of the network communication. Example: MD5 and Secure Hash Algorithm) (SHA) are used for authentication. l Authentication Key - A password for the authentication user. l GUI Users:

l Admin User Password - A password that you can set for GUI management. l Installer User Password - A password that you can set for the required installers. l Monitor User Password - A read-only password that you set for the monitoring purposes. Security tab Security tab contains Disabled, PSK, and RADIUS Server options for Wireless Security. Select the required option. Configuring 60 GHz cnWave 161 Figure 167: TheSecuritypage Wireless Security l Disabled - there is no wireless security. l PSK WPA2 pre-shared key can be configurable. A default key is used if this configuration is not present. AES-128 encryption is used for data encryption. l 802.1X Nodes are authenticated using radius server and use EAP-TLS. Encryption is based on the negotiated scheme in EAP TLS. RADIUS Server IP - IPv4/IPv6 address of the Radius authentication server. RADIUSServer port - Radius authentication server port. RADIUS server shared secret - The shared secret of a radius server. Advanced tab These settings are for advanced users only. Displays the merged configuration off all layers for a particular node. Caution The users are not recommended to do these settings. Configuring 60 GHz cnWave 162 Figure 168: TheAdvancedpage Node configuration Node configuration is used to configure the nodes via E2E Controller. E2E Controller can modify the node settings. Select the node(Radio) on the left pane to modify the settings. Node configuration contains the following tabs:

l Radio tab l Networking tab l VLAN tab l Security tab l Advanced tab Radio tab These settings apply to individual nodes selected in the left side panel. Select the required options for Transmit Power, Adaptive Modulation, Sector 1, Sector 2 from the drop-down. Enable Force GPS Disable to establish the link between indoor nodes. Configuring 60 GHz cnWave 163 Figure 169: TheRadiopage The Radio page contains the following elements:

Table 39: Elements in the Radio page Elements Description EIRP Transmit power of the radio l Maximum EIRP - The maximum EIRP transmitted by the radio. Range differs based on the platform and country selected (in the Network page). l IBF Transmit power - Transmit power using during initial beam forming. When all the links are in short-range, high transmit power can cause interference. Selecting short-range optimized will prevent this. Post beam forming, automatic power control will make sure the radio transmits at optimal power. Configuring 60 GHz cnWave 164 Elements Description Adaptive Modulation Sector 1 Select minimum and maximum coding scheme ranging from 2 to 12. l Select the frequency channel and polarity. l Channel and Polarity - When link is created in topology, the controller automatically sets the sectors channel and polarity. To manually override, click the check box and select the channel in the node configuration. Note that changing channel/polarity breaks the link. It is important to change for leaf nodes first and then higher up on DNs. Sector 1 Link

(s) Golay Golay codes help in avoiding inter-sector interference. In rare scenarios, individual links might require separate Golay codes. In most scenarios, all the links belonging to a sector are configured same Golay code. The controller automatically sets the Golay code. To manually override, select the check box and set the Golay from the drop-

down. Override All button helps in setting the same Golay code for all the links. Note Golay codes and frequency on both ends of the link should match. Sector 2 Select the frequency channel and polarity. Sector 2 Link

(s) Golay Golay code. GPS If enabled then, the radio uses internal sync rather than the GPS sync. In some scenarios like lab setups, it may be necessary to disable GPS. Caution 60 GHz cnWave V1000 and V3000 devices has only Sector 1. V3000 Small dish support The software allows the selection of smaller 40.5 dBi antenna dish. To select V3000 small dish, navigate to Configuration >Nodes > Radio. The Antenna section is available in the Radio page. Configuring 60 GHz cnWave 165 Figure 170: TheAntennasection Caution Small dish is supported only for 60 GHz cnWave V3000. Networking tab When you navigate to Nodes > Networking from the home page, the Networking page appears. In the Networking page, perform the following steps:

1. Enter the local IPv4 address. Figure 171: TheIPv4ManagementsectionintheNetworkingpage Configuring 60 GHz cnWave 166 Table 40: Elements in the IPv4 Management section Elements Description IPv4 Address Static IPv4 address of the individual node. Nodes GUI /CLI can be opened using this IP address when directly connected over Ethernet. For Over the air access, L2 Bridge should be enabled. Its predominantly used on PoP nodes with the onboard controller. Subnet Mask Gateway IP Address Subnet mask for the IPv4 address. IPv4 Gateway address. 2. Under PoP Configuration, select the options for PoP Routing, PoP Interface, and click Generate to generate PoP Interface IP Address. Figure 172: ThePoPConfigurationsectionintheNetworkingpage Table 41: Elements in the PoP Configuration section Elements Description PoP Routing PoP nodes connect to the upstream IPv6 router in one of two ways:

l Border Gateway Protocol (BGP) Routing PoP acts as a BGP peer l Static routing IP gateway address should be specified on the PoP and static route should be added on the upstream router. When the system is targeted for L2 traffic (Layer 2 bridge enabled) and an onboard controller is used, this configuration is of not much significance, recommended to set to static routing. PoP Interface The wired interface on which PoP communicates to an upstream router or switch when the L2 bridge is enabled. PoP Interface IP Address IPv6 address on the interface that the PoP node uses to communicate with the upstream router. Configuring 60 GHz cnWave 167 Elements Description IPv6 Gateway Address Gateway address. Can be left empty when the L2 bridge is enabled and no IPV6 services like NTP /Radius are used. 3. Under E2E Controller Configuration, enter E2E IPV6 Address (Address of E2E Controller). When using the onboard controller on the same node, can be left empty and GUI automatically fills the POP IPv6 address. Note If PoP DN is V5000/V3000 then, IPv6 both address is same. Table 42: Elements in the E2E Controller Configuration section Elements Description E2E IPv6 Address Address of E2E Controller. When using the onboard controller on the same node, can be left empty and GUI automatically fills the POP IPv6 address. E2E Network Prefix Seed Prefix in the CIDR format followed by a comma and the prefix length. Should be specified when BGP is used. Otherwise, optional. IPv6 CPE Interface IPv6 SLAAC provides IP prefix to downstream CPE devices. Keep it disabled when L2 Bridge is active. 4. Select the required BGP configuration. Figure 173: TheBGPConfigurationsection Configuring 60 GHz cnWave 168 Table 43: Elements in the BGP Configuration section Elements Local ASN KeepAlive Description Local ASN The BGP keepalive period in seconds. Neighbour ASN Upstream router's ASN Neighbour IPv6 Upstream router's IPv6 address Specific Network prefixes Specifically allocated network prefixes to be advertised via BGP 5. Enable the required Ethernet ports. Individual Ethernet ports can be turned off with this configuration. Figure 174: TheEthernetPortssection 6. Select the required options for Layer 2 Bridge, IPv6 Layer 3 CPE, AuX PoE (enable to power on AuX port), and Multi-PoP / Relay Port. By default, this option is disabled and PoP floods any unknown unicast ingress packets on all the L2GRE tunnels. When the option is enabled, PoP drops such packets. Configuring 60 GHz cnWave 169 Figure 175: TheLayer2BridgesectionintheNetworkingpage Table 44: Elements in the Layer 2 Bridge section Elements Description Layer 2 Bridge It has three options:

l Disable Broadcast Flood l Disable Unknown Unicast Flood l Disable IPv6 l Monitor PoP Interface Aux PoE Multi-PoP

/ Relay Port For information on Monitor PoP Interface, refer to Configuring Monitor PoP Interface, Enable PoE out (25 W) on V5000/V3000 aux port. 802.3af and 802.3at compliant devices could be powered up, passive PoE devices cannot be powered up. Note that the aux port cannot power another V5000/V3000. Indicates the wired interfaces (or Ethernet) on which OpenR is running. This element must be used:

l When DNs are connected back-to-back. l When multiple PoPs are in the network. This allows PoP nodes to forward traffic to other PoP nodes via a wired connection when the routing path of the other PoP node is closer to the traffic destination Following options are supported:

l Aux l Main l SFP l Disabled Configuring 60 GHz cnWave 170

Out of Band (OOB) interface Out of band (OOB) management interface to access the device. Management VLAN is bypassed, and data traffic will not be routed or bridged on this interface. The OOB management interface is supported at PoP. A separate IPv4 address should be configured by bypassing the Management VLAN. Navigate to Configuration > Nodes > Networking > OOB and select the required option. Enter the IPv4 address and Subnet Mask to access the device. Figure 176: TheOCBsectionintheNetworkingpage Enabling the DHCP Option 82 feature When the DHCP Option 82 feature is enabled, 60 GHz cnWave intercepts DHCPv4 REQUEST and DISCOVER packets and inserts option 82 fields. Note This feature is supported in the L2 bridge mode. In addition, you can also configure Circuit ID and Remote ID fields. Use the following wildcards to configure Circuit ID and Remote ID fields:

l $nodeMac$ - MAC address of the node in ASCII format without colons. This is a default option. l $nodeName$ - Topology name of the node. l $siteName$ - Name of the site. l $networkName$ - Network name as shown in cnMaestro. Multiple wildcards can be combined with a : delimiter. Total length of the option (after replacing wildcards with corresponding values) is truncated to 120 characters. You can also configure a custom string, which must not start with a $ character. For example, a customer's phone number. Note You cannot use the customized string and predefined wildcards together as a single sub option (Circuit ID / Remote ID). To enable the DHCP Option 82 feature, perform the following steps:

Configuring 60 GHz cnWave 171 1. Navigate to Nodes > Networking from the home page. The Networking page appears. The DHCP Option 82 feature is available in the Layer 2 Bridge section, as shown in Figure 177. Figure 177: TheDHCPOption82feature The enabled status of DHCP Option 82 implies that the feature is activated. 2. Type appropriate values in Circuit ID and Remote ID text boxes. 3. To save the configuration, click Submit. Configuring Monitor PoP Interface The Monitor PoP Interface feature is applicable to static routing and Layer 2 bridge. When the feature is enabled, the PoP interface is monitored. If the PoP interface is down, tunnels move to the next best PoP (which is best available). When there is no activity on the PoP interface, an attempt to reach the IPv4 gateway is made. Therefore, the IPv4 gateway configuration is necessary to activate this feature. To configure the Monitor PoP Interface feature, perform the following steps:

1. Select Nodes> Networking in the home page. The Networking page appears. The Monitor PoP Interface check box is available in the Layer 2 Bridge section, as shown in Figure 178. Configuring 60 GHz cnWave 172 Figure 178: TheMonitorPoPInterfacefield 2. Select the Monitor PoP Interface check box to enable the feature. VLAN tab Data VLAN The following 802.1Q features are supported per port:

l Adding single VLAN tag to untagged packets l Adding QinQ/double-tag to untagged packets l Adding QinQ outer tag to single tagged packets l Transparently bridge single/double-tagged packets (default behavior) l Remarking VLAN ID l Remarking 802.1p priority l Option to allow only the selected range of VLAN IDs l Option to drop untagged packets l Option to drop single tagged packets l Option to select the ethertype of the outer tag These options are per Ethernet port. Note VLAN configuration is applicable only when Layer2 bridge is enabled. Port Type Figure 179: Theporttypes Configuring 60 GHz cnWave 173 Transparent By default, the Ethernet port is in transparent mode. Packets will be transparently bridged without any 802.1Q processing. Q Q mode allows adding a single C-VLAN tag to untagged packets. Figure 180: NativeVLANIDandpriority Native VLAN ID and priority fields define the C-VLAN tag properties. Figure 181: AllowedVLANs Allow only the listed range of VLAN IDs. Figure 182: Untaggedtypes This option allows dropping untagged packets. Native VLAN properties are not necessary to fill when untagged packets are dropped. Configuring 60 GHz cnWave 174 QinQ QinQ mode allows adding a double tag to untagged packets and outer S-VLAN to single-tagged packets. Figure 183: NativeC-VLANIDandpriority These are the C-VLAN tag properties of added tag. Figure 184: NativeS-VLANIDandpriority These are the S-VLAN tag properties of the added outer tag. Figure 185: UntaggedandSingletaggedpackets In QinQ mode, the above options allow dropping untagged/single-tagged ingress packets. Native C-

VLAN fields are not necessary only when dropping single-tagged packets. Native S-VLAN fields are not necessary when dropping untagged and single tagged packets. Configuring 60 GHz cnWave 175 Figure 186: AllowedVLANs Allow only the listed range of VLAN IDs. VLAN ID of the outer tag is used for this check. Figure 187: QinQEtherType QinQ EtherType is used while adding an outer tag. There are no other checks for EtherType. Figure 188: VLANIDRemarking VLAN ID of the ingress packet is remarked. In the above example, if a packet with VLAN ID 10 enters an Ethernet port, it is remarked to 100. In the egress path, the reverse remarking occurs. VLAN ID 100 is remarked to 10 and egresses the ethernet port. The VLAN ID of the outer tag is used for remaking. For a double-tagged packet, S-VLAN ID gets remarked and for a single-tagged packet, C-VLAN 1D. 802.1p overriding Priority field in the (outer) VLAN tag of ingress packet can be overwritten using this option. Figure 189: VLANPriorityOverride Priority field in the (outer) VLAN tag of ingress packet can be overwritten using this option. Configuring 60 GHz cnWave 176 Management VLAN A Single tag or double tag can be added to Management traffic. Figure 190: TheManagementsection Security tab In the Security tab, enter Private key password and Radius user password. l Private key password l Radius user password Configuring 60 GHz cnWave 177 Figure 191: TheSecuritytab Controller GUI configuration This Controller GUI configuration to be made on each DN. Figure 192: ElementsspecifictoControllerconfiguration Configuring 60 GHz cnWave 178 Node GUIconfiguration Figure 193: Elementsspecifictonodeconfiguration Note Both the configurations are important for a successful authentication. RADIUS Server configuration Any RADIUS server can be used for authentication. Perform the following steps to configure the RADIUSServer:

1. Ensure RADIUS packets from IPv6 subnet (i.e., lo IP subnet is accepted in RADIUS configuration). 2. Configure EAP-TLS for RADIUS Server and setup server certificate, key. Note Server certificate is signed by CA uploaded in node configuration. 3. Set the CA certificate which signed the client certificate installed on each node. Advanced tab These settings are for advanced users only. Caution Users are not recommended to do these settings. Configuring 60 GHz cnWave 179 Figure 194: Advancedtab Configuration options under Network > Advanced and Node > Advanced are for advanced users who understand the cnWave configuration model well. It is not recommended to use these options. Shows the merged configuration from the Base layer to the Network override layer. cnWave is based on Facebooks Terragraph architecture. It follows a layered configuration model, with a nodes full configuration computed as the union of all layers in the following order:

l Base configuration - The default configuration, which is tied to a specific software version and is included as part of the image. The controller finds the closest match for a nodes software version string and falls back to the latest if no match was found. l Firmware-specific base configuration - The default configuration is tied to a specific firmware version, which is also included as part of the image. Values are applied on top of the initial base configuration layer. l Hardware-specific base configuration - The default configuration is tied to a specific hardware type, which is also included as part of the image. Each hardware type supplies configuration that changes with software versions. Values are applied on top of the firmware-based configuration layer. l Automated node overrides - Contains any configuration parameters for specific nodes that were automatically set by the E2E controller. l Network overrides - Contains any configuration parameters that should be uniformly overridden across the entire network. This takes precedence over the base configuration and automatic overrides. l Node overrides - Contains any configuration parameters that should be overridden only on specific nodes (e.g. PoP nodes). This takes precedence over the network overrides. The E2E controller manages and stores the separate configuration layers. The cnWave nodes have no knowledge of these layers, except the base configuration on the image. The nodes copy the latest base version (via natural sort order) if the configuration file on disk is missing or corrupt. Click Submit to apply the changes. Configuring 60 GHz cnWave 180 Operation Software upgrade The Software Upgrade page is used to upgrade the installed software. This page contains the following three tabs:

l Node Upgrade - to upgrade the node l Images - to upgrade the software images l Node Upgrade Status - displays the upgrade status To upgrade a node, perform the following steps:

1. From the main dashboard page, click Software upgrade on the left navigation pane. The Software Upgrade page appears, as shown below:

By default, the Node Upgrade tab is selected. 2. In the Node Upgrade page, select the required device for which you want to upgrade the node and click Prepare (as shown below). The Prepare Nodes dialog box appears. 3. In the Prepare Nodes dialog box, select the required image file for the node and click Save. Operation 181 You can also set additional options, if required, such as Upgrade Timeout, Download options, and Download Timeout. 4. Click Commit to upgrade the node. 5. To upgrade the software image, click on the Images tab in the Software Upgrade page. The Images page appears, as shown below:

Figure 195: TheImagespage 6. In the Images page, click Upload Image. You must browse and select the required image file from your machine. Example: Software image or package (cnWave60-<release>.tar.gz). The selected image file gets uploaded. You can also delete an existing image file in the Images page. 7. To view the node upgrade status, click on the Node Upgrade Status tab in the Software Upgrade page. The Node Upgrade Status page appears, as shown below:

Figure 196: TheNodeUpgradeStatuspage You can view the upgrade status for the required device nodes. Operation 182 Events The Events page displays the running and competed tasks list and these events can be exported. To export the event list click Export. Operation 183 Statistics The Statistics menu contains the following options:

l Links l Ethernet l GPS l Radio l Performance l Prefix Zone Statistics l Engineering l Border Gateway Protocol (BGP) Links The Links page has Uplink and Downlink statistical data. It displays TX and RX data of the nodes from A to Z and Z to A. Figure 197: TheLinkspage The Links page displays the following elements:

Table 45: Elements in the Links page Elements Description Link Name Link name A-Node Initiator Node Z-Node Responder Node RSSI Receiver Signal Strength Indicator The statistic value (in dB) available for each RF link The LinkFade Margin statistic values help operators to quickly assess any additional system gain or low marginal RF links (if any), which must be addressed. Link Fade Margin Operation 184 Elements Description The LinkFade Margin statistic value calculation is based on:

l Checking the RSSI received from a remote transmitter, l Assessing the availability of TX power (from the remote transmitter), and l Considering the RSSI value that is calculated based on how far away it is from an established receiver sensitively floor of -72 dBm. Rx SNR Signal to Noise Ratio Rx MCS Modulation Code Scheme of Receiver RX PER Receiver packer error rate RX Scan Beams TX Power Index Receiver scan beam index Transmitter power index EIRP The Effective Isotropic Radiated Power (EIRP) value. TX MCS Modulation Code Scheme of Transmitter TX PER Transmitter packer error rate TX Scan Beams Transmitter scan beam index RX Errors Receiver errors RX Frames Receiver frames TX Errors Transmitter errors TX Frames Transmitter frames Ethernet The Ethernet page displays Transmitting and receiving data of the nodes. Operation 185 Figure 198: TheEthernetpage The following elements are displayed in the Ethernet page:

Table 46: Elements in the Ethernet page Elements Device Name Status RX Packets TXPackets RXBytes TXBytes RXErrors TXErrors RXDropped TXDropped RXPPS TX PPS RXThroughput TXThroughput GPS Description Name of the device Ethernet link status Receiver packets Transmitter packets Receiver bytes Transmitter bytes Receiver errors Transmitter errors Receiver dropped Transmitter dropped Receiver Packets Per Second Transmitter Packets Per Second Receiver throughput Transmitter throughput The GPS page displays geographical data of the nodes. Operation 186 Figure 199: TheGPSpage The following elements are displayed in the GPS page:

Table 47: Elements in the GPS page Elements Description Device Name MAC Address Fix Type Satellites tracked Name of the device MAC address of the device GPS fix type. The fix status indicates the type of signal or technique being used by the GPS receiver to determine its location. The fix status is important for the GPS consumer, as it indicates the quality of the signal, or the accuracy and reliability of the location being reported. The number of satellites tracked Latitude Latitude of the device Longitude Longitude of the device Height Height of the device Radio The Radio page displays the radio data of the nodes. Operation 187 Figure 200: TheRadiopage The Radio page has the following elements:

Table 48: Elements in the Radio page Elements Description Device Name Name of the device MAC Address MAC address of the device Sync Mode l GPS sync:

l Entrycondition: Valid samples from GPS have been received for a few consecutive seconds (typically 2 seconds). l Exitcondition: Valid samples from GPS have not been received for a few consecutive seconds (typically 10 seconds). l RF sync: Not in GPS sync, but is reachable to a DN with GPS sync over wireless links (1-2 hops away). l Entrycondition: Conditions for GPS sync have not been met, but a link exists to at least one other DN from which to derive timing. l Exitcondition: Conditions for GPS sync have not been met and no links to other DNs exist from which to derive timing. l No sync: Neither in GPS sync nor RF sync. This is the default state. l Entrycondition: Conditions for GPS sync or RF sync are not met. l Exitcondition: Condition for GPS sync or RF sync are met. Channel Security Error Association Channel Last State Operating channel Security type Error Association Channel Last State RXThroughput Receiver throughput TXThroughput Transmitter throughput Operation 188 Performance The Performance page displays the performance graph. Figure 201: ThePerformancepage The Performance page contains the following graphs:

Table 49: Elements in the Performance page Elements Description RSSI Transmit Power Receiver Signal Strength Indicator. It is a measurement of the power present in a received radio signal Transmitting power SNR Signal to Noise Ratio MCSIndex Modulation and Coding Scheme (MCS) Index Values can be used to determine the likely data rate of your wireless connection. The MCS value essentially summarizes the number of spatial streams, the modulation type and the coding rate that is possible when connecting your wireless access point. Packet Error Ratio Packet error ratio. It is the ratio, in percent, of the number of Test Packets not successfully received by the node to the number of Test Packets sent to the node by the test set. Received Frames Transferred Frames The number of frames received at the node. The number of frames transferred from the node. Operation 189 RSSI graph Figure 202: RSSIgraph Operation 190 Transmit Power graph Figure 203: TransmitPowergraph SNR graph Figure 204: SNRgraph Operation 191 MCSIndex graph Figure 205: MCSIndexgraph Packet Error Ratio graph Figure 206: PacketErrorRatiograph Operation 192 Received Frames graph Figure 207: ReceivedFramesgraph Transferred Frames graph Figure 208: TransferredFramesgraph Prefix Zone Statistics When a Deterministic prefix is enabled and in the multi-PoP deployments, the mesh is divided into prefix zones. Prefix Zone statistics are available on the Statistics > Prefix Zone page. Operation 193 Figure 209: ThePrefixZonespage Engineering The Engineering page displays the engineering information of the system and sector. Figure 210: TheEngineeringpage Border Gateway Protocol (BGP) The BGP is the protocol used throughout the Internet to exchange routing information between networks. It is the language spoken by routers on the Internet to determine how packets can be sent from one router to another to reach their final destination. BGP has worked extremely well and continues to the be protocol that makes the Internet work. The BGP page displays the routing information. This page also contains the details of routes advertised by PoPs to their peers and the routes received by the peers. Operation 194 Figure 211: TheBGPpage Maps The Maps page displays the topology and location/sites of the deployed nodes in the cnWave network. Click the Maps icon on the left panel to display the nodes. Figure 212: TheMappage Tools The Tools menu contains Factory Reset and Logs options. Factory Reset is used to set the default settings. Operation 195 Figure 213: TheFactoryResetpage The Field Diags tab is used to view and download the error logs. To download the DN logs, select the DN node from the Select Node drop-down and click Download Logs (as shown below). Figure 214: TheFieldDiagspage To download the logs for self node, click Download Logs at the bottom and save the log file. Operation 196 Figure 215: Savinglogfiles Antenna Alignment The Antenna Alignment tool assists in optimizing the alignment of V3000 to V3000, V5000, or V1000. This feature helps you to install and align the devices to achieve optimal performances. Warning The antenna alignment tool is not a substitute for optical alignment. The optical alignment is the key to get the signal within the +/-2 degree azimuth and +/1 degree Elevation window. At this window level, the tool can be used to get away from the edge, corner or spurious beams to ensure optimal alignment. Prerequisite tasks:

l Complete a Link Plan with the help of a Link Planner from Cambium Networks. This prerequisite task provides the information on the RSSI expected for the PTP link. This must be used as target while using the antenna alignment tool. l Enter the PTP topology in cnMaestro or in the UI of a device (with the Onboard Controller on it). Then, ensure that the following tasks are performed:

l Creating two Sites and nodes. l Setting up the wireless link between the two nodes. l Ensure that the nodes are already mounted at the sites. l An installer must have access to the UI of the device. Using the Antenna Alignment tool To use the Antenna Alignment tool, perform the following steps:

1. From the landing page of the device UI, navigate to Tools > Antenna Alignment. The Antenna Alignment page appears, as shown in Figure 216. Operation 197 Figure 216: TheAntennaAlignmentpage Note If the alignment is initiated from a CN, ensure that the operating channel is set on the radio (before alignment). If the channel is not set, you must set the required channel in the Configuration page of the V3000 single node UI. 2. Click the Start Alignment button located at the top left side of the Antenna Alignment page. The Confirm message box appears (as shown in Figure 217), indicating that the link ignition will be disabled. For running the antenna alignment tool, the auto ignition needs to be disabled. If a link has been established already, it is disassociated at this level. Operation 198 Figure 217: TheConfirmmessageboxintheAntennaAlignmentpage 3. In the Confirm message box, click Continue to start the antenna alignment process. The antenna alignment process begins. Note If the alignment is initiated from a device (which is not running with Onboard Controller), perform the following actions:

a. Disable the ignition of the link at the Controller. b. Send Dis-assoc for the link from the Controller. c. When the alignment starts, select the required node from the Remote Node Model drop-down list. The Time Frame section populates the RSSI time series as shown in Figure 218. Operation 199 Figure 218: TheRSSItimeseries Following details explain about the RSSI time series that populates in the Antenna Alignment page:

l The Local Node section (located at the left side of the Antenna Alignment page) displays the direction of arrival angle with respect to the local (PoP) device. l The Remote Node section (located at the right side of the Antenna Alignment page) displays the direction of arrival angle with respect to the remote device. l In Local Node and Remote Node sections, a cell marks the direction of arrival. The color of the cell represents the RSSI based on the heatmap scale given on the left side. l The Time Frame section (located at the bottom of the Antenna Alignment page) displays the RSSI time series, along with the peak RSSI time and the latest data point (on the right end of the plot). The RSSI time series and the heatmap plots get updated in every six seconds. This is due to the processing time taken for a complete sweep of all the combinations of beams and channels. During the alignment phase, the transmit power used is the maximum configured power and the transmit power control is disabled. Note If the installer has enabled the short-range installation in the radio configuration, the transmit power control is set to the minimum configured power. Operation 200 4. Adjust the optimal RSSI that must be reached when the beams are close to the central region, as shown in Figure 219. Figure 219: TheoptionalRSSIalignment The RSSI time series must be close to the Link planner's predicted RSSI, with an error of +/-5dB. Consider the following points when adjusting the optional RSSI:

l l If the time series reporting RSSI is more than 10dB from that of the Link Planners expected RSSI, then the device has been aligned incorrectly and is being picked up by the sidelobes or spurious beams. If a cell is highlighted and the time series reporting RSSI is more than 10dB off the expected RSSI, then it is necessary to sweep beyond the current position of both azimuth and elevation, in turn to ride past the sidelobes. 5. Make use of the direction of arrival information (if there is any elevation or azimuth mismatch) to physically align the radio antennas. Operation 201 l When there is an elevation mismatch (as shown in Figure 220):

Figure 220: Exampleoftheelevationmismatch In Figure 220, the angles are exaggerated to show the point. In this example, consider that the radio has been misaligned by a down-tilt of 2 degrees behind the unit (from an installers view side). This means that the angle of the beam selected might be in the +2 degrees direction in the elevation due to beamforming. The aim is to get the optimal boresight beam. Therefore, the radio must be up tilted in the elevation direction by 2 degrees. The selected beam is now closer to the boresight beam, as shown in Figure 221. Figure 221: Oncorrectingtheelevationmismatch Operation 202 l When there is an azimuth mismatch (as shown in Figure 222):

Figure 222: Exampleoftheazimuthmismatch In Figure 222, the angles are exaggerated to show the point. In this example, consider that the radio has been misaligned in azimuth by 2 degrees to the right behind the unit (from an installers view side). This means that the angle of the beam selected might be in the -2 degrees direction due to beamforming. The aim is to get the optimal boresight beam. Therefore, the radio must be tilted in the azimuthal direction to the left by 2 degrees. The selected beam is now closer to the boresight beam, as shown in Figure 223. Figure 223: Oncorrectingtheazimuthmismatch 6. When you achieve the desired alignment and RSSI, click the End Alignment button located at the top left side of the Antenna Alignment page. If you do not click the End Alignment button, the alignment cycle ends automatically after 15 minutes. When the alignment cycle ends, the ignition state (disabled earlier) is enabled to auto Operation 203 ignition and the link is established. Figure 224 shows how the Antenna Alignment dashboard page looks on completing the antenna alignment task. Figure 224: TheupdatedAntennaAlignmentdashboardpage Ping tool The Ping feature (a tool) provides information that is used to identify the reachability between the required node and another nodes or destination (for IPv4 and IPv6). The ping tool is useful in troubleshooting the radio links. To use the ping tool, perform the following steps:

1. Navigate to Tools > Remote Command from the home page of Onboard Controller UI. The Ping page appears. 2. Set the parameters with the required values, as described in Table 50. Table 50: List of parameters in the Ping page Parameter Description Source Node Destination Type The source node for which you want to find the reachability with another node or destination. Select the required source node from the drop-down list. The required node or destination address (IPv4 or IPv6) that for which the reachability has to be identified. Following options are supported:

Operation 204 Parameter Description l Node l l IPv4 IPv6 Select the required option (mandatory). Number of times that a packet is transmitted to find the reachability. Number of Packets (-c) Default value: 3 This parameter supports values between 1 (minimum) and 10 (maximum). Type an appropriate value in the text box. Size (in bytes) of the packet. Default value: 56 This parameter supports values between 1 (minimum) and 65507 (maximum). Type an appropriate value in the text box. Buffer Size (-s) 3. Click Start Ping. The Ping Result section displays the information for the selected criteria, as shown in Figure 225. Figure 225: ThePingpage You can use the icon to download the ping result. Operation 205 Show SFP Power details The Show SFP Power Details feature (a remote command) has been introduced in this release. When you execute this remote command from the Onboard Controller UI or the node CLI, the command provides the SFP power details (as an output) for the required SFP ports and interfaces. Note Currently, the Show SFP Power Details remote command is not available in cnMaestro. To execute the Show SFP Power Details remote command, perform the following steps:

1. Navigate to Tools > Remote Command from the home page of Onboard Controller UI. The Remote Command page appears. 2. Select the required node from the Select Node drop-down list. 3. Select Show SFP Power Details from the Select Command drop-down list. 4. Click Execute. The Output section displays the SFP power details for the selected node, as shown in Figure 226. Figure 226: TheUIsupportedoutput-SFPPowerdetails Table 51 lists and describes each parameter in the output. Table 51: Output details Output Parameter Description Status Determines whether the output is valid. If the Status field contains OK, it implies that the rest of the output is valid. Operation 206 Output Parameter Description If the Status field does not contain OK, it implies that only the Status field is valid. In such cases, the Status field provides the reason for not being able to read the laser powers. CalibrationType Indicates the measurement type that is calibrated over the criteria, such as the following (for example):

l Specified transceiver temperature, l Transceiver supply voltage, l TX output power, and l RX received optical power. The value of this parameter is Internal. Indicates the unit of measurement. The value of this parameter is micro-watts (mW). Indicates the TX output power in mW. Indicates the RX received optical power in mW. Units txPwr rxPwr rxPwrMeasType Indicates whether the received power measurement represents an average input optical power. txPwr_dBm rxPwr_dBm The value of this parameter is Average. Indicates the TX output power in dBm. Indicates the RX received optical power in dBm. 5. To download the output, click the download icon located at the top left side of the Remote Command page. You can also execute the Show SFP Power Details command by using the device CLI. Log on to the device and open the CLI. At the command prompt, provide the Show SFP value and hit Enter on your keyboard. The command displays the output, as shown in Figure 227. Operation 207 Figure 227: TheCLIsupportedoutput-SFPPowerdetails cnMaestro support for Onboard Controller From System Release 1.0.1 onwards, The Onboard E2E controller can be managed by cnMaestro 2.5.0

(on-premises) for network management. 1. After the Onboard E2E controller is enabled from UI, enter the cnMaestro URL. If Cambium ID based authentication option is enabled in cnMaestro, then enter the Cambium ID and onboarding key. 2. Click Enable E2E on Onboard E2E Controller in UI. Figure 228: TheOnboardE2EControllerpage 3. Enter the cnMaestro management configuration information. Operation 208 l Remote Management - Select the required remote management option l cnMaestro URL - cnMaestro address l Cambium ID - Cambium ID of the device l Onboarding key - Password to onboard the device Figure 229: ThecnMaestrosection 4. Click Enable. 5. A new E2E Network appears in cnMaestro. Click Approve to manage it. Figure 230: InformationonthenewE2Enetwork 6. The Network Onboard window appears and provides an option to edit the network name. 7. Click Save. Operation 209 Figure 231: The60GHZcnWave-NetworkOnboard After the successful onboarding of the E2E Network, it can be managed through cnMaestro. Figure 232: TheOnboard60GHZcnWaveE2Edashboardpage Auto Manage IPv6 Routes (External E2E Controller) E2E Controller communicates with all nodes over IPv6. PoP nodes use IPv6 address of the statically configured interface to communicate with E2E Controller. CNs and DNs use the IPv6 address derived from Seed Prefix. Note The Auto Manage Routes feature requires cnMaestro 3.0.4. The Auto Manage Routes feature adds and manages the IPv6 routes at E2E Controller. These IPv6 routes are required for routing the IPv6 packets to CNs and DNs. The feature is applicable only when PoP and E2E Controller are in the same subnet. Operation 210 Single PoP network When the feature is disabled, you must add the IPv6 route by performing the following steps:

1. From the landing page of the device UI, navigate to Tools > Settings > IPv6 Routes > Add new. The Add Route page appears, as shown in the Figure 233. Figure 233: TheAddRoutepageinthecnMaestroUI 2. Type the seed prefix value in the Destination text box. 3. Type the required PoPs interface IP address in the Gateway text box. 4. Click Add. The IPv6 route is added. When the feature is enabled, all the above steps (described from step 1 to step 5 in this section) are not required and IPV6 routes are added automatically. 5. Select the Auto Manage Routes check box in the IPv6 Routes page. Figure 234 shows the location of the Auto Manage Routes check box in the IPv6 Routes page. Figure 234: TheAutoManageRoutescheckbox Operation 211 Multi-PoP network In a multi-PoP network, the Auto Manage Routes feature allows to avoid a BGP v6 router under the following conditions:

l When the Layer 2 bridge is enabled (which implies that the BGP v6 router is not required for managing data traffic). l When PoPs and E2E Controller are in the same subnet or L2 broadcast domain. In a multi-PoP network, Deterministic Prefix Allocation (DPA) is used. The mesh gets divided into zones. Each PoP is the best gateway to reach nodes in its zone. When a PoP is down, a different alive PoP must be used as a gateway to reach zones. When the Auto Manage Routes feature is enabled, it performs the following functions in a multi-PoP network:

l Understands the network topology of 60 GHz cnWave, l Keeps a track of aliveness of PoPs, and l Dynamically builds and manages the routing table. Figure 235 is an example of an IPv6 route table that is built automatically by the feature for a four PoP network. Figure 235: ExampleofIPv6routeentriesintheIPv6Routespage Figure 236 shows how the cnMaestro dashboard diagrammatically displays the routes taken by E2E Controller and the traffic controlled by cnWave nodes. Operation 212

Figure 236: DiagrammaticrepresentationofIPv6routesandtrafficcontrol Unconnected PoPs In a multi-PoP network, PoPs must be able to exchange openR packets either on wired or wireless path. Otherwise, DNs might not receive the IPv6 address allocation and do not onboard to E2E Controller. This is due to when Controller sends the Prefix Allocation message to one of the PoPs and expects the message to reach other PoPs through openR. In some cases, PoPs might be isolated temporarily, especially while building the network. Figure 237 is an example that shows two unconnected zones. Figure 237: UnconnectedzonesduetoisolatedPoPs To facilitate such a scenario, a new configuration parameter flags.enable_pop_prefix_broadcast has been introduced in this release. This parameter supports the following Boolean values:

Operation 213 l l true - When the value of this parameter is set to true, E2E Controller sends the prefix allocation message to all PoPs individually. false -When the value of this parameter is set to false, E2E Controller sends the prefix allocation message to one of the PoPs. The default value of this parameter is false (default setting). Note You must set this parameter's flag to false when there is a wired or wireless path between PoPs. You can modify the flags.enable_pop_prefix_broadcast parameter in the UI of 60 GHz cnWave. To configure the parameter, perform the following steps:

1. From the landing page of the device UI, navigate to Configuration > E2E Controller. The E2E Controller page appears. The flags.enable_pop_prefix_broadcast parameter is available in the E2E Controller page, as shown in Figure 238. Figure 238: Theflags.enable_pop_prefix_broadcastparameter 2. Modify the value of the parameter. 3. Click Save to save the configuration changes. Operation 214 Regulatory Information This chapter provides 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 Les changements ou modifications intentionnels ou non intentionnels l'quipement ne doivent pas tre effectus sauf avec le consentement exprs de la partie responsable de la conformit. De telles modifications pourraient annuler lautorisation de lutilisateur faire fonctionner lquipement et annulera la garantie du fabricant. The following topics are described in this chapter:

l Compliance with safety standards lists the safety specifications against which the 60 GHz cnWave family of ODUs has been tested and certified. It also describes how to keep RF exposure within safe limits. l Compliance with radio regulations describes how the 60 GHz cnWave family of ODUs complies with the radio regulations that are in force in various countries. Compliance with safety standards This section lists the safety specifications against which the 60 GHz cnWave platform family is tested and certified. It also describes how to keep RF exposure within safe limits. Electrical safety compliance The 60 GHz cnWave platform family hardware is tested for compliance to the electrical safety specifications listed in following Safety compliance specifications table. Table 52: Safety compliance specifications Region USA Canada Europe Specification UL 62368-1, UL 60950-22 CSA C22.2 No.62368-1, CSA C22.2 No. 60950-22 EN 62368-1, EN 60950-22 International CB certified IEC 62368-1 Edition 2 IEC 60950 -22 Electromagnetic Compatibility (EMC) compliance The EMC specification type approvals that are granted for 60 GHz cnWave platform family are listed in following table. Regulatory Information 215 Table 53: EMC compliance Region USA Canada Specification FCC Part 15 Class B RSS Gen Europe/International EN 301 489-1 V2.2.3, EN 301 489-17 V3.2.4 Human exposure to radio frequency energy Relevant standards (USA and EC) applicable when working with RF equipment are:

l ANSI IEEE C95.1-2005, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz l 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 l Directive2013/35/EU-electromagneticfieldsof 26 June 2013 on the minimum health and safety requirements regarding the exposure of workers to the risks arising from physical agents

(electromagnetic fields) (20th individual Directive within the meaning of Article 16(1) of Directive 89/391/EEC) and repealing Directive 2004/40/EC. l 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 l Health Canada limits for the general population. See the Health Canada web site at https://www.canada.ca/en.html. l EN 62232: 2017 Determination of RF field strength, power density and SAR in the vicinity of radiocommunication base stations for the purpose of evaluating human exposure (IEC 62232:2017) l EN 50385:2017 Product standard to demonstrate the compliance of base station equipment with radiofrequency electromagnetic field exposure limits (110 MHz - 100 GHz), when placed on the market l ICNIRP (International Commission on Non-Ionizing Radiation Protection) guidelines for the general public. See the ICNIRP web site at https://www.icnirp.org/cms/upload/publications/ICNIRPemfgdl.pdf and Guidelines for Limiting Exposure to Time-Varying Electric, Magnetic, and Electromagnetic Fields. Power density exposure limit Install the radios for the 60 GHz cnWave platform family of wireless solutions to provide and maintain the minimum separation distances from all persons. The applicable FCC power density exposure limit for RF energy in the 57 66 GHz frequency bands is 10 W/m2. For more information, see Human exposure to radio frequency energy. Regulatory Information 216 Calculation of power density The following calculation is based on the ANSI IEEE C95.1-1991 method, as that provides a worst-case analysis. Peak power density in the far field of a radio frequency point source is calculated as follows:

Where:

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

Calculated distances and power compliance margins The following table displays recommended calculated separation distances, for the 60 GHz cnWave for Europe the USA and Canada. These are conservative distances that include compliance margins. Note Les tableaux suivants indiquent les distances de sparation recommandes calcules pour le cnWave 60 GHz pour l'Europe, les tats-Unis et le Canada. Ce sont des distances prudentes qui incluent des marges de conformit. At these and greater separation distances, the power density from the RF field is below generally accepted limits for the general population. Note ces distances de sparation et des distances suprieures, la densit de puissance du champ RF est infrieure aux limites gnralement acceptes pour la population gnrale. 60 GHz cnWave 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 the antenna configuration of each product. Note L'ODU de la famille de plates-formes cnWave 60 GHz respecte toutes les limites EIRP applicables pour la puissance de transmission lors d'un fonctionnement en mode MIMO. Les distances de sparation et les marges de conformit incluent la compensation de la configuration d'antenne de chaque produit. Regulatory Information 217 Table 54: Calculated distances and power compliance margins Product Countries EIRP

(dBm) V1000 V2000 USA, Canada, EU USA, Canada, EU 38 49 V3000 USA, Canada 60.5 V3000 EU V5000 USA, Canada, EU 55 38 EIRP

(W) 6.3 79.4 1122 316.2 6.3 Note Maximum power density

(W/m2) Compliance distance

(m) 10 10 10 10 10 0.22 0.9 3.0 1.6 0.22 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. The calculations above are based upon platform maximum EIRP and worst case 100% duty cycle. Remarque Les rglementations exigent que la puissance utilise pour les calculs soit la puissance maximale de la rafale d'mission sous rserve de la moyenne temporelle base sur la source. Les calculs ci-dessus sont bass sur la PIRE maximale de la plate-forme et le pire des cas, un cycle de service de 100%. Compliance with radio regulations This section describes how the 60 GHz cnWave 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. 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. Regulatory Information 218 Caution Changes or modifications not expressly approved by Cambium Networks could void the users authority to operate the system. Attention Les changements ou modifications non expressment approuvs par les rseaux de Cambium pourraient annuler l'autorit de l'utilisateur faire fonctionner le systme. Type approvals The system is tested against various local technical regulations and found to comply. The Radio specifications section lists the radio specification type approvals that is granted for the 60GHz cnWave products. Some of the frequency bands in which the system operates are license exempt and the system is allowed to be used provided it does not cause interference. In these bands, the licensing authority does not guarantee protection against interference from other products and installations. Region Regulatory approvals FCC ID USA Part 15C QWP-60V1000 QWP-60V2000 QWP-60V3000 QWP-60V5000 Canada ISED RSS-210

IC ID

109AO-60V1000 109AO-60V2000 109AO-60V3000 109AO-60V5000 Federal Communications Commission (FCC) compliance The 60 GHz cnWave V1000, V2000, V3000 and V5000 comply with the regulations that are in force in the USA. Caution If this equipment does cause interference to radio or television reception. FCC Notification This device complies with part 15C of the US FCC Rules. 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. Regulatory Information 219 Innovation, Science and Economic Development Canada (ISEDC) compliance The 60 GHz cnWave V1000, V2000, V3000 and V5000 comply with the regulations that are in force in Canada. Caution If this equipment does cause interference to radio or television reception. Attention Si cet quipement cause des interfrences la rception radio ou tlvision. 60 GHz cnWave example product labels Figure 239: 60GHzcnWaveV5000DistributionNode Regulatory Information 220 Figure 240: 60GHzcnWaveV3000ClientNodeRadioonly Figure 241: 60GHzcnWaveV2000ClientNodewithnopowercord Regulatory Information 221 Figure 242: 60GHzcnWaveV1000ClientNodewithnocord Figure 243: 60GHzcnWaveV1000withUScord Table 55: Details of accessories, radio nodes, and part numbers Accessories Radio nodes Cambium Part Number 60 GHz cnWave V5000 Distribution Node V5000 C6000500A004A 60 GHz cnWave V3000 Client Node radio only V3000 C600500C024A 60GHz cnWave V2000 Client Node no power supply, no power cord V2000 C600500C030A 60 GHz cnWave V1000 Client Node with no cord V1000 C600500C14A 60 GHz cnWave V1000 with US cord V1000 C600500C001A Regulatory Information 222 Troubleshooting This section describes the troubleshooting steps and addresses frequently asked questions related to 60 GHz cnWave product deployment. l Field diagnostics logs l Setup issues in IPv4 tunneling l Link is not established l PoP not online l Link is not coming up l Link is not having expected throughput performance l Factory reset Field diagnostics logs Download the logs to view more information about the error. To download the error logs select the node from the drop-down and click Download Logs. Figure 244: TheLogstabintheToolspage After clicking Download Logs, downloading status is displayed. Troubleshooting 223 Figure 245: Downloadingthelogs To download the logs for a self node, click Download Logs at the bottom and save the log file. Figure 246: Savingthelogfiles Troubleshooting 224 Setup issues in IPv4 tunneling In IPv4 tunneling, if setup issues occurs then perform the below steps:

1. Click Configuration on the left pane, navigate to Network > Basic > Layer 2 Bridge and verify Enable Layer 2 bridge is selected. Troubleshooting 225 2. On the same page under Configuration Management, verify E2E Managed Config is selected. 3. Click Configuration > Nodes > PoP DN > Networking > Layer 2 Bridge and verify Disable Broadcast Flood and Disable IPv6 are disabled. Troubleshooting 226 4. Ensure that PoP DN and DNs are in the same subnet and verify gateway is correct. Troubleshooting 227 Link is not established If link is not established between the nodes, then verify the below options:

1. Click Configuration on the left panel. 2. Navigate to Nodes > Radio and verify Sector 2 PoP DN and DN's polarities, frequency and Golay codes. Figure 247: TheSector2sectionintheRadiopage Troubleshooting 228 3. Select DN > Networking > Ethernet Ports and ensure that specific Ethernet ports are enabled. Figure 248: TheEthernetPortssectionintheNetworkingpage 4. Click Topology on left pane, go to Nodes and verify Status is Online Initiator. Figure 249: StatusofnodesintheTopologypage 5. Click Statistics on left pane, go to Links and verify RSSI, MCS, TX Power Index. Troubleshooting 229 Figure 250: LinkdetailsintheStatisticspage 6. Go to Performance and verify the graphs. Figure 251: GraphsinthePerformancepage 7. Go to Radio and monitor the throughput capacity. Figure 252: MonitoringthethroughputintheRadiopage 8. If internal GPS is used, then verify Configuration > Nodes > Radio > GPS > Force GPS Disable is enabled. Troubleshooting 230 Figure 253: VerifyingtheForceGPSDisablecheckbox PoP not online from E2E/cnMaestro GUI This usually means that the PoP node is not able to talk to the E2E controller. Ensure that the PoP node has the E2E IPv6 configured properly. Also ensure that there is a route between the E2E controller and the PoP node, if they are not in the same VLAN. Try to ping the E2E from the PoP node (login to ssh). Link is not coming up 1. Ensure that the two ends of the radios can see each other (clear line of sight in between). If the link is using V3000, ensure that they are properly aligned. 2. Ensure that MAC address of the radios is configured correctly in the E2E Controller. 3. Ensure that GPS sync is not enabled if indoor and ensure that GPS sync is enabled if outdoor. 4. Ensure that both ends of the link has the same software version. 5. Ensure to configure country code on the E2E GUI. 6. Ensure that the two ends of the link use opposite polarity and Golay codes that matches each other. 7. Ensure that the remote ends can reach the E2E Controller IPv6 configuration (if beamforming is successful but the remote end cannot reach back to the E2E Controller, the E2E Controller/cnMaestro GUI displays link status as up, but the remote radio is offline). 8. If you already have experience setting up a link and you are trying to setup a daisy chain, ensure that there is not any interference caused by the existing link. For example, make sure that the two neighboring link use different Golay code. Troubleshooting 231 Link does not come up after some configuration change There is a possibility that the remote unit could be in a state that it uses different channel/Golay code/polarity from the near-end unit. Try to factory default the remote radio if possible. On the E2E Controller/cnMaestro, it shows that the link is up, but the remote radio is NOT online - This means that link is established but the remote end radio cannot reply to the E2E Controller. Check the E2E configuration to make sure that the IPv6 default gateway is configured correctly to allow a route between the E2E controller and the remote radio. Link is not having expected throughput performance l Check the radio GUI to ensure that the link is running as the expected MCS mode when user data is passing through. l Check to ensure that the Ethernet ports of the radios and the testing devices are negotiated to expected data rate (10Gbps). l Ensure that your testing devices are capable of handling the throughput run data throughput test by bypassing the radio link. l Do not use radio internal iperf tool to test throughput. Factory reset Recovery mode is used to reset the configuration to the factory settings. To reset the configuration, perform the following steps:

1. Go to Tools menu and click Factory Reset. Pop-up appears. Confirm to reset the device to factory reset Troubleshooting 232 2. Click Yes to reboot. 3. After the reboot, access the device using IP address 169.254.1.1. Note After factory reset, all configuration set to default mode. Troubleshooting 233 Cambium Networks Cambium Networks delivers wireless communications that work for businesses, communities, and cities worldwide. Millions of our radios are deployed to connect people, places and things with a unified wireless fabric that spans multiple standards and frequencies of fixed wireless and Wi-Fi, all managed centrally via the cloud. Our multi-gigabit wireless fabric offers a compelling value proposition over traditional fiber and alternative wireless solutions. We work with our Cambium certified ConnectedPartners to deliver purpose built networks for service provider, enterprise, industrial, and government connectivity solutions in urban, suburban, and rural environments, with wireless that just works. Installation and Configuration Guides http://www.cambiumnetworks.com/guides Technical training https://learning.cambiumnetworks.com/learn Support website (enquiries) https://support.cambiumnetworks.com Main website http://www.cambiumnetworks.com Sales enquiries solutions@cambiumnetworks.com Warranty https://www.cambiumnetworks.com/support/standard-warranty/

Telephone number list to contact Address http://www.cambiumnetworks.com/contact-us/

Cambium Networks Limited, Unit B2, Linhay Business Park, Eastern Road, Ashburton, Devon, TQ13 7UP United Kingdom www.cambiumnetworks.com Cambium Networks and the stylized circular logo are trademarks of Cambium Networks, Ltd. All other trademarks are the property of their respective owners. Copyright 2022 Cambium Networks, Ltd. All rights reserved. Cambium Networks 234

V3000 Part numbers Order the V3000 CN from Cambium Networks (V3000 CN part numbers). The V3000 CN radio is supplied without an antenna assembly, bracket, or power supply. See Precision brackets for details of suitable brackets and power supplies. Note Use a dedicated antenna assembly for V3000 CN. Order the antenna assembly required for each CN radio. Table 6: V3000 CN part numbers Cambium description 60 GHz cnWave V3000 CN radio only 60 GHz cnWave V3000 CN antenna assembly, 44.5 dBi Cambium part number C600500C024A C600500D001A 60 GHz cnWave V3000 CN antenna assembly, 40.5 dBi, 4 Pack C600500D002A 60 GHz cnWave V3000 CN antenna assembly, 44.5 dBi, 4 Pack C600500D003A 60 GHz cnWave V3000 CN Radio only Israel Only C600500C025A V5000 Distribution Node (DN) V5000 is an outdoor DN that can be connected to multiple V1000 or V3000 CNs wirelessly. V5000 supports a 10 Gigabit Ethernet interface, an 10G SFP+ interface port, and a Gigabit Ethernet Aux interface. V5000 can be powered using 60W passive POE or using an AC/DC PSU through mini an adapter (for more information, refer to the power supply and cable lengths supported in the Power supply units section). V5000 DN can also power 802.3af/at compliant auxiliary device through the Gigabit Aux interface. Figure 15: V5000DistributionNodefrontandrearviews System Hardware 34 V5000 Part numbers Order the V5000 Distribution Node (DN) from Cambium Networks (as shown in below table). The V5000 DN is supplied without a mounting bracket or power supply. Table 7: V5000 DN part numbers Cambium description 60GHz cnWave V5000 DN Cambium part number C600500A004A 60GHz cnWave V5000 Distribution Node - Israel Only C600500A005A Radio mounting brackets V1000 Wall and pole mount The V1000 CN is supplied with a mounting plate and a band clamp. The mounting plate can be used for mounting the V1000 on a wall, or it can be used with the supplied band clamp to mount the V1000 on a pole with a diameter in the range of 25 mm to 70 mm (1 inch to 2.75 inches). Note that the larger diameters can be accommodated with the customer supplied clamps. Figure 16: V1000mountingplateandbandclamp V1000 Adjustable pole mount (N000900L022A) The adjustable pole mount is used to provide elevation adjustment when a V1000 CN is mounted on a pole. The adjustable pole mount works with poles with diameters in the range of 25 mm to 70 mm (1 inch to 2.75 inches). Note The adjustable pole mount does not come with a clamp. You can use the one that is supplied with the V1000 box. Larger diameter poles can be accommodated with the customer supplied clamps. System Hardware 35 Figure 17: V1000adjustablepolemount V2000 Pole mount The V2000 CN is supplied with a mounting plate, a hose clamp, and four screws (as shown in Figure 18). These mounting accessories can be used to mount the V2000 CN on a pole. Figure 18: V2000Polemountingaccessories V2000 Adjustable pole mount The adjustable pole mount bracket (as shown in Figure 19) is used to mount the V2000 CN on a vertical pole with a diameter in the range of 25 mm to 70 mm (1 inch to 2.75 inches). The bracket provides a fine adjustment of up to +/-20 in elevation for accurate alignment of V2000. System Hardware 36 Figure 19: V2000Adjustablepolemount V3000 Precision bracket (C000000L125A) The precision bracket (as shown in Figure 20) is used to mount the V3000 CN on a vertical pole with a diameter in the range of 25 mm to 70 mm (1 inch to 2.75 inches). It accepts band clamps for larger diameter poles. The precision bracket provides fine adjustment of up to 18 in azimuth and +/-30 in elevation for accurate alignment of the V3000. System Hardware 37 Figure 20: Precisionbracket Figure 21: Precisionbracketcomponents Bracket body Azimuth arm Long (120 mm) M8 screws and flange nuts Bracket base System Hardware 38

40 mm M8 screws, plain washers, and Nyloc nuts V3000 mount 28 mm M6 screws, M8 spacers, and pole mount clamp V3000 Tilt bracket (N000045L002A) The tilt bracket (as shown in Figure 22) is used to provide elevation adjustment when a V3000 CN or V5000 DN is mounted on a pole. The tilt bracket works with poles with diameters in the range of 25 mm to 75 mm (1 inch to 3 inches). The tilt bracket assembly may be used with third-party band clamps to mount the ODU on a larger pole

(the diameter range depends on the clamps used). Figure 22: Tiltbracketassembly V5000 Pole mount (C000000L137A) The pole mount (as shown in Figure 23) is used to mount a V5000 DN on a vertical pole with a diameter in the range of 25 mm to 75 mm (1 inch to 3 inches. It provides coarse azimuth (but not elevation) adjustment. Band clamps can be used for V5000 pole mount to accommodate the larger diameter poles. System Hardware 39 Figure 23: Polemount V5000 Wall mount (C000000L136A) The wall mount (Wall mount figure below) is used to mount a V5000 DN on a vertical wall. It does not provide azimuth or elevation adjustment. The wall mount requires additional fixing hardware suitable for the type of wall. Figure 24: Wallmount Bracket part numbers Order mounting brackets by using the Cambium part numbers listed in below table. Table 8: Radio mounting bracket part numbers Bracket Radio nodes Cambium Part Number Adjustable pole mount Tilt bracket assembly Wall mount bracket V1000 V3000 V5000 N000900L022A N000045L002A C000000L136A System Hardware 40 Bracket Radio nodes Cambium Part Number Pole mount bracket Precision bracket V5000 V3000 C000000L137A C000000L125A Radio accessories Telescope mounting kit for precision brackets An alignment telescope provides the most accurate option for the alignment of the precision bracket during installation. The telescope is temporarily mounted on the bracket using the telescope mounting kit for precision brackets. The telescope mounting kit consists of a mounting plate, a knurled screw, and two rubber O-rings. Order the telescope mounting kit from Cambium Networks. Figure 25: Telescopemountingkit Order a suitable telescope from a specialist supplier specifying the following details:

Right angle, erecting, 9x50 mm alignment scope with 5 field of view System Hardware 41 Figure 26: Typicalalignmenttelescope Alignment Tube The Alignment tube (as shown in Figure 27) is designed to be used with V3000 when setting up a Point-

toPoint link. It is Ideal for aligning a Point-to-Point link that spans up to 600 m. Figure 27: AlignmentTube For longer links up to 3 km, Cambium Networks suggests to use the telescopic mounting kit

(C000000L139) and a finder scope. Note For details on how to fit the Alignment tube for V3000, refer to Fixing the alignment tube. Radio accessory part numbers Order radio accessories using the Cambium Part Number in the Radio accessory part numbers table below. Table 9: Radio accessory part numbers Accessory Radio nodes Cambium Part Number Telescope mounting kit Alignment Tube V3000 V3000 C000000L139A C000000L190A System Hardware 42 Radio external interfaces V1000 CN Figure 28: ExternalinterfacesforV1000CN Table 10: External interfaces V1000 CN Port name Connector Interface Description PSU RJ45 PoE input Standard 802.3af/at PoE 100/1000 BASE-T Ethernet Data and management System Hardware 43 V2000 CN Figure 29: ExternalinterfacesforV2000CN Table 11: External interfaces - V2000 CN Port name Connector Interface PSU RJ45 POE Input Description Passive POE 100m/1000m/2.5G BASE-T Ethernet Data and management AUX RJ45 POE Output Standard IEEE 802.3at POE 100m/1000m/2.5G BASE-T Ethernet Data and management System Hardware 44 V3000 CN Figure 30: ExternalinterfacesforV3000CN Table 12: External interfaces V3000 CN Port name Connector Interface Description SFP+

SFP 10G BASE-SR/10G BASE-LR/1G Base-SX using optional SFP+/SFP optical or copper module Data and management SFP-1G-SX / SFP-1G-LX using optional SFP optical or copper module PSU RJ45 PoE input 100m/1000m/2.5G BASE-T/5G BASE-T/ 10G BASE-T Ethernet AUX RJ45 PoE output 100/1000 BASE-T Ethernet Passive PoE Data and management Standard IEEE 802.3af/at Data and management System Hardware 45 V5000 DN Figure 31: ExternalinterfacesforV5000DN Table 13: External interfaces V5000 DN Port name Connector Interface Description SFP+

SFP 10G BASE-SR/10G BASE-LR/1G Base-SX using optional SFP+/SFP optical or copper module Data and management SFP-1G-SX / SFP-1G-LX using optional SFP optical or copper module PSU RJ45 PoE input 100m/1000m/2.5G BASE-T/5G BASE-T/ 10G BASE-T Ethernet AUX RJ45 PoE output 100/1000 BASE-T Ethernet Passive PoE Data and management Standard IEEE 802.3af/at Data and management Radio specifications The 60 GHz cnWave Radios conform to the specifications listed in Radio node specifications. Table 14: Radio node specifications Category Specification Dimensions V1000 Client Node 169 mm 100 mm 54 mm (6.6 in 3.9 in 2.1 in) System Hardware 46 Category Specification V2000 Client Node 250 mm x 200 mm x 300 mm (9.9 in x 7.9 in x 11.8 in) V3000 Client Node (44.5 dBi) V3000 Client Node (40.5 dBi) 421 mm x 347 mm x 349 mm (16.5 in x 13.6 in x 13.7 in) V5000 Distribution Node 343 mm x 198 mm x 251 mm (13.5 in x 7.7 in x 9.8 in) 280 mm 186 mm 103 mm (11.0 in 7.3 in 4.0 in) Weight V1000 Client Node 0.46 kg (1.01 lbs) V2000 Client Node 2.7 kg (5.95 lbs) V3000 Client Node (44.5 dBi) 4.17 kg (9.1 lbs) including big antenna dish 6.12 kg (13.4 lbs) = radio with dish + precision bracket V3000 Client Node (40.5 dBi) 3.2 kg (7.05 lbs) including small antenna dish 5.15 kg (11.3 lbs) = radio with dish + precision bracket V5000 Distribution Node 3.12 kg (6.8 lbs) including antenna dish 3.76 kg (8.2 lbs) = radio with dish + universal pole bracket Temperature

-40C (-40F) to +60C (140F) Wind survival 200 kph (124 mph) maximum Humidity 100% condensing Liquid and particle ingress IP66, IP67 Power consumption V1000 Client Node 10 W V2000 Client Node 30W, up to 60W with POE Out enabled V3000 Client Node 30 W, up to 60 W with PoE Out enabled V5000 Distribution Node 35 W, up to 65 W with PoE Out enabled Power input interface V1000 Client Node IEEE 802.3af V2000 Client Node Passive POE V3000 Client Node Passive PoE V5000 Distribution Node Passive PoE Power output interface V2000 Client Node IEEE 802.3af/at, 25W maximum V3000 Client Node IEEE802.3af/at, 25 W maximum V5000 Distribution Node IEEE 802.3af/at, 25 W maximum System Hardware 47 Theory of operation The 60 GHz cnWave devices support Facebook connectivity technology called Terragraph. cnWave devices implement IEEE 802.11ay WLAN standard and use 60GHz frequency band for wider spectrum and higher capacity. cnWave devices can provide multi-gigabit throughput from 100 M to 1.5 KM. Deployment of the devices uses Open/R based layer3/IPv6 mesh for efficient distribution of traffic between the nodes and higher availability of the traffic. This also overcomes non-line of sight issues. Devices use TDMA/TDD technology to achieve density deployment efficiency. Network and the nodes are configured, controlled, and monitored by a cloud-based E2E Controller. Following terminologies are used for the network deployment:

l Distribution Node (DN) - DN connects with other DN for mesh network l Client Node (CN) - CN connects to DN to provide high-speed connectivity l PoP - DN connected to the back-haul l CPE - Customer premises equipment devices like Wi-Fi router Figure 32: Deploymentscenario System Hardware 48 Power supply units (PSU) PSU Options Order PSUs from Cambium Networks. The power supply component and the part numbers are described in the following table. Table 15: Power supply component part numbers Product description Outdoor AC/DC PSU, 100W, 54V DC Waterproof PSU Cable Joiner 14-16 AWG DC to RJ45 Plug Power Adaptor Cable Gland, Long, M25, Qty 5 Radio node V3000 and V5000 V3000 and V5000 V3000 and V5000 V3000 and V5000 PoE, 60W, 56V, 5GbE DC Injector, Indoor, Energy Level 6 Supply PoE, 60W, 56V, 10GbE DC Injector, Indoor, Energy Level 6 Supply V2000, V3000, and V5000 V2000, V3000, and V5000 Cambium part number N000000L179B N000000L180A C000000L184A C000000L124A N000000L142A C000000L141A PoE, 30W, 56V, 5GbE DC Injector, Indoor, Energy Level 6 Supply V1000 and V2000 N000000L034B PoE Gigabit DC Injector, 15W Output at 56V, Energy Level 6, 0C to 50C V1000 N000900L017A AC power Injector 56V, 60W CABLE, UL POWER SUPPLY CORD SET, 720mm, AUS/NZ CABLE, UL POWER SUPPLY CORD SET, INDIA CABLE, UL POWER SUPPLY CORD SET, ARGENTINA CABLE, UL POWER SUPPLY CORD SET, CHINA CABLE, UL POWER SUPPLY CORD SET, 720mm, US V3000 and V5000 V1000, V2000, V3000, and V5000 V1000, V2000, V3000, and V5000 V1000, V2000, V3000, and V5000 V1000, V2000, V3000, and V5000 V1000, V2000, V3000, and V5000 N000065L001C N000900L011A N000900L012A N000900L013A N000900L015A N000900L031A System Hardware 49

Product description CABLE, UL POWER SUPPLY CORD SET, 720mm, EU CABLE, UL POWER SUPPLY CORD SET, 720mm, UK CABLE, UL POWER SUPPLY CORD SET, 720mm, Brazil CABLE, UL POWER SUPPLY CORD SET, 720mm, Israel Radio node V1000, V2000, V3000, and V5000 V1000, V2000, V3000, and V5000 V1000, V2000, V3000, and V5000 V1000, V2000, V3000, and V5000 Cambium part number N000900L032A N000900L033A N000900L034A N000900L037A Refer to Maximum cable lengths for details of the maximum cable lengths and the maximum PoE output power for different powering options. V1000 Power over Ethernet The V1000 CN is always powered using Power over Ethernet (PoE) at a nominal 56V, as shown in the PoE power supply to V1000 figure using the Gigabit power injector supplied with the radio, or using an IEEE 802.3af PoE output from an Ethernet switch. Figure 33: PoEpowersupplytoV1000 Table 16: PoE, 15W 56V, 1 Gigabit DC injector (N000900L017A) Category Specification Dimensions 118 mm (4.64 in) x 43 mm (1.69 in) x 32.4 mm (1.27 in) Weight 0.18 Kg (0.39 lbs) Temperature 0C (32F) to +50C (140F) Humidity AC Input 10% to 95 % non-condensing 90-264V AC, 47-63 Hz DC Output Voltage 56V System Hardware 50 Category Specification DC Output current 0.25A Efficiency Better than 84% at full load Over Current Protection Hiccup mode, recovers automatically after the fault condition is removed Hold up time At least 10 milliseconds RJ45 POE Port 7,8 ------------- DC V-

5,6 ------------- DC V+

Note The Gigabit power injector is supplied with the cnWave V1000 CN. Order part N000900L017A to obtain spares. Warning Always use an appropriately rated and approved AC supply cord-set in accordance with the regulations of the country of use. V2000 Power over Ethernet The V2000 CN is always powered using Power over Ethernet (PoE) at a nominal 56V using the Gigabit power injector supplied with the radio or using an IEEE 802.3af PoE output from an Ethernet switch. System Hardware 51 Figure 34: PowersupplytoV1000orV2000 Table 17: PoE, 30W 56V, 5GbE DC injector (N000000L034B) Category Specification Dimensions 140 mm (5.5 in) x 53 mm (2.08 in) x 35 mm (1.37 in) Weight 0.24 Kg (0.5 lbs) Temperature 0C (32F) to +50C (140F) Humidity AC Input 10% to 95 % non-condensing 90-264 V AC, 47-63 Hz DC Output voltage 56V DC Output current 0.54 A Efficiency Better than 88% at full load System Hardware 52 Category Specification Over Current Protection Hiccup mode, recovers automatically after the fault condition is removed Hold up time At least 10 milliseconds RJ45 POE Port 1,2,7,8 ------------- DC V-

3,4,5,6 ------------- DC V+

V3000, V5000 Power over Ethernet The V3000 CN and V5000 DN can be powered using DC power at a nominal 54V, using 14 AWG or 16 AWG cable, as shown in the DC power supply to V3000 or V5000 figure. Figure 35: PoEpowersupplytoV3000orV5000 System Hardware 53 Table 18: PoE, 60W, 56V, 5 GbE DC injector (N000000L142A) Category Specification Dimensions 140 mm (5.5 in) x 53 mm (2.08 in) x 35 mm (1.37 in) Weight 0.24 Kg (0.5 lbs) Temperature 0C (32F) to +50C (140F) Humidity AC Input 10% to 95 % non-condensing 90-264 V AC, 47-63 Hz DC Output voltage 56V DC Output current 1.07 A Efficiency Better than 88% at full load Over Current Protection Hiccup mode, recovers automatically after the fault condition is removed Hold up time At least 10 milliseconds RJ45 POE Port 1,2,7,8 ------------- DC V-

3,4,5,6 ------------- DC V+

System Hardware 54 V3000, V5000 Outdoor AC/DC power supply unit Figure 36: DCpowersupplytoV3000orV5000 The outdoor PSU can be installed indoors, in an outdoor cabinet, or inside street furniture. Figure 37: OutdoorAC/DCPSU,60W,54VDC System Hardware 55 Figure 38: OutdoorAC/DCPSU,100W,54VDC(N000000L179B) Table 19: Outdoor AC/DC PSU, 54V DC Category PSU Specification Part number and Dimensions N000000L178A (60W) 171 mm (6.7 in) x 62 mm (2.4 in) x 37 mm

(1.5 in) N000000L179A(100W) 220 mm (8.7 in) x 68 mm (2.7 in) x 39 mm

(1.5 in) Power 60W 100W Temperature

-40C (-40F) to +60C (140F) Humidity 20 to 95 % non-condensing Waterproofing IP65/IP67 AC Input 90-305 V AC, 47-63 Hz DC Output Voltage DC Output current 54V 60W 100W 1.15 A 1.77 A Efficiency Better than 90% at full load Over Current Protection Hiccup mode, recovers automatically after the fault condition is removed Hold up time Power factor At least 16 milliseconds Better than 0.95 System Hardware 56 Figure 39: Cablejoiner Figure 40: DCtoRJ45plugpoweradapter These cable joiners and DC to RJ45 cable adapters are used to connect to outdoor AC/DC PSU. Refer to Maximum cable lengths for details of the maximum cable lengths and the maximum PoE output power for different powering options. Note If you are using the mini RJ45 power adapter, you must use the cable gland

(C000000L123A) to ensure that the cable is protected. This cable gland comes in the radio box. For more details about the cable gland, refer to Table 23. PSU Specifications The PSUs conform to the specifications are listed in Outdoor AC/DC PSU, 54VDC. Ethernet and DC cables Maximum cable lengths Ethernet For all cnWave radios, the maximum cable length for data transmission over copper Ethernet (100BASE-

TX, 1000BASE-T, 2.5GBASE-T, 5GBASE-T, 10GBASE-T) is 100 m (328 ft) from the radio to the connected equipment. It is recommended to use outdoor braided CAT6A cable for V2000, V3000, V5000, and outdoor braided CAT5e cable for V1000. For installations where the auxiliary device is powered using ODU Aux POE port, refer to the Maximum cable lengths supported table. System Hardware 57 The maximum cable length for fiber Ethernet (10GBASE-SR, 10GBASE-LR) connections depends on the fiber used. See SFP module kits on page 19 for details of the Ethernet standards supported and maximum permitted cable lengths. Power over Ethernet (PoE) The maximum length for supplying power from a 60 W DC injector over a CAT6A Ethernet cable is shown in the Maximum cable length for Power over Ethernet table. 60W DC injector is used to power on V2000, V3000, or V5000. The maximum length for supplying power from a 30 W DC injector over a CAT6A Ethernet cable is shown in the Maximum cable length for Power over Ethernet table. 30W DC injector is used to power on V2000. Table 20: Maximum cable length for PoE supported Radio V2000 V3000 V5000 PoE enabled Maximum cable length

25W

25W

25W 390m 100m 390m 72m 330m 0m to 5m The available output power for auxiliary Power over Ethernet output in V2000, V3000, and V5000 is reduced at longer PoE cable lengths, as shown in the Maximum cable length for Power over Ethernet table. Table 21: Maximum PoE output power Radio V2000 Cable length 0m to 20m 20m to 70m 70m to 100m V3000 0m to 72m 25m 100m Maximum Aux PoE output 35W 30W 25W 25.0W 24.6W 23.6W System Hardware 58 Radio Cable length Maximum Aux PoE output V5000 0m to 5m 10m 20m 30m 40m 60m 80m 100m 25W 23.1 W 22.6W 22.1W 21.6W 20.6W 19.6W 18.6W Using AC/DC PSU with a DC power feed The maximum length for supplying power over a CAT6A Ethernet cable is shown in the Maximum cable length for DC power table. Table 22: Maximum cable length for DC power Radio PSU PoE enabled Maximum cable length 14 AWG Maximum cable length 16 AWG V3000 60W

25W 100W -

25W V5000 60W

780m 140m 780m 390m 660m 25W Not supported 100W -

25W 660m 360m 490m 90m 490m 250m 410m 410m 220m Outdoor copper CAT6A Ethernet cable Select an outdoor-rated CAT6A cable, ready terminated with RJ45 connectors in one of the following lengths:

l 25m l 50m l 100m Alternatively, terminate bulk CAT6A cable with RJ45 connectors at a length to suit each installation. Attention Always use CAT6A or better cable that has an overall copper braid shield, is outdoor rated with a UV-resistant sheath. System Hardware 59 Table 23: Terminated Ethernet cable part numbers Cambium description CAT6A outdoor cable, 305m RJ45 connector for CAT6A cable CAT6A outdoor cable, 100m Cable gland for 4-6mm cable, M25, Qty 10 Cable gland for 6-9mm cable, M25, Qty 10 CAT5E Outdoor Cable, 100m drum Cable accessories This section provides information about the required cable accessories. Figure 41: Standardcablegland Cambium part number N000082L172B N000082L174B N000000L155A C000000L176A C000000L123A N000082L016A Figure 42: Longcablegland Cable accessories available from Cambium Networks are listed in the Cable accessory part numbers table below. Table 24: Cable accessory part numbers Cambium description Cambium part number Cable gland for 6-9mm cable, M25, Qty 10 Cable gland Long, M25, Qty 5 Grounding cable, 0.6m with M6 ring to M6 ring Cable gland for 4-6mm cable, M25, Qty 10 DC to RJ45 plug power adapter Grounding cable, 1m with M6 ring to M6 ring C000000L123A C000000L124A C000000L138A C000000L176A C000000L184A N000082L116A System Hardware 60 Note One cable gland for 6-9mm cable size is included with each cnWave radio. Order additional cable glands as spares, where smaller cable size is to be used, or where the V3000 or V5000 Aux port is to be used. SFP Module kits SFP Module kits allow the connection of a V3000 CN or V5000 DN radio to a network over a 10 Gigabit optical Ethernet interface in one of the following full-duplex modes:

l l 10GBASE-SR 10GBASE-LR Order SFP+ module kits from Cambium Networks (SFP module part numbers). The SFP+ module must be used with the long cable gland. Table 25: SFP module part numbers Cambium description 10G SFP+ MMF SR Transceiver, 850nm. -40C to 85C 10G SFP+ SMF LR Transceiver, 1310nm. -40C to 85C 1G SFP MMF SX Transceiver, 850nm. -40C to 85C 1G SFP SMF LX Transceiver, 1310nm. -40C to 85C 10G SFP+ BaseT (RJ45), -40C to 85C 1000Base-T (RJ45) SFP Transceiver. -40C to 85C Cambium part number SFP-10G-SR SFP-10G-LR SFP-1G-SX SFP-1G-LX SFP-10G-Cu-EXT SFP-1G-Copper Direct attach copper (DAC) cable The DAC cable is an accessory that eliminates the need for buying two SFP Transceivers and a OM3 optical cable required to run a 10 Gigabit link. It is a low cost solution used for:

l Connecting a V5000 device that is backhauled by a V3000 device, and l Connecting V3000-to-V3000 backhauled link. The DAC cable from Cambium Networks (part number : DAC-10G-2M) is a combination of Twinax copper cable factory terminated with SFP+ modules. It delivers data rates of up to 10 Gbps. It is an outdoor, UV protected cable with two-meters length and operates at tempearatures ranging between -40C and 85C. The DAC cable (as shown in Figure 43) is a plug and play alternative that enables 10 Gigabit connectivity through the SFP+ port with no need for buying separate SFP+ transceivers and optical cables. System Hardware 61

Figure 43: DACCable Note Cambium Networks recommends to use the cable gland (part number: C000000L176A -

Cable Gland for 6 mm cable, M25, Qty 10) with the DAC cable for 60 GHZ cnWave products. Following are some of the benefits of using the DAC cable:

l Eliminates the need to buy two SFP+ transceivers and a compatible optical cable, resulting in a reduced inventory management and a low cost solution. l Consists of factory terminated and ensures watertight sealing. l Prevents installation errors when terminating optical cables to SFP+ transceivers. Use cases Following are the use cases of the DAC cable:

l Connecting a V3000-to-V3000 backhauled link With the use of the DAC cable, the V3000 devices can achieve an aggregate speed of up to 3.6 Gbps. Typically, a multi-hop point-to-point link deployment, which connects two back-to-back V3000 devices, requires the use of 10 Gig SFP+ interface. In such cases, the DAC cable (from Cambium Networks) can be used, instead of two SFP+ transceivers and an optical cable, to backhaul the traffic (as shown in Figure 44). System Hardware 62

Figure 44: V3000-to-V3000backhauledlinkconnectivityusingaDACcable l Connecting a V5000 device backhauled by a V3000 device When setting up point-to-multipoint links with the V5000 device as a distribution node (DN), if the fibre PoP is not available near the V5000 device node, a V3000 to V3000 backhaul point-to-point link is setup. For connecting V3000 to V5000, the DAC cable is recommended (as shown in Figure 45). System Hardware 63

Figure 45: V5000backhauledbyV3000usingaDACcable Optical cable and connectors Order an optical cable with LC connectors from a specialist fabricator, quoting the specification shown in the Optical optic cable and connector specification. It must be the correct length to connect the ODU to the other device. LC connectors should be supplied with dust caps to prevent dust build-up. System Hardware 64 Figure 46: Opticalopticcableandconnectorspecification Table 26: Optical cable part numbers Cambium description Optical CABLE,MM, 1m Optical CABLE,MM, 2.2m Optical CABLE,MM, 10m Optical CABLE,MM, 20m Optical CABLE,MM, 30m Optical CABLE,MM, 50m Optical CABLE,MM, 80m Optical CABLE,MM, 100m Optical CABLE,MM, 150m Optical CABLE,MM, 200m Optical CABLE,MM, 300m Optical CABLE,SM, 2.2m Optical CABLE,SM, 10m Optical CABLE,SM, 20m Cambium part number N000082L215A N000082L191A N000082L192A N000082L193A N000082L194A N000082L195A N000082L196A N000082L197A N000082L198A N000082L199A N000082L200A N000082L186A N000082L187A N000082L188A System Hardware 65 Cambium description Optical CABLE,SM, 30m Optical CABLE,SM, 50m Optical CABLE,SM, 80m Optical CABLE,SM, 100m Optical CABLE,SM, 150m Optical CABLE,SM, 200m Optical CABLE,SM, 300m Cambium part number N000082L139A N000082L140A N000082L141A N000082L142A N000082L143A N000082L189A N000082L190A System Hardware 66 System Planning Site planning This section describes factors to be considered when planning the proposed link end sites, including grounding, lightning protection, and equipment location for the ODU and PSU. 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 the 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 60 GHz cnWave 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. Note International and national standards take precedence over the requirements in this guide. Lightning protection zones Use the rolling sphere method (Rolling sphere method to determine the lightning protection zones) 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 in the zone of protection (Zone B). Similarly, where the sphere rests on two finials, the space under the sphere is in the zone of protection. Figure 47: Rollingspheremethodtodeterminethelightningprotectionzones System Planning 67 Warning Never mount equipment in Zone A. Mounting in Zone A may put equipment, structures and life at risk. Site grounding system Ensure that the site has a correctly installed grounding system on a common ground ring with access points for grounding ODU. If the outdoor equipment is to be installed on the roof of a high building, refer to the Installation section. Ensure that the system meets the following additional requirements:

l A grounding conductor is installed around the roof perimeter to form the main roof perimeter lightning protection ring. l Air terminals are installed along the length of the main roof perimeter lightning protection ring, typically every 6.1 m (20 ft). l 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 location Find a location for the ODU (and external antenna for connectorized units) that meets the following requirements:

l The equipment is high enough to achieve the best radio path. l People can be kept a safe distance away from the equipment when it is radiating. l The equipment is lower than the top of the supporting structure (tower, mast, or building) or its lightning air terminal. l 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 weather proofing 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 mid-point of the antennas. Drop cable grounding points To estimate how many grounding kits are required for each drop cable, refer to site installation and use the following criteria:

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

l The drop cable shield must be grounded at the bottom of the tower, near the vertical to the horizontal transition point. This ground cable must be bonded to the tower or tower ground bus bar (TGB) if installed. System Planning 68 l l 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 the 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, use the following additional criteria:

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

(usually on the roof). l The drop cable shield must be bonded to the building grounding system at the entry point to the equipment room. 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 site. Wind speed statistics should be available from national meteorological offices. The ODU and its mounting bracket are capable of withstanding wind speeds of up to 325 kph (200 mph). Wind blowing on the ODU subjects the mounting structure to significant lateral force. The magnitude of the force depends on both wind strength and the surface area of the ODU. Wind loading is estimated using the following formulae:

l Force (in newtons) = 0.5 V2 A Cd l is the density of air ( 1.225 kg/m3) l V is the wind speed in meters per second l A is the projected surface area of the ODU in square meters l Cd is the drag coefficient = 1.385. The drag co-efficient has been measured when the cover plate or antenna is perpendicular to the air flow. Applying these formulae to the cnWave ODU at different wind speeds, the resulting wind loadings are shown in the following ODU wind loading (newtons) table:

Table 27: ODU wind loading (newtons) Type of ODU Max surface area (square meters) Wind speed (km/h Newtons) V1000 0.017544 v3000**

0.1764 V5000 0.052597188 200*

225 250 275 300 325 67 462 118 85 583 148 105 719 185 127 871 151 177 1036 1216 224 266 312 Equivalent results in US customary units are shown in following ODU wind loading (pounds force) table:

System Planning 69 Table 28: ODU wind loading (pounds-force) Type of ODU Max surface area (square meters) Wind speed (km/h lbf) V1000 0.017544 v3000**

0.1764 V5000 0.052597188 200*

225 250 275 300 325 15 104 27 19 131 33 24 162 42 28 34 40 196 233 273 50 60 70

* 200 km/h is from measured data and used to calculate the remaining figures.

** Worst case setup with the product in -30 tilt position. PSU DC power supply Use Cambium Networks recommended DC PSU for wireless nodes and ensure the power cords and cables are appropriately rated and in accordance with the regulations of the country of use. PSU AC power supply Use Cambium recommended AC power supply for wireless nodes and ensure the power cords and cables are appropriately rated and in accordance with the regulations of the country of use. PSU location Find a location for the PSU that meets the following requirements:

DC PoE power injector l DC power injector can be mounted on a flat surface. l PSU is installed in a dry location where no condensation, flooding or rising damp is possible. l The PSU is located in an environment where it is not likely to exceed its operational temperature rating, allowing for natural convection cooling and placed not close to any fire source. l PSU can be connected to the ODU drop cable and network terminating equipment. l PSU can be connected to a compatible power supply. Outdoor AC/DC PSU Find a location for the PSU that meets the following requirements:

l The PSU is installed in a dry location where no flooding or rising damp is possible. l The PSU is located in an environment where it is not likely to exceed its operational temperature rating, allowing for natural convection cooling and placed not close to any fire source. l The PSU is not stacked and placed adjacent to the heat-generating equipment. l The PSU shall be connected to protective earth. System Planning 70 l The PSU shall be connected to ODU drop cable using cable joiner and appropriately rated cables sould be used. Lightning Surge Protection Units (LPU) All drop cables connected to the ODU (e.g. PSU and AUX drop cables) requires their own Lighting Protection Unit (LPU) or Gigabit Surge Suppressor installed close to the ODU and close to the enclosure/building entry point. The copper SFP drop cable also requires surge protection. Optical cables do not require lightning surge protection or ground cables. Guidance on the positioning of required lighting surge protection is given in the Lightning Surge Protection Units Location. Drop cable grounding points To estimate how many grounding kits are required for each drop cable, use the following criteria:

l 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. l The drop cable shield must be grounded at the building entry point. For mast or tower installations, use the following additional criteria:

l The drop cable shield must be grounded at the bottom of the tower, near the vertical to the horizontal transition point. This ground cable must be bonded to the tower or TGB, if installed. l l 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 the 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, use the following additional criteria:

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

(usually on the roof). l The drop cable shield must be bonded to the building grounding system at the entry point to the equipment room. Lightning Surge Protection Units location Lightning Surge Protection Units or Gigabit Surge Suppressors must be installed at two points on drop cables:

l There is room to mount the LPU, either on the ODU mounting bracket or on the mounting pole below the ODU. l The drop cable length between the ODU and top LPU must not exceed 600 mm. l There is access to a metal grounding point to allow the ODU and top LPU to be bonded in the following ways: top LPU to ODU; ODU to a grounding system. Find a location for the bottom LPU that meets the following requirements:

System Planning 71 l The bottom LPU can be connected to the drop cable from the ODU. l 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. l The bottom LPU can be bonded to the grounding system. Deployment Considerations This section provides a brief information specific to the deployment of 60 GHz cnWave series of products. This section covers the following topics:

l Key deployment guidelines l Sector and alignment l Minimum CN spacing l Near-far radio l Early weak interference l Avoiding the tight angle deployment l Avoiding the straight line interference l When two V5000 devices are co-located at a site l Polarity l Link Adaptation and Transmit Power Control (LATPC) Key deployment guidelines Following are some of the key guidelines that you must consider for the deployment of 60 GHz cnWave series of products:

l Mounting accuracy: Cambium Networks has three different Stock Keeping Units (SKUs). These three SKUs have different requirements in terms of alignment coverage, as shown in Table 29. Table 29: Details of alignment coverage - 60 GHz cnWave products 60 GHz cnWave product version Azimuth (in degrees) Elevation (in degrees) V5000 V3000 V1000

+/-70 per sector

+/-2

+/-40

+/-20

+/-1

+/-20 l Minimum deployment distance: A typical minimum deployment distance is based on the maximum receive signal strength of -40dBm, as listed:

l 25 meters for V1000 and V5000 l 150 meters for V3000 System Planning 72 l In case of deployments where the range is less than 25 meters (for V1000 and V5000) or 150 meters (for V3000), a short range or long range specific check box is provided in the user interface (UI) to allow this. l Deployment frequency range: 60 GHz cnWave products support the use of CH1 to CH4 (channels). Deployment in these channels depends on the allowed channels in that region. Each channel is 2.16 GHz wide and the raster frequencies supported are - 58.32 GHz, 60.48 GHz, 62.64 GHz, and 64.8 GHz. Sector and alignment Each sector is an independent radio or a baseband unit. Each sector has 2 RF tiles connected to provide extended azimuth scan range, as shon in Figure 48. Figure 48: Thesectordiagram Maximize the pole or box height during the deployment. This action minimizes the ground bounce and avoids channel fluctuations, especially for links with long distances. The suggested height is >5m. System Planning 73 You must consider the orientation of a DN node in P2MP. For example, orient the V5000 to the boresight of the RF tile to the longest link (where possible). The optimal beam angle to achieve the maximum antenna gain is at boresight of the active tile face (as shown in Figure 49 using the Red dotted line). Figure 49: Optimalbeamangle Consider the following deployment specific points:

l Avoid sticking any metallic labels on the radome. l The 60 GHz cnWave antenna tiles are located on the four marked faces. l The GPS antenna is located at the middle of the top face of the radome that is pointed to the sky. Minimum CN spacing Consider the following key points for the minimum CN spacing at a sector intersction:

l Up to 15 CNs can be installed on a single sector. Time Division Multiple Access scheme (TDMA) dynamically schedules the time slots for each wireless link on an access point, such that they do not interfere with one another. l When CNs are installed in multiple sectors, more than one CN can be talking at a given time as the sectors have independent schedulers. If both CNs installed in different sectors are located within the highlighted 20 degree range, then configure the two sectors to be on different channels to avoid interference. Figure 50 shows the minimum CN spacing at a sector intersection. System Planning 74 Figure 50: MinimumCNspacing Near-far radio Near-far ratio for links from different sectors on the same pole is based n the following factors:

l Scenario:

l One wireless link on DN sector 1 at long range, link 2 l One wireless link on DN sector 2 at short range, link 1 l Narrow angular separation between link1 and link2 (less than 20 degrees) l Configured for the same channel l Problem:

l The TG system utilizes the active Transmit Power control. l The transmit powers for link 1 is automatically set to a low level. l The transmit powers for link 2 is automatically set to a high level. l Due to narrow angular separation, the sidelobes of link 2 is interfered with link 1. As a result, the Signal-to-Noise Ratio (SNR) of link1 could degrade and this might cause the transmit power of link 1 to be boosted to a much higher level. This problem ends up in a cycle resulting in both links eventually transmitting at full power by causing network interference. l Solution:

System Planning 75 l Perform traffic test on one link at a time and then simultaneously. l If the simultaneous traffic results show degradation along with transmit power that is railed high to maximum, consider the following tasks:

o Setting the two sectors on different channels or o Capping the maximum power of the short range link. Figure 51 illustrates the problem and the solution for near-far radio. Figure 51: Near-farradio-Problemandsolution Early weak interference Early weak interference occurs when the receiver correlates to a preamble from an unwanted node, with the same Golay code (as desired). If the receiver starts decoding the preamble from the wrong node, it may be too late to recover the preamble from the correct node for that cycle. Terragraph has four Golay codes to mitigate this interference. Users can select the Golay codes {1,2,3}. Note Golay 0 is used for another purpose. Therefore, avoid selecting the Golay 0 (The use of Golay 0 has been deprecated in System Release 1.2). Consider the following points specific to the Golay codes in 802.11ad/ay:

l The 802.11ad/ay frame consists of PHY preamble, which consists of short training frame (STF) and Channel Estimation Symbol (CES). l The STF and CES are made up of complimentary Golay codes. Due to the repetition of the Golay codes, the signal can be correlated with even low SNRs. l This PHY preamble is used for frequency synchronization, timing synchronization, and channel estimation. System Planning 76 Avoiding the tight angle deployment Avoid tight P2MP angles in the deployment for the following reasons:

l In Figure 52 (shown as an example), a downlink data transmission from the DN1 to CN1 can interfere with the uplink data reception at CN2 to DN2. This interference can be both down to main lobe in very tight angles or sidelobes with up to 20 degrees delta between two CNs. l The level of interference depends on the link distances between DN1->CN1 versus DN->DN2 versus CN2->DN2. l In most cases, the main interference is due to the early weak interference. l To mitigate this early-weak interference, different Golay code assignment could be used. This issue only relates to the two links transmitting at the same time in the same physical direction. Figure 52: Tightangledeployment Avoiding the straight line interference It is recommended to avoid the straight line interference. When the desired link and interference link angles are the same, there is no assistance from the beamforming interference suppression. Figure 53: Representationofstraightlineinterference It is recommended to assign appropriate Golay codes to mitigate early-weak interference. In Figure 54, the red and orange arrows show the possible weak interference. The code assignment must be in the form of 2-2-1-1 or 1-1-2-2 but not in the 1-2-1-2 form. System Planning 77 Figure 54: AssigningGolaycodes When two V5000 devices are co-located at a site When two V5000 devices are co-located at the same site, it is recommended that one must use different channels on the two V5000 devices to start with. Evaluate the issues specific to near-far radio and Tight Angle deployment. Then, you have to configure two different channels for the two sectors or consider option 2, as shown in Figure 55. Figure 55: WhentwoV5000devicesareco-locatedatthesamesite Where local regulations allow the usage of four channels, it is advisable to choose CHA and CHB such that there are two channels apart. Example: Consider that CHA = 1 or 2 CHB = 3 or 4. The reason is that it System Planning 78 may be easier to upgrade to Channel bonding (CB2) in the future and still experience the channel isolation. Note It is important to use the same polarity at the same site. For more details about the polarity, refer to the Polarity section. Polarity 60 GHz CnWave uses TDD, which is synchronized across the network. As one sector is in the transmit phase, the neighbor sector is in the receive phase. The transmit and receive phases of the sectors are determined by the EVEN or ODD polarity. All sectors with a common polarity in a network could be transmitting or receiving at the same time. Hybrid polarity is when a node uses an EVEN polarity on one sector and an ODD on another sector. Although the hybrid polarity is possible through configuration, you must avoid this unless the installer is sure that the two links on the sectors are orthogonal. Figure 56 shows an example of the hybrid polarity. Figure 56: Hybridpolarity Link Adaptation and Transmit Power Control (LATPC) The modulation and code scheme (MCS) rate and transmit power are both adaptive values. These values are set at the transmitter, independently, for every link and for both directions. The adaptive MCS selection procedure is referred to as link adaptation (LA) and the transmit power procedure as transmit power control (TPC). There are two versions of this adaptation, data traffic, and standby, as described:

l When there is data traffic, adaptation is driven by block error rate (BLER) reported every SF

(1.6ms). A lower BLER causes the algorithm to adapt the transmit power or MCS. System Planning 79 l When there is no data traffic, the algorithm is driven by the short training frame (STF) SNR as reported by each management packet. The SNR is compared to an MCS table. If the SNR is greater or lesser than table value, the transmit power or the MCS rate is adapted accordingly. There is a maximum TX power per MCS mode (which is defined in the configuration section). During the adaptation process, the transmit power is either increased or decreased first to:

l l increase the power till the maximum per MCS power is reached or reduce the power if there is enough headroom. If the maximum power for the MCS mode has been reached, the MCS mode is reduced. Radio spectrum planning General wireless specifications The following 60 GHz cnWave wireless specifications (all variants) table lists the wireless specifications that apply to all 60 GHz cnWave frequency bands:

Table 30: 60 GHz cnWave wireless specifications (all variants) Item Specification Channel selection Open/R protocol or manual selection Manual power control Supports ATPC automatic transmit power control and maximum EIRP can be set lower than the default power limit. Integrated antenna type l V3000 44.5 dBi gain and 40.5 dBi gain l V1000 22.5 dBi gain Duplex schemes Symmetric 50:50 fixed and asymmetric fixed Range 100 m to 2 KMs, depends on the following factors:

l Frequency selected l Rain condition l Availability l EIRP limitation AES 128-bit Highly sensitive due to rain range conditions. For more information in range, refer Rain and attenuation table. Over-the-air encryption Weather sensitivity Regulatory limits Many countries impose EIRP limits (allowed EIRP) on products operating in the bands used by the 60 GHz cnWave. These are commonly identified by limitations on conducted transmit power or by antenna gain. For example:

System Planning 80 Table 31: ERC recommendation (70-03) Frequency Band Power / Magnetic Field c2 c3 57 - 71 GHz 40 dBm E.I.R.P., 23 dBm/MHz E.I.R.P. density and maximum transmit power of 27 dBm at the antenna port/ports. 57-71 GHz 55 dBm E.I.R.P., 38 dBm/MHz E.I.R.P. density and transmit antenna gain 30 dBi. CFR47 Part 15.255(c)(ii):

For fixed point-to-point transmitters located outdoors, the average power of any emission shall not exceed 82 dBm and shall be reduced by 2 dB for every dB that the antenna gain is less than 51 dBi. The peak power of any emission shall not exceed 85 dBm, and shall be reduced by 2 dB for every dB that the antenna gain is less than 51 dBi. Link planning This section describes factors that must be considered when planning links, such as range, obstacles path loss, and throughput. It is highly recommended to use Cambium LINKPlanner software when planning the links. LINKPlanner The Cambium LINKPlanner software and user guide may be downloaded from the support website (see https://support.cambiumnetworks.com/files/linkplanner/). LINKPlanner imports path profiles and predicts data rates and reliability over the path. It allows the system designer to try different antenna heights and RF power settings. It outputs an installation report that defines the parameters to be used for configuration, alignment, and operation. Use the installation report to compare predicted and actual link performance. Exclusion zones for the 59 63.9 GHz band In the three geographical areas outlined in 59 - 63.9 GHz Transmission Exclusion Zones (UK IR 2078 Section 4 and IR 2030 IR2030/7/4 (2018/316/UK)), no transmissions are permitted. Table 32: 59 - 63.9 GHz transmission exclusion zones Site Name Site Location Radius of exclusion zone from the center of site location Site 1 Site 2 Site 3 07 23 36.6 W, 57 21 3.6 N 6 Km 04 58 21 W, 51 37 16.8 N 6 Km 00 36 22.8 W, 52 38 1.8 N 6 Km 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 to achieve an accurate link feasibility assessment. The 60 GHz cnWave radios are designed to operate in Line-of-Sight (LoS) environments. System Planning 81 The 60 GHz cnWave radios operate at ranges from 15 m (49 ft) to 2000 m (1.2 miles). The operation of the system depends on the frequency channel chosen. 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:

Table 33: Input details for the link calculation Where:

Lfree_space Lexcess Lfade Lseasonal Lcapability Is:

Free Space Path Loss (dB) Excess Path Loss (dB) Fade Margin Required (dB) Seasonal Fading (dB) Equipment Capability (dB) At 60 GHz cnWave the oxygen absorption is a key component of the free space path loss and varies substantially depending on the frequency channel selected. Use LINKPlanner to calculate the oxygen absorption component for the required path and frequency channel. Data network planning This section describes factors to be considered when planning 60 GHz cnWave data networks. 60 GHz cnWave network can be deployed as point-to-point backhaul-bridge, Point-to-Multipoint coverage network and mesh network that provide network rebound. Regardless of the network topology, the underlining routing protocol between cnWave radios is always IPv6 with OpenR routing protocol. By default, the cnWave operates in IPv6 layer 3 network mode, requiring IPv6-based routing gears etc. While underlying routing in the cnWave network relies on IPv6 OpenR routing, the network can be designed to operate in pure IPv4 network mode, transporting layer two traffic (VLAN tagged and untagged) with GRE tunnels built-in by the system. There is no fundamental difference between configurations of PTP vs. PMP vs. Mesh because the underlying routing mechanism of the cnWave network is always IPv6-based OpenR routing. In a PTP network, you have one PoP DN and a CN to form a link. In a PMP network, you have one PoP DN and multiple CNs (up to 30 CNs if V5000 is used) to form a PMP cluster. You can have multiple PMP clusters to form a coverage area network. Users can have one PoP node with multiple DNs or CNs. If DNs are connected, the user gets a mesh network. User can them have multiple PoPs and DNs and if the link with each other and form a complex mesh network. System Planning 82 Point to Point-based single link Ethernet bridge A Point to Point cnWave link can be configured to work as an Ethernet bridge. The operator needs to configure one end as PoP DN, and the other end as CN. Enable Layer 2 Bridge. While the radios still run on IPv6, the Layer 2 Bridge configuration allows user Layer 2 data (VLAN tagged and untagged) to be transmitted transparently through the link. IPv6 address of the PoP and CN can be automatically generated and they do not need to be routable through the external network as long as the E2E is collocated with the PoP DN or within the same VLAN of the PoP DN. The operator can assign IPv4 addresses to the radios for management purposes. Figure 57: PointtoPointcnWavelink IPv4/L2 based PMP and mesh network planning The operator can build a complete IPv4-based network without the need for any IPv6 routers. The following figure shows the network:

Figure 58: ExampleofIPv4-basednetwork 60 GHz cnWave IPv6 IP address is generated automatically by the system. System Planning 83 1. Single PoP, E2E resides in the PoP DN When configuring the PoP E2E, the operator can configure the IPv6 address to be generated automatically. 2. Multiple PoPs, E2E controls all the PoPs cnMaestro generates the IPv6 configuration for all the PoPs. The user can download the config file from cnMaestro. This config file contains all the PoPs IPv6 configuration. The IPv6 configuration is associated with the MAC address of each PoP DN. When loading the config file to the PoP DN during initial configuration, the PoP DN chooses the IPv6 address by matching its MAC address, so there is no IPv6 address conflict. The PoP DNs automatically use the E2E controller as the default gateway of IPv6 traffic. Since IPv6 traffic is used only for management purposes, there may be no concern about overloading the E2E. (IPv6 payload traffic should be disabled in the radio configuration). The E2E chooses any one of the active PoP DN as the IPv6 default gateway. If the E2E detects that the default gateway PoP DN is down, it selects another PoP DN as a default gateway. Control traffic from E2E to all cnWave radios will be sent to the default gateway PoP, which relies on OpenR to route through correlated POP to the target radio. Select the Relay Port Interface for the PoP DNs Ethernet interface for inter-PoPs OpenR routing to work. Note IPv6 routers in the network are not required. Ensure that the PoP DNs and the E2E be in the same VLAN. Configure the IPv4 address of the radios manually. The CPE IPv4 address can be manually configured or use a DHCP server sitting in the core network. Depending on the complexity of the network, IPv4 based router may be required to route the IPv4 traffic from the CPEs. Mixture of IPv4 and IPv6 support The operator can design the network so that both IPv4 and IPv6 user data are supported. In this case, an IPv6 router is required at the core network. Ensure that if Layer 2 Bridge is enabled, by default all the user traffic including IPv6 is encapsulated in the GRE tunnel. The IPv6 user traffic is passed through the cnWave network in the GRE tunnel so that it does not be routed by the cnWave radios, but rather by an external IPv6 router. System Planning 84 Figure 59: ExampleofIPv4andIPv6supportednetwork The operator can choose certain of the radio Ethernet port to be SLAAC based port or (CPE interface), user traffic from this port is only IPv6 based and does not be encapsulated into the GRE layer two bridge when transmitted over the wireless network. Although this reduces overhead, it is not recommended since this adds complexity to the network design (the operator may need to add a BGP router to the network). IPv6 Mode network planning If the operator chooses to have the network completely run on IPv6 mode, then GRE Layer 2 Bridge is not required and a BGP router is usually required to route traffic between the wireless network and the external network. System Planning 85 Figure 60: ExampleofIPv6modenetwork IPv6 Network design consideration There are two sets of networks while designing the IPv6 network. one set is for the OpenR subnets (e.g. prefix of 56 bits and partition into multiple 64 bits subnet). Each cnWave node is assigned with a subnet. Each PoP node, besides being part of the OpenR mesh network, has a subnet assigned to it and has an IPv6 address assigned to it as PoP interface IPv6 address. If the operator lets the system automatically generates IP address configuration, the IP address always be in the format of FD00:xxxxxxx, which is a standard routable private IPv6 address. Figure 61: ExampleofanIPv6networkdesign System Planning 86 Reserved IPv6 address space If the operator let the system automatically generate the IPv6 addresses for the network, the following private IPv6 address spaces are reserved:

l FD00:CEED::0/32 for seed prefix of the mesh network l FD00:BA5E::0/32 for all the PoP nodes and the E2E Controller E2E and cnMaestro deployment consideration While the E2E and cnMaestro are two separate entities, they can be hosted on separate computers or the same computer. While the E2E communicates with the cnMaestro using IPv4, the E2E communicates with the cnWave radios using IPv6. Ethernet bridging or IP routing Layer2 Bridging L2 Bridge employs Ethernet over GRE (EoGRE) to carry the customer traffic across the Terragraph network. when L2 Bridge is enabled, all CNs and DNs automatically create an EoGRE tunnel with their PoP node and the PoP node creates a tunnel back to each of those CNs/DNs. The tunnel is capable of carrying both IPv4 and IPv6 customer traffic between CN and PoP. The IPv6 over the tunnel can be optionally disabled from the UI. Broadcast/Multicast control The downstream broadcast can be controlled by explicitly disabling it from the UI. Disabling IPv6 over the tunnel also reduces the downstream multicast traffic. Limitations l In bridge mode, the V5000 PoP node can forward 1.8 Gbps of TCP traffic and 2.0 Gbps of UDP traffic in the down-link direction. Layer 2 Bridge support in multi-PoP deployments Note Multi-PoP deployment is not recommended if on board E2E is enabled. This feature applies to Layer 2 bridging and Deterministic Prefix Allocation (DPA) are configured to be used in the network. In the Terragraph network, CNs and DNs are allocated prefixes from a seed prefix. There are various ways for allocating prefixes. In DPA, the controller assigns prefix zones to PoPs based on the network topology to allow PoP nodes to take advantage of summarizing the route and helps in load balancing ingress traffic. CNs and DNs get prefixes from the respective PoP zone which is allocated by the controller. CNs and DNs see multiple PoP nodes in the mesh, they select PoP to form GRE tunnel, by matching their lo IPv6 address with PoPs lo IPv6 address. The longest prefix match is selected as the best PoP for L2 GRE Tunnel establishment. The multi-PoP setup gives the advantage that user data traffic can take alternate routes if the best route is unavailable for some reason. Open/R makes this selection to route the traffic. If System Planning 87 PoP is unavailable, CNs and DNs switch to the next best PoP. They however keep track of their primary PoP availability and switch to it once it becomes online. External Layer 2 Concentrator support The external device can be used as an L2 GRE Concentrator. Concentrator could be a Linux server or any router or switch supporting IPv6 L2 GRE tunnels. Example: Juniper MX 100. Select the Static tunnel concentrator option and provide an IPv6 address to configure the external concentrator IPv6 address. Figure 62: Layer2TunnelConcentrator Multi-PoP deployments The following aspects must be taken care of in cnWave multi-PoP deployments:

l Layer 2 domain l Open/R on the PoP interface port l MTU of upstream switch ports l Prefix allocation Layer 2 domain All cnWave PoP nodes must be connected to the same Layer 2 broadcast domain. PoP nodes learn about other PoP nodes using IPv6 multicast packets, which do not cross broadcast domain. This allows cnWave PoP nodes to forward traffic to other cnWave PoP nodes via a wired connection when the routing path of the other PoP node is closer to the traffics destination. This concept is called Tromboning, as the traffic enters one PoP node and then leaves to another PoP node. Open/R on the PoP interface port PoP interface port must be configured to run the Open/R protocol. To enable this option, select Multi-

PoP/ Relay port Interface. System Planning 88 Figure 63: Multi-PoP/RelayPortInterface MTU of upstream switch ports PoP ports use a 2000 MTU size. So, all the switch ports must be at least 2000 MTU size. Even if the user traffic is limited to 1500 sized packets, switch ports should allow the higher MTU size. The following packets exchanged between the PoPs that can be of higher size:

l Open/R packets, l L2GRE packets (in Layer 2 mode), and l Software download packets. Prefix allocation It is recommended to select the Deterministic Prefix Allocation option for multi-PoP deployments. Figure 64: Theprefixallocationoptions Layer two control protocols 60 GHz cnWave identifies layer two control protocols (L2CPs) from the Ethernet destination address or Ethertype of bridged frames. The QoS classification can be separately configured for these protocols. Ethernet port allocation The user must decide how the three ODU Ethernet ports are allocated to the data service, management service and Local Management Service based on the following rules:

l Map the Data Service to at least one of the available wired Ethernet ports. l Map the Management Service to In-Band, or any combination of the remaining unused Ethernet ports. If the Management Service is mapped to In-Band, it shares all the ports selected for the Data Service. The Management Service can be disabled by mapping to None. l Map the Local Management Service to any combination of the remaining unused Ethernet ports. The Local Management Service can be disabled by mapping to None. The LAN configuration page ensures that the management agent can always be reached using either the management service or the local management service. System Planning 89 IP Interface Select the IP version for the IP interface of the ODU management agent. 60 GHz cnWave can operate in IPv4 mode (via L2 tunneling), IPv6 mode. Choose one IPv4 address and/or one IPv6 address for the IP interface of the ODU management agent. The IP address or addresses must be unique and valid for the connected network segment and VLAN. Find out the correct subnet mask (IPv4) or prefix length (IPv6) and gateway IP address for this network segment and VLAN. Ensure that the design of the data network permits bidirectional routing of IP datagrams between network management systems and the ODUs. For example, ensure that the gateway IP address identifies a router or another gateway that provides access to the rest of the data network. Daisy-chaining 60 GHz links When connecting two or more 60 GHz cnWave links together in a network (daisy-chaining), do not install direct copper CAT5e connections between the PSUs. Each PSU must be connected to the network terminating equipment using the LAN port. To daisy-chain 60 GHz cnWave links, install each ODU-to-

ODU links using one of the following solutions:

l A copper CAT5e connection between the Aux ports of two ODUs. l A copper CAT5e connection between the Aux port of one ODU and the SFP port of the next ODU

(using a copper SFP module). l Optical connections between the ODUs (SFP ports) using optical SFP modules at each ODU. System Planning 90 Installation 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 60 GHz cnWave radio nodes. Ensure that only qualified personnel install 60 GHz cnWave radios. Attention Pour viter toute perte de vie ou blessure physique, respectez les consignes de scurit suivantes. En aucun cas Cambium Networks ne pourra tre tenu responsable des blessures ou dommages causs lors de l'installation des nuds radio Cambium 60 GHz cnWave. Assurez-vous que seul du personnel qualifi installe les radios cnWave 60 GHz. Power lines Exercise extreme care when working near power lines. Working at heights Exercise extreme care when working at heights. PSU Always use one of the approved power supply options. Failure to use the Cambium supplied PSUs can result in equipment damage and will invalidate the safety certification and may cause a safety hazard. Grounding and protective earth The cnWave radios 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 InstallationofLightningProtectionSystems. In Canada, follow Section 54 of the CanadianElectricalCode. 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. AC Supply Always use an appropriately rated and approved AC supply cord-set in accordance with the regulations of the country of use. Powering down before servicing Before servicing 60 GHz cnWave equipment, always switch off the power supply and unplug it from the PSU. Installation 91 Do not disconnect the RJ45 drop cable connectors from the radio while the PSU is connected to the power supply. Always remove the AC or DC input power from the PSU. Primary disconnect device The primary disconnect device is the main power supply. External cables Safety may be compromised if outdoor rated cables are not used for connections that are exposed to the outdoor environment. Drop cable tester The PSU output voltage may be hazardous in some conditions such as wet weather. Do not connect a drop cable tester to the PSU, either directly or via LPUs. RF Exposure near the antenna Strong Radio Frequency (RF) fields are present close to the antenna when the transmitter is ON. Always turn off the power to the radio before undertaking maintenance activities in front of the antenna. Minimum separation distances Ensure that personnel is 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 radio is powered. Install the radios to provide and maintain the minimum separation distances from all persons. For minimum separation distances, see Calculated distances and power compliance margins. Grounding and lightning protection requirements Ensure that the installation meets the requirements defined in the Installation section. Grounding cable installation methods To provide effective protection against lightning-induced surges, observe these requirements:

l Grounding conductor runs are as short, straight and smooth as possible, with bends and curves kept to a minimum. l Grounding cables must not be installed with drip loops. l 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. l All bends, curves and connections must be routed towards the grounding electrode system, ground rod/ground bar. l Grounding conductors must be securely fastened. l Braided grounding conductors must not be used. l Approved bonding techniques must be used for the connection of dissimilar metals. Installation 92 Siting radios Radios are not designed to survive direct lightning strikes. For this reason they must be installed in Zone B as defined in Lightningprotectionzones. Mounting in Zone A may put equipment, structures, and life at risk. 60 GHz cnWave radios and mounting bracket options Mounting bracket options The 60 GHz cnWave series supports eight mounting bracket options. Select the optimum mounting bracket arrangement based on the ODU type and the choice of wall or pole mounting. The wall mount plate for V1000 and V5000 are included with the ODU. Order the remaining brackets separately. Table 34: ODU mounting bracket part numbers Bracket Pole diameter V1000 pole mount 25 mm to 70 mm (1 inch to 2.75 inches) ODU variants Bracket part number V1000 Included with V1000 V1000 wall mount Wall mount V1000 Included with V1000 V1000 adjustable pole mount 25 mm to 70 mm (1 inch to V1000 N000900L022A V3000 precision bracket V3000 tilt bracket assembly 2.75 inches) 25 mm to 70 mm (1 inch to 2.75 inches) 25 mm to 75 mm (1 inch to 3 inches) V3000 tilt bracket assembly with band clamps The diameter range depends on the clamps used. V3000 C000000L125A V3000, V5000 V3000, V5000 N000045L002A N000045L002A + third-

party band clamps V5000 pole mount 25 mm to 75 mm (1 inch to 3 inches) V5000 C000000L137A V5000 wall mount Wall mount V5000 C000000L136A Installing the cnWave radio nodes To install the radio, use the following procedure and guidelines:

1. Typical installation 2. ODU interface with LPU on the pole 3. SFP and Aux Ethernet interfaces 4. Attach ground cables to the radio 5. Mounting the ODU on the mast or wall Installation 93 Typical installation V1000 V1000 typical installation figure shows a typical installation of cnWave CN on a mast and powered through PoE Power Injector. 1. Use recommended grounding and Surge Suppressor connections. 2. Use recommended cables for interfacing ODU (refer to the supported power supply and cable length details in the Power supply units (PSU) section). 3. Always install ODU 0.5 meters below the tip of the pole. Figure 65: V1000Typicalinstallation Installation 94

V3000 V3000 typical installation figure shows a typical installation of cnWave DN on a mast and powered through outdoor AC/DC PSU. 1. Use recommended grounding and LPU connections. 2. Use recommended cables for interfacing ODU (refer to the supported power supply and cable length details in the Power supply units (PSU) section). 3. Always install ODU 0.5 meters below the tip of the pole. Figure 66: V3000Typicalinstallation Installation 95 V5000 V5000 typical installation figure shows a typical installation of cnWave DN on a mast and powered through outdoor AC/DC PSU. 1. Use recommended grounding and LPU connections. 2. Use recommended cables for interfacing ODU (refer to the supported power supply and cable length details in the Power supply units (PSU) section). 3. Always install ODU 0.5 meters below the tip of the pole. Figure 67: V5000Typicalinstallation Installation 96 ODU Interface with LPU on the pole Installing V1000 on the pole below shows steps show the installation of V1000 CN on a pole. Use 56V Gigabit Surge Suppressor for lightning protection. Ensure that the cable glands and grounding connections are made as in the following figure:

Figure 68: InstallingV1000onthepole Installation 97 Installing V3000 on the pole shows an installation of V3000 CNon a pole using a precision bracket. Use a recommended LPU for surge protection. Ensure glands and grounding connections are made as in the following figure:

Figure 69: InstallingV3000onthepole Installation 98 Installing V5000 on the pole shows an installation of V5000 DNon a pole using a tilt bracket. Use a recommended LPU for surge protection. Ensure glands and grounding connections are made as in the following figure:

Figure 70: InstallingV5000onthepole Installation 99 Attach ground cables to the radio 1. Fasten the ground cable to the radio grounding point using the M6 lug. Figure 71: Radiogroundingpoint 2. Tighten the ODU grounding bolt to a torque of 5 Nm (3.9 lb-ft). Mounting the ODU on the mast or wall Select the most appropriate bracket mounting arrangement from the options listed in the Mounting bracket options. Refer to individual procedures below for each of the options:

l V1000 pole mount l V1000 wall mount l V1000 adjustable pole mount l V3000 precision bracket l V3000 tilt bracket assembly l V3000 tilt bracket assembly with band clamps l V5000 pole mount bracket l V5000 wall mount bracket V1000 Pole mount The V1000 CN can be installed to a pole using the supplied mounting plate and jubilee clip. Follow the below instructions to mount V1000 to the pole:

1. Insert the hose clamps through the mounting plate and clamp to the pole by applying 3.0 Nm torque. Installation 100 Figure 72: Insertingthehoseclamps 2. Insert the radio into the mounting plate on the pole. Figure 73: Insertingtheradio V1000 Wall mount Follow the below instructions to mount V1000 on the wall:

1. Fix the mounting plate (supplied with the V1000 ODU) securely to a vertical wall, using suitable fixings. Note Fixing hardware is not supplied with the V1000. 2. Slide the V1000 ODU onto the mounting plate from above, ensuring that the spring clip in the mounting plate clicks into place on the radio. Installation 101 Figure 74: Fixingthemountingplateandthespringclip V1000 Adjustable pole mount Follow the below instructions to mount V1000 to the adjustable pole:

1. Insert the hose clamps through the adjustable pole mount bracket and clamp to the pole by applying 3.0 Nm torque. Figure 75: Fixinghoseclampsthroughadjustablepolemountbracket 2. Insert the radio into the adjustable pole mount bracket on the pole. Installation 102 Figure 76: Fixingtheradioonthepole V1000 Alignment The V1000 CN requires minimal effort to align as the internal antenna can beam steer +/- 45 degrees in azimuth and +/- 20 degrees in elevation from boresight. If the unit is installed with the remote node visible within this range, no further adjustment is required. V3000 Precision bracket The precision bracket is used to mount the cnWave V3000 CN on a vertical pole, providing fine adjustment up to 18 in azimuth and +/-30 in elevation for accurate alignment of the V3000. The precision bracket is compatible with pole diameters in the range of 25 mm to 70 mm (1 inch to 2.75 inches). Note that the Jubilee clamp allows for larger diameter poles and the range depends on the clamps used. These instructions illustrate the procedure for assembling and using the precision bracket. The mounting of the optional alignment telescope also explained. Installation 103 Figure 77: V3000Precisionbracket 1. Insert two of the long (120 mm) screws through the azimuth arm and the bracket body. The screws locate in the slots in the azimuth arm. Figure 78: Twoscrewsintheslotsoftheazimutharm 2. Fit two flanged M8 nuts to the long screws on the back of the bracket. Tighten using a 13 mm spanner. Installation 104 Figure 79: TwoMBnutsonthebackofbracket 3. Insert the three medium-length (40 mm) M8 screws through the bracket base and the V3000 mount. The screws locate in the slots in the bracket base. Figure 80: MBScrewsintheslotsinthebracketbase You must ensure that the pivot pin in the elevation adjuster is located in the circular hole in the V3000 mount. Installation 105 Figure 81: Thepivotpininthecircularholeofmount 4. Fit plain washers and M8 Nyloc nuts to the screws on the back of the bracket base. Tighten using a 13 mm spanner. Figure 82: PlainwashersandM8Nylocnutsonthebackofthebracket 5. Insert the two remaining long (120 mm) M8 screws through the bracket body and the azimuth arm. The screws must locate in the slots in the bracket body. Installation 106 Figure 83: MBScrewslocatedintheslotsinthebracketbody You must ensure that the pivot pin in the azimuth adjuster is located in the circular hole in the bracket body. Figure 84: Thepivotpininthecircularholeofbracketbody 6. Fit three sets of spacers, plain washers and M8 Nyloc nuts to the screws on the underside of the bracket base. Tighten using a 13 mm spanner. Installation 107

Figure 85: Fixingpacers,plainwashersandM8Nylocnuts 7. Attach the V3000 mount to the radio using the four short M6 bolts. Tighten the four bolts to a torque setting of 5.0 Nm (3.7 lb-ft) using a 13 mm spanner or socket. Figure 86: AttachingtheV3000mount 8. Attach the precision bracket to the pole using the clamp and the remaining flanged nuts. Adjust azimuth approximately and tighten the nuts to 10 Nm (7.4 lbft) using a 13 mm spanner. Installation 108 Figure 87: Attachingtheprecisionbracket 9. Lock the antenna alignment by tightening the five Nyloc nuts (see step 5 and step 8) to 10 Nm (7.4 lb-ft) using a 13 mm spanner or socket. Figure 88: Lockingtheantennaalignment Note Visit the Cambium Learning website to learn more on the precision bracket assembly:

Precision bracket alignment 1. Ensure that the three Nyloc screws for securing the bracket in elevation are loose and the fine elevation adjuster is holding the weight of the unit. Installation 109 Figure 89: ThreeNylocscrewsontheunit 2. Ensure the two Nyloc screws for securing the bracket in the azimuth are loose. Figure 90: TwoNylocscrewsintheazimuth 3. Before starting the mechanical alignment, move the fine elevation adjuster 2/3 of the way across the screw until the unit is sitting at approximately 0 degrees in elevation. Installation 110 Figure 91: Movingtheelevationadjuster 4. Move the fine azimuth adjuster to approximately the center of the available range and lock in position. Figure 92: Movingtheazimuthadjuster 5. Loosen the clamp which attaches the bracket to the pole until there is enough freedom to rotate the unit in azimuth. 6. From behind the unit, using the sight to aim towards the remote node, rotate the unit until it is approximately aligned in azimuth. Tighten the clamp. 7. While looking for the far node through the site, rotate the fine elevation adjuster until the alignment is complete in the elevation plane. One turn of the adjustment wheel is equivalent to approximately one degree of elevation. Lock the fine elevation adjuster screws in place. Installation 111 Figure 93: Lockingthefineelevationadjuster You can use the alignment tube for adjustment, as described in Fixing the alignment tube. 8. While looking for the far node through the site, rotate the fine azimuth adjuster until the alignment is complete in the azimuth plane. One turn of the adjustment wheel is equivalent to approximately one degree of azimuth. Lock the fine azimuth adjuster screws in place. 9. Make any remaining adjustments to the elevation and azimuth as required. Once complete, tighten the three Nyloc screws in place to fix the elevation alignment and do the same for the two Nyloc screws for azimuth alignment to 10 Nm (7.4 lbft) using a 13 mm spanner or socket. Precision bracket alignment optional telescope 1. Attach the telescope mount to the V3000 radio using the knurled screw. 2. Attach the telescope by looping the two elastic O-rings over the ears of the mount, ensuring that the telescope is located securely in the mount. Installation 112 Figure 94: Attachingthetelescope 3. If a telescope with a smaller body is used, shorten the O-rings by twisting. 4. Follow the previously described precision bracket alignment method, align the radio starting with the site and later fine-tune using the scope for increased accuracy. Installation 113 Fixing the alignment tube for V3000 Perform the following steps to fix the alignment tube for V3000:

1. Slide the alignment tube through the alignment slot, as shown in Figure 95. Figure 95: Slidingthealignmenttube 2. Tighten the screw to fix the alignment tube in place, as shown in Figure 96. The tube fits into the circular area. Figure 96: Fixingthealignmenttube 3. Align the device by viewing through the eyepiece, as shown in Figure 97. Installation 114 Figure 97: Aligningthedevice V3000 Tilt bracket assembly 1. Fix the mounting plate of the tilt bracket to the back of the radio using four of the short bolts, ensuring that the arrow in the plate points towards the top of the radio. Tighten the four bolts to a torque setting of 5.0 Nm (3.7 lb-ft) using a 13 mm spanner or socket. Figure 98: Fixingthemountingplateofthetiltbracket 2. Fit the two long bolts through the bracket body so that the bolt heads engage in the slots as shown. Fit two of the short bolts into the side of the bracket body but do not tighten. Installation 115 Figure 99: Fixingtwolongandshortbolts 3. Thread two of the nuts to the long bolts and tighten against the bracket body using a 13 mm spanner. Fit the bracket strap and thread the remaining nuts onto the long bolts. Figure 100: Fixingthebracketstrap 4. Fix the assembled bracket body to the pole, adjust the azimuth angle, and tighten the nuts to a torque setting of 10.0 Nm (7.4 lb-ft) using a 13 mm spanner, ensuring that the arrow in the body is pointing upwards. Installation 116 Figure 101: Fixingtheassembledbracketbody 5. Fit the mounting plate to the bracket body by positioning the open- ended slots over the short bolts. Insert the remaining short bolts through the longer curved slots into the threaded holes in the bracket body. Adjust the elevation angle and tighten the bolts to a torque setting of 5.0 Nm

(3.7 lb-ft) using a 13 mm spanner or socket. Figure 102: Fixingthemountingplateandadjustingtheelevation V3000 Tilt bracket assembly with band clamps Follow the below instructions to assemble the tilt bracket with band clamps:

1. Follow step 1 of the V3000 tilt bracket assembly procedure. 2. Feed the band clamps through the slots in the bracket body. Secure the bracket body to the pole using band clamps (not supplied by Cambium), ensuring that the arrow in the body is pointing upwards. Adjust the azimuth angle, and tighten the band clamps to a torque setting of 6.0 Nm (4.5 lb-ft). 3. Fix the mounting plate to the bracket body with four of the short bolts, using a 13 mm spanner or socket. Adjust the elevation angle, and tighten the bolts to a torque setting of 5.0 Nm (3.7 lb-ft). Installation 117

Declaration of Authorization

We

Name:

Address:

City:

Country:

Declare that:

Cambium Networks Limited

Unit B2, Linhay Business Park, Eastern Road,

Ashburton, Devon, TQ13 7UP

UK,

Name Representative of agent:

Agent Company name:

Address:

City:

Country

Daniel Sims (1)

RN Electronics Ltd (a part of Kiwa)

Arnolds Court, Arnolds Farm Lane

Mountnessing, Brentwood, Essex, CM13 1UT

United Kingdom

is authorized to apply for Certification of the following product(s):

Product description: 60 GHz Outdoor Wireless Ethernet Bridge

Type designation: V2000

Trademark:

Cambium Networks

Validity/ expiry date: 31st December 2022

on our behalf.

Date:

City:

Name:

11th August 2022

Ashburton

Donald W Reid (2)

Function:

Senior Principal Regulatory Engineer

Signature:

Notes:

(1): Required for FCC/ISED application

(2): For FCC it must be the Grantee Code “owner” as person listed with FCC, and ISED the person listed with ISED

number.

RN Electronics Ltd (a part of Kiwa)

Arnolds Court, Arnolds Farm Lane

Mountnessing,

Brentwood,

Essex,

CM13 1UT

United Kingdom

Date: 3rd August 2022

Subject: Calibration

FCC: QWP-60V2000

IC: 109AO-60V2000

To whom it may concern

We, Cambium Network Ltd, hereby attest that the 60 GHz cnWave V2000 RF Tile, SSPXA-

001326 (QD-46), is calibrated at the supplier’s factory to verify the platform baseline operation

at maximum supported EIRP, the RF Tile performance is verified by Cambium Networks in

Device Verification Testing.

The 60 GHz cnWave V2000 operational software requires the selection of a country code that

applies relevant parameter changes to ensure operation within the regulations of the country

where the 60 GHz cnWave V2000 is installed.

Once the device has left the factory, the user does not have access to the device to increase

the output power, the country setting limits the V2000 operation to local regulations.

Yours faithfully,

Donald W Reid

CEng MIET, MInstLM

Senior Principal Regulatory Engineer

Cambium Networks Ltd.

Declaration of non-usage of external phase-locking inputs nd Date: 2 August 2022 Attention director of certification To Whom It May Concern:

As per the requirement under 47 CFR 15.255(h), and RSS-201 Annex J.7 we hereby declare that 60 GHz cnWave V2000 product is not equipped with any external phase-

locking inputs that permit beam- forming arrays to be realized. By:

1

(Signature Donald W Reid

(Print name) Title:

Senior Principal Regulatory Engineer On behalf of:

Cambium Networks Limited

(Company Name) Telephone: +44 (0) 1364 655667 1 Annex A Must be signed by FCC / ISED registered person on file for the company.

FCC, Request for non-disclosure

RF_501, Issue 8

Date: 21-Nov-2018

Page 1 of 1

Company Name: Cambium Networks Limited

Address:

City:

Country:

Unit B2, Linhay Business Park, Eastern Road

Ashburton, Devon

United Kingdom, TQ13 7UP

To: Telefication B.V., Dept. FCC TCB

Edisonstraat 12A

6902 PK ZEVENAAR

The Netherlands

Subject: Request for confidentiality FCC ID: QWP-60V2000

Reference number:

Dear FCC TCB,

1. Long-Term Confidentiality

Pursuant to 47 CFR Section 0.459(a) & (b), we hereby requests non-disclosure and confidential treatment

of the following materials submitted in support of FCC certification application:

Block Diagrams

Operational Description

Schematic Diagrams

Tune-up Procedure

Above materials contain secrets, proprietary and technical information, which would customarily be

guarded from competitors under 47 CFR, section 0.457(d)(2). Disclosure or publication or any portion of

this company confidential material to other parties could cause substantial competitive harm and provide

unjustified benefits for competitors.

2. Short-Term Confidentiality (STC)

Pursuant to Public Notice DA 04-1705 of the Commission’s policy, in order to comply with the marketing

regulations in 47 CFR §2.803 and the importation rules in 47 CFR §2.1204, applicant hereby requests

Short-Term Confidential treatment of the following materials (See notes below):

Internal Photos

User’s Manual

Test Set-up Photos

External Photos

Justification: The applicant requests the exhibits selected above as short term confidential be withheld

from public view for a period of 180 days from the date of the grant of equipment authorisation and prior

to marketing. This is to avoid premature release of sensitive information prior to marketing or release of

the product to the public. The applicant is aware that they are responsible to notify the CB in the event

information regarding the product or the product is made available to the public before the requested

period has expired, at which point the CB will release the documents listed above for public disclosure,

In line with FCC public notice DA 04-1705.

Date: 12th August 2022

Name and signature of applicant: Daniel Sims (Agent)

Notes:

1) A document or type of document can only have ONE type of confidentiality!

2) Short-Term confidentiality is in principle for 45 days from date of grant; it can be extended max 3 times (total time 180 days max.)!

The planned date should stated in the RF731 application form.

3) FCC must be informed when marketing begins earlier.

FCC, Request for non-disclosure

RF_501, Issue 8

Date: 21-Nov-2018

Page 1 of 1

4) Release takes place automatically thus extension must be requested in time. Telefication does not remind you of this!

5) Request for extension or for release must be received by Telefication at least 7 days before date of actual marketing or before

expiration of the STC period