PMP450x Release 16.0.0.1 is now available. It can be downloaded at:
1 Like
Installed, for now everything works regularly
2 Likes
Were there any changes from 16.0.0.1(Build Beta-2) to 16.0.0.1 Release. Wanting to know if I should update the AP/SM's that we currently running on the Beta?
Thanks,
Jason
@Cambium_DaveS wrote:PMP450x Release 16.0.0.1 is now available. It can be downloaded at:
https://support.cambiumnetworks.com/files/pmp450/
Can you please upload this to cloud version of cnMaestro and make it the default firmware image? Thanks!
The following fixes were introduced into 16.0.0.1 official from Beta-2:
• CPY-15463: The fix properly terminates a failed AAA Re-authentication. Prior to this fix, SM software would leave the SM in a state where it would struggle to lock onto the beacon and re-register. This is an SM fix.
• CPY-15460: A cnMaestro device agent fix for occasional issues with MPU violations seen on SMs (which would cause them to briefly reboot then register). This is an SM fix.
• CPY-15468: Fixes an issue where SM-initiated link test would occasionally show a 0 Mbit DL result. This is an SM fix.
• MUMIMO-3515: Warning added to the field_diags collection page to suggest users be patient and not navigate away from the page before collection has finished. Impacts only 450m AP’s.
2 Likes
Awesome thank you! @cambium_Daves
To use mu-mimo in upload I have to upgrade the cpes too?
The cnMaestro Cloud is updated with 16.0.0.1
I have been looking through the notes since 15.2 in regards to this issue,
CPY-14742 - "IPv4 data is blocked when configuration file is loaded on PMP450 SM with Protocol filtering enabled. To workaround this issue, select some filters randomly, in Configuration -> Protocol page, undo the changes, save and reboot the SM."
I have not been able to find any problem corrected entry for it in following versions, is this confirmed to work in 16.0.0.1? Also the IPV6 filtering was broken in the same way even before 15.2.
I set initial configurations via config file with protocol filtering so it is kind of important that this works.
@RK wrote:I have been looking through the notes since 15.2 in regards to this issue,
CPY-14742 - "IPv4 data is blocked when configuration file is loaded on PMP450 SM with Protocol filtering enabled. To workaround this issue, select some filters randomly, in Configuration -> Protocol page, undo the changes, save and reboot the SM."
I have not been able to find any problem corrected entry for it in following versions, is this confirmed to work in 16.0.0.1? Also the IPV6 filtering was broken in the same way even before 15.2.
I set initial configurations via config file with protocol filtering so it is kind of important that this works.
Hi RK,
I've checked the JIRA and it is marked as resolved (and digging further a route cause was found and fix applied).
So it should be good.
Subi should be able to provide more details if you needed as he fixed it.
best regards,
Andy.
Hello Dave,
is the CPY-15463 fix related to SM stuck in "connecting status" we sometimes face since years?
I opened this post: http://community.cambiumnetworks.com/t5/PMP-450/Pppoe-sometimes-stuck-in-connecting-state-after-connectivity/m-p/77704
SM session log shows this messages during those events:
Kind regards
Rocco
Has anyone seen any improvements in the frame utilization with this firmware on a PMP-450m (compared to 15.2.1)? We have a couple of PMP-450m APs in our network that appear to be reaching capacity and we are trying to understand if a firmware upgrade would be beneficial.
Nothing noticable. I happened to put it on one that reaches 90% utilization at peak and it's utilization graph looks unchanged.
Granted I only added the SMs for that unit to my initial test and updated them today so it's not exactly the most comprehensive test yet.
Will subs running 15.0.x code link to the medusas running this level?
@snorthway wrote:Will subs running 15.0.x code link to the medusas running this level?
They should do (I just ran 15.0.3 on 450 SM to 16.0.0.1 on 450m AP in the lab to check).
UL MU-MIMO will not work and it may bring down sector performance as a whole though, so not recommended in the long term.
If you have a more complicated setup with radius, QoS, AES etc there may be incompatibilities I haven't come across.
best regards,
Andy.
@mgonzales wrote:Has anyone seen any improvements in the frame utilization with this firmware on a PMP-450m (compared to 15.2.1)? We have a couple of PMP-450m APs in our network that appear to be reaching capacity and we are trying to understand if a firmware upgrade would be beneficial.
Hi mgonzales,
The frame utilisation in the DL will be similar to previous releases. This release has UL MU-MIMO so improvements will be seen in the UL direction. This can help with TCP traffic (as we can do the TCP ack for several SMs in one slot) and you could change the percentage DL setting in the configuration to a bigger number as the UL is now more efficient and shouldn't need as many slots.
Hope that's clear.
best regards,
Andy.
We are currently running 15.1.3 on everything. Is it safe to upgrade directly to 16.0.0.1?
@MosesTechNW wrote:
We are currently running 15.1.3 on everything. Is it safe to upgrade directly to 16.0.0.1?
Before you do so, I would recommend reading the upgrade notes for 15.2, as one of the major changes between 15.1.3 and 15.2 was the obsolescence of DES encryption, which is no longer available. If you have any devices using DES encryption (or are using encrypted links in general, just to be safe) you'll want to read the 15.2 AES 256 Encryption FAQ. I would also recommend reading the release notes for both 15.2 and 16.0 before upgrading for any other potential changes that may effect your particular configurations.
Other than that, interop between 15.1.3 and 16.0.0.1 should be fine, but the changes mentioned above will break your links, and need to be carefully planned.
Any news on 16.0.0.2 with the improvements that were mentioned elsewhere? Trying to avoid doing multiple updates to the network in short timeframe, and from what i heard a few nagging things were planned to fix in 16.0.0.2
2 Likes