![]() ![]() ![]() ![]() This design has a couple of major advantages. The APs themselves lose their individual intelligence, and the controller becomes the brain for the entire WLAN. The controller's job is to be a single choke point for AP configuration, communication and, in most cases, policy enforcement. To solve these technical issues, WLAN vendors created wireless LAN controllers to force data and management control-plane data back to a single location. Even more problematic, the APs couldn't communicate with each another, so technical issues - among them co-channel interference, power adjustments and client roaming - made many networks unstable and unpredictable. Suddenly, network administrators had to manage hundreds, even thousands, of APs in an attempt to blanket entire buildings and campuses with a wireless signal. These areas were typically places such as conference rooms, lobbies and outdoor patios - any location with many users and few wired ports.Īs the demand for Wi-Fi access grew within the enterprise, so did the infrastructure required to supply it. At the time, this wasn't a problem, because most companies designated specific areas for wireless hotspots. When enterprise WLANs were originally deployed, each wireless access point was configured and managed independently from other APs on the same network. The evolution of WLAN architecture design ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |