PMP450x Release 15.2 is now available

PMP450x Release 15.2 is now available.  It can be downloaded at:

https://support.cambiumnetworks.com/files/pmp450/

2 Likes

Ok question, so upgrading to 15.2 sets all APs to none setting great that works

Then upgrades the SMs to 15.2 they connect

Do we now have to login and switch the SMs to AES or is it safe to just swap the AP to AES?

Because when I go into the sms they are on a grayed out DES setting, so trying to figure out if I have a several thousand settings change in my future or just a quick AP swap and reboot after all upgrades are done across network

Wouldn’t it be best for the SM to just follow the APs encryption setting much like region code? That drop down seems bit redundant as it’s AES or AES in reality no?

And one other question if an AP is still on 15.1.5 on des does that mean if an installer puts 15.2 on an SM it won’t be able to connect since it no longer supports DES

If that’s the case I imagine I should consider upgrading all APs across network before starting to upgrade SMs to avoid issues with installers using newer version or a 15.2 roaming to an alternate color code that isn’t upgraded yet while the upgrade process is ongoing.

This ones not a big issue either way as I imagine it will be a while till 15.2 starts coming from factory.



Also I noticed something that I thought I was told was getting fixed in 15.2, the ifHighSpeed snmp variable is still undefined 1.3.6.1.2.1.31.1.1.1.15� returns empty still

I just tested this, upgraded an AP to 15.2, upgraded all SM's to 15.2. Changed the AP from none to AES. No SM's re-connected. 

Ok so that means its smart enough to turn enc from DES to none but not from defunct-DES to AES automatically. 

Guess then its between cnMaestro to force SM's to change to AES, or a radius configurl to force them to download a config that sets them to security=aes, reboot ap, when sm reasociate they get config and are ready to be moved to AES :S


@CSup wrote:
And one other question if an AP is still on 15.1.5 on des does that mean if an installer puts 15.2 on an SM it won’t be able to connect since it no longer supports DES

If that’s the case I imagine I should consider upgrading all APs across network before starting to upgrade SMs to avoid issues with installers using newer version or a 15.2 roaming to an alternate color code that isn’t upgraded yet while the upgrade process is ongoing.

This ones not a big issue either way as I imagine it will be a while till 15.2 starts coming from factory.



Also I noticed something that I thought I was told was getting fixed in 15.2, the ifHighSpeed snmp variable is still undefined 1.3.6.1.2.1.31.1.1.1.15 returns empty still

Hi CSup,

Yes, If AP is on 15.1.5 and running DES, a SM running 15.2 will not be able to connect to the AP.

Please refer to the following FAQ for more info about upgrade options.

http://community.cambiumnetworks.com/t5/PMP-FAQ/15-2-AES-256-Encryption-FAQ/m-p/85930#M306

ifHighSpeed OID is supported in 15.2. Could you please try again.

 

Best Regards,

Balaji

Thanks your right ifHighSpeed is working, i must have typed the wrong ip to one that wasn't upgraded yet. 

Any idea on the lldp/layer2 neighbor issue?

I was reading the document you linked, so AP with 15.2

New AP Setting NONE will allow DES subscribers to connect with PT

Will subs with AES setting also be allowed to connect with the AP set to none? Is this the same for SM's in 15.1.x and 15.2? 

I notice that the doc also says to upgrade from outside inward, but wouldn't that break the SM's as they wouldn't support DES while the AP is still on DES possibly?


Lastly, if an AP is set to AES, and a SM is set to None/DES, will it be able to authenticate to get the radius downloaduri to get the new config? I ask because we have a lot of radios offline due to disconnection (non-payment, signal issues etc), if they can't then when we switch network to AES those radios will require truck roll to get back online


@CSup wrote:

Thanks your right ifHighSpeed is working, i must have typed the wrong ip to one that wasn't upgraded yet. 

Any idea on the lldp/layer2 neighbor issue? 


I'm sorry. I don't have the answer right now. I'll get back to you on that.

I was reading the document you linked, so AP with 15.2

New AP Setting NONE will allow DES subscribers to connect with PT


When encryption is set to "None", the AP does not care whether SM is running DES or AES.
It will allow both DES and AES SMs to register to it.


@CSup

Will subs with AES setting also be allowed to connect with the AP set to none? Is this the same for SM's in 15.1.x and 15.2? 


Yes, SMs running 15.1.x and 15.2 will register to AP running 15.2, with encryption set to "None".

 Lastly, if an AP is set to AES, and a SM is set to None/DES, will it be able to authenticate to get the radius downloaduri to get the new config? I ask because we have a lot of radios offline due to disconnection (non-payment, signal issues etc), if they can't then when we switch network to AES those radios will require truck roll to get back online


When AP is set to AES, only SMs with AES can register to it. 

Encryption on all the SMs in the sector should be configured to AES, before AP is flipped from "NONE" to AES.

2 Likes

AP PMP 450 i
Firmware 15.2 BETA 4

Upgraded to 15.2 final

AP almost unreachable. Noticed difficulty in navigating the menus. CPU used very low (10%)

Reply from 10.52.0.53: bytes=32 time=1ms TTL=63
Request timed out.
Request timed out.
Reply from 10.52.0.53: bytes=32 time=1278ms TTL=63
Reply from 10.52.0.53: bytes=32 time=2ms TTL=63
Reply from 10.52.0.53: bytes=32 time=2ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Reply from 10.52.0.53: bytes=32 time=1451ms TTL=63
Reply from 10.52.0.53: bytes=32 time=1ms TTL=63

Rebooted. Nothing.

Downgrade to 15.2 BETA 4, ok.

Reply from 10.52.0.53: bytes=32 time=2ms TTL=63
Reply from 10.52.0.53: bytes=32 time=1ms TTL=63
Reply from 10.52.0.53: bytes=32 time=1ms TTL=63
Reply from 10.52.0.53: bytes=32 time=1ms TTL=63
Reply from 10.52.0.53: bytes=32 time=2ms TTL=63
Reply from 10.52.0.53: bytes=32 time=1ms TTL=63


@Tuvix_IT wrote:

AP PMP 450 i
Firmware 15.2 BETA 4

Upgraded to 15.2 final

AP almost unreachable. Noticed difficulty in navigating the menus. CPU used very low (10%)

Reply from 10.52.0.53: bytes=32 time=1ms TTL=63
Request timed out.
Request timed out.
Reply from 10.52.0.53: bytes=32 time=1278ms TTL=63
Reply from 10.52.0.53: bytes=32 time=2ms TTL=63
Reply from 10.52.0.53: bytes=32 time=2ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Reply from 10.52.0.53: bytes=32 time=1451ms TTL=63
Reply from 10.52.0.53: bytes=32 time=1ms TTL=63

Rebooted. Nothing.

Downgrade to 15.2 BETA 4, ok.

Reply from 10.52.0.53: bytes=32 time=2ms TTL=63
Reply from 10.52.0.53: bytes=32 time=1ms TTL=63
Reply from 10.52.0.53: bytes=32 time=1ms TTL=63
Reply from 10.52.0.53: bytes=32 time=1ms TTL=63
Reply from 10.52.0.53: bytes=32 time=2ms TTL=63
Reply from 10.52.0.53: bytes=32 time=1ms TTL=63


This looks like a ethernet problem.
What do you see in Statistics -> ethernet ?

No errors. No event log. Very strange.

EDIT: the reported problem occurs for now only on the  APs "i".


@Tuvix_IT wrote:

AP PMP 450 i
Firmware 15.2 BETA 4

Upgraded to 15.2 final

AP almost unreachable. Noticed difficulty in navigating the menus. CPU used very low (10%)

Reply from 10.52.0.53: bytes=32 time=1ms TTL=63
Request timed out.
Request timed out.
Reply from 10.52.0.53: bytes=32 time=1278ms TTL=63
Reply from 10.52.0.53: bytes=32 time=2ms TTL=63
Reply from 10.52.0.53: bytes=32 time=2ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Reply from 10.52.0.53: bytes=32 time=1451ms TTL=63
Reply from 10.52.0.53: bytes=32 time=1ms TTL=63

Rebooted. Nothing.

Downgrade to 15.2 BETA 4, ok.

Reply from 10.52.0.53: bytes=32 time=2ms TTL=63
Reply from 10.52.0.53: bytes=32 time=1ms TTL=63
Reply from 10.52.0.53: bytes=32 time=1ms TTL=63
Reply from 10.52.0.53: bytes=32 time=1ms TTL=63
Reply from 10.52.0.53: bytes=32 time=2ms TTL=63
Reply from 10.52.0.53: bytes=32 time=1ms TTL=63


Can you please send me the "engineering.cgi" from the AP, to balaji.grandhi@cambiumnetworks.com.

1 Like

Anyone else see this happen on a 450i I haven’t gotten to any i’s yet

Hi, it looks like a problem with the Jumbo Frames. is being analyzed by Cambium.

So if we use jumbo frames should we hold off for a 15.2.1?

This is only an issue if you have a device trying to send frames larger than 1700 bytes into a 450i or 450b device's Ethernet Port.   Those packets wouldn't be being passed anyways, so if you have a device doing this, the best thing to do would be to fix that device and stop it from doing this.  

We updated some logging and handling of these packets and when we see some regular arrival of those, it appears to be that logging and analysis is causing an issue in processing other packets for a tiny bit.   If they are regularly arriving, multiple times per second, it can have a larger impact.  Our analysis of the logs we have seen with this issue were showing some regular arrival of 1800+ byte length packets.

We will address this in 16.0, but the important thing to note regarding Jumbo Frames, is that we only support up to 1700 byte packets, so anything larger than that would be dropped anyways.  It is safe to use frames up to 1700 byte length even with this issue in place for larger packets.

3 Likes

Enable or Disable Max Tx Power not work.

I change Disable Max Tx Power but power 22.

In version 15.1.3 after change it is parameters power changed.

after upgrading a 450m AP and all the SMs attached to that AP via cnMaestro the SMs now display the following red warning at the top of the SM page:

"The encryption setting configured prior to upgrade is no longer supported, radio links are not encrypted.
Apply a supported encryption configuration under Configuration->Security->Airlink Security->Encryption Setting and reboot to remove the above warning."

is ther a way to change this without touching and rebooting every SM?!?!

It’s in the release notes they discontinued DES you have to swap sms to AES once their all changed then enable aes on AP


Or just disable encryption either way your gonna have to reboot sm… that said it’s in the patch notes pretty extensively

yeah i read the notes that said encryption went away but the notes didn't explain that you'd then need to touch and reboot every dang AP and SM after upgrading. :-/

my question is "do i have to touch and reboot every device?"

why doesn't the updater just apply this change?!?!

1 Like