Users report slowness on the network, and it is suspected that certain applications are consuming all the bandwidth. A network engineer must enable the NBAR protocol to improve wireless client traffic visibility and provide advanced, granular, application classification, and analytics. How should the network engineer configure NBAR on a 9800 WLC?
The correct configuration approach is to enable Application Visibility and Control on the policy profile. On the Catalyst 9800, WLANs are not configured as isolated monolithic objects; the WLAN profile is mapped to a policy profile through a policy tag, and many client traffic services are applied from that policy profile. Cisco defines AVC as the wireless feature set that identifies and monitors applications using DPI, creates rules to manage application bandwidth and usage, and integrates with Flexible NetFlow for per-application or per-protocol statistics. Cisco further states that AVC benefits from NBAR running on the AP or controller, and that the NBAR2 engine analyzes and recognizes traffic flows.
Operationally, Cisco's 9800 AVC guide shows that AVC is enabled by navigating to Configuration > Services > Application Visibility and selecting the relevant Policy Profile. It also shows the CLI form under the policy profile: wireless profile policy AVC_testing followed by ip nbar protocol-discovery, with verification showing NBAR Protocol Discovery : Enabled. Options A and B are incorrect because the feature is not enabled directly on the WLAN. Option C is generic and incomplete; the Cisco feature construct is AVC. Reference topics: AVC, NBAR2, Flexible NetFlow, Catalyst 9800 policy profiles, and wireless application visibility.