Thanks Ryan, it makes sense now... the output was not showing because I was
using a non-existing DLCI. I tried with an existing DLCI it actually doesn't
not allow applying the map-class under interface-dlci.
Thanks a lot
On Tue, Jul 21, 2009 at 8:33 PM, Ryan West <rwest_at_zyedge.com> wrote:
>  You pretty much answered your own question.  You have to apply the
> shaping first, then your service-policy is called from the class-default
> class, like your second example.  Im not sure why you wouldnt get any
> output, but you wont accomplish the shaping properly unless its called
> from class-default and you cant adjust the shaper first without first
> defining the shaper.
>
>
>
> -ryan
>
>
>
> *From:* Molomo [mailto:letjedilakopa_at_gmail.com]
> *Sent:* Tuesday, July 21, 2009 2:13 PM
>
> *To:* Ryan West
> *Cc:* ccielab_at_groupstudy.com
> *Subject:* Re: MQC FRTS
>
>
>
> Ryan,
>
> With first scenario ( without nested policy-map), sho policy-map int s1/0
> does not gave any output.
> See output from second scenario ( with nested policy-map),
>
> R1#sho policy-map int s1/0
>  Serial1/0: DLCI 105 -
>
>   Service-policy output: FRTS
>
>     Class-map: class-default (match-any)
>       0 packets, 0 bytes
>       5 minute offered rate 0 bps, drop rate 0 bps
>       Match: any
>       Traffic Shaping
>            Target/Average   Byte   Sustain   Excess    Interval  Increment
>              Rate           Limit  bits/int  bits/int  (ms)      (bytes)
>            128000/128000    1984   7936      7936      62        992
>
>         Adapt  Queue     Packets   Bytes     Packets   Bytes     Shaping
>         Active Depth                         Delayed   Delayed   Active
>         -      0         0         0         0         0         no
>
>       Service-policy : VOICE
>
>         Class-map: VOICE (match-all)
>           0 packets, 0 bytes
>           5 minute offered rate 0 bps, drop rate 0 bps
>           Match: protocol rtp
>           Queueing
>             Strict Priority
>             Output Queue: Conversation 24
>             Bandwidth 24 (kbps) Burst 600 (Bytes)
>             (pkts matched/bytes matched) 0/0
>             (total drops/bytes drops) 0/0
>
>         Class-map: class-default (match-any)
>           0 packets, 0 bytes
>           5 minute offered rate 0 bps, drop rate 0 bps
>           Match: any
> R1#
>
>
>  Molomo
>
>
>
>
>  On Tue, Jul 21, 2009 at 8:02 PM, Ryan West <rwest_at_zyedge.com> wrote:
>
> You are correct, can you post the output from your sh policy-map int
> s1/0?   Whats different?
>
>
>
> -ryan
>
>
>
> *From:* Molomo [mailto:letjedilakopa_at_gmail.com]
> *Sent:* Tuesday, July 21, 2009 1:57 PM
> *To:* Ryan West
> *Cc:* ccielab_at_groupstudy.com
> *Subject:* Re: MQC FRTS
>
>
>
> Ryan,
> My understanding is that frame-relay traffic-shaping can only be used with
> GTS and Legacy FRTS not MQC FRTS.
>
> I'll lab and see.
>
> Rdgs,
> Molomo
>
> On Tue, Jul 21, 2009 at 6:47 PM, Ryan West <rwest_at_zyedge.com> wrote:
>
> 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 - 21:02:26 ART
This archive was generated by hypermail 2.2.0 : Sat Aug 01 2009 - 13:10:23 ART