latency betw WLC & AP (100ms or 300ms?)

Unanswered Question
Oct 3rd, 2009


[From H-REAP deployment guide]


Roundtrip latency must not exceed 300 milliseconds (ms) between the access point and the controller,

and LWAPP or CAPWAP control packets must be prioritized over all other traffic.

[From Enterprise Mobility 4.1]


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. 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.

So which is correct? one Cisco AS engineer told me that with WLC6.0, delay can be 300ms. WLC prior to 6.0 is 100ms. But i can't find any documentation on this.

Any comments greatly appreciated.


Eng Wee

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
weterry Sat, 10/03/2009 - 09:50

Don't qoute me on this, but I think in 5.x is where the 100ms latency was increased to 300ms.

The 4.1 deployment guide is accurate, for 4.1. It should not be greater than 100ms. The HREAP Deployment Guide that I found, is written for 5.1, and it mentions 300ms.


This Discussion



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode