300-425 practice question 20 of 25
An engineer must repurpose a lab WLC appliance for use in the production environment of the enterprise. After the new WLC is configured with the information of the other WLC, the mobility tunnels are still not coming up. What is the reason?
Full set: 286 questionsDomain Mobility
When moving a Wireless LAN Controller (WLC) from a lab to a production environment, a primary concern is the compatibility of hardware platforms and software versions. Lab environments often utilize older or different hardware (e.g., an AireOS controller like a 5520) compared to a standardized production environment (e.g., Catalyst 9800 series). Mobility between different platforms, such as AireOS and Catalyst 9800, requires a specific configuration for Inter-Release Controller Mobility (IRCM), which uses CAPWAP for tunneling, not the traditional EoIP (Ethernet over IP). If an engineer simply configures the new WLC with the same mobility peer information used between homogeneous production controllers, the tunnels will fail due to this fundamental incompatibility in the underlying mobility architecture.
A. A firewall is blocking UDP port 16667 between the WLCs. This port is for EoIP data traffic. The control plane (UDP 16666) is established first. A failure of both tunnels suggests a more fundamental issue than a single blocked port.
B. The WLC management interfaces are in the same VLAN. This is not a problem. As long as the WLCs have unique IP addresses and can reach each other, being in the same VLAN/subnet is a valid configuration.
D. The mobility groups are different. While this would cause failure, the context of integrating a "lab" appliance into "production" strongly points toward a more complex issue like platform incompatibility rather than a simple configuration typo.
1. Cisco Catalyst 9800 and AireOS WLC Interoperability Deployment Guide
Section: "Mobility Tunnel". This document states
"The mobility control plane and data plane between the AireOS WLC and the Catalyst 9800 WLC is based on CAPWAP. The legacy mobility solution based on EoIP tunnels (UDP ports 16666 and 16667) is not supported." This confirms that different platforms use a different
incompatible tunneling mechanism by default.
2. Enterprise Mobility 8.5 Design Guide
Section: "Mobility Tunneling". This guide details the traditional EoIP tunneling mechanism used between homogeneous AireOS controllers. It specifies
"Mobility control packets are exchanged over UDP port 16666
and mobility data traffic is carried over an EoIP tunnel
which is UDP port 16667." This highlights the legacy method that would fail if used with a Catalyst 9800.
3. Cisco Wireless Controller Configuration Guide
Release 8.10
Chapter: "Configuring Mobility Groups"
Section: "Guidelines and Restrictions for Configuring Mobility Groups". This guide notes requirements for mobility group members
including software release compatibility
which underscores the importance of platform and version alignment for successful mobility tunnel establishment.
Keep practicing
Take the free 300-425 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other 300-425 practice questions
- Question 2A wireless consultant reviewing the installation of an old wireless network. The existing…
- Question 3A company is in the process of relocating to a new force space and ends out that the Inte…
- Question 4An engineer must deploy a wireless network in an open-plan environment that has three SSI…
- Question 5A hospital wireless environment was designed with these characteristics: • RF coverage • …
- Question 6A customer has this wireless design: • two Cisco Catalyst 9800 Series wireless controller…
- Question 7An engineer is implementing a wireless design for a service provider. The design includes…
