CAPWAP Editor’s Report. Pat R. Calhoun Cisco Systems, Inc. Closed Issues. Issue 2: Potential Firmware Download Performance Issue. Raised by Transport AD, claiming that current protocol could cause firmware download to take some time. Added the following text to Transport Considerations:
Pat R. Calhoun
Cisco Systems, Inc.
“The lock step nature of the CAPWAP protocol's control channel can cause the firmware download process to take some time, depending upon the RTT. This is not expected to be a problem since the CAPWAP protocol allows firmware to be downloaded while the WTP provides service to wireless clients/devices.”
"Because there is no congestion control mechanism specified for the CAPWAP data channel, it is recommended that non-congestion-controlled traffic not be tunneled over CAPWAP. When a significant amount of non-congestion-controlled traffic is expected to be present on a WLAN, the CAPWAP connection between the AC and the WTP for that LAN should be configured to remain in Local MAC mode"
“The WTP also starts the ChangeStatePendingTimer timer (see Section 4.7).”
Needs to be changed to:
“The AC also starts the ChangeStatePendingTimer timer (see Section 4.7).”