|
Answer» Hi there,
I'm having some problems with a Cisco 1721 & WIC-1ENET.
I've got it setup as part of a Cisco site to site VPN, and now the 1721 doesn't respond on the eth0 interface anymore. When I log on to the console connection I am able to ping the tunnel (through the fa int) and the network (192.168.1.x subnet) on the other side, but I am not able to ping the eth0 interface from my LAN (192.168.2.x subnet)
Here's the show int eth0:
Ethernet0 is up, line protocol is down Hardware is PQUICC Ethernet, address is 0004.dc0c.b55b (bia 0004.dc0c.b55b) Internet address is 192.168.2.250/24 MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 10BaseT ARP type: ARPA, ARP Timeout 04:00:00 Last input never, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 244 Queueing strategy: fifo Output queue: 40/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 input packets with DRIBBLE condition detected 32 packets output, 3719 bytes, 0 underruns 0 output errors, 0 collisions, 3 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 wasn't having problems yesterday, but this morning I was unable to ping "through" the 1721 to the 192.168.1.x subnet.
Also, there are no link lights on the WIC, or on the switch it is plugged into. I have tried a different cable and a different switch port, as well as REBOOTING (switching off and on) the router (a couple of times) and issuing a shut and then no shut to the eth0 int.
Anybody got any ideas on how to troubleshoot this further, as I'm at a total loss.
(Thanks for you time and help)
Please note, out of paranoia I've changed the IP's
Well I don't how many Cisco guys hang out at these BOARDS so you may have a tough time getting your question answered. However, from my days of studying Cisco I can remember if your line protocol is down then it is due to either "keepalive settings" or an "encapsulation settings". Somehow one of these has changed. I couldn't tell you what commands you need to run to check these but it should give you a clue as to where to start focusing. Also, have you searched for "line protocol is down"? I'm sure you will get enough results to help you with this.I did have a look around on the web but couldn't find anything that worked.
I ended up taking the router out of the system, stripping it down to look for signs of PHYSICAL damage, reseating the WIC and then it worked.
I think the WIC just overheated.
|