11.3.2.2 Packet Tracer - Testing Connectivity with Traceroute Topology
Objectives Part 1: Test n!-to-n! Connectivity with the tracert Co""an! Part 2: Co"pare to the traceroute Co""an! on a #outer
$ackgroun! This activity is designed to help you troubleshoot network connectivity issues using commands to trace the route from source to destination. You You are required to examine the output of tracert (the Windows command) and traceroute (the traceroute (the !" command) as packets traverse the network and determine the cause of a network issue. #fter the issue is corrected$ use the tracert and tracert and traceroute commands traceroute commands to verify the completion.
Part 1: 1: Test Test n!-to- n!-to-n! n! Connecti Connectivity vity with the tracert tracert Co""an! Co""an! %tep 1: %en! a ping ping &ro" one en! en! o& the the network network to to the other other en!. %lick PC1 and open the Co""an! Pro"pt. Pro"pt . &ing PC3 at PC3 at 1'.1.'.2. 1'.1.'.2. What message is displayed as a result of the ping' estination host unreachable
%tep 2: Trace Trace the route &ro" PC1 to !eter"ine where in the path path connectivity connectivity &ails. a. rom th the Co""an! Pro"pt of Pro"pt of PC1$ PC1$ enter the tracert 1'.1.'.2 command. 1'.1.'.2 command. b. When When you you rece receiv ive e the the #e(uest ti"e! out message$ press Ctrl* Ctrl *C. What was the first & address listed in the tracert output' tracert output' +,.,.,.-/ 0 -,+1 %isco and2or its affiliates. #ll rights reserved. This document is %isco &ublic.
&age 1 of 3
Packet Tracer - Testing Connectivity with Traceroute c.
!bserve the results of the tracert command. What is the last address reached with the tracert command' +,.+,,.+,,.3
%tep 3: Correct the network proble". d. %ompare the last address reached with the tracert command with the network addresses listed on the topology. The furthest device from the host +,.,.,.- 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' 4outer -
e.
%lick #outerC and then the C)* tab.
f.
What is the status of the interfaces' up
g. %ompare the & addresses on the interfaces with the network addresses on the topology. oes there appear to be anything extraordinary' "erial ,2,2, is misconfigured
h. 5ake the necessary changes to restore connectivity6 however$ do not change the subnets. What is solution' 4econfiguring serial ,2,2,
%tep +: ,eri&y that en!-to-en! connectivity is establishe!. i. 7.
rom the PC1 Co""an! Pro"pt$ enter the tracert 1'.1.'.2 command. !bserve the output from the tracert command. Was the command successful'yes
Part 2: Co"pare to the traceroute Co""an! on a #outer k.
%lick #outer and then the C)* tab.
l.
8nter the traceroute 1'.1.'.2 command. id the command complete successfully' yes
m. %ompare the output from the router traceroute command with the &% tracert command. What is noticeably different about the list of addresses returned' 4outer does not ping +,.,.,.-/
0 -,+1 %isco and2or its affiliates. #ll rights reserved. This document is %isco &ublic.
&age 2 of 3
Packet Tracer - Testing Connectivity with Traceroute
%uggeste! %coring #ubric
ctivity %ection &art +9 Test 8nd:to:8nd %onnectivity with the tracert %ommand
uestion )ocation
Possible Points
"tep +
+,
"tep -b
+,
"tep -c
+,
"tep 1a
+,
"tep 1c
+,
"tep 1d
+,
"tep 1e
+,
"tep /b
+,
Part 1 Total &art -9 %ompare to the traceroute %ommand on a 4outer
/'
a
+,
b
+,
Part 2 Total
2'
Total %core
1''
0 -,+1 %isco and2or its affiliates. #ll rights reserved. This document is %isco &ublic.
arne! Points
&age 3 of 3
