discovering the reload reason for a specific switch in a stack

[Alex-Pr]

Is there a way to tell why a switch within a stack rebooted?

I have a stack of 2960X's and the non master switch has rebooted.  I am trying to figure out why.

When doing Show Version, the uptime and reload reason is based on when the overall stack last booted which was a while ago.

When I check the directory of flash2:/ (or even flash1) there is no crash file.

Both switches are plugged into the same UPS and the power cables seem solid...

Thanks

[balaji.bandi]

show version give you the uptime and reason of the switch, if the switch is crashed you may see crash logs in flashX: X is switch number ( since you mentioned there no crash) its hard to define what went wrong.

show logg from master you can see why it was rebooted ? also you can connect the console the rebooted switch and check

[Reza Sharifi]

Maybe you can look at the log of the member switch by using the session command "session x" from the master.

See link for more info:

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2960x/software/15-0_2_EX/stack_manager/command_reference/b_stck_152ex_2960-x_cr/b_stck_152ex_2960-x_cr_chapter_01.html

HTH 

[Leo Laohoo · Accepted solution]

dir flash<SWITCH NUMBER>:
remote command <SWITCH NUMBER> sh version
remote command <SWITCH NUMBER> sh log onb uptime detail