Additional References For Application Visibility And Control; Feature History For Application Visibility And Control In A Wired Network - Cisco Catalyst 9500 Manual

Additional References for Application Visibility and Control

10.
Additional References for Application Visibility and Control
Related Documents
Related Topic
For complete syntax and usage information for the
commands used in this chapter.
Feature History for Application Visibility and Control in a Wired
Network
This table provides release and related information for features explained in this module.
These features are available on all releases subsequent to the one they were introduced in, unless noted
otherwise.
Release
Cisco IOS XE Everest 16.5.1a
Cisco IOS XE Fuji 16.8.1a
Cisco IOS XE Gibraltar
16.12.1
System Management Configuration Guide, Cisco IOS XE Fuji 16.8.x (Catalyst 9500 Switches)
144
Answer: If you have any class-map with match protocol protocol-name, NBAR will be globally
activated on the switch but no traffic will be subjected to NBAR classification. This is an expected
behavior and it does not consume any resources.
Question: I see some traffic under the default QOS queue. Why?
Answer: For each new flow, it takes a few packets to classify it and install the result in the hardware.
During this time, the classification would be 'un-known' and traffic will fall under the default queue.
Feature
Application Visibility
and Control in a Wired
Network
Wired Application
Visibility and Control
(Wired AVC)
Attribute-based QoS
(EasyQoS)
DNS flow record
Configuring Application Visibility and Control in a Wired Network
Document Title
Command Reference (Catalyst 9500 Series
Switches)
Feature Information
AVC is a critical part of Cisco's efforts to evolve
its Branch and Campus solutions from being strictly
packet and connection based to being
application-aware and application-intelligent.
Support for this feature was introduced only on the
C9500-12Q, C9500-16X, C9500-24Q, C9500-40X
models of the Cisco Catalyst 9500 Series Switches.
Support for defining QoS classes and policies based
on Network-Based Application Recognition
(NBAR) attributes instead of specific protocols,
was made available, with a few limitations. Only
business-relevance and traffic-class are the
supported NBAR attributes.
Support for DNS flow record was introduced. DNS
flow record uses the DNS Domain-Name as the
collect field for defining the flow record.