Guidance for cnMaestro Enterprise Customers - (updated) 24 Sep 2026

Products cnMaestro
21

So with that, does it mean we can manually onboard cambium devices, ie epmp SM, onto the on-premise?

22

Release an unlimited X key (no time limits, unlimited devices). We paid for service and support, you run off with the money. On top v6 on prem is half baked.

Give us X in full.

23

I agree with this. I was trying to close my eyes and plug my ears regarding… but yes - we’ve paid for 5-years of cnMaestro X and even for some 5-year CCAV.

24

I Have some 4600’s and 4625’s, never been connected to cnmaestro, do I need to worry about this too or is only if they have been connected to cnmaestro? Thanks

25

Hey Joel, do you or does anyone else know if we can setup 1 on-premise instance in AWS and connect multiple customers or sites to this instance ?

26

No real solid answers… it all comes down to if they remove the cloud dependency/anchor when cloud maestro goes down Oct 1, then you should be able to onboard the devices to your on-prem, but I could be completely wrong. All I know is that cloud based or on prem base cnMaestro both rely on the cloud/anchor… so no cloud/anchor both are useless. I am not wasting time on maestro anymore and im going to setup VM on a machine and run LibrerNMS and get all my devices using SMNP and at least I can setup to have monitoring and know if I have a radio down or eth port down etc. Best of luck to everyone.

27

You can make it multi-customer, but without Maestro X - licenses, you lose managed accounts…
They’re basically wording it as if each customer is on their own.. Forgetting about MSP’s and service providers…

AWS and Azure will be costly given the VM requirements, but necessary evil right now

28

Here is a question for @KumarK or @Fedor and or anyone at cambium.

How do we solve for chicken/egg scenerio where we do NOT have remote connection to customer sites, or remote management of their networks - IT provider / MSP who only had Cambium AP’s provisioned.

The config persists reboots which will have the original cloud.cambiumnetworks.com remote-url configued…

How do you expect us to make these devices point to a new on-prem controller? It would take a truck roll / service call… at that point we fuc&*ing RIP them out and replace. For F sakes.

I just ran into this scenerio and its not cool, as the remote CLI tools do not let you remotely change the config.

Steps taken:
Staged new AP at on-prem controller
Claimed at new controller via device serial
Removed from cloud tenant
Device does not check-in at new controller – because access point config has hard coded pointer… would require a factory reset and manual config.

29

Hi all.

When creating an anchor account, does the cambiumID need to be the same or different to my existing CambiumID?

When I try to create an anchor account with my existing CambiumID it tells me that the Cambium ID is already mapped?

Any clarification from someone who has created an anchor account would be appreciated.

Thanks Dennis

30

Yes, you do not have to do a factory default. What I have done and his work successfully thus far is that I delete the device from the device list in the cloud and then I adopt or prove it on the on Prim but when you move it to your switch group it must go into the switch group that you exported and imported from cloud to premise so that everything works the same. The only problem you’ll have if any is if you have individual switch ports configured, you’ll have to reconfigure those manually post import or post approval from the on boarding page

31

Can devices still be managed onsite by logging in locally, or will that be gone once cloud goes?

32

You need to create another cambium ID for the Anchor, I have done it.

33

100% this. its the API i want/need more anything

34

My APs still can’t be onboarded in the on-premises controller.

I’ve followed the guide so far.

  • Set up the On-Prem Controller with a public IP/Hostname
  • Created a new Cambium ID in the cloud as an anchor
  • Connected the anchor to the On-Prem controller
  • Onboarding the AP to On-Prem by by entering the On-Prem hostname in the “Remote Management” section of the AP
  • The AP is shown as online in the On-Prem controller onboarding page
  • Configured and approved the AP during onboarding page
  • However, the AP isn’t configuring itself and shows “Waiting for Subscription”

I tried completely reinstalling the local controller. I tested it with an XE3-4 and an E410. I also tried resetting the AP to factory defaults and using different firmware.

What am I doing wrong?

35

I have a question about licensing with cnMaestro on prem. We have some clients with a 3 year license for the AP that enables cnMaestroX on prem and we use monitoring via restAPI that is only available with cnMaestroX, after 3 years we will be able to buy another license or cnMaestroX become cnMaestro and then lose all the monitoring via restAPI?

Thank you

36

Same problem

Waiting for subscription

37

The onboarding/dhcp guide for onpremises does not mention wi-fi 6e devices like the Xe3-4

38

I also tried it with an E410

39

Thank you for all of this so far. I had already gotten most of this done prior to this guides release and have been working with colleagues at other sites to do the same.

The only thing we were not aware of is the DHCP options for onboarding. Whilst I can easily test singular devices for how long it takes, I can’t test in bulk without firing up new vlans/networks.

So does anyone know how long we can expect it to take to onboard via the DHCP options please? I assume we’d need to reboot the devices for them to pick that up, and once they’re removed from the cloud controller the best way to achieve that would probably be by removing power from the switch. This also means we can do area by area, but not in bulk due to the AP’s automatic update/reboot procedures overnight and they’ll pick up the following morning.

So to confirm, I believe the procedure would be for minimum downtime (and please correct me if wrong!):

  • Export inventory of devices (in our case all X7 35/55 APs) with serial numbers etc
  • Add serial numbers to onboarding section of on-premise controller
  • Delete devices from cloud controller
  • Add DHCP options in scope pointing to on-prem controller
  • Reboot APs via network switches
  • APs appear in onboarding on on-prem controller - approve devices, move to relevant site(s) & AP group(s)

Any clarification/confirmation absolutely gratefully appreciated :slight_smile:

40

Apologies, this may be a silly question but where do i find the Onboarding Key when generating a new Anchor Account ? Assuming the new Cambium ID needs to be a new one different to our exiting cnMaestroX cloud ID?