I'm rusty with QoS. Really haven't had to work with it much since a lot of the networks I work on have bandwidth to spare. I've been working with some MPLS sites that have lower bandwidth connections, around 10Mbps is typical for these sites.   There have been issues and I believe it is due to the service provider dropping packets due to the CIR being exceeded. I'm trying to understand the QoS configuration better. The goal is to make some adjustments to allow file transfer over SMB to function better (TCP 445). I am looking for some help in how to best implement this as well as understand what is already occurring. The remote site was setup with AutoQoS but I don't think it is taking into account the slower upstream bandwidth. I have the service provider's config as well which is using IPP (precedence) to do it's shaping.   Would be super helpful if someone who is more knowledgable could walk me through how the current config is working and where best to adjust to help alleviate issues.    Here is the switch where all clients are connecting:   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 AutoQos-4.0-Voip-Data-CiscoPhone-Class match cos 5 class-map match-any AutoQos-4.0-Voip-Signal-CiscoPhone-Class match cos 3 class-map match-any non-client-nrt-class class-map match-any AutoQos-4.0-Default-Class match access-group name AutoQos-4.0-Acl-Default 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 ! 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 policy-map AutoQos-4.0-CiscoPhone-Input-Policy class AutoQos-4.0-Voip-Data-CiscoPhone-Class set dscp ef police cir 128000 bc 8000 conform-action transmit exceed-action set-dscp-transmit dscp table policed-dscp class AutoQos-4.0-Voip-Signal-CiscoPhone-Class set dscp cs3 police cir 32000 bc 8000 conform-action transmit exceed-action set-dscp-transmit dscp table policed-dscp class AutoQos-4.0-Default-Class set dscp default This is the service policy on the interface facing the MPLS circuit:     service-policy input AutoQos-4.0-Trust-Dscp-Input-Policy service-policy output AutoQos-4.0-Output-Policy On the service provider's router, here's what's configured there:   class-map match-any best-effort match ip precedence 0 1 class-map match-any network-control match ip precedence 4 6 7 class-map match-any expedited-forwarding match ip precedence 5 class-map match-any assured-forwarding match ip precedence 2 3 ! policy-map Template-8 class expedited-forwarding police cir percent 20 conform-action transmit exceed-action drop priority percent 20 class network-control bandwidth percent 10 random-detect class best-effort bandwidth percent 69 random-detect policy-map QOS class class-default shape average 10000000 service-policy Template-8 policy-map rate-limit-20M-out class class-default shape average 20000000 And finally, on the SP's router facing into their network:   service-policy output QOS   ... View more

I'm not in the environment right now but this one is a bit interesting. A 4507 has been running in the core of this network just fine for a while now. Something happened over night that caused it to stop routing... kinda. Basically, the only issue seems to be with routes that are redirected to a different address within the same network.    Example. The switch has an SVI in the VLAN and is acting as a default gateway for the VLAN. The switch is peering via EIGRP with a few other devices in the same VLAN. A packet destined for a different network might come into the switch at 10.0.0.1 but be redirected to 10.0.0.254 to reach a different network. This isn't working. If I were to change a host to use the .254 address as the default gateway, traffic to and from that network works. But when the switch is the default gateway, it doesn't.   This isn't a configuration issue since it has been running for well over a year without issue.    I'm not sure what this type of routing would be called... maybe hairpin "ish"? I've considered clearing the routing table but that would be service disruptive. I've thought about clearing the cef table to see if that would fix things but I'm not sure how disruptive that would be.   Any ideas on way to fix this without reloading the entire switch, and what could be causing this? Hasn't happened before.    (Also, this switch is slated for refresh soon since it is way EOL) ... View more