1-4 Semester 8 Internetwork Troubleshooting v1.0 - Lab 1.2.9.3 Copyright  2001, Cisco Systems, Inc. Lab 1.2.9.3: Basic Troubleshooting Process 3 WAN Network 2 192.168.0.96 /30 WAN Network 1 192.168.0.100 /30 SanJose1 Objective Apply the basic troubleshooting model to a simple network problem. To perform this lab read the scenario to make sure that you understand the problem from the user’s standpoint, follow the lab steps, and apply any basic troubleshooting skills that you learned in earlier Cisco courses. Remember that for this lab we are concentrating on the troubleshooting model, not any particular IOS commands. Scenario As far as you know the SanJose1 router is functioning fine. There are no user complaints. You are preparing to upgrade the IOS image and will be performing the upgrade using a TFTP server and controlling it from a console connection. Note: Since you will not actually perform the upgrade you do not need to have a TFTP server present to complete the lab. Step 1 Note: This lab may only function properly on a Cisco 2600 router. The key command fails on the 2500s that we have tested. Configure a workstation with the following settings and attach it to the Fast Ethernet or Ethernet interface on any router (same as last lab): 2-4 Semester 8 Internetwork Troubleshooting v1.0 - Lab 1.2.9.3 Copyright  2001, Cisco Systems, Inc. IP address: 192.168.0.34 (or any valid host in subnet 192.168.0.32 /27) Subnet mask: 255.255.255.224 Default Gateway: 192.168.0.33 Note: This is the same host configuration from the last lab. Use the same steps as the last lab to clear and paste the configuration file Lab1-2-9-3-SanJose1BrokenConfig.txt into any Cisco IOS-based router with at least one Ethernet / Fast Ethernet interface. Note: The “load” file is configured to support many routers with various interfaces, so do not be alarmed if you see error messages scroll by. Disconnect the console cable after loading the configuration. Step 2 From the MS-DOS (or Command) window of the workstation, ping SanJose1’s Ethernet interface (192.168.0.33) and one of the WAN interfaces (192.168.0.97 or 192.168.0.101). Both commands should work indicating that the router is functioning at some level. Use a console connection to access the SanJose1 router to prepare for the TFTP session. You should encounter a problem. 1. What are you seeing? Step 3 2. Gather the facts about the situation at hand. Assuming the router is working properly, how might you try to gain access to see what is going on? 3. It is possible to get to the router. Which IOS commands might you use to determine the problem? 4. What are the likely problems, considering only the console connection appears to be damaged? 3-4 Semester 8 Internetwork Troubleshooting v1.0 - Lab 1.2.9.3 Copyright  2001, Cisco Systems, Inc. Step 4 5. Examine the facts you have just listed. Based on your observations, consider the possible causes of the problem. Step 5 6. Create an action plan to solve this problem. Step 6 Implement the action plan and attempt to fix the problem! 7. Observe the results of your implementation. Did it fix the problem? List your results and observations below. Step 7 If your solution did not fix the problem, undo your changes and repeat the process. 8. If your solution did fix the problem, document the results below. Reflection 9. What if no password had been set on the vty connections? 4-4 Semester 8 Internetwork Troubleshooting v1.0 - Lab 1.2.9.3 Copyright  2001, Cisco Systems, Inc. 10. Could you use the AUX port as a last effort? Try just putting the console cable in the AUX port (if present). If no password is set for AUX, you won’t get in. 11. What if the speed 2400 command had been set on all of the possible connection options? What would you do? There are two possible solutions. . Troubleshooting v1.0 - Lab 1.2.9 .3 Copyright  2001, Cisco Systems, Inc. Lab 1.2.9 .3: Basic Troubleshooting Process 3 WAN Network 2 192.168.0.96 /30 WAN. Internetwork Troubleshooting v1.0 - Lab 1.2.9 .3 Copyright  2001, Cisco Systems, Inc. IP address: 192.168.0 .34 (or any valid host in subnet 192.168.0 .32 /27)