If you want redundancy without having to manually assign APs to individual controllers, you should use clustering. It is one of the most powerful features of ArubaOS 8.x
Seamless failover is built into clustering
Live upgrade allows you to upgrade two or more controllers in a cluster (clustering required) with a minimum of customer-perceived outage. It can much longer to upgrade, so it is something that is mostly useful for hospitals and other 24/7 environments. Everyone else should probably just pick a hour outage Window to upgrade so that it finishes faster.
Airmatch is on by default, and is enabled automatically. There is no other real choice in ArubaOS 8.x and it is better than ARM.
- ClientMatch is carried over from 6.x
-Airgroup is available in 8.x, as well, but it is administered differently. There is a deployment document on asp.arubanetworks.com on how to configure it.
-ARM is replaced by Airmatch in ArubaOS 8.x
-RFprotect is enabled if you migrate the licenses from 6.x. It functions almost identically in 8.x
I hope that helps.
------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
------------------------------
Original Message:
Sent: Jul 01, 2021 03:17 PM
From: Fawad A
Subject: migration from AOS6 to AOS8
@cjoseph Thank you for your response.
Yes I will be using two VMMs. I am interested in some of these technologies that are introduced in AOS 8:
- -Controller Clustering
- -Live Upgrade and Seamless Failover
- -AirMatch
- Not sure any other feature I should consider at this point?
I am assuming the following features are being carried over from 6.5??:
- ClientMatch
- AiRGroup
- ARM
- RFProtect
Also I am not sure about some security features like 802.11k/v/r. I guess these are part of AOS 8. I have not read about any new security feature other than what are part of part of featues mentioned above.
So are you suggesting that I consider using the virtual mobility controllers for transition and continue using the physical mobility controller once it is upgraded to AOS 8 with the new VMMs? I am not sure how long 7210s are good for? I think I can keep both virtual and physical controllers running in parallel but use either one of them for my AP termination.
------------------------------
Fawad A
------------------------------
Original Message:
Sent: Jun 30, 2021 06:56 PM
From: Colin Joseph
Subject: migration from AOS6 to AOS8
- You do NOT need to use the migration tool if you are working from scratch. It is recommended to work from scratch so that you understand the new hierarchical configuration, and not have to deal with the possible bloat from an auto migrated config.
- When you say "features" what do you mean, licenses? You should migrate all licenses.
- I am assuming you are using a Virtual Mobility master for the new setup. In that case, you can setup that new Virtual Mobility Master, add the two Virtual Controllers in a lab setup and test all of your features by putting a few APs on the new setup as a test. When you are happy with your configuration, you can migrate access points fro the 6.x setup to the new 8.x VMM and Virtual Controller setups. The 7200s are still up to date hardware, so after you migrate APs off of them, you can upgrade those 7200s to 8.x and integrate them into the 8.x system for additional capacity or redundancy. You would then have the option to remove the Virtual Controllers and stay with the 2 7200s as controllers if you feel that managing Virtual Machines is not something you desire.
The goal here is to safely test a new system, while at the same time keeping all of your options open.
------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.