From: gladston@br.ibm.com
Date: Fri Jul 08 2005 - 09:53:27 GMT-3
Hi,
Thanks to reply on this.
If I use "access-list 109 permit ip any any" CQ works on R1. Before that
I tried "no ip route-cache" but this did not change the result.
That is strange CQ does not work well with 'access-list 109 permit udp an
an rang 1000 2000. CBWFQ do it fine.
Cordially,
------------------------------------------------------------------
Gladston
"Shanky" <shankyz@gmail.com>
08/07/2005 04:01
To
Alaerte Gladston Vidali/Brazil/IBM@IBMBR
cc
Subject
Custom Queue and CBWFQ
Hi,
From the Output posted by you , I see that you are using CQ to match on
protocol IP using ACL 109 which is not showing any matches ..
Did you also try to do it without specifying any protocol ..does CQ work
in
this case ? If yes , then its the ACL matching issue on R1.
and you could try to turn off fast switching etc on the router and see if
any matches occur ?
Rack2R1#sh queuei custom
Current custom queue configuration:
List Queue Args
12 6 default
12 4 protocol ip list 109
12 5 protocol ip list 110
12 4 byte-count 512 limit 0
12 5 byte-count 5120
12 6 byte-count 45000
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
gladston@br.ibm.com
Sent: Thursday, July 07, 2005 7:53 PM
To: ccielab@groupstudy.com
Subject: Custom Queue and CBWFQ
Hi,
Having problem with custom queue not matching packets, I configured the
same
access-list on 2 routers.
R1 uses CQ and R4 uses CBWFQ. R4 matches the packets, R1 does not. It
seems
to be an IOS problem
with CQ. Version is C2600-J1S3-M, 12.2(15)T5is.
Have you seen this behavior?
Traffic is destinated to BB1, using RTR. BB1 is reachable through R1
ethernet0/0.
R4
Rack2R4#sh access-list 109
Extended IP access list 109
10 permit udp any any range 1000 2000 (350 matches)
Rack2R1#sh access-list 109
Extended IP access list 109
10 permit udp any any range 1000 2000
CBQWF selects the traffic, CQ does not (on R1 udp should go to queue # 4):
Rack2R4#sh policy-map int ser 0/0
Serial0/0
Service-policy output: Compare-to-CQ
Class-map: udp-100-1500 (match-all)
217 packets, 13888 bytes
5 minute offered rate 1000 bps, drop rate 0 bps
Match: access-group 109
Queueing
Output Queue: Conversation 41
Bandwidth 1 (%)
Bandwidth 1 (kbps) Max Threshold 1 (packets)
(pkts matched/bytes matched) 0/0
(depth/total drops/no-buffer drops) 0/0/0
Rack2R1#sh queuei int e0/0
Interface Ethernet0/0 queueing strategy: custom
Output queue utilization (queue/count)
0/580 1/28 2/4806 3/662 4/0 5/0 6/1032 7/1952 8/0
9/105 10/0 11/0 12/0 13/0 14/0 15/0 16/0
Rack2R1#sh queuei custom
Current custom queue configuration:
List Queue Args
12 6 default
12 4 protocol ip list 109
12 5 protocol ip list 110
12 4 byte-count 512 limit 0
12 5 byte-count 5120
12 6 byte-count 45000
(I would not use CQ on the real world, but you know, on the lab...it is
another history)
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:00:29 GMT-3