ePMP Software Release 5.9.2 is now available

Supported Platforms

  • ePMP AX Platforms
  • ePMP AC Platforms
  • ePMP N Platforms

Download the firmware and documentation from:

Features

None

Problems Corrected

Tracking ID Products Description
AXG-10633 All Improved GPS geo-location accuracy for AFC.
AXG-10175 All Fixed low-speed issues for QinQ traffic.
AXG-10850 All Fixed the issue where SMs did not reconnect to the AP after it was reconfigured with RADIUS authentication enabled.
AXG-10853 All Fixed the issue preventing ePMP 4500L and ePMP 4600L from switching to SM mode.
AXG-10914 All Fixed the issue where the AP stopped sending Beacons after receiving a frame with its own MAC address as the source.
AXG-11034 All Fixed the inaccurate representation of EIRP obtained from the AFC server on the web interface.
AXG-11083 All Fixed the issue causing ePMP4600 4x4 crashes when configured with Omni antenna mode.
AXG-11107 All Fixed the issue where the Subnet Mask for the separate management interface became blank after upgrading to 5.9.1.
CAMBIUM-19915 All Fixed the issue where N-generation SMs reconnected unexpectedly.

Limitations

None

2 Likes

Hi Andrii, this final release has a difference with the 5.9.2rc5?

1 Like

That’s my question also – is there any difference from 5.9.2-RC5, or was RC5 determined to be stable, and this IS that candidate, just renamed? I have a couple RC5 sectors & their SMs (which seem to be doing well) but just wondering if I should bother moving them to 5.9.2 Release version, or if they actually aleady are on the Release Version anyway. :slight_smile:

1 Like

It’s 5.9.2-RC5 released as the final version.

Thank you.

4 Likes

2 posts were split to a new topic: Occasional drops in downlink throughput on 4600 under 5.9.2

When will the ping problems in PTP mode on the 4625 be fixed?

Or is there any chance of improvement?

What ping problems are you talking about?

1 Like

When the real traffic exceeds 500 Mbps, the devices start to apply a timeout error.

There is the same problem with PTP 4625 features in 8 different locations.

Are you pinging the radio or something on the other end of the link that is not a radio?

This is a direct ping to the radio.

Anyone using Cambium 4625 as PTP and passing 500 Mbps traffic knows this problem.

Try to downgrade to the last recommended version 5.9.0, we are downgrading all our network to this version with better results and no downlinks or timeouts. At now this is best version, at least for us…
Regards!

We used 5.9.0 for a long time, the situation was the same in that version.

I think there is a chronic problem.

I solved the problem like this
config set cambiumAccelerationEngine 3
config commit
reboot

3 Likes

Same here.
Once this fix was applied, no more weird issues.

Whoa, check your CPU stats everyone!!!

I upgraded a few towers early this morning and ALL of them had huge increases of CPU use.

An example was one epmp3000 with only 12 subs went from 13% to 61%!!!

This is wild and cannot be expected. I imagine theres new features, but i have not turned on any packet inspection stuff and ALL APs and ALL SMs have had these massive jumps in CPU use.

I will be reverting back

We’ve updated our entire network of e1/e3k/e4k… hundreds of radios and have not experienced that with 5.9.2. So I’m wondering if there’s something different in our configurations?

Second… are you sure that the extra CPU usage is causing an issue? Even if I was experiencing unusually high CPU usage, unless it was impacting traffic, I’d leave it on 5.9.2 and work with support to help identify the issue. It may all just be a superficial reporting issue.

It doesn’t look to have effected traffic. I can still get 370Mbps to a cpe router. Pretty horrible to see a jump that high though, and on ALL APs and CPE radios put on 5.9.2. Its a shame too as I’ve seen some modulation stability improvements. Probably a good idea to open a ticket and work through it though.

Looks like this … from 3:30AM so no traffic passing

Yuck :frowning:


update: disabling crash reporting is the fix. They know about it and 5.10 will fix. Unsure if a beta will come sooner.

2 Likes