6.4.3.4 Packet Tracer - Troubleshooting Default Gateway Issues (Answers)

6.4.3.4 Packet Tracer – Troubleshooting Default Gateway Points (Teacher Model)

6.4.3.4 Packet Tracer – Troubleshooting Default Gateway Points

Addressing Desk

Goals

Half 1: Confirm Community Documentation and Isolate Issues

Half 2: Implement, Confirm, and Doc Options

Background

For a tool to speak throughout a number of networks, it should be configured with an IP deal with, subnet masks, and a default gateway. The default gateway is used when the host desires to ship a packet to a tool on one other community. The default gateway deal with is usually the router interface deal with connected to the native community to which the host is related. On this exercise, you’ll end documenting the community. You’ll then confirm the community documentation by testing end-to-end connectivity and troubleshooting points. The troubleshooting technique you’ll use consists of the next steps:

1) Confirm the community documentation and use assessments to isolate issues.

2) Decide an applicable answer for a given drawback.

3) Implement the answer.

4) Check to confirm the issue is resolved.

5) Doc the answer.

All through your CCNA research, you’ll encounter totally different descriptions of the troubleshooting technique, in addition to other ways to check and doc points and options. That is intentional. There isn’t a set normal or template for troubleshooting. Every group develops distinctive processes and documentation requirements (even when that course of is “we don’t have one”). Nevertheless, all efficient troubleshooting methodologies usually embrace the above steps.

Word: In case you are proficient with default gateway configurations, this exercise may appear extra concerned than it needs to be. You possibly can, most certainly, rapidly uncover and resolve all of the connectivity points sooner than following these procedures. Nevertheless, as you proceed in your research, the networks and issues you encounter will change into more and more extra complicated. In such conditions, the one efficient approach to isolate and resolve points is to make use of a methodical method such because the one used on this exercise.

Half 1: Confirm Community Documentation and Isolate Issues

In Half 1 of this exercise, full the documentation and carry out connectivity assessments to find points. As well as, you’ll decide an applicable answer for implementation in Half 2.

Step 1: Confirm the community documentation and isolate any issues.

a. Earlier than you may successfully check a community, you have to have full documentation. Discover within the Addressing Desk that some data is lacking. Full the Addressing Desk by filling within the lacking default gateway data for the switches and the PCs.

b. Check connectivity to gadgets on the identical community. By isolating and correcting any native entry points, you may higher check distant connectivity with the arrogance that native connectivity is operational.

A verification plan might be so simple as a listing of connectivity assessments. Use the next assessments to confirm native connectivity and isolate any entry points. The primary difficulty is already documented, however you have to implement and confirm the answer throughout Half 2.

Testing and Verification Documentation

Word: The desk is an instance; you have to create your individual doc. You should use paper and pencil to attract a desk, or you should use a textual content editor or spreadsheet. Seek the advice of your teacher in case you want additional steering.

c. Check connectivity to distant gadgets (akin to from PC1 to PC4) and doc any issues. That is incessantly known as end-to-end connectivity. Because of this all gadgets in a community have the complete connectivity allowed by the community coverage.

Word: Distant connectivity testing might not be potential but, since you should first resolve native connectivity points. After you will have solved these points, return to this step and check connectivity between networks.

Step 2: Decide an applicable answer for the issue.

a. Utilizing your data of the best way networks function and your system configuration expertise, seek for the reason for the issue. For instance, S1 shouldn’t be the reason for the connectivity difficulty between PC1 and PC2. The hyperlink lights are inexperienced and no configuration on S1 would trigger site visitors to not cross between PC1 and PC2. So the issue should be with PC1, PC2, or each.

b. Confirm the system addressing to make sure it matches the community documentation. For instance, the IP deal with for PC1 is inaccurate as verified with the ipconfig command.

c. Recommend an answer that you just assume will resolve the issue and doc it. For instance, change the IP deal with for PC1 to match the documentation.

Word: Typically there may be multiple answer. Nevertheless, it’s a troubleshooting finest follow to implement one answer at a time. Implementing multiple answer might introduce extra points in a extra complicated state of affairs.

Half 2: Implement, Confirm, and Doc Options

In Half 2 of this exercise, you’ll implement the options you recognized in Half 1. You’ll then confirm the answer labored. It’s possible you’ll have to return to Half 1 to complete isolating all the issues.

Step 1: Implement options to connectivity issues.

Discuss with your documentation in Half 1. Select the primary difficulty and implement your recommended answer. For instance, appropriate the IP deal with on PC1.

Step 2: Confirm that the issue is now resolved.

a. Confirm your answer has solved the issue by performing the check you used to determine the issue. For instance, can PC1 now ping PC2?.

b. If the issue is resolved, point out so in your documentation. For instance, within the desk above, a easy checkmark would suffice within the “Verified” column.

Step 3: Confirm that every one points are resolved.

a. In case you nonetheless have an impressive difficulty with an answer that has not but been carried out, return to Half 2, Step 1.

b. If all of your present points are resolved, have you ever additionally resolved any distant connectivity points (akin to can PC1 ping PC4)? If the reply is not any, return to Half 1, Step 1c to check distant connectivity.

Points:

PC1 can’t ping PC2 as a result of PC1 has an IP deal with that doesn’t belong to the community PC1 is
connected to.
– Units can’t ping S2 and S2 can’t ping any system as a result of S2 is lacking an IP deal with.
– Distant gadgets can’t ping PC4 as a result of PC4 has the improper default gateway configured.
– Distant gadgets can’t ping S1 as a result of S1 is lacking a default gateway configuration.

Urged Scoring Rubric

Directions

Obtain PDF & PKA file:

[sociallocker id=”54558″]

[/sociallocker]