10-03-2012 01:58 PM - edited 03-07-2019 09:15 AM
Hi,
I am not sure why the CRC and input errors are increasing in fastethernet port...This port is used as Intradomain cross connect to Data Center service provider for LAN extension between two Data Centers in different locations... The link is 100 MB. The switch port is directly connected to patch panel of DC provider and I believe they have some L3 switch or some other device that is providing LAN extension...
I am just wondering what could be the possible causes to look into....
Thanks,
Sal
#sh interfaces fastEthernet 0/23
FastEthernet0/23 is up, line protocol is up (connected)
Hardware is Fast Ethernet, address is 0019.3050.1497 (bia 0019.3050.1497)
Description: ASA_VPN_TO
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 8/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, media type is 10/100BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:01, output 00:00:05, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 3455000 bits/sec, 287 packets/sec
5 minute output rate 153000 bits/sec, 136 packets/sec
948546057 packets input, 73053163 bytes, 0 no buffer
Received 672802 broadcasts (0 multicast)
0 runts, 0 giants, 0 throttles
6861 input errors, 3216 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 672607 multicast, 0 pause input
0 input packets with dribble condition detected
502168637 packets output, 2280537502 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
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
Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 26 WS-C2960-24TT-L 12.2(25)SEE2 C2960-LANBASE-M
Solved! Go to Solution.
10-03-2012 02:42 PM
CRC | Indicates that the cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. |
CRC indicate noise or transmission problems on the LAN or the LAN
bus itself. A high number of CRCs is usually the result of collisions or a station
transmitting bad data.
1 : Check cables to determine whether any are damaged.
2. There have been 6861 'input errors' reported.
This indicates the number of packets received incorrectly, having a CRC error
and a non-integer number of octets. On a LAN, this is usually the result of collisions
or a malfunctioning Ethernet device.
3: Monitor the level of frame errors over time. If they are increasing,
try swapping interfaces and or ports to identify the problem.
http://www.cisco.com/en/US/docs/internetworking/troubleshooting/guide/tr1904.html#wp1020667
please rate if this helps
thanks
10-03-2012 02:07 PM
Have you tested the cable that is connecting this port to the ASA? Also make sure that the duplex and speed settings match on both ends. Last thing you can try is change the port and see if the errors go away.
10-03-2012 02:42 PM
CRC | Indicates that the cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. |
CRC indicate noise or transmission problems on the LAN or the LAN
bus itself. A high number of CRCs is usually the result of collisions or a station
transmitting bad data.
1 : Check cables to determine whether any are damaged.
2. There have been 6861 'input errors' reported.
This indicates the number of packets received incorrectly, having a CRC error
and a non-integer number of octets. On a LAN, this is usually the result of collisions
or a malfunctioning Ethernet device.
3: Monitor the level of frame errors over time. If they are increasing,
try swapping interfaces and or ports to identify the problem.
http://www.cisco.com/en/US/docs/internetworking/troubleshooting/guide/tr1904.html#wp1020667
please rate if this helps
thanks
10-03-2012 05:01 PM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
BTW, if your CRC and input errors stay at such a low percentage of the total packets received, it shouldn't be too detrimental to transit traffic.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide