17.7.7 Packet Tracer - Troubleshoot Connectivity Issues - Physical Mode Answers
Topology
17.7.7 Packet Tracer - Troubleshoot Connectivity Issues - Physical Mode
Addressing Table
| Device | Interface | IP Address | Subnet Mask | Default Gateway |
|---|---|---|---|---|
| R1 | G0/0/1 | 192.168.1.1 | 255.255.255.0 | N/A |
| G0/0/0 | 10.1.1.1 | 255.255.255.252 | N/A | |
| ISP | G0/0/0 | 10.1.1.2 | 255.255.255.252 | N/A |
| Lo0 | 209.165.200.226 | 255.255.255.255 | N/A | |
| S1 | VLAN 1 | 192.168.1.2 | 255.255.255.0 | 192.168.1.1 |
| PC-A | NIC | 192.168.1.10 | 255.255.255.0 | 192.168.1.1 |
Objectives
- Part 1: Identify the Problem
- Part 2: Implement Network Changes
- Part 3: Verify Full Functionality
- Part 4: Document Findings and Configuration Changes
Background / Scenario
In this Packet Tracer Physical Mode (PTPM) activity, the company that you work for is experiencing problems with their LAN. You have been asked to troubleshoot and resolve the network issues. In Part 1, you will connect to devices on the LAN and use troubleshooting tools to identify the network issues, establish a theory of probable cause, and test that theory. In Part 2, you will establish a plan of action to resolve and implement a solution. In Part 3, you will verify that full functionality has been restored. Part 4 provides space for you to document your troubleshooting findings along with the configuration changes that you made to the LAN devices.
Instructions
Part 1: Identify the Problem
The only available information about the network problem is that the users are experiencing slow response times and that they are not able to reach an external device on the internet at IP address 209.165.200.226. To determine probable cause(s) for these network issues, you will need to utilize network commands and tools on the LAN equipment.
Note: The username admin01 with a password of cisco12345 will be required to log on to the network equipment.
Step 1: Troubleshoot the network.
Use the tools available to you to troubleshoot the network, keeping in mind that the requirement is to restore connectivity to the external server and eliminate slow response times.
Step 2: Document the probable causes.
List the probable causes for the network problems that employees are experiencing.
- The Default Gateway is not set on the PC.
- S1 Interface F0/5 is set to half duplex and speed set to 10.
- S1 default-gateway is set to 192.168.1.0.
- R1 G0/0/1 is set to half duplex, the speed is set to 10, and the bandwidth is set to 10000 kb/s.
- The gateway of last resort is not set on R1.
Part 2: Implement Network Changes
You have communicated the problems that you discovered in Part 1 to your supervisor. She has approved these changes and has requested that you implement them.
S1(config)# interface fastethernet 0/5 S1(config-if)# speed 100 S1(config-if)# duplex full
S1(config)# ip default-gateway 192.168.1.1
R1(config)# interface gigabitethernet 0/0/1 R1(config-if)# no bandwidth R1(config-if)# speed 100 R1(config-if)# duplex full
R1(config)# ip route 0.0.0.0 0.0.0.0 10.1.1.2
Part 3: Verify Full Functionality
Verify that full functionality has been restored. PC-A, S1, and R1 should be able to reach the external server, and ping replies from PC-A to the external server should exhibit no significant variation in response times.
C:\> ping 209.165.200.226
S1# ping 209.165.200.226
R1# ping 209.165.200.226
Part 4: Document Findings and Configuration Changes
Use the space provided below to document the issues found during your troubleshooting and the configuration changes made to resolve those issues.
Documentation will vary but should include the date when troubleshooting was conducted, devices that were tested, commands used along with the output generated by those commands, issues found, and configuration changes made to resolve those issues.
Reflection Question
This Packet Tracer Lab Companion had you troubleshoot all devices before making any changes. Is there another way to apply the troubleshooting methodology?
Answers may vary. Another way the troubleshooting methodology could be applied would be to complete all 6 steps on a device before moving on to another device. For example, after you determined that the default gateway was not set on the PC, you would add the default gateway setting and verify functionality. If network issues still exist, you would then move on to the next device, S1 in this example. When the troubleshooting process had been completed on S1 and issues still existed, you would then move on to R1. This process would continue until full network functionality was achieved.
Issues Found and Solutions
| # | Device | Issue | Solution |
|---|---|---|---|
| 1 | PC-A | No default gateway configured | Set the default gateway to 192.168.1.1 |
| 2 | S1 F0/5 | Forced to 10 Mbps half duplex: collisions and slow response times | Set speed 100 and duplex full |
| 3 | S1 | Default gateway set to 192.168.1.0 (the network address, not a host) | Change it to 192.168.1.1 |
| 4 | R1 G0/0/1 | Configured with bandwidth 10000, speed 10 and half duplex: duplex mismatch with S1 | Remove the bandwidth statement (no bandwidth), then set speed 100 and duplex full |
| 5 | R1 | No gateway of last resort: no route to the internet (209.165.200.226) | Add a default route: ip route 0.0.0.0 0.0.0.0 10.1.1.2 |
Device Configs - Final
ROUTER R1
! ============================================================== !--- 17.7.7 Packet Tracer - Troubleshoot Connectivity Issues - Physical Mode !--- FIX SCRIPT FOR ROUTER R1 !--- Usage: open the R1 console (no login is required; R1 has no enable password) and paste this file at the R1> prompt. This is a troubleshooting activity: the script contains only the fixes for R1. Every line beginning with "!" is a comment; IOS ignores it. ! ============================================================== enable configure terminal ! -------------------------------------------------------------- !--- Part 2: Implement Network Changes. ! -------------------------------------------------------------- !--- Probable cause 4: G0/0/1 (LAN side) is configured with "bandwidth 10000", "duplex half" and "speed 10". Remove the bandwidth statement (it lowers the bandwidth/delay values used by the router), then set 100 Mbps full duplex to match S1 F0/5. interface gigabitethernet 0/0/1 no bandwidth speed 100 duplex full exit !--- Probable cause 5: R1 has no gateway of last resort. Add a default route to the ISP router (next hop 10.1.1.2) so traffic can reach 209.165.200.226. ip route 0.0.0.0 0.0.0.0 10.1.1.2 end ! -------------------------------------------------------------- !--- Save the configuration to NVRAM. (Press Enter when prompted for the destination filename.) ! -------------------------------------------------------------- copy running-config startup-config ! ============================================================== !--- Verification: !--- show interfaces gigabitethernet 0/0/1 -> Full-duplex, 100Mb/s; BW no longer 10000 Kbit !--- show ip route -> Gateway of last resort is 10.1.1.2 to network 0.0.0.0 !--- ping 209.165.200.226 -> !!!!! ! ==============================================================
SWITCH S1
! ============================================================== !--- 17.7.7 Packet Tracer - Troubleshoot Connectivity Issues - Physical Mode !--- FIX SCRIPT FOR SWITCH S1 !--- Usage: open the S1 console (no login is required; S1 has no enable password) and paste this file at the S1> prompt. This is a troubleshooting activity: the script contains only the fixes for S1. Every line beginning with "!" is a comment; IOS ignores it. ! ============================================================== enable configure terminal ! -------------------------------------------------------------- !--- Part 2: Implement Network Changes. ! -------------------------------------------------------------- !--- Probable cause 2: F0/5 (uplink to R1) is forced to 10 Mbps half duplex. Set 100 Mbps full duplex to match R1 G0/0/1. interface fastethernet 0/5 speed 100 duplex full exit !--- Probable cause 3: the default gateway is 192.168.1.0 (the network address). Set it to R1 G0/0/1, 192.168.1.1; the new value replaces the old one. ip default-gateway 192.168.1.1 end ! -------------------------------------------------------------- !--- Save the configuration to NVRAM. (Press Enter when prompted for the destination filename.) ! -------------------------------------------------------------- copy running-config startup-config ! ============================================================== !--- Verification: !--- show interfaces fastethernet 0/5 -> Full-duplex, 100Mb/s !--- show running-config | include default-gateway -> ip default-gateway 192.168.1.1 !--- ping 209.165.200.226 -> !!!!! ! ==============================================================
PC-A
Download Packet Tracer (.pka) file:
