I am having a discussion with a workmate regarding when and how many Wireless LAN controllers are needed when deploying an Enterprise WLAN. Is there a document or link that shows the best practices on when to deploy and how many Wireless LAN Controllers should be deployed based on the amount of APs, sites, branches etc.
I'm designing a WLAN for an organization that will have a central office and six remote sites within the WAN (bonded T1 connectivity). We will start out with 25 APs at each site. A Wireless Guest network will be configured so non-employees have the option to authenticate to the WLAN at each site. I have planned for a Wireless LAN Controller at each site to streamline the deployment of AP's now and in the future. My workmate is arguing that I should just use two Wireless LAN Controllers and position these at the central office and all AP's will be centrally managed by these two controllers. My thought on this is that if all my sites have their own networks/VLANs. Also, with the need for Guest access at each site, I would want a Wireless LAN Controller to facilitate this mobility option within each site's LAN.
Is there any documentation that I can consult for best practices on the deployement of Wireless LAN Controllers?
I would like to have an answer to this qestion as well. I see many customers deploy the WLC at a centralized location but I am not convinced this is the best method. For instance, the 802.11a/n and 802.11b/g/n parameters are global. You can not adjust them for individual locations. This can potentially cause some problems.
Please keep in mind that ALL traffic from wireless clients is tunneled and sent to the wireless controller.
If your wireless clients need to access resources on the local site, it makes no sense to send all the traffic to your central site and then back to the remote site. This would be a tremendous waste of bandwidth and it would add delay to your applications.
If your wireless clients need to access resources that are located on the central site, then it is no problem I guess. But still you will load your WAN with control traffic between the APs and the WLCs.
So my personal suggestion is to use WLC at each site, unless you have high bandwidth WAN links.
I had the same dillema i.e where to deploy WLC for a corporate having multiple sites.
What I can tell you consider the following:
If most of the traffic should be kept local to the site you can use H-REAP mode though if you have more than 3 APs per site (and most probably you have) then it is not recommended/supported by Cisco.
So if your wireless traffic is mostly towards applications hosted at for instance in a DC then you can go ahead with centralized WLC assuming you have sufficient WAN bandwidth.
If your wifi traffic mostly toward local file servers for instance better to use H-REAP (less than 3 APs per site) or use local WLC.
Another thing is I was told that AP to WLC control traffic consumes roughly 128kbps per AP. I don't know if it is correct but better to calculate with.
So be carefull with centralized deployment.
So I would say your design fits the requirements and also inline with recommendations. The gues traffic can be tunneled back to the central controller if you have centralized Internet breakout (auto-anchor).
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...