CCNP TSHOOT


Welcome again !

This post is for all of you out there preparing for CCNP TSHOOT exam which I must say is not easy to pass  so unless you have been paying attention , reading and labbing like crazy for some time you will most likely fail your first or even second attempt.

If you however manage to pass this one and resolve all tickets then wait no more , log on to your Pearson Vue account and book your CCNP Tshoot exam !

Cisco does provide a test TSHOOT simulation lab for us which can be accessed via this URL

These are two screenshot from the test TSHOOT lab :

CCNP_TSHOOT_ipv4_demo

CCNP_TSHOOT_layer2_demo

I would highly recommend looking into this before booking your exam because you really have to know and understand a lot and you have to be fast. Below topology is what I’ve created in GNS3 and believe it or not if you manage to pass all provided tickets like I said before then you are most definitely ready for the real one !

TSHOOT_GNS3

Every device you see in this set up is Cisco c3700 series router running c3745-adventerprisek9-mz.124-12.bin IOS image and all I did was that I simply changed  “the symbol” in GNS3 (you can do it by right clicking on a device once it’s on screen) so basically the idea is that you do not have to have real servers , laptops etc … but if you do you can actually build something like this , have those running as your VMs or real devices for that matter and have even more fun  🙂

CCNP_TSHOOT_cluid

However let’s concentrate on the first set up and just like with other posts , firstly please go ahead and use this GNS3 net file tshoot_net to build it then copy and paste all below configs into every device

Tshoot Configs : configs_tshoot

Above configs are broken with missing parts etc … this also includes the frame switch ! basically any of these device can have something misconfigured what needs fixing !

TICKETS
1 – R1 and R2 are not able to ping each other
2 – Restore management access via telnet between R1 and R2
3 – Restore OSPF adjacencies between R3 and R4
4 – The problem state that DSW1 and DSW2 are configured as HSRP routes and DSW1 should be active router but instead, currently DSW2 is active.
5 – Resolve the issues preventing management of R3 via HTTPS. Access credentials should be cisco/cisco and should be stored locally in R3
6 – The problem state that R4 and DSW1 can’t ping to R2’s loopback IPV6 address (FEC0::2:2) or (Serial1/0.12’s 2026::12:2).
7 – Client 1 is not receiving an IP address from DHCP server (R4)
8 – Client 1 can not reach R1 S0/0.12 interface
9 – Client 2 is not able to reach Web_Server at 209.65.200.241
10 – DSW2 is not able to NTP authenticate against DSW1 who is NTP master

Please note that to fix some of the issues will require a very good knowledge and understanding certain technologies also in order to get something to work in some of these tickets the fault is located in a few different places where you will need to apply , change or remove the script so let’s say if there is an issue with OSPF adjacencies between two routers and you’ve noticed that the OSPF network does not match under the interface , it does not mean that when you correct it then the adjacencies will be established , you might need to look deeper !

I will add more tickets very soon !

Enjoy !

Tom

Advertisements