This looks like a feasible plan. Make sure that the firmwares are same versions for all devices in the cluster. I think the LTE version has a slightly higher minimum version, but if you are on current versions that should not be an issue. If you are in a critical production environment, I would test in lab and get TAC or your Aruba partner involved.
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
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: Apr 10, 2023 07:13 PM
From: SkiP
Subject: Replacing cluster contained MD hardwares in MC-MD architecture
Hi Herman,
WLC-A and WLC-B are LTE models, others are not. Currently we don't use LTE functionality on this site, but would like to use at other site, this is the reason why we would like to replace all controllers.
Assume that the current IP allocation looks like this:
VRRP address: x.x.x.10
WLC-A: x.x.x.11
WLC-B: x.x.x.12
In a first step, we extend the current cluster with WLC-E hardware and a new IP address (x.x.x.13), so that there will be 3 controllers in the cluster.
I was thinking that in a second step we would remove WLC-B from the cluster and then add WLC-D using IP address x.x.x.12.
The last step would be to remove WLC-A from the system and put WLC-C in its place using IP address x.x.x.11.
Can this method work, or do you see a pitfall? What do you need to watch out for?
Thanks!
Original Message:
Sent: Apr 04, 2023 11:06 AM
From: Herman Robers
Subject: Replacing cluster contained MD hardwares in MC-MD architecture
Not sure why you would replace the current controllers by the same model, but you could put the new controllers in the same group in your hierarchy, make sure they are up, reachable and connected to the same VLANs, then add them to the cluster, and remove the old ones from the cluster. Or just add a WLC-C and add that to the cluster.
Adding or removing controllers from a cluster should be transparent to the end users.
------------------------------
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: Apr 04, 2023 09:01 AM
From: SkiP
Subject: Replacing cluster contained MD hardwares in MC-MD architecture
Hi Guys,
We have a redundant MC (MM) pair in datacenters and have controller clusters on each site. For certain reasons, we need to change (and extend) hardwares at one of the smaller site in a working environment. The reason for the +1 controller expansion is that the number of APs has increased to over 32 on that site, and thus the current deployment no longer provides full redundancy.
Currently these 9004 controllers used on the site in cluster: WLC-A and WLC-B
We need to replace WLC-A and WLC-B controllers and using these 9004 controllers with identical configuration: WLC-C, WLC-D and WLC-E
At the end, we need to grab WLC-A and WLC-B hardwares out from the environment.
CPsec is currently enabled on the configuration and I'd like to keep it enabled. (We use own certificates for captive portals.)
What do you think, what is the easiest method to archieve this?
Thanks! :)