Lab Objective:
The focus of this lab is to hone your trouble isolation and resolution skills. This lab will include Layer 2 and Layer 3 technologies which fall within the scope of the current CCNP curriculum.
Lab Topology:
The lab network topology is illustrated below:
|
IMPORTANT NOTE If you are using the www.howtonetwork.net racks, please download and paste the troubleshooting lab configurations. If you are using your own rack or lab, please modify this configuration to reflect the actual interface types, etc, that you have on your devices. Prior to beginning all labs, apply the pre-lab configuration for each individual device. When completing these labs, it is important to resolve the trouble tickets in the order in which they are listed because they build on each other. For example, if you begin with Trouble Ticket # 3, you might not get the expected resolution or result if you have not completed Trouble Ticket # 1 and Trouble Ticket # 2. It is very important to follow the order listed. |
Trouble Ticket # 1
You have received a problem report indicating that no one is able to reach switch DLS2. Troubleshoot and resolve this issue.
Trouble Ticket # 2
The NOC calls you to advise that they are unable to reach the 172.16.1.0/24 subnet from the 150.2.2.0/24 subnet. Troubleshoot and resolve this issue. However, ensure that your solution does NOT include advertising the 150.1.1.0/24 subnet via BGP or using static routes.
Trouble Ticket # 3
There is a secure tunnel between R1 and R4 that protects traffic between the 150.1.1.0/24 and 150.4.4.0/24 subnets. For some reason, this tunnel is not working and you are unable to ping between these subnets. Troubleshoot and resolve this issue.
Trouble Ticket # 4
A Multicast video solution is being tested between the 150.2.2.0/24 and the 150.3.3.0/24 subnets. However, the users are reporting that this is not working. Troubleshoot and resolve this issue. For proprietary reasons, the company does not allow RPs within the network.