03311 High Collisions or Drop rate - All switches

[alexxx86]

Hello,

we have exactly the same problem. Every morning to the same time we get an High Collision or Drop Rate on port XX message. But on the 100 mbit ports only - the gbit ports don't show the message. The switch is a ProCurve 2848 with the newest FW I.10.105.

I have monitored one of the effected ports and sniffed the traffic with wireshark. But i cant see any problem on this port at the reported time.

Also the port counters of an effected port seems to be ok:

 Status and Counters - Port Counters for port 26

  Name  :
  Link Status     : Up
  Totals (Since boot or last clear) :
   Bytes Rx        : 119,570,028        Bytes Tx        : 3,454,585,510
   Unicast Rx      : 754,251               Unicast Tx      : 4,996,036
   Bcast/Mcast Rx  : 5518               Bcast/Mcast Tx  : 12,697,686
  Errors (Since boot or last clear) :
   FCS Rx          : 0                  Drops Rx        : 0
   Alignment Rx    : 0                  Collisions Tx   : 0
   Runts Rx        : 0                  Late Colln Tx   : 0
   Giants Rx       : 0                  Excessive Colln : 0
   Total Rx Errors : 0                  Deferred Tx     : 0
  Rates (5 minute weighted average) :
   Total Rx  (bps) : 24584              Total Tx  (bps) : 508736
   Unicast Rx (Pkts/sec) : 0            Unicast Tx (Pkts/sec) : 0
   B/Mcast Rx (Pkts/sec) : 0            B/Mcast Tx (Pkts/sec) : 9
   Utilization Rx  : 00.02 %            Utilization Tx  : 00.50 %

Any idea ?!

[kkpro]

That's a bit strange, because error counters are all zeroes. Here we have huge number of errors on 100Mbit ports.

HP guy called me (suprisingly) one more time and said we must to introduce flow control on problem ports.

I do not want to do this because flow control could lead to another sort of problems.

[alex-weis]

Hey there,

we got the same problems. I found out that these problems (in our environemt) came from the HP NetAdmin Printer Monitoring Tool from HP. The tool is scanning the network for HP printers... After deinstalling the tool the error went away.