JosephDoherty wrote:
Most interesting about these numbers, the explicit policer is using a much large Bc then the implicit LLQ policer had in your prior posting and I also notice you've explicitly increased the implicit LLQ's Bc, also making it much larger than the default. With the increased Bc, we can't really tell whether its the policer or the changed Bc that's changed performance so much.
Ok, reran the results and removed the explicit shaper Bc figure I previously set (still have the police figure set). The config is:
policy-map PM_DSCP
class DSCP46
police cir 89000 bc 16687 be 22250
priority percent 80
policy-map PM_DSCP_18K
class class-default
shape average 128000
service-policy PM_DSCP
Below are the results. Now it looks like the shaping is happening but the packet distribution for the priority queue is messed up, 64k of DSCP traffic, and only 19K on non-dropped traffic forwarding. None of this should be dropped.
Service-policy output: PM_DSCP_18K
Class-map: class-default (match-any)
6688 packets, 5730772 bytes
30 second offered rate 347000 bps, drop rate 220000 bps
Match: any
Traffic Shaping
Target/Average Byte Sustain Excess Interval Increment
Rate Limit bits/int bits/int (ms) (bytes)
128000/128000 1984 7936 7936 62 992
Adapt Queue Packets Bytes Packets Bytes Shaping
Active Depth Delayed Delayed Active
- 64 2413 2048366 2409 2042406 yes
Service-policy : PM_DSCP
Class-map: DSCP46 (match-any)
800 packets, 1186576 bytes
30 second offered rate 64000 bps, drop rate 45000 bps
Match: ip dscp ef (46)
800 packets, 1186576 bytes
30 second rate 64000 bps
police:
cir 89000 bps, bc 16687 bytes
conformed 749 packets, 1116202 bytes; actions:
transmit
exceeded 51 packets, 70374 bytes; actions:
drop
conformed 59000 bps, exceed 2000 bps
Queueing
Strict Priority
Output Queue: Conversation 24
Bandwidth 80 (%)
Bandwidth 102 (kbps) Burst 2550 (Bytes)
(pkts matched/bytes matched) 749/1116202
(total drops/bytes drops) 508/758348
Class-map: class-default (match-any)
5888 packets, 4544196 bytes
30 second offered rate 284000 bps, drop rate 179000 bps
Next, I tried to reenable the Bc command on the priority line, and removed the policing command. The config is:
policy-map PM_DSCP
class DSCP46
priority percent 80 16000
policy-map PM_DSCP_18K
class class-default
shape average 128000
service-policy PM_DSCP
It looks like the priority is working to me (remember Im still new to QoS!).
Im asking it to priortize 102k of traffic, and it looks like its sending 93-3 = 90K. Heres the config as it stands:
And here is the result:
Service-policy output: PM_DSCP_18K
Class-map: class-default (match-any)
45703 packets, 39955068 bytes
30 second offered rate 389000 bps, drop rate 262000 bps
Match: any
Traffic Shaping
Target/Average Byte Sustain Excess Interval Increment
Rate Limit bits/int bits/int (ms) (bytes)
128000/128000 1984 7936 7936 62 992
Adapt Queue Packets Bytes Packets Bytes Shaping
Active Depth Delayed Delayed Active
- 69 13729 14044700 13721 14035644 yes
Service-policy : PM_DSCP
Class-map: DSCP46 (match-any)
6412 packets, 9501300 bytes
30 second offered rate 93000 bps, drop rate 3000 bps
Match: ip dscp ef (46)
6412 packets, 9501300 bytes
30 second rate 93000 bps
Queueing
Strict Priority
Output Queue: Conversation 24
Bandwidth 80 (%)
Bandwidth 102 (kbps) Burst 16000 (Bytes)
(pkts matched/bytes matched) 6059/9011222
(total drops/bytes drops) 1412/2101548
Class-map: class-default (match-any)
39291 packets, 30453768 bytes
30 second offered rate 298000 bps, drop rate 258000 bps
After this test I changed the priority to 50%, and left the burst to 16000, and below is the important part! 95-31k = 64k which is half of 128K which is whats configured!
Class-map: DSCP46 (match-any)
10449 packets, 15487758 bytes
30 second offered rate 95000 bps, drop rate 31000 bps
Match: ip dscp ef (46)
10449 packets, 15487758 bytes
30 second rate 95000 bps
Queueing
Strict Priority
Output Queue: Conversation 24
Bandwidth 50 (%)
Bandwidth 64 (kbps) Burst 16000 (Bytes)
