CRC Error and input Error how can fix these

Unanswered Question
Jan 6th, 2010
User Badges:

FastEthernet0/13 is up, line protocol is up
  Hardware is Fast Ethernet, address is 0004.4d27.66cd (bia 0004.4d27.66cd)
  Description: EDL-P-Box-NO-4
  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
     reliability 250/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive not set
  Auto-duplex (Full), Auto Speed (100), 100BaseTX/FX
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 18:52:43, output 00:00:01, output hang never
  Last clearing of "show interface" counters never
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 12000 bits/sec, 6 packets/sec
  5 minute output rate 24000 bits/sec, 6 packets/sec
     14488019 packets input, 2783320210 bytes
     Received 345346 broadcasts, 0 runts, 0 giants, 0 throttles
     261028 input errors, 259429 CRC, 1599 frame, 0 overrun, 0 ignored
     0 watchdog, 84207 multicast
     0 input packets with dribble condition detected
     19658279 packets output, 3529106068 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 output buffer failures, 0 output buffers swapped out
PAD-8-1-10.179#cle
v

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.7 (6 ratings)
Loading.
Ganesh Hariharan Wed, 01/06/2010 - 03:13
User Badges:
  • Purple, 4500 points or more
  • Community Spotlight Award,

    Member's Choice, February 2016

Hi,


Check out the below explanation for CRC error and farme error and few useful links to trouble shoot these type of problems


  The CRC error rate is 1.75915% (greater than 1 in a million packets),
  and the collision rate is less than 0.1%.
  This can indicate excessive 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.


  TRY THIS: Check cables to determine whether any are damaged. If 100BaseTX is being
  used, ensure Category 5 cabling is being used and not another type, such as Category
  3.


  There have been 1599 'frame 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.


TRY THIS: 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/customer/products/hw/modules/ps2033/products_tech_note09186a008009446d.shtml


http://www.cisco.com/en/US/docs/internetworking/troubleshooting/guide/tr1904.html


http://www.cisco.com/en/US/docs/internetworking/troubleshooting/guide/tr1904.html


Hope that helps out your query !!


Regards

Ganesh.H

vvasisth Mon, 01/11/2010 - 03:06
User Badges:
  • Silver, 250 points or more

in simple language CRC and input errors refer to Layer 1 issues could be a faulty port or cable.

Check then first.


regards,

Varun

AKM Fahad Aziz Sun, 08/16/2015 - 21:57
User Badges:

When I turn off my CISCO3825 IPBase router, it shows

Router# CRC Error

Can you please help me to solve this.

My router has 1GB D/256CF.

peter.mainwaring Mon, 01/11/2010 - 06:13
User Badges:

If possible, connect a known good device (maybe a laptop or something) to the wall/floor port that is in question. If the CRC and input errors disappear then the fault is with the NIC on the end device. If CRCs and Input errors are still being generated then there is a fault with the cabling, patch panel or wall socket.


Pete

Leo Laohoo Mon, 01/11/2010 - 14:12
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

If your switch supports TDR, use the "test cable-diagnostics tdr" command.


http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/12.2/50sg/command/reference/snmp_vtp.html#wp1208382

Hello Experts,

From last One week I am fully facing the issue with INPUT errors, CRC and Frames. Please find the below details. That is affected on my job, even lot of times I am checking the pots and cables and duplex, speed but continuously errors are increasing.I am only the person of in my organization, Please help me to find out the problem.
Now I am using CISCO 2911 router, every interfaces getting the errors like that only

Router#sh int g0/1
GigabitEthernet0/1 is up, line protocol is up
  Hardware is CN Gigabit Ethernet, address is 00c8.8b61.5371 (bia 00c8.8b61.5371)
  Internet address is 125.99.247.249/29
  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
     reliability 255/255, txload 2/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full Duplex, 100Mbps, media type is RJ45
  output flow-control is unsupported, input flow-control is unsupported
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:02, output 00:00:00, output hang never
  Last clearing of "show interface" counters 01:32:49
  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 102000 bits/sec, 59 packets/sec
  5 minute output rate 904000 bits/sec, 97 packets/sec
     232879 packets input, 50659461 bytes, 0 no buffer
     Received 1833 broadcasts (0 IP multicasts)
     0 runts, 0 giants, 0 throttles
     14546 input errors, 7274 CRC, 6472 frame, 0 overrun, 0 ignored
     0 watchdog, 288 multicast, 0 pause input
     343302 packets output, 368712945 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     185 unknown protocol drops
     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
Router#


 

Hello Experts,

From last One week I am fully facing the issue with INPUT errors, CRC and Frames. Please find the below details. That is affected on my job, even lot of times I am checking the pots and cables and duplex, speed but continuously errors are increasing.I am only the person of in my organization, Please help me to find out the problem.
Now I am using CISCO 2911 router, every interfaces getting the errors like that only

Router#sh int g0/1
GigabitEthernet0/1 is up, line protocol is up
  Hardware is CN Gigabit Ethernet, address is 00c8.8b61.5371 (bia 00c8.8b61.5371)
  Internet address is 125.99.247.249/29
  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
     reliability 255/255, txload 2/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full Duplex, 100Mbps, media type is RJ45
  output flow-control is unsupported, input flow-control is unsupported
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:02, output 00:00:00, output hang never
  Last clearing of "show interface" counters 01:32:49
  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 102000 bits/sec, 59 packets/sec
  5 minute output rate 904000 bits/sec, 97 packets/sec
     232879 packets input, 50659461 bytes, 0 no buffer
     Received 1833 broadcasts (0 IP multicasts)
     0 runts, 0 giants, 0 throttles
     14546 input errors, 7274 CRC, 6472 frame, 0 overrun, 0 ignored
     0 watchdog, 288 multicast, 0 pause input
     343302 packets output, 368712945 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     185 unknown protocol drops
     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
Router#


 

Leo Laohoo Thu, 02/02/2017 - 22:14
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

I have responded to your thread (HERE).

Thank you SIR,

Every day I am getting more errors and every 10 minutes I was cleared the errors but i don't know the exact solution because I am alone. Every minute I am searching for resolution, and I have one doubt about RJ45, is it ok for router to switch connection?


Please find the below details

1.sh run interface G0/1

Router#sh run int g0/1
Building configuration...

Current configuration : 192 bytes
!
interface GigabitEthernet0/1
 ip address 192.168.1.1 255.255.255.0 secondary
 ip address 125.99.247.249 255.255.255.248
 ip nat inside
 ip virtual-reassembly in
 duplex full
 speed 100
end

2.  sh controll G0/1


Router#sh controll g0/1
Interface GigabitEthernet0/1
 = Hardware =
Hardware is PLATFORM SGMII INTERFACE
HWIDB: 3DDEC8B0, INSTANCE: 3DDED600, FASTSEND: 300B2020, MCI_INDEX: 0
Route Cache Flag: 11



= Media  RJ45 =

Media Change Count: 1

PORT IPD Registers:
        BP_PAGE_CNT: 0x0000000000000001, BP_CNTS_PRX: 0x0000000000000000
GMX Registers:
        RXX_INT_REG: 0x0000000000000810, RXX_INT_EN : 0x0000000000000000
        PRTX_CFG   : 0x0000000000003005, RXX_FRM_CTL: 0x0000000000000077
        RXX_FRM_CHK: 0x00000000000003BA, RXX_FRM_MIN: 0x0000000000000000
        RXX_FRM_MAX: 0x0000000000000000, RXX_JABBER : 0x0000000000002580
        RXX_DECISIO: 0x0000000000000018, RXX_FRM_CTL: 0x0000000000000077
        RXX_FRM_CHK: 0x00000000000003BA, RXX_JABBER : 0x0000000000002580
        RXX_DECISIO: 0x0000000000000018, RXX_UDD_SKI: 0x0000000000000000
        RXX_STATS_C: 0x0000000000000000, RXX_IFG    : 0x0000000000000008
        RXX_PAU_DRP: 0x0000000000000000, RXX_STATS_P: 0x00000000003379B2
        RXX_STAT_CT: 0x0000000000000000, RXX_STATS_D: 0x00000000000027C8
        RXX_STAT_DR: 0x0000000000000000, RXX_STATS_B: 0x0000000000014EF7
        SMACX      : 0x000000C88B615371
        TXX_SGMII_C: 0x0000000000000001, TXX_CTL    : 0x0000000000000003
        RX_PRTS    : 0x0000000000000004, RX_BP_DROP : 0x0000000000000002
        RX_BP_ON   : 0x0000000000000040, RX_BP_OFF  : 0x0000000000000010
        TXX_PAU_PKT: 0x0000000000000060, TXX_MIN_PKT: 0x000000000000003B
        TXX_PAU_PKI: 0x0000000000000010, TXX_SOFTPAU: 0x0000000000000000
        TXX_PAU_TGO: 0x0000000000000000, TXX_PAU_ZRO: 0x0000000000000001
        INF_MODE   : 0x0000000000000022, TX_PRTS    : 0x0000000000000004
        TX_IFG     : 0x0000000000000048, TX_JAM     : 0x00000000000000EE
        TX_COL_ATMP: 0x0000000000000010, TX_PAU_DMAC: 0x00000180C2000001
        TX_PAU_TYPE: 0x0000000000008808, TX_OVR_BP  : 0x0000000000000F0F
        TX_BP      : 0x0000000000000000, TX_CORRUPT : 0x000000000000000F
        RX_PRT_INFO: 0x0000000000000000, GMX_STAT_BP: 0x0000000000000000
        TX_INT_REG : 0x0000000000000000, TX_INT_EN  : 0x0000000000000000
        ADR_CAM0   : 0x0000000000000000
        ADR_CAM1   : 0x00000000000000C8
        ADR_CAM2   : 0x000000000000008B
        ADR_CAM3   : 0x0000000000000061
        ADR_CAM4   : 0x0000000000000053
        ADR_CAM5   : 0x0000000000000071
        ADR_CTL    : 0x000000000000000D, CAM_EN     : 0x00000000000000FF
        TXX_STAT0  : 0x0000000000000000, TXX_STAT1  : 0x0000000000000000
        TXX_STAT2  : 0x000000018740924C, TXX_STAT3  : 0x000000000052639B
        TXX_STAT4  : 0x00047EFE00000000, TXX_STAT5  : 0x0001DA000006204B
        TXX_STAT6  : 0x0001C00D0001E345, TXX_STAT7  : 0x0000000000424700
        TXX_STAT8  : 0x00000668000015E4, TXX_STAT9  : 0x0000000000000000
PCS Registers:
        MRX_CTL_REG: 0x0000000000001140, MRX_STS_REG: 0x000000000000017C
        RXX_STA_REG: 0x00000000000008C7, RXX_SYN_REG: 0x0000000000000003
        TXX_STA_REG: 0x0000000000000064, SGMX_AN_ADV: 0x0000000000001801
        SGMX_AN_ADV: 0x000000000000D401, MISC_CTL   : 0x0000000000000000
        ANX_ADV_REG: 0x0000000000000060, ANX_LP_ABIL: 0x000000000000D000
        ANX_RESULTS: 0x000000000000000F, ANX_EXT_ST : 0x000000000000C000
        LNX_TMR_CNT: 0x0000000000000396, TX_RXX_PLRT: 0x0000000000000000
        INT_REG    : 0x0000000000000000, INT_EN_REG : 0x0000000000000000
        LOG_ANL_REG: 0x0000000000000000, ANX_ADV_REG: 0x0000000000000060
        ANX_LP_ABIL: 0x000000000000D000, ANX_RSL_REG: 0x000000000000000F
        ANX_EXT_ST : 0x000000000000C000, LNX_TMR_CNT: 0x0000000000000396
        MISCX_CTL: 0x0000000000001005
==============PIP Statistics================

        PIP_RX_NO_ERR = 0, PIP_PARTIAL_ERR = 0
        PIP_JABBER_ERR = 0, PIP_OVER_FCS_ERR = 0
        PIP_OVER_ERR = 0, PIP_ALIGN_ERR = 0
        PIP_UNDER_FCS_ERR = 49883, PIP_GMX_FCS_ERR = 4433
        PIP_UNDER_ERR = 0, PIP_EXTEND_ERR = 0
        PIP_LENGTH_ERR = 0, PIP_DAT_ERR = 0
        PIP_SKIP_ERR = 0, PIP_NIBBLE_ERR = 0
        PIP_UNKNOWN_ERR_14 = 0, PIP_UNKNOWN_ERR_15 = 0
        PIP_PIP_FCS = 0, PIP_PIP_SKIP_ERR = 0
        PIP_PIP_L2_MAL_HDR = 0
        pip_rx_no_particle = 0, pip_undef_err = 0
        pip_rx_no_buf_start = 0

PHY REGISTERS:
        Display for CRC check for page:6

        PACKET_GENERATION reg_addr: 16: 0x0010
        CRC COUNTERS reg_addr: 17: 0xFFFF

 Clearing CRC checker in Reg16, Page 6: Reg:16 is 0x0010

        page number:0

        Copper Contrl @ reg_addr: 0: 0x2100
        Copper Status @ reg_addr: 1: 0x7949
        PHY Idf1 @ reg_addr: 2: 0x0141
        PHY Idf2 @ reg_addr: 3: 0x0C97
        Autoneg Adv @ reg_addr: 4: 0x0D41
        Autoneg Lnk Ptr abty @ reg_addr: 5: 0x0000
        Autoneg Exp @ reg_addr: 6: 0x0004
        Autoneg Nx Pg Tx @ reg_addr: 7: 0x2801
        Autoneg Lk Prt Nx Pg @ reg_addr: 8: 0x0000
        1000B-T Ctr @ reg_addr: 9: 0x0E00
        1000B-T St @ reg_addr: 10: 0x0000
        Copper Ext St @ reg_addr: 15: 0x3000
        Copper Specific Ctl1 @ reg_addr: 16: 0x6060
        Copper Specific St1 @ reg_addr: 17: 0x6C48
        Copper Interrupt En @ reg_addr: 18: 0x0000
        Copper Specific St2 @ reg_addr: 19: 0x0440
        Copper Rcv Er Ctr @ reg_addr: 21: 0x0000
        Copper Specific Ctl2 @  reg_addr: 26: 0x8040

        page number:1

        Fiber Contrl @ reg_addr: 0: 0x1140
        Fiber Status @ reg_addr: 1: 0x7949
        PHY Idf1 @ reg_addr: 2: 0x0141
        PHY Idf2 @ reg_addr: 3: 0x0C97
        Autoneg Adv @ reg_addr: 4: 0x0060
        Autoneg Lnk Ptr abty @ reg_addr: 5: 0x0000
        Autoneg Exp @ reg_addr: 6: 0x0004
        Autoneg Nx Pg Tx @ reg_addr: 7: 0x2001
        Autoneg Lk Prt Nx Pg @ reg_addr: 8: 0x0000
        Fiber Ext St @ reg_addr: 15: 0x3000
        Fiber Specific Ctl1 @ reg_addr: 16: 0x0000
        Fiber Specific St1 @ reg_addr: 17: 0x0018
        Fiber Interrupt En @ reg_addr: 18: 0x0000
        Fiber Specific St2 @ reg_addr: 19: 0x0000
        Fiber Rcv Er Ctr @ reg_addr: 21: 0x0000
        Fiber Specific Ctl2 @  reg_addr: 26: 0x8085

        page number:2

        MAC Contrl @ reg_addr: 0: 0x1040
        PHY Idf1 @ reg_addr: 2: 0x0141
        PHY Idf2 @ reg_addr: 3: 0x0C97
        MAC Specific Ctl1 @ reg_addr: 16: 0x0288
        MAC Specific St1 @ reg_addr: 17: 0x0440
        MAC Interrupt En @ reg_addr: 18: 0x0000
        MAC Specific St2 @ reg_addr: 19: 0x0000
        MAC Specific Ctl2 @  reg_addr: 26: 0x0005

TX_COUNT: 0, TX_LIMITED: 0, TX_HEAD: 411, TX_TAIL: 411
TX_MIN_SIZE: 32, TX_MAX_SIZE: 512, TX_CURRENT_SIZE: 128
RX STARVES: 0

Software MAC Address Filter (hash:length/addr/mask/hits)
--------------------------------------------------------
  0x000:  0  ffff.ffff.ffff  0000.0000.0000     36045
  0x0C0:  0  0180.c200.0002  0000.0000.0000         0
  0x0C0:  1  0100.0ccc.cccc  0000.0000.0000      1507
  0x0C5:  0  0180.c200.0007  0000.0000.0000         0
  0x0CC:  0  0180.c200.000e  0000.0000.0000      2702
  0x0FA:  0  00c8.8b61.5371  0000.0000.0000         0

  Software filtered frames: 36994
  Unicast overflow mode: 0
  Multicast overflow mode: 1
  Promiscuous mode: 0
  Total Number of CAM entries: 1
Port Stopped: N

Internal Loopback Set: N

Router#

anshulsachdeva Tue, 07/10/2012 - 16:50
User Badges:

Two things I would check if I see the CRC/frame errors:


1.Both the end of the interfaces should have same speed and duplex settings.

2. Check the phyisical cabling , and are the two switches in the same room in DC or different to find out if there

is any media convertor in between . If yes then check the media convertor.


Note Remember- Most of the media convertor does not support fixed speed settings and people dont prefer doing that .so better to make it auto auto( speed and duplex). also check the other end of this interface , can you see the same errors ,

clear the counters and check again.


good luck!

nkarthikeyan Wed, 07/11/2012 - 22:55
User Badges:
  • Gold, 750 points or more

This is purely a physical issue...... either a cable issue or the media connected to it or a duplex problem...... verify all the above and check....

Leo Laohoo Wed, 07/11/2012 - 23:10
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

   reliability 250/255, txload 1/255, rxload 1/255

Don't know why I didn't see this.


It's a cabling issue.

Jose Solano Sat, 11/09/2013 - 15:08
User Badges:
  • Silver, 250 points or more

Hi,



Check this:


1. Check the speed/duplex both the ends

2. Check the cable
3. Check by changing the speed and duplexto half or Auto
4. Chek if the grounding is proper



Regards,

Tomas Diaz Thu, 02/25/2016 - 09:02
User Badges:

Not necessarily, i encountered this problem with a barracuda web filter in inline mode (bump in the wire). it happened from time to time when the web filter rebooted. 

i dont know the exact cause but it was not L1, i think it was the link layer negotiation (speed, duplex settings) . 

i managed to fix it by shutting down the interface of the switch then back on, to force a renegotiation.l



PC-----f0/1 SW (c2960) f0/2---- lan Barracuda  wan ----  f0/0  c2821 internet router

|-------- ------------          same Bcast domain     ----------------|

 

------------- INTERFACE CONNECTED TO LAN OF cuda

show int f0/2

FastEthernet0/2 is up, line protocol is up (connected)

  Hardware is Fast Ethernet, address is e804.627a.9403 (bia e804.627a.9403)

  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,

     reliability 236/255, txload 1/255, rxload 1/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:32, output 00:00:00, output hang never

  Last clearing of "show interface" counters 00:07:41

  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 9000 bits/sec, 16 packets/sec

  5 minute output rate 9000 bits/sec, 16 packets/sec

     6904 packets input, 1117804 bytes, 0 no buffer

     Received 272 broadcasts (3 multicasts)

     0 runts, 0 giants, 0 throttles

     1576 input errors, 582 CRC, 0 frame, 0 overrun, 0 ignored

     0 watchdog, 3 multicast, 0 pause input

     0 input packets with dribble condition detected

     8796 packets output, 819348 bytes, 0 underruns

     0 output errors, 0 collisions, 0 interface resets

     0 unknown protocol drops

     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

Leo Laohoo Thu, 02/25/2016 - 12:05
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

I disagree.  Negotiation of speed &/or duplex does NOT change the Reliability value and this I am very sure.  


Run a TDR and I am certain it's a cable issue.  


Post the complete output to the command "sh controll e Fa0/2".  If it's a duplex mismatch there should be errors on the left-hand side column under "collisions".  

Karan Puri Mon, 11/11/2013 - 12:01
User Badges:

Leo gave the answer.. see the reliability. ..

@Leo , one question for you.. is test cable tdr n test interface is intrusive commands... can we use it during production time??? Do u have any sample output for this???


Sent from Cisco Technical Support Android App

Leo Laohoo Mon, 11/11/2013 - 13:44
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

@Leo , one question for you.. is test cable tdr n test interface is intrusive commands

I've created a "blog" in regards on how to use TDR


Your question has two answers:  Yes and no.  Yes, it is intrusive particularly when you have old IOS like 12.2(44)SE or earlier/lower.   It is also intrusive if you have a PoE device in one end.  However, if you have newer IOS like 12.2(50)SE and higher (version) or if you have plain Fast- or GigabitEthernet connection, then TDR will not be intrusive.

can we use it during production time

My switches have the latest IOS and I run TDR very regularly during business hours.  Most of the time, it doesn't matter.  If you are running TDR it means something is wrong with the connection so it doesn't matter because the business owner wants the issue rectified no matter what.

Karan Puri Tue, 11/12/2013 - 11:40
User Badges:

@Leo appreciate your doc.. I am searching for test interface doc too...

Sent from Cisco Technical Support Android App

Gurudath KS Wed, 11/13/2013 - 23:58
User Badges:

Hi,


Whats the distance between the end points,is it greater than 100 meters.then you will face this issue,due to  signal attenuation.


check with cable,duplex,speed.

Bhishma Khanna Fri, 01/10/2014 - 02:57
User Badges:
  • Cisco Employee,

Hi,


In your case the input and CRC errors are almost equal


261028 input errors, 259429 CRC


This clearly points to a layer one issue, mosy probable a bad cable which is transmitting the traffic partially and that is why the counters of input errors and CRC are getting hit at same time.


Thanks.

Actions

This Discussion