28.06.2014 Views

Discussion

Discussion

Discussion

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

talking with other routers and advertising routing information to them. A number of<br />

other software modules run in the router’s control plane, including the CLI and<br />

accounting processes such as SNMP. Each of these modules runs as a separate process<br />

in the JUNOS software, and, in some cases, multiple instances of a module<br />

might be running (for instance, if two users are logged in to the router, two CLI<br />

processes run).<br />

The PFE is the router’s forwarding plane, housing the forwarding table and handling<br />

most forwarding processing. Forwarding is the process of receiving a packet on an<br />

inbound interface, de-encapsulating it, executing a number of packet-processing<br />

activities (such as filtering, accounting, and next-hop determination), encapsulating<br />

it, and queuing it on the outbound interface toward the packet’s destination. The<br />

PFE consists of custom ASICs and the router’s input and output interfaces. The ASICs<br />

use the forwarding table to perform route lookup, looking up the IP address prefix<br />

and determining the output interface (next hop) for the packet. The link between the<br />

Routing Engine and the PFE is a standard Fast Ethernet link (the fxp1 interface).<br />

On the smaller J-series routers, the control and data planes are handled by the same<br />

CPU, which runs the software for both the RE and PFE.<br />

RPD installs all active routes from the routing tables into the forwarding table. The<br />

JUNOS kernel maintains a master copy of the forwarding table and copies the table<br />

to the PFE. The operation to update the forwarding table is done atomically, one<br />

route at a time. This ensures that the forwarding table always has a single view of<br />

how to forward traffic on the network.<br />

IPv4 and IPv6 Addresses<br />

IPv4 addresses are 32 bits long and are written in a dotted quad notation. Originally,<br />

IPv4 addresses were divided into four classes, Classes A, B, C, and D. This type of<br />

addressing is called classful. Classful addresses require an address and a network<br />

mask. The address consists of a network portion and a host portion. The subnetwork<br />

mask defines how to interpret the address bits in order to know which are being used<br />

for the network portion and which for the host portion.<br />

The IETF developed classless addresses in the late 1990s with the introduction of<br />

Classless Interdomain Routing (CIDR). This was done as one way to increase the<br />

number of network addresses available on the Internet. All IPv4 addresses on<br />

JUNOS routers are expressed in CIDR format. Instead of network and host portions<br />

and subnetwork masks, CIDR addresses have a prefix that represents the network<br />

address, followed by a slash and the prefix length, which identifies the number of bits<br />

being used for the network address. For example, one of the groups of routers used<br />

as examples in this book has interface addresses in the network 10.0.1.0/24. Here,<br />

the prefix is 10.0.1.0, and 24 bits are used for the network prefix. The remaining 8<br />

bits are available for host addresses, so this network can have up to 256 hosts.<br />

248 | Chapter 8: IP Routing<br />

This is the Title of the Book, eMatter Edition<br />

Copyright © 2008 O’Reilly & Associates, Inc. All rights reserved.

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

Saved successfully!

Ooh no, something went wrong!