Output queue drops

I just recently cleared the counters on this, and I see this below. Customer states the internet is 'slow'. They have a full 100mbs connection no policy added to interface. I have increased the hold queue as you can see, but still have drops. My question is, why isnt the output queue showing any activity? It still shows 0/150 (size/max) even when its dropping. Shouldnt this number be a percentage or atleast a 150/150 when it starts dropping so you can try to figure out where a value should be?
reliability 255/255, txload 10/255, rxload 1/255
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 2828
Queueing strategy: fifo
Output queue: 0/150 (size/max)
30 second input rate 438000 bits/sec, 312 packets/sec
30 second output rate 3925000 bits/sec, 466 packets/sec

I am still plagued with this problem. Hopefully I will have some real answers next week with whats going on. I have a Cisco rep coming into town and should be able to work at this all week.
It appears to be strictly switch related. Going from a 1GIG interface from the core, down to 10mbs seems to be where the output drops are happening on the customers interface. I have moved a all policing/shaping onto the 1GBS core link, and still get drops. Although it is not as bad as it used to be.... I have also reconfigured the Ethernet interface to be 'auto' rather than hard coded so the customer is free to use whatever port speed they want and its rate shaped off another port.
Does anyone else have problems with this ME3400 line from Cisco? Is anyone else seeing the massive output drops?
If not, would love to see a sample config on an Internet link type of setup and a P2P setup config...

Similar Messages

  • QoS - output queues dropped.

    Hi, i have a phone thats no working fine, it unregister all the time from the sip server. 
    The port connected to the phone has output queues dropped on queue 1. ¿That's normal? ¿What could be the cause that there drop packet?
    Thanks!
    I have this configuration for Qos on the switch port:
    interface FastEthernet0/15
     switchport mode access
     switchport voice vlan 15
     priority-queue out
     mls qos trust cos
     spanning-tree portfast
    sh mls qos int fa0/15 st
    FastEthernet0/15 (All statistics are in packets)
      dscp: incoming
      0 -  4 :      184994            0            0            0            0
      5 -  9 :           0            0            0            0            0
     10 - 14 :           0            0            0            0            0
     15 - 19 :           0            0            0            0            0
     20 - 24 :           0            0            0            0            0
     25 - 29 :           0      2298420            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      4806226            0        16934            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 :     8134930            0            0            0            0
      5 -  9 :           0            0            0            0            0
     10 - 14 :           0            0            0            0            0
     15 - 19 :           0            0            0            0            0
     20 - 24 :           0            0            0            0            0
     25 - 29 :           0            0            0            0            0
     30 - 34 :           0            0            0            0            0
     35 - 39 :           0            0            0            0            0
     40 - 44 :         861            0            0            0            0
     45 - 49 :           0            0            0            5            0
     50 - 54 :           0            0            0            0            0
     55 - 59 :           0            0            0            0            0
     60 - 64 :           0            0            0            0
      cos: incoming
      0 -  4 :      875001            0            0            0            0
      5 -  7 :     6544104            0            0
      cos: outgoing
      0 -  4 :     8781009            3            6            1            2
      5 -  7 :      275463            5        17983
      output queues enqueued:
     queue:    threshold1   threshold2   threshold3
     queue 0:      292615           0           0
     queue 1:     8562114       44049     5388502
     queue 2:           0           0           0
     queue 3:       17982           0      183824
      output queues dropped:
     queue:    threshold1   threshold2   threshold3
     queue 0:           0           0           0
     queue 1:        5349           0           0
     queue 2:           0           0           0
     queue 3:           0           0           0
    Policer: Inprofile:            0 OutofProfile:            0

    Martin,
    Refer to this link you need to modify your buffers etc. :http://www.cisco.com/c/en/us/support/docs/switches/catalyst-3750-series-switches/116089-technote-switches-output-drops-qos-00.html
    -Terry
    Please rate all helpful posts

  • OID for "output queue drops" ?

    Hi All!
    We use Zenoss Enterprise to monitor our ~ 3200 Cisco devices. We have successfully been able to use OIDs such as 1.3.6.1.2.1.2.2.1.20 and 1.3.6.1.2.1.2.2.1.14 to keep an eye on ifInErrors and ifOutErrors. However, we need to monitor the transmit output queue drops, i.e. the stat reported via sh int <interface> :
    Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 405496
    Please be gentle with me - I am NOT a SNMP guru. (I think it ought to be called CNMP - Complex Network Management Protocol ;-) . But, a starting point would be an OID that reports that value, even if it is a simple counter, we can take it from there.
    Here's a screen shot of the Performance Template that is workin for montitoring other data:
    Thanks!
    Steve

    Success! Found it here:
    http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en&translate=Translate&objectInput=1.3.6.1.4.1.9.2.2.1.1.27
    Thanks for being there for me, people - no really, I'm never sarcastic. Sometimes nothing does the trick like a little peer pressure combined with Mr. Google. This is a great forum with a very easy to use engine.
    Here are the results from Zenoss:
    Executing command
    snmpwalk -cxxxxx -v2c 10.254.248.6 1.3.6.1.4.1.9.2.2.1.1.27
    against ECB-3560G-1A.6.episd.org
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.1 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.248 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.5004 = INTEGER: 16846
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10101 = INTEGER: 110287486
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10102 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10103 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10104 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10105 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10106 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10107 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10108 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10109 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10110 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10111 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10112 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10113 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10114 = INTEGER: 9
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10115 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10116 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10117 = INTEGER: 6020
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10118 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10119 = INTEGER: 622
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10120 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10121 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10122 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10123 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10124 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10125 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10126 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10127 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10128 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10129 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10130 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10131 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10132 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10133 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10134 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10135 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10136 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10137 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10138 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10139 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10140 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10141 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10142 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10143 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10144 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10145 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10146 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10147 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10148 = INTEGER: 57735401
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10149 = INTEGER: 16846
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10150 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10151 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10152 = INTEGER: 0
    SNMPv2-SMI::enterprises.9.2.2.1.1.27.10501 = INTEGER: 0
    Steve

  • 3560 mls qos - output queues counters?

    Hi!
    I have WS-C3560G-24TS     15.0(2)SE4.
    In gi0/10 we received IPTV multicast traffic only.
    interface GigabitEthernet0/10
    description IPTV
    switchport access vlan 929
    switchport mode access
    switchport nonegotiate
    mls qos trust dscp
    channel-protocol lacp
    channel-group 3 mode active
    service-policy input iptv-cos
    end
    on port input - 350mbit - output 2000 Bit/s!
    Queueing strategy: fifo
      5 minute input rate 348797000 bits/sec, 32008 packets/sec
      5 minute output rate 0 bits/sec, 0 packets/sec
    Then i send command:
    clear counters
    clear mlq qos int stat
    and
    sh mls qos int gi0/10 st 
    after 5-10 seconds i see:
    GigabitEthernet0/10 (All statistics are in packets)
      dscp: incoming 
      0 -  4 :      156657            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            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 :           4            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            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 
      cos: incoming 
      0 -  4 :      156661            0            0            0            0 
      5 -  7 :           0            0            0 
      cos: outgoing
      0 -  4 :           4            0            0            0            0 
      5 -  7 :           0            0            0 
      output queues enqueued:
    queue:    threshold1   threshold2   threshold3
    queue 0:           0           0           0
    queue 1:           4           0           0
    queue 2:           0           0           0
    queue 3:           0           0      112066
      output queues dropped:
    queue:    threshold1   threshold2   threshold3
    queue 0:           0           0           0
    queue 1:           0           0           0
    queue 2:           0           0           0
    queue 3:           0           0           0
    Policer: Inprofile:            0 OutofProfile:            0
    Question!
    Why i have 112066 packets in output queue 3, then bitrate output - 5 minute output rate 0 bits/sec, 0 packets/sec  and 7 packets output, 576 bytes after clear.

    I have any time this bitrate.
    a few hours later I see:
    bm18.lan#sh mls q int gi0/10 st
    GigabitEthernet0/10 (All statistics are in packets)
      dscp: incoming 
      0 -  4 :   849303034            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            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         3517            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 :       45265            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            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 
      cos: incoming 
      0 -  4 :   849324148            0            0            0            0 
      5 -  7 :           0            0            0 
      cos: outgoing
      0 -  4 :       45265            0            0            0            0 
      5 -  7 :           0            0            0 
      output queues enqueued:
    queue:    threshold1   threshold2   threshold3
    queue 0:           0           0           0
    queue 1:       45265           0        4071
    queue 2:           0           0           0
    queue 3:           0           0  605666519
      output queues dropped:
    queue:    threshold1   threshold2   threshold3
    queue 0:           0           0           0
    queue 1:           0           0           0
    queue 2:           0           0           0
    queue 3:           0           0           0
    Policer: Inprofile:            0 OutofProfile:            0
    send:
    bm18.lan#sh mls q int gi0/10 st
    GigabitEthernet0/10 (All statistics are in packets)
      dscp: incoming 
      0 -  4 :   849303034            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            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         3517            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 :       45265            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            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 
      cos: incoming 
      0 -  4 :   849324148            0            0            0            0 
      5 -  7 :           0            0            0 
      cos: outgoing
      0 -  4 :       45265            0            0            0            0 
      5 -  7 :           0            0            0 
      output queues enqueued:
    queue:    threshold1   threshold2   threshold3
    queue 0:           0           0           0
    queue 1:       45265           0        4071
    queue 2:           0           0           0
    queue 3:           0           0  605666519
      output queues dropped:
    queue:    threshold1   threshold2   threshold3
    queue 0:           0           0           0
    queue 1:           0           0           0
    queue 2:           0           0           0
    queue 3:           0           0           0
    Policer: Inprofile:            0 OutofProfile:            0
    bm18.lan#
    bm18.lan#
    bm18.lan#
    bm18.lan#
    bm18.lan#
    bm18.lan#
    bm18.lan#
    bm18.lan#
    bm18.lan#
    bm18.lan#                     
    bm18.lan#
    bm18.lan#
    bm18.lan#
    bm18.lan#
    bm18.lan#clear mls qos int st
    bm18.lan#
    bm18.lan#
    bm18.lan#clear counters
    Clear "show interface" counters on all interfaces [confirm]
    bm18.lan#
    bm18.lan#
    bm18.lan#
    bm18.lan#sh mls qos int gi0/10 st   
    GigabitEthernet0/10 (All statistics are in packets)
      dscp: incoming 
      0 -  4 :     1141981            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            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            3            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 :          92            0            0            0            0 
      5 -  9 :           0            0            0            0            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            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 
      cos: incoming 
      0 -  4 :     1142010            0            0            0            0 
      5 -  7 :           0            0            0 
      cos: outgoing
      0 -  4 :          92            0            0            0            0 
      5 -  7 :           0            0            0 
      output queues enqueued:
    queue:    threshold1   threshold2   threshold3
    queue 0:           0           0           0
    queue 1:          92           0           5
    queue 2:           0           0           0
    queue 3:           0           0      810894
      output queues dropped:
    queue:    threshold1   threshold2   threshold3
    queue 0:           0           0           0
    queue 1:           0           0           0
    queue 2:           0           0           0
    queue 3:           0           0           0
    Policer: Inprofile:            0 OutofProfile:            0
    bm18.lan#
    bm18.lan#
    bm18.lan#sh int gi0/10
    GigabitEthernet0/10 is up, line protocol is up (connected)
      Hardware is Gigabit Ethernet, address is 0019.e7b1.c68a (bia 0019.e7b1.c68a)
      Description: IPTV
      MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 89/255
      Encapsulation ARPA, loopback not set
      Keepalive set (10 sec)
      Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
      input flow-control is off, output flow-control is unsupported
      ARP type: ARPA, ARP Timeout 04:00:00
      Last input 00:00:07, output 00:00:06, output hang never
      Last clearing of "show interface" counters 00:00:37
      Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: fifo
      Output queue: 0/40 (size/max)
      5 minute input rate 351051000 bits/sec, 32219 packets/sec
      5 minute output rate 0 bits/sec, 0 packets/sec
         1202212 packets input, 1637377057 bytes, 0 no buffer
         Received 1202205 broadcasts (1202205 multicasts)
         0 runts, 0 giants, 0 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
         0 watchdog, 1202205 multicast, 0 pause input
         0 input packets with dribble condition detected
        83 packets output, 6682 bytes, 0 underruns
         0 output errors, 0 collisions, 0 interface resets
         0 unknown protocol drops
         0 babbles, 0 late collision, 0 deferred
         0 lost carrier, 0 no carrier, 0 pause output
         0 output buffer failures, 0 output buffers swapped out
    bm18.lan#
    bm18.lan#
    Queue counter is reset to 0, and after 10-15 seconds I see 810,894 packets, although a sh Int gi0/10 I see only 83 outgoing packet!

  • Qos using priority queue drops

    I have following config for Qos.
    Basically Access-list match the voip/signalling traffic & put that in High queue. I am trying to figure without hight utilization why I am seeing output drops in high queue.
    7206#sh int s5/1/5:0
    Serial5/1/5:0 is up, line protocol is up
    Hardware is PA-MC-2T3+
    Description: T1
    Internet address is 172.17.133.105/30
    MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec,
    reliability 255/255, txload 24/255, rxload 23/255
    Encapsulation HDLC, crc 16, loopback not set
    Keepalive set (10 sec)
    Last input 00:00:06, output 00:00:00, output hang never
    Last clearing of "show interface" counters 01:58:03
    Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 1800
    Queueing strategy: priority-list 4
    Output queue (queue priority: size/max/drops):
    high: 0/20/1764, medium: 0/20/0, normal: 0/15/36, low: 0/15/0
    5 minute input rate 143000 bits/sec, 82 packets/sec
    5 minute output rate 145000 bits/sec, 83 packets/sec
    734269 packets input, 148368640 bytes, 0 no buffer
    Received 708 broadcasts, 0 runts, 0 giants, 0 throttles
    0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
    734855 packets output, 148838576 bytes, 0 underruns
    0 output errors, 0 collisions, 0 interface resets
    0 output buffer failures, 0 output buffers swapped out
    0 carrier transitions no alarm present
    Timeslot(s) Used: 1-24, subrate: 1536Kb/s, transmit delay is 0 flags
    non-inverted data
    ==============================================================================
    7200#sh run int s2/1/5:0
    Building configuration...
    Current configuration : 254 bytes
    interface Serial2/1/5:0
    description T1
    ip address x.x.x.x
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    no snmp trap link-status
    priority-group 4
    no cdp enable
    end
    ====================================================================================
    Define access-list to match voice/signalling traffic
    access-list 140 permit udp any any range 1024 1151
    access-list 140 permit udp any any range 16384 32767
    access-list 140 permit udp any any eq 2427
    access-list 140 permit udp any any eq 2429
    access-list 140 permit udp any any eq 5060
    priority-list 4 protocol ip high list 140
    priority-list 4 queue-limit 20 20 15 15

    Hi,
    your queue limit is 20 packets. This can explain the behaviour. If there are 20 packets in the queueing system waiting to be serviced any newly arriving packet will be dropped.
    Basically you can have drops in any queue in any queueing system if there is a permanent overload situation. There is no magic trick, if you f.e. permanently send 2 Mbps voip towards a T1. There will be drops.
    QoS does not create resources, it just distributes them among your important traffic classes.
    Besides this I also would suggest you to use class based queueing based on Modular QoS CLI (MQC). It is more flexible and precise than the old legacy methods like priority queueing, which you are using. On the other hand, if this is sufficient for you, why not.
    Regards, Martin

  • Input Queue drops

    Hi guys I am having lot of input queue drops on one of our remote router which has got an ipsec protected gre tunnel towards our main branch
     Input queue: 0/75/168173/8 (size/max/drops/flushes); Total output drops: 0
     Throttle count         37
     Drops         RP    1770332         SP          0
    This is the output of an interface connecting to ISP
    The other thing I would like to mention here is we have some users who connects via cisco vpn client to other sites over an already established ipsec/gre tunnel so would that be a reason of having drops?
    Do I need to alter the mtu for an additional gre overhead of second tunnel
    Currently tunnel interface settings are
    ip mtu 1476
    ip tcp adjust-mss 1380
    Many thanks

    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
    Input queue drops can be an indication of process switching (which is unable to keep up with what's offered).
    If it's just short bursts, increasing the input queue value might mitigate.
    Have you reviewed Cisco's documents for troubleshooting this?
    BTW, if your GRE tunnel is "protected", the MTU is likely too large as might also be your MSS adjust.
    If you're just doing GRE, your MSS adjust is too small.

  • ME 2600X input queue drops

    We have started to install ME2600X as access switch for FTTH
    Trunk ports are configured with rep and service instances
    These interfaces are facing Cat 4500X switches with rep edge ports. Northbound is a 6880X VSS and this is connected to the legacy network consisting of a couple of Cat6500 + loads of Catalyst switches
    We see loads of input queue drops in ME 2600X on the trunk interfaces. Even if I limit the allowed vlans out from the 4500X to the ME2600X the amount of dropped packets are still about half of the number of packets received on the interface.
    Captured traffic going out of the Cat4500X towards the ME 2600X showed mostly what I suspect is REP traffic. "Show mac traffic interface" show that all packers dropped are destined for "RP".
    We do not have clients on any ports yet so all traffic are inbound to the switch
    I need info and help troubleshooting this. What are the criteria for drops and how do I find what is dropped on this model?

    Config of REP port except the service instances
    interface TenGigabitEthernet0/45
     description TRAMAN-STH-02
     no ip address
     carrier-delay msec 200
     rep segment 1
     no keepalive
     soak link notification 10
     ip dhcp snooping trust
     l2protocol peer cdp lacp
     l2protocol forward stp vtp dtp pagp dot1x
    Here is an example of the amount of drops ver input
    Switch#show int te0/45
      Input queue: 0/75/337/0 (size/max/drops/flushes); Total output drops: 0
      5 minute input rate 59000 bits/sec, 10 packets/sec
    2659 packets input, 1976424 bytes, 0 no buffer
         Received 745 broadcasts (0 IP multicasts)
         0 runts, 0 giants, 0 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
         0 watchdog, 0 multicast, 0 pause input
    Switch#show int te0/45 summ
     *: interface is up
     IHQ: pkts in input hold queue     IQD: pkts dropped from input queue
     OHQ: pkts in output hold queue    OQD: pkts dropped from output queue
     RXBS: rx rate (bits/sec)          RXPS: rx rate (pkts/sec)
     TXBS: tx rate (bits/sec)          TXPS: tx rate (pkts/sec)
     TRTL: throttle count
      Interface                   IHQ       IQD       OHQ       OQD      RXBS      RXPS      TXBS      TXPS      TRTL
    * Te0/45                        0       533         0         0     64000        16      3000         3         0
    switch#show int te0/45 switching
    TenGigabitEthernet0/45 TRAMAN-STH-02
              Throttle count          0
                       Drops         RP    5491108         SP          0
                 SPD Flushes       Fast          0        SSE          0
                 SPD Aggress       Fast          0
                SPD Priority     Inputs          0      Drops          0
        Protocol  CDP
              Switching path    Pkts In   Chars In   Pkts Out  Chars Out
                     Process      17267    8029155      19179    7690779
                Cache misses          0          -          -          -
                        Fast          0          0          0          0
                   Auton/SSE          0          0          0          0
        Protocol  Other
              Switching path    Pkts In   Chars In   Pkts Out  Chars Out
                     Process          0          0    1150382  109509702
                Cache misses          0          -          -          -
                        Fast          0          0          0          0
                   Auton/SSE          0          0          0          0
        NOTE: all counts are cumulative and reset only after a reload.

  • Output packets drops on Router interface

    Hi,
    As shown in attached diagram we have connected DC and site with two ISP.
    RTR1 and RTR2 are in HSRP mode and RTR2 is active router for site
    We are seeing packet drops on DC RTR2 interfece connected to Sprint MPLS.
    We have a site with two isp (Sprint MPLS and P2P link). Site is running on Sprint ISP.
    We are seeing out put errors on DC RTR2 Sprint interface,  when we failover site to P2P link from sprint.
    And when fail over back to Sprint at site we are not seeing any output packets drops on DC RTR2 sprint link.
    MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
    reliability 255/255, txload 36/255, rxload 12/255
    Encapsulation ARPA, loopback not set
    Keepalive set (10 sec)
    Full-duplex, 100Mb/s, media type is RJ45
    output flow-control is XON, input flow-control is XON
    ARP type: ARPA, ARP Timeout 04:00:00
    Last input 00:00:00, output 00:00:00, output hang never
    Last clearing of "show interface" counters 1w0d
    Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 82137
    Queueing strategy: fifo
    Output queue: 0/40 (size/max)
    5 minute input rate 4722000 bits/sec, 1449 packets/sec
    5 minute output rate 14469000 bits/sec, 2088 packets/sec
    601690470 packets input, 1836920253 bytes, 0 no buffer
    Received 134822 broadcasts, 0 runts, 0 giants, 0 throttles
    0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
    0 watchdog, 134790 multicast, 0 pause input
    0 input packets with dribble condition detected
    858756749 packets output, 2658785694 bytes, 0 underruns
    0 output errors, 0 collisions, 0 interface resets
    0 unknown protocol drops
    0 babbles, 0 late collision, 0 deferred
    0 lost carrier, 0 no carrier, 0 pause output
    0 output buffer failures, 0 output buffers swapped out

    Sh int
     MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
         reliability 255/255, txload 36/255, rxload 12/255
      Encapsulation ARPA, loopback not set
      Keepalive set (10 sec)
      Full-duplex, 100Mb/s, media type is RJ45
      output flow-control is XON, input flow-control is XON
      ARP type: ARPA, ARP Timeout 04:00:00
      Last input 00:00:00, output 00:00:00, output hang never
      Last clearing of "show interface" counters 1w0d
      Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 82137
      Queueing strategy: fifo
      Output queue: 0/40 (size/max)
      5 minute input rate 4722000 bits/sec, 1449 packets/sec
      5 minute output rate 14469000 bits/sec, 2088 packets/sec
         601690470 packets input, 1836920253 bytes, 0 no buffer
         Received 134822 broadcasts, 0 runts, 0 giants, 0 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
         0 watchdog, 134790 multicast, 0 pause input
         0 input packets with dribble condition detected
         858756749 packets output, 2658785694 bytes, 0 underruns
         0 output errors, 0 collisions, 0 interface resets
         0 unknown protocol drops
         0 babbles, 0 late collision, 0 deferred
         0 lost carrier, 0 no carrier, 0 pause output
         0 output buffer failures, 0 output buffers swapped out

  • Calls in queue drop when first call is answered

     When all agents are busy and there are multiple calls in queue, at the point a call gets routed to an agent and answered from queue, the other calls in queue hear the disconnect prompt.
    This is CME 9.1 on  Version 15.0(1r)M16
    application
     service queue flash:app-b-acd-2.1.2.3.tcl
      param queue-len 30
      param aa-hunt1 7426701
      param queue-manager-debugs 1
      param number-of-hunt-grps 1
     service KCC flash:app-b-acd-aa-2.1.2.3.tcl
      paramspace english index 1
      param handoff-string KCC
      paramspace english language en
      param call-retry-timer 15
      param service-name queue
      param drop-through-option 1
      param second-greeting-time 60
      paramspace english location flash:
      param drop-through-prompt _TYFC.au
      param send-account true
      param max-time-vm-retry 3
      param voice-mail 1426900
      param max-time-call-retry 1400
      param aa-pilot 7427701
      param number-of-hunt-grps 1
    Thanks in advance.
    HHe

    Try this , see if that helps...
    param queue-len number
    Router(config-app-param)# param queue-len 15
    Sets the maximum number of calls allowed in each ephone hunt group's call queue used by Cisco Unified CME B-ACD.
    •number—Number of calls that can be waiting in the call queue for each ephone hunt group. The range is from 1 to 30. The default is 10.

  • Total output drops & dot1dBridgeEventsV2

    I am seen a lot of "Total output drops: " in the LAN/WAN Router, does any one have any documents that plains the cause of "Total output drops" and what it it's?
    Also I am getting a lot of traps in the LAN, but I can't find documents that explains the event, "dot1dBridgeEventsV2" Can you guys guide me to a document where it explains the events?
    Thanks

    Total output drops is the number of packets in the output queue that have been dropped because of a full queue. Check out the following link for troubleshooting input queue drops and output queue drops :
    http://www.cisco.com/warp/public/63/queue_drops.html

  • How do I track down QOS "Aggregate Drops" in a 6807-VSS switch?

    IOS = 15.1(2)SY1
    When I do a "show platform qos" everything looks good except for this:
     ----- Switch [1], Module [3] -----
                     Counter                  IFE Pkts        IFE Bytes                 OFE Pkts           OFE Bytes
              Policing Drops        0                         0                                216304              16888896     
           Policing Forwards     2935238201     5068976519092     2949830653     5069751062945
    Police-hi Actions (Lvl3)    0                         0                                0                          0            
    Police-lo Actions (Lvl2)    0                         0                                0                          0            
             Aggregate Drops    0                         0                                263889               16888896     
          Aggregate Forwards 2935238198     5068976518864     2949830650      5069751062717
    Any idea if these drops are QOS related and/or how to get more information about them in order to troubleshoot?  OFE means 'Output Forwarding Engine'.   There are no input or output queue drops on any of the interfaces doing a "show interface gx/x/x."
    Thanks.

    Aggregate drops is just a total of drops from all the different internal processes.  The OFE Bytes matches the policing drops.  I'd assume policing is what caused these drops.  The packet number difference may be due to fragmentation.

  • Weighted fair queue question

    when i configure WFQ on an interface, i see a parameter called available bandwidth on the sh interface command which is less than the actual interface bandwidth. And if the traffic exceeds the available bandwidth then will result in output queue drops.
    also i found that changing the interface bandwidth to any arbitrary value changes these parameters as well. ( eg. if i ahve a 1 MB interface and i configure the bandwidht statement as 10 MB, the available bandwidth shows around 8MB) . will it mean then, it will not show drops till the traffic exceeds 8 MB.
    please make me understand how this is calculated and how does it affect the interface parameters like queuing etc.

    Hello,
    in case you use WFQ configured on an interface, the configured "bandwidth" has no influence on the queueing behaviour. Software based queueing (like WFQ in a router) will be involved, when the hardware queue is full, i.e. when there is more traffic than the interface can send at the time. You can never send more traffic than the layer1 clock rate allows you to send - no matter what you configure with the interface command "bandwidth".
    In case you configure CBWFQ through a policy-map, then the configured interface "bandwidth" is used to calculate the bandwidth per class within percent based CBWFQ. Again this will only make sense if you adjust the interface "bandwidth" to the clock rate.
    Hope tis helps! Please rate all posts.
    Regards, Martin

  • Catalyst 2960-S Stack Interface Packet Drop

    Hi all!
    I have a 2960-S stack with the following behavior:
    SWITCH#sh int g1/0/26
         Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 12275
    When I issue the show mls qos interface g1/0/26 statistics:
    SWITCH#show mls qos interface g1/0/26 statistics
    GigabitEthernet1/0/26 (All statistics are in packets)
      dscp: incoming 
      0 -  4 :    35356866        0            0            0            0 
      5 -  9 :            0            0            0            2            0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            0            0            0            0 
    20 - 24 :           0            0            0            0            0 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0            0            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :      634354        0            0            0            0 
    45 - 49 :           0     49446819      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 :     6835883         0            0            0            0 
      5 -  9 :            0             0            0     43973612      0 
    10 - 14 :           0            0            0            0            0 
    15 - 19 :           0            1            0            0            0 
    20 - 24 :           0            0            0            0       204586 
    25 - 29 :           0            0            0            0            0 
    30 - 34 :           0            0            0            0            0 
    35 - 39 :           0            0            0            0            0 
    40 - 44 :           2            0            0            0            0 
    45 - 49 :           0      2215325       0           55            0 
    50 - 54 :           0            0            0            0            0 
    55 - 59 :           0        29668         0            0            0 
    60 - 64 :           0            0            0            0           
      cos: incoming 
      0 -  4 :    35374153            2            0            0            0 
      5 -  7 :    50121685            0            0 
      cos: outgoing
      0 -  4 :    12975602     43973617        85081       204622          122 
      5 -  7 :    47659950          105     34377016 
      output queues enqueued:
    queue:    threshold1   threshold2   threshold3
    queue 0:           0           0    47659935
    queue 1:       92482     1222278    34432039
    queue 2:           0           0    13178400
    queue 3:           0           0    43982889
      output queues dropped:
    queue:    threshold1   threshold2   threshold3
    queue 0:           0           0          71
    queue 1:           0        1738           0
    queue 2:           0           0          20
    queue 3:           0           0      375553
    Policer: Inprofile:            0 OutofProfile:            0
    I need some help to read this output but it seems that packets are dropped at all queues, isn't it?
    Any help please?
    Thanks in advance!

    Please post the output to the following commands:
    1.  sh interface G1/0/26; and
    2.  sh controll e G1/0/26
    What kind of client is connected to port Gi1/0/26?

  • Output Dropps

    Hi,
    i have a 3750 with 12.2.55SE7 and he has some output queue 3 dropps at threashold 3. As far as i remember the threshold three is a static parameter on the switch. In fact that there is only a telephone located at this port it is not easy to explain those dropps. We also noticed some retransmissions at the telephone so i need to find out if they match the dropps.
    Here are some outputs:
    Q1/Q0 ist a Prio queue, Q2 for Best Efford, Q3 for signalling in this case
      output queues enqueued:
    queue:    threshold1   threshold2   threshold3
    queue 0:           0           0           388077
    queue 1:      147456      123815     2572166
    queue 2:           0           0           333504
    queue 3:           0           0           176711
      output queues dropped:
    queue:    threshold1   threshold2   threshold3
    queue 0:           0           0           0
    queue 1:           0           0           0
    queue 2:           0           0          13
    queue 3:           0           0           0
    #sh mls qos int gi x/x/x queueing
    GigabitEthernetx/x/x
    Egress Priority Queue : enabled
    Shaped queue weights (absolute) :  25 0 0 0
    Shared queue weights  :  1 30 35 5
    The port bandwidth limit : 100  (Operational Bandwidth:100.0)
    The port is mapped to qset : 1
    So the mapping of the dscp to queues is not relevant here because we talk only of a phone - so someone have any suggestion what causes this T3 @ Q3 (q2 in the output) causing to dropp packets on a phoneport ?
    Many Thanks !

    I would say that 13 drops is not very many at all.  I do notice they are on Q2, whereas you say that your voice is on Q1 and your signalling on Q3.  I would therefore be searching for bursty background traffic, possibly on the access VLAN rather than the voice VLAN.  Do all the phone ports show these drops?  How is the access port configured ... do you have access VLAN and voice VLAN?
    Kevin Dorrell
    Luxembourg

  • Underruns and output buffer failures

    Hi
    I have two Catalyst 3550 connecting two datacenter and I'm receiving errors on connecting switchports. Errors are output buffer failures and underruns. Is it just that switches are running out of resources or what? We are using servers in the datacenters with nfs and I'v heard that this could cause these errors. I'd really appreciate a opinion from a network professional.
    Here are port statistics. Both switchports are identical.
    FastEthernet0/3 is up, line protocol is up
    Hardware is Fast Ethernet, address is 000c.301f.c503 (bia 000c.301f.c503)
    MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
    reliability 255/255, txload 3/255, rxload 6/255
    Encapsulation ARPA, loopback not set
    Keepalive set (10 sec)
    Full-duplex, 100Mb/s
    input flow-control is off, output flow-control is off
    ARP type: ARPA, ARP Timeout 04:00:00
    Last input 00:00:00, output 00:00:00, output hang never
    Last clearing of "show interface" counters 21:54:22
    Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
    Queueing strategy: fifo
    Output queue :0/40 (size/max)
    1 minute input rate 2676000 bits/sec, 531 packets/sec
    1 minute output rate 1432000 bits/sec, 528 packets/sec
    123525330 packets input, 166317380 bytes, 0 no buffer
    Received 887720 broadcasts, 0 runts, 0 giants, 0 throttles
    0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
    0 watchdog, 671127 multicast, 0 pause input
    0 input packets with dribble condition detected
    108650060 packets output, 322356071 bytes, 11269 underruns
    0 output errors, 0 collisions, 0 interface resets
    0 babbles, 0 late collision, 0 deferred
    0 lost carrier, 0 no carrier, 0 PAUSE output
    11269 output buffer failures, 0 output buffers swapped out
    Thanks

    Hello,
    most likely, the erros are caused by your link being saturated.
    I found a previous post which explains the error as following:
    'The frames are being switched in hardware, since there are no output queue drops. But the hardware is attempting to put frames on the wire when it's pretty close to being saturated. Although your 1 minute average is only around 1,5 mbit, it only takes a couple millisecond long burst to fill up the hardware interface buffers and cause this error. It's probably time to add another link (forming an etherchannel) or jump to a gig interface. I don't think you can tune these hardware buffers at all to buy any additional time.'
    Conclusion: your link is getting overloaded...
    Regards,
    GP

Maybe you are looking for

  • Locks and Isolation Levels

    Hello, I'm new to the Oracle environment and have just started using PL/SQL on Oracle 8i. Where can I find info on how Oracle locks data and how transaction isolation levels are used? We've still not recvd our manuals so please any replies referring

  • Why is one iphone displaying the text messages of the other 2 iphones in my house?

    Why is one iphone displaying the text messages of the other 2 iphones in my house?

  • The AppStore just doesn't download apps

    When I try to download apps a grey icon appears on the screen but nothing is downloading

  • Labwindows cvi 2010 sp1 Device drivers

    Hi all   I am trying to install cvi 2010 sp1 and it is asking for the Device Drivers for the program, where can I find the drivers for the sp1. To finish installing I have some older drivers but what is the latest for sp1 Thanks in advance

  • XP Embedded updates

    We built several dozen systems using Windows XP Embedded SP3.  We downloaded updates from the Microsoft Embedded Download Center but when we try to apply the updates that are post April 2014 we get the message "wrong version of Windows".  One of our