H-REAP remote site limitiations

Unanswered Question
Sep 29th, 2009

H-REAP has been designed (according to Cisco) for small branch deployments, where a WLC may not be justifiable. It does not appear to be designed to handle medium to large deployments (say, 25 to a few 100 APs). Limitiations are as follows:

* AP Groups: No limit specified but I have been able to add 200, which would be sufficient.

* WLANs: Up to 512 allowed which is sufficient.

* H-REAP Groups: Up to 20 groups of 25 APs. A reasonable number but not really enough.

* RADIUS Servers: Up to 17. As we use 2 x per site, that would allow 8 x remote site. Unfortunately not enough.

With manufacturers like Aruba supporting up to 8000 remote APs on their top WLC I would expect these limits to be higher on their flagship WLC. Can anyone suggest how to support a few dozen H-REAP sites with 10 - 75 APs each on the 5508.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
SHANNON WYATT Tue, 09/29/2009 - 16:15

I've done a 300 plus AP deployment in H-Reap mode, but we used several controllers. We also did central authentication for their locally switched SSID. This does bring in the possibility of an outage in the case of a WAN outage, but for this customer that wasn't a big issue since the majority of the application that would be accessed on the WiFi would be down in the event of a WAN outage, plus they had VPN backup.

I would have liked more H-REAP groups, but we worked around it for small locations.

If you had a bunch of small locations with local auth you would be in trouble, but the other limitaions are minor.

scott.stapleton Tue, 09/29/2009 - 17:45

Well the biggest limitation I mentioned above was with the RADIUS server limit which obviously is an issue with local RADIUS authentication particularly if you want to allow new 802.1x connections during a WAN outage. Hopefully the controllers will move this way in the future.


This Discussion



Trending Topics - Security & Network