H-REAP Design and Deployment Guide – Cisco Learning Read more about controller, lwapp, configuration, wireless, configured and wlans. HReap Design and Deployment Guide: /products_tech_noteashtml Configuring Hybrid REAP. 27, 24, , 2/8/, Wireless LAN IPv6 Client Deployment Guide New! 55, 14, , 6/29/, H-Reap Design and Deployment Guide.

Author: Zuluhn Tuzshura
Country: Azerbaijan
Language: English (Spanish)
Genre: Video
Published (Last): 17 June 2006
Pages: 135
PDF File Size: 11.33 Mb
ePub File Size: 11.55 Mb
ISBN: 175-6-76855-925-1
Downloads: 68104
Price: Free* [*Free Regsitration Required]
Uploader: Voodookus

Because it should already know as it is configured this way before its primary WLC desifn offline for some reason. Andrew vonNagy June 29, at 8: And we are noticing the loop in to the network? Anonymous November 15, at 6: Andrew vonNagy December 13, at 2: Not exactly all of the changes make it into the release notes, but most of the major ones do.

Andrew vonNagy February 7, at 9: Anonymous June 24, at 2: Kristjan, No configuration is replicated between controllers. Anonymous March 1, at 1: I have not yet evaluated the Aerohive solution, but have some gear that I will be looking at soon. Andrew vonNagy August 26, at 2: This is still an open feature hrexp. Hi Andrew, Sorry, I missed that post Andrew vonNagy June 13, at Steve Williams June 27, at 7: Anonymous February 7, at We have tried to do load sharing by dividing groups to both controller.

I must admit though, I prefer your summaries to the matrix and release notes. In case of fail over if they go from group of one controller to default group of other, what will be impact?


Ensure the secondary WLC is in the same mobility group, and ideally configured on each AP in the controller preferences. Troy Martin June 10, at 5: It does seem like a refreshing approach, and I am curious to see how their system scales to large environments. The AP expects a response from the controller within 2 seconds, otherwise it sends up to 5 more hearbeat packets at 1 sec.

Anonymous December 13, at Hi Andrew Thank you for useful info and I really enjoy reading it. Could you kindly deploykent me to a Cisco doco that specifies the same pls?. Why must the latency not exceed 2 seconds v. Newer Post Older Post Home.

Revolution Wi-Fi: H-REAP Deployment Guidelines and Feature Limitations

Cheslin June 28, at 8: Same mobility group name is configured on the both controllers and we are following HREAP deployment requirements. First, several guidelines are recommended for successful deployment. KD July 2, at I can be reached at cbagley nmmu.

Anonymous November 16, at 9: Andrew vonNagy November 15, at 8: I can be reached at samuel. We have deployed H-reap with two centralized controllers at two different locations. We’re about to roll out wi-fi throughout our campus including remote sites and would like to adn central authentication with local switching. Are you sure it is neccesary to add the APs manually to the secondary controller?


What is H-REAP mode?

Anonymous July 2, at Local controller at remote site is deplomyent controller for the APs at remote site and centrally located controller is secondary controller for the APs at remote site. You would have to manually configure the information on both. Searching high and low for this but could not still get my hands on one. Seems like a refreshing approach. I think we’ll see some big announcements from those two in 1H In addition to feature limitations that apply to all H-REAP operational states, the following limitations also apply when the AP goes into standalone mode after losing connection to the controller.

Do we need to all H-reap groups on both controllers even there are no APs on other controller in that group? Curious about your thoughts on the controller-less solution from Aerohive? You should contact Cisco TAC for support and recommendations to remediate your issue. Administrators should understand these limitations when architecting a wireless network for remote offices, and may preclude the use of H-REAP if one or more of these features are depoyment to wireless network service in your organization.

So fail-over is not seamless. Hi Andrew, Thanks for the post.