errors in a Cisco 7206VXR FastEthernet card

icalvo · ‎10-26-2001

Hi everyone.

I send this query because I need some help with a fault that nowadays I have.

I have got a Cisco 7206 VXR with an I/O FE Controller and I can see at the FastEthernet interface a great amount of errors that I not able to know the cause.

You can see an example of statistics below.

FastEthernet0/0 is up, line protocol is up

Hardware is DEC21140A, address is 0003.fecf.a400 (bia 0003.fecf.a400)

Internet address is 192.168.93.195/24

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, 100BaseTX/FX

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:00, output 00:00:00, output hang never

Last clearing of "show interface" counters 01:33:19

Queueing strategy: fifo

Output queue 0/40, 0 drops; input queue 0/75, 0 drops

5 minute input rate 314000 bits/sec, 193 packets/sec

5 minute output rate 127000 bits/sec, 241 packets/sec

779995 packets input, 123063628 bytes

Received 8525 broadcasts, 0 runts, 3 giants, 0 throttles

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

0 watchdog

607 input packets with dribble condition detected

937826 packets output, 69127848 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 output buffer failures, 0 output buffers swapped out

I opened a TAC a week ago and the engineer asigned to the case sent me a new card. After I had installed the result was same, CRC errors and " dribble condition".

Before opening a TAC I changed the ethernet cable, the port of the switch and even the whole switch. The result was the same too.

In the ATM interface of the router, which is the only card installed, you can't see any CRC error (errors that are due to the physical transmission, I think) neither another kind of error.

You can see some statistics below.

ATM1/0 is up, line protocol is up

Hardware is ENHANCED ATM PA

MTU 4470 bytes, sub MTU 4470, BW 33920 Kbit, DLY 200 usec,

reliability 255/255, txload 2/255, rxload 1/255

Encapsulation ATM, loopback not set

Keepalive not supported

Encapsulation(s): AAL5

4096 maximum active VCs, 7 current VCCs

VC idle disconnect time: 300 seconds

0 carrier transitions

Last input 00:00:00, output 00:00:00, output hang never

Last clearing of "show interface" counters 02:41:50

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output

Queueing strategy: Per VC Queueing

30 second input rate 73000 bits/sec, 148 packets/sec

30 second output rate 385000 bits/sec, 148 packets/sec

1765814 packets input, 135897012 bytes, 0 no buffer

Received 0 broadcasts, 0 runts, 0 giants, 0 throttles

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

1447600 packets output, 238659545 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 output buffer failures, 0 output buffers swapped out

I have tried to search in the web what sort of error is "dribble condition detected".

Almost the traffic through the router is Citrix ICA Client (Metaframe).

I've one more question: Could the errors be created by the Metaframe servers that are connected to the same LAN of the router Cisco 7206VXR or maybe by the client in the remote branches?

I look forward to hearing from you.

My best regards,

Albert.

2rsliteris · ‎10-26-2001

Albert,

One thought. Is the switch the 7206 connected to configured for VLAN's? And if so, is the port connected to the router configured for trunking? One thought was that switches configured with VLANs attach a tag to the header that could cause the packets to be giants. If you are using trunking, be sure to include the command "encap isl " or "encap dot1q " on the fa interface.

Ray

TYLER WEST · ‎10-26-2001

Agreed. Check your config on the switchport the router interface is connected to. If you still don't see anything, post the config and stats for that switchport and let some of us take a look at it. Two sets of eyes are better than one.

Tyler

icalvo · ‎10-26-2001

FastEthernet0/23 is up, line protocol is up

Hardware is Fast Ethernet, address is 0004.4d8a.e5d7 (bia 0004.4d8a.e5d7)

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

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

Encapsulation ARPA, loopback not set

Keepalive not set

Auto-duplex (Half), Auto Speed (100), 100BaseTX/FX

ARP type: ARPA, ARP Timeout 04:00:00

Last input 1d17h, output 00:00:36, 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 7000 bits/sec, 11 packets/sec

5 minute output rate 10000 bits/sec, 12 packets/sec

63423387 packets input, 923823130 bytes

Received 396 broadcasts, 0 runts, 0 giants, 0 throttles

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

0 watchdog, 8 multicast

0 input packets with dribble condition detected

55395518 packets output, 1262243013 bytes, 0 underruns

82350 output errors, 39119 collisions, 1 interface resets

0 babbles, 82350 late collision, 50285 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

FastEthernet0/0 is up, line protocol is up

Hardware is DEC21140A, address is 0003.fecf.a400 (bia 0003.fecf.a400)

Internet address is 192.168.93.195/24

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, 100BaseTX/FX

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:00, output 00:00:00, output hang never

Last clearing of "show interface" counters 1d04h

Queueing strategy: fifo

Output queue 0/40, 0 drops; input queue 0/75, 0 drops

5 minute input rate 88000 bits/sec, 64 packets/sec

5 minute output rate 40000 bits/sec, 87 packets/sec

7279620 packets input, 1294973341 bytes

Received 82038 broadcasts, 0 runts, 6 giants, 0 throttles

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

0 watchdog

5839 input packets with dribble condition detected

8616514 packets output, 666367320 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 output buffer failures, 0 output buffers swapped out

interface FastEthernet0/0

ip address 192.168.93.195 255.255.255.0

no ip proxy-arp

full-duplex

no cdp enable

interface FastEthernet0/23

!

interface VLAN1

ip address 192.168.93.220 255.255.255.0

no ip directed-broadcast

no ip route-cache

KONSTANTIN FEDOROV · ‎10-26-2001

Hello

Oh ... :)) In my previous answers I did not think about this.

Change duplex on the FastEthernet0/0 to full, It will be help.

MickPhelps · ‎10-27-2001

FastE0/0 is already full

FastE0/23 is half

Look at E0/23

0 babbles, 82350 late collision, 50285 deferred

Late collision on half-duplex and CRCs on full duplex are indicative of duplex-mismatch.

Verify that FastE0/23 is set to full.

Mick.

icalvo · ‎10-29-2001

hi,

you're rigth. It seems to be the real problem.

Thank you.

KONSTANTIN FEDOROV · ‎10-26-2001

Hello

What kind of FE Controller 2FE or 1 FE ?

icalvo · ‎10-26-2001

Hello,

1 FE

TiA

Albert

KONSTANTIN FEDOROV · ‎10-26-2001

Hello

Hm.. I know some problem with 2FE I/O controller, this problem concern

different partical size FE's and others interfaces.

You have faced with not trivial problem, I think only protocol analyzer can help you.

Well I will think about this

2rsliteris · ‎10-26-2001

A dribble condition occurs when the router detects a packet that is slightly larger than specification allows. The router will forward the packet and increment the dribble condition counter.

loren · ‎11-17-2001

I also was having the same problem with an Ethernet Card in my 3640 Router.. To fix the problem I forced the port on the Switch to 100Mbs/FD this made it quit autosensing and fixed the CRC and Input Errors..