From: Brian McGahan (brian@cyscoexpert.com)
Date: Thu Jul 10 2003 - 22:19:29 GMT-3
For version specific support of a feature, check the feature
navigator at http://www.cisco.com/go/fn It's usually pretty good at
what it lists, but it's not perfect.
HTH,
Brian McGahan, CCIE #8593
Director of Design and Implementation
brian@cyscoexpert.com
CyscoExpert Corporation
Internetwork Consulting & Training
Toll Free: 866.CyscoXP
Fax: 847.674.2625
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Jeongwoo Park
> Sent: Thursday, July 10, 2003 7:46 PM
> To: 'Brian Dennis'; 'Jim Phillipo'; ccielab@groupstudy.com
> Subject: RE: More QOS CAR example
>
> What version of ios is used here?
> I don't get this.
>
> r7(config)#class
> r7(config)#class-map MC
> r7(config-cmap)#mat
> r7(config-cmap)#match pro ip
> r7(config-cmap)#exi
> r7(config)#po
> r7(config)#policy-map MP
> r7(config-pmap)#cl
> r7(config-pmap)#class MC
> r7(config-pmap-c)#?
> QoS policy-map class configuration commands:
> bandwidth Bandwidth
> default Set a command to its defaults
> exit Exit from QoS class action configuration mode
> no Negate a command or set its defaults
> priority Strict Scheduling Priority for this Class
> queue-limit Queue Max Threshold for Tail Drop
> random-detect Enable Random Early Detection as drop policy
> <cr>
>
> r7#sh version
> Cisco Internetwork Operating System Software
> IOS (tm) 3600 Software (C3620-JS-M), Version 12.1(20), RELEASE
SOFTWARE
> (fc2)
> Copyright (c) 1986-2003 by cisco Systems, Inc.
> Compiled Thu 29-May-03 19:51 by kellythw
> Image text-base: 0x60008940, data-base: 0x6128E000
>
> ROM: System Bootstrap, Version 11.1(19)AA, EARLY DEPLOYMENT RELEASE
> SOFTWARE
> (fc1)
>
> r7 uptime is 3 days, 34 minutes
> System returned to ROM by reload
> System image file is "flash:c3620-js-mz.121-20.bin"
>
> -----Original Message-----
> From: Brian Dennis [mailto:brian@labforge.com]
> Sent: Thursday, July 10, 2003 4:42 PM
> To: 'Jim Phillipo'; ccielab@groupstudy.com
> Subject: RE: More QOS CAR example
>
> Here is the output from 12.1 with just police 384000 configured.
>
> Gateway#sho policy-map interface
> Ethernet0/1
>
> Service-policy output: cisco
>
> Class-map: cisco (match-any)
> 4706 packets, 5757905 bytes
> 5 minute offered rate 148000 bps, drop rate 37000 bps
> Match: any
> police:
> 384000 bps, 12000 limit, 12000 extended limit
> conformed 3885 packets, 4652225 bytes; action: transmit
> exceeded 806 packets, 1104264 bytes; action: drop
> conformed 124000 bps, exceed 38000 bps violate 0 bps
>
> Class-map: class-default (match-any)
> 0 packets, 0 bytes
> 5 minute offered rate 0 bps, drop rate 0 bps
> Match: any
> Gateway#
>
> Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Jim Phillipo
> Sent: Thursday, July 10, 2003 4:16 PM
> To: 'Brian Dennis'; Jim Phillipo; ccielab@groupstudy.com
> Subject: RE: More QOS CAR example
>
> Better:
> Term_Serv#sho policy-map jim
> Policy Map jim
> Class jim
> police cir 80000 bc 2500
> conform-action transmit
> exceed-action drop
>
> Is it normal for the BE not to show up if not configured ?
>
> -----Original Message-----
> From: Brian Dennis [mailto:brian@labforge.com]
> Sent: Thursday, July 10, 2003 7:11 PM
> To: 'Jim Phillipo'; ccielab@groupstudy.com
> Subject: RE: More QOS CAR example
>
>
> Do a "show policy-map interface" to see the defaults.
>
> Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Jim Phillipo
> Sent: Thursday, July 10, 2003 3:43 PM
> To: 'Brian McGahan'; 'Jonathan V Hays'; Jim Phillipo;
> ccielab@groupstudy.com
> Subject: RE: More QOS CAR example
>
> Brian,
>
> When I type in Police 80000 I do not get defaults ?
> !
> policy-map jim
> class jim
> police cir 80000
> !
> !
>
> -----Original Message-----
> From: Brian McGahan [mailto:brian@cyscoexpert.com]
> Sent: Thursday, July 10, 2003 5:27 PM
> To: 'Brian McGahan'; 'Jonathan V Hays'; 'Jim Phillipo';
> ccielab@groupstudy.com
> Subject: RE: More QOS CAR example
>
>
> Group,
>
> As a follow up to my previous post, I did some testing to
> illustrate how the burst values of the CAR statement affect the
> configured rate.
>
> The following output is from a router connected to the internet
> which is policing NNTP traffic (usenet news). I am downloading files
> from alt.binaries.sounds.mp3 (for research purposes only of course),
and
> changing the burst values of the police statement to show the effect.
> The goal of our policing is to keep our NNTP traffic at or below
80kpbs.
>
> In the first example, I entered the 'police 80000' statement.
> This results in the default values of:
>
> Police 80000 2500 2500 conform-action transmit exceed-action drop
>
> http://www.cyscoexpert.com/adminimages/car4.gif
>
> As you can see from the output, I am averaging a rate of about
> 30kbps. This is much lower than the expected target rate.
>
> In the next example, the burst values are modified to meet the
> recommended formula. The 'police 80000 15000 30000' statement was
> entered, which resulted in:
>
> Police 80000 15000 30000 conform-action transmit exceed-action drop
>
> http://www.cyscoexpert.com/adminimages/car3.gif
>
> As you can see from this output, the average rate is in the high
> 70kbps range, which is very close to our desired target rate.
>
> The calculation for CAR values should therefore be as follows:
>
> Normal_burst bytes = target_rate bps * ( 1 byte / 8 bits ) * 1.5
seconds
> Excess_burst bytes = normal_burst * 2
>
>
>
> HTH,
>
> Brian McGahan, CCIE #8593
> Director of Design and Implementation
> brian@cyscoexpert.com
>
> CyscoExpert Corporation
> Internetwork Consulting & Training
> Toll Free: 866.CyscoXP
> Fax: 847.674.2625
>
>
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of
> > Brian McGahan
> > Sent: Thursday, July 10, 2003 2:32 PM
> > To: 'Jonathan V Hays'; 'Jim Phillipo'; ccielab@groupstudy.com
> > Subject: RE: More QOS CAR example
> >
> > Jim & Jonathan,
> >
> > Configuring the burst values to correspond to the formula *IS*
> > necessary. Test it with actual traffic and you will see that the
rate
> > does not correctly conform unless you use the recommended burst
> values.
> > I'm not sure where these authors are getting their burst values
from,
> > but they're not correct.
> >
> > HTH
> >
> > Brian McGahan, CCIE #8593
> > Director of Design and Implementation
> > brian@cyscoexpert.com
> >
> > CyscoExpert Corporation
> > Internetwork Consulting & Training
> > Toll Free: 866.CyscoXP
> > Fax: 847.674.2625
> >
> >
> > > -----Original Message-----
> > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
Behalf
> > Of
> > > Jonathan V Hays
> > > Sent: Wednesday, July 09, 2003 6:37 PM
> > > To: 'Jim Phillipo'; ccielab@groupstudy.com
> > > Subject: RE: More QOS CAR example
> > >
> > > > -----Original Message-----
> > > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
> > > > Behalf Of Jim Phillipo
> > > > Sent: Wednesday, July 09, 2003 6:48 PM
> > > > To: ccielab@groupstudy.com
> > > > Subject: More QOS CAR example
> > > >
> > > >
> > > > This is from VEGESNA's book
> > > >
> > > > All traffic except HTTP over a rate of 15 Mbps is marked with
> > > > IP Prec 4
> > > > HTTP over 15 Mbps is marked with 0
> > > > This is a 30 Mbps pipe from provider
> > > >
> > > > There answer:
> > > >
> > > > rate-limit input 30000000 15000 15000 conform-action continue
> > > > exceed-action-drop
> > > > rate-limit input access-group 101 15000000 10000 10000
> > conform-action
> > > > set-prec-transmit 4 exceed-action set-prec-transmit 0
> > > > rate-limit input 30000000 15000 15000 conform-action
> > > > set-prec-transmit 4
> > > > exceed-action set-prec-transmit 4
> > > >
> > > > access-list 101 permit tcp any any eq www
> > > > access-list 101 permit tcp any eq www any <This is for web
> > > > traffic leaving
> > > > the site correct ?>
> > > >
> > > > How do they arrive at 15000 and 10000 respectively ?
> > >
> > > [snip]
> > >
> > > Good observation.
> > >
> > >
> >
>
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/
> > > fqos_c/fqcprt4/qcfpolsh.htm#1000977
> > >
> > > The above reference on the Doc CD gives the CAR formula as:
> > > <quote>
> > > Recommended Burst Values
> > > Cisco recommends the following values for the normal and extended
> > burst
> > > parameters:
> > >
> > > normal burst = configured rate * (1 byte)/(8 bits) * 1.5 seconds
> > > extended burst = 2 * normal burst
> > > </quote>
> > >
> > > Here are the calculations (commas added for readability - my
> apologies
> > > to Europeans and others who don't use commas to break up the
> thousands
> > > ;-)
> > >
> > > configured rate = 30,000,000 bps
> > > normal burst = 30000000/8 * 1.5 = 5,625,000 bytes
> > > extended burst = 2 * 5625000 = 11,250,000 bytes
> > >
> > > configured rate = 10,000,000 bps
> > > normal burst = 10000000/8 * 1.5 = 1,875,000 bytes
> > > extended burst = 2 * 1875000 = 3,750,000 bytes
> > >
> > > Vegesna is obviously *not* using this formula. Maybe there is a
> > > saturation point or ceiling for burst size? (This is no more than
a
> > > SWAG.)
> > >
> > > Perhaps the "experts" will chime in ...
> > >
> > > Jonathan
> > >
> > >
> > >
> >
>
This archive was generated by hypermail 2.1.4 : Wed Aug 06 2003 - 06:52:35 GMT-3
