I have three sites geographically separated and L3 connected, each one with one controller. I know I can have site1's APs pointing to site1's controller, and if this controller fails, the APs can fail over to the site2's controller, as indicated with the backup-LMS in the AP system profile.
Now, is possible to have site1's APs pointing to site1's controller as the primary controller, site2's controller as secondary controller is site1's controller fails, and site3's as tertiary controller if site1 and site2's controllers fail? Many thanks in advance.
Unfortunately, there is no way to do this.
@cjoseph wrote:Unfortunately, there is no way to do this.
I forgot to say, but I will also have a MM for managing the three controllers. I guess it is not possible either with a MM. Can you confirm?
It is not possible with an MM.
Controllers do not fail often (the only moving part is typically a fan in the power supply). If you need high availability at a site because you need wireless 24/7 put a second controller there. Failing over to a second site is very disruptive, because all devices will have to request a different ip address (if the device even detects the failover). This is not to mention the slowness of the WAN between sites that would make wireless painful.
Well, the customer will be satisfied with Backup LMS, because controllers do not fail often.
A cluster is two or more controllers at a physical site that are fully redundant.
There is no one member cluster.
Yes, that's right, I might haven't expressed well. The question is:
In my scenario is better to have a cluster of three controllers (L3), or three controllers managed by the MM without forming a cluster? What are the pros and cons of each case?
I read a post (which I can't found now) stating that in some cases is better to have independent controllers managed by the MM instead of creating a cluster.
Reading through your posts and trying to understand the topology I would not recommend a cluster setup between sites.
You will only benefit from the cluster if all members are L2 connected. If they are on different sites, which are L3 connected you will lose most of the benefits of the cluster, like fast failover and so one.
Another point against the cluster across sites might be, that AP's and clients are balanced across all members. This means, that AP's and clients from one site might be connected to a controller on a different site. From my point of view, this is not what you want and something I would never recommend.
If you will have only one controller per site, you should run them as a single controller managed by the MM. As already said, controller failing is very uncommon.
If you start phase two of the project and you get a second controller per site, I would create a two-node cluster per site. And even with this setup, you can let the AP's failover to a cluster on a different site, for the case even the two controllers on the same site fail, at the same time.
hope this makes sense to you.
And it makes a lot of sense! Great explanation! Many thanks :)
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.