Guide Category

A guide for the TSHOOT Exam

March 7th, 2019 networktut 987 comments

For the TSHOOTv2 exam we will encounter:

2 Simlets (small troubleshooting sim)
+ Multiple Choice Questions & Drag Drop Questions
+ 12 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 answer 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” and “ping” 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.

Practice TSHOOT Tickets with Packet Tracer & EVE-NG

March 6th, 2019 networktut 567 comments

Special thanks to Buddy who sent us these files. Please say thanks to him. Now you can practice most TSHOOT Tickets with Packet Tracer v6.1. Please download all the tickets in one file here: All the guides were included in that file.

Note: Please use at least the final Packet Tracer v6.1 (STUDENT Release) or above to open them. Below is a screenshot of the pkt files:


From Buddy:

Please notice: It’s mainly all the Packet Tracer TSHOOT L2 based trouble tickets, that needs to be reconfigured with STATIC IP addresses at the PC Clients by today

Thus when reconfiguring the two PC Clients with static IP addresses, please remember to also EXCLUDE the two Client IP addresses (.3 and .4) within the DHCP Pool at DHCP Server R4, at the same time.


Special thanks to Marcus for creating the TSHOOT topology with EVE-NG network emulator (currently this is one topology file with working configuration, not the tickets). You can download this file here: Below is screenshot of the EVE-NG file:


+ EVE-NG emulator must be installed to open this file.
+ This file uses these IOL images (but you may use other IOL images):
 – i86bi_LinuxL2-AdvEnterpriseK9-M_152_May_2018.bin
 – i86bi_LinuxL3-AdvEnterpriseK9-M2_157_3_May_2018.bin
+ Importing steps:
1. click ACTIONS/Import external labs
2. select target lab but don’t unzip it then import
3. BEFORE starting any nodes on ASW1,ASW2,DSW1,DSW2 select the Layer2 IOL image that is present in your eve.
4. click More actions/Start all nodes

HSRP IP Route Tracking

May 13th, 2013 networktut 88 comments

In this article we will discuss about HSRP and do a lab on it.

Quick reminder about HSRP

+ Hot Standby Router Protocol (HSRP) is a Cisco proprietary protocol.
+ With HSRP, two or more devices support a virtual router with a fictitious MAC address and unique IP address
+ Hosts use this IP address as their default gateway and the MAC address for the Layer 2 header
+ The virtual router’s MAC address is 0000.0c07.ACxx , in which xx is the HSRP group. Multiple groups (virtual routers) are allowed.
+ The Active router forwards traffic. The Standby router is backup and monitors periodic hellos (multicast to,
UDP port 1985) to detect a failure of the active router.
+ The active router is chosen because it has the highest HSRP priority (default priority is 100). In case of a tie, the router
with the highest configured IP address wins the election
+ A new router with a higher priority does not cause an election unless it is configured to preempt.

HSRP States

+ Initial: HSRP is not running.
+ Learn: The router does not know the virtual IP address and is waiting to hear from the active router.
+ Listen: The router knows the IP and MAC of the virtual router, but it is not the active or standby router.
+ Speak: Router sends periodic HSRP hellos and participates in the election of the active router.
+ Standby: Router monitors hellos from active router and assumes responsibility if active router fails.
+ Active:Router forwards packets on behalf of the virtual router.

Load balancing traffic across two uplinks to two HSRP routers with a single HSRP group is not possible. The trick is to use two
HSRP groups:
+ One group assigns an active router to one switch.
+ The other group assigns another active router to the other switch.

(Reference: SWITCH official Certification Guide)

That is all for the boring HSRP theory, let do a lab to understand more about HSRP! We will use the topology below for this lab:


Read more…

Frame Relay Point-to-Point SubInterface GNS3 Lab

April 30th, 2013 networktut 30 comments

In this lab we will try to run a Frame Relay topology same as the one posted in TSHOOT demo ticket. The logical and physical topologies of this lab are shown below:

Logical topology:


Tasks in this lab:

+ Configure static mappings on R1 and R4.
+ Configure point-to-point subinterface on R2 & R3.
+ All routers must be able to ping themselves.

Read more…

EIGRP over Frame Relay and EIGRP Redistribute Lab

April 29th, 2013 networktut 32 comments

In the previous Frame Relay Point-to-Point Subinterface lab we have set up Layer 2 connection via Frame Relay but only adjacent routers can ping each other. For example R1 can ping R2 and R2 and ping R3 but R1 cannot ping R3. This is because R2 connects with R1 and R3 via point-to-point interfaces and they use separate subnets. In this lab we will use EIGRP to advertise these routes so that “remote” routers can ping each other.


IOS used in this lab: c3640-jk9s-mz.124-16.bin

Tasks for this lab:
+ Configure EIGRP so that R1, R2, R3 and R4 can see and ping each other
+ Configure default route on R1 to of R6
+ Advertise that default route to other routers via EIGRP so that every router can go to the Internet

Read more…

VLAN Routing

April 28th, 2013 networktut 61 comments

In this article we will discuss about the configuration on the switches of the TSHOOT Demo ticket. We post the topology here for your reference.

Layer2/3 topology


Read more…