In an AOS-8 architecture with a Mobility Conductor (MC) and Mobility Controllers (MCs), the Traffic Analysis dashboard (available in the MC UI) allows administrators to monitor wireless clients’ application usage (e.g., identifying traffic from applications like Zoom, YouTube, or Skype). To enable this functionality, the MCs must be able to inspect and classify client traffic at the application level.

Firewall Visibility and DPI: The AOS-8 platform includes a stateful firewall that can perform deep packet inspection (DPI) to classify traffic based on application signatures. Enabling "firewall visibility" on the MCs activates DPI, allowing the firewall to inspect packet payloads and identify applications. This data is then used by the Traffic Analysis dashboard to display application usage statistics for wireless clients.

Option D, "Enabling firewall visibility and deep packet inspection (DPI) on the MCs," is correct. Firewall visibility must be enabled on the MCs to perform DPI and classify client traffic by application. This is typically done with the command firewall visibility in the MC configuration, which activates DPI and allows the Traffic Analysis dashboard to display application usage data.

Option A, "Configuring packet capturing on the MCs’ data plane," is incorrect. Packet capturing (e.g., using the packet-capture command) is used for manual troubleshooting or analysis, not for enabling the Traffic Analysis dashboard. Packet captures generate raw packet data, which is not processed for application usage statistics.

Option B, "Enabling logging on the users category on the MCs," is incorrect. Enabling logging for the "users" category (e.g., using the logging command) generates logs for user events (e.g., authentication, role assignment), but it does not provide application usage data for the Traffic Analysis dashboard.

Option C, "Discovering the mobility devices in HPE Aruba Networking Central," is incorrect. While discovering devices in Aruba Central can provide centralized monitoring, the Traffic Analysis dashboard in AOS-8 is a local feature on the MC and does not require Aruba Central. Additionally, application usage monitoring requires DPI on the MCs, not just device discovery.

The HPE Aruba Networking AOS-8 8.11 User Guide states:

"The Traffic Analysis dashboard on the Mobility Controller provides visibility into wireless clients’ application usage, such as identifying traffic from applications like Zoom or YouTube. To enable this feature, you must enable firewall visibility and deep packet inspection (DPI) on the MCs. Use the command firewall visibility to activate DPI, which allows the firewall to classify traffic by application. The classified data is then displayed in the Traffic Analysis dashboard under Monitoring > Traffic Analysis." (Page 360, Traffic Analysis Dashboard Section)

Additionally, the HPE Aruba Networking Security Guide notes:

"Firewall visibility on AOS-8 Mobility Controllers enables deep packet inspection (DPI) to classify client traffic by application. This is required for features like the Traffic Analysis dashboard, which displays application usage statistics for wireless clients, helping administrators monitor network activity." (Page 55, Firewall Visibility Section)