A Mobility Controller (MC) runs ArubaOS 8. What is a valid reason for an administrator to set the MC to master-local mode?
A Mobility Controller (MC) runs ArubaOS 8. What is a valid reason for an administrator to set the MC to master-local mode?
A valid reason for an administrator to set the Mobility Controller (MC) to master-local mode in an ArubaOS 8 environment would be if the company already has a partially hierarchical deployment based on the 6.x code and wants to keep the current architecture. This setup allows for continuity in the infrastructure without the need for major changes. This ensures legacy systems and configurations are maintained while upgrading to the newer version of ArubaOS.
B is correct. The answer states that they want to keep their current architecture, NOT import their 6.X configuration. D is incorrect because not all MC configuration can set from a single location, interface settings for instance cannot be set in the Master-Local mode.
A “Master-Local” setup is used to migrate from AOS 6.x to AOS 8.x, without changes to existing infrastructure and topology. You can use HPE Aruba 72xx and 70xx for this Master-Local scenario (Figure 2-7). **This is the reference from Aruba Study Guide** **Agreed with B.
Standalone wi ll set up one MC independently while Managed by a Master Controller will set up talk to a Master MC in a master-local mode. Managed by a Mobility master will setup this MC to communicate with the VM mobility master. D is correct.
Should be D. B is wrong as 6.x will not live together with 8.x
answer is D