04-27-2015 08:49 AM - edited 07-05-2021 03:03 AM
Hi Experts ,
We are having WLC 5508 with code 7.6.130 code and 3702 AP. The problem is the flex connect mapped vlans for some of the AP's are randomly changing. Hence clients are not able to associate. Then we have to configure manually again . Have checked in the release notes , there was no bugs regarding this.
The AP's are up for 100 days and not even it got restarted. Any suggestion would be helpful.
Thanks,
Vijay
Solved! Go to Solution.
05-29-2015 11:25 AM
I had this problem on a couple of my flexconnect APs. What I ended up doing to fix it was create an AP group per location with "dummy" interfaces assigned to that wlan (eg, create interface "Boston", and give it vlan tag 192 with no IP addressing assigned).
Add the APs to the AP group, and they'll auto-populate the tags that way.
04-27-2015 09:27 AM
I've have this issue on the same version of code, affecting a very small number of APs.
Are you certain that the AP has remained registered to the same WLC, and hasn't moved? It's possible that the uptime is high, but the configuration changed when the AP moved between two different WLCs.
Pete.
04-27-2015 09:39 AM
Hi Pete,
Yes , about 40 - 50 APs are affecting out of 350 AP's . Ap's are registered with the same WLC only , and we haven't done any changes. Moreover both WLCs SSID config are same including WLAN id.
Thanks,
Vijay
04-27-2015 09:41 AM
Hi Pete,
Yes , about 40 - 50 APs are affecting out of 350 AP's . Ap's are registered with the same WLC only , and we haven't done any changes. Moreover both WLCs SSID config are same including WLAN id.
Thanks,
Vijay
05-29-2015 11:25 AM
I had this problem on a couple of my flexconnect APs. What I ended up doing to fix it was create an AP group per location with "dummy" interfaces assigned to that wlan (eg, create interface "Boston", and give it vlan tag 192 with no IP addressing assigned).
Add the APs to the AP group, and they'll auto-populate the tags that way.
05-29-2015 11:32 AM
Yep - agree I did the same and it works well.
11-21-2017 12:11 AM
@Tyler Conrad wrote:
I had this problem on a couple of my flexconnect APs. What I ended up doing to fix it was create an AP group per location with "dummy" interfaces assigned to that wlan (eg, create interface "Boston", and give it vlan tag 192 with no IP addressing assigned).
Add the APs to the AP group, and they'll auto-populate the tags that way.
the dummy interface should be vlan tag 192, or can user the other tag?
05-29-2015 09:17 AM
I have the same problem, it's happen after add a tunneled WLAN to the AP group.
06-01-2015 10:55 PM
Please refer to the link-
http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-2/configuration/guide/cg/cg_flexconnect.html
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide