Question #28

How does CAPWAP communicate between an access point in local mode and a WLC?
A
The access point must not be connected to the wired network, as it would create a loop.
B
The access point must be connected to the same switch as the WLC.
C
The access point must directly connect to the WLC using a copper cable.
D
The access point has the ability to link to any switch in the network, assuming connectivity to the WLC.
English
Here's a detailed analysis of the CCNA exam question, explained for a beginner: --- ## CCNA Exam Question Analysis: CAPWAP Communication ### Question: How does CAPWAP communicate between an access point in local mode and a WLC? ### Question Type: Single Choice ### Options: - The access point must not be connected to the wired network, as it would create a loop. - The access point must be connected to the same switch as the WLC. - The access point must directly connect to the WLC using a copper cable. - The access point has the ability to link to any switch in the network, assuming connectivity to the WLC. ### Correct Answer(s): The access point has the ability to link to any switch in the network, assuming connectivity to the WLC. --- ### Detailed Analysis This question delves into the fundamental communication principles of a centralized wireless network architecture, specifically focusing on the relationship between an Access Point (AP) and a Wireless LAN Controller (WLC) using the CAPWAP protocol. Let's break down the key terms and concepts first: #### Key Technical Terms Explained: * **Access Point (AP):** Think of an AP as a wireless hub. It's a device that allows wireless devices (like your phone, laptop, or tablet) to connect to a wired network. It converts wireless signals into wired Ethernet signals and vice-versa. * **Wireless LAN Controller (WLC):** This is a centralized device that manages and controls many APs. Instead of configuring each AP individually, you configure the WLC, and it pushes the configurations to all connected APs. This makes managing large wireless networks much easier. * **CAPWAP (Control And Provisioning of Wireless Access Points):** This is a standard protocol that allows a WLC to manage and communicate with APs. It creates a "tunnel" between the AP and the WLC. * **Control Plane:** This part of CAPWAP handles management tasks, configurations, firmware upgrades, and AP discovery. It uses **UDP port 5246**. * **Data Plane:** This part handles the actual wireless client data. In many AP modes (like "Local Mode"), the client's wireless data is encapsulated (wrapped) in a CAPWAP tunnel and sent to the WLC for processing and forwarding to the wired network. It uses **UDP port 5247**. * **Local Mode (AP Operating Mode):** This is the most common and default operating mode for APs managed by a WLC. In Local Mode, the AP creates a CAPWAP tunnel to the WLC for *both* control traffic (management) and data traffic (from wireless clients). This means all wireless client data is sent to the WLC first, and then the WLC forwards it to the rest of the wired network. * **Wired Network:** This refers to the traditional network infrastructure that uses Ethernet cables, switches, and routers to connect devices. * **Switch:** A network device that connects other devices (like computers, servers, APs, and WLCs) on a local network. It learns where devices are located and forwards data only to the intended destination. * **Connectivity to the WLC:** This means that the AP can send and receive IP (Internet Protocol) packets to and from the WLC. This requires correct IP addresses on both devices, and that the network devices (switches, routers) in between are configured to allow traffic to flow between them. --- #### Analyzing Each Option: Let's look at each option provided and determine its correctness: **1. The access point must not be connected to the wired network, as it would create a loop.** * **Explanation:** This statement is incorrect. An AP *must* be connected to the wired network to function. It needs a physical connection (usually an Ethernet cable) to a switch so it can communicate with the WLC and provide network access to wireless clients. * **Loop:** A network loop occurs when there are multiple active paths between two devices or networks, which can cause data packets to circulate endlessly, leading to network congestion and failure. While loops are a concern in network design, simply connecting an AP to a switch does not inherently create a loop. APs are typically "end devices" from a Layer 2 perspective, similar to a computer. Proper network design principles, such as using Spanning Tree Protocol (STP) on switches, prevent loops in the network. * **Why it's wrong:** An AP cannot operate without a wired connection, and connecting it correctly does not create a loop. **2. The access point must be connected to the same switch as the WLC.** * **Explanation:** This statement is also incorrect. While it's *possible* for an AP and a WLC to be connected to the same switch, it's not a requirement. CAPWAP is an IP-based protocol, meaning it operates at Layer 3 (the Network Layer) of the OSI model. As long as there is **IP connectivity** between the AP and the WLC, they can communicate. * **IP Connectivity:** This means that the AP can "ping" (send a test message to) the WLC's IP address, and vice versa. This connectivity can be established across multiple switches, routers, and even across different physical locations (like a WAN link), as long as the network infrastructure is properly configured to route CAPWAP traffic (UDP ports 5246 and 5247) between them. * **Why it's wrong:** Physical proximity or being on the same switch is not a requirement for IP-based communication. **3. The access point must directly connect to the WLC using a copper cable.** * **Explanation:** This is incorrect and highly impractical. WLCs are typically located in a central data center or a main wiring closet, managing potentially hundreds or thousands of APs spread throughout a building or campus. Directly connecting each AP to the WLC with a dedicated cable would require an immense number of cables and ports on the WLC, making it unscalable and inefficient. * **How it actually works:** As explained with CAPWAP, the communication happens over the existing IP network infrastructure (switches, routers). The AP connects to the nearest network switch, and that switch, along with other network devices, routes the CAPWAP traffic to the WLC. * **Why it's wrong:** Direct physical connection is not how centralized wireless architectures are designed or implemented. **4. The access point has the ability to link to any switch in the network, assuming connectivity to the WLC.** * **Explanation:** This is the **correct** statement and accurately describes how CAPWAP communication works in a centralized wireless environment. * **Any Switch:** An AP simply needs to be connected to *a* switch in the network. This switch could be in the same wiring closet, on a different floor, or even in a different building. * **Assuming Connectivity to the WLC:** The critical condition is that once connected to *any* switch, the network must be configured such that the AP can establish IP communication with the WLC. This means: * The AP gets an IP address (usually via DHCP). * The AP can resolve the WLC's hostname or has its IP address configured. * Routers and switches in between are correctly configured to forward traffic between the AP's subnet and the WLC's subnet. * No firewalls are blocking CAPWAP's UDP ports 5246 and 5247. * **Why it's correct:** This option correctly emphasizes the IP-based nature of CAPWAP, allowing for flexible network deployment where APs can be distributed widely across the network, as long as they can reach the central WLC over the IP network. ### Conclusion The key takeaway for this question is that CAPWAP, as an IP-based protocol, provides a flexible and scalable way for APs and WLCs to communicate. Their physical location relative to each other is not as important as their logical (IP) connectivity across the wired network. An AP can connect to any switch, and as long as that connection allows it to reach the WLC via IP, the centralized management and data tunneling will function correctly.
日本語
ネットワークエンジニアの視点から、Cisco CCNA試験で頻出となる「CAPWAP(Control and Provisioning of Wireless Access Points)」の仕組みについて詳細に解説します。 --- # CAPWAPによるAPとWLC間の通信メカニズム解析 ### 1. CAPWAPの基本概念 CAPWAPは、集中管理型無線LANアーキテクチャにおいて、**アクセスポイント(AP)**と**ワイヤレスLANコントローラ(WLC)**の間で制御信号とユーザーデータを転送するための標準プロトコルです。 ローカルモード(Local Mode)で動作するAPは、自身でトラフィックを転送せず、すべてのデータをCAPWAPトンネルを介してWLCへ送ります。 --- ### 2. 2つの独立した通信チャネル CAPWAP通信の最大の特徴は、**「コントロールプレーン」**と**「データプレーン」**を明確に分離している点です。試験対策として、以下のポート番号と役割を完全に暗記する必要があります。 #### ① CAPWAP コントロールチャネル (Control Plane) * **プロトコル/ポート:** `UDP 5246` * **役割:** APの設定、ファームウェアの更新、ステータスの監視、IDSの情報共有など、管理用通信に使用されます。 * **セキュリティ:** デフォルトで **DTLS (Datagram Transport Layer Security)** によって暗号化されており、管理情報の秘匿性が確保されています。 #### ② CAPWAP データチャネル (Data Plane) * **プロトコル/ポート:** `UDP 5247` * **役割:** 無線クライアント(スマホやPC)が送受信する実際のデータトラフィックを運びます。 * **カプセル化:** クライアントの802.11フレームはCAPWAPヘッダーでカプセル化(IP/UDPパケット化)され、WLCまで運ばれます。 * **セキュリティ:** デフォルトでは暗号化されていません(DTLSはオプション)。これはスループット(転送速度)を優先するためです。 --- ### 3. スプリットMAC(Split MAC)アーキテクチャ CAPWAP通信は「スプリットMACアーキテクチャ」に基づいています。これは、無線LANの機能をAPとWLCで分担する仕組みです。 * **AP側が担当する機能(リアルタイム処理):** * ビーコン(Beacon)の送信 * フレームの確認応答(ACK) * プローブ応答(Probe Response) * **WLC側が担当する機能(非リアルタイム処理):** * クライアントの認証 * セキュリティ管理(ポリシー適用) * モビリティ管理(ローミング) --- ### 4. ローカルモード(Local Mode)における動作 設問にある「Local Mode」は、Cisco APのデフォルトの動作モードです。このモードでは以下の挙動となります。 1. **トンネリング:** APに接続したクライアントの全通信は、CAPWAPデータチャネルを通じてWLCに「トンネリング」されます。 2. **スイッチング:** クライアントのトラフィックが有線ネットワークに送り出されるのは、APが接続されているスイッチではなく、**WLCが接続されているスイッチのインターフェース**からになります。 3. **利点:** ネットワーク全体のセキュリティポリシーを一括管理でき、VLAN設定などをAP側のスイッチで個別に行う必要がなくなります。 --- ### 5. 試験対策ポイント(まとめ) | 項目 | 詳細 | | :--- | :--- | | **コントロールポート** | **UDP 5246** (暗号化あり) | | **データポート** | **UDP 5247** (暗号化なし/オプション) | | **暗号化プロトコル** | **DTLS** | | **カプセル化** | レイヤ2の802.11フレームをレイヤ3のIPパケットに包む | | **ローカルモード** | 全トラフィックをWLCへ転送する(集中管理) | **エンジニアからのアドバイス:** CCNA試験では「ポート番号の入れ替え(5246と5247)」や「TCPかUDPか」を問うひっかけ問題がよく出題されます。**「管理(Control)はシロ(46)く、データ(Data)はシナ(47)やかに」**といった語呂合わせなどで、確実にUDPポート番号を覚えておくことを推奨します。
繁體中文
這是一題關於 Cisco 無線網路架構(Wireless Architecture)的核心觀念題。在 CCNA 考試中,理解 **CAPWAP (Control and Provisioning of Wireless Access Points)** 協議以及 **AP 模式(AP Modes)** 的運作方式至關重要。 以下是針對該考題的專業技術解析: --- # 📝 考題解析:CAPWAP 在 Local Mode AP 與 WLC 間的通訊機制 ### 1. 核心定義:什麼是 CAPWAP? CAPWAP 是一種標準化的網路協定(基於 RFC 5415),允許無線控制器(WLC)集中管理多個輕量級存取點(Lightweight APs)。它主要建立兩條獨立的「隧道」(Tunnels)來處理不同類型的流量: * **控制平面 (Control Plane):** 使用 **UDP 連接埠 5246**。用於傳輸管理訊息,例如組態設定、韌體更新、AP 狀態監控等。此流量預設會經過 DTLS 加密。 * **資料平面 (Data Plane):** 使用 **UDP 連接埠 5247**。用於傳輸無線用戶端(Client)的實際數據流量。 --- ### 2. 本地模式 (Local Mode) 的運作特性 當 Cisco AP 處於 **Local Mode**(這是 AP 的預設模式)時,其通訊行為具有以下關鍵特徵: #### A. 集中式交換 (Centralized Switching) 在 Local Mode 下,AP **不會**在本地端直接將用戶數據轉發到當地的交換機(Switch)。相反地,AP 會將所有接收到的無線用戶端流量(802.11 Frames)封裝在 CAPWAP 資料隧道中,並傳送至 WLC。 #### B. 流量封裝流程 1. **封裝:** AP 接收到來自手機或筆電的 802.11 無線影格。 2. **隧道傳輸:** AP 將該影格加上 CAPWAP 標頭,透過 UDP 5247 傳送給 WLC。 3. **解封裝:** WLC 接收到封包後,移除 CAPWAP 標頭,將其還原為 802.3 乙太網路影格。 4. **轉發:** WLC 根據 VLAN 配置,將流量轉發到核心網路。 --- ### 3. 通訊架構關鍵點總結 | 項目 | 說明 | | :--- | :--- | | **傳輸協議** | CAPWAP (基於 UDP) | | **控制通道 (Control)** | UDP Port **5246** | | **資料通道 (Data)** | UDP Port **5247** | | **流量路徑** | 所有用戶數據必須經過 WLC (Centralized) | | **主要優點** | 集中管理安全性、動態射頻管理 (RRM)、無縫漫遊 | | **潛在缺點** | 若 WLC 斷線或 WAN 頻寬不足,Local Mode AP 將無法處理用戶流量 | --- ### 4. 專家視角:考試重點提醒 在回答此類考題或在實務操作時,請務必記住以下三點: 1. **區分 Local Mode 與 FlexConnect Mode:** * **Local Mode:** 數據全部回傳 WLC(適合總部/大型校園)。 * **FlexConnect Mode:** 數據可以在本地交換(適合分公司/遠端辦公室,以避免 WAN 頻寬浪費)。 2. **分層架構:** CAPWAP 讓 AP 專注於物理層與即時的 MAC 層處理,而將較重的管理邏輯交給 WLC,這稱為 **Split-MAC 架構**。 3. **MTU 問題:** 由於 CAPWAP 封裝會增加額外的標頭(Header),有時會導致 IP 封包過大,因此在中間網路設備上可能需要考慮 **MTU (Maximum Transmission Unit)** 的調整或分段。 ### 結論 在 Local Mode 下,AP 與 WLC 之間的通訊是透過 **CAPWAP 隧道** 進行的。所有來自無線用戶端的數據都會被封裝並傳送到 WLC 進行處理。若要正確回答此題,應選擇提到 **「透過 CAPWAP 資料隧道將所有用戶流量封裝至 WLC」** 或 **「使用 UDP 5246/5247 進行通訊」** 的選項。
简体中文
这是一道关于思科无线架构中 **CAPWAP(Control and Provisioning of Wireless Access Points)** 协议核心工作机制的经典 CCNA 考题。 作为一名网络工程师,我们需要从 CAPWAP 的隧道机制、端口号以及本地模式(Local Mode)的数据转发特性三个维度来深度解析。 --- ### 考题解析:CAPWAP 在 Local Mode AP 与 WLC 间的通信机制 #### 1. CAPWAP 协议概览 CAPWAP 是思科统一无线架构(Unified Wireless Architecture)的基础。它的主要作用是在轻量级访问点(LAP)和无线控制器(WLC)之间建立安全通道,实现集中化管理。 #### 2. 双隧道机制(核心考点) CAPWAP 通信实际上由两个独立的 **UDP 隧道** 组成: * **控制平面(Control Plane):** * **用途:** 用于 WLC 对 AP 的管理、配置下发、固件更新及状态监控。 * **端口:** **UDP 5246**。 * **特性:** 该隧道通常经过 DTLS 加密,确保管理流量的安全。 * **数据平面(Data Plane):** * **用途:** 用于封装客户端(终端设备)产生的业务数据流量。 * **端口:** **UDP 5247**。 * **特性:** 在 Local Mode 下,所有客户端的 802.11 无线帧都会被封装在 CAPWAP 数据隧道内。 #### 3. 本地模式(Local Mode)的转发特性 在 Local Mode(这是思科 AP 的默认模式)下,通信遵循以下逻辑: 1. **流量集中化:** AP 不会在本地对客户端流量进行交换(Switching)。即使两个连接在同一台 AP 上的客户端互相通信,数据包也必须先通过 CAPWAP 隧道发送到 WLC。 2. **隧道封装:** AP 接收到客户端的 802.11 无线帧,将其封装在 CAPWAP 报文中,外层加上 IP/UDP 头(源为 AP IP,目的为 WLC IP)。 3. **解封装与转发:** WLC 接收到 CAPWAP 包后,剥离隧道头部,将内部的 802.3 以太网帧根据 VLAN 配置转发到有线网络中。 #### 4. 通信流程总结 当一个处于 Local Mode 的 AP 与 WLC 通信时: * **管理层面:** 维持一个持久的 UDP 5246 链接。 * **数据层面:** 维持一个持久的 UDP 5247 链接,所有用户流量“绕道”WLC。 * **分片处理:** 由于 CAPWAP 增加了额外的头部(通常约为 44 字节),CAPWAP 具备分片和重组功能,以适应标准 1500 字节的 MTU。 --- ### 关键知识点对比(考试避坑指南) | 特性 | 控制隧道 (Control) | 数据隧道 (Data) | | :--- | :--- | :--- | | **UDP 端口号** | **5246** | **5247** | | **传输内容** | 配置、CAPWAP 状态机 | 用户上网流量 | | **默认加密** | 是 (DTLS) | 否 (可开启 DTLS) | | **Local Mode 行为** | 必须通过 WLC | **必须**通过 WLC | | **FlexConnect 行为** | 必须通过 WLC | 可在本地交换(无需经过 WLC) | --- ### 专家总结 在 CCNA 考试中,如果题目问到 CAPWAP 如何通信,最标准的答案通常包含: 1. **使用两个 UDP 端口:5246(控制)和 5247(数据)。** 2. **在 Local Mode 下,所有数据流量都会被封装在隧道中发送至 WLC。** 3. **它实现了管理平面与数据平面的分离,但数据流向是集中化的。** **建议:** 牢记 5246 和 5247 这两个数字,这是考试中最常出现的干扰项(有时会故意写反,或者给成旧版的 LWAPP 端口 12222/12223)。