Latency issues b/w LWAP and WLC

[satya mothukuri]

Hi All,

My client is having enterprise network extended over 150 countries. We are connecting over DMVPN to all this countries.

We having problem in using WLC solution since, the latency is too high between my DC and remote offices.

We have radius server in every Brach office,  its AD authentication . Now I have 2 questions on this.

1. As am getting authenticated in my branch office itself, if the WAN link break, will the new users gets authenticated when the AP goes to standalone mode?
2. I have got an idea, to have distributed architecture on wireless. Instead of having WLCs in DC, we will have WLC’s at that Regional office, Ex for Africa we have 3 Regional office. I guess the latency will be low, with in Africa. Will this work in DMVPN ??

Regards,

Satya. Mothukuri

[Stephen Rodriguez]

Honestly,

   I'd leave the controllers in the DC, and just use FlexConnect for the branches.

FlexConnect deployment

HTH,

Steve

[satya mothukuri]

Thanks for your reply Stephen,

i got 1 answer for from your post. Thanks for that. 

Still the main issue is Latency. Many sites has Latency more than 200 ms. Can we increase the Latency >100 in WLC???

WAN Link

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.