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

High collision

High collision

Hi!

I got this error on alot of edge-ports. What could be wrong? Cable ? Auto-mdix/mdi ?
Both 2626/2810.

I 01/16/09 06:51:25 ports: port 2 is now on-line
I 01/16/09 07:34:51 ports: port 24 is Blocked by STP
I 01/16/09 07:34:52 ports: port 24 is now off-line
I 01/16/09 07:34:55 ports: port 24 is Blocked by STP
I 01/16/09 07:34:57 ports: port 24 is now on-line
W 01/16/09 07:35:14 FFI: port 24-Excessive CRC/alignment errors. See help.
I 01/16/09 07:35:35 ports: port 24 is now off-line
I 01/16/09 07:35:38 ports: port 24 is Blocked by STP
I 01/16/09 07:35:41 ports: port 24 is now on-line
W 01/16/09 07:35:58 FFI: port 24-Excessive CRC/alignment errors. See help.
I 01/16/09 07:46:10 ports: port 44 is Blocked by STP
I 01/16/09 07:46:12 ports: port 44 is now on-line



/Magnus
7 REPLIES
cenk sasmaztin
Honored Contributor

Re: High collision

hi Magnus
which type cable connect between switch
utp or fiber

if use fiber optical cable between switches

*which type fiber cable (multimode or single mode)
*how many meters this cable and which one use fiber module(sx,lx,fx)

if use utp cable between switch
how many meters this cable

good luck
cenk

Re: High collision

It´s edge-ports that have this error, so it´s UTP-cables. It seems like we got this error when people connect their computers to the network.

/Magnus
cenk sasmaztin
Honored Contributor

Re: High collision

Magnus

cyclic redundancy check (CRC)
check in frame cary data

this port lose some data (in frame )

check port speed, port speed must be same ratio
for example each port must be 100 full or 1000 full

check utp cable, may be retermination utp cable socked

this eror cause generally non standart nic or cable problem

cenk
cenk

Re: High collision

Ok, is this probably the same error?

I 01/16/09 17:11:20 ports: port 32 is now off-line
I 01/16/09 17:11:22 ports: port 32 is Blocked by STP
I 01/16/09 17:11:23 ports: port 32 is now off-line
I 01/16/09 17:12:01 ports: port 4 is Blocked by STP
I 01/16/09 17:12:04 ports: port 4 is now on-line
W 01/16/09 17:12:12 FFI: port 4-Excessive undersized/giant packets. See help.
W 01/16/09 17:12:12 FFI: port 4-Excessive CRC/alignment errors. See help.
I 01/16/09 17:12:19 ports: port 22 is now off-line
I 01/16/09 17:12:21 ports: port 22 is Blocked by STP
I 01/16/09 17:12:24 ports: port 22 is now on-line
I 01/16/09 17:14:32 mgr: SME TELNET from 10.46.2.250 - MANAGER Mode

/Magnus
cenk sasmaztin
Honored Contributor

Re: High collision

hi Magnus
each ethernet frame must be 64 byte between 1500 byte this range very importand for good ethernet communication

if one frame capsule excessive or small size we can see this eror
-Excessive undersized/giant packets. See help.

as for me you make connect nonstandart nıc on this port may be hub or nonstandart nic

cenk



cenk

cenk sasmaztin
Honored Contributor

Re: High collision

Magnus please connect your switch web interface
and double clik on eror
cenk

Boxx
Occasional Visitor

Re: High collision

Hello Magnus

With approx. 200 HP switches we experiense errors quite often. Somtimes these online/offline STP incidents causes Excessive CRC and/or Late collisions - as you experiense, but often they "just happens" without any visible/measurable result. We have several ports jumping up and down all day long causing no errors (read: traps).

Possible solution :
In some cases we configured the switchport (speed) to "Auto" and forced the client to either 100 Full Duplex og 100 Half Duplex.

With Canon copiers and HP Laserjet 2700 (remember to update to latest firmware) it mostly reduce the problem, but in most cases there is no change at all.

We suspect out customers cabling to be corruptet in some degree. Therefore we have ordered a cabeltester than can messure the quality of the (physical) cabeling from endpoint to endpoint.