From: kym blair (kymblair@hotmail.com)
Date: Sun Jan 12 2003 - 03:12:19 GMT-3
Rick,
Nate's right ... you need "vofr cisco" on both routers. I think you'll also
need smaller fragments than 1500 so your data has a chance of getting
through. Here's what I'd suggest(below). You're wise to study this before
NMC1; you'll be ready to absorb the details of their lesson on this.
If this doesn't work, cut your CIR and MINCIR down to realistic frame-relay
sizes (128K/64K or smaller if you have other DLCIs which would also like
some bandwidth). For voice bandwidth, I think you need at least 10K (better
12K) per call; if you want two calls, then at leaset 24K. Your 78K may
exceed the capability of the link.
>Host r6
>interface Serial0/0
> no ip address
> encapsulation frame-relay
> clockrate 2000000
> frame-relay traffic-shaping
>!
>interface Serial0/0.1 point-to-point
> ip address 150.150.10.1 255.255.255.0
> frame-relay interface-dlci 100
> class voice
vofr cisco <-----------
>!
>map-class frame-relay voice
> frame-relay cir 768000
> frame-relay bc 1000
> frame-relay mincir 120000
> no frame-relay adaptive-shaping
> frame-relay fair-queue
> frame-relay voice bandwidth 78000
> frame-relay fragment 120 <---- smaller fragments
>!
>!
>voice-port 1/0/0
>!
>voice-port 1/0/1
>!
>dial-peer cor custom
>!
>!
>!
>dial-peer voice 1 pots
> destination-pattern 1111
> port 1/0/0
>!
>dial-peer voice 2 vofr
> destination-pattern 2222
> session target Serial0/0 100
---------------------------------------------------------
>Host r11
>interface Serial0/0
> no ip address
> encapsulation frame-relay
> frame-relay traffic-shaping
> frame-relay lmi-type ansi
>!
>interface Serial0/0.1 point-to-point
> ip address 150.150.10.2 255.255.255.0
> frame-relay interface-dlci 200
> class voice
vofr cisco <--------------------------
>!
>!
>map-class frame-relay voice
> frame-relay cir 768000
> frame-relay bc 1000
> frame-relay mincir 120000
> no frame-relay adaptive-shaping
> frame-relay fair-queue
> frame-relay voice bandwidth 78000
> frame-relay fragment 120 <------- smaller
>!
>!
>voice-port 1/0/0
>!
>voice-port 1/0/1
>!
>dial-peer cor custom
>!
>!
>!
>dial-peer voice 1 pots
> destination-pattern 2222
> port 1/0/0
>!
>dial-peer voice 2 vofr
> destination-pattern 1111
> session target Serial0/0 200
>!
>!
>!
>QUESIONS: about these commands, which one are nessary? I guess I still
>don't
>no understand the Bc, etc
>map-class frame-relay voice
>frame-relay cir 768000
>frame-relay bc 1000
>frame-relay mincir 120000
>no frame-relay adaptive-shaping
>frame-relay fair-queue
> frame-relay voice bandwidth 78000
> frame-relay fragment 1500
I'm not good with the different values in FRTS. Here's as I understand, but
others have posted excellent discussions; if you have time, research the
archives. MINCIR is what you've purchased (will never have DE bit set).
CIR is max for the link (don't exceed remote end capability if it is smaller
than local end); probably twice the size of MINCIR. BC is 1/8 of CIR. You
correctly turned on global traffic-shaping and then turned off
adaptive-shaping in the map-class since you are not interested in FECN/BECN
throttling for voice traffic. Fragments causes larger packets to be split
into smaller packets so voice can get time-slots more frequently, and so
there are slots availabe for data packets. Your data packets (e.g., ping
tests) won't go through if you forget to fragment, and they may not go
through if you make the size so large. I think you wouldn't have to
fragment if the link is T1 or larger.
HTH, Kym
>From: "Nathan Chessin" <nchessin@cisco.com>
>Reply-To: "Nathan Chessin" <nchessin@cisco.com>
>To: "'Rick'" <ccie_2003@hotmail.com>, "'kym blair'" <kymblair@hotmail.com>
>CC: <ccielab@groupstudy.com>
>Subject: RE: question about VOFR
>Date: Sat, 11 Jan 2003 21:20:55 -0800
>
>what about the "vofr cisco" command under the interface-dlci command?
>
>Nate
>
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > Rick
> > Sent: Saturday, January 11, 2003 6:40 PM
> > To: kym blair
> > Cc: ccielab@groupstudy.com
> > Subject: question about VOFR
> >
> >
> > Kym, or any other VOFR gurus,
> >
> > Of the below list frame-relay commands. Which one are needed
> > to pass data and
> > voice... I tried to use only frame-relay voice bandwidth
> > 7800, and of course I
> > could not ping, but I couldn't call the other phone either..
> > I found these
> > commands on the CCO and I can ping, but I still can call
> > between routers. I
> > will attach the configs below.
> > What I'm I doing wrong.. I trying to cram as much as possible
> > before I go to
> > Netmaster NMC-1 at the end of the month... I want to have all
> > the basics down
> > so I can walk away with the advanced topics...
> >
> > Thanks,
> > Rick
> >
> > !There are only two routers and a frame switch
> >
> > Host r6
> > interface Serial0/0
> > no ip address
> > encapsulation frame-relay
> > clockrate 2000000
> > frame-relay traffic-shaping
> > !
> > interface Serial0/0.1 point-to-point
> > ip address 150.150.10.1 255.255.255.0
> > frame-relay interface-dlci 100
> > class voice
> > !
> > map-class frame-relay voice
> > frame-relay cir 768000
> > frame-relay bc 1000
> > frame-relay mincir 120000
> > no frame-relay adaptive-shaping
> > frame-relay fair-queue
> > frame-relay voice bandwidth 78000
> > frame-relay fragment 1500
> > !
> > !
> > voice-port 1/0/0
> > !
> > voice-port 1/0/1
> > !
> > dial-peer cor custom
> > !
> > !
> > !
> > dial-peer voice 1 pots
> > destination-pattern 1111
> > port 1/0/0
> > !
> > dial-peer voice 2 vofr
> > destination-pattern 2222
> > session target Serial0/0 100
> >
> > Host r11
> > interface Serial0/0
> > no ip address
> > encapsulation frame-relay
> > frame-relay traffic-shaping
> > frame-relay lmi-type ansi
> > !
> > interface Serial0/0.1 point-to-point
> > ip address 150.150.10.2 255.255.255.0
> > frame-relay interface-dlci 200
> > class voice
> > !
> > !
> > map-class frame-relay voice
> > frame-relay cir 768000
> > frame-relay bc 1000
> > frame-relay mincir 120000
> > no frame-relay adaptive-shaping
> > frame-relay fair-queue
> > frame-relay voice bandwidth 78000
> > frame-relay fragment 1500
> > !
> > !
> > voice-port 1/0/0
> > !
> > voice-port 1/0/1
> > !
> > dial-peer cor custom
> > !
> > !
> > !
> > dial-peer voice 1 pots
> > destination-pattern 2222
> > port 1/0/0
> > !
> > dial-peer voice 2 vofr
> > destination-pattern 1111
> > session target Serial0/0 200
> > !
> > !
> > !
> > QUESIONS: about these commands, which one are nessary? I
> > guess I still don't
> > no understand the Bc, etc
> > map-class frame-relay voice
> > frame-relay cir 768000
> > frame-relay bc 1000
> > frame-relay mincir 120000
> > no frame-relay adaptive-shaping
> > frame-relay fair-queue
> > frame-relay voice bandwidth 78000
> > frame-relay fragment 1500
> > .
>.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:47 GMT-3