As per 7.3 mobility design guide,
http://www.cisco.com/en/US/docs/solutions/Enterprise/Mobility/emob73dg/ch7_HREA.html#wp1108009
For the FlexConnect AP to function predictably, keep in mind the following with respect to WAN link 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 FlexConnect AP switches to standalone mode (see Operation Modes 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 time-out waiting to authenticate, which can cause other unpredictable behaviors, such as looping.
•Bandwidth—WAN links should be at least 128 kbps for deployments when up to eight APs are being deployed at a given location. If more than eight APs are deployed, proportionally more bandwidth should be provisioned for the WAN link.
•Path MTU—An MTU no smaller than 500 bytes is required.
I will use the similar guideline for OEAP 600. I would use this model AP for ONLY for home user deployment (just extending corporate SSID to home). This model cannot be compare with standard AP model & replace their functionality as OEAP600 is limited in manyways & targeted for home environment.
HTH
Rasika
