After many late nights and pouring over countless sources of documentation, including the voluminous docs found at Cisco.com, all the concepts and design elements that comprise a Cisco WLC (Wireless LAN Controller) architecture have finally “clicked”. I’ve somehow managed to escape enterprise wireless until now. Learning a new platform is simultaneously exciting and challenging, particularly on day 1. For any seasoned network engineer, jumping into the depths of enterprise wireless for the first time presents a steep learning curve that quickly needs straightening out.
Tackling a new GUI/CLI is initially a series of exercises and tests in attaining enlightenment of not only the overarching architecture of the platform, but in understanding subtle nuances and hierarchical relationships. Sample walk-thrus of configuration rarely explore these nuances in any meaningful way; that takes frequent help-searches and reference materials. The process of reaching your “light bulb” moment is akin to having a pile of multicolored marbles that you can finally begin to order in a meaningful way.
I intend to show in this series (yet to be completed — please indicate interest by using the Like button at the bottom of this article and/or registering on this site) the basic components necessary in launching a small-scale WLC deployment quickly and without taking any design shortcuts that could cut into you future expandability nor have a negative impact on high-availability.
In the next the section on the Cisco WLC Series, I’ll attempt to show the relationships between these building blocks in a concise and meaningful way. A diagram (not yet completed) showing these elements will hopefully illustrate the holistic understanding of a WLC in the least amount of time. We’ll cover:
- Interfaces (Service, Management, Dynamic)
- Interface Groups
In subsequent sections, we’ll touch topics on:
- IP and VLAN Planning for wireless
- DHCP Proxy
- AP Groups
- Guest wireless (without an auto-anchor)
- Mobility Group
- Mobility Domain
The subject of RF (radio frequencies), site surveys, AP (acces point) placement, and detailed config walk-thrus will be avoided as it’s not the goal here, and, besides, there are a great many other sources on the subject such as my80211.com that would give better treatment to those topics. The goal is to have you come away with a critical understanding of what it takes to build a small-scale WLC deployment, using a couple of 5508 WLCs, and be able to get your own system running in just a couple of weeks or less.
Sections in this series (completed):