ePMP - Release Notes - Release 5.7

Download as pdf or txt
Download as pdf or txt
You are on page 1of 16

RELEASE NOTES

ePMP

Release 5.7
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.

© 2024 Cambium Networks Limited. All rights reserved

pmp-2714_001V032 May 2024


Contents
Contents 3

General Information 4
Version information 4

ePMP Release 5.7 Information 6


Introduction 6

Features description 6

Backward Compatibility AX-to-AC 6

Quality of Service (QoS) 7

Maximum Transmission Unit (MTU 9600) 9

Split Sector and Omni mode 10

Automated Frequency Coordination (AFC) 6 GHz 11

Improvements, Known Issues or Limitations 15

Improvements 15

Limitations 15

Cambium Networks 16

Contents 3
General Information
Version information
The following table shows the issue status of this document since it was first released:

Document version Date of issue System Release

000v006 July 2022 4.7

001V001 October 2022 4.7 Beta

001V002 October 2022 5.3

001V003 November 2022 4.7

001V004 February 2023 5.4.1 Beta

001V005 February 2023 4.7.01 Beta

001V006 March 2023 4.7.0.1-RC7 Beta S2

001V007 March 2023 4.7.0.1

001V008 June 2023 5.4.1-RC15 Beta

001V010 July 2023 5.4.1

001V011 July 2023 4.7.1-RC13

001V012 August 2023 5.4.2

001V013 September 2023 4.7.1-RC17 Beta

001V014 October 2023 4.7.1-RC21 Beta

001V015 November 2023 4.7.1-RC22 Beta

001V016 December 2023 5.6.0-RC23 Beta

001V017 December 2023 5.6.0-RC26 Beta

001V018 December 2023 4.7.1-RC24 Beta

001V019 January 2024 4.7.1

001V020 January 2024 5.6.0-RC29 Beta

001V021 February 2024 5.6.0

001V023 March 2024 5.6.1-RC7 Beta

001V024 March 2024 4.8-RC12 Beta

001V025 April 2024 5.6.1

001V026 April 2024 4.8

001V027 May 2024 5.7-RC59 Beta

General Information 4
Document version Date of issue System Release

001V029 May 2024 4.8.1 RC4 Beta

001V032 May 2024 5.7

General Information 5
ePMP Release 5.7 Information
Introduction
This document provides information about the new features, additional enhancements, problems
corrected, and known issues in Release 5.7.

This chapter contains the following sections:

l Features description

l Improvements, Known Issues or Limitations

Features description
The following are the new features introduced in Release 5.7:

l Backward Compatibility AX-to-AC

l Quality of Service (QoS)

l Maximum Transmission Unit (MTU 9600)

l Split Sector and Omni mode

l Automated Frequency Coordination (AFC) 6 GHz

Backward Compatibility AX-to-AC


In this release, the backward compatibility between ePMP 4xxx APs (or Force 45xx operating in AP role)
and ePMP Force 300s SMs is supported. This feature is disabled by default and should be enabled from
the UI for interconnection between fourth and third ePMP generations. To enable this feature, navigate to
Configuration > Radio and select Enabled for Backward Compatibility (Beta Quality) as shown in Figure 1.

Figure 1: Enabling backward compatibility

ePMP Release 5.7 Information 6


Quality of Service (QoS)
In this release, Cambium Networks introduces Quality of Service (QoS) implementation for the AX
platform.

ePMP QoS is a Cambium Networks proprietary methods for prioritizing, queueing, and limiting traffic
within the system’s Time Division Duplex (TDD) scheduler. QoS feature is not available for ePTP and WLR
driver modes.

Cambium QoS consists of two functional areas:

l Prioritization

l Rate limiting.

The ePMP system prioritizes different types of traffic within internal queueing mechanisms. These
mechanisms are controlled by classification rules defined at the user level.

Radio link traffic may be prioritized as Voice, High, or Low based on system configuration and traffic
type. For all ePMP AX devices, high and low queue QoS prioritization and rate limiting mechanisms are
applied solely to traffic ingressing the device Ethernet port and exiting the device radio interface (over
the radio link). For example, ePMP AX AP devices enact QoS for High and Low priority data entering the
Ethernet port and exiting the device over the radio downlink. ePMP AX SM enact QoS for high and low
priority data entering the Ethernet port and exiting the device over the radio uplink. If there is a Voice
traffic, then the ePMP system features a mechanism where the subscriber may piggyback a bandwidth
request with VoIP packets sent over the uplink. This allows the AP to schedule additional subscriber
uplink allocation (instead of the subscriber waiting for the next uplink polling response opportunity to
schedule transmission). The result is better handling of voice application communication and more
reliable call quality.

To configure QoS, navigate to Configuration > Quality of Service, as shown in Figure 2.

Figure 2: Quality of Service (QoS

With the ePMP device, an unicast traffic is prioritized based on Layer 2 markings (VLAN, CoS, EtherType,
MAC address) and Layer 3 markings (IP, DSCP). This prioritization can be controlled by configuring QoS
classification rules on the device (these rules are configured in the device QoS Classification Rules table).
The QoS Classification Rules table () contains all of the rules enforced by the device when passing traffic
over the radio link. Traffic passed through the device is matched against each rule in the table. When a
match is made, then the traffic is sent over through the radio link using the priority defined in Priority
column.

ePMP Release 5.7 Information 7


Figure 3: The QoS Classification Rules table

Prioritization can also be controlled by modifying the Subscriber Module Priority configuration parameter
to automatically place all non-voice (non-VoIP) traffic in either the high priority queue or the low priority
queue. For example, when this parameter is set to High, the SM places all data other than VoIP in the High
priority queue. This data will be given higher priority than other sector SMs configured with Subscriber
Module Priority parameter set to Normal or Low. This high-priority SM is served by the AP with its traffic
automatically classified, and scheduled as, Voice (VoIP traffic) and High (all other traffic) priority.

Attention

For any QoS implementation, you must be careful while assigning high priority to an SM, if
additional QoS classification rules are configured on the same system.

Prioritization of Broadcast and Multicast traffic


The Operators can configure ePMP devices to prioritize broadcast and multicast traffic automatically into
the High priority queue or Low priority queue. By default, both broadcast and multicast traffic are
automatically categorized in the Low priority queue. At the user level, this prioritization is controlled by
the parameters Broadcast Priority and Multicast Priority. describes the differences between Broadcast
and Multicast priority.

Table 1: Broadcast and Multicast priority


Broadcast priority Multicast priority

Low Priority: All broadcast traffic sent over the Low Priority: All Multicast traffic sent over the
downlink is prioritized as low priority and is downlink is prioritized as low priority, and is
delivered to the SM after scheduled high priority delivered to the SM after scheduled high priority
and VoIP traffic. and VoIP traffic.

High Priority: All broadcast traffic sent over the High Priority: All Multicast traffic sent over the
downlink is prioritized as high priority and is downlink is prioritized as high priority and is
scheduled for delivery to SMs before low priority scheduled for delivery to SMs before low priority
traffic but after VoIP traffic. traffic but after VoIP priority.

Data servicing scheduling decisions are made between the various queues by a Weighted Fair Queueing
(WFQ) algorithm. This implementation introduces an internal 50:30:20 weighting between the Voice,
High, and Low queues respectively. This means that while certain packets are served with priority, high-

ePMP Release 5.7 Information 8


priority and high-bandwidth traffic does not consume the entire capacity of the link causing delivery
failure of lower-priority traffic. This contrasts with strict priority scheduling systems present in other data
delivery systems which may serve higher-priority traffic first regardless of bandwidth usage and
starvation of lower-priority traffic. The ePMP system employs weighted fair queueing to ensure reliable
user data transmission while serving higher-priority traffic on the same wireless link.

From Release 5.7.0 onwards, the extended QoS statistics are represented on the UI, CLI and SNMP.

Maximum Transmission Unit (MTU 9600)


In this release, ePMP supports for an increased Ethernet MTU. An increased MTU value of up to 9600
bytes is supported only for ePTP and WLR modes, and not for TDD/TDD PTP.

Configuring MTU 9600 from UI


To configure MTU 9600 on the device, navigate to Network > Ethernet Port and set the value of 9600 for
Ethernet MTU field as shown in Figure 4. After applying the changes, reboot the device.

Figure 4: Configuring MTU 9600

Attention

Increasing MTU size requires proper configuration and support across all the network
devices and components within a network segment. Incompatible or misconfigured MTU
settings can lead to fragmentation, packet loss, or interoperability issues.

Configuring MTU 9600 from CLI


To configure the MTU 9600 from CLI, run the following command:
>config set networkBridgeMTU "9600"
>config commit

After complete, reboot the device.

cnMaestro template
{
"device_props": {
"networkBridgeMTU": "9600"

ePMP Release 5.7 Information 9


SNMP MIB object
networkBridgeMTU OBJECT-TYPE
SYNTAX Integer32 (576..9608)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Device Bridge MTU size
For 802.11n devices maximum value is 1700 and default is 1500"
::= { networkBridge 6 }
Get
$ snmpget -v2c -c public123 169.254.1.1 .1.3.6.1.4.1.17713.21.3.4.7.6.0
Set
$ snmpset -v2c -c private123 169.254.1.1 .1.3.6.1.4.1.17713.21.3.4.7.6.0 i 9600

Split Sector and Omni mode


In this release, ePMP extends antenna support for Split-Sector and Omni mode. Omni directional antenna
based on four 90° sectors must be connected in the following H/V polarity combination per sector:

l 0/1

l 2/3

l 4/5

l 6/7.

Split-Sector antennas must be connected as follows:

l 1st one to chains 0/1/2/3

l 2nd one to chains 4/5/6/7

To select the Split Sector and Omni mode, navigate to Configuration > Radio from the UI as shown in
Figure 5.

Figure 5: Split Sector and Omni mode

ePMP Release 5.7 Information 10


Configuring through CLA
E4600_4x4_f0078a>config set wirelessAntennaType

AP Antenna for MU-MIMO:

1 - Sector

2 - Omni

Applicable for 4+ chain devices

Device Allocation: AP

E4600_4x4_f0078a>config set wirelessAntennaType 2

E4600_4x4_f0078a>config commit

Template for cnMaestro


{
"device_props": {
"wirelessAntennaType": "2"
}
}

SNMP MIB object


wirelessAntennaType OBJECT-TYPE
SYNTAX Integer32 (1|2)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"AP Antenna for MU-MIMO:
1 - Sector
2 - Omni/Split-Sector
Applicable for 4+ chain devices
Device Allocation: AP"
DEFVAL { 1 }
::= { wirelessDevice ???? }

Automated Frequency Coordination (AFC) 6 GHz


In this release Automated Frequency Coordination (AFC) functionality has been introduced for ePMP 6
GHz (ePMP 4600x/Force 46xx) platforms.

The AFC establishes the regulations for the unlicensed use of the 6 GHz band (5.925 GHz- 7.125 GHz),
aimed at mitigating potential interference from the conventional high-power access devices and the
stationary client devices to the licensed microwave receivers and specific radio astronomy observatories
operating within this frequency range.

ePMP Release 5.7 Information 11


The following are the objectives and rules for AFC:

l Prioritize and protect incumbent 6 GHz licensed microwave networks.

l 6 GHz unlicensed networks can only use channels that are not previously assigned to the licensed
microwave.

l Can use any channel that is not protected by the AFC.

l There is no prioritization or channel assignment as shown in Figure 6.

Figure 6: Channel assignment

Operation rules
The following are the operation rules for 6 GHz:

l Requires the use of AFC.

l UNII-5 and UNII-7 are allowed for fixed outdoor use at 36 dBm EIRP in the United States.

l Canada allows UNII-6.

l All SMs and APs require specific GPS receiver from the manufacturer to indicate location.

Configuring AFC
You must configure AFC on the device. Figure 7 shows the operation of the AFC.

Figure 7: Operation of the AFC

FCC (ULS)
Query: I am at this location. License
Each radio in > What channels and power >
levels are available? Proxy Server Microwave
6 GHz Network
(Optional) AFC Server Database of
Access Points Response: Use any of these Internet incumbent
Subscriber Module < channels up to these power < 6 GHz
PTP Ends levels Microwave
Licenses
Firewall

ePMP Release 5.7 Information 12


Prerequisites

The following are the prerequisites to configure AFC on the device:

l A GPS receiver is required on all radios (SMs and APs).

l Each radio must separately query the AFC with its precise location and the pre-shared encryption
key.

l An optional proxy server can be configured. All transactions use HTTPS queries once at start-up,
and then every 24 hours or after each configuration change.

l Queries are not latency sensitive and require negligible throughput.

l APs and SMs are configured to Fixed Client Mode that does not transmit unless in compliance with
the AFC response.

Configuring AFC on the device

By default, AFC is enabled and it does not require any additional configuration.

To use AFC, the APs and SMs must:

l be able to make HTTPS requests out to the Internet.

l be running Firmware version of 5.7-RC63 or higher.

l have a DNS server configured.

l have a GPS signal.

To enable the Spectrum Analyzer chart, navigate to Configuration > Radio, as shown in Figure 8. The AFC
chart gives more data to chose best channel.

Figure 8: The AFC chart page

ePMP Release 5.7 Information 13


The radio configuration section displays the data obtained from the AFC server in the chart format that
simplifies the process of the best operational channel selection for the FCC APs.

The chart demonstrates available channels and Tx power allowed accordingly. The chart scale can be
changed for accurate data analysis using the lower chart. You can edit the chart and configure the
channel directly from the chart.

The following operational modes are allowed on the SM side :

l Standard Client Mode (Default)

l Fixed Client Mode

When SM operates in Standard Client Modes, it follows AP (that interacts with AFC and gets allowed
channels and EIRPs accordingly) and EIRP 6 dBm lower, then the max EIRP advertised to AP it is
registered on by AFC server.

When SM operates in Fixed Client mode it sends the request to AFC server and gets individual respond
allowing getting Max EIRP up to 36 dBm as shown in Figure 9.

Figure 9: The radio configuration page

Run the he following command for the cnMaestro Template for Fixed Client mode configuration.
{
"wireless":
{
"@wifi-iface[0]":
{
"afc_sta_mode": "1"
}
}
}

ePMP Release 5.7 Information 14


The following are the SNMP parameters available on the system:
cambiumAfcEventWaitTrap - .1.3.6.1.4.1.17713.21.0.17
cambiumAfcTxOffTrap - .1.3.6.1.4.1.17713.21.0.18
cambiumAfcExpiryTrap - .1.3.6.1.4.1.17713.21.0.19
cambiumAfcEventOperatingTrap - .1.3.6.1.4.1.17713.21.0.20

Improvements, Known Issues or Limitations


Improvements
Improvements in Release 5.7 are listed below:

l Throughput and latency improvements for the sectors with 10+ SMs connected for
ePMP45xx/F45xx deployments.

l Stability Improvements for ePMP 45xx/ePMP 46xx, Force 4xxx/Force 6xxx platforms.

l Performance improvements for deployments operating in the noisy environment.

l FCC DFS 5.2 GHz and 5.4 GHz bands are opened for ePMP 4500L and Force 4525.

Limitations
l Separate Management Interface may not come up if the device is configured in the NAT mode.

l Slightly higher latency may be seen occasionally for Backward Compatibility deployments
compared to AC greenfield.

l There are performance improvements specifically benefits the ePMP 45xx series of products when
large number of SMs are attached. These improvements span across throughput, stability of
connections and overall stability of the system. The customers may notice impact to latency in
some cases and this is under development by Cambium Networks with urgency for the upcoming
release.

l In the 4600 series of products, there is a significant stability and connection reliability in this
release. The scalability performance improvements are not at the same level as the 4500, due to
the fundamental architecture differences. Cambium Networks is actively working on this and
anticipate that in the upcoming weeks, these improvements can be to push to the customer after
the regulatory approvals in the next 10 days.

ePMP Release 5.7 Information 15


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.

User 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 http://www.cambiumnetworks.com/contact-us/

Address 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 2024 Cambium Networks, Ltd. All rights reserved.

Cambium Networks 16

You might also like