16.06.2014 Views

Cisco CCNA Study Guide - Router Alley

Cisco CCNA Study Guide - Router Alley

Cisco CCNA Study Guide - Router Alley

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

<strong>CCNA</strong> <strong>Study</strong> <strong>Guide</strong> v2.62 – Aaron Balchunas<br />

41<br />

Layer-3 Routing<br />

Layer-3 routing is the process of forwarding a packet from one network to<br />

another network, based on the Network-layer header. <strong>Router</strong>s build routing<br />

tables to perform forwarding decisions, which contain the following:<br />

• The destination network and subnet mask<br />

• The next hop router to get to the destination network<br />

• Routing metrics and Administrative Distance<br />

Note that Layer-3 forwarding is based on the destination network, and not<br />

the destination host. It is possible to have host routes, but this is less<br />

common.<br />

The routing table is concerned with two types of Layer-3 protocols:<br />

• Routed protocols - assigns logical addressing to devices, and routes<br />

packets between networks. Examples include IP and IPX.<br />

• Routing protocols - dynamically builds the information in routing<br />

tables. Examples include RIP, EIGRP, and OSPF.<br />

Each individual interface on a router belongs to its own collision domain.<br />

Thus, like switches, routers create more collision domains, which results in<br />

fewer collisions.<br />

Unlike Layer-2 switches, Layer-3 routers also separate broadcast domains.<br />

As a rule, a router will never forward broadcasts from one network to<br />

another network (unless, of course, you explicitly configure it to). ☺<br />

<strong>Router</strong>s will not forward multicasts either, unless configured to participate in<br />

a multicast tree. Multicast is covered in great detail in another guide.<br />

Traditionally, a router was required to copy each individual packet to its<br />

buffers, and perform a route-table lookup. Each packet consumed CPU<br />

cycles as it was forwarded by the router, resulting in latency. Thus, routing<br />

was generally considered slower than switching.<br />

It is now possible for routers to cache network-layer flows in hardware,<br />

greatly reducing latency. This has blurred the line between routing and<br />

switching, from both a technological and marketing standpoint. Caching<br />

network flows is covered in greater detail shortly.<br />

* * *<br />

All original material copyright © 2013 by Aaron Balchunas (aaron@routeralley.com),<br />

unless otherwise noted. All other material copyright © of their respective owners.<br />

This material may be copied and used freely, but may not be altered or sold without the expressed written<br />

consent of the owner of the above copyright. Updated material may be found at http://www.routeralley.com.

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

Saved successfully!

Ooh no, something went wrong!