An architect plans to deploy a Mobility Controller (MC) at one building in subnet 10.23.01.0/24 and another MC in another building in subnet 10.44.12.0/24. The
MCs need to provide redundancy for each other. What must the architect take into account in the redundancy plan?
Each Mobility Controller (MC) can be the backup for the other's Access Points (APs) by using the Learning Management System (LMS) and backup LMS settings. The MCs do not have to be in the same subnet for redundancy at this level. However, they cannot be in a cluster together if they are in different subnets, as clustering requires either layer 2 or layer 3 connections with full feature functionality typically requiring layer 2.
C- actually is the most correct in this scenario... as "Clusters can be formed over a layer 2 or a layer 3 network" but with reduced features as mentioned... so although D is possible to have LMS and backup LMS standalone MCs.. it mentioned that cluster is not possible..so this is not 100% accurate... -- must admit misleading question as it also fails to mention if there is an MM as this is required for clustering..
Correct answer is C - For statefull failover the cluster needs to be layer 2 connected (page294) That make D wrong because you can have a layer 3 connected cluster when its not receive all vlan probes form the other controller.
C seems best answer here. Because Aruba support both L2 and L3 cluster of MC, but stateful failover supported in L2 cluster scenario only. Reference: https://www.arubanetworks.com/techdocs/ArubaOS_83_Web_Help/Content/ArubaFrameStyles/Cluster/cluster_overv.htm
The Clustering feature is only available in deployments with a Mobility Master (MM). [Aruba Networks] No mention of an MM here so can't have a cluster; therefore, D must be right? A wrong - because they can be backup LMS for each other. B wrong - Can't have VRRP as they are in different subnets C wrong - No MM so no cluster possible D is right.
This question is about redundancy not resiliency
Correct answer is A
Sorry, D*
D is correct - we cannot use vrrp since subnets are different ..cluster needs to be on same L2 subnet
Starting from ArubaOS 8.0.0.0, an AP can fail over between clusters. Redundancy across geographically separated data centers are supported. An AP terminates on an AAC in a cluster. If a member in the cluster fails, the AP will fails over to the S-AAC in the same cluster. If the AP is unable to establish communication with any of the members in the first cluster, then it terminates on another cluster setup in the backup data center. It terminates on another cluster only if the other cluster member IP is provided in the AP system profile as backup LMS. For example, a cluster with four managed devices is deployed in the West Coast data center. Similarly, a cluster with four managed devices is deployed in the East Coast data center. An AP is configured to have a primary termination on the West Coast data center and backup termination on the East Coast data center. If a managed device fails in the West Coast data center, then the AAC moves to another managed device in the same data center. However, if the entire West Coast data center is inaccessible to the AP, then it fails over to the East Coast data center.
This requires a cluster, no MM, no cluster.
It is C
D is right