From: Jack Heney (jheneyccie@xxxxxxxxxxx)
Date: Tue Nov 07 2000 - 19:48:16 GMT-3
Sorry about the empty post...Hit the wrong key by accident...I've manged to
get frame-relay traffic-shaping and priority up and running, but I don't
need ELMI for the priority as stated on CCO, which I haven't quite figured
out....here's what I did:
Frame-relay link between R3 and R4 with 4 active dlci's (403, 413, 423,
433). I wanted to test out priority, so I set up a priority list that gives
ICMP high priority, TCP traffic medium priority, and everything else will
end up with normal priority. I then configured 2 map classes - "pings"
(with a CIR of 128000) and "telnet" (with a CIR of 64000) to set the
frame-relay parameters for each VC. Here's the config on R4 (R3 is the same
except for the IP address):
interface Serial0/0
ip address 9.1.1.4 255.255.255.0
encapsulation frame-relay
no ip mroute-cache
no fair-queue
frame-relay traffic-shaping
frame-relay priority-dlci-group 1 403 413 423 433
frame-relay interface-dlci 403
class pings
frame-relay interface-dlci 413
class telnet
frame-relay interface-dlci 423
frame-relay interface-dlci 433
!
router rip
version 2
network 9.0.0.0
!
map-class frame-relay pings
frame-relay adaptive-shaping becn
frame-relay cir 128000
frame-relay bc 16000
frame-relay mincir 64000
!
map-class frame-relay telnet
frame-relay adaptive-shaping becn
frame-relay cir 64000
frame-relay bc 8000
frame-relay mincir 32000
access-list 100 permit icmp any any
access-list 101 permit tcp any any
priority-list 1 protocol ip high list 100
priority-list 1 protocol ip medium list 101
!
If I understand this correctly, by combining the use of "frame-relay
adaptive-shaping becn" and "frame-relay mincir", if the switch were to send
a BECN along dlci 403 or 413, the virtual circuit would drop down to the
configured mincir. I watched the counters that were listed under "show
frame-relay pvc" and the input/output packet counters on dlci 403 would only
increment if I ping, and on 413 they would only increment if I telnet (or do
something else TCP related). The counters on 423 would increment due to RIP
updates.
I think there is a lot more you can do with FRTS, this is just a sample
configuration I came up with to test out the prioritization. I think I
could also prioritize traffic on an individual DLCI using "frame-relay
priority-group #" in the map-class, so you could actually designate one dlci
for use with TCP traffic, as I have done above, and then use another
priority-list to prioritize certain TCP traffic on that dlci.
If anyone has any commnents on the above or has an interesting
configuration, I'd love to see it.
hth,
Jack
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:43 GMT-3