Wireless Access

I have a testing / lab environment with Virtual Mobility Master and Standby VMM (in L2 redundancy / HA mode) and two VMC's setup and running AOS 8.2.0.2, under VMware ESXi.

Due to a restructuring of the network infrastructure, I need to move my Virtual MM and Standby MM and both VMC's to a different subnet, and as a consequence all the IP adresses will have to change.

How can I proceed best with changing the MM ip addresses ?

 

Would also like to know this information

The answer is "it depends".  It depends on what services you require.  Airmatch, Airgroup and anything else that depends on the MM at the time will not run between the time you re-ip the MM and put it where it belongs.

It would be a pretty instant change.

How do you go about changing the IPs on the Mobility Master & the Mobility Device – do you need to re-add the controller in the MM with the new IP or can you just amend the IP? Does it lose the config or will it re-sync all config?

Thanks

Scott McMullan | Senior Systems Engineer | Kainos | DD: +44 (0)28 9057 1517 | s.mcmullan@kainos.com

Each Node points to the MM using this command:

 

masterip 192.168.1.x ipsec ****** interface vlan 1

 

For each node-specific configuration, on the MM, I would change that ip address to the new ip address, first.  When you do a write mem, that  would cut each node off from the MM because it would be pointing to a new ip address.  You would then re-ip the MM.  After the MM is changed to the new ip address, the nodes should re-connect, because they MMs are identified by their mac address.

 

**That is the general description of how it could be done.  The details of how that is accomplished could be more complicated based on your setup**

 

masterip 192.168.1.x ipsec ****** interface vlan 1

 

Hi,

What about this ipsec key? Should we enter this on only MM or both MM and controllers? Should we use the ipsec key in installation before or does it matter if we can use any key?

Thanks.

I guess the controllers will restart instantly as soon as the changes are committed?

Will they start operating again after the restart even if the new master ip is not reachable at that time?
So will wifi be usable while virtual mobility conductor is not reachable?
Normally, if master is not reachable for some hours I know that this is not a problem for a controller-based architecture. But not sure what effects this change has ...

Original Message:
Sent: Sep 13, 2019 10:22 AM
From: Colin Joseph
Subject: AOS8 Change Virtual Mobility Master MM and StandbyMM subnet & IP addresses

Each Node points to the MM using this command:

 

masterip 192.168.1.x ipsec ****** interface vlan 1

 

For each node-specific configuration, on the MM, I would change that ip address to the new ip address, first.  When you do a write mem, that  would cut each node off from the MM because it would be pointing to a new ip address.  You would then re-ip the MM.  After the MM is changed to the new ip address, the nodes should re-connect, because they MMs are identified by their mac address.

 

**That is the general description of how it could be done.  The details of how that is accomplished could be more complicated based on your setup**

 

Hello,

Finally, somebody did this operation successfully?

I'm in the same situation and I need to be sur that the configuration and access to the mobility controller will not be wipe when I change the Ip and subnet of the mobility controller.

regards,

 

Original Message:
Sent: Sep 13, 2019 10:22 AM
From: Colin Joseph
Subject: AOS8 Change Virtual Mobility Master MM and StandbyMM subnet & IP addresses

Each Node points to the MM using this command:

 

masterip 192.168.1.x ipsec ****** interface vlan 1

 

For each node-specific configuration, on the MM, I would change that ip address to the new ip address, first.  When you do a write mem, that  would cut each node off from the MM because it would be pointing to a new ip address.  You would then re-ip the MM.  After the MM is changed to the new ip address, the nodes should re-connect, because they MMs are identified by their mac address.

 

**That is the general description of how it could be done.  The details of how that is accomplished could be more complicated based on your setup**

 

May be best to work with your Aruba partner, Aruba Support, and/or test this in a lab. Most customers don't change IP subnets on a regular basis, so it's important to do this well prepared and have someone available in case you get stuck.

I could imagine that moving the Standby VMM first, and using the VMM redundancy may be an option to explore. If you lose connection between MD and MM you can after you fixed the config in the MM to what it should be, change the config in disaster-recovery mode on the MD to restore the connectivity. As mentioned above, you lose some features like AirMatch, AirGroup during when the MD can't communicate with the MM.

------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------

Original Message:
Sent: Dec 02, 2022 04:52 AM
From: Jeremy Lenaerts
Subject: AOS8 Change Virtual Mobility Master MM and StandbyMM subnet & IP addresses

Hello,

Finally, somebody did this operation successfully?

I'm in the same situation and I need to be sur that the configuration and access to the mobility controller will not be wipe when I change the Ip and subnet of the mobility controller.

regards,

 

Original Message:
Sent: Sep 13, 2019 10:22 AM
From: Colin Joseph
Subject: AOS8 Change Virtual Mobility Master MM and StandbyMM subnet & IP addresses

Each Node points to the MM using this command:

 

masterip 192.168.1.x ipsec ****** interface vlan 1

 

For each node-specific configuration, on the MM, I would change that ip address to the new ip address, first.  When you do a write mem, that  would cut each node off from the MM because it would be pointing to a new ip address.  You would then re-ip the MM.  After the MM is changed to the new ip address, the nodes should re-connect, because they MMs are identified by their mac address.

 

**That is the general description of how it could be done.  The details of how that is accomplished could be more complicated based on your setup**