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.net 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 |
|---|---|---|
| R11 | FastEthernet0/0 | 10.1.1.1/24 |
| Serial0/0 | This interface is not used | |
| Serial0/0 | This interface is not used | |
| R2 | FastEthernet0/0 | 10.1.1.2/24 |
| Serial0/0 | This interface is not used | |
| Serial0/1 | 172.16.3.2/24 | |
| R3 | FastEthernet0/0 | 10.3.3.1/24 |
| Serial1/0 | This interface is not used | |
| Serial1/1 | 172.16.3.3/24 | |
| Serial1/2 | 172.16.4.3/24 | |
| Serial1/3 | 172.16.5.3/24 | |
| R4 | FastEthernet0/0 | 10.4.4.1/24 |
| Serial0/0 | 172.16.4.4/24 | |
| Serial0/1 | 172.16.5.4/24 |
Base Configurations
The following base configuration must be implemented on switch ALS1. This switch is not used in any of the troubleshooting scenarios; however, it is required to provide LAN connectivity between internetwork devices. Simply copy & paste the following base configuration on ALS1:
| ALS1#wr te Building configuration… Current configuration : 1150 bytes ALS1# |
Trouble Tickets
- Trouble Ticket # 1You have received a problem report advising of a network-wide outage. This was experienced shortly following a configuration change on R2. Troubleshoot and resolve this issue.
- Trouble Ticket # 2You receive a problem report that a previously working MP-BGP solution is no longer working. The IPv6 subnets located on R1 are no longer reachable from R4. Troubleshoot this issue and verify connectivity to these IPv6 subnets from R4; i.e. verify that R4 can ping the IPv6 addresses.
- Trouble Ticket # 3Following a scheduled maintenance on R3, users complain that they can no longer reach the 180.3.x.x subnets. Prior to the change, R3 was advertising a single external summary route for these subnets as requested by management. Troubleshoot and resolve this issue using the appropriate commands.
- Trouble Ticket # 4Cisco IOS DHCP server has been configured on R4 in preparation for a Cisco IP Telephony implementation. The IPT engineers are testing DHCP server functionality and open up a problem report stating that it doesn’t work. No other information has been provided by the engineers. Troubleshoot and resolve this issue.