40 locations, around 20-30 APs per location, 1 gig back from each site to the main site, minimizing cost. Client wants support of remote site survivability and reducing network loading. This implies H-REAP. We can't put controllers at each location due to cost. I'm thinking two 6506's with dual sups and three WISMs in each. My concern is HREAP. Here are some thoughts, let me know if you can think of some other limitations/issues.
* Enterprise SSID central auth / local switching, Guest SSID central switching / central auth
* If WAN goes down, Guest SSID will not be available.
* If WAN goes down, limited local authentication for Enterprise SSID will be available.
* With local switching L3 roaming is not supported, so if some location is using Layer 3 to the closet, this solution will not work.
* Location services? Design guide states "H-REAP is not designed to provide location services, so Cisco will not support location accuracy claims in H-REAP deployments." Have anyone implemented H-REAP with location services?
* RRM is fully supported in H-REAP (have anyone found it to be otherwise?)
* L2 CCKM fast-roaming is supported
* 20 H-REAP groups per controller with up to 25 in each group. Is this limitation still in place on latest 6.x code? If a site has more than 25 APs, I would create two or more H-REAP groups per site.
* Regarding 20 H-REAP groups per controller limitation, I believe this will create a problem for N+1 controller redundancy. If, let's say, one controller is used for redundancy for all APs, that controller would need all H-REAP groups configured on it which would exceed the 20 H-REAP group limitation. Am I correct to assume that with H-REAP support you need 2*N redundancy?
* Any other limitations?