https://community.hpe.com/t5/switches-hubs-and-modems/fcs-rx-errors/m-p/3475883#M4515 Normally you would expect to see FCS RX errors on a full duplex link that was talking to to a half duplex link. What usually happens is the full duplex side talks anytime it want to but if the Half Duplex side is transmitting when the full side starts talking then the half side stops talking immediately in mid frame if need be. The result is that the full side receives a packet that is incomplete and thus has a frame check sum error. In your case we are looking at the half side so it should not get these errors unless there is a noisy cable or bad port somewhere. Are you sure that the FCS RX errors are current and not left over from some earlier time when the port might have been set to Full? Try clearing the counters and see if they come back.<BR /><BR />In any event it is not a major problem when you look at the percent of errors to total packets so watchful waiting is probably the best policy.<BR /><BR />Ron Tue, 01 Feb 2005 19:33:35 GMT Ron Kinner 2005-02-01T19:33:35Z https://community.hpe.com/t5/switches-hubs-and-modems/fcs-rx-errors/m-p/3475882#M4514 I have an ethernet gateway device (for secure entry system) connected to a port on a ProCurve 4000 which is showing a number of FCS Rx errors. I don't know if I should be concerned about it or not. The port is set to Auto, and running at 10 mb half duplex.<BR /><BR />Here are the port stats:<BR /><BR />Status and Counters - Port Counters - A2<BR />Link Status : Up <BR /><BR />Bytes Rx : 1,326,816,580 Bytes Tx : 3,778,092,352 <BR />Unicast Rx : 7,123,967 Unicast Tx : 7,984,674 <BR />Bcast/Mcast Rx : 6794 Bcast/Mcast Tx : 31,234,002 <BR /><BR />FCS Rx : 916 Drops Tx : 0 <BR />Alignment Rx : 0 Collisions Tx : 176 <BR />Runts Rx : 0 Late Colln Tx : 0 <BR />Giants Rx : 0 Excessive Colln : 0 <BR />Total Rx Errors : 916 Deferred Tx : 1633 <BR /><BR /><BR />Is there an issue that merits more investigation? Tue, 01 Feb 2005 11:08:31 GMT https://community.hpe.com/t5/switches-hubs-and-modems/fcs-rx-errors/m-p/3475882#M4514 Michael Tibbs 2005-02-01T11:08:31Z https://community.hpe.com/t5/switches-hubs-and-modems/fcs-rx-errors/m-p/3475883#M4515 Normally you would expect to see FCS RX errors on a full duplex link that was talking to to a half duplex link. What usually happens is the full duplex side talks anytime it want to but if the Half Duplex side is transmitting when the full side starts talking then the half side stops talking immediately in mid frame if need be. The result is that the full side receives a packet that is incomplete and thus has a frame check sum error. In your case we are looking at the half side so it should not get these errors unless there is a noisy cable or bad port somewhere. Are you sure that the FCS RX errors are current and not left over from some earlier time when the port might have been set to Full? Try clearing the counters and see if they come back.<BR /><BR />In any event it is not a major problem when you look at the percent of errors to total packets so watchful waiting is probably the best policy.<BR /><BR />Ron Tue, 01 Feb 2005 19:33:35 GMT https://community.hpe.com/t5/switches-hubs-and-modems/fcs-rx-errors/m-p/3475883#M4515 Ron Kinner 2005-02-01T19:33:35Z