[c-nsp] output rate-limiting not working in 7609

[Jimmy]

Hi guys,

Thanks for the feedback. Actually I have tried using MQC on the egress side.
It is Layer 3 port.
The port is in slot 1. For some reason when I do "show policy-map
interface", it is showing an output from 2 slots instead of 1. I am using a
dirty trick to temporarily solve the issue. I did policing to 155M instead
of 310M. With this setting, the traffic can only reach 310M.

Any idea why we need to configure like that? Or anyone has encountered the
same issue?

Cheers,
Jimmy

-------------------------------
interface GigabitEthernet1/9
 ip route-cache flow
 load-interval 30
 speed nonegotiate
 mls netflow sampling
 service-policy input CUSTOMER-310m
 service-policy output CUSTOMER-155M

policy-map CUSTOMER-155M
  class class-default
   police cir 155000000 bc 15500000 be 15500000 conform-action transmit
exceed-action drop ----> POLICE to 155M

gw1.hkg4#sh policy int g1/9
 GigabitEthernet1/9

  Service-policy output: CUSTOMER-155M

    class-map: class-default (match-any)
      Match: any
      police :
        155000000 bps 15500000 limit 15500000 extended limit
      Earl in slot 1 :
        16889514278576 bytes
        30 second offered rate 196550600 bps
        aggregate-forwarded 13191791357655 bytes action: transmit
        exceeded 3697722920921 bytes action: drop
        aggregate-forward 157101144 bps exceed 40026752 bps
      Earl in slot 2 : ----------------------------> ANOTHER POLICING ???
        14639062953589 bytes
        30 second offered rate 174721136 bps
        aggregate-forwarded 13135487245073 bytes action: transmit
        exceeded 1503575708516 bytes action: drop
        aggregate-forward 159830912 bps exceed 18063232 bps
      Earl in slot 5 :
        30560015 bytes
        30 second offered rate 176 bps
        aggregate-forwarded 30560015 bytes action: transmit
        exceeded 0 bytes action: drop
        aggregate-forward 240 bps exceed 0 bps

gw1.hkg4#sh mls qos ip g 1/9
   [In] Policy map is CUSTOMER-310m   [Out] Policy map is CUSTOMER-155M
 QoS Summary [IPv4]:      (* - shared aggregates, Mod - switch module)

      Int Mod Dir  Class-map DSCP  Agg  Trust Fl   AgForward-By
AgPoliced-By
                                   Id         Id
----------------------------------------------------------------------------
---
     Gi1/9  1  In class-defa    0    1   dscp  0   486690994913
54268431391
     Gi1/9  1 Out class-defa    0    2     --  0   548444567177
399451084094
     Gi1/9  2 Out class-defa    0    1     --  0   492136489401
404181645273 ----> SHOULDN'T HAVE ANY OUTPUT
     Gi1/9  5 Out class-defa    0    1     --  0       30561099
0
-----------------------------------------------

-----Original Message-----
From: Pete Templin [mailto:petelists at templin.org] 
Sent: Tuesday, March 04, 2008 12:26 AM
To: Jimmy
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] output rate-limiting not working in 7609

Jimmy wrote:

> I have encountered rate-limiting issue on CISCO7609 platform.
>  
> Example is:
>  
> interface GigabitEthernet1/9
>  rate-limit input 310000000 4843750 9687500 conform-action transmit 
> exceed-action drop  rate-limit output 310000000 4843750 9687500 
> conform-action transmit exceed-action drop  -------> NOT WORKING
>  
> The output rate-limiting is not working. The traffic still can go 
> above 310M and can hit 1G.
> I have created SR with cisco. They are saying there is no work around 
> for this except that we use ES20 to use policy-map on the interface.

Your example is too short - is it a layer 3 port?  If so, a policer inside a
policy-map should work.  If not, it won't work.  From the Sup720 datasheet:
rate limiting is possible on "Ingress port or VLAN and egress VLAN or
Layer-3 port".

pt