13.3.2 Lab – Use Ping and Traceroute to Test Network Connectivity Answers
Objectives
Part 1: Network Design and Configuration
Part 2: Use the Ping command for basic network testing
Part 3: Using Tracert and Traceroute for Fundamental Network Testing
Part 4: Diagnose the Topology
Context / Scenario
Ping and traceroute are vital tools for evaluating TCP/IP network connections. Ping is a network management tool used to test the connectivity of an IP network device. This application also monitors the round-trip time for messages delivered from the sending host to the receiving machine. Ping is supported by Windows, Unix-like operating systems (OS), and the Cisco Internetwork Operating System (IOS).
The traceroute programme is a network diagnostic tool that displays the path or route of IP packets and measures their transit delays. The tracert programme is accessible on Windows, while the traceroute utility is available on Unix-like operating systems and Cisco IOS.
In this lab, the ping and traceroute commands are reviewed, and command parameters to alter command behaviour are investigated. In this lab, Cisco devices and PCs are utilised for command exploration. In this lab, the appropriate Cisco device settings are supplied.
Note: Cisco 4221 routers running Cisco IOS XE Release 16.9.4 are used in CCNA hands-on labs (universalk9 image). The lab switches are Cisco Catalyst 2960s running Cisco IOS Release 15.2(2). (lanbasek9 image). Other routers, switches, and versions of Cisco IOS may be used. Depending on the model and Cisco IOS version, the available commands and output may differ from what is shown in the labs. For the right interface IDs, see the Router Interface Summary Table at the conclusion of the lab.
Note: Ensure that any startup settings have been removed from the routers and switches. If you are unclear, contact your Answers.
Refer to the Answers Lab Manual for instructions on how to initialise and reload devices.
The default bias template used by the Switch Database Manager (SDM) lacks IPv6 address support. Verify that SDM is using either the dual-ipv4-and-ipv6 or lanbase-routing template. Even if the configuration isn't saved, the new template will be utilised following a reboot.
S1# prefer sdm display
The dual-ipv4-and-ipv6 template will be assigned as the default SDM template using the instructions below.
S1# setup terminal
S1(config)# sdm prefer dual-ipv4-and-ipv6 default
S1(config)# end
S1# reload
Essential Resources
Two Routers (Cisco 4221 with Cisco IOS XE Release 16.9.4 universal image or comparable)
1 Switch (Cisco 2960 equipped with Cisco IOS Release 15.2(2) lanbasek9 image or equivalent)
2 PCs (Windows with terminal emulation program, such as Tera Term)
Ethernet and serial connections, as indicated in the diagram, are used to configure Cisco IOS equipment via their console ports.
Instructions
Part 1: Configure and construct the network
In Part 1, you will set up the PCs and Cisco devices and set up the network layout. The default router and switch configurations are given for your reference. In this architecture, packets are routed across networks by static routing.
Step 1: Wire the network according to its topology.
Step 2: Clear the router and switch settings and reload the devices.
Configure PC IP addresses and default gateways based on the Addressing Table in Step 3.
Configure the R1 and ISP routers, as well as the S1 switch, using the starting settings given below.
At the prompt for the switch or router's global configuration mode, copy and paste each device's configuration. The setting is saved to startup-config.
Launch configuration display
Initial router settings for R1:
hostname R1
no IP domain lookup
Unicast-routing in IPv6
connection g0/0/0
IP address range: 64.100.0.2 to 255.255.255.252
ipv6 address 2001:db8:acad::2/64
ipv6 address fe80::2 is a link-local address.
IP nat exterior
no shutdown
connection g0/0/1
ip add 192.168.1.1 255.255.255.0
ipv6 address 2001:db8:acad:1::1/64
address fe80::1 using link-local
IP nat inside
no suspension
IP path 0.0.0.0 0.0.0.0 64.100.0.1
ipv6 route 0::/0 2001:db8:acad::1
access-list 1 permit 192.168.1.0 0.0.0.255
IP nat overload within source list 1 interface g0/0/0
The close window for configuration
Initial ISP configurations:
Launch configuration display
hostname ISP
no ip domain lookup
Unicast-routing in IPv6
connection g0/0/0
IP address range: 64.100.0.1 to 255.255.255.252
ipv6 address 2001:db8:acad::1/64
address fe80::1 using link-local
no suspension
connection g0/0/1
IP add 209.165.200.225 255.255.255.224
ipv6 address 2001:db8:acad:200::225/64
ipv6 address fe80::225 is a link-local address.
no suspension
ipv6 route::/0 2001:db8:acf::2
The close window for configuration
Answers Note: If Netlab is utilised, inactive switch interfaces must be disabled for this lab. As an example, S1 supports the following commands:
Switch(config)# interface range f0/1 - 4, f7 - 24, and g1 - 2
Switch(config)# power off
Initial S1 configurations:
hostname S1
no IP domain-lookup
interface VLAN 1
ip add 192.168.1.2 255.255.255.0
ipv6 address 2001:db8:acad:1::2/64
ipv6 address fe80::2 is a link-local address.
no suspension
exit
192.168.1.1 is the default gateway IP address.
end
Configure an IP host table on the R1 router in Step 5.
The IP host table enables you to connect to a distant device using its hostname rather than its IP address. The host table supports name resolution for the following setups of the device. Copy and paste the settings shown below for the R1 router. The settings enable the usage of hostnames with the ping and traceroute commands on the R1 router.
Launch configuration display
IP host Externalv4 209.165.200.226
ip host Externalv6 2001:db8:acad:200::226
ISPv4 host IP address 64.100.0.1
ISPv6 host ip address 2001:db8:acad::1
PC-Av4 IP host 192.168.1.10
PC-Av6 IP Host 2001:db8:aca:1::10
ip host R1v4 64.100.0.2
ip host R1v6 2001:db8:acad::2
IP host address 192.168.1.2 for S1v4
IP address of host S1v6 is 2001:db8:acac:1::2.
end
the configuration window has been closed
Use the Ping command for basic network testing in Section 2.
In Part 2 of this experiment, verify end-to-end connection using the ping command. Ping functions by sending ICMP echo request packets to the target host and then waiting for an ICMP response. It can log the round-trip time, packet loss, and routing loops.
On a network, IP packets have a limited lifespan. IP packets use an 8-bit Time to Live (IPv4) or Hop Limit (IPv6) header field value that determines the maximum number of layer three hops that may be travelled en route to their destination. Each host on a network will set an 8-bit value with a maximum of 255.
Therefore, each time an IP packet reaches a layer three network device, its number is decreased by one before the packet is sent to its destination. Therefore, if this value hits 0, the IP packet is rejected.
Examine the findings using the ping command and extra ping parameters available on Windows-based PCs and Cisco devices.
Step 1: Use PC-A to test the network connection from the R1 network.
PC-A should be able to ping all other devices in the topology successfully. Check the topology and cabling, as well as the setup of the Cisco devices and the PCs, if they are not.
Ping the default gateway of PC-A using its IPv4 address (GigabitEthernet 0/0/1 interface on R1).
Activate command prompt
C:\> ping 192.168.1.1
192.168.1.1 was pinged with 32 bytes of data:
bytes=32 time1ms TTL=255 is the reply from 192.168.1.1.
bytes=32 time1ms TTL=255 is the reply from 192.168.1.1.
bytes=32 time1ms TTL=255 is the reply from 192.168.1.1.
bytes=32 time1ms TTL=255 is the reply from 192.168.1.1.
Statistics for 192.168.1.1's ping:
Sending = 4, Receiving = 4, Losing = 0 (0 percent loss),
Round-trip times in milliseconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
In this instance, four (4) 32-byte ICMP queries were sent, and replies were received in less than one millisecond with no packet loss. As additional devices along the path to the end destination handle ICMP requests and answers, the transmission and response times might grow.
This may also be accomplished by using the IPv6 address of the default gateway (GigabitEthernet 0/0/1 interface on R1).
C:\> ping 2001:db8:acad:1::1
With 32 bytes of data, the address 2001:db8:acad:1::1 is pinging.
5ms response time from 2001:db8:acad:1::1
time=1ms Response from 2001:db8:acad:1::1
time=1ms Response from 2001:db8:acad:1::1
time=1ms Response from 2001:db8:acad:1::1
Statistics for 2001:db8:acad:1::1: ping
Sending = 4, Receiving = 4, Losing = 0 (0 percent loss),
Round-trip times in milliseconds:
Minimum = 1ms, Maximum = 5ms, Average = 2ms
Ping the addresses mentioned in the table below from PC-A and record the average round trip time, IPv4 Time to Live (TTL), and an IPv6 Hop Limit. Optional: Utilize WireShark to determine the IPv6 Hop Limit.
Step 2: On PC-A, use extended ping instructions.
The default ping command makes four 32-byte queries. Before showing the "Request timed out" notice, it waits 4,000 milliseconds for each answer to be delivered. The ping command may be customised for network troubleshooting.
Type ping at the command prompt and click Enter.
C:\> ping
ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS] [-f] [-i TTL]
[-r count] [-s count] [[-j host-list] | [-k host-list] [-r count] [-s count]
[-w timeout] [-R [-S srcaddr] [-4] [-6]
Options:
-t Ping the given host until it is stopped.
To see statistics and proceed, press Control-Break;
To quit, press Control-C.
-a Resolve an IP address to its hostname.
-n count The quantity of echo requests to transmit.
-l size Send buffer size.
-f Set Don't Fragment flag in package (IPv4-only).
I TTL Time To Live.
-v TOS Type Of Service (IPv4-only. This parameter is no longer supported.
and has no influence on the IP header's type of service field).
-r count Record route for hops count (IPv4-only).
-s count Timestamp for number of hops (IPv4-only).
-j host-list Loose source route along host-list (IPv4-only).
-k host-list Strict source route along the specified host-list (IPv4-only).
-w timeout Waiting timeout in milliseconds for each response.
-R Use routing header for reverse route testing as well (IPv6-only).
-S srcaddr Source address to be used.
-4 Make IPv4 mandatory.
-6 Utilize IPv6 only.
Ping External using the –t option to ensure that External is accessible.
C:\Users\User1> ping –t 209.165.200.226
32 bytes of data were sent while pinging 209.165.200.226.
bytes=32 time1ms TTL=126 in reply from 209.165.200.226
bytes=32 time1ms TTL=126 in reply from 209.165.200.226
Disconnect the wire between the ISP router and External or disable the GigabitEthernet 0/0/1 interface on the ISP router to demonstrate the effects when a host is inaccessible.
bytes=32 time1ms TTL=126 in reply from 209.165.200.226
Response from 64.100.0.1: Host cannot be reached.
Response from 64.100.0.1: Host cannot be reached.
During normal network operation, the ping command may identify whether a target answered and how long it takes to obtain a response. If there is a difficulty with network connection, the ping command shows an error message.
Before proceeding, reconnect the Ethernet connection or activate the GigabitEthernet 0/0/1 interface on the ISP router (using the no shutdown command). After around 30 seconds, the ping should once again succeed.
Response from 64.100.0.1: Host cannot be reached.
Request has expired.
Request has expired.
bytes=32 time1ms TTL=126 in reply from 209.165.200.226
bytes=32 time1ms TTL=126 in reply from 209.165.200.226
Enter Ctrl+C to terminate the ping command.
Repeat the procedures above for an IPv6 address to produce an ICMP error message.
Question:
What error messages did you get from ICMP?
Destination net inaccessible, request timed out.
Before proceeding to the next step, enable the GigabitEthernet 0/0/1 interface on the ISP router using the no shutdown command. After around 30 seconds, the ping should once again succeed.
Terminate command prompt
Step 3: Utilize Cisco devices to test network connection from the R1 network.
Cisco equipment are also equipped with the ping command. This stage involves examining the ping command using the R1 router and the S1 switch.
Ping External using the IP address 209.165.200.226 on the external network from the R1 router.
R1# ping 209.165.200.226
Type escape sequence to abort.
Sending five 100-byte ICMP Echos to 209.165.200.226 with a two-second timeout:
!!!!!
100 percent success rate (5/5), round-trip minimum/average/maximum = 1/1/1 ms
The exclamation sign (!) indicates that the ping from R1 to External was successful. The round journey takes an average of 1 milliseconds with no packet loss, as demonstrated by a success rate of one hundred percent.
Due to the configuration of a local host table on the R1 router, it is possible to ping Externalv4 on the external network using the hostname defined on the R1 router.
Note that the case of the hostname is ignored. On R1 in this lab, you may swap the hostname for the IP address if required.
R1# ping externalv4
Question:
What IP address is used?
209.165.200.226
There are more options for the ping command. At the command prompt, enter ping and hit Enter. Use the ipv6 protocol. Enter 2001:DB8:ACAD:200::226 or an external IPv6 address for the Target. To accept the default setting for other selections, press Enter.
R1# ping
Protocol [ip]: ipv6
Target IPv6 address: 2001:db8:acad:200::226
Repeat number [5]:
Datagram size [100]:
Timeout in milliseconds:
Extended instructions? [no]:
Sweep range of sizes? [no]:
Type escape sequence to abort.
Sending five 100-byte ICMP Echos to 2001:DB8:ACAD:200::226, with a 2-second timeout
!!!!!
100 percent success rate (5/5), round-trip minimum/average/maximum = 1/1/1 ms
Using an extended ping, you may determine whether there is a network problem. Start the ping command with a count of 50000 to 209.165.200.226. Then, unplug the wire between the ISP router and EXTERNAL or disable GigabitEthernet 0/0/1 on the ISP router.
After the exclamation points (!) are replaced by the letter U and periods, reconnect the Ethernet connection or activate the GigabitEthernet 0/0/1 interface on the ISP router (.). After around 30 seconds, the ping should once again succeed. If preferred, use Ctrl+Shift+6 to terminate the ping command.
R1# ping
Protocol [ip]:
Target IP address: 209.165.200.226
Count of repeats [5]: 10,000
Datagram size [100]:
Timeout in milliseconds:
Extended instructions [n]:
Sweep range of sizes [n]:
Sending 500 100-byte ICMP Echos to 209.165.200.226 with a 2-second timeout:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
output withheld>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
.U.U.U.U.U.
U.U…………….!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
output withheld>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!
Success rate is 99.7% (9970/10000), round-trip minimum/average/maximum = 1/1/10 milliseconds
The letter U in the results denotes an inaccessible location. A protocol data unit (PDU) containing an error was received by the R1 router. Each period (.) indicates that the ping timed out while waiting for a response from External. 1% of the packets were lost during the simulated network outage in this scenario.
Note: You may also get the same outcomes with the following commands:
R1# ping 209.165.200.226 many times
or
R1# ping 2001:db8:acac:200::226 repeated 10000 times
Close window for configuration
The ping function is very helpful for diagnosing network connection issues. However, when ping fails, it cannot pinpoint the location of the issue. tracert (or traceroute) displays network latency and path information.
Using Tracert and Traceroute for Fundamental Network Testing
PCs and network devices include the necessary commands for tracing routes. Using ICMP messages, the tracert command on a Windows-based computer traces the route to the end destination. For Cisco devices and other Unix-like PCs, the traceroute command leverages User Datagram Protocol (UDP) datagrams to trace paths to the end destination.
In Part 3, you will analyse the traceroute instructions and discover a packet's path to its ultimate destination. You will use the tracert command on Windows computers and the traceroute command on Cisco devices. You will also investigate the different choices for fine-tuning the traceroute findings.
Utilize the tracert command from PC-A to EXTERNAL in Step 1.
Input tracert 209.165.200.226 into the command prompt.
Launch the command prompt
trace route 209.165.200.226
Following the path to EXTERNAL [209.165.200] .226]
Over no more than 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 64.100.0.1
3 1 ms <1 ms <1 ms [209.165.200 .226]
Trace complete.
The traceroute findings suggest that the path from PC-A to EXTERNAL is PC-A to R1, then ISP, and finally EXTERNAL. The route to EXTERNAL required two router hops to reach its ultimate destination.
Step 2: Investigate other tracert command options.
Enter tracert at the command line to see the available settings.
C:> tracing
Tracert [-d] [-h maximum hops] [-j host-list] [-w timeout] Usage:
[-R] [-S srcaddr] [-4] [-6] target name
Options:
-d Disable the resolution of IP addresses to hostnames.
-h maximum hops Maximum number of hops for the target search.
-j host-list Loose source route along host-list (IPv4-only).
-w timeout Delay each reply for timeout milliseconds.
-R Trail return route (IPv6-only).
-S srcaddr Source address to use (IPv6-only).
-4 Compulsory use of IPv4
-6 Utilize IPv6 only.
Utilize the –d switch. The IP address 209.165.200.226 cannot be resolved as EXTERNAL.
C:\> tracert –d 209.165.200.226
A maximum of 30 hops are required to reach 209.165.200.226.
1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 64.100.0.1
3 1 ms <1 ms <1 ms 209.165.200.226
Trace complete.
Terminate command prompt
Step 3: Use the traceroute command to reach External from the R1 router.
At the R1 router's command prompt, enter traceroute 209.165.200.226 or traceroute 2001:db8:acac:200::226. The hostnames are resolved since the R1 router was configured using a local IP host table.
Launch configuration display
Traceroute from R1 to 209.165.200.226
Type escape sequence to abort.
Identifying the path to Externalv4 (209.165.200.226)
VRF info: (vrf in name/id, vrf out name/id)
1 ISPv4 (64.100.0.1) 1 msec 1 msec 1 msec
2 Externalv4 (209.165.200.226) 1 msec 1 msec 1 msec
R1# tracing 2001:db8:aca:200::226
Type escape sequence to abort.
Identifying the path to EXTERNAL (2001:DB8:ACAD:200::226)
1 ISPv6 (2001:DB8:ACAD::1) 8 milliseconds 1 millisecond 1 millisecond
2 Externalv6 (2001:DB8:ACAD:200::226) 0 msec 0 msec 0 msec
Close window for configuration
Use the traceroute command from the S1 switch to External in the fourth step.
Enter traceroute 209.165.200.226 or traceroute 2001:db8:acac:200::226 on the S1 switch. The hostnames are not presented in the traceroute results because this switch is not set with a local IP host table.
Activate the configuration window
Traceroute from S1 to 209.165.200.226
Type escape sequence to abort.
Attempting to locate 209.165.200.226
1 192.168.1.1 0 msec 0 msec 0 msec
2 64.100.0.1 8 msec 0 msec 0 msec
3 209.165.200.226 0 msec * 0 msec
S1# traceroute 2001:db8:acad:200::226
Type escape sequence to abort.
Following the path leading to 2001:DB8:ACAD:200::226
1 2001:DB8:ACAD:1::1 0 milliseconds 0 milliseconds 0 milliseconds
2 2001:DB8:ACAD::1 8.0 0.0 0.0 seconds
3 2001:DB8:ACAD:200::226 0.00 0.00 0.00
Close window for configuration
There are other traceroute possibilities. You may use the? To explore these choices, type traceroute at the prompt and click Enter, or type traceroute and press Enter.
This page gives further information on the ping and traceroute commands for Cisco devices:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products tech note09186a00800a6057.shtml
Part 4: Diagnose the Topology
Step one is to copy and paste the settings below into the ISP router.
Launch configuration display
hostname ISP
connection g0/0/0
IP address range: 64.100.0.1 to 255.255.255.252
ipv6 address 2001:db8:acad::1/64
no suspension
connection g0/0/1
192.168.8.1 255.255.255.0 is an IP address and subnet mask.
no ipv6 address 2001:db8:acad:200::225/64
ipv6 address 2001:db8:acad:201::225/64
no suspension
end
Close window for configuration
Step 2: From the R1 network, use ping and tracert or traceroute to diagnose and resolve the issue on the ISP network.
Utilize PC-ping A's and tracert commands.
The tracert command may be used to determine end-to-end network connection. This tracert result shows that PC-A can communicate with its default gateway, 192.168.1.1, but cannot communicate with External.
Activate command prompt
trace route 209.165.200.226
Maximum of 30 hops are required to reach 209.165.200.226.
1 <1 ms <1 ms <1 ms 192.168.1.1
2 <1 ms <1 ms <1 ms 64.100.0.1
3 64.100.0.1 says that the target host is inaccessible.
Trace complete.
Pinging each hop in the network to EXTERNAL is one method for locating the network problem. Determine whether PC-A can connect to the g0/0/0 interface with IP address 64.100.0.1 on the ISP router.
C:\> ping 64.100.0.1
PC-A has access to the ISP's router. The network connection problem is with the 209.165.200.224/24 network, based on the successful ping results from PC-A to the ISP router. Ping the default gateway to External, which is the ISP router's GigabitEthernet 0/0/1 interface.
C:\> ping 209.165.200.225
32 bytes of data were sent while pinging 209.165.200.225.
Response from 209.165.200.225: Host cannot be reached.
Response from 209.165.200.225: Host cannot be reached.
Response from 209.165.200.225: Host cannot be reached.
Response from 209.165.200.225: Host cannot be reached.
Statistics for 209.165.200.225's ping:
Sending = 4, Receiving = 4, Losing = 0 (0 percent loss),
PC-A cannot connect to the GigabitEthernet 0/0/1 interface of the ISP router, as shown by the ping command results.
The findings of tracert and ping indicate that PC-A can communicate with the R1 and ISP routers, but not with External or its default gateway.
Terminate command prompt
Examine the active ISP router settings using the display command.
Launch configuration display
ISP# display ip interface summary
IP-Address Acceptable for Interface? Method Statistical Protocol
GigabitEthernet0/0/0 64.100.0.1 YES manually enabled
GigabitEthernet0/0/1 192.168.8.1 YES manually enabled
Serial0/1/0 unassigned YES unset up up
Serial0/1/1 unassigned YES unset up up
GigabitEthernet0 is unassigned and has not been laid down.
ISP# display ran
output withheld>
Gigabit Ethernet interface GigabitEthernet0/0/0
IP address range: 64.100.0.1 to 255.255.255.252
negotiation auto
address FE80::1 is a link-local
ipv6 address 2001:DB8:ACAD::1/64
!
Gigabit Ethernet interface GigabitEthernet0/0/1
192.168.8.1 255.255.255.0 is an IP address and subnet mask.
negotiation auto
address FE80::225 is a link-local
ipv6 address 2001:DB8:ACAD:201::225/64
!
serial interface Serial0/1
no ip address
!
serial port Serial0/1/1
no ip address
output withheld>
The results of the show run and show ip interface short commands reveal that the GigabitEthernet 0/0/1 interface is up/up but has an erroneous IP address.
Correct the identified errors.
ISP# setup terminal
Enter instructions for configuration, one per line. Stop at CNTL/Z.
ISP(config)# GigabitEthernet 0/0/1 interface
ISP(config-if)# 192.168.8.1 255.255.255.0 no ip address
ISP(config-if)# ip address 209.165.200.225 255.255.255.224
Close window for configuration
Verify PC-ability A's to ping and traceroute to EXTERNAL.
Activate command prompt
C:\> ping 209.165.200.226
32 bytes of data were sent while pinging 209.165.200.226.
bytes=32 time=44ms TTL=126 in reply from 209.165.200.226
bytes=32 time=41ms TTL=126 in reply from 209.165.200.226
bytes=32 time=40ms TTL=126 in reply to 209.165.200.226
bytes=32 time=41ms TTL=126 in reply from 209.165.200.226
Ping stats for IP address 209.165.200.226:
Sending = 4, Receiving = 4, Losing = 0 (0 percent loss),
Round-trip times in milliseconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
trace route 209.165.200.226
Following the path to EXTERNAL [209.165.200] .226]
Over no more than 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 64.100.0.1
3 1 ms <1 ms <1 ms [209.165.200 .226]
Trace complete.
Terminate command prompt
After confirming that there are no network connection difficulties on the 192.168.1.0/24 network, this may also be achieved using the ping and traceroute commands from the CLI on the ISP router and the S1 switch.
Now repeat the procedure to establish IPv6 connection. Note: If you discover an invalid IPv6 address, you must manually delete it since it is not replaced by a new ipv6 address command.
Reflection Questions
In addition to network connection concerns, what may prevent ping or traceroute replies from reaching the source device?
Firewall on the PCs, access list command, routing problems, interface failure, and network latency
If you ping an invalid remote network address, such as 209.165.200.227, what message is produced by the ping command? What does this signifier? What should you verify if you ping a legitimate host address and obtain this response?
Request timeouts or intervals (.). This indicates that no answer was received within the preset time period. Check the following: router is down, target host is down, return route to your device, and response latency does not exceed the preset time period.
If you attempt to ping an address that does not exist in any network in your topology, such as 192.168.5.3, from a Windows PC, what message is displayed? What is the meaning of this message?
Destination host inaccessible. This warning indicates that there is no route to the target network because it is not included in the routing database.
What is the configured IPv4 TTL value on the Windows host? What IPv4 TTL value is configured on a Cisco device?
Windows sets the TTL value to 128, whereas the Cisco device sets it to 255.
What value is specified for the IPv6 Hop Limit on the Windows host? What IPv6 Hop Limit value is configured on a Cisco device?
Windows sets the TTL value to 128, the same as the IPv4 TTL value, however the Cisco device sets the TTL value to 64.
Note: To determine how the router is setup, examine the interfaces to determine the kind of router and the number of interfaces. There is no practical method to list all configuration choices for each router type. This table contains IDs for the device's various Ethernet and Serial interface combinations. The table does not list any more interface types, despite the fact that certain routers may include them. Such an example may be an ISDN BRI interface. The text included in parentheses is the legal shorthand that may be used to represent the interface in Cisco IOS instructions.
Device Settings
R1 router
Run R1# show
Building design...
1806 bytes are used now.
!
variant 16.9
datetime msec service timestamps debug
datetime msec service timestamps logging
monitor platform qfp usage load 80
No punt-keepalive or disable-kernel-core on the platform
!
ip address R1
!
boot-start-marker
boot-end-marker
!
no new AAA models
!
Externalv4 IP address: 209.165.200.226
Externalv6 2001:DB8:ACAD:200::226 IP address
ISPv4 IP address 64.100.0.1
IP address host 2001:DB8:ACAD::1
IP address host PC-Av4:192.168.1.10
PC-Av6 2001:DB8:ACAD:1::10 IP Address
S1v4 IP Host: 192.168.1.2
S1v6 2001:DB8:ACAD:1::2 IP Host
no IP search for domain
!
On-success log for login
!
subscriber-based templates
!
Unicast routing over IPv6
genuine multilink bundle-name
!
unauthorised smart enable
minimum diagnostic bootup level
!
system-id spanning-tree extend
!
redundancy
not in mode
!
GigabitEthernet interface 0/0/0
64.100.0.2 255.255.255.252 as the IP address
ip nat exterior
bargaining auto
link-local ipv6 address FE80::
Address in IPv6: 2001:DB8:ACAD::2/64
!
Gigabit Ethernet 0/0/1 interface
IP address 255.255.255.0 is 192.168.1.1.
inside with ip
bargaining auto
link-local ipv6 address FE80::1
Address in IPv6: 2001:DB8:ACAD:1::1/64
!
Serial0/1/0 interface
IP address absent
!
connection Serial0/1/1
IP address absent
!
overload on the GigabitEthernet 0/0/0 interface with ip nat within source list 1.
forward-protocol ip nd
HTTP server without IP
server-ip http secure
IP route 64.100.0.1 is 0.0.0.0 0.0.0.0.
!
permit 192.168.1.0 0.0.0.255 access-list 1
Route::/0 2001:DB8:ACAD::1 for IPv6
!
control-plane
!
con line 0
no transport input
1 stopbits
0 line aux
1 stopbits
vty line 0 4
login
!
end
ISP router
run ISP# show
Building design...
Configuration right now: 1337 bytes
!
variant 16.9
datetime msec service timestamps debug
datetime msec service timestamps logging
monitor platform qfp usage load 80
No punt-keepalive or disable-kernel-core on the platform
!
ISP hostname
!
boot-start-marker
boot-end-marker
!
no new AAA models
!
no IP search for domain
!
On-success log for login
!
subscriber-based templates
!
Unicast routing over IPv6
genuine multilink bundle-name
!
unauthorised smart enable
minimum diagnostic bootup level
!
system-id spanning-tree extend
!
redundancy
not in mode
!
GigabitEthernet interface 0/0/0
IP address: 255.255.255.252 64.100.0.1
bargaining auto
link-local ipv6 address FE80::1
Address in IPv6: 2001:DB8:ACAD::1/64
!
Gigabit Ethernet 0/0/1 interface
IP number 255.255.255.224 is 209.165.200.225.
bargaining auto
address FE80::225 link-local in ipv6
Address in IPv6: 2001:DB8:ACAD:200::225/64
!
Serial0/1/0 interface
IP address absent
!
connection Serial0/1/1
IP address absent
!
forward-protocol ip nd
HTTP server without IP
server-ip http secure
!
Route 2001:db8:acad:1::/64 2001:db8:acad::2 in IPv6
!
control-plane
!
con line 0
no transport input
1 stopbits
0 line aux
1 stopbits
vty line 0 4
login
!
end
S1 switch
short S1# show run
Building design...
Configuration at this time: 1699 bytes
!
variant 12.2
service pad absent
datetime msec service timestamps debug
datetime msec service timestamps logging
no password encryption service
!
ip address S1
!
boot-start-marker
boot-end-marker
!
no new AAA models
1500 system mtu routing
without ip domain-lookup
!
self-signed crypto pki trustpoint 3822041216
registration self-signed
IOS Self-Signed Certificate 3822041216 is the topic.
no revocation check
TP-self-signed-3822041216 by rsakeypair
!
chain of cryptographic certificates issued by oneself (3822041216)
self-signed certificate 01
!
pvst in spanning-tree mode
system-id spanning-tree extend
!
rising vlan internal allocation policy
!
Connectivity FastEthernet0/1
!
the FastEthernet 0/2 interface
!
a FastEthernet0/3 interface
!
the FastEthernet0/4 interface
!
Connectivity FastEthernet0/5
!
FastEthernet0/6 interface
!
Connectivity FastEthernet0/7
!
Fast Ethernet interface 0/8
!
a FastEthernet 0/9 interface
!
Fast Ethernet interface 0/10
!
Fast Ethernet interface 0/11
!
FastEthernet 0/12 interface
!
/13 FastEthernet interface
!
/14 FastEthernet interface
!
FastEthernet0/15 interface
!
a FastEthernet0/16 interface
!
Fast Ethernet interface 0/17
!
the FastEthernet 0/18 interface
!
the FastEthernet 0/19 interface
!
Fast Ethernet interface 0/20
!
/21 FastEthernet interface
!
/22 FastEthernet interface
!
/23 FastEthernet interface
!
/24 FastEthernet interface
!
Gigabit Ethernet 0/1 interface
!
Gigabit Ethernet 0/2 interface
!
LAN1 interface
IP 192.168.1.2 255.255.255.0
link-local ipv6 address FE80::
Address in IPv6: 2001:DB8:ACAD:1::2/64
!
IP Address Default Gateway: 192.168.1.1
classless ip
http server ip
server-ip http secure
!
con line 0
Logging in real time
vty line 0 4
login
vty 5 and 15
login
!
end
Comments
Post a Comment