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 | IPv6 Address |
|---|---|---|
| R11 | FastEthernet0/0 | 10.1.1.1/24 | 3FFE::1/64 |
| Serial0/0 | 172.16.1.1/24 | |
| Serial0/1 | 3FFE:1::1/64 | |
| R2 | FastEthernet0/0 | 10.1.1.2/24 | 3FFE::2/64 |
| Serial0/0 | 172.16.1.2/24 | |
| Serial0/1 | 172.16.3.2/24 | |
| R3 | FastEthernet0/0 | 10.3.3.1/24 |
| Serial1/0 | 3FFE:1::3/64 | |
| 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 stating that the BGP adjacency between R1 and R2 has gone down and is not coming up following some configuration changes the night before. Troubleshoot this issue and resolve it. Verify the adjacency using appropriate commands.
- Trouble Ticket # 1You have received a problem report stating that users in AS 2, i.e. R2, R3, and R4 are unable to reach the R1 or the 10.1.1.0/24 subnet advertised by AS 1. Troubleshoot and resolve this issue. Per strict instructions from management, redistribution of any kind in the network is strictly forbidden. You must resolve this issue without redistributing. Following completion, you must be able to ping from R1 to R4. Verify your configuration using the appropriate commands.
- Trouble Ticket # 3IPv6 has currently been integrated into the network. The LAN between R1 and R2 is running RIPng while the WAN link between R1 and R3 is running OSPFv3. Developers testing IPv6 complain that they are unable to ping any of the IPv6 subnets on R2 from R1. Troubleshoot and resolve this issue. R3 should have three IPv6 routes when you are complete. Verify this using the appropriate commands.
- Trouble Ticket # 4Traffic between the 10.3.3.0/24 and 10.4.4.0/24 is encrypted. However, following a scheduled change on these routers, the network security team has opened up a problem report stating that this traffic is no longer encrypted. This encryption occurs only on the R3-R4 Serial1/3-Serial0/1 link using static routes. If this link is down, BGP is used for connectivity and the traffic is not encrypted. Troubleshoot and resolve this issue. Verify using the appropriate commands
- Trouble Ticket # 5The voice team is preparing to integrate IPT between the 10.3.3.0/24 and 10.2.2.0/24. They have decided to do some pre-implementation testing using Cisco IOS IP SLAs. Following the configuration of Cisco IOS IP SLAs, they discover that they are unable to see any results on R3. Troubleshoot this issue and verify your solution using the appropriate commands