Руководство По Проектированию для Cisco Cisco Aironet 350 Mini-PCI Wireless LAN Client Adapter
7-16
Enterprise Mobility 4.1 Design Guide
OL-14435-01
Chapter 7 Cisco Unified Wireless Hybrid REAP
Hybrid REAP
Figure 7-9
H-REAP with NAT/PAT
RADIUS Assigned VLANs
RADIUS-based VLAN assignment is supported for those H-REAP WLANs that are central-switched.
This feature is not available when the H-REAP is in Standalone mode.
This feature is not available when the H-REAP is in Standalone mode.
Web Authentication (Guest Access)
WLC-based web authentication may be used with local switched WLANs so long as the H-REAP is in
Connected mode. Otherwise, those WLANs using web authentication are unavailable when the H-REAP
is in Standalone mode.
Connected mode. Otherwise, those WLANs using web authentication are unavailable when the H-REAP
is in Standalone mode.
Restricting Inter-Client Communication
Two or more clients, associated to a WLAN that is locally switched (by an H-REAP), are not prevented
from communicating with one another even if Peer-to-Peer Blocking mode is enabled on the WLC. This
is because locally switched wireless traffic does not go through the WLC.
from communicating with one another even if Peer-to-Peer Blocking mode is enabled on the WLC. This
is because locally switched wireless traffic does not go through the WLC.
Those H-REAP WLANs that are central switched have inter-client communication restricted based on
the Peer-to-Peer Blocking mode setting on the WLC.
the Peer-to-Peer Blocking mode setting on the WLC.
H-REAP Scaling
•
Per-Site—There is no limit to the number of H-REAPs that may be deployed per remote location.
However, keep in mind that deployment of a local WLC is strongly recommended if:
However, keep in mind that deployment of a local WLC is strongly recommended if:
–
,
roaming performance can be impacted by the availability and link characteristics of the WAN
backhaul. This is true even when key caching methods, such as 802.11i or Cisco CCKM, are
employed because they are not currently supported with H-REAP.
backhaul. This is true even when key caching methods, such as 802.11i or Cisco CCKM, are
employed because they are not currently supported with H-REAP.
–
WAN reliability/performance—Branch WLAN topologies that depend on authentication, radio
resource management, and other upstream services are only as good as the availability of the
WAN backhaul. Roundtrip delays must limited to no more than 100 ms and proper QoS queuing
mechanisms must be available to manage congestion.
resource management, and other upstream services are only as good as the availability of the
WAN backhaul. Roundtrip delays must limited to no more than 100 ms and proper QoS queuing
mechanisms must be available to manage congestion.
•
Per-WLC—There are no restrictions with regard to the number of APs that can operate in H-REAP
mode. The total number of H-REAP APs per WLC is bound only by the maximum number of LAPs
that are supported for a given WLC model.
mode. The total number of H-REAP APs per WLC is bound only by the maximum number of LAPs
that are supported for a given WLC model.
NAT
Branch
Servers
H-REAP
WCS
LWAPP
Branch
190702
Corporate Central
Branch
Employee
Corporate
Servers
inside outside
inside
outside
NAT or PAT