Not able to adopt WiNG APs by a virtual controller on a routed network
APs connected to a routed (layer 3) switch are not getting adopted by a Virtual Controller (VC)
By default, adoption by a virtual controller should be done over layer 2 if seamless roaming is required, but in a routed environment, layer 2 broadcast traffic is not allowed through layer 3 switches and this will disrupt the adoption process.
Configure layer 3 adoption on the client APs and point them to the virtual controller (Read additional notes regarding seamless roaming):
Log into the AP via a browser
Under Configuration go to Basic
Under Controller Adoption click on Add
Enter the IP address or Hostname of the virtual controller
Click on Update
Click on Apply
Log into the AP via browser
Go to Configuration >> Devices >> Device Configuration
Select the AP and click on Edit
Navigate to Adoption
Under Controller Hostnames click on Add Row and Enter the Virtual controller information >> OK >> Exit
When adopting APs to a virtual controller or setting them up as standalones, it is important to note that seamless roaming will onlywork when all APs are in the same broadcast domain (layer 2 adoption) so seamless roaming is not possible in above scenarios.
If seamless roaming is imperative on a routed network, you might want to consider using a controller instead of a virtual controller for AP adoption and management or simply replace the layer 3 with a layer 2 switch.