Cisco Pros: Is my router dead?

[y2kc]

Long story short, my cisco 1605R Ethernet 1 interface appears to be dead. I have a link light but I can't even ping it from the console. Here is the message I'm getting; "%QUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver problem?" Ethernet 0 is fine btw.

 

[spidey07]

don't know 1600 model numbers - guessing it has two ether ports right?

that message is normal for an ethernet interface that has no carrier (not connected to another ethernet device). go into the config and shut the interface down with:
conf t
int e0
shut
^Z

If this doesn't describe your symptoms then please post the full results of "show interface"

 

[y2kc]

Yeah, it has two ether ports and I verified the connection it had (out of the hub, into the router interface) I ran the same cable from the hub directly into my PC, changed the IP and boom, I was getting out again. I did try a shut/no shut but still no go. Here's the results of "sh int e1"

Router#sh int e1
Ethernet1 is up, line protocol is up
Hardware is QUICC Ethernet, address is 00d0.xxxx.211d (bia 00d0.58a4.211d)
Internet address is xx.xx.xx.xxx/24
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 177/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:04, output 00:00:08, 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 0 bits/sec, 1 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
278 packets input, 17397 bytes, 0 no buffer
Received 275 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 input packets with dribble condition detected
263 packets output, 20206 bytes, 0 underruns
223 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
223 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out

Thanks for taking a look at this spidey and BTW, good luck with your upcoming CCIE Lab test.

 

[y2kc]

bump (just in case)

 

[spidey07]

<< 223 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
223 lost carrier, 0 no carrier
>>



that is a lot of output errors and lost carrier (the message you're getting). I'd swap cables or hub/switch ports. also you can type "show controller e1" for more granular details. sounds like cabling/hub problem but you could always call cisco for more indepth thoubleshooting/RMA. also check speed duplex settings on the hub/switch your attaching to.

 

[y2kc]

Thanks spidey, I cleared the counters on both interfaces and that seems to have solved the problem (for now). I spoke with a friend who says that the router may be on it's way out.....we will see.

 

[Damaged]

Well clearing the counters doesn't do anything except reset those counters. Just clears statitisitics. So I doubt that actually fixed the problem. Unless you mistakenly did a clear int ethX, which clears the hardware logic on the interface. clear counters ethX would clear the counters. Easy to make that mistake.

The message you're receiving simply means that the transceiver is having a problem. Most likely and usually a cabling issue (e.g. bad cable, wrong type, etc).

spidey, eth ints on 16xx series only do 10 half so we don't have to worry about that problem. 🙂

Finally, just because a cable works in one device doesn't mean you shouldn't try a different cable anyways. Some things are pickier than others. And it's easy enough to do. Most times what I'll do is check both ends of and ethernet cable making sure the crimp appears good, then I'll pull up on the little tab to make it fit better. Then plug it back in.

 

[y2kc]

Damaged, you are correct sir. I cleared the interfaces, not the counters (one should think before one types). I just took a look at each interface and I see no output errors after several hours, however I will change the cables. Thanks.

 

[Damaged]

Sounds like something just got a bit freaked in the interfaces logic is all. No biggee, happens sometimes. If it's working now with no errors I would say you've fixed the problem. And you learned something as well.

All's well that ends well. 🙂