Hi , How to Ap steering, How to make L3 adoption with 3th party router, L3 adoption lab with Cisco switch linked. The guide about how to  put attenna during the AP mounting, especially on big gain attenna. Thanks!! zhiguo

I think a how to guide on clustering would also be beneficial.  I know the user guide outlines the steps for it, but I think an actual guide including do's and don'ts and "things to keep in mind" would be really nice.  Including Motorola approved best practices would be really beneficial, especially when dealing with larger deployments that include adaptive AP's.   Quick Edit:  Giving bandwidth concerns as well as any timing examples would be helpful (ie: given this environment with this many AP's per switch, how long it would take for a certain # of AP's to get adopted in the cluster when one switch goes down).

Some thoughts One of the most interesting areas of this is when RFS switches are part of a cluster when the switches are in different geographical plants. As far as independent WLAN's this is a fairly straight forward situation, but when extended WLAN's are introduced there are traffic pattern considerations, secondary failover considerations (what happens when 2 adjacent AP's in location a get adopted by 2 different switches in locations B and C respectively--you now have roaming issues because of the IP addressing) There are also WAN capacity issues and traffic patterns to consider in these situations. --------My guidance would be not to use remote clustering as a redundancy strategy where extended WLANS are implemented (which is most of teh time) It would be helpful to have a "secondary" preferred  RF switch assigned to an AP to have predictable failure behavior, and an option to automatically revert to the primary preferred RF switch with a time based parameter A second area of interest is the results of inconsistent use of the Cluster CLI and Cluster GUI. I suspect this can cause some very bad behavior, and is an area in which many problems are caused. I believe that if switches are clustered, the default mode should be cluster GUI and Cluster CLI....manually exiting these when you don't want to use them.

I'd like to see a "Getting Started with WiNG 5" How-To.  It should be written technically for people who are familiar with concepts in WiNG 4.x, showing how those concepts translate to WiNG 5.  I'm thinking it could include: Creating a WLAN Extended/Independant Manual AP/WLAN mapping Clustering (Previously mentioned)

A guide on the troubleshooting capabilities of Wi-NG 5.0 in regards to packet captureing would be a good. I understand that we will be able to capture packets from all AP's at a remote site(RF Domain)with a single command, as well as stream the packets to a laptop running wireshark.

A How To on site to site VPN, with examples going between RFS switch's but also 3rd party like Cisco PIX

Hi John,

The how-to document for LDAP could stand being revised as we've added support for PEAP. Also nthing the need for more information on smart-rf. I'd also like to see the wired/wireless firewall document revisited as well. Improper configuration of the firewall drives a lot of support calls, specifically regarding improper configuration of ip arp trust or the like.

Edit: Adaptive AP FW update from the controller: a document outlining this feature and, more importantly, best practices for how many APs to do at once, automatic vs manual, etc. I will note that I'm strictly thinking in 4.x terms right now since AAP obviously isn't GA yet on 5.x, but it would certainly be a nice thing to have for when we add the AAP support.

Thanks for reaching out John!

WiNG 5 Smart RF is my next document to write. Self healing is for legacy compatability. SMART-RF is the way to go moving forward. Ill address it in detail in the next guide due out end of November. Thanks for your input. Regards, John Sellin

Hi John, L2 / L3 firewall with thin AP and Adaptive AP mode. SMART-RF, as you mentionned, is very important aswell. Matt

I have heard that there is some difficulty in configuring authentication using WIN 2008 Server. I believe this has something to do with the increased security on WIN 2008. Having a sample of the Windows config for both PEAP and TLS would be helpful

SMART RF vs Self-Healing/Neighbor Recovery Currently, we have Both options in the switch GUI, which is quite confusing. Or this might be just an update to the already existing SMART RF Howto