12-28-2022 12:41 AM - edited 12-28-2022 01:10 AM
Hi,
we have some WS-C3650-48PS switches at small site as a collapsed core with Auto QOS enabled, but the WAN link are getting saturated with file share which affects MS teams voice and video, so I had a look at their QOS settings:
show running-config policy-map
Building configuration...
Current configuration : 1163 bytes
!
policy-map port_child_policy
class non-client-nrt-class
bandwidth remaining ratio 10
policy-map AutoQos-4.0-Output-Policy
class AutoQos-4.0-Output-Priority-Queue
priority level 1 percent 30
class AutoQos-4.0-Output-Control-Mgmt-Queue
bandwidth remaining percent 10
queue-limit dscp cs2 percent 80
queue-limit dscp cs3 percent 90
queue-limit dscp cs6 percent 100
queue-limit dscp cs7 percent 100
queue-buffers ratio 10
class AutoQos-4.0-Output-Multimedia-Conf-Queue
bandwidth remaining percent 10
queue-buffers ratio 10
class AutoQos-4.0-Output-Trans-Data-Queue
bandwidth remaining percent 10
queue-buffers ratio 10
class AutoQos-4.0-Output-Bulk-Data-Queue
bandwidth remaining percent 4
queue-buffers ratio 10
class AutoQos-4.0-Output-Scavenger-Queue
bandwidth remaining percent 1
queue-buffers ratio 10
class AutoQos-4.0-Output-Multimedia-Strm-Queue
bandwidth remaining percent 10
queue-buffers ratio 10
class class-default
bandwidth remaining percent 25
queue-buffers ratio 25
policy-map AutoQos-4.0-Trust-Dscp-Input-Policy
class class-default
set dscp dscp table AutoQos-4.0-Trust-Dscp-Table
!!
show running-config class-map
Building configuration...
Current configuration : 719 bytes
!
class-map match-any AutoQos-4.0-Output-Multimedia-Conf-Queue
match dscp af41 af42 af43
match cos 4
class-map match-any AutoQos-4.0-Output-Bulk-Data-Queue
match dscp af11 af12 af13
match cos 1
class-map match-any AutoQos-4.0-Output-Priority-Queue
match dscp cs4 cs5 ef
match cos 5
class-map match-any AutoQos-4.0-Output-Multimedia-Strm-Queue
match dscp af31 af32 af33
class-map match-any non-client-nrt-class
class-map match-any AutoQos-4.0-Output-Trans-Data-Queue
match dscp af21 af22 af23
match cos 2
class-map match-any AutoQos-4.0-Output-Scavenger-Queue
match dscp cs1
class-map match-any AutoQos-4.0-Output-Control-Mgmt-Queue
match dscp cs2 cs3 cs6 cs7
match cos 3
end
and the WAN router has the following IP precedence Match:
sh policy-map interface GigabitEthernet0/0/0 input
GigabitEthernet0/0/0
Service-policy input: COS-IN
Class-map: DSCP-IN-PREC-0To5 (match-any)
669131157 packets, 223595265075 bytes
30 second offered rate 1000 bps
Match: ip precedence 0
Match: ip precedence 1
Match: ip precedence 2
Match: ip precedence 3
Match: ip precedence 4
Match: ip precedence 5
Class-map: class-default (match-any)
142573370 packets, 26549797129 bytes
30 second offered rate 1000 bps, drop rate 0000 bps
Match: any
QoS Set
ip precedence 0
Marker statistics: Disabled
but as you can see from the WAN router output, the QOS isnt working.
So wondering, if I get the provider to change their QOS IP Precedence Match to DSCP, that should be enough to get this working? if not, please let me know you have a sample of working configuration example?
will really appreciate your help.
Regards,
12-29-2022 01:21 AM - edited 12-29-2022 01:22 AM
Hi @MHM Cisco World,
the traffic is marked at source by default as its MS teams Voice and Video. when you say ingress and egress do you mean switch or router?
the switch ingress interfaces have the following commands:
auto qos trust dscp
service-policy input AutoQos-4.0-Trust-Dscp-Input-Policy
service-policy output AutoQos-4.0-Output-Policy
egress has nothing qos related.
Regards,
Qasim
12-30-2022 01:55 AM
12-30-2022 02:31 AM
Hello.
it is difficult to give any advice, since we have not seen the full configuration of the WAN router. Also, the output of 'show interfaces x' (where 'x' are the inbound (connected to your switch) and outbound (connected to the Internet) interfaces on the WAN router are needed. What device (model) is the WAN router ? What does the 3rd party say, why does their QoS policy (apparently) not work ?
12-30-2022 02:59 AM
sorry for late reply I will start today analysis issue.
12-30-2022 08:36 AM
"so any suggestions?"
Sure, stop worrying, at this time about QoS on your switches. You need to concern yourself with the congestion you've noted on the WAN link.
As @Georg Pauwen recent post notes, you need to talk with your WAN vendor.
Unfortunately, most such WAN vendors offered solution will be "we can provide you more bandwidth". They also might provide some basic QoS support, but more often than not, they'll only offer a "more bandwidth".
Sometimes more bandwidth is the right solution, although, often QoS can mitigate the need for an over abundance of it, to obtain the same perceived performance. (BTW, QoS can often tremendously impact your bandwidth requirements [downward].)
If your WAN vendor isn't responsive, and you want to explore options beyond what they offer, you can either "shop" for a more responsive WAN vendor, or you can acquire WAN bandwidth without 3rd party management. Or, you can, sometimes, manage your WAN bandwidth, before you hand off your traffic to your 3rd party router.
As you haven't detailed described you WAN, cannot offer additional suggetions.
12-30-2022 03:24 PM
the ingress in SW is the port that connect to SW/PC/IPhone and you config is OK or need some change if needing
the egress in SW which is the port toward WAN router need to also config with AutoQoS
The following policy maps and class maps are created and applied when running the auto qos classify and auto qos classify police commands:
Policy maps (For the auto qos classify policecommand):
AutoQos-4.0-Classify-Police-Input-Policy
AutoQos-4.0-Output-Polic
I am right ?
if you consider that the ingress interface is from WAN then you need to config the egress port connect to SW/PC/IPhone
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide