From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Fri Apr 20 2007 - 14:50:48 ART
With the third option you have one single output queue that both
circuits are contending for. With the first two options you have two
separate shaping queues in which you can perform more granular fancy
queueing. Also platform and version support will vary for which options
you can use. Ultimately they all accomplish the same goal but they are
different behind the scenes.
HTH,
Brian McGahan, CCIE #8593 (R&S/SP)
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Eric Poulin
Sent: Friday, April 20, 2007 10:36 AM
To: ccielab@groupstudy.com
Subject: Need help! Can we do per-DLCI traffic shaping with MQC alone?
Hi Group,
I have configured Frame Relay traffic shaping using FRTS, MQC FRTS and
MQC on a
multipoint interface. Each DLCI, 501 and 503, have different shaping
rate, 50kbps and
1Mbps respectively. From looking at the "sh traffic-shape" or "sh
policy-map int", they
are all performing per-DLCI traffic shaping and seems to be equivalent.
However, I have
never seen any workbook using the third method (MQC with match fr-dlci).
Is this a bad
implementation?
Thanks for your input.
Eric
---------------------------------------------------
FRTS
---------------------------------------------------
interface Serial0/0
frame-relay traffic-shaping
!
interface Serial0/0.10 multipoint
frame-relay map ip 155.1.0.1 501 broadcast
frame-relay map ip 155.1.0.3 503 broadcast
frame-relay interface-dlci 501
class FRTS_DLCI501
frame-relay interface-dlci 503
class FRTS_DLCI503
!
map-class frame-relay FRTS_DLCI501
frame-relay cir 50000
!
map-class frame-relay FRTS_DLCI503
frame-relay cir 1000000
-------------------------------------------
R5#sh traffic-shape
Interface Se0/0.10
Access Target Byte Sustain Excess Interval Increment
Adapt
VC List Rate Limit bits/int bits/int (ms) (bytes)
Active
503 1000000 7875 1000000 0 63 7875 -
501 50000 781 50000 0 125 781 -
---------------------------------------------------
MQC with FRTS
---------------------------------------------------
policy-map DLCI503
class class-default
shape average 1000000
policy-map DLCI501
class class-default
shape average 50000
!
interface Serial0/0
!
interface Serial0/0.10 multipoint
frame-relay map ip 155.1.0.1 501 broadcast
frame-relay map ip 155.1.0.3 503 broadcast
frame-relay interface-dlci 501
class FRTS_DLCI501
frame-relay interface-dlci 503
class FRTS_DLCI503
!
map-class frame-relay FRTS_DLCI501
service-policy output DLCI501
!
map-class frame-relay FRTS_DLCI503
service-policy output DLCI503
-------------------------------------------
R5#sh policy-map int s0/0.10
Serial0/0.10: DLCI 501 -
Service-policy output: DLCI501
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
Traffic Shaping
Target/Average Byte Sustain Excess Interval
Increment
Rate Limit bits/int bits/int (ms) (bytes)
50000/50000 2000 8000 8000 160 1000
Adapt Queue Packets Bytes Packets Bytes Shaping
Active Depth Delayed Delayed Active
- 0 0 0 0 0 no
Serial0/0.10: DLCI 503 -
Service-policy output: DLCI503
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
Traffic Shaping
Target/Average Byte Sustain Excess Interval
Increment
Rate Limit bits/int bits/int (ms) (bytes)
1000000/1000000 6250 25000 25000 25 3125
Adapt Queue Packets Bytes Packets Bytes Shaping
Active Depth Delayed Delayed Active
- 0 0 0 0 0 no
---------------------------------------------------
MQC alone
---------------------------------------------------
class-map match-all DLCI503
match fr-dlci 503
class-map match-all DLCI501
match fr-dlci 501
!
policy-map SHAPING
class DLCI503
shape average 1000000
class DLCI501
shape average 50000
!
interface Serial0/0
!
interface Serial0/0.10 multipoint
frame-relay map ip 155.1.0.1 501 broadcast
frame-relay map ip 155.1.0.3 503 broadcast
service-policy output SHAPING
!
-------------------------------------------
R5#sh policy-map interface s0/0.10
Serial0/0.10
Service-policy output: SHAPING
Class-map: DLCI503 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: fr-dlci 503
Traffic Shaping
Target/Average Byte Sustain Excess Interval
Increment
Rate Limit bits/int bits/int (ms) (bytes)
1000000/1000000 6250 25000 25000 25 3125
Adapt Queue Packets Bytes Packets Bytes Shaping
Active Depth Delayed Delayed Active
- 0 0 0 0 0 no
Class-map: DLCI501 (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: fr-dlci 501
Traffic Shaping
Target/Average Byte Sustain Excess Interval
Increment
Rate Limit bits/int bits/int (ms) (bytes)
50000/50000 2000 8000 8000 160 1000
Adapt Queue Packets Bytes Packets Bytes Shaping
Active Depth Delayed Delayed Active
- 0 0 0 0 0 no
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
This archive was generated by hypermail 2.1.4 : Tue May 01 2007 - 08:28:36 ART