cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Join Customer Connection to register!
501
Views
4
Helpful
4
Replies
dave dave
Beginner

switch issue - self reboot

hi! recently we've a issue with one of the L3 3560 switch running on ios 12.2(53r)se2. The switch will restart intermittently for at least 5 times a day. It's getting more and more frequent. I noticed that this issue will still occur even though the CPU utilization has dropped to below 20%. Thus, i've upgrade the ios version to the latest version 15.0(2)se, but that do not resolve the issue.

I searched through the internet and it seems that there's a file called crashinfo in the flash drive htat can provide some clues on why the system reset by itself. I issue a dir command on the switch, and here's the output. I did not see any crashinfo there. Any idea where i can retrieve this file, and what shd i look out for in this file to determine the cause of the switch reboot? Thx.

Directory of flash:/

    2  -rwx        1036  Mar 1 1993 05:31:30 +05:00  vlan.dat

    3  -rwx      10697  Oct 1 2012 15:15:12 +05:00  config.text

    4  -rwx    19680178  Oct 1 2012 12:49:19 +05:00  c3560e-universalk9-mz.150-2.SE.bin

    5  -rwx        1919  Oct 1 2012 15:15:12 +05:00  private-config.text

  443  -rwx        5144  Mar 1 1993 05:31:38 +05:00  multiple-fs

    7  drwx        512  Mar 1 1993 05:45:52 +05:00  c3560e-universalk9-mz.122-53.SE2

4 REPLIES 4
will.cullen
Beginner

You could try the following:

show ver - look out for System returned I think under uptime

show log - log file on the switch

In the show log output, nothing constructive there. However in the sh ver command. There's a msg "System returned to rom by power-on". Seems to be an power interuption msg?? I checked the sh env, the hardware are all fine, i've also changed to another power socket. What could be other causes for this?

Sh log won't help since that is just stored in RAM, it will be lost during a reboot. If you can setup a SysLog server and set the switch using the logging XXX.XXX.XXX.XXX (where x is the server IP) so that any log messages sent right before the reboot are captured.

Also you could try an battery backup with voltage regulation to see if it is a power issue.

You probably already went down this road....

Are all the power sockets on the same circuit?

Do you notice any other devices that are on the same socket reboot?

Agree with the UPS call, a managed UPS normally shows power issues if they exist.