Introduction
What is Remote Edge Access Point (REAP) and how is it configured on the Cisco 1030 Series Lightweight Access Point (LAP)?
Resolution
Remote Edge Access Point (REAP) mode enables an LAP to reside across a WAN link and still be able to communicate with the Wireless LAN Controller (WLC). REAP also provides the functionality of a regular LAP. REAP mode is only supported on the 1030 LAPs at this point. This functionality will be included on a broader range of LAPs in the future.
In order to provide this functionality, the 1030 REAP separates the Lightweight Access Point Protocol (LWAPP) control plane from the wireless data plane. WLCs are still used for centralized control and management in the same way that regular LWAPP-based APs are used, while all user data is bridged locally at the AP. Access to local network resources is maintained throughout WAN outages.
REAP APs support two modes of operation:
- Normal REAP mode
- Standalone mode
The LAP is set in normal REAP mode when the WAN link between the REAP AP and the WLC is up. When LAPs operate in normal REAP mode, they can support up to 16 WLANs.
Background Information
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.
In order to provide this functionality, the 1030 REAP separates the Lightweight Access Point Protocol (LWAPP) control plane from the wireless data plane. Cisco WLCs are still used for centralized control and management in the same way that regular LWAPP-based access points (APs) are used, while all user data are bridged locally at the AP. Access to local network resources is maintained throughout WAN outages.
REAP APs support two modes of operation:
- Normal REAP mode
- Standalone mode
The LAP is set in normal REAP mode when the WAN link between the REAP AP and the WLC is up. When LAPs operate in normal REAP mode, they can support up to 16 WLANs.
When the WAN link between the WLC and the LAP goes down, the REAP-enabled LAP switches to standalone mode. While in standalone mode, the REAP LAPs can support only one WLAN independently without the WLC, if the WLAN is configured with either Wired Equivalent Privacy (WEP) or any local authentication method. In this case, the WLAN that the REAP AP supports is the first WLAN that is configured on the AP, WLAN 1. This is because most of the other authentication methods need to pass information to and from the controller and, when the WAN link is down, this operation is not possible. In standalone mode, the LAPs support a minimal set of features. This table shows the set of features that a REAP LAP supports when it is in standalone mode in comparison with the features that a REAP LAP supports in normal mode (when the WAN link is up and communication to the WLC is up):
Features That a REAP LAP Supports in Normal REAP Mode and in Standalone Mode
The table shows that multiple VLANs are not supported on REAP LAPs in both modes. Multiple VLANs are not supported because REAP LAPs can only reside on a single subnet because they cannot perform IEEE 802.1Q VLAN tagging. Therefore, traffic on each of the service set identifiers (SSIDs) terminates on the same subnet as the wired network. As a result, data traffic is not separated on the wired side even though wireless traffic may be segmented over the air between SSIDs.
Refer to REAP Deployment Guide at the Branch Office for more information on REAP deployment, and how to manage REAP and its limitations.
Problem Type
Configure / Configuration issues
Products
LAP 1000
SW Features
Remote Edge Access Points (REAP)
Reference
Remote-Edge AP (REAP) with Lightweight APs and Wireless LAN Controllers (WLCs) Configuration Example
.