Troubleshooting Lab Challenge 2
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):
To troubleshooting effectively you should understand how this network operates. We summarize it as follows:
+ OSPF process 1 is running between R1, R2, R3, R4 and R5
+ RIP version 2 is running between R2 and R6
+ EIGRP AS 10 is running between R3, R7 and R8
+ Redistribution is configured on R2 & R3 to exchange OSPF, RIP and EIGRP information
+ R5 is connected to an Internet Service Provider (ISP) via BGP 65002. R5 is also providing NAT translation between inside networks (10.0.0.0/24 & 192.168.1.0/24) and outside network (184.108.40.206/30 & 220.127.116.11)
+ R5 is connected to the OSPF backbone area via a OSPF virtual-link. It is a temporary solution for merging them
+ Two access-lists are applied on R5 to increase security for the inside networks
+ Users are allocated prefixes of 192.168.1.0/24 & 10.2.2.0/24. They are represented by Client 1 & Client 2
+ R1, R2 and R3 are connected via DMVPN (this is a new topic in the ROUTEv2 exam. If you don’t understand about DMVPN and NHRP, please ignore ticket 14 & 15.)
+ For security reason, the network between R4 & R5 (10.1.1.20/30) is hidden from all other routers via a filter-list on R4.
+ In the IPv6 Topology R1, R3, R4 and R5 are running OSPFv3 AS#10 while R3 and R8 are running RIPng. Redistribution is performed on R3 so that these two IPv6 routing protocols can see each other.
+ Traceroute commands are not supported in this challenge (that would make the challenge too easy)
There are 15 tickets waiting for you to resolve. Each ticket only contains one error. Below are the links to access them:
|Ticket 1||Ticket 2||Ticket 3||Ticket 4||Ticket 5||Ticket 6||Ticket 7||Ticket 8|
|Ticket 9||Ticket 10||Ticket 11||Ticket 12||Ticket 13||Ticket 14||Ticket 15|
We hope you can solve all these problems. The difficulty of this challenge is same of the TSHOOT exam (for routers only). Please tell us if you like them or not so that we can continue making more in the future.