300-425 practice question 23 of 25

An engineer designs a new wireless network that uses a Cisco Catalyst 9800 Series wireless controller. The controller must be in a DMZ. The internal network is to be at the main on-premises data center of the customer. In addition, the customer wants to establish an EoIP tunnel to a Cisco 5520 WLC that is in a regional force. How must this requirement be incorporated into the design?

Full set: 286 questions

Domain Wired and Wireless Infrastructure

Answer options
A: Use Cisco IOS-XE code that supports encryption of the data plane on the Catalyst 9800 WLC.
B: Use AirOS code that supports encryption of the control plane on the 5520 WLC. Correct answer
C: Use Cisco IOS-XE code that supports encryption of the control plane on the Catalyst 9800 WLC.
D: Use AirOS code that supports encryption of the data plane on the 5520 WLC.
Correct Answer:
B. Use AirOS code that supports encryption of the control plane on the 5520 WLC.
Explanation

The question requires establishing a mobility tunnel between a new Catalyst 9800 WLC (IOS-XE) and a legacy 5520 WLC (AireOS). Catalyst 9800 controllers do not support the legacy EoIP tunnel protocol specified in the question. Instead, they use a modern CAPWAP-based mobility architecture, which has a mandatory DTLS-encrypted control plane. To enable this interoperability, the legacy 5520 WLC must be upgraded to an AireOS software version that supports this new, secure mobility peering with Catalyst 9800 controllers. Therefore, the design must incorporate using an AireOS code version that supports the required encrypted control plane for the mobility tunnel to be established.

Why Incorrect

A. Data plane encryption on the 9800 is an optional security feature, not a fundamental prerequisite for establishing the mobility tunnel itself.
C. All Catalyst 9800 software versions inherently use an encrypted control plane for mobility; this is a native function, not a specific design choice to be incorporated.
D. Data plane encryption on the 5520 is an optional security feature, not a fundamental prerequisite for establishing the mobility tunnel itself.

References

1. Cisco Catalyst 9800 Series Wireless Controllers Mobility Design Guide: In the "Mobility Architecture" section, it states, "The Catalyst 9800 WLCs do not support legacy mobility (also known as EoIP mobility). The Catalyst 9800 WLCs support only the new mobility (also known as CAPWAP mobility)." This confirms the premise of using EoIP is incorrect and a new mechanism must be used. (Page 6)

2. Mobility Configuration Guide, Cisco Wireless Controller, Release 8.10: In the "Information About Inter-Release Controller Mobility" section, it specifies, "For mobility peering between an AireOS controller and a Cisco Catalyst 9800 Series WLC, ensure that the AireOS controller is running Release 8.8.111.0 or a later release." It also states, "The mobility control plane between the Cisco AireOS Controller and the Cisco Catalyst 9800 Series WLC is secured by CAPWAP DTLS." This directly supports that the AireOS controller needs specific code to support the new, encrypted control plane.

3. Cisco Catalyst 9800 Series Wireless Controller Software Configuration Guide, Cisco IOS XE Bengaluru 17.6.x: In the "Mobility Interoperability" section of the "Configuring Mobility" chapter, it reiterates the AireOS version requirements and that the mobility tunnel is CAPWAP-based, which uses an encrypted control plane by default. This highlights that the capability must exist on the AireOS peer.

Scroll to Top