Globe Internet Connectivity icon was always Grey in color.
MPLS traffic was not reaching the maximum possible values.
Traffic stuck occurred with PPPoE traffic running through the link occasioanally.
The tcpdump command did not work in admin CLI.
Incorrect RSSI values was displayed in scanning list on the SM.
Configuration file imported from Force 300 was restored to Force 400 and maximum MCS was displayed incorrectly on the UI.
5745 MHz channel was not available for configuration with 40 MHz bandwidth for the FCC region countries.
Multiple Stability Improvements for Force400C and Force 425
The SNMP remote access is disabled by default for the following scenarios:
If the radio is upgraded from Firmware versions 5.1.3 or below to 5.3-RC14 or newer Firmware version and default SNMP community strings are configured.
If the configuration file from 5.1.3 or earlier Firmware is restored to the device;
If the radio is reset to default on 5.3-RC14 or newer Firmware.
The password change is needed on UI on a first boot after upgrade if password length doesn’t match the security criteria or the default values are used. The user passwords for Firmware versions 5.3.0 and SNMP Read-Write Community Strings must be at least eight characters in length.
The features introduced in System Release 5.3-RC14 Beta are as follows:
Radio Transmission Optimization
Radio Transmission Optimization
Radio Transmission Optimization brings a new configuration switch to optimize a radio transmission parameters according to the network demands. To configure radio transmission optimization, go to Configuration > Radio tab of the radio in the Access Point mode and with ePTP driver enabled. This is applicable to 5.3.0 and above 802.11 AX platforms. Next figure shows the Radio Transmission Optimization option.
There are 3 options available:
Lower Latency - Radio transmission optimized to achieve minimum latency
Balanced - Default mode of operation
Higher Throughput - Radio transmission optimized to achieve the best throughput numbers
802.11 protocols family uses PPDU/frames to transmit data. Each physical layer protocol data unit (PPDU) contains preamble and data fields. The preamble field contains the transmission vector format information. The data field contains the user payload and higher layer headers, such as medium access control (MAC) fields and cyclic redundancy check (CRC). The preamble length is constant and does not depend on payload amount. Of course the amount of data at certain periods of time is changing.
With constant PPDU duration and low payload the station will transmit underloaded frames. So wasting air time. When maximum throughput is not required the latency can be improved by decreasing PPDU duration. And in the opposite way extended PPDU duration will improve throughput because larger payload will be transmitted with the same preamble length.
Thus behind Radio Transmission Optimization switch options stands a simple PPDU duration. 3 options mentioned above correspond to 3 frame durations: 1 ms, 2 ms and 4 ms.
Now network administrators can choose one of the 3 options and optimize link performance according to current demands.
In the ePMP devices, the IPv6 Assignment configuration parameter describes the IPv6 address specification. Next figure shows the IPv6 Assignment options.
There are two applicable settings for the IPv6 Assignment parameter:
Static: Device management IP addressing is configured manually in IPv6 Address and IPv6 Gateway fields.
DHCP: Device management IP addressing (IP address and gateway) is assigned using a network DHCP server. IPv6 Address and IPv6 Gateway parameters are unused. If the DHCPv6 server is not available, then the previous static IPv6 address is used as a fallback IPv6 address. If no previous static IPv6 address is available, then no IPv6 address will be assigned. By default, DHCPv6 occurs over the wireless interface.
I have 5.3 running on a few links. It seems to just work. I haven’t played with the latency/speed knobs at all. The links are all set to balanced. 7 days now and no issues.
It would be awesome if in the future the management vlan could be tagged on just the ethernet port, for both AP and STA. We often use the same VID on both sides of the link but don’t necessarily want it to bleed over the link if possible.
We don’t have many Force 400 links left in the field anymore, but we put it on a Force400c 15km link, and it seems to be working well. I don’t really see any performance difference vs the 5.1.3 on this link, although on a couple Force 425’s in our test/shop, 5.3 was MUCH faster than 5.1.3 was… and I love the Latency/Throughput optimization settings.
What did you end up replacing the 400’s with if I might ask ?
Given ubnt being nonexistent and Mimosas chip lineup issues choices in my parts of the worlds are pretty thin.
We’ve been mostly happy with the 400’s thus far and have replaced most of the non airfibers with them.
To answer your question, we went back to AF5xHDs. I want to be clear → Force 400s are better in many ways. and they work very well for us on some links - but the AF5xHD’s GUI, and the info it provides – and most importantly, the ability to change channels seamlessly without dropping the link for multiple minutes, plus a few of it’s features just make using the AF5xHD’s preferable in quite a few of our links.
I think it depends on what your link requirements are. We don’t find ourselves changing channels very often, and when we do, we make changes late at night. So having a late night brief disconnect maybe a couple times a year is fine on our network… but it might not be for others. I’m not sure why Cambium hasn’t implemented a follow me channel feature on ePMP… they have on PMP450, although it’s not hitless (not on DFS however) like UBNT’s implementation.
Hi Andrii, I had upgraded to 5.3 and the slow Web UI load was resolved. I am experiencing some issues with 1 400c link. Everything was working as expected but then one day randomly the slave went offline for 2.5 hours and then came back on its own. I confirmed that the Tower site on the SM side did not lose power and nor did the master side. I logged into the master side and tried a reboot but the slave would not reconnect. The slave side is remote and a bit harder to get to in winter but as preparations where being made to get out to site it came back up on its own.
The link is 24km with 3ft Radiowave antennas on both sides, link with great LOS, the link RSSI was around -58 to -60db but since this random happening the link is now -67db to -73db. I am not seeing any interference but I am seeing -67 sometimes where other times its -73. Submitted a ticket but support did not find anything.