Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

procurve drops Tx at 100,000 plus

Walla
Occasional Visitor

procurve drops Tx at 100,000 plus

what is it that can cause many drops but no errors and none on the Receive Tx?
ProCurve J8773A Switch 4208vl
Software revision L.10.23
Like this :
Port Total Bytes Total Frames Errors Rx Drops Tx Ctrl
----- ------------ ------------ ------------ ------------ -----
A1 963,718,980 189,756,750 1 9,119,520 off
8 REPLIES
cenk sasmaztin
Honored Contributor

Re: procurve drops Tx at 100,000 plus

please send me
(sh int A1) commad print
cenk

Walla
Occasional Visitor

Re: procurve drops Tx at 100,000 plus

hi there here it is. thanks
Status and Counters - Port Counters for port A1

Name :
Link Status : Up
Totals (Since boot or last clear) :
Bytes Rx : 3,255,967,027 Bytes Tx : 2,076,932,449
Unicast Rx : 35,983,105 Unicast Tx : 39,999,204
Bcast/Mcast Rx : 601,825 Bcast/Mcast Tx : 113,390,502
Errors (Since boot or last clear) :
FCS Rx : 1 Drops Tx : 9,170,184
Alignment Rx : 0 Collisions Tx : 404,947
Runts Rx : 0 Late Colln Tx : 355,424
Giants Rx : 0 Excessive Colln : 0
Total Rx Errors : 1 Deferred Tx : 0
Rates (5 minute weighted average) :
Total Rx (bps) : 106776 Total Tx (bps) : 5001016
Unicast Rx (Pkts/sec) : 0 Unicast Tx (Pkts/sec) : 0
B/Mcast Rx (Pkts/sec) : 0 B/Mcast Tx (Pkts/sec) : 0
Utilization Rx : 00.01 % Utilization Tx : 00.50 %
Richard Brodie_1
Honored Contributor

Re: procurve drops Tx at 100,000 plus

You have many late collisions; that's very bad. And you have collisions but no deferrals, that's odd. Finally you have a high data rate but no actual packets being sent: that makes no sense at all.

One thing that can cause late collisions is a duplex mismatch. It would be helpful to know what the port looks like in show int brief; also what the interface statistics look like at the remote end.
cenk sasmaztin
Honored Contributor

Re: procurve drops Tx at 100,000 plus

hi Walla
I can't see any brust bandwith on port
but I can see many collision on port


Utilization Rx : 00.01 % Utilization Tx : 00.50 %


Collisions Tx : 404,947
Late Colln Tx : 355,424

drop causeses

bandwith brust
or
transport layer 4 udp and tcp protocols

udp protocol not include unknowledgement if packet not reachable destination
drop on network.

tcp include unknowledgement some time occur brust on port and occur congestion
tcp retransmit fault packet but tcp running round-trip time period

RTT to
detect congestion trend. This big burst of traffic plus
existing cross traffic will exceed the bottleneck link switch port
queue and cause up to 50% packet loss


My advice
enable flow control on port

(eth-A1)# flow-control


check int A1 on device and check cable connection

this device must be standart network device

include
802.1
802.1u
may be 802.3ab standarts

and

this device have network cable must be true installation whit true component
may be make your test on cable

neer and crosstalk test
far end crosstalk test
return loss test
propagation delay test



good luck
cenk

Walla
Occasional Visitor

Re: procurve drops Tx at 100,000 plus

Thanks Fellas! This port is one of about 20 on this switch that looks similar to this. These are workstations and laptops. they are set to auto/auto
cenk sasmaztin
Honored Contributor

Re: procurve drops Tx at 100,000 plus

and you make set two device (switch and pc )
same speed
for example

100 base full
cenk

Walla
Occasional Visitor

Re: procurve drops Tx at 100,000 plus

Thanks.
I had checked the spped and du[plex setting already and they are matched. 100/full.
cenk sasmaztin
Honored Contributor

Re: procurve drops Tx at 100,000 plus

and must be enable flow control on port

My advice
enable flow control on port

(eth-A1)# flow-control
cenk