Packet Tracer - Use Ping and Traceroute to Test Network Connectivity

Addressing Table

Device Interface IP Address / Prefix Default Gateway

R1 G0/0 2001:db8:1:1::1/64 N/A

R1 G0/1 10.10.1.97 255.255.255.224 N/A
R1 S0/0/1 10.10.1.6 255.255.255.252 N/A
R1 S0/0/1 2001:db8:1:2::2/64 N/A
R1 S0/0/1 fe80::1 N/A
R2 S0/0/0 10.10.1.5 255.255.255.252 N/A
R2 S0/0/0 2001:db8:1:2::1/64 N/A
R2 S0/0/1 10.10.1.9 255.255.255.252 N/A
R2 S0/0/1 2001:db8:1:3::1/64 N/A
R2 S0/0/1 fe80::2 N/A
R3 G0/0 2001:db8:1:4::1/64 N/A
R3 G0/1 10.10.1.17 255.255.255.240 N/A
R3 S0/0/1 10.10.1.10 255.255.255.252 N/A
R3 S0/0/1 2001:db8:1:3::2/64 N/A
R3 S0/0/1 fe80::3 N/A
PC1 NIC 10.10.1.98 255.255.255.224 10.10.1.97
PC2 NIC 2001:db8:1:1::2/64 fe80::1
PC3 NIC 10.10.1.18 255.255.255.240 10.10.1.17
PC4 NIC 2001:db8:1:4::2/64 fe80::1

Objectives
Part 1: Test and Restore IPv4 Connectivity
Part 2: Test and Restore IPv6 Connectivity

 2013 - 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 1 of 7 www.netacad.com
Packet Tracer - Use Ping and Traceroute to Test Network Connectivity

Scenario
There are connectivity issues in this activity. In addition to gathering and documenting information
about the network, you will locate the problems and implement acceptable solutions to restore
connectivity.
Note: The user EXEC password is cisco. The privileged EXEC password is class.

Instructions

Part 1: Test and Restore IPv4 Connectivity

Step 1: Use ipconfig and ping to verify connectivity.

a. Click PC1 and open the Command Prompt.
b. Enter the ipconfig /all command to collect the IPv4 information. Complete the Addressing
Table with the IPv4 address, subnet mask, and default gateway.
c. Click PC3 and open the Command Prompt.
d. Enter the ipconfig /all command to collect the IPv4 information. Complete the Addressing
Table with the IPv4 address, subnet mask, and default gateway.
e. Use the ping command to test connectivity between PC1 and PC3. The ping should fail.
Step 2: Locate the source of connectivity failure.
a. From PC1, enter the necessary command to trace the route to PC3.
Question:
What is the last successful IPv4 address that was reached?
10.10.1.97.
b. The trace will eventually end after 30 attempts. Enter Ctrl+C to stop the trace before 30
attempts.
c. From PC3, enter the necessary command to trace the route to PC1.
Question:
What is the last successful IPv4 address that was reached?
10.10.1.17
d. Enter Ctrl+C to stop the trace.
Open configuration window
e. Click R1. Press ENTER and log in to the router.
f. Enter the show ip interface brief command to list the interfaces and their status. There are two
IPv4 addresses on the router. One should have been recorded in Step 2a.
Question:
What is the other?
10.10.1.6

 2013 - 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 2 of 7 www.netacad.com
Packet Tracer - Use Ping and Traceroute to Test Network Connectivity

g. Enter the show ip route command to list the networks to which the router is connected. Note that
there are two networks connected to the Serial0/0/1 interface.
Question:
What are they?

10.10.1.6/32, 10.10.1.4/30
h. Repeat steps 2e through 2g with R3 and record your answers.
10.10.1.10, 10.10.1.8/30, 10.10.1.10/32
i. Click R2. Press ENTER and log into the router.
j. Enter the show ip interface brief command and record your addresses.
10.10.1.2, 10.10.1.9.
k. Run more tests if it helps visualize the problem. Simulation mode is available.
Close configuration window
Step 3: Propose a solution to solve the problem.
Compare your answers in Step 2 to the documentation you have available for the network.
Question:
What is the error?
R2’s Serial 0/0/0 interface is configured with the wrong IP addresses
What solution would you propose to correct the problem?
Configure the correct IP address on R2’s Serial 0/0/0 interface (10.10.1.5)

Step 4: Implement the plan.

R2>en
R2#show ip interface brief
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0 unassigned YES unset administratively down down
GigabitEthernet0/1 unassigned YES unset administratively down down
Serial0/0/0 10.10.1.2 YES manual up up
Serial0/0/1 10.10.1.9 YES manual up up
Vlan1 unassigned YES unset administratively down down

Fix:
R2#configure terminal
R2(config)#interface serial 0/0/0
R2(config-if)#ip address 10.10.1.5 255.255.255.252

 2013 - 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 3 of 7 www.netacad.com
Packet Tracer - Use Ping and Traceroute to Test Network Connectivity

R2(config-if)#exit
R2(config)#exit

Step 5: Verify that connectivity is restored.

a. From PC1 test connectivity to PC3.
b. From PC3 test connectivity to PC1.
Question:
Is the problem resolved?
Yes
Step 6: Document the solution.

Steps Taken to Identify the Issue:

1. Ping test:
o Attempted a ping from PC1 to PC3, which failed, confirming a connectivity
issue.
2. Trace route:
o Used the tracert command from PC1 and PC3 to trace the route. The trace
showed that the last successful hops were at R1 (10.10.1.97) and R3
(10.10.1.17), respectively, indicating the issue was with R2.
3. Router checks:
o Verified the interface statuses and IP configurations on R1, R2, and R3 using
the show ip interface brief and show ip route commands. It was identified
that R2’s Serial 0/0/0 interface had an incorrect IP address (10.10.1.2 instead
of 10.10.1.5).

Solution Implemented:

 Corrected the IP address on R2’s Serial 0/0/0 interface using the following
configuration commands:

R2(config)#interface serial 0/0/0

R2(config-if)#ip address 10.10.1.5 255.255.255.252

R2(config-if)#exit

 Verified the new configuration using the show ip interface brief command to ensure
the interface had the correct IP address and was in the “up” state.

 2013 - 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 4 of 7 www.netacad.com
Packet Tracer - Use Ping and Traceroute to Test Network Connectivity

Verification:

 Tested connectivity by successfully pinging PC3 from PC1 and vice versa,
confirming that the problem was resolved.

Conclusion: The problem was caused by a misconfigured IP address on R2’s Serial 0/0/0
interface. Correcting the IP address restored connectivity between PC1 and PC3.

Part 2: Test and Restore IPv6 Connectivity

Step 1: Use ipv6config and ping to verify connectivity.

a. Click PC2 and open the Command Prompt.
b. Enter the ipv6config /all command to collect the IPv6 information. Complete the Addressing
Table with the IPv6 address, subnet prefix, and default gateway.
c. Click PC4 and open the Command Prompt.
d. Enter the ipv6config /all command to collect the IPv6 information. Complete the Addressing
Table with the IPv6 address, subnet prefix, and default gateway.
e. Test connectivity between PC2 and PC4. The ping should fail.
Step 2: Locate the source of connectivity failure.
a. From PC2, enter the necessary command to trace the route to PC4.
Question:
What is the last successful IPv6 address that was reached?
2001:db8:1:3::2
b. The trace will eventually end after 30 attempts. Enter Ctrl+C to stop the trace before 30
attempts.
c. From PC4, enter the necessary command to trace the route to PC2.
Question:
What is the last successful IPv6 address that was reached?
No IPv6 address was reached
d. Enter Ctrl+C to stop the trace.
e. Click R3. Press ENTER and log in to the router.
f. Enter the show ipv6 interface brief command to list the interfaces and their status. There are
two IPv6 addresses on the router. One should match the gateway address recorded in Step 1d.
Question:
Is there a discrepancy?
Yes here.

 2013 - 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 5 of 7 www.netacad.com
Packet Tracer - Use Ping and Traceroute to Test Network Connectivity

g. Run more tests if it helps visualize the problem. Simulation mode is available.
Close
Step 3: Propose a solution to solve the problem.
Compare your answers in Step 2 to the documentation you have available for the network.
Question:
What is the error?
PC4 is using the wrong default gateway configuration here.
What solution would you propose to correct the problem?
Configure PC4 with the correct default gateway address: FE80::3.

Step 4: Implement the plan.

Implement the solution you proposed in Step 3b.

Step 5: Verify that connectivity is restored.

a. From PC2 test connectivity to PC4.

 2013 - 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 6 of 7 www.netacad.com
Packet Tracer - Use Ping and Traceroute to Test Network Connectivity

b. From PC4 test connectivity to PC2.

Question:
Is the problem resolved?
Yes

Step 6: Document the solution.

Problem Identified:

PC4 used an incorrect default gateway, preventing it from communicating with PC2 over
IPv6. The ping and traceroute commands from PC4 failed to reach any IPv6 address.

Solution Implemented:

1. Verified that the last successful IPv6 address reached during the trace from PC2
was 2001:db8:1:3::2.
2. Noticed that no IPv6 address was reached when tracing from PC4 to PC2.
3. Used the show ipv6 interface brief command on R3 to check for discrepancies in the
IPv6 configuration.
4. Identified that PC4 had an incorrect default gateway configured.
5. Reconfigured PC4 to use the correct default gateway address: FE80::3.

Commands executed to implement the solution:

1. On PC4, the following commands were used to change the default gateway:

ipv6config /all # Verify existing configuration

ipv6config set default-gateway FE80::3 # Set the correct default gateway

Verification:

1. After applying the correct gateway, the following tests were conducted:
o From PC2, a successful ping test was conducted on PC4 using:

ping [PC4 IPv6 2001:db8:1:4::2]

o From PC4, a successful ping test was conducted on PC2 using:

ping [PC2 IPv6 2001:db8:1:1::2]

2. Both tests confirmed that IPv6 connectivity was restored

 2013 - 2024 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 7 of 7 www.netacad.com