CCNPv7 - TSHOOT - Lab4 2 - Mixed Layer 2 3 Connectivity - Student
CCNPv7 - TSHOOT - Lab4 2 - Mixed Layer 2 3 Connectivity - Student
CCNPv7 - TSHOOT - Lab4 2 - Mixed Layer 2 3 Connectivity - Student
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 1 of 13
CCNPv7 TSHOOT Lab 4-2, Mixed Layer 2-3 Connectivity
Logical Topology
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 2 of 13
CCNPv7 TSHOOT Lab 4-2, Mixed Layer 2-3 Connectivity
Objectives
Load the trouble ticket device configuration files for each trouble ticket.
Diagnose and resolve problems related to switch virtual interfaces and multilayer switching.
Diagnose and resolve problems related to First Hop Redundancy Protocols.
Document troubleshooting progress, configuration changes, and problem resolution.
Background
Multilayer switches have the capability to act as routers by way of switch virtual interfaces (SVIs), routed
interfaces, and routing protocols. SVIs are Layer 3 logical interfaces representing VLANs and routed ports are
Layer 3 physical interfaces. Multilayer switches are frequently used as part of the LAN switch fabric and can
be configured with a First Hop Redundancy Protocol (FHRP). Two or more Layer 3 switches (or routers) can
provide redundant paths to the network edge for local hosts. A host is configured with a virtual default
gateway address. If one of the gateways goes down, the other can take over for the client without the client’s
knowledge. FHRPs used in CCNPv7.0 are Hot Standby Router Protocol (HSRP), Virtual Router Redundancy
Protocol (VRRP), and Gateway Load Balancing Protocol (GLBP).
In this lab, you will troubleshoot problems related to Layer 3 switching and FHRPs. For each task or trouble
ticket, the scenario and problem symptoms are described. While troubleshooting, you will discover the cause
of the problem, correct it, and then document the process and results.
Physical and Logical Topology Diagrams
The physical and logical topologies, including interface designations and IPv4/IPv6 addresses, are provided
to assist the troubleshooting effort.
Note: This lab uses Cisco ISR G2 routers running Cisco IOS 15.4(3) images with IP Base and Security
packages enabled, and Cisco Catalyst 3560 and 2960 switches running Cisco IOS 15.0(2) IP Services and
LAN Base images, respectively. The 3560 and 2960 switches are configured with the SDM templates dual-
ipv4-and-ipv6 routing and lanbase-routing, respectively. Depending on the router or switch model and
Cisco IOS Software version, the commands available and output produced might vary from what is shown in
this lab. Any changes made to the baseline configurations or topology (other than errors introduced) are noted
in the trouble ticket so that you are aware of them prior to beginning the troubleshooting process.
Required Resources
3 routers (Cisco IOS Release 15.4 or comparable)
2 multilayer switches and 1 access layer switch (Cisco IOS Release 15.0(2) or comparable with Fast
Ethernet interfaces)
SRV1 (PC with static IP address): Windows 7 with RADIUS, TFTP, and syslog servers, plus an SSH
client and WireShark software
PC-B (DHCP client): Windows 7 with SSH client and WireShark software
PC-C (DHCP client): Windows 7 with SSH client and WireShark software
Serial and Ethernet cables, as shown in the topology
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 3 of 13
CCNPv7 TSHOOT Lab 4-2, Mixed Layer 2-3 Connectivity
Step 2: Load the device trouble ticket configuration files for TT-A.
Using the procedure described in the BASE Lab, verify that the lab configuration files are present in flash. Load
the proper configuration files indicated in the Device Configuration File Table.
Note: You can test the simulated Internet access by opening a browser and entering the IP address of the R2 Lo1
interface 2.2.2.2. You will be prompted for a username and password. You can gain access to the router GUI
management interface by entering username cisco and the enable password cisco.
Device Configuration File Table
Device Name File to Load Notes
ALS1 Lab42-ALS1-TT-A-Cfg.txt
DLS1 Lab42-DLS1-TT-A-Cfg.txt
DLS2 Lab42-DLS2-TT-A-Cfg.txt
R1 Lab42-R1-TT-A-Cfg.txt
R2 Lab42-R2-TT-A-Cfg.txt
R3 Lab42-R3-TT-A-Cfg.txt
SRV1 N/A Static IP: 10.1.100.1 and 2001:DB8:CAFE:100::1
Default gateway: 10.1.100.254/24 and 2001:DB8:CAFE:100::D1/64
PC-B N/A DHCP (release and renew for IPv4 and IPv6 after loading device
configurations)
PC-C N/A DHCP (release and renew for IPv4 and IPv6 after loading device
configurations)
Step 3: Configure SRV1 and start the syslog and TFTP servers.
a. Ensure that SRV1 has the static IP address 10.1.100.1 and default gateway 10.1.100.254.
b. Start the syslog server on SRV1, which is the syslog server for the entire network. When the network
is properly configured, all devices send syslog messages to SRV1.
c. Start the TFTP server on SRV1, which is the archive server for the entire network. When the network
is properly configured, all devices send archives of their running configurations to this server
whenever the running config is copied to the startup config. Ensure that the default TFTP directory on
SRV1 is set to the directory where you want to store the archives.
Step 4: Release and renew the DHCP leases on PC-B and PC-C.
a. Ensure that PC-B and PC-C are configured as DHCP clients.
b. After loading all TT-A device configuration files, issue the ipconfig/release and
ipconfig/renew commands on PC-B and PC-C. You might need to repeat this process after the
TT problems have been resolved.
Note: Problems introduced into the network by the trouble ticket might prevent one or both of the PCs
from acquiring an IP address. Do not assign either PC a static address.
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 4 of 13
CCNPv7 TSHOOT Lab 4-2, Mixed Layer 2-3 Connectivity
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 5 of 13
CCNPv7 TSHOOT Lab 4-2, Mixed Layer 2-3 Connectivity
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 6 of 13
CCNPv7 TSHOOT Lab 4-2, Mixed Layer 2-3 Connectivity
Step 2: Load the device trouble ticket configuration files for TT-B.
Load the proper configuration files indicated in the Device Configuration File Table.
Note: The following device access methods are in effect after loading the configuration files:
Console access requires no username or password.
SSH requires the username admin and password cisco.
The enable password is cisco.
Device Configuration File Table
Device Name File to Load Notes
ALS1 Lab42-ALS1-TT-B-Cfg.txt
DLS1 Lab42-DLS1-TT-B-Cfg.txt contains errors
DLS2 Lab42-DLS2-TT-B-Cfg.txt contains errors
R1 Lab42-R1-TT-B-Cfg.txt
R2 Lab42-R2-TT-B-Cfg.txt
R3 Lab42-R3-TT-B-Cfg.txt
SRV1 N/A Static IP: 10.1.100.1 and 2001:DB8:CAFE:100::1
Default gateway: 10.1.100.254/24 and 2001:DB8:CAFE:100::D1/64
PC-B N/A DHCP (release and renew for IPv4 and IPv6 after loading device
configurations)
PC-C N/A DHCP (release and renew for IPv4 and IPv6 after loading device
configurations)
Step 3: Configure SRV1 and start the syslog and TFTP servers, as described in Task 1.
Step 4: Release and renew the DHCP leases on PC-B and PC-C, as described in Task 1.
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 7 of 13
CCNPv7 TSHOOT Lab 4-2, Mixed Layer 2-3 Connectivity
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 8 of 13
CCNPv7 TSHOOT Lab 4-2, Mixed Layer 2-3 Connectivity
When DLS1 was up, the traceroute from PC-B to the R2 simulated ISP Lo0 10.1.202.1 succeeded and
followed the path DLS1 (10.1.10.252) to R1 (10.1.2.2) to R2 (10.1.202.1). A trace to a location reports
the real IP address of the hops on the path, not the virtual ones. Thus, the trace would have looked
normal even though there might be problems with HSRP. However, when DLS1 goes down, the real IP
address that PC-B was using as its default gateway is no longer available, and the traceroute fails at
the first hop (DLS1). The second problem is caused by mismatched HSRP parameters between Layer
3 switches DLS1 and DLS2 for VLAN 100 MGMT.
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 9 of 13
CCNPv7 TSHOOT Lab 4-2, Mixed Layer 2-3 Connectivity
Step 2: Load the device trouble ticket configuration files for TT-C.
Load the proper configuration files indicated in the Device Configuration File Table.
Device Configuration File Table
Device Name File to Load Notes
ALS1 Lab42-ALS1-TT-C-Cfg.txt
DLS1 Lab42-DLS1-TT-C-Cfg.txt contains errors
DLS2 Lab42-DLS2-TT-C-Cfg.txt contains errors
R1 Lab42-R1-TT-C-Cfg.txt
R2 Lab42-R2-TT-C-Cfg.txt
R3 Lab42-R3-TT-C-Cfg.txt
SRV1 N/A Static IP: 10.1.100.1 and 2001:DB8:CAFE:100::1
Default gateway: 10.1.100.254/24 and 2001:DB8:CAFE:100::D1/64
PC-B N/A DHCP (release and renew for IPv4 and IPv6 after loading device
configurations)
PC-C N/A DHCP (release and renew for IPv4 and IPv6 after loading device
configurations)
Step 3: Configure SRV1 and start the syslog and TFTP servers, as described in Task 1.
Step 4: Release and renew the DHCP leases on PC-B and PC-C, as described in Task 1.
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 10 of 13
CCNPv7 TSHOOT Lab 4-2, Mixed Layer 2-3 Connectivity
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 11 of 13
CCNPv7 TSHOOT Lab 4-2, Mixed Layer 2-3 Connectivity
Step 2: Load the device trouble ticket configuration files for TT-D.
Load the proper configuration files indicated in the Device Configuration File Table.
Device Configuration File Table
Device Name File to Load Notes
ALS1 Lab42-ALS1-TT-D-Cfg.txt
DLS1 Lab42-DLS1-TT-D-Cfg.txt
DLS2 Lab42-DLS2-TT-D-Cfg.txt
R1 Lab42-R1-TT-D-Cfg.txt
R2 Lab42-R2-TT-D-Cfg.txt
R3 Lab42-R3-TT-D-Cfg.txt
SRV1 N/A Static IP: 10.1.100.1 and 2001:DB8:CAFE:100::1
Default gateway: 10.1.100.254/24 and 2001:DB8:CAFE:100::D1/64
PC-B N/A DHCP (release and renew for IPv4 and IPv6 after loading device
configurations)
PC-C N/A DHCP (release and renew for IPv4 and IPv6 after loading device
configurations)
Step 3: Configure SRV1 and start the syslog and TFTP servers, as described in Task 1.
Step 4: Release and renew the DHCP leases on PC-B and PC-C, as described in Task 1.
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 12 of 13
CCNPv7 TSHOOT Lab 4-2, Mixed Layer 2-3 Connectivity
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 13 of 13