01-12-2017 09:35 PM
Hello. I've recently pulled some crashinfo files from a switch that encountered a failure, where all startup and running config was lost. I'd like to know what the procedure is for analyzing the crashinfo files and hopefully find the source of error.
Solved! Go to Solution.
01-13-2017 12:57 AM
So crash files are only for TAC , that's why there are no released documents specifying how to read them , they have their own systems that are able to analyse the code that's provided in them
saying that if you open them up sometimes I have found the fault in them but there difficult to read , but most of the traceback outputs are not public so its very difficult to find the reason for them without TAC , you could run your show tech through the cli analyser and see if it pulls a bug for you but even tat I don't think can read a crash file and that's the most powerful tool available to public
If you still need assistance after following the troubleshooting steps above, and want to open a service request with the Cisco TAC, be sure to include the following information for troubleshooting a router crash: |
---|
Note: Please do not manually reload or power-cycle the router before collecting the above information unless required to troubleshoot a router crash, as this can cause important information to be lost that is needed for determining the root cause of the problem. |
01-13-2017 12:57 AM
So crash files are only for TAC , that's why there are no released documents specifying how to read them , they have their own systems that are able to analyse the code that's provided in them
saying that if you open them up sometimes I have found the fault in them but there difficult to read , but most of the traceback outputs are not public so its very difficult to find the reason for them without TAC , you could run your show tech through the cli analyser and see if it pulls a bug for you but even tat I don't think can read a crash file and that's the most powerful tool available to public
If you still need assistance after following the troubleshooting steps above, and want to open a service request with the Cisco TAC, be sure to include the following information for troubleshooting a router crash: |
---|
Note: Please do not manually reload or power-cycle the router before collecting the above information unless required to troubleshoot a router crash, as this can cause important information to be lost that is needed for determining the root cause of the problem. |
01-13-2017 08:37 PM
I see, thank you for this information. It explains a lot.
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