Objective:
The objective of this lab is to reinforce the theoretical troubleshooting concepts described in the TSHOOT guide. You should aim to complete this lab in no more than 10 – 15 minutes. The solutions for the trouble tickets presented in this lab can be found at the end of the questions.
Configurations:
The base configurations for this lab can be found in the Flash memory of the devices illustrated in the topology below. Use the copy flash:<name> run command to load these configurations onto the applicable devices. For example, to load the configuration for lab 1 onto switch DSL2, you would issue the copy flash:tshoot-lab-1-config run command on the switch. The same is applicable to any other switch or device in the topology.
Topology:
The trouble tickets in these labs are based on the following topology, which is based on the CCNP topology on the www.howtonetwork.org website. All device configurations will be based on the topology illustrated below.
IP Addressing:
The following table lists the relevant device IP addresses based on this topology:
| Device Name | Interface | IP Address |
| DLS1 | VLAN 192 | 192.2.2.2/24 |
| VLAN 193 | 192.3.3.2/24 | |
| VLAN 194 | 192.4.4.2/24 | |
| VLAN 195 | 192.5.5.2/24 | |
| DLS2 | VLAN 192 | 192.2.2.3/24 |
| VLAN 193 | 192.3.3.3/24 | |
| VLAN 194 | 192.4.4.3/24 | |
| VLAN 195 | 192.5.5.3/24 | |
| ALS1 | VLAN 192 | 192.2.2.4/24 |
| ALS2 | VLAN 192 | 192.2.2.5/25 |
Trouble Tickets
- Trouble Ticket # 1You have received a problem report about poor voice quality. You contact the WAN team and they advise that they have configured QoS on their routers so that all traffic received from the 192.5.5.0/24 with a DSCP value of EF is assigned strict priority. However, they have not seen any matches on their router. Instead, all they are seeing is traffic coming from the LAN with a default priority of 0 (best effort). Troubleshoot and resolve this issue.
- Trouble Ticket # 2Following some changes on the network yesterday, you have received multiple problem reports about users being unable to ping devices within and between VLANs. Troubleshoot and resolve this issue. Verify by pinging the different SVIs on the Distribution layer switches from the Access layer switches (ALS1 and ALS2).
- Trouble Ticket # 3The Routing team has called you and stated that since the change implemented yesterday, they are unable to establish an EIGRP neighborship between the Distribution layer switches. Troubleshoot and resolve this problem and verify that the EIGRP neighborship is established.