A customer must use deep-packet inspection on the Cisco Catalyst 9800 Series Wireless Controller. The details must include all wireless client use details. Where must AVC be configured to meet this requirement?
On the Catalyst 9800 the behaviour of a WLAN's clients is defined in the policy profile, and that is where application visibility is enabled. The profile holds the AVC settings, including the flow monitor that exports the application records and the QoS-related policy. Because the policy profile is attached to the AP through the policy tag, enabling AVC there applies it to all clients that use the WLANs of that tag and yields the per-client application usage that the customer wants to see. The WLAN profile carries SSID and security attributes, and no application-awareness settings. The RF tag and join tag are tags that select RF profiles and AP join profiles, not client policies, and the AP join profile contains AP-level parameters such as CAPWAP, credentials and NTP. The policy profile is therefore the right place. Once AVC is active in the policy profile, the application usage of each client can be reviewed from the controller's client monitoring views, which confirms that the deep packet inspection data is being collected.
[Reference:Blueprint 2.3 (Implement AVC); Cisco Catalyst 9800 Series Software Configuration Guide, AVC and flow monitor configuration., ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit