Wireless Access

 View Only
Expand all | Collapse all

Consequences of planned Mobility Master unavailability

This thread has been viewed 20 times
  • 1.  Consequences of planned Mobility Master unavailability

    Posted Apr 14, 2023 09:13 AM

    Hello,

    I'm new into Aruba Wireless technology (I used to work with another vendor solution ;-) ).

    I now have in charge of an Aruba Wireless network containing :
    - 1x MM-VA (Mobility Master Virtual Appliance)
    - 2x MC (controllers Series 70xx)
    - ~80x AP

    My system run ArubaOS 8.

    I have a task to move the MM-VA from one virtualisation hypervisor to another hypervisor (a hot move is not possible with the current infrastructure). This move operation is expected to take 1 hour or so.

    Unfortunatelly, I was not able to find a clear information of the role of the MM for the production system. I found that MM is the single point of configuration for the system, it manages the images and the licenses. But I was not able to make sure that having the MM unavailable for a limited period of time would not have any impact on my users.

    Can anyone in this community confirm that disconnecting the MM would not have impact on :
    - the already connected users?
    - the users trying to connect to the wireless network?
    - the already connected APs?
    - the APs trying to reattach to the network?
    - the already connected MCs (mobility controllers) ?

    If there is already some documentation that describes this (and that I didn't find during my previous searches), I am very open to read it.

    Thank you for the share of experience.

    Regards,
    YG




  • 2.  RE: Consequences of planned Mobility Master unavailability
    Best Answer

    Posted Apr 15, 2023 05:16 PM

    Hi YG,

    Turn off the Mobility Conductor (Master) will not impact production, clients keep online and can authenticate.

    Mobility Conductor responsibility's that will not work when the mobility conductor is down:
    - UCC information
    - Airmatch updates
    - Licensing server (controllers are unlicenced after 30-days no connectivity with conductor)

    Make a flash and configuration backup from the Aruba Mobility Conductor WebGUI before you start.
    Make sure your virtual machine ID isn't changing during migration to the new hypervisor, else your license passphrase will change.
    You can also install a second Mobility Contactor for redundancy, this not required any extra licensing.

    Hope this helps



    ------------------------------
    Marcel Koedijk | MVP Expert 2023 | ACEP | ACMP | ACCP | ACDP | Ekahau ECSE | Not an HPE Employee | Opinions are my own
    ------------------------------