Wireless Access

     I fully understand that in a AOS 8.x environment, where a Mobility Master is enabled with a cluster or multiple cluster of Managed Devices (Controllers), the AP must have their initial DNS "aruba-master" or other method pointed to one of the MD in the cluster, and that only MD can terminate AP's.  

     In a Master-Local AOS 8.1 environment can the Master Controller still terminate AP's?  I have many clients with only two controllers and this solution still makes sense.  I understand some features are only available via AOS 8.x in MM mode with clusters, but those features do not outweigh the simple two controller solution.  I have not been able to find a definitive answer in the release notes or configuration guide concerning AOS 8.1 Master-Local Mode.   

Yes , you can still use the Master\Local design scenario

Victor,

 

     Thank you for the quick reply.  Do you have documentation from Aruba?  I'd love to have a reference.

      Thanks again.

 

Jamie

 

OK. A 8.x Mobility Master cannot terminate any APs. AP adoption will also not work meaning that your AP discovery (Option 43 or DNS) must point to a manged device under the MM. 

 

As for migration there are two options:

 

1. Do not use a mobility master (VM or HW) and use "master controller mode" which delivers the new UI and some of the new features but allows you to upgrade and not have to deploy a new appliance. NOTE that you cannot terminate APs on a controller in Master Controller Mode. 

 

2. Use the MM and gain all the benefits and get a two-node cluster with Live Upgrade, Seamless Failovers, and User/AP load balancing. Possible expansions into DMZ/RAP controllers, Branch networks with a branch gateway, etc...are also possible.

 

So, yes, there is another appliance needed but there are several benefits in deploying one. Keep in mind, we have also released a MM-50 SKU for smaller/lab deployments as well. 

Seth,

     Thank you for looking at this.  In this case, its not a question about Mobility Master 8.x solutions.  This partains to only the Master-Local AOS 8.1 solution.  According to Victor, the first response, Master-Local 8.1 Mode configurations allow for direct AP termination on the Master Controller.  

     I asked Victor for documenation.  I did not see the ability in the AOS 8.1 Release Notes or User Guide about Master-Local Controller Mode specifically terminating AP's.  If you have that documentation, please share.

     Thank you!

 

 

My previous post is not correct , please use Seth answer

I will re-confirm this. In 8.x, NO AP termination of any sort is allowed on a Mobility Master (HW or VM) nor a controller acting in Master Controller Mode. 

 

This includes AP discovery and provisioning meaning that APs cannot terminate to any "master" just to be provisioned elsewhere either. 

<EDIT>

I add some questions regarding AOS 8.x

 

Not being able to terminate APs to a Master in AOS 8.x.

Does this only apply to a Master-Local scenario (Master Controller Mode)?

 

What about Master Active - Master Standby?

Let's say you have two controllers running 8.x, can you run them as Master Active - Master Standby and terminate APs on the Master?

Or is it impossible to build redundancy with two controller running 8.x without a Mobility Master?

 

 

No. No APs can terminate on a mobility master or a controller running master controller mode. Redundancy could be somewhat achieved with two standalone controllers but there are several benefits you'd lose

How do you achieve redundancy with two standalone controllers?

 

If running a Mobility Master then I need atleast two controllers to achieve redundancy in AOS 8?

 

Regarding not being able to terminate APs on a controller running Master Controller Mode, is this by design or something that will work in future updates?

Hi,

 

I did have the same questions as you. What I have found is that you have to stick with 6.x if you want to do a Master-local style of deployment and terminate APs on a Master.

 

Regards

Philip

anyone have answer for this? 

we have 2 datazone controller that is running 2 standalone mode but the AP doesnt failvover to the standby standalone controller even LMS IP and HA group configured

This sounds like a different issue than the one the thread originally discussed. Please start a new thread so we can walk through why your APs are not detecting the primary LMS failure and reverting to the backup LMS.

Will Aruba allow AP termination on virtual controller AOS8.X anytime soon or ever?

 

Regards Nick

 

---

wrote:

Will Aruba allow AP termination on virtual controller AOS8.X anytime soon or ever?

 

Regards Nick

 

---

it is only impossible with Mobility Master ! it is possible with VMC (Virtual Mobility Controller)