IMPORTANT NOTICE
The updated cybersecurity requirements of the European Union Radio Equipment Directive (RED 2014/53/EU) will become mandatory on August 1, 2025. To comply with these changes, firmware version 5.10.2 and later no longer include the default WPA2 key in the configuration. If the default key was previously in use, SMs may fail to reconnect to the AP after the upgrade. We recommend referring to the Cambium Community for the recommended migration steps.
Just FYI, I updated one of our ePMP 3000 sectors that have only 3 subs connected, and at first one of the F300-16ās only had the ability to use a limited amount of frequencies.
20 Mhz was missing 5845-5885
40 Mhz was missing over 2/3ās of the frequencies.
Luckily it was still connected to AP with current frequency of 5200Mhz, so no truck roll necessary. I tried reverting firmware but got an error with something along the lines of āwrong SKUā. I then rebooted the SM and all frequencies came back up and all good for now.
We had this happen on a F300c backhaul which is on 5.10.1 a couple days ago. There was a large storm and a wide area power outage and this particular backhaul went down, we initially assumed it was power, but when logging into the Master side, we could see it only had a handful of channels available, NOT including the one it was configured for - so the Master was in hold off and wasnāt transmitting. I didnāt screenshot or download a support file, I just rebooted the AP, and when it came back up, the full list of all the regular channels were listed as available, and it started broadcasting.
However the slave side did not reconnect - So I configured the AP side to one of the handful of channels which it was previously limited to before the record, save that, and the Slave immediately linked up. I then logged into the slave side and it also just had that same smattering of channels available. I was then able to reboot it, it booted back up with its normal compliment of channels, And I was able to reconfigure the link to its original channel.
Stupidly, I didnāt save a support file from either one of them - We had storm related issues over a large area of our network, so I was in āfix ASAPā mode on everything.
This linkās been working fine since, but it was a strange thing.
Iāve seen one a few videos they speak of a base being loaded with 40 subs, Are you saying its performance will be massively affected if say we do 80 or 100? One would assume mu-mimu negates this affect.
Hi Guys, we have 43 subs running flexible with mu mimo was rebooting 5 times a day turned mu mimo off and its stable. Just a heads up. I will be testing fixed frame to see how that goes as i know they have mentioned that it wasnāt stable on flexible. Just needed better latency.
Unfortunately I donāt, I can re enable it and wait for the first reboot but clients were getting a but frustrated. I had assumed the reboots were erasing the logs.
ePTP mode on 4625 is having some stability issues- Iām still seeing occasional session drops (1x/month or so) each on 3-4 PTP links, all in very low interference environments. Iāve opened ticket 459820 regarding this with troubleshooting files.
EU is so dumb. My bench onboarding process requires that default key since EPMP wont connect to cnmaestro through the ethernet port. I could do 9 radios at a time on my rig. tell EU to kick rocks
The Default key is still available on the AP in 5.10.1 so as a work around, you could leave your onboarding AP on 5.10.1 for now, until thereās a better solution
But its not present in the SM, thats the problem. If theres no default key in the SM the onboarding AP I can set to whatever I want and an out of box SM wont connect to it, we will have to log into the SM to set it, defeating the zerotouch process
Oh, OK, sorry. I havenāt moved past 5.10.1 yet, but I thought I read it was only erased in the APs. My bad - please resume your regular scheduled programming now.
