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 | DHCP |
| Serial0/0 | This interface is not used | |
| Serial0/0 | This interface is not used | |
| R2 | FastEthernet0/0 | 10.2.2.1/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 ! version 12.1 no service pad service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname ALS1 ! no logging console ! ip subnet-zero ! vtp domain TSHOOT vtp mode transparent ! spanning-tree mode pvst no spanning-tree optimize bpdu transmission spanning-tree extend system-id ! ! ! ! vlan 100 name TSHOOT-100 ! vlan 200 name TSHOOT-200 ! interface FastEthernet0/1 switchport access vlan 100 switchport mode access ! interface FastEthernet0/2 switchport access vlan 100 switchport mode access ! interface FastEthernet0/3 switchport access vlan 200 switchport mode access ! interface FastEthernet0/4 switchport access vlan 200 switchport mode access ! interface FastEthernet0/5 shutdown ! interface FastEthernet0/6 shutdown ! interface FastEthernet0/7 shutdown ! interface FastEthernet0/8 shutdown ! interface FastEthernet0/9 shutdown ! interface FastEthernet0/10 shutdown ! interface FastEthernet0/11 shutdown ! interface FastEthernet0/12 shutdown ! interface Vlan1 no ip address no ip route-cache shutdown ! ip http server ! line con 0 line vty 0 4 login line vty 5 15 login ! ! end ALS1# |
Trouble Tickets
- Trouble Ticket # 1You have received a problem report from a field technician installing R1. You have been told that the router is unable to acquire an IP address via DHCP. R2 is configured as a Cisco IOS DHCP Relay Agent while R3 is configured as a Cisco IOS DHCP server. Troubleshoot and resolve this issue.
- Trouble Ticket # 2After resolving the DHCP issue, you receive a call from users connected to R2s LAN stating that they are experiencing connectivity issues to the 200.1.1.1 address, which is configured on R4. Troubleshoot and resolve this issue. Management has forbidden any changes whatsoever from being made on R4. Your solution should not entail any changes on this router at all.
- Trouble Ticket # 3You have received a problem report from some network auditors stating that they cannot reach the 192.168.113.1 and 192.168.114.1 host addresses. These are being used to test reachability for a future application and should be advertised by R4. Troubleshoot and resolve this issue. Verify that these routes appear as external EIGRP routes in the routing tables of all routers.
- Trouble Ticket # 4You have received a problem report from some IPTV engineers who are testing an IP Multicast application that resides on the R4s LAN. They reside on R3s LAN but are unable to ping test Multicast group 224.4.4.4, which has been configured on R4s LAN. Troubleshoot this issue and then verify that R3 can ping Multicast group address 224.4.4.4.