[c-nsp] 7600 Rate Limiting Output

[Kevin Warwashana]

I was able to use the below configuration and it appears to max out the
connection pretty close to 26mb.  I did have to tinker with the queue size
since the default (3300+) would allow traffic to exceed and a size of 5
didn't seem to work very well.

policy-map 26MB-OUTPUT
  class class-default
    shape average 26000000
    queue-limit 100 packets
    bandwidth 26000

You mentioned "configure a shaper at class-default, with an attached
service-policy" which I believe would be adding a service policy to the
policy map, but got:

policy-map 26MB-RATE
  class class-default
    police cir 26000000 conform-action transmit exceed-action drop
policy-map 26MB-OUTPUT
  class class-default
    shape average 26000000
    queue-limit 100 packets
    bandwidth 26000
    service-policy 26MB-RATE 
Only 'shape' and 'bandwidth remaining ratio' actions are supported in parent
classes for this interface.
Only 'shape' and 'bandwidth remaining ratio' actions are supported in parent
classes for this interface.
Only 'shape' and 'bandwidth remaining ratio' actions are supported in parent
classes for this interface.
    
Please let me know if I misunderstand your statement.  Greatly appreciate
the follow up emails.

Thanks,
Kevin


-----Original Message-----
From: Rob Shakir [mailto:rjs at eng.gxn.net] 
Sent: Saturday, January 30, 2010 5:19 PM
To: Kevin Warwashana
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] 7600 Rate Limiting Output


On 24 Jan 2010, at 03:46, Kevin Warwashana wrote:
> 
> int gig4/0/0.8
> 
> service-policy output 26MB-OUTPUT    
> 
> Police and strict priority must be configured together for egress QOS.
> 
> Invalid feature combination for the class class-default
> 
> Configuration failed

This looks like what you see on ES-20 when trying a similar configuration.
It implies that one must configure an LLQ to be able to police. Therefore to
achieve this, you can do:

policy-map POLICY-POLICE-26MBPS-OUT
 class class-default
  police cir 26000000 conform-action transmit exceed-action drop
  ! forced to be an llq
  priority
 !
!

However, interestingly, the configuration that you supplied appears to be
configurable on SIP-400 w/ SPA-2x1GE:

7600#sh policy-map RJS-TEST

  Policy Map RJS-TEST
    Class class-default
     police rate 26000000 bps
       conform-action transmit
       exceed-action drop

7600#sh run int giga1/0/0.4011
Building configuration...

Current configuration : 239 bytes
!
interface GigabitEthernet1/0/0.4011
 encapsulation dot1Q 4011
 ip address 192.168.88.42 255.255.255.0
 ip vrf forwarding RJS-TEST
 service-policy input POLICY-SET-IP-DSCP-DEFAULT
 service-policy output RJS-TEST
end

This may be due to the fact that the datasheet for SIP-400 [0] says that it
supports "egress queueing", whereas SIP-600 [1] states only "egress
shaping". If you don't have inter-op requirements, can you configure it as a
shaper with a very short queue length, so that you start to emulate
policing?

Alternatively, it might be worth checking whether you can configure a shaper
at class-default, with an attached service-policy that can then police under
this.

Hope this helps!

Kind regards,
Rob

[0]:
http://www.cisco.com/en/US/prod/collateral/routers/ps368/product_data_sheet0
900aecd8027c9e6.html
[1]:
http://www.cisco.com/en/US/prod/collateral/routers/ps368/product_data_sheet0
900aecd8033998f_ps708_Products_Data_Sheet.html


-- 
Rob Shakir                      <rjs at eng.gxn.net>
Network Development Engineer    GX Networks/Vialtus Solutions
ddi: +44208 587 6077            mob: +44797 155 4098
pgp: 0xc07e6deb                 nic-hdl: RJS-RIPE

This email is subject to: http://www.vialtus.com/disclaimer.html