Cisco 1841 hung up - works fine after restart

Just wanted to add that there are two links connected to this 1841 router (Ethernet and Serial) and both were inaccessible until the router was restarted.

So, I dont think that it was a card problem or interface problem. this happened early in the morning, so i dont think that the router was pounded with too much traffic that it hung and required a restart.

Hello Gautam,

you could configure syslogging, check this link for a free Syslog Daemon, which you can install on any Windows machine:

Kiwi Syslog Daemon

On your router, you would the issue the global command 'logging x.x.x.x', where x.x.x.x is the IP address of the machine where the syslog daemon is installed. The reasons for the hung router can be many, including a software bug, or a temporary high CPU utilization. What is configured on the router ? If possible, can you post the router's configuration, as well as the output of 'show version' ?

Regards,

H

Please post IOS version loaded on the router

Hi friends,

Thanks a lot for your responses. As asked, I am posting the output of show version and show run

Show run Building configuration...

Current configuration : 4005 bytes ! version 12.4 service timestamps debug datetime msec service timestamps log datetime msec service password-encryption ! hostname BSNL-Flower ! boot-start-marker boot-end-marker ! logging buffered 10000 debugging no logging console enable secret 5 $1$1yqH$TY.ofCML7f1fiG8V9OeK90 ! no aaa new-model ! resource policy ! mmi polling-interval 60 no mmi auto-configure no mmi pvc mmi snmp-timeout 180 no ip subnet-zero ip cef ! ! no ip dhcp use vrf connected ! ! ! ! ! controller E1 0/0/0 channel-group 0 unframed ! controller E1 0/0/1 channel-group 0 unframed ! ! interface FastEthernet0/0 description "For RF Connectivity" bandwidth 1024 ip address 172.26.206.4 255.255.255.248 duplex auto speed auto ! interface FastEthernet0/1 ip address 10.1.3.1 255.255.255.0 duplex auto speed auto ! interface Serial0/0/0:0 description "FOR Leased Line Connectivity" bandwidth 2048 ip address 172.26.206.14 255.255.255.252 ! interface Serial0/0/1:0 description "FOR Leased Line Connectivity" ip address 192.168.213.49 255.255.255.252 ! router eigrp 100 redistribute connected redistribute static network 172.26.206.4 0.0.0.0 network 172.26.206.14 0.0.0.0 distance eigrp 50 60 no auto-summary ! ip classless ip route 10.0.1.16 255.255.255.248 192.168.213.50 ip route 10.249.0.8 255.255.255.248 192.168.213.50 ip route 172.26.11.0 255.255.255.0 192.168.213.50 ip route 172.26.12.0 255.255.255.0 192.168.213.50 ip route 172.26.13.0 255.255.255.0 192.168.213.50 ip route 172.26.14.0 255.255.255.0 192.168.213.50 ip route 172.26.15.0 255.255.255.0 192.168.213.50 ip route 172.26.16.0 255.255.255.0 192.168.213.50 ip route 172.26.49.0 255.255.255.0 192.168.213.50 ip route 172.26.50.0 255.255.255.0 192.168.213.50 ip route 172.26.51.0 255.255.255.0 192.168.213.50 ip route 172.26.52.0 255.255.255.0 192.168.213.50 ip route 172.26.54.0 255.255.255.0 192.168.213.50 ip route 172.26.55.0 255.255.255.0 192.168.213.50 ip route 172.26.56.0 255.255.255.0 192.168.213.50 ip route 172.26.57.0 255.255.255.0 192.168.213.50 ip route 172.26.65.0 255.255.255.0 192.168.213.50 ip route 172.26.66.0 255.255.255.0 192.168.213.50 ip route 172.26.67.0 255.255.255.0 192.168.213.50 ip route 172.26.68.0 255.255.255.0 192.168.213.50 ip route 172.26.70.0 255.255.255.0 192.168.213.50 ip route 172.26.85.0 255.255.255.0 192.168.213.50 ip route 172.26.101.0 255.255.255.0 192.168.213.50 ip route 172.26.103.0 255.255.255.0 192.168.213.50 ip route 172.26.110.0 255.255.255.0 192.168.213.50 ip route 172.26.122.0 255.255.255.0 192.168.213.50 ip route 192.168.4.8 255.255.255.252 192.168.213.50 ip route 192.168.117.0 255.255.255.0 192.168.213.50 ip route 192.168.140.172 255.255.255.252 192.168.213.50 ip route 192.168.140.176 255.255.255.252 192.168.213.50 ip route 192.168.140.180 255.255.255.252 192.168.213.50 ip route 192.168.140.184 255.255.255.252 192.168.213.50 ip route 192.168.155.220 255.255.255.252 192.168.213.50 ip route 192.168.155.224 255.255.255.252 192.168.213.50 ip route 192.168.165.84 255.255.255.252 192.168.213.50 ip route 192.168.196.80 255.255.255.252 192.168.213.50 ip route 192.168.196.88 255.255.255.252 192.168.213.50 ip route 192.168.196.224 255.255.255.252 192.168.213.50 ip route 192.168.213.52 255.255.255.252 192.168.213.50 ip route 192.168.213.56 255.255.255.252 192.168.213.50 ip route 192.168.213.60 255.255.255.252 192.168.213.50 ip route 192.168.213.68 255.255.255.252 192.168.213.50 ip route 192.168.213.72 255.255.255.252 192.168.213.50 ip route 192.168.213.76 255.255.255.252 192.168.213.50 ip route 192.168.214.100 255.255.255.252 192.168.213.50 ip route 192.168.228.164 255.255.255.252 192.168.213.50 ip route 192.168.235.100 255.255.255.252 192.168.213.50 ip route 192.168.235.124 255.255.255.252 192.168.213.50 ip route 192.168.244.176 255.255.255.252 192.168.213.50 ip route 192.168.244.180 255.255.255.252 192.168.213.50 ! ip http server ! snmp-server community public RO disable-eadi ! control-plane ! ! line con 0 line aux 0 line vty 0 4 password 7 13061E010803 login ! end

Show version

Cisco IOS Software, 1841 Software (C1841-IPBASE-M), Version 12.4(1a), RELEASE SO FTWARE (fc2) Technical Support:

(c) 1986-2005 by Cisco Systems, Inc. Compiled Fri 27-May-05 12:32 by hqluong

ROM: System Bootstrap, Version 12.3(8r)T8, RELEASE SOFTWARE (fc1)

BSNL-Flower uptime is 1 day, 1 hour, 2 minutes System returned to ROM by power-on System image file is "flash:c1841-ipbase-mz.124-1a.bin"

Cisco 1841 (revision 5.0) with 114688K/16384K bytes of memory. Processor board ID FHK09303053

2 FastEthernet interfaces 2 Serial interfaces 2 Channelized E1/PRI ports DRAM configuration is 64 bits wide with parity disabled. 191K bytes of NVRAM. 31360K bytes of ATA CompactFlash (Read/Write)

Configuration register is 0x2102

Merv wrote:

Mostly when a Cisco router restart suddenly, it's because an an IOS bug, but after restarted and you run Sh run, you should get the reason.

For example:

Router#show version Cisco Internetwork Operating System Software IOS (tm) RSP Software (RSP-PV-M), Version 12.0(10.6)ST, EARLY DEPLOYMENT MAINTENANCE INTERIM SOFTWARE Copyright (c) 1986-2000 by cisco Systems, Inc. Compiled Fri 23-Jun-00 16:02 by richv Image text-base: 0x60010908, data-base: 0x60D96000

ROM: System Bootstrap, Version 12.0(19990806:174725), DEVELOPMENT SOFTWARE BOOTFLASH: RSP Software (RSP-BOOT-M), Version 12.0(9)S, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)

Router uptime is 20 hours, 56 minutes System returned to ROM by error - a Software forced crash, PC

0x60287EE8 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

System image file is "slot0:rsp-pv-mz.120-10.6.ST"

. . .

try to get the output of a show version, show stacks, show context, or show tech support command from your Cisco device, they will help you to determine the reason was due to Hardware, memory o IOS.

show stacks

---------- It's used to monitor the stack usage of processes and interrupt routines. The show stacks output is one of the most indispensable sources of information to collect when the router crashes.

show context

------------ It's used to display information stored in nonvolatile RAM (NVRAM) when an exception occurs.

There's a crashinfo file, it's a collection of useful information related to the current crash, stored in bootflash or flash memory. When a router crashes due to data or stack corruption, more reload information is needed to debug this type of crash than just the output from the normal show stacks command. Try running the Sh dir or Sh flash to see the crashinfo file

You are running the FIRST release of a major new IOS version - it is not a big surprise that you are having an issue.

Is this the IOS version that was shipped with the unit or did the unit get upgraded to this version after it was installed?

If you did not implement 12.4 to obtain a specific product feature only available in 12.4, then I would recommend you either upgrade to

12.4(3c) or better move to the 12.3 stream @ 12.3(14)T6 should the current problem reoccur

BTW since all your statics point to the same next hop - you could just point default at 192.168.213.50 to simplify you config:

ip classless ip route 0.0.0.0 0.0.0.0 192.168.213.50

Lastly what is the reason behind changing the default admin distance for EIGRP; just curious ...