GigabitEthernet4/0/5 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is d0c2.829f.9805 (bia d0c2.829f.9805)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/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 20:25:52, output 00:00:18, output hang never
Last clearing of "show interface" counters 21:19:55
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 97661
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 10000 bits/sec, 6 packets/sec
5 minute output rate 133000 bits/sec, 159 packets/sec
237192 packets input, 45850775 bytes, 0 no buffer
Received 3616 broadcasts (1218 multicasts)
0 runts, 0 giants, 0 throttles
1 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 1218 multicast, 0 pause input
0 input packets with dribble condition detected
2004530 packets output, 304690608 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
I recommend clearing the interface counters and then observing the number of drops over the next hour
can you do : clear counter GigabitEthernet4/0/5
chane the speed and duplex setting and then check it.
Output drops typically indicate a congested interface. This can occur when going from a high speed interface (such as the SW B to SW C link at 1000Mbps) to a lower speed link (SW A to SW B at 100Mbps).
Output drops are not all bad, as the drops indicate the flow control mechanisms of the upper layer protocols are working to decrease the TCP window size. Also, if the drops are due to a constant high-rate flow of traffic you cannot prevent them, but you can control them.
Regards
