Beruflich Dokumente
Kultur Dokumente
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 1 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
Overlay Topology
Objectives
Load the device configuration files for each trouble ticket.
Diagnose and resolve problems related to features, protocols, or technology that could be encountered in
a complex, integrated enterprise network.
Document the troubleshooting progress, configuration changes, and problem resolution.
Practice a representative sample of major technologies in routing and switching to prepare for the final
skills assessment.
Background
This lab covers a range of problems and requires that you make use of the troubleshooting skills acquired
throughout this course to resolve the routing and switching problems introduced. These trouble tickets may
involve technologies from any ROUTE or SWITCH lab. But the focus is on connectivity issues related to
RIPng, RIPv2, DHCPv4/6, HSRP, MST, VTPv3, OSPFv3, Named EIGRP, MP-BGP, VRF, prefix lists, distribute
lists, offset lists, route maps, the distance command, redistribution, EEM applets, tracking with ICMPv4
echo SLAs, tracking with IPv6 TCP SLAs, and tracking lists of objects with Boolean expressions.
For each task or trouble ticket, the trouble scenario and problem symptom are described. While
troubleshooting, you will discover the cause of the problem, correct it, and then document the process and
results.
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 2 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
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, SNMP monitor, 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 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
Lab Note: VRF_A and VRF_B are two VRFs configured on R2. This enables R2 to represent two
independent ISPs, AS65502 and AS65503. These ISPs also connect to the Internet, which is represented
by the global routing table of R2. To reiterate, R2 has a VRF_A routing table, a VRF_B routing table, and
a global routing table, which represent independent networks. It is common with VRF implementations to
have overlapping IP address spaces, where each VRF is associated with a different company. The
VRF_A routing table is displayed by entering entering show ip route vrf VPN_A and show ipv6
route vrf VPN_A on R2. The VRF_B routing table is displayed by entering entering show ip route
vrf VPN_B and show ipv6 route vrf VPN_B on R2. The global routing table represents a
globally unique address space associated with the Internet. Technically, the global routing table in this lab
is the one displayed by entering show ip route and show ipv6 route on R2 while the G0/0
interface is shut down; but much of the lab is performed with the G0/0 interface up, allowing for the
injection of other non-VRF routes from the topology into the global routing table of R2 via RIPv2, RIPng,
and EIGRP.
The network documentation and testing are incomplete and the Sandbox launch is imminent. To help
Sandbox launch on schedule, you have been contracted. Your job is to ensure the consolidated network is
fully functional under any scenario involving two or less failed service provider links. The service provider
gigabit link on R2 connecting to the Sandbox access layer switch is only available on an interim basis, as a
favor from the previous owner why it links into Sandbox at the access layer and why your company provides
dynamic addressing for the associated R2 interface is a story for another day. In any case, your first task is to
verify full IPv4 and IPv6 network functionality for Scenario 1 of Table 1 (all interfaces are up), and then
document the IPv4 and IPv6 network functionality for Scenarios 2 through 7.
The CIOs have provided you with a list of routing table outputs for you to validate against as you familiarize
yourself with the Sandbox topology and document your findings. Any errors introduced in the network
implementation are inadvertent. The CIOs give you explicit instructions that you are not to make changes to
the device configurations during this phase of preparing the Sandbox network for the grand opening.
Lab Notes:
Back-to-back Frame Relay configurations are used on the serial links in order to provide two parallel
point-to-point connections for each of the R2-R1 and R2-R3 serial links. No configuration or
troubleshooting of Frame Relay is required.
The VRF configuration on R2 is designed to simulate a multi-homed BGP environment. No
configuration or troubleshooting of VRF is required. However, to verify the routing tables of the
simulated service providers, the VRF versions of the associated traditional IOS commands are used.
There is no inter-VRF routing (route leaking) configured on R2, so the VRF_A, VRF_B, and global
routing tables on R2 are actually independent.
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 4 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
IPv4 is the BGP transport for both IPv4 and IPv6 routes.
VLANs 99, 100, 110, 120, 200, 300 are allowed on all port channel interfaces on all switches.
VLAN 300 is the only VLAN used for OSPF peering between DLS1 and DLS2.
Subsequent references in this lab to Scenario 1 should be understood to mean Scenario 1 of Table
1. Similarly for Scenarios 2-7.
Interfaces G0/1 on R1, G0/1 on R3, F0/5 on DLS1, Po1 on DLS1, Po10 on DLS1, F0/5 on DLS2, Po2
on DLS2, and Po10 on DLS2 should always be up/up during any testing and validation in Task 1.
For the purposes of this lab, R1 is assumed to not support RIPng throughout the entire lab.
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 as indicated in the Device Configuration File table.
Device Configuration File Table
or if MST is not converging properly, try shutting down Po1 and Po2 on ALS1, allowing MST to
converge between DLS1 and DLS2, and then bringing up Po1 and Po2 on ALS1.
Step 4: Configure SRV1 and start the syslog and TFTP servers.
a. Configure SRV1 with the static IPv4/6 static addressing from the Device Configuration File Table.
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 5 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
b. Start the syslog server on SRV1 to monitor console messages from multiple devices.
c. Start the TFTP server on SRV1 to record device configuration changes.
d. Start the SNMP monitor on SRV1 to record SNMPv2c trap reports.
There are several alias exec commands included in the configuration files as shortcuts, such as alias exec
sre show run | begin router eigrp., which allows you to enter sre in place of show run | begin
router eigrp. You can create your own aliases, use the ones provided, or ignore these shortcuts.
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 6 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
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 the 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: defining a problem,
gathering information, analyzing the information, eliminating possible problem causes, formulating a hypothesis
about the likely cause of the problem, testing that hypothesis, and solving the problem.
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 7 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
L 2001:DB8:CAFE:20::1/128 [0/0]
via GigabitEthernet0/1, receive
OE1 2001:DB8:CAFE:90::/126 [110/103]
via FE80::D1, GigabitEthernet0/1
OI 2001:DB8:CAFE:99::/64 [110/2]
via FE80::D1, GigabitEthernet0/1
OI 2001:DB8:CAFE:100::/64 [110/2]
via FE80::D1, GigabitEthernet0/1
OI 2001:DB8:CAFE:110::/64 [110/2]
via FE80::D1, GigabitEthernet0/1
OI 2001:DB8:CAFE:120::/64 [110/2]
via FE80::D1, GigabitEthernet0/1
OI 2001:DB8:CAFE:200::/64 [110/2]
via FE80::D1, GigabitEthernet0/1
LC 2001:DB8:CAFE:201::1/128 [0/0]
via Loopback0, receive
O 2001:DB8:CAFE:203::1/128 [110/3]
via FE80::D1, GigabitEthernet0/1
O 2001:DB8:CAFE:212::/64 [110/3]
via FE80::D1, GigabitEthernet0/1
O 2001:DB8:CAFE:300::/64 [110/2]
via FE80::D1, GigabitEthernet0/1
OE1 2001:DB8:CAFE:800::/64 [110/103]
via FE80::D1, GigabitEthernet0/1
OE1 2001:DB8:CAFE:801::/64 [110/103]
via FE80::D1, GigabitEthernet0/1
OE1 2001:DB8:CAFE:2020::2/128 [110/103]
via FE80::D1, GigabitEthernet0/1
O 2001:DB8:CAFE:2110::D1/128 [110/1]
via FE80::D1, GigabitEthernet0/1
O 2001:DB8:CAFE:2120::D2/128 [110/2]
via FE80::D1, GigabitEthernet0/1
C 2001:DB8:FEED:10::/126 [0/0]
via Serial0/0/0.1, directly connected
L 2001:DB8:FEED:10::1/128 [0/0]
via Serial0/0/0.1, receive
OE1 2001:DB8:FEED:14::/126 [110/103]
via FE80::D1, GigabitEthernet0/1
B 2001:DB8:FEED:222::2/128 [20/0]
via 2001:DB8:FEED:10::2
L FF00::/8 [0/0]
via Null0, receive
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 8 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 9 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 10 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 11 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 12 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
C 2001:DB8:CAFE:100::/64 [0/0]
via Vlan100, directly connected
L 2001:DB8:CAFE:100::D1/128 [0/0]
via Vlan100, receive
C 2001:DB8:CAFE:110::/64 [0/0]
via Vlan110, directly connected
L 2001:DB8:CAFE:110::D1/128 [0/0]
via Vlan110, receive
C 2001:DB8:CAFE:120::/64 [0/0]
via Vlan120, directly connected
L 2001:DB8:CAFE:120::D1/128 [0/0]
via Vlan120, receive
C 2001:DB8:CAFE:200::/64 [0/0]
via Vlan200, directly connected
L 2001:DB8:CAFE:200::D1/128 [0/0]
via Vlan200, receive
O 2001:DB8:CAFE:201::1/128 [110/1]
via FE80::1, FastEthernet0/5
O 2001:DB8:CAFE:203::1/128 [110/2]
via FE80::D2, Vlan300
O 2001:DB8:CAFE:212::/64 [110/2]
via FE80::D2, Vlan300
C 2001:DB8:CAFE:300::/64 [0/0]
via Vlan300, directly connected
L 2001:DB8:CAFE:300::D1/128 [0/0]
via Vlan300, receive
OE1 2001:DB8:CAFE:800::/64 [110/102]
via FE80::D2, Vlan300
OE1 2001:DB8:CAFE:801::/64 [110/102]
via FE80::D2, Vlan300
OE1 2001:DB8:CAFE:2020::2/128 [110/102]
via FE80::D2, Vlan300
LC 2001:DB8:CAFE:2110::D1/128 [0/0]
via Loopback0, receive
O 2001:DB8:CAFE:2120::D2/128 [110/1]
via FE80::D2, Vlan300
OE1 2001:DB8:FEED:10::/126 [110/101]
via FE80::1, FastEthernet0/5
OE1 2001:DB8:FEED:14::/126 [110/102]
via FE80::D2, Vlan300
OE1 2001:DB8:FEED:222::2/128 [110/101]
via FE80::1, FastEthernet0/5
C FC00::/7 [0/0]
via Tunnel0, directly connected
L FC00::D1/128 [0/0]
via Tunnel0, receive
L FF00::/8 [0/0]
via Null0, receive
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 13 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 14 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
C 2001:DB8:CAFE:99::/64 [0/0]
via Vlan99, directly connected
L 2001:DB8:CAFE:99::D2/128 [0/0]
via Vlan99, receive
C 2001:DB8:CAFE:100::/64 [0/0]
via Vlan100, directly connected
L 2001:DB8:CAFE:100::D2/128 [0/0]
via Vlan100, receive
C 2001:DB8:CAFE:110::/64 [0/0]
via Vlan110, directly connected
L 2001:DB8:CAFE:110::D2/128 [0/0]
via Vlan110, receive
C 2001:DB8:CAFE:120::/64 [0/0]
via Vlan120, directly connected
L 2001:DB8:CAFE:120::D2/128 [0/0]
via Vlan120, receive
C 2001:DB8:CAFE:200::/64 [0/0]
via Vlan200, directly connected
L 2001:DB8:CAFE:200::D2/128 [0/0]
via Vlan200, receive
O 2001:DB8:CAFE:201::1/128 [110/2]
via FE80::D1, Vlan300
R 2001:DB8:CAFE:203::1/128 [109/2]
via FE80::1, FastEthernet0/5
C 2001:DB8:CAFE:212::/64 [0/0]
via FastEthernet0/5, directly connected
L 2001:DB8:CAFE:212::D2/128 [0/0]
via FastEthernet0/5, receive
C 2001:DB8:CAFE:300::/64 [0/0]
via Vlan300, directly connected
L 2001:DB8:CAFE:300::D2/128 [0/0]
via Vlan300, receive
OE1 2001:DB8:CAFE:800::/64 [110/101]
via FE80::1, FastEthernet0/5
OE1 2001:DB8:CAFE:801::/64 [110/101]
via FE80::1, FastEthernet0/5
R 2001:DB8:CAFE:2020::2/128 [109/2]
via FE80::2, Vlan120
R 2001:DB8:CAFE:2110::D1/128 [109/2]
via FE80::D1, Vlan110
via FE80::D1, Vlan99
via FE80::D1, Vlan100
via FE80::D1, Vlan120
LC 2001:DB8:CAFE:2120::D2/128 [0/0]
via Loopback0, receive
OE1 2001:DB8:FEED:10::/126 [110/102]
via FE80::D1, Vlan300
OE1 2001:DB8:FEED:14::/126 [110/101]
via FE80::1, FastEthernet0/5
OE1 2001:DB8:FEED:222::2/128 [110/101]
via FE80::1, FastEthernet0/5
R FC00::/7 [109/2]
via FE80::2, Vlan120
via FE80::D1, Vlan120
via FE80::D1, Vlan110
via FE80::D1, Vlan100
via FE80::D1, Vlan99
L FF00::/8 [0/0]
via Null0, receive
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 15 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 16 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
Step 2: Load the device trouble ticket configuration files for TT-B.
Using the procedure described in the BASE Lab, verify that the lab configuration files are present in flash.
Load the proper configuration files as indicated in the Device Configuration File table. Watch the configuration
sequences load to ensure that no commands are failing upon being entered. Remember to check that the
appropriate SDM templates are loading on the switches.
Device Configuration File Table
Step 4: Configure SRV1 and start the syslog and TFTP servers.
a. Configure SRV1 with the static IP address 10.1.100.1/24 and default gateway 10.1.100.254.
b. Start the syslog server on SRV1 to monitor console messages from multiple devices.
c. Start the TFTP server on SRV1 to record device configuration changes.
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 17 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
Step 5: Release and renew the DHCP lease on PC-B and PC-C.
a. Ensure that PC-B is configured as a DHCP client in the OFFICE VLAN.
b. Ensure that PC-C is configured as a DHCP client in the R3 branch office LAN.
c. After loading all TT-B device configuration files, issue the ipconfig /release and ipconfig
/renew commands on PC-B and PC-C.
Step 6: 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 the 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: defining a problem,
gathering information, analyzing the information, eliminating possible problem causes, formulating a
hypothesis about the likely cause of the problem, testing that hypothesis, and solving the problem.
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 18 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 19 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
Step 2: Load the device trouble ticket configuration files for TT-C.
Using the procedure described in the BASE Lab, verify that the lab configuration files are present in flash.
Load the proper configuration files as indicated in the Device Configuration File table. Watch the configuration
sequences load to ensure that no commands are failing upon being entered. Remember to check that the
appropriate SDM templates are loading on the switches.
Device Configuration File Table
Step 4: Configure SRV1 and start the syslog and TFTP servers.
a. Configure SRV1 with the static IP address 10.1.100.1/24 and default gateway 10.1.100.254.
b. Start the syslog server on SRV1 to monitor console messages from multiple devices.
c. Start the TFTP server on SRV1 to record device configuration changes.
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 20 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
Step 5: Release and renew the DHCP lease on PC-B and PC-C.
a. Ensure that PC-B is configured as a DHCP client in the OFFICE VLAN.
b. Ensure that PC-C is configured as a DHCP client in the R3 branch office LAN.
c. After loading all TT-B device configuration files, issue the ipconfig /release and ipconfig
/renew commands on PC-B and PC-C.
Step 6: 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 the 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: defining a problem,
gathering information, analyzing the information, eliminating possible problem causes, formulating a
hypothesis about the likely cause of the problem, testing that hypothesis, and solving the problem.
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
_________________________________________________________________________________
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 21 of 22
CCNPv7 TSHOOT Lab 10-2, Sandbox
2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 22 of 22