Wireless Access

Hello, 

I'm planning to deploy two virtual controllers, which will be managed by a Mobility Conductor.
For the initial setup, should these controllers be configured in Standalone mode or MCR (Mobility Controller Role) mode?

If there is any official documentation or reference available regarding this configuration, I would appreciate it if you could share it.

Thank you in advance. 

Kayvan

Hello Kayvan,

When setting up virtual controllers that will be managed by a Mobility Conductor, you should configure them in MCR (Mobility Controller Role) mode. This is the recommended and supported approach from Aruba, as it allows your controllers to be centrally managed, clustered, and benefit from features like redundancy, configuration sync, and seamless upgrades. Standalone mode is only intended for controllers that will not be managed by a Mobility Conductor.

The process for deploying in MCR mode is well documented in the ArubaOS 8.11.1.0 Virtual Appliance Installation Guide, which I highly recommend reviewing. It covers the setup of both Mobility Conductor and Mobility Controller virtual appliances and explains their roles in a managed deployment.

There's also a helpful community discussion that highlights the differences between Mobility Conductor-managed (MCR) and standalone configurations, which you might find valuable: community discussion link.

For some real-world setup tips, you might want to check out this practical blog post: 

wifiwizardofoz.com setup guide.

If you have any further questions or need guidance during your deployment, feel free to reach out. Wishing you a smooth and successful setup.

If you are wanting to use the MCR then you are required to setup the controller as a managed device.

https://arubanetworking.hpe.com/techdocs/ArubaOS_8.12.0_Web_Help/Content/gsg/init-set-ser-prt.htm

Thank you so much for your help