06-27-2013 02:58 AM - edited 07-04-2021 12:18 AM
Hi
According to this document 802.11w is only supported on 802.11n AP's
What are the implications of enabling this on a controller that has a non 802.11n AP's. Does any one know if this will this causes issues when clients roam?
Has anyone deployed this.
Thanks,
Sero
Solved! Go to Solution.
06-27-2013 08:39 AM
I would not implement anything in a mixed environment. Even having 802.11n and non 80211n can be an issue when clients roam. It just good practice not to mix thing up or else troubleshooting becomes harder.
Sent from Cisco Technical Support iPhone App
06-27-2013 08:39 AM
I would not implement anything in a mixed environment. Even having 802.11n and non 80211n can be an issue when clients roam. It just good practice not to mix thing up or else troubleshooting becomes harder.
Sent from Cisco Technical Support iPhone App
07-01-2013 01:53 AM
Thanks Scott,
FYI - We did some limiting testing in a on a single 802.11n AP (1262) and found that some clients (motorola barcode readers i think) could not connect when this was set to optional.
07-01-2013 04:43 AM
This is the problem with newer features... All client have to support it and many old devices have strict requirements which almost makes it impossible to enable new features until these devices are phased out for new ones that will hopefully support it. RF scanners are like the worst:). These have to work, but some are very old because its expensive to replace or the newer models don't support certain standards:)
Sent from Cisco Technical Support iPhone App
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide