A user is having trouble connecting to an AP managed by a standalone Mobility Controller (MC). What can you do to get detailed logs and debugs for that user's client?

Question

Options

• AIn the MC CLI, set up a control plane packet capture and filter for the client's IP address.
• BIn the MC CLI, set up a data plane packet capture and filter for the client's MAC address.
• CIn the MC UI's Traffic Analytics dashboard, look for the client's IP address.
• DIn the MC UI's Diagnostics > Logs pages, add a "user-debug" log setting for the client's MAC

• A
  4% (1)
• D
  96% (22)

Explanation

When troubleshooting connectivity issues for a user connecting to an AP managed by a standalone Mobility Controller (MC) in an AOS-8 architecture, detailed logs and debugs specific to the user's client are essential. The MC provides several tools for capturing logs and debugging information, including packet captures and user-specific debug logs. Option D, "In the MC UI's Diagnostics > Logs pages, add a `user-debug' log setting for the client's MAC address," is correct. The "user-debug" feature in the MC allows administrators to enable detailed debugging for a specific client by specifying the client's MAC address. This generates logs related to the client's authentication, association, role assignment, and other activities, which are critical for troubleshooting connectivity issues. The Diagnostics > Logs pages in the MC UI provide a user- friendly way to configure this setting and view the resulting logs.

No community discussion yet for this question.