background image
54
Chapter 1
Internetworking
but not necessarily protocols, right? Sometimes a protocol maps to more
than one layer of the OSI model, and sometimes multiple protocols commu-
nicate within a single layer. In the same way, when we build physical imple-
mentations of hierarchical networks, we may have many devices in a single
layer, or we might have a single device performing functions at two layers.
The definition of the layers is logical, not physical.
Now, let's take a closer look at each of the layers.
The Core Layer
The core layer is literally the core of the network. At the top of the hier-
archy, the core layer is responsible for transporting large amounts of traf-
fic both reliably and quickly. The only purpose of the network's core layer
is to switch traffic as fast as possible. The traffic transported across the
core is common to a majority of users. However, remember that user data
is processed at the distribution layer, which forwards the requests to the
core if needed.
If there is a failure in the core, every single user can be affected. There-
fore, fault tolerance at this layer is an issue. The core is likely to see large
volumes of traffic, so speed and latency are driving concerns here. Given
the function of the core, we can now consider some design specifics. Let's
start with some things we don't want to do.
Don't do anything to slow down traffic. This includes using access
lists, routing between virtual local area networks (VLANs), and
packet filtering.
Don't support workgroup access here.
Avoid expanding the core when the internetwork grows (i.e., adding
routers). If performance becomes an issue in the core, give prefer-
ence to upgrades over expansion.
Now, there are a few things that we want to do as we design the core.
They include the following:
Design the core for high reliability. Consider data-link technologies
that facilitate both speed and redundancy, such as FDDI, Fast Ether-
net (with redundant links), or even ATM.
Design with speed in mind. The core should have very little latency.
Copyright ©2002 SYBEX, Inc., Alameda, CA
www.sybex.com