Same for:
- 12.3.1 Packet Tracer - Use ICMP to Test and Correct Network Connectivity
- 29.3.1 Packet Tracer - Use ICMP to Test and Correct Network Connectivity
13.3.1 Packet Tracer - Use ICMP to Test and Correct Network Connectivity Instructor Version
Topology
13.3.1 Packet Tracer - Use ICMP to Test and Correct Network Connectivity
Addressing Table
| Device | Interface | Address | Mask/Prefix | Default Gateway |
|---|---|---|---|---|
| RTR-1 | G0/0/0 | 192.168.1.1 | 255.255.255.0 | N/A |
| RTR-1 | G0/0/0 | 2001:db8:4::1 | /64 | N/A |
| RTR-1 | S0/1/0 | 10.10.2.2 | 255.255.255.252 | N/A |
| RTR-1 | S0/1/0 | 2001:db8:2::2 | /126 | N/A |
| RTR-1 | S0/1/1 | 10.10.3.1 | 255.255.255.252 | N/A |
| RTR-1 | S0/1/1 | 2001:db8:3::1 | /126 | N/A |
| RTR-2 | G0/0/0 | 10.10.1.1 | 255.255.255.0 | N/A |
| RTR-2 | G0/0/1 | 2001:db8:1::1 | /64 | N/A |
| RTR-2 | S0/1/0 | 10.10.2.1 | 255.255.255.252 | N/A |
| RTR-2 | S0/1/0 | 2001:db8:2::1 | /126 | N/A |
| RTR-3 | G0/0/0 | 10.10.5.1 | 255.255.255.0 | N/A |
| RTR-3 | G0/0/1 | 2001:db8:5::1 | /64 | N/A |
| RTR-3 | S0/1/0 | 10.10.3.2 | 255.255.255.252 | N/A |
| RTR-3 | S0/1/0 | 2001:db8:3::2 | /126 | N/A |
| PC-1 | NIC | 10.10.1.10 | 255.255.255.0 | 10.10.1.1 |
| Laptop A | NIC | 10.10.1.20 | 255.255.255.0 | 10.10.1.1 |
| PC-2 | NIC | 2001:db8:1::10 | /64 | fe80::1 |
| PC-3 | NIC | 2001:db8:1::20 | /64 | fe80::1 |
| PC-4 | NIC | 10.10.5.10 | 255.255.255.0 | 10.10.5.1 |
| Server 1 | NIC | 10.10.5.20 | 255.255.255.0 | 10.10.5.1 |
| Laptop B | NIC | 2001:db8:5::10 | /64 | fe80::1 |
| Laptop C | NIC | 2001:db8:5::20 | /64 | fe80::1 |
| Corporate Server | NIC | 203.0.113.100 | 255.255.255.0 | 203.0.113.1 |
| Corporate Server | NIC | 2001:db8:acad::100 | /64 | fe80::1 |
Objectives
In this lab you will use ICMP to test network connectivity and locate network problems. You will also correct simple configuration issues and restore connectivity to the network.
- Use ICMP to locate connectivity issues.
- Configure network devices to correct connectivity issues.
Background
Customers have been complaining that they can’t reach some network resources. You have been asked to test connectivity in the network. You use ICMP to find out which resources are unreachable and the locations from which they can’t be reached. Then, you use trace to locate the point at which network connectivity is broken. Finally, you fix the errors that you find to restore connectivity to the network.
Instructor Note: The focus of this activity is the use of ICMP to identify and locate network connectivity problems. Please encourage students to use ICMP rather than other methods, such as opening configurations, to systematically locate connectivity issues.
Instructions
All hosts should have connectivity to all other hosts and the Corporate Server.
- Wait until all link lights are green.
- Select a host and use ICMP
pingto determine which hosts are reachable from that host. - If a host is found to be unreachable, use ICMP
traceto locate the general location of the network errors. - Locate the specific errors and correct them.
Connectivity Issues:
1. Server 1 is set to receive its IP address over DHCP. It should be statically configured with the correct IP address, subnet mask, and default gateway.
2. Router RTR-3 interface G0/0/1 has been configured with the wrong IPv6 address. The address should be 2001:DB8:5::1/64 as shown in the addressing table.
RTR-3# show ipv6 interface brief
RTR-3(config)# interface gigabitethernet 0/0/1 RTR-3(config-if)# no ipv6 address RTR-3(config-if)# ipv6 address 2001:db8:5::1/64 RTR-3(config-if)# ipv6 address fe80::1 link-local RTR-3(config-if)# shutdown RTR-3(config-if)# no shutdown
Note: The G0/0/1 interface may need to be shut down and brought back up in order for the new route to take effect. The old route may still show up in the routing table as well.
3. PC-4 is configured with the wrong default gateway address. It should be 10.10.5.1 as shown in the addressing table.
Device Configs - Final
ROUTER RTR-3
! ============================================================== !--- 13.3.1 Packet Tracer - Use ICMP to Test and Correct Network Connectivity !--- ANSWER SCRIPT FOR ROUTER RTR-3 !--- Usage: copy this whole file and paste it into the RTR-3 terminal (start at the RTR-3> prompt). This is a troubleshooting activity: the script contains only the fix for RTR-3. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless. ! ============================================================== enable configure terminal ! -------------------------------------------------------------- !--- Connectivity issue 2: RTR-3 G0/0/1 has the wrong IPv6 address. ! -------------------------------------------------------------- !--- Remove every IPv6 address on G0/0/1 (a new address is added next to a wrong one, it does not replace it), then add the correct GUA and the link-local fe80::1 that Laptop B and Laptop C use as their gateway. Shut and re-enable the interface so the old route is removed. interface gigabitethernet 0/0/1 shutdown no ipv6 address ipv6 address 2001:db8:5::1/64 ipv6 address fe80::1 link-local no shutdown exit end ! -------------------------------------------------------------- !--- Save the configuration to NVRAM. (Press Enter when prompted for the destination filename.) ! -------------------------------------------------------------- copy running-config startup-config ! ============================================================== !--- Verification: !--- show ipv6 interface brief -> G0/0/1 up/up with FE80::1 and 2001:DB8:5::1 only !--- show ipv6 route -> C 2001:DB8:5::/64 via GigabitEthernet0/0/1; no route for the old prefix !--- ping 2001:db8:5::10 -> reaches Laptop B !--- Note: issues 1 and 3 are fixed on the hosts (Desktop > IP Configuration): Server 1 static 10.10.5.20/24, gateway 10.10.5.1; PC-4 gateway 10.10.5.1. ! ==============================================================
SERVER 1
PC-4
Download Packet Tracer (.pka) file:
