11-22-2010 06:39 AM - edited 03-04-2019 10:32 AM
I have the following policy in place and am unsure as to why the ef queue is empty. I see the ef packets being matched and the first portion of the output indicates ef packets going to the priority queue, but the following table shows the ef queue shows 0/0 accross the board and the other packet counts don't seem to add up. Oh and what is the "cs6"
Thanks!
sho policy-map in s0/0/0
Serial0/0/0
Service-policy output: qos
Class-map: enhanced (match-any)
18929450 packets, 1332072895 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: ip dscp af31 (26)
18929450 packets, 1332072895 bytes
5 minute rate 0 bps
Queueing
Output Queue: Conversation 265
Bandwidth 384 (kbps)Max Threshold 64 (packets)
(pkts matched/bytes matched) 2355392/230029119
(depth/total drops/no-buffer drops) 0/8977/0
Class-map: high (match-any)
532831636 packets, 98884721243 bytes
5 minute offered rate 28000 bps, drop rate 0 bps
Match: ip dscp ef (46)
532831636 packets, 98884721243 bytes
5 minute rate 28000 bps
Queueing
Strict Priority
Output Queue: Conversation 264
Bandwidth 33 (%)
Bandwidth 509 (kbps) Burst 12725 (Bytes)
(pkts matched/bytes matched) 464933441/93016817984
(total drops/bytes drops) 0/0
Class-map: class-default (match-any)
716229182 packets, 359913582844 bytes
5 minute offered rate 78000 bps, drop rate 0 bps
Match: any
Queueing
Flow Based Fair Queueing
Maximum Number of Hashed Queues 256
(total queued/total drops/no-buffer drops) 0/262326/0
exponential weight: 9
dscp Transmitted Random drop Tail drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes thresh thresh prob
af11 442253270/187375309113 4279/1367847 25282/6128087 32 40 1/10
af12 0/0 0/0 0/0 28 40 1/10
af13 0/0 0/0 0/0 24 40 1/10
af21 0/0 0/0 0/0 32 40 1/10
af22 0/0 0/0 0/0 28 40 1/10
af23 0/0 0/0 0/0 24 40 1/10
af31 0/0 0/0 0/0 32 40 1/10
af32 0/0 0/0 0/0 28 40 1/10
af33 0/0 0/0 0/0 24 40 1/10
af41 0/0 0/0 0/0 32 40 1/10
af42 0/0 0/0 0/0 28 40 1/10
af43 0/0 0/0 0/0 24 40 1/10
cs1 0/0 0/0 0/0 22 40 1/10
cs2 0/0 0/0 0/0 24 40 1/10
cs3 0/0 0/0 0/0 26 40 1/10
cs4 0/0 0/0 0/0 28 40 1/10
cs5 0/0 0/0 0/0 30 40 1/10
cs6 1886907/155518082 0/0 0/0 32 40 1/10
cs7 0/0 0/0 0/0 34 40 1/10
ef 0/0 0/0 0/0 36 40 1/10
rsvp 0/0 0/0 0/0 36 40 1/10
default 271826679/172030878784 229072/338913149 3693/5467782 20 40 1/10
11-22-2010 12:36 PM
Hi,
The "following table" is for class-default; EF packets are matched in "high" class, and put in priority queue. C6 could be the routing protocol, or other control plane traffic.
HTH,
Lei Tian
11-22-2010 12:56 PM
Hi,
The default class is assigned (IP Precedence =1) , (AF11) by default if not marked. and thats what the table indicates.
the ef is matched in the class and put into priority queue,
Regards,
Mohamed
11-23-2010 06:01 AM
Ahh, ok.
So, the table is simply listing anything not matched and queued in the policy-maps. Correct?
Am I now reading this correctly:
- Conversation 264 is the Priority Queue with 33% of the bandwitch. This is for all ef packets
- Conversation 265 is some other queue with 384k for af31 packets. <---what is this queue?
- ramaining traffic goes to the default-queue and we are seeing af11 (default marked) and cs6 (possible routing protocols, etc)
- what is "default" traffic at the bottom of the table?
Thanks for your assistance, both of you.
11-23-2010 11:16 AM
Hi,
That is correct.
Class "enhanced" matches packets with dscp af31, and it uses conversaction 265; class "high" matches packets with dscp ef, and it ues conversaction 264. The rest traffic are in "class-default". There are 3 type of traffic in class-default, traffic with dscp cs6, af11 and default(0). You need to check the marking configure to see what traffic is been marked to af11 or 0.
HTH,
Lei Tian
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: