UC520 powercycles

Answered Question
Oct 7th, 2009
User Badges:
  • Silver, 250 points or more

Hi,


I'm having a trouble with a 32user model. The UC powercycles from time to time. Any idea on how to start troubleshoot. I'm going to place a pc for logging with a syslog server.


Thanks,

Eivind

Correct Answer by Saurabh Verma about 7 years 9 months ago

A powercycle is normally caused due to an exception in the Software, could also occur due to memory related issues, or because the platform wasn't able to handle the load (high CPU). Debugs won't be of much help until we know what's causing the failure. It would certainly not be helpful for CPU or memory related issues since these are more related to the processes that are running on the system and the memory allocation/de-allocation. If you were able to locate a crash-info file on the flash, I can look at it and provide some guidance. You could also look at the output of "show version" to see the last reload reason.


Thanks,
Saurabh

Correct Answer by Saurabh Verma about 7 years 9 months ago

I think that's a good start. You could also look at the flash to see if there is any "crash info" file. I would suggest that you open a TAC SR to have an engineer look at it in detail.


Thanks,

Saurabh

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Correct Answer
Saurabh Verma Wed, 10/07/2009 - 05:41
User Badges:
  • Silver, 250 points or more

I think that's a good start. You could also look at the flash to see if there is any "crash info" file. I would suggest that you open a TAC SR to have an engineer look at it in detail.


Thanks,

Saurabh

Eivind Jonassen Wed, 10/07/2009 - 08:31
User Badges:
  • Silver, 250 points or more

Do you have any recommendation on good debug commands I could use that could be related to the powercycle?!?!


Thanks,

Eivind

Correct Answer
Saurabh Verma Wed, 10/07/2009 - 09:07
User Badges:
  • Silver, 250 points or more

A powercycle is normally caused due to an exception in the Software, could also occur due to memory related issues, or because the platform wasn't able to handle the load (high CPU). Debugs won't be of much help until we know what's causing the failure. It would certainly not be helpful for CPU or memory related issues since these are more related to the processes that are running on the system and the memory allocation/de-allocation. If you were able to locate a crash-info file on the flash, I can look at it and provide some guidance. You could also look at the output of "show version" to see the last reload reason.


Thanks,
Saurabh

Actions

This Discussion

Related Content