New update from this morning… I installed a new on-prem instance and tried to connect it with the Anchor created yesterday (before 1st October) — no luck. I created a new Anchor today on 1st Octpber — still no luck. For both accounts, cnMaestro replied with an ‘Ownership Conflict’ error.
However, it’s not a real conflict since these are completely fresh, brand-new Anchor accounts.
What now?
Your first on-prem instance might already be tied to the original or first Anchor account you created.
Login to your cloud.cambiumnetworks.com account, select the anchor tenant - and delete the on-prem instance.
You’d have to re-associate the on-prem instance to the new Anchor account,etc.
There are some news on when the stand alone on-premise version will be relased? It will be an X version, right?
Any updates or news @Cambium Administration ?
I think we all [collectively] need to email the restructuring team and request more updates. Been a week, perhaps everyone has breathing room now that cnMaestro stay-alive date was pushed to EoM October. Still very uncomfortable.
Damn @Simon_King , I hope everything works out for you. You’ve always been super helpful in here.
Thank you! To be clear, I’m now an Airspan employee, so I’m in a better position than many in Cambium.
I do hope to either transfer this community to Airspan, or at least create a new site and populate it with the categories for the products that Airspan now own. I’m not sure about the legality of carrying across the other categories, but I will preserve them if at all possible.
I couldn’t agree more
WiFi Done Right LLC is a team of former Cambium employees with experience in technical training and enablement, support, professional services, and solutions architecture. We have worked closely with customers using cnMaestro, Cambium Enterprise Wi-Fi, switching, and related solutions. References from former Cambium employees, including sales, services and engineering, are available upon request.
We have already successfully assisted with cnMaestro migrations for organizations of various sizes, including large environments.
If your organization still needs to prepare for this transition and/or ongoing professional services/support, we would be happy to schedule a brief call to discuss your current environment and what migration and/or services would be the right fit for your company. You can reach us at support@wi-fidoneright.com .
I have two instances of cnmaestro running. I was able to upgrade one to the most recent version 6.0.0-r11, first by applying the 6.0.0-r6 update and then moving on to 6.0.0-r11. The second is stuck on 5.2.0-r3. I am able to apply the 6.0.0-r6 version, but then that machine stops recording polling. Also, if I try to apply the 6.0.0-r11 update, it says, “There is software update in progress. Please try after the job is complete.” Restarting the machine doesn’t clear the message. Does anyone have any similar issues updating?
Hi all,
Sharing what we observed on our cnMaestro On-Premises servers (6.0.0-r6, self-hosted, thousands of Wi-Fi APs), in case others are seeing the same.
What we noticed
The Cloud Anchor stopped answering, but the connection stays up.
Login hangs, the APs don’t.
Cloud calls hold the license lock for 2 minutes.
The broker slowly leaks Redis connections.
Other side effects.
What helped us
Open questions for the community
Thanks!
Yes, We are experiencing this today. I can say there was delays in the web interface on Friday for sure, so I would say we experienced the exact same thing.
We had some luck moving some devices still from the cloud, but anything that is in an on-prem controller is locked in. And the instance seems to not be getting subscription information. When we log into the Anchor account, it still sees the on-prem controller as online.
We literally have one more device to use that we needed to delay for a customer requested reason…
Hi all,
We are an integrator/operator supporting the Wi-Fi networks of more than 250 hotels, with thousands of Cambium APs. We are responsible for keeping those networks running every day, and right now we feel very limited.
We recently migrated our accounts from cnMaestro Cloud to cnMaestro On-Premises (6.0.0) hosted in our own AWS, following Cambium’s recommendation to move to on-premises. Our customers now want to move to a local instance, and that is where the problem appears:
1. On-Premises still depends on an Anchor account.
2. We have unregistered stock and backup devices.
Why this matters to us
What we are asking Cambium (or whoever now owns responsibility for cnMaestro)
We believe Cambium needs to help us finish this transition so we can keep supporting these networks.
If other companies are in the same situation, let’s gather our cases in this thread to make a joint request.
Thank you.
Confirmed, we are seeing this same behavior in our on-prem instances.
Hello,
I have provisioned cnMaestro on-prem, created the anchor account, and cloud and on-prem are now connected.
I understand that we can export the list of devices and profiles, then import them on-prem.
Am I able to access/manage form both portals?
Did you follow any specific guide to get to this point? I would suspect you cannot manage from both portals because the device needs to be migrated from Cloud to On-Prem
Same here, adding our case to the list.
We’re a WISP in Catalonia (Spain), roughly 1,400 Cambium devices, mostly ePMP plus some cnPilot/XV Wi-Fi for municipalities and campsites. We moved everything from cloud to two cnMaestro On-Prem 6.0.0-r11 instances (Essentials, no X) on our own Proxmox at the end of September.
We’re seeing exactly the same since Oct 2. On the first instance it started around 21:05 UTC on the 2nd, on the second one on the 4th. The connection to the Anchor stays up and the instances show “Online” in the anchor tenant, but every license sync times out (“Unable to get instance state: Request timed out”) and both instances are now in GRACE_PERIOD_CLOUD_SYNC_FAIL.
One side effect others might be hitting without realising: after a while the web UI stopped loading and nobody could log in, not even with a freshly created user. The password check passes, but POST /cn-srv/login and /cn-srv/mon8zn/features-config hang for 60 s and time out. The mon8zn broker gets stuck waiting for the Anchor and its RabbitMQ queue (mon8znrpc.do) fills up with unacked messages. Restarting just that service brings the UI back straight away without touching the devices:
sudo systemctl restart cnmaestro-mon8zn-broker
It keeps coming back, so we now run a small cron that restarts it only when that queue has pending messages. Device management itself (monitoring, config, jobs) keeps working the whole time.
For what it’s worth, claims were still going through for us on Oct 3 (we onboarded a replacement ePMP by its MSN), so if you have stock or spares it might be worth claiming them while that still works.
Like the others, what worries us most is the grace period. Our instances report gracePeriodDays 2160h (90 days) and invalidDevicesExpTimeInHr 2160h, and nobody has said what happens to already onboarded devices when that runs out. A clear answer on that, and a date for the on-prem build without the Anchor dependency, would really help.
Same here, managing EPMP and PMP450 devices. Login stalls, I have a large assumption that I’ll find the same problem.
Same problem here with CnMaestro OnPremise and I still have a lot of AP to migrate.
We are also having login issues with our on-prem instance. Not totally sure if it is the same as the above reports, but based on the timing it seems likely that it is the same problem. Login just hangs.
Our instance finally let me in after waiting about 20 minutes. Anyone else have success now as well?