Руководство По Проектированию для Cisco Cisco Aironet 350 Mini-PCI Wireless LAN Client Adapter
7-10
Enterprise Mobility 4.1 Design Guide
OL-14435-01
Chapter 7 Cisco Unified Wireless Hybrid REAP
Hybrid REAP
Deployment Considerations
The following section covers the various implementation and operational caveats associated with
deploying H-REAP APs.
deploying H-REAP APs.
WAN Link
For the H-REAP AP to function predictably, keep in mind the following with respect to WAN link
characteristics:
characteristics:
•
Latency—A given WAN link should not impose latencies greater than 100 ms. The AP sends
heartbeat messages to the WLC once every thirty seconds. If a heartbeat response is missed, the AP
sends five successive heartbeats (one per second) to determine whether connectivity still exists. If
connectivity is lost, the H-REAP AP switches to standalone mode (see
heartbeat messages to the WLC once every thirty seconds. If a heartbeat response is missed, the AP
sends five successive heartbeats (one per second) to determine whether connectivity still exists. If
connectivity is lost, the H-REAP AP switches to standalone mode (see
for operation mode definitions). The AP itself is relatively delay tolerant. However, at the client,
timers associated with authentication are sensitive to link delay, and thus a constraint of < 100 ms
is required. Otherwise, the client can timeout waiting to authenticate, which can cause other
unpredictable behaviors, such as looping.
timers associated with authentication are sensitive to link delay, and thus a constraint of < 100 ms
is required. Otherwise, the client can timeout waiting to authenticate, which can cause other
unpredictable behaviors, such as looping.
•
Bandwidth—WAN links should be at least 128 kbps for deployments where up to eight H-REAPs
are being deployed at a given location. If more than eight H-REAPs are deployed, proportionally
more bandwidth should be provisioned for the WAN link.
are being deployed at a given location. If more than eight H-REAPs are deployed, proportionally
more bandwidth should be provisioned for the WAN link.
•
Path MTU—WLC software Release 4.0 and later require an MTU no smaller than 500 bytes; this
applies to both the 1030 REAP and H-REAP APs
applies to both the 1030 REAP and H-REAP APs
NAC
Yes
Yes
No
CCKM Fast
Roaming
Roaming
No
No
No
PKC Fast Roaming
No
No
No
CAC and TSPEC
Yes
Yes
No
Client load
balancing
balancing
No
No
No
Peer-to-peer
blocking
blocking
Yes
No
No
WIDS
Yes
Yes
No
RLDP
Yes
Yes
No
RADIUS/TACACS
authentication
Yes
Yes
No
Radius/TACACS
accounting
Yes
Yes
No
Table 7-1
Supported Features and Authentication Types (continued)