Troubleshooting Lab Challenge 2:
|Note: We created this lab challenge to help you get some practice with networking problems only. These labs are only for fun and do not appear in the TSHOOT exam.
Recently our corporation has just acquired some companies. Our networking engineers are working to merge their networks into ours. An engineer has edited the network configuration and now our users are experiencing network issues. They have contacted you to resolve the issues and return the network to full functionality.
Below are the IPv4 Layer 3 Topology and IPv6 Topology (No switch is used in this challenge so we don’t have a Layer 2 Topology):
For the TSHOOTv2 exam we will encounter:
+ 1 Simlet (small troubleshooting sim)
+ Multiple Choice Questions
+ 13 Troubleshooting Tickets (check them at the right-side menu)
Notice that in the exam, the tickets are randomly given so the best way to troubleshooting is to try pinging to all the devices from nearest to farthest from the client until you don’t receive the replies.
In each ticket you will have to answers three types of questions:
+ Which device causes problem
+ Which technology is used
+ How to fix it
One more thing to remember: you can only use “show” commands to find out the problems and you are not allowed to make any changes in the configuration. In fact, in the exam you can not enter the global configuration mode!
Screenshots for your reference:
(Please visit Share your TSHOOT v2.0 Experience for bigger images)
Also you can find more information about TSHOOT exam in TSHOOT FAQs and Tips.
Note: We created this lab challenge to help you get some practice with networking problems only. These labs are only for fun and do not appear in the TSHOOT exam. Please let us know if you like this simulator or not so that we can continue making other simulators in the future. Any suggestion, recommendation, error reports are warmly welcomed!
Troubleshooting Lab Challenge 1:
A network engineer has edited their network configuration and now your customer is experiencing network issues. Some reports said that users connected to CLIENT router (R4) cannot reach the services located at SERVER router (R3). They have contacted you to resolve the issues and return the network to full functionality.