cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
787
Views
0
Helpful
5
Replies

Output Drops Value - Rare Variation

cesacal
Level 1
Level 1

Hi All,

 

I´m suffering on a  WS-C3750X-48 (IOS c3750e-universalk9-mz.122-58.SE2.bin) output drops on an interface.

I think that is due to high load on the interface.

 

However, this is not my problem, the problem is that the value of output drops makes very rare fluctuations.

Below I paste the command output "show int gi1/0/7" executed two times in the same second:


SW_X_CIC#sh int gi1/0/7
GigabitEthernet1/0/7 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is a44c.1122.8d87 (bia a44c.1122.8d87)
Description: FWA-ESN-P3-TRUNK
MTU 1500 bytes, BW 1000000 Kbit/sec, 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 6y46w, output 00:00:00, output hang never
Last clearing of "show interface" counters 00:28:04
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 310051351
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 14000 bits/sec, 24 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 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
40320 packets output, 3065104 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
SW_X_CIC#sh int gi1/0/7
GigabitEthernet1/0/7 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is a44c.1122.8d87 (bia a44c.1122.8d87)
Description: FWA-ESN-P3-TRUNK
MTU 1500 bytes, BW 1000000 Kbit/sec, 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 6y46w, output 00:00:00, output hang never
Last clearing of "show interface" counters 00:28:05
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 0 bits/sec, 0 packets/sec
5 minute output rate 13000 bits/sec, 23 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 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
40366 packets output, 3068499 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

 

Anyone suffering this problem?

How can I correct this problem?

 

Another questions, the value "Total Output drops" from "show int gix/x" is the same as the value "OutDiscards" on the command "show int gix/x counter errors"?

5 Replies 5

marce1000
VIP
VIP

 

 https://www.cisco.com/c/en/us/support/docs/routers/10000-series-routers/6343-queue-drops.html

 M.



-- ' 'Good body every evening' ' this sentence was once spotted on a logo at the entrance of a Weight Watchers Club !

Thanks for your help, but I don´t need to troubleshoot the "output drops", I need to know why in the same second I see such a huge difference in the value.

I recall the 12.2(58) train being buggy, especially the earlier versions.

Try installing the latest version of the same train, or if you don't need (58) features, try the latest version of the (55) train.

I´ll try updating the IOS ASAP, but is this issue a known bug? Do you remind the bug code?

It may be a known bug, but for such an early release (i.e. an SE2), that alone probably merits an upgrade.

If you have a support contract (which I don't), you may be allowed to search for a known bug.
Review Cisco Networking products for a $25 gift card