QOS on Catalyst 9300,not showing captured packets.

[titusroz03]

Have applied the below policy map in OUT direction but I couldn't see the packets count increased but instead the total bytes output get increases. At the same time policy towards ingress which captures the match protocols increases.

Input policy-For capturing the protocol traffic through NBAR

Service-policy input: Prod-QoS-Q4-2022_Policy & marking.

Class-map:AudioQOS (match-any)
465973 packets
Match: protocol ms-teams-audio
Match: protocol ringcentral-audio
Match: protocol cisco-jabber-audio
Match: protocol wifi-calling
Match: protocol webex-audio
QoS Set
dscp ef

Class-map:Video_QoS (match-any)
750489 packets
Match: protocol ringcentral-video
Match: protocol ms-teams-video
Match: protocol ms-lync-video
Match: protocol cisco-jabber-video
Match: protocol webex-video
QoS Set
dscp af41

Class-map: Media_QoS
48197 packets
Match: protocol webex-media
Match: protocol webex-app-sharing
Match: protocol ms-teams-media
Match: protocol ms-teams-app-sharing
QoS Set
dscp af21

Class-map: class-default (match-any)
19851931 packets
Match: any

Output policy- Capture the marked traffic and Apply bandwith percentage

Service-policy output: HK_OUT_QOS

Class-map: CM_EF (match-any)
0 packets
Match: ip precedence 5
Match: ip dscp ef (46)
Queueing

(total drops) 0
(bytes output) 169567386575
bandwidth 20% (200000 kbps)

Class-map: CM_VC (match-any)
0 packets
Match: precedence 4
Match: ip dscp af41 (34)
Queueing

(total drops) 0
(bytes output) 432862687548
bandwidth 30% (300000 kbps)

Class-map: CM_NC (match-any)
0 packets
Match: ip precedence 6 7
Queueing

(total drops) 0
(bytes output) 0
bandwidth 5% (50000 kbps)

Class-map: CM_AF (match-any)
0 packets
Match: ip precedence 2 3
Match: ip dscp af21 (18)
Queueing

(total drops) 0
(bytes output) 24835247062
bandwidth 20% (200000 kbps)

Class-map: class-default (match-any)
0 packets
Match: any

(total drops) 2733557606
(bytes output) 21938056495717

How can I ensure if my policy is working correctly..?

[Georg Pauwen]

Hello,

the logical explanation would (obviously) be that there is traffic flowing outbound through your interface, but none of that traffic is matching your criteria. Can you post the full running config of the device on which you have applied the policy ?

[titusroz03]

class-map match-any Audio

match protocol ms-teams-audio

match protocol ringcentral-audio

match protocol cisco-jabber-audio

match protocol wifi-calling

match protocol webex-audio

match protocol cisco-spark    

match protocol cisco-spark-audio

class-map match-any Video

match protocol ringcentral-video

match protocol ms-teams-video

match protocol ms-lync-video

match protocol cisco-jabber-video

match protocol webex-video

match protocol cisco-spark-video

class-map match-any Media

match protocol webex-media

match protocol webex-app-sharing

match protocol ms-teams-media

match protocol ms-teams-app-sharing

match protocol cisco-spark-media

class-map match-any CM_EF

  description Expedited Forwarding

match ip precedence 5

match ip dscp ef

class-map match-any CM_VC

  description VIDEO-CONF

match ip precedence 4

match ip dscp af41

class-map match-any CM_AF

  description Assured Forwarding

match ip precedence 2  3

match ip dscp af21

class-map match-any CM_NC

  description Network Control

match ip precedence 6  7

Ingress policy applied in User connected interface

policy-map Ingress-policy

class Audio

  set dscp ef

class video

  set dscp af41

class media

  set dscp af21

Egress policy applied in WAN interface

policy-map Egress-policy

class CM_EF

  bandwidth percent 20

class CM_VC

  bandwidth percent 30

class CM_NC

  bandwidth percent 5

class CM_AF

  bandwidth percent 20

class class-default

  random-detect