12-05-2011 10:00 AM - edited 03-07-2019 03:44 AM
Hi,
I was wondering what could be a cause for the input queue drops and flushes number to be the same. If you have any commands I can run to do some troubleshooting that would be great. Thanks
Full-duplex, 1000Mb/s, media type is SX
input flow-control is off, output flow-control is off
Clock mode is auto
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 4d21h
Input queue: 0/75/29981/29981 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
12-05-2011 10:10 AM
Hi,
input queue drops might indicate different problems depending on port configuration and other variable.
Can you attache the whole output show interface x/x for us to see other important info to correlate with the input drops.
Also, do you see the drops on this port only or in others?
What about svi's do you see drops on those too?
How fast do the drop increment? Do you see a linear increment or in burts?
Besides drops and flushes do you see other counters increasing?
Riccardo
12-05-2011 10:19 AM
Show interface whole output
GigabitEthernet9/1 is up, line protocol is up (connected)
Hardware is C6k 1000Mb 802.3, address is 001a.e31a.90c0 (bia 001a.e31a.90c0)
Description: LAN connection
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 1., loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is SX
input flow-control is off, output flow-control is off
Clock mode is auto
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 4d21h
Input queue: 0/75/29981/29981 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
30 second input rate 13000 bits/sec, 14 packets/sec
30 second output rate 3000 bits/sec, 5 packets/sec
L2 Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes
L3 in Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes mcast
L3 out Switched: ucast: 0 pkt, 0 bytes mcast: 0 pkt, 0 bytes
4330076 packets input, 385044258 bytes, 0 no buffer
Received 4207059 broadcasts (499570 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
0 input packets with dribble condition detected
2052579 packets output, 151433237 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
Also, do you see the drops on this port only or in others? Only this port
What about svi's do you see drops on those too? I do not see any drops on the svi
How fast do the drop increment? Do you see a linear increment or in burts? The drops look to be burst such as 5 or 10 in a period of time
12-05-2011 11:14 AM
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
Might be SPD random drops or buffer failures.
Since you're running at gig, you might also just first try increasing the size of your input queue.
12-05-2011 12:59 PM
I am afraid that those are not SPD drops as Gi9/1 is a L2 port and on L2 interfaces input drops/flushes have a different meaning as this traffic is not destined to the RP.
On L2 ports input drops might indicat fabric related drops (fabric flow control) which on releases after CSCsk83524 are also indicated by overruns, or physical buffers problem (oversubriscption).
To narrow this down can you send
show version
show module
show run int g9/1
show interfaces | include line protocol is|Input queue| rate
Riccardo
12-06-2011 05:46 AM
So I decided to replace the media from fiber to cat5e cable, drops seem to clear up. Thanks for your help.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide