ePMP 400/425 Software Release 5.3 is now available

Supported Platforms

  • ePMP 11ax family

Download the firmware and documentation from:

Problems corrected

Tracking ID Products Description
AXG-1772 Force400C, Force425 Globe Internet Connectivity icon was always Grey in color.
AXG-1965 Force400C, Force425 MPLS traffic was not reaching the maximum possible values.
AXG-2788 Force400C, Force425 Traffic stuck occurred with PPPoE traffic running through the link occasioanally.
AXG-3372 Force400C, Force425 The tcpdump command did not work in admin CLI.
AXG-3460 Force400C, Force425 Incorrect RSSI values was displayed in scanning list on the SM.
AXG-3902 Force400C, Force425 Configuration file imported from Force 300 was restored to Force 400 and maximum MCS was displayed incorrectly on the UI.
AXG-4451 Force400C, Force425 5745 MHz channel was not available for configuration with 40 MHz bandwidth for the FCC region countries.
AXG-4475 Force400C, Force425 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.

Features description

The features introduced in System Release 5.3-RC14 Beta are as follows:

  • Radio Transmission Optimization
  • IPv6 Supportб

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.

IPv6 Support

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.
3 Likes

Did anyone have chance to try? Is there any feedback or it just works?

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.

1 Like

Don’t think I got you right about management vlan. How do you want it not to “bleed over the link”?

Being able to tag the management vlan on only the ethernet interface (on SM and AP) would be great, vs the bridge interface (wireless + ethernet).

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.

2 Likes

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.

3 Likes

Something is wrong with the traceroute on this software, when there is no response in the step (stars appear), it crashes with some errors. I attach below what it looks like:

Complete
Hostname www.orage.pl

traceroute to www.orage.pl (188.128.255.251), 30 hops max, 38 byte packets
1 funbox.home (192.168.1.1) 46 bytes to (null) 1.693 ms (64) 1.723 ms (64) 1.820 ms (64)
2 83.1.5.76 (83.1.5.76) 36 bytes to (null) 7.429 ms (254) 12.114 ms (254) 13.601 ms (254)
3 wro-r11.tpnet.pl (80.50.158.249) 36 bytes to (null) 5.919 ms (253) 9.075 ms (253) 11.557 ms (253)
4 war-ar2.tpnet.pl (195.205.0.10) 36 bytes to (null) 14.419 ms (250) 14.085 ms (250) 15.098 ms (250)
5 80.50.131.178 (80.50.131.178) 76 bytes to (null) 14.389 ms (250) 14.965 ms (250) 14.677 ms (250)
6 62.29.242.177 (62.29.242.177) 148 bytes to (null) 15.135 ms (248) 62.29.242.181 (62.29.242.181) 148 bytes to (null) 15.758 ms (248) 15.565 ms (248)
7 rou24246ctf.isp.t-mobile.pl (157.25.255.196) 76 bytes to (null) 13.638 ms (249) 15.490 ms (249) 14.512 ms (249)
8 217.153.235.202 (217.153.235.202) 36 bytes to (null) 14.292 ms (248) 14.826 ms (248) 13.631 ms (248)
9 lsys1-lt0.home.net.pl (62.129.251.191) 36 bytes to (null) 14.284 ms (247) 14.926 ms (247) 14.236 ms (247)
10
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
*
11 *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
12
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
*
13 *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
14
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
*
15 * *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
*
16 *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
17
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
*
18 *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
19
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
*
20 *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
21
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
*
22 *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
23
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
*
24 *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
25
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
*
26 *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
27 *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
28
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
*
29 *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
30
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
* *
64 bytes from 192.168.1.18 to 192.168.1.18: icmp type 0 (Echo Reply) code 0
4: x33323130
8: x37363534
12: x3b3a3938
16: x3f3e3d3c
20: x43424140
24: x47464544
28: x4b4a4948
32: x4f4e4d4c
36: x53525150
40: x57565554
44: x5b5a5958
48: x5f5e5d5c
52: x63626160
56: x00666564
60: x00000000
*
1 Like

Thank you for your feedback.
We are checking this.

Thank you!

1 Like

The issue has been confirmed.
The fix is coming in the next firmware version.

Thank you.

1 Like

Thanks for the input.
Our 5xHD and AF11’s will be running until the magic smoke runs out of them.

Hi eveyone, I am curious if anyone @anon89030143 would like to comment on ninedd’s comment? As per his comment I also am annoyed by this as well.

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.

The seamless channel switching is coming for ePMP gear soon.
We will be able to provide Alpha firmware for testing shortly.
Please let us know if you are interested in giving it a try.

Thank you.

3 Likes

Yes, I am. I’m supposed to be one of the early Beta folks, but I never get them. I’d certainly be interested in helping test new features. :+1:

2 Likes

Hi all, is anyone field testing 5.4.1 beta on Force 400? Was the Slow WEB UI load resolved?

Hi @DigitalMan2020,

5.4.1 has a bunch of fixes related to GUI and SNMP operation.

Could you tell more about the issue you are observing? So I can check more accurate. Of course it will be easier first to try 5.4.1.

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.

Sounds like a loose antenna moving in the wind? Or a wet pigtail connector?

1 Like