A company has a Mobility Master (MM)-based solution. How does a Mobility Controller (MC) behave if it loses contact with all MM nodes?
A. The MC loses all licenses and cannot support APs or clients.
B. The MC retains its current licenses for 30 days.
C. The MC contacts Aruba Activate and uses the licensing limits defined there.
D. The MC maintains only licenses that have been locally installed on it.
|
Download Printable PDF. VALID exam to help you PASS. |
 |
Correct Answer: B
Correct Answer is B
B
“If a managed device does not receive three consecutive heartbeats from the Mobility Master, it assumes that Mobility Master is down, but continues to use the licenses it received from its Mobility Master license pool. When a managed device is unable to reach a license server for 30 consecutive days, it removes any shared licenses pushed to it from Mobility Master. If the 30-day window has passed and the managed device does not have enough installed licenses for all of its associated APs, the managed device will nonetheless continue to support each AP. However, when an AP reboots and its managed device does not have enough licenses, that AP will not come up.”
https://www.arubanetworks.com/techdocs/ArubaOS_81_Web_Help/Content/LicenseGuide/Multi__Network.htm
Correct answer is B
A Managed Device is Unreachable
Mobility Master sends keepalive heartbeats between the license server and the licensing client controllers every 30 seconds. If Mobility Master fails to receive three consecutive heartbeats from a client, it assumes that the licensing client is down, and that any APs associated with that client are also down or have failed over to another controller. Therefore, Mobility Master adds any licenses used by that client back into the available pool of licenses.
Correct answer is B