Central does the configuration, the Virtual controller (one of your APs in a cluster, automatically selected) will be the 'leader' of your cluster from a control perspective. What you configure in that screen is the VC-IP, which is an additional IP address that always follows the active VC, and can be used to access the local WebUI. Normally with Central, you would not need that, unless you have a connectivity issue and the AP can't connect to Central, and reverts back to local configuration.
Mentioned above are few scenarios where configuring a VC IP makes sense. In general, if you have a single AP cluster, it's not needed to configure the VC-IP.
There is some info about the VC in
this video series.
------------------------------
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: Oct 10, 2021 10:19 AM
From: Jaso Christenson
Subject: Virtual Controller in Central?
I am hoping somebody can help me understand what the purpose of the virtual controller in Central is. A physical AP at each of my sites functions as a VC. Would the Central virtual controller for each site take over that role? Why would the virtual controller in Central need an IP address? I can't seem to find any decent documentation on this.
The Central virtual controller I am referring to is located at Group>Devices>Config>System.
Thank you for your expert assistance.