Wireless Access

 View Only

  • 1.  Move mobility master to another datacenter

    Posted Apr 06, 2022 04:58 PM
    Good afternoon, 

    I have a virtual MM in one datacenter that I would like to move it to another datacenter, also i have a physical controller in each office.
    I am between two options to accomplish this work as following: 

    Option one:
    - change the MM IP address in all the controllers in the offices.
    - backup the VM and move it to the other data center
    - re-ip it and route the FW roles to point the new IP address.

    Option two: 
    - Backup the MM configuration.
    - Build a new MM in the other datacenter 
    - change the MM IP address in all the controllers in the offices.
    - recover the configuration in the new MM.

    Does any of these options make sense to the experts in this community?
    is there any preferred option?
    do i need to put a TAC ticket to have an engineer online during the migration time?
    suggestions and advises are always appreciated

    Thank you, 
    Husam

    ------------------------------
    Husam Yaqoob
    ------------------------------


  • 2.  RE: Move mobility master to another datacenter

    Posted Apr 06, 2022 05:54 PM
    Or you could do this:  https://www.arubanetworks.com/techdocs/ArubaOS_8.9.0_Web_Help/Content/arubaos-solutions/vrrp/conf-stby-mm-l3red.htm

    You should put in a tac ticket for advice and to be available during the migration, but the method above could make it less painful.  Ask TAC if that is an option.

    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
    ------------------------------

    Original Message


  • 3.  RE: Move mobility master to another datacenter

    Posted Apr 07, 2022 07:41 AM
    Just remember that if you do change the IP addresses and you're using PSKwithIP, you'll need to make sure your IPSec configuration is updated for the new credential. PSKwithMAC is usually preferable, since it uses the hardware address as one of the credentials rather than an IP that could (and in this case, likely will) change. 

    For moving it, you're probably better off spinning up a second MM (you should have a second one anyway; if you're already running MM-VA, then a second VA does not require an additional license) in the new datacenter under L3 redundancy (or preferably L2 if possible), letting them sync, and then going from there. If you're able to get L2 between the data centers, you can leave both MMs up, and point your controllers to the L2 VIP address. If you need to take the old one down because the DC is being decommissioned, then you can wait for the new one to be up and then once you've made it primary, you can take the old one down and move it.

    ------------------------------
    Ian Beyer
    ------------------------------

    Original Message


Related Content