Input and CRC Errors due to Speed Mismatch

[mahesh18]

Hi Everyone,

I have Printer connectd to switch port.

I saw input and CRC errors incrementing rapidly.

Switchport was flapping due to this.

I checked the port status it was auto negotiating on full duplex and speed 100.

I Replaced Lan Cable with good working cable.

Still errors were incrementing.

Then i did shut and no shut  on port.

Then saw that swichport is now auto negotiating to

Full-duplex, 10Mb/s, media type is 10/100BaseTX

After this no input and CRC errors increment.

So is this possible that device can auto negotiate to different speeds when we reset the switch port?

Have anyone seen Input and CRC errors before due to speed mismtach?

Thanks

Mahesh

[ksk391393]

Hi mahesh ,

CRC will increase only the case when the Cable is bad or Device port issue , this is applicable  either it is WAN or LAN .

If speed is mismatch device wont communicate at all .

if you need confirmation hardcode the switch port to 100 mbps and check.device wont work .

[mahesh18]

Hi,

DEvice was working fine with speed 10.

I did shut and no shut  on port.

It is now auto negotiating to

Full-duplex, 100Mb/s, media type is 10/100BaseTX.

Will check if errors increment or not ?

Thanks

Mahesh

[Gregory Snipes]

This is likely a bad cable. Setting your ports to 10Mbps will let you connect over sub optimal conditions.

Once on a wim, I terminated both ends of a spool of cat5e and tried passing data though it at 10Mbps. I was able to transfer files without error over an 800 foot loop, which is way out of spec.

Regards,

Greg

[mahesh18]

Hi Greg,

I have  put that faulty cable to  other switch  port to see rule out cable issue

thanks

mahesh

[Reza Sharifi · Accepted solution]

Hi Mahesh,

Full-duplex, 10Mb/s, media type is 10/100BaseTX

Mostly likely the printer is 10Mb.  If it is not, can you check to see if it is set to auto?

Also, shut and no shut will not change the interface speed or negotiation unless the printer was turned of when you did the show interface.

Some times, if the connecting device to the switch port is turned off, you see

Auto-duplex

once the device is turned on it will change to:

Full-duplex

HTH

Reza

[mahesh18]

Hi Reza,

Currently switch port is auto nego 100 full.

I check printer it is set to Auto.

Do you think it can be issue with switch port as sometimes switch port and printer negotiate speed of 10 and sometimes 100?

thanks

MAhesh

[Leo Laohoo]

I agree with Reza.

Printers, the cheaper the worst, don't need 100 Mbps or 1Gbps speed.  So the manufacturers commonly stick a very, very old 10 Mbps, Half duplex NIC card in order to keep the cost down.

Post the output to the following commands:

1.  sh int ; AND

2.  sh controll e

What is the exact model of your switch?

[mahesh18]

Hi,

I did shut and no shut few hours ago currently switch port is working fine.

This time it negotiated to 100 full

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

     reliability 255/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 never, output 00:00:00, output hang never

  Last clearing of "show interface" counters 05:43:40

  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 46000 bits/sec, 13 packets/sec

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

     96601 packets input, 113767361 bytes, 0 no buffer

     Received 2 broadcasts (2 multicasts)

     0 runts, 0 giants, 0 throttles

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

     0 watchdog, 2 multicast, 0 pause input

     0 input packets with dribble condition detected

     109474 packets output, 42741612 bytes, 0 underruns

     0 output errors, 0 collisions, 0 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 is 3560

It has only option for

sh controllers fastEthernet 0/41  utilization

Receive Bandwidth Percentage Utilization   : 0

Transmit Bandwidth Percentage Utilization  : 0

Seems issue was with printer NIC  as sometimes it negotiate to speed 10 sometimes to 100

thanks

mahesh

[Leo Laohoo · Accepted solution]

Full-duplex, 100Mb/s, media type is 10/100BaseTX

If you are getting line errors, why are you forcing the duplex and speed?  I'd be thinking of setting both speed and duplex to auto.

Ok, so it's a 3560, then post the output to the command "sh controller e ".

switch is 3560

Like I've asked before, would be nice if you can specify the EXACT model of your switch (rather than you and me play a game of "20 questions").  And yes, the EXACT model will tell me if your switch will support TDR or not. 

[mahesh18]

Hi,

Here is info:

WS-C3560-48PS

sh controllers ethernet-controller  fastEthernet 0/41

     Transmit FastEthernet0/41                Receive
   2296133052 Bytes                       2943368241 Bytes
     27390447 Unicast frames                14698022 Unicast frames
     12669617 Multicast frames                 11824 Multicast frames
     24333358 Broadcast frames                 44802 Broadcast frames
            0 Too old frames              2932196653 Unicast bytes
            0 Deferred frames                7742602 Multicast bytes
            0 MTU exceeded frames            2871363 Broadcast bytes
            0 1 collision frames                   2 Alignment errors
            0 2 collision frames                 118 FCS errors
            0 3 collision frames                   0 Oversize frames
            0 4 collision frames                   0 Undersize frames
            0 5 collision frames                   1 Collision fragments
            0 6 collision frames
            0 7 collision frames             6790486 Minimum size frames
            0 8 collision frames             3455001 65 to 127 byte frames
            0 9 collision frames             3086584 128 to 255 byte frames
            0 10 collision frames             474760 256 to 511 byte frames
            0 11 collision frames              22899 512 to 1023 byte frames
            0 12 collision frames             925333 1024 to 1518 byte frames
            0 13 collision frames                  0 Overrun frames
            0 14 collision frames                  0 Pause frames
            0 15 collision frames
            0 Excessive collisions               295 Symbol error frames
            0 Late collisions                      0 Invalid frames, too large
            0 VLAN discard frames                  0 Valid frames, too large
            0 Excess defer frames                  1 Invalid frames, too small
     20539871 64 byte frames                       0 Valid frames, too small
     21411253 127 byte frames
      5014351 255 byte frames                      0 Too old frames
      1082141 511 byte frames                      0 Valid oversize frames
       377421 1023 byte frames                     0 System FCS error frames
     15968385 1518 byte frames                     0 RxPortFifoFull drop frame
            0 Too large frames
            0 Good (1 coll) frames
            0 Good (>1 coll) frames

this switch does not support TDR as i tried that already

Both sides are set to auto auto.

Currently switch port is auto nego 100 full.

I check printer it is set to Auto.

Do you think it can be issue with switch port as sometimes switch port and printer negotiate speed of 10 and sometimes 100?

[Leo Laohoo · Accepted solution]

No line errors on the transmit but there are some FCS and Symbols error on the Receive side.

So my guess is the printer. 

[mahesh18]

Hi Leolaohoo,

I checked today

  sh controllers ethernet-controller fa0/41

     Transmit FastEthernet0/41                Receive
   2310321370 Bytes                       3076541953 Bytes
     27467545 Unicast frames                14806113 Unicast frames
     12712679 Multicast frames                 11824 Multicast frames
     24356938 Broadcast frames                 44802 Broadcast frames
            0 Too old frames              3065370365 Unicast bytes
            0 Deferred frames                7742602 Multicast bytes
            0 MTU exceeded frames            2871363 Broadcast bytes
            0 1 collision frames                   2 Alignment errors
            0 2 collision frames                 118 FCS errors
            0 3 collision frames                   0 Oversize frames
            0 4 collision frames                   0 Undersize frames
            0 5 collision frames                   1 Collision fragments
            0 6 collision frames
            0 7 collision frames             6795392 Minimum size frames
            0 8 collision frames             3455169 65 to 127 byte frames
            0 9 collision frames             3086929 128 to 255 byte frames
            0 10 collision frames             477340 256 to 511 byte frames
            0 11 collision frames              22932 512 to 1023 byte frames
            0 12 collision frames            1025392 1024 to 1518 byte frames
            0 13 collision frames                  0 Overrun frames
            0 14 collision frames                  0 Pause frames
            0 15 collision frames
            0 Excessive collisions               295 Symbol error frames
            0 Late collisions                      0 Invalid frames, too large
            0 VLAN discard frames                  0 Valid frames, too large
            0 Excess defer frames                  1 Invalid frames, too small
     20655112 64 byte frames                       0 Valid frames, too small
     21432331 127 byte frames
      5014394 255 byte frames                      0 Too old frames
      1083196 511 byte frames                      0 Valid oversize frames
       382596 1023 byte frames                     0 System FCS error frames
     15969533 1518 byte frames                     0 RxPortFifoFull drop frame
            0 Too large frames
            0 Good (1 coll) frames
            0 Good (>1 coll) frames

Errors are  not incrementing.

Thanks

Mahesh

[mahesh18]

Hi,

Many thanks for all the help.

Regards

Mahesh