You are on page 1of 9

CCNPv6 TSHOOT

Skills-Based Assessment

Topology

All contents are Copyright 19922011 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 1 of 9

CCNPv6 TSHOOT

IP Addressing Table
Device R1 Interface/SVI FA0/1 S0/0/0 (DCE) Lo0 R2 S0/0/0 Lo0 Lo1 R3 FA0/0 FA0/1 Lo0 Lo1 ALS1 DLS1 DLS1 DLS1 DLS1 DLS1 DLS1 DLS1 DLS1 DLS2 DLS2 DLS2 DLS2 DLS2 DLS2 DLS2 DLS2 SRV1 PC-B PC-C VLAN 100 Fa0/5 Lo0 VLAN 10 VLAN 20 VLAN 30 VLAN 50 VLAN 100 VLAN 200 Fa0/5 Lo0 VLAN 10 VLAN 20 VLAN 30 VLAN 50 VLAN 100 VLAN 200 NIC NIC NIC IP Address 172.16.2.2 209.165.200.225 192.168.1.1 209.165.200.226 192.168.2.1 172.30.1.1 172.16.80.1 172.16.2.14 172.16.203.1 172.16.80.129 172.16.100.1 172.16.2.1 172.16.211.1 172.16.10.252 172.16.20.252 172.16.30.252 172.16.50.252 172.16.100.252 172.16.200.252 172.16.2.13 172.16.212.1 172.16.10.253 172.16.20.253 172.16.30.253 172.16.50.253 172.16.100.253 172.16.200.253 172.16.50.1 172.16.10.x (DHCP) 172.16.80.x (DHCP) Subnet Mask 255.255.255.252 255.255.255.252 255.255.255.255 255.255.255.252 255.255.255.255 255.255.255.255 255.255.255.128 255.255.255.252 255.255.255.255 255.255.255.252 255.255.255.0 255.255.255.252 255.255.255.255 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.252 255.255.255.255 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.128 Default Gateway N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A 172.16.100.254 172.16.2.1 N/A 172.16.10.254 172.16.20.254 172.16.30.254 172.16.50.254 172.16.100.254 N/A 172.16.2.14 N/A 172.16.10.254 172.16.20.254 172.16.30.254 172.16.50.254 172.16.100.254 N/A 172.16.50.254 172.16.10.254 172.16.80.1

All contents are Copyright 19922011 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 2 of 9

CCNPv6 TSHOOT

Device Interfaces and Links Table


From Device ALS1 ALS1 ALS1 ALS1 ALS1 DLS1 DLS1 DLS1 DLS1 DLS2 R1 R3 Interface Fa0/1 Fa0/2 Fa0/3 Fa0/4 Fa0/18 Fa0/3 Fa0/4 Fa0/5 Fa0/6 Fa0/5 S0/0/0 (DCE) Fa0/0 To Device DLS1 DLS1 DLS2 DLS2 PC-B DLS2 DLS2 R1 SRV1 R3 R2 PC-C Interface Fa0/1 Fa0/2 Fa0/1 Fa0/2 NIC Fa0/3 Fa0/4 Fa0/1 NIC Fa0/1 S0/0/0 NIC WAN link, PPP EtherChannel Po10, 802.1Q EtherChannel Po10, 802.1Q Layer 1 and 2 Features and Protocols Used EtherChannel Po1, 802.1Q EtherChannel Po1, 802.1Q EtherChannel Po2, 802.1Q EtherChannel Po2, 802.1Q

Objectives
Part 1: Erase the startup config and copy the SBA error file from flash to the running config for each device. Part 2: Troubleshoot the errors introduced.

Exam Overview
This skills-based assessment (SBA) is the final practical exam of Academy training for the course CCNPv6 TSHOOT. In Part 1, you erase the base configs and load the error configs. You troubleshoot and resolve the errors in Part 2. In addition to correcting configurations and restoring basic connectivity, network protocols such as Telnet, SSH, and NTP must also be verified. Note: Refer to the Topology diagram, IP Addressing table, and Device Interfaces and Links table in the beginning of the SBA when troubleshooting issues. This lab uses Cisco 1841 routers with Cisco IOS Release 12.4(24)T1 and the Advanced IP Services image c1841-advipservicesk9-mz.124-24.T1.bin. The switches are Cisco WS-C2960-24TT-L with the Cisco IOS image c2960-lanbasek9-mz.122-46.SE.bin and Catalyst 3560-24PS with the Cisco IOS image c3560advipservicesk9-mz.122-46.SE.bin. Other routers (such as a 2801 or 2811), switches (such as a 2950 or 3550), and Cisco IOS Software versions can be used if they have comparable capabilities and features. 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.

All contents are Copyright 19922011 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 3 of 9

CCNPv6 TSHOOT

Required Resources
3 routers (Cisco 1841 with Cisco IOS Release 12.4(24)T1 Advanced IP Service or comparable) 1 switch (Cisco 2960 with the Cisco IOS Release 12.2(46)SE C2960-LANBASEK9-M image or comparable) 2 switches (Cisco 3560 with the Cisco IOS Release 12.2(46)SE C3560-ADVIPSERVICESK9-M image or comparable) SRV1 (Windows PC with a static IP address) with TFTP and syslog servers, plus an SSH client (PuTTY or comparable) and WireShark software PC-B (Windows PCDHCP client) with PuTTY and WireShark software PC-C (Windows PCDHCP client) with PuTTY and WireShark software Serial and Ethernet cables

Part 1: Load the SBA Error Files from Flash to the Running Config
Step 1: Verify the existence and location of the SBA error configuration files.
The error configuration file should be present in flash under the tshoot directory for a given device. Use the show flash command to verify the presence of this directory. You can also verify the contents of the directory using the dir command. If the directory and files are not present, contact your instructor.

Step 2: Erase the startup config from NVRAM. Step 3: Delete the VLAN database from flash (switches only). Step 4: Reload the device, but do not save the system configuration if prompted. Step 5: When the device restarts, do not enter the initial configuration dialog, but terminate autoinstall if prompted. Step 6: Copy the SBA device error configuration file from flash to the running config.
The format of these files is TSHOOT-SBA-Stud_xxx-Error-Cfg.txt, where xxx is the name of the device. For example: Switch#copy flash:/tshoot/TSHOOT-SBA-Stud_ALS1-Error-Cfg.txt running-config Destination filename [running-config]? <Enter> ALS1# Note: Although it is possible to copy the file to the startup config and reload the device, the RSA keys for SSH cannot be generated from the startup config.

Step 7: Copy the running config to the startup config.


Even if you see an Autosave message indicating that the running configuration has been saved to NVRAM, copy the running config to the startup config manually. Note: If the device is rebooted at this point, you can log in remotely with the username admin and the password adminpa55. To access privileged EXEC mode, use the enable password ciscoenpa55. Note: Although it is not considered security best practice, you can change the exec-timeout for the console line to 0 (no time out) to facilitate performance of this SBA.

All contents are Copyright 19922011 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 4 of 9

CCNPv6 TSHOOT

Step 8: Repeat Steps 2 through 7 for all other devices in the network. Step 9: Set the time on the NTP server R2.
Set the correct time on the NTP server R2 using the clock set command.

Step 10: Configure the PCs.


a. Configure SRV1 with the static IP address 172.16.50.1/24 and the default gateway 172.16.50.254. b. Start the syslog server and TFTP server on SRV1. c. Configure PC-B and PC-C as DHCP clients.

d. Release and renew the DHCP leases on PC-B and PC-C. Note: It is important to release and renew the DHCP leases on PC-B and PC-C because the PCs may have obtained a valid IP address previously and this could mask a problem.

Part 2: Troubleshoot the Errors Introduced


The SBA error files introduce various problems, including issues related to STP, NTP, SSH, VLANs, EtherChannel, HSRP, DHCP, EIGRP, OSPF, and BGP. Hint: Two configuration errors are introduced in each device for a total of 12 errors.

Step 1: Perform connectivity tests.


Use connectivity testing tools such as ping, traceroute, tracert (PC), and Cisco Discovery Protocol to determine the extent of connectivity loss. Use the following table to record the results of the connectivity tests. Be sure to ping from each PC to each network device interface and from each network device to every other network device using the various network addresses available, as shown in the IP Addressing table at the beginning of the SBA. Note: You can use the Ping Test table in Step 3 as a starting point.

Network Connectivity Test Table


Command From Device/Interface/IP To Device/Interface/IP Result

All contents are Copyright 19922011 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 5 of 9

CCNPv6 TSHOOT

Step 2: Document, resolve, and verify the issues discovered.


Using the tools available, such as show and debug commands, discover each problem, correct it, and document the corrective action taken. Use the Problem Resolution and Verification table to document the problem discovered, the affected devices, and the solution to the problem, including the commands used. Note: For each device, after issuing corrective commands, copy the running config to the startup config. Tip: If connecting from one device to another via Telnet, issue the terminal monitor command so that console and debug messages generated on the remote device can be viewed on the local console.

Problem Resolution and Verification Table


Device Problem or Error Discovered Corrective Action (commands used) Verification Commands (more than one command can be used)

Notes __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________

All contents are Copyright 19922011 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 6 of 9

CCNPv6 TSHOOT

Step 3: Demonstrate basic network connectivity after correcting errors.


With all devices connected and all problems resolved, you should be able to ping from any device in the network to any other device. Perform pings according to the Ping Test table below. Note: All pings in the table must be successful. If not, there are issues that need to be resolved.

Ping Test Table


From Device/Interface/IP PC-B PC-B PC-B PC-B PC-B PC-B PC-B PC-B PC-B PC-C PC-C PC-C PC-C PC-C PC-C PC-C PC-C ALS1 mgmt vlan 100 (172.16.100.1) ALS1 mgmt vlan 100 ALS1 mgmt vlan 100 ALS1 mgmt vlan 100 ALS1 mgmt vlan 100 Notes __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ To Device/Interface/IP PC-C (DHCP 172.16.80.2) HSRP default gateway (172.16.10.254) SRV1 (172.16.50.1) ALS1 mgmt (172.16.100.1) DLS1 mgmt (172.16.100.252) DLS2 mgmt (172.16.100.253) R1 Fa0/1 (172.16.2.2) R2 Lo1 (172.30.1.1) R3 Fa0/1 (172.16.2.14) R3 default gateway (172.16.80.1) SRV1 (172.16.50.1) ALS1 mgmt (172.16.100.1) DLS1 mgmt (172.16.100.252) DLS2 mgmt (172.16.100.253) R1 Fa0/1 (172.16.2.2) R2 Lo1 (172.30.1.1) R3 Fa0/1 (172.16.2.14) DLS1 mgmt (172.16.100.252) DLS2 mgmt (172.16.100.253) R1 Fa0/1 (172.16.2.2) R2 Lo1 (172.30.1.1) R3 Fa0/1 (172.16.2.14) Successful (Y/N)

Step 4: Demonstrate Telnet and SSH connectivity.


From PC-B, connect to each network device using Telnet (from the command prompt) and SSH (from an SSH client such as PuTTY) to verify remote management capability. Note: Connecting to each device via Telnet and SSH must be successful. If not, there are issues that need to be resolved.

All contents are Copyright 19922011 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 7 of 9

CCNPv6 TSHOOT

Remote Access Test Table


From Device PC-B PC-B PC-B PC-B PC-B PC-B To Device/Interface/IP ALS1 mgmt (172.16.100.1) DLS1 mgmt (172.16.100.252) DLS2 mgmt (172.16.100.253) R1 Fa0/1 (172.16.2.2) R2 S0/0/0 (209.165.200.226) R3 Fa0/1 (172.16.2.14) Telnet (Y/N) SSH (Y/N)

Step 5: Demonstrate NTP functionality.


Check each network device to verify that it has synchronized with the NTP server R2. Note: Each device must synchronize with the NTP server R2. If not, there are issues that need to be resolved.

NTP Synchronization Table


Device ALS1 DLS1 DLS2 R1 R2 R3 NTP Status Synched (Y/N)

Step 6: Demonstrate network redundancy for PC-B after correcting errors.


a. Disable (shut down) DLS2 port channel Po2. b. Ping from PC-B to all other devices in the network. Pings from PC-B to each of the other PCs and network devices must be successful. If not, there are issues that need to be resolved. c. Renew and release the PC-B IP address. PC-B should be able to obtain an IP address on subnet 172.16.10.0/24. If not, there are issues that need to be resolved.

STP Redundancy Test Table


From Device/Interface/IP PC-B PC-B PC-B PC-B PC-B PC-B PC-B PC-B PC-B To Device/Interface/IP HSRP default gateway (172.16.10.254) PC-C SRV1 (172.16.50.1) ALS1 mgmt (172.16.100.1) DLS1 mgmt (172.16.100.252) DLS2 mgmt (172.16.100.253) R1 Fa0/1 (172.16.2.2) R2 Lo1 (172.30.1.1) R3 Fa0/1 (172.16.2.14) Result

All contents are Copyright 19922011 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 8 of 9

CCNPv6 TSHOOT

Notes: __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________

Router Interface Summary Table


Router Interface Summary Router Model 1700 1800 2600 2800 Ethernet Interface #1 Fast Ethernet 0 (FA0) Fast Ethernet 0/0 (FA0/0) Fast Ethernet 0/0 (FA0/0) Fast Ethernet 0/0 (FA0/0) Ethernet Interface #2 Fast Ethernet 1 (FA1) Fast Ethernet 0/1 (FA0/1) Fast Ethernet 0/1 (FA0/1) Fast Ethernet 0/1 (FA0/1) Serial Interface #1 Serial 0 (S0) Serial 0/0/0 (S0/0/0) Serial 0/0 (S0/0) Serial 0/0/0 (S0/0/0) Serial Interface #2 Serial 1 (S1) Serial 0/0/1 (S0/0/1) Serial 0/1 (S0/1) Serial 0/0/1 (S0/0/1)

Note: To find out how the router is configured, look at the interfaces to identify the type of router and how many interfaces the router has. There is no way to list all combinations of configurations for each router class. This table includes identifiers for the possible combinations of Ethernet and serial interfaces in the device. The table does not include any other type of interface, even though a specific router might contain one, such as an ISDN BRI interface. The string in parenthesis is the legal abbreviation that can be used in Cisco IOS commands to represent the interface. Note: The first group of configurations is the functioning base set that does not contain errors. The second group of configurations is the error set that does contain errors.

All contents are Copyright 19922011 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 9 of 9