I have a fault at the moment ongoing. Symptoms are low TCP throughput but UDP/Ping tests are okay. On the PE front, there is a traffic-shaping policy applied outbound and policing inbound. I have 2 questions though:-
1. The policy-map applied inbound which is configured to police is onlyl givening 8000bits to the default traffic but 776000 to the mgmt traffic(the customer is meant to be receiving 80meg) - surely these values are the wrong way around particularly as the mgmt class only matches traffic with dscp value of 63 so all other traffic will hit the default queue. 2nd question is that when I look at the policy-map on the PE , I can see traffic shaping is consistently active but at this is the odd thing, I am not seeing this reflected on the Physical interface.
Am I correct in my assumption that the values for the policing inbound policy-map pe_in_child_XXX_hub are incorrect ie. too small for the default and too big for the mgmt class?
I would post the configs but can't see an upload button...so here is the bits I am worried about...
police 760000 27500 55000 conform-action set-mpls-exp-transmit 6 exceed-action set-mpls-exp-transmit 2 violate-action set-mpls-exp-transmit 2
police 8000 8000 8000 conform-action set-mpls-exp-transmit 5 exceed-action set-mpls-exp-transmit 5 violate-action set-mpls-exp-transmit 5
set ip dscp default
Service-policy output: pe_out_parent_xxx_hub
Class-map: class-default (match-any)
157816193 packets, 68996467859 bytes
5 minute offered rate 8962000 bps, drop rate 0 bps
Target/Average Byte Sustain Excess Interval Increment
Rate Limit bits/int bits/int (ms) (bytes)
81600000/81600000 510000 2040000 2040000 25 255000
Adapt Queue Packets Bytes Packets Bytes Shaping
Active Depth Delayed Delayed Active
- 1 0 0 0 0 yes