Device Description |
Applicable Software Package |
Connectorized Radio with Sync |
ePMP-GPS_Synced-v3.4.1.tar.gz |
Integrated Radio / Connectorized Radio |
ePMP-NonGPS_Synced-v3.4.1.tar.gz |
CNUT package (for all radios) |
ePMP-3.4.1.pkg3 |
EPMP ELEVATE SOFTWARE
The following software is provided with ePMP Elevate in ePMP
System Release 3.4.1: |
Application Description |
Applicable Software Package |
ePMP Elevate (XM firmware devices) Use this file if upgrading an
XM device to ePMP Elevate for the first time |
UBNTXM-ubntxm-squashfs-factory.bin |
ePMP Elevate (XW firmware devices) Use this file if upgrading an
XM device to ePMP Elevate for the first time |
UBNTXW-ubntxw-squashfs-factory.bin |
ePMP Elevate (XM firmware devices) |
UBNTXM-v3.4.1.tar.gz |
ePMP Elevate (XW firmware devices) |
UBNTXW-v3.4.1.tar.gz |
Defects in green are resolved
Defect Fixes (System Release 3.4.1) Defects in black are open
|
Tracking |
Description / Workaround |
14598 |
Max Registrations Allowed is reset to 10 after AP Lite upgrade
from 3.3 to 3.4 with Full Capacity License Key Entered |
14591 |
Unable to login via GUI after changing radio's IP Assignment
using Firefox |
14589 |
[Elevate 5GHz] Software Update failed for 5GHz Elevate Devices on
cnMaestro |
14337 |
Unable to set Country Code after switching from SM to AP mode |
14482 |
Force 180/200 exhibiting reboot with 3.3 FW installed |
1439914360 |
Error message is displayed upon Link Tests start |
14611 |
[Elevate 2.4] "SM disassociated from AP. Reason 32/33/48" during
Stability test {XW} |
14613 |
Incorrect processing status on GUI when Link Test is failed |
14609 |
Home User erroneously able to configure network configuration |
14614 |
The Ping utility does not show latency if use less than 8 of
'Buffer Size' |
14612 |
[Elevate 2.4] Link Test is not completed properly |
Tracking |
Description / Workaround |
13955 |
[ePMP Elevate] Out of memory on XM during software upgrade with
the GUI via https |
14030 |
Unable to add the new AP to "Preferred APs" from "show details"
view at SM/config/radio/ |
12893 |
Web management interface does not use full width on widescreen
monitors |
14179 |
SNMPD crash after changing IP Assignment (Static or DHCP) |
13637 |
MNDP reports wrong information |
14131 |
[IPv6] AP and SM Separate Management interface don't show
obtained DHCP address on GUI without refresh |
Known problems or limitations (System Release 3.4)
|
Tracking |
Description / Workaround |
14591 |
Not able to login to the GUI after changing the IP. Works with
Chrome but not with Firefox. However, once you clear the cache and
cookies, it works with Firefox. (fixed in 3.4.1) |
14589 |
Upgrade of 2.4 and 5 GHz ePMP Elevate devices to 3.4 will shows
as failed when upgraded via cnMaestro. However, the devices do
upgrade and a refresh on the cnMaestro screen will show that the
devices are running 3.4 after a successful upgrade. (fixed in 3.4.1) |
14470 |
[ePMP Elevate 2.4] Unexpected behaviour of Port Speed Settings |
13308 |
[ePMP Elevate 2.4] RADIUS GUI Authentication: Authentication not
functional if used RADIUS authentication method |
14477 |
DHCP Server on SM sends host name as lease time if only digits
are used for DHCP client name |
14510 |
Unable to Export eDetect scan results in Chromium browser with
AdBlock extension |
14558 |
GUI shows error message after saving User Certificate for RADIUS
Server |
14458 |
[ePMP Elevate 2.4, XM] Cambium Elevate operating Tx Power exceeds
original nonCambium software-configured Tx Power by 1.5 - 3 dBm |
Tracking |
Description / Workaround |
13238 |
[ePMP Elevate] ePMP Elevate devices are not supported by CNUT |
13346 |
[ePMP Elevate] Device name and network settings are not copied
from original device configuration (resolved by ePMP Elevator tool) |
13299 |
[ePMP Elevate] Not possible to configure Uplink Max Rate to any
MCS except 7th on single stream devices |
14016 |
After configuring the SM device into NAT mode and reconfiguring
the WAN IP address, the Spectrum Analyzer tool is only available via
previously-configured Bridge mode IP address |
14030 |
Unable to add new AP to Preferred APs table when in "Show
Details" view. As a workaround, add new APs to the table when in
"Show List" view. (fixed in 3.4) |
14131 |
[IPv6] AP and SM Separate Management Interface don't display
obtained DHCP address on without manual refresh (fixed in 3.4) |
Tracking |
Description / Workaround |
13846 |
It is not possible to change the SM's Network configuration from
Bridge to Router mode via SNMP. (fixed in 3.3) |
13825 |
GUI indicates In-Service-Monitoring DFS status for 5-10 seconds
after switching to non-DFS channel. |
Known problems or limitations (System Release 3.2.1)
|
Tracking |
Description / Workaround |
13783 |
User cannot login to GUI by DNS address if URL contains dash (-).
(fixed in 3.3) |
13516 |
[ePMP Elevate] XM hardware - Spectrum Analyzer not supported
(fixed in 3.3) |
13343 |
[ePMP Elevate] XW hardware - If an ePMP Elevate module is
interrupted during an ePMP software upgrade, TFTP flash recovery of
ePMP Elevate software may fail. As a workaround, load the native
device software, then upgrade again to ePMP Elevate |
13552 |
[ePMP Elevate] After changing the device management IP address,
the browser may not automatically redirect to the new IP address.
Workaround: Enter the new management IP address in the browser
address bar. (fixed in 3.3) |
13630 |
[ePMP Elevate] Upon downgrading from Release 3.2.1 to Release
3.2, the Remote Management parameter may be set to Disabled.
Workaround: Re-enable the Remote Management parameter after
downgrading from Release 3.2.1 to Release 3.2. |
Tracking |
Description / Workaround |
13472 |
[ePMP Elevate] Updates to XM hardware Ethernet port interface MAC
address assignment (fixed in 3.2.1) |
13289 |
Invalid warning appears on web management interface when
Subscriber Module Target Receive Level is configured above -60 dBm
(fixed in 3.2.1) |
13165 |
SM in NAT mode with Separate Management IP and Management VLAN is
not accessible by Separate Management IP address (fixed in 3.2.1) |
13228 |
Web management interface is not accessible after an upgrade
attempt with invalid software archive. Workaround: reboot the device
to regain management access. |
13317 |
eDetect may not display interfering devices at lower
received/detected power levels (fixed in 3.3) |
13187 |
Upon configuration restore, a browser refresh is required to
display updated parameter values (fixed in 3.2.1) |
13274 |
[ePMP Elevate] ePMP Elevate subscriber may disconnect under load
due to hardware limitations. This disconnect is followed by an
immediate re-registration. (fixed in 3.2.2) |
12791 |
[ePMP Elevate] XM devices: When downlink RSSI is stronger than
-30 dBm, the web management interface incorrectly reports RSSI of
256 dBm and SNR as 0 dB (fixed in 3.2.1) |
12919 |
[ePMP Elevate] Rocket™ M5 (XM and XW): The web management
provides options for configuring the device in AP or ePTP mode.
These modes are not supported by ePMP Elevate software and should
not be utilized. (fixed in 3.2.1) |
13332 |
On occasion, after upgrading an ePMP SM to Release 3.2, the SM's
web management interface may display "Board still in reboot state"
or the interface may not be accessible. Workaround: reboot or power
cycle the SM. (fixed in 3.3) |
Tracking |
Description / Workaround |
13220 |
Support for use of shift key to select multiple frequencies in
the Scan List (fixed in 3.2.1) |
13165 |
SM does not create static route for separate management interface
(fixed in 3.2.1) |
13117 |
ePMP 2000 device configured in SM mode reports incorrect AP
frequency and does not register (fixed in 3.2.1) |
12409 |
With rare occurrence, SM scans without registration |
12709 |
ePMP 2000: Cannot factory default via power cycle sequence (fixed
in 3.2.1) |
12792 |
Throughput Chart: Upon changing Throughput Measurement Period,
control points (hover targets) not shown (fixed in 3.2.1) |
12837 |
With certain configurations, GPS-synched software can be loaded
onto Force 200 module |
12878 |
ePMP device reboots twice after factory default |
Tracking |
Description / Workaround |
12385 |
ePMP web management interface test tool Ping (Tools > Ping) does
not execute with maximum buffer size (65507) |
12439 |
ePMP devices with saved cnMaestro credentials which are not
on-boarded by cnMaestro for more than 12 hours will stay in state
"Device Approval Pending" |
12513 |
Transmitter Output Power reference tables duplicated in web
management interface notification |
Tracking |
Description / Workaround |
12794 |
False radar detection on DFS channel FCC1322 Type1 22 (fixed in
3.2.1) |
12793 |
False radar detection on DFS channel FCC1322 Type1 24 (fixed in
3.2.1) |
12125 |
When in ETSI region and 5.4 GHz band using LBT, if the SM is
subjected to very high interference, it may cause a reboot with a
crash signature "arqtx_rwb_from_wbuf". |
11973 |
The "Internet" Globe icon on the top right of the GUI page may
take up to 40 seconds to turn green once a DNS server has responded. |
11491 |
When ePMP 2000 is in Standard WiFi, a Ubiquiti Nanobeam may not
register. There is currently no workaround. |
11406 |
When using 5 MHz channels on ePMP 2000 in TDD mode, TCP downlink
throughput may degrade by up to 20%. |
Tracking |
Description / Workaround |
11978 |
When there are more than 128 entries into the Bridge Table, the
table may display as an empty table. |
Tracking |
Description / Workaround |
10907 |
When in AP WiFi mode and the SM connected is an 802.11a SM, the
downlink throughput can be lower by 20%. (fixed in 3.3) |
10704 |
When editing the MAC Addresses entries in the Wireless MAC
Filtering table using the configuration file upload, care must be
taken to ensure MAC address format integrity. The ePMP device will
not validate the format. |
Tracking |
Description / Workaround |
9951 |
On occasion, pings are lost when continuously pinging the SM from
the AP. The ping loss can occur for a period of 30-60 seconds before
it operates normally. User traffic may also be lost during this time
and a reboot of the SM may be required to recover the SM. |
Tracking |
Description / Workaround |
8198 |
On occasion, stale ARP entries are not cleared from the ARP table
(under Monitor>network) on the SM. The entries should be cleared in
5 minutes but it may take up to 10 minutes for them to be cleared. |
Tracking |
Description / Workaround |
7822 |
When the SM is in NAT mode, it's possible to configure the
Separate Wireless Management IP in the same subnet as the IP of the
SMs Ethernet/LAN interface. Care should be taken to configure the
Separate Wireless Management IP on a different subnet for security. |
Tracking |
Description / Workaround |
7676 |
SM may not successfully obtain an IP address via DHCP if certain
special characters (ex: parenthesis) are used in the Device Name of
the SM. |
7622 |
In Release 2.3, a minor enhancement was introduced where the user
is able to select an AP from the SM's Available APs list (under
Monitor>Wireless) and add it to the Preferred APs list (under
Configuration>Radio). However the user is able to add more than 16
entries while the Preferred APs list supports a maximum of 16
entries. User will need to manually delete entries in the Preferred
APs list to not exceed 16 before the configuration can be saved.(fixed in 3.2.1) |
7289 |
On occasion, the GUI does not display data on the
Monitor>Wireless Page. Workaround is to refresh/reload the browser. |
7287 |
When ACS is run multiple times, the ACS chart (under Tools>ACS)
may display prior results while the radio is operating on a channel
selected by the last ACS run. Refresh the browser to see the latest
chart. |
Tracking |
Description / Workaround |
6919 |
When ACS is run multiple times in a row (under Tools>Automatic
Channel Selection), the ACS graph may also show the scale on the
X-axis incorrectly (40MHz instead of 20MHz). Refresh the browser
screen (F5 in MS Windows) to get the correct chart for the last ACS
run on that page. |
6801 |
When an ETSI license key is applied to an ePMP 5GHz ETSI locked
radio, it may come up with "Generic ETSI" as country code. Perform a
second reboot of the radio to load the license key. |
6407 |
When a new user logs into the radio UI, notifications for the
previously logged in user is visible. Workaround is to clear all
notifications before logging out of the radio's UI. |
Tracking |
Description / Workaround |
5018 |
On rare occasion, when using Radius and the SM is under poor RF
conditions, reauthentication may fail. A device reboot may be required
to perform Network Entry again. |