my collegue changed the native vlan of the trunk to vlan id 29 (which is AP-Manager interface) and it seems that AP now are joining ...
In my opinion it doesn't make sense, because on the WLC the AP-M interface is defined as VLAN 29, not 0 or untagged.
Maybe a problem in the LAG configuration?? The WLC is configured with LAG but up to now I have only 1 port connected to a NX 7000, the other is not connected, because I'm still not sure if vPC is supported or not.
After some tests we solved the problem in this way: we removed the "ap-manager" interface and used the standard "manager" interface, which is in access on vlan 29.
Now all the APs are registered and working fine.
Another question: we try to use LDAP (versus a M$ 2008 DC) for grant access to a wireless lan (instead of the standard password), but it seems that this configuration is not supported ... any suggestions?
IntroductionHow to use the Wireless LAN Controller Configuration Analyzer (WLCCA)
Javier Contreras is a Senior Tech Lead for the Wireless Business Unit in Cisco, with over 2 decades of experi...
< PRE >
(#)For this reason being that : - application that doesn't use multicast, sends one copy of each packet ( data unit of traffic at layer 3 ) to each client (" who seeks the traffic ).- application that does use multicast, sends ...
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...