The MCR (Mobility Conductor) allows first and foremost the ability to utilize centralized configuration that can be applied to multiple Managed Devices (MD, the controllers that are being managed by the MCR). There are several features, like Clusters and Live Upgrade, that require that an MCR be used for management.
If you have no need for the features and functionality of the MCR then you can definitely run a controller in 'Standalone' mode, and this is documented in the User Guide.
------------------------------
Carson Hulcher, ACEX#110
------------------------------
Original Message:
Sent: Feb 16, 2023 11:13 AM
From: Nigar
Subject: Difference between Mobility Master and Mobility controller
Hi FerC,
Thanks for your response.
As you said, we can push the configuration from Mobility Master to Mobility Controller so it means MM must required for Aruba setup and we can't use only MC.
If we can use MC without MM so what is the benefit of MM.
Original Message:
Sent: Feb 14, 2023 11:44 AM
From: FerC
Subject: Difference between Mobility Master and Mobility controller
Hi
The Mobility Master (Changed to Mobility Conductor) is an appliance where you can push the config to the controllers. Mobility conductors cannot terminate APs. As a Dustin said, you can enable a many features when you use a Mobility Conductor. Ej. Airmatch, cluster active-active, live upgrades, etc.
The Mobility Controllers terminate the APs and obtain the config from Mobility Conductor (if the controllers are associated with it). In other case can work as a standalone controller.
Original Message:
Sent: Feb 12, 2023 11:22 AM
From: Nigar
Subject: Difference between Mobility Master and Mobility controller
Hi folks,
I am learning Aruba 8.0 WLC, I am confused with Mobility Master and Mobility controller, I have go through available documents but still not clear the purpose of mobility master.
Can someone please explain here.
Thanks,
M. Nigar Khan