Which Tunnel Enables Seamless L3 Roaming Between Cisco WLCs?
Which tunnel type allows clients to perform a seamless Layer 3 roam between a Cisco AireOS WLC and a Cisco IOS XE WLC?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
It tests the specific protocol governing mobility tunnels, with the primary trap being the legacy assumption that Ethernet-over-IP (EoIP) is universally required for WLC-to-WLC communication.
This question evaluates understanding of inter-controller mobility tunnel protocols required for seamless Layer 3 client roaming across different Cisco WLC platforms. The community overwhelmingly agrees that CAPWAP is the correct mechanism when bridging AireOS and IOS XE controllers.
Candidates frequently select Ethernet over IP (Option D) based on older Airespace/AireOS documentation stating that dual-AireOS deployments use EoIP for mobility. They overlook the critical architectural shift where cross-platform compatibility (AireOS to IOS XE/C9800) explicitly requires CAPWAP instead.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Core Concept: Inter-Controller Mobility Tunnels
When a wireless client moves across different subnets (Layer 3 boundaries) while maintaining its session, Cisco wireless controllers establish a dedicated mobility tunnel between the anchor controller (original) and the foreign controller (new location). This tunnel ensures the client retains its original IP address and subnet association, enabling a truly seamless roaming experience.Protocol Selection: CAPWAP vs. EoIP
Historically, native AireOS WLCs communicated using Ethernet-over-IP (EoIP) for these mobility tunnels. However, Cisco modernized this architecture for interoperability. As noted by community experts, when integrating a legacy AireOS WLC with a modern Cisco IOS XE (Catalyst 9800) WLC, the platform automatically negotiates and establishes a CAPWAP tunnel instead of EoIP. This cross-platform requirement makes CAPWAP the definitive answer for mixed-environment deployments.Why Other Options Are Incorrect
- IPsec and VPN are security protocols used for encrypted site-to-site or remote-access connections, not for internal controller mobility data forwarding.
- Ethernet over IP (EoIP) is functionally correct only when connecting two identical AireOS WLCs. It lacks the necessary feature parity and negotiation capabilities required when pairing AireOS with IOS XE hardware/software stacks.
Official Reference
- https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-8/b_c9800_wireless_controller_technical_note_88.html
- Cisco Wireless LAN Controller Mobility Configuration Guide (Latest Release)
Exam Strategy
Always map the question's hardware/software combinations to their specific protocol requirements before selecting an answer. For Cisco wireless mobility questions, remember that pure AireOS environments rely on EoIP, but any deployment involving IOS XE or Catalyst 9800 controllers mandates CAPWAP for mobility tunnels.
Related Analysis
Practice All 350-401 Questions
Access 218 questions with complete answers and detailed explanations.
View Full 350-401 Practice Test →