AXISHK
asked on
Interface statistic on Cisco switch
An interface on a Cisco switch show Total Output drops is 776, txload 4/255. What does it indicates ? Does it tell something wrong for the cable or the device connecting to the switch ? How to improve this situation ?
Thx
---
GigabitEthernet1/0/14 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 381c.xxxx.xxxx (bia 381c.xxxx.xxxx)
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 4/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/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 never, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 776
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 44000 bits/sec, 73 packets/sec
5 minute output rate 1821000 bits/sec, 152 packets/sec
3457773 packets input, 964760961 bytes, 0 no buffer
Received 31107 broadcasts (19813 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 19814 multicast, 0 pause input
0 input packets with dribble condition detected
4206341 packets output, 4232934589 bytes, 0 underruns
0 output errors, 0 collisions, 1 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
Thx
---
GigabitEthernet1/0/14 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 381c.xxxx.xxxx (bia 381c.xxxx.xxxx)
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 4/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/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 never, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 776
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 44000 bits/sec, 73 packets/sec
5 minute output rate 1821000 bits/sec, 152 packets/sec
3457773 packets input, 964760961 bytes, 0 no buffer
Received 31107 broadcasts (19813 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 19814 multicast, 0 pause input
0 input packets with dribble condition detected
4206341 packets output, 4232934589 bytes, 0 underruns
0 output errors, 0 collisions, 1 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
ASKER
"Output drop" - is it the packet sending out from the interface to the device (Wifi AP in my case) ?
Will there be a possibility that there is something wrong on the device (ie Wifi AP) ?
For 1821000 bits/sec, is it equivalent to 1.8Gb/s which exceed the interface througout of 100Mb/s ?
Thx
Will there be a possibility that there is something wrong on the device (ie Wifi AP) ?
For 1821000 bits/sec, is it equivalent to 1.8Gb/s which exceed the interface througout of 100Mb/s ?
Thx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thx
You're welcome.
4/255 Tx is measure of how utilized is link that is sending traffic (4/255 = 1.5686275%).
5 minute output rate 1821000 bits/sec, 152 packets/sec
255/255 - would mean that output is completely utilized (saturated).
Other than increasing line speed, Weighted Random Early Detection (WRED/DWRED) can be configured to drop some amount TCP packets randomly before interface starts to be congested.
Configuring bigger buffer is not recommended when interfaces are saturated.