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 switch DLS2 is unable to reach any other device within VLAN 100. Troubleshoot and resolve this issue. Verify your solution using a simple ping from switch DLS2 to any other device within this VLAN.
Trouble Ticket # 2
You have received a problem report indicating that switch DLS2 is not receiving any routing information for external networks. Troubleshoot and resolve this issue. You can NOT modify the configurations on any routers when resolving this issue. Following resolution, verify that DLS2 has external EIGRP routes in its routing table.
Trouble Ticket # 3
You have received a problem report indicating that users on the 150.4.4.0/24 subnet are unable to reach the 150.1.1.0/24 and 172.16.1.0/24 subnets. Troubleshoot and resolve this issue. Verify your solution using a ping from the 150.4.4.0/24 subnets to the 150.1.1.0/24 and 172.16.1.0/24 subnets. You are only allowed to change the configuration on ONE device when implementing a resolution for this issue. Verify by pinging between the subnets.
Trouble Ticket # 4
You have received a problem report indicating that the corporate NOC is unable to ping half of the devices that reside on the 172.16.1.0/24 subnet from the 150.4.4.0/24 subnet. Troubleshoot and resolve this issue. Validate your resolution by pinging all of the devices that reside on the subnet from the 150.4.4.0/24 subnet.