background image
OSI Network Layer Functions 107
send frames to R3. (See Chapter 8 for more details on Inverse ARP
and Frame Relay mapping.) With that mapping information, R2
can complete the Frame Relay header and send the frame to R3.
Step H
Step 3 of the original algorithm is performed by R3. Like R1 and
R2 before it, R3 checks the FCS in the data link trailer, looks at
the type field to decide whether the packet inside the frame is an
IP packet, and then discards the Frame Relay header and trailer.
The routing table entry for 168.1.0.0 shows that the outgoing
interface is R3's Token Ring interface. However, there is no next
router IP address because there is no need to forward the packet to
another router. R3 simply needs to build a Token Ring header and
trailer and forward the frame that contains the original packet to
PC2. Before R3 can finish building the Token Ring header, an IP
ARP must be used to find PC2's MAC address (assuming that R3
doesn't already have that information in its IP ARP cache).
Network Layer (Layer 3) Addressing
Cisco requires that CCNAs master the details of Layer 3 addressing, both the concepts and the
particulars of IP and IPX. One key feature of network layer addresses is that they were designed
to allow logical grouping of addresses. In other words, something about the numeric value of
an address implies a group or set of addresses, all of which are considered to be in the same
grouping. In TCP/IP, this group is called a network or a subnet. In IPX, it is called a network.
In AppleTalk, the grouping is called a cable range.
Network layer addresses are also grouped based on physical location in a network. The rules
differ for some network layer protocols, but the grouping concept is identical for IP, IPX, and
AppleTalk. In each of these network layer protocols, all devices with addresses in the same
group cannot be separated from each other by a router that is configured to route that protocol,
respectively. Stated differently, all devices in the same group (subnet/network/cable range)
must be connected to the same data link; for example, all devices must be connected to the same
Ethernet.
Routing relies on the fact that Layer 3 addresses are grouped together. The routing tables for
each network layer protocol can reference the group, not each individual address. Imagine an
Ethernet with 100 Novell clients. A router needing to forward packets to any of those clients
needs only one entry in its IPX routing table. If those clients were not required to be attached
to the same data link, and if there was no way to encode the IPX network number in the IPX
address of the client, routing would not be capable of using just one entry in the table. This basic
fact is one of the key reasons that routers, using routing as defined by a network layer (Layer
3), can scale to allow tens and hundreds of thousands of devices.
ch03.fm Page 107 Monday, March 20, 2000 4:58 PM