Re: Different between the last reload ressions types

Munther · ‎06-07-2022

Hi Dears,

I have two Switches C9500-24Y4C, i upgraded them from version 16.12.4 to 17.3.5, after reload when run show version i got two different reason for reload :

Switch 1 :
Uptime for this control processor is 2 hours, 9 minutes
System returned to ROM by Image Install at 06:23:41 BGH Tue Jul 14 2020
System restarted at 07:12:30 BGH Wed Jun 8 2022
System image file is "bootflash:packages.conf"
Last reload reason: Image Install

------

Switch 2 :

Uptime for this control processor is 1 hour, 55 minutes
System returned to ROM by LocalSoft at 18:35:10 BGH Sat May 9 2020
System restarted at 07:28:52 BGH Wed Jun 8 2022
System image file is "bootflash:packages.conf"
Last reload reason: LocalSoft

----------------

what is different between LocalSoft and Image Install and why i got two different reasons while the two switches are a same model and upgraded with the same image.

Thanks.

Leo Laohoo · ‎06-07-2022

@Munther wrote:

System returned to ROM by Image Install at 06:23:41 BGH Tue Jul 14 2020

Last reload reason: Image Install

Reload was "automatic" because of Install Mode command. This is as expected.

@Munther wrote:

System returned to ROM by LocalSoft at 18:35:10 BGH Sat May 9 2020
Last reload reason: LocalSoft

Depending on the firmware version, this is due to a crash with an unknown cause. "LocalSoft" is a "generic" crash reason.

Post the complete output to the following commands:

sh log on switch 2 uptime detail
dir flash-2:/core
dir crashinfo-2:

Munther · ‎06-08-2022

@Leo Laohoo
Thanks for your reply, here is the show log , dir flash and dir crash info for switch 2.

Leo Laohoo · ‎06-08-2022

Try again.

Those are the wrong commands.

MHM Cisco World · ‎06-08-2022

I see log
"""Rx power high warning; Operating value: """
it may be the reason why the reboot reason different...
check it.

Munther · ‎06-08-2022

Hi @Leo Laohoo

i tried with these commands, but it is did not work

sh log uptime detail
dir flash-2:/core
dir crashinfo-2

#dir flash-2:/core
^
% Invalid input detected at '^' marker.

#dir crashinfo-2
%Error opening bootflash:/crashinfo-2 (No such file or directory)

Leo Laohoo · ‎06-08-2022

@Munther wrote:

#dir crashinfo-2
%Error opening bootflash:/crashinfo-2 (No such file or directory)

That is still the wrong command. There is a colon missing at the end.

Post the complete output to the command:

dir crashinfo-2:
dir bootflash-2:
dir bootflash-2:core

Munther · ‎06-08-2022

@Leo Laohoo

#dir crashinfo-2:
% Invalid input detected at '^' marker.

#dir bootflash-2:
% Invalid input detected at '^' marker.

--

#dir ?
/all List all files
/recursive List files recursively
all-filesystems List files on all filesystems
bootflash: Directory or file name
cns: Directory or file name
crashinfo: Directory or file name
flash: Directory or file name
null: Directory or file name
nvram: Directory or file name
system: Directory or file name
tar: Directory or file name
tmpsys: Directory or file name
webui: Directory or file name
| Output modifiers
<cr> <cr>

Leo Laohoo · ‎06-08-2022

This means switch-2 is either offline or split-brain.

Georg Pauwen · ‎06-08-2022

Hello,

there is a bug which might be related:

Cat9300/C9500/C9500H switches may reload with last reload reason as LocalSoft or CpuCatastrophicErr
CSCvr77861
Customer Visible
Notifications
Save Bug
Open Support Case
Description
Symptom:
A Cat9300, Cat9500, or Cat9500H series switch may see an unexpected/silent reload and recover with a reload reason of Localsoft or CpuCatastrophicError listed under the show version output.

Conditions:
First observed on Cat9300, 9500, and 9500H series switches running both 16.9.x and 16.12.x based software that recover with no crash files in the local file system directory.

It is possible that other software may also see this, and it is not specific to these releases.

Workaround:
A preventative fix has been committed which is expected to prevent the vast majority of incidents.

Fixes are available 16.9.7, 16.12.5, and 17.3.3 and higher IOS releases.

Further Problem Description:
At the time of this writing, based on field data, the majority of devices that see this condition will only see it once, and should be monitored after such an event to confirm it is likely a one-off problem. Essentially, this issue can be treated like a parity error, in that its very rare, and unlikely to happen more than once.

There are a small number of devices which have seen this problem more than once. If you have a switch that experiences this silent reload two or more times, it is recommended to upgrade to a fixed-in release which should contain a preventative fix.

Munther · ‎06-08-2022

Hi @Georg Pauwen

may be this is a reason , thanks