WLC do Primary & Secondary Controller Network locations
On WLC > Wireless > AP > High Availability, do the controllers have to be on the same LAN? In other words, can they be located across a layer 3 boundary, say in different geographic location? I don't see how Secondary WLC can support an AP that not configured 'locally' (local interfaces, WLAN, AP group, etc.). H-REAP presumably. I configured many of those and they work great (local switching). My understanding is that an LAP *must* be local with an interface, WLAN, AP group, and a local Vlan trunked to the WLC interface. Can somebody clarify this for me? Thanks.
You can have wlc across the WAN, the thing is, what ip address will the devices get. AP's will failover to any WLC that is on the same mobility group and is reachable so that isn't really the issue. You have to look at what happens when an ap joins the other wlc, and the ap is in local mode. The traffic will be placed in that local network and devices will have to obtain a new dhcp address in order for them to have network connectivity. Static address devices will not work in this scenario. H-REAP local switching doesn't matter since the traffic is local where the ap is. H-REAP centrally switched will have the same issue since the wlcs have interfaces in different subnet's.
Help out other by using the rating system and marking answered questions as "Answered"
AP join happens using control plane, as long as AP HA has Primary, Sec controller's name and IP info and have L3 reachability to those HA WLCs(from AP's IP at the remote site) failover happens without an issue. The locally switched wlan mapped to vlan is per site basis.
For hreap, AP holds the WLAN to VLAN map config for locally switched wlan unlike central switch wlan mapped to dyn int of WLC.
It is my suggestion -fail the hreap APs atleast once to all HA WLC before production so that all WLCs can learn the AP config to avoid AP's being mapped to default vlan.
Hello Community, I have an issue where APs do not connect to the WLC. Connection is made over VPN. Until yesterday all 3 APfailed with below errors. We change the LAN connection to a cisco router and now one of the AP magically connected to the...
Where to download
Attached files on this post
Alternatively, cloud version (only summaries)
New implementation for the WLC Config Analyzer. it is a new re-write of the application, with clean up and improved checks
Support for IOS...
Cisco Champion Radio · S8|E6: Fastlane+ Optimizes Network and Device Communication
Cisco Fastlane+ is a co-developed solution with Apple that significantly improves the experience of any Wi-Fi 6 capable iPhone or iPad connected to a Cisco Catalyst 9130 A...
We are pleased to announce the immediate availability of the IOS-XE release 17.4.1 for the Catalyst Wireless Controllers. The new code is now posted on the CCO and can be found at this link:
Table of Contents
The purpose of this document is to provide step-by-step instructions regarding how to connect your read-only Catalyst 9800 WLC or AireOS WLC with Cisco DNA Center for Assurance monitoring through manual configuration. I...