Re: QOS

From: Narbik Kocharians (narbikk@gmail.com)
Date: Fri Sep 19 2008 - 01:33:12 ART


Thanks,

There is no other way to do it. Simplify and explain.

On Thu, Sep 18, 2008 at 9:27 PM, John Wayne <john.wayne.ccie@gmail.com>wrote:

> Really nice explanation Narbik. Is your class this detailed and easy to
> follow?
>
> On Thu, Sep 18, 2008 at 11:19 PM, Narbik Kocharians <narbikk@gmail.com>wrote:
>
>> *Sorry for the long post and please understand that there are other ways
>> to
>>
>> do this, but here are some ways to configure FRTS:*
>>
>> * *
>>
>> *Example #1:*
>>
>> *In the first example ONLY the traffic shaping is enabled:*
>>
>>
>>
>> R1(config-map-class)#*int s0/0*
>>
>> R1(config-if)#*frame-relay traffic-shaping*
>>
>>
>>
>> *R1#Show traffic-shape*
>>
>>
>>
>> Interface Se0/0
>>
>> Access Target Byte Sustain Excess Interval Increment
>> Adapt
>>
>> VC List Rate Limit bits/int bits/int (ms) (bytes)
>> Active
>>
>> *103 56000 875 7000 0 125 875
>> - *
>>
>> *104 56000 875 7000 0 125 875
>> - *
>>
>> *105 56000 875 7000 0 125 875
>> - *
>>
>> *106 56000 875 7000 0 125 875
>> - *
>>
>> *112 56000 875 7000 0 125 875
>> - *
>>
>> *102 56000 875 7000 0 125 875
>> - *
>>
>>
>>
>> *Note once the traffic shaping is enabled, all the DLCIs are affected and
>> they are shaped to 56k.*
>>
>>
>>
>> *Example #2:*
>>
>> *In this example a map-class called "TST" is configured and it is applied
>> to
>> the main interface:*
>>
>>
>>
>> R1(config)#*map-class frame TST*
>>
>> R1(config-map-class)#*frame-relay cir 64000*
>>
>> R1(config-map-class)#*frame-relay bc 8000*
>>
>> R1(config-map-class)#*frame-relay adaptive-shaping becn*
>>
>>
>>
>> R1(config-map-class)#*int s0/0*
>>
>> R1(config-if)#*frame-relay traffic-shaping*
>>
>> R1(config-if)#*frame-relay class TST*
>>
>>
>>
>> *To verify:*
>>
>>
>>
>> *R1#Show traffic-shape *
>>
>>
>>
>> Interface Se0/0
>>
>> Access Target Byte Sustain Excess Interval Increment
>> Adapt
>>
>> VC List Rate Limit bits/int bits/int (ms) (bytes)
>> Active
>>
>> *103 64000 1000 8000 0 125 1000
>> BECN*
>>
>> *104 64000 1000 8000 0 125 1000
>> BECN*
>>
>> *105 64000 1000 8000 0 125 1000
>> BECN*
>>
>> *106 64000 1000 8000 0 125 1000
>> BECN*
>>
>> *112 64000 1000 8000 0 125 1000
>> BECN*
>>
>> *102 64000 1000 8000 0 125 1000
>> BECN*
>>
>>
>>
>> *Note because the frame-relay class was applied to the main interface,
>> it's
>> policy is applied to all the DLCIs under that interface.*
>>
>>
>>
>> *Example #3*
>>
>> *In this example the frame-relay class was applied to one of the DLCIs
>> (102):*
>>
>>
>>
>> R1(config-if)#*frame-relay interface-dlci 102*
>>
>> R1(config-fr-dlci)#*class TST*
>>
>>
>>
>> *R1#Show traffic-shape*
>>
>>
>>
>> Interface Se0/0
>>
>> Access Target Byte Sustain Excess Interval Increment
>> Adapt
>>
>> VC List Rate Limit bits/int bits/int (ms)
>> (bytes) Active
>>
>> 103 56000 875 7000 0 125
>> 875 -
>>
>> 104 56000 875 7000 0 125
>> 875 -
>>
>> 105 56000 875 7000 0 125
>> 875 -
>>
>> 106 56000 875 7000 0 125
>> 875 -
>>
>> 112 56000 875 7000 0 125
>> 875 -
>>
>> *102 64000 1000 8000 0 125
>> 1000 BECN*
>>
>>
>>
>> *Note since the policy (map-class frame-relay TST) was applied to DLCI
>> 102,
>> it effected DLCI 102 ONLY, but because the "Frame-relay traffic-shaping"
>> command is still configured under the physical interface, the other DLCIs
>> are shaped to 56000 just like the first example. *
>>
>> * *
>>
>> *Example #4*
>>
>> *Note the "Frame-relay traffic-shaping", the "class TST", and the
>> "map-class
>> frame-relay TST" are removed. *
>>
>> *A Policy-map called "TST" is configured and applied to a new map-class
>> called "QOS" using "service-policy out TST" command, and finally the
>> "Map-class frame-relay QOS" is applied to DLCI 102. *
>>
>> * *
>>
>> R1(config)#*int s0/0*
>>
>> R1(config-if)#*no frame-relay traffic-shaping*
>>
>>
>>
>> R1(config-if)#*frame-relay interface-dlci 102*
>>
>> R1(config-fr-dlci)#*no class TST*
>>
>>
>>
>> R1(config)#*no map-class frame TST*
>>
>>
>>
>> R1(config)#*policy-map TST*
>>
>> R1(config-pmap)#*class class-default*
>>
>> R1(config-pmap-c)#*shape average 64000 8000* *0*
>>
>> R1(config-pmap-c)#*Shape adaptive 32000*
>>
>>
>>
>> R1(config)#*map-class frame-relay QOS*
>>
>> R1(config-map-class)#*service-policy out TST*
>>
>>
>>
>> R1(config-map-class)#*int s0/0*
>>
>> R1(config-if)#*frame-relay interface 102*
>>
>> R1(config-fr-dlci)#*class QOS*
>>
>> * *
>>
>> *To verify:*
>>
>>
>>
>> *R1#Show policy-map interface S0/0 *
>>
>>
>>
>> Serial0/0: DLCI 102 -
>>
>> Service-policy output: TST
>>
>> 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)
>>
>> *64000/64000 1000 8000 0 125
>> 1000
>> *
>>
>>
>>
>> Adapt Queue Packets Bytes Packets Bytes
>> Shaping
>>
>> Active Depth Delayed Delayed
>> Active
>>
>> *BECN* 0 0 0 0
>> 0 no* *
>>
>>
>> On Thu, Sep 18, 2008 at 12:39 PM, Scott Morris <
>> smorris@internetworkexpert.com> wrote:
>>
>> > Follow the flow of traffic. If you left everything alone, where does
>> the
>> > IP
>> > packet go? Once you apply one mechanism (physical/subint/per-dlci),
>> does
>> > anything change?
>> >
>> > Remember to look at "show frame pvc" and see exactly how many dlcis
>> report
>> > to that particular interface. Because applying a policy to an interface
>> > will equally affect all dlci's that are there...
>> >
>> > So it's picking and choosing exactly what you do, or do not, want
>> affected.
>> >
>> > HTH,
>> >
>> > Scott
>> >
>> > -----Original Message-----
>> > From: olumayokun fowowe [mailto:olumayokun@gmail.com]
>> > Sent: Thursday, September 18, 2008 2:40 PM
>> > To: smorris@internetworkexpert.com
>> > Cc: ccielab@groupstudy.com
>> > Subject: QOS
>> >
>> > Hello guys,
>> > I am a bit confused about QOS. Apart from when I am doing FRTS, if I do
>> > policing on a frame relay interface, how do I differentiate when to
>> apply
>> > the service policy inside a map-class frame-relay from when to apply it
>> > directly to the interface.
>> >
>> > Any help will be greatly appreciated.
>> >
>> > Thanks,
>> >
>> > 'Mayokun
>> >
>> >
>> > Blogs and organic groups at http://www.ccie.net
>> >
>> > _______________________________________________________________________
>> > Subscription information may be found at:
>> > http://www.groupstudy.com/list/CCIELab.html
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>>
>> --
>> Narbik Kocharians
>> CCSI#30832, CCIE# 12410 (R&S, SP, Security)
>> www.MicronicsTraining
>> www.Net-Workbooks.com <http://www.net-workbooks.com/>
>> Sr. Technical Instructor
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>>
>>
>>
>>
>>
>>
>

-- 
Narbik Kocharians
CCSI#30832, CCIE# 12410 (R&S, SP, Security)
www.MicronicsTraining
www.Net-Workbooks.com
Sr. Technical Instructor

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



This archive was generated by hypermail 2.1.4 : Sat Oct 04 2008 - 09:26:18 ART