Cambium Networks 50450I Fixed Outdoor Point to Multipoint Transceiver User Manual 450 Platform User Guide

Cambium Networks Limited Fixed Outdoor Point to Multipoint Transceiver 450 Platform User Guide

UserManual.wiki >

Cambium Networks >

50450I User Manual >

User Manual - Part 2 HTML Version

User Manual - Part 2

Chapter 3: System planning Radio Frequency planning

Page 3-21

Figure 49 Example layout of 6 Access Point sectors (ABC), 60-degree sectors

An example for assignment of frequency channels and sector IDs is provided in the following

table.

Table 77 Example 5.8 GHz 3-channel assignment by access site

Symbol

Frequency

A 5.740 GHz

B 5.760 GHz

C 5.780 GHz

Chapter 3: System planning Radio Frequency planning

Page 3-22

Considerations on back-to-back frequency reuse

Cambium Networks recommends using back-to-back (ABAB) frequency reuse, as shown in Figure

48. This means that a base site of four sectors can be created using two frequencies, which works

very well and helps define networks in situations where high capacity is required in a limited

amount of spectrum.

The conditions necessary to implement this plan are:

• GPS synchronization: all the access points transmit at the same time

• Uplink and Downlink timings across APs do not overlap: they can be adjusted using the frame

calculators and co-location tools provided by Cambium

• Uplink power control to ensure that all signals are received on the uplink at the same level: this

is automatically enabled on all sectors

• There are no reflecting objects which are too large in the exclusion zones defined in this

section.

• The SMs do not normally have line-of-sight (LoS) to an interfering base station. The worst-case

range ratio in Figure 48 is 5:1 which in LoS only gives 14 dB protection. Greater than 30 dB is

required for 256QAM capability. Down tilt can be used to advantage when the elevation

beamwidth is low. Also, the range ratio applies to the longest distance SM, shorter distance

SMs have a better range ratio. This frequency reuse plan may not always give 256QAM for the

longest distance SMs. It is usually a good compromise between using more spectrum and

guaranteed modulation rate.

Reflecting objects

Figure 50 shows two diagrams of the same reflecting object. Uplink interference demonstrates the

situation when the two SMs are transmitting at the same time. SM2 should be received cleanly by

the AP for Sector 3. At the same time interference can arise from SM1 via the reflecting object and

cause a lower Signal-to-Interference ratio than required at AP3. This may either cause transmission

errors which are corrected by ARQ or cause the selected modulation rate to be lowered. Either

may cause a lower throughput from SM2 and therefore sector 3.

Downlink interference shows the situation when AP3 interferes with SM1. Again, the transmission

may be reduced by errors or a reduction in modulation rate.

Chapter 3: System planning Radio Frequency planning

Page 3-23

Figure 50 Reflection

Reflection likelihood guidance

As shown in the previous section, reflection can cause a decrease in throughput in an ABAB base

site. This section provides guidance on whether a reflection is likely to cause interference. The first

condition for whether a reflection can cause the data rate to reduce is that the reflecting object

must be in view of the AP and the SM to re-transmit the signal. If this is not the case, then the

object cannot cause interference.

Given that the potential reflecting object is seen by the AP and the SM, there are a range of object

sizes and a range of zones where we can predict that interference will occur which may reduce the

throughput when both sector 1 and sector 3 are carrying traffic.

Figure 51 and Figure 52 show regions enumerated A, B, C, and D. We also need to consider objects

of size 1, 2, 3 and 4 and define the areas where the objects may interfere.

• object size 1: a flat building face with a clear reflecting property from sector to AP

• object size 2: random metalwork such as a wireless tower

• object size 3: a 0.5 X 0.5m flat metallic face or tree

• object size 4: a 0.2 X 0.2m random metal structure or 0.5 X 0.5m foliage.

The conditions for no interference are:

• size 2 outside zone B

• size 3 outside zone C

• size 4 outside zone D

The size 1 object can interfere at large distances. It is necessary to look at the geometry by which

reflection could occur and cause interference. Typically, this will occur at a restricted range of

azimuths and ranges.

Chapter 3: System planning Radio Frequency planning

Page 3-24

Figure 51 Sector Antenna

Chapter 3: System planning Radio Frequency planning

Page 3-25

Figure 52 cnMedusa Antenna

Chapter 3: System planning Radio Frequency planning

Page 3-26

Figure 51 and Figure 52 each have three diagrams scaled in meters where Figure 51 is for the

sector antenna and Figure 52 is for cnMedusa. In each figure the distances and heights assume a

typical down tilt of 4°.

In each figure the top diagram represents the clearances required at zero azimuth. The middle

diagram represents the scaling required to the top diagram to allow for differences in azimuth of

the considered reflecting object. The bottom diagram is the scaled version of the top diagram

allowing for the dotted azimuth line in the middle diagram.

PMP 450m Series AP is based on Massive MU-MIMO technology. It is a 14x14 MIMO system which

allows simultaneous communication to up to seven SMs.

Figure 53 PMP 450m Series AP antenna beam

PMP 450m installation recommendations

• For best performance it is recommended to have a clearance zone around the mast. The

clearance zone depends on the surrounding environment and the antenna’s down tilt. If the

mast is surrounded by metal then larger clearance is required compared to an environment

where the antenna is surrounded by foliage

• SMs should be spread in azimuth of AP antenna

• 450m is susceptible to movement, for best MU-MIMO performance it is recommended that the

450m AP is mounted/installed on a mast that is extremely rigid (no movement and is 100%

vertical).

• LINKPlanner can be used to plan SMs across the AP antenna azimuth

Chapter 3: System planning Link planning

Page 3-27

Link planning

This section describes factors to be considered when planning links, such as range, obstacles path

loss and throughput. LINKPlanner is recommended.

Range and obstacles

Calculate the range of the link and identify any obstacles that may affect radio performance.

Perform a survey to identify all the obstructions (such as trees or buildings) in the path and to

assess the risk of interference. This information is necessary in order to achieve an accurate link

feasibility assessment.

The 450 Platform Family is designed to operate in Non-Line-of-Sight (NLoS) and Line-of-Sight

(LoS) environments. An NLOS environment is one in which there is no optical line-of-sight, that is,

there are obstructions between the antennas.

OFDM technology can often use multi-pathing to an advantage to overcome nLOS, especially in

cases where the Fresnel zone is only partially blocked by buildings, “urban canyons”, or foliage.

OFDM tends to help especially when obstacles are near the middle of the link, and less so when

the obstacles are very near the ODU.

However, attenuation through walls and trees is substantial for any use of the 5.4 GHz and 5.8 GHz

frequency bands. The lower frequency radio waves of 900 MHz radios provide greater penetration

through walls, trees and other obstacles, making it optimal for most non-line-of-sight applications.

Even with OFDM, these products are not expected to penetrate walls or extensive trees and

foliage.

Path loss

Path loss is the amount of attenuation the radio signal undergoes between the two ends of the

link. The path loss is the sum of the attenuation of the path if there were no obstacles in the way

(Free Space Path Loss), the attenuation caused by obstacles (Excess Path Loss) and a margin to

allow for possible fading of the radio signal (Fade Margin). The following calculation needs to be

performed to judge whether a link can be installed:

capabilityseasonalfadeexcessspace

free

LLLLL <+

Where: Is:

spacefree

Free Space Path Loss (dB)

excess

Excess Path Loss (dB)

fade

Fade Margin Required (dB)

Chapter 3: System planning Link planning

Page 3-28

seasonal

Seasonal Fading (dB)

capability

Equipment Capability (dB)

Calculating Link Loss

The link loss is the total attenuation of the wireless signal between two point-to-multipoint units.

The link loss calculation is presented below:

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

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

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

(dBi)

Calculating Rx Signal Level

The determinants in Rx signal level are illustrated in Figure 54.

Figure 54 Determinants in Rx signal level

Rx signal level is calculated as follows:

Rx signal level dB = Tx power − Tx cable loss + Tx antenna gain

− free space path loss + Rx antenna gain − Rx cable loss

Note

This Rx signal level calculation presumes that a clear line of sight is established

between the transmitter and receiver and that no objects encroach in the Fresnel zone.

Chapter 3: System planning Link planning

Page 3-29

Calculating Fade Margin

Free space path loss is a major determinant in Rx (received) signal level. Rx signal level, in turn, is

a major factor in the system operating margin (fade margin), which is calculated as follows:

System operating margin (fade margin) dB = Rx signal level dB − Rx sensitivity dB

Thus, fade margin is the difference between strength of the received signal and the strength that

the receiver requires for maintaining a reliable link. A higher fade margin is characteristic of a

more reliable link.

Adaptive modulation

Adaptive modulation ensures that the highest throughput that can be achieved instantaneously

will be obtained, taking account of propagation and interference. When the link has been installed,

web pages provide information about the link loss currently measured by the equipment, both

instantaneously and averaged. The averaged value will require maximum seasonal fading to be

added, and then the radio reliability of the link can be computed.

For details of the system throughput, link loss and maximum distance for each frequency band in

all modulation modes, see Link on page 10-45.

Chapter 3: System planning Planning for connectorized units

Page 3-30

Planning for connectorized units

This section describes factors to be considered when planning to use connectorized ODUs with

external antennas in 450 Platform Family links.

When to install connectorized units

Most of radio links can be successfully deployed with the integrated ODU. However, the integrated

units may not be sufficient in some areas, for example:

• Where the path is heavily obscured by dense woodland on an NLOS link.

• Where long LOS links are required.

• Where there are known to be high levels of interference.

In these areas, connectorized ODUs and external antennas should be used.

Choosing external antennas

When selecting external antennas, consider the following factors:

• The required antenna gain.

• Ease of mounting and alignment.

• Use dual-polarization antenna (as the integrated antenna).

Note

Enter the antenna gain and cable loss into the Installation Wizard, if the country

selected has an EIRP limit, the corresponding maximum transmit power will be

calculated automatically by the unit.

Calculating RF cable length (5.8 GHz FCC only)

The 5.8 GHz band FCC approval for the product is based on tests with a cable loss between the

ODU and antenna of not less than 1.2 dB. If cable loss is below 1.2 dB with a 1.3 m (4 ft) diameter

external antenna, the connectorized 450 Platform Family may exceed the maximum radiated

spurious emissions allowed under FCC 5.8 GHz rules.

Cable loss depends mainly upon cable type and length. To meet or exceed the minimum loss of

1.2 dB, use cables of the type and length specified in Table 78 (source: Times Microwave). This

data excludes connector losses.

Chapter 3: System planning Planning for connectorized units

Page 3-31

Table 78 RF cable lengths required to achieve 1.2 dB loss at 5.8 GHz

RF cable type

Minimum cable length

LMR100 0.6 m (1.9 ft)

LMR200 1.4 m (4.6 ft)

LMR300 2.2 m (7.3 ft)

LMR400 3.4 m (11.1 ft)

LMR600 5.0 m (16.5 ft)

Chapter 3: System planning Data network planning

Page 3-32

Data network planning

This section describes factors to be considered when planning 450 Platform Family data networks.

Understanding addresses

A basic understanding of Internet Protocol (IP) address and subnet mask concepts is required for

engineering your IP network.

IP address

The IP address is a 32-bit binary number that has four parts (octets). This set of four octets has two

segments, depending on the class of IP address. The first segment identifies the network. The

second identifies the hosts or devices on the network. The subnet mask marks a boundary

between these two sub-addresses.

Dynamic or static addressing

For any computer to communicate with a module, the computer must be configured to either

• use DHCP (Dynamic Host Configuration Protocol). In this case, when not connected to the

network, the computer derives an IP address on the 169.254 network within two minutes.

• have an assigned static IP address (for example, 169.254.1.5) on the 169.254 network.

Note

If an IP address that is set in the module is not the 169.254.x.x network address, then

the network operator must assign the computer a static IP address in the same subnet.

When a DHCP server is not found

To operate on a network, a computer requires an IP address, a subnet mask, and possibly a

gateway address. Either a DHCP server automatically assigns this configuration information to a

computer on a network or an operator must input these items.

When a computer is brought on line and a DHCP server is not accessible (such as when the server

is down or the computer is not plugged into the network), Microsoft and Apple operating systems

default to an IP address of 169.254.x.x and a subnet mask of 255.255.0.0 (169.254/16, where /16

indicates that the first 16 bits of the address range are identical among all members of the subnet).

Chapter 3: System planning Data network planning

Page 3-33

DNS Client

The DNS Client is used to resolve names of management servers within the operator’s

management domain (see Figure 55). This feature allows hostname configuration for NTP servers,

Authorization Servers, DHCP relay servers, and SNMP trap servers. Operators may choose to

either enter in the FQDN (Fully Qualified Domain Name) for the host name or to manually enter the

IP addresses of the servers.

Figure 55 Cambium networks management domain

Network Address Translation (NAT)

NAT, DHCP Server, DHCP Client and DMZ in SM

The system provides NAT (network address translation) for SMs in the following combinations of

NAT and DHCP (Dynamic Host Configuration Protocol):

• NAT Disabled

• NAT with DHCP Client (DHCP selected as the Connection Type of the WAN interface) and DHCP

Server

• NAT with DHCP Client (DHCP selected as the Connection Type of the WAN interface)

• NAT with DHCP Server

• NAT without DHCP

NAT

NAT isolates devices connected to the Ethernet/wired side of a SM from being seen directly from

the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic

(separate from its address for management), terminates transport traffic, and allows you to assign

a range of IP addresses to devices that are connected to the Ethernet/wired side of the SM.

Chapter 3: System planning Data network planning

Page 3-34

In the Cambium system, NAT supports many protocols, including HTTP, ICMP (Internet Control

Message Protocols), and FTP (File Transfer Protocol). For virtual private network (VPN)

implementation, L2TP over IPSec (Level 2 Tunneling Protocol over IP Security) and PPTP (Point to

Point Tunneling Protocol) are supported.

DHCP

DHCP enables a device to be assigned a new IP address and TCP/IP parameters, including a default

gateway, whenever the device reboots. Thus DHCP reduces configuration time, conserves IP

addresses, and allows modules to be moved to a different network within the Cambium system.

In conjunction with the NAT features, each SM provides:

• A DHCP server that assigns IP addresses to computers connected to the SM by Ethernet

protocol.

• A DHCP client that receives an IP address for the SM from a network DHCP server.

DMZ

In conjunction with the NAT features, a DMZ (demilitarized zone) allows the assignment of one IP

address behind the SM for a device to logically exist outside the firewall and receive network

traffic. The first three octets of this IP address must be identical to the first three octets of the NAT

private IP address.

Developing an IP addressing scheme

Network elements are accessed through IP Version 4 (IPv4) addressing.

A proper IP addressing method is critical to the operation and security of a network.

Each module requires an IP address on the network. This IP address is for only management

purposes. For security, you must either:

• Assign a non-routable IP address.

• Assign a routable IP address only if a firewall is present to protect the module.

You assign an IP addresses to computers and network components by either static or dynamic IP

addressing. You will also assign the appropriate subnet mask and network gateway to each

module.

Address Resolution Protocol

As previously stated, the MAC address identifies a module in:

• Communications between modules.

• The data that modules store about each other.

Chapter 3: System planning Data network planning

Page 3-35

The IP address is essential for data delivery through a router interface. Address Resolution

Protocol (ARP) correlates MAC addresses to IP addresses.

For communications to outside the network segment, ARP reads the network gateway address of

the router and translates it into the MAC address of the router. Then the communication is sent to

MAC address (physical network interface card) of the router.

For each router between the sending module and the destination, this sequence applies. The ARP

correlation is stored until the ARP cache times out.

Allocating subnets

The subnet mask is a 32-bit binary number that filters the IP address. Where a subnet mask

contains a bit set to 1, the corresponding bit in the IP address is part of the network address.

Example IP address and subnet mask

In Figure 56, the first 16 bits of the 32-bit IP address identify the network:

Figure 56 Example of IP address in Class B subnet

Octet 1

Octet 2

Octet 3

Octet 4

IP address 169.254.1.1 10101001 11111110 00000001 00000001

Subnet mask 255.255.0.0 11111111 11111111 00000000 00000000

In this example, the network address is 169.254 and 216 (65,536) hosts are addressable.

Selecting non-routable IP addresses

The factory default assignments for network elements are:

• Unique MAC address

• IP address of 169.254.1.1

• Subnet mask of 255.255.0.0

• Network gateway address of 169.254.0.0

For each radio and CMM4, assign an IP address that is both consistent with the IP addressing plan

for your network and cannot be accessed from the Internet. IP addresses within the following

ranges are not routable from the Internet, regardless of whether a firewall is configured:

• 10.0.0.0 – 10.255.255.255

• 172.16.0.0 – 172.31.255.255

• 192.168.0.0 – 192.168.255.255

Also, the subnet mask and network gateway for each CMM4 can be assigned.

Chapter 3: System planning Data network planning

Page 3-36

Translation bridging

Optionally, the AP can be configured to change the source MAC address in every packet it receives

from its SMs to the MAC address of the SM/BHS that bridged the packet, before forwarding the

packet toward the public network. In this case:

• Not more than 128 IP devices at any time are valid to send data to the AP from behind the SM.

• SM populates the Translation Table tab of its Statistics web page, displaying the MAC address

and IP address of all the valid connected devices.

• Each entry in the Translation Table is associated with the number of minutes that have elapsed

since the last packet transfer between the connected device and the SM.

• If 128 are connected, and another attempt to connect:

o If no Translation Table entry is older than 255 minutes, the attempt is ignored.

o If an entry is older than 255 minutes, the oldest entry is removed and the attempt is

successful.

• The Send Untranslated ARP parameter in the General tab of the Configuration page can be:

o Disabled, so that the AP overwrites the MAC address in ARP packets before forwarding

them.

o Enabled, so that the AP forwards ARP packets regardless of whether it has overwritten the

MAC address.

This is the Translation Bridging feature, which you can enable in the General page of the

Configuration web page in the AP. When this feature is disabled, the setting of the

Send Untranslated ARP parameter has no effect, because all packets are forwarded untranslated

(with the source MAC address intact). See Address Resolution Protocol on Page 3-34.

Engineering VLANs

The radios support VLAN functionality as defined in the 802.1Q (Virtual LANs) specification, except

for the following aspects of that specification:

• Protocols:

o Generic Attribute Registration Protocol (GARP) GARV

o Spanning Tree Protocol (STP)

o Multiple Spanning Tree Protocol (MSTP)

o GARP Multicast Registration Protocol (GMRP)

• Embedded source routing (ERIF) in the 802.1Q header

• Multicast pruning

• Flooding unknown unicast frames in the downlink

As an additional exception, the AP/BHM does not flood downward the unknown unicast frames to

the SM/BHS.

A VLAN configuration in Layer 2 establishes a logical group within the network. Each computer in

the VLAN, regardless of initial or eventual physical location, has access to the same data. For the

network operator, this provides flexibility in network segmentation, simpler management, and

enhanced security.

Chapter 3: System planning Data network planning

Page 3-37

Special case VLAN numbers

This system handles special case VLAN numbers according to IEEE specifications:

Table 79 Special case VLAN IDs

VLAN Number

Purpose

Usage Constraint

0 These packets have 802.1p priority, but are

otherwise handled as untagged.

Must not be used as a

management VLAN.

Although not noted as special case by IEEE

specifications, these packets identify traffic

that was untagged upon ingress into the SM

and must remain untagged upon egress.

This policy is hard-coded in the AP.

Must not be used for

system VLAN traffic.

4095 This VLAN is reserved for internal use. Must not be used at all.

SM membership in VLANs

With the supported VLAN functionality, the radios determine bridge forwarding on the basis of not

only the destination MAC address, but also the VLAN ID of the destination. This provides flexibility

in how SMs are used:

• Each SM can be a member in its own VLAN.

• Each SM can be in its own broadcast domain, such that only the radios that are members of

the VLAN can see broadcast and multicast traffic to and from the SM.

• The network operator can define a work group of SMs, regardless of the AP(s) to which they

Chapter 3: System planning Data network planning

Page 3-38

PMP 450 Platform Family modules provide the VLAN frame filters that are described in Table 80.

Table 80 VLAN filters in point-to-multipoint modules

Where VLAN is active,

if this parameter value

is selected …

then a frame is discarded if…

because of this VLAN

filter in the software:

entering the bridge/

NAT switch through…

Ethernet…

TCP/IP…

any combination of

VLAN

parameter settings

with a VID not in the

membership table Ingress

any combination of

VLAN

parameter settings

with a VID not in

the

membership table

Local Ingress

Allow Frame Types:

Tagged Frames Only

with no 802.1Q tag Only Tagged

Allow Frame Types:

Untagged Frames Only

with an 802.1Q tag,

regardless of VID Only Untagged

Local SM Management:

Disable

in the SM, or

All Local SM

Management:

Disable

in the AP

with an 802.1Q tag

and a VID in the

membership table

Local SM Management

leaving the bridge/

NAT switch through…

Ethernet…

TCP/IP…

any combination of

VLAN

parameter settings

with a VID not in the

membership table Egress

any combination of

VLAN

parameter settings

with a VID not in

the

membership table

Local Egress

Priority on VLANs (802.1p)

The radios can prioritize traffic based on the eight priorities described in the IEEE 802.1p

specification. When the high-priority channel is enabled on a SM, regardless of whether VLAN is

enabled on the AP for the sector, packets received with a priority of 4 through 7 in the 802.1p field

are forwarded onto the high-priority channel.

Chapter 3: System planning Data network planning

Page 3-39

Operators may configure priority precedence as 802.1p Then Diffserv (Default) or Diffserv Then

802.1p. Since these priority precedence configurations are independent between the AP and SM,

this setting must be configured on both the AP and SM to ensure that the precedence is adhered to

by both sides of the link.

VLAN settings can also cause the module to convert received non-VLAN packets into VLAN

packets. In this case, the 802.1p priority in packets leaving the module is set to the priority

established by the DiffServ configuration.

If VLAN is enabled, immediately monitor traffic to ensure that the results are as desired. For

example, high-priority traffic may block low-priority.

Q-in-Q DVLAN (Double-VLAN) Tagging (802.1ad)

PMP and PTP modules can be configured with 802.1ad Q-in-Q DVLAN (Double-VLAN) tagging

which is a way for an operator to put an 802.1Q VLAN inside of an 802.1ad VLAN. A nested VLAN,

which is the original 802.1Q tag and a new second 802.1ad tag, allows for bridging of VLAN traffic

across a network and segregates the broadcast domains of 802.1Q VLANs. Q-in-Q can be used

with PPPoE and/or NAT.

The 802.1ad standard defines the S-VLAN as the Service Provider VLAN and the C-VLAN as the

customer VLAN. The radio software does 2-layer Q-in-Q whereby the C-VLAN is the 802.1Q tag and

the S-VLAN is the second layer Q tag as shown in Table 81.

Table 81 Q-in-Q Ethernet frame

Ethernet Header S-VLAN EthType

0x88a8

C-VLAN EthType

0x8100 IP Data EthType 0x0800

The 802.1ad S-VLAN is the outer VLAN that is configurable on the Configuration > VLAN web page

of the AP/BHM. The Q-in-Q EtherType parameter is configured with a default EtherType of 0x88a8

in addition to four alternate EtherTypes that can be configured to aid in interoperability with

existing networks that use a different EtherType than the default.

The C-VLAN is the inner VLAN tag, which is the same as 802.1Q. As a top-level concept, this

operates on the outermost tag at any given time, either “pushing” a tag on or “popping” a tag off.

This means packets will at most transition from an 802.1Q frame to an 801.ad frame (with a tag

“pushed” on) or an untagged 802.1 frame (with the tag “popped” off. Similarly, for an 802.1ad

frame, this can only transition from an 802.1ad frame to an 802.1Q frame (with the tag “popped”

off) since the radio software only supports 2 levels of tags.

Chapter 3: System planning Network management planning

Page 3-40

Network management planning

This section describes how to plan for 450 Platform Family links to be managed remotely using

SNMP.

Planning for SNMP operation

Cambium modules provide the following SNMP traps for automatic notifications to the NMS:

• coldStart, which signals that the SNMPv2c element is reinitializing itself and that its

configuration may have been altered.

• warmStart, which signals that the SNMPv2c element is reinitializing such that its configuration

is unaltered.

• authenticationFailure, which signals that the SNMPv2c element has received a protocol

message that is not properly authenticated (contingent on the snmpEnableAuthenTraps object

setting).

• linkDown, as defined in RFC 1573

• linkUp, as defined in RFC 1573

• egpNeighborLoss, as defined in RFC 1213

• whispGPSInSync, which signals a transition from not synchronized to synchronized.

• whispGPSOutSync, which signals a transition from synchronized to not synchronized.

• whispRegComplete, which signals registration completed.

• whispRegLost, which signals registration lost.

• whispRadarDetected, which signals that the one-minute scan has been completed, radar has

been detected and the radio will shut down.

• whispRadarEnd, which signals that the one-minute scan has been completed, radar has not

been detected and the radio will resume normal operation.

Note

The proprietary MIBs are provided in the 450 Platform Family software download files

in the support website (see Contacting Cambium Networks on page 1).

Enabling SNMP

Enable the SNMP interface for use by configuring the following attributes in the SNMP

Configuration page:

• SNMP State (default disabled)

• SNMP Version (default SNMPv2c)

• SNMP Port Number (default 161)

Chapter 3: System planning Security planning

Page 3-41

Security planning

This section describes how to plan for 450 Platform Family links to operate in secure mode.

• Managing module access by passwords

• Filtering protocols and ports

• Port Configuration

Isolating AP/BHM from the Internet

Ensure that the IP addresses of the AP/BHM in the network:

• are not routable over the Internet.

• do not share the subnet of the IP address of your user.

RFC 1918, Address Allocation for Private Subnets, reserves for private IP networks three blocks of

IP addresses that are not routable over the Internet:

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

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

• /24 subnets have 256 reserved networks, 192.168.0.0 to 192.168.255.255.

Encrypting radio transmissions

Cambium fixed wireless broadband IP systems employ the following form of encryption for

security of the wireless link:

• DES (Data Encryption Standard): An over-the-air link encryption option that uses secret 56-bit

keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and

recombination operations on blocks of data. DES encryption does not affect the performance

or throughput of the system.

• AES (Advanced Encryption Standard): An over-the-air link encryption option that uses the

Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. AES

products are certified as compliant with the Federal Information Processing Standards (FIPS

197) in the U.S.A.

The default encryption setting for 450 Platform Family ODU is "None".

Chapter 3: System planning Security planning

Page 3-42

Planning for HTTPS operation

Before starting to configure HTTPS operation, ensure that the cryptographic material listed in

Table 82 is available.

Table 82 HTTPS security material

Item

Description

Quantity required

User Defined Security

Banner

The banner provides warnings and notices

to be read by the user before logging in to

the ODU. Use text that is appropriate to

the network security policy.

Normally one per link.

This depends upon

network policy.

Port numbers for HTTP,

HTTPS and Telnet

Port numbers allocated by the network. As allocated by

network.

Planning for SNMPv3 operation

SNMP security mode

Decide how SNMPv3 security will be configured.

MIB-based security management uses standard SNMPv3 MIBs to configure the user-based

security model and the view-based access control model. This approach provides considerable

flexibility, allowing a network operator to tailor views and security levels appropriate for different

types of user. MIB-based security management may allow a network operator to take advantage of

built-in security management capabilities of existing network managers.

Web-based security management allows an operator to configure users, security levels, privacy

and authentication protocols, and passphrases using the 450 Platform Family web-based

management interface. The capabilities supported are somewhat less flexible than those

supported using the MIB-based security management, but will be sufficient in many applications.

Selection of web-based management for SNMPv3 security disables the MIB-based security

management. 450 Platform Family does not support concurrent use of MIB-based and web-based

management of SNMPv3 security.

Web-based management of SNMPv3 security

Initial configuration of SNMPv3 security is available only to HTTP or HTTPS user accounts with

security role of Security Officer.

Identify the format used for SNMP Engine ID. The following formats are available:

• MAC address (default)

• 5 and 32 hex characters (the hex character input is driven by RFC 3411 recommendations on

the Engine ID)

Chapter 3: System planning Security planning

Page 3-43

Identify the user names and security roles of initial SNMPv3 users. Two security roles are

available:

• Read Only

• System Administrator

Identify the security level for each of the security roles. Three security levels are available:

(a) No authentication, no privacy

(b) Authentication, no privacy

If authentication is required, identify the protocol. The authentication protocol available is MD5.

If privacy will be used, identify the protocol. The privacy protocol available is cbc-des.

Managing module access by passwords

From the factory, each module has a preconfigured administrator-level account in the name root,

which initially requires no associated password. When you upgrade a module:

• An account is created in the name admin.

• Both admin and root inherit the password that was previously used to access the module, if:

o Full Access password, if one was set.

o Display-Only Access password, if one was set and no Full Access password was set.

Caution

If you use Wireless Manager, do not delete the root account from any module. If you

use a NMS that communicates with modules through SNMP, do not delete the root

account from any module unless you first can confirm that the NMS does not rely on

the root account for access to the modules.

Each module supports four or fewer user accounts, regardless of account levels. The available

levels are

• ADMINISTRATOR, who has full read and write permissions. This is the level of the root and

admin users, as well as any other administrator accounts that one of them creates.

• INSTALLER, who has permissions identical to those of ADMINISTRATOR except that the

installer cannot add or delete users or change the password of any other user.

• TECHNICIAN, who has permissions to modify basic radio parameters and view informational

web pages.

• GUEST, who has no write permissions and only a limited view of General Status tab.

• Admin, Installer and Tech accounts can be configured as READ-ONLY. This will allow the

account to only see the items.

The ability to view information of General Status tab can be controlled by the "Site Information

Viewable to Guest Users" under the SNMP tab.

Chapter 3: System planning Security planning

Page 3-44

From the factory default state, configure passwords for both the root and admin account at the

ADMINISTRATOR permission level, using the Account > Change Users Password page. (If

configure only one of these, then the other will still require no password for access into it and thus

remain a security risk.) If you are intent on configuring only one of them, delete the admin account.

The root account is the only account that CNUT uses to update the module.

After a password has been set for any ADMINISTRATOR-level account, initial access to the module

GUI opens the view of GUEST level.

Planning for RADIUS operation

Configure RADIUS where remote authentication is required for users of the web-based interface.

Remote authentication has the following advantages:

• Control of passwords can be centralized.

• Management of user accounts can be more sophisticated. For example; users can be prompted

by a network manager to change passwords at regular intervals. As another example,

passwords can be checked for inclusion of dictionary words and phrases.

• Passwords can be updated without reconfiguring multiple network elements.

• User accounts can be disabled without reconfiguring multiple network elements.

Remote authentication has one significant disadvantage in a wireless link product such as 450

Platform Family. If the wireless link is down, a unit on the remote side of the broken link may be

prevented from contacting a RADIUS Server, with the result that users are unable to access the

web-based interface.

One useful strategy would be to combine RADIUS authentication for normal operation with a

single locally-authenticated user account for emergency use.

PMP 450 Platform Family SM provides a choice of the following authentication methods:

• Phase 1:

o EAP-MSCHAPv2

o EAP-TTLS

o EAP PEAP

• Phase 2:

o PAP

o CHAP

o MSCHAPv2

Ensure that the authentication method selected in 450 Platform Family is supported by the RADIUS

server.

Filtering protocols and ports

Configure filters for specified protocols and ports from leaving the AP/BHM and SM/BHS and

entering the network. This protects the network from both intended and inadvertent packet loading

or probing by network users. By keeping the specified protocols or ports off the network, this

feature also provides a level of protection to users from each other.

Chapter 3: System planning Security planning

Page 3-45

Protocol and port filtering is set per AP/SM/BH. Except for filtering of SNMP ports, filtering occurs

as packets leave the AP/SM/BH.

For example, if SM is configured to filter SNMP, then SNMP packets are blocked from entering the

SM and, thereby, from interacting with the SNMP portion of the protocol stack on the SM.

Port Filtering with NAT Enabled

Where NAT is enabled on the SM/BHS, the filtering can be enabled for only the user-defined ports.

The following are examples for situations where the configure port can be filtered where NAT is

enabled:

• To block a subscriber from using FTP, you can filter Ports 20 and 21 (the FTP ports) for both the

TCP and UDP protocols.

• To block a subscriber from access to SNMP, you can filter Ports 161 and 162 (the SNMP ports)

for both the TCP and UDP protocols.

Note

In only the SNMP case, filtering occurs before the packet interacts with the protocol

stack.

Protocol and Port Filtering with NAT Disabled

Where NAT is disabled on the SM/BHS, the filtering can be enabled for both protocols and the

three user-defined ports. Using the check boxes on the interface, it can be either:

• Allow all protocols except those that user wish to block.

• Block all protocols except those that user wish to allow.

Allow or block any of the following protocols:

• PPPoE (Point to Point Protocol over Ethernet)

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

o SMB (Network Neighborhood)

o SNMP

o Bootp Client

o Bootp Server

o Up to 3 user-defined ports

o All other IPv4 traffic (see Figure 29)

• Any or all of the following IPv6 (Internet Protocol version 6) protocols:

o SMB (Network Neighborhood)

o SNMP

o Bootp Client

o Bootp Server

o Up to 3 user-defined ports

Chapter 3: System planning Security planning

Page 3-46

o All other IPv6 traffic (see Figure 29)

• Filter Direction – Upstream and Downstream

• ARP (Address Resolution Protocol)

Figure 57 Categorical protocol filtering

The following are example situations in which the protocol filtering is configured where NAT is

disabled:

• If a subscriber is blocked from only PPPoE and SNMP, then the subscriber retains access to all

other protocols and all ports.

• If PPPoE, IPv4, and Uplink Broadcast are blocked, and check the All others selection, then only

Address Resolution Protocol is not filtered.

The ports filtered because of protocol selections in the Protocol Filtering tab of the SM/BHS are

listed in Table 83.

BootP

Client

BootP

Server

SNMP

IPv4

Multica

User

Defined

Port 1

SMB

User

Defined

Port 3

User

Defined

Port 2

PPPoE ARP

All

Others

All

Other

IPv4

Chapter 3: System planning Security planning

Page 3-47

Table 83 Ports filtered per protocol selections

Port Configuration

450 Platform Family supports access to various communication protocols and only the ports

required for these protocols are available for access by external entities. Operators may change

the port numbers for these protocols via the radio GUI or SNMP.

Table 84 Device default port numbers

Port

Usage

Port Usage

Device

21 FTP Listen Port AP, SM

80 HTTP Listen Port AP, SM

443 HTTPS Listen Port AP, SM

161 SNMP port Listen Port AP, SM

162 SNMP trap port Destination Port AP, SM

514 Syslog Server port Destination Port AP, SM

1812 Standard RADIUS port Destination Port AP

1813 Standard RADIUS accounting port Destination Port AP, SM

Protocol Selected

Port Filtered (Blocked)

SMB Destination Ports UDP: 137, 138, 139, 445, 3702 and 1900

Destination Ports TCP: 137, 138, 139, 445, 2869, 5357 and 5358

SNMP Destination Ports TCP and UDP: 161 and 162

Bootp Client Source Port 68 UDP

Bootp Server Source Port 67 UDP

User Defined Port 1..3 User defined ports for filtering UDP and TCP

IPv4 Multicast Block IPv4 packet types except other filters defined

IPv6 Multicast Block IPv6 packet types except other filters defined

ARP Filter all Ethernet packet type 806

Upstream Applies packet filtering to traffic coming into the FEC interface

Downstream Applies packet filtering to traffic destined to exit the FEC

interface

Chapter 3: System planning Security planning

Page 3-48

Encrypting downlink broadcasts

An AP can be enabled to encrypt downlink broadcast packets such as the following:

• ARP

• NetBIOS

• broadcast packets containing video data on UDP.

The encryption used is DES for a DES-configured module and AES for an AES-configured module.

Before the Encrypt Downlink Broadcast feature is enabled on the AP, air link security must be

enabled on the AP.

Isolating SMs in PMP

In an AP, SMs in the sector can be prevented from directly communicating with each other. In

CMM4, the connected APs can be prevented from directly communicating with each other, which

prevents SMs that are in different sectors of a cluster from communicating with each other.

In the AP, the SM Isolation parameter is available in the General tab of the Configuration web

page. Configure the SM Isolation feature by any of the following selections from drop-down menu:

• Disable SM Isolation (the default selection). This allows full communication between SMs.

• Enable Option 1 - Block SM destined packets from being forwarded. This prevents both

multicast/broadcast and unicast SM-to-SM communication.

• Enable Option 2 - Forward SM destined packets upstream. This not only prevents

multicast/broadcast and unicast SM-to-SM communication but also sends the packets, which

otherwise may have been handled SM to SM, through the Ethernet port of the AP.

In the CMM and the CMM4, SM isolation treatment is the result of how to manage the port-based

VLAN feature of the embedded switch, where all traffic can be switched from any AP to a specified

uplink port. However, this is not packet level switching. It is not based on VLAN IDs.

Filtering management through Ethernet

Configure the SM to disallow any device that is connected to its Ethernet port from accessing the

IP address of the SM. If the Ethernet Access Control parameter is set to Enabled, then:

• No attempt to access the SM management interface (by http, SNMP, ftp, or tftp) through

Ethernet is granted.

• Any attempt to access the SM management interface over the air (by IP address, presuming

that LAN1 Network Interface Configuration, Network Accessibility is set to Public, or by link

from the Session Status or Remote Subscribers tab in the AP) is unaffected.

Chapter 3: System planning Security planning

Page 3-49

Allowing management from only specified IP addresses

The Security sub-menu of the Configuration web page in the AP/BHM and SM/BHS includes the IP

Access Control parameter. Specify one, two, or three IP addresses that must be allowed to access

the management interface (by HTTP, SNMP, FTP or TFTP).

If the selection is:

• IP Access Filtering Disabled, then management access is allowed from any IP address, even if

the Allowed Source IP 1 to 3 parameters are populated.

• IP Access Filtering Enabled, and specify at least one address in the Allowed Source IP 1 to 3

parameter, then management access is limited to the specified address(es).

Configuring management IP by DHCP

The Configuration > IP web page of every radio contains a LAN1 Network Interface Configuration,

DHCP State parameter that, if enabled, causes the IP configuration (IP address, subnet mask, and

gateway IP address) to be obtained through DHCP instead of the values of those individual

parameters. The setting of this DHCP state parameter is also viewable, but is not settable, in the

Network Interface tab of the Home page.

In the SM/BHS, this parameter is settable

• in the NAT tab of the Configuration web page, but only if NAT is enabled.

• in the IP tab of the Configuration web page, but only if the Network Accessibility parameter in

the IP tab is set to Public.

DHCP option 81

The DHCP server can be used to register and update the pointer (PTR) and host (A) DNS resource

records on behalf of its DHCP-enabled clients.

The DHCP option 81 permits the client to provide its fully qualified domain name (FQDN) as well as

instructions to the DHCP server on how it would like the server to process DNS dynamic updates

(if any) on its behalf. The hostname is populated as SiteName.DomainName depending upon

following conditions:

• If Sitename is default i.e. No Site Name, mac address will be used instead.

• The SiteName should only be a-z | A-Z | 0-9 and period(.) and dash (-).

• The domain name part should not start or end with dash (-).

• The underscore or space in domain name part will be converted to dash (-), anything else apart

from valid characters will be skipped.

Chapter 3: System planning Security planning

Page 3-50

Controlling PPPoE PADI Downlink Forwarding

The AP supports the control of forwarding of PPPoE PADI (PPPoE Active Discovery Initiation)

packets. This forwarding is configured on the AP GUI Configuration > Radio page by parameter

PPPoE PADI Downlink Forwarding. When set to “Enabled”, the AP allows downstream and

upstream transmission of PPPoE PADI packets. When set to “Disabled”, the AP does NOT allow

PPPoE PADI packets to be sent out of the AP RF interface (downstream) but will allow PPPoE PADI

packets to enter the RF interface (upstream) and exit the Ethernet interface.

Chapter 3: System planning Remote AP Deployment

Page 3-51

Remote AP Deployment

In cases where the subscriber population is widely distributed, or conditions such as geography

restrict network deployment, you can add a Remote AP to:

• provide high-throughput service to near LoS business subscribers.

• reach around obstructions or penetrate foliage with non-LoS throughput.

• reach new, especially widely distributed, residential subscribers with broadband service.

• pass sync to an additional RF hop.

In the remote AP configuration, a remote AP is co-located with an SM. The remote AP distributes

the signal to SMs that are logically behind the co-located SM. A remote AP deployment is

illustrated in Figure 58.

Figure 58 Remote AP deployment

The co-located SM receives data in one channel, and the remote AP must redistribute the data in a

different channel. The two channels need to have a frequency gap equal to at least two times the

used channel bandwidth.

Base your selection of frequency band ranges on regulatory restrictions, environmental conditions,

and throughput requirements.

Note

Each relay hop (additional daisy-chained remote AP) adds approximately 5-7 msec

round trip latency.

Chapter 3: System planning Remote AP Deployment

Page 3-52

Remote AP (RAP) Performance

The performance of a remote AP is identical to the AP performance in cluster. Throughputs,

ranges, and antenna coverage are identical.

As with all equipment operating in the unlicensed spectrum, Cambium strongly recommends that

you perform site surveys before you add network elements. These will indicate that spectrum is

available in the area where you want to grow. Keep in mind that:

• non-LoS ranges heavily depend on environmental conditions.

• in most regions, not all frequencies are available.

• your deployments must be consistent with local regulatory restrictions.

Example Use Case for RF Obstructions

A remote AP can be used to provide last-mile access to a community where RF obstructions

prevent SMs from communicating with the higher-level AP in cluster. For example, you may be

able to use 900 MHz for the last mile between a remote AP and the outlying SMs where these

subscribers cannot form good links to a higher-level 5 GHz AP. In this case, the ability of the 900-

MHz wavelength to be effective around foliage at short range solves the foliage penetration

problem.

An example of this use case is shown in Figure 59.

In this example, the 5 GHz AP is a PMP 450i AP in the 5.8 GHz band operating on a 20 MHz channel

with a 2.5 ms frame; the SMs are 5 GHz PMP 450 integrated SMs. The SM connected to the remote

AP is a PMP 450i SM.

The remote AP is a PMP 450i AP in the 900 MHz band, also operating in a 20 MHz channel with a

2.5 ms frame; the SMs are 900 MHz PMP 450 connectorized SMs using the Cambium 23 dBi gain

antenna.

Chapter 3: System planning Remote AP Deployment

Page 3-53

Figure 59 Example for 900-MHz remote AP behind 5 GHz SM

The 5 GHz modules provide a sustained aggregate throughput of up to 126 Mbps to the sector.

One of the SMs in the sector is wired to a 900-MHz remote AP, which provides NLoS sustained

aggregate throughput2 of:

• 126 Mbps to 900-MHz SMs up to 4 miles away in the sector.

• 94 Mbps to 900-MHz SMs between 4 and 10 miles away in the sector.

Example Use Case for Passing Sync

All radios support the remote AP functionality. The BHS and the SM can reliably pass the sync

pulse, and the BHM and AP can reliably receive it.

However, not all devices are compatible with all other devices. The following table shows which

SMs can be connected to which APs.

Devices

PMP 450 AP/BHM PMP 450i AP/BHM PMP 450m AP

PMP 450 SM/BHS X

PMP 450i SM/BHS X X

2 NLoS ranges depend on environmental conditions. Your results may vary from these.

Chapter 3: System planning Remote AP Deployment

Page 3-54

Examples of passing sync over cable are shown under Passing Sync in an Additional Hop on page

3-56.

For PMP 450, the sync is passed in a cable that connects Pins 1 and 6 of the RJ-11 timing ports of

the two modules.

For PMP 450i/450m the sync is passed in a cable that connects Pins7 and 8 of the RJ-45 timing

ports of the two modules.

When connecting modules in this way, make sure the AP and SM are properly configured, as

described in the Wiring to Extend Network Sync.

Physical Connections Involving the Remote AP

The SM to which a remote AP is connected to can be either an SM that serves a customer or an

SM that simply serves as a relay. If the SM serves a customer, wire the remote AP to the SM as

shown in Figure 60.

Figure 60 Remote AP wired to SM that also serves a customer

If the SM simply serves as a relay, you must use a straight-through RJ-45 female-to-female coupler

and wire the SM to the remote AP as shown in Figure 61.

Chapter 3: System planning Remote AP Deployment

Page 3-55

Figure 61 Remote AP wired to SM that serves as a relay

Chapter 3: System planning Remote AP Deployment

Page 3-56

Passing Sync signal

Passing Sync in a Single Hop

Network sync can be passed in a single hop in the following network designs:

• Design 1

o A CMM provides sync to a co-located AP.

o This AP sends the sync over the air to SMs.

• Design 2

o A CMM provides sync to a co-located BH timing master.

o This BH timing master sends the sync over the air to a BH timing slave.

Passing Sync in an Additional Hop

Network sync can be extended by one additional link in any of the following network designs:

Note

In each of these following designs, Link 2 is not on the same frequency band as Link 4.

(For example, Link 2 may be a 5.2 GHz link while Link 4 is a 5.7 or 2.4 GHz link.)

• Design 3

o A CMM provides sync to a co-located AP.

o This AP sends the sync over the air to an SM.

o This SM delivers the sync to a co-located AP.

o This AP passes the sync in the additional link over the air to SMs.

This design is illustrated in Figure 62.

Figure 62 Additional link to extend network sync, Design 3

Chapter 3: System planning Remote AP Deployment

Page 3-57

• Design 4

o A CMM provides sync to a co-located AP.

o This AP sends the sync over the air to an SM.

o This SM delivers the sync to a co-located BHM.

o This BHM passes the sync in the additional link over the air to a BHS.

This design is illustrated in Figure 63.

Figure 63 Additional link to extend network sync, Design 4

Chapter 3: System planning Remote AP Deployment

Page 3-58

• Design 5

o A CMM provides sync to a co-located BHM or the BHM generates timing.

o This BHM sends the sync over the air to a BHS.

o This BHS delivers the sync to a co-located AP.

This AP passes the sync in the additional link over the air to SMs.

This design is illustrated in Figure 64.

Figure 64 Additional link to extend network sync, Design 5

Wiring and configuration information for this sync extension is described under Wiring to Extend

Network Sync on page 3-59.

Chapter 3: System planning Remote AP Deployment

Page 3-59

Wiring to Extend Network Sync

The following procedure can be used to extend network sync by one additional hop, as described

under Passing Sync in an Additional Hop on page 3-56. When a co-located module receives sync

over the air, the co-located modules can be wired to pass the sync as follows:

1. Connect the GPS Utility ports of the co-located modules using a sync cable with RJ-11 (for

450) or RJ-45 (for 450i/450m) connectors.

2. Set the Sync Input parameter on the Configuration page of the co-located AP or BH timing

master to AutoSync.

3. Set the Device Type parameter on the Configuration page of the co-located AP or BH

timing master to Remote.

4. Set the Sync Output to Aux Port parameter on the Configuration page of the co-located AP

or BH timing master to Disabled.

5. Set the UGPS Power parameter on the Configuration page of the co-located AP or BH

timing master to Disabled.

6. Set the Frame Timing Pulse Gated parameter on the Configuration page of the co-located

SM or BH timing slave to Enable.

Note

This setting prevents interference if the SM or BH timing slave loses sync.

Figure 65 Co-located AP or BH timing master Sync Setting configuration

Page 4-1

Chapter 4: Legal and regulatory information

This chapter provides end user license agreements and regulatory notifications.

Caution

Intentional or unintentional changes or modifications to the equipment must not be

made unless under the express consent of the party responsible for compliance. Any

such modifications could void the user’s authority to operate the equipment and will

void the manufacturer’s warranty.

Attention

Changements ou modifications Intentionnels ou non de l'équipement ne doivent pas

être entrepris sans l'autorisation de l’organisme responsable de la déclaration de

conformité. Ces modifications ou changements pourraient invalider le droit de

l'utilisateur à utiliser cet appareil et annuleraient la garantie du fabricant.

The following topics are described in this chapter:

• Cambium Networks end user license agreement on page 4-2 contains the Cambium and third-

party license agreements for the 450 Platform Family ODUs.

• Compliance with safety standards on page 4-22 lists the safety specifications against which the

450 Platform Family has been tested and certified. It also describes how to keep RF exposure

within safe limits.

• Compliance with radio regulations on page 4-33 describes how the 450 Platform Family

complies with the radio regulations that are in force in various countries, and contains

notifications made to regulatory bodies for the 450 Platform Family.

Chapter 4: Legal and regulatory information Cambium Networks end user license agreement

Page 4-2

Cambium Networks end user license agreement

Definitions

In this Agreement, the word “Software” refers to the set of instructions for computers, in

executable form and in any media, (which may include diskette, CD-ROM, downloadable internet,

hardware, or firmware) licensed to you. The word “Documentation” refers to electronic or printed

manuals and accompanying instructional aids licensed to you. The word “Product” refers to

Cambium Networks’ fixed wireless broadband devices for which the Software and Documentation

is licensed for use.

Acceptance of this agreement

In connection with Cambium Networks’ delivery of certain proprietary software or products

containing embedded or pre-loaded proprietary software, or both, Cambium Networks is willing to

license this certain proprietary software and the accompanying documentation to you only on the

condition that you accept all the terms in this End User License Agreement (“Agreement”).

IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, DO NOT USE THE PRODUCT OR

INSTALL THE SOFTWARE. INSTEAD, YOU MAY, FOR A FULL REFUND, RETURN THIS PRODUCT

TO THE LOCATION WHERE YOU ACQUIRED IT OR PROVIDE WRITTEN VERIFICATION OF

DELETION OF ALL COPIES OF THE SOFTWARE. ANY USE OF THE SOFTWARE, INCLUDING BUT

NOT LIMITED TO USE ON THE PRODUCT, WILL CONSTITUTE YOUR ACCEPTANCE TO THE

TERMS OF THIS AGREEMENT.

Grant of license

Cambium Networks Limited (“Cambium”) grants you (“Licensee” or “you”) a personal,

nonexclusive, non-transferable license to use the Software and Documentation subject to the

Conditions of Use set forth in “Conditions of use” and the terms and conditions of this Agreement.

Any terms or conditions relating to the Software and Documentation appearing on the face or

reverse side of any purchase order, purchase order acknowledgment or other order document that

are different from, or in addition to, the terms of this Agreement will not be binding on the parties,

even if payment is accepted.

Chapter 4: Legal and regulatory information Cambium Networks end user license agreement

Page 4-3

Conditions of use

Any use of the Software and Documentation outside of the conditions set forth in this Agreement

is strictly prohibited and will be deemed a breach of this Agreement.

1. Only you, your employees or agents may use the Software and Documentation. You will take all

necessary steps to insure that your employees and agents abide by the terms of this Agreement.

2. You will use the Software and Documentation (i) only for your internal business purposes; (ii)

only as described in the Software and Documentation; and (iii) in strict accordance with this

Agreement.

3. You may use the Software and Documentation, provided that the use is in conformance with the

terms set forth in this Agreement.

4. Portions of the Software and Documentation are protected by United States copyright laws,

international treaty provisions, and other applicable laws. Therefore, you must treat the Software

like any other copyrighted material (for example, a book or musical recording) except that you may

either: (i) make 1 copy of the transportable part of the Software (which typically is supplied on

diskette, CD-ROM, or downloadable internet), solely for back-up purposes; or (ii) copy the

transportable part of the Software to a PC hard disk, provided you keep the original solely for back-

up purposes. If the Documentation is in printed form, it may not be copied. If the Documentation

is in electronic form, you may print out 1 copy, which then may not be copied. With regard to the

copy made for backup or archival purposes, you agree to reproduce any Cambium Networks

appear in any of several forms, including machine-readable form, and you agree to reproduce

such notice in each form in which it appears, to the extent it is physically possible to do so.

Unauthorized duplication of the Software or Documentation constitutes copyright infringement,

and in the United States is punishable in federal court by fine and imprisonment.

5. You will not transfer, directly or indirectly, any product, technical data or software to any

country for which the United States Government requires an export license or other governmental

approval without first obtaining such license or approval.

Chapter 4: Legal and regulatory information Cambium Networks end user license agreement

Page 4-4

Title and restrictions

If you transfer possession of any copy of the Software and Documentation to another party outside

of the terms of this agreement, your license is automatically terminated. Title and copyrights to the

Software and Documentation and any copies made by you remain with Cambium Networks and its

licensors. You will not, and will not permit others to: (i) modify, translate, decompile, bootleg,

reverse engineer, disassemble, or extract the inner workings of the Software or Documentation,

(ii) copy the look-and-feel or functionality of the Software or Documentation; (iii) remove any

proprietary notices, marks, labels, or logos from the Software or Documentation; (iv) rent or

transfer all or some of the Software or Documentation to any other party without Cambium’s prior

written consent; or (v) utilize any computer software or hardware which is designed to defeat any

copy protection device, should the Software and Documentation be equipped with such a

protection device. If the Software and Documentation is provided on multiple types of media (such

as diskette, CD-ROM, downloadable internet), then you will only use the medium which best meets

your specific needs, and will not loan, rent, lease, or transfer the other media contained in the

package without Cambium’s written consent. Unauthorized copying of the Software or

Documentation, or failure to comply with any of the provisions of this Agreement, will result in

automatic termination of this license.

Confidentiality

You acknowledge that all Software and Documentation contain valuable proprietary information

and trade secrets and that unauthorized or improper use of the Software and Documentation will

result in irreparable harm to Cambium Networks for which monetary damages would be

inadequate and for which Cambium Networks will be entitled to immediate injunctive relief. If

applicable, you will limit access to the Software and Documentation to those of your employees

and agents who need to use the Software and Documentation for your internal business purposes,

and you will take appropriate action with those employees and agents to preserve the

confidentiality of the Software and Documentation, using the same degree of care to avoid

unauthorized or improper disclosure as you use for the protection of your own proprietary

software, but in no event less than reasonable care.

You have no obligation to preserve the confidentiality of any proprietary information that: (i) was

in the public domain at the time of disclosure; (ii) entered the public domain through no fault of

yours; (iii) was given to you free of any obligation to keep it confidential; (iv) is independently

developed by you; or (v) is disclosed as required by law provided that you notify Cambium

Networks prior to such disclosure and provide Cambium Networks with a reasonable opportunity

to respond.

Chapter 4: Legal and regulatory information Cambium Networks end user license agreement

Page 4-5

Right to use Cambium’s name

Except as required in “Conditions of use”, you will not, during the term of this Agreement or

thereafter, use any trademark of Cambium Networks, or any word or symbol likely to be confused

with any Cambium Networks trademark, either alone or in any combination with another word or

words.

Transfer

The Software and Documentation may not be transferred to another party without the express

written consent of Cambium Networks, regardless of whether or not such transfer is accomplished

by physical or electronic means. Cambium’s consent may be withheld at its discretion and may be

conditioned upon transferee paying all applicable license fees and agreeing to be bound by this

Agreement.

Updates

During the first 12 months after purchase of a Product, or during the term of any executed

Maintenance and Support Agreement for the Product, you are entitled to receive Updates. An

“Update” means any code in any form which is a bug fix, patch, error correction, or minor

enhancement, but excludes any major feature added to the Software. Updates are available for

download at the support website.

Major features may be available from time to time for an additional license fee. If Cambium

Networks makes available to your major features and no other end user license agreement is

provided, then the terms of this Agreement will apply.

Maintenance

Except as provided above, Cambium Networks is not responsible for maintenance or field service

of the Software under this Agreement.

Chapter 4: Legal and regulatory information Cambium Networks end user license agreement

Page 4-6

Disclaimer

CAMBIUM NETWORKS DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS,

IMPLIED, STATUTORY, OR IN ANY COMMUNICATION WITH YOU. CAMBIUM NETWORKS

SPECIFICALLY DISCLAIMS ANY WARRANTY INCLUDING THE IMPLIED WARRANTIES OF

MERCHANTABILTY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. THE

SOFTWARE AND DOCUMENTATION ARE PROVIDED “AS IS.” CAMBIUM NETWORKS DOES NOT

WARRANT THAT THE SOFTWARE WILL MEET YOUR REQUIREMENTS, OR THAT THE OPERATION

OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR FREE, OR THAT DEFECTS IN THE

SOFTWARE WILL BE CORRECTED. CAMBIUM NETWORKS MAKES NO WARRANTY WITH

RESPECT TO THE CORRECTNESS, ACCURACY, OR RELIABILITY OF THE SOFTWARE AND

DOCUMENTATION. Some jurisdictions do not allow the exclusion of implied warranties, so the

above exclusion may not apply to you.

Limitation of liability

IN NO EVENT SHALL CAMBIUM NETWORKS BE LIABLE TO YOU OR ANY OTHER PARTY FOR ANY

DIRECT, INDIRECT, GENERAL, SPECIAL, INCIDENTAL, CONSEQUENTIAL, EXEMPLARY OR OTHER

DAMAGE ARISING OUT OF THE USE OR INABILITY TO USE THE PRODUCT (INCLUDING,

WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS

INTERRUPTION, LOSS OF BUSINESS INFORMATION OR ANY OTHER PECUNIARY LOSS, OR

FROM ANY BREACH OF WARRANTY, EVEN IF CAMBIUM NETWORKS HAS BEEN ADVISED OF

THE POSSIBILITY OF SUCH DAMAGES. (Some states do not allow the exclusion or limitation of

incidental or consequential damages, so the above exclusion or limitation may not apply to you.)

IN NO CASE SHALL CAMBIUM’S LIABILITY EXCEED THE AMOUNT YOU PAID FOR THE PRODUCT.

U.S. government

If you are acquiring the Product on behalf of any unit or agency of the U.S. Government, the

following applies. Use, duplication, or disclosure of the Software and Documentation is subject to

the restrictions set forth in subparagraphs (c) (1) and (2) of the Commercial Computer Software –

Restricted Rights clause at FAR 52.227-19 (JUNE 1987), if applicable, unless being provided to the

Department of Defense. If being provided to the Department of Defense, use, duplication, or

disclosure of the Products is subject to the restricted rights set forth in subparagraph (c) (1) (ii) of

the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 (OCT 1988), if

applicable. Software and Documentation may or may not include a Restricted Rights notice, or

other notice referring specifically to the terms and conditions of this Agreement. The terms and

conditions of this Agreement will each continue to apply, but only to the extent that such terms

and conditions are not inconsistent with the rights provided to you under the aforementioned

provisions of the FAR and DFARS, as applicable to the particular procuring agency and

procurement transaction.

Chapter 4: Legal and regulatory information Cambium Networks end user license agreement

Page 4-7

Term of license

Your right to use the Software will continue in perpetuity unless terminated as follows. Your right

to use the Software will terminate immediately without notice upon a breach of this Agreement by

you. Within 30 days after termination of this Agreement, you will certify to Cambium Networks in

writing that through your best efforts, and to the best of your knowledge, the original and all

copies, in whole or in part, in any form, of the Software and all related material and

Documentation, have been destroyed, except that, with prior written consent from Cambium

Networks, you may retain one copy for archival or backup purposes. You may not sublicense,

assign or transfer the license or the Product, except as expressly provided in this Agreement. Any

attempt to otherwise sublicense, assign or transfer any of the rights, duties or obligations

hereunder is null and void.

Governing law

This Agreement is governed by the laws of the United States of America to the extent that they

apply and otherwise by the laws of the State of Illinois.

Assignment

This agreement may not be assigned by you without Cambium’s prior written consent.

Survival of provisions

The parties agree that where the context of any provision indicates an intent that it survives the

term of this Agreement, then it will survive.

Entire agreement

This agreement contains the parties’ entire agreement regarding your use of the Software and

may be amended only in writing signed by both parties, except that Cambium Networks may

modify this Agreement as necessary to comply with applicable laws.

Third party software

The software may contain one or more items of Third-Party Software supplied by other third-party

suppliers. The terms of this Agreement govern your use of any Third-Party Software UNLESS A

SEPARATE THIRD-PARTY SOFTWARE LICENSE IS INCLUDED, IN WHICH CASE YOUR USE OF THE

THIRD-PARTY SOFTWARE WILL THEN BE GOVERNED BY THE SEPARATE THIRD-PARTY LICENSE.

Chapter 4: Legal and regulatory information Cambium Networks end user license agreement

Page 4-8

Net SNMP

Various copyrights apply to this package, listed in various separate parts below. Please make sure

that you read all the parts.

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

Derivative Work - 1996, 1998-2000

Permission to use, copy, modify and distribute this software and its documentation for any

purpose and without fee is hereby granted, provided that the above copyright notice appears in all

copies and that both that copyright notice and this permission notice appear in supporting

documentation, and that the name of CMU and The Regents of the University of California not be

used in advertising or publicity pertaining to distribution of the software without specific written

permission.

CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES

WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE REGENTS OF THE

UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL

DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR

PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,

ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

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

Redistribution and use in source and binary forms, with or without modification, are permitted

provided that the following conditions are met:

• Redistributions of source code must retain the above copyright notice, this list of conditions

and the following disclaimer.

• Redistributions in binary form must reproduce the above copyright notice, this list of

conditions and the following disclaimer in the documentation and/or other materials provided

with the distribution.

• Neither the name of the Networks Associates Technology, Inc nor the names of its contributors

may be used to endorse or promote products derived from this software without specific prior

written permission.

Chapter 4: Legal and regulatory information Cambium Networks end user license agreement

Page 4-9

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS”

AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE

DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE

FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR

SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER

CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR

TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF

THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

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

Redistribution and use in source and binary forms, with or without modification, are permitted

provided that the following conditions are met:

• Redistributions of source code must retain the above copyright notice, this list of conditions

and the following disclaimer.

• Redistributions in binary form must reproduce the above copyright notice, this list of

conditions and the following disclaimer in the documentation and/or other materials provided

with the distribution.

• The name of Cambridge Broadband Ltd. may not be used to endorse or promote products

derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER “AS IS” AND ANY EXPRESS OR

IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO

EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR

BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER

IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING

IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

SUCH DAMAGE.

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

Use is subject to license terms below.

This distribution may include materials developed by third parties.

Sun, Sun Microsystems, the Sun logo and Solaris are trademarks or registered trademarks of Sun

Microsystems, Inc. in the U.S. and other countries.

Redistribution and use in source and binary forms, with or without modification, are permitted

provided that the following conditions are met:

Chapter 4: Legal and regulatory information Cambium Networks end user license agreement

Page 4-10

• Redistributions of source code must retain the above copyright notice, this list of conditions

and the following disclaimer.

• Redistributions in binary form must reproduce the above copyright notice, this list of

conditions and the following disclaimer in the documentation and/or other materials provided

with the distribution.

• Neither the name of the Sun Microsystems, Inc. nor the names of its contributors may be used

to endorse or promote products derived from this software without specific prior written