09-27-2022 12:05 PM
The results from a recent pre-upgrade check are reporting that the "Safeshut Workaround" is "Needed." The comment is, "Contact TAC".
I did some research, but I cannot find any substantive information at the Cisco site or elsewhere. I resorted to reading through the Python script for information about it. Based on a condition statement in the code, it appears be "true" for UCS versions 2.2 older than "6c".
What is the issue and the workaround? Is this something I should be concerned about? (The fact that it is recommending a TAC call makes me reluctant to ignore it.)
Any insight would be appreciated. Thank you.
05-11-2023 02:04 AM
05-11-2023 05:15 AM - edited 05-11-2023 05:18 AM
Just to clarify the safeshut script was introduced to prevent filesystem corruption on the FI's during reboot for customers on code that was not yet fixed by CSCuu33864 (https://bst.cisco.com/bugsearch/bug/CSCuu33864) prior to 2.2(6c). It is not related to blade power.
If running unfixed code prior to 2.2(6c) TAC would SSH into the FI's and launch the debug plugin to load some scripts and drivers to help mitigate the possibility of filesystem corruption during FI reboot.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide