This past week I’ve been busy with my colleagues setting up WiFi for a large event on campus. What I learned out of this was planning should always be a requirement. Would you start building a house without any plans?
Little was known about what the requirements were. What we did know was we should build wireless for 1-2 Mbps per person.
What people really needed was much more. Why was this? Because the application usage of users was never provided to us. While some people did not know what that application was, I think we should have pushed for more information.
Additionally, we did not know of how the rooms would be laid out on the floor. We were left in the dark of where users would be congregating but we had less than 3 days to install our access points and antennas. So with directional antennas we decided to cover the areas from the sides and shoot signal through the middle. Later on, we needed to realign those antennas.
Another thing we missed was the amount of hotspots on the same spectrum as our access points. We had to mitigate the overlap by not propagating 2.4 GHz in some areas and providing only 5 GHz wireless connectivity. I saw a boost in usage with going with this method. But there’s a risk of having 2.4 GHz only devices stranded. I took that risk.
With my trusty spectrum analyzer in hand, I was able to identify a persistent interferer on channels 1-6. We decided not to use those channels and only use channel 11 but on a lower transmit power compared to the 5 GHz channels.
Planning is a critical step in wireless deployment. Without it, you’re purely guessing. Sure you could overdo it by installing way more than what’s required but that’s a waste of time and money. We spent a lot of time post-installation optimizing the wireless network as the event changed over time. Lots of time and resources got put into making changes.
Links and Resources

* Equipment used for the event:

* Cisco 3702E
* Cisco AIR-ANT2566D4M-R
* Metageek Chanalyzer
* Ekahau Site Survey
* WiFi Explorer
* Savvius Omnipeek
* Wireshark


* CWAP PW0-270 expires June 27th, 2016. Replaced by CWAP-402.