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: Mubar Tejas
Country: Suriname
Language: English (Spanish)
Genre: Technology
Published (Last): 17 September 2014
Pages: 418
PDF File Size: 13.58 Mb
ePub File Size: 2.26 Mb
ISBN: 811-4-40680-551-3
Downloads: 73541
Price: Free* [*Free Regsitration Required]
Uploader: Gumuro

This is still an open feature gap.

What is H-REAP mode?

Anonymous June 24, at 2: I’ll be sure to post my thoughts on their product. Local controller at remote site is primary controller for the APs at remote site and centrally located controller is secondary controller for the APs at remote site.

Hi Andrew, Sorry, I missed that post If you continue to run into troubles, you should call Cisco TAC to investigate. Andrew vonNagy July 29, at 9: Anonymous February 7, at Cheslin June 28, at 8: Seems like a refreshing approach.

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 critical to wireless network service in your organization. BJ December 24, at 2: Would you able to advise me,by having APs in one group, what effects it would have on network? You should contact Cisco TAC for support and recommendations to remediate your issue.


And we are noticing the loop in to the network?

The AP expects a response from the controller within 2 seconds, otherwise it sends up to 5 more hearbeat packets at 1 sec. Kristjan, No configuration is replicated between controllers. If you have code version 7. I think we’ll see some big announcements from those two in 1H You may be interested in reading my post on that feature matrix as well: Andrew vonNagy June 29, at 8: Ensure the secondary WLC is in the same mobility group, and ideally configured on each AP in the controller preferences.

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

It does seem like a refreshing approach, and I am curious to see how their system scales to large environments. Motorola is trying to get their with their WiNG product but will take some time.

Anonymous November 16, at 9: Posted by Andrew deploymemt Nagy at 9: Because it should already know as it is configured this way before its primary WLC goes offline for some reason. Do we need to all H-reap deplohment on both controllers even there are no APs on other controller in that group?

Not exactly all of the changes make it into the release notes, but most of the major ones do. In this post, I will build on those basic fundamentals and provide more depth on the recommended deployment guidelines if you’re thinking about deoloyment H-REAP for remote sites.


Xirrus does something similar, with a controller in every AP and coordination among multiple APs. Troy Martin June 10, at 5: First, several guidelines are recommended for successful deployment.

What is H-REAP mode?

Hi Andrew Thank you for useful info and I really enjoy reading it. Anonymous November 15, at 6: You would have to manually configure the information on both. KD July 2, at Administrators should design a solution around these requirements as best as possible.

Hi Andrew, Great post with an awesome summary!

The WAN latency can affect the responsiveness of the heartbeat communications and can cause the AP to disconnect from the controller and go into standalone mode.

Look for Cisco and Aruba to make some headway in this area in as well. Anonymous December 13, at In versions prior to 7.

Should we be expecting seamless fail-over in this scenario? 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.