cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
497
Views
0
Helpful
4
Replies

1721 router dropping ethernet interface

takaiwana
Level 1
Level 1

my 1721 router is displaying the following message at regular intervals: PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver problem?

loading of the ios is also very slow. any clues of of what is causing the problem?

thanks.

4 Replies 4

erikhjacobsen
Level 1
Level 1

Please post the output of the show proc cpu and show int fa0 commands.

Ethernet0 is up, line protocol is down

Hardware is PQUICC Ethernet, address is 0004.dd0d.0aaf (bia 0004.dd0d.0aaf)

Description: Ethernet Link to Zimbabwe ISP

Internet address is 217.15.121.106/29

MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,

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

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Half-duplex, 10BaseT

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

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

Last clearing of "show interface" counters never

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

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

0 packets input, 0 bytes, 0 no buffer

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

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

0 input packets with dribble condition detected

86 packets output, 5456 bytes, 0 underruns

86 output errors, 0 collisions, 1 interface resets

0 babbles, 0 late collision, 0 deferred

86 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

FastEthernet0 is up, line protocol is up

Hardware is PQUICC_FEC, address is 000b.be95.ff08 (bia 000b.be95.ff08)

Description: LAN Interface - Zimbabwertr

Internet address is 10.5.0.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)

Auto-duplex, 10Mb/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 never

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

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 1000 bits/sec, 2 packets/sec

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

1340 packets input, 118560 bytes

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

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

0 watchdog

0 input packets with dribble condition detected

714 packets output, 139812 bytes, 0 underruns

2 output errors, 0 collisions, 1 interface resets

0 babbles, 0 late collision, 0 deferred

2 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

Virtual-Access1 is up, line protocol is up

Hardware is Virtual Access interface

MTU 1492 bytes, BW 100000 Kbit, DLY 100000 usec,

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

Base PPPoE vaccess, loopback not set

DTR is pulsed for 5 seconds on reset

Last input never, output never, output hang never

Last clearing of "show interface" counters 00:13:15

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

Queueing strategy: fifo

Output queue: 0/40 (size/max)

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

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

0 packets input, 0 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 abort

0 packets output, 0 bytes, 0 underruns

0 output errors, 0 collisions, 0 interface resets

0 output buffer failures, 0 output buffers swapped out

0 carrier transitions

even if the router is not connected to a hub or switch the error message of lost carrier still appears.

klauset
Level 1
Level 1

Sounds physical.

Most often, "Lost carrier" indicates a physical problem. Check your cabling - replace the drop cable, try another switch/hub port, test with a cross-over cable directly to a NIC if you can.

Also, be sure to lock your interface speed and Full-Duplex/Half-Duplex settings. "Auto negotiation" too often is neither.

the problem is occuring even when nothing is connected on the ethernet port.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: