Re: Service Policy on Frame Relay

From: Jason Madsen (madsen.jason@gmail.com)
Date: Tue Nov 18 2008 - 00:49:50 ARST


sorry...kind of fat fingered something in my last posting. with this form
of policy, "frame-relay traffic-shaping" isn't even required on the
interface. that's one of the main benefits of using MQC in this manner
(directed to a specific DLCI and doesn't affect all DLCIs on the interface).

Jason

On Mon, Nov 17, 2008 at 7:38 PM, Jason Madsen <madsen.jason@gmail.com>wrote:

> ...not sure what the original question was, but by the subject line it's
> most likely about applying a service-policy to a frame relay interface.
> one way to do so is to apply it within a frame-relay map-class that's
> applied to your FR interface. example:
>
>
> policy-map MYPOL
> class class-default
> shape average xxxxx xxxx xxxx
> shape adaptive xxxxxxx
>
> map-class frame-relay FRTS
> service-policy out MYPOL
>
> int s0/0
> encap frame
> frame traffic-shaping
>
> int s0/0.12 p
> frame interface-dlci 102
> class FRTS
>
>
> Jason
>
>
> On Mon, Nov 17, 2008 at 7:31 PM, But Nicky <lyredhair@gmail.com> wrote:
>
>> Hi Arm,
>> You must choose first (class-map) when you:
>>
>> - apply to one or more DLCI.
>> - interface FR already apply with command: "Frame-relay
>> traffic-shapping".
>>
>> Else, the second can be applied.
>>
>> Regards,
>> But Nguyen,
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net



This archive was generated by hypermail 2.1.4 : Mon Dec 01 2008 - 08:18:30 ARST