3850 IOS XE QoS Queue Buffers

I'm configuring QoS on a 3850 and came across the "queue-buffers ratio" command. Does anyone know what the ratio is?  I am also assuming that this is software buffers that I'm configuring. Also, what does the command affect in the IOS? If anyone can find a source for it to, that would be awesome. I couldn't find anything online. Here is the documentation on the command I'm referring to. Thank you!
http://www.cisco.com/en/US/docs/switches/lan/catalyst3850/software/release/3.2_0_se/qos/command_reference/b_mqc_qt_32se_3850_cr_chapter_010.html#wp3514062886

Hi John,
Here is my source of reference for this response
End to End QoS Design- Quality of Service for Rich-Media & Cloud Networks
Here is the extract from above reference, which I hope useful to you.
- Hardware allocation of buffers is provided only to the priority queues on both wired & wireless queues of this platform.
- The other queues are allocated bufferes on as-needed basis, making it more flexible within the system to support several queues at once.
- Each queue (class) can leverage additional buffering capacity from the shared buffer pool based on a "queue-buffer ratio x" command.
- This command sets the ratio of buffers received by the class and these are allocated on an as-needed basis
- In general the max rate for the class is upto four times the configured value, the queue-buffer ratio command skew this value based on the overall ratio provided to the queue.
- By default these use 1:1:1... for a wired port & 10:20:50:20 for a wireless port on this platform.
- The recommended buffer allocation for wired interface queue 7 to 1 are 10:10:10:10:10:10:25 in percentage (%). Wireless port should use the default values.
- 3850 does not provide reserve thresholds and maximum(overload) thresholds are based on the queue buffer's ratio for non priority queues.
This post may also help you on this
http://mrncciew.com/2013/12/23/3850-qos-part-2-queuing-models/
HTH
Rasika
**** Pls rate all useful responses ****

Similar Messages

  • Creating JMS Queues/Buffers for WLI Deployments

    I am reading the WLI/Weblogic docs and I read that you can create a JMS application module and deploy it in an ear file with a wli process application.
    I want to add the queues/buffers required by a WLI Process Application to a JMS application module, then add the module to a wli process application ear file, so I can just deploy the ear to a production server and the queues/buffers will automatically be created when the WLI application is deployed.
    Will this work? If this will work, do I need to target the queues in the application module to a JMS Server? Anything else I need to do?
    Any help is greatly appreciated! Having to create new queues and buffers every time I deploy a WLI app to a new server is not fun.
    Thanks in advance!...
    John

    Hi John,
    Application modules work, but aren't recommended except for very advanced use cases. System modules are generally the best bet. This is advice is included in the Best Practices link I supplied in your last thread on this newsgroup, and also in the highly recommended new book "Professional Oracle WebLogic Server".
    For targeting advice, also see the "Best Practices" link -- the advice applies to all types of JMS config modules (application, stand-alone, or system).
    Tom

  • Prioritization within QoS queue possible?

    Our company runs QoS over an MPLS WAN, but I am personally new to the technology. Given that our provider only allows four queues (EF, AF31, AF21, and BE), we have configured four corresponding policies. This seems somewhat limiting, given the number of queues Cisco actually supports. Here's the question; Is it possible to further prioritize traffic within a given queue?
    Say for example, we want to place a certain traffic type within AF31, but we do not want to adversely impact other traffic within the queue. By the same token, we do not want to move either of these traffic types to EF. Can we control, in a more granular manner, prioritization within a respective queue? Any clarification you can provide would be greatly appreciated.

    As Laurent also describes, it's usually possible to fully manage congestion to MPLS (generally easy if you control the CE router). With MPLS, though, where the limitations of the provider's QoS model are most troublesome is upon MPLS cloud egress. It's possible to indirectly control this if you logically manage your MPLS cloud as you might with frame-relay or ATM. Unfortuanately, this is often impractical if you have more than a few nodes and have a logical mesh topology vs. hub and spoke.
    PS:
    Some MPLS providers allow you to select from various "profiles" of QoS model choices. This can be very helpful if traffic ratios vary between sites. Also, some MPLS vendor QoS models also provide support for different drop thresholds within some classes.

  • Cat. 3750 QoS Queue statistics

    Hi all:
    Does anyone know a way to see input and output queue statistics like occupation, number of frames discarded due to threshold reached etc ... on a Cat 3750
    May be there exists a MIB...
    Best regs.

    the command "show mls qos interface" should help.
    check out the following link for the command reference :
    http://www.cisco.com/en/US/products/hw/switches/ps5023/products_command_reference_chapter09186a008017f8ed.html#2418190

  • Possible to upgrade pkg on 3850 IOS-XE to fix bug CSCtz13264

    I am running into the bug :
    CSCtz13264  
    3850: Remove CLIs used to configure GRE tunnel - may cause crash.
    The fix for this is in 15.0(13.65)EZD.
    I have the following IOS-XE :
    *    1 56    WS-C3850-48T       03.03.03SE        cat3k_caa-universalk9 INSTALL
    Which has IOSd:
    Package: IOS, version: 150-1.EZ3, status: active
      File: cat3k_caa-iosd-universalk9.SPA.150-1.EZ3.pkg, on: Switch1
    How can I upgrade to the bug fix as we are already running the latest IOS-XE, is it possible to just upgrade the IOSd pkg, and how do I go about this?
    Also, what do the letters at the end of the file represent, ie  150-1.EZ3 and 15.0(13.65)EZD?
    Thanks in advance.

    Hello
    This bug is "fixed" - the fix is removing the ability to configure this.  When this switch first went live, we had the ability to enable this feature, however it should have never been possible.  When enabled, it was completely run in software and in turn essentially DOS'ing the box.
    EZ3 is maintenance release 3 - disregard 15.0(13.65)EZD.
    "is it possible to just update a pkg file on a IOS-XE"  ??  NO
    HTH
    luke

  • Flushing queue buffers

    Anyone know how to flush the queue buffer.
    I ran a large a large delete on a streams replicated table. Everything was captured and propagated. Since the apply takes longer than I thought, I just wanted to stop the apply and remove everything from the queue so it doesn't dequeue them.

    Seems like only option is by removing table from APPLY/CAPTURE/PROPAGATION after disabling them. You may need to remove all rules for this table from rulesets and drop rules manually after dropping the table.
    Then add the table back.

  • 3750 - mls qos queue-set output threshold

    In the IOS command, http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_44_se/command/reference/cli1.html#wp2144505. The drop-threshold1 and 2 is in the range from 1 3200%. Can somebody elaborate on the 3200%. How do they determine that number and what that number means to my threshold? Thanks

    The drop threshold should be lower than the shutdown threshold (if configured) and should be based on the maximum
    amount of PDUs you expect to receive on a port and on the CPU utilization during peaks hours. These values usually determine what is a normal peak condition and therefore what could be an abnormal peak condition. Then you can set the threshold between the two to avoid excessive spikes of PDUs on a port

  • 3850 Switch - QOS

    HI
    We've just purchased 3850 switch part of a wireless upgrade, but we are usign 8500 wlc.
    Want to use the 3580 just as a edge switch without the wlc as we didn't purchase the licences.
    Using our exsiting 3750x template haing issues with the QOS settings
    mls qos map cos-dscp 0 8 16 24 32 46 48 56
    mls qos srr-queue input cos-map queue 2 threshold 1 3
    mls qos srr-queue input dscp-map queue 2 threshold 1 24
    mls qos srr-queue output cos-map queue 1 threshold 3 5
    mls qos srr-queue output cos-map queue 2 threshold 1 2
    mls qos srr-queue output cos-map queue 2 threshold 3 3
    mls qos srr-queue output cos-map queue 3 threshold 1 1
    mls qos srr-queue output cos-map queue 3 threshold 3 0
    mls qos srr-queue output cos-map queue 4 threshold 3 6 7
    mls qos queue-set output 2 threshold 2 3200 3200 100 3200
    mls qos queue-set output 2 buffers 10 70 10 10
    mls qos
    any help would be apprieicated in pointing to right direction.
    Have been looking for last couple of days.
    cheers

    Hi
    this might help (as we moved from 3750 to 3850 switches, we had to rebuild qos).
    The basic idea is something like this
    Class-maps:
    class-map match-any CM_VOIP
    match dscp ef
    class-map match-any CM_SIGNALING
    match ip dscp cs3
    match ip dscp af31
    class-map match-any VC_VIDEO
    match dscp af41
    Policy map for the uplink:
    policy-map UPLINK-OUT
    class CM_VOIP
    priority level 1 percent 10 (this is the high priority queue)
    police cir percent 10 conform-action transmit exceed-action drop
    class CM_SIGNALING
    priority level 2 percent 5 (low priority queue)
    police cir percent 5 conform-action transmit exceed-action drop
    class VC_VIDEO
    bandwidth remaining percent 10
    class class-default
    bandwidth remaining percent 75
    Uplink config:
    Interface Gi1/1/1
    Service-policy output UPLINK-OUT
    This way you can build your qos policies. You can tune anyway you like / configure more traffic types and/or confighure policies for access ports

  • 3850 QoS question

    Hello,
    I am trying to upgrade from 3750 to 3850. Following is my outbound WTD qos config on 3750:
    mls qos srr-queue output cos-map queue 1 threshold 3 5
    mls qos srr-queue output cos-map queue 2 threshold 1 2 4
    mls qos srr-queue output cos-map queue 2 threshold 2 3
    mls qos srr-queue output cos-map queue 2 threshold 3 6 7
    mls qos srr-queue output cos-map queue 3 threshold 3 0
    mls qos srr-queue output cos-map queue 4 threshold 3 1
    mls qos srr-queue output dscp-map queue 1 threshold 3 46
    mls qos srr-queue output dscp-map queue 2 threshold 1 16 18 20 22 32 34 36 38
    mls qos srr-queue output dscp-map queue 2 threshold 2 24 26 28 30
    mls qos srr-queue output dscp-map queue 2 threshold 3 48 56
    mls qos srr-queue output dscp-map queue 3 threshold 3 0
    mls qos srr-queue output dscp-map queue 4 threshold 1 8
    mls qos srr-queue output dscp-map queue 4 threshold 3 4 10 12 14
    mls qos queue-set output 1 threshold 2 70 80 100 100
    mls qos queue-set output 1 threshold 4 40 100 100 100
    What will be the equivalent config for the 3850? I am not able to find the right documentation for 3850.
    Following is what I created but I believe it wouldnt handle WTD.
    class-map match-any EF
    match dscp ef
    class-map match-any CS3AF41
    match dscp cs3 af41
    class-map match-any AF21
    match dscp af21
    class-map match-any AF11
    match dscp af11
    class-map match-any Default
    match dscp default
    policy-map QOS-OUTBOUND
    class EF
       priority level 1
    class CS3AF41
       priority level 2
    class AF21
       bandwidth remaining percent 20
       shape average percent 100
    class AF11
       bandwidth remaining percent 20
       shape average percent 100
    class Default
       bandwidth remaining percent 60
       shape average percent 100
    Also, when I try to apply this to an interface, it accepts it but its not visible under show runn. Am I missing anything?
    I would appreciate any help with this.
    Thank you.

    Hi,
    3850 is not supporting MLS QoS (so any QoS commands start with mls keyword is not applicable in this switch platform- even thoug they are accepted).
    It is a MQC QoS based switch platform (like 6500,4500). There are few Queing models (1P7Q3T, 2P6Q3T for wired &  2P2Q for wireless) supported in this platform. Please refer below post for more detail
    http://mrncciew.com/2013/12/23/3850-qos-part-2-queuing-models/
    Based on this you need to derive your config changes. As you can see in the above "queue limit x " is the command used to configure WTD for non-priority queues (ie Q2 to Q6)
    Regarding running config, you can use "show running-config all" command to see all the configuration lines of your switch including default configs
    HTH
    Rasika
    ***Pls rate all useful responses ****

  • MLS QoS configuration

    Good Morning, everyone.  I am looking for some clarification with an existing 3750x Switch configuration.  
    I am reviewing the configuration of my network switches and found the following MLS QoS configuration on one of my switches and a partial of this same config on another switch.  Can someone please explain what function, this line of code, is performing; and is it necessary?
    mls qos map policed-dscp  0 14 24 30 38 to 8
    mls qos map policed-dscp  10 to 12
    mls qos map policed-dscp  12 to 14
    mls qos map policed-dscp  26 to 28
    mls qos map policed-dscp  28 to 30
    mls qos map policed-dscp  32 to 34
    mls qos map policed-dscp  34 to 36
    mls qos map policed-dscp  36 to 38
    mls qos map cos-dscp 0 8 16 24 34 46 48 56
    mls qos srr-queue input bandwidth 70 30
    mls qos srr-queue input threshold 1 80 90
    mls qos srr-queue input threshold 2 80 90
    mls qos srr-queue input priority-queue 2 bandwidth 30
    mls qos srr-queue input dscp-map queue 1 threshold 2 16 24
    mls qos srr-queue input dscp-map queue 1 threshold 3 48 56
    mls qos srr-queue input dscp-map queue 2 threshold 1 36 38
    mls qos srr-queue input dscp-map queue 2 threshold 2 32 34
    mls qos srr-queue input dscp-map queue 2 threshold 3 40 46
    mls qos srr-queue output cos-map queue 1 threshold 2 4
    mls qos srr-queue output cos-map queue 1 threshold 3 5
    mls qos srr-queue output cos-map queue 2 threshold 1 2
    mls qos srr-queue output cos-map queue 2 threshold 2 3
    mls qos srr-queue output cos-map queue 2 threshold 3 6 7
    mls qos srr-queue output cos-map queue 3 threshold 3 0
    mls qos srr-queue output cos-map queue 4 threshold 3 1
    mls qos srr-queue output dscp-map queue 1 threshold 2 32 34
    mls qos srr-queue output dscp-map queue 1 threshold 3 40 46
    mls qos srr-queue output dscp-map queue 2 threshold 1 18 20 22 26 28 30
    mls qos srr-queue output dscp-map queue 2 threshold 2 16 24
    mls qos srr-queue output dscp-map queue 2 threshold 3 48 56
    mls qos srr-queue output dscp-map queue 3 threshold 3 0
    mls qos srr-queue output dscp-map queue 4 threshold 1 8
    mls qos srr-queue output dscp-map queue 4 threshold 2 12 14
    mls qos srr-queue output dscp-map queue 4 threshold 3 10
    mls qos queue-set output 1 threshold 1 100 100 100 100
    mls qos queue-set output 1 threshold 2 80 90 100 400
    mls qos queue-set output 1 threshold 3 100 100 100 400
    mls qos queue-set output 1 threshold 4 90 100 100 400
    mls qos queue-set output 1 buffers 15 30 35 20
    mls qos
    If more information is required for a response, please let me know.
    Thank you, E.

    Disclaimer
    The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
    Liability Disclaimer
    In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
    Posting
    The function of each command is perhaps best explained by the Command Reference and Software Configuration Guide for your IOS version.  If you have a question that's unanswered by those, please post another question.  BTW, Cisco also publishes whitepapers that further explain some subjects.  There are a couple on 3750 QoS.
    Regarding whether a particular command is necessary would depend on what your QoS policy is attempting to accomplish.

  • 3750X QoS Problems

    I'm new to setting up QoS so I would like some input.
    I'm setting up QoS on my 3750X:
    Cisco IOS Software, C3750E Software (C3750E-UNIVERSALK9-M), Version 15.2(2)E, RELEASE SOFTWARE (fc3)
    I enabled Auto QoS on the switch:
    mls qos map policed-dscp  0 10 18 24 46 to 8
    mls qos map cos-dscp 0 8 16 24 32 46 48 56
    mls qos srr-queue input bandwidth 70 30
    mls qos srr-queue input threshold 1 80 90
    mls qos srr-queue input priority-queue 2 bandwidth 30
    mls qos srr-queue input cos-map queue 1 threshold 2 3
    mls qos srr-queue input cos-map queue 1 threshold 3 6 7
    mls qos srr-queue input cos-map queue 2 threshold 1 4
    mls qos srr-queue input dscp-map queue 1 threshold 2 24
    mls qos srr-queue input dscp-map queue 1 threshold 3 48 49 50 51 52 53 54 55
    mls qos srr-queue input dscp-map queue 1 threshold 3 56 57 58 59 60 61 62 63
    mls qos srr-queue input dscp-map queue 2 threshold 3 32 33 40 41 42 43 44 45
    mls qos srr-queue input dscp-map queue 2 threshold 3 46 47
    mls qos srr-queue output cos-map queue 1 threshold 3 4 5
    mls qos srr-queue output cos-map queue 2 threshold 1 2
    mls qos srr-queue output cos-map queue 2 threshold 2 3
    mls qos srr-queue output cos-map queue 2 threshold 3 6 7
    mls qos srr-queue output cos-map queue 3 threshold 3 0
    mls qos srr-queue output cos-map queue 4 threshold 3 1
    mls qos srr-queue output dscp-map queue 1 threshold 3 32 33 40 41 42 43 44 45
    mls qos srr-queue output dscp-map queue 1 threshold 3 46 47
    mls qos srr-queue output dscp-map queue 2 threshold 1 16 17 18 19 20 21 22 23
    mls qos srr-queue output dscp-map queue 2 threshold 1 26 27 28 29 30 31 34 35
    mls qos srr-queue output dscp-map queue 2 threshold 1 36 37 38 39
    mls qos srr-queue output dscp-map queue 2 threshold 2 24
    mls qos srr-queue output dscp-map queue 2 threshold 3 48 49 50 51 52 53 54 55
    mls qos srr-queue output dscp-map queue 2 threshold 3 56 57 58 59 60 61 62 63
    mls qos srr-queue output dscp-map queue 3 threshold 3 0 1 2 3 4 5 6 7
    mls qos srr-queue output dscp-map queue 4 threshold 1 8 9 11 13 15
    mls qos srr-queue output dscp-map queue 4 threshold 2 10 12 14
    mls qos queue-set output 1 threshold 1 100 100 50 200
    mls qos queue-set output 1 threshold 2 125 125 100 400
    mls qos queue-set output 1 threshold 3 100 100 100 3200
    mls qos queue-set output 1 threshold 4 60 150 50 200
    mls qos queue-set output 1 buffers 15 25 40 20
    mls qos
    auto qos srnd4
    All ports are setup like this:
    interface GigabitEthernet1/0/1
     switchport mode access
     srr-queue bandwidth share 1 30 35 5
     priority-queue out
     mls qos trust dscp
     auto qos trust dscp
    The problem is this:
    I have an IPTV application that I tag with AF41 (DSCP 34):
    policy-map QoS-Ceton-InfiniTV-Policy
     class QoS-Ceton-InfiniTV-Data-Class
      set dscp af41
    But when I'm playing that application back on a client, packets are dropped when I'm also running Remote Desktop tagged with AF21 (DSCP 18).
    Temporarily, I solved the problem by changing all ports to queue-set 2:
    Queueset: 1
    Queue     :       1       2       3       4
    buffers   :      15      25      40      20
    threshold1:     100     125     100      60
    threshold2:     100     125     100     150
    reserved  :      50     100     100      50
    maximum   :     200     400    3200     200
    Queueset: 2
    Queue     :       1       2       3       4
    buffers   :      25      25      25      25
    threshold1:     100     200     100     100
    threshold2:     100     200     100     100
    reserved  :      50      50      50      50
    maximum   :     400     400     400     400
    What I don't get is Auto QoS is suppose to make this easy, isn't it?
    How come AF41 packets are dropped for AF21 packets?
    Thanks for any input.

    Even with queue-set 2, I still see drops, just not as many.
    GigabitEthernet1/0/27 (All statistics are in packets)
      dscp: incoming  
      0 -  4 :     7324189            0            0            0            0  
      5 -  9 :           0            0            0            0            0  
     10 - 14 :           0            0            0            0            0  
     15 - 19 :           0            0            0       236744            0  
     20 - 24 :           0            0            0            0            0  
     25 - 29 :           0         1127            0            0            0  
     30 - 34 :           0            0            0            0            0  
     35 - 39 :           0            0            0            0            0  
     40 - 44 :           0            0            0            0            0  
     45 - 49 :           0            0            0            0            0  
     50 - 54 :           0            0            0            0            0  
     55 - 59 :           0            0            0            0            0  
     60 - 64 :           0            0            0            0  
      dscp: outgoing
      0 -  4 :    17433393            2           94            0          163  
      5 -  9 :           0          291            0            1            0  
     10 - 14 :       30613            0            0            0            0  
     15 - 19 :           0         3822            0       281615            0  
     20 - 24 :           0            0            0            0       103072  
     25 - 29 :           0           11            0            0            0  
     30 - 34 :           0            0         7605            0     15387535  
     35 - 39 :           0            0            0            0            0  
     40 - 44 :           0            0            0            0            0  
     45 - 49 :           0            0            0        16394            0  
     50 - 54 :           0            0            0            0            0  
     55 - 59 :           0        18872            0            0            0  
     60 - 64 :           0            0            0            0  
      cos: incoming  
      0 -  4 :     7564272            0            0            0            0  
      5 -  7 :           0            0            0  
      cos: outgoing
      0 -  4 :    17467998        30614       285437       103083     15395140  
      5 -  7 :        7914        16394       209955  
      output queues enqueued:
     queue:    threshold1   threshold2   threshold3
     queue 0:           0           0        7605
     queue 1:    15673244      245425      264513
     queue 2:           0           0    17441610
     queue 3:           1       30602           0
      output queues dropped:
     queue:    threshold1   threshold2   threshold3
     queue 0:           0           0           0
     queue 1:           0           0           0
     queue 2:           0           0         588
     queue 3:           0           0           0
    Policer: Inprofile:            0 OutofProfile:            0

  • 2960-X vs 2960 QOS

    I am configuring QOS for some 2960-X's for a new deployment that also has some 2960's. The current 2960's already have auto qos configured. When I configured auto qos voip trust for the 2960-X, I noticed there were not any ingress queues and the all of the numbers for the queues were different. Should this be a concern at all if the switches are trunked together or even if they aren't? I am not that proficient with QOS yet. See below for configs.
    Thanks for your help!
    From 2960
    mls qos map cos-dscp 0 8 16 24 32 46 48 56
    mls qos srr-queue input bandwidth 90 10
    mls qos srr-queue input threshold 1 8 16
    mls qos srr-queue input threshold 2 34 66
    mls qos srr-queue input buffers 67 33
    mls qos srr-queue input cos-map queue 1 threshold 2 1
    mls qos srr-queue input cos-map queue 1 threshold 3 0
    mls qos srr-queue input cos-map queue 2 threshold 1 2
    mls qos srr-queue input cos-map queue 2 threshold 2 4 6 7
    mls qos srr-queue input cos-map queue 2 threshold 3 3 5
    mls qos srr-queue input dscp-map queue 1 threshold 2 9 10 11 12 13 14 15
    mls qos srr-queue input dscp-map queue 1 threshold 3 0 1 2 3 4 5 6 7
    mls qos srr-queue input dscp-map queue 1 threshold 3 32
    mls qos srr-queue input dscp-map queue 2 threshold 1 16 17 18 19 20 21 22 23
    mls qos srr-queue input dscp-map queue 2 threshold 2 33 34 35 36 37 38 39 48
    mls qos srr-queue input dscp-map queue 2 threshold 2 49 50 51 52 53 54 55 56
    mls qos srr-queue input dscp-map queue 2 threshold 2 57 58 59 60 61 62 63
    mls qos srr-queue input dscp-map queue 2 threshold 3 24 25 26 27 28 29 30 31
    mls qos srr-queue input dscp-map queue 2 threshold 3 40 41 42 43 44 45 46 47
    mls qos srr-queue output cos-map queue 1 threshold 3 5
    mls qos srr-queue output cos-map queue 2 threshold 3 3 6 7
    mls qos srr-queue output cos-map queue 3 threshold 3 2 4
    mls qos srr-queue output cos-map queue 4 threshold 2 1
    mls qos srr-queue output cos-map queue 4 threshold 3 0
    mls qos srr-queue output dscp-map queue 1 threshold 3 40 41 42 43 44 45 46 47
    mls qos srr-queue output dscp-map queue 2 threshold 3 24 25 26 27 28 29 30 31
    mls qos srr-queue output dscp-map queue 2 threshold 3 48 49 50 51 52 53 54 55
    mls qos srr-queue output dscp-map queue 2 threshold 3 56 57 58 59 60 61 62 63
    mls qos srr-queue output dscp-map queue 3 threshold 3 32 33 34 35 36 37 38 39
    mls qos srr-queue output dscp-map queue 4 threshold 1 8
    mls qos srr-queue output dscp-map queue 4 threshold 2 9 10 11 12 13 14 15
    mls qos srr-queue output dscp-map queue 4 threshold 3 0 1 2 3 4 5 6 7
    mls qos queue-set output 1 threshold 1 138 138 92 138
    mls qos queue-set output 1 threshold 2 138 138 92 400
    mls qos queue-set output 1 threshold 3 36 77 100 318
    mls qos queue-set output 1 threshold 4 20 50 67 400
    mls qos queue-set output 2 threshold 1 149 149 100 149
    mls qos queue-set output 2 threshold 2 118 118 100 235
    mls qos queue-set output 2 threshold 3 41 68 100 272
    mls qos queue-set output 2 threshold 4 42 72 100 242
    mls qos queue-set output 1 buffers 10 10 26 54
    mls qos queue-set output 2 buffers 16 6 17 61
    mls qos
    interface FastEthernet0/2
    switchport access vlan 100
    switchport mode access
    switchport voice vlan 110
    srr-queue bandwidth share 10 10 60 20
    queue-set 2
    priority-queue out
    mls qos trust cos
    auto qos voip trust
    spanning-tree portfast
    From 2960-X
    mls qos map cos-dscp 0 8 16 24 32 46 48 56
    mls qos srr-queue output cos-map queue 1 threshold 3 4 5
    mls qos srr-queue output cos-map queue 2 threshold 1 2
    mls qos srr-queue output cos-map queue 2 threshold 2 3
    mls qos srr-queue output cos-map queue 2 threshold 3 6 7
    mls qos srr-queue output cos-map queue 3 threshold 3 0
    mls qos srr-queue output cos-map queue 4 threshold 3 1
    mls qos srr-queue output dscp-map queue 1 threshold 3 32 33 40 41 42 43 44 45
    mls qos srr-queue output dscp-map queue 1 threshold 3 46 47
    mls qos srr-queue output dscp-map queue 2 threshold 1 16 17 18 19 20 21 22 23
    mls qos srr-queue output dscp-map queue 2 threshold 1 26 27 28 29 30 31 34 35
    mls qos srr-queue output dscp-map queue 2 threshold 1 36 37 38 39
    mls qos srr-queue output dscp-map queue 2 threshold 2 24
    mls qos srr-queue output dscp-map queue 2 threshold 3 48 49 50 51 52 53 54 55
    mls qos srr-queue output dscp-map queue 2 threshold 3 56 57 58 59 60 61 62 63
    mls qos srr-queue output dscp-map queue 3 threshold 3 0 1 2 3 4 5 6 7
    mls qos srr-queue output dscp-map queue 4 threshold 1 8 9 11 13 15
    mls qos srr-queue output dscp-map queue 4 threshold 2 10 12 14
    mls qos queue-set output 1 threshold 1 100 100 50 200
    mls qos queue-set output 1 threshold 2 125 125 100 400
    mls qos queue-set output 1 threshold 3 100 100 100 400
    mls qos queue-set output 1 threshold 4 60 150 50 200
    mls qos queue-set output 1 buffers 15 25 40 20
    mls qos
    interface GigabitEthernet1/0/1
    switchport access vlan 100
    switchport mode access
    switchport voice vlan 110
    srr-queue bandwidth share 1 30 35 5
    priority-queue out
    mls qos trust cos
    auto qos trust
    spanning-tree portfast

    Disclaimer
    The  Author of this posting offers the information contained within this  posting without consideration and with the reader's understanding that  there's no implied or expressed suitability or fitness for any purpose.  Information provided is for informational purposes only and should not  be construed as rendering professional advice of any kind. Usage of this  posting's information is solely at reader's own risk.
    Liability Disclaimer
    In  no event shall Author be liable for any damages whatsoever (including,  without limitation, damages for loss of use, data or profit) arising out  of the use or inability to use the posting's information even if Author  has been advised of the possibility of such damage.
    Posting
    IMO, AutoQoS is always a concern (as are device defaults, without it).
    If you're doing to "do" QoS, you should have a policy that serves your service needs, and configurations to support it.  AutoQoS might, or might not, be exactly what you need.
    If you're not proficient with QoS, on most LANs, you might actually be better off disabling it.

  • Router 876 and IOS 12.3 (8) YI2

    I am using SDM 2.2a. I want to use QoS but the SDM replies that i can't because of the IOS. Wich version of IOS Supports QoS on this router?

    According to Feature Navigator, it takes the Advanced IP Services or Advanced Enterprise Services feature set to do QoS queuing on this router.
    Feature Navigator
    www.cisco.com/go/fn
    Hope this helps.
    Brandon

  • QoS in MPLS Packet drops

    Hello
    I have experienced the following situation recently. It hasn't fixed yet. If you have any idea, please advise. Any comments are welcome!
    The problem was that the voice packets have been dropped in class Voice despite the fact that the interface's utilization is quite low. Please see the policy-map interface output below.
    Service-policy output: out_(3072k/3072k)_QoS (4754)
    queue stats for all priority classes:
    queue limit 192 (packets)
    (queue depth/total drops/no-buffer drops) 0/297/0
    (pkts queued/bytes queued) 12372/1041424
    Class-map: Voice (match-all) (4755/7)
    12098 packets, 1042365 bytes
    5 minute offered rate 32000 bps, drop rate 3000 bps
    Match: ip precedence 5 (4756)
    Priority 50 (%) (1536 kbps) burst 1250000 (bytes)
    I removed the service-module from the multilink interface and restored. I repeated the procedure for a few times. At some point, I noticed that queue-limit of LLQ changed from 192 to 384. I didn't change it manually. It was changed by itself. Then the drop stopped.
    Service-policy output: out_(3072k/3072k)_QoS (6339)
    queue stats for all priority classes:
    queue limit 384 (packets)
    (queue depth/total drops/no-buffer drops) 0/0/0
    (pkts queued/bytes queued) 2628/221321
    Class-map: Voice (match-all) (6340/7)
    2653 packets, 228634 bytes
    5 minute offered rate 14000 bps, drop rate 0 bps
    Match: ip precedence 5 (6341)
    Priority 50 (%) (1536 kbps) burst 1250000 (bytes)
    * I omitted some of the output due to the text size in this forum.
    The average packet sizes in queue-limit 192 and 384 are almost same (86 bytes/packet).
    Does anyone know how does the IOS calculate the queue-limit in LLQ? I know that it changes dynamic in LLQ but would like to know the algorithm.
    Did anyone have a similar experience?
    Thank you,

    Hello Creed,
    >> I just think that the P router might not able to police the traffics as it get routed into the tunnels...
    With both LDP LSPs and MPLS TE LSPs traffic is forwarded inside MPLS frames and so EXP field of the topmost label is accessible to P routers to provide diffserv QoS treatments.
    Usually P routers implement only outgoing scheduling (queueing) combined with congestion avoidance (WRED).
    The service policies are applied outbound the physical interfaces.
    Rate control of what traffic enters the MPLS cloud both LDP LSPs and MPLS TE LSPs is made on PE at the edge before traffic enters the MPLS space.
    DSCP bits should not be accessible inside the MPLS cloud once the ip packet travel inside an MPLS label stack.
    Actually some inside inspections can be performed for flow based load-balancing purposes.
    So policing on the P routers is not used in general.
    Hope to help
    Giuseppe

  • Understanding QoS settings

    After going through the config on one of our switches I noticed some QoS settings that I have no idea what they mean and was wondering if someone could help me understand what these settings mean. Here is the config I found plus the config on one of the ports:
    mls qos map cos-dscp 0 8 16 26 32 46 48 56
    mls qos srr-queue input bandwidth 90 10
    mls qos srr-queue input threshold 1 8 16
    mls qos srr-queue input threshold 2 34 66
    mls qos srr-queue input buffers 67 33
    mls qos srr-queue input cos-map queue 1 threshold 2  1
    mls qos srr-queue input cos-map queue 1 threshold 3  0
    mls qos srr-queue input cos-map queue 2 threshold 1  2
    mls qos srr-queue input cos-map queue 2 threshold 2  4 6 7
    mls qos srr-queue input cos-map queue 2 threshold 3  3 5
    mls qos srr-queue input dscp-map queue 1 threshold 2  9 10 11 12 13 14 15
    mls qos srr-queue input dscp-map queue 1 threshold 3  0 1 2 3 4 5 6 7
    mls qos srr-queue input dscp-map queue 1 threshold 3  32
    mls qos srr-queue input dscp-map queue 2 threshold 1  16 17 18 19 20 21 22 23
    mls qos srr-queue input dscp-map queue 2 threshold 2  33 34 35 36 37 38 39 48
    mls qos srr-queue input dscp-map queue 2 threshold 2  49 50 51 52 53 54 55 56
    mls qos srr-queue input dscp-map queue 2 threshold 2  57 58 59 60 61 62 63
    mls qos srr-queue input dscp-map queue 2 threshold 3  24 25 26 27 28 29 30 31
    mls qos srr-queue input dscp-map queue 2 threshold 3  40 41 42 43 44 45 46 47
    mls qos srr-queue output cos-map queue 1 threshold 3  5
    mls qos srr-queue output cos-map queue 2 threshold 3  3 6 7
    mls qos srr-queue output cos-map queue 3 threshold 3  2 4
    mls qos srr-queue output cos-map queue 4 threshold 2  1
    mls qos srr-queue output cos-map queue 4 threshold 3  0
    mls qos srr-queue output dscp-map queue 1 threshold 3  40 41 42 43 44 45 46 47
    mls qos srr-queue output dscp-map queue 2 threshold 3  24 25 26 27 28 29 30 31
    mls qos srr-queue output dscp-map queue 2 threshold 3  48 49 50 51 52 53 54 55
    mls qos srr-queue output dscp-map queue 2 threshold 3  56 57 58 59 60 61 62 63
    mls qos srr-queue output dscp-map queue 3 threshold 3  16 17 18 19 20 21 22 23
    mls qos srr-queue output dscp-map queue 3 threshold 3  32 33 34 35 36 37 38 39
    mls qos srr-queue output dscp-map queue 4 threshold 1  8
    mls qos srr-queue output dscp-map queue 4 threshold 2  9 10 11 12 13 14 15
    mls qos srr-queue output dscp-map queue 4 threshold 3  0 1 2 3 4 5 6 7
    mls qos queue-set output 1 threshold 1 138 138 92 138
    mls qos queue-set output 1 threshold 2 138 138 92 400
    mls qos queue-set output 1 threshold 3 36 77 100 318
    mls qos queue-set output 1 threshold 4 20 50 67 400
    mls qos queue-set output 2 threshold 1 149 149 100 149
    mls qos queue-set output 2 threshold 2 118 118 100 235
    mls qos queue-set output 2 threshold 3 41 68 100 272
    mls qos queue-set output 2 threshold 4 42 72 100 242
    mls qos queue-set output 1 buffers 10 10 26 54
    mls qos queue-set output 2 buffers 16 6 17 61
    mls qos
    vlan internal allocation policy ascending
    interface GigabitEthernet0/2
    switchport access vlan 40
    switchport mode access
    switchport voice vlan 100
    srr-queue bandwidth share 10 10 60 20
    srr-queue bandwidth shape  10  0  0  0
    queue-set 2
    mls qos trust device cisco-phone
    mls qos trust cos
    auto qos voip cisco-phone
    spanning-tree portfast
    Sorry for my ignorance.
    Thanks
    Brian

    In order for networking device to classify traffic, there is certain information within a frame or packet to identify the importance of a frame or packet. CoS, IP Precedence, and DSCP are widely used nowadays.
    CoS is in layer 2. IP Precedence and DSCP are in IP header.
    In a dot1q tag, there are 3 bit used to identify the importance of the frame. As CoS is 3-bit, the range is between 0 to 7. In normal Cisco VOIP implementation, Cisco IP phones mark CoS 5 on RTP frames. Data traffic is put on native VLAN; so that there is no 802.1q tag on data traffic. By default, Cisco switches put any traffic without 802.1q to be CoS 0 and DSCP 0.
    Before DSCP is used, the second byte in IP header is called ToS (Type of Service). It was used to classify IP traffic. Like CoS, IP precedence is 3 bits.  Thus, the range for IP precedence is 0 to 7. After a while, we find out that 3 bit is not long enough. We expand IP precedence from 3 bites to 6 bits. It is called DSCP. As DSCP is 6 bits, the range is 0 to 63. Normally, Cisco IP phones mark EF (DSCP value 46) on RTP packets.
    QoS on campus switching is different than router. In router, we normally mark and police the traffic just before going to ISP. As a result, you determine what traffic is dropped if the traffic going to ISP exceeds the bandwidth of the circuit.
    We normally classify traffic on ports connecting to phones and end devices. To simplify configuration, Cisco switches allow you to trust CoS; so that VOIP traffic is classify with CoS 5. Different switches have difference queues. However, all Cisco switches put CoS 5 or DSCP 46 into priority queue. Once traffic is classified on the access switches, we can simply trust DSCP or CoS on the links between switches. We should use trust DSCP on any layer 3 links. Also, make sure that voice VLAN is not used as native VLAN.
    The last question is what happens if a users put a data device on the voice VLAN and construst frames with CoS 5. Here comes extended trust. Switches have to receive CDP on the port before trusting the device on the voice VLAN is a VOIP phone. Not sure if I miss anything.

Maybe you are looking for

  • Unable to edit the site in sharepoint designer 2013

    Hi, I have created a custom list for one of my requirement, and I want to change the look and feel of the custom list view, so I was trying to edit this list in SharePoint Designer 2013, I'm able to open the list in SPD 2013, but unable to edit anyth

  • Very Very Urgent Issue: Restricted Key Figure does not return any data

    Hi all, Please help me solving this urgent issue. created customer exit variable on characterstics version and also other customer exit variable on Value type. I coded that in variable exit. Problem is when I include these in restrickted keyfigure My

  • Multiple users - shared folders - file permissions

    I want to be able to copy and move files between two user accounts so that each user will have read-write permsssions for those files. I have the standard Shared User folder (HD:Users:Shared), and the standard Users' Shared folders. More specifically

  • Oversized text on Word Document Place (.docx)

    When placing text from a word document (.docx) indesign only gives me three pages for a 118 long document.  Also, those pages are blank, and to access the text, I have to delete a few blank lines.  When I do this however, the text is grossly oversize

  • Using A LaCie d2 DVD +/- RW Drive With A Mini Running Mountain Lion??

    I have an older LaCie d2 DVD  /- RW drive that I would like to use with my Mac Mini running Mountain Lion.  LaCie says it is not compatible but I read somewhere that you can type a command into the terminal which will allow the unit to function.  Doe