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 HSRP is not working between switches DLS1 and DLS1. Troubleshoot and resolve this issue.
Trouble Ticket # 2
The NOC has called you advising that they are unable to ping switch ALS1 from any of the devices. Troubleshoot and resolve this issue.
Trouble Ticket # 3
Users connected to the 150.100.1.0/24 subnet has complained that they are unable to reach devices on the 150.200.1.0/24 subnet and vice-versa. Troubleshoot and resolve this issue.
Trouble Ticket # 4
You have received an urgent call from the NOC stating that following some configuration changes on switches DLS1 and DLS2, their monitoring servers are no longer receiving any Spanning-Tree Protocol notifications from the devices. Troubleshoot and resolve this issue.
Lab Solutions
Solution # 1
The issue is that both switch DLS1 and DLS2 have been configured with the same IP addresses for the SVIs for VLANs 100 and 200:
| DLS1#show running-config interface vlan 100 Building configuration… Current configuration : 138 bytes DLS1#show running-config interface vlan 200 Current configuration : 112 bytes |
| DLS2#show running-config interface vlan 100 Building configuration… Current configuration : 112 bytes DLS2#show running-config interface vlan 200 Current configuration : 138 bytes |
To resolve this issue, change the configuration on switch DLS2s SVIs to a different IP address:
| DLS2(config)#interface vlan 100 DLS2(config-if)#ip address 150.100.1.3 255.255.255.0 DLS2(config-if)#exit DLS2(config)#interface vlan 200 DLS2(config-if)#ip address 150.200.1.3 255.255.255.0 DLS2(config-if)#exit |
Solution # 2
The issue is that the EtherChannels between switch ALS1 and switches DLS1 and DLS2 are set to passive mode. This will prevent the LACP channel from forming.
| DLS1#show etherchannel 1 port | include Mode Channel group = 1 Mode = Passive Gcchange = – Channel group = 1 Mode = Passive Gcchange = – |
| DLS2#show etherchannel 2 port | include Mode Channel group = 2 Mode = Passive Gcchange = – Channel group = 2 Mode = Passive Gcchange = – |
| ALS1#show etherchannel 1 port | include Mode Channel group = 1 Mode = Passive Gcchange = – Channel group = 1 Mode = Passive Gcchange = – |
| ALS1#show etherchannel 2 port | include Mode Channel group = 2 Mode = Passive Gcchange = – Channel group = 2 Mode = Passive Gcchange = – |
To resolve this issue, configure at least one end of the EtherChannel in active mode:
| DLS1(config)#interface range fastethernet 0/7 – 8 DLS1(config-if-range)#channel-group 1 mode active |
| DLS2(config)#interface range fastethernet 0/9 – 10 DLS2(config-if-range)#channel-group 2 mode active |
Solution # 3
The issue is that both IP routing is disabled on both DLS1 and DLS2:
| DLS1#show ip route Default gateway is not set Host Gateway Last Use Total Uses Interface |
| DLS2#show ip route Default gateway is not set Host Gateway Last Use Total Uses Interface |
To resolve this issue, enable IP routing on both of the switches:
| DLS1(config)#ip routing |
| DLS2(config)#ip routing |
Solution # 4
The issue is that both Spanning Tree logging has been disabled (default) on both switches. To resolve this issue, enable logging globally and on all trunk links:
| DLS1(config)#interface port-channel 1 DLS1(config-if)#logging event spanning-tree DLS1(config-if)#exit DLS1(config)#interface port-channel 2 DLS1(config-if)#logging event spanning-tree DLS1(config-if)#exit DLS1(config)#interface port-channel 5 DLS1(config-if)#logging event spanning-tree DLS1(config-if)#exit DLS1(config)#spanning-tree logging |
| DLS2(config)#interface port-channel 1 DLS2(config-if)#logging event spanning-tree DLS2(config-if)#exit DLS2(config)#interface port-channel 2 DLS2(config-if)#logging event spanning-tree DLS2(config-if)#exit DLS2(config)#interface port-channel 5 DLS2(config-if)#logging event spanning-tree DLS2(config-if)#exit DLS2(config)#spanning-tree logging |
Final Working Switch Configurations
DLS1
|
DLS1#term len 0 Current configuration : 4839 bytes DLS1# |
DLS2
|
DLS2#term len 0 Current configuration : 4829 bytes DLS2# |
ALS1
|
ALS1#term len 0 Current configuration : 1304 bytes ALS1# |
ALS2
|
ALS2#term len 0 Current configuration : 1224 bytes ALS2# |