Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Cisco2851 is rebooting constantly.

Hi,

I have a Cisco2851 with 2 VWIC2-2MFT-T1/E1, I'm using 3 E1 ports, but this device is rebooting constantly, so I lose data and voice service 1 or 2 minutes.

I reviewed power connections and they are Ok, I move to 3 different UPS and I got the same result.

Do you know If there are IOS commands where I can check If it has hardware problem or what else I can do?

Note: I changed the chassis 2851 5 hours ago and I got the same result.

8 REPLIES

Re: Cisco2851 is rebooting constantly.

Sounds more like an IOS bug. I would start by removing all the cards. If it's still rebooting try changing IOS. If that doesn't fix it, I would call TAC.

Hope that helps.

New Member

Re: Cisco2851 is rebooting constantly.

I have another router, same IOS, same hardware and it's working properly.

I'll remove the cards, one by one.

Thank you !.

Re: Cisco2851 is rebooting constantly.

That's the crazy thing about bugs. Some routers are affected some are not.

Hall of Fame Super Gold

Re: Cisco2851 is rebooting constantly.

That is normal, not every router sees same traffic and conditions.

You have to look at the crash message (if any) to understand what's going on.

New Member

Re: Cisco2851 is rebooting constantly.

Ok, do you know how I can see a crash message, any logs ?.

New Member

Re: Cisco2851 is rebooting constantly.

Do you know how I can see the crashinfofiles ?.

Re: Cisco2851 is rebooting constantly.

It should be in flash. Try dir /all. I believe the crash dump starts with crashfile.... Also check what the power on in show version. Example-

System returned to ROM by s/w reset

Hall of Fame Super Silver

Re: Cisco2851 is rebooting constantly.

Luis

There might be some log messages that would help to identify the issue. You can not depend on log messages sent to an external syslog server because as it crashes the router may not be able to send all of its log messages. And after it crashes and reboots there is not anything in the logging buffer that is helpful. So I would suggest that it might be good to put some PC or terminal server connected to the console of the router and displaying all of the console messages (and be sure that the console logging severity level is set to debugging). This would allow you to see any log messages generated around the time of the crash.

Also show version will usually give information about the last time that the router restarted. In the case of a crash it will sometimes have a helpful pointer to the cause of the crash. So after the next crash you might want to take a careful look at show version.

HTH

Rick

250
Views
0
Helpful
8
Replies