03-16-2020 11:22 AM
Hello ,
I have two vx9000 controllers configured to pass data via XCA [nsight profile] to XMC.
XCA has no license for AP, and is used only as proxy.
AccessPoints are visible in XCA and XMC but no clients records are present.
Please let me know if i missing something or it is normal and works as expected ?
config of vx9000:
nsight-policy XCA
server host X.Y.Z.M https
self
use nsight-policy XCA
regards,
Tomek
03-17-2020 04:41 PM
Hi Tomasz,
Just to briefly expand Daren’s message, control-vlan parameter should only be configured for an RF Domain that is separate from the managing controller’s domain (ie. a branch of multi-site deployment), and only when that “remote” site (separate RF Domain) consists of APs and no site controller (we can adopt site controllers to a HQ controller in WiNG). The parameter is used to instruct APs on what VLAN can they find each other and RFDM most importantly. 99,99% of cases it’s the same as the native VLAN (and - honestly - I’m not sure why it has to be a separate parameter from the native VLAN).
This parameter can break things up when used in different types of AP/controller placement.
If you wish we can also assist you in some troubleshooting, these may come handy:
show mint neighbors
show mint links
show adoption status
show adoption pending
show adoption history
show adoption log adopter
show adoption log adoptee #issued on the AP
Hope that helps,
Tomasz
03-16-2020 03:33 PM
Hi Tomasz,
Even if APs un-adopted because of the change they should have come right back
It might be best for you to open a ticket with GTAC.
Its a possibility issue is with how system is deployed/configured.
We will need the tech-support from the controller and 1 AP to start looking at the issues.
03-16-2020 03:21 PM
Hi, after removing that APs un-adopted controller.
Tomek
03-16-2020 03:05 PM
If controller is in default rf-domain can you remove both the control-vlan and the controller-managed configuration from the rf-domain.