Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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.
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 1 of 17
CCNPv6 TSHOOT
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 are based on scenarios from previous labs. This lab focuses on routing and switching connectivity issues related to EtherChannel, STP, OSPF, EIGRP, and ACLs. 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.
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-mz image or comparable) SRV1 (Windows PC with static IP address) with TFTP and syslog servers plus an SSH client (PuTTY or comparable) and WireShark software PC-B (Windows PC DHCP client) with PuTTY and WireShark software PC-C (Windows PC DHCP client) with PuTTY and WireShark software Serial and Ethernet cables
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 2 of 17
CCNPv6 TSHOOT
Step 2: Load the device trouble ticket configuration files for TT-A.
Using the procedure described in Lab 3-1, verify that the lab configuration files are present in flash. Load the proper configuration files as 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. Telnet and SSH require username admin and password adminpa55. The enable password is ciscoenpa55.
Lab101-ALS1-TT-A-Cfg.txt Lab101-DLS1-TT-A-Cfg.txt Lab101-DLS2-TT-A-Cfg.txt Lab101-R1-TT-A-Cfg.txt Lab101-R2-TT-A-Cfg.txt Lab101-R3-TT-A-Cfg.txt N/A N/A N/A Static IP: 10.1.50.1 Default gateway: 10.1.50.254 DHCP DHCP
Step 3: Configure SRV1 and start the syslog and TFTP servers.
a. Configure SRV1 with the static IP address 10.1.50.1/24 and default gateway 10.1.50.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.
Step 4: 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-A device configuration files, issue the ipconfig /release and ipconfig /renew commands on PC-B and PC-C.
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 3 of 17
CCNPv6 TSHOOT
Device
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 4 of 17
CCNPv6 TSHOOT
Key Information Displayed Displays link status, speed, duplex, trunk or VLAN membership, and interface descriptions. Displays detailed information about a neighbor (or neighbors) including network address, enabled protocols, hold time, and software version. Displays all essential parameters that affect the topology, such as root port, designated ports, port state, and port type, as well as the spanning-tree mode implemented. Displays the spanning-tree mode and the VLANs for which this switch is the root bridge. VLANs are listed along with the number of ports in various STP states. Displays an overview of all existing VLANs and the ports within them. Trunk ports are not listed. Displays whether the VLAN exists and which ports are assigned to it. Includes which trunk ports that the VLAN is allowed on. Displays all trunk ports, the operational status, trunk encapsulation, and native VLAN, as well as the list of allowed VLANs, active VLANs, and the VLANs in Spanning Tree Forwarding state for the trunk. Checks all VLAN-related parameters for a specific interface (access ports and trunk ports). Displays port channels, member ports, and flags indicating status.
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 5 of 17
CCNPv6 TSHOOT
Step 2: Load the device trouble ticket configuration files for TT-B.
Using the procedure described in Lab 3-1, verify that the lab configuration files are present in flash. Load the proper configuration files as 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. Telnet and SSH require username admin and password adminpa55. The enable password is ciscoenpa55.
Lab101-ALS1-TT-B-Cfg.txt Lab101-DLS1-TT-B-Cfg.txt Lab101-DLS2-TT-B-Cfg.txt Lab101-R1-TT-B-Cfg.txt Lab101-R2-TT-B-Cfg.txt Lab101-R3-TT-B-Cfg.txt N/A N/A N/A Static IP: 10.1.50.1 Default gateway: 10.1.50.254 DHCP DHCP
Step 3: Configure SRV1 and start the syslog and TFTP servers.
a. Configure SRV1 with the static IP address 10.1.50.1/24 and default gateway 10.1.50.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.
Step 4: 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.
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 6 of 17
CCNPv6 TSHOOT
_______________________________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________ 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 what you think the problem might be and the actions you take to correct the problem. Note: In addition to the commands listed for TT-A, the table of commands following this log might be helpful in troubleshooting this problem. You can also refer to Labs 5-2 and 5-3 for sample troubleshooting flows and additional commands.
Device Actions and Results
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 7 of 17
CCNPv6 TSHOOT
Command show ip route or show ip route ip-addr show ip ospf interface brief
Key Information Displayed Displays the entire routing table or information for a particular destination address. Displays interfaces that are participating in the OSPF routing process. An interface does not need to be operational to be listed in the command output. Displays the OSPF neighbor table to verify that all expected neighbor relationships are operational. Displays local and learned network entries in the BGP table with next hop, metric, local preference, weight, and AS path. Displays a summary of the BGP neighbor table. Lists important BGP parameters, such as the AS number and router ID, statistics about the memory consumption of the various BGP data structures, and a brief overview of the configured neighbors and their state. Displays parameters and extensive statistics about the peering session for all BGP neighbors. Verifies the link types and link IDs for all areas in which this device participates.
show ip bgp
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 8 of 17
CCNPv6 TSHOOT
Step 2: Load the device trouble ticket configuration files for TT-C.
Using the procedure described in Lab 3-1, verify that the lab configuration files are present in flash. Load the proper configuration files as 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. Telnet and SSH require username admin and password adminpa55. The enable password is ciscoenpa55.
Lab101-ALS1-TT-C-Cfg.txt Lab101-DLS1-TT-C-Cfg.txt Lab101-DLS2-TT-C-Cfg.txt Lab101-R1-TT-C-Cfg.txt Lab101-R2-TT-C-Cfg.txt Lab101-R3-TT-C-Cfg.txt N/A N/A N/A Static IP: 10.1.50.1 Default gateway: 10.1.50.254 DHCP DHCP
Step 3: Configure SRV1 and start the syslog and TFTP servers.
a. Configure SRV1 with the static IP address 10.1.50.1/24 and default gateway 10.1.50.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.
Step 4: 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-C device configuration files, issue the ipconfig /release and ipconfig /renew commands on PC-B and PC-C.
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 9 of 17
CCNPv6 TSHOOT
_______________________________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________ 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 that you used to gather information. As you progress, record what you think the problem might be and the actions you take to correct the problem. Note: In addition to the commands listed for TT-A and TT-B, the table of commands following this log might help you troubleshoot this problem. You can also refer to Lab 5-1 and the Chapter 9 labs for sample troubleshooting flows and additional commands.
Device Actions and Results
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 10 of 17
CCNPv6 TSHOOT
Key Information Displayed Displays the next hop and interface used for a particular destination address from the CEF table. Verifies active and standby roles and IP addresses for all VLANs on an HSRP router. Displays interfaces that are participating in the EIGRP routing process. An interface does not need to be operational to be listed in the output. Displays the EIGRP neighbor table to verify that all expected neighbor relationships are operational. Displays all ACLs configured on a device, including the ACL number and name, the type (standard or extended), the statements, and the number of matches accumulated for each statement. Displays the clock synchronization status, stratum level, and reference clock IP address. Also shows the number of seconds since the last update was received from the reference clock.
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 11 of 17
CCNPv6 TSHOOT
Step 2: Load the device trouble ticket configuration files for TT-D.
Using the procedure described in Lab 3-1, verify that the lab configuration files are present in flash. Load the proper configuration files as 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. Telnet and SSH require username admin and password adminpa55. The enable password is ciscoenpa55.
Lab101-ALS1-TT-D-Cfg.txt Lab101-DLS1-TT-D-Cfg.txt Lab101-DLS2-TT-D-Cfg.txt Lab101-R1-TT-D-Cfg.txt Lab101-R2-TT-D-Cfg.txt Lab101-R3-TT-D-Cfg.txt N/A N/A N/A Static IP: 10.1.50.1 Default gateway: 10.1.50.254 DHCP DHCP
Step 4: Configure SRV1 and start the syslog and TFTP servers.
a. Configure SRV1 with the static IP address 10.1.50.1/24 and default gateway 10.1.50.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.
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-D device configuration files, issue the ipconfig /release and ipconfig /renew commands on PC-B and PC-C.
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 12 of 17
CCNPv6 TSHOOT
_______________________________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________ Step 7: Record the troubleshooting process and configuration changes.
Use this log to document your actions and results during the troubleshooting process. List the commands that you used to gather information. As you progress, record what you think the problem might be and the actions you take to correct the problem. Note: The table of commands following this log might help you troubleshoot this problem.
Device Actions and Results
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 13 of 17
CCNPv6 TSHOOT
Key Information Displayed Displays the device hardware and software status. Displays the files and directories in flash memory.
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 14 of 17
CCNPv6 TSHOOT
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 15 of 17
CCNPv6 TSHOOT
Reflection Questions
1. Which lab trouble tickets did you have the most difficulty with? __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ 2. Would you change anything about the process that you used for any of the trouble tickets now that you see the resolution of the problem? __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ 3. Which commands did you find most useful in diagnosing issues? __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 16 of 17
CCNPv6 TSHOOT
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 effectively list all the 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 may contain one. An example of this might be an ISDN BRI interface. The string in parenthesis is the legal abbreviation that can be used in Cisco IOS commands to represent the interface.
All contents are Copyright 19922010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 17 of 17