05.01.2013 Views

CCNA Cisco Certified Network Associate Study Guide - FTP Server

CCNA Cisco Certified Network Associate Study Guide - FTP Server

CCNA Cisco Certified Network Associate Study Guide - FTP Server

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

238 Chapter 5 � IP Routing<br />

In our example, a user on Host A pings Host B’s IP address. It will not get<br />

simpler than this. Let’s work through the steps.<br />

1. From a command prompt, the user types ping 172.16.20.2. A packet<br />

is generated on the Host A machine using the IP and ICMP <strong>Network</strong><br />

layer protocols.<br />

2. IP works with the ARP protocol to determine what network this packet<br />

is destined for by looking at the IP address and the subnet mask of Host<br />

A. Since this is a request for a remote host, which means it is not destined<br />

to be sent to a host on the local network, the packet must be sent<br />

to the router so that it will be routed to the correct remote network.<br />

3. For Host A to send the packet to the router, it must know the hardware<br />

address of the router’s interface located on the local network.<br />

Remember that the <strong>Network</strong> layer will hand the packet and the destination<br />

hardware address to the Data Link layer for framing and transmitting<br />

on a local host. To get the hardware address, the host looks in<br />

a location in memory called the ARP cache.<br />

4. If the IP address has not already been resolved to a hardware address<br />

and is not in the ARP cache, the host sends an ARP broadcast looking,<br />

for the hardware address of IP address 172.16.10.1. This is why the<br />

first Ping usually times out, and the other four are successful. After the<br />

address is cached, no timeouts usually occur.<br />

5. The router responds with the hardware address of the Ethernet interface<br />

connected to the local network. The host now has everything it<br />

needs to transmit the packet out on the local network to the router.<br />

The <strong>Network</strong> layer hands down the packet it generated with the ICMP<br />

echo request (Ping) to the Data Link layer, along with the hardware<br />

address of where the host wants to send the packet. The packet<br />

includes the IP source address and the destination IP address, as well<br />

as the ICMP specified in the <strong>Network</strong> layer protocol field.<br />

6. The Data Link layer creates a frame, which encapsulates the packet<br />

with the control information needed to transmit on the local network.<br />

This includes the source and destination hardware addresses and the<br />

type field specifying the <strong>Network</strong> layer protocol (it is a type field since<br />

IP uses an Ethernet_II frame by default). Figure 5.2 shows the frame<br />

that will be generated by the Data Link layer and sent out on the local<br />

media.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!