ā02-27-2020 11:02 PM
Weāve got a new deployment of (8) 8533 APās and (8) 7632 APās. Weād like to set up two of the 8533ās as redundant virtual controllers (like a typical āclusterā of vx9000ās or older WM3600ās). I canāt seem to find any way to do this officially and Iām wondering if itās only possible via the CLI (or if itās possible at all). Iāve only done this once before on a full blown controller. If it is possible, can it be done in the UI? Are there any gotchaās to look out for?
Thanks
Eric
Solved! Go to Solution.
ā02-28-2020 01:02 AM
Hello Rick,
You can have all of the AP8533s in the same AP Profile and instead of using static IP addressing on VLAN 67 and use DHCP (possibly reservations). Have the AP76xx in their own AP Profile and I would disable rf-domain capable on this AP profile.
When you configure auto-elect VC feature for the AP8533s, you can use the ,21 as the virtual IP and whatever AP is the VC at the time you try to access .21, only that AP will respond. This way you do not need to keep track of what AP is the VC.
ā02-27-2020 11:46 PM
Thanks guys. Seems we were heading down a legacy path (not having done this recently) and missed the dynamic VC concept details. We also had (and still do) issues getting the controllers to properly trunk and allocate VLANās. We adopt at L2 on v67 and then allocate SSIDās on two other vlans (60 and 68). It seems that the DVC setup assumes that the adoption network is V1 and if you try to correct it (change the native, untagged network), it breaks your connection until you can get into the CLI and set up the trunk and native VLAN settings. Of course, one of the APās weāre using is 34ā up in the air, complicating this. Do most of you find that the CLI is a more reliable way of deploying this setup? We never use V1 for adoption.
ā02-27-2020 11:35 PM
Hi, BigRic please see the below knowledge Article :
ā02-27-2020 11:09 PM