interface output drop 6509E

[Muhammad Qasim]

Hi Mates,

i am very new in this business i am facing this issue in my network just for one up link

GigabitEthernet1/11 is up, line protocol is up (connected)
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 92813570
Received 48732930 broadcasts (20452735 multicasts)

interface GigabitEthernet1/11
description uplink to New Admin
switchport
switchport mode trunk
load-interval 30
end

#sh interfaces GigabitEthernet1/11
GigabitEthernet1/11 is up, line protocol is up (connected)
Hardware is C6k 1000Mb 802.3, address is a0ec.f942.b9ca (bia a0ec.f942.b9ca)
Description: uplink to New Admin
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 231/255, rxload 25/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is 1000BaseLH
input flow-control is off, output flow-control is off
Clock mode is auto
ARP type: ARPA, ARP Timeout 04:00:00
Last input 18w3d, output never, output hang never
Last clearing of "show interface" counters 3w4d
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 92825911
Queueing strategy: fifo
Output queue: 0/40 (size/max)
30 second input rate 100681000 bits/sec, 43536 packets/sec
30 second output rate 905960000 bits/sec, 91734 packets/sec
82005420923 packets input, 16757895840274 bytes, 0 no buffer
Received 48734538 broadcasts (20453570 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
0 input packets with dribble condition detected
183943958031 packets output, 226872805068163 bytes, 0 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
0 output buffer failures, 0 output buffers swapped out

[marce1000 · Accepted solution]

 - Check this document https://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/24053-193.html
              ( and or look for drop with find in the browser)

 M.

[Joseph W. Doherty]

reliability 255/255, txload 231/255, rxload 25/255
30 second output rate 905,960,000 bits/sec, 91734 packets/sec

If the above stats are correct, just looks like your interface is rather "busy" and drops would normally be expected.

Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 92825911
183943958031 packets output, 226872805068163 bytes, 0 underruns

92825911 / (92825911 + 183943958031)  * 100 = 0.05% overall drop

An actual drop rate of .05% should go unnoticed, but that's the overall loss percentage for almost 4 weeks.  What would be interesting is your loss percentage during much, much shorter time periods (like per minute or less).

Anyone describing network performance issues?

[Muhammad Qasim]

just facing slowness it spreading now all over the network but this uplink is facing issues with slowness. facing issue with management vlan slowness 

Reply from 172.21.1.1: bytes=32 time=1ms TTL=255
Reply from 172.21.1.1: bytes=32 time=1ms TTL=255
Reply from 172.21.1.1: bytes=32 time=76ms TTL=255
Reply from 172.21.1.1: bytes=32 time=1ms TTL=255
Reply from 172.21.1.1: bytes=32 time<1ms TTL=255
Reply from 172.21.1.1: bytes=32 time<1ms TTL=255
Reply from 172.21.1.1: bytes=32 time=2ms TTL=255
Reply from 172.21.1.1: bytes=32 time=2ms TTL=255
Reply from 172.21.1.1: bytes=32 time<1ms TTL=255
Reply from 172.21.1.1: bytes=32 time<1ms TTL=255
Reply from 172.21.1.1: bytes=32 time<1ms TTL=255
Reply from 172.21.1.1: bytes=32 time<1ms TTL=255
Reply from 172.21.1.1: bytes=32 time=100ms TTL=255
Reply from 172.21.1.1: bytes=32 time<1ms TTL=255

[Joseph W. Doherty]

A side effect of queued traffic is queuing latency.

So, possibly those spikes in ping times might be due to transient congestion.  (Also not knowing what you are pinging, far host might have busy bouts and delays response.)

Two approaches to insufficient bandwidth.

1) Increase bandwidth.

2) Manage bandwidth.

The two approaches are not mutually exclusive.

[Muhammad Qasim]

i am trying to ping core 6509E through management Vlan. how can i get out of it 

[Joseph W. Doherty]

Sorry, "how can i get out of it" is unclear, to me.

[MHM Cisco World]

Can you traceroute 172.21.1.1

share result here 

[Muhammad Qasim]

tracert 172.21.1.1

Tracing route to 172.21.1.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 172.21.1.1

Trace complete.