Re: MQC FRTS

Frame-relay traffic-shaping on the interface.

Sent from handheld.

On Jul 21, 2009, at 12:40 PM, "Molomo" <letjedilakopa_at_gmail.com> wrote:

> Group,
>
> I have labbed the two scenarios below and scenario 1 is not giving
> me any
> output when I run *sh policy-map int s1/0* . I expected to get the
> same
> result. What am I missing,
>
> ------Scenario 1---------------
>
> class-map match-all VOICE
> match protocol rtp
>
> policy-map FRTS
> class VOICE
> priority 64
> class class-default
> shape average 128000
>
> map-class frame-relay DLCI_105
> service-policy output FRTS
>
> interface Serial1/0
> ip address 10.0.0.1 255.255.255.0
> encapsulation frame-relay
> frame-relay map ip 10.0.0.5 105 br
> frame-relay interface-dlci 105
> class DLCI_105
> no frame-relay inverse-arp
> end
>
> ----------Scenario 2 -----------------
>
> class-map match-all VOICE
> match protocol rtp
>
> policy-map VOICE
> class VOICE
> priority 64
> class class-default
>
> policy-map FRTS
> class class-default
> shape average 128000
> service-policy VOICE
>
> map-class frame-relay DLCI_105
> service-policy output FRTS
>
> interface Serial1/0
> ip address 10.0.0.1 255.255.255.0
> encapsulation frame-relay
> frame-relay map ip 10.0.0.5 105 br
> frame-relay interface-dlci 105
> class DLCI_105
> no frame-relay inverse-arp
> end
>
>
> 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
Received on Tue Jul 21 2009 - 12:47:23 ART