Communication between APs and controlleurs under 100ms
I heard from a Cisco representative that communication between the APs and the controlleur(s) should be less than 100ms. Did anyone experienced problems by not respecting that restriction?
This restriction would have an impact on our design. Originaly we were planning to host the controlleurs as well as the WCS on our datacenter and have the APs communicate with the controlleurs/WCS via WAN. We would like to avoid having a controlleur for each site since the sites won't need more than 5-6 APs each...
Re: Communication between APs and controlleurs under 100ms
Have a look at the specs in this H-Reap design guide. It may help explain this restriction and the effect it will have on the "Wireless Rollout";
H-REAP WAN Considerations
Because the H-REAP has been designed specifically to operate across WAN links, it has been optimized for such installations. Though H-REAP is flexible when it comes to these remote network design scenarios, there are still a few guidelines that need to be honored when architecting a network with H-REAP functionality.
H-REAPs may not be placed across WAN links any slower than 128 kbps.
Roundtrip latencies between H-REAP and the controller may not exceed 100 ms.
Between the access point and the controller, a minimum of a 500 byte MTU is supported.
In order to ensure that support for this stated latency limitation is in place, it is strongly recommended that between the access point and controller, priority be configured in the intermediary infrastructure to elevate LWAPP control (UDP port 12223) to the highest priority queue available. Without priority placed on LWAPP control, spikes in other network traffic will very likely cause H-REAP access points to frequently shift from connected to Standalone modes as WAN link congestion prevents access point/controller messages (and keep-alives) from being delivered.
Frequent H-REAP flapping causes serious connectivity issues. Without proper network prioritization in place, it may be prudent to place controllers at remote sites to ensure consistent and stable wireless access.
Note: Whether H-REAP is configured to tunnel client traffic back to the controller or not, the LWAPP data path is used to forward all 802.11 client probes and authentication/association requests, RRM neighbor messages, and EAP and web authentication requests back to the controller. As such, ensure that LWAPP data (UDP port 12222) is not blocked anywhere between the access point and controller.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...