Rate Limit Traffic on Router

Is it possible to limit bandwidth between two IPs using ACL or policy map. Like for example i want to limit 50% file sharing traffic coming or going to an IP 172.19.60.50

Hello,
You can rate limit the traffic using Traffic Policing or traffic shapping and YES you can match based on the flow of the traffic
Looking for some Networking Assistance? 
Contact me directly at [email protected]
I will fix your problem ASAP.
Cheers,
Julio Carvajal Segura
http://laguiadelnetworking.com

Similar Messages

  • WLC 5508 and Anchor/GuestNet rate limit traffic?

    Running WLCs 5508s 7.0.116.0 with GuestNet and Anchor setup, how can I limit the bandwidth on the GuestNet SSDI to 2 Mbps, etc?
    The DMZ WLC (Anchor) runs thru a ASA 5508 7x, can I rate limit traffic via ASA?

    That's really a matter of preference.  This document describes things to keep in mind when altering these QoS profile configurations, FYI.
    http://www.cisco.com/en/US/partner/docs/wireless/controller/7.0MR1/configuration/guide/cg_controller_setting.html#wp1254532
    It really depends on how many guests, what type of traffic, etc, to make a judgement call as to where you should set these.  I'm sorry but I don't have any examples from existing configurations, but hopefully the document explains how to best alter these settings.

  • Limit traffic on router interface

    Dear all,
    how can i limit Upload/download bandwith on router interface.
    please help me
    thanks with regards
    vikas kumar

    HI,
    You can police the traffic in ingress/egress but the support may depend of your hardware. Please refer to the following link for more information:
    http://www.cisco.com/en/US/partner/docs/ios/qos/configuration/guide/polcing_shping_oview_ps6350_TSD_Products_Configuration_Guide_Chapter.html
    HTH
    Laurent.

  • Bandwidth Rate-Limit -w- WWR-Queue

    How would one convert a layer-2 port's "switchport rate-limit" bandwidth statement, on a 6509 -w- WS-X6748-SFP ports, to a routed/layer-3 "wrr-queue" bandwidth statement policy? Basically trying to hard-core the port's speed to 20MB.  Current/tested layer-2 port bandwidth setting:
    rate-limit input 20000000 5000 5000 conform-action transmit exceed-action drop
    rate-limit output 20000000 5000 5000 conform-action transmit exceed-action drop
    Got lost in how to use/configure all WRR's four queues... just need to limit the port's bandwidth to 20MB.  Any suggestions would be appreciated.
    Thanks, Kevin

    1) Enabled QoS globally...
    2960(config)#mls qos
    2) Configure an ACL to define the matched traffic...
    2960(config)#access-list 111 permit ip any any
    3) Configure a class map for the matched traffic...
    2960(config)#class-map traffic
    2960(config-cmap)#match access 111
    4) Configure a policy-map to define action...
    2960(config)#policy-map Control
    2960(config-pmap)#class traffic
    2960(config-pmap-c)#police 10000000 8000 exceed-action drop
    5) Attached the policy-map to the interface.
    a) Example
    -In this case, I'll attach the policy map to port_1....
    2960(config)#int fa0/1
    2960(config-if)#service-policy input Control
    >>>>>> This will rate-limit traffic coming from the PC

  • Rate-limit command 3560 does it exist?

    I have just come across a command in my router IOS which might be useful too me. I was wondering if the following command is available on a 3560 Switch. I don't see it on my 3550 but the IOS is quite old. I don't have a 3560 avaiable currently to check.
    Config t > int vlan x > rate-limit input/output
    does this exist on the 3560? I am also interest if it does in the Bits per second range and if available input/output.
    Thanks for any help

    Hello,
    what kind of feature are you looking for?
    CAR?
    http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_command_reference_chapter09186a0080087f26.html#wp1037428
    For command list check the following link:
    Catalyst 3560 Switch Command Reference, Rel. 12.2(25)SEE
    http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3560/12225see/cr/index.htm
    For QOS configs:
    http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3560/12225see/scg/swqos.htm
    If you need to rate limit traffic on an interface check:
    Limiting the Bandwidth on an Egress Interface
    http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3560/12225see/scg/swqos.htm#wp1253412
    Hope this help a bit,
    if it does, please rate this post.
    Vlad

  • Rate-limit for some MAC on aironet 1231

    Hello!
    I need to set rate-limit for some mac addresses on access point aironet 1231.Is it possible?
    If no, what ios or devices can do it?
    Thanks.

    No there is no option for rate-limit in Aironet but in controller, Rate-limiting is applicable to all traffic destined to the CPU from either direction (wireless or wired). Cisco recommends that you always run the controller with the default config advanced rate enable command in effect in order to rate-limit traffic to the controller and protect against denial-of-service (DoS) attacks. You can use the config advanced rate disable command to stop rate-limiting of Internet Control Message Protocol (ICMP) echo responses for testing purposes.

  • Upstream traffic rate limit

    Hi all,
    Upstream traffic rate limit is not supported by WLC . It will be done by AP.
    We have setup of Auto anchor for both corporate and guest(but authentication mechanism is diffrent) . They wont access any internal resouce .Only interner traffic is permitted.
    So can we limit the internet traffic for guest users .? If we limiting the upstream traffic at the AP level what would be the concerns we may face?
    Kindly help on this.
    Thanks,
    Regards,
    Vijay

    Hello Vijay,
    As per your query i can suggest you the following solution-
    Please refer table 1 of the given link-
    http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bd3900.shtml
    Hope this will help you.

  • Can CAR on router rate-limit per address?

    Hi, everyone
    I have a question about CAR on router. The router have a G703 E1 WAn interface and an ethernet interface. My goal is to rate-limiting access-rate of every ip address under ethernet, that is, for example, every PC under the ethernet interface cannot over 1Mb/s.
    Can CAR on the router achieve this goal? If be, how to achieve it?
    Very Thanks.
    Tao

    Farrukh
    Very thanks for your reply.
    My purpose is to put a maximum access-rate limit for every PC in a LAN. So if there are 100 PCs in the LAN, with the above CAR, I have to make 100 ACL, as below:
    access-list 101 permit ip host 192.168.1.1 any
    access-list 102 permit ip host 192.168.1.2 any
    If so, there will be too many acl items. And I don't know how many acl can we applied under FastEthernet0/0. So it maybe unreasonable.
    I know Huawei's Quidway router can support this feature, as below:
    qos carl 1 source-ip-address range 192.168.0.2 to 192.168.0.200 per-address
    I want to know Cisco can support this feature, or have some methods to achieve it.
    Very Thanks
    Tao

  • How to rate-limit different IP's entering/leaving an Interface?

    Hi There,
    We are an ISP and have an interconnect with say Provider A. Customers of ours use Provider A for layer 2 and us for Layer 3 (IP/Internet).
    Customer #1 to #100 --- (10Mb) --> Provider A ---> ISP ---> Internet
    We'd like to rate limit some customers to 2mb/sec (in/out) on our end because at present they have a 10mb/sec connection coming from Provider A.
    The config we use to peer with Provider A is this:
    interface GigabitEthernet0/1.120
    description Interconnect with Provider A
    bandwidth 400000
    encapsulation dot1Q 120
    ip address A.B.C.1 255.255.255.252
    Customers of ours are simply routed out through this interface like so:
    Customer #1:
    ip route W.X.Y.Z. 255.255.255.255 A.B.C.2
    Customer #2:
    ip route J.K.L.M 255.255.255.255 A.B.C.2
    Is there a way to rate limit both these customers without needing to create a separate class map for each like so:
    class-map match-all CUSTOMER-1-2MB
    match access-group name ACL-CUSTOMER-1
    class-map match-all CUSTOMER-2-2MB
    match access-group name ACL-CUSTOMER-2
    policy-map POLICY-RATE-LIMIT
    class CUSTOMER-1-2MB
    police 2000000 375000 750000
    class CUSTOMER-2-2MB
    police 2000000 375000 750000
    interface GigabitEthernet0/1.120
    service-policy input POLICY-RATE-LIMIT
    service-policy output POLICY-RATE-LIMIT
    I've done this in the lab and I know it works, so Customer #1 ends up with 2mb/sec and Customer #2 gets 2mb/sec too.
    But in production, I'm talking about 100's of customers which we simply route out of this interface. I can't imagine having to configure 100's of class maps and policy maps for each customer to rate limit them to 2mb/sec like in the config above.
    Is there a better way to do this on the router???
    Thanks.
    Andy

    Hi All,
    Doing what Laurent suggested works great. We are able to rate-limit the desired customers by having a separate class-map for each customer that needs to be rate limited under the single policy-map.
    But now we're finding that the CPU utilization has increased by 20% because of this.
    We're pushing about 400M through this interface and rate limiting 7 customers on it.
    Given the large traffic flow through this interface (400M), is it common to see an increase in CPU utilisation by 20%???
    When we take the service-policy off the interface, sure enough the CPU drops by 20%.
    Here's the MQC applied:
    interface GigabitEthernet0/1.120
    bandwidth 400000
    encapsulation dot1Q 120
    ip address 203.17.x.x 255.255.255.252
    ip flow ingress
    service-policy input RATE-LIMIT
    service-policy output RATE-LIMIT
    class-map match-all CLASS-TCS-200338
    description Customer #1 rate limited to 4mb/sec
    match access-group name ACL-TCS-200338
    class-map match-all CLASS-TCS-200208
    description Customer #2 rate limited to 2mb/sec
    match access-group name ACL-TCS-200208
    class-map match-all CLASS-TCS-205593
    description Customer #3 rate limited to 3mb/sec
    match access-group name ACL-TCS-205593
    class-map match-all CLASS-TCS-205679
    description Customer #4 rate limited to 4mb/sec
    match access-group name ACL-TCS-205679
    class-map match-all CLASS-TCS-200441
    description Customer #5 rate limited to 4mb/sec
    match access-group name ACL-TCS-200441
    class-map match-all CLASS-TCS-200005
    description Customer #6 rate limited to 2mb/sec
    match access-group name ACL-TCS-200005
    class-map match-all CLASS-TCS-205560
    description Customer #7 rate limited to 4mb/sec
    match access-group name ACL-TCS-205560
    policy-map RATE-LIMIT
    class CLASS-TCS-200005
    police 2000000 375000 750000 conform-action transmit exceed-action transmit violate-action drop
    class CLASS-TCS-200208
    police 2000000 375000 750000 conform-action transmit exceed-action transmit violate-action drop
    class CLASS-TCS-200441
    police 4000000 750000 1500000 conform-action transmit exceed-action transmit violate-action drop
    class CLASS-TCS-200338
    police 4000000 750000 1500000 conform-action transmit exceed-action transmit violate-action drop
    class CLASS-TCS-205679
    police 4000000 750000 1500000 conform-action transmit exceed-action transmit violate-action drop
    class CLASS-TCS-205560
    police 4000000 750000 1500000 conform-action transmit exceed-action transmit violate-action drop
    class CLASS-TCS-205593
    police 3000000 562500 1125000 conform-action transmit exceed-action transmit violate-action drop
    Is this the correct behaviour of applying the service-policy to the interface whereby the CPU increases by 20% or can the MQC be fine tuned to have less of an impact on the CPU?
    Is the router just overloaded, taking into account it's only pushing about 400M? Should it be able to do more than this??
    Thanks.
    Andy

  • WLC user rate limit on guest ssid anchor controller

    Hi,
    I have been looking through the forums & some cisco documents but not found a good example similar to what I am seeking to do so now I am turning to the expertise of my peers.
    We have been deploying 3502 APs remotely to locations with full T1s that backhaul to where I sit at HQ.
    Both the foreign and anchor controller are here at my location.
    I am seeking to rate limit per user the bandwidth each client will get on the guest internet ssid.
    As you know this traffic is encapsulated in capwap between the AP and the controller so I cant use a standard ACL on the switch or router.
    We are trying to keep the guest internet access usage in check on the T1 at any given site so the other ssid's & local lan traffic is not overly competing for the bandwidth.
    I found the place to edit the default profiles in the controller but the documentation really isnt clear on best practices.
    So I put it to you my fellow wireless engineers to suggest how you are implementing bandwidth management on your wireless guest internet.
    Thanks guys!           
    Oh and here is my hardware & software levels.
    5508wlc - forgeign
    4402wlc - anchor
    Software Version
    7.0.230.0

    Amjad,
    Thank you for taking the time to respond as well as the document link.
    It was pretty clear on the steps and what it would impact.
    Two things that push me for a different solution (assuming their is one).
    Note The values that you configure for the per-user bandwidth contracts affect only the amount of bandwidth going downstream (from the access point to the wireless client). They do not affect the bandwidth for upstream traffic (from the client to the access point).
    As you can see from the above note taken out of the linked document the roll based rate limit doesnt really rate limit the T1 traffic any guest user consumes it only limits usage from the AP down to the client.
    #1 I am looking for a solution that limits the users up & down streams (if possible) & also before it leaves the AP for the T1.
    The idea is to limit WAN utilization.
    #2 I read in the forums here others asking about the "user role" and saw some comments saying it is not considered "best practice" to use user roles.
    Let me clarify that our guest ssid's are using the http webpage pass through for authentication and it is really only the tic mark to indicate they understand the terms and conditions of using our internet as a guest service. No actual user accounts are used on the guest ssid's.
    ***One last question about this and any other changes***
    Will any change I make be on the "Foreign, Anchor" or both Controllers?

  • Wireless rate limit

    Hi,
    My network infrastructure as simple as following:
    LAN(edge switches 3560).......>Aggregator switch(3750)........>Firewall(ASA 5510)........>Router.......>Internet
    I define 3 wireless VLANs with 3 SSIDs on the Aggregator switch(3750):
    1. one SSID for company employees.
    2. one SSID for wireless IP phones.
    3. one SSID for company guest which access only internet.
    And the wireless APs connected to the LAN(edge switches) direct with trunks.
    My question is how to apply a rate limit for SSID for company guest to access internet with B.W. of 128kbps only.
    I tried policy map to be applied on the aggregator switch(3750) on the VLAN interface, but, it is not working.
    So, any suggested help, please.

    Hi Ahmed:
    With autonomous APs, rate limiting isn't possible.  All the autonomous APs support is QoS and that's pretty iffy.  At the core of the issue, you're dealing with radio waves and which ones arrive at the radio first, and who was prevented from talking because someone else was talking.  Dealing with these QoS and traffic shaping/policing issues are really tough with wireless because the transmission medium itself is unreliable.
    The "Configuring QoS" chapter of the autonomous AP configuration guide
      http://tools.cisco.com/squish/5aCf1
    will show you how you can map priority tagging to an SSID so that in that path from radio receiver to outbound on the fastethernet interface toward the rest of the network, you can control which SSID's packets get up into the network first, but the reverse path is a different story.  Because the wireless medium is half-duplex acknowledged, you can have a high priority packet out there on the radio interface trying to be beamed out to the client, and if the client isn't sending their ACK or what have you, it's going to sit and retry until its 63 retries are done before it gets out of the way to let the next high priority packet have a turn at getting transmitted out.
    Once the traffic gets past the edge switch, the fact that it was at one time wireless is irrelevant.  You should look at it as a general "rate limiting one VLAN's traffic over another" and check with the routing protocols or traffic shaping folks.
    Sincerely,
    Rollin Kibbe
    Network Management Systems Team

  • Rate-limit Burst explanation

    Hi All - I need your help to understand the Burst value in the Rate-Limit
    Example: rate-limit input access-group 101 20000000 24000 32000
    I understand the above configuration limit the traffic to 20Mbps. How to calculate the Burst-Normal (as per example above 24000 Bytes) and Burst-Max(as per above example 32000 Bytes). What is the logic for arriving the Burst-Normal & Burst-Max?
    Thanks in advance
    SAIRAM

    Hi Sairam,
    below are definitions of few terms which are involved here
    CIR : committed information rate, in bits per second, defines the rate defined in the traffic contract.
    Tc : Time interval,measured in miliseconds, over which the committed burst (Bc) can be sent.
    Bc : Committed burst size,measured in bits. This is the amount of traffic that can be sent over the interval Tc.
    Be : Excess burst size, in bits. This is number of bits beyond Bc that can sent after a period of inactivity.
    Formula to calculate Bc is 
    Bc = CIR*Tc
    Now to understand Bc and Tc, say suppose you have applied 20mbps rate-limit on a 100mbps fastethernet link. Now link can send data (bits) with clock-rate only which is 100mbps so to achieve 20mbps rate on that link router needs to send traffic for 1/5th of a sec and remain idle for 4/5th of a second. 1/5th of sec is 200 msec. If router will send traffic for 200msec and not sending traffic for next 800msec, it can achieve rate of 20mbps but a packet arrived at 199th sec will need to wait for 800msec and this will add unnecessary latency to the packet. To avoid this, router sends few bits for short duration and then does not send for some duration. For the period it sends traffic is called Tc value. and the number of bytes it can send during that interval is called Bc  value. So CIR = Bc/Tc (bits per interval).
    Now we dont have option to configure Tc but we can configure CIR and Bc, and Tc will automatically be calculated. If we do not configure Bc then router takes default Tc of 125ms and calculates the Bc. 
    What value to choose for Bc
    If we configure Bc too large then Tc will go high for same CIR and this may cause delay or jitter for delay sensitive traffic. For delay sensitive traffic cisco recommends to have Tc 10ms or less.
    If i calculate Tc in the given example, it is coming as 9.6ms which is close to 10ms that is why Bc is set as 24000.
    Tc = Bc/CIR
       = 24000(bytes)/20000000(bits/sec)
       = 192000(bits)/20000(bits/ms)
       = 192/20
       = 9.6 msec
    Now Be is to give extra bandwidth for small interval(Tc) to cater some bursty traffic. Assume there is a bucket which gets filled with Bc amount of token in every Tc interval and router can send traffic if there is sufficient  amount of token available in the bucket, equal to the packet size. After forwarding packet router reduces same amount of token from the bucket. Size of bucket is also equal to Bc which means if there is no traffic for Tc interval, bucket can not hold more token. Be is to increase the size of bucket to (Bc + Be). Now in every Tc interval bucket will be filled with Bc token and if there is a period of inactivity then in next interval bucket can be filled with extra Bc amount of token till it reaches to (Bc + Be) and if there is any bursty traffic (more than Bc) same can be adjusted. So for a very small period router may send traffic with more rate (higher than CIR, since sending Bc+Be in Tc interval) but over a period does not cross CIR.
    You can also use below "Ask the expert" event for QoS to further queries related to QoS.
    https://supportforums.cisco.com/discussion/12259571/ask-expert-quality-service-qos-cisco-ios-routers
    Please dont forget to rate post if it has been helpful.
    Regards,
    Akash

  • Rate-limit command brief explanation

    Hi,
    There is this rate-limit command in our company's router.
    rate-limit input access-group 127 1000000 187500 187500 conform-action transmit exceed-action drop
    I know that the access-group part refers to an access list
    conform action transmit means that packets will be transmitted
    exceed-action drop means that if it exceed the values listed packets will be dropped.
    What i dont understand is the logic behind the numbers 1000000 187500 187500. It would be very helpful if someone could explain it briefly, i am having a hard time understanding the cisco docs regarding this command.
    thanks.

    Hi @seaweeds24,
    Those numbers are "average rate" "normal burts size" "excess burst size", respectively.
    Average rate determines the long-term average transmission rate. Traffic that falls into this rate will always conform
    Normal burst size determines how large traffic bursts can be before some traffic exceeds the rate limit
    Excess burst size determines how larget traffic bursts can be before ALL traffic exceeds the rate limit. 
    Traffic that falls between the Normal Burst size and the Exces Burst size exceeds the rate limit with a probability that increases as the burst size increases.
    HTH.
    Rgrds,
    Martin, IT Specialist

  • Prevalence between service policy and rate limit

    Hi,
    I have a question, on the wan interface on my router I have configured two QoS configuration: one is based on rate-limit pointing to a an specified traffic but also I have a configuration with a service policy that include the same traffic with a restriction of bandwidth . I do not know what policy has prevalence if the service policy or the rate limit.
    Regards.

    Hi Rajan ,
    Thanks for teh reply.
    I'm but confused with your answer....
    We have SRM 5 implemented at our place and I see that service carts  created in the system using the link "ORDER" when converted to PO's in Sourcing create Purchase orders with HIERARCHY structure i.e. 1 header and 1 item(with the actual service line) but when they are replicated to ECC,we have done an enheancement to create LIMIT PO's for service orders.
    Hence I wanted to know when do we need to create SERVICE HIRERACHY based PO's in SRM and when we need to create LIMIT PO's directly in SRM?
    Also I understand that in SRM,for limit PO's,when the PO item is deleted in PROCESS PO trasnctions,the items are not returned back to sourcing.We dont want this to happen for all types of PO's(both material and Service).We want that when a PO item is deleted,the item should return back to sourcing.
    But other then above functionality,what are the advantages of creating SERVICE based HIERARHCY PO's v/s LIMIT PO's in SRM?
    Please advise.
    Any inputs from Experts on this forum will be appreciated.
    Thanks in advance.

  • 3750X rate-limit (QoS)

    Hello,
    I'm trying to configure a rate-limit in a 3750X but I'm not seeing any result... 
    These are my configurations:
    RF#show run 
    Building configuration...
    Current configuration : 23410 bytes
    ! Last configuration change at 08:53:35 UTC Sun Mar 14 1993
    version 15.0
    no service pad
    service timestamps debug datetime msec
    service timestamps log datetime msec
    no service password-encryption
    hostname RF
    boot-start-marker
    boot-end-marker
    no aaa new-model
    switch 1 provision ws-c3750x-48p
    system mtu routing 1500
    ip routing
    ip domain-name erf.carco.com.mx
    rep admin vlan 100
    mls qos
    spanning-tree mode pvst
    spanning-tree extend system-id
    vlan internal allocation policy ascending
    vlan 2
    vlan 4 
    vlan 6
    vlan 8
    vlan 10
    vlan 20
    vlan 21   
    vlan 22
    vlan 23
    vlan 25 
    vlan 26
    vlan 30
    vlan 50
    vlan 53
    vlan 70
    vlan 81
    vlan 91
    vlan 92
    vlan 93
    vlan 95
    vlan 96
    vlan 99
    vlan 100
    vlan 102
    vlan 110
    vlan 122
    vlan 129
    vlan 200
    vlan 213
    vlan 227
    vlan 333
    vlan 357
    vlan 417
    vlan 444
    vlan 500
    vlan 502
    vlan 555
    vlan 700
    vlan 712
    vlan 910
    vlan 911
    vlan 951
    vlan 1105
    vlan 1508
    vlan 1830
    vlan 1870
    vlan 1890
    vlan 1891
    vlan 1892
    class-map match-any test
      match access-group 100
    policy-map test
     class test
      police 150000000 512000 exceed-action drop
    interface Loopback0
     ip address 10.20.40.106 255.255.255.0
    interface Port-channel22
     switchport trunk encapsulation dot1q
     switchport trunk native vlan 100
     switchport mode trunk
     bandwidth 10000000
     rep segment 10
    interface Port-channel24
     switchport trunk encapsulation dot1q
     switchport trunk native vlan 100
     switchport mode trunk
     bandwidth 10000000
     rep segment 10
    interface FastEthernet0
     no ip address
     no ip route-cache
     shutdown
    interface GigabitEthernet1/0/1
    interface GigabitEthernet1/0/2
    interface GigabitEthernet1/0/3
     switchport trunk encapsulation dot1q
     switchport trunk native vlan 100
     switchport trunk allowed vlan 2,10,50,53,60,70,91-93,95,96,99,100,110,213,227
     switchport trunk allowed vlan add 500,700,910,911,951,1830,1870,1890-1892
     switchport mode trunk
     no logging event link-status
     shutdown
     speed 1000
     duplex full
    interface GigabitEthernet1/0/4
     switchport trunk encapsulation dot1q
     switchport trunk native vlan 100
     switchport trunk allowed vlan 2,8,10,20,50,53,70,91-93,95,96,99,100,110,213
     switchport trunk allowed vlan add 227,500,700,910,911,951,1830,1870,1890-1892
     switchport mode trunk
     shutdown
     speed 1000
     duplex full
    interface GigabitEthernet1/0/5
    interface GigabitEthernet1/0/6
    interface GigabitEthernet1/0/7
    interface GigabitEthernet1/0/8
    interface GigabitEthernet1/0/9
    interface GigabitEthernet1/0/10
     switchport access vlan 91
     switchport mode access
     logging event link-status
    interface GigabitEthernet1/0/11
    interface GigabitEthernet1/0/12
    interface GigabitEthernet1/0/13
    interface GigabitEthernet1/0/14
    interface GigabitEthernet1/0/15
     switchport access vlan 91
     switchport mode access
     logging event link-status
    interface GigabitEthernet1/0/16
    interface GigabitEthernet1/0/17
    interface GigabitEthernet1/0/18
    interface GigabitEthernet1/0/19
    interface GigabitEthernet1/0/20
     switchport access vlan 91
     switchport mode access
     logging event link-status
    interface GigabitEthernet1/0/21
    interface GigabitEthernet1/0/22
    interface GigabitEthernet1/0/23
    interface GigabitEthernet1/0/24
    interface GigabitEthernet1/0/25
     switchport access vlan 910
     switchport mode access
    interface GigabitEthernet1/0/26
    interface GigabitEthernet1/0/27
    interface GigabitEthernet1/0/28
    interface GigabitEthernet1/0/29
    interface GigabitEthernet1/0/30
    interface GigabitEthernet1/0/31
    interface GigabitEthernet1/0/32
    interface GigabitEthernet1/0/33
    interface GigabitEthernet1/0/34
    interface GigabitEthernet1/0/35
    interface GigabitEthernet1/0/36
    interface GigabitEthernet1/0/37
     no switchport
     bandwidth 150000
     ip address 10.20.103.13 255.255.255.252
     rate-limit output access-group 100 24000000 3000000 3000000 conform-action transmit exceed-action drop
     logging event link-status
    interface GigabitEthernet1/0/38
    interface GigabitEthernet1/0/39
    interface GigabitEthernet1/0/40
    interface GigabitEthernet1/0/41
    interface GigabitEthernet1/0/42
    interface GigabitEthernet1/0/43
     switchport trunk encapsulation dot1q
     switchport trunk native vlan 100
     switchport mode trunk
     bandwidth 10000000
     channel-group 24 mode on
    interface GigabitEthernet1/0/44
    interface GigabitEthernet1/0/45
     switchport trunk encapsulation dot1q
     switchport trunk native vlan 100
     switchport trunk allowed vlan 2,10,50,53,60,70,91-93,95,96,99,100,110,213,227
     switchport trunk allowed vlan add 500,700,910,911,951,1830,1870,1890-1892
     switchport mode trunk
     shutdown
    interface GigabitEthernet1/0/46
     switchport trunk encapsulation dot1q
     switchport trunk native vlan 100
     switchport trunk allowed vlan 2,10,50,53,60,70,91-93,95,96,99,100,110,213,227
     switchport trunk allowed vlan add 500,700,910,911,951,1830,1870,1890-1892
     switchport mode trunk
     shutdown
    interface GigabitEthernet1/0/47
     switchport trunk encapsulation dot1q
     switchport trunk native vlan 100
     switchport mode trunk
     bandwidth 10000000
     channel-group 22 mode on
    interface GigabitEthernet1/0/48
     switchport trunk encapsulation dot1q
     switchport trunk native vlan 6
     switchport trunk allowed vlan 2,7,10,20,50,53,70,91-93,95,96,99,100,110,213
     switchport trunk allowed vlan add 227,700,910,911,951,1830,1870,1890-1892
     switchport mode trunk
     logging event link-status
     shutdown
    interface GigabitEthernet1/1/1
     switchport trunk encapsulation dot1q
     switchport trunk native vlan 100
     switchport trunk allowed vlan 2,8,10,20,50,53,60,70,91-93,95,96,99,110,213,227
     switchport trunk allowed vlan add 500,700,910,911,951,1830,1870,1890-1892
     switchport mode trunk
     shutdown
    interface GigabitEthernet1/1/2
     switchport trunk encapsulation dot1q
     switchport trunk native vlan 100
     switchport trunk allowed vlan 2,8,10,20,50,53,60,70,91-93,95,96,99,110,213,227
     switchport trunk allowed vlan add 500,700,910,911,951,1830,1870,1890-1892
     switchport mode trunk
     shutdown
    interface GigabitEthernet1/1/3
     switchport trunk encapsulation dot1q
     switchport trunk native vlan 6
     switchport trunk allowed vlan 2,6,8,10,20,50,53,70,91-93,95,96,99,100,110,213
     switchport trunk allowed vlan add 227,700,910,911,951,1830,1870,1890-1892
     logging event link-status
     shutdown
    interface GigabitEthernet1/1/4
     switchport trunk encapsulation dot1q
     switchport trunk native vlan 6
     switchport trunk allowed vlan 2,6,8,10,20,50,53,70,91-93,95,96,99,100,110,213
     switchport trunk allowed vlan add 227,700,910,911,951,1830,1870,1890-1892
     switchport mode trunk
     logging event link-status
     shutdown
    interface TenGigabitEthernet1/1/1
    interface TenGigabitEthernet1/1/2
    interface Vlan1
     no ip address
     shutdown
    interface Vlan6
     description ***LANERF**
     ip address 10.20.6.106 255.255.255.0
     no ip redirects
    interface Vlan23
     description < TRANSITO MUR >
     no ip address
     no ip redirects
    interface Vlan100
     description < VLAN MAN >
     ip address 10.20.100.106 255.255.255.0
     no ip redirects
     ip ospf authentication message-digest
     ip ospf message-digest-key 1 md5 7 032368342B2F0F
     ip ospf dead-interval minimal hello-multiplier 4
    router ospf 1
     router-id 10.20.40.106
     auto-cost reference-bandwidth 100000
     area 0.0.0.0 authentication message-digest
     area 1.80.1.1 authentication message-digest
     redistribute connected subnets
     redistribute static subnets
     passive-interface default
     no passive-interface Vlan23
     no passive-interface Vlan100
     no passive-interface GigabitEthernet1/0/37
     network 10.20.6.0 0.0.0.0 area 0.0.0.0
     network 10.20.40.106 0.0.0.0 area 0.0.0.0
     network 10.20.91.6 0.0.0.0 area 0.0.0.0
     network 10.20.100.106 0.0.0.0 area 0.0.0.0
     default-information originate
    ip http server
    ip http secure-server
    access-list 100 permit ip 10.50.80.0 0.0.0.255 10.80.80.0 0.0.0.255
    access-list 100 permit ip 10.80.80.0 0.0.0.255 10.50.80.0 0.0.0.255
    snmp-server community ASComRO RO
    line con 0
    line vty 0 4
     login
    line vty 5 15
     login
    event manager applet track_qos_down authorization bypass
     event syslog pattern "TRACKING-5-STATE: 15 ip sla 15 reachability Up->Down"
     action 1 cli command "enable"
     action 2 cli command "configure terminal"
     action 3 cli command "interface giga1/0/37"
     action 4 cli command "rate-limit output access-group 100 400000000 50000000 50000000 conform-action transmit exceed-action drop"
     action 5 cli command "end"
    event manager applet track_qos_up authorization bypass
     event syslog pattern "TRACKING-5-STATE: 15 ip sla 15 reachability Down->Up"
     action 1 cli command "enable"
     action 2 cli command "configure terminal"
     action 3 cli command "interface giga1/0/37"
     action 4 cli command "no rate-limit output access-group 100 400000000 50000000 50000000 conform-action transmit exceed-action drop"
     action 5 cli command "end"
    end
    ERF#     
    ERF#show mls qos 
    QoS is enabled 
    QoS ip packet dscp rewrite is enabled 
    ERF#show mls qos inter gigabitEthernet 1/0/37 
    GigabitEthernet1/0/37 
    trust state: not trusted 
    trust mode: not trusted 
    trust enabled flag: ena 
    COS override: dis 
    default COS: 0 
    DSCP Mutation Map: Default DSCP Mutation Map 
    Trust device: none 
    qos mode: port-based 
    When I apply the command I'm seeing a gauge using a 3rd party but I'm not seeing that the traffic will be truncated @ 50Mbps.
    Any thoughts??? 

    Hi
    Bandwidth commands allocates the particular amount of bandwidth you mention or configure over there.
    Basically you have the liberty to configure upto 75% of the available interface bandwidth to different classes.
    most widelys used with CBWFQ technique..
    so while configuring up the same better to watch out for the exact bandwidth value keyed in on the interface to have your alloocation work properly.
    policing basically used for limiting the traffic or to control the bursts by dropping them or marking them with different ip precedence or DSCP values.
    its very much similar to the rate-limit command applied on the interface level which again uses token bucket system either single or dual based on the configuration parameters.
    for more info on above mentioned clis do check these links..
    http://www.cisco.com/en/US/tech/tk543/tk545/tsd_technology_support_protocol_home.html
    http://www.cisco.com/en/US/tech/tk543/tk544/tsd_technology_support_protocol_home.html
    regds

Maybe you are looking for