Техническая Инструкция для Cisco Cisco 2000 Series Wireless LAN Controller
REAP Deployment Guide at the Branch Office
Document ID: 81784
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
1030 REAP Architecture Introduction
Prerequisites
Requirements
Components Used
Conventions
1030 REAP Architecture Introduction
When Should REAP APs be Used?
Deploy REAP
Basic REAP Priming Functions
REAP−to−Controller Link Requirements
REAP Limitations
WLANs
Security
Network Address Translation (NAT)
Quality of Service (QoS)
Roaming and Client Load−Balancing
Radio Resource Management (RRM)
Rogue Detection and IDS Functionality
REAP Limitation Summary
Manage REAP and Central WLAN Architecture
Centralized WLAN Architecture with REAP
Appendix A
Appendix B
Related Information
Deploy REAP
Basic REAP Priming Functions
REAP−to−Controller Link Requirements
REAP Limitations
WLANs
Security
Network Address Translation (NAT)
Quality of Service (QoS)
Roaming and Client Load−Balancing
Radio Resource Management (RRM)
Rogue Detection and IDS Functionality
REAP Limitation Summary
Manage REAP and Central WLAN Architecture
Centralized WLAN Architecture with REAP
Appendix A
Appendix B
Related Information
Introduction
This document provides information that needs to be taken into consideration when you deploy Remote−Edge
Access Point (REAP). Refer to Remote−Edge AP (REAP) with Lightweight APs and Wireless LAN
Controllers (WLCs) Configuration Example for basic REAP configuration information.
Access Point (REAP). Refer to Remote−Edge AP (REAP) with Lightweight APs and Wireless LAN
Controllers (WLCs) Configuration Example for basic REAP configuration information.
Note: The REAP feature is supported up to WLC Release 3.2.215. From WLC Release 4.0.155.5, this
functionality is called Hybrid REAP (H−REAP) with few enhancements until 7.0.x.x. From 7.2.103 release,
this feature is called FlexConnect.
functionality is called Hybrid REAP (H−REAP) with few enhancements until 7.0.x.x. From 7.2.103 release,
this feature is called FlexConnect.
Traditional Cisco Lightweight Access Point Protocol (LWAPP)−based access points (APs), (also known as
LAPs), such as the 1010, 1020, and the 1100 and 1200 Series APs that run Cisco IOS® Software Release
12.3(7)JX or later, allow for central management and control through Ciscos Wireless LAN Controllers
(WLCs). Also, these LAPs permit administrators to leverage the controllers as single points of wireless data
aggregation.
LAPs), such as the 1010, 1020, and the 1100 and 1200 Series APs that run Cisco IOS® Software Release
12.3(7)JX or later, allow for central management and control through Ciscos Wireless LAN Controllers
(WLCs). Also, these LAPs permit administrators to leverage the controllers as single points of wireless data
aggregation.
While these LAPs allow controllers to perform advanced features such as QoS and access control list (ACL)
enforcement, the requirement of the controller to be a single point of ingress and egress for all wireless client
traffic can hinder, rather than enable, the ability to adequately meet user needs. In some environments, such as
remote offices, the termination of all user data at controllers can prove too bandwidth intensive, especially
when limited throughput is available over a WAN link. Also, where the links between LAPs and WLCs are
enforcement, the requirement of the controller to be a single point of ingress and egress for all wireless client
traffic can hinder, rather than enable, the ability to adequately meet user needs. In some environments, such as
remote offices, the termination of all user data at controllers can prove too bandwidth intensive, especially
when limited throughput is available over a WAN link. Also, where the links between LAPs and WLCs are