9300 - QoS

[rob1456657]

Here is my dilemma, we have a Cisco 9300 that has some phones connected to it and folks complained about phone issues. We enabled QoS. Because these phones are not Cisco phones we used auto qos trust.

Folks complained again that there were issues. The Mitel and Poly phones we are using use COS 5 and DSCP 46 which is pretty much standard from what I can tell and the auto qos trust includes policy-maps that apply to these values. Since they complained again I have change the auto qos to auto qos trust dscp to see if there would be any difference. I also ran the command:

sho policy-map int gi1/0/24 (one particular user that has complained) and it seems like the policy does not match any of the traffic:

Service-policy input: AutoQos-4.0-Trust-Dscp-Input-Policy

Class-map: class-default (match-any)
652093611 packets
Match: any
QoS Set
dscp dscp table AutoQos-4.0-Trust-Dscp-Table

Service-policy output: AutoQos-4.0-Output-Policy

queue stats for all priority classes:
Queueing
priority level 1

(total drops) 0
(bytes output) 10885284

Class-map: AutoQos-4.0-Output-Priority-Queue (match-any)
0 packets
Match: dscp cs4 (32) cs5 (40) ef (46)
Match: cos 5
Priority: 30% (300000 kbps), burst bytes 7500000,

Priority Level: 1

Class-map: AutoQos-4.0-Output-Control-Mgmt-Queue (match-any)
0 packets
Match: dscp cs2 (16) cs3 (24) cs6 (48) cs7 (56)
Match: cos 3
Queueing

queue-limit dscp 16 percent 80
queue-limit dscp 24 percent 90
queue-limit dscp 48 percent 100
queue-limit dscp 56 percent 100
(total drops) 0
(bytes output) 346119
bandwidth remaining 10%

queue-buffers ratio 10

Class-map: AutoQos-4.0-Output-Multimedia-Conf-Queue (match-any)
0 packets
Match: dscp af41 (34) af42 (36) af43 (38)
Match: cos 4
Queueing

(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10

Class-map: AutoQos-4.0-Output-Trans-Data-Queue (match-any)
0 packets
Match: dscp af21 (18) af22 (20) af23 (22)
Match: cos 2
Queueing

(total drops) 0
(bytes output) 68
bandwidth remaining 10%
queue-buffers ratio 10

Class-map: AutoQos-4.0-Output-Bulk-Data-Queue (match-any)
0 packets
Match: dscp af11 (10) af12 (12) af13 (14)
Match: cos 1
Queueing

(total drops) 0
(bytes output) 304427
bandwidth remaining 4%
queue-buffers ratio 10

Class-map: AutoQos-4.0-Output-Scavenger-Queue (match-any)
0 packets
Match: dscp cs1 (8)
Queueing

(total drops) 0
(bytes output) 244098736
bandwidth remaining 1%
queue-buffers ratio 10

Class-map: AutoQos-4.0-Output-Multimedia-Strm-Queue (match-any)
0 packets
Match: dscp af31 (26) af32 (28) af33 (30)
Queueing

(total drops) 0
(bytes output) 0
bandwidth remaining 10%
queue-buffers ratio 10

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

(total drops) 0
(bytes output) 191992207
bandwidth remaining 25%
queue-buffers ratio 25

Here is the port config:

interface GigabitEthernet1/0/24
switchport access vlan 22
switchport mode access
switchport voice vlan 23
auto qos trust dscp
spanning-tree portfast
service-policy input AutoQos-4.0-Trust-Dscp-Input-Policy
service-policy output AutoQos-4.0-Output-Policy

What else can I do, or should the configuration be different?

Appreciate any one that can provide useful advice.

[rob1456657]

After performing extensive research, capturing packets, watching voice traffic, etc. Turns out the Cisco policy is doing what it should be doing. Our issue turned out to be the ports the VoIP Provider is using. Some ports were not added to our policy in the firewall. This was causing some packets to go out a different WAN interfaces rather than the one identified for Voice Traffic. Because of this packets were being split between two WAN interfaces and it was causing our VoIP issues.

Once all of the ports were identified and we updated the policy, we have had no VoIP issues.

[balaji.bandi]

that should work - we same QoS config simlar one works as expected.

what VOIP system you have ?

[rob1456657]

It's a Mitel VoIP system. Definitely working.

Turns out it was the SD-WAN and VoIP Policy on the Firewall that was causing the issue.