Ccnp tshoot

Hey, guys I'll be sitting down for my TSHOOT hopefully this weekend and giving it a go. I've read the Official Cert Guide just as a refresher and watching CBT Nuggets. other than that do you guys have any recommendations i can do to build up some more confidence or tips on materials i can use to better understand the material.

Find more posts tagged with

Comments

cisco_trooper

Hopefully you've gotten in some good lab time....

shodown

Lab time is a must and have a strategy. If you don't have a lab the Boson net sim for TSHOOT is great. Because you can work it over and over and over. You should approach every ticket the same way. Start with pinging as far as you can go, then working your way up the layers with the technology thats implemented. Practice this over and over and you will pass with no problem.

creamy_stew

gregorio323 wrote: »

Hey, guys I'll be sitting down for my TSHOOT hopefully this weekend and giving it a go. I've read the Official Cert Guide just as a refresher and watching CBT Nuggets. other than that do you guys have any recommendations i can do to build up some more confidence or tips on materials i can use to better understand the material.

cisco publish the topology for the TSHOOT on their site somewhere. (NOT cheating)

Make sure to study that topology. If you still have time and equipment/lab-time, use it!

gregorio323

Hey, thanks for all the replies and advice. I'll most likely push it back to the following weekend. Reason being I'm receiving my second 3550 this week and plan to set up the exact topology at home. Just get familiar with the settings after all I'll learn much more setting it all up over and over. and learning from simple mistakes that i make while building it.

billyr

It's one of the only Cisco tests where you can go back to a question if you are not sure.

Use this to your advantage to compare the config of the suspect device with the config of a known working device on another ticket.

nel

creamy_stew wrote: »

cisco publish the topology for the TSHOOT on their site somewhere. (NOT cheating)

Make sure to study that topology. If you still have time and equipment/lab-time, use it!

I never knew this :S haha. Although i havent even looked at the TSHOOT yet. Thanks for the info. Heres the link to the topology for any other clueless mo fo like myself

https://learningnetwork.cisco.com/servlet/JiveServlet/download/52366-8599/TSHOOT%20Exam%20Topology.pdf

pham0329

billyr wrote: »

It's one of the only Cisco tests where you can go back to a question if you are not sure.

Use this to your advantage to compare the config of the suspect device with the config of a known working device on another ticket.

really? You can do that? Doesn't that make it kind of easy if you can compare the config of when it's working to when it's not?

martell1000

pham0329 wrote: »

really? You can do that? Doesn't that make it kind of easy if you can compare the config of when it's working to when it's not?

if you understand that network setup from bottom to top its a piece of cake ...

but i guess thats the point of the exam ...

gregorio323

Yeah, i understand the topology it's easy setup. I can already picture the questions they will ask.

Has anyone done the CCNP THSHOOT labs on cisco.com the one you pay for is it any good?

nicklauscombs

pham0329 wrote: »

really? You can do that? Doesn't that make it kind of easy if you can compare the config of when it's working to when it's not?

in the real world you would have a copy of the previous working config to roll back to after changes were made. so while it feels a lot like cheating doing it during the test it's not far from "real world".

billyr

nicklauscombs wrote: »

in the real world you would have a copy of the previous working config to roll back to after changes were made. so while it feels a lot like cheating doing it during the test it's not far from "real world".

Yep, this. I read on an official Cisco release that they had designed it this way for exactly that reason. You still need to know your stuff though, because as well as identifying the fault, you'll also need to know how to fix it.