From: Ty (tycampbell@comcast.net)
Date: Sat Jun 12 2004 - 23:37:42 GMT-3
you are correct...my mistake... :-)
----- Original Message -----
From: "Richard Dumoulin" <richard.dumoulin@vanco.es>
To: "Ty" <tycampbell@comcast.net>; "ccLABs" <ccLABs@wanit.com>
Cc: <ccielab@groupstudy.com>
Sent: Saturday, June 12, 2004 9:27 PM
Subject: RE: Traffic Priority
> Hi Ty,
>
> I have seen in your acl
>
> access-list 101 permit udp any any range 16383 16384.
>
> Should not it be
>
> access-list 101 permit udp any any range 16383 32767 ?
>
> I think it is in frame-relay where you configure the range instead,
>
> frame ip rtp priority 16384 16383
>
>
> Please correct me if I'm wrong,
>
> --Richard
>
> -----Original Message-----
> From: Ty [mailto:tycampbell@comcast.net]
> Sent: domingo, 13 de junio de 2004 4:13
> To: ccLABs
> Cc: ccielab@groupstudy.com
> Subject: Re: Traffic Priority
>
>
> rsvp is done on the interface with "ip rsvp bandwidth" and you can specify
> the parameters that you want after that. This should be applied to all
> routers in the path that your voice traffic is taking
>
> CBWFQ is a little more difficult, but here is an example from a lab I was
> working on this evening: (irrelevant parts omitted) you may have to change
> things, depends on your setup..etc....but this should give you a rough
idea
>
> class-map match-all voice
> match access-group 101
> !
> !
> policy-map traffic
> class voice <- matches class-map voice
> priority 128
> class class-default <- all other traffic
> fair-queue
> !
> int s0
> service-policy output traffic
> !
> access-list 101 permit tcp any eq 1720 any
> access-list 101 permit tcp any any eq 1720
> access-list 101 permit udp any any range 16383 16384
> ----- Original Message -----
> From: "ccLABs" <ccLABs@wanit.com>
> To: "'Ty'" <tycampbell@comcast.net>
> Sent: Saturday, June 12, 2004 8:54 PM
> Subject: RE: Traffic Priority
>
>
> > Ty:
> >
> > What are the commands to implement RSVP or CBWFQ
> >
> > Thanks In Advance
> >
> > ----------------------------------------------------------------------
> > ----
> --
> > -------------------------------
> > DISCLAIMER: If You Are Not The Intended Recipient Do Not Access Or Use
> > In Any Way! -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Ty
> > Sent: Saturday, June 12, 2004 8:11 PM
> > To: rexperts; ccielab@groupstudy.com
> > Subject: Re: Traffic Priority
> >
> > seems like you can use either RSVP or CBWFQ for this then
> >
> >
> > ----- Original Message -----
> > From: "rexperts" <routerexpert@yahoo.com>
> > To: "Ty" <tycampbell@comcast.net>; <ccielab@groupstudy.com>
> > Sent: Saturday, June 12, 2004 6:59 PM
> > Subject: Re: Traffic Priority
> >
> >
> > > There is a full T1, however, when it gets tight I want the voice to
> always
> > take priority.
> > >
> > > Thanks In Advance
> > >
> > > Ty <tycampbell@comcast.net> wrote:
> > > Sounds like CBWFQ to me
> > >
> > > how much bandwidth do want to allocate to voice, and how much to
> > > data ?
> > >
> > >
> > >
> > > ----- Original Message -----
> > > From: "rexperts"
> > > To:
> > > Sent: Saturday, June 12, 2004 4:22 PM
> > > Subject: Traffic Priority
> > >
> > >
> > > > Simple setup
> > > >
> > > > This T1 line handles Voice and Data traffic.
> > > > How do I set up queuing to give priority to voice traffic?
> > > >
> > > > Interface FastEthernet 0
> > > > IP Address 12.12.12.1 255.255.255.248
> > > > Speed auto
> > > >
> > > > Interface Serial 0
> > > > IP Unnumbered
> > > > Service-module T1 timeslots 1-24
> > > >
> > > > Thanks In Advance
> > > >
> > > >
> > > >
> > > > ---------------------------------
> > > > Do you Yahoo!?
> > > > Friends. Fun. Try the all-new Yahoo! Messenger
> > >
> > >
> > >
> > > ---------------------------------
> > > Do you Yahoo!?
> > > Friends. Fun. Try the all-new Yahoo! Messenger
>
>
>
> **********************************************************************
> Any opinions expressed in the email are those of the individual and not
> necessarily the company. This email and any files transmitted with it are
> confidential and solely for the use of the intended recipient. If you are
> not the intended recipient or the person responsible for delivering it to
> the intended recipient, be advised that you have received this email in
> error and that any dissemination, distribution, copying or use is strictly
> prohibited.
>
> If you have received this email in error, or if you are concerned with the
> content of this email please e-mail to: e-security.support@vanco.co.uk
>
> The contents of an attachment to this e-mail may contain software viruses
> which could damage your own computer system. While the sender has taken
> every reasonable precaution to minimise this risk, we cannot accept
> liability for any damage which you sustain as a result of software
viruses.
> You should carry out your own virus checks before opening any attachments
to
> this e-mail.
> **********************************************************************
This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:39 GMT-3