Q: 5
An enterprise network administrator is asked to set up an experimental WLAN for a collaboration
project with a local service provider. The
WLAN must be anchored to a WLC in the service provider
data center using legacy mobility mode. After the configurations are completed on the WLCs and the
firewalls in the path, the data path mobility tunnel is failing to come up. What should be performed
by the administrator to debug the issue?
Options
Discussion
Option B. but only if the tunnel config is confirmed and not just a port/firewall issue. Some exam reports say port testing comes up, but for actual tunnel debug, WLC mapping commands matter more.
B. not C. Saw a similar question in some exam reports, pretty sure debugging mobility tunnels means running commands on the WLC itself. Telnet/port checks are more about connectivity, not actual debug output.
B imo
B , C is a trap here since checking ports isn't a debug step like mapping on the WLC.
B tbh, official Cisco guides and lab practice both show WLC debug commands are the move for mobility tunnel issues.
C/D? Honestly not sure, kinda feels like both could fit here.
B tbh, similar question came up in some practice. Super clear what the command does here.
C or D? I don't think a mapping command is the right fit for debugging a tunnel like this. Anybody else see these used?
Definitely B. Actual debug commands for mobility tunnels are run on the WLC itself, not by checking port access from a PC.
Had something like this in a mock, pretty sure it's B since actual debugging for mobility tunneling issues is done using commands on the WLC. Connectivity checks like C are good for port testing, but not real debug steps. Agree?
Be respectful. No spam.
