From: ccie2be (ccie2be@nyc.rr.com)
Date: Wed Apr 28 2004 - 08:51:41 GMT-3
Definately an interesting question.
I think your first method doesn't fulfill your stated goal of reserving up
to 50% of the bandwidth because with that config you're assuming that the
50% is split between the 2 dlci's. I'm not sure that's a valid assumption.
I think the result of your first approach is that only 25% of the bandwidth
of the interface can be used for FTP traffic.
Again, I want to emphasize that I don't know for sure, but it depends on
where the percentage is done. If it's done at the pvc level, then your
config is correct since 25% + 25% = 50%. but, if it's done at the interface
level, you're reducing your FTP traffic to half of what you want.
Hopefully, we're hear from someone who knows for sure and get this question
all cleared up.
----- Original Message -----
From: <gladston@br.ibm.com>
To: <ccielab@groupstudy.com>
Sent: Monday, April 26, 2004 1:53 PM
Subject: QoS on Frame Relay Physical Interface
> Any help to understand the difference of implementing CBWFQ on the
physical interface and on the map-class?
>
> The goal is to reserve 50% of the bandwidth for FTP traffic traversing the
serial 0/0.
>
> Router R1 is connected to R2 and R3 using serial 0/0 (frame-relay
encapsulation)
>
> This is the first approach I tried:
>
> class-map match-all FTP
> match access-group 177
> !
> policy-map QOS
> class FTP
> bandwidth percent 25
> !
> interface Serial0/0
> ip address 142.20.125.5 255.255.255.0
> encapsulation frame-relay
> service-policy output QOS
> frame-relay map ip 142.20.125.1 12 broadcast
> frame-relay map ip 142.20.125.2 13 broadcast
> !
> access-list 177 permit tcp any any eq ftp
> access-list 177 permit tcp any any eq ftp-data
>
>
> And this is the second:
>
> class-map match-all FTP
> match access-group 177
> !
> policy-map QOS
> class FTP
> bandwidth percent 50
> !
> interface Serial0/0
> ip address 1.1.1.1 255.255.255.0
> encapsulation frame-relay
> frame-relay traffic-shaping
> frame-relay map ip 1.1.1.2 12 broadcast
> frame-relay map ip 1.1.1.3 13 broadcast
> !
> frame-relay interface-dlci 12
> class QoS
> frame-relay interface-dlci 13
> class QoS
> !
> map-class frame-relay QoS
> service-policy output QOS
> !
> access-list 177 permit tcp any any eq ftp
> access-list 177 permit tcp any any eq ftp-data
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon May 03 2004 - 19:48:57 GMT-3