Some people find templates helpful when creating Wiki articles. This one is intended to help those writing test lab guide (TLG) troubleshooting scenario content, in which you describe how to take someone through a troubleshooting scenario based on a working test lab, either the Base Configuration test lab or a test lab based on a modular TLG.

In a troubleshooting scenario, you deliberately break the configuration of the test lab, show the results, and then use recommended troubleshooting tools and methodology to determine the root cause and correct the configuration. A troubleshooting scenario is designed to teach troubleshooting skills for common problems in the controlled environment of the test lab. A Test Lab Troubleshooting Scenario can extend an existing Troubleshooting TLG. For more information, see Test Lab Guides.

This template is a work in progress, please add to it.

Feel free to copy/paste the template below into your TLG troubleshooting scenario Wiki article to help get you started. It is a best practice to leave an area that you cannot currently fill in blank. This way others can fill it in if they have the information. This is called "stubbing" on the wiki.

Test Lab Guide Troubleshooting Scenario Template

<discussion of technology/product requirement or process that provides context for the troubleshooting scenario and the following subsections>

In this troubleshooting scenario, you will configure <root cause that breaks the test lab> and then troubleshoot the results.

Break the configuration procedure

Follow these steps to configure the <technology/product> test lab for this troubleshooting scenario.

To <break procedure title>

  1.  <steps to break the test lab and demonstrate its broken state>


Step-by-step troubleshooting

From the previous procedure, it appears that <problem statement>. The following procedure uses the appropriate steps in <links to appropriate topics in technology/product Troubleshooting Guide> to determine the root cause of the problem.

To troubleshoot this scenario

  1. <steps to perform root cause troubleshooting of the problem, the last step clearly demonstrates or determines the root cause>

 This is the root cause of the problem. <discussion of why the root cause impairs the demonstrated functionality>

Correct the configuration procedure

Follow these steps to correct the configuration of the <product/technology> test lab for this troubleshooting scenario.

To configure <correction procedure title>