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.
Lab Solutions
Solution # 1
The VLAN Access Control List (VACL) on switch DLS2 is mis-configured as follows:
| vlan access-map FORWARD-ALL 10 action drop |
The result of this configuration is all packets and frames within this VLAN will be dropped by the switch. To resolve this issue, the switch VACL needs to be re-configured as follows:
| DLS2(config)#vlan access-map FORWARD-ALL 10 DLS2(config-access-map)#action forward |
Solution # 2
Switch DLS1 has been configured with a duplicate EIGRP router ID (the same as R2):
| DLS1#show run | begin router eigrp router eigrp 254 no auto-summary eigrp router-id 1.0.0.2 network 0.0.0.0 |
By default, a router running EIGRP will NOT accept external routes from another router that has the same router ID. This is designed to prevent loops. In order to resolve this issue, the EIGRP router ID needs to be configured as follows:
| DLS1(config)#router eigrp 254 DLS1(config-router)#eigrp router-id 1.0.0.3 DLS1(config-router)#end |
NOTE: You can use any other value or completely remove the RID to complete this task.
Solution # 3
R2 has been configured to redistribute an EIGRP process that does not exist:
| R2#show running-config | section bgp no synchronization bgp router-id 2.2.2.2 bgp log-neighbor-changes redistribute eigrp 252 neighbor 10.0.0.10 remote-as 253 no auto-summary |
To resolve this issue, you need to configure BGP to redistribute EIGRP AS 254 instead:
| R2(config)#router bgp 252 R2(config-router)#redistribute eigrp 254 |
Solution # 4
The issue is that switches ALS1 and ALS2 have no default gateway, which prevents them from forwarding packets beyond their local subnet. Configure a default gateway as follows:
| ALS1(config)#ip default-gateway 172.16.1.1 |
| ALS2(config)#ip default-gateway 172.16.1.1 |
Final Working Router Configurations
R1
|
R1#term len 0 Current configuration : 901 bytes R1# |
R2
|
R2#term len 0 Current configuration : 1136 bytes R2# |
R3
|
R3#term len 0 Current configuration : 1482 bytes R3# |
R4
|
R4#term len 0 Current configuration : 931 bytes R4# |
Final Working Switch Configurations
DLS1
|
DLS1# Current configuration : 5345 bytes DLS1# |
DLS2
|
DLS2#term len 0 Current configuration : 4711 bytes DLS2# |
ALS1
|
ALS1#term len 0 Current configuration : 1611 bytes ALS1# |
ALS2
|
ALS2#term len 0 Current configuration : 1514 bytes ALS2# |
