Hi Ricardo,
Here is some info that shows the differences between Reap and H-Reap including supported AP's and Controllers. This should make the choice clearer;
Remote-Edge AP (REAP) with Lightweight APs and Wireless LAN Controllers (WLCs) Configuration Example
REAP mode enables a LAP to reside across a WAN link and still be able to communicate with the WLC and provide the functionality of a regular LAP. REAP mode is supported only on the 1030 LAPs at this point. This functionality will be included on a broader range of LAPs in the future.
From this doc;
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008069da69.shtml
H-REAP is only supported on the 1130AG and 1240AG access points and on the Cisco 2000 and 4400 Series Unified Controllers, the Catalyst 3750G Integrated Wireless LAN Controller Switch, the Cisco WiSM, and the Controller Network Module for Integrated Services Routers.
All LWAPP-based access points support this Split-MAC operation, often called Local Mode in system configuration interfaces (not to be confused with Local MAC LWAPP operations), but only the Aironet 1030 Remote-Edge Access Point (REAP) falls into the "Local MAC" operation category, clearly referred to as REAP during system configuration.
The 1030 REAP, while allowing for WAN-outage resilience and local traffic switching, may not satisfy all remote and branch office installation needs. Though the 1030 REAP provides for separation over the air (due to the support of multiple basic service set identifiers [BSSIDs]), it does not also have wired-side separation due to lack of 802.1Q support. Data from all WLANs land on the same wired subnet. Also, during a WAN failure, the 1030 ceases to offer service on all WLANs except the first one specified in the controller.
It is out of these two fundamental limitations that the H-REAP is born.
The Hybrid Remote-Edge Access Point
The Hybrid Remote-Edge Access Point, or H-REAP, is a new feature supported by both the 1131 and 1242 Aironet Access Points. Supported only in Cisco's Unified Wireless Network controller release version 4.0 or later, this software-selectable feature allows for the merging of both Split and Local MAC LWAPP operations for maximum deployment flexibility. Client traffic on H-REAPs may either be switched locally at the access point or tunneled back to a controller, depending on per-WLAN configuration. Further, locally switched client traffic on the H-REAP may be 802.1Q tagged to provide for wired-side separation. During a WAN outage, service on all locally switched, locally authenticated WLANs persists.
Note: H-REAP is supported only on the LWAPP-based 1131AG and 1242AG Access Points. Running 4.0 code or later, the 2000 and 4400 Series Controllers, Catalyst 3750G Integrated Controller Switch, Catalyst 6500 Series Wireless Services Module (WiSM), and Wireless LAN Controller Module (WLCM) for Integrated Services Routers (ISRs) all support this H-REAP functionality.
H-Reap Design and Deployment Guide
From this great cisco doc;
http://www.cisco.com/en/US/products/ps6521/products_tech_note09186a0080736123.shtml#req
Here is one other fact that is newer and differs from the H-Reap guide;
Q. What are the features of the Cisco Unified Wireless Network Software Release 4.0?
A. Remote access points in a Hybrid Remote-Edge Access Point (REAP) architecture expand from three to eight. With Cisco Unified Wireless Network Software Release 4.0.194.0, Hybrid REAP capabilities have been expanded to support up to eight lightweight access points.
Hybrid Remote Edge Access Point Support for 8 Access Points
From this good doc;
http://www.cisco.com/en/US/products/ps7206/prod_bulletin0900aecd805cff22.html
Hope this helps!
Rob
