ePMP Software Release 5.9.1 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-3749 All Fixed a crash with the signature “Target assert on ar_wal_monitor.c:913,” which could occur on rare occasions.
AXG-8669 All Fixed a crash with the signature “ABT_Handle_Interrupt + 0x114 (NOC_error.c:357),” which could occur on rare occasions.
AXG-10503 All Fixed the issue preventing users’ passwords from updating after applying the appropriate cnMaestro template.
AXG-10522 All Fixed the issue where SMs could disconnect with the INVALID SECURITY KEY reason under strong interference.
AXG-10625 All Fixed the issue causing MCS fluctuation and packet loss in ePTP mode.
AXG-10732 All Resolved a problem that caused packet loss, high jitter, and increased latency in TDD mode during peak load times.
AXG-10852 All Fixed a crash with the signature “Assertion camb_eap_hw_flush_wa.c:111(tx_dm_dynamic_fc_timeout + 0x0),” which could occur on rare occasions.
AXG-10856 All Resolved an issue where the Tx Power settings configured through the UI were not applied correctly.
AXG-10904 All Resolved a graphical issue that caused an unexpected grey background to appear on the Spectrum Analyzer chart.
AXG-10928 All Fixed an issue preventing ETSI-locked F46xxs from switching to Access Point mode.
CAMBIUM-19899 All Fixed the issue where the Throughput chart failed to display on the Wireless Link Test.

Limitations

When upgrading the radio firmware from versions earlier than 5.7.2 to version 5.9.1, the Separate Wireless Management Interface may lose its Subnet Mask configuration.

Recommended Workaround:
Prior to the upgrade, disable the Separate Wireless Management Interface. Once the upgrade is complete, re-enable it. This process can be efficiently performed using a cnMaestro template.

2 Likes

It is already available in Downloads. As usually cnMaestro will have it slightly later.

3 Likes

Does this release have the legacy force200 to 4500 compatibility? Does it require a CLI command like the RC versions? If so, what was the command again?

Does this fix the issue with MIR? We were told not to implement the MIR after all the CPEs dropped from the AP.

Not yet. The fix is coming soon.

Yes, it requires the CLI command in 5.9.1 too.

allow_bc_n

Thank you.

It always takes way longer for the cnMaestro team to add ePMP firmware because they have to validate like 8 or 9 different 5.9.1 builds… e1k/e2k (regular and GPS), e3k, e4k, along with the elevate builds, the F300L, and 130 builds, etc.

2 Likes

Looks like 5.9.1 is now up in cnMaestro Cloud!!

image

3 Likes

We are having an issue with 5.9.1 firmware. On ePMP4600. When antenna is set to Omni, the radio does not upgrade. When upgraded on antenna mode sector and try to change after that to Omni , the radio does not respond. this issue was not on 5.9.0 .

Hi, why the CPU Load in the v5.x is the double or triple higher than in v4.xx? it is the new normal load by some function or why?

Hello @Alessio_Garavano and @Ing_Net,

could you PM me techsupport files when your issues are in progress?

Hello, same here all my epmp3000 APs double or Triple CPU load ! Epmp2000 all over the place but same as 4.8v. , watching over cnmaestro !

1 Like

Hello @Makoto,

could you PMP 2-3 techsupports from your radios?
Thank you!

Hi Andrii, there is not an issue, you can see in the post 5.9.0rc13 where i do this question and send a lot of graphics from the cnmaestro showing about this… so my question continue, why is this high cpu load normal now? is the NSS disabled by default using the CPU or what is the cause? can this issue affect the performance, traffic and the lifetime of devices?

I upgraded 3 APs. One was a 4500L on Dec 6th and the other two were 4600 APs on Dec 12/13th. The 4500L had one SM while each 4600 AP has 3 SMs each.

I just noticed that on the 4625 SMs that they all lost around 3-5db of reported RX signal after the upgrade from 5.9.0 while the 4525 SM showed no change.

A downgrade to one of the 4625 SMs did not restore the old RX signal. I am trying an AP downgrade as well to see if RX signal is restored.

So far I am not sure if this is affecting performance or not, but the RX signals and SNRs on all the 4625 SMs are lower than before the upgrade.

I verified that the 4600 APs are still on the same channels and are still operating at full power levels. There was no change.

Was there some change to the 4600/4625 equipment specifically with this FW that could explain this?

1 Like

I can confirm that a downgrade back to 5.9.0 restored the reported RX signal on the SMs.

Hello @terintamel,

yes, there are manipulations with signal level indication and Tx Power settings.
The right way to confirm that everything is ok: match MCS level before and after upgrade.
If it is the same - everything works fine. But in most cases I see it becomes even better. Like + 1-2 stable MCS levels.

I saw your support ticket. We need techsupports before and after to compare. Of course, better if it was done at one time.

I have provided support files from 5.9.0 after I downgraded. I will upgrade back to 5.9.1 in the next day or two and then grab the support files for the ticket.

MCS did not seem to change. It did not improve or decrease, just an RX SNR and RSSI change.

We upgraded two of our F425 links to 5.9.1 and the slaves immediately became inaccessible via web gui or ssh after upgrade. They also stopped responding to snmp entirely, and show offline in cnMaestro. They still respond to ping and are still passing traffic though…what gives? Opened a ticket, but wondering if anybody else has seen this too.

Please describe the network configuration for the management side of the radios. I have a suspicion.

Hello @SBBinc,

could you PM me your support ticket number?