Chapter 9 Lab 9-1, Network Mirror: Ccnpv7 Tshoot
Chapter 9 Lab 9-1, Network Mirror: Ccnpv7 Tshoot
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 1 of 8
CCNPv7 TSHOOT
Logical Topology
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 2 of 8
CCNPv7 TSHOOT
Objectives
Load the trouble ticket device configuration files for each trouble ticket.
Diagnose and resolve problems related to switch virtual interfaces and multilayer switching.
Background
Network documentation and security documentation are important when troubleshooting, especially when
unexpected traffic patterns emerge. In this lab, you will troubleshoot problems related to network design and
security policy. 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 baseline physical and logical topologies, including interface designations and IPv4/IPv6 addresses, are
provided to assist the troubleshooting effort. Since this lab involves network design, it may help to create new
network diagrams or modify the ones provided.
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 dualipv4-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
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
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 3 of 8
CCNPv7 TSHOOT
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.
Device Configuration File Table
Device Name
File to Load
ALS1
Lab91-ALS1-TT-A-Cfg.txt
DLS1
Lab91-DLS1-TT-A-Cfg.txt
Notes
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 4 of 8
CCNPv7 TSHOOT
Device Name
File to Load
Notes
DLS2
Lab91-DLS2-TT-A-Cfg.txt
R1
Lab91-R1-TT-A-Cfg.txt
R2
Lab91-R2-TT-A-Cfg.txt
R3
Lab91-R3-TT-A-Cfg.txt
SRV1
N/A
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 cause DHCP issues. Do not
assign PC-B or PC-C a static address.
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
Step 6: Record the troubleshooting process and configuration changes.
Use this log to document your actions and results during the troubleshooting process. List the commands you
used to gather information. As you progress, record your thoughts as to what you think the problem might be and
which actions you take to correct the problem.
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 5 of 8
CCNPv7 TSHOOT
Device
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 6 of 8
CCNPv7 TSHOOT
As the companys lead network engineer and coauthor of the security policy, you immediately get started
troubleshooting.
Step 2: Load the device trouble ticket configuration files for TT-B.
Load the proper configuration files indicated in the Device Configuration File Table.
Device Configuration File Table
Device Name
File to Load
Notes
ALS1
Lab91-ALS1-TT-B-Cfg.txt
DLS1
Lab91-DLS1-TT-B-Cfg.txt
DLS2
Lab91-DLS2-TT-B-Cfg.txt
R1
Lab91-R1-TT-B-Cfg.txt
R2
Lab91-R2-TT-B-Cfg.txt
R3
Lab91-R3-TT-B-Cfg.txt
SRV1
N/A
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.
Step 5: Outline the troubleshooting approach and validation steps.
Use this space to identify your troubleshooting approach and the key steps to verify that the problem is resolved.
Troubleshooting approaches to select from include follow-the-path, perform-comparison, bottom-up, top-down,
divide-and-conquer, shoot-from-the-hip, and swap-components (move-the-problem) methods.
Note: In addition to a specific approach, you can use the generic troubleshooting process.
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 7 of 8
CCNPv7 TSHOOT
Device
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 8 of 8