OPERATIONAL DEFECT DATABASE
...
...
Cat9300/Cat9500 switches may see silent reloads with last reload reason as LocalSoft or CpuCatastrophicError. There is no corefile/system report generated.
First observed on Cat9300 & Cat9500 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. NOTE - This defect is for the non-L series Cat9300. NOTE - This symptom can be seen for Cat9500H series switches. CSCvr77861 is tracking this issue and fixes specific for the Cat9500H
A preventative fix has been committed which is expected to prevent the vast majority of incidents. Two defects have been filed to address this issue across the different impacted platforms. CSCvr77861 will carry 9500H specific fixes and CSCvw74061 will carry Cat9300 and Cat9500 specific fixes. fixes are avaiable in the following releases: 16.9.7, 16.12.5, 17.3.3, 17.5.1, 17.6.2, 17.8.1, 17.9.1 and later releases.
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. These fixes are 16.9.7, 16.12.5, 17.3.3, 17.5.1, 17.6.2, 17.8,1, 17.9.1 and beyond. If after a software upgrade multiple unexpected reloads are still seen, it is recommended to contact TAC for further assistance referencing this defect.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
