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 users on the 150.2.2.0/24 subnet are unable to reach users on the 172.16.1.0/24 subnet and vice-versa. Troubleshoot and resolve this issue. Verify your solution by pinging between these two subnets.
Trouble Ticket # 2
You have received a problem report indicating that users on the 150.3.3.0/24 subnet are also unable to reach users on the 172.16.1.0/24 subnet and vice-versa. Troubleshoot and resolve this issue. Verify your solution by pinging between these two subnets.
Trouble Ticket # 3
You have received a problem report indicating that users no users on the network can reach the 150.4.4.0/24 subnet. Troubleshoot and resolve this issue. Test your solution by pinging this subnet from any one of the other LAN subnets.
Trouble Ticket # 4
You have received a problem report indicating users connected to the 150.4.4.0/24 subnet are unable to receive IP addressing information via DHCP. Troubleshoot and resolve this issue.
Lab Solutions
Solution # 1
The static route on R1 has been mis-configured. It is pointing to 150.1.1.22 instead of 150.1.1.2:
| R1#show ip route 172.16.1.0 255.255.255.0 Routing entry for 172.16.1.0/24 Known via “static”, distance 1, metric 0 Advertised by bgp 100 Routing Descriptor Blocks: * 150.1.1.22, via FastEthernet0/0 Route metric is 0, traffic share count is 1 |
The result of this configuration is that the subnet will be inaccessible from all other devices. To resolve this issue, remove this static route and configure a correct next hop address:
| R1(config)#no ip route 172.16.1.0 255.255.255.0 FastEthernet0/0 150.1.1.22 R1(config)#ip route 172.16.1.0 255.255.255.0 FastEthernet0/0 150.1.1.2 |
Solution # 2
By default, the NEXT_HOP attribute is not modified when routes are sent from a BGP speaker to an internal peer. This can be resolved in one of two ways:
- Redistribute the 10.0.0.0/30 subnet into OSPF on R2
- Change the NEXT_HOP attribute for BGP on R2
The following shows the latter solution. Either option is acceptable when completing this task.
| R2(config)#router bgp 252 R2(config-router)#neighbor 10.0.0.10 next-hop-self R2(config-router)#exit |
Solution # 3
The issue is that R4 has been configured as a receive-only EIGRP stub router. This prevents the router from advertising the 150.4.4.0/24 subnet via EIGRP to R3:
| R4#show running-config | section eigrp router eigrp 254 network 0.0.0.0 no auto-summary eigrp stub receive-only |
To resolve this issue, configure R4 as an EIGRP stub. By default, this will cause the router to advertise connected subnets:
| R4(config)#router eigrp 254 R4(config-router)#no eigrp stub receive-only R4(config-router)#eigrp stub |
Solution # 4
There are two issues here. First, the DHCP service is disabled on R2 , the Cisco IOS DHCP Server. The second issue is that the Cisco IOS DHCP Relay Agent is not configured on R4. Resolve this issue by enabling Cisco IOS DHCP Server functionality on R2 and then also configuring the Cisco IOS DHCP Relay Agent on R4s LAN interface:
| R2(config)#service dhcp |
| R4(config)#interface fastethernet 0/0 R4(config-if)#ip helper-address 10.0.0.9 R4(config-if)#exit |
Final Working Router Configurations
R1
|
R1#term len 0 Current configuration : 1085 bytes R1# |
R2
|
R2#term len 0 Current configuration : 1391 bytes R2# |
R3
|
R3#term len 0 Current configuration : 1592 bytes R3# |
R4
|
R4#term len 0 Current configuration : 868 bytes R4# |
Final Working Switch Configurations
DLS1
|
DLS1#term len 0 Current configuration : 6958 bytes DLS1# |
DLS2
|
DLS2#term len 0 Current configuration : 6326 bytes DLS2# |
ALS1
|
ALS1#term len 0 Current configuration : 1619 bytes ALS1# |
ALS2
|
ALS2#term len 0 Current configuration : 1522 bytes ALS2# |
