[ad_1]
7.3.2.6 Packet Tracer – Pinging and Tracing to Check the Path (Teacher Model – Non-compulsory Packet Tracer)
7.3.2.6 Packet Tracer – Pinging and Tracing to Check the Path
Addressing Desk
| System | Interface | IPv4 Deal with | Subnet Masks | Default Gateway |
|---|---|---|---|---|
| IPv6 Deal with/Prefix | ||||
| R1 | G0/0 | 2001:DB8:1:1::1/64 | N/A | |
| G0/1 | 10.10.1.97 | 255.255.255.224 | N/A | |
| S0/0/1 | 10.10.1.6 | 255.255.255.252 | N/A | |
| 2001:DB8:1:2::2/64 | N/A | |||
| Hyperlink-local | FE80::1 | N/A | ||
| R2 | S0/0/0 | 10.10.1.5 | 255.255.255.252 | N/A |
| 2001:DB8:1:2::1/64 | N/A | |||
| S0/0/1 | 10.10.1.9 | 255.255.255.252 | N/A | |
| 2001:DB8:1:3::1/64 | N/A | |||
| Hyperlink-local | FE80::2 | N/A | ||
| R3 | G0/0 | 2001:DB8:1:4::1/64 | N/A | |
| G0/1 | 10.10.1.17 | 255.255.255.240 | N/A | |
| S0/0/1 | 10.10.1.10 | 255.255.255.252 | N/A | |
| 2001:DB8:1:3::2/64 | N/A | |||
| Hyperlink-local | 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 | |
Targets
Half 1: Check and Restore IPv4 Connectivity
Half 2: Check and Restore IPv6 Connectivity
State of affairs
There are connectivity points on this exercise. Along with gathering and documenting details about the community, you’ll find the issues and implement acceptable options to revive connectivity.
Word: The consumer EXEC password is cisco. The privileged EXEC password is class.
Half 1: Check and Restore IPv4 Connectivity
Step 1: Use ipconfig and ping to confirm connectivity.
a. Click on PC1 and click on the Desktop tab > Command Immediate.
b. Enter the ipconfig /all command to gather the IPv4 data. Full the Addressing Desk with the IPv4 handle, subnet masks, and default gateway.
c. Click on PC3 and click on the Desktop tab > Command Immediate.
d. Enter the ipconfig /all command to gather the IPv4 data. Full the Addressing Desk with the IPv4 handle, subnet masks, and default gateway.
e. Check connectivity between PC1 and PC3. The ping ought to fail.
Step 2: Find the supply of connectivity failure.
a. From PC1, enter the mandatory command to hint the path to PC3. What’s the final profitable IPv4 handle that was reached? 10.10.1.97
b. The hint will finally finish after 30 makes an attempt. Enter Ctrl+C to cease the hint earlier than 30 makes an attempt.
c. From PC3, enter the mandatory command to hint the path to PC1. What’s the final profitable IPv4 handle that was reached? 10.10.1.17
d. Enter Ctrl+C to cease the hint.
e. Click on R1 after which the CLI tab. Press ENTER and log in to the router.
f. Enter the present ip interface transient command to record the interfaces and their standing. There are two IPv4 addresses on the router. One ought to have been recorded in Step 2a. What’s the different? 10.10.1.6
g. Enter the present ip route command to record the networks to which the router is related. Word that there are two networks related to the Serial0/0/1 interface. What are they? 10.10.1.6/32, 10.10.1.4/30
R1#present ip route Codes: L - native, C - related, S - static, R - RIP, M - cellular, B - BGP D - EIGRP, EX - EIGRP exterior, O - OSPF, IA - OSPF inter space N1 - OSPF NSSA exterior kind 1, N2 - OSPF NSSA exterior kind 2 E1 - OSPF exterior kind 1, E2 - OSPF exterior kind 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter space * - candidate default, U - per-user static route, o - ODR P - periodic downloaded static route Gateway of final resort isn't set 10.0.0.0/8 is variably subnetted, 4 subnets, 3 masks C 10.10.1.4/30 is immediately related, Serial0/0/1 L 10.10.1.6/32 is immediately related, Serial0/0/1 C 10.10.1.96/27 is immediately related, GigabitEthernet0/1 L 10.10.1.97/32 is immediately related, GigabitEthernet0/1
h. Repeat step 2e to 2g with R3 and the solutions right here. 10.10.1.10; 10.10.1.8/30, 10.10.1.10/32
Discover how the serial interface for R3 adjustments.
i. Run extra exams if it helps visualize the issue. Simulation mode is out there.
Step 3: Suggest an answer to resolve the issue.
a. Evaluate your solutions in Step 2 to the documentation you will have obtainable for the community. What’s the error?
R2’s Serial 0/0/0 interface is configured with the incorrect IP handle
b. What answer would you plan to right the issue?
Configure the proper IP handle on R2’s Serial 0/0/0 interface (10.10.1.5)
Step 4: Implement the plan.
Implement the answer you proposed in Step 3b.
R2>en R2#present ip interface transient Interface IP-Deal with OK? Methodology Standing 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 handbook up up Serial0/0/1 10.10.1.9 YES handbook up up Vlan1 unassigned YES unset administratively down down R2#configure terminal R2(config)#interface serial 0/0/0 R2(config-if)#ip handle 10.10.1.5 255.255.255.252 R2(config-if)#exit R2(config)#exit R2#present ip interface transient Interface IP-Deal with OK? Methodology Standing Protocol GigabitEthernet0/0 unassigned YES unset administratively down down GigabitEthernet0/1 unassigned YES unset administratively down down Serial0/0/0 10.10.1.5 YES handbook up up Serial0/0/1 10.10.1.9 YES handbook up up Vlan1 unassigned YES unset administratively down down
Step 5: Confirm that connectivity is restored.
a. From PC1 take a look at connectivity to PC3.
b. From PC3 take a look at connectivity to PC1. Is the issue resolved? Sure
Step 6: Doc the answer.
Half 2: Check and Restore IPv6 Connectivity
Step 1: Use ipv6config and ping to confirm connectivity.
a. Click on PC2 and click on the Desktop tab > Command Immediate.
b. Enter the ipv6config /all command to gather the IPv6 data. Full the Addressing Desk with the IPv6 handle, subnet prefix, and default gateway.
c. Click on PC4 and click on the Desktop tab > Command Immediate.
d. Enter the ipv6config /all command to gather the IPv6 data. Full the Addressing Desk with the IPv6 handle, subnet prefix, and default gateway.
e. Check connectivity between PC2 and PC4. The ping ought to fail.
Step 2: Find the supply of connectivity failure.
a. From PC2, enter the mandatory command to hint the path to PC4. What’s the final profitable IPv6 handle that was reached? The hint will finally finish after 30 makes an attempt. Enter Ctrl+C to cease the hint earlier than 30 makes an attempt. 2001:DB8:1:3::2
b. From PC4, enter the mandatory command to hint the path to PC2. What’s the final profitable IPv6 handle that was reached? Enter Ctrl+C to cease the hint. No IPv6 handle was reached
c. Click on R3 after which the CLI tab. Press ENTER and log in to the router.
d. Enter the present ipv6 interface transient command to record the interfaces and their standing. There are two IPv6 addresses on the router. One ought to match the gateway handle recorded in Step 1d. Is there a discrepancy? Sure
e. Run extra exams if it helps visualize the issue. Simulation mode is out there.
Step 3: Suggest an answer to resolve the issue.
a. Evaluate your solutions in Step 2 to the documentation you will have obtainable for the community. What’s the error?
PC4 is utilizing the incorrect default gateway configuration
b. What answer would you plan to right the issue?
Configure PC4 with the proper default gateway handle: FE80::3.
Step 4: Implement the plan.
Implement the answer you proposed in Step 3b.
Step 5: Confirm that connectivity is restored.
a. From PC2 take a look at connectivity to PC4.
b. From PC4 take a look at connectivity to PC2. Is the issue resolved? Sure
Step 6: Doc the answer.
Instructed Scoring Rubric
Obtain PDF & PKA file:
[sociallocker id=”54558″]
[/sociallocker]
[ad_2]