Glad you asked, I had the same question several months ago.
12.1(5)T and 12.2(1-3) this is supported see example configuration below.
The config is different depending on the platform, don't ask me why it just
is.
- Dustin -
**** On 7500 with nbma interface
class-map match-all voicegws
match access-group name voicegws
class-map match-all matchhoot
match ip precedence 5
!
!
policy-map qos-hoot1
class matchhoot
priority 80
class class-default
fair-queue
random-detect
policy-map shaper-512
class class-default
shape average 512000 2048 0
service-policy qos-hoot1
policy-map shaper-192
class class-default
shape average 192000 768 0
service-policy qos-hoot1
policy-map shaper-384
class class-default
shape average 384000 1536 0
service-policy qos-hoot1
interface Hssi5/1/0
ip address 10.253.1.1 255.255.255.0
ip pim nbma-mode
ip pim sparse-mode
encapsulation frame-relay
ip mroute-cache distributed
load-interval 30
hssi internal-clock
frame-relay interface-dlci 502
class frmap-384
frame-relay interface-dlci 503
class frmap-192
frame-relay interface-dlci 504
class frmap-512
no frame-relay broadcast-queue
frame-relay ip rtp header-compression
!
map-class frame-relay frmap-384
no frame-relay adaptive-shaping
service-policy output shaper-384
frame-relay fragment 640
!
map-class frame-relay frmap-192
no frame-relay adaptive-shaping
service-policy output shaper-192
frame-relay fragment 320
!
map-class frame-relay frmap-512
no frame-relay adaptive-shaping
service-policy output shaper-512
frame-relay fragment 960
******** On 36xx or 26xx with subinterface per pvc.
class-map match-all matchhoot
match ip precedence 5
match ip dscp 46
!
!
policy-map qos-hoot1
class matchhoot
priority 80
class class-default
fair-queue
random-detect
interface Serial0/0
no ip address
encapsulation frame-relay
load-interval 30
clockrate 512000
frame-relay traffic-shaping
!
interface Serial0/0.1 point-to-point
bandwidth 384
ip address 10.253.1.2 255.255.255.0
ip pim sparse-mode
frame-relay class frmap-test
frame-relay interface-dlci 500
frame-relay ip rtp header-compression
!
map-class frame-relay frmap-384
no frame-relay adaptive-shaping
frame-relay cir 384000
frame-relay bc 3840
frame-relay be 0
service-policy output qos-hoot1
frame-relay fragment 640
!
map-class frame-relay frmap-192
no frame-relay adaptive-shaping
frame-relay cir 192000
frame-relay bc 2304
frame-relay be 0
service-policy output qos-hoot1
frame-relay fragment 320
!
map-class frame-relay frmap-512
no frame-relay adaptive-shaping
frame-relay cir 512000
frame-relay bc 6144
frame-relay be 0
service-policy output qos-hoot1
frame-relay fragment 960
-----Original Message-----
From: Edward S. Desouza [mailto:edward_desouza@yahoo.com]
Sent: Thursday, August 16, 2001 1:16 AM
To: cisco-nsp@puck.nether.net
Subject: [nsp] CBWFQ On frame relay Interfaces
Hi,
I have a frame Relay PVC of 16 k CIR. My access
links at both end are E1. I need to configure class
based weighted fair queueing on this interface.
Class Based Weighted fair queuing allows a
percentage of bandwdith to be configured per traffic
class. However, Since my access link is much higher
than the PVC, My router will keep on pumping data into
the FR network since the access speed is much higher
than the PVC.
A solution to the above would be to confiugre FRTS.
However, FRTS does not support CBWFQ !
Have any of you guys run into a similar problem
where you need to do a class based queuing on a frame
relay PVC ? I dont want to use multiple PVC's for
multiple classes of traffic.
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:49 EDT