Hi today we are going to perform the lab for CCNA R&S 7.3.2.6 Packet Tracer – Pinging and Tracing to Test the Path. If you feel difficult to understand you can see the video down below. You may also see the 7.3.2.5 Packet Tracer – Verifying IPv4 and IPv6Addressing

Addressing Table



Objectives

Part 1: Test and Restore IPv4 Connectivity

Part 2: Test and Restore IPv6 Connectivity

Scenario

There are connectivity issues in this activity lab for CCNA R&S 7.3.2.6 Packet Tracer – Pinging and Tracing to Test the Path. 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.



Part 1: Test and Restore IPv4 Connectivity

Step 1: Use ipconfig and ping to verify connectivity.


We will perform the following tasks for securing the 100% marks in CCNA R&S 7.3.2.6 Packet Tracer – Pinging and Tracing to Test the Path.

  1. Click PC1 and click the Desktop tab > Command Prompt.
  2. Enter the ipconfig /all command to collect the IPv4 information. Complete the Addressing Table with the IPv4 address, subnet mask, and default gateway.
  3. Click PC3 and click the Desktop tab > Command Prompt.
  4. Enter the ipconfig /all command to collect the IPv4 information. Complete the Addressing Table with the IPv4 address, subnet mask, and default gateway.
  5. Test connectivity between PC1 and PC3. The ping should fail.


Step 2: Locate the source of connectivity failure.

We will locate the source of connectivity failure in CCNA R&S 7.3.2.6 Packet Tracer – Pinging and Tracing to Test the Path by performing the following tasks.

  1. From PC1, enter the necessary command to trace the route to PC3. What is the last successful IPv4 address that was reached? 10.10.1.97
  2. The trace will eventually end after 30 attempts. Enter Ctrl+C to stop the trace before 30 attempts.
  3. From PC3, enter the necessary command to trace the route to PC1. What is the last successful IPv4 address that was reached?  10.10.1.17
  4. Enter Ctrl+C to stop the trace.
  5. Click R1 and then the CLI tab. Press ENTER and log in to the router.
  6. 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. What is the other? 10.10.1.6
  7. 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. What are they?  10.10.1.6/32, 10.10.1.4/30
  8. Repeat step 2e to 2g with R3 and the answers here.  10.10.1.10; 10.10.1.8/30, 10.10.1.10/32

Notice how the serial interface for R3 changes.

  1. Run more tests if it helps visualize the problem. Simulation mode is available.


Step 3: Propose a solution to solve the problem.
  1. Compare your answers in Step 2 to the documentation you have available for the network. What is the error?

R2’s Serial 0/0/0 interface is configured with the wrong IP address

  1. 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.




Implement the solution you proposed in Step 3b.

Serial0/0/0 10.10.1.5 YES manual up up
Serial0/0/1 10.10.1.9 YES manual up up
Vlan1 unassigned YES unset administratively down down



Step 5: Verify that connectivity is restored.
  1. From PC1 test connectivity to PC3.
  2. From PC3 test connectivity to PC1. Is the problem resolved? Yes
Step 6: Document the solution.


Part 2: Test and Restore IPv6 Connectivity



Step 1: Use ipv6config and ping to verify connectivity.

We will use the ipv6config /all command for knowing the ipv6 addresses of the PC’s and to verify the connectivity between them in CCNA R&S 7.3.2.6 Packet Tracer – Pinging and Tracing to Test the Path.

  1. Click PC2 and click the Desktop tab > Command Prompt.
  2. Enter the ipv6config /all command to collect the IPv6 information. Complete the Addressing Table with the IPv6 address, subnet prefix, and default gateway.
  3. Click PC4 and click the Desktop tab > Command Prompt.
  4. Enter the ipv6config /all command to collect the IPv6 information. Complete the Addressing Table with the IPv6 address, subnet prefix, and default gateway.
  5. Test connectivity between PC2 and PC4. The ping should fail.


Step 2: Locate the source of connectivity failure.

Now we will locate the source of connectivity failure in CCNA R&S 7.3.2.6 Packet Tracer – Pinging and Tracing to Test the Path.

  1. From PC2, enter the necessary command to trace the route to PC4. What is the last successful IPv6 address that was reached? The trace will eventually end after 30 attempts. Enter Ctrl+C to stop the trace before 30 attempts. 2001:DB8:1:3::2
  2. From PC4, enter the necessary command to trace the route to PC2. What is the last successful IPv6 address that was reached? Enter Ctrl+C to stop the trace. No IPv6 address was reached
  3. Click R3 and then the CLI tab. Press ENTER and log in to the router.
  4. 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. Is there a discrepancy? Yes
  5. Run more tests if it helps visualize the problem. Simulation mode is available.


Step 3: Propose a solution to solve the problem.
  1. Compare your answers in Step 2 to the documentation you have available for the network. What is the error?

PC4 is using the wrong default gateway configuration

  1. 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. we have implemented  the solution we have proposed in the CCNA R&S 7.3.2.5 Packet Tracer – Pinging and Tracing to Test the Path which is shown below.



Step 5: Verify that connectivity is restored.

We will verify that the connectivity is restored in CCNA R&S 7.3.2.6 Packet Tracer – Pinging and Tracing to Test the Path.

  1. From PC2 test connectivity to PC4.
  2. From PC4 test connectivity to PC2. Is the problem resolved? Yes

That’s all for today. Stay tuned for more updates of CCNA R&S . which will help you in passing the CCNA certifications. Thanks

 

 

Rate this post
Hamza Arif
Follow us

Hamza Arif

Hey, i hamza arif student of telecommunication from BZU, i am good in Networking, Telecommunication and Web Development working on different projects and try my best to teach them to all of you.
Hamza Arif
Follow us

Leave a comment

Your email address will not be published. Required fields are marked *