03-25-2021 10:00 PM
Solved! Go to Solution.
03-25-2021 10:11 PM
Are those APs on a different mgmt. VLAN? Virtual controller deployments are meant for single site, single mgmt. VLAN. Actually, the single site concept is logical, you may have two buildings with APs in them connected via same mgmt. VLAN, that will still be considered single site.
As far as the APs in the other building can see the virual controller on the same VLAN and adopt to it, there shouldn't really be any difference between the APs local to the VC and the ones in the other building.
03-26-2021 08:04 PM
I am glad to hear that you found the problem.
Good luck with adding the new APs!
03-26-2021 08:00 PM
hello an apology for the delay, apparently it was an error in the configuration of the VLAN by the Switch and not by the AP, but I really appreciate the support.
03-25-2021 10:56 PM
So, few things to clarify:
1- All APs are adopted to the VC or they are not?
2- Make sure all the APs including VC are using the same profile.
3- Shed some light on the switch VLAN configuration pls.
4- If you can share the running config from the VC, that will help understand the network and VLAN assignment.
03-25-2021 10:35 PM
It is correct in both buildings the same vlan is configured, since in building A there are the DHCP, DNS. And in building B the connections to the equipment arrive and in the Switch the vlan that is in building A is configured. The VC (ap505) is located in building B, it has a profile configured for the ap, the vlan is in trunk mode. This profile has already been assigned to the AP but is it correct to do the configuration in this way, or is there a specific way to do this configuration in the VCs?