From: Bill Dellamar (wdellamar@xxxxxxxxx)
Date: Sun Jan 07 2001 - 20:24:08 GMT-3
The access-list voice_traffic was just a figurative
example, not how it's configured. Also, I was only
asking how to seperate traffic types onto pvc's, not
how to shape the traffic once it is on the pvc (bc,
be, etc.). I understand the theory just fine, I just
wasn't sure how to seperate traffic onto different
pvc's.
--- Justin Menga <Justin.Menga@computerland.co.nz>
wrote:
> No this won't work.
>
> Your access-list is wrong - 'access-list 101 permit
> voice_traffic' does not
> make sense. You also have not set any parameters to
> traffic shape to (bc,
> be, etc.)
>
> I suggest to get your nose into some books and get
> the theory under your
> belt.
>
> Regards,
>
> Justin Menga CCIE #6640 MCSE+I CCSE
> WAN Specialist
> Computerland New Zealand
> PO Box 3631, Auckland
> DDI: (+64) 9 360 4864 Mobile: (+64) 25 349 599
> mailto: justin.menga@computerland.co.nz
>
>
> -----Original Message-----
> From: Bill Dellamar [mailto:wdellamar@yahoo.com]
> Sent: Monday, 8 January 2001 2:01 a.m.
> To: ccielab@groupstudy.com
> Subject: voice and frame
>
>
> To answer my own question, would something like this
> work using frame relay traffic shaping.
>
> int serial 0
> frame-relay traffic-shaping
> int serial0.1 point-to-point
> frame-relay interface-dlci 102
> class voice_traffic
> int serial0.2 point-to-point
> frame-relay interface-dlci 103
> class ip_traffic
> !
> map-class frame-relay voice_traffic
> frame-relay priority-group 1
> !
> map-class frame-relay ip_traffic
> frame-relay priority-group 2
> !
> priority-list 1 list 101
> !
> priority-list 2 ip high
> !
> access-list 101 permit voice_traffic
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:23 GMT-3