In this last chapter, we will put the troubleshooting methods and skills that you learned in previous chapters to the test. We will perform a root cause analysis of one of the most difficult real-world scenarios: an unexpected reboot.
As we discussed in Chapter 1, Troubleshooting Best Practices, a root cause analysis is a bit more involved than simply troubleshooting and resolving an issue. In Enterprise environments, you will find that every issue that causes a significant impact will require a root cause analysis (RCA). The reason for this is because Enterprise environments often have well-established processes of how incidents are supposed to be handled.
In general, when a significant incident occurs, the organization impacted by it wants to avoid it from happening again. You can see this in many industries even outside of technical environments.
As we discussed in Chapter 1, Troubleshooting Best Practices, a useful RCA has the following...