17.7.7 Packet Tracer - Troubleshoot Connectivity Issues - Physical Mode Answers

17.7.7 Packet Tracer - Troubleshoot Connectivity Issues - Physical Mode Answers

Topology

17.7.7 Packet Tracer - Troubleshoot Connectivity Issues - Physical Mode

Addressing Table

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 the eliminate slow response times.

Step 2: Document the probable causes.

List the probable causes for the network problems that employees are experiencing.

1. The Default Gateway is not set on the PC.
2. S1 Interface F0/5 is set to half duplex and speed set to 10.
3. S1 default-gateway is set to 192.168.1.0
4. R1 G0/0/1 is set to half duplex and the speed is set to 10.
5. 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.

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.

Part 4: Document Findings and Configuration Changes

Use the space provided below to document the issues found during your troubleshooting and the configurations 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.

Device Configs – Final

Switch S1:

! ==============================================================
!--- 17.7.7 Packet Tracer - Troubleshoot Connectivity Issues (Physical Mode)
!--- FIX SCRIPT FOR SWITCH S1
!--- Usage: copy this whole file and paste it into the SWITCH S1 terminal (start at the S1> prompt). Log in with username admin01 / password cisco12345. This is a TROUBLESHOOTING lab: the script applies only the corrective commands for the diagnosed faults.
! ==============================================================

enable
configure terminal

! --------------------------------------------------------------
!--- Fault 2: F0/5 (uplink to R1) was stuck at half duplex / 10 Mbps, causing collisions and slow response times.
! --------------------------------------------------------------

!--- Restore the uplink to 100 Mbps full duplex to match R1.
interface f0/5
 speed 100
 duplex full
 exit

! --------------------------------------------------------------
!--- Fault 3: the switch default gateway was set to 192.168.1.0 (a network address, not a host), so S1 could not reach anything off its LAN.
! --------------------------------------------------------------

!--- Set the correct default gateway (R1 G0/0/1). Re-issuing this command replaces the wrong value.
ip default-gateway 192.168.1.1

end

! --------------------------------------------------------------
!--- Save the configuration to NVRAM. (Press Enter when prompted.)
! --------------------------------------------------------------
copy running-config startup-config


! ==============================================================
!--- Verification:
!---   show interfaces f0/5           -> 100 Mb/s, Full-duplex
!---   show running-config | include default-gateway  -> 192.168.1.1
!---   ping 209.165.200.226           -> S1 reaches the external server
! ==============================================================

Router R1:

! ==============================================================
!--- 17.7.7 Packet Tracer - Troubleshoot Connectivity Issues (Physical Mode)
!--- FIX SCRIPT FOR ROUTER R1
!--- Usage: copy this whole file and paste it into the ROUTER R1 terminal (start at the R1> prompt). Log in with username admin01 / password cisco12345. This is a TROUBLESHOOTING lab: the script applies only the corrective commands for the diagnosed faults.
! ==============================================================

enable
configure terminal

! --------------------------------------------------------------
!--- Fault 4: G0/0/1 (LAN side) was stuck at half duplex / 10 Mbps, mismatching S1 and causing slow response times.
! --------------------------------------------------------------

!--- Restore the LAN interface to 100 Mbps full duplex to match S1 F0/5.
interface g0/0/1
 speed 100
 duplex full
 no shutdown
 exit

! --------------------------------------------------------------
!--- Fault 5: no gateway of last resort, so R1 had no route toward the internet (209.165.200.226).
! --------------------------------------------------------------

!--- Add the default route pointing to the ISP router (G0/0/0 next hop).
ip route 0.0.0.0 0.0.0.0 10.1.1.2

end

! --------------------------------------------------------------
!--- Save the configuration to NVRAM. (Press Enter when prompted.)
! --------------------------------------------------------------
copy running-config startup-config


! ==============================================================
!--- Verification:
!---   show interfaces g0/0/1  -> 100 Mb/s, Full-duplex
!---   show ip route           -> Gateway of last resort is 10.1.1.2
!---   ping 209.165.200.226    -> R1 reaches the external server
! ==============================================================

Router ISP:

hostname ISP
no ip domain lookup
interface GigabitEthernet0/0/0
ip address 10.1.1.2 255.255.255.252
no shut
interface Lo0
ip address 209.165.200.226 255.255.255.255
ip route 0.0.0.0 0.0.0.0 10.1.1.1
end

Issues Found and Solutions

Host fix (Desktop → IP Configuration)

• PC-A — set Default Gateway to 192.168.1.1 (keep IP 192.168.1.10, mask 255.255.255.0).

Accessing the network devices

Log in to S1 and R1 with username admin01 and password cisco12345 (SSH is enabled on both devices).

Fix on S1

enable
configure terminal
interface f0/5
 speed 100
 duplex full
 exit
ip default-gateway 192.168.1.1
end
copy running-config startup-config

Fix on R1

enable
configure terminal
interface g0/0/1
 speed 100
 duplex full
 no shutdown
 exit
ip route 0.0.0.0 0.0.0.0 10.1.1.2
end
copy running-config startup-config

Verification

• S1 / R1 — show interfaces should report 100 Mb/s, Full-duplex on F0/5 and G0/0/1.
• R1 — show ip route should show Gateway of last resort is 10.1.1.2.
• PC-A, S1, R1 — all should now ping 209.165.200.226 successfully, with no significant variation in response times.

Download Packet Tracer (.pka) file:

17.7.7 Packet Tracer - Troubleshoot Connectivity Issues - Physical Mode .pka

1 file(s) 328.34 KB

Download