No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Large CRC errors received on a switch interface

Publication Date:  2018-02-22 Views:  1393 Downloads:  0
Issue Description

Product: S5700-26X-SI-12S-AC

Problem: The Core switch receives large number of CRC errors on the interface that connected to the Router and the same interface keep flapping UP/Down.


Alarm Information

<010.Communication_IT-Room_Core-Switch_01>display logbuffer

Feb  5 2018 19:13:49 010.Communication_IT-Room_Core-Switch_01 %%01IFPDT/4/IF_STATE(l)[5]:Interface GigabitEthernet0/0/1 has turned into UP state.

Feb  5 2018 19:13:31 010.Communication_IT-Room_Core-Switch_01 %%01IFPDT/4/IF_STATE(l)[6]:Interface GigabitEthernet0/0/1 has turned into DOWN state.

Feb  5 2018 19:08:19 010.Communication_IT-Room_Core-Switch_01 %%01IFPDT/4/IF_STATE(l)[7]:Interface GigabitEthernet0/0/1 has turned into UP state.

Feb  5 2018 19:08:06 010.Communication_IT-Room_Core-Switch_01 %%01IFPDT/4/IF_STATE(l)[8]:Interface GigabitEthernet0/0/1 has turned into DOWN state.

Feb  5 2018 18:47:39 010.Communication_IT-Room_Core-Switch_01 %%01IFPDT/4/IF_STATE(l)[9]:Interface GigabitEthernet0/0/1 has turned into UP state.

Feb  5 2018 18:47:24 010.Communication_IT-Room_Core-Switch_01 %%01IFPDT/4/IF_STATE(l)[10]:Interface GigabitEthernet0/0/1 has turned into DOWN state.


<010.Communication_IT-Room_Core-Switch_01>display trapbuffer

#Jan 17 2018 19:49:31 010.Communication_IT-Room_Core-Switch_01 IFNET/1/CRCERRORRISING:OID 1.3.6.1.4.1.2011.5.25.41.4.1 The CRC error is rising. (hwIfMonitorIndex=6, hwIfMonitorCrcErrorStatistics=5, hwIfMonitorCrcErrorThreshold=3, hwIfMonitorCrcErrorInterval=10, InterfaceName=GigabitEthernet0/0/1)
#Jan 17 2018 19:49:29 010.Communication_IT-Room_Core-Switch_01 MSTP/4/PFWD:OID 1.3.6.1.4.1.2011.5.25.42.4.2.1 The port has been set to forwarding state. (InstanceID=0, PortInstanceID=0, PortID=1, IfIndex=6, PortName=GigabitEthernet0/0/1)
#Jan 17 2018 19:49:29 010.Communication_IT-Room_Core-Switch_01 MSTP/1/TOPOC:OID 1.3.6.1.2.1.17.0.2 Bridge topology change.
#Jan 17 2018 19:49:29 010.Communication_IT-Room_Core-Switch_01 IFNET/1/IF_LINKUP:OID 1.3.6.1.6.3.1.1.5.4 Interface 6 turned into UP state.(AdminStatus=1,OperStatus=1,InterfaceName=GigabitEthernet0/0/1)
#Jan 17 2018 19:49:21 010.Communication_IT-Room_Core-Switch_01 IFNET/1/CRCERRORRESUME:OID 1.3.6.1.4.1.2011.5.25.41.4.2 The CRC error resume. (hwIfMonitorIndex=6, hwIfMonitorCrcErrorStatistics=0, hwIfMonitorCrcErrorThreshold=3, hwIfMonitorCrcErrorInterval=10, InterfaceName=GigabitEthernet0/0/1)
#Jan 17 2018 19:49:13 010.Communication_IT-Room_Core-Switch_01 IFNET/1/IF_LINKDOWN:OID 1.3.6.1.6.3.1.1.5.3 Interface 6 turned into DOWN state.(AdminStatus=1,OperStatus=2,InterfaceName=GigabitEthernet0/0/1)
#Jan 17 2018 19:39:31 010.Communication_IT-Room_Core-Switch_01 IFNET/1/CRCERRORRISING:OID 1.3.6.1.4.1.2011.5.25.41.4.1 The CRC error is rising. (hwIfMonitorIndex=6, hwIfMonitorCrcErrorStatistics=117, hwIfMonitorCrcErrorThreshold=3, hwIfMonitorCrcErrorInterval=10, InterfaceName=GigabitEthernet0/0/1)
#Jan 17 2018 19:39:29 010.Communication_IT-Room_Core-Switch_01 IFNET/1/CRCERRORRESUME:OID 1.3.6.1.4.1.2011.5.25.41.4.2 The CRC error resume. (hwIfMonitorIndex=6, hwIfMonitorCrcErrorStatistics=0, hwIfMonitorCrcErrorThreshold=3, hwIfMonitorCrcErrorInterval=10, InterfaceName=GigabitEthernet0/0/1)

[010.Communication_IT-Room_Core-Switch_01]display interface GigabitEthernet 0/0/1

Line protocol current state : UP                                                                                                                                                                           

Description:To_AR2200

Switch Port, Link-type : trunk(configured),

PVID :    1, TPID : 8100(Hex), The Maximum Frame Length is 9216

IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 7079-903f-15c0

Current system time: 2018-02-05 19:33:15

Port Mode: COMMON COPPER

Speed : 1000,   Loopback: NONE

Duplex: FULL,   Negotiation: ENABLE

Mdi   : AUTO,   Flow-control: DISABLE

Last 300 seconds input rate 2338368 bits/sec, 389 packets/sec

Last 300 seconds output rate 3589400 bits/sec, 503 packets/sec

Input peak rate 5685864 bits/sec, Record time: 2018-02-05 19:24:25

Output peak rate 5605984 bits/sec, Record time: 2018-02-05 19:31:33

 

Input:  250309 packets, 188157096 bytes

  Unicast:                     245903,  Multicast:                         345

  Broadcast:                       19,  Jumbo:                               0

  Discard:                          0,  Pause:                               0

  Frames:                           0

 

  Total Error:                   4042

  CRC:                           3573,  Giants:                              0

  Jabbers:                         53,  Fragments:                           0

  Runts:                            0,  DropEvents:                          0

 Alignments:                       0,  Symbols:                           416

  Ignoreds:                         0

 

Output:  313693 packets, 267303089 bytes

  Unicast:                     311325,  Multicast:                        1075

  Broadcast:                     1293,  Jumbo:                               0

  Discard:                          0,  Pause:                               0

 

  Total Error:                      0

  Collisions:                       0,  ExcessiveCollisions:                 0

  Late Collisions:                  0,  Deferreds:                           0

  Buffers Purged:                   0

 

    Input bandwidth utilization threshold : 80.00%

    Output bandwidth utilization threshold: 80.00%

    Input bandwidth utilization  : 0.23%

    Output bandwidth utilization : 0.36%

Handling Process

1. Check the switch logbuffer "display logbuffer".

2. Check the switch trapbuffer "display trapbuffer".

3. Check the flapping Interface statistics "display interface GigabitEthernet 0/0/1".

4. Configure the interfaces at the two ends of the faulty cable to both work in auto-negotiation or non-auto-negotiation mode.

5. Check whether the physical link is faulty by replacing it.

6. check the logs again and monitor the status.

Root Cause

The Ethernet cable is faulty, a faulty cable degrades link quality, affecting packet transmission on the link, so the switch receives a large number of CRC error packets.

Solution

Replace the faulty ethernet cable with new cable.

END