As I said Friday when I sent out the notes from the NETMAN session, let me start off my apologizing for taking a full month to get these out...
Secondly, again a huge thanks to Ryan Turner (UNC Chapel Hill) for putting the surveys together for both the Wireless-LAN and NETMAN discussions. Also as I said Friday, this is the first time we tried this method. I think we worked the bugs out during the NETMAN session, making the limited Wireless-LAN session time more efficient ... I'm not going to include all of my notes from the session or this email will be painfully long. I've commented on some topics, but hopefully this list will spur continued conversation on the list. I've also included a few items from the NETMAN session that touched on wireless networking (first 3 bullet items). Just a quick metric, we had 57 people in the session, representing ~50 different institutions. Top Trending Topics * NAC (just doesn't want to go away) - onboarding for both wired and wireless networks * Use of "hospitality wireless units" such as the Aruba 205H (physically, where are they being places? For lower installs, are they being damaged?) * People are just now starting to look at MGBase-T (2.5/5Gbs Ethernet, especially for access point uplinks) * Wireless performance - how best to measure/test * 2.4GHz vs 5GHz - clients still preferring 2.4GHz unless radio very close * How are you designing your placement of AP's - checkboard vs every room o Is there a placebo effect - if the AP isn't in the room, do people complain that their signal isn't good even if the signal strength is excellent? * 20MHz vs 40HMz vs 80MHz channels * Transitioning vendors o Who are you currently with; who are you moving to? o Cisco & Aruba are dominating the industry (of the 50ish unique institutions, Cisco and Aruba were about equal, combined accounting for 90% of the installs. There were no more than 2 institutions using the same vendor). * TLS vs PEAP vs MSCHAPv2 - discussion about forcing install of certs on Guest Wireless * EDUROAM - mix of using EDUROAM as primary SSID o Branding was not a driving force for not/using institutionally-associated SSID name (e.g SalemState) o Dual SSID's was common to begin rollout, with intention of only using EDUROAM down the line * Open wireless - moving toward (1) or away (4) * Usual issues with students bringing up their own hotspots in ResNet settings * Has anyone adopted WiFi calling? To those who attended, thank you (especially considering it was such an early start!). If you didn't .. next year we're in Philadelphia. We hope to see you there! -Brian Helman, Salem State University -Ryan Turner, UNC Chapel Hill ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
