Руководство По Проектированию для Cisco Cisco Aironet 350 Mini-PCI Wireless LAN Client Adapter
C H A P T E R
7-1
Enterprise Mobility 4.1 Design Guide
OL-14435-01
7
Cisco Unified Wireless Hybrid REAP
As discussed earlier in this guide, the Cisco Unified Wireless solution uses the Lightweight Access Point
Protocol (LWAPP) between LWAPP APs (LAPs) and a WLAN WLC (WLC) to both manage the APs
and carry WLAN client traffic.
Protocol (LWAPP) between LWAPP APs (LAPs) and a WLAN WLC (WLC) to both manage the APs
and carry WLAN client traffic.
LAP deployments with one or more localized WLCs is typical for medium-to-large campus
environments. However, there may be cases in small branch locations where wireless connectivity is
required, but it is not practical to deploy a WLC. If a standard LAP is deployed at a branch with a
centralized WLC located at the main campus, the LAP establishes LWAPP connectivity across the WAN
to the main campus. All wireless user traffic at the branch traverses the WAN to the central WLC. This
may work well if a majority of the services being accessed by the branch resides at the main campus.
However, if wireless clients at the branch need to access local network resources (such as printers and
servers), this approach may not be desirable, as client traffic would have to traverse the WAN twice
(branch to central and central to branch) to reach a local device. Remote edge AP (REAP) and Hybrid
REAP (H-REAP) were developed for this reason.
environments. However, there may be cases in small branch locations where wireless connectivity is
required, but it is not practical to deploy a WLC. If a standard LAP is deployed at a branch with a
centralized WLC located at the main campus, the LAP establishes LWAPP connectivity across the WAN
to the main campus. All wireless user traffic at the branch traverses the WAN to the central WLC. This
may work well if a majority of the services being accessed by the branch resides at the main campus.
However, if wireless clients at the branch need to access local network resources (such as printers and
servers), this approach may not be desirable, as client traffic would have to traverse the WAN twice
(branch to central and central to branch) to reach a local device. Remote edge AP (REAP) and Hybrid
REAP (H-REAP) were developed for this reason.
Remote Edge AP
Remote edge APs (REAPs) are special purpose LWAPP-based APs that are designed to be deployed in
remote (branch) locations where:
remote (branch) locations where:
•
Wireless users at a branch or remote location require access to local network resources, and/or local
wireless connectivity needs to be preserved during WAN link outages.
wireless connectivity needs to be preserved during WAN link outages.
•
Limited WAN bandwidth exists between the central site and a remote location where local
connectivity is required. In this scenario, it would be impractical to tunnel all wireless user traffic
to a centralized WLC, only to be routed back (in standard IP packets) across a
bandwidth-constrained WAN link to the remote site.
connectivity is required. In this scenario, it would be impractical to tunnel all wireless user traffic
to a centralized WLC, only to be routed back (in standard IP packets) across a
bandwidth-constrained WAN link to the remote site.
•
Only a few APs are needed to provide adequate wireless coverage for a given location. This is often
more cost-effective than deploying and managing WLCs at every location, especially if there are
large numbers of small remote sites requiring wireless coverage.
more cost-effective than deploying and managing WLCs at every location, especially if there are
large numbers of small remote sites requiring wireless coverage.
REAP APs are designed to address these remote branch needs by decoupling the LWAPP control plane
from the WLAN data plane. This allows WLANs to be terminated locally on a Layer 2 switch while
LWAPP control and management data is sent back to a centralized WLC. In this way, the benefits of a
centralized architecture are preserved.
from the WLAN data plane. This allows WLANs to be terminated locally on a Layer 2 switch while
LWAPP control and management data is sent back to a centralized WLC. In this way, the benefits of a
centralized architecture are preserved.
provides a high level REAP topology diagram.