From: The Great Ryan (pv.ryan@gmail.com)
Date: Tue Oct 18 2005 - 14:36:07 GMT-3
You are right. I just tested with the following and the bandwidth
percentage return to "normal". does it make sense that I set both cir
and mincir be the same value ?
map-class frame-relay FRTS
frame-relay cir 128000
frame-relay mincir 128000
service-policy output CBWFQ
Besides, my first configuration try to directly use policy-map command
on frame-relay interface (without use Frame-Relay Traffic shaping).
Does the QOS work ?
Thanks for your reply !
Ryan
2005/10/19, Edwards, Andrew M <andrew.m.edwards@boeing.com>:
> Ryan,
>
> When you use FRTS and CBWFQ with the bandwidth percentage parameter, the
> percentage is based upon the minCIR value for FRTS.
>
> HTH,
>
> andy
>
> -----Original Message-----
> From: The Great Ryan [mailto:pv.ryan@gmail.com]
> Sent: Tuesday, October 18, 2005 10:59 AM
> To: Cisco certification
> Subject: CBWFQ on Frame-Relay Interface
>
> Hi, Group,
>
> I want to classfiy two types of traffic and apply CBWFQ on 128k
> Frame-Relay Interface. Does my configuration work on Frame-Relay
> Interface?
> The "show policy-map" seem ok
>
> ==========================
> class-map match-all traffic-a
> match access-group 15
> class-map match-all traffic-b
> match access-group 25
> !
> policy-map QOS
> class traffic-a
> bandwidth percent 25
> class traffic-b
> bandwidth percent 50
> !
> interface Serial0/0
> bandwidth 128
> service-policy output QOS
> encapsulation frame-relay
> !
> R5#s policy-map interface s0/0
>
> Serial0/0
>
> Service-policy output: QOS
>
> Class-map: traffic-a (match-all)
> 0 packets, 0 bytes
> 5 minute offered rate 0 bps, drop rate 0 bps
> Match: access-group 15
> Queueing
> Output Queue: Conversation 265
> Bandwidth 25 (%)
> Bandwidth 32 (kbps) Max Threshold 64 (packets)
> (pkts matched/bytes matched) 0/0
> (depth/total drops/no-buffer drops) 0/0/0
>
> Class-map: traffic-b (match-all)
> 0 packets, 0 bytes
> 5 minute offered rate 0 bps, drop rate 0 bps
> Match: access-group 25
> Queueing
> Output Queue: Conversation 266
> Bandwidth 50 (%)
> Bandwidth 64 (kbps) Max Threshold 64 (packets)
> (pkts matched/bytes matched) 0/0
> (depth/total drops/no-buffer drops) 0/0/0
>
> Class-map: class-default (match-any)
> 23 packets, 1243 bytes
> 5 minute offered rate 0 bps, drop rate 0 bps
> Match: any
> ==========================
>
>
> However, if I try to use Frame-Relay Traffic shaping together with
> "service policy output", the bandwidth percent seem to be not correct.
> 25% traffic become 16k only. Why it changes ?
>
> ==========================
> class-map match-all traffic-a
> match access-group 15
> class-map match-all traffic-b
> match access-group 25
> !
> policy-map QOS
> class traffic-a
> bandwidth percent 25
> class traffic-b
> bandwidth percent 50
> !
> interface Serial0/0
> encapsulation frame-relay
> frame-relay class FRTS
> frame-relay traffic-shaping
> !
> map-class frame-relay FRTS
> frame-relay cir 128000
> service-policy output QOS
> !
> R5#show policy-map int s0/0 dlci 503
> Serial0/0: DLCI 503 -
>
> Service-policy output: QOS
>
> Class-map: traffic-a (match-all)
> 0 packets, 0 bytes
> 5 minute offered rate 0 bps, drop rate 0 bps
> Match: access-group 15
> Queueing
> Output Queue: Conversation 25
> Bandwidth 25 (%)
> Bandwidth 16 (kbps) Max Threshold 64 (packets)
> (pkts matched/bytes matched) 0/0
> (depth/total drops/no-buffer drops) 0/0/0
>
> Class-map: traffic-b (match-all)
> 0 packets, 0 bytes
> 5 minute offered rate 0 bps, drop rate 0 bps
> Match: access-group 25
> Queueing
> Output Queue: Conversation 26
> Bandwidth 50 (%)
> Bandwidth 32 (kbps) Max Threshold 64 (packets)
> (pkts matched/bytes matched) 0/0
> (depth/total drops/no-buffer drops) 0/0/0
>
> Class-map: class-default (match-any)
> 0 packets, 0 bytes
> 5 minute offered rate 0 bps, drop rate 0 bps
> Match: any
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Nov 06 2005 - 22:00:51 GMT-3