Wireless Access

I have a primary and secondary MM with 5 different MD Clusters that I need to change the ip numbers on. I am trying to plan the changes to cause a minimum downtime.  If I change the MC to the new ip number first will I have to reboot all the controller clusters for it to connect to the new MM ip's?  Just not sure about that.   I am at version 8.6.0.9 .  If I can change the ip of the MM without having the clusters reboot, then I can schedule a change for each cluster individually.
Thanks for any info you can provide.

The MM provides services to the MDs so there will be some downtime.
It is definitely not for the faint of heart, so I would engage professional services to do what you want to do.  
Others could give you advice on how you would tackle this, but I don't have enough detail on your setup for you to avoid the many pitfalls that this would entail.

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

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
------------------------------

We performed a similar change to move our MM to a new network, and reached out to support for assistance. We changed the IP of the standby MM and created a VRRP address for the new network and assigned the new IP as the Management IP. We pointed one MD to the new MM Cluster IP and rebooted it, pointed the second MD to the new IP and rebooted it. Repeated these steps on the 2 MD's on the second cluster one at a time. We then changed the IP of the Primary MM and added it to the VRRP.

We did have issues along the way with licensing passphrase changing and an issue with some of the MDs having to be configured in disaster recovery mode because the MM IP was configured locally on the MD before it connected to the MM, which caused it not to properly change using MM.

It was pretty impactful given the issues we had and did involve reboots of the MD's. I would agree that having support or professional services involved would be ideal. 

We were on version 8.7.1.4 at the time.

Original Message:
Sent: 10/14/2022 10:44:00 AM
From: sccmobjohnson
Subject: RE: Mobility Master (Conductor) IP change

We performed a similar change to move our MM to a new network, and reached out to support for assistance. We changed the IP of the standby MM and created a VRRP address for the new network and assigned the new IP as the Management IP. We pointed one MD to the new MM Cluster IP and rebooted it, pointed the second MD to the new IP and rebooted it. Repeated these steps on the 2 MD's on the second cluster one at a time. We then changed the IP of the Primary MM and added it to the VRRP.

We did have issues along the way with licensing passphrase changing and an issue with some of the MDs having to be configured in disaster recovery mode because the MM IP was configured locally on the MD before it connected to the MM, which caused it not to properly change using MM.

It was pretty impactful given the issues we had and did involve reboots of the MD's. I would agree that having support or professional services involved would be ideal. 

We were on version 8.7.1.4 at the time.