What is the primary function of CAPWAP in a Cisco wireless network?

The primary function of the Control and Provisioning of Wireless Access Points (CAPWAP) protocol is to create a secure, standardized tunnel between lightweight access points (APs) and a Wireless LAN Controller (WLC). This tunneling mechanism encapsulates both control and data traffic. The CAPWAP control tunnel (UDP port 5246) is used for managing, provisioning, and monitoring the APs. The CAPWAP data tunnel (UDP port 5247) is used to forward wireless client traffic from the AP to the WLC for processing in a centralized data forwarding model. This architecture allows for centralized management and policy enforcement across the wireless network.

A. Provide DNS services: DNS is a separate network service for name resolution. CAPWAP may use DNS to discover a controller, but it does not provide DNS services itself.

C. Assign IP addresses: IP address assignment is the function of a DHCP server. While a WLC can be configured as a DHCP server, this is not a function of the CAPWAP protocol.

D. Filter multicast traffic: Multicast traffic management is a feature implemented on the WLC, not a primary function of the CAPWAP protocol, which simply transports the traffic.

1. Official Vendor Documentation: Cisco Wireless LAN Controller Configuration Guide, Release 8.5, "Information About CAPWAP" section. This section states, "CAPWAP, which is based on LWAPP, is a standard, interoperable protocol that enables a controller to manage a collection of wireless access points. [...] The CAPWAP protocol encapsulates the data between the controller and the access point inside a new IP header."

2. Official Vendor Documentation: Enterprise Mobility 8.5 Design Guide, Chapter: "Unified Wireless Network Architecture," Section: "Split-MAC Architecture." This guide explains, "The CAPWAP protocol is the key component of the Cisco Unified Wireless Network Split-MAC architecture. CAPWAP defines the communication protocol between the WLC and the AP. It provides the control and data plane transport..."

3. Peer-reviewed Academic Publications: Calhoun, P., et al. (2009). RFC 5415: Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification. IETF. Section 1, Introduction. The document states, "The protocol is designed to be flexible enough to support a variety of Access Point and Wireless Termination Point implementations. It accomplishes this by defining a generic encapsulation and transport mechanism." DOI: https://doi.org/10.17487/RFC5415