Cisco Catalyst 9400

DirectionAVC Policy ExampleAVC Policy Format
Ingress and egress
policy-map webex-policy
class webex-class
police 5000000
service-policy client-in-police-only
policy-map client-in-police-only
class webex-class
police 100000
class class-webex-category
set dscp ef
police 200000
Hierarchical police
policy-map webex-policy
class class-default
police 1500000
service policy client-up-child
policy-map client-up-child
class webex-class
police 100000
set dscp ef
class class-webex-category
police 200000
set dscp af31
Hierarchical set and police
Restrictions for Wired Application Visibility and Control
• NBAR based QoS policy configuration is allowed only on wired physical ports. Policy configuration is
not supported on virtual interfaces like VLAN and other logical interfaces.
• NBAR based QoS policy configuration is not supported on port-channel member ports and virtual
interfaces like SVIs or sub-interfaces.
• NBAR based QoS policy configuration is supported on Layer 2 access and trunk ports and Layer 3 routed
ports.
• NBAR and transmit (Tx) Switched Port Analyzer (SPAN) is not supported on the same interface.
• Only one of the NBAR based QoS mechanisms are allowed to be attached to any port at the same time,
either protocol based or attributes based. Only the following two attributes are supported:
• traffic-class
• business-relevance
• The legacy WDAVC QoS limitations are still applicable:
• Only marking and policing are supported.
• Only physical interfaces are supported.
• There is a delay in the QoS classification since the application classification is done offline (while
the initial packet/s of the flow are meanwhile forwarded before the correct QoS classification).
System Management Configuration Guide, Cisco IOS XE Bengaluru 17.4.x (Catalyst 9400 Switches)
179
Configuring Application Visibility and Control in a Wired Network
Restrictions for Wired Application Visibility and Control