Lab 6.7.

1: Ping and Traceroute

Topology Diagram

Addressing Table
Device R1-ISP Interface S0/0/0 Fa0/0 S0/0/0 Fa0/0 N/A Eagle Server hostPod#A hostPod#B S1-Central N/A N/A N/A N/A IP Address 10.10.10.6 Subnet Mask 255.255.255.252 Default Gateway N/A N/A N/A N/A 192.168.254.253 N/A 172.16.255.254 172.16.255.254 172.16.255.254

192.168.254.253 255.255.255.0 10.10.10.5 172.16.255.254 255.255.255.252 255.255.0.0

R2-Central

192.168.254.254 255.255.255.0 172.31.24.254 172.16.Pod#.1 172.16.Pod#.2 172.16.254.1 255.255.255.0 255.255.0.0 255.255.0.0 255.255.0.0

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 1 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPV4

Lab 6.7.1: Ping and Traceroute

Learning Objectives
Upon completion of this lab, you will be able to: Use the ping command to verify simple TCP/IP network connectivity. Use the tracert/traceroute command to verify TCP/IP connectivity.

Background
Two tools that are indispensable when testing TCP/IP network connectivity are ping and tracert. The ping utility is available on Windows, Linux, and Cisco IOS, and tests network connectivity. The tracert utility is available on Windows, and a similar utility, traceroute, is available on Linux and Cisco IOS. In addition to testing for connectivity, tracert can be used to check for network latency. For example, when a web browser fails to connect to a web server, the problem can be anywhere between client and the server. A network engineer may use the ping command to test for local network connectivity or connections where there are few devices. In a complex network, the tracert command would be used. Where to begin connectivity tests has been the subject of much debate; it usually depends on the experience of the network engineer and familiarity with the network. The Internet Control Message Protocol (ICMP) is used by both ping and tracert to send messages between devices. ICMP is a TCP/IP Network layer protocol, first defined in RFC 792, September, 1981. ICMP message types were later expanded in RFC 1700.

Scenario
In this lab, the ping and tracert commands will be examined, and command options will be used to modify the command behavior. To familiarize the students with the use of the commands, devices in the Cisco lab will be tested. Measured delay time will probably be less than those on a production network. This is because there is little network traffic in the Eagle 1 lab.

Task 1: Use the ping Command to Verify Simple TCP/IP Network Connectivity.
The ping command is used to verify TCP/IP Network layer connectivity on the local host computer or another device in the network. The command can be used with a destination IP address or qualified name, such as eagle-server.example.com, to test domain name services (DNS) functionality. For this lab, only IP addresses will be used. The ping operation is straightforward. The source computer sends an ICMP echo request to the destination. The destination responds with an echo reply. If there is a break between the source and destination, a router may respond with an ICMP message that the host is unknown or the destination network is unknown. Step 1: Verify TCP/IP Network layer connectivity on the local host computer. C:\> ipconfig Windows IP Configuration Ethernet adapter Local Area Connection-specific IP Address. . . . . Subnet Mask . . . . Default Gateway . . C:\>

Connection: DNS Suffix . . . . . . . . . . . . . . . . . .

. . . .

: : 172.16.1.2 : 255.255.0.0 : 172.16.255.254

Figure 1. Local TCP/IP Network Information

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 2 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPV4

Lab 6.7.1: Ping and Traceroute

1. Open a Windows terminal and determine IP address of the pod host computer with the ipconfig command, as shown in Figure 1. The output should look the same except for the IP address. Each pod host computer should have the same network mask and default gateway address; only the IP address may differ. If the information is missing or if the subnet mask and default gateway are different, reconfigure the TCP/IP settings to match the settings for this pod host computer. 2. Record information about local TCP/IP network information: TCP/IP Information IP Address Subnet Mask Default Gateway Value 10.100.8.72 255.255.0.0 172.16.255.254

Figure 2. Output of the ping Command on the Local TCP/IP Stack 3. Use the ping command to verify TCP/IP Network layer connectivity on the local host computer. By default, four ping requests are sent to the destination and reply information is received. Output should look similar to that shown in Figure 2.

n Destination address, set to the IP address for the local computer. o Reply information:
bytessize of the ICMP packet. timeelapsed time between transmission and reply. TTLdefault TTL value of the DESTINATION device, minus the number of routers in the path. The maximum TTL value is 255, and for newer Windows machines the default value is 128.

p Summary information about the replies: q Packets Sentnumber of packets transmitted. By default, four packets are sent. r Packets Receivednumber of packets received. s Packets Lost difference between number of packets sent and received. t Information about the delay in replies, measured in milliseconds. Lower round trip times indicate faster links. A computer timer is set to 10 milliseconds. Values faster than 10 milliseconds will display 0.

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 3 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPV4

Lab 6.7.1: Ping and Traceroute

4. Fill in the results of the ping command on your computer: Field Size of packet Number of packets sent Number of replies Number of lost packets Minimum delay Maximum delay Average delay Value 32 bytes 4 4 0 0ms 0ms 0ms

Step 2: Verify TCP/IP Network layer connectivity on the LAN. C:\> ping 172.16.255.254 Pinging 172.16.255.254 with 32 bytes of data: Reply from 172.16.255.254: bytes=32 time=1ms TTL=255 Reply from 172.16.255.254: bytes=32 time<1ms TTL=255 Reply from 172.16.255.254: bytes=32 time<1ms TTL=255 Reply from 172.16.255.254: bytes=32 time<1ms TTL=255 Ping statistics for 172.16.255.254: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms C:\> Figure 3. Output of the ping Command to the Default Gateway 1. Use the ping command to verify TCP/IP Network layer connectivity to the default gateway. Results should be similar to those shown in Figure 3. Cisco IOS default TTL value is set to 255. Because the datagrams did not travel through a router, the TTL value returned is 255. 2. Fill in the results of the ping command to the default Gateway: Field Size of packet Number of packets sent Number of replies Number of lost packets Minimum delay Maximum delay Average delay Value 32 bytes 4 4 0ms 0ms 1ms 0ms

What would be the result of a loss of connectivity to the default gateway? could not reach external networks ___________________________________________________________________________________

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 4 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPV4

Lab 6.7.1: Ping and Traceroute

Step 3: Verify TCP/IP Network layer connectivity to a remote network. C:\> ping 192.168.254.254 Pinging 192.168.254.254 with 32 bytes of data: Reply from 192.168.254.254: bytes=32 time<1ms TTL=62 Reply from 192.168.254.254: bytes=32 time<1ms TTL=62 Reply from 192.168.254.254: bytes=32 time<1ms TTL=62 Reply from 192.168.254.254: bytes=32 time<1ms TTL=62 Ping statistics for 192.168.254.254: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\> Figure 4. Output of the ping Command to Eagle Server 1. Use the ping command to verify TCP/IP Network layer connectivity to a device on a remote network. In this case, Eagle Server will be used. Results should be similar to those shown in Figure 4. Linux default TTL value is set to 64. Since the datagrams traveled through two routers to reach Eagle Server, the returned TTL value is 62. 2. Fill in the results of the ping command on your computer: Field Size of packet Number of packets sent Number of replies Number of lost packets Minimum delay Maximum delay Average delay Value 32 bytes 4 4 0 0ms 0ms 0ms

C:\ > ping 192.168.254.254 Pinging 192.168.254.254 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.254.254: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\> Figure 5. Output of a ping Command with Lost Packets The ping command is extremely useful when troubleshooting network connectivity. However, there are limitations. In Figure 5, the output shows that a user cannot reach Eagle Server. Is the problem with Eagle Server or a device in the path? The tracert command, examined next, can display network latency and path information.

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 5 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPV4

Lab 6.7.1: Ping and Traceroute

Task 2: Use the tracert Command to Verify TCP/IP Connectivity.

The tracert command is useful for learning about network latency and path information. Instead of using the ping command to test connectivity of each device to the destination, one by one, the tracert command can be used. On Linux and Cisco IOS devices, the equivalent command is traceroute. Step 1: Verify TCP/IP Network layer connectivity with the tracert command. 1. Open a Windows terminal and issue the following command: C:\> tracert 192.168.254.254 C:\> tracert 192.168.254.254 Tracing route to 192.168.254.254 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 172.16.255.254 2 <1 ms <1 ms <1 ms 10.10.10.6 3 <1 ms <1 ms <1 ms 192.168.254.254 Trace complete. C:\> Figure 6. Output of the tracrt command to Eagle Server. Output from the tracert command should be similar to that shown in Figure 6. 2. Record your result in the following table: Field Maximum number of hops First router IP address Second router IP address Destination reached? Value 30 172.16.255.254 10.10.10.6 yes

Step 2: Observe tracert output to a host that lost network connectivity. If there is a loss of connectivity to an end device such as Eagle Server, the tracert command can give valuable clues as to the source of the problem. The ping command would show the failure but not any other kind of information about the devices in the path. Referring to the Eagle 1 lab Topology Diagram, both R2-Central and R1-ISP are used for connectivity between the pod host computers and Eagle Server. C:\> tracert -w 5 -h 4 192.168.254.254 Tracing route to 192.168.254.254 over a maximum of 4 hops 1 <1 ms <1 ms <1 ms 172.16.255.254 2 <1 ms <1 ms <1 ms 10.10.10.6 3 * * * Request timed out. 4 * * * Request timed out. Trace complete. C:\> Figure 7. Output of the tracert Command Refer to Figure 7. Options are used with the tracert command to reduce wait time (in milliseconds), -w 5, and maximum hop count, -h 4. If Eagle Server was disconnected from the network, the default gateway would respond correctly, as well as R1-ISP. The problem must be on the 192.168.254.0/24 network. In this example, Eagle Server has been turned off.
All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 6 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPV4

Lab 6.7.1: Ping and Traceroute

What would the tracert output be if R1-ISP failed? nothing reached after r2 central ___________________________________________________________________________________ What would the tracert output be if R2-Central failed? no connectivity ___________________________________________________________________________________

Task 3: Challenge
The default values for the ping command normally work for most troubleshooting scenarios. There are times, however, when fine tuning ping options may be useful. Issuing the ping command without any destination address will display the options shown in Figure 8: C:\> ping Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS] [-r count] [-s count] [[-j host-list] | [-k host-list]] [-w timeout] target_name Options: -t Break; -a -n -l -f -i -v -r -s -j -k -w C:\> count size TTL TOS count count host-list host-list timeout To stop - type Control-C. Resolve addresses to hostnames. Number of echo requests to send. Send buffer size. Set Don't Fragment flag in packet. Time To Live. Type Of Service. Record route for count hops. Timestamp for count hops. Loose source route along host-list. Strict source route along host-list. Timeout in milliseconds to wait for each reply. Ping the specified host until stopped. To see statistics and continue - type Control-

Figure 8. Output of a ping Command with no Destination Address The most useful options are highlighted in yellow. Some options do not work together, such as the t and n options. Other options can be used together. Experiment with the following options:

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 7 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPV4

Lab 6.7.1: Ping and Traceroute

To ping the destination address until stopped, use the t option. To stop, press <CTRL> C: C:\> ping t 192.168.254.254 Pinging 192.168.254.254 with 32 bytes of data: Reply from 192.168.254.254: bytes=32 time<1ms TTL=63 Reply from 192.168.254.254: bytes=32 time<1ms TTL=63 Reply from 192.168.254.254: bytes=32 time<1ms TTL=63 Reply from 192.168.254.254: bytes=32 time<1ms TTL=63 Reply from 192.168.254.254: bytes=32 time<1ms TTL=63 Reply from 192.168.254.254: bytes=32 time<1ms TTL=63 Ping statistics for 192.168.254.254: Packets: Sent = 6, Received = 6, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms Control-C ^C C:\> Figure 9. Output of a ping Command using the t Option To ping the destination once, and record router hops, use the n and r options, as shown in Figure 10. Note: Not all devices will honor the r option. C:\> ping -n 1 r 9 192.168.254.254 Pinging 192.168.254.254 with 32 bytes of data: Reply from 192.168.254.254: bytes=32 time=1ms TTL=63 Route: 10.10.10.5 -> 192.168.254.253 -> 192.168.254.254 -> 10.10.10.6 -> 172.16.255.254 Ping statistics for 192.168.254.254: Packets: Sent = 1, Received = 1, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms C:\> Figure 10. Output of a ping Command using the n and r Options

Task 4: Reflection
Both ping and tracert are used by network engineers to test network connectivity. For basic network connectivity, the ping command works best. To test latency and the network path, the tracert command is preferred. The ability to accurately and quickly diagnose network connectivity issues is a skill expected from a network engineer. Knowledge about the TCP/IP protocols and practice with troubleshooting commands will build that skill.

Task 5: Clean Up.

Unless directed otherwise by the instructor, turn off power to the host computers. Remove anything that was brought into the lab, and leave the room ready for the next class.

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 8 of 8

Lab 6.7.2: Examining ICMP Packets

Topology Diagram

Addressing Table
Device R1-ISP Interface S0/0/0 Fa0/0 S0/0/0 Fa0/0 N/A Eagle Server hostPod#A hostPod#B S1-Central N/A N/A N/A N/A IP Address 10.10.10.6 Subnet Mask 255.255.255.252 Default Gateway N/A N/A N/A N/A 192.168.254.253 N/A 172.16.255.254 172.16.255.254 172.16.255.254

192.168.254.253 255.255.255.0 10.10.10.5 172.16.255.254 255.255.255.252 255.255.0.0

R2-Central

192.168.254.254 255.255.255.0 172.31.24.254 172.16.Pod#.1 172.16.Pod#.2 172.16.254.1 255.255.255.0 255.255.0.0 255.255.0.0 255.255.0.0

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 1 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPV4

Lab 6.7.2: Examining ICMP Packets

Learning Objectives
Upon completion of this lab, you will be able to: Understand the format of ICMP packets. Use Wireshark to capture and examine ICMP messages.

Background
The Internet Control Message Protocol (ICMP) was first defined in RFC 792, September, 1981. ICMP message types were later expanded in RFC 1700. ICMP operates at the TCP/IP Network layer and is used to exchange information between devices. ICMP packets serve many uses in todays computer network. When a router cannot deliver a packet to a destination network or host, an informational message is returned to the source. Also, the ping and tracert commands send ICMP messages to destinations, and destinations respond with ICMP messages.

Scenario
Using the Eagle 1 Lab, Wireshark captures will be made of ICMP packets between network devices.

Task 1: Understand the Format of ICMP Packets.

Figure 1. ICMP Message Header Refer to Figure 1, the ICMP header fields common to all ICMP message types. Each ICMP message starts with an 8-bit Type field, an 8-bit Code field, and a computed 16-bit Checksum. The ICMP message type describes the remaining ICMP fields. The table in Figure 2 shows ICMP message types from RFC 792: Value 0 3 4 5 8 11 12 13 14 15 16 Meaning Echo Reply Destination Unreachable Source Quench Redirect Echo Time Exceeded Parameter Problem Timestamp Timestamp Reply Information Request Information Reply

Figure 2. ICMP Message Types Codes provide additional information to the Type field. For example, if the Type field is 3, destination unreachable, additional information about the problem is returned in the Code field. The table in Figure 3 shows message codes for an ICMP Type 3 message, destination unreachable, from RFC 1700:

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 2 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPV4

Lab 6.7.2: Examining ICMP Packets

Code Value 0 1 2 3 4 5 6 7 8 9 10 11 12

Meaning Net Unreachable Host Unreachable Protocol Unreachable Port Unreachable Fragmentation Needed and Don't Fragment was Set Source Route Failed Destination Network Unknown Destination Host Unknown Source Host Isolated Communication with Destination Network is Administratively Prohibited Communication with Destination Host is Administratively Prohibited Destination Network Unreachable for Type of Service Destination Host Unreachable for Type of Service Figure 3. ICMP Type 3 Message Codes

Using ICMP message capture shown in Figure 4, fill in the fields for the ICMP packet echo request. Values beginning with 0x are hexadecimal numbers:

Figure 4. ICMP Packet Echo Request

Using the ICMP message capture shown in Figure 5, fill in the fields for the ICMP packet echo reply:

Figure 5. ICMP Packet Echo Reply

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 3 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPV4

Lab 6.7.2: Examining ICMP Packets

At the TCP/IP Network layer, communication between devices is not guaranteed. However, ICMP does provide minimal checks for a reply to match the request. From the information provided in the ICMP messages above, how does the sender know that the reply is to a specific echo? the sequence number is used to identify the echo request. ___________________________________________________________________________________ ___________________________________________________________________________________

Task 2: Use Wireshark to Capture and Examine ICMP Messages.

Figure 6. Wireshark Download Site If Wireshark has not been loaded on the pod host computer, it can be downloaded from Eagle Server. 1. Open a web browser, URL FTP://eagleserver.example.com/pub/eagle_labs/eagle1/chapter6, as shown in Figure 6. 2. Right-click the Wireshark filename, click Save Link As, and save the file to the pod host computer. 3. When the file has been downloaded, open and install Wireshark. Step 1: Capture and evaluate ICMP echo messages to Eagle Server. In this step, Wireshark will be used to examine ICMP echo messages. 1. Open a Windows terminal on the pod host computer. 2. When ready, start Wireshark capture.

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 4 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPV4

Lab 6.7.2: Examining ICMP Packets

C:\> ping eagle-server.example.com Pinging eagle-server.example.com [192.168.254.254] with 32 bytes of data: Reply from 192.168.254.254: bytes=32 time<1ms TTL=63 Reply from 192.168.254.254: bytes=32 time<1ms TTL=63 Reply from 192.168.254.254: bytes=32 time<1ms TTL=63 Reply from 192.168.254.254: bytes=32 time<1ms TTL=63 Ping statistics for 192.168.254.254: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\> Figure 7. Successful ping Replies from Eagle Server 3. From the Windows terminal, ping Eagle Server. Four successful replies should be received from Eagle Server, as shown in Figure 7. 4. Stop Wireshark capture. There should be a total of four ICMP echo requests and matching echo replies, similar to those shown in Figure 8.

Figure 8. Wireshark Capture of ping Requests and Replies

192.168.254.254 Which network device responds to the ICMP echo request? __________________________________

5. Expand the middle window in Wireshark, and expand the Internet Control Message Protocol record until all fields are visible. The bottom window will also be needed to examine the Data field. 6. Record information from the first echo request packet to Eagle Server: Field Type Code Checksum Identifier Sequence number Data Value 8 0

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 5 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPV4

Lab 6.7.2: Examining ICMP Packets

yes Are there 32 bytes of data? _____

7. Record information from the first echo reply packet from Eagle Server: Field Type Code Checksum Identifier Sequence number Data Value 0 0ms

Which fields, if any, changed from the echo request? type and checksum ___________________________________________________________________________________

8. Continue to evaluate the remaining echo requests and replies. Fill in the following information from each new ping: Packet Request # 2 Reply # 2 Request # 3 Reply # 3 Request # 4 Reply # 4 Checksum Identifier Sequence number

Why did the Checksum values change with each new request? sequence number ___________________________________________________________________________________ Step 2: Capture and evaluate ICMP echo messages to 192.168.253.1. In this step, pings will be sent to a fictitious network and host. The results from the Wireshark capture will be evaluatedand may be surprising. Try to ping IP address 192.168.253.1. C:\> ping 192.168.253.1 C:\> ping 192.168.253.1 Pinging 192.168.253.1 with 32 bytes of data: Reply from 172.16.255.254: Destination host unreachable. Reply from 172.16.255.254: Destination host unreachable. Reply from 172.16.255.254: Destination host unreachable. Reply from 172.16.255.254: Destination host unreachable. Ping statistics for 192.168.253.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\> Figure 9. Ping Results from a Fictitious Destination See Figure 9. Instead of a request timeout, there is an echo response.
All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 6 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPV4

Lab 6.7.2: Examining ICMP Packets

What network device responds to pings to a fictitious destination? gateway router ___________________________________________________________________________________

Figure 10. Wireshark Capture from a Fictitious Destination Wireshark captures to a fictitious destination are shown in Figure 10. Expand the middle Wireshark window and the Internet Control Message Protocol record. Which ICMP message type is used to return information to the sender? 3 ___________________________________________________________________________________ What is the code associated with the message type? 1 host unreachable ___________________________________________________________________________________ Step 3: Capture and evaluate ICMP echo messages that exceed the TTL value. In this step, pings will be sent with a low TTL value, simulating a destination that is unreachable. Ping Eagle Server, and set the TTL value to 1: C:\> ping -i 1 192.168.254.254 C:\> ping -i 1 192.168.254.254 Pinging 192.168.254.254 with 32 bytes of data: Reply from 172.16.255.254: TTL expired in transit. Reply from 172.16.255.254: TTL expired in transit. Reply from 172.16.255.254: TTL expired in transit. Reply from 172.16.255.254: TTL expired in transit. Ping statistics for 192.168.254.254: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\> Figure 11. Ping Results for an Exceeded TTL See Figure 11, which shows ping replies when the TTL value has been exceeded. What network device responds to pings that exceed the TTL value? gateway router ___________________________________________________________________________________

Figure 12. Wireshark Capture of TTL Value Exceeded

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 7 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPV4

Lab 6.7.2: Examining ICMP Packets

Wireshark captures to a fictitious destination are shown in Figure 12. Expand the middle Wireshark window and the Internet Control Message Protocol record. Which ICMP message type is used to return information to the sender? type 11 ___________________________________________________________________________________ What is the code associated with the message type? code 0 time to live ___________________________________________________________________________________ Which network device is responsible for decrementing the TTL value? routers ___________________________________________________________________________________

Task 3: Challenge
Use Wireshark to capture a tracert session to Eagle Server and then to 192.168.254.251. Examine the ICMP TTL exceeded message. This will demonstrate how the tracert command traces the network path to the destination.

Task 4: Reflection
The ICMP protocol is very useful when troubleshooting network connectivity issues. Without ICMP messages, a sender has no way to tell why a destination connection failed. Using the ping command, different ICMP message type values were captured and evaluated.

Task 5: Clean Up
Wireshark may have been loaded on the pod host computer. If the program must be removed, click Start > Control Panel > Add or Remove Programs, and scroll down to Wireshark. Click the filename, click Remove, and follow uninstall instructions. Remove any Wireshark pcap files that were created on the pod host computer. Unless directed otherwise by the instructor, turn off power to the host computers. Remove anything that was brought into the lab, and leave the room ready for the next class.

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 8 of 8

Activity 6.7.3: IPv4 Address Subnetting Part 1

Learning Objectives
Upon completion of this activity, you will be able to determine network information for a given IP address and network mask.

Background
This activity is designed to teach how to compute network IP address information from a given IP address.

Scenario
When given an IP address and network mask, you will be able to determine other information about the IP address such as: Network address Network broadcast address Total number of host bits Number of hosts

Task 1: For a given IP address, Determine Network Information.

Given: Host IP Address Network Mask 172.25.114.250 255.255.0.0 (/16)

Find: Network Address Network Broadcast Address Total Number of Host Bits Number of Hosts

172.25.0.0 172.25.255.255 16 65536

Step 1: Translate Host IP address and network mask into binary notation. Convert the host IP address and network mask to binary: 172 10101100 11111111 255 25 11001000 11111111 255 114 01110010 00000000 0 250 11111010 00000000 0

IP Address Network Mask

Step 2: Determine the network address. 1. Draw a line under the mask. 2. Perform a bit-wise AND operation on the IP address and the subnet mask.
All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 4

CCNA Exploration Network Fundamentals: Addressing the Network - IPv4

Activity 6.7.3: IPv4 Address Subnetting Part 1

Note: 1 AND 1 results in a 1; 0 AND anything results in a 0. 3. Express the result in dotted decimal notation. 4. The result is the network address for this host IP address, which is 172.25.0.0. 172 10101100 11111111 10101100 172 25 11001000 11111111 11001000 25 114 01110010 00000000 00000000 0 250 11111010 00000000 00000000 0

IP Address Subnet Mask Network Address

Step 3: Determine the broadcast address for the network address The network mask separates the network portion of the address from the host portion. The network address has all 0s in the host portion of the address and the broadcast address has all 1s in the host portion of the address. 172 10101100 11111111 10101100 172 25 11001000 11111111 11001000 25 0 00000000 00000000 11111111 255 0 00000000 00000000 11111111 255

Network Add. Mask Broadcast.

By counting the number of host bits, we can determine the total number of usable hosts for this network. Host bits: 16 Total number of hosts: 2 = 65,536 65,536 2 = 65,534 (addresses that cannot use the all 0s address, network address, or the all 1s address, broadcast address.) Add this information to the table: Host IP Address Network Mask 172.25.114.250 255.255.0.0 (/16)
16

Network Address Network Broadcast Address Total Number of Host Bits Number of Hosts

172.25.0.0 172.25.255.255

16 / 65536

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 2 of 4

CCNA Exploration Network Fundamentals: Addressing the Network - IPv4

Activity 6.7.3: IPv4 Address Subnetting Part 1

Task 2: Challenge
For all problems: Create a Subnetting Worksheet to show and record all work for each problem. Problem 1 Host IP Address Network Mask Network Address Network Broadcast Address Total Number of Host Bits Number of Hosts 172.30.1.33 255.255.0.0

172.30.0.0 172.30.255.255 16 65536

Problem 2 Host IP Address Network Mask Network Address Network Broadcast Address Total Number of Host Bits Number of Hosts 172.30.1.33 255.255.255.0

172.30.1.0 172.30.1.255 8 2048

Problem 3 Host IP Address Network Mask Network Address Network Broadcast Address Total Number of Host Bits Number of Hosts 192.168.10.234 255.255.255.0

192.168.10.0 192.168.10.255 8 256

Problem 4 Host IP Address Network Mask Network Address Network Broadcast Address Total Number of Host Bits Number of Hosts 172.17.99.71 255.255.0.0

172.17.0.0 172.17.255.255 16 65536

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 3 of 4

CCNA Exploration Network Fundamentals: Addressing the Network - IPv4

Activity 6.7.3: IPv4 Address Subnetting Part 1

Problem 5 Host IP Address Network Mask Network Address Network Broadcast Address Total Number of Host Bits 192.168.3.219 255.255.0.0

Number of Hosts

192.168.0.0 192.168.255.254 0 1

Problem 6 Host IP Address Network Mask Network Address Network Broadcast Address Total Number of Host Bits 192.168.3.219 255.255.255.224

Number of Hosts

192.168.3.192 192.168.3.223 5 32

Task 3: Clean Up
Remove anything that was brought into the lab, and leave the room ready for the next class.

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 4 of 4

Activity 6.7.4: IPv4 Address Subnetting Part 2

Learning Objectives
Upon completion of this activity, you will be able to determine subnet information for a given IP address and subnetwork mask.

Background
Borrowing Bits How many bits must be borrowed to create a certain number of subnets or a certain number of hosts per subnet? Using this chart, it is easy to determine the number of bits that must be borrowed. Things to remember: Subtract 2 for the usable number of hosts per subnet, one for the subnet address and one for the broadcast address of the subnet. 210
1,024 Number 10 1,024

29

28

27

26 64

25 32

24 16

23 8

22 4

21 2

20 1

512 256 128 of bits borrowed: 9 8 7 512 256 128 Hosts or

6 5 4 64 32 16 Subnets

3 8

2 4

1 2

1 1

Possible Subnet Mask Values Because subnet masks must be contiguous 1s followed by contiguous 0s, the converted dotted decimal notation can contain one of a certain number of values: Dec. 255 254 252 248 240 224 192 128 0 Binary 11111111 11111110 11111100 11111000 11110000 11100000 11000000 10000000 00000000

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 1 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPv4

Activity 6.7.4: IPv4 Address Subnetting Part 2

Scenario
When given an IP address, network mask, and subnetwork mask, you will be able to determine other information about the IP address such as: The subnet address of this subnet The broadcast address of this subnet The range of host addresses for this subnet The maximum number of subnets for this subnet mask The number of hosts for each subnet The number of subnet bits The number of this subnet

Task 1: For a Given IP Address and Subnet Mask, Determine Subnet Information.
Given: Host IP Address Network Mask Subnet Mask 172.25.114.250 255.255.0.0 (/16) 255.255.255.192 (/26)

Find: Number of Subnet Bits Number of Subnets Number of Host Bits per Subnet Number of Usable Hosts per Subnet Subnet Address for this IP Address IP Address of First Host on this Subnet IP Address of Last Host on this Subnet Broadcast Address for this Subnet

10 1024 6 62 172.25.114.192 172.25.114.1 172.25.114.254 172.25.114.255

Step 1: Translate host IP address and subnet mask into binary notation. 172 10101100 11111111 255 25 11001000 11111111 255 114 01110010 11111111 255 250 11111010 11000000 192

IP Address Subnet Mask

Step 2: Determine the network (or subnet) where this host address belongs. 1. Draw a line under the mask. 2. Perform a bit-wise AND operation on the IP Address and the Subnet Mask. Note: 1 AND 1 results in a 1 0 AND anything results in a 0. 3. Express the result in dotted decimal notation.
All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPv4

Activity 6.7.4: IPv4 Address Subnetting Part 2

4. The result is the Subnet Address of this Subnet, which is 172.25.114.192 172 10101100 11111111 10101100 172 25 11001000 11111111 11001000 25 114 01110010 11111111 01110010 114 250 11111010 11000000 11000000 192

IP Address Subnet Mask Subnet Address

Add this information to the table: Subnet Address for this IP Address

172.25.114.192

Step 3: Determine which bits in the address contain network information and which contain host information. 1. Draw the Major Divide (M.D.) as a wavy line where the 1s in the major network mask end (also the mask if there was no subnetting). In our example, the major network mask is 255.255.0.0, or the first 16 left-most bits. 2. Draw the Subnet Divide (S.D.) as a straight line where the 1s in the given subnet mask end. The network information ends where the 1s in the mask end.

3. The result is the Number of Subnet Bits, which can be determined by simply counting the number of bits between the M.D. and S.D., which in this case is 10 bits. Step 4: Determine the bit ranges for subnets and hosts. 1. Label the subnet counting range between the M.D. and the S.D. This range contains the bits that are being incremented to create the subnet numbers or addresses. 2. Label the host counting range between the S.D. and the last bits at the end on the right. This range contains the bits that are being incremented to create the host numbers or addresses.

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 3 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPv4

Activity 6.7.4: IPv4 Address Subnetting Part 2

Step 5: Determine the range of host addresses available on this subnet and the broadcast address on this subnet. 1. Copy down all of the network/subnet bits of the network address (that is, all bits before the S.D.). 2. In the host portion (to the right of the S.D.), make the host bits all 0s except for the right-most bit (or least significant bit), which you make a 1. This gives us the first host IP address on this subnet, which is the first part of the result for Range of Host Addresses for This Subnet, which in the example is 172.25.114.193. 3. Next, in the host portion (to the right of the S.D.), make the host bits all 1s except for the rightmost bit (or least significant bit), which you make a 0. This gives us the last host IP address on this subnet, which is the last part of the result for Range of Host Addresses for This Subnet, which in the example is 172.25.114.254. 4. In the host portion (to the right of the S.D.), make the host bits all 1s. This gives us the broadcast IP address on this subnet. This is the result for Broadcast Address of This Subnet, which in the example is 172.25.114.255.

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 4 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPv4

Activity 6.7.4: IPv4 Address Subnetting Part 2

Lets add some of this information to our table: Host IP Address Major Network Mask 172.25.114.250 255.255.0.0 (/16)

Major (Base) Network Address Major Network Broadcast Address Total Number of Host Bits Number of Hosts

172.25.0.0 172.25.255.255 16 16 bits or 2 or 65,536 total hosts 65,536 2 = 65,534 usable hosts

Subnet Mask Number of Subnet Bits Number of Subnets

255.255.255.192 (/26)

0 /1

Number of Host Bits per Subnet Number of Usable Hosts per Subnet Subnet Address for this IP Address IP Address of First Host on this Subnet IP Address of Last Host on this Subnet Broadcast Address for this Subnet

6 / 62
172.25.114.192 172.25.114.193 172.25.114.254 172.25.114.255

Step 6: Determine the number of subnets. The number of subnets is determined by how many bits are in the subnet counting range (in this example, 10 bits). Use the formula 2 , where n is the number of bits in the subnet counting range. 1. 2
10 n

= 1024 Number of Subnet Bits Number of Subnets (all 0s used, all 1s not used) 10 bits 10 2 = 1024 subnets

Step 7: Determine the number usable hosts per subnet. The number of hosts per subnet is determined by the number of host bits (in this example, 6 bits) minus 2 (1 for the subnet address and 1 for the broadcast address of the subnet). 2 2 = 64 2 = 62 hosts per subnet Number of Host Bits per Subnet Number of Usable Hosts per Subnet 6 bits 6 2 2 = 64 2 = 62 hosts per subnet
6

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 5 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPv4

Activity 6.7.4: IPv4 Address Subnetting Part 2

Step 8: Final Answers Host IP Address Subnet Mask 172.25.114.250 255.255.255.192 (/26)

Number of Subnet Bits Number of Subnets Number of Host Bits per Subnet Number of Usable Hosts per Subnet Subnet Address for this IP Address IP Address of First Host on this Subnet IP Address of Last Host on this Subnet Broadcast Address for this Subnet

26 bits 10 2 = 1024 subnets 6 bits 6 2 2 = 64 2 = 62 hosts per subnet 172.25.114.192 172.25.114.193 172.25.114.254 172.25.114.255

Task 2: Challenge.
For all problems: Create a Subnetting Worksheet to show and record all work for each problem. Problem 1 Host IP Address Subnet Mask Number of Subnet Bits Number of Subnets 172.30.1.33 255.255.255.0

256
8 254 172.30.1.0 172.30.1.1 172.30.1.254 172.30.1.255

Number of Host Bits per Subnet Number of Usable Hosts per Subnet Subnet Address for this IP Address

IP Address of First Host on this Subnet IP Address of Last Host on this Subnet Broadcast Address for this Subnet

Problem 2 Host IP Address Subnet Mask Number of Subnet Bits 172.30.1.33 255.255.255.252

14
16384

Number of Subnets Number of Host Bits per Subnet Number of Usable Hosts per Subnet Subnet Address for this IP Address IP Address of First Host on this Subnet IP Address of Last Host on this Subnet Broadcast Address for this Subnet

2 2 172.30.1.32 172.30.1.33 172.30.1.34 172.30.1.35

Page 6 of 8

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

CCNA Exploration Network Fundamentals: Addressing the Network - IPv4

Activity 6.7.4: IPv4 Address Subnetting Part 2

Problem 3 Host IP Address Subnet Mask Number of Subnet Bits Number of Subnets 192.192.10.234 255.255.255.0

Number of Host Bits per Subnet Number of Usable Hosts per Subnet Subnet Address for this IP Address

IP Address of First Host on this Subnet IP Address of Last Host on this Subnet Broadcast Address for this Subnet

8 254 192.192.10.0 192.192.10.1 192.192.10.254 192.192.10.255

Problem 4 Host IP Address Subnet Mask Number of Subnet Bits 172.17.99.71 255.255.0.0

0
1

Number of Subnets

Number of Host Bits per Subnet Number of Usable Hosts per Subnet Subnet Address for this IP Address IP Address of First Host on this Subnet IP Address of Last Host on this Subnet Broadcast Address for this Subnet

16 65534 172.17.0.0 172.17.0.1 172.17.255.254 172.17.255.255

Problem 5 Host IP Address Subnet Mask Number of Subnet Bits Number of Subnets 192.168.3.219 255.255.255.0

0
1
8 254 192.168.3.0 192.168.3.1 192.168.3.254 192.168.3.255

Number of Host Bits per Subnet Number of Usable Hosts per Subnet Subnet Address for this IP Address

IP Address of First Host on this Subnet IP Address of Last Host on this Subnet Broadcast Address for this Subnet

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 7 of 8

CCNA Exploration Network Fundamentals: Addressing the Network - IPv4

Activity 6.7.4: IPv4 Address Subnetting Part 2

Problem 6 Host IP Address Subnet Mask Number of Subnet Bits Number of Subnets 192.168.3.219 255.255.255.252

64

Number of Host Bits per Subnet Number of Usable Hosts per Subnet Subnet Address for this IP Address IP Address of First Host on this Subnet IP Address of Last Host on this Subnet Broadcast Address for this Subnet

2 2 192.168.3.216 192.168.3.217 192.168.3.218 192.168.3.219

Task 3: Clean Up
Remove anything that was brought into the lab, and leave the room ready for the next class.

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 8 of 8

Lab 6.7.5: Subnet and Router Configuration

Topology Diagram
192.168.1.21 /27
192.168.1.64 /27
192.168.1.96 /27

Addressing Table
Device R1 Interface Fa0/0 S0/0/0 Fa0/0 S0/0/0 NIC NIC IP Address
192.168.1.33 192.168.1.65 192.168.1.97 192.168.1.94 192.168.1.62

Subnet Mask
255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224

Default Gateway N/A N/A N/A N/A

192.168.1.33

R2 PC1 PC2

192.168.1.126

255.255.255.224

192.168.1.97

Learning Objectives
Upon completion of this lab, you will be able to: Subnet an address space per given requirements. Assign appropriate addresses to interfaces and document. Configure and activate Serial and FastEthernet interfaces. Test and verify configurations. Reflect upon and document the network implementation.

Scenario
In this lab activity, you will design and apply an IP addressing scheme for the topology shown in the Topology Diagram. You will be given one address block that you must subnet to provide a logical addressing scheme for the network. The routers will then be ready for interface address configuration according to your IP addressing scheme. When the configuration is complete, verify that the network is working properly.

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 1 of 3

CCNA Exploration Network Fundamentals: Addressing the Network - IPV4

Lab 6.7.5: Subnet and Router Configuration

Task 1: Subnet the Address Space.

Step 1: Examine the network requirements. You have been given the 192.168.1.0/24 address space to use in your network design. The network consists of the following segments: The LAN connected to router R1 will require enough IP addresses to support 15 hosts. The LAN connected to router R2 will require enough IP addresses to support 30 hosts. The link between router R1 and router R2 will require IP addresses at each end of the link.

The plan should have equal size subnets and use the smallest subnet sizes that will accommodate the appropriate number of hosts. Step 2: Consider the following questions when creating your network design. 3 How many subnets are needed for this network? ____________________
255.255.255.224 What is the subnet mask for this network in dotted decimal format? ____________________
/27 What is the subnet mask for the network in slash format? ____________________ 30 How many usable hosts are there per subnet? ____________________

Step 3: Assign subnetwork addresses to the Topology Diagram. 1. Assign second subnet to the network attached to R1. 2. Assign third subnet to the link between R1 and R2. 3. Assign fourth subnet to the network attached to R2.

Task 2: Determine Interface Addresses.

Step 1: Assign appropriate addresses to the device interfaces. 1. Assign the first valid host address in second subnet to the LAN interface on R1. 2. Assign the last valid host address in second subnet to PC1. 3. Assign the first valid host address in third subnet to the WAN interface on R1. 4. Assign the last valid host address in third subnet to the WAN interface on R2. 5. Assign the first valid host address in fourth subnet to the LAN interface of R2. 6. Assign the last valid host address in fourth subnet to PC2. Step 2: Document the addresses to be used in the table provided under the Topology Diagram.

Task 3: Configure the Serial and FastEthernet Addresses.

Step 1: Configure the router interfaces. Configure the interfaces on the R1 and R2 routers with the IP addresses from your network design. Please note, to complete the activity in Packet Tracer you will be using the Config Tab. When you have finished, be sure to save the running configuration to the NVRAM of the router.

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 2 of 3

CCNA Exploration Network Fundamentals: Addressing the Network - IPV4

Lab 6.7.5: Subnet and Router Configuration

Step 2: Configure the PC interfaces. Configure the Ethernet interfaces of PC1 and PC2 with the IP addresses and default gateways from your network design.

Task 4: Verify the Configurations.

Answer the following questions to verify that the network is operating as expected. yes From the host attached to R1, is it possible to ping the default gateway? __________
yes From the host attached to R2, is it possible to ping the default gateway? __________ yes From the router R1, is it possible to ping the Serial 0/0/0 interface of R2? __________

yes From the router R2, is it possible to ping the Serial 0/0/0 interface of R1? __________

Task 5: Reflection
Are there any devices on the network that cannot ping each other? yes __________________________________________________________________________ __________________________________________________________________________

What is missing from the network that is preventing communication between these devices? switch __________________________________________________________________________ __________________________________________________________________________

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 3 of 3