Scribd
Upload
450 views3 pages

17.7.7 Lab - Troubleshoot Connectivity Issues

17.7.7 Lab - Troubleshoot Connectivity Issues Answer

Uploaded by

Joven Noblefranca
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
450 views3 pages

17.7.7 Lab - Troubleshoot Connectivity Issues

17.7.7 Lab - Troubleshoot Connectivity Issues Answer

Uploaded by

Joven Noblefranca
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

NAME: Joven M.

Noblefranca
SECTION: BSIT - 2105

17.7.7 Lab - Troubleshoot Connectivity Issues

Topology

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 lab, the company that you work for is experiencing problems with their Local Area
Network (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 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.

Note: The routers used with CCNA hands-on labs are Cisco 4221 with Cisco IOS XE
Release 16.9.4 (universalk9 image). The switches used in the labs are Cisco Catalyst
2960s with Cisco IOS Release 15.2(2) (lanbasek9 image). Other routers, switches, and
Cisco IOS versions can be used. Depending on the model and Cisco IOS version, the
commands available and the output produced might vary from what is shown in the
labs. Refer to the Router Interface Summary Table at the end of the lab for the correct
interface identifiers.

Part 1: Identify the Problem

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 set to 192.168.1.0
3. R1 G0/0/1 speed set to 100 and auto negotiation is disabled.
4. The Gateway of last resort is not set on R1.
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 lab had you troubleshoot all devices before making any changes. Is there another
way to apply the troubleshooting methodology?

- Another way the troubleshooting methodology could be applied would be to


complete all 6 steps on a device before moving on to another device. e.g. 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 exist, you
would then move on to R1. This process would continue until full network
functionality was achieved.

You might also like