11.3.2.2 Packet Tracer - Test Connectivity with Traceroute Instructions

Packet Tracer - Testing Connectivity with Traceroute

Please click here to download topology 11.3.2.2 Packet Tracer - Test Connectivity with Traceroute Instructions

Topology

11.3.2.2 Packet Tracer - Test Connectivity with Traceroute Instructions

Objectives

Part 1: Test End-to-End Connectivity with the tracert Command

Part 2: Compare to the traceroute Command on a Router

Background

This activity is designed to help you troubleshoot network connectivity issues using commands to trace the route from source to destination. You are required to examine the output of tracert (the Windows command) and traceroute (the IOS command) as packets traverse the network and determine the cause of a network issue. After the issue is corrected, use the tracert and traceroute commands to verify the completion.

Part 1:     Test End-to-End Connectivity with the tracert Command

Step 1:     Send a ping from one end of the network to the other end.

Click PC1 and open the Command Prompt. Ping PC3 at 10.1.0.2. What message is displayed as a result of the ping?

Step 2:     Trace the route from PC1 to determine where in the path connectivity fails.

a.     From the Command Prompt of PC1, enter the tracert 10.1.0.2 command.

b.    When you receive the Request timed out message, press Ctrl+C. What was the first IP address listed in the tracert output?

c.     Observe the results of the tracert command. What is the last address reached with the tracert command? 

Step 3:     Correct the network problem.

a.     Compare the last address reached with the tracert command with the network addresses listed on the topology. The furthest device from the host 10.0.0.2 with an address in the network range found is the point of failure. What devices have addresses configured for the network where the failure occurred?

b.    Click RouterC and then the CLI tab.

c.     What is the status of the interfaces?

d.    Compare the IP addresses on the interfaces with the network addresses on the topology. Does there appear to be anything extraordinary?

e.     Make the necessary changes to restore connectivity; however, do not change the subnets. What is solution?

Step 4:     Verify that end-to-end connectivity is established.

a.     From the PC1 Command Prompt, enter the tracert 10.1.0.2 command.

b.    Observe the output from the tracert command. Was the command successful?

Part 2:     Compare to the traceroute Command on a Router

a.     Click RouterA and then the CLI tab.

b.    Enter the traceroute 10.1.0.2 command. Did the command complete successfully?

c.     Compare the output from the router traceroute command with the PC tracert command. What is noticeably different about the list of addresses returned?

Suggested Scoring Rubric

Activity Section	Question Location	Possible Points	Earned Points
Part 1: Test End-to-End Connectivity with the tracert Command	Step 1	10
	Step 2b	10
	Step 2c	10
	Step 3a	10
	Step 3c	10
	Step 3d	10
	Step 3e	10
	Step 4b	10
Part 1 Total		80
Part 2: Compare to the traceroute Command on a Router	a	10
	b	10
Part 2 Total		20
Total Score		100