Interface errors

[zeeshanparkar]

I have a Cisco 6509 interface connected to an Avaya CLAN. Both are set to 10/ half duplex. But there are errors incrementing on its interface. Why is it happening. Someone at work told me its because both are half duplex but I don't buy that arguement. Can someone please explain this in a better way to me.

249 runts, 0 giants, 0 throttles

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

[Leo Laohoo · Accepted solution]

Someone at work told me its because both are half duplex but I don't buy that arguement.

I would. 

Depending on your IOS, try this command "sh interface counter error" and post the result.

[zeeshanparkar]

Port            Align-Err    FCS-Err   Xmit-Err    Rcv-Err UnderSize OutDiscards
Gix/XX                  0          0          0        272         0       39625

Port          Single-Col Multi-Col  Late-Col Excess-Col Carri-Sen     Runts                                                                                                                                                                   Giants
Gix/XX               163        48         0          0         0       272                                                                                                                                                                        0

Port           SQETest-Err Deferred-Tx IntMacTx-Err IntMacRx-Err Symbol-Err
Gix/XX                   0          81            0            0          0

How would half duplex cause errors?

[Leo Laohoo · Accepted solution]

Single and Multi-collisions are not caused by half Duplex?  It sure is.

[zeeshanparkar]

Yup got it. Dint know about it.

[Leo Laohoo]

Thanks for the ratings.

Maybe these links will help:

Troubleshooting Cisco Catalyst Switches to NIC Compatibility Issues

Configuring and Troubleshooting Ethernet 10/100/1000Mb Half/Full Duplex Auto-Negotiation

[Michael Odom]

You might check your cabling first.  In many cases CRC errors indicate a physical cabling problem.  You might try replacing your network cable with a known good cable.

Now the bad news, if you're running a TN799DP CLAN card, I'm assuming it is probably in some sort of Avaya shelf.  It's been a few years since I've messed with them, but at least the older Avaya shelves had a proprietary dongle that cabled the back of the actual shelf to the cabling panel where you would plug in your ethernet cable to the CLAN card.  The really old shelves did not have CAT rated "dongle", and were not supported for speeds over 10mbps.  I have seen these dongles go bad, and it usually required an Avaya tech to replace.

[zeeshanparkar]

It was connected to 799C which only supports half duplex. Looks like I have to live with it unless we updgrade to TN799DP, which supports full duplex.

[Michael Odom]

You shouldn't have to live with it.  I suspect your problem is cabling, and if it is cabling it could either be your patch cable or the proprietary dongle in the back of the cabinet.

[Leo Laohoo]

CRC is one thing and collisions is another.  Half duplex can cause collisions.  IF you want to test your cabling is causing the CRC then either replace it or run a TDR.  I'm not sure if TDR is supported on your 6500 (due to hardware or IOS limitation).

If you want to try TDR on your 6500 be aware that in some IOS this can be disruptive.  Here are the commands/steps:

1.  Use the command "test cable tdr interface ";

2.  Wait for about 7-10 seconds for the test to finish;

3.   To view your result use the command "sh cable tdr interface "

Post your result if you can run the commands.

[zeeshanparkar]

switch#show cable-diagnostics tdr interface gigabitEthernet X/XX

TDR test last run on: April 12 23:45:13
Interface Speed Pair Cable length        Distance to fault   Channel Pair status
--------- ----- ---- ------------------- ------------------- ------- ------------
GiX/XX    10    1-2  N/A                 N/A                 Pair B  Terminated
                3-6  N/A                 N/A                 Pair A  Terminated
                4-5  N/A                 14   +/- 2  m       Invalid Open
                7-8  N/A                 15   +/- 2  m       Invalid Open

[Leo Laohoo · Accepted solution]

Firstly, thanks for posting the result.

Next, what IOS are you using?  It's been awhile since I've seen the result of "Termination".

Ok, here's my interpretation of your result:

1.  Speed shows 10 mbps;

2.  If speed is 10 mbps, then disregard test result of 4 - 5 (Pair C) and 7 - 8 (Pair D);

3.  I'm suspecting you are using SXF or SXH IOS (maybe I'm wrong) and this is why the Cable Length and Distance to Fault is "N/A".

4.  "Terminated" pair status was replaced to "Normal" or "OK" because alot people were complaining thinking that it meant something bad.

Your cable is fine, as far as I can tell with your cable.

[zeeshanparkar]

This is the show ver for the switch:

sh ver
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Versio                                                                                                                                                             n 12.2(33)SXH4, RELEASE SOFTWARE (fc1)

[Leo Laohoo]

SXH4

Close. 

[zeeshanparkar]

So bottom line cable is fine,

but due to the half duplex I have to live with it?