So did I do RF scans, additional spectral analyses and try to plow through various waterfall and waveform views?
No.
Did I break out iPerf and set up several clients and a base and run multiple throughput tests based off of artificial traffic generation?
Nope.
Did I make gratuitous use of websites such as http://www.speedtest.net/ and http://www.speakeasy.net/speedtest/ to test download/upload throughput even though we all know that these tests are subjective based upon what server you choose and thus do not supply you with reliable results? (but you know we ALL still use them anyway haha)
Negative Ghost Rider.
When I got into the wireless game about 10 years ago my mentor said that one of the best things you can do is to try out what the user experience is like for yourself. Find out what your clients surfing habits are like (or a close educated guess will generally work too) and then do it. Then you have to be honest with yourself and ask “Am I happy with this experience? Did it meet my expectations as an end user? Did I accomplish what I set out to accomplish while online in a timely manner?” I took his advice to heart and it has served me well.
Now don’t get me wrong, when designing a wireless network I don’t just run around asking the wireless fairy where I should place APs and hope that they work. I do the legwork, I do spectral analyses when I feel it is needed (i.e. I would in a Downtown location but obviously not at a remote campus located in a rural area that time forgot and still has dinosaurs roaming about). I read building plans and blueprints taking notice of construction materials and their associated attenuation factors. I also work with the various departments to find out where their people will be located, what they want out of the system, where student concentrations will be, yadda yadda yadda…
So network design and post-performance evaluations for me are two different animals. And before the number crunchers who reside on a higher plane of geek-dom than I do rip me apart, I am stating for the record that I am not, nor do I claim to be an RF Scientist. I am however, a network administrator who has a passion for the wireless side of the house and I enjoy working with it.
So back to the original question of how I tested the APs and what did I use. Well, there is not a simple answer to that. After a while you develop an intimate knowledge of your environment in relation to your AP locations. This is especially easy for smaller shops like us with a couple of hundred Aps on two or three campuses and a few small satellite locations. I don’t know how the guys at Ohio State do it with their billions of APs. Anyway, I see the high density areas every day as I walk through campus. I know where the students and staff are and where they gather other than in classrooms. Also, the controllers have some nifty tools on their dashboards that help as well. In specific the “Usage” and “AppRF” pages on the Dashboard tab. So knowing my environment, knowing what my peak usage times are, and using these dashboard tools I am able to discern quite a bit. I look at the dashboards every day (I only have 5 controllers so it’s not really a big deal, again I don’t see a shop like Ohio State using this method LOL) and also at the combined statistics on my AirWave server. Admittedly, I am a little OCD about it and constantly check them throughout the day. So when an AP peaks my interest I check it out and first look at how many clients are associated vs. how many of those clients are authenticated vs. how many are actually passing data or setting idle.
As an example, while I am writing this staff and instructors are preparing for graduation ceremonies in our gym. One of my AP105s in there is reporting 57 associated clients, of those only 42 are authenticated and of those only 32 or 33 are actively passing data. By my reasoning then there are currently 32 ACTIVE users on this AP. So that is how I determine what I call active users.
Now on to performance. Like I said earlier, my methodology is all about replicating the user experience. So before I go out to see how performance is in a certain area, I check out the “AppRF” section on the related controller and also on my AirWave server. I take note of the tops applications and services which is usually Facebook, Instagram, believe it or not – Windows Updates, iTunes, Pandora/Spotify, Netflix (we tried blocking Netflix once and almost had an insurrection as the instructors rose up in rebellion swearing up and down that they needed Netflix for instructional purposes) and the beloved YouTube, and then I go web surfing after confirming that I am associated to the target AP. Then I take an honest look at how its performing from an end user standpoint of someone who doesn’t give a rats-@$$ about network infrastructure and how it all works and blah blah blah… but just wants to get their Ogre Mage leveled up so they can go on that Guild Raid to WunderStone during the two hour break they have between classes. Being an ex-gamer (the wife and kids kind of stomped it out of me) this is an easy viewpoint for me to take.
And then I judge, and I judge harshly. And then I work to correct what I see as an issue even if most end users don’t see it.
So MemphisBrothers and Andy from Pellissippi State (who emailed me), I don’t have a magic bullet testing tool that will give me any info that I want or need. What I do have is some experience, some nice built in tools on the controllers, but I mostly have the ability to communicate with my end users and understand their experience on my wireless network. And believe me; if these kids think it sucks, they will not hold back LOL