Cisco 2600 crashes frequently

[Guest_imported]

hi-

We are a small company using a Cisco 2600 as our internet gateway. The 2600 crashes frequently- sometimes once a week, sometimes twice a day. After a crash, I can't ping it or connect through a direct terminal connection. I end up manually switching the power off and on to restart it (i am a Cisco newbie- do i have another option in this situation?).

Ultimately I want to figure out the cause of these crashes. How can i get more information about what is going on? I will submit the config if that would help.

Any help would be greatly appreciated.

 

[BOJIKA]

try inspect your Cisco-router
#sh proc
#sh mem

also you may configure cisco router for regular reload, for example every night... at 02:00

 

[wybnormal]

There is not any reason to constantly reboot a router. This is not NT ;-)

Turn on logging and get a copy of syslog daemon. I have a trial version from solarwinds at

http://www.packetattack.com

under helpful downloads. Install it and point the router to it. That is one step.

Check your memory... sho proc mem and make sure you are not hitting the wall due to routing protocols like OSPF, EIGRP or god forbid, BGP. Bad memory chips can do this.. I just sent a 2620 back on RMA that would overheat a chip and die without warning after 30 minutes or so.

The router can run as high as 70% CPU and still have some power left.. so sayth Cisco.. myself, I get worried at 50% substained and at 70, I'm replacing the router with more horsepower.

Your milage WILL vary ;-)

MikeS
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin

 

[jeter]

Looks like Mike has this one under control, Good Job!

I would like to add a few things as I have had a 2600 do the
same and I had to upgrade the image. 12.1
Do a show version and a sh ip int brief Jeter@LasVegas.com
J.Fisher CCNA

 

[Guest_imported]

Thank you for the replies.

I have set up logging to a syslog server. I just ran the command &quot;logging <server ip>&quot;. Are there any special logging settings i should add, or are the defaults ok?

Running 'sho proc mem' shows:
total: 22399708, Used: 3027236, Free: 19372472
which i assume means i have plenty free.

please bear with me, i am definitely a newbie to cisco. How can i tell if i am &quot;hitting the wall due to routing protocols&quot; as you suggest?

I guess now i wait until next time to see if anything is logged. I'm sure it will happen again. Please let me know if I should add any logging settings to make sure i get as much info as possible.

Thank you!!!

 

[wybnormal]

Do a show proc CPU and see what the trend is.. if you are running NAT, that will chew up the CPU clock cycles in a hurry. Your memory looks fine.. right now. What protocol are you using for routing? OSPF? RIP?

Get a copy of solarwinds.. they have a 30 day demo which gives all sorts of tools for this sort of debugging.. one is a CPU load counter. Uses SNMP to talk with the router.

http://solarwinds.net

MikeS
&quot;Diplomacy; the art of saying 'nice doggie' till you can find a rock&quot; Wynn Catlin