Your not wrong, as I personally think the SM should just always be set to AES after upgraded to 15.2 and rebooted, as the SM will connect regardless of it's setting if the AP is set to PT and the SM is set to AES it connects... So why does it make sense to leave the SM on the defunct-DES setting which is operating as PT.
The drop-down can literally go away just make the radio AutoSelect AES/PT based on the AP it connects to as it already does, instead of booting up in defunct-des which technically is PT.
With DES gone the whole reason for having the setting is now useless, it's either AES128 or the ap has AES256 and it uses that instead to my knowledge, and theirs 0 performance impact so shouldn't the basic setting just be AES
I'd like to say that I'm also disappointed in how Cambium handled the whole DES to AES conversion... it just makes sense that if you upgrade to 15.2 it should automatically set the SM's and then the AP's to AES. It's going to be so much work and additional downtime for us to convert. I'm really dreading moving to 15.2 and beyond because of this.
thanks Matt, I really don't want to reboot everything twice just to do an upgrade. plus there's no way to easily ensure that everything was updated AND set to the right settings.
What does this mean for a 430 series SM that is connected to a 450series AP? Will the 430 series SM no longer connect as it doesn't have the option of AES? will 15.2 give it this option? or am I forced to stay on older firmware from this point till I can afford to swap out 500+ SMs to 450 series?
Trust me, we are working to update all legacy equipment, but this is far from happening overnight and likely not within the year.
After upgrading to 15.2, we recived multiple complaints from end-users stating that some websites would not load or took very long to load, some even had issues getting to O365. This only appeared apparnet on SMs running as routers with the pppoe client enabled. We then rolled back all APs to the previous version but kept all SMs on 15.2 and this resolved all issues and internet performace returned to normal.
We have not seen this behavior at all... I will ask if this can be replicated somehow. If possible, should this occur again (or if you're willing to try to go to 15.2 on the AP again), can you send a CNUT capture to us?
This happened with AP 450, 450i upgraded to 15.2, NOT with 450m. Some customers notice a almost zero donwload or decreasing performance over the time.
Downgrading to 15.1.5 (leaving SM to 15.2) on the AP everithing was fine. With a particular customer using our connection to streaming video the problem is easy to note (see image). It was always a perfect download until we upgrade his AP (450i), as you can see in the screenshot. We solved this issue going back to 15.1.5 for all our AP 450, 450i (90).
We upgraded all the APs (12 total) at a tower to 15.2 in order to switch from using Canopy Sync to Cambium Sync. That part went fine.
But I notice in the Sessions list we are getting a bunch of IDLE sessions in red with no customer name, just the LUID. These SMs are active on an adjacent sector, but I have never seen this behavior before, where IDLE sessions only have the LUID, not a customer name. Except occasionally with a very marginal link that can't complete registration.
We haven't been upgrading the SMs to 15.2 yet, kind of scared about the whole AES/DES fiasco. We do still have some 430 SMs. We are running with no encryption. But the encryption issue and the 430 SMs seem unrelated to the strange IDLE sessions with no customer name.
Do you have the sms set with alternate color codes maybe during reboot they roamed to that sector and then roamed back to the other sector when it was rebooted
The session list is now a bit better as they maintain Luids and offline time as a side effect if you have multicolorcode sms their a bit more visible than they were on the AP before.
the keeping luids persistent is a change that takes some getting used to but then it’s a bit more consistent
In my experience, Canopy sync is causing constant SM disconnects on 450i / 450m APs running 15.1.3 or higher so that might be the reason. Cambium sync resolves the issue...
Thanks, CSup. What you said about the LUID persistence is likely what is being seen here.
Many customers had asked for a change such that when an AP is rebooted, the LUIDs given to registering SMs be persistent across reboots, and this was introduced in 15.2. If you no longer want to see those, you can press the “Clear Idle Sessions” button on the AP and they’ll go away.
