#1 Figure out what is driving the need for redundancy. If the customer cannot afford for any downtime, they should invest in a second 7200 controller and do it right, since downtime will cost much more than an 7200. Failover/upgrades would be fairly seamless if AP density is high and of course the total failure of a controller would result in uninterrupted uptime.
#2 If the customer wants to do redundancy just for the sake of redundancy, they can do any of the other designs you mentioned. They all have the drawback of the administrator needing to keep track of how many APs should be on what controllers. Some outages are not total, so APs will fail over to other controllers silently and nothing will show as being "down", so users will be roaming between APs on different controllers for months and having issues. In that situation, troubleshooting becomes more difficult. This is how adding redundancy can create more issues if it is not done right.
------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
------------------------------
Original Message:
Sent: Sep 29, 2021 11:05 AM
From: ioan fitigau
Subject: MD redundancy/cluster
Unfortunately, I cant. I need to use the all 3 controllers to build a redundant network for them.
------------------------------
ioanf
------------------------------
Original Message:
Sent: Sep 29, 2021 10:43 AM
From: Colin Joseph
Subject: MD redundancy/cluster
Honestly? Get another 7200 and form a cluster with your first 7200. That is the best answer.
Any other iteration of redundancy will complicate management and will increase troubleshooting time.
------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.