From: Danny.Andaluz@triaton-na.com
Date: Fri Sep 19 2003 - 12:47:56 GMT-3
Thanks, Scott.
Danny
-----Original Message-----
From: Scott Morris [mailto:swm@emanon.com]
Sent: Friday, September 19, 2003 8:50 AM
To: Andaluz, Danilo, Triaton/NA; ccielab@groupstudy.com
Subject: RE: FRTS scenario
If your data DLCI is to be 50% of your port speed, then the CIR should be
128k. Personally, for data, I wouldn't set a mincir unless something in the
scenario keyed you into that. For voice, as you have done, the mincir and
cir are typically equal.
It seems that Cisco's "default" or "recommended by example" method of
queuing for voice would NOT put the fair-queuing on the voice class but
would on the data class.
If you wish your data vc to use other bandwidth as available, set your be to
allow up to 192k (265k port minus the 64k you want voice to have
unhindered).
Otherwise, you are on the right track with your Bc/Tc values being different
for voice and data. As for getting different answer, well... Traffic
shaping and queuing stuff is one of those amorphous things that since there
are many variables, there are many potential ways of thought. Key in on
what is specifically said in the scenario you have, match those things, and
everything else will start to fall into place. If it doesn't you're free to
make it up. :)
HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, CISSP,
JNCIS, et al. IPExpert CCIE Program Manager IPExpert Sr. Technical
Instructor swm@emanon.com/smorris@ipexpert.net
http://www.ipexpert.net
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Danny.Andaluz@triaton-na.com
Sent: Friday, September 19, 2003 12:03 AM
To: ccielab@groupstudy.com
Subject: FRTS scenario
Hello Group,
A scenario for FRTS on a lab that I'm doing states:
"Assume voice traffic is will be passing over dlci 101, which has 64k link
speed. Configure Frame Relay such that there is no latency and packets are
not dropped. DLCI 102 has 50% BW of port speed. Configure CIR, Bc and Be
accordingly by maintaining Tc's default value and interface queueing default
mechanism. Port speed Between r1 and r2 is 256k."
R1
|
| |
dlci 101 | | dlci 102
| |
|
R2
Here's what I have as far as configs. I get all sorts of different answers
for what this should be. Hopefully I can get this cleared up. You think you
understand something, and then you get punched in the mouth.
Thanks,
Danny
R1
interface Serial0.8 point-to-point
ip address 172.16.78.1 255.255.255.252
frame-relay interface-dlci 101
class Voice
!
interface Serial0.9 point-to-point
ip address 172.16.78.5 255.255.255.252
frame-relay interface-dlci 102
class Data
map-class frame-relay Voice
frame-relay cir 64000
frame-relay bc 640
frame-relay be 0
frame-relay mincir 64000
no frame-relay adaptive-shaping
frame-relay fair-queue
frame-relay fragment 80
!
map-class frame-relay Data
frame-relay cir 256000
frame-relay bc 32000
frame-relay be 0
frame-relay mincir 128000
no frame-relay adaptive-shaping
frame-relay fair-queue
R2
interface Serial0.2 point-to-point
ip address 172.16.78.2 255.255.255.252
frame-relay interface-dlci 101
class voice
!
interface Serial0.3 point-to-point
ip address 172.16.78.6 255.255.255.252
frame-relay interface-dlci 102
class data
map-class frame-relay voice
frame-relay cir 64000
frame-relay bc 640
frame-relay be 0
no frame-relay adaptive-shaping
frame-relay fair-queue
frame-relay fragment 80
!
map-class frame-relay data
frame-relay cir 256000
frame-relay bc 32000
frame-relay be 0
no frame-relay adaptive-shaping
frame-relay fair-queue
***Get your CCIE and a FREE vacation: Shop.GroupStudy.com***
This archive was generated by hypermail 2.1.4 : Wed Oct 01 2003 - 07:24:31 GMT-3