Next BUG !!!
This is now a drama, hotspots fly out every 10 minutes !!!
Someone really should be fired!
Next BUG !!!
I understand you, I’m often as angry as you are now with Cambium, but I think your attitude, today, is not helping.
Honestly, I have had exactly 7 months of deteriorating quality with Cambium. Problems reported repeatedly, no one will take them into account. There is no improvement, no consequences. Are you surprised that I have enough?
I have 2 projects to deliver by tomorrow and the hotspots are acting like I’m on the hunt. Once they are once they are gone. There are no logs because you need to clear the cache etc. etc. Where is the limit. Unfortunately, I am STILL forced to do European projects with Cambium. Fortunately, soon
The IP address field for most all of our ePMP SMs is now showing N/A. Seems to be fine for everything else: ePMP APs, 450 APs and SMs and cnPilot.
I came across one ePMP SM displaying the LAN IP instead of the management IP, so I rebooted it through cnMaestro, and it came back up with the correct management IP address.
I am seeing the exact same thing, no IP’s listed for my ePMP SMs. This is awful, needs to be fixed or reverted to previous version fast.
Graphs are broken too? You can clearly see more than 130 users, but showing only 10 in graphs.
Cookies were cleared. Chrome browser.
Just wanted to highlight that we rolled out the fix for below two issues over the weekend (21-22 May):
Guest Client’s Auth Status was shown as 0/1. Now it is back to False/True.
ePMP SM Device’s IP address was shown as N/A intermittently. Now it should show the proper IP address. Please check and let us know.
We have also identified the root cause for the client count graph issue and will be rolling out the fix soon.
I am doing the same since 2018 and can’t get anything. We spent more than 1M US Dollars for the Cambium products but our feature requests and bug fixes are always drop out from their release notes.
Some of bugs are discovered in 2018 and still not solved. I agree their don’t care about it. 100%.
It is also worth adding that the update procedure has been changed and has not been described anywhere. Now all cnPilot reboots before upgrading as written to avoid low memory problems ?!
Before, things like rebooting before the update only happened with the e505, now they all do that.
Additionally, the e505 performs a total of 3 reboots!?!?! because someone in the procedure probably overdid it. Sometimes you write to clients that you are changing something for such and such reason.
Cambium - life is full of surprises;)
In cnMaestro 3.1.0 release the reboot mechanism is added for e505 devices before s/w update. Now all the cnPilot e series devices will be rebooted before s/w update from cnMaestro 3.1.1.
After the last update of cnMaestro, this server (https://eu-w1-s14-75pirxpyd5.cloud.cambiumnetworks.com/) is lagging powerfully. You have to wait several seconds more than once for the browser to establish a connection. System is overloaded?
I have 2 controllers on this machine. On both same, that mean CPU is in high load ??
Thanks to this wonderful new update procedure, devices that are on weaker links or radio links are impossible to update. You have to go and do it manually from the local network because it still crashes timeout after the first restart (devices enter the network after 6-7 minutes). Congratulations Great idea
Is this another issue? We are seeing this on every AP XV-2 with 6.4.1-r15 (doesn’t happen on 6.3.5-r4 - but can’t confirm this just yet), we have PPPoE disabled in configuration. Doesn’t help having alarms that shouldn’t be there in the first place.
cnMaestro Version 3.1.1-r21
Issue is not with the cnmaestro version 3.1.1 but it is with the device build 6.4.1-r15 and has been fixed in upcoming device release 6.4.2.
Did you fix the VLAN support in WiFi?
Because in this 6.4.1 there is also a PPPoE error if more than one SSID network is set on different vlanes
Quietly, secretly, we have already reached version 3.1.1-r46
I guess there were more things than we found on this forum
Updated on-prem to 3.1.1-r8 last week but had to roll back to the prior version today due to APs not connecting to cnMaestro after AP reboot. I understand on-prem releases are delayed due to testing reasons, but if cloud is at version r46 after only a month, maybe Cambium should wait a bit longer before pushing these quick fixes that are clearly not tested. I think most customers would agree stability is more important than feature releases, but maybe Cambium’s banker shareholders are saying otherwise.