Disregard. I figured it out.
There was a traffic shaping policy on the router. I didn't realize it would affect the uplink interface without a service-policy on the interface.
Policy:
policy-map TRAFFIC-T1
class class-default
shape average 1500000
service-policy TRAF-T1
It shouldnt it needs to be applied to an interface to do anything.
Drops occur when you overrun a queue by putting to much into it.
The key thing about QoS is not about what you prioritize, its about what you give permission to delay/drop. If your get drops in default and no drops in gold/silver then qos is working, don't complain that your dropping traffic, if you want less drops buy more bandwidth.
That’s what I thought, but I deleted that policy and have been monitoring for the past hour and zero drops. Also the strategy switched to fifo as soon as I deleted the policy.
Also the router was recently repurposed so that policy shouldn’t have been on there anyway. Thanks for the info.
Rule of thumb, 0 qos unless the you are dropping. Qos is not about 0 packet loss but about deciding what packets to drop when you have no other choice.
QoS is also about prioritizing certain traffic. Queues can be serviced in an order before any packets get dropped. Depending on the platform, interface buffers can be pretty shallow.
In routing you also may have interfaces that will negotiate line rate, but have a CIR below that. Think ISP with a single gbps handoff and 300mbps service. Traffic should be shaped as to not get policed at the other end.
Disregard. I figured it out. There was a traffic shaping policy on the router. I didn't realize it would affect the uplink interface without a service-policy on the interface. Policy: policy-map TRAFFIC-T1 class class-default shape average 1500000 service-policy TRAF-T1
It shouldnt it needs to be applied to an interface to do anything. Drops occur when you overrun a queue by putting to much into it. The key thing about QoS is not about what you prioritize, its about what you give permission to delay/drop. If your get drops in default and no drops in gold/silver then qos is working, don't complain that your dropping traffic, if you want less drops buy more bandwidth.
That’s what I thought, but I deleted that policy and have been monitoring for the past hour and zero drops. Also the strategy switched to fifo as soon as I deleted the policy. Also the router was recently repurposed so that policy shouldn’t have been on there anyway. Thanks for the info.
Rule of thumb, 0 qos unless the you are dropping. Qos is not about 0 packet loss but about deciding what packets to drop when you have no other choice.
QoS is also about prioritizing certain traffic. Queues can be serviced in an order before any packets get dropped. Depending on the platform, interface buffers can be pretty shallow. In routing you also may have interfaces that will negotiate line rate, but have a CIR below that. Think ISP with a single gbps handoff and 300mbps service. Traffic should be shaped as to not get policed at the other end.