C7204VXR, Fastethernet lost communication, but not going down

[oponce]

We have a Router 7204VXR, the fastethernet 0/1 lost the communication and blocking port, but the port continue up, the solution is reset port (shutdown, no shutdown), Somebody knows this problem?

[sachinraja]

blocking port ? Is the line protocol of the particular port down ? Please send us the output of the sh interface fastethernet0/1.

This might be due to some improper cabling or faulty switch ports.

[oponce]

the cabling is fine, and the switch port too.

this is a show interface:

FastEthernet0/1 is up, line protocol is up

Hardware is i82543 (Livengood), address is 0005.dcfa.0801 (bia 0005.dcfa.0801)

Description: omited

Internet address is omited

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 02:57:18, output 00:00:08, output hang never

Last clearing of "show interface" counters 3d02h

Queueing strategy: fifo

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

30 second input rate 0 bits/sec, 0 packets/sec

30 second output rate 0 bits/sec, 0 packets/sec

825863713 packets input, 3435169950 bytes

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

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

0 watchdog

0 input packets with dribble condition detected

609254483 packets output, 328093214 bytes, 0 underruns(0/0/0)

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

[nicolas]

Hi

My name is Christophe, I've a same problem with a Cisco 7204VXR router, Sometimes the fast 0/1 port on I/O-2FE/E lost the communication, However this interface is UP,UP. The workarounds are ( shut/no shut ) or unplug /plug the ethernet cable.

I've looked your show interface fast 0/1, you have the same chipset ( Hardware is i82543 (Livengood) ) as mine.

The current runnning version is : c7200-is-mz.122-6.bin

Please find the show interface for this router :

This show has been taken during the problem.

**************************************************

FastEthernet0/1 is up, line protocol is up

Hardware is i82543 (Livengood), address is 0008.a4cd.2c06 (bia 0008.a4cd.2c06)

Description: Vers LAN

Internet address is 193.51.93.1/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:10:50, output 00:00:00, output hang never

Last clearing of "show interface" counters never

Queueing strategy: fifo

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

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 20000 bits/sec, 1 packets/sec

22562412 packets input, 3910674710 bytes

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

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

0 watchdog

0 input packets with dribble condition detected

20005052 packets output, 437914511 bytes, 0 underruns

0 output errors, 0 collisions, 6 interface resets

0 babbles, 0 late collision, 0 deferred

3 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

*****************************************************

Do you have found any issue for this problem ( bugs SW, replacement HW, etc.... ) ?

Many thanks for your answer.

Best Regards,

[jolmo]

Have you ckecked this?

"Cisco Security Advisory: Cisco IOS Interface Blocked by IPv4 Packets"

http://www.cisco.com/en/US/products/products_security_advisory09186a00801a34c2.shtml

HTH

[rinelson]

I had this same issue with a 2620 2 weeks ago. TAC swore it was the nachi virus and not hardware. I humored TAC and setup the access-list to filter it. I setup debugs to try and capture what was casuing it. I/TAC didn't see any reason for the lost communication. I replaced the hardware and haven't experienced that problem again.