Interface service policy - is this right?

Unanswered Question
Sep 20th, 2007

I have a service policy configured on a 2MB serial interface on a 2620, policy-map is as follows:

policy-map queue

class critical

priority 204

set ip dscp ef

class priority

bandwidth percent 80

class class-default

fair-queue

random-detect dscp-based

set ip dscp default

I have max-reserved-bandwidth of 100%. As I have reserved 90% (10% for critical and 80% for priority), I would expect to see a further 10% (204kbps) as being available. I use this same policy on 3 other routers, all to that result.

However, when I do a show run int, I see that 1844kbps are still available:

Serial0/0 is up, line protocol is up

Hardware is PowerQUICC Serial

Internet address is x.x.x.x/30

MTU 1500 bytes, BW 2048 Kbit, DLY 20000 usec,

reliability 255/255, txload 181/255, rxload 31/255

Encapsulation HDLC, loopback not set

Keepalive set (10 sec)

Last input 00:00:01, output 00:00:00, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 101787

Queueing strategy: weighted fair

Output queue: 0/1000/64/101603 (size/max total/threshold/drops)

Conversations 0/50/256 (active/max active/max total)

Reserved Conversations 1/1 (allocated/max allocated)

Available Bandwidth 1844 kilobits/sec

5 minute input rate 251000 bits/sec, 362 packets/sec

5 minute output rate 1457000 bits/sec, 311 packets/sec

738303666 packets input, 4012471098 bytes, 0 no buffer

Received 846788 broadcasts, 0 runts, 0 giants, 0 throttles

10 input errors, 0 CRC, 8 frame, 0 overrun, 0 ignored, 2 abort

599171675 packets output, 2803364940 bytes, 0 underruns

0 output errors, 0 collisions, 1 interface resets

0 output buffer failures, 0 output buffers swapped out

0 carrier transitions

DCD=up DSR=up DTR=up RTS=up CTS=up

What's going on here, or is this a normal way of representing for a 2620? My 2800's represent it as 204/10% as expected.

Any one can shed light on this it would be much appreciated! Thanks.

r1#show policy-map int

Serial0/0

Service-policy output: queue

Class-map: critical (match-any)

566218 packets, 38772726 bytes

5 minute offered rate 0 bps, drop rate 0 bps

Match: access-group 181

566218 packets, 38772726 bytes

5 minute rate 0 bps

Queueing

Strict Priority

Output Queue: Conversation 264

Bandwidth 204 (kbps) Burst 5100 (Bytes)

(pkts matched/bytes matched) 326895/21815708

(total drops/bytes drops) 0/0

QoS Set

dscp ef

Packets marked 566218

Class-map: priority (match-any)

7705221 packets, 3601939397 bytes

5 minute offered rate 715000 bps, drop rate 0 bps

Match: access-group 180

7705213 packets, 3601939455 bytes

5 minute rate 715000 bps

Queueing

Output Queue: Conversation 265

Bandwidth 80 (%) Max Threshold 64 (packets)

(pkts matched/bytes matched) 5162685/2786697189

(depth/total drops/no-buffer drops) 2/13549/0

Class-map: class-default (match-any)

3082096 packets, 3741578423 bytes

5 minute offered rate 1085000 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) 12/738/0

exponential weight: 9

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Pavel Bykov Thu, 09/20/2007 - 05:54

Yes, it's supposed to say what you are expecting. What IOS does it run? I have encountered some significant problems on older IOS releases.

On the other hand, it displays 2048-204=1844 Kbps. So it seems it's substracting only priority bandwidth. Try typing "bandwidth 1638" instead of "bandwidth percent 80".

But hey, this is not an important idicator of your qos. Importnat output is that of a "show policy-map interface X/X" command. I think you can safely ignore that message if your QoS functions as desired.

hope this helps

jigsaw2026 Thu, 09/20/2007 - 06:08

Thank you for your response, you have confirmed my thoughts. I think I will concentrate on policy-map int output instead.

It's running 12.1(3r)T2, so this could be a factor.

Thanks,

J

Actions

This Discussion