mobility tunnel allows the controllers to share information about client devices, facilitating seamless roaming as clients move between access points managed by different controllers.
CAPWAP is used primarily for communication between WLCs and their associated access points. It manages the configuration, control, and management of APs. While CAPWAP tunnels do carry data and control traffic between APs and WLCs, they are not specifically used to facilitate intercontroller roaming.
The answer is C. Regardless if the WLCs use CAPWAP (used by 9800s) or EoIP (used by AireOS), the tunnels they create are still referred to as "mobility" tunnels.
https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-8/b_c9800_wireless_controller-aireos_ircm_dg.pdf
Why would be CAPWAP required for intercontroller DB entry exchange ( it's just a record of AP association) , connection over EoIP would suffice, whereas it's required as transport in intersubnet case when AP continues to be anchored to original WLC, I am inclining to C now.
A
Intercontroller Roaming, which occurs when the wireless LAN interfaces of controllers are on the same IP subnet. CAPWAP tunnel
Intersubnet Roaming, which occurs when the wireless LAN interfaces of controllers are on different IP subnets. Mobility tunnel
The key is "inter-controller". Each type is used for a different use case: "mobility" tunnel is used for inter-subnet roaming CAPWAP tunnel for inter-controller roaming.
https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/config-guide/b_wl_16_10_cg/mobility.html
CAPWAP tunnels are used between AP(s) and WLC(s)
Mobility tunnels are used between WLCs to enable Intercontroller Layer 3 Roaming
Check figure 3: https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-10/config-guide/b_cg810/overview.html#:~:text=Figure%203.-,Intercontroller%20Layer%203%20Roaming,-Layer%203%20roaming
A Layer 3 intercontroller roam involves building an additional CAPWAP tunnel between the client’s initial WLC and the WLC to which it has roamed. The tunnel transmits the data to and from the client just like it is still associated with the original IP subnet and WLC.
When a Layer 3 roam happens, the original WLC is called the anchor controller, and the current WLC where the roamed client is reassociated is called the foreign controller. The client is anchored to the original WLC even if it roams to different controllers.
To enable inter-controller roaming (or inter-controller mobility) between two WLAN Controllers (WLCs), a Layer 3 tunnel is typically required. This type of tunnel allows client session information to be securely transferred between the controllers, facilitating seamless handoff of clients as they move between different areas covered by different controllers within the same mobility domain.
Ans: A
It is asking for, "TYPE" of tunnel. Not the protocol used. C is the most specific answer to this question - always go exactly what is being asked.
https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/213913-building-mobility-tunnels-on-catalyst-98.html
"Recall that Cisco controllers use CAPWAP tunnels to connect with lightweight APs. CAP- WAP tunnels are also built between controllers for Layer 3 roaming. The tunnel tethers the client to its original anchor controller (and original IP subnet), regardless of its location or how many controllers it roams through." - OCG
On page 551 of the OCG you can also see a clear picture of the tunnel between the 2 WLCs
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Shri_Fcb10
Highly Voted 7 months, 3 weeks agoExamTaker1017
Most Recent 1 month, 3 weeks agoissa1430
2 months, 1 week agozbeugene7
3 months, 1 week agozbeugene7
3 days, 6 hours agozbeugene7
3 months, 1 week agofelix_simon
3 months, 1 week agochiacche
3 months, 3 weeks agozbeugene7
3 months, 3 weeks agoAbdullahMohammad251
3 months, 4 weeks agoWanessamgp
6 months, 1 week agoapetrov
6 months, 3 weeks agoTKSuperstar
6 months, 3 weeks ago[Removed]
7 months, 1 week ago[Removed]
7 months, 2 weeks agojaurelius1420
8 months agomasrur
8 months, 1 week agoAdalberto
8 months, 1 week agostefanxradu
8 months, 2 weeks ago