Airheads,
We've been having a bit of an issue with using Airplay during peak client density times. The connection from the client to the AppleTV severs without warning and then can be reconnected again. This tends to happen only during times where the classrooms are fully populated with students (also the worst time for it to fail).
I am running 6.3.1.4 with Airgroup enabled, ARM settings set to default other than "Mode Aware Arm" being enabled, which wasn't enabled previously with the same issue occuring. I was using my own blend of uneducated guesses previously and last night created a clean ARM profile to test with and just re-enabled the Mode Aware Arm. I'll be finding out today if we still are experiencing issues.
We have added an AP into every classroom in an effort to troubleshoot this issue. I also set the AP's to prefer 5GHz since they are now in closer proximity to each other. We have a mix of 105's, 125's and 135's.
A few weeks back we discovered interference on 2.4Ghz due to some HVAC Variable Frequency Drives that we have since disabled for troubleshooting purposes.
My questions are as follows:
What commands in the CLI can I use to watch the specific MAC address of the AppleTV in question to see if it gets reassociated to another AP during it's active connection?
Is "Client Aware" or "Client Match" supposed to leave that AppleTV on the current controller until it stops having an active connection? Is there another command that should do that? What are the implications campus wide of enabling such command if it should resolve our load balancing issue?
Given the standard ARM profile, should the AppleTV's "stick" to their associated AP, even when there are a lot of clients on it's AP vs fewer on the close neighbor AP?
Thanks for the help, I'm running out of guesses on this one.
#AP135